diff --git a/marked/Q/T-REC-Q.1101-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1101-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a515851d4223b6c54fe3e127a03f378fc1fd95ab --- /dev/null +++ b/marked/Q/T-REC-Q.1101-198811-I_PDF-E/raw.md @@ -0,0 +1,658 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1101** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERWORKING WITH SATELLITE MOBILE SYSTEMS** + +## --- **GENERAL REQUIREMENTS FOR THE INTERWORKING OF THE TERRESTRIAL TELEPHONE NETWORK AND INMARSAT STANDARD A SYSTEM** + +**ITU-T Recommendation Q.1101** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation Q.1101 was published in Fascicle VI.14 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. + +## GENERAL REQUIREMENTS FOR THE INTERWORKING OF THE TERRESTRIAL TELEPHONE NETWORK AND INMARSAT STANDARD A SYSTEM + +## 1 Introduction + +1.1 The purpose of this Recommendation is to define the general interworking requirements between the telephone network and the INMARSAT Standard A system. + +1.2 In order to support automatic working between subscribers in the public telephone service and telephone subscribers to the maritime mobile-satellite service, it is necessary that the interface between the terrestrial telephone network and the maritime satellite system be defined. + +1.3 It should be possible to interface the maritime-mobile satellite system with any signalling system standardized by the CCITT for automatic working. In order to facilitate the preparation of the interworking equipment, and also aiming at the international standardization of the service, this Recommendation lists several basic interworking requirements common to all signalling systems. + +1.4 More specific interworking requirements applicable to System No. 5 are given in Recommendation Q.1103 and System R2 are given in Recommendation Q.1102. + +1.5 A brief description of the INMARSAT Standard A system is given in Annex A. SDL descriptions of incoming and outgoing signalling procedures for the INMARSAT system are given in Annexes B and C respectively. + +1.6 Interworking between the telephone network/ISDN and other INMARSAT systems is given in separate Q-Series Recommendations. + +## 2 Maritime satellite switching centre + +For the purpose of this Recommendation the term Maritime Satellite Switching Centre (MSSC) is used to indicate the interworking point between the terrestrial telephone network and the maritime satellite system. The maritime satellite switching centre (MSSC) may be located at the antenna site of the coast earth station [1] and operate as an independent international switching centre connected to one or more international switching centres (ISCs) or national switching centres, or it may be remote as a supplement to or as a part of an international switching centre. + +## 3 List of general Series Q Recommendations + +Due regard should be paid to the following general Series Q Recommendations: + +- Q.11, Q.11*bis*, Q.11*ter*, and Q.12, Q.13, numbering and routing plan +- Q.14, means of controlling the number of satellite links +- Q.15 through Q.22, general Recommendations +- Q.23, technical features of push-button telephone sets +- Q.25, splitting arrangement +- Q.26 through Q.33, miscellaneous provisions +- Q.35, tones of national signalling systems +- Q.40 through Q.45, transmission characteristics +- Q.102, facilities provided in international automatic working +- Q.103, numbering used +- Q.104, language digit or discriminating digit + +- Q.105, national (significant) number +- Q.106, the sending-finished signal +- Q.107, sending sequence of forward-address information +- Q.107*bis*, analysis of forward-address information for routing +- Q.109, transmission of the answer signal +- Q.112 through Q.114, transmission clauses +- Q.115, control of echo suppressors +- Q.116 through Q.118*bis*, abnormal conditions. + +## 4 Sending sequence of numerical (or address) signals + +### 4.1 *Calls toward ship earth station [2] (shore-to-ship)* + +In most cases the MSSC will not need the information contained in the S-digit of the country code 87S. In this situation the sequence of forward-address information sent to the MSSC should be as for a terminal international call. + +Cases may arise where an MSSC requires the S-digit to distinguish between ocean areas, satellite systems or VHF/UHF vs. satellite. In this situation the sequence of forward-address information should be as for an international transit call, i.e. the sequence includes the country code 87S. + +### 4.2 *S-digit* + +It is a matter for the terrestrial subscriber to choose the proper S-digit and the MSSC to be used will be decided by the outgoing country. (For technical reasons accounting between Administrations should be performed on the basis of only 87S.) + +### 4.3 *Calls from ship earth station (ship-to-shore)* + +The desired MSSC is selected at the ship earth station by procedures within the maritime satellite system. After the dialling tone has been provided to the subscriber, he will dial a prefix followed by the full international telephone number required, whether or not the MSSC is located in the required subscriber's country (see also Recommendation Q.11*quater*). + +The prefix must be suppressed by the MSSC since it is only required for internal routing in the MSSC. + +For calls to subscribers in the MSSC country, the country code should also be suppressed by the MSSC. + +A discriminating digit must be inserted by the MSSC according to Recommendation Q.104. + +### 4.4 *Operator services* + +The desired MSSC is selected at the ship earth station by procedures within the maritime satellite system. After the dialling tone has been provided to the subscriber, he will dial a two digit prefix, possibly followed by a 1, 2 or 3 digit country code, to identify the type of operator required (see Recommendation Q.11*quater*). + +The MSSC could then convert the received dialling information as required for setting up the terrestrial connection to the operator. + +### 4.5 *Special service terminations* + +The desired MSSC is selected at the ship earth station by procedures within the maritime satellite system. After the dialling tone has been provided to the subscriber, he will dial a two digit prefix possibly followed by other digits to identify the type of special service termination required. (See Recommendation Q.11*quater*.) The MSSC should convert the received dialling information as required for setting up the terrestrial connection. + +## 5 Special requirements related to setting-up and clearing of automatic calls + +### 5.1 *Setting-up time for shore originated calls* + +The setting-up time for shore originated calls should be as short as possible. If the MSSC has not been able to establish the connection within a period of 20 seconds after receipt of all address digits, a congestion indication should be returned. + +*Note* - In maritime satellite systems the setting-up time is not controlled by each individual MSSC but may depend on the overall traffic load in the system and on the assignment procedure used. For several reasons the setting-up time of the radio path is likely to be longer than the setting-up time of the subscriber connection in terrestrial systems. + +### 5.2 *Transmission of answer signal* + +5.2.1 When the maritime satellite switching centre (MSSC) detects the answer signal from the maritime satellite system, the MSSC must remove the ringing tone, through-connect the circuit and return the answer signal as soon as possible to the terrestrial switching centre. + +Precautions should be taken at the MSSC to avoid interpreting an interruption of the satellite link as an answer signal. + +5.2.2 For ship originated calls the maritime satellite system should preferably include provisions for transferring the answer signal to the ship earth station. + +### 5.3 *Seizure of a terrestrial circuit from the MSSC* + +The maritime satellite switching centre should not seize a terrestrial circuit before each of the following conditions has been met: + +- the satellite channel has been assigned; +- the continuity of the satellite channel has been verified; +- all digits necessary for routing decision by the maritime satellite switching centre have been received. + +### 5.4 *Clear-back conditions* + +5.4.1 The clear-back/re-answer sequence may not apply for shore originated calls, in which case the satellite link will be released when a clear-back signal is detected at the maritime satellite switching centre from the satellite link, without waiting for a clear-forward signal from the terrestrial network. + +Precautions should be taken either at the MSSC or at the ship earth station in order to avoid unintentional clearing. + +5.4.2 For ship originated calls the normal clear-back procedures should apply (see Recommendation Q.118). + +### 5.5 *Clear-forward* + +When detecting a clear-forward from the satellite link, the MSSC should immediately pass the clear-forward signal into the terrestrial network. + +When detecting a clear-forward from the terrestrial network, the release guard (and clearing) sequence should follow the procedures defined for the signalling system used. + +### 5.6 *Splitting arrangement* + +When in-band signalling is used over the satellite link for setting-up and clearing of the link, a splitting arrangement shall be provided in order to avoid that signalling tones are passed into the terrestrial network. The splitting time shall be less than 20 ms. + +In order to protect the maritime satellite system from line signals used on terrestrial signalling systems, it should be observed that such signalling tones passing through splitting arrangements in the terrestrial network may have a maximum duration of 50 ms. + +## 6 Audible tones sent by the MSSC + +Tones sent by the maritime switching centre (MSSC) should have the following characteristics: + +| | | +|---------------------------|------------------------------------------------------------------------------------| +| Dial tone: | 425 Hz (1.5 seconds maximum, minimum is determined by receipt of first dial digit) | +| Ringing tone: | 425 Hz (1 second on, 4 seconds off, immediate ringing) | +| Busy tone: | 425 Hz (1/2 second on, 1/2 second off) | +| Congestion tone: | 425 Hz (1/4 second on, 1/4 second off) | +| Special information tone: | as defined in Recommendation Q.35. | + +*Note* - The dial tone is given as 1.5 seconds pulse in order to avoid subscribers' confusion due to the two-way transmission delay of 0.5 seconds. If the normal continuous tone with interruption after the receipt of the first digit was used, the delay would cause the tone to stay on after entry of the first digit. + +## 7 Control of echo suppressors + +Since all calls to and from a ship earth station will include a satellite link, appropriate actions must be taken to insert an incoming or outgoing half-echo suppressor at the MSSC or at an international exchange closer to the terrestrial subscriber. The ship earth station will connect to the satellite link on a 4-wire basis or will be provided with the equivalent of a half-echo suppressor. In order to reduce the analysis and control requirements at the MSSC it may prove convenient to carry out all echo suppressor control at one of the international exchanges rather than at the MSSC. This is most easily achieved by fitting permanent half-echo suppressors at the ISC end of each MSSC-ISC circuit. In any case the overall echo control requirements are the same as specified in Recommendation Q.115. + +### 7.1 *Terrestrial signalling systems with signals for control of echo suppressors* + +#### 7.1.1 *Ship original calls* + +The MSSC should send an echo suppressor indicator informing transit centres or incoming centres whether or not an incoming half-echo suppressor should be included. + +Insertion of an incoming half-echo suppressor will always be requested if the MSSC does not carry out echo suppressor control. + +#### 7.1.2 *Shore originated calls* + +The MSSC will decide whether or not to insert an outgoing half-echo suppressor depending on the received echo suppressor indicator. If echo control is not performed at the MSSC, the echo suppressor indicator will always inform the MSSC that an outgoing half-echo suppressor has already been included. + +### 7.2 *Terrestrial signalling systems without signals from control of echo suppressors* + +When signals for the control of echo suppressors are not available on the particular terrestrial route, significant advantage is to be gained by carrying out the echo suppressor control at the international exchange. In any case the following rules should be observed: + +#### 7.2.1 *Ship originated calls* + +- When the terrestrial connection between the outgoing ISC, (or MSSC) and the incoming ISC (or national incoming switching centre) does not normally require the use of echo suppressors, the outgoing ISC (or MSSC) should enable (or insert) an incoming half-echo suppressor associated with the satellite link. +- When the terrestrial connection between the outgoing ISC (or MSSC) and the incoming ISC (or national incoming switching centre) normally requires the use of echo suppressors, the outgoing ISC (or MSSC) should disable (or should not insert) any half-echo suppressors associated with either the satellite link or the terrestrial link. + +#### 7.2.2 Shore originated calls + +- When the international connection between the outgoing ISC and the incoming ISC (or MSSC) does not normally require the use of echo suppressors, the incoming ISC (or MSSC) should enable (or insert) an outgoing half-echo suppressor associated with the satellite link. +- When the international connection between the outgoing ISC and the incoming ISC (or MSSC) normally requires the use of echo suppressors, the incoming ISC (or MSSC) should disable (or should not insert) any half-echo suppressors associated with either the satellite or terrestrial link. + +## 8 Handling of group calls + +### 8.1 General + +A group call is a simultaneous call to a given group of ships. Such calls are identified by the following international number: + +$$87S0X_2X_3 \dots X_k$$ + +where the first digit of the ship station number has the fixed value 0. The remaining digits determine which group of ships is being addressed. + +Facilities for originating group calls from operators either in the MSSC country or another country may be readily made available by permitting such calls only when the Z digit is a language digit. Group calls originating from ordinary telephone subscribers should not be permitted so long as calling line identification is not available. + +### 8.2 Barring at the ISC of origin + +In order to avoid setting up of the international chain for unauthorized group calls from ordinary subscribers, barring of such calls should, as a general rule, be done at the ISC of origin. + +### 8.3 Barring at the MSSC + +Barring should also be provided at the MSSC in order to reject group call attempts from ships or from subscribers in countries where barring at the outgoing ISC is not possible. + +## 9 Avoiding two or more satellite links in tandem + +### 9.1 Shore originated calls + +The country code 87S should be analysed at all transit centres where the call may either be routed on a circuit containing a satellite link or on a circuit not containing a satellite link. The latter circuit should always be chosen (see Recommendation Q.14). + +### 9.2 Ship originated calls + +If the signalling system provided between the MSSC and the terrestrial network contains signals which may be used to indicate that one satellite link is included, such signals should be used. + +If the signalling system does not contain such signals, the outgoing ISC should avoid forwarding the call on an outgoing circuit which includes a satellite link. If, however, the signalling system employed between the outgoing ISC and the next ISC in the connection contains such signals, the outgoing ISC should insert the required information. The outgoing ISC could base its procedure upon incoming route identification. + +## 10 Operator assistance for semi-automatic shore originated calls + +If code 11/12 assistance facilities are not provided at the MSSC, then arrangements should be made to intercept such calls at the preceding ISC and route them to an appropriate operator. + +It may be advantageous for Administrations to provide a publicized number (e.g. C12XXXX) for specialized assistance on calls to the maritime network. + +## ANNEX A + +(to Recommendation Q.1101) + +### **Brief description of the INMARSAT Standard A system** + +### A.1 *Introduction* + +This annex describes the signalling in the INMARSAT Standard A system in a multiple Maritime Satellite Switching Centre (MSSC) configuration, i.e., there is more than one MSSC serving an ocean region. Automatic call set-up and clearing are illustrated below. For calls which cannot be completed, the subscriber will receive from the MSSC or the terrestrial network the proper audible tone which describes the call status (i.e., busy tone, congestion tone). + +### A.2 *System configuration* + +The INMARSAT system is composed as shown in Figure A-1/Q.1101. Only the components required for interfacing the telephone network are shown. There are additional interfaces similar to the MSSC for interfacing the telex network and the international public data network. + +The purpose of the MSSC is defined in § 2 of the Recommendation. + +There is one operating Network Coordination Station (NCS) in each ocean area (there may in addition be one or more standby NCSs per ocean area). The main functions of the NCS are as follows. + +The ship earth stations can only monitor one calling channel in the shore-to-ship direction. This calling channel, denoted as the common assignment channel, is transmitted by the NCS. Each coast earth station transmits its own calling channel which is monitored by the NCS for relaying signalling messages from a coast earth station to a ship. + +The NCS also performs all assignment of telephone channels on a call-by-call basis and monitors the actual use of the channels for maintenance purposes. The NCS keeps an up-dated list of all busy ships in the ocean area. If a coast earth station calls a busy ship, the NCS may thus return a ship busy indication to the calling coast earth station on the common assignment channel. + +The procedures are further described below. + +### A.3 *Ship earth station originated calls* + +The normal call set-up procedure for automatic call processing from a ship earth station is shown in Figure A-2/Q.1101. The ship earth station transmits an out-of-band request message which includes the type of call desired, the identify of the MSSC through which the terminal wishes to communicate and the identification number of the ship earth station. + +![Diagram of the maritime satellite system composition for interconnection with the telephone network. A ship earth station on a vessel is connected via a dashed line to a coast earth station. This coast earth station is connected to an MSSC (Mobile Switching Center), which is in turn connected to a telephone network. Another coast earth station is shown connected to an NCS (Network Coordination Station), which is connected to an MSSC. A dashed line with an asterisk (*) connects the NCS to the MSSC. The diagram is labeled 'CCITT - 59 700'.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Diagram of the maritime satellite system composition for interconnection with the telephone network. A ship earth station on a vessel is connected via a dashed line to a coast earth station. This coast earth station is connected to an MSSC (Mobile Switching Center), which is in turn connected to a telephone network. Another coast earth station is shown connected to an NCS (Network Coordination Station), which is connected to an MSSC. A dashed line with an asterisk (\*) connects the NCS to the MSSC. The diagram is labeled 'CCITT - 59 700'. + +\* The NCS of an ocean area will normally be co-located with an MSSC of that area. + +FIGURE A-1/Q.1101 + +#### **Composition of the maritime satellite system for interconnection with the telephone network** + +The MSSC upon reacting to the received *request* message, sends a *Request for Assignment* message to the Network Coordination Station (NCS). The NCS receiving the *request for assignment* message assigns a channel (frequency) and transmits this information in an *assignment* message to both the MSSC and the ship earth station. Both the MSSC and ship earth station receive the *assignment* message, automatically select the correct frequency, and initiate a continuity by transmitting a 2600 Hz tone. + +When continuity has been established, the MSSC sends a dial tone pulse to the ship earth station. The ship earth station subscriber then dials in the desired prefix, country code and national significant number followed by an end-of-selection signal. The signals are transferred as in band push button signals on the satellite link. + +The MSSC proceeds to select a terrestrial trunk and follows the standard signalling sequences of the signalling system used towards the ISC (Figure A-2/Q.1101). The ringing tone from the terrestrial network is allowed to pass directly to the ship earth station subscriber. When the terrestrial party answers the call, the ISC passes the answer signal to the MSSC and the international connection is established. The answer signal, if implemented, may then be passed to the ship earth station1). + +### **A.4 Terrestrial originated calls** + +The normal call set-up procedure for automatic call processing from the terrestrial network to a ship earth station is shown in Figure A-3/Q.1101. The ISC selects a circuit and sends the seizing signal and the mobile terminal identification digits to the MSSC in accordance with the procedures used in the terrestrial signalling system. The MSSC then sends a *request-for-assignment* message to the NCS containing the ship earth station identity. The NCS responds by sending an *assignment* message to both the MSSC and the ship earth station. The MSSC and the ship earth station activate their carriers and send a 2600 Hz tone. Upon receipt of the 2600 Hz tone from the ship earth station the MSSC interprets this as an address complete condition, sends the ringing tone to the terrestrial network and stops sending 2600 Hz to the ship earth station. When the operator or subscriber at the ship earth station answers, the ship earth station discontinues sending its 2600 Hz tone. + +The MSSC recognizes the cutting of the 2600 Hz tone as an answer signal from the ship earth station and begins the answer sequence toward the ISC as shown in Figure A-3/Q.1101. + +1) This is currently under study by INMARSAT. + +![Sequence diagram for ship earth station originated calls (Figure A-2/Q.1101).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +This sequence diagram illustrates the call setup process for a ship earth station originated call. The participants are the Ship earth station, Network coordination station (NCS), Addressed maritime satellite switching centre, and ISC. The process begins with a 'Request' from the ship to the NCS, followed by a 'Request for assignment' from the NCS to the switching centre. An 'Assignment' message is returned from the switching centre via the NCS to the ship. A 'continuity check' is performed between the ship and the switching centre, involving 'SF tone on', 'Carrier on', and 'SF tone off' signals. A '1,5 s Proceed-to-select tone' is sent from the switching centre to the ship. 'Subscriber keying' is indicated at the ship. 'Digits (human cadence)' are sent from the ship to the switching centre. The switching centre sends a 'Seizing' signal to the ISC, followed by 'Inter register signalling'. A 'Ringing tone' and 'Answer' are exchanged between the switching centre and the ISC. Finally, a 'Cut through' is established between the ship and the ISC, and the call is in progress. The diagram is labeled CCITT-39262. + +Sequence diagram for ship earth station originated calls (Figure A-2/Q.1101). + +Note - If implemented. + +FIGURE A-2/Q.1101 + +#### Ship earth station originated calls + +![Sequence diagram for terrestrial originated automatic call (Figure A-3/Q.1101).](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +This sequence diagram illustrates the call setup process for a terrestrial originated automatic call. The participants are the Ship earth station, Network coordination station (NCS), Addressed maritime satellite switching centre, and ISC. The process begins with 'Ringing Off-hook' at the ship. A 'Request for assignment' is sent from the switching centre to the NCS. An 'Assignment' message is returned from the NCS to the ship. A 'continuity check' is performed between the ship and the switching centre, involving 'SF tone on', 'Carrier on', and 'SF tone off' signals. The switching centre sends a 'Seizing' signal to the ISC, followed by 'Inter-register signals' and 'Satellite trunk access'. An 'Address complete' message is sent from the switching centre to the ISC, followed by a 'Ringing tone'. An 'Answer' is received from the ISC by the switching centre. Finally, the call is in progress. The diagram is labeled CCITT-39271. + +Sequence diagram for terrestrial originated automatic call (Figure A-3/Q.1101). + +FIGURE A-3/Q.1101 + +#### Terrestrial originated automatic call + +### A.5 Automatic clearing of calls + +Whether a telephone call originated from a ship earth station or from the terrestrial network, the MSSC, upon receiving a clear-forward signal, will begin to clear the call independently in each direction. + +The MSSC, receiving a 2600 Hz clearing tone from a ship earth station will initiate clearing toward the terrestrial network in accordance with procedures defined for the signalling system used between the MSSC and the ISC. This applies to both clear-forward and clear-back from the ship earth station. Clearing will also be continued in the maritime satellite system independent of the terrestrial network. + +Clearing initiated in the terrestrial network would be recognized by the MSSC receiving the appropriate clear-back or clear-forward signal. For clear-forward, the MSSC would continue clearing with normal terrestrial procedures and begin clearing the maritime satellite circuit. For clear-back from the terrestrial network, normal time-out supervision will take place and clear-forward will commence either after expiry of time-out or after receipt of a clear-forward from the ship, whichever happens first. + +As examples of clearing sequences, Figure A-4/Q.1101 illustrates the clearing of a ship earth station originated call and Figure A-5/Q.1101 illustrates the clearing of a call originated in the terrestrial network. For a terrestrial originated call which has clearing initiated by the ship earth station, the satellite circuit is cleared after the MSSC recognizes the stopping of the ship earth station carrier. The terrestrial circuit is held until the end of release guard sequence as shown in Figure A-5/Q.1101. + +![Sequence diagrams for clearing ship earth station originated calls. Diagram (a) shows clearing initiated by the terrestrial network (Clear-back) with a time-out at the MSSC. Diagram (b) shows clearing initiated by the ship earth station (SES) going on-hook. Both diagrams show the flow of signals (SF tone, carrier off, Clear forward, Release guard) between the Ship earth station, Network coordination station (NCS), Addressed MSSC, and ISC. Diagram (b) includes a 'Subscriber on-hook' event at the ship station and a 'Notification of ship clearing' signal to the MSSC.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` + +sequenceDiagram + participant SES as Ship earth station + participant NCS as Network coordination station (NCS) + participant MSSC as Addressed MSSC + participant ISC as ISC + + Note over SES, ISC: a) Clear-back from terrestrial network; clearing by MSSC on time-out + ISC->>MSSC: Clearback + Note right of MSSC: Time out as defined in Recommendation Q.118 + MSSC->>SES: SF tone on + MSSC->>ISC: Clear forward + SES-->MSSC: SES*) carrier off + ISC->>MSSC: Release guard + SES->>NCS: SF tone and MSSC carrier off + NCS->>MSSC: Notification of ship clearing + + Note over SES, ISC: b) Clearing by ship earth station + Note left of SES: Subscriber on-hook + SES->>MSSC: SF tone on + Note left of SES: ≈ 2 s + MSSC->>ISC: Clear forward + MSSC-->SES: MSSC carrier off + ISC->>MSSC: Release guard + SES->>NCS: SF tone and SES carrier off + NCS->>MSSC: Notification of ship clearing + Note right of MSSC: t < 4 s + +``` + +a) Clear-back from terrestrial network; clearing by MSSC on time-out + +b) Clearing by ship earth station + +CCITT-39281 + +Sequence diagrams for clearing ship earth station originated calls. Diagram (a) shows clearing initiated by the terrestrial network (Clear-back) with a time-out at the MSSC. Diagram (b) shows clearing initiated by the ship earth station (SES) going on-hook. Both diagrams show the flow of signals (SF tone, carrier off, Clear forward, Release guard) between the Ship earth station, Network coordination station (NCS), Addressed MSSC, and ISC. Diagram (b) includes a 'Subscriber on-hook' event at the ship station and a 'Notification of ship clearing' signal to the MSSC. + +SES = Ship earth station + +FIGURE A-4/Q.1101 + +#### Clearing sequences for ship earth station originated calls + +![Two sequence diagrams showing call clearing procedures. Diagram (a) shows 'Clearing by terrestrial network' involving Ship earth station, Network coordination station (NCS), Addressed MSSC, and ISC. Diagram (b) shows 'Clearing by ship earth station' involving Subscriber on-hook, Ship earth station, NCS, Addressed MSSC, and ISC. Both diagrams show signal flows like 'SF tone on', 'SES carrier off', 'MSSC carrier off', 'Notification of ship clearing', 'Clear forward', 'Release guard', 'Clearback', and 'Terrestrial circuit held'.](d4af765160d04ecef538e5066006dc77_img.jpg) + +*a) Clearing by terrestrial network* + +*b) Clearing by ship earth station* + +CCITT-39291 + +Two sequence diagrams showing call clearing procedures. Diagram (a) shows 'Clearing by terrestrial network' involving Ship earth station, Network coordination station (NCS), Addressed MSSC, and ISC. Diagram (b) shows 'Clearing by ship earth station' involving Subscriber on-hook, Ship earth station, NCS, Addressed MSSC, and ISC. Both diagrams show signal flows like 'SF tone on', 'SES carrier off', 'MSSC carrier off', 'Notification of ship clearing', 'Clear forward', 'Release guard', 'Clearback', and 'Terrestrial circuit held'. + +FIGURE A-5/Q.1101 + +#### **Clearing sequences for terrestrial originated calls** + +## ANNEX B + +(to Recommendation Q. 1101) + +### **Logic procedures for incoming INMARSAT Standard A signalling system (ship originated call)** + +This annex only includes those elements of the Standard A INMARSAT system which have to be implemented for interworking purposes. + +Internal procedures such as those required for setting-up and clearing of the satellite link are not shown. They are only indicated by task symbols. + +Other procedures not shown are: + +- interruption control procedures related to the satellite link; +- pre-emption procedures for assigning channels to distress call. + +For more details on the first generation INMARSAT Standard A signalling system, see Annex A. + +![State transition diagram for incoming INMARSAT Standard A signalling system. States are numbered 00 to 07. Transitions: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, 05 to 07, 07 to 00, 07 to 02, 07 to 03, 07 to 04, 07 to 06, 06 to 02, 06 to 03, 06 to 04. A label 'CCITT - 59710' is present below the diagram.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +State transition diagram for incoming INMARSAT Standard A signalling system. States are numbered 00 to 07. Transitions: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, 05 to 07, 07 to 00, 07 to 02, 07 to 03, 07 to 04, 07 to 06, 06 to 02, 06 to 03, 06 to 04. A label 'CCITT - 59710' is present below the diagram. + +CCITT - 59710 + +| State number | State description | Sheet reference | Timers running | +|--------------|-----------------------------------|-----------------|----------------| +| 00 | Idle | 1 | | +| 01 | Wait for continuity | 1 | | +| 02 | Wait for digits | 1 | t 1 | +| 03 | Wait for result of digit analysis | 2 | t 1 | +| 04 | Wait for call set-up | 2 | t 1 | +| 05 | Connected | 2 | | +| 06 | Wait for clear-forward | 2 | t 2 | +| 07 | Wait for clearing | 1 | | + +FIGURE B-1/Q.1101 + +#### **State overview diagrams for incoming INMARSAT Standard A signalling system** + +*Supervisory timers for incoming INMARSAT Standard A signalling system* + +t1 = 15-20 seconds + +t2 = 20-30 seconds + +FIGURE B-2/Q.1101 + +#### **Notes to incoming INMARSAT Standard A signalling system** + +![Flowchart of Incoming INMARSAT Standard A signalling system. The process starts at IDLE (00), receives a REQUEST FROM SHIP, STORES the MESSAGE, and SETS UP the SATELLITE CHANNEL (with INMARSAT system supervision). It then enters WAIT FOR CONTINUITY (01). If CONTINUITY ESTABLISHED, it sends SPITE 6 CONNECT DIAL TONE, then SPITE 1, and STARTS t1 (15-20 seconds). If UNSUCCESSFUL CALL, it DISCONNECTS the SATELLITE CHANNEL (with INMARSAT system disconnection procedure) and returns to IDLE (00). After START t1, it enters WAIT FOR DIGITS (02). From here, ADDRESS SIGNAL, CLEAR FORWARD, or t1-bar can occur. ADDRESS SIGNAL leads to END OF PULSING. If YES, it goes to SPITE 35, STOP t1, STORE END-OF-PULSING DIGIT, then SPITE 12 (Note 1), and connector 2. If NO, it checks SPITE 11. If YES, it goes to START t1 and connector 1. If NO, it goes to START t1 and connector 1. CLEAR FORWARD leads to STOP t1, SPITE 3, and connector 4. t1-bar leads to SPITE 6 and connector 7. After SPITE 12 or SPITE 3, it enters CLEAR SATELLITE CHANNEL (with INMARSAT system clearing procedure), then WAIT FOR CLEARING (07), CHANNEL RELEASED, and finally IDLE (00).](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph TD + 00_1([00 IDLE]) --> RFS[REQUEST FROM SHIP] + RFS --> SM[STORE MESSAGE] + SM --> SC[SET-UP SATELLITE CHANNEL] + SC -.-> S[Signalling procedure defined within the INMARSAT system including time-out supervision] + SC --> 01_1([01 WAIT FOR CONTINUITY]) + 01_1 --> CE[CONTINUITY ESTABLISHED] + 01_1 --> UC[UNSUCCESSFUL CALL] + CE --> SDT[SPITE 6 CONNECT DIAL TONE] + SDT --> S1[SPITE 1] + S1 --> ST1[START t1] + ST1 -.-> ST1_T[15-20 seconds] + ST1 --> 02_1([02 WAIT FOR DIGITS]) + UC --> DC[DISCONNECT SATELLITE CHANNEL] + DC -.-> D[Disconnection procedure defined within the INMARSAT system] + DC --> 00_2([00 IDLE]) + 02_1 --> AS[ADDRESS SIGNAL] + 02_1 --> CF[CLEAR FORWARD] + 02_1 --> TB[ $\bar{t}_1$ ] + AS --> EP{END OF PULSING} + EP -- YES --> S35[SPITE 35] + S35 --> ST1_2[STOP t1] + ST1_2 --> SED[STORE END-OF-PULSING DIGIT] + SED --> S12[SPITE 12 Note 1] + S12 --> 2_2((2 2)) + EP -- NO --> S11{SPITE 11} + S11 -- YES --> ST1_3[START t1] + ST1_3 --> 1_1((1 1)) + S11 -- NO --> ST1_4[START t1] + ST1_4 --> 1_1 + CF --> ST1_5[STOP t1] + ST1_5 --> S3[SPITE 3] + S3 --> 4_2((4 2)) + TB --> S6[SPITE 6] + S6 --> 7_2((7 2)) + S3 --> 6_2((6 2)) + 6_2 --> CSC[CLEAR SATELLITE CHANNEL] + CSC -.-> C[Clearing procedure defined within INMARSAT system including time-out supervision] + CSC --> 07_1([07 WAIT FOR CLEARING]) + 07_1 --> CR[CHANNEL RELEASED] + CR --> 00_3([00 IDLE]) + 1_1 --> 1_2((1 2)) + 2_2 --> 1_2 + 4_2 --> 1_2 + 7_2 --> 1_2 + 6_2 --> 1_2 + +``` + +Flowchart of Incoming INMARSAT Standard A signalling system. The process starts at IDLE (00), receives a REQUEST FROM SHIP, STORES the MESSAGE, and SETS UP the SATELLITE CHANNEL (with INMARSAT system supervision). It then enters WAIT FOR CONTINUITY (01). If CONTINUITY ESTABLISHED, it sends SPITE 6 CONNECT DIAL TONE, then SPITE 1, and STARTS t1 (15-20 seconds). If UNSUCCESSFUL CALL, it DISCONNECTS the SATELLITE CHANNEL (with INMARSAT system disconnection procedure) and returns to IDLE (00). After START t1, it enters WAIT FOR DIGITS (02). From here, ADDRESS SIGNAL, CLEAR FORWARD, or t1-bar can occur. ADDRESS SIGNAL leads to END OF PULSING. If YES, it goes to SPITE 35, STOP t1, STORE END-OF-PULSING DIGIT, then SPITE 12 (Note 1), and connector 2. If NO, it checks SPITE 11. If YES, it goes to START t1 and connector 1. If NO, it goes to START t1 and connector 1. CLEAR FORWARD leads to STOP t1, SPITE 3, and connector 4. t1-bar leads to SPITE 6 and connector 7. After SPITE 12 or SPITE 3, it enters CLEAR SATELLITE CHANNEL (with INMARSAT system clearing procedure), then WAIT FOR CLEARING (07), CHANNEL RELEASED, and finally IDLE (00). + +Note 1 - Includes also translation of prefixes to the appropriate destination number. + +FIGURE B-3/Q.1101 +(sheet 1 of 2) + +#### Incoming INMARSAT Standard A signalling system + +![Flowchart of the Incoming INMARSAT Standard A signalling system (sheet 2 of 2).](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +The flowchart illustrates the signalling logic for an incoming INMARSAT Standard A call. It begins at connector 2, leading to state 03 (WAIT FOR RESULT OF DIGIT ANALYSIS). From here, multiple signal inputs are monitored: ADDRESS SIGNAL, SPITE 15, 16, 17, 18, 19, SPITE 13, SPITE 14 (Note 2), CLEAR-FORWARD, and $t_1$ . + +- The **ADDRESS SIGNAL** path leads to a decision 'END OF PULSING'. If 'NO', it triggers 'START $t_1$ '. If 'YES', it proceeds to 'STOP $t_1$ ', 'STORE END-OF-PULSING DIGIT', and 'SPITE 35', returning to connector 2. +- The **SPITE 15, 16, 17, 18, 19** path leads to 'YES' or 'NO' for 'EoP RECEIVED'. If 'YES', it triggers 'STOP $t_1$ ', 'SPITE 6', and 'SPITE 3', then 'START $t_2$ ' (where $t_2 = 20-30$ seconds), leading to state 06 (WAIT FOR CLEAR-FORWARD). From state 06, 'CLEAR-FORWARD' leads to 'STOP $t_2$ ' and connector 4. If 'EoP RECEIVED' is 'NO', it returns to connector 1. +- The **SPITE 13** path returns to connector 1. +- The **SPITE 14 (Note 2)** path leads to 'ACTIVATE INTER-WORKING PROCEDURE' and 'WHICH CATEGORY'. Categories include 'Ordinary call' (FITE 17), 'Priority call' (FITE 18), and 'Data call' (FITE 19), all leading to 'FITE 1'. 'FITE 1' leads to 'ANY MORE DIGITS'. If 'YES', it triggers 'START $t_1$ '. If 'NO', it leads to state 04 (WAIT FOR CALL SET-UP). +- The **CLEAR-FORWARD** path leads to 'STOP $t_1$ ' and connector 4. +- The **$t_1$** path leads to 'SPITE 6' and connector 7. + +From state 04 (WAIT FOR CALL SET-UP), signals like ADDRESS SIGNAL, BITE 28, CLEAR-FORWARD, BITE 27, and $t_1$ are monitored: + +- ADDRESS SIGNAL** leads to 'FITE 1' and then a decision 'END OF PULSING'. If 'YES', it returns to state 04. If 'NO', it triggers 'START $t_1$ '. +- BITE 28** leads to connector 7. +- CLEAR-FORWARD** leads to 'FITE 22' and connector 4. +- BITE 27** leads to 'STOP $t_1$ ' and connector 5. +- $t_1$** leads to 'FITE 22', 'SPITE 6', and connector 7. + +A separate branch from connector 5 includes 'SPITE 4', 'SPITE 3', and state 05 (CONNECTED). From state 05: + +- BITE 22** leads to 'ANSWER (Note 3)'. +- CLEAR-FORWARD** leads to 'FITE 22' and connector 6. +- BITE 29** leads to connector 6. + +Flowchart of the Incoming INMARSAT Standard A signalling system (sheet 2 of 2). + +Note 2 - Includes also address translated from any received prefixes. + +Note 3 - If implemented. + +FIGURE B-3/Q.1101 +(sheet 2 of 2) + +Incoming INMARSAT Standard A signalling system + +CCITT - 66041 + +## ANNEX C + +(to Recommendation Q.1101) + +### **Logic procedures for outgoing INMARSAT Standard A signalling system (shore originated call)** + +This annex only includes those elements of the INMARSAT Standard A system which have to be implemented for interworking purposes. + +Internal procedures such as those required for setting-up and clearing of the satellite link are not shown. They are only included by task symbols. + +Other procedures not shown are: + +- interruption control procedures related to the satellite link; +- pre-emption procedures for assigning channels to distress calls. + +For more details on the first generation INMARSAT Standard A signalling system, see Annex A. + +![State overview diagram for outgoing INMARSAT Standard A signalling system. It shows a sequence of states 00 to 06 with transitions between them. State 00 is Idle, 01 is Wait for CPCI Fite, 02 is Wait for Fite 1, 03 is Wait for continuity, 04 is Wait for clearing, 05 is Wait for answer, and 06 is Answered. Transitions are shown as arrows between states, with state 04 being a central node in a loop.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +``` + + graph LR + 00((00)) --> 01((01)) + 01 --> 02((02)) + 02 --> 03((03)) + 03 --> 04((04)) + 04 --> 05((05)) + 05 --> 06((06)) + 06 --> 04 + 04 --> 01 + 01 --> 00 + +``` + +State overview diagram for outgoing INMARSAT Standard A signalling system. It shows a sequence of states 00 to 06 with transitions between them. State 00 is Idle, 01 is Wait for CPCI Fite, 02 is Wait for Fite 1, 03 is Wait for continuity, 04 is Wait for clearing, 05 is Wait for answer, and 06 is Answered. Transitions are shown as arrows between states, with state 04 being a central node in a loop. + +CCITT-59 720 + +| State number | State description | Sheet reference | +|---------------------|--------------------------|------------------------| +| 00 | Idle | 1 | +| 01 | Wait for CPCI Fite | 1 | +| 02 | Wait for Fite 1 | 1 | +| 03 | Wait for continuity | 1 | +| 04 | Wait for clearing | 1 | +| 05 | Wait for answer | 1 | +| 06 | Answered | 1 | + +FIGURE C-1/Q.1101 + +**State overview diagram for outgoing INMARSAT Standard A signalling system** + +FIGURE C-2/Q.1101 + +(Reserved for future notes) + +![Flowchart of Outgoing INMARSAT Standard A signalling system. The process starts at IDLE (00), proceeds to ACTIVATE O/G INMARSAT, then WAIT FOR CPCI FITE (01). It then branches based on FITE signals (17, 18, 19, 22). If FITE 22 is received, it returns to IDLE (00). If FITE 17, 18, or 19 is received, it proceeds to WAIT FOR FITE 1 (02). From there, it checks for LAST DIGIT. If NO, it loops back to WAIT FOR FITE 1. If YES, it checks if SHIP BARRED. If YES, it sends BITE 20. If NO, it checks if SHIP BUSY. If YES, it sends BITE 16. If NO, it proceeds to SET-UP SATELLITE CHANNEL (part of the signalling procedure). Then it enters WAIT FOR CONTINUITY (03). From here, it branches based on signals: CONTINUITY (leads to BITE 5, then SPITE 6 CONNECT RINGING TONE), SHIP BUSY (leads to BITE 16), CONGESTION (leads to BITE 12), SHIP ABSENT (leads to BITE 20), CONTINUITY FAILURE (leads to BITE 17), or FITE 22 (leads to CLEAR-FORWARD). All these lead to a clearing procedure (CLEAR SATELLITE CHANNEL, WAIT FOR CLEARING (04), CHANNEL RELEASED, IDLE (00)). CONTINUITY leads to SPITE 6 CONNECT RINGING TONE, then WAIT FOR ANSWER (05). From WAIT FOR ANSWER, it branches to ANSWER (leads to SPITE 7 DISCONNECT RINGING TONE, then BITE 22, then connector 1) or FITE 22 (leads to connector 2). Connector 1 also leads to connector 2. Connector 2 leads to FITE 22 (part of the ANSWERED (06) sequence). The ANSWERED (06) sequence includes FITE 22 (leading to connector 2), CLEAR-BACK (leading to BITE 25, then connector 3), and connector 1.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph TD + IDLE00_1((00 IDLE)) --> ACTIVATE[ACTIVATE O/G INMARSAT] + ACTIVATE --> WAIT01((01 WAIT FOR CPCI FITE)) + WAIT01 --> FITE171819{FITE 17, 18, 19} + FITE171819 --> WAIT02((02 WAIT FOR FITE 1)) + FITE171819 --> FITE22_1{FITE 22} + FITE22_1 --> IDLE00_2((00 IDLE)) + WAIT02 --> LASTDIGIT{LAST DIGIT} + LASTDIGIT -- NO --> WAIT02 + LASTDIGIT -- YES --> SHIPBARRED{IS SHIP BARRED} + SHIPBARRED -- YES --> BITE20_1{BITE 20} + SHIPBARRED -- NO --> SHIPBUSY{IS SHIP BUSY} + SHIPBUSY -- YES --> BITE16_1{BITE 16} + SHIPBUSY -- NO --> SETUP[SET-UP SATELLITE CHANNEL] + SETUP --> WAIT03((03 WAIT FOR CONTINUITY)) + WAIT03 --> CONTINUITY{CONTINUITY} + WAIT03 --> SHIPBUSY_2{SHIP BUSY} + WAIT03 --> CONGESTION{CONGESTION} + WAIT03 --> SHIPABSENT{SHIP ABSENT} + WAIT03 --> CONTINUITYFAILURE{CONTINUITY FAILURE} + WAIT03 --> FITE22_2{FITE 22} + CONTINUITY --> BITE5{BITE 5} + BITE5 --> SPITE6[SPITE 6 CONNECT RINGING TONE] + SPITE6 --> WAIT05((05 WAIT FOR ANSWER)) + WAIT05 --> ANSWER{ANSWER} + ANSWER --> SPITE7[SPITE 7 DISCONNECT RINGING TONE] + SPITE7 --> BITE22{BITE 22} + BITE22 --> C1_1((1)) + SHIPBUSY_2 --> BITE16_2{BITE 16} + CONGESTION --> BITE12{BITE 12} + SHIPABSENT --> BITE20_2{BITE 20} + CONTINUITYFAILURE --> BITE17{BITE 17} + FITE22_2 --> CLEARFORWARD{CLEAR-FORWARD} + BITE16_2 --> CLEARPROC[Clearing procedure defined within the INMARSAT system] + BITE12 --> CLEARPROC + BITE20_2 --> CLEARPROC + BITE17 --> CLEARPROC + CLEARFORWARD --> C3_1((3)) + CLEARPROC --> CLEARCHAN[CLEAR SATELLITE CHANNEL] + CLEARCHAN --> WAIT04((04 WAIT FOR CLEARING)) + WAIT04 --> CHANNELREL[CHANNEL RELEASED] + CHANNELREL --> IDLE00_3((00 IDLE)) + FITE22_2 --> FITE22_3{FITE 22} + FITE22_3 --> C2_1((2)) + FITE22_3 --> CLEARBACK{CLEAR-BACK} + CLEARBACK --> BITE25{BITE 25} + BITE25 --> C3_2((3)) + C1_1 --> C2_2((2)) + C2_2 --> ANSWERED((06 ANSWERED)) + ANSWERED --> FITE22_4{FITE 22} + FITE22_4 --> C2_3((2)) + ANSWERED --> CLEARBACK_2{CLEAR-BACK} + CLEARBACK_2 --> BITE25_2{BITE 25} + BITE25_2 --> C3_3((3)) + C1_1 --> C1_2((1)) + +``` + +Flowchart of Outgoing INMARSAT Standard A signalling system. The process starts at IDLE (00), proceeds to ACTIVATE O/G INMARSAT, then WAIT FOR CPCI FITE (01). It then branches based on FITE signals (17, 18, 19, 22). If FITE 22 is received, it returns to IDLE (00). If FITE 17, 18, or 19 is received, it proceeds to WAIT FOR FITE 1 (02). From there, it checks for LAST DIGIT. If NO, it loops back to WAIT FOR FITE 1. If YES, it checks if SHIP BARRED. If YES, it sends BITE 20. If NO, it checks if SHIP BUSY. If YES, it sends BITE 16. If NO, it proceeds to SET-UP SATELLITE CHANNEL (part of the signalling procedure). Then it enters WAIT FOR CONTINUITY (03). From here, it branches based on signals: CONTINUITY (leads to BITE 5, then SPITE 6 CONNECT RINGING TONE), SHIP BUSY (leads to BITE 16), CONGESTION (leads to BITE 12), SHIP ABSENT (leads to BITE 20), CONTINUITY FAILURE (leads to BITE 17), or FITE 22 (leads to CLEAR-FORWARD). All these lead to a clearing procedure (CLEAR SATELLITE CHANNEL, WAIT FOR CLEARING (04), CHANNEL RELEASED, IDLE (00)). CONTINUITY leads to SPITE 6 CONNECT RINGING TONE, then WAIT FOR ANSWER (05). From WAIT FOR ANSWER, it branches to ANSWER (leads to SPITE 7 DISCONNECT RINGING TONE, then BITE 22, then connector 1) or FITE 22 (leads to connector 2). Connector 1 also leads to connector 2. Connector 2 leads to FITE 22 (part of the ANSWERED (06) sequence). The ANSWERED (06) sequence includes FITE 22 (leading to connector 2), CLEAR-BACK (leading to BITE 25, then connector 3), and connector 1. + +FIGURE C-3/Q.1101 + +Outgoing INMARSAT Standard A signalling system + +## References + +- [1] Radio Regulations (Article 1, No. 71), ITU, Geneva, 1982. +- [2] *Ibid.*, (Article 1, No. 73). \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5bd1715b3a587fc50847d304004966466f21fed --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50a606405f6e113c99bc45a761e9826662fb99db9219576e7043fc02933a015c +size 8297 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/47e8c2042061e08a14e012472e9fdbaa_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/47e8c2042061e08a14e012472e9fdbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74c5815ae5e900b7658e1ce0a6b181fbe21c1826 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/47e8c2042061e08a14e012472e9fdbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bec64f2efe579cd58c2caf77f51b36ca3e207cfcdac3f8c8b3015ea41d7cf67 +size 13701 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d887aaec3caa86828e98f4de3bab40accb34efbe --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a715085b0df030d725b5dd3dbac459f63938383db741301d2b45fe7ff16b6d79 +size 50561 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2d9bb6074cee61a9b74b52839560d7471c0ce7f --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59e19fae4151698dd9ee922f35d10948d26b8049d4e126ca82f28defbb70ceda +size 18323 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a4d76863de77e7ac95a90a05f1fbb3525e72927 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f057ecb4908d7db85b25b0d82bc3f13418d17156e7d22f60fc3a1f9fbd44d938 +size 42835 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1e8042a8b63c290ed3e5c1ccbff79091ed4756a --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:242bb7d8145da9c208b58871da2632c443dfb4003419d672196b14fedde3c66d +size 68045 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97a5be4e8eae55a333272ee4d0d67b4a17d220d0 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c220e3519c49ed4a4630701f700d3b0b0f8dcab8515e15f52767eefc5294c1a0 +size 54023 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..349c72d5b4be9072152e0117bf88702126c106e9 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb48ecd000a69b3f13f42e7038e8f85a9494598b33e2ea97de4cbc1d49d0ff61 +size 51034 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..182c8975b61093daca72cafbdef8343c4c104fb5 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0f4d30caaf2ae8c46a9e826a7811b358986778056bc08e2cfe585d628963cf8 +size 56084 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75a919297877dae56b729b25e81261f413bd9590 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6298948c425daa4f682977759444499b6bd78a557baeba3486f6bb3de2c34ca +size 50354 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3917f25066d2f30ea8409331bba1ae36048f48ac --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d8a9c30db75156b4550a9de816472fc2b2d29764a762353775ecc10f042607f +size 61081 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59e1ee51847d387df143ad4b80dd7a9b4ec47b80 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5907248d88a7c059f51a7e3770ba5cd5a8eff9d30b1b7f47c8d7d8526fc16f2e +size 65945 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d16358da6ea959e90646f604cb8f3fad23a9c3e --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b03a4a068ba440f0a3b42973b07660783d15252b92e57571751e1726a64f570 +size 53084 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f13a74977a3f0f425be70f368ab0aaef57cbc877 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3333d3970a207aef9ad0765bcc0760fa2607fd716c883fd4893a894b621c6283 +size 47401 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f5a7d3da2adbafed2ae45334aa94705f0384579 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62af433cb17578130821e368aea237f3ff7d434277b13687bd41f56349c5c4bb +size 21566 diff --git a/marked/Q/T-REC-Q.1151-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..84f1a7ef220fee251904838d8073a4903af59636 --- /dev/null +++ b/marked/Q/T-REC-Q.1151-199303-I_PDF-E/raw.md @@ -0,0 +1,873 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1151** + +(03/93) + +**INTERWORKING WITH SATELLITE +MOBILE SYSTEMS** + +--- + +**INTERFACES FOR INTERWORKING +BETWEEN THE INMARSAT AERONAUTICAL +MOBILE-SATELLITE SYSTEM AND +THE INTERNATIONAL PUBLIC SWITCHED +TELEPHONE NETWORK/ISDN** + +**ITU-T Recommendation Q.1151** + +(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.1151 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 | Service capabilities..... | 1 | +| 2.1 | Channel capabilities..... | 1 | +| 2.2 | Bearer capabilities..... | 2 | +| 2.3 | Teleservices ..... | 2 | +| 3 | Interworking scenarios ..... | 2 | +| 4 | Connection interface requirements..... | 4 | +| 4.1 | General..... | 4 | +| 4.2 | MSSC-network interface ..... | 4 | +| 4.3 | AES-MSSC interface..... | 4 | +| 4.4 | Calling procedures air-to-ground..... | 4 | +| 4.5 | Calling procedures, ground-to-air..... | 5 | +| 5 | Routing requirements ..... | 5 | +| 5.1 | Ground originated calls..... | 5 | +| 5.2 | Aircraft originated calls ..... | 5 | +| Appendix I | – INMARSAT aeronautical mobile-satellite system description ..... | 5 | +| I.1 | Introduction ..... | 5 | +| I.2 | System evolution ..... | 7 | +| I.3 | Channel configuration ..... | 9 | +| I.4 | Link layer formats and protocols ..... | 10 | +| I.5 | Aircraft earth station management..... | 11 | +| I.6 | Telephone services..... | 11 | + + + +# **INTERFACES FOR INTERWORKING BETWEEN THE INMARSAT AERONAUTICAL MOBILE-SATELLITE SYSTEM AND THE INTERNATIONAL PUBLIC SWITCHED TELEPHONE NETWORK/ISDN** + +*(Melbourne 1988, modified at Helsinki, 1993)* + +## **1 General** + +**1.1** This Recommendation provides information on the services offered in the INMARSAT aeronautical mobile-satellite system and describes the requirements for connection to and interworking with the public networks. Special terminology for this Recommendation is defined in Recommendation Q.1100. Detailed interworking procedures are set out in Recommendation Q.1152. + +**1.2** As well as connection to public networks, the aeronautical system is required to be able to interwork with existing specialized private networks. In implementing all interworking cases, regard should be paid to the open systems interconnection referenced model (X.200-Series Recommendations) and to ISDN services and signalling methods (I-Series Recommendations), with a view to achieving uniformity in user procedures and formats and to achieving generally applicable facilities. + +**1.3** Within the constraint of the need to operate as economically as possible, the preferred interworking cases are with the ISDN and with those parts of the international telephone network employing common channel signalling. If one of these is not available or accessible at the ISC to which an aeronautical ground earth station (GES) is connected then another signalling system from the Q-Series Recommendations should be used. + +**1.4** The use of the ISDN will offer both improvement in quality and more flexibility in service. It will be possible to supply either voice or data over the same network with the ability to change from one to the other under control of the aircraft earth station (AES) terminal. + +## **2 Service capabilities** + +A general description of the INMARSAT aeronautical system is contained in Appendix I. + +### **2.1 Channel capabilities** + +**2.1.1** The system provides circuit-mode single channel per carrier (SCPC) channels at a range of information bit rates, including at least the following: + +9600 bit/s; 4800 bit/s; 2400 bit/s + +Channels for other information bit rates, such as 64 000 bit/s, may be defined in the future. + +**2.1.2** The system provides demand assigned forward (ground to air) TDM channels and return (air to ground) random access and (reservation) TDMA channels, at a range of bit rates. Although the following bit rates include housekeeping overheads, they are indicative of the information bit rates provided: + +300 bit/s; 600 bit/s; 1200 bit/s; 2400 bit/s; 5250 bit/s. + +Channels for other bit rates may be defined in the future. + +### 2.2 Bearer capabilities + +2.2.1 The following bearer services on SCPC channels, with the following information transfer attributes as defined in Recommendation I.211, may be supported: + +- speech (initially at 9.6 kbit/s); transcoding to 64 kbit/s PCM should take place at the GES; +- circuit mode audio service (initially at 9.6 kbit/s), suitable for voice and other signals occupying the same bandwidth; transcoding to 64 kbit/s PCM should take place at the GES; +- virtual call bearer service at any of the bit rates defined in 2.1.1, with rate adaptation in the GES to 64 kbit/s using, for example, flow control and flag stuffing; +- digital data, circuit mode interworking with the ISDN should take place as defined in Recommendation X.30 for data terminals designed to Recommendation X.21, and Recommendation X.32 for data terminals designed to Recommendation X.25. + +2.2.2 The following bearer services on TDM, TDMA and RA channels may be supported: + +- virtual call bearer service – interworking with the ISDN should take place as defined for interworking between PSPDNs and the ISDN. + +### 2.3 Teleservices + +Teleservices, when supported, should be in accordance with Recommendation I.212. It is to be observed that not all teleservices of ISDN may be supported with bearer services that can be provided on SCPC or TDM/TDMA channels operating at the available information bit rates. + +## 3 Interworking scenarios + +Three interworking scenarios can be envisaged for the interface between the MSSC and the fixed networks. + +3.1 The first scenario is shown in Figure 1. The MSSC public network interface is to the PSTN only, with all data services, and some voice services, handled via private networks. + +![Diagram of interworking scenario with PSTN interface. It shows a box labeled 'AES' connected to a box labeled 'GES' which is connected to a box labeled 'MSSC'. The 'MSSC' box is connected to a circle labeled 'PSTN' and a dashed line connects it to a circle labeled 'Private network'. Below the diagram is the text 'T1 155860-93/d01'.](47e8c2042061e08a14e012472e9fdbaa_img.jpg) + +``` +graph LR; AES[AES] --- GES[GES]; GES --- MSSC[MSSC]; MSSC --- PSTN((PSTN)); MSSC -.- PrivateNetwork((Private network)); +``` + +T1 155860-93/d01 + +Diagram of interworking scenario with PSTN interface. It shows a box labeled 'AES' connected to a box labeled 'GES' which is connected to a box labeled 'MSSC'. The 'MSSC' box is connected to a circle labeled 'PSTN' and a dashed line connects it to a circle labeled 'Private network'. Below the diagram is the text 'T1 155860-93/d01'. + +FIGURE 1/Q.1151 +**Interworking scenario with PSTN interface** + +3.2 Figure 2 shows the situation where an ISDN exists and the MSSC has an interface to it. Interworking with the PSTN is achieved via the ISDN. Interworking with PDNs may be by direct interface with the PDN or via the ISDN, as in the case of the PSTN. + +![Diagram of interim interworking scenario with interfaces to ISDN and other fixed networks. It shows an AES connected to a GES, which is connected to an MSSC. The MSSC is connected to a PDN, which is connected to a PSTN. The MSSC is also connected to an ISDN. A Private network is shown with dashed lines connecting it to the MSSC, PDN, and ISDN.](fc46871d72c65d3381d9201646d23439_img.jpg) + +``` + +graph LR + AES[AES] --- GES_MSSC[GES | MSSC] + GES_MSSC --- PDN((PDN)) + GES_MSSC --- ISDN((ISDN)) + PDN --- PSTN((PSTN)) + GES_MSSC -.-> PN((Private network)) + PDN -.-> PN + ISDN -.-> PN + +``` + +T1155870-93/d02 + +Diagram of interim interworking scenario with interfaces to ISDN and other fixed networks. It shows an AES connected to a GES, which is connected to an MSSC. The MSSC is connected to a PDN, which is connected to a PSTN. The MSSC is also connected to an ISDN. A Private network is shown with dashed lines connecting it to the MSSC, PDN, and ISDN. + +FIGURE 2/Q.1151 +**Interim interworking scenario with interfaces +to ISDN and other fixed networks** + +In this scenario interworking with the ISDN supports speech, 3.1 kHz audio and data services as indicated in 2.2.1. Other bearer services as indicated in 2.2.2 may require interworking with PDNs. + +**3.3** The third scenario is shown in Figure 3. The MSSC interfaces to the ISDN, which provide data services as well as voice, although some voice and data services may still use private networks. + +![Diagram of interworking scenario with ISDN interface only. It shows an AES connected to a GES, which is connected to an MSSC. The MSSC is connected to an ISDN, which then connects to a PDN and a PSTN. A Private network is shown with dashed lines connecting it to the MSSC and ISDN.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +``` + +graph LR + AES[AES] --- GES_MSSC[GES | MSSC] + GES_MSSC --- ISDN((ISDN)) + ISDN --- PDN((PDN)) + ISDN --- PSTN((PSTN)) + GES_MSSC -.-> PN((Private network)) + ISDN -.-> PN + +``` + +T1155880-93/d03 + +Diagram of interworking scenario with ISDN interface only. It shows an AES connected to a GES, which is connected to an MSSC. The MSSC is connected to an ISDN, which then connects to a PDN and a PSTN. A Private network is shown with dashed lines connecting it to the MSSC and ISDN. + +FIGURE 3/Q.1151 +**Interworking scenario with ISDN interface only** + +# 4 Connection interface requirements + +### 4.1 General + +This subclause identifies the information that must be available at the interfaces between the AES and the MSSC and between the MSSC and the fixed network, principally for the connection of services identified in 3. + +### 4.2 MSSC-network interface + +For ISDN connections ISUP should be used for message transfer. For non-ISDN or where ISUP is not available, TUP would be preferred. + +If information transport between MSSCs over the fixed network is required, it is suggested that the procedures of the SCCP is used. Detailed interworking procedures are defined in Recommendation Q.1152. + +### 4.3 AES-MSSC interface + +Prior to and during call initiation the signalling channel functions may be provided by one or more common control channels. + +A signalling capability should always be available during conversation in case it is needed for call clearing, call control, or for call management purposes. During a call the signalling channel may be multiplexed with the traffic channel at a lower bit rate so as to conserve radio channel capacity. + +The multiplexed signalling channel or TDM/TDMA/RA channels may be used for bearer services such as connectionless data services, or connection oriented data services not requiring the establishment of a traffic channel. + +The traffic channel should be used for bearer services such as: + +- speech; +- circuit mode data services; +- packet mode data services; +- voice band data services. + +### 4.4 Calling procedures air-to-ground + +#### 4.4.1 Passenger telephony operation + +- a) The equipment for passenger telephony may consist of the following: + - the AES; + - cabin telephone equipment consisting of a fixed piece of equipment and a handset, which may be “cordless”. + +The fixed cabin telephone equipment should be provided with a credit card reader. + +- b) When a passenger wants to make a call, the typical sequence of events would be as follows: + - i) key-in seat number; + - ii) when this is accepted, insert credit card; and + - iii) when this is accepted, remove handset and return to seat. +- c) At the cabin telephone location, if a credit card which corresponds to the recognized card format is inserted into the equipment, the handset shall be released after validation of the check bits and expiry date. In the event that either of these checks fail, the card shall be returned and the handset not released. Upon obtaining the handset the customer returns to his seat and can commence making one or more telephone calls. +- d) Where telephones and associated credit card readers are located at the passengers' seats, a somewhat different procedure may apply. However, the procedure will still involve reading the credit card, validating the check bits and checking expiry date, before making calls. + +#### **4.4.2 Crew telephony operation** + +For this case, credit card validation procedures are not required. Crew will have access to special telephone services and networks, according to requirements and procedures developed by the industry. The capabilities will include at least the following: + +- a) access to the full public telephone network as for passengers, but without the need for a credit card (billing would be direct to the aircraft operator); +- b) access to specialized voice services via private networks, with or without address digits; +- c) ability to preempt an existing (passenger) call if necessary to make AES voice circuit equipment, a satellite channel or GES voice circuit equipment available; +- d) ability to seize the next available AES voice circuit equipment, but without clearing any calls in progress. + +### **4.5 Calling procedures, ground-to-air** + +**4.5.1** Selected fixed network users should be able to access aircraft automatically by using the aircraft ID in the address digits. Operator connected access may also be available. + +**4.5.2** The numbering plan to enable a PSTN subscriber to call the AES is defined in Recommendation E.215. + +## **5 Routing requirements** + +### **5.1 Ground originated calls** + +The country code 87S should be analysed at all transit centres where the call may either be routed on a circuit containing a satellite link or on a circuit not containing a satellite link. The latter circuit should always be chosen (see Recommendation Q.14). + +### **5.2 Aircraft originated calls** + +If the signalling system provided between the MSSC and the terrestrial network contains signals which may be used to indicate that one satellite link is included, such signals should be used. + +If the signalling system does not contain such signals, the outgoing ISC should avoid forwarding the call on an outgoing circuit which includes a satellite link. If, however, the signalling system employed between the outgoing ISC and the next ISC in the connection contains such signals, the outgoing ISC should insert the required information. The outgoing ISC could base its procedure upon incoming route identification. + +# **Appendix I** + +## **INMARSAT aeronautical mobile-satellite system description** + +(This appendix does not form an integral part of this Recommendation) + +## **I.1 Introduction** + +The aeronautical satellite system is a mobile communications system intended for use by aircraft in flight. It can provide voice communication services and a range of data communications services. + +**I.1.1** The major elements of the aeronautical satellite system as described in this appendix are as follows (see also Figure I.1): + +- a) space segment, in particular the satellite communication transponders and associated frequency bands assigned for use by the aeronautical satellite system; +- b) aircraft earth stations (AES) which are in accordance with the relevant technical requirements, and which interface with the space segment at L-band for communications with ground earth stations, and which interface in the aircraft with data equipment and with crew and passenger voice equipment; +- c) aeronautical (ground) earth stations (GES) which interface with the space segment (at C-band and L-band) and with the fixed networks, and which are operated in accordance with the relevant technical and operational requirements for communications with AESs; for the “Initial System” GESs will operate to their own essentially independent networks; and +- d) network coordination stations (NCS) located at designated earth stations, for the purpose of allocating satellite channels, and also for system control and monitoring; NCSs are planned to be introduced at a later stage as part of the “Enhanced System”. + +**I.1.2** The aeronautical system is made up of independent communication networks for each satellite ocean area, each network comprising the operational satellite and associated ground control facilities, the AESs and GESs operating within that area, and an NCS. The system design permits GESs to establish communications on a stand-alone basis with AESs without the intervention of the NCS, except in cases of satellite channel shortage. + +**I.1.3** Each AES is equipped with a capability to receive a medium rate forward channel transmitted from a GES with a transmission rate of 600 bit/s carrying signalling and data messages in packet form. + +**I.1.4** Each AES is equipped to transmit a return carrier in burst mode at a transmission rate of either 600 bit/s or 1200 bit/s controlled by signalling messages received via the forward 600 bit/s channel. This dual capability is required to enable some advantage of the variations in aircraft antenna pattern and in spacecraft receiver sensitivity, which will be encountered during a flight, to be taken. + +**I.1.5** AESs may also be equipped with pairs of transmit/receive voice channel equipment and data channel equipment for higher bit rates. + +**I.1.6** Each GES is equipped with at least the following data-only transmission capabilities: + +- a) one 600 bit/s transmitter for the forward channel; +- b) four 600 bit/s receivers for the slotted random access channels (this is the minimum to be provided for diversity protection against interference, and burst re-collisions); and +- c) a receiver for its 600 bit/s forward channel and for the forward channels of each other GES working to the same satellite. + +**I.1.7** At the GES owner's option, GESs may also be equipped with: + +- a) pairs of transmit/receive voice channel equipment; +- b) 600 bit/s receiver(s) for a Reservation TDMA channel(s), or 600 bit/s and 1200 bit/s receiver(s) for Reservation TDMA channel(s); and +- c) additional data channel equipment for the same or higher bit rates. + +**I.1.8** The system provides for voice communications by means of the voice channels. Signalling and user data communications is carried on the medium rate (600/1200 bit/s) data channels. This signalling and user data is formatted into fixed length signal units of either 96 bits (12 octets) or 152 bits (19 octets), which are combined as necessary to support various message sizes according to user requirements. + +## **I.2 System evolution** + +### **I.2.1 General** + +**I.2.1.1** The capabilities of the system will evolve with time, due to the progressive development of each of the four major elements identified in I.1.1 above, i.e. space segment, AES, GES and NCS. Although some of the evolutionary steps of one element are inevitably linked with those of other elements, in general the system concept is to allow the individual elements to evolve independently. The pressures which are expected to lead to this evolution include traffic growth, market awareness, new applications and new technology. + +**I.2.1.2** The use of narrow-band channels (generally single channel per carrier) and software programmable channel units (modems, etc.) are the principal requirements to achieve the required flexibility, to efficiently utilize a variety of satellite parameters, take advantage of future advances in voice coding technology, allow the aircraft installation to match the services required, and provide a smooth growth path from an initial start-up system through increasing levels of traffic. + +### **I.2.2 Space segment evolution** + +**I.2.2.1** Within the aeronautical system operational timeframe, it is anticipated that the satellite types of INMARSAT's first generation space segment still in service will comprise MARECS (leased from the European Space Agency) and INTELSAT-V MCS satellites (Maritime Communications Sub-System, leased from the International Telecommunications Satellite Organization). Satellite tracking, telecommand, telemetry and ranging services are included in the leasing arrangements with ESA and INTELSAT, with TT&C stations linked to satellite control centres (SCCs) at Darmstadt (Germany) and Washington DC, respectively. The SCCs are in turn linked to the INMARSAT Operations Control Centre (OCC) in London. + +**I.2.2.2** The aeronautical system will also operate with and take advantage of the improved performance of the (second generation) INMARSAT-2 satellites, now on order. + +### **I.2.3 AES evolution** + +**I.2.3.1** Two types of aircraft antenna are defined, one with a minimum gain of 0 dBi over its coverage area, the other with a minimum gain of 12 dBi over its coverage area. In the initial system, AESs with the 0 dBi antenna are limited to medium rate data services (see I.2.4.2), while AESs with the 12 dBi antenna can obtain multi-channel voice service as well as data services at higher bit rates. + +**I.2.3.2** Irrespective of the antenna gain, each AES is required to be equipped with a bit rate switchable data channel unit. The minimum capability is to provide for both 600 bit/s and 1200 bit/s transmission rates (300 bit/s and 600 bit/s information rate, less overheads) and this will suffice for the initial two or three years. Additional, higher bit rates will be needed in the future and these could be provided for in the initial AES design, or be achieved by a software upgrade in a programmable channel unit, or by replacement of a plug-in card. + +**I.2.3.3** In operation, the bit rate in use by the AES for data services is determined by signalling from the ground. When commencing service with a given GES, an AES goes through a "log-on" procedure, using the 600 bit/s transmission rate channels assigned for system management (and possibly other) functions. In this log-on procedure, the AES gives its class of equipment provision, and the GES measures the signal level received from the AES if needed, to determine whether a higher bit rate could be supported. From this information the GES assigns working channels for further signalling and data transactions with the AES. + +**I.2.3.4** Since the other elements of the system will evolve with time, the AES capabilities have been defined in a way which provides adequate service levels in the start-up phases, but which can take advantage of improved performance in the other elements as they become available, without requiring any significant replacement or upgrade of components. Specifically, the AES is specified with a linear high power amplifier (HPA) with a power output of 40 Watts, and a family of digital channels is defined which are all mutually consistent and compatible. + +This makes it feasible to use a single programmable channel unit [using digital signal processor (DSP) microprocessor chips] to implement a suitable selection of channel types from the family, and allow for additional or alternative channel types in the future if required, by software upgrade. The linear characteristic of the HPA permits matching the evolution + +of space segment characteristics, providing progressively greater numbers of voice channels with higher performance spacecraft, and also allowing the separation of services in different GESs if required in the future [such as dedicated GESs for air traffic services (ATS)]. + +**I.2.3.5** It may be anticipated that the service requirements and technology applied to them on aircraft will develop independently of satellite communications. Examples of this type of development are data applications such as for monitoring of equipment health, and the progressive reduction of digital bit rate needed to provide voice service of a given quality. This system makes specific provision for evolution in voice coding, and by adopting a layered approach, along the lines defined in the Open System Interconnection (OSI) model, facilitates its use for as yet unforeseen data applications. In addition, there is ample provision of spare codes in the critical signalling fields, so that if enhancements become necessary they can be implemented by software upgrades. + +**I.2.3.6** Although the AES is specified to use a linear HPA, the offset QPSK modulation method is used in the higher bit rate channels in order to make operation with a hard limiting linear (e.g. Class C) HPA feasible. This will permit the development of single-channel AES equipment suitable for general aviation aircraft, when a demand develops. + +### **I.2.4 GES evolution** + +**I.2.4.1** The aeronautical GES has been defined so it can be produced as a compatible add-on to an existing standard coast earth station in the INMARSAT system. While this type of sharing is not essential, it may enable some economies to be achieved particularly in the start-up phase of the system, and where both services are carried by the same satellite. + +**I.2.4.2** As new satellites become available and traffic grows, the data transmission bit rates which can be supported, and need to be supported, will increase. To achieve this, additional data channel units, and/or higher bit rate channel units, will need to be provided at the GESs. The system can operate exclusively with data channel bit rates of 600 bit/s, and this may be sufficient in the initial stage. However, higher bit rates in the return direction (air-to-ground) can be supported even from a 0 dBi antenna, except at edge of coverage with existing (first generation) spacecraft, and will be able to be supported globally with INMARSAT-2 satellites. Thus the provision of higher bit rate channel units by the late 1980s will be appropriate, to provide for growing traffic and to minimize data service message delays. Depending on demand, it may also be appropriate to provide data channel units for interworking with aircraft fitted with 12 dBi antennas. Since all the channels form a compatible family, the possibility exists of using a common hardware unit for all these channels, differing only in software. + +**I.2.4.3** To take advantage of evolution in voice coding technology, it may be anticipated that a point will be reached when the voice coding rate and algorithm used in the initial system will be considered inappropriate, at least for new aircraft installations. A decision to adopt new voice coding rate will be practicable, the main requirement being that GESs wishing to interwork with all aircraft will need to operate two sets of channel units and associated voice codecs. As for data, the channel unit hardware could be common, although the voice codecs may be of different designs. + +### **I.2.5 NCS evolution** + +**I.2.5.1** The function of the NCS is to manage a common pool of satellite voice channels, and to assign them on demand to individual GESs for the duration of one call. In a system with small capacity and multiple GESs the random distribution of traffic across GESs necessitates the provision of a common pool managed by an NCS, for efficiency reasons. When traffic is low in the initial start-up phase, operation with only individual pools of channels at each GES will be satisfactory, but as additional GESs come into service the NCS will become essential. + +**I.2.5.2** In the initial system operating without an NCS, communication between GESs is still required to allow aircraft to call or be called via more than one GES. This communication is achieved by using a forward channel from each GES; the channel could be the one also designated for system management functions, or a separate, lower powered channel. In any case the implementation should be arranged so as to facilitate a changeover to a separate interstation link and the provision of an NCS, in the long term. + +## I.3 Channel configuration + +### I.3.1 General + +**I.3.1.1** The basic transmission characteristics of the family of aeronautical system channels are given in Table I.1. The channel bit rates have been selected to facilitate their implementation using a single programmable channel unit and to provide future flexibility. While this may not be practicable now for the highest bit rates in the table, future implementations may be able to take advantage of this structure. + +TABLE I.1/Q.1151 + +#### Channel transmission characteristics summary + +| Bearer rate (bit/s) | Channel rate (bit/s) | Channel spacing (kHz) | Modulation | +|---------------------|----------------------|-----------------------|------------| +| 9600 | 21 000 | 17.5 | O-QPSK | +| 9600 | 10 500 | 10.0 | O-QPSK | +| 5250 a) | 10 500 | 10.0 | O-QPSK | +| 4800 | 5 250 | 5.0 | O-QPSK | +| 2400 | 6 000 | 5.0 | O-QPSK | +| 2400 a) | 4 800 | 5.0 | O-QPSK | +| 1200 a) | 2 400 | 5.0 | DECPSK | +| 600 a) | 1 200 | 5.0 | DECPSK | +| 300 a) | 600 | 5.0 | DECPSK | + +a) Less overheads. + +### I.3.2 Channel naming + +In order to simplify references to the various channel formats included in the system, each individual format has been assigned a designation as follows (see also Figure I.1): + +#### a) *P-Channel* + +Packet mode time division multiplex (TDM) channel, used in the forward direction (ground-to-air) to carry signalling and user data; the transmission is continuous from one GES; a P-channel being used for system management functions is designated Psmc, while a P-channel being used for other functions is designated Pd; + +#### b) *R-Channel* + +Random access (slotted ALOHA) channel, used in the return direction (aircraft-to-ground) to carry some signalling and user data, specifically the initial signals of a transaction, typically request signals; an R-channel being used for system management functions is designated Rsmc, while an R-channel being used for other functions is designated Rd; + +#### c) *T-Channel* + +Reservation Time Division Multiple Access channel, used in the return direction only; the receiving GES reserves time slots for transmissions requested by AESs, according to message lengths and priority; + +#### d) *C-Channel* + +Circuit-mode single channel per carrier (SCPC) voice/data channel, used in both forward and return directions; the use of the channel is controlled by assignment and release signalling at the start and end of each call. + +![Diagram of Aeronautical network configuration showing data flow between Communications terminals, Aircraft earth station (AES), Aeronautical Ground earth station (GES), and Terrestrial networks. It details P, R, T, and C channels with their respective signaling and data rates.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph LR + CT[Communications terminals] <--> AES[Aircraft earth station - AES] + AES -- "P-Channel" --> GES[Aeronautical Ground earth station - GES] + AES -- "R-Channel" --> GES + AES -- "T-Channel" --> GES + AES <--> "C-Channel (Voice + data-high rate)" <--> GES + GES <--> TN[Terrestrial networks] + OtherGES[P-Channel(s) from other GES] --> GES + + subgraph "Signalling + data-medium rate" + P-Channel + R-Channel + T-Channel + end + +``` + +P-Channel Packet mode channel +R-Channel Slotted random access (ALOHA) channel +C-Channel Circuit mode channel +T-Channel Reservation TDMA channel + +Diagram of Aeronautical network configuration showing data flow between Communications terminals, Aircraft earth station (AES), Aeronautical Ground earth station (GES), and Terrestrial networks. It details P, R, T, and C channels with their respective signaling and data rates. + +FIGURE I.1/Q.1151 +**Aeronautical network configuration** + +### I.3.3 Forward error correction coding + +The majority of channel types use Forward Error Correction (FEC) coding consisting of a convolutional encoder of constraint length $k = 7$ and an 8-level soft decision Viterbi decoder; the FEC coding rate is either $3/4$ or $1/2$ ; the rate $3/4$ code is derived by puncturing the rate $1/2$ , $k = 7$ convolutional code. + +## I.4 Link layer formats and protocols + +#### I.4.1 General + +All signalling and user data messages are formatted into signal units of length either 96 bits (12 octets) or 152 bits (19 octets). The extended length signal units (19 octets) are only used on the R-channel, whereas the standard length signal units (12 octets) are used on all channels. + +More complex messages (including user data) can be carried by a sequence of several signal units. Longer messages generated in a user application will be broken into message fragments in the network layer, compatible with the maximum size, before being presented for transmission via the link layer; the use of these signal units applies to signalling and user data transactions on the sub-band channel of the voice/data channel as well as the P-, R- and T-channels. + +### I.4.2 Basic signal unit concepts + +**I.4.2.1** A message that can be accommodated in a single signal unit is formatted into a “Lone Signal Unit” (LSU). Longer messages are formatted into more than one signal unit, of which the first is an “Initial Signal Unit” (ISU) followed by one or more “Subsequent Signal Units” (SSU). + +**I.4.2.2** Each signal unit includes 16 check bits (the last two octets) for error detection, these being calculated from the preceding octets of the signal unit using the polynomial: $x^{16} + x^{12} + x^5 + 1$ for generation (see 2.2.7/X.25). The undetected error rate on the sub-band C-channel, under nominal worst case conditions is typically less than one in $10^{10}$ signal units. The undetected error rate on P- and R-channels is expected to be much less than this. + +**I.4.2.3** At the receiver for any channel, the check bits for each received signal unit are calculated, and if there is a mismatch with the received check bits the signal unit is discarded. Recovery from lost and corrupted signal units is handled either by a Reliable Link Service function, or by the relevant signalling logic procedures. + +## **I.5 Aircraft earth station management** + +**I.5.1** Every GES maintains an up-to-date status table of AESs which have logged into the GES, and has an inter-GES and GES-NCS signalling facility, so that every GES shall be able to set up calls to and from any AES operating to the same satellite, and to manage AESs in the handover process. + +**I.5.2** Every AES logs-on to a GES of its choice for entering into the Aeronautical system and logs-out as part of terminating its operation in the system. When an AES requires a change in its log-in GES, accessing satellite or accessing spot beam of a satellite, the AES follows a handover procedure resulting in a smooth transition. + +## **I.6 Telephone services** + +### **I.6.1 General** + +**I.6.1.1** Telephone services are provided using a pair of C-channels (one in each direction) assigned from a pool held by the GES, or by the NCS from a common pool. The function of the NCS is to make C-channel assignments in response to requests from GESs (when the latter runs out of frequencies) on a call-by-call basis. + +**I.6.1.2** In the ground-to-air direction, all telephone calls may go to a single answering point on the aircraft, or may be addressed to specific answering points. In the initial system at least, for commercial aircraft, access will be restricted to a very limited number of callers for operational and practical reasons. This restriction will be imposed in the GES, or elsewhere, at the discretion of the GES owner. + +**I.6.1.3** In the air-to-ground direction, calls may be made by crew or passengers, with several types of service provided. The primary service capabilities include: + +- a) passenger telephony; +- b) crew general telephony; and +- c) crew ATC voice. + +### **I.6.2 Call set-up/termination for air-to-ground calls** + +**I.6.2.1** The basic sequences for air-to-ground telephone call set-up are shown in Figures I.2 to I.5, covering various cases including use of an NCS. + +**I.6.2.2** From the point of view of the AES, all the cases are the same, with the AES receiving the called number (and in the case of passenger calls the credit card data) prior to starting the request process. An initial request is sent using the R-channel to the GES where the AES is logged in, and a channel assignment is received on the corresponding P-channel. The communications channel is then set up, tested using signals on the sub-band data channel, and the called party address (plus the credit card number if applicable) is transmitted via the sub-band data channel. + +**I.6.2.3** If the air-to-ground call is to the log-on GES (Figure I.2), then all the access request and channel assignment transactions are carried via the R- and P-channels only. However, if the call is to a GES other than the one where the AES logged-on (Figure I.3), then the log-on GES forwards the access request (from the AES) to the called GES (designated "other" GES in Figure I.3) over the interstation link. The called GES allots a channel, if available, from its pool and transmits the channel assignment information over the interstation link. The log-on GES then forwards the information to the AES over the P-channel. The corresponding signalling sequences for air-to-ground call set-up using the NCS are shown in Figures I.4 and I.5, the former representing the case of a call addressed to a log-on GES and the latter showing a call addressed to a GES other than the one where the AES has logged- on. + +In the former case (Figure I.4), the log-on GES, on receipt of an access request from the AES, sends a Request for Assignment message over the interstation link to the NCS, whereupon the NCS responds by sending a channel assignment to the requesting GES over the same interstation link. The GES sends this channel assignment to the AES over the P-channel. + +In the case of a call addressed to "other" GES, the procedure is similar to the above, with the addition of the log-on GES as an intermediary between the AES and "other" GES. After the call is cleared, the GES to which the channel is assigned by the NCS (i.e the "other" GES), sends the channel release information to the NCS over the interstation link. The transaction is completed by the NCS sending an acknowledgement to the GES. + +In the normal case, when the call is ended both parties will replace their handsets (abnormal cases are covered in Figure I-6 and Recommendation Q.1152). The on-hook condition of the telephone in the AES initiates a series of channel release signals on the sub-band C-channel. When one of these is received in the GES, it monitors the carrier to confirm that it stops. If the AES is logged-on to another GES, the channel release signal is sent to the log-on GES via the appropriate interstation link. + +![Sequence diagram showing the air-to-ground telephone call set-up sequence between a Ground Station (GES) and an Aircraft Station (AES).](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +``` + +sequenceDiagram + participant GES + participant AES + Note right of AES: Credit card data + Note right of AES: (User) Off-hook & number + Note right of AES: Access request + Note right of AES: Service address and credit card data (if applicable) + Note right of AES: (Continuous) + Note right of AES: Connect through + Note right of AES: Service address and credit card data stopped + Note right of AES: Acknowledge + + AES->>GES: Rd + GES->>AES: Pd + GES->>AES: C, sub-band + Note left of GES: C-channel assignment + Note left of GES: Test signal units (continuous) + Note left of GES: When call inform. complete, test signals stopped + Note left of GES: Call attempt result (address complete) + Note left of GES: Connect through + +``` + +The diagram illustrates the call set-up sequence between a Ground Station (GES) and an Aircraft Station (AES). The sequence begins with the AES sending 'Credit card data', '(User) Off-hook & number', and an 'Access request' to the GES. The GES responds with 'Rd' (Request data) and 'Pd' (Provide data). The GES then sends a 'C-channel assignment' and 'Test signal units (continuous)' on the 'C, sub-band'. The AES replies with 'Service address and credit card data (if applicable)'. The GES continues with 'C, sub-band' signals. Once the call information is complete, the test signals stop, and the GES sends a 'Call attempt result (address complete)'. The AES responds with '(Continuous)', 'Connect through', 'Service address and credit card data stopped', and an 'Acknowledge'. The GES completes the 'Connect through' phase. + +T1128290-90/d05 + +Rd See 1.3.2 +Pd See 1.3.2 + +Sequence diagram showing the air-to-ground telephone call set-up sequence between a Ground Station (GES) and an Aircraft Station (AES). + +FIGURE I.2/Q.1151 +Air-to-ground telephone call set-up sequence + +![Sequence diagram showing air-to-ground telephone call set-up sequence between 'Other' GES, Log-on GES, and AES. The sequence includes messages like Credit card data, (User) Off-hook & number, Access request, Rd, Interstation link, C-channel assignment, Pd, Service address and credit card data (if applicable) (continuous), and Test signal units (continuous).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant AES + participant Log-on GES + participant Other_GES as "Other" GES + + Note right of AES: Credit card data + Note right of AES: (User) Off-hook & number + AES->>Log-on GES: Access request + Log-on GES-->>AES: Rd + Log-on GES->>Other_GES: Interstation link + Other_GES-->>Log-on GES: C-channel assignment + Log-on GES-->>AES: Pd + AES->>Log-on GES: Service address and credit card data (if applicable) (continuous) + Log-on GES-->>Other_GES: C, sub-band + Other_GES-->>Log-on GES: Test signal units (continuous) + Log-on GES-->>AES: C, sub-band + +``` + +Sequence diagram showing air-to-ground telephone call set-up sequence between 'Other' GES, Log-on GES, and AES. The sequence includes messages like Credit card data, (User) Off-hook & number, Access request, Rd, Interstation link, C-channel assignment, Pd, Service address and credit card data (if applicable) (continuous), and Test signal units (continuous). + +T1128300-90/d06 + +Further procedure is same as for air-to-ground call setup for the log-on GES + +Rd See 1.3.2 + +Pd See 1.3.2 + +FIGURE I.3/Q.1151 + +**Air-to-ground telephone call set-up sequence to other GES** + +![Sequence diagram showing the air-to-ground telephone call set-up sequence (overflow mode) between NCS, Log-on GES, and AES. The sequence includes messages like Credit card data, (User) Off-hook & number, Access request, Rd, Req. for C-channel, Interstation link, C-channel assignment, Pd, C, sub-band, Test signal units (continuous), C-channel release, and C-channel release ack.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant NCS + participant Log-on GES + participant AES + + Note right of AES: Credit card data + Note right of AES: (User) Off-hook & number + Note right of AES: Access request + AES->>Log-on GES: Rd + Note right of Log-on GES: Req. for C-channel + Log-on GES->>NCS: Interstation link + Note left of NCS: C-channel assignment + NCS->>Log-on GES: C-channel assignment + Log-on GES->>AES: Pd + Note right of AES: Service address and credit card data (if applicable) (continuous) + AES->>Log-on GES: C, sub-band + Note left of Log-on GES: Test signal units (continuous) + Log-on GES->>AES: C, sub-band + Log-on GES->>NCS: C-channel release + Note left of NCS: C-channel release ack. + NCS->>Log-on GES: + +``` + +Sequence diagram showing the air-to-ground telephone call set-up sequence (overflow mode) between NCS, Log-on GES, and AES. The sequence includes messages like Credit card data, (User) Off-hook & number, Access request, Rd, Req. for C-channel, Interstation link, C-channel assignment, Pd, C, sub-band, Test signal units (continuous), C-channel release, and C-channel release ack. + +T1128310-90/d07 + +Further procedure is same as for air to ground call without NCS till GES monitors for carrier off after clearing + +Rd See 1.3.2 + +Pd See 1.3.2 + +FIGURE 1.4/Q.1151 + +**Air-to-ground telephone call set-up sequence (overflow mode)** + +![Sequence diagram for Air-to-ground telephone call set-up sequence to other GES (overflow mode).](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates the call set-up sequence between four entities: "Other" GES, NCS, Log-on GES, and AES. The sequence of messages is as follows: + +- Request for channel assignment:** The Log-on GES sends an **Rd** message to the AES. The AES responds with **Credit card data**, **(User) Off-hook & number**, and **Access request**. The Log-on GES then sends an **Access request** to the NCS. The NCS sends an **ISL** message to the "Other" GES. The "Other" GES responds with an **ISL** message to the NCS. The NCS sends a **C-channel assign.** message to the Log-on GES. +- C-channel assign.:** The Log-on GES sends a **Pd** message to the AES. The AES responds with **Services address & credit card data (if applicable) (continuous)**. The Log-on GES sends a **C-channel assign.** message to the NCS. The NCS sends a **C, sub-band** message to the Log-on GES. The Log-on GES sends a **C, sub-band** message to the AES. +- Test signal units (continuous):** The Log-on GES sends a **C, sub-band** message to the NCS. The NCS sends a **C, sub-band** message to the Log-on GES. The Log-on GES sends a **C, sub-band** message to the AES. +- C-channel release:** The Log-on GES sends an **ISL** message to the NCS. The NCS responds with an **ISL** message to the Log-on GES. The Log-on GES sends an **ISL** message to the "Other" GES. The "Other" GES responds with an **ISL** message to the Log-on GES. The Log-on GES sends a **C-channel release ack.** message to the NCS. + +Sequence diagram for Air-to-ground telephone call set-up sequence to other GES (overflow mode). + +T1128320-90/d08 + +Further procedure is same as for air to ground call without NCS +till GES monitors carrier off after clearing + +ISL Interstation link + +Rd See 1.3.2 + +Pd See 1.3.2 + +FIGURE I.5/Q.1151 + +**Air-to-ground telephone call set-up sequence to other GES (overflow mode)** + +![Sequence diagram of Air-to-ground telephone call user switchhook signalling between GES and AES.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram illustrates the signalling sequence between a Ground Station (GES) and an Air Station (AES) for an air-to-ground call. The sequence starts with the B-party off-hook (Answer) at the GES, followed by a Connect signal. The GES then sends a series of 'C, sub-band' signals to the AES, which responds with an 'Acknowledge'. The GES then sends a 'B-party on-hook (Clearback)' signal, followed by 'Time supervision of 1 to 2 minutes'. The GES then sends a 'Channel releasea) then carrier off' signal, which the AES acknowledges with 'Channel releasea) then carrier off'. The GES monitors for carrier off and sends a 'Clearback sequence'. The AES then sends an '(A-Party) On-hook' signal, followed by 'Channel releasea) then carrier off' and 'Carrier off'. The GES monitors for carrier off again. + +Sequence of events: + +- B-party off-hook (Answer) → GES +- Connect → GES +- C, sub-band → AES +- Acknowledge → AES +- A: Answer sequence (dashed line) +- B-party on-hook (Clearback) → GES +- Time supervision of 1 to 2 minutes (dashed line) +- C, sub-band → AES +- Channel releasea) then carrier off → AES +- C, sub-band → GES +- GES monitors for carrier off (dashed line) +- B: Clearback sequence (dashed line) +- (A-Party) On-hook → AES +- Channel releasea) then carrier off → AES +- Carrier off → AES +- C, sub-band → GES +- GES monitors for carrier off (dashed line) + +Sequence diagram of Air-to-ground telephone call user switchhook signalling between GES and AES. + +T1128330-90/d09 + +C: Clearing sequence + +a) Repeated 6 times. + +FIGURE I.6/Q.1151 +Air-to-ground telephone call user switchhook signalling + +### I.6.3 Channel set-up/termination for ground-to-air calls + +**I.6.3.1** The sequences for ground-to-air telephone call set-up are shown in Figures I.7 to I.10 covering various cases, including use of an NCS. + +**I.6.3.2** From the viewpoint of the AES, all the cases are similar with the GES sending the call announcement and channel assignment information to the AES over the P-channel. After the channel assignment information is transferred to the AES, the continuity check for proper channel set-up and the eventual channel release functions of the satellite link, are carried out using signals on the sub-band C-channel. + +**I.6.3.3** In the case of a call from a log-on GES to an AES (Figure I.7) the only channel used prior to setting up the call is the P-channel. However, if the call is from a GES other than where the AES has logged-on (Figure I.8) the originating GES (“other” GES) sends the call announcement and channel assignment information to the log-on GES over the interstation link. The log-on GES then forwards this information to the AES over the P-channel. The signalling sequences for the cases where the call- originating GES does not have a channel in its allocated pool are shown in Figures I.9 and I.10, the former showing the case of a call originating from a log-on GES and the latter representing a call origination from a GES other than the one to which the AES has logged-on. In both cases the interstation link between the NCS and the call originating GES is used to obtain a channel from the NCS pool. After the call is cleared, the GES from which the call has originated, sends the channel release information to the NCS, which the NCS acknowledges. The procedure for call clearing (illustrated in Figure I.11) is initiated by the terrestrial network sending a clear forward signal, whereupon the GES sends a sequence of channel release signals on the sub-band C-channel. On receipt of one of these, the AES responds with a series of channel release signals, and ceases its carrier. When the GES detects the end of the AES carrier, it returns the channel to the pool. + +![Sequence diagram for Ground-to-air telephone call set-up sequence between GES and AES.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +This sequence diagram illustrates the call set-up between a Ground Station (GES) and an Air Station (AES). The sequence begins with an external 'Call' arriving at the GES. The GES sends a 'Call announcement' (Pd) and a 'C-channel announcement' (Pd) to the AES. The AES responds with 'Test signal units (continuous)'. The GES replies with two 'C, sub-band' messages and also sends its own 'Test signal units (continuous)'. The AES then initiates the 'Call to user terminal' and sends a 'Test signals stopped' message. Finally, the GES sends a 'Connect through' message, leading to 'Ring tone or alerting' at the user terminal. + +``` + +sequenceDiagram + participant External + participant GES + participant AES + Note left of GES: Pd See 1.3.2 + External->>GES: Call + GES->>AES: Call announcement (Pd) + GES->>AES: C-channel announcement (Pd) + AES->>GES: Test signal units (continuous) + GES->>AES: C, sub-band + GES->>GES: Test signal units (continuous) + GES->>AES: C, sub-band + AES->>External: Call to user terminal + AES->>GES: Test signals stopped + GES->>External: Connect through + External->>External: Ring tone or alerting + +``` + +Sequence diagram for Ground-to-air telephone call set-up sequence between GES and AES. + +T1128340-90/d10 + +Pd See 1.3.2 + +FIGURE I.7/Q.1151 +Ground-to-air telephone call set-up sequence + +![Sequence diagram for Ground-to-air call set-up sequence via other GES, involving 'Other' GES, Log-on GES, and AES.](a3472689858b068ef469213682965325_img.jpg) + +This sequence diagram shows the call set-up process involving three entities: 'Other' GES, Log-on GES, and AES. An external 'Call' arrives at the 'Other' GES, which sends a 'Call announcement' and a 'C-channel assignment' to the Log-on GES. The Log-on GES then sends a 'Pd' message and 'Test signal units (continuous)' to the AES. The AES responds with 'C, sub-band' and 'Test signal units (continuous)'. The Log-on GES receives a 'C, sub-band' from the AES and forwards it to the 'Other' GES. The Log-on GES also sends 'Test signals stopped' to the AES. Finally, the Log-on GES sends a 'Connect through' message to the 'Other' GES, resulting in 'Ring tone or alerting' at the user terminal. + +``` + +sequenceDiagram + participant External + participant OtherGES as "Other" GES + participant LogonGES as Log-on GES + participant AES + Note left of OtherGES: Pd See 1.3.2 + External->>OtherGES: Call + OtherGES->>LogonGES: Call announcement + OtherGES->>LogonGES: C-channel assignment + LogonGES->>AES: Pd + LogonGES->>AES: Test signal units (continuous) + AES->>LogonGES: C, sub-band + AES->>AES: Test signal units (continuous) + LogonGES->>OtherGES: C, sub-band + LogonGES->>AES: Test signals stopped + LogonGES->>OtherGES: Connect through + OtherGES->>External: Ring tone or alerting + +``` + +Sequence diagram for Ground-to-air call set-up sequence via other GES, involving 'Other' GES, Log-on GES, and AES. + +T1128350-90/d11 + +Pd See 1.3.2 + +FIGURE I.8/Q.1151 +Ground-to-air call set-up sequence via other GES + +![Sequence diagram showing the ground-to-air telephone call set-up sequence (overflow mode) between GES, NCS, and AES.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +sequenceDiagram + participant GES + participant NCS + participant AES + + Note over GES: Call + GES->>NCS: Request for channel assignment (ISL) + NCS-->>GES: C-channel assignment + GES->>AES: Call announcement (Pd) + GES->>AES: C-channel assignment (Pd) + AES-->>GES: Test signal units (continuous) (C, sub-band) + GES-->>AES: Test signal units (continuous) (C, sub-band) + GES->>NCS: C-channel release (ISL) + NCS-->>GES: C-channel release ack. (ISL) + +``` + +The diagram illustrates the call set-up sequence for a ground-to-air telephone call in overflow mode. It involves three main entities: GES (Ground Earth Station), NCS (Network Coordination Station), and AES (Aircraft Earth Station). The sequence begins with an incoming 'Call' at the GES. The GES sends a 'Request for channel assignment' via an Interstation link (ISL) to the NCS. The NCS responds with a 'C-channel assignment'. The GES then sends a 'Call announcement' and 'C-channel assignment' (both marked Pd) to the AES. Continuous 'Test signal units' are then exchanged between the AES and GES on the C, sub-band. Finally, the GES sends a 'C-channel release' (ISL) to the NCS, which acknowledges it with a 'C-channel release ack.' (ISL). + +Sequence diagram showing the ground-to-air telephone call set-up sequence (overflow mode) between GES, NCS, and AES. + +T1128360-90/d12 + +Further procedure is same as for air to ground call without NCS till GES monitors carrier off after clearing + +ISL Interstation link +Pd See 1.3.2 + +FIGURE I.9/Q.1151 +**Ground-to-air telephone call set-up sequence (overflow mode)** + +![Sequence diagram showing ground-to-air telephone call set-up sequence via other GES (overflow mode). Lifelines: Call, 'Other' GES, NCS, Log-on GES, AES. The sequence involves channel assignment, call announcement, test signal units, and channel release messages between these entities.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +sequenceDiagram + participant Call + participant OtherGES as "Other" GES + participant NCS + participant LogonGES as Log-on GES + participant AES + + Note left of Call: Call + Call->>OtherGES: Request for channel assignment + OtherGES->>NCS: ISL + NCS-->>OtherGES: C-channel assign. + OtherGES->>LogonGES: Call announcement + LogonGES->>AES: Pd + LogonGES->>AES: Pd + Note right of AES: Test signal units (continuous) + OtherGES->>NCS: C-channel assignment + NCS-->>LogonGES: Call announcement + LogonGES->>AES: C, sub-band + Note right of AES: Test signal units (continuous) + OtherGES->>NCS: Test signal units (continuous) + NCS-->>LogonGES: C, sub-band + LogonGES->>AES: C, sub-band + Note right of AES: Test signal units (continuous) + OtherGES->>NCS: C-channel release + NCS-->>OtherGES: ISL + OtherGES->>NCS: ISL + NCS-->>OtherGES: C-channel release ack. + +``` + +Sequence diagram showing ground-to-air telephone call set-up sequence via other GES (overflow mode). Lifelines: Call, 'Other' GES, NCS, Log-on GES, AES. The sequence involves channel assignment, call announcement, test signal units, and channel release messages between these entities. + +T1128370-90/d13 + +Further procedure is the same as for air to ground call without NCS till GES monitors for carrier off after clearing + +ISL Interstation link +Pd See 1.3.2 + +FIGURE I.10/Q.1151 +**Ground-to-air telephone call set-up sequence via other GES (overflow mode)** + +![Sequence diagram showing Ground-to-air telephone call user switchhook signalling between GES and AES. The diagram illustrates the interaction for answer and clearback sequences using C sub-band messages.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +sequenceDiagram + participant GES + participant AES + Note right of AES: B-Party off-hook + AES->>GES: C, sub-band (Answer) + Note left of GES: Acknowledge + GES->>AES: C, sub-band + Note right of AES: B-Party on-hook (Clearback) + AES->>GES: C, sub-band (Channel releasea) then carrier off) + Note left of GES: Channel releasea) +GES monitors for carrier off + GES->>AES: C, sub-band + Note right of AES: Carrier off + Note left of GES: B: Clearback sequence +(A-Party) On-hook + GES->>AES: C, sub-band (Channel releasea)) + Note right of AES: Channel releasea) + GES->>AES: C, sub-band + Note right of AES: Carrier off + +``` + +GES Monitors for carrier off +C: Clearing sequence + +T1128380-90/d14 + +Sequence diagram showing Ground-to-air telephone call user switchhook signalling between GES and AES. The diagram illustrates the interaction for answer and clearback sequences using C sub-band messages. + +a) Repeated 6 times. + +FIGURE I.11/Q.1151 +**Ground-to-air telephone call user switchhook signalling** + +#### I.6.4 Supervisory signalling + +**I.6.4.1** After call set-up, all subsequent supervisory functions are normally performed by means of subband signalling on the C-channel. + +**I.6.4.2** Continuity checking of the satellite voice channel is done by means of test packets transmitted on the sub-band of the C-channel. + +**I.6.4.3** Sub-band signalling on the C-channel is also used for answer/clearing signals, and to provide additional signalling capacity for potential future use in interworking with the terrestrial ISDNs. + +**I.6.4.4** Terrestrial network audible tones (ringing, busy, congestion, etc.) are passed to the AES in-band over the voice channel for air-to-ground calls. In the case of ground-to-air calls, the MSSC should return call progress and call failure causes to the terrestrial network by means of appropriate signals, from the signalling system in use. When required (due to the inadequacy of the signalling system in use), the MSSC should also generate audible tones back into the terrestrial network to the calling party. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cf8e535eadd48234a3c5e4bbf68bb12bfd404b9 --- /dev/null +++ b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00c410f24076b9247071d09551078747167bb99f86cb637cd225b2cc0c1efc64 +size 137857 diff --git a/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c216f8d1a7bf33f7519ba212b67c29ffa2ed1906 --- /dev/null +++ b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:895388ff20c0fb4796447afed3fe4b72319ac578d5672744eef43c8673397cd2 +size 69371 diff --git a/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4774b3a190fdc9f65b8ae6259a55d3a725a7dd4a --- /dev/null +++ b/marked/Q/T-REC-Q.120-Q.139-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.120-Q.139-198811-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58fb824361c469f7dea417765b431c62c3e7891d --- /dev/null +++ b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f758ad913e58208b70d9c6a793ab7ac0683d5e3c58410f4bdacb413ab59e1031 +size 237748 diff --git a/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdb94b135f01505e4ce11478d31533d57af29716 --- /dev/null +++ b/marked/Q/T-REC-Q.120-Q.139-198811-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5db882a04b49f5bdd2280c9c91d28869cfd3c11faa1d5a66b85475b014108d65 +size 147829 diff --git a/marked/Q/T-REC-Q.1210-199510-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1210-199510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6d18c3efd87174066622b6b148032c09e01cde7d --- /dev/null +++ b/marked/Q/T-REC-Q.1210-199510-I_PDF-E/raw.md @@ -0,0 +1,402 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1210** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/95) + +**INTELLIGENT NETWORK** + +--- + +**Q.1210-SERIES INTELLIGENT NETWORK +RECOMMENDATION STRUCTURE** + +**ITU-T Recommendation Q.1210** + +(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.1210 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. + +--- + +## NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SUMMARY** + +A block of one hundred numbers has been set aside in the Q-Series (Q.1200-Q.1299) for the development of Intelligent Network (IN) Recommendations. Q.1210 is a new Recommendation in the IN-Series that was developed in conjunction with the IN CS-1 refinements to better align the IN CS-1 Recommendations with the overall IN CS-n Recommendation structure. + +This Recommendation, the first in the IN Capability Set-1 Series, has been developed to show the organization of the IN CS-1 Recommendations in a meaningful way and to assist users in locating topics of interest. It provides a structural overview of the Q.1200-Series, IN Recommendations, as well as the content of each of the Q.1210-Series, IN CS-1 Recommendations. + +Associated standards work is contained in the Q.1200-Series as well as the Q.1210-Series of IN Recommendations. + + + +# Q.1210-SERIES INTELLIGENT NETWORK RECOMMENDATION STRUCTURE + +(Geneva, 1995) + +## General Q.1200-Series structure + +Table 1 shows the overall Q.1200-Series Intelligent Network Recommendation structural distribution through the tens digits (1200, 1210, 1220, etc.) and the ones digits (i.e. 1201, 1202, 1203, etc.). + +TABLE 1/Q.1210 + +### 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 Recommendations | +| 90 – Glossary | 9 – Intelligent Network user's guide | +| NOTES | | +| 1 | Recommendation Q.1200 is assigned as for the IN Recommendation framework structure. | +| 2 | Q.1290-Series has been set aside for the glossary. | + +# **Q.1210-SERIES INTELLIGENT NETWORK RECOMMENDATION STRUCTURE** + +## **1 Q.1210-Series Intelligent Network Recommendation overview** + +### **Q.1210 – Q-Series Intelligent Network Recommendation structure** + +- 1 Q.1210-Series Intelligent Network Recommendation overview + +### **Q.1211 – Introduction to Intelligent Network capability set-1** + +- 1 Introduction +- 2 Phased standardization +- 3 General description and scope of CS-1 + - 3.1 Criteria for CS-1 + - 3.2 Evolution of CS-1 +- 4 Overview of CS-1 Recommendations +- 5 Service aspects + - 5.1 Type A and B services + - 5.2 Target set of CS-1 service and service features + - 5.3 Network support of CS-1 services +- 6 Network aspects + - 6.1 Network functions + - 6.2 Control architecture principles + - 6.3 Feature interactions + - 6.4 Consistency among CS-1 supported service features +- 7 Functional relationships and interfaces + - 7.1 Reference points and identifiers for functional relationships + - 7.2 Control classes + - 7.3 Reference point identifiers of functional interfaces + - 7.4 CS-1 Non-IN connection and call control + - 7.5 CS-1 IN service control + - 7.6 Service management for CS-1 + - 7.7 Network interworking in CS-1 + - 7.8 Summary of CS-1 functional interfaces + +Annex A – Examples of relationships and mappings between services and service features + +Annex B – Short prose descriptions of targeted services and service features + +### **Q.1213 – Global functional plane for Intelligent Network CS-1** + +- 1 General +- 2 Scope of IN global functional plane for capability set 1 +- 3 References +- 4 IN CS-1 global functional plane + - 4.1 Role of SIBs in the global functional plane + - 4.2 Additional characteristics of a IN CS-1 SIBs + - 4.3 CS-1 global functional plane model + - 4.4 Terminology +- 5 IN CS-1 Service Independent Building Blocks (SIBs) + - 5.1 Data parameters for SIBs + - 5.2 Method to describe SIBs + +- 5.3 ALGORITHM +- 5.4 AUTHENTICATE +- 5.5 CHARGE +- 5.6 COMPARE +- 5.7 DISTRIBUTION +- 5.8 LIMIT +- 5.9 LOG CALL INFORMATION +- 5.10 QUEUE +- 5.11 SCREEN +- 5.12 SERVICE DATA MANAGEMENT +- 5.13 STATUS NOTIFICATION +- 5.14 TRANSLATE +- 5.15 USER INTERACTION +- 5.16 VERIFY +- 6 Basic call process + - 6.1 General + - 6.2 Point of initiation and point of return + - 6.3 BCP stage 1 description +- 7 Global service logic + - 7.1 Relationship between GSL and BCP + - 7.2 Relationship between global service logic and SIBs +- 8 Mapping of the service plane to the global functional plane + +### **Q.1214 – Distributed functional plane for Intelligent Network CS-1** + +- 1 General +- 2 Scope of IN distributed functional plane for capability set 1 + - 2.1 End-user access + - 2.2 Service invocation and control + - 2.3 End-user interaction + - 2.4 Service management +- 3 Distributed functional plane model for CS-1 + - 3.1 Explanation of diagram + - 3.2 IN functional model + - 3.3 Definition of Functional Entities related to IN service execution +- 4 Functional entity call/service processing models + - 4.1 Overview + - 4.2 SSF/CCF model + - 4.2.1 General + - 4.2.2 Basic Call Manager (BCM) + - 4.2.3 IN-Switching Manager (IN-SM) + - 4.2.4 Feature Interaction Manager (FIM)/Call Manager (CM) + - 4.2.5 Relationship of SSF/CCF model components + - 4.2.6 Relationship of SSF/CCF to SCF + - 4.3 Specialized Resource Function (SRF) model + - 4.3.1 General + - 4.3.2 SRF components + - 4.3.3 SRF and other entity relationships + - 4.3.4 Objects of SRF management + - 4.4 Service Control Function (SCF) model + - 4.4.1 General + - 4.4.2 SCF components + - 4.4.3 Functional routine categories + +- 4.5 Service Data Function (SDF) model + - 4.5.1 General + - 4.5.2 SDF components + - 4.5.3 Data types handled by the SDF +- 5 Stage 2 description of Service Independent Building Blocks (SIBs) + - 5.1 Introduction + - 5.1.1 Functional model + - 5.1.2 Description of functional entities + - 5.1.3 Numbering of functional entity actions + - 5.1.4 Relationship with clause 6 (Information flow descriptions) + - 5.1.5 Organization of clause 5 + - 5.1.6 Abbreviations used in clause 5 + - 5.2 SIB stage 2 descriptions + - 5.2.1 ALGORITHM SIB + - 5.2.2 CHARGE SIB + - 5.2.3 COMPARE SIB + - 5.2.4 DISTRIBUTION SIB + - 5.2.5 LIMIT SIB + - 5.2.6 LOG CALL INFORMATION SIB + - 5.2.7 QUEUE SIB + - 5.2.8 SCREEN SIB + - 5.2.9 SERVICE DATA MANAGEMENT SIB + - 5.2.10 STATUS NOTIFICATION SIB + - 5.2.11 TRANSLATE SIB + - 5.2.12 USER INTERACTION SIB + - 5.2.13 VERIFY SIB + - 5.2.14 AUTHENTICATE SIB + - 5.3 BASIC CALL PROCESS SIB + - 5.3.1 Description + - 5.3.2 Information flows + - 5.3.3 SDLs + - 5.3.4 Functional entity actions + - 5.4 Stage 2 description of other distributed functionality + - 5.4.1 Activity test functionality + - 5.4.2 Call Gap capability + - 5.5 Mapping of the global functional plane to the distributed functional plane + - 5.5.1 Mapping of POIs and PORs to DPs and PICs + - 5.5.2 Relating the GFP to the DFP +- 6 Relationships between FEs + - 6.1 General + - 6.2 Relationships + - 6.3 Information flows between FEs + - 6.4 SCF-SSF relationship + - 6.4.1 General + - 6.4.2 Information flows between SCF and SSF + - 6.4.3 Call party handling information flows + - 6.4.4 IE rules for SSF/CCF to SCF information flows + - 6.5 SCF-SRF relationship + - 6.5.1 General + - 6.5.2 Information flows between the SCF and SRF + - 6.6 SCF-SDF relationship + - 6.6.1 General + - 6.6.2 Information flows between the SCF and SDF + - 6.7 Summary of information flows and related SIBs + +Annex A – Communication between call segments + +Annex B – BCSM SDL Diagrams + +Appendix I – Aspects of the distributed functional plane identified as “for further study” (FFS) relative to CS-1 + +Appendix II – Charging scenarios examples + +### **Q.1215 – Physical plane for Intelligent Network CS-1** + +- 1 General +- 2 Requirements and assumptions + - 2.1 Requirements + - 2.2 Assumptions +- 3 Physical Entities (PEs) +- 4 Mapping requirements +- 5 Mapping the distributed functional plane to the physical plane + - 5.1 Mapping of functional entities to physical entities + - 5.2 Mapping FE-FE relationships to PE-PE relationships + - 5.3 Selection of underlying protocol platforms + - 5.3.1 SCP-SSP interface + - 5.3.2 AD-SSP interface + - 5.3.3 IP-SSP interface + - 5.3.4 SN-SSP interface + - 5.3.5 SCP-IP interface + - 5.3.6 AD-IP interface + - 5.3.7 SCP-SDP interface + - 5.3.8 User interfaces + +### **Q.1218 – Interface Recommendations for Intelligent Network CS-1** + +- 0 Introduction + - 0.1 Normative references + - 0.2 Definition methodology + - 0.3 Example physical scenarios + - 0.4 INAP protocol architecture + - 0.5 INAP addressing + - 0.6 Relationship between Recommendation Q.1214 and this Recommendation + - 0.7 Compatibility mechanisms used for INAP +- 1 SACF/MACF rules + - 1.1 Reflection of TCAP AC + - 1.2 Sequential/Parallel execution of operations +- 2 ASN.1 introduction + - 2.1 SSF/SCF, SCF/SRF, SSF/SRF interfaces + - 2.1.1 Operation types IN CS-1 operations + - 2.1.2 Error types IN CS-1 error + - 2.1.3 Data types IN CS-1 data types + - 2.1.4 Operation and error codes IN CS-1 codes + - 2.1.5 Application context + - 2.2 SCF/SDF Interface + - 2.2.1 Introduction to IN X.500 DAP subset + - 2.2.2 The IN X.500 DAP subset + - 2.2.2.1 Review of X.511 for use in the IN + - 2.2.2.2 Directory Access Protocol Subset + - 2.2.2.3 X.501 profile + +- 2.2.2.4 Enhancements to X.500 for the support of the IN CS-1 +- 2.2.2.5 ASN.1 Profile of the Directory Abstract Service for the IN CS-1 + +## 3 Semantics + +- 3.1 Definition of procedures and entities + - 3.1.1 SSF Application Entity procedures + - 3.1.2 SCF Application Entity procedures + - 3.1.3 SRF Application Entity procedures + - 3.1.4 SDF Application Entity procedures +- 3.2 Error procedures +- 3.3 Detailed Operation procedures +- 3.4 Services assumed from TCAP + +Annex A – INAP SDL diagrams + +Annex B – SCSM/SDSM SDLs + +Appendix I – Aspects of the Intelligent Network interface identified as “for further study” (FFS) relative to CS-1 + +Appendix II – Expanded ASN.1 Coding + +### **Q.1219 – Intelligent Network users guide for capability set-1** + +## 1 Scope + +- 1.1 Target audience +- 1.2 Intended use +- 1.3 Framework outline of Q.1200-Series +- 1.4 Initial set of capabilities +- 1.5 State of Maturity of the CS-1 Recommendations +- 1.6 Service Decomposition for CS-1 + +## 2 Intelligent Network objectives + +## 3 Capabilities provided by Capability Set-1 + +- 3.1 Service implementation independence +- 3.2 Multi-Vendor capability +- 3.3 Multi-Network capability +- 3.4 Rapid service delivery +- 3.5 Service deployment + +## 4 Service aspects for CS-1 + +- 4.1 Basic Service Capabilities +- 4.2 Type A service category +- 4.3 Type B service category +- 4.4 Phases of deployed services + +## 5 CS-1 Architecture + +- 5.1 Functions +- 5.2 IN CS-1 plane relationships + - 5.2.1 IN CS-1 Service Plane + - 5.2.2 IN CS-1 Global Functional + - 5.2.3 IN CS-1 Distributed Functional Plane + - 5.2.4 IN CS-1 Physical Plane +- 5.3 Interfaces and relationships + +## 6 Infrastructure in CS-1 + +- 6.1 Service Independent Building Blocks (SIBs) +- 6.2 Service logic + +- 6.3 Functional Entity Call/Service Logic Processing Models + - 6.3.1 Call Modelling for IN CS-1 + - 6.3.2 Modelling of Service Logic Processing for IN CS-1 + - 6.3.3 General considerations + - 6.4 Information flows + - 6.4.1 Requirement for an information flow from SCF to SSF to Initiate “Call Follow-On” + - 6.5 Intelligent Network Applications Protocol (INAP) + - 6.5.1 General ASE discussion + - 6.5.2 General Application Context discussion + - 6.5.3 Service Filtering + - 6.5.4 Optional Parameters + - 6.5.5 Considerations for the use and understanding of various operations and procedures in Recommendation Q.1218 + - 6.6 Requirement on Inter-Exchange and User-Network Signalling + - 6.6.1 General + - 6.6.2 Interworking INAP and Network or Access Signalling + - 6.6.3 Terminal Type and Access Type of User + - 6.6.4 Optional Parameters in DP operations + - 6.6.5 Miscellaneous + - 7 Service example + - 7.1 Utilizing CS-1 capabilities + - 7.2 Guidelines for service scenarios + - 7.3 Format for service scenarios + - 8 Physical deployment scenarios + - 8.1 Mapping FEs to PEs + - 8.2 Mapping of FE-FE relationships to PE-PE relationships + - 9 Future IN Capability Sets + - 9.1 Generic plans + - 9.2 “Stretch forward/ease back” + - 9.3 Evolvable capabilities + - 9.4 Evolvability concepts +- Annex A – IN CS-1 Service Scenario Examples +- Annex B – BCSM SDLs \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1218-199510-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1218-199510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d476d2b9a3d537d96dc6d37c61b68a68852fe5a8 --- /dev/null +++ b/marked/Q/T-REC-Q.1218-199510-I_PDF-E/raw.md @@ -0,0 +1,23309 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A diagonal line with an arrowhead points from the top-left towards the bottom-right across the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1218** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/95) + +**INTELLIGENT NETWORK** + +--- + +**INTERFACE RECOMMENDATION +FOR INTELLIGENT NETWORK CS-1** + +**ITU-T Recommendation Q.1218** + +(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.1218 was revised by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +*Page* + +| | | | +|---------|---------------------------------------------------------------------------|-----| +| 0 | Introduction ..... | 1 | +| 0.1 | Normative references ..... | 1 | +| 0.2 | Definition methodology ..... | 2 | +| 0.3 | Example physical scenarios ..... | 3 | +| 0.4 | INAP protocol architecture ..... | 9 | +| 0.5 | INAP addressing ..... | 11 | +| 0.6 | Relationship between Recommendation Q.1214 and this Recommendation ..... | 11 | +| 0.7 | Compatibility mechanisms used for INAP ..... | 13 | +| 1 | SACF/MACF rules ..... | 14 | +| 1.1 | Reflection of TCAP-AC ..... | 14 | +| 1.2 | Sequential/Parallel execution of operations ..... | 14 | +| 2 | Abstract syntax of the IN CS-1 Application Protocol ..... | 15 | +| 2.1 | SSF-SCF, SCF-SRF Interface ..... | 15 | +| 2.1.1 | IN CS-1 Operation Types ..... | 15 | +| 2.1.2 | IN CS-1 Error Types ..... | 31 | +| 2.1.3 | IN CS-1 Data Types ..... | 33 | +| 2.1.4 | IN CS-1 application protocol (operation and error codes) ..... | 57 | +| 2.1.5 | Application Contexts ..... | 65 | +| 2.2 | SCF-SDF interface ..... | 67 | +| 2.2.1 | Introduction to the IN X.500 DAP Subset ..... | 67 | +| 2.2.1.1 | Alignment between the X.500 concepts and the IN ..... | 67 | +| 2.2.1.2 | Use of a limited subset of X.500 ..... | 68 | +| 2.2.1.3 | Working assumptions ..... | 68 | +| 2.2.2 | The IN X.500 DAP Subset ..... | 69 | +| 2.2.2.1 | Review of X.511 for use in the IN ..... | 69 | +| 2.2.2.2 | Directory Access Protocol Subset ..... | 76 | +| 2.2.2.3 | X.501 profile ..... | 85 | +| 2.2.2.4 | ASN.1 Profile of the Directory Abstract Service for the IN CS-1 ..... | 85 | +| 3 | Semantics ..... | 92 | +| 3.1 | Definition of procedures and entities ..... | 92 | +| 3.1.1 | SSF application entity procedures ..... | 92 | +| 3.1.1.1 | General ..... | 92 | +| 3.1.1.2 | Model and interfaces ..... | 92 | +| 3.1.1.3 | Relations between SSF-FSM and the CCF and maintenance functions ..... | 93 | +| 3.1.1.4 | SSF Management Finite State Machine (SSME-FSM) ..... | 95 | +| 3.1.1.5 | SSF state transition diagram ..... | 97 | +| 3.1.1.6 | Assisting/Handoff SSF-FSM ..... | 104 | +| 3.1.2 | SCF application entity procedures ..... | 107 | +| 3.1.2.1 | General ..... | 107 | +| 3.1.2.2 | Model and interfaces ..... | 107 | +| 3.1.2.3 | Relationship between the SCF-FSM and the SLPs/maintenance functions ..... | 108 | +| 3.1.2.4 | Partial SCF Management Entity (SCME) State Transition Diagram ..... | 110 | +| 3.1.2.5 | The SCF Call State Model (SCSM) ..... | 113 | + +| | Page | +|-----------------------------------------------------------------------------------------------------|-------------| +| 3.1.3 SRF application entity procedures ..... | 128 | +| 3.1.3.1 General ..... | 128 | +| 3.1.3.2 Model and interfaces ..... | 129 | +| 3.1.3.3 Relationship between the SRF-FSM and maintenance functions/bearer connection handling ..... | 129 | +| 3.1.3.4 The SRSM ..... | 131 | +| 3.1.3.5 Example SRF control procedures ..... | 134 | +| 3.1.4 SDF application entity procedures ..... | 150 | +| 3.1.4.1 General ..... | 150 | +| 3.1.4.2 Model and interfaces ..... | 150 | +| 3.1.4.3 Relationship between the SDF-FSM and the maintenance function ..... | 150 | +| 3.1.4.4 SDF state transition model ..... | 150 | +| 3.2 Error procedures ..... | 153 | +| 3.2.1 Operation related error procedures ..... | 153 | +| 3.2.1.1 Attribute error ..... | 153 | +| 3.2.1.2 Cancelled ..... | 154 | +| 3.2.1.3 CancelFailed ..... | 155 | +| 3.2.1.4 ETCSFailed ..... | 156 | +| 3.2.1.5 ImproperCallerResponse ..... | 156 | +| 3.2.1.6 MissingCustomerRecord ..... | 157 | +| 3.2.1.7 MissingParameter ..... | 159 | +| 3.2.1.8 Name error ..... | 162 | +| 3.2.1.9 ParameterOutOfRange ..... | 163 | +| 3.2.1.10 RequestedInfoError ..... | 164 | +| 3.2.1.11 Service error ..... | 164 | +| 3.2.1.12 Security error ..... | 165 | +| 3.2.1.13 SystemFailure ..... | 166 | +| 3.2.1.14 Task refused ..... | 168 | +| 3.2.1.15 UnavailableResource ..... | 169 | +| 3.2.1.16 UnexpectedComponentSequence ..... | 170 | +| 3.2.1.17 UnexpectedDataValue ..... | 171 | +| 3.2.1.18 UnexpectedParameter ..... | 173 | +| 3.2.1.19 UnknownLegID ..... | 174 | +| 3.2.1.20 UnknownResource ..... | 174 | +| 3.2.1.21 Update error ..... | 174 | +| 3.2.2 Entity related error procedures ..... | 175 | +| 3.2.2.1 Expiration of T SSF ..... | 175 | +| 3.2.2.2 Expiration of T SRF ..... | 176 | +| 3.3 Detailed Operation procedures ..... | 176 | +| 3.3.1 ActivateServiceFiltering procedure ..... | 176 | +| 3.3.1.1 General description ..... | 176 | +| 3.3.1.2 Invoking Entity (SCF) ..... | 179 | +| 3.3.1.3 Responding Entity (SSF) ..... | 180 | +| 3.3.2 ActivityTest procedure ..... | 181 | +| 3.3.2.1 General description ..... | 181 | +| 3.3.2.2 Invoking Entity (SCF) ..... | 181 | +| 3.3.2.3 Responding Entity (SSF) ..... | 181 | +| 3.3.3 AddEntry procedure ..... | 181 | +| 3.3.3.1 General description ..... | 181 | +| 3.3.3.2 Invoking Entity (SCF) ..... | 182 | +| 3.3.3.3 Responding Entity (SDF) ..... | 182 | +| 3.3.4 AnalysedInformation Procedure ..... | 183 | +| 3.3.4.1 General description ..... | 183 | +| 3.3.4.2 Invoking Entity (SSF) ..... | 184 | +| 3.3.4.3 Responding Entity (SCF) ..... | 185 | +| 3.3.5 AnalyseInformation procedure ..... | 186 | +| 3.3.5.1 General description ..... | 186 | +| 3.3.5.2 Invoking Entity (SCF) ..... | 186 | +| 3.3.5.3 Responding Entity (SSF) ..... | 187 | + +| | Page | +|---------------------------------------------------|-------------| +| 3.3.6 ApplyCharging procedure..... | 189 | +| 3.3.6.1 General description ..... | 189 | +| 3.3.6.2 Invoking Entity (SCF)..... | 189 | +| 3.3.6.3 Responding Entity (SSF) ..... | 190 | +| 3.3.7 ApplyChargingReport procedure..... | 190 | +| 3.3.7.1 General description ..... | 190 | +| 3.3.7.2 Invoking Entity (SSF)..... | 190 | +| 3.3.7.3 Responding Entity (SCF) ..... | 191 | +| 3.3.8 AssistRequestInstructions procedure ..... | 191 | +| 3.3.8.1 General description ..... | 191 | +| 3.3.8.2 Invoking Entity (SSF-SRF)..... | 192 | +| 3.3.8.3 Responding Entity (SCF) ..... | 192 | +| 3.3.9 Bind procedure..... | 192 | +| 3.3.9.1 General description ..... | 192 | +| 3.3.9.2 Invoking Entity (SCF)..... | 193 | +| 3.3.9.3 Responding Entity (SDF)..... | 193 | +| 3.3.10 CallGap procedure ..... | 193 | +| 3.3.10.1 General description ..... | 193 | +| 3.3.10.2 Invoking Entity (SCF)..... | 196 | +| 3.3.10.3 Responding Entity (SSF) ..... | 196 | +| 3.3.11 CallInformationReport procedure ..... | 197 | +| 3.3.11.1 General description ..... | 197 | +| 3.3.11.2 Invoking Entity (SSF)..... | 197 | +| 3.3.11.3 Responding Entity (SCF) ..... | 198 | +| 3.3.12 CallInformationRequest procedure ..... | 199 | +| 3.3.12.1 General description ..... | 199 | +| 3.3.12.2 Invoking Entity (SCF)..... | 199 | +| 3.3.12.3 Responding Entity (SSF) ..... | 200 | +| 3.3.13 Cancel procedure ..... | 200 | +| 3.3.13.1 General description ..... | 200 | +| 3.3.13.2 Invoking Entity (SCF)..... | 200 | +| 3.3.13.3 Responding Entity (SRF) ..... | 201 | +| 3.3.13.4 Responding Entity (SSF) ..... | 201 | +| 3.3.14 CollectedInformation procedure ..... | 201 | +| 3.3.14.1 General description ..... | 201 | +| 3.3.14.2 Invoking Entity (SSF)..... | 203 | +| 3.3.14.3 Responding Entity (SCF) ..... | 205 | +| 3.3.15 CollectInformation procedure..... | 206 | +| 3.3.15.1 General description ..... | 206 | +| 3.3.15.2 Invoking Entity (SCF)..... | 206 | +| 3.3.15.3 Responding Entity (SSF) ..... | 207 | +| 3.3.16 Connect procedure ..... | 207 | +| 3.3.16.1 General description ..... | 207 | +| 3.3.16.2 Invoking Entity (SCF)..... | 208 | +| 3.3.16.3 Responding Entity (SSF) ..... | 209 | +| 3.3.17 ConnectToResource procedure ..... | 210 | +| 3.3.17.1 General description ..... | 210 | +| 3.3.17.2 Invoking Entity (SCF)..... | 210 | +| 3.3.17.3 Responding Entity (SSF) ..... | 211 | +| 3.3.18 Continue procedure..... | 211 | +| 3.3.18.1 General description ..... | 211 | +| 3.3.18.2 Invoking Entity (SCF)..... | 211 | +| 3.3.18.3 Responding Entity (SSF) ..... | 211 | +| 3.3.19 DisconnectForwardConnection procedure..... | 212 | +| 3.3.19.1 General description ..... | 212 | +| 3.3.19.2 Invoking Entity (SCF)..... | 212 | +| 3.3.19.3 Responding Entity (SSF) ..... | 213 | + +| | Page | +|-------------------------------------------------------|-------------| +| 3.3.20 EstablishTemporaryConnection procedure ..... | 213 | +| 3.3.20.1 General description ..... | 213 | +| 3.3.20.2 Invoking Entity (SCF)..... | 214 | +| 3.3.20.3 Responding Entity (SSF) ..... | 214 | +| 3.3.21 EventNotificationCharging procedure ..... | 215 | +| 3.3.21.1 General description ..... | 215 | +| 3.3.21.2 Invoking Entity (SSF)..... | 215 | +| 3.3.21.3 Responding Entity (SCF)..... | 216 | +| 3.3.22 EventReportBCSM procedure ..... | 216 | +| 3.3.22.1 General description ..... | 216 | +| 3.3.22.2 Invoking Entity (SSF)..... | 217 | +| 3.3.22.3 Responding Entity (SCF)..... | 218 | +| 3.3.23 FurnishChargingInformation procedure ..... | 218 | +| 3.3.23.1 General description ..... | 218 | +| 3.3.23.2 Invoking Entity (SCF)..... | 219 | +| 3.3.23.3 Responding Entity (SSF) ..... | 219 | +| 3.3.24 HoldCallInNetwork procedure..... | 220 | +| 3.3.24.1 General description ..... | 220 | +| 3.3.24.2 Invoking Entity (SCF)..... | 220 | +| 3.3.24.3 Responding Entity (SSF) ..... | 221 | +| 3.3.25 InitialDP procedure..... | 221 | +| 3.3.25.1 General description ..... | 221 | +| 3.3.25.2 Invoking Entity (SSF)..... | 223 | +| 3.3.25.3 Responding Entity (SCF)..... | 223 | +| 3.3.26 InitiateCallAttempt procedure..... | 224 | +| 3.3.26.1 General description ..... | 224 | +| 3.3.26.2 Invoking Entity (SCF)..... | 224 | +| 3.3.26.3 Responding Entity (SSF) ..... | 225 | +| 3.3.27 ModifyEntry procedure..... | 225 | +| 3.3.27.1 General description ..... | 225 | +| 3.3.27.2 Invoking Entity (SCF)..... | 226 | +| 3.3.27.3 Responding Entity (SDF)..... | 226 | +| 3.3.28 OAnswer procedure ..... | 227 | +| 3.3.28.1 General description ..... | 227 | +| 3.3.28.2 Invoking Entity (SSF)..... | 227 | +| 3.3.28.3 Responding Entity (SCF)..... | 228 | +| 3.3.29 ODisconnect procedure..... | 229 | +| 3.3.29.1 General description ..... | 229 | +| 3.3.29.2 Invoking Entity (SSF)..... | 230 | +| 3.3.29.3 Responding Entity (SCF)..... | 231 | +| 3.3.30 ONoAnswer procedure ..... | 231 | +| 3.3.30.1 General description ..... | 231 | +| 3.3.30.2 Invoking Entity (SSF)..... | 232 | +| 3.3.30.3 Responding Entity (SCF)..... | 233 | +| 3.3.31 OriginationAttemptAuthorized procedure ..... | 233 | +| 3.3.31.1 General description ..... | 233 | +| 3.3.31.2 Invoking Entity (SSF)..... | 235 | +| 3.3.31.3 Responding Entity (SCF)..... | 235 | +| 3.3.32 PlayAnnouncement procedure ..... | 236 | +| 3.3.32.1 General description ..... | 236 | +| 3.3.32.2 Invoking Entity (SCF)..... | 237 | +| 3.3.32.3 Responding Entity (SRF)..... | 237 | +| 3.3.33 PromptAndCollectUserInformation procedure..... | 238 | +| 3.3.33.1 General description ..... | 238 | +| 3.3.33.2 Invoking Entity (SCF)..... | 241 | +| 3.3.33.3 Responding Entity (SRF)..... | 241 | + +| | Page | +|---------------------------------------------------------|-------------| +| 3.3.34 ReleaseCall procedure..... | 242 | +| 3.3.34.1 General description ..... | 242 | +| 3.3.34.2 Invoking Entity (SCF)..... | 242 | +| 3.3.34.3 Responding Entity (SSF) ..... | 243 | +| 3.3.35 RemoveEntry procedure ..... | 243 | +| 3.3.35.1 General description ..... | 243 | +| 3.3.35.2 Invoking Entity (SCF)..... | 243 | +| 3.3.35.3 Responding Entity (SDF)..... | 244 | +| 3.3.36 RequestCurrentStatusReport procedure..... | 244 | +| 3.3.36.1 General description ..... | 244 | +| 3.3.36.2 Invoking Entity (SCF)..... | 244 | +| 3.3.36.3 Responding Entity (SSF) ..... | 245 | +| 3.3.37 RequestFirstStatusMatchReport procedure..... | 245 | +| 3.3.37.1 General description ..... | 245 | +| 3.3.37.2 Invoking Entity (SCF)..... | 246 | +| 3.3.37.3 Responding Entity (SSF) ..... | 246 | +| 3.3.38 RequestNotificationChargingEvent procedure ..... | 247 | +| 3.3.38.1 General description ..... | 247 | +| 3.3.38.2 Invoking Entity (SCF)..... | 247 | +| 3.3.38.3 Responding Entity (SSF) ..... | 247 | +| 3.3.39 RequestReportBCSMEEvent procedure..... | 248 | +| 3.3.39.1 General description ..... | 248 | +| 3.3.39.2 Invoking Entity (SCF)..... | 249 | +| 3.3.39.3 Responding Entity (SSF) ..... | 250 | +| 3.3.40 ResetTimer procedure..... | 250 | +| 3.3.40.1 General description ..... | 250 | +| 3.3.40.2 Invoking Entity (SCF)..... | 250 | +| 3.3.40.3 Responding Entity (SSF) ..... | 250 | +| 3.3.41 RouteSelectFailure Procedure..... | 251 | +| 3.3.41.1 General description ..... | 251 | +| 3.3.41.2 Invoking Entity (SSF)..... | 253 | +| 3.3.41.3 Responding Entity (SCF)..... | 253 | +| 3.3.42 Search procedure..... | 254 | +| 3.3.42.1 General description ..... | 254 | +| 3.3.42.2 Invoking Entity (SCF)..... | 254 | +| 3.3.42.3 Responding Entity (SDF)..... | 254 | +| 3.3.43 SelectFacility procedure..... | 255 | +| 3.3.43.1 General description ..... | 255 | +| 3.3.43.2 Invoking Entity (SCF)..... | 255 | +| 3.3.43.3 Responding Entity (SSF) ..... | 256 | +| 3.3.44 SelectRoute procedure ..... | 256 | +| 3.3.44.1 General description ..... | 256 | +| 3.3.44.2 Invoking Entity (SCF)..... | 257 | +| 3.3.44.3 Responding Entity (SSF) ..... | 257 | +| 3.3.45 SendChargingInformation procedure..... | 259 | +| 3.3.45.1 General description ..... | 259 | +| 3.3.45.2 Invoking Entity (SCF)..... | 259 | +| 3.3.45.3 Responding Entity (SSF) ..... | 259 | +| 3.3.46 ServiceFilteringResponse procedure..... | 260 | +| 3.3.46.1 General description ..... | 260 | +| 3.3.46.2 Invoking Entity (SSF)..... | 261 | +| 3.3.46.3 Responding Entity (SCF)..... | 261 | +| 3.3.47 SpecializedResourceReport procedure..... | 262 | +| 3.3.47.1 General description ..... | 262 | +| 3.3.47.2 Invoking Entity (SRF)..... | 262 | +| 3.3.47.3 Responding Entity (SCF)..... | 262 | + +| | Page | +|-------------------------------------------------------|-------------| +| 3.3.48 StatusReport procedure ..... | 263 | +| 3.3.48.1 General description ..... | 263 | +| 3.3.48.2 Invoking Entity (SSF) ..... | 263 | +| 3.3.48.3 Responding Entity (SCF) ..... | 263 | +| 3.3.49 TAnswer procedure..... | 264 | +| 3.3.49.1 General description ..... | 264 | +| 3.3.49.2 Invoking Entity (SSF) ..... | 264 | +| 3.3.49.3 Responding Entity (SCF) ..... | 265 | +| 3.3.50 TBusy procedure ..... | 265 | +| 3.3.50.1 General description ..... | 265 | +| 3.3.50.2 Invoking Entity (SSF) ..... | 267 | +| 3.3.50.3 Responding Entity (SCF) ..... | 267 | +| 3.3.51 TDisconnect procedure ..... | 268 | +| 3.3.51.1 General description ..... | 268 | +| 3.3.51.2 Invoking Entity (SSF) ..... | 269 | +| 3.3.51.3 Responding Entity (SCF) ..... | 270 | +| 3.3.52 TermAttemptAuthorized procedure ..... | 270 | +| 3.3.52.1 General description ..... | 270 | +| 3.3.52.2 Invoking Entity (SSF) ..... | 271 | +| 3.3.52.3 Responding Entity (SCF) ..... | 271 | +| 3.3.53 TNoAnswer procedure..... | 272 | +| 3.3.53.1 General description ..... | 272 | +| 3.3.53.2 Invoking Entity (SSF) ..... | 272 | +| 3.3.53.3 Responding Entity (SCF) ..... | 273 | +| 3.3.54 Unbind procedure ..... | 273 | +| 3.3.54.1 General description ..... | 273 | +| 3.3.54.2 Invoking Entity (SCF) ..... | 274 | +| 3.3.54.3 Responding Entity (SDF)..... | 274 | +| 3.3.55 RequestEveryStatusChangeReport procedure ..... | 274 | +| 3.3.55.1 General description ..... | 274 | +| 3.3.55.2 Invoking Entity (SCF)..... | 274 | +| 3.3.55.3 Responding Entity (SSF) ..... | 275 | +| 3.4 Services assumed from TCAP ..... | 275 | +| 3.4.1 Normal procedures..... | 276 | +| 3.4.1.1 SSF-to-SCF messages ..... | 276 | +| 3.4.1.2 SCF-to-SSF messages ..... | 278 | +| 3.4.1.3 SCF-to/from-SRF messages..... | 280 | +| 3.4.2 Abnormal procedures..... | 280 | +| 3.4.2.1 SCF-to-SSF/SRF messages..... | 281 | +| 3.4.2.2 SSF/SRF-to-SCF messages..... | 282 | +| 3.4.3 Dialogue establishment..... | 282 | +| 3.4.3.1 Sending of a TC-BEGIN request primitive..... | 282 | +| 3.4.3.2 Receipt of a TC-BEGIN indication..... | 283 | +| 3.4.3.3 Receipt of the first TC-CONTINUE ind..... | 283 | +| 3.4.3.4 Receipt of a TC-END ind..... | 283 | +| 3.4.3.5 Receipt of a TC-U-ABORT ind ..... | 283 | +| 3.4.3.6 Receipt of a TC-P-ABORT ind ..... | 283 | +| 3.4.4 Dialogue continuation ..... | 283 | +| 3.4.4.1 Sending entity ..... | 283 | +| 3.4.4.2 Receiving entity ..... | 284 | +| 3.4.5 Dialogue termination..... | 284 | +| 3.4.5.1 Sending of TC-END request..... | 284 | +| 3.4.5.2 Receipt of a TC-END indication..... | 284 | +| 3.4.6 User Abort..... | 284 | +| 3.4.6.1 Sending of TC-U-ABORT request ..... | 284 | +| 3.4.6.2 Receipt of a TC-U-ABORT indication ..... | 284 | + +| | Page | | +|------------------------------------------------------------------------------|-------------------------------------------------------------|-----| +| 3.4.7 | Provider Abort ..... | 284 | +| 3.4.7.1 | Receipt of a TC-P-ABORT indication ..... | 284 | +| 3.4.8 | Procedures for INAP operations ..... | 285 | +| 3.4.8.1 | Operation invocation ..... | 285 | +| 3.4.8.2 | Operation invocation receipt ..... | 285 | +| 3.4.8.3 | Operation Response ..... | 285 | +| 3.4.8.4 | Receipt of a response ..... | 285 | +| 3.4.8.5 | Other events ..... | 286 | +| 3.4.9 | Mapping on to TC services ..... | 287 | +| 3.4.9.1 | Dialogue control ..... | 287 | +| 3.4.9.2 | Operation procedures ..... | 288 | +| Annex A – INAP SDL Diagrams ..... | | 289 | +| A.1 | Introduction ..... | 289 | +| A.2 | SDL diagrams ..... | 289 | +| Annex B – Description of the SCSM (SDF-related states) and of the SDSM ..... | | 342 | +| B.1 | Description of the Process SCSM ..... | 342 | +| B.1.1 | State 1 – "Idle" ..... | 342 | +| B.1.1.1 | Normal procedures ..... | 342 | +| B.1.1.2 | Exceptional procedures ..... | 342 | +| B.1.2 | State 2 – "Wait for subsequent requests" ..... | 342 | +| B.1.2.1 | Normal procedures ..... | 342 | +| B.1.2.2 | Exceptional procedures ..... | 343 | +| B.1.3 | State 3 – "Wait for Bind result" ..... | 344 | +| B.1.3.1 | Normal procedures ..... | 344 | +| B.1.3.2 | Exceptional procedures ..... | 344 | +| B.1.4 | State 4 – "SDF Bound" ..... | 344 | +| B.1.4.1 | Normal procedures ..... | 344 | +| B.1.4.2 | Exceptional procedures ..... | 345 | +| B.2 | Description of the Process SDSM ..... | 345 | +| B.2.1 | State 1 – "Idle" ..... | 345 | +| B.2.1.1 | Normal procedures ..... | 345 | +| B.2.1.2 | Exceptional procedures ..... | 345 | +| B.2.2 | State 2 – "Bind Pending" ..... | 345 | +| B.2.2.1 | Normal procedures ..... | 345 | +| B.2.2.2 | Exceptional procedures ..... | 348 | +| B.2.3 | State 3 – "SCF Bound" ..... | 349 | +| B.2.3.1 | Normal procedures ..... | 349 | +| B.2.3.2 | Exceptional procedures ..... | 349 | +| Appendix I – Service data modelling ..... | | 352 | +| I.1 | Review of need for Service data modelling ..... | 352 | +| I.1.1 | General modelling issues ..... | 353 | +| I.1.2 | Service modelling – Defining the information required ..... | 353 | +| I.2 | Guidelines for building Service Data Models ..... | 354 | +| I.2.1 | Selection of ATTRIBUTEs ..... | 354 | +| I.2.1.1 | ATTRIBUTE Type definitions ..... | 355 | +| I.2.1.2 | Defining Permitted Values ..... | 355 | +| I.2.1.3 | Defining Default Values ..... | 356 | +| I.2.1.4 | Defining MAX Attribute Values ..... | 356 | +| I.2.1.5 | Defining Attribute Lifetimes ..... | 356 | +| I.2.1.6 | Definition of MATCHING-RULES ..... | 356 | +| I.2.1.7 | Assigning the ATTRIBUTE Object Identifiers ..... | 356 | +| I.2.2 | Selection of OBJECT-CLASSs ..... | 357 | +| I.2.2.1 | Defining the OBJECT-CLASS ..... | 357 | +| I.2.2.2 | Selecting the RDN (NAME-FORM) ..... | 357 | +| I.2.2.3 | Assigning the OBJECT-CLASS Object Identifiers ..... | 357 | +| I.2.3 | Defining the DIT ..... | 357 | +| I.2.3.1 | Defining the Object Hierarchy (STRUCTURE-RULES) ..... | 357 | +| I.2.3.2 | Defining alternative naming paths (Aliases) ..... | 359 | +| I.2.3.3 | Defining MAX number of subordinate Entries ..... | 359 | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----| +| I.3 | Example Service (UPT Like Service)..... | 359 | +| I.3.1 | Example Service description..... | 359 | +| I.3.1.1 | Service Feature – Incall..... | 359 | +| I.3.1.2 | Service Feature – Incall Registration ..... | 360 | +| I.3.1.3 | Service Feature – Incall Screening..... | 361 | +| I.3.1.4 | Service Feature – Outcall..... | 361 | +| I.3.1.5 | Service Feature – Outcall screening by location..... | 361 | +| I.3.1.6 | General Service Information ..... | 362 | +| I.3.2 | Example Service data modelling..... | 362 | +| I.3.2.1 | Selection of Attributes ..... | 362 | +| I.3.2.2 | Selection of Object Classes..... | 367 | +| I.3.2.3 | Designing the Service DIT..... | 368 | +| I.3.2.4 | Assigning Access control..... | 370 | +| I.4 | Defining Contexts..... | 371 | +| I.4.1 | Numerical Index Attribute Value Context ..... | 372 | +| Appendix II – Aspects of the intelligent network interface identified as “For Further Study” (FFS) relative to CS-1 ..... | | 372 | +| II.1 | General..... | 372 | +| II.1.1 | General consideration ..... | 372 | +| II.1.2 | Relationship to other appendices of the Q.1200-Series Recommendations..... | 372 | +| II.1.3 | Format of Document ..... | 372 | +| II.2 | Operations..... | 372 | +| II.2.1 | Consideration applicable to all operations in this appendix..... | 372 | +| II.2.2 | Add party operation ..... | 373 | +| II.2.2.1 | Consideration ..... | 373 | +| II.2.2.2 | Description..... | 373 | +| II.2.3 | Attach operation..... | 373 | +| II.2.3.1 | Consideration ..... | 373 | +| II.2.3.2 | Description..... | 373 | +| II.2.4 | Change parties operation..... | 373 | +| II.2.4.1 | Description..... | 373 | +| II.2.5 | Detach operation ..... | 373 | +| II.2.5.1 | Consideration ..... | 373 | +| II.2.5.2 | Description..... | 373 | +| II.2.6 | Hold call party connection operation ..... | 373 | +| II.2.6.1 | Description..... | 373 | +| II.2.7 | Initiate call attempt operation (for case of more than 1 party)..... | 374 | +| II.2.7.1 | Consideration ..... | 374 | +| II.2.7.2 | Description..... | 374 | +| II.2.8 | Reconnect operation..... | 374 | +| II.2.8.1 | Description..... | 374 | +| II.2.9 | Release call party connection operation..... | 374 | +| II.2.9.1 | Consideration ..... | 374 | +| II.2.9.2 | Description..... | 374 | +| II.3 | Parameters..... | 374 | +| II.3.1 | Considerations applicable to all parameters in this appendix ..... | 374 | +| II.3.2 | Leg Id created parameter (from Analyse information operation) ..... | 374 | +| II.3.2.1 | Description..... | 374 | +| II.3.3 | Leg Id created parameter (from connect operation)..... | 374 | +| II.3.3.1 | Description..... | 374 | + +| | Page | +|-----------------------------------------------------------------------------|-------------| +| II.3.4 Leg Id created parameter (from initiate call attempt operation)..... | 375 | +| II.3.4.1 Description..... | 375 | +| II.3.5 Leg Id created parameter (from select facility operation)..... | 375 | +| II.3.5.1 Description..... | 375 | +| II.3.6 Leg Id created parameter (from select route operation)..... | 375 | +| II.3.6.1 Description..... | 375 | +| II.3.7 Leg 1 parameter (from initial DP operation)..... | 375 | +| II.3.7.1 Description..... | 375 | +| II.3.8 Leg 2 Parameter (from initial DP operation) ..... | 375 | +| II.3.8.1 Description..... | 375 | +| II.3.9 Call Id Parameter ..... | 375 | +| II.3.9.1 Description..... | 375 | +| II.4 ASN.1 module of operations and parameters ..... | 375 | +| II.4.1 Abstract syntax of the IN CS-1 application protocol – Appendix ..... | 375 | +| II.5 Procedures ..... | 380 | +| Appendix III – Expanded ASN.1 coding ..... | 380 | + +## **SUMMARY** + +This Recommendation defines the intelligent network application protocol for the support of the capabilities required by the CS-1 target services over the CS-1 interfaces (SSF-SCF, SCF-SDF and SCF-SRF) as defined in Recommendation Q.1211. It defines some of the possible protocol stack scenarios, the operations which flow between the entities and the procedures to be followed at each functional entity. + +Revisions to this Recommendation provide: details on operations procedures, details on services assumed from underlying protocol layers, extensions to ensure applicability in multiple administration networks, a new SCF-SDF interface for data administration and acquisition based upon the X.500-Series of Recommendations, and detailed error handling procedures. The intent of these revisions is to facilitate consistent multi-vendor implementations in multiple networks. + +Associated standardization work is contained in all the Q.1200-Series Recommendations (Intelligent network). + +## **INTERFACE RECOMMENDATION FOR INTELLIGENT NETWORK CS-1** + +*(Helsinki, 1993; modified 1995)* + +### **0 Introduction** + +This Recommendation defines the Intelligent Network Application Protocol, (INAP) required for support of Intelligent Network Capability Set 1. It supports interactions between the following four functional entities (FE's), as defined in the IN functional model: + +- Service Switching Function (SSF); +- Service Control Function (SCF); +- Specialized Resource Function (SRF); +- Service Data Function (SDF). + +The scope of this Recommendation is the further development of the INAP for both the Integrated Services Digital Network (ISDN) and Public Switched Telecommunications Network (PSTN). + +It is intended as a guide to implementors and network operators to ensure interworking between different manufacturers equipment for all the IN CS-1 defined interfaces (SCF-SSF, SCF-SRF and SCF-SDF) and between network operators for the internetwork interface (SCF-SDF). + +As this Recommendation is intended for the early introduction of IN in the existing ISDN/PSTN, only simple solutions are assumed for solving the service interaction problems between IN and ISDN/PSTN. + +NOTE – More sophisticated solutions for the service interactions between IN and the ISDN/PSTN environment should be studied in the scope of future versions of INAP and the ISDN/PSTN signalling standards. + +### **0.1 Normative references** + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation X.500 (1993) | ISO/IEC 9594-1:1995, *Information technology – Open Systems Interconnection – The Directory: Overview of concepts, models and services.* +- ITU-T Recommendation X.501 (1993) | ISO/IEC 9594-2:1995, *Information technology – Open Systems Interconnection – The Directory: Models.* +- ITU-T Recommendation X.509 (1993) | ISO/IEC 9594-8:1995, *Information technology – Open Systems Interconnection – The Directory: Authentication framework.* +- ITU-T Recommendation X.511 (1993) | ISO/IEC 9594-3:1995, *Information technology – Open Systems Interconnection – The Directory: Abstract service definition.* +- ITU-T Recommendation X.518 (1993) | ISO/IEC 9594-4:1995, *Information technology – Open Systems Interconnection – The Directory: Procedures for distributed operation.* +- ITU-T Recommendation X.519 (1993) | ISO/IEC 9594-5:1995, *Information technology – Open Systems Interconnection – The Directory: Protocol specifications.* +- ITU-T Recommendation X.680 (1994) | ISO/IEC 8824-1:1995, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation.* + +- ITU-T Recommendation X.681 (1994) | ISO/IEC 8824-2:1995, *Information technology – Abstract Syntax Notation One (ASN.1): Information object specification.* +- ITU-T Recommendation X.682 (1994) | ISO/IEC 8824-3:1995, *Information technology – Abstract Syntax Notation One (ASN.1): Constraint specification.* +- ITU-T Recommendation X.683 (1994) | ISO/IEC 8824-4:1995, *Information technology – Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications.* +- ITU-T Recommendation X.690 (1994) | ISO/IEC 8825-1:1995, *Information technology – ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER).* +- ITU-T Recommendation X.880 (1994) | ISO/IEC 13712-1:1995, *Information technology – Remote Operations: Concepts, model and notation.* +- CCITT Recommendation Q.29 (1988), *Causes of noise and ways of reducing noise in the telephone exchange.* +- ITU-T Recommendation Q.711 (1993), *Signalling System No. 7 – Functional description of the Signalling connection control part: Service definition.* +- ITU-T Recommendation Q.762 (1993) – *General function of messages and signals of the ISDN User Part of Signalling System No. 7.* +- ITU-T Recommendation Q.763 (1993), *Formats and codes of the ISDN User Part of Signalling System No. 7.* +- ITU-T Recommendation Q.771 (1993), *Signalling System No. 7 – Functional description of transaction capabilities.* +- ITU-T Recommendation Q.772 (1993), *Signalling System No. 7 – Transaction capabilities information elements definitions.* +- ITU-T Recommendation Q.773 (1993), *Signalling System No. 7 – SCCP formats and codes.* +- ITU-T Recommendation Q.774 (1993), *Signalling System No. 7 – Transaction capabilities procedures.* +- ITU-T Recommendation Q.775 (1993), *Signalling System No. 7 – Guidelines for using transaction capabilities.* +- ITU-T Recommendation Q.931 (1993), *Digital Subscriber Signalling System No. 1 (DSS 1) – ISDN user-network interface layer 3 specification for basic call control.* +- ITU-T Recommendation Q.932 (1993), *Digital Subscriber Signalling System No. 1 (DSS 1) – Generic procedures for the control of ISDN supplementary services.* +- ITU-T Recommendation Q.1290 (1995), *Glossary of terms used in the definition of intelligent networks.* + +## 0.2 Definition methodology + +The definition of the protocol can be split into three clauses: + +- the definition of the SACF/MACF rules for the protocol (clause 1); +- the definition of the operations transferred between entities (clause 2); +- the definition of the actions taken at each entity (clause 3). + +The SACF/MACF rules are defined in prose. The operation definitions are in Abstract Syntax Notation 1 (ASN.1, see Recommendations X.208 and X.680), and the actions are defined in terms of state transition diagrams. Further guidance on the actions to be performed on receipt of an operation can be gained from clause 2 and from the relevant information flow in clause 6/Q.1214 (see 0.6 for the relationship between the information flows and the operations). + +The INAP is a ROSE user protocol (see Recommendations X.219 and 229). The ROSE protocol is contained within the component sublayer of TCAP (see Recommendations Q.771 to 775) and DSS 1 (see Recommendation Q.932). At + +present the ROSE APDU's (Application protocol data units) 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 PDU's is the Basic Encoding Rules (see Recommendation X.209). + +### 0.3 Example physical scenarios + +The protocol will support any mapping of functional to Physical Entities (PE's). It is the responsibility of network operators and equipment manufacturers to decide how to co-locate FE's to the best possible advantage as this may vary between manufacturers and between network operators. Therefore the protocol is defined assuming maximum distribution (i.e. one PE per FE). + +The figures depicted in this subclause show how INAP would be supported in an SS No. 7 network environment. This does not imply that only SS No. 7 may be used as the network protocol to support INAP. + +For each physical scenario, the typical SRF control procedures to be applied are shown in 3.1.3.5. + +The interface between remotely located SCF and SDF will be INAP using TCAP which in turn, uses the services of the connectionless SCCP and MTP (see Figure 1). The SDF is responsible for any interworking to other protocols to access other types of networks. + +![Diagram showing the physical interface between SCP and SDP. The SCP side includes SCF, MACF, ASE(s) (SCF-SSF), TCAP, SCCP, and MTP layers. The SDP side includes SDF, ASE(s) (SCF-SDF), TCAP, SCCP, and MTP layers. Both sides connect to an SS No. 7 network via links. The SCP side also connects to an SSP.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +The diagram illustrates the protocol stack and physical connections for an SCP (Service Control Point) and an SDP (Service Data Point). +**SCP Stack:** At the top is the SCF (Service Control Function). Below it is the MACF (Management and Control Function). The MACF connects to two parallel paths. Each path contains a vertical stack of four boxes labeled S, A, C, and F. To the right of the 'A' and 'C' boxes in each path is a box labeled 'ASE(s) (SCF-SSF)'. Below the 'F' box in each path is a box labeled 'TCAP'. Below each 'TCAP' box is a box labeled 'SCCP'. Below each 'SCCP' box is a box labeled 'MTP'. Both 'MTP' boxes connect to a common horizontal line representing the 'SS No. 7 link'. From this link, one path goes left to a box labeled 'To SSP', and the other path goes right to a box labeled 'SS No. 7 network'. +**SDP Stack:** At the top is the SDF (Service Data Function). Below it is a vertical stack of four boxes labeled S, A, C, and F. To the right of the 'A' and 'C' boxes is a box labeled 'ASE(s) (SCF-SDF)'. Below the 'F' box is a box labeled 'TCAP'. Below 'TCAP' is a box labeled 'SCCP'. Below 'SCCP' is a box labeled 'MTP'. The 'MTP' box connects to the same 'SS No. 7 link' as the SCP's 'MTP' boxes. + +Diagram showing the physical interface between SCP and SDP. The SCP side includes SCF, MACF, ASE(s) (SCF-SSF), TCAP, SCCP, and MTP layers. The SDP side includes SDF, ASE(s) (SCF-SDF), TCAP, SCCP, and MTP layers. Both sides connect to an SS No. 7 network via links. The SCP side also connects to an SSP. + +T1147150-92/d01 + +FIGURE 1/Q.1218 +**Physical interface between SCP and SDP** + +When TCAP appears in one of the following figures, it shall be understood as representing the TCAP functionalities associated with a single dialogue and transaction (as opposed to a TCAP entity). + +If segmentation and re-assembly of INAP messages is required on the SCF-to-SDF interface (and on other interfaces, if needed) due to the length of messages, the segmentation and re-assembly procedure for SCCP connectionless messages, as specified in Q.714, should be used. + +A number of example scenarios have been identified for support of the SCF, SSF and SRF functional entities as physical entities. These are illustrated as Figures 2 to 6. Each example is characterized by: + +- i) the method to support SCF-SRF relationship; and +- ii) the type of signalling system between SSF and SRF. + +![Diagram showing the example architecture for supporting SRF, Case 1. It illustrates three main entities: SSP, IP, and SCP, connected via SS No. 7 links. The SSP contains SSF and SCF, MACF, SACC, ASE(s) (SCF-SSF), TCAP, ISUP (Notes 1 and 2), SCCP, and MTP. The IP contains SRF, MACF, ISUP (Notes 1 and 2), SACC, ASE(s) (SCF-SRF), TCAP, SCCP, and MTP. The SCP contains SCF, MACF, SACC, ASE(s) (SCF-SRF), TCAP, SCCP, and MTP. The SSP and IP are connected via an ISDN/PSTN link. The IP and SCP are connected via an SS No. 7 link. All three entities are connected to a common SS No. 7 network.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Diagram showing the example architecture for supporting SRF, Case 1. It illustrates three main entities: SSP, IP, and SCP, connected via SS No. 7 links. The SSP contains SSF and SCF, MACF, SACC, ASE(s) (SCF-SSF), TCAP, ISUP (Notes 1 and 2), SCCP, and MTP. The IP contains SRF, MACF, ISUP (Notes 1 and 2), SACC, ASE(s) (SCF-SRF), TCAP, SCCP, and MTP. The SCP contains SCF, MACF, SACC, ASE(s) (SCF-SRF), TCAP, SCCP, and MTP. The SSP and IP are connected via an ISDN/PSTN link. The IP and SCP are connected via an SS No. 7 link. All three entities are connected to a common SS No. 7 network. + +T1147160-92/d02 + +NOTES + +- 1 Transfer of correlation information needs to be supported. This may be supported in ISUP without introducing a new ISUP parameter. +- 2 Other signalling systems may be used. + +FIGURE 2/Q.1218 +**Example architecture for supporting SRF, Case 1** +**(SRF in IP connected to SSP and accessed by SCP** +**through direct SS No. 7 connection)** + +![Diagram showing the architecture for supporting SRF, Case 2. It consists of three main entities: SSP, IP, and SCP. The SSP contains SSF and CCF, MACF, SACC (with ASE(s) (SCF-SRF+ SSF) and TCAP), SCCP, and MTP. The IP contains SRF and SACC (with ASE(s) (SCF-SRF) and ROSE). The SCP contains SCF, MACF, SACC (with ASE(s) (SCF-SSF) and (SCF-SRF) and TCAP), SCCP, and MTP. Connections include a B-channel between SSP and IP, a D-channel between SSP and the SS No. 7 network, and an SS No. 7 link between the IP and the SS No. 7 network. Notes indicate that info flows between SCF and SRF are supported by the ROSE entity, and the relay function is provided by MACF or an application process at the SSP.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Diagram showing the architecture for supporting SRF, Case 2. It consists of three main entities: SSP, IP, and SCP. The SSP contains SSF and CCF, MACF, SACC (with ASE(s) (SCF-SRF+ SSF) and TCAP), SCCP, and MTP. The IP contains SRF and SACC (with ASE(s) (SCF-SRF) and ROSE). The SCP contains SCF, MACF, SACC (with ASE(s) (SCF-SSF) and (SCF-SRF) and TCAP), SCCP, and MTP. Connections include a B-channel between SSP and IP, a D-channel between SSP and the SS No. 7 network, and an SS No. 7 link between the IP and the SS No. 7 network. Notes indicate that info flows between SCF and SRF are supported by the ROSE entity, and the relay function is provided by MACF or an application process at the SSP. + +T1146670-92/d03 + +NOTES + +- 1 Info flows between SCF and SRF are supported by this (ROSE) entity. +- 2 Relay function is provided either by MACF or by application process at SSP. + +FIGURE 3/Q.1218 +**Example architecture for supporting SRF, Case 2 + (SRF in IP connected to SSP and accessed by SCP + through D-channel via SSP)** + +![Diagram showing the architecture for supporting SRF, Case 3 (SRF in SSP and accessed via AP of SSP). It illustrates the internal components of an SSP and an SCP, their connection via an SS No. 7 link, and the overall SS No. 7 network structure.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph TD + subgraph SSP + A1[SSF, SRF and CCF] --- B1[SACF] + subgraph SSP_Stack + B1 --- C1[ASEs SCF-SRF] + B1 --- D1[ASEs SSF-SCF] + B1 --- E1[TCAP] + end + E1 --- F1[SCCP] + F1 --- G1[MTP] + G1 --- H1((SS No. 7 link)) + end + + subgraph SCP + A2[SCF] --- B2[SACF] + subgraph SCP_Stack + B2 --- C2[ASEs SCF-SRF] + B2 --- D2[ASEs SSF-SRF] + B2 --- E2[TCAP] + end + E2 --- F2[SCCP] + F2 --- G2[MTP] + G2 --- H2((SS No. 7 link)) + end + + H1 --- I[SS No. 7 network] + H2 --- I + +``` + +T1146680-92/d04 + +Diagram showing the architecture for supporting SRF, Case 3 (SRF in SSP and accessed via AP of SSP). It illustrates the internal components of an SSP and an SCP, their connection via an SS No. 7 link, and the overall SS No. 7 network structure. + +FIGURE 4/Q.1218 +**Example architecture for supporting SRF, Case 3 +(SRF in SSP and accessed via AP of SSP)** + +![Diagram showing the architecture for supporting SRF, Case 4. It consists of three main entities: SSP, IP, and SCP. The SSP contains SSF and CCF, MACF (Note 2), a stack of S, A, C, F layers with ASE(s) (SCF-SRF+ SSF) and TCAP, ISUP (Notes 1, 3 and 4), SCCP, and MTP. The IP contains SRF, ISUP (Notes 1, 3 and 4), and MTP. The SCP contains SCF, a stack of S, A, C, F layers with ASE(s) (SCF-SSF) and (SCF-SRF) and TCAP, SCCP, and MTP. The SSP and IP are connected by an ISDN/PSTN link. All three entities are connected to a common SS No. 7 network via their respective MTP layers and SS No. 7 links. A telephone icon is shown on the left side of the SSP.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Diagram showing the architecture for supporting SRF, Case 4. It consists of three main entities: SSP, IP, and SCP. The SSP contains SSF and CCF, MACF (Note 2), a stack of S, A, C, F layers with ASE(s) (SCF-SRF+ SSF) and TCAP, ISUP (Notes 1, 3 and 4), SCCP, and MTP. The IP contains SRF, ISUP (Notes 1, 3 and 4), and MTP. The SCP contains SCF, a stack of S, A, C, F layers with ASE(s) (SCF-SSF) and (SCF-SRF) and TCAP, SCCP, and MTP. The SSP and IP are connected by an ISDN/PSTN link. All three entities are connected to a common SS No. 7 network via their respective MTP layers and SS No. 7 links. A telephone icon is shown on the left side of the SSP. + +T1146690-92/d05 + +NOTES + +- 1 Info flows between SCF and SRF as well as connection control are directly supported by ISUP. +- 2 Relay function is provided either by MACF or by application process at SSP. +- 3 Assumes that ISUP provides a means to transport ROSE information. +- 4 Other signalling systems may be used. + +FIGURE 5/Q.1218 +**Example architecture for supporting SRF, Case 4 + (SRF in IP connected to SSP and accessed by SCP + through ISUP via SSP)** + +![Diagram showing the example architecture for supporting SRF, Case 5. It consists of three main entities: SSP, IP, and SCP. The SSP contains SSF and CCF, MACF, SACC F (with ASE(s) (SCF-SSF) and TCAP), SCCP, MTP, and a B-ch. The IP contains SRF, MACF, SACC F (with ASE(s) (SCF-SRF) and TCAP), SCCP, MTP, and a B-ch. The SCP contains SCF, MACF, SACC F (with ASE(s) (SCF-SRF) and TCAP), SCCP, and MTP. All three entities are connected to a common SS No. 7 network via their respective links. The SSP and IP are also connected via a D-channel (Notes 1 and 2).](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram illustrates the architecture for supporting SRF, Case 5. It features three main components: SSP, IP, and SCP, all connected to a common SS No. 7 network. + +- SSP (Service Switching Point):** Contains SSF and CCF, MACF, SACC F (with ASE(s) (SCF-SSF) and TCAP), SCCP, MTP, and a B-ch. It is connected to the SS No. 7 network via an SS No. 7 link and to the IP via a D-channel (Notes 1 and 2). +- IP (Interworking Point):** Contains SRF, MACF, SACC F (with ASE(s) (SCF-SRF) and TCAP), SCCP, MTP, and a B-ch. It is connected to the SS No. 7 network via an SS No. 7 link and to the SSP via a D-channel (Notes 1 and 2). +- SCP (Service Control Point):** Contains SCF, MACF, SACC F (with ASE(s) (SCF-SRF) and TCAP), SCCP, and MTP. It is connected to the SS No. 7 network via an SS No. 7 link. + +The SSP and IP are also connected via a D-channel (Notes 1 and 2). + +Diagram showing the example architecture for supporting SRF, Case 5. It consists of three main entities: SSP, IP, and SCP. The SSP contains SSF and CCF, MACF, SACC F (with ASE(s) (SCF-SSF) and TCAP), SCCP, MTP, and a B-ch. The IP contains SRF, MACF, SACC F (with ASE(s) (SCF-SRF) and TCAP), SCCP, MTP, and a B-ch. The SCP contains SCF, MACF, SACC F (with ASE(s) (SCF-SRF) and TCAP), SCCP, and MTP. All three entities are connected to a common SS No. 7 network via their respective links. The SSP and IP are also connected via a D-channel (Notes 1 and 2). + +T1146700-92/d06 + +NOTES + +- 1 Transfer of correlation information needs to be supported. +- 2 Other signalling systems may be used. + +FIGURE 6/Q.1218 +**Example architecture for supporting SRF, Case 5 + (SRF in IP connected to SCP and SSP and accessed + via both SS No. 7 and D-channel respectively)** + +Table 1 summarizes the selection of features for each figure. + +TABLE 1/Q.1218 + +| Type of signalling system between SSF and SRF | Method to support SCF-SRF relationship | | +|-----------------------------------------------|----------------------------------------------------------------------|------------------------| +| | Direct TCAP link | Relay via SSP | +| ISUP | Figure 2 a) | Figure 5 d) | +| DSS 1 | Figure 6 e) | Figure 3 b) | +| Implementation dependent | As Figures 2 or 6 but with implementation dependent SCP-IP interface | Figure 4 c) | + +Additional information related to each figure: + +- a) Figure 2: All associations are supported by SS No. 7, either TCAP or ISUP. In this case the IP is one of the network nodes. +- b) Figure 3: IP can be accessed by DSS 1 only. The IP can be a physical entity residing outside the network. +- c) Figure 4: SSP supports both CCF/SSF and SRF. The handling of SRF by SCF could be the same as the Figure 3. +- d) Figure 5: IP can be accessed by ISUP only. The handling of SRF by SCF could be the same as that of Figure 3. +- e) Figure 6: The handling of SRF by SCF could be the same as that of Figure 2. Other types of signalling systems could be used. + +## 0.4 INAP protocol architecture + +Many of the terms used in this clause are based on the OSI application layer structure as defined in ISO IS-9545. + +The INAP protocol architecture can be illustrated as shown in Figure 7. + +A physical entity has either single interactions (Case a) or multiple coordinated interactions (Case b) with other physical entities. + +In case a, SACF provides a coordination function in using ASE's, which includes the ordering of operations supported by ASE(s), (based on the order of received primitives). The SAO represents the SACF plus a set of ASE's to be used over a single interaction between a pair of PE's. + +In Case b, MACF provides a coordinating function among several SAO's, each of which interacts with an SAO in a remote PE. + +Each ASE supports one or more operations. Description of each operation is tied with the action of corresponding FE modelling (see Recommendation Q.1214 and clause 3 of this Recommendation). Each operation is specified using the OPERATION macro described in Figure 8 except for the SCF-to-SDF interface, which is described using the CLASS notation. + +The use of the application context negotiation mechanism [as defined in the Q.770-Series (Transaction capabilities application part)] allows the two communicating entities to identify exactly what their capabilities are and also what the capabilities required on the interface should be. This should be used to allow evolution through Intelligent Network capability sets. + +If the indication of a specific application context is not supported by a pair of communicating FE's, some mechanism to pre-arrange the context must be supported. + +![Diagram showing INAP protocol architecture for multiple co-ordinated interactions and single interaction. Both paths show layers: Application process, MACF/SAO (containing SACS and TCAP), SCCP, and MTP. The multiple interactions path has two parallel SACS units.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +T1146710-92/d07 + +Diagram showing INAP protocol architecture for multiple co-ordinated interactions and single interaction. Both paths show layers: Application process, MACF/SAO (containing SACS and TCAP), SCCP, and MTP. The multiple interactions path has two parallel SACS units. + +SACF Single association control function + MACF Multiple association control function + SAO Single association object + ASE Application service element + INAP Intelligent network application protocol + +NOTE – INAP is the collection of specifications of all in ASE's. + +FIGURE 7/Q.1218 +**INAP protocol architecture** + +![Diagram showing INAP user ASE's and TCAP ASE. The INAP user ASE contains operation descriptions like OPERATION, ARGUMENT, RESULT, etc. The TCAP ASE contains Component and Transaction sub-layers. Arrows show data flow to peer for both ASE types.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +T1137290-91/d08 + +Diagram showing INAP user ASE's and TCAP ASE. The INAP user ASE contains operation descriptions like OPERATION, ARGUMENT, RESULT, etc. The TCAP ASE contains Component and Transaction sub-layers. Arrows show data flow to peer for both ASE types. + +FIGURE 8/Q.1218 +**Operation description** + +#### 0.4.1 INAP signalling congestion control for Signalling System No. 7 + +The same type of procedure shall apply as defined for ISDN User Part signalling congestion control. The INAP procedures for signalling congestion control shall as far as possible be aligned with the ISDN User Part signalling congestion control procedures as specified (see D.2.11/Q.767), i.e. on receipt of N-PCSTATE indication primitive with the information "signalling point congested" from SCCP, the INAP shall reduce the traffic load (e.g. InitialDP, AnalyzedInformation, or InitiateCallAttempts) into the affected direction in several steps. + +The above procedure may only apply to traffic which uses MTP Point Code addressing in the affected direction. + +#### 0.5 INAP addressing + +SCCP global title and MTP point code addressing [see Q.710-Series (Signalling connection control part) and Q.700-Series (Message transfer part)] ensure that PDU's reach their physical destination (i.e. the correct point code) regardless of which network it is in. + +Within a node, it is the choice of the network operator/implementor as to which SSN or SSNs are assigned to INAP. + +Regardless of the above, any addressing scheme supported by the SCCP may be used. + +#### 0.6 Relationship between Recommendation Q.1214 and this Recommendation + +The following is a complete list of information flows. These map one-to-one with operations except where indicated. + +| Rec. Q.1214
Reference
| Information Flow | Operation | +|----------------------------------|------------------------------|----------------------------------| +| 6.4.2.1 | Activate Service Filtering | Same | +| 6.4.2.2 | Activity Test | Same | +| 6.4.2.3 | Activity Test Response | Return Result from ActivityTest | +| 6.4.2.4 | Analysed Information | Same, InitialDP, EventReportBCSM | +| 6.4.2.5 | Analyse Information | Same, Connect | +| 6.4.2.6 | Apply Charging | Same | +| 6.4.2.7 | Apply Charging Report | Same | +| 6.4.2.8 | Assist Request Instructions | Same | +| 6.4.2.9 | Call Gap | Same | +| 6.4.2.10 | Call Information Report | Same | +| 6.4.2.11 | Call Information Request | Same | +| 6.4.2.13 | Cancel Status Report Request | Same | +| 6.4.2.14 | Collected Information | Same, InitialDP, EventReportBCSM | +| 6.4.2.15 | Collect Information | Same | +| 6.4.2.16 | Connect | Same | +| 6.4.2.17 | Connect to Resource | Same | + +| Rec. Q.1214
Reference
| Information Flow | Operation | +|----------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------| +| 6.4.2.18 | Continue | Same | +| 6.4.2.19 | Disconnect Forward Connection | Same | +| 6.4.2.20 | Establish Temporary Connection | Same | +| 6.4.2.21 | Event Notification Charging | Same | +| 6.4.2.22 | Event Report BCSM | Same | +| 6.4.2.23 | Furnish Charging Information | Same | +| 6.4.2.24 | Hold call in network | Same, ResetTimer and
FurnishChargingInformation | +| 6.4.2.25 | Initial DP | Same | +| 6.4.2.26 | Initiate Call Attempt | Same | +| 6.4.2.27 | OAnswer | Same, InitialDP, EventReportBCSM | +| 6.4.2.28 | OCalledPartyBusy | Same, InitialDP, EventReportBCSM | +| 6.4.2.29 | ODisconnect | Same, InitialDP, EventReportBCSM | +| 6.4.2.30 | OMidCall | Same, InitialDP, EventReportBCSM | +| 6.4.2.31 | ONo_Answer | Same, InitialDP, EventReportBCSM | +| 6.4.2.32 | Origination Attempt Authorized | Same, InitialDP | +| 6.4.2.33 | Release Call | Same | +| 6.4.2.34 | Request Notification Charging Event | Same | +| 6.4.2.35 | Request Report BCSM Event | Same | +| 6.4.2.36 | Request Status Report | RequestCurrentStatusReport
RequestFirstStatusMatchReport
RequestEveryStatusChangeReport | +| 6.4.2.37 | Reset Timer | Same | +| 6.4.2.38 | Route Select Failure | Same, InitialDP, EventReportBCSM | +| 6.4.2.39 | Select Facility | Same | +| 6.4.2.40 | Select Route | Same, Connect | +| 6.4.2.41 | Send Charging Information | Same | +| 6.4.2.42 | Service Filtering Response | Same | +| 6.4.2.43 | Status Report | Same | +| 6.4.2.44 | TAnswer | Same, InitialDP, EventReportBCSM | +| 6.4.2.45 | TCalled Party Busy | Same, InitialDP, EventReportBCSM | +| 6.4.2.46 | TDisconnect | Same, InitialDP, EventReportBCSM | +| 6.4.2.47 | Term Attempt Authorized | Same, InitialDP | + +| Rec. Q.1214
Reference
| Information Flow | Operation | +|----------------------------------|-------------------------------------|--------------------------------------------------------| +| 6.4.2.48 | TMidCall | Same, InitialDP, EventReportBCSM | +| 6.4.2.49 | TNoAnswer | Same, InitialDP, EventReportBCSM | +| 6.5.2.1 | AssistRequestInstructions from SRF | AssistRequestInstructions | +| 6.5.2.2 | Cancel Announcement | Cancel | +| 6.5.2.3 | Collected User Information | Return Result from Prompt and collect user information | +| 6.5.2.4 | Play Announcement | Same | +| 6.5.2.5 | Prompt and collect user information | Same | +| 6.5.2.6 | Specialized Resource Report | Same | +| 6.6.2.1 | Search | Same | +| 6.6.2.2 | Search Result | Return Result from Search | +| 6.6.2.3 | ModifyEntry | Same | +| 6.6.2.4 | Modify Entry Result | Return Result from Modifyentry | +| 6.6.2.5 | Authenticate | Bind | +| 6.6.2.6 | Authenticate Result | Return Result from Bind | +| 6.6.2.7 | AddEntry | Same | +| 6.6.2.8 | Add Entry Result | Return Result from AddEntry | +| 6.6.2.9 | RemoveEntry | Same | +| 6.6.2.10 | Remove Entry Result | Return Result from RemoveEntry | + +## 0.7 Compatibility mechanisms used for INAP + +### 0.7.1 Introduction + +This subclause specifies the compatibility mechanisms that shall be used to ensure consistent future versions of INAP. + +There are three categories of compatibility: + +- *Minor changes to INAP in future standardized versions:* + +A minor change can be defined as a change of a functionality which is not essential for the requested IN service. In case it is a modification of an existing function, it is acceptable that the addressed function is executed in either the older or the modified variant. If the change is purely additional, it is acceptable that it is not executed at all and that the peer Application Entity (AE) need not know about the effects of the change. For minor changes, a new AC is not required. + +- *Major changes to INAP in future standardized versions:* + +A major change can be defined as a change of a functionality which is essential for the requested IN service. In case it is a modification of an existing function, both application entities shall have a shared knowledge about the addressed functional variant. If the change is purely additional, the requested IN service will not be provided if one of the application entities does not support the additional functionality. For major changes, a new AC is required. + +- *Network-specific changes to INAP:* + +These additions may be of either the major or minor type for a service. No new AC is expected to be defined for this type of change. At the time of definition, the additions would not be expected to be included in identical form in future versions of Recommendations. + +## **0.7.2 Definition of INAP compatibility mechanisms** + +### **0.7.2.1 Procedures for major additions to INAP** + +In order to support the introduction of major functional changes, the protocol allows a synchronization between the two applications with regard to which functionality is to be performed. This synchronization takes place before the new function is invoked in either application entity, in order to avoid complicated fall-back procedures. The solution chosen to achieve such a synchronization is to use the AC negotiation procedures provided in Recommendation Q.773. + +### **0.7.2.2 Procedures for minor additions to INAP** + +The extension mechanism marker shall be used for future standardized minor additions to INAP. This mechanism implements extensions differently by including an "extensions marker" in the type definition. The extensions are expressed by optional fields that are placed after the marker. When an entity receives unrecognized parameters that occur after the marker, they are ignored (see Recommendation X.680-Series). + +### **0.7.2.3 Procedures for inclusion of network specific additions to INAP** + +This mechanism is based on the ability to explicitly declare fields of any type via the Macro facility in ASN.1 at the outermost level of a type definition. It works by defining an "ExtensionField" that is placed at the end of the type definition. This extension field is defined as a set of extensions, where an extension can contain any type. Each extension is associated with a value that defines whether the terminating node should ignore the field if unrecognized, or reject the message, similar to the comprehension required mechanism described in the previous subclause. Refer to Recommendation Q.1400 for a definition of this mechanism. + +For the SCF-to-SDF interface, the extension mechanisms are defined in 2.2. + +## **1 SACF/MACF rules** + +### **1.1 Reflection of TCAP-AC** + +TCAP Application Context negotiation rules require that the proposed AC, if acceptable, is reflected in the first backwards message. + +If the AC is not acceptable, and the TC-User does not wish to continue the dialogue, it may provide an alternate AC to the initiator which can be used to start a new dialogue. + +TCAP-AC negotiation applies only to the SCF interfaces. + +Refer to the Q.770-Series (Transaction capabilities application part) for a more detailed description of the TCAP AC negotiation mechanism. + +### **1.2 Sequential/Parallel execution of operations** + +In some cases it may be necessary to distinguish whether operations should be performed sequentially or in parallel (synchronized). Operations which may be synchronized are: + +- charging operations may be synchronized with any other operation. + +The method of indicating that operations are to be synchronized is to include them in the same message. Where one of the operations identified above must not be executed until some other operation has progressed to some extent or finished, the sending PE (usually SCP) can control this by sending the operations in two separate messages. + +This method does not imply that all operations sent in the same message should be executed simultaneously, but simply that where it could make sense to do so (in the situations identified above) the operations should be synchronized. + +In case of inconsistency between the above-mentioned generic rules and the FE-specific rules, as specified in clause 3, the FE-specific rules take precedence over the generic rules. + +## 2 Abstract syntax of the IN CS-1 Application Protocol + +This clause specifies the abstract syntax for the IN CS-1 Application Protocol using Abstract Syntax Notation One (ASN.1), defined in Recommendations X.208 and X.680. + +The encoding rules which are applicable to the defined abstract syntax are the basic encoding rules for ASN.1, defined in Recommendation X.209 with the restrictions as described in 4.1.1/Q.773. Additional encodings are cited for parameters used in existing ISUP (Q.763) and DSS 1 (Q.931) Recommendations. + +For the ISUP and DSS 1 parameters used in the INAP, only the coding of the parameter value will be coded as defined in ISUP or DSS 1. The DSS 1/ISUP defined parameter identifiers are removed and replaced by the INAP defined parameter identifiers. + +The mapping of OPERATION and ERROR to TCAP components is defined in Recommendation Q.773. The class of an operation is not stated explicitly but is specified in the ASN.1 OPERATION MACRO, as follows: + +Class 1 – Both RESULT and ERRORS appear in the ASN.1 OPERATION MACRO definition. + +Class 2 – Only ERRORS appears in the ASN.1 OPERATION MACRO definition. + +Class 3 – Only RESULT appears in the ASN.1 OPERATION MACRO definition. + +Class 4 – Neither RESULT nor ERRORS appears in the ASN.1 OPERATION MACRO definition. + +These map to the classes 2 through 5, respectively, specified in Recommendations X.219 and Q.932. + +The abstract syntax for INAP is composed of several ASN.1 modules describing operations, errors, and associated data types. The values (operation codes and error codes) are defined in a separate module. + +The module containing all the type definitions for INAP operations is **IN-CS-1-Operations** and is described in 2.1.1 and 2.2.2.4.1. + +The module containing all the type definitions for INAP errors is **IN-CS-1-Errors** and is described in 2.1.2 and 2.2.2.4.1. + +The module containing all the type definitions for INAP data types is **IN-CS-1-Data Types** and is described in 2.1.3 and 2.2.2.4.1. + +The module containing the operation codes and error codes for INAP is **IN-CS-1-Codes** and is described in 2.1.4 and 2.2.2.4.1. + +### 2.1 SSF-SCF, SCF-SRF Interface + +#### 2.1.1 IN CS-1 Operation Types + +**IN-CS-1-Operations { ccitt recommendation q 1218 modules(0) cs-1-operations(0) version1(0) }** + +-- *This module contains the type definitions for the IN CS-1 operations.* + +-- *There may be functional redundancies in the operation set related to call processing.* + +-- *This may make product interworking more difficult. Administrations wishing to deploy* + +-- *IN and equipment manufacturers implementing IN should take this into account.* + +**DEFINITIONS ::=** + +**BEGIN** + +**IMPORTS** + +**OPERATION** + +FROM TCAPMessages { ccitt recommendation q 773 modules(0) messages(1) version2(2) } + +-- *error types* + +Cancelled, +CancelFailed, +ETCFailed, +ImproperCallerResponse, +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +RequestedInfoError, +SystemFailure, +TaskRefused, +UnavailableResource, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter, +UnknownLegID, +UnknownResource + +FROM IN-CS-1-Errors { ccitt recommendation q 1218 modules(0) cs-1-errors(1) version1(0) } + +-- *argument types* + +ActivateServiceFilteringArg, +AnalysedInformationArg, +AnalyseInformationArg, +ApplyChargingArg, +ApplyChargingReportArg, +AssistRequestInstructionsArg, +CallGapArg, +CallInformationReportArg, +CallInformationRequestArg, +CancelArg, +CancelStatusReportRequestArg, +CollectedInformationArg, +CollectInformationArg, +ConnectArg, +ConnectToResourceArg, +EstablishTemporaryConnectionArg, +EventNotificationChargingArg, +EventReportBCSMAArg, +FurnishChargingInformationArg, +HoldCallInNetworkArg, +InitialDPArg, +InitiateCallAttemptArg, +MidCallArg, +OAnswerArg, +OCalledPartyBusyArg, +ODisconnectArg, +ONoAnswerArg, +OriginationAttemptAuthorizedArg, +PlayAnnouncementArg, +PromptAndCollectUserInformationArg, +ReceivedInformationArg, +ReleaseCallArg, +RequestCurrentStatusReportArg, +RequestCurrentStatusReportResultArg, +RequestEveryStatusChangeReportArg, +RequestFirstStatusMatchReportArg, +RequestNotificationChargingEventArg, +RequestReportBCSMEEventArg, +ResetTimerArg, +RouteSelectFailureArg, +SelectFacilityArg, +SelectRouteArg, +SendChargingInformationArg, +ServiceFilteringResponseArg, +SpecializedResourceReportArg, + +StatusReportArg, +TAnswerArg, +TBusyArg, +TDisconnectArg, +TermAttemptAuthorizedArg, +TNoAnswerArg, + +FROM IN-CS-1-DataTypes { ccitt recommendation q 1218 modules(0) cs-1-datatypes(2) version1(0) }; + +-- TYPE DEFINITIONS FOR IN CS-1 OPERATIONS FOLLOWS + +-- SCF-SSF operations + +ActivateServiceFiltering ::= OPERATION + +ARGUMENT + +ActivateServiceFilteringArg + +RESULT + +ERRORS { + +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedParameter +} + +-- Direction: SCF -> SSF, Timer: $T_{asf}$ + +-- When receiving this operation, the SSF handles calls to destination in a specified manner + +-- without sending queries for every detected call. It is used for example for providing + +-- televoting or mass calling services. Simple registration functionality (counters) and + +-- announcement control may be located at the SSF. The operation initializes the specified + +-- counters in the SSF. + +ActivityTest ::= OPERATION + +RESULT + +-- Direction: SCF -> SSF, Timer: $T_{at}$ + +-- This operation is used to check for the continued existence of a relationship between the SCF + +-- and SSF. If the relationship is still in existence, then the SSF will respond. If no reply is + +-- received, then the SCF will assume that the SSF has failed in some way and will take the + +-- appropriate action. + +AnalysedInformation ::= OPERATION + +ARGUMENT + +AnalysedInformationArg + +ERRORS { + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +-- Direction: SSF -> SCF, Timer: $T_{adi}$ + +-- This operation is used to indicate availability of routing address and call type. (DP 3 - + +-- Analysed\_Info). + +-- For additional information on this operation and its use with open numbering plans, refer to + +-- 4.2.2.2a)3)/Q.1214. + +AnalyseInformation ::= OPERATION + +ARGUMENT + +AnalyseInformationArg + +ERRORS { + +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, + +``` + + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +``` + +- *Direction: SCF -> SSF, Timer: $T_{ai}$* +- *This operation is used to request the SSF to perform the originating basic call processing actions* +- *to analyse destination information that is either collected from a calling party or provided by the SCF* +- *(e.g. for number translation). This includes actions to validate the information according to an office* +- *or customized dialling plan, and if valid, to determine call termination information, to include the called* +- *party address, the type of call (e.g. intra-network or inter-network), and carrier (if inter-network).* +- *If the called party is not served by the SSF, the SSF also determines a route index based on the called* +- *party address and class of service, where the route index points to a list of outgoing trunk groups.* + +**ApplyCharging ::= OPERATION** + +**ARGUMENT** + +``` + + ApplyChargingArg + +``` + +**ERRORS {** + +``` + + MissingParameter, + UnexpectedComponentSequence, + UnexpectedParameter, + UnexpectedDataValue, + ParameterOutOfRange, + SystemFailure, + TaskRefused +} + +``` + +- *Direction: SCF -> SSF, Timer: $T_{ac}$* +- *This operation is used for interacting from the SCF with the SSF charging mechanisms. The* +- *ApplyChargingReport operation provides the feedback from the SSF to the SCF.* + +**ApplyChargingReport ::= OPERATION** + +**ARGUMENT** + +``` + + ApplyChargingReportArg + +``` + +**ERRORS {** + +``` + + MissingParameter, + UnexpectedComponentSequence, + UnexpectedParameter, + UnexpectedDataValue, + ParameterOutOfRange, + SystemFailure, + TaskRefused +} + +``` + +- *Direction: SSF -> SCF, Timer: $T_{acr}$* +- *This operation is used by the SSF to report to the SCF the occurrence of a specific charging event as* +- *requested by the SCF using the ApplyCharging operation.* + +**AssistRequestInstructions ::= OPERATION** + +**ARGUMENT** + +``` + + AssistRequestInstructionsArg + +``` + +**ERRORS {** + +``` + + MissingCustomerRecord, + MissingParameter, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter +} + +``` + +- *Direction: SSF -> SCF or SRF -> SCF, Timer: $T_{ari}$* +- *This operation is used when there is an assist or a hand-off procedure and may be sent by the SSF* +- *or SRF to the SCF. This operation is sent by the assisting SSF or assisting SRF to the SCF, when the* +- *initiating SSF has set up a connection to the SRF or to the assisting SSF as a result of receiving* +- *an EstablishTemporaryConnection or Connect operation (in the case of hand-off) from the SCF.* +- *Refer to clause 3 for a description of the procedures associated with this operation.* + +**CallGap ::= OPERATION****ARGUMENT****CallGapArg** + +- *Direction: SCF -> SSF, Timer: $T_{cg}$* +- *This operation is used to request the SSF to reduce the rate at which specific service requests are sent to* +- *the SCF. Use of this operation by the SCF to gap queries and updates at the SDF is for further study.* + +**CallInformationReport ::= OPERATION****ARGUMENT****CallInformationReportArg** + +- *Direction: SSF -> SCF, Timer: $T_{cirp}$* +- *This operation is used to send specific call information for a single call to the SCF as requested by the* +- *SCF in a previous CallInformationRequest.* + +**CallInformationRequest ::= OPERATION****ARGUMENT****CallInformationRequestArg****ERRORS {** + +**MissingParameter,** +**ParameterOutOfRange,** +**RequestedInfoError,** +**SystemFailure,** +**TaskRefused,** +**UnexpectedComponentSequence,** +**UnexpectedDataValue,** +**UnexpectedParameter** +**}** + +- *Direction: SCF -> SSF, Timer: $T_{cirq}$* +- *This operation is used to request the SSF to record specific information about a single call and report it to* +- *the SCF (with a CallInformationReport operation).* + +**Cancel ::= OPERATION****ARGUMENT****CancelArg****ERRORS {** + +**CancelFailed,** +**MissingParameter,** +**TaskRefused** +**}** + +- *Direction: SCF -> SSF, or SCF -> SRF, Timer: $T_{can}$* +- *This generic operation cancels the correlated previous operation or all previous requests. The following* +- *operations can be canceled: PlayAnnouncement, PromptAndCollectUserInfo.* + +**CancelStatusReportRequest ::= OPERATION****ARGUMENT****CancelStatusReportRequestArg****ERRORS {** + +**CancelFailed,** +**MissingParameter,** +**TaskRefused** +**}** + +- *Direction: SCF -> SSF, Timer: $T_{csr}$* +- *This operation cancels the following processes: RequestFirstStatusMatchReport and* +- *RequestEveryStatusChangeReport.* + +**CollectedInformation ::= OPERATION****ARGUMENT****CollectedInformationArg****ERRORS {** + +**MissingCustomerRecord,** +**MissingParameter,** +**ParameterOutOfRange,** +**SystemFailure,** +**TaskRefused,** +**UnexpectedComponentSequence,** +**UnexpectedDataValue,** +**UnexpectedParameter** +**}** + +- *Direction: SSF -> SCF, Timer: $T_{cdi}$* +- *This operation is used to indicate availability of complete initial information package/dialling string from originating party. (This event may have already occurred in the case of en bloc signalling, in which case the waiting duration in this PIC is zero.) (DP 2 – Collected\_Info). For additional information on this operation and its use with open numbering plans, refer to 4.2.2.2.1-2/Q.1214.* + +**CollectInformation ::= OPERATION** + +**ARGUMENT** + +**CollectInformationArg** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +- *Direction: SCF -> SSF, Timer: $T_{ci}$* +- *This operation is used to request the SSF to perform the originating basic call processing actions to prompt a calling party for destination information, then collect destination information according to a specified numbering plan (e.g. for virtual private networks).* + +**Connect ::= OPERATION** + +**ARGUMENT** + +**ConnectArg** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +- *Direction: SCF -> SSF, Timer: $T_{con}$* +- *This operation is used to request the SSF to perform the call processing actions to route or forward a call to a specified destination. To do so, the SSF may or may not use destination information from the calling party (e.g. dialled digits) and existing call set-up information (e.g. route index to a list of trunk groups), depending on the information provided by the SCF.* +- *When address information is only included in the Connect operation, call processing resumes at PIC3 in the O-BCSM.* +- *When address information and routing information is included, call processing resumes at PIC4.* + +**ConnectToResource ::= OPERATION** + +**ARGUMENT** + +**ConnectToResourceArg** + +**ERRORS {** + +MissingParameter, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +- *Direction: SCF -> SSF, Timer: $T_{ctr}$* +- *This operation is used to connect a call from the SSP to the physical entity containing the SRF.* +- *Refer to clause 3 for a description of the procedures associated with this operation.* + +**Continue ::= OPERATION** + +- *Direction: SCF -> SSF, Timer: $T_{cue}$* +- *This operation is used to request the SSF to proceed with call processing at the DP at which it previously suspended call processing to await SCF instructions (i.e. proceed to the next point in call in the BCSM). The SSF continues call processing without substituting new data from SCF.* + +**DisconnectForwardConnection ::= OPERATION****ERRORS {** + +SystemFailure, +TaskRefused, +UnexpectedComponentSequence +} + +-- Direction: SCF -> SSF, Timer: $T_{dfc}$ + +-- This operation is used to disconnect a forward temporary connection or a connection to a resource. + +-- Refer to clause 3 for a description of the procedures associated with this operation. + +**EstablishTemporaryConnection ::= OPERATION****ARGUMENT** + +EstablishTemporaryConnectionArg + +**ERRORS {** + +ETCFailed, +MissingParameter, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +-- Direction: SCF -> SSF, Timer: $T_{etc}$ + +-- This operation is used to create a connection to a resource for a limited period of time + +-- (e.g. to play an announcement, to collect user information); it implies the use of the assist + +-- procedure. Refer to clause 3 for a description of the procedures associated with this operation. + +**EventNotificationCharging ::= OPERATION****ARGUMENT** + +EventNotificationChargingArg + +-- Direction: SSF -> SCF, Timer: $T_{enc}$ + +-- This operation is used by the SSF to report to the SCF the occurrence of a specific charging event + +-- type as previously requested by the SCF in a RequestNotificationChargingEvent operation. + +**EventReportBCSM ::= OPERATION****ARGUMENT** + +EventReportBCSMArg + +-- Direction: SSF -> SCF, Timer: $T_{erb}$ + +-- This operation is used to notify the SCF of a call-related event (e.g. BCSM events such as busy or + +-- no answer) previously requested by the SCF in a RequestReportBCSMEvent operation. + +**FurnishChargingInformation ::= OPERATION****ARGUMENT** + +FurnishChargingInformationArg + +**ERRORS {** + +MissingParameter, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +-- Direction: SCF -> SSF, Timer: $T_{fci}$ + +-- This operation is used to request the SSF to generate, register a call record or to include some + +-- information in the default call record. The registered call record is intended for off line charging of the + +-- call. + +**HoldCallInNetwork ::= OPERATION****ARGUMENT** + +HoldCallInNetworkArg + +**ERRORS {** + +MissingParameter, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- *Direction: SCF -> SSF, Timer: $T_{hcn}$* +- *This operation is used to provide the capability of queueing a call during the set-up phase (e.g. to provide a call completion to busy, the call would be queued until the destination becomes free).* + +**InitialDP ::= OPERATION** + +**ARGUMENT** + +**InitialDPArg** + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- *Direction: SSF -> SCF, Timer: $T_{idp}$* +- *This operation is used after a TDP to indicate request for service.* + +**InitiateCallAttempt ::= OPERATION** + +**ARGUMENT** + +**InitiateCallAttemptArg** + +**ERRORS {** + +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- *Direction: SCF -> SSF, Timer: $T_{ica}$* +- *This operation is used to request the SSF to create a new call to one call party using address information provided by the SCF.* + +**OAnswer ::= OPERATION** + +**ARGUMENT** + +**OAnswerArg** + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- *Direction: SSF -> SCF, Timer: $T_{oa}$* +- *This operation is used for indication from the terminating half BCSM that the call is accepted and answered by terminating party (e.g. terminating party goes offhook, Q.931 Connect message received, ISDN-UP Answer message received) (DP 7 – O\_Answer). For additional information on this operation, refer to 4.2.2.2.1-5/Q.1214.* + +**OCalledPartyBusy ::= OPERATION** + +**ARGUMENT** + +**OCalledPartyBusyArg** + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- Direction: SSF -> SCF, Timer: $T_{ob}$ +- This operation is used for Indication from the terminating half BCSM that the terminating party is busy +- (DP 5 – *O\_Called\_Party\_Busy*). For additional information on this operation, refer to 4.2.2.2.1-4/Q.1214. + +**ODisconnect ::= OPERATION** + +**ARGUMENT** + +**ODisconnectArg** + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- Direction: SSF -> SCF, Timer: $T_{od}$ +- This operation is used for a disconnect indication (e.g. onhook, Q.931 Disconnect message, SS7 Release message) is received from the originating party, or received from the terminating party via the terminating half BCSM. (DP 9 – *O\_Disconnect*). For additional information on this operation, refer to 4.2.2.2.1-5/Q.1214. + +**OMidCall ::= OPERATION** + +**ARGUMENT** + +**MidCallArg** + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- Direction: SSF -> SCF, Timer: $T_{omc}$ +- This operation is used to indicate a feature request is received from the originating party +- (e.g. hook flash, ISDN feature activation, Q.931 HOLD or RETrieve message). (DP 8 – *O\_Mid\_Call*). +- For additional information on this operation, refer to 4.2.2.2.1-5/Q.1214. + +**ONoAnswer ::= OPERATION** + +**ARGUMENT** + +**ONoAnswerArg** + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- Direction: SSF -> SCF, Timer: $T_{ona}$ +- This operation is used for indication from the terminating half BCSM that the terminating party does not answer within a specified time period (DP 6 – *O\_No\_Answer*). For additional information on this operation, refer to 4.2.2.2.1-4/Q.1214. + +**OriginationAttemptAuthorized ::= OPERATION** + +**ARGUMENT** + +**OriginationAttemptAuthorizedArg** + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, + +TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +- Direction: SSF → SCF, Timer: $T_{oaa}$ +- This operation is used to indicate the desire to place outgoing call (e.g. offhook, Q.931 Set-up message, +- ISDN-UP IAM message) and authority/ability to place outgoing call verified +- (DP 1 – Origination\_Attempt\_Authorized). For additional information on this operation, refer to +- 4.2.2.2.1-1/Q.1214. + +**ReleaseCall ::= OPERATION** + +**ARGUMENT** + +**ReleaseCallArg** + +- Direction: SCF → SSF, Timer: $T_{rc}$ +- This operation is used to tear down an existing call at any phase of the call for all parties +- involved in the call. + +**RequestCurrentStatusReport ::= OPERATION** + +**ARGUMENT** + +**RequestCurrentStatusReportArg** + +**RESULT** + +**RequestCurrentStatusReportResultArg** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedParameter, + UnknownResource + } + +- Direction: SCF → SSF, Timer: $T_{rcs}$ +- This operation is used to request the SSF to report immediately the busy/idle status of a physical +- termination resource. + +**RequestEveryStatusChangeReport ::= OPERATION** + +**ARGUMENT** + +**RequestEveryStatusChangeReportArg** + +**RESULT** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedParameter, + UnknownResource + } + +- Direction: SCF → SSF, Timer: $T_{res}$ +- This operation is used to request the SSF to report every change of busy/idle status of a physical +- termination resource. + +**RequestFirstStatusMatchReport ::= OPERATION** + +**ARGUMENT** + +**RequestFirstStatusMatchReportArg** + +**RESULT** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedParameter, + UnknownResource + } + +- *Direction: SCF -> SSF, Timer: $T_{rfs}$* +- *This operation is used to request the SSF to report the first change busy/idle to the specified status of a physical termination resource.* + +**RequestNotificationChargingEvent ::= OPERATION** + +**ARGUMENT** + +**RequestNotificationChargingEventArg** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +- *Direction: SCF -> SSF, Timer: $T_{rnc}$* +- *This operation is used by the SCF to instruct the SSF on how to manage the charging events* +- *which are received from other FE's and not under control of the service logic instance.* + +**RequestReportBCSMEvent ::= OPERATION** + +**ARGUMENT** + +**RequestReportBCSMEventArg** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +- *Direction: SCF -> SSF, Timer: $T_{rrb}$* +- *This operation is used to request the SSF to monitor for a call-related event (e.g. BCSM events such as busy or no answer), then send a notification back to the SCF when the event is detected.* +- *It is proposed that Event Detection Point (EDP) processing be always initiated by RequestReportBCSMEvent and the EDP may be acknowledged with either an EventReportBCSM or by a DP-specific operations:* +- *NOTE – The application context should identify whether Request Report BCSM Event ASE and DP Generic BCSM EventReport ASE are being used, or whether Request Report BCSM EventASE, Basic BCP DP ASE, and Advanced BCP DP ASE are being used.* +- *– For a particular IN, only one of the two alternatives identified by the respective ASEs should be selected (i.e. only one approach should be selected for a given application context).* +- *– Further study is required to identify the small set of parameters required to be conveyed for EDPs when the Basic BCP DP ASE and Advanced BCP DP ASE are used.* +- *– For CS2 further study should be given for the feasibility of progressing of one of both alternatives for both TDPs and EDPs.* +- *– Every EDP must be explicitly armed by the SCF via a RequestReportBCSMEvent operation. No implicit arming of EDPs at the SSF after reception of any operation (different from RequestReportBCSMEvent) from the SCF is allowed.* + +**ResetTimer ::= OPERATION** + +**ARGUMENT** + +**ResetTimerArg** + +**ERRORS {** + +MissingParameter, + ParameterOutOfRange, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +- *Direction: SCF -> SSF, Timer: $T_{rt}$* +- *This operation is used to request the SSF to refresh an application timer in the SSF.* + +**RouteSelectFailure ::= OPERATION** + +**ARGUMENT** + +**RouteSelectFailureArg** + +**ERRORS {** + +**MissingCustomerRecord, + MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + }** + +- *Direction: SSF → SCF, Timer: $T_{rsf}$* +- *This operation is used to indicate that the SSP is unable to select a route (e.g. unable to determine a correct route, no more routes on route list) or indication from the terminating half BCSM that a call cannot be presented to the terminating party (e.g. network congestion) (DP 4 – Route\_Select\_Failure).* +- *For additional information on this operation, refer to 4.2.2.2.1-4/Q.1214.* + +**SelectFacility ::= OPERATION** + +**ARGUMENT** + +**SelectFacilityArg** + +**ERRORS {** + +**MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + }** + +- *Direction: SCF → SSF, Timer: $T_{sf}$* +- *This operation is used to request the SSF to perform the terminating basic call processing actions to select the terminating line if it is idle, or selects an idle line from a multi-line hunt group, or selects an idle trunk from a trunk group, as appropriate. If no idle line or trunk is available, the SSF determines that the terminating facility is busy.* + +**SelectRoute ::= OPERATION** + +**ARGUMENT** + +**SelectRouteArg** + +**ERRORS {** + +**MissingParameter, + ParameterOutOfRange, + SystemFailure, + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + }** + +- *Direction: SCF → SSF, Timer: $T_{sr}$* +- *This operation is used to request the SSF to perform the originating basic call processing actions to determine routing information and select a route for a call, based either on call information available to the SSF, or on call information provided by the SCF (e.g. for alternate routing), to include the called party address, type of call, carrier, route index, and one or more alternate route indices.* +- *Based on the routing information, the SSF attempts to select a primary route for the call, and if the route is busy, attempts to select an alternate route. The SSF may fail to select a route for the call if all routes are busy.* + +**SendChargingInformation ::= OPERATION** + +**ARGUMENT** + +**SendChargingInformationArg** + +**ERRORS {** + +**MissingParameter, + UnexpectedComponentSequence, + UnexpectedParameter, + }** + +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnknownLegID +} + +- Direction: SCF -> SSF, Timer: $T_{sci}$ +- This operation is used to instruct the SSF on the charging information to send by the SSF. The charging information can either be sent back by means of signalling or internal if the SSF is located in the local exchange. In the local exchange this information may be used to update the charge meter or to create a standard call record. + +**ServiceFilteringResponse ::= OPERATION** + +**ARGUMENT** + +ServiceFilteringResponseArg + +- Direction: SSF -> SCF, Timer: $T_{sfr}$ +- This operation is used to send back to the SCF the values of counters specified in a previous ActivateServiceFiltering operation. + +**StatusReport ::= OPERATION** + +**ARGUMENT** + +StatusReportArg + +- Direction: SSF -> SCF, Timer: $T_{srp}$ +- This operation is used as a response to RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operations. + +**TAnswer ::= OPERATION** + +**ARGUMENT** + +TAnswerArg + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- Direction: SSF -> SCF, Timer: $T_{ta}$ +- This operation is used to indicate that the call is accepted and answered by terminating party (e.g. terminating party goes offhook, Q.931 Connect message received, ISDN-UP Answer message received) (DP 15 - T\_Answer). For additional information on this operation, refer to 4.2.2.2.2-10/Q.1214. + +**TBusy ::= OPERATION** + +**ARGUMENT** + +TBusyArg + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- Direction: SSF -> SCF, Timer: $T_{tb}$ +- This operation is used to indicate all resources in group busy (DP 13 - TBusy). +- For additional information on this operation, refer to 4.2.2.2.2-8/Q.1214. + +**TDisconnect ::= OPERATION** + +**ARGUMENT** + +TDisconnectArg + +**ERRORS {** + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, + +``` + +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +``` + +- Direction: SSF → SCF, Timer: $T_{td}$ +- This operation is used for a disconnect indication (e.g. onhook, Q.931 Disconnect message, +- SS7 Release message) is received from the terminating party, or received from the originating party +- via the originating half BCSM. (DP 17 – *T\_Disconnect*.) For additional information on this operation, +- refer to 4.2.2.2.2-10/Q.1214. + +**TermAttemptAuthorized ::= OPERATION** + +**ARGUMENT** + +``` +TermAttemptAuthorizedArg +``` + +**ERRORS {** + +``` + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +``` + +- Direction: SSF → SCF, Timer: $T_{taa}$ +- This operation is used for indication of incoming call received from originating half BCSM and authority +- to route call to a specified terminating resource (or group) verified. (DP 12 – *Termination\_Authorized*.) +- For additional information on this operation, refer to 4.2.2.2.2-7/Q.1214. + +**TMidCall ::= OPERATION** + +**ARGUMENT** + +``` +MidCallArg +``` + +**ERRORS {** + +``` + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +``` + +- Direction: SSF → SCF, Timer: $T_{tmc}$ +- This operation is used to indicate that a feature request is received from the terminating party (e.g. hook +- flash, ISDN feature activation Q.931 HOLD or RETrieve message). (DP 16 – *T\_Mid\_Call*.) +- For additional information on this operation, refer to 4.2.2.2.2-10/Q.1214. + +**TNoAnswer ::= OPERATION** + +**ARGUMENT** + +``` +TNoAnswerArg +``` + +**ERRORS {** + +``` + +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +``` + +- Direction: SSF → SCF, Timer: $T_{tna}$ +- This operation is used to indicate that the terminating party does not answer within a specified duration. +- (DP 14 – *T\_No\_Answer*.) For additional information on this operation, refer to 4.2.2.2.2-9/Q.1214. + +- *SCF-SRF operations* +- *AssistRequestInstructions* +- *SRF -> SCF* +- *Refer to previous description of this operation in the SCF-SSF operations clause.* +- *Cancel* +- *SCF -> SRF* +- *Refer to previous description of this operation in the SCF-SSF operations clause.* + +**PlayAnnouncement ::= OPERATION** + +**ARGUMENT** + +**PlayAnnouncementArg** + +**ERRORS {** + +Cancelled, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter, +UnavailableResource +} + +**LINKED {** + +SpecializedResourceReport +} + +- *Direction: SCF -> SRF, Timer: $T_{pa}$* +- *This operation is to be used after Establish Temporary Connection (assist procedure with a second SSP)* +- *or a Connect to Resource (no assist) operation. It may be used for inband interaction with an analogue* +- *user, or for interaction with an ISDN user. In the former case, the SRF is usually collocated with the SSF* +- *for standard tones (congestion tone...) or standard announcements. In the latter case, the SRF is always* +- *collocated with the SSF in the switch. Any error is returned to the SCF. The timer associated with this* +- *operation must be of a sufficient duration to allow its linked operation to be correctly correlated.* + +**PromptAndCollectUserInformation ::= OPERATION** + +**ARGUMENT** + +**PromptAndCollectUserInformationArg** + +**RESULT** + +**ReceivedInformationArg** + +**ERRORS {** + +Cancelled, +ImproperCallerResponse, +MissingParameter, +ParameterOutOfRange, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnavailableResource, +UnexpectedDataValue, +UnexpectedParameter +} + +- *Direction: SCF -> SRF, Timer: $T_{pc}$* +- *This operation is used to interact with a user to collect information.* + +**SpecializedResourceReport ::= OPERATION** + +**ARGUMENT** + +**SpecializedResourceReportArg** + +- *Direction: SRF -> SCF, Timer: $T_{srr}$* +- *This operation is used as the response to a PlayAnnouncement operation when the announcement* +- *completed report indication is set.* + +**END** + +The following value ranges do apply for operation specific timers in INAP: + +Short: 1-10 seconds + +Medium: 1-60 seconds + +Long: 1 second-30 minutes + +ffs For further study + +Table 2 below lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +TABLE 2/Q.1218 + +| Operation Name | Timer | Value range | +|------------------------------|-------------------|-------------| +| ActivateServiceFiltering | T asf | Medium | +| ActivityTest | T at | Short | +| AnalyzeInformation | T ai | ffs | +| AnalyzedInformation | T adi | ffs | +| ApplyCharging | T ac | Short | +| ApplyChargingReport | T acr | Short | +| AssistRequestInstructions | T ari | Short | +| CallGap | T cg | Short | +| CallInformationReport | T cirp | Short | +| CallInformationRequest | T cirq | Short | +| Cancel | T can | Short | +| CancelStatusReportRequest | T csr | ffs | +| CollectedInformation | T cdi | ffs | +| CollectInformation | T ci | Medium | +| Connect | T con | Short | +| ConnectToResource | T ctr | Short | +| Continue | T cue | Short | +| DisconnectForwardConnection | T dfc | Short | +| EstablishTemporaryConnection | T etc | Medium | +| EventNotificationCharging | T enc | Short | +| EventReportBCSM | T erb | Short | +| FurnishChargingInformation | T fci | Short | +| HoldCallInNetwork | T hen | ffs | +| InitialDP | T idp | Short | +| InitiateCallAttempt | T ica | Short | +| OAnswer | T oa | ffs | +| OCalledPartyBusy | T ob | ffs | +| ODisconnect | T od | ffs | +| OMidCall | T omc | ffs | +| ONoAnswer | T ona | ffs | +| OriginationAttemptAuthorized | T oaa | ffs | +| ReleaseCall | T rc | Short | + +TABLE 2/Q.1218 (end) + +| Operation Name | Timer | Value range | +|----------------------------------|-----------|-------------| +| RequestCurrentStatusReport | $T_{rcs}$ | ffs | +| RequestEveryStatusChangeReport | $T_{res}$ | Short | +| RequestFirstStatusMatchReport | $T_{rfs}$ | Short | +| RequestNotificationChargingEvent | $T_{rnc}$ | Short | +| RequestReportBCSMEEvent | $T_{rrb}$ | Short | +| ResetTimer | $T_{rt}$ | Short | +| RouteSelectFailure | $T_{rsf}$ | ffs | +| SelectFacility | $T_{sf}$ | ffs | +| SelectRoute | $T_{sr}$ | ffs | +| SendChargingInformation | $T_{sci}$ | Short | +| ServiceFilteringResponse | $T_{sfr}$ | Short | +| StatusReport | $T_{srp}$ | ffs | +| TAnswer | $T_{ta}$ | ffs | +| TBusy | $T_{tb}$ | ffs | +| TDisconnect | $T_{td}$ | ffs | +| TermAttemptAuthorized | $T_{taa}$ | ffs | +| TMidCall | $T_{tmc}$ | ffs | +| TNoAnswer | $T_{tna}$ | ffs | +| PlayAnnouncement | $T_{pa}$ | Long | +| PromptAndCollectUserInformation | $T_{pc}$ | Long | +| SpecializedResourceReport | $T_{srr}$ | Short | + +## 2.1.2 IN CS-1 Error Types + +IN-CS-1-Errors { ccitt recommendation q 1218 modules(0) cs-1-errors(1) version1(0) } + +-- This module contains the type definitions for the IN CS-1 errors. + +-- Where a parameter of type CHOICE is tagged with a specific tag value, the tag is automatically + +-- replaced with an EXPLICIT tag of the same value. + +DEFINITIONS IMPLICIT TAGS ::= + +BEGIN + +IMPORTS + +ERROR + +FROM TCAPMessages { ccitt recommendation q 773 modules(0) messages(1) version2(2) } + +InvokeID, + +UnavailableNetworkResource + +FROM IN-CS-1-DataTypes { ccitt recommendation q 1218 modules(0) cs-1-datatypes(2) version1(0) }; + +-- TYPE DEFINITION FOR IN CS-1 ERRORS FOLLOWS + +Cancelled ::= ERROR + +-- The operation has been cancelled. + +**CancelFailed ::= ERROR** + +``` +PARAMETER SEQUENCE { + problem [0] ENUMERATED { + unknownOperation(0), + tooLate(1), + operationNotCancellable(2) + }, + operation [1] InvokeID +} +``` + +-- The operation failed to be cancelled. + +**ETCFailed ::= ERROR** + +-- The establish temporary connection failed. + +**ImproperCallerResponse ::= ERROR** + +-- The caller response was not as expected. + +**MissingCustomerRecord ::= ERROR** + +-- The Service Logic Program could not be found in the SCF. + +**MissingParameter ::= ERROR** + +-- An expected optional parameter was not received. + +**ParameterOutOfRange ::= ERROR** + +-- The parameter was not as expected (e.g. missing or out of range). + +**RequestedInfoError ::= ERROR** + +``` +PARAMETER ENUMERATED { + unknownRequestedInfo(1), + requestedInfoNotAvailable(2) + -- other values FFS +} +``` + +-- The requested information cannot be found. + +**SystemFailure ::= ERROR** + +``` +PARAMETER + unavailableNetworkResource UnavailableNetworkResource +``` + +-- The operation could not be completed due to a system failure at the serving physical entity. + +**TaskRefused ::= ERROR** + +``` +PARAMETER ENUMERATED { + generic(0), + unobtainable (1), + congestion(2) + -- other values FFS +} +``` + +-- An entity normally capable of the task requested cannot or chooses not to perform the task at this time. This includes error situations like congestion and unobtainable address as used in (e.g. the connect operation). + +**UnavailableResource ::= ERROR** + +-- A requested resource is not available at the serving entity. + +**UnexpectedComponentSequence ::= ERROR** + +-- An incorrect sequence of Components was received (e.g. "DisconnectForwardConnection" followed by "PlayAnnouncement"). + +**UnexpectedDataValue ::= ERROR** + +-- The data value was not as expected (e.g. routing number expected but billing number received). + +**UnexpectedParameter ::= ERROR** + +-- A parameter received was not expected. + +**UnknownLegID ::= ERROR** + +-- Leg not known to the SSF. + +**UnknownResource ::= ERROR** + +-- Resource whose status is being requested is not known to the serving entity. + +END + +### 2.1.3 IN CS-1 Data Types + +**EXTENSION MACRO::=** + +**BEGIN** + +``` +TYPE NOTATION ::= ExtensionType Criticality +VALUE NOTATION ::= value(INTEGER) +ExtensionType ::= "EXTENSION-SYNTAX" type +Criticality ::= "CRITICALITY" value(CriticalityType) +CriticalityType ::= ENUMERATED { + ignore(0), + abort(1) + } +``` + +**END** + +-- Example of addition of an extension named 'Some Network Specific Indicator' of type +-- BOOLEAN, with criticality 'abort' and to be identified as extension number 1. +-- Example of definition using the above macro: +-- +-- SomeNetworkSpecificIndicator ::= EXTENSION +-- EXTENSION-SYNTAX BOOLEAN +-- CRITICALITY abort +-- +-- someNetworkSpecificIndicator SomeNetworkSpecificIndicator ::= 1 +-- +-- Example of transfer syntax, using the ExtensionField datatype as specified in the module +-- below. Assuming the value of the extension is set to TRUE, the extensions parameter +-- becomes a Sequence of type INTEGER ::= 1, criticality ENUMERATED ::= 1 and value [1] +-- EXPLICIT BOOLEAN ::= TRUE. +-- +-- Use of Q.1400 defined Extension is ffs. +-- In addition the extension mechanism marker is used to identify the future minor additions to INAP. + +**IN-CS-1-datatypes { ccitt recommendation q 1218 modules(0) cs-1-datatypes(2) version1(0) }** + +-- This module contains the type definitions for the IN CS-1 data types. +-- Where a parameter of type CHOICE is tagged with a specific tag value, the tag is automatically +-- replaced with an EXPLICIT tag of the same value. +-- The following parameters map onto bearer protocol (i.e. Q.931, case 2 and ISUP) parameters: +-- CallingPartySubaddress, CalledPartyNumber, +-- Prefix (derived from dialled digits), DestinationRoutingAddress, +-- DialledDigits, ISDNAccessRelatedInformation, CallingPartysCategory, LocationNumber, +-- TravellingClassMark, AssistingSSPIPRoutingAddress, AlertingPattern (Q.931 only), +-- ReleaseCause (and other Cause parameters), ServiceProfileIdentifier (Q.932 only), +-- BearerCapability, CallingPartyNumber, HighLayerCompatibility, OriginalCalledPartyID, +-- RedirectingPartyID, and RedirectionInformation. +-- The procedures for mapping of parameters onto bearer protocol are ffs. + +-- The following SSF parameters do not map onto bearer protocol (i.e. Q.931, case 2 and ISUP) +-- parameters and therefore are assumed to be local to the switching system: CallingPartyBusinessGroupID +-- FacilityGroup, FacilityGroupMember, RouteList, LegID, IPSSPCapabilities, IPAvailable, CGEncountered, +-- ForwardingCondition, CorrelationID, ApplicationTimer, TerminalType, MiscCallInfo, TriggerType and +-- ServiceKey. + +-- Where possible, Administrations should specify the maximum size within their network of +-- parameters specified in this Recommendation that are of an indeterminate length. + +**DEFINITIONS IMPLICIT TAGS ::=** + +**BEGIN** + +**IMPORTS** + +``` + InvokeIdType +FROM TCAPMessages {ccitt recommendation q.773 modules(2) messages(1) version2(2)}; +``` + +-- TYPE DEFINITIONS FOR IN CS-1 DATA TYPES FOLLOWS + +-- *Argument data types* + +-- *The ordering of parameters in the argument sequences has been arbitrary. Further study may be* + +-- *required to order arguments in a manner which will facilitate efficient encoding and decoding.* + +``` +ActivateServiceFilteringArg ::= SEQUENCE { + filteredCallTreatment [0] FilteredCallTreatment, + filteringCharacteristics [1] FilteringCharacteristics, + filteringTimeOut [2] FilteringTimeOut, + filteringCriteria [3] FilteringCriteria, + startTime [4] DateAndTime OPTIONAL, + extensions [5] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- ... +} +``` + +``` +AnalysedInformationArg ::= SEQUENCE { + dpSpecificCommonParameters [0] DpSpecificCommonParameters, + dialledDigits [1] CalledPartyNumber OPTIONAL, + callingPartyBusinessGroupID [2] CallingPartyBusinessGroupID OPTIONAL, + callingPartySubaddress [3] CallingPartySubaddress OPTIONAL, + callingFacilityGroup [4] FacilityGroup OPTIONAL, + callingFacilityGroupMember [5] FacilityGroupMember OPTIONAL, + originalCalledPartyID [6] OriginalCalledPartyID OPTIONAL, + prefix [7] Digits OPTIONAL, + redirectingPartyID [8] RedirectingPartyID OPTIONAL, + redirectionInformation [9] RedirectionInformation OPTIONAL, + routeList [10] RouteList OPTIONAL, + travellingClassMark [11] TravellingClassMark OPTIONAL, + extensions [12] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + featureCode [13] FeatureCode OPTIONAL, + accessCode [14] AccessCode OPTIONAL, + carrier [15] Carrier OPTIONAL +-- ... +} +``` + +-- *For the OPTIONAL parameters, refer to clause 3 for the trigger detection point processing rules* + +-- *to specify when these parameters are included in the message.* + +``` +AnalyseInformationArg ::= SEQUENCE { + destinationRoutingAddress [0] DestinationRoutingAddress, + alertingPattern [1] AlertingPattern OPTIONAL, + iSDNAcessRelatedInformation [2] ISDNAcessRelatedInformation OPTIONAL, + originalCalledPartyID [3] OriginalCalledPartyID OPTIONAL, + extensions [4] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + callingPartyNumber [5] CallingPartyNumber OPTIONAL, + callingPartysCategory [6] CallingPartysCategory OPTIONAL, + calledPartyNumber [7] CalledPartyNumber OPTIONAL, + chargeNumber [8] ChargeNumber OPTIONAL, + travellingClassMark [9] TravellingClassMark OPTIONAL, + carrier [10] Carrier OPTIONAL +-- ... +} +``` + +``` +ApplyChargingArg ::= SEQUENCE { + aChBillingChargingCharacteristics [0] AChBillingChargingCharacteristics, + partyToCharge [2] LegID OPTIONAL, + extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- ... +} +``` + +-- *The partyToCharge parameter indicates the party in the call to which the ApplyCharging operation* + +-- *should be applied. If it is not present, then it is applied to the A-party.* + +**ApplyChargingReportArg ::= CallResult** + +**AssistRequestInstructionsArg ::= SEQUENCE {** + +| | | | | +|-------------------|-----|--------------------------------------|-----------| +| correlationID | [0] | CorrelationID, | | +| iPAvailable | [1] | IPAvailable | OPTIONAL, | +| iPSSPCapabilities | [2] | IPSSPCapabilities | OPTIONAL, | +| extensions | [3] | SEQUENCE SIZE(1..numOfExtensions) OF | | +| | | ExtensionField | OPTIONAL | + +-- ... +} + +-- OPTIONAL denotes network operator specific use. The value of the correlationID may be the + +-- Called Party Number supplied by the initiating SSF. + +**CallGapArg ::= SEQUENCE {** + +| | | | | +|---------------|-----|--------------------------------------|-----------| +| gapCriteria | [0] | GapCriteria, | | +| gapIndicators | [1] | GapIndicators, | | +| controlType | [2] | ControlType | OPTIONAL, | +| gapTreatment | [3] | GapTreatment | OPTIONAL, | +| extensions | [4] | SEQUENCE SIZE(1..numOfExtensions) OF | | +| | | ExtensionField | OPTIONAL | + +-- ... +} + +-- OPTIONAL denotes network operator optional. If gapTreatment is not present, the SSF will use + +-- a default treatment depending on network operator implementation. + +**CallInformationReportArg ::= SEQUENCE {** + +| | | | | +|--------------------------|-----|--------------------------------------|-----------| +| requestedInformationList | [0] | RequestedInformationList, | | +| correlationID | [1] | CorrelationID | OPTIONAL, | +| extensions | [2] | SEQUENCE SIZE(1..numOfExtensions) OF | | +| | | ExtensionField | OPTIONAL | + +-- ... +} + +-- OPTIONAL denotes network operator optional. + +**CallInformationRequestArg ::= SEQUENCE {** + +| | | | | +|------------------------------|-----|--------------------------------------|-----------| +| requestedInformationTypeList | [0] | RequestedInformationTypeList, | | +| correlationID | [1] | CorrelationID | OPTIONAL, | +| extensions | [2] | SEQUENCE SIZE(1..numOfExtensions) OF | | +| | | ExtensionField | OPTIONAL | + +-- ... +} + +-- OPTIONAL denotes network operator optional. + +**CancelArg ::= CHOICE {** + +| | | | | +|-------------|-----|-----------|--| +| invokeID | [0] | InvokeID, | | +| allRequests | [1] | NULL | | + +-- The InvokeID has the same value as that which was used for the operation to be cancelled. + +**CancelStatusReportRequestArg ::= SEQUENCE {** + +| | | | | +|------------|-----|--------------------------------------|-----------| +| resourceID | [0] | ResourceID | OPTIONAL, | +| extensions | [1] | SEQUENCE SIZE(1..numOfExtensions) OF | | +| | | ExtensionField | OPTIONAL | + +-- ... +} + +**CollectedInformationArg ::= SEQUENCE {** + +| | | | | +|-----------------------------|-----|-----------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| dialledDigits | [1] | CalledPartyNumber | OPTIONAL, | +| callingPartyBusinessGroupID | [2] | CallingPartyBusinessGroupID | OPTIONAL, | +| callingPartySubaddress | [3] | CallingPartySubaddress | OPTIONAL, | +| callingFacilityGroup | [4] | FacilityGroup | OPTIONAL, | +| callingFacilityGroupMember | [5] | FacilityGroupMember | OPTIONAL, | +| originalCalledPartyID | [6] | OriginalCalledPartyID | OPTIONAL, | +| prefix | [7] | Digits | OPTIONAL, | +| redirectingPartyID | [8] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [9] | RedirectionInformation | OPTIONAL, | + +| | | | | +|---------------------|------|-----------------------------------|-----------| +| travellingClassMark | [10] | TravellingClassMark | OPTIONAL, | +| extensions | [11] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| featureCode | [12] | FeatureCode | OPTIONAL, | +| accessCode | [13] | AccessCode | OPTIONAL, | +| carrier | [14] | Carrier | OPTIONAL | + +-- ... +} + +-- *For the OPTIONAL parameters, refer to clause 3 for the trigger detection point processing rules* +-- *to specify when these parameters are included in the message.* + +CollectInformationArg ::= SEQUENCE { + +| | | | | +|-----------------------|-----|-----------------------------------|-----------| +| alertingPattern | [0] | AlertingPattern | OPTIONAL, | +| numberingPlan | [1] | NumberingPlan | OPTIONAL, | +| originalCalledPartyID | [2] | OriginalCalledPartyID | OPTIONAL, | +| travellingClassMark | [3] | TravellingClassMark | OPTIONAL, | +| extensions | [4] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| callingPartyNumber | [5] | CallingPartyNumber | OPTIONAL, | +| dialledDigits | [6] | CalledPartyNumber | OPTIONAL | + +-- ... +} + +ConnectArg ::= SEQUENCE { + +| | | | | +|------------------------------|------|-----------------------------------|-----------| +| destinationRoutingAddress | [0] | DestinationRoutingAddress, | | +| alertingPattern | [1] | AlertingPattern | OPTIONAL, | +| correlationID | [2] | CorrelationID | OPTIONAL, | +| cutAndPaste | [3] | CutAndPaste | OPTIONAL, | +| forwardingCondition | [4] | ForwardingCondition | OPTIONAL, | +| iSDNAcessRelatedInformation | [5] | iSDNAcessRelatedInformation | OPTIONAL, | +| originalCalledPartyID | [6] | OriginalCalledPartyID | OPTIONAL, | +| routeList | [7] | RouteList | OPTIONAL, | +| scfID | [8] | ScfID | OPTIONAL, | +| travellingClassMark | [9] | TravellingClassMark | OPTIONAL, | +| extensions | [10] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| carrier | [11] | Carrier | OPTIONAL, | +| serviceInteractionIndicators | [26] | ServiceInteractionIndicators | OPTIONAL, | +| callingPartyNumber | [27] | CallingPartyNumber | OPTIONAL, | +| callingPartysCategory | [28] | CallingPartysCategory | OPTIONAL, | +| redirectingPartyID | [29] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [30] | RedirectionInformation | OPTIONAL | + +-- ... +} + +-- *For alerting pattern, OPTIONAL denotes that this parameter only applies if SSF is the terminating* +-- *local exchange for the subscriber.* + +ConnectToResourceArg ::= SEQUENCE { + +| | | | | +|------------------------------|------|----------------------------------------|-----------| +| resourceAddress | | CHOICE { | | +| ipRoutingAddress | [0] | IPRoutingAddress, | | +| legID | [1] | LegID, | | +| both | [2] | SEQUENCE { | | +| | | ipRoutingAddress [0] IPRoutingAddress, | | +| | | legID [1] LegID | | +| | | }, | | +| none | [3] | NULL | | +| }, | | | | +| extensions | [4] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| serviceInteractionIndicators | [30] | ServiceInteractionIndicators | OPTIONAL | + +-- ... +} + +DpSpecificCommonParameters ::= SEQUENCE { + +| | | | | +|---------------------------|-----|----------------------------|-----------| +| serviceAddressInformation | [0] | ServiceAddressInformation, | | +| bearerCapability | [1] | BearerCapability | OPTIONAL, | +| calledPartyNumber | [2] | CalledPartyNumber | OPTIONAL, | +| callingPartyNumber | [3] | CallingPartyNumber | OPTIONAL, | +| callingPartysCategory | [4] | CallingPartysCategory | OPTIONAL, | + +| | | | | +|------------------------------|------|-----------------------------------|-----------| +| iPSSPCapabilities | [5] | IPSSPCapabilities | OPTIONAL, | +| iPAvailable | [6] | IPAvailable | OPTIONAL, | +| iSDNAccessRelatedInformation | [7] | ISDNAccessRelatedInformation | OPTIONAL, | +| cGEncountered | [8] | CGEncountered | OPTIONAL, | +| locationNumber | [9] | LocationNumber | OPTIONAL, | +| serviceProfileIdentifier | [10] | ServiceProfileIdentifier | OPTIONAL, | +| terminalType | [11] | TerminalType | OPTIONAL, | +| extensions | [12] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| chargeNumber | [13] | ChargeNumber | OPTIONAL, | +| servingAreaID | [14] | ServingAreaID | OPTIONAL | + +-- ... +} + +-- OPTIONAL for iPSSPCapabilities, iPAvailable, and cGEncountered denotes network operator specific use. OPTIONAL for callingPartyNumber, and callingPartysCategory refer to clause 3 for the trigger detection point processing rules to specify when these parameters are included in the message. bearerCapability should be appropriately coded as speech. + +EstablishTemporaryConnectionArg ::= SEQUENCE { + +| | | | | +|------------------------------|------|-----------------------------------|-----------| +| assistingSSPIPRoutingAddress | [0] | AssistingSSPIPRoutingAddress, | | +| correlationID | [1] | CorrelationID | OPTIONAL, | +| legID | [2] | LegID | OPTIONAL, | +| scfID | [3] | ScfID | OPTIONAL, | +| extensions | [4] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| carrier | [5] | Carrier | OPTIONAL, | +| serviceInteractionIndicators | [30] | ServiceInteractionIndicators | OPTIONAL | + +-- ... +} + +EventNotificationChargingArg ::= SEQUENCE { + +| | | | | +|----------------------------------|------|-----------------------------------|---------------------------| +| eventTypeCharging | [0] | EventTypeCharging, | | +| eventSpecificInformationCharging | [1] | EventSpecificInformationCharging | OPTIONAL, | +| legID | [2] | LegID | OPTIONAL, | +| extensions | [3] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| monitorMode | [30] | MonitorMode | DEFAULT notifyAndContinue | + +-- ... +} + +-- OPTIONAL denotes network operator specific use. + +EventReportBCSMArg ::= SEQUENCE { + +| | | | | +|------------------------------|-----|-----------------------------------|--------------------------------| +| eventTypeBCSM | [0] | EventTypeBCSM, | | +| bcsmEventCorrelationID | [1] | CorrelationID | OPTIONAL, | +| eventSpecificInformationBCSM | [2] | EventSpecificInformationBCSM | OPTIONAL, | +| legID | [3] | LegID | OPTIONAL, | +| miscCallInfo | [4] | MiscCallInfo | DEFAULT {messageType request}, | +| extensions | [5] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL | + +-- ... +} + +FurnishChargingInformationArg ::= FCIBillingChargingCharacteristics + +HoldCallInNetworkArg ::= CHOICE { + +| | | | | +|-----------|-----|------------|--| +| holdcause | [0] | HoldCause, | | +| empty | [1] | NULL | | + +-- holdcause is optional and denotes network operator specific use. + +InitialDPArg ::= SEQUENCE { + +| | | | | +|-----------------------------|-----|-----------------------------|-----------| +| serviceKey | [0] | ServiceKey | OPTIONAL, | +| dialledDigits | [1] | CalledPartyNumber | OPTIONAL, | +| calledPartyNumber | [2] | CalledPartyNumber | OPTIONAL, | +| callingPartyNumber | [3] | CallingPartyNumber | OPTIONAL, | +| callingPartyBusinessGroupID | [4] | CallingPartyBusinessGroupID | OPTIONAL, | +| callingPartysCategory | [5] | CallingPartysCategory | OPTIONAL, | +| callingPartySubaddress | [6] | CallingPartySubaddress | OPTIONAL, | + +| | | | | +|------------------------------|------|-----------------------------------|-----------| +| cGEncountered | [7] | CGEncountered | OPTIONAL, | +| iPSSPCapabilities | [8] | IPSSPCapabilities | OPTIONAL, | +| iPAvailable | [9] | IPAvailable | OPTIONAL, | +| locationNumber | [10] | LocationNumber | OPTIONAL, | +| miscCallInfo | [11] | MiscCallInfo | OPTIONAL, | +| originalCalledPartyID | [12] | OriginalCalledPartyID | OPTIONAL, | +| serviceProfileIdentifier | [13] | ServiceProfileIdentifier | OPTIONAL, | +| terminalType | [14] | TerminalType | OPTIONAL, | +| extensions | [15] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| triggerType | [16] | TriggerType | OPTIONAL, | +| highLayerCompatibility | [23] | HighLayerCompatibility | OPTIONAL, | +| serviceInteractionIndicators | [24] | ServiceInteractionIndicators | OPTIONAL, | +| additionalCallingPartyNumber | [25] | AdditionalCallingPartyNumber | OPTIONAL, | +| forwardCallIndicators | [26] | ForwardCallIndicators | OPTIONAL, | +| bearerCapability | [27] | BearerCapability | OPTIONAL, | +| eventTypeBCSM | [28] | EventTypeBCSM | OPTIONAL, | +| redirectingPartyID | [29] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [30] | RedirectionInformation | OPTIONAL | + +-- ... +} + +- OPTIONAL for iPSSPCapabilities, iPAvailable, cGEncountered, and miscCallInfo denotes network operator specific use. +- OPTIONAL for dialledDigits, callingPartyNumber, and callingPartysCategory refer to clause 3 for the trigger detection point processing rules to specify when these parameters are included in the message. +- OPTIONAL for terminalType indicates that this parameter applies only at originating or terminating local exchanges if the SSF has this information. + +InitiateCallAttemptArg ::= SEQUENCE { + +| | | | | +|------------------------------|------|-----------------------------------|-----------| +| destinationRouting_address | [0] | DestinationRoutingAddress, | | +| alertingPattern | [1] | AlertingPattern | OPTIONAL, | +| iSDNAccessRelatedInformation | [2] | ISDNAccessRelatedInformation | OPTIONAL, | +| travellingClassMark | [3] | TravellingClassMark | OPTIONAL, | +| extensions | [4] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL | +| serviceInteractionIndicators | [29] | ServiceInteractionIndicators | OPTIONAL, | +| callingPartyNumber | [30] | CallingPartyNumber | OPTIONAL | + +-- ... +} + +MidCallArg ::= SEQUENCE { + +| | | | | +|-----------------------------|-----|-----------------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| calledPartyBusinessGroupID | [1] | CalledPartyBusinessGroupID | OPTIONAL, | +| calledPartySubaddress | [2] | CalledPartySubaddress | OPTIONAL, | +| callingPartyBusinessGroupID | [3] | CallingPartyBusinessGroupID | OPTIONAL, | +| callingPartySubaddress | [4] | CallingPartySubaddress | OPTIONAL, | +| featureRequestIndicator | [5] | FeatureRequestIndicator | OPTIONAL, | +| extensions | [6] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| carrier | [7] | Carrier | OPTIONAL | + +-- ... +} + +- For the OPTIONAL parameters, refer to clause 3 for the trigger detection point processing rules to specify when these parameters are included in the message. + +OAnswerArg ::= SEQUENCE { + +| | | | | +|-----------------------------|-----|-----------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| callingPartyBusinessGroupID | [1] | CallingPartyBusinessGroupID | OPTIONAL, | +| callingPartySubaddress | [2] | CallingPartySubaddress | OPTIONAL, | +| callingFacilityGroup | [3] | FacilityGroup | OPTIONAL, | +| callingFacilityGroupMember | [4] | FacilityGroupMember | OPTIONAL, | +| originalCalledPartyID | [5] | OriginalCalledPartyID | OPTIONAL, | +| redirectingPartyID | [6] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [7] | RedirectionInformation | OPTIONAL, | + +| | | | | +|---------------------|------|-----------------------------------|-----------| +| routeList | [8] | RouteList | OPTIONAL, | +| travellingClassMark | [9] | TravellingClassMark | OPTIONAL, | +| extensions | [10] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL | + +-- ... +} + +-- For the *OPTIONAL* parameters, refer to clause 3 for the trigger detection point processing rules +-- to specify when these parameters are included in the message. + +**OCalledPartyBusyArg ::= SEQUENCE {** + +| | | | | +|-----------------------------|------|-----------------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| busyCause | [1] | Cause | OPTIONAL, | +| callingPartyBusinessGroupID | [2] | CallingPartyBusinessGroupID | OPTIONAL, | +| callingPartySubaddress | [3] | CallingPartySubaddress | OPTIONAL, | +| callingFacilityGroup | [4] | FacilityGroup | OPTIONAL, | +| callingFacilityGroupMember | [5] | FacilityGroupMember | OPTIONAL, | +| originalCalledPartyID | [6] | OriginalCalledPartyID | OPTIONAL, | +| prefix | [7] | Digits | OPTIONAL, | +| redirectingPartyID | [8] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [9] | RedirectionInformation | OPTIONAL, | +| routeList | [10] | RouteList | OPTIONAL, | +| travellingClassMark | [11] | TravellingClassMark | OPTIONAL, | +| extensions | [12] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| carrier | [13] | Carrier | OPTIONAL | + +-- ... +} + +-- For the *OPTIONAL* parameters, refer to clause 3 for the trigger detection point processing rules +-- to specify when these parameters are included in the message. + +**ODisconnectArg ::= SEQUENCE {** + +| | | | | +|-----------------------------|-----|-----------------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| callingPartyBusinessGroupID | [1] | CallingPartyBusinessGroupID | OPTIONAL, | +| callingPartySubaddress | [2] | CallingPartySubaddress | OPTIONAL, | +| callingFacilityGroup | [3] | FacilityGroup | OPTIONAL, | +| callingFacilityGroupMember | [4] | FacilityGroupMember | OPTIONAL, | +| releaseCause | [5] | Cause | OPTIONAL, | +| routeList | [6] | RouteList | OPTIONAL, | +| extensions | [7] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| carrier | [8] | Carrier | OPTIONAL, | +| connectTime | [9] | Integer4 | OPTIONAL | + +-- ... +} + +-- For the *OPTIONAL* parameters, refer to clause 3 for the trigger detection point processing rules +-- to specify when these parameters are included in the message. + +**ONoAnswerArg ::= SEQUENCE {** + +| | | | | +|-----------------------------|------|-----------------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| callingPartyBusinessGroupID | [1] | CallingPartyBusinessGroupID | OPTIONAL, | +| callingPartySubaddress | [2] | CallingPartySubaddress | OPTIONAL, | +| callingFacilityGroup | [3] | FacilityGroup | OPTIONAL, | +| callingFacilityGroupMember | [4] | FacilityGroupMember | OPTIONAL, | +| originalCalledPartyID | [5] | OriginalCalledPartyID | OPTIONAL, | +| prefix | [6] | Digits | OPTIONAL, | +| redirectingPartyID | [7] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [8] | RedirectionInformation | OPTIONAL, | +| routeList | [9] | RouteList | OPTIONAL, | +| travellingClassMark | [10] | TravellingClassMark | OPTIONAL, | +| extensions | [11] | SEQUENCE SIZE(1..numOfExtensions) | OF | +| | | ExtensionField | OPTIONAL, | +| carrier | [12] | Carrier | OPTIONAL | + +-- ... +} + +-- For the *OPTIONAL* parameters, refer to clause 3 for the trigger detection point processing rules +-- to specify when these parameters are included in the message. + +``` + +OriginationAttemptAuthorizedArg ::= SEQUENCE { + dpSpecificCommonParameters [0] DpSpecificCommonParameters, + dialledDigits [1] CalledPartyNumber OPTIONAL, + callingPartyBusinessGroupID [2] CallingPartyBusinessGroupID OPTIONAL, + callingPartySubaddress [3] CallingPartySubaddress OPTIONAL, + callingFacilityGroup [4] FacilityGroup OPTIONAL, + callingFacilityGroupMember [5] FacilityGroupMember OPTIONAL, + travellingClassMark [6] TravellingClassMark OPTIONAL, + extensions [7] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + carrier [8] Carrier OPTIONAL +-- ... +-- } +-- For the OPTIONAL parameters, refer to clause 3 for the trigger detection point processing rules +-- to specify when these parameters are included in the message. + +PlayAnnouncementArg ::= SEQUENCE { + informationToSend [0] InformationToSend, + disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE, + requestAnnouncementComplete [2] BOOLEAN DEFAULT TRUE, + extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- ... +-- } + +PromptAndCollectUserInfoArg ::= SEQUENCE { + collectedInfo [0] CollectedInfo, + disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE, + informationToSend [2] InformationToSend OPTIONAL, + extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- ... +-- } + +ReceivedInformationArg ::= CHOICE { + digitsResponse [0] Digits, + ia5Response [1] IA5String +-- } + +ReleaseCallArg ::= Cause +-- A default value of decimal 31 (normal unspecified) should be coded appropriately. + +RequestCurrentStatusReportArg ::= ResourceID + +RequestCurrentStatusReportResultArg ::= SEQUENCE { + resourceStatus [0] ResourceStatus, + resourceID [1] ResourceID OPTIONAL, + extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- ... +-- } + +RequestEveryStatusChangeReportArg ::= SEQUENCE { + resourceID [0] ResourceID, + correlationID [1] CorrelationID OPTIONAL, + monitorDuration [2] Duration OPTIONAL, + extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- ... +-- } +-- For correlationID OPTIONAL denotes network operator optional. +-- monitorDuration is required if outside the context of a call. It is not expected if we are in the context +-- of a call, because in that case the end of the call implicitly means the end of the monitoring. + +RequestFirstStatusMatchReportArg ::= SEQUENCE { + resourceID [0] ResourceID OPTIONAL, + resourceStatus [1] ResourceStatus OPTIONAL, + correlationID [2] CorrelationID OPTIONAL, + +``` + +``` + + monitorDuration [3] Duration OPTIONAL, + extensions [4] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + bearerCapability [5] BearerCapability OPTIONAL +-- + ... +} + +-- For correlationID OPTIONAL denotes network operator optional. +-- monitorDuration is required if outside the context of a call. It is not expected if we are in the context +-- of a call, because in that case the end of the call implicitly means the end of the monitoring. + +RequestNotificationChargingEventArg ::= SEQUENCE SIZE(1..numOfChargingEvents) + OF ChargingEvent + +RequestReportBCSMEventArg ::= SEQUENCE { + bcsmeEvents [0] SEQUENCE SIZE(1..numOfBCSMEvents) OF + BCSMEvent, + bcsmeEventCorrelationID [1] CorrelationID OPTIONAL, + extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- + ... +} + +-- Indicates the BCSM related events for notification. +-- For correlationID OPTIONAL denotes network operator optional. + +ResetTimerArg ::= SEQUENCE { + timerID [0] TimerID DEFAULT tssf, + timerValue [1] TimerValue, + extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- + ... +} + +RouteSelectFailureArg ::= SEQUENCE { + dpSpecificCommonParameters [0] DpSpecificCommonParameters, + dialledDigits [1] CalledPartyNumber OPTIONAL, + callingPartyBusinessGroupID [2] CallingPartyBusinessGroupID OPTIONAL, + callingPartySubaddress [3] CallingPartySubaddress OPTIONAL, + callingFacilityGroup [4] FacilityGroup OPTIONAL, + callingFacilityGroupMember [5] FacilityGroupMember OPTIONAL, + failureCause [6] Cause OPTIONAL, + originalCalledPartyID [7] OriginalCalledPartyID OPTIONAL, + prefix [8] Digits OPTIONAL, + redirectingPartyID [9] RedirectingPartyID OPTIONAL, + redirectionInformation [10] RedirectionInformation OPTIONAL, + routeList [11] RouteList OPTIONAL, + travellingClassMark [12] TravellingClassMark OPTIONAL, + extensions [13] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + carrier [14] Carrier OPTIONAL +-- + ... +} + +-- For the OPTIONAL parameters, refer to clause 3 for the trigger detection point processing +-- rules to specify when these parameters are included in the message. + +SelectFacilityArg ::= SEQUENCE { + alertingPattern [0] AlertingPattern OPTIONAL, + destinationNumberRoutingAddress [1] CalledPartyNumber OPTIONAL, + iSDNAccessRelatedInformation [2] ISDNAccessRelatedInformation OPTIONAL, + calledFacilityGroup [3] FacilityGroup OPTIONAL, + calledFacilityGroupMember [4] FacilityGroupMember OPTIONAL, + originalCalledPartyID [5] OriginalCalledPartyID OPTIONAL, + extensions [6] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- + ... +} + +-- OPTIONAL parameters are only provided if modifications desired to basic call processing values. + +``` + +``` + +SelectRouteArg ::= SEQUENCE { + destinationRoutingAddress [0] DestinationRoutingAddress, + alertingPattern [1] AlertingPattern OPTIONAL, + correlationID [2] CorrelationID OPTIONAL, + iSDNAccessRelatedInformation [3] ISDNAccessRelatedInformation OPTIONAL, + originalCalledPartyID [4] OriginalCalledPartyID OPTIONAL, + routeList [5] RouteList OPTIONAL, + scfID [6] ScfID OPTIONAL, + travellingClassMark [7] TravellingClassMark OPTIONAL, + extensions [8] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + carrier [9] Carrier OPTIONAL +-- +} + +``` + +-- OPTIONAL parameters are only provided if modifications desired to basic call processing values. + +``` + +SendChargingInformationArg ::= SEQUENCE { + sCIBillingChargingCharacteristics [0] SCIBillingChargingCharacteristics, + partyToCharge [1] LegID, + extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- +} + +``` + +``` + +ServiceFilteringResponseArg ::= SEQUENCE { + countersValue [0] CountersValue, + filteringCriteria [1] FilteringCriteria, + extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + responseCondition [3] ResponseCondition OPTIONAL +-- +} + +``` + +SpecializedResourceReportArg ::= NULL + +``` + +StatusReportArg ::= SEQUENCE { + resourceStatus [0] ResourceStatus OPTIONAL, + correlationID [1] CorrelationID OPTIONAL, + resourceID [2] ResourceID OPTIONAL, + extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL, + reportCondition [4] ReportCondition OPTIONAL +-- +} + +``` + +-- For correlationID, OPTIONAL denotes network operator optional. + +-- resourceID is required when the SSF sends a report as an answer to a previous request when the + +-- correlationID was present. + +``` + +TAnswerArg ::= SEQUENCE { + dpSpecificCommonParameters [0] DpSpecificCommonParameters, + calledPartyBusinessGroupID [1] CalledPartyBusinessGroupID OPTIONAL, + calledPartySubaddress [2] CalledPartySubaddress OPTIONAL, + calledFacilityGroup [3] FacilityGroup OPTIONAL, + calledFacilityGroupMember [4] FacilityGroupMember OPTIONAL, + extensions [5] SEQUENCE SIZE(1..numOfExtensions) OF + ExtensionField OPTIONAL +-- +} + +``` + +``` + +TBusyArg ::= SEQUENCE { + dpSpecificCommonParameters [0] DpSpecificCommonParameters, + busyCause [1] Cause OPTIONAL, + calledPartyBusinessGroupID [2] CalledPartyBusinessGroupID OPTIONAL, + calledPartySubaddress [3] CalledPartySubaddress PTIONAL, + originalCalledPartyID [4] OriginalCalledPartyID OPTIONAL, + redirectingPartyID [5] RedirectingPartyID OPTIONAL +-- +} + +``` + +| | | | | +|------------------------|-----|--------------------------------------------------------|-----------| +| redirectionInformation | [6] | RedirectionInformation | OPTIONAL, | +| routeList | [7] | RouteList | OPTIONAL, | +| travellingClassMark | [8] | TravellingClassMark | OPTIONAL, | +| extensions | [9] | SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField | OPTIONAL | + +-- ... +} + +-- *For the OPTIONAL parameters, refer to clause 3 for the trigger detection point processing rules* +-- *to specify when these parameters are included in the message.* + +**TDisconnectArg ::= SEQUENCE {** + +| | | | | +|----------------------------|-----|--------------------------------------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| calledPartyBusinessGroupID | [1] | CalledPartyBusinessGroupID | OPTIONAL, | +| calledPartySubaddress | [2] | CalledPartySubaddress | OPTIONAL, | +| calledFacilityGroup | [3] | FacilityGroup | OPTIONAL, | +| calledFacilityGroupMember | [4] | FacilityGroupMember | OPTIONAL, | +| releaseCause | [5] | Cause | OPTIONAL, | +| extensions | [6] | SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField | OPTIONAL, | +| connectTime | [7] | Integer4 | OPTIONAL | + +-- ... +} + +**TermAttemptAuthorizedArg ::= SEQUENCE {** + +| | | | | +|-----------------------------|-----|--------------------------------------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| calledPartyBusinessGroupID | [1] | CalledPartyBusinessGroupID | OPTIONAL, | +| calledPartySubaddress | [2] | CalledPartySubaddress | OPTIONAL, | +| callingPartyBusinessGroupID | [3] | CallingPartyBusinessGroupID | OPTIONAL, | +| originalCalledPartyID | [4] | OriginalCalledPartyID | OPTIONAL, | +| redirectingPartyID | [5] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [6] | RedirectionInformation | OPTIONAL, | +| routeList | [7] | RouteList | OPTIONAL, | +| travellingClassMark | [8] | TravellingClassMark | OPTIONAL, | +| extensions | [9] | SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField | OPTIONAL | + +-- ... +} + +**TNoAnswerArg ::= SEQUENCE {** + +| | | | | +|----------------------------|-----|--------------------------------------------------------|-----------| +| dpSpecificCommonParameters | [0] | DpSpecificCommonParameters, | | +| calledPartyBusinessGroupID | [1] | CalledPartyBusinessGroupID | OPTIONAL, | +| calledPartySubaddress | [2] | CalledPartySubaddress | OPTIONAL, | +| calledFacilityGroup | [3] | FacilityGroup | OPTIONAL, | +| calledFacilityGroupMember | [4] | FacilityGroupMember | OPTIONAL, | +| originalCalledPartyID | [5] | OriginalCalledPartyID | OPTIONAL, | +| redirectingPartyID | [6] | RedirectingPartyID | OPTIONAL, | +| redirectionInformation | [7] | RedirectionInformation | OPTIONAL, | +| travellingClassMark | [8] | TravellingClassMark | OPTIONAL, | +| extensions | [9] | SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField | OPTIONAL | + +-- ... +} + +-- *The Definition of Common Data Types* + +**AccessCode ::= LocationNumber** + +-- *An access code from a business group dialling plan attendant access codes, access codes to escape* +-- *to the public network, access code to access a private facility/network, and feature access codes.* +-- *Uses the LocationNumber format which is based on the Q.763 Location Number format.* +-- *The Nature of Address indicator field shall be set to "Spare" (value 00000000).* +-- *The Numbering Plan Indicator field shall be set to "Spare" (value 000).* +-- *Of local significance.* + +**AChBillingChargingCharacteristics ::= OCTET STRING (SIZE (minAChBillingChargingLength.. +maxAChBillingChargingLength))** + +-- *The AChBillingChargingCharacteristics parameter specifies the charging related information* +-- *to be provided by the SSF and the conditions on which this information has to be reported* +-- *back to the SCF with the ApplyChargingReport operation.* +-- *Examples of charging related information to be provided by the SSF may be: bulk counter* +-- *values, costs, tariff change and time of charge, time stamps, durations, etc.* + +- Examples of conditions on which the charging related information are to be reported may be: +- threshold value reached, timer expiration, tariff change, end of connection configuration, etc. + +**AdditionalCallingPartyNumber ::= Digits** + +- Indicates the Additional Calling Party Number. Refer to Recommendation Q.763 for encoding. + +**AlertingPattern ::= OCTET STRING (SIZE(3))** + +- Indicates a specific pattern that is used to alert a subscriber (e.g. distinctive ringing, tones, etc.). +- Only applies if SSF is the terminating local exchange for the subscriber. Refer to the Q.931 +- Signal parameter for encoding. + +**ApplicationTimer ::= INTEGER (0..2047)** + +- Used by the SCF to set a timer in the SSF. The timer is in seconds. + +**AssistingSSPIPRoutingAddress ::= Digits** + +- Indicates the destination address of the SRF for the assist procedure. + +**BCSMEvent ::= SEQUENCE {** + +| | | | | +|--------------------|------|--------------------|-----------| +| eventTypeBCSM | [0] | EventTypeBCSM, | | +| monitorMode | [1] | MonitorMode, | | +| legID | [2] | LegID | OPTIONAL, | +| dpSpecificCriteria | [30] | DpSpecificCriteria | OPTIONAL | + +} + +- Indicates the BCSM Event information for monitoring. + +**BearerCapability ::= CHOICE {** + +| | | | | +|-----------|-----|-------------------------------------------------------|--| +| bearerCap | [0] | OCTET STRING
(SIZE(2..maxBearerCapabilityLength)), | | +| tmr | [1] | OCTET STRING (SIZE(1)) | | + +} + +- Indicates the type of bearer capability connection to the user. For bearerCapability, either +- DSS 1 (Q.931) or the ISUP User Service Information (Q.763) encoding can be used. Refer +- to the Q.763 Transmission Medium Requirement parameter for tmr encoding. + +**CalledPartyBusinessGroupID ::= OCTET STRING** + +- Indicates the business group of the called party. The value of this octet string is network +- operator specific. + +**CalledPartyNumber ::= OCTET STRING (SIZE (minCalledPartyNumberLength.. +maxCalledPartyNumberLength))** + +- Indicates the Called Party Number. Refer to Recommendation Q.763 for encoding. + +**CalledPartySubaddress ::= OCTET STRING** + +- Indicates the Called Party Subaddress. Refer to Recommendation Q.931 for encoding. + +**CallingPartyBusinessGroupID ::= OCTET STRING** + +- Indicates the business group of the calling party. The value of this octet string is network +- operator specific. + +**CallingPartyNumber ::= OCTET STRING (SIZE (minCallingPartyNumberLength.. +maxCallingPartyNumberLength))** + +- Indicates the Calling Party Number. Refer to Recommendation Q.763 for encoding. + +**CallingPartySubaddress ::= OCTET STRING** + +- Indicates the Calling Party Subaddress. Refer to Recommendation Q.931 for encoding. + +**CallingPartysCategory ::= OCTET STRING (SIZE(1))** + +- Indicates the type of calling party (e.g. operator, payphone, ordinary subscriber). +- Refer to Recommendation Q.763 for encoding. + +**CallResult ::= OCTET STRING (SIZE (minCallResultLength.. +maxCallResultLength))** + +- This parameter provides the SCF with the charging related information previously requested +- using the ApplyCharging operation. This shall include the partyToCharge parameter as +- received in the related ApplyCharging operation to correlate the result to the request. +- The remaining content is network operator specific. + +- Examples of charging related information to be provided by the SSF may be: bulk counter values, +- costs, tariff change and time of change, time stamps, durations, etc. +- Examples of conditions on which the charging related information are to be reported may be: +- threshold value reached, timer expiration, tariff change, end of connection configuration, etc. + +**Carrier ::= OCTET STRING** + +- Contains the carrier selection and carrier ID fields. +- Carrier selection is one octet and is encoded as: +- 00000000 No indication +- 00000001 Selected carrier code pre subscribed and not input by calling party +- 00000010 Selected carrier identification code pre subscribed and input by calling party +- 00000011 Selected carrier identification code pre subscribed, no indication of whether input by calling party +- 00000100 Selected carrier identification code not pre subscribed and input by calling party +- 00000101 +- to Spare +- 11111110 +- 11111111 Reserved +- +- Carrier ID has a one octet field indicating the number of digits followed by the digits encoded using BCD. +- Detailed coding is for further study. It is of local significance and carrying it through the ISUP is for further study. + +**Cause ::= OCTET STRING (SIZE (minCauseLength..maxCauseLength))** + +- Indicates the cause for interface related information. Refer to the Q.763 Cause parameter for encoding. +- For the use of cause and location values refer to Recommendation Q.850. + +**CGEncountered ::= ENUMERATED {** + +    noCGEncountered(0), +     manualCGencountered(1), +     scpOverload(2) + } + +- Indicates the type of automatic call gapping encountered, if any. + +**ChargeNumber ::= LocationNumber** + +- Information sent in either direction indicating the chargeable number for the call and consisting +- of the odd/even indicator, nature of address indicator, numbering plan indicator, and address signals. +- Uses the LocationNumber format which is based on the Q.763 Location Number format. +- For example, the ChargeNumber may be a third party number to which a call is billed for the 3rd party +- billing service. In this case, the calling party may request operator assistance to charge the call to, +- for example, their home number. + +**ChargingEvent ::= SEQUENCE {** + +| | | | | +|-------------------|-----|--------------------|----------| +| eventTypeCharging | [0] | EventTypeCharging, | | +| monitorMode | [1] | MonitorMode, | | +| legID | [2] | LegID | OPTIONAL | +| } | | | | + +- This parameter indicates the charging event type and corresponding +- monitor mode and LedID. + +**CollectedDigits ::= SEQUENCE {** + +| | | | | +|---------------------|------|----------------------------|-------------------| +| minimumNbOfDigits | [0] | INTEGER (1..127) | DEFAULT 1, | +| maximumNbOfDigits | [1] | INTEGER (1..127), | | +| endOfReplyDigit | [2] | OCTET STRING (SIZE (1..2)) | OPTIONAL, | +| cancelDigit | [3] | OCTET STRING (SIZE (1..2)) | OPTIONAL, | +| startDigit | [4] | OCTET STRING (SIZE (1..2)) | OPTIONAL, | +| firstDigitTimeout | [5] | INTEGER (1..127) | OPTIONAL, | +| interDigitTimeout | [6] | INTEGER (1..127) | OPTIONAL, | +| errorTreatment | [7] | ErrorTreatment | DEFAULT | +| | | | reportErrorToScf, | +| interruptableAnnInd | [8] | BOOLEAN | DEFAULT TRUE, | +| voiceInformation | [9] | BOOLEAN | DEFAULT FALSE, | +| voiceBack | [10] | BOOLEAN | DEFAULT FALSE | +| } | | | | + +- The use of voiceBack is network operator specific. +- The endOfReplyDigit, cancelDigit, and startDigit parameters have been designated as OCTET STRING, +- and are to be encoded as BCD, one digit per octet only, contained +- in the four least significant bits of each OCTET. The usage is service dependent. + +**CollectedInfo ::= CHOICE {** + +| | | | +|-----------------|-----|------------------| +| collectedDigits | [0] | CollectedDigits, | +| iA5Information | [1] | BOOLEAN | + +} + +**ControlType ::= ENUMERATED {** + +sCPOverloaded(0), + manuallyInitiated(1), + destinationOverload(2) + -- other values FFS + } + +**CorrelationID ::= Digits** + +- used by SCF for correlation with a previous operation. Refer to clause 3 for a description of the +- procedures associated with this parameter. + +**CounterAndValue ::= SEQUENCE {** + +| | | | +|--------------|-----|------------| +| counterID | [0] | CounterID, | +| counterValue | [1] | Integer4 | + +} + +**CounterID ::= INTEGER (0..99)** + +- Indicates the counters to be incremented. +- The counterIDs can be addressed by using the last digits of the dialled number. + +**CountersValue ::= SEQUENCE SIZE(0..numOfCounters) OF CounterAndValue** + +**CutAndPaste ::= INTEGER (0..22)** + +- Indicates the number of digits to be deleted. Refer to 6.4.2.16/Q.1214 for additional information. + +**DateAndTime ::= OCTET STRING (SIZE(6))** + +- Indicates, amongst others, the start time for activate service filtering. Coded as YYMMDDHHMMSS +- with each digit coded BCD. +- The first octet contains YY and the remaining items are sequenced following. +- For example, 1993 September 30th, 12:15:01 would be encoded as: + +| Bits | HGFE | DCBA | +|---------------|------|------| +| leading octet | 3 | 9 | +| -- | 9 | 0 | +| -- | 0 | 3 | +| -- | 2 | 1 | +| -- | 5 | 1 | +| -- | 1 | 0 | + +**DestinationRoutingAddress ::= SEQUENCE SIZE(1..3) OF CalledPartyNumber** + +- Indicates the list of Called Party Numbers (primary and alternates). + +**Digits ::= OCTET STRING (SIZE (minDigitsLength..maxDigitsLength))** + +- Indicates the address signalling digits. Refer to the Q.763 Generic Number and Generic Digits parameters +- for encoding. The coding of the subfields 'NumberQualifier' in Generic Number and 'TypeOfDigits' in +- Generic Digits are irrelevant to the INAP, the ASN.1 tags are sufficient to identify the parameter. +- The ISUP format does not allow to exclude these subfields, therefore the value is network operator specific. +- The following parameters should use Generic Number: +- CorrelationID for AssistRequestInstructions, AssistingSSPIPRoutingAddress for +- EstablishTemporaryConnection, calledAddressValue for all occurrences, callingAddressValue for all +- occurrences. The following parameters should use Generic Digits: prefix, all +- other CorrelationID occurrences, dialledNumber filtering criteria, callingLineID filtering criteria, lineID +- for ResourceID type, digitResponse for ReceivedInformationArg. + +**DisplayInformation ::= IA5String (SIZE (minDisplayInformationLength.. +maxDisplayInformationLength))** + +- Indicates the display information. + +**DpSpecificCriteria ::= CHOICE {** + +| | | | +|-------------------------|-----|-------------------------| +| numberOfDigits | [0] | NumberOfDigits, | +| applicationTimer | [1] | ApplicationTimer | +| } | | | + +- *The SCF may specify the number of digits to be collected by the SSF for the CollectedInfo event.* +- *When all digits are collected, the SSF reports the event to the SCF.* +- *The SCF may set a timer in the SSF for the No Answer event. If the user does not answer the call within the allotted time, the SSF reports the event to the SCF.* + +**Duration ::= INTEGER (-2..86400)** + +- *Values are seconds.* + +**ErrorTreatment ::= ENUMERATED {** + +| | +|-----------------------------| +| reportErrorToScf(0), | +| help(1), | +| repeatPrompt(2) | +| } | + +- *reportErrorToScf means returning the "ImproperCallerResponse" error in the event of an error condition during collection of user info.* + +**EventSpecificInformationBCSM ::= CHOICE {** + +| | | | | | +|---------------------------------------|------|---------------------------------------|-----|--------------------------| +| collectedInfoSpecificInfo | [0] | SEQUENCE { | | | +| | | calledPartynumber | [0] | CalledPartyNumber | +| | | -- ... -- | | | +| | | }, | | | +| analyzedInfoSpecificInfo | [1] | SEQUENCE { | | | +| | | calledPartynumber | [0] | CalledPartyNumber | +| | | -- ... -- | | | +| | | }, | | | +| routeSelectFailureSpecificInfo | [2] | SEQUENCE { | | | +| | | failureCause | [0] | Cause OPTIONAL | +| | | -- ... -- | | | +| | | }, | | | +| oCalledPartyBusySpecificInfo | [3] | SEQUENCE { | | | +| | | busyCause | [0] | Cause OPTIONAL | +| | | -- ... -- | | | +| | | }, | | | +| oNoAnswerSpecificInfo | [4] | SEQUENCE { | | | +| | | -- no specific info defined -- | | | +| | | -- ... -- | | | +| | | }, | | | +| oAnswerSpecificInfo | [5] | SEQUENCE { | | | +| | | -- no specific info defined -- | | | +| | | -- ... -- | | | +| | | }, | | | +| oMidCallSpecificInfo | [6] | SEQUENCE { | | | +| | | connectTime | [0] | Integer4 OPTIONAL | +| | | -- ... -- | | | +| | | }, | | | +| oDisconnectSpecificInfo | [7] | SEQUENCE { | | | +| | | releaseCause | [0] | Cause OPTIONAL, | +| | | connectTime | [1] | Integer4 OPTIONAL | +| | | -- ... -- | | | +| | | }, | | | +| tBusySpecificInfo | [8] | SEQUENCE { | | | +| | | busyCause | [0] | Cause OPTIONAL | +| | | -- ... -- | | | +| | | }, | | | +| tNoAnswerSpecificInfo | [9] | SEQUENCE { | | | +| | | -- no specific info defined -- | | | +| | | -- ... -- | | | +| | | }, | | | +| tAnswerSpecificInfo | [10] | SEQUENCE { | | | +| | | -- no specific info defined -- | | | +| | | -- ... -- | | | +| | | }, | | | + +``` + +tMidCallSpecificInfo [11] SEQUENCE { + connectTime [0] Integer4 OPTIONAL + -- ... -- +}, +tDisconnectSpecificInfo [12] SEQUENCE { + releaseCause [0] Cause OPTIONAL, + connectTime [1] Integer4 OPTIONAL + -- ... -- +} +} + +``` + +- Indicates the call related information specific to the event. +- The connectTime indicates the duration between the received answer indication from the called party side and the release of the connection for ODisconnect, OException, TDisconnect, or TException events. +- The unit for the connectTime is 100 milliseconds. + +**EventSpecificInformationCharging ::= OCTET STRING (SIZE (minEventSpecificInformationChargingLength..maxEventSpecificInformationChargingLength))** + +- defined by network operator. +- Indicates the charging related information specific to the event. +- An example data type definition for this parameter is given below: +- chargePulses [0] Integer4, +- chargeMessages [1] OCTET STRING (SIZE (min..max)) + +**EventTypeBCSM ::= ENUMERATED {** + +``` + +origAttemptAuthorized(1), +collectedInfo(2), +analysedInformation(3), +routeSelectFailure(4), +oCalledPartyBusy(5), +oNoAnswer(6), +oAnswer(7), +oMidCall(8), +oDisconnect(9), +oAbandon(10), +termAttemptAuthorized(12), +tBusy(13), +tNoAnswer(14), +tAnswer(15), +tMidCall(16), +tDisconnect(17), +tAbandon(18) +} + +``` + +- Indicates the BCSM detection point event. Refer to 4.2.2.2/Q.1214 for additional information on the events. Values origAttemptAuthorized and termAttemptAuthorized can only be used for TDPs. + +**EventTypeCharging ::= OCTET STRING (SIZE (minEventTypeChargingLength..maxEventTypeChargingLength))** + +- This parameter indicates the charging event type. Its content is network operator specific. +- +- An example data type definition for this parameter is given below: +- EventTypeCharging ::= ENUMERATED { +- chargePulses (0), +- chargeMessages (1) +- } + +**ExtensionField ::= SEQUENCE {** + +``` + +type INTEGER, -- shall identify the value of an EXTENSION type +criticality ENUMERATED { + ignore (0), + abort (1) +} DEFAULT ignore, +value [1] ANY DEFINED BY type +} + +``` + +- This parameter indicates an extension of an argument data type. Its content is network operator specific. + +**FacilityGroup ::= CHOICE {** + +| | | | +|--------------------------|------------|----------------------| +| trunkGroupID | [0] | INTEGER, | +| privateFacilityID | [1] | INTEGER, | +| huntGroup | [2] | OCTET STRING, | +| routeIndex | [3] | OCTET STRING | + +**}** + +-- Indicates the particular group of facilities to route the call. *huntGroup* and *routeIndex* are encoded as network operator specific. + +**FacilityGroupMember ::= INTEGER** + +-- Indicates the specific member of a trunk group or multi-line hunt group. + +**FCIBillingChargingCharacteristics ::= OCTET STRING (SIZE (minFCIBillingChargingLength..maxFCIBillingChargingLength))** + +-- This parameter indicates the billing and/or charging characteristics. Its content is network operator specific. An example datatype definition for this parameter is given below: + +**FCIBillingChargingCharacteristics ::= CHOICE {** + +| | | | +|-------------------------------|------------|-------------------------------------------------------| +| completeChargingrecord | [0] | OCTET STRING (SIZE (min..max)), | +| correlationID | [1] | CorrelationID, | +| scenario2Dot3 | [2] | SEQUENCE { | +| | | chargeParty [0] LegID OPTIONAL, | +| | | chargeLevel [1] OCTET STRING (SIZE (min..max)) | +| | | OPTIONAL, | +| | | chargeItems [2] SET OF Attribute OPTIONAL | +| | | } | + +**}** + +-- Depending on the applied charging scenario, the following information elements can be included + +-- (refer to Q.1214 Appendix II): + +-- complete charging record (scenario 2.2) + +-- charge party (scenario 2.3) + +-- charge level (scenario 2.3) + +-- charge items (scenario 2.3) + +-- correlationID (scenario 2.4) + +**FeatureCode ::= LocationNumber** + +-- The two-digit feature code preceded by "\*" or "11". + +-- Uses the LocationNumber format which is based on the Q.763 Location Number format. + +-- The Nature of Address indicator field shall be set to "Spare" (value 00000000). + +-- The Numbering Plan Indicator field shall be set to "Spare" (value 000). + +-- Used for stimulus signalling (Q.932). + +**FeatureRequestIndicator ::= ENUMERATED {** + +**hold(0),** +**retrieve(1),** +**featureActivation(2),** +**spare1(3),** +**sparen(127)** + +**}** + +-- Indicates the feature activated (e.g. a switch-hook flash, feature activation). Spare values reserved for future use. + +**FilteredCallTreatment ::= SEQUENCE {** + +| | | | +|-----------------------------------------|------------|------------------------------------------| +| sFBillingChargingCharacteristics | [0] | SFBillingChargingCharacteristics, | +| informationToSend | [1] | InformationToSend OPTIONAL, | +| maximumNumberOfCounters | [2] | MaximumNumberOfCounters OPTIONAL, | +| releaseCause | [3] | Cause OPTIONAL | + +**}** + +-- If *releaseCause* is not present, the default value is the same as the ISUP cause value decimal 31. + +-- If *informationToSend* is present, the call will be released after the end of the announcement with the indicated or default *releaseCause*. + +-- If *maximumNumberOfCounters* is not present, ServiceFilteringResponse will be sent with + +-- *CountersValue* ::= SEQUENCE SIZE (0) OF *CountersAndValue*. + +**FilteringCharacteristics ::= CHOICE {** + +| | | | +|----------------------|------------|-----------------------------| +| interval | [0] | INTEGER (-1..32000), | +| numberOfCalls | [1] | Integer4 | + +**}** + +- Indicates the severity of the filtering and the point in time when the ServiceFilteringResponse is to be sent. +- If = interval, every interval of time the next call leads to an InitialDP and a ServiceFilteringResponse is sent to the SCF. The interval is specified in seconds. +- If = NumberOfCalls, every N calls the Nth call leads to an InitialDP and a ServiceFilteringResponse is sent to the SCF. +- If ActivateServiceFiltering implies several counters – filtering on several dialled numbers –, the numberOfCalls would include calls to all the dialled numbers. + +**FilteringCriteria ::= CHOICE {** + +| | | | | +|---------------------|------|----------------|-----------| +| dialledNumber | [0] | Digits, | | +| callingLineID | [1] | Digits, | | +| serviceKey | [2] | ServiceKey, | | +| addressAndService | [30] | SEQUENCE { | | +| calledAddressValue | [0] | Digits, | | +| serviceKey | [1] | ServiceKey, | | +| callingAddressValue | [2] | Digits | OPTIONAL, | +| locationNumber | [3] | LocationNumber | OPTIONAL | +| | | } | | + +- In case calledAddressValue is specified, the numbers to be filtered are from calledAddressValue up to and including calledAddressValue + maximumNumberOfCounters-1. +- The last two digits of calledAddressvalue can not exceed 100-maximumNumberOfCounters. + +**FilteringTimeOut ::= CHOICE {** + +| | | | | +|----------|-----|-------------|--| +| duration | [0] | Duration, | | +| stopTime | [1] | DateAndTime | | + +- Indicates the maximum duration of the filtering. When the timer expires, a ServiceFilteringResponse is sent to the SCF. + +**ForwardCallIndicators ::= OCTET STRING (SIZE(2))** + +- Indicates the Forward Call Indicators. Refer to Recommendation Q.763 for encoding. + +**ForwardingCondition ::= ENUMERATED {** + +| | | +|--------------|--| +| busy(0), | | +| noanswer(1), | | +| any(2) | | + +- Indicates the condition that must be met to complete the connect. + +**GapCriteria ::= CHOICE {** + +| | | | | +|--------------------------|------|----------------|----------| +| calledAddressValue | [0] | Digits, | | +| gapOnService | [2] | GapOnService, | | +| calledAddressAndService | [29] | SEQUENCE { | | +| calledAddressValue | [0] | Digits, | | +| serviceKey | [1] | ServiceKey | | +| | | }, | | +| callingAddressAndService | [30] | SEQUENCE { | | +| callingAddressValue | [0] | Digits, | | +| serviceKey | [1] | ServiceKey, | | +| locationNumber | [2] | LocationNumber | OPTIONAL | +| | | } | | + +- Both calledAddressValue and callingAddressValue can be incomplete numbers, in the sense that a limited amount of digits can be given. +- +- For the handling of numbers starting with the same digit string, refer to the detailed procedure of the CallGap operation in 3.3. + +**GapOnService ::= SEQUENCE {** + +| | | | | +|------------|-----|---------------|----------| +| serviceKey | [0] | ServiceKey, | | +| dpCriteria | [1] | EventTypeBCSM | OPTIONAL | + +**GapIndicators ::= SEQUENCE {** + +| | | +|--------------------|----------------------| +| duration | [0] Duration, | +| gapInterval | [1] Interval | +| } | | + +-- Indicates the gapping characteristics. No gapping when gapInterval equals 0, and gap all calls when gapInterval equals 1. + +**GapTreatment ::= CHOICE {** + +| | | +|--------------------------|-------------------------------------------------| +| informationToSend | [0] InformationToSend, | +| releaseCause | [1] Cause, | +| both | [2] SEQUENCE { | +| | informationToSend [0] InformationToSend, | +| | releaseCause [1] Cause | +| | } | +| } | | + +-- The default value for Cause is the same as in ISUP. + +**HighLayerCompatibility ::= OCTET STRING (SIZE (highLayerCompatibilityLength))** + +-- Indicates the teleservice. For encoding, DSS 1 (Q.931) is used. + +**HoldCause ::= OCTET STRING** -- defined by network operator. + +-- Indicates the cause for holding the call. + +**InbandInfo ::= SEQUENCE {** + +| | | | +|----------------------------|-------------------------------|------------------| +| messageID | [0] MessageID, | | +| numberOfRepetitions | [1] INTEGER (1..127) | OPTIONAL, | +| duration | [2] INTEGER (0..32767) | OPTIONAL, | +| interval | [3] INTEGER (0..32767) | OPTIONAL | +| } | | | + +-- Interval is the time in seconds between each repeated announcement. Duration is the total + +-- amount of time in seconds, including repetitions and intervals. + +-- The end of announcement is either the end of duration or numberOfRepetitions, whatever comes first. + +-- Duration with value 0 indicates infinite duration. + +**InformationToSend ::= CHOICE {** + +| | | +|---------------------------|-------------------------------| +| inbandInfo | [0] InbandInfo, | +| tone | [1] Tone, | +| displayInformation | [2] DisplayInformation | +| } | | + +**Integer4 ::= INTEGER (0..2147483647)** + +**Interval ::= INTEGER (-1..60000)** + +-- Units are milliseconds. A -1 value denotes infinite. + +**InvokeID ::= InvokeIdType** + +-- Operation invoke identifier. + +**IPAvailable ::= OCTET STRING (SIZE (minIPAvailableLength..maxIPAvailableLength))** + +-- defined by network operator. + +-- Indicates that the resource is available. + +**IPRoutingAddress ::= CalledPartyNumber** + +-- Indicates the routing address for the IP. + +**IPSSPCapabilities ::= OCTET STRING (SIZE (minIPSSPCapabilitiesLength..maxIPSSPCapabilitiesLength))** + +-- defined by network operator. + +-- Indicates the SRF resources available at the SSP. + +**ISDNAccessRelatedInformation ::= OCTET STRING** + +-- Indicates the destination user network interface related information. Refer to the Q.763 Access + +-- Transport parameter for encoding. + +**LegID ::= CHOICE {** + +| | | +|------------------------|---------------------| +| sendingSideID | [0] LegType, | +| receivingSideID | [1] LegType | +| } | | + +-- Indicates a reference to a specific party in a call. OPTIONAL denotes network operator specific use + -- with a choice of unilateral ID assignment or bilateral ID assignment. + -- OPTIONAL for LegID also denotes the following: + -- -- when only one party exists in the call, this parameter is not needed (as no ambiguity exists); + -- -- when more than one party exists in the call, one of the following alternatives applies: + -- 1. LegID is present and indicates which party is concerned. + -- 2. LegID is not present and a default value is assumed (e.g. calling party in the case of the ApplyCharging operation). + -- Choice between these two alternatives is kept a network operator option. + +**LegType ::= OCTET STRING (SIZE(1))** + +**leg1 LegType ::= '01'H** + +**leg2 LegType ::= '02'H** + +**LocationNumber ::= OCTET STRING (SIZE (minLocationNumberLength.. + maxLocationNumberLength))** + +-- Indicates the Location Number for the calling party. Refer to Recommendation Q.763 (White book) for encoding. + +**MaximumNumberOfCounters ::= INTEGER (1..numOfCounters)** + +**MessageID ::= CHOICE {** +     **elementaryMessageID [0] Integer4,** +     **text [1] SEQUENCE {** +         **messageContent [0] IA5String (SIZE** +         **(minMessageContentLength..** +         **maxMessageContentLength)),** +         **attributes [1] OCTET STRING (SIZE (** +         **minAttributesLength..** +         **maxAttributesLength))** +         **OPTIONAL** +     **},** +     **elementaryMessageIDs [29] SEQUENCE SIZE (1..numOfMessageIDs) OF Integer4,** +     **variableMessage [30] SEQUENCE {** +         **elementaryMessageID [0] Integer4,** +         **variableParts [1] SEQUENCE SIZE (1..5)** +         **OF VariablePart** +     **}** +**}** + +-- OPTIONAL denotes network operator specific use. + +**MiscCallInfo ::= SEQUENCE {** +     **messageType [0] ENUMERATED {** +         **request(0),** +         **notification(1)** +     **},** +     **dpAssignment [1] ENUMERATED {** +         **individualLine(0),** +         **groupBased(1),** +         **officeBased(2)** +     **}** +     **OPTIONAL** +**}** + +-- Indicates detection point related information. + +**MonitorMode ::= ENUMERATED {** +     **interrupted(0),** +     **notifyAndContinue(1),** +     **transparent(2)** +**}** + +-- Indicates the event is relayed and/or processed by the SSP. + -- If this parameter is used in the context of charging events, the following definitions apply for the handling of charging events: + -- Interrupted means that the SSF notifies the SCF of the charging event using + -- EventNotificationCharging, does not process the event but discard it. + +-- *NotifyAndContinue means that SSF notifies the SCF of the charging event using* +-- *EventNotificationCharging, and continues processing the event or signal without waiting for SCF* +-- *instructions. Transparent means that the SSF does not notify the SCF of the event. This value is used to* +-- *end the monitoring of a previously requested charging event. Previously requested charging events are* +-- *monitored until ended by a transparent monitor mode, or until the end of the connection configuration.* +-- *For the use of this parameter in the context of BCSM events refer to 3.3.39.* + +**NumberingPlan ::= OCTET STRING (SIZE(1))** + +-- *Indicates the numbering plan for collecting the user information. Refer to the Q.763 Numbering Plan.* +-- *Indicator field for encoding.* + +**NumberOfDigits ::= INTEGER (1..255)** + +-- *Indicates the number of digits to be collected* + +**OriginalCalledPartyID ::= OCTET STRING (SIZE (minOriginalCalledPartyIDLength.. +maxOriginalCalledPartyIDLength))** + +-- *Indicates the original called number. Refer to the Q.763 Original Called Number for encoding.* + +**RedirectingPartyID ::= OCTET STRING (SIZE (minRedirectingPartyIDLength.. +maxRedirectingPartyIDLength))** + +-- *Indicates redirecting number. Refer to the Q.763 Redirecting number for encoding.* + +**RedirectionInformation ::= OCTET STRING (SIZE(2))** + +-- *Indicates redirection information. Refer to the Q.763 Redirection Information for encoding.* + +**ReportCondition ::= ENUMERATED {** +    statusReport(0), +    timerExpired(1), +    canceled(2) +**}** + +-- *ReportCondition specifies the cause of sending "StatusReport" operation to the SCF.* + +**RequestedInformationList ::= SEQUENCE SIZE (1..numOfInfoItems) OF RequestedInformation** + +**RequestedInformationTypeList ::= SEQUENCE SIZE (1..numOfInfoItems) OF +    RequestedInformationType** + +**RequestedInformation ::= SEQUENCE {** +    requestedInformationType          [0] RequestedInformationType, +    requestedInformationValue         [1] RequestedInformationValue +**}** + +**RequestedInformationType ::= ENUMERATED {** +    callAttemptElapsedTime(0), +    callStopTime(1), +    callConnectedElapsedTime(2), +    calledAddress(3), +    releaseCause(30) +**}** + +**RequestedInformationValue ::= CHOICE {** +    callAttemptElapsedTimeValue     [0] INTEGER (0..255), +    callStopTimeValue                 [1] DateAndTime, +    callConnectedElapsedTimeValue   [2] Integer4, +    calledAddressValue                [3] Digits, +    releaseCauseValue                 [30] Cause +**}** + +-- *The callAttemptElapsedTimeValue is specified in seconds. The unit for the* +-- *callConnectedElapsedTimeValue is 100 milliseconds.* + +**ResourceID ::= CHOICE {** +    lineID                                [0] Digits, +    facilityGroupID                    [1] FacilityGroup, + +``` + +facilityGroupMemberID [2] INTEGER, +trunkGroupID [3] INTEGER +} + +``` + +-- Indicates a logical identifier for the physical termination resource. + +``` + +ResourceStatus ::= ENUMERATED { + busy(0), + idle(1) +} + +``` + +``` + +ResponseCondition ::= ENUMERATED { + intermediateResponse(0), + lastResponse(1) +} + +``` + +-- additional values are for further study. + +-- ResponseCondition is used to identify the reason why ServiceFilteringResponse operation is sent. +-- intermediateResponse identifies that service filtering is running and the interval time is expired and +-- a call is received, or that service filtering is running and the threshold value is reached. +-- lastResponse identifies that the duration time is expired and service filtering has been finished or +-- that the stop time is met and service filtering has been finished. + +``` + +RouteList ::= SEQUENCE SIZE(1..3) OF OCTET STRING (SIZE + (minRouteListLength..maxRouteListLength)) + +``` + +-- Indicates a list of trunk groups or a route index. See Recommendation Q.1214 for additional information on this item. + +``` + +ScfID ::= OCTET STRING (SIZE (minScfIDLength..maxScfIDLength)) + +``` + +-- defined by network operator. +-- Indicates the SCF identifier. + +``` + +SCIBillingChargingCharacteristics ::= OCTET STRING (SIZE (minSCIBillingChargingLength.. + maxSCIBillingChargingLength)) + +``` + +-- This parameter indicates the billing and/or charging characteristics. Its content is network operator +-- specific. An example datatype definition for this parameter is given below: +-- SCIBillingChargingCharacteristics ::= CHOICE { +-- chargeLevel [0] OCTET STRING (SIZE (min..max)), +-- chargePulses [1] Integer4, +-- chargeMessages [2] OCTET STRING (SIZE (min..max)) +-- } +-- Depending on the applied charging scenario the following information elements +-- can be included (refer to Appendix II/Q.1214): +-- chargeLevel (scenario 3.2) +-- chargePulses (scenario 3.2) +-- chargeMessages (scenario 3.2) + +``` + +ServiceAddressInformation ::= SEQUENCE { + serviceKey [0] ServiceKey OPTIONAL, + miscCallInfo [1] MiscCallInfo, + triggerType [2] TriggerType OPTIONAL +} + +``` + +-- Information that represents the result of trigger analysis and allows the SCF to choose the appropriate +-- service logic. + +``` + +ServiceInteractionIndicators ::= OCTET STRING (SIZE ( minServiceInteractionIndicatorsLength.. + maxServiceInteractionIndicatorsLength)) + +``` + +-- Indicators which are exchanged between SSP and SCP to resolve interactions between IN based services +-- and network based services, respectively between different IN based services. +-- The contents are network specific and identified as a subject for further study with respect to INAP. +-- The following example is listed to illustrate the use of this parameter: +-- CallToBeDiverted Allowed/NotAllowed Indicator + +-- If the CallToBeDiverted indicator is set to NotAllowed, the destination exchange shall not allow any +-- diversion on the subjected call. By this, each service can pass the applicable indicators to inform the +-- destination exchange of how specific services are to be handled. + +**ServiceKey ::= Integer4** + +-- Information that allows the SCF to choose the appropriate service logic. + +**ServiceProfileIdentifier ::= OCTET STRING** + +-- Indicates a particular ISDN terminal. Refer to Recommendation Q.932 for encoding. + +**ServingAreaID ::= LocationNumber** + +-- Identifies the local serving area where a network provider operates. Uses the LocationNumber +-- format which is based on the Q.763 Location Number format. +-- The Nature of Address indicator field shall be set to "Spare" (value 00000000). +-- The Numbering Plan Indicator field shall be set to "Spare" (value 000). +-- Defined by the network operator. + +**SFBillingChargingCharacteristics ::= OCTET STRING (SIZE (minSFBillingChargingLength.. +maxSFBillingChargingLength))** + +-- This parameter indicates the billing and/or charging characteristics for filtered calls. +-- Its content is network operator specific. + +**TerminalType ::= ENUMERATED {** +    unknown(0), +    dialPulse(1), +    dtmf(2), +    isdn(3), +    isdnNoDtmf(4), +    spare(16) +} + +-- Identifies the terminal type so that the SCF can specify, to the SRF, the appropriate type of capability +-- (voice recognition, DTMF, display capability, etc.). Since present signalling systems do not convey +-- terminal type, this parameter applies only at originating or terminating local exchanges. + +**TimerID ::= ENUMERATED {** +    tssf(0) +    -- others ffs +} + +-- Indicates the timer to be reset. + +**TimerValue ::= Integer4** + +-- Indicates the timer value (in seconds). + +**Tone ::= SEQUENCE {** +    toneID                                                    [0] Integer4, +    duration                                                 [1] Integer4                                                    OPTIONAL +} + +-- The duration specifies the length of the tone in seconds, value 0 indicates infinite duration. + +**TravellingClassMark ::= LocationNumber** + +-- Indicates travelling class mark information. +-- Uses the LocationNumber format which is based on the Q.763 Location Number format. +-- The Nature of Address indicator field shall be set to "Spare" (value 00000000). +-- The Numbering Plan Indicator field shall be set to "Spare" (value 000). +-- Maximum 2 digits. + +**TriggerType ::= ENUMERATED {** +    featureActivation(0), +    verticalServiceCode(1), +    customizedAccess(2), + +``` + +customizedIntercom(3), +emergencyService(12), +aFR(13), +sharedIOTrunk(14), +offHookDelay(17), +channelSetupPRI(18), +tNoAnswer(25), +tBusy(26), +oCalledPartyBusy(27), +oNoAnswer(29), +originationAttemptAuthorized(30), +oAnswer(31), +oDisconnect(32), +termAttemptAuthorized(33), +tAnswer(34), +tDisconnect(35) +-- Private (ffs) +} + +``` + +-- The type of trigger which caused call suspension +-- 4-11: Reserved; 15,16: Reserved; 19-24: Reserved + +``` + +UnavailableNetworkResource ::= ENUMERATED { + unavailableResources(0), + componentFailure(1), + basicCallProcessingException(2), + resourceStatusFailure(3), + endUserFailure(4) +} + +``` + +-- Indicates the network resource that failed. + +``` + +VariablePart ::= CHOICE { + integer [0] Integer4, + number [1] Digits, -- Generic digits + time [2] OCTET STRING (SIZE(2)), -- HH:MM, BCD coded + date [3] OCTET STRING (SIZE(3)), -- YYMMDD, BCD coded + price [4] OCTET STRING (SIZE(4)) +} + +``` + +-- Indicates the variable part of the message. +-- BCD coded variable parts are encoded as described in the examples below. +-- For example, time = 12:15 would be encoded as: + +| Bits | HGFE | DCBA | +|---------------|------|------| +| leading octet | 2 | 1 | +| | 5 | 1 | + +-- date = 1993 September 30th would be encoded as: + +| Bits | HGFE | DCBA | +|---------------|------|------| +| leading octet | 3 | 9 | +| | 9 | 0 | +| | 0 | 3 | + +-- The Definition of range of constants Follows + +| | | | +|------------------------------|---------------|---------------------| +| highLayerCompatibilityLength | INTEGER ::= 2 | | +| minAChBillingChargingLength | INTEGER ::= | -- network specific | +| maxAChBillingChargingLength | INTEGER ::= | -- network specific | +| minAttributesLength | INTEGER ::= | -- network specific | +| maxAttributesLength | INTEGER ::= | -- network specific | +| maxBearerCapabilityLength | INTEGER ::= | -- network specific | +| minCalledPartyNumberLength | INTEGER ::= | -- network specific | +| maxCalledPartyNumberLength | INTEGER ::= | -- network specific | +| minCallingPartyNumberLength | INTEGER ::= | -- network specific | +| maxCallingPartyNumberLength | INTEGER ::= | -- network specific | +| minCallResultLength | INTEGER ::= | -- network specific | +| maxCallResultLength | INTEGER ::= | -- network specific | + +``` + +minCauseLength INTEGER ::= 2 +maxCauseLength INTEGER ::= -- network specific +minDigitsLength INTEGER ::= -- network specific +maxDigitsLength INTEGER ::= -- network specific +minDisplayInformationLength INTEGER ::= -- network specific +maxDisplayInformationLength INTEGER ::= -- network specific +minEventSpecificInformationChargingLength INTEGER ::= -- network specific +maxEventSpecificInformationChargingLength INTEGER ::= -- network specific +minEventTypeChargingLength INTEGER ::= -- network specific +maxEventTypeChargingLength INTEGER ::= -- network specific +minFCIBillingChargingLength INTEGER ::= -- network specific +maxFCIBillingChargingLength INTEGER ::= -- network specific +minIPAvailableLength INTEGER ::= -- network specific +maxIPAvailableLength INTEGER ::= -- network specific +minIPSSPCapabilitiesLength INTEGER ::= -- network specific +maxIPSSPCapabilitiesLength INTEGER ::= -- network specific +minLocationNumberLength INTEGER ::= -- network specific +maxLocationNumberLength INTEGER ::= -- network specific +minMessageContentLength INTEGER ::= -- network specific +maxMessageContentLength INTEGER ::= -- network specific +minOriginalCalledPartyIDLength INTEGER ::= -- network specific +maxOriginalCalledPartyIDLength INTEGER ::= -- network specific +minRedirectingPartyIDLength INTEGER ::= -- network specific +maxRedirectingPartyIDLength INTEGER ::= -- network specific +minRouteListLength INTEGER ::= -- network specific +maxRouteListLength INTEGER ::= -- network specific +minScfIDLength INTEGER ::= -- network specific +maxScfIDLength INTEGER ::= -- network specific +minSCIBillingChargingLength INTEGER ::= -- network specific +maxSCIBillingChargingLength INTEGER ::= -- network specific +minServiceInteractionIndicatorsLength INTEGER ::= -- network specific +maxServiceInteractionIndicatorsLength INTEGER ::= -- network specific +minSFBillingChargingLength INTEGER ::= -- network specific +maxSFBillingChargingLength INTEGER ::= -- network specific +numOfBCSMEEvents INTEGER ::= -- network specific +numOfChargingEvents INTEGER ::= -- network specific +numOfCounters INTEGER ::= 100 +numOfExtensions INTEGER ::= -- network specific +numOfInfoItems INTEGER ::= 5 +numOfMessageIDs INTEGER ::= -- network specific +END + +``` + +#### 2.1.4 IN CS-1 application protocol (operation and error codes) + +-- This module contains the operation and error code assignments for the IN CS-1 application protocol. + +``` +IN-CS-1-Codes { ccitt recommendation q 1218 modules(0) cs-1-codes(3) version1(0) } +``` + +``` +DEFINITIONS ::= +``` + +``` +BEGIN +``` + +-- OPERATION AND ERROR CODE ASSIGNMENTS FOR THE IN CS-1 PROTOCOL + +-- FOLLOW + +``` +IMPORTS +``` + +-- macros + +``` +APPLICATION-SERVICE-ELEMENT +``` + +``` +FROM Remote-Operations-Notation-Extension +``` + +{joint-iso-ccitt                remote-operations(4)                notation-extension(2)} + +-- operation types + +ActivateServiceFiltering, +ActivityTest, +AnalysedInformation, +AnalyseInformation, +ApplyCharging, +ApplyChargingReport, +AssistRequestInstructions, +CallGap, +CallInformationReport, +CallInformationRequest, +Cancel, +CancelStatusReportRequest, +CollectedInformation, +CollectInformation, +Connect, +ConnectToResource, +Continue, +DisconnectForwardConnection, +EstablishTemporaryConnection, +EventNotificationCharging, +EventReportBCSM, +FurnishChargingInformation, +HoldCallInNetwork, +InitialDP, +InitiateCallAttempt, +OAnswer, +OCalledPartyBusy, +ODisconnect, +OMidCall, +ONoAnswer, +OriginationAttemptAuthorized, +PlayAnnouncement, +PromptAndCollectUserInfoInformation, +ReleaseCall, +RequestCurrentStatusReport, +RequestEveryStatusChangeReport, +RequestFirstStatusMatchReport, +RequestNotificationChargingEvent, +RequestReportBCSMEVENT, +ResetTimer, +RouteSelectFailure, +SelectFacility, +SelectRoute, +SendChargingInformation, +ServiceFilteringResponse, +SpecializedResourceReport, +StatusReport, +TAnswer, +TBusy, +TDisconnect, +TermAttemptAuthorized, +TMidCall, +TNoAnswer + +FROM IN-CS-1-Operations { ccitt recommendation q 1218 modules(0) cs-1-operations(0) version1(0) } + +-- error types + +Canceled, +CancelFailed, +ETCFailed, +ImproperCallerResponse, +MissingCustomerRecord, +MissingParameter, +ParameterOutOfRange, +RequestedInfoError, + +SystemFailure, + TaskRefused, + UnavailableResource, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter, + UnknownLegID, + UnknownResource + +FROM IN-CS-1-Errors { ccitt recommendation q 1218 modules(0) cs-1-errors(1) version1(0) }; + +-- *the operations are grouped by the identified ASEs.* + +-- *SCF activation ASE* + +| | | | +|------------------|------------------|-------------------------| +| initialDP | InitialDP | ::= localValue 0 | +|------------------|------------------|-------------------------| + +-- *Basic BCP DP ASE* + +| | | | +|-------------------------------------|-------------------------------------|--------------------------| +| originationAttemptAuthorized | OriginationAttemptAuthorized | ::= localValue 1 | +| collectedInformation | CollectedInformation | ::= localValue 2 | +| analysedInformation | AnalysedInformation | ::= localValue 3 | +| routeSelectFailure | RouteSelectFailure | ::= localValue 4 | +| oCalledPartyBusy | OCalledPartyBusy | ::= localValue 5 | +| oNoAnswer | ONoAnswer | ::= localValue 6 | +| oAnswer | OAnswer | ::= localValue 7 | +| oDisconnect | ODisconnect | ::= localValue 8 | +| termAttemptAuthorized | TermAttemptAuthorized | ::= localValue 9 | +| tBusy | TBusy | ::= localValue 10 | +| tNoAnswer | TNoAnswer | ::= localValue 11 | +| tAnswer | TAnswer | ::= localValue 12 | +| tDisconnect | TDisconnect | ::= localValue 13 | + +-- *Advanced BCP DP ASE* + +| | | | +|-----------------|-----------------|--------------------------| +| oMidCall | OMidCall | ::= localValue 14 | +| tMidCall | TMidCall | ::= localValue 15 | + +-- *SCF/SRF activation of assist ASE* + +| | | | +|----------------------------------|----------------------------------|--------------------------| +| assistRequestInstructions | AssistRequestInstructions | ::= localValue 16 | +|----------------------------------|----------------------------------|--------------------------| + +-- *Assist connection establishment ASE* + +| | | | +|-------------------------------------|-------------------------------------|--------------------------| +| establishTemporaryConnection | EstablishTemporaryConnection | ::= localValue 17 | +|-------------------------------------|-------------------------------------|--------------------------| + +-- *Generic disconnect resource ASE* + +| | | | +|------------------------------------|------------------------------------|--------------------------| +| disconnectForwardConnection | DisconnectForwardConnection | ::= localValue 18 | +|------------------------------------|------------------------------------|--------------------------| + +-- *Non-assisted connection establishment ASE* + +| | | | +|--------------------------|--------------------------|--------------------------| +| connectToResource | ConnectToResource | ::= localValue 19 | +|--------------------------|--------------------------|--------------------------| + +-- *Connect ASE (elementary SSF function)* + +| | | | +|----------------|----------------|--------------------------| +| connect | Connect | ::= localValue 20 | +|----------------|----------------|--------------------------| + +-- *Call handling ASE (elementary SSF function)* + +| | | | +|--------------------------|--------------------------|--------------------------| +| holdCallInNetwork | HoldCallInNetwork | ::= localValue 21 | +| releaseCall | ReleaseCall | ::= localValue 22 | + +-- *BCSM Event handling ASE* + +| | | | +|--------------------------------|--------------------------------|--------------------------| +| requestReportBCSMEEvent | RequestReportBCSMEEvent | ::= localValue 23 | +| eventReportBCSM | EventReportBCSM | ::= localValue 24 | + +| | | | +|--------------------------------------------|--------------------------------------------|--------------------------| +| -- Charging Event handling ASE | | | +| requestNotificationChargingEvent | RequestNotificationChargingEvent | ::= localValue 25 | +| eventNotificationCharging | EventNotificationCharging | ::= localValue 26 | +| -- SSF call processing ASE | | | +| collectInformation | CollectInformation | ::= localValue 27 | +| analyseInformation | AnalyseInformation | ::= localValue 28 | +| selectRoute | SelectRoute | ::= localValue 29 | +| selectFacility | SelectFacility | ::= localValue 30 | +| continue | Continue | ::= localValue 31 | +| -- SCF call initiation ASE | | | +| initiateCallAttempt | InitiateCallAttempt | ::= localValue 32 | +| -- Timer ASE | | | +| resetTimer | ResetTimer | ::= localValue 33 | +| -- Billing ASE | | | +| furnishChargingInformation | FurnishChargingInformation | ::= localValue 34 | +| -- Charging ASE | | | +| applyCharging | ApplyCharging | ::= localValue 35 | +| applyChargingReport | ApplyChargingReport | ::= localValue 36 | +| -- Status reporting ASE | | | +| requestCurrentStatusReport | RequestCurrentStatusReport | ::= localValue 37 | +| requestEveryStatusChangeReport | RequestEveryStatusChangeReport | ::= localValue 38 | +| requestFirstStatusMatchReport | RequestFirstStatusMatchReport | ::= localValue 39 | +| statusReport | StatusReport | ::= localValue 40 | +| -- Traffic management ASE | | | +| callGap | CallGap | ::= localValue 41 | +| -- Service management ASE | | | +| activateServiceFiltering | ActivateServiceFiltering | ::= localValue 42 | +| serviceFilteringResponse | ServiceFilteringResponse | ::= localValue 43 | +| -- Call report ASE | | | +| callInformationReport | CallInformationReport | ::= localValue 44 | +| callInformationRequest | CallInformationRequest | ::= localValue 45 | +| -- Signalling control ASE | | | +| sendChargingInformation | SendChargingInformation | ::= localValue 46 | +| -- Specialized resource control ASE | | | +| playAnnouncement | PlayAnnouncement | ::= localValue 47 | +| promptAndCollectUserInfoInformation | PromptAndCollectUserInfoInformation | ::= localValue 48 | +| specializedResourceReport | SpecializedResourceReport | ::= localValue 49 | +| -- Cancel ASE | | | +| cancel | Cancel | ::= localValue 53 | +| cancelStatusReportRequest | CancelStatusReportRequest | ::= localValue 54 | +| -- Activity Test ASE | | | +| activityTest | ActivityTest | ::= localValue 55 | + +-- *ERROR codes* + +| | | | +|-----------------------------|-----------------------------|-------------------| +| cancelled | Cancelled | ::= localValue 0 | +| cancelFailed | CancelFailed | ::= localValue 1 | +| eTCFailed | ETCFailed | ::= localValue 3 | +| improperCallerResponse | ImproperCallerResponse | ::= localValue 4 | +| missingCustomerRecord | MissingCustomerRecord | ::= localValue 6 | +| missingParameter | MissingParameter | ::= localValue 7 | +| parameterOutOfRange | ParameterOutOfRange | ::= localValue 8 | +| requestedInfoError | RequestedInfoError | ::= localValue 10 | +| systemFailure | SystemFailure | ::= localValue 11 | +| taskRefused | TaskRefused | ::= localValue 12 | +| unavailableResource | UnavailableResource | ::= localValue 13 | +| unexpectedComponentSequence | UnexpectedComponentSequence | ::= localValue 14 | +| unexpectedDataValue | UnexpectedDataValue | ::= localValue 15 | +| unexpectedParameter | UnexpectedParameter | ::= localValue 16 | +| unknownLegID | UnknownLegID | ::= localValue 17 | +| unknownResource | UnknownResource | ::= localValue 18 | + +-- *APPLICATION SERVICE ELEMENTS* + +**SCF-activation-ASE ::= APPLICATION-SERVICE-ELEMENT** + +-- *consumer is SSF* +**CONSUMER INVOKE {** +    initialDP +**}** +-- *supplier is SCF* +**SUPPLIER INVOKE** + +**SCF-SRF-activation-of-assist-ASE ::= APPLICATION-SERVICE-ELEMENT** + +-- *consumer is SSF/SRF* +**CONSUMER INVOKE {** +    assistRequestInstructions +**}** +-- *supplier is SCF* +**SUPPLIER INVOKE** + +**Assist-connection-establishment-ASE ::= APPLICATION-SERVICE-ELEMENT** + +-- *consumer is SSF* +**CONSUMER INVOKE** +-- *supplier is SCF* +**SUPPLIER INVOKE {** +    establishTemporaryConnection +**}** + +**Generic-disconnect-resource-ASE ::= APPLICATION-SERVICE-ELEMENT** + +-- *consumer is SSF* +**CONSUMER INVOKE** +-- *supplier is SCF* +**SUPPLIER INVOKE {** +    disconnectForwardConnection +**}** + +**Non-assisted-connection-establishment-ASE ::= APPLICATION-SERVICE-ELEMENT** + +-- *consumer is SSF* +**CONSUMER INVOKE** +-- *supplier is SCF* +**SUPPLIER INVOKE {** +    connectToResource +**}** + +**Connect-ASE ::= APPLICATION-SERVICE-ELEMENT** + +-- *consumer is SSF* +**CONSUMER INVOKE** +-- *supplier is SCF* +**SUPPLIER INVOKE {** +    connect +**}** + +``` + +BCSM-event-handling-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES { + eventReportBCSM + } + -- supplier is SCF + SUPPLIER INVOKES { + requestReportBCSMEven + } + +DP-specific-event-handling-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES { + originationAttemptAuthorized, + collectedInformation, + analyzedInformation, + routeSelectFailure, + oCalledPartyBusy, + oNoAnswer, + oAnswer, + oDisconnect, + termAttemptAuthorized, + TBusy, + tNoAnswer, + tAnswer, + tDisconnect, + oMidCall, + tMidCall + } + -- supplier is SCF + SUPPLIER INVOKES { + requestReportBCSMEven + } + +Charging-event-handling-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES { + eventNotificationCharging + } + -- supplier is SCF + SUPPLIER INVOKES { + requestNotificationChargingEvent + } + +SCF-call-initiation-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES + -- supplier is SCF + SUPPLIER INVOKES { + initiateCallAttempt + } + +Timer-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF/SRF + CONSUMER INVOKES + -- supplier is SCF + SUPPLIER INVOKES { + resetTimer + } + +Billing-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES + -- supplier is SCF + SUPPLIER INVOKES { + furnishChargingInformation + } + +``` + +``` + +Charging-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES { + applyChargingReport + } + -- supplier is SCF + SUPPLIER INVOKES { + applyCharging + } + +Traffic-management-ASE ::= APPLICATION-SERVICE-ELEMENT + --consumer is SSF + CONSUMER INVOKES + -- supplier is SCF + SUPPLIER INVOKES { + callGap + } + +Service-management-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES { + serviceFilteringResponse + } + -- supplier is SCF + SUPPLIER INVOKES { + activateServiceFiltering + } + +Call-report-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES { + callInformationReport + } + -- supplier is SCF + SUPPLIER INVOKES { + callInformationRequest + } + +Signalling-control-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES + -- supplier is SCF + SUPPLIER INVOKES { + sendChargingInformation + } + +Specialized-resource-control-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF/SRF + CONSUMER INVOKES { + specializedResourceReport + } + -- supplier is SCF + SUPPLIER INVOKES { + playAnnouncement, + promptAndCollectUserInformation + } + +Activity-test-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF/SRF + CONSUMER INVOKES + -- supplier is SCF + SUPPLIER INVOKES { + activityTest + } + +Basic-BCP-DP-ASE ::= APPLICATION-SERVICE-ELEMENT + -- consumer is SSF + CONSUMER INVOKES { + originationAttemptAuthorized, + collectedInformation, + } + +``` + +``` + +analyzedInformation, +routeSelectFailure, +oCalledPartyBusy, +oNoAnswer, +oAnswer, +oDisconnect, +termAttemptAuthorized, +tCalledPartyBusy, +tNoAnswer, +tAnswer, +tDisconnect +} +-- supplier is SCF +SUPPLIER INVOKES + +``` + +``` + +Advanced-BCP-DP-ASE ::= APPLICATION-SERVICE-ELEMENT +-- consumer is SSF +CONSUMER INVOKES { + oMidCall, + tMidCall +} +-- supplier is SCF +SUPPLIER INVOKES + +``` + +``` + +SSF-Call-Processing-ASE ::= APPLICATION-SERVICE-ELEMENT +-- consumer is SSF +CONSUMER INVOKES +-- supplier is SCF +SUPPLIER INVOKES { + collectInformation, + analyzeInformation, + selectRoute, + selectFacility, + continue +} + +``` + +``` + +Status-reporting-ASE ::= APPLICATION-SERVICE-ELEMENT +-- consumer is SSF +CONSUMER INVOKES { + statusReport +} +-- supplier is SCF +SUPPLIER INVOKES { + requestCurrentStatusReport, + requestEveryStatusChangeReport, + requestFirstStatusMatchReport +} + +``` + +``` + +Cancel-ASE ::= APPLICATION-SERVICE-ELEMENT +-- consumer is SSF/SRF +CONSUMER INVOKES +-- supplier is SCF +SUPPLIER INVOKES { + cancel, + cancelStatusReportRequest +} + +``` + +``` + +Call-handling-ASE ::= APPLICATION-SERVICE-ELEMENT +-- consumer is SSF +CONSUMER INVOKES +-- supplier is SCF +SUPPLIER INVOKES { + holdCallInNetwork, + releaseCall +} + +``` + +END + +### 2.1.5 Application Contexts + +APPLICATION-CONTEXT MACRO::= + +BEGIN +TYPE NOTATION ::= Symmetric | InitiatorConsumerOfResponderConsumerOf | empty +VALUE NOTATION ::= value(VALUE OBJECT IDENTIFIER) +Symmetric ::= "OPERATIONS OF" "{ASEList}" +InitiatorConsumerOf ::= "INITIATOR CONSUMER OF" "{ASEList}" | empty +ResponderConsumerOf ::= "RESPONDER CONSUMER OF" "{ASEList}" | empty +ASEList ::= ASE | ASEList "," ASE +ASE ::= type - shall reference an APPLICATION-SERVICE-ELEMENT type +END + +IN-CS1-SSF-to-SCF-Generic-AC APPLICATION-CONTEXT + +-- dialogue initiated by SSF with InitialDP operation + +INITIATOR CONSUMER OF { +    SCF-activation-ASE, +    Assist-connection-establishment-ASE, +    Generic-disconnect-resource-ASE, +    Non-assisted-connection-establishment-ASE, +    Connect-ASE, +    Call-handling-ASE, +    BCSM-event-handling-ASE, +    Charging-event-handling-ASE, +    SSF-call-processing-ASE, +    Timer-ASE, +    Billing-ASE, +    Charging-ASE, +    Traffic-management-ASE, +    Status-reporting-ASE, +    Call-report-ASE, +    Signalling-control-ASE, +    Specialized-resource-control-ASE, +    Cancel-ASE, +    Activity-test-ASE +} +RESPONDER CONSUMER OF +::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) generic-ssf-to-scf(0) version 1(0)}; + +IN-CS1-SSF-to-SCF-DP-specific-AC APPLICATION-CONTEXT + +-- dialogue initiated by SSF with DP Specific Initial Operation + +INITIATOR CONSUMER OF { +    Basic-BCP-DP-ASE, +    Advanced-BCP-DP-ASE, +    Assist-connection-establishment-ASE, +    Generic-disconnect-resource-ASE, +    Non-assisted-connection-establishment-ASE, +    Connect-ASE, +    Call-handling-ASE, +    DP-specific-event-handling-ASE, +    Charging-event-handling-ASE, +    SSF-call-processing-ASE, +    Timer-ASE, +    Billing-ASE, +    Charging-ASE, +    Traffic-management-ASE, +    Status-reporting-ASE, +    Call-report-ASE, +    Signalling-control-ASE, +    Specialized-resource-control-ASE, +    Cancel-ASE, +    Activity-test-ASE +} +RESPONDER CONSUMER OF +::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) dp-specific-ssf-to-scf(1) version 1(0)}; + +``` + +IN-CS1-assist-handoff-SSF-to-SCF-AC APPLICATION-CONTEXT +-- dialogue initiated by SSF with AssistRequestInstructions +INITIATOR CONSUMER OF { + SCF-SRF-activation-of-assist-ASE, + Generic-disconnect-resource-ASE, + Non-assisted-connection-establishment-ASE, + Call-handling ASE, + Timer-ASE, + Billing-ASE, + Charging-ASE, + Status-reporting-ASE, + Specialized-resource-control-ASE, + Cancel-ASE, + Activity-test-ASE +} +RESPONDER CONSUMER OF +::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) assist-handoff-ssf-to-scf(2) version 1(0)}; + +IN-CS1-SRF-to-SCF-AC APPLICATION-CONTEXT +-- dialogue initiated by SRF with AssistRequestInstructions +INITIATOR CONSUMER OF { + SCF-SRF-activation-of-assist-ASE, + Specialized-resource-control-ASE, + Cancel-ASE +} +RESPONDER CONSUMER OF +::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) srf-to-scf(3) version 1(0)}; + +IN-CS1-SCF-to-SSF-AC APPLICATION-CONTEXT +-- dialogue initiated by SCF with InitiateCallAttempt, Generic Case +INITIATOR CONSUMER OF +RESPONDER CONSUMER OF { + Assist-connection-establishment-ASE, + Generic-disconnect-resource-ASE, + Non-assisted-connection-establishment-ASE, + Connect-ASE, + Call-handling-ASE, + BCSM-event-handling-ASE, + Charging-event-handling-ASE, + SSF-call-processing-ASE, + SCF-call-initiation-ASE, + Timer-ASE, + Billing-ASE, + Charging-ASE, + Status-reporting-ASE, + Call-report-ASE, + Signalling-control-ASE, + Specialized-resource-control-ASE, + Cancel-ASE, + Activity-test-ASE +} +::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) generic-scf-to-ssf(4) version 1(0)}; + +IN-CS1-SCF-to-SSF-AC APPLICATION-CONTEXT +-- dialogue initiated by SCF with InitiateCallAttempt, DP-specific Case +INITIATOR CONSUMER OF +RESPONDER CONSUMER OF { + Assist-connection-establishment-ASE, + Generic-disconnect-resource-ASE, + Non-assisted-connection-establishment-ASE, + Connect-ASE, + Call-handling-ASE, + DP-specific-event-handling-ASE, + Charging-event-handling-ASE, + SSF-call-processing-ASE, + SCF-call-initiation-ASE, + Timer-ASE, + Billing-ASE, + Charging-ASE, + Status-reporting-ASE, +} + +``` + +``` + + Call-report-ASE, + Signalling-control-ASE, + Specialized-resource-control-ASE, + Cancel-ASE, + Activity-test-ASE + } + ::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) dp-specific-scf-to-ssf(5) version 1(0)}; + +IN-CS1-SCF-to-SSF-traffic-management-AC APPLICATION-CONTEXT +-- dialogue initiated by SCF with CallGap +INITIATOR CONSUMER OF +RESPONDER CONSUMER OF { + Traffic-management-ASE +} + ::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) scf-to-ssf-traffic-management(6) version 1(0)}; + +IN-CS1-SCF-to-SSF-service-management-AC APPLICATION-CONTEXT +-- dialogue initiated by SCF with ActivateServiceFiltering +INITIATOR CONSUMER OF +RESPONDER CONSUMER OF { + Service-management-ASE +} + ::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) scf-to-ssf-service-management(7) version 1(0)}; + +IN-CS1-SSF-to-SCF-service-management-AC APPLICATION-CONTEXT +-- dialogue initiated by SSF with ServiceFilteringResponse +INITIATOR CONSUMER OF { + Service-management-ASE +} +RESPONDER CONSUMER OF + ::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) ssf-to-scf-service-management(8) version 1(0)}; + +IN-CS1-SCF-to-SSF-status-reporting-AC APPLICATION-CONTEXT +-- dialogue initiated by SCF with Status Reporting Operations +INITIATOR CONSUMER OF +RESPONDER CONSUMER OF { + Cancel-ASE, + Status-reporting-ASE +} + ::= {ccitt recommendation q1218 scf-ssf-srf-objects(1) scf-to-ssf-status-reporting(9) version 1(0)}; + +``` + +## 2.2 SCF-SDF interface + +### 2.2.1 Introduction to the IN X.500 DAP Subset + +#### 2.2.1.1 Alignment between the X.500 concepts and the IN + +The X.500 Recommendations are used to specify the SCF-SDF interface and the contents of the SDF. Most of the concepts of the X.500-Series are directly used in the IN environment, however some alignments need to be done at the terminology level to ensure that the concepts introduced in the Directory are correctly understood. The purpose of this subclause to provide this alignment. It therefore only concentrates on the terms that are ambiguous in the IN environment. + +When looking at the structure of the SCF, the Service Data Management is the part of the SCF responsible for the interactions with the SDF. It can be mapped onto the concept of Directory User Agent (DUA). When a SCF on a behalf of a user wants to setup an association with an SDF, an instance of a DUA is created in the SLPI. It is killed when the association is ended. + +The SDF is the entity responsible to answer the database requests. This functional entity can be mapped onto the Directory System Agent (DSA). When an association is setup between an SCF and a SDF, an instance of a DSA is created for the length of the association. + +The Directory is a collection of DSAs/SDFs. This set can be used for a specific service or for a variety of services. The notion of Directory is equivalent to the concept of database systems in IN. + +The Directory can also be seen as a repository of data. IN services provides various kinds of data access to users. The information is organized into entries. An entry is a collection of information that can be identified (or named). When it represents an object (i.e. contains primary information about an object), it is called an object entry. + +Objects are anything which are identifiable (can be named) and which are of interest to hold information on, in the database. A typical example of an object is a user. Objects can be described by several entries. Each individual information that is used to describe an object is an attribute. They are associated to entries. + +In the IN environment, the service provider is responsible for the management and the administration of the data contained in an DSA. Therefore the service provider plays the administrator role. He is the administrative authority in X.500 terminology. The service provider enforces the security procedure (authentication and access control). + +### 2.2.1.2 Use of a limited subset of X.500 + +The primary purpose of the X.500-Series Recommendations is to provide a directory service and not the description of the SCF-SDF interface as SG 11 wants to use them. The X.500 functionalities cover more than the functionalities needed for IN CS-1. This subclause tries to indicate which aspects of the Directory Abstract Service should be considered and supported by implementations within the scope of CS-1. It also mentions the attitude to adopt when a not-supported parameter is received. Profiling is used as a means to present the status of the different parameters. + +It is important to mention that the number of parameters carried in a message should be minimized, because each of them is associated to a load in the signalling traffic and to some processing time. This is the reason why the parameters are removed unless they are absolutely necessary when they are sent. On reception removed parameters should not be treated but should be understood by the receiving entity. This allows the extensions of the profile in the future according to its actual description in the 1993 edition of the Directory. + +For convenience and clarity, this profile is defined using ASN.1 subtyping facilities however these definitions do not form a protocol specification. This simply indicates which parameters an implementation should not send. It does not change the behaviour of the receiving entity which shall still be capable of decoding values conform to the original definition of the Directory Abstract Service. Nevertheless elements that are excluded by subtyping should be ignored. + +### 2.2.1.3 Working assumptions + +Several assumptions were used to design the Directory Abstract Service profile for IN CS-1. References to the assumptions used are made in 2.2.2.1, they are as follows: + +- **Assumption 1:** The version of the Directory Abstract Service used for CS-1 is the 1993 version. The parameters only used for the 1988 version shall be ignored. Functionalities that might be needed in future Capabilities Sets should be at least considered if not supported. +- **Assumption 2:** Data distribution mechanisms are not considered within CS-1. The reason behind that assumption is that the distribution mechanisms use the SDF-SDF interface that is not part of CS-1. Those mechanisms include the chaining and the broadcasting of requests as well as the referral. Even though they need not to be supported, those indications of the use of such mechanisms should be considered (see assumption 1). +- **Assumption 3:** Copy mechanisms are not considered within CS-1. Like the data distribution mechanisms, they use the SDF-SDF interface. They imply complex maintenance mechanisms that are not within the scope of CS-1. +- **Assumption 4:** The operations used for CS-1 do not need to be signed. Since no security requirement was expressed toward the use of signed operations like the definition of an algorithm for the signature, this functionality is not covered within the scope of CS-1. + +- **Assumption 5:** The strong authentication mechanisms are not covered by the present profile. Those mechanisms are used for a security system with public keys. Given the present status of the security work, such a functionality is not foreseen for CS-1. +- **Assumption 6:** The alias entries in IN are just a means to provide an alternative name for an object and therefore should be dereferenced when needed. +- **Assumption 7:** An SCF-SDF operation cannot be abandoned. If an operation takes too much time, its timer expires and there is no need to abandon it. + +## 2.2.2 The IN X.500 DAP Subset + +### 2.2.2.1 Review of X.511 for use in the IN + +The profiling of Recommendation X.511 provided thereafter is based upon Recommendation X.511 and the amendments made to it (DAM 2 on contexts, DAM 3 on minor extensions) + +#### 2.2.2.1.1 Information types and common procedures + +##### 2.2.2.1.1.1 CommonArguments + +IN-CommonArguments ::= CommonArguments ( + WITH COMPONENTS { + serviceControls (IN-ServiceControls....), + securityParameters OPTIONAL, + requestor ABSENT, + operationProgress ({nameResolutionPhase notStarted}....), + aliasedRDNs ABSENT, + criticalExtensions OPTIONAL + referenceType ABSENT, + entryOnly (TRUE....), + exclusions ABSENT, + nameResolveOnMaster (FALSE....) + operationContexts OPTIONAL}, + ...) + +The status of each component of **CommonArguments** parameter is as follows: + +- The **serviceControls** component (see 2.2.2.1.1.3). +- The **securityParameters** component – The securityParameters component governs the security features associated with a Directory operation (i.e. the signature of an operation). Since the operations are not signed in CS-1 (assumption 4), the securityParameters component should not be present. +- The **requestor** component provides the name of the originator of a particular operation. This is mainly used for signed requests and as such should not be sent (assumption 4). +- The **operationProgress**, **referenceType**, **entryOnly**, **exclusions** and **nameResolveOnMaster** components are used when the DUA is acting on a continuation reference from a DSA. Since the distribution mechanisms are not supported (assumption 2), those parameters should not be sent. +- The **aliasedRDNs** component is present in the 1993 version only for compatibility reasons. It should always be omitted in the 1993 implementations of the Directory (assumption 1). +- The **criticalExtensions** component is used to indicated to 1988 edition implementations the criticality of a number of extensions which are available in the 1993 versions. Since the 1993 version is used within CS-1 (assumption 1), the component should not be sent. However in the IN context the following extensions should be supported: subentries, modifyRightsRequest, matchedValuesOnly, useAliasOnUpdate, useContexts, selectionOnModify, extendedEntryMods. +- The **operationContexts** component supplies a set of context assertions which are applied to attribute value assertions and entry information made within the operation. Since the use of contexts is part of the IN requirements, the component is present whenever necessary. + +#### 2.2.2.1.1.2 Common results + +IN-CommonResults ::= CommonResults ( +WITH COMPONENTS { +securityParameters ABSENT, +performer ABSENT, +aliasDereferenced}) + +The status of each component of **CommonResults** parameter is as follows: + +- The **securityParameters** component – The operations are not signed therefore this component should not be present. +- The **performer** component provides the name of the performer of a particular operation. This is mainly used for signed results and as such should not be sent (assumption 4). +- The **aliasDereferenced** component is set to TRUE when an alias was encountered and dereferenced during the processing of an operation. + +#### 2.2.2.1.1.3 Service controls + +IN-ServiceControls ::= ServiceControls +(WITH COMPONENTS { +options ({chainingProhibited, localScope}| +({changingProhibited, localScope}| +{changingProhibited, localScope, dontDereferenceAliases, subentries}| +{chainingProhibited, localScope, subentries}), +priority , +timeLimit ABSENT, +sizeLimit ABSENT, +scopeOfReferral ABSENT, +attributeSizeLimit ABSENT}) + +The status of each component of **ServiceControls** parameter is as follows: + +- The **options** component contains an number of indications: + - **preferChaining** should be absent because it implies the use of distribution (assumption 2); + - **chainingProhibited** and **localScope** should always be set, because chaining is not allowed in CS1 (assumption 2); + - **dontUseCopy** and **copyShallDo** refer to copy mechanisms and should not be present (assumption 3); + - **dontDereferenceAliases** should only be included when the object of interest is an alias (e.g. to remove an alias); + - **subentries** should be set depending on whether the entries or the subentries need to be addressed. +- The **priority** component is used to specified at which priority the service is to be provided. This parameter could be used to manage congestion in the DSA and may be needed. +- The **timeLimit** component indicates the maximum elapsed time to fulfil a request. It is redundant with the operation timers of TCAP and therefore is not needed. +- The **sizeLimit** and the **attributeSizeLimit** sets some size limits on the results either in terms of objects or in terms of attributes. This is useful when requests are expected to be general (the requestor does not know the structure of the DSA), but in the case of IN, this type of limitation does not seem applicable. +- The **scopeOfReferral** component indicates the scope relevant for a referral. Since referral is not one of the features considered in IN CS1 (assumption 2), the parameter should not be present. + +#### 2.2.2.1.1.4 Entry information selection + +IN-EntryInformationSelection ::= EntryInformationSelection +(WITH COMPONENTS { +attributes , +infoTypes (attributeTypesAndValues....), +extraAttributes OPTIONAL}) + +``` + +contextSelection OPTIONAL, +returnContexts }, +...) + +``` + +The status of each component of **EntryInformationSelection** parameter is as follows: + +- The **attributes** component specifies the attributes that should be returned in a retrieval service. The **allUserAttributes** option is kept even though it is advised to service specifiers to avoid its use which generates more traffic than needed. They should use instead the **select** option that precisely name the requested attributes. +- The **infoTypes** component specifies whether the attribute types and values should be returned or only the types. In IN services are mainly interested in the attribute values that are relevant to the processing of the service. This component should be absent given its default value. +- The **extraAttributes** component has a similar use as the **attributes** component. The only difference is that the option **allUserAttributes** is replaced by **allOperationalAttributes**. +- The **contextSelection** component is used to specify which attribute values should be returned of the attributes selected by **attributes** when contexts are used. Therefore this component is of interest for IN specifications. +- The **returnContexts** component is to request the SDF to return attribute values with their associated context lists. The component can be used for some IN services. + +#### 2.2.2.1.1.5 EntryInformation + +**IN-EntryInformation ::= EntryInformation** + +``` + +(WITH COMPONENTS { + name PRESENT, + fromEntry (TRUE....), + information (WITH COMPONENTS { + attributeType ABSENT, + attribute PRESENT}....) OPTIONAL, + incompleteEntry , + partialNameResolution (FALSE....)}, +...) + +``` + +The status of each component of **EntryInformation** parameter is as follows: + +- The **name** component gives the name of the entry returned. It is a mandatory component. +- The **fromEntry** component indicates if a copy or the entry itself is returned. Since IN CS-1 does not use copy mechanisms (assumption 3), only the default value of this component should be used. +- The **information** parameter contains the relevant information which is returned. Given the choice made for the **infoTypes** component (see 2.2.2.1.1.4), only the **attribute** option should be used. +- The **incompleteEntry** parameter indicates when the returned result is not complete due to some access rights limitations for example. It is necessary to support such a parameter. +- The **partialNameResolution** component indicates whether the name resolution was partially or totally completed. This component does not correspond to any IN requirements and is not included. + +#### 2.2.2.1.1.6 Optionally-signed parameters + +**UNSIGNED {Type} ::= OPTIONALLY-SIGNED {Type}** + +``` + +(WITH COMPONENTS { + unsigned PRESENT, + signed ABSENT}) + +``` + +The operations are not signed for CS-1 (assumption 4). This means that only the unsigned option should be used. + +### 2.2.2.1.2 Bind operation + +``` +in-DirectoryBind OPERATION ::= { + ARGUMENT IN-DirectoryBindArgument + RESULT IN-DirectoryBindResult + ERRORS {in-DirectoryBindError} +``` + +The **DirectoryBind** and **DirectoryUnbind** operations are used at the beginning and end of a particular period of accessing the Directory. + +#### 2.2.2.1.2.1 Bind arguments and results + +``` +IN-DirectoryBindArgument ::= DirectoryBindArgument +(WITH COMPONENTS { + credentials (IN-Credentials) OPTIONAL, + versions }) +``` + +``` +IN-Credentials ::= Credentials +(WITH COMPONENTS { + simple , + strong ABSENT, + externalProcedure }) +``` + +``` +IN-DirectoryBindResult ::= IN-DirectoryBindArgument +``` + +The status of each parameter of **DirectoryBindArgument** is as follows: + +- The **credentials** parameter is used to establish the identity of the user. It is necessary for services that requires authentication. However, the **strong** credentials should not be used because they correspond to the use of a public key system (assumption 5). +- The **versions** parameter identifies the version of the **DirectoryService** which is to be used. + +The same considerations apply to the **DirectoryBindResult**. + +#### 2.2.2.1.2.2 Bind errors + +``` +in-DirectoryBindError ERROR ::= { + PARAMETER IN-DirectoryBindErrorParameter} +``` + +``` +IN-DirectoryBindErrorParameter ::= DirectoryBindErrorParameter +(WITH COMPONENTS { + versions , + error (WITH COMPONENTS { + securityError (SecurityProblem (1/2/7...)), + serviceError (ServiceProblem (2))})}) +``` + +The **DirectoryBindError** remains as defined in the **Directory** Abstract Service. In reception, all the possible errors should be supported to understand a Bind error. + +### 2.2.2.1.3 Search operation + +``` +in-Search OPERATION ::= { + ARGUMENT IN-SearchArgument + RESULT IN-SearchResult + ERRORS {in-NameError | in-ServiceError | in-SecurityError | attributeError} + CODE id-opcode-in-search} +``` + +The search operation is used to search a portion of the DIT for entries of interest. + +#### 2.2.2.1.3.1 Search arguments and errors + +``` +IN-SearchArgument ::= UNSIGNED {SearchArgument +(WITH COMPONENTS { + baseObject PRESENT, + subset , + filter , + searchAliases (TRUE...), + selection (IN-EntryInformationSelection...), + pagedResults ABSENT, +``` + +``` + + matchedValuesOnly , + extendedFilter ABSENT, + checkOverspecified }, + ...)} + +``` + +The status of each parameter of **SearchArgument** is as follows: + +- The **baseObject** parameter identifies the object entry where the search operation should take place. It is a mandatory parameter. +- The **subset** parameter indicates which part of the DIT should be involved in the search operation. This parameter is needed even though the use of the wholeSubtree should be avoided to prevent the operation timer to expire. +- The **filter** parameter is used to eliminate entries from the search space. However the **extendedFilter** parameter was added in the 1993 version of the Directory for compatibility reasons and should therefore not be sent. Only the **filter** parameter should be sent. +- The **searchAliases** parameter indicates whether the aliases encountered in the search space (except the base object) should be considered. Since in IN aliases are always dereferenced when searching, this parameter should be used only with its default value. +- The **selection** parameter indicates what information from the entries, e.g. types and values, is requested (see 2.2.2.1.1.4). +- The **pagedResults** parameter is used to request a page by page result. The **pagedResults** parameter is used to present the results of a search operation in a page format. This type of information is not needed in CS-1 since the SCF treats the results. +- The **matchedValuesOnly** is a facility used to return only the values that fulfil the filter if any. This might be needed for IN CS-1. +- The **checkOverspecified** parameter is used to request the SDF to return an **overspecFilter** item in the Search result when appropriate. The IN services might need an **overspecFilter** item and therefore this parameter should be included. + +Concerning errors, the **abandoned** and the **referral** errors are not supported. + +### 2.2.2.1.3.2 Search results + +``` + +IN-SearchResult ::= UNSIGNED {SearchResult + (WITH COMPONENTS { + searchInfo (WITH COMPONENTS { + name , + entries (WITH COMPONENT (IN-EntryInformation...)...), + partialOutcomeQualifier (PartialOutcomeQualifier + (WITH COMPONENTS { + limitProblem OPTIONAL, + unexplored ABSENT, + unavailableCriticalExtensions , + unknownErrors ABSENT, + queryReference ABSENT, + overspecFilter OPTIONAL}, + ...) ...)}, + ...), + uncorrelatedSearchInfo ABSENT}, + ...)} + +``` + +The status of each parameter of **SearchResult** is as follows: + +- The **name** parameter indicates the name of the returned entries if different from the name of the **baseObject** name. It is needed when the search operation has entries other than the base object as a result. +- The **entries** parameter contains the entries that satisfy the filter (see 2.2.2.1.1.5). + +- The **partialOutcomeQualifier** parameter is present when the search operation was not fully completed. It contains information on the reasons why the search operation was not finished and on where the operation was stopped: + - The **limitProblem** parameter indicates which type of limit was reached (administrative). It is necessary to carry such indications. + - The **unexplored** parameter indicates where the search operation was stopped and gives indications about the state of the operation (object considered and progress indication). If the operation is to be resent, such a parameter is needed. This is equivalent to a referral and as such should be absent (assumption 2). + - The **unavailableCriticalExtensions** parameter indicates that some critical extensions were not available. + - The **unknownErrors** parameter corresponds to the reception of unknown errors from other SDF. It implies the use of a chaining mechanism that is not available in CS-1 (assumption 2) and is not used. + - The **queryReference** parameter is used when paged results were requested and therefore is not needed. + - The **overspecFilter** parameter is used when the returned Search result is empty as a consequence of over-specified filtering. The filter returned corresponds to a part of the initial filter for which some entries are still available. This functionalities could be used for IN services. +- The **uncorrelatedSearchInfo** contains signed results that could not be unsigned. Since the operations are not signed in IN CS-1, this parameter should not be used. + +#### 2.2.2.1.4 AddEntry operation + +``` +in-AddEntry OPERATION ::= { + ARGUMENT IN-AddEntryArgument + RESULT AddEntryResult + ERRORS {nameError | in-ServiceError | in-SecurityError | attributeError | + in-UpdateError} + CODE id-opcode-in-addEntry} +``` + +The addEntry operation is used to add a leaf entry to the DIT. + +##### 2.2.2.1.4.1 AddEntry arguments, results and errors + +``` +IN-AddEntryArgument ::= UNSIGNED {AddEntryArgument + (WITH COMPONENTS { + object PRESENT, + entry PRESENT, + targetSystem ABSENT})} +``` + +The status of each parameter of **AddEntryArgument** is as follows: + +- The **object** parameter identifies the entry to be added. It is a mandatory parameter. +- The **entry** parameter describes the entry to be added. It is also a mandatory parameter. +- The **targetSystem** parameter contains the name of the SDF where the entry was added. When no distribution is considered (assumption 2), the SDF is the same as the one where the operation was sent. The parameter is therefore unnecessary. + +Concerning errors, the **referral** error is not supported. + +#### 2.2.2.1.5 RemoveEntry operation + +``` +in-RemoveEntry OPERATION ::= { + ARGUMENT IN-RemoveEntryArgument + RESULT RemoveEntryResult + ERRORS {nameError | in-ServiceError | in-SecurityError | in-UpdateError} + CODE id-opcode-in-removeEntry} +``` + +The `removeEntry` operation is used to remove a leaf entry from the DIT. + +#### 2.2.2.1.5.1 RemoveEntry arguments, results and errors + +**IN-RemoveEntryArgument ::= UNSIGNED {RemoveEntryArgument}** + +The parameters are only the name of the object to be deleted. It is mandatory. The argument of the operation should be kept as it is described in the Directory. + +Concerning errors, the **referral** error is not supported. + +#### 2.2.2.1.6 ModifyEntry operation + +**in-ModifyEntry OPERATION ::= {** +    **ARGUMENT           IN-ModifyEntryArgument** +    **RESULT           IN-ModifyEntryResult** +    **ERRORS           {nameError | in-ServiceError | in-SecurityError | attributeError |** +    **in-UpdateError}** +    **CODE             id-opcode-in-modifyEntry}** + +The `modifyEntry` operation is used to perform a series of modifications to a single entry. + +##### 2.2.2.1.6.1 ModifyEntry arguments and errors + +**IN-ModifyEntryArgument ::= UNSIGNED {ModifyEntryArgument** +    **(WITH COMPONENTS {** +        **object           PRESENT,** +        **changes          PRESENT,** +        **selection        (IN-EntryInformationSelection)})}** + +The parameters are the name of the object to be modified, the list of changes and the **selection** parameter that specifies some attributes and values to be returned. The first two are mandatory and the third one corresponds to 2.2.2.1.1.4. Since all the changes available in the **changes** parameter are useful for IN CS-1, the argument of the operation should be kept as it is described in the Directory except the selection parameter. + +Concerning errors, the **referral** error is not supported. + +##### 2.2.2.1.6.2 ModifyEntry results + +**IN-ModifyEntryResult ::= ModifyEntryResult** +    **(WITH COMPONENTS {** +        **null                   ,** +        **information          UNSIGNED {Information** +            **(WITH COMPONENTS {** +                **entry        (IN-EntryInformation)})}** + +If no information was to be retrieved with the `modifyEntry` operation, the **null** result is returned. Otherwise the information is to be returned in the **entry** component of the **information** result. For IN CS-1 this component is specified in 2.2.2.1.15. + +#### 2.2.2.1.7 Errors + +The precedence rule defined in the Directory should apply. + +The **abandoned**, **abandonFailed** and **referral** errors are not considered because not supported by CS-1 (assumption 1 and assumption 7). + +##### 2.2.2.1.7.1 Attribute error + +All the attribute problems cited in the **attributeError** can be used in CS-1 and therefore this error should not be modified and directly taken from the Directory. + +##### 2.2.2.1.7.2 Name error + +All the naming problems cited in the **nameError** can be used in CS-1 and therefore this error should be modified and directly taken from the Directory. + +### 2.2.2.1.7.3 Security Error + +``` +in-SecurityError ERROR ::= { + PARAMETER IN-SecurityErrorParameter + CODE id-errcode-in-securityError} + +IN-SecurityErrorParameter ::= SecurityErrorParameter +(WITH COMPONENTS { + problem (SecurityProblem (1 | 2 | 3 | 6))}) +``` + +The **securityError** reports a security problem that was encountered during the execution of an operation. + +It contains only the **problem** parameter that indicates which type of problem was met. Among the possible problems, the **invalidSignature** and **protectionRequired** ones should not be sent, because they are used in conjunction with signed operations (assumption 4). + +### 2.2.2.1.7.4 Service error + +``` +in-ServiceError ERROR ::= { + PARAMETER IN-ServiceErrorParameter + CODE id-errcode-in-serviceError} + +IN-ServiceErrorParameter ::= ServiceErrorParameter +(WITH COMPONENTS { + problem (ServiceProblem (1 | 2 | 3 | 5 | 10 | 8 | 9 | 12))}) +``` + +The **serviceError** reports a problem related to the provision of the service. + +It contains only the **problem** parameter that indicates which type of problem was encountered. Among the possible problems, several should not be sent because they are linked to distributed operation (assumption 2), to the incompatibility of versions (assumption 1) and to the use of paged results. That are the **chainingRequired**, **invalidReference**, **timeLimitExceeded**, **outOfScope** and **invalidQueryReference** problems. + +### 2.2.2.1.7.5 Update error + +``` +in-UpdateError ERROR ::= { + PARAMETER IN-UpdateErrorParameter + CODE id-errcode-in-updateError} + +IN-UpdateErrorParameter ::= UpdateErrorParameter +(WITH COMPONENTS { + problem (UpdateProblem (1 | 2 | 3 | 4 | 5 | 7))}) +``` + +The **UpdateError** reports problems related to attempts to add, delete, or modify information in the DIB. It contains only the **problem** parameter that indicates which type of problem was encountered. Among the possible problems, the **affectsMultipleDSAs** problem should not be sent because it is linked to distributed operation (assumption 2). + +## 2.2.2.2 Directory Access Protocol Subset + +### 2.2.2.2.1 Protocol overview + +#### 2.2.2.2.1.1 Remote Operations – Specification and SS No. 7 realization + +ITU-T Rec. X.880 | ISO/IEC 13712-1 defines several information object classes that are useful in the specification of ROS-based application protocols such as the various Directory protocols defined in this Directory Specification. A number of these classes are used in this and subsequent subclauses. The specification techniques provided in ITU-T Rec. X.880 | ISO/IEC 13712-1 are used to define a generic protocol between objects. When realized as an SS No. 7 application layer protocol, the concepts of ITU-T Rec. X.880 | ISO/IEC 13712-1 are mapped to SS No. 7 concepts in Recommendation Q.775. The SS No. 7 application layer protocol defined in this Recommendation, is a protocol to provide communication between a pair of application processes. In the SS No. 7 environment this is represented as communication between a pair of application-entities (AEs) using the Transaction Capabilities. The function of an AE is + +provided by a set of application-service-elements (ASEs). The interaction between AEs is described in terms of their use of the services provided by the ASEs. All the services provided by the Directory ASEs are contained in a single AE. The Component Handler (CHA) of the Transaction Capabilities (TC) supports the request/reply paradigm of the operation. The Directory ASEs provide the mapping function of the abstract-syntax notation of the directory operation packages onto the services provided by TC. The Dialogue handler (DHA) of the TC supports the establishment and release of an application – association called "dialogue" between a pair of AEs. Dialogues between a DUA and a DSA may be established only by the DUA. + +#### 2.2.2.2.1.2 Directory ROS-Objects and Contracts + +ITU-T Rec. X.511 | ISO/IEC 9594-3 defines the abstract service between a DUA and the Directory which provides an access point to support a user accessing Directory services. Subclause 2.2.2 defines the sub-set of this abstract service used in the context of Intelligent Networks. + +The **dua** class of ROS-object describes a DUA, being an instance of this class, as the initiator of the contract **dapContract**. This contract is referred to in these Directory Specifications as the Directory Abstract Service. It is specified as a ROS-based information object in 2.2.2.2.1.3. + +``` +dua ROS-OBJECT-CLASS ::= { + INITIATES {dapContract} + ID id-rosObject-dua} +``` + +The **directory** class of ROS-object describes the provider of the Directory Abstract Service. This provider is the responder of the **dapContract**. + +``` +directory ROS-OBJECT-CLASS ::= { + RESPONDS {dapContract} + ID id-rosObject-directory} +``` + +The Directory is further modeled as being represented to a DUA by a DSA which support the particular access point concerned. In the context of Intelligent Networks, each DSA is potentially an access point to the Directory. + +The **directory** object is manifested as a set of DSAs (each of which resides in an SDF). Each DSA comprising the **directory** is an instance of the **dap-dsa** class. A **dap-dsa** object assumes the role of responder in the **dapContract**. + +``` +dap-dsa ROS-OBJECT-CLASS ::= { + RESPONDS {dapContract} + ID id-rosObject-dapDSA} +``` + +Future versions of this Recommendation will enable DSAs to interact with one another to achieve various objectives. + +#### 2.2.2.2.1.3 DAP Contract and Packages + +The **dapContract** is defined as an information object of class CONTRACT. + +``` +dapContract CONTRACT ::= { + CONNECTION dapConnectionPackage + INITIATOR CONSUMER OF {searchPackage | modifyPackage} + ID id-contract-dap} +``` + +When a DUA and DSA from different IN physical entities, this association contract shall be realized as an SS No. 7 application layer protocol, referred to as the IN Directory Access Protocol (DAP). The definition of this protocol in terms of an SS No. 7 application context is provided in 7.2. + +The **dapContract** is composed of a **connection package**, **dapConnectionPackage**, and two operation packages, **searchPackage** and **modifyPackage**. The **connection package**, **dapConnectionPackage**, is defined as an information object of class CONNECTION-PACKAGE. The bind and unbind operations of this connection package, **directoryBind** and **directoryUnbind**, are defined in ITU-T Rec. X.511 | ISO/IEC 9594-3. + +``` +dapConnectionPackage CONNECTION-PACKAGE ::= { + BIND directoryBind + UNBIND directoryUnbind + ID id-package-dapConnection} +``` + +The operation packages, **searchPackage** and **modifyPackage**, are defined as information objects of class OPERATION-PACKAGE. The operations of these operation packages are defined in ITU-T Rec. X.511 | ISO/IEC 9594-3. ITU-T Rec. X.511 | ISO/IEC 9594-3 defines additional operations for supporting access to the Directory. Such operations are not used in the context of Intelligent Networks. + +``` +searchPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {search} + ID id-package-search} +modifyPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {addEntry | removeEntry | modifyEntry} + ID id-package-modify} +``` + +NOTE – These packages, when realized as ASEs, are used for the construction of application contexts defined in this Specification. They are not intended to allow for claims of conformance to individual, or other combinations of, ASEs. + +Since the DUA is the initiator of the **dapContract**, it assumes the role of consumer of the operation packages of the contract. This means that only the DUA can invoke operations in this contract and its SS No. 7 realization. + +#### 2.2.2.2.1.4 Use of underlying services + +The DAP protocol makes use of underlying services as described below. + +##### 2.2.2.2.1.4.1 Use of component handling services + +The Directory ASEs are users of the TC component handling services except for the TC-L-REJECT and TC-L-CANCEL services which are used by the application-process. Receipt of a TC-L-REJECT-Ind or TC-L-CANCEL-Ind, leads the application-process to abandon the dialogue (i.e. it issues a TC-U-ABORT-Request primitive). + +The TC-U-CANCEL service is never used. + +##### 2.2.2.2.1.4.2 Use of dialogue handling services + +Dialogue handling services are used to support the DirectoryBind and DirectoryUnbind operations and to trigger the sending of the APDUs associated with the operations involved in the Directory packages. + +Component grouping is performed under the control of the application-process through an appropriate usage of the TC-BEGIN and TC-CONTINUE service. + +The TC-END service is solely used to support the unbind procedure (i.e. it is never used to trigger the sending of components). + +On receipt of an empty TC-CONTINUE.req primitive, the SDF should ignore the primitive. + +On receipt of a TC-END.req with a database request, the SDF should not perform the database request and consider the requested TC-END service as an unbind procedure. The dialogue is then terminated (see 2.2.2.2.3.1.2). + +On receipt of a TC-U-REJECT.ind in the SDF, this primitive should be ignored. + +On receipt of a TC-R-REJECT.ind in the SDF, the dialogue should be released with a TC-U-ABORT.req. + +If reject situations are detected in the SDF, a TC-U-REJECT.req should be sent followed by a TC-CONTINUE.req. + +The pre-arranged termination procedure is never used. + +The application-process is the sole user of the TC-P-ABORT service and TC-NOTICE service. + +The receipt of a TC-U-ABORT-Ind or TC-P-ABORT-Ind on a dialogue terminates all request processing. It is the application-process responsibility to confirm if requested modifications occurred. + +It is an application-process responsibility to provide in the TC-BEGIN.req primitive a destination address which can be used by the underlying SCCP to route the message to the proper SDF. + +### 2.2.2.2.2 Directory protocol abstract syntax + +#### 2.2.2.2.2.1 Abstract syntaxes + +This version of the Directory Access Protocol requires the support of three abstract syntaxes: + +- a) the abstract-syntax of TC dialogue control protocol data units, **dialogue-abstract-syntax**, which is needed to establish the dialogues between the SCFs and the SDFs and is specified in Recommendation Q.773; +- b) the abstract-syntax for conveying the protocol data units for invoking **directoryBind** and **directoryUnbind** operations and reporting their outcome; +- c) the abstract-syntax for conveying the protocol data units for invoking the operations involved in the operation packages specified in 2.2.2.2.1.3 and reporting their outcome. + +The ASN.1 type from which the values of the second abstract syntax are derived is specified using the parameterized types, **Bind {}** and **Unbind {}** which are defined in Recommendation X.880. + +The ASN.1 type from which the values of the last abstract syntax are derived is specified using the parameterized types **TCAPMessage {}** defined in Recommendation Q.773. + +All these abstract syntaxes shall (as a minimum) be encoded according to the Basic ASN.1 encoding rules with the restrictions listed in Recommendation Q.773. + +##### 2.2.2.2.2.1.1 DAP Abstract Syntax + +The Directory ASEs that realize the operation packages specified in 2.2.2.2.1.3 share a single abstract syntax, **directoryOperationsAbstractSyntax**. This is specified as an information object of the class ABSTRACT-SYNTAX. + +``` +inDirectoryOperationsAbstractSyntax ABSTRACT-SYNTAX ::= { + BasicDAP-PDUs + IDENTIFIED BY id-as-directoryOperationsAS} + +BasicDAP-PDUs ::= TCAPMessage {{DAP-Invokable},{DAP-Returnable}} + +DAP-Invokable OPERATION ::= {search | addEntry | removeEntry | modifyEntry} + +DAP-Returnable OPERATION ::= {search | addEntry | removeEntry | modifyEntry} +``` + +The realization of the connection package specified in 2.2.2.2.1.3 uses a separate abstract syntax, **directoryBindingAbstractSyntax**. This is specified as an information object of the class ABSTRACT-SYNTAX. + +``` +InDirectoryBindingAbstractSyntax ABSTRACT-SYNTAX ::= { + DAPBinding-PDUs + IDENTIFIED BY id-as-directoryBindingAS} + +DAPBinding-PDUs ::= CHOICE { + bind Bind {directoryBind}, + unbind Unbind {directoryUnbind}} +``` + +#### 2.2.2.2.2.2 Directory application contexts + +##### 2.2.2.2.2.2.1 Directory Access Application Context + +The **dapContract** is realized as the **iNdirectoryAccessAC**. This application context is specified as an information object of the class APPLICATION-CONTEXT. + +``` +iNdirectoryAccessAC APPLICATION-CONTEXT ::= { + CONTRACT dapContract + DIALOGUE MODE structured + TERMINATION basic + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + inDirectoryOperationsAbstractSyntax | + inDirectoryBindingAbstractSyntax } + APPLICATION CONTEXT NAME id-ac-directoryAccessAC} +``` + +### **2.2.2.2.2.3 Operation Codes** + +The operations involved in the packages defined in this Recommendation are specified in Recommendation X.519 where the assigned operation codes are imported from Recommendation X.519. + +### **2.2.2.2.2.4 Error Codes** + +The errors involved in the packages defined in this Recommendation are specified in Recommendation X.519 where the assigned error codes are imported from Recommendation X.519. + +### **2.2.2.2.2.5 Versions and the rules for extensibility** + +The Directory may be distributed and more than two Directory Application Entities may interoperate to service a request. The Directory AEs may be implemented conforming to different editions of the Directory specification of the Directory service which may or may not be represented by different protocol version numbers. The version number is negotiated to the highest common version number between two directly binding Directory AEs. + +#### **2.2.2.2.2.5.1 Version negotiation** + +When accepting an association, i.e. binding, utilizing the DAP, the version negotiated shall only affect the point-to-point aspects of the protocol exchanged between the DUA and the DSA to which it is connected. Subsequent requests or responses on the association shall not be constrained by the version negotiated. + +NOTE – There are no point-to-point aspects of the DAP that are currently indicated by different protocol versions. + +#### **2.2.2.2.2.5.2 DUA side** + +##### **2.2.2.2.2.5.2.1 Request and response processing at the DUA side** + +The DUA may initiate requests using the highest edition of the specification of that request it supports. If one or more elements of the request are critical, it shall indicate the extension number(s) in the critical Extensions parameter. + +NOTE 1 – If the information, the extension replaced in a CHOICE, ENUMERATED or INTEGER (used as ENUMERATED) type would be essential for proper operation in a DSA implemented according to an earlier edition of this Specification, it is recommended that the extension be marked critical. + +When processing a response, a DUA shall: + +- a) ignore all unknown bit name assignments within a bit string; and +- b) ignore all unknown named numbers in an ENUMERATED type or INTEGER type that is being used in the enumerated style, provided the number occurs as an optional element of a SET or SEQUENCE; and +- c) ignore all unknown elements in SETs, at the end of SEQUENCES, or in CHOICES where the CHOICE is itself an optional element of a SET or SEQUENCE. + +NOTE 2 – Implementations may as a local option ignore certain additional elements in a Directory PDU. In particular, some unknown named numbers and unknown CHOICES in mandatory elements of SETs and SEQUENCES can be ignored without invalidating the operation. The identification of such elements is for further study. + +- d) not consider the receipt of unknown attribute types and attribute values as a protocol violation; and +- e) optionally report the unknown attribute types and attribute values to the user. + +##### **2.2.2.2.2.5.2.2 Extensibility rules for error handling at the DUA side** + +When processing a known error type with unknown indicated problems and parameters, a DUA shall: + +- a) not consider the receipt of unknown indicated problems and parameters as a protocol violation (i.e. it shall not issue a TC-U-REJECT or abort the dialogue); and +- b) optionally report the additional error information to the user. + +When processing an unknown error type, a DUA shall: + +- a) not consider the receipt of unknown error type as a protocol violation (i.e. it shall not issue a TC-U-REJECT or abort the application association); and +- b) optionally report the error to the user. + +### 2.2.2.2.2.5.3 Request processing at the DSA side + +If any DSA performing an operation detects an element **criticalExtensions** whose semantic is unknown, it shall return an **unavailableCriticalExtension** indication as a **serviceError**. + +NOTE 1 – If a **criticalExtensions** string with one or more zero values is received, this indicates either that the extensions corresponding to the values are not present or are not critical. The presence of a zero value in a **criticalExtensions** string shall not be inferred as either the presence or absence of the corresponding extension in the APDU. + +Otherwise, when processing a request from a DUA, a DSA shall: + +- a) ignore all unknown bit name assignments within a bit string; and +- b) ignore all unknown named numbers in an **ENUMERATED** type or **INTEGER** type that is being used in the enumerated style, provided the number occurs as an optional element of a **SET** or **SEQUENCE**; and +- c) ignore all unknown elements in **SETs**, at the end of **SEQUENCEs**, or in **CHOICEs** where the **CHOICE** is itself an optional element of a **SET** or **SEQUENCE**. + +NOTE 2 – Implementations may as a local option ignore certain additional elements in a Directory PDU. In particular, some unknown named numbers and unknown **CHOICEs** in mandatory elements of **SETs** and **SEQUENCEs** can be ignored without invalidating the operation. The identification of such elements is for further study. + +### 2.2.2.2.3 Mapping onto used services + +This subclause defines the mapping of the DAP onto TC services. + +#### 2.2.2.2.3.1 Mapping onto dialogue services + +This subclause defines the mapping of the **DirectoryBind** and **DirectoryUnbind** services onto the services of the TC dialogue handling services defined in Recommendation Q.771. + +##### 2.2.2.2.3.1.1 Bind + +The **DirectoryBind** service is mapped onto TC-services as follows: + +- a) The **TC-BEGIN** service is used to invoke the **DirectoryBind** operation. +- b) The **TC-CONTINUE** service is used to report the success of the **DirectoryBind** operation. +- c) The **TC-U-ABORT** service is used to report the failure of the **DirectoryBind** operation. + +The use of the parameter of these services is qualified in the following subclauses. + +##### 2.2.2.2.3.1.1.1 Mapping onto TC-BEGIN + +###### 2.2.2.2.3.1.1.1.1 Quality of Service + +This parameter shall be used as specified in Recommendation Q.771. No specific constraints are imposed by this Recommendation. + +###### 2.2.2.2.3.1.1.1.2 Destination Address + +This parameter shall contain the address of the SDF which plays the role of the DSA. + +###### 2.2.2.2.3.1.1.1.3 Application-Context-Name + +This parameter shall take the value of the application-context-name field of the **iNdirectoryAccessAC** object. + +###### 2.2.2.2.3.1.1.1.4 Originating Address + +This parameter shall contain the address of the SCF in which the DUA resides. + +###### 2.2.2.2.3.1.1.1.5 Dialogue Id + +This parameter shall be used as specified in Recommendation Q.771. + +###### 2.2.2.2.3.1.1.1.6 User Information + +This parameter shall contain a value of type **DirectoryBindArgument**. + +#### **2.2.2.2.3.1.1.1.7 Component Present** + +This parameter shall be used as specified in Recommendation Q.771. + +#### **2.2.2.2.3.1.1.2 Mapping onto TC-CONTINUE** + +##### **2.2.2.2.3.1.1.2.1 Quality of Service** + +This parameter shall be used as specified in Recommendation Q.771. No specific constraints are imposed by this Recommendation. + +##### **2.2.2.2.3.1.1.2.2 Originating Address** + +This parameter shall be used as specified in Recommendation Q.771. If, present it shall contain the address of the SDF which plays the role of a DSA. + +##### **2.2.2.2.3.1.1.2.3 Application-Context-Name** + +This parameter shall be used as specified in Recommendation Q.771. + +##### **2.2.2.2.3.1.1.2.4 Dialogue Id** + +This parameter shall be used as specified in Recommendation Q.771. + +The Authorized Relationship Id can be mapped onto the TCAP Dialogue Id. + +##### **2.2.2.2.3.1.1.2.5 User Information** + +This parameter shall contain a value of type **DirectoryBindResult**. + +##### **2.2.2.2.3.1.1.2.6 Component Present** + +This parameter shall be used as specified in Recommendation Q.771. + +#### **2.2.2.2.3.1.1.3 Mapping onto TC-U-ABORT** + +##### **2.2.2.2.3.1.1.3.1 Quality of Service** + +This parameter shall be used as specified in Recommendation Q.771. No specific constraints are imposed by this Recommendation. + +##### **2.2.2.2.3.1.1.3.2 Dialogue Id** + +This parameter shall be used as specified in Recommendation Q.771. + +##### **2.2.2.2.3.1.1.3.3 Abort Reason** + +This parameter shall be used as specified in Recommendation Q.771. + +##### **2.2.2.2.3.1.1.3.4 Application-Context-Name** + +This parameter shall be used as specified in Recommendation Q.771. When the SDF refuses a dialogue because the application-context-name it receives is not supported, this parameter shall have the value of the &application-context-name field of the **iNdirectoryAccessAC** object. + +##### **2.2.2.2.3.1.1.3.5 User information** + +When the abort reason parameter has the value "dialogue-refused", this parameter shall contain a value of type **DirectoryBindError**. Otherwise it shall be absent. + +#### **2.2.2.2.3.1.2 Unbind** + +The **DirectoryUnbind** service is mapped onto the TC-END service. The use of the parameter of the TC-END service is qualified in the following subclauses. + +##### **2.2.2.2.3.1.2.1 Quality of Service** + +This parameter shall be used as specified in Recommendation Q.771. No specific constraints are imposed by this Recommendation. + +#### 2.2.2.2.3.1.2.2 Application-Context-Name + +This parameter is not used in this phase of a dialogue. + +#### 2.2.2.2.3.1.2.3 Dialogue Id + +This parameter shall be used as specified in Recommendation Q.771. + +#### 2.2.2.2.3.1.2.4 User Information + +This parameter shall be empty. + +#### 2.2.2.2.3.1.2.5 Component Present + +This parameter shall be used as specified in Recommendation Q.771. + +#### 2.2.2.2.3.2 Mapping onto component handling services + +The Directory ASE services are mapped onto the TC component handling services. The mapping of operations and errors onto TC services is defined in Recommendation Q.774. + +The timeout parameter of the TC-INVOKE-Req primitives is set according to Table 3. + +TABLE 3/Q.1218 +TC timer values of DAP operations + +| Operation | Timeout | +|-------------|---------| +| search | ffs | +| modifyEntry | ffs | +| addEntry | ffs | +| removeEntry | ffs | + +#### 2.2.2.2.4 Conformance + +This subclause defines the requirements for conformance to this Specification. + +##### 2.2.2.2.4.1 Conformance by SCFs + +An SCF implementation claiming conformance to this Specification shall satisfy the requirements specified in 2.2.2.2.4.1.1 through 2.2.2.2.4.1.3. + +###### 2.2.2.2.4.1.1 Statement requirements + +The following shall be stated: + +- the operations of the **iNdirectoryAccessAC** application-context that the SCF is capable of invoking for which conformance is claimed; +- the security-level(s) for which conformance is claimed (none, simple, strong); +- the extensions listed in the table of 7.3.1 of ITU-T Rec. X.511 | ISO/IEC 9594-3, that the SCF is capable of initiating for which conformance is claimed. + +###### 2.2.2.2.4.1.2 Static requirements + +An SCF shall: + +- have the capability of supporting the **iNdirectoryAccessAC** application-context as defined by its abstract syntax in 2.2.2.2.2; +- conform to the extensions for which conformance was claimed in 2.2.2.2.4.1.1 c). + +#### 2.2.2.2.4.1.3 Dynamic requirements + +An SCF shall: + +- a) conform to the mapping onto used services defined in 2.2.2.2.3; +- b) shall conform to the rules of extensibility procedures defined in 2.2.2.2.5.2. + +#### 2.2.2.2.4.2 Conformance by SDFs + +An SDF implementation claiming conformance to this Specification shall satisfy the requirements specified in 2.2.2.2.4.2.1 through 2.2.2.2.4.2.3. + +##### 2.2.2.2.4.2.1 Statement requirements + +The following shall be stated: + +- a) The application-context for which conformance is claimed. The present version of this Recommendation only requires conformance to the **iNdirectoryAccessAC** application-context. + +NOTE – An application context shall not be divided except as stated herein; in particular, conformance shall not be claimed to particular operations. + +- b) The security-level(s) for which conformance is claimed (none, simple, strong). +- c) The attribute types for which conformance is claimed and whether for attributes based on the syntax **DirectoryString**, conformance is claimed for the **UNIVERSAL STRING** choice. +- d) The object classes, for which conformance is claimed. +- e) The extensions listed in the table of 7.3.1 of ITU-T Rec. X.511 | ISO/IEC 9594-3, that the SDF is capable of responding to for which conformance is claimed. +- f) Whether conformance is claimed for collective attributes as defined in 8.8 of ITU-T Rec. X.501 | ISO/IEC 9594-2 and 7.6, 7.8.2 and 9.2.2 of ITU-T Rec. X.511 | ISO/IEC 9594-3. +- g) Whether conformance is claimed for hierarchical attributes as defined in 7.6, 7.8.2 and 9.2.2 of ITU-T Rec. X.511 | ISO/IEC 9594-3. +- h) The operational attribute types defined in ITU-T Rec. X.501 | ISO/IEC 9594-2 and any other operational attribute types for which conformance is claimed. +- i) Whether conformance is claimed for return of alias names as described in 7.7.1 of ITU-T Rec. X.511 | ISO/IEC 9594-3. +- j) Whether conformance is claimed for indicating that returned entry information is complete, as described in 7.7.6 of ITU-T Rec. X.511 | ISO/IEC 9594-3. +- k) Whether conformance is claimed for modifying the object class attribute to add and/or remove values identifying auxiliary object classes, as described in 11.3.2 of ITU-T Rec. X.511 | ISO/IEC 9594-3. +- l) Whether conformance is claimed to Basic Access Control. +- m) Whether conformance is claimed to Simplified Access Control. +- n) The name bindings for which conformance is claimed. +- o) Whether the SDF is capable of administering collective attributes, as defined in ITU-T Rec. X.501 | ISO/IEC 9594-2 +- p) Whether conformance is claimed for contexts. + +##### 2.2.2.2.4.2.2 Static requirements + +An SDF shall: + +- a) have the capability of supporting the application-contexts for which conformance is claimed as defined by their abstract syntax in 2.2.2.2.2; +- b) have the capability of supporting the information framework defined by its abstract syntax in ITU-T Rec. X.501 | ISO/IEC 9594-2; +- c) have the capability of supporting the attribute types for which conformance is claimed; as defined by their abstract syntaxes; + +- d) have the capability of supporting the object classes for which conformance is claimed, as defined by their abstract syntaxes; +- e) conform to the extensions for which conformance was claimed in 2.2.2.2.4.2.1; +- f) if conformance is claimed for collective attributes, have the capability of performing the related procedures defined in 7.6, 7.8.2 and 9.2.2 of ITU-T Rec. X.511 | ISO/IEC 9594-3; +- g) if conformance is claimed for hierarchical attributes, have the capability of performing the related procedures defined in 7.6, 7.8.2 and 9.2.2 of ITU-T Rec. X.511 | ISO/IEC 9594-3; +- h) have the capability of supporting the operational attribute types for which conformance is claimed; +- i) if conformance is claimed to Basic Access Control, have the capability of holding ACI items that conform to the definitions of Basic Access Control; +- j) if conformance is claimed to Simplified Access Control, have the capability of holding ACI items that conform to the definitions of Simplified Access Control. + +#### **2.2.2.2.4.2.3 Dynamic requirements** + +An SDF shall: + +- a) conform to the mapping onto used services defined in 2.2.2.2.3; +- b) conform to the rules of extensibility procedures defined in 2.2.2.2.5.3; +- c) if conformance is claimed to Basic Access Control, have the capability of protecting information within the SDF in accordance with the procedures of Basic Access Control; +- d) if conformance is claimed to Simplified Access Control, have the capability of protecting information within the SDF in accordance with the procedures of Simplified Access Control. + +#### **2.2.2.3 X.501 profile** + +The Recommendation X.501 provides a generic information model that is needed to support the service provided by the Directory. In the context of IN, the generic information model should conform to the part of the Recommendation going from clauses 1 to 7 of the Recommendation X.501. However certain aspects of this Recommendation need not to be supported. This includes the DIT content rules whose use is a local matter. + +Some other points are outside the scope of this Recommendation. This concerns the distributed procedures, the replications procedures and other items associated with capabilities not covered by IN CS-1. Therefore the following parts of Rec. X.501 are not applicable: + +- Subclause 3.3 Distributed operation definitions; +- Subclause 3.4 Replication definitions; +- last paragraph of 6.3.2; +- paragraphs f), h) and i) in 16.2.3; +- paragraph a) in 16.2.4. The compare operation is not used, the search operation is used instead. Therefore the FilterMatch permission replaces the Compare permission. + +In this subclause when it is referred to Recommendation X.501, it refers to the modified version of the Recommendation X.501 including the amendments made to it (DAM2 on contexts and DAM3 on minor extensions). + +#### **2.2.2.4 ASN.1 Profile of the Directory Abstract Service for the IN CS-1** + +##### **2.2.2.4.1 ASN.1 Module for IN X.500 profile** + +This subclause contains the full ASN.1 profiling of the Directory Abstract Service. It has been successfully compiled. + +``` + +IN-DirectoryAbstractService {ccitt recommendation q 1218 modules (0) abstractService (15) version 1 (0)} + +DEFINITIONS ::= + +BEGIN + +IMPORTS +attributeError, ServiceControls, EntryInformation, EntryInformationSelection, DirectoryBindArgument, Credentials, +SearchArgument, SearchResult, SearchInfo, PartialOutcomeQualifier, AddEntryArgument, RemoveEntryArgument, +ModifyEntryArgument, ServiceProblem, UpdateProblem, SecurityProblem, directoryBindError, AddEntryResult, +BindErrorParameter, ModifyEntryResult, RemoveEntryResult, SecurityErrorParameter, ServiceErrorParameter, +AttributeErrorParameter, UpdateErrorParameter, +FROM DirectoryAbstractService {joint-iso-ccitt ds (5) module (1) directoryAbstractService (2) 2} + +Code, OPERATION, ERROR +FROM Remote-Operations-Information-Objects {joint-iso-ccitt remote-operations (4) informationObjects (5) +version1 (0)}; + +IN-ServiceControls ::= ServiceControls +(WITH COMPONENTS { + options ({chainingProhibited, localScope}| + {chainingProhibited, localScope, dontDereferenceAliases, subentries}| + {chainingProhibited, localScope, dontDereferenceAliases}| + {chainingProhibited, localScope, subentries}...), + priority , + timeLimit ABSENT, + sizeLimit ABSENT, + scopeOfReferral ABSENT, + attributeSizeLimit ABSENT}, + ...) + +IN-EntryInformationSelection ::= EntryInformationSelection +(WITH COMPONENTS { + attributes , + infoTypes (attributeTypesAndValues ....), + extraAttributes OPTIONAL, + contextSelection OPTIONAL, + returnContexts }, + ...) + +IN-EntryInformation ::= EntryInformation +(WITH COMPONENTS { + name PRESENT, + fromEntry (TRUE ....), + information (WITH COMPONENTS { + attributeType ABSENT, + attribute PRESENT}, + ..) OPTIONAL, + incompleteEntry , + partialNameResolution (FALSE ...), + ...) + +UNSIGNED {Type} ::= OPTIONALLY-SIGNED {Type} +(WITH COMPONENTS { + unsigned PRESENT, + signed ABSENT} ...) + +in-DirectoryBind OPERATION ::= { + ARGUMENT IN-DirectoryBindArgument + RESULT IN-DirectoryBindResult + ERRORS {in-DirectoryBindError}} + +IN-DirectoryBindArgument ::= DirectoryBindArgument +(WITH COMPONENTS { + credentials (IN-Credentials ....) OPTIONAL, + versions } ....) + +IN-Credentials ::= Credentials +(WITH COMPONENTS { + simple , + strong ABSENT, + externalProcedure } ....) + +``` + +**IN-DirectoryBindResult ::= IN-DirectoryBindArgument** + +**in-DirectoryBindError ERROR ::= {** +    **PARAMETER IN-DirectoryBindErrorParameter}** + +**IN-DirectoryBindErrorParameter ::= DirectoryBindErrorParameter** +    **(WITH COMPONENTS {** +        **versions ,** +        **error (WITH COMPONENTS {** +            **securityError (SecurityProblem (1|2|7 ....)),** +            **serviceError (ServiceProblem (2 ....))} ....)}** + +**in-Search OPERATION ::= {** +    **ARGUMENT IN-SearchArgument** +    **RESULT IN-SearchResult** +    **ERRORS {nameError | in-ServiceError | in-SecurityError | attributeError}** +    **CODE id-opcode-in-search}** + +**IN-SearchArgument ::= UNSIGNED {SearchArgument** +    **(WITH COMPONENTS {** +        **baseObject PRESENT,** +        **subset ,** +        **filter ,** +        **searchAliases (TRUE ....),** +        **selection (IN-EntryInformationSelection ....),** +        **pagedResults ABSENT,** +        **matchedValuesOnly ,** +        **extendedFilter ABSENT** +        **serviceControls (IN-ServiceControls ....),** +        **securityParameters OPTIONAL,** +        **requestor ABSENT,** +        **operationProgress ({nameResolutionPhase notStarted} ....),** +        **aliasedRDNs ABSENT,** +        **criticalExtensions OPTIONAL,** +        **referenceType ABSENT,** +        **entryOnly (TRUE ....),** +        **exclusions ABSENT,** +        **nameResolveOnMaster (FALSE ....),** +        **checkOverspecified },** +    **...)}** + +**IN-SearchResult ::= UNSIGNED {SearchResult** +    **(WITH COMPONENTS {** +        **searchInfo (WITH COMPONENTS {** +            **name ,** +            **entries (WITH COMPONENT (IN-EntryInformation ....) ....),** +            **partialOutcomeQualifier PartialOutcomeQualifier** +            **(WITH COMPONENTS {** +                **limitProblem OPTIONAL,** +                **unexplored ABSENT** +                **unavailableCriticalExtensions ,** +                **unknownErrors ABSENT,** +                **queryReference ABSENT,** +                **overspectFilter OPTIONAL},** +            **...) ....),** +            **securityParameters ABSENT,** +            **performer ABSENT,** +            **aliasDereferenced },** +            **...),** +            **uncorrelatedSearchInfo ABSENT},** +        **...)}** + +**in-AddEntry OPERATION ::= {** +    **ARGUMENT IN-AddEntryArgument** +    **RESULT AddEntryResult** +    **ERRORS {nameError | in-ServiceError | in-SecurityError | attributeError | in-UpdateError}** +    **CODE id-opcode-in-addEntry}** + +``` + +IN-AddEntryArgument ::= UNSIGNED {AddEntryArgument + (WITH COMPONENTS { + object PRESENT, + entry PRESENT, + targetSystem ABSENT, + serviceControls (IN-ServiceControls ....), + securityParameters OPTIONAL, + requestor ABSENT, + operationProgress ({nameResolutionPhase notStarted} ....), + aliasedRDNs ABSENT, + criticalExtensions OPTIONAL, + referenceType ABSENT, + entryOnly (TRUE ....), + exclusions ABSENT, + nameResolveOnMaster (FALSE ....)}, + ...)} + +in-RemoveEntry OPERATION ::= { + ARGUMENT IN-RemoveEntryArgument + RESULT RemoveEntryResult + ERRORS {nameError | in-ServiceError | in-SecurityError | in-UpdateError} + CODE id-opcode-in-removeEntry} + +IN-RemoveEntryArgument ::= UNSIGNED {RemoveEntryArgument + (WITH COMPONENTS { + object PRESENT, + serviceControls (IN-ServiceControls ....), + securityParameters OPTIONAL, + requestor ABSENT, + operationProgress ({nameResolutionPhase notStarted} ....), + aliasedRDNs ABSENT, + criticalExtensions OPTIONAL, + referenceType ABSENT, + entryOnly (TRUE ....), + exclusions ABSENT, + nameResolveOnMaster (FALSE ....)}, + ...)} + +in-ModifyEntry OPERATION ::= { + ARGUMENT IN-ModifyEntryArgument + RESULT ModifyEntryResult + ERRORS {nameError | in-ServiceError | in-SecurityError | attributeError | in-UpdateError} + CODE id-opcode-in-modifyEntry} + +IN-ModifyEntryArgument ::= UNSIGNED {ModifyEntryArgument + (WITH COMPONENTS { + object PRESENT, + changes PRESENT, + selection (IN-EntryInformationSelection ....), + serviceControls (IN-ServiceControls ....), + securityParameters OPTIONAL, + requestor ABSENT, + operationProgress ({nameResolutionPhase notStarted} ....), + aliasedRDNs ABSENT, + criticalExtensions OPTIONAL, + referenceType ABSENT, + entryOnly (TRUE ....), + exclusions ABSENT, + nameResolveOnMaster (FALSE ....)}, + ...)} + +IN-ModifyEntryResult ::= ModifyEntryResult + (WITH COMPONENTS { + null , + information UNSIGNED {Information + (WITH COMPONENTS { + +``` + +``` + + entry (IN-EntryInformation ....), + securityParameters OPTIONAL, + performer ABSENT, + aliasDereferenced }, + ...}}}; + ... +) + +in-SecurityError ERROR ::= { + PARAMETER IN-SecurityErrorParameter + CODE id-errcode-in-securityError} + +IN-SecurityErrorParameter ::= SecurityErrorParameter + (WITH COMPONENTS { + problem (SecurityProblem (1 | 2 | 3 | 6/7 ....) ....) ....) + +in-ServiceError ERROR ::= { + PARAMETER IN-ServiceErrorParameter + CODE id-errcode-in-serviceError} + +IN-ServiceErrorParameter ::= ServiceErrorParameter + (WITH COMPONENTS { + problem (ServiceProblem (1 | 2 | 3 | 5 | 8 | 9 | 10 | 12 ....) ....) ....) + +in-UpdateError ERROR ::= { + PARAMETER IN-UpdateErrorParameter + CODE id-errcode-in-updateError} + +IN-UpdateErrorParameter ::= UpdateErrorParameter + (WITH COMPONENTS { + problem (UpdateProblem (1/2/3/4/5/7 ....) ....) ....) + +id-errcode-in-serviceError Code ::= local:2 +id-errcode-in-securityError Code ::= local:3 +id-errcode-in-updateError Code ::= local:4 + +id-opcode-in-modifyEntry Code ::= local:1 +id-opcode-in-addEntry Code ::= local:2 +id-opcode-in-removeEntry Code ::= local:3 +id-opcode-in-search Code ::= local:4 + +END + +``` + +#### 2.2.2.4.2 ASN.1 Modules for the DAP + +This subclause includes all of the ASN.1 type and value definitions contained in this Directory Specification, in the form of the ASN.1 module, "DirectoryAccessProtocol". It also includes all of the ASN.1 Object Identifiers assigned in this Specification, in the form of a ASN.1 module, "ProtocolObjectIdentifiers". + +``` + +INDirectoryAccessProtocol {ccitt recommendation q 1218 module(0) indap(12) version1( 0)} +DEFINITIONS ::= +BEGIN + +``` + +-- EXPORTS All -- + +-- *The types and values defined in this module are exported for use in the other ASN.1 modules contained within the Directory Specifications, and for the use of other applications which will use them to access Directory services. Other applications may use them for their own purposes, but this will not constrain extensions and modifications needed to maintain or improve the Directory service.* + +IMPORTS + +``` + +directoryAbstractService + FROM UsefulDefinitions {joint-iso-ccitt ds(5) module(1) usefulDefinitions(0) 2} + +ROS-OBJECT-CLASS, CONTRACT, OPERATION-PACKAGE, CONNECTION-PACKAGE, +Code, OPERATION + FROM Remote-Operations-Information-Objects + {joint-iso-ccitt remote-operations(4) informationObjects(5) version1(0)} + +Bind{}, Unbind{}, InvokeID + FROM Remote-Operations-Generic-ROS-PDUs + {joint-iso-ccitt remote-operations(4) generic-ROS-PDUs(6) version1(0)} + +``` + +``` + +TCAPMessage {} + FROM TCAPMessages + {ccitt recommendation q 773 modules(2) messages(1) version3(3)} + +APPLICATION-CONTEXT + FROM TC-Notation-Extension + {ccitt recommendation q 775 modules(2) notation-extensions (4) version1(1)} + +dialogue-as-id + FROM DialoguePDUs + {ccitt recommendation q 773 modules(2) dialoguePDUs (2) version1(1)} + +id-ac-directoryAccessAC, id-rosObject-dua, id-rosObject-directory, id-rosObject-dapDSA, +id-contract-dap, id-package-dapConnection, id-package-search, id-package-modify, +id-as-directoryOperationsAS, id-as-directoryBindingAS + FROM SDFProtocolObjectIdentifiers + {ccitt recommendation q 1218 modules(0) sdfProtocolObjectIdentifiers (10) version1 (0)} + +directoryUnbind FROM DirectoryAbstractService directoryAbstractService ; + +directoryBind, search, addEntry, removeEntry, modifyEntry + FROM ExtendedDirectoryAbstractService + {ccitt recommendation q 1218 modules(0) informationFramework (11) version1( 0)} + +``` + +-- application contexts -- + +``` + +iNdirectoryAccessAC APPLICATION-CONTEXT ::= +{ + CONTRACT dapContract + DIALOGUE MODE structured + TERMINATION basic + ABSTRACT SYNTAXES { dialogue-abstract-syntax | + inDirectoryOperationsAbstractSyntax | + inDirectoryBindingAbstractSyntax } + APPLICATION CONTEXT NAME id-ac-directoryAccessAC +} + +``` + +-- ROS-objects -- + +``` + +dua ROS-OBJECT-CLASS ::= +{ + INITIATES { dapContract } + ID id-rosObject-dua +} + +directory ROS-OBJECT-CLASS ::= +{ + RESPONDS { dapContract } + ID id-rosObject-directory +} + +``` + +``` + +dap-dsa ROS-OBJECT-CLASS ::= +{ + RESPONDS { dapContract } + ID id-rosObject-dapDSA +} + +``` + +-- contracts -- + +``` + +dapContract CONTRACT ::= +{ + CONNECTION dapConnectionPackage + INITIATOR CONSUMER OF {searchPackage | modifyPackage } + ID id-contract-dap +} + +``` + +-- connection package -- + +dapConnectionPackage CONNECTION-PACKAGE ::= +{ +    BIND                            directoryBind +    UNBIND                        directoryUnbind +    ID                              id-package-dapConnection +} + +-- search package -- + +searchPackage OPERATION-PACKAGE ::= +{ +    CONSUMER INVOKES            {search } +    ID                            id-package-search +} + +-- modify package -- + +modifyPackage OPERATION-PACKAGE ::= +{ +    CONSUMER INVOKES            { addEntry | removeEntry | modifyEntry } +    ID                            id-package-modify +} + +-- abstract-syntaxes -- + +inDirectoryOperationsAbstractSyntax ABSTRACT-SYNTAX ::= { +    BasicDAP-PDUs +    IDENTIFIED BY                id-as-directoryOperationsAS } + +BasicDAP-PDUs ::= TCAPMessage {{ DAP-Invokable }, { DAP-Returnable } } + +DAP-Invokable OPERATION ::= {search | addEntry | removeEntry | modifyEntry} + +DAP-Returnable OPERATION ::= {search | addEntry | removeEntry | modifyEntry} + +inDirectoryBindingAbstractSyntax ABSTRACT-SYNTAX ::= { +    DAPBinding-PDUs +    IDENTIFIED BY                id-as-directoryBindingAS } + +DAPBinding-PDUs ::= CHOICE +{ +    bind                            Bind { directoryBind }, +    unbind                        Unbind { directoryUnbind } +} + +END + +SDFProtocolObjectIdentifiers + +{ccitt recommendation q 1218 module(0) sdfProtocolObjectIdentifiers(10) version1 (0)} + +DEFINITIONS ::= + +BEGIN + +-- EXPORTS All -- + +IMPORTS + +-- useful definitions + +in-ds OBJECT IDENTIFIER ::= +{ccitt recommendation q 1218 sdf-objects (10)} + +id-rosObject OBJECT IDENTIFIER ::= {in-ds 25} +id-contract OBJECT IDENTIFIER ::= {in-ds 26} +id-package OBJECT IDENTIFIER ::= {in-ds 27} +id-ac OBJECT IDENTIFIER ::= {in-ds 3} +id-as OBJECT IDENTIFIER ::= {in-ds 5} + +-- ROS Objects -- + +| | | | | +|------------------------|-------------------|-----|------------------| +| id-rosObject-dua | OBJECT IDENTIFIER | ::= | {id-rosObject 1} | +| id-rosObject-directory | OBJECT IDENTIFIER | ::= | {id-rosObject 2} | +| id-rosObject-dapDSA | OBJECT IDENTIFIER | ::= | {id-rosObject 3} | + +-- contracts -- + +| | | | | +|-----------------|-------------------|-----|-----------------| +| id-contract-dap | OBJECT IDENTIFIER | ::= | {id-contract 1} | +|-----------------|-------------------|-----|-----------------| + +-- packages -- + +| | | | | +|--------------------------|-------------------|-----|-----------------| +| id-package-search | OBJECT IDENTIFIER | ::= | {id-package 2} | +| id-package-modify | OBJECT IDENTIFIER | ::= | {id-package 3} | +| id-package-dapConnection | OBJECT IDENTIFIER | ::= | {id-package 10} | + +-- application contexts -- + +| | | | | +|-------------------------|-------------------|-----|-----------| +| id-ac-directoryAccessAC | OBJECT IDENTIFIER | ::= | {id-ac 1} | +|-------------------------|-------------------|-----|-----------| + +-- abstract syntaxes -- + +| | | | | +|-----------------------------|-------------------|-----|-----------| +| id-as-directoryOperationsAS | OBJECT IDENTIFIER | ::= | {id-as 1} | +| id-as-directoryBindingAS | OBJECT IDENTIFIER | ::= | {id-as 2} | + +END + +### 3 Semantics + +#### 3.1 Definition of procedures and entities + +##### 3.1.1 SSF application entity procedures + +###### 3.1.1.1 General + +This clause provides the definition of the SSF Application Entity (AE) procedures related to the SSP-SCP interface. The procedures are based on the use of Common Channel Signalling System No. 7 (CCSS No. 7); other signalling systems can be used (e.g. DSS 1-layer 3). + +Capabilities not explicitly covered by these procedures may be supported in an implementation dependent manner in the SSP, while remaining in line with clause 2. + +The AE, following the architecture defined in the Recommendations Q.700, Q.771 and Q.1400, includes Transaction Capabilities Application Part (TCAP) and one or more ASEs called TC-users. The following subclauses define the TC-user ASE which interfaces with TCAP using the primitives specified in Recommendation Q.771; other signalling systems, such as DSS 1 (layer 3), may be used. + +The procedure may equally be used with other signalling message transport systems supporting the application layer structures defined. + +In case interpretations for the application entity procedures defined in the following differ from detailed procedures and the rules for using of TCAP service, the statements and rules contained in the detailed subclauses 3.3 and 3.4 shall be followed. + +###### 3.1.1.2 Model and interfaces + +The functional model of the AE-SSF is shown in Figure 9; the ASEs interface to TCAP to communicate with the SCF, and interface to the call control function (CCF) and the maintenance functions already defined for switching systems. The scope of this Recommendation is limited to the shaded area in Figure 9. + +The interfaces shown in Figure 9 use the TC-user ASE primitives specified in Recommendation Q.771 and N-Primitives specified in Recommendation Q.711. The operations and parameters of Intelligent Network Application Protocol (INAP) are defined in clause 2. + +![Functional model of SSF-AE diagram showing nested functional blocks. The outermost block is 'Application process invocation (call control functions, maintenance functions)'. Inside it is 'Service switching functions' (SSF), which contains a dashed box for 'MACF'. Below MACF is 'SAO', which connects to a vertical 'SACF' block. SACF connects to two 'ASE' blocks and a 'TCAP' block (labeled 'a)'). The 'SSF-FSM' block contains the 'ASE' blocks and 'TCAP'. The entire SSF block is part of an 'AEI' (Application Entity Invocation). At the bottom, a separate block labeled 'SCCP/DSS 1/Others' is connected to the AEI via a line labeled 'b)'.](bd33d5bc49161429f4c7da76529bcd18_img.jpg) + +Functional model of SSF-AE diagram showing nested functional blocks. The outermost block is 'Application process invocation (call control functions, maintenance functions)'. Inside it is 'Service switching functions' (SSF), which contains a dashed box for 'MACF'. Below MACF is 'SAO', which connects to a vertical 'SACF' block. SACF connects to two 'ASE' blocks and a 'TCAP' block (labeled 'a)'). The 'SSF-FSM' block contains the 'ASE' blocks and 'TCAP'. The entire SSF block is part of an 'AEI' (Application Entity Invocation). At the bottom, a separate block labeled 'SCCP/DSS 1/Others' is connected to the AEI via a line labeled 'b)'. + +T1146720-92/d09 + +AEI Application Entity Invocation + SSF Service Switching Functions + FSM Finite State Machine + MACF Multiple Association Control Function + SACF Single Association Control Function + SAO Single Association Object + +a) TC-Primitives + b) N-Primitives + +NOTE – SSF-FSM includes several finite state machines. + +FIGURE 9/Q.1218 +**Functional model of SSF-AE** + +### 3.1.1.3 Relations between SSF-FSM and the CCF and maintenance functions + +The primitive interface between the SSF-FSM and the CCF/maintenance functions is an internal interface and is not subject to standardization in CS-1. Nevertheless this interface should be in line with the BCSM defined in 4.2.1.2/Q.1214. + +The relationship between the BCSM and the SSF-FSM may be described as follows for the case of a call/attempt initiated by an end user, and the case of a call/attempt initiated by IN service logic: + +- When a call/attempt is initiated by an end user and processed at an exchange, an instance of a BCSM is created. As the BCSM proceeds, it encounters detection points (DPs, see 4.2/Q.1214). If a DP is armed as a Trigger DP (TDP) an instance of an SSF-FSM is created. +- If an InitiateCallAttempt is received from the SCF, an instance of a BCSM is created, as well as an instance of an SSF-FSM. + +The SSF logic should: + +- perform the DP processing actions specified in 4.2.2.7/Q.1214, including if DP criteria are met; +- check if traffic mechanisms are active; +- check for SCF accessibility; +- handle service feature interactions. + +The SSF hands control back to the CCF at least in the following cases: + +- If call gapping is in effect – The SSF logic will instruct the CCF to terminate the call with the appropriate treatment. +- If service filtering is in effect – The call is counted (if required) and the SSF logic instructs the CCF to handle the call with the appropriate treatment. +- If a trigger (TDP) criteria match is not found (e.g. insufficient information to proceed) – The SSF logic returns call control to the CCF. +- If the call is abandoned – The SSF logic returns call control to the CCF and continues processing as described in 3.1.1.5. +- If the destination SCF is not accessible – The SSF logic will instruct the CCF to route the call if possible (e.g. default routing to a terminating announcement). +- If there is an existing control relationship for the call and the DP is armed as an EDP-R – The SSF returns call control to the CCF. + +The management functions related to the execution of operations received from the SCF are executed by the SSF Management Entity (SSME). The SSME comprises a SSME-Control and several instances of SSME FSMs. The SSME-control interfaces the different SSF FSMs and SSME FSMs respectively and the Functional Entity Access Manager (FEAM). Figure 10 shows the SSF Interfaces. + +![Diagram of SSF interfaces showing FEAM, SSME-Control, SSF FSMs, and SSME FSMs within an SSF boundary, interfacing with SRF and SCF.](9bafc60bf378685e5e246c3ffad7b792_img.jpg) + +The diagram illustrates the internal architecture of the SSF (Service Switching Function) and its interfaces. A central oval labeled 'SSME-Control' is connected to a circle labeled 'FEAM' above it and to several circles below it. The circles below 'SSME-Control' are labeled 'SSF FSM', 'SSF FSM', 'SSME FSM', and 'SSME FSM', with ellipses between the second and third circles. All these circles are contained within a dashed rectangular boundary labeled 'SSF' at the bottom. The 'FEAM' circle is connected to two external entities: 'SRF' (Service Requesting Function) on the left and 'SCF' (Service Controlling Function) on the right, both via double-headed arrows. The 'SSF' boundary is labeled 'T1169150-94/d10' at the bottom right. + +Diagram of SSF interfaces showing FEAM, SSME-Control, SSF FSMs, and SSME FSMs within an SSF boundary, interfacing with SRF and SCF. + +FIGURE 10/Q.1218 +SSF interfaces + +The Functional Entity Access Manager (FEAM) provides the low level interface maintenance functions including the following: + +- 1) establishing and maintaining the interfaces to the SCF and SRF; +- 2) passing and queuing (when necessary) the messages received from the SCF and SRF to the SSME-Control; +- 3) formatting, queuing (when necessary), and sending the messages received from the SSME-Control to the SCF and SRF. + +The SSME-control maintains the dialogues with the SCF and SRF on behalf of all instances of the SSF Finite State Machine (FSM). These instances of the SSF FSM occur concurrently and asynchronously as calls occur, which explains the need for a single entity that performs the task of creation, invocation and maintenance of the SSF-FSMs. In particular the SSME-control performs the following tasks: + +- 1) Interprets the input messages from other FEs and translates them into corresponding SSF FSM events. +- 2) Translates the SSF-FSM outputs into corresponding messages to other FEs. +- 3) Captures asynchronous (with call processing) activities related to management or supervisory functions in the SSF and creates an instance of a SSME-FSM. For example, the SSME provides non-call associated treatment due to changes in Service Filtering or Call Gapping. Therefore, the SSME-control separates the SSF-FSM from the Call Gapping and Service Filtering functions by creating instances of SSME-FSMs for each context of management related operations. + +The different contexts of the SSME-FSMs may be distinguished based on the address information provided in the initiating operations. In the case of service filtering this address information is given by filteringCriteria, i.e. all ActivateServiceFiltering operations using the same address, address the same SSME-FSM handling this specific service filtering instance. For example ActivateServiceFiltering operations providing different filtering Criteria cause the invocation of new SSME-FSMs. + +The SSF-FSM passes call handling instructions to the related instances of the BCSM as needed. DPs may be dynamically armed as Event DPs, requiring the SSF-FSM to remain active. At some point, further interaction with the SCF is not needed, and the SSF-FSM may be terminated while the BCSM continues to handle the call as needed. A later TDP in the BCSM may result in a new instance of the SSF-FSM for the same call. + +Consistent with the single-ended control characteristic of IN service features for CS-1, the SSF-FSM only applies to a functionally separate call portion (e.g. the originating BCSM or the terminating BCSM in a two-party call, but not both). + +#### **3.1.1.4 SSF Management Finite State Machine (SSME-FSM)** + +The SSME-FSM state diagram is described in Figure 11. + +The SSME-FSM is independent of the individual SSF-FSMs. + +The non-call associated treatment state is entered from the IdleManagement state when one of the following non-call associated operations is received (transition em1): + +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport; +- ActivateServiceFiltering; +- CallGap; +- ActivityTest. + +The CallGap operation may be received inside as well as outside a call context transaction. The ActivityTest operation applies to call context transactions only. The ActivateServiceFiltering operation may be received outside a call context only. + +![SSME-FSM state diagram showing two states: State mb (Non-call Associated Treatment) and State ma (Idle Management). State mb has a self-loop transition em3. There is a transition em1 from State ma to State mb and a transition em2 from State mb to State ma. The diagram is labeled T1169140-94/d11.](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State ma + State ma --> State mb : em1 + State mb --> State ma : em2 + State mb --> State mb : em3 + state "State mb" as State mb + State mb : Non-call Associated Treatment + state "State ma" as State ma + State ma : Idle Management + +``` + +T1169140-94/d11 + +SSME-FSM state diagram showing two states: State mb (Non-call Associated Treatment) and State ma (Idle Management). State mb has a self-loop transition em3. There is a transition em1 from State ma to State mb and a transition em2 from State mb to State ma. The diagram is labeled T1169140-94/d11. + +FIGURE 11/Q.1218 +**SSME-FSM state diagram** + +During this state the following events can occur: + +- given that service filtering is active, the SSF needs to send a service filtering response to the SCF: the SSME-FSM remains in this state (transition em3); +- given that service filtering is active, the SSF needs to increment a counter: the SSME FSM remains in this state (transition em3); +- given that service filtering is active and the service filtering duration expires: the SSME should move to the Idle Management state (transition em2) and send a ServiceFilteringResponse operation to the SCF; +- given that status report is active previously requested by a RequestEveryStatusChangeReport operation, the SSF needs to send a StatusReport operation: the SSF remains in this state (transition em3); +- given that status report is active previously requested by a RequestFirstStatusMatchReport operation, the SSF needs to send a StatusReport operation: the SSF transits to Idle Management state (transition em2); +- given that status report is active previously requested by a RequestFirstStatusMatchReport or a RequestEveryStatusMatchReport operation, and the CancelStatusReportRequest operation is received by the SSF or the status report duration expires, the SSME-FSM should move to the Idle Management state (transition em2); +- given that status report is active previously requested by a RequestCurrentStatusReport operation, the SSF sends the StatusReport operation, the SSME-FSM should move to the Idle Management state (transition em2); +- if call gap related duration timer expires, the SSME-FSM should move to the Idle Management state (transition em2); +- given that call gap/service filtering is active, another CallGap/ActivateServiceFiltering operation could be received by the SSF, which has the same gapping/filtering criteria: the second “filter” or “gap” replace the first one (transition em3) unless the duration timer value is equal to zero, in which case the SSME-FSM should move to the Idle Management state (transition em2). + +All other operations have no effect on the SSME-FSMs; the operations are passed by the SSME-Control to the relevant SSF-FSM. + +### 3.1.1.5 SSF state transition diagram + +Figure 12 shows the state diagram of the SSF part of the SSP during the processing of an IN call/attempt. + +![State transition diagram for the SSF finite state machine. The diagram shows five states: State a (idle), State c (waiting for instructions), State d (waiting for end of user interaction), State e (waiting for end of temporary connection), and State f (monitoring). Transitions are labeled e1 through e16. State a has a self-loop e1 and transitions e3 and e4 to State c. State c has a self-loop e14, a transition e9 back to State a, transitions e10 and e11 to State f, transitions e5 and e6 to State d, and transitions e7 and e8 to State e. State d has a self-loop e13. State e has a self-loop e15 and transition e16 to State f. State f has a transition e12 back to State a and an unlabeled self-loop.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +``` + +stateDiagram-v2 + State_a: State a +idle + State_c: State c +waiting for instructions + State_d: State d +waiting for end of user interaction + State_e: State e +waiting for end of temporary connection + State_f: State f +monitoring + + State_a --> State_a : e1 + State_a --> State_c : e3 + State_a --> State_c : e4 + State_c --> State_a : e9 + State_c --> State_c : e14 + State_c --> State_d : e5 + State_c --> State_d : e6 + State_c --> State_e : e7 + State_c --> State_e : e8 + State_c --> State_f : e10 + State_c --> State_f : e11 + State_d --> State_d : e13 + State_e --> State_e : e15 + State_e --> State_f : e16 + State_f --> State_a : e12 + State_f --> State_f + +``` + +State transition diagram for the SSF finite state machine. The diagram shows five states: State a (idle), State c (waiting for instructions), State d (waiting for end of user interaction), State e (waiting for end of temporary connection), and State f (monitoring). Transitions are labeled e1 through e16. State a has a self-loop e1 and transitions e3 and e4 to State c. State c has a self-loop e14, a transition e9 back to State a, transitions e10 and e11 to State f, transitions e5 and e6 to State d, and transitions e7 and e8 to State e. State d has a self-loop e13. State e has a self-loop e15 and transition e16 to State f. State f has a transition e12 back to State a and an unlabeled self-loop. + +NOTE - The abandon and disconnect transition is not shown. + +FIGURE 12/Q.1218 +**SSF finite state machine** + +Each state is discussed in the following subclauses. General rules applicable to more than one state are addressed here. + +One or a sequence of components received in one or more TCAP messages may include a single operation or multiple operations, and is processed as follows: + +- Process the operations in the order in which they are received. +- Each operation causes a state transition independent of whether or not a single operation or multiple operations are received in a message. + +- The SSF examines subsequent operations in the sequence. As long as sequential execution of these operations would leave the FSM in the same state, it will execute them (e.g. RequestReportBCSMEVENT). If a subsequent operation causes a transition out of the state, then the following operations should be buffered until the current operation has been executed. In all other cases, await an event that would cause a transition out of the current state (such an event would be the completion of operation being executed, or reception of an external event). An example of this is as follows: + - The SSF receives the operations FurnishChargingInformation, ConnectToResource, and PlayAnnouncement in a component sequence inside a single TCAP message. Upon receipt of this message, these operations are executed up to and including ConnectToResource while the SSF is in the Waiting For Instructions state. As the ConnectToResource operation is executed (and when, or after the FurnishChargingInformation operation has been completed), the SSF-FSM will transit to the Waiting For End Of User Interaction state. The PlayAnnouncement operation is relayed to the SRF while the SSF is in Waiting For End Of User Interaction state. +- If there is an error in processing one of the operations in the sequence, the SSF-FSM processes the error (see below) and discards all remaining operations in the sequence. +- If an operation is not understood or is out of context (i.e. violates the SACF rules defined by the SSF-FSM) as described above, ABORT the interaction. For example, when the SSF-FSM applies to an originating BCSM, then receiving SelectFacility operation would be out of context since this applies only to the terminating half of the BCSM. + +In any state, if there is an error in a received operation, the maintenance functions are informed and the SSF-FSM remains in the same state as when it received the erroneous operation; depending on the class of the operation, the error could be reported by the SSF to the SCF using the appropriate component (see Recommendation Q.774). + +In any state (except idle), if the calling party abandons the call before it is answered (i.e. before the Active PIC in the BCSM), then the SSF-FSM should instruct the CCF to clear the call and ensure that any CCF resources allocated to the call have been de-allocated, then continue processing as follows: + +- If the Abandon DP is not armed and there is no call information request pending, then transition to the idle state. +- If the Abandon DP is not armed and there is a CallInformationRequest pending, send a CallInformationReport, then transit to the Idle state. +- If the Abandon DP is armed as an EDP-R, send an EventReportBCSM or a DP specific operation, then transit to the Waiting For Instructions state. If a CallInformationRequest is pending, a CallInformationRequest shall be sent before the corresponding EventReportBCSM or a DP specific operation is sent. +- If the Abandon DP is armed as an EDP-N and there is no CallInformationRequest pending, send an EventReportBCSM or a DP specific operation, then transit to the Idle state. +- If the Abandon DP is armed as an EDP-N and there is a CallInformationRequest pending, send an EventReportBCSM or a DP specific operation, followed by a CallInformationReport, then transit to the Idle state. +- Other pending requests that should be treated in the same way as the CallInformationRequest in the above list is the ApplyCharging. + +In any state (except Idle), if a call party disconnects from a stable call (i.e. from the Active PIC in the BCSM), then the SSF-FSM should process this event as follows: + +- If the Disconnect DP is not armed for that specific leg and there is no CallInformationRequest pending, transit to the Idle state. +- If the Disconnect DP is not armed and there is a CallInformationRequest pending, send a CallInformationReport and transit to the Idle state. + +- If the Disconnect DP is armed as an EDP-R for that specific leg, send an EventReportBCSM or a DP specific operation, then transit to the Waiting For Instructions state. If a Call Information Request is pending, a CallInformationReport shall be sent before the corresponding EventReportBCSM or a DP specific operation is sent. +- If the Disconnect DP is armed as an EDP-N and there is no CallInformationRequest pending, send an EventReportBCSM or a DP specific operation, then transit to the Idle state. +- If the Disconnect DP is armed as an EDP-N and there is a CallInformationRequest pending, send an EventReportBCSM or a DP specific operation and a CallInformationReport, then transit to the Idle state. +- Other pending requests that should be treated in the same way as the CallInformationRequest in the above list is the ApplyCharging. + +In any state (except Idle), an EventNotificationCharging can be sent to the SCF, if previously requested by a RequestNotificationCharging and if the charging event has been detected by the CCF. In this case no state transition takes place. + +The SSF has an application timer, $T_{\text{SSF}}$ , whose purpose is to prevent excessive call suspension time and to guard the association between the SSF and the SCF. + +Timer $T_{\text{SSF}}$ is set in the following cases: + +- When the SSF sends an InitialDP, DP specific (refer to 3.1.1.5.2 State c: Waiting For Instructions), or AssistRequestInstructions operation (refer to 3.1.1.6.2 State b: Waiting For Instructions in assisting/handoff case). While waiting for the first response from the SCF, the timer $T_{\text{SSF}}$ can be reset only once by a ResetTimer operation. Subsequent to the first response, the timer can be reset any number of times. +- When the SSF enters the Waiting For Instructions state (refer to 3.1.1.5.2) under any other condition than the ones listed in the previous case. In this case the SCF may reset the $T_{\text{SSF}}$ timer using the ResetTimer operation any number of times. +- When the SSF receives a HoldCallInNetwork operation (refer to 3.1.1.5.2 State c: Waiting For Instructions). In this case the SCF may reset $T_{\text{SSF}}$ using the ResetTimer operation any number of times. +- When the SSF enters the Waiting For End of User Interaction state or the Waiting For End of Temporary Connection state (refer to 3.1.1.5.3 and 3.1.1.5.4). In these cases the SCF may reset $T_{\text{SSF}}$ using the ResetTimer operation any number of times.(OPTIONAL). + +NOTE – This "OPTIONAL" means that the application timer $T_{\text{SSF}}$ is optionally set. Whether it is used or not depends on implementation. But it must be synchronized with $T_{\text{SCF-SSF}}$ in the SCSM. + +In the four above cases $T_{\text{SSF}}$ may respectively have four different values as defined by the application. + +When receiving or sending any operation which is different from the above, the SSF should reset $T_{\text{SSF}}$ to the last used set value. This value is either one associated to the four different cases as listed above, or received in a ResetTimer operation, whatever occurred last. In the monitoring state (refer to 3.1.1.5.5) $T_{\text{SSF}}$ is not used. + +On expiration of $T_{\text{SSF}}$ the SSF-FSM transitions to the idle state, aborts the interaction with the SCF and the CCF progresses the BCSM if possible. + +The SSF state diagram contains the following transitions (events): + +- e1 TDP-N encountered +- e3 InitiateCallAttempt received +- e4 TDP-R encountered +- e5 User interaction requested +- e6 User interaction ended +- e7 Temporary connection created +- e8 Temporary connection ended +- e9 Idle return from wait for instruction + +- e10 EDP-R encountered +- e11 Routing instruction received +- e12 EDP-N last encountered or ReleaseCall received or Cancel(allRequests) received +- e13 Waiting for End of User Interaction state no change +- e14 Waiting for Instructions state no change +- e15 Waiting for End of Temporary Connection state no change +- e16 Monitoring state no change +- e17 Abandon (from any state) (not shown in the SSF state diagram) +- e18 Disconnect (from any state) (not shown in the SSF state diagram) +- e19 Non-Call Associated Treatment from any state (not shown in the SSF state diagram) + +The SSF state diagram contains the following states: + +- State a Idle +- State c Waiting for Instructions +- State d Waiting for End of User Interaction +- State e Waiting for End of Temporary Connection +- State f Monitoring + +### 3.1.1.5.1 State a – Idle + +The SSF-FSM enters the Idle state under a variety of conditions, as described below. + +The SSF-FSM enters the Idle state when sending or receiving an ABORT TCAP primitive due to abnormal conditions in any state. + +The SSF-FSM enters the Idle state when one of the following occurs: + +- when the call is abandoned or one or more call parties disconnect in any other state under the conditions identified in 3.1.1.5; +- when a Connect or proceed call processing operation is processed in the Waiting for Instructions state, and no EDPs are armed and there are no outstanding report requests (transition e9); +- when the application timer $T_{\text{SSF}}$ expires in one of the states: Waiting for Instructions, Waiting for End of User Interaction or Waiting for End of Temporary Connection; +- when a ReleaseCall operation is processed in Waiting for Instructions (transition e9) or Monitoring (transition e12); +- when the last EDP-N is encountered in the Monitoring state, and there are no EDP-Rs armed and no monitoring is active for charging events (transition e12); +- when the last charging event is encountered in the Monitoring state, and there are no EDPs armed (transition e12). + +When transiting to the Idle state, if there is a CallInformationRequest pending (see 3.1.1.5), the SSF sends a CallInformationReport operation to the SCF before returning to Idle. Once in the Idle state, if status reporting is still active the SSF deactivates it, any outstanding responses to send to the SCF are discarded. + +During this state the following call-associated events can occur: + +- indication from the CCF that an armed TDP is encountered related to a possible IN call/service attempt, the SSF-FSM acts as described below: + - if the DP is a TDP-N, send a generic InitialDetectionPoint or DP-specific operation (see Note) to the SCF, as determined from DP processing; there is no resulting transition to a different state (transition e1); + +- if the DP is a TDP-R, send a generic InitialDetectionPoint or DP-specific operation (see Note) to the SCF, as determined from DP processing, and transit to the Waiting for Instructions state (transition e4); +- the rules for DP processing are described in Recommendation Q.1214, section "DP Processing"; +- a message related to a new transaction containing an InitiateCallAttempt operation is received from the SCF: in this case the SSF-FSM moves to the state Waiting for Instructions (transition e3). + +Any other operation received from the SCF while the SSF is in Idle state should be treated as an error. The event should be reported to the maintenance functions and the transaction should be aborted according to the procedure specified in TCAP (see Recommendation Q.774). + +NOTE – DP specific operations are the following (refer to clause 2): TAnswer, TDisconnect, TermAttemptAuthorized, TMidCall, TNoAnswer, AnalysedInformation, TBusy, CollectedInformation, OAnswer, OCalledPartyBusy, ODisconnect, OMidCall, ONoAnswer, OriginationAttemptAuthorized, RouteSelectFailure. + +### 3.1.1.5.2 State c – Waiting for Instructions + +This state is entered from the Idle state, as indicated above (transition e4), directly from the Idle state on receipt at the SSF of a TC-BEGIN indication primitive containing an InitiateCallAttempt operation from the SCF (transition e3), from the state Monitoring on detection of an EDP-R (transition e10), from the state Waiting for End of User Interaction on occurrence of call disconnect from/to the SRF (transition e6), or from the state Waiting for End of Temporary Connection on occurrence of disconnection of temporary connection (transition e8). + +In this state the SSF-FSM is waiting for an instruction from the SCF; call handling is suspended and an application timer ( $T_{\text{SSF}}$ ) should be set on entering this state. + +During this state the following events can occur: + +- The user dials additional digits (applies for open-ended numbering plans) – The CCF should store the additional digits dialled by the user. +- The user abandons or disconnects. This should be processed in accordance with the general rules in 3.1.1.5. +- The application Timer $T_{\text{SSF}}$ expires – The SSF-FSM moves to the Idle state, the CCF routes the call if possible (e.g. default routing to a terminating announcement), the $T_{\text{SSF}}$ expiration is reported to the maintenance functions and the transaction is aborted. +- An operation is received from the SCF – The SSF-FSM acts according to the operation received as described below. + +The following operations may be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e14): + +- HoldCallInNetwork; +- RequestReportBCSMEEvent; +- RequestNotificationChargingEvent; +- ResetTimer; +- FurnishChargingInformation; +- ApplyCharging; +- CallInformationRequest; +- SendChargingInformation; +- Cancel. + +The following operations may be received from the SCF and processed by the SSF, causing a state transition to Waiting for End of User Interaction state (transition e5): + +- ConnectToResource. + +The following operations may be received from the SCF and processed by the SSF, causing a state transition to Waiting for End of Temporary Connection state (transition e7): + +- EstablishTemporaryConnection + +The following operations may be received from the SCF and processed by the SSF, causing a state transition to either Monitoring state (if any EDPs were armed or any reports were requested) (transition e11) or Idle state (transition e9): + +- Connect; +- CollectInformation; +- AnalyseInformation; +- SelectRoute; +- SelectFacility; +- Continue; +- ReleaseCall. + +ReleaseCall operation may be received from the SCF. In this case, the SSF-FSM should instruct the CCF to clear the call and ensure that any CCF resources allocated to the call have been de-allocated, then continue processing as follows: + +- if neither CallInformationRequest nor ApplyChargingReport operation has been requested, the SSF-FSM transits to the Idle state (transition e9); +- if CallInformationRequest or ApplyChargingReport operation has been requested, the SSF sends each operation which has been requested from SCF, and then the SSF-FSM transits to the Idle state (transition e9). + +When processing the above operations, any necessary call handling information is provided to the Call Control Function (CCF). + +Any other operation received in this state should be processed in accordance with the general rules in 3.1.1.5. + +### 3.1.1.5.3 State d – Waiting for End of User Interaction + +The SSF enters this state from the Waiting for Instructions state (transition e5) on the reception of one of the following operations: + +- ConnectToResource. + +During this state the following events can occur: + +- A valid SCF-SRF operation [i.e. PlayAnnouncement, PromptAndCollectUserInfoInformation, and Cancel(invokeID)] for relaying is received and is correct, the operation is transferred to the SRF for execution. The SSF-FSM remains in the Waiting for End of User Interaction state (transition e13). +- A valid SRF-SCF operation (i.e. SpecializedResourceReport and ReturnResult from PromptAndCollectUserInfoInformation) for relaying is received and is correct, the operation is transferred to the SCF. The SSF-FSM remains in the Waiting for End of User Interaction state (transition e13). +- The application timer $T_{\text{SSF}}$ expires (if it was set) – The SSF-FSM moves to the Idle state, the CCF routes the call if possible (e.g. default routing to a terminating announcement), the $T_{\text{SSF}}$ expiration is reported to the maintenance functions and the transaction is aborted. +- An operation is received from the SCF – The SSF-FSM acts according to the operation received as described below. +- The user abandons – This should be processed in accordance with the general rules in 3.1.1.5. + +The following operations may be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e13): + +- RequestNotificationChargingEvent; +- ResetTimer; +- FurnishChargingInformation; +- ApplyCharging; +- Send Charging Information. + +The DisconnectForwardConnection operation may be received from the SCF and processed by the SSF in this state. Call disconnect can also be received from the SRF. In both cases this causes the release of the connection to the SRF and the transition to the Waiting for Instructions state. The disconnection is not transferred to the other party (transition e6). + +Any other operation received in this state should be processed in accordance with the general rules in 3.1.1.5. + +#### 3.1.1.5.4 State e – Waiting for End of Temporary Connection + +The SSF enters this state from the Waiting for Instructions state (transition e7) upon receiving an EstablishTemporaryConnection operation. + +The call is routed to the assisting SSF-SRF and call handling is suspended while waiting for the end of the assisting procedure. The timer $T_{\text{SSF}}$ is active in this state (whether it is used or not is optional). + +During this state the following events can occur: + +- The application timer $T_{\text{SSF}}$ expires (if it was set) – The SSF-FSM moves to the Idle state, the CCF routes the call if possible (e.g. default routing to a terminating announcement), the $T_{\text{SSF}}$ expiration is reported to the maintenance functions and the transaction is aborted. +- The receipt of an indication of disconnection of forward connection from the CCF – In this case, the SSF moves to the Waiting for Instructions state (transition e8). The disconnection is not transferred to the calling party. +- The user abandons – This should be processed in accordance with the general rules in 3.1.1.5 +- An operation is received from the SCF – The SSF acts according to the operation received as described below. + +The following operations can be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e15): + +- RequestNotificationChargingEvent; +- ResetTimer; +- FurnishChargingInformation; +- ApplyCharging; +- SendChargingInformation. + +The DisconnectForwardConnection operation may be received from the SCF and processed by the SSF in this state. Call disconnect can also be received from the SRF. In both cases this causes the release of the connection to the SRF and the transition to the Waiting for Instructions state. The disconnection is not transferred to the other party (transition e8). + +Any other operation received in this state should be processed in accordance with the general rules in 3.1.1.5. + +#### 3.1.1.5.5 State f – "Monitoring" + +The SSF enters this state from the Waiting For Instructions state (transition e11) upon receiving a Connect, CollectInformation, AnalyseInformation, SelectRoute, SelectFacility, Continue, operation or processing an Initiate CallAttempt operation when one or more EDPs are armed or/and there are other reports pending (see 3.1.1.5). + +In this state the timer $T_{\text{SSF}}$ is not used, i.e. the expiration of $T_{\text{SSF}}$ does not have any impact on the SSF-FSM. + +During this state the following events can occur: + +- An EDP-N should be reported to the SCF by sending an EventReportBCSM operation or a DP specific operation; the SSF-FSM should remain in the Monitoring state (transition e16) if one or more EDPs are armed or there are report requests pending. The SSF-FSM should move to the Idle state (transition e12) if there are no remaining EDPs armed or there are no report requests pending. + +If the event causing a CallInformationReport is also detected by an armed EDP-N, then the CallInformationReport shall be sent immediately before the corresponding EventReportBCSM or a DP specific operation is sent. + +- An EDP-R should be reported to the SCF by sending an EventReportBCSM operation or a DP specific operation; the SSF-FSM should move to the Waiting For Instructions state (transition e10). +- If the event causing a CallInformationReport is also detected by an armed EDP-R, then the CallInformationReport shall be sent immediately after the corresponding EventReportBCSM or a DP specific operation is sent. +- The receipt of an END or ABORT primitive from TCAP has no effect on the call; the call may continue or be completed with the information available. In this case, the SSF-FSM transits to the Idle state (transition e12), disassociating the SSF-FSM from the call. +- An operation is received from the SCF: The SSF-FSM acts according to the operation received as described below. +- The user abandons or disconnects. This should be processed in accordance with the general rules in 3.1.1.5. + +The following operations can be received from the SCF and processed by the SSF with no resulting transition to a different state (transition e16): + +- RequestNotificationChargingEvent; +- SendChargingInformation; +- FurnishChargingInformation; +- ApplyCharging. + +The RequestReportBCSMEVENT operation may be received from the SCF. In this case, the SSF-FSM transits as follows: + +- if one or more EDPs are armed or a part of armed EDPs are disarmed, the SSF-FSM transits back to the same state (transition e16); +- if all of armed EDPs are disarmed and there is outstanding CallInformationRequest, EventNotificationCharging or ApplyChargingReport, the SSF-FSM transits back to the same state (transition e16); +- if all of armed EDPs are disarmed and there is no outstanding CallInformationRequest, EventNotificationCharging or ApplyChargingReport, the SSF-FSM transits to the Idle (transition e12). + +The Cancel(allRequests) operation may be received from the SCF and processed by the SSF, causing a state transition to the Idle state (transition e12). + +The ReleaseCall operation may be received from the SCF. In this case, the SSF-FSM should instruct the CCF to clear the call and ensure that any CCF resources allocated to the call have been de-allocated, then continue processing as follows: + +- if neither CallInformationRequest nor ApplyChargingReport operation has been requested, the SSF-FSM transits to the Idle state (transition e12); +- if CallInformationRequest or ApplyChargingReport operation has been requested, the SSF sends each operation which has been requested from SCF, and then the SSF-FSM transits to the Idle state (transition e12). + +Any other operation received in this state should be processed in accordance with the general rules in 3.1.1.5. + +### 3.1.1.6 Assisting/Handoff SSF-FSM + +This subclause describes the SSF-FSM related to the Assisting/Handoff SSF. The assisting SSF is structured as defined in 3.1.1.1 through 3.1.1.5. The Handoff FSM for CS-1 applies only to the case where final treatment is to be applied. + +Within this subclause, the term "Assisting SSF" refers to both Assisting and Handoff SSFs unless an explicit indication to one or the other is provided. + +The Assisting/Handoff SSF state diagram contains the following transitions (events) (see Figure 13): + +- ea1 Assist/Handoff detected +- ea2 Assist/Handoff fail/success +- ea3 User interaction requested +- ea4 User interaction ended +- ea5 Waiting For Instruction state no change +- ea6 Waiting For End Of User Interaction state no change +- ea7 Initiating bearer channel disconnect + +The Assisting/Handoff SSF state diagram contains the following states: + +- State a Idle +- State b Waiting for Instructions +- State c Waiting for End of User Interaction + +![State diagram for Assisting/Handoff SSF finite state machine showing three states: State a (idle), State b (waiting for instructions), and State c (waiting for end of user interaction) with transitions ea1 through ea7.](6348f4fc8b3848158fcfbe85e26a731d_img.jpg) + +``` +stateDiagram-v2 + [*] --> State_a + State_a --> State_b : ea1 + State_b --> State_a : ea2 + State_b --> State_c : ea3 + State_c --> State_a : ea4 + State_c --> State_a : ea7 + State_b --> State_b : ea5 + State_c --> State_c : ea6 + + state "State a" as State_a + State_a : idle + state "State b" as State_b + State_b : waiting for instructions + state "State c" as State_c + State_c : waiting for end of user interaction +``` + +The diagram illustrates the Assisting/Handoff SSF finite state machine. It consists of three rectangular state boxes. State a, labeled 'idle', is at the top. State b, labeled 'waiting for instructions', is in the middle. State c, labeled 'waiting for end of user interaction', is at the bottom. Transitions are indicated by arrows: ea1 from State a to State b; ea2 from State b to State a; ea3 from State b to State c; ea4 from State c to State a; ea7 from State c to State a; ea5 is a self-loop on State b; and ea6 is a self-loop on State c. A small text label 'T1171720-95/d13' is located to the right of State b. + +State diagram for Assisting/Handoff SSF finite state machine showing three states: State a (idle), State b (waiting for instructions), and State c (waiting for end of user interaction) with transitions ea1 through ea7. + +FIGURE 13/Q.1218 +**Assisting/Handoff SSF finite state machine** + +### 3.1.1.6.1 State a – Idle + +The SSF-FSM enters the Idle state when one of the following occurs: + +- when sending or receiving an ABORT TCAP primitive due to abnormal conditions in any state; +- given a temporary connection between an initiating SSF and the Assisting SSF, when a bearer channel disconnect is received from the initiating SSF (transition ea2). + +Once in the Idle state, if there are any outstanding responses to send to the SCF, they are discarded by the Assisting SSF. + +The Assisting SSF-FSM transits from the Idle state to the Waiting for Instructions state on receipt of an assist indication at the assisting SSF from another SSF (transition ea1). + +Any operation received from the SCF while the Assisting SSF is in Idle state should be treated as an error. The event should be reported to the maintenance functions and the transaction should be aborted according to the procedure specified in TCAP (see Recommendation Q.774). + +### 3.1.1.6.2 State b – Waiting for Instructions + +This state is entered from the Idle state on receipt of a connect at an SSF from another SSF indicating that an assist is required, based on an implementation dependent detection mechanism (transition ea1). + +Before entering this state, the SSF sends an AssistRequestInstructions operation to the SCF. In this state the Assisting SSF-FSM is waiting for an instruction from the SCF; call handling is suspended and an application timer ( $T_{\text{SSF}}$ ) should be set on entering this state. + +During this state the following events can occur: + +- The application timer $T_{\text{SSF}}$ expires – The Assisting SSF-FSM moves to the Idle state (transition ea2) and the expiration is reported to the maintenance functions and the transaction is aborted. +- An operation is received from the SCF – The SSF-FSM acts according to the operation received as described below. +- A bearer channel disconnect is received from the initiating SSF and the FSM moves to the Idle state (transition ea2). + +The following operations may be received from the SCF and processed by the Assisting SSF with no resulting transition to a different state (transition ea5): + +- ResetTimer; +- FurnishChargingInformation; +- ApplyCharging; +- SendChargingInformation. + +The following operations can be received from the SCF and processed by the Assisting SSF, causing a state transition to Waiting for End of User Interaction state (transition ea3): + +- ConnectToResource. + +In the case of Handoff SSF the ReleaseCall operation can be received from the SCF. The Handoff SSF-FSM should instruct the CCF to clear the call and ensure that any CCF resources allocated to the call have been de-allocated, then continue processing as follows: + +- if ApplyChargingReport operation is not requested, the Handoff SSF-FSM transits to the Idle state (transition ea2); +- if ApplyChargingReport operation has been requested, the Handoff SSF sends ApplyChargingReport to SCF and then the Handoff SSF-FSM transits to the Idle state (transition ea2). + +Note that the above operation is allowed only in the Handoff SSF. In the case where an implementation is not capable of differentiating between a Handoff or an assisting SSF case, it may execute the ReleaseCall operation in the assisting SSF. + +Any other operation received in this state should be processed in accordance with the general rules in 3.1.1.5. + +Note that multiple Handoff procedures are not covered by this Recommendation. + +### 3.1.1.6.3 State c – Waiting for End of User Interaction + +The Assisting SSF enters this state from the Waiting for Instructions state (transition ea3) on the reception of one of the following operations: + +- ConnectToResource. + +During this state the following events can occur: + +- A valid SCF-SRF operation [i.e. Play announcement, prompt and collect user information, and cancel (announcement)] for relaying is received and is correct, the operation is transferred to the SRF for execution. The SSF-FSM remains in the Waiting for End of User Interaction state (transition ea6). +- When the SRF indicates to the assisting SSF the end of user interaction by initiating disconnection the assisting SSF-FSM returns to the Waiting for Instructions state (only in handoff case) (transition ea4). +- The application timer $T_{SSF}$ expires – The SSF-FSM moves to the Idle state, the CCF routes the call if possible (e.g. default routing to a terminating announcement), the $T_{SSF}$ expiration is reported to the maintenance functions and the transaction is aborted. +- An operation is received from the SCF – The SSF-FSM acts according to the operation received as described below. +- A bearer channel disconnect is received from the initiating SSF – The assisting SSF-FSM moves to the Idle state, the connection to the SRF is released and the transaction is terminated (transition ea7). + +The following operation can be received from the SCF and processed by the SSF with no resulting transition to a different state (transition ea6): + +- ResetTimer. + +The DisconnectForwardConnection operation may be received from the SCF and processed by the assisting/handoff SSF in this state, causing a transition to the Waiting for Instructions state (transition ea4). This procedure is only valid if a ConnectToResource was previously processed to cause a transition into the Waiting for End of User Interaction state. + +Any other operation received in this state should be processed in accordance with the general rules in 3.1.1.5. + +### **3.1.2 SCF application entity procedures** + +#### **3.1.2.1 General** + +This subclause provides the definition of the SCF Application Entity (AE) procedures related to the SCF-SSF/SRF/SDF interfaces. The procedures are based on the use of Signalling System No. 7 (SS No.7); other signalling systems can also be used. + +In addition, other capabilities may be supported in an implementation-dependent manner in the SCP, AD or SN. + +The AE, following the architecture defined in Recommendations Q.700, Q.771 and Q.1400, includes Transaction Capabilities Application Part (TCAP) and one or more ASEs called TC-users. The following subclauses define the TC-user ASE and SACF/MACF rules, which interface with TCAP using the primitives specified in Recommendation Q.774. + +The procedure may equally be used with other message-based signalling systems supporting the Application Layer structures defined. By no means is this text intended to dictate any limitations to Service Logic Programs (SLPs). + +In case interpretations for the AE procedures defined in the following differ from detailed procedures and the rules for using the TCAP service, the statements and rules contained in 3.3 and 3.4 shall be followed. + +#### **3.1.2.2 Model and interfaces** + +The functional model of the AE-SCF is shown in Figure 14; the ASEs interface with supporting protocol layers to communicate with the SSF, SRF and SDF, and interface to the service logic programs and maintenance functions. The scope of this Recommendation is limited to the shaded area in Figure 14. + +NOTE – The SCF-FSM includes several Finite State Machines. + +The interfaces shown in Figure 14 use the TC-user ASE primitives specified in Recommendation Q.771 [interface (1)] and N-primitives specified in Recommendation Q.711 [interface (2)]. The operations and parameters of INAP are defined in clause 2. + +![Functional model of SCF-AE diagram showing nested layers of functions and objects. The outermost layer is 'Application process invocation (Service logic programs, maintenance functions)'. Inside is a box for 'Service execution environment functions' containing an oval for the same. Below that is a dashed box for 'MACF'. The next layer contains two 'SAO' boxes, each with a vertical 'SACF' box. The left 'SACF' connects to two 'ASE' boxes and a 'TCAP' box. The right 'SACF' connects to two 'ASE' boxes, a 'ROSE' box, and a 'Q.932' box. These elements are grouped under 'AEI'. To the right, 'SCF' and 'FSM' are shown. At the bottom, 'SCCP/Others' is connected via lines labeled 'a)' and 'b)'.](18b914bd6d55df64c6935e65803a3f79_img.jpg) + +Functional model of SCF-AE diagram showing nested layers of functions and objects. The outermost layer is 'Application process invocation (Service logic programs, maintenance functions)'. Inside is a box for 'Service execution environment functions' containing an oval for the same. Below that is a dashed box for 'MACF'. The next layer contains two 'SAO' boxes, each with a vertical 'SACF' box. The left 'SACF' connects to two 'ASE' boxes and a 'TCAP' box. The right 'SACF' connects to two 'ASE' boxes, a 'ROSE' box, and a 'Q.932' box. These elements are grouped under 'AEI'. To the right, 'SCF' and 'FSM' are shown. At the bottom, 'SCCP/Others' is connected via lines labeled 'a)' and 'b)'. + +T1146770-92/d14 + +AEI Application Entity Invocation + SCF Service Control Functions + FSM Finite State Machine + MACF Multiple Association Control Function + SACF Single Association Control Function + SAO Single Association Object + +a) TC-primitives or Q.932-primitives. + +b) N-primitives. + +NOTE – The SCF-FSM includes several finite state machines. + +FIGURE 14/Q.1218 +**Functional model of SCF-AE** + +### 3.1.2.3 Relationship between the SCF-FSM and the SLPs/maintenance functions + +The primitive interface between the SCF-FSM and the SLPs/maintenance functions is an internal interface and is not a subject of standardization in CS1. + +The relationship between the SLP and the SCF-FSM may be described as follows (for both cases where a call is initiated by an end user and by IN service logic): + +- If a request for IN call processing is received from the SSF, an instance of an SCF Call State Model (SCSM) is created, and the relevant SLP is invoked. +- When initiation of a call is requested from service logic, an instance of the SCSM is created. + +In either case, the SCF-FSM handles the interaction with the SSF-FSM (and the SRF-FSM and SDF-FSM) as required, and notifies the SLP of events as needed. + +The management functions related to the execution of operations received from the SCF are executed by the SCF Management Entity (SCME). The SCME is comprised of the SCME-Control and multiple instances of SCME FSMs. The SCME-Control interfaces different SCF Call State Models (SCSMs) and the Functional Entity Access Manager (FEAM). Figure 15 shows the SCF-FSM structure. + +![Diagram of SCF-FSM structure showing FEAM, SCME-Control, SCSMs, and SCME FSMs within an SCF boundary, interfacing with SSF and SRF.](c05763eff20551449de1eac378fed769_img.jpg) + +The diagram illustrates the SCF-FSM structure. A dashed rectangular box labeled 'SCF' at the bottom contains several components. At the top, a circle labeled 'FEAM' has bidirectional arrows pointing to it from 'SSF' on the left and 'SRF' on the right. Below 'FEAM' is an oval labeled 'SCME-Control', connected to 'FEAM' by a bidirectional vertical arrow. Below 'SCME-Control' are four circles: two labeled 'SCSM' (with a dashed line between them) and two labeled 'SCME FSM'. Each of these four circles has a bidirectional arrow pointing to the 'SCME-Control' oval. At the bottom right of the dashed box is the text 'T1169150-94/d15'. + +FEAM      Functional Entity Access Manager +SCME      SCF Management Entity +SCSM      SCF Call State Model + +Diagram of SCF-FSM structure showing FEAM, SCME-Control, SCSMs, and SCME FSMs within an SCF boundary, interfacing with SSF and SRF. + +FIGURE 15/Q.1218 +**SCF-FSM structure** + +The following text systematically describes the procedural aspects of the interface between the SCF and other functional entities, with the main goal of specifying the proper order of operations rather than the functional capabilities of the entities. Consequently, this text describes only a subset of the SCF functional capabilities. + +The procedural model associates an SCSM with each query from the SSF. The SCSM maintains dialogues with the SSF, SRF and SDF on behalf of service logic. + +Multiple requests may be executed concurrently and asynchronously by the SCF, which explains the need for a single entity that performs the tasks of creation, invocation and maintenance of the SCF-FSM objects. This entity is called the SCF Management Entity-Control (SCME-Control). In addition to the above tasks, the SCME maintains the dialogues with the SSF, SDF and SRF on behalf of all instances of the SCF-FSMs. In particular, the SCME-Control: + +- 1) interprets the input messages from other FEs and translates them into corresponding SCSM events; +- 2) translates the SCSM outputs into corresponding messages to other FEs; + +- 3) performs some asynchronous (with call processing) activities (one such activity is flow control). It is the responsibility of the SCME-control to detect nodal overload and send the Overload Indication (e.g. Automatic Call Gap) to the SSF to place flow control on queries. Other such activities include non-call associated treatment due to changes in Service Filtering, Call Gapping, or Resource Monitoring status and also provision of resource status messages to the SSF; +- 4) supports persistent interactions between the SCF and other FEs; and +- 5) performs asynchronous (with call processing) activities related to management and supervisory functions in the SCF and creates an instance of a SCME-FSM. For example, the SCME provides the non-call associated treatment due to changes in Service Filtering. Therefore, the SCME-Control separates the SCSM from the Service Filtering by creating instances of SCME-FSMs for each context of related operations. + +The different contexts of the SCME-FSMs may be distinguished based on the address information provided in the initiating operations. In the case of service filtering, this address information is given by Filtering Criteria, i.e. all ActivateServiceFiltering operations using the same address, address the same SCME-FSM handling this specific service filtering instance. For example, ActivateServiceFiltering operations providing different Filtering Criteria cause the invocation of new SCME-FSMs. + +Finally, the FEAM relieves the SCME of low-level interface functions. The functions of the FEAM include: + +- 1) establishing and maintaining the interfaces to the SSF, SRF and SDF; +- 2) passing (and queueing when necessary) the messages received from the SSF, SRF and SDF to the SCME; and +- 3) formatting, queueing (when necessary), and sending messages received from the SCME to the SSF, SRF and SDF. + +Note that although the SCSM includes a state and procedures concerning queue management, this type of resource management only represents one way of managing network call queues. Another alternative is to let the SSF-CCF manage call queues; however, the technical details of how the SSF-CCF performs queue management is beyond the scope of IN. As such, the RCO (see 3.1.2.4.5) and the queueing state of the SCSM (State 2.2), along with its relevant sub-states, events and procedures, are only required and applicable in the case where queue management is performed in the SCF. + +### 3.1.2.4 Partial SCF Management Entity (SCME) State Transition Diagram + +The two key parts of SCF Management Entity (SCME) State Diagram are described in Figures 16 and 17. + +![State transition diagram for the status report FSM in the SCME. It shows two states: M1. Status report idle and M2. Waiting for SSF resource status report. Transitions include (em1) Request_Status_Report_to_SSF, (Em2) Status_Report_from_SSF, (em3) Cancel_to_SSF, and (Em4) Status_Report_for_Every_Change_from_SSF.](9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg) + +``` + +stateDiagram-v2 + [*] --> M1: Status report idle + M1 --> M2: Waiting for SSF resource status report + M2 --> M1: (Em2) Status_Report_from_SSF + M2 --> M1: (em3) Cancel_to_SSF + M2 --> M2: (Em4) Status_Report_for_Every_Change_from_SSF + +``` + +The diagram illustrates the state transitions for the status report FSM in the SCME. It consists of two states: M1. Status report idle and M2. Waiting for SSF resource status report. Transitions are as follows: + + +- From M1 to M2: (em1) Request\_Status\_Report\_to\_SSF +- From M2 to M1: (Em2) Status\_Report\_from\_SSF +- From M2 to M1: (em3) Cancel\_to\_SSF +- Self-loop on M2: (Em4) Status\_Report\_for\_Every\_Change\_from\_SSF + +State transition diagram for the status report FSM in the SCME. It shows two states: M1. Status report idle and M2. Waiting for SSF resource status report. Transitions include (em1) Request\_Status\_Report\_to\_SSF, (Em2) Status\_Report\_from\_SSF, (em3) Cancel\_to\_SSF, and (Em4) Status\_Report\_for\_Every\_Change\_from\_SSF. + +FIGURE 16/Q.1218 +The status report FSM in the SCME + +![State transition diagram for the service filtering FSM in the SCME. It shows two states: M3. Service filtering idle and M4. Waiting for SSF Service filtering response. Transitions include (em5) Filtering_Request_to_SSF, (Em6) End_of_Service_Filtering_from_SSF, (em7) End_of_Service_Filtering, and (Em8) Filtering_Response_from_SSF. A self-loop on M4 is labeled (Em8) Filtering_Response_from_SSF. The diagram is labeled T1146800-92/d17.](49d7bfbc65a92a7e1bd61777326a212d_img.jpg) + +``` + +stateDiagram-v2 + [*] --> M3: M3. Service filtering idle + M3 --> M4: (em5) Filtering_Request_to_SSF + M4 --> M3: (Em6) End_of_Service_Filtering_from_SSF + M4 --> M4: (em7) End_of_Service_Filtering + M4 --> M4: (Em8) Filtering_Response_from_SSF + +``` + +State transition diagram for the service filtering FSM in the SCME. It shows two states: M3. Service filtering idle and M4. Waiting for SSF Service filtering response. Transitions include (em5) Filtering\_Request\_to\_SSF, (Em6) End\_of\_Service\_Filtering\_from\_SSF, (em7) End\_of\_Service\_Filtering, and (Em8) Filtering\_Response\_from\_SSF. A self-loop on M4 is labeled (Em8) Filtering\_Response\_from\_SSF. The diagram is labeled T1146800-92/d17. + +FIGURE 17/Q.1218 +The service filtering FSM in the SCME + +The SCME handles the following operations: + +- **RequestCurrentStatusReport;** +- **RequestEveryStatusChangeReport;** +- **RequestFirstStatusMatchReport;** +- **CancelStatusReport (including the Invoke ID previously used for request FirstStatusMatchReport or RequestEveryStateChangeReport operations);** +- **StatusReport;** +- **ActivateServiceFiltering;** +- **ServiceFilteringReport;** +- **CallGap; and** +- **ActivityTest.** + +Issuing the **CallGap** and **ActivityTest** operations does not cause state transitions in the SCME. The procedures for the rest of the above operations are described below. + +The operations that are not listed above do not affect the state of the SCME; these operations are passed to the relevant SCSM. + +#### 3.1.2.4.1 State M1 – "Status report idle" + +The following event1) is considered in this state: + +- (em1) Request\_Status\_Report\_to\_SSF – This is an internal event, caused by a decision to transmit one of the following operations: + - request current status report; + - request first status match report; + - request every status change report. + +This event causes a transition to state M2, Waiting for SSF response status report. + +#### 3.1.2.4.2 State M2 – "Waiting for SSF response status report" + +The following events are considered in this state: + +- (Em2) Status\_Report\_from\_SSF – This is an external event, caused by the reception of the response to the request current status report or request first status match report operation previously issued to the SSF. This event causes a transition out of this state to state M1, Status report idle; + +1) All events are enumerated, and the number of an event is prefixed with either the letter "E" (for external events) or "e" (for internal ones) and included in parentheses in the beginning of the event name. The scope of event names and numbers is defined by the state machine in which these events appear; the same applies to state names. + +- (em3) `Cancel_to_SSF` – This is an internal event, caused by the service logic's need to end status monitoring of the resources in the SSF, and by transmission of cancel status report operation to the SSF. This event takes place only for previously issued request first status match report or request every status change report operations. This event causes a transition to state M1, Status report idle; and +- (Em4) `Status_Report_for_Every_Change_from_SSF` – This is an external event, caused by reception of the response to the request every status change report operation previously issued to the SSF. This event does not cause a transition out of this state, so the SCSM still remains in state M2, Waiting for the SSF resource status report. + +#### 3.1.2.4.3 State M3 – "Service filtering idle" + +The following event is considered in this state: + +- (em5) `Filtering_Request_to_SSF` – This is an internal event, caused by service logic's need to filter service requests to the SSF, and by transmission of the activate service filtering operation. This event causes a transition to state M4, Waiting for SSF service filtering response. + +#### 3.1.2.4.4 State M4 – "Waiting for SSF service filtering response" + +In this state, the SCF is waiting for the service filtering response from the SSF. The following events are considered in this state: + +- (Em6) `End_of_Service_Filtering_Response_from_SSF` – This is an external event, caused by reception of the response to the request service filtering previously issued to the SSF at the end of the service filtering duration. This event causes a transition out of this state to state M3, Service filtering idle. +- (em7) `End_of_Service_Filtering` – This is an internal event, caused by the expiration of service filtering duration timer in the SCF. This event causes a transition to state M3, Service filtering idle. +- (Em8) `Filtering_Response_from_SSF` – This is an external event, caused by reception of the response to the request service filtering operation previously issued to the SSF. This event does not cause a transition out of this state, and the SCSM remains in state M4, Waiting for SSF service filtering response. + +When service filtering is active, another service filtering operation could be sent to the SSF that has the same filtering criteria; this second "filter" replaces the first one. + +#### 3.1.2.4.5 The Resource Control Object + +The Resource Control Object (RCO) is part of the SCF management entity that controls data relevant to resource information. + +The RCO consists of: + +- 1) a data structure that (by definition) resides in the SDF and can be accessed only via the RCO's methods; and +- 2) the RCO methods. + +For purposes of this Recommendation, no implementation constraints are placed on the structure. The only requirement to the structure is that, for each supported resource, it: + +- 1) stores the resource's status (e.g. busy or idle); and +- 2) maintains the queue of SCSMs that are waiting for this resource. For continuous monitoring, the RCO maintains its knowledge of the status of the resources through use of the request every status change report operation. + +The following three methods are defined for the RCO: + +- 1) Get\_Resource – This method is used to obtain the address of an idle line on behalf of an SCSM. If the resource is busy, the SCSM is queued for it; +- 2) Free\_Resource – This method is used when a disconnect notification from the SSF is received. The method either advances the queue (if it is not empty) or makes the resource free (otherwise); and +- 3) Cancel – This method is used when either the queueing timer has expired or the call has been abandoned. + +### 3.1.2.5 The SCF Call State Model (SCSM) + +Figure 18 shows the general State Diagram of the SCSM as relevant to the procedures concerning the SCF-FSM part of the SCP/AD/SN during the processing of an IN call. Each state is discussed in one of the following subclauses. Each state may have internal sub FSMs composed of the sub-states. + +![State diagram of the SCSM finite state machine showing four states: 1. Idle, 2. Preparing SSF instructions, 3. Routing to resource, and 4. User interaction. Transitions are labeled with events like (e1) SL_Invocation, (e2) Query_from_SSF, (e3) Notification_from_SSF, (e4) Processing_Completed, (e5) SR_Fac_Needed, (e6) Processing_Failure, (e7) Resource_Attached, (e8) Hand-off_Needed, (e9) Failure_from_SSF, (e10) Timer_Expired, (e11) Continue_SCF_Processing, and Exception_to_SSF. A self-loop on the Idle state is labeled (E3) Notification_from_SSF.](9874e3ac6f14360133f8e1674f79824f_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 1.Idle + 1.Idle --> 1.Idle : (E3) Notification_from_SSF + 1.Idle --> 2.Preparing SSF instructions : (e1) SL_Invocation (E2) Query_from_SSF + 2.Preparing SSF instructions --> 1.Idle : (e4) Processing_Completed + 2.Preparing SSF instructions --> 3.Routing to resource : (e5) SR_Fac_Needed + 3.Routing to resource --> 1.Idle : (e8) Hand-off_Needed + 3.Routing to resource --> 2.Preparing SSF instructions : (e9) Failure_from_SSF (e10) Timer_Expired + 3.Routing to resource --> 4.User interaction : (e7) Resource_Attached + 4.User interaction --> 2.Preparing SSF instructions : (e11) Continue_SCF_Processing + 1.Idle --> Exception_to_SSF : (e6) Processing_Failure + Exception_to_SSF --> 1.Idle + +``` + +State diagram of the SCSM finite state machine showing four states: 1. Idle, 2. Preparing SSF instructions, 3. Routing to resource, and 4. User interaction. Transitions are labeled with events like (e1) SL\_Invocation, (e2) Query\_from\_SSF, (e3) Notification\_from\_SSF, (e4) Processing\_Completed, (e5) SR\_Fac\_Needed, (e6) Processing\_Failure, (e7) Resource\_Attached, (e8) Hand-off\_Needed, (e9) Failure\_from\_SSF, (e10) Timer\_Expired, (e11) Continue\_SCF\_Processing, and Exception\_to\_SSF. A self-loop on the Idle state is labeled (E3) Notification\_from\_SSF. + +T1171730-95/d18 + +FIGURE 18/Q.1218 +The SCSM finite state machine + +General rules applicable to more than one state are as follows: + +In every state, if there is an error in a received operation, the SLP and the maintenance functions are informed. Generally, the SCSM remains in the same state; however, different error treatment is possible in specific cases as described in 3.3. Depending on the class of the operation, the error can be reported to the SSF, SRF, or SDF (see Recommendation Q.774). + +It also holds that, in every state, if the SCSM is informed that the dialogue with the SSF is terminated, then it informs the SLP and returns to the Idle state. In this case, all resources allocated to that call, including those required for relevant dialogues with the other functions, shall be de-allocated. To simplify the diagram, such transitions are not demonstrated in the figures. + +When the SLP requests call information, the SCSM transmits the **Call InformationRequest** operation to the SSF, and then **CallInformationReport** is outstanding. + +In any state (except Idle), the SCSM may receive the **CallInformationReport** operation from the SSF when the **CallInformationReport** is outstanding. Other pending requests that should be treated in the same way as the **CallInformationRequest** is the **ApplyCharging** operation. + +From any state (except Idle), if **CallInformationReport** is outstanding and the SLP indicates that the processing has been completed, the SCSM remains in the same state until it receives the **CallInformationReport** operation. + +The general rules for one or a sequence of components sent in one or more TCAP messages, which may include a single operation or multiple operations, are specified in 3.1.1.5 and are not described here. + +The SCSM has an application timer, $T_{SCF-SSF}$ , whose purpose is to reset the timer $T_{SSF}$ , which is used to prevent excessive call suspension time and to guard the association between the SSF and the SCF. + +Timer $T_{SCF-SSF}$ is set in the following cases: + +- when the SCF receives an **InitialDP**, **TAnswer**, **TDisconnect**, **TermAttemptAuthorized**, **TMidCall**, **TNoAnswer**, **AnalysedInformation**, **TBusy**, **CollectedInformation**, **OAnswer**, **OCalledPartyBusy**, **ODisconnect**, **OMidCall**, **ONoAnswer**, **OriginationAttemptAuthorized**, **RouteSelectFailure**, or **AssistRequestInstructions** operation (see 3.1.2.5.2.1 state 2.1: "**Preparing SSF Instructions**", and 3.1.2.5.2.2.1 state 2.2.1: "**Preparing SSF Instructions**"). In this case, this timer is reset when the first request, other than **ResetTimer** operation, is sent to the SSF. Subsequent to the sending of the first response, the SCF may reset $T_{SSF}$ any number of times, using the **ResetTimer** operation, and also reset $T_{SCF-SSF}$ . Prior to the sending of the first response, on the expiration of $T_{SCF-SSF}$ , the SCF may reset $T_{SSF}$ once, using the **ResetTimer** operation, and also reset $T_{SCF-SSF}$ . On second expiration of $T_{SCF-SSF}$ , the SCSM informs SLP and the maintenance functions, and the SCSM transits to the **Idle** state; +- when the SCF enters the Preparing SSF Instructions state after sending **InitiateCallAttempt** operation or **DisconnectForwardConnection** operation or after receiving a report on EDP-R from the SSF. In this case, the SCF may reset $T_{SSF}$ using the **ResetTimer** operation any number of times; +- when the SCF enters the Queueing sub-state (see 3.1.2.5.2.2, State 2.2.2: "**Queueing**"). In this case, on the expiration of timer $T_{SCF-SSF}$ , the SCF may reset $T_{SSF}$ using the **ResetTimer** operation any number of times; and +- when the SCF enters the "**Waiting for Assist Request Instructions**" state or the "**User Interaction**" state (see 3.1.2.5.3.2 and 3.1.2.5.4). In these cases, on the expiration of $T_{SCF-SSF}$ , the SCF may reset $T_{SSF}$ using the **ResetTimer** operation any number of times (OPTIONAL). + +NOTE – The word "OPTIONAL" refers to the use of the application timer $T_{SCF-SSF}$ . Whether it is used or not depends on an implementation, but, if used, it must be synchronized with $T_{SSF}$ in the SSF-FSM. + +In all four cases, $T_{SCF-SSF}$ may respectively have four different values as defined by the application. The value of $T_{SCF-SSF}$ are smaller than the respective values of $T_{SSF}$ . + +In all other cases, when receiving or sending any operation, the SCF should reset $T_{SCF-SSF}$ . In the "**Waiting for Notification or Request**" state (see 3.1.2.5.2.3), $T_{SCF-SSF}$ is not used. + +The SCSM also has an application timer, $T_{ASSIST/HANDOFF}$ , whose purpose is to prevent excessive assist/handoff suspension time. The SCSM sets the timer $T_{ASSIST/HANDOFF}$ when the SCSM sends the **EstablishTemporaryConnection** or **Select Route/Connect** operation with a correlation ID. This timer is stopped when the SCSM receives the **AssistRequestInstructions** operation from the assisting/handed-off SSF. On expiration of $T_{ASSIST/HANDOFF}$ , the SCSM informs service logic and the maintenance functions. Then, in the Assist case, the SCSM transits to the **Preparing SSF Instructions** state, and in the Handoff case, the SLPI will be released. + +The call-control-related operations relevant to the SCF-SSF interface (except the SCME related operations) are categorized into: + +- 1) call-processing-related operations; and +- 2) non-call-processing-related operations. + +Call-processing-related operations are grouped into the following two sets: + +- **CollectInformation;** + - **AnalyseInformation;** + - **SelectFacility;** + - **SelectRoute;** + - **Connect;** + - **Continue.** +- and +- **InitiateCallAttempt;** + - **ConnectToResource;** + - **DisconnectForwardConnection;** + - **ReleaseCall;** + - **EstablishTemporaryConnection.** + +For the first set of call-processing-related operations, the SCF may not send two operations of the same set in a series of TCAP messages or in a component sequence to the SSF, but send them only one at a time. Two operations of the first set shall be separated by at least one EDP-R message received by the SCSM. The same applies for any operation of the first set followed by ConnectToResource or Establish Temporary Connection. + +The non-call-processing operations include the rest of the operations at the SCF-SSF interface (but not the SCME related operations). When the service logic needs to send operations in parallel, they are sent in the component sequence. + +In what follows, each state is described in a separate subclause together with the events that cause a transition out of this state. The outputs are presented within smaller rectangles than the states are; unlike the states and events, the outputs are not enumerated. + +#### 3.1.2.5.1 State 1 – "Idle" + +The following events are considered in this state: + +- (e1) SL\_Invocation – This is an internal event caused by the need of the service logic to start a call. The SCSM issues the **InitiateCallAttempt** operation to the SSF. +- (E2) Query\_from\_SSF – This is an external event, caused by a reception of one of the following operations: + - **InitialDP;** + - **AssistRequestInstructions** (for the Service Handoff case); + - **TAnswer;** + - **TDisconnect;** + - **TermAttemptAuthorized;** + - **TMidCall;** + - **TNoAnswer;** + - **AnalysedInformation;** + - **TBusy;** + - **CollectedInformation;** + - **OAnswer;** + - **OCalledPartyBusy;** + - **ODisconnect;** + - **OMidCall;** + - **ONoAnswer;** + - **OriginationAttemptAuthorized;** and + - **RouteSelectFailure.** + +In the case of handoff, the timer $T_{\text{ASSIST/HANDOFF}}$ is stopped. + +Both events cause a transition to State 2, **PreparingSSFInstructions**. + +- (E3) **Notification\_from\_SSF** – This is an external event caused by the reception of **InitialIDP** or **TAnswer**, **TDisconnect**, **TermAttemptAuthorized**, **TMidCall**, **TNoAnswer**, **AnalysedInformation**, **TBusy**, **CollectedInformation**, **OAnswer**, **OCalledPartyBusy**, **ODisconnect**, **OMidCall**, **ONoAnswer**, **OriginationAttemptAuthorized**, **RouteSelectFailure** operation that notifies the detection of TDP\_N in the SSF. This event causes a transition back to the same state. + +### 3.1.2.5.2 State 2 – "Preparing SSF Instructions" + +In this state, the SCF determines how to further process. + +The following events are considered in this state: + +- (e4) **Processing\_Completed** – This is an internal event. In this case, the SCF has completed the processing of the instructions to the SSF. This event causes a response to be sent to the SSF and a transition to State 1, **Idle**. +- (e5) **SR\_Facilities\_Needed** – This is an (internal) event caused by the need of the service logic for additional information from the call party; hence is the necessity to set up a connection between the call party and the SRF. This event causes a transition to State 3, **Routing to Resource**. +- (e6) **Processing\_Failure** – This (internal) event causes an appropriate exception processing and a transition back to State 1, **Idle**. + +NOTE – Here and further in this Recommendation, the exception processing is not defined. It is assumed, however, that it has to include releasing all the involved resources and sending an appropriate response message to the SSF. + +To further describe the procedures relevant to this state, the state is divided into three sub-states, which are described in the following three subclauses (this subdivision is illustrated in Figure 19). + +#### 3.1.2.5.2.1 State 2.1 – "Preparing SSF Instructions" + +State 2.1, **Preparing SSF Instructions**, is where the initial decision is made on whether the SDF information or a Specialized Resource is needed, whether queueing is supported, etc. In addition, the EDP-R-related processing is also performed in this state. + +On entering this state, the SCSM starts or resets the timer $T_{SCF-SSF}$ . + +The following events are considered in this state: + +- (e2.1) **Non-Call\_Processing\_Instructions** – This is an internal event caused by the service logic when there is a need to send such an operation to the SSF. It causes one or more of the following operations to be issued to the SSF: + - **ApplyCharging**; + - **CallInformationRequest**; + - **Cancel (allRequests)**; + - **FurnishChargingInformation**; + - **RequestReportBCSMEvent**; + - **RequestNotificationChargingEvent**; + - **ResetTimer**; and + - **SendChargingInformation**. + +This event causes a transition back to State 2.1, **Preparing SSF Instructions**. + +- (e2.2) **SR\_Facilities\_Needed** – This is an internal event, caused by the service logic when there is a need to use the SRF. This event maps into the SCSM event (e5). +- (e2.3) **Call\_Processing\_Instruction\_Ready** (Monitoring not required) – This is an internal event caused by the service logic when the final call-processing-related operation is ready and there is no armed EDP and no outstanding **CallInformationReport**, **EventNotificationCharging** or **ApplyChargingReport** operation. It causes one of the following operations to be issued to the SSF: + - **AnalyseInformation**; + - **Connect**; + - **Continue**; + - **ReleaseCall**; + - **SelectFacility**; and + - **SelectRoute**. + +![State machine diagram for State 2 FSM, partial expansion. It shows states 2.1 (Preparing SSF instructions), 2.2 (Queueing FSM), and 2.3 (Waiting for notification or request). Transitions include (e2.1) Non-Call_Processing_Instructions, (e2.2) SR_Fac_Needed, (e2.3) Call_Processing_Instruction_Ready (Note 1), (e2.4) Call_Processing_Instruction_Ready (Note 1), (e2.5) Ready_for_Q_Processing, (e2.6) Processing_Failure, (e2.7) EDP-R, (e2.8) Not_Last_EDP-N (Note 2), (e2.9) Last_EDP-N (Note 2), (e2.10) Q_Processing_Finished, (e2.11) Abort_from_SSF, (e2.12) Notification_or_Request_Continuing_Instruction, (e2.13) Monitoring_Cancel_Instruction, (e2.14) Release_Call_Instruction, (e2.15) Release_Call_Instruction. External events (e1), (e2), (e9), (e10), (e11) enter state 2.1. State 2.1 leads to (e5) and (e4). State 2.2 leads to (e6) and (e4). State 2.3 leads to (e4). A 'Request to SSF' state is nested within 2.3.](f2b561f8d2d2b8402379552179d9fbef_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 2.1: (e1), (e2), (e9), (e10), (e11) + + state "2.1 Preparing SSF instructions" as 2.1 + state "2.2 Queueing FSM" as 2.2 + state "2.3 Waiting for notification or request" as 2.3 + state "Response_to_SSF" as Response_to_SSF + state "Request to SSF" as Request_to_SSF + + 2.1 --> Response_to_SSF: (e2.1) Non-Call_Processing_Instructions + Response_to_SSF --> 2.1 + 2.1 --> 2.2: (e2.5) Ready_for_Q_Processing + 2.1 --> [*]: (e2.6) Processing_Failure (e6) + 2.1 --> [*]: (e5) + 2.1 --> Response_to_SSF: (e2.2) SR_Fac_Needed + 2.1 --> Response_to_SSF: (e2.3) Call_Processing_Instruction_Ready (monitoring not required) (Note 1) + 2.1 --> Response_to_SSF: (e2.4) Call_Processing_Instruction_Ready (monitoring required) (Note 1) + + 2.2 --> 2.1: (e2.10) Q_Processing_Finished + 2.2 --> [*]: (e2.11) Abort_from_SSF + 2.2 --> [*]: (e4) + + Response_to_SSF --> 2.3 + 2.3 --> [*]: (e2.7) EDP-R + 2.3 --> [*]: (e2.8) Not_Last_EDP-N (Note 2) + 2.3 --> [*]: (e2.9) Last_EDP-N (Note 2) + 2.3 --> [*]: (e4) + + 2.3 --> Request_to_SSF + Request_to_SSF --> 2.3: (e2.12), (e2.13), (e2.14), (e2.15) + Request_to_SSF --> [*]: (e4) + +``` + +State machine diagram for State 2 FSM, partial expansion. It shows states 2.1 (Preparing SSF instructions), 2.2 (Queueing FSM), and 2.3 (Waiting for notification or request). Transitions include (e2.1) Non-Call\_Processing\_Instructions, (e2.2) SR\_Fac\_Needed, (e2.3) Call\_Processing\_Instruction\_Ready (Note 1), (e2.4) Call\_Processing\_Instruction\_Ready (Note 1), (e2.5) Ready\_for\_Q\_Processing, (e2.6) Processing\_Failure, (e2.7) EDP-R, (e2.8) Not\_Last\_EDP-N (Note 2), (e2.9) Last\_EDP-N (Note 2), (e2.10) Q\_Processing\_Finished, (e2.11) Abort\_from\_SSF, (e2.12) Notification\_or\_Request\_Continuing\_Instruction, (e2.13) Monitoring\_Cancel\_Instruction, (e2.14) Release\_Call\_Instruction, (e2.15) Release\_Call\_Instruction. External events (e1), (e2), (e9), (e10), (e11) enter state 2.1. State 2.1 leads to (e5) and (e4). State 2.2 leads to (e6) and (e4). State 2.3 leads to (e4). A 'Request to SSF' state is nested within 2.3. + +**NOTES** + +1 Including Call Information Request, Apply Charging with report request and Request Notification Charging Event. + +2 Including Call Information Report, Apply Charging Report and Event Notification Charging. + +(e2.12) Notification\_or\_Request\_Continuing\_Instruction + +(e2.13) Monitoring\_Cancel\_Instruction + +(e2.14) Release\_Call\_Instruction (Call Information Report or Apply Charging Report has been requested) + +(e2.15) Release\_Call\_Instruction (Neither Call Information Report nor Apply Charging Report has been required) + +FIGURE 19/Q.1218 +**Partial expansion of the State 2 FSM** + +In addition, one or more of the following operations may be issued to the SSF prior to the operations listed above: + +- **Cancel (allRequests);** +- **RequestReportBCSMEEvent** (to disarm all armed EDPs); +- **FurnishChargingInformation**, and +- **SendChargingInformation.** + +This event maps into the SCSM event (e4). + +- (e2.4) **Call\_Processing\_Instruction\_Ready** (Monitoring required) – This is an internal event caused by the service logic when a call-processing-related operation is ready and the monitoring of the call is required (e.g. an EDP is set, or there is an outstanding **CallInformationReport** or **ApplyChargingReport**, or there is a need to issue such a request). It causes one of the following operations to be issued to the SSF: + - **AnalyseInformation;** + - **CollectInformation;** + - **Connect;** + - **Continue;** + - **ReleaseCall;** + - **SelectFacility;** and + - **SelectRoute.** + +In addition, one or more of the following operations may be issued to the SSF prior to issuing one of the operations listed above: + +- **ApplyCharging;** +- **CallInformationRequest;** +- **FurnishChargingInformation;** +- **RequestReportBCSMEEvent;** +- **RequestNotificationChargingEvent;** and +- **SendChargingInformation.** + +This event causes a transition into State 2.3, **Waiting for Notification or Request**. + +- (e2.5) **Ready\_for\_Queueing\_Processing** – This is an internal event caused by the service logic when queuing of the call is required. This event causes a transition into State 2.2, **Queueing FSM**. +- (e2.6) **Processing\_Failure** – This is an internal event, and it maps into the SCSM event (e6) **Processing\_Failure**. + +### 3.1.2.5.2.2 State 2.2 – "Queueing FSM" + +When the SCF is processing the query from the SSF-CCF, it may find that the resource to which the call shall be routed is unavailable. One possible reason causing the resource to be unavailable is the "busy" condition. + +NOTE – The manner in which the status of the resources is maintained is described in 3.1.2.4.5. + +Such a resource may be an individual line or trunk or a customer-defined group of lines or trunks. In the latter case, the word "busy" means that all lines or trunks in the group are occupied; and the word "idle" means that at least one line or trunk in the group is idle. + +If the resource is busy, the SCF may put the call on queue and resume it later when the resource is idle. The following operations can be sent in this state: + +- **HoldCallInNetwork;** +- **ApplyCharging;** +- **CallInformationRequest;** +- **FurnishChargingInformation;** +- **RequestReportBCSMEEvent;** +- **RequestNotificationChargingEvent;** +- **ResetTimer;** and +- **SendChargingInformation.** + +The following events are considered in this state: + +- (e2.10) Queueing\_Processing\_Finished – This is an internal event caused by the SLP when it is ready to prepare the call-related operation to the SSF. This event causes a transition to State 2.1, **Preparing SSF Instructions**. +- (E2.11) Abort\_from\_SSF – This is an external event caused by the reception of the **Abort** message from the SSF (on call abandonment), and it causes a transition that maps into the SCSM event (e4). + +This state further expands into an FSM, which is depicted in Figure 20. + +![State transition diagram for the 2.2 Queueing FSM. It shows two main states: 2.2.1 Preparing SSF instructions and 2.2.2 Queueing. Transitions include internal events like Non-Call_Processing_Instructions, Busy line/trunk, Idle_Line/Trunk, Refresh_Timer_Expired, and Queueing_Timer_Expired, as well as external events like Instruction_Ready and Abort_from_SSF. Sub-functions like Response_to_SSF, Hold_Call_in_Network_to_SSF, and Reset_Timer_to_SSF are also shown.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 2.2.1 : (e2.5) + state "2.2.1 Preparing SSF instructions" as 2.2.1 + state "2.2.2 Queueing" as 2.2.2 + state "Response_to_SSF" as Response_to_SSF + state "Hold_Call_in_Network_to_SSF" as Hold_Call_in_Network_to_SSF + state "Reset_Timer_to_SSF" as Reset_Timer_to_SSF + + 2.2.1 --> Response_to_SSF : (e2.2.2) Non-Call_Processing_Instructions + Response_to_SSF --> 2.2.1 + 2.2.1 --> [*] : (e2.2.1) Instruction_Ready + 2.2.1 --> Hold_Call_in_Network_to_SSF : (e2.2.3) Busy line/trunk + Hold_Call_in_Network_to_SSF --> 2.2.2 + 2.2.2 --> [*] : (e2.2.5) Idle_Line/Trunk + 2.2.2 --> [*] : (E2.2.7) Abort_from_SSF + 2.2.2 --> Reset_Timer_to_SSF : (e2.2.4) Refresh_Timer_Expired + Reset_Timer_to_SSF --> 2.2.2 + 2.2.2 --> [*] : (e2.2.6) Queueing_Timer_Expired + subgraph 2.2 Queueing FSM + 2.2.1 + 2.2.2 + Response_to_SSF + Hold_Call_in_Network_to_SSF + Reset_Timer_to_SSF + end + note right of 2.2.2 : T1171750-95/d20 + +``` + +State transition diagram for the 2.2 Queueing FSM. It shows two main states: 2.2.1 Preparing SSF instructions and 2.2.2 Queueing. Transitions include internal events like Non-Call\_Processing\_Instructions, Busy line/trunk, Idle\_Line/Trunk, Refresh\_Timer\_Expired, and Queueing\_Timer\_Expired, as well as external events like Instruction\_Ready and Abort\_from\_SSF. Sub-functions like Response\_to\_SSF, Hold\_Call\_in\_Network\_to\_SSF, and Reset\_Timer\_to\_SSF are also shown. + +FIGURE 20/Q.1218 + +**Partial expansion of the State 2 FSM as related to queueing** + +This FSM does not explicitly describe all possible combinations of resource monitoring functions used for queueing. The following possibilities may be used in implementations: + +- **RequestFirstStatusMatchReport** by means of SCME; +- **RequestCurrentStatusChangeReport** by means of the SCME; + +- **RequestEveryStatusChangeReport** by means of the SCME; and +- monitoring based on issuing by the SCSM of the **RequestEventReportBCSM** operation and subsequent reception of the **EventReportBCSM** operation to report the availability of the resource. Both the Request and Report occur in a single different call context. In this case, operations to the SDF or equivalent SCF functionality may be used for scanning the status of resources. + +In the rest of this subclause, the state-by-state description of the FSM is followed by the description of the supporting mechanisms of the SCME. + +#### 3.1.2.5.2.2.1 State 2.2.1 – "Preparing SSF Instructions" + +In this state, the SCSM prepares the instructions for the SSF to complete the call. The following events are considered in this state: + +- (e2.2.1) **Instruction\_Ready** – This is an internal event that takes place only when the required resource is available. In this case, the SCSM has obtained the address of the free resource via the **Get\_Resource** method of the RCO (see 3.1.2.4.5). This event causes a transition to the State 2.1, **PreparingSSFInstructions** [transition (e2.10)]. +- (e2.2.2) **Non-Call\_Processing\_Instructions** – This is an internal event caused by the service logic when there is a need to send such an operation to the SSF. It causes one or more of the following operations to be issued to the SSF: + - **ApplyCharging;** + - **CallInformationRequest;** + - **FurnishChargingInformation;** + - **RequestReportBCSMEEvent;** + - **RequestNotificationChargingEvent;** + - **ResetTimer;** and + - **SendChargingInformation.** +This event causes a transition back to State 2.2.1, **Preparing SSF Instructions**. +- (e2.2.3) **Busy\_Line/Trunk** – This is an internal event caused by the RCO when no terminating line/trunk is available. This event causes the operation, with a suitable queueing timervalue, to be sent to the SSF, and a transition to State 2.2.2, **Queueing**. + +#### 3.1.2.5.2.2.2 State 2.2.2 – "Queueing" + +In this state, the SCSM is awaiting an indication from the RCO to proceed with routing a call to an idle trunk/line. The support of playing various announcements is also provided when the SCSM is in this state. In this Recommendation, the relevant further expansion of the state is not provided; it is, however, not different from that of the SCSM States 3 and 4. Nevertheless, if announcements are completed before the call is dequeued and the SSF-FSM has transitioned to state **Waiting for Instructions**, the operation should be sent to set the $T_{SSF}$ with an appropriate value. Once the SCSM enters this state, the Queueing Timer is started, and the $T_{SCF-SSF}$ is reset. The respective roles of these timers are as follows: + +- 1) The Queueing Timer limits the time that a call can spend in the queue, and its value may be customer-specific. +- 2) The $T_{SCF-SSF}$ signals when the **ResetTimer** operation shall be sent to the SSF-CCF lest the latter abandons the call. Hence, the value of this timer is set in agreement with that of the relevant timer $T_{SSF}$ within the SSF-CCF. + +The **FurnishChargingInformation** operation may also be sent to the SSF at this time to indicate the initiation of queueing for call logging purposes. + +The following events are considered in this state: + +- (e2.2.4) **Refresh\_Timer\_Expired** – This is an internal event, which results in sending the **ResetTimer** operation to the SSF-CCF and a transition back to the same state. +- (e2.2.5) **Idle\_Line/Trunk** – This is an internal event, which maps into the State 2 event (e2.10). + +- (e2.2.6) Queueing\_Timer\_Expired – This is an internal event, which results in processing the Cancel method of the RCO and causes a transition out of this state to the State 2.1, **Preparing SSF Instructions** [Transition (e2.10)] [following procedures depends on decision of the service logic that may play (or not play) the terminating announcement]. +- (E2.2.7) Abort\_from\_SSF – This is an external event caused by the reception of the Abort message from the SSF (on call abandonment), and it causes a transition that maps into the State 2 event (E2.11). The Service Control Managing Entity (SCME) takes care of updating the queueing data via the Cancel method of the RCO. + +### 3.1.2.5.2.3 State 2.3 – "Waiting for Notification or Request" + +In this state, the SCSM waits for a notification or a request from the SSF. + +On entering this state the SCSM stops the timer TSCF-SSF. + +The following events are considered in this state: + +- (E2.7) EDP-R – This is an external event, caused by a reception of the following operations: + - EventReportBCSM (for EDP\_R); + - TAnswer; + - TDisconnect; + - TermAttemptAuthorized; + - TMidCall; + - TNoAnswer; + - AnalysedInformation; + - TBusy; + - CollectedInformation; + - OAnswer; + - OCalledPartyBusy; + - ODisconnect; + - OMidCall; + - ONoAnswer; + - OriginationAttemptAuthorized; and + - RouteSelectFailure. + +This event causes a transition to State 2.1, **Preparing SSF Instructions**. + +- (E2.8) Not\_Last\_EDP-N – This is an external event, caused by a reception of one of the following operations: + - ApplyChargingReport; + - CallInformationReport; + - EventReportBCSM (for EDP\_N); + - EventNotificationCharging; + - TAnswer; + - TDisconnect; + - TermAttemptAuthorized; + - TMidCall; + - TNoAnswer; + - AnalysedInformation; + - TBusy; + - CollectedInformation; + - OAnswer; + - OCalledPartyBusy; + - ODisconnect; + - OMidCall; + - ONoAnswer; + - OriginationAttemptAuthorized; and + - RouteSelectFailure. + +In this case, there is still an outstanding armed EDP or pending **CallInformationReport** or **ApplyChargingReport** operation. This event causes a transition back to State 2.3, **Waiting for Notification or Request**. + +- (E2.9) Last\_EDP-N – This is an external event, caused by a reception of one of the following operations: + - **ApplyChargingReport**; + - **CallInformationReport**; + - **EventReportBCSM** (for EDP\_N); + - **TAnswer**; + - **TDisconnect**; + - **TermAttemptAuthorized**; + - **TMidCall**; + - **TNoAnswer**; + - **AnalysedInformation**; + - **TBusy**; + - **CollectedInformation**; + - **OAnswer**; + - **OCalledPartyBusy**; + - **ODisconnect**; + - **OMidCall**; + - **ONoAnswer**; + - **OriginationAttemptAuthorized**; and + - **RouteSelectFailure**. + +In this case, there is no outstanding armed EDP and no pending **CallInformationReport** or **ApplyChargingReport**. This event maps into the SCSM event (e4). + +- (e2.12) Notification\_or\_Request\_Continuing\_Instruction – This is an internal event caused by the service logic when there is a need to send such an operation to the SSF. It causes one of the following operations to be issued to the SSF: + - **RequestReportBCSMEEvent** (for the purpose of which: + - i) one or more EDPs will be armed; + - ii) some armed EDPs will be disarmed; or + - iii) all armed EDPs will be disarmed when there are other pending requests). + - **FurnishChargingInformation**; + - **ApplyCharging**; + - **RequestNotificationChargingEvent**; and + - **SendChargingInformation**. + +This event causes a transition to State 2.3, **Waiting for Notification or Request**. + +- (e2.13) Monitoring\_Cancel\_Instruction – This is an internal event caused by the service logic when there is a need to send this operation to the SSF. It causes the following operation to be issued to the SSF: + - **Cancel** (all Requests); and + - **RequestReportBCSMEEvent** (for the purpose of which all armed EDPs will be disarmed when there are no more other pending requests). + +This event maps into the SCSM event (e4). + +- (e2.14) Release\_Call\_Instruction (**CallInformationReport** or **ApplyChargingReport** has been requested) – This is an internal event caused by the service logic when there is a need to send such an operation to the SSF. It causes the following operation to be issued to the SSF: + - **ReleaseCall** (when there is an outstanding **CallInformationReport** or **ApplyChargingReport**). + +This event causes a transition to State 2.3, **Waiting for Notification or Request**. + +- (e2.15) Release\_Call\_Instruction (neither **CallInformationReport** nor **ApplyChargingReport** has been requested) – This is an internal event caused by the service logic when there is a need to send such an operation to the SSF. It causes the following operation to be issued to the SSF: + - **ReleaseCall** (when there is no outstanding **CallInformationReport** or **ApplyChargingReport**). + +This event maps into the SCSM event (e4). + +This concludes the description of State 2, **Preparing SSF Instructions**. + +### 3.1.2.5.3 State 3 – "Routing to Resource" + +The resource is any SRF facility (e.g. Intelligent Peripheral). + +In this state, interactions with the SSF are necessary. Accordingly, the following events cause transitions out of this state: + +- (e7) Resource\_Attached – The SRF is available. This event causes a transition to State 4, **User Interaction**; +- (e8) Handoff\_Needed – When the Handoff procedure is initiated, the SCSM terminates the interaction with the initiating SSF. This event causes a transition to the State 1, **Idle**. When the **AssistRequestInstructions** operation from the Handed-off SSF is received by the SCME-Control, the SCME-Control creates the new SCSM. The SCF shall maintain sufficient information in order to correlate the subsequent **AssistRequestInstructions** operation (from the Handoff SSF) to the existing Service Logic Program Instance (SLPI); +- (e9) Failure\_from\_SSF – The inability of the SSF to connect to requested resources causes a transition to State 2, **Preparing SSF Instructions**; and +- (e10) Timer\_Expired – This event takes place when $T_{\text{ASSIST/HANDOFF}}$ expires. This event causes a transition to State 2, **Preparing SSF Instructions**. + +To further describe the procedures relevant to this state, the state is divided into three sub-states, which are described in the following two subclauses (this subdivision is illustrated in Figure 21). + +#### 3.1.2.5.3.1 State 3.1 – "Determine Mode" + +In this state, the SCSM determines the User Interaction mode to connect the call to SRF. The following events are considered in this state: + +- (e3.1) Instruction\_Ready – This is an internal event that takes place only in the Initiating SSF relay case. In this case, the SCSM sends the **ConnectToResource** operation accompanied by **PlayAnnouncement** or **PromptAndCollectUserInfoInformation** operation to the Initiating SSF, and transits out to the State 4, **User Interaction**. This transition maps into the event (e7); +- (e3.2) Assist\_Needed – This event is an internal event that takes place when the Assisting SSF is needed or Direct SCF-SRF relation is needed. In this case, the SCSM sends the **EstablishTemporaryConnection** operation to the Initiating SSF with the Assisting SSF address or SRF address, and transits to the State 3.2, **WaitingForAssistRequestInstructions**; and +- (e3.3) Handoff\_Needed – This is an internal event that takes place only in the Handoff case. In this case, the SCSM sends the **Connect** or **SelectRoute** operation with the Handed-off SSF address to the Initiating SSF, sets the $T_{\text{ASSIST/HANDOFF}}$ timer, and transits to the State 1, **Idle**. This transition maps into the event (e8). The SCF shall maintain sufficient information in order to correlate the subsequent **AssistRequestInstructions** operation (from the handoff SSF) to the existing SLPI. + +#### 3.1.2.5.3.2 State 3.2 – "Waiting for Assist Request Instructions" + +In this state, the SCSM waits for the **AssistRequestInstructions** operation from the Assisting SSF (SSF relay case) or from the SRF (Direct SCF-SRF case). On entering this state the SCSM starts the Timer $T_{\text{ASSIST/HANDOFF}}$ , and resets the timer $T_{\text{SCF-SSF}}$ (if it is used). The following events are considered in this state: + +- (E3.4) Assist\_Request\_Instructions\_from\_SSF (Assisting SSF relay case) – This is an external event caused by the receipt of **AssistRequestInstructions** from the Assisting SSF. In this case, the SCSM transmits the **ConnectToResource** operation accompanied by **PlayAnnouncement** or **PromptAndCollectUserInfoInformation** operation to the Assisting SSF, and transits out to the State 4, **User Interaction**. This transition maps into the event (e7); +- (E3.5) Assist\_Request\_Instructions\_from\_SRF (Direct SCF-SRF case) – This is an external event caused by the receipt of **AssistRequestInstructions** from the SRF. In this case, the SCSM transmits the **PlayAnnouncement** or **PromptAndCollectUserInfoInformation** operation to the SRF, and transits out to the State 4, **User Interaction**. This transition maps into the event (e7); + +- (e3.6) Refresh\_Timer\_Expired (OPTIONAL: see the Note in 3.1.2.5) – This is an internal event that takes place on the expiration of $T_{SCF-SSF}$ . In this case, the SCSM transmits the **ResetTimer** operation to the Initiating SSE, and transits back to the same state; +- (e3.7) Assist\_Timer\_Expired – This is an internal event that takes place on the expiration of $T_{ASSIST/HANDOFF}$ . In this case, the SCSM informs the SCME and SLP, and transits to State 2, **Preparing SSF Instructions**, after sending the **DisconnectForwardConnection** operation to the SSF. This event maps into the event (e10); and +- (E3.8) Initial\_SSF\_Failure – This is an external event caused by the reception of SSF failure. This event causes a transition that maps into the SCSM event (E9). + +![State 3 FSM diagram showing transitions between '3.1 Determine mode' and '3.2 Waiting for assist request instructions' states, leading to '3. Routing to resource'.](cb9e3603e260c7b07aca73128586df80_img.jpg) + +``` + +stateDiagram-v2 + direction TB + [*] --> 3.1_Determine_mode : (e5) + + state 3.1_Determine_mode { + direction LR + state "3.1 Determine mode" as DM + } + + 3.1_Determine_mode --> Establish_Temporary_Connection : (e3.2) Assist_Needed + Establish_Temporary_Connection --> 3.2_Waiting_for_assist_request_instructions + + 3.1_Determine_mode --> Connect_Select_Route_to_SSF : (e3.3) Hand-off_Needed + Connect_Select_Route_to_SSF --> (e8) + + 3.1_Determine_mode --> Connect_to_Resource_ind_to_SSF_1 : (e3.1) Instruction_Ready (SSF relay case) + Connect_to_Resource_ind_to_SSF_1 --> Request_to_SRF_1 + Request_to_SRF_1 --> (E9) + + state 3.2_Waiting_for_assist_request_instructions { + direction TB + state "3.2 Waiting for assist request instructions" as WARI + } + + 3.2_Waiting_for_assist_request_instructions --> Send_Reset_Timer_to_initiating_SSP : (e3.6) Refresh_Timer_Expired + Send_Reset_Timer_to_initiating_SSP --> 3.2_Waiting_for_assist_request_instructions + + 3.2_Waiting_for_assist_request_instructions --> Disconnect_Forward_Conn_ind_to_SSF : (e3.7) Assist_Timer_Expired + Disconnect_Forward_Conn_ind_to_SSF --> (e10) + + 3.2_Waiting_for_assist_request_instructions --> (E9) : (E3.8) Initial_SSF_Failure + + 3.2_Waiting_for_assist_request_instructions --> Request_to_SRF_2 : (E3.5) Assist_Request_Instructions_from_SRF (Direct SCF-SRF case) + + 3.2_Waiting_for_assist_request_instructions --> Connect_to_Resource_ind_to_SSF_2 : (E3.4) Assist_Request_Instructions_from_SSF (Assisting SSF relay case) + Connect_to_Resource_ind_to_SSF_2 --> Request_to_SRF_3 + + Request_to_SRF_2 --> 3_Routing_to_resource + Request_to_SRF_3 --> 3_Routing_to_resource + + state 3_Routing_to_resource { + state "3. Routing to resource" as RR + } + + 3_Routing_to_resource --> (e7) + +``` + +The diagram illustrates the State 3 FSM (Finite State Machine). It begins with entry event (e5) into state '3.1 Determine mode'. From here, three paths exist: (e3.3) 'Hand-off\_Needed' leads to 'Connect/Select\_Route\_to\_SSF' and exits via (e8); (e3.1) 'Instruction\_Ready (SSF relay case)' leads through 'Connect\_to\_Resource\_ind\_to\_SSF' and 'Request\_to\_SRF' to exit (E9); and (e3.2) 'Assist\_Needed' leads through 'Establish\_Temporary\_Connection' to state '3.2 Waiting for assist request instructions'. From state 3.2, several transitions are possible: (e3.6) 'Refresh\_Timer\_Expired' triggers 'Send Reset\_Timer to initiating SSP' and returns to state 3.2; (e3.7) 'Assist\_Timer\_Expired' leads to 'Disconnect\_Forward\_Conn.\_ind\_to\_SSF' and exits via (e10); (E3.8) 'Initial\_SSF\_Failure' exits via (E9); (E3.5) 'Assist\_Request\_Instructions\_from\_SRF (Direct SCF-SRF case)' leads to 'Request\_to\_SRF' and then to state '3. Routing to resource'; and (E3.4) 'Assist\_Request\_Instructions\_from\_SSF (Assisting SSF relay case)' leads through 'Connect\_to\_Resource\_ind\_to\_SSF' and 'Request\_to\_SRF' to state '3. Routing to resource'. State '3. Routing to resource' exits via (e7). + +State 3 FSM diagram showing transitions between '3.1 Determine mode' and '3.2 Waiting for assist request instructions' states, leading to '3. Routing to resource'. + +T1169180-94/d21 + +FIGURE 21/Q.1218 +The State 3 FSM + +### 3.1.2.5.4 State 4 – "User Interaction" + +In this state, the SCF requests the SRF to provide user interaction (e.g. collect additional information and/or play announcements). When an interaction is finished the SCF can instruct the SSF to disconnect the bearer between SSF and SRF. Alternatively, it can send a user interaction operation to the SRF containing an indication that allows the SRF initiated disconnect. + +On entering this state the SCSM resets the timer $T_{SCF-SSF}$ (if it is used). + +One event causes a transition out of this state: + +- (e11) Continue\_SCF\_Processing – In this case, the SCF has obtained all the information from the SRF, that is needed to instruct the SSF to complete the call. This event causes a transition to State 2, **Preparing SSF Instructions**. + +To consider the processing of this state in more detail, it is expanded into a separate FSM depicted in Figure 22A. + +![State 4 FSM diagram showing transitions between '4.1 Waiting for response from the SRF' and various actions like 'Req_to_SRF', 'Instr_to_SRF', 'Response_from_SRF', and 'Disconnect_Forward_Connection'.](5efe6377e22b9ab76a19a70da29976b9_img.jpg) + +``` + +graph TD + Entry((e7)) --> State41[4.1 Waiting for response from the SRF] + + State41 -- (e4.1) More_Info_Needed --> ReqSRF[Req._to_SRF] + ReqSRF --> State41 + + State41 -- (e4.3) Continue_SCF_Processing --> InstrSRF1["Instr._to_SRF (with permission of SRF initiated disc., Specialized. ResourceReport not requested)"] + InstrSRF1 --> UserInt((4. User interaction)) + UserInt -- "(for non-Assisting SSF case)" --> e11a((e11 SRF initiated disconnect)) + + State41 -- (e4.3) Continue_SCF_Processing --> InstrSRF2["Instr._to_SRF (with permission of SRF initiated disc., Specialized. ResourceReport requested)"] + InstrSRF2 --> UserInt + + State41 -- (E4.2) Final_Response_from_SRF --> RespSRF["Response_from_SRF (when permission for SRF initiated disc. was given)"] + RespSRF -- "(for non-Assisting SSF case)" --> e11b((e11 SRF initiated disconnect)) + + State41 -- (e4.3) Continue_SCF_Processing --> DiscFC[Disconnect_Forward_Connection] + DiscFC --> e11c((e11 SCF initiated disconnect)) + + State41 -- (e4.7) Cancellation_Required --> CancelSRF[Cancel_to_SRF] + CancelSRF --> State41 + + State41 -- (e4.6) Refresh_Timer_Expired --> ResetTimer[Reset_Timer_to_Initiating/Assisting_SSF] + ResetTimer --> State41 + + State41 -- (e4.8) Non_Call_Processing_Instructions --> ReqSSF[Req._to_SSF] + ReqSSF --> State41 + + State41 -- "(E4.5) Failure_from_SRF / (E4.2) Response_from_SRF" --> State41 + +``` + +The diagram illustrates the State 4 FSM, enclosed in a dashed box. The central state is **4.1 Waiting for response from the SRF**. Transitions are triggered by various events (e4.x and E4.x) leading to actions like requesting more info, sending instructions, or disconnecting. Final exit points are labeled (e11), representing either SRF-initiated or SCF-initiated disconnects. Diagram code: T1171760-95/d22 + +State 4 FSM diagram showing transitions between '4.1 Waiting for response from the SRF' and various actions like 'Req\_to\_SRF', 'Instr\_to\_SRF', 'Response\_from\_SRF', and 'Disconnect\_Forward\_Connection'. + +FIGURE 22A/Q.1218 +The State 4 FSM + +#### 3.1.2.5.4.1 State 4.1 – "Waiting for Response from the SRF" + +In this state, the SCF waits for the response to the previously sent operation and evaluates this response. The following events are considered in this state: + +- (e4.1) More\_Information\_Needed results in issuing yet another operation to the SRF; it causes a transition back to State 4.1; +- (E4.2) Response\_from\_SRF – This is an external event caused by the reception of **SpecializedResourceReport** or Return Result from **PromptAndCollectUserInformation** operation. On the receipt of this operation, the SCSM transits back to the same state; +- (E4.2') Final\_Response\_from\_SRF – This is an external event caused by the reception of **SpecializedResourceReport** operation, as requested by the SCF, in response to the previous **PlayAnnouncement** or Return Result from **PromptAndCollectUserInformation** operation with permission of SRF-initiated disconnect. In the Initiating SSF relay case and the Direct SCF-SRF case, on the receipt of this event, the SCSM transits to the State 2, Preparing SSF Instructions. This event maps into the event (*e11*); +- (e4.3) Continue\_SCF\_Processing – This is an internal event that takes place when the SCSM finishes the User Interaction and requests the disconnection of bearer connection between the Initiating SSF and SRF by means of SCF initiated disconnect. In this case, the SCSM sends the **DisconnectForwardConnection** operation to the Initiating SSF and transits to the State 2, Preparing SSF Instructions. This event maps into the event (*e11*); +- (e4.3') Continue\_SCF\_Processing – This is an internal event that takes place when the SCSM finishes the User Interaction and requests the disconnection of bearer connection between the Initiating SSF and SRF by means of SRF-initiated disconnect, while an **SpecializedResourceReport** operation is requested to be returned to the SCF in case an announcement is completed. In this case, the SCSM sends the **PlayAnnouncement** (containing a request for returning a **SpecializedResourceReport** operation as an indication of completion of the operation) or **PromptAndCollectUserInformation** operation with permission of SRF-initiated disconnect to the SRF. In the case of Assisting SSF, the SRF-initiated disconnect cannot be used. In this case, the SCSM transits back to the same state; +- (e4.3'') Continue\_SCF\_Processing – This is an internal event that takes place when the SCSM finishes the User Interaction and requests the disconnection of bearer connection between the Initiating SSF and SRF by means of SRF-initiated disconnect, while no **SpecializedResourceReport** operation is requested to be returned to the SCF in case the announcement is completed. In this case, the SCSM sends the **PlayAnnouncement** operation (not containing a request for returning a **SpecializedResourceReport** operation as an indication of completion of the operation) with permission of SRF-initiated disconnect to the SRF. In the case of Assisting SSF, the SRF-initiated disconnect cannot be used. In this case, the SCSM transits to the State 2, Preparing SSF Instructions. This event maps into the event (*e11*); +- (E4.5) Failure\_from\_SRF – This is an external event caused by the reception of return error for **PlayAnnouncement** or **PromptAndCollectUserInformation** operation. In this case, the SCSM does not change its state. +- (e4.6) Refresh\_Timer\_Expired (OPTIONAL: see 3.1.2.5) – This is an internal event that takes place on the expiration of $T_{SCF-SSF}$ . In this case, the SCSM transmits the **ResetTimer** operation to the Initiating/Assisting SSF, and transits back to the same state; and +- (e4.7) Cancellation\_Required – This is an internal event that takes place when the SCSM cancels the previous **PlayAnnouncement** or **PromptAndCollectUserInformation** operation. In this case, the SCSM sends the **Cancel** operation to the Assisting SSF (SSF relay case) or the SRF (Direct SCF-SRF case), and transits back to the same state. + +It should be noted that the bearer connection between the SSF and the SRF is disconnected when the SCSM exits from this state. + +- (e4.8) **Non\_Call\_Processing\_Instructions** – This is an internal event caused by the service logic when there is a need to send this operation to the SSF. It causes one or more of the following operations to be issued to the SSF: + - **ApplyCharging;** + - **FurnishChargingInformation;** + - **RequestNotificationChargingEvent;** and + - **SendChargingInformation.** + +In this case, the SCSM remains in the same state. + +### 3.1.2.5.5 SDF-related states + +The interaction with the SDF is possible from any state of the SCF. In the following subclauses, the SDF-related states are specified. The model describes the relationship of one SCF with one SDF. If an SCF needs to access another SDF a new FSM should be instantiated. + +In what follows, the states and events are enumerated independent of the rest of the SCSM; the discussion is accompanied by Figure 22B. + +![State transition diagram for SDF-related states. The diagram shows four states: 1. Idle, 2. Wait for subsequent requests, 3. Wait for Bind result, and 4. SDF bound. Transitions are triggered by events (e1) through (e8). State 1 (Idle) transitions to State 2 (Wait for subsequent requests) on (e1) Bind request. State 2 has a self-loop for (e2) Request to SDF and (e3) Request to SDF with Bind, and transitions to State 3 (Wait for Bind result) on (e3). State 3 transitions to State 1 (Idle) on (E4) Bind error and to State 4 (SDF bound) on (E5) Response from SDF with Bind. State 4 has a self-loop for (e6) Request to SDF and (E7) Response from SDF, and transitions to State 1 (Idle) on (e8) Unbind request.](c2e2b17d61aecbead88a6278e4ba3605_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 1.Idle + 1.Idle --> 2.Wait for subsequent requests : (e1) Bind request + 2.Wait for subsequent requests --> 2.Wait for subsequent requests : (e2) Request to SDF + 2.Wait for subsequent requests --> 2.Wait for subsequent requests : (e3) Request to SDF with Bind + 2.Wait for subsequent requests --> 3.Wait for Bind result : (e3) Request to SDF with Bind + 3.Wait for Bind result --> 1.Idle : (E4) Bind error + 3.Wait for Bind result --> 4.SDF bound : (E5) Response from SDF with Bind + 4.SDF bound --> 4.SDF bound : (e6) Request to SDF + 4.SDF bound --> 4.SDF bound : (E7) Response from SDF + 4.SDF bound --> 1.Idle : (e8) Unbind request + +``` + +T1 169200-94/d23 + +State transition diagram for SDF-related states. The diagram shows four states: 1. Idle, 2. Wait for subsequent requests, 3. Wait for Bind result, and 4. SDF bound. Transitions are triggered by events (e1) through (e8). State 1 (Idle) transitions to State 2 (Wait for subsequent requests) on (e1) Bind request. State 2 has a self-loop for (e2) Request to SDF and (e3) Request to SDF with Bind, and transitions to State 3 (Wait for Bind result) on (e3). State 3 transitions to State 1 (Idle) on (E4) Bind error and to State 4 (SDF bound) on (E5) Response from SDF with Bind. State 4 has a self-loop for (e6) Request to SDF and (E7) Response from SDF, and transitions to State 1 (Idle) on (e8) Unbind request. + +FIGURE 22B/Q.1218 +The SDF-related states + +#### 3.1.2.5.5.1 State 1 – "Idle" + +This state is a sub-state of any state before a request to the SDF is issued. The following event is considered in this state: + +- (e1) **Bind\_Request** – This is an internal event, caused by the need of the service logic to create an association with an SDF in order to begin accessing data. This event causes a transition to the State 2, **Wait for Subsequent Requests**. + +#### 3.1.2.5.5.2 State 2 – "Wait for Subsequent Requests" + +In this state, subsequent operations to be sent with the **Bind** operation (in the same message) to the SDF are expected. The following two events are considered in this state: + +- (e2) **Request\_to\_SDF** – This is an internal event, caused by the reception of an operation. The operation is buffered until the reception of a delimiter (or a timer expiration). The SCSM remains in the same state; and +- (e3) **Request\_to\_SDF\_with\_Bind** – This is an internal event caused by the reception of a delimiter, that indicates the reception of the last operation to be sent. Once the delimiter is received, a message containing the argument of the **Bind** operation and other operations' arguments, if any, is sent to the SDF. This event causes a transition out of this state to the State 3, **Wait for Bind Result**. + +#### 3.1.2.5.5.3 State 3 – "Wait for Bind Result" + +In this state, the SCF is waiting for the response from the SDF. Two events are considered in this state: + +- (E4) **Bind Error** – This is an external event, caused by the reception of an error to the **Bind** operation previously issued to the SDF. This event causes a transition out of this state to State 1, **Idle**. +- (E5) **Response\_from\_SDF\_with\_Bind** – This is an external event, caused by the reception of a **Bind** result combined with the responses to other operations previously issued to the SDF (if any). This event causes a transition to State 4, **SDF Bound**. + +#### 3.1.2.5.5.4 State 4 – "SDF Bound" + +In this state, the SCF has established an authenticated access to the SDF, and is waiting for requests to the SDF from the service logic or is waiting for responses to the operations previously issued to the SDF. Three events are considered in this state: + +- (e6) **Request\_to\_SDF** – This is an internal event, caused by the need of the service logic to access data in the SDF. The SCSM remains in the same state; +- (E7) **Response\_from\_SDF** – This is an external event, caused by the reception of responses to the operations previously issued to the SDF. The SCSM remains in the same state; and +- (e8) **Unbind\_request** – This is an internal event, caused by the need of the service logic to terminate the authenticated access to the SDF. This event causes a transition state to State 1, **Idle**. + +In addition to the above model, an SDL description of SCSM is shown in Annex B. + +### 3.1.3 SRF application entity procedures + +#### 3.1.3.1 General + +This subclause provides the definition of the SRF Application Entity (AE) procedures related to the SRF-SCF interface. The procedures are based on the use of Signalling System No. 7 (SS No. 7); other signalling systems can be used. + +Other capabilities may be supported in an implementation-dependent manner in the IP, SSP or SN. + +The AE, following the architecture defined in Recommendations Q.700, Q.771 and Q.1400, includes Transaction Capabilities Application Part (TCAP) and one or more ASEs called TC-users. The following subclauses define the TC-user ASE and SACF and MACF rules, which interface with TCAP using the primitives specified in Recommendation Q.771. + +The procedure may equally be used with other message-based signalling systems supporting the application layer structures defined. + +In case interpretations for the application entity procedures defined in the following differ from detailed procedures and the rules for using TCAP services, the statements and rules contained in the detailed subclauses 3.3 and 3.4 shall be followed. + +### 3.1.3.2 Model and interfaces + +The functional model of the AE-SRF is shown in Figure 23; the ASEs interface to TCAP (to communicate with the SCF) as well as interface to the maintenance functions. The scope of this Recommendation is limited to the shaded area in Figure 23. + +The interfaces shown in Figure 23 use the TC-user ASE primitives specified in Recommendation Q.771 [interface (1)] and N-Primitives specified in Recommendation Q.711 [interface (2)]. The operations and parameters of intelligent network application protocol (INAP) are defined in clause 2. + +![Functional model of SRF-AE diagram showing nested functional blocks and interfaces.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +The diagram illustrates the functional model of the SRF-AE. At the top is a box labeled 'Application process invocation (Maintenance functions)'. Inside this box is a large shaded rectangle containing several components: + + +- An oval at the top labeled 'Specialized resource function'. +- A dashed box below it labeled 'MACF'. +- Below the MACF box, there are two vertical 'SAO' (Single Association Object) blocks, one on the left and one on the right. +- To the left of the left SAO is a vertical 'SACF' (Single Association Control Function) block. +- To the right of the right SAO is a 'Bearer signalling handling' block. +- Between the SACF and the left SAO are two 'ASE' (Application Service Element) blocks and a 'TCAP' block. The TCAP block is connected to the left SAO via an interface labeled 'a)'. The ASE blocks are connected to both the SACF and the left SAO. +- The right SAO is connected to the 'Bearer signalling handling' block via an interface labeled 'b)'. +- On the far right of the shaded area is a vertical 'SRF FSM' (Finite State Machine) block. +- At the bottom right of the shaded area is an 'AEI' (Application Entity Invocation) label. + + Below the shaded area, two lines labeled 'b)' extend down to a box labeled 'SCCP/DSS 1 (Layer 3)/Others'. + +Functional model of SRF-AE diagram showing nested functional blocks and interfaces. + +T1146860-92/d24 + +AEI Application Entity Invocation + SRF Specialized Resource Functions + FSM Finite State Machine + MACF Multiple Association Control Function + SACF Single Association Control Function + SAO Single Association Object + +- a) TC-primitives or Q.932-primitives. +- b) N-primitives. + +NOTE – The SRF-FSM includes several finite state machines. + +FIGURE 23/Q.1218 +**Functional model of SRF-AE** + +### 3.1.3.3 Relationship between the SRF-FSM and maintenance functions/bearer connection handling + +The primitive interface between the SRF-FSM and the maintenance functions is an internal interface and is not subject for standardization in IN CS-1. + +The relationship between the bearer connection handling and the SRF-FSM may be described as follows for the case of a call initiated by the SSF: when a call attempt is initiated by the SSF, an instance of an SRF-FSM is created. + +The SRF-FSM handles the interaction with the SCF-FSM and the SSF-FSM. + +The management functions related to the execution of operations received from the SCF are executed by the SRF Management Entity (SRME). The SRME interfaces the different SRF Call State Models (SRSM) and the Functional Entity Access Manager (FEAM). Figure 24 shows the SRF-FSM structure. + +![Diagram of SRF-FSM structure showing FEAM, SRME, and multiple SRSM components within a dashed boundary labeled SRF-FSM.](1684f5f8c34bd0ef6e933664d88b9d86_img.jpg) + +The diagram illustrates the SRF-FSM structure. A dashed rectangular box labeled 'SRF-FSM' contains three main components: FEAM (Functional Entity Access Manager) at the top, SRME (SRF Management Entity) in the center, and multiple SRSM (SRF Call State Model) components at the bottom. FEAM is connected to SSF (Service Switching Function) on the left and SCF (Service Control Function) on the right. FEAM is also connected to SRME. SRME is connected to each of the SRSM components. The SRSM components are arranged horizontally, with three shown and an ellipsis between the second and third. The diagram is labeled 'T1146870-92/d25' at the bottom right. + +Diagram of SRF-FSM structure showing FEAM, SRME, and multiple SRSM components within a dashed boundary labeled SRF-FSM. + +FEAM Functional Entity Access Manager +SRME SRF Management Entity +SRSM SRF Call State Model + +FIGURE 24/Q.1218 +**SRF-FSM structure** + +The model associates a Finite State Machine (FSM) with each initial interaction request from the SCF. Thus, multiple initial requests may be executed concurrently and asynchronously by the SRF, which explains the need for a single entity that performs the tasks of creation, invocation, and maintenance of the SRSM objects. This entity is called the SRF management entity (SRME). In addition to the above tasks, the SRME maintains the dialogues with the SCF and SSF on behalf of all instances of the SCSM. In particular, the SRME: + +- 1) interprets the input messages from other FEs and translates them into corresponding SRSM events; and +- 2) translates the SRSM outputs into corresponding messages to other FEs. + +NOTE – Such a request from the SCF is executed by the SCSM when it is in its State 4. + +Finally, the Functional Entity Access Manager (FEAM) relieves the SRME of low-level interface functions. The FEAM functions include: + +- 1) establishing and maintaining the interfaces to the SSF and SCF; +- 2) passing (and queueing when necessary) the messages received from the SSF and SCF to the SRME; and +- 3) formatting, queueing (when necessary), and sending messages received from the SRME to the SSF and SCF. + +### 3.1.3.4 The SRSM + +The SRSM is presented in Figure 25. In what follows, each state is described in a separate subclause together with the events that cause a transition out of this state. Finally, the outputs are presented within smaller rectangles than the states are; unlike the states and events, the outputs are not enumerated. + +![State transition diagram for the SRSM (State Transition Diagram for the SRSM). The diagram shows three states: 1. Idle, 2. Connected, and 3. User interaction. Transitions are triggered by events (E1-E12) and result in outputs (Assist_Request_Instructions, Disconnect_Bearer_Connection).](ecae674475cecdd0962200a5d1e2591e_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 1.Idle + 1.Idle --> 2.Connected : (E1) Connect_Request_from_SSF + 2.Connected --> 1.Idle : (e4) SRF_Sanity_Timeout, (E3) Connection_Released_from_SSF + 2.Connected --> 2.Connected : Assist_Request_Instructions + 2.Connected --> 3.User_interaction : (E2) PlayAnnouncement/PromptAndCollectUserInformation_from_SCF + 3.User_interaction --> 1.Idle : (E10) Connection_Released_from_SSF + 3.User_interaction --> 1.Idle : Disconnect_Bearer_Connection + 3.User_interaction --> 2.Connected : (e11) Disconnect_to_SSF (SRF initiated disconnect case), (e12) SRF_Sanity_Timeout + 3.User_interaction --> 3.User_interaction : T1146880-92/d26 + +``` + +Legend: + +- (E5) PlayAnnouncement/PromptAndCollectUserInformation\_from\_SCF +- (E6) Cancel\_from\_SCF +- (e7) SRF\_Report\_to\_SCF +- (e8) PlayAnnouncement/PromptAndCollectUserInformation\_Cancelled\_to\_SCF +- (e9) Cancel\_Error\_to\_SCF + +State transition diagram for the SRSM (State Transition Diagram for the SRSM). The diagram shows three states: 1. Idle, 2. Connected, and 3. User interaction. Transitions are triggered by events (E1-E12) and result in outputs (Assist\_Request\_Instructions, Disconnect\_Bearer\_Connection). + +FIGURE 25/Q.1218 + +### The SRSM + +Each state is discussed in the following subclauses. General rules applicable to more than one state are addressed here. + +One component or a sequence of components received in one or more TCAP messages may include a single operation or multiple operations, and it is processed as follows: + +- The SRSM processes the operations in the order in which they are received. + +- The SRSM examines subsequent operations in the sequence. When a Cancel (for PlayAnnouncement or PromptAndCollectUserInfo) operation is encountered in the sequence in state user interaction, it executes it immediately. In all other cases, the SRSM queues the operations and awaits an event (such an event would be the completion of the operation being executed, or reception of an external event). +- If there is an error in processing one of the operations in the sequence, the SRF-FSM processes the error (see below) and discards all remaining operations in the sequence. +- If an operation is not understood or is out of context (i.e. it violates the SACF rules defined by the SRSM) as described above, the SRF-FSM processes the error according to the rules given in 3.4.2 (using TC U-REJECT or the operation error UnexpectedComponentSequence). + +In any state, if there is an error in a received operation, the maintenance functions are informed. Generally, the SRSM remains in the same state in which it received the erroneous operations, however different error treatment is possible in specific cases as described in 3.2; depending on the class of the operation, the error could be reported by the SRF to the SCF using the appropriate component (see Recommendation Q.774). + +In any state, if the dialogue with the SCF (direct SCF-SRF case) is terminated, then the SRSM returns to idle state after ensuring that all resources allocated to the dialogues have been de-allocated. The SRF shall remain connected to the SSF as long as it has PlayAnnouncement operations active or buffered. The resources allocated to the call will be de-allocated when all announcements are completed or when the SSF disconnects the bearer connection (i.e. call party release). + +In any state (except idle), if the SSF disconnects the bearer connection to the SRF before the SRF completes the user interaction, then the SRSM clears the call and ensures that all SRF resources allocated to the call have been de-allocated. Then it transits to the idle state. + +The SRSM has an application timer, $T_{\text{SRF}}$ , whose purpose is to prevent excessive call suspension time. This timer is set when the SRF sends Setup Response bearer message to the SSF (SSF relay case) or the AssistRequestInstructions operation (Direct SCF-SRF case). This timer is stopped when a request is received from the SCF. The SRF may reset $T_{\text{SRF}}$ on transmission of the SpecializedResourceReport operation or the return result for the PromptAndCollectUserInfo operation when there is no queued user interaction operation. On the expiration of $T_{\text{SRF}}$ , the SRSM transits to the idle state ensuring that all SRF resources allocated to the call have been de-allocated. + +#### 3.1.3.4.1 State 1 – “Idle” + +The idle state represents the condition prior to, or at the completion of, an instance of user interaction. This state is entered as a result of events E3, e4, E10, e11 and e12. It is exited as a result of event E1. + +- (E1) Connect\_Request\_from\_SSF – This event corresponds to a bearer signalling connection request message from the SSF. The details of the bearer signalling state machine related to establishing the connection are not of interest to the FSM. The SRSM goes to state “Connected”; +- (E3) Connection\_Released\_from\_SSF – This event takes place when the SRSM receives a release message from the SSF in connected state. The SRSM goes to state “Idle”; +- (e4) SRF\_Sanity\_Timeout – This event occurs when the SRSM has been in connected state for a network-operator-defined period of time (timer $T_{\text{SRF}}$ ) without having a PlayAnnouncement/PromptAndCollectUserInfo operation to execute. The SRF initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. The SRSM goes to state “Idle”; +- (E10) Connection\_Released\_from\_SSF – This event takes place when the SRSM receives a release message from the SSF in user interaction state. The SRSM goes to state “Idle”; + +- (e11) `Disconnect_to_SSF` – This event occurs when the SCF has enabled SRF initiated disconnect by the last `PlayAnnouncement/PromptAndCollectUserInfoInformation` from SCF (E2) or (E5) with the parameter `disconnectFromIPForbidden`. The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system after sending the last `SpecializedResourceReport` operation to the SCF (e7). The SRSM goes to state “Idle”; and +- (e12) `SRF_Sanity_Timeout` – This event occurs when the SRSM has been in User interaction state for a network-operator-defined period of time (timer $T_{\text{SRF}}$ ) without having a `PlayAnnouncement/PromptAndCollectUserInfoInformation` operation to execute. The SRF initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. The SRSM goes to state “Idle”. + +#### 3.1.3.4.2 State 2 – “Connected” + +This state represents the condition of the SRSM when a bearer channel has been established between a user and the SRF but the initial `PlayAnnouncement/PromptAndCollectUserInfoInformation` has not yet been received (e.g. when `EstablishTemporaryConnection` procedures are used). The method used to provide this bearer channel is not of interest in the FSM. + +- (E1) `Connect_Request_from_SSF` – This event corresponds to a bearer signalling connection request message from the SSF in the Idle state. The details of the bearer signalling state machine related to establishing the connection are not of interest in the SRF-FSM. The SRSM goes to state “Connected”. +- (E2) `PlayAnnouncement/PromptAndCollectUserInfoInformation_from_SCF` – This event takes place when the first `PlayAnnouncement` or `PromptAndCollectUserInfoInformation` operation(s) from the SCF is received. The SRSM goes to state “User interaction”. +- (E3) `Connection_Released_from_SSF` – This event takes place when the SRF receives a release message from the SSF. The SRSM goes to state “Idle”. +- (e4) `SRF_Sanity_Timeout` – This event occurs when the SRSM has been connected for a network-operator-defined period of time (timer $T_{\text{SRF}}$ ) without having a `PlayAnnouncement/PromptAndCollectUserInfoInformation` operation to execute. The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. The SRSM goes to state “Idle”. +- (e5) `Assist_Request_Instructions_Needed` – This event occurs when the `AssistRequestInstructions` operation is sent from the SRSM to the SCF in the absence of a `PlayAnnouncement/PromptAndCollectUserInfoInformation` event (E2) initiated by the presence of a `PlayAnnouncement/PromptAndCollectUserInfoInformation` operation concatenated with the setup request from SSF (E1) (Direct SCF-SRF case). No state change occurs as a result of this event. + +#### 3.1.3.4.3 State 3 – “User interaction” + +The User interaction state indicates that communication is occurring between the user and the SRF via the bearer channel established at the Connected state. This state is entered as a result of event E2. It is exited as a result of events E10, e11 and e12. Events E5, E6, e7, e8 and e9 do not cause a state change. Event E5 also represents additional `PlayAnnouncement/PromptAndCollectUserInfoInformation` operations which are buffered as discussed in the procedures. + +- (E2) and (E5) `PlayAnnouncement/PromptAndCollectUserInfoInformation_from_SCF` – This event takes place when an initial or subsequent `PlayAnnouncement` or `PromptAndCollectUserInfoInformation` operation(s) from the SCF is received. The SRSM goes to state “User interaction” on the first (E2). The SRSM remains in state “User interaction” for subsequent (E5)s. +- (E6) `Cancel_from_SCF` (for `PlayAnnouncement/PromptAndCollectUserInfoInformation`) – This event takes place when the corresponding `PlayAnnouncement` or `PromptAndCollectUserInfoInformation` operation is received from the SCF. The indicated interaction is terminated if it is presently running, otherwise it is deleted from the buffer. The SRSM remains in state “User interaction”. + +- (e7) SRF\_Report\_to\_SCF – This event takes place when a SpecializedResourceReport or a return result for PromptAndCollectUserInformation operation is sent to the SCF. The SRSM remains in state “User interaction”. +- (e8) PlayAnnouncement/PromptAndCollectUserInformation\_Cancelled\_to\_SCF – This event takes place when the PlayAnnouncement/PromptAndCollectUserInformation error caused by the Cancel (for PlayAnnouncement or PromptAndCollectUserInformation) operation is sent to the SCF. This event represents the successful cancellation of an active or buffered PlayAnnouncement/PromptAndCollectUserInformation operation. The SRSM remains in state “User interaction”. +- (e9) Cancel\_Error\_to\_SCF – This event takes place when the cancel error (for PlayAnnouncement or PromptAndCollectUserInformation) is sent to the SCF. This event represents the unsuccessful cancellation of a PlayAnnouncement/PromptAndCollectUserInformation operation. The SRSM remains in state “User interaction”. +- (E10) Connection\_Released\_from\_SSF – This event takes place when the SRSM receives a release message from the SSF. The SRSM goes to state “Idle”. +- (e11) Disconnect\_to\_SSF – This event occurs when the SCF has enabled SRF initiated disconnect with the last PlayAnnouncement/PromptAndCollectUserInformation from SCF (E2) or (E5). The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system after sending the last SpecializedResourceReport or a return result for PromptAndCollectUserInformation operation to the SCF. The SRSM goes to state “Idle”. +- (e12) SRF\_Sanity\_Timeout – This event occurs when the SRSM has been in user interaction state for a network-operator-defined-period of time (timer TSRF) without having a PlayAnnouncement/PromptAndCollectUserInformation operation to execute. The SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system. The SRSM goes to state “Idle”. + +In addition to these explicitly marked transitions, failure of a user-SRF bearer connection will cause the SRSM to transit to Idle from any state. These transitions are not shown on Figure 25 for the purpose of visual clarity. + +### 3.1.3.5 Example SRF control procedures + +This subclause provides a detailed description of the SRF procedures. Arrow diagrams are used for the description of the connect, interaction with the end user, and disconnect stages. + +The SRF control procedures are based on various physical allocation patterns of SRF. The various control procedures are described in this subclause in accordance with the example physical scenarios of protocol architecture in 0.2. + +The service assist and handoff procedures based on the physical scenarios are also described in this subclause as examples. + +Note that, through this subclause, bearer connection control signalling messages are used for explanatory purpose, and are not subject for standardization in this Recommendation. The terms used for bearer connection control signalling messages only represent the functional meaning. + +#### 3.1.3.5.1 SRF connect procedures + +##### 3.1.3.5.1.1 SRF connect physical procedures + +Several procedures are required for different physical scenarios. The cases to be covered are described below and illustrated in Figure 26: + +- the IP is integrated into the SSP, or directly attached to the SSP, that is interacting with the SCP but the SCP’s operations to the IP are relayed via the SSP which performs any needed protocol conversion; +- the IP is directly attached to the SSP that is interacting with the SCP but the SCP’s operations to the IP are sent directly to the IP without SSP relaying involved; + +- iii) the IP is integrated into another SSP, or directly attached to another SSP, than the one that is interacting with the SCP but the SCP's operations to the IP are relayed via the second SSP (called the "Assist" method), and on completion of the user interaction, control is returned to the first SSP; +- iv) the IP is directly attached to a node other than the SSP that is interacting with the SCP but the SCP's operations to the IP are sent directly to the IP without SSP relaying involved (called the "Assist" method, but with a variation on the physical connectivity of the entities involved), and on completion of the user interaction, control is returned to the first SSP; and +- v) the IP is attached to another SSP and on completion of the user interaction, control of the call is retained at that SSP (called the "Handoff" approach). + +In each of the above cases, the operations between the SCP and the SSP may be SS No. 7 TCAP-based; the messaging between the SSP and the IP when the SSP does relaying may be DSS 1 using the facility IE (in this case, the SSP would have to do protocol conversion from SS No. 7 TCAP to DSS-1 facility IE for the operations and responses it relayed between the SCP and the IP); the direct messaging between the SCP and the IP may be SS No. 7 TCAP based; and bearer control signalling may be any system. + +Each of the scenarios will now be examined using arrow diagrams. + +Case i) is illustrated in Figure 27. Note that for the integrated IP/SSP, the internal activities of the node can still be modelled in this way, but the details of how this is achieved are left to the implementor. This approach makes it unnecessary for the SCP to distinguish between integrated and external but directly connected IPs. See also a note on the possibility of concatenating the first user interaction operation with the `ConnectToResource` operation discussed in the subclause on user interaction below. The establishment of the SCF-SRF relationship in this case is implicit. + +Case ii) requires that the IP indicate to the SCP that it is ready to receive operations (see Figure 28). The establishment of the SCF-SRF relationship is explicit. Note that it is necessary to convey a correlation ID to ensure that the transaction established between the SCP and the IP can be correlated to the bearer connection set-up as a result of the SCP's preceding operation to the SSP. + +Case iii) requires that a transaction be opened with the assisting SSP so that it may relay operations from the SCP to the IP (integrated or external). Once the bearer control signalling has reached the assisting SSP, it triggers on the identity of the called facility, and initiates an interaction with the SCP that has requested the assistance. It would also be possible to trigger on other IEs such as the incoming address. The bearer control signalling must contain information to identify the SCP requesting the assistance, and a correlation ID. This information may be hidden in the address information in such a way that non-message based signalling systems may also be used to establish the bearer connection to the assisting SSP. After the `AssistRequestInstructions` are received by the SCP, the procedures are the same as in case i). Figure 29 illustrates the preamble involved. + +Case iv) does not require the establishment of a second transaction from the assisting exchange, hence it need not be an SSP. This then becomes a preamble to the procedure shown in Figure 28 as shown in Figure 30. + +Case v) merely requires the sending of an operation to the first SSP to route the call to the handed-off SSP, and then Figure 27 applies at handed-off SSP. This is shown in Figure 31. Note that the activity at handed-off SSP represents a new interaction with the SCP and "`AssistRequestInstructions`" is used. Once the bearer control signalling has reached the assisting SSP, it triggers on the identity of the called facility, and initiates an interaction with the SCP that has requested the assistance. It would also be possible to trigger on other IEs such as the incoming address. The bearer control signalling must contain information to identify the SCP requesting the assistance, and a correlation ID. This information may be hidden in the address information in such a way that non-message based signalling systems may also be used to establish the bearer connection to the assisting SSP. + +Case i) SSF relay + +![Diagram for Case i) SSF relay. It shows an SCP connected to an SSF. The SSF is connected to an IP. The IP is connected to an SRF. The SSF is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'.](c80e1284549c9914d0249b0e749c500a_img.jpg) + +Diagram for Case i) SSF relay. An SCP (Service Control Point) containing an SCF (Service Control Function) is connected to an SSF (Service Switching Function) containing SSF and CCF (Call Control Function) components. The SSF is connected to an IP (Intelligent Peripheral) containing an SRF (Service Resource Function). The SSF is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'. + +Diagram for Case i) SSF relay. It shows an SCP connected to an SSF. The SSF is connected to an IP. The IP is connected to an SRF. The SSF is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'. + +Case ii) Direct path SCP to IP + +![Diagram for Case ii) Direct path SCP to IP. It shows an SCP connected to an SSF and an IP. The SSF is connected to an SRF. The IP is labeled 'IP'.](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) + +Diagram for Case ii) Direct path SCP to IP. An SCP containing an SCF is connected directly to an SSF (containing SSF and CCF) and an IP (containing an SRF). The SSF is connected to the SRF. The IP is labeled 'IP'. + +Diagram for Case ii) Direct path SCP to IP. It shows an SCP connected to an SSF and an IP. The SSF is connected to an SRF. The IP is labeled 'IP'. + +Case iii) Assist with relay; return control to initiating SSP on completion of UI + +![Diagram for Case iii) Assist with relay; return control to initiating SSP on completion of UI. It shows an SCP connected to an Initiating SSP and an Assisting SSP. The Initiating SSP is connected to the Assisting SSP. The Assisting SSP is connected to an IP. The IP is connected to an SRF. The Assisting SSP is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'.](16e2337d7302fa71012e69303a459c35_img.jpg) + +Diagram for Case iii) Assist with relay; return control to initiating SSP on completion of UI. An SCP containing an SCF is connected to an Initiating SSP (containing SSF and CCF) and an Assisting SSP (containing SSF and CCF). The Initiating SSP is connected to the Assisting SSP. The Assisting SSP is connected to an IP (containing an SRF). The Assisting SSP is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'. + +Diagram for Case iii) Assist with relay; return control to initiating SSP on completion of UI. It shows an SCP connected to an Initiating SSP and an Assisting SSP. The Initiating SSP is connected to the Assisting SSP. The Assisting SSP is connected to an IP. The IP is connected to an SRF. The Assisting SSP is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'. + +Case iv) Assist without relay: return control to initiating SSP on completion of UI + +![Diagram for Case iv) Assist without relay: return control to initiating SSP on completion of UI. It shows an SCP connected to an Initiating SSP and an Exchange. The Initiating SSP is connected to the Exchange. The Exchange is connected to an IP. The IP is connected to an SRF. The Exchange is labeled 'Exchange'. The IP is labeled 'IP'.](ff722ae9516b94709d721deaf5523d2e_img.jpg) + +Diagram for Case iv) Assist without relay: return control to initiating SSP on completion of UI. An SCP containing an SCF is connected to an Initiating SSP (containing SSF and CCF) and an Exchange (containing a CCF). The Initiating SSP is connected to the Exchange. The Exchange is connected to an IP (containing an SRF). The Exchange is labeled 'Exchange'. The IP is labeled 'IP'. + +Diagram for Case iv) Assist without relay: return control to initiating SSP on completion of UI. It shows an SCP connected to an Initiating SSP and an Exchange. The Initiating SSP is connected to the Exchange. The Exchange is connected to an IP. The IP is connected to an SRF. The Exchange is labeled 'Exchange'. The IP is labeled 'IP'. + +Case v) Hand-off: retain control at assisting SSP after UI completed + +![Diagram for Case v) Hand-off: retain control at assisting SSP after UI completed. It shows an SCP connected to an Initiating SSP and an Assisting SSP. The Initiating SSP is connected to the Assisting SSP. The Assisting SSP is connected to an IP. The IP is connected to an SRF. The Assisting SSP is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'.](8792c5728b4e100e0a00432bbfcab87b_img.jpg) + +Diagram for Case v) Hand-off: retain control at assisting SSP after UI completed. An SCP containing an SCF is connected to an Initiating SSP (containing SSF and CCF) and an Assisting SSP (containing SSF and CCF). The Initiating SSP is connected to the Assisting SSP. The Assisting SSP is connected to an IP (containing an SRF). The Assisting SSP is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'. + +Diagram for Case v) Hand-off: retain control at assisting SSP after UI completed. It shows an SCP connected to an Initiating SSP and an Assisting SSP. The Initiating SSP is connected to the Assisting SSP. The Assisting SSP is connected to an IP. The IP is connected to an SRF. The Assisting SSP is labeled 'Non-integrated SRF' and 'Integrated SRF'. The IP is labeled 'IP'. + +T1146890-92/d27 + +FIGURE 26/Q.1218 +Physical scenarios + +![Sequence diagram for FIGURE 27/Q.1218 showing connections between SCP, SSP, and IP. SCP sends a black 'ConnectToResource' message to SSP. SSP sends a gray 'Setup request' to IP and receives a gray 'Setup response' from IP. A vertical double-headed arrow labeled 'IP connection' is between SSP and IP. Reference T1146900-92/d28 is at the bottom right.](a76fd8608a1490167e6c1a4ed32b38e6_img.jpg) + +Sequence diagram for FIGURE 27/Q.1218 showing connections between SCP, SSP, and IP. SCP sends a black 'ConnectToResource' message to SSP. SSP sends a gray 'Setup request' to IP and receives a gray 'Setup response' from IP. A vertical double-headed arrow labeled 'IP connection' is between SSP and IP. Reference T1146900-92/d28 is at the bottom right. + +FIGURE 27/Q.1218 +**Connection to integrated or external IP with SSP relay of IP operations** + +![Sequence diagram for FIGURE 28/Q.1218 showing connections between SCP, SSP, and IP. SCP sends a black 'EstablishTemporary Connection' message to SSP. SSP sends a gray 'Setup request' to IP and receives a gray 'Setup response' from IP. IP then sends a black 'AssistRequestInstructions' message to SCP. A vertical double-headed arrow labeled 'IP connection' is between SSP and IP. Reference T1146910-92/d29 is at the bottom right.](5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg) + +Sequence diagram for FIGURE 28/Q.1218 showing connections between SCP, SSP, and IP. SCP sends a black 'EstablishTemporary Connection' message to SSP. SSP sends a gray 'Setup request' to IP and receives a gray 'Setup response' from IP. IP then sends a black 'AssistRequestInstructions' message to SCP. A vertical double-headed arrow labeled 'IP connection' is between SSP and IP. Reference T1146910-92/d29 is at the bottom right. + +FIGURE 28/Q.1218 +**Connection to IP with direct link to SCP – IP initiates interaction with SCP** + +NOTE – Black lines indicate INAP operations, gray lines indicate DSS 1 operations. + +![Sequence diagram for FIGURE 29/Q.1218 showing connections between SCP, Initiating SSP, Assisting SSP, and IP. SCP sends a black 'EstablishTemporary Connection' message to Initiating SSP. Initiating SSP sends a gray 'Setup request' to Assisting SSP and receives a gray 'Setup response' from Assisting SSP. Assisting SSP sends a black 'AssistRequestInstructions' message to SCP. SCP then sends a black 'ConnectToResource' message to Assisting SSP. A vertical double-headed arrow labeled 'IP connection' is next to IP. Reference T1146920-92/d30 is at the bottom right.](0ad1b90f313a822e42d66a872e981b42_img.jpg) + +Sequence diagram for FIGURE 29/Q.1218 showing connections between SCP, Initiating SSP, Assisting SSP, and IP. SCP sends a black 'EstablishTemporary Connection' message to Initiating SSP. Initiating SSP sends a gray 'Setup request' to Assisting SSP and receives a gray 'Setup response' from Assisting SSP. Assisting SSP sends a black 'AssistRequestInstructions' message to SCP. SCP then sends a black 'ConnectToResource' message to Assisting SSP. A vertical double-headed arrow labeled 'IP connection' is next to IP. Reference T1146920-92/d30 is at the bottom right. + +FIGURE 29/Q.1218 +**Preamble for assist case with integrated IP +or external IP and SSP relay of SCP-IP messages** + +![Sequence diagram for FIGURE 30/Q.1218 showing interactions between SCP, SSP, Exchange, and IP. The diagram shows the 'Preamble for assist case with external IP and direct SCP-IP messaging'. Lifelines: SCP, SSP, Exchange, IP. Messages: SCP to SSP: EstablishTemporary Connection; SSP to Exchange: Setup request; Exchange to IP: Setup request; IP to Exchange: Setup response; Exchange to SSP: Setup response; SSP to SCP: AssistRequestInstructions. A vertical double-headed arrow on the right labeled 'IP connection' spans between the IP lifeline and the bottom of the diagram. Reference T1146930-92/d31 is at the bottom right.](28e47e64ac18ca4d8924dab65cedc2d8_img.jpg) + +Sequence diagram for FIGURE 30/Q.1218 showing interactions between SCP, SSP, Exchange, and IP. The diagram shows the 'Preamble for assist case with external IP and direct SCP-IP messaging'. Lifelines: SCP, SSP, Exchange, IP. Messages: SCP to SSP: EstablishTemporary Connection; SSP to Exchange: Setup request; Exchange to IP: Setup request; IP to Exchange: Setup response; Exchange to SSP: Setup response; SSP to SCP: AssistRequestInstructions. A vertical double-headed arrow on the right labeled 'IP connection' spans between the IP lifeline and the bottom of the diagram. Reference T1146930-92/d31 is at the bottom right. + +FIGURE 30/Q.1218 +**Preamble for assist case with external IP and direct SCP-IP messaging** + +![Sequence diagram for FIGURE 31/Q.1218 showing interactions between SCP, Initiating SSP, Assisting SSP, and IP. The diagram shows the 'Preamble for hand-off case'. Lifelines: SCP, Initiating SSP, Assisting SSP, IP. Messages: SCP to Initiating SSP: SelectRoute/Connect; Initiating SSP to Assisting SSP: Setup request; Assisting SSP to Initiating SSP: Setup response; Assisting SSP to SCP: AssistRequestInstructions; SCP to Assisting SSP: ConnectToResource. A vertical double-headed arrow on the right labeled 'IP connection' spans between the IP lifeline and the bottom of the diagram. Reference T1179990-96/d32 is at the bottom right.](1daee79ab1ab652586116f083d50ed9d_img.jpg) + +Sequence diagram for FIGURE 31/Q.1218 showing interactions between SCP, Initiating SSP, Assisting SSP, and IP. The diagram shows the 'Preamble for hand-off case'. Lifelines: SCP, Initiating SSP, Assisting SSP, IP. Messages: SCP to Initiating SSP: SelectRoute/Connect; Initiating SSP to Assisting SSP: Setup request; Assisting SSP to Initiating SSP: Setup response; Assisting SSP to SCP: AssistRequestInstructions; SCP to Assisting SSP: ConnectToResource. A vertical double-headed arrow on the right labeled 'IP connection' spans between the IP lifeline and the bottom of the diagram. Reference T1179990-96/d32 is at the bottom right. + +FIGURE 31/Q.1218 +**Preamble for hand-off case** + +**3.1.3.5.2 SRF end user interaction procedures** + +The end user interaction procedures allow: + +- the sending of one or multiple messages to the end user by using the PlayAnnouncement operations; +- a dialogue with the end user by using one or a sequence of PromptAndCollectUserInformation operations; +- a combination of the above; and +- cancellation of a PlayAnnouncement or PromptAndCollectUserInformation operations by using a generic cancel operation. + +**3.1.3.5.2.1 Play Announcement/Prompt & Collect User Information (PA/P&C)** + +There are only two physical scenarios for user interaction: + +- i) the SSP relays the operations from the SCP to the IP and the responses from the IP to the SCP (SSF relay case); and +- ii) the operations from the SCP to the IP and the responses from the IP are sent directly between the SCP and the IP without involving the SSP (direct SCF-SRF case). + +Case i) is illustrated in Figure 32 below. + +![Sequence diagram for Figure 32 showing SSP relay of user interaction operations and responses. Lifelines: SCP, SSP, IP. The diagram shows a relay of PlayAnnouncement/PromptAndCollectUserInfo and SpecializedResourceReport/RR messages between SCP, SSP, and IP. A vertical double-headed arrow on the right indicates SRF interaction with the end user. Reference T1146950-92/d33 is at the bottom right.](0757c1ca2d4a19ca824d92246e610fc7_img.jpg) + +``` + +sequenceDiagram + participant SCP + participant SSP + participant IP + Note right of IP: SRF interaction with the end user + SCP->>SSP: PlayAnnouncement/PromptAndCollectUserInfo + SSP->>IP: PlayAnnouncement/PromptAndCollectUserInfo + IP-->>SSP: SpecializedResourceReport/RR for PromptAndCollectUserInfo + SSP-->>SCP: SpecializedResourceReport/RR for PromptAndCollectUserInfo + Note right of IP: T1146950-92/d33 + +``` + +Sequence diagram for Figure 32 showing SSP relay of user interaction operations and responses. Lifelines: SCP, SSP, IP. The diagram shows a relay of PlayAnnouncement/PromptAndCollectUserInfo and SpecializedResourceReport/RR messages between SCP, SSP, and IP. A vertical double-headed arrow on the right indicates SRF interaction with the end user. Reference T1146950-92/d33 is at the bottom right. + +FIGURE 32/Q.1218 + +**SSP relay of user interaction operations and responses** + +Case ii) is illustrated in Figure 33. + +It is also necessary to consider the capability of SS No. 7 TCAP to concatenate several Invoke PDUs in one message. This capability allows, for the scenario in Figure 27, the ConnectToResource and the first PlayAnnouncement/PromptAndCollectUserInfo to be carried in one message. This has some advantages in this physical scenario, such as reduced numbers of messages, and possibly better end-user perceived performance. + +![Sequence diagram for Figure 33 showing direct SCF-SRF user interaction operations and responses. Lifelines: SCP, SSP, IP. The diagram shows a concatenated PlayAnnouncement/PromptAndCollectUserInfo message from SCP to IP, and a SpecializedResourceReport/RR for PromptAndCollectUserInfo from IP to SCP. A vertical double-headed arrow on the right indicates SRF interaction with the end user. Reference T1146960-92/d34 is at the bottom right.](7beca7f8804a7b96d70e59e4b9034085_img.jpg) + +``` + +sequenceDiagram + participant SCP + participant SSP + participant IP + Note right of IP: SRF interaction with the end user + SCP->>IP: PlayAnnouncement/PromptAndCollectUserInfo + IP-->>SCP: SpecializedResourceReport/RR for PromptAndCollectUserInfo + Note right of IP: T1146960-92/d34 + +``` + +Sequence diagram for Figure 33 showing direct SCF-SRF user interaction operations and responses. Lifelines: SCP, SSP, IP. The diagram shows a concatenated PlayAnnouncement/PromptAndCollectUserInfo message from SCP to IP, and a SpecializedResourceReport/RR for PromptAndCollectUserInfo from IP to SCP. A vertical double-headed arrow on the right indicates SRF interaction with the end user. Reference T1146960-92/d34 is at the bottom right. + +FIGURE 33/Q.1218 + +**Direct SCF-SRF of user interaction operations and responses** + +**3.1.3.5.3 SRF disconnection procedures** + +The disconnection procedures are controlled by the SCF and the procedure used is selected based on the needs of the service being executed. The bearer disconnection procedure selected by the SCF is to either allow the SRF to disconnect on completion of user interaction, or to have the SCF explicitly order the SSF to disconnect. + +SRF disconnect does not cause disconnection by the SSF-CCF back to the end user terminal unless the transaction with the SCF has been terminated, indicating the user interaction completed the call. The SSF-CCF recognizes that a connection to an SRF is involved because the operations from the SCF for this purpose are distinct from the operations that would be used to route the call towards a destination. There is no impact on bearer signalling state machines as a result of this since incoming and outgoing bearer signalling events are not simply transferred to each other, but rather are absorbed in call processing, and regenerated as needed by call processing. Therefore, to achieve the desired functionality, call processing need simply choose not to regenerate the disconnect in the backward direction. Figure 34 illustrates this concept. + +As for the SRF connection procedures, the SRF disconnection is affected by the physical network configuration. + +![Diagram showing the relationship of incoming and outgoing signalling systems to call processing. At the top is a box labeled 'Call processing'. Below it, two boxes labeled 'Incoming signalling system' and 'Outgoing signalling system' are connected to 'Call processing' via lines labeled 'Primitives'. Arrows labeled 'Messages' point outwards from the bottom of each signalling system box. A reference code 'T1146970-92/d35' is shown below the outgoing system.](b8dd9521b601d25e46c5effa0a59b7e1_img.jpg) + +``` + +graph TD + CP[Call processing] + ISS[Incoming signalling system] + OSS[Outgoing signalling system] + CP ---|Primitives| ISS + CP ---|Primitives| OSS + ISS -- Messages --> M1[Messages] + OSS -- Messages --> M2[Messages] + T1146970-92/d35 + +``` + +Diagram showing the relationship of incoming and outgoing signalling systems to call processing. At the top is a box labeled 'Call processing'. Below it, two boxes labeled 'Incoming signalling system' and 'Outgoing signalling system' are connected to 'Call processing' via lines labeled 'Primitives'. Arrows labeled 'Messages' point outwards from the bottom of each signalling system box. A reference code 'T1146970-92/d35' is shown below the outgoing system. + +FIGURE 34/Q.1218 +**Relationship of incoming and outgoing signalling systems to call processing** + +In order to simplify the interface between the SCF and the SRF, a number of assumptions are made. The assumptions, and the resulting rules, result in unambiguous procedures from both the SCF and the SRF points of view. The rules, presented below, refer to the SRF originated disconnect, or “SRF Initiated Disconnect”, and to the SCF originated disconnect, or “SCF Initiated Disconnect”. While other scenarios are possible, they are not included because they either duplicate the functionality presented below or they otherwise do not add value from a service perspective. + +- 1) If a series of PlayAnnouncement/PromptAndCollectUserInformation operations are to be executed by the same SRF, then SRF disconnect is inhibited for all but the last and may be inhibited on the last PlayAnnouncement/PromptAndCollectUserInformation. When a subsequent PlayAnnouncement/PromptAndCollectUserInformation is received, it is buffered until the completion of any preceding PlayAnnouncement/PromptAndCollectUserInformation. +- 2) A generic cancel operation terminates the indicated PlayAnnouncement/PromptAndCollectUserInformation if it is being executed by the SRF, but does not disconnect the SRF. If the cancel operation is for a buffered PlayAnnouncement/PromptAndCollectUserInformation, that PlayAnnouncement/PromptAndCollectUserInformation is discarded, but the current and any buffered PlayAnnouncement/PromptAndCollectUserInformations are executed. An SRF interacts with one user only and therefore cancelling a PlayAnnouncement/PromptAndCollectUserInformation only affects the user to which the SRF is connected. +- 3) The SCF must either explicitly order “Disconnect” or enable SRF initiated disconnect at the end of the PlayAnnouncement/PromptAndCollectUserInformation. An SRF left connected without a PlayAnnouncement/PromptAndCollectUserInformation to execute may autonomously disconnect if it has not received any PlayAnnouncement/PromptAndCollectUserInformation operations within a defined time limit. This could occur, for example, after an EstablishTemporaryConnection which is not followed within a reasonable time period with a PlayAnnouncement/PromptAndCollectUserInformation operation. This sanity timing value will depend on the nature of the interaction the SRF supports and should be selected by the network operator accordingly. +- 4) When SRF initiated disconnect is enabled in a PlayAnnouncement/PromptAndCollectUserInformation, then the SRF must disconnect on completion of the user interaction. +- 5) When SRF initiated disconnect is not enabled, the SCF must ask the SRF to inform it of the completion of the user interaction using the SpecializedResourceReport operation for “announcement complete” or using the return result for the PromptAndCollectUserInformation operation. + +- 6) If the user disconnects, the SRF is disconnected and the SSF releases resources and handles the transaction between the SSF and the SCF as specified in Recommendation Q.1214 and in this Recommendation. The SRF discards any buffered operations and returns its resources to idle. The relationship with the SCF is terminated. +- 7) When the SCF explicitly orders the SSF to disconnect by “DisconnectForwardConnection” operation, the SSF releases the bearer connection to the SRF, and returns to the “waiting for instructions” state. No operation reporting SRF disconnect from the SSF to the SCF is required. + +### 3.1.3.5.3.1 SRF initiated disconnect + +The SRF disconnect procedure is illustrated in Figure 35. The SRF disconnect is enabled by the SCF within a PlayAnnouncement/PromptAndCollectUserInformation operation. When the SRF receives a PlayAnnouncement/PromptAndCollectUserInformation enabling disconnection, it completes the dialogue as instructed by the PlayAnnouncement/PromptAndCollectUserInformation, and then initiates the SRF initiated disconnection using the applicable bearer control signalling. The SSF-CCF knows that it is an SRF disconnecting and does not continue clearing the call toward the end user. The SSF returns to the “waiting for instructions” state and executes any buffered operations. In the handoff case, the SSP shown in Figure 35 is the “handed-off” SSP. + +![Sequence diagram illustrating the SRF initiated disconnect procedure. The diagram shows three entities: SCP, SSP, and IP. The sequence of messages is: 1. SCP sends PlayAnnouncement/PromptAndCollectUserInformation to SSP. 2. SSP sends PlayAnnouncement/PromptAndCollectUserInformation to IP. 3. IP sends SpecializedResourceReport/RR for PromptAndCollectUserInformation to SSP. 4. SSP sends Disconnect to IP. 5. SSP sends SpecializedResourceReport/RR for PromptAndCollectUserInformation to SCP. Vertical arrows on the right indicate 'SRF interaction with the end user' (between SSP and IP) and 'SRF disconnection' (starting from IP). The diagram is labeled T1146980-92/d36.](09797d4289ec96309d21a9a993153dab_img.jpg) + +Sequence diagram illustrating the SRF initiated disconnect procedure. The diagram shows three entities: SCP, SSP, and IP. The sequence of messages is: 1. SCP sends PlayAnnouncement/PromptAndCollectUserInformation to SSP. 2. SSP sends PlayAnnouncement/PromptAndCollectUserInformation to IP. 3. IP sends SpecializedResourceReport/RR for PromptAndCollectUserInformation to SSP. 4. SSP sends Disconnect to IP. 5. SSP sends SpecializedResourceReport/RR for PromptAndCollectUserInformation to SCP. Vertical arrows on the right indicate 'SRF interaction with the end user' (between SSP and IP) and 'SRF disconnection' (starting from IP). The diagram is labeled T1146980-92/d36. + +a) Disconnect from SRF is not forbidden. + +FIGURE 35/Q.1218 + +### SCF disconnect for local, embedded and hand-off scenarios + +For the assisting SSF case, the SRF initiated disconnect procedures are not used because the assisting SSF remains in the “waiting for instructions” state and does not propagate the disconnection of the bearer connection to the Initiating SSF. The SCF initiated disconnect procedures described in the following subclause are used for the assisting SSF case. + +For the direct SCF-SRF case, the procedures also work in the same manner. The SRF disconnect is enabled by the SCF within a PlayAnnouncement/PromptAndCollectUserInformation operation. When the SRF receives a PlayAnnouncement/PromptAndCollectUserInformation enabling disconnection, it completes the dialogue as instructed by the PlayAnnouncement/PromptAndCollectUserInformation, and then initiates the SRF initiated disconnection using the applicable bearer control signalling. The Initiating SSF-CCF knows that it is an SRF disconnecting and does not continue clearing the call toward the end user. The Initiating SSF returns to the “waiting for instructions” state and executes any buffered operations. + +### 3.1.3.5.3.2 SCF initiated disconnect + +The SCF initiated disconnect procedure is illustrated in Figure 36. Bearer messages are shown in gray. The figure shows only the assisting SSF case, and the direct SCF-SRF case is not shown. To initiate the SCF initiated disconnection of the SRF, the SCF must request and receive a reply to the last PlayAnnouncement/PromptAndCollectUserInformation operation requested. The SpecializedResourceReport operation contains an “announcement complete” and return result for PromptAndCollectUserInformation contains “collected information.” + +![Sequence diagram for SCF initiated disconnect for assist scenario. Lifelines: SCP, Initiating SSP, Assisting SSP, IP. The sequence shows: 1. SCP sends PlayAnnouncement/PromptAndCollectUserInformation to Initiating SSP. 2. Initiating SSP forwards it to Assisting SSP. 3. Assisting SSP sends it to IP. 4. IP responds with SpecializedResourceReport/RR for PromptAndCollectUserInformation to Assisting SSP. 5. Assisting SSP forwards it to Initiating SSP. 6. Initiating SSP sends DisconnectForwardConnection to SCP. 7. SCP sends Disconnect to Initiating SSP. 8. Initiating SSP sends Disconnect to Assisting SSP. 9. Assisting SSP sends Disconnect to IP. Vertical double-headed arrows on the right indicate 'SRF interaction with the end user' (between Assisting SSP and IP) and 'SRF disconnection' (between Assisting SSP and IP). Reference T1146990-92/d37 is at the bottom right.](3eb2af31c2e61e2595c8440d726f5d4e_img.jpg) + +Sequence diagram for SCF initiated disconnect for assist scenario. Lifelines: SCP, Initiating SSP, Assisting SSP, IP. The sequence shows: 1. SCP sends PlayAnnouncement/PromptAndCollectUserInformation to Initiating SSP. 2. Initiating SSP forwards it to Assisting SSP. 3. Assisting SSP sends it to IP. 4. IP responds with SpecializedResourceReport/RR for PromptAndCollectUserInformation to Assisting SSP. 5. Assisting SSP forwards it to Initiating SSP. 6. Initiating SSP sends DisconnectForwardConnection to SCP. 7. SCP sends Disconnect to Initiating SSP. 8. Initiating SSP sends Disconnect to Assisting SSP. 9. Assisting SSP sends Disconnect to IP. Vertical double-headed arrows on the right indicate 'SRF interaction with the end user' (between Assisting SSP and IP) and 'SRF disconnection' (between Assisting SSP and IP). Reference T1146990-92/d37 is at the bottom right. + +a) Disconnect from SRF forbidden. + +FIGURE 36/Q.1218 +**SCF initiated disconnect for assist scenario** + +The SCF initiated disconnect uses an operation called `DisconnectForwardConnection`. Once the `DisconnectForwardConnection` is received by the SSF, it will initiate a “release of bearer channel connection” between the physical entities containing the SSF and SRF, using applicable bearer control signalling. Since the SCF (which initiates the disconnect), the SSF (which instructs bearer signalling to disconnect) and the SRF (which receives disconnect notification via bearer signalling) are aware that disconnect is occurring, they are synchronized. Therefore, a “pre-arranged” end may be used to close the transaction. This does not preclude the use of explicit end messages for this purpose. + +For assisting SSF case, the initiating SSP, on receipt of the `DisconnectForwardConnection` from the SCP, disconnects forward to the assisting SSP, and this disconnection is propagated to the IP. The initiating SSP, knowing that the forward connection was initiated as the result of an `EstablishTemporaryConnection`, does not disconnect back to the user but returns to the “waiting for instructions” state. + +### 3.1.3.5.4 Examples illustrating complete user interaction sequences + +The following figures and their accompanying tables provide examples of complete sequences of user interaction operations covering the three stages: + +- connect the SRF and the end user (bearer connection) and establish the SCF-SRF relationship; +- interact with the end user; +- disconnect the SRF and the end user (bearer connection) and terminate the SCF-SRF relationship. + +![Diagram of SSP with integrated SRF. An SCP triangle contains an SCF circle. An SSP rectangle contains SSF, CCF, and SRF circles. Arrows show protocol flows: A (SCF to SSP), D (SSP to SCF), B (CCF to SRF), and C (SRF to CCF). The link is labeled 'SS No. 7 TCAP'.](defe20e5056d0c3552de2d50ce88c5cb_img.jpg) + +Diagram of SSP with integrated SRF. An SCP triangle contains an SCF circle. An SSP rectangle contains SSF, CCF, and SRF circles. Arrows show protocol flows: A (SCF to SSP), D (SSP to SCF), B (CCF to SRF), and C (SRF to CCF). The link is labeled 'SS No. 7 TCAP'. + +T1147000-92/d38 + +FIGURE 37/Q.1218 +**SSP with integrated SRF** + +In Figure 37, the SSP with an integrated (or embedded) SRF, the procedural scenarios can be mapped as follows: + +| Procedure name | Operations | Protocol flows | +|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| Connect to resource and first PA/P&C | ConnectToResource;
PlayAnnouncement/
PromptAndCollectUserInformation
Setup; PlayAnnouncement/
PromptAndCollectUserInformation | A
B | +| User interaction | PlayAnnouncement/
PromptAndCollectUserInformation
SpecializedResourceReport/RR for
PromptAndCollectUserInformation | A then B
C then D | +| SRF initiated disconnect | SpecializedResourceReport/RR for
PromptAndCollectUserInformation
Disconnect | C then D
C (intra-SSP bearer control) | +| SCF initiated disconnect | SpecializedResourceReport/RR for
PromptAndCollectUserInformation
DisconnectForwardConnection
Disconnect | C then D
A
B (intra-SSP bearer control) | + +A simple extension to this integrated case is the configuration where the SRF is located in an intelligent peripheral locally attached to the SSP. The SCP-IP operations are relayed via the SSF in the SSP. This is depicted in Figure 38. + +![Diagram showing message relaying between an SCP, an SSP, and an IP. The SCP contains an SCF. The SSP contains an SSF and a CCF. The IP contains an SRF. Arrows A and D show SS No. 7 TCAP messages between the SCF and the SSP. Arrows B and C show DSS 1 or SS No. 7 TCAP service control messages between the SSP and the IP. Arrows E and F show DSS 1 or SS No. 7 ISUP bearer control messages between the SSP and the IP.](af4f213abb5ad1891a43425e0d758021_img.jpg) + +The diagram illustrates the message relaying architecture between an SCP, an SSP, and an IP. + +- SCP (Service Control Point):** Represented by a triangle containing an oval labeled **SCF**. +- SSP (Service Switching Point):** Represented by a rectangle containing two ovals labeled **SSF** and **CCF**. +- IP (Intelligent Peripheral):** Represented by a rectangle containing an oval labeled **SRF**. + +Message flows are indicated by arrows: + +- A:** Message from the SCF in the SCP to the SSP. +- D:** Message from the SSP to the SCF in the SCP. +- Protocol for A and D:** SS No. 7 TCAP. +- B:** Message from the SSP to the IP. +- C:** Message from the IP to the SSP. +- Protocol for B and C:** DSS 1 or SS No. 7 TCAP service control. +- E:** Message from the SSP to the IP. +- F:** Message from the IP to the SSP. +- Protocol for E and F:** DSS 1 or SS No. 7 ISUP bearer control. + +T1147010-92/d39 + +Diagram showing message relaying between an SCP, an SSP, and an IP. The SCP contains an SCF. The SSP contains an SSF and a CCF. The IP contains an SRF. Arrows A and D show SS No. 7 TCAP messages between the SCF and the SSP. Arrows B and C show DSS 1 or SS No. 7 TCAP service control messages between the SSP and the IP. Arrows E and F show DSS 1 or SS No. 7 ISUP bearer control messages between the SSP and the IP. + +FIGURE 38/Q.1218 +**SSP relays messages between SCP and IP** + +The procedural scenarios for this relay SSF with an IP (see Figure 38) can be mapped as follows: + +| Procedure name | Operations | Protocol flows | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| Connect to resource and first PA/P&C | ConnectToResource;
PlayAnnouncement/
PromptAndCollectUserInformation
If DSS 1 used:
Setup; PlayAnnouncement/
PromptAndCollectUserInformation
If SS No. 7 used:
IAM
PlayAnnouncement/
PromptAndCollectUserInformation | A

E and B (Facility IE)

E
B | +| User interaction | PlayAnnouncement/
PromptAndCollectUserInformation
SpecializedResourceReport/RR for
PromptAndCollectUserInformation | A then B

C then D | +| SRF initiated disconnect | SpecializedResourceReport/RR for
PromptAndCollectUserInformation
If DSS 1 used:
Disconnect
If SS No. 7 used:
Release | C then D

F
F | +| SCF initiated disconnect | SpecializedResourceReport/RR for
PromptAndCollectUserInformation
DisconnectForwardConnection
If DSS 1 used:
Disconnect
If SS No. 7 used:
Release | C then D

A

E
E | + +In some cases, the IP may have an SS No. 7 or other interface to the controlling SCP. This case is shown in Figure 39. Note that the SCP must correlate two transactions to coordinate the activities. + +![Diagram of Direct SCP-IP information transfer. At the top is an SCP (Service Control Point) containing an SCF (Service Control Function). Below it are two boxes: SSP (Service Switching Point) on the left containing SSF (Service Switching Function) and CCF (Call Control Function); and IP (Intelligent Peripheral) on the right containing SRF (Speech Resource Function). Arrows indicate protocol flows: A (SSP to SCP), B (SCP to SSP), C (SCP to IP), E (SSF to SRF), and F (SRF to SSP). Labels 'SS No. 7 TCAP' are on the SCP-SSP and SCP-IP links. A label 'DSS 1 or SS No. 7 ISUP bearer control' is on the F arrow. A reference 'T1180000-96/d40' is at the bottom right.](5cc9a312ebe733ae244e3b93cfea67e1_img.jpg) + +Diagram of Direct SCP-IP information transfer. At the top is an SCP (Service Control Point) containing an SCF (Service Control Function). Below it are two boxes: SSP (Service Switching Point) on the left containing SSF (Service Switching Function) and CCF (Call Control Function); and IP (Intelligent Peripheral) on the right containing SRF (Speech Resource Function). Arrows indicate protocol flows: A (SSP to SCP), B (SCP to SSP), C (SCP to IP), E (SSF to SRF), and F (SRF to SSP). Labels 'SS No. 7 TCAP' are on the SCP-SSP and SCP-IP links. A label 'DSS 1 or SS No. 7 ISUP bearer control' is on the F arrow. A reference 'T1180000-96/d40' is at the bottom right. + +FIGURE 39/Q.1218 +**Direct SCP-IP information transfer** + +In Figure 39, the procedural scenarios can be mapped as follows: + +| Procedure name | Operations | Protocol flows | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Connect to resource | EstablishTemporaryConnection
If DSS 1 used:
Setup
AssistRequestInstructions
If SS No. 7 used:
IAM
AssistRequestInstructions | A
E
C
E
C | +| User interaction | PlayAnnouncement/
PromptAndCollectUserInformation
SpecializedResourceReport/RR for
PromptAndCollectUserInformation | B
C | +| SRF initiated disconnect | SpecializedResourceReport/RR for
PromptAndCollectUserInformation
If DSS 1 used:
Disconnect
If SS No. 7 used:
Release | C
F
F | +| SCF initiated disconnect | SpecializedResourceReport/RR for
PromptAndCollectUserInformation
DisconnectForwardConnection
If DSS 1 used:
Disconnect
If SS No. 7 used:
Release | C
A
E
E | + +The assisting SSF scenario involves straightforward procedural extensions to the basic cases shown above. One mapping of the assisting SSF case is shown in Figure 40. In this case, SRF initiated disconnect cannot be used. Other physical mappings can be derived as described in the text following the figure and its accompanying table. + +![Diagram of Figure 40/Q.1218: SSP assist (relay SSP). The diagram shows an SCP (Service Control Point) at the top with an internal SCF (Service Control Function). Below it are two SSPs: an Initiating SSP on the left and an Assisting SSP on the right. The Initiating SSP contains SSF (Service Switch Function) and CCF (Call Control Function). The Assisting SSP contains SSF, CCF, and SRF (Service Resource Function). Arrows indicate signaling paths: A (Initiating SSP to SCP), B (SCP to Initiating SSP), C (SCP to Assisting SSP), E (Initiating SSP to Assisting SSP), F (Assisting SSP to Initiating SSP), G (Assisting SSP internal), and H (Assisting SSP internal). A label 'SS No. 7 TCAP' is present near the SCP connections. A label 'Bearer control signalling (possibly with transit exchanges)' is present between the SSPs. A small code 'T1180010-96/d41' is at the bottom right.](dc075f714892571abc5f74f1a76b80dc_img.jpg) + +Diagram of Figure 40/Q.1218: SSP assist (relay SSP). The diagram shows an SCP (Service Control Point) at the top with an internal SCF (Service Control Function). Below it are two SSPs: an Initiating SSP on the left and an Assisting SSP on the right. The Initiating SSP contains SSF (Service Switch Function) and CCF (Call Control Function). The Assisting SSP contains SSF, CCF, and SRF (Service Resource Function). Arrows indicate signaling paths: A (Initiating SSP to SCP), B (SCP to Initiating SSP), C (SCP to Assisting SSP), E (Initiating SSP to Assisting SSP), F (Assisting SSP to Initiating SSP), G (Assisting SSP internal), and H (Assisting SSP internal). A label 'SS No. 7 TCAP' is present near the SCP connections. A label 'Bearer control signalling (possibly with transit exchanges)' is present between the SSPs. A small code 'T1180010-96/d41' is at the bottom right. + +FIGURE 40/Q.1218 +**SSP assist (relay SSP)** + +Note that the integrated SRF and SSF relay case requires a transaction between the SCP and the assisting SSP (see Figure 40) but the SCP direct case does not since the transaction is directly between the SCP and the IP connected to the remote exchange. In the latter case, any transit exchanges, including the one the IP (SRF) is connected to, are transparent to the procedures. + +Note also that the SCP must again correlate two transactions. + +In Figure 40, the procedural scenarios can be mapped as follows: + +| Procedure name | Operations | Protocol flows | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| Assist preamble | EstablishTemporaryConnection
If DSS 1 used:
Setup
AssistRequestInstructions
ConnectToResource
Setup
ResetTimer
If SS No. 7 used:
IAM
AssistRequestInstructions
ConnectToResource
Setup
ResetTimer | A

E
C
B
G
A

E
C
B
G
A | +| User interaction | PlayAnnouncement/
PromptAndCollectUserInformation
SpecializedResourceReport/RR for
PromptAndCollectUserInformation | B then G

H then C | +| SCF initiated disconnect | SpecializedResourceReport/RR for
PromptAndCollectUserInformation
DisconnectForwardConnection
If DSS 1 used:
Disconnect
If SS No. 7 used:
Release | H then C

A

E and G (intra-SSP bearer ctrl)

E and G (intra-SSP bearer ctrl) | + +Note that the assisting SSP case shown in Figure 40 can be generalized to cover both the case where the SRF is embedded in assisting SSP (as shown), and the case where the SRF is locally connected to assisting SSP. In this latter case, the SRF communication (protocol flows B, C, G and H) would conform to the physical scenario shown in Figure 38. + +The service handoff scenario can similarly be viewed as a sequence consisting of an IN service to route a call from one SSP to another, followed by any one of the previously described physical user interaction scenarios. For describing this scenario Figure 40 can be used also. + +#### 3.1.3.5.4.1 Message sequences for service assist + +The following subclause provides additional details on the message sequences for the service assist procedure in Figure 40: + +- 1) The SCP, during the processing of a request for instruction, determines that resources remote from the initiating SSP are required and that call processing will continue from the initiating SSP after the remote resources have been used (e.g. the call will be completed to a destination address after information is collected from the calling party). An EstablishTemporaryConnection operation containing the address of the assisting SSP (for routing the call), the ScfID and the CorrelationID (both used for the assisting SSP to establish communication back to the SCP) is sent to the initiating SSP. The EstablishTemporaryConnection is used instead of a regular Connect operation because of the nature of the connection to the assisting SSP. The initiating SSP must be aware that the SCP will ask it to continue in the processing of the call at some point in the future. + +NOTE 1 – The ScfID and CorrelationID may be included in the routing address of the assisting SSP. + +*Protocol Flow A* + +- 2) The initiating SSP routes the call to the assisting SSP. The ScfID and CorrelationID are sent to the assisting SSP. Existing in-band signalling and SS No. 7 information elements (e.g. routing number) could be used to transport this information. The transport mechanism used to send this information between SSPs is independent of the service assist control procedures between the SCF and SSF. + +*Protocol Flow E* + +- 3) The assisting SSP uses an AssistRequestInstructions operation to establish communication with the SCP. The CorrelationID is sent in the AssistRequestInstructions to allow the SCP to correlate two transactions. + +*Protocol Flow C* + +- 4) The SCP sends instructions to the assisting SSP based on service logic control. + +*Protocol Flow B* + +- 5) The SCP may need to generate reset timer events to the initiating SSP so that it does not time out the call. + +*Protocol Flow A* + +NOTE 2 – The usage of ResetTimer operation is optional. + +- 6) When resource functions have been completed, a DisconnectForwardConnection operation is sent to the initiating SSP. This indicates, that the temporary connection to the assisting SSP has to be disconnected. + +*Protocol Flow A* + +- 7) The initiating SSP sends a message via bearer control signalling to the assisting SSP to close the "assist" transaction. + +*Protocol Flow E* + +- 8) The call control returns to the initiating SSP. + +#### **3.1.3.5.4.2 Message sequences for handoff** + +The following subclause outlines message sequences for the handoff procedure using the protocol flows shown in Figure 40: + +- 1) The SCP, during the processing of a request for instruction, determines that resources remote from the initiating SSP are required and that call processing need not continue from the initiating SSP after the remote resources have been used (e.g. a terminating announcement will be played). A Connect operation containing the address of the assisting SSP (for routing the call), the ScfID and the CorrelationID (both used for the assisting SSP to establish communication back to the SCP) is sent to the initiating SSP. + +NOTE – The ScfID and CorrelationID may be included in the routing address of the assisting SSP. + +*Protocol Flow A* + +- 2) The initiating SSP routes the call to the assisting SSP. The ScfID and CorrelationID are sent to the assisting SSP. Existing in-band signalling and SS No. 7 information elements (e.g. routing number) could be used to transport this information. The transport mechanism used to send this information between SSPs is independent of the service assist control procedures between the SCF and SSF. + +*Protocol Flow E* + +- 3) The assisting SSP uses an AssistRequestInstructions operation to establish communication with the SCP. The CorrelationID is sent in the AssistRequestInstructions to allow the SCP to correlate two transactions. The AssistRequestInstructions is used instead of a regular request instruction (InitialDP or DP-specific operation) because the SCP must associate the AssistRequestInstructions from the assisting SSP-IP with an already active dialogue the SCP has with another SSP. + +#### *Protocol Flow C* + +- 4) The SCP sends instructions to the assisting SSP based on service logic control. + +#### *Protocol Flow B* + +- 5) The call control remains at the assisting SSP. + +The same service assist and handoff procedures can be reused for a direct link to an IP in this and future capability sets. + +### **3.1.4 SDF application entity procedures** + +#### **3.1.4.1 General** + +This subclause provides the definition of the SDF Application Entity (AE) procedures related to the SDF-SCF interface. The procedures are based on the use of Signalling System No. 7 (SS No. 7). + +Other capabilities may be supported in an implementation-dependent manner in the SCP, SDP, SSP, AD or SN. + +The AE, following the architecture defined in Recommendations Q.700, Q.771 and Q.1400, includes Transaction Capabilities Application Part (TCAP) and one or more ASEs called TC-users, which are based on the Directory (X.500-Series Recommendations). The following subclauses define the TC-user ASE and SACF & MACF rules, which interface with TCAP using the primitives specified in Recommendation Q.771. + +The procedure may equally be used with other signalling message transport systems supporting the application layer structures defined. + +In case interpretations for the application entity procedures defined in the following differ from detailed procedures and the rules for using of TCAP service, the statements and rules contained in the detailed subclauses 3.3 and 2.2.2.2 shall be followed. + +#### **3.1.4.2 Model and interfaces** + +The functional model of the AE-SDF is shown in Figure 41; the ASEs interface to TCAP to communicate with the SCF, and interface to the maintenance functions. The scope of this Recommendation is limited to the shaded area in Figure 41. + +The interfaces shown in Figure 41 use the TC-user ASE primitives specified in Recommendation Q.771 [interface 1)] and N-Primitives specified in Recommendation Q.711 [interface 2)]. The operations and parameters of Intelligent Network Application Protocol (INAP) are defined in clause 2. + +An instance of SDF-FSM may be created if IN call handling is received from the SCF. + +The SDF-FSM handles the interaction with the SCF-FSM. + +#### **3.1.4.3 Relationship between the SDF-FSM and the maintenance function** + +The primitive interface between the SDF-FSM and the maintenance functions is an internal interface and is not subject for standardization in IN CS-1. + +#### **3.1.4.4 SDF state transition model** + +As far as IN CS-1 is concerned, the SDF's job is to (synchronously) respond to every request from the SCF after the Bind procedure. The respective Finite State Machine (FSM) is depicted in Figure 42. + +Each state is discussed in one of the following subclauses. + +General rules applicable to more than one state are as follows: + +In any state, if the dialogue with the SCF is terminated, then the SDF-FSM returns to **Idle** state after ensuring that any resources allocated to the call have been de-allocated. + +![Functional model of SDF-AE diagram showing nested layers: Application process invocation (Maintenance functions) containing Service data function, SAO, ASE, TCAP, and SDF-FSM, which in turn contains AEI. The entire structure is connected to an external SCCP layer via a vertical line labeled 'b)'.](40d0aaaa3afa0a9fabe637941ca250bb_img.jpg) + +The diagram illustrates the functional model of SDF-AE. It consists of several nested components: + + +- Application process invocation (Maintenance functions)**: The outermost container. +- Service data function (SDF)**: Represented by an oval at the top. +- SAO (Single association object)**: A vertical rectangle containing the letters S, A, C, F stacked vertically. +- ASE (Association entity)**: Two rectangular blocks connected to the SAO. +- TCAP**: A rectangular block connected to the SAO via a line labeled 'a)'. +- SDF-FSM (Service data function finite state machine)**: A large rectangular area containing the ASEs and TCAP. +- AEI (Application entity invocation)**: Located within the SDF-FSM area. + + A vertical line extends from the bottom of the SAO, labeled 'b)', down to a separate box labeled **SCCP**. + +Functional model of SDF-AE diagram showing nested layers: Application process invocation (Maintenance functions) containing Service data function, SAO, ASE, TCAP, and SDF-FSM, which in turn contains AEI. The entire structure is connected to an external SCCP layer via a vertical line labeled 'b)'. + +T1147040-92/d42 + +AEI Application entity invocation + SDF Service data function + FSM Finite state machine + SACF Single association control function + SAO Single association object + +a) TC-primitives or Q.932-primitives. + b) N-primitives. + +NOTE – The SDF FSM includes several finite state machines. + +FIGURE 41/Q.1218 +**Functional model of SDF-AE** + +![State transition diagram for the SDF-FSM showing three states: 1. Idle, 2. Bind Pending, and 3. SCF Bound. Transitions are triggered by events (E1-E7).](b5ce6d659e1431289c2e79b01bf38a15_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 1. Idle + 1. Idle --> 2. Bind Pending : (E1) Bind_from_SCF + 2. Bind Pending --> 2. Bind Pending : (E3) Request_from_SCF + 2. Bind Pending --> 1. Idle : (e2) Bind_Error + 2. Bind Pending --> 3. SCF Bound : (e4) Bind_Successful + 3. SCF Bound --> 1. Idle : (E5) Unbind_from_SCF + 3. SCF Bound --> 3. SCF Bound : (e6) Response_to_SCF + 3. SCF Bound --> 3. SCF Bound : (E7) Request_from_SCF + +``` + +T1169210-94/d43 + +State transition diagram for the SDF-FSM showing three states: 1. Idle, 2. Bind Pending, and 3. SCF Bound. Transitions are triggered by events (E1-E7). + +FIGURE 42/Q.1218 +The SDF-FSM + +#### 3.1.4.4.1 State 1 – "Idle" + +The only event accepted in this state is: + +- (E1) Bind\_from\_SCF – This is an external event caused by the reception of Bind operation from the SCF. This event causes a transition out of this state to State 2, **Bind Pending**. + +#### 3.1.4.4.2 State 2 – "Bind Pending" + +In this state, a Bind request has been received from the SCF. The SDF is performing the SCF access control procedures behind the Bind operation (e.g. access authentication). There may also be a case such that the Bind operation is a dummy one. Then, the access authentication is not required. Three events are considered in this state: + +- (e2) Bind\_Error – This is an internal event, caused by the failure of the Bind operation previously issued to the SDF. This event causes a transition out of this state to State 1, **Idle** and a Bind error is returned to the invoking SCF; +- (E3) Request\_from\_SCF – This is an external event, caused by the reception of operations before the result from the Bind operation is determined. The SDSM remains in the same state; and +- (e4) Bind\_Successful – This is an internal event, caused by the successful completion of the Bind operation previously issued to the SDF. This event causes a transition out of this state to State 3, **SCF Bound**. + +#### 3.1.4.4.3 State 3 – "SCF Bound" + +In this state, the access of the SCF to the SDF was authorized and operations coming from the SCF are accepted. Besides waiting for requests from the SCF, the SDF can send in that state responses to previously issued operations. Three events are considered in this state: + +- (E5) Unbind\_from\_SCF – This is an external event, caused by the reception of the Unbind operation from the SCF. The SCF-SDF association is ended and all associated resources are released. This event causes a transition out of this state to State 1, **Idle**; + +- (e6) Response\_to\_SCF – This is an internal event, caused by the completion of the operations previously issued by the SCF. Responses are sent to the SCF. The SDSM remains in the same state; and +- (E7) Request\_from\_SCF – This is an external event, caused by the reception of a request from the SCF to the SDF. The SDSM remains in the same state. + +In addition to this finite state machine, an SDL description of SDSM is shown in the Annex B. + +## 3.2 Error procedures + +This subclause defines the generic error procedures for the IN CS-1 INAP. The error procedure descriptions have been divided in two subclauses, 3.2.1 listing the errors related to INAP operations and 3.2.2 listing the errors related to error conditions in the different FEs which are not directly related to the INAP operations. + +### 3.2.1 Operation related error procedures + +The following subclauses define the generic error handling for the operation related errors. The errors are defined as operation errors in 2.1.2. The TCAP services which are used for reporting operation errors are described in 3.4. + +Errors which have a specific procedure for an operation are described in 3.3 with the detailed procedure of the related operation. + +All errors, which can be detected by the ASN.1 decoder, already may be detected during the decoding of the TCAP message and indicated by the TC error indication "MistypedParameter" in the TC-U-Reject. + +#### 3.2.1.1 Attribute error + +##### 3.2.1.1.1 General description + +###### 3.2.1.1.1.1 Error description + +This error is sent by the SDF to the SCF to report an attribute related problem. The conditions under which an attribute error is to be issued are defined in 12.4/X.511 (1993). + +###### 3.2.1.1.1.2 Argument description + +The attribute error parameter and problem codes are specified in 12.4/X.511 (1993). + +###### 3.2.1.1.2 Operations SCF-> SDF + +- Search; +- Add Entry; +- Modify Entry. + +#### Procedure at Invoking Entity (SCF) + +##### A) Sending Operation + +| | | | +|----------------|--------------|------------------------------| +| Precondition: | SCSM state 4 | SDF Bound or | +| | SCSM state 2 | Wait for subsequent requests | +| Postcondition: | SCSM state 4 | SDF Bound or | +| | SCSM state 2 | Wait for subsequent requests | + +##### B) Receiving Error + +| | | | +|----------------|--------------|-----------| +| Precondition: | SCSM state 4 | SDF Bound | +| Postcondition: | SCSM state 4 | SDF Bound | + +Error Procedure is dependent on the Service Logic. If the SCF is able to change the request, it can do another SDF query, otherwise the service processing should be terminated. + +### Procedure at Responding Entity (SDF) + +#### A) Receiving Operation + +| | | | +|----------------|-----------------|-----------| +| Precondition: | SDF-FSM state 3 | SCF Bound | +| Postcondition: | SDF-FSM state 3 | SCF Bound | + +#### B) Returning Error + +| | | | +|----------------|-----------------|-----------| +| Precondition: | SDF-FSM state 3 | SCF Bound | +| Postcondition: | SDF-FSM state 3 | SCF Bound | + +The SDF could not perform the operation due to an attribute problem and therefore sends an Attribute error to the SCF. After returning the error, no further error treatment is performed. + +### 3.2.1.2 Cancelled + +#### 3.2.1.2.1 General description + +##### 3.2.1.2.1.1 Error description + +The Error "Cancelled" gives an indication to the SCF that the cancellation, as it was requested by the SCF, of a specific Operation, has been successful. The SCF is only able to cancel certain predefined SCF-->SRF Operations. + +##### 3.2.1.2.2 Operations SCF->SRF + +- PlayAnnouncement +- PromptAndCollectUserInfoInformation + +### Procedures at Invoking Entity (SCF) + +#### A) Sending Cancel + +| | | | +|----------------|----------------|------------------------------------| +| Precondition: | SCSM state 4.1 | Waiting for Response from the SRF. | +| Postcondition: | SCSM state 4.1 | Waiting for Response from the SRF. | + +The SCF sends a Cancel after a Play Announcement or PromptAndCollectUserInfoInformation has been sent. The SCF remains in the same state. + +#### B) Receiving Cancelled Error + +| | | | +|----------------|----------------|--------------------------| +| Precondition: | SCSM state any | Service Logic dependent. | +| Postcondition: | SCSM state any | Service Logic dependent. | + +After sending a Cancel operation the Service Logic may continue (e.g. sending more PlayAnnouncement or PromptAndCollectUserInfoInformation or a DisconnectForwardConnection). The Cancelled Error can therefore be received in any state. The treatment is Service Logic dependent. + +### Procedures at Responding Entity (SRF) + +#### A) Receiving Cancel + +| | | | +|----------------|--------------|-------------------| +| Precondition: | SRSM state 3 | User Interaction. | +| Postcondition: | SRSM state 3 | User Interaction. | + +The indicated PlayAnnouncement or PromptAndCollectUserInfoInformation is terminated if it is presently executing or deleted from the buffer. If the indicated PlayAnnouncement or PromptAndCollectUserInfoInformation is already executed this causes a failure ("CancelFailed"). + +#### B) Sending Cancel Error + +| | | | +|----------------|--------------|-------------------| +| Precondition: | SRSM state 3 | User Interaction. | +| Postcondition: | SRSM state 3 | User Interaction. | + +After returning the "Cancelled" Error the SRF stays in the same state. The execution of the indicated PlayAnnouncement or PromptAndCollectUserInfoInformation is aborted, i.e. the SRF remains connected and the next PlayAnnouncement or PromptAndCollectUserInfoInformation is executed if available. + +### 3.2.1.3 CancelFailed + +#### 3.2.1.3.1 General description + +##### 3.2.1.3.1.1 Error description + +This Error is returned by Cancel if the cancelling of an Operation, as requested by the SCF, was not successful. Possible failure reasons are: + +- 1) unknownOperation – When the InvokeID of the operation to cancel is not known to SRF (this may also happen in case the operation has already been completed). +- 2) tooLate – When the InvokeID is known but the execution of the operation is in a state that it cannot be cancelled anymore. For instance, the announcement is finished but the SpecializedResourceReport has not been sent to the SCF yet. The conditions for the occurrence of failure reason "tooLate" may be implementation dependent. +- 3) operationNotCancellable, when the InvokeID points to an Operation that the SCF is not allowed to cancel. + +##### 3.2.1.3.1.2 Argument description + +``` +PARAMETER SEQUENCE { + problem [0] ENUMERATED { + unknown operation (0), + tooLate (1), + operationNotCancellable (2) }, + operation [1] InvokeID +} +-- The operation failed to be cancelled. +``` + +##### 3.2.1.3.2 Operations SCF → SSF + +- CancelStatusReportRequest; +- Cancel. + +##### 3.2.1.3.3 Operations SCF → SRF + +- Cancel. + +#### Procedures at Invoking Entity (SCF) + +##### A) Sending Cancel + +| | | | +|----------------|----------------|------------------------------------| +| Precondition: | SCSM state 4.1 | Waiting for Response from the SRF. | +| Postcondition: | SCSM state 4.1 | Waiting for Response from the SRF. | + +The SCF sends a Cancel after a Play Announcement or PromptAndCollectUserInfoInformation has been sent. The SCF remains in the same state. + +##### B) Receiving CancelFailed Error + +| | | | +|----------------|----------------|--------------------------| +| Precondition: | SCSM state any | Service Logic dependent. | +| Postcondition: | SCSM state any | Service Logic dependent. | + +After sending a Cancel operation the Service Logic may continue (e.g. sending another PlayAnnouncement or PromptAndCollectUserInfoInformation or a DisconnectForwardConnection). The CancelFailed Error can therefore be received in any state. The treatment is Service Logic dependent. + +#### Procedures at Responding Entity (SRF) + +##### A) Receiving Cancel. However, the indicated PlayAnnouncement or PromptAndCollectUserInfoInformation is not known, or already executed. This causes a failure, CancelFailed. + +| | | | +|----------------|--------------|-------------------| +| Precondition: | SRSM state 3 | User Interaction. | +| Postcondition: | SRSM state 3 | User Interaction. | +| or | SRSM state 1 | Idle. | + +- B) Sending CancelFailed Error +- | | | | +|----------------|--------------|-------------------| +| Precondition: | SRSM state 3 | User Interaction. | +| or | SRSM state 1 | Idle. | +| Postcondition: | SRSM state 3 | User Interaction. | +| or | SRSM state 1 | Idle. | + +After returning the CancelFailed the SRF stays in the same state. + +### 3.2.1.4 ETCFailed + +#### 3.2.1.4.1 General description + +##### 3.2.1.4.1.1 Error description + +ETCFailed is an error from SSF to SCF, indicating the fact that the establishment of a temporary connection to an assisting SSF or SRF was not successful (e.g. receiving a "Backwards Release" after sending an IAM). + +##### 3.2.1.4.2 Operations SCF → SSF + +- EstablishTemporaryConnection. + +#### Procedures at Invoking Entity (SCF) + +- A) SCF sends EstablishTemporaryConnection to SSF +- | | | | +|----------------|----------------|----------------------------------------| +| Precondition: | SCSM state 3.1 | Determine Mode. | +| Postcondition: | SCSM state 3.2 | Waiting for AssistRequestInstructions. | +- B) SCF receives ETCFailed Error from SSF +- | | | | +|----------------|----------------|----------------------------------------| +| Precondition: | SCSM state 3.2 | Waiting for AssistRequestInstructions. | +| Postcondition: | SCSM state 2.1 | Preparing SSF Instructions. | + +Error handling depends on the Service Logic, e.g. selecting another SRF or continue the processing of the call. + +#### Procedures at Responding Entity (SSF) + +A SSF receives EstablishTemporaryConnection from a SCF but the establishment of the connection fails, results in returning an ETCFailed Error to the SCF. + +| | | | +|----------------|-----------------|---------------------------| +| Precondition: | SSF-FSM state c | Waiting for Instructions. | +| Postcondition: | SSF-FSM state c | Waiting for Instructions. | + +No further Error treatment. + +### 3.2.1.5 ImproperCallerResponse + +#### 3.2.1.5.1 General description + +##### 3.2.1.5.1.1 Error description + +The format of the user input has been checked by the SRF and does not correspond to the required format as it was defined in the initiating PromptAndCollectUserInformation Operation. + +##### 3.2.1.5.2 Operations SCF → SRF + +- PromptAndCollectUserInformation. + +#### Procedures at Invoking Entity (SCF) + +- A) SCF sends PromptAndCollectUserInformation to SRF +- | | | | +|---------------|----------------|---------------------------------------------------------------------------------------| +| Precondition: | SCSM state 3.1 | Determine Mode; PromptAndCollectUserInformation will accompany the ConnectToResource. | +|---------------|----------------|---------------------------------------------------------------------------------------| + +| | | | +|-------------------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------| +| or | SCSM state 3.2 | Waiting for AssistRequestInstructions; after EstablishTemporaryConnection. | +| or | SCSM state 4.1 | Waiting for Response from the SRF; if more PlayAnnouncements or PromptAndCollectUser-
Informations are active. | +| Postcondition: | SCSM state 4.1 | Waiting for Response from the SRF. | +| B) SCF receives ImproperCallerResponse Error from SRF | | | +| Precondition: | SCSM state 4.1 | Waiting for Response from the SRF. | +| Postcondition: | SCSM state 4.1 | Waiting for Response from the SRF. | + +Error treatment depends on Service Logic. A SCF can initiate new User Interaction or force a Disconnect (to SSF). + +### Procedures at Responding Entity (SRF) + +| | | | +|-----------------------------------------------------------------------------------|--------------|-------------------| +| A) SRF receives PromptAndCollectUserInformation | | | +| Precondition: | SRSM state 2 | Connected. | +| or | SRSM state 3 | User Interaction. | +| Postcondition: | SRSM state 3 | User Interaction. | +| B) Response from caller is not correct, SRF returns ImproperCallerResponse to SCF | | | +| Precondition: | SRSM state 3 | User Interaction. | +| Postcondition: | SRSM state 3 | User Interaction. | + +SRF waits for a new Operation from SCF. This may be a new PromptAndCollectUserInformation or PlayAnnouncement. + +#### 3.2.1.6 MissingCustomerRecord + +##### 3.2.1.6.1 General description + +###### 3.2.1.6.1.1 Error description + +The Service Logic Program could not be found in the SCF, because the required customer record does not exist, or the requested Service Logic Program Instance, indicated by the CorrelationID in "AssistRequestInstructions" does not exist anymore. These two cases should be distinguished as two different error situations, because the error procedure shows that the occurrence of the MissingCustomerRecord error is reported to the maintenance function, but the report to the maintenance function for the occurrence of the former case should be optional because it occurs not only in extraordinary situation but in ordinary situation. For example, the former may occur when the end user dials a missing free-phone number. + +###### 3.2.1.6.2 Operations SSF → SCF + +- AnalysedInformation; +- AssistRequestInstructions; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- ODisconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- TAnswer; +- TBusy; +- TDisconnect; +- TermAttemptAuthorized; +- TMidCall; +- TNoAnswer. + +### Procedures at Invoking Entity (SSF) + +#### A) Sending Operation + +| | | | +|----------------|------------------|-------------------------------------------------------| +| Precondition: | SSF-FSM state b | Trigger processing. | +| or | SSF-FSM state b' | Waiting for Instructions; in case of assist/hand-off. | +| Postcondition: | SSF-FSM state c | Waiting for Instructions. | +| or | SSF-FSM state b' | Waiting for Instructions; in case of assist/hand-off. | + +#### B) SSF receives Error "MissingCustomerRecord" + +| | | | +|----------------|------------------|-------------------------------------------------------| +| Precondition: | SSF-FSM state c | Waiting for Instructions. | +| or | SSF-FSM state b' | Waiting for Instructions; in case of assist/hand-off. | +| Postcondition: | SSF-FSM state a | Idle. | +| or | SSF-FSM state a' | Idle; in case of assist/hand-off. | + +The CCF routes the call if necessary (e.g. default routing to a terminating announcement). + +### Procedures at Responding Entity (SCF) + +| | | | +|----------------|-------------------|---------------------------------------------------------------------------------| +| Precondition: | 1) SCSM | Appropriate state. | +| | 2) SCSM | Operation received, appropriate event occurred. | +| Postcondition: | 1) SCSM state 1 | Idle; in case of all operations listed above, except AssistRequestInstructions. | +| | 2) SCSM state 2.1 | Preparing SSF instructions; for AssistRequest-Instructions. | + +The SCSM detects that the required Service Logic Program does not exist. The Service Logic Program Instance may not exist anymore (e.g. in case of the operation AssistRequestInstructions), or the Service Logic Program may have never existed at all (i.e. the customer record in the SCF does not exist, e.g. in case of TDPs a Service Logic Program is attempted to be invoked). The Error parameter MissingCustomerRecord is used to inform the invoking entity of this situation. The maintenance functions are informed (however, it is optional for the TDP operation case). + +#### 3.2.1.6.3 Operations SRF → SCF + +- AssistRequestInstructions. + +### Procedures at Invoking Entity (SRF) + +#### A) Sending Operation + +| | | | +|----------------|--------------|------------| +| Precondition: | SRSM state 2 | Connected. | +| Postcondition: | SRSM state 2 | Connected. | + +#### B) SRF receives Error "MissingCustomerRecord" + +| | | | +|----------------|--------------|------------| +| Precondition: | SRSM state 2 | Connected. | +| Postcondition: | SRSM state 1 | Idle. | + +SRF initiated Disconnect. + +### Procedures at Responding Entity (SCF) + +The SCSM detects that the required Service Logic Program does not exist (anymore). The establishment of a connection between the SSF and the SRF took too long or the correlationID was invalid. In both cases the requested Service Logic Program cannot be found. The Error parameter MissingCustomerRecord is used to inform the invoking entity of this situation. The maintenance functions are informed. + +### 3.2.1.7 MissingParameter + +#### 3.2.1.7.1 General description + +##### 3.2.1.7.1.1 Error description + +There is an Error in the received Operation argument. The responding entity cannot start to process the requested Operation because the argument is incorrect: a mandatory parameter (the application shall always return this error in case it is not detected by the ASN.1 decoder) or an expected optional parameter which is essential for the application is not included in the Operation argument. + +#### 3.2.1.7.2 Operations SCF → SSF + +##### Non Call Associated + +- ActivateServiceFiltering. + +##### Call Associated/Non Call Processing + +- ApplyCharging; +- CallInformationRequest; +- Cancel; +- CancelStatusReportRequest; +- FurnishChargingInformation; +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport; +- RequestNotificationChargingEvent; +- RequestReportBCSMEEvent; +- ResetTimer; +- SendChargingInformation. + +##### Call Associated/Call Processing + +- AnalyseInformation; +- CollectInformation; +- Connect; +- ConnectToResource; +- EstablishTemporaryConnection; +- HoldCallInNetwork; +- InitiateCallAttempt; +- SelectFacility; +- SelectRoute. + +#### Procedures at Invoking Entity (SCF) + +##### A) Sending Operation + +| | | | +|----------------|------|-----------------------------------------------------------------------------------------| +| Precondition: | SCSM | Any state in which the above Call associated operations can be transferred. | +| | SCME | Any state in which the above Non call associated operations can be transferred. | +| Postcondition: | SCSM | Any state as result of the transfer of any of the above operations. | +| | SCME | Any state as result of the transfer of any of the above Non call associated operations. | + +##### B) SCF receives Error "MissingParameter" + +| | | | +|----------------|------|-----------------------------------------------------------------------------------------| +| Precondition: | SCSM | Any state as result of the transfer of any of the above Call associated operations. | +| | SCME | Any state as result of the transfer of any of the above Non call associated operations. | +| Postcondition: | SCSM | Transition to the initial state (i.e. before sending the erroneous operation). | +| | SCME | Transition to the initial state (i.e. before sending the erroneous operation). | + +The Service Logic and maintenance functions are informed. Further treatment of the call is dependent on Service Logic. + +### Procedures at Responding Entity (SSF) + +| | | | +|----------------|------------|----------------------------------------------------------------------------------| +| Precondition: | 1) SSF-FSM | Appropriate state. | +| | 2) SSF-FSM | Call associated operation received, appropriate event occurred. | +| | 3) SSME | Appropriate state. | +| | 4) SSME | Non call associated operation received, appropriate event. | +| Postcondition: | 1) SSF-FSM | Transition to the same state. | +| | 2) SSME | Transition to the initial state (i.e. before receiving the erroneous operation). | + +The SSF-FSM detects the error in the received operation. The Error parameter is returned to inform the SCF of this situation. + +### 3.2.1.7.3 Operations SSF → SCF + +- AnalysedInformation; +- ApplyChargingReport; +- AssistRequestInstructions; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- ODisconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- TAnswer; +- TBusy; +- TDisconnect; +- TermAttemptAuthorized; +- TMidCall; +- TNoAnswer. + +### Procedures at Invoking Entity (SSF) + +#### A) Sending Operation + +| | | | +|----------------|---------|---------------------------------------------------------------------| +| Precondition: | SSF-FSM | Any state in which the above operations can be transferred. | +| Postcondition: | SSF-FSM | Any state as result of the transfer of any of the above operations. | + +#### B) SSF receives Error "MissingParameter" + +| | | | +|----------------|-----------------|---------------------------------------------------------------------| +| Precondition: | SSF-FSM | Any state as result of the transfer of any of the above operations. | +| Postcondition: | SSF-FSM state a | Idle. | + +After receiving this Error, the SSF-FSM returns to the state Idle. The CCF routes the call if necessary (default routing to a terminating announcement). If the call is already established (i.e. mid-call trigger or ApplyChargingReport), the CCF may maintain the call or disconnect it. The choice between these two options is network operator specific. In case of an assisting SSF, the temporary connection is released by the assisting SSF. + +### Procedures at Responding Entity (SCF) + +| | | | +|----------------|-------------------|--------------------------------------------------------------------------------| +| Precondition: | 1) SCSM | Appropriate state. | +| | 2) SCSM | Operation received, appropriate event occurred. | +| Postcondition: | 1) SCSM state 1 | Idle; in case of any operation listed above, except AssistRequestInstructions. | +| or | 2) SCSM state 2.1 | Preparing SSF Instructions; in case of AssistRequestInstructions. | + +The SCSM detects the erroneous situation. The Error parameter is used to inform the SSF of this situation. The Service Logic and maintenance functions are informed. + +#### 3.2.1.7.4 Operations SCF → SRF + +- PlayAnnouncement; +- PromptAndCollectUserInfoInformation; +- Cancel. + +### Procedures at Invoking Entity (SCF) + +#### A) Sending Operation + +| | | | +|----------------|----------------|-----------------------------------------------------------------------------------------------------------------------| +| Precondition: | SCSM state 3.1 | Determine Mode; PromptAndCollectUserInfoInformation or PlayAnnouncement will accompany the ConnectTo-Resource. | +| or | SCSM state 3.2 | Waiting for AssistRequestInstructions; after EstablishTemporaryConnection. | +| or | SCSM state 4.1 | Waiting for Response from the SRF; if more PlayAnnouncements or PromptAndCollectUserInfoInformations are outstanding. | +| Postcondition: | SCSM state 4.1 | Waiting for Response from the SRF. | + +#### B) Receiving Error + +| | | | +|----------------|----------------|------------------------------------| +| Precondition: | SCSM state 4.1 | Waiting for Response from the SRF. | +| Postcondition: | SCSM state 4.1 | Waiting for Response from the SRF. | + +Error treatment depends on Service logic. SCF can initiate new User Interaction or force Disconnect (to SSF). + +### Procedures at Responding Entity (SRF) + +| | | | +|----------------|--------------|-------------------| +| Precondition: | SRSM state 2 | Connected. | +| or | SRSM state 3 | User Interaction. | +| Postcondition: | SRSM state 3 | User Interaction. | + +The SRSM detects that a required parameter is not present in the Operation argument. The Error parameter MissingParameter is used to inform the SCF of this situation. The SCF should take the appropriate actions to treat this error. + +#### 3.2.1.7.5 Operations SRF → SCF + +- AssistRequestInstructions. + +### Procedures at Invoking Entity (SRF) + +#### A) Sending Operation + +| | | | +|----------------|--------------|------------| +| Precondition: | SRSM state 2 | Connected. | +| Postcondition: | SRSM state 2 | Connected. | + +#### B) Receiving Error + +| | | | +|----------------|--------------|------------| +| Precondition: | SRSM state 2 | Connected. | +| Postcondition: | SRSM state 1 | Idle. | + +### **Procedures at Responding Entity (SCF)** + +| | | | +|----------------|----------------|----------------------------------------| +| Precondition: | SCSM state 3.2 | Waiting for AssistRequestInstructions. | +| Postcondition: | SCSM state 2.1 | Preparing SSF instructions. | + +The SCSM detects the error in the received operation. The Error parameter is used to inform the SRF of this situation. The Service Logic and maintenance functions are informed. The SCF might try another SRF, route the call or release the call (Service Logic dependent). + +#### **3.2.1.8 Name error** + +##### **3.2.1.8.1 General description** + +###### **3.2.1.8.1.1 Error description** + +This error is sent by the SDF to the SCF to report a problem related to the name of the object. The conditions under which an attribute error is to be issued are defined in 12.5/X.511 (1993). + +###### **3.2.1.8.1.2 Argument description** + +The name error parameter and problem codes are specified in 12.5/X.511 (1993). + +##### **3.2.1.8.2 Operations SCF → SDF** + +- Search; +- Add Entry; +- Remove Entry; +- Modify Entry. + +### **Procedure at Invoking Entity (SCF)** + +#### **A) Sending Operation** + +| | | | +|----------------|--------------|-------------------------------| +| Precondition: | SCSM state 4 | SDF Bound or | +| | SCSM state 2 | Wait for subsequent requests. | +| Postcondition: | SCSM state 4 | SDF Bound or | +| | SCSM state 2 | Wait for subsequent requests. | + +#### **B) Receiving Error** + +| | | | +|----------------|--------------|------------| +| Precondition: | SCSM state 4 | SDF Bound. | +| Postcondition: | SCSM state 4 | SDF Bound. | + +Error Procedure is dependent on the Service Logic. If the SCF is able to change the request, it can do another SDF query, otherwise the service processing should be terminated. + +### **Procedure at Responding Entity (SDF)** + +#### **A) Receiving Operation** + +| | | | +|----------------|-----------------|------------| +| Precondition: | SDF-FSM state 3 | SCF Bound. | +| Postcondition: | SDF-FSM state 3 | SCF Bound. | + +#### **B) Returning Error** + +| | | | +|----------------|-----------------|------------| +| Precondition: | SDF-FSM state 3 | SCF Bound. | +| Postcondition: | SDF-FSM state 3 | SCF Bound. | + +The SDF could not perform the operation due to a name problem and therefore sends a Name error to the SCF. After returning the error, no further error treatment is performed. + +### 3.2.1.9 ParameterOutOfRange + +#### 3.2.1.9.1 General description + +##### 3.2.1.9.1.1 Error description + +The responding entity cannot start the processing of the requested Operation because an Error in a parameter of the Operation argument is detected: a parameter value is out of range. This error is applied for the following two cases (when the error is determined by the application): + +- 1) For the parameter which type is defined with the range of its size, such as INTEGER(x..y), SEQUENCE SIZE(x..y) OF Type. This error is applied when the parameter value is z or the parameter size is z where $z < x$ or $z > y$ . +- 2) For the parameter which type is defined as list of ENUMERATED value, the ParameterOutOfRange error is applied when the parameter value is not equal to any of the ENUMERATED values in the list. + +#### 3.2.1.9.2 Operations SCF → SSF + +##### Non Call Associated + +- ActivateServiceFiltering. + +##### Call Associated/Non Call Processing + +- ApplyCharging; +- CallInformationRequest; +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport; +- SendChargingInformation. + +##### Call Associated/Call Processing + +- AnalyzeInformation; +- CollectInformation +- Connect; +- InitiateCallAttempt; +- RequestNotificationChargingEvent; +- RequestReportBCSMEEvent; +- ResetTimer; +- SelectFacility; +- SelectRoute. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +#### 3.2.1.9.3 Operations SSF → SCF + +- AnalyzedInformation; +- ApplyChargingReport; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- Disconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- TAnswer; +- TCalledPartyBusy +- TDisconnect; +- TermAttemptAuthorized +- TMidCall; +- TNoAnswer. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +#### 3.2.1.9.4 Operations SCF → SRF + +- PlayAnnouncement; +- PromptAndCollectUserInfoInformation. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +#### 3.2.1.10 RequestedInfoError + +##### 3.2.1.10.1 General description + +###### 3.2.1.10.1.1 Error description + +The RequestedInfoError is an immediate response to the CallInformationRequest operation, indicating that the requested information is not known to the SSF or is not available. RequestedInfoError is used when a specific SSF-CCF cannot offer the information specified with RequestedInformationType but there exists other SSF-CCF that can offer the information. + +###### 3.2.1.10.1.2 Argument description + +**PARAMETER ENUMERATED {** +    **unknownRequestedInfo (1),** +    **requestedInfoNotAvailable (2)** +    -- *other values FFS* +**}** + +##### 3.2.1.10.2 Operations SCF → SSF + +- CallInformationRequest. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +#### 3.2.1.11 Service error + +##### 3.2.1.11.1 General description + +###### 3.2.1.11.1.1 Error description + +This error is sent by the SDF to the SCF to report a problem related to the provision of the service. The conditions under which a service error is to be issued are defined in 12.8/X.511 (1993). + +###### 3.2.1.11.1.2 Argument description + +The Service error parameter and problem codes are specified in 12.8/X.511 (1993). + +##### 3.2.1.11.2 Operations SCF → SDF + +- Bind; +- Search; +- Add Entry; +- Remove Entry; +- Modify Entry. + +#### Procedure at Invoking Entity (SCF) + +##### A) Sending Operation + +| | | | +|---------------|--------------|-------------------------------------------------------------------| +| Precondition: | SCSM state 1 | Idle (in case of Bind). | +| or | SCSM state 2 | Wait for subsequent requests (in case of operations except Bind). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | + +| | | | +|--------------------|--------------|------------------------------------------------------------------------| +| Postcondition: | SCSM state 2 | Wait for subsequent requests (in case of all the possible operations). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | +| B) Receiving Error | | | +| Precondition: | SCSM state 3 | Wait for Bind result (in case of Bind). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | +| Postcondition: | SCSM state 1 | Idle (in case of Bind). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | + +Error Procedure is dependent on the Service Logic. If there is an alternative SDF it may be possible to do another query, otherwise the service processing should be terminated. + +### Procedure at Responding Entity (SDF) + +| | | | +|------------------------|-----------------|------------------------------------------------| +| A) Receiving Operation | | | +| Precondition: | SDF-FSM state 1 | Idle (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | +| Postcondition: | SDF-FSM state 2 | Bind Pending (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | +| B) Returning Error | | | +| Precondition: | SDF-FSM state 2 | Bind Pending (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | +| Postcondition: | SDF-FSM state 1 | Idle (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | + +The SDF could not perform the operation due to a service related problem and sends a Service error to the SCF. After returning the error, no further error treatment is performed. + +#### 3.2.1.12 Security error + +##### 3.2.1.12.1 General description + +###### 3.2.1.12.1.1 Error description + +This error is sent by the SDF to the SCF to report a problem in carrying out an operation for security reasons. The conditions under which a security error is to be issued are defined in 12.7/X.511 (1993). + +###### 3.2.1.12.1.2 Argument description + +The security error parameter and problem codes are specified in 12.7/X.511 (1993). + +###### 3.2.1.12.2 Operations SCF → SDF + +- Bind; +- Search; +- Add Entry; +- Remove Entry; +- Modify Entry. + +## Procedure at Invoking Entity (SCF) + +### A) Sending Operation + +| | | | +|----------------|--------------|------------------------------------------------------------------------| +| Precondition: | SCSM state 1 | Idle (in case of Bind). | +| or | SCSM state 2 | Wait for subsequent requests (in case of operations except Bind). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | +| Postcondition: | SCSM state 2 | Wait for subsequent requests (in case of all the possible operations). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | + +### B) Receiving Error + +| | | | +|----------------|--------------|------------------------------------------------| +| Precondition: | SCSM state 3 | Wait for Bind result (in case of Bind). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | +| Postcondition: | SCSM state 1 | Idle (in case of Bind). | +| or | SCSM state 4 | SDF Bound (in case of operations except Bind). | + +Error Procedure is independent of the Service Logic. The service processing should be terminated. + +## Procedure at Responding Entity (SDF) + +### A) Receiving Operation + +| | | | +|----------------|-----------------|------------------------------------------------| +| Precondition: | SDF-FSM state 1 | Idle (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | +| Postcondition: | SDF-FSM state 2 | Bind Pending (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | + +### B) Returning Error + +| | | | +|----------------|-----------------|------------------------------------------------| +| Precondition: | SDF-FSM state 2 | Bind Pending (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | +| Postcondition: | SDF-FSM state 1 | Idle (in case of Bind). | +| or | SDF-FSM state 3 | SCF Bound (in case of operations except Bind). | + +The SDF could not perform the operation for security reasons and therefore sends a Security error to the SCF. After returning the error, no further error treatment is performed. + +### 3.2.1.13 SystemFailure + +#### 3.2.1.13.1 General description + +##### 3.2.1.13.1.1 Error description + +This error is returned by a physical entity if it was not able to fulfil a specific task as requested by an operation, and recovery is not expected to be completed within the current call instance (clarification is FFS). + +### 3.2.1.13.1.2 Argument description + +#### PARAMETER + +UnavailableNetworkResource + +UnavailableNetworkResource ::= ENUMERATED { +    unavailableResources (0), +    componentFailure (1), +    basicCallProcessingException (2), +    resourceStatusFailure (3), +    endUserFailure (4)} + +### 3.2.1.13.2 Operations SCF → SSF + +#### Non Call Associated + +- ActivateServiceFiltering. + +#### Call Associated/Non Call Processing + +- ApplyCharging; +- CallInformationRequest; +- CancelStatusReportRequest; +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport; +- RequestNotificationChargingEvent; +- RequestReportBCSMEEvent; +- SendChargingInformation. + +#### Call Associated/Call Processing + +- AnalyseInformation; +- CollectInformation; +- Connect; +- ConnectToResource; +- DisconnectForwardConnection; +- EstablishTemporaryConnection; +- HoldCallInNetwork; +- InitiateCallAttempt; +- SelectFacility; +- SelectRoute. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### 3.2.1.13.3 Operations SSF → SCF + +- AnalysedInformation; +- ApplyChargingReport; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- ODisconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- TAnswer; +- TBusy; +- TDisconnect; +- TermAttemptAuthorized; +- TMidCall; +- TNoAnswer. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.13.4 Operations SCF → SRF** + +- Cancel; +- PlayAnnouncement; +- PromptAndCollectUserInfoInformation. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.13.5 Operations SRF → SCF** + +- AssistRequestInstructions. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.14 Task refused** + +#### **3.2.1.14.1 General introduction** + +##### **3.2.1.14.1.1 Error description** + +This Error is returned by a physical entity if it was not able to fulfil a specific task as requested by an operation, and recovery is expected to be completed within the current call instance. (The precise definition is FFS.) + +##### **3.2.1.14.1.2 Argument description** + +###### **PARAMETER ENUMERATED {** + +- generic (0),** + - unobtainable (1),** + - congestion (2)** + - *other values FFS* +- }** + +#### **3.2.1.14.2 Operations SCF → SSF** + +##### **Non Call Associated** + +- ActivateServiceFiltering. + +##### **Call Associated/Non Call Processing** + +- ApplyCharging; +- CallInformationRequest; +- Cancel; +- CancelStatusReportRequest; +- FurnishChargingInformation; +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport; +- RequestNotificationChargingEvent; +- RequestReportBCSMEEvent; +- ResetTimer; +- SendChargingInformation. + +##### **Call Associated/Call Processing** + +- AnalyseInformation; +- CollectInformation; +- Connect; +- ConnectToResource; +- DisconnectForwardConnection; +- EstablishTemporaryConnection; +- HoldCallInNetwork; +- InitiateCallAttempt; +- SelectFacility; +- SelectRoute; + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### 3.2.1.14.3 Operations SSF → SCF + +- AnalysedInformation; +- ApplyChargingReport; +- AssistRequestInstructions; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- ODisconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- TAnswer; +- TBusy; +- TDisconnect; +- TermAttemptAuthorized; +- TMidCall; +- TNoAnswer. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### 3.2.1.14.4 Operations SCF → SRF + +- Cancel; +- PlayAnnouncement; +- PromptAndCollectUserInfoInformation. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### 3.2.1.14.5 Operations SRF → SCF + +- AssistRequestInstructions. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +## 3.2.1.15 UnavailableResource + +### 3.2.1.15.1 General description + +#### 3.2.1.15.1.1 Error description + +The SRF is not able to perform its function (i.e. play a certain announcement and/or collect specific user information), and cannot be replaced. A reattempt is not possible. + +### 3.2.1.15.2 Operations SCF → SRF + +- PlayAnnouncement; +- PromptAndCollectUserInfoInformation. + +## Procedures at Invoking Entity (SCF) + +- A) SCF sends PlayAnnouncement or PromptAndCollectUserInfoInformation to SRF + +| | | | +|----------------|----------------|-----------------------------------------------------------------------------------------------------------------------| +| Precondition: | SCSM state 3.1 | Determine Mode; PlayAnnouncement or PromptAndCollectUserInfoInformation will accompany the ConnectToResource. | +| or | SCSM state 3.2 | Waiting for AssistRequestInstructions; after Establish-TemporaryConnection. | +| or | SCSM state 4.1 | Waiting for Response from the SRF; if more PlayAnnouncements or PromptAndCollectUserInfoInformations are outstanding. | +| Postcondition: | SCSM state 4.1 | Waiting for Response from the SRF. | + +B) SCF receives UnavailableResource Error from SRF + +Precondition: SCSM state 4.1 Waiting for Response from the SRF. + +Postcondition: SCSM state 4.1 Waiting for Response from the SRF. + +If the chosen resource cannot perform its function, the further treatment is service dependent. + +Examples: – request SSF to connect to alternative SRF; +– service processing without PlayAnnouncement or PromptAndCollectUserInfo (if possible); +– terminate service processing. + +### **Procedures at Responding Entity (SRF)** + +A) SRF receiving PlayAnnouncement or PromptAndCollectUserInfo + +Precondition: SRSM state 2 Connected; if initial PlayAnnouncement or PromptAndCollectUserInfo. + +or SRSM state 3 User Interaction; if not initial PlayAnnouncement or PromptAndCollectUserInfo. + +B) SRF is not able to perform its function (and cannot be replaced). SRF sends UnavailableResource. + +Precondition: SRSM state 3 User Interaction. + +Postcondition: SRSM state 3 User Interaction. + +### **3.2.1.16 UnexpectedComponentSequence** + +#### **3.2.1.16.1 General description** + +##### **3.2.1.16.1.1 Error description** + +The responding entity cannot start the processing of the requested operation because a SACF or MACF rule is violated, or the operation could not be processed in the current state of the FSM. + +#### **3.2.1.16.2 Operations SCF → SSF** + +##### **Non Call Associated** + +– ActivateServiceFiltering. + +##### **Call Associated/Non Call Processing** + +– ApplyCharging; +– CallInformationRequest; +– FurnishChargingInformation; +– RequestCurrentStatusReport; +– RequestEveryStatusChangeReport; +– RequestFirstStatusMatchReport; +– RequestNotificationChargingEvent; +– RequestReportBCSMEEvent; +– ResetTimer; +– SendChargingInformation. + +##### **Call Associated/Call Processing** + +– AnalyseInformation; +– CollectInformation; +– Connect; +– ConnectToResource; +– DisconnectForwardConnection; +– EstablishTemporaryConnection; +– HoldCallInNetwork; +– InitiateCallAttempt; +– SelectFacility; +– SelectRoute. + +In this case the SSF detects the erroneous situation, sends the UnexpectedComponentSequence error and remains in the same state. In the SCF the Service Logic and maintenance functions are informed and the Service Logic decides about error treatment. + +### 3.2.1.16.3 Operations SSF → SCF + +- AnalysedInformation; +- ApplyChargingReport; +- AssistRequestInstructions; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- ODisconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- Answer; +- TBusy; +- TDisconnect; +- TermAttemptAuthorized; +- TMidCall; +- TNoAnswer. + +In case of assisting SSF an error occurs in case an AssistRequestInstructions is sent while a relationship between SCF and assisting SSF has already been established, the SCF returns the error parameter. Service Logic and maintenance are informed. On receiving the error, the assisting SSF moves to Idle and the temporary connection is released. + +In case the operation is sent by an "initiating" SSF in the context of an existing relationship, the SCF returns the error parameter. Service Logic and maintenance are informed. On receiving the error, the SSF moves to Idle. + +### 3.2.1.16.4 Operations SCF → SRF (only applicable for direct SCF-SRF case) + +- PlayAnnouncement; +- PromptAndCollectUserInfoInformation. + +In this case the SRF detects the erroneous situation, sends the UnexpectedComponentSequence error and remains in the same state. In the SCF, the Service Logic and maintenance functions are informed and the Service Logic decides about error treatment. Possible error treatment is to send the DisconnectForwardConnection operation to the SSF. + +### 3.2.1.16.5 Operations SRF → SCF + +- AssistRequestInstructions. + +In this case, an error occurs if the SRF has already an established relationship with the SCF and sends an AssistRequestInstructions. The SCF detects the erroneous situation, informs Service Logic and maintenance functions and returns the error parameter. On receiving the parameter, the SRF moves to Idle and releases the temporary connection. + +## 3.2.1.17 UnexpectedDataValue + +### 3.2.1.17.1 General description + +#### 3.2.1.17.1.1 Error description + +The responding entity cannot complete the processing of the requested Operation because a parameter has an unexpected data value. + +Note that this error does not overlap with "ParameterOutOfRange" + +Example: **startTime DateAndTime :=** *-- value indicating January 32 1993, 12:15:01* + +The responding entity does not expect this value and responds with "UnexpectedDataValue". + +### 3.2.1.17.2 Operations SCF → SSF + +#### Non Call Associated + +- ActivateServiceFiltering. + +#### Call Associated/Non Call Processing + +- ApplyCharging; +- CallInformationRequest; +- Cancel; +- CancelStatusReportRequest; +- FurnishChargingInformation; +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport; +- RequestNotificationChargingEvent; +- RequestReportBCSMEEvent; +- ResetTimer; +- SendChargingInformation. + +#### Call Associated/Call Processing + +- AnalyseInformation; +- CollectInformation; +- Connect; +- ConnectToResource; +- EstablishTemporaryConnection; +- HoldCallInNetwork; +- InitiateCallAttempt; +- SelectFacility; +- SelectRoute. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### 3.2.1.17.3 Operations SSF → SCF + +- AnalysedInformation; +- ApplyChargingReport; +- AssistRequestInstructions; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- ODisconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- TAnswer; +- TBusy; +- TDisconnect; +- TermAttemptAuthorized; +- TMidCall; +- TNoAnswer. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### 3.2.1.17.4 Operations SCF → SRF + +- Cancel; +- PlayAnnouncement; +- PromptAndCollectUserInfoInformation. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.17.5 Operations SRF → SCF** + +- AssistRequestInstructions. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.18 UnexpectedParameter** + +#### **3.2.1.18.1 General description** + +##### **3.2.1.18.1.1 Error description** + +There is an error in the received Operation argument. A valid but unexpected parameter was present in the Operation argument. The presence of this parameter is not consistent with the presence of the other parameters. The responding entity cannot start to process the Operation. + +#### **3.2.1.18.2 Operations SCF → SSF** + +##### **Non Call Associated** + +- ActivateServiceFiltering. + +##### **Call Associated/Non Call Processing** + +- ApplyCharging; +- CallInformationRequest; +- FurnishChargingInformation; +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport; +- RequestNotificationChargingEvent; +- RequestReportBCSMEVENT; +- ResetTimer; +- SendChargingInformation. + +##### **Call Associated/Call Processing** + +- AnalyseInformation; +- CollectInformation; +- Connect; +- ConnectToResource; +- EstablishTemporaryConnection; +- HoldCallInNetwork; +- InitiateCallAttempt; +- SelectFacility; +- SelectRoute. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +#### **3.2.1.18.3 Operations SSF → SCF** + +- AnalysedInformation; +- ApplyChargingReport; +- AssistRequestInstructions; +- CollectedInformation; +- InitialDP; +- OAnswer; +- OCalledPartyBusy; +- ODisconnect; +- OMidCall; +- ONoAnswer; +- OriginationAttemptAuthorized; +- RouteSelectFailure; +- TAnswer; +- TBusy; + +- TDisconnect; +- TermAttemptAuthorized; +- TMidCall; +- TNoAnswer. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +#### **3.2.1.18.4 Operations SCF → SRF** + +- PlayAnnouncement; +- PromptAndCollectUserInfo. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +#### **3.2.1.18.5 Operations SRF → SCF** + +- AssistRequestInstructions. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.19 UnknownLegID** + +#### **3.2.1.19.1 General description** + +##### **3.2.1.19.1.1 Error description** + +This error is used to indicate to the SCF that a specific leg, indicated by the LegID parameter value in the operation, is unknown to the SSF. + +#### **3.2.1.19.2 Operations SCF → SSF** + +##### **Call Associated/Non Call Processing** + +- SendChargingInformation. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.20 UnknownResource** + +#### **3.2.1.20.1 General description** + +##### **3.2.1.20.1.1 Error description** + +This error is used to indicate to the SCF that a specific physical resource which is indicated by the ResourceID parameter, is not known to the SSF. + +#### **3.2.1.20.2 Operations SCF → SSF** + +- Call Associated/Non Call Processing; +- RequestCurrentStatusReport; +- RequestEveryStatusChangeReport; +- RequestFirstStatusMatchReport. + +Refer to 3.2.1.7 MissingParameter for the appropriate error procedures. + +### **3.2.1.21 Update error** + +#### **3.2.1.21.1 General description** + +##### **3.2.1.21.1.1 Error description** + +This error is sent by the SDF to the SCF to report a problem related to attempts to add, delete, or modify information in the SDF. The conditions under which an update error is to be issued are defined in 12.9/X.511 (1993). + +##### **3.2.1.21.1.2 Argument description** + +The update error parameter and problem codes are specified in 12.9/X.511 (1993). + +### 3.2.1.21.2 Operations SCF → SDF + +- Add Entry; +- Remove Entry; +- Modify Entry. + +### Procedure at Invoking Entity (SCF) + +#### A) Sending Operation + +| | | | +|----------------|--------------|-------------------------------| +| Precondition: | SCSM state 4 | SDF Bound or | +| | SCSM state 2 | Wait for subsequent requests. | +| Postcondition: | SCSM state 4 | SDF Bound or | +| | SCSM state 2 | Wait for subsequent requests. | + +#### B) Receiving Error + +| | | | +|----------------|--------------|------------| +| Precondition: | SCSM state 4 | SDF Bound. | +| Postcondition: | SCSM state 4 | SDF Bound. | + +Error Procedure is dependent on the Service Logic. + +### Procedure at Responding Entity (SDF) + +#### A) Receiving Operation + +| | | | +|----------------|-----------------|------------| +| Precondition: | SDF-FSM state 3 | SCF Bound. | +| Postcondition: | SDF-FSM state 3 | SCF Bound. | + +#### B) Returning Error + +| | | | +|----------------|-----------------|------------| +| Precondition: | SDF-FSM state 3 | SCF Bound. | +| Postcondition: | SDF-FSM state 3 | SCF Bound. | + +The SDF could not perform the operation due to a problem related to the addition, deletion or modification of information and sends an Update error to the SCF. After returning the error, no further error treatment is performed. + +## 3.2.2 Entity related error procedures + +The following subclauses define the error handling for the entity related errors. Since the error situations are not originated by the reception of an operation, the invoking entity is denoted here as the entity at which the error situation is detected. The responding entity is the entity which receives the error report. + +The TCAP services used for reporting errors are described in 3.4. + +### 3.2.2.1 Expiration of TSSF + +#### 3.2.2.1.1 General description + +##### 3.2.2.1.1.1 Error description + +A timeout occurred in the SSF on the response from the SCF. + +#### 3.2.2.1.2 Procedures SSF → SCF + +### Procedure at the Invoking Entity (SSF) + +Timeout occurs in SSF on TSSF. + +| | | | +|----------------|-----------------|------------------------------------------| +| Precondition: | SSF-FSM state c | Waiting for Instructions. | +| or | SSF-FSM state d | Waiting for end of User Interaction. | +| or | SSF-FSM state e | Waiting for end of Temporary connection. | +| Postcondition: | SSF-FSM state a | Idle. | + +The SSF-FSM aborts the dialogue and moves to the Idle state, the CCF routes the call if necessary (e.g. default routing to a terminating announcement). The abort is reported to the maintenance functions. + +### Procedure at the Responding Entity (SCF) + +SCF receives a dialogue abort. + +| | | | +|----------------|--------------|-----------------------------------------------------------------------------------| +| Precondition: | Any state. | | +| Postcondition: | SCSM state 1 | Idle; if the abort is related to a SSF dialogue. | +| or | SCSM state 2 | Preparing SSF instructions; if the abort is related to an assisting SSF dialogue. | + +The SCF releases all allocated resources and reports the abort to the maintenance functions, if the abort is received on a SSF dialogue. The SCF releases all resources related to the dialogue, reports the abort to the maintenance functions and returns to state preparing SSF instructions, if the abort is received on an assisting SSF dialogue. + +#### 3.2.2.2 Expiration of TSRF + +##### 3.2.2.2.1 General description + +###### 3.2.2.2.1.1 Error description + +A timeout occurred in the SRF on the response from the SCF. This procedure concerns only the direct SCF-SRF case. + +##### 3.2.2.2.2 Procedures SRF → SCF + +### Procedure at the Invoking Entity (SRF) + +Timeout occurs in SRF on TSRF. + +| | | | +|----------------|--------------|-------------------| +| Precondition: | SRSM state 2 | Connected. | +| or | SRSM state 3 | User Interaction. | +| Postcondition: | SRSM state 1 | Idle. | + +The SRF aborts the dialogue and moves to the Idle state, all allocated resources are de-allocated. The abort is reported to the maintenance functions. + +### Procedure at the Responding Entity (SCF) + +SCF receives a dialogue abort. + +| | | | +|----------------|--------------|-----------------------------| +| Precondition: | SCSM state 4 | User Interaction. | +| Postcondition: | SCSM state 2 | Preparing SSF instructions. | + +The SCF releases all resources related to the dialogue, reports the abort to the maintenance functions and returns to state preparing SSF instructions. + +## 3.3 Detailed Operation procedures + +The intended use of operations and parameters from clause 2 not described in the following detailed procedure descriptions is for further study. For more information please refer to 6.4/Q.1214. + +### 3.3.1 ActivateServiceFiltering procedure + +#### 3.3.1.1 General description + +When receiving this operation, the SSF handles calls to destinations in a specified manner without request for instructions to the SCF. In the case of service filtering, the SSF executes a specific service filtering algorithm. For the transfer of service filtering results refer to the operation 'ServiceFilteringResponse'. + +##### 3.3.1.1.1 Parameters + +- filteredCallTreatment: + +This parameter specifies how filtered calls are treated. It includes information about the announcement to be played, the charging approach, the number of counters used and the release cause to be applied to filtered calls. + +i) sFBillingChargingCharacteristics: + +This parameter determines the charging to be applied for service filtering. Its content is network specific. + +NOTE – Actual format and encoding is for further study. + +ii) informationToSend: + +This parameter indicates an announcement, a tone or display information to be sent to the calling party. At the end of information sending, the call shall be released. + +• inbandInfo: + +This parameter specifies the inband information to be sent. + +– messageID: + +This parameter indicates the message(s) to be sent, it can be one of the following: + +1) elementaryMessageID: + +This parameter indicates a single announcement. + +2) text: + +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech). This parameter consist of two subparameters, messageContent and attributes. The attributes of text may consist of items such as language. + +3) elementaryMessageIDs: + +This parameter specifies a sequence of announcements. + +4) variableMessage: + +This parameter specifies an announcement with one or more variable parts. + +– numberOfRepetitions: + +This parameter indicates the maximum number of times the message shall be sent to the end-user. + +– duration: + +This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. ZERO indicates endless repetition. + +– interval: + +This parameter indicates the time interval in seconds between repetitions, i.e. the time between the end of the announcement and the start of the next repetition. This parameter can only be used when the number of repetitions is > 1. + +• tone: + +This parameter specifies a tone to be sent to the end-user. + +– toneID: + +This parameter indicates the tone to be sent. + +– duration: + +This parameter indicates the time duration in seconds of the tone to be sent. ZERO indicates infinite duration. + +• displayInformation: + +This parameter indicates a text string to be sent to the end-user. This information can not be received by a PSTN end-user. + +iii) maximumNumberOfCounters: + +This parameter provides the number of counters to be allocated as well as the number of destinations included in the service filtering, i.e. 'maximumNumberOfCounters' subsequent destination addresses beginning with the destination address provided in 'filteringCriteria' are used for service filtering. One counter is assigned to each of these destination addresses. + +The number of counters may only be >1 if the 'filteringCriteria' are of the type 'addressAndService'. + +iv) releaseCause: + +This parameter provides the cause value used for call release after the 'informationToSend' (for example announcement) has been sent to the calling party. If 'releaseCause' is not present, the default value is the same as the ISUP value decimal 31 (normal unspecified). + +b) filteringCharacteristics: + +This parameter indicates the severity of the filtering and the point in time when the 'ServiceFilteringResponse' shall be sent. It determines whether the 'interval' or the 'numberOfCalls' are used. + +i) interval: + +After expiration of the interval timer the next call to arrive causes following actions: + +- sending of an 'InitialDP' or a DP-specific operation; +- sending of a 'ServiceFilteringResponse'; +- starting again the interval timer. + +When filtering is started the first interval is started. + +An interval of 0 indicates that all calls matching the filtering criteria will result in sending of an 'InitialDP' or a DP-specific operation and no filtering will be applied (i.e. no 'ServiceFilteringResponse' will be sent). + +An interval of -1 indicates that none of the calls matching the filtering criteria will either result in sending of an 'InitialDP' or a DP-specific operation or a 'ServiceFilteringResponse' operation. + +Other values indicate duration in seconds. + +ii) numberOfCalls: + +The *n* th call causes an 'InitialDP' or a DP-specific operation and a 'ServiceFilteringResponse' operation sent to the SCF. This threshold value is met if the sum of all counters assigned to one service filtering entity is equal to 'numberOfCalls'. + +A number of calls of 0 indicates that none of the calls matching the filtering criteria will result in sending of an 'InitialDP' or a DP-specific operation and a 'ServiceFilteringResponse' operation. + +c) filteringTimeout: + +This parameter indicates the duration of the filtering. When the time expires, a 'ServiceFilteringResponse' is sent to the SCF and service filtering is stopped. Two approaches are supported (duration or stopTime): + +i) duration: + +If the duration time expires, then service filtering is stopped and the final report is sent to the SCF. + +A duration of 0 indicates that service filtering is to be removed. + +A duration of -1 indicates an infinite duration. + +A duration of -2 indicates a network specific duration. + +Other values indicate duration in seconds. + +ii) stopTime: + +When the 'stopTime' is met then service filtering is stopped and the final report is sent to the SCF. If 'stopTime' was already met, i.e. the value of the stopTime is less than the value of the actual time but the difference does not exceed the value equivalent to 50 years, then service filtering is immediately stopped and the actual counter values are reported to the SCF. This occurs in cases where the SCF wishes to explicitly stop a running service filtering. + +d) filteringCriteria: + +This parameter specifies which calls are filtered based on 'serviceKey', 'callingAddressValue', 'calledAddressValue' or 'locationNumber'. It is a choice of 'servicekey' or 'addressAndService'. + +i) serviceKey: + +This parameter identifies unambiguously the requested IN service for which filtering should be applied. + +ii) addressAndService: + +This parameter identifies the IN service and dialled number for which filtering should be applied. The geographical area may also be identified ('callingAddressValue' and/or 'locationNumber'). + +iii) calledAddressValue: + +This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. + +iv) serviceKey: + +This parameter identifies unambiguously the requested IN service for which filtering should be applied. + +v) callingAddressValue: + +This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied. + +vi) locationNumber: + +This parameter identifies the geographical area from which the call to be filtered originates. It is used when 'callingAddressValue' does not contain any information about the geographical location of the calling party. + +e) startTime: + +This parameter defines when filtering is started. If 'startTime' is not provided or was already met, the SSF starts filtering immediately. + +### 3.3.1.2 Invoking Entity (SCF) + +#### 3.3.1.2.1 Normal procedure + +SCF Precondition: + +- SLPI detects that service filtering has to be initiated at the SSF. + +SCF Postconditions: + +- 1) SLPI starts an application timer to monitor the expected end of service filtering. +- 2) The SCME is in the state "Waiting For ServiceFilteringResponse". + +Sending the 'ActivateServiceFiltering' operation causes a transition of the SCME from the state "Service Filtering Idle" to the state "Waiting For SSF Service Filtering Response". The SCME remains in this state until the application timer in the SLPI expires. The SCME is informed by the SLPI about timer expiration. Then it moves to the state "Service Filtering Idle". + +If no errors occurred after receiving an 'ActivateServiceFiltering' at the SSF an empty Return Result is sent to the SCF. That causes no state transition in the SCME. + +To change the parameters of an existing service filtering entity, the SCF has to send an 'ActivateServiceFiltering' operation with the same 'filtering Criteria'. The second parameter set replaces the first one. + +#### 3.3.1.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.1.3 Responding Entity (SSF) + +#### 3.3.1.3.1 Normal procedure + +SSF Precondition: + +- None. + +SSF Postcondition: + +- The SSME-FSM is in the state "Non Call Associated Treatment". + +If there is no already existing SSME-FSM for the "filteringCriteria" provided, then a new SSME-FSM is created. This SSME-FSM enters the state "Non-Call Associated Treatment" and initializes the service filtering for the specified IN calls. The parameters "filteredCallTreatment", "filteringCharacteristics", "filteringCriteria", "filteringTimeOut" and "startTime" are set as provided in the operation. A number of counters will be allocated and reset. In the case of the "startTime" that has not been met yet, the service filtering will be started at the specified point in time. + +If the operation "ActivateServiceFiltering" addresses an already existing service filtering entity, the parameters "filteredCallTreatment", "filteringCharacteristics", "filteringTimeOut" and "startTime" are modified as provided in the operation. In the case that the addressed service filtering entity is active, the SSF reports the counter values to the SCF via the operation "ServiceFilteringResponse". The service filtering process is stopped if an already expired "stopTime" or "duration" equal to ZERO or a new not yet met "startTime" is provided. The SSF then proceeds as described for "ServiceFilteringResponse". In the case of the "startTime" that has not been met yet, the service filtering will be continued at the specified point in time. + +If the service filtering proceeds, then the SSME-FSM remains in the state "Non-Call Associated Treatment". Otherwise the SSME-FSM moves to state "Idle Management". + +When a call matches several active "filteringCriteria" it should be subject to filtering on the most specific criteria, i.e. the criteria with the longest "callingAddressValue" or "locationNumber", or alternatively the criteria with the largest number of parameters specified. + +When performing service filtering with the "filteringCriteria"-"addressAndService", the first parameters checked will always be the "serviceKey" and "calledAddressValue". + +If an "ActivateServiceFiltering" operation is passed to the SSF with the "filteringCriteria" "addressAndService" with both "callingAddressValue" and "locationNumber" present, the following is applicable: + +- When the SSF receives a call that matches "serviceKey" and "calledAddressValue" (in the active "filteringCriteria"), it investigates whether or not the "locationNumber" is present in the initial address message. If it is present and matches the active "filteringCriteria", the call is filtered. If the SSF finds that the "locationNumber" is absent, then it will check the "callingAddressValue" and perform filtering depending on that parameter. + +If no errors occurred after receiving an "ActivateServiceFiltering" on the SSF, an empty Return Result is sent to the SCF. That causes no state transition in the SSME-FSM. + +Following application timers are used: + +- detect moment to start service filtering (start time); +- duration time for service filtering; +- interval time for service filtering (for timer controlled approach). + +#### 3.3.1.3.2 Error handling + +If the SSF detects an error with any of the defined error values, then this error is reported to the SCF. + +The event is recorded in the SSF and an error condition indicated. + +In case a new SSME-FSM should be created, the relationship is ended and all concerned resources (e.g. counters) are released. The SSME-FSM remains in the state "Idle Management". + +In case there is already an existing SSME-FSM, the service filtering data remains unchanged. The SSME-FSM remains in the state "Non-Call Associated Treatment". + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.2 ActivityTest procedure** + +#### **3.3.2.1 General description** + +This operation is used to check for the continued existence of a relationship between the SCF and SSF. If the relationship is still in existence, then the SSF will respond. If no reply is received within a given time period, then the SCF will assume that the SSF has failed in some way and will take the appropriate action. + +##### **3.3.2.1.1 Parameters** + +None. + +#### **3.3.2.2 Invoking Entity (SCF)** + +##### **3.3.2.2.1 Normal procedure** + +SCF Preconditions: + +- 1) A relationship exists between the SCF and the SSF. +- 2) The activity test timer (Tati) expires, after which the 'ActivityTest' operation is sent to the SSF. + +SCF Postcondition: + +- If a Return Result 'ActivityTest' is received, the SCME resets the activity test timer and takes no further action. + +##### **3.3.2.2.2 Error handling** + +If a time-out on the 'ActivityTest' operation or a P-Abort is received from TCAP, this is an indication that the relationship with the SSF was somehow lost. If a time-out is received, SCF aborts the dialogue. + +The SLPI that was the user of this dialogue will be informed, the corresponding SCSM-FSM will move to the state "Idle". + +#### **3.3.2.3 Responding Entity (SSF)** + +##### **3.3.2.3.1 Normal procedure** + +SSF Precondition: + +- A relationship exists between the SCF and the SSF. + +SSF Postconditions: + +- 1) The SSME-FSM stays in, or moves to the state "Non Call Associated Treatment". +- 2) If the Dialogue ID is active and if there is a SSF-FSM using the dialogue, the SSME sends a Return Result 'ActivityTest' to the SCF. If there are no other management activities, the SSME-FSM returns to the state "Idle Management"; or + +If the Dialogue ID is not active, the TCAP in the SSF will issue a P-Abort, the SSME will in that case never receive the 'ActivityTest' req.ind and thus will not be able to reply. + +##### **3.3.2.3.2 Error handling** + +Operation related error handling is not applicable, due to class 3 operation. + +### **3.3.3 AddEntry procedure** + +#### **3.3.3.1 General description** + +The X.500 'AddEntry' operation is used to request the SDF to add a leaf entry (either an object entry or an alias entry) in the DIT. For a full description of the AddEntry operation, see 11.1/X.511. + +##### **3.3.3.1.1 Parameters** + +See 11.1.1/X.511 and 11.1.2/X.511. + +### 3.3.3.2 Invoking Entity (SCF) + +#### 3.3.3.2.1 Normal procedure + +SCF Precondition: + +- SCSM: "SDF Bound" or "Wait for Subsequent Requests". + +SCF Postcondition: + +- SCSM: "SDF Bound". + +When the SCSM is in the state "Wait for Subsequent Requests" and a need of the service logic to add an entry in the SDF exists, an internal event [(e2) Request\_to\_SDF] occurs. Until the application process has not indicated with a delimiter (or a timer expiry) that the operation should be sent, the SCSM remains in the state "Wait for Subsequent Requests" and the operation is not sent. The operation is sent to the SDF in a message containing a Bind argument. The SCSM waits for the response from the SDF. The reception of the response [(E5) Response\_from\_SDF\_with\_Bind or (E4) Bind\_Error] to the Bind operation previously issued to the SDF causes a transition of the SCF to the state "SDF Bound" or to the state "Idle". When the SCSM has moved to state "Idle", the AddEntry operation was discarded. In the State "SDF Bound", the response of the AddEntry operation [(E7) Response\_from\_SDF] causes a transition of the SCF to the same state ("SDF Bound"). It may be either the result of the AddEntry operation or an error. + +When the SCSM is in the state "SDF Bound" and a need of the service logic to add an entry in the SDF exists, an internal event occurs. This event, called (e6) Request\_to\_SDF causes a transition to the same state "SDF Bound" and the SCSM waits for the response from the SDF. The reception of the response [(E7) Response\_from\_SDF] to the AddEntry operation previously issued to the SDF causes a transition of the SCF to the same state "SDF Bound". The response from the SDF may be either the result of the AddEntry operation or an error. + +#### 3.3.3.2.2 Error handling + +Generic error handling for the operation related errors is described in 11.1.4/X.511 and 11.1.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +### 3.3.3.3 Responding Entity (SDF) + +#### 3.3.3.3.1 Normal procedure + +SDF Precondition: + +- SDSM: "SCF Bound" or "Bind Pending". + +SDF Postcondition: + +- SDSM "SCF Bound". + +When the SDF is in the state "Bind Pending", the external event (E3) Request\_from\_SCF caused by the reception of an 'AddEntry' operation from the SCF occurs. The SDF does not proceed to the operation until a Bind operation has been successfully executed. It remains in the same state. + +When the SDF is in the state "SCF Bound", the external event (E7) Request\_from\_SCF caused by the reception of an 'AddEntry' operation from the SCF occurs. The SDF waits for the response to the operation. + +On the receipt of the event (E7) and before adding the new entry item, the SDF takes the following actions: + +- verify that the superior object to which the entry should be added exists in the SDF; +- verify that the entry does not already exist in the SDF; +- verify that the access rights to add the entry and each of its components (attributes and values) are sufficient; +- verify that the entry conforms to the Directory schema. + +After the specified actions indicated above are successfully executed, the entry is added into the SDF database. A null result is returned to the SCF. The sending of the result corresponds to the event (e6) Response\_to\_SCF. + +### **3.3.3.3.2 Error handling** + +Generic error handling for the operation related errors is described in 11.1.4/X.511 and 11.1.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +## **3.3.4 AnalysedInformation Procedure** + +### **3.3.4.1 General description** + +This operation is sent by the SSF to the SCF after detecting a valid trigger condition at the Analysed Info DP, or to report an event requested by RequestReportBCSMEvent. + +#### **3.3.4.1.1 Parameters** + +- dPSpecificCommonParameters: +- dialledDigits: +See Recommendation Q.1290. +- callingPartyBusinessGroupID: +See Recommendation Q.1290. The SCF can use this IE to select SLPs based on the group and for authorization purposes. The network operators can specify that this IE should be used if their particular network has the information available. +- callingPartySubaddress: +See Recommendation Q.931. +- callingFacilityGroup: +See Recommendation Q.1290. +- callingFacilityGroupMember: +See Recommendation Q.1290. +- originalCalledPartyID: +See Recommendation Q.762. Original Called Number signalling information. +- prefix: +See Recommendation Q.1290. +- redirectingPartyID: +This parameter (if available) is the directory number of the last redirecting party. +- redirectionInformation: +See Recommendation Q.763 Redirection Information signalling information. +- routeList: +Route List represents the list of routes which would have been used in order to route the call. The network operators can specify that this IE should be used if their particular network has the information available. +- travellingClassMark: +See Recommendation Q.1290. +- featureCode: +See Recommendation Q.1290. +- accessCode: +See Recommendation Q.1290. +- carrier: +See Recommendation Q.1290. + +### 3.3.4.2 Invoking Entity (SSF) + +#### 3.3.4.2.1 Normal procedure + +SSF Preconditions (TDP): + +- 1) Call origination attempt has been initiated. +- 2) Called Party Number is available and nature of address determined. +- 3) Call gapping or service filtering are not in effect. +- 4) DP criteria are met. +- 5) For a TDP-R, there is no existing control relationship influencing the call segment. + +SSF Preconditions (EDP): + +- 1) For an EDP-R, there is an existing control relationship and the EDP AnalysedInformation is armed. +- 2) For an EDP-N, there is a monitoring or control relationship. + +SSF Postconditions (TDP): + +- 1) For a TDP-R, basic call processing has been suspended at Analysed\_Info DP, and a control relationship has been established. +- 2) For a TDP-N, basic call processing proceeds at Select\_Route PIC, and no control relationship is established. + +SSF Postconditions (EDP): + +- 3) For an EDP-R, basic call processing has been suspended at Analysed\_Info DP, and the existing control relationship continues. +- 4) For an EDP-N, basic call processing proceeds at Select\_Route PIC, and the existing non-control relationship continues unless no further EDPs are armed and no "CallInformationReport or "ApplyChargingReport" are requested. + +The SSF has sufficient information available associated with the originating call portion. This information has been analysed and the results are as described below: + +- 1) From a non-ISDN line or ISDN interface, the Analysis Results consists of one or more of the following: + - CalledPartyID – The number used to identify the called party in the forward direction (i.e. it is used to populate the bearer signalling protocol's called party number information element). + - TypeOfCall – Indicates one of: interexchange carrier, international carrier, local exchange operator, interexchange carrier operator or international carrier operator. + - Carrier (for calls requiring an interexchange carrier) – Indicates the type of carrier requested. + - CarrierIdentificationCode (for calls requiring an interexchange carrier) – Indicates the code for the specific carrier to be used. + - CarrierSelection (for calls requiring an interexchange carrier) – Indicates whether the caller dialled the selected carrier and whether the caller pre-subscribed to the selected carrier. + - RouteIndex – An index to a route list (if the call does not terminate on this SSF). + - Collected Information – Access Codes and Prefixes, Collected Address Information/Digits. + +- 2) From a conventional or SS No. 7-supported trunk interface, this consists of one or more of the following: + - ChargeNumber. + - CalledPartyID. + - TypeOfCall. + - CarrierIdentificationCode (for interexchange carrier calls). + - Carrier (for interexchange carrier calls). + - CarrierSelection (for interexchange carrier calls). + - RouteIndex. + - Collected Information – Collected Address Information, Prefixes, etc. The Collected Information for a call from an SS No. 7-supported trunk is based on information provided in the IAM. + +### 3.3.4.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### 3.3.4.3 Responding Entity (SCF) + +#### 3.3.4.3.1 Normal procedure + +SCF Preconditions (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or + +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or + +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +#### 3.3.4.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### 3.3.5 AnalyseInformation procedure + +#### 3.3.5.1 General description + +This operation requests the SSF to perform the originating basic call processing actions to analyse destination information that is either collected from a calling party, or provided by the SCF. This includes actions to validate the destination information according to a specified dialling plan, and if valid, to determine call set-up information. + +##### 3.3.5.1.1 Parameters + +- destinationRoutingAddress: +Represents a list of called party numbers (primary and alternates). +- alertingPattern: +See Recommendation Q.1290. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber. +- iSDNAccessRelatedInformation: +Carries the same information as the protocol element ISUP Access Transport parameter in Recommendation Q.762. +- originalCalledPartyID: +See Recommendation Q.762 Original Called Number signalling information. +- callingPartyNumber: +See Recommendation Q.762. +- callingPartysCategory: +See Recommendation Q.762 +- calledPartyNumber: +See Recommendation Q.762. Either the calledPartyNumber or the destinationRoutingAddress shall be provided by the SCF in the AnalyseInformation operation. +- chargeNumber: +See Recommendation Q.1290. +- travellingClassMark: +See Recommendation Q.1290. +- carrier: +See Recommendation Q.1290. In this message, the carrier selection field is null (00000000) and Carrier ID indicates the carrier to use for the call. + +#### 3.3.5.2 Invoking Entity (SCF) + +##### 3.3.5.2.1 Normal procedure + +SCF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Authority/ability to place outgoing call has been verified. +- 3) Destination information is available in the SSF or provided by the SCF. +- 4) Basic call processing has been suspended at one of the following DPs: + - Origination\_Attempt\_Authorized; + - Collected\_Info; + - Analysed\_Info; + - Route\_Select\_Failure; + - O\_Called\_Party\_Busy; + - O\_No\_Answer; + - O\_Disconnect (called party disconnect only). + +- 5) A control relationship has been established and the SLPI is processing the incoming request. + +SCF Postconditions: + +- 1) SLPI execution is terminated if no monitoring is requested. +- 2) SLPI execution is suspended pending the monitored event occurring, if monitoring is requested. + +The AnalyseInformation message requests the SSF-CCF to resume call origination processing taking into account the address, routing and billing information provided in the message parameters. Processing resumes at the ANALYSE\_INFORMATION PIC. + +### 3.3.5.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.5.3 Responding Entity (SSF) + +#### 3.3.5.3.1 Normal procedure + +SSF Preconditions: + +- A TDP or EDP request has been invoked. + +SSF Postconditions: + +- The SSF performs the call processing actions to analyse destination information. + +The following message parameter configurations are supported and shall result in the SSF-CCF call processing actions specified: + +- 1) No Carrier Specified: + - Switch-based carrier selection shall be performed. + - The called party address provided in the CalledPartyNumber parameter shall be subjected to trigger analysis. It should be noted that if the same called party address is returned, the same trigger may be detected and processed again at the Analysed Information TDP. +- 2) Carrier Specified: + - The SSF-CCF shall resume call processing at the ANALYSE INFORMATION PIC using the designated carrier (network operator specific). + +The following additional requirements also apply to the AnalyseInformation message. + +- The SSF-CCF shall accept called party address information contained in the CalledPartyNumber parameter that conforms to the public network numbering plan. +- If a route requires a TCM, the value in the TCM parameter shall be used. If a TCM is required and the TCM parameter is not supplied in the AnalyseInformation, the SSF-CCF shall derive the TCM in accordance with requirements that apply assuming no IN involvement with the call. (Network operator specific option). +- If the SCF does not designate a carrier and carrier selection is performed by the SSF-CCF, this indicator shall be set in the normal fashion as if IN involvement with the call had not occurred (network operator specific option). + +AnalyseInformation with CallingPartysCategory and ChargeNumber: + +- If the CallingPartysCategory parameter is included, that value shall be used as the DTMF digits or the ISDN-UP Calling Party's Category parameter in any subsequent signalling including signalling to an operator system via operator services signalling (network operator specific). +- When DTMF digits are needed for subsequent signalling, the decimal equivalent of the CallingPartysCategory value shall be used (e.g. "01000000" is equivalent to 11 digits of "64") (network operator specific). + +- If the CallingPartysCategory parameter is not included, a proper failure indication shall be used in any subsequent DTMF or ISDN-UP signalling (network operator specific). +- If the ChargeNumber parameter is included, that value shall be used as the Calling party number on non-SS No. 7 trunks or the network specific ISDN-UP Charge Number parameter in any subsequent signalling including signalling to an operator system via Operator Services Signalling (network operator specific). +- If the ChargeNumber parameter is not included, the value “0 digits” shall be used for the ChargeNumber in any subsequent non-SS No. 7 trunk or network specific ISDN-UP signalling (network operator specific). + +AnalyseInformation and O\_Called\_Party\_Busy, O\_No\_Answer: + +- When the SSF-CCF receives the AnalyseInformation message in response to an O\_Called\_Party\_Busy message the SSF-CCF shall do the following: + - 1) The SSF-CCF shall release any resources that were used to process the call between the ANALYSE\_INFORMATION and ROUTING & ALERTING PICs. + - 2) The SSF-CCF shall resume call processing at the ANALYSE\_INFORMATION PIC, and process the message as described in this procedure description. + - 3) If the originating access is DSS-1, then the SSF-CCF shall not send another CALL PROCeeding message. (INAP-DSS-1 interworking is for further study.) +- When the AnalyseInformation message is received in response to an O\_No\_Answer TDP-Request Message, the SSF-CCF shall do the following: + - 1) The SSF-CCF, if it is providing audible ringing tone to the calling party, shall remove this tone. + - 2) The SSF-CCF shall release any resources that were used to process the call between the ANALYSE\_INFORMATION and ROUTING & ALERTING PICs. + - 3) The SSF-CCF shall resume call processing at the ANALYSE\_INFORMATION PIC, and process the message as described in this procedure description. + - 4) If the originating access is DSS-1, then the SSF-CCF shall not send another CALL PROCeeding message (INAP-DSS-1 interworking is for further study.) +- When the Analyse Information message is received in response to an O\_No\_Answer EDP-Request message, the SSF-CCF shall do the following: + - 1) The SSF-CCF, if it is providing audible ringing tone to the calling party, shall remove this tone. + - 2) The SSF-CCF shall release any resources that were used to process the call between the ANALYSE\_INFORMATION and ROUTING & ALERTING PICs. + - 3) The SSF-CCF shall resume call processing at the ANALYSE\_INFORMATION PIC, and process the message as described in this Recommendation. + - 4) If the originating access is DSS-1, then the SSF-CCF shall not send another CALL PROCeeding message. (INAP-DSS-1 interworking is for further study.) + +AnalyseInformation with OriginalCalledPartyID: + +- When the SSF-CCF receives an AnalyseInformation message that contains the OriginalCalledPartyID parameter, the SSF-CCF shall map the received OriginalCalledPartyID parameter to, for example (ISUP interworking is for further study): + - 1) The OriginalCalledNumber information element in the Facility Information Element if the SSF-CCF does not yet have a value for the OriginalCalledNumber AND if the SSF-CCF routes the call to an ISDN line (for Basic rate and Primary rate ISDN signalling). + +- 2) The OriginalCalledNumber parameter in the IAM if the SSF-CCF does not already have a value for the OriginalCalledNumber AND if the SSF-CCF routes the call to an SS No. 7 trunk (for ISDN-UP signalling). + +Other AnalyseInformation Requirements. + +- If the SSF-CCF has associated a Business Group ID with the call and the call is routed over an SS No. 7 trunk, the SSF-CCF shall include this information in the Business Group parameter of the network specific ISDN-UP IAM (network operator specific). +- If the CalledPartyNumber or CallingPartyNumber parameter is included in the AnalyseInformation operation, that value shall be used subsequently for the call and the existing value replaced. + +### **3.3.5.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +## **3.3.6 ApplyCharging procedure** + +### **3.3.6.1 General description** + +This operation is used for interacting from the SCF with the SSF charging mechanisms. The "ApplyChargingReport" operation provides the feedback from the SSF to the SCF. + +As several connection configurations may be established during a call, a possibility exists for the "ApplyCharging" to be invoked at the beginning of each connection configuration, for each party. + +The charging scenarios supported by this operation are 4.1 and 4.2 (refer to Appendix II/Q.1214, "Charging scenarios"). + +#### **3.3.6.1.1 Parameters** + +- aChBillingChargingCharacteristics: + +This parameter specifies the charging related information to be provided by the SSF and the conditions on which this information has to be reported back to the SCF via the "ApplyChargingReport" operation. Its contents is network operator specific. + +- partyToCharge: + +This parameter indicates the party in the call to which the "ApplyCharging" operation should be applied. If it is not present, then it is applied to the A-party. + +### **3.3.6.2 Invoking Entity (SCF)** + +#### **3.3.6.2.1 Normal procedure** + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) The SLPI has determined that an "ApplyCharging" operation has to be sent. + +SCF Postconditions: + +- 1) No FSM state transition. +- 2) The SLPI is expecting "ApplyChargingReport" operations from the SSF. + +The SCSM-FSM is in state "Preparing SSF Instructions" or is in state "Queuing FSM". This operation is invoked by the SCF if a SLPI results in the request of interacting with the charging mechanisms within the SSF to get back information about the charging. + +#### **3.3.6.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### 3.3.6.3 Responding Entity (SSF) + +#### 3.3.6.3.1 Normal procedure + +SSF Preconditions: + +- The SSF-FSM is in one of the following states: + - "Waiting for Instructions" (state c); + - "Waiting for End of User Interaction" (state d); + - "Waiting for End of Temporary Connection" (state e); + - "Monitoring" (state f);or the assisting/hand-off SSF-FSM is in state: + - "Waiting for Instructions" (state b). + +SSF Postconditions: + +- No FSM state transition. + +On receipt of this operation, the SSF sets the charging data using the information elements included in the operation and acts accordingly. In addition, the SSF will start the monitoring of the end of the connection configuration and other charging events, if requested. + +#### 3.3.6.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### 3.3.7 ApplyChargingReport procedure + +#### 3.3.7.1 General description + +This operation is used by the SSF to report charging related information to the SCF as requested by the SCF using the 'ApplyCharging' operation. + +During a connection configuration the 'ApplyChargingReport' operation may be invoked on multiple occasions. For each call party and each connection configuration, the 'ApplyChargingReport' operation may be used several times. Note that at least one 'ApplyChargingReport' operation is to be sent at the end of the connection configuration charging process. + +The charging scenarios supported by this operation are 4.1 and 4.2 (refer to Appendix II/Q.1214, 'Charging scenarios'). + +##### 3.3.7.1.1 Parameters + +- CallResult: + +This parameter provides the SCF with the charging related information previously requested using the 'ApplyCharging' operation. The 'CallResult' will include the 'partyToCharge' parameter as received in the related 'ApplyCharging' operation to correlate the result to the request. The remaining content of 'CallResult' is network operator specific. Examples of these contents may be: bulk counter values, costs, tariff change and time of change, time stamps, durations, etc. + +#### 3.3.7.2 Invoking Entity (SSF) + +##### 3.3.7.2.1 Normal procedure + +SSF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) A charging event has been detected that was requested by the SCF via an 'ApplyCharging' operation. + +SSF Postconditions: + +- If the connection configuration does not change, then no FSM state transition shall occur. If the connection configuration changes, then the FSM shall move to: + - "Idle" state if there is no other EDP armed and no report requests are pending; or + - otherwise, shall remain in the same state. + +This operation is invoked if a charging event has been detected that was requested by the SCF. The 'ApplyChargingReport' operation only deals with charging events within the SSF itself. Examples of charging events may be: threshold value reached, timer expiration, tariff change, end of connection configuration, etc. + +### **3.3.7.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### **3.3.7.3 Responding Entity (SCF)** + +#### **3.3.7.3.1 Normal procedure** + +SCF preconditions: + +- An 'ApplyCharging' operation has been sent at the request of an SLPI and the SLPI is expecting an 'ApplyChargingReport' from the SSF. + +SCF postconditions: + +- No FSM state transition if further reports, including "EventReportBCSM" and "CallInformationReport", are expected, or Transition to the state "Idle" if the report is the last one and no "EventReportBCSM" or "CallInformationReport" is expected. + +On receipt of this operation the SLPI which is expecting this operation will continue. + +#### **3.3.7.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 the TCAP services used for reporting operation errors are described in 3.4. + +### **3.3.8 AssistRequestInstructions procedure** + +#### **3.3.8.1 General description** + +This operation is sent to the SCF by an SSF, which is acting as the assisting SSF in an assist or handoff procedure, or by a SRF. The operation is sent when the assisting SSF or SRF receives an indication from an initiating SSF containing information indicating an assist or handoff procedure. + +##### **3.3.8.1.1 Parameters** + +- correlationID: + +This parameter is used by the SCF to associate the 'AssistRequestInstructions' from the assisting SSF or by a SRF with the request from the initiating SSF. The value of the 'correlationID' may be extracted from the digits received from the initiating SSF or be all of the digits. + +- iPAvailable: + +See Recommendation Q.1290. This parameter is applicable to this operation only in the physical scenarios corresponding to assist with relay or handoff. The use of this parameter is network operator dependent. + +- iPSSPCapabilities: + +See Recommendation Q.1290. This parameter is applicable to this operation only in the physical scenarios corresponding to assist with relay or handoff. The use of this parameter is network operator dependent. + +### **3.3.8.2 Invoking Entity (SSF-SRF)** + +#### **3.3.8.2.1 Normal procedure** + +SSF Precondition: + +- An assist indication is detected by the assisting or Handoff SSF. + +SSF Postcondition: + +- The assisting or Handoff SSF waits for instructions. + +On receipt of an assist indication from the initiating SSF, the SSF or SRF shall assure that the required resources are available to invoke an 'AssistRequestInstructions' operation in the SSF-SRF and indicate to the initiating SSF that the call is accepted (refer to Recommendation Q.71). The 'AssistRequestInstructions' operation is invoked by the SSF or SRF after the call, which initiated the assist indication, is accepted. The assisting SSF-FSM transitions to state "Waiting For Instructions". + +#### **3.3.8.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.8.3 Responding Entity (SCF)** + +#### **3.3.8.3.1 Normal procedure** + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the initiating SSF in case of assist procedure. +- 2) The SCF waits for 'AssistRequestInstructions'. + +SCF Postcondition: + +- An SSF or SRF instruction is being prepared. + +On receipt of this operation in the SCSM state "Waiting for Assist Request Instructions", the SCP has to perform the following actions. + +If the 'AssistRequestInstructions' operation was received from an assisting SSF, and the resource is available, the SCSM prepares the 'ConnectToResource' and 'PlayAnnouncement' or 'PromptAndCollectUserInfo' to be sent to the assisting SSF. + +The SCF determines SSF-SRF by means of 'correlationID', 'destinationNumber' or network knowledge. + +If the 'AssistRequestInstructions' operation was received from a SRF, and the resource is available, the SCSM prepares the 'PlayAnnouncement' or 'PromptAndCollectUserInfo' to be sent to the SRF. + +On receipt of this operation from the Handoff SSF, the SCSM associated with the Handoff SSF transits from the "Idle" state to the "Preparing SSF Instructions" state. + +#### **3.3.8.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.9 Bind procedure** + +#### **3.3.9.1 General description** + +The X.500 'Bind' operation is used by the SDF to create an authenticated association between an SCF and an SDF on behalf of the end user. It carries the authentication information of the end user if any. For a full description of the Bind operation, see 8.1/X.511. + +##### **3.3.9.1.1 Parameters** + +See 8.1.2/X.511 and 8.1.3/X.511. + +### **3.3.9.2 Invoking Entity (SCF)** + +#### **3.3.9.2.1 Normal procedure** + +SCF Preconditions: + +- SCSM: "Idle". + +SCF Postconditions: + +- 1) SCSM: "SDF Bound" in case of success. +- 2) SCSM: "Idle" in case of failure. + +When the SCSM is in the state "Idle" and a need of the service logic to interrogate an SDF exists, an internal event occurs. This event, called (e1) Bind\_Request, causes a transition to the state "Wait for Subsequent Request" and other operations are awaited. Until the application process has not indicated by a delimiter that the Bind should be sent, the SCSM remains in the state "Wait for Subsequent Requests" and the operation is not sent. The reception of the delimiter causes a transition to the state "Wait for Bind result" through the internal transition (e3) Request\_to\_SDF\_with\_Bind. The operation is sent to the SDF. The SCSM waits for the response from the SDF. The reception of the response [(E5) Response\_from\_SDF\_with\_Bind] to the Bind operation previously issued to the SDF causes a transition of the SCF to the state "SDF Bound" if the result of the Bind operation is positive. Otherwise the reception of an error [(E4) Bind\_Error] moves back the SCSM to the state "Idle". + +#### **3.3.9.2.2 Error handling** + +Generic error handling for the operation related errors is described in 8.1.4/ X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +### **3.3.9.3 Responding Entity (SDF)** + +#### **3.3.9.3.1 Normal procedure** + +SDF Preconditions: + +- SDSM: "Idle". + +SDF Postconditions: + +- 1) SDSM: "SCF Bound" (success). +- 2) SDSM: "Idle" (failure). + +The SDF is initially in the state "Idle". After accepting the external event (E1) Bind\_from\_SCF caused by the reception of a 'Bind' operation from the SCF, a transition to state "Bind Pending" occurs. The SDF performs the Bind operation according to the contents of the Bind argument. Once the SDF has completed the 'Bind' operation, the result or error indication is returned to the SCF. The SDF returns to the state "Idle" if the Bind fails or to the state "SCF Bound" if the Bind is successful. Should the Bind request succeed, the result returned may consist of credentials of the DirectoryBindResult. These credentials allow the user to establish the identity of the Directory. They allow information identifying the DSA (that is directly providing the Directory service) to be conveyed to the DUA. The credentials are of the same form (i.e. name, password) as those supplied by the user. + +#### **3.3.9.3.2 Error handling** + +Generic error handling for the operation related errors is described in 8.1.4/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +### **3.3.10 CallGap procedure** + +#### **3.3.10.1 General description** + +This operation is used to request the SSF to reduce the rate at which specific service requests are sent to the SCF. + +### 3.3.10.1.1 Parameters + +a) gapCriteria: + +This parameter identifies the criteria for a call to be subject to call gapping. + +i) calledAddressValue: + +This parameter indicates that call gapping will be applied when the leading digits of the dialled number of a call attempt match those specified in "gapCriteria". + +ii) gapOnService: + +This parameter indicates that call gapping will be applied when the "servicekey" of a call attempt match those specified in "gapCriteria". + +iii) calledAddressAndService: + +This parameter indicates that call gapping will be applied when the "serviceKey" and the leading digits of the dialled number of a call attempt match those specified in "gapCriteria". + +iv) callingAddressAndService: + +This parameter indicates that call gapping will be applied when the "serviceKey" and the leading digits of the calling party number or the location number of a call attempt match those specified in "gapCriteria". + +b) gapIndicators: + +This parameter indicates the gapping characteristics. + +i) duration: + +Duration specifies the total time interval during which call gapping for the specified gap criteria will be active. + +A duration of 0 indicates that gapping is to be removed. + +A duration of -1 indicates an infinite duration. + +A duration of -2 indicates a network specific duration. + +Other values indicate duration in seconds. + +ii) gapInterval: + +This parameter specifies the minimum time between calls being allowed through. + +An interval of 0 indicates that calls meeting the gap criteria are not to be rejected. + +An interval of -1 indicates that all calls meeting the gap criteria are to be rejected. + +Other values indicate interval in milliseconds. + +c) controlType: + +This parameter indicates the reason for activating call gapping. + +The "controlType" value "sCPOverloaded" indicates that an automatic congestion detection and control mechanism in the SCP has detected a congestion situation. + +The "controlType" value "manuallyInitiated" indicates that the service and or network/service management centre has detected a congestion situation, or any other situation that requires manually initiated controls2). + +--- + +2) The controlType "manuallyInitiated" will have priority over "sCPOverloaded" call gap. + +It should be noted that also non-IN controlled traffic control mechanism can apply to an exchange with the SSF functionality. The non-IN controlled traffic control may also have some influence to the IN call. Therefore it is recommended to take measures to coordinate several traffic control mechanisms. The non-IN controlled traffic control and coordination of several traffic control mechanisms are out of the scope of INAP. + +d) gapTreatment: + +This parameter indicates how calls that were stopped by the call gapping mechanism shall be treated. + +i) informationToSend: + +This parameter indicates an announcement, a tone or display information to be sent to the calling party. At the end of information sending, the call shall be released. + +• inbandInfo: + +This parameter specifies the inband information to be sent. + +– messageID: + +This parameter indicates the message(s) to be sent, it can be one of the following: + +1) elementaryMessageID: + +This parameter indicates a single announcement. + +2) text: + +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech). This parameter consist of two subparameters, messageContent and attributes. The attributes of text may consist of items such as language. + +3) elementaryMessageIDs: + +This parameter specifies a sequence of announcements. + +4) variableMessage: + +This parameter specifies an announcement with one or more variable parts. + +– numberOfRepetitions: + +This parameter indicates the maximum number of times the message shall be sent to the end-user. + +– duration: + +This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. ZERO indicates endless repetition. + +– interval: + +This parameter indicates the time interval in seconds between repetitions, i.e. the time between the end of the announcement and the start of the next repetition. This parameter can only be used when the number of repetitions is > 1. + +• tone: + +This parameter specifies a tone to be sent to the end-user. + +– toneID: + +This parameter indicates the tone to be sent. + +– duration: + +This parameter indicates the time duration in seconds of the tone to be sent. ZERO indicates infinite duration. + +• displayInformation: + +This parameter indicates a text string to be sent to the end-user. This information can not be received by a PSTN end-user. + +ii) releaseCause: + +This parameter indicates that the call shall be released using the given release cause. See Recommendation Q.762. + +iii) both: + +This parameter indicates inband info, a tone or display information to be sent to the calling party. At the end of information sending, the call shall be released, using the given release cause. + +### 3.3.10.2 Invoking Entity (SCF) + +#### 3.3.10.2.1 Normal procedure + +SCF Preconditions: + +- The SCF detects an overload, condition persists and call gapping has to be initiated at the SSF; or +- the SCF receives a manually initiated call gapping request. + +SCF Postcondition: + +- The SCME-FSM remains in the same state upon issuing the "CallGap" operation. + +A congestion detection and control algorithm monitors the load of SCP resources. After detection of a congestion situation the parameters for the "CallGap" operation are provided. + +If the congestion level changes, new 'CallGap' operations may be sent for active gap criteria but with new gap interval. If no congestion is detected, gapping may be removed. + +A manual initiated call gap will take prevail over an automatic initiated call gap. + +#### 3.3.10.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +### 3.3.10.3 Responding Entity (SSF) + +#### 3.3.10.3.1 Normal procedure + +SSF Preconditions: + +- call gapping for gapCriteria is not active; or +call gapping for gapCriteria is active. + +SSF Postconditions: + +- 1) the SSME-FSM is in the state "Non call associated treatment"; +- 2) call gapping for gapCriteria is activated; or +call gapping for gapCriteria is renewed; or +call gapping for gapCriteria is removed. + +If there is no already existing SSME-FSM for the gap criteria provided, a new SSME-FSM is created. This SSME-FSM enters the state 'Non-call associated treatment' and initializes call gapping for the specified IN calls. The parameters 'gapIndicators', 'controlType' and 'gapTreatment' for the indicated gap criteria will be set as provided by the 'CallGap' operation. + +In general, the manuallyInitiated call gapping will prevail over automatically initiated ('sCPOverloaded'). More specifically, the following rules will be applied in the SSF to manage the priority of different control Types associated with the same 'gapCriteria': + +- If an SSME-FSM already exists for the 'gapCriteria' provided, then: + - 1) If the (new) 'controlType' equals an existing 'controlType', then the new parameters (i.e. 'gapIndicators' and 'gapTreatment') will overwrite the existing parameter values. + - 2) If the (new) 'controlType' is different than the existing 'controlType', then the new parameters (i.e. 'controlType', 'gapIndicators', and 'gapTreatment') will be appended to the appropriate SSME-FSM (in addition to the existing parameters). The SSME-FSM remains in the state "Non-Call Associated Treatment". + +If the SSF meets a TDP, it will check if call gapping was initiated either for the 'serviceKey' or for the 'calledAddressValue' assigned to this TDP. If not, an 'InitialDP' or a DP-specific operation can be sent. In case call gapping was initiated for 'calledAddressAndService' or 'callingAddressAndService' and the 'serviceKey' matches, a + +check on the 'calledAddressValue' and 'callingAddressValue' – and optionally 'locationNumber' – for active call gapping is performed. If not, an 'InitialDP' or a DP-specific operation can be sent. + +In case of gapping on 'callingAddressAndService' and the parameter 'locationNumber' is present, gapping will be performed on 'locationNumber' instead of 'callingAddressValue'. + +If a call to a controlled number matches only one 'gapCriteria', then the corresponding control is applied. If both 'manuallyInitiated' and 'sCPOverload' controls are active, then only the manually initiated control will be applied. + +If a call to a controlled called number matches several active 'gapCriteria', then only the 'gapCriteria' associated with the longest called party number should be used, and the corresponding control should be applied. For example, the codes 1234 and 12345 are under control. Then the call with 123456 is subject to the control on 12345. Furthermore, if both 'manuallyInitiated' and 'sCPOverloaded' 'controlTypes' are active for this 'gapCriteria', then the 'manuallyInitiated' control will be applied. + +If call gapping shall be applied and there is no gap interval active, an "InitialDP" or a DP-specific operation can be sent including the "cGEncountered" parameter according to the specified controlType. A new gap interval will be initiated as indicated by "gapInterval". + +If a gap interval is active, no "InitialDP" or a DP-specific operation is sent and the call is treated as indicated by "gapTreatment". + +The call gap process is stopped if the indicated duration equals ZERO. + +If call gapping proceeds then the SSME-FSM remains in the state "Non-call associated treatment". Otherwise, the SSME-FSM moves to state "idle management". + +### **3.3.10.3.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +## **3.3.11 CallInformationReport procedure** + +### **3.3.11.1 General description** + +This operation is used to send specific call information for a single call to the SCF as requested by the SCF in previous 'CallInformationRequest' operation. The report is sent at the end of a call which is indicated by one of the events specified below. + +#### **3.3.11.1.1 Parameters** + +- requestedInformationList: + +According to the requested information, the SSF sends the appropriate types and values to the SCF. + +#### **3.3.11.2 Invoking Entity (SSF)** + +##### **3.3.11.2.1 Normal procedure** + +SSF Preconditions: + +- 1) At least one party disconnects from a call or call set-up is not completed. +- 2) Requested call information has been collected. +- 3) 'CallInformationReport' is pending due to a previously received 'CallInformationRequest' operation. +- 4) A control relationship exists between the SCF and the SSF. + +SSF Postcondition: + +- The SSF-FSM shall move to the "Idle" state in the case where no other report requests are pending and no EDPs are armed, otherwise the SSF-FSM shall remain in the same state. + +If the SSF-FSM executes a state transition caused by one of the following events: + +- A party release; +- A party abandon; +- B party release; +- B party busy; +- SSF no answer timer expiration; +- route select failure indicated by the network; +- release call initiated by the SCF; + +and 'CallInformationRequest' is pending, then one 'CallInformationReport' operation is sent to the SCF containing all information requested. + +If a 'CallInformationReport' has been sent to the SCF then no 'CallInformationReport' is pending, i.e. a further 'CallInformationReport', for example in the case of follow-on, has to be explicitly requested by the SCF. + +If an event causing the 'CallInformationReport' is also detected by an armed EDP-R, then immediately after 'CallInformationReport', the corresponding 'EventReportBCSM' has to be sent. + +If an event causing the 'CallInformationReport' is also detected by an armed EDP-N, then immediately before 'CallInformationReport', the corresponding 'EventReportBCSM' has to be sent. + +### **3.3.11.2.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +### **3.3.11.3 Responding Entity (SCF)** + +#### **3.3.11.3.1 Normal procedure** + +SCF Preconditions: + +- 1) An SLPI is expecting 'CallInformationReport'. +- 2) A control relationship exists between the SCF and the SSF. + +SCF Postcondition: + +- The SLPI may be further executed. + +In any state (except 'Idle') the SCSM may receive 'CallInformationReport' from the SSF, when the 'CallInformationReport' is outstanding. + +If 'CallInformationReport' is outstanding and the service logic program indicates that the processing has been completed, the SCSM remains in the same state until it receives the 'CallInformationReport' operation. + +When the SCF receives the 'CallInformationReport' operation and the service logic processing has been completed, then the SCSM moves to the "Idle" state. + +When the SCF receives the 'CallInformationReport' operation and the service logic processing has not been completed yet, then the SCSM remains in the same state (EventReportBCSM or ApplyChargingReport pending). + +#### **3.3.11.3.2 Error handling** + +If requested information is not available, a 'CallInformationReport' will be sent, indicating the requested information type, but with 'RequestedInformationValue' filled in with an appropriate default value as specified by the network operator. + +Operation related error handling is not applicable, due to class 4 operation. + +### 3.3.12 CallInformationRequest procedure + +#### 3.3.12.1 General description + +This operation is used to request the SSF to record specific information about a single call and report it to the SCF using the 'CallInformationReport' operation. + +##### 3.3.12.1.1 Parameters + +- requestedInformationTypeList: + +This parameter specifies a list of specific items of information which is requested. + +The list may contain: + +- callAttemptElapsedTime: +This parameter indicates the duration between the end of INAP processing of operations initiating call set-up ('Connect', 'AnalyseInformation', 'CollectInformation', 'Continue' and 'SelectRoute') and the received answer indication from the called party side. +In case of unsuccessful call set-up the network event indicating the unsuccessful call set-up stops the measurement of 'callAttemptElapsedTime'. +- callStopTime: +This parameter indicates the time stamp when the connection is released. +- callConnectedElapsedTime: +This parameter indicates the duration between the received answer indication from the called party side and the release of the connection. +- calledAddress +This parameter indicates the incoming called party address that was received by the SSF (i.e. before translation by the SCF) and is as available on the UNI or NNI and interpreted as per the numbering plan. +- releaseCause: +See Recommendation Q.762. + +Any set of these values can be requested. + +#### 3.3.12.2 Invoking Entity (SCF) + +##### 3.3.12.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) The SLPI has determined that a 'CallInformationRequest' operation has to be sent by the SCF. + +SCF Postcondition: + +- The SLPI is expecting a 'CallInformationReport' from SSF. + +When the service logic program requests call information, the SCF sends the 'CallInformationRequest' operation to the SSF to request the SSF to provide call related information. + +The 'CallInformationRequest' operation specifies the information items to be provided by the SSF. + +##### 3.3.12.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.12.3 Responding Entity (SSF) + +#### 3.3.12.3.1 Normal procedure + +SSF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) A control relationship exists between SSF and SCF. + +SSF Postconditions: + +- 1) Requested call information is retained by the SSF. +- 2) The SSF is waiting for further instructions. + +The SSF may receive the "CallInformationRequest" operation within an existing Call Associated (CA) dialogue only. + +The "CallInformationRequest" operation is accepted by the SSF Finite State Machine (SSF-FSM) only in the state "Waiting for Instructions". The operation does not lead to any transition to another state. + +The SSF allocates a record and stores the requested information if already available and prepares the recording of information items, that will become available later like for example "callStopTimeValue". + +#### 3.3.12.3.2 Error handling + +In any other than the "Waiting for Instruction" state the "CallInformationRequest" operation will be handled as an error with the error code "UnexpectedComponentSequence". + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.13 Cancel procedure + +#### 3.3.13.1 General description + +The SCF uses this class 2 operation to request the SRF-SSF to cancel a correlated previous operation. + +The SRF operation to be deleted can be either a 'PlayAnnouncement' operation or a 'PromptAndCollectUserInfoInformation' operation. + +The cancellation of an operation is indicated via a respective error indication, "Cancelled", to the invoking entity of the cancelled "PlayAnnouncement" or "PromptAndCollectUserInfoInformation" operation. The 'Cancel' operation can also be used to cancel all outstanding requests and enable the state machine (SSF) to go to idle. In this case the 'Cancel' operation does not specify any specific operation to be cancelled. + +##### 3.3.13.1.1 Parameters + +- invokeID: +This parameter specifies which operation is to be cancelled, i.e. PromptAndCollectUserInfoInformation or PlayAnnouncement. +- allRequests: +This parameter indicates that all active requests for EDP reports (generic or DP specific), "ApplyChargingReport" and "CallInformationReport" should be cancelled. + +NOTE – This cancellation is different from the invokeID based cancel mechanism described above. + +#### 3.3.13.2 Invoking Entity (SCF) + +##### 3.3.13.2.1 Normal procedure + +The SCF may either invoke this operation to the SSF or to the SRF, different conditions will prevail in each case. + +SCF Preconditions: + +- 1) a control relationship exists between the SCF and the SSF-SRF; +- 2) an SLPI in the "Waiting for response from SRF" state has determined that a previously requested operation is to be cancelled; or +an SLPI has determined that it is no longer interested in any reports or notifications from the SSF and that the control relationship should be ended. + +SCF Postcondition: + +- the SLPI remains in the "Waiting for Response from SRF" state; or +in case all requests are cancelled, the control relationship with the concerned FE (SSF) is ended and the SCSM-FSM returns to "Idle" state. + +### **3.3.13.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.13.3 Responding Entity (SRF)** + +#### **3.3.13.3.1 Normal procedure** + +SRF Precondition: + +- A PlayAnnouncement or PromptAndCollectUserInfo operation has been received and the SRF is in the "User Interaction" state. + +SRF Postcondition: + +- The execution of the PlayAnnouncement or PromptAndCollectUserInfo operation has been aborted and the SRF remains in the "User Interaction" state. + +#### **3.3.13.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.13.4 Responding Entity (SSF)** + +#### **3.3.13.4.1 Normal procedure** + +SSF Precondition: + +- The SSF-FSM is in the state "Waiting for Instructions" or "Monitoring". + +SSF Postcondition: + +- 1) all active requests for reports and notifications have been cancelled; +- 2) in case the SSF-FSM was in state "Monitoring" it shall return to idle; or +in case the SSF-FSM was in state "Waiting for Instructions" it will remain in that state. + +A subsequent call-processing operation will move the SSF-FSM state to "Idle". The call, if in active state, is further treated by SSF autonomously as a normal (non-IN-) call. + +#### **3.3.13.4.2 Error handling** + +Sending of return error on cancel is not applicable in the cancel "allRequests" case. Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.14 CollectedInformation procedure** + +#### **3.3.14.1 General description** + +This operation is sent by the SSF after detection of a TDP-Rx, TDP-N, EDP-R, or EDP-N in the originating BCSM, to indicate availability of complete initial package/dialling string from the originating party. + +### 3.3.14.1.1 Parameters + +- **serviceAddressInformation** (triggerType, serviceKey, miscCallInfo): + +See Recommendation Q.1290. The currently defined events applicable to the Collected\_Information DP are Off\_Hook\_Delay, Channel\_Setup\_PRI, and Shared\_Interoffice\_Trunk. The miscCallInfo indicates that a request for instructions has been issued to the SCF and the category for the trigger (line, group, office). The serviceKey is used in identifying the service logic to be invoked. + +- **bearerCapability**: + +This parameter indicates the type of bearer capability connection to the user. Refer to 6.4.4/Q.1214 for population rules for the bearer capability parameter. + +- **calledPartyNumber**: + +See Recommendation Q.762 Called Party Number signalling information. This parameter is used to identify the called party in the forward direction. + +- **callingPartyNumber**: + +See Recommendation Q.762 Calling Party Number signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartyNumber parameter. + +- **callingPartysCategory**: + +See Recommendation Q.762 Calling Party Category signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartysCategory parameter. + +- **iPSSPCapabilities**: + +See Recommendation Q.1290. + +- **iPAvailable**: + +See Recommendation Q.1290. + +- **iSDNAccessRelatedInformation**: + +This parameter contains (possibly multiple) information elements as per Recommendation Q.931. See Access Transport Parameter signalling information in Recommendations Q.762, Q.763 and Q.931. Refer to 6.4.4/Q.1214 for population rules for ISDN access related information. + +- **cGEncountered**: + +See Recommendation Q.1290. + +- **locationNumber**: + +This parameter is used to convey the geographical area address for mobility services, see Recommendation Q.762. It is used when the 'callingPartyNumber' does not contain any information about the geographical location of the calling party (e.g. origin dependent routing when the calling party is a mobile subscriber). + +- **serviceProfileIdentifier**: + +See Annex A/Q.932. See 6.4.4/Q.1214 for population rules for serviceProfileIdentifier. + +- **terminalType**: + +See Recommendation Q.1290. Identifies the terminal type so that the SCF can specify, to the SRF, the appropriate type of capability (voice recognition, DTMF, display capability, etc.). + +- **chargeNumber**: + +See Recommendation Q.1290. See 6.4.4/Q.1214 for population rules for chargeNumber. + +- **servingAreaID**: + +See Recommendation Q.1290. + +- dialledDigits: +See Recommendation Q.1290. See 6.4.4/Q.1214 for population rules for dialledDigits. +- callingPartyBusinessGroupID: +See Recommendation Q.1290. +- callingPartySubaddress: +See Recommendation Q.931 for details. +- callingFacilityGroup: +See Recommendation Q.1290. +- callingFacilityGroupMember: +See Recommendation Q.1290. +- originalCalledPartyID: +See Recommendation Q.762 Original Called Number signalling information. Refer to 6.4.4/Q.1214 for population rules for the originalCalledPartyID parameter. +- prefix: +See Recommendation Q.1290. +- redirectingPartyID: +Contains the directory number of the last redirecting party. +- redirectionInformation: +See Recommendation Q.763 Redirection Information signalling information. +- travellingClassMark: +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules for the travellingClassMark parameter. +- featureCode: +See Recommendation Q.1290. +- accessCode: +See Recommendation Q.1290. +- carrier: +See Recommendation Q.1290. + +### 3.3.14.2 Invoking Entity (SSF) + +#### 3.3.14.2.1 Normal procedure + +SSF Preconditions for TDP-R and TDP-N: + +- 1) An event resulting in trigger criteria being met has occurred at the Collected\_Information DP (e.g. Off\_Hook\_Delay, Channel\_Setup\_PRI, Shared\_Interoffice\_Trunk). +- 2) Call gapping and SS No. 7 overload are not in effect for the call, and the call is not to be filtered. + +SSF Preconditions for EDP-R and EDP-N: + +- 1) A control relationship has been established and the SCF requests Collected\_Information as EDP-R or EDP-N. +- 2) Call processing reaches the Collected\_Information DP. + +SSF Postcondition for TDP-R: + +- A control relationship has been established and the SSF waits for instructions from the SCF. + +SSF post-condition for EDP-R: + +- The control relationship continues and the SSF waits for instructions from the SCF. + +SSF post-condition for TDP-N and EDP-N: + +- Call processing continues at the Analysed\_Information PIC. + +The SSF/CCF collects enough information (e.g. a feature code, prefix, address information, etc.) from the originating access to process the call. This information is collected according to the dialling plan assigned to the originating access: + +- 1) For a call from a non-ISDN line, the SSF-CCF sends an in-band prompt (e.g. dial tone) to prompt the user, attaches a digit receiver, collects digits and applies inter-digit timing. From a non-ISDN line, the "dialling plan in force" is the dialling plan assigned to the line. For example, if a Private Dialling Plan (PDP) (sometimes referred to as a Customized Dialling Plan) is assigned, then that PDP is considered to be the "dialling plan in force". If, on a given call, the caller dials an access code to escape to a Public Office Dialling Plan (PODP) (i.e. Recommendation E.164), then that PODP is considered to be the "dialling plan in force". In this case, call processing can not return to the PDP at this SSF-CCF. If a PDP is not assigned, then a PODP is assumed to be the "dialling plan in force". +- 2) For a call from an ISDN user following *en bloc* sending procedures (i.e. all the information necessary to process the call, which can include a feature code, feature activator, called party number, etc., is included in the SETUP message), no further action is taken on the originating access interface. For a call from an ISDN user not following *en bloc* sending procedures, the SSF-CCF prompts the user with a SETUP ACKnowledge message to send more information. Overlap sending procedures are then followed. + +For a call from an ISDN BRI or PRI, the "dialling plan in force" is determined by the type of number and numbering plan field of the called party number information element. If this field indicates "unknown" or if the keypad information element is used, then the dialling plan is determined as defined for non-ISDN lines above. + +- 3) For conventional trunks, if required by the trunk type, an appropriate start signal is returned. A digit receiver is attached, digits are collected and inter-digit timing is applied. + +For a call from a conventional trunk, the number received in signalling is expected to be a non-private number that conforms to Recommendation E.164. + +- 4) For SS No. 7 trunks, all the information may be available in the IAM or may come in subsequent messages (i.e. overlap sending). A check is made to ensure that the IAM contains all the information necessary to process the call. + +For a call from an SS No. 7 trunk, the number received in signalling is expected to be a non-private number that conforms to Recommendation E.164. + +- 5) For private-facility trunks, if required by the private-facility trunk group, an appropriate start signal is returned. Depending on the private-facility trunk group, digits may be collected. + +Following the trigger detection (due to the DP criteria assigned being met) related to an armed TDP-R or TDP-N in the BCSM at the Collected\_Information DP, caused by a call origination attempt, the SSF checks if call gapping, SS No. 7 overload, or service filtering are not in effect for the related call segment. If these conditions are met, then the CollectedInformation operation is invoked by the SSF. The address of the SCF to which the CollectedInformation has to be sent is determined on the basis of trigger instance related data. The SSF provides parameters as per rules defined in 6.4.4/Q.1214. For TDP-R, a control relationship is established to the SCF and the SSF application timer $T_{\text{SSF}}$ is set when the SSF sends the CollectedInformation operation for requesting instructions from the SCF. $T_{\text{SSF}}$ is used to prevent excessive call suspension time. For EDP-R, $T_{\text{SSF}}$ is also used. For TDP-N and EDP-N, no new control relationship is established. Hence, $T_{\text{SSF}}$ is not set. + +### 3.3.14.2.2 Error handling + +If the destination SCF is not accessible, then the call is given final treatment (other treatments are for further study). On expiration of $T_{\text{SSF}}$ before receiving any operation, the SSF aborts the interaction with the SCF and the call is given final treatment (e.g. routing to a final announcement). If the calling party abandons after the sending of the CollectedInformation operation, then the SSF aborts the control relationship after the first answer message from the SCF has been received. If the caller abandons the call and $T_{\text{SSF}}$ is running, then the Transaction ID is held open until $T_{\text{SSF}}$ is satisfied or expires. If the caller abandons the call and Timer $T_{\text{SSF}}$ is not running, then procedures to support the encountered situation (e.g. procedures to report the condition of Caller Abandon, procedures associated with the condition of $T_{\text{SSF}}$ Timer Expired), shall be followed. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.14.3 Responding Entity (SCF) + +#### 3.3.14.3.1 Normal procedure + +SCF Preconditions (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or + +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or + +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +For TDP-R, on receipt of the CollectedInformation operation, the SCSM moves from "Idle" state to the state "Preparing SSF Instructions". A control relationship to the related SSF is created. A Service Logic Program Instance (SLPI) is invoked for process the CollectedInformation operation based on the triggerType parameter. By means of this control relationship, the SCF may influence the Basic Call Processing in accordance with the service logic invoked. The actions to be performed in the SLPI depend on the parameters conveyed via this operation and the SLPI (i.e. the requested IN service itself). + +For EDP-R, on receipt of the CollectedInformation operation, the SCSM moves from "Waiting for Notification" state to the state "Preparing SSF Instructions". A control relationship to the related SSF continues. A Service Logic Program Instance (SLPI) is invoked for process the CollectedInformation operation based on the triggerType parameter. By means of this control relationship, the SCF may influence the Basic Call Processing in accordance with the service logic invoked. The actions to be performed in the SLPI depend on the parameters conveyed via this operation and the SLPI (i.e. the requested IN service itself). + +For TDP-N, the SCSM remains in state "Idle" and takes appropriate action on the notification. + +For EDP-N, if this is the last event notification and there are no CallInformationReport and ApplyChargingReport pending, the SCSM returns to state "Idle". Otherwise, it remains in state "Waiting for Notification or Report". Appropriate actions on the notification are taken. + +### **3.3.14.3.2 Error handling** + +If the CollectedInformation operation is rejected, then the SCSM remains in the same state. The maintenance function is informed and no SLPI is invoked. Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.15 CollectInformation procedure** + +#### **3.3.15.1 General description** + +The CollectInformation is a class 2 operation which is used by the SCF to request the call to return to the Collect\_Information PIC, and then perform the basic originating call processing actions associated with this PIC (e.g. the checking of information in the CalledPartyNumber parameter with the supported dialling plan). This operation uses only the resources of the SSF-CCF to collect the information. The use of this operation is only appropriate for a call which had not yet left the set-up phase. + +When the user provides calledPartyNumber, Collect\_Information PIC processing includes collecting of destination information from a calling party. When the calledPartyNumber is included (as dialledDigits) in the Collect\_Information operation, further collection is not performed (e.g. SSF-CCF checks the provided calledPartyNumber against the supported dialling plan). + +#### **3.3.15.1.1 Parameters** + +- alertingPattern: +See Recommendation Q.1290. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber. +- numberingPlan: +See Recommendation Q.763 Numbering Plan for encoding. +- originalCalledPartyID: +See Recommendation Q.762 Original Called Number signalling information. +- travellingClassMark: +See Recommendation Q.1290. This parameter contains the travelling class mark information of the calling party. It uses the LocationNumber format which is based on the Q.763 Location Number format. +- callingPartyNumber: +See Recommendation Q.762. +- dialledDigits: +This parameter is applied against the supported dialling plan in the SSF-CCF and, if valid, is used in routing of the call. If provided, it replaces the calledPartyNumber for the call. + +#### **3.3.15.2 Invoking Entity (SCF)** + +##### **3.3.15.2.1 Normal procedure** + +SCF Precondition: + +- An SLPI has determined that more information from the calling party is required to enable processing to proceed. + +SCF Postcondition: + +- SLPI execution is suspended pending receipt of dialled digits. + +This operation is invoked in the SCSM-FSM state "Preparing SSF Instructions" if the SLP requires additional information to progress the call. It causes a transition of the FSM to the state "Waiting for Notification or Report". + +### **3.3.15.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.15.3 Responding Entity (SSF)** + +#### **3.3.15.3.1 Normal procedure** + +SSF Precondition: + +- A TDP Request has been invoked. + +SSF Postconditions: + +- 1) The SSF has executed a transition to the state "Monitoring". +- 2) The SSF performs the call processing actions to collect destination information from the calling party. This may include prompting the party with in-band or out-band signals. +- 3) Basic call processing is resumed at PIC 2. + +The operation is only valid in the state "Waiting for Instruction" and after having received an operation 'RequestReportBCSMEEvent' for DP2. The SSP has to perform the following actions: + +- The SSF cancels $T_{\text{SSF}}$ . +- When DP2 will be encountered, an 'EventReportBCSM' operation will be invoked, and the SSF-FSM will return to the state "Waiting for Instructions". + +#### **3.3.15.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4 . + +### **3.3.16 Connect procedure** + +#### **3.3.16.1 General description** + +This operation is used to request the SSF to perform the call processing actions to route a call to a specific destination. To do so, the SSF may use destination information from the calling party (e.g. dialled digits) and existing call set-up information (e.g. route index to a list of trunk groups) depending on the information provided by the SCF. + +In general, all parameters which are provided in a Connect operation to the SSF shall replace the corresponding signalling parameter in the CCF, if the relevant parameter has already been received in the CCF, and shall be used for subsequent call processing. Parameters which are not provided by the Connect operation shall retain their value (if already assigned) in the CCF for subsequent call processing. + +##### **3.3.16.1.1 Parameters** + +- destinationRoutingAddress: + +This parameter contains the list of called party numbers (see Recommendation Q.762) towards which the call is to be routed. The encoding of the parameter is defined in Recommendation Q.763. The 'destinationRoutingAddress' may include the 'correlationID' and 'scfID' if used in the context of a hand-off procedure, but only if 'correlationID' and 'scfID' are not specified separately. + +- alertingPattern: + +See Recommendation Q.1290. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber. + +- correlationID: + +This parameter is used by the SCF to associate the 'AssistRequestInstructions' operation from the assisting SSF with the Request from the initiating SSF. The 'correlationID' is used in the context of a hand-off procedure and only if the correlation id is not embedded in the 'destinationRoutingAddress'. The network operators has to decide about the actual mapping of this parameter on the used signalling system. + +- cutAndPaste: +This parameter is used by the SCF to instruct the SSF to delete (cut) a specified number of leading digits that it has received from the calling party and to paste the remaining dialled digits on to the end of the digits supplied by the SCF in the 'destinationRoutingAddress'. +- forwardingCondition: +Indicates the condition that must be met to complete the Connect operation. +- iSDNAccessRelatedInformation: +Carries the same information as the protocol element ISUP Access Transport parameter in Recommendation Q.762. +- originalCalledPartyID: +See Q.762 Original Called Number signalling information. The use of this parameter in the context of the 'Connect' operation is to be specified by the network operator. +- routeList: +This parameter is used to select the outgoing trunk group used for routing the call. A sequence of routes is provided to allow flexible routing for applications such as VPN without increasing the number of queries required for such applications. +- scfID: +See Recommendation Q.1290. The scfID is used in the context of a hand-off procedure and only if the SCF id is not embedded in the 'destinationRoutingAddress'. The network operator has to decide about the actual mapping of this parameter on the used signalling system. +- travellingClassMark: +The SCF uses the travellingClassMark parameter to provide essential route selection information to the SSF. The SSF uses this information to populate the outgoing ISUP-IAM message, the population and mapping of this parameter is network operator specific. +- carrier: +See Recommendation Q.1290. In this message, the carrier selection field is null (00000000) and Carrier ID indicates the carrier to use for the call. +- serviceInteractionIndicators: +This parameter contains indicators sent from the SCF to the SSF for control of the network based services at the originating exchange and the destination exchange. +- callingPartyNumber: +This parameter, if present, is used to identify the calling party for the call (see Q.762 Calling Party Number). It may be used for applications such as UPT, where only the SCF can verify the identity of the calling party. +- callingPartysCategory: +See Recommendation Q.762 Calling Party Category signalling information. +- redirectingPartyID: +This parameter, if present, indicates the last directory number the call was redirected from. +- redirectionInformation: +See Recommendation Q.763 Redirection Information signalling information. + +### 3.3.16.2 Invoking Entity (SCF) + +#### 3.3.16.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) An SLPI has determined that a 'Connect' has to be sent by the SCF. + +SCF Postcondition: + +- SLPI execution may continue. + +In the SCSM-FSM state "Preparing SSF Instructions", this operation is invoked by the SCF if the service logic results in the request to the SSF to route a call to a specific destination. If no event monitoring has been requested and no reports (CallInformationReport and ApplyChargingReport) have been requested in a previously sent operation, a SCSM-FSM transition to state "Idle" occurs. Otherwise, if event monitoring has been requested or any report (CallInformationReport and ApplyChargingReport) has been requested, the SCSM-FSM transitions to state "Waiting for Notification or Report". When the 'Connect' operation is used in the context of a hand-off procedure, the SCSM-FSM transitions to state "Idle". However, in this case, the SCF must maintain sufficient information in order to correlate the subsequent 'AssistRequestInstructions' operation (from the assisting SSF or SRF) to the existing SLPI. + +### 3.3.16.2.2 Error handling + +If reject or error messages are received, then the SCSM informs the SLPI and remains in the state "Preparing SSF Instructions". + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.16.3 Responding Entity (SSF) + +#### 3.3.16.3.1 Normal procedure + +SSF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Basic call processing has been suspended at a DP. +- 3) The SSF waits for instructions. + +SSF Postconditions: + +- 1) The SSF performs the call processing actions to route the call to the specified destination. +- 2) In the O-BCSM, when only address information is included in the Connect operation, call processing resumes at PIC 3. +- 3) In the O-BCSM, when address information and routing information is included in the Connect operation, call processing resumes at PIC 4. + +On receipt of this operation in the SSF-FSM state "Waiting for Instructions", the SSP performs the following actions: + +- The SSF cancels $T_{\text{SSF}}$ . +- If "cutAndPaste" is present, then the SSF deletes ("cut") from the dialled IN number the indicated number of digits and pastes the remaining dialled digits at the end of the "destinationRoutingAddress" parameter delivered by the SCF. The resulting directory number is used for routing to complete the related call. +- If "cutAndPaste" is not present, then the "destinationRoutingAddress" parameter delivered by the SCF is used for routing to complete the related call. Note that in the case of hand-off, this results in routing to an assisting SSP or IP. +- If the "callingPartyNumber" is supplied, this value may be used for all subsequent SSF processing. +- If no EDPs have been armed and neither a CallInformationReport nor an ApplyChargingReport has been requested, the FSM goes to state "Idle" (e9). Otherwise, the FSM goes to state "Monitoring" (e11). + +No implicit activation or deactivation of DPs occurs. + +Statistic counter(s) are not affected. + +Connect completes when the INAP processing of the operation is complete and before the SSP starts the processing necessary to select a circuit. + +Therefore, in order to detect route select failure after a "Connect" it is necessary to explicitly arm the "Route Select Failure" EDP before sending the "Connect" (although they may be in the same message). + +### **3.3.16.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.17 ConnectToResource procedure** + +#### **3.3.17.1 General description** + +This operation is used to connect a call from the SSF to a specialized resource. After successful connection to the SRF, the interaction with the caller can take place. The SSF relays all operations for the SRF and all responses from the SRF. + +##### **3.3.17.1.1 Parameters** + +- resourceAddress: + +This parameter identifies the physical location of the SRF. + +- iPRoutingAddress: + +This parameter indicates the routing address to set up a connection towards the SRF. + +- none: + +This parameter indicates that the call party is to be connected to a predefined SRF. + +- serviceInteractionIndicators: + +This parameter contain indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange. + +#### **3.3.17.2 Invoking Entity (SCF)** + +##### **3.3.17.2.1 Normal procedure** + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) The SLPI has determined that additional information from the call party is needed. +- 3) The call party is not connected to any other party. +- 4) The SCSM-FSM is in the state "Routing to Resource", substate "Determine Mode". +- 5) The SLPI has determined that the SRF can be accessed from the SSF. + +SCF Postconditions: + +- 1) The SCSM sends out a 'PlayAnnouncement' or 'PromptAndCollectUserInfo' operation accompanying the 'ConnectToResource' +- 2) The SCSM-FSM moves to the state "User Interaction". + +##### **3.3.17.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.17.3 Responding Entity (SSF) + +#### 3.3.17.3.1 Normal procedure + +SSF Preconditions: + +- 1) Basic call processing has been suspended at a DP and a control relationship has been established. +- 2) The SSF-FSM is in the state "Waiting for Instructions". + +SSF Postconditions: + +- 1) The call is switched to the SRF. +- 2) A control relationship to the SRF is established. +- 3) The SSF-FSM moves to the state "Waiting for End of User Interaction". If necessary, $T_{SSF}$ is set. + +NOTES + +- 1) Whether the $T_{SSF}$ is used or not in this case is network operator dependent. But it must be synchronized with $T_{SCF-SSF}$ in the SCSM. +- 2) The successful connection to the SRF causes a state transition in the SRF-FSM from "Idle" to "Connected". + +#### 3.3.17.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.18 Continue procedure + +#### 3.3.18.1 General description + +This operation is used to request the SSF to proceed with call processing at the DP at which it previously suspended call processing to await SCF instructions. The SSF continues call processing without substituting new data from the SCF. + +##### 3.3.18.1.1 Parameters + +None. + +#### 3.3.18.2 Invoking Entity (SCF) + +##### 3.3.18.2.1 Normal procedure + +SCF Precondition: + +- SCSM is in the state "Preparing SSF instructions". + +SCF Postcondition: + +- SCSM is in the state "Waiting for Notification or Request", in case monitoring was required, or in the state "Idle", in case no monitoring was required. + +The SCSM is in state "Preparing SSF instructions". The 'Continue' operation is invoked by a SLPI. This causes a SCSM transition to state "Idle" if no subsequent monitoring is required. However, if monitoring is required, like in the case of armed EDPs or outstanding report requests, the SCSM transitions to state "Waiting for Notification of Report". + +##### 3.3.18.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +#### 3.3.18.3 Responding Entity (SSF) + +##### 3.3.18.3.1 Normal procedure + +SSF Preconditions: + +- 1) BCSM: Basic call processing has been suspended at any DP. +- 2) SSF-FSM is in the state "Waiting for Instructions". + +SSF Postconditions: + +- 1) BCSM: Basic call processing continues. +- 2) SSF-FSM is in the state "Monitoring", because at least one EDP was armed, or a 'CallInformationReport' or 'ApplyChargingReport' was requested; or + +SSF-FSM is in the state "Idle", because no EDPs were armed and neither the 'CallInformationReport' nor the 'ApplyChargingReport' was requested. + +The SSF-FSM is in state "Waiting for instructions". The SSME-Control receives the 'Continue' operation and relays it to the appropriate SSF-FSM. The SSF-FSM transitions to state "Idle" in case no EDPs are armed and no outstanding report requests are present. The SSF-FSM transits to state "Monitoring" if at least one EDP is armed, or if there is at least one outstanding report request. Basic call processing is resumed. + +### 3.3.18.3.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 3.3.19 DisconnectForwardConnection procedure + +### 3.3.19.1 General description + +This operation is used in the following two cases: + +- 1) To clear a connection to a SRF + +This operation is used to explicitly disconnect a connection to a resource (SRF) established previously with a 'ConnectToResource' or an 'EstablishTemporaryConnection' operation. It is used for a forward disconnection from the SSF. An alternative solution is the backward disconnect from the SRF, controlled by the 'DisconnectFromIPForbidden' parameter in the 'PlayAnnouncement' and 'PromptAndCollectUserInfo' operations. + +- 2) To clear a connection to an assisting SSF + +This operation is sent to the non-assisting SSF of a pair of SSFs involved in an assist procedure. It is used to disconnect the temporary connection between the initiating SSF and the assisting SSF, and the assisting SSF and its associated SRF. + +#### 3.3.19.1.1 Parameters + +None. + +### 3.3.19.2 Invoking Entity (SCF) + +#### 3.3.19.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) An assist- or a relay procedure is in progress. +- 3) An SLPI has determined that a 'DisconnectForwardConnection' operation has to be sent by the SCF. + +SCF Postcondition: + +- SLPI execution may continue. + +The 'DisconnectForwardConnection' operation is used to instruct the SSF to disconnect the concerned forward connection to the assisting SSF or the physical entity containing the SRF. + +In the SCSM-FSM state "User Interaction", substate "Waiting for Response from the SRF", this operation is invoked by the SCF when the service logic determines that user interaction is finished and requests the SSF to disconnect the temporary connection to the assisting SSF or the SRF. The SCSM-FSM then transitions to state "Preparing SSF Instructions". + +### 3.3.19.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.19.3 Responding Entity (SSF) + +#### 3.3.19.3.1 Normal procedure + +SSF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Basic call processing has been suspended at a DP. +- 3) The initiating SSF is in the state "Waiting for End of User Interaction" or "Waiting for End of Temporary Connection". + +SSF Postconditions: + +- 1) The connection to the SRF or assisting SSF is released. +- 2) The SSF is waiting for instructions. + +The receipt of "DisconnectForwardConnection" results in disconnecting the assisting SSF or the physical entity containing the SRF from the concerned call. It does not release the connection from the SSF back to the end user. + +This operation is accepted in the SSF-FSM states "Waiting for End of Temporary Connection" or "Waiting for End of User Interaction". On receipt of this operation in these states, the SSF must perform the following actions: + +- The initiating SSF releases the connection to the assisting SSF or the relay SRF. +- The SSF resets $T_{\text{SSF}}$ . +- The SSF-FSM goes to state "Waiting for Instructions" (e8). + +NOTE – The successful disconnection to the SRF causes a state transition in the SRF-FSM to "Idle". A current order ("PlayAnnouncement" or "PromptAndCollectUserInformation") is cancelled and any queued order ("PlayAnnouncement" or "PromptAndCollectUserInformation") is discarded. + +#### 3.3.19.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.20 EstablishTemporaryConnection procedure + +#### 3.3.20.1 General description + +This operation is used to create a connection between an initiating SSF and an assisting SSF as part of a service assist procedure. It can also be used to create a connection between a SSF and a SRF, for the case where the SRF exists in a separately addressable physical entity. + +##### 3.3.20.1.1 Parameters + +- assistingSSPIPRoutingAddress: + +This parameter indicates the destination address of the SRF for assist procedure. The 'assistingSSPIPRoutingAddress' may contain embedded within it, a 'correlationID' and 'scfID', but only if 'correlationID' and 'scfID' are not specified separately. + +- correlationID: + +This parameter is used by the SCF to associate the 'AssistRequestInstructions' from the assisting SSF (or the SRF) with the Request from the initiating SSF. The 'correlationID' is used only if the correlation id is not embedded in the 'assistingSSPIPRoutingAddress'. The network operator has to decide about the actual mapping of this parameter on the used signalling system. + +- scfID: +See Recommendation Q.1290. The 'scfID' is used only if the SCF id is not embedded in the 'assistingSSPIPRoutingAddress'. The network operator has to decide about the actual mapping of this parameter on the used signalling system. +- carrier: +See Recommendation Q.1290. In this message, the carrier selection field is null (00000000) and Carrier ID indicates the carrier to use for the call. +- serviceInteractionIndicators: +This parameter contain indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange. + +### 3.3.20.2 Invoking Entity (SCF) + +#### 3.3.20.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) The service logic has determined that a connection is needed between the SSF and SRF or between the SSF and an assisting SSF. +- 3) The call party is not connected to any other party. + +SCF Postcondition: + +- The SCF is "Waiting for Assist Request Instructions". + +In the SCSM-FSM state "Routing to Resource", this operation is invoked by the SCF when the service logic determines that an assisting SSF or a Direct SCF-SRF relation is needed. The SCSM-FSM then transitions to state "Waiting for Assist Request Instructions". + +#### 3.3.20.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.20.3 Responding Entity (SSF) + +#### 3.3.20.3.1 Normal procedure + +SSF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Basic call processing has been suspended at DP 1,2,3,4,5,6,7,12,13,14, or 15. +- 3) The SSF waits for instructions. +- 4) The SSF is not an assisting SSF. + +SSF Postconditions: + +- 1) The SSF performs the call processing actions to route the call to the assisting SSF or SRF according to the 'assistingSSPIPRoutingAddress' requested by the SCF. +- 2) The SSF waits for end of temporary connection. + +On receipt of this operation in the SSF-FSM state "Waiting for Instructions", the SSP has to perform the following actions: + +- Reset the $T_{\text{SSF}}$ (optional). +NOTE – This "optional" means that the application timer $T_{\text{SSF}}$ is optionally set. Whether it is used or not is network operator dependent. But it must be synchronized with $T_{\text{SCF-SSF}}$ in the SCSM. +- Route the call to assisting SSF or SRF using 'assistingSSPIPRoutingAddress'. +- The SSF-FSM goes to state "Waiting for End of Temporary Connection" (e7). + +### **3.3.20.3.2 Error handling** + +Until the connection set-up has been accepted (refer to Recommendation Q.71) by the assisting SSF-SRF, all received failure indications from the network on the ETC establishment shall be reported to the SCF as ETC error ETCFailed (e.g. busy, congestion). Note that the operation timer for ETC shall be longer than the maximum allowed time for the signalling procedures to accept the connection. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.21 EventNotificationCharging procedure** + +#### **3.3.21.1 General description** + +This operation is used by the SSF to report to the SCF the occurrence of a specific charging event type as requested by the SCF using the "RequestNotificationChargingEvent" operation. The operation supports the options to cope with the interactions concerning the charging (refer to Appendix II.4/Q.1214 "Charging scenarios"). + +As several charging events may occur during a connection configuration a possibility exists for the EventNotificationCharging operation to be invoked on multiple occasions. For each connection configuration EventNotificationCharging may be used several times. + +#### **3.3.21.1.1 Parameters** + +- **eventTypeCharging:** +This parameter indicates the charging event type which has occurred. Its content is network operator specific, which may be "charge pulses" or "charge messages". +- **eventSpecificInformationCharging:** +This parameter contains charging related information specific to the event. Its content is network operator specific. +- **legID:** +This parameter indicates the leg id on which the charging event type applies. +- **monitorMode:** +This parameter indicates how the charging event is reported. When the "monitorMode" is "interrupted", the event is reported as a request; if the "monitorMode" is "notifyAndContinue" the event is reported as a notification. The "monitorMode" "transparent" is not applicable for the "EventNotificationCharging" operation. + +#### **3.3.21.2 Invoking Entity (SSF)** + +##### **3.3.21.2.1 Normal procedure** + +SSF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) A charging event has been detected that is requested by the SCF. + +SSF Postcondition: + +- No FSM state transition. + +The SSF-FSM is in any state except "Idle". This operation is invoked if a charging event has been detected that is requested by the SCF. The detected charging event can be caused by: + +- a) another SLPI; or +- b) another exchange. + +Irrespective of the charging event cause, the SSF performs one of the following actions on occurrence of the charging event (according the corresponding monitorMode): + +**Interrupted:** + +- Notify the SCF of the charging event using "EventNotificationCharging" operation: do not process the event, but discard it. However, call and existing charging processing will not be suspended in the SSF. + +**NotifyAndContinue:** + +- Notify the SCF of the charging event using "EventNotificationCharging", and continue processing the event or signal. + +**3.3.21.2.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +**3.3.21.3 Responding Entity (SCF)****3.3.21.3.1 Normal procedure** + +SCF Precondition: + +- A "RequestNotificationChargingEvent" has been sent at the request of a SLPI and the SLPI is expecting an "EventNotificationCharging" from the SSF. + +SCF Postcondition: + +- No FSM state transition. + +On receipt of this operation the SLPI which is expecting this notification can continue. If the corresponding monitor mode was set by the SLPI to Interrupted, the SLPI prepares instructions for the SSF if necessary. + +**3.3.21.3.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +**3.3.22 EventReportBCSM procedure****3.3.22.1 General description** + +This operation is used to notify the SCF of a call related event previously requested by the SCF in an 'RequestReportBCSMEVENT' operation. The monitoring of more than one event could be requested with a 'RequestReportBCSMEVENT' operation, but each of these requested events is reported in a separate 'EventReportBCSM' operation. + +**3.3.22.1.1 Parameters** + +- eventTypeBCSM: + +This parameter specifies the type of event that is reported. + +- bcsmeventCorrelationID: + +Used by the SCF for correlation with a previous operation. + +- eventSpecificInformationBCSM: + +This parameter indicates the call related information specific to the event. + +For 'CollectedInfo' it will contain the 'calledPartyNumber'. + +For 'AnalysedInfo' it will contain the 'calledPartyNumber'. + +For 'RouteSelectFailure' it will contain the 'FailureCause', if available. + +For O- or T-Busy it will contain the 'BusyCause', if available. + +For O- or T-NoAnswer it will be empty. + +For O- or T-Answer it will be empty. + +For O- or T-MidCall it will contain 'connectTime', if available. + +For O- or T-Disconnect it will contain the 'releaseCause' and/or 'connectTime', if available. + +The connect time, if available, indicates the duration between the received answer indication from the called party side and the release of the connection in units of 100 ms. + +- legID: + +This parameter indicates the party in the call for which the event is reported. SSF will use the option 'ReceivingSideID' only. + +- receivingSideID: + +The following values for 'legID' are assumed: + +- 'legID' = 1 indicates the party that was present at the moment of the 'InitialDP' or a DP-specific operation (in case of a midcall trigger, the party causing the trigger), or the party that was created with an 'InitiateCallAttempt' operation. +- 'legID' = 2 indicates the party that was created with a 'Connect' operation, or in case of a mid call trigger, the party not causing the trigger. + +If not included, the following defaults are assumed: + +- legID = 1 for the events CollectedInfo, AnalysedInformation, O-Abandon and T-Abandon. +- legID = 2 for the events RouteSelectFailure, O-CalledPartyBusy, O-NoAnswer, O-Answer, T-Busy, T-NoAnswer and T-Answer. + +The 'legID' parameter shall always be included for the events O-MidCall, O-Disconnect, T-MidCall and T-Disconnect. + +- miscCallInfo: + +This parameter indicates detection point related information. + +- messageType: + +This parameter indicates whether the message is a request, i.e. resulting from a 'RequestReportBCSMEVENT' with 'monitorMode' = 'interrupted', or a notification, i.e. resulting from a 'RequestReportBCSMEVENT' with 'monitorMode' = 'notifyAndContinue'. + +- dPAssignment: + +This parameter shall be omitted for this operation. + +### 3.3.22.2 Invoking Entity (SSF) + +#### 3.3.22.2.1 Normal procedure + +SSF Preconditions: + +- The SSF-FSM is in the state "Monitoring"; or +the SSF-FSM may be in state "Waiting for Instructions" if the O/TDisconnect DP is armed and encountered; or +the SSF-FSM may be in any state if the O/TAbandon DP is armed and encountered. +- The BCSM proceeds to an EDP that is armed. + +SSF Postconditions: + +- The SSF-FSM stays in the state "Monitoring" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested. +- The SSF-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested. +- The SSF-FSM moves to the state "Waiting for Instructions" if the message type was request. Call processing is interrupted. + +For certain service features it is necessary that the same O-BCSM instance is reused. Examples are follow-on calls. + +The decision to reuse the same O-BCSM instance can only be taken by the SCF after certain armed EDP-R's are reported. + +The considered EDP-R's are: + +- RouteSelectFailure; +- O\_CalledPartyBusy; +- O\_NoAnswer; +- O\_Disconnect. + +If a EDP-R is met that causes the release of the related leg, all EDPs related to that leg are disarmed and the event is reported via "EventReportBCSM". To allow the reuse of the same O-BCSM instance, the BCSM has to store all call related signalling parameters (e.g. "callingPartyNumber", "callingPartyCategory") until the BCSM instance is released. + +In the case the respective EDP-R is met (see list above with "O-Disconnect" only for legID = 2), the A-leg will be held, the B-leg will be released and the SCF is informed via "EventReportBCSM". + +If the A-party disconnects, the call is released whether or not a DP was armed. + +### **3.3.22.2.2 Error handling** + +In case the message type is request, on expiration of $T_{SSF}$ before receiving any operation, the SSF aborts the interaction with the SCF and the call is given final treatment, e.g. a final announcement. + +Operation related error handling is not applicable, due to class 4 operation. + +### **3.3.22.3 Responding Entity (SCF)** + +#### **3.3.22.3.1 Normal procedure** + +SCF Preconditions: + +- 1) A control relationship exists between the SSF and the SCF. +- 2) The SCSM-FSM is in the state "Preparing SSF Instructions", substate "Waiting for Notification or Request". + +SCF Postconditions: + +- 1) The SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or + +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or + +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. +- 2) The event is reported to a SLPI, based on the dialogue ID. The SCF will prepare SSF or SRF instructions in accordance with the SLPI. + +#### **3.3.22.3.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +### **3.3.23 FurnishChargingInformation procedure** + +#### **3.3.23.1 General description** + +This operation is used to request the SSF to generate, register a call record or to include some information in the default call record. The registered call record is intended for off-line charging of the call. A possibility exists for the FurnishChargingInformation (FCI) operation to be invoked on multiple occasions. FCI could be applied at the beginning of the call in order to request to start call record generation. In addition FCI can also be applied at the end of the call or connection configuration (e.g. for follow-on calls). In this case FCI is used to include charge related information into the + +call record which was started at the beginning of the call. When additional FCIs are used it is recommended to arm an EDP-R (indicating the end of call or connection configuration) to be able to apply FCI before the termination of the call record generation. The charging scenarios supported by this operation are: 2.2, 2.3 and 2.4 (refer to Appendix II/Q.1214, "Charging scenarios"). + +#### 3.3.23.1.1 Parameters + +- FCIBillingChargingCharacteristics: + +This parameter indicates billing and/or charging characteristics. Its content is network operator specific. Depending on the applied charging scenario, the following information elements can be included (refer to Appendix II/Q.1214, "Charging scenarios"): + +- complete charging record (scenario 2.2); +- charge party (scenario 2.3); +- charge level (scenario 2.3); +- charge items (scenario 2.3); +- correlationID (scenario 2.4). + +#### 3.3.23.2 Invoking Entity (SCF) + +##### 3.3.23.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) An SLPI has determined that a "FurnishChargingInformation" has to be sent by the SCF. + +SCF Postconditions: + +- 1) No FSM state transition. +- 2) SLPI execution may continue. + +The SCSM-FSM is in state "Preparing SSF instruction" or is in state "Queueing FSM". This operation is invoked by the SCF if a SLPI results in the request of creating a call record to the SSF or to include some billing or charging information into the default call record. In the case of call queueing, this operation may contain information pertaining to the initiation of queueing or the call queueing time duration for call logging purpose. This causes no SCSM-FSM state transition. + +##### 3.3.23.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +#### 3.3.23.3 Responding Entity (SSF) + +##### 3.3.23.3.1 Normal procedure + +SSF Preconditions: + +- SSF-FSM: State c, "Waiting for Instructions"; or +SSF-FSM: State d, "Waiting for End of User Interaction"; or +SSF-FSM: State e, "Waiting for End of Temporary Connection"; or +SSF-FSM: State f, "Monitoring"; or +Assisting/hand-off SSF-FSM State b, "Waiting for Instructions". + +SSF Postcondition: + +- No FSM state transition. + +On receipt of this operation, the SSF performs actions to create the call record according the off line charging scenario which is applicable using the information elements included in the operation: + +- registers the complete call record included in the operation; +- generates and registers a call record according the information (charge party, charge level, charge items); +- include the information received "correlationID" in the default call record which is generated and, registered by default at the SSF. + +By means of a parameter at the "FurnishChargingInformation" operation the SCF can initiate the pulse metering function of the SSF. + +In that case the SSF shall generate meter pulses according to the applicable charging level, account and record them. + +The SSF records charge related data like for example the call duration, begin time stamp or end time stamp. Additionally the SSF records further data if required. + +The charging level can be determined by: + +- a) the SCF; or +- b) the SSF; or +- c) a succeeding exchange; or +- d) the post processing function. + +If a) applies, the charging level is included in the "FurnishChargingInformation" operation. + +If b) applies, the SSF shall determine the charging level based on the corresponding parameters contained in the operation. + +If c) applies, either the "FurnishChargingInformation" operation contains the corresponding parameters indicating that the charging level shall be determined in a succeeding exchange, or the SSF detects during the determination of the charging level based on the provided parameters that the charging level shall be determined in a succeeding exchange. + +The SSF can either account received pulses or convert any charging messages received from the B-side to pulses. In both cases, the accumulated pulses are included when the IN call record is generated or ignored. + +### **3.3.23.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +## **3.3.24 HoldCallInNetwork procedure** + +### **3.3.24.1 General description** + +This operation is used to provide the capability of queueing a call during the setup phase (e.g. to provide a call completion to busy, a call would be queued until the destination becomes free). + +#### **3.3.24.1.1 Parameters** + +- holdcause: +This parameter is optional. When used, it is network-specific and denotes the cause for holding the call. + +### **3.3.24.2 Invoking Entity (SCF)** + +#### **3.3.24.2.1 Normal procedure** + +SCF Precondition: + +- The SCSM is in state 2.2.1, "Preparing SSF Instructions", and the event (e2.2.3) Busy\_Line/Trunk has taken place. + +SCF Postcondition: + +- The SCSM enters state 2.2.2 Queueing. + +### **3.3.24.2.2 Error handling** + +There is no specific error treatment associated with this operation. Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### **3.3.24.3 Responding Entity (SSF)** + +#### **3.3.24.3.1 Normal procedure** + +SSF Precondition: + +- The SSF-FSM is in state c, "Waiting for Instructions". + +SSF Postcondition: + +- The SSF-FSM remains in the same state. + +#### **3.3.24.3.2 Error handling** + +There is no operation-specific error treatment associated with this operation. Generic error handling for the operation-related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.25 InitialDP procedure** + +#### **3.3.25.1 General description** + +This operation is sent by the SSF after detection of a TDP-R in the BCSM, to request the SCF for instructions to complete the call. + +##### **3.3.25.1.1 Parameters** + +- serviceKey: + +This parameter identifies for the SCF unambiguously the requested IN service. It is used to address the correct application/SLP within the SCF (not for SCP addressing). + +- calledPartyNumber: + +This parameter contains the number used to identify the called party in the forward direction, i.e. see Recommendation Q.762. + +- callingPartyNumber: + +See Q.762 Calling Party Number signalling information. + +- callingPartysCategory: + +See Q.762 Calling Party Category signalling information. + +- cGEncountered: + +See Recommendation Q.1290. + +- iPSSPCapabilities: + +See Recommendation Q.1290. + +- iPAvailable: + +See Recommendation Q.1290. + +- locationNumber: + +This parameter is used to convey the geographical area address for mobility services, see Recommendation Q.762. It is used when 'callingPartyNumber' does not contain any information about the geographical location of the calling party (e.g. origin dependent routing when the calling party is a mobile subscriber). + +- originalCalledPartyID: + +See Q.762 Original Called Number signalling information. + +- triggerType: + +This parameter indicates to the SCF the particular event which caused the detection of a valid trigger condition. + +- highlayerCompatibility: + +This parameter indicates the type of the high layer compatibility, which will be used to determine the ISDN-teleservice of a connected ISDN terminal. For encoding DSS-1 (see Recommendation Q.931) is used. The highlayerCompatibility can also be transported by ISUP within the ATP (see Recommendation Q.763) parameter. + +- serviceInteractionIndicators: + +This parameter contains indicators sent from the SSF to the SCF for control of the network based services at the originating exchange and the destination exchange. + +- additionalCallingPartyNumber: + +The calling party number provided by the access signalling system of the calling user, e.g. provided by a PBX. + +- forwardCallIndicators: + +This parameter indicates if the call shall be treated as a national or international call. It also indicates the signalling capabilities of the network access, preceding network connection and the preferred signalling capabilities of the succeeding network connection. The network access capabilities does not indicate the terminal type. For example, an ISPBX will have an ISDN type of access, but the end user terminal behind the ISPBX may be ISDN or non-ISDN. + +- bearerCapability: + +This parameter indicates the type of the bearer capability connection or the transmission medium requirements to the user. It is a network option to select one of the two parameters to be used: + +- bearerCap: + +This parameter contains the value of the DSS-1 Bearer Capability parameter (see Recommendation Q.931) in case the SSF is at local exchange level or the value of the ISUP User Service Information parameter (see Recommendation Q.763) in case the SSF is at transit exchange level. + +The parameter 'bearerCapability' shall only be included in the 'InitialDP' operation in case the DSS-1 Bearer Capability parameter or the ISUP User Service Information parameter is available at the SSP. + +If two values for bearer capability are available at the SSF or if User Service Information and User Service Information Prime are available at the SSF, the 'bearerCap' shall contain the value of the preferred bearer capability respectively the value of the User Service Information Prime parameter. + +- tmr: + +The tmr is encoded as the Transmission Medium Requirement parameter of the ISUP according to Recommendation Q.763. + +If two values for transmission medium requirement are available at the SSF or if Transmission Medium Requirement and Transmission Medium Requirement Prime are available at the SSF, the 'bearerCap' shall contain the value of the preferred transmission medium requirement respectively the value of the Transmission Medium Requirement Prime parameter. + +- eventTypeBCSM: + +This parameter indicates the armed BCSM detection point event, resulting in the 'InitialDP' operation. + +- redirectingPartyID: + +This parameter indicates the last directory number the call was redirected from. + +- redirectionInformation: + +See Q.763 Redirection Information signalling information. + +### 3.3.25.2 Invoking Entity (SSF) + +#### 3.3.25.2.1 Normal procedure + +SSF Preconditions: + +- 1) An event fulfilling the criteria for the DP being executed has been detected. +- 2) Call gapping and SS No. 7 overload are not in effect for the call, and the call is not to be filtered. + +SSF Postconditions: + +- 1) A control relationship has been established if the DP was armed as a TDP-R. The SSF-FSM moves to the state "Waiting for Instructions". +- 2) The SSF-FSM remains in the state "Idle" if the DP was armed as a TDP-N. + +Following a trigger detection (due to the DP criteria assigned being met) related to an armed TDP in the BCSM caused by a call origination attempt, the SSF checks if call gapping, SS No. 7 overload or service filtering are not in effect for the related call segment. + +If these conditions are met, then the 'InitialDP' operation is invoked by the SSF. The address of the SCF the 'InitialDP' operation has to be sent to, is determined on the base of trigger related data. The SSF provide as many parameters as available. In some cases, some parameters must be available (such as 'callingPartyNumber' or 'callingPartyCategory'). This is to be handled appropriately by the SSF in its trigger table (to know that such parameters are necessary for some triggering conditions) and in conducting the necessary action to get these parameters if they are not available (for instance if non-SS No. 7 signalling is used, it may be possible to request the 'callingPartyCategory' from a preceding exchange). + +Otherwise, the call control is given back to the underlying network. + +If the DP was armed as a TDP-R, a control relationship is established to the SCF. The SSF application timer $T_{\text{SSF}}$ is set when the SSF sends 'InitialDP' for requesting instructions from the SCF. It is used to prevent excessive call suspension time. + +#### 3.3.25.2.2 Error handling + +If the destination SCF is not accessible, then the call is given final treatment. + +On expiration of $T_{\text{SSF}}$ before receiving any operation, the SSF aborts the interaction with the SCF and the call is given final treatment, e.g. routing to a final announcement. + +If the calling party abandons after the sending of 'InitialDP', then the SSF aborts the control relationship by means of an abort to TCAP. Note that TCAP will wait until the first response message from the SCF has been received before it sends an abort to the SCF (see also 3.2). + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.25.3 Responding Entity (SCF) + +#### 3.3.25.3.1 Normal procedure + +SCF Precondition: + +- None. + +SCF Postcondition: + +- An SLPI has been invoked. + +On receipt of 'InitialDP' operation the SCSM moves from "Idle" to the state "Preparing SSF Instructions", a control relationship to the related SSF is created. A Service Logic Program Instance (SLPI) is invoked for processing the 'InitialDP' operation based on the 'serviceKey' parameter. By means of this control relationship, the SCF may influence the Basic Call Processing in accordance with the service logic invoked. + +The actions to be performed in the SLPI depend on the parameters conveyed via this operation and the SLPI, i.e. the requested IN service itself. + +### **3.3.25.3.2 Error handling** + +If the 'InitialDP' operation is rejected, then the SCSM remains in "Idle". The maintenance function is informed and no SLPI is invoked. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +## **3.3.26 InitiateCallAttempt procedure** + +### **3.3.26.1 General description** + +This operation is used to request the SSF to create a new call to one call party using the address information provided by the SCF (e.g. wake-up call). An EDP-R must be armed on answer and all the call failure events, in order to have the SCF, treat this call appropriately when either of these events is encountered. + +#### **3.3.26.1.1 Parameters** + +- destinationRoutingAddress: + +This parameter contains the called party number towards which the call is to be routed. The destinationRoutingAddress may contain one called party number only for this operation. The encoding of the parameter is defined in Recommendation Q.763. + +- alertingPattern: + +See Recommendation Q.1290. It only applies if the network signalling supports this parameter or if SSF is the terminating local exchange for the subscriber. + +- iSDNAcessRelatedInformation: + +Carries the same information as the protocol element ISUP Access Transport parameter in Recommendation Q.762. + +- travellingClassMark: + +The SCF uses the travellingClassMark parameter to provide essential route selection information to the SSF. The SSF uses this information to populate the outgoing ISUP-IAM message, the population and mapping of this parameter is network operator specific. + +- serviceInteractionIndicators: + +This parameter contains indicators sent from the SCF to the SSF for control of the network based services at the originating exchange and the destination exchange. + +- callingPartyNumber: + +This parameter identifies which number shall be regarded as the calling party for the created call. If this parameter is not sent by the SCF, the SSF may supply a network dependent default value. + +### **3.3.26.2 Invoking Entity (SCF)** + +#### **3.3.26.2.1 Normal procedure** + +SCF Preconditions: + +- 1) An SLPI has been invoked, no control relationship exists between SCF and SSF. +- 2) An SLPI has determined that an 'InitiateCallAttempt' operation should be sent to the SCF. +- 3) The SCSM-FSM is in state "Idle". + +SCF Postconditions: + +- 1) A control relationship is established between the SCF and SSF. +- 2) The SCSM-FSM is in state "Preparing SSF Instructions". +- 3) SLPI execution continues. + +The SCSM-FSM moves to state "Preparing SSF Instructions" when the service logic invokes this operation. In order to enable the establishment of a control relationship between the SCF and SSF and to allow the SCF to control the created call appropriately, the SLPI shall monitor for the BCSM event(s) which report the result of the created call set-up. This includes DP 3 or DP 4, 5, 6, and 7. Any other Non-Call\_Processing\_Instructions may be sent as well. The 'InitiateCallAttempt' operation creates a BCSM instance in the SSF but the SSF suspends the call processing of this BCSM. The SLPI shall send a 'Continue' operation to request the SSF to route the call to the specified destination. The SCSM-FSM shall proceed as specified at the procedure for the 'Continue' operation. + +The above described procedure shall be part of the establishment of the control relationship, i.e. operations up to and including the 'Continue' operation shall be sent together in the same message to the SSF. The SCF shall start a response Timer $T_{SCF}$ when the 'InitiateCallAttempt' operation is sent. The response Timer shall supervise the confirmation of the dialogue from SSF, the value of $T_{SCF}$ shall be equal or less than the network no answer timer. + +### 3.3.26.2.2 Error handling + +On expiration of $T_{SCF}$ the SCF shall abort the dialogue, report the abort to the maintenance functions and inform the SLPI on the failure of dialogue establishment. The SCSM-FSM moves to the "Idle" state. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.26.3 Responding Entity (SSF) + +#### 3.3.26.3.1 Normal procedure + +SSF Precondition: + +- None. + +SSF Postconditions: + +- 1) A new originating BCSM has been created, call processing is suspended at DP 1. +- 2) The SSF-FSM has moved from "Idle" state to state "Waiting for Instructions". + +Upon reception of 'InitiateCallAttempt', the SSF creates a new originating BCSM and suspends the call processing of this BCSM at DP 1. All subsequent operations are treated according to their normal procedures. + +The properties and capabilities, normally received from or associated to the calling party, required for the call set-up shall have a network dependent default value. If a calling party number is supplied by the SCF, these properties may be dependent on the received calling party number + +#### 3.3.26.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.27 ModifyEntry procedure + +#### 3.3.27.1 General description + +The X.500 'ModifyEntry' operation is used to request the SDF to make one or several modifications to a data object. The modifications concern the attributes and their values of which the object is composed. The type of modifications to perform is given in the operation argument provided by the SCF. The modifications do not concern the values of the attributes used to identify the object (i.e. the object name). For a full description of the ModifyEntry operation, see 11.3/X.511. + +### 3.3.27.1.1 Parameters + +See 11.3.2/X.511 and 11.3.3/X.511. + +### 3.3.27.2 Invoking Entity (SCF) + +#### 3.3.27.2.1 Normal procedure + +SCF Precondition: + +- SCSM: "SDF Bound" or "Wait for Subsequent Requests". + +SCF Postcondition: + +- SCSM: "SDF Bound". + +When the SCSM is in the state "Wait for Subsequent Requests" and a need of the service logic to modify information of the SDF exists, an internal event [(e2) Request\_to\_SDF] occurs. Until the application process indicates, with a delimiter (or a timer expiry), that the operation should be sent, the SCSM remains in the state "Wait for Subsequent Requests" and the operation is not sent. The operation is sent to the SDF in a message containing a Bind argument. The SCSM waits for the response from the SDF. The reception of the response [(E5) Response\_from\_SDF\_with\_Bind or (E4) Bind\_Error] to the Bind operation previously issued to the SDF causes a transition of the SCF to the state "SDF Bound" or to the state "Idle". When the SCSM has moved to state "Idle", the ModifyEntry operation was discarded. In the state "SDF Bound", the response of the ModifyEntry operation [(E7) Response\_from\_SDF] causes a transition of the SCF to the same state ("SDF Bound"). It may be either the result of the ModifyEntry operation or an error. + +When the SCSM is in the state "SDF Bound" and a need of the service logic to modify information of the SDF exists, an internal event occurs. This event, called (e6) Request\_to\_SDF causes a transition to the same state "SDF Bound" and the SCSM waits for the response from the SDF. The reception of the response [(E7) Response\_from\_SDF] to the ModifyEntry operation previously issued to the SDF causes a transition of the SCF to the same state "SDF Bound". The response from the SDF may be either the result of the ModifyEntry operation or an error. + +#### 3.3.27.2.2 Error handling + +Generic error handling for the operation related errors is described in 11.3.4/X.511 and 11.3.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +### 3.3.27.3 Responding Entity (SDF) + +#### 3.3.27.3.1 Normal procedure + +SDF Precondition: + +- SDSM: "SCF Bound" or "Bind Pending". + +SDF Postcondition: + +- SDSM "SCF Bound". + +When the SDF is in the state "Bind Pending", the external event (E3) Request\_from\_SCF caused by the reception of a 'ModifyEntry' operation from the SCF occurs. The SDF does not proceed to the operation until a Bind operation has been successfully executed. It remains in the same state. + +When the SDF is in the state "SCF Bound", the external event (E7) Request\_from\_SCF caused by the reception of a 'ModifyEntry' operation from the SCF occurs. The SDF waits for the response to the operation. + +On the receipt of the event (E7) and before updating the different attributes specified in the operation parameters, the SDF shall take the following actions: + +- verify that the object accessed by the request exists; +- verify that the user on behalf of whom the request is performed has sufficient access rights to modify the object for each elementary modifications contained in the operation; +- verify that each attribute or value on which an operation should be performed exists in the object; +- verify that the proposed modifications are compatible with the object class of the object or with the syntax of the attribute. + +After the specified actions, indicated above, are successfully executed for all the modifications requested in the operation, all the modifications for a same attribute take place in the order given in the "changes" parameter. A result is returned to the SCF. The sending of the result corresponds to the event (e6) Response\_to\_SCF. + +### **3.3.27.3.2 Error handling** + +Generic error handling for the operation related errors is described in 11.3.4/X.511 and 11.3.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +## **3.3.28 OAnswer procedure** + +### **3.3.28.1 General description** + +This operation is sent from the SSF to the SCF at the O\_Answer DP, after detecting a valid trigger condition, or to report an event requested by RequestReportBCSMEEvent. + +#### **3.3.28.1.1 Parameters** + +- dPSpecificCommonParameters: + +- callingPartyBusinessGroupID: + +See Recommendation Q.1290. The SCF can use this parameter to select SLPs based on the group and for authorization purposes. The network operators can specify that this parameter should be used if their particular network has the information available. + +- callingPartySubaddress: + +See Q.931 Calling Party Subaddress. + +- callingFacilityGroup: + +See Recommendation Q.1290. + +- callingFacilityGroupMember: + +See Recommendation Q.1290. + +- originalCalledPartyID: + +See Q.762 Original Called Number signalling information. + +- redirectingPartyID: + +This parameter (if available) is the directory number of the last redirecting party. + +- redirectionInformation: + +See Q.763 Redirection Information signalling information. + +- routeList: + +routeList represents the list of routes which would have been used in order to route the call. The network operators can specify that this parameter should be used if their particular network has the information available. + +- travellingClassMark: + +As defined in Recommendation Q.1290. + +### **3.3.28.2 Invoking Entity (SSF)** + +#### **3.3.28.2.1 Normal procedure** + +SSF Preconditions (TDP and EDP): + +- 1) Call origination attempt has been initiated. +- 2) Indication received that the call has been accepted and the terminating party has answered. +- 3) Call gapping or service filtering are not in effect. +- 4) DP criteria are met. + +- 5) For a TDP-R, there is no existing control relationship. +- 6) For an EDP-R, there is an existing control relationship and the EDP O\_Answer is armed. +- 7) For an EDP-N, there is an existing control or monitoring relationship and the EDP O\_Answer is armed. + +SSF Postconditions for TDP: + +- 1) For a TDP-R, basic call processing has been suspended at O\_Answer DP, and a control relationship has been established. +- 2) For a TDP-N, basic call processing proceeds at O\_Active PIC, and no control relationship has been established. + +SSF Postconditions for EDP: + +- 1) The SSF-FSM stays in the state "Monitoring" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested. +- 2) The SSF-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested. +- 3) The SSF-FSM moves to the state "Waiting for Instructions" if the message type was request. Call processing is interrupted. + +### 3.3.28.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.28.3 Responding Entity (SCF) + +#### 3.3.28.3.1 Normal procedure + +SCF Precondition (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +#### 3.3.28.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.29 ODisconnect procedure + +#### 3.3.29.1 General description + +This operation is sent by the SSF to the SCF after detecting a valid trigger condition at the O\_Disconnect DP, or to report an event requested by RequestReportBCSMEVENT. Refer to 4.2.2.2/Q.1214 for additional call modelling related semantics. + +##### 3.3.29.1.1 Parameters + +- serviceAddressInformation (serviceKey, miscCallInfo, triggerType): +See Recommendation Q.1290. The triggerType indicates the particular event which caused call suspension. The miscCallInfo indicates that a request for instructions or a notification has been issued to the SCF and the category for the trigger (line, group, office). The serviceKey is used in identifying the service logic to be invoked. +- bearerCapability: +This parameter indicates the type of bearer capability connection to the user. Refer to 6.4.4/Q.1214 for population rules for the bearer capability parameter. +- calledPartyNumber: +See Q.762 Called Party Number signalling information. This parameter is used to identify the called party in the forward direction. +- callingPartyNumber: +See Q.762 Calling Party Number signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartynumber parameter. +- callingPartysCategory: +See Q.762 Calling Party's Category signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartysCategory parameter. +- iPSSPCapabilities: +See Recommendation Q.1290. +- iPAvailable: +See Recommendation Q.1290. +- iSDNAccessRelatedInformation: +This parameter contains (possibly multiple) information elements as per Recommendation Q.931. See Access Transport Parameter signalling information in Recommendations Q.762, Q.763 and Q.931. Refer to 6.4.4/Q.1214 (Analysed Information) for population rules for ISDN access related information. +- cGEncountered: +See Recommendation Q.1290. +- locationNumber: +See Q.762 Location Number signalling information. This parameter is used to convey the geographical area address for mobility services. It is used when the "callingPartyNumber" does not contain any information about the geographical location of the calling party (e.g. origin dependent routing when the calling party is a mobile subscriber). +- serviceProfileIdentifier: +See Annex A/Q.932. Refer to 6.4.4/Q.1214 for population rules for serviceProfileIdentifier. +- terminalType: +See Recommendation Q.1290. This parameter identifies the terminal type so that the SCF can specify, to the SRF, the appropriate type of capability (voice recognition, DTMF, display capability, etc.). + +- chargeNumber: +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules for chargeNumber. +- servingAreaID: +See Recommendation Q.1290. +- callingPartyBusinessGroupID: +See Recommendation Q.1290. +- callingPartySubaddress: +See Q.931 Calling Party Subaddress. +- callingFacilityGroup: +See Recommendation Q.1290. +- callingFacilityGroupMember: +See Recommendation Q.1290. +- releaseCause: +Indicates the cause of the disconnect. +- routeList: +See Recommendation Q.1290. +- carrier: +See Recommendation Q.1290. +- connectTime: +Indicates the duration between the received answer indication from the called party side and the release of the connection. + +### 3.3.29.2 Invoking Entity (SSF) + +#### 3.3.29.2.1 Normal procedures + +SSF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Indication received from Terminating BCSM that the call is accepted and the terminating party has answered. +- 3) Disconnect indication received from an originating party, or received from the terminating party via the terminating BCSM. +- 4) For a TDP, call gapping or service filtering are not in effect. +- 5) DP criteria have been met. +- 6) For a TDP-R or a TDP-N, there is no existing control relationship. +- 7) For an EDP, there is an existing control relationship and the EDP O\_Disconnect is armed. + +SSF Postconditions: + +- 1) For a TDP-R, basic call processing has been suspended at O\_Disconnect DP, and a control relationship has been established. +- 2) For a TDP-N, call processing proceeds to the O\_Null and Authorize Termination Attempt PIC, and no control relationship has been established. +- 3) For an EDP, as for EventReportBCSM procedure (see 3.3.22.2.1). + +#### 3.3.29.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### 3.3.29.3 Responding Entity (SCF) + +#### 3.3.29.3.1 Normal procedure + +SCF Precondition (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or + +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or + +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +#### 3.3.29.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### 3.3.30 ONoAnswer procedure + +#### 3.3.30.1 General description + +This operation is sent from the SSF to the SCF at the O\_No\_Answer DP, after detecting a valid trigger condition, or to report an event requested by RequestReportBCSMEvent. + +##### 3.3.30.1.1 Parameters + +- dPSpecificCommonParameters: +- callingPartyBusinessGroupID: + +See Recommendation Q.1290. The SCF can use this parameter to select SLPs based on the group and for authorization purposes. The network operators can specify that this parameter should be used if their particular network has the information available. + +- callingPartySubaddress: + +See Q.931 Calling Party Subaddress. + +- callingFacilityGroup: + +See Recommendation Q.1290. + +- callingFacilityGroupMember: + +See Recommendation Q.1290. + +- originalCalledPartyID: + +See Q.762 Original Called Number signalling information. + +- prefix: +As defined in Recommendation Q.1290. +- redirectingPartyID: +This parameter (if available) is the directory number of the last redirecting party. +- redirectionInformation: +See Q.763 Redirection Information signalling information. +- routeList: +routeList represents the route used. +- travellingClassMark: +As defined in Recommendation Q.1290. +- carrier: +As defined in Recommendation Q.1290. + +### 3.3.30.2 Invoking Entity (SSF) + +#### 3.3.30.2.1 Normal procedure + +SSF Preconditions (TDP and EDP): + +- 1) Call origination attempt has been initiated. +- 2) Indication received that the terminating party has not answered within the specified time period. +- 3) Call gapping or service filtering are not in effect. +- 4) DP criteria have been met (TDP or EDP). +- 5) For a TDP-R, there is no existing control relationship. +- 6) For an EDP-R, there is an existing control relationship and the EDP O\_No\_Answer is armed. +- 7) For an EDP-N, there is an existing control or monitoring relationship and the EDP O\_No\_Answer is armed. + +SSF Postconditions for TDP: + +- 1) For a TDP-R, basic call processing has been suspended at O\_No\_Answer DP, and a control relationship has been established. +- 2) For a TDP-N, default exception handling has been provided, and no control relationship has been established. Use of TDP-N at this DP implies that there is no further alerting of the called party and that switch based no-answer treatments, as applicable, may be invoked. + +SSF Postconditions for EDP: + +- 1) The SSF-FSM stays in the state "Monitoring" if the message type was notification and there are still EDPs armed or a 'CallInformationReport' or 'ApplyChargingReport' requested. +- 2) The SSF-FSM moves to the state 'Idle' if the message type was notification and there are no more EDPs armed, no 'CallInformationReport' or 'ApplyChargingReport' are requested. +- 3) The SSF-FSM moves to the state "Waiting for Instructions" if the message type was request. Call processing is interrupted. + +#### 3.3.30.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.30.3 Responding Entity (SCF) + +#### 3.3.30.3.1 Normal procedure + +SCF Precondition (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a 'CallInformationReport' or 'ApplyChargingReport' requested; or + +The SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no 'CallInformationReport' or 'ApplyChargingReport' are requested; or + +The SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +#### 3.3.30.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.31 OriginationAttemptAuthorized procedure + +#### 3.3.31.1 General description + +This operation is sent by the SSF after Authorization for call attempt is complete from BCSM O\_Null and Authorize Origination Attempt PIC processing and a TDP has been detected. + +##### 3.3.31.1.1 Parameters + +- serviceAddressInformation (triggerType, serviceKey, miscCallInfo): + +The triggerType indicates the particular event which caused call suspension. The miscCallInfo indicates that a request for instructions has been issued to the SCF and the category for the trigger (line, group, office). The serviceKey is used in identifying the service logic to be invoked. + +- bearerCapability: + +See Q.762 User Service Information and Q.931 Bearer Capability information element. Refer to 6.4.4/Q.1214 for population rules for the bearer capability parameter. + +- calledPartyNumber: + +See Q.762 Called Party Number signalling information. This parameter is used to identify the called party in the forward direction (i.e. it is used to populate the bearer signalling protocol's Called Party Number information element). + +- callingPartyNumber: + +See Q.762 Calling Party Number signalling information. This parameter identifies the directory number of the originating line or the calling party number received in ISUP signalling. Refer to 6.4.4/Q.1214 for population rules for the callingPartyNumber parameter. + +- callingPartysCategory: + +See Q.762 Calling Party's Category signalling information. This parameter indicates the type of the calling party (e.g. operator, pay phone, ordinary subscriber). Refer to 6.4.4/Q.1214 for population rules for the callingPartysCategory parameter. + +- iSSPCapabilities: + +See Recommendation Q.1290. + +- iPAvailable: + +See Recommendation Q.1290. + +- iSDNAccessRelatedInformation: + +Carries the same information as the protocol element ISUP Access Transport parameter in Recommendation Q.762. This parameter contains information elements provided across an ISDN interface. Refer to 6.4.4/Q.1214 for population rules for ISDN access related information. + +- cGEncountered: + +This parameter indicates that the related call has passed call gapping. + +- locationNumber: + +See Q.762 Location Number signalling information. This parameter is used to convey the geographical area address for mobility services. It is used when the 'callingPartyNumber' does not contain any information about the geographical location of the calling party (e.g. origin dependent routing when the calling party is a mobile subscriber). + +- serviceProfileIdentifier: + +See Annex A/Q.932. This parameter allows ISDN to support identification and selection of specific terminals on a multi-point user-network interface to support multiple user service profiles when Q.931 information elements are not sufficient. See 6.4.4/Q.1214 for population rules for serviceProfileIdentifier. + +- terminalType: + +See Recommendation Q.1290. Identifies the terminal type so that the SCF can specify, to the SRF, the appropriate type of capability (voice recognition, DTMF, display capability, etc.). + +- chargeNumber: + +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules for chargeNumber. + +- servingAreaID: + +See Recommendation Q.1290. + +- dialledDigits: + +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules for dialledDigits. + +- callingPartyBusinessGroupID: + +See Recommendation Q.1290. + +- callingPartySubaddress: + +See Q.931 Calling Party Subaddress. + +- callingFacilityGroup: + +See Recommendation Q.1290. + +- callingFacilityGroupMember: +See Recommendation Q.1290. +- travellingClassMark: +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules for the travellingClassMark parameter. +- Carrier: +See Recommendation Q.1290. + +### 3.3.31.2 Invoking Entity (SSF) + +#### 3.3.31.2.1 Normal procedure + +SSF Preconditions: + +- 1) Call processing has progressed through the O\_Null and Authorize Origination Attempt PIC of the O-BCSM and the call origination attempt has been authorized. +- 2) Call gapping and SS No. 7 overload are not in effect for the call, and the call is not to be filtered. +- 3) A trigger is armed as a TDP at the Origination\_Attempt\_Authorized detection point. + +SSF Postconditions: + +- 1) For TDP-R, a control relationship has been established and the SSF waits for instructions from the SCF. +- 2) For TDP-N, call processing continues at the Collect\_Info PIC. + +#### 3.3.31.2.2 Error handling + +If the destination SCF is not accessible, then the call is given final treatment (other treatments are for further study). On expiration of $T_{\text{SSF}}$ before receiving any operation, the SSF aborts the interaction with the SCF and the call is given final treatment (e.g. routing to a final announcement). If the calling party abandons after the sending of the OriginationAttemptAuthorized operation, then the SSF aborts the control relationship after the first answer message from the SCF has been received: the Transaction ID is held open until $T_{\text{SSF}}$ expires. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.31.3 Responding Entity (SCF) + +#### 3.3.31.3.1 Normal procedure + +SCF Precondition: + +- No control relationship exists. + +SCF Postconditions: + +- 1) An SLPI has been invoked; a control relationship is established for TDP-R. +- 2) For TDP-N: None. + +On receipt of the OriginationAttemptAuthorized operation, the SCSM moves from "Idle" state to the state "Preparing SSF Instructions". A control relationship to the related SSF is created. A Service Logic Program Instance (SLPI) is invoked for processing the OriginationAttemptAuthorized operation. By means of this control relationship, the SCF may influence the Basic Call Processing in accordance with the service logic invoked. The actions to be performed in the SLPI depend on the parameters conveyed via this operation and the SLPI (i.e. the requested IN service itself). + +#### 3.3.31.3.2 Error handling + +If the OriginationAttemptAuthorized operation is rejected, then the SCSM remains in the same state. The maintenance function is informed and no SLPI is invoked. Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.32 PlayAnnouncement procedure + +#### 3.3.32.1 General description + +This operation is used for inband interaction with an analogue user or for interaction with an ISDN user. + +##### 3.3.32.1.1 Parameters + +- informationToSend: + +This parameter indicates an announcement, a tone or display information to be sent to the end user by the SRF. + +- a) inbandInfo: + +This parameter specifies the inband information to be sent. + +- messageID: + +This parameter indicates the message(s) to be sent, this can be one of the following: + +- i) elementaryMessageID: + +This parameter indicates a single announcement. + +- ii) text: + +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the SRF. This parameter consists of two subparameters, messageContent and attributes. The attributes of text may consist of items such as language. + +- iii) elementaryMessageIDs: + +This parameter specifies a sequence of announcements. + +- iv) variableMessage: + +This parameter specifies an announcement with one or more variable parts. + +- numberOfRepetitions: + +This parameter indicates the maximum number of times the message shall be sent to the end-user. + +- duration: + +This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. ZERO indicates endless repetition. + +- interval: + +This parameter indicates the time interval in seconds between repetitions, i.e. the time between the end of the announcement and the start of the next repetition. This parameter can only be used when the number of repetitions is > 1. + +- b) tone: + +This parameter specifies a tone to be sent to the end-user. + +- toneID: + +This parameter indicates the tone to be sent. + +- duration: + +This parameter indicates the time duration in seconds of the tone to be sent. ZERO indicates infinite duration. + +- c) displayInformation: + +This parameter indicates a text string to be sent to the end-user. This information can not be received by a PSTN end-user. + +NOTE – As the current signalling systems (DSS-1/ISUP) do not provide an indication whether or not information can be displayed by the user's terminal, in case of user interaction with an ISDN user two consecutive 'PlayAnnouncement' operations are sent. The first contains the display information, the second contains the inband information to be sent to the user. Since the execution of the display information by the SRF should take a limited amount of time, the inband information will be immediately sent by the SRF to the user, in sequence with the display information. + +- disconnectFromIPForbidden: + +This parameter indicates whether or not the SRF should be disconnected from the user when all information has been sent. + +- requestAnnouncementComplete: + +This parameter indicates whether or not a 'SpecializedResourceReport' shall be sent to the SCF when all information has been sent. + +### 3.3.32.2 Invoking Entity (SCF) + +#### 3.3.32.2.1 Normal procedure + +SCF Preconditions: + +- 1) The SLPI detects that information should be sent to the user. +- 2) A connection between the user and a SRF has been established. +- 3) The SCSM-FSM is in the state "User interaction", substate "Waiting for response from the SRF". + +SCF Postconditions: + +- 1) If "RequestAnnouncementComplete" was set TRUE, the SCSM will stay in substate "Waiting for Response from the SRF" and wait for the "SpecializedResourceReport". +- 2) If "RequestAnnouncementComplete" was set FALSE and more information needs to be sent ("DisconnectFromIPForbidden" was set to TRUE), the SCSM will stay in substate "Waiting for Response from the SRF". +- 3) If "RequestAnnouncementComplete" was set FALSE and no more information needs to be sent ("DisconnectFromIPForbidden" was set to FALSE), the SCSM will move to the state "Preparing SSF Instructions". + +#### 3.3.32.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.32.3 Responding Entity (SRF) + +#### 3.3.32.3.1 Normal procedure + +SRF Precondition: + +- The SRSM-FSM is in the state "Connected" or in the state "User Interaction" if the SRF received previously an operation from the SCF. + +SRF Postconditions: + +- 1) The SRF sends the information to the user as indicated by "informationToSend". +- 2) The SRSM-FSM moves to the state "User Interaction" or remains in the same state. +- 3) If all information has been sent and "RequestAnnouncementComplete" was set TRUE, the SRSM sends a "SpecializedResourceReport" operation to the SCF. +- 4) If all information has been sent and "disconnectFromIPForbidden" was set FALSE, the SRSM disconnects the SRF from the user. + +The announcement send to the end-user is ended in the following conditions: + +- if neither "duration" or "numberOfRepetitions" is specified, then the network specific announcement ending conditions shall apply; or +- if "numberOfRepetitions" is specified, when all repetitions have been sent; or +- if duration is specified, when the duration has expired. The announcement is repeated until this condition is met; or +- if "duration" and "numberOfRepetitions" is specified, when one of both conditions is satisfied (whatever comes first). + +### 3.3.32.3.2 Error handling + +If a Cancel operation is received before or during the processing of the operation, then the operation is immediately cancelled and the error "Cancelled" is reported to the invoking entity. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.33 PromptAndCollectUserInformation procedure + +#### 3.3.33.1 General description + +This operation is used to interact with a call party in order to collect information. + +##### 3.3.33.1.1 Parameters + +a) collectedInfo + +i) collectedDigits + +• minimumNbOfDigits: + +If this parameter is missing, the default value is defined to be 1. The "minimumNbOfDigits" specifies the minimum number of valid digits to be collected. + +• maximumNbOfDigits: + +This parameter should always be present and specifies the maximum number of valid digits to be collected. The following applies: "maximumNbOfDigits" >= "minimumNbOfDigits". + +• endOfReplyDigit: + +This parameter indicates the digit used to signal the end of input. + +In case the "maximumNbOfDigits" = "minimumNbOfDigits", the "endOfReplyDigit" (could be present but) has no further meaning. This parameter can be one or two digits. + +In case the "maximumNbOfDigits" > "minimumNbOfDigits", the following applies: + +- If "endOfReplyDigit" is not present, the end of input is indicated: + - 1) when the inter-digit timer expires; or + - 2) when the number of valid digits received equals the "maximumNbOfDigits". +- If "endOfReplyDigit" is present, the end of input is indicated: + - 1) when the inter-digit timer expires; or + - 2) when the end of reply digit is received; or + - 3) when the number of valid digits received equals the "maximumNbOfDigits". + +When the end of input is attained, the collected digits are sent from SRF to the SCF, including the "endOfReplyDigit" if received by the SRF. + +In the case the number of valid digits received is less than the "minimumNbOfDigits" when the inter-digit timer expires or when the end of reply digit is received, the input is specified as being erroneous. + +• cancelDigit: + +If this parameter is present, the cancel digit can be entered by the user to request a possible retry. All digits already received by the SRF are discarded and the same "PromptAndCollectInformation" procedure is performed again, thus, e.g. the same announcement to request user information is given to the user and information is collected. This parameter can be one or two digits . + +If this parameter is not present, the user is not able to request a possible retry. + +- startDigit: + +If this parameter is present, the start digit indicates the start of the valid digits to be collected. The digits that are received by the SRF before this start digit is received, are discarded and are not considered to be valid. This parameter can be one or two digits. + +If this parameter is not present, all received digits are considered to be valid. + +- firstDigitTimeout: + +If this parameter is present, the first digit should be received by the SRF before the first-digit timer expiration. In case the first digit is not received before first-digit timer expiration, the input is regarded to be erroneous. After receipt of the first valid or non-valid input digit, the corresponding first-digit timer is stopped. + +If this parameter is not present, then the SRF uses a default value (network operator specific) for the first-digit timer in which the first valid or non-valid input digit is received. + +If "startDigit" is present, the first-digit timer is stopped after the start digit is received. + +- interDigitTimeOut: + +If this parameter is present any subsequent valid or non-valid digit should be received by the SRF before the inter-digit timer expires. As result the inter-digit timer is reset and restarted. + +In case a subsequent valid or non-valid digit is not received before the inter-digit timer expires and the number of received valid digits is less than the "minimumNbOfDigits", the input is regarded to be unsuccessful. + +In case a subsequent valid or non-valid digit is not received before the inter-digit timer expires and the number of received valid digits is greater than the "minimumNbOfDigits", and less than or equal to the "maximumNbOfDigits", the input is regarded to be successful. + +If the "interDigitTimeOut" is not present, then the SRF uses a default value for the inter-digit time. + +- errorTreatment: + +This optional parameter defines what specific action should be taken by the SRF in the event of error conditions occurring. The default value is reportErrorToSCF. + +- interruptableAnnInd: + +This parameter is optional, where the default value is specified being TRUE. + +If this parameter is TRUE, the announcement is interrupted after the first valid or non-valid digit is received by the SRF. If the announcement is interrupted, a possible start-digit timer will not apply anymore. However, if the announcement has not been interrupted, a possible start-digit timer is started after the announcement has been finished. + +If this parameter is present and explicitly set to FALSE, the announcement will not be interrupted after the first digit is received by the SRF. The received digits during the announcement are discarded and considered to be non-valid. All other specified parameters ("minimumNbOfDigits", "maximumNbOfDigits", "endOfReplyDigit", etc.) do not apply before the announcement has been finished. The possible start-digit timer is started after the announcement has been finished. + +- voiceInformation: + +This parameter is optional, where the default value is specified being FALSE. If the "voiceInformation" parameter is FALSE, all valid or non-valid digits are entered by DTMF. + +If this parameter is present and explicitly set to TRUE, calling user is required to provide all valid or non-valid information by speech. The SRF will perform voice recognition and translation of the provided information into digits. A possible end of reply digit will also have to be provided by speech. + +- voiceBack: + +This parameter is optional, where the default value is specified being FALSE. If the "voiceBack" parameter is FALSE, no voice back information is given by the SRF. + +If this parameter is present and explicitly set to TRUE, the valid input digits received by the SRF will be announced back to the calling user immediately after the end of input is received. The non-valid input digits will not be announced back to the calling user. + +A possible end of reply digit is not voiced back. + +- b) disconnectFromIPForbidden: + +This parameter indicates whether the SRF should initiate disconnection to the SSF-CCF after the interaction has been completed. If the parameter is not present or set to TRUE, the SRF shall not initiate disconnection. + +- c) informationToSend: + +This parameter indicates an announcement, a tone or display information to be sent to the end user by the SRF. + +- i) inbandInfo: + +This parameter specifies the inband information to be sent. + +- messageID: + +This parameter indicates the message(s) to be sent, this can be one of the following: + +- elementaryMessageID: + +This parameter indicates a single announcement. + +- text: + +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the SRF. This parameter consist of two subparameters, messageContent and attributes. The attributes of text may consist of items such as language. + +- elementaryMessageIDs: + +This parameter specifies a sequence of announcements. + +- variableMessage: + +This parameter specifies an announcement with one or more variable parts. + +- numberOfRepetitions: + +This parameter indicates the maximum number of times the message shall be sent to the end-user. + +- duration: + +This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. ZERO indicates endless repetition. + +- interval: + +This parameter indicates the time interval in seconds between repetitions, i.e. the time between the end of the announcement and the start of the next repetition. This parameter can only be used when the number of repetitions is > 1. + +- ii) tone: + +This parameter specifies a tone to be sent to the end-user. + +- toneID: + +This parameter indicates the tone to be sent. + +- duration: + +This parameter indicates the time duration in seconds of the tone to be sent. ZERO indicates infinite duration. + +iii) displayInformation: + +This parameter indicates a text string to be sent to the end-user. This information can not be received by a PSTN end-user. + +NOTE – As the current signalling systems (DSS 1/ISUP) do not provide an indication whether or not information can be displayed by the user's terminal, in case of user interaction with an ISDN user, the 'displayInformation' parameter is not used in the 'PromptAndCollectUserInfoInformation' operation. Instead, a 'PlayAnnouncement' operation containing the 'displayInformation' parameter followed by a 'PromptAndCollectUserInfoInformation' operation containing inband information are sent to the user. Since the execution of the displayed information by the SRF should take a limited amount of time, the inband information will be immediately sent after by the SRF to the user, in sequence with the displayed information. + +– digitsResponse: + +This parameter contains the information collected from the end-user. + +### 3.3.33.2 Invoking Entity (SCF) + +#### 3.3.33.2.1 Normal procedure + +SCF Preconditions: + +- 1) The SLPI detects that information should be collected from the end-user. +- 2) A connection between the end-user and a SRF has been established. +- 3) The SCSM-FSM is in state "User Interaction", substate "Waiting for Response from the SRF". + +SCF Postconditions: + +- 1) The collected information is received from the SRF as response to the 'PromptAndCollectUserInfoInformation' operation. +- 2) If the 'disconnectFromIPForbidden' was set to FALSE, the SCSM-FSM will move to the state "Preparing SSF Instructions". +- 3) Otherwise the SCSM-FSM remains in the same state. + +The SLPI may continue execution before the response is received from the 'PromptAndCollectUserInfoInformation' operation, more than one operation may be sent to the SRF before the response is received. The 'disconnectFromIPForbidden' parameter may only be set to FALSE if the 'PromptAndCollectUserInfoInformation' operation is the last operation sent to the SRF. + +#### 3.3.33.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.33.3 Responding Entity (SRF) + +#### 3.3.33.3.1 Normal procedure + +SRF Precondition: + +- The SRSM-FSM is in the state "Connected", or in state "User Interaction" if the SRF received previously an operation from the SCF. + +SRF Postconditions: + +- 1) The SRF has sent the information to the end-user as indicated by "informationToSend". +- 2) The collected information from the end-user is sent to the SCF as RETURN RESULT of the "PromptAndCollectUserInfoInformation". +- 3) If the "disconnectFromIPForbidden" was set to FALSE, the SRF initiates a bearer channel disconnect to the SSF and the SRSM-FSM moves to the state "Idle". +- 4) Otherwise the SRSM-FSM moves to the state "User Interaction", or remains in the same state. + +The announcement send to the end-user is ended in the following conditions: + +- if neither "duration" or "numberOfRepetitions" is specified, then the network specific announcement ending conditions shall apply; or +- if "numberOfRepetitions" is specified, when all repetitions have been sent; or +- if duration is specified, when the duration has expired. The announcement is repeated until this condition is met; or +- if "duration" and "numberOfRepetitions" is specified, when one of both conditions is satisfied (whatever comes first). + +The above conditions are overruled if the parameter "interruptableAnnInd" is not set to FALSE and the end-user has responded with a digit during the sending of the announcement. In this case the announcement is ended immediately. The above procedures apply only to inband information and tones send to the end-user, for "displayInformation" the end conditions are met upon sending, i.e. no interruption can occur. + +The parameter "errorTreatment" specifies how the SRF shall treat the error. The default value "reportErrorToSCF" means that the error shall be reported to SCF by means of Return Error with "ImproperCallerResponse". The value "help" indicates that no error shall be reported to SCF but assistance shall be given to the end-user in form of a network dependent default announcement (which may be dependent on the context, i.e. the send message). The value "repeatPrompt" indicates that no error shall be reported to the SCF but the prompt shall be repeated to the end-user. The last two procedures shall only be done once per "PromptAndCollectUserInfo" operation. + +NOTE – Processing "endOfInput": The receipt of any "endOfInput" condition (e.g. endOfReplyDigit, cancelDigit, firstDigitTimeout, interDigitTimeout) terminates immediately the ongoing input. In other words, when e.g. an endOfReplyDigit is received, the receipt of a subsequent cancelDigit will not be processed anymore. + +### **3.3.33.3.2 Error handling** + +If a Cancel operation is received before or during the processing of the operation, then the operation is immediately cancelled and the error "Cancelled" is reported to the invoking entity. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +If any of the parameter restrictions are violated (e.g. minimumNbOfDigits > maximumNbOfDigits), then an operation error has occurred. + +### **3.3.34 ReleaseCall procedure** + +#### **3.3.34.1 General description** + +This operation is used to tear down by the SCF an existing call at any phase of the call for all parties involved in the call. This operation may not be sent to an assisting SSF, except in the case of hand-off procedure. + +##### **3.3.34.1.1 Parameters** + +- Cause: +A number giving an indication to the SSF about the reason of releasing this specific call. This may be used by SSF for generating specific tones to the different parties in the call or to fill in the 'cause' in the release message. + +#### **3.3.34.2 Invoking Entity (SCF)** + +##### **3.3.34.2.1 Normal procedure** + +SCF Precondition: + +- State 2.1, "Preparing SSF instructions" or State 2.3, "Waiting for Notification or Request". + +SCF Postcondition: + +- State 1, "Idle", if neither 'CallInformationReport' nor 'ApplyChargingReport' has to be received from the SSF. All resources (e.g. queue) related to the call are released by the SCF; or + +State 2.3, "Waiting for Notification or Request" if a 'CallInformationReport' or 'ApplyChargingReport' still has to be received from the SSF. + +#### **3.3.34.2.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +#### **3.3.34.3 Responding Entity (SSF)** + +##### **3.3.34.3.1 Normal procedure** + +SSF Precondition: + +- State C, "Waiting for Instructions"; or +State F, "Monitoring" or hand-off waiting for instructions. + +SSF Postcondition: + +- "Idle", state a, after sending any outstanding 'CallInformationReport'. Possible armed EDPs are ignored. All connections and resources related to the call are released. + +##### **3.3.34.3.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +#### **3.3.35 RemoveEntry procedure** + +##### **3.3.35.1 General description** + +The X.500 'RemoveEntry' operation is used to request the SDF to remove a leaf entry (either an object entry or an alias entry) from the DIT. For a full description of the RemoveEntry operation, see 11.2/X.511. + +##### **3.3.35.1.1 Parameters** + +See 11.2.2/X.511 and 11.2.3/X.511. + +##### **3.3.35.2 Invoking Entity (SCF)** + +##### **3.3.35.2.1 Normal procedure** + +SCF Precondition: + +- SCSM: "SDF Bound" or "Wait for Subsequent Requests". + +SCF Postcondition: + +- SCSM: "SDF Bound". + +When the SCSM is in the state "Wait for Subsequent Requests" and a need of the service logic to remove an entry from the SDF exists, an internal event [(e2) Request\_to\_SDF] occurs. Until the application process has not indicated with a delimiter (or a timer expiry) that the operation should be sent, the SCSM remains in the state "Wait for Subsequent Requests" and the operation is not sent. The operation is sent to the SDF in a message containing a Bind argument. The SCSM waits for the response from the SDF. The reception of the response [(E5) Response\_from\_SDF\_with\_Bind or (E4) Bind\_Error] to the Bind operation previously issued to the SDF causes a transition of the SCF to the state "SDF Bound" or to the state "Idle". When the SCSM has moved to state "Idle", the RemoveEntry operation was discarded. In the State "SDF Bound", the response of the RemoveEntry operation [(E7) Response\_from\_SDF] causes a transition of the SCF to the same state ("SDF Bound"). It may be either the result of the RemoveEntry operation or an error. + +When the SCSM is in the state "SDF Bound" and a need of the service logic to remove an entry from the SDF exists, an internal event occurs. This event, called (e6) Request\_to\_SDF causes a transition to the same state "SDF Bound" and the SCSM waits for the response from the SDF. The reception of the response [(E7) Response\_from\_SDF] to the RemoveEntry operation previously issued to the SDF causes a transition of the SCF to the same state "SDF Bound". The response from the SDF may be either the result of the RemoveEntry operation or an error. + +### **3.3.35.2.2 Error handling** + +Generic error handling for the operation related errors is described in 11.2.4/X.511 and 11.2.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +### **3.3.35.3 Responding Entity (SDF)** + +#### **3.3.35.3.1 Normal procedure** + +SDF Precondition: + +- SDSM: "SCF Bound" or "Bind Pending". + +SDF Postcondition: + +- SDSM "SCF Bound". + +When the SDF is in the state "Bind Pending", the external event (E3) Request\_from\_SCF caused by the reception of a 'RemoveEntry' operation from the SCF occurs. The SDF does not proceed to the operation until a Bind operation has been successfully executed. It remains in the same state. + +When the SDF is in the state "SCF Bound", the external event (E7) Request\_from\_SCF caused by the reception of a 'RemoveEntry' operation from the SCF occurs. The SDF waits for the response to the operation. + +On the receipt of the event (E7) and before removing the entry item, the SDF takes the following actions: + +- verify that the object to be removed exists and is a leaf entry; +- verify that the access rights to remove the entry are sufficient. + +After the specified actions indicated above are successfully executed, the entry is removed from the SDF database. A null result is returned to the SCF. The sending of the result corresponds to the event (e6) Response\_to\_SCF. + +#### **3.3.35.3.2 Error handling** + +Generic error handling for the operation related errors is described in 11.2.4/X.511 and 11.2.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +### **3.3.36 RequestCurrentStatusReport procedure** + +#### **3.3.36.1 General description** + +This operation is used to request the SSF to watch the current status (busy or idle) of particular termination resource. + +##### **3.3.36.1.1 Parameters** + +- resourceID: +This parameter indicates the physical termination resource which is requested by the SCF to be monitored by the SSF. This parameter is one of the lineID, facilityGroupID, facilityGroupMemberID, or trunkGroupID. +- resourceStatus: + +#### **3.3.36.2 Invoking Entity (SCF)** + +##### **3.3.36.2.1 Normal procedure** + +SCF Preconditions: + +- 1) The SLPI has been determined that a "Request Current Status Report" operation has to be sent. +- 2) The SCME is in the state "Status Report Idle". + +SCF Postcondition: + +- The SCME is in the state "Waiting for SSF Response Status Report". + +When the SPLI requests to watch the status of physical termination resource, the SCF sends "Request Current Status Report" operation to the SSF to request the SSF watch the status of a specific termination resource. Then the SCME is moved to the state "Waiting for SSF Response Status Report" from the state "Status Report Idle". The SCME is returned to the State "Status Report Idle", when the SCF receives a response from the SSF. + +Clarification on the use of this operation within or outside the context of a call is for further study. + +### **3.3.36.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### **3.3.36.3 Responding Entity (SSF)** + +#### **3.3.36.3.1 Normal procedure** + +SSF Precondition: + +- The SSME is in one of the following states: +state ma: "IdleManagement"; +state mb: "Non\_Call\_Associated\_Treatment". + +SSF PostCondition: + +- The SSME is in the state "Non\_Call\_Associated\_Treatment". + +On receipt of this operation, the SSF watches the status of specific termination resource, and the SSF sends ReturnResult of this operation with result of the watched status to the SCF. If an error is occurred (e.g. the SSF cannot find specific termination resource), then the SSF sends ReturnError of this operation with proper error type to the SCF. + +### **3.3.36.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### **3.3.37 RequestFirstStatusMatchReport procedure** + +NOTE – For RequestEveryStatusChangeReport procedure, see 3.3.55. + +#### **3.3.37.1 General description** + +This operation is used to request the SSF start to monitor the status of particular termination resource is changed in the specific status (busy or idle). + +##### **3.3.37.1.1 Parameters** + +- resourceID: +This parameter indicates the physical termination resource which is requested by the SCF to be monitored by the SSF. This parameter is one of the lineID, facilityGroupID, facilityGroupMemberID, or trunkGroupID. +- resourceStatus: +This parameter indicates the status which is requested to detect by SCF of termination resource. +- correlationID: +Used by the SCF for correlation with a previous operation. +- monitorDuration: +This parameter indicates the maximum time duration for monitoring in the SSF. + +### 3.3.37.2 Invoking Entity (SCF) + +#### 3.3.37.2.1 Normal procedure + +SCF Preconditions: + +- 1) The SLPI has been determined that a "Request First Status Match Report" operation has to be sent. +- 2) The SCME is in the state "Status Report Idle". + +SCF Postcondition: + +- The SCME is in the state "Waiting for SSF Response Status Report". + +When the SPLI requests to monitor the status of physical termination resource, the SCF sends "Request First Status Match Report" operation to the SSF to request the SSF start to monitor a specific termination resource. Then the SCME is moved to the state "Waiting for SSF Response Status Report" from the state "Status Report Idle". After this, in the case that the SCF receives ReturnResult of this operation, the SCME is remained in same status. When the SCF receives ReturnError of this operation, the SCME is returned to the state "Status Report Idle". + +The SCME is returned to the state "Status Report Idle", when the SCF is received a Status Report operation from the SSF. + +Clarification on the use of this operation within or outside the context of a call is for further study. + +#### 3.3.37.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### 3.3.37.3 Responding Entity (SSF) + +#### 3.3.37.3.1 Normal procedure + +SSF Precondition: + +- The SSME is in one of the following states: +state ma: "IdleManagement"; +state mb: "Non\_Call\_Associated\_Treatment". + +SSF Postcondition: + +- The SSME is in one of the following states: +state ma: "IdleManagement"; +state mb: "Non\_Call\_Associated\_Treatment". + +On receipt of this operation, the SSF starts to monitor the status of particular termination resource and the SSF sends ReturnResult of this operation to the SCF. If an error is occurred (e.g. the SSF cannot find specific termination resource), then the SSF sends ReturnError of this operation with proper error type to the SCF. + +The SSF continuously monitors the status of particular termination resource till the status is changed in specific state or timer which is specified by monitorDuration parameter is expired. If the SSF finds the change of status in specific state, the SSF sends "Status Report" operation to the SCF with monitorCondition parameter set to "statusReport". If the timer expiration is occurred, the SSF sends "StatusReport" operation to the SCF with monitorCondition parameter is set to "timerExpired". Another case, the SSF receives "Cancel Status Report" operation from the SCF, the SSF sends "Status Report" operation to the SCF with monitorCondition parameter set to "Canceled". After the SSF sends this operation, the SSME should move to the state "IdleManagement" unless there are another processes of Non-Call Associated operation, in which case the SSF should remain in the "Non\_Call\_Associated\_Treatment". + +### 3.3.37.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +## 3.3.38 RequestNotificationChargingEvent procedure + +### 3.3.38.1 General description + +This operation is used to instruct the SSF how to manage the charging events which are received from other FE's not under the control of the service logic instance. The operation supports the options to cope with the interactions concerning the charging (refer to Appendix II.4/Q.1214 "Charging scenarios"). As several connection configurations may be established during a call, a possibility exists for the RequestNotificationChargingEvent (RNC) operation to be invoked on multiple occasions. For each connection configuration an RNC may be used several times. + +#### 3.3.38.1.1 Parameters + +- Sequence of ChargingEvent: + +This parameter contains a list of the charging events and the corresponding monitor types and corresponding legs. For each element in the list the following information elements are included: + +- eventTypeCharging: + +This subparameter indicates the charging event type. Its content is network operator specific, which may be "charge pulses" or "charge messages". + +- monitorMode: + +This subparameter indicates the monitorMode applicable for the corresponding "eventTypeCharging" subparameter. Monitor may be "interrupted", "notifyAndContinue" or "transparent". + +- legID: + +This subparameter indicates the leg id of the corresponding event type charging subparameter. + +#### 3.3.38.2 Invoking Entity (SCF) + +##### 3.3.38.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) An SLPI has determined that a "RequestNotificationChargingEvent" has to be sent by the SCF. + +SCF Postconditions: + +- 1) No FSM state transition; +- 2) SLPI execution may continue. + +The SCSM-FSM is in state "Preparing SSF Instruction" or is in state "Queueing FSM". This operation is invoked by the SCF if a SLPI results in the instruction of SSF how to cope with the interactions concerning the charging. This causes no SCSM-FSM state transition. + +#### 3.3.38.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.38.3 Responding Entity (SSF) + +#### 3.3.38.3.1 Normal procedure + +SSF Preconditions: + +- SSF-FSM: State c: "Waiting for Instructions"; or +SSF-FSM State d: "Waiting for End of User Interaction"; or + +SSF-FSM State e: "Waiting for End of Temporary Connection"; or +SSF-FSM State f: "Monitoring"; or +Assisting/Hand-off SSF-FSM State b: "Waiting for Instructions". + +SSF Postcondition: + +- No FSM state transition. + +On receipt of this operation the SSF performs actions to cope with the interactions concerning the charging according to the information elements included in the operation. The requested charging event can be caused by: + +- a) another SLPI; or +- b) another exchange. + +Irrespective of by what the charging event is caused, the SSF performs one of the following actions on occurrence of the charging event (according the corresponding monitorMode): + +- **Interrupted:** +Notify the SCF of the charging event using "EventNotificationCharging" operation, do not process the event or propagate the signal. However, call and existing charging processing will not be suspended in the SSF. +- **NotifyAndContinue:** +Notify the SCF of the charging event using "EventNotificationCharging", and continue processing the event or signal without waiting for SCF instructions (handled like EDP-N for BCSM events). +- **Transparent:** +Do not notify the SCF of the event. This ends the monitoring of a previously requested charging event. + +Requested charging events are monitored until ended by a transparent monitor mode (or in the case of charging events) until the end of the connection configuration. + +In the case that multiple "RequestNotificationChargingEvent" operations are received for the same connection configuration with the same "eventTypeCharging" and "legID", only the last received "monitorMode" will apply. + +### 3.3.38.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.39 RequestReportBCSMEVENT procedure + +#### 3.3.39.1 General description + +This operation is used to request the SSF to monitor for a call-related event (e.g. BCSM events such as busy or no answer), then send a notification back to the SCF when the event is detected. + +NOTE – If the RequestReportBCSMEVENT requests arming of the current DP from which the call processing was suspended, the next occurrence of the DP encountered during BCSM processing will be detected (i.e. not the current one from which the call was suspended). + +##### 3.3.39.1.1 Parameters + +- bcsmEvents: + +This parameter specifies the event or events of which a report is requested. + +- a) eventTypeBCSM: + +This parameter specifies the type of event of which a report is requested. Values origAttemptAuthorized and termAttemptAuthorized are not valid for the eventTypeBCSM parameter. + +b) monitorMode: + +This parameter indicates how the event should be reported. When the 'monitorMode' is 'interrupted', the event shall be reported as a request, if the 'monitorMode' is 'notifyAndContinue', the event shall be reported as a notification, if the 'monitorMode' is 'transparent', the event shall not be reported. + +c) legID: + +This parameter indicates the party in the call for which the event shall be reported. SCF will use the option 'sendingSideID' only. + +– sendingSideID: + +The following values for 'legID' are assumed: + +legID = 1 indicates the party that was present at the moment of the 'InitialDP' or a DP-specific operation (in case of a mid call trigger, the party causing the trigger), or the party that was created with an 'InitiateCallAttempt' operation. + +legID = 2 indicates the party that was created with a 'Connect' operation, or in case of a mid call trigger, the party not causing the trigger. + +If not included, the following defaults are assumed: + +legID = 1 for the events CollectedInfo, AnalysedInformation, O-Abandon and T-Abandon. + +legID = 2 for the events RouteSelectFailure, O-CalledPartyBusy, O-NoAnswer, O-Answer, T-Busy, T-NoAnswer and T-Answer. + +The 'legID' parameter shall always be included for the events O-MidCall, O-Disconnect, T-MidCall and T-Disconnect. + +d) dPSpecificCriteria: + +This parameter indicates information specific to the EDP to be armed. + +– numberOfDigits: + +This parameter indicates the number of digits to be collected by the SSF for the CollectedInfo event. If the indicated number of digits is collected, SSF reports the event to the SCF. + +– applicationTimer: + +This parameter indicates the application timer for the NoAnswer event. If the user does not answer the call within the allotted time, the SSF reports the event to the SCF. This timer is expected to be shorter than the network no-answer timer. + +e) bcsmEventCorrelationID: + +Used by the SCF for correlation with a previous operation. + +### 3.3.39.2 Invoking Entity (SCF) + +#### 3.3.39.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) The SLPI has decided that a request for an event report BCSM is needed. +- 3) The SCSM-FSM is in the appropriate state to send 'RequestReportBCSMEvent'. + +SCF Postconditions: + +- 1) The SCSM-FSM remains in the same state. +- 2) SLPI execution continues. +- 3) If all EDPs have been disarmed and neither a CallInformationReport nor an ApplyChargingReport is pending, the control relationship with the concerned SSF is ended. If no other relationship persists, the SCSM shall return to "Idle" state. + +### **3.3.39.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.39.3 Responding Entity (SSF)** + +#### **3.3.39.3.1 Normal procedure** + +SSF Precondition: + +- The SSF-FSM is in either the state "Waiting for Instructions" or the state "Monitoring". + +SSF Postconditions: + +- 1) The requested EDPs have been armed as indicated. +- 2) Previously requested events are monitored until ended by a transparent monitor mode, until the end of the call, until the EDPs are detected or until the corresponding leg is released. +- 3) The SSF-FSM remains in the same state. +- 4) If all EDPs have been disarmed and no "CallInformationReport" or "ApplyChargingReport" has been requested, the SSF-FSM moves to the state "Idle". + +#### **3.3.39.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.40 ResetTimer procedure** + +#### **3.3.40.1 General description** + +This class 2 operation is used by the SCF to refresh the $T_{\text{SSF}}$ application timer, in order to avoid the $T_{\text{SSF}}$ time-out at the SSF. + +##### **3.3.40.1.1 Parameters** + +- timerID: +This parameter has a default value identifying the $T_{\text{SSF}}$ timer. +- timerValue: +This parameter specified the value to which the $T_{\text{SSF}}$ is to be set. + +#### **3.3.40.2 Invoking Entity (SCF)** + +##### **3.3.40.2.1 Normal procedure** + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) An SLPI has determined by the $T_{\text{SCF-SSF}}$ guard timer expiration that the 'ResetTimer' operation has to be sent in order to avoid $T_{\text{SSF}}$ time-out at the SSF. + +SCF Postcondition: + +- The SLPI reset the $T_{\text{SCF-SSF}}$ guard timer. + +#### **3.3.40.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.40.3 Responding Entity (SSF)** + +#### **3.3.40.3.1 Normal procedure** + +SSF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Basic call processing has been suspended at a DP. + +- 3) The SSF-FSM is in the "Waiting for Instruction" state or in the "Waiting for End of User Interaction" state or in the "Waiting for End of Temporary Connection" state or Assisting/hand-off waiting for instructions or Assisting/hand-off waiting for end of user interaction. + +NOTE – Whether the $T_{\text{SSF}}$ is used or not in the state "Waiting for End of User Interaction" or in the state "Waiting for End of Temporary Connection" is network operator dependent. + +SSF Postconditions: + +- 1) The $T_{\text{SSF}}$ timer has been reset. +- 2) The SSF-FSM remains in the same state. + +### 3.3.40.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.41 RouteSelectFailure Procedure + +#### 3.3.41.1 General description + +This operation is sent by the SSF to the SCF after detecting a valid trigger condition at the RouteSelectFailure DP, or to report an event requested by RequestReportBCSMEEvent. Refer to 4.2.2.2/Q.1214 for additional call modelling related semantics. + +##### 3.3.41.1.1 Parameters + +- serviceAddressInformation (serviceKey, miscCallInfo, triggerType): + +See Recommendation Q.1290. The triggerType indicates the particular event which caused call suspension. The miscCallInfo indicates that a request for instructions or a notification has been issued to the SCF and the category for the trigger (line, group, office). The serviceKey is used in identifying the service logic to be invoked. + +- bearerCapability: + +This parameter indicates the type of bearer capability connection to the user. Refer to 6.4.4/Q.1214 for population rules for the bearer capability parameter. + +- calledPartyNumber: + +See Q.762 Called Party Number signalling information. This parameter is used to identify the called party in the forward direction. + +- callingPartyNumber: + +See Q.762 Calling Party Number signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartyNumber parameter. + +- callingPartysCategory: + +See Q.762 Calling Party's Category signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartysCategory parameter. + +- iPSSPCapabilities: + +See Recommendation Q.1290. + +- iPAvailable: + +See Recommendation Q.1290. + +- iSDNAccessRelatedInformation: + +This parameter contains (possibly multiple) information elements as per Recommendation Q.931. See Access Transport Parameter signalling information in Recommendations Q.762, Q.763 and Q.931. Refer to 6.4.4/Q.1214 (Analysed Information) for population rules for ISDN access related information. + +- cGEncountered: + +See Recommendation Q.1290. + +- locationNumber: + +See Q.762 Location Number signalling information. This parameter is used to convey the geographical area address for mobility services. It is used when the "callingPartyNumber" does not contain any information about the geographical location of the calling party (e.g. origin dependent routing when the calling party is a mobile subscriber). + +- serviceProfileIdentifier: + +See Annex A/Q.932. Refer to 6.4.4/Q.1214 for population rules for serviceProfileIdentifier. + +- terminalType: + +See Recommendation Q.1290. Identifies the terminal type so that the SCF can specify, to the SRF, the appropriate type of capability (voice recognition, DTMF, display capability, etc.). + +- chargeNumber: + +See Recommendation Q.1290. + +- servingAreaID: + +See Recommendation Q.1290. + +- dialledDigits: + +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules. + +- callingPartyBusinessGroupID: + +See Recommendation Q.1290. + +- callingPartySubaddress: + +See Recommendation Q.931. + +- callingFacilityGroup: + +See Recommendation Q.1290. + +- callingFacilityGroupMember: + +See Recommendation Q.1290. + +- failureCause: + +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules. + +- originalCalledPartyID: + +See Q.762 Original Called Number signalling information. + +- prefix: + +See Recommendation Q.1290. Refer to 6.4.4/Q.1214 for population rules. + +- redirectingPartyID: + +This parameter (if available) is the directory number of the last redirecting party. + +- redirectionInformation: + +See Q.763 Redirection Information signalling information. + +- routeList: + +See Recommendation Q.1290. + +- travellingClassMark: + +See Recommendation Q.1290. + +- carrier: + +See Recommendation Q.1290. + +### **3.3.41.2 Invoking Entity (SSF)** + +#### **3.3.41.2.1 Normal procedure** + +SSF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Called Party Number is available and nature of address determined. +- 3) Call gapping or service filtering are not in effect for the call segment. +- 4) DP criteria have been met. +- 5) For a TDP-R, there is no existing control relationship influencing the call segment. + +SSF Postconditions: + +- 1) For a TDP-R, basic call processing has been suspended at Route\_Select\_Failure DP, and a control relationship has been established. +- 2) For a TDP-N, basic call processing proceeds at O\_Exception, and no control relationship has been established. +- 3) For an EDP, as for EventReportBCSM procedure (see 3.3.22.2.1). + +#### **3.3.41.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### **3.3.41.3 Responding Entity (SCF)** + +#### **3.3.41.3.1 Normal procedure** + +SCF Preconditions (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +#### **3.3.41.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### **3.3.42 Search procedure** + +#### **3.3.42.1 General description** + +The X.500 'Search' operation is used to search a portion of the SDF resident DIT for entries of interest and to return selected information from those entries. For a full description of the Search operation, see 10.2/X.511. + +##### **3.3.42.1.1 Parameters** + +See 10.2.2/X.511 and 10.2.3/X.511. + +#### **3.3.42.2 Invoking Entity (SCF)** + +##### **3.3.42.2.1 Normal procedure** + +SCF Precondition: + +- 1) SCSM: "SDF Bound" or "Wait for Subsequent Requests". + +SCF Postcondition: + +- SCSM: "SDF Bound". + +When the SCSM is in the state "Wait for Subsequent Requests" and a need of the service logic to search and/or read information of the SDF exists, an internal event [(e2) Request\_to\_SDF] occurs. Until the application process has not indicated with a delimiter that the operation should be sent, the SCSM remains in the state "Wait for Subsequent Requests" and the operation is not sent. The operation is sent to the SDF in a message containing a Bind argument. The SCSM waits for the response from the SDF. The reception of the response [(E5) Response\_from\_SDF\_with\_Bind or (E4) Bind\_Error] to the Bind operation previously issued to the SDF causes a transition of the SCF to the state "SDF Bound" or to the state "Idle". When the SCSM has moved to state "Idle", the Search operation was discarded. In the State "SDF Bound", the response of the Search operation [(E7) Response\_from\_SDF] causes a transition of the SCF to the same state ("SDF Bound"). It may be either the result of the Search operation or an error. + +When the SCSM is in the state "SDF Bound" and a need of the service logic to search and/or read information of the SDF exists, an internal event occurs. This event, called (e6) Request\_to\_SDF causes a transition to the same state "SDF Bound" and the SCSM waits for the response from the SDF. The reception of the response [(E7) Response\_from\_SDF] to the Search operation previously issued to the SDF causes a transition of the SCF to the same state "SDF Bound". The response from the SDF may be either the result of the Search operation or an error. + +##### **3.3.42.2.2 Error handling** + +Generic error handling for the operation related errors is described in 10.2.4/X.511 and 10.2.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +#### **3.3.42.3 Responding Entity (SDF)** + +##### **3.3.42.3.1 Normal procedure** + +SDF Precondition: + +- 1) SDSM: "SCF Bound" or "Bind Pending". + +SDF Postcondition: + +- SDSM "SCF Bound". + +When the SDF is in the state "Bind Pending", the external event (E3) Request\_from\_SCF caused by the reception of a 'Search' operation from the SCF occurs. The SDF does not proceed to the operation until a Bind operation has been successfully executed. It remains in the same state. + +When the SDF is in the state "SCF Bound", the external event (E7) Request\_from\_SCF caused by the reception of a 'Search' operation from the SCF occurs. The SDF waits for the response to the operation. + +On the receipt of the event (E7) and before retrieving the data as specified in the operation parameters, the SDF takes the following actions: + +- verify that the objects accessed by the request exists; +- verify that the user on behalf of whom the request is performed has sufficient access rights to access the objects and attributes reached during the execution of the operation; +- verify that attributes on which an operation should be performed exist in the object. + +After the specified actions indicated above are successfully executed, the SDF returns all the possible attributes that satisfy the retrieval criteria to the SCF. The sending of the result corresponds to the event (e6) Response\_to\_SCF. + +### 3.3.42.3.2 Error handling + +Generic error handling for the operation related errors is described in 10.2.4/X.511 and 10.2.5/X.511 and the TCAP services that are used for reporting operating errors are described in 2.2.2. + +## 3.3.43 SelectFacility procedure + +### 3.3.43.1 General description + +This operation is sent by the SCF to the SSF and requests the SSF to perform the terminating basic call processing actions to select the terminating line if it is idle, or selects an idle line from a multi-line hunt group, or selects an idle trunk from a trunk group, as appropriate. If no idle line or trunk is available, the SSF determines that the terminating facility is busy. Refer to 4.2.2.2/Q.1214 for additional call modelling related semantics. + +#### 3.3.43.1.1 Parameters + +- alertingPattern: +See Recommendation Q.1290. It only applies if the network signalling supports this parameter or if SSF is the terminating local exchange for the subscriber. +- destinationNumberRoutingAddress: +This parameter contains the called party number towards which the call is to be routed. The encoding of the parameter is defined in Recommendation Q.763. +- iSDNAccessRelatedInformation: +This parameter contains (possibly multiple) information elements as per Recommendation Q.931. See Access Transport Parameter signalling information in Recommendations Q.762, Q.763 and Q.931. Refer to 6.4.4/Q.1214 (Analysed Information) for population rules for ISDN access related information. +- calledFacilityGroup: +See Recommendation Q.1290. +- calledFacilityGroupMember: +See Recommendation Q.1290. +- originalCalledPartyID: +See Q.762 Original Called Number signalling information. + +#### 3.3.43.2 Invoking Entity (SCF) + +##### 3.3.43.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) An SLPI has determined that a “SelectFacility” is to be sent by the SCF. + +SCF Postcondition: + +- SLPI execution may continue. + +In the SCSM-FSM state “Preparing SSF Instructions”, this operation is invoked by an SCF if the service logic results in the request to an SSF to route a call to a specific destination and to continue call processing at the Select\_Facility\_and\_Present\_Call PIC. If no event monitoring has been requested and no reports (CallInformationReport and ApplyChargingReport) have been requested in a previously sent operation, an SCSM-FSM transition to the state “Idle” occurs. Otherwise, if event monitoring has been requested or any report (CallInformationReport and ApplyChargingReport) has been requested, the SCSM-FSM transitions to the state “Waiting for Notification or Request”. + +#### **3.3.43.2.2 Error handling** + +If reject or error messages are received, then the SCSM informs the SLPI of the message and remains in the state “Preparing SSF Instructions”. + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +#### **3.3.43.3 Responding Entity (SSF)** + +##### **3.3.43.3.1 Normal procedure** + +SSF Preconditions: + +- 1) Call termination attempt has been initiated. +- 2) Basic call processing has been suspended at a DP. +- 3) The SSF waits for instructions. + +SSF Postconditions: + +- 1) The SSF performs call processing action to route the call to the specified destination and applies the appropriate alerting pattern. +- 2) In the T-BCSM, call processing resumes at the Select\_Facility\_and\_Present\_Call PIC. + +##### **3.3.43.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +#### **3.3.44 SelectRoute procedure** + +##### **3.3.44.1 General description** + +This operation requests the SSF to perform the originating basic call processing actions to determine routing information and select routing for a call, based either on call information available at the SSF or on call information provided by the SCF. Based on the routing information provided, the SSF attempts to select a primary route for the call. If the route is busy, the SSF attempts to select an alternative route. The SSF may fail to select a route for the call if all routes are busy. + +##### **3.3.44.1.1 Parameters** + +- destinationRoutingAddress: +Represents a list of called party numbers (primary and alternates). +- alertingPattern: +See Recommendation Q.1290. It only applies if the network signalling supports this parameter or if SSF is the terminating local exchange for the subscriber. +- correlationID: +Used by the SCF to associate the 'AssistRequestInstructions' operation from the assisting SSF with the Request from the initiating SSF. The 'correlationID' is used in the context of a hand-off procedure and only if the correlation id is not embedded in the 'destinationRoutingAddress'. + +- iSDNAccessRelatedInformation: +Carries the same information as the protocol element ISUP Access Transport parameter in Recommendation Q.762. +- originalCalledPartyID: +See Q.762 Original Called Number signalling information. +- routeList: +See Recommendation Q.1290. +- scfID: +Used by an assisting SSF to identify which SCF the 'destinationRoutingAddress' should be sent to. +- travellingClassMark: +See Recommendation Q.1290. +- carrier: +See Recommendation Q.1290. In this message, the carrier selection field is null (00000000) and Carrier ID indicates the carrier to use for the call. + +### 3.3.44.2 Invoking Entity (SCF) + +#### 3.3.44.2.1 Normal procedure + +SCF Preconditions: + +- 1) Call origination attempt has been initiated. +- 2) Authority/ability to place outgoing call has been verified. +- 3) Destination information is available in the SSF or provided by the SCF. +- 4) Basic call processing has been suspended at one of the following DPs: + - Origination\_Attempt\_Authorized; + - Collected\_Info; + - Analysed\_Info; + - Route\_Select\_Failure; + - O\_Called\_Party\_Busy; + - O\_No\_Answer; + - O\_Disconnect (called party disconnect only). +- 5) A control relationship has been established and the SLPI is processing the incoming request. + +SCF Postconditions: + +- 1) SLPI execution is terminated if no monitoring is requested. +- 2) SLPI execution is suspended pending the monitored event occurring, if monitoring is requested. + +The SelectRoute message requests the SSF-CCF to resume call origination processing taking into account the address and routing information provided in the message parameters. Call Processing resumes at the ROUTING & ALERTING PIC. + +#### 3.3.44.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.44.3 Responding Entity (SSF) + +#### 3.3.44.3.1 Normal procedure + +SSF Precondition: + +- A TDP or EDP request has been invoked. + +SSF Postcondition: + +- The SSF performs the call processing actions to select the route. + +The SSF-CCF shall resume call processing at the ROUTING & ALERTING PIC and proceed according to the BCSM description to attempt to complete the call over the designated route. + +The following additional requirements also apply to the SelectRoute message: + +- Alternate route/carrier selection as indicated in the SelectRoute shall proceed until either an idle facility is found or until processing of the call encounters a screening feature which blocks the call. (Network operator specific.) +- If a route requires a TCM, the value in the TCM parameter shall be used. If a TCM is required and the TCM parameter is not supplied in the SelectRoute, the SSF-CCF shall derive the TCM in accordance with requirements that apply assuming no IN involvement with the call. + +SelectRoute and O\_Called\_Party\_Busy, O\_No\_Answer: + +- When the SSF-CCF receives the SelectRoute message in response to an O\_Called\_Party\_Busy message the SSF-CCF shall do the following: + - 1) The SSF-CCF shall release any resources that were used to process the call between the ANALYSE\_INFORMATION and ROUTING & ALERTING PICs. + - 2) The SSF-CCF shall resume call processing at the ROUTING & ALERTING PIC, and process the message as described in this procedure description. + - 3) If the originating access is DSS 1, then the SSF-CCF shall not send another CALL PROCeeding message (INAP-DSS 1 interworking is for further study). +- When the SelectRoute message is received in response to an O\_No\_Answer TDP-Request Message, the SSF-CCF shall do the following: + - 1) The SSF-CCF, if it is providing audible ringing tone to the calling party, shall remove this tone. + - 2) The SSF-CCF shall release any resources that were used to process the call between the ANALYSE\_INFORMATION and ROUTING & ALERTING PICs. + - 3) The SSF-CCF shall resume call processing at the ROUTING & ALERTING PIC, and process the message as described in this procedure description. + - 4) If the originating access is DSS 1, then the SSF-CCF shall not send another CALL PROCeeding message (INAP-DSS 1 interworking is for further study). +- When the SelectRoute message is received in response to an O\_No\_Answer EDP-Request message, the SSF-CCF shall do the following: + - 1) The SSF-CCF, if it is providing audible ringing tone to the calling party, shall remove this tone. + - 2) The SSF-CCF shall resume call processing at the ROUTING & ALERTING PIC, and process the message as described in this Recommendation. + - 3) If the originating access is DSS 1, then the SSF-CCF shall not send another CALL PROCeeding message (INAP-DSS 1 interworking is for further study). + +SelectRoute with OriginalCalledPartyID: + +- When the SSF-CCF receives a SelectRoute message that contains the OriginalCalledPartyID parameter, the SSF-CCF shall map the received OriginalCalledPartyID parameter to, for example (ISUP interworking is for further study): + - 1) the OriginalCalledNumber information element in the Facility information element if the SSF-CCF does not yet have a value for the OriginalCalledNumber AND if the SSF-CCF routes the call to an ISDN line (for Basic rate and Primary rate ISDN signalling); + - 2) the OriginalCalledNumber parameter in the IAM if the SSF-CCF does not already have a value for the OriginalCalledNumber AND if the SSF-CCF routes the call to an SS7 trunk (for ISDN-UP signalling). + +### 3.3.44.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.45 SendChargingInformation procedure + +#### 3.3.45.1 General description + +This operation is used to instruct the SSF on the charging information to be sent by the SSF. The sending of charging information can either be by charge pulses or signalling or internal if SSF is located in the Local Exchange (LE). In the LE, either charge meter can be updated or a standard call record created. A possibility exists for the SendChargingInformation (SCI) operation to be invoked on multiple occasions. The charging scenario supported by this operation is: 3.2 (refer to Appendix II/Q.1214, "Charging scenarios"). + +NOTE – The interworking between SSF and PSTN is network operator specific. This operation has much PSTN/IN interactions. + +#### 3.3.45.1.1 Parameters + +- sCIBillingChargingCharacteristics: + +This parameter indicates billing and/or charging characteristics. Its content is network operator specific. Depending on the applied charging scenario, the following information elements can be included (refer to Appendix II/Q.1214, "Charging scenarios"): + +- charge level (scenario 3.2); +- chargePulses; +- chargeMessages. +- partyToCharge: + +This parameter indicates where the charging information must be sent. + +#### 3.3.45.2 Invoking Entity (SCF) + +##### 3.3.45.2.1 Normal procedure + +SCF Preconditions: + +- 1) A control relationship exists between the SCF and the SSF. +- 2) An SLPI has determined that a "SendChargingInformation" has to be sent by the SCF. + +SCF Postconditions: + +- 1) No FSM state transition; +- 2) SLPI execution may continue. + +The SCSM-FSM is in state "Preparing SSF Instruction" or is in state "Queueing FSM". The SendChargingInformation procedure shall be invoked by the SCF in accordance with the demands of the SLPI for relevant charging information. If appropriate this information shall be sent back down the call path. + +This causes no SCSM-FSM state transition. + +#### 3.3.45.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +#### 3.3.45.3 Responding Entity (SSF) + +##### 3.3.45.3.1 Normal procedure + +SSF Preconditions: + +- SSF-FSM: State c: "Waiting for Instructions"; or +- SSF-FSM: State d: "Waiting for End of User Interaction"; or +- SSF-FSM: State e: "Waiting for End of Temporary Connection"; or + +SSF-FSM: State f: "Monitoring"; or +Assisting/hand-off SSF-FSM State b: "Waiting for Instructions". + +SSF Postcondition: + +- No FSM state transition. + +On receipt of this operation the SSF performs actions to send the charging information. The sending of charging information can either be by charge pulses or signalling or internal if SSF is located in LE. In the LE, either charge metre can be updated or a standard call record created. The interworking between SSF and PSTN is network operator specific. This operation has much PSTN/IN interactions. + +For instance, by sending an operation "SendChargingInformation" the SCF instructs the SSF to initiate the PSTN/ISDN charging functions according to the given information about the charging level to use. + +The charging level can be determined either by one of the following functions: + +- a) the SCF; or +- b) the SSF; or +- c) the charging function in a succeeding exchange. + +In case the SCF has determined the charging level, the "SendChargingInformation" operation contains the charging level to be applied. + +In case the SSF determines the charging level, the "SendChargingInformation" operation contains the parameters to determine the charging level. + +If the charging level was determined by the IN (SCF or SSF), the SSF provides the charging level to be applied to the PSTN/ISDN charging functions [cases a) and b)]. + +In case c), the charging level is determined in a succeeding exchange. The "SendChargingInformation" operation either contains the corresponding parameters indicating this fact or the SSF detects during trying to determine the charging level based on SCF provided parameters that the charging level shall be determined in a succeeding exchange. Based on already existing PSTN/ISDN capabilities, the SSF provides the PSTN/ISDN charging functions with the necessary information and backward charge messages shall be transferred down the call path when allowed by the SCF (generated by a succeeding exchange, for example an international gateway). + +In the scenario described above, charging/billing is performed by means of existing mechanisms of the PSTN/ISDN initiated and controlled by the IN. + +That means the determination of the charging method – on-line or off-line – and the items to be charged for shall be done in the basic network, just like the charge generation and the charge registration. + +### **3.3.45.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.46 ServiceFilteringResponse procedure** + +#### **3.3.46.1 General description** + +This operation is used to report the values of counters specified in a previous sent 'ActivateServiceFiltering' operation to the SCF. + +##### **3.3.46.1.1 Parameters** + +- countersValue: + +The parameter contains the count of calls filtered during the filtering period. It is a list of counter identifications and the related values. + +- filteringCriteria: + +This parameter is used to address the concerned service logic at the SCF. + +- responseCondition: + +This parameter is used to identify the reason why the ServiceFilteringResponse is sent. + +intermediateResponse indicates that service filtering is active, a call is received and the interval timer is expired; or + +that service filtering is active and the threshold value, 'numberOfCalls', is reached. + +lastResponse indicates that the duration time is expired and service filtering is stopped, or that the stop time is met and service filtering is stopped. + +### 3.3.46.2 Invoking Entity (SSF) + +#### 3.3.46.2.1 Normal procedure + +SSF Preconditions: + +- 1) Service filtering is running and the interval time is expired and a call is received; or +- 2) Service filtering is running and the threshold value is reached; or +- 3) Service filtering has been finished (duration time expired or stop time met); or +- 4) The operation 'ActivateServiceFiltering' is received and encounters an active service filtering entity. + +SSF Postcondition: + +- Service filtering proceeds or is ended depending on the duration time. + +The SSF sends the 'ServiceFilteringResponse' operation to the SCF. The 'filteringCriteria' parameter is provided to enable the addressing of the concerned service logic at the SCF. + +Before 'ServiceFilteringResponse' is sent, it is checked whether call gapping criteria are met. If so, the 'ServiceFilteringResponse' is not sent and the counting continues without resetting the counters. The last 'ServiceFilteringResponse' (stop time is met or duration time expired) is sent without checking any call gap criteria. + +After sending 'ServiceFilteringResponse' the service filtering counters are reset. + +If service filtering proceeds after sending 'ServiceFilteringResponse' (e.g. interval time expired), the SSME-FSM remains in the state "Non\_Call\_Associated\_Treatment". + +If service filtering is stopped after sending 'ServiceFilteringResponse' (duration time expired or stop time is met), then the SSME-FSM moves to the "Idle Management" state. All allocated resources are released, i.e. the SSME-FSM is removed as well. + +#### 3.3.46.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +### 3.3.46.3 Responding Entity (SCF) + +#### 3.3.46.3.1 Normal procedure + +SCF Preconditions: + +- 1) Service filtering is running. +- 2) The SCME is in the state "Waiting for Service Filtering Response". + +SCF Postcondition: + +- The SCME forwards the received counter values to the SLPI. + +The operation is handled by the Service Filtering FSM part of the SCF Management Entity (SCME). The SCME passes the received counter values to the SLPI where they are added to previously received counter values. + +The "filteringCriteria" parameter as provided in "ServiceFilteringResponse" is used to address the SCME and the concerned service logic instance. + +The Service Filtering FSM of the SCME remains in the state "Waiting For SSF Service Filtering Response" until the internal service filtering duration time in the SLPI expires. Then the SLPI informs the SCME about timer expiration. Now the SCME moves to the state "Service Filtering Idle". + +### **3.3.46.3.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +### **3.3.47 SpecializedResourceReport procedure** + +#### **3.3.47.1 General description** + +This operation is used as the response to a "PlayAnnouncement" operation when the announcement completed indication is set. + +##### **3.3.47.1.1 Parameters** + +- None. + +#### **3.3.47.2 Invoking Entity (SRF)** + +##### **3.3.47.2.1 Normal procedure** + +SRF Preconditions: + +- 1) The SRSM-FSM is in the state "User Interaction". +- 2) A "PlayAnnouncement" operation is being executed for which the parameter "RequestAnnouncementComplete" was set TRUE. +- 3) All information has been sent to the user. + +SRF Postconditions: + +- 1) The SRSM-FSM remains in the same state. +- 2) If the "DisconnectFromIPForbidden" parameter was set FALSE, the SRSM initiates a bearer channel disconnect sequence to the SSF using the applicable bearer channel signalling system after sending the "SpecializedResourceReport" operation to the SCF. The SRSM-FSM moves to the state "Idle". + +##### **3.3.47.2.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +#### **3.3.47.3 Responding Entity (SCF)** + +##### **3.3.47.3.1 Normal procedure** + +SCF Precondition: + +- The SCSM-FSM is in the state "User Interaction", substate "Waiting for response from the SRF". + +SCF Postconditions: + +- 1) The SCSM-FSM remains in the same state. +- 2) If the "SpecializedResourceReport" relates to a "PlayAnnouncement" operation with permission of SRF initiated disconnection, the SCSM-FSM moves to the state "Preparing SSF Instructions". + +##### **3.3.47.3.2 Error handling** + +Operation related error handling is not applicable, due to class 4 operation. + +### **3.3.48 StatusReport procedure** + +#### **3.3.48.1 General description** + +This operation is used to notify the result of monitoring that is requested by "RequestFirstStatusMatchReport" or "RequestEveryStatusChangeReport" operation to the SCF. + +##### **3.3.48.1.1 Parameters** + +- **resourceStatus:** +this parameter indicates the detected status of physical termination resource which is requested to monitor by the SCF. +- **CorrelationID:** +Used by the SCF for correlation with a previous operation. +- **ResourceID:** +- **ReportCondition:** +Specifies the reason of issuing this operation (normal status report or monitor duration expired). + +#### **3.3.48.2 Invoking Entity (SSF)** + +##### **3.3.48.2.1 Normal procedure** + +SSF Preconditions: + +- The SSME is in the state "Non\_Call\_Associated\_Treatment". + +SSF Postconditions: + +- The SSME is in one of the following states: +state ma: "IdleManagement"; +state mb: "Non\_Call\_Associated\_Treatment". + +The SSF sends "StatusReport" operation to the SCF, when the following events are occurred: + +- The SSF find the change of status in specific state. +- The SSF received "CancelStatusReportRequest" operation from the SCF. +- The timer expiration is occurred in the SSF. + +After the SSF sends this operation, the SSME should move to the state "IdleManagement" unless there are other processes of Non-Call Associated operation, in which case the SSF should remain in the "Non\_Call\_Associated\_Treatment". + +Clarification on the use of this operation within or outside the context of a call is for further study. + +##### **3.3.48.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +#### **3.3.48.3 Responding Entity (SCF)** + +##### **3.3.48.3.1 Normal procedure** + +SCF Preconditions: + +- The SCME is in the state "Waiting for SSF Response Status Report". + +SCF Postconditions: + +- 1) The SCME is in the state "Status Report Idle". +- 2) The SCF notifies SLPI of the result of resource monitoring in the SSF. + +On receipt of this operation the SLPI which is expecting this operation will continue. + +### **3.3.48.3.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### **3.3.49 TAnswer procedure** + +#### **3.3.49.1 General description** + +This operation is sent from the SSF to the SCF at the T\_Answer DP, after detecting a valid trigger condition, or to report an event requested by RequestReportBCSMEVENT. + +##### **3.3.49.1.1 Parameters** + +- dPSpecificCommonParameters: + - calledPartyBusinessGroupID: +See Recommendation Q.1290. + - calledPartySubaddress: +See Recommendation Q.931. + - calledFacilityGroup: +See Recommendation Q.1290. + - calledFacilityGroupMember: +See Recommendation Q.1290. + +#### **3.3.49.2 Invoking Entity (SSF)** + +##### **3.3.49.2.1 Normal procedure** + +SSF Preconditions (TDP): + +- 1) Incoming call received from originating BCSM. +- 2) Call has been accepted and the terminating party has answered. +- 3) For TDP, call gapping or service filtering are not in effect for the call segment. +- 4) DP criteria have been met. +- 5) For a TDP-R, there is no existing control relationship influencing the call segment. + +SSF Preconditions (EDP): + +- 1) For an EDP-R, there is an existing control relationship and the EDP T\_Answer is armed. +- 2) For an EDP-N, there is an existing monitoring or control relationship and the EDP T\_Answer is armed. + +SSF Postconditions (TDP): + +- 1) For a TDP-R, basic call processing has been suspended at T\_Answer DP, and a control relationship has been established. +- 2) For a TDP-N, basic call processing proceeds at T\_Answer PIC, and no control relationship has been established. + +SSF Postconditions (EDP): + +- 1) The SSF-FSM stays in the state "Monitoring" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested. +- 2) The SSF-FSM moves to the state "idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested. +- 3) The SSF-FSM moves to the state "Waiting for Instructions" if the message type was request. Call processing is interrupted. + +### 3.3.49.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.49.3 Responding Entity (SCF) + +SCF Preconditions (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or + +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or + +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +### 3.3.49.3.1 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +## 3.3.50 TBusy procedure + +### 3.3.50.1 General description + +This operation is sent by the SSF to the SCF after detecting a valid trigger condition at the TBusy DP, or to report an event requested by RequestReportBCSMEVENT. Refer to 4.2.2.2/Q.1214 for additional call modelling related semantics. + +#### 3.3.50.1.1 Parameters + +- serviceAddressInformation (serviceKey, miscCallInfo, triggerType): + +See Recommendation Q.1290. The triggerType indicates the particular event which caused call suspension. The miscCallInfo indicates that a request for instructions or a notification has been issued to the SCF and the category for the trigger (line, group, office). The serviceKey is used in identifying the service logic to be invoked. + +- bearerCapability: + +This parameter indicates the type of bearer capability connection to the user. Refer to 6.4.4/Q.1214 for population rules for the bearer capability parameter. + +- calledPartyNumber: + +See Q.762 Called Party Number signalling information. This parameter is used to identify the called party in the forward direction. + +- callingPartyNumber: +See Q.762 Calling Party Number signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartyNumber parameter. +- callingPartysCategory: +See Q.762 Calling Party's Category signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartysCategory parameter. +- iPSSPCapabilities: +See Recommendation Q.1290. +- iPAvailable: +See Recommendation Q.1290. +- iSDNAccessRelatedInformation: +This parameter contains (possibly multiple) information elements as per Recommendation Q.931. See Access Transport Parameter signalling information in Recommendations Q.762, Q.763 and Q.931. Refer to 6.4.4/Q.1214 (Analysed Information) for population rules for ISDN access related information. +- cGEncountered: +See Recommendation Q.1290. +- locationNumber: +See Q.762 Location Number signalling information. This parameter is used to convey the geographical area address for mobility services. It is used when the "callingPartyNumber" does not contain any information about the geographical location of the calling party (e.g. origin dependent routing when the calling party is a mobile subscriber). +- serviceProfileIdentifier: +See Annex A/Q.932. See 6.4.4/Q.1214 for population rules for serviceProfileIdentifier. +- terminalType: +See Recommendation Q.1290. Identifies the terminal type so that the SCF can specify, to the SRF, the appropriate type of capability (voice recognition, DTMF, display capability, etc.). +- chargeNumber: +See Recommendation Q.1290. +- servingAreaID: +See Recommendation Q.1290. +- busyCause: +See Recommendation Q.1290. See 6.4.4/Q.1214 for population rules. +- calledPartyBusinessGroupID: +See Recommendation Q.1290. +- calledPartySubaddress: +See Recommendation Q.931. +- originalCalledPartyID: +See Q.762 Original Called Number signalling information. +- redirectingPartyID: +This parameter (if available) is the directory number of the last redirecting party. +- redirectionInformation: +See Q.763 Redirection Information signalling information. + +- routeList: +See Recommendation Q.1290. +- travellingClassMark: +See Recommendation Q.1290. + +### **3.3.50.2 Invoking Entity (SSF)** + +#### **3.3.50.2.1 Normal procedure** + +SSF Preconditions: + +- 1) Call termination attempt has been initiated. +- 2) Called Party Number is available and nature of address determined. +- 3) Call gapping or service filtering are not in effect for the call segment. +- 4) DP criteria have been met. +- 5) For a TDP-R, there is no existing control relationship influencing the call segment. + +SSF Postconditions: + +- 1) For a TDP-R, basic call processing has been suspended at T\_Busy DP, and a control relationship has been established. +- 2) For a TDP-N, basic call processing proceeds at T\_Exception, and no control relationship has been established. +- 3) For an EDP, as for EventReportBCSM procedure (See 3.3.22.2.1). + +The SSF has sufficient information available associated with the terminating call portion. The SSF shall detect T\_Busy when the terminating access is network-determined user-busy. The conditions that result in the detection of network-determined user-busy depend on the type of terminating access and subscribed services (an analogue line access, DSS 1, multiline hunt group, etc.). + +#### **3.3.50.2.2 Error handling** + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### **3.3.50.3 Responding Entity (SCF)** + +#### **3.3.50.3.1 Normal procedure** + +SCF Preconditions (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or + +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or + +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +### 3.3.50.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### 3.3.51 TDisconnect procedure + +#### 3.3.51.1 General description + +This operation is sent by the SSF to the SCF after detecting a valid trigger condition at the T\_Disconnect DP, or to report an event requested by RequestReportBCSMEEvent. Refer to 4.2.2.2/Q.1214 for additional call modelling related semantics. + +#### 3.3.51.1.1 Parameters + +- serviceAddressInformation (serviceKey, miscCallInfo, triggerType): + +See Recommendation Q.1290. The triggerType indicates the particular event which caused call suspension. The miscCallInfo indicates that a request for instructions or a notification has been issued to the SCF and the category for the trigger (line, group, office). The serviceKey is used in identifying the service logic to be invoked. + +- bearerCapability: + +This parameter indicates the type of bearer capability connection to the user. Refer to 6.4.4/Q.1214 for population rules for the bearer capability parameter. + +- calledPartyNumber: + +See Q.762 Called Party Number signalling information. This parameter is used to identify the called party in the forward direction. + +- callingPartyNumber: + +See Q.762 Calling Party Number signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartynumber parameter. + +- callingPartysCategory: + +See Q.762 Calling Party's Category signalling information. Refer to 6.4.4/Q.1214 for population rules for the callingPartysCategory parameter. + +- iPSSPCapabilities: + +See Recommendation Q.1290. + +- iPAvailable: + +See Recommendation Q.1290. + +- iSDNAccessRelatedInformation: + +This parameter contains (possibly multiple) information elements as per Recommendation Q.931. See Access Transport Parameter signalling information in Recommendations Q.762, Q.763 and Q.931. Refer to 6.4.4/Q.1214 (Analysed Information) for population rules for ISDN access related information. + +- cGEncountered: + +See Recommendation Q.1290. + +- locationNumber: +See Q.762 Location Number signalling information. This parameter is used to convey the geographical area address for mobility services. It is used when the "callingPartyNumber" does not contain any information about the geographical location of the calling party (e.g. origin dependent routing when the calling party is a mobile subscriber). +- serviceProfileIdentifier: +See Annex A/Q.932. See 6.4.4/Q.1214 for population rules for serviceProfileIdentifier. +- terminalType: +See Recommendation Q.1290. Identifies the terminal type so that the SCF can specify, to the SRF, the appropriate type of capability (voice recognition, DTMF, display capability, etc.). +- chargeNumber: +See Recommendation Q.1290. See 6.4.4/Q.1214 for population rules for chargeNumber. +- servingAreaID: +See Recommendation Q.1290. +- calledPartyBusinessGroupID: +See Recommendation Q.1290. +- calledPartySubaddress: +See Recommendation Q.931 Called Party Subaddress. +- calledFacilityGroup: +See Recommendation Q.1290. +- calledFacilityGroupMember: +See Recommendation Q.1290. +- releaseCause: +Indicates the cause of the disconnect. +- connectTime: +Indicates the duration between the received answer indication from the called party side and the release of the connection. + +### 3.3.51.2 Invoking Entity (SSF) + +#### 3.3.51.2.1 Normal procedures + +SSF Preconditions: + +- 1) Incoming call received from originating BCSM. +- 2) Call has been accepted and the terminating party has answered. +- 3) Disconnect indication received from terminating party, or received from originating party via the originating BCSM. +- 4) For a TDP, call gapping or service filtering are not in effect. +- 5) DP criteria have been met. +- 6) For a TDP-R or a TDP-N, there is no existing control relationship. +- 7) For an EDP, there is an existing control relationship and the EDP T\_Disconnect is armed. + +SSF Postconditions: + +- 1) For a TDP-R, basic call processing has been suspended at T\_Disconnect DP, and a control relationship has been established. +- 2) For a TDP-N, call processing proceeds to the T\_Null & Authorize Termination Attempt PIC, and no control relationship has been established. +- 3) For an EDP, as for EventReportBCSM procedure (see 3.3.22.2.1). + +### 3.3.51.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### 3.3.51.3 Responding Entity (SCF) + +#### 3.3.51.3.1 Normal procedure + +SCF Preconditions (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +#### 3.3.51.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP service which are used for reporting operation errors are described in 3.4. + +### 3.3.52 TermAttemptAuthorized procedure + +#### 3.3.52.1 General description + +This operation is sent from the SSF to the SCF at the TermAttemptAuthorized DP, after detecting a valid trigger condition, or to report an event requested by RequestReportBCSMEEvent. + +##### 3.3.52.1.1 Parameters + +- dPSpecificCommonParameters: +- calledPartyBusinessGroupID: +See Recommendation Q.1290. +- calledPartySubaddress: +See Recommendation Q.931. +- callingPartyBusinessGroupID: +See Recommendation Q.1290. +- originalCalledPartyID: +See Q.762 Original Called Number signalling information. + +- redirectingPartyID: +Contains the directory number of the last redirecting party. +- redirectionInformation: +See Q.763 Redirection Information signalling information. +- routeList: +routeList represents the list of routes which would have been used in order to route the call. The network operators can specify that this IE should be used if their particular network has the information available. +- travellingClassMark: +See Recommendation Q.1290. + +### 3.3.52.2 Invoking Entity (SSF) + +#### 3.3.52.2.1 Normal procedure + +SSF Preconditions: + +- 1) Incoming call received. +- 2) Authority to route the call to specified terminating resources verified. +- 3) Call gapping or service filtering are not in effect. +- 4) TDP criteria have been met. +- 5) For a TDP-R there is no existing control relationship. + +SSF Postconditions: + +- 1) For a TDP-R, basic call processing has been suspended at Term\_Attempt\_Authorized DP, and a control relationship has been established. +- 2) For a TDP-N, basic call processing proceeds at PIC Select\_Facility&Present Call, and no control relationship has been established. + +#### 3.3.52.2.2 Error handling + +If the destination SCF is not accessible, then the call is given final treatment (other treatments are for further study). If the calling party abandons after the sending of the TermAttemptAuthorized operation, then the SSF aborts the control relationship after the first answer message from the SCF has been received: the Transaction ID is held open until $T_{\text{SSF}}$ expires. + +Generic error handling for the operation related errors is described in 3.2 the TCAP services which are used for reporting operation errors are described in 3.4. + +### 3.3.52.3 Responding Entity (SCF) + +#### 3.3.52.3.1 Normal procedure + +SCF Preconditions: + +- 1) For TDP, none. +- 2) EDP case does not apply. + +SCF Postconditions: + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, an SSF instruction is being prepared. + +On receipt of the TermAttemptAuthorized operation, the SCSM moves from "Idle" state to the state "Preparing SSF Instructions". A control relationship to the related SSF is created. A Service Logic Program Instance (SLPI) is invoked for processing the TermAttemptAuthorized operation. By means of this control relationship, the SCF may influence the Basic Call Processing in accordance with the service logic invoked. The actions to be performed in the SLPI depend on the parameters conveyed via this operation and the SLPI (i.e. the requested IN service itself). + +### **3.3.52.3.2 Error handling** + +If the TermAttemptAuthorized operation is rejected, then the SCSM remains in the same state. The maintenance function is informed and no SLPI is invoked. Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +### **3.3.53 TNoAnswer procedure** + +#### **3.3.53.1 General description** + +This operation is sent from the SSF to the SCF after detecting a valid trigger condition at the T\_No\_Answer DP, or to report an event requested by RequestReportBCSMEvent. + +This operation requests the SSF-CCF to send a T\_No\_Answer TDP-Request message when it encounters a T\_No\_Answer trigger. + +#### **3.3.53.1.1 Parameters** + +- dPSpecificCommonParameters: +- calledPartyBusinessGroupID: +See Recommendation Q.1290. +- calledPartySubaddress: +See Recommendation Q.931. +- calledFacilityGroup: +See Recommendation Q.1290. +- calledFacilityGroupMember: +See Recommendation Q.1290. +- originalCalledPartyID: +See Q.762 Original Called Number signalling information. +- redirectingPartyID: +Contains the directory number of the last redirecting party. +- redirectionInformation: +See Q.763 Redirection Information signalling information. +- travelingClassMark: +See Recommendation Q.1290. + +#### **3.3.53.2 Invoking Entity (SSF)** + +##### **3.3.53.2.1 Normal procedure** + +SSF Preconditions (TDP): + +- 1) Incoming call has been received. +- 2) The terminating party has not answered within a specified time period. +- 3) Call gapping or service filtering are not in effect. +- 4) DP criteria have been met. +- 5) For a TDP-R, there is no existing control relationship. + +SSF Preconditions (EDP): + +- 1) For an EDP-R, there is an existing control relationship and the T\_No\_Answer EDP is armed. +- 2) For an EDP-N, there is an existing control or monitoring relationship and the T\_No\_Answer EDP is armed. + +SSF Postconditions (TDP): + +- 1) For a TDP-R, basic call processing has been suspended at T\_No\_Answer DP, and a control relationship has been established. +- 2) For a TDP-N, default exception handling has been provided, and no control relationship has been established. + +SSF Postconditions (EDP): + +- 1) The SSF-FSM stays in the state "Monitoring" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested. +- 2) The SSF-FSM moves to the state "idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested. +- 3) The SSF-FSM moves to the state "Waiting for Instructions" if the message type was request. Call processing is interrupted. + +#### 3.3.53.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +#### 3.3.53.3 Responding Entity (SCF) + +##### 3.3.53.3.1 Normal procedure + +SCF Preconditions (TDP): + +- None. + +SCF Preconditions (EDP): + +- 1) For an EDP-R at the SSF, an existing control relationship is in place and an SLPI is running. +- 2) For an EDP-N, an existing monitoring relationship is in place and an SLPI is running. + +SCF Postconditions (TDP): + +- 1) An SLPI has been invoked. +- 2) For a TDP-R, a control relationship is established, and an SLPI has been invoked. +- 3) For a TDP-R, an SSF instruction is being prepared. +- 4) For a TDP-N, no relationship is established. An SLPI has been invoked, executes and terminates. + +SCF Postconditions (EDP): + +- 1) For an EDP, the SCSM-FSM stays in the substate "Waiting for Notification or Request" if the message type was notification and there are still EDPs armed or a "CallInformationReport" or "ApplyChargingReport" requested; or +the SCSM-FSM moves to the state "Idle" if the message type was notification and there are no more EDPs armed, no "CallInformationReport" or "ApplyChargingReport" are requested; or +the SCSM-FSM moves to the state "Preparing SSF Instructions" if the message type was request. + +#### 3.3.53.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services which are used for reporting operation errors are described in 3.4. + +#### 3.3.54 Unbind procedure + +##### 3.3.54.1 General description + +The X.500 'Unbind' operation is used by the SDF to end an authenticated association between an SCF and an SDF on behalf of the end user. For a full description of the Unbind operation, see 8.2/X.511. + +##### 3.3.54.1.1 Parameters + +None. + +### **3.3.54.2 Invoking Entity (SCF)** + +#### **3.3.54.2.1 Normal procedure** + +SCF Preconditions: + +- SCSM: "SDF Bound". + +SCF Postconditions: + +- SCSM: "Idle". + +The SCSM has previously initiated a successful Bind operation to the SDF directory. It is in state "SDF Bound". The service logic determines that the authenticated access to the SDF is to be terminated. It issues an Unbind operation [(e8) Unbind\_request] that causes the SCSM to transit back to the state "Idle". + +#### **3.3.54.2.2 Error handling** + +The 'Unbind' operation does not have operation related errors. + +### **3.3.54.3 Responding Entity (SDF)** + +#### **3.3.54.3.1 Normal procedure** + +SDF Preconditions: + +- SDSM: "SCF Bound". + +SDF Postconditions: + +- SDSM: "Idle". + +A Bind operation was previously issued and the SDSM is in State "SCF Bound" waiting for a request from the SCF and/or performing an operation. The reception of the Unbind operation causes a transition to State "Idle" with the transition (E5) Unbind\_from\_SCF. + +#### **3.3.54.3.2 Error handling** + +The 'Unbind' operation does not have operation related errors. + +### **3.3.55 RequestEveryStatusChangeReport procedure** + +#### **3.3.55.1 General description** + +This operation is used to request the SSF start to monitor every change of the busy/idle status of a particular termination. + +##### **3.3.55.1.1 Parameters** + +- resourceID: + +This parameter indicates that physical termination resource which is requested by the SCF to be monitored by the SSF. This parameter is one of the lineID, facilityGroupID, facilityGroupMemberID, or trunkGroupID. + +- correlationID: + +This parameter is used by the SCF to associate the "StatusReport" from the SSF with the request in the SCF. + +- monitorDuration: + +This parameter indicates the maximum time duration for monitoring in the SSF. + +### **3.3.55.2 Invoking Entity (SCF)** + +#### **3.3.55.2.1 Normal procedure** + +SCF Preconditions: + +- 1) The SLPI has been determined that a "Request Every Status Change Report" operation has to be sent. +- 2) The SCME is in the state "Status Report Idle". + +SCF Postcondition: + +- The SCME is in the state "Waiting for SSF Response Status Report". + +When the SPLI requests to monitor every change of the busy/idle status of a physical termination resource, the SCF sends "Request Every Status Change Report" operation to the SSF to monitor every change of the status of a particular termination resource. Then the SCME is moved to the state "Waiting for SSF Resource Status Report" from the state "Status Report Idle". After this, in the case that the SCF receives ReturnResult of this operation, the SCME remains in same state. When the SCF receives ReturnError of this operation, the SCME is returned to the state "Status Report Idle". + +When the SCF receives a Status Report operation from the SSF, the SCME remains in the state "Waiting for SSF Resource Status Report". Alternatively when the SCF receives a "Status Report" operation with the monitorCondition parameter set to "timerExpired" or "cancelled" from SSF, the SCME is returned to the state "Status Report Idle". + +Clarification on the use of this operation within or outside the context of a call is for further study. + +### 3.3.55.2.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +### 3.3.55.3 Responding Entity (SSF) + +#### 3.3.55.3.1 Normal procedure + +SSF Precondition: + +- The SSME is in one of the following states: +state ma: "IdleManagement"; +state mb: "Non-Call Associated Treatment". + +SSF Postcondition: + +- The SSME is in one of the following states: +state ma: "IdleManagement"; +state mb: "Non-Call Associated Treatment". + +On receipt of this operation, the SSF starts to monitor every change of the busy/idle status of a particular termination resource. If an error is occurred (e.g. the SSF can not find the specific termination resource), then the SSF sends ReturnError of this operation with proper error type to the SCF. + +The SSF continuously monitors every change of the busy/idle status of a particular termination resource until a timer which is specified by monitorDuration parameter expires. Whenever the SSF finds a change of status, the SSF sends the "Status Report" Operation to the SCF with monitorCondition parameter set to "statusReport". After sending this operation, the SSF should remain in the "Non-Call Associated Treatment" state. If timer expiration occurs, the SSF sends the "StatusReport" Operation to the SCF with monitorCondition parameter set to "timerExpired". Alternatively, when the SSF receives a "Cancel Status Report" operation from the SCF, the SSF sends the "Status Report" Operation to the SCF with monitorCondition parameter set to "Cancelled". After the SSF sends this operation, the SSME should move to the state "IdleManagement" unless there are other processes of Non-Call Associated operation, in which case the SSF should remain in the state "Non-Call AssociatedTreatment". + +#### 3.3.55.3.2 Error handling + +Generic error handling for the operation related errors is described in 3.2 and the TCAP services used for reporting operation errors are described in 3.4. + +## 3.4 Services assumed from TCAP + +This subclause describes the procedures and TCAP primitives that shall be used for transmitting messages between SSF, SCF and SRF. For the SCF-SDF interface, refer to 2.2.2.2. + +### 3.4.1 Normal procedures + +This subclause describes the procedures and TCAP primitives that shall be used for transmitting messages between SSF, SCF and SRF under normal operation. + +The INAP, as TC-user, uses only the structured dialogue facility provided by TCAP. The following situations can occur when a message is sent between two physical entities: + +- a) A dialogue shall be established – The TC-user issues a TC-BEGIN request primitive. +- b) A dialogue shall be maintained – The TC-user issues a TC-CONTINUE request primitive. +- c) A dialogue shall no longer be maintained – The TC-user issues a TC-END request primitive with either basic end or with pre-arranged end depending on the following conditions: + - i) Basic End + - In the case the dialogue is established, operations, leading to a termination of the relationship, can be transmitted by the FE with a TC-END request primitive (basic) in case the FE is not interested in the reception of any ERROR or REJECT components for these sent operations. Once the FE dialogue resources have been released, any ERROR or REJECT components received for these operations will be discarded by TC as described in Recommendation Q.774. + - In the case the dialogue is established and the FE has received an operation, leading to the termination of the relationship does not interest to continue dialogue and there is no operation to be sent, a TC-END request primitive (basic) with zero components can be sent from the FE. + - ii) Pre-arranged End: + - In the case, an entity is interested in possible ERROR or REJECT messages on response to sent operations leading to a termination of the relationship, the dialogue is ended with a TC-END request primitive (pre-arranged end) after the last associated operation timer expires. The receiving entity can end the dialogue with a TC-END request primitive (pre-arranged end) after successful processing of these operations (i.e. the relationship is terminated). +- d) In general, the use of pre-arranged end shall be limited to the case for both communicating entities clearly recognizable that peer entity applies pre-arranged end. In all other cases, basic end shall be used. +- e) A dialogue shall not be established – For class 2 or 4 operations only the sending TC-user issues a TC-BEGIN request primitive and ends the dialogue locally after operation time out by means of a pre-arranged end. Upon reception of the TC-BEGIN indication primitive the receiving TC-user shall end the dialogue locally. + +#### 3.4.1.1 SSF-to-SCF messages + +##### 3.4.1.1.1 SSF-FSM related messages + +A dialogue shall be established when the SSF-FSM moves from the state **Idle** to the state **Waiting for Instructions**. The relevant INAP operation, which can be the InitialDP operation or one of DP specific operations for TDP-R, shall be transmitted in the same message. + +No dialogue shall be established when the SSF-FSM moves from the state **Idle** and back to the state **Idle** on the detection of TDP-N. The relevant INAP operation, which can be the InitialDP operation or one of DP specific operations for TDP-N, shall be sent with a TC-BEGIN request primitive and the dialogue is locally ended by means of TC-END request primitive with pre-arranged end. + +For all other operations sent from the SSF-FSM, the dialogue shall be maintained except for the following cases. + +When the SSF-FSM makes a non-error case state transition to the state **Idle** and there is one or more pending operation and TCAP dialogue is established, TCAP dialogue can be terminated by TC-END primitive with component(s). When the SSF sends the last EventReportBCSM, ApplyChargingReport or CallInformationReport, the dialogue may be ended from the SSF by a TC-END request primitive with basic end. + +In the case that there is no pending operation and TCAP dialogue is established, TCAP dialogue can be terminated by TC-END primitive with zero component or pre-arranged end. When the SSF-FSM makes a non-error case state transition to the state **Idle** and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components, or the dialogue is locally ended by means of a TC-END request primitive with pre-arranged end. + +The SSF can end a dialogue with a TC-END request primitive with zero component or pre-arranged end depending on that TCAP dialogue is established or not, in the case call release is initiated by any other entity, then the SCF and the SSF has no pending call information requests (or pending requests which should be treated in the same way, see Note 1 of 3.1.1.5) nor any armed EDP to notify the SCF of the call release (for alternative way, see 3.4.2.2). + +When the SSF has sent the last EventReportBCSM, ApplyChargingReport or CallInformationReport, the dialogue may be ended from the SCF by a TC-END request primitive with basic end. + +#### 3.4.1.1.2 Assisting/Handoff SSF-FSM related messages + +A dialogue shall be established when the Assisting/Handoff SSF-FSM moves from the state **Idle** to the state **Waiting for Instructions**. The AssistRequestInstructions operation shall be transmitted with a TC-BEGIN request primitive. + +For all other operations sent from the Assisting/Handoff SSF-FSM, the dialogue shall be maintained except for the following cases. + +When the SSF-FSM makes a non-error case state transition to the state **Idle** and there is one or more pending operation and TCAP dialogue is established, TCAP dialogue can be terminated by TC-END primitive with component(s). When the SSF sends the last ApplyChargingReport, the dialogue may be ended from the SSF by a TC-END request primitive with basic end. + +In the case that there is no pending operation and TCAP dialogue is established, TCAP dialogue can be terminated by TC-END primitive with zero component or pre-arranged end. When the SSF-FSM makes a non-error case state transition to the state **Idle** and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components, or the dialogue is locally ended by means of a TC-END request primitive with pre-arranged end. + +When the SSF has sent the last ApplyChargingReport, the dialogue may be ended from the SCF by a TC-END request primitive with basic end. + +#### 3.4.1.1.3 SSME-FSM related messages + +The following procedures shall be followed: + +- The dialogue shall be maintained when the ActivityTest Return Result is sent. +- No dialogue shall be established when the ServiceFilteringResponse operation is sent. The operation is sent with a TC-BEGIN request primitive and the dialogue is ended by means of a TC-END request primitive with pre-arranged end. +- A dialogue shall no longer be maintained when the Return Result of the ActivateServiceFiltering operation is sent. The dialogue is ended by means of a TC-END request primitive with basic end, the Return Result is transmitted with the same request. +- The dialogue is locally terminated by means of a TC-END request primitive with pre-arranged end, upon reception of a TC-BEGIN indication primitive with a CallGap operation. +- The dialogue shall be maintained when the RequestCurrentStatusReport, RequestEveryStatusChangeReport or RequestFirstStatusMatchReport operation is received inside the call context. + +- The dialogue shall be maintained on sending following operations inside the call context if the operations are not final one: + - Return Result of the RequestCurrentStatusReport operation; + - Return Result of the RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation; and + - StatusReport operation in reply to RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation. +- The dialogue shall no longer be maintained on sending following operations inside the call context if the operations are final one: + - Return Result of the RequestCurrentStatusReport operation; + - Return Result of the RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation; and + - StatusReport operation in reply to RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation. + +The dialogue is ended from the SSF by means of TC-END request primitive with basic end, one of the above operations is transmitted with the same request. + +If monitor duration expires for RequestFirstStatusMatchReport or RequestEveryStatusChangeReport which has been received inside the call context and there is no need to maintain dialogue, the dialogue is ended from the SSF by means of a TC-END request primitive (basic) with zero component. + +- The dialogue shall be established when the RequestCurrentStatusReport, RequestEveryStatusChangeReport or RequestFirstStatusMatchReport operation is received outside the call context. +- The dialogue shall no longer be maintained when the Return Result of the RequestCurrentStatusReport operation is sent outside the call context. The dialogue is ended from the SSF by means of a TC-END request primitive with basic end, the Return Result is transmitted with the same request. +- The dialogue shall be maintained when the Return Result of the RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation is sent outside the call context. +- The dialogue shall no longer be maintained when the StatusReport operation is sent in reply to the RequestFirstStatusMatchReport operation outside the call context. The dialogue is ended from the SSF by means of a TC-END request primitive with basic end, the StatusReport operation is transmitted with the same request. +- The dialogue shall be maintained when the StatusReport operation is sent in reply to the RequestEveryStatusChangeReport operation outside the call context. +- The dialogue shall no longer be maintained when the monitor duration expires for RequestFirstStatusMatchReport or RequestEveryStatusChangeReport which has been received outside the call context. The dialogue is ended from the SSF by means of a TC-END request primitive (basic) with zero component. + +### 3.4.1.2 SCF-to-SSF messages + +#### 3.4.1.2.1 SCSM-FSM related messages + +No dialogue shall be established when the SCSM-FSM moves from state **Idle** to state **Idle** upon receipt of InitialDP operation or one of DP specific operations for TDP-N. The operation is received with a TC-BEGIN indication primitive and the dialogue is locally terminated by means of a TC-END request primitive with pre-arranged end. + +A dialogue shall be established when the SCSM-FSM moves from state **Idle** to state **Preparing SSF Instructions** upon the receipt of InitialDP operation for TDP-R, one of DP specific operations for TDP-R or AssistRequestInstructions operation. + +A dialogue shall be established when the SCSM-FSM moves from state **Idle** to state **Preparing SSF Instructions** on sending an InitiateCallAttempt operation to the SSF. + +For subsequent operations sent from the SCSM-FSM, the dialogue shall be maintained except for the following cases, i.e. all other operations are sent after a dialogue was established from the SSF (the SCF has previously received a TC-BEGIN indication primitive with an InitialDP operation, one of DP specific operations or an AssistRequestInstructions operation). + +The dialogue shall no longer be maintained when the pre-arranged end condition is met in the SCF. When the SCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with pre-arranged end. Alternatively, the sending of operations, leading to the termination of the relationship, by means of a TC-END request primitive (basic end) is possible. + +#### 3.4.1.2.2 SCME-FSM related messages + +The operations sent from the SCME-FSM shall be issued according to the following procedures: + +- The dialogue shall be maintained when the ActivityTest operation is sent. +- A dialogue shall not be established when a CallGap operation is sent without using a SCSM associated dialogue. The operation is sent using a TC-BEGIN request primitive and the dialogue is terminated with a pre-arranged end. +- For sending one or more CallGap operations, the SCME-FSM may use an existing SCSM-FSM associated dialogue which was initiated by a SSF-FSM (i.e. established for the transmission of the InitialDP operation or one of DP specific operations). The dialogue shall be maintained and the CallGap operation(s) shall be sent with the first response of the SCSM-FSM to the InitialDP operation or one of DP specific operations. +- A dialogue shall be established when an ActivateServiceFiltering operation is sent. The operation shall be transmitted with a TC-BEGIN request primitive. +- The dialogue is locally terminated upon reception of a ServiceFilteringResponse operation using a TC-END request primitive with pre-arranged end. +- The dialogue shall be maintained when the RequestCurrentStatusReport, RequestEveryStatusChangeReport or RequestFirstStatusMatchReport operation is sent inside the call context. +- The dialogue shall be maintained on receiving following operations inside the call context if the operations are not the final ones: + - Return Result of the RequestCurrentStatusReport operation; + - Return Result of the RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation; and + - StatusReport operation in reply to RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation. +- The dialogue shall no longer be maintained on receiving following operations inside the call context if the operations are the final ones: + - Return Result of the RequestCurrentStatusReport operation; + - Return Result of the RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation; and + - StatusReport operation in reply to RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation. + +The dialogue is ended from the SSF by means of TC-END indication primitive with basic end, one of above operations is transmitted with the same request. + +If monitor duration expires for RequestFirstStatusMatchReport or RequestEveryStatusChangeReport which has been received inside the call context and there is no needs to maintain dialogue, the dialogue is ended from the SSF by means of a TC-END indication primitive (basic) with zero component. + +- The dialogue shall be established when the RequestCurrentStatusReport, RequestEveryStatusChangeReport or RequestFirstStatusMatchReport operation is sent outside the call context. +- The dialogue shall no longer be maintained when the Return Result of the RequestCurrentStatusReport operation is received outside the call context. The dialogue is ended from the SSF by means of a TC-END indication primitive with basic end, the Return Result is transmitted with the same indication. +- The dialogue shall be maintained when the Return Result of the RequestFirstStatusMatchReport or RequestEveryStatusChangeReport operation is received outside the call context. +- The dialogue shall no longer be maintained when the StatusReport operation is received in reply to the RequestFirstStatusMatchReport operation outside the call context. The dialogue is ended from the SSF by means of a TC-END indication primitive with basic end, the StatusReport operation is received with the same indication. +- The dialogue shall be maintained when the StatusReport operation is received in reply to the RequestEveryStatusChangeReport operation outside the call context. +- The dialogue shall no longer be maintained when the monitor duration expires for RequestFirstStatusMatchReport or RequestEveryStatusChangeReport outside the call context. The dialogue is ended from the SSF by means of a TC-END indication primitive (basic) with zero component. + +### 3.4.1.3 SCF-to/from-SRF messages + +A dialogue is established when the SRF sends an AssistRequestInstructions operation to the SCF. For all other operations sent to/from the SRF, the dialogue shall be maintained. + +In the case that there is no pending operation and TCAP dialogue is established, TCAP dialogue can be terminated by TC-END primitive with zero component. When the SCSM makes a non-error case state transition to end user interaction and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components. + +The dialogue shall no longer be maintained when sending the SRReport operation for PlayAnnouncement with disconnection from the SRF set to TRUE or Return Result of the PromptAndCollectUserInfo with disconnection from the SRF set to TRUE. The dialogue is ended by means of a TC-END request primitive with basic end, and one of the above operations is transmitted with the same request. + +Regardless of whether pending operation exists or not, when the SRSM-FSM is informed of the disconnection of bearer connection (in the case of SCF initiated disconnection or call abandon from call party) and dialogue is established, the dialogue is ended by means of a TC-END request primitive (basic) with zero components or TC-END request primitive (pre-arranged end). + +The dialogue shall no longer be maintained when the pre-arranged end condition is met in the SRF. When the SRSM-FSM is informed the disconnection of bearer connection and TCAP dialogue is not established, TCAP dialogue is locally terminated by TC-END primitive with pre-arranged end. + +When the SCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with pre-arranged end. Alternatively, the sending of operations, leading to the termination of the relationship, by means of a TC-END request primitive (basic end) is possible. + +In the relay case, the SRF-SCF relationship uses the SSF-SCF TCAP dialogue. This is possible, because begin and end of the SRF-SCF relationship are embedded in the SSF-SCF relationship. SRF-SCF information shall be exchanged with TC-CONTINUE request primitives. + +In the case of the SSF relay, it is for further study how to map messages to ROSE capability of bearer signalling system between the SSF and the SRF, and what services are assumed from ROSE. + +### 3.4.2 Abnormal procedures + +This subclause describes the procedures and TCAP primitives that shall be used for reporting abnormal situations between SSF, SCF and SRF. The error cases are defined in 3.2. + +The following primitives shall be used to report abnormal situations: + +- operation errors, as defined in the INAP, are reported with TC-U-ERROR request primitive; +- rejection of a TCAP component by the TC-user shall be reported with TC-U-REJECT request primitive; +- when the FE detecting error or rejecting operation decides the termination of TC dialogue, TC-END request primitive (basic) with error or reject can be used for the termination of TC dialogue; +- when the SSF or the SRF detecting error or rejecting operation recognizes the possibility to continue dialogue, TC-CONTINUE request primitive with error or reject can be used for the continuation of TC dialogue; +- a dialogue shall be aborted by the TC-user with a TC-U-ABORT request primitive; +- on expiration of application timer $T_{\text{SSF}}$ or $T_{\text{SRF}}$ , dialogue shall be terminated by means of a TC-U-ABORT primitive with an Abort reason, regardless of TCAP dialogue is established or not. + +For abnormal situations detected by TCAP the same rules shall apply for reception of TC-R-REJECT indication as for transmission of TC-U-REJECT request and for transmission of TC-P-ABORT indication as for transmission of TC-U-ABORT request primitive. + +The following rules shall be applied to terminate the TCAP dialogue under abnormal situations: + +- in the case that abort condition is detected and TCAP dialogue is established, TCAP dialogue is terminated by TC-U-ABORT primitive with an Abort reason; +- in the case that abort condition is detected and TCAP dialogue is not established, TCAP dialogue is locally terminated by TC-U-ABORT primitive (in the case such as application time out). + +In error situations pre-arranged end shall not be used to terminate the TCAP dialogue. In case any application entity encounters an error situation, the peer entity shall be explicitly notified of the error, if possible. If from any entity's point of view the error encountered requires the relationship to be ended, it shall close the dialogue via a TC-END request primitive with basic end or via a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +In case an entity receives a TC-END indication primitive and after all components have been considered, the FSM is not in a state to terminate the relationship, an appropriate internal error should be provided. + +In cases when a dialogue needs to be closed by the initiating entity before its establishment has been completed (before the first TC indication primitive to the TC-BEGIN request primitive has been received from the responding entity), the TC-user shall issue a TC-END request primitive with pre-arranged end or a TC-U-ABORT request primitive. The result of these primitives will be only local, any subsequent TC indication received for this dialogue will be handled according to the abnormal procedures as specified in Recommendation Q.774. + +### 3.4.2.1 SCF-to-SSF/SRF messages + +Considering that both SSF and SRF do not have the logic to recover from error cases detected on the SCF-SSF/SRF interface, the following shall apply: + +- Operation errors and rejection of TCAP components shall be transmitted to the SSF and, respectively, the SRF with a TC-END request primitive, basic end. + +If, in violation of the above procedure, an ERROR or REJECT component is received with a TC-CONTINUE indication primitive, the SSF and, respectively, the SRF shall abort the dialogue with a TC-U-ABORT request primitive. + +In the case of the SSF relay, it is for further study how to map messages to ROSE capability of bearer signalling system between the SSF and the SRF, and what services are assumed from ROSE. + +### 3.4.2.2 SSF/SRF-to-SCF messages + +Operation errors and rejection of TCAP components shall be transmitted to the SCF according to the following rules: + +- The dialogue shall be maintained when the preceding message, which contained the erroneous component, indicated that the dialogue shall be maintained, i.e. the error or reject shall be transmitted with a TC-CONTINUE request primitive if the erroneous component was received with a TC-CONTINUE indication primitive. +- On receipt of an ERROR or REJECT component the SCF decides on further processing. It may either continue, explicitly end or abort the dialogue. +- In all other situations the dialogue shall no longer be maintained, i.e. the error or reject shall be transmitted with a TC-END request primitive, basic end, if the erroneous component was received with a TC-BEGIN indication primitive. +- On expiration of application timer $T_{\text{SSF}}$ or $T_{\text{SRF}}$ , dialogue shall be terminated by means of a TC-U-ABORT primitive with an Abort reason, regardless of whether TCAP dialogue is established or not. + +If the error processing in the SSF-SRF leads to the case where the SSF-SRF is not able to process further SCF operations while the dialogue is to be maintained, the SSF-SRF aborts the dialogue with a TC-END request primitive with basic end or a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +The SSF can end a dialogue with a TC-U-ABORT request primitive in case call release is initiated by any other entity, then the SCF and the SSF has no pending call information requests (or pending requests which should be treated in the same way, i.e. ApplyCharging nor any armed EDP to notify the SCF of the call release (for alternative way, see 3.4.1.1.1)). + +In the case of the SSF relay, it is for further study how to map messages to ROSE capability of bearer signalling system between the SSF and the SRF, and what services are assumed from ROSE. + +### 3.4.3 Dialogue establishment + +The establishment of an INAP dialogue involves two application processes as described in 0.4, one that is the dialogue-initiator and one that is the dialogue-responder. + +Application context negotiation may not be supported in all physical entities and/or all networks. + +This procedure is driven by the following signals: + +- A TC-BEGIN request primitive from the dialogue-initiator. +- A TC-BEGIN indication primitive occurring at the responding side. +- The first TC-CONTINUE indication primitive occurring at the initiating side or under specific conditions: + - A TC-END indication primitive occurring at the initiating side. + - A TC-U-ABORT indication primitive occurring at the initiating side. + - A TC-P-ABORT indication primitive occurring at the initiating side. + +#### 3.4.3.1 Sending of a TC-BEGIN request primitive + +Before issuing a TC-BEGIN request primitive, SACF shall store the AC-name and if present the user-information parameter. + +SACF shall request the invocation of the associated operations using the TC-INVOKE service. See 3.4.8 for a description of the invocation procedure. + +After processing of the last invocation request, SACF shall issue a TC-BEGIN request primitive. + +The initiator SACF then waits for a TC indication primitive and will not issue any other requests, except a TC-U-ABORT request or a TC-END request with the release method parameter set to "pre-arranged release". + +If no TC indication primitive is expected because no dialogue is to be established according to the rules as stated in 3.4.1 and 3.4.2, SACF will wait for the last associated TCAP operation timer to expire and issue a TC-END request with the release method parameter set to "pre-arranged release". + +### **3.4.3.2 Receipt of a TC-BEGIN indication** + +On receipt of a TC-BEGIN indication primitive, responder SACF shall: + +- Analyse the application-context-name if included in the primitive. If it is supported, process any other indication primitives received from TC as described in 3.4.8. +- If no dialogue is to be established according to the rules as stated in 3.4.1 and 3.4.2, SACF will wait for the last indication primitive from TC and issue a TC-END request with the release method parameter set to "pre-arranged release". +- If the application-context-name included in the primitive is not supported, issue a TC-U-ABORT request primitive. If an alternative application-context can be offered its name is included in the TC-U-ABORT request primitive. + +It is for further study whether or not the application-context-negotiation is limited only for using the TC-U ABORT primitive. + +### **3.4.3.3 Receipt of the first TC-CONTINUE ind** + +On receipt of the first TC-CONTINUE indication primitive for a dialogue, SACF shall check the value of the application-context-name parameter. If this value matches the one used in the TC-BEGIN request primitive, SACF shall process the following TC component handling indication primitives as described in 3.4.8, otherwise it shall issue a TC-U-ABORT request primitive. + +It is for further study whether or not the application-context-negotiation is limited only for using the TC-U ABORT primitive. + +### **3.4.3.4 Receipt of a TC-END ind** + +On receipt of a TC-END indication primitive in the dialogue initiated state, SACF shall check the value of the application-context-name parameter. If this value matches the one used in the TC-BEGIN request primitive, then the SACF shall process the following TC component handling indication primitives as described in 3.4.8. + +### **3.4.3.5 Receipt of a TC-U-ABORT ind** + +Receipt of a TC-U-ABORT indication primitive is described as part of user abort procedure (see 3.4.6.2). If the abort reason is application context name not supported, the responding side may propose an alternative application-context-name in the TC-U-ABORT indication. If an alternative application-context is proposed, the receiving entity shall check this name and if it can be supported a new dialogue may be established. + +### **3.4.3.6 Receipt of a TC-P-ABORT ind** + +Receipt of a TC-P-ABORT indication primitive is described as part of provider abort procedure (see 3.4.7.1). + +## **3.4.4 Dialogue continuation** + +Once established the dialogue is said to be in a continuation phase. + +Both application processes can request the transfer of INAP APDUs until one of them requests the termination of the dialogue. + +### **3.4.4.1 Sending entity** + +SACF shall process any component handling request primitives as described in 3.4.8. + +After processing the last component handling request primitive, SACF shall issue a TC-CONTINUE request primitive. + +#### **3.4.4.2 Receiving entity** + +On receipt of a TC-CONTINUE indication primitive SACF shall accept zero, one or several TC component handling indication primitives and process them as described in 3.4.8. + +#### **3.4.5 Dialogue termination** + +Both the dialogue-initiator and the dialogue-responder have the ability to request the termination of a dialogue after it has been established when no dialogue is to be established or when a dialogue is no longer to be maintained according to the rules as stated in 3.4.1 and 3.4.2. + +The dialogue termination procedure is driven by the following events: + +- A TC-END request primitive. +- A TC-END indication primitive. + +##### **3.4.5.1 Sending of TC-END request** + +When the dialogue shall no longer be maintained, SACF shall process any component handling request primitives as described in 3.4.8 + +After processing the last component handling request primitive (if any), SACF shall issue a TC-END request primitive with the release method parameter set to "basic end" or "pre-arranged release", according to the rules as stated in 3.4.1 and 3.4.2. + +When no dialogue is to be established, refer to 3.4.3.1 and 3.4.3.2. + +##### **3.4.5.2 Receipt of a TC-END indication** + +On receipt of a TC-END indication primitive, the SACF shall accept any component handling indication primitives and process them as described in 3.4.8. + +After processing the last component handling primitive all dialogue related resources are released. + +#### **3.4.6 User Abort** + +Both the dialogue-initiator and the dialogue-responder have the ability to abort a dialogue at any time. + +The user abort procedure is driven by one of the following events: + +- A TC-U-ABORT request primitive. +- A TC-U-ABORT indication primitive. + +##### **3.4.6.1 Sending of TC-U-ABORT request** + +After issuing a TC-U-ABORT request primitive, all dialogue related resources are released. + +##### **3.4.6.2 Receipt of a TC-U-ABORT indication** + +On receipt of a TC-U-ABORT indication all dialogue related resources are released. + +#### **3.4.7 Provider Abort** + +TC has the ability to abort a dialogue at both the dialogue-initiator side and the dialogue-responder side. + +The provider abort procedure is driven by the following event: + +- A TC-P-ABORT indication primitive. + +##### **3.4.7.1 Receipt of a TC-P-ABORT indication** + +On receipt of a TC-P-ABORT indication, all dialogue related resources are released. + +### **3.4.8 Procedures for INAP operations** + +This subclause describes the procedures for INAP operations. + +#### **3.4.8.1 Operation invocation** + +SACF shall build an operation argument from the parameters received and request the invocation of the associated operation using the TC-INVVOKE procedure. If a linked ID parameter is inserted in the primitive, this indicates a child operation and implies that the operation is linked to a parent operation. + +#### **3.4.8.2 Operation invocation receipt** + +On receipt of a TC-INVVOKE indication primitive, SACF shall: + +- If the operation code does not correspond to an operation supported by the application-context, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized operation). +- If a linked ID is included, perform the following checks: if the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to a permitted linked operation, or if the parent operation invocation is not active, issue a TC-U-REJECT request primitive with the appropriate problem code (linked response unexpected or unexpected linked operation). +- If the type of the argument is not the one defined for the operation, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter). +- If the operation cannot be invoked because the INAP related dialogue is about to be released, requests the transfer of the reject component using the TC-U-REJECT request primitive with the problem code (Initiating Release). +- If sufficient INAP related resources are not available to perform the requested operation, request the transfer of a reject component using the TC-U-REJECT request primitive with the problem code (Resource Limitation). +- Otherwise, accept the TC-INVVOKE indication primitive. If the operation is to be user confirmed, SACF waits for the corresponding response. + +#### **3.4.8.3 Operation Response** + +For user confirmed operations, SACF shall: + +- If no error indication is included in the response to a class 1 or 3 operation, construct a result information element from the parameters received and request its transfer using the TC-RESULT-L service. +- If an error indication is included in the response to a class 1 or 2 operation, construct an error parameter from the parameters received and request its transfer using the TC-U-ERROR request primitive. + +#### **3.4.8.4 Receipt of a response** + +##### **3.4.8.4.1 Receipt of TC-RESULT-NL indication** + +On receipt of a TC-RESULT-NL indication, SACF shall: + +- Request the transfer of a reject component using the TC-U-REJECT request primitive with the appropriate problem code (mistyped parameter). + +##### **3.4.8.4.2 Receipt of TC-RESULT-L indication** + +On receipt of a TC-RESULT-L indication, SACF shall: + +- If the type of the result parameter is not the one defined for the result of this operation, request the transfer of a reject component using the TC-U-REJECT request primitive with the appropriate problem code (mistyped parameter). +- Otherwise, accept the TC-RESULT-L indication primitive. + +#### **3.4.8.4.3 Receipt of TC-U-ERROR indication** + +On receipt of a TC-U-ERROR indication, SACF shall: + +- If the error code is not defined for the SACF or is not one associated with the operation referred to by the invoke identifier, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized error or unexpected error). +- If the type of the error parameter is not the one defined for this error, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter). +- Otherwise, accept the TC-U-ERROR indication primitive. + +#### **3.4.8.4.4 Receipt of TC-U-REJECT indication** + +On receipt of a TC-U-REJECT indication primitive which affects a pending operation, SACF shall accept the TC-U-REJECT indication primitive. + +#### **3.4.8.4.5 Receipt of a TC-L-REJECT indication** + +This event occurs when the local TC detects a protocol error in an incoming component which affects an operation. + +On receipt of a TC-L-REJECT indicating "return result problem, return error unexpected", SACF shall inform the application process. + +On receipt of a TC-L-REJECT indicating "return error problem, return error unexpected", SACF shall inform the application process. + +Note that when the problem code indicates a general problem, it is considered that the event cannot be related to an active operation even if the invoke Id is provided by TC. This is because it is unclear whether the invoke Id refers to a local or remote invocation. The behaviour of SACF in such a case is described in 3.4.8.5.3. + +#### **3.4.8.4.6 Receipt of a TC-L-CANCEL indication** + +On receipt of a TC-L-CANCEL indication, the SACF shall: + +- If the associated operation is a class 1 operation, inform the application process. +- If the associated operation is a class 2 operation and no linked operations are defined for this operation, ignore the primitive. +- If the associated operation is a class 2 operation and has linked operations but none of them has been invoked, inform the application process. +- If the associated operation is a class 2 operation and a linked operation invocation has already been received in response to this operation, ignore the primitive. +- If the associated operation is a class 3 operation, inform the application process. +- If the associated operation is a class 4 operation, ignore the primitive. + +### **3.4.8.5 Other events** + +This subclause describes the behaviour of SACF on receipt of a component handling indication primitive which cannot be related to any operation or which does not affect a pending one. + +#### **3.4.8.5.1 Receipt of a TC-U-REJECT indication** + +On receipt of a TC-U-REJECT indication primitive which does not affect an active operation (i.e. indicating a return result or return error problem), it is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in 3.4.2. This is also applicable for invoke problems related to a class 4 linked operation. + +#### **3.4.8.5.2 Receipt of a TC-R-REJECT indication** + +On receipt of a TC-R-REJECT indication (i.e. when a protocol error has been detected by the peer TC entity) which does not affect an active operation, it is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in 3.4.2. + +#### **3.4.8.5.3 Receipt of a TC-L-REJECT indication** + +On receipt of a TC-L-REJECT indication primitive (i.e. when a protocol error has been detected by the local TC entity) which cannot be related to an active operation, it is up to the application process to continue, or to terminate the dialogue and implicitly trigger the transmission of the reject component or to abort the dialogue. + +#### **3.4.8.5.4 Receipt of a TC-NOTICE indication** + +This informs the SACF that a message cannot be delivered by the Network Layer, this can only occur if the Return Option has been set (see 3.4.9.1.8). It is for the application process to decide whether to terminate the dialogue or retry. + +### **3.4.9 Mapping on to TC services** + +#### **3.4.9.1 Dialogue control** + +The TC-UNI service is not used by INAP. + +##### **3.4.9.1.1 Destination address** + +This parameter is set by the dialogue initiating application process, and may optionally be modified by the responding dialogue in the first backward TC-CONTINUE, but will not be seen by initiating user. + +##### **3.4.9.1.2 Originating address** + +This parameter is set by the dialogue initiating application process. + +##### **3.4.9.1.3 Dialogue Id** + +The value of this parameter is associated with the INAP invocation in an implementation dependent manner. + +##### **3.4.9.1.4 Application-context-name** + +The application-context-name parameter is set by SACF as defined in 2.1.5 and 2.2.2.5.3. + +##### **3.4.9.1.5 User information** + +This parameter may be used by both initiating and responding application process. + +##### **3.4.9.1.6 Component present** + +This parameter is used by SACF as described in Recommendation Q.771. + +##### **3.4.9.1.7 Termination** + +The value of the release method parameter of the TC-END request primitive is set by SACF according to the rules as stated in 3.4.1 and 3.4.2. + +##### **3.4.9.1.8 Quality of Service** + +The quality of Service of TC request primitives is set by the SACF to the following value: + +- Sequencing requested. +- Return option – This parameter is set by SACF in an implementation dependent manner. + +### **3.4.9.2 Operation procedures** + +#### **3.4.9.2.1 Invoke Id** + +This parameter is set by the sending application process. + +#### **3.4.9.2.2 Linked Id** + +This parameter is set by the sending application process. + +#### **3.4.9.2.3 Dialogue Id** + +The value of this parameter is associated with the INAP invocation in an implementation dependent manner. + +#### **3.4.9.2.4 Class** + +The value of this parameter is set by SACF according to the type of the operation to be invoked according to 2.1. + +#### **3.4.9.2.5 Operation** + +The operation code of a TC-INVOKE request primitive is set by the sending application process as defined in 2.4 + +SACF shall set the operation code of the TC-RESULT-L primitive (if required) to the same value as the one received at invocation time. + +#### **3.4.9.2.6 Error** + +The error parameter of the TC-U-ERROR request primitive is set by the sending application process as defined in 2.4. + +#### **3.4.9.2.7 Parameters** + +The argument parameter of TC-INVOKE primitives is set by the sending application process as defined in 2. + +The result parameter of TC-RESULT-L primitives is set by the sending application process as defined in 2. + +The parameter of TC-U-ERROR primitives are set by the sending application process as defined in 2. + +#### **3.4.9.2.8 Time out** + +The value of this parameter is set by SACF according to the type of operation invoked. + +#### **3.4.9.2.9 Last component** + +This parameter is used by SACF as described in Recommendation Q.771. + +#### **3.4.9.2.10 Problem code** + +This parameter is used by SACF as described in 3.4.8. + +#### **3.4.9.2.11 Abort reason** + +This parameter is used by SACF, and attributes and coding are specified by network operator. + +## Annex A + +### INAP SDL Diagrams + +(This annex forms an integral part of this Recommendation) + +#### A.1 Introduction + +This annex contains SDL diagrams for the FSMs for the SSF, assisting/handoff SSF, SCF and SRF, as described in the text and Figures of 3.1.1.5, 3.1.1.6, 3.1.2 and 3.1.3, together with information from relevant detailed operation procedures. SDL diagrams for the SDF-related states of the SCF and for the SDF itself are contained in Annex B. + +Notes on the diagrams give further details where necessary. The SDL diagrams are at the same level of detail as the relevant text and figures, and do not contain anything not in the main body of this Recommendation unless specifically noted. + +The SDL used is compliant with the latest Recommendations for SDL [Recommendation Z.100 (1993)], but no symbols are used which are not contained in Recommendation Z.100 (1988). + +In the case of inconsistency between SDL diagrams and text, text shall be taken as correct. + +#### A.2 SDL diagrams + +The SDL in these diagrams is very high-level. It is incomplete in that data declarations are given only for timers and signals, but data carried by the signals is not declared. + +Names used for operations are exactly those of this Recommendation, and other locally-defined names in general relate to event names used in this Recommendation. In some cases, however, new names have been introduced for signals where this Recommendation does not provide a name. Where operation names have been split to contain them within a symbol, the SDL technique of breaking lines with an underline followed by a space is used; this combination is ignored in SDL so A\_B is the same name as AB. + +In general receipt of a signal (input) from an FE outside the FE being modelled will require some service logic processing, but the detail of such processing is not of interest to the FSM (only its results). The existence of this service logic processing has been shown by inclusion of a general procedure called Process\_Input. In other places SDL tasks are used to indicate the scope of processing required. + +It should be noted that in SDL the word "reset" applied to timers means to stop the timer, not restart it. "Set" in SDL means both start and restart a timer. + +``` +/* +SSF SDLs for INAP +Based on Q.1218, Section 3.1.1.5, "SSF State Transition Diagram". +Version 2.0 January 1995 +*/ +``` + +![](6d05c026b02a4762fcd1dcb5171327ac_img.jpg) + +Process\_Input + +``` +/* Data declarations */ + +TIMER Tssf; +``` + +``` +/* Timer Tssf can have four different values, as described in Q.1218, Section 3.1.1.5. These +are denoted: + +value1 when entering State Waiting For Instructions after sending initiating IF to SCF + +value2 when entering State Waiting For Instructions under any other condition + +value3 when SSF receives HoldCallInNetwork operation + +value4 when entering States Waiting For End of User Interaction or Waiting For End of +Temporary Connection (optional) + +*/ +``` + +``` +/* + +A locally defined procedure Process_Input is used to indicate analysis of an Input from an external source to +determine whether service logic processing (outside the SSF FSM) is required. + +No details of possible processing in the procedure are given, as it is intended only to indicate that processing +may be required, not its exact nature. + +*/ +``` + +T1171770-95/d44 + +FIGURE A.1/Q.1218 (sheet 1 of 17) +**SDL for SSF-FSM** + +``` + +/* Signal definitions - First part +These signals to and from CCF are internal indications which are not defined in the IN +CS-1 Recommendations. + +The names are therefore local names only. +*/ +/* From CCF */ +SIGNAL ForwardConnectionReleased, Abandon, Disconnect; +/* To CCF */ +SIGNAL RestartProcessing, TerminateCall, ConnectSRF, RouteToDefault, SRFReleaseRequest; + +/* Signal definitions - Second part. +These signals from internal (SSF) logic are internal indications which are not defined in the IN CS-1 +Recommendations. + +The names are therefore local names only. +*/ +/* From SSF service logic */ +SIGNAL TDP_R, TDP_N, EDP_N, EDP_R; +/* Local names defined for signals SSF to SCF */ +SIGNAL TDPEvent; /* Indicates one of InitialDP or a DP specific operation */ +SIGNAL EDPEvent; /* Indicates one of EventReportBCSM or a DP specific operation */ + +/* Signal definitions - Third part. Defined in IN CS-1 Recommendations. */ + +/* To SCF - The following are the DP specific operations from SSF to SCF */ +SIGNAL TAnswer, TDisconnect, TermAttemptAuthorized, TmidCall, TNoAnswer, AnalysedInformation, +TCalledPartyBusy, CollectedInformation, OAnswer, OCalledPartyBusy, ODisconnect, OMidCall, +ONoAnswer, OriginationAttemptAuthorized, RouteSelectFailure; + +/* Other signals SSF to SCF */ +SIGNAL Initial DP, EventReport BCSM, ApplyChargingReport, EventNotificationCharging, +CallInformationReport; + +/* From SCF */ +SIGNAL InitiateCallAttempt, ConnectToResource, EstablishTemporaryConnection, HoldCallInNetwork, +ApplyCharging, CallInformationRequest, FurnishChargingInformation, RequestNotificationChargingEvent, +RequestReportBCSMEVENT, ResetTimer, SendChargingInformation, AnalyseInformation, +CollectInformation, Connect, Continue, SelectFacility, SelectRoute, DisconnectForwardConnection, +ReleaseCall; + +/* Signal definitions - Fourth part. Defined in IN CS-1 Recommendations. */ +/* Relay from SCF to SRF */ +/* NOTE - Cancel can also be used SCF to SSF */ +SIGNAL Cancel, PlayAnnouncement, PromptAndCollectUserInfoInformation; +/* Relay from SRF to SCF */ +SIGNAL ReturnResult_from_PromptAndCollectUserInfoInformation, SpecializedResourceReport; + +``` + +T1171780-95/d45 + +FIGURE A.1/Q.1218 (sheet 2 of 17) +**SDL for SSF-FSM** + +``` + +/* TDPEvent is a locally-defined name for the signal which is sent from the SCF. +Its meaning is: + Send either InitialDP or a DP specific operation +(as defined in Q.1218, Section 3.1.1.5) +*/ + +``` + +![State transition diagram for INAP_SSF process. It starts at an initial state leading to 'Idle'. From 'Idle', two transitions are possible: 'TDP_R' and 'TDP_N'. The 'TDP_R' path leads to 'Process_Input', then 'TDPEvent to SCF' (with a note about TDP-R detection), then 'SET (NOW + value 1, Tssf)', and finally 'Waiting For Instructions'. The 'TDP_N' path leads to 'Process_Input', then 'TDPEvent to SCF' (with a note about TDP-N detection), then 'Restart_Processing TO CCF', and finally 'Idle'.](0c373f7645ae57a94d9107bb41043cfe_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> TDP_R + Idle --> TDP_N + state "TDP_R" as TDP_R + state "TDP_N" as TDP_N + TDP_R --> Process_Input_R + state "Process_Input" as Process_Input_R + Process_Input_R --> TDPEvent_R + state "TDPEvent to SCF" as TDPEvent_R + TDPEvent_R --> SET_R + state "SET (NOW + value 1, Tssf)" as SET_R + SET_R --> Waiting_R + state "Waiting For Instructions" as Waiting_R + TDP_N --> Process_Input_N + state "Process_Input" as Process_Input_N + Process_Input_N --> TDPEvent_N + state "TDPEvent to SCF" as TDPEvent_N + TDPEvent_N --> Restart_N + state "Restart_Processing TO CCF" as Restart_N + Restart_N --> Idle_N + state "Idle" as Idle_N + +``` + +State transition diagram for INAP\_SSF process. It starts at an initial state leading to 'Idle'. From 'Idle', two transitions are possible: 'TDP\_R' and 'TDP\_N'. The 'TDP\_R' path leads to 'Process\_Input', then 'TDPEvent to SCF' (with a note about TDP-R detection), then 'SET (NOW + value 1, Tssf)', and finally 'Waiting For Instructions'. The 'TDP\_N' path leads to 'Process\_Input', then 'TDPEvent to SCF' (with a note about TDP-N detection), then 'Restart\_Processing TO CCF', and finally 'Idle'. + +T1171790-95/d46 + +FIGURE A.1/Q.1218 (sheet 3 of 17) +SDL for SSF-FSM + +![State transition diagram for INAP_SSF process. It shows a sequence of states and transitions: Idle (State a) -> Initiate_CallAttempt (from SCF) -> Process_Input -> SET (NOW + value2, Tssf) -> Waiting For Instructions. Annotations indicate that Idle is also on Page 3 and that BCSM is instantiated as well as SSF FSM during the Initiate_CallAttempt transition.](fc6c35ceb9e2311c5aabd66c1d677483_img.jpg) + +``` +graph TD; Idle([Idle]) --> Initiate{Initiate_CallAttempt +/*from SCF */}; Initiate --> ProcessInput[Process_Input]; ProcessInput --> SET[SET (NOW + value2, Tssf)]; SET --> Waiting([Waiting For Instructions]); Idle -.-> Note1[State a +Also appears +on Page 3]; Initiate -.-> Note2[BCSM is instantiated +as well as SSF FSM]; +``` + +State transition diagram for INAP\_SSF process. It shows a sequence of states and transitions: Idle (State a) -> Initiate\_CallAttempt (from SCF) -> Process\_Input -> SET (NOW + value2, Tssf) -> Waiting For Instructions. Annotations indicate that Idle is also on Page 3 and that BCSM is instantiated as well as SSF FSM during the Initiate\_CallAttempt transition. + +T1171800-95/d47 + +FIGURE A.1/Q.1218 (sheet 4 of 17) +**SDL for SSF-FSM** + +``` + +/* Use of timer Tssf in states Waiting For End of User Interaction and Waiting For End +Of Temporary Connection is optional. + +Timer value after receipt of Cancel may be value2, if call resulted from InitiateCallAttempt +operation + +*/ + +``` + +![State transition diagram for INAP_SSF process. It starts from 'Waiting For Instructions' (State c) and branches into three paths: 1) 'ConnectTo_Resource' -> 'Process_Input' -> 'ConnectSRF TO CCF' -> 'SET (NOW + value4, Tssf)' -> 'Waiting For End Of User Interaction'; 2) 'Establish_Temporary_Connection' -> 'Process_Input' -> 'ConnectSRF TO CCF' -> 'SET (NOW + value4, Tssf)' -> 'Waiting For End Of Temporary Connection'; 3) 'Tssf / Timer expiry' -> 'Process_Input' -> 'RouteTo_Default TO CCF' -> 'Abort transaction' -> 'Idle'.](f2c8124b953b46b53423532cff4903e8_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WaitingForInstructions : Waiting For Instructions (State c) + WaitingForInstructions --> ConnectTo_Resource : ConnectTo_Resource /* from SCF */ + WaitingForInstructions --> Establish_Temporary_Connection : Establish_Temporary_Connection /* from SCF */ + WaitingForInstructions --> Tssf : Tssf /* Timer expiry */ + + ConnectTo_Resource --> Process_Input_1 : Process_Input + Process_Input_1 --> ConnectSRF_TO_CCF_1 : ConnectSRF TO CCF + ConnectSRF_TO_CCF_1 --> SET_1 : SET (NOW + value4, Tssf) + SET_1 --> WaitingForEndOfUserInteraction : Waiting For End Of User Interaction + + Establish_Temporary_Connection --> Process_Input_2 : Process_Input + Process_Input_2 --> ConnectSRF_TO_CCF_2 : ConnectSRF TO CCF + ConnectSRF_TO_CCF_2 --> SET_2 : SET (NOW + value4, Tssf) + SET_2 --> WaitingForEndOfTemporaryConnection : Waiting For End Of Temporary Connection + + Tssf --> Process_Input_3 : Process_Input + Process_Input_3 --> RouteTo_Default_TO_CCF : RouteTo_Default TO CCF + RouteTo_Default_TO_CCF --> Abort_transaction : "Abort transaction" + Abort_transaction --> Idle : Idle + +``` + +State transition diagram for INAP\_SSF process. It starts from 'Waiting For Instructions' (State c) and branches into three paths: 1) 'ConnectTo\_Resource' -> 'Process\_Input' -> 'ConnectSRF TO CCF' -> 'SET (NOW + value4, Tssf)' -> 'Waiting For End Of User Interaction'; 2) 'Establish\_Temporary\_Connection' -> 'Process\_Input' -> 'ConnectSRF TO CCF' -> 'SET (NOW + value4, Tssf)' -> 'Waiting For End Of Temporary Connection'; 3) 'Tssf / Timer expiry' -> 'Process\_Input' -> 'RouteTo\_Default TO CCF' -> 'Abort transaction' -> 'Idle'. + +T1171810-95/d48 + +FIGURE A.1/Q.1218 (sheet 5 of 17) +SDL for SSF-FSM + +/\* Where test is made for CallInformationReport pending, ApplyChargingReport is also to be handled the same way \*/ + +![State transition diagram for PROCESS INAP_SSF starting from 'Waiting For Instructions' state, branching into 'Process_Input' and 'ReleaseCall' paths.](bb0e323a672fa2f89e0132b1db61cfb3_img.jpg) + +The diagram is a State Transition Diagram (STD) for the process INAP\_SSF. It begins with an initial state 'Waiting For Instructions' (oval). A dashed line from this state points to a note: 'Also appears on Pages 5, 7, 8'. From the initial state, two transitions lead to different paths. The left path goes through a transition (chevron) labeled 'Call-processing signals from SCF' (indicated by a dashed line) to a state 'Process\_Input' (double rectangle). From 'Process\_Input', a transition leads to a decision diamond 'EDP armed'. If 'Yes', it goes to state 'Monitoring' (oval). If 'No', it goes to another decision diamond 'Report pending'. If 'Yes', it goes to 'Monitoring'. If 'No', it goes to state 'Idle' (oval). The right path from the initial state goes through a transition (chevron) labeled 'ReleaseCall /\* from SCF \*/' to another state 'Process\_Input' (double rectangle). From this 'Process\_Input', a transition leads to a state 'TerminateCall TO CCF' (pentagon). From 'TerminateCall TO CCF', a transition leads to a decision diamond 'Report pending'. If 'Yes', it goes to a state 'Call\_Information\_Report TO SCF' (pentagon). If 'No', it goes directly to state 'Idle' (oval). Both 'Call\_Information\_Report TO SCF' and the 'No' path from 'Report pending' lead to the final 'Idle' state (oval). + +State transition diagram for PROCESS INAP\_SSF starting from 'Waiting For Instructions' state, branching into 'Process\_Input' and 'ReleaseCall' paths. + +T1171820-95/d49 + +FIGURE A.1/Q.1218 (sheet 6 of 17) +SDL for SSF-FSM + +![SDL diagram for SSF-FSM showing transitions from 'Waiting For Instructions' state. Two paths lead through input processing and timer setting back to the same state.](a561e135db923dfc9249466ba186f1cd_img.jpg) + +``` + +stateDiagram-v2 + state "Waiting For Instructions" as S1 + state "Waiting For Instructions" as S2 + + [*] --> S1 + S1 --> LeftPath + S1 --> RightPath + + state LeftPath { + direction TB + Input1: Cancel (allRequests), +ApplyCharging, CallInformationRequest, +FurnishChargingInformation, +RequestNotificationChargingEvent, +RequestReportBCSMEEvent, +SendChargingInformation +/* from SCF */ + Proc1: Process_Input + Task1: SET (NOW + value1, Tssf) + Note1: May be value2 if +call resulted from +InitiatedCallAttempt + + Input1 --> Proc1 + Proc1 --> Task1 + } + + state RightPath { + direction TB + Input2: HoldCall_InNetwork +/* from SCF */ + Proc2: Process_Input + Task2: SET (NOW + value3, Tssf) + Note2: RequestNotificationChargingEvent and +Request ReportBCSMEvent may also terminate +monitoring of a previously requested event + + Input2 --> Proc2 + Proc2 --> Task2 + } + + LeftPath --> S2 + RightPath --> S2 + S2 --> [*] + + note right of S1: Also appears on Pages 5, 6, 8 + +``` + +SDL diagram for SSF-FSM showing transitions from 'Waiting For Instructions' state. Two paths lead through input processing and timer setting back to the same state. + +T1171830-95/d50 + +FIGURE A.1/Q.1218 (sheet 7 of 17) +**SDL for SSF-FSM** + +/\* While waiting for the first response from the SCF, the timer Tssf can be restarted only once by a ResetTimer operation. Subsequent to the first response, the timer can be restarted any number of times. + +ResetTimer itself is not treated as the first response. + +When InitiateCallAttempt has been received, the timer can be restarted any number of times. + +\*/ + +![SDL diagram for SSF-FSM showing the logic for ResetTimer and Tssf timer management. It includes states for 'Waiting For Instructions', inputs for 'ResetTimer', and decision logic based on whether the first response was received or if it has already been restarted once.](9fd01022f79fbde4502e8da2a8fe4372_img.jpg) + +``` + +graph TD + S1([Waiting For Instructions]) -- "Also appears on Pages 5, 6, 7" --- S1 + S1 --> I1[/ResetTimer +/* from SCF *//] + I1 --> T1[[Process_Input]] + T1 --> D1{"First response received"} + D1 -- "No" --> D2{"Already restarted once"} + D1 -- "Yes" --> T2[SET (NOW + VALUE, Tssf)] + D2 -- "No" --> T2 + D2 -- "Yes" --> S2([Waiting For Instructions]) + T2 --> S2 + + subgraph Annotations + A1[Test does not apply if +InitiateCallAttempt +received] -.- D1 + A2[VALUE as received in +ResetTimer operation] -.- T2 + end + +``` + +SDL diagram for SSF-FSM showing the logic for ResetTimer and Tssf timer management. It includes states for 'Waiting For Instructions', inputs for 'ResetTimer', and decision logic based on whether the first response was received or if it has already been restarted once. + +T1171840-95/d51 + +FIGURE A.1/Q.1218 (sheet 8 of 17) +**SDL for SSF-FSM** + +![State transition diagram for PROCESS INAP_SSF. The diagram shows a state machine starting from 'Waiting For End Of User Interaction' (State d). Transitions include 'Cancel, PlayAnnouncement, PromptAndCollect_UserInformation' (from SCF), 'SpecializedResource_Report, ReturnResult_from_PromptAndCollect_UserInformation' (from SRF), and 'Tssf' (timer expiry). Actions include 'Process_Input', 'Relay message to SRF', 'SET (NOW + value4, Tssf)', 'RouteTo_Default TO CCF', 'Abort transaction', and 'Relay message to SCF'. The final state is 'Idle'.](e1e99216b0e841d19353400e3303ba45_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WaitingForEndOfUserInteraction : Waiting For End Of User Interaction (State d) + state "Waiting For End Of User Interaction" as WaitingForEndOfUserInteraction + state "Process_Input" as ProcessInput1 : Process_Input + state "Relay message to SRF" as RelayMessageToSRF + state "SET (NOW + value4, Tssf)" as SET1 + state "Waiting For End Of User Interaction" as WaitingForEndOfUserInteraction1 : Waiting For End Of User Interaction + state "Process_Input" as ProcessInput2 : Process_Input + state "RouteTo_Default TO CCF" as RouteToDefaultTOCCF + state "Abort transaction" as AbortTransaction + state "Idle" as Idle + state "Relay message to SCF" as RelayMessageToSCF + state "SET (NOW + value4, Tssf)" as SET2 + state "Waiting For End Of User Interaction" as WaitingForEndOfUserInteraction2 : Waiting For End Of User Interaction + + WaitingForEndOfUserInteraction --> ProcessInput1 + WaitingForEndOfUserInteraction --> Tssf : Tssf /* Timer expiry */ + WaitingForEndOfUserInteraction --> ProcessInput2 + WaitingForEndOfUserInteraction --> RelayMessageToSCF + WaitingForEndOfUserInteraction --> SET2 + + ProcessInput1 --> RelayMessageToSRF + RelayMessageToSRF --> SET1 + SET1 --> WaitingForEndOfUserInteraction1 + + Tssf --> ProcessInput2 + ProcessInput2 --> RouteToDefaultTOCCF + RouteToDefaultTOCCF --> AbortTransaction + AbortTransaction --> Idle + + ProcessInput2 --> RelayMessageToSCF + RelayMessageToSCF --> SET2 + SET2 --> WaitingForEndOfUserInteraction2 + + note right of WaitingForEndOfUserInteraction : /* Cancel here is cancellation of an announcement. +Use of timers for this state is optional. +*/ + note right of WaitingForEndOfUserInteraction : State d +Also appears on Page 10 + +``` + +State transition diagram for PROCESS INAP\_SSF. The diagram shows a state machine starting from 'Waiting For End Of User Interaction' (State d). Transitions include 'Cancel, PlayAnnouncement, PromptAndCollect\_UserInformation' (from SCF), 'SpecializedResource\_Report, ReturnResult\_from\_PromptAndCollect\_UserInformation' (from SRF), and 'Tssf' (timer expiry). Actions include 'Process\_Input', 'Relay message to SRF', 'SET (NOW + value4, Tssf)', 'RouteTo\_Default TO CCF', 'Abort transaction', and 'Relay message to SCF'. The final state is 'Idle'. + +T1171850-95/d52 + +FIGURE A.1/Q.1218 (sheet 9 of 17) +SDL for SSF-FSM + +![State transition diagram for PROCESS INAP_SSF. It shows two main paths starting from 'Waiting For End Of User Interaction'. The left path involves 'Disconnect_Forward_Connection' from SCF, 'Process_Input', 'SRFRelease_Request TO CCF', a transition to 'Process_Input', a 'SET (NOW + VALUE, Tssf)' operation, and finally 'Waiting For End Of User Interaction'. The right path involves 'Forward_Connection_Released' from CCF, 'Process_Input', a 'SET (NOW + value1, Tssf)' operation, and 'Waiting For Instructions'. Various annotations explain parameters and external references.](d1ba2b47c5ebc10187d8e9089eacca4d_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Waiting_For_End_Of_User_Interaction + state "Waiting For End Of User Interaction" as Waiting_For_End_Of_User_Interaction + state "Waiting For Instructions" as Waiting_For_Instructions + state "Process_Input" as Process_Input + state "SET (NOW + VALUE, Tssf)" as SET_NOW_VALUE_Tssf + state "SET (NOW + value1, Tssf)" as SET_NOW_value1_Tssf + + Waiting_For_End_Of_User_Interaction --> Disconnect_Forward_Connection + state "Disconnect_Forward_Connection /* from SCF */" as Disconnect_Forward_Connection + Disconnect_Forward_Connection --> Process_Input + Process_Input --> SRFRelease_Request_TO_CCF + state "SRFRelease_Request TO CCF" as SRFRelease_Request_TO_CCF + SRFRelease_Request_TO_CCF --> Process_Input + Process_Input --> SET_NOW_VALUE_Tssf + SET_NOW_VALUE_Tssf --> Waiting_For_End_Of_User_Interaction + + Waiting_For_End_Of_User_Interaction --> Forward_Connection_Released + state "Forward_Connection_Released /* from CCF */" as Forward_Connection_Released + Forward_Connection_Released --> Process_Input + Process_Input --> SET_NOW_value1_Tssf + SET_NOW_value1_Tssf --> Waiting_For_Instructions + + note right of Waiting_For_End_Of_User_Interaction: Also appears on Page 9 + note right of Forward_Connection_Released: SRF-initiated release + note right of SET_NOW_VALUE_Tssf: VALUE is parameter from ResetTimer operation, if received, else value4 (optional use of timer in this state) + note right of SET_NOW_value1_Tssf: value2 if from Initiate Call Attempt + note right of Disconnect_Forward_Connection: ApplyCharging, FurnishChargingInformation, RequestNotificationChargingEvent, SendChargingInformation, ResetTimer /* from SCF */ + +``` + +State transition diagram for PROCESS INAP\_SSF. It shows two main paths starting from 'Waiting For End Of User Interaction'. The left path involves 'Disconnect\_Forward\_Connection' from SCF, 'Process\_Input', 'SRFRelease\_Request TO CCF', a transition to 'Process\_Input', a 'SET (NOW + VALUE, Tssf)' operation, and finally 'Waiting For End Of User Interaction'. The right path involves 'Forward\_Connection\_Released' from CCF, 'Process\_Input', a 'SET (NOW + value1, Tssf)' operation, and 'Waiting For Instructions'. Various annotations explain parameters and external references. + +T1171860-95/d53 + +FIGURE A.1/Q.1218 (sheet 10 of 17) +**SDL for SSF-FSM** + +![State transition diagram for INAP_SSF process. The diagram shows transitions between states 'Waiting For End Of Temporary Connection', 'Waiting For Instructions', 'Idle', and 'Waiting For End Of Temporary Connection'. Transitions are triggered by events like Disconnect_Foward_Connection, Forward_Connection_Released, and Tssf, and result in actions like Process_Input, SRFRelease_Request TO CCF, SET (NOW + value1, Tssf), RouteTo_Default TO CCF, 'Abort transaction', ApplyCharging, and SET (NOW + VALUE, Tssf).](793b6344c79e3e858d29ef190b2c014f_img.jpg) + +PROCESS INAP\_SSF + +PAGE 11 (17) + +``` + +stateDiagram-v2 + [*] --> WaitingForEndOfTemporaryConnection1: Waiting For End Of Temporary Connection + state "Waiting For End Of Temporary Connection" as WaitingForEndOfTemporaryConnection1 + state "Waiting For Instructions" as WaitingForInstructions + state "Idle" as Idle + state "Waiting For End Of Temporary Connection" as WaitingForEndOfTemporaryConnection2 + + WaitingForEndOfTemporaryConnection1 --> Disconnect_Foward_Connection: Disconnect_Foward_Connection /* from SCF */ + WaitingForEndOfTemporaryConnection1 --> Forward_Connection_Released: Forward_Connection_Released /* from CCF */ + WaitingForEndOfTemporaryConnection1 --> Tssf + + Disconnect_Foward_Connection --> Process_Input1: Process_Input + Process_Input1 --> SRFRelease_Request_TO_CCF: SRFRelease_Request TO CCF + SRFRelease_Request_TO_CCF --> SET_NOW_value1_Tssf: SET (NOW + value1, Tssf) + SET_NOW_value1_Tssf --> WaitingForInstructions + SET_NOW_value1_Tssf --> value2_if_call_resulted_from_InitiateCall_Attempt: value2 if call resulted from InitiateCall Attempt + + Forward_Connection_Released --> Process_Input2: Process_Input + Process_Input2 --> SET_NOW_value1_Tssf + + Tssf --> Process_Input3: Process_Input + Process_Input3 --> RouteTo_Default_TO_CCF: RouteTo_Default TO CCF + RouteTo_Default_TO_CCF --> Abort_transaction: "Abort transaction" + Abort_transaction --> Idle + + WaitingForEndOfTemporaryConnection2 --> ApplyCharging: ApplyCharging, FurnishChargingInformation, RequestNotificationChargingEvent, SendChargingInformation, ResetTimer /* from SCF */ + ApplyCharging --> Process_Input4: Process_Input + Process_Input4 --> SET_NOW_VALUE_Tssf: SET (NOW + VALUE, Tssf) + SET_NOW_VALUE_Tssf --> Value_is_parameter_from_ResetTimer_operation: Value is parameter from ResetTimer operation, if received, else value4 (optional timer in this state) + Value_is_parameter_from_ResetTimer_operation --> SET_NOW_VALUE_Tssf + SET_NOW_VALUE_Tssf --> WaitingForEndOfTemporaryConnection2 + +``` + +State transition diagram for INAP\_SSF process. The diagram shows transitions between states 'Waiting For End Of Temporary Connection', 'Waiting For Instructions', 'Idle', and 'Waiting For End Of Temporary Connection'. Transitions are triggered by events like Disconnect\_Foward\_Connection, Forward\_Connection\_Released, and Tssf, and result in actions like Process\_Input, SRFRelease\_Request TO CCF, SET (NOW + value1, Tssf), RouteTo\_Default TO CCF, 'Abort transaction', ApplyCharging, and SET (NOW + VALUE, Tssf). + +T1 171870-95/d54 + +FIGURE A.1/Q.1218 (sheet 11 of 17) +**SDL for SSF-FSM** + +``` + +/* Only EDPs are handled within the existing FSM. If a TDP is armed it will create a new +instance of an FSM to handle the interaction. + +DPs 4, 5, 6, 8 in O_BCSM and 13, 14, 16 in T_BCSM shown here. +Handling of EDPs at DPs 9, 10, 17 and 18 (abandon and disconnect) is shown on page 16. + +The description here follows CallInformationReport procedure, not the text of Q.1218, Section 3.1.1.5.6. + +*/ + +``` + +![State transition diagram for SSF-FSM starting from Monitoring state. It branches into EDP_R and EDP_N paths. EDP_R leads to Process_Input, then a 'Report pending' decision. EDP_N leads to Process_Input, then EDPEvent TO SCF, then a 'Report pending' decision. Both paths lead to Call_Information_Report to SCF. The EDP_N path continues with 'Last EDP' and 'Report pending' decisions leading to either Monitoring or Idle state. The EDP_R path leads to EDPEvent TO SCF, SET (NOW + value1, Tssf), and Waiting For Instructions state.](f3f568cc57088117f1c4589f174d3dbf_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> EDP_R + Monitoring --> EDP_N + EDP_R --> Process_Input_R[Process_Input] + Process_Input_R --> ReportPending_R{Report pending} + ReportPending_R -- No --> EDPEvent_TO_SCF_R[EDPEvent TO SCF] + ReportPending_R -- Yes --> CallInfo_R[Call_Information_Report to SCF] + EDPEvent_TO_SCF_R --> SET_R[SET (NOW + value1, Tssf)] + SET_R --> WaitingForInstructions[Waiting For Instructions] + EDP_N --> Process_Input_N[Process_Input] + Process_Input_N --> EDPEvent_TO_SCF_N[EDPEvent TO SCF] + EDPEvent_TO_SCF_N --> ReportPending_N{Report pending} + ReportPending_N -- No --> CallInfo_N[Call_Information_Report to SCF] + ReportPending_N -- Yes --> LastEDP{Last EDP} + LastEDP -- Yes --> ReportPending_Next{Report pending} + ReportPending_Next -- Yes --> Monitoring + ReportPending_Next -- No --> Idle + LastEDP -- No --> Monitoring + +``` + +State transition diagram for SSF-FSM starting from Monitoring state. It branches into EDP\_R and EDP\_N paths. EDP\_R leads to Process\_Input, then a 'Report pending' decision. EDP\_N leads to Process\_Input, then EDPEvent TO SCF, then a 'Report pending' decision. Both paths lead to Call\_Information\_Report to SCF. The EDP\_N path continues with 'Last EDP' and 'Report pending' decisions leading to either Monitoring or Idle state. The EDP\_R path leads to EDPEvent TO SCF, SET (NOW + value1, Tssf), and Waiting For Instructions state. + +T1171880-95/d55 + +FIGURE A.1/Q.1218 (sheet 12 of 17) +**SDL for SSF-FSM** + +``` + +/* The reports which can be pending here are CallInformationReport, + ApplyChargingReport and EventNotificationCharging + + RequestReportBCSMEVENT and RequestNotificationChargingEvent can terminate + monitoring for a previously requested event. + +*/ + +``` + +![State transition diagram for PROCESS INAP_SSF. It starts with a Monitoring state (oval) leading to a horizontal line. From this line, three paths emerge: 1) Request_Report_BCSMEVENT (parallelogram) leading to Process_Input (double rectangle), then to a decision 'EDPs still armed' (diamond). If 'Yes', it goes to Monitoring (oval). If 'No', it goes to 'Report pending' (diamond). If 'Yes' to 'Report pending', it goes to Monitoring (oval). If 'No', it goes to Idle (oval). 2) RequestNotificationChargingEvent, SendChargingInformation, FurnishChargingInformation, ApplyCharging (rectangle) leading to an empty parallelogram. 3) An empty parallelogram leading to Process_Input (double rectangle), then to Monitoring (oval). A note 'State f Also on Pages 12 and 14' is connected to the first Monitoring state.](35ddc8b19bd31dedba7ba2d696f43bd0_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> HorizontalLine + HorizontalLine --> Request_Report_BCSMEVENT + HorizontalLine --> RequestNotificationChargingEvent + HorizontalLine --> EmptyParallelogram + Request_Report_BCSMEVENT --> Process_Input1[Process_Input] + Process_Input1 --> EDPsStillArmed{EDPs still armed} + EDPsStillArmed -- Yes --> Monitoring1(Monitoring) + EDPsStillArmed -- No --> ReportPending{Report pending} + ReportPending -- Yes --> Monitoring2(Monitoring) + ReportPending -- No --> Idle + RequestNotificationChargingEvent --> RequestNotificationChargingEvent + RequestNotificationChargingEvent --> EmptyParallelogram + EmptyParallelogram --> Process_Input2[Process_Input] + Process_Input2 --> Monitoring3(Monitoring) + +``` + +State transition diagram for PROCESS INAP\_SSF. It starts with a Monitoring state (oval) leading to a horizontal line. From this line, three paths emerge: 1) Request\_Report\_BCSMEVENT (parallelogram) leading to Process\_Input (double rectangle), then to a decision 'EDPs still armed' (diamond). If 'Yes', it goes to Monitoring (oval). If 'No', it goes to 'Report pending' (diamond). If 'Yes' to 'Report pending', it goes to Monitoring (oval). If 'No', it goes to Idle (oval). 2) RequestNotificationChargingEvent, SendChargingInformation, FurnishChargingInformation, ApplyCharging (rectangle) leading to an empty parallelogram. 3) An empty parallelogram leading to Process\_Input (double rectangle), then to Monitoring (oval). A note 'State f Also on Pages 12 and 14' is connected to the first Monitoring state. + +T1171890-95/d56 + +FIGURE A.1/Q.1218 (sheet 13 of 17) +SDL for SSF-FSM + +![State transition diagram for PROCESS INAP_SSF starting from Monitoring state. Transitions include ReleaseCall, TC_END/TC_ABORT, and Cancel_(allRequests) leading to Process_Input blocks. From Process_Input, one path leads to TerminateCall TO CCF and another to a 'Report pending' decision. The decision leads to either Call_Information_Report TO SCF or Idle state. A note indicates 'ApplyChargingReport treated same way as CallInformation Report'.](a699461afffb5a9ccfc5db15fa7fe728_img.jpg) + +``` +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> ReleaseCall + Monitoring --> TC_END_TC_ABORT + Monitoring --> Cancel_allRequests + ReleaseCall --> Process_Input_1 + TC_END_TC_ABORT --> Process_Input_2 + Cancel_allRequests --> Process_Input_3 + Process_Input_1 --> TerminateCall_TO_CCF + Process_Input_2 --> Report_pending + Process_Input_3 --> Idle_1 + TerminateCall_TO_CCF --> Report_pending + Report_pending --> Call_Information_Report_TO_SCF + Report_pending --> Idle_2 + Note right of Report_pending: ApplyChargingReport treated same way as CallInformation Report +``` + +The diagram illustrates the state transitions for the INAP\_SSF process. It begins in the **Monitoring** state, which is also referenced on pages 12 and 13. From **Monitoring**, three transitions are available: **ReleaseCall** (from SCF), **TC\_END, TC\_ABORT** (from SCF), and **Cancel\_(allRequests)** (from SCF). Each transition leads to a **Process\_Input** block. The **ReleaseCall** path leads to **TerminateCall TO CCF**, which then leads to a decision diamond labeled **"Report pending"**. The **TC\_END, TC\_ABORT** path leads directly to the same **"Report pending"** decision. The **Cancel\_(allRequests)** path leads to **Process\_Input** and then to the **Idle** state. From the **"Report pending"** decision, a **"Yes"** response leads to **Call\_Information\_Report TO SCF**, which then leads to the **Idle** state. A **"No"** response from the decision also leads directly to the **Idle** state. A note indicates that **ApplyChargingReport** is treated the same way as **CallInformation Report**. + +State transition diagram for PROCESS INAP\_SSF starting from Monitoring state. Transitions include ReleaseCall, TC\_END/TC\_ABORT, and Cancel\_(allRequests) leading to Process\_Input blocks. From Process\_Input, one path leads to TerminateCall TO CCF and another to a 'Report pending' decision. The decision leads to either Call\_Information\_Report TO SCF or Idle state. A note indicates 'ApplyChargingReport treated same way as CallInformation Report'. + +T1 171900-95/d57 + +FIGURE A.1/Q.1218 (sheet 14 of 17) +SDL for SSF-FSM + +/\* Charging events requested by RequestNotificationChargingEvent can be handled in any state except Idle \*/ + +![State transition diagram for INAP_SSF process. It starts at the *Idle state, followed by a Charging_Event transition (Previously requested), a Process_Input state (Service logic handles event as required), an Event_Notification_Charging TO SCF transition, a SET (NOW + VALUE, Tssf) state (If required, VALUE is current value), and finally a transition back to the previous state.](0dd5bfd07d4d960d2768f54254691653_img.jpg) + +``` +stateDiagram-v2 + [*] --> *Idle + *Idle --> Charging_Event : Previously requested + Charging_Event --> Process_Input : Service logic handles event as required + Process_Input --> Event_Notification_Charging_TO_SCF + Event_Notification_Charging_TO_SCF --> SET_NOW_VALUE_Tssf : If required, VALUE is current value + SET_NOW_VALUE_Tssf --> PreviousState : Return to previous state +``` + +State transition diagram for INAP\_SSF process. It starts at the \*Idle state, followed by a Charging\_Event transition (Previously requested), a Process\_Input state (Service logic handles event as required), an Event\_Notification\_Charging TO SCF transition, a SET (NOW + VALUE, Tssf) state (If required, VALUE is current value), and finally a transition back to the previous state. + +T1171910-95/d58 + +FIGURE A.1/Q.1218 (sheet 15 of 17) +SDL for SSF-FSM + +/\* Charging events requested by ApplyCharging can be handled in any state except Idle \*/ + +![State transition diagram for INAP_SSF process. It starts at *Idle, goes through Charging_Event, Process_Input, and Apply_Charging. Then it checks 'Connection Configuration changed'. If 'No', it goes to a state labeled '-'. If 'Yes', it checks 'EDPs armed'. If 'Yes', it goes to '-'. If 'No', it checks 'Reports pending'. If 'Yes', it goes to 'SET (NOW + VALUE, Tssf)'. If 'No', it goes to Idle. From 'SET (NOW + VALUE, Tssf)', it goes to '-'.](0bb475bf99a4fb0082c265e9fcfd3433_img.jpg) + +``` +stateDiagram-v2 + [*] --> *Idle + *Idle --> Charging_Event + Charging_Event --> Process_Input + Process_Input --> Apply_Charging + Apply_Charging --> Connection_Configuration_Changed{Connection Configuration changed} + Connection_Configuration_Changed --> No1{No} + Connection_Configuration_Changed --> Yes1{Yes} + Yes1 --> EDPs_Armed{EDPs armed} + EDPs_Armed --> Yes2{Yes} + EDPs_Armed --> No2{No} + No2 --> Reports_Pending{Reports pending} + Reports_Pending --> Yes3{Yes} + Reports_Pending --> No3{No} + No3 --> Idle + Yes3 --> SET[SET (NOW + VALUE, Tssf)] + SET --> Dash{-} +``` + +The diagram is a State Transition Diagram (STD) for the INAP\_SSF process. It begins with an initial state labeled \*Idle. The first transition is Charging\_Event, which is associated with a note "Previously requested". This leads to Process\_Input, associated with a note "Service logic handles event as required". The next transition is Apply\_Charging, labeled "Report to SCF". This leads to a decision diamond "Connection Configuration changed". If the answer is "No", the flow goes to a state labeled "-". If the answer is "Yes", it proceeds to another decision diamond "EDPs armed". If "Yes", it goes to "-". If "No", it proceeds to a third decision diamond "Reports pending". If "Yes", it goes to a state transition box "SET (NOW + VALUE, Tssf)", which is associated with a note "If required VALUE is current value". From this box, it goes to "-". If "No", it returns to the Idle state. The state labeled "-" is associated with a note "Return to previous state". + +State transition diagram for INAP\_SSF process. It starts at \*Idle, goes through Charging\_Event, Process\_Input, and Apply\_Charging. Then it checks 'Connection Configuration changed'. If 'No', it goes to a state labeled '-'. If 'Yes', it checks 'EDPs armed'. If 'Yes', it goes to '-'. If 'No', it checks 'Reports pending'. If 'Yes', it goes to 'SET (NOW + VALUE, Tssf)'. If 'No', it goes to Idle. From 'SET (NOW + VALUE, Tssf)', it goes to '-'. + +T1171920-95/d59 + +FIGURE A.1/Q.1218 (sheet 16 of 17) +SDL for SSF-FSM + +``` + +/* +Cleardown sequences for +- A party abandon +- A and B party disconnection */ + +``` + +![SDL flowchart for SSF-FSM process showing cleardown sequences for A party abandon and A/B party disconnection. The flow starts from a combined state of Waiting/Monitoring, branches into Abandon and Release paths, goes through input processing, and then enters a series of decision points regarding DP arming and report pending status, eventually leading to either an Idle state or back to Waiting For Instructions after sending reports to SCF.](2f428a156e5b9a3416517ee20ce7e4e6_img.jpg) + +``` + +stateDiagram-v2 + state "Waiting For Instructions,\nWaiting For End Of User Interaction,\nWaiting For End Of Temporary Connection,\nMonitoring" as StartState + + [*] --> StartState + + StartState --> AbandonInput + StartState --> ReleaseInput + + state AbandonInput <> + note right of AbandonInput + Abandon /* from CCF */ + Abandon from A party + DP10 in orig. BCSM, + DP18 in term. BCSM + end note + + state ReleaseInput <> + note right of ReleaseInput + Release /* from CCF */ + Release from either party. + DP9 in orig. BCSM + DP17 in term. BCSM + end note + + AbandonInput --> ProcessInput1 + ProcessInput1 --> TerminateCall + TerminateCall --> DPArmed + + ReleaseInput --> ProcessInput2 + ProcessInput2 --> DPArmed + + state DPArmed <> + DPArmed --> EDPR : "Yes" + DPArmed --> ReportPending1 : "No" + + state EDPR <> + EDPR --> ReportPending2 : "Yes" + EDPR --> EDPEvent1 : "No" + + state ReportPending2 <> + ReportPending2 --> CallInfoReport1 : "Yes" + ReportPending2 --> EDPEvent1 : "No" + + CallInfoReport1 --> EDPEvent1 + EDPEvent1 --> SetTimer + SetTimer --> WaitingForInstructions + + state ReportPending1 <> + ReportPending1 --> CallInfoReport2 : "Yes" + ReportPending1 --> Idle : "No" + + CallInfoReport2 --> Idle + + ProcessInput1: Process_Input + ProcessInput2: Process_Input + TerminateCall: Terminate_Call to CCF + EDPEvent1: EDPEvent To SCF + CallInfoReport1: Call_Information_Report to SCF + CallInfoReport2: Call_Information_Report to SCF + SetTimer: SET (NOW + Value2, Tssf) + WaitingForInstructions: Waiting For Instructions + Idle: Idle + +``` + +SDL flowchart for SSF-FSM process showing cleardown sequences for A party abandon and A/B party disconnection. The flow starts from a combined state of Waiting/Monitoring, branches into Abandon and Release paths, goes through input processing, and then enters a series of decision points regarding DP arming and report pending status, eventually leading to either an Idle state or back to Waiting For Instructions after sending reports to SCF. + +T1171930-95/d60 + +FIGURE A.1/Q.1218 (sheet 17 of 17) +**SDL for SSF-FSM** + +``` +/* +SDL for Assist/Handoff SSF for INAP +Based on Q.1218, Section 3.1.1.6 + +Version 3.1 January 1995 +*/ +``` + +Process\_Input + +``` +/* Data declarations */ + +Timer Tssf; +``` + +``` +/* The identification of the possible values of Tssf is given in the SDL +diagrams for the SSF. + +Reference Q.1218, Section 3.1.1.5 +*/ +``` + +``` +/* +A locally defined procedure Process_Input is used to indicate analysis of an input from an external source to +determine whether service logic processing (outside the SSF FSM) is required. + +No details of possible processing in the procedure are given, as it is intended only to indicate that processing +may be required, not its exact nature. +*/ +``` + +T1171940-95/d61 + +FIGURE A.2/Q.1218 (sheet 1 of 8) +SDL for assist/handoff SSF-FSM + +``` +/* Signal definitions – First part. +These signals to and from the CCF are internal indications which are not defined in the +IN CS-1 Recommendations. +The names are therefore local names only. +*/ + +/* From CCF */ + +SIGNAL AssistRequired, BackwardConnectionReleased, +ForwardConnectionReleased; + +/* To CCF */ + +SIGNAL ConnectSRF, RouteToDefault, SRFReleaseRequest, +TerminateCall; + +/* Indication from SRF representing bearer signalling release request */ +SIGNAL ReleaseRequestFrom SRF; +``` + +``` +/* Signal definitions – Second part. Operations defined in IN CS-1 +Recommendations. */ + +/* To SCF */ + +SIGNAL AssistRequestInstructions; + +/* From SCF */ + +SIGNAL ConnectTo Resource, ApplyCharging, FurnishChargingInformation, +SendChargingInformation, ResetTimer, DisconnectForwardConnection, +ReleaseCall; +``` + +``` +/* Signal definitions – Third part. Operations defined in +IN CS-1 Recommendations. */ + +/* Relay from SCF to SRF */ + +SIGNAL Cancel, PlayAnnouncement, PromptAndCollectUserInfoInformation; + +/* Relay from SRF to SCF */ + +Signal ReturnResult_from_PromptAndCollectUserInfoInformation, +SpecializedResourceReport; +``` + +T1171950-95/d62 + +FIGURE A.2/Q.1218 (sheet 2 of 8) +**SDL for assist/handoff SSF-FSM** + +![State transition diagram for PROCESS Assist_Handoff_SSF. The diagram shows a sequence of states and transitions: Idle (State a) -> Assist_Required /* from CCF */ -> Process_Input -> Assist_Request_Instructions TO SCF -> SET (NOW + value1, Tssf) -> Waiting For Instructions.](a27fa32e1be00d2a19ff032799fb432f_img.jpg) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Assist_Required : Assist_Required /* from CCF */ + Assist_Required --> Process_Input + Process_Input --> Assist_Request_Instructions : Assist_Request_Instructions TO SCF + Assist_Request_Instructions --> SET : SET (NOW + value1, Tssf) + SET --> Waiting_For_Instructions : Waiting For Instructions +``` + +State transition diagram for PROCESS Assist\_Handoff\_SSF. The diagram shows a sequence of states and transitions: Idle (State a) -> Assist\_Required /\* from CCF \*/ -> Process\_Input -> Assist\_Request\_Instructions TO SCF -> SET (NOW + value1, Tssf) -> Waiting For Instructions. + +T1171960-95/d63 + +FIGURE A.2/Q.1218 (sheet 3 of 8) +SDL for assist/handoff SSF-FSM + +![State transition diagram for PROCESS Assist_Handoff_SSF starting from 'Waiting For Instructions' (State b). Transitions include ConnectTo_Resource, ReleaseCall, BearerChannel_Disconnect, and Tssf. Subsequent actions include Process_Input, TerminateCall TO CCF, SRFRelease_Request TO CCF, and Apply_Charging_Report TO SCF, leading to Idle or Waiting For End of User Interaction states.](a37e121a419c071145d1d3600d60e35d_img.jpg) + +``` +stateDiagram-v2 + [*] --> WaitingForInstructions : Waiting For Instructions + state "Waiting For Instructions" as WaitingForInstructions + WaitingForInstructions --> ConnectTo_Resource : ConnectTo_Resource /* from SCF */ + WaitingForInstructions --> ReleaseCall : ReleaseCall /* from SCF - handoff case only */ + WaitingForInstructions --> BearerChannel_Disconnect : BearerChannel_Disconnect /* from initiating SSF */ + WaitingForInstructions --> Tssf : Tssf /* Timer expiry */ + + ConnectTo_Resource --> Process_Input1 : Process_Input + Process_Input1 --> ConnectSRF_To_CCF : ConnectSRF To CCF + ConnectSRF_To_CCF --> SET_NOW : SET (NOW + value4, Tssf) + SET_NOW --> WaitingForEndOfUserInteraction : Waiting For End of User Interaction + + ReleaseCall --> Process_Input2 : Process_Input + Process_Input2 --> TerminateCall_TO_CCF : TerminateCall TO CCF + TerminateCall_TO_CCF --> ApplyChargingReportPending : "Apply Charging_ Report pending" + ApplyChargingReportPending --> ApplyChargingReportTO_SCF : "Yes" + ApplyChargingReportTO_SCF --> Idle1 : Idle + ApplyChargingReportPending --> Idle1 : "No" + + BearerChannel_Disconnect --> Process_Input3 : Process_Input + Process_Input3 --> SRFRelease_Request_TO_CCF : SRFRelease_Request TO CCF + SRFRelease_Request_TO_CCF --> Idle2 : Idle + + Tssf --> AbortTransaction : "Abort transaction" + AbortTransaction --> Idle3 : Idle +``` + +State transition diagram for PROCESS Assist\_Handoff\_SSF starting from 'Waiting For Instructions' (State b). Transitions include ConnectTo\_Resource, ReleaseCall, BearerChannel\_Disconnect, and Tssf. Subsequent actions include Process\_Input, TerminateCall TO CCF, SRFRelease\_Request TO CCF, and Apply\_Charging\_Report TO SCF, leading to Idle or Waiting For End of User Interaction states. + +T1171970-95/d64 + +FIGURE A.2/Q.1218 (sheet 4 of 8) +SDL for assist/handoff SSF-FSM + +![SDL diagram for PROCESS Assist_Handoff_SSF showing state transitions from 'Waiting For Instructions' through various inputs and decisions back to the same state.](62a17edc9f17ac4fc99094922645e3a7_img.jpg) + +``` + +stateDiagram-v2 + state "Waiting For Instructions" as S1 + state "Waiting For Instructions" as S2 + state "Waiting For Instructions" as S3 + + S1 --> ResetTimer : Reset Timer /* from SCF */ + S1 --> ChargingInfo : ApplyCharging, FurnishChargingInformation, SendChargingInformation /* from SCF */ + + ResetTimer --> ProcessInput1 : Process_Input + ChargingInfo --> ProcessInput2 : Process_Input + + ProcessInput1 --> FirstResponse : "First response received" + + FirstResponse --> AlreadyRestarted : "No" + FirstResponse --> Set1 : "Yes" + + AlreadyRestarted --> Set1 : "Yes" + AlreadyRestarted --> S2 : "No" + + Set1 : SET (NOW + VALUE, Tssf) + Set1 --> S2 + + ProcessInput2 --> Set2 : SET (NOW + VALUE, Tssf) + Set2 --> S3 + + note right of Set1 : VALUE is parameter from Reset_Timer operation, if received, else value1 + note right of Set2 : VALUE is parameter from Reset_Timer operation, if received, else value1 + +``` + +VALUE is parameter from Reset\_Timer operation, if received, else value1 + +SDL diagram for PROCESS Assist\_Handoff\_SSF showing state transitions from 'Waiting For Instructions' through various inputs and decisions back to the same state. + +T117 1980-95/d65 + +FIGURE A.2/Q.1218 (sheet 5 of 8) +**SDL for assist/handoff SSF-FSM** + +![SDL diagram for assist/handoff SSF-FSM. The process starts in state 'Waiting For End Of User Interaction' (State c). Two input signals are possible: one from SCF (Cancel, PlayAnnouncement, PromptAndCollectUserInformation) and one from SRF (SpecializedResourceReport, ReturnResult_from_PromptAndCollectUserInformation). Each leads to a 'Process_Input' procedure and a relay task ('Relay message to SRF' or 'Relay message to SCF'). Both paths then set a timer 'SET (NOW + value4, Tssf)' and return to the 'Waiting For End Of User Interaction' state.](587077b00d0f998c32b4ead2fed3637e_img.jpg) + +``` + +stateDiagram-v2 + state "Waiting For End Of User Interaction" as StateC + note right of StateC : State c + + StateC --> InputFromSCF + state "Cancel,\nPlayAnnouncement,\nPromptAndCollectUserInformation\n/* from SCF */" as InputFromSCF + InputFromSCF --> ProcInput1 + state "Process_Input" as ProcInput1 + ProcInput1 --> RelaySRF + state "Relay message\nto SRF" as RelaySRF + + StateC --> InputFromSRF + state "SpecializedResourceReport,\nReturnResult_from_\nPromptAndCollectUserInformation\n/* from SRF */" as InputFromSRF + InputFromSRF --> ProcInput2 + state "Process_Input" as ProcInput2 + ProcInput2 --> RelaySCF + state "Relay message\nto SCF" as RelaySCF + + RelaySRF --> SetTimer + RelaySCF --> SetTimer + + state "SET (NOW +\nvalue4, Tssf)" as SetTimer + SetTimer --> StateC + +``` + +SDL diagram for assist/handoff SSF-FSM. The process starts in state 'Waiting For End Of User Interaction' (State c). Two input signals are possible: one from SCF (Cancel, PlayAnnouncement, PromptAndCollectUserInformation) and one from SRF (SpecializedResourceReport, ReturnResult\_from\_PromptAndCollectUserInformation). Each leads to a 'Process\_Input' procedure and a relay task ('Relay message to SRF' or 'Relay message to SCF'). Both paths then set a timer 'SET (NOW + value4, Tssf)' and return to the 'Waiting For End Of User Interaction' state. + +T1171990-95/d66 + +FIGURE A.2/Q.1218 (sheet 6 of 8) +SDL for assist/handoff SSF-FSM + +/\* +In the handoff case, the Handoff SSF returns to Waiting For Instructions state at the end of user interaction (i.e. when the SRF has been disconnected) and then takes over the call. From that point on, the SDL becomes that shown for Process INAP\_SSF. This has not been shown here. +\*/ + +![State transition diagram for Process Assist_Handoff_SSF. It shows two main paths from 'Waiting For End Of User Interaction' state. The left path is for 'Assist and handoff cases' and the right path is for 'Handoff case only'. Both paths lead through 'Process_Input' and then to either 'Idle' or 'Waiting For Instructions' states via various message exchanges.](7579620056cbb3563b34324b539e2e50_img.jpg) + +``` +stateDiagram-v2 + [*] --> WFEUI1: Waiting For End Of User Interaction + WFEUI1 --> BC: BearerChannel_Disconnect /* from initiating SSF */ + WFEUI1 --> DF: Disconnect_Forward_Connection /* from SCF */ + WFEUI1 --> WFEUI2: Waiting For End Of User Interaction + WFEUI2 --> RR: Release_Request_FromSRF + + BC --> PI1: Process_Input + PI1 --> SRRCF1: SRFRelease_Request TO CCF + SRRCF1 --> Idle + + DF --> PI2: Process_Input + PI2 --> SRRCF2: SRFRelease_Request TO CCF + SRRCF2 --> SET1: SET (NOW + value2, Tssf) + SET1 --> WFI: Waiting For Instructions + + RR --> PI3: Process_Input + PI3 --> SET2: SET (NOW + value2, Tssf) + SET2 --> WFI +``` + +State transition diagram for Process Assist\_Handoff\_SSF. It shows two main paths from 'Waiting For End Of User Interaction' state. The left path is for 'Assist and handoff cases' and the right path is for 'Handoff case only'. Both paths lead through 'Process\_Input' and then to either 'Idle' or 'Waiting For Instructions' states via various message exchanges. + +T1172000-95/d67 + +FIGURE A.2/Q.1218 (sheet 7 of 8) +**SDL for assist/handoff SSF-FSM** + +![State transition diagram for PROCESS Assist_Handoff_SSF. It starts at 'Waiting For End of User Interaction' and branches into two paths: one for 'ResetTimer' (from SCF) leading to 'Process_Input' and 'SET (NOW + VALUE, Tssf)' (with a note about VALUE parameter), returning to the initial state; the other for 'Tssf' (Timer expiry) leading to 'RouteToDefault TO CCF' and 'Abort transaction', ending at 'Idle'.](99bc201efaff9a7c0a66a617b474a29c_img.jpg) + +``` +stateDiagram-v2 + [*] --> WaitingForEndOfUserInteraction + state "Waiting For End of User Interaction" as WaitingForEndOfUserInteraction + state "Waiting For End Of User Interaction" as WaitingForEndOfUserInteraction2 + state Idle + WaitingForEndOfUserInteraction --> ResetTimer + state "ResetTimer /* from SCF */" as ResetTimer + ResetTimer --> Process_Input + state "Process_Input" as Process_Input + Process_Input --> SET_NOW_VALUE_Tssf + state "SET (NOW + VALUE, Tssf)" as SET_NOW_VALUE_Tssf + SET_NOW_VALUE_Tssf --> WaitingForEndOfUserInteraction2 + WaitingForEndOfUserInteraction --> Tssf + state "Tssf /* Timer expiry */" as Tssf + Tssf --> RouteToDefault_TO_CCF + state "RouteToDefault TO CCF" as RouteToDefault_TO_CCF + RouteToDefault_TO_CCF --> Abort_transaction + state "Abort transaction" as Abort_transaction + Abort_transaction --> Idle +``` + +VALUE is parameter from Reset\_Timer operation, if received, else value1 + +State transition diagram for PROCESS Assist\_Handoff\_SSF. It starts at 'Waiting For End of User Interaction' and branches into two paths: one for 'ResetTimer' (from SCF) leading to 'Process\_Input' and 'SET (NOW + VALUE, Tssf)' (with a note about VALUE parameter), returning to the initial state; the other for 'Tssf' (Timer expiry) leading to 'RouteToDefault TO CCF' and 'Abort transaction', ending at 'Idle'. + +T1172010-95/d68 + +FIGURE A.2/Q.1218 (sheet 8 of 8) +SDL for assist/handoff SSF-FSM + +``` +/* +SCF SDLs for INAP. +Based on Q.1218, Section 3.1.2.5, "The SCSM". + +Version 2.1 January 1995 +*/ +``` + +Process\_Input + +``` +/* Data declarations */ + +Timer Tscf_ssf, Tassist_handoff, Tq; +``` + +``` +/* Timer Tscf_ssf can have four different values, as described in Q.1218, Section 3.1.2.5. +These are denoted valueA, valueB, valueC and valueD. +Timer assist_handoff is given valueE. Queuing timer Tq is given valueQ. +``` + +``` +*/ +``` + +``` +/* +Procedure Process_Input analyses an input from an external source to determine +processing required. It can invoke SCF service logic. + +Output Operation TO SSF or TO SRF sends one or more of the signals listed in the +attached comment to the SSF or SRF, respectively. + +Output Exception TO SSF indicates that various types of system failure are to be +handled. +``` + +``` +*/ +``` + +T1172020-95/d69 + +FIGURE A.3/Q.1218 (sheet 1 of 20) +**SDL for SCF-FSM** + +``` + +/* Signal definitions – First part. +These signals from (internal) SCF logic are all internal indications which are defined as internal +events in the IN CS-1 Recommendations. +The names are based on the event names. +*/ + +``` + +``` + +/* From SCF service logic */ +SIGNAL SL_Invocation, Non-Call_Processing_Instructions, SR_Facilities_Needed, +Call_Processing_Instruction_Ready_e2.3, Call_Processing_Instruction_Ready_e2.4, +Ready_for_Queuing_Processing, Processing_Failure, Instruction_Ready, +Instruction_Ready_Relay, Assist_Needed, Hand_off_Needed, +More_Information_Needed, Continue_SCF_Processing_e4.3, +Continue_SCF_Processing_e4.3', Continue_SCF_Processing_e4.3'', +Cancellation_Required; + +``` + +``` + +/* Signal definitions – First part continued */ + +``` + +``` + +/* From SCF service logic */ +SIGNAL Busy_Line/Trunk, Idle_Line/Trunk, +Notification_or_Request_Continuing_Instruction, +Monitoring_Cancel_Instruction, Release_Call_Instruction_e2.14, +Release_Call_Instruction_e2.15; + +``` + +``` + +/* Signal definitions – Second part. +These signals to and from external FEs are indications which are not defined in the IN CS-1 +Recommendations. The names are therefore local names only. +*/ + +``` + +``` + +/* Local names defined for signals SSF to SCF */ +SIGNAL TDPEvent; /* Indicates one of InitialDP or a DP-specific operation */ +SIGNAL EDPEvent; /* Indicates one of EventReportBCSM or a DP_specific operation */ + +``` + +``` + +/* To SSF */ +SIGNAL Exception; + +``` + +``` + +/* From SSF */ +SIGNAL Abort_from_SSF, Initial_SSF_Failure; + +``` + +``` + +/* From SRF */ +SIGNAL Failure_from_SRF; + +``` + +T1172030-95/d70 + +FIGURE A.3/Q.1218 (sheet 2 of 20) + +**SDL for SCF-FSM** + +``` +/* Signal definitions – Third part. Defined in IN CS-1 Recommendations. */ +``` + +``` +/* From SSF or SRF */ +SIGNAL AssistRequestInstructions; +``` + +``` +/* From SSF – DP-specific operations */ +``` + +``` +SIGNAL AnalysedInformation, CollectedInformation, OAnswer, +OCalledPartyBusy, ODisconnect, OMidCall, ONoAnswer, +OriginationAttemptAuthorized, RouteSelectFailure, TAnswer, +TCalledPartyBusy, TDisconnect, TermAttemptAuthorized, TMidCall, +TNoAnswer; +``` + +``` +/* Other operations from SSF */ +SIGNAL InitialDP, EventReportBCSM, ApplyChargingReport, +CallInformationReport, EventNotificationCharging; +``` + +``` +/* Signal definitions – Fourth part. Defined in IN CS-1 Recommendations. */ +``` + +``` +/* To SSF */ +SIGNAL ResetTimer, ApplyCharging, CallInformationRequest, +Cancel, FurnishChargingInformation, RequestNotificationChargingEvent, +RequestReportBCSMEVENT, SendChargingInformation, +AnalyseInformation, CollectInformation, Connect, Continue, ReleaseCall, +SelectFacility, SelectRoute, ConnectToResource, +EstablishTemporaryConnection; +``` + +``` +/* Signal definitions – Fifth part. Operations defined in IN CS-1 Recommendations. */ +``` + +``` +/* To SRF */ +SIGNAL PlayAnnouncement, PromptAndCollectUserInfoInformation; +``` + +``` +/* From SRF */ +SIGNAL ReturnResult_from_PromptAndCollectUserInfoInformation, +SpecializedResourceReport; +``` + +T1 172040-95/d71 + +FIGURE A.3/Q.1218 (sheet 3 of 20) +**SDL for SCF-FSM** + +![State transition diagram for INAP_SCF process. It starts with an initial state leading to 'Idle' (State 1). Transitions include SL_Invocation (e1), Assist_Request_Instructions (E2), and TDPEvent. Actions include Initiate_CallAttempt, SET (NOW + valueB, Tscf_ssf), Process_Input, RESET (Tassist_handoff), SET (NOW + valueA, Tscf_ssf), and TDP type decision (TDP-R, TDP-N).](c6a96f95e328ae9493edffdae3d3cb28_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> SL_Invocation : e1; from service logic + Idle --> Assist_Request_Instructions : E2 from SSF + Idle --> TDPEvent : from SSF + SL_Invocation --> Initiate_CallAttempt : TO SSF + Initiate_CallAttempt --> SET_B : NOW + valueB, Tscf_ssf + SET_B --> Preparing_B : Preparing SSF Instructions + Assist_Request_Instructions --> Process_Input_A + Process_Input_A --> RESET : Tassist_handoff, Stop timer + RESET --> SET_A : NOW + valueA, Tscf_ssf + SET_A --> Preparing_A : Preparing SSF Instructions + TDPEvent --> Process_Input_T + Process_Input_T --> TDP_type : TDP type + TDP_type --> Idle : TDP-N + TDP_type --> SET_A : TDP-R + Note right of Idle : State 1 + Note right of Assist_Request_Instructions : Handoff only + Note right of TDPEvent : One of InitialDP or a DP-specific operation E2 (query) or E3 (notification) from SSF + +``` + +State transition diagram for INAP\_SCF process. It starts with an initial state leading to 'Idle' (State 1). Transitions include SL\_Invocation (e1), Assist\_Request\_Instructions (E2), and TDPEvent. Actions include Initiate\_CallAttempt, SET (NOW + valueB, Tscf\_ssf), Process\_Input, RESET (Tassist\_handoff), SET (NOW + valueA, Tscf\_ssf), and TDP type decision (TDP-R, TDP-N). + +T1 172050-95/d72 + +FIGURE A.3/Q.1218 (sheet 4 of 20) +SDL for SCF-FSM + +![SDL diagram for SCF-FSM process INAP_SCF, sheet 5 of 20. The diagram shows the logic for preparing SSF instructions, handling call and non-call processing instructions, and managing timers and reports.](f7a5075ce066ebe76dd287dccaa15ab9_img.jpg) + +``` + +graph TD + Start(( )) --> State2_1[Preparing SSF Instructions] + State2_1 --- State2_1_Label(State 2.1) + Note1[/* Part of State 2 Processing Query */] -.- State2_1 + + State2_1 --> Input1[/Non-Call_Processing_Instructions +/* e2.1 *//] + State2_1 --> Input2[/Call_Processing_Instruction_Ready_e2.3/] + Note2[Monitoring not required.] -.- Input2 + + Input1 --> Op1[Operation TO SSF +/* Send 1 or more */] + Input2 --> Op1 + + Op1 --> List1["ApplyCharging, +CallInformation_Request, +Cancel (allRequests), +FurnishCharging_Information, +Request_ReportBCSMEVENT, +RequestNotification_ChargingEvent, +ResetTimer, +SendChargingInformation"] + + Op1 --> Dec1{First request to SSF} + Dec1 --| "No" |--> State2_1_End[Preparing SSF Instructions] + Dec1 --| "Yes" |--> Dec2{Was ResetTimer just sent} + Dec2 --| "Yes" |--> State2_1_End + Dec2 --| "No" |--> Task1[SET (NOW + valueA, Tscf_ssf)] + Task1 --> State2_1_End2[Preparing SSF Instructions] + + Op1 --> List2["Cancel (allRequests), +RequestReportBCSMEVENT, +FurnishChargingInformation, +SendChargingInformation"] + List2 --> Op2[Operation TO SSF +/* Send 1 or more */] + + Op2 --> List3["AnalyseInformation, +CollectInformation, +Connect, Continue, +ReleaseCall, +SelectFacility, +SelectRoute"] + List3 --> Op3[Operation TO SSF +/* Send 1 only */] + + Op3 --> Dec3{Report pending} + Dec3 --| "Yes" |--> State2_1_End3[Preparing SSF Instructions] + Dec3 --| "No" |--> Idle([Idle]) + +``` + +SDL diagram for SCF-FSM process INAP\_SCF, sheet 5 of 20. The diagram shows the logic for preparing SSF instructions, handling call and non-call processing instructions, and managing timers and reports. + +T1172060-95/d73 + +FIGURE A.3/Q.1218 (sheet 5 of 20) +**SDL for SCF-FSM** + +![State transition diagram for INAP_SCF process. It starts with a note 'Part of State 2 Processing Query'. The main state is 'Preparing SSF Instructions' (State 2.1). Transitions include 'Call_Processing_Instruction_Ready_e2.4' (with 'Monitoring required'), 'SR_Facilities_Needed_e2.2' (leading to 'Determine Mode'), 'Operation TO SSF / Send 1 or more' (with 'ApplyCharging, CallInformationRequest, FurnishChargingInformation'), 'Operation TO SSF / Send 1 only' (with 'AnalyseInformation, CollectInformation, Connect, Continue, ReleaseCall, SelectFacility, SelectRoute'), and 'RESET (Tscf_ssf) / Stop timer' leading to 'Waiting For Notification Or Request'.](27007a3bb60f941559e7b307f905cdfb_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Preparing SSF Instructions : State 2.1 + Preparing SSF Instructions --> Call_Processing_Instruction_Ready_e2.4 + Preparing SSF Instructions --> SR_Facilities_Needed_e2.2 + Call_Processing_Instruction_Ready_e2.4 --> Operation_TO_SSF_Send_1_or_more + SR_Facilities_Needed_e2.2 --> Determine Mode + Operation_TO_SSF_Send_1_or_more --> Operation_TO_SSF_Send_1_only + Operation_TO_SSF_Send_1_only --> RESET_Tscf_ssf + RESET_Tscf_ssf --> Waiting_For_Notification_Or_Request + + note left of [*] : /* Part of State 2 Processing Query */ + note right of Preparing SSF Instructions : State 2.1 + note left of Call_Processing_Instruction_Ready_e2.4 : Monitoring required + note left of Operation_TO_SSF_Send_1_or_more : ApplyCharging, CallInformationRequest, FurnishChargingInformation + note left of Operation_TO_SSF_Send_1_only : AnalyseInformation, CollectInformation, Connect, Continue, ReleaseCall, SelectFacility, SelectRoute + +``` + +State transition diagram for INAP\_SCF process. It starts with a note 'Part of State 2 Processing Query'. The main state is 'Preparing SSF Instructions' (State 2.1). Transitions include 'Call\_Processing\_Instruction\_Ready\_e2.4' (with 'Monitoring required'), 'SR\_Facilities\_Needed\_e2.2' (leading to 'Determine Mode'), 'Operation TO SSF / Send 1 or more' (with 'ApplyCharging, CallInformationRequest, FurnishChargingInformation'), 'Operation TO SSF / Send 1 only' (with 'AnalyseInformation, CollectInformation, Connect, Continue, ReleaseCall, SelectFacility, SelectRoute'), and 'RESET (Tscf\_ssf) / Stop timer' leading to 'Waiting For Notification Or Request'. + +T1172070-95/d74 + +FIGURE A.3/Q.1218 (sheet 6 of 20) +**SDL for SCF-FSM** + +![State transition diagram for SCF-FSM. It starts with 'Preparing SSF Instructions' leading to three parallel transitions: 'Tscf_ssf / Timer expiry *', 'Ready_for_Queuing_Processing / e2.5 *', and 'Processing_Failure / e2.6 *'. The first leads to 'First expiry' decision; 'Yes' leads to 'ResetTimer TO SSF / Restart Tssf *' then 'SET (NOW + valueA, Tscf_ssf)' then 'Preparing SSF Instructions'; 'No' leads to 'Exception TO SSF' then 'Report pending' decision. 'Report pending' 'Yes' leads to 'Preparing SSF Instructions', 'No' leads to 'Idle'. The second transition leads to 'Preparing SSF Instructions (Q)'. The third leads to 'Exception TO SSF' then 'Report pending' decision; 'Yes' leads to 'Preparing SSF Instructions', 'No' leads to 'Idle'.](4cc77834b75e6e10bed21fde344bd1f4_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Preparing_SSF_Instructions + Preparing_SSF_Instructions --> Tscf_ssf_Timer_expiry : Tscf_ssf / Timer expiry * + Preparing_SSF_Instructions --> Ready_for_Queuing_Processing : Ready_for_Queuing_Processing / e2.5 * + Preparing_SSF_Instructions --> Processing_Failure : Processing_Failure / e2.6 * + Tscf_ssf_Timer_expiry --> First_expiry + First_expiry --> ResetTimer_TO_SSF : Yes / ResetTimer TO SSF / Restart Tssf * + First_expiry --> Exception_TO_SSF_1 : No + ResetTimer_TO_SSF --> SET_NOW_valueA_Tscf_ssf : SET (NOW + valueA, Tscf_ssf) + SET_NOW_valueA_Tscf_ssf --> Preparing_SSF_Instructions_1 + Exception_TO_SSF_1 --> Report_pending_1 + Report_pending_1 --> Preparing_SSF_Instructions_2 : Yes + Report_pending_1 --> Idle_1 : No + Ready_for_Queuing_Processing --> Preparing_SSF_Instructions_3 + Processing_Failure --> Exception_TO_SSF_2 + Exception_TO_SSF_2 --> Report_pending_2 + Report_pending_2 --> Preparing_SSF_Instructions_4 : Yes + Report_pending_2 --> Idle_2 : No + +``` + +State transition diagram for SCF-FSM. It starts with 'Preparing SSF Instructions' leading to three parallel transitions: 'Tscf\_ssf / Timer expiry \*', 'Ready\_for\_Queuing\_Processing / e2.5 \*', and 'Processing\_Failure / e2.6 \*'. The first leads to 'First expiry' decision; 'Yes' leads to 'ResetTimer TO SSF / Restart Tssf \*' then 'SET (NOW + valueA, Tscf\_ssf)' then 'Preparing SSF Instructions'; 'No' leads to 'Exception TO SSF' then 'Report pending' decision. 'Report pending' 'Yes' leads to 'Preparing SSF Instructions', 'No' leads to 'Idle'. The second transition leads to 'Preparing SSF Instructions (Q)'. The third leads to 'Exception TO SSF' then 'Report pending' decision; 'Yes' leads to 'Preparing SSF Instructions', 'No' leads to 'Idle'. + +T1172080-95/d75 + +FIGURE A.3/Q.1218 (sheet 7 of 20) +SDL for SCF-FSM + +/\* +The Queuing FSM is not described in detail in Q.1218. +Part of State 2 Processing Query +\*/ + +![SDL diagram for SCF-FSM showing state transitions for Preparing SSF Instructions (Q) / State 2.2. It includes inputs for Instruction_Ready and Non-Call_Processing_Instructions, leading to timer sets and state returns.](7015953aa0cca0cafa62bfe4305fbc0e_img.jpg) + +``` + +stateDiagram-v2 + state "Preparing SSF Instructions (Q)" as State2_2 + state "State 2.2" as S22 + State2_2 -- S22 + + State2_2 --> Instruction_Ready : From service logic + state Instruction_Ready { + direction LR + input1: Instruction_Ready /* e2.2.1 */ + } + input1 --> Set1 : SET (NOW + valueA, Tscf_ssf) + Set1 --> PrepSSF : Preparing SSF Instructions + + State2_2 --> NonCallProc : e2.2.2 from service logic + state NonCallProc { + direction LR + input2: Non-Call_Processing_Instructions + } + input2 --> OpToSSF : Operation TO SSF /* Send 1 or more */ + OpToSSF --> Set2 : SET (NOW + valueA, Tscf_ssf) + Set2 --> State2_2_Return : Preparing SSF Instructions (Q) + + note right of State2_2 + ApplyCharging, + CallInformationRequest, + FurnishChargingInformation, + RequestReportBCSMEvent, + RequestNotification_ChargingEvent, + ResetTimer, + SendChargingInformation + end note + +``` + +SDL diagram for SCF-FSM showing state transitions for Preparing SSF Instructions (Q) / State 2.2. It includes inputs for Instruction\_Ready and Non-Call\_Processing\_Instructions, leading to timer sets and state returns. + +T1172090-95/d76 + +FIGURE A.3/Q.1218 (sheet 8 of 20) +**SDL for SCF-FSM** + +![State transition diagram for SCF-FSM. The process starts at 'Preparing SSF Instructions (Q)' (State 2.2). It branches into two main paths: 'Tscf_ssf / Timer expiry */' and 'Busy_Line / Trunk / e2.2.3 */'. The 'Tscf_ssf' path leads to a 'First expiry' decision. If 'Yes', it goes to 'ResetTimer TO SSF', then 'SET (NOW + valueA, Tscf_ssf)', and finally to 'Preparing SSF Instructions (Q)'. If 'No', it goes to 'Exception TO SSF', then to a 'Report pending' decision. If 'Yes', it returns to 'Preparing SSF Instructions (Q)'. If 'No', it goes to 'Idle'. The 'Busy_Line' path leads to 'HoldCallIn_Network TO SSF', then 'Furnish_Charging_Information TO SSF' (which initiates call logging), then 'SET (NOW + valueQ, Tq)' (where ValueQ may be customer-specific), then 'SET (NOW + valueC, Tscf_ssf)', and finally to 'Queuing'.](3a0a7168ef04d3e6889925511b52b66d_img.jpg) + +``` +stateDiagram-v2 + [*] --> State22 : Preparing SSF Instructions (Q) + State22 --> Tscf_ssf : Tscf_ssf / Timer expiry */ + State22 --> Busy_Line : Busy_Line / Trunk / e2.2.3 */ + Tscf_ssf --> First_expiry : {First expiry} + First_expiry --> Yes1 : Yes + Yes1 --> ResetTimer : ResetTimer TO SSF + ResetTimer --> SET_A : SET (NOW + valueA, Tscf_ssf) + SET_A --> PreparingSSF : Preparing SSF Instructions (Q) + First_expiry --> No1 : No + No1 --> Exception : Exception TO SSF + Exception --> Report_pending : {Report pending} + Report_pending --> Yes2 : Yes + Yes2 --> PreparingSSF : Preparing SSF Instructions (Q) + Report_pending --> No2 : No + No2 --> Idle : Idle + Busy_Line --> HoldCallIn : HoldCallIn_Network TO SSF + HoldCallIn --> Furnish : Furnish_Charging_Information TO SSF + Furnish --> Logging : Initiates call logging + Furnish --> SET_Q : SET (NOW + valueQ, Tq) + SET_Q --> ValueQ : ValueQ may be customer-specific + SET_Q --> SET_C : SET (NOW + valueC, Tscf_ssf) + SET_C --> Queuing : Queuing +``` + +State transition diagram for SCF-FSM. The process starts at 'Preparing SSF Instructions (Q)' (State 2.2). It branches into two main paths: 'Tscf\_ssf / Timer expiry \*/' and 'Busy\_Line / Trunk / e2.2.3 \*/'. The 'Tscf\_ssf' path leads to a 'First expiry' decision. If 'Yes', it goes to 'ResetTimer TO SSF', then 'SET (NOW + valueA, Tscf\_ssf)', and finally to 'Preparing SSF Instructions (Q)'. If 'No', it goes to 'Exception TO SSF', then to a 'Report pending' decision. If 'Yes', it returns to 'Preparing SSF Instructions (Q)'. If 'No', it goes to 'Idle'. The 'Busy\_Line' path leads to 'HoldCallIn\_Network TO SSF', then 'Furnish\_Charging\_Information TO SSF' (which initiates call logging), then 'SET (NOW + valueQ, Tq)' (where ValueQ may be customer-specific), then 'SET (NOW + valueC, Tscf\_ssf)', and finally to 'Queuing'. + +T1172100-95/d77 + +FIGURE A.3/Q.1218 (sheet 9 of 20) +SDL for SCF-FSM + +![State transition diagram for Queuing state (State 2.2.2) in the INAP_SCF process. Transitions include Tscf_ssf (Timer expiry), Idle_Line / Trunk, Tq (Queuing Timer Expired), and Abort_from_SSF. Actions include ResetTimer TO SSF, SET (NOW + valueC, Tscf_ssf), SET (NOW + valueQ, Tq), and Preparing SSF Instructions. A decision diamond 'Report pending' leads to Queuing (Yes) or Idle (No).](3579d1bdd2ea6e202a6b8e5b151746f9_img.jpg) + +``` +stateDiagram-v2 + [*] --> Queuing + state "Queuing" as Queuing + Queuing --> Tscf_ssf : Tscf_ssf / * Timer expiry - e2.2.4 */ + Queuing --> Idle_Line : Idle_Line / Trunk / * e2.2.5 */ + Queuing --> Tq : Tq / * Queuing Timer Expired e2.2.6 */ + Queuing --> Abort_from_SSF : Abort_from_SSF / * e2.2.7 */ + Tscf_ssf --> ResetTimer : ResetTimer TO SSF + ResetTimer --> SET_C : SET (NOW + valueC, Tscf_ssf) + SET_C --> SET_Q : SET (NOW + valueQ, Tq) + SET_Q --> Queuing + Idle_Line --> Preparing_SSF_Instructions_1 : Preparing SSF Instructions + Tq --> Report_pending : "Report pending" + Report_pending --> Queuing : "Yes" + Report_pending --> Idle : "No" + Abort_from_SSF --> Process_Input : Process_Input + Process_Input --> Preparing_SSF_Instructions_2 : Preparing SSF Instructions +``` + +State transition diagram for Queuing state (State 2.2.2) in the INAP\_SCF process. Transitions include Tscf\_ssf (Timer expiry), Idle\_Line / Trunk, Tq (Queuing Timer Expired), and Abort\_from\_SSF. Actions include ResetTimer TO SSF, SET (NOW + valueC, Tscf\_ssf), SET (NOW + valueQ, Tq), and Preparing SSF Instructions. A decision diamond 'Report pending' leads to Queuing (Yes) or Idle (No). + +T1172110-95/d78 + +FIGURE A.3/Q.1218 (sheet 10 of 20) +SDL for SCF-FSM + +![State transition diagram for INAP_SCF process. It starts at 'Waiting For Notification Or Request' (State 2.3). From here, an 'EDPEvent from SSF' leads to 'Process_Input', then 'SET (NOW + valueB, Tscf_ssf)', and finally 'Preparing SSF Instructions'. A transition 'EDP-R; e2.7' from 'Process_Input' leads to a state with guard 'Not last EDP-N; e2.8'. From this state, an event 'EDPEvent, ApplyChargingReport, CallInformationReport, EventNotificationCharging from SSF' leads to another 'Process_Input' block, which then leads to 'Waiting For Notification Or Request'. From this second 'Waiting' state, a transition 'Last EDP-N; e2.9' leads to a state that receives 'EDPEvent, ApplyChargingReport, CallInformationReport from SSF', followed by 'Process_Input', and finally reaching the 'Idle' state.](98bc1b81b23361c8ca5c0f1635878233_img.jpg) + +``` + +/* +Part of State 2 Processing_Query. +Timer Tscf_ssf not used in this State. + +EDPEvent indicates reception of one of InitialDP or +DP-specific operation from SSF. + +*/ + +``` + +``` + +stateDiagram-v2 + [*] --> Waiting_1: Waiting For Notification Or Request (State 2.3) + Waiting_1 --> EDPEvent_1: EDPEvent /* from SSF */ + EDPEvent_1 --> Process_Input_1: Process_Input + Process_Input_1 --> SET_1: SET (NOW + valueB, Tscf_ssf) + SET_1 --> Preparing_1: Preparing SSF Instructions + Preparing_1 --> EDPEvent_2: EDPEvent /* from SSF */ + EDPEvent_2 --> EDP_R: EDP-R; e2.7 + EDP_R --> Not_last_EDP_N: Not last EDP-N; e2.8 + Not_last_EDP_N --> EDPEvent_3: EDPEvent, ApplyChargingReport, CallInformationReport, EventNotificationCharging /* from SSF */ + EDPEvent_3 --> Process_Input_2: Process_Input + Process_Input_2 --> Waiting_2: Waiting For Notification Or Request + Waiting_2 --> Last_EDP_N: Last EDP-N; e2.9 + Last_EDP_N --> EDPEvent_4: EDPEvent, ApplyChargingReport, CallInformationReport /* from SSF */ + EDPEvent_4 --> Process_Input_3: Process_Input + Process_Input_3 --> Idle: Idle + +``` + +State transition diagram for INAP\_SCF process. It starts at 'Waiting For Notification Or Request' (State 2.3). From here, an 'EDPEvent from SSF' leads to 'Process\_Input', then 'SET (NOW + valueB, Tscf\_ssf)', and finally 'Preparing SSF Instructions'. A transition 'EDP-R; e2.7' from 'Process\_Input' leads to a state with guard 'Not last EDP-N; e2.8'. From this state, an event 'EDPEvent, ApplyChargingReport, CallInformationReport, EventNotificationCharging from SSF' leads to another 'Process\_Input' block, which then leads to 'Waiting For Notification Or Request'. From this second 'Waiting' state, a transition 'Last EDP-N; e2.9' leads to a state that receives 'EDPEvent, ApplyChargingReport, CallInformationReport from SSF', followed by 'Process\_Input', and finally reaching the 'Idle' state. + +T1172120-95/d79 + +FIGURE A.3/Q.1218 (sheet 11 of 20) +SDL for SCF-FSM + +![State transition diagram for the first process instance. It starts with an initial state 'Waiting For Notification Or Request'. Two transitions are available: 'Notification_ or_Request_ Continuing_ Instruction' (triggered by e2.12 from service logic) and 'Monitoring_ Cancel_ Instruction' (triggered by e2.13 from service logic). The 'Notification' transition leads to an action 'Operation TO SSF /* Send 1 only */' which then leads to another 'Waiting For Notification Or Request' state, with a side action of sending various BCSM events. The 'Monitoring' transition leads to an action 'Operation TO SSF /* Send 1 only */' which then leads to an 'Idle' state, with a side action of sending a BCSM event and canceling all requests.](f0d55af3900e87e0b946d125c0702d60_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WaitingForNotificationOrRequest1 : Waiting For Notification Or Request + WaitingForNotificationOrRequest1 --> NotificationOrRequestContinuingInstruction : Notification_ or_Request_ Continuing_ Instruction + NotificationOrRequestContinuingInstruction --> e2_12 : e2.12 from service logic + e2_12 --> OperationTOSSF1 : Operation TO SSF /* Send 1 only */ + OperationTOSSF1 --> WaitingForNotificationOrRequest2 : Waiting For Notification Or Request + OperationTOSSF1 --> RequestReportBCSMEVENT : RequestReportBCSMEVENT, RequestNotification_ Charging Event, SendChargingInformation, FurnishCharging, ApplyCharging + WaitingForNotificationOrRequest1 --> MonitoringCancelInstruction : Monitoring_ Cancel_ Instruction + MonitoringCancelInstruction --> e2_13 : e2.13 from service logic + e2_13 --> OperationTOSSF2 : Operation TO SSF /* Send 1 only */ + OperationTOSSF2 --> Idle1 : Idle + OperationTOSSF2 --> RequestReportBCSMEVENTTOSSF : RequestReport_ BCSMEVENT TO SSF, Cancel (allRequests) + +``` + +State transition diagram for the first process instance. It starts with an initial state 'Waiting For Notification Or Request'. Two transitions are available: 'Notification\_ or\_Request\_ Continuing\_ Instruction' (triggered by e2.12 from service logic) and 'Monitoring\_ Cancel\_ Instruction' (triggered by e2.13 from service logic). The 'Notification' transition leads to an action 'Operation TO SSF /\* Send 1 only \*/' which then leads to another 'Waiting For Notification Or Request' state, with a side action of sending various BCSM events. The 'Monitoring' transition leads to an action 'Operation TO SSF /\* Send 1 only \*/' which then leads to an 'Idle' state, with a side action of sending a BCSM event and canceling all requests. + +![State transition diagram for the second process instance. It starts with an initial state 'Waiting For Notification Or Request'. Two transitions are available: 'Release_ Call_ Instruction_ e2.14' (triggered by 'Report still pending e2.14 from service logic') and 'Release_ Call_ Instruction_ e2.15' (triggered by 'No reports pending. e2.15 from service logic'). The 'Release_ e2.14' transition leads to an action 'ReleaseCall TO SSF' which then leads to another 'Waiting For Notification Or Request' state. The 'Release_ e2.15' transition leads to an action 'ReleaseCall TO SSF' which then leads to an 'Idle' state.](a1c4b7e73d6dd20eea74f7d6c116cfa5_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WaitingForNotificationOrRequest3 : Waiting For Notification Or Request + WaitingForNotificationOrRequest3 --> ReleaseCallInstructione2_14 : Release_ Call_ Instruction_ e2.14 + ReleaseCallInstructione2_14 --> ReportStillPending : Report still pending e2.14 from service logic + ReportStillPending --> ReleaseCallTOSSF3 : ReleaseCall TO SSF + ReleaseCallTOSSF3 --> WaitingForNotificationOrRequest4 : Waiting For Notification Or Request + WaitingForNotificationOrRequest3 --> ReleaseCallInstructione2_15 : Release_ Call_ Instruction_ e2.15 + ReleaseCallInstructione2_15 --> NoReportsPending : No reports pending. e2.15 from service logic + NoReportsPending --> ReleaseCallTOSSF4 : ReleaseCall TO SSF + ReleaseCallTOSSF4 --> Idle2 : Idle + +``` + +State transition diagram for the second process instance. It starts with an initial state 'Waiting For Notification Or Request'. Two transitions are available: 'Release\_ Call\_ Instruction\_ e2.14' (triggered by 'Report still pending e2.14 from service logic') and 'Release\_ Call\_ Instruction\_ e2.15' (triggered by 'No reports pending. e2.15 from service logic'). The 'Release\_ e2.14' transition leads to an action 'ReleaseCall TO SSF' which then leads to another 'Waiting For Notification Or Request' state. The 'Release\_ e2.15' transition leads to an action 'ReleaseCall TO SSF' which then leads to an 'Idle' state. + +T1172130-95/d80 + +FIGURE A.3/Q.1218 (sheet 12 of 20) +SDL for SCF-FSM + +/\* +Part of State 3 +Routing To Resource. +\*/ + +![SDL diagram for SCF-FSM State 3.1 'Determine Mode'. The process branches into three paths: 1) Instruction_Ready_Relay leads to ConnectTo_Resource TO SSF, then Operation TO SSF (Send 1 only), then SET (NOW + valueD, Tscf_ssf), ending in Waiting For Response From SRF. 2) Assist_Needed leads to Establish_Temporary_Connection TO SSF, then SET (NOW + valueE, Tassist_handoff), then SET (NOW + valueC, Tscf_ssf), ending in Waiting For Assist Request Instructions. 3) Hand_off_Needed leads to Operation TO SSF (Send 1 only), then SET (NOW + valueE, Tassist_handoff), ending in Idle state. Side notes include 'Play_Announcement, PromptAnd_CollectUser_Information' linked to the first path's operation, 'Connect, SelectRoute' linked to the third path's operation, and a note on the Idle state: 'If report pending, is it sent? SCSM must go to Idle state'.](6b89ce8be0091cec81aaaad513a8b93f_img.jpg) + +``` + +stateDiagram-v2 + state "Determine Mode" as DM + state "Instruction_Ready_Relay* e3.1 */" as IRR + state "Assist_Needed/* e3.2 */" as AN + state "Hand_off_Needed/* e3.3 */" as HON + + [*] --> DM : State 3.1 + DM --> IRR + DM --> AN + DM --> HON + + IRR --> ConnectTo_Resource_TO_SSF + ConnectTo_Resource_TO_SSF --> Operation_TO_SSF_1 : /* Send 1 only */ + Operation_TO_SSF_1 --> SET_D : SET (NOW + valueD, Tscf_ssf) + SET_D --> Waiting_For_Response_From_SRF + + AN --> Establish_Temporary_Connection_TO_SSF + Establish_Temporary_Connection_TO_SSF --> SET_E_1 : SET (NOW + valueE, Tassist_handoff) + SET_E_1 --> SET_C : SET (NOW + valueC, Tscf_ssf) + SET_C --> Waiting_For_Assist_Request_Instructions + + HON --> Operation_TO_SSF_2 : /* Send 1 only */ + Operation_TO_SSF_2 --> SET_E_2 : SET (NOW + valueE, Tassist_handoff) + SET_E_2 --> Idle + + note left of Operation_TO_SSF_1 : Play_Announcement, PromptAnd_CollectUser_Information + note right of Operation_TO_SSF_2 : Connect, SelectRoute + note right of Idle : If report pending, is it sent? SCSM must go to Idle state + +``` + +SDL diagram for SCF-FSM State 3.1 'Determine Mode'. The process branches into three paths: 1) Instruction\_Ready\_Relay leads to ConnectTo\_Resource TO SSF, then Operation TO SSF (Send 1 only), then SET (NOW + valueD, Tscf\_ssf), ending in Waiting For Response From SRF. 2) Assist\_Needed leads to Establish\_Temporary\_Connection TO SSF, then SET (NOW + valueE, Tassist\_handoff), then SET (NOW + valueC, Tscf\_ssf), ending in Waiting For Assist Request Instructions. 3) Hand\_off\_Needed leads to Operation TO SSF (Send 1 only), then SET (NOW + valueE, Tassist\_handoff), ending in Idle state. Side notes include 'Play\_Announcement, PromptAnd\_CollectUser\_Information' linked to the first path's operation, 'Connect, SelectRoute' linked to the third path's operation, and a note on the Idle state: 'If report pending, is it sent? SCSM must go to Idle state'. + +T1172140-95/d81 + +FIGURE A.3/Q.1218 (sheet 13 of 20) +**SDL for SCF-FSM** + +/\* +Part of State 3 +Routing To Resource. +Timer Tscf\_ssf expiry is not +explicitly shown in Q.1218. +\*/ + +![State transition diagram for INAP_SCF process. It starts with 'Determine Mode' (State 3.1), followed by 'Tscf_ssf / Timer expiry' event. A decision 'First expiry' follows. 'No' leads to 'Exception TO SSF' then 'Report pending' decision. 'Yes' leads to 'ResetTimer TO SSF / Restart Tssf' then 'SET (NOW + valueD, Tscf_ssf)' then 'Determine Mode'. 'Report pending' 'Yes' leads to 'Determine Mode', 'No' leads to 'Idle'.](dd3dd734369fe3ecf3bd85f59e5416f0_img.jpg) + +``` +stateDiagram-v2 + [*] --> DetermineMode1 : Determine Mode + DetermineMode1 --> Tscf_ssf : Tscf_ssf / Timer expiry + Tscf_ssf --> FirstExpiry : First expiry + FirstExpiry --> ExceptionTOSSF : No + FirstExpiry --> ResetTimerTOSSF : Yes + ExceptionTOSSF --> ReportPending : Report pending + ReportPending --> DetermineMode2 : Yes + ReportPending --> Idle : No + ResetTimerTOSSF --> SET : SET (NOW + valueD, Tscf_ssf) + SET --> DetermineMode3 : Determine Mode +``` + +State transition diagram for INAP\_SCF process. It starts with 'Determine Mode' (State 3.1), followed by 'Tscf\_ssf / Timer expiry' event. A decision 'First expiry' follows. 'No' leads to 'Exception TO SSF' then 'Report pending' decision. 'Yes' leads to 'ResetTimer TO SSF / Restart Tssf' then 'SET (NOW + valueD, Tscf\_ssf)' then 'Determine Mode'. 'Report pending' 'Yes' leads to 'Determine Mode', 'No' leads to 'Idle'. + +T1172150-95/d82 + +FIGURE A.3/Q.1218 (sheet 14 of 20) +SDL for SCF-FSM + +![SDL diagram for SCF-FSM showing transitions from 'Waiting For Assist Request Instructions' (State 3.2). It details paths for assisting SSF relay, direct SCF-SRF case, and timer expiry, involving operations like Process_Input, RESET Tassist/handoff, ConnectTo_Resource, and Play_Announcement, leading to states like 'Waiting For Response From SRF'.](8661a3b6438f6772a78a59f6a9224409_img.jpg) + +/\* +Part of State 3 +Routing To Resource +\*/ + +``` + +stateDiagram-v2 + state "Waiting For Assist Request Instructions" as State32 + state "Waiting For Response From SRF" as WaitingSRF + state "Waiting For Assist Request Instructions" as WaitingAssist + + [*] --> State32 : State 3.2 + + State32 --> Assist1 : e3.4 from assisting SSF relay / Assist_Request_Instructions + State32 --> Assist2 : Assist_Request_Instructions + State32 --> DirectCase : e3.5 Direct SCF-SRF case + State32 --> TimerExpiry : Tscf_ssf /* e3.6 Timer expiry */ + + Assist1 --> ProcessInput1 : Process_Input + ProcessInput1 --> ResetTassist : RESET Tassist/handoff /* Stop timer */ + ResetTassist --> ConnectToSSF : ConnectTo_Resource TO SSF + ConnectToSSF --> OperationSSF : Operation TO SSF + + DirectCase --> PlayPrompt : Play_Announcement, PromptAnd_CollectUser_Information + PlayPrompt --> OperationSSF + + OperationSSF --> SetTimer1 : SET (NOW + valueD, Tscf_ssf) + SetTimer1 --> WaitingSRF + + Assist2 --> ProcessInput2 : Process_Input + ProcessInput2 --> OperationSRF : Operation TO SRF + OperationSRF --> SetTimer2 : SET (NOW + valueD, Tscf_ssf) + SetTimer2 --> WaitingAssist + + TimerExpiry --> ResetTimerSSF : ResetTimer TO SSF /* Restart Tssf */ + ResetTimerSSF --> SetTimer3 : SET (NOW + valueD, Tscf_ssf) + SetTimer3 --> WaitingAssist + +``` + +SDL diagram for SCF-FSM showing transitions from 'Waiting For Assist Request Instructions' (State 3.2). It details paths for assisting SSF relay, direct SCF-SRF case, and timer expiry, involving operations like Process\_Input, RESET Tassist/handoff, ConnectTo\_Resource, and Play\_Announcement, leading to states like 'Waiting For Response From SRF'. + +T1172160-95/d83 + +FIGURE A.3/Q.1218 (sheet 15 of 20) +**SDL for SCF-FSM** + +/\* +Part of State 3 +Routing To Resource +\*/ + +![State transition diagram for INAP_SCF process. It starts with 'Waiting For Assist Request Instructions' (oval), leading to a split. The left path is 'Tassist_handoff /* e3.7 Timer expiry */' (parallelogram) followed by 'Disconnect_ Forward_ Connection TO SSF' (parallelogram). The right path is 'Initial_SSF_ Failure /* E3.8 from SSF */' (parallelogram) followed by 'Process_Input' (rectangle). Both paths merge into 'SET (NOW + valueA, Tscf_ssf)' (rectangle), which then leads to 'Preparing SSF Instructions' (oval).](5d18e168996dc3ae3f595f348261e80e_img.jpg) + +``` +graph TD; S1([Waiting For Assist Request Instructions]) --> Split(( )); Split --> T1[/Tassist_handoff +/* e3.7 +Timer expiry *//]; Split --> T2[/Initial_SSF_ Failure +/* E3.8 from +SSF *//]; T1 --> T3[/Disconnect_ Forward_ +Connection TO SSF/]; T2 --> T4[Process_Input]; T3 --> Merge(( )); T4 --> Merge; Merge --> T5[SET (NOW + valueA, +Tscf_ssf)]; T5 --> S2([Preparing SSF Instructions]); +``` + +State transition diagram for INAP\_SCF process. It starts with 'Waiting For Assist Request Instructions' (oval), leading to a split. The left path is 'Tassist\_handoff /\* e3.7 Timer expiry \*/' (parallelogram) followed by 'Disconnect\_ Forward\_ Connection TO SSF' (parallelogram). The right path is 'Initial\_SSF\_ Failure /\* E3.8 from SSF \*/' (parallelogram) followed by 'Process\_Input' (rectangle). Both paths merge into 'SET (NOW + valueA, Tscf\_ssf)' (rectangle), which then leads to 'Preparing SSF Instructions' (oval). + +T1172170-95/d84 + +FIGURE A.3/Q.1218 (sheet 16 of 20) +**SDL for SCF-FSM** + +``` + +/* +Part of State 4 User Interaction +Output operations to SRF do not distinguish +between direct SCF-SRF and SSF relay cases. + +*/ + +``` + +![SDL diagram for SCF-FSM process INAP_SCF, sheet 17 of 20. The diagram shows the logic for 'Waiting For Response From SRF' (State 4.1). It handles inputs like 'More_Information_Needed' and 'Continue_SCF_Processing', performs operations like 'Play_Announcement', processes input, and branches based on whether a response is final to either return to waiting or prepare SSF instructions.](1ba9045eb6dc22039a16b92b1427e696_img.jpg) + +``` + +stateDiagram-v2 + state "Waiting For Response From SRF" as State4_1 + state "Waiting For Response From SRF" as State4_1_Return + state "Preparing SSF Instructions" as PrepSSF + + [*] --> State4_1 : State 4.1 + + State4_1 --> MoreInfo : More_Information_Needed / e4.1 */ + MoreInfo --> OpToSRF : Operation TO SRF /* Send 1 only */ + OpToSRF --> PlayAnn : Play_Announcement, PromptAnd_CollectUser_Information + PlayAnn --> ProcInput + + State4_1 --> ContinueSCF : Continue_SCF_Processing / e4.3 + ContinueSCF --> DisconnSSF : Disconnect_Forward_Connection TO SSF + DisconnSSF --> SetValueB + + state "e4.3; SCF-initiated disconnect" as e43 + e43 --> ContinueSCF + + state "E4.2 and E4.2' from SRF; SRF-initiated disconnect if final" as E42 + E42 --> ProcInput + + state "ReturnResult_from_PromptAndCollect_UserInformation, SpecializedResource_Report" as RetRes + RetRes --> ProcInput + + ProcInput --> FinalDec : Process_Input + state FinalDec <> + note right of FinalDec : Final response + + FinalDec --> SetValueD : No + FinalDec --> SetValueB : Yes + + state "SET (NOW + valueD, Tscf_ssf)" as SetValueD + state "SET (NOW + valueB, Tscf_ssf)" as SetValueB + + SetValueD --> State4_1_Return + SetValueB --> PrepSSF + +``` + +SDL diagram for SCF-FSM process INAP\_SCF, sheet 17 of 20. The diagram shows the logic for 'Waiting For Response From SRF' (State 4.1). It handles inputs like 'More\_Information\_Needed' and 'Continue\_SCF\_Processing', performs operations like 'Play\_Announcement', processes input, and branches based on whether a response is final to either return to waiting or prepare SSF instructions. + +T1172180-95/d85 + +FIGURE A.3/Q.1218 (sheet 17 of 20) +**SDL for SCF-FSM** + +``` + +/* +Part of State 4 User Interaction +Output operations to SRF do not distinguish +between direct SCF-SRF and SSF relay cases. +*/ + +``` + +![SDL diagram for SCF-FSM showing transitions from 'Waiting For Response From SRF' state based on three inputs: e4.3', e4.3'', and Failure_from_SRF.](1f94fa97697122830275fb74bbe6f718_img.jpg) + +``` + +stateDiagram-v2 + state "Waiting For Response From SRF" as State1 + state "Preparing SSF Instructions" as State2 + + [*] --> State1 + + State1 --> Input1: e4.3'; SRF initiated disconnect + Input1 --> Output1: Continue_ SCF_ Processing_ e4.3' + Output1 --> Task1: Operation TO SRF /* Send 1 only */ + Task1 --> Task2: Play_ Announcement, PromptAnd_ CollectUser_ Information + Task2 --> Task3: SET (NOW + valueD, Tscf_ssf) + Task3 --> State1 + + State1 --> Input2: e4.3''; SRF initiated disconnect + Input2 --> Output2: Continue_ SCF_ Processing_ e4.3'' + Output2 --> Task4: Play_ Announcement TO SRF + Task4 --> Task5: SET (NOW + valueA, Tscf_ssf) + Task5 --> State2 + + State1 --> Input3: Failure_ from_SRF /* E4.5 from SRF */ + Input3 --> Proc1: Process_Input + Proc1 --> Task6: SET (NOW + valueD, Tscf_ssf) + Task6 --> State1 + +``` + +SDL diagram for SCF-FSM showing transitions from 'Waiting For Response From SRF' state based on three inputs: e4.3', e4.3'', and Failure\_from\_SRF. + +T1172190-95/d86 + +FIGURE A.3/Q.1218 (sheet 18 of 20) +**SDL for SCF-FSM** + +/\* +Part of State 4 User Interaction +\*/ + +![State transition diagram for INAP_SCF process. It starts with 'Waiting For Response From SRF', leading to a choice between 'Tscf_ssf' (timer expiry), 'Cancellation_Required', and 'Non-Call_Processing_Instructions'. Each path leads to specific actions like resetting timers, canceling to SSF, or sending operations to SSF, eventually leading to 'SET (NOW + valueD, Tscf_ssf)' and back to 'Waiting For Response From SRF'. A side note 'e4.8' lists charging-related information.](848818ad9dfb7f32f050c0d9a177df89_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WaitingForResponseFromSRF1 : Waiting For Response From SRF + state "Waiting For Response From SRF" as WaitingForResponseFromSRF1 + WaitingForResponseFromSRF1 --> Tscf_ssf : Tscf_ssf / e4.6 Timer expiry + WaitingForResponseFromSRF1 --> Cancellation_Required : Cancellation_Required / e4.7 + WaitingForResponseFromSRF1 --> Non-Call_Processing_Instructions : Non-Call_Processing_Instructions + Tscf_ssf --> ResetTimerTOSSF : ResetTimer TO SSF / Initiating or assisting SSF + Cancellation_Required --> CancelTOAssistSSF : Cancel TO Assist_SSF + CancelTOAssistSSF --> ToSRFinDirectCase : To SRF in direct case + Non-Call_Processing_Instructions --> OperationTOSSF : Operation TO SSF / Send 1 or more + ResetTimerTOSSF --> SET : SET (NOW + valueD, Tscf_ssf) + CancelTOAssistSSF --> SET + ToSRFinDirectCase --> SET + OperationTOSSF --> SET + SET --> WaitingForResponseFromSRF2 : Waiting For Response From SRF + state "Waiting For Response From SRF" as WaitingForResponseFromSRF2 + +``` + +e4.8 + +ApplyCharging, +FurnishCharging\_Information, +RequestNotification\_ChargingEvent, +SendCharging\_Information + +State transition diagram for INAP\_SCF process. It starts with 'Waiting For Response From SRF', leading to a choice between 'Tscf\_ssf' (timer expiry), 'Cancellation\_Required', and 'Non-Call\_Processing\_Instructions'. Each path leads to specific actions like resetting timers, canceling to SSF, or sending operations to SSF, eventually leading to 'SET (NOW + valueD, Tscf\_ssf)' and back to 'Waiting For Response From SRF'. A side note 'e4.8' lists charging-related information. + +T1172200-95/d87 + +FIGURE A.3/Q.1218 (sheet 19 of 20) +SDL for SCF-FSM + +/\* CallInformationReport and ApplyChargingReport can be received in any state except Idle. +If processing has been completed and SCSM is only awaiting receipt of report, then SCSM goes to Idle, else it remains in the previous state. +\*/ + +![State transition diagram for PROCESS INAP_SCF. It starts with an initial state '* Idle' leading to a transition 'Call_Information_Report' (or 'ApplyCharging Report. From SSF'). This leads to a process block 'Process_Input'. A decision diamond 'Processing complete' follows. If 'Yes', it goes to state 'Idle'. If 'No', it goes to a state '-' which returns to the previous state.](c747f23d3c916cb48bebaa14372b8d75_img.jpg) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Call_Information_Report : Any state except Idle + Call_Information_Report --> Process_Input : or ApplyCharging Report. From SSF + Process_Input --> Processing_complete{Processing complete} + Processing_complete --> Idle : Yes + Processing_complete --> PreviousState[-] : No + PreviousState --> PreviousState : Return to previous state +``` + +State transition diagram for PROCESS INAP\_SCF. It starts with an initial state '\* Idle' leading to a transition 'Call\_Information\_Report' (or 'ApplyCharging Report. From SSF'). This leads to a process block 'Process\_Input'. A decision diamond 'Processing complete' follows. If 'Yes', it goes to state 'Idle'. If 'No', it goes to a state '-' which returns to the previous state. + +T1172210-95/d88 + +FIGURE A.3/Q.1218 (sheet 20 of 20) +**SDL for SCF-FSM** + +``` +/* +SRF SDLs for INAP. +Based on Q.1218, Section 3.1.3.4, "The SRSM". + +Version 2.0 January 1995 +*/ +``` + +![SDL Procedure Call symbol for Process_Input](18597cad6e1aa6d57eeda7f0736b28b5_img.jpg) + +Process\_Input + +SDL Procedure Call symbol for Process\_Input + +``` +/* Data declarations */ + +Timer Tsrf; +``` + +``` +/* +``` + +A locally defined procedure Process\_Input is used to indicate analysis of an input from an external source to determine whether service logic processing (outside the SRF FSM) is required. + +No details of possible processing in the procedure are given, as it is intended only to indicate that processing may be required, not its exact nature. + +The output Send\_PAPC\_Result TO SCF sends the appropriate SpecializedResourceReport or ReturnResult\_from\_PromptAndCollectUserInfo operation to the SCF (including error reports). + +``` +*/ +``` + +T1172220-95/d89 + +FIGURE A.4/Q.1218 (sheet 1 of 7) +**SDL for SRF-FSM** + +``` +/* Signal definitions – First part. +``` + +Internal indications which are defined in the IN CS-1 Recommendations as event names, not operations. Names are therefore local names only. + +``` +*/ +``` + +``` +/* From SRF service logic */ +``` + +``` +SIGNAL Assist_Request_Instructions_Needed, SRF_Report_to_SCF; +PAPC_Cancelled_to_SCF, Cancel_Error_to_SCF, Disconnect_to_SSF; +``` + +``` +/* Signal definitions – Second part. +``` + +Internal indications which are defined in the IN CS-1 Recommendations as event names, not operations. Names are therefore local names only. + +``` +/* From SSF */ +``` + +``` +SIGNAL Connect_Request_from_SSF, Connection_Released_from_SSF; +``` + +``` +/* Signal definitions – Third part. Operations defined in IN CS-1 +Recommendations. +``` + +``` +*/ +``` + +``` +/* From SCF */ +``` + +``` +SIGNAL PlayAnnouncement, PromptAndCollectUserInfo, Cancel; +``` + +``` +/* To SCF */ +``` + +``` +SIGNAL AssistRequestInstructions; +``` + +T1172230-95/d90 + +FIGURE A.4/Q.1218 (sheet 2 of 7) + +**SDL for SRF-FSM** + +![State transition diagram for SRF-FSM showing states Idle and Connected, and transitions Connect_Request_from_SSF, Process_Input, and SET (NOW + value, Tsrf).](191a6d549000e91eaad1a606bf90aea0_img.jpg) + +The diagram is a state transition diagram for the SRF-FSM. It consists of the following elements: + +- States:** + - An initial state represented by an oval at the top. + - An **Idle** state represented by a double-oval shape, with a dashed line pointing to a box labeled **State 1**. + - A **Connected** state represented by a double-oval shape at the bottom. +- Transitions:** + - A transition from the **Idle** state to the **Connected** state, triggered by **Connect\_Request\_from\_SSF** (represented by a chevron shape). This transition is associated with the action **E1; bearer connection request** (shown in a box to the right). + - A transition from the **Connected** state back to the **Idle** state, triggered by **Process\_Input** (represented by a double rectangle shape). + - A self-loop transition on the **Connected** state, triggered by **SET (NOW + value, Tsrf)** (represented by a rectangle shape). + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Connected : Connect_Request_from_SSF (E1; bearer connection request) + Connected --> Idle : Process_Input + Connected --> Connected : SET (NOW + value, Tsrf) +``` + +State transition diagram for SRF-FSM showing states Idle and Connected, and transitions Connect\_Request\_from\_SSF, Process\_Input, and SET (NOW + value, Tsrf). + +T1172240-95/d91 + +FIGURE A.4/Q.1218 (sheet 3 of 7) +**SDL for SRF-FSM** + +![SDL diagram for SRF-FSM showing transitions from Connected state to Idle or User Interaction states based on various inputs like Connection_Released, Timer expiry, or PromptAndCollect instructions.](491842c5803069f249bb83ce00725ad4_img.jpg) + +``` + +stateDiagram-v2 + state "Connected" as Connected + state "State 2" as State2 + Connected -- State2 + + Connected --> Process_Input_1 : Connection_Released_from_SSF /* E3 */ + Process_Input_1 --> Idle + + Connected --> Disconnect_SSF : Tsrf /* Timer expiry; e4 */ + Disconnect_SSF --> Idle : "Initiate bearer channel disconnect to SSF" + + Connected --> AssistRequest : AssistRequest_Instructions_Needed /* e5 */ + AssistRequest --> Set_Tsrf : AssistRequest_Instructions TO SCF + Set_Tsrf --> Connected : SET (NOW + value, Tsrf) + + state "Idle" as Idle + + [*] --> Process_Input_2 : PromptAndCollect_UserInformation, PlayAnnouncement /* E2 from SCF */ + Process_Input_2 --> Reset_Tsrf : Process_Input + Reset_Tsrf --> User_Interaction : RESET (Tsrf) /* Stop timer */ + + state "User Interaction" as User_Interaction + +``` + +SDL diagram for SRF-FSM showing transitions from Connected state to Idle or User Interaction states based on various inputs like Connection\_Released, Timer expiry, or PromptAndCollect instructions. + +T1172250-95/d92 + +FIGURE A.4/Q.1218 (sheet 4 of 7) +SDL for SRF-FSM + +![SDL diagram for SRF-FSM process INAP_SRF, sheet 5 of 7. It shows transitions from State 3 (User Interaction) triggered by three different inputs: PromptAndCollect_UserInformation/PlayAnnouncement, Cancel, and SRF_Report_to_SCF. Each path performs specific tasks or procedure calls before returning to the User Interaction state.](3cd2dad2cfb3907d8e97939c13ccd132_img.jpg) + +``` + +stateDiagram-v2 + state "User Interaction" as State3 + note right of State3 : State 3 + + State3 --> PromptInput + State3 --> CancelInput + State3 --> ReportInput + + state PromptInput <> + note right of PromptInput : PromptAndCollect_ +UserInformation, +PlayAnnouncement +/* e5 from SCF */ + PromptInput --> ProcessInput1 : Process_Input + ProcessInput1 --> ResetTask : RESET (Tsrf) +/* Stop timer */ + ResetTask --> State3_End1 : User Interaction + + state CancelInput <> + note right of CancelInput : Cancel /* +From SCF; +E6 */ + CancelInput --> ProcessInput2 : Process_Input + ProcessInput2 --> State3_End2 : User Interaction + + state ReportInput <> + note right of ReportInput : SRF_Report_ +to_SCF /* +e7 */ + ReportInput --> SendOutput : Send_PAPC_ +Result TO SCF + SendOutput --> SetTask : SET (NOW + +value, Tsrf) + SetTask --> State3_End3 : User Interaction + +``` + +SDL diagram for SRF-FSM process INAP\_SRF, sheet 5 of 7. It shows transitions from State 3 (User Interaction) triggered by three different inputs: PromptAndCollect\_UserInformation/PlayAnnouncement, Cancel, and SRF\_Report\_to\_SCF. Each path performs specific tasks or procedure calls before returning to the User Interaction state. + +T1172260-95/d93 + +FIGURE A.4/Q.1218 (sheet 5 of 7) +**SDL for SRF-FSM** + +![State transition diagram for PROCESS INAP_SRF. It starts with a 'User Interaction' state, leading to three transitions: 'PAPC_Cancelled_to_SCF / e8 *', 'Cancel_Error_to_SCF / e9 *', and 'Connection_Released_from_SSF / E10 *'. The first two lead to 'Send_PAPC_Result_to_SCF' messages ('Cancel OK' and 'Task refused' respectively), which then lead to a 'SET (NOW + value, Tsrf)' action and back to 'User Interaction'. The third transition leads to 'Process_Input' and then to an 'Idle' state.](9d354ffb3f05c847e46b22f0c3b7ebff_img.jpg) + +``` +stateDiagram-v2 + [*] --> User_Interaction + User_Interaction --> PAPC_Cancelled_to_SCF : PAPC_Cancelled_to_SCF / e8 * + User_Interaction --> Cancel_Error_to_SCF : Cancel_Error_to_SCF / e9 * + User_Interaction --> Connection_Released_from_SSF : Connection_Released_from_SSF / E10 * + PAPC_Cancelled_to_SCF --> Send_PAPC_Result_to_SCF_1 : Send_PAPC_Result_to_SCF / Cancel OK * + Cancel_Error_to_SCF --> Send_PAPC_Result_to_SCF_2 : Send_PAPC_Result_to_SCF / Task refused * + Send_PAPC_Result_to_SCF_1 --> SET : SET (NOW + value, Tsrf) + Send_PAPC_Result_to_SCF_2 --> SET + SET --> User_Interaction + Connection_Released_from_SSF --> Process_Input + Process_Input --> Idle +``` + +State transition diagram for PROCESS INAP\_SRF. It starts with a 'User Interaction' state, leading to three transitions: 'PAPC\_Cancelled\_to\_SCF / e8 \*', 'Cancel\_Error\_to\_SCF / e9 \*', and 'Connection\_Released\_from\_SSF / E10 \*'. The first two lead to 'Send\_PAPC\_Result\_to\_SCF' messages ('Cancel OK' and 'Task refused' respectively), which then lead to a 'SET (NOW + value, Tsrf)' action and back to 'User Interaction'. The third transition leads to 'Process\_Input' and then to an 'Idle' state. + +T1172270-95/d94 + +FIGURE A.4/Q.1218 (sheet 6 of 7) +SDL for SRF-FSM + +![State transition diagram for SRF-FSM. It starts at 'User Interaction' (oval), leading to a horizontal line. From this line, a dashed arrow points to 'SRF-initiated disconnection' (rectangle). The main path goes to a junction. From the junction, one path goes left through 'Disconnect_to_SSF /* e11 */' (parallelogram) to 'Send_PAPC_Result_to_SCF /* End OK */' (parallelogram). The other path from the junction goes right through 'Tsr /* e12; timer expiry */' (parallelogram). Both paths converge at a junction leading to 'Initiate bearer channel disconnect to SSF' (rectangle), which then leads to 'Idle' (oval).](09379cbeb48f1fb8ed18b60f336448a4_img.jpg) + +``` +graph TD; Start([User Interaction]) --> Junction1(( )); Junction1 -.-> SRF[SRF-initiated disconnection]; Junction1 --> Junction2(( )); Junction2 --> D[Disconnect_to_SSF /* e11 */]; D --> S[Send_PAPC_Result_to_SCF /* End OK */]; Junction2 --> T[Tsr /* e12; timer expiry */]; S --> Junction3(( )); T --> Junction3; Junction3 --> I[Initiate bearer channel disconnect to SSF]; I --> End([Idle]); +``` + +State transition diagram for SRF-FSM. It starts at 'User Interaction' (oval), leading to a horizontal line. From this line, a dashed arrow points to 'SRF-initiated disconnection' (rectangle). The main path goes to a junction. From the junction, one path goes left through 'Disconnect\_to\_SSF /\* e11 \*/' (parallelogram) to 'Send\_PAPC\_Result\_to\_SCF /\* End OK \*/' (parallelogram). The other path from the junction goes right through 'Tsr /\* e12; timer expiry \*/' (parallelogram). Both paths converge at a junction leading to 'Initiate bearer channel disconnect to SSF' (rectangle), which then leads to 'Idle' (oval). + +T1172280-95/d95 + +FIGURE A.4/Q.1218 (sheet 7 of 7) +**SDL for SRF-FSM** + +## Annex B + +### Description of the SCSM (SDF-related states) and of the SDSM + +(This annex forms an integral part of this Recommendation) + +This description includes a text and an SDL description. + +#### B.1 Description of the Process SCSM + +When the Application process at the SCF side decides to create a binding between an SCF and the SDF on behalf of the end user, then a SCSM process instance shall be created by the application process. Two processes occur in the course of establishing a binding namely authentication and version negotiation. Authentication shall be concerned with the user and the directory. The standard shall provide the following methods of authentication techniques namely: + +- the use of passwords; or +- the use of protected passwords. + +When a SCSM process instance is created it shall be put in the "Idle" state. + +##### B.1.1 State 1 – "Idle" + +###### B.1.1.1 Normal procedures + +When the SCSM process instance is in the state "Idle" and a need of the application process to interrogate an SDF exists, a Bind.inv primitive shall be sent by the SCF Application process. The bind argument shall be stored and a timer $T_1$ shall be started. This event shall cause a transition to the state "Wait\_for\_Subsequent\_Requests" and other events are awaited. The timer $T_1$ is started in order to supervise the state "Wait\_for\_Subsequent\_Requests" and will ensure that the SCSM process is deleted when the communication with the application process is interrupted. The Dialogue handling services of TC shall be used to support the DirectoryBind operation and to trigger the sending of the associated APDU to the peer SDF process instance. + +###### B.1.1.2 Exceptional procedures + +None identified. + +##### B.1.2 State 2 – "Wait for subsequent requests" + +###### B.1.2.1 Normal procedures + +In this state, subsequent operations to be sent with the Bind operation (in the same message) to the SDF are expected. The following normal events are considered in this state: + +- When a Op.inv primitive is received from the application process a component handling primitive TC-INVOKED req shall be sent to the TC and the process instance shall return to the "Wait\_for\_Subsequent\_Requests" state. This operation shall be sent to the SDF in a message containing a Bind argument. The SCSM process instance shall wait for a Delimiter primitive response from the application process. The operations to be carried by the TC-INVOKED req primitive can be a search, modifyEntry, addEntry or removeEntry. +- When a Delimiter primitive is received from the application process the SCSM process instance shall stop the timer $T_1$ , shall start timer $T_2$ and shall send a dialogue handling primitive TC-BEGIN req to TC. Once the TC-BEGIN req. primitive is received by the TC, a message containing the Bind argument and other operation arguments if any shall be sent to the SDF. This event shall cause the SCSM process instance to transit to the State 3 "Wait\_for\_Bind\_result". The SCSM process instance shall wait for the response from the SDF. The timer $T_2$ is started in order to supervise the state "Wait\_for\_Bind\_result" and will ensure that the SCSM process is deleted when the communication with the peer SDF application process is interrupted. + +![SCF-SDF Model diagram showing interactions between SCF Application, SDF Application, SCSM, SDSM, and TCAP.](600c8f9d34f98c395e29c266aebfbd8e_img.jpg) + +Block SCF\_SDF PAGE 1 (1) + +``` + +graph TD + subgraph Block_SCF_SDF + SCF[SCF Application] -->|Bind.res, Bind.err, U_Abort, Process_error, Op.res, Op.err, Op.rej| SCSM[SCSM] + SCSM -->|Bind.inv, Unbind.inv, Delimitor, Op.inv, AP_U_Abort| SCF + SDF[SDF Application] -->|Bind.inv, Unbind.inv, Op.inv, U_Abort| SDSM[SDSM] + SDSM -->|Bind.res, Bind.err, AP_U_Abort, Delimitor, Op.res, Op.err, Op.rej| SDF + SCSM -->|TC_INVOKE, TC_U_ABORT, TC_END, Dialogue_terminated, TC_CONTINUE, TC_BEGIN| TCAP[TCAP] + TCAP -->|TC_CONTINUE, TC_U_ABORT, TC_RESULT, TC_ERROR, TC_CANCEL, TC_REJECT| SCSM + SDSM -->|TC_INVOKE, TC_U_ABORT, TC_END, TC_CONTINUE, TC_BEGIN| TCAP + TCAP -->|TC_CONTINUE, TC_U_ABORT, TC_RESULT, TC_ERROR, TC_REJECT| SDSM + end + +``` + +The diagram illustrates the SCF-SDF Model. It features five main components: SCF Application, SDF Application, SCSM, SDSM, and TCAP. The SCF Application and SDF Application are at the top, each connected to its respective middle component (SCSM and SDSM). The SCF Application sends 'Bind.res, Bind.err, U\_Abort, Process\_error, Op.res, Op.err, Op.rej' to SCSM, which in turn sends 'Bind.inv, Unbind.inv, Delimitor, Op.inv, AP\_U\_Abort' back. The SDF Application sends 'Bind.inv, Unbind.inv, Op.inv, U\_Abort' to SDSM, which responds with 'Bind.res, Bind.err, AP\_U\_Abort, Delimitor, Op.res, Op.err, Op.rej'. Both SCSM and SDSM are connected to the bottom TCAP component. SCSM sends 'TC\_INVOKE, TC\_U\_ABORT, TC\_END, Dialogue\_terminated, TC\_CONTINUE, TC\_BEGIN' to TCAP, which responds with 'TC\_CONTINUE, TC\_U\_ABORT, TC\_RESULT, TC\_ERROR, TC\_CANCEL, TC\_REJECT'. SDSM sends 'TC\_INVOKE, TC\_U\_ABORT, TC\_END, TC\_CONTINUE, TC\_BEGIN' to TCAP, which responds with 'TC\_CONTINUE, TC\_U\_ABORT, TC\_RESULT, TC\_ERROR, TC\_REJECT'. + +SCF-SDF Model diagram showing interactions between SCF Application, SDF Application, SCSM, SDSM, and TCAP. + +T1169700-94/d96 + +FIGURE B.1/Q.1218 +**SCF-SDF Model** + +### B.1.2.2 Exceptional procedures + +- When the timer T1 expires and the SCSM process instance is in the "Wait\_for\_Subsequent\_Request" the "Dialogue terminated" primitive shall be sent to the Component Coordination of the TC in order to discard the eventual directory invoke operation stored and awaiting transmission, a "Process\_error" primitive shall be sent to the SCF application process and the SCSM process shall be terminated. +- When the SCF application process wants to abort the communication with the peer SDF it shall send a "AP\_U\_Abort" primitive to SCSM process instance, this process instance shall send a "Dialogue terminated" primitive to the Component Coordination of the TC in order to discard the eventual directory invoke operation stored and awaiting transmission and the SCSM process shall be terminated. + +### **B.1.3 State 3 – "Wait\_for\_Bind\_result"** + +#### **B.1.3.1 Normal procedures** + +In this state, the SCF is waiting for the response from the SDF. The reception of the response in the TC-CONTINUE ind primitive from TC to the Bind operation previously issued to the SDF, shall stop the timer T2, shall send a Bind.res primitive to the application process and shall cause a transition of the SCF to the state "SDF Bound". + +#### **B.1.3.2 Exceptional procedures** + +- When the timer T2 expires and the SCSM process instance is in the "Wait\_for\_Bind\_result", the "TC-U-ABORT" req primitive shall be sent to the Dialogue Handling of the TC in order to abort the started dialogue with the peer SDF process, a "Process\_error" primitive shall be sent to the SCF application process and the SCSM process shall be terminated. +- When the SCF application process wants to abort the communication with the peer SDF it shall send a "AP\_U\_Abort" primitive to SCSM process instance, this process instance shall send a "TC-U-ABORT" req primitive to the Dialogue Handling of the TC in order to abort the started dialogue with the peer SDF process and the SCSM process shall be terminated. +- When a TC-U-ABORT ind. primitive is received from the TC having a directoryBind error operation component from the peer SDF process, this operation shall be passed in the "Bind.err" primitive to the application process and the SCSM process shall be terminated. +- When a TC-U-ABORT ind. primitive is received from the TC without having a directoryBind error operation component from the peer SDF process, a "U\_Abort" primitive shall be passed to the application process and the SCSM process shall be terminated. + +### **B.1.4 State 4 – "SDF Bound"** + +#### **B.1.4.1 Normal procedures** + +In this state, the SCF has established an authenticated access to the SDF, and is waiting for requests to the SDF from the service logic or is waiting for responses to the operations previously issued to the SDF: + +- When a Op.inv primitive is received from the application process, a component handling primitive TC-INVOKED req shall be sent to the TC and the process instance shall return to the "SDF\_Bound" state. The SCSM process instance shall wait for a Delimiter primitive response from the application process. The operations to be carried by the TC-INVOKED req primitive can be a search, modifyEntry, addEntry or removeEntry. +- When a "Delimiter" primitive is received from the application process, then a TC-CONTINUE req primitive will be sent to the TC in order to forward the received operation(s) to the remote SDF application process instance. +- When a TC-RESULT ind primitive is received from the TC caused by the successful reception of a response to the operation previously issued to the SDF, the SCSM process instance shall send the operation return result to the application process and shall return to the same state. +- When a TC-U-ERROR ind primitive is received from the TC indicating that the invoked operation from the SCF application process has failed at the peer SDF side, the SCSM process shall send the operation return error to the application process and shall return to the same state. +- When the TC-L-REJECT ind primitive is received indicating that the TC Component sub-layer received an invalid operation, then the SCSM process instance shall send an operation reject to the application process and shall return to the same state. + +- When the TC-R-REJECT ind primitive is received from the TC indicating that the operation was rejected by the remote Component sub-layer, then the SCSM process instance shall send an operation reject to the application process and shall return to the same state. +- When the TC-U-REJECT ind primitive is received from the TC indicating that the operation was rejected by the remote application process instance, then the SCSM process instance shall send an operation reject to the application process and shall return to the same state. +- When the TC-L-CANCEL ind primitive is received from the TC indicating that the operation invocation was locally terminated due to a time-out condition, then the SCSM process instance shall inform the application process and shall return to the same state. +- When an Unbind.inv primitive is received from the SCF application process caused by the need to terminate the authenticated access to the SDF, a TC-END req primitive shall be sent to the TC in order to end the dialogue with the remote SDF application process and the SCSM process instance shall be terminated. + +#### **B.1.4.2 Exceptional procedures** + +- When the SCF application process wants to abort the communication with the peer SDF, it shall send a "AP\_U\_Abort" primitive to SCSM process instance, this process instance shall send a "TC-U-ABORT" req primitive to the Dialogue Handling of the TC in order to abort the started dialogue with the peer SDF process and the SCSM process shall be terminated. +- When a TC-U-ABORT ind. primitive is received from the TC, a "U\_Abort" primitive shall be passed to the application process and the SCSM process shall be terminated. + +### **B.2 Description of the Process SDSM** + +The SDF directory abstract service is defined in terms of a number of operations which the SDF can perform at the request of the SCF on behalf of the end user. Before invoking these operations, the SCF shall perform a bind operation at some access point. The SCF can then invoke operations, each invocation shall identify the particular operation to be performed and shall carry the arguments which define the actual request. + +#### **B.2.1 State 1 – "Idle"** + +##### **B.2.1.1 Normal procedures** + +When the Dialogue handling services of TC sends a TC-BEGIN ind. containing the DirectoryBind operation, a SDSM process instance shall be created, a "Bind.inv" primitive shall be sent to the application process and timer T3 shall be started. This event shall cause a transition to the state "Bind pending". The timer T3 is started in order to supervise the state "Bind pending" and shall ensure that the SDSM process is deleted when the communication with the application process is interrupted. + +##### **B.2.1.2 Exceptional procedures** + +None identified. + +#### **B.2.2 State 2 – "Bind Pending"** + +##### **B.2.2.1 Normal procedures** + +In this state, a Bind request has been received from the SCF. The SDF is performing the SCF access control procedures behind the Bind operation (e.g. access authentication). There may also be a case such that the Bind operation is a dummy one. Then, the access authentication is not required. Two events are considered in this state: + +- When the TC-INVOKE ind. component handling primitive is received caused by the reception of operations before the result from the Bind operation is sent from the application process, a "Op.inv" primitive shall be sent to the application process and the SDSM process instance shall return to the "Bind pending" state. +- When the bind request succeeds, the SDF application process shall send a "Bind.res" primitive to the SDSM process instance containing the directoryBind return result. On receipt of the "Bind res" primitive the SDSM process instance shall stop timer T3, store the information locally until a "Delimitor" primitive is received from the application process and shall transit to the "SCF bound" state. + +![State transition diagram for Process SCSM. The process starts with an initial state leading to a data store, then receives a 'Bind.inv' from an SCF Application. It stores the bind argument, starts timer T1, and waits for subsequent requests. A decision point leads to four possible paths: 'Delimitor' (stop T1, start T2, TC_BEGIN with bind argument, wait for result), 'Op.inv' (TC_INVOKE to TCAP, then a self-loop), 'T1 Expiry' (Dialogue_terminated, Process_error), and 'AP_U_Abort' (Dialogue_terminated, end state).](00706efebe902e8e06e8ec7cd9747604_img.jpg) + +``` +graph TD; Start([ ]) --> DataStore(( )); DataStore --> BindInv[/Bind.inv/]; SCF[From SCF Application] -.-> BindInv; BindInv --> StoreBind[Store Bind Argument]; StoreBind --> StartT1[Start Timer T1]; StartT1 --> WaitSub[Wait for Subsequent Requests]; WaitSub --> Decision{ }; Decision --> Delimitor[/Delimitor/]; Decision --> OpInv[/Op.inv/]; Decision --> T1Expiry[/T1 Expiry/]; Decision --> APUAbort[/AP_U_Abort/]; Delimitor --> StopT1[Stop Timer T1]; StopT1 --> StartT2[Start Timer T2]; StartT2 --> TCBegin[/TC_BEGIN/]; TCBegin --> WithBind[With Bind Argument]; WithBind --> WaitResult[Wait for Bind result]; OpInv --> TCInvoke[/TC_INVOKE/]; TCInvoke --> ToTCAP[To TCAP]; TCInvoke --> SelfLoop(( - )); T1Expiry --> DialogueTerminated1[/Dialogue_terminated/]; DialogueTerminated1 --> ProcessError[/Process_error/]; ProcessError --> End1(( )); APUAbort --> DialogueTerminated2[/Dialogue_terminated/]; DialogueTerminated2 --> End2(( )); +``` + +State transition diagram for Process SCSM. The process starts with an initial state leading to a data store, then receives a 'Bind.inv' from an SCF Application. It stores the bind argument, starts timer T1, and waits for subsequent requests. A decision point leads to four possible paths: 'Delimitor' (stop T1, start T2, TC\_BEGIN with bind argument, wait for result), 'Op.inv' (TC\_INVOKE to TCAP, then a self-loop), 'T1 Expiry' (Dialogue\_terminated, Process\_error), and 'AP\_U\_Abort' (Dialogue\_terminated, end state). + +T1169710-94/d97 + +FIGURE B.2/Q.1218 (sheet 1 of 3) +SCSM + +![SDL flowchart for Process SCSM showing state transitions from 'Wait for Bind result' and 'SDF bound' based on various TC signals and timer events.](3112fb7d627cf9f6d2328f8529ca3277_img.jpg) + +``` + +graph TD + State1([Wait for Bind result]) + State1 --- Branch1 + + Branch1 --- In1[/TC_CONTINUE/] + In1 --> Task1[Stop Timer T2] + Task1 --> Out1[/Bind.res/] + Out1 --> State2([SDF bound]) + + Branch1 --- In2[/TC_U_ABORT/] + In2 --> Dec1{Bind.err?} + Dec1 -- Yes --> Out2[/Bind.err/] + Out2 --> Term1((X)) + Dec1 -- No --> Out3[/U_Abort/] + Out3 --> Term2((X)) + + Branch1 --- In3[/T2 Expiry/] + In3 --> Out4[/TC_U_ABORT/] + Out4 --> Task2[Process_error] + Task2 --> Term3((X)) + + Branch1 --- In4[/AP_U_Abort/] + In4 --> Out5[/TC_U_ABORT/] + Out5 --> Term4((X)) + + State2 --- Branch2 + + Branch2 --- In5[/TC_RESULT/] + In5 --> Out6[/Op.res/] + Out6 --> Term5([ - ]) + + Branch2 --- In6[/TC_CANCEL +TC_ERROR +TC_REJECT/] + In6 --> Out7[/Op.err +Op.rej/] + Out7 --> Term6([ - ]) + + Branch2 --- In7[/TC_U_ABORT/] + In7 --> Out8[/U_Abort/] + Out8 --> Term7((X)) + +``` + +SDL flowchart for Process SCSM showing state transitions from 'Wait for Bind result' and 'SDF bound' based on various TC signals and timer events. + +T1169720-94/d98 + +FIGURE B.2/Q.1218 (sheet 2 of 3) + +SCSM + +![State transition diagram for Process SCSM. The diagram shows four parallel state transition paths starting from a common 'SDF bound' state. Each path consists of an input primitive (Op.inv, Delimitor, AP_U_ABORT, Unbind.inv), a corresponding transition primitive (TC_INVOKE, TC_CONTINUE, TC_U_ABORT, TC_END), and a resulting state (two are stable states marked with '-', and two are error states marked with a circled X).](5083128e335a383c042e15d2d8795c95_img.jpg) + +Process SCSM + +PAGE 3 (3) + +``` + +stateDiagram-v2 + [*] --> SDF_bound : SDF bound + SDF_bound --> Op_inv : Op.inv + SDF_bound --> Delimitor + SDF_bound --> AP_U_ABORT + SDF_bound --> Unbind_inv : Unbind.inv + Op_inv --> TC_INVOKE + Delimitor --> TC_CONTINUE + AP_U_ABORT --> TC_U_ABORT + Unbind_inv --> TC_END + TC_INVOKE --> S1 : - + TC_CONTINUE --> S2 : - + TC_U_ABORT --> [*] : X + TC_END --> [*] : X + +``` + +T1169730-94/d99 + +State transition diagram for Process SCSM. The diagram shows four parallel state transition paths starting from a common 'SDF bound' state. Each path consists of an input primitive (Op.inv, Delimitor, AP\_U\_ABORT, Unbind.inv), a corresponding transition primitive (TC\_INVOKE, TC\_CONTINUE, TC\_U\_ABORT, TC\_END), and a resulting state (two are stable states marked with '-', and two are error states marked with a circled X). + +FIGURE B.2/Q.1218 (sheet 3 of 3) +SCSM + +#### B.2.2.2 Exceptional procedures + +- When the bind request fails, the application process shall send a "Bind.err" primitive to the SDSM process instance containing the directoryBind errors. The SDSM process instance shall send a "TC-U-ABORT" req primitive to the Dialogue Handling of the TC in order to abort the started dialogue with the peer SCF process and the SDSM process shall be terminated. +- When the timer T3 expires and the SDSM process instance is in the "Bind\_pending" state, the "TC-U-ABORT" req primitive shall be sent to the Dialogue Handling of the TC in order to abort the started dialogue with the peer SCF process, a "Process\_error" primitive shall be sent to the SDF application process and the SDSM process shall be terminated. +- When the SDF application process wants to abort the communication with the peer SCF it shall send a "AP\_U\_Abort" primitive to SDSM process instance, this process instance shall send a "TC-U-ABORT" req primitive to the Dialogue Handling of the TC in order to abort the started dialogue with the peer SCF process and the SDSM process shall be terminated. + +### **B.2.3 State 3 – "SCF Bound"** + +#### **B.2.3.1 Normal procedures** + +In this state, the access of the SCF to the SDF is authorized and operations coming from the SCF are accepted. Besides waiting for requests from the SCF, the SDF can also send in that state responses to previously issued operations. The following normal events are considered in this state: + +- When a Op.res primitive is received from the application process indicating that an operation is successfully executed, a component handling primitive TC-RESULT req shall be sent to the TC and the process instance shall return to the "SCF bound" state. The SDSM process instance shall wait for a Delimiter primitive response from the application process to send a TC-CONTINUE req primitive to the TC Dialogue Handling entity so that the TC can forward this return result to the peer SCSM process instance. The return results to be carried by the TC-RESULT req primitive can be originated from previously received search, modifyEntry, addEntry or removeEntry operations. +- When a Op.err primitive is received from the application process indicating that an previously received operation cannot be successfully executed, a component handling primitive TC-U-ERROR req shall be sent to the TC and the process instance shall return to the "SDF bound" state. The SDSM process instance shall wait for a Delimiter primitive response from the application process to send a TC-CONTINUE req primitive to the TC Dialogue Handling entity so that the TC can forward this return error to the peer SCSM process instance. The return errors to be carried by the TC-U-ERROR req primitive can be originated from previously received search, modifyEntry, addEntry or removeEntry operations. +- When a Delimiter primitive is received from the application process, the SDSM process instance shall send a dialogue handling primitive TC-CONTINUE req to TC. Once the TC-CONTINUE req. primitive is received by the TC, a message containing the Bind return result, return error or reject argument previously stored, if not already sent, and other operation return result, return error or reject arguments if any shall be sent to the SCF. This event shall cause the SDSM process instance to return to the State "SCF bound". +- When a TC-END ind primitive is received from the Dialogue Handling of the TC caused by the reception of the Unbind operation from the SCF, the SDSM process instance shall send a "Unbind.inv" primitive to the application process and shall terminate the SDSM process instance. The SCF-SDF association shall be ended and all associated resources are released. +- When a TC-INVOKED ind component handling primitive is received from the TC a "Op.inv" primitive shall be sent to the application process and the SDSM process instance shall return to the "SCF bound" state. + +#### **B.2.3.2 Exceptional procedures** + +- When a Op.rej primitive is received from the application process indicating that an previously received operation is rejected, a component handling primitive TC-U-REJECT req shall be sent to the TC and the process instance shall return to the "SCF bound" state. The SDSM process instance shall wait for a Delimiter primitive response from the application process to send a TC-U-CONTINUE req primitive to the TC Dialogue Handling entity so that the TC can forward this reject to the peer SCSM process instance. The reject to be carried by the TC-U-REJECT req primitive can be originated from previously received search, modifyEntry, addEntry or removeEntry operations. +- When a TC-U-ABORT ind. primitive is received from the TC a "U\_Abort" primitive shall be passed to the application process and the SDSM process shall be terminated. +- When the SDF application process wants to abort the communication with the peer SCF it shall send a "AP\_U\_Abort" primitive to SDSM process instance, this process instance shall send a "TC-U-ABORT" req primitive to the Dialogue Handling of the TC in order to abort the started dialogue with the peer SCF process and the SDSM process shall be terminated. + +![Flowchart for Process SDSM showing states and transitions.](66d73f03871ad30f2bd1a6c76e5140c0_img.jpg) + +``` +graph TD; Start([ ]) --> End1([ ]); End1 --> TC_BEGIN{{TC_BEGIN}}; TC_BEGIN --> Bind.inv{Bind.inv}; Bind.inv --> StartTimerT3[Start Timer T3]; StartTimerT3 --> BindPending([Bind pending]); BindPending --> TC_INVOKE{{TC_INVOKE}}; BindPending --> Bind.err{{Bind.err}}; BindPending --> AP_U_Abort{{AP_U_Abort}}; BindPending --> T3_Expiry{{T3 Expiry}}; TC_INVOKE --> Op.inv{Op.inv}; Op.inv --> Dash([ - ]); Bind.err --> TC_U_ABORT1{TC_U_ABORT}; TC_U_ABORT1 --> X1((X)); AP_U_Abort --> TC_U_ABORT2{TC_U_ABORT}; TC_U_ABORT2 --> X2((X)); T3_Expiry --> TC_U_ABORT3{TC_U_ABORT}; TC_U_ABORT3 --> Process_error{Process_error}; Process_error --> X3((X)); +``` + +The flowchart illustrates the state transitions for Process SDSM. It begins with an initial state (oval) leading to an end state (oval), which then leads to the TC\_BEGIN transition (chevron). This is followed by the Bind.inv transition (chevron), the Start Timer T3 action (rectangle), and the Bind pending state (oval). From Bind pending, four transitions are possible: TC\_INVOKE (chevron), Bind.err (chevron), AP\_U\_Abort (chevron), and T3 Expiry (chevron). TC\_INVOKE leads to the Op.inv transition (chevron), which ends in a state represented by a dash (oval). Bind.err, AP\_U\_Abort, and T3 Expiry all lead to a TC\_U\_ABORT transition (chevron), each of which ends in an error state represented by a circled X. The T3 Expiry path also includes a Process\_error transition (chevron) before the final error state. + +Flowchart for Process SDSM showing states and transitions. + +T1169740-94/d100 + +FIGURE B.3/Q.1218 (sheet 1 of 3) +SDSM + +![Flowchart for Process SDSM showing steps from 'Bind pending' to 'SCF bound' and then branching into 'Op.res', 'Delimiter', 'Op.err Op.rej', and 'AP_U_Abort' paths.](e7bb732c66eeb3d251bc32507a62c86e_img.jpg) + +``` +graph TD; A([Bind pending]) --> B[/Bind.res/]; B --> C[Stop Timer T3]; C --> D[Store Bind result]; D --> E([SCF bound]); E --> F1[Op.res]; E --> F2[/Delimiter/]; E --> F3[Op.err Op.rej]; E --> F4[AP_U_Abort]; F1 --> G1[TC_RESULT]; G1 --> H1([ - ]); F2 --> G2[TC_CONTINUE]; G2 --> H2[Clear user info]; H2 --> H3([ - ]); F3 --> G3[TC-REJECT TC-ERROR]; G3 --> H4([ - ]); F4 --> G4[TC_U_ABORT]; G4 --> H5((X)); +``` + +Flowchart for Process SDSM showing steps from 'Bind pending' to 'SCF bound' and then branching into 'Op.res', 'Delimiter', 'Op.err Op.rej', and 'AP\_U\_Abort' paths. + +T1169750-94/d101 + +FIGURE B.3/Q.1218 (sheet 2 of 3) +**SDSM** + +![A hierarchical diagram titled 'Process SDSM' showing the relationship between SCF bound and various service operations. At the top is a double-oval labeled 'SCF bound'. Below it, a horizontal line branches into three chevron-shaped boxes: 'TC_INVOKE', 'TC_END', and 'TC_U_ABORT'. Below 'TC_INVOKE' is a chevron-shaped box labeled 'Op.inv', which points down to a double-oval containing a dash '-'. Below 'TC_END' is a chevron-shaped box labeled 'Unbind.inv', which points down to a circle with an 'X'. Below 'TC_U_ABORT' is a chevron-shaped box labeled 'U_Abort', which points down to a circle with an 'X'. The entire diagram is enclosed in a rectangular border.](0c4a8a2e7502cb4a43d6e45efe56e9dc_img.jpg) + +``` + +graph TD + SCF_bound([SCF bound]) --> TC_INVOKE[TC_INVOKE] + SCF_bound --> TC_END[TC_END] + SCF_bound --> TC_U_ABORT[TC_U_ABORT] + TC_INVOKE --> Op_inv[Op.inv] + TC_END --> Unbind_inv[Unbind.inv] + TC_U_ABORT --> U_Abort[U_Abort] + Op_inv --> Dash([-]) + Unbind_inv --> CircleX1((X)) + U_Abort --> CircleX2((X)) + +``` + +A hierarchical diagram titled 'Process SDSM' showing the relationship between SCF bound and various service operations. At the top is a double-oval labeled 'SCF bound'. Below it, a horizontal line branches into three chevron-shaped boxes: 'TC\_INVOKE', 'TC\_END', and 'TC\_U\_ABORT'. Below 'TC\_INVOKE' is a chevron-shaped box labeled 'Op.inv', which points down to a double-oval containing a dash '-'. Below 'TC\_END' is a chevron-shaped box labeled 'Unbind.inv', which points down to a circle with an 'X'. Below 'TC\_U\_ABORT' is a chevron-shaped box labeled 'U\_Abort', which points down to a circle with an 'X'. The entire diagram is enclosed in a rectangular border. + +T1169760-94/d102 + +FIGURE B.3/Q.1218 (sheet 3 of 3) + +SDSM + +## Appendix I + +### Service data modelling + +(This appendix does not form an integral part of this Recommendation) + +This appendix outlines the required steps and provides a set of guidelines and examples for the definition of a service data model and the mapping of it onto the information model defined in 2.2.2.3. These guidelines and examples provide a simple mechanism which addresses the items in I.1.1 and I.2.1. + +Additional tools (e.g. attribute context specifications) may also provide solutions to data modelling, however this appendix does not address these tools. + +#### I.1 Review of need for Service data modelling + +The adoption of the X.501 information model as the data model for representing service data within the SDF, together with the use of X.511 operations for the interface between the SCF and SDF, has opened up the question of how IN Service data should be mapped onto this information model. + +Inappropriate mapping of service data onto the X.500 information model used within the SDF can dramatically increase the amount of information which must be transferred across the SCF-SDF interface (in certain cases even exceeding the capacity of the TCAP link). In addition to higher interface traffic, the choice of mapping can also affect the amount of data processing which must be performed by the Functional Element Actions (FEA) within the SCF, to the point of making the SCF-FEA implementations dependent on the service data. + +This subclause outlines a simple set of mapping rules which can be applied to service data to both minimize SCF-SDF interface traffic and to maintain service-independent handling of data. + +### **I.1.1 General modelling issues** + +There are three general requirements to keep in mind when organizing the IN Service data into the X.500 information model. Each of these requirements should be given equal weight. + +- **Req-1** – Minimize the traffic between the SCF and the SDF. + +The SCF-SDF interface will probably be one of the most heavily used interfaces within the IN environment. Each SLPI within the SCF may have to initiate multiple accesses to data stored in the SDF. It is crucial from a performance point of view that the data transfers be kept to a minimum. + +- **Req-2** – Minimize the data processing to be done within the SCF. + +Data processing within the SCF is performed by the FEAs defined in Recommendation Q.1214 to handle the Information flows. These FEAs are assumed to be independent of the service for which they are invoked. If the data information being transferred is of the wrong granularity, then service dependent processing may be performed by the FEAs within the SCF. Care must be taken in the design of the X.500 information model for the IN service Data to maintain the service independency of the FEA. + +- **Req-3** – Consider the effect of data distribution on the X.500 data management. + +For CS-1 systems, the SDF implementation may not be distributed. It should be noted that X.500 systems are inherently distributed data management systems. If the design of the structure of the DIT does not take the distribution of data into account, then the resulting Directory may be unmanageable in terms of the "knowledge" management required to access the Directory information across multiple Directory Service Agents (DSA). + +While it can be argued that a centralized Directory implementation need not take distribution into account, performance requirements may require the splitting of the Directory over a number of local DSAs, requiring distribution knowledge to be maintained within each DSA. + +### **I.1.2 Service modelling – Defining the information required** + +Service modelling is defined in Recommendation Q.1203. It consists of the following steps: + +- 1) identifying the service features which comprise the service; +- 2) identifying the data required to support the needed service feature; +- 3) identifying the shared data between the service features used by the service; +- 4) identify the operations and processing required on the service data; +- 5) identify the Access Control requirements for the service data. + +These steps are not covered in this Recommendation. Only the additional steps required to map the Service Data onto the SDF Information Model defined in 2.2 are covered here. + +## I.2 Guidelines for building Service Data Models + +Once the IN Service Data Model has been defined in terms of the service feature data, it must be mapped onto the X.500 information model. This can be done using the following steps: + +- 1) selection of ATTRIBUTES; +- 2) selection of OBJECT-CLASSs; +- 3) designing the Service DIT; +- 4) assignment of Access Control to ATTRIBUTES and OBJECT-CLASSs. + +### I.2.1 Selection of ATTRIBUTES + +The selection of the ATTRIBUTES is affected by the operations and processing required by the SCF. The following rules are provided to assist the selection process: + +- **Guideline 1** – ATTRIBUTES are the smallest addressable unit of IN Service Data which may be transferred across the SCF-SDF interface for processing by the SCF. Structured data types should be avoided in ATTRIBUTE definitions. +- **Guideline 2** – All the ATTRIBUTES in the Directory which are to be retrieved by the IN service are by preference to be SINGLE-VALUED. +- **Guideline 3** – If Service Data contains multi-column tables of information (see Figure I.1), then each column3), 4) of the table should have an ATTRIBUTE definition. + +For example, in Figure I.1a) (Time of Day Routing table) three ATTRIBUTES are defined (StartTime, StopTime and Destination). For Figure I.1b) (Abbreviated Number table) two ATTRIBUTES are defined (AbbrevNo and Destination). + +After all ATTRIBUTES have been identified it may be possible to reduce the total number of ATTRIBUTES defined due to identical definitions (e.g. Destination in Figure I.1). + +| Start Time | Stop Time | Destination | +|------------|-----------|-------------| +| 01:00 | 09:00 | 204 23456 | +| 09:01 | 15:00 | 204 12345 | +| 15:01 | 23:00 | 204 23456 | +| | | | + +a) Time of Day Routing table + +| Abbreviated No. | Destination | +|-----------------|-------------| +| 01 | 204 23456 | +| 02 | 204 12345 | +| 03 | 204 23456 | +| | | + +b) Abbreviated Number table + +FIGURE I.1/Q.1218 +Multi-Column Tables in Service Data + +3) This assumes that the tables are organized as in Figure I.1 with each row in the table representing a separate group of information. If this organization is reversed, with the columns containing the item groups then each row in the table should have an ATTRIBUTE definition. + +4) This guideline is normally used in conjunction with Guideline 6 to determine entry items in the DIT. + +### I.2.1.1 ATTRIBUTE Type definitions + +An ATTRIBUTE's type is defined by an ASN.1 data definition. + +``` +thisAttribute ATTRIBUTE ::= { + .. + WITH SYNTAX thisAttributeASN1DataType, + .. +} +``` + +An ATTRIBUTE can be defined as a SUB-TYPE of another ATTRIBUTE which means that it must conform to the definition of the parent ATTRIBUTE. + +``` +thisAttribute ATTRIBUTE ::= { + .. + SUBTYPE OF anotherAttribute, + .. +} +``` + +While this provides a convenient way to re-use attribute definitions it can have a side-effect which will impact on Req-1. This is because an X.500 Search operation for a specific AttributeType will return not only the required Attribute's values but also the Attribute Values of those Attributes which are a sub-type of the required Attribute. + +It should be noted that Searching for a particular Attribute will not return any of the parent Attribute values. + +An ATTRIBUTE can be defined as a Collective Attribute which implies that its values can be shared amongst a number of Directory Entries. + +``` +collectiveAttribute ATTRIBUTE ::= { + .. + COLLECTIVE TRUE, + .. +} +``` + +Examples of pre-defined attribute can be found in clause 2/X.520. + +### I.2.1.2 Defining Permitted Values + +There are two methods which can be used to define permitted values for an attribute. + +These are: + +- 1) restrict the values to a specific set of values, +- 2) restrict the values to a range on numeric values. + +The first case requires two additional attributes: + +- a) an attribute to hold the permitted values for the current attribute, +- b) an Access Control attribute linking the two attributes together. This attribute must have a syntax of ACItem and contain a ProtectedItem field containing the following: + +``` +ProtectedItem ::= SEQUENCE { + .. + restrictedBy [10] SET OF RestrictedValue OPTIONAL + .. +} +``` + +The RestrictedValue contents contain the Attribute Id's of the current Attribute and the Attribute containing the permitted values. Since the RestrictedValue value is part of the Access Control attribute, the ability to change the RestrictedValue value implies the ability to modify all the Access control parameters for the current Entry contained within the Access Control Attribute. + +The second case requires only one additional attribute: + +- c) an Access Control attribute holding the value range for the current attribute. This attribute must have a syntax of ACItem type and contain a ProtectedItem field containing the following: + +``` +ProtectedItem ::= SEQUENCE { + .. + rangeOfValues [7] Filter OPTIONAL + .. +} +``` + +The Filter contents contain the value range specification the Attribute values. Note that to change one part of the value range requires replacing the entire Filter. Also since the Filter value is part of the Access Control attribute, the ability to change the Filter value implies the ability to modify all the Access control parameters for the current Entry contained within the Access Control attribute. + +#### I.2.1.3 Defining Default Values + +The default for an attribute type is set at execution time by specifying an Attribute value with a context whose Fallback field is set to TRUE. + +Attribute values whose context fallback values are set to TRUE will only be returned if no other attribute values that match the criteria are present. + +#### I.2.1.4 Defining MAX Attribute Values + +Limiting the number of values which an Attribute may have, is done by specifying an Access Control Attribute containing a ProtectedItem field with the following syntax: + +``` +ProtectedItem ::= SEQUENCE { + .. + maxValueCount [8] SET OF MaxValueCount OPTIONAL + .. +} +``` + +The MaxValueCount contents contain the Attribute Id and the maximum number of values which can be stored in the Attribute. Since the MaxValueCount value is part of the Access Control attribute, the ability to change the MaxValueCount value implies the ability to modify all the Access control parameters for the current Entry contained within the Access Control Attribute. + +#### I.2.1.5 Defining Attribute Lifetimes + +Attribute lifetimes are set by supplying a TemporalContext for the Attribute Value (at execution time). + +#### I.2.1.6 Definition of MATCHING-RULES + +MATCHING-RULES define how Attribute values are tested against external values for use in search Filters and Name Matching. An ATTRIBUTE definition has three different types of Matching Rules: + +EQUALITY for testing (value == attribute Value). + +ORDERING for testing (value < attribute Value). + +SUBSTRINGS for testing sub-strings matches. + +``` +thisAttribute ATTRIBUTE ::= { + .. + EQUALITY MATCHING RULE equalityMatchingRuleName, + ORDERING MATCHING RULE orderingMatchingRuleName, + SUBSTRINGS MATCHING RULE substringsMatchingRuleName, + .. +} +``` + +Examples of predefined matching-rules can be found on clause 3/X.520. + +#### I.2.1.7 Assigning the ATTRIBUTE Object Identifiers + +Each ATTRIBUTE defined is assigned a unique Object Identifier. The form of this Object Identifier should be as follows: + +-- IN object identifier prefix + +``` +in-oi OBJECT IDENTIFIER ::= { ccitt recommendation q 1218 ... } +``` + +-- service attribute definitions + +``` +attributeX OBJECT IDENTIFIER ::= { in-oi ServiceID attributeType(4) AttributeID } +``` + +-- ServiceID defines the service/service feature to which the attribute belongs. + +-- AttributeID defines the Attribute ID within the service: this is assigned by the Service + +-- designer. + +## I.2.2 Selection of OBJECT-CLASSs + +Once the ATTRIBUTES used within the Service Data Model have been identified, then they can be grouped together into specific OBJECT-CLASS elements. + +### I.2.2.1 Defining the OBJECT-CLASS + +An OBJECT-CLASS defines the specification of a Directory Entry. It consists of a grouping of ATTRIBUTES into a single object class. Each instance of a Directory Entry within the DIT has a unique identity (see 6.2.2.2 for specification). The following rules can be used to assist the OBJECT-CLASS definition: + +- **Guideline 4** – Service data values which can share a common unique identity should be grouped as ATTRIBUTES within a Directory Entry (e.g. Service Data, User Data for a service). +- **Guideline 5** – Service data values which are part of a multi-column Table (see Guideline 3) should be grouped into a single OBJECT-CLASS definition. + +An OBJECT-CLASS can be specified as being a SUB-CLASS of another OBJECT-CLASS. In this case the OBJECT-CLASS contains all of the attributes and properties of the parent OBJECT-CLASS. + +This is similar to inheritance in C++. + +### I.2.2.2 Selecting the RDN (NAME-FORM) + +Each OBJECT-CLASS can have a number of attributes designated as possible RDN attributes. This is done using the NAME-FORM specification. When the Directory Entry is created one of these must be designated the active RDN (through the Distinguished Name defined in the AddEntry operation). After the object has been created, only the active RDN can be used in the name matching procedures for locating an object using the access operations (Search, ModifyEntry, RemoveEntry, ...). + +Therefore if two objects of the same OBJECT-CLASS are created with the same ATTRIBUTE values but using different active RDNs, then they are considered as two distinct objects within the DIT. If the same RDN had been used for the second object then an object creation error would have occurred. + +### I.2.2.3 Assigning the OBJECT-CLASS Object Identifiers + +Each OBJECT-CLASS defined is assigned a unique Object Identifier. The form of this Object Identifier should be as follows: + +-- *IN object identifier prefix* + +**in-oi OBJECT IDENTIFIER ::= { ccitt recommendation q 1218 ... }** + +-- *service object-class definitions* + +**objectClassX OBJECT IDENTIFIER ::= { in-oi ServiceID objectClass(6) ObjectClassID }** + +-- *ServiceID defines the service/service feature to which the attribute belongs.* + +-- *ObjectClassID defines the Object Class ID within the service: this is assigned by the Service designer.* + +## I.2.3 Defining the DIT + +This subclause describes how to build the DIT for an IN Service Data model. + +### I.2.3.1 Defining the Object Hierarchy (STRUCTURE-RULES) + +The DIT defines a hierarchy of data objects. Each Distinguished name of an object consists of the concatenation of the RDN of the object with the RDN's of the objects in the DIT above the object. The hierarchy of objects within the DIT is defined using STRUCTURE-RULES. Figure I.2 shows how a set of OBJECT-CLASS and STRUCTURE-RULES form the DIT. + +![Figure I.2/Q.1218: Mapping of STRUCTURE-RULES onto DIT. Part (a) shows a Structure Rule Design with Object A at the top, connected to Object B (sr1) and Object C (sr2). Object B is connected to Object D (sr3) and Object C is connected to Object D (sr4). Part (b) shows the DIT structure with root at the top, object-A below it, object-B and object-C below object-A, object-D1 below object-B, and object-D2 below object-C. A small code T1169770-94/d103 is at the bottom right.](831c19022658f416cb09b881629c2574_img.jpg) + +Figure I.2/Q.1218: Mapping of STRUCTURE-RULES onto DIT. Part (a) shows a Structure Rule Design with Object A at the top, connected to Object B (sr1) and Object C (sr2). Object B is connected to Object D (sr3) and Object C is connected to Object D (sr4). Part (b) shows the DIT structure with root at the top, object-A below it, object-B and object-C below object-A, object-D1 below object-B, and object-D2 below object-C. A small code T1169770-94/d103 is at the bottom right. + +FIGURE I.2/Q.1218 +Mapping of STRUCTURE-RULES onto DIT + +The following set of rules can be used to build the DIT from the set of OBJECT-CLASS specifications: + +- **Guideline 6** – Where Service Data values share a common structure, but may have multiple value sets (e.g. rows in a time-of-day translation table, user-specific data within a service) these are to be placed in Directory Entries which are subordinate to another Directory Entry (i.e. there is a STRUCTURE-RULE defining the relationship between the Directory Entries). +- **Guideline 7** – Where multiple sets of Data Entries exist under a specific Data Entry, it is recommended that each of the sets be placed as subordinates to a single data entry which is subordinate to the specific data entry (see Figure I.3). This will allow more efficient searching of the set data entries using the X.500 operations. + +![Figure I.3/Q.1218: Multiple Set recommended model structure. Part (a) shows 'After design' with DE type A at the top, connected to DE type B (sr1) and DE type C (sr2). Part (b) shows 'Recommended implementation' with DE type A at the top, connected to DE type Bh (sr1) and DE type Ch (sr2). DE type Bh is connected to DE type B (sr3) and DE type Ch is connected to DE type C (sr4). A small code T1169780-94/d104 is at the bottom right.](49a271e5b255a5dd4fc1be97a52c3e65_img.jpg) + +Figure I.3/Q.1218: Multiple Set recommended model structure. Part (a) shows 'After design' with DE type A at the top, connected to DE type B (sr1) and DE type C (sr2). Part (b) shows 'Recommended implementation' with DE type A at the top, connected to DE type Bh (sr1) and DE type Ch (sr2). DE type Bh is connected to DE type B (sr3) and DE type Ch is connected to DE type C (sr4). A small code T1169780-94/d104 is at the bottom right. + +FIGURE I.3/Q.1218 +Multiple Set recommended model structure + +### I.2.3.2 Defining alternative naming paths (Aliases) + +Once an object class has been instantiated its Distinguished Name is fixed. If an alternative naming path to the object is required, then an Alias object must be defined within the DIT. This Alias object will have its own RDN attributes and will contain a pointer to the object being referenced. + +An Alias object is an OBJECT-CLASS which is a subtype of the predefined alias OBJECT-CLASS. + +### I.2.3.3 Defining MAX number of subordinate Entries + +Limiting the number of subordinate entries an Entry may have, is done by specifying an Access Control Attribute within the Entry containing a ProtectedItem field with the following syntax; + +``` +ProtectedItem ::= SEQUENCE { + .. + maxImmSub [8] INTEGER OPTIONAL, + .. +} +``` + +The maxImmSub value contains the maximum number of subordinate entries which may be stored below the current Entry. Note that this limit only applies to the current DSA. Since the maxImmSub value is part of the Access Control attribute, the ability to change the maxImmSub value implies the ability to modify all the Access Control parameters for the Entry contained in the Access Control Attribute. + +## I.3 Example Service (UPT Like Service) + +This subclause implements an X.500 DIT for a simplified subset of a UPT service using the mapping rules. + +### I.3.1 Example Service description + +The example service contains the following service features: + +- 1) incall; +- 2) incall Registration; +- 3) incall Screening; +- 4) outcall; +- 5) outcall Screening by location. + +These features are described briefly below together with the data information which would be available after the service design stage (ref. I.1.2). The information for each service feature is presented in table form with the following columns: + +- | | | +|----------------------|---------------------------------------------------------------------------------------------------------| +| – Data: | The name of the data item. | +| – Definition: | The definition of the data item type (using ASN.1 style notation). | +| – Cardinality: | This defines how different versions of the data item can occur (e.g. one for each user of the service). | +| – Feature Operation: | This defines what operations (SCF-SDF interface) are used to manipulate the data item. | +| – Access Control: | This defines what level of access is required by the different levels of service operators. | + +NOTE – This is not intended to be a complete service. Only sufficient detail is provided to show how mapping's onto the SDF Information Model should be performed. + +#### I.3.1.1 Service Feature – Incall + +Normal Incall operation performs the following routing algorithm: + +- 1) if the user has a registered location active, then send call to registered location; +- 2) if active time-of-day location is active, then route to time-of-day location; +- 3) if the user has default location, then route to default location; +- 4) reject call with announcement "user is not available on system". + +All defined locations must be one of a pre-defined set of locations for the user. + +## Service Feature Information + +| Data | Definition | Cardinality | Feature Operations | Security Access Control | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|-----------------------------------------------| +| Registered Locations | SET OF Location | One per service user | None | Service: R
User management: R/W
User: R | +| Time Of Day Location | SEQUENCE {
startTime SEQUENCE {
day DayOfWeek,
time TimeOfDay },
stopTime SEQUENCE {
day DayOfWeek,
time TimeOfDay },
location Location } | Many per service user | Search | Service: R
User management: R/W
User: R | +| Current Location | Location | One per user | Search | Service: R
User: R/W | +| Current Location Expiry | TimeOfDay | One per user | None | Service: R
User: R/W | +| Default Expiry | TimeOfDay | One per user | None | Service: R
User management: R/W
User: R | +| Default Location | Location | One per user | Search | Service: R
User management: R/W
User: R | + +### I.3.1.2 Service Feature – Incall Registration + +This service feature allows the user to register his current location. The current location can either be set to the current terminal (identified by CLI or a defined location). The user can optionally set an expiry time for the current location. If no expiry time is set, a default expiry time is used. The current location must be one of a predefined set of locations. + +## Service Feature Information + +| Data | Definition | Cardinality | Feature Operations | Security Access Control | +|-------------------------|-----------------|----------------------|--------------------|-----------------------------------------------| +| Registered Location | SET OF Location | One per service user | None | Service: R
User management: R/W
User: R | +| Current Location | Location | One per user | modifyEntry | Service: R
User: R/W | +| Current Location Expiry | TimeOfDay | One per user | modifyEntry | Service: R
User: R/W | +| Default Expiry | TimeOfDay | One per user | None | Service: R
User management: R/W
User: R | + +### I.3.1.3 Service Feature – Incall Screening + +This service feature allows the user to reject an incoming call if it is from a specific location. There is a limit to the number of locations which can be used for screening. + +#### Service Feature Information + +| Data | Definition | Cardinality | Feature Operations | Security Access Control | +|--------------------|------------------------------------------|----------------------|--------------------|-----------------------------------------------| +| Incall Screen List | SET OF Location
SIZE (1..MaxListSize) | One per service user | Search | Service: R
User management: R/W
User: R | +| MaxListSize | INTEGER | One per service user | None | Service: R
Service management: R/W | + +### I.3.1.4 Service Feature – Outcall + +This service feature allows a user to make an outgoing call from a terminal location. The location must be one of the permitted locations for the user. The charge for the call is billed to the service user, not the owner of the terminal. + +#### Service Feature Information + +| Data | Definition | Cardinality | Feature Operations | Security Access Control | +|----------------------|-----------------|----------------------|--------------------|------------------------------------------------------------------------| +| Registered Locations | SET OF Location | One per service user | Search | Service: R
User management: R/W
User: R | +| User Id | ServiceNumber | One per service user | match/bind | Service management: R/W
Service: R
User management: R
User: R | +| User Password | Password | One per service user | match/bind | Service: R
User management: R/W
User: R | + +### I.3.1.5 Service Feature – Outcall screening by location + +This service feature provides for preventing outgoing calls to specific locations from proceeding. The list of prescribed locations is different for each location the user can use. + +#### Service Feature Information + +| Data | Definition | Cardinality | Feature Operations | Security Access Control | +|---------------------|------------------------------------------------------------------------------|----------------------|--------------------|---------------------------------| +| Outcall Screen List | SET OF {
SEQUENCE {
stopList SET OF Location,
location Location }}} | One per service user | Search | User management: R/W
User: R | + +### I.3.1.6 General Service Information + +The service features have the following relationships for interaction: + +- Incall screening is done before Incall; +- Outcall is done before Outcall Screening by location. + +### Additional Service Information + +The following additional service parameters are provided: + +| Data | Definition | Cardinality | Feature Operations | Security Access Control | +|-------------|------------|----------------------|--------------------|------------------------------------------------------------------------| +| Service Key | ServiceId | One per service | match/bind | Service management: R/W
Service: R
User management: R
User: R | +| User Name | String | One per service user | match | User management: R/W
User: R | + +## I.3.2 Example Service data modelling + +Now that the service data information has been defined, the mapping of the data onto the information model using the steps defined in subclause I.2 can begin. + +### I.3.2.1 Selection of Attributes + +The first step is to determine the ATTRIBUTE definitions required for the Service Data. For the purposes of defining attribute identifiers, the following object identifier is used: + +**exampleAttribute OBJECT IDENTIFIER ::= { in-oi exampleService(1) attributeType(4) }** + +### Data – Registered Locations + +The Registered Location stores the Locations at which a user may register to receive incoming calls. + +| | | | | | +|----------------------|-----------------|----------------------|------|-----------------------------------------------| +| Registered Locations | SET OF Location | One per service user | None | Service: R
User management: R/W
User: R | +|----------------------|-----------------|----------------------|------|-----------------------------------------------| + +For the purposes of this example the definition of a Location can be considered to be equivalent to a telephone number. This allows the use of SUBTYPE definitions for the service attributes which use Location type definitions from a pre-defined attribute in Recommendation X.520 (telephoneNumber). The definition of the Registered Location attribute therefore becomes: + +**regLocations ATTRIBUTE ::= { +    SUBTYPE OF telephoneNumber, +    COLLECTIVE TRUE, +    ID in-at-regLocations }** + +The attribute is defined as a Collective Attribute since its values will be shared among a number of Entries in the DIT (refer to I.3.3.2) + +## Data – Time Of Day Location + +The Time Of Day Location is actually a translation table consisting of 5 columns (startTime.day, startTime.time, stopTime.day, stopTime.time, location). + +| | | | | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------|-----------------------------------------------| +| Time Of Day Location | SEQUENCE {
startTime SEQUENCE {
day DayOfWeek,
time TimeOfDay },
stopTime SEQUENCE {
day DayOfWeek,
time TimeOfDay },
location Location } | Many per service
user | Search | Service: R
User management: R/W
User: R | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------|-----------------------------------------------| + +Using Guideline 3, 5 different ATTRIBUTES are defined, one for each column: + +``` + +startDay ATTRIBUTE ::= { + WITH SYNTAX DaysOfWeek -- from proposed X.520 Temporal Context + SINGLE VALUE TRUE + ID in-at-startDay } + +startTime ATTRIBUTE ::= { + WITH SYNTAX DayTime -- from proposed X.520 Temporal Context + EQUALITY MATCHING RULE numericStringMatch -- from X.520 + ORDERING MATCHING RULE numericStringOrderingMatch -- from X.520 + SUBSTRINGS MATCHING RULE numericStringSubstringsMatch -- from X.520 + SINGLE VALUE TRUE + ID in-at-startTime } + +stopDay ATTRIBUTE ::= { + WITH SYNTAX DaysOfWeek -- from proposed X.520 Temporal Context + SINGLE VALUE TRUE + ID in-at-stopDay } + +stopTime ATTRIBUTE ::= { + WITH SYNTAX DayTime -- from proposed X.520 Temporal Context + EQUALITY MATCHING RULE numericStringMatch -- from X.520 + ORDERING MATCHING RULE numericStringOrderingMatch -- from X.520 + SUBSTRINGS MATCHING RULE numericStringSubstringsMatch -- from X.520 + SINGLE VALUE TRUE + ID in-at-stopTime } + +location ATTRIBUTE ::= { + SUBTYPE OF telephoneNumber + SINGLE VALUE TRUE + ID in-at-location } +``` + +This Attribute requires additional set-up to restricts it's values to those contained in the Attribute regLocations. This will be done later with an Access Control Attribute in the entry containing both regLocations and location. + +## Data – Current Location + +The Current Location defines the registered location for a user. It has a specific lifetime. + +| | | | | | +|------------------|----------|--------------|--------|-------------------------| +| Current Location | Location | One per user | Search | Service: R
User: R/W | +|------------------|----------|--------------|--------|-------------------------| + +The definition of the Current Location attribute therefore becomes: + +``` + +currentLocation ATTRIBUTE ::= { + SUBTYPE OF telephoneNumber + SINGLE VALUE TRUE + ID in-at-cur-location } +``` + +This Attribute requires additional set-up to restrict its values to those contained in the Attribute regLocations. This will be done later with an Access Control Attribute in the entry containing both regLocations and currentLocation. + +The lifetime for this attribute is specified by providing the value with a temporal context with the endTime field set to the value of either Current Location Expiry or Default Expiry. The selection of which endTime to use is the responsibility of the function setting the attribute value5). + +#### Data – Current Location Expiry + +The Current Location Expiry data contains the expiration time for the current location data. + +| | | | | | +|-------------------------|-----------|--------------|------|-------------------------| +| Current Location Expiry | TimeOfDay | One per user | None | Service: R
User: R/W | +|-------------------------|-----------|--------------|------|-------------------------| + +Since the Current Expiry data is only used for setting the lifetime of the currentLocation Attribute, this data is not stored as a separate Attribute within the Directory. Instead, it is present as a TemporalContext value attached to the value of currentLocation. Note that this is an optionally supplied value from the User. If it is not supplied, then the value of Default Expiry is used instead. This selection is managed by the SCF-FEA responsible for managing the Attribute. + +#### Data – Default Expiry + +The Default Expiry data contains the default expiry time for the current location expiry data. + +| | | | | | +|----------------|-----------|--------------|------|-----------------------------------------------| +| Default Expiry | TimeOfDay | One per user | None | Service: R
User management: R/W
User: R | +|----------------|-----------|--------------|------|-----------------------------------------------| + +Since the Default Expiry data is only used as a default value for setting the lifetime of the currentLocation Attribute, this data is not stored as a separate Attribute within the Directory. Instead, it is present as a TemporalContext value attached to the value of currentLocation. Note that this value is only used if the User does not supply a value for Current Location Expiry. This selection is managed by the SCF-FEA responsible for managing the Attribute. + +#### Data – Default Location + +The Default Location defines the location to use if all other routing options fail. + +| | | | | | +|------------------|----------|--------------|--------|-----------------------------------------------| +| Default Location | Location | One per user | Search | Service: R
User management: R/W
User: R | +|------------------|----------|--------------|--------|-----------------------------------------------| + +The definition of the Default Location attribute therefore becomes: + +``` +defaultLocation ATTRIBUTE ::= { + SUBTYPE OF telephoneNumber + SINGLE VALUE TRUE + ID in-at-def-location } +``` + +5) While this may appear to require Service dependent information in the SCF-FEA responsible for managing the Attribute, the lifetime concept is sufficiently general (i.e. can be applied to a large number of attributes independently) that a standard mechanism can be developed to handle it in a service independent manner. + +This Attribute requires additional set-up to restricts it's values to those contained in the Attribute **regLocations**. This will be done later with an Access Control Attribute in the entry containing both **regLocations** and **defaultLocation**. + +#### Data – Incall Screen List + +The Incall Screen List defines a list of Locations, of specified maximum length, from which calls to the user are to be rejected. + +| | | | | | | +|--------------------|----------------------------------------|----------------------|--------|---------------------------------------|---------------| +| Incall Screen List | SET OF Location
SIZE 1..MaxListSize | One per service user | Search | Service:
User management:
User: | R
R/W
R | +|--------------------|----------------------------------------|----------------------|--------|---------------------------------------|---------------| + +The Incall Screen List can be considered in two ways, as a table with a single column or as an attribute with multiple values. In this case, since the operation only tests to see if specific values are present and does not retrieve the value, the multi-valued attribute version can be safely used. + +The definition of the Incall Screen List attribute therefore becomes: + +``` +incallScreenList ATTRIBUTE ::= { + SUBTYPE OF telephoneNumber, + ID in-at-incall-screen } +``` + +This attribute requires additional set-up to restrict the number of values which can be stored in the Attribute. This will be done later with an Access Control Attribute in the entry containing IncallScreenList. + +#### Data – MaxListSize + +The MaxListSize data holds the maximum length of the Incall Screen List. + +| | | | | | | +|-------------|---------|----------------------|------|---------------------------------|----------| +| MaxListSize | INTEGER | One per service user | None | Service:
Service management: | R
R/W | +|-------------|---------|----------------------|------|---------------------------------|----------| + +Since the MaxListSize data is only used as a value for the maximum number of values of the **IncallScreenList** Attribute, this data is not stored as a separate Attribute within the Directory. Instead, it is present as a Protected Item of type maxValueCount in an Access Control Attribute in the entry containing **IncallScreenList**. + +#### Data – User Id + +The User Id data defines the number used to identify the user of a service. When coupled to a service prefix (e.g. 014) it forms a Location. + +| | | | | | | +|---------|---------------|----------------------|------------|--------------------------------------------------------------|--------------------| +| User Id | ServiceNumber | One per service user | match/bind | Service management:
Service:
User management:
User: | R/W
R
R
R | +|---------|---------------|----------------------|------------|--------------------------------------------------------------|--------------------| + +The definition of the User Id attribute therefore becomes: + +``` +userId ATTRIBUTE ::= { + WITH SYNTAX NumericString + EQUALITY MATCHING RULE numericStringMatch -- from X.520 + ORDERING MATCHING RULE numericStringOrderingMatch -- from X.520 + SUBSTRINGS MATCHING RULE numericStringSubstringsMatch -- from X.520 + SINGLE VALUE TRUE + ID in-at-user-id } +``` + +## Data – User Password + +The User Password holds the PIN number of a user. It is used to validate registration and Outcall information. + +| | | | | | +|---------------|----------|----------------------|------------|-----------------------------------------------| +| User Password | Password | One per service user | match/bind | Service: R
User management: R/W
User: R | +|---------------|----------|----------------------|------------|-----------------------------------------------| + +Since this attribute is used in the Bind operation, the User Password must use the userPassword attribute definition defined in 6.3/X.509. + +## Data – Outcall Screen List + +The Outcall Screen List provides a list of barred locations for each registered location the user has. It is a table with two columns (regLocation, stopList). + +| | | | | | +|---------------------|------------------------------------------------------------------------------|----------------------|--------|---------------------------------| +| Outcall Screen List | SET OF {
SEQUENCE {
stopList SET OF Location,
location Location }}} | One per service user | Search | User management: R/W
User: R | +|---------------------|------------------------------------------------------------------------------|----------------------|--------|---------------------------------| + +Two attributes are defined for the Outcall Screen List: + +``` +outcallScreenLocation ATTRIBUTE ::= { + SUBTYPE OF telephoneNumber + SINGLE VALUE TRUE + ID in-at-outcall-location } +``` + +This Attribute requires additional set-up to restrict its values to those contained in the Attribute **regLocations**. This will be done later with an Access Control Attribute in the entry containing both **regLocations** and **outcallScreenLocation**. + +``` +outcallScreenStopList ATTRIBUTE ::= { + SUBTYPE OF telephoneNumber + ID in-at-outcall-stoplist } +``` + +## Data – Service Key + +The Service Key data identifies the Service being used. + +| | | | | | +|-------------|-----------|-----------------|------------|------------------------------------------------------------------------| +| Service Key | ServiceId | One per service | match/bind | Service management: R/W
Service: R
User management: R
User: R | +|-------------|-----------|-----------------|------------|------------------------------------------------------------------------| + +The definition of the Service Key attribute therefore becomes: + +``` +serviceKey ATTRIBUTE ::= { + WITH SYNTAX Object Identifier + SINGLE VALUE TRUE + ID in-at-service-key } +``` + +## Data – User Name + +The User Name data hold the name of the User of the Service. + +| | | | | | | +|-----------|--------|----------------------|-------|---------------------------|----------| +| User Name | String | One per service user | match | User management:
User: | R/W
R | +|-----------|--------|----------------------|-------|---------------------------|----------| + +The definition of the User Name attribute therefore becomes: + +``` + +userName ATTRIBUTE ::= { + SUBTYPE OF name, + ID in-at-user-name } + -- from X.520 + +``` + +### I.3.2.2 Selection of Object Classes + +Once the ATTRIBUTES have been selected, they can be organized into OBJECT-CLASSs. Using Guideline 5, the following attributes can be grouped together (attributes in [] denotes referenced attributes): + +- startDay, startTime, stopDay, stopTime, location, [regLocations]; +- outcallScreenLocation, outcallScreenStopList, [regLocations]. + +The remaining attributes must be grouped using Guideline-4. Since attributes which share the same cardinality can be said to share the same identity, the following groupings are used: + +- serviceKey; +- currentLocation, defaultLocation, incallScreenList, userId, userPassword, userName, [regLocations]. + +Attributes can be mandatory or optional within an object-class. From the description of the service logic it can be determined that the currentLocation, defaultLocation attributes are optional. Also, any attribute which is grouped as part of a table must be a mandatory attribute. Other attributes should be made mandatory as well. + +The OBJECT-CLASS definitions required are: + +``` + +serviceClass OBJECT-CLASS ::= { + MUST CONTAIN serviceKey + ID in-oc-service } + +serviceUserClass OBJECT-CLASS ::= { + MUST CONTAIN userId, userPassword, userName, incallScreenList, reqLocations, + MAY CONTAIN currentLocation, defaultLocation + ID in-o-service-user } + +timeOfDayLocation OBJECT-CLASS ::= { + MUST CONTAIN startDay, startTime, stopDay, stopTime, location, reqLocations + ID in-oc-time-location } + +outcallScreenList OBJECT-CLASS ::= { + MUST CONTAIN outcallScreenLocation, outcallScreenStopList, reqLocations + ID in-oc-outcall-screen } + +``` + +The definition of the Access Control Attributes used to handle Attribute Access Control has been deferred until the DIT design is complete (see I.3.2.4). + +Once the object classes have been defined, the naming attributes for the objects must be assigned. This requires the identification of one of the mandatory attributes which has a unique value for each occurrence of the object. + +Examining the objects defined, the following naming attributes can be used: + +| | | +|--------------------------|------------------------------| +| serviceClass | serviceKey | +| serviceUserClass | userId | +| timeOfDayLocation | ? (Nothing useable) | +| outcallScreenList | outcallScreenLocation | + +The only object class which has a naming problem is the timeOfDayLocation object. There are two ways around this problem. The first is to define a unique attribute (for example tableRowIndex) to allow naming. This does not affect performance of operations and can be useful in the management operation which are not being considered here. + +The second solution is to combine the StartDay, StartTime attributes into a composite attribute, the values of which would then be unique. This method would involve redefining MATCHING-RULEs and some extra processing. + +For simplicity the first solution is chosen. The required name forms, with new attribute and revised object-class, are: + +``` +tableRowIndex ATTRIBUTE ::= { + WITH SYNTAX Integer + SINGLE VALUE TRUE + ID in-at-maxListValues } + +timeOfDayLocation OBJECT-CLASS ::= { + MUST CONTAIN tableRowIndex, startDay, startTime, stopDay, stopTime, location, + regLocations + ID in-oc-time-location } + +serviceName NAME-FORM ::= { + NAMES serviceClass + WITH ATTRIBUTES serviceKey + ID in-nf-service-name } + +serviceUserName NAME-FORM ::= { + NAMES serviceUserClass + WITH ATTRIBUTES userId + ID in-nf-service-user-name } + +timeOfDayLocationName NAME-FORM ::= { + NAMES timeOfDayLocation + WITH ATTRIBUTES tableRowIndex + ID in-nf-tod-location-name } + +outcallScreenName NAME-FORM ::= { + NAMES outcallScreenList + WITH ATTRIBUTES outcallScreenLocation + ID in-nf-outcall-screen-name } +``` + +### I.3.2.3 Designing the Service DIT + +At this point the design of the DIT can begin. Looking at the cardinality information, the following OBJECT-CLASS relationships can be derived (see Figure I.4): + +![A diagram showing object-class relationships. A central oval labeled 'serviceUserClass' is connected to three other ovals: 'serviceClass' to its left, 'timeOfDayLocation' above it, and 'outcallScreenLocation' below it. The connections are lines with open arrowheads pointing towards the central 'serviceUserClass' oval.](45ac7625d3625e2a76f2bffd8447f431_img.jpg) + +``` +graph LR; serviceClass((serviceClass)) --> serviceUserClass((serviceUserClass)); timeOfDayLocation((timeOfDayLocation)) --> serviceUserClass; outcallScreenLocation((outcallScreenLocation)) --> serviceUserClass; +``` + +A diagram showing object-class relationships. A central oval labeled 'serviceUserClass' is connected to three other ovals: 'serviceClass' to its left, 'timeOfDayLocation' above it, and 'outcallScreenLocation' below it. The connections are lines with open arrowheads pointing towards the central 'serviceUserClass' oval. + +T1169790-94/d105 + +FIGURE I.4/Q.1218 +Object-Class Relationships + +Since serviceUserClass has two entry sets below it, Guideline 7 should be invoked which results in adding an extra object level, as shown in Figure I.5: + +![A hierarchical diagram showing object class relationships. At the top level is 'serviceClass'. Below it is 'serviceUserClass', connected by a line. From 'serviceUserClass', two lines branch down to 'tableHeadA' and 'tableHeadB'. 'tableHeadA' is connected to 'timeOfDayLocation', and 'tableHeadB' is connected to 'outcallScreenLocation'. All nodes are represented by ovals.](eaa8ee2530516c47ef4dcc8a5db20fd0_img.jpg) + +``` + +graph TD + serviceClass((serviceClass)) --- serviceUserClass((serviceUserClass)) + serviceUserClass --- tableHeadA((tableHeadA)) + serviceUserClass --- tableHeadB((tableHeadB)) + tableHeadA --- timeOfDayLocation((timeOfDayLocation)) + tableHeadB --- outcallScreenLocation((outcallScreenLocation)) + +``` + +A hierarchical diagram showing object class relationships. At the top level is 'serviceClass'. Below it is 'serviceUserClass', connected by a line. From 'serviceUserClass', two lines branch down to 'tableHeadA' and 'tableHeadB'. 'tableHeadA' is connected to 'timeOfDayLocation', and 'tableHeadB' is connected to 'outcallScreenLocation'. All nodes are represented by ovals. + +T1169800-94/d106 + +FIGURE I.5/Q.1218 +Object-Class Relationships after Guideline 7 + +This requires additional object class and attribute definitions. These are: + +``` + +tableHeadIdentifier ATTRIBUTE ::= { + WITH SYNTAX Integer + SINGLE VALUE TRUE + ID oi-gen-table-head } + +``` + +``` + +tableHead OBJECT-CLASS ::= { + MUST CONTAIN tableHeadIdentifier + ID in-oc-tableHead } + +``` + +``` + +tableHeadA OBJECT-CLASS ::= { + MUST CONTAIN tableHeadIdentifier + ID in-oc-tableHeadA } + +``` + +``` + +tableHeadA NAME-FORM ::= { + NAMES tableHeadA + WITH ATTRIBUTES tableHeadIdentifier + ID in-nf-tableHeadNameA } + +``` + +``` + +tableHeadB OBJECT-CLASS ::= { + MUST CONTAIN tableHeadIdentifier + ID in-oc-tableHeadB } + +``` + +``` + +tableHeadNameB NAME-FORM ::= { + NAMES tableHeadB + WITH ATTRIBUTES tableHeadIdentifier + ID in-nf-tableHeadNameB } + +``` + +Therefore the structure rules required to define the DIT structure are: + +``` + +sr-root STRUCTURE-RULE ::= { + NAME FORM serviceClassName + ID sr0 } + +``` + +``` + +sr-user STRUCTURE-RULE ::= { + NAME FORM serviceClassName + SUPERIOR RULES sr0 + ID sr1 } + +sr-tableA STRUCTURE-RULE ::= { + NAME FORM tableHeadNameA + SUPERIOR RULES sr1 + ID sr2 } + +sr-tod-location STRUCTURE-RULE ::= { + NAME FORM timeOfDayLocationName + SUPERIOR RULES sr2 + ID sr3 } + +sr-tableB STRUCTURE-RULE ::= { + NAME FORM tableHeadNameB + SUPERIOR RULES sr1 + ID sr4 } + +sr-outcall-screen STRUCTURE-RULE ::= { + NAME FORM outcallScreenListName + SUPERIOR RULES sr4 + ID sr5 } + +``` + +The creation of an Entry of OBJECT-CLASS subEntry holds the specification of the sub-tree to which the collective attributes apply. For the case of the regLocations collective attribute the subEntry is subordinate to an Entry of the OBJECT-CLASS serviceUserClass. + +To modify the regLocation Attribute requires the Distinguished Name of the subEntry to be supplied (see Figure I.6). + +![A tree diagram showing the hierarchy of service classes and their sub-entries. At the top level is 'serviceClass', which points to 'serviceUserClass'. 'serviceUserClass' branches into three sub-entries: 'tableHeadA', 'subEntry', and 'tableHeadB'. 'tableHeadA' points to 'timeOfDayLocation', and 'tableHeadB' points to 'outcallScreenLocation'.](c52ea16bac02e546d0c5767db5dd4981_img.jpg) + +``` + +graph TD + serviceClass((serviceClass)) --> serviceUserClass((serviceUserClass)) + serviceUserClass --> tableHeadA((tableHeadA)) + serviceUserClass --> subEntry((subEntry)) + serviceUserClass --> tableHeadB((tableHeadB)) + tableHeadA --> timeOfDayLocation((timeOfDayLocation)) + tableHeadB --> outcallScreenLocation((outcallScreenLocation)) + +``` + +T1180020-96/d107 + +A tree diagram showing the hierarchy of service classes and their sub-entries. At the top level is 'serviceClass', which points to 'serviceUserClass'. 'serviceUserClass' branches into three sub-entries: 'tableHeadA', 'subEntry', and 'tableHeadB'. 'tableHeadA' points to 'timeOfDayLocation', and 'tableHeadB' points to 'outcallScreenLocation'. + +FIGURE I.6/Q.1218 +**Directory Tree showing sub-entry location** + +### I.3.2.4 Assigning Access control + +Note that the DIT is complete, the next required step is to define the Access Control Attribute values for each of the Entries in the DIT. An Entry's Access Control Attribute (entryACI, see 16.5.2/X.501) contains values of type ACIItem which control how the user may access the Attribute values. The following table defines the Access Control required for each of the attributes defined within the DIT. + +| Object | Attribute | UserClasses defined by X.500 Management | | | | | Special Protected Items | +|-----------------------|-------------------------|-----------------------------------------|----------|-------------|---------|-------------|-------------------------| +| | | User-X | AllUsers | User Mgt | Service | Service Mgt | | +| serviceClass | serviceKey | +R+F | +F | +R+F | +R+F | +R+A+D+F | | +| serviceUserClass | userId | +R+F | +F | +R+F | +R+F | +R+A+D+F | | +| | userPassword | +R+F+C | | +R+A+D+F | +R+F | +R+F | | +| | userName | +R+F+C | | +R+A+D+F | +R+F | +R+F | | +| | incallScreenList | +R+F | | +R+A+D+F(*) | +R+F | +R+F | maxValueCount | +| | currentLocation | +R+A+D+F(*) | | +R+F | +R+F | +R+F | restrictedBy | +| | defaultLocation | +R+A+D+F(*) | | +R+F | +R+F | +R+F | restrictedBy | +| tableHeadA | tableHead Identifier | +R+F | | +R+F | +R+F | +R+A+D+F | | +| timeOfDay Location | tableRowIndex | +R+F | | +R+A+D+F | +R+F | +R+F | | +| | startDay | +R+F | | +R+A+D+F | +R+F | +R+F | | +| | startTime | +R+F | | +R+A+D+F | +R+F | +R+F | | +| | stopDay | +R+F | | +R+A+D+F | +R+F | +R+F | | +| | stopTime | +R+F | | +R+A+D+F | +R+F | +R+F | | +| | location | +R+F | | +R+A+D+F(*) | +R+F | +R+F | restrictedBy | +| tableHeadB | tableHead_ Identifier | +R+F | | +R+F | +R+F | +R+A+D+F | | +| outcallScreenList | outcallScreen_ Location | +R+F | | +R+A+D+F(*) | +R+F | +R+F | restrictedBy | +| | outcallScreen_ StopList | +R+F | | +R+A+D+F | +R+F | +R+F | | +| serviceUser_ Subentry | regLocations | +R+F | | +R+A+D+F | +R+F | +R+F | | + ++ Grant permission + +A Add attribute to entry + +M Modify attribute + +– Deny permission + +R Read access + +C Compare attribute + +\* Special protected item + +D Remove access + +F Filter match attribute + +Each table column under UserClasses denotes a potential ACIItem value for the entryACI attribute. In practice the values can be combined in a single ACIItem which combines a set of protected items which have the same access permissions for a set of UserClasses. Each ACIItem has a unique identifier field, which can be used to apply Access Control to individual values of the Access Control Attribute itself. This allows different "Users" to modify different Access Control values (which may contain permitted value or size limits) without being able to change other values of the Access Control attribute. + +Where permissions are marked with a (\*) this indicates that a special Protected Item of the type specified in the last column (Special Protected Items) must be included in the ACIItem to handle permitted value or value count limit controls. + +#### I.4 Defining Contexts + +This subclause defines a set of Context types which may be found useful across of range on IN services. + +#### **I.4.1 Numerical Index Attribute Value Context** + +The Numerical Index Attribute Value Context associates a numerical index with an attribute value. + +``` +numericalIndexAVC ATTRIBUTE-VALUE-CONTEXT ::= { + SYNTAX INTEGER + id id-avc-numericalIndex } +``` + +An example of use of the numerical index attribute value context is an "abbreviated to expanded number" conversion table, where the index (the context value) is the abbreviated number and the attribute value the expanded number. + +Note that a similar String Index Attribute Value Context type could also be defined. + +## **Appendix II** + +### **Aspects of the intelligent network interface identified as "For Further Study" (FFS) relative to CS-1** + +(This appendix does not form an integral part of this Recommendation) + +#### **II.1 General** + +##### **II.1.1 General consideration** + +This appendix includes call party handling and other issues which were considered to be incomplete when developing the Q.1218 intelligent network interface Recommendation CS-1. Although the material in this appendix is built upon CS-1, the procedures for these capabilities may be undefined and FFS relative to CS-1. The material is included in this appendix to provide some technical basis for future work. + +##### **II.1.2 Relationship to other appendices of the Q.1200-Series Recommendations** + +This appendix only applies to Q.1218 intelligent network interface Recommendation CS-1. Each of the Q.1200-Series Recommendations includes a specific appendix, if needed. + +##### **II.1.3 Format of Document** + +This introduction provides an explanation of the purpose and scope of the appendix: + +- Subclause II.2 itemizes the operations. +- Subclause II.3 itemizes the parameters. +- Subclause II.4 is an ASN.1 module of the operations and parameters. +- Subclause II.5 includes procedures for the operations. + +#### **II.2 Operations** + +The operations listed in this subclause are in addition to the operations itemized in clause 2. + +##### **II.2.1 Consideration applicable to all operations in this appendix** + +The following operations or aspects of the operations are FFS relative to CS-1. These operations rely on CS-1 capabilities for which the corresponding procedures are undefined. Therefore, they are included in this appendix for completeness. + +The defined defaults may be incomplete (e.g. Leg ID) and may be dependent on the point in call (PIC). + +## **II.2.2 Add party operation** + +### **II.2.2.1 Consideration** + +The difference between this operation and the attach operation needs to be clarified. + +### **II.2.2.2 Description** + +SCF → SSF + +This operation is used to perform the call processing actions to add all call party connections from one call to another call, then clear the first call (e.g. to create a conference call). From the perspective of the controlling party, this operation effectively bridges two calls. + +## **II.2.3 Attach operation** + +### **II.2.3.1 Consideration** + +The difference between this operation and the add party operation needs to be clarified. + +### **II.2.3.2 Description** + +SCF → SSF + +This operation enables the SCF to request the SSF to include a leg in the current relationship instance. The leg is transferred from another relationship instance, from which it was removed using the detach operation. Notice that detach may also be executed after attach using the same absolute identifier. + +## **II.2.4 Change parties operation** + +### **II.2.4.1 Description** + +SCF → SSF + +This operation is used to perform the call processing actions to change a particular party connection from one call to another call. From the perspective of the particular call party, this operation effectively places the first call on hold and retrieves the associated call from hold. + +## **II.2.5 Detach operation** + +### **II.2.5.1 Consideration** + +The difference between this operation and the release call party operation needs to be clarified. + +### **II.2.5.2 Description** + +SCF → SSF + +This operation enables the SCF to request the SSF to remove a leg from one relationship instance and to assign it an absolute (i.e. single network-wide) identifier (Correlation identifier), so that it can be transferred to another relationship instance, to which the leg was/will be attached by means of the attach operation using the same absolute identifier. + +## **II.2.6 Hold call party connection operation** + +### **II.2.6.1 Description** + +SCF → SSF + +This operation is used during the active phase of a call between two or more parties to put one party connection on hold. + +## **II.2.7 Initiate call attempt operation (for case of more than 1 party)** + +### **II.2.7.1 Consideration** + +This information flow is included in the main body of Recommendation Q.1214, for the case of creating a call to one call party. The IF is listed in this appendix for the case of creating a call to more than one party, in the same call, which for CS-1 is FFS. + +### **II.2.7.2 Description** + +SCF → SSF + +This operation is used to request the SSF to create a new call to one or more parties using address information provided by the SCF (e.g. predefined conference call, previous prompt and collect information). Any errors associated with performing this operation are returned. + +## **II.2.8 Reconnect operation** + +### **II.2.8.1 Description** + +SCF → SSF + +This operation is used to resume a held party to a call (inverse of hold call party connection). + +## **II.2.9 Release call party connection operation** + +### **II.2.9.1 Consideration** + +The difference between this operation and the detach operation needs to be clarified. + +### **II.2.9.2 Description** + +SCF → SSF + +This operation is used to release a call party connection during a call between two or more parties. + +## **II.3 Parameters** + +The parameters listed in this subclause are additional parameters for the operations itemized in clause 2. + +### **II.3.1 Considerations applicable to all parameters in this appendix** + +The following parameters are FFS relative to CS-1. These parameters rely on CS-1 capabilities for which the corresponding procedures are undefined. Therefore, they are included in this appendix for completeness. + +### **II.3.2 Leg Id created parameter (from Analyse information operation)** + +#### **II.3.2.1 Description** + +DEFAULT bPARTY + +Indicates a reference to a specific party in a call. OPTIONAL denotes network operator specific use with a choice of unilateral ID assignment or bilateral ID assignment. + +### **II.3.3 Leg Id created parameter (from connect operation)** + +#### **II.3.3.1 Description** + +DEFAULT bPARTY + +Indicates a reference to a specific party in a call. OPTIONAL denotes network operator specific use with a choice of unilateral ID assignment or bilateral ID assignment. + +### **II.3.4 Leg Id created parameter (from initiate call attempt operation)** + +#### **II.3.4.1 Description** + +DEFAULT bPARTY + +Indicates a reference to a specific party in a call. OPTIONAL denotes network operator specific use with a choice of unilateral ID assignment or bilateral ID assignment. + +### **II.3.5 Leg Id created parameter (from select facility operation)** + +#### **II.3.5.1 Description** + +DEFAULT bPARTY + +Indicates a reference to a specific party in a call. OPTIONAL denotes network operator specific use with a choice of unilateral ID assignment or bilateral ID assignment. + +### **II.3.6 Leg Id created parameter (from select route operation)** + +#### **II.3.6.1 Description** + +DEFAULT bPARTY + +Indicates a reference to a specific party in a call. OPTIONAL denotes network operator specific use with a choice of unilateral ID assignment or bilateral ID assignment. + +### **II.3.7 Leg 1 parameter (from initial DP operation)** + +#### **II.3.7.1 Description** + +DEFAULT {aPARTY, pending} + +Indicates call party information, as defined by a Leg object. This includes a LegID to reference each call party, and a LegStatus to indicate whether the call party is connected or not. + +### **II.3.8 Leg 2 Parameter (from initial DP operation)** + +#### **II.3.8.1 Description** + +OPTIONAL + +Indicates call party information, as defined by a Leg Object. This includes a LegID to reference each call party, and a LegStatus to indicate whether the call party is connected or not. + +### **II.3.9 Call Id Parameter** + +#### **II.3.9.1 Description** + +Indicates an identifier to reference an instance of a Call accessible to the SCF. Refer to 4.2.2.1/Q.1214 for a description of call segment. + +## **II.4 ASN.1 module of operations and parameters** + +The following modules describe the additional operations discussed in this appendix. The modules do not describe the modifications to the operations in clause 2 to include the leg parameters discussed in subclause II.3. + +### **II.4.1 Abstract syntax of the IN CS-1 application protocol – Appendix** + +This subclause specifies additional abstract syntax for the IN CS-1 application protocol using Abstract Syntax Notation One (ASN.1), defined in Recommendation X.208. + +The material in this appendix is based on the appendix material in Recommendation Q.1214. + +#### *Operation types* + +**IN-CS-1-Operations-appendix { ccitt recommendation q 1218 modules(0) cs-1-operations-app(4) version1(0) }** + +*-- This module contains additional type definitions for IN CS-1 operations.* + +**DEFINITIONS IMPLICIT TAGS ::=** + +**BEGIN** + +**IMPORTS** + +**OPERATION, +ERROR** + +**FROM TCAPMessages { ccitt recommendation q 773 modules(0) messages(1) version2(2) };** + +*-- TYPE DEFINITION FOR ADDITIONAL IN CS-1 OPERATIONS* + +*-- SCF-SSF operations* + +**AddParty ::= OPERATION** + +**ARGUMENT** + +**AddPartyArg** + +**RESULT** + +**CallPartyHandlingResultsArg** + +**ERRORS {** + +**DataAlreadyExists, +MissingParameter, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter** +**}** + +*-- SCF → SSF* + +*-- This operation is used to perform the call processing actions to add all call party connections* + +*-- from one Call to another Call, then clear the first Call (e.g. to create a conference call).* + +*-- From the perspective of the controlling party, this operation effectively bridges two Calls.* + +**Attach ::= OPERATION** + +**ARGUMENT** + +**AttachArg** + +**ERRORS {** + +**DataAlreadyExists, +LegIDAlreadyAssigned, +MissingParameter, +SystemFailure, +TaskRefused, +TooLate, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter** +**}** + +*-- SCF → SSF* + +*-- This operation is used to attach two Calls.* + +**ChangeParties ::= OPERATION** + +**ARGUMENT** + +**ChangePartiesArg** + +**RESULT** + +**CallPartyHandlingResultsArg** + +**ERRORS {** + +**DataAlreadyExists, +MissingParameter, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter** +**}** + +- SCF → SSF +- *This operation is used to perform the call processing actions to change a particular party connection from one Call to another Call. From the perspective of the particular call party, this operation effectively places the first Call on hold and retrieves the associated Call from hold.* + +**Detach ::= OPERATION** + +**ARGUMENT** + +**DetachArg** + +**ERRORS {** + +DataAlreadyExists, +MissingParameter, +SystemFailure, +TaskRefused, +TooLate, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter, +UnknownLegID +} + +- SCF → SSF +- *This operation is used to detach two Calls.* + +**HoldCallPartyConnection ::= OPERATION** + +**ARGUMENT** + +**HoldCallPartyConnectionArg** + +**RESULT** + +**CallPartyHandlingResultsArg** + +**ERRORS {** + +DataUnavailable, +MissingParameter, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- SCF → SSF +- *This operation is used during the active phase of a call between two or more parties to put one party connection on hold.* + +**Reconnect ::= OPERATION** + +**ARGUMENT** + +**ReconnectArg** + +**RESULT** + +**CallPartyHandlingResultsArg** + +**ERRORS {** + +DataAlreadyExists, +MissingParameter, +SystemFailure, +TaskRefused, +UnexpectedComponentSequence, +UnexpectedDataValue, +UnexpectedParameter +} + +- SCF → SSF +- *This operation is used to resume a held party to a call (inverse of HoldCallPartyConnection).* + +**ReleaseCallPartyConnection ::= OPERATION** + +**ARGUMENT** + +**ReleaseCallPartyConnectionArg** + +**RESULT** + +**CallPartyHandlingResultsArg** + +**ERRORS {** + +DataAlreadyExists, +MissingParameter, +SystemFailure, + +``` + + TaskRefused, + UnexpectedComponentSequence, + UnexpectedDataValue, + UnexpectedParameter + } + +``` + +-- SCF → SSF + +-- *This operation is used to release a call party connection during a call between two or more parties.* + +END + +IN-CS-1-Errors-appendix { ccitt recommendation q 1218 modules(0) cs-1-errors-app(5) version1(0) } + +-- *This module contains additional type definitions for the IN CS-1 errors.* + +DEFINITIONS IMPLICIT TAGS ::= + +BEGIN + +IMPORTS + +    ERROR + +FROM TCAPMessages { ccitt recommendation q 773 modules(0) messages(1) version2(2) }; + +-- TYPE DEFINITION FOR IN CS-1 ERRORS + +LegIDAlreadyAssigned ::= ERROR + +-- *Indicates that a legID has already been assigned with the requested value.* + +TooLate ::= ERROR + +-- *Indicates that the operation could not be performed in a timely manner.* + +UnknownLegID ::= ERROR + +-- *Indicates that the legID does not exist.* + +END + +*Data types* + +IN-CS-1-DataTypes-appendix { ccitt recommendation q 1218 modules(0) cs-1-datatypes-app(6) version1(0) } + +-- *This module contains additional type definitions for the IN CS-1 data types.* + +DEFINITIONS IMPLICIT TAGS ::= + +BEGIN + +-- TYPE DEFINITION FOR ADDITIONAL IN CS-1 DATA TYPES + +-- *Argument Data Types* + +AddPartyArg ::= SEQUENCE { + +| | | | | +|-------------------|-----|--------|-----------| +| originalCallID | [0] | CallID | OPTIONAL, | +| destinationCallID | [1] | CallID | OPTIONAL | + +} + +-- *OPTIONAL denotes network operator specific use.* + +AttachArg ::= SEQUENCE { + +| | | | | +|-----------------------|-----|---------------|-----------| +| newLegID | [0] | LegID | OPTIONAL, | +| correlationidentifier | [1] | CorrelationID | OPTIONAL | + +} + +-- *OPTIONAL denotes network operator specific use.* + +CallPartyHandlingResultsArg ::= SEQUENCE OF LegInformation + +ChangePartiesArg ::= SEQUENCE { + +| | | | | +|--------------------|-----|---------|-----------| +| callID | [0] | CallID | OPTIONAL, | +| targetCallID | [1] | CallID, | | +| legToBeConnectedID | [2] | LegID | | + +} + +-- *OPTIONAL denotes network operator specific use.* + +DetachArg ::= SEQUENCE { + +| | | | | +|-----------------------|-----|---------------|-----------| +| legToBeDetached | [0] | LegID | OPTIONAL, | +| correlationidentifier | [1] | CorrelationID | OPTIONAL | + +} + +-- *OPTIONAL denotes network operator specific use.* + +``` + +HoldCallPartyConnectionArg ::= SEQUENCE { + callID [0] CallID OPTIONAL, + legID [1] LegID + } + +``` + +-- OPTIONAL denotes network operator specific use. + +``` + +ReconnectArg ::= SEQUENCE { + callID [0] CallID OPTIONAL, + heldLegID [1] LegID + } + +``` + +-- OPTIONAL denotes network operator specific use. + +``` + +ReleaseCallPartyConnectionArg ::= SEQUENCE { + legToBeReleased [0] LegID, + callID [1] CallID OPTIONAL, + releaseCause [2] Cause OPTIONAL + } + +``` + +-- OPTIONAL denotes network operator specific use. Common Data Types + +**CallID ::= INTEGER** + +-- Indicates an identifier to reference an instance of a Call accessible to the SCF. Refer to + +-- 4.2.2.1/Q.1214 for a description of Call Segment. + +**Cause ::= OCTET STRING** + +-- Indicates the cause for interface related information. Refer to the Q.763 Cause parameter + +-- for encoding. + +``` + +LegInformation ::= SEQUENCE { + legID [0] LegID, + legStatus [1] LegStatus + } + +``` + +-- Indicates call party information, as defined by a Leg object. This includes a LegID to reference + +-- each call party, and a LegStatus to indicate whether the call party is connected or not. + +``` + +LegStatus ::= ENUMERATED { + connected(0), + unconnected(1), + pending(2), + interacting(3) -- user connected to a resource + } + +``` + +-- Indicates the state of the call party. + +**END** + +*Application Protocol (Operation and Error Codes)* + +IN-CS1-Codes-appendix { ccitt recommendation q 1218 modules(0) cs-1-codes-app(7) version1(0) } + +**DEFINITIONS IMPLICIT TAGS ::=** + +**BEGIN** + +-- OPERATION AND ERROR CODE DEFINITION + +-- Code point values are for further study. The operations are grouped by the identified ASEs. + +-- Call party handling ASE + +``` + +addParty AddParty ::= ffs +changeParties ChangeParties ::= ffs +holdCallPartyConnection HoldCallPartyConnection ::= ffs +reconnect Reconnect ::= ffs +releaseCallPartyConnection ReleaseCallPartyConnection ::= ffs +-- Attach ASE +attach Attach ::= ffs +detach Detach ::= ffs + +``` + +**END** + +## II.5 Procedures + +PRINCIPLE is as follows: + +The SSF procedures are illustrated by means of Finite State Machines (FSMs). + +The (call level) finite state machine, presently described in this Recommendation, consists of several states, which represent different states of the call. + +In some of the call states, another level of finite state machine(s) exists, which will have to be described, and which represents the state of a connection to one of the parties. This FSM is named "leg level FSM". + +Such a "leg level FSM" is "born out" or "dies out" of some of the call level FSM transitions. Any "event" (e.g. an operation received) causes a state transition of all relevant FSMs. + +The Leg states used are the possible values of the parameter "LegStatus", are the following: + +- "IDLE": connection to the party does not exist; +- "PENDING": party not connected, and under creation process; +- "UNCONNECTED": party not connected, but in a stable state; +- "CONNECTED": party connected to another party; +- "INTERACTING": party connected to an SRF. + +## Appendix III Expanded ASN.1 coding + +(This appendix does not form an integral part of this Recommendation) + +This appendix contains the expanded ASN.1 source of the SCF/SSF/SRF interface. + +For ASN.1 type definitions see 2.1. + +### NOTES + +- 1 "???" as a range value means a network specific value. +- 2 The operations are arranged alphabetically. + +### activateServiceFiltering OPERATION + +#### ARGUMENT + +##### SEQUENCE { + +###### filteredCallTreatment [0] IMPLICIT SEQUENCE { + +###### sFBillingChargingCharacteristics [0] IMPLICIT OCTET STRING (SIZE (??..??)), + +###### informationToSend [1] CHOICE { + +###### inbandInfo [0] IMPLICIT SEQUENCE { + +###### messageID [0] CHOICE { + +###### elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + +###### text [1] IMPLICIT SEQUENCE { + +###### messageContent [0] IMPLICIT IA5String (SIZE (??..??)), + +###### attributes [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL,} + +``` + +elementaryMessageIDs [29] IMPLICIT SEQUENCE SIZE (1..??) OF + INTEGER (0..2147483647), +variableMessage [30] IMPLICIT SEQUENCE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + variableParts [1] IMPLICIT SEQUENCE SIZE (1..5) OF + CHOICE { + integer [0] IMPLICIT INTEGER (0..2147483647), + number [1] IMPLICIT OCTET STRING (SIZE (??..??)), + time [2] IMPLICIT OCTET STRING (SIZE (2)), + date [3] IMPLICIT OCTET STRING (SIZE (3)), + price [4] IMPLICIT OCTET STRING (SIZE (4))}}, + numberOfRepetitions [1] IMPLICIT INTEGER (1..127) OPTIONAL, + duration [2] IMPLICIT INTEGER (0..32767) OPTIONAL, + interval [3] IMPLICIT INTEGER (0..32767) OPTIONAL}, + tone [1] IMPLICIT SEQUENCE { + toneID [0] IMPLICIT INTEGER (0..2147483647), + duration [1] IMPLICIT INTEGER (0..2147483647) OPTIONAL}, + displayInformation [2] IMPLICIT IA5String (SIZE (??..??)) OPTIONAL, + maximumNumberOfCounters [2] IMPLICIT INTEGER (1..100) OPTIONAL, + releaseCause [3] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL}, +filteringCharacteristics [1] CHOICE { + interval [0] IMPLICIT INTEGER (-1..32000), + numberOfCalls [1] IMPLICIT INTEGER (0..2147483647)}, +filteringTimeout [2] CHOICE { + duration [0] IMPLICIT INTEGER (-2..86400), + stopTime [1] IMPLICIT OCTET STRING (SIZE (6))}, +filteringCriteria [3] CHOICE { + dialledNumber [0] IMPLICIT OCTET STRING (SIZE (??..??)), + callingLineID [1] IMPLICIT OCTET STRING (SIZE (??..??)), + serviceKey [2] IMPLICIT INTEGER (0..2147483647), + addressAndService [30] IMPLICIT SEQUENCE { + calledAddressValue [0] IMPLICIT OCTET STRING (SIZE (??..??)), + serviceKey [1] IMPLICIT INTEGER (0..2147483647), + callingAddressValue [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + locationNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}}, + startTime [4] IMPLICIT OCTET STRING (SIZE (6)) OPTIONAL, + extensions [5] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +#### ERRORS { + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedParameter -- localValue 16} +::= localValue 42 + +``` + +#### activityTest OPERATION + +``` +::= localValue 55 +``` + +#### analysedInformation OPERATION + +##### ARGUMENT + +``` + +SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + +``` + +``` + +dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, +triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, +bearerCapability [1] CHOICE { + bearerCap[0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, +iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, +cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, +locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, +terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF +SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, +chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, +dialledDigits [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyBusinessGroupID [2] IMPLICIT OCTET STRING OPTIONAL, +callingPartySubaddress [3] IMPLICIT OCTET STRING OPTIONAL, +callingFacilityGroup [4] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, +callingFacilityGroupMember [5] IMPLICIT INTEGER OPTIONAL, +originalCalledPartyID [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +prefix [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectingPartyID [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectionInformation [9] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, +routeList [10] IMPLICIT SEQUENCE SIZE (1..3) OF + +``` + +``` + +OCTET STRING (SIZE (??..??)) OPTIONAL, +travellingClassMark [11] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF +SEQUENCE { +type INTEGER, +criticality ENUMERATED { +inore (0), +abort (1)} DEFAULT ignore , +value [1] ANY DEFINED BY type } OPTIONAL, +featureCode [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +accessCode [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +carrier [15] IMPLICIT OCTET STRING OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 3 + +``` + +**analyseInformation OPERATION** + +**ARGUMENT** + +``` + +SEQUENCE { +destinationRoutingAddress [0] IMPLICIT SEQUENCE SIZE (1..3) OF +OCTET STRING (SIZE (??..??)), +alertingPattern [1] IMPLICIT OCTET STRING (SIZE (3)) OPTIONAL, +iSDNAccessRelatedInformation [2] IMPLICIT OCTET STRING OPTIONAL, +originalCalledPartyID [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +extensions [4] IMPLICIT SEQUENCE SIZE (1..??) OF +SEQUENCE { +type INTEGER, +criticality ENUMERATED { +ignore (0), +abort (1)} DEFAULT ignore , +value [1] ANY DEFINED BY type } OPTIONAL, +callingPartyNumber [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartysCategory [6] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, +calledPartyNumber [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +chargeNumber [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +travellingClassMark [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +carrier [10] IMPLICIT OCTET STRING OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 28 + +``` + +**applyCharging OPERATION** + +**ARGUMENT** + +``` + +SEQUENCE { +aChBillingChargingCharacteristics [0] IMPLICIT OCTET STRING (SIZE (??..??)), +partyToCharge [2] CHOICE { +sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), +receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +extensions [3] IMPLICIT SEQUENCE SIZE (1..??) OF +SEQUENCE { +type INTEGER, +criticality ENUMERATED { +ignore (0), +abort (1)} DEFAULT ignore , +value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +``` + +ERRORS { +-- missingParameter -- localValue 7, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedParameter -- localValue 16, +-- unexpectedDataValue -- localValue 15, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12} +::= localValue 35 + +applyChargingReport OPERATION +ARGUMENT + OCTET STRING (SIZE (??..??)) +ERRORS { +-- missingParameter -- localValue 7, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedParameter -- localValue 16, +-- unexpectedDataValue -- localValue 15, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12} +::= localValue 36 + +assistRequestInstructions OPERATION +ARGUMENT + SEQUENCE { + correlationID [0] IMPLICIT OCTET STRING (SIZE (??..??)), + iPAvailable [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPSSPCapabilities [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [3] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 16 + +callGap OPERATION +ARGUMENT + SEQUENCE { + gapCriteria [0] CHOICE { + calledAddressValue [0] IMPLICIT OCTET STRING (SIZE (??..??)), + gapOnService [2] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647), + dpCriteria [1] IMPLICIT ENUMERATED { + origAttemptAuthorized (1), + collectedInfo (2), + analysedInformation (3), + routeSelectFailure (4), + oCalledPartyBusy (5), + oNoAnswer (6), + oAnswer (7), + oMidCall (8), + oDisconnect (9), + oAbandon (10), + termAttemptAuthorized (12), + tBusy (13), + tNoAnswer (14), + } + } + } + } + +``` + +``` + +tAnswer (15), +tMidCall (16), +tDisconnect (17), +tAbandon (18)} OPTIONAL}, +calledAddressAndService [29] IMPLICIT SEQUENCE { + calledAddressValue [0] IMPLICIT OCTET STRING (SIZE (??..??)), + serviceKey [1] IMPLICIT INTEGER (0..2147483647)}, +callingAddressAndService [30] IMPLICIT SEQUENCE { + callingAddressValue [0] IMPLICIT OCTET STRING (SIZE (??..??)), + serviceKey [1] IMPLICIT INTEGER (0..2147483647), + locationNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}}, +gapIndicators [1] IMPLICIT SEQUENCE { + duration [0] IMPLICIT INTEGER (-2..86400), + gapInterval [1] IMPLICIT INTEGER (-1..60000)}, +controlType [2] IMPLICIT ENUMERATED { + sCPOverloaded (0), + manuallyInitiated (1), + destinationOverload (2)} OPTIONAL, +gapTreatment [3] CHOICE { + informationToSend [0] CHOICE { + inbandInfo [0] IMPLICIT SEQUENCE { + messageID [0] CHOICE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + text [1] IMPLICIT SEQUENCE { + messageContent [0] IMPLICIT IA5String (SIZE (??..??)), + attributes [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + elementaryMessageIDs [29] IMPLICIT SEQUENCE SIZE (1..??) OF + INTEGER (0..2147483647), + variableMessage [30] IMPLICIT SEQUENCE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + variableParts [1] IMPLICIT SEQUENCE SIZE (1..5) OF + CHOICE { + integer [0] IMPLICIT INTEGER (0..2147483647), + number [1] IMPLICIT OCTET STRING (SIZE (??..??)), + time [2] IMPLICIT OCTET STRING (SIZE (2)), + date [3] IMPLICIT OCTET STRING (SIZE (3)), + price [4] IMPLICIT OCTET STRING (SIZE (4))}}}, + numberOfRepetitions [1] IMPLICIT INTEGER (1..127) OPTIONAL, + duration [2] IMPLICIT INTEGER (0..32767) OPTIONAL, + interval [3] IMPLICIT INTEGER (0..32767) OPTIONAL, + tone [1] IMPLICIT SEQUENCE { + toneID [0] IMPLICIT INTEGER (0..2147483647), + duration [1] IMPLICIT INTEGER (0..2147483647) OPTIONAL}, + displayInformation [2] IMPLICIT IA5String (SIZE (??..??)), + releaseCause [1] IMPLICIT OCTET STRING (SIZE (2..??)), + both [2] IMPLICIT SEQUENCE { + informationToSend [0] CHOICE { + inbandInfo [0] IMPLICIT SEQUENCE { + messageID [0] CHOICE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + text [1] IMPLICIT SEQUENCE { + messageContent [0] IMPLICIT IA5String (SIZE (??..??)), + attributes [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + elementaryMessageIDs [29] IMPLICIT SEQUENCE SIZE (1..??) OF + INTEGER (0..2147483647), + variableMessage [30] IMPLICIT SEQUENCE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + variableParts [1] IMPLICIT SEQUENCE SIZE (1..5) OF + CHOICE { + integer [0] IMPLICIT INTEGER (0..2147483647), + number [1] IMPLICIT OCTET STRING (SIZE (??..??)), + time [2] IMPLICIT OCTET STRING (SIZE (2)), + date [3] IMPLICIT OCTET STRING (SIZE (3)), + price [4] IMPLICIT OCTET STRING (SIZE (4))}}}, + numberOfRepetitions [1] IMPLICIT INTEGER (1..127) OPTIONAL, + duration [2] IMPLICIT INTEGER (0..32767) OPTIONAL, + interval [3] IMPLICIT INTEGER (0..32767) OPTIONAL, + } + } + } +} + +``` + +``` + +tone [1] IMPLICIT SEQUENCE { + toneID [0] IMPLICIT INTEGER (0..2147483647), + duration [1] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + displayInformation [2] IMPLICIT IA5String (SIZE (??..??)), + releaseCause [1] IMPLICIT OCTET STRING (SIZE (2..??))} + OPTIONAL, +extensions [4] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} +::= localValue 41 + +``` + +**callInformationReport OPERATION** + +**ARGUMENT** + +``` + +SEQUENCE { + requestedInformationList [0] IMPLICIT SEQUENCE SIZE (1..5) OF + SEQUENCE { + requestedInformationType [0] IMPLICIT ENUMERATED { + callAttemptElapsedTime (0), + callStopTime (1), + callConnectedElapsedTime (2), + calledAddress (3), + releaseCause (30)}, + requestedInformationValue [1] CHOICE { + callAttemptElapsedTimeValue [0] IMPLICIT INTEGER (0..255), + callStopTimeValue [1] IMPLICIT OCTET STRING (SIZE (6)), + callConnectedElapsedTimeValue [2] IMPLICIT INTEGER (0..2147483647), + calledAddressValue [3] IMPLICIT OCTET STRING (SIZE (??..??)), + releaseCauseValue [30] IMPLICIT OCTET STRING (SIZE (2..??))}, + correlationID [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [2] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + } +::= localValue 44 + +``` + +**callInformationRequest OPERATION** + +**ARGUMENT** + +``` + +SEQUENCE { + requestedInformationTypeList [0] IMPLICIT SEQUENCE SIZE (1..5) OF + ENUMERATED { + callAttemptElapsedTime (0), + callStopTime (1), + callConnectedElapsedTime (2), + calledAddress (3), + releaseCause (30)}, + correlationID [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [2] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- requestedInfoError -- localValue 10, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 45 + +``` + +``` + +cancel OPERATION + ARGUMENT + CHOICE { + invokeID [0] IMPLICIT INTEGER (-128..127), + allRequests [1] IMPLICIT NULL} + ERRORS { + -- cancelFailed -- localValue 1, + -- missingParameter -- localValue 7, + -- taskRefused -- localValue 12} + ::= localValue 53 + +cancelStatusReportRequest OPERATION + ARGUMENT + SEQUENCE { + resourceID [0] CHOICE { + lineID [0] IMPLICIT OCTET STRING (SIZE (??..??)), + facilityGroupID [1] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING}, + facilityGroupMemberID [2] IMPLICIT INTEGER, + trunkGroupID [3] IMPLICIT INTEGER} OPTIONAL, + extensions [1] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + ERRORS { + -- cancelFailed -- localValue 1, + -- missingParameter -- localValue 7, + -- taskRefused -- localValue 12} + ::= localValue 54 + +collectedInformation OPERATION + ARGUMENT + SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + } + } + } + } + } + } + +``` + +``` + + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, +bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, +iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, +cGEncountered [8] IMPLICIT ENUMERATED { + noCGEncountered (0), + manualCGEncountered (1), + scpOverload (2)} OPTIONAL, +locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, +terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, +dialledDigits [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyBusinessGroupID [2] IMPLICIT OCTET STRING OPTIONAL, +callingPartySubaddress [3] IMPLICIT OCTET STRING OPTIONAL, +callingFacilityGroup [4] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, +callingFacilityGroupMember [5] IMPLICIT INTEGER OPTIONAL, +originalCalledPartyID [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +prefix [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectingPartyID [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectionInformation [9] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, +travellingClassMark [10] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +extensions [11] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + featureCode [12] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + accessCode [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + carrier [14] IMPLICIT OCTET STRING OPTIONAL} +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 2 + +``` + +**collectInformation OPERATION****ARGUMENT****SEQUENCE {** + +alertingPattern [0] IMPLICIT OCTET STRING (SIZE (3)) OPTIONAL, + numberingPlan [1] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + originalCalledPartyID [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + travellingClassMark [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [4] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + callingPartyNumber [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + dialledDigits [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL} + +**ERRORS {** + +-- missingParameter -- localValue 7, + -- parameterOutOfRange -- localValue 8, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 27 + +**connect OPERATION****ARGUMENT****SEQUENCE {** + +destinationRoutingAddress [0] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)), + alertingPattern [1] IMPLICIT OCTET STRING (SIZE (3)) OPTIONAL, + correlationID [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + cutAndPaste [3] IMPLICIT INTEGER (0..22) OPTIONAL, + forwardingCondition [4] IMPLICIT ENUMERATED { + busy (0), + noanswer (1), + any (2)} OPTIONAL, + iSDNAccessRelatedInformation [5] IMPLICIT OCTET STRING OPTIONAL, + originalCalledPartyID [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + routeList [7] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, + scfID [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + travellingClassMark [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [10] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [11] IMPLICIT OCTET STRING OPTIONAL, + serviceInteractionIndicators [26] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [27] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartysCategory [28] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + redirectingPartyID [29] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectionInformation [30] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL} + +**ERRORS {** + +-- missingParameter -- localValue 7, + -- parameterOutOfRange -- localValue 8, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 20 + +``` + +connectToResource OPERATION +ARGUMENT + SEQUENCE { + resourceAddress CHOICE { + ipRoutingAddress [0] IMPLICIT OCTET STRING (SIZE (??..??)), + legID [1] CHOICE { + sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), + receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))}, + both [2] IMPLICIT SEQUENCE { + ipRoutingAddress [0] IMPLICIT OCTET STRING (SIZE (??..??)), + legID [1] CHOICE { + sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), + receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))}, + none [3] IMPLICIT NULL}, + extensions [4] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + serviceInteractionIndicators [30] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL} +ERRORS { + -- missingParameter -- localValue 7, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 19 + +continue OPERATION + ::= localValue 31 + +disconnectForwardConnection OPERATION +ERRORS { + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14} + ::= localValue 18 + +establishTemporaryConnection OPERATION +ARGUMENT + SEQUENCE { + assistingSSPIPRoutingAddress [0] IMPLICIT OCTET STRING (SIZE (??..??)), + correlationID [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + legID [2] CHOICE { + sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), + receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + scfID [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [4] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [5] IMPLICIT OCTET STRING OPTIONAL, + serviceInteractionIndicators [30] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL} +ERRORS { + -- eTCFailed -- localValue 3, + -- missingParameter -- localValue 7, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 17 + +``` + +**eventNotificationCharging OPERATION** +**ARGUMENT** +**SEQUENCE {** + +eventTypeCharging [0] IMPLICIT OCTET STRING (SIZE (??..??)), + eventSpecificInformationCharging [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + legID [2] CHOICE { +   sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), +   receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + extensions [3] IMPLICIT SEQUENCE SIZE (1..??) OF +   SEQUENCE { +     type INTEGER, +     criticality ENUMERATED { +       ignore (0), +       abort (1)} DEFAULT ignore , +     value [1] ANY DEFINED BY type } OPTIONAL, + monitorMode [30] IMPLICIT ENUMERATED { +   interrupted (0), +   notifyAndContinue (1), +   transparent (2)} DEFAULT notifyAndContinue } + ::= localValue 26 + +**eventReportBCSM OPERATION** +**ARGUMENT** +**SEQUENCE {** + +eventTypeBCSM [0] IMPLICIT ENUMERATED { +   origAttemptAuthorized (1), +   collectedInfo (2), +   analysedInformation (3), +   routeSelectFailure (4), +   oCalledPartyBusy (5), +   oNoAnswer (6), +   oAnswer (7), +   oMidCall (8), +   oDisconnect (9), +   oAbandon (10), +   termAttemptAuthorized (12), +   tBusy (13), +   tNoAnswer (14), +   tAnswer (15), +   tMidCall (16), +   tDisconnect (17), +   tAbandon (18)}, + bcsmEventCorrelationID [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + eventSpecificInformationBCSM [2] CHOICE { +   collectedInfoSpecificInfo [0] IMPLICIT SEQUENCE { +     calledPartynumber [0] IMPLICIT OCTET STRING (SIZE (??..??))}, +   analyzedInfoSpecificInfo [1] IMPLICIT SEQUENCE { +     calledPartynumber [0] IMPLICIT OCTET STRING (SIZE (??..??))}, +   routeSelectFailureSpecificInfo [2] IMPLICIT SEQUENCE { +     failureCause [0] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL}, +   oCalledPartyBusySpecificInfo [3] IMPLICIT SEQUENCE { +     busyCause [0] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL}, +   oNoAnswerSpecificInfo [4] IMPLICIT SEQUENCE {}, +   oAnswerSpecificInfo [5] IMPLICIT SEQUENCE {}, +   oMidCallSpecificInfo [6] IMPLICIT SEQUENCE { +     connectTime [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL}, +   oDisconnectSpecificInfo [7] IMPLICIT SEQUENCE { +     releaseCause [0] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL, +     connectTime [1] IMPLICIT INTEGER (0..2147483647) OPTIONAL}, +   tBusySpecificInfo [8] IMPLICIT SEQUENCE { +     busyCause [0] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL}, +   tNoAnswerSpecificInfo [9] IMPLICIT SEQUENCE {}, +   tAnswerSpecificInfo [10] IMPLICIT SEQUENCE {}, +   tMidCallSpecificInfo [11] IMPLICIT SEQUENCE { +     connectTime [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL}, +   tDisconnectSpecificInfo [12] IMPLICIT SEQUENCE { +     releaseCause [0] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL, +     connectTime [1] IMPLICIT INTEGER (0..2147483647) OPTIONAL}} } + } + +``` + +legID [3] CHOICE { + sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), + receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +miscCallInfo [4] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL} DEFAULT { + messageType request }, +extensions [5] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} +::= localValue 24 + +``` + +**furnishChargingInformation OPERATION** + +**ARGUMENT** + +OCTET STRING (SIZE (??..??)) + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 34 + +``` + +**holdCallInNetwork OPERATION** + +**ARGUMENT** + +**CHOICE {** + +``` + + holdcause [0] IMPLICIT OCTET STRING, + empty [1] IMPLICIT NULL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 21 + +``` + +**initialDP OPERATION** + +**ARGUMENT** + +**SEQUENCE {** + +``` + + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + dialledDigits [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyBusinessGroupID [4] IMPLICIT OCTET STRING OPTIONAL, + callingPartysCategory [5] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + callingPartySubaddress [6] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [7] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, + iPSSPCapabilities [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + locationNumber [10] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + miscCallInfo [11] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + +``` + +``` + +dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL} OPTIONAL, +originalCalledPartyID [12] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +serviceProfileIdentifier [13] IMPLICIT OCTET STRING OPTIONAL, +terminalType [14] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [15] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, +triggerType [16] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL, +highLayerCompatibility [23] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, +serviceInteractionIndicators [24] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +additionalCallingPartyNumber [25] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +forwardCallIndicators [26] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, +bearerCapability [27] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +eventTypeBCSM [28] IMPLICIT ENUMERATED { + origAttemptAuthorized (1), + collectedInfo (2), + analysedInformation (3), + routeSelectFailure (4), + oCalledPartyBusy (5), + oNoAnswer (6), + oAnswer (7), + oMidCall (8), + oDisconnect (9), + oAbandon (10), + termAttemptAuthorized (12), + tBusy (13), + tNoAnswer (14), + tAnswer (15), + tMidCall (16), + tDisconnect (17), + tAbandon (18)} OPTIONAL, +redirectingPartyID [29] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectionInformation [30] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 0 + +``` + +**initiateCallAttempt OPERATION** + +**ARGUMENT** + +**SEQUENCE {** + +``` + + destinationRoutingAddress [0] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)), + alertingPattern [1] IMPLICIT OCTET STRING (SIZE (3)) OPTIONAL, + iSDNAccessRelatedInformation [2] IMPLICIT OCTET STRING OPTIONAL, + travellingClassMark [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [4] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + serviceInteractionIndicators [29] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [30] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 32 + +``` + +**oAnswer OPERATION** + +**ARGUMENT** + +**SEQUENCE {** + +``` + + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + +``` + +``` + + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, +bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, +iSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, +cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, +locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, +terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, +callingPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, +callingPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, +callingFacilityGroup [3] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, +callingFacilityGroupMember [4] IMPLICIT INTEGER OPTIONAL, +originalCalledPartyID [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectingPartyID [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectionInformation [7] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, +routeList [8] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, +travellingClassMark [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +extensions [10] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 7 + +``` + +``` + +oCalledPartyBusy OPERATION +ARGUMENT +SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, + bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, + extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + }, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + busyCause [1] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL, + callingPartyBusinessGroupID [2] IMPLICIT OCTET STRING OPTIONAL, + callingPartySubaddress [3] IMPLICIT OCTET STRING OPTIONAL, + callingFacilityGroup [4] CHOICE { + +``` + +``` + +trunkGroupID [0] IMPLICIT INTEGER, +privateFacilityID [1] IMPLICIT INTEGER, +huntGroup [2] IMPLICIT OCTET STRING, +routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, +callingFacilityGroupMember [5] IMPLICIT INTEGER OPTIONAL, +originalCalledPartyID [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +prefix [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectingPartyID [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +redirectionInformation [9] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, +routeList [10] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, +travellingClassMark [11] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [13] IMPLICIT OCTET STRING OPTIONAL} +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 5 + +``` + +**oDisconnect OPERATION** + +**ARGUMENT** + +``` + +SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, + +``` + +``` + +bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, +iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, +cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, +locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, +terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, +callingPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, +callingPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, +callingFacilityGroup [3] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, +callingFacilityGroupMember [4] IMPLICIT INTEGER OPTIONAL, +releaseCause [5] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL, +routeList [6] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, +extensions [7] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [8] IMPLICIT OCTET STRING OPTIONAL, + connectTime [9] IMPLICIT INTEGER (0..2147483647) OPTIONAL} +ERRORS { + -- missingCustomerRecord -- localValue 6, + -- missingParameter -- localValue 7, + -- parameterOutOfRange -- localValue 8, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 8 + +oMidCall OPERATION + ARGUMENT + SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + +``` + +``` + +serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, +miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, + bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, + extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + calledPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, + calledPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, + callingPartyBusinessGroupID [3] IMPLICIT OCTET STRING OPTIONAL, + callingPartySubaddress [4] IMPLICIT OCTET STRING OPTIONAL, + featureRequestIndicator [5] IMPLICIT ENUMERATED { + hold (0), + retrieve (1), + featureActivation (2), + spare1 (3), + } +} + +``` + +``` + + sparen (127); OPTIONAL, + extensions [6] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [7] IMPLICIT OCTET STRING OPTIONAL} +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 14 + +oNoAnswer OPERATION +ARGUMENT +SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, + bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, + +``` + +locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + terminalType [11] IMPLICIT ENUMERATED { +     unknown (0), +     dialPulse (1), +     dtmf (2), +     isdn (3), +     isdnNoDtmf (4), +     spare (16)} OPTIONAL, + extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF +     SEQUENCE { +         type INTEGER, +         criticality ENUMERATED { +             ignore (0), +             abort (1)} DEFAULT ignore , +         value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + callingPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, + callingPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, + callingFacilityGroup [3] CHOICE { +     trunkGroupID [0] IMPLICIT INTEGER, +     privateFacilityID [1] IMPLICIT INTEGER, +     huntGroup [2] IMPLICIT OCTET STRING, +     routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, + callingFacilityGroupMember [4] IMPLICIT INTEGER OPTIONAL, + originalCalledPartyID [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + prefix [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectingPartyID [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectionInformation [8] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, + routeList [9] IMPLICIT SEQUENCE SIZE (1..3) OF +     OCTET STRING (SIZE (??..??)) OPTIONAL, + travellingClassMark [10] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [11] IMPLICIT SEQUENCE SIZE (1..??) OF +     SEQUENCE { +         type INTEGER, +         criticality ENUMERATED { +             ignore (0), +             abort (1)} DEFAULT ignore , +         value [1] ANY DEFINED BY type } OPTIONAL, + carrier [12] IMPLICIT OCTET STRING OPTIONAL} + +ERRORS { + -- missingCustomerRecord -- localValue 6, + -- missingParameter -- localValue 7, + -- parameterOutOfRange -- localValue 8, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 6 + +**originationAttemptAuthorized OPERATION** + ARGUMENT +     SEQUENCE { +         dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { +             serviceAddressInformation [0] IMPLICIT SEQUENCE { +                 serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, +                 miscCallInfo [1] IMPLICIT SEQUENCE { +                     messageType [0] IMPLICIT ENUMERATED { +                         request (0), +                         notification (1)}, +                     dpAssignment [1] IMPLICIT ENUMERATED { +                         individualLine (0), +                         groupBased (1), +                         officeBased (2)} OPTIONAL}, + +Recommendation Q.1218 (10/95) 401 + +``` + +triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL, +bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, +iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, +cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, +locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, +terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + dialledDigits [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyBusinessGroupID [2] IMPLICIT OCTET STRING OPTIONAL, + callingPartySubaddress [3] IMPLICIT OCTET STRING OPTIONAL, + callingFacilityGroup [4] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, + callingFacilityGroupMember [5] IMPLICIT INTEGER OPTIONAL, + travellingClassMark [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [7] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [8] IMPLICIT OCTET STRING OPTIONAL} + +``` + +``` + +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 1 + +playAnnouncement OPERATION +ARGUMENT + SEQUENCE { + informationToSend [0] CHOICE { + inbandInfo [0] IMPLICIT SEQUENCE { + messageID [0] CHOICE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + text [1] IMPLICIT SEQUENCE { + messageContent [0] IMPLICIT IA5String (SIZE (??..??)), + attributes [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + elementaryMessageIDs [29] IMPLICIT SEQUENCE SIZE (1..??) OF + INTEGER (0..2147483647), + variableMessage [30] IMPLICIT SEQUENCE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + variableParts [1] IMPLICIT SEQUENCE SIZE (1..5) OF + CHOICE { + integer [0] IMPLICIT INTEGER (0..2147483647), + number [1] IMPLICIT OCTET STRING (SIZE (??..??)), + time [2] IMPLICIT OCTET STRING (SIZE (2)), + date [3] IMPLICIT OCTET STRING (SIZE (3)), + price [4] IMPLICIT OCTET STRING (SIZE (4))}}}, + numberOfRepetitions [1] IMPLICIT INTEGER (1..127) OPTIONAL, + duration [2] IMPLICIT INTEGER (0..32767) OPTIONAL, + interval [3] IMPLICIT INTEGER (0..32767) OPTIONAL}, + tone [1] IMPLICIT SEQUENCE { + toneID [0] IMPLICIT INTEGER (0..2147483647), + duration [1] IMPLICIT INTEGER (0..2147483647) OPTIONAL}, + displayInformation [2] IMPLICIT IA5String (SIZE (??..??))}, + disconnectFromIPForbidden [1] IMPLICIT BOOLEAN DEFAULT TRUE, + requestAnnouncementComplete [2] IMPLICIT BOOLEAN DEFAULT TRUE, + extensions [3] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + } +ERRORS { +-- canceled -- localValue 0, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16, +-- unavailableResource -- localValue 13} +LINKED { +-- specializedResourceReport -- localValue 49} +::= localValue 47 + +promptAndCollectUserInformation OPERATION +ARGUMENT + SEQUENCE { + collectedInfo [0] CHOICE { + +``` + +``` + +collectedDigits [0] IMPLICIT SEQUENCE { + minimumNbOfDigits [0] IMPLICIT INTEGER (1..127) DEFAULT 1, + maximumNbOfDigits [1] IMPLICIT INTEGER (1..127), + endOfReplyDigit [2] IMPLICIT OCTET STRING (SIZE (1..2)) OPTIONAL, + cancelDigit [3] IMPLICIT OCTET STRING (SIZE (1..2)) OPTIONAL, + startDigit [4] IMPLICIT OCTET STRING (SIZE (1..2)) OPTIONAL, + firstDigitTimeOut [5] IMPLICIT INTEGER (1..127) OPTIONAL, + interDigitTimeOut [6] IMPLICIT INTEGER (1..127) OPTIONAL, + errorTreatment [7] IMPLICIT ENUMERATED { + reportErrorToScf (0), + help (1), + repeatPrompt (2)} DEFAULT reportErrorToScf , + interruptableAnnInd [8] IMPLICIT BOOLEAN DEFAULT TRUE, + voiceInformation [9] IMPLICIT BOOLEAN DEFAULT FALSE, + voiceBack [10] IMPLICIT BOOLEAN DEFAULT FALSE}, + ia5Information [1] IMPLICIT BOOLEAN}, + disconnectFromIPForbidden [1] IMPLICIT BOOLEAN DEFAULT TRUE, + informationToSend [2] CHOICE { + inbandInfo [0] IMPLICIT SEQUENCE { + messageID [0] CHOICE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + text [1] IMPLICIT SEQUENCE { + messageContent [0] IMPLICIT IA5String (SIZE (??..??)), + attributes [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + elementaryMessageIDs [29] IMPLICIT SEQUENCE SIZE (1..??) OF + INTEGER (0..2147483647), + variableMessage [30] IMPLICIT SEQUENCE { + elementaryMessageID [0] IMPLICIT INTEGER (0..2147483647), + variableParts [1] IMPLICIT SEQUENCE SIZE (1..5) OF + CHOICE { + integer [0] IMPLICIT INTEGER (0..2147483647), + number [1] IMPLICIT OCTET STRING (SIZE (??..??)), + time [2] IMPLICIT OCTET STRING (SIZE (2)), + date [3] IMPLICIT OCTET STRING (SIZE (3)), + price [4] IMPLICIT OCTET STRING (SIZE (4))}}}, + numberOfRepetitions [1] IMPLICIT INTEGER (1..127) OPTIONAL, + duration [2] IMPLICIT INTEGER (0..32767) OPTIONAL, + interval [3] IMPLICIT INTEGER (0..32767) OPTIONAL}, + tone [1] IMPLICIT SEQUENCE { + toneID [0] IMPLICIT INTEGER (0..2147483647), + duration [1] IMPLICIT INTEGER (0..2147483647) OPTIONAL}, + displayInformation [2] IMPLICIT IA5String (SIZE (??..??)) OPTIONAL, + extensions [3] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +#### RESULT + +``` + +CHOICE { + digitsResponse [0] IMPLICIT OCTET STRING (SIZE (??..??)), + ia5Response [1] IMPLICIT IA5String } + +``` + +#### ERRORS { + +``` + +-- canceled -- localValue 0, +-- improperCallerResponse -- localValue 4, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unavailableResource -- localValue 13, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 48 + +``` + +``` + +releaseCall OPERATION + ARGUMENT + OCTET STRING (SIZE (2..??)) + ::= localValue 22 + +requestCurrentStatusReport OPERATION + ARGUMENT + CHOICE { + lineID [0] IMPLICIT OCTET STRING (SIZE (??..??)), + facilityGroupID [1] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING}, + facilityGroupMemberID [2] IMPLICIT INTEGER, + trunkGroupID [3] IMPLICIT INTEGER} + RESULT + SEQUENCE { + resourceStatus [0] IMPLICIT ENUMERATED { + busy (0), + idle (1)}, + resourceID [1] CHOICE { + lineID [0] IMPLICIT OCTET STRING (SIZE (??..??)), + facilityGroupID [1] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING}, + facilityGroupMemberID [2] IMPLICIT INTEGER, + trunkGroupID [3] IMPLICIT INTEGER} OPTIONAL, + extensions [2] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + ERRORS { + -- missingParameter -- localValue 7, + -- parameterOutOfRange -- localValue 8, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedParameter -- localValue 16, + -- unknownResource -- localValue 18} + ::= localValue 37 + +requestEveryStatusChangeReport OPERATION + ARGUMENT + SEQUENCE { + resourceID [0] CHOICE { + lineID [0] IMPLICIT OCTET STRING (SIZE (??..??)), + facilityGroupID [1] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING}, + facilityGroupMemberID [2] IMPLICIT INTEGER, + trunkGroupID [3] IMPLICIT INTEGER}, + correlationID [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + monitorDuration [2] IMPLICIT INTEGER (-2..86400) OPTIONAL, + extensions [3] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedParameter -- localValue 16, +-- unknownResource -- localValue 18} +::= localValue 38 + +``` + +**requestFirstStatusMatchReport OPERATION****ARGUMENT****SEQUENCE {** + +``` + +resourceID [0] CHOICE { + lineID [0] IMPLICIT OCTET STRING (SIZE (??..??)), + facilityGroupID [1] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING}, + facilityGroupMemberID [2] IMPLICIT INTEGER, + trunkGroupID [3] IMPLICIT INTEGER} OPTIONAL, +resourceStatus [1] IMPLICIT ENUMERATED { + busy (0), + idle (1)} OPTIONAL, +correlationID [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +monitorDuration [3] IMPLICIT INTEGER (-2..86400) OPTIONAL, +extensions [4] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, +bearerCapability [5] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedParameter -- localValue 16, +-- unknownResource -- localValue 18} +::= localValue 39 + +``` + +**requestNotificationChargingEvent OPERATION****ARGUMENT****SEQUENCE SIZE (1..??) OF** + +``` + +SEQUENCE { + eventTypeCharging [0] IMPLICIT OCTET STRING (SIZE (??..??)), + monitorMode [1] IMPLICIT ENUMERATED { + interrupted (0), + notifyAndContinue (1), + transparent (2)}, + legID [2] CHOICE { + sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), + receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, + +``` + +``` + +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 25 + +requestReportBCSMEvent OPERATION +ARGUMENT + SEQUENCE { + bcsmEvents [0] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + eventTypeBCSM [0] IMPLICIT ENUMERATED { + origAttemptAuthorized (1), + collectedInfo (2), + analysedInformation (3), + routeSelectFailure (4), + oCalledPartyBusy (5), + oNoAnswer (6), + oAnswer (7), + oMidCall (8), + oDisconnect (9), + oAbandon (10), + termAttemptAuthorized (12), + tBusy (13), + tNoAnswer (14), + tAnswer (15), + tMidCall (16), + tDisconnect (17), + tAbandon (18)}, + monitorMode [1] IMPLICIT ENUMERATED { + interrupted (0), + notifyAndContinue (1), + transparent (2)}, + legID [2] CHOICE { + sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), + receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + dpSpecificCriteria [30] CHOICE { + numberOfDigits [0] IMPLICIT INTEGER (1..255), + applicationTimer [1] IMPLICIT INTEGER (0..2047)} OPTIONAL}, + bcsmEventCorrelationID [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [2] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} +ERRORS { +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 23 + +resetTimer OPERATION +ARGUMENT + SEQUENCE { + timerID [0] IMPLICIT ENUMERATED { + tssf (0)} DEFAULT tssf , + timervalue [1] IMPLICIT INTEGER (0..2147483647), + extensions [2] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 33 + +``` + +**routeSelectFailure OPERATION****ARGUMENT****SEQUENCE {** + +``` + +dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + +``` + +``` + + serviceAddressInformation [0] IMPLICIT SEQUENCE { + +``` + +``` + + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + +``` + +``` + + miscCallInfo [1] IMPLICIT SEQUENCE { + +``` + +``` + + messageType [0] IMPLICIT ENUMERATED { + +``` + +``` + + request (0), + +``` + +``` + + notification (1)}, + +``` + +``` + + dpAssignment [1] IMPLICIT ENUMERATED { + +``` + +``` + + individualLine (0), + +``` + +``` + + groupBased (1), + +``` + +``` + + officeBased (2)} OPTIONAL}, + +``` + +``` + + triggerType [2] IMPLICIT ENUMERATED { + +``` + +``` + + featureActivation (0), + +``` + +``` + + verticalServiceCode (1), + +``` + +``` + + customizedAccess (2), + +``` + +``` + + customizedIntercom (3), + +``` + +``` + + emergencyService (12), + +``` + +``` + + aFR (13), + +``` + +``` + + sharedIOTrunk (14), + +``` + +``` + + offHookDelay (17), + +``` + +``` + + channelSetupPRI (18), + +``` + +``` + + tNoAnswer (25), + +``` + +``` + + tBusy (26), + +``` + +``` + + oCalledPartyBusy (27), + +``` + +``` + + oNoAnswer (29), + +``` + +``` + + originationAttemptAuthorized (30), + +``` + +``` + + oAnswer (31), + +``` + +``` + + oDisconnect (32), + +``` + +``` + + termAttemptAuthorized (33), + +``` + +``` + + tAnswer (34), + +``` + +``` + + tDisconnect (35)} OPTIONAL}, + +``` + +``` + + bearerCapability [1] CHOICE { + +``` + +``` + + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + +``` + +``` + + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + +``` + +``` + + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + +``` + +``` + + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + +``` + +``` + + callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + +``` + +``` + + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + +``` + +``` + + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + +``` + +``` + + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + +``` + +``` + + cGEncountered [8] IMPLICIT ENUMERATED { + +``` + +``` + + noCGencountered (0), + +``` + +``` + + manualCGencountered (1), + +``` + +``` + + scpOverload (2)} OPTIONAL, + +``` + +``` + + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + +``` + +``` + + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + +``` + +``` + + terminalType [11] IMPLICIT ENUMERATED { + +``` + +``` + + unknown (0), + +``` + +``` + + dialPulse (1), + +``` + +``` + + dtmf (2), + +``` + +``` + + isdn (3), + +``` + +``` + + isdnNoDtmf (4), + +``` + +``` + + spare (16)} OPTIONAL, + +``` + +``` + + extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + +``` + +``` + + SEQUENCE { + +``` + +``` + + type INTEGER, + +``` + +``` + + criticality ENUMERATED { + +``` + +``` + + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + dialledDigits [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyBusinessGroupID [2] IMPLICIT OCTET STRING OPTIONAL, + callingPartySubaddress [3] IMPLICIT OCTET STRING OPTIONAL, + callingFacilityGroup [4] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, + callingFacilityGroupMember [5] IMPLICIT INTEGER OPTIONAL, + failureCause [6] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL, + originalCalledPartyID [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + prefix [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectingPartyID [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectionInformation [10] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, + routeList [11] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, + travellingClassMark [12] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [13] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [14] IMPLICIT OCTET STRING OPTIONAL} +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 4 + +selectFacility OPERATION +ARGUMENT +SEQUENCE { + alertingPattern [0] IMPLICIT OCTET STRING (SIZE (3)) OPTIONAL, + destinationNumberRoutingAddress [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [2] IMPLICIT OCTET STRING OPTIONAL, + calledFacilityGroup [3] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, + calledFacilityGroupMember [4] IMPLICIT INTEGER OPTIONAL, + originalCalledPartyID [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [6] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} +ERRORS { +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, + +``` + +``` + +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 30 + +selectRoute OPERATION +ARGUMENT + SEQUENCE { + destinationRoutingAddress [0] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)), + alertingPattern [1] IMPLICIT OCTET STRING (SIZE (3)) OPTIONAL, + correlationID [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [3] IMPLICIT OCTET STRING OPTIONAL, + originalCalledPartyID [4] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + routeList [5] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, + scfID [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + travellingClassMark [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [8] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + carrier [9] IMPLICIT OCTET STRING OPTIONAL} +ERRORS { +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 29 + +sendChargingInformation OPERATION +ARGUMENT + SEQUENCE { + sCIBillingChargingCharacteristics [0] IMPLICIT OCTET STRING (SIZE (??..??)), + partyToCharge [1] CHOICE { + sendingSideID [0] IMPLICIT OCTET STRING (SIZE (1)), + receivingSideID [1] IMPLICIT OCTET STRING (SIZE (1))}, + extensions [2] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} +ERRORS { +-- missingParameter -- localValue 7, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedParameter -- localValue 16, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unknownLegID -- localValue 17} +::= localValue 46 + +serviceFilteringResponse OPERATION +ARGUMENT + SEQUENCE { + countersValue [0] IMPLICIT SEQUENCE SIZE (0..100) OF + SEQUENCE { + counterID [0] IMPLICIT INTEGER (0..99), + counterValue [1] IMPLICIT INTEGER (0..2147483647)}, + +``` + +``` + +filteringCriteria [1] CHOICE { + dialledNumber [0] IMPLICIT OCTET STRING (SIZE (??..??)), + callingLineID [1] IMPLICIT OCTET STRING (SIZE (??..??)), + serviceKey [2] IMPLICIT INTEGER (0..2147483647), + addressAndService [30] IMPLICIT SEQUENCE { + calledAddressValue [0] IMPLICIT OCTET STRING (SIZE (??..??)), + serviceKey [1] IMPLICIT INTEGER (0..2147483647), + callingAddressValue [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + locationNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}}, + extensions [2] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + responseCondition [3] IMPLICIT ENUMERATED { + intermediateResponse (0), + lastResponse (1)} OPTIONAL} + ::= localValue 43 + +specializedResourceReport OPERATION + ARGUMENT + NULL + ::= localValue 49 + +statusReport OPERATION + ARGUMENT + SEQUENCE { + resourceStatus [0] IMPLICIT ENUMERATED { + busy (0), + idle (1)} OPTIONAL, + correlationID [1] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + resourceID [2] CHOICE { + lineID [0] IMPLICIT OCTET STRING (SIZE (??..??)), + facilityGroupID [1] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING}, + facilityGroupMemberID [2] IMPLICIT INTEGER, + trunkGroupID [3] IMPLICIT INTEGER} OPTIONAL, + extensions [3] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + reportCondition [4] IMPLICIT ENUMERATED { + statusReport (0), + timerExpired (1), + canceled (2)} OPTIONAL} + ::= localValue 40 + +tAnswer OPERATION + ARGUMENT + SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + } + } + } + } + +``` + +``` + +triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL, +bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, +calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, +iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, +cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, +locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, +terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, +calledPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, +calledPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, +calledFacilityGroup [3] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, +calledFacilityGroupMember [4] IMPLICIT INTEGER OPTIONAL, +extensions [5] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +**ERRORS {** + +``` + +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 12 + +``` + +**tBusy OPERATION** +**ARGUMENT** +**SEQUENCE {** + +``` + +dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, + bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, + +``` + +``` + +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + busyCause [1] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL, + calledPartyBusinessGroupID [2] IMPLICIT OCTET STRING OPTIONAL, + calledPartySubaddress [3] IMPLICIT OCTET STRING OPTIONAL, + originalCalledPartyID [4] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectingPartyID [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectionInformation [6] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, + routeList [7] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, + travellingClassMark [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [9] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +``` + +#### ERRORS { + +``` + +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 10 + +``` + +#### tDisconnect OPERATION + +##### ARGUMENT + +``` + +SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOT trunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + +``` + +``` + + tAnswer (34), + tDisconnect (35)} OPTIONAL}, +bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartysCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGEncountered (0), + manualCGEncountered (1), + scpOverload (2)} OPTIONAL, + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, + extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, +calledPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, +calledPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, +calledFacilityGroup [3] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, +calledFacilityGroupMember [4] IMPLICIT INTEGER OPTIONAL, +releaseCause [5] IMPLICIT OCTET STRING (SIZE (2..??)) OPTIONAL, +extensions [6] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, +connectTime [7] IMPLICIT INTEGER (0..2147483647) OPTIONAL} +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 13 + +termAttemptAuthorized OPERATION + ARGUMENT + SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + +``` + +``` + +miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, + bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1))} OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGEncountered (0), + manualCGEncountered (1), + scpOverload (2)} OPTIONAL, + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, + extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + calledPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, + calledPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, + callingPartyBusinessGroupID [3] IMPLICIT OCTET STRING OPTIONAL, + originalCalledPartyID [4] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectingPartyID [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectionInformation [6] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, + routeList [7] IMPLICIT SEQUENCE SIZE (1..3) OF + OCTET STRING (SIZE (??..??)) OPTIONAL, + travellingClassMark [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [9] IMPLICIT SEQUENCE SIZE (1..??) OF + +``` + +``` + +SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} + +ERRORS { + -- missingCustomerRecord -- localValue 6, + -- missingParameter -- localValue 7, + -- parameterOutOfRange -- localValue 8, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 9 + +tMidCall OPERATION +ARGUMENT + SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTtrunk (14), + offHookDelay (17), + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, + bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1)); OPTIONAL, + }, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAccessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, + }, + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + } + } + } +} + +``` + +``` + +terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, +extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + calledPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, + calledPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, + callingPartyBusinessGroupID [3] IMPLICIT OCTET STRING OPTIONAL, + callingPartySubaddress [4] IMPLICIT OCTET STRING OPTIONAL, + featureRequestIndicator [5] IMPLICIT ENUMERATED { + hold (0), + retrieve (1), + featureActivation (2), + spare1 (3), + sparen (127)} OPTIONAL, + extensions [6] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + }, + carrier [7] IMPLICIT OCTET STRING OPTIONAL} +ERRORS { + -- missingCustomerRecord -- localValue 6, + -- missingParameter -- localValue 7, + -- parameterOutOfRange -- localValue 8, + -- systemFailure -- localValue 11, + -- taskRefused -- localValue 12, + -- unexpectedComponentSequence -- localValue 14, + -- unexpectedDataValue -- localValue 15, + -- unexpectedParameter -- localValue 16} + ::= localValue 15 + +tNoAnswer OPERATION + ARGUMENT + SEQUENCE { + dpSpecificCommonParameters [0] IMPLICIT SEQUENCE { + serviceAddressInformation [0] IMPLICIT SEQUENCE { + serviceKey [0] IMPLICIT INTEGER (0..2147483647) OPTIONAL, + miscCallInfo [1] IMPLICIT SEQUENCE { + messageType [0] IMPLICIT ENUMERATED { + request (0), + notification (1)}, + dpAssignment [1] IMPLICIT ENUMERATED { + individualLine (0), + groupBased (1), + officeBased (2)} OPTIONAL}, + triggerType [2] IMPLICIT ENUMERATED { + featureActivation (0), + verticalServiceCode (1), + customizedAccess (2), + customizedIntercom (3), + emergencyService (12), + aFR (13), + sharedIOTtrunk (14), + offHookDelay (17), + +``` + +``` + + channelSetupPRI (18), + tNoAnswer (25), + tBusy (26), + oCalledPartyBusy (27), + oNoAnswer (29), + originationAttemptAuthorized (30), + oAnswer (31), + oDisconnect (32), + termAttemptAuthorized (33), + tAnswer (34), + tDisconnect (35)} OPTIONAL}, +bearerCapability [1] CHOICE { + bearerCap [0] IMPLICIT OCTET STRING (SIZE (2..??)), + tmr [1] IMPLICIT OCTET STRING (SIZE (1)); OPTIONAL, + calledPartyNumber [2] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyNumber [3] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + callingPartyCategory [4] IMPLICIT OCTET STRING (SIZE (1)) OPTIONAL, + iPSSPCapabilities [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iPAvailable [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + iSDNAcessRelatedInformation [7] IMPLICIT OCTET STRING OPTIONAL, + cGEncountered [8] IMPLICIT ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2)} OPTIONAL, + locationNumber [9] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + serviceProfileIdentifier [10] IMPLICIT OCTET STRING OPTIONAL, + terminalType [11] IMPLICIT ENUMERATED { + unknown (0), + dialPulse (1), + dtmf (2), + isdn (3), + isdnNoDtmf (4), + spare (16)} OPTIONAL, + extensions [12] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL, + chargeNumber [13] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + servingAreaID [14] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL}, + calledPartyBusinessGroupID [1] IMPLICIT OCTET STRING OPTIONAL, + calledPartySubaddress [2] IMPLICIT OCTET STRING OPTIONAL, + calledFacilityGroup [3] CHOICE { + trunkGroupID [0] IMPLICIT INTEGER, + privateFacilityID [1] IMPLICIT INTEGER, + huntGroup [2] IMPLICIT OCTET STRING, + routeIndex [3] IMPLICIT OCTET STRING} OPTIONAL, + calledFacilityGroupMember [4] IMPLICIT INTEGER OPTIONAL, + originalCalledPartyID [5] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectingPartyID [6] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + redirectionInformation [7] IMPLICIT OCTET STRING (SIZE (2)) OPTIONAL, + travellingClassMark [8] IMPLICIT OCTET STRING (SIZE (??..??)) OPTIONAL, + extensions [9] IMPLICIT SEQUENCE SIZE (1..??) OF + SEQUENCE { + type INTEGER, + criticality ENUMERATED { + ignore (0), + abort (1)} DEFAULT ignore , + value [1] ANY DEFINED BY type } OPTIONAL} +ERRORS { +-- missingCustomerRecord -- localValue 6, +-- missingParameter -- localValue 7, +-- parameterOutOfRange -- localValue 8, +-- systemFailure -- localValue 11, +-- taskRefused -- localValue 12, +-- unexpectedComponentSequence -- localValue 14, + +``` + +``` + +-- unexpectedDataValue -- localValue 15, +-- unexpectedParameter -- localValue 16} +::= localValue 11 + +canceled ERROR +::= localValue 0 + +cancelFailed ERROR +PARAMETER +SEQUENCE { + problem [0] IMPLICIT ENUMERATED { + unknownOperation (0), + tooLate (1), + operationNotCancellable (2)}, + operation [1] IMPLICIT INTEGER (-128..127)} +::= localValue 1 + +eTCFailed ERROR +::= localValue 3 + +improperCallerResponse ERROR +::= localValue 4 + +missingCustomerRecord ERROR +::= localValue 6 + +missingParameter ERROR +::= localValue 7 + +parameterOutOfRange ERROR +::= localValue 8 + +requestedInfoError ERROR +PARAMETER +ENUMERATED { + unknownRequestedInfo (1), + requestedInfoNotAvailable (2)} +::= localValue 10 + +systemFailure ERROR +PARAMETER +unavailableNetworkResource ENUMERATED { + unavailableResources (0), + componentFailure (1), + basicCallProcessingException (2), + resourceStatusFailure (3), + endUserFailure (4)} +::= localValue 11 + +taskRefused ERROR +PARAMETER +ENUMERATED { + generic (0), + unobtainable (1), + congestion (2)} +::= localValue 12 + +unavailableResource ERROR +::= localValue 13 + +unexpectedComponentSequence ERROR +::= localValue 14 + +unexpectedDataValue ERROR +::= localValue 15 + +unexpectedParameter ERROR +::= localValue 16 + +unknownLegID ERROR +::= localValue 17 + +unknownResource ERROR +::= localValue 18 + +``` \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1220-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1220-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36a32fb27730598abaef54b051cf1fffedc17599 --- /dev/null +++ b/marked/Q/T-REC-Q.1220-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.1220-199709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1220-199709-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..48c3123ef0d914335969c9ac19156a4e68c32cbe --- /dev/null +++ b/marked/Q/T-REC-Q.1220-199709-I_PDF-E/raw.md @@ -0,0 +1,1047 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1220** + +(09/97) + +SERIES Q: SWITCHING AND SIGNALLING + +Intelligent Network + +--- + +**Q.1220-series Intelligent Network +Capability Set 2 Recommendation structure** + +ITU-T Recommendation Q.1220 + +(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.1220** + +## **Q.1220-SERIES INTELLIGENT NETWORK CAPABILITY SET 2 RECOMMENDATION STRUCTURE** + +## **Summary** + +This Recommendation explains the structure of the Q.122x (CS-2)-series IN Recommendations and provides their outlines. + +### **Source** + +ITU-T Recommendation Q.1220 was prepared 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 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 | +|--------------------------------------------------------------------|-------------| +| 0 Introduction ..... | 1 | +| 1 General Q.1200-series structure ..... | 1 | +| 2 Q.122x-series Intelligent Network Recommendations overview ..... | 1 | + + + +## Q.1220-SERIES INTELLIGENT NETWORK CAPABILITY SET 2 RECOMMENDATION STRUCTURE + +*(Geneva, 1997)* + +# 0 Introduction + +A block of one hundred numbers has been set aside in the Q series (Q.1200-Q.1299) for the development of Intelligent Network (IN) Recommendations. This Recommendation has been developed to organize the IN CS-2 Recommendations in a meaningful way in order to assist users in locating topics of interest. It provides a structural overview of the content of the Q.1220 series. + +Terms and definitions pertinent to IN CS-2 are included in Recommendation Q.1290. + +## 1 General Q.1200-series structure + +Table 1 shows the overall Q.1200-series Intelligent Network Recommendation naming structure. + +**Table 1/Q.1220 – Recommendation framework structure** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| 1200 – General | | +| 1210 – CS-1 | 121 – Principles introduction | +| 1220 – CS-2 | 122 – Service plane (not included for CS-1) | +| 1230 – CS-3 | 123 – Global functional plane | +| 1240 – CS-4 | 124 – Distributed functional plane | +| 1250 – CS-5 | 125 – Physical plane | +| 1260 – CS-6 | 126 – For future use | +| 1270 – CS-7 | 127 – For future use | +| 1280 – CS-8 | 128 – Interface Recommendation | +| 1290 – Glossary | 129 – Intelligent network user's guide | +| NOTE 1 – 1200 is assigned for the IN Recommendation framework structure.
NOTE 2 – 1290-series has been set aside for the glossary. | | + +## 2 Q.122x-series Intelligent Network Recommendations overview + +### **Q.1220-Q.1220-series Intelligent Network Capability Set 2 Recommendation structure** + +- 0 Introduction +- 1 General Q.1200-series structure +- 2 Q.122x-series Intelligent Network Recommendations overview + +### **Q.1221 – Introduction to Intelligent Network Capability Set 2** + +- 1 Introduction +- 2 Phased standardization +- 3 General description and scope of IN CS-2 + - 3.1 Criteria for IN CS-2 + - 3.2 Evolution of IN CS-2 +- 4 Overview of IN CS-2 Recommendations +- 5 Service aspects + - 5.1 Telecommunication services + - 5.2 Service management services + - 5.3 Service creation services + - 5.4 Network support of IN CS-2 services +- 6 Network aspects + - 6.1 Network functions + - 6.2 Control architecture principles + - 6.2.1 Service invocation and control + - 6.2.2 End-user interactions + - 6.2.3 Service management + - 6.3 Feature interactions + - 6.4 Consistency among IN CS-2 supported service features +- 7 Functional relationships and interfaces + - 7.1 Functional relationships and control classes + - 7.1.1 Bearer connection control + - 7.1.2 Non-IN call control + - 7.1.3 IN service control + - 7.1.4 Service management control + - 7.1.5 Non-IN call unrelated control + - 7.2 Key functions and interfaces + - 7.2.1 Single point/multiple points of control + - 7.2.2 Single-ended/multi-ended calls + - 7.2.3 Mid-call interruption + - 7.2.4 Call party handling + - 7.2.5 Enhanced SRF + - 7.2.6 Call unrelated user interaction + - 7.2.7 Out-channel call related user interaction + - 7.2.8 Service/feature interaction (service processing) + - 7.2.9 Internetworking + - 7.2.10 Security + - 7.2.11 IN-TMN + - 7.2.12 Service management + - 7.2.13 Service creation + - 7.2.14 Personal mobility + +## **Appendix I – IN CS-2 benchmark services and features** + +- I.1 General +- I.2 Definitions + - I.2.1 Telecommunication services + - I.2.2 Service management services + - I.2.3 Service creation services +- I.3 Telecommunication services + - I.3.1 General + - I.3.2 Definitions + - I.3.3 Mobility service features (UPT, FPLMTS) + - I.3.4 Other services + - I.3.5 Other service features + +- I.4 Service management services + - I.4.1 General + - I.4.2 Definition + - I.4.3 Service management service/service feature +- I.5 Service creation services + - I.5.1 General + - I.5.2 Service specification services + - I.5.3 Service development services + - I.5.4 Service verification services + - I.5.5 Service deployment services + - I.5.6 Service creation service management services + +### **Q.1222 – Service plane for Intelligent Network Capability Set 2** + +- 1 General +- 2 Service plane architecture + - 2.1 General + - 2.2 Characterization of services and service capability requirement + - 2.2.1 Service and service feature requirements + - 2.3 Service and service feature interaction + - 2.3.1 Types of features considered for interactions + - 2.3.2 Mechanisms for handling feature interactions + - 2.4 Service plane modelling + +### **Q.1223 – Global functional plane for Intelligent Network Capability Set 2** + +- 1 General +- 2 Scope of IN global functional plane for capability set 2 +- 3 References +- 4 Global functional plane modelling for capability set 2 + - 4.1 Elements on the global functional plane + - 4.1.1 Modelling requirements + - 4.1.2 Modelling elements + - 4.2 The basic call process + - 4.3 The capability view + - 4.3.1 Definition + - 4.3.2 Service independent building blocks + - 4.3.3 Methods to describe SIBs + - 4.4 Interaction management + - 4.4.1 Interaction between SIBs + - 4.4.2 Interaction handling methods in the SIB definition phase + - 4.5 The service view + - 4.5.1 Definition + - 4.5.2 Global service logic + - 4.5.3 SIB operations + - 4.5.4 Characteristics of an HLSIB + - 4.5.5 Characteristics of a service process + - 4.5.6 Communication between service processes + - 4.5.7 Domains + - 4.6 Terminology +- 5 IN CS-2 Service Independent Building Blocks (SIBs) + - 5.1 ALGORITHM + - 5.2 AUTHENTICATE + - 5.3 CHARGE + - 5.4 COMPARE + - 5.5 DISTRIBUTION + - 5.6 END + - 5.7 INITIATE SERVICE PROCESS + - 5.8 JOIN + +- 5.9 LOG CALL INFORMATION + - 5.10 MESSAGE HANDLER + - 5.11 QUEUE + - 5.12 SCREEN + - 5.13 SERVICE DATA MANAGEMENT + - 5.14 SERVICE FILTER + - 5.15 SPLIT + - 5.16 STATUS NOTIFICATION + - 5.17 TRANSLATE + - 5.18 USER INTERACTION + - 5.19 VERIFY + - 6 IN CS-2 specialized SIBs + - 6.1 The basic call process + - 6.1.1 General + - 6.1.2 Points of initiation and points of return + - 6.1.3 BCP stage 1 description + - 6.2 Basic call unrelated process + - 6.2.1 General + - 6.2.2 Points of initiation and points of return + - 6.2.3 BCUP stage 1 description + - 7 Mapping of the service plane to the global functional plane +- Annex A – Overview of the SIBs and SIB operations +- Appendix I – IN management +- I.1 Management view + - I.2 The Basic Service Management Process (BSMP) + - I.2.1 The basic service management process + +### **Q.1224 – Distributed functional plane for Intelligent Network Capability Set 2** + +- 1 General + - 1.1 Normative references + - 1.2 Abbreviations and acronyms +- 2 Scope of IN distributed functional plane for capability set 2 + - 2.1 End user access + - 2.2 Service invocation and control + - 2.3 End user interaction + - 2.4 IN service management functionality + - 2.5 Call Party Handling + - 2.5.1 Overview + - 2.5.2 Background and motivation + - 2.5.3 Scope + - 2.5.4 Assumptions + - 2.5.5 Core Capabilities + - 2.6 Internetworking + - 2.7 Security + - 2.8 Out-Channel Call Related User Interaction (OCCRUI) + - 2.9 Out-Channel Call Unrelated User Interaction (OCUUI) + - 2.10 Wireless access + - 2.11 Feature interactions + +- 3 Distributed functional model for IN CS-2 + - 3.1 Explanation of diagram + - 3.2 IN functional model + - 3.3 Definition of functional entities related to IN service execution + - 3.3.1 CCA function (CCAF) + - 3.3.2 CC function (CCF) + - 3.3.3 SS function (SSF) + - 3.3.4 SC function (SCF) + - 3.3.5 SD function (SDF) + - 3.3.6 SR function (SRF) + - 3.3.7 IA function (IAF) + - 3.3.8 CUS function (CUSF) + - 3.3.9 SCUA function (SCUAF) + - 3.3.10 SM function (SMF) + - 3.4 Use of individual relationships between functional entities related to IN service execution + - 3.4.1 SCF-SSF relationship + - 3.4.2 SCF-SCF relationship + - 3.4.3 SCF-IAF relationship + - 3.4.4 SRF-CCF relationship + - 3.4.5 SCF-SRF relationship + - 3.4.6 SRF-SCF relationship + - 3.4.7 SRF-SMF relationship + - 3.4.8 SDF-SDF relationship + - 3.4.9 SCF-SDF relationship + - 3.4.10 SCF-CUSF relationship + - 3.4.11 CUSF-SSF relationship + - 3.4.12 CUSF-CCF relationship + - 3.4.13 SMF-SCF relationship + - 3.4.14 SMF-SDF relationship + - 3.4.15 SMF-SSF/CCF relationship + - 3.4.16 SMF-SRF relationship + - 3.4.17 SMF-SMAF relationship + - 3.4.18 SMF-SCEF relationship + - 3.4.19 SMF-SMF relationship + - 3.4.20 SMF-CUSF relationship + - 3.5 Overview of functional entity call/service logic processing models +- 4 SSF/CCF model + - 4.1 General + - 4.2 Basic Call Manager (BCM) + - 4.2.1 BCSM + - 4.2.2 CS-2 BCSM description + - 4.2.3 BCSM resume points and BCSM transitions in the IN CS-2 call model + - 4.2.4 BCSM indications for the CS-2 call model + - 4.2.5 BCSM detection points + - 4.2.6 DP criteria + - 4.2.7 Trigger types and trigger precedence + - 4.2.8 DP processing + - 4.2.9 Out-Channel Call Related User Interaction (OCCRUI) + - 4.3 IN-Switching Manager (IN-SM) + - 4.3.1 IN-Switching State Model (IN-SSM) + - 4.3.2 IN-SM Core Capabilities for Call Party Handling + - 4.3.3 The Connection View State (CVS) approach + - 4.3.4 The Hybrid Approach + - 4.3.5 IN-SSM EDPs + - 4.3.6 SSF resource control + +- 4.4 Feature Interactions Manager (FIM)/Call Manager (CM) + - 4.4.1 FIM/CM functions + - 4.4.2 Service logic instance interactions considerations + - 4.4.3 FIM mechanisms +- 4.5 Relationship of SSF/CCF Model Components + - 4.5.1 General + - 4.5.2 Typical sequence of model actions +- 4.6 Relationship of SSF/CCF to SCF +- 5 Specialized Resource Function (SRF) model + - 5.1 General + - 5.2 SRF Components + - 5.2.1 Functional Entity Access Manager (FEAM) + - 5.2.2 Resource Control Part (RCP) + - 5.2.3 Resource Function Part (RFP) + - 5.2.4 Data Part (DP) + - 5.3 Objects of SRF management +- 6 Service Control Function (SCF) model + - 6.1 General + - 6.2 SCF components + - 6.2.1 General + - 6.2.2 Service Logic Execution Manager (SLEM) + - 6.2.3 SCF data access manager + - 6.2.4 Functional routine manager + - 6.2.5 Functional Entity Access Manager (FEAM) + - 6.2.6 SLP manager + - 6.2.7 Security manager + - 6.3 Functional routine categories + - 6.3.1 SLPI management functional routines + - 6.3.2 SLPI communication functional routines + - 6.3.3 Timer management functional routines + - 6.3.4 Data management interface functional routines + - 6.3.5 Asynchronous event handling functional routines + - 6.3.6 Connection management functional routines + - 6.3.7 Specialized resource management functional routines + - 6.3.8 OAM functional routines +- 7 Service Data Function (SDF) model + - 7.1 General + - 7.2 SDF components + - 7.2.1 General + - 7.2.2 SDF data manager + - 7.2.3 Functional entity access manager + - 7.2.4 Security manager + - 7.3 Data types handled by SDF +- 8 Call Unrelated Service Function (CUSF) model + - 8.1 General + - 8.2 Basic Non-Call Manager (BNCM) + - 8.2.1 BCUSM + - 8.2.2 BCUSM description for CS-2 + - 8.2.3 Transition for BCUSM + - 8.2.4 BCUSM DP criteria + - 8.3 Description of relationship model + +- 9 Service Management Function (SMF) model + - 9.1 General + - 9.2 SMF components + - 9.2.1 General +- 10 Mapping of the global functional plane to the distributed functional plane + - 10.1 Mapping of POIs and PORs to DPs and PICs +- 11 Information flow diagrams and distributed service logic in the DFP + - 11.1 Introduction + - 11.1.1 Functional model + - 11.1.2 Description of functional entities + - 11.1.3 Numbering of functional entity actions + - 11.1.4 Relationship with clause 12 (information flow descriptions) + - 11.1.5 Organization of clause 11 + - 11.1.6 Generic security information flows + - 11.1.7 SDF-SDF interactions + - 11.1.8 SCF-SCF interactions + - 11.2 SIB stage 2 descriptions + - 11.2.1 ALGORITHM SIB + - 11.2.2 AUTHENTICATE SIB + - 11.2.3 CHARGE SIB + - 11.2.4 COMPARE SIB + - 11.2.5 DISTRIBUTION SIB + - 11.2.6 END SIB + - 11.2.7 INITIATE SERVICE PROCESS SIB + - 11.2.8 JOIN SIB + - 11.2.9 LOG CALL INFORMATION SIB + - 11.2.10 MESSAGE HANDLER SIB + - 11.2.11 QUEUE SIB + - 11.2.12 SCREEN SIB + - 11.2.13 SERVICE DATA MANAGEMENT SIB + - 11.2.14 SERVICE FILTER SIB + - 11.2.15 SPLIT SIB + - 11.2.16 STATUS NOTIFICATION SIB + - 11.2.17 TRANSLATE SIB + - 11.2.18 USER INTERACTION SIB + - 11.2.19 VERIFY SIB + - 11.3 BASIC PROCESS SIBs + - 11.3.1 BASIC CALL PROCESS SIB + - 11.3.2 BASIC CALL UNRELATED PROCESS SIB + - 11.4 Stage 2 description of other distributed functionality + - 11.4.1 Activity test functionality + - 11.4.2 Call gap capability + - 11.5 Distributed service logic + - 11.5.1 SDL diagrams + - 11.5.2 Distributed service logic for SSF + - 11.5.3 Distributed service logic for assist/hand-off SSF + - 11.5.4 Distributed service logic for SRF + - 11.5.5 Distributed service logic for SCF + - 11.5.6 Distributed service logic for SDF + - 11.5.7 Distributed service logic for CUSF + - 11.6 Mapping between information flows and SIBs +- 12 Relationships between FEs + - 12.1 General + - 12.2 Relationships + - 12.3 Information flows between FEs + +- 12.4 SCF-SSF relationship + - 12.4.1 General + - 12.4.2 DP specific Common Elements + - 12.4.3 Information flows between SCF and SSF + - 12.4.4 IE Definitions for SSF/CCF to SCF information flows +- 12.5 SCF-SRF relationship + - 12.5.1 General + - 12.5.2 Information flows between the SCF and SRF + - 12.5.3 IE Definitions for SCF to SRF information flows +- 12.6 SCF-SCF relationship + - 12.6.1 General + - 12.6.2 Information flows between the SCF and SCF + - 12.6.3 IE Definitions for SCF to SCF information flows +- 12.7 SCF-CUSF relationship + - 12.7.1 General + - 12.7.2 Information flows between the SCF and CUSF + - 12.7.3 IE Description for the SCF-CUSF information flows +- 12.8 SCF-SDF relationship + - 12.8.1 General + - 12.8.2 Information flows between the SCF and SDF + - 12.8.3 IE Description for the SCF-SDF information flows +- 12.9 SDF-SDF relationship + - 12.9.1 General + - 12.9.2 Information flows between the SDF and SDF + - 12.9.3 IE Description for the SDF-SDF information flows +- 12.10 IE Population Rules + - 12.10.1 SSF/CCF to SCF Information Flows +- 12.11 Summary of information flows and related SIBs + +## Annex A – Mobility aspects + +- A.1 General +- A.2 Scope +- A.3 Mobility Aspects of Distributed Functional Model for IN CS-2 + - A.3.1 Explanation of the diagram + - A.3.2 Wireless access enhancements to the IN functional model + - A.3.3 Definitions of wireless access specific functional entities related to IN service execution + - A.3.4 Use of individual relationships between FEs for wireless access +- A.4 Example mapping of wireless access FEs to physical platforms + - A.4.1 Example mapping 1 + - A.4.2 Example mapping 2 + - A.4.3 Example mapping 3 + - A.4.4 Example mapping 4 + - A.4.5 Example mapping 5 + - A.4.6 Example mapping 6 + - A.4.7 Example mapping 7: RCF and CRACF in RS, CURACF in SCP + - A.4.8 Example mapping 8: RCF and CRACF in RS, CURACF in standalone platform + - A.4.9 Example mapping 9: RCF in Radio System, CRACF in standalone platform CURACF in SCP + - A.4.10 Example mapping 10: RCF in Radio System, CRACF in standalone platform and CURACF in standalone platform + +## Annex B – Telecommunications Management Network (TMN) concepts + +- B.1 Introduction +- B.2 The TMN functional architecture + - B.2.1 Operations Systems + - B.2.2 Work Station Functions + - B.2.3 The Human Machine Adaptation (HMA) + - B.2.4 TMN information modelling +- B.3 Applying TMN concepts to the IN + - B.3.1 IN management functional model + - B.3.2 Correspondence between the IN concept of SIB and the TMN concept of MO + - B.3.3 IN management protocols +- B.4 Modelling aspects imported from TMN + - B.4.1 Mappings of IN SMF onto TMN logical layers + - B.4.2 Mapping of IN SMF onto TMN management functions + - B.4.3 Mapping of the IN SCEF onto TMN logical layers +- B.5 IN management and generic TMN management + - B.5.1 Management process independence + - B.5.2 SMF complexity +- B.6 IN SMF-SMF internetworking relationship mapping to TMN + - B.6.1 Fault management example + +## Annex C – IN SSF Q3 Management Information Model + +- C.1 Introduction + - C.1.1 Technical approach +- C.2 SSF functional decomposition + - C.2.1 Rationale + - C.2.2 Method +- C.3 SSF management requirements + - C.3.1 Rationale + - C.3.2 Method +- C.4 SSF management information model + +## Annex D – IN testing and fault management + +- D.1 Introduction +- D.2 IN testing capabilities for the SSF/CCF + - D.2.1 Translation Check + - D.2.2 Trigger Data Check + - D.2.3 SSF/CCF Query Test + - D.2.4 Using the SSF/CCF testing capabilities +- D.3 IN end-to-end testing + - D.3.1 IN end-to-end testing information elements + - D.3.2 SSF to SCF + - D.3.3 SCF to SSF + - D.3.4 SCF-SRF + - D.3.5 SRF-SCF + +### Appendix I – Example/application of IN SSF Q3 management information model + +- I.1 Introduction +- I.2 SSF functional decomposition + - I.2.1 SSF model +- I.3 Example to illustrate development of information models and managed object requirements + - I.3.1 General + - I.3.2 Example of trigger management information model and managed object requirements + - I.3.3 SMF functionality mapping to information model + - I.3.4 SSF/CCF functionality mapping to information model + - I.3.5 SSF/CCF information model managed object requirements + +### Appendix II – Information flows and call models for terminal mobility + +- II.1 General +- II.2 Functional entity call/service processing models for wireless access + - II.2.1 Overview + - II.2.2 Terminal Access State Model (TASM) + - II.2.3 Basic Non-Call Associate State Model for CURACF (BNCSM) + - II.2.4 BCSM +- II.3 Information flow enhancements for wireless access + - II.3.1 General + - II.3.2 Relationships + - II.3.3 Information flows between FEs + - II.3.4 SCF-SSF relationship + - II.3.5 SCF-CRACF relationship + - II.3.6 SCF-CURACF relationship + +### Q.1225 – Physical plane for Intelligent Network Capability Set 2 + +- 1 General +- 2 Requirements and assumptions + - 2.1 Requirements + - 2.2 Assumptions +- 3 Physical Entities (PEs) +- 4 Mapping requirements +- 5 Mapping the distributed functional plane to the physical plane + - 5.1 Mapping of functional entities to physical entities + - 5.2 Mapping of FE-FE relationships to PE-PE relationships + - 5.3 Selection of underlying protocol platforms + - 5.3.1 SCP-SSP interface + - 5.3.2 AD-SSP interface + - 5.3.3 IP-SSP interface + - 5.3.4 SN-SSP interface + - 5.3.5 SCP-IP interface + - 5.3.6 AD-IP interface + - 5.3.7 SCP-SDP interface + - 5.3.8 User interfaces + - 5.3.9 Enhanced ISDN CPE-CUSP interface + - 5.3.10 AD-CUSP interface + +### Q.1228 – Interface Recommendations for Intelligent Network Capability Set 2 + +- 1 Introduction +- 2 General + - 2.1 Normative references + - 2.2 Abbreviations and acronyms + - 2.3 Conventions +- 3 Interface recommendation for telecommunication services + - 3.1 General + - 3.1.1 Definition methodology + - 3.1.2 Example physical scenarios + - 3.1.3 INAP protocol architecture + - 3.1.4 INAP addressing + - 3.1.5 Relationship between Recommendation Q.1224 and this Recommendation + - 3.1.6 Compatibility mechanisms used for INAP + - 3.2 SACF/MACF rules + - 3.2.1 Reflection of TCAP AC + - 3.2.2 Sequential/parallel execution of operations + + + +- 8.3 The IN X.500 DISP Subset + - 8.3.1 Shadowing agreement specification + - 8.3.2 DSA Shadow Bind + - 8.3.3 IN-DSA Shadow Unbind + - 8.3.4 Coordinate Shadow Update + - 8.3.5 Update Shadow + - 8.3.6 Request Shadow Update +- 8.4 The IN X.500 DSP Subset + - 8.4.1 Information types and common procedures + - 8.4.2 DSA Bind + - 8.4.3 IN DSA Unbind + - 8.4.4 Chained Operations + - 8.4.5 Chained Errors +- 8.5 Protocol overview + - 8.5.1 ROS-Objects and contracts + - 8.5.2 DSP contract and packages + - 8.5.3 DISP contract and packages +- 8.6 Protocol abstract syntax + - 8.6.1 DSP Abstract Syntax + - 8.6.2 DISP Abstract Syntax + - 8.6.3 Directory System Application Context + - 8.6.4 Directory Shadow Application Context + - 8.6.5 Versions and the rules for extensibility +- 8.7 Conformance + - 8.7.1 Conformance by SDFs + - 8.7.2 Conformance by a shadow supplier + - 8.7.3 Conformance by a shadow consumer +- 8.8 ASN.1 modules for the SDF-SDF interface + - 8.8.1 IN-CS2-SDF-SDF-Protocol Module +- 9 SCF/SCF interface + - 9.1 SCF/SCF operations and arguments + - 9.2 SCF/SCF contracts, packages and Application Contexts + - 9.2.1 Protocol overview + - 9.2.2 ASN.1 modules +- 10 SCF/CUSF interface + - 10.1 Operations and arguments + - 10.2 SCF/CUSF Contracts, Operation Packages, and Application Contexts + - 10.2.1 Protocol overview + - 10.2.2 ASN.1 module +- 11 SSF application entity procedures + - 11.1 General + - 11.2 Model and interfaces + - 11.3 Relations between SSF FSM and the CCF and maintenance functions + - 11.4 SSF management finite state model (SSME FSM) + - 11.5 SSF switching state model (SSM) FSM + - 11.5.1 Finite State Model for Call Segment Association (CSA) + - 11.5.2 Finite State Model for Call Segment + - 11.6 Assisting SSF FSM + - 11.6.1 State aa: Idle + - 11.6.2 State ab: Waiting For Instructions + - 11.6.3 State ac: Waiting For End Of User Interaction + +- 11.7 Handed-off SSF FSM + - 11.7.1 State ha: Idle + - 11.7.2 State hb: Waiting for Instructions + - 11.7.3 State hc: Waiting for End Of User Interaction +- 11.8 User Service Interaction USI FSM +- 12 SCF application entity procedures + - 12.1 General + - 12.2 Model and interfaces + - 12.3 Relationship between the SCF FSM and the SLPs/maintenance functions + - 12.4 Partial SCF Management Entity (SCME) State Transition Diagram + - 12.4.1 State M1: Status report idle + - 12.4.2 State M2: Waiting for SSF Resource Status Report + - 12.4.3 State M3: Service filtering idle + - 12.4.4 State M4: Waiting for SSF service filtering response + - 12.4.5 State M5: Activity test idle + - 12.4.6 State M6: Waiting for activity test response + - 12.4.7 State M7: ManageTriggerData idle + - 12.4.8 State M8: Waiting for ManageTriggerData activity test response + - 12.4.9 The Resource Control Object + - 12.5 The SCF Call State Model (SCSM) + - 12.5.1 SSF/SRF-related states (SCSM-SSF/SRF) + - 12.5.2 SDF-related states (SCSM-SDF) + - 12.5.3 SCF-related states + - 12.5.4 CUSF-related states (SCSM-CUSF) + - 12.5.5 USI\_SCF FSM +- 13 SRF application entity procedures + - 13.1 General + - 13.2 Model and interfaces + - 13.3 Relationship between the SRF FSM and maintenance functions/bearer connection handling + - 13.4 The SRSM + - 13.4.1 State 1: Idle + - 13.4.2 State 2: Connected + - 13.4.3 State 3: User interaction + - 13.5 Example SRF control procedures + - 13.5.1 SRF connect procedures + - 13.5.2 SRF end-user interaction procedures + - 13.5.3 SRF disconnection procedures + - 13.5.4 Examples illustrating Complete User Interaction Sequences +- 14 SDF application entity procedures + - 14.1 General + - 14.2 Model and interfaces + - 14.3 The SDF FSM structure + - 14.4 SDF state transition models + - 14.4.1 SDF state transition model for SCF-related states + - 14.4.2 SDF state transition model for SDF-related states +- 15 CUSF application entity procedures + - 15.1 General + - 15.2 Model and interfaces + - 15.2.1 Background for the modelling and protocol + - 15.2.2 Modelling and protocol + - 15.3 Relations between CUSF FSM and the SSF/CCF and maintenance functions + +- 15.4 CUSF management finite state model (CUSME FSM) +- 15.5 CUSF state transition diagram + - 15.5.1 State a: Idle + - 15.5.2 State b: Waiting For Instructions + - 15.5.3 State c: Monitoring +- 16 Error procedures + - 16.1 Operation related error procedures + - 16.1.1 AttributeError + - 16.1.2 Cancelled + - 16.1.3 CancelFailed + - 16.1.4 DSAREferral + - 16.1.5 ETCFailed + - 16.1.6 ExecutionError + - 16.1.7 ImproperCallerResponse + - 16.1.8 MissingCustomerRecord + - 16.1.9 MissingParameter + - 16.1.10 Name Error + - 16.1.11 ParameterOutOfRange + - 16.1.12 Referral + - 16.1.13 RequestedInfoError + - 16.1.14 ScfReferral + - 16.1.15 Security + - 16.1.16 Service + - 16.1.17 Shadow + - 16.1.18 SystemFailure + - 16.1.19 TaskRefused + - 16.1.20 UnavailableResource + - 16.1.21 UnexpectedComponentSequence + - 16.1.22 UnexpectedDataValue + - 16.1.23 UnexpectedParameter + - 16.1.24 UnknownLegID + - 16.1.25 UnknownResource + - 16.1.26 Update + - 16.1.27 ChainingRefused + - 16.1.28 DirectoryBindError + - 16.1.29 ScfBindFailure + - 16.1.30 ScfTaskRefused + - 16.2 Entity-related error procedures + - 16.2.1 Expiration of TSSF + - 16.2.2 Expiration of TSRF + - 16.2.3 Expiration of TCUSF +- 17 Detailed operation procedures + - 17.1 ActivateServiceFiltering procedure + - 17.2 ActivationReceivedAndAuthorized procedure + - 17.3 ActivityTest procedure + - 17.4 AddEntry procedure + - 17.5 AnalysedInformation procedure + - 17.6 AnalyseInformation procedure + - 17.7 ApplyCharging procedure + - 17.8 ApplyChargingReport procedure + - 17.9 AssistRequestInstructions procedure + - 17.10 AssociationReleaseRequested procedure + - 17.11 AuthorizeTermination procedure + - 17.12 CallGap procedure + - 17.13 CallInformationReport procedure + - 17.14 CallInformationRequest procedure + - 17.15 Cancel procedure + - 17.16 CancelStatusReportRequest procedure + +17.17 chainedAddEntry procedure + 17.18 ChainedConfirmedNotificationProvided procedure + 17.19 ChainedConfirmedReportChargingInformation procedure + 17.20 ChainedEstablishChargingRecord procedure + 17.21 chainedExecute procedure + 17.22 ChainedHandlingInformationRequest procedure + 17.23 ChainedHandlingInformationResult procedure + 17.24 chainedModifyEntry procedure + 17.25 ChainedNetworkCapability procedure + 17.26 ChainedNotificationProvided procedure + 17.27 ChainedReportChargingInformation procedure + 17.28 ChainedProvideUserInfo procedure + 17.29 chainedRemoveEntry procedure + 17.30 ChainedRequestNotification procedure + 17.31 chainedSearch procedure + 17.32 CollectedInformation procedure + 17.33 CollectInformation procedure + 17.34 ComponentReceived procedure + 17.35 ConfirmedNotificationProvided procedure + 17.36 ConfirmedReportChargingInformation procedure + 17.37 Connect procedure + 17.38 ConnectToResource procedure + 17.39 Continue procedure + 17.40 ContinueWithArgument procedure + 17.41 CoordinateShadowUpdate procedure + 17.42 CreateCallSegmentAssociation procedure + 17.43 in-directoryBind procedure + 17.44 DirectoryUnbind procedure + 17.45 DisconnectForwardConnection procedure + 17.46 DisconnectForwardConnectionWithArgument procedure + 17.47 DisconnectLeg procedure + 17.48 dSABind procedure + 17.49 DSAShadowBind procedure + 17.50 in-DSAShadowUnbind procedure + 17.51 EntityReleased Procedure + 17.52 EstablishChargingRecord procedure + 17.53 EstablishTemporaryConnection procedure + 17.54 EventNotificationCharging procedure + 17.55 EventReportBCSM procedure + 17.56 EventReportFacility procedure + 17.57 Execute procedure + 17.58 FacilitySelectedAndAvailable procedure + 17.59 FurnishChargingInformation procedure + 17.60 HandlingInformationRequest procedure + 17.61 HandlingInformationResult procedure + 17.62 HoldCallInNetwork procedure + 17.63 in-DSAUnbind procedure + 17.64 InitialDP procedure + 17.65 InitiateAssociation procedure + 17.66 InitiateCallAttempt procedure + 17.67 ManageTriggerData procedure + 17.68 MergeCallSegments procedure + 17.69 ModifyEntry procedure + +17.70 MoveCallSegments procedure + 17.71 MoveLeg procedure + 17.72 NetworkCapability procedure + 17.73 NotificationProvided procedure + 17.74 OAbandon procedure + 17.75 OAnswer procedure + 17.76 OCalledPartyBusy procedure + 17.77 ODisconnect procedure + 17.78 OMidCall procedure + 17.79 ONoAnswer procedure + 17.80 OriginationAttempt procedure + 17.81 OriginationAttemptAuthorized procedure + 17.82 OSuspended procedure + 17.83 PlayAnnouncement procedure + 17.84 PromptAndCollectUserInfoInformation procedure + 17.85 PromptAndReceiveMessage procedure + 17.86 ProvideUserInfoInformation procedure + 17.87 Reconnect procedure + 17.88 ReleaseAssociation procedure + 17.89 ReleaseCall procedure + 17.90 RemoveEntry procedure + 17.91 ReportChargingInformation procedure + 17.92 ReportUTSI procedure + 17.93 RequestCurrentStatusReport procedure + 17.94 RequestEveryStatusChangeReport procedure + 17.95 RequestFirstStatusMatchReport procedure + 17.96 RequestNotification procedure + 17.97 RequestNotificationChargingEvent procedure + 17.98 RequestReportBCSMEVENT procedure + 17.99 RequestReportBCUSMEVENT procedure + 17.100 RequestReportFacilityEvent procedure + 17.101 RequestReportUTSI procedure + 17.102 RequestShadowUpdate procedure + 17.103 ResetTimer procedure + 17.104 RouteSelectFailure procedure + 17.105 SCFBind procedure + 17.106 scfBind procedure (in the chaining case) + 17.107 SCFUnBind procedure + 17.108 scfUnBind procedure (in the chaining case) + 17.109 ScriptClose procedure + 17.110 ScriptEvent procedure + 17.111 ScriptInformation procedure + 17.112 ScriptRun procedure + 17.113 Search procedure + 17.114 SelectFacility procedure + 17.115 SelectRoute procedure + 17.116 SendChargingInformation procedure + 17.117 SendComponent procedure + 17.118 SendFacilityInformation procedure + 17.119 SendSTUI procedure + 17.120 ServiceFilteringResponse procedure + +- 17.121 SpecializedResourceReport procedure +- 17.122 SplitLeg procedure +- 17.123 StatusReport procedure +- 17.124 TAnswer procedure +- 17.125 TBusy procedure +- 17.126 TDisconnect procedure +- 17.127 TerminationAttempt procedure +- 17.128 TermAttemptAuthorized procedure +- 17.129 TMidCall procedure +- 17.130 TNoAnswer procedure +- 17.131 TSuspended procedure +- 17.132 UpdateShadow procedure +- 18 Services assumed from Lower Layers + - 18.1 Services assumed from TCAP + - 18.1.1 Common procedures + - 18.1.2 SSF-SCF interface + - 18.1.3 SCF-SRF interface + - 18.1.4 SCF-CUSF interface + - 18.1.5 SCF-SCF interface + - 18.1.6 SCF-SDF interface + - 18.1.7 SDF-SDF interface + - 18.2 Services assumed from SCCP + - 18.2.1 Normal procedures + - 18.2.2 Service functions from SCCP +- 19 IN generic interface security + - 19.1 Interface security requirements + - 19.1.1 Data confidentiality + - 19.1.2 Data integrity and data origin authentication + - 19.1.3 Key management + - 19.2 Procedures and algorithms + - 19.2.1 Authentication procedures + - 19.2.2 SPKM algorithms and negotiation + - 19.2.3 Three-way mutual authentication + - 19.2.4 Assignment of credentials + - 19.3 Mapping of security information flow definitions to tokens + - 19.4 Security FSM definitions + - 19.4.1 Two-way mutual authentication FSMs + - 19.4.2 Three-way mutual authentication FSMs +- Annex A.1 – Introduction to the INAP CS-1 and CS-2 SDL models + - A.1.1 Introduction + - A.1.2 Example for the interworking of the SSF/CCF SDL processes + - A.1.3 Example for the Three-Party Call setup as seen from the environment +- Annex A.2 – Transition diagrams + - A.2.1 Call Segment Association transition diagram + - A.2.2 Call Segment transition diagram +- Annex A.3 – SDL Specification of CS-1 SSF/CCF +- Annex A.4 – SDL Specification of CS-2 extensions to SSF/CCF +- Annex A.5 – SDL Specification of CS-2 SRF +- Annex A.6 – SDL Specification of CS-2 Assist/Hand-off SSF +- Annex A.7 – SDL Specification of CS-2 CUSF +- Annex A.8 – SDL Specification of CS-2 SCF + +Appendix I – Expanded ASN.1 source + +Appendix II – Data modelling + +- II.1 Introduction + - II.1.1 Purpose and scope + - II.1.2 Assumptions + - II.1.2.1 Mobility service and subscriber identifiers + - II.1.2.2 Disclosure of profile entries +- II.2 Directory Information Tree (DIT) schema + - II.2.1 X.500 DIT + - II.2.1.1 Location of local profiles + - II.2.1.2 Location of remote subscriber profiles + - II.2.1.3 Location of locally visiting subscriber profiles + - II.2.1.4 Reducing message flow + - II.2.2 Object classes + - II.2.2.1 inMobilityUserProfile + - II.2.2.2 inMobilityServiceProvider + - II.2.2.3 inMobilitySubscriberGroup + - II.2.3 Attribute types + - II.2.3.1 inMobilityID + - II.2.3.2 inMobilityPIN + - II.2.3.3 inMobilityPrefix + - II.2.3.4 inMobilitySubPrefix + - II.2.4 DIT structure definition + - II.2.4.1 Name forms + - II.2.4.2 Structure rules + - II.2.4.3 Object identifier assignments + +Appendix III – Examples of SPKM algorithms for IN CS-2 + +- III.1 General +- III.2 Integrity Algorithm (I-ALG) + - III.2.1 Example-1 + - III.2.2 Example-2 + - III.2.3 Example-3 + - III.2.4 Example-4 +- III.3 Confidentiality Algorithm (C-ALG) + - III.3.1 Example-1 +- III.4 Key Establishment Algorithm (K-ALG) + - III.4.1 Example-1 + - III.4.2 Example-2 + - III.4.3 Example-3 +- III.5 One-Way Function (O-ALG) for Subkey Derivation Algorithm + - III.5.1 Example-1 + +**Q.1229 – Users’ Guide for Intelligent Network Capability Set 21** + +--- + +1 Presently in the stage of draft. + +## ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1221-199709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1221-199709-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..28e99cd1cc66bd034697b6d4c6c72c2d0909dea7 --- /dev/null +++ b/marked/Q/T-REC-Q.1221-199709-I_PDF-E/raw.md @@ -0,0 +1,1447 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1221** + +(09/97) + +SERIES Q: SWITCHING AND SIGNALLING +Intelligent Network + +# --- **Introduction to Intelligent Network Capability Set 2** + +ITU-T Recommendation Q.1221 + +(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.* + +# **INTRODUCTION TO INTELLIGENT NETWORK CAPABILITY SET 2** + +## **Summary** + +Intelligent Network Capability Set 2 (IN CS-2) is the second standardized stage of the Intelligent Network (IN) as an architectural concept for the creation and provision of services, including telecommunication services, service management services and service creation services. This Recommendation gives an introduction to IN CS-2. It describes the main characteristics and overall capabilities of IN CS-2 and defines the service aspects, network aspects and functional relationships that form the basis of the IN CS-2 capabilities. + +This Recommendation is the first in the Q.122x-Series of Recommendations devoted to IN CS-2, which builds on the architectural principles of IN as described in the Q.121x- and the Q.120x-Series of Recommendations. + +The IN CS-2 Recommendations form a detailed and stable basis for implementing IN CS-2 telecommunication services. They also provide high-level guidelines for supporting service management services, service creation services and some partially supported telecommunication services. The IN CS-2 Recommendations are intended to give the same degree of technical information as the IN CS-1 Recommendations (1995). + +## **Source** + +ITU-T Recommendation Q.1221 was prepared 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 | Phased standardization ..... | 2 | +| 3 | General description and scope of IN CS-2 ..... | 2 | +| 3.1 | Criteria for IN CS-2..... | 2 | +| 3.2 | Evolution of IN CS-2 ..... | 2 | +| 4 | Overview of IN CS-2 Recommendations..... | 3 | +| 5 | Service aspects ..... | 3 | +| 5.1 | Telecommunication services ..... | 5 | +| 5.2 | Service management services..... | 5 | +| 5.3 | Service creation services ..... | 6 | +| 5.4 | Network support of IN CS-2 services ..... | 7 | +| 6 | Network aspects ..... | 7 | +| 6.1 | Network functions ..... | 8 | +| 6.2 | Control architecture principles ..... | 9 | +| 6.2.1 | Service invocation and control..... | 9 | +| 6.2.2 | End-user interactions..... | 9 | +| 6.2.3 | Service management ..... | 10 | +| 6.3 | Feature interactions ..... | 10 | +| 6.4 | Consistency among IN CS-2 supported service features..... | 10 | +| 7 | Functional relationships and interfaces ..... | 10 | +| 7.1 | Functional relationships and control classes ..... | 10 | +| 7.1.1 | Bearer connection control ..... | 11 | +| 7.1.2 | Non-IN call control ..... | 11 | +| 7.1.3 | IN service control..... | 12 | +| 7.1.4 | Service management control..... | 12 | +| 7.1.5 | Non-IN call unrelated control ..... | 12 | +| 7.2 | Key functions and interfaces ..... | 12 | +| 7.2.1 | Single point multiple points of control ..... | 12 | +| 7.2.2 | Single-ended/multi-ended calls..... | 12 | +| 7.2.3 | Mid-call interruption ..... | 13 | +| 7.2.4 | Call party handling..... | 13 | +| 7.2.5 | Enhanced SRF ..... | 13 | +| 7.2.6 | Call unrelated user interaction ..... | 13 | +| 7.2.7 | Out-channel call related user interaction..... | 13 | + +| | Page | +|-------------------------------------------------------------|-------------| +| 7.2.8 Service/feature interaction (service processing)..... | 13 | +| 7.2.9 Internetworking ..... | 14 | +| 7.2.10 Security ..... | 15 | +| 7.2.11 IN-TMN ..... | 16 | +| 7.2.12 Service management ..... | 16 | +| 7.2.13 Service creation..... | 19 | +| 7.2.14 Personal mobility ..... | 21 | +| Appendix I – IN CS-2 benchmark services and features..... | 22 | +| I.1 General ..... | 22 | +| I.2 Definitions ..... | 22 | +| I.2.1 Telecommunication services..... | 22 | +| I.2.2 Service management services..... | 22 | +| I.2.3 Service creation services ..... | 22 | +| I.3 Telecommunication services ..... | 22 | +| I.3.1 General ..... | 22 | +| I.3.2 Definitions..... | 22 | +| I.3.3 Mobility service features (UPT, FPLMTS)..... | 23 | +| I.3.4 Other services..... | 28 | +| I.3.5 Other service features..... | 30 | +| I.4 Service management services..... | 34 | +| I.4.1 General ..... | 34 | +| I.4.2 Definition ..... | 34 | +| I.4.3 Service management service/service feature..... | 35 | +| I.5 Service creation services ..... | 37 | +| I.5.1 General ..... | 37 | +| I.5.2 Service specification services ..... | 37 | +| I.5.3 Service development services ..... | 37 | +| I.5.4 Service verification services ..... | 38 | +| I.5.5 Service deployment services ..... | 38 | +| I.5.6 Service creation service management services ..... | 39 | + +# **INTRODUCTION TO INTELLIGENT NETWORK CAPABILITY SET 2** + +*(Geneva, 1997)* + +# **1 Introduction** + +Intelligent Network Capability Set 2 (IN CS-2) is the second standardized stage of the Intelligent Network (IN) as an architectural concept for the creation and provision of services, including telecommunication services, service management services and service creation services. This Recommendation gives an introduction to IN CS-2. It describes the main characteristics and overall capabilities of IN CS-2 and defines the service aspects, network aspects and functional relationships that form the basis of the IN CS-2 capabilities. + +Listed below are the acronyms used in this Recommendation: + +| | | +|--------|----------------------------------------------------------------------------------| +| BCSM | Basic Call State Model | +| CCAF | Call Control Agent Function | +| CCF | Call Control Function | +| CCIS | Common Channel Interoffice Signalling | +| CRACF | Call-related Radio Access Control Function | +| CS | Capability Set | +| CURACF | Call-Unrelated Radio Access Control Function | +| CUSF | Call-Unrelated Service Function | +| DTMF | Dual-Tone Multi-Frequency | +| FE | Functional Entity | +| GFP | Global Functional Plane | +| IAF | Intelligent Access Function | +| INAP | Intelligent Network Application Protocol | +| IN-SSM | IN-Switching State Model | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| OAM | Operation, Administration, and Maintenance | +| PBX | Private Branch Exchange | +| PE | Physical Entity | +| PLMN | Public Land Mobile Network | +| PSTN | Public Switched Telephone Network | +| QOS | Quality of Service | +| RCF | Radio Control Function | +| SCE | Service Creation Environment | +| SCEF | Service Creation Environment Function | +| SCF | Service Control Function | + +| | | +|-------|---------------------------------------| +| SCUAF | Service Control User Agent Function | +| SDF | Service Data Function | +| SIB | Service-Independent Building Blocks | +| SMAF | Service Management Access Function | +| SMF | Service Management Function | +| SRF | Specialized Resource Function | +| SS7 | Signalling System No. 7 | +| SSF | Service Switching Function | +| TMN | Telecommunications Management Network | +| UPT | Universal Personal Telecommunication | + +## 2 Phased standardization + +The phased approach of IN capability sets has been described in Recommendation Q.1201. + +In order to prepare for the next phases of IN (CS-3 and beyond), the IN CS-2 Recommendations contain both complete technical specifications (with complete support for physical architecture and detailed protocol description) and incomplete specifications that are intended to be the base for subsequent capability sets (with SIB description and the impact on the functional architecture). Capabilities which are only incompletely covered by IN CS-2 Recommendations are highlighted through special notes or caveats. + +## 3 General description and scope of IN CS-2 + +### 3.1 Criteria for IN CS-2 + +IN CS-2 defines an initial subset of IN capabilities that meet the following general criteria: + +- IN CS-2 is a subset of the target Intelligent Network architecture; +- IN CS-2 is a superset of IN CS-1, as defined in the IN CS-1 Recommendations (1995); +- IN CS-2 is a set of definitions of capabilities that is of direct use to both manufacturers and network operators; +- IN CS-2 provides network capabilities defined to support the set of IN CS-2 benchmark services or service features. These capabilities can also be used for the support of other services that may, or may not, be standardized by ITU-T. + +The IN CS-2 architecture could be applied for PSTN, ISDN, and mobile networks. + +### 3.2 Evolution of IN CS-2 + +The IN CS-2 Recommendations (Q.122x-Series) form a detailed and stable basis for implementing IN CS-2 telecommunication services. They also give high-level guidelines for supporting service management services and service creation services and some partially supported telecommunication services. Complete technical specifications of these services will be in the subsequent IN capability sets. + +As IN CS-1, IN CS-2 takes into account the evolution requirement. It is defined to support the IN CS-2 benchmark services and service features without assumptions that are known to limit its evolution into future capability sets. + +The IN CS-2 Recommendations are intended to give the same degree of technical information as the IN CS-1 Recommendations (Q.121x-Series). + +## 4 Overview of IN CS-2 Recommendations + +Table 1 contains an overview of the Recommendations that are specifically related to IN CS-2: + +**Table 1/Q.1221 – IN CS-2 Recommendations** + +| Rec. | Title | +|-------------|-----------------------------------------------------------------------------| +| Q.1220 | Q.1220-Series Intelligent network capability set 2 Recommendation structure | +| Q.1221 | Introduction to Intelligent Network Capability Set 2 | +| Q.1222 | Service plane for Intelligent Network Capability Set 2 | +| Q.1223 | Global functional plane for Intelligent Network Capability Set 2 | +| Q.1224 | Distributed functional plane for Intelligent Network Capability Set 2 | +| Q.1225 | Physical plane for Intelligent Network Capability Set 2 | +| Q.1228 | Interface Recommendation for Intelligent Network Capability Set 2 | +| Q.1229 | Intelligent network users guide for capability set 2 | +| Q.1290 | Glossary of terms used in the definition of intelligent networks | + +## 5 Service aspects + +The services and service features that are to be supported by IN CS-2 are fundamental to the IN CS-2 Service-Independent Building Blocks (SIBs), call processing model and service control principles. Three types of services have been identified in IN CS-2: telecommunication service, service management service and service creation services. The last two types of services are first introduced in IN CS-2. + +Tables 2 and 3 list IN CS-2 benchmark services and service features, which, in addition to IN CS-1 related telecommunication services/service features, can be used to identify and verify the service-independent capabilities of IN CS-2. + +Appendix I provides short prose descriptions of the benchmark services and service features. It was used to develop the current Q.122x-Series of Recommendations and was intended for this purpose only. It is not to be used by service designers for service creation. + +**Table 2/Q.1221 – Target set of IN CS-2 telecommunication services** + +### **Benchmark telecommunication services** + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| Internetwork Freephone (IFPH) | Call Transfer (CT) | +| Internetwork Premium rate (IPRM) | Call Waiting (CW) | +| Internetwork Mass calling (IMAS) | Hot line (HOT) | +| Internetwork televoting (IVOT) | Multimedia (MMD) a) | +| Global Virtual Network Service (GVNS) | Terminating Key Code Screening (TKCS) a) | +| Completion of Call to Busy Subscriber (CCBS) a) | Message Store and Forward (MSF) | +| Conference calling (CONF) | International Telecommunication Charge Card (ITCC) a) | +| Call Hold (HOLD) | Mobility services (UPT) a) | +| NOTE 1 – The above service names apply to the descriptions of targeted services (see Appendix I), and not to the user-network interface descriptions provided by ITU-T Study Group 1. | | +| NOTE 2 – Network implementation aspects may be important for some services. | | +| a) These services may be partially supported in IN CS-2. For example, they may be supported at the GFP level but not supported at the protocol level. Some of these services may also require capabilities beyond IN CS-2. Please note that SIBs are used for modelling purpose. They are not meant to be used as a standardized solution for service creation, even though some organizations may wish to use them for this purpose. | | + +**Table 3/Q.1221 – Target set of IN CS-2 telecommunication service features** + +### **Benchmark telecommunication service features** + +| | | +|-------------------------------------------------------------|--------------------------------------------------------------------| +| User Authentication (UAUT) | InterNetwork Service Identification (INSI) | +| User Registration (UREG/outgoing call registration) | InterNetwork Rate Indicator, Forward (INRI-F) a) | +| Secure Answering (SANSW) | InterNetwork Rate Indicator, Backward (INRI-B) a) | +| Follow-On (FO) | Real Time Flexible Rating (RTFR) a) | +| Flexible (call) Origination Authorization (FOA) | Originating Carrier Identification (OCI) a) | +| Flexible (call) Termination Authorization (FTA) | Terminating carrier identification (OTC) a) | +| Provision of Stored Messages (PSM) | Resource Allocation (RAL) a) | +| Multiple Terminal Address Registration (MTAR) a) | Delivery of Complementary Information (DCI) a) | +| Intended Recipient Identity Presentation (IRIP) | Service Indication (SIND) | +| Blocking/Unblocking of Incoming Calls (BUIC) a) | Service Negotiation (SNEG) a) | +| Terminal Authentication (TAUT) a) | Call Forwarding (CF) | +| Handover (HOV) a) | B-ISDN Multiple Connections Point to Point (BI-MCPP) a) | +| Terminal Location Registration (TLR) a) | B-ISDN Multi-Casting (BI-MCAST) a) | + +**Table 3/Q.1221 – Target set of IN CS-2 telecommunication service features (concluded)** + +### **Benchmark telecommunication service features** + +| | | +|----------------------------------------------------------|-------------------------------------------------------------------------------------------| +| Terminal Attach/Detach (ATDT) a) | B-ISDN Conferencing (BI-CONF) a) | +| Terminal Paging (TPAG) a) | Call Connection Elapsed time Limitation (CCEL) a) | +| Radio Paging (RPAG) a) | Special Facility Selection (SFS) a) | +| Emergency Calls in Wireless (ECW) a) | Concurrent Features Activation with Bi-Control (CFA BC) a) | +| Terminal Equipment Validation (TEV) a) | Customized Call Routing with Public network (CCR-PU) | +| Cryptographic Information Management (CIM) a) | Customized Call Routing with Private network (CCR-PR) | +| Automatic Call Back (ACB) a) | Internetwork Service Profile Interrogation (ISPI) | +| Call Hold (HOLD) | Internetwork Service Profile Modification (ISPM) | +| Call Retrieve (CRET) | Internetwork Service Profile Transfer (ISPT) | +| Call Transfer (CT) | Reset of UPT registration for incoming calls (IRUR) a) | +| Call Toggle (CTOG) | Mobility Call Origination (MCO) (mobile call origination/UPT outcall) a) | +| Call Waiting (CW) | Mobility Incall Delivery (MID) (Mobile user call term./UPT incall delivery) a) | +| Meet-Me Conference (MMC) a) | Data Communication between different Protocol Terminals (DCPT) a) | +| Multi-Way Calling (MWC) a) | Charge Determination (CDET) a) | +| Call Pick-Up (CPU) a) | Charge Card Validation (CCV) a) | +| Calling Name Delivery (CND) | Call Disposition (CD) a) | +| Message Waiting Indication (MWI) a) | Enhanced Call Disposition (ECD) a) | +| Feature Use Charging (FUC) a) | User Service Interaction (USI) a) | +| Services On-Demand (SOD) a) | | + +a) These services may be partially supported in IN CS-2. For example, they may be supported at the GFP level but not supported at the protocol level. Some of these services may also require capabilities beyond IN CS-2. Please note that SIBs are used for modelling purpose. They are not meant to be used as a standardized solution for service creation, even though some organizations may wish to use them for this purposes + +### 5.1 Telecommunication services + +As in IN CS-1, IN CS-2 capabilities are intended to support *single-ended single-point-of-control* services and service features. Single-ended and single-point-of-control are to be described in 7.2.1 and 7.2.2. + +## 5.2 Service management services + +Service management services/service features are supported by IN CS-2. The following list (Table 4) represents service names but not user-network interface descriptions provided by ITU-T Study Group 1. + +**Table 4/Q.1221 – Target set of IN CS-2 service management services/service features** + +### **Benchmark service management services and service features** + +| | | +|------------------------------------------------------|----------------------------------------------------| +| Service customization services | Service monitoring services | +| Telecommunications Service Customization (TSC) | Subscriber Service Report (SSR) | +| Service Control Customization (SCC) | Billing Report (BR) | +| Service Monitoring Customization (SMC) | Subscriber Service Status Report (SSSR) | +| Service control services | Subscriber Traffic Monitoring (STM) | +| Subscriber Service Activation/Deactivation (SSAD) | Subscriber service Management Usage Report (SMPUR) | +| Subscriber Monitoring Activation/Deactivation (SMAD) | Other management services | +| Subscriber Profile Management (SPM) | Subscriber Service Testing (SST) | +| Subscriber Service Limiter (SSL) | SMP Usage Report (SUR) | +| Subscriber Service Invocation (SSI) | Subscriber Security Control (SSC) | + +## **5.3 Service creation services** + +Service creation services/service features are supported by IN CS-2. The following list (Table 5) represents service names but not user-network interface descriptions provided by ITU-T Study Group 1. + +**Table 5/Q.1221 – Target set of IN CS-2 services creation services/service features** + +### **Benchmark service creation services and service features** + +| | | +|------------------------------------------------|------------------------------------------------| +| Service specification services | Service deployment services | +| Feature interaction detection | SMP-created service data and SLP update | +| Cross-service feature interaction detection | Service distribution | +| Feature interaction rule/guidelines generation | SIB distribution | +| Service and SIB cataloguing | Data rule distribution | +| Created service resource utilization | Feature interaction rule distribution | +| Service development services | Multiple SMP support | +| Creation interface selection | Network tailoring | +| Creation initiation | Network element capability specification | +| Editing | Network element function/capability assignment | +| Combining | Service creation management services | +| Data population rule generation | SCE access control | +| SMP service creation | SCE usage scope | + +**Table 5/Q.1221 – Target set of IN CS-2 services creation services/service features (concluded)** + +### **Benchmark service creation services and service features** + +| | | +|-------------------------------------------|-----------------------------------------| +| Syntax and data checking | SCE recovery | +| Service and SIB archiving | SCE release management | +| Service configuration control | SCE capability expansion | +| SIB configuration control | SCE conversion | +| Network configuration tracking capability | Cross-SCE service maintenance | +| Service verification services | SCE-to-SCE system consistency | +| SCE testing | SCE service/modular/system transference | +| Created service simulation | Conversion of created services | +| Created service live testing | Service management interaction | + +## **5.4 Network support of IN CS-2 services** + +The services are to be supported over various networks. For IN CS-2 applications the following networks are considered: + +- i) PSTN; +- ii) ISDN (public and private networks); +- iii) PLMN. + +## **6 Network aspects** + +This clause provides an overview of the IN network functions and sets guidelines for the control architecture of IN CS-2. It also describes how the issues of feature interaction and service-feature consistency are handled in IN CS-2. + +Figure 1 summarizes the IN network functions and their functional relationships. + +![Diagram of IN functions and functional relationships. The diagram shows a central SCF (Service control function) connected to various other functions. SMF (Service management function) is at the top, connected to SMAF (Service management access function), SCEF (Service creation environment function), SDF (Service data function), and SCF. SRF (Specialized resource function) is connected to SMF and SCF. SCUAF (Service control user agent function) is connected to SCF and CUSF (Call-unrelated service function). CUSF is connected to SCF and SSF (Service switching function). SSF is connected to SCF and CCF (Call control function). CCF is connected to SCF, SSF, and CCAF (Call control agent function). CCAF is connected to CCF and another CCAF. The text 'All other network functions except CCAF' is near the SMF node. The code 'T1184890-97' is at the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Diagram of IN functions and functional relationships. The diagram shows a central SCF (Service control function) connected to various other functions. SMF (Service management function) is at the top, connected to SMAF (Service management access function), SCEF (Service creation environment function), SDF (Service data function), and SCF. SRF (Specialized resource function) is connected to SMF and SCF. SCUAF (Service control user agent function) is connected to SCF and CUSF (Call-unrelated service function). CUSF is connected to SCF and SSF (Service switching function). SSF is connected to SCF and CCF (Call control function). CCF is connected to SCF, SSF, and CCAF (Call control agent function). CCAF is connected to CCF and another CCAF. The text 'All other network functions except CCAF' is near the SMF node. The code 'T1184890-97' is at the bottom right. + +| | | | | +|------|---------------------------------------|-------|-------------------------------------| +| CCAF | Call control agent function | SMF | Service management function | +| CCF | Call control function | SRF | Specialized resource function | +| SCEF | Service creation environment function | SSF | Service switching function | +| SCF | Service control function | CUSF | Call-unrelated service function | +| SDF | Service data function | SCUAF | Service control user agent function | +| SMAF | Service management access function | | | + +**Figure 1/Q.1221 – IN functions and functional relationships** + +### 6.1 Network functions + +#### Call control and call unrelated control related functions + +SSF – Service switching function: This function interfaces with CCF and SCF. It allows the CCF to be directed by the SCF. + +SRF – Specialized resources function: This function provides a category of resources for access by other network entities. Examples of resources include DTMF sending and receiving, protocol conversion, speech recognition, and synthesized speech provision. + +CCF – Call control function: This function refers to call and connection handling in the classical sense (e.g. that of an exchange). + +CCAF – Call control agent function: This function provides the user access to the network. + +CUSF – Call unrelated service function: This function handles call unrelated activities. + +SCUAF – Service control user agent function: This function provides the user access to the network call unrelated service function. + +#### Service control related functions + +SCF – Service control function: This function contains the IN service logic and handles service related processing activity. + +SDF – Service data function: This function handles access to service-related data and network data and provides consistency checks on data. It hides from the SCF the real data implementation and provides a logical data view to SCF. + +#### Management related functions + +SCEF – Service creation environment function: This function allows an intelligent network service to be defined, developed, tested and input to the SMF. The output of this function involves service logic and service data templates. + +SMAF – Service management access function: This function provides an interface (e.g. screen presentation) for service subscribers and service administrators who have access to the SMF. + +SMF – Service management function: This function involves service operation control, service provision control, service deployment control, service monitoring and billing. + +### **6.2 Control architecture principles** + +As stated in clause 5 (Service aspects), the service scope of IN CS-2 shall be restricted to single-ended single-point-of-control services. This subclause identifies principles for the control architecture of IN CS-2, in the context of this service scope. + +This subclause is organized around three control aspects: + +- service invocation and control; +- end-user interaction with and without the SRF; and +- service management. + +#### **6.2.1 Service invocation and control** + +This control aspect involves the CCF, SSF and SCF. + +As in IN CS-1, the following points capture key principles for IN CS-2: + +- 1) The CCF retains ultimate responsibility for integrity and control of the local connection at all times. +- 2) The SSF-to-SCF relationship is, by definition, service-independent. Therefore, the CCF and SSF should never contain service logic specific to IN CS-2 supported services. +- 3) In the event of SCF malfunction, or time-out in the SCF to SSF response, the SSF/CCF combination should be capable of reverting to a default call completion sequence, with appropriate announcement(s) to the calling and/or called party. +- 4) The SSF should never have to interact with more than one SCF at any given time in order to complete a sequence of query/response interactions on behalf of a calling or called party. +- 5) Call hand-offs (transfer of responsibility) between SCFs, and between SSFs are permitted in IN CS-2. Nevertheless, the hand-off must be explicit, and must not violate principle 4). + +#### **6.2.2 End-user interactions** + +As part of the process of formulating a response to the SSF, the SCF may need to enter into a dialogue with the calling or called party. This would take the form of a prompt and collection sequence with the aid of an SRF, or the form of call unrelated/out-channel call related interactions, which are new in IN CS-2 (see 7.2.6 and 7.2.7 for more details). + +As in IN CS-1, when the SRF is being used, the SCF in IN CS-2 does not have to enter into this dialogue directly. Instead, it instructs the SRF to carry out a prompt and collection sequence with the calling or called party on its behalf. In general, the actual implementation of IN services will govern the kind of transport systems and protocols (e.g. DTMF, D-channel user-to-user signalling, and data services) used to collect information from the user. + +Again, the following key principles apply, when the SRF is being used in IN CS-2: + +- 1) The SCF has full IN-supported service control of instruction formulation and sequencing with respect to the SRF and SSF. +- 2) As a corollary to principle 1), there shall be no direct service control interaction between the SSF and SRF for IN CS-2-based services. The SSF and SRF have a peer-peer relationship for the control of IN CS-2-based services, and both are subsidiary to the SCF. + +- 3) The SCF will require the capability of suspending processing of an IN CS-2-based service on behalf of a calling or called party, and then resuming on behalf of the same party at a later time. + +#### **6.2.3 Service management** + +The control aspects covered in 6.2.1 and 6.2.2 address the real-time interactions between IN CS-2 functions on behalf of a particular calling or called party. In contrast, the service management aspect primarily addresses the network operator's interaction with the SSF, SCF, SDF, and SRF. This interaction normally takes place outside the context of a particular call or service invocation. Nonetheless, IN CS-2 must neither preclude nor constrain the capability of service customers to interact directly with customer-specific service management information (e.g. a personal service profile). + +The following points capture key principles for IN CS-2: + +- 1) The SMF may be used to add, change or delete IN CS-2-based service-related information or resources in the SSF/CCF, CUSF, SCF, SDF, and SRF. Such changes should not interfere with IN CS-2-based service invocations or calls that are already in progress. +- 2) The SMAF may be used to add, change, or delete appropriate customer-specific information. The mechanism and safeguards that are put into place by the network operator for this interaction may take advantage of IN CS-2 functions and capabilities. +- 3) The SCEF may be used by service providers to introduce new services. The task of deploying the service is the role of the SMF and is initiated from within the SMF. + +### **6.3 Feature interactions** + +As in IN CS-1, the constraints placed on the IN CS-2 architecture have been put in place primarily to minimize and control feature interactions within single domains of responsibility. See 7.2.8 for more details. + +The single-endedness of IN CS-2-based services means that all aspects of a call are under the control of one CCF/SSF and one SCF at any point in time [principle 4) in 6.2.1]. The SCF and SSF are therefore responsible for the handling of interactions between IN CS-2-based SSF/CCF capabilities, and non-IN features already provided in the basic network. + +### **6.4 Consistency among IN CS-2 supported service features** + +The ultimate responsibility for consistency of operations within a set of IN CS-2-based service features lies with the network operator. Nonetheless, the software and data structures of the SCF and SDF, operation and control of these software and database structures via the SMF, and the tools provided by the SCEF, may be designed to aid the network operator in fulfilling this responsibility. + +## **7 Functional relationships and interfaces** + +### **7.1 Functional relationships and control classes** + +Five groups of control capabilities, called control classes, have been identified to support the functional relationships: + +- 1) Bearer connection control: the class of capabilities to establish, and clear the bearer connections (e.g. voice paths through the network), and provide surveillance. + +- 2) Non-IN call control: the class of capabilities to invoke the user and provide the end-to-end control required for the non-IN delivery of supplementary services. The non-IN delivery does not involve the structured separation of the CCF, SSF, and SCF. +- 3) IN service-control: the class of capabilities that involve the structured separation of the SSF from SCF. +- 4) Service management control: the class of capabilities that involve service deployment, service provisioning, service operation control, and service monitoring. +- 5) Non-IN call unrelated control: the class of capabilities to establish, provide monitoring, and clear a non-bearer connection (e.g. out-channel interaction via the DSS 1 D-channel without a bearer connection). + +Figure 2 depicts the classes of control capabilities required for the functional relationships. The following subsections further describe the control relationships for each control class, respectively. A control relationship is the relationship between a functional relationship and a control class. + +![Diagram showing functional relationships and control classes for IN CS-2. It includes nodes for SMF, SRF, SCUAF, CCAF, CUSF, CCF, SSF, SCF, SDF, SMAF, and SCEF. A legend defines five types of control relationships: Bearer connection control relationship (dotted line), Non-IN call control (dash-dot line), Non-IN call unrelated control (double line), IN service control relationship to be standardized for CS-2 (dashed line), and Service management control relationship (long dash-dot-dot line).](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +The diagram illustrates the functional relationships and control classes for IN CS-2. It features several network function nodes represented by ovals: SMF (Service Management Function), SRF (Service Resource Function), SCUAF (Service Control User Agent Function), CCAF (Call Control User Agent Function), CUSF (Call User Service Function), CCF (Call Control Function), SSF (Service Switching Function), SCF (Service Control Function), SDF (Service Data Function), SMAF (Service Management Agent Function), and SCEF (Service Control Element Function). The nodes are arranged in a hierarchical manner, with SMF at the top, connected to various other nodes. A legend at the bottom left defines the line styles used for different control relationships: + + +- Bearer connection control relationship:** Represented by a dotted line. +- Non-IN call control:** Represented by a dash-dot line. +- Non-IN call unrelated control:** Represented by a double line. +- IN service control relationship to be standardized for CS-2:** Represented by a dashed line. +- Service management control relationship:** Represented by a long dash-dot-dot line. + + Functional relationships are shown as solid lines between nodes. For example, SMF is connected to SRF, SCUAF, CCAF, CUSF, CCF, SSF, and SCF. SCF is connected to SDF, SSF, and CCF. CCF is connected to CCAF and another CCF node. The diagram also includes a note "All other network functions except CCAF" pointing to the SMF node and a reference code "T1184900-97" in the bottom right corner. + +Diagram showing functional relationships and control classes for IN CS-2. It includes nodes for SMF, SRF, SCUAF, CCAF, CUSF, CCF, SSF, SCF, SDF, SMAF, and SCEF. A legend defines five types of control relationships: Bearer connection control relationship (dotted line), Non-IN call control (dash-dot line), Non-IN call unrelated control (double line), IN service control relationship to be standardized for CS-2 (dashed line), and Service management control relationship (long dash-dot-dot line). + +**Figure 2/Q.1221 – Functional relationships and control classes for IN CS-2** + +#### 7.1.1 Bearer connection control + +Control relationships exist between the bearer connection control class and the CCAF-CCF, CCF-CCF, and CCF-SRF functional relationships, respectively. Standard interfaces are employed to realize these control relationships and are listed below by the involved functional relationships: + +- CCAF-CCF: DSS 1/Q.931 +- CCF-CCF: SS7/ISUP +- CCF-SRF: DSS 1/Q.931; SS7/ISUP + +#### 7.1.2 Non-IN call control + +Control relationships exist between the non-IN call control class and the CCAF-CCF, CCF-CCF, and CCF-SRF functional relationships, respectively. Standard interfaces are employed to realize these control relationships and are listed below by the involved functional relationships: + +- CCAF-CCF: DSS 1/Q.931 +- CCF-CCF: SS7/ISUP +- CCF-SRF: DSS 1/Q.931; SS7/ISUP + +#### 7.1.3 IN service control + +Control relationships exist between the IN service control class and the SCF-CUSF, SCF-SCF, SCF-SDF, SCF-SRF, SCF-SSF, and SDF-SDF functional relationships, respectively. They can be realized through SS7/TCAP/INAP. + +IN CS-2 can support mid-call and topology manipulation capabilities, as noted in other Q.122x-Series of Recommendations. In addition, IN CS-2 may support services or service features which require ISUP or/and DSS 1 modifications. + +#### 7.1.4 Service management control + +Control relationships exist between the service management control class and the SMF-CUSF, SMF-SCF, SMF-SCEF, SMF-SDF, SMF-SMAF, SMF-SRF, and SMF-SSF functional relationships, respectively. They can be realized through CMIP/Q.812. No modification to INAP (i.e. Q.1228) is foreseen for management aspects. In addition, no modification to the IN physical plane (i.e. Q.1225) is foreseen; namely, no additional Physical Entities (PEs) are required assuming basic PEs exist for management aspects. + +#### 7.1.5 Non-IN call unrelated control + +There is a control relationships between the non-IN call unrelated control class and the SCUAf-CUSF functional relationship. Standard interfaces listed below are employed to realize this control relationship: + +- SCUAf-CUSF: DSS 1/Q.932; SS7/ISUP + +### 7.2 Key functions and interfaces + +#### 7.2.1 Single point multiple points of control + +Single point of control describes a control relationship where the same aspects of a call are influenced by one and only one service control function at any point in time. Multiple points of control is the ability for multiple service logic instances to interact with a single call segment. The SSF/CCF may have to be able to manage interactions between IN service logic instances realized in different service logic instances that are simultaneously active on a single call. New capabilities beyond the single point of control capability are required to enable the SCF to control two call segments in different SSF/CCFs simultaneously. + +*Interfaces:* SCF-SSF/CCF, SCF-SCF + +#### 7.2.2 Single-ended/multi-ended calls + +A single-ended service feature applies to one and only one party in a call and is orthogonal (independent) at both the service and topology levels to any other parties participating in the call. Orthogonality allows another instance of the same or a different single-ended service feature to apply to another party in the same call as long as the service feature instances do not have feature interaction problems with each other. + +Multi-ended is the ability for a service logic instance to interact with multiple call segments. The service logic instance may have to be able to manage IN call/connection processing among multiple call segments on a single call. + +*Interfaces:* SCF-SSF/CCF, SSF-SSF, SCF-SCF + +#### **7.2.3 Mid-call interruption** + +Mid-call interruption supports SCF-SSF interaction during the alerting or active phase of a call (i.e. during ringing for the originating party or after the call reaching a stable state). + +*Interfaces:* SCF-SSF/CCF. + +#### **7.2.4 Call party handling** + +Call party handling is the ability to manage various parties' participation in a call. Parties' bearer channels may be added, deleted, joined and/or separated from the other parties involved in the call. + +*Interfaces:* SCF-SSF/CCF. + +#### **7.2.5 Enhanced SRF** + +Enhanced SRF capabilities are identified in 4.3.4/Q.1214 and 3.3.6/Q.1224. Examples include audio conference bridge, information distribution bridge, text-to-speech synthesis, protocol converters, automatic voice recognition and voice message sender/receiver. Capabilities such as voice message sender/receiver, text to speech synthesis, and automatic voice recognition can be supported using elementary operations (as in IN CS-1) or user interaction scripts (as in IN CS-2). The latter is based on the concept of task sharing between SCF and SRF; the SCF is responsible for the global service logic while the SRF is responsible for the user interaction logic. Other capabilities such as audioconference bridge and information distribution bridge are supported by using the hybrid approach for call party handling that an SRF as well as an SSF is involved in providing the services. + +*Interfaces:* SRF-SCF, SSF-SCF. + +#### **7.2.6 Call unrelated user interaction** + +Call unrelated user interaction between the user and service processing is the ability to communicate information outside the context of a call, required for services/service features such as message waiting indication. As this capability is not supported by the BCSM, which is call related, the basic call unrelated state model (BCUSM) is introduced in IN CS-2. + +*Interfaces:* SCF-CUSF, CUSF-SCUAF. + +#### **7.2.7 Out-channel call related user interaction** + +Out-channel call related user interaction provides the ability to communicate information within the context of a call on the out-channel signalling access (within the same call reference of a call) to support features such as user authentication. + +*Interfaces:* SCF-SSF/CCF, SCF-SRF. + +#### **7.2.8 Service/feature interaction (service processing)** + +Service interaction during service processing focuses on the service interaction in the phase of service executions. It relates to the call control. To help characterize service interactions between non-IN supported services/features and IN supported services/features, it may be useful to map non-IN supported services/features to the IN-Switching State Model (IN-SSM). Non-IN supported services/features may be fully mapped, partially mapped, or unmapped. Placement of a non-IN supported service or service feature into one of these groups serves to characterize the information available to the Feature Interaction Manager/Call Manager (FIM/CM) during the operation of the feature. In characterizing service interactions for fully mapped non-IN-based services and service features, higher priority should be given to fully mapped non-IN-based services than to partially or unmapped non-IN-based services. + +*Interfaces:* SCF-SCF, SCF-SDF, SCF-SRF, SCF-SSF/CCF + +#### 7.2.9 Internetworking + +Internetworking is the process in which several networks (potentially of different types, such as IN-structured, non-IN-structured, public and private) cooperate to provide a service. The need for internetworking capabilities results from the fact that customers may want to access services which span multiple networks. A typical situation is when the data needed by a service (e.g. UPT, VPN and global network services) reside in a network that is different from the one in which the call has originated. + +To meet the IN CS-2 internetworking need, extension of the IN models and architecture to a multi-network context as well as extension of existing functionalities defined in IN CS-1 to support interfaces between functional elements physically located in different network contexts has been provided by IN CS-2. + +IN CS-2 identifies the SCF-SCF, SCF-SDF, SCF-IAF, SDF-SDF and SMF-SMF relationships for internetworking purposes. Distributed service logic, but not distributed service control, is supported. Additionally, internetwork management interactions and distributed data handling processes are supported. + +##### 7.2.9.1 Internetworking between IN-structured networks + +General requirements for internetworking capabilities are presented in 2.2.6/Q.1201. + +Although the involved networks may have different access types (e.g. PSTN and ISDN), as well as different levels of IN structure, IN CS-2 internetworking services are to be provided to customers in a consistent way, regardless of such differences. + +Similar to Figure 1, which depicts the functional relationships between the IN functions within one network, Figure 3 depicts possible functional relationships between the IN functions that are located in two different networks. + +The following observations can be made concerning the applicability of Figure 3 to IN CS-2: + +![Diagram showing possible IN network interworking functional relationships between Network A and Network B. A vertical dashed line separates the two networks. In Network A, four functional elements are shown in a vertical stack: SMF, SDF, SCF, and SSF. In Network B, the same four functional elements are shown in a vertical stack. Connections are as follows: SMF in Network A connects to SMF in Network B; SDF in Network A connects to both SDF and SCF in Network B; SCF in Network A connects to both SDF and SCF in Network B; SSF in Network A connects to SCF and SSF in Network B. No connection is shown between SSF in Network A and SDF in Network B, nor between SCF in Network A and SSF in Network B. A label 'T1184910-97' is present below the SSF in Network B.](552ca016af3d6240648ab5a2cad97f60_img.jpg) + +``` +graph LR + subgraph Network_A [Network A] + SMF_A((SMF)) + SDF_A((SDF)) + SCF_A((SCF)) + SSF_A((SSF)) + end + subgraph Network_B [Network B] + SMF_B((SMF)) + SDF_B((SDF)) + SCF_B((SCF)) + SSF_B((SSF)) + end + SMF_A --- SMF_B + SDF_A --- SDF_B + SDF_A --- SCF_B + SCF_A --- SDF_B + SCF_A --- SCF_B + SSF_A --- SCF_B + SSF_A --- SSF_B +``` + +Diagram showing possible IN network interworking functional relationships between Network A and Network B. A vertical dashed line separates the two networks. In Network A, four functional elements are shown in a vertical stack: SMF, SDF, SCF, and SSF. In Network B, the same four functional elements are shown in a vertical stack. Connections are as follows: SMF in Network A connects to SMF in Network B; SDF in Network A connects to both SDF and SCF in Network B; SCF in Network A connects to both SDF and SCF in Network B; SSF in Network A connects to SCF and SSF in Network B. No connection is shown between SSF in Network A and SDF in Network B, nor between SCF in Network A and SSF in Network B. A label 'T1184910-97' is present below the SSF in Network B. + +**Figure 3/Q.1221 – Possible IN network interworking functional relationships** + +- 1) The SSF-SCF functional relationship across two networks is out of the scope of IN CS-2. As for IN CS-1, and as described in 2.2.6/Q.1201, which underlines the necessity to maintain the network security and network integrity, internetworking between the SSF in one network and the SCF in another one is not an IN CS-2 requirement. + +- 2) IN CS-2 will support the SCF-SCF functional relationship across two networks when only one SCF directly interacts with the call. This restriction is necessary because IN CS-2 has no requirement for multiple point of control capability, where two SCFs are able to interact with the call at the same time. This internetworking relationship is new for IN CS-2 as it was not supported by IN CS-1. +- 3) As in IN CS-1, the SCF-SDF functional relationship across two networks is within the scope of IN CS-2. +- 4) The SDF-SDF functional relationship across two networks is within the scope of IN CS-2. This internetworking relationship is new for IN CS-2 as it was not supported by IN CS-1. +- 5) The SMF-SMF functional relationship across two networks is within the scope of IN CS-2. The assumed protocol should align with TMN generic protocols and the TMN X interface. This internetworking relationship is new for IN CS-2 as it was not supported by IN CS-1. +- 6) In IN CS-2, specific internetworking capabilities are assumed to be localized within the FEs which support an internetworking relationship, i.e. within the SCF, SDF and the SMF. +- 7) The internal architecture of one network is not visible from another network. However, functions needed for processing internetworking are to be visible from the other network (IN or non-IN). + +##### 7.2.9.2 Internetworking with non-IN-structured networks + +The previous subclause defines the internetworking relationships for two networks, both of which have a structure compatible with the IN functional architecture. For IN CS-2, the Intelligent Access Function (IAF) provides access between the SCF of an IN-structured network and an entity of a non IN-structured network. This latter entity may be other networks or customers (e.g. private networks, simple databases used in the customer call routing service, terminals, and PABXs). It: + +- a) provides access to and from the SCF of the IN-structured network; and +- b) maps the information between the internal and external representation. + +As such, for the subscriber's each incoming call, information (such as dialled number, calling number, and caller entered digits) may be conveyed, for example, from a public network to a private one for the latter to determine how that call will be handled. A private network is defined as a network which provides services only to a specific set of users. + +Similar to Figure 3, which depicts possible functional relationships between the IN functions that are located in two different IN-structured networks, Figure 4 depicts a possible functional relationship between the SCF located in an IN-structured network and the IAF located in a non-IN-structured network. + +![Diagram showing the functional relationship between an SCF in Network A (IN-structured network) and an IAF in Network B (non-IN-structured network).](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +The diagram illustrates a functional relationship between two networks, Network A and Network B, separated by a vertical dashed line. Network A is labeled 'IN-structured network' and contains an oval labeled 'SCF'. Network B is labeled 'non-IN-structured network' and contains an oval labeled 'IAF'. A solid horizontal line connects the 'SCF' oval in Network A to the 'IAF' oval in Network B, crossing the dashed boundary line. Below the 'IAF' oval, the text 'T1184920-97' is present. + +Diagram showing the functional relationship between an SCF in Network A (IN-structured network) and an IAF in Network B (non-IN-structured network). + +**Figure 4/Q.1221 – IN to non-IN network interworking functional relationship** + +#### 7.2.10 Security + +Security is a general property which relates to safe and reliable operation. The high-level requirements of a secure system are: + +- Confidentiality, which is defined in Recommendation X.800 as *the avoidance of the disclosure of information without the permission of its owner*. Thus, confidentiality may be considered as a property which ensures that conversations or interactions remain private; +- Integrity, which is defined in Recommendation X.800 as *the property that data has not been altered or destroyed in an unauthorized manner*. Integrity may then be considered as a property which ensures that operations occur as they are expected to; +- Availability, which may be considered as a property relating to the readiness of resources for authorized use; +- Accountability, which may be considered as a property which ensures that any operational request can be correctly attributed in case of doubt or dispute. + +The components of an IN system must be assembled and operated in such a way as to provide a defined level of security. + +To assist in this, any interface within the IN functional architecture may have the need to apply security assisting functions to the information flows passing across the interface such as: + +- Network access security functions: This includes user/terminal authentication (i.e. the result of a process by which a service user proves his or her identity to an IN system), user profile verification (i.e. the verification that a user is authorized to use a functionality); +- Internetworking security functions: This includes peer entity authentication (i.e. a process which allows a communicating entity to prove its identity to another entity in the network), signalling data or TMN data integrity, non-repudiation, confidentiality, entity profile verification (i.e. the verification that an entity is authorized to use a functionality). + +Recommendation Q.1228 defines a generic set of security mechanisms and procedures to offer some of the generic properties described above. In any particular circumstance, a set of network elements will be required to be configured according to some security scheme. + +The definition of IN CS-2 offers the provision of certain security assisting functions at the SCF-SDF, SDF-SDF, and SCF-SCF interfaces. Additional security functions may be required depending on the security schemes in place. + +*Interfaces:* SCF-SCF, SCF-SDF, SDF-SDF + +#### 7.2.11 IN-TMN + +Applying TMN concepts, TMN functional architecture modeling aspects to the IN are identified in Recommendation Q.1224 and its associated annexes. Harmonization of IN/TMN using TMN concepts to define service management and network management is specified in 7.2.12. + +*Interfaces:* See 7.2.12. + +#### 7.2.12 Service management + +IN specific service management refers to the network capabilities that are necessary from a network operator's point of view, to support the proper operation of services. This includes management during deployment, provisioning and utilization phases. TMN functionality can be used to provide these capabilities. Service interaction during service management focuses on service interaction in the phase of service subscription, service registration and service activation. + +The Service Management Function (SMF) is defined in 2.4/Q.1204. The actors who have access to the SMAF and thereby the SMF are service subscribers and service administrators. Service subscribers are users of the IN-supported services. (When subscribing for a particular IN-supported service, the service subscribers may choose some service features offered by the service provider + +according to their needs.) Service administrators consist of both the service provider and network provider; they are responsible for the following areas of service support: + +- 1) Service provisioning: introduction and allocation of the service logic with the ability to modify that service logic. Provisioning may also include changing certain service-related parameters prior to and during testing and distributing the related logic and data to other IN functional entities; +- 2) Service monitoring: monitoring service performance, receive trouble reports from service subscribers, and using the SMF to identify and correct the problem; +- 3) Security management: secure access to the functions of the SMAF. + +The above activities so far have been performed only by service administrators; however, service subscribers need and demand more control over the specifics of the services. The capabilities of the service subscribers to control the subscribed services are named "customer control service capability". Specific controlling capabilities can be granted depending on specific services (e.g. the freephone-related capabilities may differ from the VPN-related capabilities). + +In general, this set of capabilities would allow service subscribers to: + +- 1) view and adjust the service parameters they subscribe to; and +- 2) request and receive reports. + +Two technical approaches are supported in IN for the provision of the customer control service capability: + +- 1) Access through the SMAF to the SDF: This would be done via dedicated terminals. +- 2) Access through the network via the CCAF: This approach is supported at service processing level, and the SDF is involved. + +The second solution is constrained technically by the network-to-user interface and by the data available in the SDF. Full customer control service capability is only possible with the first solution. + +The solution choice is specific to each service. For instance, simple customer control service capability, such as location registration in UPT from any terminal, would be based on the second solution. A more complex customer control service capability, such as VPN management would be based on the first solution. + +The management-related functional relationships (i.e. SMF-SCF, SMF-SDF, SMF-SSF/CCF, SMF-SRF, and SMF-CUSF) are defined in IN CS-2 down to the distributed functional plane, with a high-level description of functions, functional model, functional relationships and interfaces (and guidance on the information model). The technical assumption is the alignment of IN and TMN. The assumed protocols to be used are the TMN generic protocols (e.g. common management information protocol, CMIP, as defined in Recommendation Q.812). No modification to INAP (Recommendation Q.1228) are foreseen for management aspects. + +Within IN CS-2, the management relationships to be studied are: SMF-SCEF, SMF-SMAF, SMF-SSF/CCF, SMF-SCF, SMF-SDF, and SMF-SRF. The last four relationships describe the management of IN network elements. + +The IN-specific management requirements concerning the service life cycle phases of creation, deployment, provisioning and utilization of IN-supported services are considered from a service plane point of view. Listed below are the requirements at the service and network level. + +The service level requirements are: + +- Install and configure the service script/software. + +- Install and configure service management scripts/software (e.g. scripts for the introduction and allocation of subscriber specific data). +- Install and configure the service testing (for the provisioning of tests on line). +- Install and configure the service generic data. +- Install and configure the specialized resource data. +- Set the target time and date the service should be enabled (service is pending). +- Receive reports on installation and configuration. +- Receive information on service availability (to inform customer of problems). +- Workstation program configuration. +- Enable/disable (parts of) the service on a global (network-wide) level. +- Monitor and control the service performance. +- Monitor, control (e.g. setting conditions on alarm reporting) and correct the service faults. +- Update service generic data. +- Update specialized resource data. +- Tariffs initialization and modification. +- Remove service management scripts/software. +- Remove the service script/software. +- Remove the service testing. +- Remove the service generic data. +- Remove the specialized resource data. +- Receive reports on the removing actions. +- Set the target time and date the service should be disabled. +- Install customer data in the network. +- Handle complaints on service malfunctioning. +- Handle customer control requests (e.g. update customized announcements and change parameter settings). +- Remove customer data from the network. +- Obtain information on the usage of the service per service subscriber for billing (e.g. via usage records). + +The network level requirements are: + +- Test the installed software. +- Install and configure trigger data. +- Install and configure signalling routing data. +- Install and configure network elements. +- Configure the workstation program. +- Monitor and control the performance/QOS of the network element. +- Enable/disable the use of the resources of the network element involved in the "service execution". +- Reallocate specialized resources (e.g. following QOS criteria). +- Monitor, control and correct the network element. + +- Test the network element. +- Update signalling routing data. +- Update trigger data. +- Update list of accountable events. +- Generate, collect and store usage information (e.g. for accounting purposes). +- Remove the installed software. +- Remove trigger data. +- Remove signalling routing data. +- Remove network elements. +- Handle complaints on network malfunctioning. + +*Interfaces:* SMF to SMAF, SCEF, SCF, SDF, SRF, CUSF, and SSF/CCF + +#### 7.2.13 Service creation + +IN service creation presents the operator's point of view for the creation of new services. These include service specification, service development, and service verification. Output is expected to be service logic for the execution aspects of a service, service logic for the management aspects of a service, and user data related logic and service data related logic. This includes partitioning of functionality between the SMF and SCEF. + +The SCEF allows services provided in Intelligent Network to be defined, developed, tested and input to SMF. Output of this function would include service logic, service management logic, service data template and service trigger information. Based on this definition, it is possible to distinguish the following three phases of service creation activity (defined in 2.2.2/1201): + +- service specification; +- service development; +- service verification. + +The service specification phase involves the following: + +- requirements specification based on customer/market input; +- analysis; +- feature interaction rules; +- OAM requirements; +- high-level design including evolution aspects. + +The service development phase involves the following: + +- detailed design: + - feature design; + - data schema; + - test case generation; + - engineering considerations; +- service logic and service management logic definition; +- development of service logic modules. + +Note that the feature design may impact platform development but it should not be considered as part of the service creation services because the impact on the platform depends on the intrinsic + +capabilities of the platform and it is vendor dependent. The output of the service development phase feeds into service verification phase. + +The service verification phase involves the following: + +- service logic syntactic checking; +- service logic and service management logic simulation; +- service logic module verification; +- network simulation; +- testing for service order requirement; +- engineering verification. + +Service interaction focuses on service interaction in all phases of service creation. The output of this phase verifies that customer/market requirements are met. + +Similarly, the SMF functionality can be subdivided into following phases: + +- service deployment; +- service provisioning; +- monitoring and maintenance; +- service negotiation. + +The service deployment phase involves the following: + +- service configuration on each Functionality Entity (FE), i.e. SCF, SSF, SDF, and SRF; +- configuration verification; +- subscription template and customization; +- database initialization; +- resource allocation on each FE; +- distribution of service support data and logic on each FE; +- service activation and deactivation via trigger detection point data distribution. + +Service interaction (from a service creation perspective) focuses on service interaction in the service deployment phase. + +The service distribution activity involves transferring appropriate information about the service to other FEs, e.g. SCF, SDF, SSF, SRF. + +The service provisioning phase involves the following activities: + +- customer subscription data-fill based on service order template and service customization; +- validation, taking into account customer account information via SMAF; +- subscription provisioning, i.e. informing the subscriber that his order has been executed. + +The service monitoring and maintenance phase involves the following activities: + +- audit; +- operations measurement/log collection: + - logic tracing; + - fraud detection; + - traffic management; + - usage report; + - performance analysis. + +The service negotiation phase of the SMF is needed to ensure that there are sufficient network resources available to support the customer's request for IN supported services. This would include at least the following verifications: + +- Ensure that the customer has access to the Service Switching Function (SSF). +- Ensure that the SSF/CCF supports the requested IN supported service. +- Ensure that all IN resources are available to support the requested IN supported service. +- Ensure that the requested IN supported service does not conflict with other existing IN supported services that the customer currently subscribes to. This requires an evaluation of potential feature interactions. +- Ensure that the customer has access to other switch-based services, such as ISDN, that may be required by the requested IN supported service. +- Ensure that the requested IN supported service does not conflict with existing switch-based services that the customer currently subscribes to. + +Service interaction during service creation focuses on the service interaction in the phase of service creation and service deployment. + +This provides a preliminary analysis of the SCEF and SMF functionalities. + +Once the functional partitioning between SMF and SCEF are established, then specific functions pertaining to what an SCEF is expected to provide can be addressed in greater detail. An SCEF is unlike other network elements in that it is a tool, not a service execution platform. The implementation of a service design tool, including the extent of the functions is offered its end-user, should be independent of network configurations, i.e. platforms. It is proposed that the services be identified to reflect what information is required between the SCEF and the service management element. With respect to standardization of service creation, it is the interface to other network elements that should be seen as the focal concern. In particular, the SCEF to SMF interface should be specified. + +*Interfaces: SMF to SCEF* + +![Diagram showing the partitioning of functionality between SMF and SCEF. SMF is on the left, containing Service deployment, Service provisioning, Monitoring and maintenance, and Service negotiation. SCEF is on the right, containing Service specification, Service development, and Service verification. A line connects the two ovals.](088921fa3f5a44c8551815122517eefd_img.jpg) + +The diagram illustrates the functional partitioning between the Service Management Function (SMF) and the Service Control Function (SCEF). It consists of two ovals connected by a horizontal line. The left oval is labeled 'SMF' and contains the following functions: 'Service deployment', 'Service provisioning', 'Monitoring and maintenance', and 'Service negotiation'. The right oval is labeled 'SCEF' and contains the following functions: 'Service specification', 'Service development', and 'Service verification'. A small text label 'T1184930-97' is located below the SCEF oval. + +Diagram showing the partitioning of functionality between SMF and SCEF. SMF is on the left, containing Service deployment, Service provisioning, Monitoring and maintenance, and Service negotiation. SCEF is on the right, containing Service specification, Service development, and Service verification. A line connects the two ovals. + +**Figure 5/Q.1221 – Partitioning of functionality between SMF and SCEF** + +#### 7.2.14 Personal mobility + +Personal mobility allows a user to associate with and/or configure any terminal, according to individual needs to access telecommunication services. It also enables the user to customize various aspects of the offered features, thereby receiving personal telecommunication service features. Universal Personal Telecommunications (UPT) is an example of a telecommunications service supporting personal mobility. + +IN CS-2 provides the network capabilities that are necessary to support personal mobility among heterogeneous access networks. In particular, IN CS-2 has extended the IN model and architecture to guarantee a correct handling of the user profile and service processing, independent of the user + +access. The IN CS-2 relationships that may be involved in providing personal mobility services include the SCF-SDF, SDF-SDF, SCF-SCF and SCF-SSF. + +# APPENDIX I + +## IN CS-2 benchmark services and features + +## I.1 General + +This Appendix provides short prose descriptions of the benchmark services and service features used to develop the current Q.122x-Series of Recommendations. These descriptions are not meant to be used by service designers for service creation. Note that some of the listed services and service features may be partially supported by IN CS-2 and not be supported at the protocol level. + +## I.2 Definitions + +The following definitions have to be taken into consideration: + +### I.2.1 Telecommunication services + +A telecommunication service is an information telecommunication service offered to subscribers by a service provider in areas where the (IN supported) service logic is executed to provide the service. A subscriber is a person or organization that is billed for use of a telecommunication service. A subscription is an instance of telecommunication service that is provided and billed to a particular subscriber. + +### I.2.2 Service management services + +A service management service offers customization, control and monitoring functions to the telecommunication services for which it is provided. This may be a commercial offering to subscribers. + +### I.2.3 Service creation services + +A service creation service offers specification, development, verification functions to the network operator. + +## I.3 Telecommunication services + +### I.3.1 General + +It should be recognized that the services proposed are not an extensive list but are taken from categories of services that are important for the next phase of IN standardization. Work to enable this proposed set of services and service features will also enable other services that would also use these capabilities. + +### I.3.2 Definitions + +More detailed definitions are to be found in Recommendation Q.1222. + +**I.3.2.1** A **telecommunication service** is characterized by one or more core service features, that can be optionally enhanced by other service features. + +**I.3.2.2** A **service feature** is a specific aspect of a telecommunication service that can also be used in conjunction with other telecommunication services/service features. A **core service feature** is a particular service feature fundamental to the telecommunication service, i.e. in the absence of this + +service feature, the name of the telecommunication service does not make sense as a commercial offering to the service subscriber. + +### **I.3.3 Mobility service features (UPT, FPLMTS)** + +These service features are aimed at, but not limited to, supporting UPT and FPLMTS. Other telecommunication services may utilize these service features. + +#### **I.3.3.1 Personal mobility features (UPT)** + +Personal mobility allows a user to appear at any network access point and initiate telecommunication services. Once recognized, the end user can access provisioned services and features according to a personal user profile, which can be customized by the subscriber or user. Please note that service features used in UPT but of more general nature (such as service indication, internetwork service profile interrogation, modification or transfer, reset of UPT registration for incoming calls) are described in 3.5. + +**I.3.3.1.1 User authentication (UAUT):** This feature confirms the identity of a user with the network and the identity of the network with a user. UAUT takes place during interactions between the network and a user. + +UAUT assumes that appropriate information is exchanged between the network and a user. A user has to provide his authentication data through the terminal or via an access device, which transmits the data to the network as well as establish a connection between the network and a user. + +UAUT implies the use of security algorithms to check the validity of the information provided by a user. + +Once the authentication has been performed, the visited network might keep the track of the authenticated user to avoid multiple use of UAUT. + +**I.3.3.1.2 User registration (UREG):** This feature enables a user to register on a terminal access for the purpose of receiving or placing calls. This may be accomplished either from the terminal where the user wishes to register or from another terminal (remote registration) There are two aspects to this feature, which are both included in the list of UPT Set 1 features described in the Recommendation F.851 "UPT – Service description". + +**I.3.3.1.2.1 in-call registration** is a means by which a user registers from the current terminal address for incoming calls to be presented to that terminal address. When registered, all the incoming calls to that user will be presented to the registered terminal for the duration specified by the user, or until a specific de-registration time. A new in-call registration made by the same user will cancel the previous in-call registration of that user. Several users may register for incoming calls to the same terminal address simultaneously. A user may also explicitly de-register for incoming calls. + +**I.3.3.1.2.2 Outgoing call registration (OGREG):** The out-call registration allows a user from the current terminal address to register for outgoing calls to be made from that terminal address. When registered, all outgoing calls (except some calls like emergency calls) from the terminal address will be charged to the user account for the duration specified by the user in terms of time or number of calls, or until a de-registration takes place. Normally the user will not have to carry out any further authentication procedures in order to make outgoing calls. However, optionally a simplified authentication procedure may be used. A user may be registered for outgoing calls at several terminal addresses simultaneously, but at any time only one user may be registered for outgoing calls at the same terminal address. The user may prevent another user from de-registering him for outgoing calls. The user may also explicitly de-register for outgoing calls. A third party *may* prevent a user from registering at his terminal address for outgoing calls. + +**I.3.3.1.3 Secure answering (SANSW):** Secure answering is a feature by which the service subscriber/user requires that incoming calls cannot be answered unless the answering party first successfully authenticates himself as the wanted subscriber. The use of this feature is strictly related to the privacy requirements from a service subscriber/user; although it has been considered only in the UPT description, it could be useful also for other services, e.g. freephone, VPN, and UMTS. (This feature is currently included in the list of UPT Set 1 optional features in Recommendation F.851 "UPT – Service description", with the name "called party specific secure answering of incoming UPT calls"). + +**I.3.3.1.4 Follow-on (FO):** This feature enables a user to make a series of service requests without going through the identification and authentication process before each service feature request. The identification and authentication are performed only for the first service request of the series. The user should be offered the choice after each service feature request to continue with a new service request. + +**I.3.3.1.5 Flexible (call) origination authorization (FOA):** The FOA feature can take effect immediately prior to the time that an IN capable switch would authorize call origination, during the call set-up process. A customized algorithm, provided by the network provider or the subscriber, can then determine whether or not the call should be originated. + +If the call is not authorized by the IN customized algorithm, then the call attempt is ended. If the call is authorized by the IN customized algorithm, then, depending on the feature subscriber profile, call processing can bypass switch-based authorization, or call processing can continue with switch-based authorization. + +The FOA feature can be used by personal and terminal mobility services to provide authorization capability where a switch has restrictions on call origination authorization. Such restrictions could be a consequence of a switched-based call screening feature, on behalf of the "home" subscriber of a given access line. There exists the possibility that a mobile user may roam to such an access line, at which time restrictions may have to be removed. + +**I.3.3.1.6 Flexible (call) termination authorization (FTA):** The FTA feature can take effect immediately prior to the time that an IN capable switch would authorize call termination, during the call set-up process. A customized algorithm, provided by the network provider or the subscriber, can then determine whether or not the call should be authorized. + +If the call is not authorized by the IN customized algorithm, then the call attempt is ended. If the call is authorized by the IN customized algorithm, then, depending on the feature subscriber profile, call processing can bypass switched-based authorization, or call processing can continue with switch-based authorization. + +The FTA feature can be used by personal and terminal mobility services to provide authorization capability where a switch has restrictions on call termination authorization. Such restrictions could be a consequence of a switched-based call screening feature, on behalf of the "home" subscriber of a given access line. There exists the possibility that a mobile user may roam to such an access line, at which time restrictions may have to be removed. + +**I.3.3.1.7 Provision of stored messages (PSM):** When the service subscriber registers the location, the network automatically informs the subscriber of the service and sends the voice messages which were stored before. + +**I.3.3.1.8 Multiple terminal address registration (MTAR):** This service feature enables a user to be registered for incoming calls on more than one terminal, with calls being offered to the terminals according to a certain algorithm (e.g. in sequence if there is no answer after a user-determined time (i.e. a user-configurable hunt group), and simultaneously). + +**I.3.3.1.9 Intended recipient identity presentation (IRIP):** This service feature allows identification at the receiving terminal of the intended recipient of an incoming call. It is required to enable Secure Answering (SANSW) to be offered when there is more than one UPT user registered for incoming calls on the one terminal. + +**I.3.3.1.10 Blocking/unblocking of incoming calls (BUIC):** This service feature enables any person, even if not a UPT user, to block and unblock calls incoming to UPT users currently registered on the third party's terminal. + +#### **I.3.3.2 Terminal mobility features (FPLMTS)** + +Terminal mobility provides a tetherless link between the user's terminal equipment and fixed network access points, thereby providing freedom of movement for the user during the use of telecommunication services and service features. The network is able to locate and identify a particular terminal as it appears within a network domain and while it is in motion, whether or not a call is currently taking place. Please note that service features used in FPLMTS but of more general nature (such as internetwork service profile interrogation, modification or transfer, mobile call origination or mobile user call termination) are described in 3.5. + +**I.3.3.2.1 Terminal authentication (TAUT):** The TAUT feature is initiated within the mobility processes of location management (i.e. terminal location registration), call origination, call delivery and at other times as initiated by the network or terminal. In support of security, the feature ensures the validity of the terminal and the network. Also, the feature enables the establishment of a private control and communications channel between the network and a terminal. Authentication process should occur when a terminal authenticates either in its home network or visited network. + +**I.3.3.2.2 Handover (HOV):** The handover (HOV) service feature enables a mobile terminal to change network access areas/points within a network or to an other network, while maintaining the call(s) and/or signalling relationship(s). Active services should be maintained, within the limits imposed by available radio and network resources. In the case of a lack of resources, active services could be modified (e.g. fall back to a lower grade of service quality) or interrupted. + +Handover is a complex operation involving four types of entities. They are: the monitoring entity type, the initiating entity type, the performing entity type and the controlling entity type. There could be more than one entity of the same type involved in the handover operation, even during the same handover. Handover can be initiated by the terminal, or network entities. + +The handover service feature consists of four processes: the handover monitoring process, the handover decision process, the handover execution process and the handover completion process. + +**Monitoring process:** This process collects radio measurements, aggregates these data (e.g. averaging) and forwards them to the initiating entity. These data are to be used as indicators of the quality of the radio link and of the radio environment (e.g. signal profile and path loss) and also for determining the target cell during the decision process. + +**Decision process:** The decision process comprises two sub-processes which can take place simultaneously. The first one determines when a handover must be triggered by comparing the data from the monitoring process with preset thresholds. The second one selects the target cell according to criteria defined for the handover. Otherwise stated, the decision process uses two sets of criteria: one for the triggering decision and the other for the selection of the target cell. + +**Execution process:** The execution process reserves and allocates the resources and creates the new link and routes the traffic and the signalling of the handed-over communication on this new link. This process could include a macro diversity phase during which two links (the old and the new one) are both in use. + +NOTE – The interrelationship between the resource reservation and the execution is not clear enough at this stage. Defining any precedence between the resource reservation and the execution operations in the network could impact on the handover processes at the radio interface. The way by which resource reservation at the radio interface and in the network are linked together for handover execution should be investigated. There is a need to consider the resource reservation process as an underlying process of the execution process. + +**Completion process:** This process frees up any unused resources. + +**I.3.3.2.3 Terminal location registration (TLR):** Terminal location registration is used when terminals notify the system of their location. This is a feature by which the location area information of a terminal is registered with the network. A location registration procedure is generally carried out (A) when the terminal changes the location area, or (B) when no previous location details are known (including updating of the location area information after network or terminal failure). + +The location area information is used by the network to handle incoming calls to the terminal. Terminal location registration uses the terminal authentication service feature to validate the terminal. Case (B) also covers the situation when a terminal first appears in a network. The terminal location registration may be accompanied by the internetwork service profile transfer feature. + +**I.3.3.2.4 Terminal attach/detach (ATDT):** The detach feature is used by the terminal to notify the network whether the terminal is temporarily not reachable. The network will modify the status information of the terminal. + +The attach feature is used by the terminal to notify the network whether the terminal is reachable again. The network will modify the status information of the terminal. + +**I.3.3.2.5 Terminal paging (TPAG):** This service feature enables the determination of the current location of a user or of a mobile terminal. It pages the terminal in the terminal location registration area based on the stored terminal location information, and determines the visited cell by the response from the terminal. + +When several cells exist in a terminal location registration area, the following paging procedures may be used: + +- 1) paging to all the cells in the terminal location registration area simultaneously; +- 2) paging to some of the cells in turn based on, e.g. priority and traffic statistics. + +Different location registration area for macro, micro and pico cells can be overlaid at some locations within the service area. TPAG can be invoked by the network other than the network in which the terminal resides. Paging is executed in the network which covers the location area registered by mobile terminals. It can be executed before incoming calls are routed to the network (i.e. other network can invoke the paging execution to get the routing information). + +**I.3.3.2.6 Radio paging (RPAG):** This service feature enables one-way personal selective calling with alert. The RPAG feature enables a user to send a message, either voice, tone, or alphanumeric, to a selected pager terminal or a group of terminals. This service feature also enables a user to request a receipt for such a message. + +The length of both the sending message and reply message will be limited. The sending messages will not be sent on a real-time basis. The waiting duration for a reply message will also be limited. A sending user will send a message to a service centre. The service centre will then send the message through radio channels. For a message without reply receipt requested, the service centre may send the message again at a pre-determined time spacing to ensure reception. For a message requesting reply receipt, the service centre /paging control node will wait for a pre-determined time interval for a reply message, and send it again if no reply message is received. It will repeat this process till a maximum number of tries is reached. The reply message may be generated automatically by the pager terminal. It may also be generated by the paged user within a limited short time interval + +(e.g. 30 seconds) after the message is received or the pager terminal will generate the reply message automatically. The service centre will store the reply message with a time-stamp for sender's retrieval. It should be clear that this service feature allows two-way message exchange, but not on a real-time basis, between a sender and a receiver. + +**I.3.3.2.7 Emergency calls in wireless (ECW):** The ECW service feature allows emergency calls to have priority over all other calls to ensure service. Emergency calls can be readily connected without dropping other active calls and without the requirement of successful terminal authentication, privacy or user authentication. Some services restrictions which may apply to the terminal may be suspended (e.g. time-of-day restrictions). Once active, the emergency call has priority over other active calls (e.g. during handover). The ECW service feature consists of three processes. + +**The emergency call origination process:** This process initiates a call with conventional terminal authentication, privacy, user authentication and user validation being performed. However, it does not depend on the success of these processes. The purpose of these processes is to obtain more available information about the user/terminal to facilitate assistance. This information and the location of the cell from which the call is originated should be available for forwarding to the emergency dispatcher, if required. The emergency call can not be denied if an RF channel can be found. The emergency call can be initiated by a user dialling the appropriate digits (e.g. 911) or by a terminal feature button. Either means of initiation can begin the process by placing a "normal" call or by invoking special signalling to the network. + +**The emergency call re-establishment – loss of RF contact process:** This process occurs when the Radio System Function (RSF) is no longer able to receive RF signals from the terminal during an emergency call. The RSF will attempt to re-establish contact with the terminal. If successful, the reconnection processes undertaken are equivalent to those which follow the handover process, namely, the handover execution process and handover completion process. + +**The emergency call termination – dispatcher hang up process:** This process occurs when the emergency operator goes on hook, which is the only means to normally end an emergency call. If the user returns the terminal to on hook condition, then the emergency call does not terminate; if necessary, the above process will be invoked. This emergency call should occur regardless whether a terminal is in its home network, or is in another network (i.e. local network). + +**I.3.3.2.8 Terminal equipment validation (TEVA):** The TEVA feature should be considered as a part of the mobility processes of location management (i.e. terminal location registration), call origination, call delivery and at other times as initiated by the network or terminal. The feature enables FPLMTS network operator to identify stolen, lost, suspicious or non-type-approved terminal equipment and then track or prevent the use of this terminal equipment. A blacklist of the identities of individual stolen, lost or suspicious terminal equipment and a white list of the identities of type-approved terminal equipment will be needed. + +Manufacturer should provide a terminal equipment identity, for example IMEI (International Mobile Equipment Identity), to be associated with a terminal equipment itself. + +**I.3.3.2.9 Cryptographic information management (CIM):** Cryptographic information management is a service feature which manages the secret information associated with cryptographic security mechanism including: the enhanced authentication mechanism, the integrity mechanism, and the encipherment mechanism. This feature is concerned with the generation, distribution, storage, updating, and deletion of cryptographic information whose secrecy or integrity must be assured. + +This feature is strongly related to User Authentication (UAUT) and Terminal Authentication (TAUT). Associated with each user and terminal is some information which only that user or + +terminal and possibly the network knows. Authentication is based upon the user or terminal convincing the network that it knows the correct secret information through some cryptographic protocol and vice versa. Unlike simple password authentication schemes the secret information is never disclosed. Furthermore, during the authentication process, the user and service provider can generate some shared secret information which can be the basis of other security mechanisms. + +The identity specific secret information is normally a key for a cryptographic algorithm. These keys are classified either as asymmetric or symmetric keys depending on the type of algorithm used. With symmetric keys (associated with conventional secret key encryption algorithms) the network needs to know and assure the confidentiality of the value of the key. Alternatively, if the key is asymmetric (associated with public key encryption algorithms) then the network only needs a copy of the public key of the secret/public key pair. Although the public key does not have to be protected from disclosure, the key must be protected from modification so that the public key really corresponds to the secret key of the entity in question. + +When public key schemes are used there is only limited security risk in distributing the authentication information to local service providers and the authentication algorithms could be standardized. Local authentication is possible. + +With secret key schemes, the keys could be distributed to local service providers; however, this greatly increases the risk of disclosure. Again, a standard authentication algorithm could be used and local authentication is possible. + +As an option with secret key schemes, the home service provider may not wish to disclose the secret key information but only distribute sufficient information for a limited number of authentication. Authentication in this case is essentially centralized. The type of information distributed depends on the authentication mechanism which may vary depending on the network involved. For example, the authentication process may need to proceed with only one message from the user to the service provider. The service provider would either have a list of expected authentication message from the home service provider and use these to check the identity locally, or the authentication message may need to be sent to the home service provider for remote authentication. The scheme chosen has implications for security and worldwide roaming. + +As another option with secret key schemes, the home service provider may not wish to disclose the secret key information but only distribute sufficient information for a local key being generated. Those local keys would be valid for a limited number of authentication. Authentication in this case is not centralized. + +This service feature also provides for the management of cryptographic data associated with encryption. The type of data which should be encrypted depends on the network and may include: user information, especially for radio networks; user identity, and signalling data; and terminal identities. + +### **I.3.4 Other services** + +**I.3.4.1 Internetwork Freephone (IFPH):** This service allows the served user having one or more installations to be reached from a specific network other than his/her network with a freephone number, and to be charged for this kind of call. The subscriber's network configuration is defined per subscriber direction using customer-specific information resident in multiple networks. + +**I.3.4.2 Internetwork Premium rate (IPRM):** This service provides two-way interactive communication between callers in one network and service/information providers in another network. The calling party is charged with a premium rate for this kind of call. It can be available in the public telephone network, whereby a service provider having connections to the public network can be allocated a special telephone number by a network operator, known as premium rate number. + +The service provider is able to earn revenue for each call successfully made to this premium rate number. In return, the service provider provides caller with some form of information service via the call connection. Calls to the premium rate number are charged to the caller at special rates. + +**I.3.4.3 Internetwork Mass calling (IMAS):** This service is designed to accommodate large volumes of simultaneous calls to a single directory number in another network. It can provide one-way, non-interactive communication between each caller in a given network and a service/information provider in another network. Using this service, the network operator can temporarily allocate a single directory number to the served user. Alternatively, each time a call is made to this number by an end user from another network, for example, an announcement can be played to the end user asking him to input an additional digit to indicate a preference. The choice made can be recorded and a counter incremented. When the service has ceased, the network operator can supply details of the total "votes" cast for each preference to the served user and the special number can be re-allocated. + +**I.3.4.4 Internetwork televoting (IVOT):** This service allows a service/information provider in one network to conduct voting or polling over the phone. The caller in another network votes by placing a call to a specific number corresponding to a voting/polling choice. The service provides communication between each caller in a given network and a service/information provider in another network. The service/information provider receives a tally of the number of calls to each number. Televoting enables subscribers to survey public opinions using the telephone network. Persons wishing to respond to an opinion poll can call televoting numbers to register their votes. The charging is to the discretion of the service subscriber. As an option, using this service, the network operator can temporarily allocate directory numbers to the served user. Each time a call is made to one of these numbers by an end user from another network, an announcement can be played to the end user, acknowledging the call, and a count of calls made to this number can be incremented. When televoting has ceased, the network operator can supply details of the total numbers of calls made to each number to the served user in a different network, and the special numbers can be re-allocated. Calls made to these special numbers may be charged at varying rates. + +**I.3.4.5 Global Virtual Network Service (GVNS):** The global virtual network service is a global switched VPN service supported by multiple networks (e.g. offered to customers over PSTN and/or ISDN). + +**I.3.4.6 Completion of Call to Busy Subscriber (CCBS):** This service enables a calling user encountering a busy destination to have the call completed when the busy destination becomes not busy, without having to make a new call attempt. + +**I.3.4.7 Conference calling (CONF):** This service enables a group of users to be connected into a multi-party call. + +**I.3.4.8 Call Hold (HOLD):** This service allows a user to place a call on hold and play an announcement to the held party, and to initiate a new call. The user can subsequently resume participation in the original call. + +**I.3.4.9 Call Transfer (CT):** This service allows a user to place a call party on hold and to be offered dial tone to provide a destination number (optionally service logic can provide the destination number). Upon successful call set-up, the subscriber is released and the held party is connected to the new destination in a two-party active call. + +**I.3.4.10 Call Waiting (CW):** This service allows a user to notify a subscriber of the occurrence of a call termination attempt, while that subscriber is participating in an active call. Upon the subscriber's request, the network is able to place on hold the call party participating in a previous active call, and allow the subscriber to accept the incoming call. The subscriber is then associated + +with both calls and able to toggle between the two calls, causing the other call parties to toggle between hold and active conditions. + +**I.3.4.11 Hot line (HOT):** The hot line service allows a user to place calls without providing, in the call request, the called party information required by the network to route the call. This routing information is stored in the network by prior subscription. The service also allows terminating restrictions to be provided to ensure that certain hot line subscribers only receive calls from other specified users. For the hot line receiving service, the user may receive calls only from a specified list of parties, a screening list before authorizing termination of the call. + +**I.3.4.12 Multimedia (MMD):** This service allows a subscriber to receive or send an integrated communication consisting of mixtures of voice, data, image, and video information. A key capability will be the ability to synchronize and control delivery of information from disparate sources (e.g. voice and data). This will include controlling delivery from multiple sources to a single recipient and from a single source to multiple recipients. + +The subscriber will also desire the ability to tailor a particular service to the type of terminating device or subscriber preference (i.e. turning off the video feed). Another key aspect of this service is that additional capabilities may be requested during the call (i.e. adding data capabilities to an existing voice connection). + +**I.3.4.13 Terminating Key Code Screening (TKCS):** This service enables a subscriber to screen incoming calls by means of a user-defined key, i.e. pin code. The callers are required to enter this key. In case of success, either the subscriber is alerted or the busy tone is sent to the caller. In case of failure, appropriate information is sent to the caller. The subscriber may activate and deactivate the service. + +**I.3.4.14 Message Store and Forward (MSF):** This service enables a user to send a message to be distributed to one or several destination users. Different types of messages (such as voice, data, and fax) may be supported and different methods of delivery and/or times of delivery (such as only to pre-subscribed mail-box holders or direct to any access) may be specified. + +**I.3.4.15 International telecommunication charge call (ITCC):** This service allows the holders of a telecommunication charge card to make use of a variety of telecommunication services provided by the card acceptor (visited network) and have the charges billed to the customer's account number by the card issuer (home network). It is described in Recommendations E.113 and Q.86.7. + +### **I.3.5 Other service features** + +**I.3.5.1 Automatic Call Back (ACB):** This service feature allows the called party to automatically call back the calling party of the last call directed to the called party. + +**I.3.5.2 Call Hold (HOLD):** This service feature allows a user to interrupt his/her connection to an existing call, without releasing that call. Some of the resources which were dedicated to that call (e.g. bearer capability) become available for other uses. + +**I.3.5.3 Call Retrieve (CRET):** This service feature allows a user to re-establish his/her connection to a call previously placed on hold. + +**I.3.5.4 Call Transfer (CT):** This service feature allows a user who is a party in two separate calls, to cause the other two parties to those calls to be connected to each other, releasing him/her from both. + +**I.3.5.5 Call Toggle (CTOG):** This service feature is applicable to a user who has one active call and one on hold. It allows him/her repeatedly to select the currently held party as the new connection, the previously connected party being automatically put on hold. + +**I.3.5.6 Call Waiting (CW):** This service feature informs a user already engaged in a call that another party is trying to establish a connection to him/her. Signalling means are provided to enable the user to instruct the network as to what further action it should take. + +**I.3.5.7 Meet-Me Conference (MMC):** This service feature allows the user to reserve a conference resource for making a multi-party call, indicating the date, time, and conference duration. At the specified date and time, each participant in the conference has to dial a designated number which has been assigned to the reserved conference resource, in order to have access to that resource, and therefore, the conference. + +**I.3.5.8 Multi-Way Calling (MWC):** This feature allows the user to establish multiple, simultaneous telephone calls with other parties. + +**I.3.5.9 Call Pick-Up (CPU):** This service feature enables a user to associate a call request to an already alerting call. The alerting call awaits answer while the user originating call pick-up signals to the network a desire to connect to the alerting call. The network then connects the call parties. + +**I.3.5.10 Calling Name Delivery (CND):** This service feature gives to the network operator the capability to display/announce the name of the calling party to the calling name delivery user (the called party) prior to answer, thus allowing this user to screen or distinctively answer the call. + +**I.3.5.11 Services On-Demand (SOD):** This service feature enables a user to request new services while initiating or involved in a call, e.g. multi-way calling at a pay phone. This includes the capability to invoke new services for the duration of the call. + +**I.3.5.12 Message Waiting Indication (MWI):** This feature enables a user to be informed that messages for his attention are waiting. + +**I.3.5.13 Feature Use Charging (FUC):** This feature enables the service provider to apply a certain charge to the use of any specified feature. + +**I.3.5.14 Internetwork Service Identification (INSI):** This service feature permits the receiving network, in an internetwork call, to receive from the originating network an indication of the service used in the received call. + +**I.3.5.15 Internetwork Rate Indicator, Forward (INRI-F):** This service feature is the ability to provide across networks, in the forward direction, an indication of the rate either being charged or to be charged for the presented call. + +**I.3.5.16 Internetwork Rate Indicator, Backward (INRI-B):** This service feature is the ability to provide across networks, in the backward direction, an indication of the rate either being charged or to be charged for the received call. + +**I.3.5.17 Real Time Flexible Rating (RTFR):** This service feature is the ability to vary in real time, for a given call, the billing rate, or the party being charged. This could be done at subscriber's direction, during a call or during call set-up. + +**I.3.5.18 Originating Carrier Identification (OCI):** This service feature permits the receiving network, in an internetwork call, to receive an indication identifying the "originating carrier" (i.e. the originating network/network operator). + +**I.3.5.19 Terminating carrier identification (OTC):** This service feature permits the receiving network, in an internetwork call, to receive from the originating network, an indication identifying the network where the call is destined to, or "terminating carrier" (i.e. the terminating network/network operator). + +**I.3.5.20 Resource Allocation (RAL):** This service feature enables the allocation, in advance and for a certain period of time, of pooled resources (e.g. conference bridges) required for a service. + +**I.3.5.21 Delivery of Complementary Information (DCI):** This service feature enables a calling user to supply to the network complementary information (e.g. an account number and a password) associated with the call set-up information. + +**I.3.5.22 Service Indication (SIND):** This service feature enables the called party to receive an indication concerning the presented call (for instance, an application to the freephone service would be the indication that the charge is to be supported by the called party; an application to the call forwarding service would be the forwarding number). + +**I.3.5.23 Service Negotiation (SNEG):** This service feature enables the parties involved in a call to negotiate the bearer services, teleservices and supplementary services to be provided for the call, depending on the services subscribed by the parties, the terminal and network capabilities, etc. This negotiation may take place both during call set-up and during the active call phase. + +**I.3.5.24 Call Forwarding (CF):** As defined in Recommendation Q.1211. Nevertheless, this feature is listed here for inclusion in IN CS-2 because some useful capability had not been fully included in IN CS-1. Refer to Annex B of Recommendation Q.1211 for more detail and for a template description of this feature. + +**I.3.5.25 B-ISDN Multiple Connections Point-to-Point (BI-MCPP):** This service feature enables a user to make a call between two points involving multiple connections, e.g. voice, audio, video, and/or data. This service feature may make use of B-ISDN point-to-point connection service feature (BI-PPC) and need other service features such as multi-connection. + +**I.3.5.26 B-ISDN Multi-Casting (BI-MCAST):** This service feature enables the network to set up multiple connections among multiple parties where the connections are point-to-multipoint unidirectional. This service feature may make use of B-ISDN point-to-multipoint connection service feature (BI-PMC) and/or B-ISDN multipoint-to-point connection service feature(BI-MPC) and need other service features such as leaf control. + +**I.3.5.27 B-ISDN Conferencing (BI-CONF):** This service feature enables the network to set up multiple connections among multiple parties where the connections are multipoint to multipoint. This service feature may make use of B-ISDN multipoint-to-multipoint connection service feature (BI-MMC) and other service features such as third party control. + +**I.3.5.28 Call Connection Elapsed time limitation (CCEL):** This service feature allows a calling party to make calls and communicate with one or more parties within a duration time predefined on a subscription basis. A tone or an announcement may be provided to the parties (i.e. calling and called parties) to indicate that the call will be cleared in a short time. + +**I.3.5.29 Special Facility Selection (SFS):** This service feature enables a call to be routed via a special facility (e.g. a virtual leased line) under the determination of service control. + +**I.3.5.30 Concurrent Features Activation with Bi-control (CFA-BC):** This service feature enables a call to be influenced by some features at two different point concurrently, such as originating side and terminating side. With this feature, a set of features is pre-defined in one service logic and controlled by its context with bi-control relationship. + +**I.3.5.31.a Customized Call Routing with Public networks (CCR-PU):** This service feature permits the public network to access other public networks for call processing and routing information. According to the subscriber's needs, the accessed public network determines each incoming call's appropriate destination, which could be local, national, or international telephone number. This action will remain under the sole control of the accessed public network, allowing for convenient updating, as well as confidentiality. CCR service feature can be provided either as a originating or as a terminating trigger feature. + +**I.3.5.31.b Customized Call Routing with Customers (CCR-CU):** This service feature permits the public network to access customers systems for call processing and routing information. The accessed system (which may be in private network, simple database, a PABX, or a terminal) determines each incoming call's appropriate destination, which could be local, national, or international telephone number. This action will remain under the sole control of the accessed system, allowing for convenient updating, as well as confidentiality. CCR service feature can be provided either as a originating or as a terminating trigger feature. + +**I.3.5.32 Internetwork Service Profile Interrogation (ISPI):** This service feature enables a user to interrogate (read only) the current contents of the user's service profile. The profile information could include information such as telecommunication services subscribed to, default parameters, activated supplementary services, current registrations for incoming and outgoing calls, etc. + +The identification and authentication procedures should be required at beginning. The network will respond with the requested information to the user if the information can be disclosed. Any rejection could depend on the authentication procedure, service profile restriction. + +**I.3.5.33 Internetwork Service Profile Modification (ISPM):** This service feature enables a user to modify (read and write) the appropriate user's service profile parameters that are allowed to be modified. Such parameters could be activation or deactivation of supplementary services, various default parameters, or PIN code. + +The identification and authentication procedures should be required at beginning. The network will respond with the requested information to the user if the information can be modified. Any rejection could depend on the authentication procedure or service profile restriction. + +**I.3.5.34 Internetwork Service Profile Transfer (ISPT):** This service feature enables service profile information to be transferred to other service profile storage locations in other networks. It is required to enable user profile information portability. The value of data which are simultaneously stored in some networks should be consistent. Information which is transferred to each visited network may depend on the contract with home network. The information updated in a visited network is transferred to the home network and conversely. + +**I.3.5.35 Reset of UPT registration for incoming calls (IRUR):** This service feature enables any person (the third party), even if not a UPT user, to reset any UPT registrations for incoming calls on the third party's terminal. + +**I.3.5.36 Mobility Call Origination (MCO):** The MCO feature covers both mobile call origination and UPT call termination. It is initiated within the mobility process of call origination. This feature does not require any location registration of terminal/users and allows a provision of customized authentication of terminal/user for call origination. This feature is independent of the registration states of the user and other users at the terminal. + +For terminals, due to the radio access nature of third generation mobile system such as FPLMTS, the timing of the creation of the access bearers for FPLMTS should be flexible, i.e. the off-air call set-up scheme may be possible. + +**I.3.5.37 Mobility Incall Delivery (MID):** The MID feature covers both mobile user call termination and UPT incall delivery. + +**I.3.5.38 Data communication between different protocol terminals (DCPT):** This service feature enables a mobile terminal to handle data communication between different protocol terminals in the intra-network or internetwork environment. This service feature enables a mobile terminal to handle data communication between different protocol terminals in the intra-network or internetwork environment. This type of data communication service feature is performed by protocol conversion unit within SRF upon requesting the data communication from the subscriber. + +**I.3.5.39 Charge Determination (CDET):** This service feature enables the calculation of charges related to a call. The charged party(s) may include FPLMTS subscribers, UPT subscribers and/or other calling parties. Charges may be based on usage and chargeable events/procedures (e.g. location update and service profile management). Two methods of charge determination are possible. + +The first method is off-line charging. Relevant call information (i.e. a call record) is stored by the network at the end of a call. Call records are periodically processed off-line to calculate call charges. Call charge records are then transferred in batch-mode to the local billing centre, which may then forward them to the home service providers or home network designated locations for subsequent billing of their subscribers. + +The second method is on-line charging. Charging information is calculated in real time during the call. This method supports calls from pay phones, charge metering and advice of charge. Some calls may involve both on-line and off-line charging (e.g. for split charging). + +**I.3.5.40 Charge Card Validation (CCV):** This service feature provides the ITCC service an authentication feature to compare user-side information, provided to the visited network, with information stored in the home network. Authentication attempts and fails are to be recorded for security purposes. + +**I.3.5.41 Call Disposition (CD):** This service feature provides the ITCC service the means to verify that the card has enough spare credit (e.g. the card usage value has not been exceeded) to give the permission to make the call. It implies that the usage of the card against the credit limit is tracked. The visited network sends to the home network an indication of the call card usage at the end of the call. The home network can accordingly decrement the current credit usage and, if exceeded, subsequent calls at authentication time are inhibited. + +**I.3.5.42 User Service Interaction (USI):** This service feature enables a user to interact with, and thus to send or receive information to or from, a service in association with a call involving this service. + +**I.3.5.43 Enhanced Call Disposition (ECD):** This service feature provides a means to cut down the call as soon as the card usage is exceeded. As soon as the card usage is exceeded, the call should be cut down and subsequent authentication requests should be inhibited according to pre-defined time basis (e.g. monthly and daily). As the card profile might imply different customers (such as the case for a multi-PIN card), concurrent usage, if any, should be tracked from different visited network locations. The previous requirements can be accomplished in different ways; anyway the home network is required to record the database access, in order to allows subsequent actions/requests during the same session. To accomplish the ECD requirements, the visited network gets a credit usage limit indication back in the authentication response. In this case the visited SCF is charged with real time control of the card usage and it has to cut down the call, if needed. + +## **I.4 Service management services** + +### **I.4.1 General** + +This subclause intends to provide short prose descriptions of targeted service management services and service features. + +### **I.4.2 Definition** + +**I.4.2.1 service control service** enables a subscriber to directly change the value of the parameters of his/her subscription to a telecommunication service and a service monitoring service after the service provisioning. + +**I.4.2.2 service control parameters** are what a subscriber can directly control regarding a subscription to a telecommunication service and a service monitoring service. The service control parameters available for control within this subscription are specified by service customization parameters. + +**I.4.2.3 service monitoring service** enables a subscriber to get information about the usage of a subscription to telecommunication service after the service provisioning. + +**I.4.2.4 service monitoring data** are what a subscriber can directly monitor regarding a subscription to a telecommunication service. + +**I.4.2.5 service customization service** provides the capability to select the type of telecommunication service feature, service control service, and service monitoring service to be provided to the subscriber after provisioning. Service customization is actually done by a network operator and possibly a service provider based on a subscriber's requirement during the service provisioning phase. + +Service customization parameters define the services, parameters, and data which a subscriber can manipulate as part of his/her subscription to a telecommunication service, service control service, and service monitoring service. The service customization parameter value are set through negotiation with a network operator and/or service provider. + +**I.4.2.6 service management processes** are the following types of activity performed by network operators/service providers: + +- **service deployment** is the introduction of a service into the IN-structured network in a subscriber independent way; +- **service provisioning** is the initial installation and deployment of necessary resources and data in appropriate network elements to provide a service subscription to a specific subscriber; +- **management during the service utilization** contains service monitoring, service maintenance, service traffic management, audit administration, and billing activities. + +The capability of the service management service can be recognized as follows: + +- a) Generic: Capabilities are generic for all services; +- b) Service specific: Capabilities are service specific but common for service subscribers; +- c) Service subscriber specific: Capabilities are service subscriber specific as well as service specific. + +### **I.4.3 Service management service/service feature** + +#### **I.4.3.1 Service customization service** + +**I.4.3.1.1 Telecommunications Service Customization (TSC):** Allows customization of telecommunication service to be provided to a specific subscriber according to requirements. There are two types of TSC: + +- Generic TSC: Customization parameters for telecommunication service are service-specific but common for subscribers. A network operator sets subscriber-specific initial values for each necessary customization parameter to specify the telecommunication service features. +- Subscriber-specific TSC: TSC is fully subscriber-specific, so it requires the creation of subscriber-specific telecommunication service. + +**I.4.3.1.2 Service Control Customization (SCC):** Allows customization of service control service to be provided to a specific subscriber according to requirements. There are two types of SCC: + +- Generic SCC: Service control parameters for service control service are service-specific but common for subscribers. A network operator sets initial values for each necessary customization parameter to specify service control parameters available to the subscription. +- Subscriber-specific SCC: fully subscriber-specific, so it requires the creation of subscriber-specific service control parameters. + +**I.4.3.1.3 Service Monitoring Customization (SMC):** Allows customization of service monitoring service to be provided to a specific subscriber according to requirements. There are two types of SMC: + +- Generic SMC: Service monitoring data for service monitoring service are service-specific but common for subscribers. A network operator sets a subscriber-specific initial list of service monitoring data to be collected for a subscription. +- Subscriber-specific SMC: SMC is fully subscriber-specific, so it requires the creation of subscriber-specific service monitoring data collection lists. + +#### **I.4.3.2 Service control service** + +**I.4.3.2.1 Subscriber Service Activation/Deactivation (SSAD):** Allows the subscriber to activate/deactivate a subscription to a telecommunication service. While the service is deactivated, network provides the default announcement which indicates that the telecommunication service stops. + +**I.4.3.2.2 Subscriber Monitoring Activation/Deactivation (SMAD):** Allows the subscriber to activate/deactivate a subscription to a service monitoring service. + +**I.4.3.2.3 Subscriber Profile Management (SPM):** Allows the subscriber to manage his/her subscription to a telecommunication service profile and a service monitoring service profile, i.e. terminating destinations, announcements to be played, call distribution, and call originating areas for traffic monitoring. + +**I.4.3.2.4 Subscriber Service Limiter (SSL):** Allows the subscriber to restrict the number of simultaneous usage of the telecommunication service. + +**I.4.3.2.5 Subscriber Service Invocation (SSI):** Allows the subscriber to invoke the telecommunication service. The target telecommunication service should be designed to be invoked using SSI. + +#### **I.4.3.3 Service monitoring service** + +**I.4.3.3.1 Subscriber Service Report (SSR):** Allows the subscriber to get a report on the usage of service subscriptions. The report may involve some statistics, such as the number of calls and mean call duration under specific conditions like time of day, origination area and termination telephone. + +**I.4.3.3.2 Billing Report (BR):** Allows the subscriber to get billing report of a chosen type. Several types of billing report may exist, e.g. total, terminating telephone basis, and group basis. + +**I.4.3.3.3 Subscriber Service Status Report (SSSR):** Allows the subscriber to receive the following status on each subscription to a telecommunication service: + +- performance (e.g. number of calls per measurement period); +- congestion (e.g. number of blocked calls per measurement period); +- fault (e.g. number of failed calls per measurement period). + +**I.4.3.3.4 Subscriber Traffic Monitoring (STM):** Allows the subscriber to monitor real-time usage of service subscriptions (e.g. the number currently processing calls in mass calling service, and the length of queue in call-queueing service). + +**I.4.3.3.5 Subscriber service Management service Usage Report (SMPUR):** Allows the subscriber to get a report on the usage of service control/monitoring service. + +#### **I.4.3.4 Other service management services** + +**I.4.3.4.1 Subscriber Service Testing (SST):** Allows the subscribers to perform their own test service subscriptions. + +**I.4.3.4.2 SMP Usage Report (SUR):** Allows the subscriber to get a report on usage of SMP (e.g. number of login sessions, length of each, CPU usage, and mass storage usage). + +**I.4.3.4.3 Subscriber Security Control (SSC):** Allows the subscriber to change security parameters (e.g. password). + +## **I.5 Service creation services** + +### **I.5.1 General** + +This subclause intends to provide short prose descriptions of targeted service creation services. + +### **I.5.2 Service specification services** + +**I.5.2.1 feature interaction detection:** Designed to aid detection of potential interactions between a new feature and existing features within a service (new or existing). + +**I.5.2.2 cross-service feature interaction detection:** Designed to aid detection of potential interactions between a new feature and existing features across services (new or existing). + +**I.5.2.3 feature interaction rule/guidelines generation:** Permits the specification of feature interaction rules for interactions within and across services (e.g. provisioning/rules governing which features can be provisioned together under specified conditions and network-level rules for run-time feature interaction management). + +**I.5.2.4 service and SIB cataloguing:** Provides a system for cataloguing the services and service-independent building blocks (SIBs), their intended uses, their inputs, their outputs, etc. for reference and re-use. + +**I.5.2.5 created service resource utilization:** Provides the capability to predict network resource utilization for services prior to deployment and to monitor actual resource utilization by a deployed service and limited testing use. + +### **I.5.3 Service development services** + +**I.5.3.1 creation interface selection:** Permits the selection of different interface devices for obtaining access to a service creation environment (SCE) (e.g. graphic terminals or ASCII terminals). + +**I.5.3.2 creation initiation:** Controls the process of initiating the creation of a new service or SIB (e.g. initial front-end loading activities, designation of permissible users). + +**I.5.3.3 editing:** Permits the editing of partially-created or existing services or SIBs. + +**I.5.3.4 combining:** Permits the creation of new services or SIBs as combinations of existing services and SIBs with new service logic to bind them together. + +**I.5.3.5 data population rule generation:** Permits the creation of the data population mechanism that are required for both the deployed services and supported services in the Service Management System (SMP). + +**I.5.3.6 SMP service creation:** Permits the creation of the SMP functions that are required to support the telecommunication services being created (e.g. OAM&P service logic programs for the SMP). Support is supplied as for all other services. + +**I.5.3.7 syntax and data checking:** Permits systems checks (graphical or textual) and data definition checks as a part of the service or SIB creation process. + +**I.5.3.8 service and SIB archiving:** Performs all the activities associated with storage, retrieval, and management of existing services and SIBs and services and SIBs still in the creation process. + +**I.5.3.9 service configuration control:** Permits access to the appropriately defined current and former versions of each service so that the defined set is available for use as desired. + +**I.5.3.10 SIB configuration control:** Permits access to the appropriately defined current and former versions of each SIB so that the defined set is available for use as desired. + +**I.5.3.11 network configuration tracking capability:** Provides the functions necessary to ensure that the SCE has an accurate representation for as much of the network as it needs to perform the service creation functions. + +### **I.5.4 Service verification services** + +**I.5.4.1 SCE testing:** Supports the localized testing of a created service or SIB in the SCE (e.g. debuggers, code tracers, graphics analysers). + +**I.5.4.2 created service simulation:** Supports the use of simulation testing of created services prior to release to the network. + +**I.5.4.3 cated service live testing:** Supports the distribution to the full network or to a limited set of network elements for "live" testing prior to making the new service generally available. + +### **I.5.5 Service deployment services** + +**I.5.5.1 SMP-created service data and service logic program update:** Provides the ability to build and distribute updates to the installed services being controlled by an SMP (e.g. modifications to general data for a service, bug fixes). + +**I.5.5.2 Service distribution:** Controls the distribution of services across a complex of related service creation entities. Service can be accessed and used at all sites in the associated system. + +**I.5.5.3 SIB distribution:** Controls the distribution of SIBs across a complex of related service creation entities. The SIB can be accessed and used at all sites in the associated system. + +**I.5.5.4 Data rule distribution:** Permits the distribution of updated data rules into the existing services and support entities. + +**I.5.5.5 Feature interaction rule distribution:** Permits the distribution of updated feature interaction rules into the system to improve existing rules and account for additional services in the system. + +**I.5.5.6 Multiple SMP support:** Permits the service creation entities to interact with different SMP implementations (e.g. permits one SCE to interact with SMPs of multiple vendors). + +**I.5.5.7 Network tailoring:** Provides the functions necessary to modify the SCEs and all the service-description-related information when changes occur in the structure of the network the SCEs are interacting with (e.g. the addition, deletion, modification of network elements). + +**I.5.5.8 Network element capability specification:** Permits the specification of the capabilities of network elements in a form that will be required for use during the service creation activities. + +**I.5.5.9 Network element function/capability assignment:** Permits the assignment within the service creation entities of function or capability to network elements as they will be used by the created services (especially useful when multiple network elements are capable of performing the same function). This assignment may be only for a particular service being created or set as a default for all services that are created. + +### **I.5.6 Service creation service management services** + +**I.5.6.1 SCE access control:** Provides the access security and limits the forms of access to those permitted for each registered user of an SCE. + +**I.5.6.2 SCE usage scope control:** Permits the definition of levels of activity for utilization of the SCE capabilities (e.g. standard service creation activities, new service creation element generation, and system-level activities with unlimited permission). + +**I.5.6.3 SCE recovery:** Permits the ability to recover the most recent versions of all activities, data, and service definitions after an SCE outage. + +**I.5.6.4 SCE release management:** Controls the SCE version releases that are available for use (actively or by recall) on a particular platform element. + +**I.5.6.5 SCE capability expansion:** Provides the ability to add new SCE functions (e.g. support functions such as editing service creation capabilities or improving implementations of existing capabilities). + +**I.5.6.6 SCE conversion:** Converts the representation of the created service from the representation that is used on one service creation platform into a representation that can be used on another service creation platform. + +**I.5.6.7 cross-SCE service maintenance:** Provides the functions necessary to ensure that the service creation infrastructures on different SCE implementations within related systems are capable of interworking as required. + +**I.5.6.8 SCE-to-SCE system consistency:** Provides the functions necessary to ensure that all SCEs in the related complex have consistent data service representations and capabilities. + +**I.5.6.9 SCE service/modular/system transference:** Provides the ability to transfer created or partially-created services, SIBs, and new SCE system creations across a complex of related SCEs. + +**I.5.6.10 conversion of created services:** Permits the conversion of all existing service representations to the representations required in another SCE implementation (e.g. different SCE implementations or a new release of the same implementation). + +**I.5.6.11 service management interaction:** Permits interaction with the SMP (e.g. obtains data not normally available to the SCE). + + + +# 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.1300-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..005dfdc28ca325889ab51d322b80ec72d13ebf84 --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60226fb27bd135ffdbaa577f6307b385d85ca842588bb2d0676907bd99ca3930 +size 8305 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ca12624fc289672c67765bfc9e2326db0e41b85 --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e107700c95796576c8b46588597335af8eb717f1960119bf6755e3ce50301c7c +size 27298 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2538cd3b9c65fdffc33f3da11d20ac95ebc646e5 --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e56f1abfe7e8f89c04b86c7126e09978f772a4c14958fd763d36aa25b3d901cc +size 41157 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..753a3bd5e5621fc5e774338c04a1c636a8abc591 --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7eaea6f2fb8d6aef22c0d7e09049e2bf58222093038bdf08b4874eb759270805 +size 67489 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9afa1e930f0734e38b71e444886b43a032b985d0 --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:038b9c5c66ab3b75042ed2ff4dd01d834d1e5a32ebaae746d140450d2be4f865 +size 46612 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15daeeee40f8731d325ae596378e44dc0b1e5172 --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92dbfb2c7914334f16074f8eabcf24ba243311e36cc5fe05903b7a918ad2c309 +size 35315 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91737f16e64067849c01cbbbe3ab9e1aa7cccddf --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b23262b08aa474d17fe9a9e246f72840bd4a1bae39794f0317d6c948479d9d66 +size 93825 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51e6b192694aa7360439ebae4690c610a94f1000 --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32769bbb9b73c1152d8ad4dd42ffcfa44bea1841961a3262cbdd485bbad155e3 +size 13694 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77d0c95721e73ebdd591ff599f3deaf95c1c16da --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6402722ba1c7b74d8aeb4bd2c7d6dcc4c51a721b514e4942aa548d826e55b67a +size 43591 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13e3769d8b222f5396b97eab3f99014b90bb636c --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8df53400dcfda141750691f3bff6266430760cee4aa4e405739b44ad8043d98 +size 61856 diff --git a/marked/Q/T-REC-Q.1300-199510-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7761d6517e1d530c1fe036fe4109e530f828e77b --- /dev/null +++ b/marked/Q/T-REC-Q.1300-199510-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b03c14dbc85ab7c09c6de092b14585bda21507efdd49d8f8ded4da04bc9f7e2 +size 35462 diff --git a/marked/Q/T-REC-Q.1301-199510-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1301-199510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a78dd4ded00a6ca875236c8636950de02bc34944 --- /dev/null +++ b/marked/Q/T-REC-Q.1301-199510-I_PDF-E/raw.md @@ -0,0 +1,1071 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.1301** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/95) + +**INTELLIGENT NETWORK** + +--- + +**TELECOMMUNICATION APPLICATIONS +FOR SWITCHES AND COMPUTERS (TASC) – +TASC ARCHITECTURE** + +**ITU-T Recommendation Q.1301** + +(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.1301 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +*Page* + +| | | | +|-------|--------------------------------------------|----| +| 1 | Introduction ..... | 1 | +| 2 | Scope ..... | 1 | +| 3 | References ..... | 1 | +| 4 | Terms and Definitions ..... | 2 | +| 4.1 | Abbreviations ..... | 2 | +| 5 | Architecture ..... | 2 | +| 5.1 | Domains ..... | 2 | +| 5.1.1 | Domain ..... | 2 | +| 5.1.2 | Call views ..... | 3 | +| 6 | Call monitoring ..... | 6 | +| 6.1 | Introduction ..... | 6 | +| 6.2 | CE monitoring versus call monitoring ..... | 6 | +| 6.3 | Call monitoring operation ..... | 6 | +| 7 | TASC interfaces ..... | 7 | +| 7.1 | Single TASC interface ..... | 7 | +| 7.2 | Multiple TASC interfaces ..... | 7 | +| 8 | TASC switching model ..... | 8 | +| 8.1 | TASC objects ..... | 8 | +| 8.1.1 | Communication Entity ..... | 8 | +| 8.1.2 | Line CE ..... | 9 | +| 8.1.3 | Distribution CE ..... | 10 | +| 8.2 | Communication Party ..... | 11 | +| 8.2.1 | Description and behaviour ..... | 11 | +| 8.2.2 | Types ..... | 11 | +| 8.2.3 | Line CP ..... | 11 | +| 8.2.4 | Distribution CP ..... | 12 | +| 8.3 | User ..... | 13 | +| 8.3.1 | Description and Behaviour ..... | 13 | +| 8.3.2 | Types ..... | 13 | +| 8.3.3 | Registered User ..... | 14 | +| 8.3.4 | Non-Registered User ..... | 15 | +| 8.4 | Call View ..... | 16 | +| 8.4.1 | Originating Call View ..... | 16 | +| 8.4.2 | Terminating Call View ..... | 16 | +| 8.4.3 | Incoming Distribution Call View ..... | 17 | +| 9 | Call view states ..... | 18 | +| 9.1 | Call View State descriptions ..... | 18 | +| 9.1.1 | Originating states ..... | 18 | +| 9.1.2 | Terminating Call View States ..... | 20 | +| 9.1.3 | Incoming Distribution Call View ..... | 21 | +| 9.1.4 | Agent model ..... | 22 | + +# **SUMMARY** + +This Recommendation identifies the Architecture that supports TASC (Telecommunication Applications for Switches and Computers) and is one in the Q.1300-Series Recommendations on TASC. The main purpose of TASC is to allow applications running within the network user's environment to integrate telecommunication services with computing facilities. This would typically allow business applications to use TASC to integrate the computer workstation and telephone at the user's desktop. This Recommendation does not define how the elements of the architecture are implemented. Part of the definition of the TASC architecture includes the TASC objects which are the basis for the TASC Functional Services. + +# **INTRODUCTION** + +The concept of TASC, which this architecture supports, is described in Recommendation Q.1300, TASC Overview. Although the TASC architecture identifies, describes and models interactions between the TASC objects, it does not specify how they should be implemented. In addition to call and telecommunication device objects, the role of Agents (as in ACD system) is modelled. + +# **BACKGROUND** + +This Recommendation is based on the experience of ECMA (Standardising Information and Communication Systems) and ANSI (American National Standards Institute) member companies in developing switch-to-computer interfaces and takes directions from CSTA (Computer Supported Telecommunications Application) and SCAI (Switch-to-Computer Application Interface) standards. + +# **KEYWORDS** + +Architecture, Models, Objects, TASC. + +# **TELECOMMUNICATION APPLICATIONS FOR SWITCHES AND COMPUTERS (TASC) – TASC ARCHITECTURE** + +*(Geneva, 1995)* + +# **1 Introduction** + +This Recommendation defines the architecture for TASC and identifies the various objects which represent information which the TASC interface operates on. The concept behind TASC is described in Recommendation Q.1300, which is considered essential reading prior to this Recommendation, and the services that the architecture supports are defined in Recommendation Q.1302. Recommendation Q.1303 defines the requirements for managing the objects herein described. + +# **2 Scope** + +This Recommendation defines an architecture for the support of Telecommunication Applications of Switches and Computers. The architecture supports the communication between the switch and computer and the services conveyed by that communication. This Recommendation considers how the information communicated is represented. TASC does not define how the aspects making up TASC in either the switch or computer environment are implemented. + +The emphasis of TASC has been to define third-party call control functions which also encompasses first-party call control. TASC is independent of any underlying mechanism and is applicable to public, private and hybrid networks. TASC is designed to be flexible in order to support other communication environments in addition to those based upon ISDN and Intelligent Network (IN) principles. + +It is focused on providing an application service interface between a switch and computer. + +TASC supports both a single-ended call (originating and terminating) view as well as a global call view. + +The TASC architecture accommodates different ways of viewing calls available in implementations but models these views on stable and accepted models of how calls work. + +# **3 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation Q.1300 (1995), *Telecommunication Applications for Switches and Computers (TASC) – General overview*. +- ITU-T Recommendation Q.1302 (1995), *Telecommunication Applications for Switches and Computers (TASC) – TASC Functional services*. +- ITU-T Recommendation Q.1303 (1995), *Telecommunication Applications for Switches and Computers (TASC) – TASC management: Architecture, methodology and requirements*. + +# 4 Terms and Definitions + +This Recommendation uses terms defined in Recommendation Q.1300. + +## 4.1 Abbreviations + +For the purposes of this Recommendation, the following abbreviations are used: + +| | | +|------|-----------------------------------------------------------| +| ACD | Automatic Call Distributor | +| CE | Communication Entity | +| CP | Communication Party | +| CV | Call View | +| FS | Functional Service | +| OCV | Originating Call View | +| TASC | Telecommunication Applications for Switches and Computers | +| TCV | Terminating Call View | + +# 5 Architecture + +The TASC Architecture provides a framework for communication between a computer and a switch. Recommendation Q.1300 describes the environments in which TASC may be used. + +## 5.1 Domains + +Domains identify the area that TASC may manipulate and influence. + +### 5.1.1 Domain + +Call domains ultimately deal with controllable and visible telecommunication devices in TASC's problem space. Such devices are referred to as Communication Entities (CE) so as to avoid confusion with connotations of specific types of devices. + +#### 5.1.1.1 Control and visibility + +TASC deals with the control and visibility of calls as they originate and terminate at CEs. All TASC functions revolve around this fundamental principle. Therefore, the problem space involves calls which can originate, terminate, or become visible at CEs. The CEs defined by TASC include Line CEs and Distribution CEs. + +When dealing with a call the switch is transparent to the application. TASC does not attempt to directly control or provide visibility of switches and computers. So switch and computer objects are not in the TASC problem space. Only the CEs related to or attached to switches and computers involved in the calls are visible. + +#### 5.1.1.2 Objects of interest + +TASC consists of a set of functional services that provide peer-to-peer applications with a standard means of communication for the control and visibility of calls. Ultimately it is the peer-to-peer applications which know the objects of interest. Peer-to-peer applications not only have a communication application context, but they also have a common, and agreed, set of CEs in the object space. In other words, the two applications know the CEs over which they have control and visibility. This object space is either statically or dynamically defined. The locations of the objects are transparent to TASC. This is depicted in Figure 1 below. + +![Diagram illustrating the transparent location of CEs. A Computer and a Switch are shown, each containing an Application and a TASC component. The Applications are connected to the TASC components, which are in turn connected to a central TASC component. The central TASC component is connected to a circle labeled 'Operation Domain' containing three CEs (CE 1, CE 2, CE 3). Arrows indicate 'Physical communication' between the TASC components and the CEs. A note states 'Object location is transparent to TASC'. A reference code 'T1168020-94/d01' is present.](fc46871d72c65d3381d9201646d23439_img.jpg) + +The diagram shows a 'Computer' box containing an 'Application' and a 'TASC' (oval). The 'Application' is connected to the 'TASC'. Below the 'Computer' box is another 'TASC' (oval). To the right is a 'Switch' box containing an 'Application' and a 'TASC' (oval). The 'Application' is connected to the 'TASC'. Below the 'Switch' box is another 'TASC' (oval). A central 'TASC' (oval) is connected to the 'TASC' in the 'Computer', the 'TASC' in the 'Switch', and the 'TASC' below the 'Computer'. Below the central 'TASC' is a circle labeled 'Operation Domain' containing three boxes labeled 'CE 1', 'CE 2', and 'CE 3'. Arrows point from the central 'TASC' to each of the 'CE' boxes. A double-headed arrow labeled 'Physical communication' connects the 'TASC' below the 'Computer' and the 'TASC' below the 'Switch'. A note with an arrow pointing to the 'Operation Domain' circle states 'Object location is transparent to TASC'. In the bottom right corner, the text 'T1168020-94/d01' is present. + +Diagram illustrating the transparent location of CEs. A Computer and a Switch are shown, each containing an Application and a TASC component. The Applications are connected to the TASC components, which are in turn connected to a central TASC component. The central TASC component is connected to a circle labeled 'Operation Domain' containing three CEs (CE 1, CE 2, CE 3). Arrows indicate 'Physical communication' between the TASC components and the CEs. A note states 'Object location is transparent to TASC'. A reference code 'T1168020-94/d01' is present. + +FIGURE 1/Q.1301 +**Transparent Location of CEs** + +#### 5.1.1.3 Operation and working domains + +The identification of CEs of interest to an application may occur through static (subscription arrangements) and dynamic means (messaging). The identified CEs are the operation domain for a particular application. Once that application has begun processing, the transitional objects such as CVs (calls views), CPs (connections between CEs and calls), and Users may be created and destroyed as a result of TASC related activity. The working domain may expand or contract during the lifetime of the application but may not expand to include CEs outside of the defined operation domain. It is the set of CEs (objects) which can be monitored by an application which form a Working Domain. The relationship between Operation and Working Domain is illustrated in Figure 2. + +TASC does not provide the ability for applications to acquire and lock the use of a CE for the exclusive use of a particular application process. Therefore coordination of applications and their use of CEs is outside the scope of TASC. + +For example, in a customer service department for a company which has agents and an ACD system, the object space for the application is the set of objects representing the agent CEs and ACD pilot numbers where calls are originated, terminated, or become visible. This Operation Domain does not include end users (i.e. the customers' phones), external phones where service calls are originated, or the switches or computers. The objects which can be monitored are the agent CEs and pilot numbers, and these represent the domain of objects of interest in the calls. This object space is defined for, and known by, the peer-to-peer applications. The locations of the objects are transparent to TASC. The objects actually monitored form the Working Domain. + +### 5.1.2 Call views + +TASC defines a call view object to represent a call in the problem space. A call view has a call view identifier, a call view state, and participants or parties. The call view identifier is unique within the Operation domain. That is, in the communication between the peer applications, the Call View ID identifies a unique call. No two calls visible to the peer applications may have the same Call view ID. + +![Diagram illustrating the relationship between the Operation Domain and the Working Domain for a single call. The Operation Domain is a large circle containing several 'CE' (Call Element) boxes. The Working Domain is a smaller circle within the Operation Domain. The Call Monitor Domain (global view) is a dashed rectangle enclosing some CEs. Individual Device Monitor Domains (single-ended view) are dotted circles around specific CEs. Lines connect CEs to show their involvement in the life of a single call.](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +The diagram shows a large circle labeled 'Operation Domain'. Inside it, a dashed rectangle labeled 'Call Monitor Domain (global view)' contains three 'CE' boxes. A smaller circle labeled 'Working Domain' is also inside the Operation Domain. Within the Working Domain, there are three 'CE' boxes, each enclosed in a dotted circle labeled 'Individual Device Monitor Domains (single-ended view)'. Lines connect various 'CE' boxes, with a label 'CE's involved in the life of a single call' pointing to one of the connections. + +Diagram illustrating the relationship between the Operation Domain and the Working Domain for a single call. The Operation Domain is a large circle containing several 'CE' (Call Element) boxes. The Working Domain is a smaller circle within the Operation Domain. The Call Monitor Domain (global view) is a dashed rectangle enclosing some CEs. Individual Device Monitor Domains (single-ended view) are dotted circles around specific CEs. Lines connect CEs to show their involvement in the life of a single call. + +T1168030-94/d02 + +FIGURE 2/Q.1301 +Operation and working domain + +#### 5.1.2.1 Single-ended view + +The single-ended view of a call is the view of call progress and call states from a CE's perspective. The TASC object model for a two-party call splits into originating and terminating views. For example, for a basic call, when that CE is originating a call, the switch provides the single-ended view incorporating the originating call model events. The actions of the terminating side are implied in those events. When that CE is terminating a call, the switch provides the single-ended view incorporating the terminating call model events. The actions of the originating side are implied in those events but cannot be guaranteed. Information available about that CE and other CEs in the call is made available in the single-ended view by the switch. + +Single-ended views are independent of each other. A switch may allocate separate call view identifiers for each single-ended view. + +#### 5.1.2.2 Monitoring within a single-ended view + +TASC defines a single-ended view for the associated CE. This means that TASC defines call events which are reported for calls based on whether the call is originating, terminating or distributing at the CE. Thus if a CE is being monitored and a call terminates at the CE, the terminating call events may be reported. If a CE is being monitored and a call originates at the CE, the originating call events may be reported. Events may also be reported for monitored CEs at which calls appear such as Distribution CEs. + +#### 5.1.2.3 Global view + +An alternative to the single-ended view is the global view where the view of call progress and call states are from the domain's perspective of a call. Thus all parties associated with a specific call can be visible with a global call view. Each party associated with the call still needs to adhere to the relevant basic call model (originating/terminating or distribution) but are united by a common identifier for the call. + +The extent of a global call is limited by the operation domain, thus a call that goes outside of the Operation Domain may only be able to support a single-ended view in some circumstances. + +#### 5.1.2.4 Monitoring within a global view + +The method used to invoke device and call monitoring differs but the event reports generated remain the same. With device monitoring, events are generated as a result of a change in the Call View state currently at the monitored device. With call monitoring, events are generated as a result of Call View state changes anywhere within the call. Two forms of Call Monitoring are defined within TASC: + +- 1) A Call Monitor set on a call will generate events as a result of Call View state changes anywhere within the call. A call where some CEs are outside the TASC operation domain may report less call progress information; at least one CE must reside within the Operation Domain for call monitoring to function. This type of monitor will follow a single call. It may only be invoked once the call has been created and a Call View ID returned to the application, e.g. after a TASC Make Call Functional Service request or Call-Arrived event (see Recommendation Q.1302). +- 2) A Call Monitor set on a CE will generate events as a result of a Call View state change for every call that has involved the specified CE since the call monitor was invoked. A call where some CEs are outside the TASC operation domain may report less call progress information; at least one CE must reside within the Operation Domain for call monitoring to function. This type of monitor will follow all calls which have contact with the specified CE, e.g. a call monitor on a distribution CE will monitor all calls which are distributed by that CE. Events will be generated during the complete life of each call distributed. + +Call monitoring is considered further in clause 6. + +#### 5.1.2.5 Calls between CEs + +As calls originate, arrive, terminate and disappear from CEs within the working domain, events are reported based on the single-ended view, features in effect, and characteristics of a CE. Since all calls are uniquely identified by a Call View ID, any and all events which specify the same Call View ID in the communication protocol between the peer applications refer to the same call. The switches assign and manage Call IDs although a management function may manipulate these ID's as described in Recommendation Q.1303 + +#### 5.1.2.6 Call view ID + +Call IDs are assigned and managed by the switch and must uniquely identify calls at CEs. These Call IDs must be unique within the Working Domain between peer applications. How the switch assigns Call IDs to calls between CEs in the operation domain (i.e. whether or not it uses the same Call view ID for both originating and terminating objects and events) must be understood and known by the applications prior to association. Thus Call view ID assignment is part of the application rules and in part a function of the type of network – public, private or hybrid. It should be noted that a request for a global call view may be rejected based upon the capabilities of the signalling environment in which the applications exists. + +#### 5.1.2.7 Global call view ID + +In a call between two CEs in a working domain, a Global Call is characterized by the same Call View ID being assigned for both originating, terminating and distributing endpoints. The Call view ID is unique in the Working Domain. + +Management of identifiers is achieved via parameters included in Functional Service responses and Event Reports. Identifiers cease to be valid when their context vanishes. If a call ends, its Call View Identifier is no longer valid to refer to that call. + +If a call changes its Call View Identifier when a Conference or Transfer occurs, identifiers are provided to link the old Call View Identifier to the new Call View Identifier. Similarly, if a CE Identifier is changed identifiers are provided to link new and old identifiers. Event Reports are used to report state changes. + +Identifiers can be re-used. Once an identifier has lost its context, it may be re-used to identify another object. + +Note that it is recommended that implementations do not re-use identifiers prematurely. + +Individual Call View and CE Identifiers are not guaranteed to be globally unique. TASC requires that the combination of Call View and CE Identifier be globally unique within an operation domain. To accomplish this, either the Call View Identifier, or the CE Identifier (or both) shall be globally unique. + +# **6 Call monitoring** + +## **6.1 Introduction** + +Call Monitoring is a Functional Service which will provide call progress information for all Communication Entities (CEs) involved in a call. During the life of a call, regardless of the operations performed on that call, this service will continue to provide call progress information for as long as the call remains within the TASC Operation Domain. Call Monitoring will continue to provide call progress information after transfers, forwarding and conference operations. + +## **6.2 CE monitoring versus call monitoring** + +CE monitoring will report call progress information while a call resides at CEs which have active CE monitors; this is known as the TASC Working Domain. The collection of CEs on which these monitors have been placed remains fairly static; they are not changed by any particular call. An application using CE monitoring must therefore define precisely the CEs from which it wishes to receive call progress information. The complete collection of CEs on which an application may set monitors is known as the TASC Operation Domain. + +During the life of a single call many CEs may participate; some with active CE monitors and some without. An application may therefore wish to invoke a monitor which will report call progress information throughout the life of a call, regardless of the CEs which are involved in that call. Call Monitoring will provide an application with this information without having to explicitly place monitors on all the CEs which have participated in that call. With Call Monitoring, the domain of the monitor changes very dynamically to include the collection of CEs involved during the life of a particular call. Figure 2 illustrates the relationship between the various TASC domains. + +The TASC Operation Domain is the collection of CEs on which an application may place a monitor. The TASC Working Domain represents the collection of CEs within the Operation Domain on which an application has placed CE monitors independently of any particular call. The Call Monitor Domain is the collection of CEs within the Operation Domain which participate in a single call when call monitoring has been enabled. There will be a Call Monitor Domain, dynamically changing as the call progresses, for each call monitor invoked. When a call dies, then its associated call monitor domain also dies. The Call Monitoring domain is only constrained by the Operation Domain and operates independently from the Working Domain but may include CEs within the Working Domain. When a CE monitor is invoked then the domain of that monitor is restricted to the individual CE, i.e. the individual CE monitor domain. + +## **6.3 Call monitoring operation** + +TASC Functional Services such as Transfer, Conference and Forwarding (see Recommendation Q.1302) will not prevent a Call monitor from following the call even if the Call View ID changes. A Call Monitor identifier will be included in each event reported. + +For a Call Monitor set on a CE a Call Monitor identifier will be returned. This Call Monitor identifier will be reported for all calls which involve that CE while the Call monitor is active. This Call Monitor identifier is distinct from any CE Monitor identifier. As an example, a Call Monitor placed upon a Distribution CE will generate call progress events for all calls which are distributed by that distribution CE and will use the same Call Monitor identifier. + +# 7 TASC interfaces + +## 7.1 Single TASC interface + +A single viewing point covers scenarios where there is a single TASC interface. There is a single switch, a single computer, and a single application context instance. The computer thus has control and visibility of calls from a single point. However, the operation domain of CEs which can be monitored may all be local, all remote, or mixed between local and remote. + +## 7.2 Multiple TASC interfaces + +Multiple viewing points exist when there are multiple TASC interfaces for the same operation domain. This may involve multiple interfaces between a single switch and a single computer or multiple interfaces with multiple switches and computers. The scenario calls for a common domain of CEs known by all applications on which monitors can be placed. There are many peer-to-peer applications operating in a cooperative manner. However, in order to cooperate they all share a common definition of the operation domain which can be monitored. The operation domain of CEs which can be monitored may all be local to a single switch or distributed between switches. + +There may be proprietary communication links between computers, between switches, and/or between computers and switches, to facilitate coordination and information flow. These links and information exchange are outside the scope of TASC. See Figure 3. + +![Diagram illustrating multiple TASC interfaces and their interaction with an operation domain.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram shows a network architecture with multiple components. At the top, 'Computer M' and 'Switch N' are shown. Each contains an 'Application' box connected to a 'TASC' circle. A thick horizontal line connects the 'Application' in Computer M to the 'Application' in Switch N. Below this, 'Computer 1' and 'Switch 1' are shown in a similar configuration. A thick horizontal line connects the 'Application' in Computer 1 to the 'Application' in Switch 1. Both 'Computer 1' and 'Switch 1' have multiple overlapping boxes behind them, representing multiple instances. At the bottom, a double-headed arrow labeled 'Physical Communication' connects the 'TASC' in Computer 1 and the 'TASC' in Switch 1. On the right, a large circle labeled 'Operation Domain' contains three boxes labeled 'CE 1', 'CE 2', and 'CE 3'. Dotted lines connect the 'TASC' in Computer 1, the 'TASC' in Switch 1, the 'TASC' in Computer M, and the 'TASC' in Switch N to this 'Operation Domain'. A text label 'Object location is transparent to TASC' is near the 'Operation Domain'. A text label 'Call IDs must be unique in the information flow between peer applications' is near the top left. A small code 'T1168040-94/d03' is in the bottom right corner of the diagram area. + +Diagram illustrating multiple TASC interfaces and their interaction with an operation domain. + +FIGURE 3/Q.1301 +Cooperating Applications + +In both ways of viewing calls identified in this Recommendation, the following is true: + +A call between two CEs in the operation domain is a Global Call view ID if the same Call view ID is assigned for both the originating and terminating events. + +The locations of the CEs are transparent to TASC. If a CE does not reside on the local switch, capabilities outside of TASC must exist to place a monitor on this 'remote' CE, signalling must exist to facilitate information flow between switches or computers, and global Call view ID management (i.e. management of Call view IDs between multiple switches) must be defined and provided. This is a function of the scope of the application, the type of network (public, private), and network capabilities. + +In a single interface, all CEs are viewed and controlled over a single interface regardless of location. With multiple interfaces, CEs may be viewed and controlled from multiple points but the views at all points are considered with Global Call IDs. + +### **In summary** + +- 1) TASC supports the following concepts: Operation Domain, Working Domains, Single-ended Calls View and Global Call Views. +- 2) Operation Domains are defined prior to application initiation. Working Domains are identified by dynamic means and may include a subset of those CEs which were identified as members of the Operation domain. +- 3) The physical locations of monitored CEs are transparent to TASC. +- 4) A Global Call View is a function of Call view ID management and assignment and thus a function of the switch, application, and/or network. Call view ID management is implementation specific. TASC provides the flexibility to support different Call view ID management schemes. +- 5) TASC does not define standardized signalling or information flow between applications in a distributed environment to facilitate coordination and control of calls across multiple TASC interfaces. However, TASC provides the basic information necessary to facilitate that coordination and control. + +# **8 TASC switching model** + +The TASC switching model provides an abstract view of switching objects and their behaviour. This switching model consists of TASC objects, their models, and their relationships. + +## **8.1 TASC objects** + +The following objects for TASC have been identified (see Figure 4): + +**Communication Entity (CE)** – An entity that originates, terminates, or becomes visible in a call. + +**User** – An entity that makes use of a CE (e.g. initiates a call or answers a call). + +**Call View (CV)** – An abstraction of a call which represents the progression of a Call at a CE from the standpoint of a CE involved in a call. + +**Communication Party (CP)** – An associative object that maintains the relationship between a call and CE. + +### **8.1.1 Communication Entity** + +#### **8.1.1.1 Description and behaviour** + +An entity that originates, terminates, or becomes visible in a call. Many users, calls, and CPs may be associated with each CE. + +#### **8.1.1.2 Types** + +**Line CE** – A component of a switch over which calls are originated from or terminated to a CE. + +**Distribution CE** – An entity that distributes calls to other CEs. + +![Diagram of TASC Objects showing a 'Global Call' within a 'Switch' box. The 'Global Call' is a large circle containing two 'CV' (Call View) circles. To the left of the 'Global Call' is a 'CE' (Control Element) rectangle, and to the right is another 'CE' rectangle. Below each 'CE' is a 'CP' (Control Point) circle. Arrows point from each 'CP' to its corresponding 'CE'. Outside the 'Switch' box, on both the left and right, are 'User' boxes connected to the 'CE' rectangles by horizontal lines.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Diagram of TASC Objects showing a 'Global Call' within a 'Switch' box. The 'Global Call' is a large circle containing two 'CV' (Call View) circles. To the left of the 'Global Call' is a 'CE' (Control Element) rectangle, and to the right is another 'CE' rectangle. Below each 'CE' is a 'CP' (Control Point) circle. Arrows point from each 'CP' to its corresponding 'CE'. Outside the 'Switch' box, on both the left and right, are 'User' boxes connected to the 'CE' rectangles by horizontal lines. + +T1168050-94/d04 + +FIGURE 4/Q.1301 +TASC Objects + +### 8.1.2 Line CE + +#### 8.1.2.1 Description and behaviour + +A component of a switch over which calls are originated from or terminated to a user. See Figure 5. + +![Diagram of a Line CE within a 'Switch' box. It shows a 'CV' (Call View) circle on the left, a 'Line CE' rectangle in the center, and a 'CP' (Control Point) circle at the bottom. An arrow points from the 'CP' to the 'Line CE'. A horizontal line connects the 'Line CE' to a 'User' box outside the 'Switch' box on the right.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Diagram of a Line CE within a 'Switch' box. It shows a 'CV' (Call View) circle on the left, a 'Line CE' rectangle in the center, and a 'CP' (Control Point) circle at the bottom. An arrow points from the 'CP' to the 'Line CE'. A horizontal line connects the 'Line CE' to a 'User' box outside the 'Switch' box on the right. + +T1168060-94/d05 + +FIGURE 5/Q.1301 +Line CE + +The call related events are those events reported by transitions in the originating and terminating basic call view. + +#### 8.1.2.2 Attributes + +**Line Identifier** – Each Line CE has at least one unique identifier. Some Line CEs may have multiple identifiers. + +**Call View Identifiers** – One or more call view identifiers may be associated with each Line CE. + +**CP Identifiers** – One or more CP Identifiers may be associated with each Line CE. A CP identifier is comprised of a CE identifier, and CV identifier if required for unambiguous identification. + +**User** – A user is associated with a Line CE. + +**State** – The condition of the Line CE is described by Enable, Disable, In-service, Out-of-service, etc. + +#### 8.1.2.3 Actions + +The actions associated with a Line CE are those provided by management (e.g. Enable, Disable) and those provided by user action (e.g. Set-Forwarding, Clear Forwarding, etc.). + +#### 8.1.2.4 Notifications + +The notifications associated with a Line CE are those provided by management (e.g. Enabled, Disabled) and those provided by user action (e.g. Forwarding-Set, Forwarding-Clear, etc.). + +### 8.1.3 Distribution CE + +#### 8.1.3.1 Description and behaviour + +An entity that distributes calls to other CEs. + +#### 8.1.3.2 Types + +**Incoming Distribution CE** – An entity that distributes calls to Line CEs and other incoming Distribution CEs. + +**Outgoing Distribution CE** – Not defined by this Recommendation. + +#### 8.1.3.3 Incoming Distribution CE + +##### 8.1.3.3.1 Description and Behaviour + +An entity that distributes calls to Line CEs or other Incoming Distribution CEs. + +The call related events are those events reported by transitions in the Incoming Distribution CE. + +##### 8.1.3.3.2 Attributes + +**Incoming Distribution CE Identifier** – Each Incoming Distribution CE has at least one unique identifier. Some Incoming Distribution CEs may have multiple identifiers. + +**Call View Identifiers** – One or more call view identifiers may be associated with each Incoming Distribution CE. + +**CP Identifiers** – One or more CP Identifiers may be associated with each Incoming Distribution CE. A CP identifier is comprised of a CE identifier, and CV identifier if required for unambiguous identification. + +**CE Identifiers** – One or more Line or Incoming Distribution CE Identifiers to which calls are to be distributed may be associated with an Incoming Distribution CE. + +**State** – The condition of the Incoming Distribution CE is described by Enable, Disable, In-service, Out-of-service. + +##### 8.1.3.3.3 Actions + +The actions associated with a Incoming Distribution CE are those provided by management (e.g. Enable, Disable, Query). + +##### 8.1.3.3.4 Notifications + +The notifications associated with an Incoming Distribution CE are those provided by management (e.g. Enabled, Disabled, QueryResult). + +## 8.2 Communication Party + +### 8.2.1 Description and behaviour + +When a CP is specified by the computer it should at least identify the CE. However, the omission of a Call View should not make the CP ambiguous to the switch (i.e. preventing the switch from identifying a single relationship). + +When a CP is specified by the switch then both the Call View and the CE should be specified. + +### 8.2.2 Types + +**Line CP** – Maintains an abstract call view association between a Line CE and an Originating or Terminating Call View which is direction independent. + +**Distribution CP** – Maintains an abstract call view association between a Distribution CE and a Call View which is direction independent. + +### 8.2.3 Line CP + +#### 8.2.3.1 Description and behaviour + +A Line CP maintains an abstract call view association between a Line CE and a particular Call View which is direction independent. See Figure 6. + +![Diagram of a Switch containing OCV/TCV, Line CE, and Line CP components.](18722c46c9e8475524e634dedd08bac2_img.jpg) + +The diagram shows a rectangular box labeled 'Switch'. Inside the box, on the left, is a circle containing the text 'OCV' and 'TCV'. On the right is a rectangle labeled 'Line CE'. At the bottom center is a circle labeled 'Line CP'. A thick horizontal line passes through the center of the 'OCV/TCV' circle and the 'Line CE' rectangle. An arrow points from the 'Line CP' circle up to this thick horizontal line. Below the diagram, the text 'T1168070-94/d06' is present. + +Diagram of a Switch containing OCV/TCV, Line CE, and Line CP components. + +FIGURE 6/Q.1301 + +##### Line CP + +#### 8.2.3.2 Attributes + +**Line CP Identifier** – Each Line CP has a unique identifier. A CP identifier is comprised of a CE identifier, and CV identifier if required for unambiguous identification. + +**Call View Identifier** – Only one Call View Identifier may be associated with each Line CP. + +**Line CE** – Only one Line CE may be associated with each Line CP. + +**State** – The abstract state association between the Line CE and a Call View (Null, Active, Held). + +#### 8.2.3.3 Actions + +The actions associated with a Line CP are those provided by management (Enable, Disable, Query). + +#### 8.2.3.4 Notifications + +The notifications associated with a Line CP are those provided by management (Enabled, Disabled, QueryResult). + +### 8.2.4 Distribution CP + +#### 8.2.4.1 Description and behaviour + +Distribution CP maintains an abstract call view direction independent association between a Distribution CE and a Distribution Call View. + +#### 8.2.4.2 Types + +**Incoming Distribution CP** – An entity that maintains an abstract call view association between an Incoming Distribution CE and a Distribution Call which is direction independent. + +**Outgoing Distribution CP** – Not defined by this Recommendation. + +#### 8.2.4.3 Incoming Distribution CP + +##### 8.2.4.3.1 Description and behaviour + +Incoming Distribution CP maintains an abstract call view association between an Incoming Distribution CE and an Incoming Distribution Call View which is direction independent. See Figure 7. + +![Diagram of a Switch containing an Incoming Distribution CV, an Incoming Distribution CE, and an Incoming Distribution CP.](2de714cedbbdd36f901f71bafa78f75a_img.jpg) + +The diagram shows a rectangular box labeled 'Switch'. Inside the box, there are three components: 'Incoming Distribution CV' (represented by a circle on the left), 'Incoming Distribution CE' (represented by a rectangle on the right), and 'Incoming Distribution CP' (represented by a circle at the bottom). A thick horizontal line connects the 'Incoming Distribution CV' and the 'Incoming Distribution CE'. An arrow points from the 'Incoming Distribution CP' up to this thick horizontal line. Below the diagram, the text 'T1 168080-94/d07' is present. + +Diagram of a Switch containing an Incoming Distribution CV, an Incoming Distribution CE, and an Incoming Distribution CP. + +FIGURE 7/Q.1301 +**Incoming Call Distribution CP** + +##### 8.2.4.3.2 Attributes + +**Incoming Distribution CP Identifier** – Each Incoming Distribution CP has a unique identifier. A CP identifier is comprised of a CE identifier, and CV identifier if required for unambiguous identification. + +**Call View Identifier** – Only one Call View identifier may be associated with each Incoming Distribution CP. + +**Incoming Distribution CE** – Only one Incoming Distribution CE may be associated with each Incoming Distribution CP. + +**State** – The abstract state association between the incoming Distribution CE and an Incoming Distribution Call View (Null, Active, Held). + +##### 8.2.4.3.3 Actions + +The actions associated with an Incoming Call Distribution CP are those provided by management (Enable, Disable, Query). + +##### 8.2.4.3.4 Notifications + +The notifications associated with an Incoming Call Distribution CP are those provided by management (Enabled, Disabled, QueryResult). + +## 8.3 User + +### 8.3.1 Description and Behaviour + +An entity that makes direct use of a CE (e.g. initiates or answers a Call). A user may be associated with multiple CEs and Call Views. See Figure 8. + +![Diagram showing a Switch containing a Line CE connected to a User.](9b62a616c7a1097c5da57f001ab6dd64_img.jpg) + +The diagram illustrates a 'Switch' represented by a large rectangle. Inside this rectangle is a smaller rectangle labeled 'Line CE'. To the right of the 'Switch' rectangle is a rounded rectangle labeled 'User'. A thick black horizontal oval connects the 'Line CE' rectangle to the 'User' rounded rectangle. Below the diagram, the text 'T1168090-94/d08' is visible. + +Diagram showing a Switch containing a Line CE connected to a User. + +FIGURE 8/Q.1301 + +User + +### 8.3.2 Types + +**Registered User** – A user that is identified by some log-on process. + +- **Agent** – A type of registered user that is distinguished from other users by being able to log-on to systems which distribute calls. +- **Other Registered User** – A type of registered user that performs a registration or explicit identification action, e.g. authorization code. + +**Non-Registered User** – A user whose identity cannot be ascertained by TASC. + +### 8.3.3 Registered User + +#### 8.3.3.1 Description and behaviour + +A user that is identified by some log-on process. + +#### 8.3.3.2 Attributes + +**Registered User Identifier** – Each registered user has a unique identifier. + +**Call View Identifiers** – One or more Call View Identifiers may be associated a single each registered user. + +**Line CEs** – One or more Line CE Identifiers may be associated with a single registered user. + +**State** – The condition of the registered user at a Line CE (e.g. Null, Active). + +#### 8.3.3.3 Actions + +The actions associated with a User are those provided by management (Enable, Disable, Query). + +#### 8.3.3.4 Notifications + +The notifications associated with a User are those provided by management (Enabled, Disabled, QueryResult). + +#### 8.3.3.5 Agent + +##### 8.3.3.5.1 Description and behaviour + +A type of registered user that is distinguished from other users by being able to log-on to systems which distribute calls. Agents may be members of one or more pools of agents or agent groups. An example of a system which coordinates and distributes calls is an automatic call distribution system. The agent group can be identified by an agent group identifier. Agents are represented in TASC as agent objects. In subsequent text, the word agent means agent object. + +Agents have agent identifiers which uniquely identify the agent. Each agent may also have an agent password to be used during log-on for security. + +Agents may control their availability to receive calls by invoking agent operations such as log-on, log-off, and indicating ready or not ready to accept calls. Agents have states and agent operations result in state changes. The agent state may be used by the call distribution system to determine the availability of agents. An agent may or may not be in different states in different groups. + +Agent events may be reported by the switch to the computer when an agent invokes an operation at a telephone station or when an agent invokes one of the Manipulate Feature Functional Services (see Recommendation Q.1302). + +##### 8.3.3.5.2 Attributes + +**Agent Identifier** – Each Agent has a unique identifier. + +**Password** – Each Agent may have a unique password. + +**Agent Groups** – Agents may be members of one or more groups. + +**Call View Identifiers** – One or more Call View Identifiers may be associated with each Agent. + +**Line CE** – One or more Line CEs may be associated with each Agent. + +**State** – The condition of an Agent at a Line CE is described by Null, Agent-Logged-On, Agent-Logged-Off, Agent-Ready, Agent-Busy, Agent-Working-After-Call. + +##### 8.3.3.5.3 Actions + +The actions associated with an agent are those provided by management (Enable, Disable, Query) and those provided by agent action (Agent-Log-in, Agent-Log-Out, Agent-Ready, Agent-Busy, Agent-Working-After-Call). + +##### 8.3.3.5.4 Notifications + +The notifications associated with an agent are those provided by management (Enabled, Disabled QueryResult) and those provided by agent action (Logged-in, Logged-Out, Ready, Not-Ready, QueryResult). + +#### 8.3.3.6 Other registered user + +##### 8.3.3.6.1 Description and Behaviour + +A type of registered user that performs a registration or explicit identification action, e.g. authorization code. This user will have access to different services and those services may be limited by the registration process. For example, GVNS or CUG. + +##### 8.3.3.6.2 Attributes + +**Other Registered User Identifier** – Each Other Registered User has a unique identifier. + +**Password** – Each Other Registered User may have a unique password. + +**Other Registered User Groups** – Other Registered User may be members of one or more groups. + +**Call View Identifiers** – One or more Calls may be associated with an Other Registered User . + +**Line CE** – One or more Line CEs may be associated with an Other Registered User. + +**State** – The condition of the Other Registered User at a Line CE is described by (e.g. Null, Active). + +##### 8.3.3.6.3 Actions + +The actions associated with an Other Registered User are those provided by management (Enable, Disable, Query) and those provided by the Other Registered Users action (e.g. authorization code). + +##### 8.3.3.6.4 Notifications + +The notifications associated with an Other Registered User are those provided by management (Enabled, Disabled QueryResult) and those provided by Other Registered Users actions. + +### 8.3.4 Non-Registered User + +#### 8.3.4.1 Description and behaviour + +A user whose identity cannot be ascertained by TASC. + +#### 8.3.4.2 Attributes + +**Non-Registered User Identifier** – A non-registered user may be recognized by the Line CE Identifier with which the user is associated. + +**Call View Identifiers** – One or more Call View identifiers may be associated with each non-registered user. + +**Line CE** – One Line CE identifier may be associated with each non-registered user. + +**State** – The condition of the non-registered user at a Line CE (e.g. Null, Active, etc.). + +#### 8.3.4.3 Actions + +The actions associated with a Non-Registered User are those provided by management (Enable, Disable, Query). + +#### 8.3.4.4 Notifications + +The notifications associated with a Non-Registered User are those provided by management (Enabled, Disabled QueryResult). + +## 8.4 Call View + +There is a relationship among the CEs and Call Views. For a particular CE a particular Call View is presented. This Call View may present a unique set of events which is derived from the call related attributes of the CE. Each Call view presents a single-ended view of a call which is the view of call progress and call states from a switch's perspective for that particular CE. + +The call view for a Line CE is separated into originating and terminating Call Views. + +The following are the currently recognized Call Views. + +### 8.4.1 Originating Call View + +#### 8.4.1.1 Description and behaviour + +A type of Call View that has one CE originating the call and one CP. + +#### 8.4.1.2 Attributes + +**Call View Identifier** – Each Originating Call View has a unique identifier. + +**Line CE Identifier** – Each Originating Call View has one Line CE. + +**Line CP Identifier** – Uniquely identifies the relationship between one CE and one call view (originating). A CP identifier is comprised of a CE identifier, and CV identifier if required for unambiguous identification. + +**Users** – Each Originating Call View has one User. + +**Call View State** – The condition of a Originating Call View. + +- 1) NULL +- 2) PENDING +- 3) ORIGINATING +- 4) DELIVERED +- 5) ESTABLISHED +- 6) FAILED + +#### 8.4.1.3 Actions + +The actions associated with a call view are those provided by management (e.g. Query) and those actions initiated by application or user action (Make-Call, Answer-Call, Clear-Call, Hold-Call, Retrieve-Call, Transfer-Call, etc.). + +#### 8.4.1.4 Notifications + +The actions associated with a call view are those provided by management (e.g. QueryResult) and those actions as a result of application or user action (Service-Pending, Call-Delivered, Call- Established, Call-Cleared, etc.). + +### 8.4.2 Terminating Call View + +#### 8.4.2.1 Description and behaviour + +A type of Call that has one terminating CE and one CP. + +#### 8.4.2.2 Attributes + +**Call View identifier** – Each Terminating Call View has a unique identifier. + +**Line CE Identifier** – Each Terminating Call View has one Line CE. + +**Line CP Identifier** – Uniquely identifies the relationship between one CE and one call view (terminating). A CP identifier is comprised of a CE identifier, and CV identifier if required for unambiguous identification. + +**Users** – Each Terminating Call View has one User. + +**Call View State** – The condition of a Terminating Call View. + +- 1) NULL +- 2) ARRIVED +- 3) RECEIVED +- 4) ESTABLISHED +- 5) FAILED + +#### 8.4.2.3 Actions + +The actions associated with a call view are those provided by management (e.g. Query) and those actions initiated by an application or user action (Make-Call, Answer-Call, Clear-Call, Hold-Call, Retrieve-Call, Transfer-Call, etc.). + +#### 8.4.2.4 Notifications + +The actions associated with a call view are those provided by management (e.g. QueryResult) and those actions as a result of application or user action (Call Arrived, Call Received, Call Established, Call Cleared). + +### 8.4.3 Incoming Distribution Call View + +#### 8.4.3.1 Description and behaviour + +A type of Call View that may have one Incoming Distribution CE and one Incoming Distribution CP. An incoming Distribution Call View describes the behaviour when an incoming call arrives at and is manipulated by a distribution function within a switch. + +#### 8.4.3.2 Attributes + +**Call View Identifier** – Each Incoming Distribution Call view has a unique identifier. + +**Incoming Distribution CEs** – Each Incoming Distribution Call has at least one Line CE and may have two Line CEs. + +**Incoming Distribution CPs** – Each Incoming Distribution Call has at least one Incoming Distribution CP. + +**Incoming Distribution Call State** – The condition of an Incoming Distribution Call are the following states: + +- 1) NULL +- 2) DISTRIBUTED +- 3) FAILED + +#### 8.4.3.3 Actions + +The actions associated with an Incoming distribution call view are those provided by management (e.g. Query). + +#### 8.4.3.4 Notifications + +The actions associated with an Incoming distribution call view are those provided by management and state transitions (e.g. QueryResult). + +# 9 Call view states + +The call view states are an abstraction of the call processing activity in the switch that particularly relates to a CE. Not all call processing activities are reflected in the TASC call view. For example, during the PENDING state, the destination CE address information is collected, yet the collection of the digit is not reported to the computer. + +Call view state transitions are reflected by call progress events which are reported at the connection. These call progress events uniquely indicate the new call view state. + +The following template is used to describe the call states: + +**Description** – Describes the state. + +**Entry Event Reported** – Identifies the event reported for the state transition. + +## 9.1 Call View State descriptions + +### 9.1.1 Originating states + +Figure 9 shows the state transition diagram from the originating end perspective. The following originating states are defined: + +- 1) NULL +- 2) PENDING +- 3) ORIGINATED +- 4) DELIVERED +- 5) ESTABLISHED +- 6) FAILED + +#### 9.1.1.1 NULL state + +##### Description + +The state where no call exists from the perspective of the TASC single-ended view. For example, the switch may verify the authorization of this CE to place an outgoing call with given properties (e.g. bearer capability or CE restrictions) before exiting the NULL state. The type of authorization may vary for different types of originating resources. + +**Entry Event Reported:** Call\_Cleared. + +#### 9.1.1.2 PENDING state + +##### Description + +The switch is collecting information for the purpose of processing the call. In addition, other information may be collected. + +**Entry Event Reported:** Service\_Pending. + +#### 9.1.1.3 ORIGINATED state + +##### Description + +Destination address analysis, route selection, and routing initiation are performed by the switch. Authorization may be performed. + +**Entry Event Reported:** Call\_Originated. + +#### 9.1.1.4 DELIVERED state + +##### Description + +The terminating end of the call is alerting. + +**Entry Event Reported:** Call\_Delivered. + +#### 9.1.1.5 ESTABLISHED state + +##### Description + +The destination CE has answered the call and the parties in the call may exchange information. + +**Entry Event Reported:** Call\_Established. + +#### 9.1.1.6 FAILED state + +##### Description + +Normal call progression has been aborted. Call failure indication is provided to calling party (e.g. busy). + +**Entry Event Reported:** Call\_Failed. + +![State transition diagram for originating call view states. States: NULL, PENDING, ORIGINATED, DELIVERED, ESTABLISHED, FAILED. Transitions include Call-Cleared, Service-Pending, Call-Originated, Call-Failed, Call-Delivered, Call-Established.](2119293733c74fc64de88aefd597f4bb_img.jpg) + +``` +stateDiagram-v2 + [*] --> NULL + NULL --> PENDING: Service-Pending + PENDING --> NULL: Call-Cleared + PENDING --> ORIGINATED: Call-Originated + PENDING --> FAILED: Call-Failed + ORIGINATED --> NULL: Call-Cleared + ORIGINATED --> DELIVERED: Call-Delivered + ORIGINATED --> FAILED: Call-Failed + DELIVERED --> NULL: Call-Cleared + DELIVERED --> ESTABLISHED: Call-Established + DELIVERED --> FAILED: Call-Failed + ESTABLISHED --> NULL: Call-Cleared + ESTABLISHED --> PENDING: Call-Cleared + FAILED --> NULL: Call-Cleared + FAILED --> PENDING: Call-Failed +``` + +State transition diagram for originating call view states. States: NULL, PENDING, ORIGINATED, DELIVERED, ESTABLISHED, FAILED. Transitions include Call-Cleared, Service-Pending, Call-Originated, Call-Failed, Call-Delivered, Call-Established. + +T1168100-94/d09 + +FIGURE 9/Q.1301 +Originating call view states + +### 9.1.2 Terminating Call View States + +Figure 10 shows the state transition diagram from the terminating end perspective. The following terminating call view states are defined: + +- 1) NULL +- 2) ARRIVED +- 3) RECEIVED +- 4) ESTABLISHED +- 5) FAILED + +#### 9.1.2.1 NULL state + +##### Description + +The state where no call exists from the perspective of the TASC single-ended view. For example, the authorization to route an incoming call to the terminating CE may be performed (e.g. business group restrictions, restricted incoming access to a CE). + +**Entry Event Reported:** Call\_Cleared. + +#### 9.1.2.2 ARRIVED state + +##### Description + +A call has arrived at or within the switch and the destination CE (e.g. telephone set, etc.) has been identified. No validation has been done as to the suitability of the selected CE for termination of the call (i.e. the CE may be busy, out of service, restricted, etc.). + +**Entry Event Reported:** Call\_Arrived. + +#### 9.1.2.3 RECEIVED state + +##### Description + +The terminating end of the call is alerting. + +**Entry Event Reported:** Call\_Received. + +#### 9.1.2.4 ESTABLISHED state + +##### Description + +The two CEs are connected. Information may be exchanged between the two users participating in the call. + +**Entry Event Reported:** Call\_Established. + +#### 9.1.2.5 FAILED state + +##### Description + +Normal call progression has been aborted. Call failure indication is provided to calling party (e.g. busy). + +**Entry Event Reported:** Call\_Failed. + +![State transition diagram for Terminating call view states. States: NULL, ARRIVED, RECEIVED, ESTABLISHED, FAILED. Transitions: Call-Received (NULL to ARRIVED), Call-Arrived (NULL to ARRIVED), Call-Cleared (NULL to ARRIVED, NULL to RECEIVED, NULL to ESTABLISHED), Call-Failed (ARRIVED to FAILED), Call-Received (ARRIVED to RECEIVED), Call-Failed (RECEIVED to FAILED), Call-Established (RECEIVED to ESTABLISHED), Call-Established (ARRIVED to ESTABLISHED), Call-Cleared (FAILED to NULL).](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NULL + NULL --> ARRIVED : Call-Received + NULL --> ARRIVED : Call-Arrived + NULL --> ARRIVED : Call-Cleared + NULL --> RECEIVED : Call-Cleared + NULL --> ESTABLISHED : Call-Cleared + ARRIVED --> FAILED : Call-Failed + ARRIVED --> RECEIVED : Call-Received + ARRIVED --> ESTABLISHED : Call-Established + RECEIVED --> FAILED : Call-Failed + RECEIVED --> ESTABLISHED : Call-Established + FAILED --> NULL : Call-Cleared + +``` + +T1168110-94/d10 + +State transition diagram for Terminating call view states. States: NULL, ARRIVED, RECEIVED, ESTABLISHED, FAILED. Transitions: Call-Received (NULL to ARRIVED), Call-Arrived (NULL to ARRIVED), Call-Cleared (NULL to ARRIVED, NULL to RECEIVED, NULL to ESTABLISHED), Call-Failed (ARRIVED to FAILED), Call-Received (ARRIVED to RECEIVED), Call-Failed (RECEIVED to FAILED), Call-Established (RECEIVED to ESTABLISHED), Call-Established (ARRIVED to ESTABLISHED), Call-Cleared (FAILED to NULL). + +FIGURE 10/Q.1301 +Terminating call view states + +### 9.1.3 Incoming Distribution Call View + +Figure 11 shows the state transition diagram from the incoming Distribution Call View perspective. The following distribution call view states are defined: + +- 1) NULL +- 2) DISTRIBUTED ARRIVED +- 3) FAILED + +#### 9.1.3.1 NULL + +##### Description + +The state where no call exists from the perspective of the TASC single-ended view. + +**Entry Event Reported:** Call\_Cleared (with a cause of distributed). + +#### 9.1.3.2 DISTRIBUTED ARRIVED + +##### Description + +A call has arrived at or within the switch and the destination CE (e.g. ACD, hunt group) has been identified. No validation has been done as to the suitability of the selected CE for termination of the call (i.e. the CE may be busy, out-of-service, restricted, etc.). + +**Entry Event Reported:** Call\_Arrived (with a cause of distributed). + +#### 9.1.3.3 FAILED + +##### Description + +Normal call progression has been aborted. + +**Entry Event Reported:** Call\_Failed (with a cause of distributed). + +![State diagram for Incoming Distribution Call View states showing transitions between NULL, DISTRIBUTION ARRIVED, and FAILED states.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +``` +stateDiagram-v2 + [*] --> NULL + NULL --> DISTRIBUTION ARRIVED : Call-Arrived + DISTRIBUTION ARRIVED --> NULL : Call-Cleared + DISTRIBUTION ARRIVED --> FAILED : Call-Failed + FAILED --> NULL : Call-Cleared +``` + +The diagram illustrates the state transitions for the 'Incoming Distribution Call View'. It consists of three states: 'NULL', 'DISTRIBUTION ARRIVED', and 'FAILED'. Transitions are as follows: from 'NULL' to 'DISTRIBUTION ARRIVED' on 'Call-Arrived'; from 'DISTRIBUTION ARRIVED' to 'NULL' on 'Call-Cleared'; from 'DISTRIBUTION ARRIVED' to 'FAILED' on 'Call-Failed'; and from 'FAILED' to 'NULL' on 'Call-Cleared'. A small label 'T1168120-94/d11' is present near the bottom right of the diagram. + +State diagram for Incoming Distribution Call View states showing transitions between NULL, DISTRIBUTION ARRIVED, and FAILED states. + +FIGURE 11/Q.1301 +Incoming Distribution Call View states + +#### 9.1.3.4 State diagrams + +### 9.1.4 Agent model + +The agent Model consists of the concepts of agent States and State Transitions. + +#### 9.1.4.1 Agent states + +The following states are defined for an agent: + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AGENT NULL | The state where an Agent is not logged on to a CE. Logging-on to a CE causes a transition from this state and Logging-off from a CE causes a transition to this state. | +| AGENT NOT READY | The state where an Agent is logged on to a CE but is not prepared to handle calls distributed by the distribution CE. An Agent may receive calls which are not handled by the distributor while in this state. | +| AGENT READY | The state where an Agent is logged-on to a CE and is prepared and waiting to handle calls from the distribution function. | +| AGENT BUSY | The state where a CE, on behalf of an Agent, participates in a call. | +| AGENT WORKING AFTER CALL | The state where a CE, on behalf of an agent, inactively participates in a call. While in this state the agent cannot receive further calls from the distributor function but may well be performing administrative duties for a previous call, e.g. updating a business order form. | + +#### 9.1.4.2 Agent diagram and transitions + +Figure 12 shows the agent state model and agent state transitions. + +![State transition diagram for an agent with five states: AGENT NULL, AGENT NOT READY, AGENT READY, AGENT BUSY, and AGENT WORKING AFTER CALL. Transitions are shown as double-headed arrows between states.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NULL + NULL --> NOT_READY + NULL --> READY + NULL --> BUSY + NULL --> WORKING_AFTER_CALL + NOT_READY --> NULL + NOT_READY --> READY + NOT_READY --> BUSY + NOT_READY --> WORKING_AFTER_CALL + READY --> NULL + READY --> NOT_READY + READY --> BUSY + READY --> WORKING_AFTER_CALL + BUSY --> NULL + BUSY --> NOT_READY + BUSY --> READY + BUSY --> WORKING_AFTER_CALL + WORKING_AFTER_CALL --> NULL + WORKING_AFTER_CALL --> NOT_READY + WORKING_AFTER_CALL --> READY + WORKING_AFTER_CALL --> BUSY + +``` + +T1168130-94/d12 + +State transition diagram for an agent with five states: AGENT NULL, AGENT NOT READY, AGENT READY, AGENT BUSY, and AGENT WORKING AFTER CALL. Transitions are shown as double-headed arrows between states. + +FIGURE 12/Q.1301 + +Agent state model + +Agent state transitions are shown in the Table 1 below. The original state is shown in the far left-hand column and the state to which the agent is moving shown across the top. The valid events which will be reported are shown within the table body. + +TABLE 1/Q.1301 + +Agent state transitions + +| | AGENT NULL | AGENT NOT READY | AGENT READY | AGENT BUSY | AGENT WORKING AFTER CALL | +|--------------------------|------------------|-----------------|-------------|------------|--------------------------| +| AGENT NULL | | Agent_logged_on | | | | +| AGENT NOT READY | Agent_logged_off | | Agent_ready | | | +| AGENT READY | Agent_logged_off | Agent_not_ready | | Agent_busy | | +| AGENT BUSY | | Agent_not_ready | Agent_ready | | Agent_working_after_call | +| AGENT WORKING AFTER CALL | Agent_logged_off | Agent_not_ready | Agent_ready | | | + +The agent events are: + +- Agent\_Logged\_On +- Agent\_Logged\_Off +- Agent\_Not\_Ready +- Agent\_Ready +- Agent\_Busy +- Agent\_Working\_After\_Call + +An agent will have access to both a data terminal for communicating to the application and a telephony terminal for communicating to the switch. An agent may perform operations at both of those terminals. If an agent logs on by using the telephony terminal, then the computer application will be informed of state changes by the events identified above. If an agent logs on by using the data terminal, then state changes will be notified to the switch by use of the Manipulate Agent Functional Service as defined within the TASC Functional Service definitions. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1701-199903-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f65d9f7e935fd8e383948913bc9d1930e660926c --- /dev/null +++ b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e14e57480fe8e00775cea7cccdf272043ee616d785f7d62ece55da96a807f4a +size 27451 diff --git a/marked/Q/T-REC-Q.1701-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e46258b9e7857208ea403c8fe77ea87cf23099c5 --- /dev/null +++ b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f815cde00ffd7ef8da14f8a5eaba66189a0a169c561cd9d3c07db58b48ca8d69 +size 8166 diff --git a/marked/Q/T-REC-Q.1701-199903-I_PDF-E/b3c108e7145f2017957569d06ea359cb_img.jpg b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/b3c108e7145f2017957569d06ea359cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab24356b2459ee257a98147a7befcf30f4337314 --- /dev/null +++ b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/b3c108e7145f2017957569d06ea359cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:556d2bc00179bcbeb8c8bca873108e483b4f79ac5d16951780190592287b74c4 +size 27108 diff --git a/marked/Q/T-REC-Q.1701-199903-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd2b0c4222d5ad95910373c60d2fed999afa87e2 --- /dev/null +++ b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b1213684342497803907f22a28b545f322c229afb19e135f48ec1df4c6ae7a1 +size 87756 diff --git a/marked/Q/T-REC-Q.1701-199903-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..103f9ff76d200d97229c068b18c53f5579aec0ac --- /dev/null +++ b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8948cf93dbbb2e837a04ba38f72ac8d81ed44ab5efbad7fb30e1d7407f4b379 +size 44438 diff --git a/marked/Q/T-REC-Q.1701-199903-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a541e0c58032e447bc6f70ba3f1bf55a7e5afa5d --- /dev/null +++ b/marked/Q/T-REC-Q.1701-199903-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0589aa0ca8ef39240730b017920e63ed3d0559d23735de6430cfd85ae02b4f67 +size 28926 diff --git a/marked/Q/T-REC-Q.1704-200810-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fa5890d7660182e6ea2597ef6f4f97b38dc528f --- /dev/null +++ b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2759a9d96780947e8b6f3adf0ab0278c50853804bbc381405464bb9b4dd91ad +size 6986 diff --git a/marked/Q/T-REC-Q.1704-200810-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b1e2d99ef76da3bf5f51f911433417aededf860 --- /dev/null +++ b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:486d4309903d204619ec2101261a244044159153d13703e0deaf8a988a8a6566 +size 43800 diff --git a/marked/Q/T-REC-Q.1704-200810-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..380b1465b5b95f3afe51705c1e29c9863b7d45c8 --- /dev/null +++ b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5e3b9e2bd66c1760daf88f88b67500efb528a8ff721e2020b7083b0d4e57fa4 +size 50791 diff --git a/marked/Q/T-REC-Q.1704-200810-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60483d7872ccef32edd4e1b85d4eb8f5eba3a995 --- /dev/null +++ b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2c9068e1226a5b2947c9800a3fbde061e15ff2aa53d1b1f3a7c6840bac3423f +size 56444 diff --git a/marked/Q/T-REC-Q.1704-200810-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8084696e37bf8f33660436c7d4c81eee94174579 --- /dev/null +++ b/marked/Q/T-REC-Q.1704-200810-I_PDF-E/raw.md @@ -0,0 +1,539 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1704** + +(10/2008) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +--- + +**Functional network architecture for +IMT-Advanced** + +Recommendation ITU-T Q.1704 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global connectivity and telecommunications. The text "International Telecommunication Union" is written in blue to the right of the globe. + +ITU logo + +# 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.1704** + +# **Functional network architecture for IMT-Advanced** + +## **Summary** + +Recommendation ITU-T Q.1704 specifies a long-term high-level network architecture for IMT-Advanced specified in Recommendations ITU-T Q.1702, Q.1703 and ITU-R M.1645. + +## **Source** + +Recommendation ITU-T Q.1704 was approved on 14 October 2008 by ITU-T Study Group 19 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +IMT-Advanced. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|---------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Introduction ..... | 3 | +| 7 General principles of the functional architecture..... | 3 | +| 8 Functional network architecture overview ..... | 4 | +| 8.1 NGN architecture overview..... | 4 | +| 8.2 IMT-Advanced architecture overview and NGN ..... | 4 | +| 9 Generalized functional architecture and functional entities ..... | 4 | +| 9.1 Network functions ..... | 4 | +| 9.2 Network functional entities ..... | 5 | + + + +## Recommendation ITU-T Q.1704 + +## Functional network architecture for IMT-Advanced + +# 1 Scope + +The scope of this Recommendation is to provide a long-term high-level network architecture for IMT-Advanced1 as specified by [ITU-T Q.1703], [ITU-T Q.1702], and [ITU-R M.1645]. + +This Recommendation identifies network functions specific to IMT-Advanced and defines the corresponding network functional entities through functional models, which will form the basis for further designating reference points and developing information flows and functional entity actions. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- | | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| [ITU-T M.3060] | Recommendation ITU-T M.3060/Y.2401 (2006), Principles for the management of next generation networks . | +| [ITU-T Q.1701] | Recommendation ITU-T Q.1701 (1999), Framework for IMT-2000 networks . | +| [ITU-T Q.1702] | Recommendation ITU-T Q.1702 (2002), Long-term vision of network aspects for systems beyond IMT-2000 . | +| [ITU-T Q.1703] | Recommendation ITU-T Q.1703 (2004), Service and network capabilities framework of network aspects for systems beyond IMT-2000 . | +| [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 (2006), Functional requirements and architecture of the NGN release 1 . | +| [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 . | + +--- + +1 The term "IMT-Advanced" is now used in place of "systems beyond IMT-2000" per ITU-R Resolution 56 (2007). + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 functional entity:** [ITU-T Y.2012] An entity that comprises an indivisible set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. + +**3.1.2 functional architecture:** [ITU-T Y.2012] A set of functional entities and the reference points between them used to describe the structure of an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. + +NOTE – The functional entities can be used to describe a set of reference configurations. These reference configurations identify which reference points are visible at the boundaries of equipment implementations and between administrative domains. + +**3.1.3 reference point:** [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. + +NOTE – A reference point may correspond to one or more physical interfaces between pieces of equipment. + +## 3.2 Terms defined in this Recommendation + +This Recommendation does not define any new terms. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|----------------------------------------------| +| 3GPP | 3rd Generation Partnership Project | +| AAA | Authentication, Authorization and Accounting | +| AP | Access Point | +| APR | Anchor Point Router | +| AR | Access Router | +| AS | Application Server | +| CSCF | Call Session Control Function | +| FE | Functional Entity | +| G-MM-FE | Global Mobility Management Functional Entity | +| HSS | Home Subscriber Server | +| IMT-2000 | International Mobile Telecommunications-2000 | +| IP | Internet Protocol | +| L2 | Layer 2 | +| L3 | Layer 3 | +| L-MM-FE | Local Mobility Management Functional Entity | +| NGN | Next Generation Network | +| P-CSC-FE | Proxy Call Session Control Functional Entity | +| PD-FE | Policy Decision Functional Entity | + +| | | +|----------|------------------------------------------------| +| QoS | Quality of Service | +| RACF | Resource and Admission Control Function | +| RAM-FE | Radio Access Management Functional Entity | +| RAN | Radio Access Network | +| SCF | Service Control Function | +| S-CSC-FE | Serving Call Session Control Functional Entity | +| TRC-FE | Transport Resource Control Functional Entity | + +# 5 Conventions + +Functional entities in this Recommendation with the same name as in [ITU-T Y.2012] follow the general concept stated in [ITU-T Y.2012]; however the former is not always identical to the latter mainly because of possible additional functionalities derived as a consequence of addressing mobility. Convergence, in a precise sense, in terms of functional entities that appear in this Recommendation and in [ITU-T Y.2012] is for further study. + +# 6 Introduction + +In defining a vision for the future of mobile telecommunications, a number of layers of detail is required. The highest layer is an overall end-user service oriented perspective. This is provided in [ITU-T Q.1701] and [ITU-T Q.1702]. + +[ITU-T Q.1703] provides the service and network capabilities and/or requirements framework, from the network aspect, for IMT-Advanced. + +The next level of detail is the definition of the high-level network architecture for IMT-Advanced, which includes the definition of functional entities and its relationships. This level is the objective of this Recommendation. + +It is expected that a future Recommendation will define how the information should flow among the functional entities in IMT-Advanced, according to the functional network architecture model adopted. + +# 7 General principles of the functional architecture + +The functional architecture incorporates the following general principles: + +- Network architecture based on IP technology + +Access networks, which provide a rich set of access mechanisms using various wired and wireless access technologies, terminate layer two link characteristics and provide IP-based connection to core networks. Core networks and application servers connected to them are IP based. + +- Modular construction using expandable components + +The subsystems themselves, such as access networks, core networks, and application servers; as well as the systems built based on them are hierarchical. In particular, core networks provide universal interfaces to different access networks and to all kinds of application servers. + +Accessibility to each subsystem is separately controlled based on each operator's policy; on the other hand in particular, paths that users can control to access application servers are prepared. + +- Open interfaces between various systems +Interoperation with homogeneous networks and with heterogeneous networks is facilitated with open interfaces in various levels of subsystems. + +# **8 Functional network architecture overview** + +The IMT-Advanced architecture should support multiple access networks, converged services in a converged network, enhanced security and protection, and total service accessibility, based on the services and network capabilities framework of network aspects defined in [ITU-T Q.1703] and aligned with the NGN architecture. + +## **8.1 NGN architecture overview** + +The NGN architecture is based on the general principles defined in [ITU-T Y.2011]. It is further detailed in [ITU-T Y.2012] for transport and service stratum functions and in [ITU-T M.3060] for management functions that apply to both transport and service strata. + +## **8.2 IMT-Advanced architecture overview and NGN** + +The IMT-Advanced architecture is based on the general principles defined in [ITU-T Y.2011]. It is not necessarily identical to the NGN architecture because of additional functions derived as a consequence of addressing mobility, recognizing that these two architectures are moving towards convergence. + +# **9 Generalized functional architecture and functional entities** + +This clause identifies network functions specific to IMT-Advanced and defines the corresponding network functional entities through functional models, which will form the basis for further designating reference points and developing information flows and functional entity actions. + +It is intended to link service and network capabilities defined in [ITU-T Q.1703] and specific to IMT-Advanced into functional entities defined in the NGN architecture, when possible. + +The IMT-Advanced architecture that encompasses these identified functional entities is to be understood as generalized, to allow for possible plural instantiations in more specific service or technology contexts. + +## **9.1 Network functions** + +### **9.1.1 Mobility management** + +The mobility management function manages mobility of terminals. In other words, it manages handover, location updating and paging for terminals. At handover and paging, the mobility management component sets routing information in entities of transport network. At location updating, the mobility management component tracks the paging area information of the terminal. + +Different mechanisms are applied based on the mobility management state of the terminal; i.e., location management and handover. + +#### **9.1.1.1 Location management** + +When the terminal is in idle state (i.e., it is not involved in an active session and/or radio resources for the terminal have been released), the network needs to track the location of the terminal by means of location update from the terminal. The network is able to reach the idle state terminal through the paging procedure. + +#### **9.1.1.2 Handover management** + +When the terminal is in active state (i.e., it is involved in an active session), the mobile terminal is required to be able to communicate whilst changing its point of attachment to the network due to its movement. + +### **9.1.2 QoS management** + +QoS management is meant to provide an end-to-end QoS which includes wireless and wired networks. In NGN environments, QoS management will be performed by the resource and admission control function (RACF). QoS will be based on users' preferences and/or applications. QoS management will be highly inter-related to the service control function (SCF), mobility managements and authentication, authorization and accounting (AAA). + +In order to efficiently meet diverse QoS requirements from the users/applications and achieve flexibility in developing QoS-enabled applications with no knowledge of the underlying transport technology and QoS mechanisms, RACF provides its QoS management service relative to a SCF in the service stratum, through which the users/applications can communicate with RACF entities to send QoS requirements, receive results and so forth. + +In order to provide an end-to-end QoS in the overall network interconnecting multiple access technologies and different operators' networks, RACF applies a distribution mechanism that distributes end-to-end QoS bearer specifications to each network and access system along the end-to-end path. Based on the information elements of the QoS specification, the RACF of each network and access system makes a local decision that is optimized for the local network domain. + +When RACF receives a QoS set up request from the SCF in the service stratum, it starts to set up QoS for the session. RACF asks mobility management to give the information for the route that a user's packet passes. + +Allowing differentiated QoS for different users will require the authentication and authorization of users for the requested levels of QoS, as well as accounting procedures, if the QoS is to be modified. + +### **9.1.3 Call session control function (CSCF)** + +The call session control function basically handles transactions for call/session setup, termination and forwarding to other call session control functional entities. It interacts with other network functions (mobility management, QoS management, security management, etc.) in order to support the call/session. + +The call session control function is realized by two functional entities, i.e., the proxy call session control functional entity (P-CSC-FE) and the serving call session control functional entity (S-CSC-FE). The P-CSC-FE acts like a proxy function to mobile terminals. The S-CSC-FE controls the call/session for the mobile terminals. It maintains a call/session state for management purposes. + +## **9.2 Network functional entities** + +### **9.2.1 Mobility management function** + +#### **9.2.1.1 Access router (AR)** + +The access router (AR) is an entity that connects a terminal to the network. This entity connects the terminal directly at the network layer. + +It manages the entries that contain the mapping of the terminal's network layer address to a port that connects to the corresponding AP that is associated with the terminal. Packets addressed to the terminal are forwarded by referring to the entries. + +It creates, updates, or deletes the entries when a RAM-FE notifies it of the AP selected by the RAM-FE. + +#### **9.2.1.2 Access point (AP)** + +The access point (AP) is an entity that connects terminals directly at the link layer to the network. It is connected to the AR. + +It does not terminate any network or upper layer protocol. It terminates the link layer protocol. + +#### **9.2.1.3 Terminal** + +The terminal is a device used by service subscribers to access the network. + +It is an entity that can connect directly to AP(s) at the link layer and to AR(s) at the network layer. + +It sends/receives the network control requests/responses to/from network control entities. + +It has two states, active and dormant, in conjunction with the routing information management in the mobility management entities. + +The active and dormant states are defined as follows: + +**Active:** The state in which the terminal is ready to send and receive packets. The transport network has the routing information of the terminal the L-MM-FE is currently serving. + +**Dormant:** The state where the terminal is not ready to send or receive packets. The transport network is not ready to route packets to its destination. + +#### **9.2.1.4 Anchor point router (APR)** + +The anchor point router (APR) is a router located in the L-MM-FE domain. There may be several APRs in an L-MM-FE domain. + +It will receive all packets on behalf of the terminals it is serving and forward them to the current address of the terminals through the ARs. + +This function has redundancy to avoid a single point of failure and achieve load balancing, regardless of whether or not it is distributed or centralized. + +Several APRs are located in the L-MM-FE domain. An APR is selected for each terminal. + +The APR is selected by the L-MM-FE. The selected APR is used while the terminal moves within the L-MM-FE domain. + +The area in which the APR does not change even if the terminal moves is defined as the APR domain. + +#### **9.2.1.5 Global mobility management functional entity (G-MM-FE)** + +The global mobility management functional entity (G-MM-FE) manages the global mobility for terminals. Global mobility is mobility between L-MM-FE domains. The G-MM-FE manages the addresses of terminals and L-MM-FE, where the terminal is located in the L-MM-FE domain. The G-MM-FE is not involved in local mobility management. + +It receives updated information from L-MM-FE when the L-MM-FE of a terminal changes. It stores the address of the L-MM-FE, which is used for routing information retrieval for the terminals. + +The G-MM-FE receives retrieval requests of routing information of a terminal from a router. The G-MM-FE forwards the request to the L-MM-FE that manages the routing information of the target terminal. + +It manages handover between L-MM-FE domains. It receives notifications of change of the L-MM-FE domain which is currently accessed to/from a terminal, and updates routing information for the terminal in routers, if needed. The notification comes from L-MM-FE. + +#### **9.2.1.6 Local mobility management functional entity (L-MM-FE)** + +The local mobility management functional entity (L-MM-FE) manages the local mobility for terminals. Local mobility is mobility within an L-MM-FE domain. The L-MM-FE domain is an area where the mobility related signals are controlled by the same L-MM-FE, even if the terminal moves. The FE is also involved in global mobility, which is mobility between L-MM-FE domains. + +The area of L-MM-FE domain is identical to that of APR domain. (Because one same APR is used while a terminal moves in the L-MM-FE domain.) + +It receives updated information from terminals when terminal changes paging area. It stores the paging area information, which is used for paging the terminals. + +The L-MM-FE receives a retrieval request from the AR and resolves the address of the G-MM-FE that manages the L-MM-FE domain of the target terminal currently located. The L-MM-FE may have the database for resolving the G-MM-FE from the address of target terminal. + +The L-MM-FE receives retrieval requests of routing information of a terminal from another L-MM-FE by way of the G-MM-FE. The request may trigger the paging for the terminal. From the paging, the L-MM-FE finds the routing information of the terminal, and sends the information directly to the L-MM-FE that requested the routing information of the terminal. + +When locating a particular terminal, the L-MM-FE can look for the appropriate RAM-FE or for multiple RAM-FEs whose addresses are in correspondence to the terminal, and request the RAM-FE or multiple RAM-FEs to page the terminal. + +The L-MM-FE manages the APRs and decides upon the appropriate APR when a terminal activates at paging or when initiating a communication. + +The L-MM-FE manages the inter-AR terminal handover within the L-MM-FE domain. It receives notifications of change of the AR that is currently connected to a terminal, and updates the routing information for the terminal in the APR and/or other routers, if needed. The notification may come from a RAM-FE or an AR. + +In case of intra-AR handovers, the RAM-FE only notifies the selected AP to the AR to which the terminal is connected and it does not notify any information to the L-MM-FE. Therefore, the L-MM-FE does not engage in intra-AR handover for terminals. + +The L-MM-FE manages addresses of terminals and RAM-FE. + +When the terminal moves from one L-MM-FE domain to another, the communication quality during handover and handover mechanisms should be equivalent to the case of inter-AR handover. + +The L-MM-FE has redundancy to avoid a single point of failure and achieve load balancing. There are several L-MM-FEs in a L-MM-FE domain. + +An L-MM-FE is selected when the terminal comes to a new L-MM-FE domain (i.e., active terminals perform handover from one domain to another and dormant terminals perform location registration to the new L-MM-FE domain). + +#### **9.2.1.7 Radio access management functional entity (RAM-FE)** + +The radio access management functional entity (RAM-FE) provides common interfaces to the L-MM-FE and the PD-FE. + +The RAM-FE receives the location update request from each radio system via control signalling in the radio systems. It sends the location update request with the addresses of terminals, the addresses of RAM-FE and location information of terminals to the L-MM-FEs via the common interface. + +The RAM-FE receives the paging request from the L-MM-FE and starts the paging procedure for each relevant radio system. The RAM-FE manages L3/L2 addresses of terminals and/or the addresses of radio systems. Even if the RAM-FE receives the control signal updating the location + +information from the RAN, the RAM-FE does not send the signalling to the L-MM-FE if that RAM-FE has already sent the same information to L-MM-FE. RAM-FEs can select the most appropriate radio system or the radio system's AP based on user's preference, QoS profile negotiated, and radio resource usage of the candidate APs when starting the paging procedure or handover, by performing (resource and QoS) coordination among the radio systems with the PD-FE. + +The RAM-FE can be accommodated in an AR or in multiple ARs. + +RAM-FE notifies the AP to the relevant entities as follows: + +When the RAM-FE selects the AP, the RAM-FE checks the AR that accommodates the selected AP. If the selected AP and the AP currently used are accommodated by the same AR, the RAM-FE notifies it to the AR. + +If the selected AP and the AP currently used are not accommodated in the same AR, the RAM-FE notifies the AR that accommodates the selected AP and notifies the new AR to PD-FE. + +![Figure 1 – Functional model for mobility management. The diagram shows a network architecture with two home networks, Home1 and Home2, and two visited networks, Visited1 and Visited2. Home1 contains G-MM-FE1, L-MM-FE1, RAM-FE1, AR1, and APR1. Home2 contains G-MM-FE2, L-MM-FE2, RAM-FE2, AR2, and APR2. Visited1 contains Terminal 1, AP1, and AR1. Visited2 contains Terminal 2, AP2, and AR2. A central C-plane U-plane connects the home networks. The diagram illustrates the functional model for mobility management, showing the interaction between various functional entities (FEs) and network elements (ARs, APs, Terminals) across different network domains.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +Figure 1 – Functional model for mobility management. The diagram shows a network architecture with two home networks, Home1 and Home2, and two visited networks, Visited1 and Visited2. Home1 contains G-MM-FE1, L-MM-FE1, RAM-FE1, AR1, and APR1. Home2 contains G-MM-FE2, L-MM-FE2, RAM-FE2, AR2, and APR2. Visited1 contains Terminal 1, AP1, and AR1. Visited2 contains Terminal 2, AP2, and AR2. A central C-plane U-plane connects the home networks. The diagram illustrates the functional model for mobility management, showing the interaction between various functional entities (FEs) and network elements (ARs, APs, Terminals) across different network domains. + +**Figure 1 – Functional model for mobility management** + +### 9.2.2 QoS management function + +In the NGN environment, QoS management will be performed by resource and admission control functions (RACF). The RACF executes policy-based transport resource control upon request of the SCF, determines transport resource availability, makes admission decisions, and applies controls to transport functions for enforcing the policy decisions. The RACF consists of two types of resource and admission control functional entities: the PD-FE (policy decision functional entity) and the TRC-FE (transport resource control functional entity). This decomposition of PD-FE and TRC-FE enables the RACF to support a variety of accesses and core networks (e.g., fixed and mobile access networks). + +#### 9.2.2.1 Transport function + +The transport function executes QoS policies to the IP flows based on the end-to-end QoS specifications instructed by PD-FE. That is, it marks the QoS class for packets and allocates the bandwidth to the flow. These instructions are directly sent to each transport function by the PD-FE. + +If the transport function does not have enough bandwidth to receive the instruction from PD-FE, it notifies the PD-FE that it cannot guarantee the required QoS for the communication, and then the PD-FE denies the communication. + +#### 9.2.2.2 Policy decision functional entity (PD-FE) + +This function acts as an end-to-end QoS allocation function and coordination function. It is in charge of performing the negotiations with mobile terminals trying to access the network (by means of a call initiation or a handoff) or P-CSC-FE, and routers and access systems via RAM-FE to provide the resources according to the network service level policies. To identify the routers that the users' packet passes, the PD-FE inquires the user's address to mobility management functions. It is + +also in charge of instructing the transport function to execute QoS policies based on the result of the negotiation. + +If the IP flow for the user data transfer expands to another network domain, PD-FEs in different networks negotiate with each other for inter-QoS allocation. + +In inter-AR handover cases, the PD-FE is notified of the new AR by the RAM-FE. The PD-FE inquires the new user's address to mobility management and instructs QoS execution to transport functions. + +#### 9.2.2.3 Transport resource control functional entity (TRC-FE) + +This function deals with the diversity of underlying transport technologies and provides the resource-based admission control decision results to the PD-FE. The TRC-FE is service-independent and consists of transport technology-dependent resource control functions. The PD-FE requests the TRC-FE in the involved transport networks to detect and determine the requested QoS resources along the media flow path. The TRC-FE may collect and maintain the transport network topology and the transport resource status information, and authorize resource admission control of a transport network, based on network information. + +#### 9.2.2.4 Radio access management functional entity for QoS + +Radio access management functional entity (RAM-FE) for QoS supports an interworking function between IMT-Advanced and various access systems. It converts each access system QoS signalling to/from common QoS signalling. In this negotiation, it asks the access system (e.g., radio resource management in 3GPP RAN) to setup radio bearer based on the request from the PD-FE. + +![Figure 2 – Functional model for QoS management. The diagram shows a sequence of functional blocks from left to right: Mobile terminal, Access system, IMT-Advanced (containing RAM-FE, RACF, PD-FE, TRC-FE, and Transport function), IMT-Advanced (containing PD-FE, TRC-FE, and Transport function), Access system, and Correspondent terminal. Two types of connections are shown: thin lines for 'QoS signalling' and thick lines for 'User IP flows'. The Mobile terminal connects to the first Access system. The first Access system connects to the first IMT-Advanced block via both signalling and flow lines. Inside the first IMT-Advanced block, the RAM-FE connects to the RACF, which connects to the PD-FE. The PD-FE connects to the TRC-FE, which in turn connects to the Transport function. The PD-FE also connects to the second IMT-Advanced block. Inside the second IMT-Advanced block, the PD-FE connects to the TRC-FE, which connects to the Transport function. The second IMT-Advanced block connects to the second Access system. Finally, the second Access system connects to the Correspondent terminal via both signalling and flow lines.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +Figure 2 – Functional model for QoS management. The diagram shows a sequence of functional blocks from left to right: Mobile terminal, Access system, IMT-Advanced (containing RAM-FE, RACF, PD-FE, TRC-FE, and Transport function), IMT-Advanced (containing PD-FE, TRC-FE, and Transport function), Access system, and Correspondent terminal. Two types of connections are shown: thin lines for 'QoS signalling' and thick lines for 'User IP flows'. The Mobile terminal connects to the first Access system. The first Access system connects to the first IMT-Advanced block via both signalling and flow lines. Inside the first IMT-Advanced block, the RAM-FE connects to the RACF, which connects to the PD-FE. The PD-FE connects to the TRC-FE, which in turn connects to the Transport function. The PD-FE also connects to the second IMT-Advanced block. Inside the second IMT-Advanced block, the PD-FE connects to the TRC-FE, which connects to the Transport function. The second IMT-Advanced block connects to the second Access system. Finally, the second Access system connects to the Correspondent terminal via both signalling and flow lines. + +Figure 2 – Functional model for QoS management + +### 9.2.3 Call session control function (CSCF) + +The call session control function basically handles transactions for call/session setup, termination and forwarding to other call session control functional entities. It interacts with other network functions (mobility management, QoS management, security management, etc.) in order to support the call/session. + +The call session control function is realized by two functional entities, i.e., the proxy call session control functional entity (P-CSC-FE) and the serving call session control functional entity (S-CSC-FE). The P-CSC-FE acts like a proxy function to mobile terminals. The S-CSC-FE controls the call/session for the mobile terminals. It maintains a call/session state for management purposes. + +#### 9.2.3.1 Proxy call session control functional entity (P-CSC-FE) + +The proxy call session control functional entity forwards call/sessions to the serving call session control functional entity from mobile terminals and vice versa. When the call/session control signalling cannot be sent to the correspondent node, the P-CSC-FE requests for mobility + +management to activate the terminal. When QoS is requested from the terminal, the P-CSC-FE directs QoS management to reserve the required resource. + +The P-CSC-FE controls the call/session for a given user. The call/session is initiated by a mobile terminal or the P-CSC-FE itself. + +The P-CSC-FE and the mobile terminal send and receive the call/session via the radio access management functional entity, which converts from access specific signalling to common network session signalling. + +The P-CSC-FE determines a change related to an active mobile terminal, and/or to the content that is being provided to that terminal and controls the changes. + +The P-CSC-FE holds the S-CSC-FE address, mobility management address and QoS management address for a given user. + +#### **9.2.3.2 Serving call session control functional entity (S-CSC-FE)** + +The serving call session control functional entity performs call/session control and service initiation for a given terminal. + +The session initiation may be authenticated and authorized by security management (e.g., HSS in 3GPP networks). + +When the S-CSC-FE receives call/session signals from the P-CSC-FE, it resolves the correspondent's S-CSC-FE address by inquiring mobility management, and then forwards the session signal to the correspondent's S-CSC-FE. + +The parties of the call/session may be identified by a string of alphabet letters, E.164 numbers or others. The S-CSC-FE may retrieve the address of the parties' mobile terminal with the identifier from directory manager. + +The S-CSC-FE collects the relevant data; static data (user profile, mobile terminal profile) from the global database (e.g., HSS in 3GPP systems) and dynamic data of mobile terminals (service processing status, etc.) from the mobile terminals. + +The S-CSC-FE may send a trigger to a media converter, when the mobile terminals in use change. + +The S-CSC-FE holds the P-CSC-FE address where the terminal is accommodated. + +#### **9.2.3.3 Global database for CSCF** + +Global database is a master database that manages the S-CSC-FE address of each mobile terminal. When an S-CSC-FE inquires a correspondent's S-CSC-FE address, it answers the correspondent S-CSC-FE address. When global database has no information of a mobile terminal, it returns null information, which means that the mobile terminal has not yet registered itself. + +#### **9.2.3.4 Radio access management functional entity for CSCF** + +Radio access management functional entity for the CSCF supports an interworking function between IMT-Advanced and various access systems. It converts each access system session signalling to/from common session signalling. + +##### **9.2.3.5 Application server (AS)** + +An application server (AS) offers value-added services. To this end, it interacts with the S-CSC-FE and global database. The application server may host and execute services with service logics. + +![Functional model for call session control function diagram showing two mobile terminals connected via access systems to a central IMT-Advanced network. The network contains AS, Global database, S-CSC-FE, and P-CSC-FE components, with RAM-FE units at the network edges.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph LR + subgraph IMT-Advanced + AS1[AS] --- GD[Global database] + AS2[AS] --- GD + S1[S-CSC-FE] --- GD + S2[S-CSC-FE] --- GD + S1 --- S2 + P1[P-CSC-FE] --- S1 + P2[P-CSC-FE] --- S2 + RAM1[RAM-FE] --- P1 + P2 --- RAM2[RAM-FE] + end + MT1[Mobile terminal] --- AS1yst[Access system] --- RAM1 + RAM2 --- AS2yst[Access system] --- MT2[Mobile terminal] + +``` + +Functional model for call session control function diagram showing two mobile terminals connected via access systems to a central IMT-Advanced network. The network contains AS, Global database, S-CSC-FE, and P-CSC-FE components, with RAM-FE units at the network edges. + +Q.1704(08)\_F03 + +**Figure 3 – Functional model for call session control function** + + + + + +## 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.1707-200802-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75da5264b725a13e955bd2fc53edfc94924c83c0 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1b3641852f03df8433df047d72104a2a8b3b569eb216c0c89bdb60502f3027a +size 38315 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..667bbb98acb8479194cb008886f5504fde15628b --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7553380118c1f6513f55f7ac311063814d0a5713f10446fd465e8b33db35f72 +size 40468 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b22ff9fd1f869a33cbfb28386338e272868e33d --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fab60a505797d7e968f2e08dcb4e49ab84f5c1167b72fe46b24392413430f00 +size 65857 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc505ab2c2fead616e89052ae156f01a7c4b0a75 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6431a5db853807838e964b75c007e0ca83e030458c813dec1aa129daeeeaad72 +size 26299 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab9b216ddfa2c0110e06c85dd17c1cf4e134f296 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:862c1b0b378e07f2bdc42aef92ac1f332de31bca2b5e275f9de790053ed566a0 +size 34459 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2c73c2ade76890fb0f352f1f0d827376098ba58 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8197ad30a66144eb311f0d741ea48f12e8607d620d81dd1889403ec6055cc375 +size 63884 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac871e941369f95171aba18e7d8ef2215f3b62ea --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:547f9d8051bcfe9b391316820f443fdd38e91ecb935c6887f31a65a0d21d9e93 +size 68852 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c07b1703dd84c07f2e41aa47074a54e33f9dc81 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd534d5c31d986c43d54cf6c3dc6e8b0e2b4f532137b1cd8f8cc13c24c3eba10 +size 40815 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3647dd8124dd820c612d36180e7d85d8d6cca702 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b772b7fd931c8b55df49727261e36fe50c840c2a325eddebac2c5b12ea8772f +size 65675 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12b698c63180fd9747ed8b6a6bbdc5136902dff5 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14210fc8b233dceb112690fa87f29034c7291595c514857640c1993e464f833e +size 28281 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2bf5693b7b4716d3d1c04bce9d0d6b6dabd5164 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83ffc7a424a67761297fcc7918fcf3604c608bf0e59bba4f5e794a4af47d0349 +size 60903 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..269fd263ea5b3d16c9984a3b937aa45ad8de9a83 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5991047907064880af7f3ef7582aa6e6155e391c0c2b4722d67dc4091f08c98a +size 41077 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_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.1707-200802-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51943c75037e19bbd15447d2383c5a03e4cc3298 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8ab5d1ad1fe94b6357e2262403b36ad22f6ac491ccb4f2a0aed6655e85f199f +size 65065 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e54e959274bf332bd4e20a9119725e44ea263646 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f147d286b9485dcbc753604e19998f7193262ffa240e99583dbf210d6c3eba14 +size 26883 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de782621d797725cec8ffd8e11a49249036fbc3b --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d7eb2f14c4b2ccd62da455d403b6ce17cb9d876fd1ef24305801899283f213f +size 54919 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7febdd7c7134adeccf37412e6d366b2113107237 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f926390e8b24a74b56325f55a9a767c7bd72c1602a44af9902ac1024679b619c +size 84998 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a9f19161ef5fdfef1ab1f23dd66e0fc933e01b1 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27a918ed6f5e94b114516eb50a1d4d23f951779e01206f531e39bae5e46c9fd0 +size 23789 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2814151bf08881c641a0b76b95c2147ff7dc7c42 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46b33026e31a5560d7c819de55802f8151e616b9d7115c2278c0b181703d9c0d +size 64384 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adf398b41c89571147c626699b45dc56a3f26bf8 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2755b96e3dd7cea24520a68c67558c968e9b7a1b2b1570e16ad2eb4d71f189ed +size 28156 diff --git a/marked/Q/T-REC-Q.1707-200802-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5771b66142d3d9d8ff02a1539658d8517829f988 --- /dev/null +++ b/marked/Q/T-REC-Q.1707-200802-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f2143233f57748f726207699b56d7dae4974abb92448aaf0d419954b228629a +size 55012 diff --git a/marked/Q/T-REC-Q.1741.1-200204-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1741.1-200204-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..35ab067e31a6eb0758175450bca5d65316d34337 --- /dev/null +++ b/marked/Q/T-REC-Q.1741.1-200204-I_PDF-E/raw.md @@ -0,0 +1,5263 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1741.1** + +(04/2002) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +--- + +**IMT-2000 references to release 1999 of GSM +evolved UMTS core network with UTRAN access +network** + +ITU-T Recommendation Q.1741.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 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.1741.1** + +## **IMT-2000 references to release 1999 of GSM evolved UMTS core network with UTRAN access network** + +## **Summary** + +This Recommendation identifies the IMT-2000 Family Member, "GSM evolved UMTS core network with UTRAN access network". This release of the family member is known to the Standards Development Organizations (i.e. ARIB, CWTS, ETSI, TTA, TTC) as the "3GPP Release 1999". + +## **Source** + +ITU-T Recommendation Q.1741.1 was prepared by ITU-T Study Group SSG (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 April 2002. + +## **Keywords** + +Core Network, GSM, IMT-2000, Release 1999, third generation system, UMTS. + +## 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 | +| 2.1 | Normative references..... | 1 | +| 2.2 | Informative references..... | 4 | +| 3 | Definitions ..... | 4 | +| 4 | Abbreviations and acronyms ..... | 7 | +| 5 | Introduction ..... | 14 | +| 6 | Basic architecture for the UMTS IMT-2000 family member..... | 14 | +| 7 | Network entities..... | 18 | +| 7.1 | Gateway Mobile Switching Centre (GMSC) ..... | 18 | +| 7.2 | Mobile Switching Centre and Visitor Location Register MSC/VLR
(MSC/VLR)..... | 18 | +| 7.2.1 | Mobile Switching Centre (MSC)..... | 18 | +| 7.2.2 | Visitor Location Register (VLR)..... | 19 | +| 7.3 | Home Location Register (HLR) ..... | 19 | +| 7.4 | Authentication Centre (AuC) ..... | 20 | +| 7.5 | Equipment Identity Register (EIR)..... | 20 | +| 7.6 | Gateway GPRS Support Node (GGSN)..... | 21 | +| 7.7 | Serving GPRS Support Node (SGSN) ..... | 21 | +| 7.8 | Gateway Mobile Location Centre (GMLC) ..... | 21 | +| 7.9 | GPRS Service Switching Function (gprsSSF) ..... | 22 | +| 7.10 | GSM Service Control Function (gsmSCF)..... | 22 | +| 7.11 | GSM Service Switching Function (gsmSSF)..... | 22 | +| 7.12 | GSM Specialised Resource Function (gsmSRF)..... | 22 | +| 7.13 | Gateway Location Register (GLR)..... | 22 | +| 7.14 | Intermediate GPRS Serving Node (IM-GSN)..... | 22 | +| 7.15 | Intermediate Mobile-services Switching Centre (IM- MSC)..... | 22 | +| 8 | Interfaces..... | 23 | +| 8.1 | C-Interface (Gateway Mobile Switching Centre (GMSC) – Home
Location Register (HLR))..... | 23 | +| 8.2 | D Interface (Visitor Location Register (VLR) – Home Location Register
(HLR)) ..... | 23 | +| 8.3 | E Interface (Mobile Switching Centre (MSC) – Mobile Switching Centre
(MSC))..... | 23 | +| 8.4 | F Interface (Mobile Switching Centre (MSC) – Equipment Identity
Register (EIR)) ..... | 24 | + +| | Page | | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 8.5 | G Interface (Visitor Location Register (VLR) – Visitor Location Register (VLR)) ..... | 24 | +| 8.6 | Gc Interface (Home Location Register (HLR) – Gateway GPRS Support Node (GGSN))..... | 24 | +| 8.7 | Gf Interface (Equipment Identity Register (EIR) – Serving GPRS Support Node (SGSN)) ..... | 24 | +| 8.8 | Gi Interface (Gateway GPRS Support Node (GGSN) – Public Network)..... | 24 | +| 8.9 | GLa Interface (Gateway Location Register (GLR) – Home Location Register (HLR))..... | 25 | +| 8.10 | GLb Interface (Gateway Location Register (GLR) – Visitor Location Register (VLR))..... | 25 | +| 8.11 | GLc Interface (Gateway Location Register (GLR) – Serving GPRS Support Node (SGSN))..... | 25 | +| 8.12 | GLd Interface (Gateway Location Register (GLR) – Intermediate Mobile services Switching Centre (IM- MSC))..... | 25 | +| 8.13 | GLe Interface (Gateway Location Register (GLR) – Intermediate GPRS Serving Node (IM-GSN))..... | 25 | +| 8.14 | GLf Interface (Gateway Location Register (GLR) – Short Message Service-Gateway Mobile Switching Centre (SMS-GMSC)) ..... | 25 | +| 8.15 | GLg Interface (Intermediate Mobile-services Switching Centre (IM- MSC) – Short Message Service-Gateway Mobile Switching Centre (SMS-GMSC)) ..... | 25 | +| 8.16 | GLh Interface (Intermediate Mobile-services Switching Centre (IM- MSC) – Mobile Switching Centre (MSC)) ..... | 26 | +| 8.17 | GLi Interface (Intermediate Mobile-services Switching Centre (IM- MSC)– Gateway Mobile Location Centre (GMLC)) | 26 | +| 8.18 | GLj Interface (Intermediate GPRS Serving Node (IM-GSN) – Gateway GPRS Support Node (GGSN))..... | 26 | +| 8.19 | GLk Interface (Intermediate GPRS Serving Node (IM-GSN) – Serving GPRS Support Node (SGSN))..... | 26 | +| 8.20 | Gn Interface (Gateway GPRS Support Node (GGSN) – Serving GPRS Support Node (SGSN))..... | 26 | +| 8.21 | Gp Interface (Serving GPRS Support Node (SGSN) – Public Network) ..... | 26 | +| 8.22 | Gr Interface (Home Location Register (HLR) – Serving GPRS Support Node (SGSN)) ..... | 27 | +| 8.23 | Gs Interface (Mobile Switching Centre (MSC)/Visitor Location Register (VLR) – Serving GPRS Support Node (SGSN)) ..... | 27 | +| 8.24 | gsmSCF – HLR Interface ..... | 27 | +| 8.25 | gsmSCF – gsmSRF Interface ..... | 27 | +| 8.26 | gsmSSF – gsmSCF Interface..... | 27 | +| 8.27 | gprsSSF – gsmSCF Interface..... | 27 | +| 8.28 | H Interface (Home Location Register (HLR) – Authentication Centre (AuC))..... | 28 | +| 8.29 | IuBC Interface (Core Network (CN) – Radio Network Controller (RNC))... | 28 | + +| | | | +|-------|----------------------------------------------------------------------------------------------------------------------------------|-----| +| 8.30 | IuCS Interface (Mobile Switching Centre (MSC) – Radio Network Controller (RNC)) ..... | 28 | +| 8.31 | IuPS Interface (Serving GPRS Support Node (SGSN) – Radio Network Controller (RNC)) ..... | 28 | +| 8.32 | Lc Interface (Gateway Mobile Location Centre (GMLC) – GSM Service Control Function (gsmSCF))..... | 28 | +| 8.33 | Le Interface (Gateway Mobile Location Centre (GMLC) – External LCS client)..... | 28 | +| 8.34 | Lg Interface (Mobile Switching Centre (MSC)/Visitor Location Register (VLR) – Mobile Location Centre (MLC)) ..... | 29 | +| 8.35 | Lh Interface (Home Location Register (HLR) – Gateway Mobile Location Centre (GMLC))..... | 29 | +| 8.36 | Mobile Switching Centre (MSC) – gsmSCF Interface..... | 29 | +| 8.37 | PSTN Interface (Mobile Switching Centre (MSC)/Visitor Location Register (VLR) – Public Switching Telephone Network (PSTN)) ..... | 29 | +| 9 | Technical specifications structure..... | 29 | +| 10 | Technical specifications..... | 36 | +| 10.1 | 21-series, Requirements specifications ..... | 36 | +| 10.2 | 22-series, Service aspects ..... | 38 | +| 10.3 | 23-series, Technical realization ..... | 65 | +| 10.4 | 24-series, Signalling protocols (User Equipment-Core Network) ..... | 95 | +| 10.5 | 26-series, Codecs (speech, video, etc.)..... | 110 | +| 10.6 | 27-series, Data ..... | 117 | +| 10.7 | 29-series, Signalling protocols (NSS) ..... | 123 | +| 10.8 | 31-series, UIM User Identity Module ..... | 130 | +| 10.9 | 32-series, Operation and Maintenance ..... | 132 | +| 10.10 | 33-series, Security aspects..... | 141 | +| 10.11 | 35-series, Algorithm specifications ..... | 144 | + +# ITU-T Recommendation Q.1741.1 + +# IMT-2000 references to release 1999 of GSM evolved UMTS core network with UTRAN access network + +# 1 Scope + +This Recommendation identifies the IMT-2000 Family Member, "GSM evolved UMTS core network with UTRAN access network". This release of the family member is known to the Standards Development Organizations (i.e. ARIB, CWTS, ETSI, T1, TTA, TTC) as the "3GPP Release 1999". + +The core network interfaces identified in this Recommendation and the radio interfaces identified in ITU-R Rec. M.1457 [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 which 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 [1], shall take precedence. + +# 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. + +NOTE – The reference to a document within this Recommendation does not give it, as a standalone document, the status of a Recommendation. + +## 2.1 Normative references + +- [1] ITU-R Recommendation M.1457 (2000), *Detailed specifications of the radio interfaces of international mobile telecommunications-2000 (IMT-2000)*. +- [2a] ETSI TS 123.002 (2001), *Network Architecture (Release 99)*. +- [2b] TTC JP-3GA-23.002(R99) (2001), *Network Architecture (Release 99)*. +- [2c] T1 T1.3GPP.23.002V340 (2001), *Network Architecture (Release 99)*. +- [2d] TTA TTAE.3G-23.002(R99) (2001), *Network Architecture (Release 99)*. +- [2e] CWTS CWTS-TSD-CN-23.002(R99) (2002), *Network Architecture (Release 99)*. + +--- + +1 Technical documents of Standards Development Organizations recognized under the provisions of ITU-T Rec. A.5 can be found under: + +- ARIB at +- CWTS at +- ETSI at +- T1 at +- TTA at +- TTC at + +- [3a] ARIB ARIB STD-T63-23.171(R99) Functional stage 2 description of location (2001), *services in UMTS*. +- [3b] ETSI TS 123.171 (2001), *Universal Mobile Telecommunications System (UMTS); Functional stage 2 description of location services in UMTS*. +- [3c] T1 T1.3GPP.23.171V330 (2001), *Functional stage 2 description of location services in UMTS*. +- [3d] TTA TTAE.3G-23.171(R99) (2001), *Functional stage 2 description of location services in UMTS*. +- [3e] CWTS CWTS-TSD-CN-23.171(R99) Functional stage 2 description of location (2002), *services in UMTS*. +- [4] ETSI EN 300 356-18 (2001), *ISDN User Part (ISUP) version 2 for the international interface: Part 18: Completion of Calls to Busy Subscriber (CCBS) supplementary service*. +- [5] ETSI EN 301 140-1 (1999), *Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 1: Protocol Specification*. +- [6] ISO/IEC 3309 (1993), *Information technology – Telecommunication and information exchange between systems – High level data link control (HDLC) procedures – Frame structure*. +- [7] ISO/IEC 4335 (1993), *Information technology – Telecommunications and information exchange between systems – High level data link control (HDLC) procedures – Elements of procedures*. +- [8] ISO/IEC 7809 (1993), *Information technology – Telecommunication and information exchange between systems – High level data link control (HDLC) procedures – Classes of procedures*. +- [9] ITU-T Recommendation X.212 (1995) | ISO/IEC 8886: 1996, *Information technology – Open Systems Interconnection – Data link service definition*. +- [10] ITU-T Recommendation E.164 (1997), *The international public telecommunication numbering plan*. +- [11] ITU-T Recommendation H.324 (2002), *Terminal for low bit-rate multimedia communication*. +- [12] ITU-T Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*. +- [13] ITU-T Recommendation I.420 (1988), *Basic user-network interface*. +- [14] ITU-T Recommendation I.460 (1999), *Multiplexing, rate adaptation and support of existing interfaces*. +- [15] ITU-T Recommendation X.30/I.461 (1993), *Support of X.21, X.21 bis and X.20 bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN)*. +- [16] ITU-T Recommendation X.31/I.462 (1995), *Support of packet mode terminal equipment by an ISDN*. +- [17] ITU-T Recommendation V.110/I.463 (2000), *Support by an ISDN of data terminal equipments with V-Series type interfaces*. +- [18] ITU-T Recommendation Q.65 (2000), *The unified functional methodology for the characterization of services and network capabilities including alternative object oriented techniques*. + +- [19] ITU-T Recommendation Q.920 (1993), *ISDN user-network interface data link layer – General aspects.* +- [20] ITU-T Recommendation Q.921 (1997), *ISDN user-network interface – Data link layer specification.* +- [21] ITU-T Recommendation Q.921 bis (1993), *Abstract test suite for LAPD conformance testing.* +- [22] ITU-T Recommendation Q.922 (1992), *ISDN data link layer specification for frame mode bearer services.* +- [23] ITU-T Recommendation Q.1214 (1995), *Distributed functional plane for intelligent network CS-1.* +- [24] ITU-T Recommendation T.31 (1995), *Asynchronous facsimile DCE control – Service Class 1.* +- [25] ITU-T Recommendation T.32 (1995), *Asynchronous facsimile DCE control – Service Class 2.* +- [26] ITU-T Recommendation V.14 (1993), *Transmission of start-stop characters over synchronous bearer channels.* +- [27] ITU-T Recommendation V.21 (1988), *300 bits per second duplex modem standardized for use in the general switched telephone network.* +- [28] ITU-T Recommendation 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.* +- [29] ITU-T Recommendation 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.* +- [30] ITU-T Recommendation V.24 (2000), *List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE).* +- [31] ITU-T Recommendation V.25 bis (1996), *Synchronous and asynchronous automatic dialling procedures on switched networks.* +- [32] ITU-T Recommendation V.25 ter (1997), *Serial asynchronous automatic dialling and control.* +- [33] ITU-T Recommendation 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.* +- [34] ITU-T Recommendation 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.* +- [35] ITU-T Recommendation V.80 (1996), *In-band DCE control and synchronous data modes for asynchronous DTE.* +- [36] ITU-T Recommendation V.250 (1999), *Serial asynchronous automatic dialling and control.* +- [37] ITU-T Recommendation X.21 bis (1988), *Use on public data networks of Data Terminal Equipment (DTE) which is designed for interfacing to synchronous V-Series modems.* + +- [38] 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.* +- [39] ITU-T Recommendation 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.* +- [40] TIA IS-99 (1998), *Telecommunications Industry Association TIA IS-99: Data Services Option Standard for Wideband Spread Spectrum Digital Cellular System.* +- [41] TIA IS-135 (1998), *Telecommunications Industry Association TIA IS-135: 800 MHz Cellular Systems, TDMA Services, Async Data and Fax.* +- [42] TIA IS-617 (1996), *Data Transmission Systems and Equipment – In Band DCE Control.* +- [43] ISO/IEC 7498 (1994), *Information processing systems – Open Systems Interconnection – Basic Reference Model.* +- [44] ITU-T Recommendation H.323 (2000), *Packet-based multimedia communications systems.* + +## 2.2 Informative references + +- [45a] ETSI TR 121.905 v.3.2.0 (2000), *3G Vocabulary.* +- [45b] ARIB TD-3GA-21.905(R99) v.3.2.0 (2000), *3G Vocabulary.* +- [45c] TTA TTAE.3G-21905 v.3.2.0 (2000), *3G Vocabulary.* + +# 3 Definitions + +The text is based on references [45a]-[45c]. + +This Recommendation defines the following terms: + +- 3.1 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.2 basic telecommunication service:** This term is used as a common reference to both bearer services and teleservices. +- 3.3 bearer:** An information transmission path of defined capacity, delay and bit error rate, etc. +- 3.4 bearer capability:** A transmission function that the UE requests to the network. +- 3.5 bearer service:** A type of telecommunication service that provides the capability of transmission of signals between access points. +- 3.6 call Detail 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.7 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.8 cipher key:** A code used in conjunction with a security algorithm to encode and decode user and/or signalling data. + +- 3.9 closed user group:** A group with a predefined set of members. Only defined members may participate in a closed user group. +- 3.10 handover:** The transfer of a user's connection from one radio channel to another (can be the same or different cell). +- 3.11 home environment:** The home environment is responsible for enabling a user to obtain UMTS services in a consistent manner regardless of the user's location or terminal used (within the limitations of the serving network and current terminal). +- 3.12 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.13 IC Card:** A card holding an Integrated Circuit containing subscriber, end user, authentication and/or application data for one or more applications. +- 3.14 interface:** The common boundary between two associated systems. +- 3.15 International Mobile Station Equipment Identity (IMEI):** An "International Mobile Station Equipment Identity" is a unique number that shall be allocated to each individual mobile station equipment in the PLMN and shall be unconditionally implemented by the Mobile Station (MS) manufacturer. +- 3.16 Iu:** Interconnection point between an RNC and a Core Network. It is also considered as a reference point. +- 3.17 Iub:** Interface between an RNC and a node B. +- 3.18 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.19 MExE server:** A node supporting MExE services in the MExE service environment. +- 3.20 MExE service:** A service enhanced (or made possible) by MExE technology. +- 3.21 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.22 mobile number portability:** The ability for a mobile subscriber to change subscription network within the same country whilst retaining their original MSISDN(s). +- 3.23 Mobile Station (MS):** See user equipment. +- 3.24 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.25 open service architecture:** Concept for introducing a vendor independent means for introduction of new services. +- 3.26 OSA interface:** Standardized Interface used by application/clients to access service capability features. +- 3.27 performance:** The ability to track service and resource usage levels and to provide feedback on the responsiveness and reliability of the network. + +**3.28 PLMN area:** The PLMN area is 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 border coverage is minimised in adjacent countries unless otherwise agreed. + +**3.29 public land mobile network:** A telecommunications network providing mobile cellular services. + +**3.30 quality of service:** The collective effect of service performance which determine the degree of satisfaction of a user of a service. It is characterised by the combined aspects of performance factors applicable to all services, such as; + +- Service operability performance; +- Service accessibility performance; +- Service retain ability performance; +- Service integrity performance; and +- Other factors specific to each service. + +**3.31 roaming:** The ability for a user to function in a serving network different from the home network. + +**3.32 security:** The ability to prevent fraud as well as the protection of information availability, integrity and confidentiality. + +**3.33 service capabilities:** Bearers defined by parameters, and/or mechanisms needed to realise services. These are within networks and under network control. + +**3.34 service capability feature:** Functionality offered by service capabilities that are accessible via the standardized application interface. + +**3.35 service capability server:** Network functionality providing open interfaces towards the functionality offered by UMTS service capabilities. + +**3.36 subscriber:** The responsibility for payment of charges incurrent by one or more users may be undertaken by another entity designated as a subscriber. This division between use of, and payment for, services has no impact on standardization. + +**3.37 supplementary service:** A service which modifies or supplements a basic telecommunication service. Consequently, it cannot be offered to a user as a standalone 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.38 telecommunication service:** That which is offered by a PLMN operator or service provider to its customers in order to satisfy a specific telecommunication requirement. Telecommunication services are divided into two broad families: bearer services and teleservices. + +**3.39 teleservice:** Is 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.40 Universal Mobile Telecommunications System (UMTS):** The telecommunications system, incorporating mobile cellular and other functionality, that is the subject of standards + +produced by Standardization Development Organization, that constitutes the 3G Partnership Project. + +**3.41 Universal Subscriber Identity Module (USIM):** An application residing on the Universal Integrated Circuit Card used for accessing services provided by mobile networks, which the application is able to register on with the appropriate security. + +**3.42 user:** An entity, not part of UMTS, which uses UMTS services. Example: a person using a UMTS mobile station as a portable telephone. + +**3.43 user equipment:** A device allowing a user access to network services. For the purpose of 3GPP specifications the interface between the UE and the network is the radio interface. A User Equipment can be subdivided into a number of domains, the domains being separated by reference points. Currently defined domains are the USIM and ME Domains. The ME Domain can further be subdivided into several components showing the connectivity between multiple functional groups. These groups can be implemented in one or more hardware devices. An example of such a connectivity is the TE-MT interface. Further, an occurrence of a User Equipment is an MS for GSM as defined TS 24.002. + +**3.44 virtual home environment:** A concept for personal service environment portability across network boundaries and between terminals. + +# **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 | +| ACELP | Algebraic Code Excited Linear Prediction | +| AID | Application Identifier | +| AMR | Adaptive Multi-Rate | +| ANSI | American National Standards Institute | +| AoC | Advice of Charge | +| AoCC | Advice of Charge (Charging) | +| AoCI | Advice of Charge (Information) | +| API | Application Programming Interface | +| ARIB | Association of Radio Industries and Business | +| ASE | Application Service Element | +| ASN.1 | Abstract Syntax Notation One | +| AT-command | ATtension Command | +| AuC | Authentication Centre | +| BAIC | Barring of All Incoming Call | +| BAOC | Barring of All Outgoing Call | +| BICC | Bearer Independent Call Control | +| BIC-Roam | Barring of Incoming Calls when Roaming outside the home PLMN country | + +| | | +|-----------|----------------------------------------------------------------------------------------| +| BOIC | Barring of Outgoing International Call | +| BOIC-exHC | Barring of Outgoing International Calls except those directed to the Home PLMN Country | +| BS | Base Station | +| BSC | Base Station Control | +| BSS | Base Station System | +| BSSMAP | Base Station System 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 | +| CD | Call Deflection | +| CDR | Call Detail Record | +| CF | Call Forwarding | +| CFB | Call Forwarding Busy | +| CFNRc | Call Forwarding on Terminal Not Reachable | +| CFNR | Call Forwarding on No Reply | +| CFU | Call Forwarding Unconditional | +| CLI | Calling Line Identity | +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| CM | Configuration Management | +| CMIP | Common Management Information Protocol | +| CMISE | Common Management Information Service Element | +| 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 | +| CS-1 | Capability Set 1 | +| CSE | CAMEL Service Environment | + +| | | +|---------|--------------------------------------------------------| +| CUG | Closed User Group | +| CW | Call Waiting | +| CWTS | China Wireless Telecommunications Standards Group | +| DCE | Data Circuit-terminating Equipment | +| DTE | Data Terminal Equipment | +| DTMF | Dual Tone Multi-Frequency | +| DTX | Discontinuous Transmission | +| ECT | Explicit Call Transfer | +| EGPRS | Enhanced GPRS | +| EIR | Equipment Identity Register | +| EM | Element Manager | +| eMLPP | enhanced Multi-Level Precedence and Preemption service | +| EN | European Norm | +| E-OTD | Enhanced Observed Time Difference | +| EP | Elementary Procedure | +| ETSI | European Telecommunications Standards Institute | +| FM | Fault Management | +| GAD | Geographical Area Description | +| GBS | General Bearer Services | +| GDMO | Guidelines for the Definition of Managed Objects | +| GERAN | GSM EDGE Radio Access Network | +| GGSN | Gateway GPRS Support Node | +| GLR | Gateway Location Register | +| GMLC | Gateway Mobile Location Centre | +| GMSC | Gateway MSC | +| 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 | +| 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 | +| ID | Identifier | +| IMEI | International Mobile Equipment Identity | +| IM-GSN | Intermediate GPRS Serving Node | +| IM-MSC | Intermediate Mobile-services Switching Centre | +| IMSI | International Mobile Station Identity | +| IN | Intelligent Network | +| INAP | Intelligent Network Application Protocol | +| IP | Internet Protocol | +| IPLMN | Interrogating PLMN | +| IrDA | Infrared Data Association | +| IrMC | Infrared Mobile Communications | +| IRP | Integration Reference Point | +| IS | Information Service | +| ISDN | Integrated Services Data Network | +| ISO | International Organization for Standardization | +| ISUP | ISDN User Part | +| Itf-N | Interface N | +| IWF | InterWorking Function | +| LAN | Local Area Network | +| LCS | Location Services | +| LMSI | Local Mobile Station Identity | +| LMU | Location Measurement Unit | +| LR | Location Request | +| MAP | Mobile Application Part | +| MC | Multicall | +| MCC | Mobile Country Code | +| ME | Mobile Equipment | +| MExE | Mobile station application Execution Environment | +| MIM | Management Information Model | +| MIME | Multipurpose Internet Mail Extensions | +| MLC | Mobile Location Centre | +| MM | Mobility Management | + +| | | +|---------|----------------------------------------------| +| MMI | Man-Machine Interface | +| MMS | Multimedia Messaging Service | +| MNC | Mobile Network Code | +| MNP | Mobile Number Portability | +| MO | Mobile Originated | +| MO-LR | Mobile Originated Location Request | +| MPTY | MultiParty | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MSISDN | Mobile Station International ISDN number | +| MSP | Multiple Subscriber Profile | +| MSRN | Mobile Station Roaming Number | +| MT | Mobile Terminal | +| MT | Mobile Termination | +| NE | Network Element | +| NITZ | Network Identity and Time Zone | +| NM | Network Management | +| NRM | Network Resource Model | +| OACSU | Off-Air Call Set-Up | +| ODB | Operator Determined Barring | +| OMG | Object Management Group | +| OS | Operations System | +| OSA | Open Service Architecture | +| OSI | Open System Interconnection | +| PBX | Private Branch eXchange | +| PCM | Pulse Code Modulation | +| 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 | +| PP | Point-to-Point | +| PS | Packet Switched | +| PSE | Personal Service Environment | +| PSTN | Public Switched Telephone Network | + +| | | +|---------|-----------------------------------------------------------------| +| RANAP | Radio Access Network Application Part | +| RID | Registered application provider Identifier | +| RLC/MAC | Radio Link Control/ Medium Access Control | +| RLP | Radio Link Protocol | +| RNC | Radio Network Controller | +| RNS | Radio Network System | +| RR | Radio Resources | +| SAT | SIM Application Toolkit | +| SC | Service Centre | +| SCCP | Signalling Connection Control Part | +| SCR | Source Controlled Rate | +| SCS | Service Capability Servers | +| SDO | Standards Development Organization | +| SGSN | Serving GPRS Support Node | +| SI | Screening Indicator | +| SID | Silence Descriptor | +| SIM | GSM Subscriber Identity Module | +| SIWF | Shared Interworking Function | +| SIWFS | Shared InterWorking Function Server | +| SM | Session Management | +| SMIL | Synchronized Multimedia Integration Language | +| SM-RL | Short Message Relay function | +| SMS | Short Message Service | +| SMSC | Short Message Service Center | +| SMSCB | Short Message Service Cell Broadcast | +| SMTP | Simple Mail Transfer Protocol | +| SOR | Support of Optimal Routing | +| SRNC | Serving Radio Network Controller | +| SRNS | Serving RNS | +| SS | Supplementary Service | +| SS | Solution Set | +| SS7 | Signalling System No. 7 | +| SSF | Service Switching Function | +| T1 | T1 Standardization Committee (part of ANSI) | +| T1P1 | Technical Subcommittee for wireless/Mobile Services and Systems | +| TA | Terminal Adaptation | +| TAF | Terminal Adaptation Function | + +| | | +|----------|---------------------------------------------------------------| +| T-BCSM | Terminating Basic Call State Model | +| TCAP | Transaction Capabilities | +| TCH/F | A full rate Traffic CHannel | +| 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 | +| TIA | Telecommunications Industry Association | +| TMSI | Temporary Mobile Station Identity | +| TOA | Time Of Arrival | +| TrFO | Transcoder Free Operation | +| TS | Technical Specification | +| TSG | Technical Specification Group | +| TTA | Telecommunication Technology Association (Korea) | +| TTC | Telecommunication Technology Committee (Japan) | +| TUP | Telephone User Part (SS7) | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UICC | Universal IC Card | +| UIM | User Identity Module | +| UMTS | Universal Mobile Telecommunication 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 "UMTS", is based on an evolved core network from the 2nd generation mobile system, GSM. 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 wide-band communications capability with integrated personal and terminal mobility to meet the user and service requirements. + +Release 1999 is the first 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 terrestrial usage based on GSM evolved UMTS core network with UTRAN access network + +Refer to 10.2.37 "UMTS Service principles" for more information. + +The description of the Technical Specifications listed in Clause 10 are for informative purposes only. Normative information is in the tables. + +# 6 Basic architecture for the UMTS IMT-2000 family member + +This text is based on references [2a]-[2e] section 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 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 Iubis are defined in the UMTS 25.4xx-series of Technical Specifications, which are outside the scope of this Recommendation. Interfaces C, D, E, F and G need the support of the Mobile Application Part of the 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 UMTS 23- and 24-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. + +![Diagram of a PLMN supporting CS and PS services and interfaces. The diagram shows the internal components of a Core Network (CN) and its interfaces to external and internal networks. CN components include GMSC, GGSN, HLR, EIR, MSC/VLR, and SGSN. External interfaces include PSTN (via GMSC), Gi (to GGSN), and Gp (to GGSN). Internal interfaces include C (GMSC-HLR), H (AuC-HLR), Gc (GGSN-HLR), Gn (GGSN-SGSN), Gr (HLR-SGSN), D (MSC/VLR-HLR), F (MSC/VLR-EIR), Gf (EIR-SGSN), Gs (MSC/VLR-SGSN), G (MSC/VLR-external MSC/VLR), and E (MSC/VLR-external MSC/VLR). The Radio Network Subsystem (RNS) contains an RNC connected to the CN via IuCS (to MSC/VLR) and IuPS (to SGSN). The RNC is also connected to another RNC via Iur and to two Node B cells via Iubis. Each Node B contains three cells. The User Equipment (UE) consists of a Mobile Equipment (ME) and a USIM connected via Cu. The ME connects to the Node B cells via the Uu interface. Bold lines represent user traffic interfaces, and dashed lines represent signalling interfaces.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +Diagram of a PLMN supporting CS and PS services and interfaces. The diagram shows the internal components of a Core Network (CN) and its interfaces to external and internal networks. CN components include GMSC, GGSN, HLR, EIR, MSC/VLR, and SGSN. External interfaces include PSTN (via GMSC), Gi (to GGSN), and Gp (to GGSN). Internal interfaces include C (GMSC-HLR), H (AuC-HLR), Gc (GGSN-HLR), Gn (GGSN-SGSN), Gr (HLR-SGSN), D (MSC/VLR-HLR), F (MSC/VLR-EIR), Gf (EIR-SGSN), Gs (MSC/VLR-SGSN), G (MSC/VLR-external MSC/VLR), and E (MSC/VLR-external MSC/VLR). The Radio Network Subsystem (RNS) contains an RNC connected to the CN via IuCS (to MSC/VLR) and IuPS (to SGSN). The RNC is also connected to another RNC via Iur and to two Node B cells via Iubis. Each Node B contains three cells. The User Equipment (UE) consists of a Mobile Equipment (ME) and a USIM connected via Cu. The ME connects to the Node B cells via the Uu interface. Bold lines represent user traffic interfaces, and dashed lines represent signalling interfaces. + +Q.1741.1 +F06-1 + +Bold lines      Interfaces supporting user traffic +Dashed lines    Interfaces supporting signalling + +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 – This is a simplified architecture figure. Not all nodes and interfaces are indicated. + +NOTE 3 – This figure differs from the original figure in reference [2a]–[2e]. This figure only shows the third generation aspects. + +**Figure 6-1/Q.1741.1 – Basic configuration of a PLMN supporting CS and PS services and interfaces** + +This text is based on text in references [2a]–[2e] section 5.2.2. + +The basic configuration of UMTS Location Services is presented in Figure 6-2. + +![Figure 6-2/Q.1741.1 – Configuration of location services entities in an UMTS PLMN. This diagram shows the network architecture for location services. At the top left, an 'LMU Type A' is connected to a 'UE' (User Equipment) via a 'Uu' interface. The 'UE' is connected to a 'Node B (LMU Type B)', which in turn connects to an 'SRNC (SMLC functionality)' via an 'Iub' interface. The 'SRNC' is connected to a '3G-SGSN' via an 'Iu' interface and to an 'RNC' via an 'Iur' interface. The 'RNC' is connected to another 'Node B (LMU Type B)' via an 'Iub' interface. The '3G-SGSN' is connected to a '3G-MSC/VLR' via an 'Lg' interface. The '3G-MSC/VLR' is connected to an 'HLR' via an 'Lh' interface and to a 'Gateway MLC' via an 'Lg' interface. The 'Gateway MLC' is connected to an 'External LCS client' via an 'Le' interface and to a 'gsmSCF' via an 'Lc' interface. A shaded oval labeled 'Other PLMN' contains a 'Gateway MLC' which is connected to the '3G-MSC/VLR' via an 'Lg' interface. A small text 'Q.1741.1 F06-2' is in the bottom right corner.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure 6-2/Q.1741.1 – Configuration of location services entities in an UMTS PLMN. This diagram shows the network architecture for location services. At the top left, an 'LMU Type A' is connected to a 'UE' (User Equipment) via a 'Uu' interface. The 'UE' is connected to a 'Node B (LMU Type B)', which in turn connects to an 'SRNC (SMLC functionality)' via an 'Iub' interface. The 'SRNC' is connected to a '3G-SGSN' via an 'Iu' interface and to an 'RNC' via an 'Iur' interface. The 'RNC' is connected to another 'Node B (LMU Type B)' via an 'Iub' interface. The '3G-SGSN' is connected to a '3G-MSC/VLR' via an 'Lg' interface. The '3G-MSC/VLR' is connected to an 'HLR' via an 'Lh' interface and to a 'Gateway MLC' via an 'Lg' interface. The 'Gateway MLC' is connected to an 'External LCS client' via an 'Le' interface and to a 'gsmSCF' via an 'Lc' interface. A shaded oval labeled 'Other PLMN' contains a 'Gateway MLC' which is connected to the '3G-MSC/VLR' via an 'Lg' interface. A small text 'Q.1741.1 F06-2' is in the bottom right corner. + +**Figure 6-2/Q.1741.1 – Configuration of location services entities in an UMTS PLMN** + +This text is based on text in references [2a]-[2e] sections 4a.4 and 5.3. + +The CAMEL feature (Customized Applications for Mobile network Enhanced Logic) provides the mechanisms to support services consistently independently of the serving network. + +Figure 6-3 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 and HLR interfaces depicted in Figure 6-3 are still supported by these entities even if not shown. + +NOTE – The 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-3/Q.1741.1 – Configuration of CAMEL entities. This diagram shows the interconnection of CAMEL-specific entities. At the top, a 'GMSC' is connected to a 'gsmSSF'. The 'gsmSSF' is connected to a 'gsmSCF' via an interface labeled 'C'. The 'gsmSCF' is connected to an 'HLR' via an interface labeled 'D'. The 'HLR' is connected to a 'gprsSSF' via an interface labeled 'Gr'. The 'gsmSCF' is also connected to a 'gsmSRF'. The 'gsmSRF' is connected to an 'MSC' via an interface labeled 'B'. The 'MSC' is connected to a 'VLR'. The 'gprsSSF' is connected to an 'SGSN'. A small text 'Q.1741.1 F06-03' is in the bottom right corner.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +Figure 6-3/Q.1741.1 – Configuration of CAMEL entities. This diagram shows the interconnection of CAMEL-specific entities. At the top, a 'GMSC' is connected to a 'gsmSSF'. The 'gsmSSF' is connected to a 'gsmSCF' via an interface labeled 'C'. The 'gsmSCF' is connected to an 'HLR' via an interface labeled 'D'. The 'HLR' is connected to a 'gprsSSF' via an interface labeled 'Gr'. The 'gsmSCF' is also connected to a 'gsmSRF'. The 'gsmSRF' is connected to an 'MSC' via an interface labeled 'B'. The 'MSC' is connected to a 'VLR'. The 'gprsSSF' is connected to an 'SGSN'. A small text 'Q.1741.1 F06-03' is in the bottom right corner. + +**Figure 6-3/Q.1741.1 – Configuration of CAMEL entities** + +This text is based on text in references [2a]-[2e] section 5.3. + +The bold lines are used for interfaces supporting user data only; the dashed lines are used for interfaces supporting signalling only. + +This text is based on text in references [2a]-[2e] section 4.a.4.5. + +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. + +![Diagram showing the configuration of a PLMN supporting cell broadcast service entities. A dashed box labeled 'CN' contains a 'CBC' entity. A solid line labeled 'IuBC' connects 'CBC' to an 'RNC' inside a dashed box labeled 'RNS'. The 'RNC' is connected to two 'Node B' entities by dashed lines labeled 'Iub'. A zigzag line connects one 'Node B' to a 'UE' entity. The text 'Q.1741.1 F06-4' is in the bottom right corner.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` +graph TD + subgraph CN + CBC + end + subgraph RNS + RNC + NB1[Node B] + NB2[Node B] + RNC -.-> NB1 + RNC -.-> NB2 + end + CBC -- IuBC --> RNC + NB1 -.-> UE + style CBC fill:none,stroke:none + style RNC fill:none,stroke:none + style NB1 fill:none,stroke:none + style NB2 fill:none,stroke:none + style UE fill:none,stroke:none +``` + +Diagram showing the configuration of a PLMN supporting cell broadcast service entities. A dashed box labeled 'CN' contains a 'CBC' entity. A solid line labeled 'IuBC' connects 'CBC' to an 'RNC' inside a dashed box labeled 'RNS'. The 'RNC' is connected to two 'Node B' entities by dashed lines labeled 'Iub'. A zigzag line connects one 'Node B' to a 'UE' entity. The text 'Q.1741.1 F06-4' is in the bottom right corner. + +**Figure 6-4/Q.1741.1 – Configuration of a PLMN supporting cell broadcast service entities** + +This text is based on text in references [2a]-[2e] Annex A. + +Gateway Location Register (GLR) is an optional functional entity to optimize signalling traffic between PLMNs. This entity handles location management of roaming subscriber in 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-5, all the functions related to GLR introduction is 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 the 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 GPRS Tunnelling Protocol – Control to provide the packet domain services. + +![Diagram showing the configuration of a PLMN and interfaces with GLR. The diagram includes various network entities: SGSN, VLR/MSC, IM-GSN, GLR, IM-SC, GGSN, HLR, SMS-GMSC, and GMLC. Interfaces are labeled GLk, GLc, GLb, GLh, GLe, GLd, GLj, GLa, GLg, GLi, and GLf. A legend indicates that dotted lines represent signalling interfaces and solid lines represent user traffic interfaces. The diagram is labeled Q.1741.1 F06-5.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +The diagram illustrates the network architecture and interfaces within a PLMN. At the top, SGSN and VLR/MSC are shown. SGSN connects to IM-GSN via GLk (user traffic) and GLc (signalling). VLR/MSC connects to IM-SC via GLh (user traffic) and GLb (signalling). IM-GSN connects to GLR via GLe (signalling) and GLj (user traffic). IM-SC connects to GLR via GLd (signalling) and GLg (user traffic). GLR connects to GGSN via GLa (signalling), to HLR via GLf (signalling), and to SMS-GMSC via GLi (signalling). All these entities (GGSN, HLR, SMS-GMSC, GMLC) are part of the 'Other PLMN'. A legend at the bottom left defines the line types: dotted for signalling and solid for user traffic, noting that user traffic includes Short Messages. The diagram is identified by Q.1741.1 F06-5 in the bottom right. + +Diagram showing the configuration of a PLMN and interfaces with GLR. The diagram includes various network entities: SGSN, VLR/MSC, IM-GSN, GLR, IM-SC, GGSN, HLR, SMS-GMSC, and GMLC. Interfaces are labeled GLk, GLc, GLb, GLh, GLe, GLd, GLj, GLa, GLg, GLi, and GLf. A legend indicates that dotted lines represent signalling interfaces and solid lines represent user traffic interfaces. The diagram is labeled Q.1741.1 F06-5. + +**Figure 6-5/Q.1741.1 – 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 references [2a]-[2e] section 4.1.2.2. + +The Mobile Switching Center (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). + +## 7.2 Mobile Switching Centre and Visitor Location Register MSC/VLR (MSC/VLR) + +### 7.2.1 Mobile Switching Centre (MSC) + +The text in this clause is based on references [2a]-[2e] section 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 base stations are normally required; i.e. each MSC would thus have to interface several base stations. In addition, several MSCs may be required to cover a country. + +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. 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. + +### 7.2.2 Visitor Location Register (VLR) + +The text in this clause is based on references [2a]-[2e] section 4.1.1.2. + +A mobile station roaming in an MSC area is controlled by the Visitor Location Register 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 also contains the information needed to handle the calls set up or received by the MSs registered in its data base (for some supplementary services, the VLR may have to obtain additional information from the HLR). The following elements are included: + +- The International Mobile Station 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 Location Register (HLR) + +The text in this clause is based on references [2a]-[2e] section 4.1.1.1. + +The Home Location Register (HLR) is a database in charge of the management of mobile subscribers. A PLMN may contain one or several HLRs: it depends on the number of mobile subscribers, on the capacity of the equipment and on the organization of the network. The following kinds of information are stored there: + +- The subscription information; +- Some location information enabling the charging and routing of calls towards the MSC where the MS is registered (e.g. the MS Roaming Number, the VLR Number, the MSC Number, the Local MS Identity); + +and, if GPRS is supported, also: + +- Location information enabling the charging and routing of messages in the SGSN where the MS is currently registered (e.g. the SGSN Number); + +and, if LCS is supported, also: + +- A LCS privacy exception list, which indicates the privacy class of the MS subscriber; +- A GMLC list; +- A MO-LR list. + +Different types of identity are attached to each mobile subscription and are stored in the HLR. The following identities are stored: + +- The International Mobile Station Identity (IMSI); +- One or more Mobile Station International ISDN number(s) (MSISDN); + +If GPRS is supported, the following identity is also stored: + +- Zero or more Packet Data Protocol (PDP) address(es); + +and, if LCS is supported, the following identity is also stored: + +- The LMU indicator. + +There is always at least one identity, apart from the IMSI, attached to each mobile subscription and stored in the HLR. + +The IMSI or the MSISDN may be used as a key to access the information in the database for a mobile subscription. + +The database contains other information such as: + +- Teleservices and bearer services subscription information; +- Service restrictions (e.g. roaming limitation); +- A list of all the group IDs a service subscriber is entitled to use to establish voice group or broadcast calls; +- Supplementary services; the HLR contains the parameters attached to these services; + +and, if GPRS is supported, also: + +- Information about if a GGSN is allowed to dynamically allocate PDP addresses for a subscriber. + +## 7.4 Authentication Centre (AuC) + +The text in this clause is based on references [2a]-[2e] section 4.1.1.3. + +The Authentication Centre (AuC) is an entity that stores data for each mobile subscriber to allow the International Mobile Subscriber Identity (IMSI) to be authenticated and to allow communication over the radio path between the mobile station and the network to be ciphered. The AuC transmits the data needed for authentication and ciphering via the HLR to the VLR, MSC and SGSN which need to authenticate a mobile station. + +The Authentication Centre (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: + +- Data that are used to authenticate the International Mobile Subscriber Identity (IMSI); +- 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 an interface denoted the H-interface (see 8.28). + +## 7.5 Equipment Identity Register (EIR) + +The text in this clause is based on references [2a]-[2e] section 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.6 Gateway GPRS Support Node (GGSN)** + +The text in this clause is based on references [2a]-[2e] sections 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.7 Serving GPRS Support Node (SGSN)** + +The text in this clause is based on references [2a]-[2e] sections 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 routing 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.8 Gateway Mobile Location Centre (GMLC)** + +The text in this clause is based on references [2a]-[2e] section 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.9 GPRS Service Switching Function (gprsSSF)** + +This text is based on text in references [2a]-[2e] section 4a.4.4. + +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.10 GSM Service Control Function (gsmSCF)** + +This text is based on text in references [2a]-[2e] section 4a.4.1. + +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.11 GSM Service Switching Function (gsmSSF)** + +This text is based on text in references [2a]-[2e] section 4a.4.2. + +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.12 GSM Specialised Resource Function (gsmSRF)** + +This text is based on text in references [2a]-[2e] section 4a.4.3. + +A functional entity, which provides various specialized resources. It interfaces with the gsmSCF and with the MSC. This entity is defined in ITU-T Rec. Q.1214 [23] with variations defined in TS 23.078 (see 10.3.25). + +## **7.13 Gateway Location Register (GLR)** + +The text in this clause is based on references [2a]-[2e] Annex 2. + +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 routing information for both CS services and PS services. This entity can be only located in a visited PLMN. The GLR is an optional functional entity to optimize signalling traffic between PLMNs. + +## **7.14 Intermediate GPRS Serving Node (IM-GSN)** + +The text in this clause is based on references [2a]-[2e] Annex 2. + +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 only located in a visited PLMN. + +## **7.15 Intermediate Mobile-services Switching Centre (IM-MSC)** + +The text in this clause is based on references [2a]-[2e] Annex 2. + +The Intermediate Mobile-services Switching Centre (IM-MSC) is used as serving MSC towards home network and relay some messages between home network and serving MSC. This entity can only be located in a visited PLMN. + +# 8 Interfaces + +## 8.1 C-Interface (Gateway Mobile Switching Centre (GMSC) – Home Location Register (HLR)) + +The text in this clause is based on the text in references [2a]-[2e] section 6.4.1.2. + +The Gateway MSC must interrogate the HLR of the required subscriber to obtain routing 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 Applications for Mobile network Enhanced Logic (CAMEL) purposes, this interface is used e.g. at terminating calls to exchange routing 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 [2a]-[2e] section 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 Applications 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 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 (MSC) – Mobile Switching Centre (MSC)) + +The text in this clause is based on the text in references [2a]-[2e] section 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 MSCs have to exchange data to initiate and then to realise the operation. + +After the handover operation has been completed, the MSCs will exchange information to transfer A-interface signalling as necessary. + +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 serving the Mobile Station and the MSC, 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. + +## **8.4 F Interface (Mobile Switching Centre (MSC) – Equipment Identity Register (EIR))** + +The text in this clause is based on the text in references [2a]-[2e] section 6.4.1.5. + +This interface is used between MSC 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 Gi Interface (Gateway GPRS Support Node (GGSN) – Public Network)** + +The text in this clause is based on the text in references [2a]-[2e] section 7.2. + +This interface connects the PLMN to external public or private packet data networks. + +## **8.9 GLa Interface (Gateway Location Register (GLR) – Home Location Register (HLR))** + +The text in this clause is based on the text in references [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 that 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) – Public Network)** + +The text in this clause is based on the text in references [2a]-[2e] section 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 [2a]-[2e] section 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 [2a]-[2e] section 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 UE 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** + +This text is based on text in references [2a]-[2e] section 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** + +This text is based on text in references [2a]-[2e] section 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** + +This text is based on text in references [2a]-[2e] section 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** + +This text is based on text in references [2a]-[2e] section 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 [2a]-[2e] section 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 (Core Network (CN) – Radio Network Controller (RNC))** + +The text in this clause is based on the text in references [2a]-[2e] section 6a.5.1. + +The 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) – Radio Network Controller (RNC))** + +The text in this clause is based on the text in references [2a]-[2e] section 6.2.1.2. + +The interface between the MSC and its RNS 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) – Radio Network Controller (RNC))** + +The text in this clause is based on the text in references [2a]-[2e] section 6.2.2.2. + +The RNS-3G-SGSN interface is used to carry information concerning: + +- Packet data transmission; +- Mobility management. + +The IuPS interface is defined in the 25.41x-series of UMTS Technical Specifications. + +## **8.32 Lc Interface (Gateway Mobile Location Centre (GMLC) – GSM Service Control Function (gsmSCF))** + +The text in this clause is based on the text in references [3a]-[3e] section 6.3.10. + +The Lc interface supports CAMEL access to LCS. + +## **8.33 Le Interface (Gateway Mobile Location Centre (GMLC) – External LCS client)** + +The text in this clause is base on the text in references [2a]-[2e] section 7.3. + +This interface connects the PLMN to the external LCS Client. + +## **8.34 Lg Interface (Mobile Switching Centre (MSC)/Visitor Location Register (VLR) – Mobile Location Centre (MLC))** + +The text in this clause is based on the text in references [2a]-[2e] section 6a.3.1. + +The MSC-GMLC interface is used to exchange data needed by the MSC to perform subscriber authorization and allocate network resources. The GMLC provides the IMSI and requested Quality of Service information. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (TCAP). + +## **8.35 Lh Interface (Home Location Register (HLR) – Gateway Mobile Location Centre (GMLC))** + +The text in this clause is based on the text in references [2a]-[2e] section 6a.3.4. + +This interface is used by the GMLC to retrieve the VMSC location and IMSI for a particular mobile. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (TCAP). + +## **8.36 Mobile Switching Centre (MSC) – gsmSCF Interface** + +This text is based on text in references [2a]-[2e] section 6a.4.6 + +This interface is used by the MSC to send supplementary service invocation notifications to the gsmSCF. + +## **8.37 PSTN Interface (Mobile Switching Centre (MSC)/Visitor Location Register (VLR) – Public Switching Telephone Network (PSTN))** + +The text in this clause is based on the text in references [2a]-[2e] section 7.1. + +The MSC is based on a normal ISDN exchange. It has, for call control, the same interface as the fixed network exchanges. The signalling interface considered in the GSM 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. + +# **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 with UTRAN 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 3GPP 3rd Generation Mobile System. + +Specifications for Release 1999 of the 3rd Generation mobile system are identified by the "ab.cde" numbering scheme. + +Where existing GSM Specifications are enhanced or modified by the TSGs for the 3rd Generation Mobile System, the specification title and version should change (title reflecting 3rd Generation Mobile System). The GSM number (ab) has increased by 20 and a "c" digit equal to zero added (e.g., GSM 07.07 becomes 3GTS 27.007) indicating the GSM heritage of the Specification. Table 1 is a conversion table between specifications on the second generation GSM system and specifications in the third generation UMTS system. + +For newly created 3GPP Specifications the "c" digit is not zero. + +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 (see Note 1); | +| 26-series | Codecs (speech, video, etc.); | +| 27-series | Data; | +| 28-series | Reserved for future use; | +| 29-series | Signalling protocols; | +| 30-series | Programme management (see Note 2); | +| 31-series | User Identity Module (UIM); | +| 32-series | Operation and maintenance; | +| 33-series | Security aspects; | +| 34-series | Test specifications (see Note 2); | +| 35-series | Algorithm specifications. | + +NOTE 1 – Technical specifications in this series are not included in the scope of this Recommendation. They are described in reference [1]. + +NOTE 2 – Technical specifications in these series are not included in the scope of this Recommendation. + +**Table 1/Q.1741.1 – Conversion between 2G and 3G** + +| GSM Number | 3G Spec. Number | Title | +|-------------------|------------------------|---------------------------------------------------------------------------------------------------| +| 01.01 | 21.101 | 3rd Generation mobile system Release 1999 Specifications | +| 01.11 | 21.111 | USIM and IC card requirements | +| 01.33 | 21.133 | Security threats and requirements | +| 02.00 | 22.100 | UMTS Phase 1 | +| 02.01 | 22.001 | Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) | +| 02.01 | 22.101 | Service aspects; Service principles | +| 02.02 | 22.002 | Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) | +| 02.03 | 22.003 | Circuit Teleservices supported by a Public Land Mobile Network (PLMN) | +| 02.04 | 22.004 | General on Supplementary Services | +| 02.05 | 22.105 | Services & service capabilities | +| 02.11 | 22.011 | Service accessibility | +| 02.15 | 22.115 | Service Aspects Charging and billing | +| 02.16 | 22.016 | International Mobile Equipment Identities (IMEI) | +| 02.21 | 22.121 | Service aspects; The Virtual Home Environment; Stage 1 | + +**Table 1/Q.1741.1 – Conversion between 2G and 3G** + +| GSM Number | 3G Spec. Number | Title | +|-------------------|------------------------|------------------------------------------------------------------------------| +| 02.22 | 22.022 | Personalization of Mobile Equipment (ME); Mobile functionality specification | +| 02.24 | 22.024 | Description of Charge Advice Information (CAI) | +| 02.29 | 22.129 | Handover Requirements between UMTS and GSM or other Radio Systems | +| 02.30 | 22.030 | Man-Machine Interface (MMI) of the User Equipment (UE) | +| 02.34 | 22.034 | High Speed Circuit Switched Data (HSCSD); Stage 1 | +| 02.35 | 22.135 | Multicall; Stage 1 | +| 02.38 | 22.038 | USIM/SIM Application Toolkit (USAT/SAT); Service description; Stage 1 | +| 02.40 | 22.140 | Multimedia Messaging Service; Stage 1 | +| 02.41 | 22.041 | Operator Determined Call Barring | +| 02.42 | 22.042 | Network Identity and Time Zone (NITZ); Stage 1 | +| 02.57 | 22.057 | Mobile Execution Environment (MExE); Stage 1 | +| 02.60 | 22.060 | General Packet Radio Service (GPRS); Stage 1 | +| 02.66 | 22.066 | Support of Mobile Number Portability (MNP); Stage 1 | +| 02.67 | 22.067 | Enhanced Multi-Level Precedence and Preemption service (eMLPP); Stage 1 | +| 02.71 | 22.071 | Location Services (LCS); Stage 1 | +| 02.72 | 22.072 | Call Deflection (CD); Stage 1 | +| 02.78 | 22.078 | CAMEL; Stage 1 | +| 02.79 | 22.079 | Support of optimal routing; Stage 1 | +| 02.81 | 22.081 | Line Identification supplementary services; Stage 1 | +| 02.82 | 22.082 | Call Forwarding (CF) supplementary services; Stage 1 | +| 02.83 | 22.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 1 | +| 02.84 | 22.084 | MultiParty (MPTY) supplementary services; Stage 1 | +| 02.85 | 22.085 | Closed User Group (CUG) supplementary services; Stage 1 | +| 02.86 | 22.086 | Advice of Charge (AoC) supplementary services; Stage 1 | +| 02.87 | 22.087 | User-to-user signalling (UUS); Stage 1 | +| 02.88 | 22.088 | Call Barring (CB) supplementary services; Stage 1 | +| 02.90 | 22.090 | Unstructured Supplementary Service Data (USSD); Stage 1 | +| 02.91 | 22.091 | Explicit Call Transfer (ECT) supplementary service; Stage 1 | +| 02.93 | 22.093 | Call Completion to Busy Subscriber (CCBS); Stage 1 | +| 02.94 | 22.094 | Follow Me service description; Stage 1 | +| 02.96 | 22.096 | Name identification supplementary services; Stage 1 | +| 02.97 | 22.097 | Multiple Subscriber Profile (MSP); Stage 1 | +| 03.01 | 23.101 | General UMTS Architecture | +| 03.02 | 23.002 | Network Architecture | +| 03.03 | 23.003 | Numbering, Addressing and Identification | +| 03.07 | 23.007 | Restoration procedures | +| 03.07 | 23.107 | Quality of Service (QoS) concept and architecture | +| 03.08 | 23.008 | Organization of subscriber data | + +**Table 1/Q.1741.1 – Conversion between 2G and 3G** + +| GSM Number | 3G Spec. Number | Title | +|-------------------|------------------------|------------------------------------------------------------------------------------------------------| +| 03.08 | 23.108 | Mobile Radio Interface Layer 3 specification Core Network Protocols; Stage 2 (structured procedures) | +| 03.09 | 23.009 | Handover procedures | +| 03.10 | 23.110 | UMTS Access Stratum services and functions | +| 03.11 | 23.011 | Technical realization of supplementary services | +| 03.12 | 23.012 | Location management procedures | +| 03.14 | 23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | +| 03.15 | 23.015 | Technical realization of Operator Determined Barring (ODB) | +| 03.16 | 23.016 | Subscriber data management; Stage 2 | +| 03.16 | 23.116 | Super-Charger technical realization; Stage 2 | +| 03.18 | 23.018 | Basic Call Handling; Technical realization | +| 03.19 | 23.119 | Gateway Location Register (GLR); Stage2 | +| 03.21 | 23.121 | Architecture Requirements for release 99 | +| 03.22 | 23.122 | Non-Access-Stratum functions related to Mobile Station (MS) in idle mode | +| 03.27 | 23.127 | Virtual Home Environment; Stage 2 | +| 03.32 | 23.032 | Universal Geographical Area Description (GAD) | +| 03.34 | 23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | +| 03.35 | 23.135 | Multicall supplementary service; Stage 2 | +| 03.38 | 23.038 | Alphabets and Language | +| 03.40 | 23.040 | Technical realization of Short Message Service (SMS) | +| 03.40 | 23.140 | Multimedia Messaging Service (MMS) | +| 03.41 | 23.041 | Technical realization of Cell Broadcast Service (CBS) | +| 03.42 | 23.042 | Compression algorithm for SMS | +| 03.54 | 23.054 | Shared Interworking Functions; Stage 2 | +| 03.57 | 23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | +| 03.60 | 23.060 | General Packet Radio Service (GPRS) Service description; Stage 2 | +| 03.66 | 23.066 | Support of GSM Mobile Number Portability (MNP); Stage 2 | +| 03.67 | 23.067 | Enhanced Multi-Level Precedence and Preemption Service (eMLPP); Stage 2 | +| 03.71 | 23.171 | Functional stage 2 description of location services in UMTS | +| 03.72 | 23.072 | Call Deflection supplementary service; Stage 2 | +| 03.78 | 23.078 | Customized Applications for Mobile network Enhanced Logic (CAMEL) – Phase 3; Stage 2 | +| 03.79 | 23.079 | Support of Optimal Routing (SOR) Technical realization; Stage 2 | +| 03.81 | 23.081 | Line Identification supplementary services; Stage 2 | +| 03.82 | 23.082 | Call Forwarding (CF) supplementary services; Stage 2 | +| 03.83 | 23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary service; Stage 2 | +| 03.84 | 23.084 | MultiParty (MPTY) supplementary service; Stage 2 | +| 03.85 | 23.085 | Closed User Group (CUG) supplementary service; Stage 2 | +| 03.86 | 23.086 | Advice of Charge (AoC) supplementary service; Stage 2 | + +**Table 1/Q.1741.1 – Conversion between 2G and 3G** + +| GSM Number | 3G Spec. Number | Title | +|-------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 03.87 | 23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | +| 03.88 | 23.088 | Call Barring (CB) supplementary service; Stage 2 | +| 03.90 | 23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | +| 03.91 | 23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | +| 03.93 | 23.093 | Completion of Calls to Busy Subscriber (CCBS); Stage 2 | +| 03.94 | 23.094 | Follow Me; Stage 2 | +| 03.96 | 23.096 | Name Identification Supplementary Service; Stage 2 | +| 03.97 | 23.097 | Multiple Subscriber Profile (MSP); Stage 2 | +| 04.02 | 24.002 | GSM-UMTS Public Land Mobile Network (PLMN) access reference configuration | +| 04.07 | 24.007 | Mobile Radio Interface Signalling Layer 3 – General Aspects | +| 04.08 | 24.008 | Mobile Radio Interface Layer 3 specification; Core network protocols; Stage 3 | +| 04.10 | 24.010 | Mobile Radio Interface Layer 3 – Supplementary Services Specification – General Aspects | +| 04.11 | 24.011 | Point-to-Point (PP) Short Message Service (SMS) Support on Mobile Radio Interface | +| 04.12 | 24.012 | Short Message Service Cell Broadcast (SMSCB) Support on the Mobile Radio Interface | +| 04.22 | 24.022 | Radio Link Protocol (RLP) for Data and Telematic Services on the (MS-BSS) Interface and the Base Station System – Mobile-services Switching Centre (BSS-MSC) Interface | +| 04.30 | 24.030 | Location Services LCS Stage 3 SS (MO-LR) | +| 04.35 | 24.135 | Multicall supplementary service; Stage 3 | +| 04.67 | 24.067 | Enhanced Multi-Level Precedence and Preemption service (eMLPP); Stage 3 | +| 04.72 | 24.072 | Call Deflection supplementary service; Stage 3 | +| 04.80 | 24.080 | Mobile radio layer 3 supplementary service specification – Formats and coding | +| 04.81 | 24.081 | Line Identification supplementary service; Stage 3 | +| 04.82 | 24.082 | Call Forwarding supplementary service; Stage 3 | +| 04.83 | 24.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary service; Stage 3 | +| 04.84 | 24.084 | MultiParty (MPTY) supplementary service; Stage 3 | +| 04.85 | 24.085 | Closed User Group (CUG) supplementary service; Stage 3 | +| 04.86 | 24.086 | Advice of Charge (AoC) supplementary service; Stage 3 | +| 04.87 | 24.087 | User-to-User Signalling (UUS); Stage 3 | +| 04.88 | 24.088 | Call Barring (CB) supplementary service; Stage 3 | +| 04.90 | 24.090 | Unstructured Supplementary Service Data (USSD); Stage 3 | +| 04.91 | 24.091 | Explicit Call Transfer (ECT) supplementary service; Stage 3 | +| 04.93 | 24.093 | Completion of Calls to Busy Subscriber (CCBS); Stage 3 | +| 04.96 | 24.096 | Name Identification supplementary service; Stage 3 | +| 06.01 | 26.101 | AMR speech codec; Frame structure | +| 06.02 | 26.102 | AMR speech codec; Interface to Iu and Uu | + +**Table 1/Q.1741.1 – Conversion between 2G and 3G** + +| GSM Number | 3G Spec. Number | Title | +|-------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 06.03 | 26.103 | Codec lists | +| 06.04 | 26.104 | AMR speech codec; Floating point C-Code | +| 06.10 | 26.110 | Codec for circuit switched Multimedia Telephony Service; General description | +| 06.11 | 26.111 | Codec for circuit switched Multimedia Telephony Service; Modifications to ITU-T Rec. H.324 | +| 06.31 | 26.131 | Narrow-Band (3,1 kHz) Speech & Video Telephony Terminal Acoustic Characteristics | +| 06.32 | 26.132 | Narrow-Band (3,1 kHz) Speech & Video Telephony Terminal Acoustic Test Specification. | +| 06.71 | 26.071 | AMR speech codec; General description | +| 06.73 | 26.073 | AMR speech codec; C-source code | +| 06.74 | 26.074 | AMR speech codec; Test sequences | +| 06.90 | 26.090 | AMR speech codec; Transcoding functions | +| 06.91 | 26.091 | AMR speech codec; Error concealment of lost frames | +| 06.92 | 26.092 | AMR speech codec; Comfort noise for AMR speech traffic channels | +| 06.93 | 26.093 | AMR speech codec; Source controlled rate operation | +| 06.94 | 26.094 | AMR speech codec; Voice Activity Detector for AMR speech traffic channels | +| 07.01 | 27.001 | General on Terminal Adaptation Function(s) (TAF) for Mobile Stations (MS) | +| 07.02 | 27.002 | Terminal Adaptation Function(s) (TAF) for services using asynchronous bearer capabilities | +| 07.03 | 27.003 | Terminal Adaptation Function(s) (TAF) for services using synchronous bearer capabilities | +| 07.03 | 27.103 | Wide Area Network Synchronization | +| 07.05 | 27.005 | Use of Data Terminal Equipment – Data Circuit terminating Equipment (DTE-DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) | +| 07.07 | 27.007 | AT command set for 3G User Equipment (UE) | +| 07.10 | 27.010 | Terminal Equipment to User Equipment (TE-UE) multiplexer protocol User Equipment (UE) | +| 07.60 | 27.060 | Packet domain; Mobile Station (MS) supporting Packet Switched services | +| 09.02 | 29.002 | Mobile Application Part (MAP) specification | +| 09.07 | 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) | +| 09.08 | 29.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | +| 09.10 | 29.010 | Information Element Mapping between Mobile Station – Base Station System (MS – BSS) and Base Station System – Mobile-services Switching Centre (BSS – MCS) Signalling Procedures and the Mobile Application Part (MAP) | +| 09.11 | 29.011 | Signalling interworking for supplementary services | +| 09.13 | 29.013 | Signalling interworking between ISDN supplementary services Application Service Element (ASE) and Mobile Application Part (MAP) protocols | + +**Table 1/Q.1741.1 – Conversion between 2G and 3G** + +| GSM Number | 3G Spec. Number | Title | +|-------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 09.16 | 29.016 | Serving GPRS Support Node (SGSN) – Visitors Location Register (VLR); Gs Interface Network Service Specification | +| 09.18 | 29.018 | Serving GPRS Support Node (SGSN) – Visitors Location Register (VLR); Gs Interface Layer 3 Specification | +| 09.19 | 29.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | +| 09.20 | 29.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR); Stage 3 | +| 09.60 | 29.060 | GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | +| 09.61 | 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN) | +| 09.78 | 29.078 | Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 3; CAMEL Application Part (CAP) specification | +| 09.98 | 29.198 | Open Service Architecture (OSI) Application Programming Interface (API) – Part 1 | +| 11.01 | 31.101 | UICC-terminal interface; Physical and logical characteristics | +| 11.02 | 31.102 | Characteristics of the USIM Application | +| 11.10 | 31.110 | Numbering system for telecommunication IC card applications | +| 11.11 | 31.111 | USIM Application Toolkit (USAT) | +| 11.20 | 31.120 | UICC-terminal interface; Physical, electrical and logical test specification | +| 11.21 | 31.121 | UICC-terminal interface; USIM application test specification | +| 11.22 | 31.122 | USIM conformance test specification | +| 12.01 | 32.101 | 3G Telecom Management principles and high level requirements | +| 12.02 | 32.102 | 3G Telecom Management Architecture | +| 12.04 | 32.104 | 3G Performance Management | +| 12.05 | 32.005 | Telecommunications Management; Charging and billing; 3G call and event data for the Circuit Switched (CS) domain | +| 12.06-1 | 32.106-1 | Telecommunication Management; Configuration Management; Part 1: 3G configuration management; Concept and requirements | +| 12.06-2 | 32.106-2 | Telecommunication Management; Configuration Management; Part 2: Notification Integration Reference Point; Information Service version 1 | +| 12.06-3 | 32.106-3 | Telecommunication Management; Configuration Management; Part 3: Notification Integration Reference Point; CORBA solution set version 1:1 | +| 12.06-4 | 32.106-4 | Telecommunication Management; Configuration Management; Part 4: Notification Integration Reference Point; CMIP solution set version 1:1 | +| 12.06-5 | 32.106-5 | Telecommunication Management; Configuration Management; Part 5: Basic Configuration Management IRP information model (including NRM) version 1 | +| 12.06-6 | 32.106-6 | Telecommunication Management; Configuration Management; Part 6: Basic Configuration Management IRP CORBA solution set version 1:1 | +| 12.06-7 | 32.106-7 | Telecommunication Management; Configuration Management; Part 7: Basic Configuration Management IRP CMIP solution set version 1:1 | + +**Table 1/Q.1741.1 – Conversion between 2G and 3G** + +| GSM Number | 3G Spec. Number | Title | +|-------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------| +| 12.06-8 | 32.106-8 | Telecommunication Management; Configuration Management; Part 8: Name convention for Managed Objects | +| 12.11-1 | 32.111-1 | Telecommunication Management; Fault Management; Part 1: 3G fault management requirements | +| 12.11-2 | 32.111-2 | Telecommunication Management; Fault Management; Part 2: Alarm Integration Reference Point: Information Service | +| 12.11-3 | 32.111-3 | Telecommunication Management; Fault Management; Part 3: Alarm Integration Reference Point: CORBA solution set version 1:1 | +| 12.11-4 | 32.111-4 | Telecommunication Management; Fault Management; Part 4: Alarm Integration Reference Point: CMIP solution set | +| 12.15 | 32.015 | Telecommunications Management; Charging and billing; 3G call and event data for the Packet Switched (PS) domain | +| 13.02 | 33.102 | 3G security; Security architecture | +| 13.03 | 33.103 | Security Integration Guidelines | +| 13.05 | 33.105 | Cryptographic Algorithm requirements | +| 13.06 | 33.106 | Lawful interception requirements | +| 13.07 | 33.107 | Lawful interception architecture and functions | +| 13.20 | 33.120 | Security Objectives and Principles | +| 15.01 | 35.201 | Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specifications | +| 15.02 | 35.202 | Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi algorithm specification | +| 15.03 | 35.203 | Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | +| 15.04 | 35.204 | Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | + +# **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. + +## **10.1 21-series, Requirements specifications** + +### **10.1.1 TS 21.101 3rd Generation mobile system Release 1999 specifications** + +The document identifies the 3rd generation mobile system specifications for Release 1999. The specifications and reports of 3GPP Release 1999 have a major version number 3 (e.g. 3.x.y). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-21.101 (R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 121 101 | 3.3.0 | Published | 17-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13427 | +| TI | TI.3GPP.21.101V330-2001 | 3.3.0 | Approved | 02-11-01 | http://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-21.101(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-21_101_R99_.zip | +| TTC | TS-3GA-21.101(R99)v3.3.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts21101r99.pdf | + +### 10.1.2 TS 21.111 USIM and IC card requirements + +This document defines the requirements of the Universal Subscriber Identity Module (USIM) and the IC card for 3G (UICC). These are derived from the service and security requirements defined in TS 22.100 and 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 terminals. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-21.111(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/21.111.html | +| CWTS | CWTS-TSD-CN-21.111 (R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 121 111 | 3.3.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11501 | +| TI | TI.3GPP.21.111V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-21.111(R99F) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-21_111_R99_.zip | + +### 10.1.3 TS 21.133 Security threats and requirements + +This specification takes notice of the Security Principles and Objectives as set out in TS 33.120. It contains an evaluation of perceived threats to 3GPP and subsequently produces a list of security requirements to address these threats. + +As teleservices and applications will not, in general, be standardized, it is difficult to predict their exact nature. Therefore, this specification considers all security threats and aims at listing generic security requirements that shall be applicable, irrespective of the actual services offered. The list of threats and requirements may, however, need to be updated as the 3GPP system evolves. + +The threat analysis performed relies to a large extent on previous experiences with 2G systems, in particular GSM, and takes into account known problems from that area. + +The security requirements listed in this specification shall be used as input for the choice of security features and the design of the 3GPP security architecture as specified in TS 33.102. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-21.133(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/21.133.html | +| CWTS | CWTS-TSD-CN-21.133 (R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 121 133 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=6973 | +| T1 | T1.3GPP.21.133V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-21.133(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-21_133.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 present 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.001(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.001.html | +| CWTS | CWTS-TSD-CN-21.001 (R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122 001 | 3.2.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=9985 | +| T1 | T1.3GPP.22.001V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.001(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_001_R99_.zip | + +### 10.2.2 TS 22.002 Circuit bearer services supported by a 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.002(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.002.html | +| CWTS | CWTS-TSD-CN-22.002 (99) | 3.6.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.002 | 3.6.0 | Published | 19-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13537 | +| T1 | T1.3GPP.22.002V 360-2001 | 3.6.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.002(R99) | 3.6.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_002_R99_.zip | + +### 10.2.3 TS 22.003 Circuit teleservices supported by a Public Land Mobile Network (PLMN) + +The document 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.003(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.003.html | +| CWTS | CWTS-TSD-CN-22.003(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.003 | 3.2.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=9932 | +| T1 | T1.3GPP.22.003V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.003(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_003_R99_.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 TS 24.010. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.004(R99) | 3.2.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.004 | 3.2.1 | Published | 17-04-00 | http://pda.etsi.org/pda/home.asp?wki_id=10202 | +| T1 | T1.3GPP.22.004V321-2001 | 3.2.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.004(R99) | 3.2.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_004.zip | +| TTC | JP-3GA-22.004(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp22004r99.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 (User Equipment). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.011(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.011 | 3.4.0 | Published | 23-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13541 | +| T1 | T1.3GPP.22.011V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.011(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_011_R99_.zip | +| TTC | TS-3GA-22.011(R99)v3.4.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts22011r99.pdf | + +### 10.2.6 TS 22.016 International Mobile 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. + +NOTE – The present document covers description for GSM only. The document needs to be updated to make it applicable to 3GPP. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.016(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.016.html | +| CWTS | CWTS-TSD-CN-22.016(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.016 | 3.2.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11304 | +| T1 | T1.3GPP.22.016V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.016(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_016_R99_.zip | + +### 10.2.7 TS 22.022 Personalisation of GSM ME Mobile functionality specification; Stage 1 + +The document provides functional specifications of five features to personalise Mobile Equipment (ME) for GSM and 3G systems. These features are called: + +- Network personalization; +- Network subset personalization; +- Service Provider (SP) personalization; +- Corporate personalization; +- USIM personalization. + +The document specifies requirements for MEs, which provide these personalization features. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.022(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.022.html | +| CWTS | CWTS-TSD-CN-22.022 (R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.022 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11305 | +| TI | T1.3GPP.22.022V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.022(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_022_R99_.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, which 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.024(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.024 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8739 | +| TI | T1.3GPP.22.024V 301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.024(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_024.zip | +| TTC | JP-3GA-22.024(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22024r99.pdf | + +### 10.2.9 TS 22.030 Man-Machine Interface (MMI) of the Mobile Station (MS) + +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. + +The document included requirements only to UE connected to CS Domain. See TS 22.101; for overall service principles and TS 22.001 for Circuit telecommunication services. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.030(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.030.html | +| CWTS | CWTS-TSD-CN-22.030(R99) | 3.4.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.030 | 3.4.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11933 | +| T1 | T1.3GPP.22.030V 340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.030(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_030_R99_.zip | + +### 10.2.10 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, which 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 in TS 23.107. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.034(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.034.html | +| CWTS | CWTS-TSD-CN-22.034(R99) | 3.2.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.034 | 3.2.1 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=9988 | +| T1 | T1.3GPP.22.034V 321-2001 | 3.2.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.034(R99) | 3.2.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_034.zip | + +### 10.2.11 TS 22.038 SIM application toolkit (SAT); Stage 1 + +This Technical Specification defines the stage one description of the USIM/SIM application Toolkit (SAT/USAT). Stage one 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/SIM application Toolkit (SAT/USAT), which are sufficient to provide a complete service. + +It is highly desirable however, those technical solutions for a USIM/SIM application Toolkit (SAT/USAT) should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this Technical Specification may implement requirements, which are considered outside the scope of this Technical Specification. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service. + +![Diagram illustrating the scope of TS 22.038 Technical Specification. It shows an ME (Mobile Equipment) connected to a PLMN (Packet Switched Network) and a SAT/USAT Server(s). The ME contains a GSM/UMTS and SAT/USAT section, which is further connected to a SIM/USIM. Arrows indicate the scope of the specification, pointing to the ME, the SIM/USIM, and the interaction between the ME and the PLMN.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +Q.1741.1 +F10.2.11-1 + +Diagram illustrating the scope of TS 22.038 Technical Specification. It shows an ME (Mobile Equipment) connected to a PLMN (Packet Switched Network) and a SAT/USAT Server(s). The ME contains a GSM/UMTS and SAT/USAT section, which is further connected to a SIM/USIM. Arrows indicate the scope of the specification, pointing to the ME, the SIM/USIM, and the interaction between the ME and the PLMN. + +**Figure 10-1/Q.1741.1 – Scope of TS 22.038 Technical Specification** + +As indicated in Figure 10-1, the scope of this Technical Specification encompasses the SAT/USAT functionality in the UE/MS (comprising USIM/SIM and ME) and the interaction with the PLMN environment. The SAT/USAT Server is not necessarily a separate entity as shown in the figure; nodes providing SAT/USAT services may also exist within the PLMN. The functionalities of the SAT/USAT servers (such as charging aspects, security level classification etc.) are not covered by this specification. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.038(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.038.html | +| CWTS | CWTS-TSD-CN-22.038(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.038 | 3.2.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11306 | +| T1 | T1.3GPP.22.038V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.038(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_038_R99_.zip | + +### 10.2.12 TS 22.041 Operator determined call barring + +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 Circuit services by the barring of certain categories of outgoing or incoming calls or of roaming. ODB shall take effect immediately and shall terminate ongoing calls and bar future calls. + +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. + +| Organi-zation | Document No. | Version | Status | Issued date | Location | +|---------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.041(R99) | 3.3.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.041 | 3.3.1 | Published | 25-06-01 | http://pda.etsi.org/pda/home.asp?wki_id=13548 | +| T1 | T1.3GPP.22.041V 330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.041(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_041_R99_.zip | +| TTC | TS-3GA-22.041(R99)v.3.3.1 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/22041r99.pdf | + +### 10.2.13 TS 22.042 Network Identity and Time Zone (NITZ); 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 has changed their name since the ME was sold. Additionally time, Daylight Saving Time and time zone information can be utilized by MEs as desired. + +| Organi-zation | Document No. | Version | Status | Issued date | Location | +|---------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.042(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.042 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8743 | +| T1 | T1.3GPP.22.042V 301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.042(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_042.zip | +| TTC | JP-3GA-22.042(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22042r99.pdf | + +### 10.2.14 TS 22.057 Mobile Station Application Execution Environment (MExE); Stage 1 + +This Technical Specification (TS) defines the stage one description of the Mobile Station Application Execution Environment (MExE). Stage one 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 Station Application Execution Environment (MExE), which is sufficient to provide a complete service. + +It is highly desirable however, that technical solutions for a Mobile Station Application Execution Environment (MExE) should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this Technical Specification may implement requirements, which are considered outside the scope of this TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service. + +![Diagram showing the scope of TS 22.057. A Mobile Station (MS) is shown with a Mobile Equipment (ME) part. The ME is connected to a cloud labeled 'MExE Service Environment'. Arrows from the cloud point to the ME and the MS, labeled 'Scope of this TS'. Reference Q.1741.1 F10.2.14-1 is noted.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +Diagram showing the scope of TS 22.057. A Mobile Station (MS) is shown with a Mobile Equipment (ME) part. The ME is connected to a cloud labeled 'MExE Service Environment'. Arrows from the cloud point to the ME and the MS, labeled 'Scope of this TS'. Reference Q.1741.1 F10.2.14-1 is noted. + +**Figure 10-2/Q.1741.1 – Scope of TS 22.057 Technical Specification** + +As indicated in Figure 10-2, the scope of this Technical Specification encompasses the MExE functionality in the MS, 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.057(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.057.html | +| CWTS | CWTS-TSD-CN-22.057(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.057 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8745 | +| T1 | T1.3GPP.22.057V 301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.057(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_057.zip | + +### 10.2.15 TS 22.060 General Packet Radio Service (GPRS); Stage 1 + +This Technical Specification defines the stage one description of the General Packet Radio Service (GPRS). Stage one 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 data base manufacturers. + +This Technical Specification contains the core requirements for the packet switched networks specified by 3GPP, which 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 to GPRS, EGPRS and the PS Domain of the 3G PLMN. + +The GPRS shall not prevent the user's operation of other UMTS services. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.060(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.060 | 3.5.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12044 | +| T1 | T1.3GPP.22.060V350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.060(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_060_R99_.zip | +| TTC | JP-3GA-22.060(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp22060r99.pdf | + +### 10.2.16 TS 22.066 Support of Mobile Number Portability (MNP); Stage 1 + +This Technical Specification defines the stage one 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 GSM mobile networks). Stage one 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, which 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, which are considered outside the scope of this specification. This additional functionality may be on a network-wide basis, nation-wide 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), which 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 Mobile Station (MS) 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.066(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.066 | 3.2.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11316 | +| T1 | T1.3GPP.22.066V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.066(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_066_R99_.zip | +| TTC | JP-3GA-22.066(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp22066r99.pdf | + +### 10.2.17 TS 22.067 Enhanced Multi-Level Precedence and Preemption service (eMLPP); Stage 1 + +The document specifies the stage 1 description of the enhanced Multi-Level Precedence and Preemption Service (eMLPP). This service has two parts: precedence and preemption. Precedence involves assigning a priority level to a call in combination with fast call set-up. Preemption 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. Preemption can also involve the disconnection of an on-going 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. + +NOTE – It is under study whether normal GSM Phase 2 Mobile Stations will be able to be used for this service. + +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. Any interaction with other services and/or networks not dealt with in clauses 8 or 9 is outside the scope of the present document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.067(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.067.html | +| CWTS | CWTS-TSD-CN-22.067(R99) | 3.0.1 | Published | -02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.067 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8748 | +| TI | T1.3GPP.22.067V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.067(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_067.zip | + +### 10.2.18 TS 22.071 Location Services (LCS); Stage 1 (T1P1) + +The document provides the Stage One description of Location Services (LCS) networks. A stage one 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 data base manufacturers. + +NOTE – Location Services may be considered as a network provided enabling technology consisting of standardized service capabilities, which enables the provision of location applications. This application 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 sections of the specification. + +The document contains the core requirements for the LCS to an extent sufficient to derive a complete definition of the LCS at the service level. However, the present document also documents some additional requirements, which may suggest, in a non-normative manner, certain ways the system may be implemented to support the LCS feature. + +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 MS 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 MS whether or not the MS supports LCS, but with restrictions on choice of positioning method or notification of a location request to the MS user when LCS or individual positioning methods, respectively, are not supported by the MS. + +LCS will be developed in phases. Phase 1 includes provision of the following: + +LCS Phase 1. This is the initial default phase of LCS. It provides a generic flexible architecture capable of supporting all positioning methods. Specific support is provided for Time Of Arrival (TOA), Enhanced Observed Time Difference (E-OTD) and Global Positioning System (GPS) based positioning methods. Support is provided for emergency services, value added services and PLMN operator services. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.071(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.071.html | +| CWTS | CWTS-TSD-CN-22.071(R99) | 3.3.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.071 | 3.3.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12045 | +| T1 | T1.3GPP.22.071V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.071(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_071_R99_.zip | + +### 10.2.19 TS 22.072 Call Deflection (CD); 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.072(R99) | 3.0.1 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.072 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8752 | +| T1 | T1.3GPP.22.072V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.072(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_072.zip | +| TTC | JP-3GA-22.072(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22072r99.pdf | + +### 10.2.20 TS 22.078 CAMEL; Stage 1 + +This standard specifies the stage 1 description for the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature, which 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. + +CAMEL is developed in phases. + +- CAMEL phase 1. This is the default phase in this specification. +- CAMEL phase 2. +- CAMEL phase 3. + +A VPLMN or IPLMN supporting CAMEL phase 2 shall also support CAMEL phase 1. + +The CAMEL feature is applicable + +- To mobile originated and mobile terminated call related activities; +- As a CAMEL phase 2 function, to supplementary service invocations; + +- As a CAMEL Phase 3 function, 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. The following capabilities are added: + +- Additional event detection points; +- Interaction between a user and 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-) reach ability and roaming; +- Control of GPRS sessions and PDP contexts; +- Control of mobile originating SMS through both circuit switched and packet switched serving network entities; +- The CSE can be informed about the invocation of the GSM supplementary service CCBS. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.078(R99) | 3.7.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.078 | 3.7.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13559 | +| TI | TI.3GPP.22.078V 370-2001 | 3.7.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.078(R99) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_078_R99_.zip | +| TTC | TS-3GA-22.078(R99)v.3.7.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts22078r99.pdf | + +### 10.2.21 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 are to calls directed to a mobile subscriber roaming in her home country, but registered in a PLMN different from 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.079(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.079 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8754 | +| T1 | T1.3GPP.22.079V 301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.079(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_079.zip | +| TTC | JP-3GA-22.079(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22079r99.pdf | + +### 10.2.22 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 11.2/E.164 [10]. + +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". + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.081(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.081 | 3.2.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11324 | +| T1 | T1.3GPP.22.081V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.081(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_081_R99_.zip | +| TTC | JP-3GA-22.081(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp22081r99.pdf | + +### 10.2.23 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 her actual location, according to the schemes: + +- 1) National (significant) number; +- 2) National (trunk) prefix plus national (significant) number; +- 3) International prefix (see Note), 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 her actual location, according to the following scheme: + +- International prefix (see 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 for her. + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|---------------------|-------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.082(R99) | 3.0.1 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.082 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8756 | +| 3GPP | T1.3GPP.22.082V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.082(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_082.zip | +| TTC | JP-3GA-22.082(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22082r99.pdf | + +### **10.2.24 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.083(R99) | 3.0.1 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.083 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8757 | +| T1 | T1.3GPP.22.083V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.083(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_083.zip | +| TTC | JP-3GA-22.083(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22083r99.pdf | + +### 10.2.25 TS 22.084 MultiParty (MPTY) supplementary service; Stage 1 + +The document describes the Supplementary Services belonging to the group MultiParty 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 Supplementary Services MultiParty Supplementary Services consists of one Supplementary Service: + +- MultiParty service. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.084(R99) | 3.0.1 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.084 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8758 | +| T1 | T1.3GPP.22.084V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.084(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_084.zip | +| TTC | JP-3GA-22.084(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22084r99.pdf | + +### 10.2.26 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.085(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.085 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8759 | +| T1 | T1.3GPP.22.085V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.085(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_085.zip | +| TTC | JP-3GA-22.085(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22085r99.pdf | + +### 10.2.27 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.086(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.086 | 3.1.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=8760 | +| T1 | T1.3GPP.22.086V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.086(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_086.zip | +| TTC | JP-3GA-22.086(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22086r99.pdf | + +### 10.2.28 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.087(R99) | 3.1.0 | Published | -02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.087 | 3.1.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=9840 | +| TI | TI.3GPP.22.087V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.087(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_087.zip | +| TTC | JP-3GA-22.087(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp22087r99.pdf | + +### 10.2.29 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.088(R99) | 3.0.2 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.088 | 3.0.2 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=12314 | +| T1 | T1.3GPP.22.088V302-2001 | 3.0.2 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.088(R99) | 3.0.2 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_088_R99_.zip | +| TTC | JP-3GA-22.088(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp22088r99.pdf | + +### 10.2.30 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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.090(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.090 | 3.1.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=9993 | +| T1 | T1.3GPP.22.090V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.090(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_090.zip | +| TTC | JP-3GA-22.090(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp22090r99.pdf | + +### 10.2.31 TS 22.091 Explicit Call Transfer (ECT) supplementary service; 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 present document in terms of the charging information required to be collected. Any subsequent charging implications are outside of the scope of the document. + +Any interactions with other networks not dealt with in clause 9 are outside the scope of the document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.091(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.091 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12047 | +| T1 | T1.3GPP.22.091V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.091(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_091_R99_.zip | +| TTC | JP-3GA-22.091(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp22091r99.pdf | + +### 10.2.32 TS 22.093 Call Completion to Busy Subscriber (CCBS); 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 is outside the scope of the document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.093(R99) | 3.0.1 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.093 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8765 | +| T1 | T1.3GPP.22.093V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.093(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_093.zip | +| TTC | JP-3GA-22.093(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22093r99.pdf | + +### 10.2.33 TS 22.094 Follow Me; 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| ETSI | TS 122.094 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=9732 | +| TI | T1.3GPP.22.094V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.094(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_094.zip | + +### 10.2.34 TS 22.096 Calling Name Presentation (CNAP); Stage 1 (T1P1) + +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: + +CNAP Calling Name Presentation. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.096(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.096 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8767 | +| TI | T1.3GPP.22.096V 301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.096(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_096.zip | +| TTC | JP-3GA-22.096(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp22096r99.pdf | + +### 10.2.35 TS 22.097 Multiple Subscriber Profile (MSP); 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.097(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.097 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12048 | +| TI | T1.3GPP.22.097V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.097(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_097_R99_.zip | +| TTC | JP-3GA-22.097(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp22097r99.pdf | + +### 10.2.36 TS 22.100 UMTS Phase 1 + +The UMTS system will be defined in a phased approach. The present document specifies the requirements for Release '99 of UMTS. Some requirements, which are necessary to ensure a smooth transition to later releases, are also indicated. The present document should, however, be read in conjunction with the other 22.000 series documents, which provide a complete description of the requirements for UMTS Release '99. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.100(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.100.html | +| CWTS | CWTS-TSD-CN-22.100(R99) | 3.6.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.100 | 3.6.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=9994 | +| T1 | T1.3GPP.22.100V 360-2001 | 3.6.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.100(R99) | 3.6.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_100.zip | + +### 10.2.37 TS 22.101 UMTS Service principles + +This Technical Specification (TS) describes the Service principles for PLMNs specified by 3GPP. + +3GPP specifications provide integrated personal communications services. The system will support different applications ranging from narrow-band to wide-band communications capability with integrated personal and terminal mobility to meet the user and service requirements of the 21st century. + +3GPP 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. + +3GPP 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 to use and uniform way in all environments; +- To allow differentiation between service offerings of various serving networks and home environments; +- To provide a wide range of telecommunications services including those provided by fixed networks and requiring user bit rates of up to 2 Mbits/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 hand-held, portable, vehicular mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments i.e. 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. +- To provide audio, data, video and particularly multimedia services; +- 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.101(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.101.html | +| CWTS | CWTS-TSD-CN-22.101(R99) | 3.12.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.101 | 3.12.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12938 | +| T1 | T1.3GPP.22.101V 3120-2001 | 3.12.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.101(R99) | 3.12.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_101_R99_.zip | + +### 10.2.38 TS 22.105 Services and Service capabilities + +Existing systems have largely standardized the complete sets of bearer services, teleservices and supplementary services, which they provide. 3GPP 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.105(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.105.html | +| CWTS | CWTS-TSD-CN-22.105(R99) | 3.10.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.105 | 3.10.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12795 | +| T1 | T1.3GPP.22.105V 3100-2001 | 3.10.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.105(R99) | 3.10.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_105_R99_.zip | + +### 10.2.39 TS 22.115 Service aspects charging and billing + +The document describes the Service Aspects of charging and billing of the Universal Mobile Telecommunications System (UMTS). + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-21.115(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.115 | 3.3.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=9997 | +| TI | TI.3GPP.22.115V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.115(R99) | 3.3.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_115.zip | +| TTC | JP-3GA-22.115(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp22115r99.pdf | + +### 10.2.40 TS 22.121 Provision of services in UMTS – The Virtual Home Environment (VHE); Stage 1 + +The document specifies the content of the stage one requirement for realization of VHE. + +Virtual Home Environment (VHE) is defined as a concept for personal service environment (PSE) portability across network boundaries and between terminals. The concept of the VHE is such that users are consistently presented with the same personalized features, User Interface customization and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located. + +A key feature to support VHE is the ability to build services using a standardized application interface. + +Requirements not applicable for R99 will be explicitly indicated. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.121(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.121 | 3.3.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11328 | +| TI | TI.3GPP.22.121V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.121(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_121_R99_.zip | +| TTC | JP-3GA-22.121(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp22121r99.pdf | + +### 10.2.41 TS 22.129 Handover requirements between UMTS and GSM 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 multi-mode 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 observables that are not internal to the UTRAN. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.129(R99) | 3.5.0 | Published | -02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.129 | 3.5.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12796 | +| TI | TI 3GPP.22.129V 350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-22.129(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_129_R99_.zip | +| TTC | JP-3GA-22.129(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp22129r99.pdf | + +### 10.2.42 TS 22.135 Multicall; Stage 1 + +The document describes Multicall supplementary service for UMTS phase 1 release '99. + +The general aspects, including definitions and recommended provision, of the description of the 3GPP Supplementary Services are given in TS 22.004. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-22.135(R99) | 3.4.0 | Published | -02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.135 | 3.4.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12050 | +| TI | TI 3GPP.22.135V 340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.22.135(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_135_R99_.zip | +| TTC | JP-3GA-22.135(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp22135r99.pdf | + +### 10.2.43 TS 22.140 Multimedia messaging service; Stage 1 + +This Technical Specification (TS) defines the stage one description of the non real-time Multimedia Messaging Service, MMS. Stage one 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. + +Additional functionalities not documented in this Technical Specification may implement requirements, which are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the 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; +- Negotiate different terminal and network MM capabilities; +- Notification and acknowledgement of MM related events (e.g. delivery, deletion, ...); +- Handling of undeliverable MM; +- Flexible charging. + +The above list is not exhaustive. + +Thus the MMS enables a unified application, which 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-22.140(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/22.140.html | +| CWTS | CWTS-TSD-CN-22.140(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 122.140 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11333 | +| TTA | TTAE.3G-22.140(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-22_140_R99_.zip | + +## 10.3 23-series, Technical realization + +### 10.3.1 TS 23.002 Network architecture + +The purpose of the document is to present the possible architectures of the mobile system. The document contains a definition of the different functional entities needed to support the mobile service. The configuration of a PLMN is described as well as the organization of the functional entities; the configuration presented is the most general in order to cope with all the possible implementations, which can be imagined in the different countries. To illustrate that purpose, some examples of possible configurations are presented. The document contains also a brief description of the interfaces involved, which shows the principle of the organization considered. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.002(R99) | 3.4.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.002 | 3.4.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=11937 | +| T1 | T1.3GPP.23.002V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.002(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_002_R99_.zip | +| TTC | JP-3GA-23.002(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23002r99.pdf | + +### 10.3.2 TS 23.003 Numbering, addressing and identification + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.003(R99) | 3.8.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.003 | 3.8.0 | Published | 12-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13431 | +| T1 | T1.3GPP.23.003V380-2001 | 3.8.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.003(R99) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_003_R99_.zip | +| TTC | TS-3GA-23.003(R99)v.3.8.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts23003r99.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 this 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. The 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 TS 29.002 and TS 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 Gateway GPRS Support Node (GGSN) 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 Serving GPRS Support Node (SGSN) 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 is described in this document. + +A Type A Location Measurement Unit (LMU) 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.007(R99) | 3.4.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.007 | 3.4.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11362 | +| T1 | T1.3GPP.23.007V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.007(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_007_R99_.zip | +| TTC | JP-3GA-23.007 | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23007r99.pdf | + +### 10.3.4 TS 23.008 Organization of subscriber data + +The document provides details concerning information to be stored in home location registers, visitor location registers and GPRS Support Nodes concerning mobile subscriber. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.008(R99) | 3.5.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.008 | 3.5.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11939 | +| T1 | T1.3GPP.23.008V350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.008(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_008_R99_.zip | +| TTC | JP-3GA-23.008(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23008r99.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 present 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; +- 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: + - The Basic Inter-MSC Handover procedure, where the MS is handed over from a controlling MSC (MSC-A) to another MSC (MSC-B); + - The subsequent Inter-MSC Handover procedure, where the MS is handed over from MSC-B to a third MSC (MSC-B'); + - 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. This category can be divided into three further subprocedures: +- 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); + - 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); + - 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 subprocedures 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 the TS 08.08 and the 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 the TS 25.413 and the TS 24.008 shall be used on the Iu-interface. If the 3G\_MSC in case ii) also supports the A-interface, the TS 08.08 and the 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 08.08 protocol is described in TS 29.010. + +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. + +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. The 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 the present 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, as 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 hand-over imposes a few limitations on the system. After inter-MSC handover: + +- Call re-establishment is not supported. + +The list of TS 08.08 features supported during and after Inter-MSC handover is given in TS 09.08. + +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. + +NOTE – The message primitive names used in the SDL diagrams and message flows in the present document do not represent the actual messages specified in the GSM or 3GPP stage 3 technical specifications. The primitive names are only intended to be indicative of their use in the document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.009(R99) | 3.6.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.009 | 3.6.0 | Published | 17-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13433 | +| T1 | T1.3GPP.23.009V360-2001 | 3.6.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.009(R99) | 3.6.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_009_R99_.zip | +| TTC | TS-3GA-23.009(R99)v.3.6.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts23009r99.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 GSM system are realized from a technical point of view. + +Description of technical realization for specific supplementary services can be found in TS 23.08x and 23.09x-series technical specifications. + +All supplementary services may require signalling on the radio path. Signalling procedures and messages used are defined in the TS 24.08x and 24.09x-series of technical specifications. + +For some supplementary services, information needs to be transferred between the Home Location Register (HLR), the Visitor Location Register (VLR) and the Mobile services Switching Centre (MSC). Signalling procedures for such information transfer are defined in TS 29.002. + +Definitions and descriptions of supplementary services are given in the TS 22.08x and TS 22.09x-series of technical specifications. + +Definitions are given in 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 is not having the subscription. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.011(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.011 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11941 | +| T1 | T1.3GPP.23.011V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.011(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_011_R99_.zip | +| TTC | JP-3GA-23.011(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23011r99.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 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 TS 29.002. + +The document excludes location management procedures for the packet switched domain, which are covered in 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.012(R99) | 3.3.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.012 | 3.3.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11365 | +| TI | T1.3GPP.23.012V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.012(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_012_R99_.zip | +| TTC | JP-3GA-23.012(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23012r99.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 GSM system. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.014(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.014 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7836 | +| TI | T1.3GPP.23.014V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.014(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_014.zip | +| TTC | JP-3GA-23.014(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp23014r99.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 GSM services, by the barring of certain categories of incoming or outgoing traffic 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.015(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.015 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7837 | +| T1 | T1.3GPP.23.015V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.015(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_015.zip | +| TTC | JP-3GA-23.015(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp23015r99.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 scope of this specification. The GPRS context update from the SGSN to the GGSN is out of scope of this specification. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.016(R99) | 3.7.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.016 | 3.7.0 | Published | 25-06-01 | http://pda.etsi.org/pda/home.asp?wki_id=13437 | +| TI | T1.3GPP.23.016V370-2001 | 3.7.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.016(R99) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_016_R99_.zip | +| TTC | TS-3GA-23.016(R99)v.3.7.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts23016r99.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) are 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 routing (TS 23.079). The use of the Provide Subscriber Information message flow is shown in TS 23.078 and TS 23.079. + +The specification of the handling of data calls rerouted to a SIWFS is described in TS 23.054. + +The logical separation of the MSC and VLR, and the messages transferred between them is 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 08.08 and TS 29.002), the stage 3 specifications shall prevail. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.018(R99) | 3.7.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.018 | 3.7.0 | Published | 12-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13439 | +| TI | T1.3GPP.23.018V370-2001 | 3.7.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.018(R99) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_018_R99_.zip | +| TTC | TS-3GA-23.018(R99)v.3.7.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts23018r99.pdf | + +### 10.3.12 TS 23.032 Universal Geographical Area Description (GAD) + +The document defines an intermediate universal Geographical Area Description, which subscriber applications or GSM services can use and the network can convert into an equivalent radio coverage map. + +For GSM 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). + +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 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.032(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.032 | 3.1.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10010 | +| 1T | T1.3GPP.23.032V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.032(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_032_R99_.zip | +| TTC | JP-3GA-23.032(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23032r99.pdf | + +### 10.3.13 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. HSCSD utilizes the multislot mechanism, i.e. using multiple traffic channels (/bearers) for the communication. In Iu mode one bearer can provide all needed data rates, and the multislot mechanism is therefore not needed. The Iu mode aspects concerning HSCSD are described exclusively. + +In analogy with ITU-T Recs. I.130 [12] (refer to annex A) and ITU-T Rec. Q.65 [18] (Stage 2 of the method for characterization of services supported by an ISDN), 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 specifications. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.034(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.034 | 3.3.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12757 | +| T1 | T1.3GPP.23.034V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.034(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_034_R99_.zip | +| TTC | JP-3GA-23.034(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23034r99.pdf | + +### 10.3.14 TS 23.038 Alphabets and Language + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.038(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.038.html | +| CWTS | CWTS-TSD-CN-23.038(R99) | 3.3.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.038 | 3.3.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8033 | +| T1 | T1.3GPP.23.038V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.038(R99F) | 3.3.0 | Approved | 28-03-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_038F.zip | +| | TTAE.3G-23.038(R99T) | 3.3.0 | Approved | 28-03-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_038T.zip | + +### 10.3.15 TS 23.040 Technical realization of 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 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 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 present 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 PLMN's. 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 PLMN's as they see fit. + +The required and assumed network service offered to the higher layers is defined in the present document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.040(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.040.html | +| CWTS | CWTS-TSD-CN-23.040(R99) | 3.5.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123-040 | 3.5.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11369 | +| T1 | T1.3GPP.23.040V 350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.040(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_040_R99_.zip | + +### 10.3.16 TS 23.041 Technical realization of Cell Broadcast Service (CBS) + +The document describes the Cell Broadcast short message service (CBS) for UMTS. + +For UMTS it defines the interface requirements for the Cell Broadcast Center – 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.041(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.041.html | +| CWTS | CWTS-TSD-CN-23.041(R99) | 3.3.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.041 | 3.3.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11946 | +| T1 | T1.3GPP.23.041V 330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.041(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_041_R99_.zip | + +### 10.3.17 TS 23.042 Compression algorithm for SMS + +The document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.042(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.042.html | +| CWTS | CWTS-TSD-CN-23.042(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.042 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8031 | +| TI | T1.3GPP.23.042V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.042(R99F) | 3.1.0 | Approved | 28-03-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_042F.zip | +| | TTAE.3G-23.042(R99T) | 3.1.0 | Approved | 28-03-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_042T.zip | + +### 10.3.18 TS 23.054 Shared interworking functions; Stage 2 + +The document defines the stage two description of the Shared Interworking Function (SIWF) on Global System for Mobile communications (GSM). + +A stage one description does not exist because this service is not visible to the service subscribers and users. This stage two identifies the functional Capabilities and information flows needed to support the service. The signalling system protocols and switching functions needed to implement this service are defined in the relevant specifications. + +Interworking with other networks (e.g. PSTN) needs the presence of specific functions associated with the MSC, known as interworking functions (IWF). The IWFs depend on the type of network with which it is desired to interconnect and the type of service desired. + +A Shared Interworking Function is a network function that may be used by any MSC in the same PLMN to provide interworking for a data/fax call. Whereas an IWF can only be used by its MSC, the SIWF can be used by several other network nodes e.g. any MSC within the same PLMN (the concept is not limited to a certain number of MSCs). SIWF is applied to data services in GSM Phase 2 and GSM Phase 2+ (as defined in GSM 02.02, GSM 02.03 and GSM 02.34). + +The usage of a SIWF requires no additional manipulation at the MS. + +There is an interest to have a Shared Interworking Function (SIWF) for the following reasons: + +- Possibility to fabricate/obtain the specific functionality needed for data services in areas where data traffic is expected to be low; +- Handling of data calls in case of local overload of the data traffic; +- Quick introduction and roll-out of new data services. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.054(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.054 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7844 | +| TI | T1.3GPP.23.054V 300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.054(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_054.zip | +| TTC | JP-3GA-23.054(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp23054r99.pdf | + +### 10.3.19 TS 23.057 Mobile Station Application Execution Environment (MExE) + +The document defines the stage 2 and stage 3 description of the Mobile Station Application 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 Station Application Execution Environment (MExE), which are sufficient to provide a complete service. + +MExE uses a number of technologies to realise the requirements of the stage 1 description (TS 22.057). The document describes how the service requirements are realized with the selected technologies. The Technical Specification is devised 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.057(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.057.html | +| CWTS | CWTS-TSD-CN-23.057(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.057 | 3.4.0 | Published | 12-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13445 | +| TT1 | T1.3GPP.23.057V 340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.057(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_057_R99_.zip | + +### 10.3.20 TS 23.060 General Packet Radio Service (GPRS) service description; Stage 2 + +The document defines the stage 2 service description for the packet domain, which includes the General Packet Radio Service (GPRS) in GSM and UMTS. ITU-T Rec. I.130 [12] describes a three-stage method for characterisation of telecommunication services, and ITU-T Rec. Q.65 [18] defines stage 2 of the method. + +The document does not cover the Access Network functionality. GSM 03.64 contains an overall description of the GSM GPRS Access Network. TS 25.301 contains an overall description of the UMTS Terrestrial Radio Access Network. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.060(R99) | 3.7.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.060 | 3.7.0 | Published | 17-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13447 | +| TT1 | T1.3GPP.23.060V 370-2001 | 3.7.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.060(R99) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_060_R99_.zip | +| TTC | TS-3GA-23.060(R99)v.3.7.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts23060r99.pdf | + +### **10.3.21 TS 23.066 Support of GSM Mobile Number Portability (MNP); 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 present 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 Annex A and Normative Annex 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|---------------------|-------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.066(R99) | 3.3.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.066 | 3.3.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11380 | +| T1 | T1.3GPP.23.066V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.066(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_066_R99_.zip | +| TTC | JP-3GA-23.066(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23066r99.pdf | + +### **10.3.22 TS 23.067 Enhanced Multi-Level Precedence and Preemption Service (eMLPP); Stage 2** + +The document specifies the stage 2 description of the enhanced Multi-Level Precedence and Preemption Service (eMLPP) which provides different call priorities in combination with fast call set-up and preemption for different applications according to TS 22.067. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.067(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.067 | 3.2.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12814 | +| T1 | T1.3GPP.23.067V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.067(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_067_R99_.zip | +| TTC | JP-3GA-23.067(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23067r99.pdf | + +### 10.3.23 TS 23.072 Call Deflection supplementary service; Stage 2 + +This Technical Specification gives the stage 2 description of the Call Deflection supplementary service. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.072(R99) | 3.3.0 | Published | -01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.072 | 3.3.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11949 | +| T1 | T1.3GPP.23.072V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.072(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_072_R99_.zip | +| TTC | JP-3GA-23.072(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23072r99.pdf | + +### 10.3.24 TS 23.078 CAMEL; Stage 2 + +The document specifies the stage 2 description for the third 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 GSM 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 specification, 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. + +In the third phase the CAMEL feature supports: + +- Mobile originated and forwarded calls; +- Mobile terminating calls; +- Any time interrogation; +- Active location information retrieval; +- Suppression of announcements; +- Announcements, in band user interaction; +- Charging features; + +- Supplementary service invocation notifications; +- USSD interaction with the gsmSCF; +- North American carrier selection; +- Mobility Management event notifications; +- Change of Calling Line Identification Presentation Indicator for an MO call to restricted; +- Subscribed dialled services; +- Serving network dialled services; +- MO SMS; +- GPRS data transmission; +- Mobility management; +- Notification to CSE of change of subscriber data; +- Any Time Modification; +- Any Time Interrogation of subscription Information; +- T-BCSM in the VMSC and terminating AoC; +- Interworking with Location Services; +- Multiple Subscriber Profile; +- Active Location Retrieval; +- Call Gapping. + +Note that CAMEL is not applicable to Emergency Setup (Tele Service 12), i.e., in case an Emergency call has been requested the gsmSSF shall not be invoked. + +The mechanism described in this standard especially addresses 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 standard. 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 that 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 standard. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.078(R99) | 3.8.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.078 | 3.8.0 | Published | 17-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13449 | +| TI | T1.3GPP.23.078V 380-2001 | 3.8.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.078(R99) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_078_R99_.zip | +| TTC | TS-3GA-23.078(R99)v.3.8.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts23078r99.pdf | + +### 10.3.25 TS 23.079 Support of Optimal Routing (SOR) – Phase 1; 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.079(R99) | 3.6.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.079 | 3.6.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11954 | +| TI | TI 1.3GPP.23.079V 360-2001 | 3.6.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.079(R99) | 3.6.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_079_R99_.zip | +| TTC | JP-3GA-23.079(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23079r99.pdf | + +### 10.3.26 TS 23.081 Line Identification supplementary services; Stage 2 + +The 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.081(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.081 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11383 | +| TI | T1.3GPP.23.081V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.081(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_081_R99_.zip | +| TTC | JP-3GA-23.081(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23081r99.pdf | + +### 10.3.27 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 no reply (CFNR); +- Call forwarding on terminal not reachable (CFNRc). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.082(R99) | 3.5.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.082 | 3.5.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12813 | +| TI | T1.3GPP.23.082V 350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.082(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_082_R99_.zip | +| TTC | JP-3GA-23.082(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23082r99.pdf | + +### 10.3.28 TS 23.083 Call Waiting (CW) and Call Hold (HOLD) supplementary service; Stage 2 + +The 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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.083(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.083 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11956 | +| T1 | T1.3GPP.23.083V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.083(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_083_R99_.zip | +| TTC | JP-3GA-23.083(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23083r99.pdf | + +### 10.3.29 TS 23.084 MultiParty (MPTY) supplementary service; Stage 2 + +The document gives the stage 2 description of the multiparty supplementary services. + +Only one multiparty supplementary service has been defined, this is the MultiParty (MPTY) service. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.084(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.084 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11957 | +| T1 | T1.3GPP.23.084V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.084(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_084_R99_.zip | +| TTC | JP-3GA-23.084(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23084r99.pdf | + +### 10.3.30 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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.085(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.085 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11959 | +| T1 | T1.3GPP.23.085V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.085(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_085_R99_.zip | +| TTC | JP-3GA-23.085(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23085r99.pdf | + +### 10.3.31 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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.086(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.086 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11960 | +| TI | T1.3GPP.23.086V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.086(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_086_R99_.zip | +| TTC | JP-3GA-23.086(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23086r99.pdf | + +### 10.3.32 TS 23.087 User-to-User Signalling (UUS); 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) + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.087(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.087 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11961 | +| TI | T1.3GPP.23.087V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.087(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_087_R99_.zip | +| TTC | JP-3GA-23.087(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23087r99.pdf | + +### 10.3.33 TS 23.088 Call Barring (CB) supplementary service; 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" (clause 2) 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.088(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.088 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11962 | +| T1 | T1.3GPP.23.088V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.088(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_088_R99_.zip | +| TTC | JP-3GA-23.088(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23088r99.pdf | + +### 10.3.34 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. The following diagram shows how handling of USSD is carried out, independently of the applications. + +![Diagram illustrating the handling of USSD across network entities: USER, MS, MSC, VLR, and HLR. Each entity contains an 'Applications' block and a 'USSD Handler' block. The USER connects to the MS. The MS connects to the MSC. The MSC connects to the VLR. The VLR connects to the HLR. Within each entity, the Applications block connects to the USSD Handler block. The USSD Handler blocks are interconnected across the entities.](2fbb410da68e626ba5e994d872031f14_img.jpg) + +Q.1741.1 +F10.3.36-1 + +Diagram illustrating the handling of USSD across network entities: USER, MS, MSC, VLR, and HLR. Each entity contains an 'Applications' block and a 'USSD Handler' block. The USER connects to the MS. The MS connects to the MSC. The MSC connects to the VLR. The VLR connects to the HLR. Within each entity, the Applications block connects to the USSD Handler block. The USSD Handler blocks are interconnected across the entities. + +**Figure 10-3/Q.1741.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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.090(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.090 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11963 | +| TI | T1.3GPP.23.090V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.090(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_090_R99_.zip | +| TTC | JP-3GA-23.090(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23090r99.pdf | + +### 10.3.35 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 the document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.091(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.091 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11964 | +| TI | T1.3GPP.23.091V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.091(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_091_R99_.zip | +| TTC | JP-3GA-23.091(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23091r99.pdf | + +### 10.3.36 TS 23.093 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.093(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.093 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11965 | +| TI | T1.3GPP.23.093V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.093(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_093_R99_.zip | +| TTC | JP-3GA-23.093(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23093r99.pdf | + +### 10.3.37 TS 23.094 Follow Me diversion; Stage 2 + +The document specifies the stage 2 description for the Follow Me diversion 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.094(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.094 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11966 | +| TI | T1.3GPP.23.094V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.094(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_094_R99_.zip | +| TTC | JP-3GA-23.094(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23094r99.pdf | + +### 10.3.38 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.096(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.096 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7859 | +| TI | T1.3GPP.23.096V 301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.096(R99) | 3.0.1 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_096_R99_.zip | +| TTC | JP-3GA-23.096(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23096r99.pdf | + +### 10.3.39 TS 23.097 Multiple Subscriber Profile (MSP); 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.097(R99) | 3.1.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.097 | 3.1.1 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10022 | +| T1 | T1.3GPP.23.097V 311-2001 | 3.1.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.097(R99) | 3.1.1 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_097_R99_.zip | +| TTC | JP-3GA-23.097(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23097r99.pdf | + +### 10.3.40 TS 23.101 General UMTS architecture + +This Technical Specification defines the basic physical and functional separation of UMTS. The contents of this specification are 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.101(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.101 | 3.1.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12861 | +| T1 | T1.3GPP.23.101V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.101(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_101_R99_.zip | +| TTC | JP-3GA-23.101(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23101r99.pdf | + +### 10.3.41 TS 23.107 Quality of Service, 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.107(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.107.html | +| CWTS | CWTS-TSD-CN-23.107(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.107 | 3.5.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12899 | +| T1 | T1.3GPP.23.107V 350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.107(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_107_R99_.zip | + +### 10.3.42 TS 23.108 Mobile Radio Interface Layer 3 specification Core Network Protocols; Stage 2 (structured procedures) + +The document specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for Call Control (CC), Mobility Management (MM), and Session Management (SM). + +When the notations for "further study" or "FS" or "FFS" are present in the present 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 GSM 04.03. + +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 the document 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. + +GSM 04.11 contains functional procedures for support of point-to-point short message services. + +GSM 04.12 contains functional description of short message – cell broadcast. + +GSM 04.60 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels. + +GSM 04.18 contains the procedures for the RR protocol. + +TS 24.008 Contains the procedures for the CN protocols. + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.108(R99) | 3.2.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.108 | 3.2.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10024 | +| TI | TI.3GPP.23.108V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.108(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_108_R99_.zip | +| TTC | JP-3GA-23.108(R99) | 2 | TTC published | 25-10-00 | http://www.ttc.or.jp/imt/std/jp23108r99.pdf | + +### 10.3.43 TS 23.110 UMTS Access Stratum services and functions + +The document specifies the services provided by the Access Stratum to the rest of the system. The adopted architecture is given by TS 23.101. + +The 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 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.110(R99) | 3.4.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.110 | 3.4.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10025 | +| T1 | T1.3GPP.23.110V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.110(R99) | 3.4.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_110.zip | +| TTC | JP-3GA-23.110(R99) | 2 | TTC published | 25-10-00 | http://www.ttc.or.jp/imt/std/jp23110r99.pdf | + +### 10.3.44 TS 23.116 Super-Charger; 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.116(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.116 | 3.0.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10312 | +| T1 | T1.3GPP.23.116V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.116(R99) | 3.0.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_116_R99_.zip | +| TTC | JP-3GA-23.116(R99) | 1 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23116r99.pdf | + +### 10.3.45 TS 23.119 Gateway Location Register (GLR); Stage 2 + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.119(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.119 | 3.0.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10234 | +| T1 | T1.3GPP.23.119V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.119(R99) | 3.0.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_119_R99_.zip | +| TTC | JP-3GA-23.119(R99) | 1 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp23119r99.pdf | + +### 10.3.46 TS 23.121 Architecture requirements for release '99 + +The document covers issues related to the evolution of the GSM platform towards UMTS with the overall goal of fulfilling the UMTS service requirements, the support of the UMTS role model, support of roaming and support of new functionality, signalling systems and interfaces. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.121(R99) | 3.5.1 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.121 | 3.5.1 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12714 | +| TI | T1.3GPP.23.121V 351-2001 | 3.5.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.121(R99) | 3.5.1 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_121_R99_.zip | +| TTC | JP-3GA-23.121(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23121r99.pdf | + +### 10.3.47 TS 23.122 Non-Access-Stratum functions related to Mobile Station (MS) in idle mode + +This 3GPP 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. + +This 3GPP Technical Specification outlines how the requirements of the 22-series Technical Specifications (especially TS 22.011) on idle mode operation shall be implemented. Further details are given in TS 24.008. + +This 3GPP 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.122(R99) | 3.6.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.122 | 3.6.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13459 | +| TI | T1.3GPP.23.122V 360-2001 | 3.6.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.122(R99) | 3.6.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_122_R99_.zip | +| TTC | TS-3GA-23.122(R99)v.3.6.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts23122r99.pdf | + +### 10.3.48 TS 23.127 Virtual Home Environment; Stage 2 + +The document specifies the stage 2 of the Virtual Home Environment and Open Service Architecture. + +Virtual Home Environment (VHE) is defined as a concept for personal service environment (PSE) portability across network boundaries and between terminals. The concept of the VHE is such that users are consistently presented with the same personalized features, User Interface customization and services in whatever network and whatever terminal (within the capabilities of the terminal and + +the network), wherever the user may be located. For Release 1999, e.g. CAMEL, MExE and SAT are considered the mechanisms supporting the VHE concept. + +The Open Service Architecture (OSA) defines an architecture that enables operator and third party applications to make use of network functionality through an open standardized API (the OSA API). OSA provides the glue between applications and service capabilities provided by the network. In this way applications become independent from the underlying network technology. The applications constitute the top level of the Open Service Architecture (OSA). This level is connected to the Service Capability Servers (SCSs) via the OSA API. The SCSs map the OSA API onto the underlying telecom specific protocols (e.g. MAP, CAP etc.) and are therefore hiding the network complexity from the applications. + +Applications can be network/server centric applications or terminal centric applications. Terminal centric applications reside in the Mobile Station (MS). Examples are MExE and SAT applications. Network/server centric applications are outside the core network and make use of service capability features offered through the OSA API. (Note that applications may belong to the network operator domain although running outside the core network. Outside the core network means that the applications are executed in Application Servers that are physically separated from the core network entities). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.127(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.127 | 3.3.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12862 | +| TI | TI.3GPP.23.127V 330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.127(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_127_R99_.zip | +| TTC | JP-3GA-23.127(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23127r99.pdf | + +### 10.3.49 TS 23.135 Multicall supplementary service; Stage 2 + +The document gives the stage 2 description of the Multicall supplementary service. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-23.135(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.135 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11971 | +| TI | TI.3GPP.23.135V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-23.135(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp23135r99.pdf | + +### 10.3.50 TS 23.140 Multimedia Messaging Service (MMS) + +The document defines the stage 2 and stage 3 description of the non-real-time Multimedia Messaging Service, MMS. 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 non-real-time Multimedia Messaging Service, MMS, which are sufficient to provide a basic service. + +MMS uses a number of technologies to realise the requirements of the stage 1 description (TS 22.140). The document describes how the service requirements are realized with the selected technologies. As far as possible existing protocols (e.g. WAP, SMTP, ESMTP as transfer protocols; lower layers to provide push, pull, notification) and existing message formats (e.g. SMIL, MIME) shall be used for the realization of the Multimedia Messaging Service. + +This specification serves as a foundation for the development of MMS for release '99. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.140(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.140.html | +| CWTS | CWTS-TSD-CN-23.140(R 99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.140 | 3.0.1 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=8779 | +| TI | TI 1.3GPP.23.140V 301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.140(R99) | 3.0.1 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_140_R99_.zip | + +### 10.3.51 TS 23.171 Functional stage 2 description of location services in UMTS + +The document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, 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 the 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-23.171(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/23.171.html | +| CWTS | CWTS-TSD-CN-23.171(R99) | 3.3.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 123.171 | 3.3.0 | Published | 19-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13465 | +| TI | TI 1.3GPP.23.171V 330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-23.171(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-23_171_R99_.zip | + +## 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 UE-UTRAN (in 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 UE-UTRAN (in Iu mode) interface. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.002(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.002 | 3.1.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12759 | +| T1 | T1.3GPP.24.002V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-24.002(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp24002r99.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 the document. + +For GPRS services in addition the local information transfer and stimuli sent between sublayers is informatively included within Annex C of the document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.007(R99) | 3.7.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.007 | 3.7.0 | Published | 19-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13493 | +| T1 | T1.3GPP.24.007V 370-2001 | 3.7.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.007(R99F) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_007_R99F_.zip | +| | TTAE.3G-24.007(R99T) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_007_R99T_.zip | +| TTC | TS-3GA-24.007(R99)v.3.7.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts24007r99.pdf | + +### 10.4.3 TS 24.008 Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3 + +This Technical Specification 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). + +When the notations for "further study" or "FS" or "FFS" are present in this Technical Specification 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 GSM 04.03 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 Technical Specification 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.011 contains functional procedures for support of supplementary services. + +TS 24.012 contains functional procedures for support of point-to-point short message services. + +GSM 04.12 contains functional description of short message – cell broadcast. + +GSM 04.60 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.008(R99) | 3.7.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.008 | 3.7.0 | Published | 19-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13495 | +| TI | TI.3GPP.24.008V 370-2001 | 3.7.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.008(R99F) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_008_R99F_.zip | +| | TTAE.3G-24.008(R99T) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_008_R99T_.zip | +| TTC | TS-3GA-24.008(R99)v.3.7.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts24008r99.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. + +GSM 04.8x and 04.9x-series specify the procedures used at the radio interface (reference point Um as defined in GSM 04.02) 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. + +GSM 04.08 and GSM 04.80 specify the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and 02.9x-series. + +Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and 03.9x-series. + +The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3-radio interface are defined in GSM 04.07 and GSM 04.08. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.010(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.010 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11393 | +| T1 | T1.3GPP.24.010V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.010(R99F) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_010_R99F_.zip | +| | TTAE.3G-24.010(R99T) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_010_R99T_.zip | +| TTC | JP-3GA-24.010(R99) | 2 | TTC published | 25-10-00 | http://www.ttc.or.jp/imt/std/jp24010r99.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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.011(R99) | 3.6.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.011 | 3.6.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13497 | +| T1 | T1.3GPP.24.011V 360-2001 | 3.6.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.011(R99F) | 3.6.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_011_R99F_.zip | +| | TTAE.3G-24.011(R99T) | 3.6.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_011_R99T_.zip | +| TTC | TS-3GA-24.011(R99)v3.6.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts24011r99.pdf | + +### 10.4.6 TS 24.012 Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface + +This Technical Specification describes how the Short Message Service Cell Broadcast (SMSCB) (Teleservice 23 as specified in GSM 02.03) is supported over the mobile radio interface. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-24.012(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/24.012.html | +| CWTS | CWTS-TSD-CN-24.012(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| TTA | TTAE.3G-24.012(R99F) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_012F.zip | +| | TTAE.3G-24.012(R99T) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_012T.zip | + +### 10.4.7 TS 24.022 Radio Link Protocol (RLP) for Data and Telematic Services on the (MS-BSS) Interface and the Base Station System – Mobile-services Switching Centre (BSS-MSC) Interface + +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 7498) [43]. It is based on ideas contained in ISO/IEC 3309 [6], ISO/IEC 4335 [7] and ISO/IEC 7809 [8] (HDLC of ISO) as well as ITU-T Recs. X.25 [38] and Q.92x [19-22] (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 ITU-T Rec. X.212 | ISO/IEC 8886 [9]. + +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 [38] 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.006 and TS 29.007. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.022(R99) | 3.4.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.022 | 3.4.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11914 | +| 3GPP | T1.3GPP.24.022V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.022(R99F) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_002_R99F_.zip | +| | TTAE.3G-24.022(R99T) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_002_R99T_.zip | + +### **10.4.8 TS 24.030 Location Services (LCS); Stage 3 SS (MO-LR)** + +The document gives the stage 3 description of the Location Service (LCS) operations for mobile station. + +The group of location services operations is divided into two different classes: + +- Network initiated location services operations; +- Mobile initiated location services operations. + +| Organization | Document No. | Version | Status | Issued date | Location | +|---------------------|-------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.030(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.030 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11396 | +| TI | T1.3GPP.24.030V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-24.030(R99) | 1 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp24030r99.pdf | + +### **10.4.9 TS 24.067 Enhanced Multi-Level Precedence and Preemption 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 Preemption 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 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 TS 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 TS 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 procedure for Radio Resource management at layer 3-radio interface is defined in GSM 04.18 (for GSM) and TS 25.331 (for UMTS). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.067(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.067 | 3.1.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12812 | +| T1 | T1.3GPP.24.067V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.067(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_067_R99_.zip | +| TTC | JP-3GA-24.067(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp24067r99.pdf | + +### 10.4.10 TS 24.072 Call Deflection 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 GSM 04.02) 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.072(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.072 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7902 | +| T1 | T1.3GPP.24.072V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.072(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_072.zip | +| TTC | JP-3GA-24.072(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24072r99.pdf | + +### 10.4.11 TS 24.080 Mobile radio layer 3 supplementary service specification – Formats and coding + +The document contains the coding of information necessary for 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 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.080(R99) | 3.4.1 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.080 | 3.4.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11915 | +| T1 | T1.3GPP.24.080V341-2001 | 3.4.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.080(R99F) | 3.4.1 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_080_R99F_.zip | +| | TTAE.3G-24.080(R99T) | 3.4.1 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_080_R99T_.zip | +| TTC | TSJP-3GA-24.080(R99)v.3.4.1 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts24080r99.pdf | + +### 10.4.12 TS 24.081 Line Identification supplementary service; 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 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.081 is related specially to line identification supplementary services. + +Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and TS 23.09x-series. 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 TS 24.007 and TS 24.008. + +The following supplementary services belong to the line identification supplementary services and are described in the document: + +- Calling line identification presentation (CLIP); +- Calling line identification restriction (CLIR); +- Connected line identification presentation (COLP); +- Connected line identification restriction (COLR). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.081(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.081 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11398 | +| T1 | T1.3GPP.24.081V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.081(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_081_R99_.zip | +| TTC | JP-3GA-24.081(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp24081r99.pdf | + +### 10.4.13 TS 24.082 Call Forwarding supplementary service; Stage 3 + +This document specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) 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 GSM 04.10, the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.82 is related specially to call offering supplementary services. + +Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. GSM 03.82 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 GSM 04.07 and GSM 04.08. + +The following supplementary services belong to the call offering supplementary services and are described in the document: + +- Call forwarding unconditional (CFU); +- Call forwarding on mobile subscriber busy (CFB); +- Call forwarding on no reply (CFNR); +- Call forwarding on mobile subscriber not reachable(CFNRc). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.082(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.082 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7905 | +| TI | T1.3GPP.24.082V 300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.082(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_082.zip | +| TTC | JP-3GA-24.082(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24082r99.pdf | + +### 10.4.14 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 GSM 04.02) 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 GSM 04.10 the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.83 is related specially to call completion supplementary services. + +Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. + +GSM 03.83 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 GSM 04.07 and GSM 04.08. + +The following supplementary services belong to the call completion supplementary services and are described in the document: + +- Call waiting(CW); +- Call hold (HOLD). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.083(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.083 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7906 | +| TI | TI 3GPP.24.083V 300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.083(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_083.zip | +| TTC | JP-3GA-24.083(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24083r99.pdf | + +### **10.4.15 TS 24.084 MultiParty (MPTY) supplementary service; Stage 3** + +The document specifies the procedures used at the radio interface (Reference point Um as defined in GSM 04.02) for normal operation and invocation of MultiParty supplementary services. + +In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04 and the GSM 02.8x and GSM 02.9x-series. + +GSM 02.84 is related specially to MultiParty supplementary services. + +Technical realization of supplementary services is described in GSM 03.11 and the GSM 03.8x and GSM 03.9x-series. + +GSM 03.84 is related specially to MultiParty supplementary services. + +The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3-radio interface are defined in GSM 04.07 and GSM 04.08. + +The following supplementary service belongs to the MultiParty supplementary services and is described in the document: + +- MultiParty service (MPTY). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.084(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.084 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7907 | +| T1 | T1.3GPP.24.084V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.084(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_084.zip | +| TTC | JP-3GA-24.084(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24084r99.pdf | + +### 10.4.16 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 GSM 04.02) 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 GSM 04.10, the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.85 is related to the community of interest supplementary services. + +Technical realization of supplementary services is described in technical specifications GSM 03.11 and GSM 03.8x and 03.9x-series. GSM 03.85 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 GSM 04.07 and GSM 04.08. + +Signalling interworking for supplementary services between GSM 09.02 and GSM 04.08 and between GSM 09.02 and GSM 04.80 is defined in GSM 09.11. + +The following supplementary service belongs to the community of interest supplementary services and is described in this Technical Specification: + +- Closed User Group (CUG). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.085(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.085 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7908 | +| T1 | T1.3GPP.24.085V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.085(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_085.zip | +| TTC | JP-3GA-24.085(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24085r99.pdf | + +### 10.4.17 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 GSM 04.02) 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 GSM 04.10 the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.24 and 02.86 are related to the charging supplementary services. + +Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. GSM 03.86 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 GSM 04.07 and GSM 04.08. + +The following supplementary services belong to the charging supplementary services and are described in the document: + +- Advice of Charge (Information) (AoCI); +- Advice of Charge (Charging) (AoCC). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.086(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.086 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7909 | +| T1 | T1.3GPP.24.086V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.086(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_086.zip | +| TTC | JP-3GA-24.086(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24086r99.pdf | + +### 10.4.18 TS 24.087 User-to-User Signalling (UUS); Stage 3 + +This Technical Specification gives the stage 3 descriptions 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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.087(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.087 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7910 | +| T1 | T1.3GPP.24.087V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.087(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_087.zip | +| TTC | JP-3GA-24.087(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24087r99.pdf | + +### 10.4.19 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 GSM 04.02) 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 GSM 04.10 the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. + +Technical realization of supplementary services is described in GSM 03.11, GSM 03.8x and GSM 03.9x-series. + +The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3-radio interface are defined in GSM 04.07 and GSM 04.08. + +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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.088(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.088 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7911 | +| T1 | T1.3GPP.24.088V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.088(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_088.zip | +| TTC | JP-3GA-24.088(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24088r99.pdf | + +### 10.4.20 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.090(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.090 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7828 | +| T1 | T1.3GPP.24.090V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.090(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_090.zip | +| TTC | JP-3GA-24.090(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24090r99.pdf | + +### 10.4.21 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 GSM 04.02) 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 GSM 04.10 the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. GSM 02.91 is related specifically to call transfer supplementary services. + +The technical realization of supplementary services is described in GSM 03.11, GSM 03.8x and GSM 03.9x-series. GSM 03.91 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 GSM 04.07 and GSM 04.08. + +The following supplementary service belongs to the call transfer supplementary services and is described in the document: + +- Explicit Call Transfer (ECT). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.091(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.091 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7913 | +| T1 | T1.3GPP.24.091V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.091(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_091.zip | +| TTC | JP-3GA-24.091(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24091r99.pdf | + +### 10.4.22 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 GSM 04.02) 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 GSM 04.10 the general aspects of the specification of supplementary services at the layer 3-radio interface are given. + +GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. Technical specification GSM 02.93 is related specifically to the Completion of Calls to Busy Subscriber supplementary service. + +The technical realization of supplementary services is described in technical specifications GSM 03.11, GSM 03.8x and 03.9x-series. GSM 03.93 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 GSM 04.07 and GSM 04.08. + +The following supplementary service belongs to the call completion supplementary services and is described in the document: + +- Completion of Calls to Busy Subscriber (CCBS). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.093(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.093 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7914 | +| T1 | T1.3GPP.24.093V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.093(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_093.zip | +| TTC | JP-3GA-24.093(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24093r99.pdf | + +### **10.4.23 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 GSM 04.10 the general aspects of the specification of supplementary services at the layer 3-radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. + +Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and 02.9x-series. GSM 02.96 is related specially to name identification supplementary services. + +Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and 03.9x-series. Technical specification GSM 03.96 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 GSM 04.07 and GSM 04.08. + +The following supplementary service belongs to the name identification supplementary services and is described in this Technical Specification: + +- Calling name presentation (CNAP). + +| Organization | Document No. | Version | Status | Issued date | Location | +|---------------------|--------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.096(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.096 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7915 | +| TI | T1.3GPP.24.096V 300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-24.096(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-24_096.zip | +| TTC | JP-3GA-24.096(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp24096r99.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 are an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. + +TS 24.010 describes the general aspects of the specification of supplementary services at the layer 3 radio-interface. + +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.072, TS 22.08x, TS 22.09x-series and TS 22.135. TS 22.135 is related specifically to the Multicall supplementary service. + +The technical realization of supplementary services are described in TS 23.011, TS 23.072, TS 23.08x, 23.09x-series and TS 23.135. 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 TS 24.007 and TS 24.008. + +The following supplementary service is described in the document: + +- Multicall (MC). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-24.135(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 124.135 | 3.1.0 | Published | 19-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=11399 | +| T1 | T1.3GPP.24.135V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-24.135(R99) | 1 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp24135r99.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 narrowband 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.071(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.071.html | +| CWTS | CWTS-TSD-CN-26.071(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.071 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8052 | +| T1 | T1.3GPP.26.071V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.071(R99) | 3.0.1 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_071.zip | + +### 10.5.2 TS 26.073 AMR speech codec; C-source code + +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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.073(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.073.html | +| CWTS | CWTS-TSD-CN-26.073(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.073 | 3.2.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13604 | +| T1 | T1.3GPP.26.073V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.073(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_073_R99_.zip | + +### 10.5.3 TS 26.074 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). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.074(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.074.html | +| CWTS | CWTS-TSD-CN-26.074(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.074 | 3.1.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13618 | +| T1 | T1.3GPP.26.074V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.074(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_074_R99_.zip | + +### 10.5.4 TS 26.090 AMR speech Codec; Transcoding functions + +This Technical Specification (TS) 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 this TS and the fixed points computational description (ANSI-C code) of these requirements contained in TS 26.073, the description in TS 26.073 will prevail. The ANSI-C code is not described in this TS, see TS 26.073 for a description of the ANSI-C code. + +The transcoding procedure specified in this TS is mandatory for systems using the AMR speech codec. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.090(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.090.html | +| CWTS | CWTS-TSD-CN-26.090(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.090 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8053 | +| T1 | T1.3GPP.26.090V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.090(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_090.zip | + +### 10.5.5 TS 26.091 AMR speech codec; Error concealment of lost frames + +This specification 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 Equipment (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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.091(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.091.html | +| CWTS | CWTS-TSD-CN-26.091(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.091 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8054 | +| T1 | T1.3GPP.26.091V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.091(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_091.zip | + +### 10.5.6 TS 26.092 AMR speech codec; Comfort noise for AMR speech traffic channels + +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 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 points computational description of these requirements contained in TS 26.073, the description in TS 26.073 will prevail. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.092(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.092.html | +| CWTS | CWTS-TSD-CN-26.092(R99) | 3.0.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.092 | 3.0.1 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8055 | +| T1 | T1.3GPP.26.092V301-2001 | 3.0.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.092(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_092.zip | + +### 10.5.7 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. + +The 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 Type GSM\_AMR for the GSM system. 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.093(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.093.html | +| CWTS | CWTS-TSD-CN-26.093(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.093 | 3.3.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12816 | +| T1 | T1.3GPP.26.093V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.093(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_093_R99_.zip | + +### 10.5.8 TS 26.094 AMR speech codec; Voice Activity Detector for AMR speech traffic channels + +This document specifies two alternatives for the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in TS 26.093. Implementors 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.094(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.094.html | +| CWTS | CWTS-TSD-CN-26.094(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.094 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8073 | +| TI | T1.3GPP.26.094V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.094(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_094.zip | + +### 10.5.9 TS 26.101 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.101(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.101.html | +| CWTS | CWTS-TSD-CN-26.101(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.101 | 3.1.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10090 | +| TI | T1.3GPP.26.101V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.101(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_101_R99_.zip | + +### 10.5.10 TS 26.102 AMR speech codec; Interface to Iu and Uu + +The document specifies the mapping of the AMR generic frame format (TS 26.101) to the Iu Interface (TS 25.415) and the Uu Interface. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.102(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.102.html | +| CWTS | CWTS-TSD-CN-26.102(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.102 | 3.3.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13625 | +| TI | T1.3GPP.26.102V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.102(R99) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_102_R99_.zip | + +### 10.5.11 TS 26.103 Codec lists + +The Technical Specification outlines the Codec List in 3GPP including both systems, GSM and UMTS, to be used by the Bearer Independent Call Control (BICC) protocol to set up a call or modify a call in Transcoder Free Operation (TrFO). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.103(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.103.html | +| CWTS | CWTS-TSD-CN-26.103(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.103 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=9376 | +| TTA | TTAE.3G-26.103(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_103.zip | + +### 10.5.12 TS 26.104 AMR speech codec; Floating point C-code + +This Technical Specification (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 [44]) 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.104(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.104.html | +| CWTS | CWTS-TSD-CN-26.104(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.104 | 3.1.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12833 | +| TTA | TTAE.3G-26.104(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_104_R99_.zip | + +### 10.5.13 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.110(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.110.html | +| CWTS | CWTS-TSD-CN-26.110(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.110 | 3.1.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13628 | +| T1 | T1.3GPP.26.110V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.110(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_110_R99_.zip | + +### 10.5.14 TS 26.111 Codec for circuit switched Multimedia Telephony Service; Modifications to ITU-T Rec. H.324 + +In ITU-T Rec. H.324 [11], 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 3GPP networks. Note that this implicitly excludes the network interface and call setup procedures. Also excluded are any general introductions to the system components. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.111(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.111.html | +| CWTS | CWTS-TSD-CN-26.111(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.111 | 3.4.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12835 | +| T1 | T1.3GPP.26.111V 340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.111(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_111_R99_.zip | + +### 10.5.15 TS 26.131 Narrow-band (3,1 kHz) Speech & Video Telephony Terminal Acoustic Characteristics + +The document is applicable to any terminal capable of supporting narrow-band or wideband telephony, either as a standalone 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.131(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.131.html | +| CWTS | CWTS-TSD-CN-26.131(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.131 | 3.2.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13633 | +| T1 | T1.3GPP.26.131V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.131(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_131_R99_.zip | + +### 10.5.16 TS 26.132 Narrow-band (3,1 kHz) Speech & Video Telephony Terminal Acoustic Test Specification + +The document is applicable to any terminal capable of supporting narrow-band or wideband telephony, either as a standalone service or as the telephony component of a multimedia service. The 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-26.132(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/26.132.html | +| CWTS | CWTS-TSD-CN-26.132(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 126.132 | 3.2.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13635 | +| T1 | T1.3GPP.26.132V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-26.132(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-26_132_R99_.zip | + +## 10.6 27-series, Data + +### 10.6.1 TS 27.001 General on Terminal Adaptation Function(s) (TAF) for Mobile Station(s) (MS) + +The document is based on the principles of terminal adaptor functions presented in the ITU-T I-series of Recommendations (I.460 to V.110/I.463) [14]-[17]. + +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. + +In the TS 22.002 the bearer services are described. The general network configuration is described in TS 23.002 and the GSM PLMN access reference configuration is defined in GSM 04.02. The various connection types used in the GSM PLMN are presented in GSM 03.10. Terminology used in the present document is presented in GSM 01.04 (ETR 350), 3GPP TR 21.905 and TS 29.990. For support of data services between a PLMN and other networks see TS 29.007. + +The document is valid for a 2nd generation PLMN (GSM) as well as for a 3rd generation PLMN (UMTS). If text applies only for one of these systems it is explicitly mentioned by using the terms "GSM" and "UMTS". 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. + +Descriptions related to facsimile are not applied to UMTS. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-27.001(R99) | 3.8.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.001 | 3.8.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13644 | +| T1 | T1.3GPP.27.001V 380-2001 | 3.8.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-27.001(R99) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_001_R99_.zip | +| TTC | TS-3GA-27.001(R99)v.3.8.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts27001r99.pdf | + +### 10.6.2 TS 27.002 Terminal Adaptation Function(s) (TAF) for services using asynchronous bearer capabilities + +The document defines the interfaces and Terminal Adaptation Function(s) (TAF) 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 24.002 and TS 23.101). + +The general aspects of Terminal Adaptation Functions are contained in TS 27.001. + +The document covers support of these services for the following interfaces and procedures: + +- i) ITU-T Rec. V.14 [26] procedures; +- ii) ITU-T Rec. V.21 [27] DTE/DCE interface; +- iii) ITU-T Rec. V.22 *bis* [29] DTE/DCE interface; +- iv) ITU-T Rec. V.32 [34] DTE/DCE procedures; +- v) ITU-T Rec. I.420 [13] S interface; +- vi) ITU-T Rec. V.250 [36] signalling procedures. + +The asynchronous data rates between the MT and the IWF are defined in TS 22.002. + +Descriptions related to facsimile are not applied to UMTS. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-27.002(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.002 | 3.5.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12027 | +| T1 | T1.3GPP.27.002V 350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-27.002(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_002_R99_.zip | +| TTC | JP-3GA-27.002(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp27002r99.pdf | + +### 10.6.3 TS 27.003 Terminal Adaptation Function(s) (TAF) for service using synchronous bearer capabilities + +The document defines Terminal Adaptation Function(s) (TAF) 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 the 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. The present document covers support of synchronous data services (see TS 22.002) for the following interfaces and procedures: + +- ITU-T Rec. V.22 [28] DTE/DCE Interface; +- ITU-T Rec. V.22 *bis* [29] DTE/DCE Interface; +- ITU-T Rec. V.26 *ter* [33] DTE/DCE Interface; +- ITU-T Rec. X.21 *bis* [37] DTE/DCE Interface; +- ITU-T Rec. X.32 [39] Procedure; +- ITU-T Rec. V.25 *bis* [31] Procedure. + +LAPB is the only synchronous non-transparent protocol, which is considered in the present document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-27.003(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.003 | 3.5.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12028 | +| T1 | T1.3GPP.27.003V 350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-27.003(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_003_R99_.zip | +| TTC | JP-3GA-27.003(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp27003r99.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 Rec. V.25 *ter* [32]. 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 3GPP/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-4. + +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* [32] "command" state or "on-line command" state. + +The "Text" and "PDU" modes are not in themselves V.25 *ter* [32] states, but are simply sets of commands, which will operate in either the V.25 *ter* [32] "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* [32] "command" state or "on-line command" state. Whilst in the V.25 *ter* [32] command state, the MS is available to handle incoming and outgoing calls such as Data or Facsimile. + +![Diagram illustrating the relationship between V.25 ter states and SMS modes. A large circle represents the '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 to it by a vertical line. To the right of the rectangle is the text 'Q.1741.1 F10.6.4-1'.](85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg) + +The diagram shows a large circle at the top containing the text "V.25 *ter* 'command' state and 'on-line command' state". Inside this large circle are two smaller circles side-by-side: the left one is labeled "SMS text mode" and the right one is labeled "SMS PDU mode". Below the large circle, a vertical line connects it to a rectangular box labeled "SMS block mode". To the right of this box, the text "Q.1741.1 F10.6.4-1" is displayed. + +Diagram illustrating the relationship between V.25 ter states and SMS modes. A large circle represents the '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 to it by a vertical line. To the right of the rectangle is the text 'Q.1741.1 F10.6.4-1'. + +**Figure 10-4/Q.1741.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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-27.005(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/27.005.html | +| CWTS | CWTS-TSD-CN-27.005(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.005 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8036 | +| T1 | T1.3GPP.27.005V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-27.005(R99F) | 3.1.0 | Approved | 28-03-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_005F.zip | +| | TTAE.3G-27.005(R99T) | 3.1.0 | Approved | 28-03-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_005T.zip | + +### 10.6.5 TS 27.007 AT command set for 3G User Equipment (UE) + +The document specifies a profile of AT commands and recommends that this profile be used for controlling Mobile Equipment (ME) 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 Rec. V.25 *ter* [32]. The present document has also the syntax details used to construct these extended GSM/UMTS commands. Commands from ITU-T Rec. V.25 *ter* [32] and existing digital cellular standards (TIA IS-99 [40] and TIA IS-135 [41]) are used whenever applicable. Some of the new commands are defined such way that they can be easily applied to ME of networks other than GSM/UMTS. ITU-T Recs. T.31 [24] and T.32 [25] fax AT commands may be used for GSM/UMTS fax transmission from TE. GSM/UMTS Short Message Service AT commands are defined in TS 27.005. GPRS AT commands are defined in clause 10 of this specification. The present document assumes an abstract architecture comprising a TE (e.g. a computer) and a ME interfaced by a TA (see Figure 10-5). The span of control of the defined commands should allow handling of any physical implementation that this abstract architecture may lead to: + +- TA, ME and TE as three separate entities; +- TA integrated under the ME cover, and the TE implemented as a separate entity; +- TA integrated under the TE cover, and the ME implemented as a separate entity; +- TA and ME integrated under the TE cover as a single entity. + +The commands described in the present document may be observed on the link between the TE and the TA. However, most of the commands retrieve information about the ME, not about the TA. + +![Diagram illustrating the setup for Figure 10-5/Q.1741.1. It shows three main components: TE (Terminal Equipment), TA (Terminal Adaptor), and ME (Mobile Equipment). The TE is connected to 'User and applications' via a vertical double-headed arrow. The TE sends 'AT cmds' to the TA and receives 'Responses' from it. The TA sends 'ME status' to the ME and receives 'ME control' from it. The ME is connected to the 'Network' via a vertical double-headed arrow labeled 'Network messages'. A small text 'Q.1741.1 F10.6.5-1' is in the bottom right corner.](4f3c8d71b3b182deb469aed61870e3fe_img.jpg) + +``` + +graph LR + UA[User and applications] <--> TE + TE -- "AT cmds" --> TA + TA -- "Responses" --> TE + TA -- "ME status" --> ME + ME -- "ME control" --> TA + ME <--> |"Network messages"| Network + style UA fill:none,stroke:none + style Network fill:none,stroke:none + +``` + +Diagram illustrating the setup for Figure 10-5/Q.1741.1. It shows three main components: TE (Terminal Equipment), TA (Terminal Adaptor), and ME (Mobile Equipment). The TE is connected to 'User and applications' via a vertical double-headed arrow. The TE sends 'AT cmds' to the TA and receives 'Responses' from it. The TA sends 'ME status' to the ME and receives 'ME control' from it. The ME is connected to the 'Network' via a vertical double-headed arrow labeled 'Network messages'. A small text 'Q.1741.1 F10.6.5-1' is in the bottom right corner. + +Figure 10-5/Q.1741.1 – Setup + +Interface between TE and TA is intended to operate over existing serial (ITU-T Rec. V.24 [30]) 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 be set to eight-bits/ byte mode. (For infrared operation implementation refer informative references IrDA. + +For embedding AT commands and data during online data state refer to TTA IS-617 [42] and ITU-T Rec. V.80 [35].) Interface between TA and ME is dependent on the interface in the ME. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-27.007(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/27.007.html | +| CWTS | CWTS-TSD-CN-27.007(R99) | 3.8.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.007 | 3.8.0 | Published | 20-07-01 | http://pda.etsi.org/pda/home.asp?wki_id=13649 | +| TTA | TTAE.3G-27.007(R99F) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_007_R99F_.zip | +| | TTAE.3G-27.007(R99T) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_007_R99T_.zip | + +### 10.6.6 TS 27.010 Terminal Equipment to User Equipment (TE-UE) multiplexer protocol User Equipment (UE) + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-27.010(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/27.010.html | +| CWTS | CWTS-TSD-CN-27.010(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.010 | 3.3.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10096 | +| TTA | TTAE.3G-27.010(R99F) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_010_R99F_.zip | +| | TTAE.3G-27.010(R99T) | 3.3.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_010_R99T_.zip | + +### 10.6.7 TS 27.060 GPRS Mobile Stations supporting GPRS + +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). The 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-27.060(R99) | 3.5.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.060 | 3.5.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13652 | +| TI | T1.3GPP.27.060V 350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-27.060(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_060_R99_.zip | +| TTC | TS-3GA-27.060(R99)v.3.5.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts27060r99.pdf | + +### 10.6.8 TS 27.103 Wide Area Network Synchronisation + +This specification provides a definition of a Wide Area Synchronization protocol. The synchronization protocol is based upon IrMC level 4. + +The document covers Wide Area Network Synchronization between current and future mobile communication end-user devices, desktop applications and server-based information servers. This is a living document and, as such, it will evaluate new technologies (e.g. XML) for inclusion as they become readily available. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-27.103(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/27.103.html | +| CWTS | CWTS-TSD-CN-27.103(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 127.103 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=11465 | +| TI | T1.3GPP.27.103V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-27.103(R99F) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_103_R99F_.zip | +| | TTAE.3G-27.103(R99T) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-27_103_R99T_.zip | + +## 10.7 29-series, Signalling protocols (NSS) + +### 10.7.1 TS 29.002 Mobile Application Part (MAP) + +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. + +The present document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil these signalling needs. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.002(R99) | 3.8.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129 002 | 3.8.0 | Published | 04-09-01 | http://pda.etsi.org/pda/home.asp?wki_id=13702 | +| T1 | T1.3GPP.29.002V380-2001 | 3.8.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.002(R99) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_002_R99_.zip | +| TTC | TS-3GA-29.002(R99)v.3.8.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29002r99.pdf | + +### 10.7.2 TS 29.007 General requirements on interworking between the PLMN and the ISDN or PSTN + +The document identifies the Mobile-services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between: + +- PLMN and PSTN; +- 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 the document, the requirements for voice and non-voice (data) calls are considered separately. + +Descriptions related to facsimile are not applied to UMTS. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.007(R99) | 3.8.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.007 | 3.8.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13719 | +| T1 | T1.3GPP.29.007V380-2001 | 3.8.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.007(R99) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_007_R99_.zip | +| TTC | TS-3GA-29.007(R99)v.3.8.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29007r99.pdf | + +### 10.7.3 TS 29.010 Information Element Mapping between Mobile Station – Base Station System (MS – BSS) and Base Station System – Mobile-services Switching Centre (BSS – MCS) 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 TS 24.008) and parameters contained in MAP services sent over the MSC-VLR interface (TS 29.002) 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 (TS 29.002) 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 (GSM 08.08) and RANAP (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 GSM 09.08. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in GSM 09.07 and 09.08. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.010(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.010 | 3.5.0 | Published | 25-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13721 | +| TI | T1.3GPP.29.010V350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.010(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_010_R99_.zip | +| TTC | TS-3GA-29.010(R99)v.3.5.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29010r99.pdf | + +#### 10.7.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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.011(R99) | 3.0.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.011 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=7918 | +| TI | T1.3GPP.29.011V300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.011(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_011.zip | +| TTC | JP-3GA-29.011(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp29011r99.pdf | + +### 10.7.5 TS 29.013 Signalling interworking between ISDN supplementary services Application Service Element (ASE) and Mobile Application Part (MAP) protocols + +This Technical Specification 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 Completion of Calls to Busy Subscriber (CCBS) service between the ISDN CCBS-ASE and MAP. + +The MAP protocol for CCBS service is specified in TS 29.002. The ISDN CCBS-ASE protocol is specified in ETSI ETS 300 356-18 [4]. 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 Completion of Calls to Busy Subscriber (CCBS) service. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.013(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.013 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=9051 | +| T1 | T1.3GPP.29.013V 300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.013(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_013.zip | +| TTC | JP-3GA-29.013(R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp29013r99.pdf | + +### 10.7.6 TS 29.016 Serving GPRS Support Node (SGSN) – Visitors Location Register (VLR); Gs Interface Network Service Specification + +This document specifies or references the subset of MTP and SCCP, which is used for the reliable transport of BSSAP+ messages in the Gs interface. 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 VLRs. No segmentation at SCCP level is needed on the Gs interface. Only SCCP class 0 is used on the Gs interface. This document identifies the SCCP subset that should be used between an SGSN and a VLR. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.016(R99) | 3.1.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.016 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12032 | +| T1 | T1.3GPP.29.016V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.016(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_016_R99_.zip | +| TTC | JP-3GA-29.016(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp29016r99.pdf | + +### 10.7.7 TS 29.018 Serving GPRS Support Node (SGSN) – Visitors Location Register (VLR); Gs Interface Layer 3 Specification + +The document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors Location Register (VLR) interface for interoperability between GSM circuits 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 present document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.018(R99) | 3.6.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.018 | 3.6.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13727 | +| TI | T1.3GPP.29.018V 360-2001 | 3.6.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.018(R99) | 3.6.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_018_R99_.zip | +| TTC | TS-3GA-29.018(R99)v.3.6.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29018r99.pdf | + +### 10.7.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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.060(R99) | 3.8.0 | Published | 01-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.060 | 3.8.0 | Published | 14-08-01 | http://pda.etsi.org/pda/home.asp?wki_id=13730 | +| TI | T1.3GPP.29.060V 380-2001 | 3.8.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.060(R99) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_060_R99_.zip | +| TTC | TS-3GA-29.060(R99)v.3.8.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29060r99.pdf | + +### 10.7.9 TS 29.061 General Packet Radio Service (GPRS); Interworking between the Public Land Mobile Network (PLMN) supporting GPRS and Packet + +The document defines the requirements for Packet Domain interworking between a: + +- a) PLMN and PDN; +- b) PLMN and PLMN. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.061(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.061 | 3.5.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13733 | +| TI | T1.3GPP.29.061V350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.061(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_061_R99_.zip | +| TTC | TS-3GA-29.061(R99)v.3.5.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29061r99.pdf | + +### 10.7.10 TS 29.078 CAMEL; Stage 3 + +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 subset of the ETSI Core INAP CS-2 as specified by EN 301 140-1 [5]. Descriptions and definitions provided by ETSI EN 301 140-1 [5] are directly referenced by this standard in case no additions or clarifications are needed for the use in the CAP. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.078(R99) | 3.7.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.078 | 3.7.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13735 | +| TI | T1.3GPP.29.078V370-2001 | 3.7.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.078(R99) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_078_R99_.zip | +| TTC | TS-3GA-29.078(R99)v.3.7.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29078r99.pdf | + +### 10.7.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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.108(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.108 | 3.1.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12860 | +| TI | T1.3GPP.29.108V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-29.108(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp29108r99.pdf | + +### 10.7.12 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 3GPP system at the application level. + +The document gives the description of the systems needed only in the network utilising GLR as the delta document against TS 29.060. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.119(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.119 | 3.0.0 | Published | 17-05-00 | http://pda.etsi.org/pda/home.asp?wki_id=10331 | +| TI | TI.3GPP.29.119V 300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.119(R99) | 3.0.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_119_R99_.zip | +| TTC | TD-3GA-29.119(R99) | 1 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp29119r99.pdf | + +### 10.7.13 TS 29.120 Mobile Application Part (MAP) specification for Gateway Location Register (GLR); Stage 3 + +The document describes the signalling requirements and procedures used at network elements related to the GLR for MAP within the 3GPP system at the application level. + +The document gives the description of the systems needed only in the network utilising GLR as the delta document against TS 29.002. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.120(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129.120 | 3.1.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12036 | +| TI | TI.3GPP.29.120V 310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-29.120(R99) | 3.1.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-29_120_R99_.zip | +| TTC | TD-3GA-29.120(R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp29120r99.pdf | + +### 10.7.14 TS 29.198 Open Services Architecture API – Part 1 + +This document specifies the stage 3 of the Open Service Architecture (OSA) Application Programming Interface (API). The concepts and the functional architecture of the Open Service Architecture (API) are described by TS 23.127. This document describes the stage 3 specification of the Open Service Architecture API. + +The Open Service Architecture defines an architecture that enables service providers to make use of network functionality through an open standardized interface, i.e. the OSA API. The network functionality is described as Service Capability Servers. Within the OSA concepts the following Service Capability Servers are identified: + +- CAMEL Service Environment (see in TS 23.078) +- WAP execution platform (i.e. WAP Gateway & WAP Push Proxy) +- Home Location Register (HLR) + +The stage 3 documentation of the OSA R'99 API consists of two parts: + +– **The API specification (Part 1)** + +This is a normative stage 3 specification of the capabilities of the OSA R'99 API and describes the OSA API interface classes, containing class diagrams (see section 6), state transition diagrams (see section 7), data type definitions (section 8), and the IDLs (see section 9). + +– **The Mapping specification of the OSA R'99 API and the network protocols (Part 2)** + +This is an informative specification to provide an example how the OSA API can be mapped on the network protocols (i.e. MAP, CAP and WAP). It is an informative document, since this mapping is considered as implementation/vendor dependent. On the other hand this mapping will provide potential service designers with a better understanding of the relationship of the OSA API interface classes and the behaviour of the network associated to these interface classes. + +The OSA API Stage 3 activity is performed jointly with ETSI SPAN3's Service Provider Access Requirements activity. The contents of this document is related to the jointly owned 3GPP & ETSI document referred as the API Master document, which contains the API interface descriptions that are common and differentiated between ETSI & 3GPP. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-29.198(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 129 198 | 3.3.0 | Published | 04-05-01 | http://pda.etsi.org/pda/home.asp?wki_id=13899 | +| TI | T1.3GPP.29.198V 330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | TS-3GA-29.198(R99)v.3.3.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts29198r99.pdf | + +## 10.8 31-series, UIM User Identity Module + +### 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 present document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------| +| TTA | TTAE.3G-31.101(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-31_101.zip | + +### 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 manufacturers, 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, which may be used. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-31-102(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/31.102.html | +| CWTS | CWTS-TSD-CN-31.102(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 131.102 | 3.5.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13665 | +| TTA | TTAE.3G-31.102(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-31_102_R99_.zip | + +### 10.8.3 TS 31.110 Numbering system for telecommunication IC card applications + +The document describes the numbering system for Application Identifiers (AID) for 3G telecommunication Integrated Circuits (IC) card applications. + +The numbering system described in the document provides a means for an application and related services offered by a provider to identify if a given card contains the elements required by its application and related services. + +An AID is used to address an application in the card. It consists of a Registered application provider Identifier (RID) and a Proprietary application Identifier eXtension (PIX). + +The document describes the coding of the PIX. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-31.110(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/31.110.html | +| CWTS | CWTS-TSD-CN-31.110(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 131.110 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12041 | +| TTA | TTAE.3G-31.110(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-31_110_R99_.zip | + +### 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 present document defines: + +- The commands; +- The application protocol; +- The mandatory requirements on the UICC and ME for each procedure. + +The 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 present document does not specify any of the security algorithms, which may be used. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-31.111(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/31.111.html | +| CWTS | CWTS-TSD-CN-31.111(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 131.111 | 3.4.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13670 | +| TI | TI 3GPP.31.111V 340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-31.111(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-31_111_R99_.zip | + +## 10.9 32-series, Operation and Maintenance + +### 10.9.1 TS 32.005 Telecommunications Management; Charging and billing; 3G call and event data for the Circuit Switched (CS) domain + +The document is concerned with the administration of subscriber related event and call data. This includes both the collection of call data from, and the distribution of tariff data to, the Network Elements. + +The subscriber (IMSI) and mobile equipment (IMEI) related call and event data collected is employed by a number of management activities including billing and accounting, statistical analysis and customer care. + +The tariff data in the Network Elements is required to support the supplementary service "Advice of Charge". + +The aim of the document is to describe both the network management functions required and the data involved. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.005(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.005 | 3.4.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13675 | +| T1 | T1.3GPP.32.005V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-32.005(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-32_005_R99_.zip | +| TTC | TS-3GA-32.005(R99)v.3.4.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32005r99.pdf | + +### 10.9.2 TS 32.015 Telecommunications Management; Charging and billing; 3G call and event data for the Packet Switched (PS) domain + +The GSM and UMTS PLMN support a range of packet-based services in the same network. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions. The document describes the functionality of charging, which includes the General Packet Radio Service (GPRS) in GSM and UMTS, as defined in TS 22.060 and TS 23.060 (packet-based services). + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.015(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.015 | 3.5.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13676 | +| T1 | T1.3GPP.32.015V350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-32.015(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-32_015_R99_.zip | +| TTC | TS-3GA-32.015(R99)v.3.5.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32015r99.pdf | + +### 10.9.3 TS 32.101 3G Telecom 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, the 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 methodology to be followed in further steps of the UMTS Management Specifications. + +The document does not provide physical architectures of the UMTS Management System. These aspects are defined and discussed in more detail in TS 32.102. + +This document is applicable to all further 3GPP specifications regarding the Network Management of UMTS. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.101(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.101 | 3.4.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13677 | +| T1 | T1.3GPP.32.101V 340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-32.101(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-32_101_R99_.zip | +| TTC | JP-3GA-32.101(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp32101r99.pdf | + +#### 10.9.4 TS 32.102 3G Telecom Management Architecture + +The document identifies identify and standardises 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 document is applicable to all further Technical Specifications regarding the Telecom Management of UMTS. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.102(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.102 | 3.2.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11479 | +| T1 | T1.3GPP.32.102V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-32.102(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-32_102_R99_.zip | +| TTC | JP-3GA-32.102(R99) | 2 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp32102r99.pdf | + +#### 10.9.5 TS 32.104 3G Performance Management + +The document describes the requirements for the management of performance measurements and the collection of performance measurement data across a 3G network. 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 document is built upon is described. The requirements how an EM administers the performance measurements and how the results can be collected are defined in detail. The file format for the bulk transfer of performance measurement results to the NM is specified, the file transfer procedure utilized on that interface is described. A set of measurements available for collection by NEs is described; effort has been made to ensure consistency in the definition of measurements between different NEs. + +The following is beyond the scope of the document, and therefore the 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 minimize 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 data produced in multi-vendor 3G networks, 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. + +The document considers all the above aspects of Performance Management for a 3G network and its NEs defined in the 3G core Technical Specifications. However, only those aspects which are specific to a 3G system and particular to 3G-network operation are included in the document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.104(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.104 | 3.4.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12842 | +| T1 | T1.3GPP.32.104V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-32.104(R99) | 3.4.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-32_104_R99_.zip | +| TTC | JP-3GA-32.104(R99) | 3 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp32104r99.pdf | + +### 10.9.6 TS 32.106-1 Telecommunication Management; Configuration Management; Part 1: 3G configuration management; Concept and 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. + +The 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 inter working are ensured. In this way, the present 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. + +This document contains the specific definitions for the standardized N interface, which are necessary to follow for compliance to this specification. + +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 the Name Convention) are defined herein, used by this as well as by other specifications for Telecom Management produced by 3GPP. All these are included in Parts 2 through 8 of the document as follows: + +- Notification IRP Information Service version 1: 32.106 Part 2 +- Notification IRP CORBA solution set version 1:1: 32.106 Part 3 +- Notification IRP CMIP solution set version 1:1 32.106 Part 4 +- Basic Configuration Management IRP information model (including NRM) version 1: 32.106 Part 5 +- Basic Configuration Management IRP CORBA solution set version 1:1: 32.106 Part 6 +- Basic Configuration Management IRP CMIP solution set version 1:1: 32.106 Part 7 +- Name Convention for Managed Objects: 32.106 Part 8 + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-1(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-1 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11492 | +| TI | TI.3GPP.32.106-1 V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-32.106-1 (R99) | 1 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp32106-1r99.pdf | + +### 10.9.7 TS 32.106-2 Telecommunication Management; Configuration Management; Part 2: Notification Integration Reference Point; Information Service version 1 + +Network Elements (NEs) under management generate events to inform event receivers about occurrences within the network that may be of interest to event receivers. There are a number of categories of events. Alarm, as specified in Alarm IRP: Information Service TS 32.111-2, is one member of this category. + +The purpose of Notification IRP is to define an interface through which an IRPManager (typically a network management system) can subscribe to IRPAgent (typically an Element Manager (EM) or a NE) for receiving network events. It also specifies attributes carried in the network events. These attributes are common among all event categories. Attributes that are specific to a particular event category are not part of the present document. For example, *perceivedSeverity* is an attribute specific for alarm event category. This attribute is not defined in the document but in Alarm IRP TS 32.111-2. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|------------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-2(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-2 | 3.3.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13687 | +| TI | TI.3GPP.32.106-2 V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | TS-3GA-32.106-2 (R99)v.3.3.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32106-2r99.pdf | + +### **10.9.8 TS 32.106-3 Telecommunication Management; Configuration Management; Part 3: Notification Integration Reference Point; CORBA solution set version 1:1** + +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 (TS 32.106-2). + +| Organization | Document No. | Version | Status | Issued date | Location | +|---------------------|------------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-3(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-3 | 3.3.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13688 | +| T1 | T1.3GPP.32.106-3 V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | TS-3GA-32.106-3 (R99)v.3.3.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32106-3r99.pdf | + +### **10.9.9 TS 32.106-4 Telecommunication Management; Configuration Management; Part 4: Notification Integration Reference Point: CMIP solution set version 1:1** + +The document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Notification Integration Reference Point (IRP): Information Service defined in TS 32.106-2. This document contains: + +- An introduction to some concepts that are the base for some specific aspects of the CMIP interfaces. +- The GDMO definitions for the Alarm Management over the CMIP interfaces. +- The ASN.1 definitions supporting the GDMO definitions. + +| Organization | Document No. | Version | Status | Issued date | Location | +|---------------------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-4(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-4 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11496 | +| T1 | T1.3GPP.32.106-4 V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-32.106-4 (R99) | 1 | TTC published | 31-03-00 | http://www.ttc.or.jp/imt/std/jp32106-4r99.pdf | + +### **10.9.10 TS 32.106-5 Telecommunication Management; Configuration Management; Part 5: Basic Configuration Management IRP information model (including NRM) version 1** + +The document (Basic Configuration Management (CM) IRP: Information Model) defines 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 document is divided into three main parts: + +- Specifies a generic IRP Information Service with operations and notifications to be used by an 'IRPManager' to retrieve information on managed objects maintained by an 'IRPAgent'. +- Specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model – MIM) with definitions of Managed Object Classes. + +- Defines the UMTS management NRM by reusing this generic model either by direct reuse or subclassing. + +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 Basic CM IRP here provides a base for all CM-related resource modelling. + +To summarize, the Basic CM IRP has three main purposes: + +- 1) To define an interface for retrieval of Configuration Management information; +- 2) To define a generic Network Resource Model that constitutes a base from which other (more specialized) resource models can inherit; and +- 3) To define the applied UMTS management Network Resource Model. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|------------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-5(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-5 | 3.1.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13689 | +| T1 | T1.3GPP.32.106-5 V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | TS-3GA-32.106-5 (R99)v.3.1.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32106-5r99.pdf | + +#### 10.9.11 TS 32.106-6 Telecommunication Management; Configuration Management; Part 6: Basic Configuration Management IRP CORBA solution set version 1:1 + +The purpose of this *Basic Configuration Management (CM) IRP: Information Service CORBA Solution Set* is to define the mapping of the IRP information model (see TS 32.106-5) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment. + +The document does not describe any Network Resource Model (NRM) – this is described in TS 32.106-5. Please note that TS 32.106-5 defines an *IRP Information Model*, which comprises both an IS and NRM definition. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|------------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-6(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-6 | 3.1.0 | Published | 06-08-01 | http://pda.etsi.org/pda/home.asp?wki_id=13690 | +| T1 | T1.3GPP.32.106-6 V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | TS-3GA-32.106-6 (R99)v.3.1.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32106-6r99.pdf | + +#### 10.9.12 TS 32.106-7 Telecommunication Management; Configuration Management; Part 7: Basic Configuration Management IRP CMIP solution set version 1:1 + +The document defines a CMIP Solution Set for the Basic CM IRP introduced in TS 32.106-5. + +The version of this CMIP Solution Set is 1:1, where the first "1" means that it corresponds to the Information Model version 1, and the second "1" means that it is the first CMIP Solution Set corresponding to Information Model version 1. + +This document maps the protocol- and technology-independent operations, parameters, notifications and the Network Resource Model specified in the Basic CM IRP Information Model (Chapter 6 of TS 32.106-5) onto the corresponding CMIP/CMISE equivalences. The important technical aspects specific to this CMIP Solution Set are also described there. The GDMO definitions are introduced. This document also contains the ASN.1 definitions related to the GDMO definitions. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|------------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-7(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-7 | 3.1.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13692 | +| T1 | T1.3GPP.32.106-7 V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | TS-3GA-32.106-7 (R99)v.3.1.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32106-7r99.pdf | + +#### 10.9.13 TS 32.106-8 Telecommunication Management; Configuration Management; Part 8: 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, 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 of different technologies such as CMIP and CORBA, identical network resource name semantics must be conveyed in all IRPs. The document specifies one such name convention. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.106-8(R99) | 3.1.0 | Published | -02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.106-8 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11506 | +| T1 | T1.3GPP.32.106-8 V310-2001 | 3.1.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-32.106-8 (R99) | 1 | TTC published | 30-11-00 | http://www.ttc.or.jp/imt/std/jp32106-8r99.pdf | + +#### 10.9.14 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 the present document cover: + +- Fault surveillance and detection in the NEs; +- Notification of alarms (including alarm cease) and operational state changes; + +- Retrieval of current alarms from the NEs; +- Fault isolation and defence mechanisms in the NEs; +- Alarm filtering +- Management of alarm severity levels; +- Alarm and operational state data presentation and analysis at the Operations System (OS); +- Retention of alarm and operational state data in the NEs and the OS; and +- The management of tests. + +Any (re)configuration activity exerted from the EM as a consequence of faults will not be subject of the present document; these are described in TS 32.106. + +This document also 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.111-1(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.111-1 | 3.2.0 | Published | 07-11-00 | http://pda.etsi.org/pda/home.asp?wki_id=12052 | +| T1 | T1.3GPP.32.111-1 V320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-32.111-1 (R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp32111-1r99.pdf | + +#### 10.9.15 TS 32.111-2 Telecommunication Management; Fault Management; Part 2: Alarm Integration Reference Point: Information Service + +The document (TS 32.111 Part-2) 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 between EM-NM and NE-NM. + +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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.111-2(R99) | 3.3.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.111-2 | 3.3.0 | Published | 13-02-01 | http://pda.etsi.org/pda/home.asp?wki_id=12975 | +| T1 | T1.3GPP.32.111-2 V330-2001 | 3.3.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-32.111-2 (R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp32111-2r99.pdf | + +### 10.9.16 TS 32.111-3 Telecommunication Management; Fault Management; Part 3: Alarm Integration Reference Point: CORBA solution set version 1:1 + +The document specifies the CORBA Solution Set (SS) for the IRP whose semantics is specified in Alarm IRP: Information Service (IS) (TS 32.111-2). + +This document provides key architectural features supporting the SS. Defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Defines the usage of OMG CORBA Structured Event to carry information defined in notifications carrying alarm information. The document also describes the notification interface containing the push method. Annex A contains the IDL specification. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|------------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.111-3(R99) | 3.4.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.111-3 | 3.4.0 | Published | 27-04-01 | http://pda.etsi.org/pda/home.asp?wki_id=13694 | +| T1 | T1.3GPP.32.111-3 V340-2001 | 3.4.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | TS-3GA-32.111-3 (R99)v.3.4.0 | 1 | TTC published | 29-05-01 | http://www.ttc.or.jp/imt/ts/ts32111-3r99.pdf | + +### 10.9.17 TS 32.111-4 Telecommunication Management; Fault Management; Part 4: Alarm Integration Reference Point: CMIP solution set + +The document (TS 32.111 Part-4) defines the alarm integration reference point for the CMIP solution set. This document contains: + +- An introduction to some basic concepts of the CMIP interfaces. +- The GDMO definitions for the Alarm Management over the CMIP interfaces. +- The ASN.1 definitions supporting the GDMO definitions. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------| +| CWTS | CWTS-TSD-CN-32.111-4(R99) | 3.1.1 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 132.111-4 | 3.1.0 | Published | 22-08-00 | http://pda.etsi.org/pda/home.asp?wki_id=11505 | +| T1 | T1.3GPP.32.111-4 V311-2001 | 3.1.1 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTC | JP-3GA-32.111-4 (R99) | 2 | TTC published | 14-05-01 | http://www.ttc.or.jp/imt/std/jp32111-4r99.pdf | + +## 10.10 33-series, Security aspects + +### 10.10.1 TS 33.102 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 address 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-33.102(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/33.102.html | +| CWTS | CWTS-TSD-CN-33.102(R99) | 3.8.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 133.102 | 3.8.0 | Published | 16-05-01 | http://pda.etsi.org/pda/home.asp?wki_id=13695 | +| T1 | T1.3GPP.33.102V380-2001 | 3.8.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-33.102(R99) | 3.8.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-33_102_R99_.zip | + +### 10.10.2 TS 33.103 Security Integration Guidelines + +This technical specification defines how elements of the 3G-security architecture is to be integrated into the following entities of the system architecture. + +- Home Environment Authentication Centre (HE/AuC); +- Serving Network Visited Location Register (VLR/SGSN); +- Radio Network Controller (RNC); +- Mobile station User Identity Module (UIM); +- Mobile Equipment (ME). + +This specification is derived from 3G "Security architecture" TS 33.102. + +The structure of this technical specification is a series of tables, which describe the security information and cryptographic functions to be stored in the above entities of the 3G systems. + +For security information, this is in terms of multiplicity, lifetime, parameter length and whether mandatory or optional. + +For the cryptographic functions, the tables also include an indication of whether the implementation needs to be standardized or whether it can be proprietary. + +The equivalent information for the alternative Temporary Key proposal is included in an appendix to this document. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-33.103(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/33.103.html | +| CWTS | CWTS-TSD-CN-33.103(R99) | 3.5.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 133.103 | 3.5.0 | Published | 16-05-01 | http://pda.etsi.org/pda/home.asp?wki_id=13697 | +| T1 | T1.3GPP.33.103V350-2001 | 3.5.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-33.103(R99) | 3.5.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-33_103_R99_.zip | + +### 10.10.3 TS 33.105 Cryptographic Algorithm requirements + +This specification constitutes requirements specification for the security functions, which may be used to provide the network access security features defined in 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-33.105(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/33.105.html | +| CWTS | CWTS-TSD-CN-33.105(R99) | 3.7.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 133.105 | 3.7.0 | Published | 16-05-01 | http://pda.etsi.org/pda/home.asp?wki_id=13699 | +| TTA | TTAE.3G-33.105(R99) | 3.7.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-33_105_R99_.zip | + +### 10.10.4 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-33.106(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/33.106.html | +| CWTS | CWTS-TSD-CN-33.106(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 133.106 | 3.1.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8684 | +| TTA | TTAE.3G-33.106(R99) | 3.1.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-33_106.zip | + +### 10.10.5 TS 33.107 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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-33.107(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/33.107.html | +| CWTS | CWTS-TSD-CN-33.107(R99) | 3.2.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 133.107 | 3.2.0 | Published | 16-05-01 | http://pda.etsi.org/pda/home.asp?wki_id=13703 | +| TI | T1.3GPP.33.107V 320-2001 | 3.2.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-33.107(R99) | 3.2.0 | Approved | 19-12-01 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-33_107_R99_.zip | + +### 10.10.6 TS 33.120 Security Objectives and Principles + +The document gives the objectives and principles of 3GPP security. + +The principles state what is to be provided by 3G securities as compared to the security of second-generation systems. The principles will also ensure that 3G securities can secure the new services and new service environments offered by 3G systems. + +The objectives give general, high level requirements for 3GPP security, which will be expanded upon in TS 21.133. + +The priorities for the implementation of 3GPP security are also given. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-33.120(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/33.120.html | +| CWTS | CWTS-TSD-CN-33.120(R99) | 3.0.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 133.120 | 3.0.0 | Published | 01-02-00 | http://pda.etsi.org/pda/home.asp?wki_id=8050 | +| TI | T1.3GPP.33.120V 300-2001 | 3.0.0 | Approved | 02-11-01 | https://www.atis.org/atis/docstore/search.asp?committee=S24 | +| TTA | TTAE.3G-33.120(R99) | 3.0.0 | Approved | 13-07-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-33_120.zip | + +## 10.11 35-series, Algorithm specifications + +### 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 3GPP confidentiality algorithm *f8*, and the 3GPP integrity algorithm *f9*. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-35.201(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/35.201.html | +| CWTS | CWTS-TSD-CN-35.201(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 135.201 | 3.1.2 | Published | 27-08-01 | http://pda.etsi.org/pda/home.asp?wki_id=10405 | +| TTA | TTAE.3G-35.201(R99) | 3.1.0 | Approved | 20-12-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-35_201.zip | + +### 10.11.2 TS 35.202 Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi algorithm specification + +This specification gives a detailed specification of the 3GPP Algorithm Kasumi. Kasumi is a block cipher that forms the heart of the 3GPP confidentiality algorithm *f8*, and the 3GPP integrity algorithm *f9*. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-35.202(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/35.202.html | +| CWTS | CWTS-TSD-CN-35.202(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 135.202 | 3.1.2 | Published | 27-08-01 | http://pda.etsi.org/pda/home.asp?wki_id=10406 | +| TTA | TTAE.3G-35.202(R99) | 3.1.0 | Approved | 20-12-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-35_201.zip | + +### 10.11.3 TS 35.203 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 realization of the algorithms. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-35.203(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/35.203.html | +| CWTS | CWTS-TSD-CN-35.203(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 135.203 | 3.1.2 | Published | 27-08-01 | http://pda.etsi.org/pda/home.asp?wki_id=10407 | +| TTA | TTAE.3G-35.203(R99) | 3.1.0 | Approved | 20-12-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-35_203.zip | + +### 10.11.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. + +| Organization | Document No. | Version | Status | Issued date | Location | +|--------------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | ARIB STD-T63-35.204(R99) | 2.00 | ARIB SA Approved | 06-09-01 | http://www.arib.or.jp/IMT-2000/ARIB-STD/STD-T63/R99T/35.204.html | +| CWTS | CWTS-TSD-CN-35.204(R99) | 3.1.0 | Published | 02-02 | http://www.cwts.org/cwts/itu.htm | +| ETSI | TS 135.204 | 3.1.2 | Published | 27-08-01 | http://pda.etsi.org/pda/home.asp?wki_id=10408 | +| TTA | TTAE.3G-35.204(R99) | 3.1.0 | Approved | 20-12-00 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-35_204.zip | + +## 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.1902.2-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..efa964050364cc0a7e13ff9054a653a4e8d854d1 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/raw.md @@ -0,0 +1,911 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1902.2** + +(07/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**Bearer Independent Call Control protocol +(Capability Set 2) and Signalling System No. 7 +ISDN user part: General functions of messages +and parameters** + +ITU-T Recommendation Q.1902.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 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 | +| 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.* + +## **Bearer Independent Call Control protocol (Capability Set 2) and Signalling System No. 7 ISDN user part: General functions of messages and parameters** + +## **Summary** + +This Recommendation describes the messages, parameters and the signalling information contained within parameters used by the Bearer Independent Call Control (BICC) protocol and the ISDN user part, and their functions. + +###### **Source** + +ITU-T Recommendation Q.1902.2 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 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 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 | Definitions ..... | 1 | +| 4 | Abbreviations..... | 1 | +| 5 | Signalling messages..... | 4 | +| 6 | Signalling parameters ..... | 7 | +| 7 | Parameter information ..... | 12 | + + + +## ITU-T Recommendation Q.1902.2 + +## Bearer Independent Call Control protocol (Capability Set 2) and Signalling System No. 7 ISDN user part: General functions of messages and parameters + +## 1 Scope + +This Recommendation describes the elements of signalling information used by the Bearer Independent Call Control protocol and the ISDN user part and their functions. The encoding of these elements, the format of the messages in which they are conveyed, their applicability to the two protocols, and an indication of whether or not they are for national use, are described in ITU-T Rec. Q.1902.3. Throughout this Recommendation where a message, a parameter or parameter information relates to either physical circuits controlled by the ISDN user part or the BICC protocol call instances the notation "circuit/CIC" is used. Also, a generic term "node" is used to refer to signalling entities in either the ISUP (i.e. an exchange) or the BICC network (i.e. either an SN or an CMN) whenever a message, a parameter or parameter information is applicable to either. + +## 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 Q.1902.1 (2001), *Bearer Independent Call Control protocol (Capability Set 2): Functional description*. + +See ITU-T Rec. Q.1902.1 [1] for all the references used within this Recommendation. + +## 3 Definitions + +See ITU-T Rec. Q.1902.1 [1]. + +## 4 Abbreviations + +This 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 Set-up | +| DME | Digital Multiplexing Equipment | +| DNIC | Data Network Identification Code | +| ECT | Explicit Call Transfer | + +| | | +|--------|----------------------------------------| +| GSN | Gateway Serving Node | +| GVNS | Global Virtual Network Service | +| ID | Identifier | +| IN | Intelligent Network | +| ISC | International Switching Centre | +| LFB | Look For Busy | +| MCID | Malicious Call Identification | +| MLPP | Multi-Level 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 | +| SN | Serving Node | +| UID | User Interactive Dialogue | +| WGS-84 | World Geodetic System 1984 | + +For further abbreviations see ITU-T Rec. Q.1902.1 [1]. + +Table 1 defines the acronyms used for BICC and ISUP messages. + +**Table 1/Q.1902.2 – 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/CIC Group Blocking | +| CGBA | Circuit/CIC Group Blocking Acknowledgement | +| CGU | Circuit/CIC Group Unblocking | +| CGUA | Circuit/CIC Group Unblocking Acknowledgement | +| CON | Connect | +| COT | Continuity | +| CPG | Call Progress | +| CRG | Charge information | +| CQM | Circuit/CIC Group Query | +| CQR | Circuit/CIC 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/CIC Group Reset Acknowledgement | +| GRS | Circuit/CIC 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/CIC | +| SAM | Subsequent Address | +| SDM | Subsequent Directory Number | +| SGM | Segmentation | +| SUS | Suspend | +| UBL | Unblocking | +| UBA | Unblocking Acknowledgement | +| UCIC | Unequipped CIC | +| UPA | User Part Available | +| UPT | User Part Test | +| USR | User-to-user information | + +## 5 Signalling messages + +**5.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. + +**5.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 ITU-T Rec. Q.28); and +- start measurement of call duration for international accounting purposes (see ITU-T Rec. E.260). + +**5.3 Application Transport Message (APM):** A message sent in either direction to convey application information using the Application Transport mechanism. + +**5.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. + +**5.5 Blocking Acknowledgement message (BLA):** A message sent in response to a blocking message indicating that the circuit has been blocked. + +**5.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. + +**5.7 Charge information message (CRG):** Information sent in either direction for accounting and/or call charging purposes. + +**5.8 Circuit/CIC Group Blocking message (CGB):** A message sent to the node to permit the switching equipment or maintenance system to remove from (and return to) traffic a group of circuits/CICs. A node receiving a Circuit/CIC group blocking message must be able to accept incoming calls on the group of blocked circuits/CICs unless it has also sent a Circuit/CIC group blocking message. + +**5.9 Circuit/CIC Group Blocking Acknowledgement message (CGBA):** A message sent in response to a Circuit/CIC group blocking message to indicate that the requested group of circuits/CICs has been blocked. + +**5.10 Circuit/CIC Group Reset message (GRS):** A message sent to release an identified group of circuits/CICs 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/CICs in the group. If at the receiving end a circuit/CIC is remotely blocked, reception of this message should cause that condition to be removed. + +**5.11 Circuit/CIC Group Reset Acknowledgement message (GRA):** A message sent in response to a Circuit/CIC group reset message indicating that the requested group of circuits/CICs has been reset. The message also indicates the maintenance blocking state of each circuit/CIC. + +**5.12 Circuit/CIC Group Unblocking message (CGU):** A message sent to the node to cause cancellation in a group of circuits/CICs of a blocked condition invoked earlier by a Circuit/CIC group blocking message. + +**5.13 Circuit/CIC Group Unblocking Acknowledgement message (CGUA):** A message sent in response to a Circuit/CIC group unblocking message to indicate that the requested group of circuits/CICs has been unblocked. + +- 5.14 Circuit/CIC Group Query Message (CQM):** A message sent on a routine or demand basis to request the far-end node to give the state of all circuits/CICs in a particular range. +- 5.15 Circuit/CIC Group Query Response message (CQR):** A message sent in response to a Circuit/CIC group query message to indicate the state of all circuits/CICs in a particular range. +- 5.16 Confusion message (CFN):** A message sent in response to any message (other than a confusion message) if the node does not recognize the message or detects a part of the message as being unrecognizable. +- 5.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. +- 5.18 Continuity message (COT) (ISUP):** 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. +- 5.18a Continuity message (COT) (BICC):** A message sent in the forward direction indicating that the establishment of the bearer is complete up to and including the SN sending the COT message. +- 5.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. +- 5.20 Facility Accepted message (FAA):** A message sent in response to a facility request message indicating that the requested facility has been invoked. +- 5.21 Facility message (FAC):** A message sent in either direction at any phase of the call to request an action at another node. The message is also used to carry the results, error or rejection of a previously requested action. +- 5.22 Facility Reject message (FRJ):** A message sent in response to a facility request message to indicate that the facility request has been rejected. +- 5.23 Facility Request message (FAR):** A message sent from a node to another node to request activation of a facility. +- 5.24 Forward Transfer message (FOT):** A message sent in the forward direction on semi-automatic calls when the outgoing international exchange/GSN operator wants the help of an operator at the incoming international exchange/GSN. The message will normally serve to bring an assistance operator (see ITU-T Rec. Q.101) into the call if the call is automatically set up at the exchange/GSN. When the call is completed via an operator (incoming or delay operator) at the incoming international exchange/GSN, the message should preferably cause this operator to be recalled. +- 5.25 Identification Request message (IDR):** A message sent in the backward direction to request action regarding the malicious call identification supplementary service. +- 5.26 Identification Response message (IRS):** A message sent in response to the identification request message. +- 5.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. +- 5.28 Information Request message (INR):** A message sent by a node to request information in association with a call. + +- 5.29 Initial Address Message (IAM):** A message sent in the forward direction to initiate seizure of an outgoing circuit/CIC and to transmit number and other information relating to the routing and handling of a call. +- 5.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. +- 5.31 Loop Prevention message (LOP):** A message sent to convey information required by the ECT supplementary service. +- 5.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. +- 5.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. +- 5.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. +- 5.35 Pre-release Information message (PRI):** A message to be used with the Release message for the transport of information which cannot be sent in the Release message due to the compatibility rules (see ITU-T Rec. Q.1902.4 for BICC and ITU-T Rec. Q.764 for ISUP). +- 5.36 Release message (REL):** A message sent in either direction to indicate that the circuit/CIC 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. +- 5.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/CIC concerned has been brought into the idle condition. +- 5.38 Reset Circuit/CIC message (RSC):** A message sent to release a circuit/CIC 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/CIC is remotely blocked, reception of this message should cause that condition to be removed. +- 5.39 Resume message (RES):** A message sent in either direction indicating that the calling or called party, after having been suspended, is reconnected. +- 5.40 Segmentation Message (SGM):** A message sent in either direction to convey an additional segment of an overlength message. +- 5.41 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. +- 5.42 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. +- 5.43 Suspend message (SUS):** A message sent in either direction indicating that the calling or called party has been temporarily disconnected. +- 5.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. + +- 5.45 Unblocking Acknowledgement message (UBA):** A message sent in response to an unblocking message indicating that the circuit has been unblocked. +- 5.46 Unequipped CIC message (UCIC):** A message sent from one node to another when it receives a message on a circuit/CIC that is not provisioned for use. +- 5.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. +- 5.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. +- 5.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. + +## **6 Signalling parameters** + +- 6.1 access delivery information:** Information sent in the backward direction indicating that a SETUP message was generated at the destination access. +- 6.2 access transport:** Information generated on the access side of a call and transferred transparently in either direction between originating and terminating local nodes. The information is significant to both users and local nodes. +- 6.3 application transport parameter (APP):** Information sent in either direction to allow the peer-to-peer communication of Application Transport mechanism user applications. +- 6.4 automatic congestion level:** Information sent to the node to indicate that a particular level of congestion exists at the sending node. +- 6.5 backward call indicators:** Information relating to the characteristics of the connection, signalling path and called party sent in the backward direction. +- 6.6 backward GVNS:** Information sent in the backward direction used for a GVNS call to convey GVNS related information. +- 6.7 call diversion information:** Information sent in the backward direction indicating the redirecting reason and the notification subscription option of the redirecting user. +- 6.8 call diversion treatment indicators:** Information sent in the forward direction concerning treatment of call diversion. +- 6.9 call history information:** Information sent in the backward direction to indicate the accumulated propagation delay of a connection. +- 6.10 call offering treatment indicators:** Information sent in the forward direction concerning treatment of call offering. +- 6.11 call reference:** Information identifying a particular call. +- 6.12 call transfer number:** Information sent in both directions to identify each of the users involved in a call transfer. +- 6.13 call transfer reference:** Information used to convey a reference number associated with the ECT supplementary service. +- 6.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. +- 6.15 called IN number:** Information indicating the number which was received in the SSP as called party number in IAM and SAM messages. + +**6.16 called party number:** Information to identify the called party. + +**6.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. + +**6.18 Calling Party Geodetic Velocity Information:** Information that indicates velocity information associated with the Calling Party Geodetic Information. + +**6.19 calling party number:** Information sent in the forward direction to identify the calling party. + +**6.20 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. + +**6.21 carrier selection information:** Information sent in the forward direction to indicate the method (namely call per call or preselection) being used to invoke carrier selection. + +**6.22 cause indicators:** Information sent in either direction indicating the reason for sending the message (e.g. release message). + +**6.23 CCNR possible indicator:** Information sent in ACM (subscriber free)/CPG (alerting) to indicate the possibility to invoke a possible succeeding CCNR service request. + +**6.24 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. + +**6.25 charged party identification:** Information identifying the charged party, e.g. the account number. + +**6.26 circuit assignment map:** Information sent in the forward direction to identify the circuits used for an $N \times 64$ kbit/s connection. + +**6.27 circuit group supervision message type:** Information sent in a Circuit Group Blocking or Unblocking message, indicating that blocking (unblocking) is maintenance oriented or hardware oriented. + +**6.28 CIC group supervision message type:** Information sent in a CIC Group Blocking or Unblocking message, indicating that blocking (unblocking) is maintenance oriented. + +**6.29 circuit/CIC state indicator:** Information indicating the state of a circuit/CIC according to the sending node. + +**6.30 closed user group interlock code:** Information uniquely identifying a closed user group within a network. + +- 6.31 Coding Decoding Processing parameter:** Information sent in the Initial Address message, in support of DME tandeming avoidance procedure. This parameter indicates whether the voice call is compressed and the type of voice compression used. +- 6.32 collect call request:** Information sent in the forward direction indicating whether or not a call is a collect call. +- 6.33 conference treatment indicators:** Information sent in both directions concerning treatment of a multi-party call. +- 6.34 connected number:** Information sent in the backward direction to identify the connected party. +- 6.35 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. +- 6.36 continuity indicators (ISUP):** 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. +- 6.36a continuity indicators (BICC):** Information sent in the forward direction indicating that the establishment of the bearer is complete up to and including the SN sending the COT message. +- 6.37 correlation id:** Information used by the SCF for correlation with a previous connection (see ITU-T Rec. Q.1218 and Q.1228 – Definition of common data types). +- 6.38 display information:** Information sent in either direction indicating a text string to be sent to the user. +- 6.39 echo control information:** Indicators used to request activation and deactivation of echo control devices, and to respond to such requests. +- 6.40 end of optional parameters:** The end of optional parameters field indicates that there are no more optional parameters in the message. +- 6.41 event information:** Information indicating the type of event which caused a call progress message to be sent. +- 6.42 facility indicator:** Information sent in facility related messages identifying the facility or facilities with which the message is concerned. +- 6.43 forward call indicators:** Information relating to the characteristics of the connection, signalling path and calling party sent in the forward direction. +- 6.44 forward GVNS:** Information sent in the forward direction used for a GVNS call to convey GVNS related information. +- 6.45 generic digits:** Digit information, which is not suitable to be sent within numbering address parameter, sent in either direction to convey information between nodes due to a supplementary service. +- 6.46 generic notification:** Information sent in either direction intended to provide supplementary service notification to a user. +- 6.47 generic number:** Number information sent in either direction to enhance network operation or for supplementary services. +- 6.48 global call reference:** Information sent in forward direction to uniquely identify a call and correlate activities associated with that call. + +- 6.49 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 (ISUP)/call control associations (BICC) that are allowed to complete the call, assuming all subsequent intermediate nodes decrement the hop counter. +- 6.50 HTR Information:** Information identifying a Hard to Reach destination (see ITU-T Rec. E.412). +- 6.51 information indicators:** Information identifying the optional parameters included in a message. +- 6.52 information request indicators:** Information identifying the optional parameters requested in a message. +- 6.53 IN service compatibility:** Information sent in either direction indicating the IN Services being invoked in a call. +- 6.54 inter-nodal traffic group identifier:** Information sent in the forwards direction identifying to which logical traffic group the call belongs. This identifier is of significance only between two adjacent nodes. +- 6.55 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. +- 6.56 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. +- 6.57 MCID request indicator:** Information sent in the backward direction to request the identity of the calling party for the purpose of malicious call identification. +- 6.58 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. +- 6.59 message compatibility information:** Information sent in either direction indicating how a node should react in case this message is unrecognizable. +- 6.60 MLPP precedence:** Information relating specifically to the multi-level precedence and pre-emption service. +- 6.61 nature of connection indicators:** Information relating to the transmission path used on a connection. +- 6.62 network management controls:** Information sent in the forward direction concerning network management related action for a call. +- 6.63 network routing number:** Information to indicate the network routing number. The network routing number is a number used by the network to route a call. +- 6.64 network specific facility:** Service related information transparently transferred in either direction between the local node and the identified network which contracts the service. The information is significant to both user and the identified network. +- 6.65 number portability forward information:** Information sent in the forward direction concerning treatment of number portability. +- 6.66 optional backward call indicators:** Information relating to the characteristics of the connection, signalling path and called party sent in the backward direction. +- 6.67 optional forward call indicators:** Information relating to the characteristics of the connection, signalling path and called party sent in the forward direction. + +- 6.68 original called number:** Information sent in the forward direction when a call is redirected and identifies the original called party. +- 6.69 original called IN number:** Information sent in the forward direction indicating the original called IN number, if multiple IN interactions have taken place. +- 6.70 origination ISC point code:** Information sent in the initial address message of an international call, indicating the point code of the originating ISC. +- 6.71 parameter compatibility information:** Information sent in either direction indicating how a node should react in case the parameter is unrecognized. +- 6.72 pivot capability:** General information about allowed operation of pivot routing. +- 6.73 pivot counter:** Information indicating the number of pivot attempts (successful and unsuccessful) that a call has undergone. +- 6.74 pivot routing backward information:** Information sent in the backward direction in support of pivot routing. +- 6.75 pivot routing forward information:** Information sent in the forward direction in support of pivot routing. +- 6.76 pivot routing indicators:** Information used in the FAC message to indicate the pivot routing action to be performed at the next (failure action) or previous (request action or cancel action) node. +- 6.77 pivot status:** Information used to inform nodes regarding the possibility that an offer to pivot route will be accepted later. +- 6.78 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. +- 6.79 QoR capability:** Information sent in the forward direction to indicate that at least one node in the connection is able to perform the query to the database as described in the QoR procedures. +- 6.80 range and status:** Information sent in a group supervision message (e.g. Circuit/CIC Group Blocking) to indicate the range and status of circuits/CIC values affected by the action in the message. +- 6.81 redirect backward information:** Information sent in the backward direction in support of redirection. +- 6.82 redirect capability:** Information sent in the forward direction to indicate that at least one node in the connection is able to redirect the call and the call states in which the procedure is possible. +- 6.83 redirect counter:** Information indicating the number of invocations of redirection that a call has undergone. +- 6.84 redirect forward information:** Information sent in the forward direction in support of redirection. +- 6.85 redirect status:** Information used to inform nodes regarding the possibility that an offer to redirect will be accepted later. +- 6.86 redirecting number:** Information sent in the forward direction when a call is diverted, indicating the number from which the call was diverted. +- 6.87 redirection information:** Information sent in either direction giving information about call redirection or call rerouting. + +- 6.88 redirection number:** Information sent in the backward direction indicating the number towards which the call must be redirected or has been forwarded. +- 6.89 redirection number restriction:** Information sent in the backward direction indicating whether the diverted-to user allows the presentation of his number. +- 6.90 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. +- 6.91 SCF id:** Information indicating the SCF identifier (see ITU-T Q.1218 and Q.1228 – Definition of common data types). +- 6.92 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. +- 6.93 signalling point code:** Information sent to identify the signalling point in which an event occurred. +- 6.94 subsequent number:** Additional called party address digits sent subsequent to the sending of the called party number parameter. +- 6.95 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. +- 6.96 transit network selection:** Information sent in the initial address message indicating the transit network requested to be used in the call. +- 6.97 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). +- 6.98 transmission medium requirement prime:** Information sent in the forward direction indicating the fallback connection type in case of fallback. +- 6.99 transmission medium used:** Information sent in the backward direction indicating a resulting fallback connection type used for a call after fallback has occurred. +- 6.100 UID action indicators:** Information sent in the backward direction to instruct preceding nodes to enable a user interactive dialogue to occur. +- 6.101 UID capability indicators:** Information sent in the forward direction to inform succeeding nodes that on request a user interactive dialogue is possible. +- 6.102 user service information:** Information sent in the forward direction indicating the bearer capability requested by the calling party. +- 6.103 user service information prime:** Information sent in the forward direction indicating the additional bearer capability requested by the calling party. +- 6.104 user teleservice information:** Information sent in the initial address message indicating the Higher Layer Compatibility information requested by the calling party. +- 6.105 user-to-user indicators:** Information sent in association with a request (or response to a request) for user-to-user signalling supplementary service(s). +- 6.106 user-to-user information:** Information generated by a user and transferred transparently through the network between the originating and terminating nodes. + +## **7 Parameter information** + +- 7.1 access delivery indicator:** Information sent in the backward direction indicating that a SETUP message was generated at the destination access. + +- 7.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. +- 7.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. +- 7.4 **altitude:** Information that indicates the geodetic location of the calling party in terms of distance above or below the WGS-84 ellipsoid surface. +- 7.5 **altitude sign:** Information that indicates the geodetic location of the calling party in terms of above or below the WGS-84 ellipsoid surface. +- 7.6 **altitude uncertainty code:** Information indicating the level of uncertainty inherent to the associated altitude information. +- 7.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. +- 7.8 **APM-user information:** Information supplied by the APM-user application and conveyed in the Application Transport Parameter. +- 7.9 **application context identifier:** A value that uniquely identifies the application using the application transport mechanism. +- 7.10 **application transport instruction indicators (ATII):** Information sent in either direction indicating how a node should react in case the indicated application using the application transport mechanism is not supported. +- 7.11 **binary code:** A code allocated to a closed user group administered by a particular ISDN or data network. +- 7.12 **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. +- 7.13 **call identity:** Information sent in the call reference parameter indicating the identity of a call in a signalling point. +- 7.14 **call to be diverted indicator:** Information sent in the forward direction indicating whether diverting of the call shall be accepted. +- 7.15 **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. +- 7.16 **called party's category indicator:** Information sent in the backward direction indicating the category of the called party, e.g. ordinary subscriber or payphone. +- 7.17 **called party's status indicator:** Information sent in the backward direction indicating the status of the called party, e.g. subscriber free. +- 7.18 **calling party address request indicator:** Information sent in the backward direction indicating a request for the calling party address to be returned. +- 7.19 **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. +- 7.20 **calling party's category request indicator:** Information sent in the backward direction indicating a request for the calling party's category to be returned. + +- 7.21 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. +- 7.22 call reference ID:** Information sent in the Global Call Reference parameter indicating the reference associated to the call. +- 7.23 call reference length indicator:** Binary coded information indicating the number of octets in the Call Reference ID field. +- 7.24 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 Rec. Q.850. +- 7.25 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 node. +- 7.26 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. +- 7.27 charge indicator:** Information sent in the backward direction indicating whether or not the call is chargeable. +- 7.28 charge information request indicator:** Information sent in either direction requesting charge information to be returned. +- 7.29 charge information response indicator:** Information sent in response to a request for charge information indicating whether or not the requested information is included. +- 7.30 Call Instance Code:** Information identifying the instance of call control signalling. +- 7.31 Circuit Identification Code:** Information identifying the physical path between a pair of exchanges. +- 7.32 circuit group supervision message type indicator:** Information sent in a Circuit Group Supervision Message Type parameter, indicating that blocking (unblocking) is maintenance oriented or hardware oriented. +- 7.33 CIC group supervision message type indicator:** Information sent in a CIC Group Supervision Message Type parameter, indicating that blocking (unblocking) is maintenance oriented. +- 7.34 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. +- 7.35 coding standard:** Information sent in association with a parameter (e.g. cause indicators) identifying the standard in which the parameter format is described. +- 7.36 component ID tag:** Information identifying the type of component ID used in remote operations. +- 7.37 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 Rec. X.880 are used, viz.: + +| Component | X.880 PDU | +|---------------|--------------------| +| Invoke | Invoke{} PDU | +| Return Result | ReturnResult{} PDU | +| Return Error | ReturnError{} PDU | +| Reject | Reject{} PDU | + +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. + +**7.38 component type tag:** Information identifying the type of component used in remote operations. + +**7.39 Compression Status Indicator:** Information sent in the coding decoding processing parameter indicating whether the voice codecs applied at Digital Multiplexing Equipments were enabled or not with DME tandeming avoidance procedure. + +**7.40 confidence:** Information identifying the confidence by which it is known that the calling party lies within the associated shape description. + +**7.41 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. + +**7.42 connected line identity request indicator:** Information sent in the forward direction indicating a request for the connected party number to be returned. + +**7.43 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. + +**7.44 continuity indicator:** Information sent in the forward direction indicating whether or not a continuity message is to be expected. + +**7.45 credit:** Information sent in a connection request, indicating the window size requested by the signalling connection control part for an end-to-end connection. + +**7.46 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. + +**7.47 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. + +**7.48 destination address:** Address of the node where the APM-user application information shall be delivered. + +**7.49 destination address length:** Binary coded information indicating the number of octets in the Destination Address field. + +**7.50 diagnostic:** Information sent in association with a cause and which provides supplementary information about the reason for sending the message. + +**7.51 discard message indicator:** Information sent to inform another node to discard the related message, due to compatibility reasons. + +**7.52 discard parameter indicator:** Information sent to inform another node to discard the related parameter, due to compatibility reasons. + +**7.53 echo control device indicator:** Information indicating whether or not an echo control device is included in the connection. + +**7.54 ellipsoid arc:** Information that describes a point that is characterized by the coordinates of an ellipsoid point $o$ (the origin), inner radius $r1$ , uncertainty radius $r2$ , both radii being geodesic distances over the surface of the ellipsoid, the offset angle ( $\theta$ ) between the first defining radius of the ellipsoid arc and North, and the included angle ( $\beta$ ) being the angle between the first and second defining radii. The offset angle is within the range of $0^\circ$ to $359^\circ$ while the included angle is within the range from $1^\circ$ to $360^\circ$ . This is to be able to describe a full circle, $0^\circ$ to $360^\circ$ . + +This shape-definition can also be used to describe a sector (inner radius equal to zero), a circle (included angle equal to $360^\circ$ ) and other circular shaped areas. The confidence level with which the position of a target entity is included within the shape is also included. + +![Diagram of an ellipsoid arc. A vertical arrow points up to 'North'. A point 'Point (o)' is the origin. A radius line labeled 'r1' extends from 'Point (o)' at an angle 'theta' from the North arrow. Another radius line extends from 'Point (o)' at an angle 'beta' from the first radius. A cyan-colored arc connects the two radii. A second radius line labeled 'r2' extends from 'Point (o)' parallel to the 'r1' line. The label 'T11111990-01' is at the bottom right.](5f748e9d8e77de7b6a98e6039de7d0fd_img.jpg) + +Diagram of an ellipsoid arc. A vertical arrow points up to 'North'. A point 'Point (o)' is the origin. A radius line labeled 'r1' extends from 'Point (o)' at an angle 'theta' from the North arrow. Another radius line extends from 'Point (o)' at an angle 'beta' from the first radius. A cyan-colored arc connects the two radii. A second radius line labeled 'r2' extends from 'Point (o)' parallel to the 'r1' line. The label 'T11111990-01' is at the bottom right. + +**Figure 1/Q.1902.2 – Description of an ellipsoid arc** + +**7.55 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 2. + +Similar to the ellipsoid point, this shape description can be used to indicate points on the Earth's surface, or near the surface. + +![Figure 2: Description of an ellipse on the ellipsoid. The diagram shows a tilted ellipse. A vertical dashed line represents North. An angle θ is shown between the North line and the major axis of the ellipse. The semi-major axis is labeled r_major and the semi-minor axis is labeled r_minor. The ellipse is filled with diagonal hatching. The code T11103460-99 is at the bottom right.](b91e305493a4852dca57a801f54085c8_img.jpg) + +Figure 2: Description of an ellipse on the ellipsoid. The diagram shows a tilted ellipse. A vertical dashed line represents North. An angle θ is shown between the North line and the major axis of the ellipse. The semi-major axis is labeled r\_major and the semi-minor axis is labeled r\_minor. The ellipse is filled with diagonal hatching. The code T11103460-99 is at the bottom right. + +**Figure 2/Q.1902.2 – Description of an ellipse on the ellipsoid** + +**7.56 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 3. + +![Figure 3: Description of a circle sector. The diagram shows a sector of a circle originating from a point. A vertical dashed line represents North. An angle θ is shown between the North line and the first radius of the sector. An angle β is shown between the first and second radii. The radius is labeled r. The code T11103470-99 is at the bottom right.](a2c9fe78d22304889baddc26f4329ddf_img.jpg) + +Figure 3: Description of a circle sector. The diagram shows a sector of a circle originating from a point. A vertical dashed line represents North. An angle θ is shown between the North line and the first radius of the sector. An angle β is shown between the first and second radii. The radius is labeled r. The code T11103470-99 is at the bottom right. + +**Figure 3/Q.1902.2 – Description of a circle sector** + +**7.57 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 4 illustrates a point on the surface of the ellipsoid and its coordinates. + +![Figure 4: A 3D diagram of an ellipsoid showing a point on its surface. The point is defined by two coordinates: Latitude, which is the angle between the equatorial plane and the normal to the surface at that point, and Longitude, which is the angle between the Greenwich meridian and the meridian passing through the point. The diagram includes a vertical polar axis, a horizontal equatorial plane, and a meridian plane for the point. A small label 'T11103480-99' is at the bottom right.](e9a1dfde7b55d69a0a56f5bbe35328d4_img.jpg) + +Figure 4: A 3D diagram of an ellipsoid showing a point on its surface. The point is defined by two coordinates: Latitude, which is the angle between the equatorial plane and the normal to the surface at that point, and Longitude, which is the angle between the Greenwich meridian and the meridian passing through the point. The diagram includes a vertical polar axis, a horizontal equatorial plane, and a meridian plane for the point. A small label 'T11103480-99' is at the bottom right. + +**Figure 4/Q.1902.2 – 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. + +**7.58 ellipsoid Point with Altitude:** Information that describes a point at a specified distance above or below a point on the earth's surface. This is defined by an ellipsoid point with the given longitude and latitude and the altitude above or below the ellipsoid point. Figure 5 illustrates the altitude aspect of this description. + +![Figure 5: A 2D diagram illustrating altitude on an ellipsoid. It shows a circular cross-section of the ellipsoid. A point on the surface is shown with two altitude indicators: one pointing outwards from the surface labeled 'Point with positive altitude' and another pointing inwards from the surface labeled 'Point with negative altitude'. Both altitude distances are labeled 'Altitude'. A small label 'T11112000-01' is at the bottom right.](ca81500b365ed30190cb2d9c38fc1f84_img.jpg) + +Figure 5: A 2D diagram illustrating altitude on an ellipsoid. It shows a circular cross-section of the ellipsoid. A point on the surface is shown with two altitude indicators: one pointing outwards from the surface labeled 'Point with positive altitude' and another pointing inwards from the surface labeled 'Point with negative altitude'. Both altitude distances are labeled 'Altitude'. A small label 'T11112000-01' is at the bottom right. + +**Figure 5/Q.1902.2 – Description of an Ellipsoid Point with Altitude** + +**7.59 ellipsoid point with altitude and uncertainty ellipsoid:** Information that describes a point that is characterized by the coordinates of an ellipsoid point with altitude, distances $r1$ (the "Major Radius"), $r2$ (the "Minor Radius") and $r3$ (the "Uncertainty Altitude") and an angle of orientation $A$ (the "Orientation"). It describes formally the set of points which fall within or on the surface of a general (three dimensional) ellipsoid centred on an ellipsoid point with altitude whose real semi-major, semi-mean and semi-minor axis are some permutation of $r1$ , $r2$ , $r3$ with $r1 \geq r2$ . The $r3$ axis is aligned vertically, while the $r1$ axis, which is the semi-major axis of the ellipse in a horizontal plane that bisects the ellipsoid, is oriented at an angle $A$ (0 to 180 degrees) measured clockwise from north, as illustrated in Figure 6. + +![Figure 6/Q.1902.2 – Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid. The diagram shows a 3D ellipsoid with semi-axes labeled r1, r2, and r3. A vertical axis is indicated by an arrow pointing upwards. A point on the ellipsoid's surface is marked with a dot and labeled 'ellipsoid point with altitude'. A vector from the center to this point is labeled 'N'. The angle between the vertical axis and this vector is labeled 'A'. The identifier 'T11112010-01' is shown below the diagram.](ae02603e9e4b46477222bf72c1c7c7f6_img.jpg) + +Figure 6/Q.1902.2 – Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid. The diagram shows a 3D ellipsoid with semi-axes labeled r1, r2, and r3. A vertical axis is indicated by an arrow pointing upwards. A point on the ellipsoid's surface is marked with a dot and labeled 'ellipsoid point with altitude'. A vector from the center to this point is labeled 'N'. The angle between the vertical axis and this vector is labeled 'A'. The identifier 'T11112010-01' is shown below the diagram. + +**Figure 6/Q.1902.2 – Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid** + +The typical use of this shape is to indicate a point when its horizontal position and altitude are known only with a limited accuracy, but the geometrical contributions to uncertainty can be quantified. The confidence level with which the position of a target entity is included within the shape is also included. + +**7.60 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 7. 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. + +![Figure 7/Q.1902.2 – Description of uncertainty. The diagram shows a circle filled with diagonal hatching. A central point is marked with a dot. A radius line extends from this point to the right edge of the circle, labeled 'r'. The identifier 'T11103490-99' is shown below the diagram.](d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg) + +Figure 7/Q.1902.2 – Description of uncertainty. The diagram shows a circle filled with diagonal hatching. A central point is marked with a dot. A radius line extends from this point to the right edge of the circle, labeled 'r'. The identifier 'T11103490-99' is shown below the diagram. + +**Figure 7/Q.1902.2 – Description of uncertainty** + +**7.61 encapsulated application information:** Application information required to be transported by the application transport mechanism. + +**7.62 encoding scheme:** Information sent to indicate the coding type for the digit information, e.g. BCD-coded. + +**7.63 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. + +**7.64 end-to-end method indicator:** Information sent in either direction indicating the available methods, if any, for end-to-end transfer of information. + +- 7.65 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. +- 7.66 event indicator:** Information indicating the type of event which caused a call progress message to be sent. +- 7.67 event presentation restricted indicator:** Information sent in the backward direction indicating that the event should not be presented to the calling party. +- 7.68 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. +- 7.69 GVNS user group identification:** Information sent in the forward direction that uniquely identifies the GVNS customer. +- 7.70 feature code:** Information sent in either direction to invoke, accept, or reject a specific action for a supplementary service. +- 7.71 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 remaining four bits in the last octet have no digit information. +- 7.72 holding indicator:** Information sent in the backward direction indicating that holding of the connection is requested. +- 7.73 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. +- 7.74 Horizontal Velocity:** Horizontal velocity is characterized by the horizontal speed and bearing. The horizontal speed gives the magnitude of the horizontal component of the velocity of a target entity. The bearing provides the direction of the horizontal component of velocity taken clockwise from North. + +![Diagram illustrating Horizontal Velocity. A vertical arrow points upwards, labeled 'North'. A horizontal line at the bottom is labeled 'Horizontal Plane'. A diagonal arrow points upwards and to the right, labeled 'Magnitude'. An arc between the vertical 'North' arrow and the diagonal 'Magnitude' arrow is labeled 'Bearing', indicating the clockwise angle from North.](f2f0092624aaf8ad2bcb99a821409714_img.jpg) + +Diagram illustrating Horizontal Velocity. A vertical arrow points upwards, labeled 'North'. A horizontal line at the bottom is labeled 'Horizontal Plane'. A diagonal arrow points upwards and to the right, labeled 'Magnitude'. An arc between the vertical 'North' arrow and the diagonal 'Magnitude' arrow is labeled 'Bearing', indicating the clockwise angle from North. + +T11112020-01 + +**Figure 8/Q.1902.2 – Description of Horizontal Velocity** + +- 7.75 Horizontal and Vertical Velocity:** Horizontal and vertical velocity is characterized by horizontal speed, bearing, vertical speed and direction. The horizontal speed and bearing characterize the horizontal component of velocity. The vertical speed and direction provides the component of velocity of a target entity in a vertical direction. + +**7.76 Horizontal Velocity with Uncertainty:** Horizontal velocity with uncertainty is characterized by a horizontal speed and bearing, giving a horizontal velocity vector $\vec{V}$ , and an uncertainty speed $s$ . It describes the set of velocity vectors $\vec{v}$ related to the given velocity $\vec{V}$ as follows: + +$$|\vec{v} - \vec{V}| \leq s$$ + +![Figure 9/Q.1902.2 – Description of Horizontal Velocity with Uncertainty. The diagram shows a 2D coordinate system with horizontal axis v_x and vertical axis v_y. A vector V points from the origin to a point. A dashed circle of radius s is centered at the tip of vector V. Another vector v points from the origin to a point on the circumference of this circle. The distance between the tips of V and v is labeled s.](391ab9e5616ba6311161af4d7a93422b_img.jpg) + +T11112030-01 + +Figure 9/Q.1902.2 – Description of Horizontal Velocity with Uncertainty. The diagram shows a 2D coordinate system with horizontal axis v\_x and vertical axis v\_y. A vector V points from the origin to a point. A dashed circle of radius s is centered at the tip of vector V. Another vector v points from the origin to a point on the circumference of this circle. The distance between the tips of V and v is labeled s. + +**Figure 9/Q.1902.2 – Description of Horizontal Velocity with Uncertainty** + +**7.77 Horizontal and Vertical Velocity with Uncertainty:** Horizontal and vertical velocity with uncertainty is characterized by a horizontal speed and bearing, giving a horizontal velocity vector $\vec{V}_{x,y}$ , a vertical speed and direction giving a vertical velocity component $V_z$ , and uncertainty speeds $s_1$ and $s_2$ . It describes the set of velocity vectors $\vec{v}$ with horizontal and vertical components $\vec{v}_{x,y}$ and $v_z$ that are related to the given velocity components $\vec{V}_{x,y}$ and $V_z$ as follows: + +$$|\vec{v}_{x,y} - \vec{V}_{x,y}| \leq s_1$$ + +$$|v_z - V_z| \leq s_2$$ + +**7.78 inband information indicator:** Information sent in the backward direction indicating that inband information or an appropriate pattern is now available. + +**7.79 included angle:** Information identifying the included angle of a circle sector. + +**7.80 incoming echo control device request indicator:** Information sent to request the activation or deactivation of an incoming echo control device. + +**7.81 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. + +**7.82 IN service compatibility indication:** Information sent in either direction indicating the IN Services being invoked in a call. + +**7.83 instruction indicator:** Information indicating the reactions to be taken if an unrecognized message or unrecognized parameter is received. + +**7.84 internal network number:** Information sent to the destination node for specific numbers, e.g. roaming numbers indicating whether or not the number contained in the parameter is generated by the network. + +- 7.85 interworking indicator:** Information sent in either direction indicating whether or not Signalling System No. 7 and/or BICC is used in all parts of the network connection. +- 7.86 interworking to redirection indicator:** Information used to indicate whether interworking from pivot routing to redirection is allowed. +- 7.87 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. +- 7.88 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. +- 7.89 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. +- 7.90 ISDN access indicator:** Information sent in either direction indicating whether or not the access signalling protocol is ISDN. +- 7.91 ISDN user part indicator:** Information sent in either direction to indicate that the ISDN user part and/or BICC 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. +- 7.92 ISDN user part preference indicator:** Information sent in the forward direction indicating whether or not the ISDN user part and/or BICC is required or preferred in all parts of the network connection. +- 7.93 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. +- 7.94 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. +- 7.95 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. +- 7.96 latitude sign:** Information that indicates the geodetic location of the calling party in terms of northern or southern Hemisphere. +- 7.97 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 Rec. Q.850. +- 7.98 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. +- 7.99 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. +- 7.100 major radius:** Information identifying the size of the major axis of an ellipse on the ellipsoid shape description. +- 7.101 minor radius:** Information identifying the size of the minor axis of an ellipse on the ellipsoid shape description. +- 7.102 MLPP service domain:** Information sent in the forward direction to identify the specific MLPP service domain subscribed to by the calling user. + +- 7.103 MLPP user indicator:** Information sent in the backward direction to indicate that the called user is an MLPP user. +- 7.104 more instruction indicators:** Octets reserved for future use for enhancement of the instruction indicators. +- 7.105 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. +- 7.106 nature of address indicator:** Information sent in association with an address indicating the nature of that address, e.g. international number, national significant number, or subscriber number. +- 7.107 network discard indicator:** This indicator indicates that user-to-user information included in the call control message has been discarded by the network. +- 7.108 network ID:** Information identifying a network. +- 7.109 network identification plan:** Information sent to indicate the identification plan for identifying the network, e.g. ITU-T Rec. X.121 or E.212 (DNIC or MNIC). +- 7.110 network identification:** Information sent to identify a network. +- 7.111 network identity:** Information sent to identify the network which administers the supplementary service. +- 7.112 network ID length indicator:** Binary coded information indicating the number of octets in the Network ID field. +- 7.113 network specific facility indicator:** Information identifying specific facilities requested or provided. +- 7.114 node ID:** Information sent in the Global Call Reference parameter to identify the node that generated the call reference. +- 7.115 node ID length indicator:** Binary coded information indicating the number of octets in the Node ID field. +- 7.116 notification indicator:** Information sent in either direction intended to provide supplementary service notification to a user. +- 7.117 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. +- 7.118 Nth upgraded parameter name:** Information identifying the Nth parameter which has been upgraded for compatibility purposes. +- 7.119 number incomplete indicator:** Information sent to indicate whether the delivered number is complete or incomplete. +- 7.120 number portability status indicator:** Information sent in the forward direction identifying whether number portability checks have taken place at a node in the call path and also whether the called number is ported or non-ported. +- 7.121 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. +- 7.122 numbering plan indicator:** Information sent in association with a number indicating the numbering plan used for that number. +- 7.123 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. + +- 7.124 offset:** Information identifying the offset of a circle sector from North. +- 7.125 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. +- 7.126 orientation:** Information identifying the orientation of an ellipse on the ellipsoid. +- 7.127 original redirection reason:** Information sent in either direction indicating the reason why the call was originally redirected. +- 7.128 originating address:** Address of the node which has initiated the relationship with the remote APM-user application. +- 7.129 originating address length:** Binary coded information indicating the number of octets in the Originating Address field. +- 7.130 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. +- 7.131 outgoing echo control device request indicator:** Information sent to request the activation or deactivation of an outgoing echo control device. +- 7.132 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. +- 7.133 parameter tag:** Information identifying the type of parameter used in remote operations. +- 7.134 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. +- 7.135 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. +- 7.136 performing redirect indicator:** Information sent in the redirect forward information parameter that indicates a willingness to perform redirection for a particular reason. +- 7.137 pivot possible indicator:** Information used to indicate the call state until which the pivot routing is possible. +- 7.138 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 7.60) as shown in Figure 10. + +![Figure 10/Q.1902.2 – Description of a point with altitude and uncertainty. The diagram shows a sphere representing Earth with a coordinate system. A point is marked on the surface, and its position is defined by 'Longitude' (an angle in the equatorial plane) and 'Latitude' (an angle from the equator to the point). Above the surface point, a vertical dashed line indicates altitude, and a small dashed circle around the point represents the uncertainty in its horizontal position. A label 'T11103500-99' is at the bottom right.](008b6e24fa6aef654a11223efed035dd_img.jpg) + +Figure 10/Q.1902.2 – Description of a point with altitude and uncertainty. The diagram shows a sphere representing Earth with a coordinate system. A point is marked on the surface, and its position is defined by 'Longitude' (an angle in the equatorial plane) and 'Latitude' (an angle from the equator to the point). Above the surface point, a vertical dashed line indicates altitude, and a small dashed circle around the point represents the uncertainty in its horizontal position. A label 'T11103500-99' is at the bottom right. + +**Figure 10/Q.1902.2 – Description of a point with altitude and uncertainty** + +**7.139 polygon shape description:** Information that describes an arbitrary shape that is described by an ordered series of points (in the example pictured in Figure 11, 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. + +![Figure 11/Q.1902.2 – Description of a polygon. The diagram shows a polygon with five vertices labeled A, B, C, D, and E. The vertices are connected in the order A-B-C-D-E-A. The interior of the polygon is shaded with diagonal lines. A label 'T11103510-99' is at the bottom right.](11728b408ca6402f502858c9bc161c4a_img.jpg) + +Figure 11/Q.1902.2 – Description of a polygon. The diagram shows a polygon with five vertices labeled A, B, C, D, and E. The vertices are connected in the order A-B-C-D-E-A. The interior of the polygon is shaded with diagonal lines. A label 'T11103510-99' is at the bottom right. + +**Figure 11/Q.1902.2 – Description of a polygon** + +**7.140 precedence level:** Information sent in the forward direction to indicate the priority of the call. + +**7.141 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 in general and which do not relate to any specific component type. All of these are generated by the Remote Operation capability. They are: + +##### – Unrecognized Component + +The component type is not recognized as being one of those defined in 7.37 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 Rec. Q.1902.3. + +#### – Badly Structured Component + +The contents of the component do not conform to the encoding rules defined in ITU-T Q.1902.3. + +#### 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. + +**7.142 protocol class:** Information indicating the protocol class requested by the signalling connection control part for the end-to-end connection. + +**7.143 protocol profile:** Information sent in either direction to indicate the protocol used in the Remote Operations parameter. + +**7.144 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. + +**7.145 radius:** Information identifying the size of the radius of the associates circle sector shape description. + +**7.146 range:** Information sent in a circuit/CIC group supervision message (e.g. circuit/CIC group blocking) to indicate the range of circuits/CICs affected by the action in the message. + +**7.147 redirect possible indicator:** Information sent in the forward direction to indicate that at least one node in the connection is able to redirect the call and the call states in which the procedure is possible. + +**7.148 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. + +**7.149 redirecting reason:** Information sent in either direction indicating, in the case of calls undergoing redirection, the reason why the call has been redirected. + +**7.150 redirection counter:** Information sent in either direction indicating the number of redirections which have occurred on a call. + +**7.151 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 unrecognized. + +**7.152 return to invoking exchange call identifier:** Information used by the return to invoking node function to identify a call. + +**7.153 return to invoking exchange duration:** Information sent in the backward direction to indicate how long information will be retained at the invoking node to facilitate the return to invoking node function. + +- 7.154 return to invoking exchange possible:** Information sent in the forward direction to indicate the capability to make use of the return to invoking node call identifier and return to invoking node duration. +- 7.155 satellite indicator:** Information sent in the forward direction indicating the number of satellite circuits in the connection. +- 7.156 SCCP method indicator:** Information sent in either direction indicating the available SCCP methods, if any, for end-to-end transfer of information. +- 7.157 screening indicator:** Information sent in either direction to indicate whether the address/location information was provided by the user or network. +- 7.158 segmentation local reference (SLR):** A unique value to a call used to associate segments in an APM segmentation procedure. +- 7.159 send notification indicator:** Information sent to inform another node to send notification, due to compatibility reason, if the related message or parameter is unrecognizable. +- 7.160 sequence:** The sequence is an ordered set used in remote operations. +- 7.161 sequence indicator:** Used to indicate the beginning (first segment) of an APM segmentation procedure sequence. +- 7.162 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. +- 7.163 shape description:** Information that describes the geodetic location of the calling party. +- 7.164 signalling point code:** Information identifying the signalling point. +- 7.165 simple segmentation indicator:** Information sent in either direction to indicate that additional information will be forwarded in a segmentation message (unsolicited). +- 7.166 solicited information indicator:** Information sent in an information message to indicate whether or not the message is a response to an information request message. +- 7.167 status:** Information sent in a circuit/CIC group supervision message (e.g. circuit/CIC group blocking) to indicate the specific circuits/CICs, within the range of circuits/CICs stated in the message, that are affected by the action specified in the message. +- 7.168 T9 timer indicator:** Information sent in the forward direction to inform succeeding nodes that on request stopping of the timer T9 is possible. +- 7.169 timer instruction indicator:** Information sent in the backward direction to instruct preceding nodes to stop or not to start, respectively, the timer T9. +- 7.170 temporary alternative routing indicator:** Information sent in the forward direction indicating that a call is a temporary alternative routing controlled call. +- 7.171 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. +- 7.172 terminating network routing number:** A number sent in the forward direction which a terminating functional entity may use to complete a GVNS call to on-net locations. +- 7.173 through connection indicator:** Information sent in the forward direction to inform succeeding nodes that on request through-connection of the transmission path in both directions is possible. + +- 7.174 through connection instruction indicator:** Information sent in the backward direction to instruct preceding nodes to through-connect the transmission path in both directions. +- 7.175 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 unrecognized. +- 7.176 type:** Information sent in either direction to indicate whether the message is a request or a response. +- 7.177 type of digits:** Information sent in association with a generic digit to indicate the type of digit, e.g. authorization code. +- 7.178 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. +- 7.179 type of shape:** Information that indicates the format of the geodetic location information held in the associated shape description. +- 7.180 Type Of Voice Compression:** Information sent in coding decoding processing parameter indicating the voice codec type applied at Digital Multiplexing Equipments in preceding and/or succeeding network. +- 7.181 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 | 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.1902.3-200107-I_PDF-E/02ff9af2c63fedce97679915681f3475_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/02ff9af2c63fedce97679915681f3475_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..443982dbd8faf8e6776e6459116ee1c9bdb50e27 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/02ff9af2c63fedce97679915681f3475_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb835fe7953beb95241a127e3b00ee9666bb1d1393e2de1e7d0af51336036128 +size 8164 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/060648daa95345c57f019fc00ad75993_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/060648daa95345c57f019fc00ad75993_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c573f2be0c2ae59f763ae707c22970bfe529fe1b --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/060648daa95345c57f019fc00ad75993_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30b87a7ff7be578ec8e4780b3507d393885e747994309c743144cf9d51a5512a +size 17690 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1c9835c05c880ef8b7704d3d1a6f334f58fcc94 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:293e8d0760866a150d2bb426dd9790da44f39908cde22609fbc8c62c54fbc6bc +size 18010 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75f9ec7595f49d184946e44b2358d7263fbc7d73 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ff1073386ba7cb8d4ff7d4fcf71de963348218521f1ac811776d5d3624936cc +size 14917 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d06b0f1725c2dba0e645e4ae047900942d74b727 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:076c696e3417c530dd01aad5ff89dba2ce7f3fc26a78371e63ab78dded38c112 +size 20088 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/11bbed8294a393058c901641b8f50b5c_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/11bbed8294a393058c901641b8f50b5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0d33a8ad305e0580f1e81f092af1aa26bc42cef --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/11bbed8294a393058c901641b8f50b5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d96bc77413ea4e1cd8187556d75d3ff7817e4ffdcab6180de92e09eac6eac84 +size 33893 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/132ad076dd59b60fd549f7a612ed568b_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/132ad076dd59b60fd549f7a612ed568b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48cb21913a908c3fb70badb68ac71c05a550229a --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/132ad076dd59b60fd549f7a612ed568b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85d5ea45bf3cfbe681d9bc09e937dc3c1f246d03f59d399f878581e69555a87c +size 25500 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/195611c20b2dc7ed0fa3033392e22908_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bc9eca635e5cf1c7438e8e860f03d3dd1ca29d0 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/195611c20b2dc7ed0fa3033392e22908_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0834c52de3575d028d44c191983e8dc70d5418fe7b38a8c03d7aefbc37b3dc33 +size 7284 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5cba6719c88e6397d37fb649ff6c7a512fd4b2d --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4679cbe8c7442ae80669cc9f200a9e7146861b92030dd64d9aa3fa49c1404bc +size 18434 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/1fa325e34e0974a6426c93e541a7ee86_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/1fa325e34e0974a6426c93e541a7ee86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a8317179c56301f3bd1dbdd0cca538fc185e9b6 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/1fa325e34e0974a6426c93e541a7ee86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:391fb01c9490b75abbd81cb37f532416586d853104a30b1ae0d2a3878c994ae7 +size 24879 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c92cff17a03e1d9bea4c7c9a01541c9ed197456e --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b20a0e5fd629ef47baefbfc1b05326dd33a5c1bb0bae10f548be477017d97e3a +size 34786 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/21d8ca19de468e733e521605b1890767_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/21d8ca19de468e733e521605b1890767_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ec40670ccb45e3eabd918546a1d21c805db2247 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/21d8ca19de468e733e521605b1890767_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13a719609371972928cb3ffa11a3453f3aca934815a60e2a24981cf4dfc12aaf +size 29911 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efb725e6dbe61deb68feb9e78764e1b29195f3b1 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b704c06ea320d41af0f73f0b1c192cf18419fbaf309366c570c699cc790c7e9 +size 7629 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/29997432244f81212ee1e6c94f308f1b_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/29997432244f81212ee1e6c94f308f1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e19eaaf68786a62192806167e6e9493c24ae8967 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/29997432244f81212ee1e6c94f308f1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f813f64f1876776ce9564bbf8c1b1353dc14a649413402ab50c28402319beb8 +size 7181 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..126fdcf824467f0128c0ee4814b49dd542f704fd --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01e5685e64c1f4d1689fe9d25afe0ba7ea35ef55f3b38cd34b0cc8e3ecbdcc15 +size 10754 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-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.1902.3-200107-I_PDF-E/2f2911db53fbb1b2624f83a51555eb81_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2f2911db53fbb1b2624f83a51555eb81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f340c769087a871fd2e8979a03d3b22913ad5a8a --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2f2911db53fbb1b2624f83a51555eb81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33f639ba7cfc2d2901771157cd0efc7223a5266a623551a28ee21ba70125723a +size 7378 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c586bc3c21c5082174f09571cdc15962e845541 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03e716d2597c2298b367e8696841763be467786d02675ed3b146af3e386115bf +size 8043 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f01849a9f36794c7d2a6847a4f4d225aaea6675 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21bf000448eaac6e5d6386782c9dab4a90061aaa6287b5f7b210a93f440a0198 +size 7007 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..280c623850b92a11ef4be21719112221d11ae1cc --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e16966c4a2f858e182c06354be0b4e8794d1f58c174299b70e8544cc7b85d643 +size 17743 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/35656f382b89337af282106bd74b4f50_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/35656f382b89337af282106bd74b4f50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86c8e271ca5d076f87c5921623ba8ef88273335b --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/35656f382b89337af282106bd74b4f50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b4b4f677e26dce2de1221cf7dc2eed92d1821f636b05fc9e09daeedc078d22d +size 18665 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddd7c013595497f48c5f7ddbbccad8f168a3abde --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e24977e9d34c47537d012a7ce2bc689270576fa0225d5924a0814aa176585544 +size 16740 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/46b47a38697e3aedb09cccd7eba47192_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/46b47a38697e3aedb09cccd7eba47192_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2335acc181c5154af90256c58332e327893b40b --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/46b47a38697e3aedb09cccd7eba47192_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:362dbc3f50b0baae0769d370ae22d782050bc16ea8f1004a52eaf5fd7106103e +size 6628 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/52c2f44546dd3be7be45c369edbb0593_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/52c2f44546dd3be7be45c369edbb0593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b593d057536bf012fd75066e4156c4ea9f95cc1 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/52c2f44546dd3be7be45c369edbb0593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80c99166ef385138cbb82345c735560cdf0dfdae30b74e6b7eb8d6d00b777a2e +size 18556 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d579f3064aca0991af3f149ab928b7f62c21a0e8 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9228c4bdfaa8f04c159761e25bb794c89bfa83347a7d5a6f90b96d8f2a9b2e13 +size 6908 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/562a410f563a1f837a436dca179c4f72_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/562a410f563a1f837a436dca179c4f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f4b4ab296da072ab1a232c6f206c51a3246b906 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/562a410f563a1f837a436dca179c4f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53fd286b7e20c17ee761fc2fb99d0a8f6d0d7925352cefa7a68065f3e0a985c3 +size 19349 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3161e47d4a38d998202e8f4d8a388be654d38b2 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc4dc68a23b77307a582cf6cca637b6ab39df8ab1824c9af568a2c2dce82f4f7 +size 38827 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/59e29b37c5e332b0be088cde8c4d217e_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/59e29b37c5e332b0be088cde8c4d217e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47b783d663335f95957a1b0f0fbc09f39c267d4c --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/59e29b37c5e332b0be088cde8c4d217e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79461b6664483cf0cc6094c2f5a2cc30ee2e7fa6dd791f1a7fb89aa7ad7bb70a +size 9171 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a37ab0a114b18562b41fc7fef75dc535b3de56a --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99ee5d6c176fe7ad7fde3550a82a9fa716b6466e14df12d07a517702911584f2 +size 67321 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c07119ca739ba5e12e390f9708d0a7f1aa8bef7f --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83f7890d667c21ac55457e8a4fb80820ffec8b1f883db8ff91a436fce9c87969 +size 51064 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6116b1a533010c170fc526ec513ba0b8_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7c75069ddf8d017409b09c30c939428d29d481b --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f20294e21cd97658e9d0243637226497827127ccafca08ed79265bdfa6f68b5 +size 9561 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/61a49f3179b455e4d35242fc3d187a29_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/61a49f3179b455e4d35242fc3d187a29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74e8dd3bdb8ae3d810a835d8dde04558c25ffab9 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/61a49f3179b455e4d35242fc3d187a29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:120a82eb5ca02c8cb91c0382abe1927c0d6e2fe89ae4dd8496b9ecd9f0c26c15 +size 6948 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/61eda2ca38642c48593d7bb41fb34236_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/61eda2ca38642c48593d7bb41fb34236_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..930cc6842e9a666fe809eb44a4aa8df81096a49e --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/61eda2ca38642c48593d7bb41fb34236_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47f7dc64da7567a5ad3cd79ae63c10e054674c37273e53c6a914282ac5d97935 +size 10473 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/64323b705244afc70bf77babdacb6ce5_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/64323b705244afc70bf77babdacb6ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b34b9f1d4210d6c3e7304eeb2d37e5d326f4fd99 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/64323b705244afc70bf77babdacb6ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:136cd869231a2d98a4e51e116b643d6813fad3bf531b99e0863e0b2daeb57cf1 +size 36195 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6584b95e34ea1f0b67144aa841db0863_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6584b95e34ea1f0b67144aa841db0863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f64a8390d2e7f1b75fdcfd251f166097e4b6155 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6584b95e34ea1f0b67144aa841db0863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4ba3371a53da2e83d04fd555261dfaba6bfb6b79756e4c0af04f6e96dd01faf +size 37788 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/66e89867f97592fd4bfab0e4f2b2054f_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/66e89867f97592fd4bfab0e4f2b2054f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e30a8752525f0134e0e373914a9990d30dccaa04 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/66e89867f97592fd4bfab0e4f2b2054f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d2ada059905d0cef71d69919c56af86b4d15b8d6f254ef931f714bf819bb7b1 +size 7361 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6d2057d7e401741861ca63545a5d7d3b_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6d2057d7e401741861ca63545a5d7d3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d3167202b0c516eccb2839a92cd603829b8cdfc --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/6d2057d7e401741861ca63545a5d7d3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0366b9ac93c1be4cf00f151dbb95315e1f1a27d8c527ce10bcc31425ef2f820 +size 8842 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/704082cc3e11776bda29595c76411362_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/704082cc3e11776bda29595c76411362_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2945b788602a43298b8b3dadeeae526332d12c98 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/704082cc3e11776bda29595c76411362_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1d0f40d43403143511bdd6cb522848423f40c95456efe859693d3863f47ed08 +size 12181 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c43ebf740a04156a6c14a5c09ecc957e86751b0 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:618e27a6bbb386929528b31fca8271e1a6223f2b775045b067844c87f7560af7 +size 7348 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54da6c2b23529b631210eb3d305d4367f3414705 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:676ea2c949ea2f55f2fccb8d26e8de06922a7d3e5c5ec8c9216deb66efa79270 +size 7013 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/7dfe05137c554aca6bed20d67e52d739_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/7dfe05137c554aca6bed20d67e52d739_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..945425a1cb21c39cf486a4ca095c7b8011dc6866 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/7dfe05137c554aca6bed20d67e52d739_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:772d0b99e799b497214d1f90c4a6f00bcae7ca07f6a48090ffb7dd9c05344fee +size 7728 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/7e30ab71b6390dfe2edbbb473254abb7_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/7e30ab71b6390dfe2edbbb473254abb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea6b2570b06d9fa9cd854fcbc34c074dab811eef --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/7e30ab71b6390dfe2edbbb473254abb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8c8fca36a09539c3a9ffc4b54d8e696ac65f90e251799cc386f2940e4132129 +size 31270 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70f7fb922ce728722ecaae7000b213c9574b06e5 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5db1ed73e25f3317640135aef664f5ab8e60355b826adf508d55738c7066ed2 +size 38833 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de81d5b79aefc35d15f8eaec60aad1049925fdc7 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:424d921581d486415d90d6d799021b161c65d51fc96fb7d8aa742bbc406c24a7 +size 38458 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/85b53faf49a839f512153285c78fbbdb_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/85b53faf49a839f512153285c78fbbdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26e0b5d765b9f8b37201a2b7e3ed71bde9627d4d --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/85b53faf49a839f512153285c78fbbdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62bb92d695e0c63170553eec0fe7e3703640306330d147e79138e6d94df63753 +size 18186 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6a3a13d6aef143df142218f460807943b529f31 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c3aab6c9ab300bc0506c1aaffb7a3fd7e7f0587a3463d021e29ef3f7d994cdc +size 11795 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd1109fb0921e8de3fcffdd870e671261b71e57d --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53e753b2774d7ab2e76e71f4ce1275ae07e8a19882780abaa5be110ff8c8152a +size 8780 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..429aaa3320b1f8b4d67cb1271e3fd9d05f8a9be1 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6aa32e75dafec126e5eb4498206e92cae2d2f04b63dadab79c64c53c7233173a +size 8997 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1774211a137fae87e97e4a4bbfab1e7161a94317 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2947220bf277813cc19ffecdc3e8e8b40b0225947f3257ce912e9f5592159d0c +size 8016 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/91aa06b0972f24b4889588fa0e3a331a_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/91aa06b0972f24b4889588fa0e3a331a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47d1aba5c21345e534c74c51e998c2e070a138c3 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/91aa06b0972f24b4889588fa0e3a331a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:186d9f7a7936dbbeab9a930534ae4d3edcc67d15d5a294f7cf8fc33355e531fb +size 37965 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..056444009f84ba8271a4c35bab95cc1436a1c309 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d84967cd317ee7bac1ce7f8cac88b71ef3aa9c78a9791bc27b94e3adb14a694 +size 36304 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/985267cff5b5d65ce5c180ff2ef37118_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/985267cff5b5d65ce5c180ff2ef37118_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..317710b7173941e83091658471854033bc4cd544 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/985267cff5b5d65ce5c180ff2ef37118_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18c15682d48d05be53ab831a62c150d61901b1386c4400096335bc7e953363eb +size 12885 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a67d1977c450d9142da89692ef859d900c6738c8 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ef2a365253339851673a504cbb6c89c8ec969c3f0016db199533384757c0f4a +size 9838 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9cd7ec4a653f07d02def283cb6f2309e_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9cd7ec4a653f07d02def283cb6f2309e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6419899f683bbeed7cc2184daa3209a25cea59c6 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9cd7ec4a653f07d02def283cb6f2309e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c807615627d66514845714eeac612aa7e2c36580dfe39bb159b3d010a493cf7d +size 7128 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e88fbc7ca35f1ec0f2fe03a6ee4f0368746981e --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33643b834bc77aaf260782b7920ced97f370eff7820a999f248bae08bd4b157a +size 8165 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d5f460aa67004c1bf63941580b9a347d913204e --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2ac3460d102e35e7f612a1ef3d1b902e7d2f26ec6aa137665240b3be00d933e +size 17934 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a057800564be3506d2d87b6a4daee25b_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a057800564be3506d2d87b6a4daee25b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc4f7cb604eeb68e20b873d34c5c57aa79f191a0 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a057800564be3506d2d87b6a4daee25b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c42aefb04d2f52952d10ecade0b5feea53a61fe46228761bb6451964d4a9e45c +size 11704 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d39ba66e4270fa9739f58062d2f185f5e49139f --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e42e36814becc06037688f14ac7789ab1613a71f82517a1068258c32a6337a06 +size 28433 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1091931b7f24a418732293ff8e0d5509f1d55943 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:584059a23fac826e4d9c1f59870f94d8f7958827602e4f8a96f379a9e9646b1b +size 19526 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a849a9dd421d00bb95ba7ce6112498e2_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a849a9dd421d00bb95ba7ce6112498e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..661826d5d9c799277750e0391823ded607871056 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a849a9dd421d00bb95ba7ce6112498e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c58cac10719d2f0a35740b138a2b896ba8a23cc8e7170634acb60466461dd579 +size 31083 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a9b204d7d6890b85948aec7ce5c94cdf_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a9b204d7d6890b85948aec7ce5c94cdf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ecbbf455ab7d462ced3c2c10abbdd69884d87f1 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/a9b204d7d6890b85948aec7ce5c94cdf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88164c0a9bfda3085313c6eb5f42665dd6324116c8f9632d4955d04268f48f17 +size 10203 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/aa22da43c463563d3d0035722bd79449_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/aa22da43c463563d3d0035722bd79449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..773abff7a79f10c593a1c2b2131d3c1309250429 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/aa22da43c463563d3d0035722bd79449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:293e576e58cf6755bf0a39961ebacc2118290716d541c102611b9983c58a8467 +size 22116 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eef03892fc49bf68c63279a0a7875ae433c91507 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ca51ba02e157ecf760bfd88db78856dfa9d83ec323ee7d1ec204119f26c8fca +size 36586 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b22a15a7e2c0c793b57b823f796d8290ed6737fe --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:600c970044d8ab880b84dc3fcdf3a4c32d3577150656074bf827f194da342905 +size 44962 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f76d10e929197205781409bd9b402bdf456c5a9b --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c568d1d20a3939ef3dcdf12e5ac6fdd227b0540f60531d38e43d7ec317c1576b +size 7374 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a042f5280f17a69ff4057839680e8d81fdb09a5f --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:745b433220c91138a846c0068ef875b42319efcbad078d8e1bfd14380ca32bec +size 24159 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b81d1613e285a9353171cdc5ef97a1f0_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b81d1613e285a9353171cdc5ef97a1f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5479ea4455d483c7293fa646856fd5b43915d325 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b81d1613e285a9353171cdc5ef97a1f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5ca24ee206ebae0bca3a3088d5610853cc38c07804eb849decd7ecb962dd4e4 +size 6704 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b8efedb73292a798b3f2050f9335cae6_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b8efedb73292a798b3f2050f9335cae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8ac5ffe2a1cff366c6f83d8d9057d6650da3af5 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/b8efedb73292a798b3f2050f9335cae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60fd032de94c2d6c78483ad83bd2351f44cd903645a064cdc5cab761209c06ef +size 10951 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..326726dbc838bc7bb0bfffbe1212e178f23ef41d --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f5efeb9260f81ec9cad053ec351787e90da6c6295b1c45c586216257c733114 +size 11441 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bbddeb46a8bee133d49003273fcfc8dd_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bbddeb46a8bee133d49003273fcfc8dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eae14331ed2bb555d2f9ec6590405b7f576da048 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bbddeb46a8bee133d49003273fcfc8dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afd6062b97238696fcabe9c7e9c507f0ce893e1c87742fece95a8f7786458e79 +size 6925 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff574c8ccc12d935b3905b5186b6bb21addc6902 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b627d5ccbab7da03678b36fe42bfd542dd92f9a7521a39c9bb3031d8f6ac482d +size 7655 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a74024e7533f7b4c3ea005b20944053a8daacdb --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75222d2044d7987f190912202fccab576af52cb82b31f7292dcafd8e6f8ea6d9 +size 38292 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4892870316c2dfe5ff456ab8c48aa93e63fb1584 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e7464c32f252e5d6e1736931c4877af4ae168f80e10cf4aa10efc184b7a1164 +size 6955 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dce4efc607145e825032089d1812a18e7a2e7041 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c3c1824c1b95419e4229bac630861678f63fb2577f700ecb59050d70748f6a6 +size 48399 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c4f4e64722ba94da46d926c92ef35b46_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c4f4e64722ba94da46d926c92ef35b46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beec25514c254e2e635c96405b4abffdaf45b677 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c4f4e64722ba94da46d926c92ef35b46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:930fc031f0d27f56f60650c4aef90a140608f73cdc4b99c4490a3c2d38d85e89 +size 8363 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c5c767928d086da5347036f88309fc7a_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c5c767928d086da5347036f88309fc7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33a0b9f08eeb391ae42144190914b02eb3e18067 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c5c767928d086da5347036f88309fc7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:325c09aa0a00ed0736a358b49a96e397c1f87f0646ae5e168df92491b2065d66 +size 38010 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c64555b7f91435b01997807dbb4bcc4c_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c64555b7f91435b01997807dbb4bcc4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81404c0c86aaea679b5719d344b9a9a47241e2f9 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c64555b7f91435b01997807dbb4bcc4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c86839a9d873e78c4a3a6fb49e23756b5f723c9cbf8912f97d9c0c7a98ab4bc +size 24958 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16752f640699f1a165a1629b992d4e1cc49f00c4 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7659a42eebbfc5c38baa9d07c406f1b3619cfac323174fd555e5a7f776b40f84 +size 27254 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df48adf275327bb8372a974c588fa6cff592cb4a --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:092201b50c980ae6737b9f8baaf7d7370ba35914ad5b0f8aa34661c198b36d2d +size 11925 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9be6ed52e897b211a0355043dfe7f7e99bf81f8b --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e39c032e35bd76fc2f1a8153ddcc5221a85a05d4e70a2d4b2b032cc5b47bd40 +size 6821 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3af8a24763f3b030c2e43ca7d80ddb20d1b1564a --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:036e4bedb50e2b98c7b228017fe0a38bfaf6b7412276da887498bb9073d97d31 +size 9251 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d3a0b3f8c929b3435f4f6af13af1531f9a98ba1 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94af859cb1d7bbcfc21f51c30a761bf5ab6fca2efe79e8775f21471cfae036e2 +size 7336 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e09da2bfde404c3650abf1697d4d90d864180f9 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa4ec7bdc73278b8916135c6c72454686e3b3b038a0c9ff05efd814a72d4c13 +size 8706 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/df65c22a46ec3e7285e44de67d3a59cf_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/df65c22a46ec3e7285e44de67d3a59cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6f9c4de218ad48a66b73bf34c274ea261d24bfd --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/df65c22a46ec3e7285e44de67d3a59cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e118f0edc135bab740085f9d218afcd7a94cb81e5af345c1e2e15ed6415ca1de +size 6785 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dfcc01409c46b852d874f5bf45539d77297a719 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:407feb28d8d6768ea1d5fcaf645ac8596f479f8ed52843a1e5a3967c0f2ee1b6 +size 25087 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e48a7aa9d3880694350259852fefbef2_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e48a7aa9d3880694350259852fefbef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd6e0d22cfa0b40c2d038dfdc572a6957340bb24 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e48a7aa9d3880694350259852fefbef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3e3c57e5bc51e55f48c5020f8838b9837f2dee76bc2f395a4b98b6f92580035 +size 13765 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e534e903e6dae8a582643bfd9f89254c_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e534e903e6dae8a582643bfd9f89254c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85ac363906a3344e9a4a68ab65402954c6677eac --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e534e903e6dae8a582643bfd9f89254c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93f56b154d161dbf61c8d24105c52335af8ff73b8d85e80e61564829e74c402b +size 6654 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e694eeb983c07b3dd631358292db6af1_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e694eeb983c07b3dd631358292db6af1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2c462c1eb8774877848be297a5fbb23e2cd88f2 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e694eeb983c07b3dd631358292db6af1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17c2072e65bb8f69d66b8f5bf73acbff1269c0d4664400b3ae9baf3a9bfb165a +size 8182 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a05f77927e432b23a7c005e51ea74be8bb81cb78 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af69da4e345b9528fb186f85ce5b8f69beee46ab9d4978c6cc85554e3bacad4c +size 7003 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e0d2bb3f3b594373de67cf73966296b74e5f354 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaa0093be6f7f33c21bcd7b44848a6410058e6516eded5eb029d58b238ba2bf1 +size 7169 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3acd8679b76635a7e6fbf3c164a898fca350544 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db52bdb4d6edcab1de02ce422562ffe75ce723205a51f53a676171b1b3cf4bd8 +size 7488 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7e715ec2b0ad5e46bfdaa1869c4de8991747099 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:813166b94272e6d04fdb912f6d29735b7fe5b6047fba6ca43ffb51fb686b142f +size 36557 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d22067f2ab598a7b29f8a228cb92f80f6b97dd5c --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e6c881ed52e9bf87b8fc540b3106470828b28a7c333d057ca8bb67431eef8ec +size 6856 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b99a2547c38d8da660af6b0fff6e7f409ec98ffb --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eb1ce45be3dad1d13b256a367643666d1e014abbb718540baac8f26bcc8f354 +size 7574 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f8163a5402ad1756cf135c42bc22c5f5_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f8163a5402ad1756cf135c42bc22c5f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77ca29f2a11b00a701255f26effa8f974253fce3 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/f8163a5402ad1756cf135c42bc22c5f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a8d373b4b7d4ecd2b00414a38be42195ca20447973a95a9f8a96ebd305305d1 +size 39769 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fa3258abeaa067802e97eb4d1901572f_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fa3258abeaa067802e97eb4d1901572f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64ac9fef5f5fbb41d4ee692a6ae73a669a7b9846 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fa3258abeaa067802e97eb4d1901572f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa4c4dbacd7e7489e1fbf2d65173fe99e9bc7dc20c4886a075dd5f7edd6523ed +size 7265 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceed4c096f0dad0380b64542e3681ed977bef719 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8443fe43bf4d6e0a819ff77005de5fc3d3dc0ed3afd23c7a2bc02d246068c98d +size 31579 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d21a353d7d96dd6587e6a4fd39bba51dbdb8ddc0 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a716059b7d1564b0379a0cb365815e6e019241d662f57443dfdc8de563910a7 +size 8065 diff --git a/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7eb6db8fc1b41319f1b2a1fe614e8d8aa6da2ea2 --- /dev/null +++ b/marked/Q/T-REC-Q.1902.3-200107-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ec687315951e00fd489df1b11c8568be29fe243b7b0717df15f13aa9b19f649 +size 109390 diff --git a/marked/Q/T-REC-Q.1912.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1912.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/Q/T-REC-Q.1912.2-200107-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.1912.2-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Q/T-REC-Q.1912.2-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c3cd17bc7546f7f6ba067129dd57f0cf42772a9 --- /dev/null +++ b/marked/Q/T-REC-Q.1912.2-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:134065fbe82922459297f5205006e5b69e6a7bda36960e8ff1f51e1e85c478dc +size 71991 diff --git a/marked/Q/T-REC-Q.1912.2-200107-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.1912.2-200107-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccfeb2de8f1b1c06bdbad452ff92e9d34c5575a3 --- /dev/null +++ b/marked/Q/T-REC-Q.1912.2-200107-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:524744c548d7db6eb1fda16cf50e0faf08ad99305db42e8841e61512a7e9903f +size 68388 diff --git a/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..543eca593dbedfbbf45b55db2def98a21b330a7c --- /dev/null +++ b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/raw.md @@ -0,0 +1,332 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1912.3** + +(07/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**Interworking between H.323 and the Bearer +Independent Call Control protocol** + +ITU-T Recommendation Q.1912.3 + +(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 | +| 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. + +# **Interworking between H.323 and the Bearer Independent Call Control protocol** + +## **Summary** + +This Recommendation defines the signalling interworking between the Bearer Independent Call Control (BICC) protocol and H.323. It defines in particular the signalling interworking between the BICC protocol and the H.225.0 Multimedia Call Control protocol based on the interworking between H.225.0 and the ISDN User Part (ISUP) protocol of Signalling System No. 7. + +## **Source** + +ITU-T Recommendation Q.1912.3 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 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..... | 2 | +| 3 | Definitions ..... | 3 | +| 4 | Abbreviations..... | 3 | +| 5 | General considerations..... | 3 | +| 6 | Interworking considerations ..... | 4 | +| 6.1 | General..... | 4 | +| 6.2 | Prevention of speech clipping..... | 4 | +| 6.3 | Codec negotiation and out-of-band transport of DTMF and tone information ..... | 4 | +| 6.4 | Interworking of ISDN supplementary services ..... | 4 | +| | Appendix I – Guidelines BICC/H.323 interworking for end-to-end codec negotiation..... | 5 | +| I.1 | Introduction..... | 5 | +| I.2 | H.323 to BICC interworking ..... | 5 | +| I.2.1 | If the H.245 procedures are used (with a separate H.245 control channel or using the H.245 encapsulation method) ..... | 5 | +| I.2.2 | If Fast Connect procedure is used..... | 6 | +| I.3 | BICC to H.323 interworking ..... | 6 | +| I.3.1 | If H.245 procedures are used (with a separate H.245 control channel or using the H.245 encapsulation method) ..... | 7 | +| I.3.2 | If Fast Connect procedure is used..... | 7 | + + + +# **Interworking between H.323 and the Bearer Independent Call Control protocol** + +## **1 Scope** + +This Recommendation defines the signalling interworking between the Bearer Independent Call Control (BICC) protocol and H.323. + +It defines in particular the signalling interworking between the BICC protocol and the H.225.0 Multimedia Call Control protocol in an H.323 network based on the interworking between H.225.0 and the ISDN User Part (ISUP) protocol of Signalling System No. 7. + +The interworking between H.245 and BICC is for further study (some aspects are addressed in 6.3 and Appendix I). + +BICC is the protocol defined in ITU-T Recommendations Q.1902.1 to Q.1902.4 [5]. The Multimedia Call Control protocol is defined in ITU-T H.225.0 [1] for a network in accordance with ITU-T H.323 [3]. ISUP is the protocol defined in ITU-T Recommendations Q.761 to Q.764 [4]. + +The description of the signalling interworking between the H.225.0 Multimedia Call Control protocol and the BICC protocol in this Recommendation builds upon: + +- The signalling interworking between the H.225.0 Multimedia Call Control protocol and the ISDN User Part (ISUP) protocol of Signalling System No. 7 as defined in Annex C/H.246 [2]. +- The signalling interworking between the Bearer Independent Call Control (BICC) protocol and the ISDN User Part (ISUP) protocol of Signalling System No. 7 as defined in ITU-T Q.1912.1 [6]. + +The scope of this Recommendation with regard to the signalling interworking between the H.225.0 Multimedia Call Control protocol and the BICC protocol is as shown in Figure 1. + +![Diagram illustrating the scope of Recommendation Q.1912.3 for BICC/H.225.0 interworking. The diagram shows an ISDN network (H.323 network) on the left and a BICC network using separate call and bearer signalling on the right. The ISDN network contains H.323 call/bearer control and H.245. The BICC network contains N-ISUP call/bearer control, CSF-N, BICC, BIWF, and BCF-N. The scope of this Recommendation is indicated by a dashed box around the N-ISUP call/bearer control and CSF-N components. The scope of Annex C/H.246 is indicated by a dashed box around the H.323 call/bearer control. The scope of ITU-T Q.1912.1 is indicated by a dashed box around the CSF-N, BICC, BIWF, and BCF-N components. Arrows indicate the flow of H.225.0, H.245, BICC, and Bearer control signals.](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +The diagram illustrates the interworking between an H.323 network (ISN) and a BICC network. On the left, the H.323 network contains H.323 call/bearer control and H.245. On the right, the BICC network contains N-ISUP call/bearer control, CSF-N, BICC, BIWF, and BCF-N. The scope of this Recommendation (Q.1912.3) is highlighted by a dashed box encompassing the N-ISUP call/bearer control and CSF-N. The scope of Annex C/H.246 is indicated by a dashed box around the H.323 call/bearer control. The scope of ITU-T Q.1912.1 is indicated by a dashed box around the CSF-N, BICC, BIWF, and BCF-N components. Arrows show the flow of H.225.0, H.245, BICC, and Bearer control signals between the networks. + +Diagram illustrating the scope of Recommendation Q.1912.3 for BICC/H.225.0 interworking. The diagram shows an ISDN network (H.323 network) on the left and a BICC network using separate call and bearer signalling on the right. The ISDN network contains H.323 call/bearer control and H.245. The BICC network contains N-ISUP call/bearer control, CSF-N, BICC, BIWF, and BCF-N. The scope of this Recommendation is indicated by a dashed box around the N-ISUP call/bearer control and CSF-N components. The scope of Annex C/H.246 is indicated by a dashed box around the H.323 call/bearer control. The scope of ITU-T Q.1912.1 is indicated by a dashed box around the CSF-N, BICC, BIWF, and BCF-N components. Arrows indicate the flow of H.225.0, H.245, BICC, and Bearer control signals. + +Figure 1/Q.1912.3 – Scope of this Recommendation for BICC/H.225.0 interworking + +## 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 H.225.0 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems.* +- [2] ITU-T H.246 Annex C (2000), *ISDN user part function – H.225.0 Interworking.* +- [3] ITU-T H.323 (2000), *Packet-based multimedia communications systems.* +- [4] ITU-T Q.761 to Q.764 (1999), *Specifications of Signalling System No. 7 – ISDN user part (ISUP).* +- [5] ITU-T Q.1902.1 to Q.1902.4 (2001), *Specifications of the Bearer Independent Call Control protocol (BICC).* +- [6] ITU-T Q.1912.1 (2001), *Interworking between Signalling System No. 7 ISDN user part (ISUP) and the Bearer Independent Call Control protocol.* +- [7] ITU-T H.450.x-family (1998 onwards), *Procedures and the signalling protocols between H.323 entities for the control of supplementary services.* +- [8] ITU-T Implementors Guide (2001) for H.323, H.225.0, H.245, H.246, H.283, H.235, H.450-series and H.341 Recommendations. +- [9] ITU-T H.245 (2001), *Control protocol for multimedia communication.* + +## 3 Definitions + +For BICC specific terminology, the reader is referred to ITU-T Q.1902.1 [5]. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|-------------------------------------| +| APM | Application Transport Message | +| BCF-N | Bearer Control Nodal Function | +| BICC | Bearer Independent Call Control | +| BIWF | Bearer InterWorking Function | +| CSF-N | Call Service Nodal Function | +| DTMF | Dual Tone Multi Frequency | +| ISDN | Integrated Services Digital Network | +| ISN | Interface Serving Node | +| ISUP | ISDN User Part | +| SCN | Switched Circuit Network | + +# 5 General considerations + +This clause describes the interworking principle between H.225.0 and BICC based on the interworking between H.225.0 and ISUP concatenated with the interworking between ISUP and BICC. This refers to the necessary mapping of signalling information to achieve connectivity and functionality between an H.323 network and a BICC network. Figure 2 provides the functional grouping of the interworking functions involved following the half call model description technique for BICC. + +![Functional description of the interworking configuration diagram](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram illustrates the functional grouping of interworking functions for BICC, following the half call model. It is divided into two main sections by a vertical grey line, each labeled 'Half call' at the top. The left section, labeled 'CSF-N', contains three functional blocks: 'H.225.0', 'Annex C/H.246', and 'Q.1912.1'. 'H.225.0' is connected to 'Annex C/H.246' by a double-headed arrow. 'Annex C/H.246' is connected to 'Q.1912.1' by a double-headed arrow. 'Q.1912.1' is connected to the right section by a double-headed arrow. The right section contains a 'BICC' block, which is connected to the 'Q.1912.1' block by a double-headed arrow. External connections are shown as single-headed arrows pointing into the 'CSF-N' and 'BICC' blocks from the left and right respectively. The diagram is labeled 'T11111940-01' at the bottom right. + +Functional description of the interworking configuration diagram + +Figure 2/Q.1912.3 – Functional description of the interworking configuration + +## **6 Interworking considerations** + +## **6.1 General** + +The interworking between H.225.0 and BICC shall act according to the interworking between H.225.0 and ISUP in Annex C/H.246 [3], and the additional interworking statements in the Implementors Guide for H.323, H.225.0, H.245, H.246, H.283, H.235, H.450-series and H.341 Recommendations in ITU-T Implementors Guide [8], concatenated with the interworking between ISUP and BICC in ITU-T Q.1912.1 [6]. + +## **6.2 Prevention of speech clipping** + +For an incoming H.323 call for which the incoming bearer is not established yet in the H.323 network, the Continuity Indicator in the Nature of Connection Indicators parameter in the IAM in BICC shall be set to indicate "COT to be expected" if the ISN is aware that the call establishment procedures in ITU-T H.245 [9] can take place in the H.323 network without waiting until an ACM message is received in BICC (Note). + +The Continuity message, with the Continuity Indicators parameter set to "Continuity" shall be sent in BICC upon successful completion of the incoming H.323 bearer set-up procedures. + +NOTE – In some H.323 implementations, the H.245 call establishment procedures cannot be initiated before an ACM is received from the BICC network (because the H.245 procedures are not handled until a CONNECT is received or because a CALL PROCEEDING message is not generated before an ACM is received). In such cases, speech clipping cannot be prevented. H.323 networks using such implementations should not be interconnected to BICC networks. The H.245 call establishment procedures shall be initiated as soon as possible on the H.323 side. + +If the Fast Connect procedure is used on the H.323 side, the ISN shall first check that the bearer establishment can be successfully completed according to the proposals received in the fastStart element of the SETUP message received from the H.323 side, before sending the IAM in BICC. + +## **6.3 Codec negotiation and out-of-band transport of DTMF and tone information** + +Interworking procedures related to codec negotiation (including mid-call codec modification and mid-call codec negotiation procedures) and out-of-band transport of DTMF and tone information have also to be considered in case of interworking between an H.323 network and a BICC network. These procedures require the definition of interactions between the BICC protocol and some parts of the H.245 protocol. The accurate definition of these procedures is for further study. Appendix I provides guidelines for the implementation of the end-to-end codec negotiation procedures through a BICC and H.323 network. + +## **6.4 Interworking of ISDN supplementary services** + +Please note that the interworking of ISDN supplementary services (ITU-T H.450.x-series [7]) is for further study. + +# Guidelines BICC/H.323 interworking for end-to-end codec negotiation + +## I.1 Introduction + +The H.245 capability exchange procedures are more complex than the BICC codec negotiation procedures since H.323 nodes have the possibility to separately indicate receive and transmit capabilities, as well as various combination of modes in which the node can operate simultaneously. A different codec can be selected for each unidirectional media channel in H.323. + +As the same codec is used for transmission and reception in a BICC network, only the codecs which are proposed by the H.323 network for reception and transmission will be included in the initial BICC Supported Codecs list used to perform the BICC codec negotiation. This principle is generally applied in the procedures defined below although it is not explicitly mentioned. + +## I.2 H.323 to BICC interworking + +![Diagram showing the network architecture for H.323 to BICC interworking. It consists of three nodes: Node A, ISN B, and Node C. Node A is connected to the H.323 network, which is connected to the BICC network, which is connected to Node C. ISN B is the interface between the H.323 and BICC networks.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` + +graph LR + A[Node A] --- H323[H.323 network] + H323 --- ISNB[ISN B] + ISNB --- BICC[BICC network] + BICC --- C[Node C] + +``` + +Diagram showing the network architecture for H.323 to BICC interworking. It consists of three nodes: Node A, ISN B, and Node C. Node A is connected to the H.323 network, which is connected to the BICC network, which is connected to Node C. ISN B is the interface between the H.323 and BICC networks. + +### I.2.1 If the H.245 procedures are used (with a separate H.245 control channel or using the H.245 encapsulation method) + +- 1) If the capabilities supported by the preceding H.323 node (node A) are received by the ISN (in an H.245 TerminalCapabilitySet message) before the IAM is sent on the outgoing side, the Supported Codec List sent in the IAM is derived from the capability structures contained in the received TerminalCapabilitySet message by deleting the codecs that cannot be used for the call (not offered by the ISN) and adding (with a lower priority) the codecs that can be used for the call (proposed by the ISN) but were not indicated in the received capabilities from the preceding H.323 node (node A). + +The ISN shall wait until an APM with the selected codec is received before indicating its capabilities to the preceding H.323 node (node A). + +- If the Selected Codec received in the APM was contained in the received TerminalCapabilitySet message from the preceding H.323 node (node A), the H.245 TerminalCapabilitySet message sent by the ISN shall only contain the selected codec received in the BICC APM. The end-to-end codec negotiation procedures are successfully completed. The codec selected by the ISN on the H.323 side (sent in the OpenLogicalChannel message) is the codec resulting from the BICC negotiation procedure. +- If the Selected Codec received in the APM does not belong to the capabilities indicating by the preceding H.323 node (node A), a transcoder shall be used. + +- 2) If the capabilities supported by the preceding H.323 node (node A) are not received by the ISN (in an H.245 TerminalCapabilitySet message) before the IAM is sent on the outgoing side, the Supported Codec List is constructed in the ISN as described in ITU-T Q.1902.4 (SN initiating codec negotiation). The ISN waits until the codec negotiation procedure is completed on the BICC side before indicating its capabilities to the preceding node (node A). + +When the APM with the selected codec is received by the ISN: + +- The ISN sends a TerminalCapabilitySet message containing the codecs that can be used for the call (codecs supported by the ISN), allocating the highest priority to the BICC selected codec and the other codecs of the Available codec List. +- If the codec selected by the preceding H.323 node (node A) (received in the H.245 OpenLogicalChannel message) is the BICC Selected codec, end-to-end negotiation procedures are successfully completed. The codec selected by the ISN on the H.323 side (sent in the OpenLogicalChannel message) is the same as the codec selected by the preceding H.323 node. +- If the codec selected by the preceding H.323 node (node A) (received in the H.245 OpenLogicalChannel message) is not the BICC Selected codec but belongs to the BICC Available codec List, the BICC Modification procedure shall be applied on the BICC side: the newly selected codec is the codec selected by node A and the new Available codec List is the old one from which the codecs not supported by node A are deleted. The codec selected by the ISN on the H.323 side (sent in the OpenLogicalChannel message) is the same as the codec selected by the preceding H.323 node. +- If the codec selected by the preceding H.323 node (node A) does not belong to the BICC Available codec List, a transcoder shall be used. + +### I.2.2 If Fast Connect procedure is used + +The Supported Codec List sent in the IAM is derived from the OpenLogicalChannel proposals received in the fastStart element of the Setup message by deleting the codecs which are not supported for the call (the codecs are listed in the same priority order as received in the fastStart element) and adding (with a lower priority) the codecs that can be used for the call but were not proposed in the received fastStart element. + +The backward APM with the Selected codec is awaited before the fastStart element is sent back by the ISN. + +- If the Selected Codec received in the APM was proposed in the received fastStart element, the ISN sends a fastStart element selecting amongst the OpenLogicalChannel proposals containing the Selected codec received in the APM. The end-to-end codec negotiation is successfully completed. +- If the Selected Codec received in the APM was not proposed in the received fastStart element, a transcoder shall be used. + +## I.3 BICC to H.323 interworking + +![Diagram illustrating BICC to H.323 interworking. It shows three nodes: Node A, ISN B, and Node C. Node A is connected to the BICC network, which is connected to the H.323 network, which is connected to Node C. ISN B is located at the boundary between the BICC and H.323 networks.](853f59c89931a666c07903b31d098277_img.jpg) + +``` +graph LR; NodeA[Node A] --- BICC[BICC network]; BICC --- ISNB[ISN B]; ISNB --- H323[H.323 network]; H323 --- NodeC[Node C]; +``` + +Diagram illustrating BICC to H.323 interworking. It shows three nodes: Node A, ISN B, and Node C. Node A is connected to the BICC network, which is connected to the H.323 network, which is connected to Node C. ISN B is located at the boundary between the BICC and H.323 networks. + +### **I.3.1 If H.245 procedures are used (with a separate H.245 control channel or using the H.245 encapsulation method)** + +It may not be possible to wait until the capabilities of node C are received before selecting the codec on the BICC side: H.245 procedures may only begin in the H.323 network when a H.225.0 CONNECT message is sent (when an answer is received from the called party) whereas the BICC codec negotiation procedures must be completed before the ACM is sent. It is therefore preferable to complete the BICC codec negotiation procedures independently of the H.323 procedures on the outgoing side. + +- The ISN waits until a TerminalCapabilitySet message is received from the succeeding H.323 node. +- If the BICC Selected codec is supported by the succeeding H.323 node (node C), end-to-end negotiation procedures are successfully completed. The ISN sends a TerminalCapabilitySet containing the BICC selected codec only. The OpenLogicalChannel message which will be sent by the ISN shall contain this same BICC selected codec. The end-to-end codec negotiation procedures are successfully completed. +- If the BICC selected codec does not belong to the list of codecs supported by the succeeding H.323 node, the ISN selects the codec with the highest priority in the BICC Available Codecs List which is also supported by the succeeding H.323 node. The ISN sends a TerminalCapabilitySet containing the BICC selected codec only. The OpenLogicalChannel message which will be sent by the ISN shall contain this same BICC selected codec. The BICC modification procedure is applied on the BICC side: the newly selected codec is the codec selected by the ISN and the new Available codec List is the old one from which the codecs not supported by the succeeding H.323 (node C) are deleted. +- If no codec of the BICC Available Codecs List is supported by the succeeding H.323 node, a transcoder shall be used. + +#### **I.3.2 If Fast Connect procedure is used** + +The OpenLogicalChannel proposals sent in the fastStart element of the SETUP message contains the codecs that can be used for the call (supported by the ISN). The BICC Selected codec and the codecs of the BICC Available codecs List resulting from the BICC negotiation procedure are proposed with the highest priority. + +- If the codec selected by the succeeding H.323 node (node C) (received in the selected OpenLogicalChannel indicated in the fastStart element) is the BICC Selected codec, end-to-end negotiation procedures are successfully completed. +- If the codec selected by the succeeding H.323 node (node C) (received in the OpenLogicalChannel contained in the fastStart element) is not the BICC Selected codec but belongs to the BICC Available codec List, the BICC Modification procedure shall be applied on the BICC side: the newly selected codec is the codec selected by the succeeding H.323 node (node C) and the new Available codec List is the old one from which the codecs which were proposed with a higher priority than the H.323 Selected codec (codecs not supported by the succeeding H.323 node (node C)) are deleted. +- If the codec selected by the succeeding H.323 node (node C) does not belong to the BICC Available Codecs List, a transcoder shall be used. + + + + + +# 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.1912.4-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/Q/T-REC-Q.1912.4-200107-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.1912.4-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd046671fdbf5c87af7a400edd20fd304decea35 --- /dev/null +++ b/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bda700e9513c71d84c29137280b3d3537bd7c73311efb7a6faba9a6d06880697 +size 81942 diff --git a/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05a1fa7c29a3f021013d8b1c9278bfe75365f657 --- /dev/null +++ b/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a39cf807c9ea65b59b1fa00fa3ea2c4288c48eb69de416830bad7e66804dca91 +size 33914 diff --git a/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a3f56e9821bd4fa557a99a68343602165fdfb0b0 --- /dev/null +++ b/marked/Q/T-REC-Q.1912.4-200107-I_PDF-E/raw.md @@ -0,0 +1,225 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1912.4** + +(07/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**Interworking between Digital Subscriber +Signalling System No. 2 and the Bearer +Independent Call Control protocol** + +ITU-T Recommendation Q.1912.4 + +(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 | +| 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.* + +## **Interworking between Digital Subscriber Signalling System No. 2 and the Bearer Independent Call Control protocol** + +## **Summary** + +This Recommendation defines the signalling interworking for 64 kbit/s ISDN Circuit Mode Services between Digital Subscriber Signalling System No. 2 (DSS2) and Bearer Independent Call Control (BICC). + +### **Source** + +ITU-T Recommendation Q.1912.4 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 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..... | 2 | +| 3 | Definitions ..... | 3 | +| 4 | Abbreviations..... | 3 | +| 5 | General considerations..... | 3 | + + + +## **Interworking between Digital Subscriber Signalling System No. 2 and the Bearer Independent Call Control protocol** + +## **1 Scope** + +This Recommendation defines the signalling interworking between the Bearer Independent Call Control (BICC) protocol and Digital Subscriber Signalling System No. 2 (DSS2). In this Recommendation, interworking is defined through the relationships in existing Recommendations for interworking between DSS2 and B-ISUP, in addition to interworking between B-ISUP and ISUP. + +BICC is the protocol defined in ITU-T Q.1902.1 to Q.1902.4 [6]. DSS2 is defined by ITU-T Q.2931 [15], Q.2932.1 [17], Q.2951 [18], Q.2951.9 [19], Q.2957 [20], Q.2941.2 [21]. B-ISUP is the protocol defined in ITU-T Q.2761 to Q.2764 [14]. ISUP is the protocol defined in ITU-T Q.761 to Q.764 [4]. + +This Recommendation builds on: + +- The signalling interworking between existing DSS2 and the B-ISDN User Part (B-ISUP) protocol as defined in various ITU-T Recommendations. +- The signalling interworking between existing B-ISUP signalling systems and the ISDN User Part (ISUP) protocol of Signalling System No. 7 as defined in various ITU-T Recommendations. +- The signalling interworking between the Bearer Independent Call Control (BICC) protocol and the ISDN User Part (ISUP) protocol of Signalling System No. 7 as defined in ITU-T Q.1912.1 [7]. + +The scope of this Recommendation as shown in Figure 1. + +![Diagram illustrating the scope of ITU-T Recommendation Q.1912.4 for BICC/DSS2 interworking. It shows a central ISN (ISDN) block containing four call/bearer control units: DSS2 call/bearer control, B-ISUP call/bearer control, N-ISUP call/bearer control, and CSF-N (containing BICC). Arrows show interworking between these units. External connections include DSS2 on the left, BICC on the right, and an ATM network/BICC network using separate call and bearer signalling at the bottom via a BIWF/BCF-N unit. Three dashed boxes indicate the scope of different ITU-T recommendations: ITU-T Q.2650 and Q.2660 (covering DSS2 and B-ISUP), this Recommendation (covering B-ISUP and N-ISUP), and ITU-T Q.1912.1 (covering N-ISUP and BICC).](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +Diagram illustrating the scope of ITU-T Recommendation Q.1912.4 for BICC/DSS2 interworking. It shows a central ISN (ISDN) block containing four call/bearer control units: DSS2 call/bearer control, B-ISUP call/bearer control, N-ISUP call/bearer control, and CSF-N (containing BICC). Arrows show interworking between these units. External connections include DSS2 on the left, BICC on the right, and an ATM network/BICC network using separate call and bearer signalling at the bottom via a BIWF/BCF-N unit. Three dashed boxes indicate the scope of different ITU-T recommendations: ITU-T Q.2650 and Q.2660 (covering DSS2 and B-ISUP), this Recommendation (covering B-ISUP and N-ISUP), and ITU-T Q.1912.1 (covering N-ISUP and BICC). + +**Figure 1/Q.1912.4 – Scope of this Recommendation for BICC/DSS2 interworking** + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Q.617 (1993), *Logic procedures for incoming Signalling System No. 7 (ISUP)*. +- [2] ITU-T Q.627 (1993), *Logic procedures for outgoing Signalling System No. 7 (ISUP)*. +- [3] ITU-T Q.699 (1997), *ISDN access and non-ISDN access over ISDN user part of Signalling System No. 7*. +- [4] ITU-T Q.761 to Q.764 (1999), *Specifications of Signalling System No. 7 ISDN user part (ISUP)*. +- [5] ITU-T Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*. +- [6] ITU-T Q.1902.1 to Q.1902.4 (2001), *Specifications of the Bearer Independent Call Control protocol (BICC)*. +- [7] ITU-T Q.1912.1 (2001), *Interworking between Signalling System No. 7 ISDN user part (ISUP) and the Bearer Independent Call Control protocol (BICC)*. +- [8] ITU-T Q.118 (1997), *Abnormal conditions – Special release arrangements*. +- [9] ITU-T Q.543 (1993), *Digital exchange performance design objectives*. +- [10] ITU-T Q.2650 (1999), *Interworking between Signalling System No. 7 broadband ISDN user part (B-ISUP) and Digital Subscriber Signalling System No. 2 (DSS2)*. +- [11] ITU-T Q.2660 (1999), *Interworking between Signalling System No. 7 broadband ISDN user part (B-ISUP) and narrow-band ISDN user part (N-ISUP)*. +- [12] ITU-T Q.2730 (1999), *Signalling System No. 7 B-ISDN user part (B-ISUP) – Supplementary services*. +- [13] ITU-T Q.2735.1 (1997), *Stage 3 description for community of interest supplementary services for B-ISDN using SS No. 7: Closed User Group (CUG)*. +- [14] ITU-T Q.2761 to Q.2764 (1999), *Broadband Integrated Services Digital Network (B-ISDN) – Signalling System No. 7 B-ISDN user part (B-ISUP)*. +- [15] ITU-T Q.2931 (1995), *Digital Subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control*. +- [16] ITU-T Q.2931, Amendment 2 (1999), *Digital Subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control*. +- [17] ITU-T Q.2932.1 (1996), *Digital Subscriber Signalling System No. 2 – Generic functional protocol: Core functions*. +- [18] ITU-T Q.2951.1-8 (1995), *Stage 3 description for number identification supplementary services using B-ISDN Digital Subscriber Signalling System No. 2 (DSS2) – Basic Call*. +- [19] ITU-T Q.2951.9 (1999), *Stage 3 description for number identification supplementary services using B-ISDN Digital Subscriber Signalling System No.2 (DSS2) – Basic Call: Support of ATM end system addressing format by Number identification supplementary services*. + +- [20] ITU-T Q.2957 (1995), *Stage 3 Description for Additional Information Transfer Supplementary Services Using B-ISDN Digital Subscriber Signalling System No. 2 (DSS2) – Basic Call.* +- [21] ITU-T Q.2941.2 (1999), *Digital Subscriber Signalling System No. 2 – Generic identifier transport extensions.* + +## 3 Definitions + +For the BICC specific terminology, the reader is referred to ITU-T Q.1902.1 [6]. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|--------|--------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| BICC | Bearer Independent Call Control | +| B-ISDN | Broadband ISDN | +| B-ISUP | Broadband ISUP | +| CSF-N | Call Service Nodal Function | +| DSS1 | Digital Subscriber Signalling System No. 1 | +| DSS2 | Digital Subscriber Signalling System No. 2 | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | + +## 5 General considerations + +This Recommendation specifies the interworking principle between BICC and Digital Subscriber Signalling System No. 2. The interworking is defined by the concatenation of information provided by several ITU-T Recommendations that are part of a set of interlocking B-ISDN service and signalling Recommendations that comprise broadband signalling capabilities. Figure 2 provides the functional grouping of the entities involved. + +The B-ISDN access signalling DSS2 is specified in ITU-T Q.2931 [16]. The interworking between DSS2 for 64 kbit/s circuit mode services and BICC shall act according to the interworking between DSS2 and B-ISUP defined in ITU-T Q.2650 [10] and the interworking between B-ISUP and ISUP defined in ITU-T Q.2660 [11]. + +The ISDN circuit mode services are interworked following, in sequence, the procedures in ITU-T Q.2650 and Q.2660. The reader may find it helpful to read ITU-T Q.699 [3] for the detailed description of how indicator values are used when interworking 64 kbit/s ISDN Circuit Mode Services. + +![Functional description of the interworking configuration diagram showing a CSF-N box with internal components (DSS2 Access, Q.2650, Q.2660, Q.1912.1, BICC) and external 'Half call' connections.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the functional description of the interworking configuration. It features a large rectangular box labeled "CSF-N" at the top left. Inside this box, five smaller rectangular boxes are arranged horizontally from left to right: "DSS2 Access", "Q.2650", "Q.2660", "Q.1912.1", and "BICC". These internal components are interconnected by double-headed arrows. The "DSS2 Access" box has a double-headed arrow pointing to the left, outside the CSF-N box. The "BICC" box has a double-headed arrow pointing to the right, outside the CSF-N box. Above the CSF-N box, there are two horizontal double-headed arrows. The first is labeled "Half call" and spans from the left edge of the CSF-N box to a vertical grey line positioned between the "Q.1912.1" and "BICC" boxes. The second is also labeled "Half call" and spans from the vertical grey line to the right edge of the CSF-N box. In the bottom right corner, outside the CSF-N box, the text "T11111980-01" is present. + +Functional description of the interworking configuration diagram showing a CSF-N box with internal components (DSS2 Access, Q.2650, Q.2660, Q.1912.1, BICC) and external 'Half call' connections. + +**Figure 2/Q.1912.4 – Functional description of the interworking configuration** + + + +## 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.1930-200204-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9eaeec39985b82a24461d1e777a94fa8cd51d95 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a53c42db187fd07f0fd979995b519ed90f4ef05485a11faafca913eccfc8485 +size 13545 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/107c8e1abcb7033ad244e30e7a910045_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/107c8e1abcb7033ad244e30e7a910045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a06a7e1331bfb67acb0b1df9bc9ed9ee72627e7 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/107c8e1abcb7033ad244e30e7a910045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cef6f77c5687e2a48d6f6d2f4d1f16fc182816fb808e0236146f9145d73be91 +size 32961 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9046ec32dcd64a0e1c6a4bbbe6b892fe26ccd341 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:283138e1e889249ef27ab26e380d9b14dd0fb6b6b04af75dd4276e86d5c43cb6 +size 12935 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..793f24dd543a8dc0cecd0ff48363c0365920e946 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9161b9aa708a79864d52c3fbfebd052a2a72b40f6c471982d02f8bc4bb9506cb +size 14895 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..193e2b3250150a61f03b8db5d9c446fa579bafe7 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b494d14ec5137e1a2e5702467f2a7ae6f43ef9d61ebb840d4e9c7e8a00c08c3 +size 15707 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eac623a17bfdd3094e40dddfbd52bad7f606e4b5 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faa0a7e0acde9e381904116ca6093b49d3212824e322f2c1b76d8792b0e6b1e0 +size 14348 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b468d13b9b3f842542cfd96266089e5cac37aa5c --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4d74cc7618b5adc457a4be59d886746bfd8340c8948e865e00b6d400543c081 +size 31155 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-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.1930-200204-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5232d655a8ec2847b4329abd0432a6e2db3b034b --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:186d5987c848af2e8167f22320a25b42994abef0efeb986f7a151f87f1401d23 +size 17214 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d1ada3407c01def9c47dc7da6800b98d51d4cc3 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c30eacaf0357584153a748e770a8382e4ab9369be3b0d716c9983dc358b2d59b +size 162478 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f58ad1b7ba8170d3632ad03752de5be993d0d965 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:353aa0b9d25a2c446148a3d683123cda9b797b278904ccab0a2a4bcd2b5ed68a +size 23894 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..198ae3fa05d5e464f97ed03c54d63b4ce7559b18 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b043ca09cdb12d3fbfdb8f862574d68d49021c9c772ea785ffbae0205e0ce7fb +size 53223 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/4c731b7bb6a5851992b8b7440b4e9356_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/4c731b7bb6a5851992b8b7440b4e9356_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba81f0d25a4dde08d3ebe00308663326716a249c --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/4c731b7bb6a5851992b8b7440b4e9356_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c68b81b06e66ab9f819f973df9495b5d32e92eb9f64a23dfe99c99ac3529bfb5 +size 36923 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb816beebf7928e5cbb5a38a73f95ad36b433c34 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fca5ad4b909e19422dfe51b3bebdfdfee3ebabce6c8d5991efbf59a082758286 +size 28582 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f560ac6ad622299e285766f896859b365726cd7 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7776508e26e65f73c459c14794b229b7bb8cf2a4924526459db12296153eb447 +size 124182 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce88e16b73701ee4f5462bdbcda56592c8a92591 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:318e9a20148b7edaaa76a0ac7dd7b6010e8e1aeb9a12fde41f1a768d857fe9bb +size 73529 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bf8a4b95705895576dc0ae5a2cec0e49d11833b --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef63e73979b9d00e6cb5ce44e437849e69efd3be8e65df5bc8f094d5c37eba22 +size 14225 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..548718d1710a7124a059df35316d8962c3a806a2 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:832c277eb549b62a49c51d1220af1d1448ff2fb86b0aa1089fdff667fdbf8b78 +size 124143 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c7ba963e870a08af3df83980396e410fa125f15 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53cf7eb88ad8f7e1055da0fa6def7c991296f6c8ed36f6d252cc9ef10568b80c +size 12796 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd2856a3d597bb11811345c99eaec2f464554bc5 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e49416c514ddb11a5e1d628724c6aee3146dbbbecd5c81aa83fc86c9128a1231 +size 156541 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97ce82fc7907050ef463724d570ecdbb10e710cf --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aa0646686effb4ad0f21906b3b4f6df5bcc2f83594fcd45db07fe5faa05ab1f +size 147847 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2efafe6d949a0003f81f20bbc453426f7861a193 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ea93b256e10752aac28f10c9ebf5fe50308e17ae4fa27739c0d491a6b86b7d9 +size 45909 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9244b9417cdc1c857b557c1770a14f912a651a3e --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f16e3e61aaaec13f940a52068c0203041555ff527e20196c7e7e48d4b1f40ddc +size 6297 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ccdeaf31dbe65613f2f87a7b2b06e391_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ccdeaf31dbe65613f2f87a7b2b06e391_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..616030152782bfa766ddd6a3914a2772f28b25fe --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ccdeaf31dbe65613f2f87a7b2b06e391_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e38af7d3e4f2298ce275eb37c1bb511ee299ba408fae7f2c3c9229830cdc5b6e +size 50442 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a326f3bd6cfe6378a9b1863c70f065db1c94dd1c --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d59137ce1019b2b5b606c2cf79c1d5c54674d0f8ee049b1e7dc5789041bd42a +size 12954 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ddcdc1712375261ba1d89165fdf12aa6_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ddcdc1712375261ba1d89165fdf12aa6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f9722e51010e49614db65af662781525a0ad886 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ddcdc1712375261ba1d89165fdf12aa6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff61835500a254e730a6ed2d3a7dcbc78edb2573b09c73de6f09b8b4cf1c8153 +size 57266 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97ea645a54539f1aa3d382ddcfe98c5598f24258 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df99089c7b116e247d777552bd32d56bfa135ba49f634e46175e0fda190c0287 +size 17841 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ad0c493b5f13c7979087d1d3ad6be6c80d6fe41 --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:388128c0af2b5d1d73c28a6b40331390ae7debe77fdaefed5b734cfd15fd4fff +size 53540 diff --git a/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24f581a4ff2d9cbf25f9966bd62b054863df48de --- /dev/null +++ b/marked/Q/T-REC-Q.1930-200204-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81d0b34699c280087abd13e9c80cf036c7c85330f53c8add1e0d5ad51c42403d +size 53818 diff --git a/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b125fdac1f410a672f41014c838f6d1e28b207bd --- /dev/null +++ b/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/raw.md @@ -0,0 +1,8100 @@ + + +![ITU logo: A globe with a red lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a red lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1980.1** + +(12/2004) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of signalling related to Bearer Independent +Call Control (BICC) + +--- + +**The Narrowband Signalling Syntax (NSS) – +Syntax definition** + +ITU-T Recommendation Q.1980.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 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation Q.1980.1** + +# **The Narrowband Signalling Syntax (NSS) – Syntax definition** + +## **Summary** + +This Recommendation describes a Narrowband Signalling Syntax (NSS) to provide a normalized set of telephony parameters. NSS enables mapping from multiple telephony protocols in use today into a common parameter set. + +## **Source** + +ITU-T Recommendation Q.1980.1 was approved on 10 December 2004 by ITU-T Study Group 11 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | | Page | +|------|-------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Message and parameter syntax overview ..... | 3 | +| 5.1 | Character set ..... | 3 | +| 5.2 | Structure ..... | 4 | +| 5.3 | NSS compact transmission mode ..... | 5 | +| 6 | Message definitions ..... | 5 | +| 6.1 | Unsupported messages ..... | 5 | +| 6.2 | NSS message identifier codes ..... | 5 | +| 7 | Parameter definitions ..... | 7 | +| 7.1 | Unsupported parameter disposition..... | 7 | +| 7.2 | NSS parameter codes..... | 7 | +| 7.3 | Detailed parameter descriptions ..... | 14 | +| 7.4 | BAT ASE parameters ..... | 78 | +| 8 | MIME encoding of NSS body ..... | 90 | +| 8.1 | MIME-Version header field ..... | 90 | +| 8.2 | Content-Type header field ..... | 90 | +| 8.3 | Content-Transfer-Encoding header field ..... | 90 | +| 8.4 | Content-Disposition header field..... | 90 | +| 8.5 | NSS MIME media type specification..... | 91 | +| 9 | Encapsulation in SIP ..... | 91 | +| 10 | Encapsulation in H.323..... | 91 | +| 11 | Security considerations..... | 91 | +| 12 | NSS-specific syntactical elements and procedures ..... | 91 | +| 12.1 | NSS-specific messages ..... | 91 | +| 12.2 | NSS-specific parameters ..... | 91 | +| 12.3 | NSS compatibility procedures ..... | 92 | +| | Annex A – Narrowband Signalling Syntax ABNF grammar ..... | 94 | +| | Appendix I – Narrowband Signalling Syntax (NSS) encoding examples ..... | 113 | +| I.1 | Message examples ..... | 113 | +| I.2 | Compatibility ordering example..... | 115 | +| I.3 | GCI and TID structure example ..... | 115 | +| | Appendix II – NSS verbose encoding..... | 117 | + + + +# The Narrowband Signalling Syntax (NSS) – Syntax definition + +# 1 Scope + +This Recommendation specifies a flexible encoding syntax of narrowband signalling information to be transferred in protocols that cannot inherently transfer such information. + +![Diagram illustrating the scope of the Recommendation. It shows two systems connected by a 'Signalling interface'. Each system consists of a 'Native protocol service user' connected to a 'Native protocol service provider'. Between the user and provider in each system is a 'Narrowband signalling syntax user' connected to a 'Narrowband signalling syntax provider'. A dashed box labeled 'Scope of this Recommendation' encloses the 'Narrowband signalling syntax' components (the users and providers) and the 'Narrowband signalling syntax' interface between them. The 'Native protocol' components (the users, providers, and the interface between them) are outside this scope.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram illustrates the scope of the Recommendation. It shows two systems connected by a 'Signalling interface'. Each system consists of a 'Native protocol service user' connected to a 'Native protocol service provider'. Between the user and provider in each system is a 'Narrowband signalling syntax user' connected to a 'Narrowband signalling syntax provider'. A dashed box labeled 'Scope of this Recommendation' encloses the 'Narrowband signalling syntax' components (the users and providers) and the 'Narrowband signalling syntax' interface between them. The 'Native protocol' components (the users, providers, and the interface between them) are outside this scope. + +Diagram illustrating the scope of the Recommendation. It shows two systems connected by a 'Signalling interface'. Each system consists of a 'Native protocol service user' connected to a 'Native protocol service provider'. Between the user and provider in each system is a 'Narrowband signalling syntax user' connected to a 'Narrowband signalling syntax provider'. A dashed box labeled 'Scope of this Recommendation' encloses the 'Narrowband signalling syntax' components (the users and providers) and the 'Narrowband signalling syntax' interface between them. The 'Native protocol' components (the users, providers, and the interface between them) are outside this scope. + +Figure 1/Q.1980.1 – Scope of this Recommendation + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation H.225.0 (2003), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*. +- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communication systems*. +- ITU-T Recommendation Q.761 (1999), *Signalling System No. 7 – ISDN User Part functional description*. +- ITU-T Recommendation Q.762 (1999), *Signalling System No. 7 – ISDN User Part general functions of messages and signals*. +- ITU-T Recommendation Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes*; plus Amendment 1 (2001), *Coding of the application transport parameter*; Corrigendum 1 (2001); plus Amendment 2 (2002), *Support for the International Emergency Preference Scheme*. +- ITU-T Recommendation Q.765.5 (2004), *Signalling System No. 7 – Application Transport Mechanism: Bearer Independent Call Control (BICC)*. +- ITU-T Recommendation Q.767 (1991), *Application of the ISDN User Part of CCITT Signalling System No. 7 for international ISDN interconnections*; plus Amendment 1 (2002), *Support for the International Emergency Preference Scheme*. + +- ITU-T Recommendation Q.850 (1998), *Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part*; plus Addendum 1 (2000), plus Amendment 1 (2001). +- ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*; plus Amendment 1 (2002), *Extensions for the support of digital multiplexing equipment*; plus Erratum 1 (2003). +- ITU-T Recommendation Q.1902.3 (2001), *Bearer Independent Call Control protocol (Capability Set 2) and Signalling System No. 7 ISDN user part: Formats and codes*; plus Amendment 1 (2002), *Support for the International Emergency Preference Scheme*. +- ETSI TS 126 103 v 5.5.0 (2004-09), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Speech codec list for GSM and UMTS (3GPP TS 26.103 version 5.5.0 Release 5)*. +- IETF RFC 2045 (1996), *Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies*. +- IETF RFC 2046 (1996), *Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types*. +- IETF RFC 2183 (1997), *Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field*. +- IETF RFC 2234 (1997), *Augmented BNF for Syntax Specifications: ABNF*. +- IETF RFC 2327 (1998), *SDP: Session Description Protocol*. +- IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 compatibility parameter:** A compatibility parameter is a NSS parameter used to carry unrecognized syntax objects and requiring the PRN parameter for interpretation. The set of compatibility parameters includes FDC, UFC, PCI, and MCI. + +NOTE – The ATP parameter also requires the PRN parameter for interpretation. + +**3.2 mappable parameter:** An ISUP/BICC parameter which satisfies the following conditions with respect to the protocol transporting the NSS body: + +- every field in the ISUP/BICC parameter is accounted for by a field or combination of fields in the encapsulating protocol; +- every potential value of the ISUP/BICC field is accounted for by a value of the corresponding field(s) in the encapsulating protocol; and +- the original value of every ISUP/BICC field can be recovered when the encapsulating protocol alone (disregarding any encapsulated NSS or ISUP/BICC) is mapped back to the same variant of ISUP/BICC as was mapped into the encapsulating protocol at the NSS-originating node. + +**3.3 NSS message:** A NSS message is a body composed of a contiguous set of text lines as defined in clause 5. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------------------------------| +| ABNF | Augmented Backus-Naur Form (see RFC 2234) | +| ASCII | American Standard Code for Information Interchange | +| BICC | Bearer Independent Call Control | +| COT | Continuity Test (used for TDM circuits) | +| IA5 | International Alphabet No. 5 (same as 7-bit ASCII) | +| IE | Information Element | +| IEPS | International Emergency Preference Scheme | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| MIME | Multipurpose Internet Mail Extensions | +| NSS | Narrowband Signalling Syntax | +| PBX | Private Branch eXchange | +| POTS | Plain Old Telephone Service | +| PSTN | Public Switched Telephone Network | +| RAS | Registration, Admission and Status (see ITU-T Rec. H.225.0) | +| RTP | Real-time Transport Protocol | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| SS7 | Signalling System No. 7 | +| TDM | Time Division Multiplexing | + +# 5 Message and parameter syntax overview + +The general rules for NSS message, parameter, and field formats are specified in this clause. + +## 5.1 Character set + +NSS messages are composed of printable IA5 (i.e., 7-bit US ASCII) characters plus carriage return (CR = x0D) and line feed (LF = x0A). Alphabetic characters are case sensitive. The case rules are described in this clause and in 5.2. + +Values potentially requiring the representation of information lying outside this character set shall be presented as a sequence of one or more binary octets, expressed as a series of one or more pairs of characters ("0"-"9", "A"-"F") without a preceding "x" representing the binary octets as hexadecimal values. The characters "A" through "F" must be upper case. The ordering of the binary octets in a given value is defined by the source protocol. The resulting sequence of character pairs will be placed into an NSS value field with no leading "x" character in that same order. The first character of each pair represents the most significant four bits of the binary octet being expressed. If an octet of the source protocol contains bits which do not belong to the field or sub-field value being encoded, these bits shall be set to zero before applying the hexadecimal encoding. + +NOTE – The ordering of bits within individual octets as represented by the hexadecimal encoding is the reverse of their order of transmission in the source protocol. See 1.9/Q.763. + +Clauses 7.3 and 7.4 indicate for each field or subfield value whether the direct or ASCII-hexadecimal representation is used. + +The CR and LF characters are reserved for use together as line termination. See 5.2.1. + +The "," and "=" characters are reserved for use as separators. Parentheses "(" and ")" and braces "{" and "}" are reserved for use as group delimiters. The application of these reserved characters is described in 5.2. + +The "\" character is reserved for use as an escape mechanism and must be placed immediately before any "," or "=" or "(" or ")" or "{" or "}" or CR or LF or "\" character found in a field value during parameter construction. During parsing, each first encounter of an "\" character is not used as part of the field value and the character following the "\" is treated as part of the field value. + +## 5.2 Structure + +### 5.2.1 NSS message + +A NSS message is composed of a sequence of lines, each beginning with a sequence of three upper-case letters followed by a comma and ending with a carriage return – line feed sequence (x0Dx0A). + +Except for the Message Identifier line, the initial sequence of letters on a line identifies a parameter. On the Message Identifier line, the initial sequence of letters identifies a message. + +The set of message identifiers defined in this Recommendation is listed in 6.2, "NSS message identifier codes". + +The set of parameter identifiers defined in this Recommendation is listed in 7.2, "NSS parameter codes". + +A NSS message begins with three mandatory NSS-specific parameters: Version (VER), Protocol Name/Version (PRN), and Message Identifier in that order. These are followed by zero or more other parameters. + +This Recommendation does not specify which additional parameters must be present in a NSS message, nor does it specify the order in which those parameter lines must appear. It is recommended that this order be the same as that of the corresponding parameters in the source protocol message. + +NOTE – It is expected that NSS messages will not include parameter lines derived from source protocol parameters that have been successfully mapped to the encapsulating protocol. Rules for interworking BICC and ISUP to the combination of SIP (RFC 3261) or ITU-T Rec. H.323 and NSS are not in the scope of this Recommendation. + +Multiple parameters of the same type indicate concurrent instances of a parameter within a single NSS message. + +### 5.2.2 NSS parameter line + +Each parameter identifier is followed by a sequence of fields. The set of fields that is required to be present for each parameter defined in this Recommendation and the order in which these fields must appear is specified in the applicable sub-clauses of Recommendation 7.3, "Detailed parameter descriptions", and 7.4, "BAT ASE parameters". + +Two successive fields are separated by a comma ",". + +### 5.2.3 NSS fields + +The type and the actual set of values permitted for each field is specified in the applicable sub-clause of Recommendation 7.3, "Detailed parameter descriptions" and of 7.4, "BAT ASE parameters". + +The value may be omitted if the field value is unknown, leaving only the separating comma if there is a following field. This is permitted only if the range of permissible values for the field includes "unknown". The decoding end must correspondingly interpret an empty field value as having the "unknown" value. + +Field values defined as literals in 7.3 must be transmitted exactly as defined, e.g., a field value of "0001" must not be transmitted as "1". + +For multiple groups of fields and values within some parameters, multiple iterations of the same element type or value may be enclosed by parentheses "(" and ")". Braces "{" and "}" denote a tuple of dissimilar elements. Commas must separate elements within each type of group. From the perspective of higher-level constructs, those groups are viewed as a single field value. Detailed descriptions are provided in those parameters where this applies, e.g., in 7.3.18, "Calling Geodetic Location (CGL)" and in 7.3.23, "Cause indicators (CAI)". + +## 5.3 NSS compact transmission mode + +The normal encoding of NSS requires that field values be presented without identifying tags. This is possible because all field values in a parameter have a fixed order. + +NOTE – For human display purposes, a "field-name=" construct may be inserted before each field value. Alphabetic characters within field names are always lower case. The field names for fields specified in this Recommendation are shown in 7.3, "Detailed parameter descriptions", to aid in readability, but are not transmitted. The corresponding ABNF for converting from the transmission mode to a display is shown in Appendix II. + +For an example of a NSS message in compact transmission mode, see Appendix I. + +# 6 Message definitions + +This clause describes the Message Identifiers supported by the NSS. Clause 7 describes all messages, parameters, and fields specifically introduced by the NSS protocol with both structure and intended use. Although this Recommendation provides detailed breakdowns of NSS parameter structure and field values, these must not be considered to be descriptions of the structure and use of existing ISUP messages, parameters, and fields. + +NOTE – It is intended that the procedures associated with parameters in NSS will be those applicable to the source protocol parameter from which they were mapped. This topic is not in the scope of this Recommendation. + +## 6.1 Unsupported messages + +There are no NSS equivalents for ISUP/BICC messages that do not have end-to-end significance, especially the TDM circuit management messages. Unrecognized NSS Message Handling (see 12.3) procedures can be used in the event that the such messages are required to be transmitted. + +## 6.2 NSS message identifier codes + +The following is the list of message names and their associated NSS Message Identifier codes. Parameter codes and Message Identifier codes share the same code space. + +| Message Name | Message Identifier Code | | +|-----------------------------|--------------------------------|--------------| +| Address Complete | ACM | | +| Answer | ANM | | +| Application Transport | APM | | +| Call Progress | CPG | | +| Charge Information | CRG | | +| Confusion | CFN | | +| Connect | CON | | +| Continuity | COT | | +| Facility | FAC | | +| Facility Accepted | FAA | | +| Facility Reject | FRJ | | +| Facility Request | FAR | | +| Forward Transfer | FOT | | +| Generic Parameter List | GPL | NSS-specific | +| Identification Request | IDR | | +| Identification Response | IRS | | +| Information | INF | | +| Information Request | INR | | +| Initial Address | IAM | | +| Loop Prevention | LOP | | +| Network Resource Management | NRM | | +| Overload | OLM | | +| Pass Along | PAM | | +| Pre-Release Information | PRI | | +| Release | REL | | +| Release Complete | RLC | | +| Resume | RES | | +| Segmentation | SGM | | +| Subsequent Address | SAM | | +| Subsequent Directory Number | SDN | | +| Suspend | SUS | | +| Unrecognized Message | UNR | NSS-specific | +| User-to-user Information | USR | | + +See 12.1 for explanations of NSS-specific messages. + +# 7 Parameter definitions + +This clause describes the syntax, parameters, fields, and field values. + +## 7.1 Unsupported parameter disposition + +The parameter "End Of Optional Parameters" is derived from ISUP specifications. It is not supported in NSS because that role is superseded by the encoding rules defined in 5.2.1. + +## 7.2 NSS parameter codes + +The following list of parameter names is derived as a superset of ISUP and BICC parameters from the specifications identified in clause 2. The NSS-specific parameters are needed to address transparency issues. + +Parameter codes and Message Identifier codes share the same code space. + +| Parameter name | NSS code | | +|-------------------------------------------|-----------------|---------| +| Access Delivery Information | ADI | | +| Access Transport | ATP | | +| Action Indicator | ACT | BAT ASE | +| Application Transport | APP | | +| Automatic Congestion Level | ACL | | +| Backward Call Indicators | BCI | | +| Backward GVNS | BVN | | +| Backward Network Connection Identifier | BID | BAT ASE | +| BAT Compatibility Report | BAT | BAT ASE | +| Bearer Control Information | BCD | BAT ASE | +| Bearer Control Tunnelling | BCT | BAT ASE | +| Bearer Control Unit Identifier | BDU | BAT ASE | +| Bearer Network Connection Characteristics | BNC | BAT ASE | +| Bearer Redirection Capability | BRC | BAT ASE | +| Bearer Redirection Indicators | BRI | BAT ASE | +| Call Completion Service Set-up | CCS | | +| Call Diversion Information | CDI | | +| Call Diversion Treatment Indicators | CDT | | +| Call History Information | CHI | | +| Call Offering Treatment Indicators | OCT | | +| Call Reference | CRF | | +| Call Transfer Number | CTN | | +| Call Transfer Reference | CTR | | +| Called Directory Number | CDN | | +| Called IN Number | CIN | | +| Called Party Number | CPN | | + +| | | | +|----------------------------------------------------|-----|--------------| +| Calling Geodetic Location | CGL | | +| Calling Party Geodetic Velocity Information | CGV | | +| Calling Party Number | CGN | | +| Calling Party's Category | CPC | | +| Carrier Selection Information | CSI | | +| Cause Indicators | CAI | | +| CCNR Possible Indicator | CCN | | +| Charged Party Identification | CPI | | +| Circuit Identification (Call Instance) Code | CIC | | +| Closed User Group Interlock Code | GIC | | +| Codec | COD | BAT ASE | +| Codec List | CDL | BAT ASE | +| Coding Decoding Processing | CDP | | +| Collect Call Request | COL | | +| Conference Treatment Indicator | CNF | | +| Connected Number | CNN | | +| Connection Request | CNR | | +| Continuity Indicators | CTI | | +| Correlation Identity | COR | | +| Display Information | DIS | | +| Echo Control Information | ECI | | +| Event Information Indicators | EVI | | +| Facility Indicators | FAI | | +| Forward Call Indicators | FCI | | +| Forward GVNS | FVN | | +| Generic Address (Generic Number) | GEA | | +| Generic Digits | GED | | +| Generic Notification Indicator | GNO | | +| Global Call Identification (Global Call Reference) | GCI | NSS-specific | +| Hard To Reach | HTR | | +| Hop Counter | HOC | | +| Information Indicators | INI | | +| Information Request Indicators | IRI | | +| IN Service Compatibility | INC | | +| Inter-nodal Traffic Group Identifier | ITG | | +| Interworking Function Address | IWF | BAT ASE | +| Known Field Compatibility Information | FDC | NSS-specific | + +| | | | +|----------------------------------------|-----|--------------| +| Location Number | LON | | +| Loop Prevention Indicator | LPI | | +| Mapped Parameter List | MPL | NSS-specific | +| MCID Request Indicator | MRI | | +| MCID Response Indicator | MCR | | +| Message Compatibility Information | MCI | | +| MLPP Precedence | MLP | | +| Nature of Connection Indicators | NOC | | +| Network Management Controls | NMC | | +| Network Routing Number | NRN | | +| Network Specific Facilities | NSF | | +| Number Portability Forward Information | NPF | | +| Optional Backward Call Indicators | OBI | | +| Optional Forward Call Indicators | OFI | | +| Original Called IN Number | OCI | | +| Original Called Number | OCN | | +| Originating ISC Point Code | ISC | | +| Parameter Compatibility Information | PCI | | +| Pivot Capability | PCA | | +| Pivot Counter | PCT | | +| Pivot Routing Backward Information | PBI | | +| Pivot Routing Forward Information | PFI | | +| Pivot Routing Indicator | PVR | | +| Pivot Status | PVS | | +| Propagation Delay Counter | PDC | | +| Protocol Name | PRN | NSS-specific | +| Query On Release Capability | QOR | | +| Redirect Backward Information | RBI | | +| Redirect Capability | RDC | | +| Redirect Counter | RCT | | +| Redirect Forward Information | RFI | | +| Redirect Status | RDS | | +| Redirecting Number | RGN | | +| Redirection Information | RNI | | +| Redirection Number | RNN | | +| Redirection Number Restriction | RNR | | +| Remote Operations | RMO | | + +| | | | +|-----------------------------------------|-----|--------------| +| SCF ID | SCF | | +| Segmentation Indicator | SEG | NSS-specific | +| Service Activation | SEA | | +| Signal | SIG | BAT ASE | +| Signalling Point Code | SPC | | +| Source Parameter Information | SPI | NSS-specific | +| Subsequent Number | SUN | | +| Suspend/Resume Indicators | SRI | | +| Transaction ID | TID | NSS-specific | +| Transit Network Selection | TNS | | +| Transmission Medium Required | TMR | | +| Transmission Medium Required Prime | TMP | | +| Transmission Medium Used | TMU | | +| UID Action Indicators | UID | | +| UID Capability Indicators | UCI | | +| Unknown Field Compatibility Information | UFC | NSS-specific | +| User Service Information | USI | | +| User Service Information Prime | USP | | +| User Teleservice Information | UTI | | +| User-To-User Indicators | UUI | | +| User-To-User Information | UUS | | +| Version of NSS | VER | NSS-specific | + +Telecommunications vendors and operators may wish to use new or private network-specific parameters. In such cases, the parameter must use a three-letter code different from the above list and should encapsulate it within the Parameter Compatibility Information (PCI) parameter so that intermediate nodes are not burdened. Nodes that agree to use that parameter should also agree on PRN values to indicate what parameter set to expect. + +The order of the parameters detailed in the remainder of clause 7 follows the order in the above list. The following list is ordered by NSS code to aid in finding the full parameter name. + +| NSS code | Parameter name | +|-----------------|-----------------------------| +| ACL | Automatic Congestion Level | +| ACT | Action Indicator | +| ADI | Access Delivery Information | +| APP | Application Transport | +| ATP | Access Transport | +| BAT | BAT Compatibility Report | +| BCD | Bearer Control Information | +| BCI | Backward Call Indicators | + +| | | +|-----|---------------------------------------------| +| BCT | Bearer Control Tunnelling | +| BDU | Bearer Control Unit Identifier | +| BID | Backward Network Connection Identifier | +| BNC | Bearer Network Connection Characteristics | +| BRC | Bearer Redirection Capability | +| BRI | Bearer Redirection Indicators | +| BVN | Backward GVNS | +| CAI | Cause Indicators | +| CCN | CCNR Possible Indicator | +| CCS | Call Completion Service Set-up | +| CDI | Call Diversion Information | +| CDL | Codec List | +| CDN | Called Directory Number | +| CDP | Coding Decoding Processing | +| CDT | Call Diversion Treatment Indicators | +| CGL | Calling Geodetic Location | +| CGN | Calling Party Number | +| CGV | Calling Party Geodetic Velocity Information | +| CHI | Call History Information | +| CIC | Circuit Identification (Call Instance) Code | +| CIN | Called IN Number | +| CNF | Conference Treatment Indicator | +| CNN | Connected Number | +| CNR | Connection Request | +| COD | Codec | +| COL | Collect Call Request | +| COR | Correlation Identity | +| CPC | Calling Party's Category | +| CPI | Charged Party Identification | +| CPN | Called Party Number | +| CRF | Call Reference | +| CSI | Carrier Selection Information | +| CTI | Continuity Indicators | +| CTN | Call Transfer Number | +| CTR | Call Transfer Reference | +| DIS | Display Information | +| ECI | Echo Control Information | + +| | | +|-----|----------------------------------------| +| EVI | Event Information Indicators | +| FAI | Facility Indicators | +| FCI | Forward Call Indicators | +| FDC | Known Field Compatibility Information | +| FVN | Forward GVNS | +| GCI | Global Call Identification | +| GEA | Generic Address | +| GED | Generic Digits | +| GIC | Closed User Group Interlock Code | +| GNO | Generic Notification Indicator | +| HOC | Hop Counter | +| HTR | Hard To Reach | +| INC | IN Service Compatibility | +| INI | Information Indicators | +| IRI | Information Request Indicators | +| ISC | Originating ISC Point Code | +| ITG | Inter-nodal Traffic Group Identifier | +| IWF | Interworking Function Address | +| LON | Location Number | +| LPI | Loop Prevention Indicator | +| MCI | Message Compatibility Information | +| MCR | MCID Response Indicator | +| MLP | MLPP Precedence | +| MPL | Mapped Parameter List | +| MRI | MCID Request Indicator | +| NMC | Network Management Controls | +| NOC | Nature of Connection Indicators | +| NPF | Number Portability Forward Information | +| NRN | Network Routing Number | +| NSF | Network-Specific Facilities | +| OBI | Optional Backward Call Indicators | +| OCI | Original Called IN Number | +| OCN | Original Called Number | +| OCT | Call Offering Treatment Indicators | +| OFI | Optional Forward Call Indicators | +| PBI | Pivot Backward Information | +| PCA | Pivot Capability | + +| | | +|-----|-----------------------------------------| +| PCI | Parameter Compatibility Information | +| PCT | Pivot Counter | +| PDC | Propagation Delay Counter | +| PFI | Pivot Forward Information | +| PRN | Protocol Name | +| PVR | Pivot Routing Indicator | +| PVS | Pivot Status | +| QOR | Query On Release Capability | +| RBI | Redirect Routing Backward Information | +| RCT | Redirect Counter | +| RDC | Redirect Capability | +| RDS | Redirect Status | +| RFI | Redirect Routing Forward Information | +| RGN | Redirecting Number | +| RMO | Remote Operations | +| RNI | Redirection Information | +| RNN | Redirection Number | +| RNR | Redirection Number Restriction | +| SCF | SCF ID | +| SEA | Service Activation | +| SEG | Segmentation Indicator | +| SIG | Signal | +| SPC | Signalling Point Code | +| SPI | Source Parameter Information | +| SRI | Suspend/Resume Indicators | +| SUN | Subsequent Number | +| TID | Transaction ID | +| TMP | Transmission Medium Required Prime | +| TMR | Transmission Medium Required | +| TMU | Transmission Medium Used | +| TNS | Transit Network Selection | +| UCI | UID Capability Indicators | +| UFC | Unknown Field Compatibility Information | +| UID | UID Action Indicators | +| USI | User Service Information | +| USP | User Service Information Prime | +| UTI | User Teleservice Information | + +| | | +|-----|--------------------------| +| UUI | User-To-User Indicators | +| UUS | User-To-User Information | +| VER | Version of NSS | + +## 7.3 Detailed parameter descriptions + +The designation "a" means all possible characters allowed in 5.1, unless otherwise constrained by the field description. The designation "d" means only characters 0-9 are used. The designation "h" means that the field or subfield is to be hexadecimal-encoded. + +The first field value for most fields will be the "unknown" value. "Unknown" means that the information was absent or unavailable at the source of the NSS encoding. + +The left-hand columns in the following clauses are **literal** values to be used as codepoints. The Format lines show "=" preceding the field values; however, these field names (tags) are not transmitted in the compact encoding used on the wire. + +### 7.3.1 Access Delivery Information (ADI) + +Format: ADI, adi=a + +Fields: + +Field-01: adi - access delivery indicator +a description +- ----- +u - unknown +y - set-up message generated +n - no set-up message generated + +### 7.3.2 Access Transport (ATP) + +Format: ATP, dat=1\*(2Hex) + +Fields: (may carry Q.931 IE) + +Field-01: dat - access Transport data +1\*(2h) description +- ----- +1\*(2h) - one or more pairs of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). +(If unknown, parameter is omitted.) + +### 7.3.3 Application Transport (APP) + +Format: APP, aci=a, sni=a, rci=a, si=a, seg=hh, slr=hh, apm=0\*(2Hex) + +Fields: + +Field-01: aci - application context identifier +a definition +- ----- +u - unknown +0 - Unidentified Context and Error Handling (UCEH) ASE +1 - PSS1 ASE (VPN) +2 - Charging ASE +3 - GAT ASE +4 - BAT ASE +5 - Enhanced Unidentified Context and Error Handling (EUCHEH) ASE + +Field-02: sni - send notification indicator + +a definition + +- - - - - + +u - unknown + +n - do not send notification + +y - send notification + +Field-03: rci - release call indicator + +a definition + +- - - - - + +u - unknown + +n - do not release call + +y - release call + +Field-04: si - sequence indicator + +a definition + +- - - - - + +0 - subsequent segment to first segment + +1 - new sequence + +Field-05: seg - segmentation indicator + +dd definition + +-- - - - - - + +00 + +-99 - 2 decimal digits 0-9 - indicates number +of following segments + +Field-06: slr - segmentation local reference + +hh definition + +-- - - - - - + +00 + +-FF - 2 hexadecimal digits 0-9 or A-F + +Field-07: apm - APM user information + +0\*(2h) description + +----- + +0\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a +hexadecimal encoding (see clause 5.1). + +See clause 7.4 for additional NSS parameters that must be used with the APP Field-01 code point number 4 (BAT ASE) instead of tunnelling in Field-07. In this case, Field-07 shall be left empty in the encoding of the APP parameter. When other Field-01 code point values are used, the APM user information is encoded in Field-07 and not parameters in clause 7.4. When Field-07 is empty and BAT ASE clause 7.4 parameters are absent from the message, then the APM user information value is "unknown". + +### 7.3.4 Automatic Congestion Level (ACL) + +Format: ACL,acl=a + +Fields: + +Field-01: acl - auto congestion level + +a description + +- - - - - + +u - unknown + +1 - congestion level 1 exceeded + +2 - congestion level 2 exceeded + +### 7.3.5 Backward Call Indicators (BCI) + +Format: BCI, cha=a, sta=a, cpc=dd, e2ei=a, e2em=a, inter=a, iupi=a, h=a, +acc=a, eco=a, sccpm=d + +Fields: + +Field-01: cha - charge indicator + +a description +- ----- +0 - no indication +y - charge +n - no charge + +Field-02: sta - called party status + +a description +- ----- +0 - no indication +f - subscriber free +c - connect when free + +Field-03: cpc - call(ed) party category (reuses clause 7.3.21 cpc=field) + +dd description +-- ----- +00 - unknown/no indication +09 - ordinary subscriber +15 - public payphone + +Field-04: e2ei - end-to-end information indicator + +a definition +- ----- +u - unknown (meaning 'No Indication') +y - end-to-end information is available +n - end-to-end information is not available + +Field-05: e2em - end-to-end method indicator + +a definition +- ----- +u - unknown +n - no end-to-end method available +1 - pass-along method available +2 - SCCP method available +3 - pass-along and SCCP methods available + +Field-06: inter - interworking Indicator + +a definition +- ----- +u - unknown +y - interworking has been encountered +n - interworking has not been encountered (SS7/BICC all the way) + +Field-07: iupi - ISDN user part indicator + +a definition +- ----- +u - unknown +y - ISDN user part/BICC is used all the way +n - ISDN user part/BICC is not used all the way + +Field-08: h - hold indicator + +a definition +- ----- +u - unknown +y - call hold requested +n - call hold not requested + +Field-09: acc - ISDN access indicator + +a definition + +- ----- + +u - unknown + +y - Terminating access is ISDN + +n - Terminating Access is not ISDN + +Field-10: eco - Echo control device indicator + +a definition + +- ----- + +u - unknown + +y - incoming half echo device included + +n - incoming half echo device not included + +Field-11: sccpm - SCCP Method Indicator + +d definition + +- ----- + +0 - no indication + +1 - connectionless method available + +2 - connection-oriented method available + +3 - connectionless and connection-oriented methods available + +### 7.3.6 Backward GVNS (BVN) + +Format: BVN,tai=a + +Fields: + +Field-01: tai - terminating access indicator + +a description + +- ----- + +0 - no information + +d - dedicated terminating access + +s - switched terminating access + +### 7.3.7 Call Completion Service Set-up (CCS) + +Format: CCS,ccss=a + +Fields: + +Field-01: ccss - CCSS call indicator + +a description + +- ----- + +0 - no indication + +y - CCSS call + +### 7.3.8 Call Diversion Information (CDI) + +Format: CDI,nso=a,rr=a + +Fields: + +Field-01: nso - notification subscription options + +a description + +- ----- + +u - unknown + +1 - presentation restricted + +2 - presentation allowed with redirection number + +3 - presentation allowed without redirection number + +Field-02: rr - redirecting reason +a description +- ----- +u - unknown +1 - user busy +2 - no reply +3 - unconditional +4 - deflection during alerting +5 - deflection immediate response +6 - mobile subscriber not reachable + +### 7.3.9 Call Diversion Treatment Indicators (CDT) + +Format: CDT,ct=a + +Fields: + +Field-01: ct - call diversion treatment +a definition +- ----- +u - unknown +y - call diversion allowed +n - call diversion not allowed + +### 7.3.10 Call History Information (CHI) + +Format: CHI,pd=ddddd + +Fields: + +Field1 : pd - propagation delay +ddddd definition +----- +00000 - delay unknown +-65535 - delay in milliseconds + +### 7.3.11 Call Offering Treatment Indicators (OCT) + +Format: OCT,coi=a + +Fields: + +Field-01: coi - call offering treatment indicator +a description +- ----- +u - unknown +n - call offering not allowed +y - call offering allowed + +### 7.3.12 Call Reference (CRF) + +Format: CRF,cid=hhhhhh,pc=aaaaaaaaaa + +Fields: + +Field-01: cid - call identity +hhhhhh description +----- +000000 - 6 characters 0-9, A-F representing hexadecimal values +-FFFFFF + +Field-02: pc - Point Code + +``` + +aaaaaaaaaa description +----- +nnn.ccc.mmm - nine characters separated by two periods, where + nnn is for network/zone (most significant 3 or 8 bits), + ccc is for cluster/area (middle 8 bits), + mmm is for member (least significant 3 or 8 bits). + The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 + representing the decimal equivalent of the subfield viewed + as a binary number. [NOTE - ITU format is 3.8.3 bit.] + +``` + +### 7.3.13 Call Transfer Number (CTN) + +Format: CTN,noa=dd,npi=a,pi=a,si=a,#=1\*h + +Fields: + +Field-01: noa - nature of address + +``` + +dd description +-- ----- +00 - unknown, number present +02 - unique subscriber number +04 - unique national (significant) number +06 - unique international number +08 - network-specific number +30 - network routing number in national (significant) format +31 - network routing number in network-specific format +32 - network routing number concatenated with Called Directory + Number +35 - PISN specific number + +``` + +[NOTE - noa= appears in the following additional parameters: + CDN, CPN, CIN, CGN, CNN, FVN, GEA, HTR, LON, OCI, OCN, RGN, RNN. + Those parameters refer back to the above list because of its + size. The NRN parameters use alternative lists.] + +Field-02: npi - numbering plan indicator + +``` + +a description +- ----- +u - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +``` + +Field-03: pi - presentation indicator + +``` + +a description +- ----- +u - unknown +y - presentation allowed +n - presentation restricted +0 - address not available + +``` + +Field-04: si - screening indicator + +``` + +a description +- ----- +u - unknown +1 - user provided not screened +2 - user provided screening passed +3 - user provided screening failed +4 - network provided + +``` + +Field-05: # - address + +``` + +1*h description + +``` + +--- +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.14 Call Transfer Reference (CTR) + +Format: CTR,ref=ddd + +Fields: + +Field-01: ref - call transfer reference +ddd description +--- +000 - positive integer number 0-9 (omit if parameter unknown) +-255 + +### 7.3.15 Called Directory Number (CDN) + +Format: CDN,noa=dd,inn=a,npi=a,#=1\*h + +Fields: + +Field-01: noa - nature of address +dd description +-- +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-02: inn - internal network number indicator +a description +- +u - unknown +n - routing to internal network number not allowed +y - routing to internal network number allowed + +Field-03: npi - numbering plan indicator +a description +- +u - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +Field-04: # - address +1\*h description +--- +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.16 Called IN Number (CIN) + +Format: CIN,noa=dd,npi=a,pi=a,#=1\*h + +Fields: + +Field-01: noa - nature of address +dd description +-- +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +``` + +Field-02: npi - numbering plan indicator +a description +- ----- +u - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +Field-03: pi - presentation indicator +a description +- ----- +u - unknown +y - presentation allowed +n - presentation restricted +0 - address not available + +Field-04: # - address +1*h description +--- ----- +1*h - one or more telephony digits: 0-9, A-F + (see formal grammar) + +``` + +### 7.3.17 Called Party Number (CPN) + +Format: CPN,noa=dd,inn=a,npi=a,#=1\*h + +Fields: + +``` + +Field-01: noa - nature of address +dd description +-- ----- + See definition of "noa=" in clause 7.3.13, + Call Transfer Number (CTN). + +Field-02: inn - Internal network number indicator +a description +- ----- +u - unknown +n - routing to internal network number not allowed +y - routing to internal network number allowed + +Field-03: npi - numbering plan indicator +a description +- ----- +u - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +Field-04: # - address +1*h description +--- ----- +1*h - one or more telephony digits: 0-9, A-F + (see formal grammar) + +``` + +### 7.3.18 Calling Geodetic Location (CGL) + +Format: CGL,pi=a,si=a,type=d,[Field Container] + +Fields: + +Field-01: pi - presentation indicator + +a description +- ----- +u - unknown +y - presentation allowed +n - presentation restricted +0 - location not available + +Field-02: si - screening indicator + +a description +- ----- +u - unknown +1 - user provided not screened +2 - user provided screening passed +3 - user provided screening failed +4 - network provided + +Field-03: type - type of shape + +| | | | +|---|---------------------------------------------------------|-------------------| +| d | description | | +| - | ----- | | +| u | unknown | | +| 0 | ellipsoid point | field container 1 | +| 1 | ellipsoid point with uncertainty | field container 2 | +| 2 | ellipsoid point with altitude and uncertainty | field container 3 | +| 3 | ellipse on ellipsoid | field container 4 | +| 4 | ellipsoid circle sector | field container 5 | +| 5 | polygon | field container 6 | +| 6 | ellipsoid point with altitude | field container 7 | +| 7 | ellipsoid point with altitude and uncertainty ellipsoid | field container 8 | +| 8 | ellipsoid arc | field container 9 | + +Field containers: + +Field container 1 - ellipsoid point + +Format: ns=d,lat=1\*d,lon=1\*d + +Field-04: ns - north/south + +d description +- ----- +0 - north +1 - south + +Field-05: lat - degrees of latitude + +1\*d description +- ----- +1\*d - This field value is the decimal equivalent of the 23-bit binary value N, that when multiplied by 90 and divided by $2^{23}$ produces degrees and fraction of degrees to multiple decimal places of precision. This note applies to all latitude fields in this parameter. +Example: 111 0000 0000 0000 0000 0000 = 7,340,032 + $x \ 90 = 660,602,880 / 2^{23} = 78.75$ degrees. +In other words, $N/(2^{23})$ produces a fraction $0 \leq X < 1$ of the total 90 degrees. + +Field-06: lon - degrees of longitude + +1\*d description + +- - - - - + +1\*d - This field value is the decimal equivalent of the 24-bit binary value N, that when multiplied by 360 and divided by $2^{24}$ produces degrees and fraction of degrees to multiple decimal places of precision. For conversion to negative degrees West, when resulting degrees exceed 180, subtract 360. This note applies to all longitude fields in this parameter. + +Example: $N/(2^{24}) \times 360$ is similar to that above. A value of 275 degrees converts to: $275 - 360 = -85$ degrees West. + +Field container 2 - ellipsoid point with uncertainty + +Format: ns=d, lat=1\*d, lon=1\*d, unc=d, con=d + +Field-04: ns - north/south + +d description + +- - - - - + +0 - north + +1 - south + +Field-05: lat - degrees of latitude + +1\*d description + +- - - - - + +1\*d - same as in field container 1 + +Field-06: lon - degrees of longitude + +1\*d description + +- - - - - + +1\*d - same as in field container 1 + +Field-07: unc - uncertainty + +1\*d description + +- - - - - + +1\*d - This field value is the decimal equivalent of the 7-bit binary value K used in the formula: +$$\text{uncertainty} = 10 \times [(1.1)^K - 1]$$ + that produces uncertainty values in the range of 0 to 1800 metres. This applies to all Latitude/Longitude uncertainty fields in this parameter. + +Field-08: con - confidence + +1\*d description + +- - - - - + +1\*d - This field value is the decimal equivalent of the 7-bit binary value $0 \leq K \leq 100$ expressed as a percentage, and where K=0 means "no information". +This applies to any confidence field in this parameter. + +Field container 3 - ellipsoid point with altitude and uncertainty + +Format: ns=d, lat=1\*d, lon=1\*d, unc=1\*d, as=d, alt=1\*d, +auc=1\*d, con=1\*d [NOTE - continued on same line.] + +Field-04: ns - north/south + +d description + +- - - - - + +0 - north + +1 - south + +Field-05: lat - degrees of latitude +1\*d description + +1\*d - same as in field container 1 + +Field-06: lon - degrees of longitude +1\*d description + +1\*d - same as in field container 1 + +Field-07: unc - uncertainty +1\*d description + +1\*d - same as in field container 2 + +Field-08: as - altitude sign +d description + +0 - above ellipsoid +1 - below ellipsoid + +Field-09: alt - altitude +1\*d description + +1\*d - This field value is the decimal equivalent of the 15-bit binary value indicating $0 \leq a \leq 32767$ metres. This applies to any altitude field in this parameter. + +Field-10: auc - altitude uncertainty code +1\*d description + +1\*d - This field value is the decimal equivalent of the 7-bit binary value K used in the formula: +uncertainty = $45 \times [(1.025)^K - 1]$ that produces uncertainty values in the range of 0 to 1000 metres. This note applies to all altitude uncertainty fields in this parameter. + +Field-11: con - confidence +1\*d description + +1\*d - same as in field container 2 + +Field container 4 - ellipse on ellipsoid + +Format: ns=d, lat=1\*d, lon=1\*d, maj=1\*d, min=1\*d, ori=1\*d, +con=1\*d + +Field-04: ns - latitude sign +d description + +0 - north +1 - south + +Field-05: lat - degrees of latitude +1\*d description + +1\*d - same as in field container 1 + +Field-06: lon - degrees of longitude +1\*d description + +1\*d - same as in field container 1 + +Field-07: maj - major radius + 1\*d description + --- + 1\*d - This field value is the decimal equivalent of the 7-bit binary value K used in the formula: + +$$\text{radius} = 10 \times [(1.1)^K - 1]$$ + that produces radius values in the range of 0 to 1800 metres. This note applies to most Radius fields in this parameter. + +Field-08: min - minor radius + 1\*d description + --- + 1\*d - same as major radius above + +Field-09: ori - orientation + 1\*d description + --- + 1\*d - This field value is the decimal equivalent of the 8-bit binary value $0 \leq K \leq 180$ degrees. This applies to any orientation field in this parameter. + +Field-10: con - confidence + 1\*d description + --- + 1\*d - same as in field container 2 + +Field container 5 - ellipsoid circle sector + +Format: ns=d, lat=1\*d, lon=1\*d, rad=1\*d, off=1\*d, ang=1\*d, con=1\*d + +Field-04: ns - north/south + d description + - + 0 - north + 1 - south + +Field-05: lat - degrees of latitude + 1\*d description + --- + 1\*d - same as in field container 1 + +Field-06: lon - degrees of longitude + 1\*d description + --- + 1\*d - same as in field container 1 + +Field-07: rad - radius + 1\*d description + --- + 1\*d - same as major radius in container 4 + +Field-08: off - offset angle + 1\*d description + --- + 1\*d - This field value is the decimal equivalent of the 8-bit binary value $0 \leq K \leq 180$ with degrees= $2 \times K$ , where 0 degrees is North and 90 degrees is East. This applies to any offset or included angle field in this parameter. + +Field-09: ang - included angle +1\*d description +--- +1\*d - same as offset angle above + +Field-10: con - confidence +1\*d description +--- +1\*d - same as in field container 2 + +Field container 6 - polygon + +Format: num=dd, (3\*15{ns=d, lat=1\*d, lon=1\*d}), con=1\*d + +Field-04: num - number of points +dd description +-- +03 - the number of points in the polygon +-15 + +For each point in the polygon, a tuple of three fields is needed to describe that point. The number of tuples is indicated by Field-04 above. Each tuple must begin with an open brace "{", end with a close brace "}", with tuples comma-delimited. A comma separates subfields within the tuple. Example: + +Triangle: ({ns=0, lat=33, lon=89}, +{ns=0, lat=34, lon=90}, +{ns=0, lat=34, lon=89}) + +In the following fields, T1, T2, and T3 compose the tuple: + +Field-T1: ns - north/south +d description +- +0 - north +1 - south + +Field-T2: lat - degrees of latitude +1\*d description +- +1\*d - same as in field container 1 + +Field-T3: lon - degrees of longitude +1\*d description +- +1\*d - same as in field container 1 + +A single occurrence of confidence ends the parameter: + +Field-NN: con - confidence +1\*d description +--- +1\*d - same as in field container 2 + +Field container 7 - ellipsoid point with altitude + +Format: ns=d, lat=1\*d, lon=1\*d, as=d, alt=1\*d + +Field-04: ns - north/south +d description +- +0 - north +1 - south + +Field-05: lat - degrees of latitude +1\*d description +- ----- +1\*d - same as in field container 1 + +Field-06: lon - degrees of longitude +1\*d description +- ----- +1\*d - same as in field container 1 + +Field-07: as - altitude sign +d description +- ----- +0 - above ellipsoid +1 - below ellipsoid + +Field-08: alt - altitude +1\*d description +--- ----- +1\*d - same as in field container 3 + +Field container 8 - ellipsoid point with altitude and +uncertainty ellipsoid + +Format: ns=d, lat=1\*d, lon=1\*d, as=d, alt=1\*d, maj=1\*d, min=1\*d, +ori=1\*d, auc=1\*d, con=1\*d + +Field-04: ns - latitude sign +d description +- ----- +0 - north +1 - south + +Field-05: lat - degrees of latitude +1\*d description +--- ----- +1\*d - same as in field container 1 + +Field-06: lon - degrees of longitude +1\*d description +--- ----- +1\*d - same as in field container 1 + +Field-07: as - altitude sign +d description +- ----- +0 - above ellipsoid +1 - below ellipsoid + +Field-08: alt - altitude +1\*d description +--- ----- +1\*d - same as in field container 3 + +Field-09: maj - major radius +1\*d description +--- ----- +1\*d - same as in field container 4 + +Field-10: min - minor radius +1\*d description +--- ----- +1\*d - see ITU-T Recs Q.763/Q.1902.3 for encoding + +Field-11: ori - orientation +1\*d description +--- +1\*d - same as in field container 4 + +Field-12: auc - altitude uncertainty code +1\*d description +--- +1\*d - same as in field container 3 + +Field-13: con - confidence +1\*d description +--- +1\*d - same as in field container 2 + +Field container 9 - ellipsoid arc + +Format: ns=d, lat=1\*d, lon=1\*d, inr=1\*d, unc=1\*d, off=1\*d, ang=1\*d, +con=1\*d + +Field-04: ns - latitude sign +d description +- +0 - north +1 - south + +Field-05: lat - degrees of latitude +1\*d description +--- +1\*d - same as in field container 1 + +Field-06: lon - degrees of longitude +1\*d description +--- +1\*d - same as in field container 1 + +Field-07: inr - inner radius +1\*d description +--- +1\*d - This field value is the decimal equivalent of the +16-bit binary value N used in the standard formula. This +note applies to most Radius fields in this parameter. + +Field-08: unc - uncertainty radius (identical to uncertainty) +1\*d description +--- +1\*d - same as in field container 2 + +Field-09: off - offset angle +1\*d description +--- +1\*d - same as in field container 5 + +Field-10: ang - included angle +1\*d description +--- +1\*d - same as offset angle in container 5 + +Field-11: con - confidence +1\*d description +--- +1\*d - same as in field container 2 + +### 7.3.19 Calling Party Geodetic Velocity Information (CGV) + +Format: CGV,pi=a,si=a,type=d,[field container] + +Based on the value of "type", none or one of the following field containers will follow. This parameter can appear multiple times, indicating different types of information within the same message. + +Fields: + +Field-01: pi - presentation indicator + +a description + +- ----- + +u - unknown + +y - presentation allowed + +n - presentation restricted + +0 - location not available + +Field-02: si - screening indicator + +a description + +- ----- + +u - unknown + +1 - user provided not screened + +2 - user provided screening passed + +3 - user provided screening failed + +4 - network provided + +Field-03: type - type of geodetic velocity information + +d definition + +- ----- + +0 - unknown + +1 - Horizontal velocity field container 1 + +2 - Horizontal with Vertical velocity field container 2 + +3 - Horizontal velocity with Uncertainty field container 3 + +4 - Horizontal with Vertical velocity +and Uncertainty field container 4 + +Field Containers: + +Field Container 1 (type=1) + +Format: bear=ddd,hvel=ddddd + +Fields: + +Field-04: bear - bearing + +ddd definition + +--- ----- + +000 - degrees clockwise from North + +-360 (maximum) + +Field-05: hvel - horizontal speed + +ddddd definition + +----- + +00000 - rounded up to nearest kilometer per hour + +-65535 (e.g., X.5 rounds to X+1) + +Field Container 2 (type=2) + +Format: bear=ddd,hvel=ddddd,dir=d,vvel=ddd + +Fields: + +Field-04: bear - bearing + +ddd definition + +--- ----- + +000 - degrees clockwise from North + +-360 (maximum) + +Field-05: hvel - horizontal speed + +ddddd definition + +----- + +00000 - rounded up to nearest kilometer per hour + +-65535 (e.g., X.5 rounds to X+1) + +Field-06: dir - direction of vertical speed + +d definition + +- ----- + +0 - upward + +1 - downward + +Field-07: vvel - vertical speed + +ddd definition + +--- ----- + +000 - rounded up to nearest kilometer per hour + +-255 (e.g., X.5 rounds to X+1) + +Field Container 3 (type=3) + +Format: bear=ddd,hvel=ddddd,hu=ddd + +Fields: + +Field-04: bear - bearing + +ddd definition + +--- ----- + +000 - degrees clockwise from North + +-360 (maximum) + +Field-05: hvel - horizontal speed + +ddddd definition + +----- + +00000 - rounded up to nearest kilometer per hour + +-65535 (e.g., X.5 rounds to X+1) + +Field-06: hu - horizontal uncertainty speed + +ddd definition + +--- ----- + +000 - increments of one kilometer per hour + +-254 + +255 - indicates that uncertainty is not specified + +Field Container 4 (type=4) + +Format: bear=ddd,hvel=ddddd,hu=ddd,dir=d,vvel=ddd,vu=ddd + +Fields: + +Field-04: bear - bearing + +ddd definition + +--- ----- + +000 - degrees clockwise from North + +-360 (maximum) + +``` + +Field-05: hvel - horizontal speed + ddddd definition + ----- + 00000 - rounded up to nearest kilometer per hour + -65535 (e.g., X.5 rounds to X+1) + +Field-06: hu - horizontal uncertainty speed + ddd definition + --- ----- + 000 - increments of one kilometer per hour + -254 + 255 - indicates that uncertainty is not specified + +Field-07: dir - direction of vertical speed + d definition + - ----- + 0 - upward + 1 - downward + +Field-08: vvel - vertical speed + ddd definition + --- ----- + 000 - rounded up to nearest kilometer per hour + -255 (e.g., X.5 rounds to X+1) + +Field-09: vu - vertical uncertainty speed + ddd definition + --- ----- + 000 - increments of one kilometer per hour + -254 + 255 - indicates that uncertainty is not specified + +``` + +### 7.3.20 Calling Party Number (CGN) + +Format: CGN,noa=dd,cni=a,npi=a,pi=a,si=a,#=1\*h + +Fields: + +``` + +Field-01: noa - nature of address + dd description + -- ----- + See definition of "noa=" in clause 7.3.13, + Call Transfer Number (CTN). + +Field-02: cni - complete number indicator + a description + - ----- + u - unknown + y - number complete + n - number incomplete + +Field-03: npi - numbering plan indicator + a description + - ----- + u - unknown + 1 - ISDN numbering plan (ITU-T Rec. E.164) + 2 - Data numbering plan (ITU-T Rec. X.121) + 3 - Telex numbering plan (ITU-T Rec. F.69) + 4 - Private numbering plan + 5 - national + +``` + +Field-04: pi - presentation indicator + +a description + +- - - - - + +u - unknown + +y - presentation allowed + +n - presentation restricted + +0 - address not available + +1 - restricted by network + +Field-05: si - screening indicator + +a description + +- - - - - + +u - unknown + +1 - user provided not screened + +2 - user provided screening passed + +3 - user provided screening failed + +4 - network provided + +Field-06: # - address + +1\*h description + +- - - - - + +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.21 Calling Party's Category (CPC) + +Format: CPC,cpc=dd + +Fields: + +Field-01: cpc - Call(ing) Party Category + +(Calling or called derived from parameter context) + +dd description + +- - - - - + +00 - unknown + +01 - operator, Language French + +02 - operator, Language English + +03 - operator, Language German + +04 - operator, Language Russian + +05 - operator, Language Spanish + +06 - admin1 + +07 - admin2 + +08 - admin3 + +09 - ordinary calling subscriber + +11 - calling subscriber with priority + +12 - data call (voiceband data) + +13 - test call + +15 - public payphone + +19 - IEPS call marking for preferential call set-up + +### 7.3.22 Carrier Selection Information (CSI) + +Format: CSI,csi=dd + +Fields: + +Field-01: csi - carrier selection information (omit parm if unknown) + +dd description + +- - - - - + +00 - no indication + +01 - selected carrier identification pre-subscribed and no +input by calling party + +02 - selected carrier identification pre-subscribed and +input by calling party + +- 03 - selected carrier identification pre-subscribed and input by calling party undetermined +- 04 - selected carrier identification not pre-subscribed and input by calling party +- 05 - primary preferred carrier of the charged party +- 06 - alternate preferred carrier of the charged party +- 07 - selected carrier identification presubscription unknown (verbal) instructions from the calling party +- 08 - selected carrier identification presubscription unknown (verbal) instructions from the charged party +- 09 - emergency call handling +- 10 - carrier selected by input from the calling party +- 11 - carrier selected by a network operator + +### 7.3.23 Cause Indicators (CAI) + +Format: CAI, cs=a, loc=aaa, rec=a, cau=ddd, +           di={condition\_coding, tni\_coding, ccbs\_ind, +               call\_rejected\_ind, cdpn\_coding, fac\_id\_reject, +               attribute\_ids, chan\_type, incompat\_param, +               timer\_num, msg\_type, param\_name} + +[NOTE - The eleven subfields according to ITU-T Rec. Q.850 may occur. Their values are defined in detail in the grammar in Annex A. When no diagnostics are included, the braces and all between the braces are omitted, and only the comma before the di= remains.] + +Fields: + +Field-01: cs - code standard + +a definition + - ----- + u - unknown + c - ITU-T standardized coding + i - ISO/IEC + n - national standard + p - standard defined for the network either public or private + +Field-02: loc - location + +aaa definition + --- ----- + unk - unknown + usr - user + lpn - local private network (private network serving local user) + lln - local public network (public network serving local user) + tra - transit network + rln - remote local network (public network serving remote user) + rpn - remote private network (private network serving remote user) + int - international network + bip - network beyond interworking point + +Field-03: rec - recommendation (specific standard) + +a definition + - ----- + u - unknown + q - ITU-T Rec. Q.763 + p - Public land and mobile networks, Q.1000-series Recommendations + 1 - ITU-T Rec. X.21 + 5 - ITU-T Rec. X.25 + +Field-04: cau - cause indicators + +ddd definition + --- ----- + 000 - unknown + +001 - Unallocated number + 002 - no route to specified transit network + 003 - no route to destination + 004 - send special information tone + 005 - misdialled trunk prefix + 006 - channel unacceptable + 007 - call awarded and being delivered in an established channel + 008 - preemption + 009 - preemption - circuit reserved for reuse + 014 - Query On Release (QOR): ported number + 016 - normal call clearing + 017 - user busy + 018 - no user responding + 019 - no answer from user + 020 - subscriber absent + 021 - call rejected + 022 - number changed + 023 - redirect to new destination (e.g., release to pivot) + 024 - call rejected due to feature at the destination + 026 - non-selected user clearing + 027 - destination out of order + 028 - invalid number format + 029 - facility rejected + 030 - response to status enquiry + 031 - normal unspecified + 034 - no circuit/channel available + 038 - network out of order + 039 - permanent frame mode connection out of service + 040 - permanent frame mode connection operational + 041 - temporary failure + 042 - switching equipment congestion + 043 - access information discarded + 044 - requested circuit/channel not available + 046 - precedence call blocked + 047 - resource unavailable unspecified + 049 - quality of service unavailable + 050 - requested facility not subscribed + 053 - outgoing calls barred within CUG + 055 - incoming calls barred within CUG + 057 - bearer capability not authorized + 058 - bearer capability not presently available + 062 - Inconsistency in designated outgoing access information and + subscriber class + 063 - service or option not available unspecified + 065 - bearer capability not implemented + 066 - channel type not implemented + 069 - requested facility not implemented + 070 - only restricted digital information bearer capability is + available + 079 - service or option not implemented unspecified + 081 - invalid call reference value + 082 - identified channel does not exist + 083 - a suspended call exists but this call identity does not + 084 - call identity in use + 085 - no call suspended + 086 - call having the requested call identity has been cleared + 087 - user not member of CUG + 088 - incompatible destination + 090 - non-existent CUG + 091 - invalid transit network selection + 095 - invalid message unspecified + 096 - mandatory information element missing + 097 - message type non-existent or not implemented + 098 - message not compatible with call state or + +message type non-existent or not implemented + 099 - information element/parameter not implemented + 100 - invalid parameter contents + 101 - message not compatible with call state + 102 - recovery on timer expiry + 103 - parameter non-existent or not implemented passed on + 110 - message with unrecognised parameter + 111 - protocol error unspecified + 127 - interworking unspecified + +Field-05: di - diagnostics + +di={condition\_coding, tni\_coding, ccbs\_ind, call\_rejected\_ind, + cdpn\_coding, fac\_id\_reject, attribute\_ids, chan\_type, + incompat\_param, timer\_num, msg\_type, param\_name} + +[NOTES - Subfields tni\_codings and attribute\_ids may occur multiple times. When that occurs, the subfield encoding takes the form of: + ... , (val1, val2, val3), ... in the comma-delimited list within the di= braces. + +The value of the subfield may also be a tuple of values. In that case, that one subfield takes the form of: + +... , ({part1-1, part1-2, part1-3}, {part2-1, part2-2, part2-3}), ... + +Note that any collective set of related values, be it di={ } or the set composing the subfield value {part1, part2, part3} are enclosed with braces. In contrast, parentheses () are used to enclose multiple instances of the same type of value. Combined example: + , di={val1, ({x1, x2, x3}, {y1, y2, y3}), , , , , , , , , } with 2 instances of value 2 named x and y, each composed of 3 sub-subfields. + +The twelve subfields according to Q.850 may occur independently. Their values are defined in detail in the grammar in Annex A. + +When no diagnostics are included, the compact form uses only one comma: ",di=" becomes "," -- NOT ",di={ , , , , , , , , , , }" and ",{ , , , , , , , , , , }". + +Note that if any subfield is present, the braces and all placeholder commas are required: , { , , , , , val8, , , , } ] + +### 7.3.24 CCNR Possible Indicator (CCN) + +Format: CCN, cpi=a + +Fields: + +Field-01: cpi - ccnr possible indicator + a definition + + u - unknown + n - CCNR not possible + y - CCNR possible + +### 7.3.25 Charged Party Identification (CPI) + +Format: CPI, dat=1\*(2Hex) + +Fields: + +Field-01: dat - charge information used in ITU-T Rec. Q.1218 or Q.1228 + 1\*(2h) description + +1\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). +(If unknown, parameter is omitted.) + +### 7.3.26 Circuit Identification (Call Instance) Code (CIC) + +Format: CIC,cic=ddddddddd + +Field-01: cic - circuit identification code +ddddddddd description +----- +0000000000 - unknown +-4294967295 ten-digit positive integer + +### 7.3.27 Closed User Group Interlock Code (GIC) + +Format: GIC,ni=hhhh,bc=hhhh + +Field-01 : ni - network identity +hhhh description +---- ----- +0000 - unknown +-FFFF positive integer of 0-9, A-F + +Field-02 : bc - binary code +hhhh description +---- ----- +0000 - unknown +-FFFF four digits of 0-9, A-F. + +### 7.3.28 Coding Decoding Processing (CDP) + +Format: CDP,toc=aaaa,comp=d + +Fields: + +Field-01: toc - type of compression +aaaa description +---- ----- +ulaw - G.711 m-law +alaw - G.711 A-law +g726 - G.726 32 kbit/s ADPCM +g728 - G.728 LD-CELP +g729 - G.729 CS-ACELP + +Field-02: comp - compression status indicator +d definition +- ----- +0 - Decompressed +1 - Compressed + +### 7.3.29 Collect Call Request Indicator (COL) + +Format: COL,cci=a + +Fields: + +Field-01: cci - collect Call Indicator +a description +- ----- +0 - no indication +y - collect call request + +### 7.3.30 Conference Treatment Indicators (CNF) + +Format: CNF,cai=a + +Fields: + +Field-01: cai - conference acceptance indicator +a definition +- ----- +0 - no indication +y - accept conference request +n - reject conference request + +### 7.3.31 Connected Number (CNN) + +Format: CNN,noa=dd,npi=a,pi=a,si=a,#=1\*h + +Fields: + +Field-01: noa - nature of address +dd description +-- ----- +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-02: npi - numbering plan indicator +a description +- ----- +u - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +Field-03: pi - presentation indicator +a description +- ----- +u - unknown +y - presentation allowed +n - presentation restricted +0 - address not available + +Field-04: si - screening indicator +a description +- ----- +u - unknown +1 - user provided not screened +2 - user provided screening passed +3 - user provided screening failed +4 - network provided + +Field-05: # - address +1\*h description +--- ----- +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.32 Connection Request (CNR) + +Format: CNR, loc=hhhhhh, pc=aaaaaaaaaa, cls=ddd, cre=ddd + +Fields: + +Field-01: loc - local reference + +hhhhhh description + +----- + +000000 - unknown + +-FFFFFF 0-9, A-F + +Field-02: pc - Point Code + +aaaaaaaaaa description + +----- + +nnn.ccc.mmm - nine characters separated by two periods, where +nnn is for network/zone (most significant 3 or 8 bits), +ccc is for cluster/area (middle 8 bits), +mmm is for member (least significant 3 or 8 bits). +The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 +representing the decimal equivalent of the subfield viewed +as a binary number. [NOTE - ITU format is 3.8.3 bit.] + +Field-03: cls - protocol class + +ddd description + +--- + +000 - classes 0-255 + +-255 + +Field-04: cre - credit + +ddd description + +--- + +000 - credit 0-255 + +-255 + +### 7.3.33 Continuity Indicators (CTI) + +Format: CTI, cti=a + +Fields: + +Field-01: cti - continuity indicator + +a description + +- + +u - unknown + +f - continuity check failed + +s - continuity check successful + +### 7.3.34 Correlation Identity (COR) + +Format: COR, dat=1\*(2Hex) + +Fields: + +Field-01: dat - representation of the parameter contents + +1\*(2h) description + +----- + +1\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a +hexadecimal encoding (see clause 5.1). +(If unknown, parameter is omitted.) + +### 7.3.35 Display Information (DIS) + +Format: DIS, info=1\* (2Hex) + +Fields: + +Field-01: info - display info +1\* (2h) description +----- +1\* (2h) - one or more *pairs of characters* (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). +(If unknown, parameter is omitted.) + +### 7.3.36 Echo Control Information (ECI) + +Format: ECI, oei=d, ie=d, oer=a, ier=a + +Fields: + +Field-01: oei - outgoing echo device control information indicator +d description +- ----- +0 - no information +1 - outgoing echo control device included +2 - outgoing echo control device not included but available +3 - outgoing echo control device not included and not available + +Field-02: ie - incoming echo device control information indicator +d description +- ----- +0 - no information +1 - incoming echo control device included +2 - incoming echo control device not included but available +3 - incoming echo control device not included and not available + +Field-03: oer - outgoing echo device control request indicator +a description +- ----- +0 - no information +a - outgoing echo control device activation request +d - outgoing echo control device deactivation request + +Field-04: ier - incoming echo device control request indicator +a description +- ----- +0 - no information +a - incoming echo control device activation request +d - incoming echo control device deactivation request + +### 7.3.37 Event Information Indicators (EVI) + +Format: EVI, evi=a, evr=a + +Fields: + +Field-01: evi - event information indicator +a description +- ----- +u - unknown +a - Alerting +p - Progress +i - in-band information or pattern is now available +1 - call forwarded on busy +2 - call forwarded on no reply + +3 - call forwarded unconditional + +Field-02: evr - event presentation restriction indicator + +a definition + +- ----- + +0 - no indication + +y - presentation restricted + +n - not restricted + +### 7.3.38 Facility Indicators (FAI) + +Format: FAI,fai=a + +Fields: + +Field-01: fai - facility indicator + +a definition + +- ----- + +s - user-to-user service + +### 7.3.39 Forward Call indicators (FCI) + +Format: FCI,int=a,e2ei=a,e2em=a,inter=a,iupi=a,pref=a,acc=a, +sccpm=a + +Fields: + +Field-01: int - international call indicator + +a definition + +- ----- + +u - unknown + +y - yes - call to be treated as an international call + +n - no - call to be treated as a national call + +Field-02: e2ei - end-to-end information indicator + +a definition + +- ----- + +u - unknown + +y - end-to-end information available (ISUP)/reserved (BICC) + +n - no end-to-end information available + +Field-03: e2em - end-to-end method indicator + +a definition + +- ----- + +u - unknown + +n - no end-to-end method available (only link-by-link method available) + +1 - pass-along method available (national use) (ISUP)/reserved (BICC) + +2 - SCCP method available (ISUP)/reserved (BICC) + +3 - pass-along and SCCP methods available(national use) (ISUP)/ +reserved (BICC) + +Field-04: inter - interworking indicator + +a definition + +- ----- + +u - unknown + +y - interworking encountered + +n - no interworking encountered (Signalling System No. 7/BICC all the way) + +Field-05: iupi - ISDN user part/BICC indicator + +a definition + +- ----- + +u - unknown + +y - ISDN user part/BICC used all the way + +n - ISDN user part/BICC not used all the way + +Field-06: pref - ISDN user part/BICC preference indicator + +a definition + +- - - - - + +u - unknown + +n - ISDN user part/BICC not required all the way + +1 - ISDN user part/BICC preferred all the way + +2 - ISDN user part/BICC required all the way + +Field-07: acc - ISDN access indicator + +a definition + +- - - - - + +u - unknown + +y - Originating access ISDN + +n - Originating Access not ISDN + +Field-08: sccpm - SCCP method indicator + +a definition + +- - - - - + +0 - no information + +1 - connectionless method available (national use) (ISUP)/reserved (BICC) + +2 - connection oriented method available (ISUP)/reserved (BICC) + +3 - connectionless and connection oriented methods available (national use) (ISUP)/reserved (BICC) + +NOTE 1 - For interworking the collect call indicator has been superseded by use of the parameter COL. + +NOTE 2 - Ported out of rate center and local service provider portability now moved to parameter NPF. + +### 7.3.40 Forward Global Virtual Network Services (FVN) + +Format: FVN,type=aaa, [Field Container] + +This parameter can appear multiple times in one message indicating different types of information. + +Fields: + +Field-01: type + +aaa description + +--- - - - - - + +osp - Originating Participating Service provider Field container 1 + +cug - GVNS User Group CUG Field container 2 + +trn - Terminating Network Routing Number Field container 3 + +Field container 1 + +Format: osp=1\*d + +Field-02: osp - originating participating service provider + +1\*d description + +--- - - - - - + +1\*d - 1 or more digits (0-9) representing the OSPP + +Field container 2 + +Format: cug=1\*d + +Field-02: cug - GVNS User Group CUG + +1\*d description + +--- - - - - - + +1\*d - 1 or more digits (0-9) representing GVNS User Group CUG + +Field container 3 + +Format: noa=dd,npi=a,trn=1\*d + +Field-02: noa - nature of address + +dd description + +-- ----- + +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-03: npi - numbering plan indicator + +a description + +- ----- + +u - unknown + +1 - ISDN numbering plan (ITU-T Rec. E.164) + +2 - Data numbering plan (ITU-T Rec. X.121) + +3 - Telex numbering plan (ITU-T Rec. F.69) + +4 - Private numbering plan + +5 - national + +Field-04: trn - terminating network routing number + +1\*d description + +--- ----- + +1\*d - 1 or more digits (0-9) representing GVNS User Group CUG + +### 7.3.41 Generic Number/Address (GEA) + +Format: GEA,type=aaaa,noa=dd,npi=a,cni=a,pi=a,si=a,#=1\*h + +Based on the value of type the following parameters will follow. + +Fields: + +Field-01: type - type of address (number qualifier indicator) + +aaaa definition + +---- ----- + +dest - destination number/additional called number + +diad - dialed number + +rsrv - reserved (used in 1993 Q.761) + +sufs - supplemental user provided calling address - failed network screening + +suns - supplemental user provided calling address - not screened + +trs1 - redirecting terminating number + +trs2 - additional connected number + +trs3 - additional calling party number + +trs4 - additional original called number + +trs5 - additional redirecting number + +trs6 - additional redirection number + +Field-02: noa - nature of address + +dd description + +-- ----- + +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-03: npi - numbering plan indicator + +a description + +- ----- + +u - unknown + +1 - ISDN numbering plan (ITU-T Rec. E.164) + +2 - Data numbering plan (ITU-T Rec. X.121) + +3 - Telex numbering plan (ITU-T Rec. F.69) + +4 - Private numbering plan + +5 - national + +Field-04: cni - complete number indicator + a description + - ----- + u - unknown + y - number complete + n - number incomplete + +Field-05: pi - address presentation indicator + a description + - ----- + u - unknown + y - presentation allowed + n - presentation restricted + 0 - address not available + +Field-06: si - screening indicator + a description + - ----- + u - unknown or not applicable + 1 - user provided not screened (verified) + 2 - user provided screening passed + 3 - user provided screening failed + 4 - network provided + +Field-07: # - address + 1\*h description + --- ----- + 1\*h - one or more telephony digits: 0-9, A-F + (see formal grammar) + +### 7.3.42 Generic Digits (GED) + +Format: GED,tod=d,es=d,#=1\*h + +Fields: + +Field-01: tod - type of digits + d definition + - ----- + 0 - account code + 1 - authorization code + 2 - private network traveling class mark + 5 - business communication group identity + +Field-02: es - Encoding scheme + d description + - ----- + 0 - BCD even + 1 - BCD odd + 2 - IA5 + 3 - binary + +NOTE - Because ISUP IA5 and binary digits may contain non-zero most significant bit, each ISUP character must be represented as 2 hexadecimal characters (0-9, A-F) in NSS. + +Field-03: # - digits + 1\*h description + --- ----- + 1\*h - one or more telephony digits: 0-9, A-F + (see formal grammar) + +### 7.3.43 Generic Notification Indicator (GNO) + +Format: GNO,ni=dd + +Fields: + +Field-01: ni - notification indicator + +dd description + +-- ----- + +00 - user suspended + +01 - user resumed + +02 - bearer service change + +03 - discriminator for extension to ASN.1 encoded component + +04 - call completion delay + +05 - conference call established + +06 - conference call disconnected + +07 - other party added + +08 - isolated + +09 - reattached + +10 - other party isolated + +11 - other party reattached + +12 - other party split + +13 - other party disconnected + +14 - conference floating + +15 - call is a waiting call + +16 - diversion activated + +17 - call transfer, alerting + +18 - call transfer, active + +19 - remote hold + +20 - remote retrieval + +21 - call is diverting + +99 - unknown + +### 7.3.44 Global Call Identification (GCI) + +The Global Call ID field is a system-wide unique identifier for a Call. The Global Call ID may be passed in all NSS messages associated with a given call to aid in correlation. + +Format: GCI,gci=1\*a + +Fields: + +Field-01: gci - global Call ID + +1\*a definition + +--- ----- + +IA5 - IA5 printable characters. See Annex A for specific encoding details. See Appendix I for suggested implementation details. + +### 7.3.45 Hard To Reach (HTR) + +HTR,noa=dd,npi=d,#=1\*h + +Fields: + +Field-01: noa - nature of address + +dd description + +-- ----- + +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +``` + +Field-02: npi - numbering plan indicator +d description +- ----- +0 - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +Field-03: # - digits +1*h description +--- ----- +1*h - one or more telephony digits: 0-9, A-F + (see formal grammar) + +``` + +### 7.3.46 Hop Counter (HOC) + +Format: HOC, hc=dd + +Fields: + +``` + +Field-01: hc - Hop Counter +dd definition +-- ----- +00 - zero +-31 positive integer 0-31 + +``` + +### 7.3.47 Information Indicators (INI) + +Format: INI, inf=a, resp=a, sol=a + +Fields: + +``` + +Field-01: inf - information requested +a definition +- ----- +1 - calling party number +2 - hold provided indicator +3 - calling party category +4 - charge information +5 - malicious call ID + +Field-02: resp - information response +a definition +- ----- +i - information included +x - information not available +n - information not included + +Field-03: sol - solicited +a definition +- ----- +u - unknown +y - solicited information +n - un-solicited information + +``` + +[NOTE – This parameter can appear multiple times in an NSS message.] + +### 7.3.48 Information Request Indicators (IRI) + +Format: IRI,inf=a + +Fields: + +Field-01: inf - information requested +a definition +- - - - - +1 - calling party number +2 - holding indicator +3 - calling party category +4 - charge information +5 - malicious call ID + +[NOTE - This parameter can appear multiple times in an NSS message.] + +### 7.3.49 IN Service Compatibility (INC) + +Format: INC,dat=1\*(2Hex) + +Fields: + +Field-01: dat - IN Service Compatibility Indication parameter +defined by ITU-T Rec. Q.1228 +1\*(2h) description +- - - - - +1\*(2h) - one or more *pairs of characters (0-9, A-F)* representing a +hexadecimal encoding (see clause 5.1). +(If unknown, parameter is omitted.) + +### 7.3.50 Inter-nodal Traffic Group Identifier (ITG) + +Format: ITG,dat=1\*(2Hex) + +Fields: + +Field-01: dat - ASCII equivalent of binary value representing +the traffic group for the call +1\*(2h) description +- - - - - +1\*(2h) - one or more *pairs of characters (0-9, A-F)* representing a +hexadecimal encoding (see clause 5.1). +(If unknown, parameter is omitted.) + +### 7.3.51 Known Field Compatibility Information (FDC) + +This field is used in order to allow network-specific values of known fields to be transmitted even though the actual field is populated with a best-fit mapping. + +All parameters declared in this Recommendation have individual fields numbered. For any field which requires a value not declared in this Recommendation, the encoding application should map the value to a best-fit declared value in the actual field and include a known field compatibility parameter containing the actual value. This should be passed transparently through intermediate nodes which do not understand NSS. This parameter can appear multiple times. + +Format: FDC,parm=aaa, fname=aaaaa, instr=a, dat=1\*(2Hex) + +Fields: + +Field-01 : parm - parameter name + +aaa definition + +--- ----- + +aaa - 3 ascii characters as defined at the beginning of clause 7.2 +for NSS parameter names + +Field-02 : fname - field name - refers to the field name declared +against the parameter in this Recommendation + +aaaaa definition + +----- + +aaaaa - five-character maximum lower-case alphabetic field name +(See Appendix II grammar for nss\_field\_name.) + +Field-03 : instr - instruction + +a definition + +- ----- + +u - unknown + +1 - release call if not understood, regardless of the ability to +forward + +2 - use the default value if not understood regardless of the +ability to forward, no notification required, but continue call + +3 - use the default value if not understood regardless of the +ability to forward, send notification (in Confusion) but +continue call + +4 - Attempt to forward value; if unable to forward the value release +the call + +5 - Attempt to forward value; if unable to forward the value use +default value without notification but continue the call + +6 - Attempt to forward value; if unable to forward the value use +default value and send notification but continue the call + +Field-04: dat - hexadecimal representation of the field value +contents + +1\*(2h) description + +----- + +1\*(2h) - one or more pairs of characters (0-9, A-F) representing a +hexadecimal encoding (see clause 5.1). + +### 7.3.52 Location Number (LON) + +Format: LON, noa=dd, inn=a, npi=a, pi=a, si=a, #=1\*h + +Fields: + +Field-01: noa - nature of address + +dd description + +-- ----- + +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-02: inn - Internal network number indicator + +a description + +- ----- + +u - unknown + +n - routing to internal network number not allowed + +y - routing to internal network number allowed + +``` + +Field-03: npi - numbering plan indicator +a description +- ----- +u - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +Field-04: pi - presentation indicator +a description +- ----- +u - unknown +y - presentation allowed +n - presentation restricted +0 - address not available + +Field-05: si - screening indicator +a description +- ----- +u - unknown +1 - user provided not screened +2 - user provided screening passed +3 - user provided screening failed +4 - network provided + +Field-06: # - address +1*h description +--- ----- +1*h - one or more telephony digits: 0-9, A-F + (see formal grammar) + +``` + +### 7.3.53 Loop Prevention Indicator (LPI) + +Format: LPI,req=d,lpi=a + +Fields: + +``` + +Field-01 : req - request indicator +d definition +- ----- +0 - request +1 - response + +Field-02 : lpi - loop indicator +a definition +- ----- +u - unknown (insufficient information) +1 - no loop exists +2 - loop detected (simultaneous transfer) + +``` + +### 7.3.54 Mapped Parameter List (MPL) + +Format: MPL,plist=(aaa,aaa,...) + +Fields: + +``` + +Field-01: plist - parameter list +aaa description +--- ----- +aaa - Comma-separated list of one or more parameter codes bounded + by parentheses, e.g., MPL,plist=(GEN,GED,OCN,RNI). Commas + are used only when two or more parameter codes are present. + Parentheses are always present. (See ABNF in Annex A.) + +``` + +### 7.3.55 MCID Request Indicator (MRI) + +Format: MRI,ri=a,hi=a + +Fields: + +Field-01 : ri - request indicator + +a definition + +- ----- + +u - unknown + +n - MCID not requested + +y - MCID requested + +Field-02 : hi - holding indicator + +a definition + +- ----- + +u - unknown + +n - Holding not requested + +y - Holding requested + +### 7.3.56 MCID Response Indicator (MCR) + +Format: MCR,rp=a,hp=a + +Fields: + +Field-01 : rp - response indicator + +a definition + +- ----- + +u - unknown + +n - MCID not included + +y - MCID included + +Field-02 : hp - hold provided indicator + +a definition + +- ----- + +u - unknown + +n - Holding not provided + +y - Holding provided + +### 7.3.57 Message Compatibility Information (MCI) + +This parameter is usually expected to be associated with a UNR message. This parameter gives explicit information to the next node on how to proceed when an unrecognized message is forwarded. + +Format: MCI,instr=a,tri=d,dat=1\*(2Hex) + +Fields: + +Field-01: instr - instruction + +a definition + +- ----- + +u - unknown + +1 - release Call regardless of the ability to forward the message + +2 - discard message regardless of the ability to forward the message, no notification required, but continue call + +3 - discard message regardless of the ability to forward the message, send notification (in Confusion) but continue call + +4 - Attempt to forward message; if unable to forward the message, release the call + +5 - Attempt to forward message; if unable to forward the message, discard message without notification but continue the call + +6 - Attempt to forward message; if unable to forward the message, + +discard the message send notification but continue the call + +Field-02 : tri - transit at intermediate exchange indicator + +d definition + +- - - - - + +0 - no transit (end node interpretation) + +1 - yes transit + +Field-03: dat - encapsulation of unrecognized message + +1\*(2h) description + +- - - - - + +1\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). + +### 7.3.58 MLPP Precedence (MLP) + +Format: MLP, lfb=a, pl=a, ni=hhhh, sd=hhhhh + +Fields: + +Field-01: lfb - Look-ahead For Busy + +a definition + +- - - - - + +u - unknown + +y - lfb allowed + +n - lfb not allowed + +r - path reserved (national use) + +Field-02: pl - Precedence Level + +a definition + +- - - - - + +u - unknown + +0 - flash override + +1 - flash + +2 - immediate + +3 - priority + +4 - routine + +Field-03: ni - Network ID + +hhhh definition + +- - - - - + +0000 - unknown + +-9999 - 4 hex digits 0-9 + +Field-04: sd - MLPP service domain + +hhhhh definition + +- - - - - + +000000 - unknown + +-FFFFFF - 6 hex digits 0-9 or A-F + +### 7.3.59 Nature Of Connection Indicator (NOC) + +Format: NOC, sat=d, eco=a, cot=d + +Fields: + +Field-01: sat - satellite indicator + +d definition + +- - - - - + +u - unknown + +0 - no satellite in connection + +1 - one satellite in connection + +2 - two satellites in connection + +Field-02: eco - echo control device indicator + +a definition + +- - - - - + +u - unknown + +n - echo device not included + +y - echo device included + +Field-03: cot - continuity indicator + +d definition + +- - - - - + +0 - not applicable + +1 - continuity check not required/no COT to be expected (BICC) + +2 - continuity check required on this circuit (NOTE - COT may not be applicable across a packet-based network. If not applicable, then this value must not be used.) + +3 - continuity check performed on a previous circuit/COT to be expected (BICC) + +### 7.3.60 Network Management Controls (NMC) + +Format: NMC,tari=a + +Fields: + +Field-01 : tari - temporary alternative routing indicator + +a definition + +- - - - - + +0 - no indication + +y - TAR controlled call + +### 7.3.61 Network Routing Number (NRN) + +Format: NRN,npi=a,noa=d,#=1\*h + +Fields: + +Field-01: npi - numbering plan indicator + +a description + +- - - - - + +u - unknown + +1 - ISDN numbering plan (ITU-T Rec. E.164) + +Field-02: noa - nature of address + +d description + +- - - - - + +0 - unknown + +1 - network routing number in national (significant) number format + +2 - network routing number in network specific number format + +Field-03: # - address + +1\*h description + +- - - - - + +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.62 Network Specific Facilities (NSF) + +Format: NSF, ton=a, nip=a, nid=1\* (2Hex) , nsf=1\* (2Hex) + +Fields: + +Field-01: ton - type of network identification + +a description + +- - - - - + +u - unknown + +c - ITU/CCITT (international network) + +n - national + +Field-02: nip - network identification plan + +a description + +- - - - - + +a - one IA5 character of 0-9, A-F, meaning determined by ton + +Field-03: nid - network identification + +1\* (2h) description + +- - - - - + +1\* (2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). + +Field-04: nsf - network-specific facility indicator + +1\* (2h) description + +- - - - - + +1\* (2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). + +### 7.3.63 Number Portability Forward Information (NPF) + +Format: NPF, nps=a + +Fields: + +Field-01: nps - number portability status indicator + +a definition + +- - - - - + +0 - no indication + +1 - number portability query not done for called number + +2 - number portability query done, non-ported called subscriber + +3 - number portability query done, ported called subscriber + +### 7.3.64 Optional Backward Call Indicators (OBI) + +Format: OBI, inb=a, cf=a, mlpp=a + +Fields: + +Field-01: inb - inband information Indicator + +a definition + +- - - - - + +0 - no indication + +y - in-band information or an appropriate pattern is now available + +n - in-band information or an appropriate pattern is not available + +Field-02: cf - call forwarding (diversion) may occur indicator + +a definition + +- - - - - + +0 - no indication + +y - call forwarding (diversion) may occur + +n - call forwarding (diversion) may not occur + +Field-03: mlpp - mlpp user Indicator +a definition +- ----- +0 - no indication +y - MLPP user +n - not an MLPP user + +NOTE - Segmentation is indicated by presence of SEG parameter. +For user-network interaction - see UID Indicators parameter - UID + +### 7.3.65 Optional Forward Call Indicators (OFI) + +Format: OFI,cug=a,cnn=a + +Fields: + +Field-01: cug - closed user group call indicator +a definition +- ----- +u - unknown +n - non-cug call +1 - closed user group call, outgoing access allowed +2 - closed user group call, outgoing access not allowed + +Field-02: cnn - connected line identity request Indicator +a definition +- ----- +u - unknown +y - connected line identity requested +n - connected line identity not requested + +NOTE - Segmentation is indicated by presence of SEG parameter. + +### 7.3.66 Original Called IN Number (OCI) + +Format: OCI,noa=dd,npi=a,pi=a,si=a,#=1\*h + +Fields: + +Field-01: noa - nature of address +dd description +-- ----- +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-02: npi - numbering plan indicator +a description +- ----- +u - unknown +1 - ISDN numbering plan (ITU-T Rec. E.164) +2 - Data numbering plan (ITU-T Rec. X.121) +3 - Telex numbering plan (ITU-T Rec. F.69) +4 - Private numbering plan +5 - national + +Field-03: pi - presentation indicator +a description +- ----- +u - unknown +y - presentation allowed +n - presentation restricted +0 - address not available + +Field-04: si - screening indicator + +| a | description | +|---|--------------------------------| +| u | unknown | +| 1 | user provided not screened | +| 2 | user provided screening passed | +| 3 | user provided screening failed | +| 4 | network provided | + +Field-05: # - address + +| 1*h | description | +|-----|----------------------------------------------------------------| +| 1*h | one or more telephony digits: 0-9, A-F
(see formal grammar) | + +### 7.3.67 Original Called Number (OCN) + +Format: OCN,noa=dd,npi=a,pi=a,#=1\*h + +[Fields are the same as in OCI directly above, omitting si field.] + +### 7.3.68 Originating ISC Point Code (ISC) + +Format: ISC,pc=aaaaaaaaa + +Fields: + +Field-01: pc - Point Code + +| aaaaaaaaa | description | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nnn.ccc.mmm | nine characters separated by two periods, where
nnn is for network/zone (most significant 3 or 8 bits),
ccc is for cluster/area (middle 8 bits),
mmm is for member (least significant 3 or 8 bits).
The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 representing the decimal equivalent of the subfield viewed as a binary number. [NOTE - ITU format is 3.8.3 bit.] | + +### 7.3.69 Parameter Compatibility Information(PCI) + +This parameter is used to transmit any unknown parameter across the network. This parameter includes instructions for the end node on how to proceed in the event of not being able to interpret the parameter. + +Format: PCI,instr=a,tri=d,dat=1\*(2Hex) + +Fields: + +Field-01: instr - instruction + +| a | definition | +|---|--------------------------------------------------------------------------------------------------------------------------| +| u | unknown | +| 0 | Release call regardless of the ability to forward the parameter | +| 1 | Discard message regardless of the ability to forward the parameter, no notification required, but continue call | +| 2 | Discard message regardless of the ability to forward the parameter, send notification (in Confusion), but continue call | +| 3 | Discard parameter regardless of the ability to forward the parameter, no notification required, but continue call | +| 4 | Discard parameter regardless of the ability to forward the parameter, send notification (in Confusion) but continue call | +| 5 | Attempt to forward the parameter; if unable to forward the | + +- parameter release the call +- 6 - Attempt to forward the parameter; if unable to forward the parameter discard message without notification but continue the call + - 7 - Attempt to forward the parameter; if unable to forward the parameter, discard message, send notification but continue the call + - 8 - Attempt to forward the parameter; if unable to forward the parameter, discard the parameter; without notification but continue the call + - 9 - Attempt to forward the parameter; if unable to forward the parameter discard the parameter; send notification but continue the call + +Field-02 : tri - transit at intermediate exchange indicator + +- d definition +- ----- +- 0 - no transit (end node interpretation) + - 1 - yes transit (transit node interpretation) + +Field-03: dat - representation of the parameter contents + +- 1\*(2h) description +- +- 1\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1) of the parameter. + +### 7.3.70 Pivot Capability (PCA) + +Format: PCA,ppi=a,iwri=a + +Fields: + +Field-01: ppi - pivot possible indicator + +- a definition +- ----- +- 0 - no indication + - 1 - pivot routing possible before ACM + - 2 - pivot routing possible before ANM + - 3 - pivot routing possible at any time during call + +Field-02: iwri - interworking to redirection indicator + +- a definition +- ----- +- u - unknown + - y - allowed + - n - not allowed + +### 7.3.71 Pivot Counter (PCT) + +Format: PCT,pct=dd + +Fields: + +Field-01: pct - pivot counter + +- dd definition +- ----- +- 00 - unknown or zero + - 31 - positive integer 0-31 + +### 7.3.72 Pivot Routing Backward Information (PBI) + +Format: PBI,tag=a,[Field Container] + +Fields: + +Field-01: tag - information type tag + +a description + +- - - - - + +u - unknown + +1 - return to invoking exchange information + +field container 1 + +2 - return to invoking exchange call identifier + +field container 2 + +3 - invoking pivot reason + +field container 3 + +Field containers: + +Field container 1 + +Format: dur=d + +Field-01: dur - duration + +ddddd description + +- - - - - + +00000 - number of seconds + +-65535 + +Field container 2 + +Format: cid=hhhhh,pc=aaaaaaaaaa + +Fields: + +Field-01: cid - call identity + +hhhhh description + +- - - - - + +00-ff - six characters representing hexadecimal values + +Field-02: pc - point code + +aaaaaaaaaa description + +- - - - - + +nnn.ccc.mmm - nine characters separated by two periods, where + +nnn is for network/zone (most significant 3 or 8 bits), + +ccc is for cluster/area (middle 8 bits), + +mmm is for member (least significant 3 or 8 bits). + +The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 representing the decimal equivalent of the subfield viewed as a binary number. [NOTE - ITU format is 3.8.3 bit.] + +Field container 3 + +Format: rea=ddd + +Field-01: rea - pivot reason + +ddd description + +- - - - - + +000 - unknown/not available + +001 - service provider portability + +002 - location portability + +003 - service portability + +### 7.3.73 Pivot Routing Forward Information (PFI) + +Format: PFI,tag=a,[Field Container] + +Fields: + +Field-01: tag - information type tag + +a description + +- - - - - + +u - unknown + +1 - return to invoking exchange possible + +2 - return to invoking exchange call identifier field container 1 + +3 - performing pivot indicator field container 2 + +4 - invoking pivot reason field container 3 + +Field containers: + +Field container 1 + +Format: cid=hhhhhh,pc=aaaaaaaaa + +Fields: + +Field-01: cid - Call identity + +hhhhhh description + +- - - - - + +00-ff - six characters representing hexadecimal values + +Field-02: pc - Point Code + +aaaaaaaaa description + +- - - - - + +nnn.ccc.mmm - nine characters separated by two periods, where +nnn is for network/zone (most significant 3 or 8 bits), +ccc is for cluster/area (middle 8 bits), +mmm is for member (least significant 3 or 8 bits). +The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 +representing the decimal equivalent of the subfield viewed +as a binary number. [NOTE - ITU format is 3.8.3 bit.] + +Field container 2 + +Format: ppr=ddd,ppi=a + +Field-01: ppr - performing pivot reason + +ddd description + +- - - - - + +000 - unknown/not available + +001 - service provider portability + +002 - location portability + +003 - service portability + +Field-02: ppi - pivot possible indicator + +a definition + +- - - - - + +0 - no indication + +1 - pivot routing possible before ACM + +2 - pivot routing possible before ANM + +3 - pivot possible at any time during call + +Field container 3 + +Format: rea=ddd + +``` + +Field-01: rea - pivot reason +ddd description +--- - +000 - unknown/not available +001 - service provider portability +002 - location portability +003 - service portability + +``` + +### 7.3.74 Pivot Routing Indicator (PVR) + +Format: PVR,pvr=a + +Fields: + +``` + +Field-01: pvr - pivot routing indicator +a definition +- - +0 - no indication +1 - pivot request +2 - cancel pivot request +3 - pivot request failure +4 - interworking to redirection prohibited + +``` + +### 7.3.75 Pivot Status (PVS) + +Format: PVS,psi=a + +Fields: + +``` + +Field-01: psi - pivot status indicator +a definition +- - +0 - no indication +1 - acknowledgement of pivot routing +2 - pivot routing will not be invoked + +``` + +### 7.3.76 Propagation Delay Counter (PDC) + +Format: PDC,pd=ddddd + +Fields: + +``` + +Field1 : pd - propagation delay + +ddddd definition +----- +00000 - delay in milliseconds +-65535 + +``` + +### 7.3.77 Protocol Name (PRN) + +This parameter shall be populated by the node that first constructs the NSS encoding. This parameter shall appear in the first forward and first backward messages as a minimum. + +Format: PRN,prot=aaaaa + +Fields: + +``` + +Field-01: prot - Protocol base derivative +aaaaa - 5 char String indicating base variant derivative +----- +uknow - unknown +q761* - ITU-T Recs Q.761-Q.764 +q1902 - ITU-T Rec. Q.1902.3 + +``` + +### 7.3.78 Query On Release Capability (QOR) + +Format: QOR,qci=a + +Fields: + +Field-01: qci - query on release capability indicator +a definition +- ----- +0 - no indication +y - QOR support + +### 7.3.79 Redirect Backward Information (RBI) + +Format: RBI,tag=a,[Field Container] + +Fields: + +Field-01: tag - information type tag +a description +- ----- +u - unknown +1 - return to invoking exchange information field container 1 +2 - return to invoking exchange call identifier field container 2 +3 - invoking redirect reason field container 3 + +Field containers: + +Field container 1 + +Format: dur=d + +Field-01: dur - duration +ddddd description +----- +00000 - unknown +-65535 number of seconds + +Field container 2 + +Format: cid=hhhhhh,pc=aaaaaaaaaa + +Fields: + +Field-01: cid - call identity +hhhhhh description +----- +000000 - six characters representing hexadecimal values +-FFFFFF + +Field-02: pc - point code +aaaaaaaaaa description +----- +nnn.ccc.mmm - nine characters separated by two periods, where +nnn is for network/zone (most significant 3 or 8 bits), +ccc is for cluster/area (middle 8 bits), +mmm is for member (least significant 3 or 8 bits). +The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 +representing the decimal equivalent of the subfield viewed +as a binary number. [NOTE - ITU format is 3.8.3 bit.] + +Field container 3 + +Format: rea=ddd + +Field-01: rea - redirect reason +ddd description +--- +000 - unknown/not available +001 - service provider portability +002 - location portability +003 - service portability + +### 7.3.80 Redirect Capability (RDC) + +Format: RDC,rc=a + +Fields: + +Field-01: rc - redirect capability +a definition +- +0 - no indication +1 - redirection possible before ACM +2 - redirection possible before ANM +3 - redirection possible at any time during the call + +### 7.3.81 Redirect Counter (RCT) + +Format: RCT,rc=dd + +Fields: + +Field-01: rc - redirect counter +dd definition +-- +00 - zero redirections known to application (unknown) +-31 - 1-31 positive integer indicating number of redirections + +### 7.3.82 Redirect Forward Information (RFI) + +Format: RFI,tag=a,[Field Container] + +Fields: + +Field-01: tag - information type tag +a description +- +u - unknown +1 - return to invoking exchange possible +2 - return to invoking exchange call identifier field container 1 +3 - perform redirect indicator field container 2 +4 - invoking redirect reason field container 3 + +Field containers: + +Field container 1 + +Format: cid=hhhhhh,pc=aaaaaaaaa + +Fields: + +Field-01: cid - call identity +hhhhhh description +----- +00-ff - six characters representing hexadecimal values + +Field-02: pc - point code +aaaaaaaaaa description +----- +nnn.ccc.mmm - nine characters separated by two periods, where +nnn is for network/zone (most significant 3 or 8 bits), +ccc is for cluster/area (middle 8 bits), +mmm is for member (least significant 3 or 8 bits). +The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 +representing the decimal equivalent of the subfield viewed +as a binary number. [NOTE - ITU format is 3.8.3 bit.] + +Field container 2 + +Format: prr=ddd,rpi=d + +Field-01: prr - performing redirect reason +ddd description +--- +000 - unknown/not available +001 - service provider portability +002 - location portability +003 - service portability + +Field-02: rpi - redirect possible indicator +a definition +- +0 - no indication +1 - redirection possible before ACM +2 - redirection possible before ANM +3 - redirection possible at any time during call + +Field container 3 + +Format: rea=ddd + +Field-01: rea - redirect reason +ddd description +--- +000 - unknown/not available +001 - service provider portability +002 - location portability +003 - service portability + +### 7.3.83 Redirect Status (RDS) + +Format: RDS,rpi=a + +Fields: + +Field-01: rpi - redirect possible indicator +a definition +- +0 - no indication +1 - acknowledgement of redirection +2 - redirection will not be invoked + +### 7.3.84 Redirecting Number (RGN) + +Format: RGN,noa=dd,npi=a,pi=a,#=1\*h + +Fields: + +Field-01: noa - nature of address + +dd description + +-- - - - - - - - - - - + +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-02: npi - numbering plan indicator + +a description + +- - - - - - - - - - - + +u - unknown + +1 - ISDN numbering plan (ITU-T Rec. E.164) + +2 - Data numbering plan (ITU-T Rec. X.121) + +3 - Telex numbering plan (ITU-T Rec. F.69) + +4 - Private numbering plan + +5 - national + +Field-03: pi - presentation indicator + +a description + +- - - - - - - - - - - + +u - unknown + +y - presentation allowed + +n - presentation restricted + +0 - address not available + +Field-04: # - address + +1\*h description + +--- - - - - - - - - - - + +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.85 Redirection Information (RNI) + +Format: RNI,ri=d,orr=a,rc=dd,rr=a + +Fields: + +Field-01: ri - Redirecting Indicator + +d definition + +- - - - - - - - - - - + +0 - no redirection + +1 - call rerouted + +2 - call rerouted, all redirection info presentation restricted + +3 - call diverted + +4 - call diverted, all redirection information presentation +restricted + +5 - call rerouted, redirection number presentation restricted + +6 - call diversion, redirection number presentation restricted + +Field-02: orr - original redirection Reason + +a definition + +- - - - - - - - - - - + +u - unknown/not available + +1 - user busy + +2 - no reply + +3 - unconditional + +4 - deflection during alerting + +5 - deflection immediate response + +6 - mobile subscriber not reachable + +Field-03: rc - redirection counter +dd definition +-- +00 - zero redirections known to application (unknown) +-31 - 1-31 positive integer indicating number of redirections + +Field-04: rr - redirection reason +a definition +- +u - unknown/not available +1 - user busy +2 - no reply +3 - unconditional +4 - deflection during alerting +5 - deflection immediate response +6 - mobile subscriber not reachable + +### 7.3.86 Redirection Number (RNN) + +Format: RNN, noa=dd, inn=a, npi=a, #=1\*h + +Fields: (redirected-to number) + +Field-01: noa - nature of address + +dd description +-- + +See definition of "noa=" in clause 7.3.13, +Call Transfer Number (CTN). + +Field-02: inn - Internal network number indicator + +a description +- + +u - unknown + +n - routing to internal network number not allowed + +y - routing to internal network number allowed + +Field-03: npi - numbering plan indicator + +a description +- + +u - unknown + +1 - ISDN numbering plan (ITU-T Rec. E.164) + +2 - Data numbering plan (ITU-T Rec. X.121) + +3 - Telex numbering plan (ITU-T Rec. F.69) + +4 - Private numbering plan + +5 - national + +Field-04: # - address + +1\*h description +--- + +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.87 Redirection Number Restriction (RNR) + +Format: RNR, rnr=a + +Fields: + +Field-01: rnr - redirection number restriction + +a definition +- + +u - unknown + +y - presentation allowed + +n - presentation restricted + +### 7.3.88 Remote Operations (RMO) + +Format: RMO, pp=a, dat=1\*(2Hex) + +Fields: + +Field-01: pp - protocol profile +a description +- - - - - +u - unknown +1 - remote operations protocol + +Field-02: dat - representation of the parameter contents +1\*(2h) description +- - - - - +1\*(2h) - one or more *pairs of characters (0-9, A-F)* representing a hexadecimal encoding (see clause 5.1) of the parameter. +[Follows Q.700 description method based on X.690 encoding rules or uses X.680 ASN.1 encoding of this parameter. +Components are based on ROSE ITU-T Rec. X.880. +See 6.90/Q.1902.3, for more details. +This element is viewed as a tunneled opaque object.] + +### 7.3.89 SCF ID (SCF) + +Format: SCF, scf=1\*(2Hex) + +Fields: + +Field-01: scf - SCF id +1\*(2h) description +- - - - - +1\*(2h) - one or more *pairs of characters (0-9, A-F)* representing a hexadecimal encoding (see clause 5.1) of the parameter. + +### 7.3.90 Segmentation indicator (SEG) + +This parameter indicates that more information related to this message will follow in a subsequent SGM message. The SEG parameter is not tied to a maximum or minimum message length. SEG in a NSS body part can only be used to indicate segmentation of the messages used in a NSS body part. + +Format: SEG, + +Fields: No fields + +### 7.3.91 Service Activation (SEA) + +Format: SEA, fci=dd + +Fields: + +Field-01: fci - feature code indicator (omit parameter if unknown) +dd description +- - - - - +20 - call transfer + +### 7.3.92 Signalling Point Code (SPC) + +Format: SPC,pc=aaaaaaaaaa + +Fields: + +Field-01: pc - point code +aaaaaaaaaa description +----- +nnn.ccc.mmm - nine characters separated by two periods, where +nnn is for network/zone (most significant 3 or 8 bits), +ccc is for cluster/area (middle 8 bits), +mmm is for member (least significant 3 or 8 bits). +The nnn, ccc, and mmm are 3-digit numbers from 000 to 255 +representing the decimal equivalent of the subfield viewed +as a binary number. [NOTE - ITU format is 3.8.3 bit.] + +### 7.3.93 Source Parameter Information (SPI) + +Format: SPI,mparm=aaa,sparm=hhh + +Fields: + +Field-01: mparm - mapped-to parameter +aaa description +--- +aaa - Three-letter NSS parameter name, e.g., DIS for Display. + +Field-02: sparm - source parameter +hhh description +--- +0-9 - Three ASCII characters representing hex digits that +A-F identify the Source Parameter ID. For example, 07E +means User-to-User IE was 1 of N possible source +parameters. PRN provides context for this value. + +### 7.3.94 Subsequent Number (SUN) + +Format: SUN,#=1\*h + +Fields: + +Field-01: # - address +1\*h description +--- +1\*h - one or more telephony digits: 0-9, A-F +(see formal grammar) + +### 7.3.95 Suspend/Resume Indicators (SRI) + +Format: SRI,sri=a + +Fields: + +Field-01: sri - suspend/resume indicator +a definition +- +u - unknown +s - ISDN subscriber initiated +n - network initiated + +### 7.3.96 Transaction Identifier (TID) + +This parameter is used as a unique identifier for a message. It is the responsibility of the first NSS entry point from the PSTN (typically an access server) to construct this parameter and for all intermediate nodes to pass this on transparently or construct one if not present. Once created, TID must not be modified by subsequent nodes. This is used for message event correlation across switching nodes but does not require call state history to be maintained to generate this parameter. The distinction between TID and GCI is that TID typically involves tracing the message only, whereas the GCI may span multiple messages and multiple call legs. + +Format: TID, tid=1\*a + +Fields: + +Field-01: tid - global call ID + +1\*a definition + +--- ----- + +IA5 - IA5 printable characters. See Annex A for specific encoding details. See Appendix I for suggested implementation details. + +### 7.3.97 Transit Network Selection (TNS) + +Format: TNS, ton=a, nip=a, tns=1\*a + +Fields: + +Field-01: ton - type of network + +a definition + +- ----- + +u - unknown + +c - ITU/CCITT + +n - national + +Field-02: nip - network identification plan + +a definition + +- ----- + +u - unknown + +1 - public data network identification code +(DNIC - ITU-T Rec. X.121) + +2 - public land mobile network identification code +(MNIC - ITU-T Rec. E.212) + +[NOTE - Need to use FDC to carry nip= for national plans.] + +Field-03: tns - network identification + +1\*a definition + +--- ----- + +IA5 - characters of 0-9, A-F of length defined by ton and nip + +### 7.3.98 Transmission Medium Required (TMR) + +Format: TMR, tmr=dd + +Fields: + +Field-01: tmr - transmission medium required +(omit parameter if unknown) + +dd definition + +-- ----- + +``` + +00 - speech +01 - 3.1 kHz audio +02 - 7 kbit/s audio/video +03 - 64 kbit/s preferred +04 - 1 x 64 kbit/s unrestricted +05 - 2 x 64 kbit/s unrestricted +06 - 3 x 64 kbit/s unrestricted +07 - 4 x 64 kbit/s unrestricted +08 - 5 x 64 kbit/s unrestricted +09 - 6 x 64 kbit/s unrestricted (384 kbit/s) +10 - 7 x 64 kbit/s unrestricted +11 - 8 x 64 kbit/s unrestricted +12 - 9 x 64 kbit/s unrestricted +13 - 10 x 64 kbit/s unrestricted +14 - 11 x 64 kbit/s unrestricted +15 - 12 x 64 kbit/s unrestricted +16 - 13 x 64 kbit/s unrestricted +17 - 14 x 64 kbit/s unrestricted +18 - 15 x 64 kbit/s unrestricted +19 - 16 x 64 kbit/s unrestricted +20 - 17 x 64 kbit/s unrestricted +21 - 18 x 64 kbit/s unrestricted +22 - 19 x 64 kbit/s unrestricted +23 - 20 x 64 kbit/s unrestricted +24 - 21 x 64 kbit/s unrestricted +25 - 22 x 64 kbit/s unrestricted +26 - 23 x 64 kbit/s unrestricted +27 - 24 x 64 kbit/s unrestricted (1536 kbit/s) +28 - 25 x 64 kbit/s unrestricted +29 - 26 x 64 kbit/s unrestricted +30 - 27 x 64 kbit/s unrestricted +31 - 28 x 64 kbit/s unrestricted +32 - 29 x 64 kbit/s unrestricted +33 - 30 x 64 kbit/s unrestricted (1920 kbit/s) + +``` + +### 7.3.99 Transmission Medium Required Prime (TMP) + +Format: TMP,tmr=dd + +Fields: + +Field-01: tmr - transmission medium required + (omit parameter if unknown) + +``` + +dd definition +-- ----- + +``` + +See definition of tmr field in TMR parameter above. + +### 7.3.100 Transmission Medium Used (TMU) + +Format: TMU,tmr=dd + +Fields: + +Field-01: tmr - transmission medium required + (omit parameter if unknown) + +``` + +dd definition +-- ----- + +``` + +See definition of tmr field in TMR parameter above. + +#### 7.3.101 UID Action Indicators (UID) + +Format: UID,tc=a,t9=a + +Fields: + +Field-01: tc - through connection instruction indicator + +a definition + +- ----- + +0 - no indication + +y - through connect in both directions + +Field-02: t9 - T9 timer instruction + +a definition + +- ----- + +0 - no indication + +y - stop or do not start T9 timer + +#### 7.3.102 UID Capability Indicators (UCI) + +Format: UCI,tc=a,t9=a + +Fields: + +Field-01: tc - through connection indicator + +a definition + +- ----- + +0 - no indication + +y - through connection modification possible + +n - through connection modification not possible + +Field-02: t9 - T9 timer instruction + +a definition + +- ----- + +0 - no indication + +y - stopping of T9 timer possible + +n - stopping of T9 timer not possible + +#### 7.3.103 Unknown Field Compatibility Information (UFC) + +This field is used in order to allow network-specific fields not declared in this Recommendation to be transmitted even though the actual field does not exist in the Recommendation. The parameter includes the parameter name in which the field appears, and a free format description and value area. This will only be able to be interpreted by the end point if the protocol name and potentially protocol version match there is a high probability that the unrecognized values will be understood. + +This parameter can appear multiple times. + +Format: UFC,parm=aaa,instr=d,fname=aaaaa,dat=1\*(2Hex) + +Fields: + +Field-01: parm - parameter name where field is to be found + +aaa definition + +--- ----- + +aaa - 3 ASCII characters of a-z denoting NSS parameter name + +Field-02: instr - instruction on how to proceed + +d definition + +- ----- + +1 - release call if not understood, regardless of the ability to + +- forward +- 2 - use the default value if not understood, regardless of the ability to forward, no notification required, but continue call +- 3 - use the default value if not understood regardless of the ability to forward, send notification (in Confusion) but continue call +- 4 - Attempt to forward value; if unable to forward the value release the call +- 5 - Attempt to forward value; if unable to forward the value use default value without notification but continue the call +- 6 - Attempt to forward value; if unable to forward the value use default value and send notification but continue the call + +Field-03: fname - field name + +aaaaa definition + +----- + +aaaaa - 5 ASCII characters that describe the field +(See Appendix II grammar for nss\_field\_name) + +Field-04: dat - Value of field + +1\*(2h) description + +----- + +1\*(2h) - one or more pairs of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1) of the field value. + +#### 7.3.104 User Service Information (USI) + +Format: USI,type=aaaa,[field container] + +Based on the value of "type", one of the following field containers will follow. This parameter can appear multiple times, indicating different types of information with the same message. + +Fields: + +Field-01: type - type of User Service information + +aaaa definition + +----- + +| | | +|-------------------------------------------|--------------------| +| rate - bearer rate information | field container 1 | +| sup1 - supplementary information 1 | field container 2 | +| symm - symmetry supplementary information | field container 3 | +| mult - rate multiplier | field container 4 | +| lay1 - layer 1 supplementary information | field container 5 | +| subr - subrate supplementary information | field container 6 | +| v110 - v110 supplementary information | field container 7 | +| v120 - v120 supplementary information | field container 8 | +| pari - parity supplementary information | field container 9 | +| modm - modem supplementary information | field container 10 | +| lay2 - layer 2 supplementary information | field container 11 | +| lay3 - layer 3 supplementary information | field container 12 | + +Field Containers: + +Field Container 1 (type=rate) + +Format: cs=a,cap=a,mode=a,rate=d + +Fields: + +Field-02: cs - coding standard + +a definition + +----- + +u - unknown + +c - ITU-T standardized coding + +i - ISO/IEC standard +n - national standard +p - standard defined for the network either public or private + +##### Field-03: cap - Information transfer capability + +a definition +- ----- +u - unknown +s - speech +d - unrestricted digital information +r - restricted digital information +3 - 3.1 kbit/s audio +7 - 7 kbit/s audio +v - video + +##### Field-04: mode - transfer mode + +a definition +- ----- +u - unknown +c - circuit mode +p - packet mode + +##### Field-05: rate - Information transfer rate + +d definition +- ----- +0 - not applicable (used for packet calls) +1 - 64 kbit/s +2 - 384 kbit/s +3 - 1472 kbit/s +4 - 1536 kbit/s +5 - 1920 kbit/s +6 - multirate (64 kbit/s base rate) +7 - 2 x 64 kbit/s + +##### Field Container 2 (type = sup1) + +Format: str=d,estab=d,conf=d + +##### Field-02: str - structure + +d definition +- ----- +0 - default or unknown +1 - 8 kHz integrity +2 - service data unit integrity +3 - unstructured + +##### Field-03: estab - establishment + +d definition +- ----- +u - unknown +d - demand + +##### Field-04: conf - configuration + +d definition +- ----- +u - unknown +p - point-to-point + +##### Field Container 3 (type = symm) + +Format: sym=aa,rate=d + +Field-02: sym - symmetry +aa definition + +-- +uu - unknown +sb - symmetric bidirectional + +Field-03: rate - information transfer rate in the backwards direction + +d definition +- +0 - not applicable (used for packet calls) +1 - 64 kbit/s +2 - 384 kbit/s +3 - 1472 kbit/s +4 - 1536 kbit/s +5 - 1920 kbit/s +6 - multirate (64 kbit/s base rate) +7 - 2 x 64 kbit/s + +Field Container 4 (type = mult) + +Format: mult=dd + +Field-02: mult - rate multiplier + +dd definition +-- +00 - unknown +02 - values 2 to the maximum number of B-channels +-99 - available on the interface + +Field Container 5 (type = lay1) Layer 1 Protocol + +Format: lay1=aaaa + +Field-02: lay1 - Layer 1 protocol + +aaaa definition +---- +uuuu - unknown +v110 - ITU-T standardized rate adaptation V.110/X.30. +ulaw - G.711 u-law +alaw - G.711 a-law +g721 - G.721 32 kbit/s ADPCM and ITU-T Rec. I.460 +g722 - G.722 and G.725/G.724 7 kHz audio +h221 - H.221 and H.242 +nonc - non-ITU-T rate adaptation +v120 - ITU-T standardized rate adaptation V.120 +hdlc - ITU-T standardized X.31 HDLC flag stuffing +g735 - ITU-T Rec. G.735 for 384 kbit/s video +h223 - ITU-T Recs H.223 and H.245 + +Field Container 6 (type = subr) + +Format: subr=dd,neg=a,sync=a + +Field-02: subr - user rate (sub-rate) + +dd definition +-- +00 - rate is indicated by E-bits in ITU-T Rec. I.460 +01 - 0.6 kbit/s ITU-T Recs V.6 and X.1 +02 - 1.2 kbit/s ITU-T Rec. V.6 +03 - 2.4 kbit/s ITU-T Recs V.6 and X.1 +04 - 3.6 kbit/s ITU-T Rec. V.6 +05 - 4.8 kbit/s ITU-T Recs V.6 and X.1 +06 - 7.2 kbit/s ITU-T Rec. V.6 +07 - 8.0 kbit/s ITU-T Rec. I.460 +08 - 9.6 kbit/s ITU-T Recs V.6 and X.1 + +| | | | +|----------------|--------|------------------------| +| 09 - 14.4 | kbit/s | ITU-T Rec. V.6 | +| 10 - 16.0 | kbit/s | ITU-T Rec. I.460 | +| 11 - 19.2 | kbit/s | ITU-T Rec. V.6 | +| 12 - 32.0 | kbit/s | ITU-T Rec. I.460 | +| 13 - 48.0 | kbit/s | ITU-T Recs V.6 and X.1 | +| 14 - 56.0 | kbit/s | ITU-T Rec. V.6 | +| 15 - 0.1345 | kbit/s | ITU-T Rec. X.1 | +| 16 - 0.1000 | kbit/s | ITU-T Rec. X.1 | +| 17 - 0.075/1.2 | kbit/s | ITU-T Recs V.6 and X.1 | +| 18 - 1.2/0.075 | kbit/s | ITU-T Recs V.6 and X.1 | +| 19 - 0.050 | kbit/s | ITU-T Recs V.6 and X.1 | +| 20 - 0.075 | kbit/s | ITU-T Recs V.6 and X.1 | +| 21 - 0.110 | kbit/s | ITU-T Recs V.6 and X.1 | +| 22 - 0.150 | kbit/s | ITU-T Recs V.6 and X.1 | +| 23 - 0.200 | kbit/s | ITU-T Recs V.6 and X.1 | +| 24 - 0.300 | kbit/s | ITU-T Recs V.6 and X.1 | +| 25 - 12 | kbit/s | ITU-T Rec. V.6 | + +##### Field-03: neg - negotiation + +a definition + - ----- + n - in-band negotiation not possible + y - in-band negotiation possible + +##### Field-04: sync - synchronization + +a definition + - ----- + n - asynchronous + y - synchronous + +##### Field Container 7 (type = v110) V.110/X.30 Rate Adaptation + +Format: int=dd,txnic=a,rxnic=a,txfl=a,rxfl=a + +##### Field-02: int - intermediate rate + +dd definition + -- ----- + 08 - 8 kbit/s + 16 - 16 kbit/s + 32 - 32 kbit/s + +##### Field-03: txnic - Network independent clock (NIC) on transmission (TX) + +a definition + - ----- + u - unknown + y - required to send data with network independent clock + n - not required to send data with network independent clock + +##### Field-04: rxnic - Network independent clock (NIC) on reception (RX) + +a definition + - ----- + u - unknown + y - can accept data with network independent clock + n - cannot accept data with network independent clock + +##### Field-05: txfl - Flow control on transmission (TX) + +a definition + - ----- + u - unknown + y - required to send data with flow control mechanism + n - not required to send data with flow control mechanism + +Field-06: rxfl - Flow control on reception (RX) +a definition +- ----- +u - unknown +y - can accept data with flow control mechanism +n - cannot accept data with flow control mechanism + +Field Container 8 (type = v120) V.120 Rate Adaptation + +Format: hdr=a,mf=a,mode=d,lli=d,asgn=d,inbnd=d + +Field-02: hdr - rate adaptation header +a definition +- ----- +u - unknown +y - rate adaptation header included +n - rate adaptation header not included + +Field-03: mf - multiframe establishment support for data link +a definition +- ----- +u - unknown +y - multiframe frame establishment supported +n - multiframe frame establishment not supported + +Field-04: mode - Mode of operation +d definition +- ----- +0 - bit transparent mode of operation +1 - protocol sensitive mode of operation + +Field-05: lli - Logical link identifier (LLI) negotiation +d definition +- ----- +0 - default LLI of 256 will be used +1 - full protocol negotiation + +Field-06: asgn - assignor/assignee +d definition +- ----- +0 - message originator is "Default Assignee" +1 - message originator is "Assignor only" + +Field-07: inbnd - inband/out-of-band negotiation +d definition +- ----- +0 - not applicable to this standard +1 - negotiation is done in-band using logical link 0 + +Field Container 9 (type = pari) Parity + +Format: stp=d,dat=d,par=a + +Field-02: stp - number of stop bits +d definition +- ----- +1 - 1 bit +2 - 2 bits +3 - 1.5 bits + +Field-03: dat - number of data bits +d definition +- ----- +5 - 5 bits + +7 - 7 bits +8 - 8 bits + +##### Field-04: par - parity + +a definition +- ----- +o - odd +e - even +n - none +0 - forced to 0 +1 - forced to 1 + +##### Field Container 10 (type = modm) Modem Type + +Format: modm=dd,dupl=d + +##### Field-02: modm - modem type + +dd definition +-- ----- +00 - V.22 +01 - V.22 bis +02 - V.23 +03 - V.26 +04 - V.26 bis +05 - V.26 ter +06 - V.27 +07 - V.27 bis +08 - V.27 ter +09 - V.29 +10 - V.32 +11 - V.21 +12 - V.34 + +##### Field-03: dupl - duplex + +d definition +- ----- +h - half-duplex +f - full-duplex + +##### Field Container 11 (type = lay2) Layer 2 Protocol + +Format: lay2=dd,mode=a,use=a,inf=hh,win=ddd + +##### Field-02: lay2 - layer 2 protocol + +dd definition +-- ----- +00 - T1.602 +01 - ITU-T Rec. X.25 link level +02 - ITU-T Rec. Q.921 (I.441) +03 - LAN LLC (ISO/IEC 8802-2) +04 - ITU-T Rec. Q.922 +05 - ITU-T Rec. Q.922 core aspects +06 - Basic Mode ISO 1745 +07 - ITU-T Rec. X.25 Multilink +08 - Extended LAPB +09 - HDLC ARM +10 - HDLC NRM +11 - HDLC ABM +12 - ITU-T Rec. X.75 +13 - User specified +14 - DTE-DCE Operation (ISO/IEC 7776) + +##### Field-03: mode - Mode of Operation + +a definition + +- ----- +n - Normal mode of operation +e - extended mode of operation + +Field-04: use - Q.933 use + +a definition + +- ----- + +n - Coding as defined in ITU-T Rec. Q.933 NOT used + +Field-05: inf - User specified layer 2 protocol information + +hh definition + +-- ----- + +00-FF 2 digit Hex data + +Field-06: win - Window Size (k) + +ddd definition + +--- ----- + +3 digit decimal (range 1 to 127) + +Field Container 12 (type = lay3) Layer 3 Protocol + +Format: lay3=d,mode=a,pks=d,win=ddd,inf=d + +Field-02: lay3 - layer 3 protocol + +d definition + +- ----- + +0 - T1.607 + +1 - ITU-T Rec. X.25 packet layer + +2 - ITU-T Rec. Q.931 (I.451)/ANSI T1.607 + +3 - ISO/IEC TR 9577 + +4 - ISO/IEC 8208 + +5 - ITU-T Rec. X.223 and ISO/IEC 8878 + +6 - ISO/IEC 8473 (OSI Connectionless mode protocol) + +7 - ITU-T Rec. T.70 + +8 - User specified + +Field-03: mode - Mode of Operation + +a definition + +- ----- + +n - Normal mode of operation + +e - extended mode of operation + +Field-04: pks - Default Packet size + +d definition + +- ----- + +0 - Default packet size 16 octets + +1 - Default packet size 32 octets + +2 - Default packet size 64 octets + +3 - Default packet size 128 octets + +4 - Default packet size 256 octets + +5 - Default packet size 512 octets + +6 - Default packet size 1024 octets + +7 - Default packet size 2048 octets + +8 - Default packet size 4096 octets + +Field-05: win - Window size + +ddd definition + +--- ----- + +3 digit decimal in the range of 1-127 + +Field-06: inf - Additional Layer 3 protocol information + +d definition + +- ----- + +0 - Internet Protocol (IP) + +1 - Point-to-Point Protocol (PPP) + +#### 7.3.105 User Service Information Prime (USP) + +Format: USP,type=aaaa,{field container} + +This parameter represents another iteration of the USI. Refer to parameter USI: for formatting rules. + +#### 7.3.106 User Teleservice Information (UTI) + +Format: UTI,cs=a,int=d,pfl=d,hlc=ddd,ehl=ddd + +Fields: + +Field-01: cs - coding standard + +a definition + +- ----- + +u - unknown + +c - ITU-T standardized coding + +i - ISO/IEC standard + +n - national standard + +p - standard defined for the network either public or private + +Field-02: int - interpretation + +d definition + +- ----- + +0 - unknown + +4 - high-level characteristics identification + +Field-03: pfl - presentation method of protocol profile + +d definition + +- ----- + +0 - unknown + +1 - high-level protocol profile + +Field-04: hlc - High-level characteristics identification + +ddd definition + +--- ----- + +000 - no information + +001 - telephony + +002 - group 2/3 fax (ITU-T Rec. F.182) + +003 - group 4 fax class I (ITU-T Rec. F.184) + +004 - group 4 fax class II/III (ITU-T Rec. F.184) + +005 - syntax based videotex (ITU-T Recs F.300 and T.102) + +006 - international videotex interworking + +007 - telex service (ITU-T Rec. F.60) + +008 - message handling systems (ITU-T Rec. X.400) + +009 - OSI application (ITU-T Rec. X.200) + +010 - FTAM application (ISO 8571) + +011 - maintenance + +012 - management + +013 - videotelephony (ITU-T Recs F.720, F.721, F.731) + +014 - videoconferencing (ITU-T Recs F.702, F.731) + +015 - audiographic conferencing (ITU-T Recs F.701, F.731) + +016 - audiovisual service + +017 - multimedia service + +018 - Teletex service, basic mode of operation +(ITU-T Rec. F.200) + +019 - Teletex service, basic and processable mode of operation +(ITU-T Rec. F.220) + +Field-05: ehl - Extended High-level characteristics identification + +ddd definition + +--- ----- + +000 - no information (use when ehl is not present) +otherwise use same definitions as hlc field above + +### 7.3.107 User-To-User Indicators (UUI) + +Format: UUI,type=aaaa,{field container} + +Based on the value of type the following parameters will follow. + +Fields: + +Field-01: type - type of UUI indicator +aaaa description +---- - +reqt - request Field Container 1 +resp - response Field Container 2 + +Field Containers: + +Field Container 1 (type=reqt) + +Format: srv1=a,srv2=a,srv3=a + +Fields: + +Field-02: srv1 - Service 1 +a description +- - +0 - no information +y - request, essential +n - request, not essential + +Field-03: srv2 - Service 2 +a description +- - +0 - no information +y - request, essential +n - request, not essential + +Field-04: srv3 - Service 3 +a description +- - +0 - no information +y - request, essential +n - request, not essential + +Field Container 2 (Type = resp) + +Format: srv1=a,srv2=a,srv3=a,ndi=a + +Fields: + +Field-02: srv1 - Service 1 +a description +- - +0 - no information +y - provided +n - not provided + +Field-03: srv2 - Service 2 +a description +- - +0 - no information +y - provided + +n - not provided + +Field-04: srv3 - Service 3 + +a description +- ----- +0 - no information +y - provided +n - not provided + +Field-05: ndi - network discard indicator + +a description +- ----- +0 - no information +y - user-to-user information discarded by the network + +### 7.3.108 User-To-User Information (UUS) + +Format: UUS, pd=a, dat=1\*(2Hex) + +Fields: + +Field-01: pd - protocol discriminator + +a description +- ----- +0 - user-specific protocol +1 - OSI higher layer protocols +2 - ITU-T Rec. X.263 (replaces ITU-T Rec. X.244) +3 - IA5 characters (are contained in field 2) +4 - ITU-T Recs X.208 and X.209 coded user information +5 - ITU-T Rec. V.120 rate adaption +6 - ITU-T Recs Q.931/I.451 user-network call control messages + +Field-02: dat - user-to-user info + +1\*(2h) description +----- +1\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). + +### 7.3.109 Version of NSS (VER) + +Format: VER, v=aaaa + +Fields: + +Field-01: v - version + +aaaa description +---- ----- +x.yy - x and yy are version.sub-version numerical values, e.g. +"v=2.15". Decimal characters 0-9 must be used for x and yy. + +## 7.4 BAT ASE parameters + +The following parameters may be used to explicitly convey these parameters in NSS rather than tunnelling as ascii-encoded binary inside the apm user information. + +### 7.4.1 Action Indicator (ACT) + +Format: ACT, instr={d,a,d,a}, act=dd + +Fields: + +Field-01: instr - compatibility information + +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible +d description +- ----- +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +Subfield-02: Pass-on possible notification +a description +- ----- +y - send notification +n - do not send notification + +Subfield-03: Pass-on not possible +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification +a description +- ----- +y - send notification +n - do not send notification + +#### **Field-02: act - action indicators** + +dd description +-- ----- +00 - no indication +01 - connect backward +02 - connect forward +03 - connect forward, no notification +04 - connect forward, plus notification +05 - connect forward, no notification + selected codec +06 - connect forward, plus notification + selected codec +07 - use idle +08 - connected +09 - switched +10 - selected codec +11 - modify codec +12 - successful codec modification +13 - codec modification failure +14 - mid-call codec negotiation +15 - modify to selected codec information +16 - mid-call codec negotiation failure +17 - start signal, notify +18 - start signal, no notify +19 - stop signal, notify +20 - stop signal, no notify +21 - start signal acknowledge +22 - start signal reject +23 - stop signal acknowledge +24 - bearer redirect + +### **7.4.2 Backward Network Connection Identifier (BID)** + +Format: BID, instr={d,a,d,a}, bid=1\* (2Hex) + +#### **Fields:** + +Field-01: instr - compatibility information + +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible + +d description +- ----- +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +Subfield-02: Pass-on possible notification + +a description +- ----- +y - send notification +n - do not send notification + +Subfield-03: Pass-on not possible + +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification + +a description +- ----- +y - send notification +n - do not send notification + +Field-02: bid - backward connection identifier + +1\*(2h) description +- ----- +1\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1) of the parameter. + +### 7.4.3 BAT Compatibility Report (BAT) + +Format: BAT, instr={d,a,d,a}, rea=d, diag=(\*{diagnostic\_id, diagnostic\_index}) + +Fields: + +Field-01: instr - compatibility information + +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible + +d description +- ----- +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +Subfield-02: Pass-on possible notification + +a description +- ----- +y - send notification +n - do not send notification + +Subfield-03: Pass-on not possible + +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Field-02: rea - report reason + +d description + +- - - - - + +0 - no indication + +1 - information element non-existent or not implemented + +2 - BICC data with unrecognized information element, discarded + +Field-03: diag - diagnostics + +diag = (\*{diagnostic\_id,diagnostic\_index}) + +NOTE - The diagnostics field is a parenthesis delimited comma-separated list of diagnostics tuples. The diagnostics tuples are delimited by braces. + +### 7.4.4 Bearer Control Information (BCD) + +Format: BCD, instr={d,a,d,a}, dat=1\*(2Hex) + +Fields: + +Field-01: instr - compatibility information + +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible + +d description + +- - - - - + +0 - pass-on + +1 - discard information element + +2 - discard BICC data + +3 - release call + +Subfield-02: Pass-on possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Subfield-03: Pass-on not possible + +d description + +- - - - - + +0 - release call + +1 - discard information element + +2 - discard BICC data + +Subfield-04: Pass-on not possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Field-02: dat - bearer control tunnelling protocol data unit + +1\*(2h) description + +- - - - - + +1\*(2h) - one or more *pairs of* characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1). + +### 7.4.5 Bearer Control Tunnelling (BCT) + +Format: BCT, instr={d,a,d,a}, bct=d + +Fields: + +Field-01: instr - compatibility information +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible + +d description + +- - - - - + +0 - pass-on + +1 - discard information element + +2 - discard BICC data + +3 - release call + +Subfield-02: Pass-on possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Subfield-03: Pass-on not possible + +d description + +- - - - - + +0 - release call + +1 - discard information element + +2 - discard BICC data + +Subfield-04: Pass-on not possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Field-02: bct - bearer control tunnelling indicator + +d description + +- - - - - + +0 - no indication + +1 - tunnelling to be used + +### 7.4.6 Bearer Control Unit Identifier (BDU) + +Format: BDU, instr={d,a,d,a}, lid=hhhhhhh, nid=0\*(2Hex) + +Fields: + +Field-01: instr - compatibility information +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible + +d description + +- - - - - + +0 - pass-on + +1 - discard information element + +2 - discard BICC data + +3 - release call + +Subfield-02: Pass-on possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Subfield-03: Pass-on not possible +d description +- - - - - +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification +a description +- - - - - +y - send notification +n - do not send notification + +Field-02: lid - local identity +hhhhhhhh description +- - - - - +0-9, A-F - 8 IA5 characters 0-9, A-F +representing hexadecimal values + +Field-03: nid - network identity +0\*(2h) description +- - - - - +0\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a +hexadecimal encoding (see clause 5.1) of the parameter. + +### 7.4.7 Bearer Network Connection Characteristics (BNC) + +Format: BNC, instr={d,a,d,a}, bnc=d + +Fields: + +Field-01: instr - compatibility information +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible +d description +- - - - - +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +Subfield-02: Pass-on possible notification +a description +- - - - - +y - send notification +n - do not send notification + +Subfield-03: Pass-on not possible +d description +- - - - - +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification +a description +- - - - - +y - send notification +n - do not send notification + +``` + +Field-02: bnc - bearer network connection characteristics +d description +- ----- +0 - no indication +1 - AAL Type 1 +2 - AAL Type 2 +3 - Structured AAL Type 1 +4 - IP/RTP + +``` + +### 7.4.8 Bearer Redirection Capability (BRC) + +Format: BRC, instr={d,a,d,a}, brc=d + +Fields: + +Field-01: instr - compatibility information +The subfields {d,a,d,a} are defined as follows: + +``` + +Subfield-01: Pass-on possible +d description +- ----- +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +``` + +``` + +Subfield-02: Pass-on possible notification +a description +- ----- +y - send notification +n - do not send notification + +``` + +``` + +Subfield-03: Pass-on not possible +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +``` + +``` + +Subfield-04: Pass-on not possible notification +a description +- ----- +y - send notification +n - do not send notification + +``` + +``` + +Field-02: brc - bearer redirection capability +d description +- ----- +0 - late cut-through not supported +1 - late cut-through supported + +``` + +### 7.4.9 Bearer Redirection Indicators (BRI) + +Format: BRI, instr={d,a,d,a}, bri=(dd, dd,...) + +Fields: + +Field-01: instr - compatibility information +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible +d description +- ----- +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +Subfield-02: Pass-on possible notification +a description +- ----- +y - send notification +n - do not send notification + +Subfield-03: Pass-on not possible +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification +a description +- ----- +y - send notification +n - do not send notification + +Field-02: bri - bearer redirection indicators +dd description +- ----- +00 - no indication +01 - late cut-through request +02 - redirect temporary reject +03 - redirect backwards request +04 - redirect forwards request +05 - redirect bearer release request +06 - redirect bearer release proceed +07 - redirect bearer release complete +08 - redirect cut-through request +09 - redirect bearer connected indication +10 - redirect failure +11 - new connection identifier + +NOTE - One or more indicators are provided in a parenthesis delimited comma-separated list. + +### 7.4.10 Codec List (CDL) + +Format: CDL, instr={d,a,d,a}, ({}, {}, {}, ...) + +Fields: + +Field-01: instr - compatibility information (for the entire codec list) +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible +d description +- ----- +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +Subfield-02: Pass-on possible notification +a description +- ----- +y - send notification +n - do not send notification + +Subfield-03: Pass-on not possible +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification +a description +- ----- +y - send notification +n - do not send notification + +Field-02: This is a parenthesis-delimited comma-separated list of codecs that follow the structure of the COD fields (see clause 7.4.11). The codecs are listed in decreasing order of preference (i.e., codec-1 has highest preference level). + +### 7.4.11 Codec (COD) + +Format: COD, instr={d,a,d,a}, org=ddd, codec=dd, +config=(opt-1,opt-2,opt-3,...), cdat=0\*(2Hex) + +Fields: + +Field-01: instr - compatibility information (for a single codec) +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible +d description +- ----- +0 - pass-on +1 - discard information element +2 - discard BICC data +3 - release call + +Subfield-02: Pass-on possible notification +a description +- ----- +y - send notification +n - do not send notification + +Subfield-03: Pass-on not possible +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification +a description +- ----- +y - send notification +n - do not send notification + +Field-02: org - organization name + ddd description + --- + 000 - no indication + 001 - ITU-T + 002 - ETSI (refer to ETS 126 103) + +Field-03: codec - codec name + dd description + -- + 00 - no indication + 01 - G.711 a-law + 02 - G.711 mu-law + 03 - G.711 a-law 56 kbit/s + 04 - G.711 mu-law 56 kbit/s + 05 - G.722 (sb-adpcm) + 06 - G.723.1 + 07 - Annex A/G.723.1 (silence suppression) + 08 - G.726 (adpcm) + 09 - G.727 (embedded adpcm) + 10 - G.728 + 12 - G.729 (cs-acelp) + 12 - Annex B/G.729 (silence suppression) + +Field-04: config - codec configuration (option selection form) + Config=(opt-1,opt-2,opt-3,...) + +The semantic for each option (opt-1, etc.) is codec-specific and usually defined in a standard, e.g., Table 13/Q.765.5. The semantic follows the byte (first to last) and bit order (LSB to MSB) of the standard. + +When a configuration option is supported, coding is "y"; + when it is not supported, coding is "n". + +For ITU-T Recs G.726 and G.727: (Example: config=(y,n,y,n) means + that 16 and 32 kbit/s are supported) + +| Option# | Description | +|---------|----------------| +| Opt-1 | 16 kbit/s rate | +| Opt-2 | 24 kbit/s rate | +| Opt-3 | 32 kbit/s rate | +| Opt-4 | 40 kbit/s rate | + +For ITU-T Rec. G.728: + +| Option# | Description | +|---------|------------------| +| Opt-1 | 9.6 kbit/s rate | +| Opt-2 | 12.8 kbit/s rate | +| Opt-3 | 16 kbit/s rate | + +For ITU-T Rec. G.729 (cs-acelp) or Annex B: + +| Option# | Description | +|---------|------------------| +| Opt-1 | 6.4 kbit/s rate | +| Opt-2 | 8 kbit/s rate | +| Opt-3 | 11.8 kbit/s rate | + +NOTE - When the value is "()" the NULL list means that all options are supported, i.e., the equivalent of "(y,y,y...)". + When the value is absent this means that there is no configuration data for this codec. + +Field-05: cdat - codec alternate configuration (free-form) + 0\*(2h) description + ----- + 0\*(2h) - one or more pairs of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1) of the parameter. + +### 7.4.12 Interworking Function Address (IWF) + +Format: IWF, instr={d,a,d,a}, iwf=1\*(2Hex) + +Fields: + +Field-01: instr - compatibility information +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible + +d description + +- - - - - + +0 - pass-on + +1 - discard information element + +2 - discard BICC data + +3 - release call + +Subfield-02: Pass-on possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Subfield-03: Pass-on not possible + +d description + +- - - - - + +0 - release call + +1 - discard information element + +2 - discard BICC data + +Subfield-04: Pass-on not possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Field-02: iwf - interworking function address + +1\*(2h) description + +- - - - - + +1\*(2h) - one or more *pairs* of characters (0-9, A-F) representing a hexadecimal encoding (see clause 5.1) of the parameter. + +### 7.4.13 Signal (SIG) + +Format: SIG, instr={d,a,d,a}, sig=(1\*{sigid=dd, dur=ddddd}) + +Fields: + +Field-01: instr - compatibility information +The subfields {d,a,d,a} are defined as follows: + +Subfield-01: Pass-on possible + +d description + +- - - - - + +0 - pass-on + +1 - discard information element + +2 - discard BICC data + +3 - release call + +Subfield-02: Pass-on possible notification + +a description + +- - - - - + +y - send notification + +n - do not send notification + +Subfield-03: Pass-on not possible +d description +- ----- +0 - release call +1 - discard information element +2 - discard BICC data + +Subfield-04: Pass-on not possible notification +a description +- ----- +y - send notification +n - do not send notification + +Field-02: sig - signal +sig = (1\*{sigid,dur}) + +NOTE - The signal field is a parenthesis-delimited comma-separated list of signal tuples. The signal tuples are delimited by braces. + +Subfield-01: sigid - signal identifier +dd description +-- ----- +00 - DTMF 0 +01 - DTMF 1 +02 - DTMF 2 +03 - DTMF 3 +04 - DTMF 4 +05 - DTMF 5 +06 - DTMF 6 +07 - DTMF 7 +08 - DTMF 8 +09 - DTMF 9 +10 - DTMF \* +11 - DTMF # +12 - DTMF A +13 - DTMF B +14 - DTMF C +15 - DTMF D +16 - dial tone +17 - pabx internal dial tone +18 - special dial tone +19 - second dial tone +20 - ringing tone +21 - special ringing tone +22 - busy tone +23 - congestion tone +24 - special information tone +25 - warning tone +26 - instruction tone +27 - call waiting tone +28 - pay tone +29 - payphone recognition tone +30 - comfort tone +31 - tone on hold +32 - record tone +33 - caller waiting tone +34 - positive indication tone +35 - negative indication tone + +``` + +Subfield-02: dur - duration +ddddd description +----- +ddddd - 0-65535 milliseconds the signal is played + +``` + +# 8 MIME encoding of NSS body + +The following clauses describe the header elements specific to MIME (specified in RFC 2045) that may be used to encapsulate NSS within a SIP message. The MIME headers must be used with SIP messages. MIME headers should not be used with H.323 messages, since ITU-T Rec. H.323 has its own encapsulation mechanisms. + +## 8.1 MIME-Version header field + +The MIME-Version header field uses a version number to declare a message to be conformant with MIME and allows mail processing agents to distinguish between such messages and those generated by older or non-conformant software, which are presumed to lack such a field. + +## 8.2 Content-Type header field + +The Content-Type header field for the NSS MIME body is "application/nss". + +In NSS, the optional 'base' parameter is not used. Instead, the source protocol identity is carried in the NSS PRN parameter. + +In NSS, the optional 'version' parameter is not used. Instead, the version of NSS used is carried in the NSS VER parameter. This enables direct transfer from SIP networks to H.323 networks, which do not use the MIME headers in encoding. + +The 'charset' parameter indicates that the contents of the MIME body part will only use 7-bit US-ASCII encoding. In some NSS parameters, one-byte ASCII characters are used to represent the hexadecimal equivalent of one nibble binary values. The 7-bit encoding enables transport through text-based e-mail at the cost of doubling bandwidth. That binary-to-ASCII encoding transformation is usually for compatibility parameters, which are of limited size. + +## 8.3 Content-Transfer-Encoding header field + +A Content-Transfer-Encoding header field is used to indicate both the encoding transformation that was applied to the body and the domain of the result. Encoding transformations other than the identity transformation are usually applied to data in order to allow it to pass through mail transport mechanisms which may have data or character set limitations. + +The mechanism employed for content transfer encoding could be a choice from "7bit", "8bit", "binary", "quoted-printable", "base64", ietf-token, or x-token. ISUP messages are natively binary, but NSS will use US-ASCII to represent all parameter tags and values. Binary values are represented by ASCII representation of the hexadecimal equivalent. This header is optional for NSS. + +## 8.4 Content-Disposition header field + +The Content-Disposition header (specified in RFC 2183) describes how the encapsulated NSS is to be processed and how to handle the received Content-Type if it is not recognized. The default disposition-type for a NSS message body is "signal". This type indicates that the body part contains signalling information associated with the session, but does not describe the session. This header is optional for NSS. + +## 8.5 NSS MIME media type specification + +This media type is defined by the following information: + +- Media type name: application; +- Media subtype name: nss; +- Required parameters: none; +- Optional parameters: charset; +- Encoding scheme: us-ascii; +- Security considerations: See clause 11. + +# 9 Encapsulation in SIP + +NSS is encapsulated in SIP by placing it in the message body. The Content-Type must have value "application/nss" and Content-Disposition must have value "signal". For an example of a SIP message using a MIME header to carry a NSS body, see Appendix I. + +# 10 Encapsulation in H.323 + +NSS may be tunnelled within H.323 version 4 (11/2000) messages. + +However, in order to be backward compatible, the NSS messages can be tunnelled in the **non-StandardControl** field of the H323-UU-PDU parameter of H.323v2 and H.323v3 messages. + +# 11 Security considerations + +Security of NSS, if needed, should use the mechanisms defined for securing components of the encapsulating protocol (i.e., SIP or H.323). + +# 12 NSS-specific syntactical elements and procedures + +## 12.1 NSS-specific messages + +All NSS messages, which are also declared in ISUP, will be used as described in the signalling procedures of ITU-T Rec. Q.761/Q.1902.1. Q.1980.1 will cover handling for new messages or changes to those Recommendations. + +### 12.1.1 Generic Parameter List (GPL) + +The GPL message is used when an application needs to transmit any combination of parameters outside the context of the other defined message types. No semantics are associated with GPL and no state-machine changes are implied. + +### 12.1.2 Unrecognized Message (UNR) + +UNR extends the concept of handling unrecognized parameters to messages. The UNR message transparently transports any message that is not recognized by the native protocol at ingress. The MCI parameter provides the message handling instruction and carries the content of the unrecognized message that is transported to the final destination that may then dispose of the message accordingly. + +## 12.2 NSS-specific parameters + +This clause briefly describes the NSS-specific parameters. + +### **12.2.1 Unrecognized field handling (UFC: Field compatibility mechanism)** + +UFC extends the concept of handling unrecognized parameters using the parameter compatibility information (PCI) to using field compatibility to handle unrecognized fields within a parameter. Further details of parameter construction are defined in clause 12.3 below. + +### **12.2.2 Unrecognized value handling (FDC: Value compatibility mechanism)** + +FDC extends the PCI and UFC concept to cases where the field is recognized, but the value is not recognized. Further details of parameter construction are defined in 12.3 below. + +### **12.2.3 Protocol Name/Version (PRN)** + +PRN provides information about the source protocol for the messages and parameters necessary to interpret them. In particular, compatibility parameters require PRN for interpretation. + +### **12.2.4 Version (VER)** + +VER provides information about the version of NSS used to construct the NSS message and parameters. Use of the same version ensures that parsing of NSS parameters is done correctly. + +### **12.2.5 Segmentation Indicator (SEG)** + +SEG indicates that an additional SGM message is to follow with additional parameters related to the message carrying the SEG parameter. + +### **12.2.6 Global Call Identification (GCI)** + +GCI enables all messages associated with a single "call" to be associated. + +### **12.2.7 Transaction Identifier (TID)** + +At the first ingress point to an IP network, a unique transaction identifier (TID) may be populated on the message. This may be passed unchanged throughout the network so that external call tracing tools (sniffers) can associate any arriving event with its associated generated events. + +### **12.2.8 Mapped Parameter List (MPL)** + +MPL is used to indicate which parameters from the source protocol have been mapped into the parameters of the encapsulating protocol. However, when a parameter is carried by both the protocol encapsulating NSS and NSS, the parameter name shall not be carried in MPL. The parameter list from MPL and the NSS indicates the parameters that were present in the original source message. This aids the receiving node in reconstructing the original PSTN message, albeit some values may have changed. + +NOTE – Movement of a parameter, e.g., through mapping, between NSS and the protocol that carries it, requires a corresponding adjustment to the MPL. The specification of such an interworking, e.g., SIP/NSS to H.323/NSS, is not in the scope of this Recommendation. + +### **12.2.9 Source Parameter Information (SPI)** + +SPI is used to indicate what source parameter type provided the initial information, when the source protocol defines more than one parameter type that could carry the same information, and when a subsequent PSTN call leg is required to use the identical parameter type. If two instances of a parameter are carried by the source protocol, then the order of SPI parameters indicates the original order of the source parameters. + +## **12.3 NSS compatibility procedures** + +The PRN parameter in the message is used to interpret any message/parameter/field compatibility information included in the message. Failure to include this information in the message may + +preclude any such information from being utilized or understood. This could result in the call being dropped if the compatibility instructions point to this action. + +No field shall be placed in a NSS parameter line unless it has been declared in this Recommendation. All fields which exist in network-specific variants of the source protocol, but not in the corresponding parameter for a given NSS parameter specified in this Recommendation, will be treated as unrecognized fields. The parameter name, unrecognized field name, and value can be indicated in a following UFC parameter using field compatibility procedures. Any parameter exceptions to field values can be referenced by parameter name and field number in the FDC parameter. + +NOTE – With respect to the UFC parameter, the ordering of optional fields in national variants of ISUP that may be mapped to UFC is not in the scope of this Recommendation. + +The compatibility parameters for unknown fields (UFC) and unknown values (FDC) must directly follow the parameter that they modify. If compatibility for more than one field is required, the order from top to bottom of the compatibility parameters follows the order defined in NSS or indicates the field order from the source protocol parameter, if not found in NSS. Modification of compatibility parameters is consistent with modification of other parameters such that only the current instance of a compatibility parameter is present in the message for each parameter, field, or value. Examples of the ordering of compatibility parameters are shown in Appendix I. + +A stand-alone FDC or UFC is a syntax error. Handling in that case is not in the scope of this Recommendation. + +When encoding an unrecognized syntax element, the lowest (most granular) compatibility mechanism should be used. For example, with unrecognized: + +- field values, use Known Field Compatibility Information (FDC) +- fields, use Unknown Field Compatibility Information (UFC) +- parameter tags, use Parameter Compatibility Information (PCI) +- message tags, use Unrecognized Message (UNR). + +In essence, UNR should be the last resort, not the first. + +# Annex A + +## Narrowband Signalling Syntax ABNF grammar + +### Part 1. General format of NSS parameters + +``` +nss_message = compact_message + +compact_message = VER_param CRLF + PRN_param CRLF + nss_msg_name "," CRLF + *compact_nss_param +``` + +**NOTE – For detail on the numbers of compact\_fields for nss parameters, see Part 2, Detailed format of individual NSS parameters.** + +``` +nss_msg_name = "ACM" / "ANM" / "APM" / "CFN" / "CON" / + "COT" / "CPG" / "CRG" / "FAA" / "FAC" / + "FAR" / "FOT" / "FRJ" / "GPL" / "IAM" / + "IDR" / "INF" / "INR" / "IRS" / "LOP" / + "NRM" / "OLM" / "PAM" / "PRI" / "REL" / + "RES" / "RLC" / "SAM" / "SDN" / "SGM" / + "SUS" / "UNR" / "USR" / token +``` + +**NOTE – If a field has an unknown value, then it need not be specified explicitly, meaning that there is no value present.** + +``` +opt-unk = ["u"] ; Wherever used "u" may be omitted. +``` + +``` +dat_field = 1*(2HEX) +``` + +``` +HEX = DIGIT / %x41-46 ; 'A-F' case sensitive + ; see clause 5 for rules to transform octet to ascii +``` + +``` +UALPHA = %x41-5a ; 'A-Z' +``` + +``` +LALPHA = %x61-7a ; 'a-z' +``` + +``` +ALPHA = UALPHA / LALPHA +``` + +``` +ALPHANUM = ALPHA / DIGIT +``` + +``` +LALPHANUM = LALPHA / DIGIT +``` + +``` +UALPHANUM = UALPHA / DIGIT +``` + +``` +CHAR = %x20-27 / %x2a-2b / %x2d-3c / %x3e-5b / %x5d-7a / %x7c / %x7e + / NSS_ESCAPED_CHAR +``` + +``` +NSS_ESCAPED_CHAR = %x5c %x0a / ; LF + %x5c %x0d / ; CR + %x5c %x28 / ; opening parenthesis '(' + %x5c %x29 / ; closing parenthesis ')' + %x5c %x2c / ; comma ',' + %x5c %x3d / ; equal '=' + %x5c %x5c / ; backslash '\' + %x5c %x7b / ; opening brace '{' + %x5c %x7d / ; closing brace '}' +``` + +``` +CRLF = %x0d %x0a +``` + +``` +telephone-number = 1*phonedigit +``` + +phonedigit = HEX + +**NOTE - The phone digits are encoded in the same order as they would be transmitted in ISUP or BICC, unlike the hex encoding of binary octets.** + +token = 1\*(alphanum / "-" / "." / "!" / "%" / +"\*" / "\_" / "+" / "`" / "'" / "~" ) ; from RFC 3261, p. 221 + +**NOTE - The grammar given in the next part, Part 2, has been simplified and updated to closely match the specification of clause 7. Both parameter and field definitions have been alphabetized to aid in cross-referencing. Also, note that many data structures have the list of possible values embedded directly in the field definitions.** + +### **Part 2. Detailed formats of individual NSS parameters** + +compact\_nss\_param = ( token / +ACL\_param / ACT\_param / ADI\_param / APP\_param / ATP\_param / +BAT\_param / BCD\_param / BCI\_param / BCT\_param / BDU\_param / +BID\_param / BNC\_param / BRC\_param / BRI\_param / BVN\_param / +CAI\_param / CCN\_param / CCS\_param / CDI\_param / CDL\_param / +CDN\_param / CDP\_param / CDT\_param / CGL\_param / CGN\_param / +CGV\_param / CHI\_param / CIC\_param / CIN\_param / CNF\_param / +CNN\_param / CNR\_param / COD\_param / COL\_param / COR\_param / +CPC\_param / CPI\_param / CPN\_param / CRF\_param / CSI\_param / +CTI\_param / CTN\_param / CTR\_param / DIS\_param / ECI\_param / +EVI\_param / FAI\_param / FCI\_param / FDC\_param / FVN\_param / +GCI\_param / GEA\_param / GED\_param / GIC\_param / GNO\_param / +HOC\_param / HTR\_param / INC\_param / INI\_param / IRI\_param / +ISC\_param / ITG\_param / IWF\_param / LON\_param / LPI\_param / +MCI\_param / MCR\_param / MLP\_param / MPL\_param / MRI\_param / +NMC\_param / NOC\_param / NPF\_param / NRN\_param / NSF\_param / +OBI\_param / OCI\_param / OCN\_param / OCT\_param / OFI\_param / +PBI\_param / PCA\_param / PCI\_param / PCT\_param / PDC\_param / +PFI\_param / PVR\_param / PVS\_param / QOR\_param / RBI\_param / +RCT\_param / RDC\_param / RDS\_param / RFI\_param / RGN\_param / +RMO\_param / RNI\_param / RNN\_param / RNR\_param / SCF\_param / +SEA\_param / SEG\_param / SIG\_param / SPC\_param / SPI\_param / +SRI\_param / SUN\_param / TID\_param / TMP\_param / TMR\_param / +TMU\_param / TNS\_param / UCI\_param / UFC\_param / UID\_param / +USI\_param / USP\_param / UTI\_param / UUI\_param / UUS\_param ) CRLF + +**NOTE - Unless specified explicitly, each field can occur in a parameter at most once, in the order specified below.** + +**NOTE - The following is an alphabetized list of parameter definitions.** + +ACL\_param = "ACL," acl\_field + +ACT\_param = "ACT," inst\_field "," act\_field + +ADI\_param = "ADI," adi\_field + +APP\_param = "APP," aci\_field "," sni\_field "," rci\_field "," sn\_field "," +seg\_field "," slr\_field "," apm\_field + +ATP\_param = "ATP," dat\_field + +BAT\_param = "BAT," inst\_field "," rea\_field "," diag\_list\_field + +BCD\_param = "BCD," inst\_field "," dat\_field + +``` + +BCI_param = "BCI," charge_field "," status_field "," cpc_field "," + e2ei_field "," e2em_field "," inter_field "," isup_ind_field "," + hold_ind_field "," acc_field "," echo_field "," sccpm_field + +BCT_param = "BCT," inst_field "," bct_field + +BDU_param = "BDU," inst_field "," lid_field "," nid_field + +BID_param = "BID," inst_field "," bid_field + +BNC_param = "BNC," inst_field "," bnc_field + +BRC_param = "BRC," inst_field "," brc_field + +BRI_param = "BRI," inst_field "," bri_field + +BVN_param = "BVN," bvn_field + +CAI_param = "CAI," cs_field "," lc_field "," rec_field "," cause_field "," + diag_field + +CCN_param = "CCN," ccn_field + +CCS_param = "CCS," ccs_field + +CDI_param = "CDI," nso_field "," rr_field + +CDL_param = "CDL," inst_field "," codec_list_field + +CDN_param = "CDN," noa_field "," inn_field "," npi_field "," nr_field + +CDP_param = "CDP," toc_field "," comp_field + +CDT_param = "CDT," cdt_field + +CGL_param = ("CGL," cgl_field_0) / + ("CGL," cgl_field_1) / + ("CGL," cgl_field_2) / + ("CGL," cgl_field_3) / + ("CGL," cgl_field_4) / + ("CGL," cgl_field_5) / + ("CGL," cgl_field_6) / + ("CGL," cgl_field_7) / + ("CGL," cgl_field_8) / + ("CGL," cgl_field_9) + +CGN_param = "CGN," noa_field "," cni_field "," npi_field "," pi_field "," + si_field "," nr_field + +CGV_param = ("CGV," cgv_field_0) / + ("CGV," cgv_field_1) / + ("CGV," cgv_field_2) / + ("CGV," cgv_field_3) / + ("CGV," cgv_field_4) + +CHI_param = "CHI," chi_field + +CIC_param = "CIC," cic_field + +CIN_param = "CIN," noa_field "," npi_field "," pi_field "," nr_field + +CNF_param = "CNF," cnf_field + +``` + +``` + +CNN_param = "CNN," noa_field "," npi_field "," pi_field "," si_field "," + nr_field + +CNR_param = "CNR," loc_field "," pc_field "," cls_field "," cre_field + +COD_param = "COD," codec_seq_field + +COL_param = "COL," col_field + +COR_param = "COR," dat_field + +CPC_param = "CPC," cpc_field + +CPI_param = "CPI," dat_field + +CPN_param = "CPN," noa_field "," inn_field "," npi_field "," nr_field + +CRF_param = "CRF," call_id_field "," pc_field + +CSI_param = "CSI," csi_field + +CTI_param = "CTI," cti_field + +CTN_param = "CTN," noa_field "," npi_field "," pi_field "," si_field "," + nr_field + +CTR_param = "CTR," ctr_field + +DIS_param = "DIS," dis_field + +ECI_param = "ECI," out_info_field "," in_info_field "," out_req_field "," + in_req_field + +EVI_param = "EVI," evi "," evr + +FAI_param = "FAI," fai_field + +FCI_param = "FCI," intnat_field "," e2ei_field "," e2em_field "," + inter_field "," isup_ind_field "," isdn_pref "," acc_field "," + sccpm_field + +FDC_param = "FDC," nss_param_name "," nss_field_name "," instr_field "," + dat_field + +FVN_param = ("FVN," fvn_field_1) / + ("FVN," fvn_field_2) / + ("FVN," fvn_field_3) + +GCI_param = "GCI," gci_field + +GEA_param = "GEA," gea_type "," noa_field "," npi_field "," cni_field "," + pi_field "," si_field "," nr_field + +GED_param = "GED," type_of_digit "," encoding_scheme "," nr_field + +GIC_param = "GIC," net_id_field "," gic_bc_field + +GNO_param = "GNO," gno_field + +``` + +``` + +HOC_param = "HOC," hoc_field + +HTR_param = "HTR," noa_field "," npi_field "," nr_field + +INC_param = "INC," dat_field + +INI_param = "INI," ini_info_field "," ini_resp_field "," ini_sol_field + +IRI_param = "IRI," iri_field + +ISC_param = "ISC," pc_field + +ITG_param = "ITG," dat_field + +IWF_param = "IWF," inst_field "," iwf_field + +LON_param = "LON," noa_field "," inn_field "," npi_field "," pi_field "," + si_field "," nr_field + +LPI_param = "LPI," req_field "," loop_field + +MCI_param = "MCI," mci_inst "," tri_field "," dat_field + +MCR_param = "MCR," mcr_resp "," hold_prov + +MLP_param = "MLP," mlp_lfb "," mlp_pl "," net_id_field "," mlp_sd + +MPL_param = "MPL," mpl_field + +MRI_param = "MRI," mlp_req_field "," hold_ind_field + +NMC_param = "NMC," nmc_field + +NOC_param = "NOC," sat_field "," echo_field "," cot_field + +NPF_param = "NPF," nps_field + +NRN_param = "NRN," npi_field "," nrn_noa_field "," nr_field + +NSF_param = "NSF," ton_field "," nip_field "," nsf_nid "," nsf_ind + +OBI_param = "OBI," obi_inb "," obi_cf "," obi_mlpp + +OCI_param = "OCI," noa_field "," npi_field "," pi_field "," si_field "," + nr_field + +OCN_param = "OCN," noa_field "," npi_field "," pi_field "," nr_field + +OCT_param = "OCT," oct_field + +OFI_param = "OFI," cug_call "," con_line_id_req + +PBI_param = ("PBI,tag=u" ) / + ("PBI," pbi_field_1) / + ("PBI," pbi_field_2) / + ("PBI," pbi_field_3) + +``` + +``` + +PCA_param = "PCA," pca_field "," iwri_field + +PCI_param = "PCI," pci_inst "," tri_field "," dat_field + +PCT_param = "PCT," pct_field + +PDC_param = "PDC," pdc_field + +PFI_param = ("PFI,tag=u" ) / + ("PFI,tag=1" ) / + ("PFI," pfi_field_1) / + ("PFI," pfi_field_2) / + ("PFI," pfi_field_3) + +PRN_param = "PRN," prot_field + +PVR_param = "PVR," pvr_field + +PVS_param = "PVS," pvs_field + +QOR_param = "QOR," qor_field + +RBI_param = ("RBI,tag=u" ) / + ("RBI," rbi_field_1) / + ("RBI," rbi_field_2) / + ("RBI," rbi_field_3) + +RCT_param = "RCT," rct_field + +RDC_param = "RDC," rdc_field + +RDS_param = "RDS," rds_field + +RFI_param = ("RFI,tag=u" ) / + ("RFI,tag=1" ) / + ("RFI," rfi_field_1) / + ("RFI," rfi_field_2) / + ("RFI," rfi_field_3) + +RGN_param = "RGN," noa_field "," npi_field "," pi_field "," nr_field + +RMO_param = "RMO," protocol_profile "," dat_field + +RNI_param = "RNI," redirecting_ind "," orig_red__reason "," + redirect_count "," redirect_reason + +RNN_param = "RNN," noa_field "," inn_field "," npi_field "," nr_field + +RNR_param = "RNR," rnr_field + +SCF_param = "SCF," scf_field + +SEA_param = "SEA," sea_field + +SEG_param = "SEG," + +SIG_param = "SIG," inst_field "," sig_list_field + +SPC_param = "SPC," pc_field + +SPI_param = "SPI," mparm_field "," sperm_field + +``` + +``` + +SRI_param = "SRI," sri_field +SUN_param = "SUN," sun_field + +TID_param = "TID," tid_field +TMP_param = "TMP," tmr_field +TMR_param = "TMR," tmr_field +TMU_param = "TMU," tmr_field + +TNS_param = "TNS," ton_field "," nip_field "," trans_field + +UCI_param = "UCI," uci_tc_field "," uci_t9_field + +UFC_param = "UFC," nss_param_name "," instr_field "," nss_field_name "," + dat_field + +UID_param = "UID," uid_tc_field "," uid_t9_field + +USI_param = ("USI," usi_field_1) / + ("USI," usi_field_2) / + ("USI," usi_field_3) / + ("USI," usi_field_4) / + ("USI," usi_field_5) / + ("USI," usi_field_6) / + ("USI," usi_field_7) / + ("USI," usi_field_8) / + ("USI," usi_field_9) / + ("USI," usi_field_10) / + ("USI," usi_field_11) / + ("USI," usi_field_12) / + +USP_param = USI_param + +UTI_param = "UTI," cs_field "," interp_field "," pfl_field "," hlc_field "," + ehl_field + +UUI_param = ("UUI," uui_field_1) / + ("UUI," uui_field_2) + +UUS_param = "UUS," pd_field "," dat_field + +VER_param = "VER," ver_field + +``` + +**NOTE - The following is an alphabetized list of compact field definitions.** + +``` + +acc_field = (opt-unk / "n" / "y") +aci_field = opt-unk / DIGIT +acl_field = (opt-unk / "1" / "2") +act_field = 2DIGIT +adi_field = (opt-unk / "n" / "y") +alt_field = 1*DIGIT + +``` + +``` + +ang_field = 1*DIGIT +apm_field = 0*(2HEX) +asg_field = ("0" / "1") ; CGL +attribute_ids = attribute_id / + ( "(" attribute_id 1*("," attribute_id) ")" ) +attribute_id = "{" attribute_num "," rejected_attribs "," avail_attribs "}" +attribute_num = "1" / ; info transfer cap + "2" / ; info transfer mode + "3" / ; info transfer rate + "4" / ; structure + "5" / ; configuration + "6" / ; establishment + "7" / ; symmetry + "8" / ; info transfer rate_dest_orig + "9" / ; layer id + "A" ; rate multiplier +auc_field = 1*DIGIT +avail_attribs = rejected_attribs + +bct_field = DIGIT +bear_field = 3DIGIT +bid_field = 1*(2HEX) +bnc_field = DIGIT +brc_field = ("0" / "1") +bri_field = "(" redir_ind *( "," redir_ind ) ")" +bvn_field = ("0" / "d" / "s") + +call_id_field = 6HEX +call_rejected_ind = "{" reject_reason "," reject_cond + [ "," user_specific_diag ] [ "," ie_type "," ie_id ] + "}" +cap_field = LALPHANUM +cause_field = 3DIGIT +cc_field = opt-unk / "n" / "1" / "2" +ccbs_ind = (opt-unk / "n" / "y") ; y for CCBS possible, n for CCBS not possible + ; u for unknown +ccn_field = (opt-unk / "n" / "y") +ccs_field = ("0" / "y") +cdpn_coding = "{" noa_field "," npi_field "," nr_field "}" + NOTE - Only short form is used in the 'embedded' field. + +``` + +``` + +cdt_field = (opt-unk / "n" / "y") + +cgl_field_0 = pi_field "," si_field "," opt-unk + +cgl_field_1 = pi_field "," si_field "," "0" "," ns_field "," + lat_field "," lon_field + +cgl_field_2 = pi_field "," si_field "," "1" "," ns_field "," + lat_field "," lon_field "," unc_field "," con_field + +cgl_field_3 = pi_field "," si_field "," "2" "," ns_field "," + lat_field "," lon_field "," unc_field "," asg_field "," + alt_field "," auc_field "," con_field + +cgl_field_4 = pi_field "," si_field "," "3" "," ns_field "," + lat_field "," lon_field "," maj_field "," min_field "," + ori_field "," con_field + +cgl_field_5 = pi_field "," si_field "," "4" "," ns_field "," + lat_field "," lon_field "," rad_field "," off_field "," + ang_field "," con_field + +cgl_field_6 = pi_field "," si_field "," "5" "," num_field "," + pts_fields "," con_field + +cgl_field_7 = pi_field "," si_field "," "6" "," ns_field "," + lat_field "," lon_field "," asg_field "," alt_field + +cgl_field_8 = pi_field "," si_field "," "7" "," ns_field "," + lat_field "," lon_field "," asg_field "," alt_field "," + maj_field "," min_field "," ori_field "," auc_field "," + con_field + +cgl_field_9 = pi_field "," si_field "," "8" "," ns_field "," + lat_field "," lon_field "," inr_field "," unc_field "," + off_field "," ang_field "," con_field + +cgv_field_0 = pi_field "," si_field "," "0" + +cgv_field_1 = pi_field "," si_field "," "1" "," bear_field "," + hvel_field + +cgv_field_2 = pi_field "," si_field "," "2" "," bear_field "," + hvel_field "," dir_field "," vvel_field + +cgv_field_3 = pi_field "," si_field "," "3" "," bear_field "," + hvel_field "," hu_field + +cgv_field_4 = pi_field "," si_field "," "4" "," bear_field "," + hvel_field "," hu_field "," dir_field "," vvel_field "," + vu_field + +chan_type = "0" / "1" / "2" / "3" ; B, H0, H11, H12 channel units respectively + ; per Table 4-13/Q.931 octet 3.2 + ; not generated by ISUP + +charge_field = ("0" / "n" / "y") + +chi_field = 5DIGIT + +cic_field = 10DIGIT + +cls_field = 3DIGIT + +``` + +``` + +cnf_field = ("0" / "n" / "y") +cni_field = (opt-unk / "n" / "y") +codec_field = 2DIGIT +codec_list_field = "(" "{" codec_seq_field "}" + *( "," "{" codec_seq_field "}" ) ")" +codec_seq_field = inst_field "," org_field "," codec_field "," + config_field "," config_alt_field +col_field = ("0" / "y") +comp_field = "0" / "1" +con_field = 1*DIGIT +con_line_id_req = (opt-unk / "n" / "y") +condition_coding = "{" cond_c1 "," cond_c2 "," cond_c3 "}" +cond_c1 = (opt-unk / "0" / "1") ; u for unknown, 0 for user, 1 for provider +cond_c2 = (opt-unk / "0" / "1") ; u for unknown, 0 for normal, 1 for abnormal +cond_c3 = reject_cond +conf_field = (opt-unk / "p") +config_alt_field = *(2HEX) +config_field = [ "(" [ option_field *( "," option_field) ] ")" ] +cot_field = DIGIT +cpc_field = 2DIGIT +cre_field = 3DIGIT +cs_field = ( opt-unk / "c" / "i" / "n" / "p" ) ; i from ITU-T Rec. Q.850 +csi_field = 2DIGIT +cti_field = opt-unk / "f" / "s" +ctr_field = 3DIGIT +cug_call = opt-unk / "n" / "1" / "2" + +dat_field = 1*(2HEX) +data_bit = DIGIT +diag_field = [ "{" [condition_coding] "," ; Condition, see subfield + [tni_coding] "," ; Transit Network Identity (TNS/NSF) + [ccbs_ind] "," ; CCBS Indicator (ITU-T Rec. Q.733.3) + [call_rejected_ind] "," ; Call Rejected Diagnostic + [new_dest] "," ; New destination Called Party Number + [fac_id_reject] "," ; Facility ID/Rejected parameter + [attribute_ids] "," ; Attribute identity + [chan_type] "," ; Channel type + [incompat_param] "," ; Incompatible parameter (IE ID) + ] "}" + +``` + +``` + + [timer_num] "," ; Timer Number + [msg_type] "," ; Message Type + [param_name] "}" ; Parameter Name + ] ; at least one diagnostic or else entire field is empty + +diag_list_field = [ "(" "{" diagnostic_id "," diagnostic_index "}" + *( "," "{" diagnostic_id "," diagnostic_index "}" ) ")" ] + +diagnostic_id = 2HEX + +diagnostic_index = 2(2HEX) + +dir_field = DIGIT + +dis_field = 1*(2Hex) + +dur_field = 5DIGIT + +duration_ms = 5DIGIT + +e2ei_field = (opt-unk / "n" / "y") + +e2em_field = (opt-unk / "n" / "1" / "2" / "3") + +echo_field = (opt-unk / "n" / "y") + +ehl_field = 3DIGIT + +encoding_scheme = DIGIT + +estab_field = (opt-unk / "d") + +evi = opt-unk / "a" / "p" / "i" / DIGIT + +evr = "0" / "y" / "n" + +fai_field = "s" + +fac_id_reject = 1*(2HEX) ;network dependent, variable length. + +fvn_field_1 = "osp," 1*DIGIT + +fvn_field_2 = "cug," 1*DIGIT + +fvn_field_3 = "trn," noa_field "," npi_field "," trn_field + +gci_field = token ["@" token] + +gea_type = ( "dest" / "diad" / "rsrv" / "sufs" / "suns" / + "trs1" / "trs2" / "trs3" / "trs4" / "trs5" / "trs6" ) + +gic_bc_field = 4HEX + +gno_field = 2DIGIT + +hlc_field = 3DIGIT + +hoc_field = 2DIGIT + +hold_ind_field = (opt-unk / "n" / "y") + +``` + +``` + +hold_prov = (opt-unk / "n" / "y") +hu_field = 3DIGIT +hvel_field = 5DIGIT + +ie_type = ("0" / "1") +ie_id = 1*(2HEX) +in_info_field = DIGIT +in_req_field = "0" / "a" / "d" +incompat_param = 2HEX +ini_info_field = DIGIT +ini_resp_field = "i" / "x" / "n" +ini_sol_field = (opt-unk / "n" / "y") +inn_field = (opt-unk / "n" / "y") ; CDN and CPN +inr_field = 1*DIGIT +inst_field = "{ " pass_field "," not_field "," nopass_field "," not_field + "}" +instr_field = opt-unk / DIGIT +inter_field = (opt-unk / "n" / "y") +interp_field = DIGIT ; UTI parameter +intnat_field = (opt-unk / "n" / "y") +iri_field = DIGIT +isdn_pref = opt-unk / "n" / "1" / "2" +isup_ind_field = (opt-unk / "n" / "y") +iwf_field = dat_field +iwri_field = (opt-unk / "n" / "y") ; PCA + +lat_field = 1*DIGIT +layer1_field = 4LALPHANUM +layer2_field = lay2_prot "," lay_mode "," lay2_use "," lay2_inf "," + lay_win +layer3_field = lay3_prot "," lay_mode "," lay3_pks "," lay_win "," + lay3_inf +lay_mode = LALPHA +lay_win = 3DIGIT + +``` + +``` + +lay2_prot = 2DIGIT +lay2_use = LALPHA +lay2_inf = 2HEX +lay3_prot = DIGIT +lay3_pks = DIGIT +lay3_inf = DIGIT +lc_field = ( "unk" / "usr" / "lpn" / "lln" / "tra" / + "rln" / "rpn" / "int" / "bip" ) ;CAI +lid_field = 4(2HEX) +loc_field = 6HEX ;CNR +lon_field = 1*DIGIT +loop_field = (opt-unk / "1" / "2") + +maj_field = 1*DIGIT +mci_inst = opt-unk / DIGIT +mcr_resp = (opt-unk / "n" / "y") +min_field = 1*DIGIT +mlp_lfb = opt-unk / "y" / "n" / "r" +mlp_pl = opt-unk / DIGIT +mlp_req_field = (opt-unk / "n" / "y") +mlp_sd = 6HEX +mod_field = opt-unk / "c" / "p" +modem_type = 2DIGIT +mparm_field = nss_param_name +mpl_field = "(" nss_param_name *("," nss_param_name) ")" +msg_type = 2HEX ; refer to Table 4/Q.763 and Table 4-2/Q.931 +mult_rate_field = 2DIGIT + +neg_field = ("n" / "y") +net_id_field = 4HEX ; GIC and MLP + +new_dest = cdpn_coding / ; CDP alone or CDP plus TNS +( "{" cdpn_coding "," + "{" ton_field "," nip_field "," cc_field "," trans_field "}" + "}" ) + +nid_field = *(2HEX) + +``` + +``` + +nip_field = LALPHANUM ; NSF and TNS +nmc_field = ("0" / "1" / "y") +noa_field = 2DIGIT +nopass_field = DIGIT +not_field = ("n" / "y") +npi_field = opt-unk / DIGIT +nps_field = DIGIT +nr_field = telephone-number +nrn_noa_field = DIGIT +ns_field = ("0" / "1") +nso_field = opt-unk / DIGIT +nsf_nid = 1*(2HEX) +nsf_ind = 1*(2HEX) +num_field = 2DIGIT + +obi_cf = ("0" / "n" / "y") +obi_mlpp = ("0" / "n" / "y") +obi_inb = ("0" / "n" / "y") +oct_field = (opt-unk / "n" / "y") +off_field = 1*DIGIT +option_field = ("y" / "n") +org_field = 3DIGIT +ori_field = 1*DIGIT +orig_red__reason = opt-unk / DIGIT +out_info_field = DIGIT +out_req_field = "0" / "a" / "d" + +param_name = 2HEX ; Table 5/Q.763 (in CAI param) +parity = "o" / "e" / "n" / "0" / "1" +pass_field = DIGIT +pbi_field_1 = "1," duration_ms +pbi_field_2 = "2," call_id_field "," pc_field +pbi_field_3 = "3," redirect_reason_field + +``` + +``` + +pc_cluster = 3DIGIT +pc_field = (pc_net "." pc_cluster "." pc_member) +pc_member = 3DIGIT +pc_net = 3DIGIT +pca_field = DIGIT +pci_inst = opt-unk / DIGIT +pct_field = 2DIGIT +pdc_field = 5DIGIT +pd_field = DIGIT +pfi_field_1 = "2," duration_ms +pfi_field_2 = "3," pfi_ppr "," pfi_ppi +pfi_field_3 = "4," redirect_reason_field +pfi_ppr = 3DIGIT +pfi_ppi = DIGIT +pfl_field = ("0" / "1") +pi_field = opt-unk / "y" / "n" / "0" +prot_field = 5CHAR +protocol_profile = (opt-unk / "1") +pts_field = "{" ns_field "," lat_field "," lon_field "}" +pts_fields = "(" pts_field 2*14("," pts_field) ")" +pvr_field = DIGIT +pvs_field = ("0" / "1" / "2") + +qor_field = ("0" / "y") + +rad_field = 1*DIGIT +rate_field = DIGIT +rbi_field_1 = "1," duration_ms +rbi_field_2 = "2," call_id_field "," pc_field +rbi_field_3 = "3," redirect_reason_field +rci_field = (opt-unk / "n" / "y") +rct_field = 2DIGIT +rdc_field = DIGIT + +``` + +``` + +rds_field = ("0" / "1" / "2") + +rea_field = DIGIT + +rec_field = (opt_unk / "q" / "p" / "1" / "5") + +redir_ind = 2DIGIT + +redirecting_ind = DIGIT + +redirect_count = 2DIGIT + +redirect_reason = opt-unk / DIGIT + +redirect_reason_field = 3DIGIT + +reject_reason = ("00" / "01" / "02") +; 00 for user_specific, +; 01 for IE missing, +; 02 for IE contents not sufficient + +reject_cond = (opt-unk / "0" / "1") +; u for unknown, +; 0 for transient, +; 1 for permanent + +rejected_attribs = rejected_attrib / + "(" rejected_attrib 1*("," rejected_attrib) ")" + +rejected_attrib = 1*(2HEX) + +req_field = ("0" / "1") + +rfi_field_1 = "2," call_id_field "," pc_field + +rfi_field_2 = "3," rfi_prr "," rfi_rpi + +rfi_field_3 = "4," redirect_reason_field + +rfi_prr = 3DIGIT + +rfi_rpi = DIGIT + +rnr_field = (opt-unk / "n" / "y") + +rr_field = opt-unk / DIGIT + +sat_field = opt-unk / DIGIT + +sccpm_field = ("0" / "1" / "2" / "3") + +scf_field = 1*(2HEX) + +sea_field = 2DIGIT + +seg_field = 2DIGIT + +si_field = opt-unk / DIGIT + +sig_list_field = "(" "{" sigid_field "," dur_field "}" + *("," "{" sigid_field "," dur_field "}" ) ")" + +sigid_field = 2DIGIT + +``` + +``` + +slr_field = 2HEX +sn_field = ("0" / "1") +sni_field = (opt-unk / "n" / "y") +sparm_field = 3HEX +sri_field = (opt-unk / "s" / "n") +status_field = (opt-unk / "f" / "c") +stop_bit = DIGIT +str_field = DIGIT +sub_add_field = 2DIGIT +sun_field = nr_field +sym_field = 2LALPHA +sync_field = ("n" / "y") + +tid_field = token ["@" token] +timer_num = 3DIGIT ; not generated by ISUP (in CAI diagnostics) +tmr_field = DIGIT +tni_coding = tni_val / "(" tni_val 1*("," tni_val) ")" ; CAI +tni_val = "{" ("0," ton_field "," nip_field "," nsf_nid "," nsf_ind) ; NSF + / ("1," ton_field "," nip_field "," cc_field "," trans_field) ; TNS + "}" ; encapsulates the corresponding information element + +toc_field = 4LALPHANUM +ton_field = (opt-unk / "c" / "n") ; type of network for CID, NSF, and TNS +trans_field = 1*HEX +trn_field = 1*DIGIT +tri_field = ("0" / "1") +type_of_digit = DIGIT ; GED + +uci_t9_field = ("0" / "y" / "n") +uci_tc_field = ("0" / "y" / "n") +uid_t9_field = ("0" / "y") +uid_tc_field = ("0" / "y") +unc_field = 1*DIGIT +user_specific_diag = 1*(2HEX) +usi_asgn_field = ("0" / "1") + +``` + +``` + +usi_field_1 = "rate," cs_field "," cap_field "," mod_field "," rate_field +usi_field_2 = "sup1," str_field "," estab_field "," conf_field +usi_field_3 = "symm," sym_field "," rate_field +usi_field_4 = "mult," mult_rate_field +usi_field_5 = "lay1," layer1_field +usi_field_6 = "subr," sub_addr_field "," neg_field "," sync_field +usi_field_7 = "v110," usi_int_field "," usi_txnic_field "," + usi_rxnic_field "," usi_txfl_field "," usi_rxfl_field +usi_field_8 = "v120," usi_hdr_field "," usi_mf_field "," usi_mode_field "," + usi_lli_field "," usi_asgn_field "," usi_inband_field +usi_field_9 = "pari," stop_bit "," data_bit "," parity +usi_field_10 = "modm," modem_type +usi_field_11 = "lay2," layer2_field +usi_field_12 = "lay3," layer3_field +usi_hdr_field = (opt-unk / "n" / "y") +usi_inband_field = ("0" / "1") +usi_int_field = 2DIGIT +usi_lli_field = ("0" / "1") +usi_mf_field = (opt-unk / "n" / "y") +usi_mode_field = ("0" / "1") +usi_rxfl_field = (opt-unk / "n" / "y") +usi_rxnic_field = (opt-unk / "n" / "y") +usi_txfl_field = (opt-unk / "n" / "y") +usi_txnic_field = (opt-unk / "n" / "y") +uui_field_1 = "reqt," uui_srv1 "," uui_srv2 "," uui_srv3 +uui_field_2 = "resp," uui_ssrv1 "," uui_ssrv2 "," uui_ssrv3 "," uui_ndi +uui_ndi = ("0" / "y") +uui_srv1 = ("0" / "y" / "n") +uui_srv2 = ("0" / "y" / "n") +uui_srv3 = ("0" / "y" / "n") +uui_ssrv1 = ("0" / "y" / "n") +uui_ssrv2 = ("0" / "y" / "n") +uui_ssrv3 = ("0" / "y" / "n") + +``` + +``` +ver_field = DIGIT "." 2DIGIT +vu_field = 3DIGIT +vvel_field = 3DIGIT +``` + +# Appendix I + +## Narrowband Signalling Syntax (NSS) encoding examples + +## I.1 Message examples + +This appendix provides some examples of (verbose) display and (compact) transmission mode NSS messages, as well as the encapsulation of the NSS body using MIME in a SIP message. + +**Table I.1/Q.1980.1 – Message sequence examples** + +| Display Mode message sequence | Transmission Mode message sequence | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VER,v=1.00
PRN,prot=q1902
IAM,
GCI,gci=1234567890
TID,tid=4444000010
NOC,sat=0,eco=n,cot=0,vci=n
FCI,int=n,e2ei=n,e2em=1,inter=n,iupi=y,pref=n,acc=y,sccpm=0
CPC,cpc=09
USI,type=rate,cs=n,cap=s,mode=c,rate=1
USI,type=lay1,lay1=ulaw
CPN,noa=04,inn=y,npi=1,#=7035551234
CGN,noa=04,cni=y,npi=1,pi=y,si=1,#=4085551234 | VER,1.00
PRN,q1902
IAM,
GCI,1234567890
TID,4444000010
NOC,0,n,0,n
FCI,n,n,1,n,y,n,y,0
CPC,09
USI,rate,n,s,c,1
USI,lay1,ulaw
CPN,04,y,1,7035551234
CGN,04,y,1,y,1,4085551234 | +| VER,v=1.00
PRN,prot=q1902
ACM,
TID,tid=4444000020
GCI,gci=123456789@itsp1.com
BCI,cha=y,sta=f,cpc=09,e2ei=n,e2em=1,inter=n,iupi=y,h=n,acc=y,
eco=n,sccpm=0 | VER,1.00
PRN,q1902
ACM,
TID,tid=4444000020
GCI,123456789@itsp1.com
BCI,y,f,09,n,1,n,y,n,y,n,0 | +| VER,v=1.00
PRN,prot=q1902
ANM,
GCI,gci=1234567890
TID,tid=4444000030 | VER,1.00
PRN,q1902
ANM,
GCI,1234567890
TID,tid=4444000030 | +| VER,v=1.00
PRN,prot=q1902
REL,
GCI,gci=1234567890
TID,tid=4444000040
CAI,cs=c,loc=lln,rec=q,cau=016,di= | VER,1.00
PRN,q1902
REL,
GCI,1234567890
TID,4444000040
CAI,c,lln,q,016, | +| VER,v=1.00
PRN,prot=q1902
RLC,
GCI,gci=1234567890
TID,tid=4444000050 | VER,1.00
PRN,q1902
RLC,
GCI,1234567890
TID,4444000050 | + +To illustrate the use of the 'application/nss' media type, below is an INVITE message which has the originating SDP (specified in RFC 2327) information and the encapsulated ISUP IAM. Note that the two payloads are demarcated by the boundary parameter (specified in RFC 2046) which in the example has the value "unique-boundary". This is part of the specification of MIME multipart and is not related to the 'application/nss' media type. + +Example: + +``` +INVITE sip:7775551212@callagent.company.com SIP/2.0 +Via: SIP/2.0/UDP callagent.itsp.com:5060 +From: Sip:7775553333@callagent.itsp.com +To: Sip:7775551212@callagent.company.com +Call-ID: Q23ert67@callagent.itsp.com +Cseq: 1 +Contact: +Subject: Transit stuff +Content-Type: multipart-mixed; boundary=unique-boundary +Content-Length: 1234 +MIME-Version: 1.0 + +--unique-boundary +Content-Type: application/sdp; charset=us-ascii + +v=0 +o=john-doe 200104101630 001 IN IP4 111.22.33.4 +s=NSS Call Session +c=IN IP4 callagent.company.com +t= 3034423619 3034443619 +m=audio 9092 RTP/AVP 0 3 4 + +--unique-boundary +Content-Type: application/nss; charset=us-ascii +Content-Transfer-Encoding: 7bit +Content-Disposition: signal; handling=required + +VER,1.00 +PRN,q1902 +IAM, +GCI,1234567890123456 +TID,444400001 +NOC,0,n,0,n +FCI,n,n,l,n,y,n,y,n +CPC,09 +``` + +``` + +USI,rate,n,s,c,1 +USI,lay1,ulaw +CPN,04,y,1,7891234567 +CGN,04,y,1,y,1,9876543210 +--unique-boundary— + +``` + +### I.2 Compatibility ordering example + +The following is an example of the order in which compatibility parameters are found in an NSS message. A FDC (or UFC) must immediately follow the parameter whose field value needs the FDC (or UFC). If there are more than one FDC for the same instance of a parameter, the order of those FDCs (or UFCs) shall follow the order of the fields that occur in the parameter. + +For example, suppose both the noa and pi fields of the first GEA need FDC and the si field of the second GEA also need FDC, then proper order of parameters shall be: + +``` + +GEA,,,,,,,<#> +FDC for noa,,, +FDC for pi,,, +GEA,,,,,,,<#> +FDC for si,,, + +``` + +The following is an incorrect message structure, because it would indicate that the values in the three FDC parameters were associated with the number found in the second GEA parameter: + +``` + +GEA,,,,,,,<#> +GEA,,,,,,,<#> +FDC for noa,,, +FDC for pi,,, +FDC for si,,, + +``` + +### I.3 GCI and TID structure example + +The following are some suggested guidelines for constructing GCI and TID values. + +Use values of the form: locally-unique-identifier@address, where locally-unique-identifier is a value determined by the protocol, and address is a globally unique. Use of an IPv4 address of the form: 123.123.123.123, IPv6 address, or a fully qualified domain name (FQDN) is recommended. An ASCII representation of the 48-bit IEEE 802 address can also be used. It is recommended that the locally-unique-identifier be a 16-character value composed of monotonically increasing IA5 0-9 or A-F characters. + +For mapping to the ITU-T H.225 standard for GloballyUniqueID, this could also be a 16-character ASCII representation of a UTC timestamp followed by a 4-character ASCII representation of the clock sequence. That could be expanded directly from the 10-byte 8-bit value from GloballyUniqueID or the UTC timestamp could be ordered with the year in the leftmost position. + +The BICC Global Call Reference binary octets could be represented as hex digits in the locally\_unique\_identifier, followed by the "@" and the FQDN of the gateway. The "dot" character would separate the three parts of the global call reference (e.g., a 3-octet reference value: + +msb->1000 0010<-lsb, 0000 0011, and 0001 1010 would appear as: 82.03.1A@gw1-abc.com). + +Since the Call-ID is generated by and for SIP, there is no reason to deal with the complexity of URL-encoding and case-ignoring string comparison. The following is extracted from SIP: + +The callid MUST be a globally unique identifier and MUST NOT be reused for later calls. Use of cryptographically random identifiers is RECOMMENDED. Implementations MAY use the form "localid@host". Call-IDs are case-sensitive and are simply compared byte-by-byte. Using cryptographically random identifiers provides some protection against session hijacking. Call-ID, To and From are needed to identify a call leg. The distinction between call and call leg matters in calls with third-party control. + +# Appendix II + +## NSS verbose encoding + +It is possible to easily generate the verbose description from compact transmission mode by inserting the field name string literals of the form "tag=" into their fixed positions. Likewise, the compact mode can be generated from the verbose description by removing the "tag=" from all fields. + +### General format of NSS verbose description ABNF + +The compact transmission encoding and verbose description use identical message, parameter, and value formats. Only the field encoding differs. The field formats include the tag literals as defined below. + +``` +verbose_message = VER_param CRLF ; using the field definitions below + PRN_param CRLF ; using the field definitions below + nss_msg_name "," CRLF + *verbose_nss_param ; using the field definitions below +``` + +**NOTE - The following is an alphabetized list of verbose field definitions.** + +``` +acc_field = "acc=" (opt-unk / "n" / "y") +aci_field = "aci=" opt-unk / DIGIT +acl_field = "acl=" (opt-unk / "1" / "2") +act_field = "act=" 2DIGIT +adi_field = "adi=" (opt-unk / "n" / "y") +alt_field = "alt=" 1*DIGIT +ang_field = "ang=" 1*DIGIT +apm_field = "apm=" 0*(2HEX) +asg_field = "as=" ("0" / "1") ; CGL +attribute_ids = attribute_id / + ( "(" attribute_id 1*("," attribute_id) ")" ) +attribute_id = "{" attribute_num "," rejected_attribs "," avail_attribs "}" +attribute_num = "1" / ; info transfer cap + "2" / ; info transfer mode + "3" / ; info transfer rate + "4" / ; structure + "5" / ; configuration + "6" / ; establishment + "7" / ; symmetry + "8" / ; info transfer rate_dest_orig + "9" / ; layer id + "A" ; rate multiplier +auc_field = "auc=" 1*DIGIT +avail_attribs = rejected_attribs +``` + +``` + +bct_field = "bct=" DIGIT +bear_field = "bear=" 3DIGIT +bid_field = "bid=" 1*(2HEX) +bnc_field = "brc=" DIGIT +brc_field = "brc=" ("0" / "1") +bri_field = "bri=" "(" redir_ind *( "," redir_ind ) ")" +bvn_field = "tai=" ("0" / "d" / "s") + +call_id_field = "cid=" 6HEX +call_rejected_ind = "{ " reject_reason "," reject_cond + [ "," user_specific_diag ] [ "," ie_type "," ie_id ] + "}" +cap_field = "cap=" LALPHANUM +cause_field = "cau=" 3DIGIT +cc_field = "cc=" opt-unk / "n" / "1" / "2" +ccbs_ind = (opt-unk / "n" / "y") ; y for CCBS possible, n for CCBS not possible + ; u for unknown +ccn_field = "cpi=" (opt-unk / "n" / "y") +ccs_field = "ccss=" ("0" / "y") +cdpn_coding = "{ " noa_field "," npi_field "," nr_field "}" + NOTE - Only short form is used in the 'embedded' field. +cdt_field = "ct=" (opt-unk / "n" / "y") +cgl_field_0 = pi_field "," si_field "," "type=u" +cgl_field_1 = pi_field "," si_field "," "type=0" "," ns_field "," + lat_field "," lon_field +cgl_field_2 = pi_field "," si_field "," "type=1" "," ns_field "," + lat_field "," lon_field "," unc_field "," con_field +cgl_field_3 = pi_field "," si_field "," "type=2" "," ns_field "," + lat_field "," lon_field "," unc_field "," asg_field "," + alt_field "," auc_field "," con_field +cgl_field_4 = pi_field "," si_field "," "type=3" "," ns_field "," + lat_field "," lon_field "," maj_field "," min_field "," + ori_field "," con_field +cgl_field_5 = pi_field "," si_field "," "type=4" "," ns_field "," + lat_field "," lon_field "," rad_field "," off_field "," + ang_field "," con_field +cgl_field_6 = pi_field "," si_field "," "type=5" "," num_field "," + pts_fields "," con_field +cgl_field_7 = pi_field "," si_field "," "type=6" "," ns_field "," + lat_field "," lon_field "," asg_field "," alt_field + +``` + +``` + +cgl_field_8 = pi_field "," si_field "," "type=7" "," ns_field "," + lat_field "," lon_field "," asg_field "," alt_field "," + maj_field "," min_field "," ori_field "," auc_field "," + con_field + +cgl_field_9 = pi_field "," si_field "," "type=8" "," ns_field "," + lat_field "," lon_field "," inr_field "," unc_field "," + off_field "," ang_field "," con_field + +cgv_field_0 = pi_field "," si_field "," "type=0" + +cgv_field_1 = pi_field "," si_field "," "type=1" "," bear_field "," + hvel_field + +cgv_field_2 = pi_field "," si_field "," "type=2" "," bear_field "," + hvel_field "," dir_field "," vvel_field + +cgv_field_3 = pi_field "," si_field "," "type=3" "," bear_field "," + hvel_field "," hu_field + +cgv_field_4 = pi_field "," si_field "," "type=4" "," bear_field "," + hvel_field "," hu_field "," dir_field "," vvel_field "," + vu_field + +chan_type = "0" / "1" / "2" / "3" ; B, H0, H11, H12 channel units respectively + ; per Table 4-13/Q.931 octet 3.2 + ; not generated by ISUP + +charge_field = "cha=" ("0" / "n" / "y") + +chi_field = "pd=" 5DIGIT + +cic_field = "cic=" 10DIGIT + +cls_field = "cls=" 3DIGIT + +cnf_field = "cai=" ("0" / "n" / "y") + +cni_field = "cni=" (opt-unk / "n" / "y") + +codec_field = "codec=" 2DIGIT + +codec_list_field = "(" "{" codec_seq_field "}" + *( "," "{" codec_seq_field "}" ) ")" + +codec_seq_field = inst_field "," org_field "," codec_field "," + config_field "," config_alt_field + +col_field = "cci=" ("0" / "y") + +comp_field = "comp=" "0" / "1" + +con_field = "con=" 1*DIGIT + +con_line_id_req = (opt-unk / "n" / "y") + +condition_coding = "{" cond_c1 "," cond_c2 "," cond_c3 "}" + +cond_c1 = (opt-unk / "0" / "1") ; u for unknown, 0 for user, 1 for provider + +cond_c2 = (opt-unk / "0" / "1") ; u for unknown, 0 for normal, 1 for abnormal + +cond_c3 = reject_cond + +``` + +``` + +conf_field = "conf=" (opt-unk / "p") +config_alt_field = "cdat=" *(2HEX) +config_field = "config=" [ "(" [ option_field *( "," option_field) ] ")" ] +cot_field = "cot=" DIGIT +cpc_field = "cpc=" 2DIGIT +cre_field = "cre=" 3DIGIT +cs_field = "cs=" ( opt-unk / "c" / "i" / "n" / "p" ) ; i ITU-T Rec. from Q.850 +csi_field = "csi=" 2DIGIT +cti_field = "cti=" opt-unk / "f" / "s" +ctr_field = "ref=" 3DIGIT +cug_call = "cug=" opt-unk / "n" / "1" / "2" + +dat_field = "dat=" 1*(2HEX) +data_bit = "dat=" DIGIT + +diag_field = [ "{" [condition_coding] "," ; Condition, see subfield + [tni_coding] "," ; Transit Network Identity + (TNS/NSF) + [ccbs_ind] "," ; CCBS Indicator (Q.733.3) + [call_rejected_ind] "," ; Call Rejected Diagnostic + [new_dest] "," ; New destination Called Party + Number + [fac_id_reject] "," ; Facility ID/Rejected parameter + [attribute_ids] "," ; Attribute identity + [chan_type] "," ; Channel type + [incompat_param] "," ; Incompatible parameter (IE ID) + [timer_num] "," ; Timer Number + [msg_type] "," ; Message Type + [param_name] "}" ; Parameter Name +] ; at least one diagnostic or else entire field is empty + +``` + +**NOTE - The diagnostics subfields do not have tags (tag=) construction.** + +``` + +diag_list_field = "diag=" [ "(" "{" diagnostic_id "," diagnostic_index "}" + *( "," "{" diagnostic_id "," diagnostic_index "}" ) ")" ] +diagnostic_id = 2HEX +diagnostic_index = 2(2HEX) +dir_field = "dir=" DIGIT +dis_field = "info=" 1*(2Hex) +dur_field = "dur=" 5DIGIT +duration_ms = "dur=" 5DIGIT + +e2ei_field = "e2ei=" (opt-unk / "n" / "y") + +``` + +``` + +e2em_field = "e2em=" (opt-unk / "n" / "1" / "2" / "3") +echo_field = "eco=" (opt-unk / "n" / "y") +ehl_field = "ehl=" 3DIGIT +encoding_scheme = "es=" DIGIT +estab_field = "estab=" (opt-unk / "d") +evi = "evi=" opt-unk / "a" / "p" / "i" / DIGIT +evr = "evr=" "0" / "y" / "n" + +fai_field = "fai=" "s" +fac_id_reject = 1*(2HEX) ;network dependent, variable length. +fvn_field_1 = "type=osp,osp=" 1*DIGIT +fvn_field_2 = "type=cug,cug=" 1*DIGIT +fvn_field_3 = "type=trn," noa_field "," npi_field "," trn_field + +gci_field = "gci=" token ["@" token] +gea_type = "type=" ("dest" / "diad" / "rsrv" / "sufs" / "suns" / + "trs1" / "trs2" / "trs3" / "trs4" / "trs5" / "trs6" ) +gic_bc_field = "bc=" 4HEX +gno_field = "ni=" 2DIGIT + +hlc_field = "hlc=" 3DIGIT +hoc_field = "hc=" 2DIGIT +hold_ind_field = "h=" (opt-unk / "n" / "y") +hold_prov = "hp=" (opt-unk / "n" / "y") +hu_field = "hu=" 3DIGIT +hvel_field = "hvel=" 5DIGIT + +ie_type = ("0" / "1") +ie_id = 1*(2HEX) +in_info_field = "iei=" DIGIT +in_req_field = "ier=" "0" / "a" / "d" +incompat_param = 2HEX +ini_info_field = "inf=" DIGIT +ini_resp_field = "inf=" "i" / "x" / "n" +ini_sol_field = "inf=" (opt-unk / "n" / "y") + +``` + +``` + +inn_field = "inn=" (opt-unk / "n" / "y") ; CDN and CPN +inr_field = "inr=" 1*DIGIT +inst_field = "instr={" pass_field "," not_field "," nopass_field "," not_field + "}" +instr_field = "instr=" opt-unk / DIGIT +inter_field = "inter=" (opt-unk / "n" / "y") +interp_field = "int=" DIGIT ; UTI +intnat_field = "int=" (opt-unk / "n" / "y") +iri_field = "iri=" DIGIT +isdn_pref = "pref=" opt-unk / "n" / "1" / "2" +isup_ind_field = "iupi=" (opt-unk / "n" / "y") +iwf_field = "iwf=" dat_field +iwri_field = "iwri=" (opt-unk / "n" / "y") ; PCA + +lat_field = "lat=" 1*DIGIT +layer1_field = "lay1=" 4LALPHANUM +layer2_field = lay2_prot "," lay_mode "," lay2_use "," lay2_inf "," lay_win +layer3_field = lay3_prot "," lay_mode "," lay3_pks "," lay_win "," lay3_inf +lay_mode = "mode=" LALPHA +lay_win = "win=" 3DIGIT +lay2_prot = "lay2=" 2DIGIT +lay2_use = "use=" LALPHA +lay2_inf = "inf=" 2HEX +lay3_prot = "lay3=" DIGIT +lay3_pks = "pks=" DIGIT +lay3_inf = "inf=" DIGIT +lc_field = "loc=" ( "unk" / "usr" / "lpn" / "lln" / "tra" / + "rln" / "rpn" / "int" / "bip" ) ; CAI +lid_field = "lid=" 4(2HEX) +loc_field = "loc=" 6HEX ; CNR +lon_field = "lon=" 1*DIGIT +loop_field = "lpi=" (opt-unk / "1" / "2") + +maj_field = "maj=" 1*DIGIT + +``` + +``` + +mci_inst = "instr=" opt-unk / DIGIT +mcr_resp = "rp=" (opt-unk / "n" / "y") +min_field = "min=" 1*DIGIT +mlp_lfb = "lfb=" opt-unk / "y" / "n" / "r" +mlp_pl = "pl=" opt-unk / DIGIT +mlp_req_field = "ri=" (opt-unk / "n" / "y") +mlp_sd = "sd=" 6HEX +mod_field = "mode=" opt-unk / "c" / "p" +modem_type = "modm=" 2DIGIT +mparm_field = "mparm=" nss_param_name +mpl_field = "plist=" "(" nss_param_name *("," nss_param_name) ")" +msg_type = 2HEX ; refer to Table 4/Q.763 and Table 4-2/Q.931 +mult_rate_field = "mult=" 2DIGIT + +neg_field = "neg=" ("n" / "y") +net_id_field = "ni=" 4HEX ; GIC and MLP +new_dest = cdpn_coding / ; CDP alone or CDP plus TNS + ( "{" cdpn_coding "," + "{" ton_field "," nip_field "," cc_field "," trans_field "}" + "}" ) +nid_field = "nid=" *(2HEX) +nip_field = "nip=" LALPHANUM ; NSF and TNS +nmc_field = "tari=" ("0" / "1" / "y") +noa_field = "noa=" 2DIGIT +nopass_field = DIGIT +not_field = ("n" / "y") +npi_field = "npi=" opt-unk / DIGIT +nps_field = "nps=" DIGIT +nr_field = "#=" telephone-number +nrn_noa_field = "noa=" DIGIT + +ns_field = "ns=" ("0" / "1") +nso_field = "nso=" opt-unk / DIGIT +nsf_nid = "nid=" 1*(2HEX) + +``` + +``` + +nsf_ind = "nsf=" 1*(2HEX) +num_field = "num=" 2DIGIT + +obi_cf = "cf=" ("0" / "n" / "y") +obi_mlpp = "mlpp=" ("0" / "n" / "y") +obi_inb = "inb=" ("0" / "n" / "y") +oct_field = "coi=" (opt-unk / "n" / "y") +off_field = "off=" 1*DIGIT +option_field = ("y" / "n") +org_field = "org=" 3DIGIT +ori_field = "ori=" 1*DIGIT +orig_red__reason = "orr=" opt-unk / DIGIT +out_info_field = "oei=" DIGIT +out_req_field = "oer=" "0" / "a" / "d" + +param_name = 2HEX ; Table 5/Q.763 (in CAI param) +parity = "parity=" ("o" / "e" / "n" / "0" / "1") +pass_field = DIGIT +pbi_field_1 = "tag=1," duration_ms +pbi_field_2 = "tag=2," call_id_field "," pc_field +pbi_field_3 = "tag=3," redirect_reason_field +pc_cluster = 3DIGIT +pc_field = "pc=" (pc_net "." pc_cluster "." pc_member) +pc_member = 3DIGIT +pc_net = 3DIGIT +pca_field = "ppi=" DIGIT +pci_inst = "instr=" (opt-unk / DIGIT) +pct_field = "pct=" 2DIGIT +pdc_field = "pd=" 5DIGIT +pd_field = "pd=" DIGIT +pfi_field_1 = "tag=2," duration_ms +pfi_field_2 = "tag=3," pfi_ppr "," pfi_ppi +pfi_field_3 = "tag=4," redirect_reason_field + +``` + +``` + +pfi_ppr = "ppr=" 3DIGIT +pfi_ppi = "ppi=" DIGIT +pfl_field = "pfl=" ("0" / "1") +pi_field = "pi=" opt-unk / "y" / "n" / "0" +prot_field = "prot=" 5CHAR +protocol_profile = "pp=" (opt-unk / "1") +pts_field = "{" ns_field "," lat_field "," lon_field "}" +pts_fields = "(" pts_field 2*14("," pts_field) ")" +pvr_field = "pvr=" DIGIT +pvs_field = "psi=" ("0" / "1" / "2") + +qor_field = "qor=" ("0" / "y") + +rad_field = "rad=" 1*DIGIT +rate_field = "rate=" DIGIT +rbi_field_1 = "tag=1," duration_ms +rbi_field_2 = "tag=2," call_id_field "," pc_field +rbi_field_3 = "tag=3," redirect_reason_field +rci_field = "rci=" (opt-unk / "n" / "y") +rct_field = "rc=" 2DIGIT +rdc_field = "rc=" DIGIT +rds_field = "rpi=" ("0" / "1" / "2") +rea_field = "rea=" DIGIT +rec_field = "rec=" (opt_unk / "q" / "p" / "1" / "5") +redir_ind = 2DIGIT +redirecting_ind = "ri=" DIGIT +redirect_count = "rc=" 2DIGIT +redirect_reason = "rr=" (opt-unk / DIGIT) +redirect_reason_field = "rea=" 3DIGIT + +reject_reason = ("00" / "01" / "02") +; 00 for user_specific, +; 01 for IE missing, +; 02 for IE contents not sufficient +reject_cond = (opt-unk / "0" / "1") +; u for unknown, +; 0 for transient, + +``` + +``` + +; 1 for permanent + +rejected_attribs = rejected_attrib / + "(" rejected_attrib 1*("," rejected_attrib) ")" + +rejected_attrib = 1*(2HEX) + +req_field = "req=" ("0" / "1") + +rfi_field_1 = "tag=2," call_id_field "," pc_field + +rfi_field_2 = "tag=3," rfi_prr "," rfi_rpi + +rfi_field_3 = "tag=4," redirect_reason_field + +rfi_prr = "prr=" 3DIGIT + +rfi_rpi = "rpi=" DIGIT + +rnr_field = "rnr=" (opt-unk / "n" / "y") + +rr_field = "rr=" opt-unk / DIGIT + +sat_field = "sat=" (opt-unk / DIGIT) + +sccpm_field = "sccpm=" ("0" / "1" / "2" / "3") + +scf_field = "scf=" 1*(2HEX) + +sea_field = "fci=" 2DIGIT + +seg_field = "seq=" 2DIGIT + +si_field = "si=" opt-unk / DIGIT + +sig_list_field = "sig=" "(" "{" sigid_field "," dur_field "}" + *(" " "," "{" sigid_field "," dur_field "}" ) ")" + +sigid_field = "sigid=" 2DIGIT + +slr_field = "slr=" 2HEX + +sn_field = "si=" ("0" / "1") + +sni_field = "sni=" (opt-unk / "n" / "y") + +sparm_field = "sparm=" 3HEX + +sri_field = "sri=" (opt-unk / "s" / "n") + +status_field = "sta=" (opt-unk / "f" / "c") + +stop_bit = "stp=" DIGIT + +str_field = "str=" DIGIT + +sub_add_field = "subr=" 2DIGIT + +sun_field = nr_field + +sym_field = "sym=" 2LALPHA + +sync_field = "sync=" ("n" / "y") + +``` + +``` + +tid_field = "tid=" token ["@" token] + +timer_num = 3DIGIT ; not generated by ISUP (in CAI diagnostics) + +tmr_field = "tmr=" DIGIT + +tni_coding = tni_val / "(" tni_val 1*("," tni_val) ")" ; CAI + +tni_val = "{" ("0," ton_field "," nip_field "," nsf_nid "," nsf_ind) ; NSF + / ("1," ton_field "," nip_field "," cc_field "," trans_field) ; TNS + "}" ; encapsulates the corresponding information element + +toc_field = "toc=" 4LALPHANUM + +ton_field = "ton=" (opt-unk / "c" / "n") ; type of network for CID, NSF, and + TNS + +trans_field = "tns=" 1*HEX + +trn_field = "trn=" 1*DIGIT + +tri_field = "tri=" ("0" / "1") + +type_of_digit = "tod=" DIGIT ; GED + +uci_t9_field = "t9=" ("0" / "y" / "n") + +uci_tc_field = "tc=" ("0" / "y" / "n") + +uid_t9_field = "t9=" ("0" / "y") + +uid_tc_field = "tc=" ("0" / "y") + +unc_field = "unc=" 1*DIGIT + +user_specific_diag = 1*(2HEX) + +usi_asgn_field = "asgn=" ("0" / "1") + +usi_field_1 = "type=rate," cs_field "," cap_field "," mod_field "," rate_field + +usi_field_2 = "type=sup1," str_field "," estab_field "," conf_field + +usi_field_3 = "type=symm," sym_field "," rate_field + +usi_field_4 = "type=mult," mult_rate_field + +usi_field_5 = "type=lay1," layer1_field + +usi_field_6 = "type=subr," sub_addr_field "," neg_field "," sync_field + +usi_field_7 = "type=v110," usi_int_field "," usi_txníc_field "," + usi_rxníc_field "," usi_txfl_field "," usi_rxfl_field + +usi_field_8 = "type=v120," usi_hdr_field "," usi_mf_field "," usi_mode_field "," + usi_lli_field "," usi_asgn_field "," usi_inband_field + +usi_field_9 = "type=pari," stop_bit "," data_bit "," parity + +usi_field_10 = "type=modm," modem_type + +``` + +``` + +usi_field_11 = "type=lay2," layer2_field +usi_field_12 = "type=lay3," layer3_field +usi_hdr_field = "hdr=" (opt-unk / "n" / "y") +usi_inband_field = "inbnd=" ("0" / "1") +usi_int_field = "int=" 2DIGIT +usi_lli_field = "lli=" ("0" / "1") +usi_mf_field = "mf=" (opt-unk / "n" / "y") +usi_mode_field = "mode=" ("0" / "1") +usi_rxfl_field = "rxfl=" (opt-unk / "n" / "y") +usi_rxnic_field = "rxnic=" (opt-unk / "n" / "y") +usi_txfl_field = "txfl=" (opt-unk / "n" / "y") +usi_txnic_field = "txnic=" (opt-unk / "n" / "y") +uui_field_1 = "type=reqt," uui_srv1 "," uui_srv2 "," uui_srv3 +uui_field_2 = "type=resp," uui_ssrv1 "," uui_ssrv2 "," uui_ssrv3 "," uui_ndi +uui_ndi = "ndi=" ("0" / "y") +uui_srv1 = "srv1=" ("0" / "y" / "n") +uui_srv2 = "srv2=" ("0" / "y" / "n") +uui_srv3 = "srv3=" ("0" / "y" / "n") +uui_ssrv1 = "srv1=" ("0" / "y" / "n") +uui_ssrv2 = "srv2=" ("0" / "y" / "n") +uui_ssrv3 = "srv3=" ("0" / "y" / "n") + +ver_field = "v=" DIGIT "." 2DIGIT +vu_field = "vu=" 3DIGIT +vvel_field = "vvel=" 3DIGIT + +``` + + + +## 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.2-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.2-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.2100-199407-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2100-199407-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..44b559906b9b18f71cd0f05fea94f75f62acd1ae --- /dev/null +++ b/marked/Q/T-REC-Q.2100-199407-I_PDF-E/raw.md @@ -0,0 +1,189 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.2100** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/94) + +**BROADBAND ISDN** + +--- + +**B-ISDN SIGNALLING ATM ADAPTATION +LAYER (SAAL) OVERVIEW DESCRIPTION** + +**ITU-T Recommendation Q.2100** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU 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.2100 was prepared by the ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 29th of July 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 ..... | 1 | +| 2 Normative references ..... | 1 | +| 3 Abbreviations ..... | 1 | +| 4 General ..... | 2 | +| 5 Description of SAAL ..... | 2 | +| 5.1 SAAL-SAP ..... | 2 | +| 5.2 SSCF-UNI ..... | 2 | +| 5.3 SSCF-NNI ..... | 2 | +| 5.4 SSCOP ..... | 2 | +| 5.5 CPCS ..... | 3 | +| 5.6 SAR ..... | 3 | +| 5.7 ATM-SAP ..... | 3 | + +# **SUMMARY** + +This Recommendation briefly describes the various components which make up the AAL functions necessary to support signalling (SAAL). It is intended to serve as a guide to all other Recommendations required by a user for the implementation of an AAL for the purpose of signalling. + +The ATM adaptation layer (AAL) is defined as enhancing the services provided by the ATM layer to support the functions required by the next higher layer. Different AALs support various protocols to suit the different needs of a range of AAL service users. One particular type of AAL service user is the signalling entity wishing to communicate with a peer entity. The SAAL comprises AAL functions necessary to support such a signalling entity. + +# **KEYWORDS** + +| | | +|--------|-----------------------------------------------| +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband Integrated Services Digital Network | +| CPCS | Common Part Convergence Sublayer | +| NNI | Network Node Interface | +| SAAL | Signalling AAL | +| SAP | Service Access Point | +| SAR | Segmentation and Reassembly | +| SSCF | Service Specific Coordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSCS | Service Specific Convergence Sublayer | +| UNI | User-Network Interface | + +###### B-ISDN SIGNALLING ATM ADAPTATION LAYER (SAAL) OVERVIEW DESCRIPTION + +(Geneva, 1994) + +# 1 Scope + +This Recommendation briefly describes the various components which make up the AAL functions necessary to support signalling (SAAL). It is intended to serve as a guide to all other Recommendations required by a user who intends to construct an AAL for the purpose of signalling. + +# 2 Normative references + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of currently valid ITU-T Recommendations is regularly published. + +- Recommendation I.361, *ATM layer specification for B-ISDN*. +- Recommendation I.362, *B-ISDN ATM adaptation layer functional description*. +- Recommendation I.363, *B-ISDN ATM adaptation layer specification*. +- ITU-T Recommendation Q.2110, *B-ISDN ATM Adaptation Layer Service Specific Connection Oriented Protocol (SSCOP)*. +- ITU-T Recommendation Q.2130, *B-ISDN ATM Adaptation Layer Service Specific Coordination Function (SSCF) for signalling at the User Network Interface (UNI)*. +- ITU-T Recommendation Q.2140, *B-ISDN ATM Adaptation Layer Service Specific Coordination Function (SSCF) for signalling at the Network Node Interface (NNI)*. + +# 3 Abbreviations + +For the purposes of this Recommendation, the following abbreviations apply: + +| | | +|------|----------------------------------| +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| CPCS | Common Part Convergence Sublayer | +| NNI | Network Node Interface | +| SAAL | Signalling AAL | +| SAP | Service Access Point | +| SAR | Segmentation And Reassembly | + +| | | +|-------|-----------------------------------------------| +| SSCF | Service Specific Coordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSCS | Service Specific Convergence Sublayer | +| UNI | User-Network Interface | + +# 4 General + +The ATM adaptation layer (AAL) is defined as enhancing the services provided by the ATM layer to support the functions required by the next higher layer. Different AALs support various protocols to suit the different needs of a range of AAL service users. Recommendation I.362 gives an overview of the basic structure of an AAL and the manner in which it aligns with the service class. + +One particular type of AAL service user is the signalling entity wishing to communicate with a peer entity. Any such entity would require that functions are provided above the common part of the AAL specifically designed to facilitate this task. + +The information transfer between the SAAL user and the SAAL is performed in Message Mode. Two peer-to-peer operational procedures may be offered: Unassured or Assured operation. + +# 5 Description of SAAL + +The complete specification of the SAAL is indicated in Figure 1. The SAAL makes use of the service provided by the Common Part Convergence Sublayer (CPCS) and Segmentation and Re-assembly (SAR) which form the common part of AAL type 5. The Service Specific Convergence Sublayer (SSCS) part of AAL type 5 is performed by a combination of the Service Specific Connection Oriented Protocol (SSCOP) and one of several types of Service Specific Coordination Function (SSCF), two of which are currently defined and shown in the figure. The function of the SSCOP is such as to make it equally well suited for use by the user plane. A description of each SAAL component follows. + +## 5.1 SAAL-SAP + +This is the Service Access Point (SAP) through which all SAAL functions are accessed by the next higher layer. It provides bi-directional flow of information. + +Further information regarding this component is found in Recommendations Q.2130 and Q.2140. + +## 5.2 SSCF-UNI + +This is the Service Specific Coordination Function which maps the particular requirements of the UNI layer 3 protocol to the SSCOP services. + +Further information regarding this component is found in Recommendation Q.2130. + +## 5.3 SSCF-NNI + +This is the Service Specific Coordination Function which maps the particular requirements of the NNI layer 3 protocol to the SSCOP services. + +Further information regarding this component is found in Recommendation Q.2140. + +## 5.4 SSCOP + +This is the Service Specific Connection Oriented Protocol function which provides mechanisms for the establishment and release of connections and the reliable exchange of information between peer entities. + +Further information regarding this component is found in Recommendation Q.2110. + +![Diagram of the complete AAL structure for signalling applications. The diagram shows a stack of layers: SAAL SAP at the top, followed by SSCF, SSCOP, CPCS, and SAR. The CPCS and SAR layers are grouped together with a bracket labeled 'See clause 6/I.363'. The bottom of the stack is the ATM SAP. Management planes are indicated on the left: 'Plane Management' and 'Layer Management'. Arrows show data flow between adjacent layers. A note '(Note)' is next to SSCF, and 'Q.2110' is next to SSCOP. The diagram is labeled 'T1153040-93/d01' at the bottom right.](fc46871d72c65d3381d9201646d23439_img.jpg) + +Diagram of the complete AAL structure for signalling applications. The diagram shows a stack of layers: SAAL SAP at the top, followed by SSCF, SSCOP, CPCS, and SAR. The CPCS and SAR layers are grouped together with a bracket labeled 'See clause 6/I.363'. The bottom of the stack is the ATM SAP. Management planes are indicated on the left: 'Plane Management' and 'Layer Management'. Arrows show data flow between adjacent layers. A note '(Note)' is next to SSCF, and 'Q.2110' is next to SSCOP. The diagram is labeled 'T1153040-93/d01' at the bottom right. + +NOTE – SSCF-UNI (see Recommendation Q.2130) or SSCF-NNI (see Recommendation Q.2140). + +FIGURE 1/Q.2100 +**Complete AAL structure for signalling applications** + +## 5.5 CPCS + +This is the Common Part Convergence Sublayer which provides transparent transport of Service Data Units produced by the next higher layer. + +Further information regarding this component is found in clause 6/I.363. + +## 5.6 SAR + +This is the Segmentation and Re-assembly function. It provides the services whereby SAR service data units (SDUs) are segmented to fit into outgoing ATM cells, while incoming cells are reassembled into SAR SDUs and data are passed up to the CPCS. + +Further information regarding this component is found in clause 6/I.363. + +## 5.7 ATM-SAP + +This is the point through which all ATM functions are accessed by the ATM adaptation layer. It provides bidirectional flow of information. + +Further information regarding this component is found in Recommendation I.361. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..090600e4cb730ec53e7e95be6422bc54e394bcf9 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3108295bfb13cfb03f96505702c5782ce62a5378ca5d74de357944a9bba42550 +size 63746 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60ad9ec365bc35bec9b408aa648a3154612a805f --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33d13abafeb6e708d51ed6752125f60b17c1835c5220c77e886d04a2d71e9fa0 +size 174719 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0199f9e8e62129c485c598468de2128f8935a582 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49b2f6a16a6ef1c1262b0500a3a001cac987353c7a4f57e1482fa702ddd82259 +size 152238 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72b06bfd7001f5281cbc0b6b3c5101f97388cb45 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb94e4ef7228bec33fea01f88718d1b68f47bb38dbe9e2fc3627217c979da032 +size 174991 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5bd1715b3a587fc50847d304004966466f21fed --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50a606405f6e113c99bc45a761e9826662fb99db9219576e7043fc02933a015c +size 8297 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22288eebae9e91a70d664050c14225063021ea13 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:599416aa405fc57d1519dce00eb5a527322512887aa0f2aa30307b8a9e6c5808 +size 93274 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a52a4937e4e28545884e791cc32f79a3709f5c1 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d366f8d1ae8aa4a484b3fcc04650ae56a715e8a3120ae3ddfe59e5f6c9d49d38 +size 128503 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..858820f9839cf58814b2b8bf2e1c29acfcee70a2 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12523aee1f50f0a188fffcefdaba189633ef6af8a66347cb065c7acece350842 +size 158285 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57392b998a31731cdfc71c120d3f07ab2953a0e7 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac8aeb7b4c44513e818b9d14e115bcedaccf5e1ed55324a2a3f86312df626359 +size 133649 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4767b6e106f34fe8b63a6838810bf913_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4767b6e106f34fe8b63a6838810bf913_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8f3ae8234f20313ee06b2ac5e03ca5a7b1d7a9b --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/4767b6e106f34fe8b63a6838810bf913_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75f3157fdc2fe4b47fb8a0787db4c41f3604617847f9f746e4a6f00407dd8195 +size 11802 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b44ae2f8c379f6b763c5c3d1ce2e260b9b0d4d28 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e7c3edf40e9d0ec8ee47b84cdd1b211413e455247d8989e9cf99ea4b73cec39 +size 213531 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11d251d1fbc4de21a8765376cb92284508eba98a --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed4094d7872985e60f1c5a396f3cf2aea4843c298fb67c3d8ea8a3e87d15afa +size 180388 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1332dbb08c02349e5ea9356905adb45e5003bb2 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51f8d6e6766c1c457dcbda2457f8527c5f20ab15a5d3d800067186051a30f894 +size 140867 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91c033c64b4206b428e87be94836c5c3fac2e050 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13b14dc881aa9a5896bccf9670c75b64e7258bab907d05329aabcb7cb708a78c +size 88432 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aeb5c5fb010adaad38261c1fb9d3104b0decb3c5 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1749ab1aba0ff9d96768c804b29ff8e231e472f8c7d1357f7fdbbce118e8845a +size 191937 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f7211185277c55ba9d92ff8112e00a7061541d1 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d0fd0a93d216cb2fd4f4da0d513d87e45793cde89f1ae5aa2bd80599a85813a +size 170795 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33421c0fd9db0044c5fc65029cdbed1bd5339ad6 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a4f97cac835c77c31b7851053408d0f7d2de202093e2959a26a126830f45e4 +size 111366 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c8887ac685227c886c08b937eccccce0e20d478 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5c4d3fe33d39b7d21a6a4fd217cfb6ecc9821737b839e3cf94895ffa8724be5 +size 221446 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b6e7f9a2553c01e20998a1e9aa3c8c81ca90a1a --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd4ee685474670be8dcc48c1643eec6dd36929132cc735cfb861f56b5cc9d974 +size 185180 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f5c48bf341307c35020121235dc1b7314f8a5d7 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8971cbedaaac36df664cd21047218b7cd165a8ce374071cf90a60823c7e7ffe +size 80674 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..130976ed33da749bf5f07ca5f97d758afbeaf82e --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69ed73a08524424e8a8991ef64eb124d19e2c191b1c2e49a22bd4d005f5afdf9 +size 190920 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a089a539491416266f8f2c59bba2f4da8e69e40 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1db85c95650909859ceeb13520dd0669695b7c403b1c4fe4aee9b3412119f06 +size 184552 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..487029bbab011eb2b6cfd721865c869b1aa5fe37 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d599d218469ca979fa57b50ac846c7ba30df963a346259d8384d995a297c215 +size 170178 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cd71f4f72fc9000f701dc6484a2b1eaaa7af6c9 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:675b396fbb2334079a5459d0a1963da1fe9e5b58ab4c890c1653c4422ee4b374 +size 176658 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55403188bf227210f646d2691b0966de5ff17971 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9839d81f9b5c9dd5ce60d7fd544a14395c77020b1eee29bd03660f03c45fc3b8 +size 130627 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b1ea1b82c5cd2730b285f42d52044516ba08191 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6a2632e9e52f05523407e5d21802bd90753c7b7d84b05484461f83e7b80a61c +size 134711 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb717911e53a877f52c8eb575f931b1ab1feaa06 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2cbf56fc37d1a8b96ecca6e48090a607848b65f4219836835021102f92e2c4c +size 150553 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/f142b022cfc716cd967297f027efe647_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/f142b022cfc716cd967297f027efe647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f88cf955263d40dcc7dda362a880a6b263039928 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/f142b022cfc716cd967297f027efe647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d85de1415048178b68f23d1096f84cd02e83bb4a267c39d06e96289fefd23ac +size 196735 diff --git a/marked/Q/T-REC-Q.2140-199502-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67b4c8605fcb7c3bd8579646f6d66a7496255b62 --- /dev/null +++ b/marked/Q/T-REC-Q.2140-199502-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4858e3b92555982cb65546fb39075452f60d0e7db75e3babad6d7812cc0a6b36 +size 68253 diff --git a/marked/Q/T-REC-Q.22-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.22-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.22-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.22-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.22-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2f1e5c7952387aecbc7ceb35fbcfb61b85c9fcdb --- /dev/null +++ b/marked/Q/T-REC-Q.22-198811-I_PDF-E/raw.md @@ -0,0 +1,46 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.22** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**FREQUENCIES TO BE USED FOR IN-BAND +SIGNALLING** + +**ITU-T Recommendation Q.22** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.22 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. + +# **FREQUENCIES TO BE USED FOR IN-BAND SIGNALLING** + +To reduce the risk of signal imitation by speech currents, the frequencies for an in-band signalling system should be chosen from the frequencies in the band in which speech signal power is lowest, i.e. frequencies above 1500 Hz. + +The desirability of this was confirmed by tests carried out in London, Paris and Zurich in 1946 and 1948 to choose the signalling frequencies of systems standardized by the CCITT. These tests led to the conclusion that, if relative freedom from false signals was to be obtained other than by undue increase in signal duration, frequencies of at least 2000 Hz would have to be used. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2210-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..597350198bf183a462cef91611cc21dc746957d4 --- /dev/null +++ b/marked/Q/T-REC-Q.2210-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.2210-199607-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..432b377c2ad65887e656d1e520b0c90b57382a9a --- /dev/null +++ b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d78366ca812cabe07739d12452c2ee0bdfd8ce62cbba22cabaa0bdfc5a3f9c26 +size 95677 diff --git a/marked/Q/T-REC-Q.2210-199607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a57aee4d4bfee5013266e287b53bef8fd1ff2783 --- /dev/null +++ b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a921739ecc62d1636671559bd29c75d98c728574926ba7eaafd21aaaf85e8251 +size 242311 diff --git a/marked/Q/T-REC-Q.2210-199607-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6eee6a2a996fb331924dd8efe9e59f0f6798e41 --- /dev/null +++ b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b6276a79d67e99b0641be2723b991dd35f1ebc914491fe3767c2e4ad80b59e8 +size 113235 diff --git a/marked/Q/T-REC-Q.2210-199607-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b553ccc0d5ceb83c63315f00dbc3819e8a0a7650 --- /dev/null +++ b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a7f2b6657de9fe7f0d11f0749e1d6fc93a393ca94fb26d8e5e138ea536f6114 +size 33829 diff --git a/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02840612e3b4080e9fb0c8581f5d23d3c824bba9 --- /dev/null +++ b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68c1563156ab073aeabc379a914594b33a910e640325e481cbd742ece918d447 +size 66032 diff --git a/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce08b39e3d8b0ce95276552563c5c07362f51982 --- /dev/null +++ b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a74118554048622fc41efe12bea6f9c89fbdab18104adeb1c9e6dffb81fc94c6 +size 103073 diff --git a/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..877f60d77c0d4f7782636a161707b7d75e7ede8f --- /dev/null +++ b/marked/Q/T-REC-Q.2210-199607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd61d5005acb894f40c3efdab00b46d19469ae3d6bc18a5ca510692968dac244 +size 65741 diff --git a/marked/Q/T-REC-Q.23-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.23-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.23-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.23-198811-I_PDF-E/61d9180e505c3366d5ad3dd72408f6fe_img.jpg b/marked/Q/T-REC-Q.23-198811-I_PDF-E/61d9180e505c3366d5ad3dd72408f6fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c58fc67fe0077f20e4dbb75813d995d76f47ae1 --- /dev/null +++ b/marked/Q/T-REC-Q.23-198811-I_PDF-E/61d9180e505c3366d5ad3dd72408f6fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:657aa45fee867c9f8b7a2de9d77991798ea70b81aaa1c0d3ba093a7782380eb7 +size 39847 diff --git a/marked/Q/T-REC-Q.23-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.23-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7f22ea38567f233575f972cddfde3f62dc60a926 --- /dev/null +++ b/marked/Q/T-REC-Q.23-198811-I_PDF-E/raw.md @@ -0,0 +1,107 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.23** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**TECHNICAL FEATURES OF PUSH-BUTTON +TELEPHONE SETS** + +**ITU-T Recommendation Q.23** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.23 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. + +## Recommendation Q.23 + +# TECHNICAL FEATURES OF PUSH-BUTTON TELEPHONE SETS + +1 The introduction of push-buttons on telephone sets may have an effect on the operation of international circuits: + +- a) owing to the greater dialling speed, the post-dialling may be longer, since national and international networks will only be gradually adapted to allow for this greater speed; +- b) when pressing the buttons after an international call has been set up, the signalling frequencies for push-button sets may cause interference to foreign signalling systems on the connection. However, the subscriber can be warned of the possible disadvantages of touching the buttons in conditions different from those prescribed. + +2 There can be no doubt that, owing to the high dialling speed which can be obtained with push-button sets, their use is bound to spread widely and rapidly and it is desirable for the signalling methods for such sets to be internationally standardized. + +One factor in favour of such standardization is the advantage it offers for countries which have to import their equipments from various other countries. This argument, admittedly, applies to any type of telephone equipment. + +Other advantages of standardization are: + +- the possibility of using the push-button of such sets for signalling directly from one subscriber to another subscriber via a national and/or international connection; +- the standardized allocation of signalling frequencies for push-button sets facilitates the choice of signalling frequencies in the frequency band of a telephone circuit for any other use (data transmission, telephone signalling system, etc.) for which provision might have to be made. The risk of mutual interference among the signalling systems (see Recommendation Q.25) makes it necessary to have an orderly arrangement of the spectrum of frequencies used for signalling. + +3 The general use of push-button sets for purposes other than telephone dialling is envisaged by some Administrations. However, some Administrations observe that it would seem advisable to reserve such uses for a network of relatively limited extent; in their view the reliability of standards for data transmission should not make any demands on the push-button set system other than those required for the transmission of telephone numerical information to the local exchange, if the design of push-button sets is to remain within economical limits compatible with their widespread use. + +However, the CCITT considered, at Mar del Plata in 1968 that, even if the transmission of data from a push-button telephone set is at present to be envisaged in international traffic on a limited scale only, it would nonetheless be wise not to rule out the possibility of such transmission of data on a general scale. + +4 In choosing a signalling system for push-button sets, Administrations may be guided by conditions which vary considerably from one country to another. Economic considerations may, for instance, lead them to prefer a direct current system which might be less expensive than a voice-frequency system. The numerical dialling information would then be transmitted only as far as the telephone exchange to which the subscriber is connected. There are no tones that could affect the connection after its establishment. Data would not be transmitted from the push-button sets unless a suitable converter were used in the exchange. + +Standardization of a direct current system for signalling from push-button sets does not seem justified at the international level; it may depend on the conditions peculiar to the local networks of the country concerned. + +5 The signalling system for push-button sets recommended by the CCITT applies solely to voice-frequency signals. + +A multifrequency code for such signalling is recommended in which the dialling signal is composed of two frequencies emitted simultaneously when a button is pressed. It is planned to have 10 decimal digits and 6 reserve signals, making 16 signals in all. The two frequencies composing each signal are taken from two mutually exclusive frequency groups of four frequencies each, a code known as the "2 (1/4) code". + +6 The low group frequencies of this 2 (1/4) code are: + +697, 770, 852, 941 Hz. + +The high group frequencies are: + +1209, 1336, 1477 and 1633 Hz. + +The allocation of frequencies to the various digits and symbols of a push-button set appears in Figure 1/Q.23. + +7 The frequency variation tolerances and the permissible intermodulation products are defined as follows: + +7.1 each transmitted frequency must be within $\pm 1.8\%$ of the nominal frequency; + +7.2 the total distortion products (resulting from harmonics or intermodulation) must be at least 20 dB below the fundamental frequencies. + +8 The CCITT determined, at Mar del Plata in 1968, that it was not practicable to specify a standardization of the levels for the frequencies transmitted when a push-button is pressed, as these level conditions depend essentially on national transmission plans which are not the same in all countries. + +However, the sending level conditions must be such that on an international connection they do not exceed the values specified in Recommendation Q.16 (maximum permissible value for the absolute power level of a signalling pulse). + +![Diagram showing the allocation of frequencies to digits and symbols on a push-button set. It is a grid with 4 columns for high group frequencies (1209, 1336, 1477, 1633 Hz) and 4 rows for low group frequencies (697, 770, 852, 941 Hz). The grid contains digits 1-9, 0, *, and letters A, B, C, D.](61d9180e505c3366d5ad3dd72408f6fe_img.jpg) + +| Low group frequencies (Hz) | High group frequencies (Hz) | | | | +|----------------------------|-----------------------------|------|------|------| +| | 1209 | 1336 | 1477 | 1633 | +| 697 | 1 | 2 | 3 | A | +| 770 | 4 | 5 | 6 | B | +| 852 | 7 | 8 | 9 | C | +| 941 | * | 0 | # | D | + +CCITT-48430 + +Diagram showing the allocation of frequencies to digits and symbols on a push-button set. It is a grid with 4 columns for high group frequencies (1209, 1336, 1477, 1633 Hz) and 4 rows for low group frequencies (697, 770, 852, 941 Hz). The grid contains digits 1-9, 0, \*, and letters A, B, C, D. + +**FIGURE 1/Q.23** +**Allocation of frequencies to the various digits and symbols of a push-button set** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.24-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.24-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9dd8da974838247830164a4328a54d1b10b92a05 --- /dev/null +++ b/marked/Q/T-REC-Q.24-198811-I_PDF-E/raw.md @@ -0,0 +1,115 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.24** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**MULTIFREQUENCY PUSH-BUTTON SIGNAL +RECEPTION** + +**ITU-T Recommendation Q.24** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation Q.24 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. + +# **MULTIFREQUENCY PUSH-BUTTON SIGNAL RECEPTION** + +## **1 Introduction** + +Characteristics of multifrequency push-button (MFPB) telephone sets using voice frequency signals are included in Recommendation Q.23. This Recommendation Q.24 is intended primarily for application in local exchanges for the reception of MFPB signals. Other MFPB signal receiving applications, such as transit exchanges, would need to take into account the effects of transmission impairments, such as signal clipping, that could be introduced in long distance telephone networks. Since technical factors, such as transmission loss, vary among national networks, varying national standards exist. Varying standards may also exist, for example, to incorporate differences between local and transit exchange applications. This Recommendation is not intended to supersede existing national standards nor is it intended to imply that Administrations should modify those standards. + +## **2 Technical parameters** + +### **2.1 General** + +The technical parameters identified herein are fundamental to the MFPB receiving function and reasons are given for the importance of each parameter. The parameters require operational values to be specified for compatibility with the MFPB sending equipment (Recommendation Q.23) and the network environment in which the receiving equipment must function. Annex A contains a Table showing values for some of these parameters that have been adopted by various Administrations and RPOAs. In addition to the fundamental parameters covered by this Recommendation, Administrations should consider whether other parameters need specification to account for operating conditions found in their networks. + +### **2.2 Signal frequencies** + +Each signal consists of two frequencies taken from two mutually exclusive frequency groups (a high group and a low group) of four frequencies each, as specified in Recommendation Q.23. These frequencies and their allocation to form the various digits and symbols of the push-button signalling code are defined in Recommendation Q.23. The exchange shall provide a check for the simultaneous presence of one and only one frequency from the high group and one and only one from the low group. + +### **2.3 Frequency tolerances** + +The exchange should respond to signals whose frequencies are within the tolerances for MFPB sending. Somewhat wider tolerances may be appropriate, for example to cater for transmission impairments encountered in subscriber cables or FDM transmission facilities. However, wider limits may increase susceptibility to noise and digit simulation by speech. + +### **2.4 Power levels** + +The exchange should provide proper reception of signals whose power levels are determined by the amplitude of the sending equipment and loss that may be introduced by the subscriber cables or other network elements. The sending amplitude and transmission attenuation may be different for different frequencies. The reception characteristics may take advantage of a limitation, if specified, on the maximum difference in power level between the two received frequencies forming a valid signal to facilitate improved overall performance. + +### **2.5 Signal reception timing** + +The exchange should recognize signals whose duration exceeds the minimum expected value from subscribers. To guard against false signal indications the exchange should not respond to signals whose duration is less than a specified maximum value. Similarly, pause intervals greater than a specified minimum value should be recognized by the exchange. To minimize erroneous double-registration of a signal if reception is interrupted by a short break in transmission or by a noise pulse, interruptions shorter than a specified maximum value must not be recognized. The + +maximum rate at which signals can be received (signalling velocity) may be related to the above minimum values. All of these values may also be determined by subscriber feature requirements. + +### 2.6 *Signal simulation by speech* + +Because telephone set speech transmitters are normally connected in the circuit during the push-button dialling interval, it is necessary for the exchange to properly receive valid MFPB signals in the presence of voice or other disturbances. The nature of such disturbances may vary from one geographical area to another. The number of calls affected by signal simulation should not significantly degrade the overall telephone network performance experienced by subscribers. + +Since actual immunity to digit simulation may be difficult to measure, a test environment using recorded speech, music, and other voice frequency sounds may be utilized to verify design performance. + +### 2.7 *Interference by dial tone* + +MFPB reception should not be adversely affected while dial tone is being applied. Characteristics of dial tone such as frequencies, power levels and spurious components are covered in Recommendation Q.35. These characteristics are specified to minimize the interference between the dial tone sending and the MFPB receiving functions. These functions are normally provided by closely related exchange equipment which must be designed to function properly over the entire range of signal characteristics and transmission impairments to be encountered. + +### 2.8 *Interference by echos* + +MFPB signal reception from extended subscriber lines having long 4-wire transmission sections must discriminate between a true signal condition and an echo condition which may persist for a number of milliseconds. Failure to provide such discrimination could result in signal reception errors, for example due to a reduction of the detected pause duration. Administrations having such extended subscriber lines with MFPB signalling should therefore specify the echo conditions under which the MFPB signalling function must operate. + +### 2.9 *Noise immunity* + +Noise sources such as power lines, electric railways and telecommunication circuits may induce electrical disturbances with various characteristics into MFPB signalling paths. These disturbances may cause MFPB signals to be missed, split (double signal registration) or cause signal simulation. The distortion products produced by the MFPB signalling source should also be included in the noise environment. A realistic noise environment specification and facilities for testing MFPB reception under the specified conditions, e.g., using recorded test tapes, are important to ensure that performance standards will be met under actual service conditions. + +## ANNEX A (to Recommendation Q.24) + +TABLE A-1/Q.24 +**Values of multi-frequency push-button receiving parameters adopted by various Administrations/RPOAs** + +| Parameters | | Values | | | | | | +|--------------------------------------------|---------------------|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------------------|----------------------------------------------------------------|--------------------| +| | | NTT | AT&T | Danish Administration a) | Australian Administration | Brazilian Administration | | +| Signal frequencies | Low group | 697, 770, 852, 941 Hz | same as left column | same as left column | same as left column | same as left column | | +| | High group | 1209, 1336, 1477, 1633 Hz | | | | | | +| Frequency tolerance
$ \Delta f $ | Operation | $\leq 1.8\%$ | $\leq 1.5\%$ | $\leq (1.5\% + 2 \text{ Hz})$ | $\leq (1.5\% + 4 \text{ Hz})$ | $\leq 1.8\%$ | | +| | Non-operation | $\geq 3.0\%$ | $\geq 3.5\%$ | | $\geq 7\%$ | $\geq 3\%$ | | +| Power levels per
frequency | Operation | -3 to -24 dBm | 0 to -25 dBm | (A + 25) to A dBm | -5 to -27 dBm | -3 to -25 dBm | | +| | Non-operation | Max. -29 dBm | Max. -55 dBm | Max. (A - 9) dBm (A = -27) | Max. -30 dBm | Max. -50 dBm | | +| Power level difference between frequencies | | Max. 5 dB | +4 dB to -8 dB b) | Max. 6 dB | Max. 10 dB | Max. 9 dB | | +| Signal reception
timing | Signal
duration | Operation | Min. 40 ms | Min. 40 ms | Min. 40 ms | Min. 40 ms | Min. 40 ms | +| | | Non-Operation | Max. 24 ms | Max. 23 ms | Max. 20 ms | Max. 25 ms | Max. 20 ms | +| | Pause duration | | Min. 30 ms | Min. 40 ms | Min. 40 ms | Min. 70 ms | Min. 30 ms | +| | Signal interruption | | Max. 10 ms c) | Max. 10 ms | Max. 20 ms | Max. 12 ms | Max. 10 ms | +| | Signalling velocity | | Min. 120 ms/digits | Min. 93 ms/digit | Min 100 ms/digit | Min. 125 ms/digit | Min. 120 ms/digits | +| Signal simulation by speech | | 6 false/46 hours for speech
with a mean level of
-15 dBm | For the codes 0-9,
1 false/3000 calls
For the codes 0-9, *, #,
1 false/2000 calls
For the codes 0-9,
*, # A-D,
1 false/1500 calls | 46 false/100 hours for
speech with a mean level
of -12 dBm | | 5 false/50 hours for speech
with a mean level of
-13 dBm | | +| Interference by echos | | | Should tolerate echos
delayed up to 20 ms and
at least 10 dB down | | | | | + +- a) Same characteristics are used by several European Administrations; Values of A range from -22 to -30 to suit national conditions. +b) The high group frequency power level may be up to 4 dB more or 8 dB less than the low group frequency power level. +c) For analogue multifrequency push-button receivers only. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.25-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.25-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.25-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.2630.3-200310-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..098bebbdcc9042102fa6a9ac4b70ff68142ada9c --- /dev/null +++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/raw.md @@ -0,0 +1,6039 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2630.3** + +(10/2003) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – Common aspects of B-ISDN +application protocols for access signalling and network +signalling and interworking + +--- + +**AAL type 2 signalling protocol – Capability Set 3** + +ITU-T Recommendation Q.2630.3 + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|---------------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| 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.2630.3** + +# **AAL type 2 signalling protocol – Capability Set 3** + +# **Summary** + +This Recommendation specifies the inter-node protocol and nodal functions that control AAL type 2 point-to-point connections. + +The AAL type 2 signalling protocol specified in this Recommendation is usable in switched and non-switched environments and can operate in public or private networks over a range of signalling transport protocol stacks. + +It also provides maintenance capabilities, carriage of user-plane protocol stack information and carriage of an identifier to link the connection control protocol with other higher layer control protocols. + +## **Source** + +ITU-T Recommendation Q.2630.3 was approved on 14 October 2003 by ITU-T Study Group 11 (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 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..... | 3 | +| 3 | Definitions ..... | 3 | +| 4 | Abbreviations..... | 5 | +| 5 | General framework of the AAL type 2 signalling protocol..... | 9 | +| 5.1 | Interface between the AAL type 2 signalling entity and the AAL type 2 served user ..... | 11 | +| 5.2 | Interface between the AAL type 2 signalling entity and the generic signalling transport ..... | 15 | +| 5.3 | Interface between the AAL type 2 signalling entity and layer management..... | 16 | +| 6 | Forward and backward compatibility ..... | 18 | +| 6.1 | Backward compatibility rules..... | 18 | +| 6.2 | Forward compatibility mechanism ..... | 18 | +| 7 | Format and coding of AAL type 2 signalling protocol..... | 19 | +| 7.1 | Coding conventions for the AAL type 2 signalling protocol ..... | 19 | +| 7.2 | Format and coding of the AAL type 2 signalling protocol messages ..... | 21 | +| 7.3 | Parameter specification of the AAL type 2 signalling protocol messages..... | 26 | +| 7.4 | Field specification of the AAL type 2 signalling protocol parameters ..... | 34 | +| 8 | Procedure of the AAL type 2 signalling protocol..... | 47 | +| 8.1 | Compatibility ..... | 48 | +| 8.2 | Nodal functions ..... | 52 | +| 8.3 | Protocol entity ..... | 75 | +| 8.4 | List of timers..... | 102 | +| Annex A | – Support for non-switched scenario ..... | 102 | +| A.1 | Introduction ..... | 102 | +| A.2 | References ..... | 103 | +| A.3 | Definitions ..... | 103 | +| A.4 | Abbreviations ..... | 103 | +| A.5 | General framework of the AAL type 2 signalling protocol ..... | 103 | +| A.6 | Forward and backward compatibility ..... | 105 | +| A.7 | Format and coding of AAL type 2 signalling protocol ..... | 105 | +| A.8 | Procedure of the AAL type 2 signalling protocol ..... | 108 | + +| | Page | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Annex B – Coding of the compatibility information ..... | 111 | +| B.1    Coding of the compatibility information for CS-1 and CS-2 networks
using link characteristics for connection resource allocation..... | 111 | +| B.2    Coding of the compatibility information for CS-1 and CS-2 networks
using service specific information for connection resource allocation ..... | 113 | +| B.3    Coding of the compatibility information of the new parameters for CS-1
and CS-2 networks ..... | 114 | +| Annex C – Interworking with CS-1 and CS-2 nodes for connection resource allocation ..... | 116 | +| C.1    Connection resources indicated with link characteristic parameters..... | 116 | +| C.2    Connection resources indicated with service specific information
parameters..... | 120 | +| C.3    Service Specific Information indicated with SSCS information
parameters..... | 124 | +| Annex D – SDL Definition of the AAL type 2 Signalling Protocol..... | 126 | +| Appendix I – Example message sequences..... | 127 | +| I.1    Successful establishment and release ..... | 127 | +| I.2    Unsuccessful establishment..... | 128 | +| I.3    Management message sequences ..... | 128 | +| I.4    Release crossover/release collision ..... | 129 | +| I.5    Resource contention ..... | 130 | +| I.6    Successful modification..... | 131 | +| I.7    Unsuccessful modification ..... | 131 | +| I.8    Modification Collision..... | 132 | +| Appendix II – Conversion of CS-1 or CS-2 (Preferred) Link Characteristics to
(Preferred) Transfer Capability parameters ..... | 132 | +| II.1   Guidelines and definitions..... | 132 | +| II.2   Bit rates..... | 134 | +| II.3   Maximum allowed packet sizes..... | 135 | +| II.4   Token bucket sizes ..... | 136 | +| II.5   Determination of the TC class ..... | 136 | +| II.6   Source traffic type ..... | 136 | +| Appendix III – Interworking examples..... | 137 | +| III.1  Symbols and abbreviations..... | 137 | +| III.2  Connection Establishment ..... | 138 | +| III.3  Connection Resource Modification ..... | 148 | + +# **AAL type 2 signalling protocol – Capability Set 3** + +# **1 Scope** + +This Recommendation describes the AAL type 2 signalling protocol that supports the dynamic establishment and release of individual AAL type 2 point-to-point connections. It also describes the maintenance procedures, the framework of the protocol, and the interactions between an AAL type 2 signalling protocol entity and: + +- the signalling protocol user; +- a signalling transport converter; and +- layer management. + +This Recommendation also describes the connection states, messages, parameters, timers, local, and peer-to-peer procedures used for the control of those connections. The scope of this Recommendation is illustrated in Figure 1-1. The AAL type 2 signalling protocol can be deployed over a range of signalling transport protocol stacks. + +This Recommendation is based on the requirements defined in ITU-T Q-series Recommendations – Supplement 42 [21] "Signalling Requirements for AAL type 2 Link Control Capability Set 3". + +![Functional architecture of the AAL type 2 signalling diagram showing two symmetric stacks. Each stack consists of an AAL type 2 served user (top), an AAL type 2 signalling entity, a Signalling transport converter, and a Signalling transport entity (bottom). The AAL type 2 signalling entity is connected to the user via SAPs and primitives, to the converter via generic primitives, and to layer management via SAPs and primitives. A dashed line labeled 'This Recommendation (Note 1)' encloses the AAL type 2 signalling entities and their associated SAPs. A dashed line labeled 'AAL type 2 signalling messages' connects the two signalling entities. Note 2 indicates that the AAL type 2 served user may not be present in some cases.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +Detailed Diagram Description: The diagram illustrates the functional architecture of AAL type 2 signalling. It features two identical vertical stacks representing peer entities. Each stack, from top to bottom, includes: 'AAL type 2 served user' (Note 2), 'AAL type 2 signalling', 'Signalling transport converter', and 'Signalling transport'. These layers interact through Service Access Points (SAPs) and Primitives. Specifically, 'AAL type 2 signalling' interacts with the 'AAL type 2 served user' via SAPs and Primitives, and with the 'Signalling transport converter' via 'Generic primitives'. The 'Signalling transport converter' interacts with 'Signalling transport' via 'Specific primitives' and SAPs. On the far left and right, 'Layer management' blocks interact with the 'AAL type 2 signalling' layer via SAPs and Primitives. A large gray dashed box labeled 'This Recommendation (Note 1)' encloses the 'AAL type 2 signalling' blocks and their immediate SAP interfaces. A horizontal dashed line labeled 'AAL type 2 signalling messages' connects the two 'AAL type 2 signalling' blocks. At the bottom, a dashed line connects the two 'Signalling transport' blocks, indicating the physical or lower-layer connection. + +Functional architecture of the AAL type 2 signalling diagram showing two symmetric stacks. Each stack consists of an AAL type 2 served user (top), an AAL type 2 signalling entity, a Signalling transport converter, and a Signalling transport entity (bottom). The AAL type 2 signalling entity is connected to the user via SAPs and primitives, to the converter via generic primitives, and to layer management via SAPs and primitives. A dashed line labeled 'This Recommendation (Note 1)' encloses the AAL type 2 signalling entities and their associated SAPs. A dashed line labeled 'AAL type 2 signalling messages' connects the two signalling entities. Note 2 indicates that the AAL type 2 served user may not be present in some cases. + +Q.2630.3\_F1-1 + +NOTE 1 – The entities and Service Access Points (SAP) bounded by the gray broken line indicate the extent of the definitions specified in this Recommendation. + +NOTE 2 – There are cases where the AAL type 2 served user is not present. + +**Figure 1-1/Q.2630.3 – Functional architecture of the AAL type 2 signalling** + +# 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 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 I.363.2 (2000), *B-ISDN ATM adaptation layer specification: Type 2 AAL*. +- [2] ITU-T Recommendation I.361 (1999), *B-ISDN ATM layer specification*. +- [3] ITU-T Recommendation X.200 (1994) ISO/IEC 7498-1:1994, *Information technology – Open Systems Interconnection – Basic Reference Model: The basic model*. +- [4] ITU-T Recommendation X.210 (1993) | ISO/IEC 10731:1994, *Information technology – Open Systems Interconnection – Basic Reference Model: Conventions for the definition of OSI services*. +- [5] ITU-T Recommendation X.213 (2001) | ISO/IEC 8348:2002, *Information technology – Open Systems Interconnection – Network service definition*. +- [6] ITU-T Recommendation Q.850 (1998), *Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part*. +- [7] ITU-T Recommendation Q.2610 (1999), *Usage of cause and location in B-ISDN user part and DSS2*. +- [8] ITU-T Recommendation I.366.2 (1999), *AAL type 2 service specific convergence sublayer for trunking*. +- [9] ITU-T Recommendation I.366.1 (1998), *Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2*. +- [10] ITU-T Recommendation E.164 (1997), *The international public telecommunication numbering plan*. +- [11] IEEE Standard 802-2001, *IEEE Standards for Local and Metropolitan Area Networks: Overview and Architecture*. +- [12] ITU-T Recommendation Q.2150.0 (2001), *Generic signalling transport service*. +- [13] ITU-T Recommendation I.356 (2000), *B-ISDN ATM layer cell transfer performance*. +- [14] ITU-T Recommendation I.366.2 (2000), *AAL type 2 service specific convergence sublayer for narrow-band services*. +- [15] ITU-T Recommendation Q.2630.1 (1999), *AAL type 2 signalling protocol – Capability Set 1*. +- [16] ITU-T Recommendation Q.2630.2 (2000), *AAL type 2 signalling protocol – Capability Set 2*. +- [17] ITU-T Recommendation E.412 (2003), *Network management controls*. + +- [18] ITU-T Recommendation Q.542 (1993), *Digital exchange design objectives – Operations and maintenance*. +- [19] ITU-T Recommendation I.378 (2002), *Traffic control and congestion control at the ATM Adaptation Layer Type 2*. + +## 2.2 Informative references + +The documents listed in this clause provide informative background information for the reader and are not normative within this Recommendation. + +- [21] ITU-T Q-series Recommendations – Supplement 42 (2003), *Technical Report TRQ.2402: Transport control signalling requirements – Signalling requirements for AAL type 2 link control Capability Set 3*. +- [22] ITU-T Recommendation Q.2150.1 (2001), *Signalling transport converter on MTP3 and MTP3b*. +- [23] ITU-T Recommendation Q.2150.2 (2001), *Signalling transport converter on SSCOP and SSCOPMCE*. +- [24] ITU-T Recommendation Q.2210 (1996), *Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140*. +- [25] ITU-T Recommendation Q.2110 (1994), *B-ISDN ATM adaptation layer – Service Specific Connection Oriented Protocol (SSCOP)*. +- [26] ITU-T Recommendation Q.2130 (1994), *B-ISDN signalling ATM adaptation layer – Service specific coordination function for support of signalling at the user-network interface (SSCF at UNI)*. +- [27] ITU-T Recommendation Q.2941.2 (1999), *Digital Subscriber Signalling System No. 2 – Generic identifier transport extensions*. +- [28] ITU-T Recommendation Q.2150.3 (2002), *Signalling transport converter on SCTP*. +- [29] ITU-T Recommendation Q.2140 (1995), *B-ISDN ATM adaptation layer – Service specific coordination function for signalling at the network node interface (SSCF at NNI)*. +- [30] ETSI TS 126 103 V 5.1.0 (2002), *Universal Mobile Telecommunications System (UMTS); Speech codec list for GSM and UMTS (3GPP TS 26.103 version 5.1.0 Release 5)*. + +# 3 Definitions + +This Recommendation is based upon the concepts developed in ITU-T Recs X.200 [3] and X.210 [4]. + +In addition, for the purposes of this Recommendation, the following definitions apply: + +**3.1 AAL type 2 channel:** A concept used in ITU-T Rec. I.363.2 [1] to describe transport of CPS-packets [1] associated in a common unique identifier value called CID on an ATM VCC. + +**3.2 AAL type 2 connection:** The logical concatenation of one or more AAL type 2 links between two AAL type 2 service endpoints. + +**3.3 AAL type 2 connection resource:** Describe the attributes of the AAL type 2 links making up the connection, and the Service Specific Convergence Sublayer resources used at the AAL type 2 service endpoints. + +**3.4 AAL type 2 link:** The logical user plane communication facility between two adjacent AAL type 2 switching points or service endpoints. An AAL type 2 link is designated by a single CID value. + +**3.5 AAL type 2 link characteristics:** Information that describes the attributes of the AAL type 2 link. + +NOTE – In this Recommendation, AAL type 2 link characteristics are only used for backward compatibility, i.e., for interworking with AAL type 2 nodes that conform only to ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16] (see Annex C). + +**3.6 AAL type 2 node:** An AAL type 2 service endpoint or an AAL type 2 switch. + +**3.7 AAL type 2 path:** An ATM VCC between two adjacent AAL type 2 nodes. This ATM VCC can either be an SVC, SPVC or PVC. + +**3.8 AAL type 2 path identifier:** The identifier of the AAL type 2 path. + +**3.9 AAL type 2 requested path type:** Information that describes the AAL type 2 path type. These path types may be "stringent class", "tolerant class", or "stringent bi-level class" (see ITU-T Rec. I.356 [13]). + +**3.10 AAL type 2 service endpoint:** A termination point of an AAL type 2 connection. + +**3.11 AAL type 2 served user:** The user of an AAL type 2 signalling protocol. + +**3.12 AAL type 2 signalling protocol:** Control plane functions for establishing and releasing AAL type 2 connections and the maintenance functions associated with the AAL type 2 signalling. + +**3.13 AAL type 2 signalling transport:** A facility for carrying AAL type 2 signalling messages. + +**3.14 AAL type 2 signalling endpoint:** The termination point of an AAL type 2 signalling transport. + +**3.15 AAL type 2 switch:** A system capable of switching AAL type 2 connections. + +**3.16 AAL type 2 transfer capability:** Information that describes the attributes of the AAL type 2 link according to ITU-T Rec. I.378 [19]. + +NOTE – The attributes of the AAL type 2 link as described by AAL type 2 transfer capability parameters are intended to replace the attributes of the AAL type 2 link as described by AAL type 2 link characteristics parameters. The AAL type 2 transfer capability may describe the attributes of the AAL type 2 link in greater detail than the AAL type 2 link characteristics. + +**3.17 ATM layer signalling:** Control plane functions for establishing, clearing and maintaining ATM VCCs. + +**3.18 ATM VCC:** The logical concatenation of one or more ATM virtual channel links between two ATM service endpoints. + +**3.19 Connection resource:** (see AAL type 2 connection resource.) + +**3.20 CS-1 node:** An AAL type 2 node conforming to capability set 1 (see ITU-T Rec. Q.2630.1 [15]). + +**3.21 CS-1 service endpoint:** An AAL type 2 service endpoint conforming to capability set 1 (see ITU-T Rec. Q.2630.1 [15]). + +**3.22 CS-1 switch:** An AAL type 2 switch conforming to capability set 1 (see ITU-T Rec. Q.2630.1 [15]). + +**3.23 CS-2 node:** An AAL type 2 node conforming to capability set 2 (see ITU-T Rec. Q.2630.2 [16]). + +**3.24 CS-2 service endpoint:** An AAL type 2 service endpoint conforming to capability set 2 (see ITU-T Rec. Q.2630.2 [16]). + +**3.25 CS-2 switch:** An AAL type 2 switch conforming to capability set 2 (see ITU-T Rec. Q.2630.2 [16]). + +- 3.26 CS-3 node:** An AAL type 2 node, switch, or service endpoint conforming to capability set 3 (defined in this Recommendation). +- 3.27 CS-3 service endpoint:** An AAL type 2 service endpoint conforming to capability set 3 (defined in this Recommendation). +- 3.28 CS-3 switch:** An AAL type 2 switch conforming to capability set 3 (defined in this Recommendation). +- 3.29 field:** Information carried in a parameter in a message. A field can have fixed or variable length data. +- 3.30 generic signalling transport:** The function that enables an AAL type 2 signalling entity to communicate with a peer AAL type 2 signalling entity independently of the underlying signalling transport. +- 3.31 link associated signalling relationship:** A logical signalling relationship that is established during AAL type 2 connection establishment between two protocol entities in adjacent AAL type 2 nodes associated with the AAL type 2 link as part of the connection. A link associated signalling relationship is uniquely identified by a pair of Signalling Association Identifiers (Originating and Destination) within a signalling transport association and for the time the link exists. +- 3.32 link characteristics:** (See AAL type 2 link characteristics.) +- 3.33 network default stringent QoS class:** A stringent QoS class as defined in ITU-T Rec. I.356 [13] and as deployed in a network operating with signalling defined in ITU-T Rec. Q.2630.1 [15]. +- 3.34 nodal function:** The functions that provide the bridge between incoming and outgoing protocol entities, perform the routing, and keep track of the AAL type 2 path resources. +- 3.35 parameter:** Information carried in a message. A parameter has a fixed, defined set of fields. +- 3.36 path identifier:** See AAL type 2 path identifier. +- 3.37 protocol entity:** The functions performed within an AAL type 2 signalling entity that relate to the exchange of AAL type 2 signalling information. +- 3.38 requested path type:** (See AAL type 2 requested path type.) +- 3.39 signalling transport association:** A signalling capability that exists between two adjacent AAL type 2 nodes to control the AAL type 2 connections that may exist in one or more AAL type 2 paths. There may be one or more signalling transport associations between two adjacent AAL type 2 nodes. +- 3.40 signalling transport:** A signalling link or network that connects two AAL type 2 nodes. +- 3.41 signalling transport converter:** A function that converts the services provided by a particular signalling transport to the services required by the generic signalling transport. +- 3.42 subfield:** The smallest unit of information in a field that has its own functional meaning. +- 3.43 transfer capability:** (See AAL type 2 transfer capability.) + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|----------------------------| +| A2P | AAL type 2 Path Identifier | +| A2SU | AAL type 2 Served User | +| AAL | ATM Adaptation Layer | + +| | | +|---------|---------------------------------------------------------------| +| ACC | Automatic Congestion Control | +| AESA | ATM End System Address | +| AMR | Adaptive Multi-rate Codec | +| ANI | Adjacent AAL type 2 Node Identifier | +| ATM | Asynchronous Transfer Mode | +| ATM VCC | ATM Virtual Channel Connection | +| BCD | Binary Coded Decimal | +| BLC | Block Confirm Message | +| BLO | Block Request Message | +| CAS | Channel Associated Signalling | +| CAU | Cause Parameter | +| CEID | AAL type 2 Connection Element Identifier | +| CFN | Confusion Message | +| CID | Channel Identifier | +| CMD | Circuit Mode Data | +| CP | Connection Priority | +| CPHL | CPS Packet Header Overhead Length | +| CPS | (AAL type 2) Common Part Sublayer | +| CS | Capability Set | +| CS-1 | Capability Set 1 (ITU-T Rec. Q.2630.1 [15]) | +| CS-2 | Capability Set 2 (ITU-T Rec. Q.2630.2 [16]) | +| CS-3 | Capability Set 3 (this Recommendation) | +| DA2EA | Destination AAL type 2 Service Endpoint Address (Note 1) | +| DESEA | Destination E.164 Service Endpoint Address Parameter (Note 1) | +| DNSEA | Destination NSAP Service Endpoint Address Parameter (Note 1) | +| DSAID | Destination Signalling Association Identifier | +| DTMF | Dual Tone Multi-Frequency | +| ECF | Establish Confirm Message | +| ERQ | Establish Request Message | +| FAX | Demodulated Facsimile Data | +| FBW | Fixed Bandwidth Transfer Capability | +| FRM | Frame Mode Data | +| GST | Generic Signalling Transport | +| HBx | Header Bit Rate associated with x | +| HC | Hop Counter | +| ID | Identifier | + +| | | +|--------|-------------------------------------------------------------| +| IEC | International Electrotechnical Commission | +| IEEE | Institute of Electrical and Electronics Engineers | +| ISO | International for Standardization Organization | +| LB | Loopback | +| LC | Link Characteristics (Note 2) | +| LM | Layer Management | +| LSB | Least Significant Bit | +| M | Mandatory | +| MF-R1 | Multi-Frequency R1 | +| MF-R2 | Multi-Frequency R2 | +| MOA | Modification Acknowledge message | +| MOD | Modification Request message | +| MOR | Modification Reject message | +| MSB | Most Significant Bit | +| MSLC | Modify Support for Link Characteristics | +| MSSSI | Modify Support for SSCS Information | +| MTP3b | Message Transfer Part level 3 using ITU-T Rec. Q.2140 [29] | +| NF | Nodal Function | +| NNI | Network-Network Interface | +| NSAP | Network Service Access Point | +| O | Optional | +| OA2EA | Origination AAL type 2 Service Endpoint Address | +| OESEA | Origination E.164 Service Endpoint Address Parameter | +| ONSEA | Origination NSAP Service Endpoint Address Parameter | +| OSAID | Originating Signalling Association Identifier (Parameter) | +| OUI | Organizational Unique Identifier | +| PFBW | Preferred FBW | +| PLC | Preferred Link Characteristics | +| PSSCS | Preferred SSCS Information | +| PSSIAE | Preferred Service Specific Information (Audio Extended) | +| PSSIME | Preferred Service Specific Information (Multirate Extended) | +| PT | Path Type | +| PTC | Preferred Transfer Capability | +| PVBWS | Preferred VBWS | +| PVBWT | Preferred VBWT | + +| | | +|-------|-------------------------------------------------------------------| +| PVC | Permanent Virtual Channel | +| RC | Rate Control | +| REL | Release Request Message | +| RES | Reset Request Message | +| RLC | Release Confirm Message | +| RSC | Reset Confirm Message | +| SAAL | ATM Adaptation Layer for Signalling | +| SAID | Signalling Association Identifier | +| SAP | Service Access Point | +| SAR | Segmentation and Reassembly (Sublayer) | +| SDL | Specification and Description Language | +| SDU | Service Data Unit | +| SPVC | Soft PVC | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSCS | Service Specific Convergence Sublayer | +| SSCS | SSCS Information | +| SSIA | Service Specific Information (Audio) Parameter | +| SSIAE | Service Specific Information (Audio Extended) | +| SSIM | Service Specific Information (Multirate) Parameter | +| SSIME | Service Specific Information (Multirate Extended) | +| SSISA | Service Specific Information (SAR-assured) Parameter | +| SSISU | Service Specific Information (SAR-unassured) Parameter | +| SSSAR | Segmentation and Reassembly Service Specific Convergence Sublayer | +| STC | Signalling Transport Converter | +| SUCI | Served User Correlation ID | +| SUGR | Served User Generated Reference | +| SUT | Served User Transport | +| SVC | Switched Virtual Channel | +| SYN | Synchronization of change in SSCS operation | +| TAR | Temporary Alternative Routing | +| TC | Transfer Capability | +| TCC | TAR Controlled Connection | +| TCI | Test Connection Indication | +| TCS | Transfer Capability Support | +| TED | Transmission Error Detection | +| UBC | Unblock Confirm Message | +| UBL | Unblock Request Message | + +| | | +|------|--------------------------------------------------| +| UNI | User-Network Interface | +| UU | User-user | +| VBWS | Variable Bandwidth Stringent Transfer Capability | +| VBWT | Variable Bandwidth Tolerant Transfer Capability | +| VCC | Virtual Channel Connection | +| VPC | Virtual Path Connection | + +NOTE 1 – In ITU-T Recs Q.2630.1 [15] and Q.2630.2 [16], the abbreviation A2EA was used instead of DA2EA, ESEA instead of DESEA, and NSEA instead of DNSEA. + +NOTE 2 – In ITU-T Rec. Q.2630.1 [15], the abbreviation ALC was used instead of LC. + +# 5 General framework of the AAL type 2 signalling protocol + +The AAL type 2 signalling protocol provides the signalling capability to establish, release and maintain AAL type 2 point-to-point connections across a series of ATM VCCs that carry AAL type 2 links. These services are accessible via the AAL type 2 served user service access point (A2SU-SAP). + +The AAL type 2 signalling protocol also provides maintenance functions associated with the AAL type 2 signalling. + +An AAL type 2 signalling endpoint shall be able to control AAL type 2 links on more than one AAL type 2 path. These AAL type 2 paths may be contained on different ATM VPCs, which in turn may be carried on different ATM physical interfaces. + +Two peer AAL type 2 signalling entities rely on the generic signalling transport service to provide assured data transfer between them and service availability indications. These services are accessible via the Generic Signalling Transport Service Access Point (GST-SAP). + +NOTE – Primitives over the A2SU-SAP, GST-SAP, and LM-SAP are used for descriptive purpose only. They do not imply a specific implementation. + +Both peer AAL type 2 signalling entities provide the same set of services. + +The AAL type 2 signalling entity is subdivided into protocol entities and nodal functions as shown in Figure 5-1. At each AAL type 2 service endpoint, the AAL type 2 signalling entity communicates with the AAL type 2 served user. At an AAL type 2 switch, the AAL type 2 signalling entity does not communicate with an AAL type 2 served user. + +![Figure 5-1/Q.2630.3 – AAL type 2 signalling protocol reference architecture. This diagram shows the protocol stack for AAL type 2 signalling across three nodes: an AAL type 2 service endpoint, an AAL type 2 switch, and another AAL type 2 service endpoint. Each node contains an 'AAL type 2 served user' connected to an 'AAL type 2 signalling entity' via an A2SU-SAP. The signalling entity consists of a 'Nodal function' and a 'Protocol entity'. The Nodal function is connected to a 'Layer management' block via an LM-SAP. The Protocol entity exchanges 'AAL type 2 Signalling message' with the adjacent node's Protocol entity. Below the signalling entity is a 'Signalling transport converter' connected via a GST-SAP. This converter is connected to a 'Signalling transport' layer (e.g., MTP3b + NNI-SAAL, UNI-SAAL, SSCOP, ...). Notes indicate that in every AAL type 2 node, a signalling transport converter instance is associated with each AAL type 2 signalling transport. The diagram is labeled Q.2630.3_F5-1 at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 5-1/Q.2630.3 – AAL type 2 signalling protocol reference architecture. This diagram shows the protocol stack for AAL type 2 signalling across three nodes: an AAL type 2 service endpoint, an AAL type 2 switch, and another AAL type 2 service endpoint. Each node contains an 'AAL type 2 served user' connected to an 'AAL type 2 signalling entity' via an A2SU-SAP. The signalling entity consists of a 'Nodal function' and a 'Protocol entity'. The Nodal function is connected to a 'Layer management' block via an LM-SAP. The Protocol entity exchanges 'AAL type 2 Signalling message' with the adjacent node's Protocol entity. Below the signalling entity is a 'Signalling transport converter' connected via a GST-SAP. This converter is connected to a 'Signalling transport' layer (e.g., MTP3b + NNI-SAAL, UNI-SAAL, SSCOP, ...). Notes indicate that in every AAL type 2 node, a signalling transport converter instance is associated with each AAL type 2 signalling transport. The diagram is labeled Q.2630.3\_F5-1 at the bottom right. + +NOTE – In every AAL type 2 node, a signalling transport converter instance is associated with each AAL type 2 signalling transport. + +**Figure 5-1/Q.2630.3 – AAL type 2 signalling protocol reference architecture** + +Protocol Entities define the interactions between two adjacent AAL type 2 nodes. AAL type 2 messages are exchanged between peer protocol entities using the generic signalling transport service. + +The AAL type 2 signalling is independent of the signalling transport, although an assured data transport is required and a message size limit applies. The Generic Signalling Transport Service used is defined in ITU-T Rec. Q.2150.0 [12]. To adapt the Generic Signalling Transport Services to a specific signalling transport service, a signalling transport converter may be needed. The specification of signalling transport converters is beyond the scope of this Recommendation (see ITU-T Recs Q.2150.1 [22], Q.2150.2 [23] and Q.2150.3 [28]). + +The protocol entity is divided into several procedures as shown in Figure 5-2. + +![Figure 5-2/Q.2630.3 – Internal structure of the AAL type 2 signalling protocol entity. This diagram shows the internal structure of a 'Protocol entity' box. It contains three sub-boxes: 'Outgoing protocol procedures', 'Incoming protocol procedures', and 'Maintenance protocol procedures'. The diagram is labeled Q.2630.3_F5-2 at the bottom right.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +Figure 5-2/Q.2630.3 – Internal structure of the AAL type 2 signalling protocol entity. This diagram shows the internal structure of a 'Protocol entity' box. It contains three sub-boxes: 'Outgoing protocol procedures', 'Incoming protocol procedures', and 'Maintenance protocol procedures'. The diagram is labeled Q.2630.3\_F5-2 at the bottom right. + +**Figure 5-2/Q.2630.3 – Internal structure of the AAL type 2 signalling protocol entity** + +The outgoing protocol procedures provide the mechanism to initiate an AAL type 2 connection request. The incoming protocol procedures are applied when a request for an AAL type 2 connection is received from a peer entity. Both of these procedures provide for the orderly release of an AAL type 2 connection. The maintenance protocol procedures provide the mechanisms to align the status of the AAL type 2 resources at the two adjacent AAL type 2 nodes and the procedures to block and unblock an AAL type 2 path. + +The unrecognised information procedures in the nodal function as well as in the protocol entities provide the forward compatibility mechanism which enables extension of the protocol in the future. + +The nodal function provides the bridge between incoming and outgoing protocol entities, performs the routing functionality, and keeps track of the AAL type 2 path resources. + +## **5.1 Interface between the AAL type 2 signalling entity and the AAL type 2 served user** + +### **5.1.1 Service provided by the AAL type 2 signalling entity** + +The AAL type 2 signalling entity provides the following services to the AAL type 2 served user across the A2SU-SAP: + +- establishment of AAL type 2 connections; +- release of AAL type 2 connections; and +- modification of AAL type 2 connection resources. + +The AAL type 2 signalling protocol entity is independent of the AAL type 2 served user. + +### **5.1.2 Primitives between AAL type 2 signalling entities and the AAL type 2 served user** + +The A2SU-SAP primitives are used: + +- 1) by the originating served user to initiate AAL type 2 connection establishment and by the originating and destination served users to initiate the release of a connection; +- 2) by the AAL type 2 signalling entities to indicate an incoming connection to the destination served user and notifying either the originating or destination served user of the release of a connection; +- 3) by the modification sending served user to originate, and the modification receiving served user to respond to, an AAL type 2 connection resource modification request; and +- 4) by the AAL type 2 signalling entities to indicate a modification of the AAL type 2 connection resource to the modification receiving served user and notify the modification originating served user of the successful or unsuccessful modification. + +NOTE – When sending a primitive between the signalling protocol and its user, the primitive needs to be associated with a particular AAL type 2 connection instance. The mechanism used for this binding is considered to be an implementation detail and therefore is outside the scope of this Recommendation. + +The services are provided through the transfer of primitives which are summarized in Table 5-1, and are defined after the table. + +The AAL type 2 served user passes information in parameters in the primitives. Some of those parameters are mandatory and some are optional; the appropriate usage of the parameters is described in clause 8. + +**Table 5-1/Q.2630.3 – Primitives and parameters exchanged between the AAL type 2 signalling entities and the AAL type 2 served user** + +| Primitive generic name | Type | | | | +|------------------------|------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-------------|---------------------| +| | Request | Indication | Response | Confirm | +| ESTABLISH | DA2EA,
OA2EA,
SUGR, SUT,
TC, PTC, TCS,
LC, PLC, MSLC,
SSCS, PSSCS,
MSSSI,
PT, CP, TCI | OA2EA,
SUGR, SUT,
TC, PTC, TCS,
LC, PLC, MSLC,
SSCS, PSSCS,
MSSSI,
PT, CP, TCI | Not defined | TCS, MSLC,
MSSSI | +| RELEASE | Cause | Cause | Not defined | Cause | +| MODIFY | TC, LC, SSCS,
SUCI | TC, LC, SSCS,
SUCI | SUCI | SUCI | +| MODIFY-REJECT | Not defined | Not defined | Not defined | Cause | + +#### a) **ESTABLISH.request:** + +This primitive is used by the AAL type 2 served user to initiate the establishment of a new AAL type 2 connection, and optionally request the capability for subsequent modification to be performed on the requested connection. + +#### b) **ESTABLISH.indication:** + +This primitive is used by the AAL type 2 signalling entities to indicate that an incoming connection has been successfully established, and optionally indicate that the incoming connection is capable of subsequent modification. + +#### c) **ESTABLISH.confirm:** + +This primitive is used by the AAL type 2 signalling entities to indicate that the connection (which was previously requested by the served user) has successfully been established and optionally indicate that the established connection is capable of subsequent modification. + +#### d) **RELEASE.request:** + +This primitive is used by the AAL type 2 served user to initiate clearing of an AAL type 2 connection. + +#### e) **RELEASE.indication:** + +This primitive is used by the AAL type 2 signalling entities to indicate that an AAL type 2 connection has been released. + +#### f) **RELEASE.confirm:** + +This primitive is used as a negative acknowledgement for an ESTABLISH.request. + +#### g) **MODIFY.request:** + +This primitive is used by the AAL type 2 served user to originate the modification of the AAL type 2 connection resource. + +#### h) **MODIFY.indication:** + +This primitive is used by the AAL type 2 signalling entities to indicate that the modification of the AAL type 2 connection resource has been successfully performed. + +#### i) **MODIFY.response:** + +This primitive is used by the AAL type 2 served user to respond to the modification of the AAL type 2 connection resource. + +- j) **MODIFY.confirm:** +This primitive is used by the AAL type 2 signalling entities to indicate that the AAL type 2 connection resource modification (which was previously requested by the served user) has successfully been performed. +- k) **MODIFY-REJECT.confirm:** +This primitive is used by the AAL type 2 signalling entities to indicate that the AAL type 2 connection resource modification (which was previously requested by the served user) has been rejected. +- 5.1.3 Parameters between AAL type 2 signalling entities and the AAL type 2 served user** +- a) **Destination AAL type 2 Service Endpoint Address (DA2EA)** +This parameter carries the service endpoint address of the destination. It can have the form of an E.164 address or an NSAP address. +- b) **Origination AAL type 2 Service Endpoint Address (OA2EA)** +This parameter carries the service endpoint address of the origination. It can have the form of an E.164 address or an NSAP address. +- c) **Served User Generated Reference (SUGR)** +This parameter carries a reference provided by the originating AAL type 2 served user and this reference is transported unmodified to the destination served user. +- d) **Served User Transport (SUT)** +This parameter carries the served user data that is transported unmodified to the destination served user. +- e) **Transfer Capability (TC)** +This parameter gives an indication of the AAL type 2 transfer capability required for the AAL type 2 connection. This parameter can have the form of either: +- Fixed Bandwidth Transfer Capability; or + - Variable Bandwidth Stringent Transfer Capability; or + - Variable Bandwidth Tolerant Transfer Capability. +- f) **Preferred Transfer Capability (PTC)** +This parameter gives an indication that the AAL type 2 Transfer Capability shall be set as indicated in this parameter if the modification of the AAL type 2 Transfer Capability is permitted. This parameter can have the form of either: +- Preferred Fixed Bandwidth Transfer Capability; or + - Preferred Variable Bandwidth Stringent Transfer Capability; or + - Preferred Variable Bandwidth Tolerant Transfer Capability. +- g) **Transfer Capability Support (TCS)** +This parameter gives an indication whether Transfer Capabilities are supported by all AAL type 2 nodes of the AAL type 2 connection. +- h) **Link Characteristics (LC)** +This parameter gives an indication of the resources required for the AAL type 2 connection and is used only for AAL type 2 path selection and connection admission control. +- i) **Preferred Link Characteristics (PLC)** +This parameter gives an indication that the Link Characteristics shall be set as indicated in this parameter if the modification of the Link Characteristics is permitted. + +#### j) **Modify Support for Link Characteristics (MSLC)** + +This parameter gives an indication that the AAL type 2 Link Characteristics of the AAL type 2 connection may need to be modified during the lifetime of the AAL type 2 connection (ESTABLISH.request) or is permitted to be modified (ESTABLISH.indication and ESTABLISH.confirm). + +#### k) **SSCS Information (SSCS)** + +This parameter identifies the type and the capabilities of an AAL type 2 SSCS protocol. This parameter can have the form of either: + +- Service Specific Information (Multirate) (see ITU-T Rec. I.366.2 [14]), +- Service Specific Information (Audio) (see ITU-T Rec. I.366.2 [14]), +- Service Specific Information (Multirate Extended) (see Note); +- Service Specific Information (Audio Extended) (see Note); or +- Service Specific Information (SAR) (see ITU-T Rec. I.366.1 [9]) with or without the additional parameters necessary for the assured data transfer. + +NOTE – Multirate Extended and Audio Extended are used in this Recommendation to support the services of the U-Plane definitions of the 2000 version of ITU-T Rec. I.366.2 [14]. The (non-extended) Multirate and Audio are retained for backward compatibility with ITU-T Rec. Q.2630.1 [15]. For example, the Audio Extended form of the SSCS Information parameter in this Recommendation (see 7.4.19) adds support for LB, RC, and SYN that were added as U-Plane functions in the 2000 version of ITU-T Rec. I.366.2 [14]. + +#### l) **Preferred SSCS Information (PSSCS)** + +This parameter gives an indication that the SSCS Information shall be set as indicated in this parameter if the modification of the SSCS Information is permitted. This parameter can have the form of either: + +- Preferred Service Specific Information (Multirate Extended) (see Note); or +- Preferred Service Specific Information (Audio Extended) (see Note). + +Modification of Frame Mode Data as specified in ITU-T Rec. I.366.2 [14], or modification of SAR as specified in ITU-T Rec. I.366.1 [9] is outside the scope of this Recommendation. + +#### m) **Modify Support for SSCS Information (MSSSI)** + +This parameter gives an indication that the SSCS Information of the AAL type 2 connection may need to be modified during the lifetime of the AAL type 2 connection (ESTABLISH.request) or are permitted to be modified (ESTABLISH.indication and ESTABLISH.confirm). + +#### n) **Path Type (PT)** + +This parameter indicates a request for an AAL type 2 path with a specified Quality of Service. + +#### o) **Connection Priority (CP)** + +This parameter carries information sent in the forward direction to indicate the priority level of the connection request. + +#### p) **Test Connection Indication (TCI)** + +By its presence, this parameter indicates that the AAL type 2 connection to be established is a test connection. + +#### q) **Cause** + +This parameter describes the reason for the release of the AAL type 2 connection. It also may indicate the reason why an AAL type 2 connection could not be established or a modification was rejected. + +#### r) **Served User Correlation ID (SUCI)** + +This parameter carries the SSCS correlation ID (as specified in ITU-T Rec. I.366.2 [14]) during the modification of SSCS information and is transported unmodified to the destination or origination served user. + +## 5.2 Interface between the AAL type 2 signalling entity and the generic signalling transport + +### 5.2.1 Service provided by the generic signalling transport service + +The Generic Signalling Transport Service is specified in ITU-T Rec. Q.2150.0 [12]. For convenience, a summary of the primitives for accessing the service is reproduced in Table 5-2. In the event of any difference between this table and the definitions in ITU-T Rec. Q.2150.0, the definitions in ITU-T Rec. Q. 2150.0 take precedence. + +**Table 5-2/Q.2630.3 – Primitives and parameters of the Generic Signalling Transport Sublayer** + +| Primitive generic name | Type | | | | +|------------------------|--------------------------------------------------------|------------------------------------|-------------|-------------| +| | Request | Indication | Response | Confirm | +| START-INFO | Not defined | Max_Length
CIC_Control | Not defined | Not defined | +| IN-SERVICE | Not defined | Level | Not defined | Not defined | +| OUT-OF-SERVICE | Not defined | (Note 1) | Not defined | Not defined | +| CONGESTION | Not defined | Level | Not defined | Not defined | +| TRANSFER | Sequence Control
STC User Data
Priority (Note 2) | STC User Data
Priority (Note 2) | Not defined | Not defined | + +NOTE 1 – This primitive has no parameters. +NOTE 2 – This parameter is a national option (and the use of this parameter is not supported by all signalling transports). + +On the establishment of a signalling transport converter entity and the respective signalling transport converter user entity, for example at power up, the initial conditions are 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. + +NOTE – The CIC\_Control parameter of the START-INFO.indication is ignored by the AAL type 2 signalling entity. + +### 5.2.2 State transition diagram for sequences of primitives of the generic signalling transport service + +This clause defines the constraints on the sequences in which the primitives may occur at the layer boundaries of the generic signalling transport service. The sequences are related to the states at one generic signalling transport endpoint between the generic signalling transport service provider and its user. The possible overall sequences of primitives are shown in the state transition diagram, Figure 5-3. + +![State transition diagram for sequences of primitives between the GST 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', a 'TRANFER.request' leads to 'In Service'. From 'In Service', an 'IN-SERVICE.indication' leads to 'Out of Service'. From 'Out of Service', an 'OUT-OF-SERVICE.indication' leads to 'In Service'. Both states have self-loops: 'Out of Service' has 'TRANFER.request' and 'TRANFER.indication'; 'In Service' has 'TRANFER.request' and 'TRANFER.indication CONGESTION.indication'. The diagram is labeled Q.2630.3_F5-3.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +State transition diagram for sequences of primitives between the GST 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', a 'TRANFER.request' leads to 'In Service'. From 'In Service', an 'IN-SERVICE.indication' leads to 'Out of Service'. From 'Out of Service', an 'OUT-OF-SERVICE.indication' leads to 'In Service'. Both states have self-loops: 'Out of Service' has 'TRANFER.request' and 'TRANFER.indication'; 'In Service' has 'TRANFER.request' and 'TRANFER.indication CONGESTION.indication'. The diagram is labeled Q.2630.3\_F5-3. + +**Figure 5-3/Q.2630.3 – State transition diagram for sequences of primitives between the GST and its user** + +This model assumes that a request primitive is never issued at the same time as an indication primitive. The model also assumes that the primitives are serviced immediately and in zero time. + +## 5.3 Interface between the AAL type 2 signalling entity and layer management + +### 5.3.1 Service provided by layer management + +This interface provides the internal interface to the network management system. + +### 5.3.2 Primitives between AAL type 2 signalling entities and layer management + +The primitives are summarized in Table 5-3, and are defined after the table. + +**Table 5-3/Q.2630.3 – Primitives and parameters exchanged between the AAL type 2 signalling entities and layer management** + +| Primitive generic name | Type | | | | +|-------------------------------------|-------------|------------------------|-------------|-------------| +| | Request | Indication | Response | Confirm | +| BLOCK | ANI, A2P | Not defined | Not defined | Cause | +| UNBLOCK | ANI, A2P | Not defined | Not defined | Cause | +| RESET | ANI, CEID | ANI, CEID | Not defined | – | +| STOP-RESET | ANI, CEID | Not defined | Not defined | Not defined | +| ADD-PATH | Not defined | ANI, A2P, PT Ownership | Not defined | Not defined | +| REMOVE-PATH | Not defined | ANI, A2P | Not defined | Not defined | +| ERROR | Not defined | ANI, CEID, Cause | Not defined | Not defined | +| – This primitive has no parameters. | | | | | + +NOTE – When sending a primitive between the AAL type 2 signalling entity and layer management, the primitive needs to be associated with a particular management action instance. The mechanism used for this binding is considered to be an implementation detail and, therefore, is outside the scope of this Recommendation. + +#### a) **BLOCK.request:** + +A primitive to request the AAL type 2 signalling entity to locally block a particular, unblocked AAL type 2 path and to indicate this to the peer AAL type 2 signalling entity. + +#### b) **BLOCK.confirm:** + +A primitive with no parameter indicates that the AAL type 2 signalling entity has successfully informed the peer AAL type 2 signalling entity of the blocking of a particular AAL type 2 path. A primitive with a cause parameter indicates that the AAL type 2 signalling entity has detected an error in the blocking procedures. + +- c) **UNBLOCK.request:** +A primitive to request the AAL type 2 signalling entity to locally unblock a particular, blocked AAL type 2 path and to indicate this to the peer AAL type 2 signalling entity. +- d) **UNBLOCK.confirm:** +A primitive with no parameter indicates that the AAL type 2 signalling entity has successfully informed the peer signalling entity of the unblocking of a particular AAL type 2 path. A primitive with a cause parameter indicates that the AAL type 2 signalling entity has detected an error in the unblocking procedures. +- e) **RESET.request:** +A primitive to request the AAL type 2 signalling entity to reset a particular channel, all channels on a particular AAL type 2 path, or all channels on all AAL type 2 paths associated with a signalling transport association to the "Idle" state and to indicate this to the peer AAL type 2 signalling entity. +- f) **RESET.indication:** +A primitive indicating that the AAL type 2 signalling entity has reset a particular channel, all channels on a particular AAL type 2 path, or all channels on all AAL type 2 paths associated with a signalling transport association to the "Idle" state on the request of the peer AAL type 2 signalling entity. +- g) **RESET.confirm:** +A primitive indicating that the AAL type 2 signalling entity has successfully informed the peer AAL type 2 signalling entity of the resetting of the channel or all the channels on a specific AAL type 2 path or on all AAL type 2 paths associated with a signalling transport association. +- h) **STOP-RESET.request:** +A primitive to request the AAL type 2 signalling entity to stop a reset procedure. +- i) **ADD-PATH.indication:** +This primitive informs the AAL type 2 signalling entity that a new AAL type 2 path has been established towards one of the adjacent AAL type 2 nodes. +- j) **REMOVE-PATH.indication:** +This primitive informs the AAL type 2 signalling entity that an AAL type 2 path has been removed. +- k) **ERROR.indication:** +A primitive to indicate any operational errors in the AAL type 2 signalling procedures. + +### 5.3.3 Parameters between AAL type 2 signalling entities and layer management + +- a) **AAL type 2 Path Identifier (A2P)** +This parameter indicates an AAL type 2 path. +- b) **Connection Element Identifier (CEID)** +This parameter allows for the identification of: + - i) all AAL type 2 paths between two adjacent AAL type 2 nodes associated with a signalling transport association; + - ii) a particular AAL type 2 path; or + - iii) a particular channel on a particular AAL type 2 path. +- c) **Cause** +This parameter gives the reason of an operational error. + +- d) **Ownership** +This parameter indicates whether a newly established AAL type 2 path is owned by the AAL type 2 signalling entity or by its peer. +- e) **Adjacent AAL type 2 Node Identifier (ANI)** +This parameter is used to unambiguously indicate an adjacent AAL type 2 node. +- f) **Path Type (PT)** +This parameter indicates the Quality of Service class of the newly established AAL type 2 path. + +# 6 Forward and backward compatibility + +The compatibility mechanism remains unchanged for all capability sets and/or subsets of the AAL type 2 protocol defined in this Recommendation. It is based on forward compatibility information associated with all signalling information. + +The compatibility method eases the network operation, for example: + +- For the typical case of an AAL type 2 signalling protocol mismatch during a network upgrading. +- To interconnect two networks on a different functional level. +- For networks using a different subset of the same AAL type 2 protocol, etc. + +NOTE – A node may be at a different functional level due to having implemented a different capability set or another subset of the protocol specified in this Recommendation. + +The coding of message and parameter compatibility information is shown in Annex B; these codings shall be used to maintain backward compatibility with AAL type 2 nodes conforming only to ITU-T Rec. Q.2630.1 [15] and with AAL type 2 nodes conforming only to ITU-T Rec. Q.2630.2 [16]. + +The forward compatibility mechanism specified in 6.2 and 8.1 applies to this and future capability sets of this Recommendation. + +## 6.1 Backward compatibility rules + +Compatible interworking between AAL type 2 protocol capability sets should be optimized by adhering to the following rules when specifying a new capability set (release): + +- 1) Existing protocol elements, i.e., procedures, messages, parameters and subfield values, should not be changed unless a protocol error needs to be corrected or it becomes necessary to change the operation of the service that is being supported by the protocol. +- 2) The semantics of a message, a parameter, or of a field and subfield within a parameter should not be changed. +- 3) Established rules for formatting and encoding messages and parameters should not be modified. + +## 6.2 Forward compatibility mechanism + +Compatibility between this and future capability sets will be guaranteed, in the sense that any two capability sets can be interconnected directly with each other, if the following requirements are fulfilled: + +- i) *Protocol compatibility* +Connections between any two AAL type 2 protocols do not fail for the reason of not satisfying protocol requirements. + +### ii) *Service and functional compatibility* + +This feature may be considered as compatibility typically between originating and destination nodes. Services and functions available at these nodes, but possibly not yet taken into account in the intermediate nodes, are supported, provided that information related to these services and functions can be passed transparently through intermediate nodes. + +### iii) *Resource control and management compatibility* + +For these functions, occurring only link-by-link, at least a backward notification is needed, if correct handling is not possible. + +# 7 Format and coding of AAL type 2 signalling protocol + +## 7.1 Coding conventions for the AAL type 2 signalling protocol + +### 7.1.1 Principles + +The following principles shall apply for the coding of the AAL type 2 signalling protocol: + +- a) The order of coding of messages shall consist of "destination signalling association identifier", "message identifier", "message compatibility", and any parameters. +- b) Messages shall carry zero or more parameters. +- c) The sequence of parameters is unconstrained. +- d) The order of coding of parameters shall consist of "parameter identifier", "parameter compatibility", "parameter length", and any fields. +- e) Parameters shall carry zero or more fields. +- f) A parameter shall always consist of the same sequence of fields. +- g) If new fields need to be added to a parameter or the length of a fixed size field needs to be changed, the modifications shall be carried in a new parameter (different parameter identifier); the existing parameter shall remain unchanged. +- h) Any sequence of fixed size fields and variable size fields is permissible. +- i) Fixed length fields shall consist of the "field" only; no length is indicated. +- j) Variable length fields shall consist of "field length" and "field". +- k) Fields shall be multiples of one octet. +- l) Fields are composed of one or more subfields. +- m) Reserved subfields shall be coded all zeroes and need not be interpreted by the receiver. +- n) If there is no information to be carried in a variable size field, its length shall be set to zero, i.e., only the field length octet will be present. +- o) If there is no information to be carried in a fixed size field, its content shall be set to zero in all octets. +- p) The presence or the interpretation of a field shall not depend on the value of a field in another parameter. + +Consistent with the above coding principles, it is further specified that: + +- The message length shall allow for lengths of up to 4 000 octets. +- The parameter length shall allow for lengths of up to 255 octets. + +### 7.1.2 General format of messages + +The general format of a message is shown in Table 7-1. + +NOTE – No "message length" needs to be carried in the message itself; the length of information passed via a primitive implicitly defines its length and the assured data transfer assures that no octets are lost or gained in transport. + +**Table 7-1/Q.2630.3 – AAL type 2 message format** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------|-----------------------------------------------|---|---|---|---|---|---|---|----------| +| Header | Destination signalling association identifier | | | | | | | | 4 octets | +| | Message identifier | | | | | | | | 1 octet | +| | Message compatibility | | | | | | | | 1 octet | +| Payload | Parameters | | | | | | | | | + +The message header consists of the destination signalling association identifier field, the message identifier field, and the message compatibility field. The destination signalling association identifier field is coded the same as the signalling association identifier field (see 7.4.2), the coding of the message identifier field is specified in 7.2.1, and the message compatibility field is coded the same as the compatibility field (see 7.4.1). + +The message payload consists of zero, one, or more parameters. + +#### 7.1.2.1 Bit coding rules + +When a field is contained within a single octet, the lowest bit number of the field represents the lowest order value. + +When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases; the lowest bit number associated with the field represents the lowest order value. + +(This coding conforms to the coding conventions specified in 2.1/I.361 [2].) + +### 7.1.3 General format of parameters + +The general format of a parameter is shown in Table 7-2. + +**Table 7-2/Q.2630.3 – AAL type 2 parameter format** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------|-------------------------|---|---|---|---|---|---|---|---------| +| Header | Parameter identifier | | | | | | | | 1 octet | +| | Parameter compatibility | | | | | | | | 1 octet | +| | Parameter length | | | | | | | | 1 octet | +| Payload | Fields | | | | | | | | | + +The coding of the parameter identifier field is specified in 7.2.2, Table 7-7 and the parameter compatibility field is coded as a compatibility field (see 7.4.1). The coding of the parameter length is a binary value indicating the number of octets in the parameter payload, i.e., the count does not include the octets in the parameter header. + +Each parameter has a defined number of fields of defined type and in a particular order. + +### 7.1.4 General format of fixed length fields + +The general format of a fixed length field is shown in Table 7-3. + +**Table 7-3/Q.2630.3 – AAL type 2 field – Fixed length format** + +![](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +| | | | | | | | | | | +|---------|-------|---|---|---|---|---|---|---|----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Payload | Field | | | | | | | | n octets | + +The field type is determined by the location of the field in the particular parameter. + +### 7.1.5 General format of variable length fields + +The general format of a variable length field is shown in Table 7-4. + +**Table 7-4/Q.2630.3 – AAL type 2 field – Variable length format** + +![](356eb99ab9489bbd647223390a913903_img.jpg) + +| | | | | | | | | | | +|---------|--------------|---|---|---|---|---|---|---|----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | Field length | | | | | | | | 1 octet | +| Payload | Field | | | | | | | | n octets | + +The coding of the field length is a binary value indicating the number of octets in the field payload, i.e., the count does not include the field length octet. + +The field type is determined by the location of the field in the particular parameter. + +## 7.2 Format and coding of the AAL type 2 signalling protocol messages + +### 7.2.1 AAL type 2 signalling protocol messages + +The AAL type 2 signalling protocol messages and their message identifiers are shown in Table 7-5. + +**Table 7-5/Q.2630.3 – AAL type 2 messages and the coding of the message identifiers** + +| Message | Acronym | Message identifier | +|--------------------|---------|--------------------| +| Block Confirm | BLG | 0 0 0 0 0 0 0 1 | +| Block Request | BLO | 0 0 0 0 0 0 1 0 | +| Confusion | CFN | 0 0 0 0 0 0 1 1 | +| Establish Confirm | ECF | 0 0 0 0 0 1 0 0 | +| Establish Request | ERQ | 0 0 0 0 0 1 0 1 | +| Modify Acknowledge | MOA | 0 0 0 0 1 1 0 0 | +| Modify Reject | MOR | 0 0 0 0 1 1 0 1 | +| Modify Request | MOD | 0 0 0 0 1 1 1 0 | +| Release Confirm | RLC | 0 0 0 0 0 1 1 0 | +| Release Request | REL | 0 0 0 0 0 1 1 1 | +| Reset Confirm | RSC | 0 0 0 0 1 0 0 0 | +| Reset Request | RES | 0 0 0 0 1 0 0 1 | +| Unblock Confirm | UBC | 0 0 0 0 1 0 1 0 | +| Unblock Request | UBL | 0 0 0 0 1 0 1 1 | + +### 7.2.2 Parameters of the AAL type 2 signalling protocol messages + +The parameters of the AAL type 2 signalling protocol messages are shown in Table 7-6. The indications of "mandatory" and "optional" are for information only. The authoritative definition is given in clause 8 and Annex C. If any difference between the indications in this clause and the definitions in clause 8 and Annex C exists, the definitions in clause 8 take precedence. + +Multiple presence of the same parameter in a single message is not permitted. + +**Table 7-6/Q.2630.3 (part 1 of 2) – Parameters of the AAL type 2 signalling protocol messages** + +| Parameter | Message | | | | | | | +|-------------------------------------------------------------|---------------|----------|-----|-----------|----------|-----|-----| +| | ERQ | ECF | REL | RLC | MOD | MOA | MOR | +| Automatic Congestion Control | – | – | O | O | – | – | – | +| Cause | – | – | M | (Note 12) | – | – | M | +| Connection Element Identifier | M | – | – | O | – | – | – | +| Connection Priority | O | – | – | – | – | – | – | +| Destination E.164 Service Endpoint Address | (Note 2) | – | – | – | – | – | – | +| Destination NSAP Service Endpoint Address | (Note 2) | – | – | – | – | – | – | +| Destination Signalling Association Identifier (Note 1) | (Note 3) | M | M | M | M | M | M | +| Hop Counter | O | – | – | – | – | – | – | +| Link Characteristics | (Note 4) | – | – | – | (Note 4) | – | – | +| Modify Support for Service Specific Information | (Notes 4, 16) | (Note 4) | – | – | – | – | – | +| Modify Support for Link Characteristics | (Notes 4, 14) | (Note 4) | – | – | – | – | – | +| Originating Signalling Association Identifier | M | M | – | – | – | – | – | +| Origination E.164 Service Endpoint Address | (Note 5) | – | – | – | – | – | – | +| Origination NSAP Service Endpoint Address | (Note 5) | – | – | – | – | – | – | +| Path Type | (Note 6) | – | – | – | – | – | – | +| Preferred Link Characteristics | (Notes 4, 15) | – | – | – | – | – | – | +| Preferred Service Specific Information (Audio Extended) | (Notes 4, 7) | – | – | – | – | – | – | +| Preferred Service Specific Information (Multirate Extended) | (Notes 4, 7) | – | – | – | – | – | – | +| Preferred Transfer Capability (FBW) | (Notes 4, 8) | – | – | – | – | – | – | +| Preferred Transfer Capability (VBWS) | (Notes 4, 8) | – | – | – | – | – | – | +| Preferred Transfer Capability (VBWT) | (Notes 4, 8) | – | – | – | – | – | – | +| Served User Correlation ID | – | – | – | – | O | O | – | +| Served User Generated Reference | O | – | – | – | – | – | – | + +**Table 7-6/Q.2630.3 (part 1 of 2) – Parameters of the AAL type 2 signalling protocol messages** + +| Parameter | Message | | | | | | | | +|---------------------------------------------------|------------------|----------|-----|-----|----------------|-----|-----|--| +| | ERQ | ECF | REL | RLC | MOD | MOA | MOR | | +| Served User Transport | O | – | – | – | – | – | – | | +| Service Specific Information (Audio Extended) | (Notes 9, 10) | – | – | – | (Notes 13, 17) | – | – | | +| Service Specific Information (Audio) | (Notes 4, 9, 10) | – | – | – | – | – | – | | +| Service Specific Information (Multirate Extended) | (Notes 9, 10) | – | – | – | (Notes 13, 17) | – | – | | +| Service Specific Information (Multirate) | (Notes 4, 9, 10) | – | – | – | – | – | – | | +| Service Specific Information (SAR-assured) | (Note 9) | – | – | – | – | – | – | | +| Service Specific Information (SAR-unassured) | (Note 9) | – | – | – | – | – | – | | +| TAR Controlled Connection | O | – | – | – | – | – | – | | +| Test Connection Indicator | O | – | – | – | – | – | – | | +| Transfer Capability (FBW) | (Note 11) | – | – | – | (Notes 13, 17) | – | – | | +| Transfer Capability (VBWS) | (Note 11) | – | – | – | (Notes 13, 17) | – | – | | +| Transfer Capability (VBWT) | (Note 11) | – | – | – | (Notes 13, 17) | – | – | | +| Transfer Capability Support (TCS) | (Note 4) | (Note 4) | – | – | – | – | – | | + +M Mandatory parameter +O Optional parameter +– Parameter not present + +NOTE 1 – This row designates the Destination Signalling Association Identifier field in the message header. + +NOTE 2 – Exactly one of these parameters must be present in an instance of the message. + +NOTE 3 – The Destination Signalling Association Identifier field contains the value "unknown". + +NOTE 4 – This parameter is only used for backward compatibility, i.e., for interworking with AAL type 2 nodes that conform only to ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16] (see Annex C). + +NOTE 5 – At most one of these parameters is present in an instance of the message. + +NOTE 6 – If the path type parameter is not included, the path type shall be considered to be the network default stringent QoS class. + +NOTE 7 – This parameter may only be included if "Modify Support for Service Specific Information" is included; at most one of these parameters is present in an instance of the message. If present it must refer to the same service specific information as the Service Specific Information parameter present in the same Establish Request message, i.e., Audio or Multirate. + +NOTE 8 – This parameter must be included if a "Preferred Link Characteristics" and/or a "Preferred Service Specific Information" is included. At most one of these parameters is present in an instance of the message. If present, it must refer to the same transfer capability as the Transfer Capability parameter present in the same Establish Request message. + +NOTE 9 – At most one of these parameters is present in an instance of the message. + +**Table 7-6/Q.2630.3 (part 1 of 2) – Parameters of the AAL type 2 signalling protocol messages** + +| Parameter | Message | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----|-----|-----|-----|-----|-----| +| | ERQ | ECF | REL | RLC | MOD | MOA | MOR | +| NOTE 10 – If the Modify Support for Service Specific Information parameter is included, this parameter shall also be included.
NOTE 11 – Exactly one of these parameters is present in an instance of the message.
NOTE 12 – The "Cause" parameter is present in the Release Confirm message if:
a) the RLC is used to reject a connection establishment; or
b) the cause reports unrecognized information received in the REL message.
NOTE 13 – At most one of these parameters is present in an instance of the message, and only the same parameter that was present in the Establish Request message may be present.
NOTE 14 – This parameter may be present only if the parameter "Link Characteristics" is present also.
NOTE 15 – This parameter may be present only if the parameter "Modify Support for Link Characteristics" is present also.
NOTE 16 – This parameter may be present only if one of the parameters "Service Specific Information (Audio)", "Service Specific Information (Audio Extended)", "Service Specific Information (Multirate)", and "Service Specific Information (Multirate Extended)" is present also.
NOTE 17 – At least one of these parameters is present in an instance of the message. | | | | | | | | + +**Table 7-6/Q.2630.3 (part 2 of 2) – Parameters of the AAL type 2 signalling protocol messages** + +| Parameter | Message | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|---------------|----------|---------------|----------|-----| +| | RES | RSC | BLO | BLC | UBL | UBC | CFN | +| Cause | – | (Note 4) | – | (Note 4) | – | (Note 4) | M | +| Connection Element Identifier | M | – | M
(Note 3) | – | M
(Note 3) | – | – | +| Destination Signalling Association Identifier (Note 1) | (Note 2) | M | (Note 2) | M | (Note 2) | M | M | +| Originating Signalling Association Identifier | M | – | M | – | M | – | – | +| M Mandatory parameter
O Optional parameter
– Parameter not present
NOTE 1 – This row designates the Destination Signalling Association Identifier field in the message header.
NOTE 2 – The Destination Signalling Association Identifier field contains the value "unknown".
NOTE 3 – The Channel Identifier field is set to "Null", but the Path Identifier includes a value identifying an AAL type 2 path.
NOTE 4 – The "Cause" parameter is present only if the cause reports unrecognized information received. | | | | | | | | + +The identifiers of the AAL type 2 message parameters are defined in Table 7-7. + +**Table 7-7/Q.2630.3 – Identifiers of the AAL type 2 message parameters** + +| AAL type 2 Parameter | Ref. | Acronym | Identifier | +|--------------------------------------------------------------------|--------|---------|-----------------| +| Automatic Congestion Control | 7.3.25 | ACC | 0 0 0 1 1 0 0 0 | +| Cause | 7.3.1 | CAU | 0 0 0 0 0 0 0 1 | +| Connection Element Identifier | 7.3.2 | CEID | 0 0 0 0 0 0 1 0 | +| Connection Priority | 7.3.26 | CP | 0 0 0 1 1 0 0 1 | +| Destination E.164 Service Endpoint Address | 7.3.3 | DESEA | 0 0 0 0 0 0 1 1 | +| Destination NSAP Service Endpoint Address | 7.3.4 | DNSEA | 0 0 0 0 0 1 0 0 | +| Hop Counter | 7.3.27 | HC | 0 0 0 1 1 0 1 0 | +| Link Characteristics (Note) | 7.3.5 | LC | 0 0 0 0 0 1 0 1 | +| Modify Support for Link Characteristics (Note) | 7.3.20 | MSLC | 0 0 0 0 1 1 1 0 | +| Modify Support for Service Specific Information (Note) | 7.3.21 | MSSSI | 0 0 0 0 1 1 1 1 | +| Originating Signalling Association Identifier | 7.3.6 | OSAID | 0 0 0 0 0 1 1 0 | +| Origination E.164 Service Endpoint Address | 7.3.23 | OESSEA | 0 0 0 1 1 0 1 1 | +| Origination NSAP Service Endpoint Address | 7.3.24 | ONSEA | 0 0 0 1 0 1 0 1 | +| Path Type | 7.3.14 | PT | 0 0 0 1 0 0 0 0 | +| Preferred Link Characteristics (Note) | 7.3.19 | PLC | 0 0 0 1 0 0 0 1 | +| Preferred Service Specific Information (Audio Extended) (Note) | 7.3.17 | PSSIAE | 0 0 0 1 0 0 1 0 | +| Preferred Service Specific Information (Multirate Extended) (Note) | 7.3.18 | PSSIME | 0 0 0 1 0 0 1 1 | +| Preferred Transfer Capability (FBW) (Note) | 7.3.29 | PFBW | 0 0 0 1 1 1 0 0 | +| Preferred Transfer Capability (VBWS) (Note) | 7.3.30 | PVBWS | 0 0 0 1 1 1 0 1 | +| Preferred Transfer Capability (VBWT) (Note) | 7.3.31 | PVBWT | 0 0 0 1 1 1 1 0 | +| Served User Correlation ID | 7.3.22 | SUCI | 0 0 0 1 0 1 0 0 | +| Served User Generated Reference | 7.3.7 | SUGR | 0 0 0 0 0 1 1 1 | +| Served User Transport | 7.3.8 | SUT | 0 0 0 0 1 0 0 0 | +| Service Specific Information (Audio Extended) | 7.3.15 | SSIAE | 0 0 0 1 0 1 1 0 | +| Service Specific Information (Audio) (Note) | 7.3.9 | SSIA | 0 0 0 0 1 0 0 1 | +| Service Specific Information (Multirate Extended) | 7.3.16 | SSIME | 0 0 0 1 0 1 1 1 | +| Service Specific Information (Multirate) (Note) | 7.3.10 | SSIM | 0 0 0 0 1 0 1 0 | +| Service Specific Information (SAR-assured) | 7.3.11 | SSISA | 0 0 0 0 1 0 1 1 | +| Service Specific Information (SAR-unassured) | 7.3.12 | SSISU | 0 0 0 0 1 1 0 0 | +| TAR Controlled Connection | 7.3.28 | TCC | 0 0 0 1 1 1 1 1 | +| Test Connection Indicator | 7.3.13 | TCI | 0 0 0 0 1 1 0 1 | +| Transfer Capability (FBW) | 7.3.32 | FBW | 0 0 1 0 0 0 0 0 | +| Transfer Capability (VBWS) | 7.3.33 | VBWS | 0 0 1 0 0 0 0 1 | +| Transfer Capability (VBWT) | 7.3.34 | VBWT | 0 0 1 0 0 0 1 0 | +| Transfer Capability Support (Note) | 7.3.35 | TCS | 0 0 1 0 0 0 1 1 | + +NOTE – In this Recommendation, this parameter is only used for backward compatibility, i.e., for interworking with AAL type 2 nodes that conform only to ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16]. + +## 7.3 Parameter specification of the AAL type 2 signalling protocol messages + +### 7.3.1 Cause + +The sequence of fields in the cause parameter is shown in Table 7-8. + +**Table 7-8/Q.2630.3 – Sequence of fields in the cause parameter** + +| Field No. | Field | Ref. | +|-----------|-------------|--------| +| 1 | Cause Value | 7.4.16 | +| 2 | Diagnostics | 7.4.17 | + +### 7.3.2 Connection element identifier + +The sequence of fields in the connection element identifier parameter is shown in Table 7-9. + +**Table 7-9/Q.2630.3 – Sequence of fields in the connection element identifier parameter** + +| Field No. | Field | Ref. | +|-----------|--------------------|-------| +| 1 | Path Identifier | 7.4.3 | +| 2 | Channel Identifier | 7.4.4 | + +| AAL type 2 Path Identifier | Channel Identifier | Meaning | +|-----------------------------------|---------------------------|-------------------------------------------------------------------------| +| Null | Ignored | All AAL type 2 paths associated with a signalling transport association | +| Value | Null | AAL type 2 path identifier "Value" | +| Value | CID | Channel "CID" in AAL type 2 path identifier "Value" | + +### 7.3.3 Destination E.164 service endpoint address + +The sequence of fields in the destination E.164 [10] service endpoint address parameter is shown in Table 7-10. + +**Table 7-10/Q.2630.3 – Sequence of fields in the destination E.164 service endpoint address parameter** + +| Field No. | Field | Ref. | +|-----------|-------------------|--------| +| 1 | Nature of Address | 7.4.13 | +| 2 | E.164 Address | 7.4.14 | + +### 7.3.4 Destination NSAP service endpoint address + +The sequence of fields in the destination NSAP [5] service endpoint address parameter is shown in Table 7-11. + +**Table 7-11/Q.2630.3 – Sequence of fields in the destination NSAP service endpoint address parameter** + +| Field No. | Field | Ref. | +|-----------|--------------|--------| +| 1 | NSAP Address | 7.4.15 | + +### 7.3.5 Link characteristics + +The sequence of fields in the link characteristics parameter is shown in Table 7-12. + +**Table 7-12/Q.2630.3 – Sequence of fields in the link characteristics parameter** + +| Field No. | Field | Ref. | +|-----------|--------------------------|----------| +| 1 | Maximum CPS-SDU Bit Rate | (Note 1) | +| 2 | Average CPS-SDU Bit Rate | (Note 1) | +| 3 | Maximum CPS-SDU Size | (Note 2) | +| 4 | Average CPS-SDU Size | (Note 2) | + +NOTE 1 – This field is coded as a CPS-SDU Bit Rate field (see 7.4.11). +NOTE 2 – This field is coded as a CPS-SDU Size field (see 7.4.12). + +### 7.3.6 Originating signalling association identifier + +The sequence of fields in the originating signalling association identifier parameter is shown in Table 7-13. + +**Table 7-13/Q.2630.3 – Sequence of fields in the originating signalling association identifier parameter** + +| Field No. | Field | Ref. | +|-----------|------------------------------------|--------| +| 1 | Originating Signalling Association | (Note) | + +NOTE – This field is coded as a Signalling Association Identifier field (see 7.4.2). + +### 7.3.7 Served user generated reference + +The sequence of fields in the served user generated reference parameter is shown in Table 7-14. + +**Table 7-14/Q.2630.3 – Sequence of fields in the served user generated reference parameter** + +| Field No. | Field | Ref. | +|-----------|---------------------------------|--------| +| 1 | Served User Generated Reference | 7.4.10 | + +### 7.3.8 Served user transport + +The sequence of fields in the served user transport parameter is shown in Table 7-15. + +**Table 7-15/Q.2630.3 – Sequence of fields in the served user transport parameter** + +| Field No. | Field | Ref. | +|-----------|-----------------------|--------| +| 1 | Served User Transport | 7.4.18 | + +### 7.3.9 Service specific information (Audio) + +The sequence of fields in the service specific information (audio) parameter is shown in Table 7-16. + +**Table 7-16/Q.2630.3 – Sequence of fields in the service specific information (audio) parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------------|-------| +| 1 | Audio Service | 7.4.6 | +| 2 | Organizational Unique Identifier | 7.4.5 | + +### 7.3.10 Service specific information (Multirate) + +The sequence of fields in the service specific information (multirate) parameter is shown in Table 7-17. + +**Table 7-17/Q.2630.3 – Sequence of fields in the service specific information (multirate) parameter** + +| Field No. | Field | Ref. | +|-----------|-------------------|-------| +| 1 | Multirate Service | 7.4.7 | + +### 7.3.11 Service specific information (SAR-assured) + +The sequence of fields in the service specific information (SAR-assured) parameter is shown in Table 7-18. + +**Table 7-18/Q.2630.3 – Sequence of fields in the service specific information (SAR-assured) parameter** + +| Field No. | Field | Ref. | +|-----------|-----------------------------------------------------|-------| +| 1 | Segmentation and Reassembly (Assured Data Transfer) | 7.4.8 | + +### 7.3.12 Service specific information (SAR-unassured) + +The sequence of fields in the service specific information (SAR-unassured) parameter is shown in Table 7-19. + +**Table 7-19/Q.2630.3 – Sequence of fields in the service specific information (SAR-unassured) parameter** + +| Field No. | Field | Ref. | +|-----------|-------------------------------------------------------|-------| +| 1 | Segmentation and Reassembly (Unassured Data Transfer) | 7.4.9 | + +### 7.3.13 Test connection indicator + +The test connection indicator parameter has no fields, i.e., the parameter length is always zero. + +### 7.3.14 Path type + +The sequence of fields in the path type parameter is shown in Table 7-20. + +**Table 7-20/Q.2630.3 – Sequence of fields in the path type parameter** + +| Field No. | Field | Ref. | +|-----------|-------------------------------|--------| +| 1 | AAL Type 2 Path QoS Codepoint | 7.4.21 | + +If the path type parameter is not included, the path type shall be considered to be the network default stringent QoS class. + +### 7.3.15 Service specific information (Audio Extended) + +The sequence of fields in the service specific information (Audio Extended) parameter is shown in Table 7-21. + +**Table 7-21/Q.2630.3 – Sequence of fields in the service specific information (Audio Extended) parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------------|--------| +| 1 | Audio extended service | 7.4.19 | +| 2 | Organizational unique identifier | 7.4.5 | + +### 7.3.16 Service specific information (Multirate Extended) + +The sequence of fields in the service specific information (Multirate Extended) parameter is shown in Table 7-22. + +**Table 7-22/Q.2630.3 – Sequence of fields in the service specific information (Multirate Extended) parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------|--------| +| 1 | Multirate extended service | 7.4.20 | + +### 7.3.17 Preferred service specific information (Audio Extended) + +The sequence of fields in the preferred service specific information (Audio Extended) parameter is shown in Table 7-23. + +**Table 7-23/Q.2630.3 – Sequence of fields in the preferred service specific information (Audio Extended) parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------------|--------| +| 1 | Audio extended service | 7.4.19 | +| 2 | Organizational unique identifier | 7.4.5 | + +### 7.3.18 Preferred service specific information (Multirate Extended) + +The sequence of fields in the preferred service specific information (Multirate Extended) parameter is shown in Table 7-24. + +**Table 7-24/Q.2630.3 – Sequence of fields in the preferred service specific information (Multirate Extended) parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------|--------| +| 1 | Multirate extended service | 7.4.20 | + +### 7.3.19 Preferred link characteristics + +The sequence of fields in the preferred link characteristics parameter is shown in Table 7-25. + +**Table 7-25/Q.2630.3 – Sequence of fields in the preferred link characteristics parameter** + +| Field No. | Field | Ref. | +|-----------|--------------------------|----------| +| 1 | Maximum CPS-SDU Bit Rate | (Note 1) | +| 2 | Average CPS-SDU Bit Rate | (Note 1) | +| 3 | Maximum CPS-SDU Size | (Note 2) | +| 4 | Average CPS-SDU Size | (Note 2) | + +NOTE 1 – This field is coded as a CPS-SDU Bit Rate field (see 7.4.11). +NOTE 2 – This field is coded as a CPS-SDU Size field (see 7.4.12). + +### 7.3.20 Modify support for link characteristics + +The modify support for link characteristics parameter has no fields, i.e., the parameter length is always zero. + +### 7.3.21 Modify support for service specific information + +The modify support for service specific information parameter has no fields, i.e., the parameter length is always zero. + +### 7.3.22 Served user correlation ID + +The sequence of fields in the served user correlation ID parameter is shown in Table 7-26. + +**Table 7-26/Q.2630.3 – Sequence of fields in the served user correlation ID parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------------|--------| +| 1 | Served User Correlation ID value | 7.4.22 | + +### 7.3.23 Origination E.164 service endpoint address + +The sequence of fields in the origination E.164 [10] service endpoint address parameter is shown in Table 7-27. + +**Table 7-27/Q.2630.3 – Sequence of fields in the origination E.164 service endpoint address parameter** + +| Field No. | Field | Ref. | +|-----------|-------------------|--------| +| 1 | Nature of Address | 7.4.13 | +| 2 | E.164 Address | 7.4.14 | + +### 7.3.24 Origination NSAP service endpoint address + +The sequence of fields in the origination NSAP [5] service endpoint address parameter is shown in Table 7-28. + +**Table 7-28/Q.2630.3 – Sequence of fields in the origination NSAP service endpoint address parameter** + +| Field No. | Field | Ref. | +|-----------|--------------|--------| +| 1 | NSAP Address | 7.4.15 | + +### 7.3.25 Automatic congestion control + +The sequence of fields in the Automatic congestion control parameter is shown in Table 7-29. + +**Table 7-29/Q.2630.3 – Sequence of fields in the automatic congestion control parameter** + +| Field No. | Field | Ref. | +|-----------|--------------------------------------------|--------| +| 1 | AAL type 2 Node Automatic Congestion Level | 7.4.23 | + +### 7.3.26 Connection priority + +The sequence of fields in the connection priority parameter is shown in Table 7-30. + +**Table 7-30/Q.2630.3 – Sequence of fields in the connection priority parameter** + +| Field No. | Field | Ref. | +|-----------|----------|--------| +| 1 | Priority | 7.4.24 | + +### 7.3.27 Hop counter + +The sequence of fields in the hop counter parameter is shown in Table 7-31. + +**Table 7-31/Q.2630.3 – Sequence of fields in the hop counter parameter** + +| Field No. | Field | Ref. | +|-----------|------------------------|--------| +| 1 | AAL type 2 Hop Counter | 7.4.25 | + +### 7.3.28 TAR controlled connection + +The TAR Controlled Connection parameter has no fields, i.e., the parameter length is always zero. + +### 7.3.29 Preferred fixed bandwidth transfer capability + +The sequence of fields in the preferred fixed bandwidth transfer capability parameter is shown in Table 7-32. + +**Table 7-32/Q.2630.3 – Sequence of fields in the preferred fixed bandwidth transfer capability parameter** + +| Field No. | Field | Ref. | +|-----------|---------------------------------------------------------|----------| +| 1 | Peak CPS bit rate | (Note 1) | +| 2 | CPS token bucket size associated with Peak CPS bit rate | (Note 2) | +| 3 | Maximum allowed CPS packet size | 7.4.28 | + +NOTE 1 – This field is coded as a CPS Bit rate field (see 7.4.26). +NOTE 2 – This field is coded as a CPS Token Bucket Size field (see 7.4.27). + +### 7.3.30 Preferred variable bandwidth stringent transfer capability + +The sequence of fields in the preferred variable bandwidth stringent transfer capability parameter is shown in Table 7-33. + +**Table 7-33/Q.2630.3 – Sequence of fields in the preferred variable bandwidth stringent transfer capability parameter** + +| Field No. | Field | Ref. | +|-----------|---------------------------------------------------------|----------| +| 1 | Peak CPS bit rate | (Note 1) | +| 2 | CPS token bucket size associated with Peak CPS bit rate | (Note 2) | +| 3 | Maximum allowed CPS packet size | 7.4.28 | +| 4 | Source Traffic Type | 7.4.29 | + +NOTE 1 – This field is coded as a CPS Bit rate field (see 7.4.26). +NOTE 2 – This field is coded as a CPS Token Bucket Size field (see 7.4.27). + +### 7.3.31 Preferred variable bandwidth tolerant transfer capability + +The sequence of fields in the preferred variable bandwidth tolerant transfer capability parameter is shown in Table 7-34. + +**Table 7-34/Q.2630.3 – Sequence of fields in the preferred variable bandwidth tolerant transfer capability parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------------------------------------------|----------| +| 1 | Peak CPS bit rate | (Note 1) | +| 2 | CPS token bucket size associated with Peak CPS bit rate | (Note 2) | +| 3 | Sustainable CPS bit rate | (Note 1) | +| 4 | CPS token bucket size associated with Sustainable CPS bit rate | (Note 2) | +| 5 | Maximum allowed CPS packet size | 7.4.28 | + +NOTE 1 – This field is coded as a CPS Bit rate field (see 7.4.26). +NOTE 2 – This field is coded as a CPS Token Bucket Size field (see 7.4.27). + +### 7.3.32 Fixed bandwidth transfer capability + +The sequence of fields in the fixed bandwidth transfer capability parameter is shown in Table 7-35. + +**Table 7-35/Q.2630.3 – Sequence of fields in the fixed bandwidth transfer capability parameter** + +| Field No. | Field | Ref. | +|-----------|---------------------------------------------------------|----------| +| 1 | Peak CPS bit rate | (Note 1) | +| 2 | CPS token bucket size associated with Peak CPS bit rate | (Note 2) | +| 3 | Maximum allowed CPS packet size | 7.4.28 | + +NOTE 1 – This field is coded as a CPS Bit rate field (see 7.4.26). +NOTE 2 – This field is coded as a CPS Token Bucket Size field (see 7.4.27). + +### 7.3.33 Variable bandwidth stringent transfer capability + +The sequence of fields in the variable bandwidth stringent transfer capability parameter is shown in Table 7-36. + +**Table 7-36/Q.2630.3 – Sequence of fields in the variable bandwidth stringent transfer capability parameter** + +| Field No. | Field | Ref. | +|-----------|---------------------------------------------------------|----------| +| 1 | Peak CPS bit rate | (Note 1) | +| 2 | CPS token bucket size associated with Peak CPS bit rate | (Note 2) | +| 3 | Maximum allowed CPS packet size | 7.4.28 | +| 4 | Source Traffic Type | 7.4.29 | + +NOTE 1 – This field is coded as a CPS Bit rate field (see 7.4.26). +NOTE 2 – This field is coded as a CPS Token Bucket Size field (see 7.4.27). + +### 7.3.34 Variable bandwidth tolerant transfer capability + +The sequence of fields in the variable bandwidth tolerant transfer capability parameter is shown in Table 7-37. + +**Table 7-37/Q.2630.3 – Sequence of fields in the variable bandwidth tolerant transfer capability parameter** + +| Field No. | Field | Ref. | +|-----------|----------------------------------------------------------------|----------| +| 1 | Peak CPS bit rate | (Note 1) | +| 2 | CPS token bucket size associated with Peak CPS bit rate | (Note 2) | +| 3 | Sustainable CPS bit rate | (Note 1) | +| 4 | CPS token bucket size associated with Sustainable CPS bit rate | (Note 2) | +| 5 | Maximum allowed CPS packet size | 7.4.28 | + +NOTE 1 – This field is coded as a CPS Bit rate field (see 7.4.26). +NOTE 2 – This field is coded as a CPS Token Bucket Size field (see 7.4.27). + +### 7.3.35 Transfer capability support + +The transfer capability support parameter has no fields, i.e., the parameter length is always zero. + +## 7.4 Field specification of the AAL type 2 signalling protocol parameters + +### 7.4.1 Compatibility + +The structure of the compatibility field is shown in Table 7-38; the field is a fixed size field of 1 octet. + +**Table 7-38/Q.2630.3 – Structure of the compatibility field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------|-----------------------------|---|-----------------------|----------------|----------|-----------------------------|---|-----------------------| +| pass-on not possible | | | | general action | | | | Octet 1 | +| reserved | send notification indicator | | instruction indicator | | reserved | send notification indicator | | instruction indicator | + +The following codes are used in the subfields of the compatibility information field. + +#### a) *Send notification indicator* + +- 0 Do not send notification. +- 1 Send notification. + +#### b) *Instruction indicator* + +- 00 Pass on message or parameter (see Note 1). +- 01 Discard parameter (see Note 2). +- 10 Discard message. +- 11 Release Connection. + +NOTE 1 – When used in a "pass-on not possible" instruction indicator, value "00" is interpreted so as to release the connection. + +NOTE 2 – When used as message compatibility field, value "01" should not be used. If received, it is interpreted so as to discard the message. + +### 7.4.2 Signalling association identifier + +The structure of the signalling association identifier field is shown in Table 7-39; the field is a fixed size field of 4 octets. + +**Table 7-39/Q.2630.3 – Structure of the signalling association identifier field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|---|---|---|---|---|---|---|---------| +| Signalling association identifier | | | | | | | | Octet 1 | +| | | | | | | | | Octet 2 | +| | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | + +The coding is implementation dependent. + +If the signalling association identifier is used as a destination signalling association identifier that is not known, the field is set to zero indicating the value "unknown". + +If the signalling association identifier is used as an originating signalling association identifier, the value zero shall not be used. + +### 7.4.3 AAL type 2 path identifier + +The structure of the AAL type 2 path identifier field is shown in Table 7-40; the field is a fixed size field of 4 octets. + +**Table 7-40/Q.2630.3 – Structure of the AAL type 2 path identifier field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------|---|---|---|---|---|---|---|---------| +| AAL type 2 path identifier | | | | | | | | Octet 1 | +| | | | | | | | | Octet 2 | +| | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | + +The coding is implementation dependent. It identifies unambiguously an AAL type 2 path between a pair of adjacent AAL type 2 nodes. A value of "0" in all octets indicates "Null"; therefore, the all zero code cannot be used to identify an AAL type 2 path. + +NOTE – When the AAL type 2 path is a switched VCC between two adjacent AAL type 2 nodes, the procedure defined in 9.2/Q.2941.2 [27] may be used to assign the AAL type 2 path identifier field value at the time of the VCC establishment. + +### 7.4.4 Channel identifier + +The structure of the channel identifier field is shown in Table 7-41; the field is a fixed size field of 1 octet. + +**Table 7-41/Q.2630.3 – Structure of the channel identifier field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Channel identifier | | | | | | | | Octet 1 | + +The coding reflects the Channel Identifier (CID) as specified in ITU-T Rec. I.363.2 [1]. CID values permitted in this field range from "8" to "255" inclusive. A value of "0" indicates "Null". + +### 7.4.5 Organizational unique identifier + +The structure of the organizational unique identifier field is shown in Table 7-42; the field is a fixed size field of 3 octets. + +**Table 7-42/Q.2630.3 – Structure of the organizational unique identifier field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|---|---|---|---|---|---|---|---------| +| Organizational unique identifier | | | | | | | | Octet 1 | +| | | | | | | | | Octet 2 | +| | | | | | | | | Octet 3 | + +The coding reflects the Organizational Unique Identifier (OUI) specified by IEEE 802-2001 [11] clause 5.1. + +### 7.4.6 Audio service + +The audio service for the AAL type 2 is defined in ITU-T Rec. I.366.2 [8]. The structure of the audio service field is shown in Table 7-43; the field is a fixed size field of 5 octets. + +**Table 7-43/Q.2630.3 – Structure of the audio service field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|----------|-------|-------|------|-----|-----|----------|---------| +| Profile Type | Reserved | | | | | | | Octet 1 | +| Profile identifier | | | | | | | | Octet 2 | +| FRM | CMD | MF-R2 | MF-R1 | DTMF | CAS | FAX | A-/μ-Law | Octet 3 | +| Maximum length of frame mode data | | | | | | | | Octet 4 | +| | | | | | | | | Octet 5 | + +The following codes are used in the subfields of the audio service field: + +- a) *Profile type* + - 00 The "Profile Identifier" designates a profile specified in ITU-T Rec. I.366.2 [8]; the organizational unique identifier field in the same parameter is ignored. + - 01 The "Profile Identifier" designates a profile specified by an organization designated by the organizational unique identifier field in the same parameter. + - 10 The "Profile Identifier" designates a custom profile; the organizational unique identifier field in the same parameter is ignored. + - 11 Reserved. +- b) *Profile identifier* + +The "Profile Identifier" designates a profile as specified in either ITU-T Rec. I.366.2 [8], by an organization designated by the organizational unique identifier field in the same parameter, or a custom profile depending of the value of the "Profile Type". +- c) + - FRM + - 0: Transport of frame mode data disabled + - 1: Transport of frame mode data enabled + - CMD + - 0: Transport of circuit mode data (64 kbit/s) disabled + - 1: Transport of circuit mode data (64 kbit/s) enabled + - MF-R2 + - 0: Transport of multi-frequency R2 dialled digits disabled + - 1: Transport of multi-frequency R2 dialled digits enabled + - MF-R1 + - 0: Transport of multi-frequency R1 dialled digits disabled + - 1: Transport of multi-frequency R1 dialled digits enabled + +- DTMF 0: Transport of dual tone multi-frequency dialled digits disabled +1: Transport of dual tone multi-frequency dialled digits enabled +- CAS 0: Transport of channel associated signalling disabled +1: Transport of channel associated signalling enabled +- FAX 0: Transport of demodulated facsimile data disabled +1: Transport of demodulated facsimile data enabled +- A-/ $\mu$ -Law 0: Interpretation of generic PCM coding: A-Law +1: Interpretation of generic PCM coding: $\mu$ -Law + +### 7.4.7 Multirate service + +The multirate service for the AAL type 2 is defined in ITU-T Rec. I.366.2 [8]. The structure of the multirate service field is shown in Table 7-44; the field is a fixed size field of 3 octets. + +**Table 7-44/Q.2630.3 – Structure of the multirate service field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------|----------|---|---------------------------------------|---|---|---|---|---------| +| FRM | Reserved | | Multiplier n for $n \times 64$ kbit/s | | | | | Octet 1 | +| Maximum length of | | | | | | | | Octet 2 | +| frame mode data | | | | | | | | Octet 3 | + +- FRM 0: Transport of frame mode data disabled +1: Transport of frame mode data enabled +- n $1 \leq n \leq 31$ Multiplier for $n \times 64$ kbit/s + +### 7.4.8 Segmentation and reassembly (Assured data transfer) + +The segmentation and reassembly service for the AAL type 2 is defined in ITU-T Rec. I.366.1 [9]. The structure of the segmentation and reassembly (assured data transfer) field is shown in Table 7-45; the field is a fixed size field of 14 octets. + +**Table 7-45/Q.2630.3 – Structure of the segmentation and reassembly (assured data transfer) field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------|---|---|---|---|---|---|---|----------| +| Maximum length of | | | | | | | | Octet 1 | +| SSSAR-SDU | | | | | | | | Octet 2 | +| in the forward direction | | | | | | | | Octet 3 | +| Maximum length of | | | | | | | | Octet 4 | +| SSSAR-SDU | | | | | | | | Octet 5 | +| in the backward direction | | | | | | | | Octet 6 | +| Maximum length of SSCOP-SDU | | | | | | | | Octet 7 | +| in the forward direction | | | | | | | | Octet 8 | +| Maximum length of SSCOP-SDU | | | | | | | | Octet 9 | +| in the backward direction | | | | | | | | Octet 10 | +| Maximum length of SSCOP-UU | | | | | | | | Octet 11 | +| in the forward direction | | | | | | | | Octet 12 | +| Maximum length of SSCOP-UU | | | | | | | | Octet 13 | +| in the backward direction | | | | | | | | Octet 14 | + +### 7.4.9 Segmentation and reassembly (Unassured data transfer) + +The structure of the segmentation and reassembly (unassured data transfer) field is shown in Table 7-46; the field is a fixed size field of 7 octets. + +**Table 7-46/Q.2630.3 – Structure of the segmentation and reassembly (unassured data transfer) field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------|----------|---|---|---|---|---|---|-------------------------------| +| Maximum length of SSSAR-SDU in the forward direction | | | | | | | | Octet 1
Octet 2
Octet 3 | +| Maximum length of SSSAR-SDU in the backward direction | | | | | | | | Octet 4
Octet 5
Octet 6 | +| TED | Reserved | | | | | | | Octet 7 | + +TED 0: Transmission Error Detection disabled +1: Transmission Error Detection enabled + +### 7.4.10 Served user generated reference + +The structure of the served user generated reference field is shown in Table 7-47; the field is a fixed size field of 4 octets. + +**Table 7-47/Q.2630.3 – Structure of the served user generated reference field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|---|---|---|---|------------------------------------------| +| Served user generated reference | | | | | | | | Octet 1
Octet 2
Octet 3
Octet 4 | + +### 7.4.11 CPS-SDU bit rate + +The structure of the CPS-SDU bit rate field is shown in Table 7-48; the field is a fixed size field of 4 octets. + +**Table 7-48/Q.2630.3 – Structure of the CPS-SDU bit rate field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------|---|---|---|---|---|---|---|--------------------| +| CPS-SDU bit rate in the forward direction | | | | | | | | Octet 1
Octet 2 | +| CPS-SDU bit rate in the backward direction | | | | | | | | Octet 3
Octet 4 | + +This field may be used to convey the maximum CPS-SDU bit rate or the average CPS-SDU bit rate. + +The maximum CPS-SDU bit rate is defined as the maximum bandwidth, available to the AAL type 2 served user in the specified direction. The maximum bandwidth is the maximum ratio of the amount of bits transported during the inter-departure time between two subsequent CPS-SDUs, and that inter-departure time. Allowed values are 0 to 2048 kbit/s. The granularity is 64 bit/s. + +The average CPS-SDU bit rate is defined as the total expected amount of bits transported in the specified direction during the holding time of the connection, divided by the holding time of the connection. The average bit rate is also expected to be valid for the time interval between any two active periods. Allowed values are 0 to 2048 kbit/s. The granularity is 64 bit/s. + +### 7.4.12 CPS-SDU size + +The structure of the CPS-SDU size field is shown in Table 7-49; the field is a fixed size field of 2 octets. + +**Table 7-49/Q.2630.3 – Structure of the CPS-SDU size field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------|---|---|---|---|---|---|---|---------| +| CPS-SDU size in the forward direction | | | | | | | | Octet 1 | +| CPS-SDU size in the backward direction | | | | | | | | Octet 2 | + +This field may be used to convey the maximum CPS-SDU size or the average CPS-SDU size. + +The maximum CPS-SDU size is defined as the largest CPS-SDU size, in octets, allowed to be sent in the specified direction during the holding time of the connection. Allowed values are 1 to 45. + +The average CPS-SDU size is defined in the specified direction as the expected number of transported octets divided by the number of transported CPS-SDUs during the holding time of the connection. The average CPS-SDU size is also expected to be valid for the time interval between any two active periods. Allowed values are 1 to 45. + +### 7.4.13 Nature of address + +The structure of the nature of address field is shown in Table 7-50; the field is a fixed size field of 1 octet. + +**Table 7-50/Q.2630.3 – Structure of the nature of address field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------|------------------------|---|---|---|---|---|---|---------| +| Reserved | Nature of address code | | | | | | | Octet 1 | + +The "nature of address code" has the following meaning: + +| | | +|--------------------------|-------------------------------------------------| +| 0000000 | Spare | +| 0000001 | Subscriber number (national use) | +| 0000010 | Unknown (national use) (Note 1) | +| 0000011 | National (significant) number | +| 0000100 | International number | +| 0000101 | Network-specific number (national use) (Note 2) | +| 0000110
to
1101111 | } Spare | +| 1110000
to
1111110 | } Reserved for national use | +| 1111111 | Spare | + +NOTE 1 – This codepoint is used when the type of number is indicated using the digits in the E.164 Address field. The E.164 Address field is organized according to the network dialling plan; e.g., prefix digits might be present; in addition, escape digits may also be present. + +NOTE 2 – This codepoint is used to indicate an administration/service number specific to the serving network. + +### 7.4.14 E.164 address + +The structure of the E.164 address field is shown in Table 7-51; the field is a variable size field. + +**Table 7-51/Q.2630.3 – Structure of the E.164 address field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------|---|---|---|---|--------------------------------------------|---|---|---------| +| Field length | | | | | | | | Octet 1 | +| Reserved | | | | | First hexadecimal digit of address
---- | | | Octet 2 | +| | | | | | Last hexadecimal digit of address | | | Octet n | + +### 7.4.15 NSAP address + +The structure of the NSAP [5] address field is shown in Table 7-52; the field is a fixed size field of 20 octets. + +**Table 7-52/Q.2630.3 – Structure of the NSAP address field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------|---|---|---|---|---|---|---|----------| +| | | | | | | | | Octet 1 | +| NSAP | | | | | | | | Octet 20 | + +### 7.4.16 Cause value + +The structure of the cause value field is shown in Table 7-53; the field is a fixed size field of 2 octets. + +**Table 7-53/Q.2630.3 – Structure of the cause value field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------|-------|---|---|---|---|-----------------|---|---------| +| Reserved | | | | | | Coding standard | | Octet 1 | +| Reserved | Cause | | | | | | | Octet 2 | + +#### Coding Standard + +- 00 ITU-T standardized coding as described in ITU-T Recs Q.850 [6] and Q.2610 [7] +- 01 ISO/IEC standard (Note) +- 10 National standard (Note) +- 11 Standard defined for the network (either public or private) present on the network side of the interface (Note) + +NOTE – These other coding standards should be used only when the parameter contents cannot be represented with the ITU-T standardized coding. + +The procedures defined in clause 8 make use of ITU-T standardized codes described in ITU-T Recs Q.850 [6] and Q.2610 [7]. The codes are listed here for convenience. If there exists any difference in the names and codepoints of the following causes, the definitions in ITU-T Recs Q.850 and Q.2610 take precedence. + +#### *Code    Cause Description* + +| | | +|-----|---------------------------------------------------------------| +| 1 | Unallocated (unassigned) number | +| 3 | No route to destination | +| 25 | Exchange routing error | +| 31 | Normal, unspecified | +| 34 | No circuit/channel available | +| 38 | Network out of order | +| 41 | Temporary failure | +| 42 | Switching equipment congestion | +| 44 | Requested circuit/channel not available | +| 47 | Resource unavailable, unspecified | +| 93 | AAL parameters cannot be supported | +| 95 | Invalid message, unspecified | +| 96 | Mandatory information element is missing | +| 97 | Message type non-existent or not implemented | +| 99 | Information element/parameter non-existent or not implemented | +| 100 | Invalid information element contents | +| 102 | Recovery on timer expiry | +| 110 | Message with unrecognized parameter, discarded | +| 111 | Protocol error, unspecified | + +### **7.4.17 Diagnostics** + +The structure of the diagnostics field is shown in Table 7-54; the field is a variable size field. + +**Table 7-54/Q.2630.3 – Structure of the diagnostics field** + +![](69e5f1993021af230d08c08aac97d9df_img.jpg) + +| | | | | | | | | | +|--------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Field length | | | | | | | | Octet 1 | +| Diagnostic | | | | | | | | Octet 2 | +| | | | | | | | | Octet n | + +The coding is specified in ITU-T Rec. Q.2610 [7] except when associated with one of the following causes: + +- Message type non-existent or not implemented; +- Information element/parameter non-existent or not implemented; or +- Message with unrecognized parameter discarded. + +In these cases, the Diagnostics field is shown in Table 7-55; the field is a variable size field. + +**Table 7-55/Q.2630.3 – Structure of the diagnostics field for compatibility causes** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|----------------------|---|---|---|---------| +| Field length | | | | | | | | Octet 1 | +| Message identifier | | | | | | | | Octet 2 | +| first pair | | | | Parameter identifier | | | | Octet 3 | +| | | | | Field number | | | | Octet 4 | +| second pair | | | | Parameter identifier | | | | Octet 5 | +| | | | | Field number | | | | Octet 6 | +| last pair | | | | Parameter identifier | | | | Octet n | +| | | | | Field number | | | | | + +The diagnostics field for compatibility always starts – after the field length – with an octet containing the copy of the Message Identifier (of the message that gave rise to a compatibility diagnostic) followed by 0 to 125 octet pairs each containing a parameter identifier and a field number. If the field number octet is zero, the whole parameter is designated. + +### 7.4.18 Served user transport + +The structure of the served user transport field is shown in Table 7-56; the field is a variable size field. + +**Table 7-56/Q.2630.3 – Structure of the served user transport field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|---|---|---|---|---------| +| Field length | | | | | | | | Octet 1 | +| Served user transport | | | | | | | | Octet 2 | +| | | | | | | | | Octet n | + +The served user transport length can be from 1 to 254 octets. + +### 7.4.19 Audio extended service + +The Audio Extended service for the AAL type 2 is defined as "audio service" in ITU-T Rec. I.366.2 [14]. The structure of the audio extended service field is shown in Table 7-57; the field is a fixed size field of 5 octets. + +**Table 7-57/Q.2630.3 – Structure of the audio extended service field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|-----|----------|-------|------|-----|-----|----------|---------| +| Profile type | | Reserved | | | LB | RC | SYN | Octet 1 | +| Profile identifier | | | | | | | | Octet 2 | +| FRM | CMD | MF-R2 | MF-R1 | DTMF | CAS | FAX | A-/μ-Law | Octet 3 | +| Maximum length of frame mode data | | | | | | | | Octet 4 | +| | | | | | | | | Octet 5 | + +The following codes are used in the subfields of the audio service field: + +#### a) *Profile type* + +- 00 The "Profile Identifier" designates a profile specified in ITU-T Rec. I.366.2 [14], the organizational unique identifier field in the same parameter is ignored. +- 01 The "Profile Identifier" designates a profile specified by an organization designated by the organizational unique identifier field in the same parameter. + +10 The "Profile Identifier" designates a custom profile, the organizational unique identifier field in the same parameter is ignored. + +11 Reserved. + +#### b) *Profile identifier* + +The "Profile Identifier" designates a profile as specified in either ITU-T Rec. I.366.2 [14], by an organization designated by the organizational unique identifier field in the same parameter, or a custom profile depending of the value of the "profile Type". + +- c) +- LB 0: Loopback disabled +1: Loopback enabled + - RC 0: Transport of rate control commands disabled +1: Transport of rate control commands enabled + - SYN 0: Transport of synchronization of change in SSCS operation disabled +1: Transport of synchronization of change in SSCS operation enabled + - FRM 0: Transport of frame mode data disabled +1: Transport of frame mode data enabled + - CMD 0: Transport of circuit mode data (64 kbit/s) disabled +1: Transport of circuit mode data (64 kbit/s) enabled + - MF-R2 0: Transport of multi-frequency R2 dialled digits disabled +1: Transport of multi-frequency R2 dialled digits enabled + - MF-R1 0: Transport of multi-frequency R1 dialled digits disabled +1: Transport of multi-frequency R1 dialled digits enabled + - DTMF 0: Transport of dual tone multi-frequency dialled digits disabled +1: Transport of dual tone multi-frequency dialled digits enabled + - CAS 0: Transport of channel associated signalling disabled +1: Transport of channel associated signalling enabled + - FAX 0: Transport of demodulated facsimile data disabled +1: Transport of demodulated facsimile data enabled + - A-/μ-Law 0: Interpretation of generic PCM coding: A-Law +1: Interpretation of generic PCM coding: μ-Law + +### 7.4.20 Multirate extended service + +The structure of the multirate extended service field is shown in Table 7-58; the field is a fixed size field of 3 octets. + +**Table 7-58/Q.2630.3 – Structure of the multirate extended service field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----|----|-----------------------------------|--------------------------------|---|---|---|---|---------|--|--|--|--| +| FRM | LB | Reserved | Multiplier n for n × 64 kbit/s | | | | | Octet 1 | | | | | +| | | Maximum length of frame mode data | | | | | | Octet 2 | | | | | +| | | | | | | | | Octet 3 | | | | | + +- FRM 0: Transport of frame mode data disabled +1: Transport of frame mode data enabled + +- LB 0: Loopback disabled +1: Loopback enabled + +n 1 ≤ n ≤ 31 Multiplier for n × 64 kbit/s + +### 7.4.21 AAL type 2 path QoS codepoint + +The structure of the AAL type 2 path QoS codepoint field is shown in Table 7-59; the field is a fixed size field of 1 octet. + +**Table 7-59/Q.2630.3 – Structure of the AAL type 2 path QoS codepoint field** + +| | | | | | | | | +|-------------------------------|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| AAL type 2 path QoS codepoint | | | | | | | | + +Octet 1 + +The "AAL type 2 path QoS codepoint" has the following meaning: + +- 0: Reserved for assignment by ITU-T +- 1: Stringent class +- 2: Tolerant class +- 3,4: Reserved for assignment by ITU-T +- 5: Stringent bi-level class +- 6 to 127: Reserved for assignment by ITU-T +- 128 to 255: Reserved for network specific assignment + +The attributes of "stringent class", "tolerant class", and "stringent bi-level class" are those defined in ITU-T Rec. I.356 [13]. + +### 7.4.22 Served user correlation ID value + +The structure of the Served User Correlation ID value field is shown in Table 7-60; the field is a fixed size field of 1 octet. + +**Table 7-60/Q.2630.3 – Structure of the served user correlation ID value field** + +| | | | | | | | | +|----------------------------------|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Served user correlation ID value | | | | | | | | + +Octet 1 + +The Served User Correlation ID value adheres to the specifications in ITU-T Rec. I.366.2 [14]. + +### 7.4.23 AAL Type 2 node automatic congestion level + +The structure of the AAL type 2 Node Automatic Congestion Level field is shown in Table 7-61; the field is a fixed size field of 1 octet. + +**Table 7-61/Q.2630.3 – Structure of the AAL type 2 node automatic congestion level field** + +| | | | | | | | | +|------------------------------------------------------|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| AAL type 2 node automatic congestion level codepoint | | | | | | | | + +Octet 1 + +The "AAL type 2 Node Automatic Congestion Level Codepoint" has the following meaning: + +- 0000000 Spare +- 0000001 Congestion level 1 exceeded +- 0000010 Congestion level 2 exceeded +- 0000011 to 1111111 } Spare + +### 7.4.24 Priority + +The structure of the Priority field is shown in Table 7-62; the field is a fixed size field of 1 octet. + +**Table 7-62/Q.2630.3 – Structure of the priority field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------|---|---|---|---|----------|---|---|---------| +| Reserved | | | | | Priority | | | Octet 1 | + +The priority codepoint has the following meaning: + +- 0 0 0 Level 1 (highest) +- 0 0 1 Level 2 +- 0 1 0 Level 3 +- 0 1 1 Level 4 +- 1 0 0 Level 5 (lowest) +- 1 0 1 } Reserved +- to } +- 1 1 1 } + +### 7.4.25 AAL type 2 hop counter + +The structure of the AAL type 2 Hop Counter field is shown in Table 7-63; the field is a fixed size field of 1 octet. + +**Table 7-63/Q.2630.3 – Structure of the AAL type 2 hop counter field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|---|---|---|---|---|---|---|---------| +| AAL type 2 hop counter codepoint | | | | | | | | Octet 1 | + +The "AAL type 2 Hop Counter Codepoint" has the following meaning: The hop counter contains the binary value of the number of contiguous connection segments/bearer control associations that are allowed to complete the connection. + +### 7.4.26 CPS bit rate + +The structure of the CPS bit rate field is shown in Table 7-64; the field is a fixed size field of 6 octets. + +**Table 7-64/Q.2630.3 – Structure of the CPS bit rate field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------|---|---|---|---|---|---|---|-------------------------------| +| CPS bit rate in the forward direction | | | | | | | | Octet 1
Octet 2
Octet 3 | +| CPS bit rate in the backward direction | | | | | | | | Octet 4
Octet 5
Octet 6 | + +A CPS bit rate may be used as a Peak CPS bit rate or a Sustainable CPS bit rate according to ITU-T Rec. I.378 [19]. Allowed values are 0 to 16 384 kbit/s. The granularity is 64 bit/s. + +### 7.4.27 CPS token bucket size + +The structure of the CPS token bucket size field is shown in Table 7-65; the field is a fixed size field of 4 octets. + +**Table 7-65/Q.2630.3 – Structure of the CPS token bucket size field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------|---|---|---|---|---|---|---|--------------------| +| CPS token bucket size in the forward direction | | | | | | | | Octet 1
Octet 2 | +| CPS token bucket size in the backward direction | | | | | | | | Octet 3
Octet 4 | + +A CPS token bucket size represents a CPS token bucket size associated either with a Peak CPS bit rate or a Sustainable CPS bit rate according to ITU-T Rec. I.378 [19]. Allowed values are 48 to 4096 octets. + +### 7.4.28 Maximum allowed CPS packet size + +The structure of the CPS packet size field is shown in Table 7-66; the field is a fixed size field of 2 octets. + +**Table 7-66/Q.2630.3 – Structure of the CPS packet size field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------|---|---|---|---|---|---|---|---------| +| CPS packet size in the forward direction | | | | | | | | Octet 1 | +| CPS packet size in the backward direction | | | | | | | | Octet 2 | + +A CPS packet size may be used as maximum CPS packet size, in octets, allowed to be sent in the specified direction during the holding time of the connection according to ITU-T Rec. I.378 [19]. Allowed values are 4 to 48 octets. + +### 7.4.29 Source traffic type + +The structure of the source traffic type field is shown in Table 7-67; the field is a fixed size field of 1 octet. + +**Table 7-67/Q.2630.3 – Structure of source traffic type field** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|---|---|---|---|---|---|---|---------| +| Source traffic type codepoint | | | | | | | | Octet 1 | + +A source traffic type may be used in the specification of a variable bandwidth stringent transfer capability according to ITU-T Rec. I.378 [19]. + +Each source traffic type represented by a codepoint in the Source Traffic Type field must be compliant to the definition of source traffic type in ITU-T Rec. I.378 [19]. + +The following codes are used for the Source Traffic Type field: + +00000000 STT unknown + +00000001 AMR [30] coded speech + +00000010 } +to } Reserved for ITU-T assignment +01111111 } + +10000000 } +to } Reserved for assignment by IMT-2000 family members +10111111 } + +11000000 } +to } Reserved for network specific assignment +11111111 } + +# 8 Procedure of the AAL type 2 signalling protocol + +Before an ATM VCC (AAL type 2 path) is put into service between a pair of adjacent AAL type 2 nodes, certain actions need to be performed. An identifier called the AAL type 2 path identifier is assigned to the ATM VCC. This identifier is used to refer to the ATM VCC in the AAL type 2 signalling protocol messages. The AAL type 2 path identifier shall uniquely identify the ATM VCC between the two adjacent AAL type 2 nodes. + +On any ATM VCC used for AAL type 2 connections, all CID values from "8" to "255" are available for assignment. + +Any time a new ATM VCC is put into service, the ownership of the ATM VCC shall be determined before AAL type 2 connections are established in it. In case of switched ATM VCC, the owner of the VCC shall be the AAL type 2 node that initiated the establishment of the VCC. In case of PVC and soft PVC, it is the responsibility of the management system to determine the owner of the VCC. + +The nodal function is informed by layer management of a newly established AAL type 2 path by the use of the ADD-PATH.indication primitive containing the adjacent AAL type 2 node identifier, the AAL type 2 path identifier, and the ownership. The nodal function is informed by layer management of the removal of an AAL type 2 path by use of the REMOVE-PATH.indication primitive containing the adjacent AAL type 2 node identifier and the AAL type 2 path identifier. + +In order to minimize the likelihood of CID collision, the following CID allocation mechanism shall be used: + +- if the AAL type 2 node owns the AAL type 2 path that carries the new connection, it allocates CID values from CID value 8 upwards; and +- if the AAL type 2 node does not own the AAL type 2 path that carries the new connection, it allocates CID values from CID value 255 downwards. + +Each AAL type 2 connection request (regardless of coming directly from an AAL type 2 served user or from an adjacent AAL type 2 node) shall contain an AAL type 2 service endpoint address which indicates the destination of the intended AAL type 2 connection instance. This information is used to route the AAL type 2 connection via the AAL type 2 network to its destination service endpoint. In capability set 3, the supported address formats are: NSAP and E.164. + +It is up to the application area or the operator of a particular network to decide what addressing plan is used in the AAL type 2 network. The addressing plan in the AAL type 2 network can be a reuse of the addressing plan in the underlying ATM network but it can also be an independent addressing plan defined exclusively for the AAL type 2 network. + +NOTE – Causes in the procedures defined in clause 8 specify which ITU-T standardized code should be used in cause parameters of AAL type 2 signalling protocol messages. Implementation dependent non-standardized causes may be used for AAL type 2 signalling entity internal processing and for A2SU-SAP and LM-SAP cause primitive parameters. + +The following procedures may be supported as a network option: + +- a) Connection priority; +- b) Automatic congestion control (see ITU-T Rec. Q.542 [18]); +- c) Hop Counter Procedure; +- d) Temporary Alternative Routing Procedure (see ITU-T Rec. E.412 [17]). + +## 8.1 Compatibility + +### 8.1.1 General requirements on receipt of unrecognized signalling information + +It may happen that a node receives unrecognized signalling information, i.e., messages, parameter types or subfield values. This can typically be caused by the upgrading of the signalling system used by other nodes in the network. In these cases, the following compatibility procedures are invoked to ensure the predictable network behaviour. + +All messages and parameters shall include a compatibility field generated by the nodal function. + +The procedures to be used on receipt of unrecognized information make use of: + +- compatibility field received in the same message as the unrecognized information; +- the cause parameter containing a cause value and diagnostics; +- the confusion message and the release request message (maintaining the link associated signalling relationship); and +- the release confirm message, the reset confirm message, the block confirm message, and the unblock confirm message (terminating the link associated signalling relationship). + +The following causes are used: + +- "message type non-existent or not implemented"; +- "information element/parameter non-existent or not implemented"; or +- "message with unrecognized parameter discarded". + +For all the above causes a diagnostic field is included containing, dependant on the cause, the message identifier and zero, one, or more pairs of parameter identifier and field number. + +The procedures are based on the following assumptions: + +- i) Since nodes can be both national and international nodes, the compatibility mechanism is applicable to the national and international network. +- ii) If a node receives a confusion message, a release request message, a release confirm message, a reset confirm message, a block confirm message, or an unblock confirm message indicating an unrecognized message or parameter received, it assumes interaction with a node supporting a different functional level. + +NOTE 1 – A node may be at a different functional level due to having implemented a different capability set or another subset of the protocol specified in this Recommendation. + +When an unrecognized parameter or message is received, the node will find some corresponding instructions contained in the parameter compatibility information or message compatibility field respectively. The message compatibility field contains the instructions specific for the handling of the complete message. + +The instruction indicators consist of two subfields, one to indicate how to handle unrecognized parameters or messages and the other to indicate what to do when an unrecognized parameter or message cannot be passed on. The following general rules apply to the interpretation of these instruction indicators: + +- a) "Reserved" subfields of the compatibility field are not examined. They may be used by future capability sets of this Recommendation; in this case, the future capability sets will set the currently defined instruction indicators to a reasonable value for nodes implementing the current capability set. This rule ensures that more types of instructions can be defined in the future without creating a backward compatibility problem. +- b) At an AAL type 2 node, the connection is released, using normal release procedures, if the instruction indicator is set to "release connection". +- c) At an AAL type 2 node if the instruction indicator is set to: "Discard message", or "Discard parameter", the message or parameter is discarded, as instructed. If the send notification indicator is set to "send notification", the appropriate message is issued towards the node that sent the unrecognized information: + - A confusion message is sent in response to an establish request message, an establish confirm message or in response to an unrecognized message. + - The appropriate confirm message is sent in response to a release request message, block request message, unblock request message, or reset request message. + - No response is returned in response to a confusion message, release confirm message, block confirm message, unblock confirm message, or reset confirm message. +- d) At an AAL type 2 node, if the instruction indicator is set to "pass-on", the unrecognized message or parameter is passed to the link associated signalling relationship on the other side of the AAL type 2 switch used for this connection. If the ability to "pass-on" is not possible at an AAL type 2 switch, then the instruction indicators "pass-on not possible" are examined. + +NOTE 2 – Examples of where "pass-on" might not be possible are: At AAL type 2 service endpoints, or in AAL type 2 switches in inter-operator situations, where "pass-on" might depend on bilateral agreements. +- e) For the case of an unrecognized parameter, it is possible for the instruction to require that either the unrecognized parameter or the whole message be discarded. This provides for the case where the sending node determines that it is not acceptable for the message to continue being processed without this parameter. + +### 8.1.2 Procedures for the handling of the unrecognized messages or parameters + +If the unrecognized signalling information is received, an ERROR.indication primitive with an appropriate cause (described in the following subclauses) is sent to layer management, except when the action taken is to pass on the message or parameter transparently. + +A confusion message must not be issued in response to the following messages: + +- | | | | +|-------------------|-------------------|-------------------| +| • Confusion | • Block request | • Block confirm | +| • Release request | • Unblock request | • Unblock confirm | +| • Release confirm | • Reset request | • Reset confirm | + +Any unrecognized parameters received in the following messages are discarded: + +- | | | | +|-------------------|-----------------|-------------------| +| • Confusion | • Block confirm | • Unblock confirm | +| • Release confirm | • Reset confirm | | + +#### 8.1.2.1 Unrecognized messages + +Depending on the instructions received in the message compatibility field, a node receiving an unrecognized message will either: + +- a) transfer the message transparently; +- b) discard the message; +- c) discard the message and send notification; or +- d) release the connection. + +The release request in case d) and the confusion message in case c) shall include the cause "Message type non-existent or not implemented", followed by a diagnostic field containing only the message identifier. + +#### 8.1.2.2 Unrecognized parameters + +Unexpected parameters (a parameter in the "wrong" message) are handled like unrecognized parameters. + +Depending on the instructions received in the parameter compatibility information field, a node receiving an unrecognized parameter will either: + +- a) transfer the parameter transparently; +- b) discard the parameter; +- c) discard the parameter and send notification; +- d) discard the message; +- e) discard the message and send notification; or +- f) release the connection. + +In case c), the confusion message shall include the cause "Information element/parameter non-existent or not implemented" followed by a diagnostic field containing the message identifier and containing pairs of parameter identifier and field number for each unrecognized parameter; the field number in each pair is set to "zero". + +In case e), the confusion message shall include the cause "Message with unrecognized parameter discarded", followed by a diagnostic field containing the message identifier and a parameter identifier (of the first detected unrecognized parameter which caused the message to be discarded) and a field number set to "zero". A confusion message may refer to multiple unrecognized parameters. + +A node receiving a message including multiple unrecognized parameters shall process the different instruction indicators, associated with those parameters, according to the following order: + +- 1) release the connection; +- 2) discard the message and send notification; +- 3) discard the message. + +A release request message shall include the cause "Information element/parameter non-existent or not implemented" followed by a diagnostic field containing the message identifier, the parameter identifier (of the first detected unrecognized parameter which caused the connection to be released), and a field number set to "zero". + +If a release request message is received containing an unrecognized parameter, depending on the instructions received in the parameter compatibility field, the node will either: + +- transfer the parameter transparently; +- discard the parameter; or + +- discard the parameter and send a cause "Information element/parameter non-existent or not implemented", in the release confirm message; the diagnostic field contains the message identifier and one or more pairs of parameter identifier and field number indicating all parameters that match the cause value; the field number of all pairs contains the null value. + +If a block request message is received containing an unrecognized parameter, depending on the instructions received in the parameter compatibility field, the node will either: + +- discard the parameter; or +- discard the parameter and send a cause "Information element/parameter non-existent or not implemented", in the block confirm message; the diagnostic field contains the message identifier and one or more pairs of parameter identifier and field number indicating all parameters that match the cause value; the field number of all pairs contains the null value. + +If an unblock request message is received containing an unrecognized parameter, depending on the instructions received in the parameter compatibility field, the node will either: + +- discard the parameter; or +- discard the parameter and send a cause "Information element/parameter non-existent or not implemented", in the unblock confirm message; the diagnostic field contains the message identifier and one or more pairs of parameter identifier and field number indicating all parameters that match the cause value; the field number of all pairs contains the null value. + +If a reset request message is received containing an unrecognized parameter, depending on the instructions received in the parameter compatibility field, the node will either: + +- discard the parameter; or +- discard the parameter and send a cause "Information element/parameter non-existent or not implemented", in the reset confirm message; the diagnostic field contains the message identifier and one or more pairs of parameter identifier and field number indicating all parameters that match the cause value; the field number of all pairs contains the null value. + +#### 8.1.2.3 Unrecognized fields + +There exists no specific compatibility information for each field. For all fields contained in a parameter, the compatibility information of the parameter applies. + +Any value in a subfield that is marked as "spare", "reserved" or "national use" is regarded as unrecognized and the procedures as stated for unrecognized parameters apply except that the field number is coded in the diagnostics field. + +### 8.1.3 Procedures for the handling of responses indicating unrecognized information has been sent + +Action taken on receipt of responses indicating unrecognized information has been sent at an originating or terminating AAL type 2 node will depend on the connection state and the affected service. + +The definition of any procedure that is outside the basic connection setup protocol, as defined in this Recommendation, should include procedures for handling responses that indicate that another node has received, but not recognized, information belonging to that procedure. The procedure receiving this response should take the appropriate actions. + +The default action taken on receipt of a confusion message is to discard the message without disrupting normal connection processing. + +## 8.2 Nodal functions + +Interworking with AAL type 2 nodes that conform only to ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16] is specified in Annex C; the procedures in the main body of this Recommendation exclusively describe the AAL type 2 signalling control protocol capability set 3. + +### 8.2.1 Nodal functions for AAL type 2 nodes with served user interaction + +#### 8.2.1.1 Connection control + +##### 8.2.1.1.1 Successful connection set up + +###### 8.2.1.1.1.1 Actions at the originating AAL type 2 service endpoint + +When the nodal function receives an ESTABLISH.request primitive from the AAL type 2 served user, the following parameters are mandatory: + +- Destination Endpoint Address; and +- Transfer Capability. + +When the nodal function receives an ESTABLISH.request primitive from the AAL type 2 served user, the restrictions on the optionality of the parameters used only for interworking with CS-1 or CS-2 nodes is described in Annex C. These optional parameters are the following: + +- The Preferred Transfer Capability; +- Transfer Capability Support; +- Link Characteristics; +- Preferred Link Characteristics; +- Modify Support for Link Characteristics; +- Preferred Service Specific Information; +- Modify Support for Service Specific Information; +- Service Specific Information (Audio); and +- Service Specific Information (Multirate). + +No optionality restrictions apply to the other parameters. + +The nodal function analyses the routing information and selects a route with sufficient AAL type 2 path resources on a path with the requested path type (or network default if the path type is not specified) to the succeeding AAL type 2 node. It then selects an AAL type 2 path from within that route which is able to accommodate the new connection. + +NOTE 1 – Routing typically is based on: + +- Addressing information; +- The Test Connection Indicator; +- Transfer Capability; +- Requested Path Type; +- Automatic congestion control and the congestion level in the routing tables; and +- Temporary Alternative Routing control (see ITU-T Rec. E.412 [17]). + +When the nodal function selects a route, the connection priority information, if received from the AAL Type 2 served user, is used to select a route that has sufficient AAL type 2 path resources to the succeeding AAL type 2 node. + +Under the normal condition, when the network is not congested and the AAL Type 2 service endpoint has the necessary resources to complete it, the connection establishment is processed without special treatments. + +NOTE 2 – In times of network congestion, when the AAL Type 2 service endpoint does not have sufficient resources to complete all of the incoming connection establishment requests, as one option, the AAL Type 2 service endpoint may give preferential treatments based on the priority level. + +NOTE 3 – The preferential treatment should include access to reserved network resources, e.g.: + +- the highest priority connections are given access to available network resources including the resources reserved for highest priority connections; +- the second highest priority connections are given access to available network resources including the resources reserved for the second highest priority connections, except for the resources reserved for the highest priority connections, and so on. + +NOTE 4 – Allocation of reserved network resources to specific priority levels is implementation specific, and is not a subject for standardization. + +AAL type 2 service endpoint internal resources are allocated for the new connection from the originating AAL type 2 served user to the outgoing AAL type 2 path. The connection priority information, if received, is taken into consideration when allocating these resources. + +On the selected outgoing AAL type 2 path, the CID and other resources (e.g., indicated by the Transfer Capability parameter) are allocated for the outgoing AAL type 2 link. The handling of interworking with CS-1 and CS-2 nodes is specified in Annex C. + +The following parameters – if they were conveyed by the originating AAL type 2 served user – shall not be modified by the nodal function: + +- the Destination Service Endpoint Address; +- the Origination Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; +- the Modify Support for Link Characteristics; +- the SSCS Information; +- the Preferred SSCS Information; +- the Modify Support for SSCS Information; +- the Path Type; +- the Connection Priority; and +- the Test Connection Indicator. + +The following parameters – if they were conveyed by the originating AAL type 2 served user – have significance to the served user only; therefore, they shall not be examined by the nodal function: + +- the Origination Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; + +- the SSCS Information; +- the Preferred SSCS Information; and +- the Modify Support for SSCS Information. + +An outgoing protocol entity instance is invoked and the following parameters are passed to it: + +- the Destination AAL type 2 Service Endpoint Address; +- the Transfer Capability; +- the AAL type 2 Path Identifier; and +- a CID value. + +The nodal function shall pass the following parameters to the outgoing protocol entity instance only if they were conveyed by the originating AAL type 2 served user: + +- the Origination AAL type 2 Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; +- the Modify Support for Link Characteristics; +- the SSCS Information; +- the Preferred SSCS Information; +- the Modify Support for SSCS Information; +- the Path Type; +- the Connection Priority; and +- the Test Connection Indicator. + +If the Temporary Alternative Routing control is applied a "TAR controlled connection" indication shall be passed to the outgoing protocol entity instance. + +If the hop counter procedure has been activated, a Hop Counter containing an initial count value shall be passed to the outgoing protocol entity instance. The initial count value of the Hop Counter shall be provisioned by the network operator on a per AAL type 2 node basis (31 maximum). + +NOTE 5 – Through-connection at AAL type 2 service endpoints is not specified by this Recommendation. It may be controlled by the AAL type 2 served user. + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, an ESTABLISH.confirm primitive is sent to the AAL type 2 served user. If a Transfer Capability Support parameter, a Modify Support for Link Characteristics, or a Modify Support for SSCS Information parameter was received from the outgoing protocol instance, the respective parameter shall be included in the ESTABLISH.confirm primitive. + +###### **8.2.1.1.1.2 Actions at the destination AAL type 2 service endpoint** + +Upon receiving an indication from an incoming protocol entity instance requesting a new connection, the nodal function checks the availability of the CID value and other resources (e.g., indicated by the Transfer Capability parameter), in the incoming AAL type 2 path. + +NOTE 1 – In case of interworking, the Transfer Capability and the Preferred Transfer Capability may be generated by the AAL type 2 service endpoint (see Annex C). + +The following parameters – if they were conveyed by the incoming protocol entity instance – shall not be modified by the nodal function: + +- the Destination Service Endpoint Address; +- the Origination Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; +- the Modify Support for Link Characteristics; +- the SSCS Information; +- the Preferred SSCS Information; +- the Modify Support for SSCS Information; +- the Path Type; +- the Connection Priority; and +- the Test Connection Indicator. + +The following parameters – if they were conveyed by the incoming protocol entity instance – have significance to the served user only; therefore, they shall not be examined by the nodal function: + +- the Origination Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the SSCS Information; +- the Preferred SSCS Information; and +- the Modify Support for SSCS Information. + +If the Test Connection Indicator parameter is present, a "locally blocked" or "remotely blocked" AAL type 2 path shall be acceptable for the incoming connection. + +If the CID and the other resources are available for the new connection, they are allocated to the new connection and then the AAL type 2 service endpoint address is examined. The nodal function determines that the destination AAL type 2 service endpoint has been reached. + +When the nodal function checks the availability of resources in the incoming AAL type 2 path, the Connection Priority information, if received, is taken into consideration. + +Under the normal condition, when the network is not congested and the AAL Type 2 service endpoint has the necessary resources to complete it, the connection establishment is processed without special treatments (see Notes in 8.2.1.1.1.1). + +If a Temporary Alternative Routing (TAR) control parameter or a Hop Counter parameter is received, they shall be ignored. + +AAL type 2 service endpoint internal resources are allocated for the new connection from the incoming AAL type 2 path to the destination AAL type 2 served user. The connection priority information, if received, is taken into consideration when allocating these resources. + +The nodal function acknowledges the successful AAL type 2 connection establishment towards the incoming protocol entity instance. The nodal function shall pass the following parameters to the incoming protocol entity instance only if they were conveyed by the incoming protocol entity instance: + +- the Transfer Capability Support; +- the Modify Support for Link Characteristics; and +- the Modify Support for SSCS Information. + +An ESTABLISH.indication primitive is sent to the AAL type 2 served user to inform it of the successfully established new connection. The nodal function shall pass the following parameters to the destination AAL type 2 served user only if they were conveyed by the incoming protocol entity instance: + +- the Origination AAL type 2 Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; +- the Modify Support for Link Characteristics; +- the SSCS Information; +- the Preferred SSCS Information; +- the Modify Support for SSCS Information; +- the Path Type; +- the Connection Priority; and +- the Test Connection Indicator. + +NOTE 2 – Through-connection at AAL type 2 service endpoints is not specified by this Recommendation. It may be controlled by the AAL type 2 served user. + +##### **8.2.1.1.2 Unsuccessful/abnormal connection setup** + +###### **8.2.1.1.2.1 Actions at the originating AAL type 2 service endpoint** + +If the AAL type 2 path selection or the allocation of a CID and other resources for the outgoing AAL type 2 link described in 8.2.1.1.1.1 fails, a RELEASE.confirm primitive is returned to the AAL type 2 served user with one of the following causes: + +- "Unallocated (unassigned) number"; +- "No route to destination"; +- "No circuit/channel available"; +- "Resource unavailable, unspecified"; +- "Network out of order"; or +- "Temporary failure". + +NOTE – Path selection failure may be due to the unavailability of an AAL type 2 path with the requested path type. + +If AAL type 2 service endpoint internal resources are not available for the new connection, a RELEASE.confirm primitive is sent to the AAL type 2 served user with the cause "Switching equipment congestion". + +If the AAL Type 2 service endpoint cannot complete a high priority connection establishment request even after application of the preferential treatment, a RELEASE.confirm primitive is sent to the AAL type 2 served user with the cause "Resource unavailable, unspecified". + +Upon receiving a negative acknowledgement for the connection setup request from the outgoing protocol entity instance, all the resources associated with this AAL type 2 link are released and made available for new traffic. The association to the outgoing protocol entity instance is released. + +Features that enable a further connection attempt, involving the selection of a different AAL type 2 path within the same route or of an alternative route, may be implemented. Such reattempts may use the CEID parameter returned in the Release Confirm (RLC) message and may select a different AAL type 2 path within the same route only. If the CEID parameter specifies an AAL Type 2 path with insufficient resources available for the connection attempt, no connection attempt is made on that path. + +If no further connection attempt is made, the AAL type 2 service endpoint internal resources are released and a RELEASE.confirm primitive is sent to the AAL type 2 served user with the cause received from the outgoing protocol entity instance. + +When an indication is received from the outgoing protocol entity that the establishment request has been rejected, and there has been a change in the level of congestion of the adjacent node, the routing tables in the nodal function shall be updated accordingly. The absence of an Automatic Congestion Control parameter indicates that there is no reported congestion in the adjacent node, whilst if the Automatic Congestion Control parameter is present it indicates whether congestion level 1 or 2 has been exceeded. After the routing tables have been updated, the Automatic Congestion Control parameter is discarded. + +Upon receiving an indication from the outgoing protocol entity instance that a timer has expired, the association to the outgoing protocol entity instance is released and a reset procedure is started (see 8.2.1.2.1.1 case 3 a). The AAL type 2 service endpoint internal resources are released. A RELEASE.confirm primitive is sent to the AAL type 2 served user with the cause received from the outgoing protocol entity instance, i.e., "Recovery on timer expiry". + +###### **8.2.1.1.2.2 Actions at the destination AAL type 2 service endpoint** + +If resources on the incoming AAL type 2 path are not available, the nodal function requests the incoming protocol entity instance to reject the AAL type 2 connection with one of the following causes as applicable: + +- "Resource unavailable, unspecified"; or +- "Requested circuit/channel not available". + +If the nodal function detects that the destination is not reachable it may issue a redirection request by rejecting the AAL type 2 connection with the cause "No route to destination" and include an alternative AAL type 2 path identifier in a Connection Element Identifier parameter. + +If the nodal function is aware that the SSCS parameters are not supported, it requests the incoming protocol entity instance to reject the AAL type 2 connection with the cause "AAL parameters cannot be supported". + +The association between the nodal function entity and its incoming protocol entity instance is released. + +If an AAL type 2 path is "locally blocked" and an indication from an incoming protocol entity instance of the request for a new connection other than a test connection is received, the following actions are taken: + +- 1) The indication of the request for a new connection establishment is ignored and the incoming protocol entity instance is instructed to terminate and enter state "Idle"; the association with the incoming protocol entity instance is released and an ERROR.indication primitive with the CEID and the cause "Temporary failure" is sent to layer management. +- 2) The blocking procedure specified in 8.2.1.2.2.1 case b) is initiated for the AAL type 2 path on which the new connection was requested to be established. + +If an AAL type 2 path is "remotely blocked" and an indication from an incoming protocol entity instance of the request for a new connection other than a test connection is received, the following actions are taken: + +- 1) The AAL type 2 path is set to "remotely unblocked". + +NOTE – This procedure shall not be considered as the normal way to remove the "remotely blocked" condition. + +- 2) The incoming connection establishment request is processed normally, i.e., as if the AAL type 2 path was not "remotely blocked" to begin with. + +If AAL type 2 service endpoint internal resources are not available for the new connection, a negative acknowledgement for the connection setup request shall be returned to the incoming protocol entity instance with the cause "Switching equipment congestion". The resources allocated to the incoming AAL type 2 path are released and the association between the incoming protocol entity instance and the nodal function is released. + +If the AAL Type 2 service endpoint cannot complete a high priority connection establishment request even after application of the preferential treatment, a negative acknowledgement for the connection setup request shall be returned to the incoming protocol entity instance with the cause "Resource unavailable, unspecified". The resources allocated to the incoming AAL type 2 path are released and the association between the incoming protocol entity instance and the nodal function is released. + +Upon receiving an indication from an incoming protocol entity instance requesting a new connection and the connection request is to be rejected, the nodal function checks the level of congestion of the node. If either of the two congestion thresholds is exceeded, an Automatic Congestion Control parameter is passed to the protocol entity with the rejection indication. This parameter indicates the level of congestion (congestion level 1 or 2) to the adjacent AAL Type 2 node. + +##### **8.2.1.1.3 Normal connection release** + +###### **8.2.1.1.3.1 Actions at the AAL type 2 service endpoint that originates the release** + +When the nodal function at an AAL type 2 service endpoint receives a RELEASE.request primitive from the AAL type 2 served user, it requests the protocol entity instance to release the connection. The request carries the cause of the release which shall be "Normal, unspecified" in case of normal connection release or "AAL parameters cannot be supported" if the AAL type 2 served user determines that it cannot support the SSCS parameters. + +The Cause parameters shall not be modified by the nodal function. + +When a release is to be initiated, the nodal function checks the level of congestion of the node. If either of the two congestion thresholds is exceeded, an Automatic Congestion Control parameter is passed to the protocol entity with the release indication. This parameter indicates the level of congestion (congestion level 1 or 2) to the adjacent AAL Type 2 node. + +Upon acknowledgement of the successful connection release from the protocol entity instance, all the resources associated with this AAL type 2 link are released and made available for new traffic, and the AAL type 2 service endpoint internal resources are released. The association to the protocol entity instance is released. + +###### **8.2.1.1.3.2 Actions at the AAL type 2 service endpoint that receives the release** + +When the nodal function at an AAL type 2 service endpoint receives a request from a protocol entity instance to clear the connection, all the resources associated with this AAL type 2 link are released and made available for new traffic, and the AAL type 2 service endpoint internal resources are released. The release is confirmed to the protocol entity instance and a RELEASE.indication primitive with the cause received from the protocol entity instance is sent to the AAL type 2 served user. The Cause parameters shall not be modified by the nodal function. The association between the nodal function and the protocol entity instance is released. + +When a Release indication containing an Automatic Congestion Control parameter is received from the incoming or outgoing protocol entity, and there has been a change in the level of congestion of the adjacent node, the routing tables in the nodal function shall be updated according to the indicated congestion level. The absence of an Automatic Congestion Control parameter indicates that there is no reported congestion in the adjacent node, whilst if the Automatic Congestion Control parameter is present it indicates whether congestion level 1 or 2 has been exceeded. After the routing tables have been updated, the Automatic Congestion Control parameter is discarded. + +##### **8.2.1.1.4 Abnormal connection release procedures** + +When the nodal function at an AAL type 2 service endpoint receives an indication from the protocol entity instance that a timer has expired, the association to the protocol entity instance is released and a maintenance protocol entity instance is ordered to start a reset procedure. + +##### **8.2.1.1.5 Successful modification** + +NOTE 1 – Modification of connection resources and SSCS layer resources are mandatory capabilities in this Recommendation (as in ITU-T Rec. Q.2630.2 [16]). Modify Support parameters and the Transfer Capability Support parameter are only required for interworking with CS-1 and CS-2 nodes (see Annex C). + +NOTE 2 – The effect of SSCS information in AAL type 2 CS-3 nodes is restricted to the allocation, configuration and management of the respective SSCS layer resources in AAL type 2 CS-3 service endpoints. + +###### **8.2.1.1.5.1 Actions at the AAL type 2 service endpoint originating the modification request** + +When the nodal function receives a MODIFY.request primitive from the AAL type 2 served user, the following restrictions on the optionality of the parameters of the primitive apply: + +- A Transfer Capability parameter or an SSCS Information parameter must be present. +- If a Transfer Capability parameter is present, this parameter has to refer to the same AAL type 2 transfer capability as the AAL type 2 Transfer Capability parameter in the ESTABLISH.request primitive. + +NOTE 1 – For example, if the AAL type 2 Transfer Capability parameter in the ESTABLISH.request primitive indicated a Variable Bandwidth Stringent Transfer Capability, the AAL type 2 Transfer Capability parameter in the MODIFY.request primitive, if present, may only indicate a Variable Bandwidth Stringent Transfer Capability. + +- If an SSCS Information parameter is present, this parameter has to refer to the same SSCS Information as the SSCS Information parameter in the ESTABLISH.request primitive. + +NOTE 2 – For example, if the SSCS Information parameter in the ESTABLISH.request primitive indicated an audio service specific information, the SSCS Information parameter in the MODIFY.request primitive, if present, may only indicate an audio service specific information. + +- If an SSCS Information parameter is present, it must be either an "SSCS Information (Audio Extended)" parameter or an "SSCS Information (Multirate Extended)" parameter. + +When the nodal function receives a MODIFY.request primitive from the AAL type 2 served user, the restrictions on the optionality of the Link Characteristics parameter that is used only for interworking with CS-1 or CS-2 nodes are described in Annex C. + +When the nodal function receives a MODIFY.request primitive from the AAL type 2 served user that conveys a Transfer Capability parameter, it checks the availability of resources indicated by the AAL type 2 connection resource in the AAL type 2 path. If the resources are available for the connection, they are reserved for the connection. + +The protocol entity instance is informed of the modification request. The nodal function shall pass the following parameters to the protocol entity instance only if they were conveyed by the AAL type 2 served user: + +- the Served User Correlation ID; +- the Transfer Capability; +- the Link Characteristics; and +- the SSCS Information. + +The following parameters – if they were conveyed by the originating AAL type 2 served user – shall not be modified by the nodal function: + +- the Served User Correlation ID; +- the Transfer Capability; +- the Link Characteristics; and +- the SSCS Information. + +The following parameters – if they were conveyed by the originating AAL type 2 served user – have significance to the served user only; therefore, they shall not be examined by the nodal function: + +- the Served User Correlation ID; and +- the SSCS Information. + +After receiving an indication of the successful modification from the protocol entity instance and AAL type 2 connection resources were requested to be modified, the reserved additional resources are allocated to the connection or resources no longer required for this AAL type 2 connection are freed. + +A MODIFY.confirm primitive is then sent to the AAL type 2 served user. If a Served User Correlation ID parameter was received from the protocol entity instance, it shall be included in the MODIFY.confirm primitive. The Served User Correlation ID parameter has significance to the served user only; therefore, it shall not be examined by the nodal function. + +###### **8.2.1.1.5.2 Actions at the AAL type 2 service endpoint receiving the modification request** + +Upon receiving an indication from a protocol entity instance requesting modification of the AAL type 2 connection resource, i.e., a Transfer Capability parameter is conveyed, the nodal function checks the availability of resources indicated by the AAL type 2 connection resource information in the incoming AAL type 2 path. If the resources are available for the connection, they are reserved for the connection. + +NOTE – In case of interworking, the Transfer Capability may be generated by the AAL type 2 service endpoint (see Annex C). + +A MODIFY.indication primitive is sent to the AAL type 2 served user to inform it of the modification of AAL type 2 connection resource. The nodal function shall pass the following + +parameters to the AAL type 2 served user only if they were conveyed by the protocol entity instance: + +- the Served User Correlation ID; +- the Transfer Capability; +- the Link Characteristics; and +- the SSCS Information. + +The following parameters – if they were conveyed by the originating AAL type 2 served user – have significance to the served user only; therefore, they shall not be examined by the nodal function: + +- the Served User Correlation ID; and +- the SSCS Information. + +Upon receiving a MODIFY.response from the served user and AAL type 2 connection resources were requested to be modified, the reserved additional resources are allocated to the connection or resources no longer required for this AAL type 2 connection are freed. The nodal function acknowledges the successful AAL type 2 connection resource modification towards the protocol entity instance. If a Served User Correlation ID parameter was contained in the MODIFY.response primitive, this parameter is passed to the protocol entity. The Served User Correlation ID parameter has significance to the served user only; therefore, it shall not be examined by the nodal function. + +##### **8.2.1.1.6 Unsuccessful/abnormal modification** + +###### **8.2.1.1.6.1 Actions at the AAL type 2 service endpoint originating the modification request** + +If resources on the AAL type 2 path are not available, a MODIFY-REJECT.confirm primitive is returned to the AAL type 2 served user with the cause "Resource unavailable, unspecified". + +Upon receiving a negative acknowledgement for the modification request from the protocol entity instance, all additional resources reserved for the modification request are freed. A MODIFY-REJECT.confirm primitive is sent to the AAL type 2 served user with the cause received from the protocol entity instance. The Cause parameters shall not be modified by the nodal function. + +Upon receiving an indication from the outgoing protocol entity instance that a timer has expired, the association to the outgoing protocol entity instance is released and a reset procedure is started (see 8.2.1.2.1.1 case 3 a). The AAL type 2 service endpoint internal resources are released. A RELEASE.indication primitive is sent to the AAL type 2 served user with the cause received from the outgoing protocol entity instance, i.e., "Recovery on timer expiry". + +###### **8.2.1.1.6.2 Actions at the AAL type 2 service endpoint receiving the modification request** + +If the resources on the AAL type 2 path are not available, the nodal function requests the protocol entity instance to reject the AAL type 2 modification request with the cause "Resource unavailable, unspecified". + +##### **8.2.1.1.7 Connection release during modification** + +The release procedures take precedence over the modification procedures. + +###### **8.2.1.1.7.1 Actions at the AAL type 2 service endpoint** + +When the nodal function receives a RELEASE.request primitive from the AAL type 2 served user or an indication of connection release from the protocol entity instance during the modification procedures, the nodal function will continue with normal connection release procedures. + +#### 8.2.1.2 Maintenance control + +##### 8.2.1.2.1 Reset + +The reset procedure is invoked under abnormal conditions such as when the current status of the channels is unknown or ambiguous, for example, an AAL type 2 switching system that has suffered memory mutilation will not know the status of channels in one or several AAL type 2 paths. All the affected channels and any associated resources (e.g., bandwidth, etc.) between the two adjacent AAL type 2 nodes shall be released. The resources are made available for new traffic. + +The reset procedure covers the following three cases: + +- 1) Case 1: Reset all channels used for user plane traffic (see Note) in all AAL type 2 paths associated with a signalling transport association between two adjacent AAL type 2 nodes. +- 2) Case 2: Reset all channels used for user plane traffic (see Note) in a single AAL type 2 path between two adjacent AAL type 2 nodes represented by an AAL type 2 Path Identifier. +- 3) Case 3: Reset a single channel between two adjacent AAL type 2 nodes. + +NOTE – Channels used for user plane traffic refers to channels that are under the control of the AAL type 2 signalling entity. They are identified by CID values "8" ... "255". Other channels are unaffected by the reset procedure. + +The reset procedure should be initiated when: + +- a) Signalling anomalies are detected by the AAL type 2 signalling entity. The following anomalies are detected by the protocol procedures and are indicated to the nodal function: + - Timer "Timer\_ERQ" expiry – Action: Reset the single AAL type 2 channel associated with the outgoing protocol entity instance. + - Timer "Timer\_REL" expiry – Action: Reset the single AAL type 2 channel associated with the incoming or outgoing protocol entity instance. + - Timer "Timer\_MOD" expiry – Action: Reset the single AAL type 2 channel associated with the incoming or outgoing protocol entity instance. +- b) Maintenance action is required to recover from abnormal conditions such as loss or ambiguity of association information (e.g., caused by memory mutilation) between SAID(s) and the channel status of either a specific channel in a specific AAL type 2 path, all channels in a specific AAL type 2 path, or all AAL type 2 paths associated with a signalling transport association between two AAL type 2 signalling nodes. Action: Reset a single AAL type 2 channel in a specific AAL type 2 path, all AAL type 2 channels in a single AAL type 2 path or all AAL type 2 channels in all AAL type 2 paths associated with a signalling transport association between two adjacent AAL type 2 nodes respectively. + +The reset procedures take precedence over the modification procedures. + +###### 8.2.1.2.1.1 Actions at reset initiating AAL type 2 node + +Reset procedures can be initiated to reset: + +- 1) all AAL type 2 paths associated with a signalling transport association between two adjacent AAL type 2 nodes, +- 2) a specific AAL type 2 path; +- 3) a single AAL type 2 channel. + +For case 1), layer management passes a RESET.request together with the indication "All AAL type 2 paths associated with a signalling transport association" to the nodal function which in turn invokes a maintenance protocol entity and passes a request for reset to that entity together with an indication that all AAL type 2 paths associated with a signalling transport association must be reset. + +For case 2), layer management passes a RESET.request together with the AAL type 2 path identifier to the nodal function which in turn invokes a maintenance protocol entity and passes a request for reset together with the AAL type 2 path identity. + +For case 3) there are two possible subcases, one due to timer expiry and the other due to layer management action: + +- a) After the expiry of Timer\_ERQ, Timer\_REL, or Timer\_MOD, the nodal function invokes a maintenance protocol entity by passing a request for a reset together with the identity of the AAL type 2 path and the channel. +- b) Layer management invokes the nodal function which in turn invokes a maintenance protocol entity by passing a request for a reset together with the identity of the AAL type 2 path and the channel. + +In cases 1), 2), and 3 b), the nodal function requests any affected incoming or outgoing protocol entity instances to terminate and enter state "Idle". The associations to the incoming or outgoing protocol entity instances are released. The affected AAL type 2 served users are informed with a RELEASE.indication primitive with the cause "Temporary failure". + +For cases 1) and 2), the remote blocking state for the affected path(s) is set to "remotely unblocked". + +Upon receiving a reset confirmation from the maintenance protocol entity instance, the nodal function will make the affected resources available for new connections, and the AAL type 2 node internal resources are released. The association to the maintenance protocol entity instance is released. In case 3 a), a RESET.indication primitive with a CEID parameter is sent to layer management; in all other cases, a RESET.confirm primitive is sent to the layer management. + +NOTE – The local blocking states are not affected. + +###### **8.2.1.2.1.2 Actions at reset responding node** + +Upon receiving a reset indication from the maintenance protocol entity, the nodal function analyses the received information to determine which AAL type 2 channels are to be reset. + +- 1) If an indication that all AAL type 2 paths associated with a signalling transport association must be reset is received, then all AAL type 2 channels associated with a signalling transport association between the two adjacent AAL type 2 nodes are reset. +- 2) If an indication that all the channels within the identified AAL type 2 path must be reset is received, all AAL type 2 channels within that path are reset. +- 3) If an indication that a specific channel within an AAL type 2 path must be reset is received, only that channel is reset. + +In cases 1) and 2), for "locally blocked" AAL type 2 paths, blocking procedures (refer to 8.2.1.2.2.1 case b)) are initiated prior to the sending of the reset confirmation. + +If resources have been assigned to any of the channels that are reset, the nodal functions make the affected resources available for new connections, and the AAL type 2 node internal resources are released. It also returns a reset confirmation to the maintenance protocol entity. The association between the nodal function and the maintenance protocol entity instance is released. The nodal function informs layer management about the receipt of the reset request by sending a RESET.indication primitive with the same CEID parameter as has been received in the RES message (reset request). + +The nodal function also requests the affected incoming or outgoing protocol entity instances (if any) to terminate and enter state "Idle". The associations to the incoming or outgoing protocol entity instances are released. The affected AAL type 2 served user is informed with a RELEASE.indication primitive with the cause "Temporary failure". + +###### **8.2.1.2.1.3 Abnormal reset procedures** + +Upon receiving a negative acknowledgement with a cause "Switching equipment congestion" from the maintenance protocol entity instance, the nodal function repeats the request for the reset. + +Upon receiving a negative acknowledgement with another cause from the maintenance protocol entity instance, an ERROR.indication primitive including the cause received from the maintenance protocol entity instance and the CEID parameter is sent to layer management. + +Upon receiving a STOP-RESET.request primitive with adjacent AAL type 2 node identifier and connection element identifier parameters from layer management, the nodal function will make the affected resources available for new connections. The nodal function requests the maintenance protocol entity instance to terminate and enter state "Idle". The association between the nodal function and the maintenance protocol entity instance is released. + +##### **8.2.1.2.2 Blocking and unblocking of AAL type 2 paths** + +The AAL type 2 path blocking procedure is provided to prevent an AAL type 2 path from being selected for carrying new connections other than test connections. Existing connections on the AAL type 2 path are not affected. + +Blocking can be initiated by either signalling endpoint that controls an AAL type 2 path. When blocking is invoked, both ends of the AAL type 2 path are put into a blocked state. A blocked AAL type 2 path cannot be selected for new, non-test traffic by either AAL type 2 node. + +An acknowledgment is required for each blocking and unblocking request. The acknowledgment is not sent until the appropriate action – blocking or unblocking – has been taken. + +Unblocking can only be initiated by the same AAL type 2 node which initiated the blocking procedures. It is performed by sending an unblocking request. At either end, the blocked state is removed and the AAL type 2 path is made available again for all new connections. + +An AAL type 2 path is considered "unblocked" if it is both "locally unblocked" and "remotely unblocked". + +The blocking and unblocking procedures do not affect the modification procedures. + +###### **8.2.1.2.2.1 Initiating blocking** + +Blocking can be initiated either by layer management, by the reset procedure, or by the connection set up procedure. + +Case a): When a BLOCK.request primitive is received from layer management for an AAL type 2 path that is currently "locally unblocked", the AAL type 2 path becomes "locally blocked". The AAL type 2 path is made unavailable for the selection to accommodate new non-test connections. + +Case b): A request for blocking can also be received from the reset procedure (8.2.1.2.1.2) or from the connection set up procedure (8.2.1.1.2.2). + +In both cases, a maintenance protocol entity is then invoked and the AAL type 2 path identifier and a request for blocking is passed to it. + +When confirmation of the blocking is received from the maintenance protocol entity, a BLOCK.confirm primitive is sent to layer management and the association to the maintenance protocol entity instance is released. + +###### **8.2.1.2.2.2 Initiating unblocking** + +When an UNBLOCK.request is received from layer management for an AAL type 2 path that is currently "locally blocked", a maintenance protocol entity is invoked and the AAL type 2 path identifier and a request for unblocking is passed to it. + +When confirmation of the unblocking is received from the maintenance protocol entity, the AAL type 2 path becomes "locally unblocked" and the AAL type 2 path is made available again to accommodate new connections (if it is not "remotely blocked"). An UNBLOCK.confirm is sent to layer management and the association to the maintenance protocol entity instance is released. + +###### **8.2.1.2.2.3 Receiving blocking** + +When an indication of blocking is received from a maintenance protocol entity for an AAL type 2 path that is currently "remotely unblocked", the AAL type 2 path becomes "remotely blocked" and the AAL type 2 path is made unavailable to accommodate new non-test connections. A response is then sent to the maintenance protocol entity indicating the acceptance of the blocking and the association to the maintenance protocol entity instance is released. + +###### **8.2.1.2.2.4 Receiving unblocking** + +When an indication of unblocking is received from a maintenance protocol entity for an AAL type 2 path that is currently "remotely blocked", the AAL type 2 path becomes "remotely unblocked" and the AAL type 2 path is made available to accommodate new connections (if it is not "locally blocked"). A response is then issued to the maintenance protocol entity indicating the acceptance of the unblocking and the association to the maintenance protocol entity instance is released. + +###### **8.2.1.2.2.5 Abnormal blocking and unblocking procedures** + +- a) If an indication for blocking is received from a maintenance protocol entity for an AAL type 2 path which is already "remotely blocked", a blocking confirmation is sent to the maintenance protocol entity and the association to the maintenance protocol entity instance is released. No further actions are performed. +- b) If an indication for unblocking is received from a maintenance protocol entity for an AAL type 2 path which is "remotely unblocked", an unblocking confirmation is sent to the maintenance protocol entity and the association to the maintenance protocol entity instance is released. No further actions are performed. +- c) If a BLOCK.request primitive is received from layer management for an AAL type 2 path that is already "locally blocked", the procedure in 8.2.1.2.2.1 is performed. +- d) If an UNBLOCK.request primitive is received from layer management for an AAL type 2 path that is already "locally unblocked", the procedure in 8.2.1.2.2.2 is performed. +- e) If an indication of an error is received from the maintenance protocol entity, a BLOCK.confirm primitive or an UNBLOCK.confirm primitive with the cause received from the maintenance protocol entity instance is sent to layer management. The association to the maintenance protocol entity is released. + +##### **8.2.1.2.3 Transmission fault handling** + +Fully digital transmission systems are provided between all AAL type 2 nodes. They have some inherent fault indication features that give an indication to the switching system when faults are detected on the transmission path level and/or on the virtual path level. On receipt of a fault indication from layer management, the routing function in the switching system inhibits selection of the AAL type 2 path (or paths) concerned for the period that the fault condition persists. No special action is required for active connections. + +##### **8.2.1.2.4 AAL type 2 signalling entity signalling congestion control** + +On receipt of a CONGESTION.indication primitive from the generic signalling transport service, the AAL type 2 signalling entity should alter traffic load (e.g., connection attempts) toward the affected AAL type 2 nodes to align with the congestion level indicated by the primitive. + +##### **8.2.1.2.5 Adjacent AAL type 2 node availability** + +On receipt of an OUT-OF-SERVICE.indication primitive from the generic signalling transport service, the following action is required: All AAL type 2 paths to the affected adjacent AAL type 2 node are marked as unavailable in the routing function prohibiting new (test or user) connection establishments to that AAL type 2 node. Already established connections need not be released even though signalling messages cannot be sent to the affected node. + +On receipt of an IN-SERVICE.indication primitive from the generic signalling transport service, the following action is required: All AAL type 2 paths to the affected adjacent AAL type 2 node, that are both "locally unblocked" and "remotely unblocked", are again marked available in the routing function and any of the unallocated channels can be used for connections immediately consistent with the congestion level in the primitive. Reset procedures that may have started during the period of signalling isolation continue and ensure that affected channels are returned to state "Idle". Connections that are in state "Established" are unaffected. + +#### **8.2.1.3 Error handling** + +A message received indicating an AAL type 2 path or CID value that is not controlled by the nodal function shall be discarded and layer management shall be informed with an ERROR.indication primitive with a cause "Invalid information element contents". + +If a parameter is present more than once in a message where this parameter is allowed only once, only the first parameter shall be processed; all subsequent instances of the parameter shall be ignored. + +When receiving a message which does not contain the minimum set of parameters required to continue processing, a protocol error is reported to layer management with an ERROR.indication primitive with a cause "Mandatory information element is missing" and the message is discarded. + +### **8.2.2 Nodal functions for AAL type 2 nodes without served user interaction** + +#### **8.2.2.1 Connection control** + +##### **8.2.2.1.1 Successful connection setup** + +Upon receiving notification from an incoming protocol entity instance requesting a new connection, the nodal function checks the availability of the CID value and other resources (e.g., indicated by Transfer Capability parameter), in the incoming AAL type 2 path. + +NOTE 1 – In case of interworking, the Transfer Capability and the Preferred Transfer Capability may be generated by the AAL type 2 switch (see Annex C). + +If the Test Connection Indicator parameter is present, "locally blocked" or "remotely blocked" AAL type 2 paths shall be acceptable for the incoming connection. + +If the CID and the other resources are available for the incoming AAL type 2 link, the resources are allocated to the new connection. + +If the Hop Counter is received, and the hop counter procedure is activated, the nodal functions shall decrement the Hop Counter value by 1. If the result is greater than 0, the nodal function shall pass the updated Hop Counter to the outgoing protocol entity instance when it is invoked. If the Hop Counter is received, and the hop counter procedure is not activated, the nodal functions shall pass the Hop Counter unmodified to the outgoing protocol entity instance when it is invoked. + +NOTE 2 – If the result is 0, see 8.2.2.1.2. + +The AAL type 2 service endpoint address is then examined. The nodal function determines that the AAL type 2 connection needs to be routed further to reach the destination AAL type 2 service endpoint and analyses the routing information. It selects a route with sufficient AAL type 2 path resources on a path with the requested path type (or network default if the path type is not specified) + +to the next AAL type 2 node. It then selects an AAL type 2 path from within the route which is able to accommodate the new connection. + +NOTE 3 – Routing typically is based on: + +- Addressing information; +- Transfer Capability; +- Test Connection Indicator; +- Requested Path Type; +- Automatic congestion control and the congestion level in the routing tables; and +- Temporary Alternative Routing (TAR) control (see ITU-T Rec. E.412 [17]). + +When the nodal function selects a route, the Connection Priority information, if received from the incoming protocol entity instance is used to select a route that has sufficient AAL type 2 path resources to the succeeding AAL type 2 node. + +If the "TAR controlled connection" indication is received, the nodal functions shall not apply network management Temporary Alternative Routing (TAR) to the same connection. + +If a Hop Counter is not received, and the hop counter procedure is activated, the nodal function shall pass the Hop Counter containing an initial count value to the outgoing protocol entity instance when it is invoked. The initial count value shall be provisioned by the network operator on a per AAL type 2 node basis (31 maximum). + +AAL type 2 node internal resources are allocated for the new connection from the incoming AAL type 2 path to the outgoing AAL type 2 path. The connection priority information, if received, is taken into consideration when allocating these resources. + +Under the normal condition, when the network is not congested and the AAL Type 2 node has the necessary resources to complete it, the connection establishment is processed without special treatments. + +NOTE 4 – In times of network congestion, when the AAL Type 2 node does not have sufficient resources to complete all of the incoming connection establishment requests, as one option, the AAL Type 2 node may give preferential treatments based on the priority level. + +NOTE 5 – The preferential treatment should include access to reserved network resources, e.g.: + +- the highest priority connections are given access to available network resources including the resources reserved for highest priority connections; +- the second highest priority connections are given access to available network resources including the resources reserved for the second highest priority connections, except for the resources reserved for the highest priority connections, and so on; + +NOTE 6 – Allocation of reserved network resources to specific priority levels is implementation specific, and is not a subject for standardization. + +On the selected outgoing AAL type 2 path, the CID and other resources (e.g., indicated by Transfer Capability, Link Characteristics, or SSCS information) are allocated for the outgoing AAL type 2 link. The handling of Transfer Capability, Link Characteristics, and SSCS information is specified in Annex C. + +The following parameters – if they were conveyed by the incoming protocol entity instance – shall not be modified by the nodal function: + +- the Destination Service Endpoint Address; +- the Origination Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the Transfer Capability; + +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; +- the Modify Support for Link Characteristics; +- the SSCS Information; +- the Preferred SSCS Information; +- the Modify Support for SSCS Information; +- the Path Type; +- the Connection Priority; and +- the Test Connection Indicator. + +The following parameters – if they were conveyed by the incoming protocol entity instance – have significance to the served user only; therefore, they shall not be examined by the nodal function: + +- the Origination Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the SSCS Information; +- the Preferred SSCS Information; and +- the Modify Support for SSCS Information. + +An outgoing protocol entity instance is invoked and the following parameters are passed to it: + +- the Destination AAL type 2 Service Endpoint Address; +- the AAL type 2 Path Identifier; +- a CID value; and +- the Transfer Capability. + +The nodal function shall pass the following parameters to the outgoing protocol entity instance only if they were conveyed by the incoming protocol entity instance: + +- the Origination AAL type 2 Service Endpoint Address; +- the Served User Generated Reference; +- the Served User Transport; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; +- the Modify Support for Link Characteristics; +- the SSCS Information; +- the Preferred SSCS Information; +- the Modify Support for SSCS Information; +- the Path Type; +- the Connection Priority; and +- the Test Connection Indicator. + +A received "TAR controlled connection" indication shall be passed to the invoked outgoing protocol entity instance unchanged; alternatively, if the "TAR controlled connection" indication is not received and the nodal function applies network management Temporary Alternative Routing to the connection, the nodal function shall pass a "TAR controlled connection" parameter to the invoked outgoing protocol entity instance. + +If the Hop Counter has been received or generated by the nodal function, it is passed to the invoked outgoing protocol entity instance. + +Through-connection in both directions will then be completed. + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, the incoming protocol entity instance is informed of the successful AAL type 2 connection setup. If one or more of the parameters Transfer Capability Support, Modify Support for Link Characteristics, or Modify Support for SSCS Information parameter, was received from the outgoing protocol instance they shall be conveyed to the incoming protocol entity instance. + +##### **8.2.2.1.2 Unsuccessful/abnormal connection setup** + +If resources on the incoming AAL type 2 path are not available, the nodal function requests the incoming protocol entity instance to reject the connection with one of the following causes as applicable: + +- "Resource unavailable, unspecified"; or +- "Requested circuit/channel not available". + +The association between the nodal function entity and its incoming protocol entity instance is released. + +If an AAL type 2 path is "locally blocked" and an indication from an incoming protocol entity instance of the request for a new connection other than a test connection is received, the following actions are taken: + +- 1) The indication of the request for a new connection establishment is ignored and the incoming protocol entity instance is instructed to terminate and enter state "Idle"; the association with the incoming protocol entity instance is released and an ERROR.indication primitive with the CEID and the cause "Temporary failure" is sent to layer management. +- 2) The blocking procedure specified in 8.2.1.2.2.1 case b) is initiated for the AAL type 2 path on which the new connection was requested to have been established. + +If an AAL type 2 path is "remotely blocked" and an indication from an incoming protocol entity instance of the request for a new connection other than a test connection is received, the following actions are taken: + +- 1) The AAL type 2 path is set to "remotely unblocked". + +NOTE 1 – This procedure shall not be considered as the normal way to remove the "remotely blocked" condition. + +- 2) The incoming connection establishment request is processed normally, i.e., as if the AAL type 2 path was not "remotely blocked" to begin with. + +If the Hop Counter is received, the nodal functions shall decrement the Hop Counter value by 1. If the result equals 0, the nodal function shall request the incoming protocol entity instance to reject the connection with cause value "exchange routing error". The association between the nodal function entity and its incoming protocol entity instance is released and all the resources associated with the incoming AAL type 2 link are released and made available for new traffic. + +In all cases where the request from an incoming protocol entity instance to establish a new connection has to be rejected, the nodal function checks the level of congestion of the node. If either of the two congestion thresholds is exceeded, an Automatic Congestion Control parameter is passed + +to the protocol entity with the rejection indication. This parameter indicates the level of congestion (congestion level 1 or 2) to the adjacent AAL Type 2 node. + +If AAL type 2 node internal resources are not available for the new connection, a negative acknowledgement for the connection setup request shall be returned to the incoming protocol entity instance with the cause "Switching equipment congestion". The resources allocated to the incoming AAL type 2 path are released and the association between the incoming protocol entity instance and the nodal function is released. + +If the AAL Type 2 node cannot complete a high priority connection establishment request even after application of the preferential treatment, a negative acknowledgement for the connection setup request shall be returned to the incoming protocol entity instance with the cause "Resource unavailable, unspecified". The resources allocated to the incoming AAL type 2 path are released and the association between the incoming protocol entity instance and the nodal function is released. + +If the AAL type 2 path selection or the allocation of a CID and other resources for the outgoing AAL type 2 link described in 8.2.2.1.1 fails, a negative acknowledgement for the connection setup request shall be returned to the incoming protocol entity instance with one of the following causes: + +- "Unallocated (unassigned) number"; +- "No route to destination"; +- "No circuit/channel available"; +- "Resource unavailable, unspecified"; +- "Network out of order"; or +- "Temporary failure". + +NOTE 2 – Path selection failure may be due to the unavailability of an AAL type 2 path with the requested path type. + +The resources allocated to the preceding AAL type 2 path are released and the association between the incoming protocol entity instance and the nodal function is released. + +Upon receiving a negative acknowledgement from the outgoing protocol entity instance, all resources associated with the outgoing AAL type 2 link are released and made available for new traffic. The association to the outgoing protocol entity instance is released. + +Features that enable a further connection attempt, involving the selection of a different AAL type 2 path within the same route or of an alternative route, may be implemented. Such reattempts may use the CEID parameter returned in the Release Confirm (RLC) message and may select a different AAL type 2 path within the same route only. If the CEID parameter specifies an AAL Type 2 path with insufficient resources available for the connection attempt, no connection attempt is made on that path. + +If no further connection attempt is made, the AAL type 2 node internal resources are released, the rejection of the connection establishment is forwarded to the incoming protocol entity instance with the cause received from the outgoing protocol entity instance; a Connection Element Identifier parameter possibly received in the Release Confirm (RLC) message is not forwarded to the incoming protocol entity instance. All the resources associated with the incoming AAL type 2 link are freed. The association to the incoming protocol entity instance is released. + +When an indication is received from the outgoing protocol entity that the establishment request has been rejected, and there has been a change in the level of congestion of the adjacent node, the routing tables in the nodal function shall be updated accordingly. The absence of an Automatic Congestion Control parameter indicates that there is no reported congestion in the adjacent node, whilst if the Automatic Congestion Control parameter is present it indicates whether congestion + +level 1 or 2 has been exceeded. After the routing tables have been updated, the Automatic Congestion Control parameter is discarded. + +Upon receiving an indication from the outgoing protocol entity instance that a timer has expired, the association to the outgoing protocol entity instance is released and a reset procedure is started (see 8.2.1.2.1.1 case 3 a)). The AAL type 2 node internal resources are released. The rejection of the connection establishment is forwarded to the incoming protocol entity instance with the cause received from the outgoing protocol entity instance (i.e., "Recovery on timer expiry") and all the resources associated with the incoming AAL type 2 link are released and made available for new traffic. The association to the incoming protocol entity instance is released. + +##### **8.2.2.1.3 Normal connection release** + +When the nodal function has received a request from a (first) protocol entity instance to release the connection, an acknowledgement is returned to that protocol entity instance and all the resources associated with the AAL type 2 link being governed by the protocol entity instance are released and made available for new traffic. The association to the protocol entity instance is released. + +When a Release indication containing an Automatic Congestion Control parameter is received from the incoming or outgoing protocol entity, and there has been a change in the level of congestion of the adjacent node, the routing tables in the nodal function shall be updated according to the indicated congestion level. The absence of an Automatic Congestion Control parameter indicates that there is no reported congestion in the adjacent node, whilst if the Automatic Congestion Control parameter is present it indicates whether congestion level 1 or 2 has been exceeded. After the routing tables have been updated, the Automatic Congestion Control parameter is discarded. + +The AAL type 2 node internal resources are released. + +When a release is to be forwarded, the nodal function checks the level of congestion of the node. If either of the two congestion thresholds is exceeded, an Automatic Congestion Control parameter is passed to the protocol entity with the release indication. This parameter indicates the level of congestion (congestion level 1 or 2) to the adjacent AAL Type 2 node. + +The request to release the connection is forwarded to the companion incoming or outgoing (second) protocol entity instance with the Cause parameter received from the first protocol entity instance. The Cause parameter shall not be modified by the nodal function. + +After receiving the acknowledgement of the successful connection release from the second protocol entity instance, all the resources associated with the AAL type 2 link being governed by the protocol entity instance are released and made available for new traffic. The association to the protocol entity instance is released. + +##### **8.2.2.1.4 Abnormal connection release procedures** + +###### **8.2.2.1.4.1 Actions at the AAL type 2 switch that initiates the release** + +When the nodal function receives an indication from the second protocol entity instance that a timer has expired, the association to that protocol entity instance is released and a reset procedure is started (see 8.2.2.2.1.1, case 3 a). + +##### **8.2.2.1.5 Successful modification** + +NOTE 1 – In this clause the following conventions apply: + +- The term "AAL type 2 connection resource information" refers to Transfer Capability. +- The term "modify receiving" refers to the AAL type 2 connection element identifier for which the Modify Request (MOD) message is received and the Modify Acknowledge (MOA) or Modify Reject (MOR) message is sent; conversely, the term "modify sending" refers to the AAL type 2 connection element identifier for which the Modify Request (MOD) message is sent and the Modify Acknowledge (MOA) or Modify Reject (MOR) message is received. + +NOTE 2 – The effect of SSCS information in AAL type 2 CS-3 nodes is restricted to the allocation, configuration and management of the respective SSCS layer resources in AAL type 2 CS-3 service endpoints. + +Upon receiving an indication from a protocol entity instance requesting modification of the AAL type 2 connection resource, i.e., a Transfer Capability parameter is conveyed, the nodal function checks the availability of the requested internal resources on the indicated AAL type 2 path. If the modification is requesting additional internal resources and they are available, they are reserved for the connection. + +NOTE 3 – In case of interworking, the Transfer Capability may be generated by the AAL type 2 switch (see Annex C). + +The nodal function checks the availability of the requested resources on the modify sending AAL type 2 path. If the modification is requesting additional resources and they are available, they are reserved for the connection. + +The companion (modify sending) protocol entity instance is informed of the modification. The nodal function shall pass the following parameters to the protocol entity instance only if they were conveyed by the AAL type 2 served user: + +- the Served User Correlation ID; +- the Transfer Capability; +- the Link Characteristics; and +- the SSCS Information. + +The following parameters – if they were received from the modify receiving protocol entity – shall not be modified by the nodal function: + +- the Served User Correlation ID; +- the Transfer Capability; +- the Link Characteristics; and +- the SSCS Information. + +The following parameters – if they were received from the modify receiving protocol entity– have significance to the served user only; therefore, they shall not be examined by the nodal function: + +- the Served User Correlation ID; and +- the SSCS Information. + +After receiving an indication of the successful AAL type 2 connection resource modification from the modify sending protocol entity instance and AAL type 2 connection resources were requested to be modified, the nodal function allocates the reserved additional resources to the modify receiving and modify sending connection or frees resources no longer required for this AAL type 2 connection. + +The modify receiving protocol entity instance is informed of the successful modification. The nodal function shall pass the Served User Correlation ID parameter to the modify receiving protocol entity instance only if it was conveyed by the modify sending protocol entity instance. The Served User Correlation ID parameter has significance to the served user only; therefore, it shall not be examined by the nodal function. + +##### **8.2.2.1.6 Unsuccessful/abnormal modification** + +If additional resources on the modify receiving AAL type 2 path are not available, the nodal function requests the modify receiving protocol entity instance to reject the AAL type 2 modification request with the cause "Resource unavailable, unspecified". + +If the resources on the modify sending AAL type 2 path are not available, the nodal function requests the modify receiving protocol entity instance to reject the AAL type 2 modification request with the cause "Resource unavailable, unspecified". The additional resources reserved for the modify receiving AAL type 2 path are freed. + +Upon receiving a negative acknowledgement for the modification request from the modify sending protocol entity instance, the nodal function frees all the additional resources reserved for the modification request. The rejection of the modification is forwarded to the modify receiving protocol entity instance with the cause received from the modify sending protocol entity instance. The Cause parameters shall not be modified by the nodal function. + +Upon receiving an indication from the modify sending protocol entity instance that a timer has expired (in this case Timer\_MOD), the association to the modify sending protocol entity instance is released and a reset procedure is started (see 8.2.2.2.1.1 case 3 a)). The AAL type 2 node internal resources for this AAL type 2 connection are released. The nodal function requests the modify receiving protocol entity instance to release the connection with the cause "Recovery on timer expiry". All resources associated with the modify receiving AAL type 2 link are freed. The association to the modify receiving protocol entity instance is released. + +##### **8.2.2.1.7 Connection release during modification** + +The release procedures take precedence over the modification procedures. + +When the nodal function receives an indication of connection release from the modify receiving or modify sending protocol entity instance during the modification procedures, the nodal function will continue with normal connection release procedures. + +#### **8.2.2.2 Maintenance control** + +##### **8.2.2.2.1 Reset** + +Refer to 8.2.1.2.1. + +###### **8.2.2.2.1.1 Actions at reset initiating node** + +Reset procedures can be initiated to reset: + +- 1) all AAL type 2 paths between two adjacent AAL type 2 nodes associated with a signalling transport association; +- 2) a specific AAL type 2 path; +- 3) a single AAL type 2 channel. + +For case 1), layer management passes a RESET.request together with the indication "All AAL type 2 paths associated with a signalling transport association" to the nodal function which in turn invokes a maintenance protocol entity and passes the request for reset to that entity together with an indication that all AAL type 2 paths associated with a signalling transport association must be reset. + +For case 2), layer management passes a RESET.request together with the AAL type 2 path identifier to the nodal function which in turn invokes a maintenance protocol entity and passes a request for reset to that entity together with the identity of the AAL type 2 path. + +For case 3) there are two possible subcases, one due to timer expiry and the other due to layer management action: + +- a) After the expiry of Timer\_ERQ, Timer\_REL, or Timer\_MOD, the nodal function invokes a maintenance protocol entity by passing a request for a reset together with the identity of the AAL type 2 path and the channel. +- b) Layer management invokes the nodal function which in turn invokes a maintenance protocol entity by passing a request for a reset together with the identity of the AAL type 2 path and the channel. + +In cases 1), 2), and 3 b), the nodal function requests any affected incoming or outgoing protocol entity instances to terminate and enter state "Idle". The associations to the incoming or outgoing protocol entity instances are released. + +For cases 1) and 2), the remote blocking state for the affected path(s) is set to "remotely unblocked". + +Upon receiving a reset confirmation from the maintenance protocol entity instance, the nodal function will make the affected resources available for new connections, and the AAL type 2 node internal resources are released. The association to the maintenance protocol entity instance is released. In case 3 a), a RESET.indication primitive with a CEID parameter is sent to layer management; in all other cases, a RESET.confirm primitive is sent to the layer management. + +NOTE – The local blocking states are not affected. + +###### **8.2.2.2.1.2 Actions at reset responding node** + +Upon receiving a reset indication from the maintenance protocol entity, the nodal functions analyses the received information to determine which AAL type 2 channels are to be reset. + +- 1) If an indication that all AAL type 2 paths associated with a signalling transport association must be reset is received, then all AAL type 2 channels associated with a signalling transport association between the two adjacent AAL type 2 nodes are reset. +- 2) If an indication that all the channels within the identified AAL type 2 path must be reset is received, all AAL type 2 channels within that path are reset. +- 3) If an indication that a specific channel within an AAL type 2 path must be reset is received, only that channel is reset. + +In cases 1) and 2), for "locally blocked" AAL type 2 paths, blocking procedures (refer to 8.2.1.2.2 case b)) are initiated prior to the sending of the reset confirmation. + +If resources have been assigned to one of the channels that are reset, the nodal functions make the affected resources available for new connections, and the AAL type 2 node internal resources are released. It also returns a reset confirmation to the maintenance protocol entity. The association between the nodal function and the maintenance protocol entity instance is released. The nodal function informs layer management about the receipt of the reset request by sending a RESET.indication primitive with the same CEID parameter as has been received in the RES message (Reset Request). + +The nodal function also requests the affected incoming or outgoing protocol entity instances (if any) to terminate and enter state "Idle". The associations to the incoming or outgoing protocol entity instances are released. + +###### **8.2.2.2.1.3 Abnormal reset procedures** + +Refer to 8.2.1.2.1.3. + +##### **8.2.2.2.2 Blocking and unblocking of AAL type 2 path** + +Refer to 8.2.1.2.2. + +##### **8.2.2.2.3 Transmission fault handling** + +Refer to 8.2.1.2.3. + +##### **8.2.2.2.4 AAL type 2 signalling entity signalling congestion control** + +Refer to 8.2.1.2.4. + +##### **8.2.2.2.5 Adjacent AAL type 2 node availability** + +Refer to 8.2.1.2.5. + +#### **8.2.2.3 Error handling** + +Refer to 8.2.1.3. + +## **8.3 Protocol entity** + +The following rules relating to Signalling Association Identifiers (SAID) apply: + +- The AAL type 2 signalling system that does not issue the value of such a field is not allowed to modify it, but shall use it in the destination signalling association identifier field in the header of a message directed towards the issuer. +- When a message is received at the generic signalling transport service access point (GST-SAP), the destination signalling association identifier field of the incoming message is used to distribute the messages to the appropriate protocol entity instance. +- If a received message contains a destination signalling association identifier set to the "unknown" value and an originating signalling association identifier, a new incoming protocol entity instance or a new maintenance protocol entity instance is created and marked with a newly allocated signalling association identifier. The originating signalling association identifier parameter in the first response message issued by the new protocol entity instance will inform the peer protocol entity instance of the newly allocated signalling association identifier. +- If a new protocol entity instance is created by the nodal function, a signalling association identifier is allocated for it and the signalling association identifier is conveyed to the peer AAL type 2 signalling entity as the originating signalling association identifier parameter in the first message issued by the new protocol entity instance. The DSAID field in the header in this message is set to "unknown". +- If a protocol entity instance sends a message to its peer, the message includes the signalling association identifier of the peer in the destination signalling association identifier field. +- If a new maintenance protocol entity instance is created as a result of an incoming maintenance message, no signalling association identifier is allocated for it and no originating signalling association identifier parameter is conveyed to the peer AAL type 2 signalling entity in the first (and only) message issued by the new maintenance protocol entity instance. + +The sequence control parameter of the TRANSFER.request primitive across the GST-SAP is allocated on a cyclic basis per protocol entity instance. + +Example message sequences are shown in Appendix I where usage of originating and destination signalling association identifiers is also described. + +All messages are sent in a TRANSFER.request primitive. All messages are received in a TRANSFER.indication primitive. + +Appendix I provides examples for modification. + +### **8.3.1 General protocol error handling** + +If a message is received that is too short to contain a complete message (i.e., less than 6 octets), it shall be ignored. + +The message is discarded and layer management informed with an ERROR.indication in the following cases: + +- If the parameter length points beyond the end of the message – cause "Message with unrecognized parameter discarded" is indicated. +- If the field length points beyond the end of the parameter – cause "Message with unrecognized parameter discarded" is indicated. +- If an unrecognized message containing a destination signalling association identifier set to the "unknown" value – cause "Message type non-existent or not implemented" is indicated. + +NOTE – If an unrecognized message containing a valid destination signalling association identifier is received, the message is conveyed to the addressed protocol entity instance as if it were a recognized message. + +- If the message contains a destination signalling association identifier with an illegal/invalid value – cause "Invalid information element contents" is indicated. +- If the message is considered unexpected by the signalling procedures – cause "Invalid message, unspecified" is indicated. +- If a mandatory originating signalling association identifier parameter is not present – cause "Mandatory information element is missing" is indicated. +- If the originating signalling association identifier field is set to "zero" – cause "Invalid information element contents" is indicated. + +### 8.3.2 Outgoing protocol procedures + +#### 8.3.2.1 Successful connection setup + +When an outgoing protocol entity instance in state "Idle" receives a request for a new connection from the nodal function, a free Signalling Association Identifier (SAID) is allocated for the outgoing protocol entity instance. + +Upon allocating an SAID, an ERQ message (establish request) is sent to the adjacent AAL type 2 node, entering state "Outgoing establishment pending" and starting Timer\_ERQ. The ERQ message contains a destination signalling association identifier field set to the "unknown" value and an originating signalling association identifier parameter in addition to those parameters given by the nodal function. + +If an ECF (establish confirm) message is received in state "Outgoing establishment pending", Timer\_ERQ is stopped, the nodal function is informed and state "Established" is entered. + +#### 8.3.2.2 Unsuccessful connection setup + +If the SAID allocation specified in section 8.3.2.1 fails, the nodal function is informed by passing the cause "Resource unavailable, unspecified". + +If the ERQ message (establish request) is longer than the signalling transport allows, the nodal function is informed by passing the cause ""Protocol error, unspecified". The SAID allocated to this particular outgoing protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +NOTE – If AAL type 2 signalling is used in an MTP3 signalling network (e.g., via the Signalling Transport Converter on MTP3 and MTP3b, see ITU-T Rec. Q.2150.1), it is possible that the ERQ message (establish request) may be longer than the minimum transport capability of 272 octets. This is due to the potential size of the Served User Transport (SUT) parameter. However, AAL type 2 signalling is specified to be deployed only in MTP3b networks. + +If Timer\_ERQ expires, the nodal function is informed by passing the cause "Recovery on timer expiry". The SAID allocated to this particular outgoing protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +If an RLC (release confirm) message is received in state "Outgoing establishment pending", the nodal function is informed about the rejection of the establishment request (including the cause and the Automatic Congestion Control parameter, if present, from the RLC message). + +Timer\_ERQ is stopped. The SAID allocated to this particular outgoing protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +#### **8.3.2.3 Normal connection release** + +In state "Established", an REL message (Release Request) containing a cause parameter can be received. The protocol entity instance informs the nodal function with the received cause and the Automatic Congestion Control parameter, if present. It then enters state "Incoming Release Pending". After the nodal function acknowledges the release, an RLC message (Release Confirm) is sent to the peer protocol entity instance (without a cause parameter). The SAID allocated to the protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +In state "Established", the nodal function can request the release of the connection. In this case an REL message is sent, Timer\_REL is started and state "Outgoing release pending" is entered. The REL message contains the cause received from the nodal function. + +If an RLC message is received, Timer\_REL is stopped and the nodal function is informed. The SAID allocated to the protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +#### **8.3.2.4 Release request collision** + +If an REL message (Release Request) is received in state "Outgoing Release Pending", an RLC message (Release Confirm) is immediately sent back to the peer protocol entity instance and state "Release Collision" is entered. + +When an RLC message is received in state "Release collision", Timer\_REL is stopped and the nodal function is informed. The SAID allocated to the protocol procedure entity instance is released and made available for new traffic and state "Idle" is entered. + +#### **8.3.2.5 Abnormal connection release procedures** + +If Timer\_REL expires in states "Outgoing release pending" or "Release collision", the nodal function is informed with a cause "Recovery on timer expiry". The SAID allocated to the protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +If in any state except state "Idle" a request to terminate an outgoing protocol procedure entity instance from the nodal function is received, all timers are stopped. The SAID allocated to the protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +#### **8.3.2.6 Successful modification** + +When an outgoing protocol entity instance in state "Established" receives a request for modification from the nodal function, an MOD message (Modify Request) is sent to the adjacent AAL type 2 node, entering state "Outgoing Modification Pending" and starting Timer\_MOD. The MOD message contains the DSAID which was received during the connection establishment phase and the parameter given by the nodal function, i.e., the Transfer Capability, Link Characteristics and/or SSCS information and the Served User Correlation ID if it was received from the nodal function. + +If an MOA (Modify Acknowledge) message is received in state "Outgoing Modification Pending", Timer\_MOD is stopped, the nodal function is informed of the successful modification, and the outgoing protocol entity instance returns to state "Established". + +Upon receiving an MOD message (Modify Request) in state "Established" with the DSAID which was received during the connection establishment phase, the outgoing protocol entity instance + +informs the nodal function of the request for the modification and state "Incoming Modification Pending" is entered. + +After receiving an acknowledgement from the nodal function that the connection modification is accepted, an MOA message (Modify Acknowledge) is sent to the preceding AAL type 2 node, and the outgoing protocol entity instance returns to state "Established". + +#### **8.3.2.7 Unsuccessful modification** + +If Timer\_MOD expires, the nodal function is informed by passing the cause "Recovery on timer expiry". The SAID allocated to this particular outgoing protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +If an MOR (Modify Reject) message is received in state "Outgoing Modification Pending", the nodal function is informed about the rejection of the modification request. Timer\_MOD is stopped and the outgoing protocol entity instance returns to state "Established". + +When an outgoing protocol entity instance in state "Incoming Modification Pending" receives a request to reject the requested modification from the nodal function, an MOR message is issued towards the adjacent AAL type 2 node with the cause provided by the nodal function. The MOD message contains the DSAID which was received during the connection establishment phase. The outgoing protocol entity instance returns to state "Established". + +#### **8.3.2.8 Connection release during modification** + +In state "Outgoing Modification Pending" or "Incoming Modification Pending", an REL message (Release Request) containing a cause parameter can be received. The normal connection release procedures specified in 8.3.2.3 shall apply. + +In state "Outgoing Modification Pending" or "Incoming Modification Pending", the nodal function can request the release of the connection. The normal connection release procedures specified in 8.3.2.3 shall apply. + +#### **8.3.2.9 Modification request collision** + +If an MOD message is received in state "Outgoing Modify Pending", an MOR message is immediately sent back to the peer protocol entity instance and "Modification Collision" state is entered. + +Clauses 8.3.2.7 and 8.3.2.8 shall apply with the replacement of "Modification Collision" with "Outgoing Modify Pending". + +#### **8.3.2.10 Unrecognized information procedures** + +When an unrecognized message, parameter, or subfield value is received, the message, the parameter, or the subfield value respectively is conveyed to the nodal function for appropriate action. + +When a request to pass on an unrecognized message, parameter, or subfield value is received from the nodal function, the unrecognized message is passed on and an unrecognized parameter or subfield value is sent in the recognized message being constructed respectively. + +When a request to send a CFN message (confusion) is received from the nodal function in any state except "Idle" and "Outgoing establishment pending", the message is sent. The CFN message (confusion) contains a cause parameter provided by the nodal function. + +When a request to send a cause parameter in an RLC message (release confirm) as a response to an unrecognized parameter or subfield value received in an REL message (release request) is received from the nodal function in any State except "Incoming release pending" and "Outgoing release pending", the cause parameter provided by the nodal function is sent in the RLC message (release confirm). + +When a CFN message (confusion) is received in any state except "Idle", the message is conveyed to the nodal function for appropriate action. + +When a cause parameter is received in an RLC message (release confirm) in state "Outgoing release pending", the cause parameter is conveyed to the nodal function for appropriate action. + +#### 8.3.2.11 State transition model + +##### 8.3.2.11.1 State transition + +The state transition diagram for the outgoing protocol procedure is shown in Figure 8-1. + +![Figure 8-1/Q.2630.3 – State transition diagram for the outgoing protocol procedure](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +``` + +stateDiagram-v2 + direction TB + + state "Idle" as Idle + state "Establishment" as Establishment { + state "Outgoing establishment pending" as OutgoingEstablishmentPending + } + state "Release" as Release { + state "Outgoing release pending" as OutgoingReleasePending + state "Release collision" as ReleaseCollision + state "Incoming release pending" as IncomingReleasePending + } + state "Modify" as Modify { + state "Outgoing modify pending" as OutgoingModifyPending + state "Modify collision" as ModifyCollision + state "Incoming modify pending" as IncomingModifyPending + } + state "Established" as Established + + Idle --> OutgoingEstablishmentPending: ESTABLISH.request / send ERQ message / start Timer_ERQ + OutgoingEstablishmentPending --> Idle: receive RLC message RELEASE.indication / stop Timer_ERQ + OutgoingEstablishmentPending --> Idle: Timer_ERQ ERROR.indication + OutgoingEstablishmentPending --> Established: receive ECF message ESTABLISH.confirm / stop Timer_ERQ + + Established --> OutgoingReleasePending: RELEASE.request / send REL message / start Timer_REL + OutgoingReleasePending --> Idle: receive RLC message RELEASE.confirm / stop Timer_REL + OutgoingReleasePending --> Idle: Timer_REL ERROR.indication + OutgoingReleasePending --> ReleaseCollision: receive REL message / send RLC message + + Established --> IncomingReleasePending: receive REL message / RELEASE.indication + IncomingReleasePending --> Idle: Release.response / send RLC message + + Established --> OutgoingModifyPending: MODIFY.request / send MOD message / start Timer_MOD + OutgoingModifyPending --> Established: receive MOA message MODIFY.confirm / stop Timer_MOD + OutgoingModifyPending --> Established: receive MOR message MODIFY-REJECT.confirm / stop Timer_MOD + OutgoingModifyPending --> Idle: Timer_MOD ERROR.indication + OutgoingModifyPending --> ModifyCollision: receive MOD message / send MOR message + + Established --> IncomingModifyPending: receive MOD message / MODIFY.indication + IncomingModifyPending --> Established: MODIFY.response / send MOA message + IncomingModifyPending --> Established: MODIFY-REJECT.request / send MOR message + + ReleaseCollision --> Idle: receive RLC message RELEASE.confirm / stop Timer_REL + ModifyCollision --> Established: receive MOR message MODIFY-REJECT.confirm / stop Timer_MOD + + Established --> Idle: TERMINATE.request + +``` + +Figure 8-1/Q.2630.3 – State transition diagram for the outgoing protocol procedure + +Figure 8-1/Q.2630.3 – State transition diagram for the outgoing protocol procedure + +##### 8.3.2.11.2 SDL diagrams for the outgoing protocol procedures + +The SDL diagram for the outgoing protocol procedure is shown in Figure 8-2 (parts 1 to 6). + +The SDL diagrams contained in Figure 8-2 (parts 1 to 6) are an introduction to the procedures described in detail in 8.3.2. + +![SDL diagram for the outgoing protocol procedure (Process OPP2b). The diagram shows two main state machines. The left one starts at 'Idle', receives an 'ESTABLISH. request' from a nodal function, allocates a SAID, and checks if the allocation was successful. If successful, it sets a timer and constructs an ERQ message to be transferred to Generic Signalling Transport, ending in 'Outgoing Establishment Pending'. If not successful, it sends an error indication and returns to 'Idle'. The right state machine starts at 'Outgoing Establishment Pending', receives a 'TRANSFER. indication (message)', and checks its type. If it's an 'ECF', it resets the timer and sends an 'ESTABLISH. confirm' to the nodal function, ending in 'Established'. If it's an 'RLC', it resets the timer and sends a 'RELEASE. confirm' to the nodal function, then releases the SAID and returns to 'Idle'. Other transitions include 'Timer_ERQ' and 'ERROR. indication (Cause)' leading to 'reset (Timer_ERQ)', and 'TERMINATE. request' leading to 'release SAID' and 'Idle'. A note at the bottom left states that signals to/from nodal functions are not defined and are for descriptive purposes only.](5cc4a2ef554f31ea0577731931007fff_img.jpg) + +Process OPP2b OPP21(6) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> ESTABLISH_request: ESTABLISH. request (from nodal function) + ESTABLISH_request --> allocate_SAID: allocate SAID + allocate_SAID --> allocation_successful{allocation successful} + allocation_successful -- TRUE --> set_timer: set (now + t1, Timer_ERQ) + allocation_successful -- FALSE --> ERROR_indication: ERROR. indication (Cause) + set_timer --> Construct_ERQ: Construct ERQ message + Construct_ERQ --> TRANSFER_request: TRANSFER. request (ERQ message) (to Generic Signalling Transport) + TRANSFER_request --> Outgoing_Establishment_Pending: Outgoing Establishment Pending + ERROR_indication --> Idle + Outgoing_Establishment_Pending --> TRANSFER_indication: TRANSFER. indication (message) (from Generic Signalling Transport) + TRANSFER_indication --> message_type{message.type} + message_type -- ECF --> reset_timer: reset (Timer_ERQ) + message_type -- RLC --> reset_timer + message_type -- else --> A1 + reset_timer --> ESTABLISH_confirm: ESTABLISH. confirm (to nodal function) + ESTABLISH_confirm --> Established: Established + reset_timer --> RELEASE_confirm: RELEASE. confirm (to nodal function) + RELEASE_confirm --> release_SAID: release SAID + release_SAID --> Idle + Timer_ERQ --> ERROR_indication: ERROR. indication (Cause) (to nodal function) + ERROR_indication --> reset_timer + TERMINATE_request --> reset_timer: TERMINATE. request (from nodal function) + reset_timer --> release_SAID + release_SAID --> Idle + +``` + +The signals to and from the nodal function are not defined and are for descriptive purposes only. + +SDL diagram for the outgoing protocol procedure (Process OPP2b). The diagram shows two main state machines. The left one starts at 'Idle', receives an 'ESTABLISH. request' from a nodal function, allocates a SAID, and checks if the allocation was successful. If successful, it sets a timer and constructs an ERQ message to be transferred to Generic Signalling Transport, ending in 'Outgoing Establishment Pending'. If not successful, it sends an error indication and returns to 'Idle'. The right state machine starts at 'Outgoing Establishment Pending', receives a 'TRANSFER. indication (message)', and checks its type. If it's an 'ECF', it resets the timer and sends an 'ESTABLISH. confirm' to the nodal function, ending in 'Established'. If it's an 'RLC', it resets the timer and sends a 'RELEASE. confirm' to the nodal function, then releases the SAID and returns to 'Idle'. Other transitions include 'Timer\_ERQ' and 'ERROR. indication (Cause)' leading to 'reset (Timer\_ERQ)', and 'TERMINATE. request' leading to 'release SAID' and 'Idle'. A note at the bottom left states that signals to/from nodal functions are not defined and are for descriptive purposes only. + +**Figure 8-2/Q.2630.3 (part 1 of 6) – SDL diagram for the outgoing protocol procedure** + +![SDL diagram for the outgoing protocol procedure (Process OPP2b).](4a2b39fa33747a6553031cfe1e0947fa_img.jpg) + +``` + +stateDiagram-v2 + state "Established" as Established + state "Outgoing Release Pending" as OutgoingReleasePending + state "Outgoing Modify Pending" as OutgoingModifyPending + state "Incoming Release Pending" as IncomingReleasePending + state "Incoming Modify Pending" as IncomingModifyPending + state "Release Collision" as ReleaseCollision + state "Idle" as Idle + + [*] --> Established + + %% Path 1: RELEASE. request + Established --> RELEASE_req : from nodal function + state "RELEASE. request" as RELEASE_req + RELEASE_req --> set_REL : set (now + t2, Timer_REL) + state "set (now + t2, Timer_REL)" as set_REL + set_REL --> Construct_REL : Construct REL message + Construct_REL --> TRANSFER_req_REL : TRANSFER. request (REL message) + TRANSFER_req_REL --> OutgoingReleasePending : to Generic Signalling Transport + + %% Path 2: MODIFY. request + Established --> MODIFY_req : from nodal function + state "MODIFY. request" as MODIFY_req + MODIFY_req --> set_MOD : set (now + t6, Timer_MOD) + state "set (now + t6, Timer_MOD)" as set_MOD + set_MOD --> Construct_MOD : Construct MOD message + Construct_MOD --> TRANSFER_req_MOD : TRANSFER. request (MOD message) + TRANSFER_req_MOD --> OutgoingModifyPending : to Generic Signalling Transport + + %% Path 3: TERMINATE. request + Established --> TERMINATE_req : from nodal function + state "TERMINATE. request" as TERMINATE_req + TERMINATE_req --> release_SAID_1 : release SAID + release_SAID_1 --> Idle + + %% Path 4: TRANSFER. indication + Established --> TRANSFER_ind : from Generic Signalling Transport + state "TRANSFER. indication (message)" as TRANSFER_ind + TRANSFER_ind --> message_type_1 : message.type + state message_type_1 <> + message_type_1 --> REL_ind : REL + message_type_1 --> MOD_ind : MOD + message_type_1 --> A1_1 : else + + state "RELEASE. indication" as REL_ind + REL_ind --> IncomingReleasePending + IncomingReleasePending --> to_nodal_1 : to nodal function + + state "MODIFY. indication" as MOD_ind + MOD_ind --> IncomingModifyPending + IncomingModifyPending --> to_nodal_2 : to nodal function + + %% Outgoing Release Pending transitions + OutgoingReleasePending --> Timer_REL_timeout : Timer_REL + state "Timer_REL" as Timer_REL_timeout + Timer_REL_timeout --> ERROR_ind : ERROR. indication (Cause) + ERROR_ind --> to_nodal_3 : to nodal function + + OutgoingReleasePending --> TERMINATE_req_2 : TERMINATE. request (from nodal function) + state "TERMINATE. request" as TERMINATE_req_2 + TERMINATE_req_2 --> reset_T_REL_1 : reset (Timer_REL) + reset_T_REL_1 --> release_SAID_2 : release SAID + release_SAID_2 --> Idle + + OutgoingReleasePending --> TRANSFER_ind_2 : TRANSFER. indication (message) (from Generic Signalling Transport) + state "TRANSFER. indication (message)" as TRANSFER_ind_2 + TRANSFER_ind_2 --> message_type_2 : message.type + state message_type_2 <> + message_type_2 --> REL_path : REL + message_type_2 --> RLC_path : RLC + message_type_2 --> A1_2 : else + + state "Construct RLC message" as REL_path + REL_path --> TRANSFER_req_RLC : TRANSFER. request (RLC message) + TRANSFER_req_RLC --> ReleaseCollision : to Generic Signalling Transport + + state "reset (Timer_REL)" as RLC_path + RLC_path --> RELEASE_conf : RELEASE. confirm + RELEASE_conf --> to_nodal_4 : to nodal function + RELEASE_conf --> release_SAID_3 : release SAID + release_SAID_3 --> Idle + +``` + +The diagram illustrates the outgoing protocol procedure (Process OPP2b) starting from an 'Established' state. It branches into four main paths based on input: 'RELEASE. request' (from nodal function), 'MODIFY. request' (from nodal function), 'TERMINATE. request' (from nodal function), and 'TRANSFER. indication (message)' (from Generic Signalling Transport). The 'RELEASE. request' path involves setting a timer (t2), constructing a REL message, and transitioning to 'Outgoing Release Pending'. The 'MODIFY. request' path involves setting a timer (t6), constructing a MOD message, and transitioning to 'Outgoing Modify Pending'. The 'TERMINATE. request' path releases the SAID and returns to an 'Idle' state. The 'TRANSFER. indication' path checks the message type; if 'REL', it sends a 'RELEASE. indication' to 'Incoming Release Pending'; if 'MOD', it sends a 'MODIFY. indication' to 'Incoming Modify Pending'; otherwise, it goes to state A1. From 'Outgoing Release Pending', the process can handle a 'Timer\_REL' (sending an 'ERROR. indication' to nodal function), a 'TERMINATE. request' (resetting the timer, releasing the SAID, and returning to 'Idle'), or a 'TRANSFER. indication (message)' from transport. This second 'TRANSFER. indication' leads to a 'message.type' decision; if 'REL', it constructs an RLC message and transitions to 'Release Collision'; if 'RLC', it resets the timer, sends a 'RELEASE. confirm' to nodal function, releases the SAID, and returns to 'Idle'; otherwise, it goes to state A1. + +SDL diagram for the outgoing protocol procedure (Process OPP2b). + +Figure 8-2/Q.2630.3 (part 2 of 6) – SDL diagram for the outgoing protocol procedure + +![SDL diagram for the outgoing protocol procedure (Process OPP2b).](3b11cc18f8ee769d0076c139dbf81ba3_img.jpg) + +``` + +stateDiagram-v2 + [*] --> IncomingReleasePending + IncomingReleasePending --> RELEASE_response + RELEASE_response --> Construct_RLC_message + Construct_RLC_message --> TRANSFER_request_RLC_message + TRANSFER_request_RLC_message --> release_SAID + release_SAID --> Idle + + RELEASE_response : from nodal function + TRANSFER_request_RLC_message : to Generic Signalling Transport + TRANSFER_indication_message : from Generic Signalling Transport + + [*] --> Release_Collision + Release_Collision --> Timer_REL + Release_Collision --> TERMINATE_request + Release_Collision --> TRANSFER_indication_message + TERMINATE_request : from nodal function + + Timer_REL --> ERROR_indication_Cause + ERROR_indication_Cause --> reset_Timer_REL + reset_Timer_REL --> release_SAID + release_SAID --> Idle + + ERROR_indication_Cause : to nodal function + + TRANSFER_indication_message --> RLC_message_type{RLC message.type} + RLC_message_type --> reset_Timer_REL + RLC_message_type --> RELEASE_confirm + RELEASE_confirm --> release_SAID + release_SAID --> Idle + + RELEASE_confirm : to nodal function + reset_Timer_REL : reset (Timer_REL) + +``` + +The diagram illustrates the outgoing protocol procedure for Process OPP2b. It begins with an initial state leading to 'Incoming Release Pending'. From here, three paths emerge: 'RELEASE. response' (from nodal function), 'TERMINATE. request', and 'TRANSFER. indication (message)' (from Generic Signalling Transport). The 'RELEASE. response' path leads to 'Construct RLC message', which then becomes 'TRANSFER. request (RLC message)' (to Generic Signalling Transport), followed by 'release SAID' and an 'Idle' state. The 'TERMINATE. request' path leads directly to 'release SAID' and 'Idle'. The 'TRANSFER. indication (message)' path leads to a junction point 'A1'. A second initial state, 'Release Collision', leads to 'Timer\_REL', 'TERMINATE. request' (from nodal function), and 'TRANSFER. indication (message)' (from Generic Signalling Transport). 'Timer\_REL' leads to 'ERROR. indication (Cause)' (to nodal function), which then leads to 'reset (Timer\_REL)', 'release SAID', and 'Idle'. 'TERMINATE. request' leads to 'reset (Timer\_REL)', 'release SAID', and 'Idle'. 'TRANSFER. indication (message)' leads to a decision 'RLC message.type'. If 'else', it leads to junction 'A1'. If 'RLC', it leads to 'reset (Timer\_REL)', 'RELEASE. confirm' (to nodal function), 'release SAID', and 'Idle'. + +SDL diagram for the outgoing protocol procedure (Process OPP2b). + +Figure 8-2/Q.2630.3 (part 3 of 6) – SDL diagram for the outgoing protocol procedure + +![SDL diagram for the outgoing protocol procedure. The diagram is divided into two main sections. The top section starts with 'Outgoing Modify Pending' and branches into 'RELEASE. request', 'Timer_MOD', and 'TERMINATE. request'. 'RELEASE. request' leads to 'reset (Timer_MOD)', 'set (now + t2, Timer_REL)', 'Construct REL message', 'TRANSFER. request (REL message)', and 'Outgoing Release Pending'. 'Timer_MOD' leads to 'ERROR. indication (Cause)'. 'TERMINATE. request' leads to 'reset (Timer_MOD)', 'release SAID', and 'Idle'. The bottom section starts with 'Outgoing Modify Pending', followed by 'TRANSFER. indication (message)', and a decision diamond 'message.type'. The 'message.type' decision branches into 'REL', 'MOA', 'MOR', 'MOD', and 'else'. 'REL' leads to 'reset (Timer_MOD)', 'RELEASE. indication', and 'Incoming Release Pending'. 'MOA' leads to 'reset (Timer_MOD)', 'MODIFY. confirm', and 'Established'. 'MOR' leads to 'reset (Timer_MOD)', 'MODIFY-REJECT. confirm', and 'Established'. 'MOD' leads to 'Construct MOR message', 'TRANSFER. request (MOR message)', and 'Modify Collision'. The 'else' branch leads to a circle labeled 'A1'. Various interfaces are indicated with dashed lines: 'from nodal function', 'to nodal function', and 'to Generic Signalling Transport'.](778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Outgoing_Modify_Pending_1 : Outgoing Modify Pending + Outgoing_Modify_Pending_1 --> RELEASE_request : RELEASE. request + Outgoing_Modify_Pending_1 --> Timer_MOD_1 : Timer_MOD + Outgoing_Modify_Pending_1 --> TERMINATE_request : TERMINATE. request + RELEASE_request --> reset_1 : reset (Timer_MOD) + reset_1 --> set_timer : set (now + t2, Timer_REL) + set_timer --> Construct_REL : Construct REL message + Construct_REL --> TRANSFER_REL : TRANSFER. request (REL message) + TRANSFER_REL --> Outgoing_Release_Pending : Outgoing Release Pending + Timer_MOD_1 --> ERROR_indication : ERROR. indication (Cause) + TERMINATE_request --> reset_2 : reset (Timer_MOD) + reset_2 --> release_SAID : release SAID + release_SAID --> Idle : Idle + + [*] --> Outgoing_Modify_Pending_2 : Outgoing Modify Pending + Outgoing_Modify_Pending_2 --> TRANSFER_indication : TRANSFER. indication (message) + TRANSFER_indication --> message_type : message.type + message_type --> REL : REL + message_type --> MOA : MOA + message_type --> MOR : MOR + message_type --> MOD : MOD + message_type --> else : else + REL --> reset_3 : reset (Timer_MOD) + reset_3 --> RELEASE_indication : RELEASE. indication + RELEASE_indication --> Incoming_Release_Pending : Incoming Release Pending + MOA --> reset_4 : reset (Timer_MOD) + reset_4 --> MODIFY_confirm_1 : MODIFY. confirm + MODIFY_confirm_1 --> Established_1 : Established + MOR --> reset_5 : reset (Timer_MOD) + reset_5 --> MODIFY_REJECT_confirm : MODIFY-REJECT. confirm + MODIFY_REJECT_confirm --> Established_2 : Established + MOD --> Construct_MOR : Construct MOR message + Construct_MOR --> TRANSFER_MOR : TRANSFER. request (MOR message) + TRANSFER_MOR --> Modify_Collision : Modify Collision + else --> A1 : A1 + +``` + +SDL diagram for the outgoing protocol procedure. The diagram is divided into two main sections. The top section starts with 'Outgoing Modify Pending' and branches into 'RELEASE. request', 'Timer\_MOD', and 'TERMINATE. request'. 'RELEASE. request' leads to 'reset (Timer\_MOD)', 'set (now + t2, Timer\_REL)', 'Construct REL message', 'TRANSFER. request (REL message)', and 'Outgoing Release Pending'. 'Timer\_MOD' leads to 'ERROR. indication (Cause)'. 'TERMINATE. request' leads to 'reset (Timer\_MOD)', 'release SAID', and 'Idle'. The bottom section starts with 'Outgoing Modify Pending', followed by 'TRANSFER. indication (message)', and a decision diamond 'message.type'. The 'message.type' decision branches into 'REL', 'MOA', 'MOR', 'MOD', and 'else'. 'REL' leads to 'reset (Timer\_MOD)', 'RELEASE. indication', and 'Incoming Release Pending'. 'MOA' leads to 'reset (Timer\_MOD)', 'MODIFY. confirm', and 'Established'. 'MOR' leads to 'reset (Timer\_MOD)', 'MODIFY-REJECT. confirm', and 'Established'. 'MOD' leads to 'Construct MOR message', 'TRANSFER. request (MOR message)', and 'Modify Collision'. The 'else' branch leads to a circle labeled 'A1'. Various interfaces are indicated with dashed lines: 'from nodal function', 'to nodal function', and 'to Generic Signalling Transport'. + +Figure 8-2/Q.2630.3 (part 4 of 6) – SDL diagram for the outgoing protocol procedure + +![SDL diagram for the outgoing protocol procedure, showing two state transition diagrams for Process OPP2c. The top diagram starts with 'Modify Collision' and handles outgoing requests. The bottom diagram starts with 'Incoming Modify Pending' and handles incoming requests. Both diagrams include states like 'Idle', 'Outgoing Release Pending', 'Incoming Release Pending', and 'Established', with transitions for messages like RELEASE, TERMINATE, TRANSFER, and TIMER_MOD.](bd0283b61b6a59829e9370b29076c79a_img.jpg) + +The diagram consists of two State Transition Diagrams (STDs) for Process OPP2c. + +**Top STD (Outgoing Procedure):** + +- Initial State:** Modify Collision (oval). +- Transitions from Modify Collision:** + - RELEASE. request** (input) → **reset (Timer\_MOD)** (action) → **set (now + t2, Timer\_REL)** (action) → **Construct REL message** (action) → **TRANSFER. request (REL message)** (output) → **Outgoing Release Pending** (state). + - TERMINATE. request** (input) → **reset (Timer\_MOD)** (action) → **release SAID** (action) → **Idle** (state). + - Timer\_MOD** (input) → **ERROR. indication (Cause)** (output). + - TRANSFER. indication (message)** (input) → **message.type** (decision). + - REL** path: **reset (Timer\_MOD)** (action) → **RELEASE. indication** (output) → **Incoming Release Pending** (state). + - MOR** path: **reset (Timer\_MOD)** (action) → **MODIFY-REJECT. confirm** (output) → **Established** (state). + - else** path: → **A1** (state). +- Internal Transitions:** + - RELEASE. request** and **TERMINATE. request** inputs have dashed arrows to a box labeled "from nodal function". + - A box labeled "to nodal function" has dashed arrows to **reset (Timer\_MOD)** actions and **ERROR. indication (Cause)** output. + - TRANSFER. request (REL message)** output has a dashed arrow to a box labeled "to Generic Signalling Transport". + - TRANSFER. indication (message)** input has a dashed arrow from a box labeled "from Generic Signalling Transport". + - MODIFY-REJECT. confirm** output has a dashed arrow to a box labeled "to nodal function". + +**Bottom STD (Incoming Procedure):** + +- Initial State:** Incoming Modify Pending (oval). +- Transitions from Incoming Modify Pending:** + - MODIFY. response** (input) → **Construct MOA message** (action) → **TRANSFER. request (MOA message)** (output) → **Established** (state). + - MODIFY-REJECT. request** (input) → **Construct MOR message** (action) → **TRANSFER. request (MOR message)** (output) → **Established** (state). + - RELEASE. request** (input) → **set (now + t2, Timer\_REL)** (action) → **Construct REL message** (action) → **TRANSFER. request (REL message)** (output) → **Outgoing Release Pending** (state). + - TERMINATE. request** (input) → **release SAID** (action) → **Idle** (state). + - TRANSFER. indication (message)** (input) → **message.type** (decision). + - REL** path: → **RELEASE. indication** (output) → **Incoming Release Pending** (state). + - else** path: → **A1** (state). +- Internal Transitions:** + - MODIFY. response** input has a dashed arrow from a box labeled "from nodal function". + - TRANSFER. request (MOA message)** and **TRANSFER. request (MOR message)** outputs have dashed arrows to a box labeled "to Generic Signalling Transport". + - TRANSFER. indication (message)** input has a dashed arrow from a box labeled "from Generic Signalling Transport". + - RELEASE. indication** output has a dashed arrow to a box labeled "to nodal function". + +SDL diagram for the outgoing protocol procedure, showing two state transition diagrams for Process OPP2c. The top diagram starts with 'Modify Collision' and handles outgoing requests. The bottom diagram starts with 'Incoming Modify Pending' and handles incoming requests. Both diagrams include states like 'Idle', 'Outgoing Release Pending', 'Incoming Release Pending', and 'Established', with transitions for messages like RELEASE, TERMINATE, TRANSFER, and TIMER\_MOD. + +Figure 8-2/Q.2630.3 (part 5 of 6) – SDL diagram for the outgoing protocol procedure + +![SDL diagram for the outgoing protocol procedure, Process OPP2b. The diagram shows two main parts. The top part is a state transition diagram starting from a state 'Any state except Idle and Outgoing Establishment Pending'. It has two transitions: 'UNRECOGNIZED request (message)' leading to 'Construct Unrecognized Message' then 'TRANSFER. request (Unrecognized message)' to an end state; and 'CONFUSION. request' leading to 'Construct CFN message' then 'TRANSFER. request (CFN message)' to an end state. The bottom part is a message processing diagram starting from connector 'A1'. A decision 'message.type' has three branches: 'unrecognized' leading to 'UNRECOGNIZED indication (message)' to an end state; 'CFN' leading to 'CONFUSION. indication (message)' to an end state; and 'else' leading to 'ERROR. indication (Cause)' to an end state. Various external functions are indicated with dashed boxes: 'from nodal function', 'to Generic Signalling Transport', 'to nodal function', and 'to layer management'.](90183a52275501da5a0fd5c63d837009_img.jpg) + +SDL diagram for the outgoing protocol procedure, Process OPP2b. The diagram shows two main parts. The top part is a state transition diagram starting from a state 'Any state except Idle and Outgoing Establishment Pending'. It has two transitions: 'UNRECOGNIZED request (message)' leading to 'Construct Unrecognized Message' then 'TRANSFER. request (Unrecognized message)' to an end state; and 'CONFUSION. request' leading to 'Construct CFN message' then 'TRANSFER. request (CFN message)' to an end state. The bottom part is a message processing diagram starting from connector 'A1'. A decision 'message.type' has three branches: 'unrecognized' leading to 'UNRECOGNIZED indication (message)' to an end state; 'CFN' leading to 'CONFUSION. indication (message)' to an end state; and 'else' leading to 'ERROR. indication (Cause)' to an end state. Various external functions are indicated with dashed boxes: 'from nodal function', 'to Generic Signalling Transport', 'to nodal function', and 'to layer management'. + +Figure 8-2/Q.2630.3 (part 6 of 6) – SDL diagram for the outgoing protocol procedure + +### **8.3.3 Incoming protocol procedures** + +#### **8.3.3.1 Successful connection setup** + +Upon receiving an ERQ message (establish request) in state "Idle" with the DSAID set to "unknown", a Signalling Association Identifier (SAID) is allocated for the new incoming protocol entity instance. + +The incoming protocol entity instance informs the nodal function of the request for a new connection and state "Incoming establishment pending" is entered. + +After receiving an acknowledgement from the nodal function that the connection establishment is accepted, an ECF message (establish confirm) is sent to the preceding AAL type 2 node and state "Established" is entered. + +#### **8.3.3.2 Unsuccessful connection setup** + +If a Signalling Association Identifier (SAID) allocation for the incoming protocol entity instance fails, an RLC message (release confirm) is returned containing the cause "Resource unavailable, unspecified". + +If a request to terminate the connection establishment from the nodal function is received, the SAID allocated to this particular incoming protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +If the nodal function informs the incoming protocol entity instance that the connection establishment is not accepted, an RLC message is issued towards the preceding AAL type 2 node with the cause and optionally the Automatic Congestion Control parameter provided by the nodal function. The SAID allocated to this particular incoming protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +#### **8.3.3.3 Normal connection release** + +Refer to 8.3.2.3. + +#### **8.3.3.4 Release request collision** + +Refer to 8.3.2.4. + +#### **8.3.3.5 Abnormal connection release procedures** + +Refer to 8.3.2.5. + +#### **8.3.3.6 Successful modification** + +Refer to 8.3.2.6. + +#### **8.3.3.7 Unsuccessful modification** + +Refer to 8.3.2.7. + +#### **8.3.3.8 Connection release during modification** + +Refer to 8.3.2.8. + +#### **8.3.3.9 Modification request collision** + +Refer to 8.3.2.9. + +#### **8.3.3.10 Unrecognized information procedures** + +Refer to 8.3.2.10. + +#### 8.3.3.11 State transition model + +##### 8.3.3.11.1 State transition + +The state transition diagram for the incoming protocol procedure is shown in Figure 8-3. + +![State transition diagram for the incoming protocol procedure. The diagram shows four main states: Idle, Release, Modify, and Established. Transitions are triggered by various messages and timers. Idle state transitions to Release, Modify, and Established. Release state transitions to Idle, Modify, and Established. Modify state transitions to Idle, Release, and Established. Established state transitions to Idle, Release, and Modify. The diagram includes sub-states like 'Outgoing release pending', 'Release collision', 'Outgoing modify pending', 'Modify collision', 'Incoming establishment pending', 'Incoming release pending', and 'Incoming modify pending'. Transitions are labeled with messages like TERMINATE.request, RELEASE.request, MODIFY.request, ESTABLISH.response, and timers like Timer_REL, Timer_MOD.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +The state transition diagram for the incoming protocol procedure is shown in Figure 8-3. The diagram is organized into four horizontal bands representing the main states: Idle, Release, Modify, and Established. The Idle state is at the top, and the Established state is at the bottom. Transitions between states are triggered by specific messages and timers. The diagram includes sub-states such as 'Outgoing release pending', 'Release collision', 'Outgoing modify pending', 'Modify collision', 'Incoming establishment pending', 'Incoming release pending', and 'Incoming modify pending'. Transitions are labeled with messages like TERMINATE.request, RELEASE.request, MODIFY.request, ESTABLISH.response, and timers like Timer\_REL, Timer\_MOD. The diagram also shows error indications like Timer\_REL ERROR.indication and Timer\_MOD ERROR.indication. The diagram is labeled Q.2630.3\_F8-3. + +State transition diagram for the incoming protocol procedure. The diagram shows four main states: Idle, Release, Modify, and Established. Transitions are triggered by various messages and timers. Idle state transitions to Release, Modify, and Established. Release state transitions to Idle, Modify, and Established. Modify state transitions to Idle, Release, and Established. Established state transitions to Idle, Release, and Modify. The diagram includes sub-states like 'Outgoing release pending', 'Release collision', 'Outgoing modify pending', 'Modify collision', 'Incoming establishment pending', 'Incoming release pending', and 'Incoming modify pending'. Transitions are labeled with messages like TERMINATE.request, RELEASE.request, MODIFY.request, ESTABLISH.response, and timers like Timer\_REL, Timer\_MOD. + +Figure 8-3/Q.2630.3 – State transition diagram for the incoming protocol procedure + +##### 8.3.3.11.2 SDL diagrams for the incoming protocol procedures + +The SDL diagram for the incoming protocol procedure is shown in Figure 8-4 (parts 1 to 6). + +The SDL diagrams contained in Figure 8-4 (parts 1 to 6) are an introduction to the procedures described in detail in 8.3.3. + +![SDL diagram for the incoming protocol procedure (Process IPP2b).](abeba89144744fac6a1571aa9f94889e_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> TRANSFER.indication (message) + TRANSFER.indication (message) --> ERQ message.type + ERQ message.type --> ERROR.indication (Cause) + ERROR.indication (Cause) --> Idle + ERQ message.type --> allocate SAID + allocate SAID --> allocation successful + allocation successful --> ESTABLISH.indication + ESTABLISH.indication --> Incoming Establishment Pending + allocation successful --> Construct RLC message + Construct RLC message --> TRANSFER.request (RLC message) + TRANSFER.request (RLC message) --> Idle + TRANSFER.indication (message) --> ERROR.indication (Cause) + ERROR.indication (Cause) --> Incoming Establishment Pending + Incoming Establishment Pending --> TRANSFER.indication (message) + TRANSFER.indication (message) --> ESTABLISH.response + ESTABLISH.response --> Construct ECF message + Construct ECF message --> TRANSFER.request (ECF message) + TRANSFER.request (ECF message) --> Established + TRANSFER.indication (message) --> TERMINATE.request + TERMINATE.request --> release SAID + release SAID --> Idle + ESTABLISH.response --> RELEASE.response + RELEASE.response --> Construct RLC message + Construct RLC message --> TRANSFER.request (RLC message) + TRANSFER.request (RLC message) --> release SAID + release SAID --> Idle + +``` + +The diagram illustrates the state transitions and message exchanges for Process IPP2b. It starts in the 'Idle' state. Upon receiving a 'TRANSFER.indication (message)' from Generic Signalling Transport, it checks the 'message.type'. If it's an 'ERQ', it sends an 'ERROR.indication (Cause)' to layer management and returns to 'Idle'. If not an 'ERQ', it attempts to 'allocate SAID'. If allocation is successful, it sends an 'ESTABLISH.indication' to the nodal function, enters 'Incoming Establishment Pending', constructs an 'RLC message', sends a 'TRANSFER.request (RLC message)' to Generic Signalling Transport, and returns to 'Idle'. If allocation fails, it constructs an 'RLC message', sends a 'TRANSFER.request (RLC message)', and returns to 'Idle'. If the 'message.type' is not 'ERQ', it sends an 'ERROR.indication (Cause)' to layer management and enters 'Incoming Establishment Pending'. From 'Incoming Establishment Pending', it receives a 'TRANSFER.indication (message)'. This leads to either an 'ESTABLISH.response' (which results in constructing an 'ECF message', sending a 'TRANSFER.request (ECF message)', and reaching 'Established'), a 'TERMINATE.request' (leading to 'release SAID' and 'Idle'), or a 'RELEASE.response' (leading to constructing an 'RLC message', sending a 'TRANSFER.request (RLC message)', 'release SAID', and 'Idle'). + +SDL diagram for the incoming protocol procedure (Process IPP2b). + +The signals to and from the nodal function are not defined and are for descriptive purposes only. + +Figure 8-4/Q.2630.3 (part 1 of 6) – SDL diagram for the incoming protocol procedure + +![SDL diagram for the incoming protocol procedure, starting from an 'Established' state. It details transitions for RELEASE, MODIFY, TERMINATE, and TRANSFER requests, leading to various pending states and subsequent message exchanges.](b3d488012fdceacab867cf24c5efef05_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Established + Established --> RELEASE_request: from nodal function + Established --> MODIFY_request: from nodal function + Established --> TERMINATE_request: from nodal function + Established --> TRANSFER_indication: from Generic Signalling Transport + + RELEASE_request --> set_REL_timer: set (now + 12, Timer_REL) + set_REL_timer --> Construct_REL_message: Construct REL message + Construct_REL_message --> TRANSFER_request_REL: TRANSFER. request (REL message) + TRANSFER_request_REL --> Outgoing_Release_Pending + + MODIFY_request --> set_MOD_timer: set (now + t6, Timer_MOD) + set_MOD_timer --> Construct_MOD_message: Construct MOD message + Construct_MOD_message --> TRANSFER_request_MOD: TRANSFER. request (MOD message) + TRANSFER_request_MOD --> Outgoing_Modify_Pending + + TERMINATE_request --> release_SAID_T: release SAID + release_SAID_T --> Idle_T: Idle + + TRANSFER_indication --> message_type_1: message.type + message_type_1 --> REL_1: REL + message_type_1 --> MOD_1: MOD + message_type_1 --> else_1: else + else_1 --> A1_1: A1 + REL_1 --> RELEASE_indication_1: RELEASE. indication + RELEASE_indication_1 --> Incoming_Release_Pending_1: Incoming Release Pending + Incoming_Release_Pending_1 --> to_nodal_function_1: to nodal function + + MOD_1 --> MODIFY_indication_1: MODIFY. indication + MODIFY_indication_1 --> Incoming_Modify_Pending_1: Incoming Modify Pending + + Outgoing_Release_Pending --> Timer_REL_2: Timer_REL + Outgoing_Release_Pending --> TERMINATE_request_2: TERMINATE. request + Outgoing_Release_Pending --> TRANSFER_indication_2: TRANSFER. indication + + Timer_REL_2 --> ERROR_indication: ERROR. indication (Cause) + ERROR_indication --> to_nodal_function_2: to nodal function + + TERMINATE_request_2 --> reset_TIMER_REL: reset (Timer_REL) + reset_TIMER_REL --> release_SAID_T2: release SAID + release_SAID_T2 --> Idle_T2: Idle + + TRANSFER_indication_2 --> message_type_2: message.type + message_type_2 --> REL_2: REL + message_type_2 --> RLC_2: RLC + message_type_2 --> else_2: else + else_2 --> A1_2: A1 + REL_2 --> Construct_RLC_message: Construct RLC message + Construct_RLC_message --> TRANSFER_request_RLC: TRANSFER. request (RLC message) + TRANSFER_request_RLC --> Release_Collision: Release Collision + + RLC_2 --> reset_TIMER_REL_2: reset (Timer_REL) + reset_TIMER_REL_2 --> RELEASE_confirm: RELEASE. confirm + RELEASE_confirm --> to_nodal_function_3: to nodal function + RELEASE_confirm --> release_SAID_T3: release SAID + release_SAID_T3 --> Idle_T3: Idle + +``` + +SDL diagram for the incoming protocol procedure, starting from an 'Established' state. It details transitions for RELEASE, MODIFY, TERMINATE, and TRANSFER requests, leading to various pending states and subsequent message exchanges. + +Figure 8-4/Q.2630.3 (part 2 of 6) – SDL diagram for the incoming protocol procedure + +![SDL diagram for the incoming protocol procedure (Process IPP2b).](487c58c79e44e6cf98b6368b6667b9c6_img.jpg) + +``` + +stateDiagram-v2 + state "Incoming Release Pending" as Incoming_Release_Pending + state "Release Collision" as Release_Collision + state "Idle" as Idle + state "A1" as A1 + + [*] --> Incoming_Release_Pending + Incoming_Release_Pending --> RELEASE_response : from nodal function + RELEASE_response --> Construct_RLC_message + Construct_RLC_message --> TRANSFER_request : to Generic Signalling Transport + TRANSFER_request --> release_SAID_1 + release_SAID_1 --> Idle + + Incoming_Release_Pending --> TERMINATE_request_1 : from nodal function + TERMINATE_request_1 --> release_SAID_1 + + Incoming_Release_Pending --> TRANSFER_indication_1 : from Generic Signalling Transport + TRANSFER_indication_1 --> A1 + + [*] --> Release_Collision + Release_Collision --> Timer_REL + Timer_REL --> ERROR_indication : to nodal function + ERROR_indication --> release_SAID_2 + release_SAID_2 --> Idle + + Release_Collision --> TERMINATE_request_2 : from nodal function + TERMINATE_request_2 --> reset_Timer_REL_1 + reset_Timer_REL_1 --> release_SAID_2 + + Release_Collision --> TRANSFER_indication_2 : from Generic Signalling Transport + TRANSFER_indication_2 --> message_type_check + state message_type_check <> + message_type_check --> reset_Timer_REL_2 : RLC + message_type_check --> A1 : else + + reset_Timer_REL_2 --> RELEASE_confirm : to nodal function + RELEASE_confirm --> release_SAID_3 + release_SAID_3 --> Idle + +``` + +The SDL diagram describes the 'Incoming Release Pending' and 'Release Collision' states for Process IPP2b. In 'Incoming Release Pending', receiving a 'RELEASE. response' from the nodal function triggers constructing an RLC message, sending a 'TRANSFER. request' to transport, releasing the SAID, and returning to 'Idle'. A 'TERMINATE. request' also leads to releasing the SAID and 'Idle'. A 'TRANSFER. indication' from transport leads to connector 'A1'. In the 'Release Collision' state, three events are handled: 1) 'Timer\_REL' expiry leads to an 'ERROR. indication' to the nodal function, releasing SAID, and 'Idle'. 2) A 'TERMINATE. request' from the nodal function resets 'Timer\_REL', releases SAID, and goes to 'Idle'. 3) A 'TRANSFER. indication' from transport checks the message type; if it is 'RLC', 'Timer\_REL' is reset, a 'RELEASE. confirm' is sent to the nodal function, SAID is released, and the process enters 'Idle'. If the message type is not 'RLC', it transitions to connector 'A1'. + +SDL diagram for the incoming protocol procedure (Process IPP2b). + +Figure 8-4/Q.2630.3 (part 3 of 6) – SDL diagram for the incoming protocol procedure + +![SDL diagram for the incoming protocol procedure. The diagram is split into two main sections. The top section shows the 'Outgoing Modify Pending' process, which branches into 'RELEASE. request', 'Timer_MOD', and 'TERMINATE. request'. 'RELEASE. request' leads to 'reset (Timer_MOD)', 'set (now + t2, Timer_REL)', 'Construct REL message', and 'TRANSFER. request (REL message)', ending at 'Outgoing Release Pending'. 'Timer_MOD' leads to 'ERROR. indication (Cause)'. 'TERMINATE. request' leads to 'reset (Timer_MOD)', 'release SAID', and 'Idle'. The bottom section shows the 'Outgoing Modify Pending' process receiving a 'TRANSFER. indication (message)' from 'Generic Signalling Transport'. It then checks 'message.type' with options 'REL', 'MOA', 'MOR', 'MOD', and 'else'. 'REL' leads to 'reset (Timer_MOD)', 'RELEASE. indication', and 'Incoming Release Pending'. 'MOA' leads to 'reset (Timer_MOD)', 'MODIFY. confirm', and 'Established'. 'MOR' leads to 'reset (Timer_MOD)', 'MODIFY-REJECT. confirm', and 'Established'. 'MOD' leads to 'Construct MOR message', 'TRANSFER. request (MOR message)', and 'Modify Collision'. 'else' leads to connector 'A1'. Various interfaces are labeled: 'from nodal function', 'to nodal function', and 'to Generic Signalling Transport'.](d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg) + +``` + +stateDiagram-v2 + state "Outgoing Modify Pending" as OMP1 + state "Outgoing Modify Pending" as OMP2 + + [*] --> OMP1 + OMP1 --> RELEASE_req: from nodal function + OMP1 --> Timer_MOD + OMP1 --> TERMINATE_req: from nodal function + + RELEASE_req --> reset_T1: reset (Timer_MOD) + reset_T1 --> set_T2: set (now + t2, Timer_REL) + set_T2 --> Construct_REL: Construct REL message + Construct_REL --> TRANSFER_req_REL: TRANSFER. request (REL message) + TRANSFER_req_REL --> Outgoing_Release_Pending: to Generic Signalling Transport + + Timer_MOD --> ERROR_ind: ERROR. indication (Cause) + ERROR_ind --> release_SAID: to nodal function + + TERMINATE_req --> reset_T2: reset (Timer_MOD) + reset_T2 --> release_SAID + release_SAID --> Idle + + [*] --> OMP2 + OMP2 --> TRANSFER_ind: from Generic Signalling Transport + TRANSFER_ind --> message_type: message.type + + state message_type <> + message_type --> REL + message_type --> MOA + message_type --> MOR + message_type --> MOD + message_type --> else + + REL --> reset_T3: reset (Timer_MOD) + reset_T3 --> RELEASE_ind: RELEASE. indication + RELEASE_ind --> Incoming_Release_Pending + + MOA --> reset_T4: reset (Timer_MOD) + reset_T4 --> MODIFY_conf: MODIFY. confirm + MODIFY_conf --> Established1: Established + + MOR --> reset_T5: reset (Timer_MOD) + reset_T5 --> MODIFY_REJ_conf: MODIFY-REJECT. confirm + MODIFY_REJ_conf --> Established2: Established + MODIFY_REJ_conf --> nodal_func: to nodal function + + MOD --> Construct_MOR: Construct MOR message + Construct_MOR --> TRANSFER_req_MOR: TRANSFER. request (MOR message) + TRANSFER_req_MOR --> Modify_Collision: to Generic Signalling Transport + + else --> A1 + +``` + +SDL diagram for the incoming protocol procedure. The diagram is split into two main sections. The top section shows the 'Outgoing Modify Pending' process, which branches into 'RELEASE. request', 'Timer\_MOD', and 'TERMINATE. request'. 'RELEASE. request' leads to 'reset (Timer\_MOD)', 'set (now + t2, Timer\_REL)', 'Construct REL message', and 'TRANSFER. request (REL message)', ending at 'Outgoing Release Pending'. 'Timer\_MOD' leads to 'ERROR. indication (Cause)'. 'TERMINATE. request' leads to 'reset (Timer\_MOD)', 'release SAID', and 'Idle'. The bottom section shows the 'Outgoing Modify Pending' process receiving a 'TRANSFER. indication (message)' from 'Generic Signalling Transport'. It then checks 'message.type' with options 'REL', 'MOA', 'MOR', 'MOD', and 'else'. 'REL' leads to 'reset (Timer\_MOD)', 'RELEASE. indication', and 'Incoming Release Pending'. 'MOA' leads to 'reset (Timer\_MOD)', 'MODIFY. confirm', and 'Established'. 'MOR' leads to 'reset (Timer\_MOD)', 'MODIFY-REJECT. confirm', and 'Established'. 'MOD' leads to 'Construct MOR message', 'TRANSFER. request (MOR message)', and 'Modify Collision'. 'else' leads to connector 'A1'. Various interfaces are labeled: 'from nodal function', 'to nodal function', and 'to Generic Signalling Transport'. + +Figure 8-4/Q.2630.3 (part 4 of 6) – SDL diagram for the incoming protocol procedure + +![SDL diagram for the incoming protocol procedure, showing two state machines: 'Modify Collision' and 'Incoming Modify Pending'.](909726977de6efd2d4df015198a2907b_img.jpg) + +The diagram consists of two State Transition Diagrams (STDs) for the incoming protocol procedure. + +**Top State Machine: Modify Collision** + +- Initial State:** Modify Collision (oval). +- Transitions:** + - RELEASE. request** (input) → **reset (Timer\_MOD)** (action) → **set (now + t2, Timer\_REL)** (action) → **Construct REL message** (action) → **TRANSFER. request (REL message)** (output) → **Outgoing Release Pending** (state). + - TERMINATE. request** (input) → **reset (Timer\_MOD)** (action) → **release SAID** (action) → **Idle** (state). + - Timer\_MOD** (input) → **ERROR. indication (Cause)** (output). + - TRANSFER. indication (message)** (input) → **message.type** (decision). + - REL** path: **reset (Timer\_MOD)** (action) → **RELEASE. indication** (output) → **Incoming Release Pending** (state). + - MOR** path: **reset (Timer\_MOD)** (action) → **MODIFY-REJECT. confirm** (output) → **Established** (state). + - else** path: **A1** (state).- Internal/Contextual Elements:** + - Dashed boxes indicate interactions with 'nodal function' and 'Generic Signalling Transport'. + - Arrows from 'RELEASE. request' and 'TERMINATE. request' point to a 'from nodal function' box. + - An arrow from 'ERROR. indication (Cause)' points to a 'to nodal function' box. + - An arrow from 'TRANSFER. request (REL message)' points to a 'to Generic Signalling Transport' box. + +**Bottom State Machine: Incoming Modify Pending** + +- Initial State:** Incoming Modify Pending (oval). +- Transitions:** + - MODIFY. response** (input) → **Construct MOA message** (action) → **TRANSFER. request (MOA message)** (output) → **Established** (state). + - MODIFY-REJECT. request** (input) → **Construct MOR message** (action) → **TRANSFER. request (MOR message)** (output) → **Established** (state). + - RELEASE. request** (input) → **set (now + t2, Timer\_REL)** (action) → **Construct REL message** (action) → **TRANSFER. request (REL message)** (output) → **Outgoing Release Pending** (state). + - TERMINATE. request** (input) → **release SAID** (action) → **Idle** (state). + - TRANSFER. indication (message)** (input) → **message.type** (decision). + - REL** path: **RELEASE. indication** (output) → **Incoming Release Pending** (state). + - else** path: **A1** (state).- Internal/Contextual Elements:** + - Dashed boxes indicate interactions with 'nodal function' and 'Generic Signalling Transport'. + - An arrow from 'MODIFY. response' points to a 'from nodal function' box. + - An arrow from 'TRANSFER. request (MOR message)' points to a 'to Generic Signalling Transport' box. + - An arrow from 'TRANSFER. request (REL message)' points to a 'to Generic Signalling Transport' box. + - An arrow from 'RELEASE. indication' points to a 'to nodal function' box. + +SDL diagram for the incoming protocol procedure, showing two state machines: 'Modify Collision' and 'Incoming Modify Pending'. + +Figure 8-4/Q.2630.3 (part 5 of 6) – SDL diagram for the incoming protocol procedure + +![SDL diagram for the incoming protocol procedure. The diagram is split into two parts. The top part shows a state transition from 'Any state except Idle and Outgoing Establishment Pending' to two parallel message paths: 'UNRECOGNIZED request (message)' leading to 'Construct Unrecognized Message' then 'TRANSFER. request (Unrecognized message)' to a sink; and 'CONFUSION. request' leading to 'Construct CFN message' then 'TRANSFER. request (CFN message)' to 'Generic Signalling Transport' and a sink. The bottom part starts at connector 'A1' and branches based on 'message.type': 'unrecognized' leads to 'UNRECOGNIZED. indication (message)' to 'nodal function' and a sink; 'CFN' leads to 'CONFUSION. indication (message)' to a sink; and 'else' leads to 'ERROR. indication (Cause)' to 'layer management' and a sink.](592f13acca3e6d5152dd4489f030d004_img.jpg) + +``` +stateDiagram-v2 + [*] --> TopState + state "Any state except Idle and Outgoing Establishment Pending" as TopState + TopState --> UNRECOGNIZED_request[UNRECOGNIZED request (message)] + TopState --> CONFUSION_request[CONFUSION. request] + UNRECOGNIZED_request --> Construct_Unrecognized[Construct Unrecognized Message] + Construct_Unrecognized --> TRANSFER_Unrecognized[TRANSFER. request (Unrecognized message)] + TRANSFER_Unrecognized --> Sink1([ - ]) + CONFUSION_request --> Construct_CFN[Construct CFN message] + Construct_CFN --> TRANSFER_CFN[TRANSFER. request (CFN message)] + TRANSFER_CFN --> Sink2([ - ]) + TRANSFER_CFN -.-> Generic_Signalling_Transport[Generic Signalling Transport] + A1((A1)) --> message_type{message.type} + message_type -- unrecognized --> UNRECOGNIZED_indication[UNRECOGNIZED. indication (message)] + message_type -- CFN --> CONFUSION_indication[CONFUSION. indication (message)] + message_type -- else --> ERROR_indication[ERROR. indication (Cause)] + UNRECOGNIZED_indication --> Sink3([ - ]) + UNRECOGNIZED_indication -.-> nodal_function[nodal function] + CONFUSION_indication --> Sink4([ - ]) + ERROR_indication --> Sink5([ - ]) + ERROR_indication -.-> layer_management[layer management] +``` + +SDL diagram for the incoming protocol procedure. The diagram is split into two parts. The top part shows a state transition from 'Any state except Idle and Outgoing Establishment Pending' to two parallel message paths: 'UNRECOGNIZED request (message)' leading to 'Construct Unrecognized Message' then 'TRANSFER. request (Unrecognized message)' to a sink; and 'CONFUSION. request' leading to 'Construct CFN message' then 'TRANSFER. request (CFN message)' to 'Generic Signalling Transport' and a sink. The bottom part starts at connector 'A1' and branches based on 'message.type': 'unrecognized' leads to 'UNRECOGNIZED. indication (message)' to 'nodal function' and a sink; 'CFN' leads to 'CONFUSION. indication (message)' to a sink; and 'else' leads to 'ERROR. indication (Cause)' to 'layer management' and a sink. + +Figure 8-4/Q.2630.3 (part 6 of 6) – SDL diagram for the incoming protocol procedure + +### **8.3.4 Maintenance protocol procedures** + +#### **8.3.4.1 Reset** + +##### **8.3.4.1.1 Sending reset** + +When a request for reset is received from the nodal function, a maintenance protocol entity instance is created and an SAID allocated to it. + +If the request indicates all AAL type 2 paths associated with a signalling transport association are to be reset, a RES message (Reset Request) containing the Connection Element Identifier parameter – with both the Path Identifier and the Channel Identifier coded with a "Null" value – is sent to the adjacent AAL type 2 node. + +If the request contains the identity of an AAL type 2 path with the channel identifier coded with a "Null" value, a RES message containing the connection element identifier parameter – with the path identifier set to indicate the path and the channel identifier coded with the "Null" value – is sent to the adjacent AAL type 2 node. + +If the request contains the identity of a path and a channel, a RES message containing the connection element identifier parameter – with the path identifier set to indicate the path and the channel identifier set to indicate the channel – is sent to the adjacent AAL type 2 node. + +When the RES message is sent, Timer\_RES is started and state "Outgoing reset pending" is entered. + +If an RSC message (reset confirm) is received in state "Outgoing reset pending", a reset confirmation is passed to the nodal function and Timer\_RES is stopped. The SAID allocated to the maintenance protocol entity instance is released and made available for new traffic. The maintenance protocol entity instance enters state "Idle". + +##### **8.3.4.1.2 Receiving reset** + +When a RES message (reset request) is received, a maintenance protocol entity instance will be invoked. + +If the Path Identifier field in the CEID parameter included in the RES message is coded with the "Null" value, an indication that all AAL type 2 paths associated with the signalling transport association must be reset is passed to the nodal function. + +If the path identifier field in the CEID parameter included in the RES message is coded with a "non-Null" value but the channel identifier field with a "Null" value, an indication that all channels within the AAL type 2 path must be reset is passed to the nodal function. + +If the RES message contains the CEID parameter with both a "non-Null" path identifier field and a "non-Null" channel identifier field, an indication that the channel within the identified path must be reset is passed to the nodal function. + +After notifying the nodal function, state "Incoming reset pending" is entered. + +When a Reset response is received from the nodal function, a RSC message (reset confirm) is sent to the peer protocol entity instance. The maintenance protocol entity instance enters state "Idle". + +##### **8.3.4.1.3 Exceptional reset procedures** + +If the SAID allocation fails, the nodal function is informed with a cause "Switching equipment congestion" and the maintenance protocol entity instance enters state "Idle". + +When Timer\_RES expires in state "Outgoing reset pending", the RES message is sent again, the nodal function is informed with a cause "Recovery on timer expiry", state "Outgoing reset continuing" is entered, and Timer\_RES is started again. + +When Timer\_RES expires in state "Outgoing reset continuing", the RES message is sent again and Timer\_RES is started again; the nodal function is not informed. + +When an RSC message (reset confirm) is received in state "Outgoing reset continuing", a reset confirmation is passed to the nodal function and Timer\_RES is stopped. The SAID allocated to the maintenance protocol entity instance is released and made available for new traffic. The maintenance protocol entity instance enters state "Idle". + +When a request to terminate the repetition of the reset procedure is received, Timer\_RES is stopped. The SAID allocated to the maintenance protocol entity instance is released and made available for new traffic. The maintenance protocol entity instance enters state "Idle". + +##### 8.3.4.1.4 State transition model + +The state transition diagram for the reset procedure is shown in Figure 8-5. + +![State transition diagram for the maintenance control procedure (reset). The diagram shows four states: Idle, Outgoing reset pending, Outgoing reset continuing, and Incoming reset pending. Transitions are triggered by messages like RESET.request, RESET.confirm, RESET.response, and RES message, or by timer expiration (Timer_RES).](ff87509cc2b267501d910a2d9f9054ac_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Outgoing_reset_pending: RESET.request, send RES message, start Timer_RES + Outgoing_reset_pending --> Idle: receive RSC message, RESET.confirm, stop Timer_RES + Outgoing_reset_pending --> Outgoing_reset_continuing: Timer_RES, send RES message, start Timer_RES, ERROR.indication + Outgoing_reset_continuing --> Idle: receive RSC message, RESET.confirm, stop Timer_RES + Outgoing_reset_continuing --> Outgoing_reset_continuing: Timer_RES, send RES message, start Timer_RES + Outgoing_reset_continuing --> Idle: TERMINATE.request + Idle --> Incoming_reset_pending: RESET.response, send RSC message + Incoming_reset_pending --> Idle: receive RES message, RESET.indication + +``` + +The diagram illustrates the state transitions for the maintenance control procedure (reset). It consists of four states: Idle, Outgoing reset pending, Outgoing reset continuing, and Incoming reset pending. Transitions are triggered by specific messages or timer expiration. The Idle state is the initial state. Transitions to Outgoing reset pending and Incoming reset pending lead to the Reset state, while transitions to Outgoing reset continuing lead to the Idle state. + +State transition diagram for the maintenance control procedure (reset). The diagram shows four states: Idle, Outgoing reset pending, Outgoing reset continuing, and Incoming reset pending. Transitions are triggered by messages like RESET.request, RESET.confirm, RESET.response, and RES message, or by timer expiration (Timer\_RES). + +Figure 8-5/Q.2630.3 – State transition diagram for the maintenance control procedure (reset) + +#### 8.3.4.2 Blocking and unblocking of AAL type 2 paths + +##### 8.3.4.2.1 Sending blocking/unblocking + +When a request for blocking is received from the nodal function, a new maintenance protocol entity instance is created, a new SAID is allocated and a BLO message (block request) is sent to the peer AAL type 2 signalling entity. The BLO message contains a connection element identifier with the path identifier coded to indicate the AAL type 2 path to be blocked (as instructed from the nodal function) and the channel identifier coded with the "Null" value. Timer\_BLO is started and state "Outgoing block pending" is entered. + +When a BLC message (block confirm) is received from the peer AAL type 2 signalling entity in state "Outgoing block pending", a confirmation of blocking is sent to the nodal function and Timer\_BLO is stopped. The SAID allocated to the maintenance procedure entity instance is released and made available for new traffic and state "Idle" is entered. + +When a request for unblocking is received from the nodal function, a new maintenance protocol entity instance is created, a new SAID is allocated and an UBL message (unblock request) is sent to the peer AAL type 2 signalling entity. The UBL message contains a connection element identifier with the path identifier coded to indicate the AAL type 2 path to be unblocked (as instructed from the nodal function) and the channel identifier coded with the "Null" value. Timer\_UBL is started and state "Outgoing unblock pending" is entered. + +When a UBC message (unblock confirm) is received from the peer AAL type 2 signalling entity in state "Outgoing unblock pending", a confirmation of unblocking is sent to the nodal function and Timer\_UBL is stopped. The SAID allocated to the maintenance protocol entity instance is released and made available for new traffic and state "Idle" is entered. + +##### 8.3.4.2.2 Receiving blocking/unblocking + +When a BLO message (block request) is received from the peer AAL type 2 signalling entity, a new maintenance protocol entity instance is created, an indication of the blocking is sent to the nodal function and state "Incoming block pending" is entered. + +When a response to the blocking is received from the nodal function in state "Incoming block pending", a BLC message (block confirm) is sent to the peer AAL type 2 signalling entity and state "Idle" is entered. + +When a UBL message (unblock request) is received from the peer AAL type 2 signalling entity, a new maintenance protocol entity instance is created, an indication of the unblocking is sent to the nodal function and state "Incoming unblock pending" is entered. + +When a response to the unblocking is received from the nodal function in state "Incoming unblock pending", a UBC message (unblock confirm) is sent to the peer AAL type 2 signalling entity and state "Idle" is entered. + +##### 8.3.4.2.3 Exceptional blocking and unblocking procedures + +If the SAID allocation fails, the nodal function is informed with a cause "Switching equipment congestion" and the maintenance protocol entity instance enters state "Idle". + +If Timer\_BLO expires, the nodal function is informed with a cause "Recovery on timer expiry", the SAID is released, and state "Idle" is entered. + +If Timer\_UBL expires, the nodal function is informed with a cause "Recovery on timer expiry", the SAID is released, and state "Idle" is entered. + +##### 8.3.4.2.4 State transition + +The state transition diagram for the path blocking procedure is shown in Figure 8-6. + +![State transition diagram for the maintenance control procedure (blocking and unblocking). The diagram shows four states: Idle, Outgoing block pending, Incoming block pending, Outgoing unblock pending, and Incoming unblock pending. Transitions are triggered by messages (BLOCK.request, BLC.confirm, BLO.indication, UNBLOCK.request, UBC.confirm) and timers (Timer_BLO, Timer_UBL).](d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Outgoing_block_pending : BLOCK.request send BLO message start Timer_BLO + Outgoing_block_pending --> Idle : receive BLC message BLOCK.confirm stop Timer_BLO + Outgoing_block_pending --> Idle : Timer_BLO ERROR.indication + Idle --> Incoming_block_pending : receive BLO message BLOCK.indication + Incoming_block_pending --> Idle : BLOCK_response send BLC message + Idle --> Outgoing_unblock_pending : UNBLOCK.request send UBL message start Timer_UBL + Outgoing_unblock_pending --> Idle : receive UBC message UNBLOCK.confirm stop Timer_UBL + Idle --> Incoming_unblock_pending : receive UBL message UNBLOCK.indication + Incoming_unblock_pending --> Idle : UNBLOCK_response send UBC message + +``` + +The diagram illustrates the state transitions for the maintenance control procedure. It starts with an initial state leading to 'Idle'. From 'Idle', a 'BLOCK.request' message triggers a transition to 'Outgoing block pending', where a 'BLO message' is sent and 'Timer\_BLO' starts. A return to 'Idle' occurs upon receiving a 'BLC message' (BLOCK.confirm) and stopping 'Timer\_BLO', or if 'Timer\_BLO' expires with an 'ERROR.indication'. Another transition from 'Idle' to 'Incoming block pending' is triggered by a 'receive BLO message' (BLOCK.indication), returning to 'Idle' upon a 'BLOCK\_response' (send BLC message). Similarly, a 'UNBLOCK.request' message triggers a transition to 'Outgoing unblock pending', where a 'UBL message' is sent and 'Timer\_UBL' starts. A return to 'Idle' occurs upon receiving a 'UBC message' (UNBLOCK.confirm) and stopping 'Timer\_UBL', or if 'Timer\_UBL' expires with an 'ERROR.indication'. Finally, a 'receive UBL message' (UNBLOCK.indication) triggers a transition to 'Incoming unblock pending', returning to 'Idle' upon a 'UNBLOCK\_response' (send UBC message). The states are grouped into 'Idle', 'Block', and 'Unblock' categories on the right side of the diagram. + +State transition diagram for the maintenance control procedure (blocking and unblocking). The diagram shows four states: Idle, Outgoing block pending, Incoming block pending, Outgoing unblock pending, and Incoming unblock pending. Transitions are triggered by messages (BLOCK.request, BLC.confirm, BLO.indication, UNBLOCK.request, UBC.confirm) and timers (Timer\_BLO, Timer\_UBL). + +Figure 8-6/Q.2630.3 – State transitions of the maintenance control procedure (blocking and unblocking) + +#### **8.3.4.3 Unrecognized information procedures** + +When an unrecognized message, parameter, or subfield value is received, the message, the parameter, or the subfield value respectively is conveyed to the nodal function for the appropriate action. + +If a request to send a notification of receipt of unrecognized information is received from the nodal function, the BLC message (block confirm), UBC message (unblock confirm), or RSC message (reset confirm) shall contain the cause received from the nodal function. + +When a cause parameter is received in a BLC message (block confirm), UBC message (unblock confirm), or RSC message (reset confirm), the cause parameter is conveyed to the nodal function for the appropriate action. + +#### **8.3.4.4 SDL diagrams for the maintenance control procedures** + +The SDL diagram for the maintenance control procedure is shown in Figure 8-7 (parts 1 to 4). + +The SDL diagrams contained in Figure 8-7 (parts 1 to 4) are an introduction to the procedures described in detail in 8.3.4. + +![SDL diagram for the maintenance control procedure. The diagram starts with an 'Idle' state. Three parallel transitions are shown: RESET.request, BLOCK.request, and UNBLOCK.request. Each transition involves allocating a SAID, checking if successful, setting a timer, constructing a message, and transferring it. RESET leads to RES message, BLOCK to BLO message, and UNBLOCK to UBL message. All three lead to 'Outgoing' pending states. A separate path labeled 'A3' shows a 'message.type' decision leading to 'UNRECOGNIZED' or 'ERROR' indications.](235e996e83e7d5198cf9d909f5713cdd_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> RESET.request + Idle --> BLOCK.request + Idle --> UNBLOCK.request + + RESET.request --> allocate_SAID_RES[allocate SAID] + allocate_SAID_RES --> allocation_successful_RES{allocation successful} + allocation_successful_RES -- false --> ERROR_indication_RES[ERROR indication (Cause)] + allocation_successful_RES -- TRUE --> set_timer_RES[set (now+t3, Timer_RES)] + set_timer_RES --> Construct_RES[Construct RES message] + Construct_RES --> TRANSFER_RES[TRANSFER request (RES message)] + TRANSFER_RES --> Outgoing_Reset[Outgoing Reset Pending] + + BLOCK.request --> allocate_SAID_BLO[allocate SAID] + allocate_SAID_BLO --> allocation_successful_BLO{allocation successful} + allocation_successful_BLO -- false --> ERROR_indication_BLO[ERROR indication (Cause)] + allocation_successful_BLO -- TRUE --> set_timer_BLO[set (now+t4, Timer_BLO)] + set_timer_BLO --> Construct_BLO[Construct BLO message] + Construct_BLO --> TRANSFER_BLO[TRANSFER request (BLO message)] + TRANSFER_BLO --> Outgoing_Block[Outgoing Block Pending] + + UNBLOCK.request --> allocate_SAID_UBL[allocate SAID] + allocate_SAID_UBL --> allocation_successful_UBL{allocation successful} + allocation_successful_UBL -- false --> ERROR_indication_UBL[ERROR indication (Cause)] + allocation_successful_UBL -- TRUE --> set_timer_UBL[set (now+t5, Timer_UBL)] + set_timer_UBL --> Construct_UBL[Construct UBL message] + Construct_UBL --> TRANSFER_UBL[TRANSFER request (UBL message)] + TRANSFER_UBL --> Outgoing_Unblock[Outgoing Unblock Pending] + + ERROR_indication_RES --> Idle + ERROR_indication_BLO --> Idle + ERROR_indication_UBL --> Idle + + [*] --> A3((A3)) + A3 --> message_type{message.type} + message_type -- unrecognized --> UNRECOGNIZED[UNRECOGNIZED indication (message)] + message_type -- else --> ERROR_indication_A3[ERROR indication (Cause)] + UNRECOGNIZED --> End1[ - ] + ERROR_indication_A3 --> End2[ - ] + + note right of RESET.request: from nodal function + note right of allocate_SAID_RES: to nodal function + note right of TRANSFER_RES: to Generic Signalling Transport + note right of BLOCK.request: from nodal function + note right of allocate_SAID_BLO: to nodal function + note right of TRANSFER_BLO: to Generic Signalling Transport + note right of UNBLOCK.request: from nodal function + note right of allocate_SAID_UBL: to nodal function + note right of TRANSFER_UBL: to Generic Signalling Transport + note right of UNRECOGNIZED: to nodal function + note right of ERROR_indication_A3: to layer management + note left of End1: The signals to and from the nodal function are not defined and are for descriptive purposes only. + +``` + +SDL diagram for the maintenance control procedure. The diagram starts with an 'Idle' state. Three parallel transitions are shown: RESET.request, BLOCK.request, and UNBLOCK.request. Each transition involves allocating a SAID, checking if successful, setting a timer, constructing a message, and transferring it. RESET leads to RES message, BLOCK to BLO message, and UNBLOCK to UBL message. All three lead to 'Outgoing' pending states. A separate path labeled 'A3' shows a 'message.type' decision leading to 'UNRECOGNIZED' or 'ERROR' indications. + +Figure 8-7/Q.2630.3 (part 1 of 4) – SDL diagram for the maintenance control procedure + +![SDL diagram for the maintenance control procedure (Process MCP2).](6d697ce8828ba75fddee0a1b7767a7ca_img.jpg) + +The diagram illustrates the state transitions for Process MCP2. It begins with an initial state labeled 'Idle'. A transition arrow points from 'Idle' to a message box labeled 'TRANSFER. indication (message)'. A dashed box to the left of this message box contains the text 'from Generic Signalling Transport'. Below the message box is a decision diamond labeled 'message.type'. Three arrows branch out from this diamond, labeled 'RES', 'BLO', and 'UBL'. The 'RES' arrow points to a message box labeled 'RESET. indication', which then points to a state box labeled 'Incoming Reset Pending'. Below this state box is a dashed box containing the text 'to nodal function'. The 'BLO' arrow points to a message box labeled 'BLOCK. indication', which then points to a state box labeled 'Incoming Block Pending'. Below this state box is a dashed box containing the text 'to nodal function'. The 'UBL' arrow points to a message box labeled 'UNBLOCK. indication', which then points to a state box labeled 'Incoming Unblock Pending'. Below this state box is a dashed box containing the text 'to nodal function'. A large dashed box encloses the 'RESET. indication', 'Incoming Reset Pending', and 'to nodal function' components, as well as the 'BLOCK. indication', 'Incoming Block Pending', and 'to nodal function' components. Another dashed box encloses the 'UNBLOCK. indication', 'Incoming Unblock Pending', and 'to nodal function' components. + +SDL diagram for the maintenance control procedure (Process MCP2). + +Figure 8-7/Q.2630.3 (part 2 of 4) – SDL diagram for the maintenance control procedure + +![SDL diagram for the maintenance control procedure. The diagram is divided into four main sections based on initial states: Outgoing Reset Pending, Outgoing Reset Continuing, Incoming Reset Pending, and Outgoing Reset Continuing. It shows transitions between states like Idle, Reset Pending, and Reset Continuing, triggered by messages like TRANSFER.indication, RESET.confirm, and TERMINATE.request. It includes actions like constructing messages, setting timers, and releasing SAIDs. Junctions A3 are used to link different parts of the diagram.](9687bd5e8b62cadba093b0d1b70536cd_img.jpg) + +Process MCP2 MCP13(4) + +``` + +stateDiagram-v2 + [*] --> Outgoing_Reset_Pending: Outgoing Reset Pending + Outgoing_Reset_Pending --> Timer_RES_1: Timer_RES + Timer_RES_1 --> set_t1: set (now+t3, Timer_RES) + set_t1 --> Construct_RES_1: Construct RES message + Construct_RES_1 --> TRANSFER_request_1: TRANSFER.request (RES message) + TRANSFER_request_1 --> ERROR_indication: ERROR.indication (Cause) + ERROR_indication --> Outgoing_Reset_Continuing_1: Outgoing Reset Continuing + + TRANSFER_request_1 --> message_type_1: message.type + message_type_1 --> RSC_1: RSC + message_type_1 --> else_1: else + else_1 --> A3_1: A3 + + RSC_1 --> reset_t1: reset (Timer_RES) + reset_t1 --> RESET_confirm_1: RESET.confirm + RESET_confirm_1 --> release_SAID_1: release SAID + release_SAID_1 --> Idle_1: Idle + + [*] --> Outgoing_Reset_Continuing_2: Outgoing Reset Continuing + Outgoing_Reset_Continuing_2 --> Timer_RES_2: Timer_RES + Timer_RES_2 --> set_t2: set (now+t3, Timer_RES) + set_t2 --> Construct_RES_2: Construct RES message + Construct_RES_2 --> TRANSFER_request_2: TRANSFER.request (RES message) + TRANSFER_request_2 --> Outgoing_Reset_Continuing_2 + + TRANSFER_request_2 --> message_type_2: message.type + message_type_2 --> RSC_2: RSC + message_type_2 --> else_2: else + else_2 --> A3_2: A3 + + RSC_2 --> reset_t2: reset (Timer_RES) + reset_t2 --> RESET_confirm_2: RESET.confirm + RESET_confirm_2 --> release_SAID_2: release SAID + release_SAID_2 --> Idle_2: Idle + + [*] --> Outgoing_Reset_Continuing_3: Outgoing Reset Continuing + Outgoing_Reset_Continuing_3 --> TERMINATE_request: TERMINATE.request + TERMINATE_request --> reset_t3: reset (Timer_RES) + reset_t3 --> release_SAID_3: release SAID + release_SAID_3 --> Idle_3: Idle + + [*] --> Incoming_Reset_Pending: Incoming Reset Pending + Incoming_Reset_Pending --> RESET_response: RESET.response + RESET_response --> Construct_RSC: Construct RSC message + Construct_RSC --> TRANSFER_request_3: TRANSFER.request (RSC message) + TRANSFER_request_3 --> Idle_4: Idle + + TRANSFER_request_3 --> message_type_3: message.type + message_type_3 --> A3_3: A3 + +``` + +SDL diagram for the maintenance control procedure. The diagram is divided into four main sections based on initial states: Outgoing Reset Pending, Outgoing Reset Continuing, Incoming Reset Pending, and Outgoing Reset Continuing. It shows transitions between states like Idle, Reset Pending, and Reset Continuing, triggered by messages like TRANSFER.indication, RESET.confirm, and TERMINATE.request. It includes actions like constructing messages, setting timers, and releasing SAIDs. Junctions A3 are used to link different parts of the diagram. + +Figure 8-7/Q.2630.3 (part 3 of 4) – SDL diagram for the maintenance control procedure + +![Four SDL diagrams for maintenance control procedure: Outgoing Block Pending, Outgoing Unblock Pending, Incoming Block Pending, and Incoming Unblock Pending.](301f4a188198a15b1415d54545b07e0d_img.jpg) + +Process MCP2 MCP14(4) + +The diagram consists of four State Transition Diagrams (STDs) arranged in a 2x2 grid, representing the maintenance control procedure (Process MCP2). + +- Outgoing Block Pending (Top Left):** + - Initial state: **Outgoing Block Pending** (Initial state symbol). + - Transition to **Timer\_BLO** (State symbol). + - From **Timer\_BLO**, a transition labeled **TRANSFER. indication (message)** (Transition symbol) leads to a decision node **message.type** (Decision symbol). + - The **message.type** node has two branches: + - else**: Leads to state **A3** (State symbol). + - BLC**: Leads to action **reset (Timer\_BLO)** (Action symbol). + - From **reset (Timer\_BLO)**, a transition leads to state **BLOCK. confirm** (State symbol). + - From **BLOCK. confirm**, a transition labeled **ERROR. indication (Cause)** (Transition symbol) leads to state **release SAID** (State symbol). + - From **release SAID**, a transition leads to the final state **Idle** (Final state symbol). + - There are dashed boxes indicating protocol layers: **from Generic Signalling Transport** for the incoming message and **to nodal function** for the outgoing message. +- Outgoing Unblock Pending (Top Right):** + - Initial state: **Outgoing Unblock Pending** (Initial state symbol). + - Transition to **Timer\_UBL** (State symbol). + - From **Timer\_UBL**, a transition labeled **TRANSFER. indication (message)** (Transition symbol) leads to a decision node **message.type** (Decision symbol). + - The **message.type** node has two branches: + - else**: Leads to state **A3** (State symbol). + - UBC**: Leads to action **reset (Timer\_UBL)** (Action symbol). + - From **reset (Timer\_UBL)**, a transition leads to state **UNBLOCK. confirm** (State symbol). + - From **UNBLOCK. confirm**, a transition labeled **ERROR. indication (Cause)** (Transition symbol) leads to state **release SAID** (State symbol). + - From **release SAID**, a transition leads to the final state **Idle** (Final state symbol). + - There are dashed boxes indicating protocol layers: **from Generic Signalling Transport** for the incoming message and **to nodal function** for the outgoing message. +- Incoming Block Pending (Bottom Left):** + - Initial state: **Incoming Block Pending** (Initial state symbol). + - From this state, two transitions are possible: + - BLOCK. response** (Transition symbol) from **from nodal function** (dashed box) leads to action **Construct BLC message** (Action symbol). + - TRANSFER. indication (message)** (Transition symbol) from **from Generic Signalling Transport** (dashed box) leads to state **A3** (State symbol). + - From **Construct BLC message**, a transition labeled **TRANSFER. request (BLC message)** (Transition symbol) leads to state **Idle** (Final state symbol). + - This transition is associated with **to Generic Signalling Transport** (dashed box). +- Incoming Unblock Pending (Bottom Right):** + - Initial state: **Incoming Unblock Pending** (Initial state symbol). + - From this state, two transitions are possible: + - TRANSFER. indication (message)** (Transition symbol) from **from Generic Signalling Transport** (dashed box) leads to state **A3** (State symbol). + - UNBLOCK. response** (Transition symbol) from **from nodal function** (dashed box) leads to action **Construct UBC message** (Action symbol). + - From **Construct UBC message**, a transition labeled **TRANSFER. request (UBC message)** (Transition symbol) leads to state **Idle** (Final state symbol). + - This transition is associated with **to Generic Signalling Transport** (dashed box). + +Four SDL diagrams for maintenance control procedure: Outgoing Block Pending, Outgoing Unblock Pending, Incoming Block Pending, and Incoming Unblock Pending. + +Figure 8-7/Q.2630.3 (part 4 of 4) – SDL diagram for the maintenance control procedure + +## 8.4 List of timers + +The timers used in the procedures described in 8.3 are listed in Table 8-1 together with a timeout value range, their cause for setting the timer, resetting the timer, and the action at expiry of the timer. + +**Table 8-1/Q.2630.3 – List of timers** + +| Timer | Timeout value | Cause for initiation | Normal termination | At expiry | +|-----------|---------------|-----------------------------|-------------------------------|------------------------------------------------------------------------------------| +| Timer_ERQ | 5-30 s (t1) | When an ERQ message is sent | At the receipt of ECF message | Release all resources and the connection, send RES message. | +| Timer_REL | 2-60 s (t2) | When an REL message is sent | At the receipt of RLC message | Release resources, send RES message. | +| Timer_RES | 2-60 s (t3) | When an RES message is sent | At the receipt of RSC message | Repeat RES message, restart Timer_RES, at first expiry: inform the nodal function. | +| Timer_BLO | 2-60 s (t4) | When a BLO message is sent | At the receipt of BLC message | Alert maintenance system, inform the nodal function. | +| Timer_UBL | 2-60 s (t5) | When an UBL message is sent | At the receipt of UBC message | Alert maintenance system, inform the nodal function. | +| Timer_MOD | 5-30 s (t6) | When a MOD message is sent | At the receipt of MOA message | Release all resources and the connection, send RES message. | + +NOTE – In the diagnostic field associated with a cause field indicating "Recovery on timer expiry", the timer number is included. Timer\_ERQ is coded as the IA5 character "1"; Timer\_MOD is coded as the IA5 character "6". + +# Annex A + +# Support for non-switched scenario + +## A.1 Introduction + +The AAL type 2 signalling protocol described in this Recommendation can be deployed in support of a non-switched scenario as depicted in Figure A.1. + +![Diagram showing two AAL type 2 service endpoints connected by a single line. The left box is labeled 'AAL type 2 service endpoint' and the right box is also labeled 'AAL type 2 service endpoint'. A horizontal line connects the two boxes. To the right of the right box is the text 'Q.2630.3_FA-1'.](23d9fcc2863a6b0548d6b4e8abf15106_img.jpg) + +Diagram showing two AAL type 2 service endpoints connected by a single line. The left box is labeled 'AAL type 2 service endpoint' and the right box is also labeled 'AAL type 2 service endpoint'. A horizontal line connects the two boxes. To the right of the right box is the text 'Q.2630.3\_FA-1'. + +**Figure A.1/Q.2630.3 – Non-switched scenario** + +In this scenario, AAL type 2 paths are typically provisioned – with each originating AAL type 2 service endpoint having one signalling transport association with each neighbouring AAL type 2 service endpoint. There is no AAL type 2 switch used in this scenario. + +This annex describes the subset of the signalling requirements needed to support the non-switched scenario. Because most signalling procedures are link-by-link, there are few differences from the switched scenario. Since the non-switched scenario is a subset of the switched scenario, there are no additional requirements to support non-switched. + +Subclauses below correspond with similarly numbered subclauses in the body of ITU-T Rec. Q.2630.1 [15]. + +## **A.2 References** + +Clause 2/Q.2630.1 [15] applies. + +## **A.3 Definitions** + +Clause 3/Q.2630.1 [15] applies. + +## **A.4 Abbreviations** + +Clause 4/Q.2630.1 [15] applies. + +## **A.5 General framework of the AAL type 2 signalling protocol** + +The AAL type 2 signalling protocol provides the signalling capability to establish, release and maintain AAL type 2 point-to-point connections across a single ATM VCC that carries AAL type 2 links. These services are accessible via the AAL type 2 User Service Access Point (A2SU-SAP). + +Two peer AAL type 2 signalling entities rely on the generic signalling transport service to provide assured data transfer between them and service availability indications. These services are accessible via the Generic Signalling Transport Service Access Point (GST-SAP). + +NOTE – Primitives over the A2SU-SAP, GST-SAP, and LM-SAP are used for descriptive purpose only. They do not imply a specific implementation. + +Both peer AAL type 2 signalling entities provide the same set of services. + +The AAL type 2 signalling entity is subdivided into protocol entities and nodal functions as shown in Figure A.5-1. At each AAL type 2 service endpoint, the AAL type 2 signalling entity communicates with the AAL type 2 served user. + +![Diagram of AAL type 2 signalling protocol reference architecture for the non-switched scenario. The diagram shows two identical stacks of protocol layers connected by a dashed line representing an 'AAL type 2 signalling message'. Each stack consists of: an 'AAL type 2 service endpoint' at the top, followed by an 'AAL type 2 served user' block; an 'A2SU-SAP' interface; an 'AAL type 2 signalling entity' block containing 'Nodal function' and 'Protocol entity' sub-blocks; an 'LM-SAP' interface connected to a 'Layer management' block; a 'GST-SAP' interface; a 'Signalling transport converter' block (with a '(Note)' label); and finally, a 'Signalling transport' block at the bottom, which includes examples like 'MTP3b + NNI-SAAL, UNI-SAAL, SSCOP, ...'. The 'Protocol entity' blocks in both stacks are connected to this common 'Signalling transport' block.](c7111699f84f3e2bc4016b7876f10de6_img.jpg) + +Diagram of AAL type 2 signalling protocol reference architecture for the non-switched scenario. The diagram shows two identical stacks of protocol layers connected by a dashed line representing an 'AAL type 2 signalling message'. Each stack consists of: an 'AAL type 2 service endpoint' at the top, followed by an 'AAL type 2 served user' block; an 'A2SU-SAP' interface; an 'AAL type 2 signalling entity' block containing 'Nodal function' and 'Protocol entity' sub-blocks; an 'LM-SAP' interface connected to a 'Layer management' block; a 'GST-SAP' interface; a 'Signalling transport converter' block (with a '(Note)' label); and finally, a 'Signalling transport' block at the bottom, which includes examples like 'MTP3b + NNI-SAAL, UNI-SAAL, SSCOP, ...'. The 'Protocol entity' blocks in both stacks are connected to this common 'Signalling transport' block. + +Q.2630.3\_FA-5.1 + +NOTE – A signalling transport converter instance is associated with each AAL type 2 signalling transport. + +**Figure A.5-1/Q.2630.3 – AAL type 2 signalling protocol reference architecture for the non-switched scenario** + +Protocol Entities define the interactions between two adjacent AAL type 2 nodes. AAL type 2 messages are exchanged between peer protocol entities using the generic signalling transport service. + +The AAL type 2 signalling is independent of the signalling transport, although an assured data transport is required and a message size limit applies. To adapt the signalling transport services to a specific signalling transport service, a signalling bearer converter may be needed. The specification of signalling bearer converters is beyond the scope of this Recommendation (see ITU-T Recs Q.2150.0 [12], Q.2150.1 [22], and Q.2150.2 [23]). + +The protocol entity is divided into several procedures as shown in Figure A.5-2. + +![Diagram of the internal structure of the AAL type 2 signalling protocol entity. A large box labeled 'Protocol entity' contains three smaller boxes: 'Outgoing protocol procedures', 'Incoming protocol procedures', and 'Maintenance protocol procedures'.](54a1e5d91d7f442361767b1f8c81c777_img.jpg) + +``` +graph TD + PE[Protocol entity] --> OPP[Outgoing protocol procedures] + PE --> IPP[Incoming protocol procedures] + PE --> MP[Maintenance protocol procedures] +``` + +Diagram of the internal structure of the AAL type 2 signalling protocol entity. A large box labeled 'Protocol entity' contains three smaller boxes: 'Outgoing protocol procedures', 'Incoming protocol procedures', and 'Maintenance protocol procedures'. + +Q.2630\_FA-5.2 + +**Figure A.5-2/Q.2630.3 – Internal structure of the AAL type 2 signalling protocol entity** + +The outgoing protocol procedures provide the mechanism to initiate an AAL type 2 connection request. The incoming protocol procedures are applied when a request for an AAL type 2 connection is received from a peer entity. Both of these procedures provide for the orderly release of an AAL type 2 connection. The maintenance protocol procedures provide the mechanisms to align the status of the AAL type 2 resources within the two adjacent AAL type 2 nodes and procedures to block and unblock an AAL type 2 path. + +The unrecognized information procedures in the nodal function as well as in the protocol entities provide the forward compatibility mechanism which enables extension of the protocol in the future. + +The nodal function keeps track of the AAL type 2 path resources. + +### **A.5.1 Interface between the AAL type 2 signalling entity and the AAL type 2 served user** + +Clause 5.1/Q.2630.1 [15] applies, except for the following: + +In the ESTABLISH.request primitive, AAL type 2 Service Endpoint Address (DA2EA) is not included. + +### **A.5.2 Service provided by the generic signalling transport service** + +Clause 5.2/Q.2630.1 [15] applies except for the following: + +CONGESTION.indication primitive does not apply. + +### **A.5.3 Interface between the AAL type 2 signalling entities and layer management** + +Clause 5.3/Q.2630.1 [15] applies. + +## **A.6 Forward and backward compatibility** + +Clause 6/Q.2630.1 [15] applies. + +## **A.7 Format and coding of AAL type 2 signalling protocol** + +Clause 7/Q.2630.1 [15] applies. + +### **A.7.1 Coding conventions for the AAL type 2 signalling protocol** + +Clause 7.1/Q.2630.1 [15] and its subclauses apply. + +### **A.7.2 Format and coding of the AAL type 2 signalling protocol messages** + +#### **A.7.2.1 AAL type 2 signalling protocol messages** + +Clause 7.2.1/Q.2630.1 [15] applies. + +#### A.7.2.2 Parameters of the AAL type 2 signalling protocol messages + +Clause 7.2.2/Q.2630.1 [15] applies as modified below: + +The parameters of the AAL type 2 signalling protocol messages are shown in Table A.7-1. The indications of "mandatory" and "optional" are for information only. The authoritative definition is given in A.8. If any difference between the indications in this clause and the definitions in A.8 exists, the definitions in A.8 take precedence. + +Multiple presence of the same parameter in a single message is not permitted. + +**Table A.7-1/Q.2630.3 (part 1 of 2) – Parameters of the AAL type 2 signalling protocol messages** + +| AAL type 2 parameter | AAL type 2 message | | | | +|--------------------------------------------------------|--------------------|-----|-----|----------| +| | ERQ | ECF | REL | RLC | +| Cause | – | – | M | (Note 4) | +| Connection Element ID | M | – | – | – | +| Destination Signalling Association Identifier (Note 1) | (Note 2) | M | M | M | +| Link Characteristics | O | – | – | – | +| Originating Signalling Association Identifier | M | M | – | – | +| Served User Generated Reference | O | – | – | – | +| Served User Transport | O | – | – | – | +| Service Specific Information (Audio) | (Note 3) | – | – | – | +| Service Specific Information (Multirate) | (Note 3) | – | – | – | +| Service Specific Information (SAR-assured) | (Note 3) | – | – | – | +| Service Specific Information (SAR-unassured) | (Note 3) | – | – | – | +| Test Connection Indicator | O | – | – | – | + +M Mandatory parameter +O Optional parameter +– Parameter not present + +NOTE 1 – This row designates the Destination Signalling Association Identifier field in the message header. + +NOTE 2 – The Destination Signalling Association Identifier field contains the value "unknown". + +NOTE 3 – At most one of these parameters is present in an instance of the message. + +NOTE 4 – The "Cause" parameter is present in the Release Confirm message if: + +- the RLC is used to reject a connection establishment; or +- the cause reports unrecognized unknown information received in the REL message. + +**Table A.7-1/Q.2630.3 (part 2 of 2) – Parameters of the AAL Type 2 Signalling Protocol messages** + +| AAL type 2 parameter | AAL type 2 message | | | | | | | +|--------------------------------------------------------|--------------------|----------|---------------|----------|---------------|----------|-----| +| | RES | RSC | BLO | BLC | UBL | UBC | CFN | +| Cause | – | (Note 4) | – | (Note 4) | – | (Note 4) | M | +| Connection Element ID | M | – | M
(Note 3) | – | M
(Note 3) | – | – | +| Destination Signalling Association Identifier (Note 1) | (Note 2) | M | (Note 2) | M | (Note 2) | M | M | +| Originating Signalling Association Identifier | M | – | M | – | M | – | – | + +M Mandatory parameter +O Optional parameter +– Parameter not present +NOTE 1 – This row designates the Destination Signalling Association Identifier field in the message header. +NOTE 2 – The Destination Signalling Association Identifier field contains the value "unknown". +NOTE 3 – The Channel Identifier field is set to "Null". +NOTE 4 – The "Cause" parameter is present only if the cause reports unrecognized information received. + +The identifiers of the AAL type 2 message parameters are defined in Table A.7-2. + +**Table A.7-2/Q.2630.3 – Identifiers of the AAL Type 2 message parameters** + +| AAL type 2 Parameter | Ref. | Acronym | Identifier | +|-----------------------------------------------|--------|---------|-----------------| +| Cause | 7.3.1 | CAU | 0 0 0 0 0 0 0 1 | +| Connection Element ID | 7.3.2 | CEID | 0 0 0 0 0 0 1 0 | +| Link Characteristics | 7.3.5 | ALC | 0 0 0 0 0 1 0 1 | +| Originating Signalling Association Identifier | 7.3.6 | OSAID | 0 0 0 0 0 1 1 0 | +| Served User Generated Reference | 7.3.7 | SUGR | 0 0 0 0 0 1 1 1 | +| Served User Transport | 7.3.8 | SUT | 0 0 0 0 1 0 0 0 | +| Service Specific Information (Audio) | 7.3.9 | SSIA | 0 0 0 0 1 0 0 1 | +| Service Specific Information (Multirate) | 7.3.10 | SSIM | 0 0 0 0 1 0 1 0 | +| Service Specific Information (SAR-assured) | 7.3.11 | SSISA | 0 0 0 0 1 0 1 1 | +| Service Specific Information (SAR-unassured) | 7.3.12 | SSISU | 0 0 0 0 1 1 0 0 | +| Test Connection Indicator | 7.3.13 | TCI | 0 0 0 0 1 1 0 1 | + +### A.7.3 Parameter specification of the AAL type 2 signalling protocol messages + +Applicable parameters are specified in 7.3/Q.2630.1 [15] except: + +- For 7.3.3 "Destination E.164 service endpoint address" and 7.3.4 "Destination NSAP service endpoint address" which are not applicable. + +### **A.7.4 Field specification of the AAL type 2 signalling protocol parameters** + +Applicable fields are specified in 7.4/Q.2630.1 [15] except: + +- a) In 7.4.12/Q.2630.1 [15] add the following sentence: "Optionally, it is possible to increase the CPS-SDU size to 64 octets". +- b) Subclauses 7.4.13/Q.2630.1, 7.4.14/Q.2630.1 and 7.4.15/Q.2630.1 are not applicable. +- c) In 7.4.16/Q.2630.1 [15], cause "Unallocated (unassigned) number" is not applicable. + +## **A.8 Procedure of the AAL type 2 signalling protocol** + +Before an ATM VCC (AAL type 2 path) is put into service between a pair of adjacent AAL type 2 nodes, certain actions need to be performed. An identifier called the AAL type 2 path identifier is assigned to the ATM VCC. This identifier is used to refer to the ATM VCC in the AAL type 2 signalling protocol messages. The AAL type 2 path identifier shall uniquely identify the ATM VCC between the two adjacent AAL type 2 nodes. + +On any ATM VCC used for AAL type 2 connections, all CID values from "8" to "255" are available for assignment. + +Any time a new ATM VCC is put into service, the ownership of the ATM VCC shall be determined before AAL type 2 connections are established in it. In case of switched ATM VCC, the owner of the VCC shall be the AAL type 2 node that initiated the establishment of the VCC. In case of PVC and soft PVC, it is the responsibility of the management system to determine the owner of the VCC. + +The nodal function is informed by layer management of a newly established AAL type 2 path by the use of the ADD-PATH.indication primitive containing the adjacent AAL type 2 node identifier, the AAL type 2 path identifier, and the ownership. The nodal function is informed by layer management of the removal of an AAL type 2 path by use of the REMOVE-PATH.indication primitive containing the adjacent AAL type 2 node identifier and the AAL type 2 path identifier. + +In order to minimize the likelihood of CID collision, the following CID allocation mechanism shall be used: + +- if the AAL type 2 node owns the AAL type 2 path that carries the new connection, it allocates CID values from CID value 8 upwards; and +- if the AAL type 2 node does not own the AAL type 2 path that carries the new connection, it allocates CID values from CID value 255 downwards. + +NOTE – Causes in the procedures defined in clause 8/Q.2630.1 [15] specify which ITU-T standardized code should be used in cause parameters of AAL type 2 signalling protocol messages. Implementation dependent non-standardized causes may be used for AAL type 2 signalling entity internal processing and for A2SU-SAP and LM-SAP cause primitive parameters. + +The service endpoint address, the served user generated reference, the served user transport parameter, the link characteristics, the SSCS information, and the test connection indicator shall not be modified by the nodal function. The served user generated reference and the served user transport are parameters with significance to the served user only; therefore, they shall not be examined by the nodal function. + +### **A.8.1 Compatibility** + +Clause 8.1 applies with the following modifications: + +- a) In 8.1.1/Q.2630.1 [15] "General requirements on receipt of unrecognized signalling information", bullet item d) and the Note below it are not applicable. + +- b) In 8.1.2.1/Q.2630.1 [15] "Unrecognized messages", the bullet item "transfer the message transparently" is not applicable. +- c) In 8.1.2.2/Q.2630.1 [15] "Unrecognized parameters", the bullet item "transfer the parameter transparently" appears twice and is not applicable in either location. + +### **A.8.2 Nodal functions** + +#### **A.8.2.1 Nodal functions for AAL type 2 nodes with served user interaction** + +Clause 8.2.1/Q.2630.1 [15] applies with the modifications below. + +- a) Subclause 8.2.1.1.1.1/Q.2630.1 "Actions at the originating AAL type 2 service endpoint" is replaced by the following paragraphs: + +When the nodal function receives an ESTABLISH.request primitive from the AAL type 2 served user, it determines the availability of a route with enough AAL type 2 path resources and selects an AAL type 2 path to the succeeding AAL type 2 service endpoint. + +Selection of an AAL type 2 path typically is based on: + +- the test connection indicator; +- link information (link characteristics); and +- other information (such as SSCS information). + +AAL type 2 node internal resources are allocated for the new connection from the originating AAL type 2 served user to the outgoing AAL type 2 path. + +On the selected outgoing AAL type 2 path, the CID and other resources (e.g. indicated by link characteristic or SSCS information) are allocated for the outgoing AAL type 2 link. + +An outgoing protocol entity instance is invoked and the following parameters are passed to it: the AAL type 2 Path Identifier, and a CID value. The nodal function shall pass the following parameters to the outgoing protocol entity instance only if they were conveyed by the originating AAL type 2 served user: the link characteristics, the SSCS information, the served user generated reference, the served user transport, and the test connection indicator. + +NOTE 1 – Through-connection at AAL type 2 service endpoints is not specified by this Recommendation. It may be controlled by the AAL type 2 served user. + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, an ESTABLISH.confirm primitive is sent to the AAL type 2 served user. + +- b) Subclause 8.2.1.1.1.2/Q.2630.1 "Actions at the destination AAL type 2 service endpoint" is replaced by the following paragraphs: + +Upon receiving an indication from an incoming protocol entity instance requesting a new connection, the nodal function checks the availability of the CID value and other resources, e.g., indicated by link characteristic or SSCS information in the incoming AAL type 2 path. + +If the test connection indicator parameter is present, a "locally blocked" or "remotely blocked" AAL type 2 path shall be acceptable for the incoming connection. + +If the CID and the other resources are available, they are allocated to the new connection. + +AAL type 2 node internal resources are allocated for the new connection from the incoming AAL type 2 path to the destination AAL type 2 served user. + +The nodal function acknowledges the successful AAL type 2 connection establishment towards the incoming protocol entity instance. + +An ESTABLISH.indication primitive is sent to the AAL type 2 served user to inform it of the successfully established new connection. The nodal function shall pass the following parameters to the outgoing protocol entity instance only if they were conveyed by the incoming protocol entity instance: the SSCS information, the served user transport, the served user generated reference, and the test connection indicator. + +NOTE 2 – Through-connection at AAL type 2 service endpoints is not specified by this Recommendation. It may be controlled by the AAL type 2 served user. + +- c) Subclause 8.2.1.1.2.1/Q.2630.1 "Actions at the originating AAL type 2 service endpoint" is replaced by the following paragraphs: + +If the AAL type 2 path selection or the CID and other resources allocation described in 8.2.1.1.1.1 fails, a RELEASE.confirm primitive is returned to the AAL type 2 served user with one of the following causes: + +- "No route to destination"; +- "No circuit/channel available"; +- "Resource unavailable, unspecified"; +- "Network out of order"; or +- "Temporary failure". + +If AAL type 2 node internal resources are not available for the new connection, a RELEASE.confirm primitive is sent to the AAL type 2 served user with the cause "Switching equipment congestion". + +Upon receiving a negative acknowledgement for the connection setup request from the outgoing protocol entity instance, all the resources associated with this AAL type 2 link are released and made available for new traffic. The association to the outgoing protocol entity instance is released. Features that enable a further connection attempt, involving the selection of a different AAL type 2 path within the same route, may be implemented. If no further connection attempt is made, the AAL type 2 node internal resources are released and a RELEASE.confirm primitive is sent to the AAL type 2 served user with the cause received from the outgoing protocol entity instance. + +Upon receiving an indication from the outgoing protocol entity instance that a timer has expired, the association to the outgoing protocol entity instance is released and a reset procedure is started (see 8.2.1.2.1.1 case 3 a). The AAL type 2 node internal resources are released. A RELEASE.confirm primitive is sent to the AAL type 2 served user with the cause received from the outgoing protocol entity instance, i.e., "Recovery on timer expiry". + +#### **A.8.2.2 Nodal functions for AAL type 2 nodes without served user interaction** + +Subclause 8.2.2/Q.2630.1 [15] is not applicable. + +### **A.8.3 Protocol entity** + +Subclause 8.3/Q.2630.1 [15] applies. + +### **A.8.4 List of timers** + +Subclause 8.4/Q.2630.1 [15] applies. + +# Annex B + +# Coding of the compatibility information + +## B.1 Coding of the compatibility information for CS-1 and CS-2 networks using link characteristics for connection resource allocation + +### B.1.1 Message compatibility + +To ensure backward compatibility with AAL type 2 nodes conforming only to ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16], the message compatibility field of the Modify Request (MOD), Modify Acknowledge (MOA), and Modify Reject (MOR) messages shall be set as indicated in Table B.1. + +Table B.1/Q.2630.3 – Coding of the message compatibility information + +| Message | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------------------------------|----------------------|-----------------------------|-----------------------|---|----------------|-----------------------------|-----------------------|---| +| | pass-on not possible | | | | general action | | | | +| | res. | send notification indicator | instruction indicator | | res. | send notification indicator | instruction indicator | | +| Modify Request (MOD) with Transfer Capability | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | +| | | do not send notification | discard message | | | do not send notification | discard message | | +| Modify Request (MOD) without Transfer Capability | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | +| | | do not send notification | discard message | | | do not send notification | pass on message | | +| Modify Acknowledge (MOA) | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | +| | | do not send notification | discard message | | | do not send notification | pass on message | | +| Modify Reject (MOR) | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | +| | | do not send notification | discard message | | | do not send notification | pass on message | | + +### B.1.2 Parameter compatibility + +To ensure backward compatibility with AAL type 2 nodes conforming only to ITU-T Rec. Q.2630.1 [15], the parameter compatibility field of the new or differently used parameters introduced in ITU-T Rec. Q.2630.2 [16] shall be set as indicated in Table B.2. + +**Table B.2/Q.2630.3 – Coding of the parameter compatibility information** + +| Parameter | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------------------------------------------------------------------------------|----------------------|-------------------------------|-----------------------|-------------------------|----------------|-------------------------------|-----------------------|------------------------| +| | pass-on not possible | | | | general action | | | | +| | res. | send notification indicator | instruction indicator | | res. | send notification indicator | instruction indicator | | +| Connection Element Identifier (CEID) in RLC message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Modify Support for Link Characteristics (MSLC) in ERQ and ECF messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Modify Support for Service Specific Information (MSSSI) in ERQ and ECF messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Preferred Link Characteristics (PLC) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Preferred Service Specific Information (Audio Extended) (PSSIAE) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Preferred Service Specific Information (Multirate Extended) (PSSIME) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Service Specific Information (Audio Extended) (SSIAE) in ERQ message | 0 | 0
do not send notification | 1 | 1
release connection | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Service Specific Information (Multirate Extended) (SSIME) in ERQ message | 0 | 0
do not send notification | 1 | 1
release connection | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Path Type (PT) in ERQ message | 0 | 1
send notification | 0 | 1
discard parameter | 0 | 1
send notification | 0 | 0
pass on parameter | +| Served User Correlation ID (SUCI) in MOD and MOA messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | + +## B.2 Coding of the compatibility information for CS-1 and CS-2 networks using service specific information for connection resource allocation + +### B.2.1 Message compatibility + +To ensure backward compatibility with AAL type 2 nodes conforming only to ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16], the message compatibility field of the Modify Request (MOD), Modify Acknowledge (MOA), and Modify Reject (MOR) messages shall be set as indicated in Table B.3. + +**Table B.3/Q.2630.3 – Coding of the message compatibility information** + +| Message | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------|----------------------|-------------------------------|-----------------------|----------------------|----------------|-------------------------------|-----------------------|----------------------| +| | pass-on not possible | | | | general action | | | | +| | res. | send notification indicator | instruction indicator | | res. | send notification indicator | instruction indicator | | +| Modify Request (MOD) | 0 | 0
do not send notification | 1 | 0
discard message | 0 | 0
do not send notification | 1 | 0
discard message | +| Modify Acknowledge (MOA) | 0 | 0
do not send notification | 1 | 0
discard message | 0 | 0
do not send notification | 0 | 0
pass on message | +| Modify Reject (MOR) | 0 | 0
do not send notification | 1 | 0
discard message | 0 | 0
do not send notification | 0 | 0
pass on message | + +### B.2.2 Parameter compatibility + +To ensure backward compatibility with AAL type 2 nodes conforming only to ITU-T Rec. Q.2630.1 [15], the parameter compatibility field of the new or differently used parameters introduced in ITU-T Rec. Q.2630.2 [16] shall be set as indicated in Table B.4. + +**Table B.4/Q.2630.3 – Coding of the parameter compatibility information** + +| Parameter | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------------------------------------------------------------------------------|----------------------|-------------------------------|-----------------------|-------------------------|----------------|-------------------------------|-----------------------|-------------------------| +| | pass-on not possible | | | | general action | | | | +| | res. | send notification indicator | instruction indicator | | res. | send notification indicator | instruction indicator | | +| Connection Element Identifier (CEID) in RLC message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Modify Support for Service Specific Information (MSSSI) in ERQ and ECF messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Preferred Service Specific Information (Audio Extended) (PSSIAE) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Preferred Service Specific Information (Multirate Extended) (PSSIME) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Service Specific Information (Audio Extended) (SSIAE) in ERQ message | 0 | 0
do not send notification | 1 | 1
release connection | 0 | 0
do not send notification | 1 | 1
release connection | +| Service Specific Information (Multirate Extended) (SSIME) in ERQ message | 0 | 0
do not send notification | 1 | 1
release connection | 0 | 0
do not send notification | 1 | 1
release connection | +| Path Type (PT) in ERQ message | 0 | 1
send notification | 0 | 1
discard parameter | 0 | 1
send notification | 0 | 0
pass on parameter | +| Served User Correlation ID (SUCI) in MOD and MOA messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | + +## B.3 Coding of the compatibility information of the new parameters for CS-1 and CS-2 networks + +To ensure backward compatibility with AAL type 2 nodes conforming only to ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16], the parameter compatibility field of the new parameter shall be set as indicated in Table B.5. + +**Table B.5/Q.2630.3 – Coding of the parameter compatibility information** + +| Parameter | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------------------------------------------------------------------------|----------------------|-------------------------------|-----------------------|------------------------|----------------|-------------------------------|-----------------------|------------------------| +| | pass-on not possible | | | | general action | | | | +| | res. | send notification indicator | instruction indicator | | res. | send notification indicator | instruction indicator | | +| Origination AAL type 2 Service Endpoint Address (OA2AE) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Connection Priority (CP) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Congestion Level (CL) in REL or RLC message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Hop Counter (HC) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| TAR Controlled Connection (TCC) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Transfer Capability Support (TCS) in ERQ and ECF messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 1
discard parameter | +| Fixed Bandwidth Transfer Capability (FBW) in ERQ and MOD messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Variable Bandwidth Stringent Transfer Capability (VBWS) in ERQ and MOD messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Variable Bandwidth Tolerant Transfer Capability (VBWT) in ERQ and MOD messages | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Preferred Fixed Bandwidth Transfer Capability (PFBW) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Preferred Variable Bandwidth Stringent Transfer Capability (PVBWS) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | +| Preferred Variable Bandwidth Tolerant Transfer Capability (PVBWT) in ERQ message | 0 | 0
do not send notification | 0 | 1
discard parameter | 0 | 0
do not send notification | 0 | 0
pass on parameter | + +# Annex C + +# Interworking with CS-1 and CS-2 nodes for connection resource allocation + +Examples of interworking cases are illustrated in Appendix III. + +## C.1 Connection resources indicated with link characteristic parameters + +### C.1.1 Connection establishment + +#### C.1.1.1 Introduction + +NOTE 1 – In order to ensure interworking the following three cases are considered: + +- a) If no connection resource modifications are required for the AAL type 2 connection, the originating AAL type 2 served user may include a Link Characteristics parameter in the ESTABLISH.request primitive that corresponds to the Transfer Capability parameter. +- b) If connection resource modifications may be required for the AAL type 2 connection and interworking to CS-1 nodes is not required, the originating AAL type 2 served user may include a Link Characteristics parameter and a Modify Support for Link Characteristics parameter in the ESTABLISH.request primitive; the Link Characteristics parameter corresponds to the Transfer Capability parameter. +- c) If connection resource modifications may be required for the AAL type 2 connection and interworking to CS-1 nodes may be required, the originating AAL type 2 served user may additionally include the following parameters in the ESTABLISH.request primitive: + - the Link Characteristics; + - the Preferred Transfer Capability; + - the Preferred Link Characteristics; and + - the Modify Support for Link Characteristics. + +Interworking with CS-2 and CS-1 nodes is designed such that: + +- If the Modify Support for Link Characteristics parameter is received by the destination AAL type 2 service endpoint, no CS-1 node is part of the AAL type 2 connection; resource allocation for the AAL type 2 connection is based on the Preferred Transfer Capability (for CS-3 nodes) and Preferred Link Characteristics (for CS-2 nodes) and the connection resources are modifiable. +- If the Modify Support for Link Characteristics parameter is not received by the destination AAL type 2 service endpoint, a CS-1 node is part of the AAL type 2 connection; resource allocation for the AAL type 2 connection is based on the Transfer Capability (for CS-3 nodes) and Link Characteristics (for CS-1 and CS-2 nodes) and the connection resources are not modifiable. +- In all cases, the originating AAL type 2 served user includes a Transfer Capability Support parameter in the ESTABLISH.request primitive as well. If this parameter is received by a destination CS-3 service endpoint, it is sent back towards the originating AAL type 2 service endpoint. The complete AAL type 2 connection passes through CS-3 nodes only and the originating and the destination AAL type 2 served users know that the full functionality of this Recommendation is available for this connection. + +NOTE 2 – From the point of view of this Recommendation, it is regarded to be within the responsibility of the AAL type 2 served user to ensure consistency between Transfer Capability and Link Characteristics parameters. + +#### C.1.1.2 Actions at the originating AAL type 2 service endpoint + +In addition to the specifications in 8.2, the following applies: + +When the nodal function receives an ESTABLISH.request primitive from the AAL type 2 served user, the following restrictions on the optionality of the parameters of the primitive apply: + +- The Transfer Capability Support parameter shall be present; +- The Link Characteristics parameter shall be present; +- The Modify Support for Link Characteristics parameter may be present; +- The Preferred Link Characteristics parameter may be present only if the Modify Support for Link Characteristics parameter is also present; +- The Preferred Transfer Capability parameter shall be present if the AAL type 2 Preferred Link Characteristics parameter is present; and +- If a Preferred Transfer Capability parameter is specified, it must refer to the same AAL type 2 transfer capability as the Transfer Capability parameter. + +NOTE 1 – For example, if the Transfer Capability parameter indicates a Variable Bandwidth Stringent Transfer Capability, the Preferred Transfer Capability parameter, if present, may only indicate a Variable Bandwidth Stringent Transfer Capability. + +Depending on the presence of Preferred Transfer Capability parameter, the following applies: + +- If the Preferred Transfer Capability parameter is not present, connection admission control and connection resource allocation are performed as defined in 8.2. +- If the Preferred Transfer Capability parameter is present, the connection admission control and connection resource allocation shall be based on the most demanding of the Preferred Transfer Capability and the Transfer Capability. + +NOTE 2 – The concept of "demanding" depends on the connection admission control algorithm and connection resource allocation mechanisms in use which are outside the scope of this Recommendation. + +If the originating AAL type 2 service endpoint receives a notification that the succeeding node did not recognize the Path Type parameter, the connection establishment shall be allowed to continue (QoS requirements are met by the network default stringent QoS class), or the connection is released and a RELEASE.confirm primitive is returned to the AAL type 2 served user with the cause "Resource unavailable, unspecified" (QoS requirements are not met by network default stringent QoS class). + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, the following applies depending on the presence of the Modify Support for Link Characteristics parameter and the Preferred Transfer Capability parameter: + +- If the Modify Support for Link Characteristics parameter is not present, connection admission control and connection resource allocation shall reflect the Transfer Capability (TC). +- If the Modify Support for Link Characteristics parameter is present, connection admission control and connection resource allocation shall reflect the Preferred Transfer Capability (PTC) if present; otherwise, the Transfer Capability (TC) shall be reflected. + +#### C.1.1.3 Actions at AAL type 2 nodes without served user interaction + +In addition to the specifications in 8.2, the following applies: + +Upon receiving notification from an incoming protocol entity instance requesting a new connection and the Transfer Capability parameter is not conveyed by the incoming protocol entity instance, + +- the nodal function prepares a Transfer Capability parameter corresponding to the Link Characteristics parameter; and +- if a Preferred Link Characteristics parameter is also conveyed by the incoming protocol entity instance, the nodal function prepares a Preferred Transfer Capability parameter corresponding to the Preferred Link Characteristics parameter. The Preferred Transfer Capability parameter must refer to the same AAL type 2 transfer capability as the Transfer Capability parameter. + +NOTE 1 – For example, if the Transfer Capability parameter indicates a Variable Bandwidth Stringent Transfer Capability, the Preferred Transfer Capability parameter, if present, may only indicate a Variable Bandwidth Stringent Transfer Capability. + +NOTE 2 – In Appendix II, guidelines to derive the Transfer Capability parameter from a Link Characteristics parameter are shown. + +These parameters are treated as if they would have been conveyed by the incoming protocol entity instance. + +If a Preferred Transfer Capability parameter is conveyed by the incoming protocol entity instance but not a Preferred Link Characteristics parameter, the Preferred Transfer Capability parameter is discarded; subsequent treatment of the parameters is as if the Preferred Transfer Capability parameter would not have been conveyed by the incoming protocol entity instance. + +Depending on the presence of Preferred Transfer Capability parameter, the following applies: + +- If the Preferred Transfer Capability parameter is not present, the connection admission control and connection resource allocation are performed as defined in 8.2. +- If the Preferred Transfer Capability parameter is present, the connection admission control and connection resource allocation shall be based on the most demanding of the Preferred Transfer Capability and the Transfer Capability. + +NOTE 3 – The concept of "demanding" depends on the connection admission control algorithm and connection resource allocation mechanisms in use which are outside the scope of this Recommendation. + +If AAL type 2 node receives a notification that the succeeding node did not recognize the Path Type parameter, the AAL type 2 node allows the connection to be established (QoS requirements are met by the network default stringent QoS class), or releases the connection with the cause "Resource unavailable, unspecified" (QoS requirements are not met by network default stringent QoS class). + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, the following applies depending on the presence of the Modify Support for Link Characteristics parameter and the Preferred Transfer Capability parameter: + +- If the Modify Support for Link Characteristics parameter is not present, connection admission control and connection resource allocation shall reflect the Transfer Capability (TC). +- If the Modify Support for Link Characteristics parameter is present, connection admission control and connection resource allocation shall reflect the Preferred Transfer Capability (PTC) if present; otherwise, the Transfer Capability (TC) shall be reflected. + +#### **C.1.1.4 Actions at the destination AAL type 2 service endpoint** + +In addition to the specifications in 8.2, the following applies: + +Upon receiving notification from an incoming protocol entity instance requesting a new connection and the Transfer Capability parameter is not conveyed by the incoming protocol entity instance, + +- the nodal function prepares a Transfer Capability parameter corresponding to the Link Characteristics parameter; and +- if a Preferred Link Characteristics parameter is also conveyed by the incoming protocol entity instance, the nodal function prepares a Preferred Transfer Capability parameter corresponding to the Preferred Link Characteristics parameter. The Preferred Transfer Capability parameter must refer to the same AAL type 2 transfer capability as the Transfer Capability parameter. + +NOTE 1 – For example, if the Transfer Capability parameter indicates a Variable Bandwidth Stringent Transfer Capability, the Preferred Transfer Capability parameter, if present, may only indicate a Variable Bandwidth Stringent Transfer Capability. + +NOTE 2 – In Appendix II, guidelines to derive the Transfer Capability parameter from a Link Characteristics parameter are shown. + +These parameters are treated as if they would have been conveyed by the incoming protocol entity instance. + +If a Preferred Transfer Capability parameter is conveyed by the incoming protocol entity instance but not a Preferred Link Characteristics parameter, the Preferred Transfer Capability parameter is discarded; subsequent treatment of the parameters is as if the Preferred Transfer Capability parameter would not have been conveyed by the incoming protocol entity instance. + +Depending on the presence of Preferred Transfer Capability parameter, the following applies: + +- If the Preferred Transfer Capability parameter is not present, AAL type 2 connection resources (internal and on the incoming AAL type 2 path) indicated by the Transfer Capability (TC) parameter are allocated as specified in 8.2. +- If the Preferred Transfer Capability parameter is present, AAL type 2 connection resources (internal and on the incoming AAL type 2 path) indicated by the Preferred Transfer Capability (PTC) parameter are allocated. + +If a Transfer Capability Support parameter was received from the incoming protocol instance, the parameter shall be passed to the incoming protocol entity instance when the nodal function acknowledges the successful AAL type 2 connection establishment. + +If a Modify Support for Link Characteristics parameter was received from the incoming protocol instance, the parameter shall be passed to the incoming protocol entity instance when the nodal function acknowledges the successful AAL type 2 connection establishment. + +### **C.1.2 Connection resource modification** + +#### **C.1.2.1 Introduction** + +If, during connection establishment, a Transfer Capability Support parameter was received by an AAL type 2 service endpoint, connection resource modification as specified in 8.2 applies. + +If, during connection establishment, a Transfer Capability Support parameter was not received but a Modify Support for Link Characteristics parameter was received by an AAL type 2 service endpoint, connection resource modification follows the specifications in this subclause. + +If, during connection establishment, neither a Transfer Capability Support parameter nor a Modify Support for Link Characteristics parameter was received by an AAL type 2 service endpoint, no connection resource modification is possible. + +NOTE – From the point of view of this Recommendation, it is regarded to be within the responsibility of the AAL type 2 served user to ensure consistency between Transfer Capability and Link Characteristics parameters. + +#### **C.1.2.2 Actions at the AAL type 2 service endpoint originating the modification** + +In addition to the specifications in 8.2, the following applies: + +The AAL type 2 served user shall include a Link Characteristics parameter (corresponding to the Transfer Capability parameter) in the MODIFY.request primitive. + +#### **C.1.2.3 Actions at AAL type 2 nodes without served user interaction** + +Upon receiving notification from a protocol entity instance requesting a connection modification and the Transfer Capability parameter is not conveyed by the protocol entity instance, the nodal function prepares a Transfer Capability parameter corresponding to the Link Characteristics parameter. This parameter is treated as if it would have been conveyed by the protocol entity instance. + +NOTE – In Appendix II, guidelines to derive the Transfer Capability parameter from a Link Characteristics parameter are shown. + +#### **C.1.2.4 Actions at the AAL type 2 service endpoint receiving the modification** + +Upon receiving notification from a protocol entity instance requesting a connection modification and the Transfer Capability parameter is not conveyed by the protocol entity instance, the nodal function prepares a Transfer Capability parameter corresponding to the Link Characteristics parameter. This parameter is treated as if it would have been conveyed by the protocol entity instance. + +NOTE – In Appendix II, guidelines to derive the Transfer Capability parameter from a Link Characteristics parameter are shown. + +## **C.2 Connection resources indicated with service specific information parameters** + +### **C.2.1 Connection establishment** + +#### **C.2.1.1 Introduction** + +NOTE 1 – In order to ensure interworking the following three cases are considered: + +- a) If no connection resource modifications are required for the AAL type 2 connection, the originating AAL type 2 served user may include an SSCS Information parameter in the ESTABLISH.request primitive whose connection resource requirements corresponds to those of the Transfer Capability parameter. +- b) If connection resource modifications may be required for the AAL type 2 connection and interworking with CS-1 nodes is not required, the originating AAL type 2 served user may include an SSCS Information parameter and a Modify Support for SSCS Information parameter in the ESTABLISH.request primitive; the connection resource requirements of the SSCS Information parameter corresponds to those of the Transfer Capability parameter. +- c) If connection resource modifications may be required for the AAL type 2 connection and interworking to CS-1 nodes may be required, the originating AAL type 2 served user may additionally include the following parameters in the ESTABLISH.request primitive: + - the SSCS Information; + - the Preferred Transfer Capability; + - the Preferred SSCS Information; and + - the Modify Support for SSCS Information. + +Interworking with CS-2 and CS-1 nodes is designed such that: + +- If the Modify Support for SSCS Information parameter is received by the destination AAL type 2 service endpoint, no CS-1 node is part of the AAL type 2 connection; resource allocation for the AAL type 2 connection is based on the Preferred Transfer Capability (for CS-3 nodes) and Preferred SSCS Information (for CS-2 nodes) and the connection resources are modifiable. +- If the Modify Support for SSCS Information parameter is not received by the destination AAL type 2 service endpoint, a CS-1 node is part of the AAL type 2 connection; resource allocation for the AAL type 2 connection is based on the Transfer Capability (for CS-3 nodes) and SSCS Information (for CS-1 and CS-2 nodes) and the connection resources are not modifiable. +- In all cases, the originating AAL type 2 served user includes a Transfer Capability Support parameter in the ESTABLISH.request primitive as well. If this parameter is received by a destination CS-3 service endpoint, it is sent back towards the originating AAL type 2 service endpoint. The complete AAL type 2 connection passes through CS-3 nodes only and the originating and the destination AAL type 2 served users know that the full functionality of this Recommendation is available for this connection. + +NOTE 2 – From the point of view of this Recommendation, it is regarded to be within the responsibility of the AAL type 2 served user to ensure consistency between the resource requirements of the Transfer Capability and SSCS Information parameters. + +#### **C.2.1.2 Actions at the originating AAL type 2 service endpoint** + +In addition to the specifications in 8.2, the following applies: + +When the nodal function receives an ESTABLISH.request primitive from the AAL type 2 served user, the following restrictions on the optionality of the parameters of the primitive apply: + +- The Transfer Capability Support parameter shall be present; +- The SSCS Information parameter shall be present; +- The Modify Support for SSCS Information parameter may be present; +- The Preferred SSCS Information parameter may only be present if the Modify Support for SSCS Information parameter is present; +- If a Preferred SSCS Information parameter is specified, it has to refer to the same SSCS Information type as the SSCS Information parameter. + +NOTE 1 – For example, if the SSCS Information parameter indicates an Audio SSCS Information, the Preferred SSCS Information parameter, if present, may only indicate an Audio SSCS Information. + +- If a Preferred SSCS Information parameter is specified, the SSCS Information "Audio Extended" and "Multirate Extended" shall not be used in the SSCS Information parameter. +- The Preferred Transfer Capability parameter shall be present if the Preferred SSCS Information parameter is present; and +- If a Preferred Transfer Capability parameter is specified, it has to refer to the same Transfer Capability as the Transfer Capability parameter. + +NOTE 2 – For example, if the Transfer Capability parameter indicates a Variable Bandwidth Stringent Transfer Capability, the Preferred Transfer Capability parameter, if present, may only indicate a Variable Bandwidth Stringent Transfer Capability. + +Depending on the presence of Preferred Transfer Capability parameter, the following applies: + +- If the Preferred Transfer Capability parameter is not present, connection admission control and connection resource allocation are performed as defined in 8.2. +- If the Preferred Transfer Capability parameter is present, the connection admission control and connection resource allocation shall be based on the most demanding of the Preferred Transfer Capability and the Transfer Capability. + +NOTE 3 – The concept of "demanding" depends on the Connection Admission Control algorithm and connection resource allocation mechanisms in use which are outside the scope of this Recommendation. + +If the originating AAL type 2 service endpoint receives a notification that the succeeding node did not recognize the Path Type parameter, the connection establishment shall be allowed to continue (QoS requirements are met by the network default stringent QoS class), or the connection is released and a RELEASE.confirm primitive is returned to the AAL type 2 served user with the cause "Resource unavailable, unspecified" (QoS requirements are not met by network default stringent QoS class). + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, the following applies depending on the presence of the Modify Support for SSCS Information parameter and the Preferred SSCS Information parameter: + +- If the Modify Support for SSCS Information parameter is not present, connection admission control and connection resource allocation shall reflect the Transfer Capability (TC). +- If the Modify Support for SSCS Information parameter is present, connection admission control and connection resource allocation shall reflect the Preferred Transfer Capability (PTC) if present; otherwise, the Transfer Capability (TC) shall be reflected. + +#### C.2.1.3 Actions at AAL type 2 nodes without served user interaction + +In addition to the specifications in 8.2, the following applies: + +Upon receiving notification from an incoming protocol entity instance requesting a new connection and the Transfer Capability parameter is not conveyed by the incoming protocol entity instance, + +- the nodal function prepares a Transfer Capability parameter whose connection resource requirements correspond to those of the SSCS Information parameter; and +- if a Preferred SSCS Information parameter is also conveyed by the incoming protocol entity instance, the nodal function prepares a Preferred Transfer Capability parameter whose connection resource requirements correspond to those of the Preferred SSCS Information parameter. The Preferred Transfer Capability parameter must refer to the same AAL type 2 transfer capability as the Transfer Capability parameter. + +NOTE 1 – For example, if the Transfer Capability parameter indicates a Variable Bandwidth Stringent Transfer Capability, the Preferred Transfer Capability parameter, if present, may only indicate a Variable Bandwidth Stringent Transfer Capability. + +These parameters are treated as if they would have been conveyed by the incoming protocol entity instance. + +If a Preferred Transfer Capability parameter is conveyed by the incoming protocol entity instance but not a Preferred SSCS Information parameter, the Preferred Transfer Capability parameter is discarded; the treatment of the parameters is as if the Preferred Transfer Capability parameter would not have been conveyed by the incoming protocol entity instance. + +Depending on the presence of Preferred Transfer Capability parameter, the following applies: + +- If the Preferred Transfer Capability parameter is not present, connection admission control and connection resource allocation are performed as defined in 8.2. +- If the Preferred Transfer Capability parameter is present, the connection admission control and connection resource allocation shall be based on the most demanding of the Preferred Transfer Capability and the Transfer Capability. + +NOTE 2 – The concept of "demanding" depends on the Connection Admission Control algorithm and connection resource allocation mechanisms in use which are outside the scope of this Recommendation. + +If AAL type 2 node receives a notification that the succeeding node did not recognize the Path Type parameter, the AAL type 2 node allows the connection to be established (QoS requirements are met by the network default stringent QoS class), or releases the connection with the cause "Resource unavailable, unspecified" (QoS requirements are not met by network default stringent QoS class). + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, the following applies depending on the presence of the Modify Support for SSCS Information parameter and the Preferred SSCS Information parameter: + +- If the Modify Support for SSCS Information parameter is not present, connection admission control and connection resource allocation shall reflect the Transfer Capability (TC). +- If the Modify Support for SSCS Information parameter is present, connection admission control and connection resource allocation shall reflect the Preferred Transfer Capability (PTC) if present, otherwise the Transfer Capability (TC) shall be reflected. + +#### **C.2.1.4 Actions at the destination AAL type 2 service endpoint** + +In addition to the specifications in 8.2, the following applies: + +Upon receiving notification from an incoming protocol entity instance requesting a new connection and the Transfer Capability parameter is not conveyed by the incoming protocol entity instance, + +- the nodal function prepares a Transfer Capability parameter whose connection resource requirements correspond to those of the SSCS Information parameter; and +- if a Preferred SSCS Information parameter is also conveyed by the incoming protocol entity instance, the nodal function prepares a Preferred Transfer Capability parameter whose connection resource requirements correspond to those of the Preferred SSCS Information parameter. The Preferred Transfer Capability parameter must refer to the same AAL type 2 transfer capability as the Transfer Capability parameter. + +NOTE – For example, if the Transfer Capability parameter indicates a Variable Bandwidth Stringent Transfer Capability, the Preferred Transfer Capability parameter, if present, may only indicate a Variable Bandwidth Stringent Transfer Capability. + +These parameters are treated as if they would have been conveyed by the incoming protocol entity instance. + +If a Preferred Transfer Capability parameter is conveyed by the incoming protocol entity instance but not a Preferred SSCS Information parameter, the Preferred Transfer Capability parameter is discarded; subsequent treatment of the parameters is as if the Preferred Transfer Capability parameter would not have been conveyed by the incoming protocol entity instance. + +Depending on the presence of Preferred Transfer Capability parameter, the following applies: + +- If the Preferred Transfer Capability parameter is not present, AAL type 2 connection resources (internal and on the incoming AAL type 2 path) indicated by the Transfer Capability (TC) parameter are allocated as specified in 8.2. +- If the Preferred Transfer Capability parameter is present, AAL type 2 connection resources (internal and on the incoming AAL type 2 path) indicated by the Preferred Transfer Capability (PTC) parameter are allocated. + +If a Transfer Capability Support parameter was received from the incoming protocol instance, the parameter shall be passed to the incoming protocol entity instance when the nodal function acknowledges the successful AAL type 2 connection establishment. + +If a Modify Support for SSCS Information parameter was received from the incoming protocol instance, the parameter shall be passed to the incoming protocol entity instance when the nodal function acknowledges the successful AAL type 2 connection establishment. + +### **C.2.2 Connection Resource Modification** + +#### **C.2.2.1 Introduction** + +If, during connection establishment, a Transfer Capability Support parameter was received by the destination AAL type 2 service endpoint and sent back to the originating AAL type 2 service endpoint, connection resource modification as specified in 8.2 applies. + +If, during connection establishment, a Transfer Capability Support parameter was not received but a Modify Support for SSCS Information parameter was received by an AAL type 2 service endpoint, connection resource modification follows the specifications in this subclause. + +If, during connection establishment, neither a Transfer Capability Support parameter nor a Modify Support for SSCS Information parameter was received by an AAL type 2 service endpoint, no connection resource modification is possible. + +NOTE – From the point of view of this Recommendation, it is regarded to be within the responsibility of the AAL type 2 served user to ensure consistency between Transfer Capability and SSCS Information parameters. + +#### **C.2.2.2 Actions at the AAL type 2 service endpoint originating the modification** + +In addition to the specifications in 8.2, the following applies: + +The AAL type 2 served user shall include a SSCS Information parameter (whose connection resource requirements correspond to those of the Transfer Capability parameter) in the MODIFY.request primitive. + +#### **C.2.2.3 Actions at AAL type 2 nodes without served user interaction** + +Upon receiving notification from a protocol entity instance requesting a connection modification and the Transfer Capability parameter is not conveyed by the protocol entity instance, the nodal function prepares a Transfer Capability parameter corresponding to the SSCS Information parameter. This parameter is treated as if it would have been conveyed by the protocol entity instance. + +#### **C.2.2.4 Actions at the AAL type 2 service endpoint receiving the modification** + +Upon receiving notification from a protocol entity instance requesting a connection modification and the Transfer Capability parameter is not conveyed by the protocol entity instance, the nodal function prepares a Transfer Capability parameter corresponding to the SSCS Information parameter. This parameter is treated as if it would have been conveyed by the protocol entity instance. + +## **C.3 Service Specific Information indicated with SSCS information parameters** + +This clause only applies to the signalling for the service specific convergence sublayer. + +NOTE – From the point of view of this Recommendation, it is regarded to be within the responsibility of the AAL type 2 served user to ensure consistency between the resource requirements of the Transfer Capability and SSCS Information parameters. + +### **C.3.1 Connection establishment** + +#### **C.3.1.1 Introduction** + +NOTE 1 – In order to ensure interworking the following three cases are considered: + +- a) If no Service Specific Information modifications are required for the AAL type 2 connection, the originating AAL type 2 served user may include an SSCS Information parameter in the ESTABLISH.request primitive. + +b) If Service Specific Information modifications are required for the AAL type 2 connection and interworking to CS-1 nodes is not required, the originating AAL type 2 served user may include an SSCS Information parameter and a Modify Support for SSCS Information parameter in the ESTABLISH.request primitive. + +c) If Service Specific Information modifications are required for the AAL type 2 connection and interworking to CS-1 nodes may be required, the originating AAL type 2 served user may additionally include the following parameters in the ESTABLISH.request primitive: + +- the SSCS Information parameter; +- the Preferred SSCS Information parameter; and +- the Modify Support for SSCS Information. + +Interworking with CS-2 and CS-1 nodes is designed such that: + +- If the Modify Support for SSCS Information parameter is received by the destination AAL type 2 service endpoint and this endpoint is a CS-2 node, the Service Specific Information for the AAL type 2 connection is based on the Preferred SSCS Information (if present) and the Service Specific Information is modifiable. +- Otherwise, the Service Specific Information for the AAL type 2 connection is based on the SSCS Information and the Service Specific Information is not modifiable. + +NOTE 2 – If the destination AAL type 2 service endpoint is a CS-1 node, the Service Specific Information (Audio Extended) and Service Specific Information (Multirate Extended) are unknown to the AAL type 2 service endpoint. + +- In all cases, the originating AAL type 2 served user includes a Transfer Capability Support parameter in the ESTABLISH.request primitive as well. If this parameter is received by a destination CS-3 service endpoint, it is sent back towards the originating AAL type 2 service endpoint. The complete AAL type 2 connection passes through CS-3 nodes only and the originating and the destination AAL type 2 served users know that the full functionality of this Recommendation is available. + +#### C.3.1.2 Actions at the originating AAL type 2 service endpoint + +In addition to the specifications in 8.2, the following applies: + +When the nodal function receives an ESTABLISH.request primitive from the AAL type 2 served user, the following restrictions on the optionality of the parameters of the primitive apply: + +- The Transfer Capability Support parameter shall be present; +- The SSCS Information parameter shall be present; +- The Modify Support for SSCS Information parameter may be present; +- The Preferred SSCS Information parameter shall only be present if the Modify Support for SSCS Information parameter is present; +- If a Preferred SSCS Information parameter is specified, it has to refer to the same SSCS Information type as the SSCS Information parameter. + +NOTE – For example, if the SSCS Information parameter indicates an Audio SSCS Information, the Preferred SSCS Information parameter, if present, may only indicate an Audio SSCS Information. + +After receiving an indication of the successful AAL type 2 connection setup from the outgoing protocol entity instance, the following applies depending on the presence of the Modify Support for SSCS Information parameter and the Preferred SSCS Information parameter: + +- If the Modify Support for SSCS Information parameter is not present, the Service Specific Information used for the connection is based on the SSCS Information parameter (SSCS) in the ESTABLISH.request primitive. + +- If the Modify Support for SSCS Information parameter is present, the Service Specific Information used for the connection is based on the Preferred SSCS Information parameter (PSSCS) in the ESTABLISH.request primitive if present; otherwise, the SSCS Information parameter (SSCS) shall be reflected. + +#### **C.3.1.3 Actions at AAL type 2 nodes without served user interaction** + +NOTE – No changes to the procedures in § 8.2 are required. + +#### **C.3.1.4 Actions at the destination AAL type 2 service endpoint** + +In addition to the specifications in 8.2, the following applies: + +The Service Specific Information used for the connection depends on the presence of the Preferred SSCS Information parameter and the Preferred SSCS Information parameter in the indication from the incoming protocol entity instance as follows: + +- If the Preferred SSCS Information parameter is not present, the Service Specific Information used for the connection is based on the SSCS Information parameter indicated by the incoming protocol entity. +- If the Preferred SSCS Information parameter is present, the Service Specific Information used for the connection is based on the Preferred SSCS Information parameter indicated by the incoming protocol entity if present; otherwise, the SSCS Information parameter (SSCS) shall be reflected. + +If a Modify Support for SSCS Information parameter was received from the incoming protocol instance, the parameter shall be passed to the incoming protocol entity instance when the nodal function acknowledges the successful AAL type 2 connection establishment. + +### **C.3.2 Service specific information modification** + +If, during connection establishment, a Transfer Capability Support parameter was received by the destination AAL type 2 service endpoint and sent back to the originating AAL type 2 service endpoint, Service Specific Information modification as specified in 8.2 applies. + +If, during connection establishment, a Transfer Capability Support parameter was not received but a Modify Support for SSCS Information parameter was received by an AAL type 2 service endpoint, Service Specific Information modification also follows the specifications in 8.2. + +If, during connection establishment, neither a Transfer Capability Support parameter nor a Modify Support for SSCS Information parameter was received by an AAL type 2 service endpoint, no Service Specific Information modification is possible. + +NOTE – From the point of view of this Recommendation, it is regarded to be within the responsibility of the AAL type 2 served user to ensure consistency between Transfer Capability and SSCS Information parameters. + +# **Annex D** + +# **SDL Definition of the AAL type 2 Signalling Protocol** + +The SDL definitions may contain more detail than the prose definition in clause 8. Nevertheless, should there exist any technical difference between this annex and clause 8, then the definitions in clause 8 take precedence. + +## Appendix I + +### Example message sequences + +### I.1 Successful establishment and release + +Figure I.1 illustrates the message sequences for a successful AAL type 2 connection establishment and its release. + +![Sequence diagram showing AAL type 2 connection establishment and release between two service endpoints and a switch.](bc90605aeb4173d4b4aa6eb475037a0c_img.jpg) + +The diagram illustrates the message sequences for a successful AAL type 2 connection establishment and release between two AAL type 2 service endpoints and an AAL type 2 switch. + +**Establishment Phase:** + +- The left AAL type 2 service endpoint sends an **ERQ(DSAID = 0, OSAID = r, ...)** message to the switch. +- The switch responds with **ECF(DSAID = r, OSAID = u, ...)**. +- The left endpoint then sends a **Memorize DSAID = u** message. +- The switch allocates an OSAID **s** and sends an **ERQ(DSAID = 0, OSAID = s, ...)** message to the right endpoint. +- The right endpoint responds with **ECF(DSAID = s, OSAID = t, ...)**. +- The right endpoint then sends a **Memorize DSAID = s** message. +- A horizontal grey bar indicates that the **AAL type 2 connection is established**. + +**Release Phase:** + +- The left endpoint sends a **REL(DSAID = u, ...)** message to the switch. +- The switch responds with **RLC(DSAID = r, ...)**. +- The left endpoint then sends an **Allocate OSAID = r** message. +- The switch releases the OSAID **s** and sends a **REL(DSAID = t, ...)** message to the right endpoint. +- The right endpoint responds with **RLC(DSAID = s, ...)**. +- The right endpoint then sends a **Release OSAID = t** message. + +Q.2630.3\_FI-1 + +Sequence diagram showing AAL type 2 connection establishment and release between two service endpoints and a switch. + +**Figure I.1/Q.2630.3 – Example of successful AAL type 2 connection establishment and release message sequences** + +Signalling Association Identifiers (SAID) are treated in the following way: + +- 1) Whenever a new link associated signalling relationship is created, a new protocol entity instance is created and an OSAID is allocated to it; this ID is then transported in the first message in the OSAID parameter. The DSAID in this message contains the value "unknown", i.e., all octets are set to "0". (In the figures, this is indicated by "DSAID = 0".) +- 2) Upon receipt of a message that has a DSAID field set to "unknown", a new protocol entity instance is created and an OSAID is allocated to it. +- 3) In the first message returned to the originator of the association, the OSAID of the sending protocol entity instance is transported in the OSAID parameter. The DSAID field carries the previously received OSAID of the originator of the association. +- 4) In all subsequent messages, the DSAID field carries the previously received OSAID of the destination entity. + +- 5) If the first message returned to the originator of the association is also the last one for this link associated signalling relationship (see Figure I.2 or I.3), no OSAID parameter is carried in the message. The DSAID field carries the previously received OSAID of the originator of the association. + +### I.2 Unsuccessful establishment + +Figure I.2 illustrates the message sequences for an unsuccessful AAL type 2 connection establishment. + +![Sequence diagram for an unsuccessful AAL type 2 connection establishment between two service endpoints and a switch.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +The diagram illustrates the message sequence for an unsuccessful AAL type 2 connection establishment between two AAL type 2 service endpoints and an AAL type 2 switch. + +- Left Service Endpoint:** Initiates the process with "Allocate OSAID = r". It sends an **ERQ(DSAID = 0, OSAID = r, ...)** message to the switch. +- Switch:** Responds with "Allocate OSAID = u" and "Memorize DSAID = r". It then sends an **ERQ(DSAID = 0, OSAID = s, ...)** message to the right service endpoint. +- Right Service Endpoint:** Responds with "Allocate OSAID = t", "Memorize DSAID = s", and "Release OSAID = t". It sends an **RLC(DSAID = s, ...)** message back to the switch. +- Switch:** Receives the RLC message and sends a "Release OSAID = u" message back to the left service endpoint. +- Left Service Endpoint:** Receives the RLC message and sends a "Release OSAID = r" message. + +The diagram is labeled Q.2630.3\_FI-2. + +Sequence diagram for an unsuccessful AAL type 2 connection establishment between two service endpoints and a switch. + +**Figure I.2/Q.2630.3 – Example of a message sequence for an unsuccessful AAL type 2 connection establishment** + +### I.3 Management message sequences + +Figure I.3 illustrates the message sequences for a management operation. Management operations include: + +- reset procedures; +- blocking procedures; +- unblocking procedures. + +![Sequence diagram for a management operation between two AAL type 2 nodes.](901343511e3efc3f994eaffe6fc393ca_img.jpg) + +The diagram illustrates the message sequence for a management operation between two AAL type 2 nodes. + +- Left Node:** Initiates the process with "Allocate OSAID = s". It sends a **RES(DSAID = 0, OSAID = s, ...)** message to the right node. +- Right Node:** Responds with "Memorize DSAID = s" and sends an **RSC(DSAID = s, ...)** message back to the left node. +- Left Node:** Receives the RSC message and sends a "Release OSAID = s" message. + +The diagram is labeled Q.2630.3\_FI-3. + +Sequence diagram for a management operation between two AAL type 2 nodes. + +**Figure I.3/Q.2630.3 – Example of a message sequence for a management operation** + +NOTE – Message sequences for blocking or unblocking are the same as for reset except that instead of "RES" and "RSC": + +- for blocking, the messages "BLO" and "BLC" are used respectively; and +- for unblocking, the messages "UBL" and "UBC" are used respectively. + +### I.4 Release crossover/release collision + +Figure I.4 illustrates the message sequences for release collision on an AAL type 2 connection release. + +![Sequence diagram showing a release collision on an AAL type 2 connection between two nodes.](f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg) + +The diagram illustrates a release collision on an AAL type 2 connection between two AAL type 2 nodes. The sequence of events is as follows: + +- Node 1 (Left):** Initiates the release with "Allocate OSAMD = r", "Memorize", and "DSAID = u". +- Node 2 (Right):** Initiates the release with "Allocate OSAMD = u", "Memorize", and "DSAID = r". +- Connection Establishment:** A horizontal bar indicates that the "AAL type 2 connection is established". +- Release Messages:** + - Node 1 sends $REL(DSAID = u, \dots)$ to Node 2. + - Node 2 sends $REL(DSAID = r, \dots)$ to Node 1. + - Node 1 receives $RLC(DSAID = u, \dots)$ from Node 2. + - Node 2 receives $RLC(DSAID = r, \dots)$ from Node 1. +- Release Completion:** + - Node 1 completes the release with "Release OSAMD = r". + - Node 2 completes the release with "Release OSAMD = u". + +The diagram is labeled "Q.2630.3\_FI-4" at the bottom right. + +Sequence diagram showing a release collision on an AAL type 2 connection between two nodes. + +Figure I.4/Q.2630.3 – Example of a message sequence for a release collision on an AAL type 2 connection + +### I.5 Resource contention + +Figure I.5 illustrates the message sequences for a resource contention on an AAL type 2 connection establishment. + +![Sequence diagram showing resource contention between two AAL type 2 connections (A-B and A-C) at switch B. The diagram shows Allocate, ERQ, RLC, and Release messages with specific OSAID and DSAID values.](3c0be9369e1f99f7f820fda3f9d676e6_img.jpg) + +The diagram illustrates the message sequences for a resource contention on an AAL type 2 connection establishment between AAL type 2 node A and AAL type 2 switch B, and between AAL type 2 node C and AAL type 2 switch B. + +**Sequence of events:** + +- Node A to Switch B:** + - Allocate OSAID = r + - ERQ(DSAID = 0, OSAID = r, ...) + - Allocate OSAID = u, Memorize DSAID = r + - Allocate OSAID = w, Memorize DSAID = v + - Release OSAID = w + - RLC(DSAID = r, ...) + - Release OSAID = r +- Switch B to Node C:** + - Allocate OSAID = s + - ERQ(DSAID = 0, OSAID = s, CID = n, ...) + - Allocate OSAID = v + - Allocate OSAID = t, Memorize DSAID = s + - Release OSAID = t + - Release OSAID = v +- Switch B internal actions:** + - RLC(DSAID = v, ...) + - RLC(DSAID = s, ...) + - Release OSAID = s +- Node A internal actions:** + - Release OSAID = u + +Q.2630.3\_FI-5 + +Sequence diagram showing resource contention between two AAL type 2 connections (A-B and A-C) at switch B. The diagram shows Allocate, ERQ, RLC, and Release messages with specific OSAID and DSAID values. + +**Figure I.5/Q.2630.3 – Example of a message sequence for a resource contention on two AAL type 2 connections** + +NOTE – The resource contention is shown for a CID value "n" that is attempting to be assigned to two new AAL type 2 connections. + +### I.6 Successful modification + +Figure I.6 illustrates the message sequences for a successful resource modification of an established AAL type 2 connection. + +![Sequence diagram for a successful resource modification of an established AAL type 2 connection. The diagram shows three lifelines: AAL type 2 service endpoint (left), AAL type 2 switch (middle), and AAL type 2 service endpoint (right). The sequence starts with allocation and memorization of OSAs and DSAs. A grey bar indicates the connection is established. The left endpoint sends a MOD(DSAID = u,...) message to the switch. The switch then sends a MOD(DSAID = t,...) message to the right endpoint. The right endpoint responds with a MOA(DSAID = s,...) message to the switch. Finally, the switch sends a MOA(DSAID = r,...) message back to the left endpoint. The diagram is labeled Q.2630.3_FI-6.](4c63a0e17b54c7e61d512c276932114c_img.jpg) + +``` + +sequenceDiagram + participant EP1 as AAL type 2 +service endpoint + participant SW as AAL type 2 +switch + participant EP2 as AAL type 2 +service endpoint + + Note over EP1: Allocate +OSAID = r +Memorize +DSAID = u + Note over SW: Allocate OSAID = u, Memorize DSAID = r +Allocate OSAID = s, Memorize DSAID = t + Note over EP2: Allocate +OSAID = t +Memorize +DSAID = s + + rect rgb(200, 200, 200) + Note over EP1, EP2: AAL type 2 connection is established + end + + EP1->>SW: MOD(DSAID = u,...) + SW->>EP2: MOD(DSAID = t,...) + EP2->>SW: MOA(DSAID = s,...) + SW->>EP1: MOA(DSAID = r,...) + +``` + +Q.2630.3\_FI-6 + +Sequence diagram for a successful resource modification of an established AAL type 2 connection. The diagram shows three lifelines: AAL type 2 service endpoint (left), AAL type 2 switch (middle), and AAL type 2 service endpoint (right). The sequence starts with allocation and memorization of OSAs and DSAs. A grey bar indicates the connection is established. The left endpoint sends a MOD(DSAID = u,...) message to the switch. The switch then sends a MOD(DSAID = t,...) message to the right endpoint. The right endpoint responds with a MOA(DSAID = s,...) message to the switch. Finally, the switch sends a MOA(DSAID = r,...) message back to the left endpoint. The diagram is labeled Q.2630.3\_FI-6. + +**Figure I.6/Q.2630.3 – Example of a message sequence for a successful resource modification of an established AAL type 2 connection** + +### I.7 Unsuccessful modification + +Figure I.7 illustrates the message sequences for an unsuccessful resource modification of an established AAL type 2 connection. + +![Sequence diagram for an unsuccessful resource modification of an established AAL type 2 connection. The diagram shows three lifelines: AAL type 2 service endpoint (left), AAL type 2 switch (middle), and AAL type 2 service endpoint (right). The sequence starts with allocation and memorization of OSAs and DSAs. A grey bar indicates the connection is established. The left endpoint sends a MOD(DSAID = u,...) message to the switch. The switch responds with a MOR(DSAID = r,...) message to the left endpoint. The right endpoint remains idle. The diagram is labeled Q.2630.3_FI-7.](5efe6377e22b9ab76a19a70da29976b9_img.jpg) + +``` + +sequenceDiagram + participant EP1 as AAL type 2 +service endpoint + participant SW as AAL type 2 +switch + participant EP2 as AAL type 2 +service endpoint + + Note over EP1: Allocate +OSAID = r +Memorize +DSAID = u + Note over SW: Allocate OSAID = u, Memorize DSAID = r +Allocate OSAID = s, Memorize DSAID = t + Note over EP2: Allocate +OSAID = t +Memorize +DSAID = s + + rect rgb(200, 200, 200) + Note over EP1, EP2: AAL type 2 connection is established + end + + EP1->>SW: MOD(DSAID = u,...) + SW->>EP1: MOR(DSAID = r,...) + +``` + +Q.2630.3\_FI-7 + +Sequence diagram for an unsuccessful resource modification of an established AAL type 2 connection. The diagram shows three lifelines: AAL type 2 service endpoint (left), AAL type 2 switch (middle), and AAL type 2 service endpoint (right). The sequence starts with allocation and memorization of OSAs and DSAs. A grey bar indicates the connection is established. The left endpoint sends a MOD(DSAID = u,...) message to the switch. The switch responds with a MOR(DSAID = r,...) message to the left endpoint. The right endpoint remains idle. The diagram is labeled Q.2630.3\_FI-7. + +**Figure I.7/Q.2630.3 – Example of a message sequence for an unsuccessful resource modification of an established AAL type 2 connection** + +### **I.8 Modification Collision** + +Figure I.8 illustrates the message sequences for a resource modification collision of an established AAL type 2 connection. + +![Sequence diagram illustrating a resource modification collision for an established AAL type 2 connection between two nodes.](426a0ab9454f31706038a0ac0bc37b9c_img.jpg) + +``` + + sequenceDiagram + participant NodeA as AAL type 2 node + participant NodeB as AAL type 2 node + Note over NodeA: Allocate OSAID = r +Memorize DSAID = u + Note over NodeB: Allocate OSAID = u +Memorize DSAID = r + rect rgb(200, 200, 200) + Note over NodeA, NodeB: AAL type 2 connection is established + end + NodeA->>NodeB: MOD(DSAID = u, ...) + NodeB->>NodeA: MOD(DSAID = r, ...) + NodeA->>NodeB: MOR(DSAID = u, ...) + NodeB->>NodeA: MOR(DSAID = r, ...) + +``` + +The diagram shows two AAL type 2 nodes. At the top, each node performs an 'Allocate' operation with $OSAID = r$ (or $u$ ) and 'Memorize' with $DSAID = u$ (or $r$ ). A grey bar labeled 'AAL type 2 connection is established' spans the timeline. Below this, four messages are exchanged: +1. From the left node to the right node: $MOD(DSAID = u, …)$ +2. From the right node to the left node: $MOD(DSAID = r, …)$ +3. From the left node to the right node: $MOR(DSAID = u, …)$ +4. From the right node to the left node: $MOR(DSAID = r, …)$ +The diagram is labeled 'Q.2630.3\_FI-8' at the bottom right. + +Sequence diagram illustrating a resource modification collision for an established AAL type 2 connection between two nodes. + +**Figure I.8/Q.2630.3 – Example of a message sequence for a resource modification collision of an established AAL type 2 connection** + +## Appendix II + +## Conversion of CS-1 or CS-2 (Preferred) Link Characteristics to (Preferred) Transfer Capability parameters + +The purpose of this appendix is to give guidance to implementers how to capture the problem of interworking of CS-1 and CS-2 Link Characteristics parameters into CS-3 Transfer Capability parameters. + +NOTE – In this Appendix the terms "Transfer Capability" and "Preferred Transfer Capability" and the abbreviations "TC" and "PTC" do not distinguish between the different types of Transfer Capabilities, i.e., Fixed Bandwidth, Variable Bandwidth Stringent, Variable Bandwidth Tolerant. + +### **II.1 Guidelines and definitions** + +This appendix provides rules for conversions from LC-type to TC-type parameters. In some cases, explicit expressions are defined that allow computing the outgoing parameter values based on incoming parameter values. These expressions should be understood as formal in the sense that: + +- they do not request by themselves the existence of certain parameters neither incoming nor outgoing, +- they do not overrule constraints of any type that are defined within this protocol specification. + +For the purpose of this clause, the following shorthand notation shall be used (see Tables II.1 to II.4). + +**Table II.1/Q.2630.3 – 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 II.2/Q.2630.3 – TC parameter fields** + +| | +|---------------------------------------------------------------| +| U = Peak CPS bit rate in the forward direction | +| V = Sustainable CPS bit rate in the forward direction | +| W = Peak CPS bit rate in the backward direction | +| X = Sustainable CPS bit rate in the backward direction | +| Y = Maximum allowed CPS packet size in the forward direction | +| Z = Maximum allowed CPS packet size in the backward direction | +| STT = Source traffic type | + +**Table II.3/Q.2630.3 – 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 II.4/Q.2630.3 – PTC parameter fields** + +| | +|---------------------------------------------------------------| +| u = Peak CPS bit rate in the forward direction | +| v = Sustainable CPS bit rate in the forward direction | +| w = Peak CPS bit rate in the backward direction | +| x = Sustainable CPS bit rate in the backward direction | +| y = Maximum allowed CPS packet size in the forward direction | +| z = Maximum allowed CPS packet size in the backward direction | +| stt = Source traffic type | + +CPHL shall denote the length of the CPS packet header (see ITU-T Rec. I.363.2 [1]) in octet. + +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 octet. + +### II.2 Bit rates + +The conversion from LC-type to TC-type bit rates requires to estimate the rate that will be caused by the CPS packet header overhead of length CPHL. This estimate is given in Table II.5. The values are "normalized" to multiples of 64 bit/s. + +**Table II.5/Q.2630.3 – CPS packet header overhead rates** + +| Definition | Meaning | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| $HBA := [(CPHL*A) / (64*F)] * 64$ | Estimate of the CPHL bit rate for the Peak CPS bit rate in the forward direction for given LC | +| $HBa := [(CPHL*a) / (64*f)] * 64$ | Estimate of the CPHL bit rate for the Peak CPS bit rate in the forward direction for given PLC | +| $HBB := [(CPHL*B) / (64*F)] * 64$ | Estimate of the CPHL bit rate for the Sustainable CPS bit rate in the forward direction for given LC | +| $HBb := [(CPHL*b) / (64*f)] * 64$ | Estimate of the CPHL bit rate for the Sustainable CPS bit rate in the forward direction for given PLC | +| $HBC := [(CPHL*C) / (64*H)] * 64$ | Estimate of the CPHL bit rate for the Peak CPS bit rate in the backward direction for given LC | +| $HBc := [(CPHL*c) / (64*h)] * 64$ | Estimate of the CPHL bit rate for the Peak CPS bit rate in the backward direction for given PLC | +| $HBD := [(CPHL*D) / (64*H)] * 64$ | Estimate of the CPHL bit rate for the Sustainable CPS bit rate in the backward direction for given LC | +| $HBd := [(CPHL*d) / (64*h)] * 64$ | Estimate of the CPHL bit rate for the Sustainable CPS 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 protocol specification. | | + +Table II.6 defines the interworking of LC bit rates (AAL type 2) to TC CPS bit rates + +**Table II.6/Q.2630.3 – TC CPS bit rates determined from LC** + +| TC parameter field | Value | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| U | A + HBA | +| V | B + HBB | +| W | C + HBC | +| X | D + HBD | +| NOTE 1 – Whether or not a certain field is required is determined by the protocol specification.
NOTE 2 – Whether or not a certain value is meaningful and valid is determined by the protocol specification. | | + +Table II.7 defines the interworking of PLC bit rates (AAL type 2) to PTC CPS bit rates + +**Table II.7/Q.2630.3 – PTC bit rates determined from PLC** + +| PTC parameter field | Value | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| u | a + HBa | +| v | b + HBb | +| w | c + HBc | +| x | d + HBd | +| NOTE 1 – Whether or not a certain field is required is determined by the protocol specification.
NOTE 2 – Whether or not a certain value is meaningful and valid is determined by the protocol specification. | | + +### II.3 Maximum allowed packet sizes + +Table II.8 defines the derivation of TC and PTC maximum allowed packet sizes from LC and PLC CPS-SDU sizes. + +**Table II.8/Q.2630.3 – Determination of maximum allowed packet sizes** + +| TC/PTC SDU size subfields | Value | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Y | CPHL + E | +| Z | CPHL + G | +| y | CPHL + e | +| z | CPHL + g | +| NOTE 1 – Whether or not a certain field is required is determined by the protocol specification.
NOTE 2 – Whether or not a certain value is meaningful and valid is determined by the protocol specification. | | + +### II.4 Token bucket sizes + +The CS-3 node receiving LC without TC in an initial ERQ 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 – If modification is possible, an appropriate adjustment of the token bucket sizes controlled by the Served User may be initiated from a CS-3 service endpoint with a subsequent MOD message. + +Token bucket sizes shall not be affected by received MOD messages with LC but without TC parameter. + +### II.5 Determination of the TC class + +ITU-T Rec. I.378 [19] defines three AAL Type 2 transfer capability classes: Fixed Bandwidth, Variable Bandwidth Stringent, and Variable Bandwidth Tolerant Transfer Capability. + +A CS-3 node receiving LC without TC in an initial ERQ has to determine the AAL Type 2 Transfer Capability class to be used by CS-3 nodes. + +If all subsequent conditions: + +- C1) A = B +- C2) C = D +- C3) E = F +- C4) G = H +- C5) MSLC not set + +are satisfied, the Fixed Bandwidth Transfer Capability shall be selected. If at least one of the conditions C1), ... , C5) is not fulfilled, the Variable Bandwidth Stringent or Variable Bandwidth Tolerant Transfer Capability shall be applied. If not otherwise indicated by administrative settings in the CS-3 node (possibly in dependence from a received Path Type parameter), Variable Bandwidth Stringent Transfer Capability shall be selected. + +### II.6 Source traffic type + +A CS-3 node, which receives LC (and possibly PLC) without TC (and PTC) in an initial ERQ and which selects the Variable Bandwidth Stringent Transfer Capability, shall set the Source Traffic Type parameters in TC (and possibly PTC) as follows: + +STT = STT unknown + +stt = STT unknown + +NOTE 1 – If the received signalling information or network configuration knowledge indicate that other valid source traffic type values are more suitable, then the STT and stt parameters may be set to values other than "unknown". + +NOTE 2 – If modification is possible, an appropriate adjustment of the source traffic type controlled by the Served User may be initiated from a CS-3 service endpoint with a subsequent MOD message. + +Source traffic types shall not be affected by received MOD messages with LC but without TC parameter. + +## Appendix III + +## Interworking examples + +This appendix illustrates the mechanism for connection resource allocation in a network where the CS-1 and CS-2 nodes allocate connection resources based on link characteristics. The mechanisms where CS-1 and CS-2 nodes allocate connection resources based on SSCS information are similar. + +This appendix assumes the behaviour of CS-3 nodes according to Annex C. + +### III.1 Symbols and abbreviations + +The diagrams show the exchange of ERQ/ECF messages (originating at left) and the exchange of MOD/MOA messages (also originating at left). Only parameters relevant to connection resource reservation and allocation are shown. + +- a) The 1st column shows the name of the relevant parameters. + +On the Modify Request (MOD) message, LCold indicates the actually allocated resources in CS-2 and CS-1 nodes, LCnew the new LC that the modification attempts to allocate. Similarly, TCold indicates the actually allocated resources in CS-3 nodes, TCnew the new TC that the modification attempts to allocate. + +NOTE – The indications TC, PTC, LC, and PLC in the 1st column of the ECF messages or the indications TCold; TCnew; LCold; and LCnew in the 1st column of the MOA messages do not refer to parameters carried in the message but are used to indicate which parameter is used to make the actual resource allocation. + +- b) The 2nd column shows the name of the message. +c) The 3rd column indicates the parameters of the primitive from (↪) or to (↩) the originating served user. +d) The 4th to the 13th columns show the AAL type 2 nodes where in the top cell the capability set of the node is indicated. The indications in the other cells are explained below. +e) The 14th column indicates the parameters of the primitive to (↩) or from (↪) the destination served user. + +In columns 4 to 13, the indications in a row of a parameter or an actually allocated resource have the following meaning: + +- "-": Parameter not present or actual resource allocation not done with this parameter. +"—": Parameter passed because it is not relevant or due to the compatibility instructions. +"==": Parameter passed according to specifications in ITU-T Recs Q.2630.1 [15] or Q.2630.2 [16]. +"≡": Parameter passed according to instructions in 8.2. +"✓": Parameter processed. +"A": This parameter is used to perform the allocation of resources. +"R": These parameters are used to reserve resources according to the "most demanding" requirements. +"★": Parameter inserted by the AAL type 2 node. +"✗": Parameter discarded by the AAL type 2 node due to compatibility instructions. +"⊠": Parameter discarded by the AAL type 2 node due interworking specifications instructions (see Annex C). + +### III.2 Connection Establishment + +#### III.2.1 All CS-3 nodes + +This clause illustrates AAL type 2 connection establishment where the originating and the destination AAL type 2 service endpoints as well as all AAL type 2 switches reside in a part of the network consisting of CS-3. + +The parameters transported in the Establish Request (ERQ) and Establish Confirm (ECF) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.1. + +| | | CS3a | CS3b | CS3c | CS3d | CS3e | CS3f | CS3g | CS3h | CS3i | | +|-------------|---|------|------|------|------|------|------|------|------|------|---| +| LC
PLC | E | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ↗ | +| | R | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ↘ | +| TC
PTC | E | R | R | R | R | R | R | R | R | | ↗ | +| | R | R | R | R | R | R | R | R | R | A | ↘ | +| MSLC
TCS | E | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ↗ | +| | R | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ↘ | +|
| | | | | | | | | | | | +| LC
PLC | E | | | | | | | | | | | +| | R | | | | | | | | | | | +| TC
PTC | E | A | A | A | A | A | A | A | A | | | +| | R | | | | | | | | | | | +| MSLC
TCS | E | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | | +| | R | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | ≡ | | + +Figure III.1/Q.2630.3 – All CS-3 nodes in the AAL type 2 connection + +In the ESTABLISH.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; and +- the Modify Support for Link Characteristics. + +Nodes CS3a, CS3b, CS3c, CS3d, CS3e, CS3f, CS3g, and CS3h reserve connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +Node CS3i allocates connection resources reflecting the Preferred Transfer Capability (PTC) parameter; this decision is based on the presence of the Preferred Transfer Capability (PTC) parameter. The parameters Transfer Capability (TC), Preferred Transfer Capability (PTC), Link Characteristics (LC), Preferred Link Characteristics (PLC), Modify Support for Link Characteristics (MSLC), and Transfer Capability Support (TCS) are passed to the AAL type 2 served user, which interprets the last parameter to indicate that the AAL type 2 connection passes only through CS-3 nodes and that, therefore, the full functionality of this Recommendation is available. + +The parameters Modify Support for Link Characteristics (MSLC) and Transfer Capability Support (TCS) are inserted into the Establish Confirm (ECF) message. + +Nodes CS3h, CS3g, CS3f, CS3e, CS3d, CS3c, CS3b, and CS3a allocate connection resources reflecting the Preferred Transfer Capability (PTC) parameter that was passed previously in the Establish Request (ERQ) message or received from the AAL type 2 served user; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Node CS3a includes the Modify Support for Link Characteristics (MSLC) and Transfer Capability Support (TCS) parameters in the ESTABLISH.confirm primitive to the AAL type 2 served user, which interprets the latter parameter to indicate that the AAL type 2 connection passes only through CS-3 nodes and that, therefore, the full functionality of this Recommendation is available. + +#### III.2.2 From CS-3 via CS-2/CS-1 nodes to CS-3 + +This clause illustrates AAL type 2 connection establishment where the originating and the destination AAL type 2 service endpoints reside in a part of the network consisting of CS-3 nodes and where the AAL type 2 connection passes through a part of the network consisting of CS-2 and/or CS-1 nodes. + +##### III.2.2.1 No CS-1 nodes in the AAL type 2 connection + +The parameters transported in the Establish Request (ERQ) and Establish Confirm (ECF) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.2. + +| | | CS3a | CS3b | CS2c | CS2d | CS2e | CS2f | CS2g | CS3h | CS3i | | +|-------------|-----|------|------|------|------|------|------|------|------|------|---| +| LC
PLC | ERQ | ≡ | ≡ | R | R | R | R | R | ≡ | ≡ | ↗ | +| | ECF | ≡ | ≡ | R | R | R | R | R | ≡ | ≡ | ↗ | +| | | | | | | | | | | | | +| TC
PTC | ERQ | R | R | — | — | — | — | — | R | A | ↗ | +| | ECF | R | R | — | — | — | — | — | R | A | ↗ | +| | | | | | | | | | | | | +| MSLC
TCS | ERQ | ≡ | ≡ | == | == | == | == | == | ≡ | ≡ | ↗ | +| | ECF | ≡ | ≡ | × | | | | | | | | +| | | | | | | | | | | | | +| LC
PLC | ERQ | | | A | A | A | A | A | | | | +| | ECF | | | | | | | | | | | +| | | | | | | | | | | | | +| TC
PTC | ERQ | A | A | | | | | | A | | | +| | ECF | | | | | | | | | | | +| | | | | | | | | | | | | +| MSLC
TCS | ERQ | ≡ | ≡ | == | == | == | == | == | ≡ | ★ | | +| | ECF | | | | | | | | | | | +| | | | | | | | | | | | | + +Figure III.2/Q.2630.3 – No CS-1 nodes in the AAL type 2 connection in the "From CS-3 via CS-2/CS-1 nodes to CS-3" scenario + +In the ESTABLISH.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; and +- the Modify Support for Link Characteristics. + +Nodes CS3a and CS3b reserve connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +At node CS2c, the Transfer Capability Support (TCS) parameter is discarded (compatibility instructions); the AAL type 2 served users at both AAL type 2 service endpoints realize that the connection does not pass through CS-3 nodes entirely. + +Nodes CS2c, CS2d, CS2e, CS2f, and CS2g reserve connection resources reflecting the more "demanding" of the parameters Link Characteristics (LC) and Preferred Link Characteristics (PLC). + +Node CS3h reserves connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +Node CS3i allocates connection resources reflecting the Preferred Transfer Capability (PTC) parameter; this decision is based on the presence of the Preferred Transfer Capability (PTC) parameter. The parameters Transfer Capability (TC), Preferred Transfer Capability (PTC), Link Characteristics (LC), Preferred Link Characteristics (PLC), and Modify Support for Link Characteristics (MSLC) are passed to the AAL type 2 served user. The absence of the Transfer Capability Support (TCS) parameter indicates that the AAL type 2 connection does not pass through CS-3 nodes entirely. The Modify Support for Link Characteristics (MSLC) parameter is inserted into the Establish Confirm (ECF) message. + +Node CS3h allocates connection resources reflecting the Preferred Transfer Capability (PTC) parameter that was previously passed in the Establish Request (ERQ) message; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Nodes CS2g, CS2f, CS2e, CS2d, and CS2c allocate connection resources reflecting the Preferred Link Characteristics (PLC) parameter that was previously passed in the Establish Request (ERQ) message; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Nodes CS3b and CS3a allocate connection resources reflecting the Preferred Transfer Capability (PTC) that was previously passed in the Establish Request (ERQ) message or received from the AAL type 2 served user; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Node CS3a includes the Modify Support for Link Characteristics (MSLC) parameter in the ESTABLISH.confirm primitive to the AAL type 2 served user. + +##### **III.2.2.2 At least one CS-1 node in the AAL type 2 connection** + +The parameters transported in the Establish Request (ERQ) and Establish Confirm (ECF) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.3. + +| | | CS3a | CS3b | CS2c | CS2d | CS1e | CS2f | CS2g | CS3h | CS3i | | +|-------------|---|------|------|------|------|------|------|------|------|------|---| +| LC
PLC | E | ≡ | ≡ | R | R | A | A | A | ≡ | ≡ | ↗ | +| | R | ≡ | ≡ | R | R | ✗ | | | | | | +| | Q | | | | | | | | | | | +| TC
PTC | E | R | R | — | — | — | — | — | A | A | ↗ | +| | R | R | R | — | — | — | — | — | ⊠ | | | +| | Q | | | | | | | | | | | +| MSLC
TCS | E | ≡ | ≡ | == | == | ✗ | | | | | | +| | R | ≡ | ≡ | ✗ | | | | | | | | +| | Q | | | | | | | | | | | +| LC
PLC | E | | | A | A | | | | | | | +| | C | | | | | | | | | | | +| | F | | | | | | | | | | | +| TC
PTC | E | A | A | | | | | | | | | +| | C | | | | | | | | | | | +| | F | | | | | | | | | | | +| MSLC
TCS | E | | | | | | | | | | | +| | C | | | | | | | | | | | +| | F | | | | | | | | | | | + +**Figure III.3/Q.2630.3 – At least one CS-1 node in the AAL type 2 connection in the "From CS-3 via CS-2/CS-1 nodes to CS-3" scenario** + +In the ESTABLISH.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; and +- the Modify Support for Link Characteristics. + +Nodes CS3a and CS3b reserve connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +At node CS2c, the Transfer Capability Support (TCS) parameter is discarded (compatibility instructions); the AAL type 2 served users at both AAL type 2 service endpoints realize that the connection does not pass through CS-3 nodes entirely. + +Nodes CS2c and CS2d reserve connection resources reflecting the more "demanding" of the parameters Link Characteristics (LC) and Preferred Link Characteristics (PLC). + +At node CS1e, the parameters Preferred Link Characteristics (PLC) and Modify Support for Link Characteristics (MSLC) are discarded (compatibility instructions). Connection resources reflecting the Link Characteristics (LC) are allocated. + +Nodes CS2f and CS2g allocate connection resources reflecting the Link Characteristics (LC); the Preferred Link Characteristics (PLC) parameter is no longer present in the Establish Request (ERQ) message. + +At node CS3h it is detected that although no Preferred Link Characteristics (PLC) parameter is present, a Preferred Transfer Capability (PTC) parameter is; this parameter is discarded due to interworking definitions (see Annex C) before the Establish Request (ERQ) message is interpreted by the nodal function. Connection resources reflecting the Transfer Capability (TC) are allocated. + +At node CS3i, connection resources reflecting the Transfer Capability (TC) are allocated. The parameters Transfer Capability (TC) and Link Characteristics (LC) are passed to the AAL type 2 served user. The absence of the Transfer Capability Support (TCS) parameter indicates that the AAL type 2 connection does not pass through CS-3 nodes entirely. No parameters are inserted into the Establish Confirm (ECF) message. + +At nodes CS3h, CS2g, CS2f, and CS1e, no action except passing the Establish Confirm (ECF) message is performed. + +Nodes CS2d and CS2c allocate connection resources reflecting the Link Characteristics (LC) that was previously passed in the Establish Request (ERQ) message; this decision is based on the absence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Nodes CS3b and CS3a allocate connection resources reflecting the Transfer Capability (TC) that was previously passed in the Establish Request (ERQ) message or received from the AAL type 2 served user; this decision is based on the absence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Node CS3a includes no parameters in the ESTABLISH.confirm primitive to the AAL type 2 served user. + +#### III.2.3 From a CS-3 service endpoint to a CS-2/CS-1 service endpoint + +This clause illustrates AAL type 2 connection establishment where the originating AAL type 2 service endpoint resides in a part of the network consisting of CS-3 nodes and where the destination AAL type 2 service endpoint resides in a part of the network consisting of CS-2 and/or CS-1 nodes. + +##### III.2.3.1 No CS-1 nodes in the AAL type 2 connection + +The parameters transported in the Establish Request (ERQ) and Establish Confirm (ECF) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.4. + +| | | CS3a | CS3b | CS3c | CS3d | CS2e | CS2f | CS2g | CS2h | CS2i | | +|-------------|-----|------|------|------|------|------|------|------|------|------|---| +| LC
PLC | ERQ | ≡ | ≡ | ≡ | ≡ | R | R | R | R | | ↗ | +| | ECF | ≡ | ≡ | ≡ | ≡ | R | R | R | R | A | ↗ | +| TC
PTC | ERQ | R | R | R | R | — | — | — | — | ✗ | | +| | ECF | R | R | R | R | — | — | — | — | ✗ | | +| MSLC
TCS | ERQ | ≡ | ≡ | ≡ | ≡ | == | == | == | == | == | ↗ | +| | ECF | ≡ | ≡ | ≡ | ≡ | ✗ | | | | | | +| LC
PLC | ERQ | | | | | A | A | A | A | | | +| | ECF | | | | | | | | | | | +| TC
PTC | ERQ | A | A | A | A | | | | | | | +| | ECF | | | | | | | | | | | +| MSLC
TCS | ERQ | ≡ | ≡ | ≡ | ≡ | == | == | == | == | ★ | | +| | ECF | | | | | | | | | | | + +Figure III.4/Q.2630.3 – No CS-1 nodes in the AAL type 2 connection in the "From CS-3 to CS-2/CS-1" scenario + +In the ESTABLISH.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; and +- the Modify Support for Link Characteristics. + +Nodes CS3a, CS3b, CS3c, and CS3d reserve connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +At node CS2e, the Transfer Capability Support (TCS) parameter is discarded (compatibility instructions). + +Nodes CS2e, CS2f, CS2g, and CS2h reserve connection resources reflecting the more "demanding" of the parameters Link Characteristics (LC) and Preferred Link Characteristics (PLC). + +Node CS2i allocates connection resources reflecting the Preferred Link Characteristics (PLC) parameter; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter. The parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC) are discarded. The parameters Link Characteristics (LC), Preferred Link Characteristics (PLC), and Modify Support for Link Characteristics (MSLC) are passed to the AAL type 2 served user. The Modify Support for Link Characteristics (MSLC) parameter is inserted into the Establish Confirm (ECF) message. + +Nodes CS2h, CS2g, CS2f, and CS2e allocate connection resources reflecting the Preferred Link Characteristics (PLC) parameter that was previously passed in the Establish Request (ERQ) message; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Nodes CS3d, CS3c, CS3b, and CS3a allocate connection resources reflecting the Preferred Transfer Capability (PTC) that was previously passed in the Establish Request (ERQ) message or received from the AAL type 2 served user; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Node CS3a includes the Modify Support for Link Characteristics (MSLC) parameter in the ESTABLISH.confirm primitive to the AAL type 2 served user. The absence of the Transfer Capability Support (TCS) parameter indicates that the AAL type 2 connection does not pass through CS-3 nodes entirely. + +##### III.2.3.2 At least one CS-1 node in the AAL type 2 connection + +The parameters transported in the Establish Request (ERQ) and Establish Confirm (ECF) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.5. + +| | | CS3a | CS3b | CS3c | CS3d | CS2e | CS2f | CS1g | CS2h | CS2i | | +|-------------|------|------|------|------|------|---------|------|--------|------|------|---| +| E
R
Q | LC | ≡ | ≡ | ≡ | ≡ | R | R | A
✗ | A | A | ➔ | +| | PLC | ≡ | ≡ | ≡ | ≡ | R | R | | | | | +| | TC | R | R | R | R | -- | -- | -- | -- | ✗ | | +| E
C
F | PTC | R | R | R | R | -- | -- | -- | -- | ✗ | | +| | MSLC | ≡ | ≡ | ≡ | ≡ | --
✗ | -- | ✗ | | | | +| | TCS | ≡ | ≡ | ≡ | ≡ | | | | | | | +| E
C
F | LC | | | | | A | A | | | | | +| | PLC | | | | | | | | | | | +| | TC | A | A | A | A | | | | | | | +| E
C
F | PTC | | | | | | | | | | | +| | MSLC | | | | | | | | | | | +| | TCS | | | | | | | | | | | + +Figure III.5/Q.2630.3 – At least one CS-1 nodes in the AAL type 2 connection +in the "From CS-3 to CS-2/CS-1" scenario + +In the ESTABLISH.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Transfer Capability; +- the Preferred Transfer Capability; +- the Transfer Capability Support; +- the Link Characteristics; +- the Preferred Link Characteristics; and +- the Modify Support for Link Characteristics. + +Nodes CS3a, CS3b, CS3c, and CS3d reserve connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +At node CS2e, the Transfer Capability Support (TCS) parameter is discarded (compatibility instructions). + +Nodes CS2e and CS2f reserve connection resources reflecting the more "demanding" of the parameters Link Characteristics (LC) and Preferred Link Characteristics (PLC). + +At node CS1g, the parameters Preferred Link Characteristics (PLC) and Modify Support for Link Characteristics (MSLC) are discarded (compatibility instructions). Connection resources reflecting the Link Characteristics (LC) are allocated. + +Node CS2h allocates connection resources reflecting the Link Characteristics (LC); the Preferred Link Characteristics (PLC) parameter is no longer present in the Establish Request (ERQ) message. + +At node CS2i, connection resources reflecting the Link Characteristics (LC) are allocated; the Preferred Link Characteristics (PLC) parameter is no longer present in the Establish Request (ERQ) message. The parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC) are discarded. The Link Characteristics (LC) parameter is passed to the AAL type 2 served user. No parameters are inserted into the Establish Confirm (ECF) message. + +At nodes CS2h and CS1g, no action except passing the Establish Confirm (ECF) message is performed. + +Nodes CS2f and CS2e allocate connection resources reflecting the Link Characteristics (LC) that was previously passed in the Establish Request (ERQ) message; this decision is based on the absence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Nodes CS3d, CS3c, CS3b, and CS3a allocate connection resources reflecting the Transfer Capability (TC) that was previously passed in the Establish Request (ERQ) message or received from the AAL type 2 served user; this decision is based on the absence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Node CS3a includes no parameters in the ESTABLISH.confirm primitive to the AAL type 2 served user. The absence of the Transfer Capability Support (TCS) parameter indicates that the AAL type 2 connection does not pass through CS-3 nodes entirely. + +#### III.2.4 From a CS-2/CS-1 service endpoint to a CS-3 service endpoint + +This clause illustrates AAL type 2 connection establishment where the originating AAL type 2 service endpoint resides in a part of the network consisting of CS-2 and/or CS-1 nodes and where the destination AAL type 2 service endpoint resides in a part of the network consisting of CS-3 nodes. + +##### III.2.4.1 No CS-1 nodes in the AAL type 2 connection + +The parameters transported in the Establish Request (ERQ) and Establish Confirm (ECF) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.6. + +| | | CS2a | CS2b | CS2c | CS2d | CS2e | CS3f | CS3g | CS3h | CS3i | | +|-------------|--------------------------|--------------------------|--------|--------|--------|--------|------------|--------|--------|--------|--------------------------| +| LC
PLC |

Image: arrow icon

| R
R | R
R | R
R | R
R | R
R | ≡
≡ | ≡
≡ | ≡
≡ | ≡
≡ |

Image: arrow icon

| +| |

Image: arrow icon

| R
R | R
R | R
R | R
R | R
R | ≡
≡ | ≡
≡ | ≡
≡ | ≡
≡ |

Image: arrow icon

| +| TC
PTC | E
R
Q | | | | | | ★ R
★ R | R
R | R
R | |

Image: arrow icon

| +| | | | | | | | | R
R | R
R | A |

Image: arrow icon

| +| MSLC
TCS |

Image: arrow icon

| == | == | == | == | == | ≡ | ≡ | ≡ | ≡ |

Image: arrow icon

| +| | | | | | | | | | | | | +| LC
PLC | E
C
F | | | | | | | | | | | +| | | A | A | A | A | A | | | | | | +| TC
PTC | | | | | | | | | | | | +| | | | | | | | A | A | A | | | +| MSLC
TCS | |

Image: arrow icon

| == | == | == | == | == | ≡ | ≡ | ≡ | ★ | + +**Figure III.6/Q.2630.3 – No CS-1 nodes in the AAL type 2 connection in the +"From CS-2/CS-1 to CS-3" scenario** + +In the ESTABLISH.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Link Characteristics; +- the Preferred Link Characteristics; and +- the Modify Support for Link Characteristics. + +Nodes CS2a, CS2b, CS2c, CS2d, and CS2e reserve connection resources reflecting the more "demanding" of the parameters Link Characteristics (LC) and Preferred Link Characteristics (PLC). + +At node CS3f, the Transfer Capability (TC) parameter is not present; hence, the nodal function prepares a Transfer Capability (TC) parameter corresponding to the Link Characteristics (LC) parameter. In addition, the Preferred Link Characteristics (PLC) parameter is present also; hence, the nodal function prepares a Preferred Transfer Capability (PTC) parameter corresponding to the Preferred Link Characteristics (PLC) as well. Node CS3f then reserves connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +Nodes CS3g and CS3h reserve connection resources reflecting the more "demanding" of the parameters Transfer Capability (TC) and Preferred Transfer Capability (PTC). + +Node CS3i allocates connection resources reflecting the Preferred Transfer Capability (PTC) parameter; this decision is based on the presence of the Preferred Transfer Capability (PTC) parameter. The parameters Transfer Capability (TC), Preferred Transfer Capability (PTC), Link Characteristics (LC), Preferred Link Characteristics (PLC), and Modify Support for Link Characteristics (MSLC) are passed to the AAL type 2 served user. The absence of the Transfer Capability Support (TCS) parameter indicates that the AAL type 2 connection does not pass through CS-3 nodes entirely. The Modify Support for Link Characteristics (MSLC) parameter is inserted into the Establish Confirm (ECF) message. + +Nodes CS3h, CS3g, and CS3f allocate connection resources reflecting the Preferred Transfer Capability (PTC) parameter that was previously passed in the Establish Request (ERQ) message; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Nodes CS2e, CS2d, CS2c, CS2b, and CS2a allocate connection resources reflecting the Preferred Link Characteristics (PLC) parameter that was previously passed in the Establish Request (ERQ) message or received from the AAL type 2 served user; this decision is based on the presence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Node CS2a includes the Modify Support for Link Characteristics (MSLC) parameter in the ESTABLISH.confirm primitive to the AAL type 2 served user. + +##### **III.2.4.2 At least one CS-1 node in the AAL type 2 connection** + +The parameters transported in the Establish Request (ERQ) and Establish Confirm (ECF) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.7. + +| | | CS2a | CS2b | CS1c | CS2d | CS2e | CS3f | CS3g | CS3h | CS3i | | +|-------------|-------------|--------|--------|--------|------|------|------|------|------|------|---| +| E
R
Q | LC
PLC | R
R | R
R | A
✗ | A | A | ≡ | ≡ | ≡ | ≡ | ↗ | +| | TC
PTC | | | | | | ★ A | A | A | A | ↗ | +| | MSLC
TCS | == | == | ✗ | | | | | | | | +| E
C
F | LC
PLC | A | A | | | | | | | | | +| | TC
PTC | | | | | | | | | | | +| | MSLC
TCS | | | | | | | | | | | + +**Figure III.7/Q.2630.3 – At least one CS-1 nodes in the AAL type 2 connection in the "From CS-2/CS-1 to CS-3" scenario** + +In the ESTABLISH.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Link Characteristics; +- the Preferred Link Characteristics; and +- the Modify Support for Link Characteristics. + +Nodes CS2a and CS2b reserve connection resources reflecting the more "demanding" of the parameters Link Characteristics (LC) and Preferred Link Characteristics (PLC). + +At node CS1c, the parameters Preferred Link Characteristics (PLC) and Modify Support for Link Characteristics (MSLC) are discarded (compatibility instructions). Connection resources reflecting the Link Characteristics (LC) are allocated. + +Nodes CS2d and CS2e allocate connection resources reflecting the Link Characteristics (LC); the Preferred Link Characteristics (PLC) parameter is no longer present in the Establish Request (ERQ) message. + +At node CS3f, the Transfer Capability (TC) parameter is not present; hence, the nodal function prepares a Transfer Capability (TC) parameter corresponding to the Link Characteristics (LC) parameter. The Preferred Link Characteristics (PLC) parameter is not present; hence, no Preferred Transfer Capability (PTC) parameter needs to be prepared. Node CS3f then allocates connection resources reflecting the Transfer Capability (TC) parameter. + +Nodes CS3g and CS3h allocate connection resources reflecting the Transfer Capability (TC) parameter. + +Node CS3i allocates connection resources reflecting the Transfer Capability (TC) parameter. The parameters Transfer Capability (TC) and Link Characteristics (LC) are passed to the AAL type 2 served user. The absence of the Transfer Capability Support (TCS) parameter indicates that the AAL type 2 connection does not pass through CS-3 nodes entirely. No parameters are inserted into the Establish Confirm (ECF) message. + +At nodes CS3h, CS3g, CS3f, CS2e, CS2d and CS1c, no action except passing the Establish Confirm (ECF) message is performed. + +Nodes CS2b and CS2a allocate connection resources reflecting the Link Characteristics (LC) parameter that was previously passed in the Establish Request (ERQ) message or received from the AAL type 2 served user; this decision is based on the absence of the Modify Support for Link Characteristics (MSLC) parameter in the Establish Confirm (ECF) message. + +Node CS2a includes no parameters in the ESTABLISH.confirm primitive to the AAL type 2 served user. + +### III.3 Connection Resource Modification + +#### III.3.1 All CS-3 nodes + +This clause illustrates AAL type 2 connection resource modifications where the originating and the destination AAL type 2 service endpoints as well as all AAL type 2 switches reside in a part of the network consisting of CS-3. + +The availability of the full functionality specified in this Recommendation (capability set 3) was asserted by the receipt of the Transfer Capability Support (TCS) parameter by both service endpoints at connection establishment (see III.2.1). There exists no need to transmit parameters used only for interworking. + +The parameters transported in the Modify Request (MOD) and Modify Acknowledge (MOA) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.8. + +| | | | CS3a | CS3b | CS3c | CS3d | CS3e | CS3f | CS3g | CS3h | CS3i | +|----------------------------------------|---|---|------|------|------|------|------|------|------|------|------| +| LC old
LC new | M | | | | | | | | | | | +| | O | | | | | | | | | | | +| TC old
TC new | D | ↳ | R | R | R | R | R | R | R | R | | +| | A | ↪ | R | R | R | R | R | R | R | R | A | +| LC old
LC new | M | | | | | | | | | | | +| | O | | | | | | | | | | | +| TC old
TC new | A | | A | A | A | A | A | A | A | A | | +| | | | | | | | | | | | | + +Figure III.8/Q.2630.3 – AAL type 2 connection resource modification in the "All CS-3" scenario + +In the MODIFY.request primitive, the nodal function receives from the AAL type 2 served user the Transfer Capability (TC) parameter. + +Nodes CS3a, CS3b, CS3c, CS3d, CS3e, CS3f, CS3g, and CS3h reserve connection resources reflecting the more "demanding" of the currently allocated connection resources (TCold) and the Transfer Capability (TCnew) parameter. + +Node CS3i allocates connection resources reflecting the Transfer Capability (TCnew) parameter. The Transfer Capability (TCnew) parameter is passed to the AAL type 2 served user. + +Nodes CS3h, CS3g, CS3f, CS3e, CS3d, CS3c, CS3b, and CS3a allocate connection resources reflecting the new Transfer Capability (TCnew) parameter that was previously passed in the Modify Request (MOD) message or received from the AAL type 2 served user; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Node CS3a includes no parameters in the MODIFY.confirm primitive to the AAL type 2 served user. + +#### III.3.2 From CS-3 via CS-2 nodes to CS-3 + +This clause illustrates AAL type 2 connection resource modification where the modify originating and the modify destination AAL type 2 service endpoints reside in a part of the network consisting of CS-3 nodes and where the AAL type 2 connection passes through a part of the network consisting of CS-2 nodes. + +NOTE – Connection Resource Modification is not possible if a CS-1 node is part of the AAL type 2 connection. + +The parameters transported in the Modify Request (MOD) and Modify Acknowledge (MOA) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.9. + +| | | | CS3a | CS3b | CS2c | CS2d | CS2e | CS2f | CS2g | CS3h | CS3i | +|----------------------------------------|---|---|------|------|------|------|------|------|------|------|------| +| LC old
LC new | M | ↳ | ≡ | ≡ | R | R | R | R | R | ≡ | ≡ | +| | O | ↳ | ≡ | ≡ | R | R | R | R | R | ≡ | ≡ | +| TC old
TC new | D | ↳ | R | R | — | — | — | — | — | R | A | +| | A | ↳ | R | R | — | — | — | — | — | R | A | +| LC old
LC new | M | ↳ | | | A | A | A | A | A | | | +| | O | ↳ | | | A | A | A | A | A | | | +| TC old
TC new | D | ↳ | A | A | | | | | | A | | +| | A | ↳ | A | A | | | | | | A | | + +Figure III.9/Q.2630.3 – AAL type 2 connection resource modification in the "From CS-3 via CS-2 nodes to CS-3" scenario + +In the MODIFY.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Transfer Capability; and +- the Link Characteristics. + +Nodes CS3a and CS3b reserve connection resources reflecting the more "demanding" of the currently allocated connection resources (TCold) and the Transfer Capability (TCnew) parameter. + +Nodes CS2c, CS2d, CS2e, CS2f and CS2g reserve connection resources reflecting the more "demanding" of the currently allocated connection resources (LCold) and the Link Characteristics (LCnew) parameter. + +Node CS3h reserves connection resources reflecting the more "demanding" of the currently allocated connection resources (TCold) and the Transfer Capability (TCnew) parameter. + +Node CS3i allocates connection resources reflecting the Transfer Capability (TCnew) parameter. The parameters Transfer Capability (TCnew) and Link Characteristics (LCnew) are passed to the AAL type 2 served user. + +Node CS3h allocates connection resources reflecting the new Transfer Capability (TCnew) parameter that was previously passed in the Modify Request (MOD) message; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Nodes CS2g, CS2f, CS2e, CS2d and CS2c allocate connection resources reflecting the new Link Characteristics (LCnew) parameter that was previously passed in the Modify Request (MOD) message; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Nodes CS3b and CS3a allocate connection resources reflecting the new Transfer Capability (TCnew) parameter that was previously passed in the Modify Request (MOD) message or received from the AAL type 2 served user; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Node CS3a sends a MODIFY.confirm primitive to the AAL type 2 served user. + +#### III.3.3 From a CS-3 service endpoint to a CS-2 service endpoint + +This clause illustrates AAL type 2 connection resource modification where the modify originating AAL type 2 service endpoint resides in a part of the network consisting of CS-3 nodes and where the modify destination AAL type 2 service endpoint resides in a part of the network consisting of CS-2 nodes. + +NOTE – Connection Resource Modification is not possible if a CS-1 node is part of the AAL type 2 connection. + +The parameters transported in the Modify Request (MOD) and Modify Acknowledge (MOA) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.10. + +| | | | CS3a | CS3b | CS3c | CS3d | CS2e | CS2f | CS2g | CS2h | CS2i | | +|----------------------------------------|---|---|--------|--------|--------|--------|--------|--------|--------|--------|------|---| +| LC old
LC new | M | ↳ | ≡ | ≡ | ≡ | ≡ | R
R | R
R | R
R | R
R | A | ↳ | +| | O | ↳ | | | | | | | | | | | +| TC old
TC new | D | ↳ | R
R | R
R | R
R | R
R | — | — | — | — | × | | +| | D | ↳ | | | | | | | | | | | +| LC old
LC new | M | | | | | | A | A | A | A | | | +| | O | | | | | | | | | | | | +| TC old
TC new | A | | A | A | A | A | | | | | | | +| | A | | | | | | | | | | | | + +Figure III.10/Q.2630.3 – AAL type 2 connection resource modification in the "From CS-3 to CS-2" scenario + +In the MODIFY.request primitive, the nodal function receives from the AAL type 2 served user the following parameters relevant to interworking and connection resource allocation: + +- the Transfer Capability; and +- the Link Characteristics. + +Nodes CS3a, CS3b, CS3c, and CS3d reserve connection resources reflecting the more "demanding" of the currently allocated connection resources (TCold) and the Transfer Capability (TCnew) parameter. + +Nodes CS2e, CS2f, CS2g and CS2h reserve connection resources reflecting the more "demanding" of the currently allocated connection resources (LCold) and the Link Characteristics (LCnew) parameter. + +Node CS2i allocates connection resources reflecting the Link Characteristics ( $LC_{new}$ ) parameter. The Transfer Capability (TC) parameter is discarded. The Transfer Capability ( $LC_{new}$ ) parameter is passed to the AAL type 2 served user. + +Nodes CS2h, CS2g, CS2f and CS2e allocate connection resources reflecting the new Link Characteristics ( $LC_{new}$ ) parameter that was previously passed in the Modify Request (MOD) message; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Nodes CS3d, CS3c, CS3b, and CS3a allocate connection resources reflecting the new Transfer Capability ( $TC_{new}$ ) parameter that was previously passed in the Modify Request (MOD) message or received from the AAL type 2 served user; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Node CS3a sends a MODIFY.confirm primitive to the AAL type 2 served user. + +#### III.3.4 From a CS-2 service endpoint to a CS-3 service endpoint + +This clause illustrates AAL type 2 connection resource modification where the modify originating AAL type 2 service endpoint resides in a part of the network consisting of CS-2 nodes and where the modify destination AAL type 2 service endpoint resides in a part of the network consisting of CS-3 nodes. + +NOTE – Connection Resource Modification is not possible if a CS-1 node is part of the AAL type 2 connection. + +The parameters transported in the Modify Request (MOD) and Modify Acknowledge (MOA) messages and the effects on the connection resource allocation mechanisms are illustrated in Figure III.11. + +| | | | CS2a | CS2b | CS2c | CS2d | CS2e | CS3f | CS3g | CS3h | CS3i | +|--------------------------|---|---|------|------|------|------|------|----------|--------|--------|------| +| $LC_{old}$
$LC_{new}$ | M | ↳ | R | R | R | R | R | ≡ | ≡ | ≡ | ≡ | +| | O | | R | R | R | R | R | ≡ | ≡ | ≡ | ≡ | +| $TC_{old}$
$TC_{new}$ | D | | | | | | | R
★ R | R
R | R
R | A | +| | A | | | | | | | | | | ↗ | +| $LC_{old}$
$LC_{new}$ | M | | A | A | A | A | A | | | | | +| | O | | | | | | | | | | | +| $TC_{old}$
$TC_{new}$ | A | | | | | | | A | A | A | | +| | A | | | | | | | | | | | + +Figure III.11/Q.2630.3 – AAL type 2 connection resource modification in the "From CS-2 to CS-3" scenario + +In the MODIFY.request primitive, the nodal function receives from the AAL type 2 served user the Link Characteristics ( $LC_{new}$ ) parameter. + +Nodes CS2a, CS2b, CS2c, CS2d and CS2e reserve connection resources reflecting the more "demanding" of the currently allocated connection resources ( $LC_{old}$ ) and the Link Characteristics ( $LC_{new}$ ) parameter. + +At node CS3f, the Transfer Capability ( $TC_{new}$ ) parameter is not present; hence, the nodal function prepares a Transfer Capability ( $TC_{new}$ ) parameter corresponding to the Link Characteristics ( $LC_{new}$ ) parameter. + +Nodes CS3f, CS3g and CS3h reserve connection resources reflecting the more "demanding" of the currently allocated connection resources ( $TC_{old}$ ) and the Transfer Capability ( $TC_{new}$ ) parameter. + +Node CS3i allocates connection resources reflecting the Transfer Capability ( $TC_{new}$ ) parameter. The parameters Transfer Capability ( $TC_{new}$ ) and Link Characteristics ( $LC_{new}$ ) are passed to the AAL type 2 served user. + +Nodes CS3h, CS3g, and CS3f allocate connection resources reflecting the new Transfer Capability ( $TC_{new}$ ) parameter that was previously passed in the Modify Request (MOD) message; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Nodes CS2e, CS2d, CS2c, CS2b and CS2a allocate connection resources reflecting the new Link Characteristics ( $LC_{new}$ ) parameter that was previously passed in the Modify Request (MOD) message or received from the AAL type 2 served user; this decision is based on the nature of the message, i.e., Modification Acknowledge (MOA) message rather than the Modification Reject (MOR) message. + +Node CS2a sends a MODIFY.confirm primitive to the AAL type 2 served user. + + + +# 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 | + +\*25389\* \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2631.1-200310-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Q/T-REC-Q.2631.1-200310-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a15b60751a93f5cecb954fa3493e126283981fcf --- /dev/null +++ b/marked/Q/T-REC-Q.2631.1-200310-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d26ec4f259f10ff2652f8f6217c8379c3494803641f68d1c1e21d4c88d9a5cc +size 94389 diff --git a/marked/Q/T-REC-Q.2631.1-200310-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2631.1-200310-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.2631.1-200310-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.2631.1-200310-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.2631.1-200310-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b33a7ba639e8f914e916a699c435f775424ed12 --- /dev/null +++ b/marked/Q/T-REC-Q.2631.1-200310-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa8ee5391753379aca20714688dedb000afcbaee8a293893dcd5383aa5a5bb1b +size 36316 diff --git a/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0de55b308079d1e742de19a3a2fbf402ccdef532 --- /dev/null +++ b/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/raw.md @@ -0,0 +1,422 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2726.4** + +(06/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for the +network signalling + +--- + +**Extensions to the B-ISDN user part – +Application generated identifiers** + +ITU-T Recommendation Q.2726.4 + +(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. + +# **Extensions to the B-ISDN user part – Application generated identifiers** + +## **Summary** + +This Recommendation defines B-ISUP capability to transport application generated identifiers. This capability allows the transport through the B-ISDN of identifiers required and used by various distributed applications. This capability allows an originating entity (e.g. a calling party) to transmit identifiers that can be used by a peer entity. + +## **Source** + +ITU-T Recommendation Q.2726.4 was revised by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 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 Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 B-ISDN user part messages and parameters ..... | 2 | +| 5.1 Messages ..... | 2 | +| 5.1.1 IAM..... | 2 | +| 5.1.2 ACM..... | 2 | +| 5.1.3 CPG ..... | 2 | +| 5.1.4 ANM..... | 2 | +| 5.1.5 REL..... | 2 | +| 5.2 Application generated identifier parameter..... | 2 | +| 5.3 Application process procedures ..... | 3 | +| 5.3.1 Call/connection establishment..... | 3 | +| 5.3.2 Completion of the call/connection setup request..... | 4 | +| 5.3.3 Call/connection release..... | 4 | +| 5.4 Application service elements and primitives ..... | 5 | +| 5.4.1 Primitives between SACF and AP..... | 5 | +| 5.5 Interworking..... | 6 | +| 5.5.1 Interworking with nodes which do not support the procedures described in this Recommendation ..... | 6 | +| 5.5.2 Interworking with ISUP..... | 6 | +| 5.5.3 Interworking with DSS2 ..... | 6 | +| Appendix I – Setting of instruction indicators ..... | 7 | + +# **Extensions to the B-ISDN user part – Application generated identifiers** + +# **1 Scope** + +This Recommendation defines B-ISUP capability to transport application generated identifiers. This capability allows the transport through the B-ISDN of identifiers required and used by various distributed applications. This capability allows an originating entity (e.g. a calling party) to transmit identifiers that can be used by a peer entity. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Q.2722.1 (1996), *B-ISDN user part – Network node interface specification for point-to-multipoint call/connection control.* +- [2] ITU-T Q.2761 (1999), *Functional description of the B-ISDN user part (B-ISUP) of signalling system No. 7.* +- [3] ITU-T Q.2762 (1999), *General functions of messages and signals of the B-ISDN user part (B-ISUP) of signalling system No. 7.* +- [4] ITU-T Q.2763 (1999), *Signalling System No. 7 B-ISDN User Part (B-ISUP) – Formats and codes.* +- [5] ITU-T Q.2764 (1999), *Signalling System No. 7 B-ISDN User Part (B-ISUP) – Basic call procedures.* +- [6] ITU-T Q.2941.1 (1997), *Digital Subscriber Signalling System No. 2 – Generic identifier transport.* + +# **3 Definitions** + +No new definitions are required. + +# **4 Abbreviations** + +No new abbreviations are used. The abbreviations of ITU-T Q.2722.1, Q.2761, Q.2762, Q.2763 and Q.2764 apply. + +# 5 B-ISDN user part messages and parameters + +## 5.1 Messages + +### 5.1.1 IAM + +The IAM contains the following additional parameter: + +- Application generated identifier. + +### 5.1.2 ACM + +The ACM contains the following additional parameter: + +- Application generated identifier. + +### 5.1.3 CPG + +The CPG contains the following additional parameter: + +- Application generated identifier. + +### 5.1.4 ANM + +The ANM contains the following additional parameter: + +- Application generated identifier. + +### 5.1.5 REL + +The REL contains the following additional parameter: + +- Application generated identifier. + +## 5.2 Application generated identifier parameter + +The parameter name code allocated to the application generated identifier parameter is 0110 1010. + +The application generated identifier parameter carries one or more instances of the DSS2 generic identifier transport information element. The format of the application generated identifier is shown in Figure 1. + +![Diagram of the application generated identifier parameter structure showing octet 1 with Spare, Repeat indicator, and Priority subfields, followed by one or more instances of the generic identifier transport information element.](af242f25c3ad34b01ebf5fcb23430021_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-------------------------------------------------------------------------------------------------------------------------------|---|---|------------------|----------|---|---|---|--------| +| Spare | | | Repeat indicator | Priority | | | | 1 | +| One or more instances of the generic identifier transport information element defined in ITU-T Q.2941.1 starting with octet 1 | | | | | | | | 2 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | = | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | n | + +Diagram of the application generated identifier parameter structure showing octet 1 with Spare, Repeat indicator, and Priority subfields, followed by one or more instances of the generic identifier transport information element. + +Figure 1/Q.2726.4 – Application generated identifier parameter + +The following codes are used in the subfields of the application generated identifier parameter field. + +### a) *Repeat indicator (octet 1)* + +- 0 Information element not repeated +- 1 Information element repeated + +- b) *Priority (octet 1)* +- 0000 No prioritized order +- 0001 Prioritized list for selecting one possibility: ascending order +- 0010 Prioritized list for selecting one possibility: descending order +- 0011 } Reserved +to } +1111 } +- c) *Generic identifier transport information elements (octet 2-n)* +- This field contains all instances of the generic identifier transport information element received from DSS2 or generated by an originating or addressed entity located in the network. The format of the generic identifier transport information elements is the same as specified in ITU-T Q.2941.1 [6]. The order of the information elements is not changed. The number of instances or maximum length of the generic identifier transport information element is network-dependent. + +## 5.3 Application process procedures + +### 5.3.1 Call/connection establishment + +- a) *Originating exchange* +- The Set\_Up request primitive may include an application generated identifier parameter carrying unaltered, one or more instances of the generic identifier transport information element received from the DSS2 or generated by an application entity located in the originating exchange. +- b) *Intermediate national exchange* +- If an incoming side of an intermediate national exchange receives an application generated identifier parameter in a Set\_Up indication primitive, the outgoing side of the exchange will include it unaltered in the Set\_Up request primitive it will issue. +- c) *Outgoing international exchange* +- If an outgoing international exchange receives an application generated identifier parameter in a Set\_Up indication primitive, it shall include it unaltered in the Set\_Up request primitive it will issue. +- d) *Incoming international exchange* +- It is a network option how an incoming international gateway shall proceed when it receives an application generated identifier parameter. If the application generated identifier service is not supported by the network, the incoming international exchange may either: +- clear the call with cause # 63, "Service option not available, unspecified", or + - pass on the parameter and progress the call establishment. +- If the incoming international gateway decides to progress the call establishment, it will issue a Set\_Up request primitive containing unaltered, the application generated identifier parameter it has received. + +#### e) *Destination exchange* + +If the Set\_Up request primitive contains an application generated identifier parameter, it will be transferred unaltered in the indication sent to the called party as specified in ITU-T Q.2941.1 [6]. Alternatively, the destination exchange may process the application generated identifier parameter, if the addressed entity is located in the destination exchange. + +### 5.3.2 Completion of the call/connection setup request + +#### a) *Destination exchange* + +Primitives issued by the destination exchange after receiving a signal from the called party may contain an application generated identifier parameter. The application generated identifier parameter will contain unaltered, the identifiers received from the access or generated by the addressed entity. The following primitives may carry the application generated parameter: + +- Address\_Complete request; +- Progress request; +- Answer request. + +#### b) *Intermediate national or international exchange* + +The incoming side of an intermediate national or international exchange may receive in the Address\_Complete indication, the Progress indication or the Answer indication primitive an application generated identifier parameter. The outgoing side of the exchange will pass the application generated identifier parameter in a corresponding Address\_Complete indication, Progress indication or Answer indication primitive. + +It is a network option how an incoming or outgoing international gateway shall proceed when it receives an application generated identifier parameter. The options defined in 5.3.1 d) are applicable. + +#### c) *Originating exchange* + +The originating exchange may receive an Address\_Complete indication, a Progress indication or an Answer indication primitive containing an application generated identifier parameter. The access side of the originating exchange will relay the contents of the application generated identifier parameter to the calling party in the appropriate access signal or to the application entity. + +### 5.3.3 Call/connection release + +#### a) *Access exchange initiating the release procedure* + +When the call/connection release is initiated by a user, the access exchange may receive from the user initiating the release, a signal carrying one or more application generated identifiers. The Release request primitive will carry them in an application generated identifier parameter. + +#### b) *Intermediate national or international exchange* + +If an incoming side of an intermediate exchange receives an application generated parameter in a Release indication primitive, the outgoing side of the exchange will include them unaltered in the Release request primitive to be issued. + +It is a network option how an incoming or outgoing international gateway shall proceed when it receives an application generated identifier parameter. The options defined in 5.3.1 d) are applicable. + +#### c) *Access exchange receiving a release indication* + +If an access exchange receives a Release indication primitive containing an application generated identifier parameter, the contents will be transferred unaltered in the indication sent to the user as specified in ITU-T Q.2941.1 [6]. + +## 5.4 Application service elements and primitives + +The following primitives are affected. + +### 5.4.1 Primitives between SACF and AP + +#### 5.4.1.1 Set\_Up request/indication primitives + +Table 1 shows the parameter that must be added to the Set\_Up request/indication primitives. + +**Table 1/Q.2726.4 – Parameter for the Set\_Up request/indication primitives** + +| Set_Up request/indication | B-ISDN | +|----------------------------------|--------| +| Application generated identifier | O | + +#### 5.4.1.2 Address\_Complete request/indication primitives + +Table 2 shows the parameter that must be added to the Address\_Complete request/indication primitives. + +**Table 2/Q.2726.4 – Parameter for the Address\_Complete request/indication primitives** + +| Address_Complete Request/indication | B-ISDN | +|-------------------------------------|--------| +| Application generated identifier | O | + +#### 5.4.1.3 Progress request/indication primitives + +Table 3 shows the parameter that must be added to the Progress request/indication primitives. + +**Table 3/Q.2726.4 – Parameter for the Progress request/indication primitives** + +| Progress request/indication | B-ISDN | +|----------------------------------|--------| +| Application generated identifier | O | + +#### 5.4.1.4 Answer request/indication primitives + +Table 4 shows the parameter that must be added to the Answer request/indication primitives. + +**Table 4/Q.2726.4 – Parameter for the Answer request/indication primitives** + +| Answer request/indication | B-ISDN | +|----------------------------------|--------| +| Application generated identifier | O | + +#### 5.4.1.5 Release request/indication primitives + +Table 5 shows the parameter that must be added to the Release request/indication primitives. + +**Table 5/Q.2726.4 – Parameter for the Release request/indication primitives** + +| Release request/indication | B-ISDN | +|----------------------------------|--------| +| Application generated identifier | O | + +## 5.5 Interworking + +### 5.5.1 Interworking with nodes which do not support the procedures described in this Recommendation + +The application generated identifier parameter shall be passed on such a node. If it cannot be passed on, the call shall be released. + +NOTE – The instruction indicators are set as shown in Appendix I in order to support the correct behaviour. + +### 5.5.2 Interworking with ISUP + +The application generated identifier parameter is not supported in ISUP. Therefore, the call shall be released at the B-ISUP/ISUP interworking point with cause # 63 "Service or option not available". + +NOTE – The instruction indicators are set as shown in Appendix I in order to support the correct behaviour. + +### 5.5.3 Interworking with DSS2 + +#### a) Messages + +- | | | | | | +|--------------------|---|------------|---|-----------------------| +| • SETUP | → | IAM | → | SETUP | +| • ADD PARTY | → | IAM | → | SETUP or ADD PARTY | +| • ALERTING | ← | ACM or CPG | ← | ALERTING | +| • ADD PARTY ALERT | ← | ACM or CPG | ← | ADD PARTY ALERT | +| • CONNECT | ← | ANM | ← | CONNECT | +| • ADD PARTY ACK | ← | ANM | ← | ADD PARTY ACK | +| • RELEASE | → | REL | → | RELEASE or DROP PARTY | +| • RELEASE COMPLETE | → | REL | → | RELEASE or DROP PARTY | +| • DROP PARTY | → | REL | → | RELEASE or DROP PARTY | +| • ADD PARTY REJECT | ← | REL | ← | ADD PARTY REJECT | + +#### b) Parameters + +All instances of the DSS2 generic identifier transport information element are mapped into an application generated identifier parameter. The priority subfield shall be set to "No prioritized order". + +# APPENDIX I + +## Setting of instruction indicators + +The setting of the instruction indicators for the application generated identifier parameter is as follows: + +| Indicator | Value | +|--------------------------------------------|-----------------------------| +| Pass on not possible indicator | Release call | +| Discard parameter indicator | Do not discard parameter | +| Discard message indicator | Do not discard message | +| Send notification indicator | Do not send notification | +| Release call indicator | Do not release call | +| Transit at intermediate exchange indicator | Transit node interpretation | +| BB/NB interworking indicator | Release call | + +## 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.2761-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..713c7bf255f10444404c8334989f782ba455b89b --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46692f9cc7d68ca8f043a3ddceb7c56365d6a5fd785fba411d16d414f24dd9c2 +size 45825 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceed24c578ab544ac0f334a99eb3e9cbd407d31e --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ec38ced78aae003a1c25750e77845c0df097c96d991f91dccdebfb214cc384b +size 120119 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b301df6a7a244cb78b98ca748ff0c80be0cf817 --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcab65a80601ba943c0db75b1af9e6b774218de54eb2257109e9ce907556b0bb +size 42086 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc5c653033eae4ad281c327e8af4574f3dd5312 --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a10febfd8f1e8bf419855cd4cab5cb51eab7ae2ef9768e19e3c9e2322edad46 +size 8325 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a385ede62c971157a772c603dcb0ecac4efcbfe9 --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73cfb65260b65d4afffe7f37ee488895bf1a7e3fb89dbbe2dfcb54311f3e05f2 +size 15782 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d07d8a0a4004b84ba871f411e04ae291e83f0e6b --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa73522d33ddbdf98deffce8ca1a66333ec3e1005ea07a9743a873986bf2af98 +size 101759 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b02e75b94a6bb3175b97e0a56607043aab88024 --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac343f0d6765f322c949cfae9a645912792ae3f08e26714240f1eb29a77248f0 +size 73450 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..270dfbf72640e97ddc283508d1988b6bc7764711 --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3ae349845801cfd2abe07d26a4f8ecc4ed62508d10b4f355fa0a7d702aaa78a +size 114149 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27b51c9309bcd901fc1d184f4d7eb711bbb5a22a --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cad0e151b4b98ae37ec46522d110838d9fef54321ce74b5327adba90fde9143 +size 44854 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18fc9675179aba2b2081f7cbcd05f58714d9c59a --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2be8c80670a4cbbaebc6b33319b4486a2a8b548a76b03eeff812574f690f6953 +size 59149 diff --git a/marked/Q/T-REC-Q.2761-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..278784e6ff24c6b5d07578a612f3ced42557d779 --- /dev/null +++ b/marked/Q/T-REC-Q.2761-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3cb6a1a25a72fa798ac549d24047df383539210a9d8402709a24ba75d8a0836 +size 45173 diff --git a/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b5a5b7757004d3e5c2e5b949d695904fb764edc5 --- /dev/null +++ b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/raw.md @@ -0,0 +1,849 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2767.1** + +(06/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for the +network signalling + +--- + +**Soft PVC Capability** + +ITU-T Recommendation Q.2767.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. + +# **Soft PVC Capability** + +## **Summary** + +This Recommendation utilizes the normal procedures of Broadband ISDN User Part (B-ISUP) protocol in order to support soft Permanent Virtual Connections (soft PVCs) between their endpoints. The endpoints are responsible for maintaining the end-to-end circuit by setting up a new switched connection in case the existing switched connection is released or fails. Two types of soft PVC are supported: soft Permanent Virtual Path Connection (PVPC) and soft Permanent Virtual Channel Connection (PVCC). This Recommendation contains the additional message and parameter coding, procedures, ASE descriptions and interworking mapping tables for the support of soft PVCC and soft PVPC services. + +## **Source** + +ITU-T Recommendation Q.2767.1 was revised by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 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 Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +# CONTENTS + +| | | Page | +|-------|-------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations ..... | 2 | +| 5 | B-ISDN user part messages and parameters ..... | 2 | +| 5.1 | Formats ..... | 3 | +| 5.1.1 | Soft PVC called endpoint parameter ..... | 3 | +| 5.1.2 | Soft PVC calling endpoint parameter ..... | 4 | +| 6 | Application process procedures ..... | 5 | +| 6.1 | Connection setup ..... | 5 | +| 6.1.1 | Calling endpoint exchange ..... | 5 | +| 6.1.2 | Intermediate national exchange ..... | 6 | +| 6.1.3 | Outgoing international exchange ..... | 6 | +| 6.1.4 | Intermediate international exchange ..... | 6 | +| 6.1.5 | Incoming international exchange ..... | 6 | +| 6.1.6 | Called endpoint exchange ..... | 6 | +| 6.2 | Answer ..... | 7 | +| 6.2.1 | Called endpoint exchange ..... | 7 | +| 6.2.2 | Calling endpoint exchange ..... | 7 | +| 6.2.3 | Other types of exchanges ..... | 7 | +| 6.3 | Unsuccessful connection setup ..... | 7 | +| 6.3.1 | Calling endpoint exchange ..... | 7 | +| 6.3.2 | Other type of exchanges ..... | 7 | +| 6.4 | Storage of call setup information ..... | 8 | +| 6.5 | Release ..... | 8 | +| 6.5.1 | Release within the network ..... | 8 | +| 6.5.2 | Release by the calling endpoint exchange ..... | 8 | +| 7 | Application service elements and primitives ..... | 8 | +| 7.1 | Primitives between SACF and application process ..... | 8 | +| 7.1.1 | Set_Up request/indication primitive ..... | 8 | +| 7.1.2 | Answer request/indication primitive ..... | 9 | +| 7.2 | Primitives between BCC ASE and SACF ..... | 9 | +| 7.2.1 | Link_Set_Up request/indication primitive ..... | 9 | +| 7.2.2 | Link_Information request/indication primitive ..... | 9 | +| 7.3 | ASE descriptions ..... | 9 | + +| | Page | | +|-------------|-----------------------------------------------------------------------------------|----| +| 8 | Instruction indicators and interworking ..... | 9 | +| 8.1 | Interworking with nodes not supporting this feature..... | 9 | +| 8.2 | Interworking with DSS2 ..... | 10 | +| 8.3 | Interworking with narrow-band ISDN ..... | 10 | +| 8.4 | Interaction with other capabilities..... | 10 | +| 8.4.1 | Point-to-multipoint ..... | 10 | +| 8.4.2 | Traffic parameters..... | 10 | +| 8.4.3 | Look-ahead..... | 10 | +| 8.4.4 | Negotiation of traffic characteristics during call setup..... | 10 | +| 8.4.5 | Modification of traffic characteristics during the active phase of the call ..... | 10 | +| 8.4.6 | ATM End System Address (AESA) ..... | 10 | +| 8.4.7 | Call priority..... | 10 | +| 8.4.8 | Network generated session ID ..... | 10 | +| 8.4.9 | Frame relay..... | 10 | +| 8.5 | Interworking with the first release of soft PVC – ITU-T Q.2767.1 (05/98)..... | 10 | +| 9 | Timers ..... | 11 | +| Appendix I | – Setting of instruction indicators ..... | 11 | +| Appendix II | – Retry decision ..... | 12 | + +## Soft PVC capability + +# 1 Scope + +This Recommendation contains formats and procedures for supporting soft Permanent Virtual Connections (soft PVCs). Soft PVC capability utilizes the normal procedures of B-ISUP in order to control soft permanent virtual circuit connections between their endpoints. The endpoints are responsible for maintaining the end-to-end circuit by setting up a new switched connection in case the existing switched connection is released or fails. + +The endpoints of a soft PVC are located in the exchanges to which the users of the soft PVC are connected. The endpoint is identifiable by addressing information contained in the call setup signalling, such as an E.164 number plus VPCI/VCI or DLCI value. + +Figure 1 identifies different reference points in a soft PVC using internal SVC connection switching and signalling. + +![Diagram of Soft PVC configuration showing a User connected to a Soft PVC called endpoint, which is connected via NNI signalling to another Soft PVC called endpoint, which is then connected to another User. The connections between the endpoints are labeled VC or VP.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +The diagram illustrates a soft PVC configuration. It shows a 'User' (represented by a square) connected to a 'Soft PVC called endpoint' (represented by a circle). This endpoint is connected via an 'NNI signalling' link (represented by a curved line) to another 'Soft PVC called endpoint' (another circle). This second endpoint is connected via another 'NNI signalling' link to a third 'Soft PVC called endpoint' (a third circle), which is then connected to another 'User' (another square). The connections between the 'Soft PVC called endpoint' circles are labeled 'VC or VP'. The diagram is labeled 'T11100980-98' in the bottom right corner. + +Diagram of Soft PVC configuration showing a User connected to a Soft PVC called endpoint, which is connected via NNI signalling to another Soft PVC called endpoint, which is then connected to another User. The connections between the endpoints are labeled VC or VP. + +Figure 1/Q.2767.1 – Soft PVC configuration + +Two types of soft PVC are supported: + +- soft permanent virtual path connection (PVPC); and +- soft permanent virtual channel connection (PVCC). + +This Recommendation contains the additional message and parameter coding, procedures, ASE descriptions and interworking mapping tables for the support of soft PVCC and soft PVPC services. + +The procedures for control of soft PVCCs are applicable to point-to-point and point-to-multipoint procedures. + +The procedures for control of soft PVPCs follow the additional procedures for switched virtual path connections in ITU-T Q.2766.1. + +The frame relay endpoints can only be connected by a soft PVCC connection and not by a soft PVPC connection. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Q.2724.1 (1996), B-ISDN user part – Look-ahead without state change for the network node interface. +- ITU-T Q.2726.2 (1996), *B-ISDN user part – Call priority*. +- ITU-T Q.2726.3 (1996), *B-ISDN user part – Network generated session identifier*. +- ITU-T Q.2763 (1999), *Signalling System No. 7 B-ISDN User Part (B-ISUP) – Formats and Codes*. +- ITU-T Q.2764 (1999), *Signalling System No. 7 B-ISDN User Part (B-ISUP) – Basic call procedures*. +- ITU-T Q.2766.1 (1998), *Switched virtual path capability*. +- ITU-T Q.2931 (1995), *Digital subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control*. +- ITU-T X.76 (2000), *Network-to-network interface between public networks providing PVC and/or SVC frame relay data transmission service*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 soft PVC called endpoint:** Information sent in the forward (or backward) direction indicating the VPCI or VPCI/VCI values in the case of an ATM user or DLCI value in the case of a Frame Relay user, to be used (or used) for the connection segment between the soft PVC called endpoint and a user. + +**3.2 soft PVC calling endpoint:** Information sent in the forward direction indicating the VPCI or VPCI/VCI values in the case of an ATM user or DLCI value in the case of a Frame Relay user, used for the connection segment between the soft PVC calling endpoint and a user. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|--------------------------------------| +| DLCI | Data Link Connection Identifier | +| NNI | Network-Node Interface | +| PVC | Permanent Virtual Connection | +| PVCC | Permanent Virtual Channel Connection | +| PVPC | Permanent Virtual Path Connection | +| SVC | Switched Virtual Channel | +| UNI | User-Network Interface | +| VCI | Virtual Channel Identifier | +| VPCI | Virtual Path Connection Identifier | + +# 5 B-ISDN user part messages and parameters + +The modifications to parameters and messages described in this clause are required to support soft PVCs. + +## 5.1 Formats + +### 5.1.1 Soft PVC called endpoint parameter + +The format of the Soft PVC called endpoint parameter field is shown in Figures 2a and 2b. + +The parameter name code allocated to the Soft PVC called endpoint parameter is described in ITU-T Q.2763. + +![](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +| | | | | | | | | +|--------------------|-----------------|---|----------|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| ext.
1 | Coding standard | | Reserved | | | | | +| Selection type | | | | | | | | +| Subfield indicator | | | | | | | | +| VPCI value | | | | | | | | +| Subfield indicator | | | | | | | | +| VCI value | | | | | | | | + +**Figure 2a/Q.2767.1 – Soft PVC called endpoint parameter field for ATM user** + +If the DLCI indicator and value exist in the Soft PVC parameter then the VPCI/VCI indicator and value is not needed, i.e. the two subfield parameters are mutually exclusive and only one of the two subfields can exist at one time. Currently the soft PVC called endpoint is coded as follows. + +![](0b87abe67b21a93777287649c33e755d_img.jpg) + +| | | | | | | | | | +|-------------------------|---------------------------------------|-----------------------------------|----------|---|---|-----------|----------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| ext.
1 | Coding standard | | Reserved | | | | | | +| Selection Type | | | | | | | | | +| DLCI subfield indicator | | | | | | | | | +| ext.
0 | Spare
0 | DLCI
(Most significant 6 bits) | | | | | (Note 1) | | +| ext.
0/1 | DLCI
(2nd most significant 4 bits) | | | 0 | 0 | 0 | | | +| ext.
1 | DLCI
(3rd most significant 6 bits) | | | | | Res.
0 | (Note 2) | | +| ext.
0 | DLCI
(3rd most significant 7 bits) | | | | | | (Note 3) | | +| ext.
1 | DLCI
(4th most significant 6 bits) | | | | | Res.
0 | (Note 3) | | + +NOTE 1 – The DLCI is two, three or four octets (i.e. 10 or 16 or 23 bits respectively). The standard default length of the DLCI is two octets. The extension bit mechanism is used to indicate non-default length of the DLCI. + +NOTE 2 – This octet shall only be included when bilateral agreements between the nodes which are endpoints of the soft PVC allow a 3-octet DLCI (16 bits). + +NOTE 3 – These octets shall both be included only when bilateral agreements between the nodes which are endpoints of the soft PVC allow a 4-octet DLCI (23 bits). + +**Figure 2b/Q.2767.1 – Soft PVC called endpoint parameter field for frame relay user** + +Subfields are coded as follows: + +- a) *Selection type* +- | | | +|-----------|----------------| +| 0000 0000 | Any value | +| 0000 0010 | Required value | +| 0000 0100 | Assigned value | +- All other values reserved. +- b) *Subfield indicator* +- | | | +|-----------|------------| +| 0000 0001 | VPCI value | +| 0000 0010 | VCI value | +| 0000 0011 | DLCI value | +- All other values reserved. +- c) *VPCI value* +- Two-octet value coded as in the Connection Element Identifier (see ITU-T Q.2763). +- d) *VCI value* +- Two-octet value coded as in the Connection Element Identifier (see ITU-T Q.2763). +- e) The DLCI value is coded as in ITU-T X.76 without the information element identifier. The default length of DLCI is two octets but can be extended by bilateral agreement to three or four octets (see ITU-T X.76 – Figure 10-18). + +### 5.1.2 Soft PVC calling endpoint parameter + +The format of the Soft PVC calling endpoint parameter field is shown in Figures 3a and 3b. + +The parameter name code allocated to the Soft PVC calling endpoint parameter is described in ITU-T Q.2763. + +![](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +| | | | | | | | | +|--------------------|-----------------|---|----------|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| ext.
1 | Coding standard | | Reserved | | | | | +| Subfield indicator | | | | | | | | +| VPCI value | | | | | | | | +| Subfield indicator | | | | | | | | +| VCI value | | | | | | | | + +**Figure 3a/Q.2767.1 – Soft PVC calling endpoint parameter field for ATM user** + +If the DLCI indicator and value exist in the Soft PVC parameter then the VPCI/VCI indicator and value is not needed, i.e. the two subfield parameters are mutually exclusive and only one of the two subfields can exist at one time. Currently the soft PVC calling endpoint is coded as follows. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------|---------------------------------------|-----------------------------------|----------|---|---|---|-----------|----------| +| ext.
1 | Coding standard | | Reserved | | | | | | +| DLCI subfield indicator | | | | | | | | | +| ext.
0 | Spare
0 | DLCI
(Most significant 6 bits) | | | | | | (Note 1) | +| ext.
0/1 | DLCI
(2nd most significant 4 bits) | | | | 0 | 0 | 0 | | +| ext.
1 | DLCI
(3rd most significant 6 bits) | | | | | | Res.
0 | (Note 2) | +| ext.
0 | DLCI
(3rd most significant 7 bits) | | | | | | | (Note 3) | +| ext.
1 | DLCI
(4th most significant 6 bits) | | | | | | Res.
0 | (Note 3) | + +NOTE 1 – The DLCI is two, three or four octets (i.e. 10 or 16 or 23 bits respectively). The standard default length of the DLCI is two octets. The extension bit mechanism is used to indicate non-default length of the DLCI. + +NOTE 2 – This octet shall only be included when bilateral agreements between the nodes which are endpoints of the soft PVC allow a 3-octet DLCI (16 bits). + +NOTE 3 – These octets shall both be included only when bilateral agreements between the nodes which are endpoints of the soft PVC allow a 4-octet DLCI (23 bits). + +**Figure 3b/Q.2767.1 – Soft PVC calling endpoint parameter field for frame relay user** + +Subfields are coded as follows: + +#### a) *Subfield indicator* + +0000 0001 VPCI value + +0000 0010 VCI value + +0000 0011 DLCI value + +All other values reserved. + +#### b) *VPCI value* + +Two-octet value coded as in the Connection Element Identifier (see ITU-T Q.2763). + +#### c) *VCI value* + +Two-octet value coded as in the Connection Element Identifier (see ITU-T Q.2763). + +#### e) The DLCI value is coded as in ITU-T X.76 without the information element identifier. The default length of DLCI is two octets but can be extended by bilateral agreement to three or four octets (see ITU-T X.76 – Figure 10-18). + +# 6 Application process procedures + +## 6.1 Connection setup + +### 6.1.1 Calling endpoint exchange + +The request to set up soft PVC is transmitted from the management entity to the application process and the request includes an indication whether a soft PVC is a soft PVCC or soft PVPC. If the user of the soft PVC is a Frame Relay interface only soft PVCC can be requested from the management entity. + +The soft PVC calling endpoint exchange shall initiate connection establishment by generating a Set\_Up request primitive to B-ISUP, containing the Soft PVC called endpoint parameter. The Called + +Party Number shall contain the address corresponding to the soft PVC called endpoint. The Calling Party Number shall contain the address corresponding to the soft PVC calling endpoint. + +The use of soft PVC procedures is indicated by the inclusion of the Soft PVC called endpoint parameter. + +If the VPCI/VCI or DLCI at the destination must be conveyed to the soft PVC called endpoint exchange, then this information is also carried in the Soft PVC called endpoint parameter. In this case, the selection type field should be set to "required value" and the Soft PVC called endpoint parameter shall indicate the VPCI value in case of setup of a soft PVPC or the VPCI/VCI or DLCI value in case of setup of a soft PVCC, respectively. + +In the case where the VPCI/VCI or DLCI shall be determined by the soft PVC called endpoint exchange, the Soft PVC called endpoint parameter shall be included with the selection type set to "any value". In this case, neither VPCI/VCI nor DLCI shall be indicated. + +The Soft PVC calling endpoint parameter may be included on an optional basis. + +For a soft PVCC call, the normal procedures in ITU-T Q.2764 are used. For a soft PVPC call, the procedures in ITU-T Q.2766.1 are used. + +### **6.1.2 Intermediate national exchange** + +For a soft PVCC call, the intermediate national exchange shall use the normal procedures as in ITU-T Q.2764 in order to set up the connection. For a soft PVPC call, the intermediate national exchange shall use the procedures in ITU-T Q.2766.1 to set up the connection. The presence of the Soft PVC called endpoint parameter indicates that the call is supporting the soft PVC capability. + +### **6.1.3 Outgoing international exchange** + +For a soft PVCC call, the outgoing international exchange shall use the normal procedures as in Q.2764 in order to set up the connection. For a soft PVPC call, the outgoing international exchange shall use the procedures in Q.2766.1 to set up the connection. The presence of the Soft PVC called endpoint parameter indicates that the call is supporting the soft PVC capability. + +### **6.1.4 Intermediate international exchange** + +For a soft PVCC call, the intermediate international exchange shall use the normal procedures as in Q.2764 in order to set up the connection. For a soft PVPC call, the intermediate international exchange shall use the procedures in Q.2766.1 to set up the connection. The presence of the Soft PVC called endpoint parameter indicates that the call is supporting the soft PVC capability. + +If the soft PVC capability is not supported by the receiving network, the call shall be cleared with Cause No. 21 "call rejected". + +### **6.1.5 Incoming international exchange** + +For a soft PVCC call, the incoming international exchange shall use the normal procedures as in ITU-T Q.2764 in order to set up the connection. For a soft PVPC call, the incoming international exchange shall use the procedures in ITU-T Q.2766.1 to set up the connection. The presence of the Soft PVC called endpoint parameter indicates that the call is supporting the soft PVC capability. + +If the soft PVC capability is not supported by the receiving network, the call shall be cleared with Cause No. 21 "call rejected". + +### **6.1.6 Called endpoint exchange** + +The soft PVC called endpoint exchange shall terminate call setup without sending an indication to the user, since no signalling is required for the connection segment between the endpoint and user. + +If the selection type in the Soft PVC called endpoint parameter is set to "any value", the soft PVC called endpoint exchange shall select a pre-determined VPCI/VCI or DLCI. If the selection type in the Soft PVC called endpoint parameter is set to "required value", the VPCI/VCI or DLCI indicated in the Soft PVC called endpoint parameter is used to associate the call with a particular connection segment at the soft PVC called endpoint. + +The soft PVC called endpoint exchange shall verify the authorization for the call based on the Calling Party Number, the Called Party Number and the Soft PVC called endpoint parameter. If the information is not correct, the call shall be cleared with Cause No. 21 "call rejected". + +If the call type is incompatible with the terminating access (e.g. call setup for a soft PVPC attempting to connect to a soft PVCC access link), then the call shall be cleared with Cause No. 21 "call rejected". + +If the selection type in the Soft PVC called endpoint parameter is set to "any value" and the VPCI/VCI or DLCI is included, the call shall be cleared with Cause No. 111 "Protocol error, unspecified". + +If the VPCI/VCI (or DLCI) in the case of PVCC or VPCI in the case of PVPC is not available at the terminating access, the call shall be cleared with Cause No. 34 "No circuit/channel available". + +## **6.2 Answer** + +### **6.2.1 Called endpoint exchange** + +Upon successful completion of call setup of the soft PVC, the soft PVC called endpoint exchange shall send the Answer request primitive back towards the soft PVC calling endpoint exchange. The Soft PVC called endpoint parameter shall be included in the Answer request primitive, with the indication of the VPCI in case of soft PVPC setup or VPCI/VCI (or DLCI) in case of soft PVCC setup, respectively, used at the soft PVC called endpoint. The selection type field shall be set to "assigned value". + +### **6.2.2 Calling endpoint exchange** + +Upon receiving the Answer indication primitive, the soft PVC calling endpoint exchange shall send an indication to management process. + +If the selection type in the Soft PVC called endpoint parameter is not set to "assigned value", then the call shall be cleared with Cause No. 111 "Protocol error, unspecified". + +### **6.2.3 Other types of exchanges** + +The procedures of ITU-T Q.2764 or Q.2766.1 apply. + +## **6.3 Unsuccessful connection setup** + +### **6.3.1 Calling endpoint exchange** + +The procedures of ITU-T Q.2764 or Q.2766.1 for the originating exchange apply with the following additions: + +If all attempts to reroute the connection fail, the exchange shall follow the procedures as described in 6.5.1. + +### **6.3.2 Other type of exchanges** + +The procedures of ITU-T Q.2764 or Q.2766.1 apply. + +## 6.4 Storage of call setup information + +The soft PVC calling endpoint exchange shall store the information of the IAM for as long as the soft PVCC or soft PVPC is offered to the customer. This allows re-establishment of the connection after failure. + +## 6.5 Release + +### 6.5.1 Release within the network + +In case of failure, the connection may be released by the detecting node in accordance with the procedures of ITU-T Q.2764 or Q.2766.1, as appropriate. + +Upon receipt of a first Release indication primitive (or Incoming Resources Rejected indication primitive), the soft PVC calling endpoint exchange shall send an indication to the management process, and depending on the cause value, may attempt to re-establish the connection immediately by using the call setup procedures as defined in 6.1 above. + +Upon receipt of the subsequent Release indication primitive (or Incoming Resources Rejected indication primitive), and if the maximum number of retries has not been reached, the exchange may, depending on the cause value, start the timer "Wait for Retry". The maximum number of retries is determined specifically for that soft PVC by the operator. If the maximum number of retries has been reached and the connection is not re-established or a specific cause value to stop the re-establishment is received, the exchange shall send another indication to the management process. + +When the timer "Wait for Retry" expires, the exchange shall attempt to re-establish the connection by using the call setup procedures defined in 6.1 above. + +### 6.5.2 Release by the calling endpoint exchange + +The soft PVC calling endpoint exchange may release the connection, based on a request from the management process. At this point, the calling endpoint exchange may release all information associated with the call. + +# 7 Application service elements and primitives + +The following clause identifies impacts on the B-ISUP Application Service Elements and the primitives exchanged between ASEs as shown in ITU-T Q.2764. + +## 7.1 Primitives between SACF and application process + +### 7.1.1 Set\_Up request/indication primitive + +Table 1 shows new parameters that must be added to the Set\_Up request/indication primitive. + +**Table 1/Q.2767.1 – Parameters for Set\_Up request/indication primitive** + +| Set_Up request/indication | B-ISDN | N-ISDN | +|------------------------------------------------------------------|----------|--------| +| Soft PVC called endpoint | O (Note) | – | +| Soft PVC calling endpoint | O | – | +| NOTE – This parameter is required for the setup of the soft PVC. | | | + +### 7.1.2 Answer request/indication primitive + +Table 2 shows new parameters that must be added to the Answer request/indication primitive. + +**Table 2/Q.2767.1 – Parameters for Answer request/indication primitive** + +| Answer request/indication | B-ISDN | N-ISDN | +|----------------------------------|---------------|---------------| +| Soft PVC called endpoint | O | – | + +## 7.2 Primitives between BCC ASE and SACF + +### 7.2.1 Link\_Set\_Up request/indication primitive + +Table 3 shows new parameters that must be added to the Link\_Set\_Up request/indication primitive. + +**Table 3/Q.2767.1 – Parameters for Link\_Set\_Up request/indication primitive** + +| Link_Set_Up request/indication | +|---------------------------------------| +| Soft PVC called endpoint | +| Soft PVC calling endpoint | + +### 7.2.2 Link\_Information request/indication primitive + +Table 4 shows new parameters that must be added to the Link\_Information request/indication primitive. + +**Table 4/Q.2767.1 – Parameters for Link\_Information request/indication primitive** + +| Link_Information request/indication | +|--------------------------------------------| +| Soft PVC called endpoint | + +## 7.3 ASE descriptions + +No changes are required to the ASE descriptions for BCC or CC ASEs. + +# 8 Instruction indicators and interworking + +## 8.1 Interworking with nodes not supporting this feature + +The instruction indicators shall be set so as to cause the call to be released at endpoint and gateway exchanges, but passed through transit exchanges. The instruction indicators for the Soft PVC called endpoint parameter, as shown in Appendix I, shall be set to be passed through transit exchanges, and to cause release if pass on is not possible. + +As a network option, the instruction indicators for the Soft PVC called endpoint parameter can be set to be released at transit exchanges. + +## **8.2 Interworking with DSS2** + +There is no interworking with DSS2, since there is no signalling required for the connection segment between the endpoint and user. + +## **8.3 Interworking with narrow-band ISDN** + +There is no interworking with narrow-band ISDN, since soft PVC is not supported in narrow-band. The Soft PVC called endpoint parameter shall be set to cause release at the broadband/narrow-band interworking point. + +The instruction indicators for the Soft PVC called endpoint parameter shall be coded as shown in Appendix I. + +As a network option, the instruction indicators for the Soft PVC called endpoint parameter can be set to be released at transit exchanges. + +## **8.4 Interaction with other capabilities** + +### **8.4.1 Point-to-multipoint** + +The procedures of ITU-T Q.2722.1 can be used with the soft PVCC. + +### **8.4.2 Traffic parameters** + +All the procedures specified for the traffic parameters in ITU-T Q.2764 and Q.2766 can be used for soft PVCC and soft PVPC. + +### **8.4.3 Look-ahead** + +The procedures of ITU-T Q.2724.1 can be used with the soft PVCC and soft PVPC. + +### **8.4.4 Negotiation of traffic characteristics during call setup** + +The procedures of ITU-T Q.2764 can be used with the soft PVCC and soft PVPC. + +### **8.4.5 Modification of traffic characteristics during the active phase of the call** + +The procedures of ITU-T Q.2764 can be used with the soft PVCC and soft PVPC. + +### **8.4.6 ATM End System Address (AESA)** + +The procedures of ITU-T Q.2764 can be used with the soft PVCC and soft PVPC. + +### **8.4.7 Call priority** + +The procedures of ITU-T Q.2726.2 can be used with the soft PVCC and soft PVPC. + +### **8.4.8 Network generated session ID** + +The procedures of ITU-T Q.2726.3 can be used with the soft PVCC and soft PVPC. + +### **8.4.9 Frame relay** + +A Frame Relay user of the soft PVCC is supported in this Recommendation. The interworking of a Frame Relay network with the soft PVC is for further study. + +## **8.5 Interworking with the first release of soft PVC – ITU-T Q.2767.1 (05/98)** + +If the information (i.e. the DLCI) is not recognized by the terminating exchange, the call shall be treated according to the procedure specified in ITU-T Q.2764 for unrecognized information parameter. + +If the call type is incompatible with the terminating access (e.g. call setup for a FR endpoint to connect to an ATM device), then the call shall be cleared with Cause No. 21 "call rejected". This should not occur under normal conditions and therefore can only occur under error conditions. + +# 9 Timers + +This clause specifies the additional Application Process timer relevant for B-ISUP. For the timer, the timeout value, cause for initiation of that timer, normal termination event(s) for the timer, and actions to be performed on expiry of the timer, are given in Table 5. 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. + +**Table 5/Q.2767.1 – Additional timer in B-ISUP** + +| Symbol (name) | Timeout value | Cause for initiation | Normal termination | At expiry | Reference | +|-----------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------------|-----------| +| Wait for Retry (T44b) | 0-? (Note) | If the (re-)establishment of a soft PVC fails and when a Release or IAM reject message is received in a soft PVC calling endpoint exchange | – | Re-establish the soft PVC | 6.5.1 | + +NOTE – Operator dependent. + +# APPENDIX I + +## Setting of instruction indicators + +The setting of the instruction indicators for the Soft PVC called endpoint parameter and Soft PVC calling endpoint parameter is as described in Table I.1. + +**Table I.1/Q.2767.1 – Coding of the instruction indicators** + +| Parameter | Soft PVC called endpoint | Soft PVC calling endpoint | +|-----------------------------------------|------------------------------------|------------------------------------| +| Pass on not possible ind. | Release call | Release call | +| Discard parameter ind. | Default | Default | +| Discard message ind. | Default | Default | +| Send notification ind. | Default | Default | +| Release call ind. | Release call | Release call | +| Transit at intermed. exchange ind. | Transit node interpretation (Note) | Transit node interpretation (Note) | +| Broadband/narrow-band interworking ind. | Release call | Release call | + +NOTE – As a network option, the transit at intermediate exchange indication can be set to "End node interpretation". + +# APPENDIX II + +## Retry decision + +A different decision may be required, if the failure is during: + +- *activation* + - the soft PVC was not active before, so a configuration error is quite possible; + - the operator is waiting for an answer: if the problem is no configuration error after all, or if the operator wants to retry anyway, the operator can do the retry; or +- *re-establishment* + - the soft PVC was active before, so a configuration error is not likely (but possible); + - the operator is not "handling" the soft PVC, so the node should retry. + +Taking this into account, the following guidelines can be established to decide on a retry during: + +- *activation* + +Retry if: + + - unexpected cause value (→assume that this is caused by a temporary failure); + - cause indicates a temporary failure. + +Do **not** retry if: + + - cause possibly indicates a configuration problem; + - cause indicates a "long term" failure. +- *re-establishment* + +Retry if: + + - unexpected cause (→assume that this is caused by a temporary failure); + - cause indicates a temporary failure; + - cause *possibly* indicates a configuration problem. + +Do **not** retry if: + + - cause *certainly* indicates a configuration error; + - cause indicates a "long term" failure. + +For all undefined (reserved) cause values, the action is according to the "Unspecified" value within the class. See Table II.1. + +**Table II.1/Q.2767.1 – Retry decision on cause value** + +| Value No. | Cause | Retry activation (Y/N) | Retry Re-establish. (Y/N) | Remarks | +|------------------|------------------------------------------------------------|-------------------------------|----------------------------------|--------------------------------------------------------------------| +| 001 | Unallocated (unassigned) number | N | N | Configuration error: wrong destination DN | +| 002 | No route to specified transit network | N | Y | Temporary routing problem, Routing configuration error | +| 003 | No route to destination | N | Y | Temporary routing problem, Routing configuration error | +| 004 | Send special information tone | Y | Y | Not expected (not activated in soft PVC set-up) | +| 005 | Misdialled trunk prefix | N | N | Configuration error: wrong destination DN | +| 006 | Channel unacceptable | Y | Y | Not expected (ISDN channels) | +| 007 | Call awarded and being delivered in an established channel | Y | Y | Not expected (ISDN channels) | +| 008 | Pre-emption | Y | Y | Temporary resource problem | +| 009 | Pre-emption – circuit reserved for reuse | Y | Y | Temporary resource problem | +| 010 | | Y | Y | reserved value: not expected, retry anyway | +| 011 | | Y | Y | reserved value: not expected, retry anyway | +| 012 | | Y | Y | reserved value: not expected, retry anyway | +| 013 | | Y | Y | reserved value: not expected, retry anyway | +| 014 | | Y | Y | reserved value: not expected, retry anyway | +| 015 | | Y | Y | reserved value: not expected, retry anyway | +| 016 | Normal call clearing | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | +| 017 | User busy | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | +| 018 | No user responding | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | +| 019 | No answer from user | N | Y | Temporary problem,
Configuration error (wrong destination DN) | +| 020 | Subscriber absent | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | + +**Table II.1/Q.2767.1 – Retry decision on cause value (continued)** + +| Value No. | Cause | Retry activation (Y/N) | Retry Re-establish. (Y/N) | Remarks | +|------------------|------------------------------------------------|-------------------------------|----------------------------------|------------------------------------------------------------------------------------| +| 021 | Call rejected | N | N | soft PVC capability is not supported by the receiving network | +| 022 | Number changed | N | N | Configuration changed on B-side | +| 023 | | Y | Y | reserved value: not expected, retry anyway | +| 024 | | Y | Y | reserved value: not expected, retry anyway | +| 025 | | Y | Y | reserved value: not expected, retry anyway | +| 026 | Non-selected user clearing | Y | Y | Not expected (for multipoint terminal only) | +| 027 | Destination out of order | N | Y | Temporary problem with soft PVC B-side, Configuration error (wrong destination DN) | +| 028 | Invalid number format (address incomplete) | N | N | Configuration error: wrong destination DN | +| 029 | Facility rejected | N | N | Configuration error: supplementary service not supported | +| 030 | Response to STATUS ENQUIRY | Y | Y | Not expected (response on status inquiry) | +| 031 | Normal, unspecified | Y | Y | Unspecified | +| 032 | | Y | Y | reserved value: not expected, retry anyway | +| 033 | | Y | Y | reserved value: not expected, retry anyway | +| 034 | No circuit/channel available | N | Y | VPCI/VCI respectively VPCI is not available at the terminating access | +| 035 | Requested VPCI/VCI not available | Y | Y | Glare case with SVC: always retry ! | +| 036 | VPCI/VCI assignment failure | Y | Y | Glare case with SVC: always retry ! | +| 037 | User cell rate not available | Y | Y | Glare case with SVC: always retry ! | +| 038 | Network out of order | N | N | Long-term problem with the network | +| 039 | Permanent frame mode connection out of service | Y | Y | Not expected (response on status inquiry) | +| 040 | Permanent frame mode connection operational | Y | Y | Not expected (response on status inquiry) | +| 041 | Temporary failure | Y | Y | Temporary failure | +| 042 | Switching equipment congestion | N | N | Retry would only increase the problem ... | + +**Table II.1/Q.2767.1 – Retry decision on cause value (continued)** + +| Value No. | Cause | Retry activation (Y/N) | Retry Re-establish. (Y/N) | Remarks | +|------------------|------------------------------------------------------------------------------|-------------------------------|----------------------------------|------------------------------------------------------------------------------| +| 043 | Access information discarded | N | Y | Configuration error: wrong DN, error returned by non-soft PVC user | +| 044 | Requested circuit/channel not available | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | +| 045 | No VPCI/VCI available | Y | Y | Temporary resource problem | +| 046 | Precedence call blocked | Y | Y | Temporary resource problem | +| 047 | Resource unavailable, unspecified | Y | Y | Unspecified | +| 048 | | N | Y | reserved value: not expected, retry anyway | +| 049 | Quality of service unavailable | N | N | Configuration error: QOS | +| 050 | Requested Facility not subscribed | N | N | Configuration error: soft PVC uses service which is not subscribed | +| 051 | | N | Y | reserved value: not expected, retry anyway | +| 052 | | N | Y | reserved value: not expected, retry anyway | +| 053 | Outgoing calls barred within CUG | N | N | Configuration error: default CUG should allow soft PVC | +| 054 | | N | Y | reserved value: not expected, retry anyway | +| 055 | Incoming calls barred within CUG | N | N | Configuration error: default CUG should allow soft PVC | +| 056 | | N | Y | reserved value: not expected, retry anyway | +| 057 | Bearer capability not authorized | N | N | Configuration error: soft PVC uses bearer capability which is not subscribed | +| 058 | Bearer capability not presently available | Y | Y | Temporary resource problem: bearer capability presently not available | +| 059 | | N | Y | reserved value: not expected, retry anyway | +| 060 | | N | Y | reserved value: not expected, retry anyway | +| 061 | | N | Y | reserved value: not expected, retry anyway | +| 062 | Inconsistency in designated outgoing access information and subscriber class | N | N | Configuration error: CUG inconsistency | +| 063 | Service or option not available, unspecified | N | Y | Unspecified problem, Configuration problem | + +**Table II.1/Q.2767.1 – Retry decision on cause value (continued)** + +| Value No. | Cause | Retry activation (Y/N) | Retry Re-establish. (Y/N) | Remarks | +|------------------|--------------------------------------------------------------------|-------------------------------|----------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| 064 | | N | N | reserved value: not expected, do not retry | +| 065 | Bearer capability not implemented | N | N | Configuration error: wrong DN, error returned by non-soft PVC user
Persistent error: not supported by transit switch | +| 066 | Channel type not implemented | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | +| 067 | | N | N | reserved value: not expected, do not retry | +| 068 | | N | N | reserved value: not expected, do not retry | +| 069 | Requested facility not implemented | N | N | Configuration error: wrong DN, error returned by non-soft PVC user,
Persistent error: not supported by transit switch | +| 070 | Only restricted digital information bearer capability is available | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | +| 071 | | N | N | reserved value: not expected, do not retry | +| 072 | | N | N | reserved value: not expected, do not retry | +| 073 | Unsupported combination of traffic parameters | N | N | Configuration error: not supported traffic parameters,
Persistent error: not supported by transit switch | +| 074 | | N | N | reserved value: not expected, do not retry | +| 075 | | N | N | reserved value: not expected, do not retry | +| 076 | | N | N | reserved value: not expected, do not retry | +| 077 | | N | N | reserved value: not expected, do not retry | +| 078 | | N | N | reserved value: not expected, do not retry | +| 079 | Service or option not implemented, unspecified | N | N | Configuration error: wrong DN, error returned by non-soft PVC user
Persistent error: not supported by transit switch | +| 080 | | Y | Y | reserved value: not expected, retry anyway | +| 081 | Invalid call reference value | Y | Y | Temporary error | +| 082 | Identified channel does not exist | Y | Y | Temporary error | + +**Table II.1/Q.2767.1 – Retry decision on cause value (continued)** + +| Value No. | Cause | Retry activation (Y/N) | Retry Re-establish. (Y/N) | Remarks | +|------------------|----------------------------------------------------------------------------------------|-------------------------------|----------------------------------|----------------------------------------------------------------------------------------| +| 083 | A suspended call exits, but this call identity does not | Y | Y | Temporary error | +| 084 | Call identity in use | Y | Y | Temporary error | +| 085 | No call suspended | Y | Y | Temporary error | +| 086 | Call having the requested call identity has been cleared | Y | Y | Temporary error | +| 087 | User not member of CUG | N | N | Configuration error: default CUG should allow soft PVC | +| 088 | Incompatible destination | N | N | Configuration error: wrong DN, error returned by non-soft PVC user | +| 089 | | Y | Y | reserved value: not expected, retry anyway | +| 090 | Non-existent CUG | N | N | Configuration error: default CUG should allow soft PVC | +| 091 | Invalid transit network selection | N | N | Configuration error: wrong destination DN | +| 092 | | Y | Y | reserved value: not expected, retry anyway | +| 093 | AAL parameters cannot be supported | N | N | Configuration error: wrong DN or CES parameter | +| 094 | | Y | Y | reserved value: not expected, retry anyway | +| 095 | Invalid message unspecified | Y | Y | Temporary error | +| 096 | Mandatory Information element is missing | Y | Y | Temporary error | +| 097 | Message type non-existent or not implemented | N | Y | Temporary error, Incompatible transit switch, Configuration error: non-soft PVC B-side | +| 098 | Message not compatible with call state or message type non-existent or not implemented | N | Y | Temporary error, Configuration error: non-soft PVC B-side | +| 099 | Information element/parameter non-existent or not implemented | N | Y | Temporary error, Incompatible transit switch, Configuration error: non-soft PVC B-side | +| 100 | Invalid information element contents | Y | Y | Temporary error | +| 101 | Message not compatible with call state | Y | Y | Temporary error | + +**Table II.1/Q.2767.1 – Retry decision on cause value (continued)** + +| Value No. | Cause | Retry activation (Y/N) | Retry Re-establish. (Y/N) | Remarks | +|------------------|------------------------------------------------------|-------------------------------|----------------------------------|--------------------------------------------| +| 102 | Recovery on timer expiry | Y | Y | Temporary error | +| 103 | Parameter non-existent or not implemented, passed on | Y | Y | Not expected | +| 104 | | Y | Y | reserved value: not expected, retry anyway | +| 105 | | Y | Y | reserved value: not expected, retry anyway | +| 106 | | Y | Y | reserved value: not expected, retry anyway | +| 107 | | Y | Y | reserved value: not expected, retry anyway | +| 108 | | Y | Y | reserved value: not expected, retry anyway | +| 109 | | Y | Y | reserved value: not expected, retry anyway | +| 110 | Message with unrecognized parameter, discarded | Y | Y | Not expected | +| 111 | Protocol error, unspecified | Y | Y | Temporary error | +| 112 | | Y | Y | reserved value: not expected, retry anyway | +| 113 | | Y | Y | reserved value: not expected, retry anyway | +| 114 | | Y | Y | reserved value: not expected, retry anyway | +| 115 | | Y | Y | reserved value: not expected, retry anyway | +| 116 | | Y | Y | reserved value: not expected, retry anyway | +| 117 | | Y | Y | reserved value: not expected, retry anyway | +| 118 | | Y | Y | reserved value: not expected, retry anyway | +| 119 | | Y | Y | reserved value: not expected, retry anyway | +| 120 | | Y | Y | reserved value: not expected, retry anyway | +| 121 | | Y | Y | reserved value: not expected, retry anyway | +| 122 | | Y | Y | reserved value: not expected, retry anyway | +| 123 | | Y | Y | reserved value: not expected, retry anyway | + +**Table II.1/Q.2767.1 – Retry decision on cause value (*concluded*)** + +| Value No. | Cause | Retry activation (Y/N) | Retry Re-establish. (Y/N) | Remarks | +|------------------|---------------------------|-------------------------------|----------------------------------|--------------------------------------------| +| 124 | | Y | Y | reserved value: not expected, retry anyway | +| 125 | | Y | Y | reserved value: not expected, retry anyway | +| 126 | | Y | Y | reserved value: not expected, retry anyway | +| 127 | Interworking, unspecified | Y | Y | unknown problem ... | + +# **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.2932.1-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1cb5ae85e67f1854896b92e23b53aec4333183b0 --- /dev/null +++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/raw.md @@ -0,0 +1,3791 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.2932.1** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/96) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +Digital Subscriber Signalling System No. 2 – +Generic functional protocol: + +**Core functions** + +ITU-T Recommendation Q.2932.1 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATION OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| General aspects | Q.2000–Q.2099 | +| ATM adaptation layer | Q.2100–Q.2199 | +| Signalling network protocols | Q.2200–Q.2599 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 | +| B-ISDN application protocols of the network | Q.2700–Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +## **ITU-T RECOMMENDATION Q.2932.1** + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 2 – GENERIC FUNCTIONAL PROTOCOL: CORE FUNCTIONS** + +## **Summary** + +This Recommendation defines the operation of the Digital Subscriber Signalling System Number 2 (DSS 2) for Generic Functional Protocol core functions at the $T_B$ or at the coincident $S_B$ and $T_B$ reference point of the User to Network Interface of the Broadband-Integrated Services Digital Network (B-ISDN). The Generic Functional Protocol core functions defined in this Recommendation provide a means of exchanging ROSE components on behalf of signalling application in peer entities. These signalling applications may either be for the support of supplementary services or provide protocol support for the other features (such as Look Ahead, Status request, Local/remote interrogation), in association with existing calls and bearers (bearer related signalling), or independently of existing bearers (connection-oriented or connectionless bearer independent signalling). + +## **Source** + +ITU-T Recommendation Q.2932.1 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996. + +# 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 Scope..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 3 | +| 4 Abbreviations..... | 5 | +| 5 Description..... | 6 | +| 5.1 Overview..... | 6 | +| 5.1.1 Local information exchange ..... | 6 | +| 5.1.2 Non-local information exchange ..... | 6 | +| 5.2 Protocol architecture ..... | 6 | +| 5.3 Application of the protocol model to local information exchange ..... | 8 | +| 5.4 Services provided by individual protocol entities..... | 8 | +| 5.4.1 Services provided by ROSE ..... | 8 | +| 5.4.2 Services provided by GFT-control ..... | 8 | +| 5.4.3 Services provided by bearer-related transport..... | 9 | +| 5.4.4 Services provided by connectionless bearer-independent transport..... | 9 | +| 5.4.5 Services provided by connection-oriented bearer-independent transport..... | 9 | +| 6 Operational requirements..... | 9 | +| 6.1 Provision and withdrawal ..... | 9 | +| 6.2 Requirements on the originating network side ..... | 10 | +| 6.3 Requirements on the destination network side ..... | 10 | +| 7 Primitive definitions and state definitions ..... | 10 | +| 7.1 Primitive definitions ..... | 10 | +| 7.2 State definitions ..... | 12 | +| 7.2.1 APDU transport mechanisms ..... | 12 | +| 7.2.2 GFT-Control ..... | 13 | +| 8 Coding requirements..... | 14 | +| 8.1 Message functional definitions and content..... | 14 | +| 8.1.1 Additional messages for bearer-related transactions ..... | 14 | +| 8.1.2 Messages for connectionless bearer-independent transport..... | 15 | +| 8.1.3 Messages for connection-oriented bearer-independent transport..... | 15 | +| 8.2 General message format and information element coding..... | 18 | +| 8.2.1 Message type..... | 18 | +| 8.2.2 Other information elements ..... | 19 | +| | Page | + +| | | | +|--------|-------------------------------------------------------------------------------------------------------------|-------------| +| 9 | Signalling procedures at the coincident S B and T B reference point ..... | 21 | +| 9.1 | APDU transport mechanisms..... | 21 | +| 9.1.1 | Bearer-related transport ..... | 21 | +| 9.1.2 | Bearer-independent transport mechanisms..... | 23 | +| 9.1.3 | Connection-oriented bearer-independent transport mechanism ..... | 23 | +| 9.1.4 | Connectionless bearer-independent transport mechanism..... | 26 | +| 9.2 | Addressing of APDUs..... | 27 | +| 9.2.1 | Local addressing ..... | 27 | +| 9.2.2 | Additional transport procedures where the multiple subscriber number
supplementary service applies ..... | 28 | +| 9.2.3 | Additional transport procedures where the subaddressing supplementary
service applies..... | 29 | +| 9.3 | GFT-Control ..... | 29 | +| 9.3.1 | Transmission of generic functional data..... | 29 | +| 9.3.2 | Receipt of generic functional data ..... | 30 | +| 9.4 | Remote operations procedures..... | 30 | +| 9.4.1 | Introduction..... | 30 | +| 9.4.2 | Procedures for operations ..... | 31 | +| 10 | Procedures for interworking with private ISDNs ..... | 34 | +| 10.1 | APDU transport mechanisms..... | 34 | +| 10.1.1 | Bearer-related transport ..... | 34 | +| 10.1.2 | Bearer-independent transport mechanisms..... | 34 | +| 10.1.3 | Connection-oriented bearer-independent transport mechanism ..... | 34 | +| 10.1.4 | Connectionless bearer-independent transport mechanism..... | 34 | +| 10.2 | Addressing of APDUs..... | 34 | +| 10.3 | GFT-Control ..... | 34 | +| 10.4 | Generic functional protocol ..... | 34 | +| 11 | Interactions with other networks..... | 34 | +| 11.1 | Interworking with N-ISDNs..... | 35 | +| 11.1.1 | Full termination of generic functional protocol..... | 35 | +| 11.1.2 | Generic interworking function..... | 36 | +| 11.2 | Interworking with non-ISDNs ..... | 39 | +| 11.3 | Interworking with frame-relay ..... | 39 | +| 11.4 | Interworking with PSPDNs..... | 39 | +| 12 | Parameter values ..... | 39 | +| 12.1 | Connection-oriented bearer-independent transport..... | 39 | +| | | Page | +| 13 | Dynamic description (SDLs) ..... | 40 | + +| | | | +|--------|--------------------------------------------------------------------------------------------------------|----| +| 13.1 | Block overview diagram..... | 40 | +| 13.2 | Coordination function..... | 41 | +| 13.3 | Component transport mechanisms..... | 41 | +| 13.3.1 | Bearer-related transport mechanism..... | 41 | +| 13.3.2 | Connection-oriented bearer-independent transport mechanism ..... | 41 | +| 13.3.3 | Connectionless bearer-independent transport mechanism..... | 41 | +| 13.4 | Generic functional transport control (GFT-Control) ..... | 41 | +| | Annex A – Formal definition of data types using Recommendation X.208 [6] ..... | 79 | +| A.1 | APDU types ..... | 79 | +| A.2 | Definition of Q.2931 information elements..... | 81 | +| | Annex B – Formal definition of data types using Recommendation X.680 [8]..... | 82 | +| B.1 | APDU types ..... | 82 | +| | Appendix I – Information flows..... | 86 | +| I.1 | Connection-oriented bearer-independent transport mechanism ..... | 86 | +| I.1.1 | Bearer independent establishment and data transfer..... | 86 | +| | Appendix II – Instruction indicators ..... | 87 | +| | Appendix III – Formal definitions of remote operations notation using
Recommendation X.208 [6]..... | 88 | +| | Appendix IV – Formal definitions of remote operations notation using
Recommendation X.680 [8]..... | 89 | +| | Appendix V – Assignment of object identifiers..... | 92 | + + + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 – GENERIC FUNCTIONAL PROTOCOL: CORE FUNCTIONS** + +*(Geneva, 1996)* + +# **1 Scope** + +This Recommendation specifies the functional protocol for the Broadband Integrated Services Digital Network (B-ISDN), using local information exchange, for the application to a range of additional basic call capabilities and supplementary services 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) protocol. + +The functional protocol is based on the use of the Facility information element. + +To be functional, this protocol requires knowledge of the additional basic call capabilities and supplementary services supported by the user equipment. This facilitates user equipment operation without human intervention by defining the semantics for the protocol elements which user equipment can process on its own. + +The procedures specified in this Recommendation can be used for: + +- activation and deactivation; +- invocation and operation; +- interrogation; +- status request; and +- status notification; + +of additional basic call capabilities and supplementary services in association with existing calls or outside any existing call. + +The application of this Recommendation to individual additional basic call capabilities and supplementary services is outside the scope of this Recommendation and is defined in those Recommendations which specify the individual capabilities. + +Further parts of this Recommendation cover the capabilities for non-local addressing within the generic functional protocol. + +All conformance to this Recommendation is based on the external behaviour at the interface at the $T_B$ or coincident $S_B$ and $T_B$ reference point, i.e. on the generation of the correct message structure and in the proper sequence as specified in this Recommendation. + +Further part(s) of this Recommendation specify the method of testing required to identify conformance to this Recommendation. + +This Recommendation is applicable to equipment, supporting additional basic call capabilities and supplementary services using the functional protocol, 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 ISDN. + +# 2 References + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent addition 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] CCITT Recommendation X.229 (1988), *Remote operations: Protocol specification*. +- [3] CCITT Recommendation X.219 (1988), *Remote operations: Model, notation and service definition*. +- [4] CCITT Recommendation Q.9 (1988), *Vocabulary of switching and signalling terms*. +- [5] ITU-T Recommendation I.112 (1993), *Vocabulary of terms for ISDNs*. +- [6] CCITT Recommendation X.208 (1988), *Specification of Abstract Syntax Notation One (ASN.1)*. +- [7] CCITT Recommendation X.209 (1988), *Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)*. +- [8] ITU-T Recommendation X.680 (1994), *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. +- [9] ITU-T Recommendation X.690 (1994), *Information technology – ASN.1 encoding rules; Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)*. +- [10] CCITT Recommendation I.210 (1988), *Principles of telecommunication services supported by an ISDN and the means to describe them*. +- [11] ITU-T Recommendation Q.2951.2 (1995), *Stage 3 description for number identification supplementary services using B-ISDN Digital Subscriber Signalling System No. 2 (DSS 2) – Basic call: Multiple Subscriber Number (MSN)*. +- [12] ITU-T Recommendation Q.2951.8 (1995), *Stage 3 description for number identification supplementary services using B-ISDN; Digital Subscriber Signalling System No. 2 (DSS 2) – Basic call: Sub-addressing (SUB)*. +- [13] ITU-T Recommendation Q.2931 (1995), *Broadband Integrated Services Digital Network (B-ISDN) – Digital Subscriber Signalling System No. 2 (DSS 2) – User-Network Interface (UNI) layer 3 specification for basic call/connection control*. +- [14] ITU-T Recommendation Q.2971 (1995), *Broadband Integrated Services Digital Network (B-ISDN) – Digital Subscriber Signalling System No. 2 (DSS 2) – User-network interface layer 3 specification for point-to-multipoint call/connection control*. +- [15] ITU-T Recommendation Q.2130 (1994), *B-ISDN ATM Adaptation layer-Service Specific Coordination Function (SSCF) for support of signalling at the User Network Interface (SSCF at UNI)*. +- [16] ITU-T Recommendation Z.100 (1993), *CCITT Specification and Description Language (SDL)*. + +[17] ITU-T Recommendation X.880 (1994), *Information technology – Remote operations: Concepts, model and notation*. + +# 3 Definitions + +This Recommendation makes use of the following terms defined in Recommendation X.219 [3]: + +- remote operation; +- operation; +- operation classes (class 1 to class 5); +- association (initiator; responder); +- invoking (application entity; invoker). + +For the purposes of this Recommendation, the following definitions apply: + +**3.1 application protocol data unit (APDU); component:** Data structure as defined in A.1. The term component that appears in Recommendations defining DSS 1 has an identical meaning. + +**3.2 bearer-independent control message:** A message as defined in 8.1.3, which on sending or receipt causes a change of the call/connection state at either the network or the user. + +**3.3 bearer-related transport mechanism:** A procedure tied to the procedures for basic call control and tied to a connection in progress, active or in the clearing phase. The call reference used by the basic call control procedure is adopted by the bearer-related service invocations to correlate with the appropriate basic call control transaction. + +**3.4 bearer-independent transport mechanism:** A procedure independent of the procedures for basic call control and not correlated to a connection. + +**3.5 call/connection control message:** A message as defined in 3.1/Q.2931 [13], which on sending or receipt causes a change of the call/connection state at either the network or the user. For a call that interworks with the Narrow-band ISDN (N-ISDN), a message as defined in 3.1/Q.2931 or 3.2/Q.2931 [13] which on sending or receipt causes a change of the call/connection state at either the network or the user. In this case, call/connection control messages also include the INFORMATION message and PROGRESS message. + +**3.6 call reference:** (Excluding dummy call reference) an identifier of a signalling transaction. The signalling transaction may either be bearer related, in which case the signalling transaction can be used to control that bearer, or bearer independent, in which case there is no bearer associated with that signalling transaction. Where there is only one bearer required for a call, then the call reference of the associated bearer-related signalling transaction may be used to identify the call. + +**3.7 call/connection state:** A state as defined in 2.1/Q.2931 [13] for either the user or the network as appropriate. For a call that interworks with the N-ISDN, a state as defined in 2.1/Q.2931 or 2.2/Q.2931 [13] for either the user or the network as appropriate. A call/connection state may exist for each call reference value [and for each additional responding Connection Endpoint Identifier (CEI) in the incoming call/connection states]. + +**3.8 call:** See 2.2/Q.9 [4], definition 2201. + +**3.9 connection:** See clause 0/Q.9 [4] definition 0011. In this Recommendation, the use of this term is taken to include a bearer and its associated control signalling. + +**3.10 connection-oriented transport mechanism:** A mechanism requiring the establishment of a signalling AAL connection and a transport association between the service requesting entity and the + +service provider. It provides a facility to access remote operations where success and/or failure reporting is required. It provides a call reference within the transport association as a means to associate uniquely among the related transport messages. + +**3.11 connectionless transport mechanism:** A mechanism where no transport association exists but a single transport message transfer is provided using the dummy call reference. + +**3.12 dummy call reference:** A null value indicating that the message is not applicable to an identified signalling transaction. Other rules specify the association of DSS 2 protocol entities. + +**3.13 functional protocol:** A functional protocol consists of a sequence of functional information elements. A functional information element requires a degree of intelligent processing by a terminal in either generation or analysis. + +**3.14 incoming network:** An incoming transport entity that is also a network, i.e. DSS 2 protocol entity at the network side of the interface. For bearer-related transport, the incoming network is also the destination network. + +**3.15 incoming transport entity:** An entity that responds to a peer entity initiating a transport mechanism. + +**3.16 incoming user:** An incoming transport entity that is also a user, i.e. DSS 2 protocol entity at the user side of the interface. For bearer-related transport, the incoming user is also the destination user. + +**3.17 initiator:** An entity (user or network) requesting establishment of a signalling connection between an initiator and the responder. + +**3.18 integrated Services Digital Network (ISDN):** See 2.3/I.112 [5], definition 308. + +**3.19 invoke APDU:** See 9.4.2.1. Where reference is made to an "xxxx" invoke APDU, an invoke APDU is meant with its operation value set to the value of the operation "xxxx". + +**3.20 local information exchange:** The exchange of generic functional data between ROSE or other ASEs which are located in the DSS 2 entities at either side of the access. + +**3.21 network:** The DSS 2 protocol entity at the network side of the user-network interface. + +**3.22 non-local information exchange:** The exchange of generic functional data between ROSE or other ASEs for which one, or other, or both, are not located in the DSS 2 entities at either side of the access. + +**3.23 outgoing network:** An outgoing transport entity that is also a network, i.e. DSS 2 protocol entity at the network side of the interface. For bearer-related transport, the outgoing network is also the originating network. + +**3.24 outgoing transport entity:** An entity that initiates a transport mechanism. + +**3.25 outgoing user:** An outgoing transport entity that is also a user, i.e. DSS 2 protocol entity at the user side of the interface. For bearer-related transport, the outgoing user is also the originating user. + +**3.26 party control message:** A message as defined in 8.1.2/Q.2971 [14], which on sending or receipt causes a change in party state at either the network or the user. + +**3.27 party state:** States for each party in the call (see 7.2.1/Q.2971 [14]) which are known at the interface. + +- 3.28 responder:** The entity (user or network) responding to a request from an initiator on establishing a signalling connection. +- 3.29 return result APDU:** See 9.4.2.2. Where reference is made to an "xxxx" return result APDU, a return result APDU is meant which is related to an "xxxx" invoke APDU. +- 3.30 return error APDU:** See 9.4.2.3. Where reference is made to an "xxxx" return error APDU, a return error APDU is meant which is related to an "xxxx" invoke APDU. +- 3.31 reject APDU:** See 9.4.2.4. +- 3.32 signalling AAL connection endpoint identifier; connection endpoint identifier (CEI):** Identifier used by a layer 3 protocol entity to address its peer entity. +- 3.33 signalling connection:** An association of DSS 2 protocol entities using the bearer-independent procedure with the connection-oriented transport mechanism. +- 3.34 supplementary service:** See 2.4/I.210 [10]. +- 3.35 user:** The DSS 2 protocol entity at the user side of the user-network interface. + +# 4 Abbreviations + +For the purposes of this Recommendation, the following abbreviations are used: + +| | | +|-------------|-------------------------------------------------| +| APDU | Application Protocol Data Unit | +| AS-Control | Application Service Control | +| ATM | Asynchronous Transfer Mode | +| BER | Basic Encoding Rules | +| B-ISDN | Broadband Integrated Services Digital Network | +| BR | Bearer Related | +| CL-BI | Connectionless Bearer Independent | +| CO-BI | Connection-Oriented Bearer Independent | +| DSS 1 | Digital Subscriber Signalling System No. 1 | +| DSS 2 | Digital Subscriber Signalling System No. 2 | +| GFT-Control | Generic Functional Transport Control | +| N-ISDN | Narrow-band Integrated Services Digital Network | +| NNI | Network Node Interface | +| ROSE | Remote Operations Service Element | +| SAAL | Signalling ATM Adaptation Layer | +| UNI | User-Network Interface | + +# 5 Description + +## 5.1 Overview + +The generic functional protocol provides a means of exchanging ROSE APDU on behalf of signalling applications in peer entities. These signalling applications may either be for the support of supplementary services, or provide protocol for the support of other functionality (e.g. look ahead). This exchange may take place either in association with a bearer established using DSS 2 procedures, or may be carried independently of any bearer. + +The exchange of ROSE APDU between signalling applications may be local or non-local to the user-network interface. + +### 5.1.1 Local information exchange + +If the exchange of information is local (i.e. one signalling application exists at the network and the peer signalling application exists at the user), no addressing information is required, unless there is a need to select from multiple signalling entities at the user side of the interface, e.g. as in the multiple subscriber number supplementary service. + +The exchange of information may be using any of: + +- a) bearer-related transport; +- b) connectionless bearer-independent transport; +- c) connection-oriented bearer-independent transport. + +This does not preclude a local exchange of information being used for the support of a signalling application on a more global basis; usage in this form is dependent on the specification of the individual signalling application itself. The exchange is local between a signalling application in the local network and a signalling application in the local user. As a result of receiving these APDUs, the signalling application in the local network may establish a signalling association with other signalling applications eventually incorporating the remote user. + +Non-local information exchange is outside the scope of this part of this Recommendation. Requirements for non-local information exchange will be covered in other parts of this Recommendation. + +### 5.1.2 Non-local information exchange + +If the exchange of information is non-local, then addressing information is required. This addressing information may be provided by using a value associated with a particular abstract functionality, or by explicitly using an ISDN number to identify the signalling endpoint. This non-local exchange could be entirely within the DSS 2 protocol (i.e. across a single exchange between two user-network interfaces). A more common occurrence will be to map this mechanism in DSS 2 into equivalent functionality within either broadband private network signalling protocols, or into TCAP protocol associated with the broadband NNI protocol. + +## 5.2 Protocol architecture + +Figure 1 shows the conceptual model for the generic functional protocol and its relation to the basic call model defined in Recommendation Q.2931 [13]. + +At the top layer (the signalling application layer) the actual supplementary service protocol, or other signalling application protocol, operates between peer Application Service Control (AS-Control) + +entities which are service specific. The operation of specific AS-Control entities is beyond the scope of this Recommendation. + +AS-Control entities use the services of the Remote Operations Service Element (ROSE) via the coordination function. These entities use the services of the Generic Functional Transport Control (GFT-Control) via the coordination function. + +The coordination function provides coordination between GFT-Control (and the individual transport functions controlled by GFT-Control), the various AS-Control entities and ROSE, in addition to the functions performed for basic call. + +The provision and application of this model is for the purpose of description within this Recommendation, and is expected only to constrain implementations in terms of provision of the protocol on the access. Implementations are free to use any internal architecture providing the requirements of the protocol are met. + +![Diagram of the DSS 2 protocol model showing the Coordination function at the center, connected to a Telecommunication service application above, and SAAL-UNI below. To the right of the Coordination function are AS-Control #1, AS-Control #n, ROSE, GFT-Control, CL-BI, CO-BI, and point-to-point call/connection (Note).](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram illustrates the DSS 2 protocol model. At the top is a box labeled 'Telecommunication service application'. Below it is a large vertical box labeled 'Coordination function'. At the bottom is a box labeled 'SAAL-UNI'. To the right of the 'Coordination function' box, there are several smaller boxes stacked vertically: 'AS-Control #1', a vertical ellipsis, 'AS-Control #n', 'ROSE', 'GFT-Control', 'CL-BI', 'CO-BI', and 'point-to-point call/connection (Note)'. Double-headed arrows connect the 'Telecommunication service application' to the 'Coordination function', the 'Coordination function' to the 'SAAL-UNI', and each of the boxes on the right to the 'Coordination function'. A small arrow points left from the 'SAAL-UNI' box. The text 'T1179540-96' is located to the right of the 'SAAL-UNI' box. + +Diagram of the DSS 2 protocol model showing the Coordination function at the center, connected to a Telecommunication service application above, and SAAL-UNI below. To the right of the Coordination function are AS-Control #1, AS-Control #n, ROSE, GFT-Control, CL-BI, CO-BI, and point-to-point call/connection (Note). + +NOTE – Call/connection control is included for the transport of bearer-related information. Although only the point-to-point call/connection control described in Recommendation Q.2931 [13] is shown, the point-to-multipoint call/connection control described in Recommendation Q.2971 [14] is also applicable. + +FIGURE 1/Q.2932.1 + +**DSS 2 protocol model, including additions for generic functional protocol** + +## 5.3 Application of the protocol model to local information exchange + +Figure 1 shows an example of the flow of information in the protocol model for the case where the signalling applications to be associated in communication are in adjacent nodes, e.g. between a DSS 2 user and a DSS 2 network using the CO-BI transport mechanism. Other transport mechanisms could be used as described in 5.1.1. + +![Diagram illustrating the flow of information in the protocol model for local information exchange between a User node and a Network node. The diagram shows five stacked protocol entities: AS-Control, ROSE, GFT-Control, CO-BI, and SAAL-UNI. Vertical double-headed arrows connect adjacent entities within each node. Horizontal dashed double-headed arrows connect corresponding entities between the User node and the Network node. A 'Coordination function' is indicated by a dashed box surrounding the AS-Control, ROSE, GFT-Control, and CO-BI entities in both nodes. The SAAL-UNI entities are outside this box. A small label 'T1179550-96' is present in the bottom right corner of the diagram area.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +T1179550-96 + +Diagram illustrating the flow of information in the protocol model for local information exchange between a User node and a Network node. The diagram shows five stacked protocol entities: AS-Control, ROSE, GFT-Control, CO-BI, and SAAL-UNI. Vertical double-headed arrows connect adjacent entities within each node. Horizontal dashed double-headed arrows connect corresponding entities between the User node and the Network node. A 'Coordination function' is indicated by a dashed box surrounding the AS-Control, ROSE, GFT-Control, and CO-BI entities in both nodes. The SAAL-UNI entities are outside this box. A small label 'T1179550-96' is present in the bottom right corner of the diagram area. + +FIGURE 2/Q.2932.1 + +### Application of the protocol mode to local information exchange + +## 5.4 Services provided by individual protocol entities + +### 5.4.1 Services provided by ROSE + +ROSE provides a set of services to AS-Control to support the ROSE protocol. These services are specified in Recommendation X.219 [3]. + +### 5.4.2 Services provided by GFT-control + +This entity provides the following services to AS-Control and ROSE via the coordination function: + +- a) *Bearer-related service* + - GFT-Setup: request for the transfer of data in the bearer establishment phase. This service is a confirmed service; + - GFT-Release: request for the transfer of data in the bearer release phase. This service is a confirmed service; + - GFT-Reject: rejection of the ability to use a transport mechanism. This service is an unconfirmed service; + - GFT-Data: request for the transfer of data in active phase of a bearer. This service is an unconfirmed service. +- b) *Connectionless bearer-independent service* + +- GFT-Unit Data: request for the transfer of data. This service is an unconfirmed service. +- c) *Connection-oriented bearer-independent service* +- GFT-Setup: request for the establishment of a bearer-independent signalling association (with data transfer if required). This service is a confirmed service; + - GFT-Release: request for the release of a bearer-independent signalling association (with data transfer if required). This service is a confirmed service; + - GFT-Reject: rejection of the ability to use a transport mechanism. This service is an unconfirmed service; + - GFT-Data: request for the transfer of data in active phase of a bearer-independent signalling association. This service is an unconfirmed service. + +### 5.4.3 Services provided by bearer-related transport + +Any of the bearer-related procedures specified in Recommendations Q.2931 [13] and Q.2971 [14] can be used for bearer-related protocol control. As multiconnection protocol provides the bearer control using the procedures of Recommendation Q.2931 [13], no extra services are required for transport in relation to multiconnection calls. The services provided by these entities are specified in those. In addition, these services provide one additional service: + +- BR-Data: this service is an unconfirmed service. + +A notification service is already provided within Recommendations Q.2931 [13] and Q.2971 [14]. + +### 5.4.4 Services provided by connectionless bearer-independent transport + +Connectionless bearer-independent transport provides the following services to GFT-Control via the coordination function: + +- CL-BI-Unit Data: This service is an unconfirmed service. + +### 5.4.5 Services provided by connection-oriented bearer-independent transport + +Connection-oriented bearer-independent transport provides the following services to GFT-Control via the coordination function: + +- CO-BI-Setup: this service is a confirmed service; +- CO-BI-Release: this service is a confirmed service; +- CO-BI-Reject: this service is an unconfirmed service; +- CO-BI-Data: this service is an unconfirmed service. + +In addition, connection-oriented bearer-independent transport also supports a notification data transfer service as follows: + +- CO-BI-Notification: this service is an unconfirmed service. + +# 6 Operational requirements + +## 6.1 Provision and withdrawal + +There are no direct requirements for provision and withdrawal of capabilities within this Recommendation. Provision and withdrawal of applications using this Recommendation are specified in the Recommendations describing those applications. + +Support of options within this Recommendation is conditioned by Recommendations defining the use of this Recommendation. However, in particular: + +- support of each individual transport mechanism is optional, although at least one transport mechanism shall be supported; +- support of the requirements as presented by GFT-Control and as described in 9.3 is mandatory, although support of procedures associated with individual protocol profile values within the Facility information element is optional, and at least one value of protocol profile shall be supported; +- if the value of protocol profile "ROSE" is supported, then the procedures relating to ROSE shall also be supported; +- support of the use of the Called party number information element within the bearer-independent transport mechanisms is dependent on the support of the multiple subscriber number supplementary service; +- support of the use of the Called party subaddress information element within the bearer-independent transport mechanisms is dependent on the support of the subaddressing supplementary service; +- support of the use of the Calling party number information element within the bearer-independent transport mechanisms is dependent on the support of the multiple subscriber number supplementary service. + +## **6.2 Requirements on the originating network side** + +The requirements for provision of capabilities of this Recommendation are dependent on applications using this Recommendation. Capabilities in this Recommendation are therefore network and user options, but may become mandatory according to the requirements of other Recommendations. + +## **6.3 Requirements on the destination network side** + +The requirements for provision of capabilities of this Recommendation are dependent on applications using this Recommendation. Capabilities in this Recommendation are therefore network and user options, but may become mandatory according to the requirements of other Recommendations. + +# **7 Primitive definitions and state definitions** + +## **7.1 Primitive definitions** + +The following primitives are used as defined in 8.2/Q.2931 [13] subclause 8.2: + +- AAL\_ESTABLISH.request; +- AAL\_ESTABLISH.indication; +- AAL\_ESTABLISH.confirm; +- AAL\_RELEASE.request; +- AAL\_RELEASE.indication; +- AAL\_RELEASE.confirm; +- AAL\_DATA.request; +- AAL\_DATA.indication. + +All primitives use the AAL connection endpoint identifier to identify a particular signalling AAL connection. + +The following additional primitives are described for internal use within this Recommendation, in particular in order to describe the relationship between entities within the SDL specification: + +- a) between AS-Control and the coordination function: + +NOTE 1 – These primitives are dependent entirely on those defined in other Recommendations for the supplementary services or additional capabilities, but will reflect the requirements of ROSE and the need for notification from the transport mechanisms. + +- b) between ROSE and the coordination function: + +NOTE 2 – These primitives are defined in Recommendations X.219 [3] and X.880 [17]. + +- c) between GFT-Control and the coordination function: + +– signalroute CD\_to\_GF: + +GF\_Data.request; + +BR\_Data.indication; + +CO\_BI\_Data.indication; + +CL\_BI\_Unit\_Data.indication; + +NOTE 3 – In addition, the following primitives are dealt with by GFT-Control in order to manage the CO-BI transport mechanism but not explicitly described in the SDL: +CO\_BI\_Setup.indication; CO\_BI\_Proceeding.indication; CO\_BI\_Setup.confirm; +CO\_BI\_Release.indication; CO\_BI\_Release.confirm. + +– signalroute GF\_to\_CD: + +GF\_Data.indication; + +BR\_Data.request; + +CO\_BI\_Data.request; + +CL\_BI\_Unit\_Data.request; + +NOTE 4 – In addition, the following primitives are dealt with by GFT-Control in order to manage the CO-BI transport mechanism but not explicitly described in the SDL: +CO\_BI\_Setup.request; CO\_BI\_Proceeding.request; CO\_BI\_Setup.response; +CO\_BI\_Release.request. + +- d) between the connection-oriented bearer-independent transport mechanism (CO-bearer independent) and the coordination function: + +– signalroute CO\_to\_CD: + +CO\_BI\_Setup.indication; + +CO\_BI\_Proceeding.request; + +CO\_BI\_Setup.confirm; + +CO\_BI\_Data indication; + +CO\_BI\_Notify.indication; + +CO\_BI\_Release.indication; + +CO\_BI\_Release.confirm; + +Link\_Release.indication; + +Link\_Establish.error; + +Link\_Establish.indication; + +Link\_Establish.confirm; + +- signalroute CD\_to\_CO: + CO\_BI\_Setup.request; + CO\_BI\_Proceeding.indication; + CO\_BI\_Setup.response; + CO\_BI\_Data.request; + CO\_BI\_Notify.request; + CO\_BI\_Release.request; + Link\_Establish.request; +- e) between the connectionless bearer-independent transport mechanism (CL-bearer\_independent) and the coordination function: + - signalroute CD\_to\_CL: + CL\_BI\_Unit\_Data.request; + - signalroute CL\_to\_CD: + CL\_BI\_Unit\_Data.indication; +- f) between the bearer-related transport mechanism (Q.2931\_U) and the coordination function (in addition to those defined in Recommendations Q.2931 [13] and Q.2971 [14]): + - signalroute CD\_to\_QU: + BR\_Data.request; + - signalroute QU\_to\_CD: + BR\_Data.indication; +- g) between the bearer-related transport mechanism (Q.2931\_N) and the coordination function (in addition to those defined in Recommendations Q.2931 [13] and Q.2971 [14]): + - signalroute CD\_to\_QN: + BR\_Data.request; + - signalroute QN\_to\_CD: + BR\_Data.indication. + +## 7.2 State definitions + +### 7.2.1 APDU transport mechanisms + +#### 7.2.1.1 Bearer-related transport mechanism + +There are no additional call/connection states over and above those defined in Recommendation Q.2931 [13] or Recommendation Q.2971 [14]. + +#### 7.2.1.2 Connectionless bearer-independent transport mechanism + +This subclause defines the connectionless bearer-independent states for the B-ISDN generic functional protocol. The states are identical for the network and the user. + +##### 7.2.1.2.1 Null (0) (U0) (N0) + +A request for service has been received from GFT-Control, or a transport request has been received from the peer entity, but this request has not yet been acted upon. + +This state is defined for the purpose of the SDL defined in clause 13 and does not have any direct coding impact in the protocol. + +#### **7.2.1.3 Connection-oriented bearer-independent transport mechanism** + +This subclause defines the connection-oriented bearer-independent states for the B-ISDN generic functional protocol. The states are identical for the network and the user. + +##### **7.2.1.3.1 Null (0) (U0) (N0)** + +An establishment request for service has been received from GFT-Control, or an establishment request has been received from the peer-entity, but this request has not yet been acted upon. + +NOTE – This state will also be used by the coordination process in the absence of the CO-BI process indicated by the call reference. + +##### **7.2.1.3.2 Call Initiated (1) (U1) (N1)** + +This state exists for an outgoing transport establishment request when GFT-Control requests transport establishment from the peer entity. + +##### **7.2.1.3.3 Outgoing call proceeding (3) (U3) (N3)** + +This state exists for an outgoing transport establishment request when the transport entity has received acknowledgement that the peer entity has received all information necessary to effect transport establishment. + +##### **7.2.1.3.4 Call Present (6) (U6) (N6)** + +This state exists for an incoming transport establishment request where the transport entity has not yet sent acknowledgement that GFT-Control has received all the information necessary to effect transport establishment. + +##### **7.2.1.3.5 Incoming call proceeding (9) (U9) (N9)** + +This state exists for an incoming transport establishment request when the transport entity has sent acknowledgement that GFT-Control has received all information necessary to effect transport establishment. + +##### **7.2.1.3.6 Active (10) (U10) (N10)** + +This state exists for an incoming transport establishment request when the transport entity has sent an acknowledgement to the peer entity that the information transfer has been awarded. This state exists for an outgoing transport establishment request when the transport entity has received an indication that the remote entity has agreed to the information transfer. + +##### **7.2.1.3.7 Release Request (11) (U11) (N11)** + +This state exists when the transport entity has requested the peer entity to clear the transport and is waiting for a response. + +### **7.2.2 GFT-Control** + +The following state is defined for the purposes of the Specification and Description Language (SDL) defined in clause 13, and does not have any direct coding impact on the protocol: + +- Pending: GFT-Control has been activated and is in a state ready to process APDUs. + +# 8 Coding requirements + +## 8.1 Message functional definitions and content + +This subclause shall be read in conjunction with clause 3/Q.2931 [13]. All messages are additional to those defined in that clause and the following tables should be interpreted according to the introductory material of clause 3/Q.2931 [13]. + +In the following subclauses the key as described below applies to the "Reference" column. + +**Key:** Q.2931/nn: reference to subclause nn in Recommendation Q.2931 [13]; + Q.2932.1/nn: reference to subclause nn in this Recommendation. + +To determine if an information element specified in this Recommendation is allowed to be included in the following messages, see 8.2. + +Information elements not defined in 8.2 are only allowed to be included in the following messages when explicitly indicated in the message structure. + +### 8.1.1 Additional messages for bearer-related transactions + +In addition to the message structures defined below, the Facility information element may also be included in any call/connection control message or party control message, as defined in 8.2.2.2. + +#### 8.1.1.1 FACILITY + +This message may be sent by the network or the user to control a supplementary service or additional basic call capability. The supplementary service or additional basic call capability to be invoked, and its associated parameters, are specified in the Facility information element. The structure of the FACILITY message is shown in Table 1. + +TABLE 1/Q.2932.1 +**FACILITY message content** + +| Message type: FACILITY
Significance: local (Note 1)
Direction: both | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------|------------|--------| +| Information element | Reference | Direction | Type | Length | +| Protocol discriminator | Q.2931/4.2 | Both | M | 1 | +| Call reference (Note 2) | Q.2931/4.3 | Both | M | 4 | +| Message type | Q.2932.1/8.2.1 | Both | M | 2 | +| Message length | Q.2931/4.4 | Both | M | 2 | +| Facility | Q.2932.1/8.2.2.2 | Both | M (Note 4) | 10-* | +| Notification indicator | Q.2931/4.5.23 | Both | O (Note 3) | 4-* | +| NOTES
1 – This message has local significance; however it may carry information of global significance.
2 – For bearer-related transport, the value of the call reference used is the call reference of the call/connection to which the transported APDU is related.
3 – This indicator may be present whenever notification is delivered. The Notification indicator information element may be repeated in this message. The maximum length and the number of repetitions allowed is a network option.
4 – This information element may be repeated any number of times. | | | | | + +### 8.1.2 Messages for connectionless bearer-independent transport + +#### 8.1.2.1 FACILITY + +This message may be sent by the network or the user to control a supplementary service or additional basic call capability. The supplementary service or additional basic call capability to be invoked, and its associated parameters, are specified in the Facility information element. The structure of the FACILITY message is shown in Table 2. + +TABLE 2 +**FACILITY message content** + +| Message type: FACILITY | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------|------------|--------| +| Significance: local (Note 1) | | | | | +| Direction: both | | | | | +| Information element | Reference | Direction | Type | Length | +| Protocol discriminator | Q.2931/4.2 | Both | M | 1 | +| Call reference
(Note 2) | Q.2931/4.3 | Both | M | 4 | +| Message type | Q.2932.1/8.2.1 | Both | M | 2 | +| Message length | Q.2931/4.4 | Both | M | 2 | +| Facility | Q.2932.1/8.2.2.2 | Both | M (Note 7) | 10-* | +| Called party number | Q.2931/4.5.11 | n -> u | O (Note 3) | 4-* | +| Called party subaddress | Q.2931/4.5.12 | n -> u | O (Note 4) | 4-25 | +| Calling party number | Q.2931/4.5.13 | u -> n | O (Note 6) | 4-* | +| Notification indicator | Q.2931/4.5.23 | Both | O (Note 5) | 4-* | +| NOTES | | | | | +| 1 – This message has local significance; however it may carry information of global significance. | | | | | +| 2 – The dummy call reference is used. | | | | | +| 3 – Included when the transport mechanism user-entity wishes to address a particular entity at the user using Called party number information. Usage is dependent on provision of the multiple subscriber number supplementary service. It is only applicable at the coincident S B and T B reference point. | | | | | +| 4 – Included when the transport mechanism user-entity wishes to address a particular entity at the user using called party subaddress information. Usage is dependent on the provision of the subaddressing supplementary service. It is only applicable at the coincident S B and T B reference point. | | | | | +| 5 – This indicator may be present whenever notification is delivered. The notification indicator information element may be repeated in this message. The maximum length and the number of repetitions allowed is a network option. | | | | | +| 6 – Included when an entity at the user wishes to identify itself to the transport mechanism user-entity. Usage is dependent on provision of the multiple subscriber number supplementary service. It is only applicable at the coincident S B and T B reference point. | | | | | +| 7 – This information element may be repeated any number of times. | | | | | + +### 8.1.3 Messages for connection-oriented bearer-independent transport + +#### 8.1.3.1 CALL PROCEEDING + +This message is sent by the called user to the network, or by the network to the calling user, to indicate that the requested transport establishment has been initiated and that no more establishment information will be accepted. The structure of the CALL PROCEEDING message is shown in Table 3. + +TABLE 3/Q.2932.1 + +##### **CALL PROCEEDING message content** + +| Message type: CALL PROCEEDING
Significance: local
Direction: both | | | | | +|-------------------------------------------------------------------------|------------|-----------|------|--------| +| Information element | Reference | Direction | Type | Length | +| Protocol discriminator | Q.2931/4.2 | Both | M | 1 | +| Call reference | Q.2931/4.3 | Both | M | 4 | +| Message type | Q.2931/4.4 | Both | M | 2 | +| Message length | Q.2931/4.4 | Both | M | 2 | + +#### **8.1.3.2 CO-BI SETUP** + +This message is sent by the calling user to the network, and by the network to the called user, to initiate transport establishment. The structure of the CO-BI SETUP message is shown in Table 4. + +TABLE 1-4/Q.2932.1 + +##### **CO-BI SETUP message content** + +| Message type: CO-BI SETUP
Significance: local (Note 1)
Direction: both | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------|------------|--------| +| Information element | Reference | Direction | Type | Length | +| Protocol discriminator | Q.2931/4.2 | Both | M | 1 | +| Call reference | Q.2931/4.3 | Both | M | 4 | +| Message type | Q.2932.1/8.2.1 | Both | M | 2 | +| Message length | Q.2931/4.4 | Both | M | 2 | +| Facility | Q.2932.1/8.2.2.2 | Both | O (Note 2) | 4-* | +| Called party number | Q.2931/4.5.11 | n -> u | O (Note 3) | 4-* | +| Called party subaddress | Q.2931/4.5.12 | n -> u | O (Note 4) | 4-25 | +| Calling party number | Q.2931/4.5.13 | u -> n | O (Note 5) | 4-* | +| Notification indicator | Q.2931/4.5.23 | Both | O (Note 6) | 4-* | +| NOTES
1 – This message has local significance; however it may carry information of global significance.
2 – Included if the requesting GFT-Control wishes to include APDUs in the setup request. This information element may be repeated any number of times.
3 – Included in the network-to-user direction if a transport mechanism user-entity wishes to address a particular entity at the user using Called party number information, and it is a coincident S B and T B reference point, and the multiple subscriber number supplementary service is provided.
4 – Included in the network-to-user direction if a transport mechanism user-entity wishes to address a particular entity at the user using called party subaddress information, and it is a coincident S B and T B reference point, and the subaddressing supplementary service is provided.
5 – Included in the user-to-network direction if a user wishes to identify itself to a transport mechanism user-entity using Calling party number information, and it is a coincident S B and T B reference point, and the multiple subscriber number supplementary service is provided.
6 – This indicator may be present whenever notification is delivered. The Notification indicator information element may be repeated in this message. The maximum length and the number of repetitions allowed is a network option. | | | | | + +#### 8.1.3.3 CONNECT + +This message is sent by the called user to the network, and by the network to the calling user to indicate acceptance of a transport establishment request by the called entity. The structure of the CONNECT message is shown in Table 5. + +TABLE 5/Q.2932.1 + +##### CONNECT message content + +| Message type: CONNECT
Significance: local (Note 1)
Direction: both | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------|------------|--------| +| Information element | Reference | Direction | Type | Length | +| Protocol discriminator | Q.2931/4.2 | Both | M | 1 | +| Call reference | Q.2931/4.3 | Both | M | 4 | +| Message type | Q.2931/4.4 | Both | M | 2 | +| Message length | Q.2931/4.4 | Both | M | 2 | +| Facility | Q.2932.1/8.2.2.2 | Both | O (Note 2) | 4-* | +| Notification indicator | Q.2931/4.5.23 | Both | O (Note 3) | 4-* | +| NOTES
1 – This message has local significance; however it may carry information of global significance.
2 – Included if the responding GFT-Control wishes to include APDUs in the call setup response. This information element may be repeated any number of times.
3 – This indicator may be present whenever notification is delivered. The Notification indicator information element may be repeated in this message. The maximum length and the number of repetitions allowed is a network option. | | | | | + +#### 8.1.3.4 FACILITY + +This message may be sent by the network or the user to control a supplementary service or additional basic call capability. The supplementary service or additional basic call capability to be invoked, and its associated parameters, are specified in the Facility information element. The structure of the FACILITY message is the same as that shown in 8.1.1.1 (see Table 1). + +#### 8.1.3.5 NOTIFY + +This information is sent by the user or the network to indicate information pertaining to a call. The structure of the NOTIFY message is the same as that shown in 3.1.10/Q.2931 [13] (see Table 3-11/Q.2931). + +#### 8.1.3.6 RELEASE + +This message is sent by the transport entity to request clearing of the part of the end-to-end transport connection controlled by the peer transport entity and to prepare to release its call reference value after sending RELEASE COMPLETE. The structure of the RELEASE message is shown in Table 6. + +TABLE 6/Q.2932.1 + +##### **RELEASE message content** + +| Message type: RELEASE
Significance: local (Note 1)
Direction: both | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------|------------|--------| +| Information element | Reference | Direction | Type | Length | +| Protocol discriminator | Q.2931/4.2 | Both | M | 1 | +| Call reference | Q.2931/4.3 | Both | M | 4 | +| Message type | Q.2931/4.4 | Both | M | 2 | +| Message length | Q.2931/4.4 | Both | M | 2 | +| Cause | Q.2931/4.5.15 | Both | M (Note 2) | 6-34 | +| Facility | Q.2932/8.2.2.2 | Both | O (Note 3) | 4-* | +| Notification indicator | Q.2931/4.5.23 | Both | O (Note 4) | 4-* | +| NOTES
1 – This message has local significance; however it may carry information of global significance.
2 – This information element may appear twice in a message.
3 – Included if the releasing GFT-Control wishes to include APDUs in the Release Request. This information element may be repeated any number of times.
4 – This indicator may be present whenever notification is delivered. The Notification indicator information element may be repeated in this message. The maximum length and the number of repetitions allowed is a network option. | | | | | + +#### **8.1.3.7 RELEASE COMPLETE** + +This message is sent by the user or the network to indicate that the transport entity sending the message has released its call reference value. The receiving equipment shall release its call reference value. The structure of the RELEASE COMPLETE message is the same as that shown in 3.16/Q.2931 [13] (see Table 3-7/Q.2931). + +#### **8.1.3.8 STATUS** + +This message is sent from the user or the network in response to a STATUS ENQUIRY message or at any point in time to report certain error conditions. The structure of the STATUS message is the same as that shown in 3.1.8/Q.2931 [13] (see Table 3-9/Q.2931). + +#### **8.1.3.9 STATUS ENQUIRY** + +This message is sent by the user or the network at any time to solicit a STATUS message from the peer layer 3 entity. Sending a STATUS message in response to a STATUS ENQUIRY message is mandatory. The structure of the STATUS ENQUIRY message is as shown in 3.1.9/Q.2931 [13] (see Table 3-10/Q.2931). + +## **8.2 General message format and information element coding** + +Clause 4/Q.2931 shall be used with the following additions. + +### **8.2.1 Message type** + +The additional message type codings for the purpose of this Recommendation are defined in Table 7. + +TABLE 7/Q.2932.1 + +#### **Message types** + +| | | +|-----------------|----------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 - - - - | Q.2931 [13] call establishment message group | +| 1 0 1 0 1 | CO-BI SETUP | +| 0 1 1 - - - - | Q.2931 [13] miscellaneous message group | +| 0 0 0 1 0 | FACILITY | + +### **8.2.2 Other information elements** + +Table 8 shows the additional information elements defined for the generic functional protocol and those information elements of Recommendation Q.2931 [13] which are extended for this purpose. + +TABLE 8/Q.2932.1 + +#### **Information elements specific to the generic functional protocol** + +| Bits | Subclause reference | Maximum length (octets) | +|-------------------------------|---------------------|-------------------------| +| 8 7 6 5 4 3 2 1 | | | +| 0 0 0 1 1 1 0 0 Facility | 8.2.2.2 | (Note) | +| All other values are reserved | | | + +NOTE – The maximum length of the Facility information elements is application dependent consistent with the maximum length of the message. + +#### **8.2.2.1 Call state** + +The call state information element is defined as in subclause 4.5.10/Q.2931 [13]. However the state value assignments defined in Table 9 exist for the connection-oriented bearer-independent transport mechanism. + +TABLE 9/Q.2932.1 + +##### **Call state information element** + +| | | | +|---|----------------------------|--------------------------| +| – | Call state value (octet 5) | | +| | Bits | | +| | 6 5 4 3 2 1 state | | +| | 0 0 0 0 0 0 0 | Null | +| | 0 0 0 0 0 1 1 | Call Initiated | +| | 0 0 0 0 1 1 3 | Outgoing Call Proceeding | +| | 0 0 0 1 1 0 6 | Call Present | +| | 0 0 1 0 0 1 9 | Incoming Call Proceeding | +| | 0 0 1 0 1 0 10 | Active | +| | 0 0 1 0 1 1 11 | Release Request | + +#### 8.2.2.2 Facility + +The purpose of the Facility information element is to carry APDUs. + +The Facility information element can be included in all call/connection control messages, all party control messages, and all messages defined in this Recommendation except for the NOTIFY, STATUS, and STATUS ENQUIRY messages. + +Figure 3 shows the structure of the Facility information element. Table 10 shows the value of the protocol profile field applicable for supplementary services or additional basic call capabilities. + +![](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|--------------------------------|-----------------|------|---------------------------------------|--------------------------------------|---|---|---|--------| +| Facility | | | | | | | | | +| 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | +| Information element identifier | | | | | | | | | +| 1
ext | Coding standard | | Information element instruction field | | | | | 2 | +| | | Flag | Res. | Information element action indicator | | | | | +| Length of facility contents | | | | | | | | 3 | +| | | | | | | | | 4 | +| 1
ext. | 0 | 0 | Protocol profile | | | | | 5 | +| Spare | | | | | | | | | +| APDU(s) (Note) | | | | | | | | 6 | + +NOTE – One or more APDUs may be included depending on specific service requirements. Multiple APDUs may be sent in one Facility information element or in more than one (individual) Facility information elements. It is a sender's choice to use either one or several Facility information elements taking into account the maximum length of the Facility information element. + +FIGURE 3/Q.2932.1 + +##### Facility information element + +TABLE 10/Q.2932.1 + +##### Facility information element protocol profile + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|-----------------------------------| +| Bits | | | | | | +| 5 | 4 | 3 | 2 | 1 | | +| 1 | 0 | 0 | 0 | 1 | Remote operations protocol (Note) | +| All other values are reserved and their usage is the subject of other Recommendations. | | | | | | +| NOTE – Use of this codepoint indicates that the only APDUs appearing in octet 4 will be those defined for use in ROSE. All local values will be those specified for the DSS 1 and DSS 2 protocols. | | | | | | + +The APDU structures are defined in Table A.1 using ASN.1 as specified in Recommendation X.208 [6]. A representation using ASN.1 as specified in Recommendation X.680 is defined in Table B.1. + +When specified according to Recommendation X.208 [6], all data structures in the Facility information element (octet 6, etc.) shall be encoded according to the Basic Encoding Rules (BERs) as specified in Recommendation X.209 [7]. + +When specified according to Recommendation X.680 [8], all data structures in the Facility information element (octet 6, etc.) shall be encoded according to the BER as specified in Recommendation X.690 [9]. + +NOTE – The following guidelines apply for the application of the different length encodings: + +- the short form definitive length encoding should be used to indicate the length of a data value with a length less than 128 octets; +- when the long form definitive length encoding is used, the minimum number of octets should be used; +- OCTET STRING and BIT STRING values should be encoded in a primitive form. + +Receiving entities shall be able to interpret all length forms of the basic encoding rules. + +##### **8.2.2.2.1 Treatment of existing Q.2931 information elements as parameters** + +Supplementary service or additional basic call capability protocol specifications are expected to require new parameters to be defined and to require existing Q.2931 [13] information elements. + +New parameters shall be defined using X.209 [7] coding, or Recommendation X.690 [9] as appropriate, if they do not appear elsewhere in Q.2931 [13] messages. + +Supplementary service or additional basic call capability protocol specifiers may elect to encapsulate one or more existing Q.2931 [13] information elements within an X.209 [7] data element, or X.690 [9] data element, as appropriate, thereby retaining the Q.2931 [13] coding for these information elements. When this option is chosen, all the Q.2931 [13] information elements should be grouped together as the content following the Q.2931 [13] information elements tag. This data element may appear by itself or as a member of a sequence or set. + +Encapsulation of the Facility information element within Facility information elements shall not be used. + +A formal definition of this mechanism using ASN.1, as specified in Recommendation X.208 [6], is given in A.2. A formal definition of this mechanism using ASN.1, as specified in Recommendation X.680 [8], is given in Table B.2. + +# **9 Signalling procedures at the coincident SB and TB reference point** + +## **9.1 APDU transport mechanisms** + +The transport function for operations is performed by the exchange of APDUs via DSS 2 messages. + +A supplementary service or additional basic call capability functional protocol (using the Facility information element) may use an existing bearer-related call reference if it is to be coupled to the connection, or it may use a bearer-independent call reference. + +### **9.1.1 Bearer-related transport** + +NOTE – The definition of "Bearer-related transport mechanism" is given in 3.3. + +The procedures for connection control are described in clause 5/Q.2931 [13]. These procedures are not influenced by the APDUs carried. Bearer-related transport procedures and operations shall operate independently of each other. + +#### 9.1.1.1 Normal operation + +For bearer-related transport any call/connection control message, any party control message, and the messages defined in 8.1.1, may be used to carry the APDUs in a Facility information element. These messages shall use the call reference of the bearer connection. + +The FACILITY message shall not be sent in the following call/connection states: + +- Null (0) (U0) (N0); +- Call Initiated (1) (U1) (N1); +- Call Present (6) (U6) (N6); +- Release Request (11) (U11) (N11); +- Release Indication (12) (U12) (N12). + +The call reference provides the means to correlate messages belonging to the same connection. When a supplementary service or additional basic call capability affects more than one connection, different call references are used to identify each connection individually. This implies the use of different messages in order to manage each connection separately. + +When the call/connection associated with the AS-Control functionality is cleared due to AS-Control actions, the Cause information element in the clearing message shall be set to #16 "normal clearing". + +NOTE – Any additional reason for clearing is included in the APDUs generated by AS-Control, and therefore transferred in the Facility information element. + +When indicated by GFT-Control, generic functional data shall be included in a Facility information element and transferred in a call control message or party control message if such a message is being sent for other reasons, or else in a FACILITY message. + +The transport mechanism shall pass all valid received generic functional data and protocol profile values in the Facility information element to GFT-Control and the procedures specified in GFT-Control (see 9.3) shall also apply. + +#### 9.1.1.2 Exceptional procedures + +If the network or user recognizes a supplementary service or additional basic call capability request in a received SETUP message but is not able to process the request, then the following options shall apply: + +- the network or user may clear the call request and reject the supplementary service or additional basic call capability invocation by means of an appropriate call-clearing message which contains the Cause information element and a return error APDU with the appropriate parameters in the Facility information element; +- the network or user may continue to process the call request according to the call control procedures of Recommendation Q.2931 [13], and reject the supplementary service or additional basic call capability invocation by including a return error APDU with the appropriate parameters in the Facility information element by means of a FACILITY message or in an appropriate call/connection control message or party control message. + +The option to be used depends on the individual supplementary service or additional basic call capability procedures which are the subject of other Recommendations. + +In addition, when the network or user identifies an error in the received APDU, the network or user may continue to process the call request according to the call control procedures of Recommendation Q.2931 [13], and ignore the supplementary service or additional basic call capability invocation, in which case a reject component shall be generated. + +No response message shall be sent after the call reference value has been released. + +The procedures of 9.1.1 are an extension to the procedures of Recommendations Q.2931 [13] and Q.2971 [14]. As such the general error handling procedures as defined in 5.6/Q.2931 [13] and 9.5/Q.2971 apply. However, the handling of errors in octet 5 of the Facility information element is specified in 9.3.2. The handling of errors in APDUs is specified in Appendix III. If the connection is being cleared, the treatment of outstanding supplementary service or additional basic call capability requests is subject to the Recommendations for the individual supplementary services or additional basic call capabilities. + +### **9.1.2 Bearer-independent transport mechanisms** + +This subclause and 9.1.3 and 9.1.4 define the transport of APDUs independently of a connection. This Recommendation utilizes the signalling AAL connection services as described in Recommendation Q.2130 [15]. The messages used for transport (i.e. CO-BI SETUP, CONNECT, FACILITY and RELEASE) may carry the Facility information elements containing the application-oriented operation APDUs. + +The correlation among the various transport messages is provided by means of the call reference value of each message. + +The bearer-independent transport functions are divided into the following two categories: + +- connection-oriented (Note); +- connectionless (Note). + +NOTE – A definition of the terms "connection-oriented" and "connectionless" is given in clause 3. + +Within this subclause, signalling AAL service primitives are used to illustrate the communication between protocol layers and are not intended to specify or constrain implementations. + +### **9.1.3 Connection-oriented bearer-independent transport mechanism** + +The procedures in this subclause describe a connection-oriented service which provides APDU transfer between signalling entities outside the context of a bearer. + +The description of the protocol control requirements for connection-oriented bearer-independent transport uses a set of states defined in 7.2.1.3. + +#### **9.1.3.1 Actions in the Null state** + +When asked to initiate a Bearer-independent signalling connection by GFT-Control, the outgoing transport entity shall: + +- a) ensure that a reliable SAAL connection exists. If a reliable SAAL connection does not exist, the transport entity shall establish a reliable SAAL connection according to the procedures described in Recommendation Q.2130 [15]; +- b) send a CO-BI SETUP message on the appropriate SAAL connection which shall contain only: + - a call reference, selected according to 4.3/Q.2931 [13]; + - if indicated by GFT-Control, one or more Facility information elements; + +- if indicated by any AS-Control entity, one or more Notification indicator information elements. + +NOTE – In addition, the CO-BI SETUP message may also be extended with the Called party number information element, the Calling party number information element, and the Called party subaddress information element as described in 9.2. + +- c) start timer T303; and +- d) enter the Call Initiated state. + +On receipt of a CO-BI SETUP message relating to establishment of a bearer-independent signalling connection, the incoming transport entity shall: + +- i) if the request is valid and can be processed, indicate the connection request to GFT-Control and enter the Call Present state; or +- ii) if the request is invalid or cannot be accepted by the GFT-control, return a RELEASE COMPLETE message to the outgoing transport entity, release the call reference and remain in the Null state. + +#### **9.1.3.2 Actions in the Call Present state** + +If indicated by GFT-Control, the incoming transport entity shall return a CALL PROCEEDING message to the outgoing transport entity, and shall enter the Incoming Call Proceeding state. + +If indicated by GFT-Control, the incoming transport entity shall return a CONNECT message to the outgoing transport entity, and shall enter the Active state. + +#### **9.1.3.3 Actions in the Call Initiated state** + +On receipt of a CALL PROCEEDING message from the incoming transport entity, the outgoing transport entity shall stop timer T303, and enter the Outgoing Call Proceeding state. + +If no response is received before timer T303 expires, the outgoing transport entity shall inform GFT-Control of the failure of the signalling connection request and enter the Null state. + +NOTE 1 – A clearing cause value of #102 "recovery on timer expiry" shall be indicated for use in any protocol signalling to a preceding entity. + +NOTE 2 – If the connection-oriented procedures are not supported by a GFT-Control which receives a CO-BI SETUP message, and the instruction indicators in the Message type information element do not indicate a different course of action, it will respond with a RELEASE COMPLETE message indicating, cause #81 "invalid call reference value". This will initiate connection release in accordance with 9.1.3.8. + +#### **9.1.3.4 Actions in the Incoming Call Proceeding state** + +When receiving an indication that the bearer-independent signalling connection is established from GFT-Control, the incoming transport entity shall: send a CONNECT message to the outgoing transport entity and enter the Active state. + +The CONNECT message shall contain: + +- if indicated by GFT-Control, one or more Facility information elements; +- if indicated by any AS-Control entity, one or more Notification indicator information elements. + +#### **9.1.3.5 Actions in the Outgoing Call Proceeding state** + +On receipt of a CONNECT message from the incoming transport entity, the outgoing transport entity shall: inform GFT-Control that the signalling connection is established and enter the Active state. + +#### **9.1.3.6 Actions in the Active state** + +In the Active state a FACILITY message can be sent or received. + +#### **9.1.3.7 Connection release** + +When a transport entity is requested by GFT-Control to release a bearer-independent signalling connection, the transport entity shall: + +- if in the Release Request state, ignore the request from GFT-Control; or +- if in any other transport entity state, send a RELEASE message with an appropriate cause value, start timer T308 and enter the Release Request state. + +When Transport entity makes a local decision to release a bearer-independent signalling connection (e.g. due to a protocol error), it shall, if not in the Release Request state: inform GFT-Control that the signalling connection has been released, send a RELEASE message, start timer T308 and enter the Release Request state. + +The RELEASE message shall contain: + +- an appropriate cause value; +- if indicated by GFT-Control, one or more Facility information elements; +- if indicated by any AS-Control entity, one or more Notification indicator information elements. + +On receipt of a RELEASE message in any state other than the Release Request state, the transport entity shall indicate to GFT-Control that the signalling connection has been released, stop all timers, send a RELEASE COMPLETE message, release the call reference and enter the Null state. + +On receipt of a RELEASE COMPLETE message in any state other than the Release Request state, the transport entity shall indicate to GFT-Control that the signalling connection has been released, stop all timers, release the call reference and enter the Null state. + +#### **9.1.3.8 Actions in the Release Request state** + +On receipt of a RELEASE or a RELEASE COMPLETE message, the transport entity shall: stop timer T308, release the call reference and enter the Null state. + +If timer T308 expires for the first time, the RELEASE message shall be retransmitted and timer T308 shall be restarted. If timer T308 expires a second time, the transport entity shall release the call reference and enter the Null state. + +#### **9.1.3.9 Transport of APDUs associated with a connection-oriented bearer-independent signalling connection** + +When indicated by GFT-Control, generic functional data shall be included in a Facility information element and transferred in a bearer-independent control message if such a message is being sent to establish or clear the signalling transaction, or, whilst in the Active state, in a FACILITY message. + +The transport mechanism shall pass all valid received generic functional data and protocol profile values in the Facility information element to GFT-control and the procedures specified in GFT-Control (see 9.3) shall also apply. + +#### **9.1.3.10 Transport of notifications** + +The delivery of bearer-independent notifications shall use an active call reference of the connection-oriented transport mechanism. In this context, a call reference shall be active from the initiation of + +establishment (i.e. the CO-BI SETUP message) to the initiation of clearing (i.e. the RELEASE message). + +If the delivery of the notification coincides with establishment or clearing, the notification information can be carried in a bearer-independent control message. In all other cases, the notification information shall be delivered in a NOTIFY message. In addition a NOTIFY message may be sent or received by the DSS 2 entity only after the first response to a CO-BI SETUP message has been sent or received and before the clearing of the call reference is initiated. + +If a notification is received by the network, the network shall optionally ensure that the contents of the notification are a valid coding; and forward the notification to the other user involved in the call. + +No state change shall occur at either side of the interface following sending or receipt of a NOTIFY message. + +If a receiving CO-BI transport entity has no related AS-Control entity – i.e. a relationship between AS-Control entities does not yet exist, will not be created as a result of the received message, or has ceased to exist – then the received notification shall be discarded. + +#### **9.1.3.11 Protocol error handling** + +Subclause 5.6/Q.2931 [13] shall apply with the following modifications: + +- actions regarding the handling of VCIs and VPCIs are not applicable; +- if a SETUP ACKNOWLEDGE, ALERTING or PROGRESS message (defined in ITU-T Recommendation Q.2931 [13]) is received in any state (except the Null state, where invalid call reference error procedures apply) it shall be treated as an unexpected or unrecognised message in accordance with 5.6.4/Q.2931 [13]; + +These general error handling procedures only apply for octet 1 through 4 of the Facility information element. The handling of errors in octet 5 is specified in 9.3.2. + +Subclause 5.6.11/Q.2931 [13] shall apply for the generation and request of bearer-independent connection state information. + +### **9.1.4 Connectionless bearer-independent transport mechanism** + +#### **9.1.4.1 Normal operation** + +The connectionless transport mechanism is based on FACILITY messages. However, the connectionless transport mechanism shall only use the dummy call reference value as specified in 4.3/Q.2931 [13]. + +Before data can be sent the transport entity shall first ensure establishment, if not already available, of a reliable signalling AAL connection using the signalling AAL\_ESTABLISH.request service primitive as described in Recommendation Q.2130 [15]. Completion of establishment of this connection is indicated by a signalling AAL\_ESTABLISH.confirm primitive. + +The FACILITY message is used to carry the "user" information, i.e. the APDU structures in the Facility information element. + +NOTE – In addition, the FACILITY message may also be extended with the Called party number information element, the Calling party number information element, the Called party subaddress information elements described in 9.2. + +When indicated by GFT-Control, the transport entity shall include generic functional data in one or more Facility information elements and shall transfer this information in a FACILITY message. + +The transport entity shall pass all valid received generic functional data and protocol profile values in the Facility information element to GFT-Control and the procedures specified in GFT-Control (see 9.3) shall also apply. + +#### **9.1.4.2 Exceptional procedure** + +If the message action indicator is to be applied to a received FACILITY message as a result of error handling, the receiver shall treat the "clear call" and "discard and report status" values as if "discard and ignore" had been received. + +If the instruction indicator is to be applied for a received information element, the receiver shall treat the "clear call" and discard "message and report status" values as if "discard message and ignore" had been received. + +If a FACILITY message is received and it does not contain the Facility information element, the receiving entity shall discard the FACILITY message. + +If a FACILITY message is received that contains a Facility information element with invalid content in octets 1 to 4, then that Facility information element and the FACILITY message shall be ignored and no action taken on the contents of the FACILITY message. + +If a FACILITY message is received that contains an unexpected information element, an unrecognized information element, or an optional information element with content error, and explicit actions are not applied, then that information element shall be ignored, and action taken on the message and those information elements that are recognized and have valid content. + +If either transport entity receives an indication that the signalling AAL connection has been released via the signalling AAL\_RELEASE.indication primitive, or that the signalling AAL connection has spontaneously been reset via the signalling AAL\_ESTABLISH.indication primitive, then the procedures as they affect the supplementary service or additional basic call capability are outside the scope of this Recommendation. + +NOTE – The handling of layer 2 errors is dependent on the supplementary service or additional basic call capability and are therefore specified in the individual Recommendation referencing this subclause. + +## **9.2 Addressing of APDUs** + +### **9.2.1 Local addressing** + +Within this part of this Recommendation communication is entirely local, i.e. an association exists between an AS-Control entity in the user and an AS-Control entity in the network. However, there exists the possibility that multiple AS-Control entities may exist in the user, and identification/addressing of these is performed by either the multiple subscriber number supplementary service or the subaddressing supplementary service. Figure 4 shows the associated architecture for multiple terminal applications as described above. + +![Diagram of protocol architecture for multiple subscriber number and subaddressing supplementary services. It shows a network stack and three user stacks (user 1, user 2, user 3). The network stack has AS-Control, GFT-Control, transport mechanism, and SAAL. The user stacks have the same layers. User 1's transport mechanism is labeled 'number = A, subaddr = X'. User 2's transport mechanism is labeled 'number = A, subaddr = Y'. User 3's transport mechanism is labeled 'number = B'. All transport mechanisms connect to a common SAAL layer. There are ovals between the transport mechanism and SAAL in the network and user 2 stacks. A label 'T1179560-96' is in the bottom right.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +Diagram of protocol architecture for multiple subscriber number and subaddressing supplementary services. It shows a network stack and three user stacks (user 1, user 2, user 3). The network stack has AS-Control, GFT-Control, transport mechanism, and SAAL. The user stacks have the same layers. User 1's transport mechanism is labeled 'number = A, subaddr = X'. User 2's transport mechanism is labeled 'number = A, subaddr = Y'. User 3's transport mechanism is labeled 'number = B'. All transport mechanisms connect to a common SAAL layer. There are ovals between the transport mechanism and SAAL in the network and user 2 stacks. A label 'T1179560-96' is in the bottom right. + +T1179560-96 + +FIGURE 4/Q.2932.1 + +#### **Protocol architecture associated with the use of multiple subscriber number and subaddressing supplementary services** + +Any local address required is supplied by GFT-Control and thus to the appropriate transport entity. + +### **9.2.2 Additional transport procedures where the multiple subscriber number supplementary service applies** + +#### **9.2.2.1 Bearer-related transport mechanism** + +The multiple subscriber number supplementary service applies only to the bearer as described in Recommendation Q.2951.2 [11]. + +#### **9.2.2.2 Connection-oriented bearer-independent transport mechanism** + +The outgoing user may include in the CO-BI SETUP message a Calling party number information element. The coding of the Calling party number information element shall follow the same requirements as specified for the SETUP message in 1.9.1.1/Q.2951.2 [11]. + +On receipt of a Calling party number information element in a CO-BI SETUP message by the outgoing network, the network shall apply the same procedures to the Calling party number information element as are specified in 1.9.1.1/Q.2951.2 [11] for basic call. + +The incoming network may include in the CO-BI SETUP message a Called party number information element. The coding of the Called party number information element shall follow the same requirements as specified for the SETUP message in 1.9.2.1/Q.2951.2 [11]. + +On receipt of a Called party number information element in a CO-BI SETUP message by the incoming user, the network shall apply the same procedures to the Called party number information element as are specified in 1.9.1.2/ Q.2951.2 [11] for basic call. + +#### **9.2.2.3 Connectionless bearer-independent transport mechanism** + +The outgoing user may include in the FACILITY message a Calling party number information element. The coding of the Calling party number information element shall follow the same requirements as specified for the SETUP message in 1.9.1.1/Q.2951.2 [11]. + +On receipt of a Calling party number information element in a FACILITY message by the incoming network, the network shall apply the same procedures to the Calling party number information element as are specified in 1.9.1.1/Q.2951.2 [11] for basic call. + +The incoming network may include in the FACILITY message a Called party number information element. The coding of the Called party number information element shall follow the same requirements as specified for the SETUP message in 1.9.2.1/Q.2951.2 [11]. An exception is that no protocol is returned. + +On receipt of a Called party number information element in a FACILITY message by the incoming user, the user shall apply the same procedures to the Called party number information element as are specified in 1.9.1.2/Q.2951.2 [11] subclause for basic call. + +### **9.2.3 Additional transport procedures where the subaddressing supplementary service applies** + +#### **9.2.3.1 Bearer-related transport mechanism** + +The subaddressing supplementary service applies only to the bearer as described in Recommendation Q.2951.8 [12]. + +#### **9.2.3.2 Connection-oriented bearer-independent transport mechanism** + +The incoming network may include in the CO-BI SETUP message a Called party subaddress information element. The coding of the Called party subaddress information element shall follow the same requirements as specified for the SETUP message in 1.9.2.1/Q.2951.8 [12]. + +On receipt of a Called party subaddress information element in a CO-BI SETUP message by the incoming user, the user shall apply the same procedures to the Called party subaddress information element as are specified in 1.9.2.2/Q.2951.8 [12] for basic call. + +#### **9.2.3.3 Connectionless bearer-independent transport mechanism** + +The incoming network may include in the FACILITY message a Called party subaddress information element. The coding of the Called party subaddress information element shall follow the same requirements as specified for the SETUP message in 1.9.2.1/Q.2951.8 [12]. An exception is that no protocol is returned. + +On receipt of a Called party subaddress information element in a FACILITY message by the incoming user, the user shall apply the same procedures to the Called party subaddress information element as are specified in 1.9.1.2/Q.2951.8 [12] for basic call. + +## **9.3 GFT-Control** + +This subclause provides the limited procedures for GFT-Control when local addressing only is supported. + +### **9.3.1 Transmission of generic functional data** + +When ROSE or any other ASE requires to transmit generic functional data, this is indicated to GFT-Control. GFT-Control shall: + +- determine from the information supplied by ROSE or any other ASE the transport mechanism required; +- ensure that the required transport mechanism is in a state to transmit generic functional data; + +- where it is required to establish a new connection-oriented bearer-independent transport mechanism, then on receipt of an indication from the transport mechanism that a CALL PROCEEDING message has been received, GFT-Control shall start timer T310. On receipt of an indication from GFT-Control that a CONNECT message has been received, GFT-Control shall stop timer T310. If T310 expires, then the appropriate AS-Control shall be informed of the failure to send generic functional data; + +NOTE 1 – A clearing cause value of #102 "recovery on timer expiry" shall be indicated for use in any protocol signalling to a preceding entity. + +- supply to the appropriate transport mechanism the generic functional data and protocol profile based on the type of ASE requesting transport of generic functional data. In particular, for the support of ROSE for local addressing within the constraints of this part of this Recommendation, the protocol profile shall be set to "ROSE"; +- indicate the instruction indicator for use in the Facility information element; +NOTE 2 – The prime function of the instruction indicator in the Facility information element is to provide corrective action when the generic functional protocol is not supported. +- indicate any required address for the multiple subscriber number or subaddressing supplementary service. + +If GFT-Control is unable to provide the transfer of generic functional data, it shall indicate this to ROSE or any other appropriate ASE. + +### 9.3.2 Receipt of generic functional data + +When a transport mechanism receives a Facility information element, this is indicated to GFT-Control. + +GFT-Control shall check the protocol profile, and if it is valid it shall indicate this data to the appropriate ASE. In particular, if the protocol profile is set to "ROSE", this shall be indicated to the ROSE ASE. If the protocol profile is set to a reserved value, or to a value of protocol profile that is not supported, the generic functional data shall be discarded, and the procedures for unrecognized information element content specified in 5.6.8.2/Q.2931 or 5.7.2/Q.2931 [13], as appropriate, shall be followed on the appropriate transport mechanism. The error handling rules in subclauses 5.6.8.2/Q.2931 and 5.7.2/Q.2931 [13] shall apply only for errors in the octets 1 through 5 of the Facility information element. Errors in subsequent octets shall be handled according to the appropriate ROSE procedures. + +## 9.4 Remote operations procedures + +### 9.4.1 Introduction + +The generic functional protocol provides a means of exchanging generic functional data and is specified as a realization of ROSE (see Recommendations X.219 [3] and X.880 [17]). + +### 9.4.2 Procedures for operations + +The specification of procedures for operations of this subclause is according to the definition of elements of procedure of Recommendations X.229 [2] or X.880 [17], but uses only those elements which are specified for application within the Facility information element of this Recommendation. In addition, this subclause includes some extensions to ROSE concerning the error procedures. Recommendations X.229 [2] and Recommendation X.880 [17] provide consistent specifications of the remote operation procedures and the application of one or the other depends on the version of the abstract syntax used for the specification of the remote operations by the AS-Control entities. + +The procedures for operations are defined in terms of the interactions between peer-to-peer protocol machines through the use of a transport mechanism of the DSS 2 protocol. The operation protocol comprises of the following procedures: + +- invocation; +- return result; +- return error; and +- reject. + +The structure, contents and encoding of the appropriate APDUs are defined in 8.2. Dependent on the specific operation, return result and return error APDUs can be applicable. This is specified in the Recommendation of the individual applications. + +In the following subclauses a summary of the procedures of each of these APDUs is given as far as applicable to this Recommendation. + +#### 9.4.2.1 Invocation + +An application entity (invoker) shall use the invocation procedure to initiate an operation to be performed by the other application entity (performer). The invocation procedures shall use the invoke APDU as described in Table A.1. The invoke APDU shall be delivered towards the remote peer entity within a Facility information element sent within an appropriate transport message (e.g. call/connection control messages, party control messages, bearer-independent control messages, or FACILITY messages). + +The operation value shall be used to identify the operation to be invoked, e.g. a specific supplementary service, a part of a specific supplementary service or a generic function. + +The invoke identifier shall be used to identify the request of a ROSE-invoke service (10.1/X.219 [3]) and to correlate this request with the corresponding replies. The value is assigned by the invoker. + +The invoke identifier shall be significant within a certain call reference value. The value (invoke identifier, call reference, signalling AAL connection endpoint identifier) shall uniquely identify an instance of an operation. In this respect the dummy call reference shall be regarded as a call reference as well. + +An invoke identifier value shall not be reused as long as a response is expected pertaining to the invocation identified by this invoke identifier. + +The linked identifier shall be used within a ROSE-invoke service (10.1/X.219 [3]), when the invoked operation is a child operation and this parameter identifies the linked parent operation. + +#### **9.4.2.2 Return result** + +An AS-Control entity (performer) shall use the return result procedure to request the transfer of the result of a successfully performed operation to the other AS-Control entity (invoker). The return result procedure shall use the return result APDU as described in Table A.1. + +The return result APDU shall be delivered towards the remote peer entity in a Facility information element within an appropriate transport message. + +#### **9.4.2.3 Return error** + +An AS-Control entity (performer) shall use the return error procedure to request the transfer of the error information in the case of an unsuccessfully performed operation to the other AS-Control entity (invoker). The return error procedure shall use the return error APDU as described in Table A.1. Error values shall be defined specifically for each individual operation. + +The return error APDU shall be delivered towards the remote peer entity in a Facility information element within an appropriate transport message. + +#### **9.4.2.4 Reject** + +An AS-Control entity shall use the reject procedure to reject the request (invocation) or reply (result or error) of the other AS-Control entity. The reject procedure shall be used by the receiver when the received request or reply cannot be processed because of errors in the received APDU (e.g. mistyped APDU or unrecognized operation). The receipt of a reject APDU shall not result in the start of a reject procedure. + +In addition, a reject component may also be generated by ROSE for the same reasons as apply in the application. + +The reject procedure shall use the reject APDU as described in Table A.1 and shall use the definition of problems as specified in Table 11. The reject APDU shall be delivered towards the remote peer entity in a Facility information element within an appropriate transport message. + +TABLE 11/Q.2932.1 + +##### **Problem code definitions** + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| General-problem | | +| – unrecognized-APDU | signifies that the type of the APDU, as evidenced by its type identifier, is not one of the four defined in A.1 | +| – mistyped-APDU | signifies that the structure of the APDU does not conform to A.1 | +| – badly-structured-APDU | signifies that the structure of the APDUs does not conform to the standard notation and encoding, defined in Recommendations X.208 [6] and X.209 [7], or Recommendations X.680 [8] and X.690 [9] as appropriate | +| Invoke-problem | | +| – duplicate-invocation | signifies that the invoke-identifier parameter violates the assignment rules of Recommendation X.219 [3] | +| – unrecognized-operation | signifies that the operation is not one of those agreed between the user and the network | +| – mistyped-argument | signifies that the type of the operation argument supplied is not that agreed between the user and the network (Note 1) | +| – resource-limitation | the performing user or network is not able to perform the invoked operation due to resource limitation | +| – initiator-releasing | the application is not willing to perform the invoked operation because it is about to attempt to release the connection-oriented transport mechanism | +| – unrecognized-linked-identifier | signifies that there is no operation in progress with an invoke-identifier equal to the specified linked-identifier | +| – linked-response-unexpected | signifies that the invoked operation referred to by linked-identifier is not a parent-operation | +| – unexpected-child-operation | signifies that the invoked child-operation is not one that the invoked parent-operation referred to by the linked-identifier allows | +| Return-result-problem | | +| – unrecognized-invocation | signifies that no operation with the specified invoke-identifier is in progress | +| – result-response-unexpected | signifies that the invoke operation does not report a result | +| – mistyped-result | signifies that the type of the result parameter supplied is not that agreed between the user and the network (Note 1) | +| Return-error-problem | | +| – unrecognized-invocation | signifies that no operation with the specified invoke-identifier is in progress | +| – error-response-unexpected | signifies that the invoked operation does not report failure | +| – unrecognized-error | signifies that the reported error is not one of those agreed between the user and the network | +| – unexpected-error | signifies that the reported error is not one that the invoked operation may report | +| – mistyped-parameter | signifies that the type of the error parameters supplied is not that agreed between the user and the network (Note 1) | +| NOTES | | +| 1 – This problem shall not be used if all values (data elements) which are neither optional nor have default values assigned are correctly received (see 8.2.2.2). | | +| 2 – The above definitions are adapted from 7.4.4.2/X.229 and 7.5.4.2/X.229 [2]. | | + +#### **9.4.2.5 Formal definition of data types** + +The formal definition of the OPERATION and ERROR macro shall be as given in Figure 4/X.219 [3] and is described in ASN.1 using the ASN.1 macro concept. These macros shall be used in the Recommendations of the individual supplementary services to define the required operations and errors. + +NOTE – These definitions are reproduced in Appendix III. + +# **10 Procedures for interworking with private ISDNs** + +## **10.1 APDU transport mechanisms** + +The transport function for operations is performed by the exchange of APDUs via DSS 2 messages as specified in Recommendation Q.2931 [13]. + +A supplementary service or additional basic call capability functional protocol (using the Facility information element) may use an existing bearer-related call reference if it is to be coupled to the connection, or it may use a bearer-independent call reference. + +### **10.1.1 Bearer-related transport** + +The procedures shall be as specified in 9.1.1. + +### **10.1.2 Bearer-independent transport mechanisms** + +The two transport mechanisms specified in 9.1.2 shall apply, i.e. the connection-oriented bearer independent transport mechanism and the connectionless bearer-independent transport mechanism. + +NOTE – It is recommended that the connection-oriented transport mechanism is used for procedures that are specific for interworking with private ISDNs. This is however application-dependent and specified in Recommendations using the procedures of this Recommendation. + +### **10.1.3 Connection-oriented bearer-independent transport mechanism** + +The procedures of 9.1.3 shall apply. + +### **10.1.4 Connectionless bearer-independent transport mechanism** + +The procedures of 9.1.4 shall apply. + +## **10.2 Addressing of APDUs** + +The procedures of 9.2.1 shall apply. The procedures for the multiple subscriber number or subaddressing supplementary services are not applicable at the TB reference point for interworking with private ISDNs. + +## **10.3 GFT-Control** + +This subclause provides the limited procedures for GFT-Control when local addressing only is supported. + +The procedures of 9.3 shall apply. + +## **10.4 Generic functional protocol** + +The procedures of subclause 9.4 shall apply. + +# **11 Interactions with other networks** + +This clause provides procedures for interworking between DSS 2 and other access protocols (e.g. DSS 1), through an interworking unit. It also therefore indicates possible appropriate mappings where more complex functionality intervenes. + +## 11.1 Interworking with N-ISDNs + +Two means exist for interworking with the N-ISDN. In the first the generic functional protocol is fully terminated. In the second, a generic interworking function is provided. + +An interworking function shall either provide the procedures in 11.1.1 or those in 11.1.2. The alternative procedures cannot be used on a case-by-case basis. + +NOTE – While 11.1.2 provides the simpler functionality, it is only possible to use this functionality when all supplementary services or additional basic call functionality using the generic functional protocol that it is desired to interwork across the interworking function has equivalent procedural requirements and equivalent abstract and concrete syntax definitions in both the DSS 1 and DSS 2 protocols. Where these conditions do not apply, then 11.1.1 should be used. + +### 11.1.1 Full termination of generic functional protocol + +Figure 5 shows the protocol architecture of this interworking mechanism. + +![Figure 5/Q.2932.1: Fully terminated interworking diagram. The diagram shows two protocol stacks, DSS 1 and DSS 2, connected via an 'Interworking function'. DSS 1 consists of AS-Control, Rec. Q.932 (transport), and Rec. Q.921. DSS 2 consists of AS-Control, ROSE, GFT-Control, transport, and SAAL. The Interworking function connects to the AS-Control of both stacks. Dotted double-headed arrows indicate interworking between corresponding layers: AS-Control to AS-Control, Rec. Q.932 to GFT-Control, and Rec. Q.921 to SAAL. Solid double-headed arrows indicate vertical connections within each stack. A label 'T1179570-96' is at the bottom right.](030c758fd425016b03290c8f11bef69d_img.jpg) + +Figure 5/Q.2932.1: Fully terminated interworking diagram. The diagram shows two protocol stacks, DSS 1 and DSS 2, connected via an 'Interworking function'. DSS 1 consists of AS-Control, Rec. Q.932 (transport), and Rec. Q.921. DSS 2 consists of AS-Control, ROSE, GFT-Control, transport, and SAAL. The Interworking function connects to the AS-Control of both stacks. Dotted double-headed arrows indicate interworking between corresponding layers: AS-Control to AS-Control, Rec. Q.932 to GFT-Control, and Rec. Q.921 to SAAL. Solid double-headed arrows indicate vertical connections within each stack. A label 'T1179570-96' is at the bottom right. + +FIGURE 5/Q.2932.1 + +#### Fully terminated interworking + +In this situation the generic functional protocol is fully terminated in the interworking unit, and interworking requirements are therefore specified by the ITU-T Recommendation specification giving the AS-Control entity requirements. These procedures are therefore outside the scope of this Recommendation. Within the interworking function the procedures of clauses 9 or 10 shall apply at the DSS 2 side as appropriate. + +### 11.1.2 Generic interworking function + +#### 11.1.2.1 Architecture + +Figure 6 shows the protocol architecture of this interworking mechanism. + +![Figure 6/Q.2932.1: Generic interworking architecture diagram. The diagram shows two systems, DSS 1 and DSS 2, connected via an interworking function. DSS 1 consists of AS-Control, Rec. Q.932, and Rec. Q.921. DSS 2 consists of AS-Control, ROSE, GFT-Control, transport, and SAAL. The interworking function contains Rec. Q.932, transport, and SAAL. Dotted lines indicate connections between corresponding layers in DSS 1 and DSS 2 through the interworking function. Solid double-headed arrows indicate internal connections within each system and within the interworking function. A label 'T1179580-96' is present in the bottom right corner.](32ff77da4286b58c4778033acaa10836_img.jpg) + +Figure 6/Q.2932.1: Generic interworking architecture diagram. The diagram shows two systems, DSS 1 and DSS 2, connected via an interworking function. DSS 1 consists of AS-Control, Rec. Q.932, and Rec. Q.921. DSS 2 consists of AS-Control, ROSE, GFT-Control, transport, and SAAL. The interworking function contains Rec. Q.932, transport, and SAAL. Dotted lines indicate connections between corresponding layers in DSS 1 and DSS 2 through the interworking function. Solid double-headed arrows indicate internal connections within each system and within the interworking function. A label 'T1179580-96' is present in the bottom right corner. + +FIGURE 6/Q.2932.1 + +#### Generic interworking + +For this form of interworking to take place, the supplementary service procedures or other functionality for both DSS 1 and DSS 2 are identical with the exception of the transport mechanism. The same operation and error values shall be used in both protocols for the same supplementary service or other functionality. + +The procedures for interworking the various transport mechanisms are given in the following subclauses. + +#### 11.1.2.2 Bearer-related transport mechanism + +All mapping is performed as specified in 6/Q.2931 [13], with the addition that the Facility information element is included in all mapped messages. + +In addition, for mapping DSS 2 to DSS 1 the mappings shown in Table 12 shall apply. + +TABLE 12/Q.2932.1 + +##### DSS 2 to DSS 1 mapping + +| DSS 2 message | | DSS 1 message | +|---------------|---|---------------| +| FACILITY | → | FACILITY | + +In addition, for mapping DSS 1 to DSS 2, the mappings shown in Table 13 shall apply. + +TABLE 13/Q.2932.1 + +##### **DSS 1 to DSS 2 mapping** + +| DSS 1 message | | DSS 2 message | +|---------------|---|---------------| +| FACILITY | → | FACILITY | + +The DSS 2 Facility information element is mapped to the DSS 1 Facility information element by removing its second octet and adjusting the length indication without causing other changes to the contents. + +The DSS 1 Facility information element is mapped to the DSS 2 Facility information element by inserting the second octet and changing length indication field from one to two octets, adjusting the length accordingly, without causing other changes to the contents. The flag bit in the second octet is set to "0", i.e. the normal error handling procedures as defined in 5.6/Q.2931 apply. + +#### **11.1.2.3 Connection-oriented bearer independent mechanism** + +The mapping below only applies for the local transport of generic functional data. For mapping DSS 2 to DSS 1, the mappings shown in Table 14 shall apply. + +TABLE 14/Q.2932.1 + +##### **DSS 2 to DSS 1 mapping** + +| DSS 2 message | | DSS 1 message | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---------------------------| +| CO-BI SETUP (Note 1) | → | REGISTER | +| CALL PROCEEDING | | not mapped | +| CONNECT | → | FACILITY (Note 3) | +| FACILITY | → | FACILITY | +| RELEASE (Note 2) | → | RELEASE COMPLETE | +| RELEASE COMPLETE | → | RELEASE COMPLETE (Note 4) | +| NOTIFY (Note 5) | | not mapped | +| NOTES
1 – A CALL PROCEEDING message and a CONNECT message are also returned to the DSS 2 entity by the interworking function.
2 – A RELEASE COMPLETE message is also returned to the DSS 2 entity by the interworking function.
3 – Mapping is only performed if the CONNECT message contains a Facility information element.
4 – This mapping only occurs if the DSS 2 RELEASE COMPLETE message is the first clearing message.
5 – It is not expected that this message would occur in a DSS 2 to DSS 1 interworking scenario. | | | + +For mapping DSS 1 to DSS 2, the mappings shown in Table 15 shall apply. + +TABLE 15/Q.2932.1 + +##### **DSS 1 to DSS 2 mapping** + +| DSS 1 message | | DSS 2 message | +|------------------|---|---------------| +| REGISTER | → | CO-BI SETUP | +| FACILITY | → | FACILITY | +| RELEASE COMPLETE | → | RELEASE | + +For the mappings shown in Tables 14 and 15, the following information elements are mapped in either direction: + +- facility information element; +- called party number information element; +- called party subaddress information element; +- notification indicator information element. + +The contents of the following information elements contained in the DSS 2 protocol are discarded: + +- calling party number information element. + +The DSS 2 Facility information element is mapped to the DSS 1 Facility information element by removing its second octet and adjusting the length indication without causing other changes to the contents. + +The DSS 1 Facility information element is mapped to the DSS 2 Facility information element by inserting the second octet and changing length indication field from one to two octets, adjusting the length accordingly, without causing other changes to the contents. The flag bit in the second octet is set to "0", i.e. the normal error handling procedures as defined in 5.6/Q.2931 apply. + +Other information elements are mapped as defined in 6/Q.2931. + +#### 11.1.2.4 Connectionless bearer independent mechanism + +For mapping DSS 2 to DSS 1, the mappings shown in Table 16 shall apply. + +TABLE 16/Q.2932.1 + +##### DSS 2 to DSS 1 mapping + +| | | | +|---------------|---|---------------| +| DSS 2 message | | DSS 1 message | +| FACILITY | → | FACILITY | + +For mapping DSS 1 to DSS 2, the mappings shown in Table 17 shall apply. + +TABLE 17/Q.2932.1 + +##### DSS 1 to DSS 2 mapping + +| | | | +|---------------|---|---------------| +| DSS 1 message | | DSS 2 message | +| FACILITY | → | FACILITY | + +The contents of the following information elements are mapped in either direction: + +- facility information element; +- called party number information element; +- called party subaddress information element; +- notification indicator information element. + +The contents of the following information elements contained in the DSS 2 protocol are discarded: + +- calling party number information element. + +The DSS 2 Facility information element is mapped to the DSS 1 Facility information element by removing its second octet and adjusting the length indication without causing other changes to the contents. + +The DSS 1 Facility information element is mapped to the DSS 2 Facility information element by inserting the second octet and changing length indication field from one to two octets, adjusting the length accordingly, without causing other changes to the contents. The flag bit in the second octet is set to "0", i.e. the normal error handling procedures as defined in 5.6/Q.2931 apply. + +Other information elements are mapped as defined in 6/Q.2931. + +## **11.2 Interworking with non-ISDNs** + +Interworking of the generic functional protocol with non-ISDNs is not possible. + +All information received within the DSS 2 protocol relating to the generic functional protocol is discarded at the interworking function. + +## **11.3 Interworking with frame-relay** + +Interworking of the generic functional protocol with frame-relay is not possible. + +All information received within the DSS 2 protocol relating to the generic functional protocol is discarded at the interworking function. + +## **11.4 Interworking with PSPDNs** + +Interworking of the generic functional protocol with PSPDNs is not possible. + +All information received within the DSS 2 protocol relating to the generic functional protocol is discarded at the interworking function. + +# **12 Parameter values** + +## **12.1 Connection-oriented bearer-independent transport** + +Table 18 defines the values and attributes of the protocol timers required for the connection-oriented bearer-independent transport entity. + +In Table 18, the following conventions are used to indicate the applicability of the protocol timers to an incoming transport entity or outgoing transport entity: + +M: The support of the timer is Mandatory. + +O: The support of the timer is Optional. + +M(I): The support of the timer is Mandatory if the associated (optional) procedures are implemented. + +All timer values given in Table 18 shall have a tolerance of 10%. Where minimum and maximum values are given, the choice of value is an implementation matter, within the range specified, with a tolerance of 10% below the minimum value and 10% above the maximum value. + +TABLE 18/Q.2932.1 + +### **Transport entity timer values** + +| Timer number | Timer value | Call state | Cause for start | Normally terminated | Action to be taken when timer expires | Incoming transport entity | Outgoing transport entity | +|--------------|-----------------------------|----------------------------------|---------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------|---------------------------| +| T303 | Minimum 4 s,
Maximum 6 s | Call initiated | On Sending CO-BI SETUP | On receipt of CALL PROCEEDING, CONNECT or RELEASE COMPLETE | Release the connection as specified in 9.1.3.8 | | M | +| T308 | Minimum 4 s,
Maximum 6 s | Release Request | On Sending RELEASE | On Receiving RELEASE or RELEASE COMPLETE | Retransmit RELEASE, restart T308 | M | M | +| Second T308 | Minimum 4 s,
Maximum 6 s | Release Request | On expiry of T308 | On receiving RELEASE or RELEASE COMPLETE | Release Call Reference | M | M | +| T309 | 10 s | Any state | SAAL disconnection. Connections in Stable states are not lost | On SAAL reconnected | Release connection and call reference | M | M | +| T322 | Minimum 4 s,
Maximum 6 s | Any connection state except Null | STATUS ENQUIRY sent | STATUS, RELEASE or RELEASE COMPLETE received | STATUS ENQUIRY may be transmitted several times - implementation dependent. | M (I) | M (I) | + +TABLE 19/Q.2932.1 + +### **GFT-Control timer values** + +| Timer number | Timer value | State | Cause for start | Normally terminated | Action to be taken when timer expires | Incoming entity | Outgoing entity | +|--------------|-------------|-------|-------------------------------------------|---------------------------------------------------------------|------------------------------------------------|-----------------|-----------------| +| T310 | 30 s | Idle | On receipt of CO-BI-proceeding.indication | On receipt of CO-BI-Setup.confirm or CO-BI-release.indication | Release the connection as specified in 9.1.3.8 | | M | + +# **13 Dynamic description (SDLs)** + +The Specification and Description Language (SDL) diagrams are provided according to ITU-T Recommendation Z.100 [16]. + +## **13.1 Block overview diagram** + +The block overview diagram for a DSS 2 protocol with the minimum required for the generic functional protocol is shown in Figure 7. + +## **13.2 Coordination function** + +The additional SDL diagrams for the coordination function of Recommendation Q.2931 [13] Coord-N and Coord-U are shown in Figures 8 and 9, respectively. + +## **13.3 Component transport mechanisms** + +### **13.3.1 Bearer-related transport mechanism** + +The additional SDL diagrams for the bearer-related transport mechanism for the network (Q.2931\_N) and for the user (Q.2931\_U) are shown in Figures 10 and 11, respectively. + +### **13.3.2 Connection-oriented bearer-independent transport mechanism** + +The SDL diagram for the connection-oriented bearer-independent transport mechanism is shown in Figure 12. + +### **13.3.3 Connectionless bearer-independent transport mechanism** + +The SDL diagram for the connectionless bearer-independent transport mechanism is shown in Figure 13. + +## **13.4 Generic functional transport control (GFT-Control)** + +The SDL diagram for GFT-Control is shown in Figure 14. + +The procedure for determine destination is shown in Figure 15. + +The procedures for the MSN supplementary service are shown in Figures 16 and 18. + +The procedures for the SUB supplementary service are shown in Figures 17 and 19. + +![Block overview diagram for DSS2_protocol showing a central Coordination_function (1, 1) connected to various external entities: AS-Control, ROSE (O, N), GFT_Control (O, N), CO bearer_independent (O, N), CL bearer_independent (O, 1), Q.2931_U, and Q.2931_N. It also shows interfaces for AP and SAAL.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +Block DSS2\_protocol + +The diagram illustrates the block overview for the DSS2\_protocol. At the center is a block labeled **Coordination\_function (1, 1)**. To its left, a bracket groups two interfaces: **From-AP / To-AP** and **From-SAAL / To-SAAL**. To the right of the central block, seven external entities are shown, each with bidirectional communication lines (solid for CD to entity, dashed for entity to CD): + +- AS-Control**: CD to AS, AS to CD +- ROSE (O, N)**: CD to RO, RO to CD +- GFT\_Control (O, N)**: CD to GF, GF to CD +- CO bearer\_independent (O, N)**: CD to CO, CO to CD +- CL bearer\_independent (O, 1)**: CD to CL, CL to CD +- Q.2931\_U**: CD to QU, QU to CD +- Q.2931\_N**: CD to QN, QN to CD + +This represents the Q.2931 Co-ord-N and Co-ord-U processes. For editorial convenience, both the Q.2931\_U and Q.2931\_N processes are shown dependent on a single coordination function. + +Block overview diagram for DSS2\_protocol showing a central Coordination\_function (1, 1) connected to various external entities: AS-Control, ROSE (O, N), GFT\_Control (O, N), CO bearer\_independent (O, N), CL bearer\_independent (O, 1), Q.2931\_U, and Q.2931\_N. It also shows interfaces for AP and SAAL. + +T1179590-96 + +FIGURE 7/Q.2932.1 +**Block overview diagram** + +![Flowchart for PROCESS Co-ord-N. The process starts at CN0 - AAL Connection Released, followed by CO_BI_Setup.request (#), CO_bearer_independent, CO_BI_setup.request (#) /*To CO_bearer_independent */. It then checks for ACTIVE T309. If No, it sets NOW+t309 for Timer T309. If Yes, it skips the timer setting. Both paths lead to CN1 - AAL Awaiting Establish. A note indicates this transition is additional to page 4 of 10 of the Q.2931 Co-ord-N Process. Reference T1179600-96.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +``` + +graph TD + CN0([CN0 - AAL Connection Released]) --> CO_BI_Setup[CO_BI_Setup.request (#)] + CO_BI_Setup --> CO_bearer[CO_bearer_independent] + CO_bearer --> CO_BI_setup[CO_BI_setup.request (#) +/*To CO_bearer_independent */] + CO_BI_setup --> AAL_ESTABLISH[AAL_ESTABLISH request] + AAL_ESTABLISH --> ACTIVE_T309{ACTIVE T309} + ACTIVE_T309 -- No --> SET_TIMER[SET(NOW+t309, Timer T309)] + ACTIVE_T309 -- Yes --> CN1 + SET_TIMER --> CN1 + CN1([CN1 - AAL Awaiting Establish]) + Note[This transition is additional to page 4 of 10 of the Q.2931 Co-ord-N Process] + Ref[T1179600-96] + +``` + +Flowchart for PROCESS Co-ord-N. The process starts at CN0 - AAL Connection Released, followed by CO\_BI\_Setup.request (#), CO\_bearer\_independent, CO\_BI\_setup.request (#) /\*To CO\_bearer\_independent \*/. It then checks for ACTIVE T309. If No, it sets NOW+t309 for Timer T309. If Yes, it skips the timer setting. Both paths lead to CN1 - AAL Awaiting Establish. A note indicates this transition is additional to page 4 of 10 of the Q.2931 Co-ord-N Process. Reference T1179600-96. + +FIGURE 8/Q.2932.1 (sheet 1 of 7) + +### **PROCESS Co-ord-N** + +![Flowchart for PROCESS Co-ord-N. The process starts with 'CN3 - AAL Connection Established', followed by 'AAL-DATA-ind. (#) /* From SAAL */', and 'Check-Msg (#)'. It then enters a loop: 'Q.2932 Protocol Discriminator' (No leads to 'CN3 - AAL Connection Established', Yes leads to 'Message Length <9 octets'). 'Message Length <9 octets' (Yes leads to 'Q.2932 Protocol Discriminator', No leads to 'Valid Call Reference format'). 'Valid Call Reference format' (No leads to 'CN3 - AAL Connection Established', Yes leads to 'Call Reference = Dummy'). 'Call Reference = Dummy' (Yes leads to 'To Connectionless Bearer Independent Procedure', No leads to 'Call Reference = Global'). 'Call Reference = Global' (Yes leads to 'To Global Call Reference Procedures', No leads to 'Call Reference recognized'). 'Call Reference recognized' (Yes leads to 'To Q.2931 Protocol Related Procedures', No leads to 'To ](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +This transition replaces the equivalent transition on page 6 of 10 of the Q.2931 Co-ord-N Process + +``` + +graph TD + Start([CN3 - AAL Connection Established]) --> Input[/AAL-DATA-ind. (#) +/* From SAAL *// + Input --> Process[Check-Msg (#)] + Process --> Decision1{Q.2932 Protocol Discriminator} + Decision1 -- No --> End([CN3 - AAL Connection Established]) + Decision1 -- Yes --> Decision2{Message Length <9 octets} + Decision2 -- Yes --> Decision1 + Decision2 -- No --> Decision3{Valid Call Reference format} + Decision3 -- No --> End + Decision3 -- Yes --> Decision4{Call Reference = Dummy} + Decision4 -- Yes --> V((V)) + V -.-> V_Proc[To Connectionless Bearer Independent Procedure] + Decision4 -- No --> Decision5{Call Reference = Global} + Decision5 -- Yes --> X((X)) + X -.-> X_Proc[To Global Call Reference Procedures] + Decision5 -- No --> Decision6{Call Reference recognized} + Decision6 -- No --> Z((Z)) + Z -.-> Z_Proc[To "No Protocol" Procedure] + Decision6 -- Yes --> Y((Y)) + Y -.-> Y_Proc[To Q.2931 Protocol Related Procedures] + +``` + +T1179610-96 + +Flowchart for PROCESS Co-ord-N. The process starts with 'CN3 - AAL Connection Established', followed by 'AAL-DATA-ind. (#) /\* From SAAL \*/', and 'Check-Msg (#)'. It then enters a loop: 'Q.2932 Protocol Discriminator' (No leads to 'CN3 - AAL Connection Established', Yes leads to 'Message Length <9 octets'). 'Message Length <9 octets' (Yes leads to 'Q.2932 Protocol Discriminator', No leads to 'Valid Call Reference format'). 'Valid Call Reference format' (No leads to 'CN3 - AAL Connection Established', Yes leads to 'Call Reference = Dummy'). 'Call Reference = Dummy' (Yes leads to 'To Connectionless Bearer Independent Procedure', No leads to 'Call Reference = Global'). 'Call Reference = Global' (Yes leads to 'To Global Call Reference Procedures', No leads to 'Call Reference recognized'). 'Call Reference recognized' (Yes leads to 'To Q.2931 Protocol Related Procedures', No leads to 'To + +FIGURE 8/Q.2932.1 (sheet 2 of 7) + +### **PROCESS Co-ord-N** + +![Flowchart for PROCESS Co-ord-N starting from connector Z. It branches by Message Type: RELEASE_COMPLETE(#), SETUP(#), OTHER(#), STATUS(#), and STATUS_ENQUIRY(#). Each branch contains decision diamonds (e.g., Call Ref. Flag = 0, CS=0) and process blocks (e.g., CO_bearer_independent, Q.2931-N, Cause:= 81). All branches lead to terminal states like 'CN3 - AAL Connection Established' or 'AAL-DATA.req. (#) / To SAAL */'.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +``` + +graph TD + Z((Z)) --> MT{Message Type} + MT -- RELEASE_COMPLETE(#) --> CRF1{Call Ref. Flag = 0} + MT -- SETUP(#) --> CRF2{Call Ref. Flag = 0} + MT -- OTHER(#) --> C81[Cause:= 81] + MT -- STATUS(#) --> CS0{CS=0} + MT -- STATUS_ENQUIRY(#) --> C30[Cause:= 30; CS:= 0] + + CRF1 -- No --> CRF2 + CRF1 -- Yes --> CBI[CO_bearer_independent] + CBI --> CBS1{{CO_BI_SETUP(#) / To CO-bearer_independent */}} + CBS1 --> CN3E1(CN3 - AAL Connection Established) + + CRF2 -- No --> C81 + CRF2 -- Yes --> Q2931N[Q.2931-N] + Q2931N --> S1{{SETUP(#) / To Q.2931-N */}} + S1 --> CN3E2(CN3 - AAL Connection Established) + + C81 --> BM1[Build-Msg (RELEASE-COMPLETE, Cause,#)] + BM1 --> AD1{{AAL-DATA.req. (#) / To SAAL */}} + AD1 --> CN3E3(CN3 - AAL Connection Established) + + CS0 -- No --> C101[Cause:= 101] + C101 --> C81 + + CS0 -- Yes --> CN3E4(CN3 - AAL Connection Established) + + C30 --> BM2[Build-Msg (STATUS, CS, Cause,#)] + BM2 --> AD2{{AAL-DATA.req. (#) / To SAAL */}} + AD2 --> CN3E4 + +``` + +This page replaces page 8 of 10 of Q.2931 Co-ord-N Process + +Flowchart for PROCESS Co-ord-N starting from connector Z. It branches by Message Type: RELEASE\_COMPLETE(#), SETUP(#), OTHER(#), STATUS(#), and STATUS\_ENQUIRY(#). Each branch contains decision diamonds (e.g., Call Ref. Flag = 0, CS=0) and process blocks (e.g., CO\_bearer\_independent, Q.2931-N, Cause:= 81). All branches lead to terminal states like 'CN3 - AAL Connection Established' or 'AAL-DATA.req. (#) / To SAAL \*/'. + +T1179620-96 + +FIGURE 8/Q.2932.1 (sheet 3 of 7) + +### **PROCESS Co-ord-N** + +![Flowchart for PROCESS Co-ord-N. It starts with a connector 'Y' leading to a decision 'Call Ref. initiated by'. From this decision, two paths emerge: 'CO_BI_SETUP' and 'SETUP'. Each path leads to a 'Message Type' decision. If 'Other', it leads to a 'Message (#)' block (one for CO_bearer_independent, one for Q.2931-N) and then to 'CN3 - AAL Connection Established'. If the main message type, it loops back to the 'Message Type' decision.](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +``` + +graph TD + Y((Y)) --> CallRef{Call Ref. +initiated by} + CallRef -- CO_BI_SETUP --> MT1{Message Type} + CallRef -- SETUP --> MT2{Message Type} + MT1 -- CO_BI_SETUP --> MT1 + MT1 -- Other --> M1{{Message (#) +/* To CO_bearer_ +independent */}} + M1 --> CN3_1([CN3 - AAL +Connection +Established]) + MT2 -- SETUP --> MT2 + MT2 -- Other --> M2{{Message (#) +/* To Q.2931-N */}} + M2 --> CN3_2([CN3 - AAL +Connection +Established]) + +``` + +Flowchart for PROCESS Co-ord-N. It starts with a connector 'Y' leading to a decision 'Call Ref. initiated by'. From this decision, two paths emerge: 'CO\_BI\_SETUP' and 'SETUP'. Each path leads to a 'Message Type' decision. If 'Other', it leads to a 'Message (#)' block (one for CO\_bearer\_independent, one for Q.2931-N) and then to 'CN3 - AAL Connection Established'. If the main message type, it loops back to the 'Message Type' decision. + +This page replaces +page 9 of 10 of +Q.2931 Co-ord-N +Process + +T1179630-96 + +FIGURE 8/Q.2932.1 (sheet 4 of 7) + +### **PROCESS Co-ord-N** + +![Flowchart for PROCESS Co-ord-N. It starts with a connector 'W' leading to a 'Primitive Type' decision diamond. The top section handles Q.2931-N primitives: Setup.req, Reset-req, Reset-resp, and Reset-error.resp. Setup.req goes to a 'Q.2931-N' block then to 'Setup.req. /* To Q.2931-N */'. Reset-req goes to 'Reset-req. (#) /*To Reset-Start-N*/'. Reset-resp and Reset-error.resp both go to 'Reset-req. (#) /*To Reset-Start-N*/'. All four paths lead to 'CN3 - AAL Connection Established'. The bottom section handles other primitives: 'All other Q.2931 and Q.2932 BR primitives' go to 'Primitive' /* To Q.2931-N */; 'CO_BI_Setup.request' goes to 'CO_bearer_independent' then to 'CO_BI_Setup.request /*To CO_bearer_independent */'; 'All other CO_BI_Q.2932 primitives' go to 'Primitive' /*To CO_bearer_independent */; 'CL_BI_UNITDATA.request' goes to 'CL_bearer_independent' then to 'CL_BI_UNITDATA.request /*To CL_bearer_independent */'. All four paths lead to 'CN3 - AAL Connection Established'. A note at the bottom left states 'This page replaces page 10 of 10 of Q.2931 Co-ord-N Process'. A label 'T1179640-96' is at the bottom right of the diagram.](89f8aefc01866631793087542316cef2_img.jpg) + +``` + +graph TD + W((W)) --> PT{Primitive Type} + PT -- Setup.req --> Q2931N[Q.2931-N] + PT -- Reset-req --> RR[Reset-req. (#) +/*To Reset-Start-N*/] + PT -- Reset-resp --> RR + PT -- Reset-error.resp --> RR + Q2931N --> SR[Setup.req. +/* To Q.2931-N */] + SR --> CN3AAL1((CN3 - AAL +Connection +Established)) + RR --> CN3AAL1 + A1[All other Q.2931 and +Q.2932 BR primitives] --> P1[Primitive +/* To Q.2931-N */] + P1 --> CN3AAL2((CN3 - AAL +Connection +Established)) + A2[CO_BI_Setup.request] --> BI1[CO_bearer_independent] + BI1 --> BI2[CO_BI_Setup.request +/*To CO_bearer_independent */] + BI2 --> CN3AAL2 + A3[All other CO_BI_Q.2932 +primitives] --> P2[Primitive +/*To CO_bearer_independent */] + P2 --> CN3AAL2 + A4[CL_BI_UNITDATA.request] --> BI3[CL_bearer_independent] + BI3 --> BI4[CL_BI_UNITDATA.request +/*To CL_bearer_independent */] + BI4 --> CN3AAL2 + +``` + +This page replaces page 10 of 10 of Q.2931 Co-ord-N Process + +T1179640-96 + +Flowchart for PROCESS Co-ord-N. It starts with a connector 'W' leading to a 'Primitive Type' decision diamond. The top section handles Q.2931-N primitives: Setup.req, Reset-req, Reset-resp, and Reset-error.resp. Setup.req goes to a 'Q.2931-N' block then to 'Setup.req. /\* To Q.2931-N \*/'. Reset-req goes to 'Reset-req. (#) /\*To Reset-Start-N\*/'. Reset-resp and Reset-error.resp both go to 'Reset-req. (#) /\*To Reset-Start-N\*/'. All four paths lead to 'CN3 - AAL Connection Established'. The bottom section handles other primitives: 'All other Q.2931 and Q.2932 BR primitives' go to 'Primitive' /\* To Q.2931-N \*/; 'CO\_BI\_Setup.request' goes to 'CO\_bearer\_independent' then to 'CO\_BI\_Setup.request /\*To CO\_bearer\_independent \*/'; 'All other CO\_BI\_Q.2932 primitives' go to 'Primitive' /\*To CO\_bearer\_independent \*/; 'CL\_BI\_UNITDATA.request' goes to 'CL\_bearer\_independent' then to 'CL\_BI\_UNITDATA.request /\*To CL\_bearer\_independent \*/'. All four paths lead to 'CN3 - AAL Connection Established'. A note at the bottom left states 'This page replaces page 10 of 10 of Q.2931 Co-ord-N Process'. A label 'T1179640-96' is at the bottom right of the diagram. + +FIGURE 8/Q.2932.1 (sheet 5 of 7) +**PROCESS Co-ord-N** + +![Flowcharts for PROCESS Co-ord-N. The top flowchart shows the initial connection establishment from a vertex 'V' through 'CL_bearer_independent' and a 'Message' to 'CN3 - AAL Connection Established'. The bottom flowcharts show data transfer paths: one from 'CN3 - AAL Connection Established' through 'Data.indication primitive' to 'GFT_Control' and back to 'CN3 - AAL Connection Established'; another from 'CN3 - AAL Connection Established' through 'GF-Data.request' to 'ROSE' and 'GFT_Control', and a third from 'CN3 - AAL Connection Established' through 'GF-Data.indication' to 'GFT_Control' and 'ROSE', both returning to 'CN3 - AAL Connection Established'. A note '/* From any transport */' is present in the first path.](a2251e3bbfcd726b68cc50b091e53b02_img.jpg) + +``` + +graph TD + V((V)) --> CL[CL_bearer_independent] + CL --> M[Message +/*To CL_bearer_independent */] + M --> CN3_1([CN3 - AAL Connection Established]) + + CN3_2([CN3 - AAL Connection Established]) --> D1{"Data.indication primitive"} + D1 --> D2{"Data.indication primitive" +/*To GFT_Control*/} + D2 --> CN3_3([CN3 - AAL Connection Established]) + D1 -.-> F["/* From any transport */"] + + CN3_4([CN3 - AAL Connection Established]) --> GF1{"GF-Data.request +/*From ROSE*/"} + GF1 --> GF2{"GF-Data.request +/*To GFT_Control*/"} + GF2 --> CN3_5([CN3 - AAL Connection Established]) + + CN3_6([CN3 - AAL Connection Established]) --> GF3{"GF-Data.indication +/*From GFT_Control */"} + GF3 --> GF4{"GF-Data.indication +/*To ROSE */"} + GF4 --> CN3_7([CN3 - AAL Connection Established]) + +``` + +Flowcharts for PROCESS Co-ord-N. The top flowchart shows the initial connection establishment from a vertex 'V' through 'CL\_bearer\_independent' and a 'Message' to 'CN3 - AAL Connection Established'. The bottom flowcharts show data transfer paths: one from 'CN3 - AAL Connection Established' through 'Data.indication primitive' to 'GFT\_Control' and back to 'CN3 - AAL Connection Established'; another from 'CN3 - AAL Connection Established' through 'GF-Data.request' to 'ROSE' and 'GFT\_Control', and a third from 'CN3 - AAL Connection Established' through 'GF-Data.indication' to 'GFT\_Control' and 'ROSE', both returning to 'CN3 - AAL Connection Established'. A note '/\* From any transport \*/' is present in the first path. + +T1179650-96 + +FIGURE 8/Q.2932.1 (sheet 6 of 7) + +### **PROCESS Co-ord-N** + +![Flowchart showing the establishment of CN3 - AAL connections through three parallel paths: BR-Data, CO-BI-Data, and CL_BI_UNITDATA. The process starts with 'CN3 - AAL Connection Established', branches into three request boxes (From GFT_Control), then into three corresponding request boxes (To specific bearers), and finally converges back to 'CN3 - AAL Connection Established'.](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +``` + +graph TD + Start([CN3 - AAL Connection Established]) --> BR1[BR-Data.request +/*From GFT_ +Control */] + Start --> CO1[CO-BI-Data.request +/*From GFT_ +Control */] + Start --> CL1[CL_BI_UNITDATA.request +/*From GFT_ +Control */] + BR1 --> BR2[BR-Data.request +/*To Q.2931-N */] + CO1 --> CO2[CO-BI-Data.Request +/*To CO_BI_bearer_ +independent */] + CL1 --> CL2[CL_BI_UNITDATA.request +/*To CL_Bearer_ +independent */] + BR2 --> End([CN3 - AAL Connection Established]) + CO2 --> End + CL2 --> End + +``` + +Flowchart showing the establishment of CN3 - AAL connections through three parallel paths: BR-Data, CO-BI-Data, and CL\_BI\_UNITDATA. The process starts with 'CN3 - AAL Connection Established', branches into three request boxes (From GFT\_Control), then into three corresponding request boxes (To specific bearers), and finally converges back to 'CN3 - AAL Connection Established'. + +T1179660-96 + +The creation of particular transport processes and GFT\_Control processes is not shown here. However, this has to be coordinated by the Co-ord process as well + +FIGURE 8/Q.2932.1 (sheet 7 of 7) + +### **PROCESS Co-ord-N** + +![Flowchart for PROCESS Co-ord-U. The sequence starts with 'CU0 - AAL Connection Released' (oval), followed by 'CO_BI_ Setup.request (#)' (parallelogram), 'CO_bearer_independent' (rectangle), 'CO_BI_setup.request (#) /*To CO_bearer_independent */' (parallelogram), 'AAL_ESTABLISH request' (parallelogram), 'ACTIVE T309' (diamond), 'SET(NOW+t309, Timer T309)' (rectangle), and ends with 'CU1 - AAL Awaiting Establish' (oval). A 'Yes' branch from the diamond loops back to the transition before the final oval.](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +``` + +graph TD + CU0([CU0 - AAL Connection Released]) --> CO_BI_Setup[CO_BI_ Setup.request (#)] + CO_BI_Setup --> CO_bearer[CO_bearer_independent] + CO_bearer --> CO_BI_setup[CO_BI_setup.request (#) +/*To CO_bearer_independent */] + CO_BI_setup --> AAL_ESTABLISH[AAL_ESTABLISH request] + AAL_ESTABLISH --> ACTIVE_T309{ACTIVE T309} + ACTIVE_T309 -- Yes --> CU1 + ACTIVE_T309 -- No --> SET_TIMER[SET(NOW+t309, Timer T309)] + SET_TIMER --> CU1 + CU1([CU1 - AAL Awaiting Establish]) + +``` + +Flowchart for PROCESS Co-ord-U. The sequence starts with 'CU0 - AAL Connection Released' (oval), followed by 'CO\_BI\_ Setup.request (#)' (parallelogram), 'CO\_bearer\_independent' (rectangle), 'CO\_BI\_setup.request (#) /\*To CO\_bearer\_independent \*/' (parallelogram), 'AAL\_ESTABLISH request' (parallelogram), 'ACTIVE T309' (diamond), 'SET(NOW+t309, Timer T309)' (rectangle), and ends with 'CU1 - AAL Awaiting Establish' (oval). A 'Yes' branch from the diamond loops back to the transition before the final oval. + +This transition is additional to page 4 of 10 of the Q.2931 Co-ord-U Process + +T1179670-96 + +FIGURE 9/Q.2932.1 (sheet 1 of 7) +**PROCESS Co-ord-U** + +![Flowchart for PROCESS Co-ord-U. The process starts with 'CU3 - AAL Connection Established', followed by 'AAL-DATA-ind. (#) /*From SAAL */', and 'Check-Msg (#)'. It then enters a loop of decision diamonds: 'Q.2932 Protocol Discriminator', 'Message Length <9 octets', and 'Valid Call Reference format'. If any of these are 'No', it returns to 'CU3 - AAL Connection Established'. If all are 'Yes', it checks 'Call Reference = Dummy', 'Call Reference = Global', and 'Call Reference recognized'. Depending on these checks, it leads to connector 'V' (To Connectionless Bearer Independent Procedure), connector 'X' (To Global Call Reference Procedures), connector 'Z' (To "No Protocol" Procedure), or connector 'Y' (To Q.2931 Protocol Related Procedures). A note indicates this transition replaces the equivalent transition on page 6 of 10 of the Q.2931 Co-ord-U Process. The code T1179680-96 is at the bottom right.](51d4540605fdfa2c090638305022143b_img.jpg) + +``` + +graph TD + Start([CU3 - AAL Connection Established]) --> Input[/AAL-DATA-ind. (#) +/*From SAAL *// + Input --> Process[Check-Msg (#)] + Process --> Decision1{Q.2932 Protocol Discriminator} + Decision1 -- No --> End([CU3 - AAL Connection Established]) + Decision1 -- Yes --> Decision2{Message Length <9 octets} + Decision2 -- Yes --> End + Decision2 -- No --> Decision3{Valid Call Reference format} + Decision3 -- No --> End + Decision3 -- Yes --> Decision4{Call Reference = Dummy} + Decision4 -- Yes --> V((V)) + V -.-> V_Proc[To Connectionless Bearer Independent Procedure] + Decision4 -- No --> Decision5{Call Reference = Global} + Decision5 -- Yes --> X((X)) + X -.-> X_Proc[To Global Call Reference Procedures] + Decision5 -- No --> Decision6{Call Reference recognized} + Decision6 -- No --> Z((Z)) + Z -.-> Z_Proc[To "No Protocol" Procedure] + Decision6 -- Yes --> Y((Y)) + Y -.-> Y_Proc[To Q.2931 Protocol Related Procedures] + +``` + +This transition replaces the equivalent transition on page 6 of 10 of the Q.2931 Co-ord-U Process + +T1179680-96 + +Flowchart for PROCESS Co-ord-U. The process starts with 'CU3 - AAL Connection Established', followed by 'AAL-DATA-ind. (#) /\*From SAAL \*/', and 'Check-Msg (#)'. It then enters a loop of decision diamonds: 'Q.2932 Protocol Discriminator', 'Message Length <9 octets', and 'Valid Call Reference format'. If any of these are 'No', it returns to 'CU3 - AAL Connection Established'. If all are 'Yes', it checks 'Call Reference = Dummy', 'Call Reference = Global', and 'Call Reference recognized'. Depending on these checks, it leads to connector 'V' (To Connectionless Bearer Independent Procedure), connector 'X' (To Global Call Reference Procedures), connector 'Z' (To "No Protocol" Procedure), or connector 'Y' (To Q.2931 Protocol Related Procedures). A note indicates this transition replaces the equivalent transition on page 6 of 10 of the Q.2931 Co-ord-U Process. The code T1179680-96 is at the bottom right. + +FIGURE 9/Q.2932.1 (sheet 2 of 7) + +### **PROCESS Co-ord-U** + +![Flowchart for PROCESS Co-ord-U starting from CO_BI_SETUP(#). It branches based on Message Type: RELEASE_COMPLETE(#), SETUP(#), OTHER(#), STATUS(#), and STATUS_ENQUIRY(#). Each branch leads to specific processing steps like CO_bearer_independent, Q.2931-N, or various cause codes (81, 101, 30), eventually leading to AAL connection establishment (CU3 or CN3).](c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg) + +``` + +graph TD + Start((Z)) --> MT{Message Type} + MT -- RELEASE_COMPLETE(#) --> CRF1{Call Ref. Flag = 0} + CRF1 -- No --> CRF2{Call Ref. Flag = 0} + CRF1 -- Yes --> COBI[CO_bearer_independent] + COBI --> COBIS[CO_BI_SETUP(#) +/*To CO-bearer_independent */] + COBIS --> CU3A((CU3 - AAL Connection Established)) + CRF2 -- No --> MT + CRF2 -- Yes --> Q2931N[Q.2931-N] + Q2931N --> S[SETUP(#) +/*To Q.2931-U */] + S --> CU3A + MT -- SETUP(#) --> CRF2 + MT -- OTHER(#) --> C81[Cause:= 81] + C81 --> BM[Build-Msg +(RELEASE-COMPLETE, Cause,#)] + BM --> AD[AAL-DATA-req. +(#) +/*To SAAL */] + AD --> CU3A + MT -- STATUS(#) --> CS0{CS=0} + CS0 -- No --> C101[Cause:= 101] + CS0 -- Yes --> CN3A((CN3 - AAL Connection Established)) + C101 --> BM + MT -- STATUS_ENQUIRY(#) --> C30[Cause:= 30; +CS:= 0] + C30 --> BM2[Build-Msg +(STATUS,CS, Cause,#)] + BM2 --> AD2[AAL-DATA-req. +(#) +/*To SAAL */] + AD2 --> CN3A + +``` + +This page replaces +page 8 of 10 of Q.2931 +Co-ord-U Process + +Flowchart for PROCESS Co-ord-U starting from CO\_BI\_SETUP(#). It branches based on Message Type: RELEASE\_COMPLETE(#), SETUP(#), OTHER(#), STATUS(#), and STATUS\_ENQUIRY(#). Each branch leads to specific processing steps like CO\_bearer\_independent, Q.2931-N, or various cause codes (81, 101, 30), eventually leading to AAL connection establishment (CU3 or CN3). + +T1179690-96 + +FIGURE 9/Q.2932.1 (sheet 3 of 7) +**PROCESS Co-ord-U** + +![Flowchart for PROCESS Co-ord-U. It starts with a circle 'Y' leading to a decision 'Call Ref. initiated by'. Two branches, 'CO_BI_SETUP' and 'SETUP', lead to 'Message Type' decision diamonds. Both have 'Other' paths leading to 'Message (#)' boxes ('/*To CO_bearer_independent */' and '/*To Q.2931-U */') which then lead to 'CU3 - AAL Connection Established' oval shapes. There are also direct paths from the 'Message Type' diamonds to the final oval shapes.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +``` + +graph TD + Y((Y)) --> CallRef{Call Ref. +initiated +by} + CallRef -- CO_BI_SETUP --> MT1{Message Type} + CallRef -- SETUP --> MT2{Message Type} + MT1 -- CO_BI_SETUP --> CU3_1([CU3 - AAL +Connection +Established]) + MT1 -- Other --> M1{{Message (#) +/*To CO_bearer_ +independent */}} + M1 --> CU3_1 + MT2 -- SETUP --> CU3_2([CU3 - AAL +Connection +Established]) + MT2 -- Other --> M2{{Message (#) +/*To Q.2931-U */}} + M2 --> CU3_2 + +``` + +Flowchart for PROCESS Co-ord-U. It starts with a circle 'Y' leading to a decision 'Call Ref. initiated by'. Two branches, 'CO\_BI\_SETUP' and 'SETUP', lead to 'Message Type' decision diamonds. Both have 'Other' paths leading to 'Message (#)' boxes ('/\*To CO\_bearer\_independent \*/' and '/\*To Q.2931-U \*/') which then lead to 'CU3 - AAL Connection Established' oval shapes. There are also direct paths from the 'Message Type' diamonds to the final oval shapes. + +This page replaces +page 9 of 10 of Q.2931 +Co-ord-U Process + +T1179700-96 + +FIGURE 9/Q.2932.1 (sheet 4 of 7) + +### **PROCESS Co-ord-U** + +![Flowchart for PROCESS Co-ord-U. It starts with a connector 'W' leading to a 'Primitive Type' decision diamond. The first path handles Q.2931-U primitives: Setup.req., Reset-resp., Reset-req., and Reset-error.resp., leading to 'CU3 - AAL Connection Established'. The second path handles other primitives: 'All other Q.2931 and Q.2932 BR primitives', 'CO_BI_Setup.request', 'All other CO_BI_Q.2932 primitives', and 'CL_BI_UNITDATA.request', which are processed through bearer-independent blocks and then lead to 'CU3 - AAL Connection Established'. A note at the bottom left indicates this page replaces page 10 of 10 of Q.2931 Co-ord-U Process. The diagram is labeled T1179710-96.](7e14467740b2570a44379b347a697921_img.jpg) + +``` + +graph TD + W((W)) --> PT{Primitive Type} + PT -- Setup.req. --> Q2931U[Q.2931-U] + PT -- Reset-resp. --> RR["Reset-resp. (#) +/*To Reset-resp-U*/"] + PT -- Reset-req. --> RQ["Reset-req. (#) +/*To Reset-Start-U*/"] + PT -- Reset-error-resp. --> RE["Reset-resp. (#) +/*To Reset-resp-U*/"] + Q2931U --> SR["Setup.req. +/*To Q.2931-U*/"] + RR --> CU3_1([CU3 - AAL +Connection +Established]) + RQ --> CU3_1 + RE --> CU3_1 + SR --> CU3_1 + PT -- "All other Q.2931 and +Q.2932 BR primitives" --> P["\"Primitive\" +/*To +Q.2931-U*/"] + PT -- "CO_BI_Setup +.request" --> CBI["CO_bearer_ +independent"] + PT -- "All other CO_BI_Q.2932 +primitives" --> PI["\"Primitive\" +/*To +CO_bearer_ +independent */"] + PT -- "CL_BI_UNITDATA +.request" --> CLBI["CL_bearer_ +independent"] + P --> CU3_2([CU3 - AAL +Connection +Established]) + CBI --> CBSR["CO_BI_Setup.request +/*To CO_bearer_ +independent */"] + CBSR --> CU3_2 + PI --> CU3_2 + CLBI --> CLBUR["CL_BI_ +UNITDATA.request +/*To CL_bearer_ +independent */"] + CLBUR --> CU3_2 + T1179710-96[T1179710-96] + +``` + +This page replaces +page 10 of 10 of +Q.2931 Co-ord-U +Process + +Flowchart for PROCESS Co-ord-U. It starts with a connector 'W' leading to a 'Primitive Type' decision diamond. The first path handles Q.2931-U primitives: Setup.req., Reset-resp., Reset-req., and Reset-error.resp., leading to 'CU3 - AAL Connection Established'. The second path handles other primitives: 'All other Q.2931 and Q.2932 BR primitives', 'CO\_BI\_Setup.request', 'All other CO\_BI\_Q.2932 primitives', and 'CL\_BI\_UNITDATA.request', which are processed through bearer-independent blocks and then lead to 'CU3 - AAL Connection Established'. A note at the bottom left indicates this page replaces page 10 of 10 of Q.2931 Co-ord-U Process. The diagram is labeled T1179710-96. + +FIGURE 9/Q.2932.1 (sheet 5 of 7) +**PROCESS Co-ord-U** + +![Flowchart for PROCESS Co-ord-U. The diagram shows three main flow paths. The top path starts with a circle 'V', leading to a box 'CL_bearer_independent', then a message 'Message' /To CL_bearer_independent*/ , and finally a state 'CU3 - AAL Connection Established'. The bottom-left path starts with a state 'CU3 - AAL Connection Established', followed by a message 'Data.indication primitive' /From any transport*/ , then a message 'Data.indication primitive' /To GFT_Control*/ , and ends with a state 'CU3 - AAL Connection Established'. The bottom-right path starts with a state 'CU3 - AAL Connection Established', which branches into two parallel messages: 'GF-Data.request' /From ROSE*/ and 'GF-Data.indication' /From GFT_Control*/ . These lead to 'GF-Data.request' /To GFT_Control*/ and 'GF-Data.indication' /To ROSE*/ respectively, which then converge to a final state 'CU3 - AAL Connection Established'.](5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg) + +``` + +graph TD + V((V)) --> CL[CL_bearer_independent] + CL --> M1{"Message" /To CL_bearer_independent*/} + M1 --> S1([CU3 - AAL Connection Established]) + + S2([CU3 - AAL Connection Established]) --> M2{"Data.indication primitive" /From any transport*/} + M2 --> M3{"Data.indication primitive" /To GFT_Control*/} + M3 --> S3([CU3 - AAL Connection Established]) + + S4([CU3 - AAL Connection Established]) --> M4{"GF-Data.request" /From ROSE*/} + S4 --> M5{"GF-Data.indication" /From GFT_Control*/} + M4 --> M6{"GF-Data.request" /To GFT_Control*/} + M5 --> M7{"GF-Data.indication" /To ROSE*/} + M6 --> S5([CU3 - AAL Connection Established]) + M7 --> S5 + +``` + +Flowchart for PROCESS Co-ord-U. The diagram shows three main flow paths. The top path starts with a circle 'V', leading to a box 'CL\_bearer\_independent', then a message 'Message' /To CL\_bearer\_independent\*/ , and finally a state 'CU3 - AAL Connection Established'. The bottom-left path starts with a state 'CU3 - AAL Connection Established', followed by a message 'Data.indication primitive' /From any transport\*/ , then a message 'Data.indication primitive' /To GFT\_Control\*/ , and ends with a state 'CU3 - AAL Connection Established'. The bottom-right path starts with a state 'CU3 - AAL Connection Established', which branches into two parallel messages: 'GF-Data.request' /From ROSE\*/ and 'GF-Data.indication' /From GFT\_Control\*/ . These lead to 'GF-Data.request' /To GFT\_Control\*/ and 'GF-Data.indication' /To ROSE\*/ respectively, which then converge to a final state 'CU3 - AAL Connection Established'. + +T1179720-96 + +FIGURE 9/Q.2932.1 (sheet 6 of 7) + +### **PROCESS Co-ord-U** + +![Flowchart for PROCESS Co-ord-U showing the sequence of data requests following a CU3 - AAL Connection Established. The process starts with an oval 'CU3 - AAL Connection Established', leading to three parallel request boxes: 'BR-Data.request /*From GFT_Control*/', 'CO-BI-Data.request /*From GFT_Control*/', and 'CL-BI-UNITDATA.request /*From GFT_Control*/'. These lead to three corresponding request boxes: 'BR-Data.request /*To Q.2931-U*/', 'CO-BI-Data.request /*To CO_bearer_independent*/', and 'CL-BI-UNITDATA.request /*To CL_bearer_independent*/'. All three converge to a final oval 'CU3 - AAL Connection Established'.](87c64bd7d33fca8b9b29228c80ddf175_img.jpg) + +``` + +graph TD + Start([CU3 - AAL Connection Established]) --> BR1[BR-Data.request +/*From GFT_Control*/] + Start --> CO1[CO-BI-Data.request +/*From GFT_Control*/] + Start --> CL1[CL-BI-UNITDATA.request +/*From GFT_Control*/] + BR1 --> BR2[BR-Data.request +/*To Q.2931-U*/] + CO1 --> CO2[CO-BI-Data.request +/*To CO_bearer_independent*/] + CL1 --> CL2[CL-BI-UNITDATA.request +/*To CL_bearer_independent*/] + BR2 --> End([CU3 - AAL Connection Established]) + CO2 --> End + CL2 --> End + +``` + +Flowchart for PROCESS Co-ord-U showing the sequence of data requests following a CU3 - AAL Connection Established. The process starts with an oval 'CU3 - AAL Connection Established', leading to three parallel request boxes: 'BR-Data.request /\*From GFT\_Control\*/', 'CO-BI-Data.request /\*From GFT\_Control\*/', and 'CL-BI-UNITDATA.request /\*From GFT\_Control\*/'. These lead to three corresponding request boxes: 'BR-Data.request /\*To Q.2931-U\*/', 'CO-BI-Data.request /\*To CO\_bearer\_independent\*/', and 'CL-BI-UNITDATA.request /\*To CL\_bearer\_independent\*/'. All three converge to a final oval 'CU3 - AAL Connection Established'. + +T1179730-96 + +FIGURE 9/Q.2932.1 (sheet 7 of 7) + +### **PROCESS Co-ord-U** + +![Flowchart for Process Q.2931_N. The process starts with BR-Data -req (#) and FACILITY (#) inputs. BR-Data -req (#) leads to FACILITY (#) which leads to a connector '-'. FACILITY (#) also leads to Verify-Msg. Verify-Msg leads to a 'Result' decision diamond. The 'Result' diamond has five outcomes: RAP, OK, CLR, I, and RAI. RAP leads to STATUS (Cause, CS) which leads to BR-Data -ind (#) which leads to a connector '-'. OK leads to BR-Data -ind (#) which leads to a connector '-'. CLR leads to a connector 'D'. I leads to STATUS (Cause, CS) which leads to a connector '-'. RAI leads to STATUS (Cause, CS) which leads to a connector '-'. There are also connectors '-' from the first connector '-' and from the connector 'D'. A note at the bottom left explains that this page is part of the Q.2931_N process defined in Recommendation Q.2931 [13]. A note at the bottom right explains that Verify-Msg verifies messages based on message encoding rules and lists result abbreviations: RAI (Report and Ignore), RAP (Report and Proceed), CLR (Release Call), OK (OK), and I (Ignore).](352d21d1e740e4a58cb17ab8656cfad8_img.jpg) + +\* (except N0, N1, N6, N11, N12) --- 9.1.1.1 + +``` + +graph TD + subgraph Start + A["* (except N0, N1, N6, N11, N12)"] --- B[9.1.1.1] + end + B --> BRDataReq["BR-Data -req (#)"] + B --> Facility1["FACILITY (#)"] + BRDataReq --> Facility2["FACILITY (#)"] + Facility2 --> Connector1[(-)] + Facility1 --> VerifyMsg[Verify-Msg] + VerifyMsg --> Result{Result} + Result -- RAP --> Status1["STATUS (Cause, CS)"] + Status1 --> BRDataInd1["BR-Data -ind (#)"] + BRDataInd1 --> Connector2[(-)] + Result -- OK --> BRDataInd2["BR-Data -ind (#)"] + BRDataInd2 --> Connector3[(-)] + Result -- CLR --> Connector4((D)) + Connector4 --> Connector5[(-)] + Result -- I --> Status2["STATUS (Cause, CS)"] + Status2 --> Connector6[(-)] + Result -- RAI --> Status3["STATUS (Cause, CS)"] + Status3 --> Connector7[(-)] + Status1 -.-> CS1["CS= previous state"] + Status2 -.-> CS2["CS= previous state"] + +``` + +This page forms part of the Q.2931\_N process defined in Recommendation Q.2931 [13] and provides additional transitions that are required when the bearer-related transport mechanisms are implemented + +Verify-Msg verifies messages based on message encoding rules. It removes unacceptable information elements and returns the result in the result and cause variables. + Result abbreviations are: + RAI - Report and Ignore + RAP - Report and Proceed + CLR - Release Call + OK - OK + I - Ignore + +Flowchart for Process Q.2931\_N. The process starts with BR-Data -req (#) and FACILITY (#) inputs. BR-Data -req (#) leads to FACILITY (#) which leads to a connector '-'. FACILITY (#) also leads to Verify-Msg. Verify-Msg leads to a 'Result' decision diamond. The 'Result' diamond has five outcomes: RAP, OK, CLR, I, and RAI. RAP leads to STATUS (Cause, CS) which leads to BR-Data -ind (#) which leads to a connector '-'. OK leads to BR-Data -ind (#) which leads to a connector '-'. CLR leads to a connector 'D'. I leads to STATUS (Cause, CS) which leads to a connector '-'. RAI leads to STATUS (Cause, CS) which leads to a connector '-'. There are also connectors '-' from the first connector '-' and from the connector 'D'. A note at the bottom left explains that this page is part of the Q.2931\_N process defined in Recommendation Q.2931 [13]. A note at the bottom right explains that Verify-Msg verifies messages based on message encoding rules and lists result abbreviations: RAI (Report and Ignore), RAP (Report and Proceed), CLR (Release Call), OK (OK), and I (Ignore). + +T1179740-96 + +FIGURE 10/Q.2932.1 +**Process Q.2931\_N** + +![Flowchart for Process Q.2931_U. The process starts with an entry point labeled '*' (except N0, N1, N6, N11, N12) leading to section 9.1.1.1. It branches into two parallel paths. The left path takes 'BR-Data -req (#)' and 'FACILITY (#)' as input, leading to a connector '-' and then to 'STATUS (Cause, CS)'. A dashed line from 'CS= previous state' points to 'STATUS'. From 'STATUS', the flow goes to 'BR-Data -ind (#)' and then to another connector '-'. The right path takes 'FACILITY (#)' as input, leading to 'Verify-Msg', which then leads to a 'Result' decision diamond. The 'Result' diamond has five outgoing paths: 'RAP' leads to 'STATUS (Cause, CS)' (with 'CS= previous state' dashed line); 'OK' leads to 'BR-Data -ind (#)' and then to connector '-'; 'CLR' leads to connector '-' and then to connector 'D'; 'I' leads to connector '-' (with 'CS= previous state' dashed line); and 'RAI' leads to 'STATUS (Cause, CS)' (with 'CS= previous state' dashed line) and then to connector '-'. A text box at the bottom right explains 'Verify-Msg' and lists result abbreviations: RAI (Report and Ignore), RAP (Report and Proceed), CLR (Release Call), OK (OK), and I (Ignore). A text box at the bottom left notes that this page is part of the Q.2931_U process defined in Recommendation Q.2931 [13].](fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg) + +``` + +graph TD + Entry["*(except N0, N1, N6, N11, N12)"] --> Section["9.1.1.1"] + Section --> BRDataReq["BR-Data -req (#)"] + Section --> Facility1["FACILITY (#)"] + BRDataReq --> Facility2["FACILITY (#)"] + Facility2 --> Connector1[(-)] + Facility1 --> VerifyMsg[Verify-Msg] + VerifyMsg --> Result{Result} + Result -- RAP --> Status1["STATUS (Cause, CS)"] + Status1 -.-> CS1[CS= previous state] + Status1 --> BRDataInd1["BR-Data -ind (#)"] + BRDataInd1 --> Connector2[(-)] + Result -- OK --> BRDataInd2["BR-Data -ind (#)"] + BRDataInd2 --> Connector3[(-)] + Result -- CLR --> Connector4[(-)] + Connector4 --> D((D)) + Result -- I --> Connector5[(-)] + Connector5 -.-> CS2[CS= previous state] + Result -- RAI --> Status2["STATUS (Cause, CS)"] + Status2 -.-> CS3[CS= previous state] + Status2 --> Connector6[(-)] + +``` + +Verify-Msg verifies messages based on message encoding rules. It removes unacceptable information elements and returns the result in the result and cause variables. Result abbreviations are: + RAI - Report and Ignore + RAP - Report and Proceed + CLR - Release Call + OK - OK + I - Ignore + +This page forms part of the Q.2931\_U process defined in Recommendation Q.2931 [13] and provides additional transitions that are required when the bearer-related transport mechanisms are implemented + +Flowchart for Process Q.2931\_U. The process starts with an entry point labeled '\*' (except N0, N1, N6, N11, N12) leading to section 9.1.1.1. It branches into two parallel paths. The left path takes 'BR-Data -req (#)' and 'FACILITY (#)' as input, leading to a connector '-' and then to 'STATUS (Cause, CS)'. A dashed line from 'CS= previous state' points to 'STATUS'. From 'STATUS', the flow goes to 'BR-Data -ind (#)' and then to another connector '-'. The right path takes 'FACILITY (#)' as input, leading to 'Verify-Msg', which then leads to a 'Result' decision diamond. The 'Result' diamond has five outgoing paths: 'RAP' leads to 'STATUS (Cause, CS)' (with 'CS= previous state' dashed line); 'OK' leads to 'BR-Data -ind (#)' and then to connector '-'; 'CLR' leads to connector '-' and then to connector 'D'; 'I' leads to connector '-' (with 'CS= previous state' dashed line); and 'RAI' leads to 'STATUS (Cause, CS)' (with 'CS= previous state' dashed line) and then to connector '-'. A text box at the bottom right explains 'Verify-Msg' and lists result abbreviations: RAI (Report and Ignore), RAP (Report and Proceed), CLR (Release Call), OK (OK), and I (Ignore). A text box at the bottom left notes that this page is part of the Q.2931\_U process defined in Recommendation Q.2931 [13]. + +T1179750-96 + +FIGURE 11/Q.2932.1 +**Process Q.2931\_U** + +![Flowchart for Process CO_bearer_independent. The process starts at '0 - Null', branches into 'CO-BI-Setup req. (#)' and 'CO-BI SETUP (#)'. 'CO-BI-Setup req. (#)' leads to 'CO-BI-SETUP (#)' then 'SET (NOW + t303, TIMER T303)' then '1 - Call Initiated'. 'CO-BI SETUP (#)' leads to 'Verify-Msg' then 'Result'. 'Result' has five paths: RAP, OK, CLR, CAI, and I. RAP leads to 'STATUS (Cause, CS:= 6)' then 'CO-BI-Setup .ind (#)' then '6 - Call Present'. OK leads to 'RELEASE COMPLETE (Cause, #)' which is crossed out. CLR leads to 'STATUS (Cause, CS:= UO)' then '-' (Null). CAI leads to '0 - Null'. I leads to '0 - Null'. To the right, 'Verify-Msg', 'Verify-State', and 'Recovery-Procedure' are shown as implementation-specific procedures. A note at the bottom left explains message conventions. A note at the bottom right defines result abbreviations: RAI, RAP, CLR, OK, I.](1b23b78336d8bd286c653cbdb38428dd_img.jpg) + +``` + +graph TD + Start([0 - Null]) --> COBI_Req_In{{CO-BI-Setup req. (#)}} + Start --> COBI_Setup_In{{CO-BI SETUP (#)}} + + COBI_Req_In --> COBI_Setup_Out>CO-BI-SETUP (#)] + COBI_Setup_Out --> SET[SET (NOW + t303, TIMER T303)] + SET --> Call_Initiated([1 - Call Initiated]) + + COBI_Setup_In --> Verify_Msg[[Verify-Msg]] + Verify_Msg --> Result{Result} + + Result -- RAP --> STATUS_6>STATUS (Cause, CS:= 6)] + STATUS_6 --> COBI_Ind_Out>CO-BI-Setup .ind (#)] + COBI_Ind_Out --> Call_Present([6 - Call Present]) + + Result -- OK --> Release>RELEASE COMPLETE (Cause, #)] + Release --> X((X)) + + Result -- CLR --> STATUS_UO>STATUS (Cause, CS:= UO)] + STATUS_UO --> NullDash([ - ]) + + Result -- CAI --> Null0([0 - Null]) + Result -- I --> Null0 + + subgraph Implementation_Procedures + VM[[Verify-Msg]] --- ISP1[implementation specific procedure] + VS[[Verify-State]] --- ISP2[implementation specific procedure] + RP[[Recovery-Procedure]] --- ISP3[implementation specific procedure] + end + + subgraph Notes + Note1[All messages and primitives come from and go to the CO-ORD Process. +Assumptions: +# indicates all information elements received in the message or primitive, except for those information elements specifically identified] + Note2[Verify-Msg verifies messages based on message encoding rules. It removes unacceptable IEs and returns the result in the result and cause variables. +Result abbreviations are: +RAI - Report and Ignore +RAP - Report and Proceed +CLR - Release Call +OK - OK +I - Ignore] + end + +``` + +Flowchart for Process CO\_bearer\_independent. The process starts at '0 - Null', branches into 'CO-BI-Setup req. (#)' and 'CO-BI SETUP (#)'. 'CO-BI-Setup req. (#)' leads to 'CO-BI-SETUP (#)' then 'SET (NOW + t303, TIMER T303)' then '1 - Call Initiated'. 'CO-BI SETUP (#)' leads to 'Verify-Msg' then 'Result'. 'Result' has five paths: RAP, OK, CLR, CAI, and I. RAP leads to 'STATUS (Cause, CS:= 6)' then 'CO-BI-Setup .ind (#)' then '6 - Call Present'. OK leads to 'RELEASE COMPLETE (Cause, #)' which is crossed out. CLR leads to 'STATUS (Cause, CS:= UO)' then '-' (Null). CAI leads to '0 - Null'. I leads to '0 - Null'. To the right, 'Verify-Msg', 'Verify-State', and 'Recovery-Procedure' are shown as implementation-specific procedures. A note at the bottom left explains message conventions. A note at the bottom right defines result abbreviations: RAI, RAP, CLR, OK, I. + +9.1.3.1 + +Verify-Msg --- implementation specific procedure +Verify-State --- implementation specific procedure +Recovery-Procedure --- implementation specific procedure + +FIGURE 12/Q.2932.1 (sheet 1 of 14) +**Process CO\_bearer\_independent** + +T1179760-96 + +![Flowchart for Process CO_bearer_independent. It starts with '1 - Call Initiated' (9.1.3.2), leading to 'CALL PROCEEDING (#)' and 'T303'. 'CALL PROCEEDING (#)' leads to 'Verify-Msg', which leads to a 'Result' decision. 'T303' leads to 'CO-BI-Release.ind', which has a note: 'The application process should implement a delay before releasing the call reference' and leads to a junction 'X'. From 'X', one path leads to 'Result' and another to 'R'. From 'Result', 'OK' leads to 'RAP' and 'STATUS (Cause, CS:=3)', which leads to 'RESET T303', 'CO-BI-Proceeding.ind (#)', and '3 - Outgoing Call Proceeding'. 'CLR' leads to 'R'. 'RAI' leads to 'STATUS (Cause, CS:=1)' and '1 - Call Initiated'. 'I' leads to '1 - Call Initiated'.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +``` + +graph TD + Start([1 - Call Initiated]) -- "9.1.3.2" --> CP[CALL PROCEEDING (#)] + Start --> T303[T303] + CP --> VM[Verify-Msg] + VM --> Result{Result} + T303 --> CBRI[CO-BI-Release.ind] + CBRI --> X((X)) + X -.-> Note["The application process should implement a delay before releasing the call reference"] + X --> Result + X --> R((R)) + Result -- OK --> RAP[RAP] + RAP --> S3[STATUS (Cause, CS:=3)] + S3 --> RT[RESET T303] + RT --> CBPI[CO-BI-Proceeding.ind (#)] + CBPI --> End3([3 - Outgoing Call Proceeding]) + Result -- CLR --> R + Result -- RAI --> S1[STATUS (Cause, CS:=1)] + S1 --> End1a([1 - Call Initiated]) + Result -- I --> End1b([1 - Call Initiated]) + +``` + +Flowchart for Process CO\_bearer\_independent. It starts with '1 - Call Initiated' (9.1.3.2), leading to 'CALL PROCEEDING (#)' and 'T303'. 'CALL PROCEEDING (#)' leads to 'Verify-Msg', which leads to a 'Result' decision. 'T303' leads to 'CO-BI-Release.ind', which has a note: 'The application process should implement a delay before releasing the call reference' and leads to a junction 'X'. From 'X', one path leads to 'Result' and another to 'R'. From 'Result', 'OK' leads to 'RAP' and 'STATUS (Cause, CS:=3)', which leads to 'RESET T303', 'CO-BI-Proceeding.ind (#)', and '3 - Outgoing Call Proceeding'. 'CLR' leads to 'R'. 'RAI' leads to 'STATUS (Cause, CS:=1)' and '1 - Call Initiated'. 'I' leads to '1 - Call Initiated'. + +T1179770-96 + +FIGURE 12/Q.2932.1 (sheet 2 of 14) +**Process CO\_bearer\_independent** + +![Flowchart for Process CO_bearer_independent. The process starts with '3 - Outgoing Call Proceeding', followed by 'CONNECT (#)', 'Verify-Msg', and a 'Result' decision. The 'Result' decision has five branches: RAP, OK, CLR, RAI, and I. The RAP branch leads to 'STATUS (Cause, CS = 10)' which then leads to 'CO-BI-Setup .conf (#)' and finally '10 - Active'. The OK branch leads directly to 'CO-BI-Setup .conf (#)'. The CLR branch leads to a connector 'R'. The RAI branch leads to 'STATUS (Cause, CS = U3)' which then leads to '3 - Outgoing Call Proceeding'. The I branch leads to '3 - Outgoing Call Proceeding'.](af6c3f383ddc0c142cdd7e186cc78199_img.jpg) + +``` + +graph TD + Start([3 - Outgoing Call Proceeding]) --> CONNECT{{CONNECT (#)}} + CONNECT --> Verify[Verify-Msg] + Verify --> Result{Result} + Result -- RAP --> STATUS1{{STATUS (Cause, CS = 10)}} + STATUS1 --> COBI[CO-BI-Setup .conf (#)] + Result -- OK --> COBI + Result -- CLR --> R((R)) + Result -- RAI --> STATUS2{{STATUS (Cause, CS = U3)}} + STATUS2 --> Proceeding1([3 - Outgoing Call Proceeding]) + Result -- I --> Proceeding2([3 - Outgoing Call Proceeding]) + COBI --> Active([10 - Active]) + +``` + +Flowchart for Process CO\_bearer\_independent. The process starts with '3 - Outgoing Call Proceeding', followed by 'CONNECT (#)', 'Verify-Msg', and a 'Result' decision. The 'Result' decision has five branches: RAP, OK, CLR, RAI, and I. The RAP branch leads to 'STATUS (Cause, CS = 10)' which then leads to 'CO-BI-Setup .conf (#)' and finally '10 - Active'. The OK branch leads directly to 'CO-BI-Setup .conf (#)'. The CLR branch leads to a connector 'R'. The RAI branch leads to 'STATUS (Cause, CS = U3)' which then leads to '3 - Outgoing Call Proceeding'. The I branch leads to '3 - Outgoing Call Proceeding'. + +T1179780-96 + +FIGURE 12/Q.2932.1 (sheet 3 of 14) + +### **Process CO\_bearer\_independent** + +![State transition diagram for Process CO_bearer_independent. The diagram shows transitions from state 6 (Call Present) to states 9 (Incoming Call Proceeding), 10 (Active), and an unlabeled terminal state via messages CO-BI Proceed. req (#), CO-BI-Setup.Resp (#), and CO-BI Release.resp (Cause) respectively. A bracket on the right indicates section 9.1.3.1.](6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 6 : Call Present + 6 --> CO-BI_Proceed_req : CO-BI Proceed. req (#) + 6 --> CO-BI_Setup_Resp : CO-BI-Setup.Resp (#) + 6 --> CO-BI_Release_resp : CO-BI Release.resp (Cause) + CO-BI_Proceed_req --> CALL_PROCEEDING : CALL PROCEEDING (#) + CALL_PROCEEDING --> 9 : Incoming Call Proceeding + CO-BI_Setup_Resp --> CONNECT : CONNECT (#) + CONNECT --> 10 : Active + CO-BI_Release_resp --> RELEASE_COMPLETE : RELEASE COMPLETE (Cause) + RELEASE_COMPLETE --> [*] + +``` + +State transition diagram for Process CO\_bearer\_independent. The diagram shows transitions from state 6 (Call Present) to states 9 (Incoming Call Proceeding), 10 (Active), and an unlabeled terminal state via messages CO-BI Proceed. req (#), CO-BI-Setup.Resp (#), and CO-BI Release.resp (Cause) respectively. A bracket on the right indicates section 9.1.3.1. + +T1179790-96 + +FIGURE 12/Q.2932.1 (sheet 4 of 14) +**Process CO\_bearer\_independent** + +![Flowchart showing a process flow: 9 - Incoming Call Proceeding -> CO-BI-Setup .resp (#) -> CONNECT (#) -> 10 - Active. A dashed line from the first state points to the text 9.1.3.3.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +``` + +graph TD + State9([9 - Incoming Call Proceeding]) + Ref[9.1.3.3] + Input1[/CO-BI-Setup +.resp +(#)/] + Input2[/CONNECT +(#)/] + State10([10 - Active]) + + State9 --- Ref + State9 --> Input1 + Input1 --> Input2 + Input2 --> State10 + +``` + +Flowchart showing a process flow: 9 - Incoming Call Proceeding -> CO-BI-Setup .resp (#) -> CONNECT (#) -> 10 - Active. A dashed line from the first state points to the text 9.1.3.3. + +T1179800-96 + +FIGURE 12/Q.2932.1 (sheet 5 of 14) +**Process\_CO\_bearer\_independent** + +![Flowchart for Process CO_bearer_independent. The process starts with '10 - Active' (oval) with associated numbers 9.1.3.5 and 9.1.3.8. It branches into two paths. The left path consists of 'CO-BI-Data .req (#)' (parallelogram), 'FACILITY (#)' (parallelogram), and an oval with a dash. The right path consists of 'FACILITY (#)' (parallelogram), 'Verify-Msg' (double rectangle), and 'Result' (diamond). From 'Result', five branches emerge: 'RAP' leads to 'STATUS (Cause, CS:= 10)' (parallelogram) which then leads to 'CO-BI-Data .ind (#)' (parallelogram) and an oval with a dash; 'OK' leads directly to 'CO-BI-Data .ind (#)'; 'CLR' leads to a circle with 'R'; 'RAI' leads to 'STATUS (Cause, CS:= 10)' (parallelogram) and an oval with a dash; 'I' leads to an oval with a dash.](a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg) + +``` + +graph TD + Start([10 - Active]) --- Ref["9.1.3.5 +9.1.3.8"] + Start --> COBIReq[/CO-BI-Data .req (#)/] + Start --> FACILITY1[/FACILITY (#)/] + COBIReq --> FACILITY2[/FACILITY (#)/] + FACILITY2 --> Dash1([ - ]) + FACILITY1 --> VerifyMsg[Verify-Msg] + VerifyMsg --> Result{Result} + Result -- RAP --> STATUS1[/STATUS (Cause, CS:= 10)/] + STATUS1 --> COBIInd[/CO-BI-Data .ind (#)/] + COBIInd --> Dash2([ - ]) + Result -- OK --> COBIInd + Result -- CLR --> R((R)) + Result -- RAI --> STATUS2[/STATUS (Cause, CS:= 10)/] + STATUS2 --> Dash3([ - ]) + Result -- I --> Dash4([ - ]) + +``` + +Flowchart for Process CO\_bearer\_independent. The process starts with '10 - Active' (oval) with associated numbers 9.1.3.5 and 9.1.3.8. It branches into two paths. The left path consists of 'CO-BI-Data .req (#)' (parallelogram), 'FACILITY (#)' (parallelogram), and an oval with a dash. The right path consists of 'FACILITY (#)' (parallelogram), 'Verify-Msg' (double rectangle), and 'Result' (diamond). From 'Result', five branches emerge: 'RAP' leads to 'STATUS (Cause, CS:= 10)' (parallelogram) which then leads to 'CO-BI-Data .ind (#)' (parallelogram) and an oval with a dash; 'OK' leads directly to 'CO-BI-Data .ind (#)'; 'CLR' leads to a circle with 'R'; 'RAI' leads to 'STATUS (Cause, CS:= 10)' (parallelogram) and an oval with a dash; 'I' leads to an oval with a dash. + +T1179810-96 + +FIGURE 12/Q.2932.1 (sheet 6 of 14) +**Process CO\_bearer\_independent** + +![SDL flowchart for Process CO_bearer_independent. Starting from state '10 - Active', it handles four inputs: Link-release.ind (leading to Link-establish.req), Link-establish-error (leading to Release.conf with Cause 27 and termination), and Link-establish.ind/conf (leading to a timeout reset and a decision on Timer T322). If T322 is not active, a STATUS ENQUIRY is sent and the timer is set.](b20942bb14022381a243971ab9790dd9_img.jpg) + +``` + +graph TD + StateActive([10 - Active]) --- Ref[5.6.10/Q.2931 13] + + StateActive --> In1[/Link-release.ind/] + StateActive --> In2[/Link-establish-error/] + StateActive --> In3[/Link-establish.ind/] + StateActive --> In4[/Link-establish.conf/] + + In1 --> Out1[\Link-establish.req\] + Out1 --> Next1([ - ]) + + In2 --> Out2[\Release.conf Cause:= 27\] + Out2 --> Term((X)) + + In3 --> Task1[Timeout := 0] + In4 --> Task1 + + Task1 --> Dec1{ACTIVE T322} + Dec1 -- True --> Next2([ - ]) + Dec1 -- False --> Out3[\STATUS ENQUIRY\] + Out3 --> Task2[SET Now + t322, Timer T322] + Task2 --> Next2 + +``` + +SDL flowchart for Process CO\_bearer\_independent. Starting from state '10 - Active', it handles four inputs: Link-release.ind (leading to Link-establish.req), Link-establish-error (leading to Release.conf with Cause 27 and termination), and Link-establish.ind/conf (leading to a timeout reset and a decision on Timer T322). If T322 is not active, a STATUS ENQUIRY is sent and the timer is set. + +T1179820-96 + +FIGURE 12/Q.2932.1 (sheet 7 of 14) +**Process CO\_bearer\_independent** + +![Flowchart for Process CO_bearer_independent (sheet 8 of 14) showing three main logic branches for handling release messages and requests.](29043c6ca27a7cfbc757a5d2eb029d33_img.jpg) + +``` + +stateDiagram-v2 + state "Any state\nexcluding\n0, x, 11" as S1 + state "Any state\nexcluding\n0, 6, 11" as S2 + state "11 - Release\nRequest" as S11 + + S1 --> RELEASE_COMPLETE: RELEASE COMPLETE (Cause) + RELEASE_COMPLETE --> Verify_Msg1: Verify_Msg + Verify_Msg1 --> Result1: Result + Result1 --> RESET_TIMERS1: OK, CLR, I, RAP, RAI + RESET_TIMERS1 --> COBI_Release_conf: CO-BI-Release.conf (Cause) + COBI_Release_conf --> Terminate1: X + + S1 --> RELEASE_MSG: RELEASE (Cause, #) + RELEASE_MSG --> Verify_Msg2: Verify_Msg + Verify_Msg2 --> Result2: Result + Result2 --> RESET_TIMERS2: OK, CLR, I, RAP, RAI + RESET_TIMERS2 --> COBI_Release_ind: CO-BI-Release.ind (Cause, #) + COBI_Release_ind --> RELEASE_COMPLETE_OUT: RELEASE COMPLETE + RELEASE_COMPLETE_OUT --> Terminate2: X + + S2 --> COBI_Release_req: CO-BI-Release.req (Cause) + COBI_Release_req --> Cause_Save: Cause R:= Cause /* Cause saved */ + + state "R" as ConnectorR + ConnectorR --> Release_ind: Release.ind (Cause) + + Cause_Save --> RESET_TIMERS3 + Release_ind --> RESET_TIMERS3 + + RESET_TIMERS3 --> RELEASE_OUT: RELEASE (Cause) + RELEASE_OUT --> SET_TIMER: SET (NOW + t308, Timer T308); timeout:= 9 + SET_TIMER --> S11 + +``` + +Flowchart for Process CO\_bearer\_independent (sheet 8 of 14) showing three main logic branches for handling release messages and requests. + +T1179830-96 + +FIGURE 12/Q.2932.1 (sheet 8 of 14) + +### **Process CO\_bearer\_independent** + +![SDL flowchart for Process CO_bearer_independent, showing state transitions and signal handling for Release Request.](8c3eb53c927f55acd19723cfcd0c43b6_img.jpg) + +``` + +graph TD + Start([11 - Release Request]) + Start --- L1[ ] + L1 --- In1[RELEASE +(#)] + L1 --- In2[RELEASE +COMPLETE +(#)] + L1 --- In3[STATUS +(Cause, CS-R)] + L1 --- In4[T308] + + In1 --> VM1[Verify-Msg] + VM1 --> Res1{Result} + Res1 -- "OK, CLR, I, RAP, RAI" --> ResetT308[RESET T308] + ResetT308 --> Out1[CO-BI-Release +.conf +(Cause, #)] + Out1 --> X1((X)) + + In3 --> VM2[Verify-Msg] + VM2 --> Res2{Result} + + Res2 -- RAP --> S2[STATUS +(Cause, CS:= 6)] + S2 --> CS_R_Eff{CS-R = ∅} + + Res2 -- OK --> CS_R_Eff + + Res2 -- CLR --> RC1[RELEASE +COMPLETE +(Cause, #)] + RC1 --> X3((X)) + + Res2 -- CAI --> S3[STATUS +(Cause, CS:= 11)] + S3 --> Dash([–]) + + Res2 -- I --> Null([0 - Null]) + + CS_R_Eff -- No --> R3([11 - Release Request]) + CS_R_Eff -- Yes --> Out2[CO-BI-Release +.conf +(Cause)] + Out2 --> X2((X)) + + In4 --> Timeout1{Timeout = 1} + Timeout1 -- Yes --> Reason[Release +reason = +failure] + Reason --> Out3[CO-BI-Release +.conf +(Release reason)] + Out3 --> X4((X)) + + Timeout1 -- No --> R4[RELEASE +(Cause R)] + R4 --> SET[SET (Now + t308, +Timer T308) +Timeout:= 1] + SET --> R5([11 - Release Request]) + +``` + +SDL flowchart for Process CO\_bearer\_independent, showing state transitions and signal handling for Release Request. + +T1179840-96 + +FIGURE 12/Q.2932.1 (sheet 9 of 14) + +### **Process CO\_bearer\_independent** + +![Flowchart for Process CO_bearer_independent. It consists of two main vertical paths. The left path starts with an entry point '(except 0)', followed by STATUS ENQUIRY, Verify_Msg, and a Result decision. If the result is 'I, RAP, OK, CLR, RAI', it sets CS to 'current state' with Cause 30, sends STATUS (Cause, CS), and ends. The right path starts with an entry point '(except 0, 11)', followed by STATUS (Cause, CS-R), Verify_Msg, and a connector circle. From the connector, it goes to T322, then Timeout := Timeout + 1. A decision 'Timeout = NT' follows. If 'Yes', it sends CO-BI-Release .conf (Cause := 41) and ends. If 'No', it sends STATUS ENQUIRY (#), SET (Now + t322, Timer T322), and ends. A note indicates NT is the number of STATUS ENQUIRY transmissions, implementation dependent, value ≥ 1.](e2dad48ec062e71202459a9ab82261e4_img.jpg) + +``` + +graph TD + subgraph LeftPath [ ] + L1[*(except 0)] --> L2[STATUS ENQUIRY] + L2 --> L3[Verify_Msg] + L3 --> L4{Result} + L4 -- "I, RAP, OK, CLR, RAI" --> L5[CS := "current state" +Cause := 30] + L5 --> L6[STATUS (Cause, CS)] + L6 --> L7[ - ] + end + + subgraph RightPath [ ] + R1[*(except 0, 11)] --> R2[STATUS (Cause, CS-R)] + R2 --> R3[Verify_Msg] + R3 --> R4(( )) + R4 --> R5[T322] + R5 --> R6[Timeout := Timeout + 1] + R6 --> R7{Timeout = NT} + R7 -- Yes --> R8[CO-BI-Release .conf +(Cause := 41)] + R8 --> R9[ - ] + R7 -- No --> R10[STATUS ENQUIRY (#)] + R10 --> R11[SET (Now + t322, +Timer T322)] + R11 --> R12[ - ] + end + + NT_note[NT = number of STATUS ENQUIRY transmissions: +implementation dependent value ≥ 1] -.-> R7 + +``` + +Flowchart for Process CO\_bearer\_independent. It consists of two main vertical paths. The left path starts with an entry point '(except 0)', followed by STATUS ENQUIRY, Verify\_Msg, and a Result decision. If the result is 'I, RAP, OK, CLR, RAI', it sets CS to 'current state' with Cause 30, sends STATUS (Cause, CS), and ends. The right path starts with an entry point '(except 0, 11)', followed by STATUS (Cause, CS-R), Verify\_Msg, and a connector circle. From the connector, it goes to T322, then Timeout := Timeout + 1. A decision 'Timeout = NT' follows. If 'Yes', it sends CO-BI-Release .conf (Cause := 41) and ends. If 'No', it sends STATUS ENQUIRY (#), SET (Now + t322, Timer T322), and ends. A note indicates NT is the number of STATUS ENQUIRY transmissions, implementation dependent, value ≥ 1. + +T1179850-96 + +FIGURE 12/Q.2932.1 (sheet 10 of 14) +**Process CO\_bearer\_independent** + +![Flowchart for Process CO_bearer_independent. It starts with a 'Result' decision, leading to RAP, OK, CLR, or RAI paths. The CLR path leads to '0 = Null'. The RAP and RAI paths lead to 'STATUS (Cause, CS)'. From there, it checks if 'CS-R = ∅'. If Yes, it goes to 'Release. confirm (Cause)'. If No, it checks if 'Cause = 30'. If Yes, it goes to 'RESET T322'. Both 'RESET T322' and the 'No' path from 'Cause = 30' lead to 'Verify-State'. From 'Verify-State', it checks if the state is 'Compatible'. If Yes, it leads to a connector '-'. If No, it goes to 'Recovery option'. If 'Recovery option' is Yes, it goes to 'Recovery-procedure' and then to a connector '-'. If 'Recovery option' is No, it goes to 'Status.ind (Cause := 101)' and then to connector 'R'.](3bf1696c3034743b5ab07a0b5e398347_img.jpg) + +``` + +graph TD + Start(( )) --> Result{Result} + Result -- RAP --> STATUS1[STATUS +(Cause, CS)] + Result -- OK --> OK_NULL[0 = Null] + Result -- CLR --> CLR_NULL[0 = Null] + Result -- RAI --> STATUS2[STATUS +(Cause, CS)] + STATUS1 --> CS_R{CS-R = ∅} + STATUS2 --> CS_R + CS_R -- Yes --> Release[Release. +confirm +(Cause)] + Release --> X[ ] + CS_R -- No --> Cause30{Cause = 30} + Cause30 -- Yes --> RESET[RESET +T322] + Cause30 -- No --> VerifyState[Verify-State] + RESET --> VerifyState + VerifyState --> Compatible{Compatible +state} + Compatible -- Yes --> ConnectorDash1[ - ] + Compatible -- No --> RecoveryOption{Recovery +option} + RecoveryOption -- Yes --> RecoveryProc[Recovery- +procedure] + RecoveryProc --> ConnectorDash2[ - ] + RecoveryOption -- No --> StatusInd[Status.ind +(Cause := 101)] + StatusInd --> R((R)) + +``` + +Flowchart for Process CO\_bearer\_independent. It starts with a 'Result' decision, leading to RAP, OK, CLR, or RAI paths. The CLR path leads to '0 = Null'. The RAP and RAI paths lead to 'STATUS (Cause, CS)'. From there, it checks if 'CS-R = ∅'. If Yes, it goes to 'Release. confirm (Cause)'. If No, it checks if 'Cause = 30'. If Yes, it goes to 'RESET T322'. Both 'RESET T322' and the 'No' path from 'Cause = 30' lead to 'Verify-State'. From 'Verify-State', it checks if the state is 'Compatible'. If Yes, it leads to a connector '-'. If No, it goes to 'Recovery option'. If 'Recovery option' is Yes, it goes to 'Recovery-procedure' and then to a connector '-'. If 'Recovery option' is No, it goes to 'Status.ind (Cause := 101)' and then to connector 'R'. + +T1179860-96 + +FIGURE 12/Q.2932.1 (sheet 11 of 14) +**Process CO\_bearer\_independent** + +![State transition diagram for Process CO_bearer_independent. It starts with a state entry point '*' (except 0). From here, three message types are possible: 'Unexpected message (except RELEASE or RELEASE COMPLETE)', 'Any other message', and 'Unrecognized message'. The first and third lead to a 'STATUS' message and then to a state. The second leads to a 'Status-enq option' decision. If 'Yes', it sets 'Timeout := ∅' and checks 'ACTIVE T322'. If 'False', it sends 'STATUS ENQUIRY', sets 'SET (NOW + t322, Timer T322)', and then goes to a state. If 'True', it goes directly to a state. If 'No' on the 'Status-enq option', it goes to a 'Cause option' decision. 'Cause option' 1 leads to 'STATUS (Cause := 101)' and then to a state. 'Cause option' 2 leads to 'STATUS (Cause := 98)' and then to a state.](32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 + State1 --> Unexpected[Unexpected message (except RELEASE or RELEASE COMPLETE)] + State1 --> AnyOther[Any other message] + State1 --> Unrecognized[Unrecognized message] + Unexpected --> STATUS1[STATUS] + STATUS1 --> State1_1[ - ] + AnyOther --> StatusEnq[Status-enq option] + StatusEnq -- Yes --> Timeout[Timeout := ∅] + StatusEnq -- No --> CauseOption[Cause option] + Timeout --> ActiveT322[ACTIVE T322] + ActiveT322 -- False --> STATUS_ENQ[STATUS ENQUIRY] + STATUS_ENQ --> SET_TIMER[SET (NOW + t322, Timer T322)] + SET_TIMER --> State1_2[ - ] + ActiveT322 -- True --> State1_3[ - ] + CauseOption -- 1 --> STATUS_101[STATUS (Cause := 101)] + STATUS_101 --> State1_4[ - ] + CauseOption -- 2 --> STATUS_98[STATUS (Cause := 98)] + STATUS_98 --> State1_5[ - ] + Unrecognized --> STATUS2[STATUS] + STATUS2 --> State1_6[ - ] + +``` + +State transition diagram for Process CO\_bearer\_independent. It starts with a state entry point '\*' (except 0). From here, three message types are possible: 'Unexpected message (except RELEASE or RELEASE COMPLETE)', 'Any other message', and 'Unrecognized message'. The first and third lead to a 'STATUS' message and then to a state. The second leads to a 'Status-enq option' decision. If 'Yes', it sets 'Timeout := ∅' and checks 'ACTIVE T322'. If 'False', it sends 'STATUS ENQUIRY', sets 'SET (NOW + t322, Timer T322)', and then goes to a state. If 'True', it goes directly to a state. If 'No' on the 'Status-enq option', it goes to a 'Cause option' decision. 'Cause option' 1 leads to 'STATUS (Cause := 101)' and then to a state. 'Cause option' 2 leads to 'STATUS (Cause := 98)' and then to a state. + +T1179870-96 + +FIGURE 12/Q.2932.1 (sheet 12 of 14) +**Process CO\_bearer\_independent** + +![Flowchart for Process CO_bearer_independent showing a state transition from any state except 0 or 10, receiving a Link release indication, sending a Release indication with Cause 27, and then terminating.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +``` + +graph TD + A(["* +(Except 0, 10)"]) --> B[["Link +release +indication"]] + B --> C{{"Release +indication +Cause := 27"}} + C --> D["X"] + +``` + +Flowchart for Process CO\_bearer\_independent showing a state transition from any state except 0 or 10, receiving a Link release indication, sending a Release indication with Cause 27, and then terminating. + +T1179880-96 + +FIGURE 12/Q.2932.1 (sheet 13 of 14) +**Process CO\_bearer\_independent** + +![Flowchart for Process CO_bearer_independent. The process starts with a condition '*' (except 0, 1, 6, 11). It branches into two main paths. The left path consists of CO-BI-Notify.req (#), NOTIFY (#), and an end connector. The right path consists of NOTIFY (#), Verify-Msg, and a Result decision diamond. The Result diamond has five branches: RAP, OK, CLR, RAI, and I. The RAP branch leads to STATUS (Cause, CS) and then CO-BI-Notify.ind (#), ending at an end connector. The OK branch leads directly to CO-BI-Notify.ind (#), ending at an end connector. The CLR branch leads to a connector R. The RAI branch leads to STATUS (Cause, CS) and then an end connector. The I branch leads to an end connector.](f78d2e126f00fcc5d8d9797ca410cc09_img.jpg) + +``` + +graph TD + Start["* (except 0, 1, 6, 11)"] --> COBIReq["CO-BI-Notify.req (#)"] + Start --> NOTIFY1["NOTIFY (#)"] + COBIReq --> NOTIFY2["NOTIFY (#)"] + NOTIFY2 --> End1[(- - -)] + NOTIFY1 --> VerifyMsg["Verify-Msg"] + VerifyMsg --> Result{Result} + Result -- RAP --> STATUS1["STATUS (Cause, CS)"] + STATUS1 --> COBIInd["CO-BI-Notify.ind (#)"] + COBIInd --> End2[(- - -)] + Result -- OK --> COBIInd + COBIInd --> End2 + Result -- CLR --> R((R)) + Result -- RAI --> STATUS2["STATUS (Cause, CS)"] + STATUS2 --> End3[(- - -)] + Result -- I --> End4[(- - -)] + +``` + +Flowchart for Process CO\_bearer\_independent. The process starts with a condition '\*' (except 0, 1, 6, 11). It branches into two main paths. The left path consists of CO-BI-Notify.req (#), NOTIFY (#), and an end connector. The right path consists of NOTIFY (#), Verify-Msg, and a Result decision diamond. The Result diamond has five branches: RAP, OK, CLR, RAI, and I. The RAP branch leads to STATUS (Cause, CS) and then CO-BI-Notify.ind (#), ending at an end connector. The OK branch leads directly to CO-BI-Notify.ind (#), ending at an end connector. The CLR branch leads to a connector R. The RAI branch leads to STATUS (Cause, CS) and then an end connector. The I branch leads to an end connector. + +T1179890-96 + +FIGURE 12/Q.2932.1 (sheet 14 of 14) +**Process CO\_bearer\_independent** + +![Flowchart for Process CL_bearer_independent. It starts with a connector 'U0 - Null', leading to a split. The left path goes through 'FACILITY (#)' to a decision diamond 'Check facility information element present and correct'. 'No' leads to an exit, 'Yes' leads to 'Ignore unexpected information element' then 'Ignore optional information element with content error' then 'CL-BI-UNITDATA .ind (#)' to an exit. The right path goes through 'CL-BI-UNITDATA req (#)' to 'FACILITY (#)' to an exit.](e404de9a69c05473fbd6af28ee32311b_img.jpg) + +``` + +graph TD + Start([ ]) --> U0([U0 - Null]) + U0 --> Split(( )) + + %% Left Branch + Split --> FACILITY_IN[/FACILITY +(#)/] + FACILITY_IN --> Decision{Check facility information +element present and correct} + Decision -- No --> Exit1((X)) + Decision -- Yes --> Step1[Ignore unexpected +information element] + Step1 --> Step2[Ignore optional +information element +with content error] + Step2 --> CLBI_IND[/CL-BI-UNITDATA +.ind +(#)/] + CLBI_IND --> Exit2((X)) + + %% Right Branch + Split --> CLBI_REQ[/CL-BI-UNITDATA +.req +(#)/] + CLBI_REQ --> FACILITY_OUT[/FACILITY +(#)/] + FACILITY_OUT --> Exit3((X)) + +``` + +Flowchart for Process CL\_bearer\_independent. It starts with a connector 'U0 - Null', leading to a split. The left path goes through 'FACILITY (#)' to a decision diamond 'Check facility information element present and correct'. 'No' leads to an exit, 'Yes' leads to 'Ignore unexpected information element' then 'Ignore optional information element with content error' then 'CL-BI-UNITDATA .ind (#)' to an exit. The right path goes through 'CL-BI-UNITDATA req (#)' to 'FACILITY (#)' to an exit. + +T1179900-96 + +FIGURE 13/Q.2932.1 +**Process CL\_bearer\_independent** + +![Sequence diagram for Process GFT_Control. The process starts with a 'Pending' state, followed by a 'GF-Data .req (#)' message. It then enters a loop: 'MSN provided' (Yes/No) -> 'MSN_outgoing' (if No) -> 'SUB provided' (Yes/No) -> 'SUB_outgoing' (if No) -> 'transport' -> 'BR-data .req (#)' (Note 1) -> 'CO-BI-data .req (#)' (Note 2) -> 'CL-BI-data .req (#)' -> end state '-'. External messages 'MSN_outgoing' and 'SUB_outgoing' are shown on the left.](24ba47df8be44ae91945d88ce2232df5_img.jpg) + +``` + +sequenceDiagram + participant User + participant System + Note left of User: MSN_outgoing + Note left of User: SUB_outgoing + System-->>User: Pending + User->>System: GF-Data .req (#) + System-->>User: MSN provided + alt MSN provided: No + System-->>User: MSN_outgoing + else Yes + System-->>User: SUB provided + alt SUB provided: No + System-->>User: SUB_outgoing + else Yes + System-->>User: transport + alt transport: BR + Note left of BR: (Note 1) + BR-->>User: BR-data .req (#) + Note right of BR: (Note 2) + BR-->>User: CO-BI-data .req (#) + BR-->>User: CL-BI-data .req (#) + BR-->>User: - + end + +``` + +Sequence diagram for Process GFT\_Control. The process starts with a 'Pending' state, followed by a 'GF-Data .req (#)' message. It then enters a loop: 'MSN provided' (Yes/No) -> 'MSN\_outgoing' (if No) -> 'SUB provided' (Yes/No) -> 'SUB\_outgoing' (if No) -> 'transport' -> 'BR-data .req (#)' (Note 1) -> 'CO-BI-data .req (#)' (Note 2) -> 'CL-BI-data .req (#)' -> end state '-'. External messages 'MSN\_outgoing' and 'SUB\_outgoing' are shown on the left. + +NOTE 1 – Such information can be synchronized with the bearer-related messages within the coordination process. Such synchronization is implementation dependent, and therefore not shown in this SDL. + +NOTE 2 – If appropriate, data can also be sent in the CO-BI-setup.request, CO-BI-setup.response, and CO-BI-release.request primitives. It is an implementation dependent matter and outside the scope of this Recommendation as to which the CO-BI process is established. + +T1179910-96 + +FIGURE 14/Q.2932.1 (sheet 1 of 2) +**Process GFT\_Control** + +![SDL flowchart for Process GFT_Control showing states, inputs, decisions, and procedures.](0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg) + +``` + +stateDiagram-v2 + state "Determine_destination" as DD + state "MSN_incoming" as MI + state "SUB_incoming" as SI + + [*] --> Pending + Pending --> BR_DATA + state "BR-DATA .ind (#)" as BR_DATA + BR_DATA --> CO_BI_DATA + state "CO-BI-DATA .ind (#)" as CO_BI_DATA + CO_BI_DATA --> CL_BI_DATA + state "CL-BI-DATA .ind (#)" as CL_BI_DATA + CL_BI_DATA --> MSN_provided + + state MSN_provided <> + MSN_provided --> MSN_inc_proc : No + MSN_provided --> SUB_provided : Yes + + state "MSN_incoming" as MSN_inc_proc + MSN_inc_proc --> BR_DATA + + state SUB_provided <> + SUB_provided --> SUB_inc_proc : No + SUB_provided --> GF_data : Yes + + state "SUB_incoming" as SUB_inc_proc + SUB_inc_proc --> BR_DATA + + state "GF-data ind. (#)" as GF_data + GF_data --> FinalState + state "-" as FinalState + + note right of BR_DATA : (Note 1) + note right of CO_BI_DATA : (Note 2) + note right of CL_BI_DATA : (Note 3) + +``` + +NOTE 1 – Such information can be synchronized with bearer-related messages within the coordination process. The mechanism for separating this information is performed by the coordination process. + +NOTE 2 – Such information can also appear in CO-BI-setup.indication, CO-BI-setup.confirm, CO-BI-release.indication primitives. As the time of establishment/release of the CO-BI transfer mechanism is outside the scope of this Recommendation, this SDL does not provide this in detail. + +NOTE 3 – Timer T310 is started on receipt of the CO-BI-proceeding.indication primitive. It is stopped on receipt of the CO-BI-setup.confirm primitive. On expiry of timer T310 an indication is sent to SS-Control. + +SDL flowchart for Process GFT\_Control showing states, inputs, decisions, and procedures. + +T1179920-96 + +FIGURE 14/Q.2932.1 (sheet 2 of 2) + +### **Process GFT\_Control** + +![Flowchart for Procedure determine_destination. It starts with a connector symbol, leading to a decision diamond 'Protocol profile'. From the diamond, two paths emerge: 'ROSE' leading to a box 'Result = process (ROSE ASE)' and 'Other' leading to a box 'Result = discard'. Both boxes lead to connector symbols. A dashed box to the right of the 'Result = discard' path contains the text 'Handling is as for unrecognized information element contents'.](5e05915b2a93a3b404422e0966a7c924_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{Protocol profile}; Decision -- ROSE --> Process[Result = process (ROSE ASE)]; Decision -- Other --> Discard[Result = discard]; Process --> End1((X)); Discard --> End2((X)); Discard -.-> Note[Handling is as for unrecognized information element contents]; +``` + +Flowchart for Procedure determine\_destination. It starts with a connector symbol, leading to a decision diamond 'Protocol profile'. From the diamond, two paths emerge: 'ROSE' leading to a box 'Result = process (ROSE ASE)' and 'Other' leading to a box 'Result = discard'. Both boxes lead to connector symbols. A dashed box to the right of the 'Result = discard' path contains the text 'Handling is as for unrecognized information element contents'. + +T1179930-96 + +FIGURE 15/Q.2932.1 +**Procedure determine\_destination** + +![SDL flowchart for PROCEDURE MSN_outgoing showing a split between USER and NETWORK paths. USER path includes 'Include calling party number'. NETWORK path includes 'Include called party number'.](caeb1637753f79f4cd005eda3768d1d5_img.jpg) + +``` + +graph TD + Start([ ]) --> Split{ } + Split -- USER --> Box1[Include calling party number] + Split -- NETWORK --> Box2[Include called party number] + Box1 --> End1((X)) + Box2 --> End2((X)) + +``` + +SDL flowchart for PROCEDURE MSN\_outgoing showing a split between USER and NETWORK paths. USER path includes 'Include calling party number'. NETWORK path includes 'Include called party number'. + +T1179940-96 + +FIGURE 16/Q.2932.1 +**PROCEDURE MSN\_outgoing** + +![SDL flowchart for PROCEDURE SUB_outgoing showing a split between USER and NETWORK paths. USER path leads to an end symbol. NETWORK path includes 'Include called party subaddress'.](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +graph TD + Start([ ]) --> Split{ } + Split -- USER --> End1((X)) + Split -- NETWORK --> Box[Include called party subaddress] + Box --> End2((X)) + +``` + +SDL flowchart for PROCEDURE SUB\_outgoing showing a split between USER and NETWORK paths. USER path leads to an end symbol. NETWORK path includes 'Include called party subaddress'. + +T1179950-96 + +FIGURE 17/Q.2932.1 +**PROCEDURE SUB\_outgoing** + +![Flowchart for PROCEDURE MSN_incoming. It starts with a connector symbol leading to a split between USER and NETWORK paths. The USER path checks if the called party number is included; if no, it discards data; if yes, it checks if it equals a local number. The NETWORK path checks if the calling party number is included; if yes, it assigns a profile; if no, it assigns a default profile. Both paths lead to a common connector symbol. A label T1179960-96 is present near the bottom right.](5cc4a2ef554f31ea0577731931007fff_img.jpg) + +``` + +graph TD + Start([ ]) --> Split1{ } + Split1 -- USER --> D1{Called party number included} + Split1 -- NETWORK --> D2{Calling party number included} + D1 -- No --> Discard[Discard data] + Discard --> End1([ - ]) + D1 -- Yes --> D3{Called party number = local number} + D3 -- No --> Discard + D3 -- Yes --> C1(( )) + D2 -- No --> P2[Assign default profile] + D2 -- Yes --> P1[Assign profile associated with calling party number] + P1 --> C2(( )) + P2 --> C2 + T1179960-96[T1179960-96] + +``` + +Flowchart for PROCEDURE MSN\_incoming. It starts with a connector symbol leading to a split between USER and NETWORK paths. The USER path checks if the called party number is included; if no, it discards data; if yes, it checks if it equals a local number. The NETWORK path checks if the calling party number is included; if yes, it assigns a profile; if no, it assigns a default profile. Both paths lead to a common connector symbol. A label T1179960-96 is present near the bottom right. + +FIGURE 18/Q.2932.1 +**PROCEDURE MSN\_incoming** + +![Flowchart for PROCEDURE SUB_incoming. It starts with a connector symbol leading to a triangle with 'USER' and 'NETWORK' inputs. The 'USER' path leads to a decision diamond 'Called party subaddress included'. If 'No', it goes to another decision diamond 'Called party subaddress = local subaddress'. If 'Yes' to the second diamond, it ends at a circle with an 'X'. If 'No' to the second diamond, it goes to a 'Discard data' box, which then leads to a connector symbol with a dash. If 'Yes' to the first diamond, it ends at a circle with an 'X'. The 'NETWORK' path from the triangle ends at a circle with an 'X'. The text 'T1179970-96' is at the bottom right.](d546a282ce562b4930a36fcf2ec3e7b3_img.jpg) + +``` + +graph TD + Top([ ]) --- Triangle[/ / \ \/] + Triangle -- USER --> D1{Called party subaddress included} + Triangle -- NETWORK --> End1((X)) + D1 -- No --> D2{Called party subaddress = local subaddress} + D1 -- Yes --> End2((X)) + D2 -- Yes --> End3((X)) + D2 -- No --> Discard[Discard data] + Discard --> Bottom([ - ]) + T1179970-96 + +``` + +Flowchart for PROCEDURE SUB\_incoming. It starts with a connector symbol leading to a triangle with 'USER' and 'NETWORK' inputs. The 'USER' path leads to a decision diamond 'Called party subaddress included'. If 'No', it goes to another decision diamond 'Called party subaddress = local subaddress'. If 'Yes' to the second diamond, it ends at a circle with an 'X'. If 'No' to the second diamond, it goes to a 'Discard data' box, which then leads to a connector symbol with a dash. If 'Yes' to the first diamond, it ends at a circle with an 'X'. The 'NETWORK' path from the triangle ends at a circle with an 'X'. The text 'T1179970-96' is at the bottom right. + +FIGURE 19/Q.2932.1 +**PROCEDURE SUB\_incoming** + +# **Annex A** + +## **Formal definition of data types using Recommendation X.208 [6]** + +This Annex provides the ASN.1 modules defined for the purpose of this Recommendation. + +## **A.1 APDU types** + +Table A.1 shows the formal definition of the APDU data types used in the functional protocol. + +TABLE A.1 + +### **APDU types** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Facility-Information-Element-APDU {ccitt recommendation q 2932 facility-information-element-APDU(3)}
DEFINITIONS ::=
BEGIN
EXPORTS InvokeIDType, APDU; | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +``` + +IMPORTS OPERATION, ERROR + FROM Remote-Operation-Notation + {joint-iso-ccitt remote-operations(4) notation(0)}; +APDU ::= CHOICE { + invokeAPDU [1] IMPLICIT InvokeAPDU, + returnResultAPDU [2] IMPLICIT ReturnResultAPDU, + returnErrorAPDU [3] IMPLICIT ReturnErrorAPDU, + rejectAPDU [4] IMPLICIT RejectAPDU} +InvokeAPDU ::= SEQUENCE { + invokeID InvokeIDType, + linked-ID [0] IMPLICIT InvokeIDType OPTIONAL, + operation-value OPERATION, + argument ANY DEFINED BY operation-value OPTIONAL} + -- ANY is filled by the single ASN.1 data type following the keyword + -- ARGUMENT in the type definition of a particular operation. +InvokeIDType ::= INTEGER (-32768..32767) +ReturnResultAPDU + ::= SEQUENCE { + invokeID InvokeIDType, + SEQUENCE { + operation-value OPERATION, + result ANY DEFINED BY operation-value + -- ANY is filled by the single ASN.1 data type following the keyword + -- RESULT in the type definition of a particular operation. + } OPTIONAL} +ReturnErrorAPDU + ::= SEQUENCE { + invokeID InvokeIDType, + error-value ERROR, + parameter ANY DEFINED BY error-value OPTIONAL} + -- ANY is filled by the single ASN.1 data type following the keyword + -- PARAMETER in the type definition of a particular error +RejectAPDU ::= SEQUENCE { + invokeID CHOICE { + InvokeIDType, + NULL}, + problem CHOICE { + [0] IMPLICIT GeneralProblem, + [1] IMPLICIT InvokeProblem, + [2] IMPLICIT ReturnResultProblem, + [3] IMPLICIT ReturnErrorProblem}} +GeneralProblem ::= INTEGER { -- ROSE-provider detected + unrecognizedAPDU (0), + mistypedAPDU (1), + badlyStructuredAPDU (2)} + +``` + +``` + +InvokeProblem ::= INTEGER { -- ROSE-user detected + -- supplementary service entity + duplicateInvocation (0), + unrecognizedOperation (1), + mistypedArgument (2), + resourceLimitation (3), + initiatorReleasing (4), + unrecognizedLinkedID (5), + linkedResponseUnexpected (6), + unexpectedChildOperation (7)} +ReturnResultProblem ::= INTEGER { -- ROSE-user detected + unrecognizedInvocation (0), + resultResponseUnexpected (1), + mistypedResult (2)} +ReturnErrorProblem ::= INTEGER { -- ROSE-user detected + unrecognizedInvocation (0), + errorResponseUnexpected (1), + unrecognizedError (2), + unexpectedError (3), + mistypedParameter (4)} +END -- of Facility-Information-Element-APDU + +``` + +## A.2 Definition of Q.2931 information elements + +Table A.2 contains the ASN.1 definition of a general applicable type used to include DSS 2 information elements in ASN.1 definitions. + +The DSS 2 information elements to be used shall be indicated as comment at the point where the type DSS2InformationElement is used. + +TABLE A.2/Q.2932.1 + +### Definition of embedded DSS 2 information elements + +``` + +Embedded-DSS2-Types {ccitt recommendation q 2932 embedded-dSS2-types(7)} +DEFINITIONS EXPLICIT TAGS ::= +BEGIN +EXPORTS DSS2InformationElement; +DSS2InformationElement ::= [APPLICATION 0] IMPLICIT OCTET STRING +END -- of Embedded-dSS2-Types + +``` + +# Annex B + +## Formal definition of data types using Recommendation X.680 [8] + +This Annex provides the ASN.1 modules defined for the purpose of this Recommendation. + +## B.1 APDU types + +Table B.1 shows the formal definition of the APDU data types used in the functional protocol. + +TABLE B.1/Q.2932.1 + +### APDU types + +``` +Revised-Facility-Information-Element-Components + {ccitt recommendation Q.2932 revised-facility-information-element-components(13)} + +DEFINITIONS +IMPLICIT TAGS ::= +BEGIN +-- exports everything +IMPORTS OPERATION, ERROR FROM {joint-iso-ccitt remote-operations(4) informationObjects(5) +version1(0)}; +ROS {InvokeId:InvokeIdSet, OPERATION:Invokable, OPERATION:Returnable} ::= CHOICE + { + invoke [1] Invoke{{InvokeIdSet}, {Invokable}}, + returnResult [2] ReturnResult {{Returnable}}, + returnError [3] ReturnError {{Errors{{Returnable}}}}, + reject [4] Reject + } +(CONSTRAINED BY {-- must conform to the above definition --} + ! RejectProblem : general-unrecognizedPDU) +Invoke {InvokeId:InvokeIdSet, OPERATION:Operations} ::= SEQUENCE + { + invokeId InvokeId (InvokeIdSet) + (CONSTRAINED BY {-- must be unambiguous --} + !RejectProblem : invoke-duplicateInvocation). + Linkedid CHOICE + { + present [0] IMPLICIT present < InvokeId, + absent [1] IMPLICIT NULL + } + (CONSTRAINED BY {-- must identify an outstanding operation --} + ! RejectProblem : invoke-unrecognizedLinkId) + (CONSTRAINED BY {-- which has one or more linked operations --} + ! RejectProblem : invoke-linkedResponseUnexpected) + OPTIONAL + opcode OPERATION.&operationCode + ({Operations} + ! RejectProblem : invoke-unrecognizedOperation), + argument OPERATION.&ArgumentType + ({Operations} {@opcode} + ! RejectProblem : invoke-mistypedArgument) + OPTIONAL + } +} +``` + +``` + +(CONSTRAINED BY {-- must conform to the above definition --} + ! RejectProblem : general-mistypedPDU) +( + WITH COMPONENTS + {..., + linkedid ABSENT + } + WITH COMPONENTS + {..., + linkedid PRESENT, + opcode + (CONSTRAINED BY {-- must be in the &Linked field of the associated operation --} + ! RejectProblem : invoke-unexpectedLinkedOperation) + } +) +ReturnResult {OPERATION:Operations} ::=SEQUENCE +{ + invokeId InvokeId + (CONSTRAINED BY {-- must be that for an outstanding operation --} + ! RejectProblem : returnResult-unrecognizedInvocation) + (CONSTRAINED BY {-- which returns a result --} + ! RejectProblem : returnResult-resultResponseUnexpected), + result SEQUENCE + { + opcode OPERATION.&operationCode + ({Operations})(CONSTRAINED BY {-- identified by invokeId --} + ! RejectProblem : returnResult-unrecognizedInvocation)), + result OPERATION.&ResultType + ({Operations} {@opcode} + ! RejectProblem : returnResult-mistypedResult) + } OPTIONAL +} +(CONSTRAINED BY {-- must conform to the above definition --} + ! RejectProblem : general-mistypedPDU) +ReturnError {ERROR:Errors} ::= SEQUENCE +{ + invokeId InvokeId + CONSTRAINED BY {-- must be that for an outstanding operation --} + ! RejectProblem : returnError-unrecognizedInvocation) + (CONSTRAINED BY {-- which returns an error --} + ! RejectProblem : returnError-errorResponseUnexpected), + errcode ERROR.&errorCode + ({Errors} + ! RejectProblem : returnError-unrecognizedError) + (CONSTRAINED BY + {-- must be in the &Errors field of the associated opÕn --} + ! RejectProblem : returnError-unexpectedError), + parameter ERROR.&ParameterType + ({Errors}{@errcode} + ! RejectProblem : returnError-mistypedParameter) OPTIONAL +} +(CONSTRAINED BY { -- must conform to the above definition --} + ! RejectProblem : general-mistypedPDU) + +``` + +``` + +Reject ::= SEQUENCE +{ + invokeId InvokeId + problem CHOICE + { + general [0] GeneralProblem, + invoke [1] InvokeProblem, + returnResult [2] ReturnResultProblem, + returnError [3] ReturnErrorProblem + } +} + +(CONSTRAINED BY {-- must conform to the above definition --} +! RejectProblem : general-mistypedPDU) +GeneralProblem ::= INTEGER +{ + unrecognizedComponent (0), + mistypedComponent (1), + badlyStructuredComponent (2) +} + +InvokeProblem ::= INTEGER +{ + duplicateInvocation (0), + unrecognizedOperation (1), + mistypedArgument (2), + resourceLimitation (3), + releaseInProgress (4), + unrecognizedLinkId (5), + linkedResponseUnexpected (6), + unexpectedLinkedOperation (7), +} + +ReturnResultProblem ::= INTEGER +{ + unrecognizedInvocation (0), + resultResponseUnexpected (1), + mistypedResult (2) +} + +ReturnErrorProblem ::= INTEGER +{ + unrecognizedInvocation (0), + errorResponseUnexpected (1), + unrecognizedError (2), + unexpectedError (3), + mistypedParameter (4) +} + +``` + +``` + +RejectProblem ::= INTEGER +{ + general-unrecognizedPDU (0), + general-mistypedPDU (1), + general-badlyStructuredPDU (2), + invoke-duplicateInvocation (10), + invoke-unrecognizedOperation (11), + invoke-mistypedArgument (12), + invoke-resourceLimitation (13), + invoke-releaseInProgress (14), + invoke-unrecognizedLinkId (15), + invoke-linkedResponseUnexpected (16), + invoke-unexpectedLinkedOperation (17), + returnResult-unrecognizedInvocation (20), + returnResult-resultResponseUnexpected (21), + returnResult-mistypedResult (22), + returnError-unrecognizedInvocation (30), + returnError-errorResponseUnexpected (31), + returnError-unrecognizedError (32), + returnError-unexpectedError (33), + returnError-mistypedParameter (34) +} +InvokeId ::= CHOICE +{ + present INTEGER + absent NULL +} +noInvokeId InvokeId ::= absent:NULL +NoInvokeId InvokeId ::= {noInvokeId} +Errors (OPERATION:Operations) ERROR ::= {Operations.&Errors} +END -- end of generic ROS PDU definitions + +``` + +TABLE B.2/Q.2932.1 + +### **Definition of embedded DSS 2 information elements** + +``` + +Embedded-DSS2Types {ccitt recommendation q2932 embedded-dSS2types(7)} +DEFINITIONS EXPLICIT TAGS ::= +BEGIN +EXPORTS + DSS2InformationElement; +DSS2InformationElement ::= [APPLICATION 0] IMPLICIT OCTET STRING +END -- of Embedded-dSS2Types + +``` + +# Appendix IInformation flows + +## I.1 Connection-oriented bearer-independent transport mechanism + +### I.1.1 Bearer independent establishment and data transfer + +An example of the information flow for the connection-oriented bearer-independent transport mechanism is shown in Figure I.1. + +![Sequence diagram showing information flows between an Outgoing entity and an Incoming entity for a connection-oriented bearer-independent transport mechanism.](c7e27041e661260fd0c8e89c763bb32e_img.jpg) + +``` +sequenceDiagram + participant Outgoing entity + participant Incoming entity + Note right of Outgoing entity: CO-BI SETUP Fie + Outgoing entity->>Incoming entity: CO-BI SETUP Fie + Note left of Incoming entity: CALL PROCEEDING + Incoming entity->>Outgoing entity: CALL PROCEEDING + Note left of Incoming entity: CONNECT Fie + Incoming entity->>Outgoing entity: CONNECT Fie + Note left of Incoming entity: FACILITY Fie + Incoming entity->>Outgoing entity: FACILITY Fie + Note left of Incoming entity: FACILITY Fie + Incoming entity->>Outgoing entity: FACILITY Fie + Note right of Outgoing entity: RELEASE Fie + Outgoing entity->>Incoming entity: RELEASE Fie + Note right of Outgoing entity: RELEASE COMPLETE Fie + Outgoing entity->>Incoming entity: RELEASE COMPLETE Fie +``` + +The diagram illustrates the sequence of messages for a connection-oriented bearer-independent transport mechanism. It features two vertical lifelines: 'Outgoing entity' on the left and 'Incoming entity' on the right, each represented by a circle at the top. The message sequence is as follows: 1. The Outgoing entity sends a 'CO-BI SETUP Fie' message to the Incoming entity. 2. The Incoming entity responds with a 'CALL PROCEEDING' message. 3. The Incoming entity then sends a 'CONNECT Fie' message. 4. This is followed by a 'FACILITY Fie' message from the Incoming entity. 5. A second 'FACILITY Fie' message is sent by the Incoming entity. 6. The Outgoing entity then sends a 'RELEASE Fie' message. 7. Finally, the Outgoing entity sends a 'RELEASE COMPLETE Fie' message. + +Sequence diagram showing information flows between an Outgoing entity and an Incoming entity for a connection-oriented bearer-independent transport mechanism. + +T1179980-96 + +Fie Facility information element + +FIGURE I.1/Q.2932.1 + +**Connection-oriented bearer-independent transport mechanism** + +# Appendix II Instruction indicators + +The following abbreviations have been used in Tables II.1 to II.4: + +used = Follow explicit instructions + not used = instruction field not significant + N = network + U = user + +TABLE II.1/Q.2932.1 + +#### Typical use of instruction indicators for Q.2932.1 messages which are used for bearer-related transport + +| Message | Flag | Origin | Action indicator | +|----------|--------|--------|------------------| +| FACILITY | (Note) | N&U | (Note) | + +NOTE – If the instruction indicator in any Facility information element is set to "clear call" then the instruction indicator of the FACILITY message should also be set to that value, else the flag is not used and the action indicator not significant. + +TABLE II.2/Q.2932.1 + +#### Typical use of instruction indicators for Q.2932.1 messages which are used for connection-oriented bearer-independent transport + +| Message | Flag | Origin | Action indicator | +|------------------|----------|--------|------------------| +| CALL PROCEEDING | not used | N&U | not significant | +| CO-BI SETUP | not used | N&U | not significant | +| CONNECT | not used | N&U | not significant | +| FACILITY | (Note) | N&U | (Note) | +| NOTIFY | not used | N&U | not significant | +| RELEASE | not used | N&U | not significant | +| RELEASE COMPLETE | not used | N&U | not significant | +| STATUS | not used | N&U | not significant | +| STATUS ENQUIRY | not used | N&U | not significant | + +NOTE – If the instruction indicator in any Facility information element is set to "clear call" then the instruction indicator of the FACILITY message should also be set to that value, else the flag is not used and the action indicator not significant. + +TABLE II.3/Q.2932.1 + +#### Typical use of instruction indicators for Q.2932.1 messages which are used for connectionless bearer-independent transport + +| Message | Flag | Origin | Action indicator | +|----------|----------|--------|------------------| +| FACILITY | not used | N&U | not significant | + +TABLE II.4/Q.2932.1 + +#### **Typical use of instruction indicators for Q.2932.1 information elements** + +| Information element | Flag | Origin | Action indicator | +|---------------------|------|--------|------------------| +| Facility | Note | N&U | (Note) | + +NOTE – The value contained in this field is specified by other Recommendations specifying use of Q.2932.1 procedures. The values where two Recommendations specify different values for the same field is implementation dependent, but in this case, consideration should be given to using multiple Facility information elements to contain multiple ADPUs. + +# **Appendix III** + +## **Formal definitions of remote operations notation using Recommendation X.208 [6]** + +TABLE III.1/Q.2932.1 + +### **Formal definition of remote operations data types (extract of Figure 4/X.219 [3])** + +``` + +Remote-Operation-Notation {joint-iso-ccitt remote-operations(4) notation(0)} +DEFINITIONS ::= +BEGIN +EXPORTS OPERATION, ERROR; +-- macro definition for operations +OPERATION MACRO ::= +BEGIN +TYPE NOTATION ::= Argument Result Errors LinkedOperations +VALUE NOTATION ::= value (VALUE CHOICE { + localValue INTEGER, + globalValue OBJECT IDENTIFIER}) +Argument ::= "ARGUMENT" NamedType | empty +Result ::= "RESULT" ResultType | empty +ResultType ::= NamedType | empty +Errors ::= "ERRORS" "{" ErrorNames "}" | empty +LinkedOperations ::= "LINKED" "{" LinkedOperationNames "}" | empty +ErrorNames ::= ErrorList | empty +ErrorList ::= Error | ErrorList "," Error +Error ::= value (ERROR) -- shall reference an error value + | type -- shall reference an error type if no error + -- value is specified +LinkedOperationNames ::= OperationList | empty +OperationList ::= Operation | OperationList "," Operation +Operation ::= value (OPERATION) -- shall reference an operation value + | type -- shall reference an operation type if no + -- operation value is specified +NamedType ::= identifier type | type +END -- of OPERATION MACRO + +``` + +``` + +-- macro definition for operations errors +ERROR MACRO ::= +BEGIN +TYPE NOTATION ::= Parameter +VALUE NOTATION ::= value (VALUE CHOICE { + localValue INTEGER, + globalValue OBJECT IDENTIFIER}) +Parameter ::= "PARAMETER" NamedType | empty +NamedType ::= identifier type | type +END -- of ERROR MACRO +END -- end of Remote-Operation-Notation + +``` + +# Appendix IV + +## Formal definitions of remote operations notation using Recommendation X.680 [8] + +TABLE IV.1/Q.2932.1 + +### Formal definition of remote operations data types (extract of Annex A/X.880 [17]) + +``` + +Remote-Operations-Information-Objects + {joint-iso-itu-t remote-operations(4) informationObjects(5) version 1(0)} +DEFINITIONS ::= +BEGIN +-- exports everything +IMPORTS emptyBind, emptyUnbind + FROM {joint-iso-ccitt remote-operations(4) useful-definitions(7) version1(0)} +OPERATIONS ::= CLASS +{ + &ArgumentType OPTIONAL, + &argumentTypeOptional BOOLEAN OPTIONAL, + &returnResult BOOLEAN DEFAULT TRUE, + &ResultType OPTIONAL, + &resultTypeOptional BOOLEAN OPTIONAL, + &Errors ERROR OPTIONAL, + &Linked OPERATION OPTIONAL, + &synchronous BOOLEAN DEFAULT FALSE, + &alwaysReturns BOOLEAN DEFAULT TRUE, + &InvokePriority Priority OPTIONAL, + &ResultPriority Priority OPTIONAL, + &operationCode Code UNIQUE OPTIONAL +} + +``` + +``` + +WITH SYNTAX +{ + [ARGUMENT &ArgumentType [OPTIONAL &argumentTypeOptional]] + [RESULT &ResultType [OPTIONAL &resultTypeOptional]] + [RETURN RESULT &returnResult] + [ERRORS &Errors] + [LINKED &Linked] + [SYNCHRONOUS &synchronous] + [ALWAYS RESPONDS &alwaysReturns] + [INVOKE PRIORITY &InvokePriority] + [RESULT PRIORITY &ResultPriority] + [CODE &operationCode] +} +ERROR ::= CLASS +{ + &ParameterType OPTIONAL, + ¶meterTypeOptional BOOLEAN + &ErrorPriority OPTIONAL, + &errorCode Code UNIQUE OPTIONAL +} +WITH SYNTAX +{ + [PARAMETER &ParameterType [OPTIONAL ¶meterTypeOptional]] + [PRIORITY &ErrorPriority] + [CODE &errorCode] +} +OPERATION-PACKAGE ::= CLASS +{ + &Both OPERATION OPTIONAL, + &Consumer OPERATION OPTIONAL, + &Supplier OPERATION OPTIONAL, + &id OBJECT IDENTIFIER UNIQUE OPTIONAL +} +WITH SYNTAX +{ + [OPERATIONS &Both] + [CONSUMER INVOKES &Supplier] + [SUPPLIER INVOKES &Consumer] + [ID &id] +} +CONNECTION-PACKAGE ::= CLASS +{ + &bind OPERATION DEFAULT emptyBind, + &unbind OPERATION DEFAULT emptyUnbind, + &responderCanUnbind BOOLEAN DEFAULT FALSE, + &unbindCanFail BOOLEAN DEFAULT FALSE, + &id OBJECT IDENTIFIER UNIQUE OPTIONAL +} + +``` + +#### **WITH SYNTAX** + +``` + +{ + [BIND] &bind] + [UNBIND] &unbind] + [RESPONDER UNBIND] &responderCanUnbind] + [FAILURE TO UNBIND] &unbindCanFail] + [ID] &id] +} + +``` + +#### **CONTRACT ::= CLASS** + +``` + +{ + &connection CONNECTION-PACKAGE OPTIONAL, + &OperationsOf OPERATION-PACKAGE OPTIONAL, + &InitiatorConsumerOf OPERATION-PACKAGE OPTIONAL, + &InitiatorSupplierOf OPERATION-PACKAGE OPTIONAL, + &id OBJECT IDENTIFIER UNIQUE OPTIONAL +} + +``` + +#### **WITH SYNTAX** + +``` + +{ + [CONNECTION] &connection] + [OPERATIONS OF] &OperationsOf] + [INITIATOR CONSUMER OF] &InitiatorConsumerOf] + [RESPONDER CONSUMER OF] &InitiatorSupplierOf] + [ID] &id] +} + +``` + +#### **ROS-OBJECT-CLASS ::= CLASS** + +``` + +{ + &Is ROS-OBJECT-CLASS OPTIONAL, + &Initiates CONTRACT OPTIONAL, + &Responds CONTRACT OPTIONAL, + &InitiatesAndResponds CONTRACT OPTIONAL, + &id OBJECT IDENTIFIER UNIQUE +} + +``` + +#### **WITH SYNTAX** + +``` + +{ + [IS] &Is] + [BOTH] &InitiatesAndResponds] + [INITIATES] &Initiates] + [RESPONDS] &Responds] + ID &id] +} + +``` + +#### **Code ::= CHOICE** + +``` + +{ + local INTEGER, + global OBJECT IDENTIFIER +} + +``` + +#### **Priority ::= INTEGER (0..MAX)** + +**END -- end of Information Object specifications** + +# Appendix V + +## Assignment of object identifiers + +The following object identifiers are assigned within this Recommendation. + +**ccitt recommendation q 2932 facility-information-element-APDU(3)** + +**ccitt recommendation q 2932 revised-facility-information-element-APDU(3)** + +**ccitt recommendation q 2932 embedded-dSS2-types(7)** + +# 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.2934-199805-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2934-199805-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7a6350af5bd4a4463246e63c7765133c8a58d577 --- /dev/null +++ b/marked/Q/T-REC-Q.2934-199805-I_PDF-E/raw.md @@ -0,0 +1,667 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2934** + +(05/98) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Digital subscriber Signalling System No. 2 – +Switched virtual path capability** + +ITU-T Recommendation Q.2934 + +(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.2934** + +## **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 – SWITCHED VIRTUAL PATH CAPABILITY** + +## **Summary** + +This Recommendation specifies the procedures for establishing, maintaining, and clearing of switched virtual path connections. It specifies extensions to Recommendations Q.2931 [1], Q.2961.1 [2], Q.2961.2 [3], Q.2961.3 [4], Q.2961.4 [5] and Q.2961.6 [6] to provide this capability. + +### **Source** + +ITU-T Recommendation Q.2934 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. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +| | Page | +|---------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References ..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations ..... | 2 | +| 5 Description ..... | 3 | +| 6 Operational requirements ..... | 3 | +| 6.1 Provision and withdrawal ..... | 3 | +| 6.2 Requirements on the originating network side ..... | 3 | +| 6.3 Requirements on the destination network side ..... | 3 | +| 7 Primitive definitions and state definitions ..... | 3 | +| 7.1 Primitive definitions ..... | 3 | +| 7.2 State definitions ..... | 3 | +| 8 Coding requirements – Information elements ..... | 3 | +| 8.1 Broadband bearer capability ..... | 3 | +| 8.2 Connection identifier ..... | 4 | +| 8.3 Restart indicator ..... | 4 | +| 8.4 OAM traffic descriptor ..... | 4 | +| 9 Signalling procedures at the coincident S B and T B reference point ..... | 5 | +| 9.1 Call/connection establishment at the origination interface ..... | 5 | +| 9.1.1 Associated signalling ..... | 5 | +| 9.1.2 Non-associated signalling ..... | 5 | +| 9.2 Call/connection establishment at the destination interface ..... | 5 | +| 9.2.1 Associated signalling ..... | 5 | +| 9.2.2 Non-associated signalling ..... | 5 | +| 9.2.3 Compatibility check ..... | 6 | +| 9.3 Restart procedure ..... | 6 | +| 10 Procedures at the T B reference point for interworking with private B-ISDNs ..... | 8 | +| 11 Interworking with other networks ..... | 8 | +| 11.1 Interworking with entities which do not support the SVP capability ..... | 8 | +| 11.2 Interworking with N-ISDN ..... | 8 | +| 12 Interactions ..... | 9 | + +| | Page | +|------------------------------------------------------------------------------------------------------------------------|-------------| +| 12.1 Interactions with supplementary services..... | 9 | +| 12.2 Interactions with other capabilities..... | 9 | +| 13 Timers..... | 9 | +| 14 Dynamic description (SDLs)..... | 9 | +| Annex A – Valid combinations of bearer class, broadband transfer capability and ATM traffic descriptor parameters..... | 9 | +| Appendix I – Management of VPCI and bandwidth ..... | 14 | + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 – SWITCHED VIRTUAL PATH CAPABILITY** + +*(Geneva, 1998)* + +# **1 Scope** + +This Recommendation specifies the procedures for establishing, maintaining, and clearing of switched virtual path connections by means of the Digital Subscriber Signalling System No. 2 (DSS 2) protocol in a point-to-point call/connection. The procedures are applicable at the TB reference point or coincident SB and TB reference point (as defined in Recommendation I.413) of the Broadband-Integrated Services Digital Network (B-ISDN). + +This Recommendation is part of the DSS 2 family of ITU-T Recommendations. It specifies extensions to Recommendations Q.2931 [1], Q.2961.1 [2], Q.2961.2 [3], Q.2961.3 [4], Q.2961.4 [5] and Q.2961.6 [6] and does not repeat states, information elements, messages and procedures contained therein but only specifies extensions related to the switched virtual path capability. + +# **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.2931 (1995), *Digital subscriber Signalling System No. 2 – User Network Interface (UNI) layer 3 specification for basic call/connection control* and its Amendment 1 (1997). +- [2] 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 GII rate parameter set.* +- [3] ITU-T Recommendation 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.* +- [4] ITU-T Recommendation 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.* +- [5] ITU-T Recommendation Q.2961.4 (1997), *Digital subscriber Signalling System No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the ATM Block Transfert (ABT) ATM transfer capability.* +- [6] ITU-T Recommendation 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 Recommendation Q.2962 (1998), *Digital subscriber Signalling System No. 2 – Connection characteristics negotiation during call/connection establishment phase.* +- [8] ITU-T Recommendation Q.2963.1 (1996), *Digital subscriber Signalling System No. 2 – Connection modification: Peak cell rate modification by the connection owner.* +- [9] ITU-T Recommendation Q.2963.2 (1997), *Digital subscriber Signalling System No. 2 – Connection modification: Modification procedures for sustainable cell rate parameters.* +- [10] ITU-T Recommendation Q.2963.3 (1998), *Digital subscriber Signalling System No. 2 – Connection modification – ATM traffic descriptor modification with negotiation by the connection owner.* +- [11] ITU-T Recommendation Q.2951 (1995), *Stage 3 description for number identification supplementary services using B-ISDN Digital subscriber Signalling System No. 2 (DSS 2) – Basic call.* +- [12] ITU-T Recommendation Q.2955 (1997), *Stage 3 description for community of interest supplementary services using B-ISDN Digital subscriber Signalling System No. 2 (DSS 2).* +- [13] ITU-T Recommendation Q.2957 (1995), *Stage 3 description for additional information transfer supplementary services using B-ISDN Digital subscriber Signalling System No. 2 (DSS 2) – Basic call.* +- [14] ITU-T Recommendation Q.2964.1 (1996), *Digital subscriber Signalling System No. 2 – Basic Look-ahead.* +- [15] ITU-T Recommendation Q.2959 (1996), *Digital subscriber Signalling System No. 2 – Call priority.* +- [16] ITU-T Recommendation I.371 (1996), *Traffic control and congestion control in B-ISDN.* +- [17] ITU-T Recommendation I.356 (1996), *B-ISDN ATM layer cell transfer performance.* + +# 3 Definitions + +The definitions of Annex J/Q.2931 [1] apply. + +This Recommendation defines the following term: + +**switched virtual path connection:** A virtual path connection controlled by signalling procedures. + +# 4 Abbreviations + +The definitions of Annex J/Q.2931 [1] apply. + +This Recommendation also uses the following abbreviations: + +| | | +|--------|-----------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband-Integrated Services Digital Network | +| DSS 2 | Digital subscriber Signalling System No. 2 | + +# 5 Description + +This Recommendation specifies the signalling protocol for establishing, maintaining, and releasing point-to-point, switched virtual path connections. + +# 6 Operational requirements + +## 6.1 Provision and withdrawal + +It is a user and network option to provide the procedures described in this Recommendation. Some networks may not support these procedures when a VP cross-connect is used to connect the user to the network. If implemented, the procedures of this Recommendation may be provided as a subscription option to the served user on the origination side. + +## 6.2 Requirements on the originating network side + +See 6.1. + +## 6.3 Requirements on the destination network side + +See 6.1. + +# 7 Primitive definitions and state definitions + +## 7.1 Primitive definitions + +Clause 8/Q.2931 [1] shall apply. + +## 7.2 State definitions + +No additional states to those specified in Recommendation Q.2931 [1] are required. + +# 8 Coding requirements – Information elements + +See clause 4/Q.2931 [1], clause 8/Q.2961.1 [2], clause 6/Q.2961.2 [3], clause 8/Q.2961.3 [4] and clause 8/Q.2961.4 [5]. This clause identifies the changes to support the switched virtual path capability. + +## 8.1 Broadband bearer capability + +The definition of the broadband bearer capability information element given in Recommendations Q.2961.2 [3], Q.2961.3 [4], Q.2961.4 [5] and Q.2961.6 [6] is extended as shown in Table 1 below. The following codepoint is added to the bearer class field in octet 5: + +**Table 1/Q.2934 –Broadband bearer capability information element** + +| | | +|------------------|------------------------| +| Bits (Octet 5) | | +| 5 4 3 2 1 | | +| 1 1 0 0 0 | Transparent VP Service | + +## 8.2 Connection identifier + +The codepoint 100 shall be added to the preferred/exclusive field in octet 5 in Table 4-16/Q.2931 [1], and a Note 4 shall be added as follows: + +Bits (Octet 5) + +3 2 1 + +0 0 1 Exclusive VPCI; any VCI (see Note 4) + +1 0 0 Exclusive VPCI; no VCI (see Note 4) + +NOTE 4 – In the restart procedure, either "Exclusive VPCI; any VCI" or "Exclusive VPCI; no VCI" may be used to indicate a virtual path to be restarted. + +Note 1 in Figure 4-22/Q.2931 [1] shall be replaced with the following Note: + +NOTE 1 – If the preferred/exclusive field indicates "any VCI" or "no VCI", the VCI field shall be ignored. + +## 8.3 Restart indicator + +For the following two class field codepoints the semantics and Notes 2 and 3 shall be changed as follows: + +Bits (Octet 5) + +3 2 1 + +0 0 1 indicated switched virtual path or all virtual channels in the indicated VPC which are controlled via the signalling channel on which the RESTART message is sent (see Note 2) + +0 1 0 all Switched Virtual Channels and switched virtual paths controlled by the layer 3 entity which sends the RESTART message (see Note 3) + +NOTE 2 – The connection identifier information element shall be included and indicates the switched virtual path to be restarted or the virtual path connection in which all Switched Virtual Channels are to be restarted. The virtual channel identification field in the connection identifier information element is ignored. + +NOTE 3 – The connection identifier information element is not included. All Switched Virtual Channels and paths controlled by the point-to-point signalling channel are to be restarted. + +## 8.4 OAM traffic descriptor + +In 4.5.24/Q.2931 [1], Figure 4-30/Q.2931 [1] and Table 4-22/Q.2931 [1], replace all occurrence of "OAM F5 flow" with "OAM F4 flow". + +The following sentence is added to the last part of 4.5.24/Q.2931 [1]: + +"OAM traffic descriptor information element is used for OAM F4 flow in case of SVP, and OAM F5 flow in case of SVC". + +In 4.5.6/Q.2931 [1] and Annex I/Q.2931 [1], replace all occurrence of "OAM F5 flow" with "OAM F4 flow" except in the Note in I.3. + +# 9 Signalling procedures at the coincident SB and TB reference point + +This clause identifies changes to the procedures of Recommendations Q.2931 [1], Q.2961.1 [2], Q.2961.3 [4], Q.2961.4 [5] and Q.2961.6 [6] to support the switched virtual path capability. + +## 9.1 Call/connection establishment at the origination interface + +### 9.1.1 Associated signalling + +Associated signalling does not apply when supporting switched virtual paths. + +### 9.1.2 Non-associated signalling + +In order to request the establishment of a switched virtual path the user shall set the bearer class field of the bearer capability information element in the SETUP message to "Transparent VP Service", and shall indicate one of the following in the connection identifier information element: + +- c) No indication is included (i.e. the connection identifier information element is not included in the SETUP message); or +- d) Exclusive VPCI; no VCI. + +In case c), the network selects any available VPCI. + +In case d), if the indicated VPCI is available, the network selects it for the call. + +The selected VPCI is indicated in the connection identifier information element in the first message returned by the network in response to the SETUP message (e.g. CALL PROCEEDING). The VP associated signalling field is coded as "explicit indication of VPCI". The preferred/exclusive field is coded as "exclusive VPCI; no VCI". + +In case c), if the network is not able to allocate a VPCI, a RELEASE COMPLETE message with Cause #45 "No VPCI/VCI available" is sent by the network. + +In case d), if the indicated VPCI is not available, a RELEASE COMPLETE message with Cause #35 "Requested VPCI/VCI not available" is sent by the network. + +## 9.2 Call/connection establishment at the destination interface + +### 9.2.1 Associated signalling + +Associated signalling does not apply when supporting switched virtual paths. + +### 9.2.2 Non-associated signalling + +When the establishment of a switched virtual path is requested (i.e. the bearer class field of the bearer capability information element in the SETUP message indicates "Transparent VP Service"), the network shall indicate one of the following: + +- c) No indication is included (i.e. the connection identifier information element is not included in the SETUP message); or +- d) Exclusive VPCI; no VCI. + +In case c), the user selects any available VPCI. + +In case d), if the indicated VPCI is available, the user selects it for the call. + +The selected VPCI is indicated in the connection identifier information element in the first message returned by the user in response to the SETUP message (e.g. CALL PROCEEDING). The VP associated signalling field is coded as "explicit indication of VPCI". The preferred/exclusive field is coded as "exclusive VPCI; no VCI". If the connection identifier information element is not present in the first response message, the connection identifier in the SETUP message shall be assumed. + +In case c), if the user is not able to allocate a VPCI, a RELEASE COMPLETE message with Cause #45 "*No VPCI/VCI available*" is sent by the user. + +In case d), if the indicated VPCI is not available, a RELEASE COMPLETE message with Cause #35 "*Requested VPCI/VCI not available*" is sent by the user. + +### 9.2.3 Compatibility check + +Subclause 5.2.2.2.1/Q.2931 [1] shall apply. Only broadband category 1 compatibility information is applicable to switched virtual paths. Currently, no equivalent broadband category 2 compatibility information is defined for switched virtual paths. + +## 9.3 Restart procedure + +This subclause identifies changes to the restart procedures of Recommendation Q.2931 [1] to support the switched virtual path capability. The changes are shown under the specific section headers of Recommendation Q.2931 [1]. + +*5.5/Q.2931 Restart procedure:* + +Replace line 1 of paragraph 2 by: + +The restart procedure is used to return a Switched Virtual Channel, all Switched Virtual Channels in a virtual path, a switched virtual path, or all Switched Virtual Channels and switched virtual paths controlled by the signalling virtual channel to the idle condition. + +Replace line 3 of Note by: + +In the case where the same Switched Virtual Channel(s) or switched virtual path(s) are specified, they shall not be considered free for reuse until all relevant restart procedures are completed. + +*5.5.1/Q.2931 Sending RESTART:* + +*5.5.1.1/Q.2931 Normal procedure* + +Replace paragraph 1 by: + +A RESTART message is sent by the network or user equipment in order to return Switched Virtual Channels or switched virtual paths to the idle condition. The Restart indicator information element shall be present in the RESTART message to indicate whether an "Indicated Switched Virtual Channel", "indicated switched virtual path or all Switched Virtual Channels in a virtual path" or "all Switched Virtual Channels and switched virtual paths controlled by the layer 3 entity" are to be restarted. If the Restart indicator information element is coded as "indicated Switched Virtual Channel" or "indicated switched virtual path or all Switched Virtual Channels in a virtual path", then the connection identifier information element shall be present to indicate which Switched Virtual Channel or switched virtual path is to be returned to the idle condition. If the Restart indicator information element is coded as "all Switched Virtual Channels and switched virtual paths controlled by the layer 3 entity", then the connection identifier information element shall not be included. + +Replace lines 3 and 4 of paragraph 2 by: + +Receipt of a RESTART ACKNOWLEDGE message stops timer T316 and indicates that the Switched Virtual Channel(s)/switched virtual path(s) and associated resources [e.g. call reference value(s)] can be freed for reuse. The Null state will be entered after the Switched Virtual Channel/switched virtual path and call reference value are released. + +Replace paragraph 4 by: + +Calls associated with restarted Switched Virtual Channel(s)/switched virtual path(s) shall be cleared towards the remote parties using Cause #41, "*Temporary failure*". + +#### 5.5.1.2/Q.2931 Exceptional procedures + +Replace line 2 of paragraph 1 by: + +While timer T316 is running, the Switched Virtual Channel(s)/switched virtual path(s) being restarted shall not be used to support new calls requested using the call set-up procedures. + +Replace line 6 of paragraph 1 by: + +The Switched Virtual Channel(s)/switched virtual path(s) is considered to be in an out-of-service condition until maintenance action has been taken. + +Replace paragraph 2 by: + +If a RESTART ACKNOWLEDGE message is received indicating a different set of Switched Virtual Channel(s)/switched virtual path(s) from the set indicated in the RESTART message, the RESTART ACKNOWLEDGE message shall be discarded. + +### 5.5.2/Q.2931 Receipt of RESTART: + +#### 5.5.2.1/Q.2931 Normal procedures + +Replace line 1 of paragraph 1 by: + +Upon receiving a RESTART message the recipient shall enter the Restart state associated to the global call reference and start timer T317; it shall then initiate the appropriate internal actions to return the specified Switched Virtual Channel(s)/switched virtual path(s) to the idle condition and release all call references associated with it. + +Replace paragraph 2 by: + +Calls associated with restarted Switched Virtual Channel(s)/switched virtual path(s) shall be cleared towards the remote parties using Cause #41, "*Temporary failure*". + +Replace paragraph 3 by: + +Even if all the specified Switched Virtual Channel(s)/switched virtual path(s) are in the idle condition, or already in the process of restart to the idle condition, receiving entity shall transmit a RESTART ACKNOWLEDGE message to the originator upon receiving a RESTART message. + +Replace paragraph 4 by: + +If the Restart indicator information element is coded as "all Switched Virtual Channels and switched virtual paths controlled by the layer 3 entity which sends the RESTART message", then all calls on all interfaces associated with the signalling virtual channel shall be cleared. + +In paragraph 5, replace all occurrences of "all user plane virtual channels in the indicated VPC controlled via the signalling virtual channel in which the RESTART message is sent" by "indicated switched virtual path or all Switched Virtual Channels in a virtual path". + +In paragraph 7, replace all occurrences of "virtual channels" by "Switched Virtual Channels and switched virtual paths". + +#### 5.5.2.2/Q.2931 *Exceptional procedures* + +Replace paragraphs 2, 3 and 4 by: + +If the Restart indicator information element is coded as "all Switched Virtual Channels and switched virtual paths controlled by the layer 3 entity which sends the RESTART message" and a connection identifier information element is included, the connection identifier information element is treated as described in 5.6.8.3/Q.2931 [1]. + +If the Restart indicator information element is coded as "indicated Switched Virtual Channel" or "indicated switched virtual path or all Switched Virtual Channels in a virtual path" and the connection identifier information element is not included, then the procedures in 5.6.7.1/Q.2931 [1] shall be followed. + +If the Restart indicator information element is coded as "indicated Switched Virtual Channel" or "indicated switched virtual path or all Switched Virtual Channels in a virtual path" and the connection identifier information element contains an unrecognizable VPCI, then the procedures in 5.6.7.2/Q.2931 [1] shall be followed. + +If the restart Indicator information element in the received RESTART message is coded "indicated Switched Virtual Channel" and the VPCI indicated in Connection identification information element is being used for an active switched virtual path, then the procedures in 5.6.7.2/Q.2931 [1] shall be followed. + +# 10 Procedures at the TB reference point for interworking with private B-ISDNs + +The procedures of clause 9 apply. + +# 11 Interworking with other networks + +## 11.1 Interworking with entities which do not support the SVP capability + +If an entity which does not support the SVP capability described in this Recommendation receives a broadband bearer capability information element identifying the transparent VP service in a SETUP message, it shall follow the procedures described in 5.6, 5.7 and 5.8/Q.2931 [1]. + +## 11.2 Interworking with N-ISDN + +For SVPs interworking with an N-ISDN entity is not possible. SVP call/connection requests shall be rejected at the interworking point with Cause #63 "*Service or option not available, unspecified*". + +# 12 Interactions + +## 12.1 Interactions with supplementary services + +The support of the SVP capability described in this Recommendation has no impact on the support of the CLIP, CLIR, COLP, COLR, DDI, SUB, MSN, CUG, and UUS supplementary services as specified in Recommendations Q.2951 [11], Q.2955 [12], and Q.2957 [13]. + +## 12.2 Interactions with other capabilities + +If negotiation of SVP connection characteristics during call/connection set-up is supported, the procedures of Recommendation Q.2962 [7] apply. In this case, the connection characteristics of the SVP may be negotiated during call/connection establishment by means of the alternative traffic descriptor or the minimum acceptable traffic descriptor. + +If connection modification is supported for SVPs, the procedures of Recommendations Q.2963.1 [8] and Q.2963.2 [9] apply. + +If connection modification with negotiation is supported for SVPs, the procedures of Recommendation Q.2963.3 [10] apply. + +The support of the SVP capability described in this Recommendation has no impact on the support of Look-ahead and Call Priority capabilities as specified in Recommendations Q.2964.1 [14] and Q.2959 [15]. + +# 13 Timers + +See clause 7/Q.2931 [1]. No additional timers are defined. + +# 14 Dynamic description (SDLs) + +See Annex A/Q.2931 [1]. No additional SDLs are defined. + +# 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 for the SVP capability. + +NOTE 1 – The BTC values considered in Table A.1 are the ones applicable at the time of publication of this Recommendation. This does not preclude other combinations to be defined in future when new BTC values are specified. + +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 when the QoS Class is 0. In addition, Table A.1 identifies the I.371 [16] ATM transfer capability that supports the requested ATM transfer capability and the I.356 [17] QoS class that supports the implicitly requested QoS. + +NOTE 2 – Recommendation I.371 [16] constrains the ATM transfer capability to be the same for both directions of a connection. + +Table A.2 identifies the ATM transfer capability which may be used to enable backward compatibility with ATCs not defined in Recommendation I.371 [16]. 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 [16]. This is in part due to the need to be backward compatible with the first edition of Recommendation Q.2931 [1] (1995) and also due to the implicit association of End-to-end timing requirements for some of the BTC codepoints. + +At the SB reference point or coincident SB/TB reference point, a user compliant to this Recommendation shall not use these combinations in a transmitted SETUP message, but shall be able to accept these combinations on reception. A network compliant to this Recommendation shall relay these combinations. + +**Table A.1/Q.2934 –Valid combinations of traffic related parameters in the SETUP message** + +| | | | | | | | | | +|--------------------------------------------------------------------------------|---------|---------|----------|-----------------|--------------------|--------------------|------------------|------------------| +| Broadband bearer capability | | | | | | | | | +| Bearer class | VP | VP | VP | VP | VP | VP | VP | VP | +| BTC (value) | 7 | 11 | 19 | 12 | 16 | 17 | 20 | 21 | +| Traffic descriptor for a given direction | | | | | | | | | +| PCR (CLP = 0) | | | | | | | | | +| 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 | | Opt
(Note 4) | Opt
(Note 4) | | | +| ABR MCR | | | | S | | | | | +| PCR (RM) | | | | | S | S | | | +| Tagging (Note 2) | N | N | N | N | N | N | N | N | +| End-to-end timing required
(Note 3) | Y | N | Y | N | Y | N | N | N | +| For the given direction: | | | | | | | | | +| Requested ATC [4] | DBR | SBR1 | SBR1 | ABR
(Note 5) | ABT-DT
(Note 6) | ABT-IT
(Note 6) | SBR2
(Note 7) | SBR3
(Note 7) | +| Implicitly requested QoS
when the QoS class is 0
| Class 1 | Class 2 | (Note 1) | Class 3 | Class 1 | Class 2 | Class 3 | Class 3 | +| For the given direction: | | | | | | | | | +| I.371 [14] ATC that supports
the requested ATC
| DBR | SBR1 | SBR1 | ABR | ABT-DT | ABT-IT | SBR2 | SBR3 | +| I.356 [15] QoS class that
supports the implicitly
requested QoS
| Class 1 | Class 2 | Class 1 | Class 3 | Class 1 | Class 2 | Class 3 | Class 3 | + +**Table A.1/Q.2934 –Valid combinations of traffic related parameters in the SETUP message (concluded)** + +### **Notes relatives to Table A.1/Q.2934:** + +NOTE 1 – The implicitly requested QoS class in this case is not defined in Recommendation I.356 [17]. + +NOTE 2 – 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. + +NOTE 3 – This information is not signalled. + +NOTE 4 – Optional. When not specified, SCR (CLP = 0 + 1) is equal to 0 and MBS (CLP = 0 + 1) is equal to 1. + +NOTE 5 – For the definition of this ATC see Recommendation Q.2961.3 [4]. + +NOTE 6 – For the definition of this ATC see Recommendation Q.2961.4 [5]. + +NOTE 7 – For the definition of this ATC see Recommendation Q.2961.6 [6]. + +A blank in the table means that the traffic parameter is not applicable for this combination. + +PCR            Peak Cell Rate + +SCR            Sustainable Cell Rate + +MBS            Maximum Burst Size + +ABR MCR    ABR Minimum cell rate + +RM             Resource Management + +S                Specified + +Opt            Optional + +For the tagging row, + +Y                Yes + +N                No or No indication + +Y/N    Either "Yes" or "No or No Indication" + +**Table A.2/Q.2934 – Valid combinations of Traffic related parameters in the +SETUP message supported for backward compatibility** + +| | | | | | | | +|------------------------------------------------------------------------|----------|--------------|--------------|--------------|----------|----------| +| Broadband bearer capability | | | | | | | +| Bearer class | VP | VP | VP | VP | VP | VP | +| BTC (value) | 5 | 5 | absent or 10 | absent or 10 | 9 | 9 | +| Traffic descriptor for a given direction | | | | | | | +| PCR (CLP = 0) | | S | | | | | +| PCR (CLP = 0 + 1) | S | S | S | S | S | S | +| {SCR, MBS} (CLP = 0) | | | S | | S | | +| {SCR, MBS} (CLP = 0 + 1) | | | | S | | S | +| Tagging (Note 9) | N | Y/N | Y/N | N | Y/N | N | +| End-to-end timing required | Y | Y | N | N | Y | Y | +| For the given direction: | | | | | | | +| Requested ATC [4] | (Note 1) | (Note 1) | (Note 4) | (Note 6) | (Note 4) | (Note 6) | +| Implicitly requested QoS when the QoS class is 0 | (Note 2) | (Note 2) | Class 3 | (Note 5) | (Note 7) | (Note 7) | +| For the given direction: | | | | | | | +| I.371 [14] ATC that supports the requested ATC | DBR | DBR (Note 3) | (Note 4) | SBR1 | (Note 8) | SBR1 | +| I.356 [15] QoS class that supports the implicitly requested QoS | Class 1 | Class 1 | Class 3 | Class 2 | | Class 1 | + +NOTE 1 – The requested capability in this case is not defined in Recommendation I.371 [16] and differs from the DBR ATM transfer capability (see Recommendation I.371 [16]) only in that selective discardability of CLP = 1 cells may apply. + +NOTE 2 – The implicitly requested QoS class in this case is not defined in Recommendation I.356 [17] and differs from QoS class 1 (see Recommendation I.356 [17]) in that the CLR commitment is only for CLP = 0 cells. + +NOTE 3 – PCR (CLP = 0) is ignored and tagging is not performed. + +NOTE 4 – The requested or provided capability in this case is not defined in Recommendation I.371 [16] and differs from the SBR2/SBR3 ATM transfer capability as defined in Recommendation I.371 [16] and supported by the signalling procedures specified in Recommendation Q.2961.6 [6], in that tagging is applied only locally according to the procedures described in Recommendation Q.2961.1 [2]. + +NOTE 5 – The implicitly requested QoS class corresponds to QoS class 3 (see Recommendation I.356 [17]). + +NOTE 6 – The requested capability in this case is not defined in Recommendation I.371 [16] and differs from the SBR1 ATM transfer capability (see Recommendation I.371 [16]) only in that selective discardability of CLP = 1 cells may apply. + +**Table A.2/Q.2934 – Valid combinations of Traffic related parameters in the +SETUP message supported for backward compatibility (concluded)** + +NOTE 7 – The implicitly requested QoS class in this case is not defined in Recommendation I.356 [17] and differs from QoS class 3 (see Recommendation I.356 [17]) in that end-to-end timing is required. + +NOTE 8 – There is no combination recommended in Recommendation I.356 [17]. + +NOTE 9 – 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 the 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" + +# APPENDIX I + +## Management of VPCI and bandwidth + +Mutually exclusive subsets of VPCIs need to be defined for Switched Virtual Channel (SVC) connections and Switched Virtual Path (SVP) connections. For SVPs, subsets should be defined on a physical interface basis. + +When sending a SETUP message the initiating entity would first try to select a VPCI from the subset(s) of VPCIs allocated for SVPs. Based on the connection request, bandwidth will be assigned to this VPCI from the pool of bandwidth associated with the VPCI subset the selected VPCI belongs to. The selected VPCI will be signalled in the connection identifier information element together with other parameters in the SETUP. If there is no available VPCI belonging to the subset(s) of VPCIs allocated for SVPs, or the available bandwidth is insufficient to satisfy the connection request, the entity will request the remote entity to allocate VPCI and bandwidth, i.e. the SETUP will be sent without the connection identifier information element. + +![A hierarchical diagram showing the management of VPCI and bandwidth resources. At the top level is 'VPCIs'. It branches into three categories: 'Subset of VPCIs for SVP – Interface 2', 'Subset of VPCIs for SVP – Interface 1', and 'Subset of VPCIs for SVC'. The 'Subset of VPCIs for SVP – Interface 1' category further branches into 'Subset of VPCIs – Assigning' and 'Subset of VPCIs – non-Assigning'. Both of these lead to a 'BW Pool'. The 'BW Pool' for the 'Assigning' category branches into four 'VPCI' labels, each of which leads to a 'BW' label. The 'BW Pool' for the 'non-Assigning' category leads to a single 'BW Pool' label.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +graph TD + VPCIs[VPCIs] --> SVP2[Subset of VPCIs for SVP – Interface 2] + VPCIs --> SVP1[Subset of VPCIs for SVP – Interface 1] + VPCIs --> SVC[Subset of VPCIs for SVC] + SVP1 --> Assigning[Subset of VPCIs – Assigning] + SVP1 --> nonAssigning[Subset of VPCIs – non-Assigning] + Assigning --> BWPool1[BW Pool] + nonAssigning --> BWPool2[BW Pool] + BWPool1 --> VPCI1[VPCI] + BWPool1 --> VPCI2[VPCI] + BWPool1 --> VPCI3[VPCI] + BWPool1 --> VPCI4[VPCI] + VPCI1 --> BW1[BW] + VPCI2 --> BW2[BW] + VPCI3 --> BW3[BW] + VPCI4 --> BW4[BW] + +``` + +A hierarchical diagram showing the management of VPCI and bandwidth resources. At the top level is 'VPCIs'. It branches into three categories: 'Subset of VPCIs for SVP – Interface 2', 'Subset of VPCIs for SVP – Interface 1', and 'Subset of VPCIs for SVC'. The 'Subset of VPCIs for SVP – Interface 1' category further branches into 'Subset of VPCIs – Assigning' and 'Subset of VPCIs – non-Assigning'. Both of these lead to a 'BW Pool'. The 'BW Pool' for the 'Assigning' category branches into four 'VPCI' labels, each of which leads to a 'BW' label. The 'BW Pool' for the 'non-Assigning' category leads to a single 'BW Pool' label. + +T1199150-98 + +**Figure I.1/Q.2934 – Management of VPCI and bandwidth resources between the entities at the UNI** + + + +# 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.2957.1-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4eb59a86e7f853a82bd7fa9ccf45c68cb116248 --- /dev/null +++ b/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e2afd90e5081164a00e7d9b25ccefdddc83a8b608d0e6869a6e97256dd6bb58 +size 8227 diff --git a/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b39f25eb121b623468ce3d2c6c44c9afe6f7d142 --- /dev/null +++ b/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c834e357d42a1bc0a3900d7c1750237d6aab026f8d550d5bd99cdea4e2830a3c +size 47515 diff --git a/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b0648ba2e6e33e71076ed8f3bf4a34998074ca3b --- /dev/null +++ b/marked/Q/T-REC-Q.2957.1-199502-I_PDF-E/raw.md @@ -0,0 +1,456 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.2957** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/95) + +# **B-ISDN APPLICATION PROTOCOLS FOR ACCESS SIGNALLING** --- + +**STAGE 3 DESCRIPTION FOR ADDITIONAL +INFORMATION TRANSFER SUPPLEMENTARY +SERVICES USING B-ISDN DIGITAL +SUBSCRIBER SIGNALLING SYSTEM No. 2 +(DSS 2) – BASIC CALL +Clause 1 – User-to-user signalling (UUS)** + +**ITU-T Recommendation Q.2957** + +(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.2957, clause 1, was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 7th of February 1995. + +--- + +## NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|-----------------------------------------------------------------------------------------------------|-------------| +| 1 User-to-User Signalling (UUS) ..... | 1 | +| 1.1 Scope ..... | 1 | +| 1.2 References..... | 1 | +| 1.3 Definitions ..... | 2 | +| 1.4 Abbreviations..... | 2 | +| 1.5 Description..... | 2 | +| 1.6 Operational requirements..... | 2 | +| 1.7 State definitions ..... | 3 | +| 1.8 Coding Requirements ..... | 3 | +| 1.9 Signalling procedures at the coincident S B and T B reference point ..... | 6 | +| 1.10 Procedures for interworking with private networks ..... | 8 | +| 1.11 Interworking with other networks ..... | 8 | +| 1.12 Interaction with other supplementary services ..... | 9 | +| 1.13 Parameter values (timers) ..... | 9 | +| 1.14 Dynamic description (SDLs) ..... | 9 | +| Appendix I – Signalling flows..... | 9 | +| Appendix II – Instruction indicators..... | 10 | + +## **SUMMARY** + +This Recommendation defines the operation of the Digital subscriber Signalling System No. 2 (DSS 2) for the support of the User-to-User Signalling (UUS) supplementary service at the $T_B$ or the coincident $S_B$ and $T_B$ reference point of the user to network interface of the Broadband-Integrated Services Digital Network (B-ISDN). + +The User-to-User Signalling (UUS) supplementary service allows a B-ISDN user to send and receive a limited amount of information to/from another B-ISDN user over the signalling virtual channel in association with a call/connection to the other B-ISDN user. + +## STAGE 3 DESCRIPTION FOR ADDITIONAL INFORMATION TRANSFER SUPPLEMENTARY SERVICES USING B-ISDN DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 (DSS 2) – BASIC CALL + +(Geneva, 1995) + +# 1 User-to-User Signalling (UUS) + +## 1.1 Scope + +This Recommendation specifies the stage three of the User-to-User Signalling (UUS) supplementary service 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) protocol. Stage three identifies the protocol procedures and switching functions needed to support a telecommunications service (see Recommendation I.130 [2]). + +In addition, this Recommendation specifies the protocol requirements at the $T_B$ reference point where the service is provided to the user via an intermediate private B-ISDN. + +This Recommendation does not specify the additional protocol requirements where the service is provided to the user via a telecommunications network that is not a B-ISDN. + +The User-to-User Signalling (UUS) supplementary service allows a B-ISDN user to send/receive a limited amount of information to/from another B-ISDN user over the signalling virtual channel in association with a call/connection to the other B-ISDN user. + +For N-ISDN services supported in B-ISDN, see Recommendation I.257.1 [5]. For B-ISDN services, the applicability has yet to be defined. + +This Recommendation is applicable to equipment, supporting the UUS supplementary service, 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. + +## 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 I.413 (1993), *B-ISDN user-network interfaces*. +- [2] CCITT Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*. +- [3] ITU-T Recommendation Q.2931 (1995), *Broadband-Integrated Services Digital Network (B-ISDN) – Digital Subscriber Signalling No. 2 (DSS2) – User-network interface layer 3 specification for basic call/connection control*. +- [4] CCITT Recommendation E.164 (1991), *Numbering plan for the ISDN era*. +- [5] CCITT Recommendation I.257.1 (1992), *User-to-user signalling*. +- [6] CCITT Recommendation X.213 (1992), *Information technology – Network service definition for Open Systems interconnection (OSI)*. +- [7] ITU-T Recommendation I.580 (1993), *General arrangements for interworking between B-ISDN and 64 kbit/s based ISDN*. + +## 1.3 Definitions + +For the purposes of this Recommendation, the following definitions apply: + +- 1.3.1 user:** The DSS 2 protocol entity at the user side of the user-network interface. +- 1.3.2 network:** The DSS 2 protocol entity at the network side of the user-network interface. +- 1.3.3 called user:** The user who is offered an incoming call/connection at the terminating interface. +- 1.3.4 calling user:** The user who initiates an outgoing call/connection at the originating interface. +- 1.3.5 served user:** The user requesting the User-to-User (UUS) supplementary service. + +## 1.4 Abbreviations + +For the purposes of this Recommendation, the following abbreviations are used: + +| | | +|--------|-------------------------------------------------| +| B-ISDN | Broadband Integrated Services Digital Network | +| DSS 2 | Digital Subscriber Signalling System No. 2 | +| ISDN | Integrated Services Digital Network | +| N-ISDN | Narrow-band Integrated Services Digital Network | +| UUS | User-to-User Signalling | +| UUI | User-to-User Information | + +## 1.5 Description + +The UUS supplementary services provide a means of communication between two users by using as a basis the layer 3 protocol defined in clause 5/Q.2931 [3]. User-to-user signalling is used to exchange information between two users to provide the services described in the Stage 1 Service Description. The exchange of user-to-user signalling is limited by flow control procedures provided by the network or the user. The exchange of user-to-user information is not a network acknowledged service. Any acknowledgement procedure shall be controlled at a higher layer between users. + +Three UUS services associated with B-ISDN calls that may be provided by the network to users are: + +- a) *Service 1* – User-to-user information exchanged during the set-up and clearing phases of a call/connection, by transporting the User-user information element within Recommendation Q.2931 [3] call/connection control messages; +- b) *Service 2* – User-to-user information exchanged from the sender's point of view during call/connection establishment, between the ALERTING and CONNECT messages, within USER INFORMATION messages; and +- c) *Service 3* – User-to-user information exchanged while a call/connection is in the Active state, within USER INFORMATION messages. + +All three services may be used separately or in any combination in association with a single call. As an option, at call/connection set-up, users may be able to specify that the requested user-to-user signalling service(s) is (are) required for the call, i.e. the call should not be completed if user-to-user information cannot be passed. + +For B-ISDN Release 1, only UUS service 1 (implicitly requested) is specified and supported. UUS service 1 (explicitly requested), UUS service 2 and UUS service 3 are outside the scope of this Recommendation. + +## 1.6 Operational requirements + +### 1.6.1 Provision/withdrawal + +UUS service 1 must be subscribed to by the calling user. + +### 1.6.2 Requirements on the originating network side + +The basic call/connection control procedures according to 5.1/Q.2931 and 5.4/Q.2931 [3] are applicable. + +### 1.6.3 Requirements on the destination network side + +The basic call/connection control procedures according to 5.2/Q.2931 and 5.4/Q.2931 [3] are applicable. + +### 1.6.4 Assumptions made about the terminal + +Terminal equipment using UUS service 1 is expected to be able to generate and accept the User-user information element (see 1.8.3) as described in 1.9 below. + +## 1.7 State definitions + +The states associated with basic call/connection control according to Recommendation Q.2931 [3] are applicable. + +## 1.8 Coding Requirements + +### 1.8.1 Messages + +The following messages are applicable to the operation of service 1: SETUP, ALERTING, CONNECT, RELEASE, RELEASE COMPLETE, PROGRESS. + +Tables 1-1 to 1-6 show the message contents for UUS service 1 implicit. + +### 1.8.2 Codesets + +The UUS supplementary service information elements are in codeset 0. + +### 1.8.3 Information elements + +The User-user information element is applicable to the operation of service 1. + +The purpose of the User-user information element is to convey information between B-ISDN users. This information is not interpreted by the network, but rather is carried transparently and delivered to the remote user(s). + +The User-user information element shall be considered as an access information element (see Annex J/Q.2931 [3]). + +TABLE 1-1/Q.2957 + +#### Contents of ALERTING message + +Message type: ALERTING + +| Information element | Reference | Direction | Type | Length | +|---------------------------------------------------------------------------------|--------------|-----------|--------------|--------| +| Protocol discriminator | 4.2/Q.2931 | Both | M | 1 | +| Call reference | 4.3/Q.2931 | Both | M | 4 | +| Message type | 4.4.1/Q.2931 | Both | M | 2 | +| Message length | 4.4.2/Q.2931 | Both | M | 2 | +| User-user | 1.8.3 | Both | O (see Note) | 4-133 | +| Other mandatory and optional information elements per Recommendation Q.2931 [3] | | | | | +| NOTE – May be included for UUS service 1 (implicit activation). | | | | | + +TABLE 1-2/Q.2957 + +#### **Contents of CONNECT message** + +Message type: CONNECT + +| Information element | Reference | Direction | Type | Length | +|-----------------------------------------------------------------------------------------|--------------|-----------|--------------|--------| +| Protocol discriminator | 4.2/Q.2931 | Both | M | 1 | +| Call reference | 4.3/Q.2931 | Both | M | 4 | +| Message type | 4.4.1/Q.2931 | Both | M | 2 | +| Message length | 4.4.2/Q.2931 | Both | M | 2 | +| User-user | 1.8.3 | Both | O (see Note) | 4-133 | +| Other mandatory and optional information elements
per Recommendation Q.2931 [3] | | | | | +| NOTE – May be included for UUS service 1 (implicit activation). Not included otherwise. | | | | | + +TABLE 1-3/Q.2957 + +#### **Contents of RELEASE message** + +Message type: RELEASE + +| Information element | Reference | Direction | Type | Length | +|-----------------------------------------------------------------------------------------|--------------|-----------|--------------|--------| +| Protocol discriminator | 4.2/Q.2931 | Both | M | 1 | +| Call reference | 4.3/Q.2931 | Both | M | 4 | +| Message type | 4.4.1/Q.2931 | Both | M | 2 | +| Message length | 4.4.2/Q.2931 | Both | M | 2 | +| User-user | 1.8.3 | Both | O (see Note) | 4-133 | +| Other mandatory and optional information elements
per Recommendation Q.2931 [3] | | | | | +| NOTE – May be included for UUS service 1 (implicit activation). Not included otherwise. | | | | | + +TABLE 1-4/Q.2957 + +#### **Contents of RELEASE COMPLETE message** + +Message type: RELEASE COMPLETE + +| Information element | Reference | Direction | Type | Length | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------|--------------|--------| +| Protocol discriminator | 4.2/Q.2931 | Both | M | 1 | +| Call reference | 4.3/Q.2931 | Both | M | 4 | +| Message type | 4.4.1/Q.2931 | Both | M | 2 | +| Message length | 4.4.2/Q.2931 | Both | M | 2 | +| User-user | 1.8.3 | U → N | O (see Note) | 4-133 | +| Other mandatory and optional information elements
per Recommendation Q.2931 [3] | | | | | +| NOTE – May be included for UUS service 1 where a RELEASE COMPLETE message is sent by the user to reject an incoming SETUP message. Not included otherwise. | | | | | + +TABLE 1-5/Q.2957 + +#### **Contents of SETUP message** + +Message type: SETUP + +| Information element | Reference | Direction | Type | Length | +|----------------------------------------------------------------------------------------------------------|--------------|-----------|--------------|--------| +| Protocol discriminator | 4.2/Q.2931 | Both | M | 1 | +| Call reference | 4.3/Q.2931 | Both | M | 4 | +| Message type | 4.4.1/Q.2931 | Both | M | 2 | +| Message length | 4.4.2/Q.2931 | Both | M | 2 | +| User-user | 1.8.3 | Both | O (see Note) | 4-133 | +| Other mandatory and optional information elements
per Recommendation Q.2931 [3] | | | | | +| NOTE – Always included for UUS service 1 (implicit activation); the length must be at least four octets. | | | | | + +TABLE 1-6/Q.2957 + +#### **Contents of PROGRESS message** + +Message type: PROGRESS + +| Information element | Reference | Direction | Type | Length | +|-----------------------------------------------------------------------------------------|--------------|-----------|--------------|--------| +| Protocol discriminator | 4.2/Q.2931 | Both | M | 1 | +| Call reference | 4.3/Q.2931 | Both | M | 4 | +| Message type | 4.4.1/Q.2931 | Both | M | 2 | +| Message length | 4.4.2/Q.2931 | Both | M | 2 | +| User-user | 1.8.3 | N → U | O (see Note) | 4-133 | +| Other mandatory and optional information elements
per Recommendation Q.2931 [3] | | | | | +| NOTE – May be included for UUS service 1 (implicit activation). Not included otherwise. | | | | | + +The coding for the User-user information element is shown in Figure 1-1. + +![](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +| | | | | | | | | | +|---------------------------------------------------------------|----------|---|----------------------|----------|------------------|---|---|-------| +| Bits | | | | | | | | Octet | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| User-user | | | | | | | | | +| 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | +| Information element identifier | | | | | | | | | +| 1 | Coding | | IE Instruction field | | | | | 2 | +| Ext | standard | | Flag | Reserved | Action indicator | | | | +| Length of User-user contents | | | | | | | | 3, 4 | +| Further contents as in Figure 4-36/Q.931 and Table 4-26/Q.931 | | | | | | | | 5 | + +FIGURE 1-1/Q.2957 + +#### **User-user information element** + +## **1.9 Signalling procedures at the coincident SB and TB reference point** + +### **1.9.1 Activation/deactivation/registration** + +Service 1 shall be activated implicitly as described in 1.9.2 below. In this case, activation and operation of the service are indistinguishable. + +The procedures for call establishment are described in Recommendation Q.2931 [3] with the following modifications. On call request, the SETUP message sent by the calling user shall contain the service 1 request, i.e. the User-user information element. + +The SETUP message sent by the network towards the called user shall also contain the same service requests, i.e. the User-user information element. + +Deactivation procedures are not required to support service 1 implicit. + +### **1.9.2 Call establishment phase – Implicit operation** + +#### **1.9.2.1 Normal operation** + +Service 1 may be implicitly requested by including a User-user information element of variable length as specified in 1.8.2 in the SETUP message, transferred across the user-network interface at the calling side as described in 5.1.1/Q.2931 [3]. This information element is transported by the network and delivered unchanged in the User-user information element included in the SETUP message transferred across the user-network interface at the called side as described in 5.2.1/Q.2931 [3]. For activation purposes, this information element must be at least five octets long, as defined in 1.8.3. + +A User-user information element may be included in the ALERTING and/or CONNECT messages transferred across the user-network interface at the called side as described in 5.2.5/Q.2931 [3]. It may also be included in the RELEASE or RELEASE COMPLETE message (see 1.9.3). The content of this information element is transported by the network and delivered in the User-user information element included in the corresponding message(s) transferred across the user-network interface at the calling side as described in 5.1.6/Q.2931 and 5.1.7/Q.2931 [3]. + +NOTE – In accordance with the Network Service Definition for Open Systems Interconnection, ISO 8348 | Recommendation X.213 [6], the called user may perform compatibility checking using the User-user information element contents (see Annex B/Q.2931 [3]). In the context of the OSI Network Service, service 1 may be used to support the conveyance of the NS-User-Data parameter of the N-CONNECT and N-DISCONNECT primitives. + +#### **1.9.2.2 Exceptional procedures** + +The network shall discard the User-user information element if it is received from the calling user in a SETUP message, but the calling user has not subscribed to UUS service 1. If the discard occurs, the network shall continue to process the call request. The network shall also inform the calling user that the UUS request is not accepted by sending a STATUS message containing cause No. 50 *requested facility non-subscribed*, or cause No. 43 *access information discarded*. + +The network shall discard the User-user information element if it is received from the called user in the ALERTING or CONNECT message, but a request for UUS was not indicated implicitly in the SETUP message delivered to the called user. If discard occurs, the network shall take action on the remaining contents of the message received from the calling user and shall send a STATUS message to the called user containing cause No. 43 *access information discarded*. + +The called user may not be able to interpret incoming User-user information elements. In such situations, the user should discard this information without disrupting normal call handling. No specific signalling is provided by the network to accommodate this situation. + +### **1.9.3 Call clearing phase** + +#### **1.9.3.1 Normal operation** + +A User-user information element may be included in the first message used to initiate the normal call clearing phase (see 5.4.3/Q.2931 and 5.4.4/Q.2931 [3]). + +The information contained in such an information element is transferred to the remote user in the first clearing message (see 5.3.3/Q.2931 and 5.3.4/Q.2931 [3]). Such a transfer is only performed if the information is received at the local exchange of the remote user before sending a clearing message to that user; otherwise, the information is discarded without sending any notification. + +A User-user information element may be included in the first normal clearing message sent by the called user during call establishment. + +If the called user rejects the call with a clearing message containing a User-user information element, the network shall deliver the User-user information element in the RELEASE message sent to the calling user. However, if the network is providing in-band information to the calling user, and chooses not to initiate clearing procedures at that time, the network may deliver the User-user information element in a PROGRESS message sent to the calling user. + +NOTE – It is intended that this capability may be used to provide the clearing data transfer (i.e. conveyance of the NS User-Data parameter to the N-DISCONNECT primitives) described in ISO 8348 | Recommendation X.213 [6]. + +#### 1.9.3.2 Exceptional procedures + +The network shall discard the User-user information element if it is received from either user in a RELEASE or RELEASE COMPLETE message, but a request for UUS was not indicated implicitly in the SETUP message delivered to the called user. If discard occurs, the network shall take action on the remaining contents of the message received from the user. If the clearing party has sent a RELEASE message, the network shall send to the clearing party a RELEASE COMPLETE message containing cause No. 43 *access information discarded*. If the clearing party had sent a RELEASE COMPLETE message, the network shall consider the call as cleared to that party; no additional action shall be taken. + +The network shall discard the User-user information element in the following cases not explicitly discussed elsewhere in clause 9: + +- the overall length of the User-user information element is greater than 133 octets and UUS service 1 was activated implicitly; +- the network receives a message containing the User-user information element, but that message is not allowed to contain UUS as defined by this Recommendation. + +If discard occurs, the network shall take action on the remaining contents of the message received from the sending user and shall send a STATUS message to that user containing cause No. 43, *access information discarded*. However, if the network discards a User-user information element from a received clearing message, the network shall include cause No. 43 *access information discarded*, in the next sequential clearing message sent to the user as specified in 5.4/Q.2931 [3]. If the network discards a User-user information element from a RELEASE COMPLETE message, the network shall consider the call as cleared to that party; no additional action shall be taken. + +## 1.10 Procedures for interworking with private networks + +The procedures described in 1.9 shall apply. + +NOTE – Generally, interworking between a public ISDN and a private ISDN is based on bilateral agreements. + +## 1.11 Interworking with other networks + +### 1.11.1 Interworking with N-ISDNs + +This subclause specifies the particular features to support access signalling interworking between B-ISDN and N-ISDN. The description of interworking assumes the communication scenario B as defined in Annex A/I.580 [7]. + +#### Interworking N-ISDN → B-ISDN + +The DSS 1 User-user information element is mapped to the DSS 2 User-user information element by the terminal adapter or the interworking function by inserting octet 2 and changing the length indication from one to two octets. + +NOTE – It is recommended that the flag bit and the action indicator field in octet 2 is set as shown in Appendix I. + +#### Interworking B-ISDN → N-ISDN + +The DSS 2 User-user information element is mapped to the DSS 1 User-user information element by the terminal adapter or interworking function by removing its second octet and adjusting the length indication without causing other changes to the contents, and by respecting the order of this information element in the DSS 1 message. + +### **1.11.2 Interworking with non-ISDNs** + +In the case of interworking with a non-ISDN, the return of a PROGRESS or an ALERTING message with the Progress indicator information element indicating No. 1 *call is not end-to-end ISDN; further call progress information may be available in-band* to the calling user shall serve as indication that, in particular, the delivery of User-user information elements in call control messages cannot be guaranteed. + +In the case of interworking with a non-ISDN called user, the return of a PROGRESS or an ALERTING message with the Progress indicator information element indicating No. 2 *destination address is non-ISDN* to the calling user shall serve as indication that, in particular, the delivery of User-user information elements in call control messages cannot be guaranteed. + +## **1.12 Interaction with other supplementary services** + +### **1.12.1 Connected Line Identification Presentation** + +No impact. + +### **1.12.2 Connected Line Identification Restriction** + +No impact. + +### **1.12.3 Calling Line Identification Presentation** + +No impact. + +### **1.12.4 Calling Line Identification Restriction** + +No impact. + +### **1.12.5 Direct Dialling-In** + +No impact. + +### **1.12.6 User-to-User Signalling** + +#### **1.12.6.1 Service 1** + +Not relevant. + +### **1.12.7 Multiple Subscriber Number** + +No impact. + +### **1.12.8 Sub-addressing** + +No impact. + +## **1.13 Parameter values (timers)** + +No timers in addition to those used for basic call (Recommendation Q.2931 [3]) are required. + +## **1.14 Dynamic description (SDLs)** + +See Annex A/Q.931 [3]. + +# **Appendix I** + +## **Signalling flows** + +(This appendix does not form an integral part of this Recommendation) + +The signalling flows are not included as they form an integral part of the basic call control procedures. + +# Appendix II + +## Instruction indicators + +(This appendix does not form an integral part of this Recommendation) + +This appendix specifies the values for the instruction indicator field of the messages and information elements defined and used in this Recommendation. + +TABLE II-1/Q.2957 + +### Information element instruction indicators + +| Information element type | Flag | Action indicator | +|--------------------------|------------------------------|---------------------------------------------------------| +| User-user | Follow explicit instructions | Discard information element, proceed, and report status | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2962F-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2962F-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22ae9ebdea9b51453430f8f1eec96d3dbc3b7c43 --- /dev/null +++ b/marked/Q/T-REC-Q.2962F-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.2962F-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2962F-200012-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..34894690b50e66e7d17d2fbad444c45740d98586 --- /dev/null +++ b/marked/Q/T-REC-Q.2962F-200012-I_PDF-E/raw.md @@ -0,0 +1,255 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2962 F** + +(12/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Digital subscriber signalling system No. 2 – +Connection characteristics negotiation during +call/connection establishment phase: Abstract +test suite (ATS) and partial protocol +implementation extra information for testing +(PIXIT) proforma for the network** + +ITU-T Recommendation Q.2962 F + +(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 | +| 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 | +| 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 – Connection characteristics negotiation during call/connection establishment phase: Abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma for the network** + +## **Summary** + +This Recommendation specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network at the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [6]) of implementations conforming to the procedures for the handling of the connection characteristics negotiation during call/connection establishment phase of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2962 [1]. + +Other Recommendations of the Q.2962 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) 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.2962 F 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 modifications..... | 2 | +| 5.2 Technical modifications..... | 3 | +| 5.2.1 AAL parameters IE..... | 3 | +| Appendix I – Bibliography ..... | 3 | + +## **Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase: Abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma for the network** + +# 1 Scope + +This Recommendation specifies the Test Suite Structure and Test Purposes (TSS & TP) for the network at the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [6]) of implementations conforming to the procedures for the handling of the connection characteristics negotiation during call/connection establishment phase of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2962 [1]. + +Other Recommendations of the Q.2962 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) based on this Recommendation. + +This Recommendation is applicable to equipment, supporting connection characteristics negotiation during call/connection establishment phase, to be attached at either side of a TB reference point or coincident SB and TB reference point when used as an access to the public B-ISDN. + +The ATS realizes test purposes identified in the TSS & TP part of the Recommendation and groups them according to the test suite structure given in the TSS & TP. Test purposes defined in the TSS & TP part but not testable are identified in this Recommendation. + +The supplier of a protocol implementation that is claimed to conform to ITU-T Q.2962 [1] is required to complete a copy of the PICS proforma and the PIXIT proforma provided by the testlab. The PIXIT proforma shall contain the tables identified in the partial PIXIT proforma part of this Recommendation and may contain additional information required by the testlab to be able to appropriately execute the test campaign. + +# 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.2962 (1998), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase.* +- [2] ITU-T Q.2962 B (2000), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase: Protocol implementation conformance statement (PICS) proforma.* +- [3] ITU-T Q.2962 E (2000), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase: Test suite structure and test purposes (TSS & TP) for the network.* +- [4] ITU-T Q.2931 (1995), *Digital subscriber signalling system No. 2 – User-network interface (UNI) layer 3 specification for basic call/connection control.* + +- [5] ITU-T Q.2931 B (2000), Broadband integrated services digital network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control: Protocol implementation conformance statement (PICS) proforma. +- [6] ITU-T I.413 (1993), *B-ISDN user-network interface*. +- [7] ETSI EN 301 067-6 V2.1.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network*. + +# 3 Endorsement + +The text of ETSI EN 301 067-6 [7] was approved by ITU-T as Recommendation Q.2962 F 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.2962 [1]. + +# 5 Modifications + +## 5.1 General modifications + +Throughout the text of ETSI EN 301 067-6 [7] replace references and text as shown in the following table: + +| Reference in ETSI EN 301 067-6 | Modified reference | +|--------------------------------|--------------------| +| EN 300 443-1 | ITU-T Q.2931 | +| EN 300 443-2 | ITU-T Q.2931 B | +| EN 301 067-1 | ITU-T Q.2962 | +| EN 301 067-2 | ITU-T Q.2962 B | +| EN 301 067-5 | ITU-T Q.2962 E | +| EN 301 067-6 | ITU-T Q.2962 F | +| Standard | Recommendation | + +### Page 5, Intellectual Property Rights + +Delete the whole section. + +### Page 5, Foreword + +Delete the whole Foreword. + +NOTE 1 – It is replaced by the Foreword of this Recommendation. + +### Page 6, Clause 1 Scope + +Replace the whole clause with the following: + +#### **"1 Scope** + +See clause 1 Scope of this Recommendation above." + +###### **Page 21, Bibliography** + +Delete the whole clause "Bibliography". + +NOTE 2 – Replaced by Appendix I "Bibliography" of this Recommendation. + +###### **Page 22, History** + +Delete the whole clause "History". + +## **5.2 Technical modifications** + +NOTE – Modifications in the TTCN part of this Recommendation are described in terms of changes in the TTCN.GR representation. + +#### **5.2.1 AAL parameters IE** + +In the TTCN, Declarations Part, Test Suite Type Definitions, ASN.1 Type Definitions alter definition for the type "AAL\_contents" as below: + +"OCTET STRING(SIZE(1..20 ~~17~~))". + +NOTE – This limitation may be removed in later versions of the TTCN part. + +# **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 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.* +- [C] ETSI 301 067-2 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 2: Protocol Implementation Conformance Statement (PICS) proforma.* +- [D] ETSI EN 301 067-3 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.* +- [E] ETSI EN 301 067-4 V2.1.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user.* + +- [F] ETSI EN 301 067-5 V1.2.1 (2000), Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network. +- [G] ETSI ETS 300 406 (1995), *Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology.* + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96c18651a1da128f6cffc7707214b70dfac20b44 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:437323ad7407fde2e87a2390575e16c3ef0cb5396e72fd8d48a188a770a6d97d +size 99116 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..692bb71160ef4eac960d7ef72a53129214dbd47c --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4f0db8ceec5be0a2f9105a7f20ade3fdeb54efaa1f5435862e19e99ded8d351 +size 58185 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d4ca706c9cdca1d5e52f6b830108e969bfc5119 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edac238800c0b0c2dcab5358798d182da9e1c175a986891ff6cddc6493212bce +size 175250 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b1f512ffaa1ca029e12956fc1dd89ece0e7118c --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc9b1fab18f878612290a041422ce2aa2e7f21193455dff5e0844a512885f03e +size 124461 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71ab3200b6e92e27d8c93b33f6328e15e4921a35 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:096739e6c02898b47453f6b752d061134a72e0c8a87b77d959a2c44c6b0f5d30 +size 70583 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1a459690c1f790706cdfd7111fd6ab05835f0a4 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60e5493d2c56331e4e24912aa388d98697362c026198c2033437f0686aa248e4 +size 65154 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-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.2963.1-199912-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1be714da86547e1540aac6758a10c3ec8a1a2e65 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1fd3d5af35cdad5b1688e4bf5c3bba6e7815b55b707ae223e82396d6632f943 +size 86125 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1c7d097c894410938c7a9f0b72b366e45f56265 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:181e027b595a6fa3e2e7ef4d27ac2038332c8afd6c3f860c9dd2a6d9d7329722 +size 175768 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..328170b144d7d94ed6ec70c3d9b2a1a24ef69875 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b59670bea20c775677f09b8bf433f80ab74fbb64ce455a71c51a7cf68b27b37d +size 79839 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2a71cb121b52a6a7f5e580010367d2d9d3b4ac9 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7804cdc8b4b7807a3dfcb6d3d8d08c600372cc4a6c6dd7c5ec952c1eb701312 +size 82357 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28ab3e1006a4b78260b8fe1c2110af91716b9857 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0b20a7e4d2596d59a1dcb7d4efe260f6e9808ea23ed280c46154f9ad6fb3810 +size 128749 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa2de6e6c0ea77e16dfb2794fa1df70936e098c2 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d0f54e4352c143b9a61a7cadd90a64b8087d9ddb0575690804ccdd5a2cdb567 +size 96255 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c84b89ec03fe0607b987482d30c90425474e840 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5262e3ce90642b17682bc8b00b61db3309f4f37011bfeb03e8188185e5b6e07 +size 67460 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cac3ffbec4cc58a6e3f03d9453f6f177657a9cb4 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e4766bb636c5d8a2528fc0799b85f443a04865c92ec78e7fb505fc89f3f6285 +size 100305 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37501261d78dc416be697543934c0a530fbd30f2 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aad268ea43d899c60162f8d2021180cb952b1fbcd4138ee96c511921d3fd0b4 +size 43796 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cb6a5fb4379f35386ecdf7688ab4623dc7aecb9 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67950caf532e585a6f44e937d7e18cc129e168d06a2eca46d8b4c223642c1486 +size 59674 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93b63d8ed422613fc63ec9c6e1ca55d1313d538d --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9562b2f3cc4e83d420ce8d41cf2251c3a42fee78f80f975b779876c09c0bbfd9 +size 77753 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bc7ae5c47f55e2e87de4deb973a2f5861e5f5d6 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d97398ac8e8db9fda478b2a4be33bed5015af4a67747dd1b586960a6f1498da +size 59340 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..328f16d2e34a0dd1136e07f08c554723886c9c28 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c6d3e29bd84e84fc6a9236d675a39cf4fc898091b9d901ccc2161075566b194 +size 97626 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e3d7f7ea4cb86e0c0c3a42b186313e90527fe53 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdd99030021091a5265fa8eed59f2aceecb880895ab824055ce5dceff4ce1771 +size 125927 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..227930ec5176d5b8e810fc3162a920eee7b54f6e --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a216ae8d7da5482a4ec783cdf71f54199b073ac3f94305f5c41ab0e2fdc2f2d8 +size 119983 diff --git a/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd4a2d3c7baeb6542214355e92d3f40200425716 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cb7ce8274d5c89ec4d8b2237a2c6be2e658138b9de3e45cdd382b72ab77aa41 +size 36672 diff --git a/marked/Q/T-REC-Q.2965.2B-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2965.2B-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/Q/T-REC-Q.2965.2B-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.2971F-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2971F-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.2971F-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.2981-199912-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e45ad0ea737b2b1762cd961e798ec9133883b728 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c7e6ac1d28aa03a6de5917e6bc4ec2645efae8d09378091cd04a69223dbe5c2 +size 35169 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f657e2b293fc59e77a287e4aa30df5c630c38c81 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0f3983234170b314731ca5d73c85dfd0ccd98806e0ba9158b3527f464620310 +size 19499 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdf4d5a1d2c245295affd9328dce101e8864e7e4 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23b066fb689c48e4e45e3c86525847956098d3086072263c731a9794f2349ac9 +size 75581 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f81b469fe8481a824ee29422a6881a34bc8e019 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ca9160864b629364010a47eb7faa5d884a0154245c796fe6f6b0b84ddd64d81 +size 65006 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d8469b0460431ed1323f3d9641d122e98ac1810 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da8391c0c7411cbd77ea2315b663d690989185dfeaba5d345555ab47cfda0362 +size 21096 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccd164d30c1aa16de73b90ea4bc8f838cc005e96 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51a282bdd1704a80374f6a318d8a9c858d49603b7c5d85c7138f3277fa5955ba +size 78684 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc5c653033eae4ad281c327e8af4574f3dd5312 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a10febfd8f1e8bf419855cd4cab5cb51eab7ae2ef9768e19e3c9e2322edad46 +size 8325 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc05715668d78813339fc140f0b78c4a1924750 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912225ae5c169bde3157b0b6bd6d5bf9c7f8de4b70e3a571e021e8583f44b686 +size 32510 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6641d8fbfc5068ffc0f4dc429364e7b610b09503 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcd696a178fe9a95e0aa10567d59085d26c690681209f195fa2ad2c7c40f7190 +size 60533 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd9ec445f27eebc57b9623c24ecf37ed2a93084 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1522b1e43ff00d12ec05ad9cd38aadfbfa7f6e3e309b68b08613777f4778cf99 +size 127119 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82b04386e02e334e57d38d0abda20c501c0f4502 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a344e1b4d170610d63dea4e2d5211b26fd9f91d78a40391b9d669182cf5c33e7 +size 19471 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49151aa21cf7e23d9b92767180f08189088f0dee --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:197c1f02f3256aa42650fa7fb0037a0ebb11eda414176ffc3c964e8fb8f47cc1 +size 66496 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93f36259f5498ce9c972228dead318981e4f37a2 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1cb1832cc98a2d39a9e2d4d823ffd2a863f6c4803739e6220647b3d4d9c7f35 +size 58989 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f0f9cc9cc307f8dcc5f178c128a5a25621eb31d --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bb5b7f515f1cb4166007fb38fe5d201e2e2f15127e3a2b270546193d1ab98dd +size 104941 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70faeadeb3e6d1e697ddb42f741ab004166c8181 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb209d11bfe7c8eb8052a69158da2b9ebf13f7743206cea502afd7e18e5bf86e +size 32898 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10611f1f62b308fcb0d12d74f7383828244fb22a --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0cdacf460a3333d67a2ba7546121ba9a060c411b2593883bf7566f0583f344 +size 35739 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..981b28cb2d72951a8844aba6235fdf7104977838 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36679033a8b11f5c8677b069ec5b45072df8932964ba9e4da1af81c8fdb569bb +size 73795 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbf4f90ffbadd0dda12486a0c047103a4d3de079 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebd40f0ed886dd738954d4ddc57e1fbd10a7b5847f8b68445a20bff79f229d9d +size 22065 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8327d7cbe4b6dfb710fe2abf320cde7837a5e609 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd75f020e3fd5e167ee16eb12a8e8bf13456b76201444d1b3b0e508ef1e5e43d +size 21545 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/935075de5250cfe8aa0fb9d65d63dde5_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/935075de5250cfe8aa0fb9d65d63dde5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0fc82ea849455320ed4f61ee68236af7bcba9b4 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/935075de5250cfe8aa0fb9d65d63dde5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:215c53c4842749d979f56d94dacc3f0ba152068a53dec559ec7d041c14b1a904 +size 74851 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05cfb42d06f93ba132f1be381bdfd34ad82e1718 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9eb9f3b140289c94cbd1ce8a82b53f43d2e6cc59112bf5f193a6b691d53b7e34 +size 95300 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac3bf9b3351dfaea40a5a082fd08cd7a9fe45238 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22084bc3780bec663a4a5e956defb20118bac9ead4a9f4d453f6777a0a446385 +size 26025 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ce40f268880478c98adf8420fae13bbc5eddeda --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a5b52ab3abad094d576ee8ef8485bc1609de910b73b7bd2a741165cac754369 +size 34033 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..299a85810c9ba1b14b3b4a60accf24bb00abd709 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b82fe0af4aa0d1a2ffd3afbd4ab6f8417c37b5d4947d433a0350a110461968f7 +size 13248 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a5790868ac51b198657cd989bdad0c71c72f2f9 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d12c0b329199e93ade2c5a4f022177f02ede13bbeae6f410877e55be1b59c934 +size 65100 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc72a530289e1fb6c9688a960f09625ba4b690bb --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7c37e70b4f47192f50f62545ec461a6a4362d79b41384549d1345ea3e86f79a +size 41021 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d41b98fd8dff1e1999a0c98fa1fe582ea8caeb --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a931da20a220396b1c160c281c5919510d4ea0d681e023cb175d490e95e4a894 +size 46977 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66d472b9c2214e41532a39df63334df0adadc93a --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a00e3a156cf38b27bca4fed13de857f40d839cf42f9fd3bcaa88884e41253034 +size 47790 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..632069f568a7e074ff590cfd3efc1aa6118f41e5 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79a5fc2be4e52d3eed9c25377a8b0e6e4a00ed59e39c755dccc7f2634f1ac346 +size 30893 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fc35540ac43d0c841444b43aa70df942da409f1 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93962a87a8fed54fdbbb164543fb9770c75221ef417fc69dd6884498051969f4 +size 28211 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87a1e38640269cc45ebdf47c8da04ea1c0d69966 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e745c9d1b0c3e04b908304e9f74901b39e32c2d33e01e7387c3cbc3e071fa8bb +size 78759 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed004933661894743c892249e6467c4283c7f7a4 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50de36903734ba56127d3fa5320c0f6b6c2a3ebb0ae62b9cdd03fb72b41d90fc +size 37055 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c53adb7cac91cd2e3efd15ba43befd3a02f1a9c7 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d10d41fd583d6ee68017c249ca40fab095c50d68676496d90aaa03d0f8eb80ee +size 161452 diff --git a/marked/Q/T-REC-Q.2981-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4457f5bb10508c282fb355a3c1f833af5ebcfc54 --- /dev/null +++ b/marked/Q/T-REC-Q.2981-199912-I_PDF-E/raw.md @@ -0,0 +1,2707 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.2981** + +(12/1999) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Broadband integrated services digital network +(B-ISDN) and broadband private integrated +services network (B-PISN) – Call control +protocol** + +ITU-T Recommendation Q.2981 + +(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 ITU-T List of Recommendations. + +## **BROADBAND INTEGRATED SERVICES DIGITAL NETWORK (B-ISDN) AND BROADBAND PRIVATE INTEGRATED SERVICES NETWORK (B-PISN) – CALL CONTROL PROTOCOL** + +## **Summary** + +This Recommendation specifies a signalling protocol for the purpose of call control at the $Q_B$ , $S_B$ , $T_B$ , and co-incident $S_B/T_B$ reference points within, between, and at the access to Broadband Private Integrated Services Networks and within, between, and at the access to Broadband Integrated Services Digital Networks. The protocol operates between two adjacent call control entities. The protocol is applicable to a terminal or network node in a separated call and bearer (connection) control environment for the support of calls having none, a single bearer or multiple bearers. The protocol is applicable to a two-party call. The protocol also provides forward compatibility to the extent that an implementation can also operate within a multi-party call with other implementations that use additional capabilities, provided the implementation is deployed where it does not need to be aware of more than two parties. + +## **Source** + +ITU-T Recommendation Q.2981 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution 1 procedure on 3 December 1999. + +## **Keywords** + +Bearer control, call control, separation. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|-----------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Basic model..... | 3 | +| 5.1 | Separation of call control and bearer control ..... | 3 | +| 5.2 | Point-to-point and multi-party call control ..... | 3 | +| 5.3 | Call control architecture..... | 4 | +| 5.4 | Relationship to bearer control architecture ..... | 5 | +| 5.5 | Screening function ..... | 5 | +| 6 | Operational requirements..... | 7 | +| 6.1 | Provision and withdrawal ..... | 7 | +| 6.2 | Transport mechanism..... | 7 | +| 7 | Primitive definitions and state definitions ..... | 7 | +| 7.1 | Service primitives ..... | 7 | +| 7.1.1 | Service primitive architecture..... | 7 | +| 7.1.2 | ESTABLISH-CALL ..... | 8 | +| 7.1.3 | COMPLETE-CALL..... | 8 | +| 7.1.4 | STATUS-CALL ..... | 9 | +| 7.1.5 | RELEASE-CALL ..... | 9 | +| 7.1.6 | PROCEED-CALL ..... | 10 | +| 7.1.7 | ERROR..... | 10 | +| 7.2 | Parameters..... | 11 | +| 7.2.1 | Call segment ID ..... | 11 | +| 7.2.2 | Call description..... | 11 | +| 7.2.3 | Call changed parameter ..... | 11 | +| 7.2.4 | Await complete indicator..... | 11 | +| 7.2.5 | Bearer establishment address..... | 11 | +| 7.2.6 | Release cause ..... | 11 | +| 7.2.7 | Result ..... | 12 | +| 7.2.8 | Diagnostics ..... | 12 | +| 7.3 | Call control states..... | 12 | +| 7.3.1 | Call Idle ..... | 12 | +| 7.3.2 | Call Initiated ..... | 12 | +| 7.3.3 | Outgoing Call Proceeding..... | 12 | + +| | Page | +|-------------------------------------------------------------------------------|-------------| +| 7.3.4 Call Ready ..... | 12 | +| 7.3.5 Call Present..... | 12 | +| 7.3.6 Incoming Call Proceeding ..... | 12 | +| 7.3.7 Await Call Completion..... | 12 | +| 7.3.8 Call Active..... | 12 | +| 7.3.9 Call Release Request ..... | 12 | +| 7.3.10 Call Release Indication ..... | 13 | +| 8 Coding requirements..... | 13 | +| 8.1 Abstract definition of the call control operations ..... | 13 | +| 8.2 Definition of Call Control Object Super Class ..... | 18 | +| 8.3 Definitions of Call Control Object Classes in the Information Model ..... | 18 | +| 9 Procedures..... | 21 | +| 9.1 Call establishment request ..... | 21 | +| 9.1.1 Preceding CC entity..... | 21 | +| 9.1.2 Succeeding CC entity ..... | 21 | +| 9.2 Call Proceeding..... | 21 | +| 9.2.1 Preceding CC entity..... | 21 | +| 9.2.2 Succeeding CC entity ..... | 22 | +| 9.3 Call accepted..... | 22 | +| 9.3.1 Preceding CC entity..... | 22 | +| 9.3.2 Succeeding CC entity ..... | 22 | +| 9.4 Completion of call establishment ..... | 23 | +| 9.4.1 Preceding CC entity..... | 23 | +| 9.4.2 Succeeding CC entity ..... | 23 | +| 9.5 Call status change report..... | 23 | +| 9.5.1 General..... | 23 | +| 9.5.2 Initiating CC entity ..... | 23 | +| 9.5.3 Receiving CC entity..... | 24 | +| 9.6 Call establishment failure ..... | 24 | +| 9.6.1 Preceding CC entity..... | 24 | +| 9.6.2 Succeeding CC entity ..... | 24 | +| 9.7 Call clearing..... | 25 | +| 9.7.1 Procedures at the CC entity that initiates call clearing ..... | 25 | +| 9.7.2 Procedures at the CC entity that responds to clearing ..... | 25 | +| 9.7.3 Call clearing collision..... | 26 | +| 9.8 Exceptional procedures..... | 26 | +| 9.8.1 Timer expiry ..... | 26 | +| 9.8.2 Receipt of APDUs with unknown Call Segment Id ..... | 26 | + +| | Page | +|----------------------------------------------------------------------------------------------------------|-------------| +| 9.8.3 Receipt of APDUs with duplicated Call Segment Id..... | 26 | +| 9.8.4 Receipt of APDUs out of sequence ..... | 26 | +| 9.8.5 Receipt of reject APDUs ..... | 27 | +| 9.8.6 Handling of unrecognized parameters within CC-Operations..... | 28 | +| 10 Parameter values (Timers) ..... | 28 | +| 11 Transport mechanism..... | 29 | +| 12 SDL Diagrams ..... | 29 | +| 12.1 Outgoing CC-ASE ..... | 32 | +| 12.2 Incoming CC-ASE..... | 38 | +| Annex A – Bearer coordination requirements for CC signalling service users ..... | 47 | +| A.1 Requirements at a CC entity that establishes a bearer towards an adjacent CC entity ..... | 47 | +| A.2 Requirements at a CC entity that receives a bearer establishment from an adjacent CC entity ..... | 48 | +| A.3 Additional requirements at a transit CC ..... | 49 | +| A.4 Requirement on call clearing ..... | 49 | +| Annex B – Call description handling requirements for CC signalling service users..... | 49 | +| B.1 Call description handling at a CC signalling service user within an originating CC entity ..... | 49 | +| B.2 Call description handling at a CC signalling service user within a transit CC entity . | 50 | +| B.3 Call description handling at a CC signalling service user within a terminating CC entity ..... | 50 | +| B.4 Call description errors..... | 50 | +| B.5 End-to-end relevant object handling at a CC signalling service user within a transit CC entity ..... | 51 | +| B.6 Changes to the Information Model ..... | 51 | +| B.6.1 Deletion of a Service Component Object ..... | 51 | +| B.6.2 Addition of a Service Component Object..... | 52 | +| B.6.3 Changes to the attributes of the Party Object ..... | 52 | +| B.6.4 Changes to the Open Call attribute of the Call Object ..... | 52 | +| Annex C – Interworking ..... | 54 | +| C.1 Interworking with networks not supporting separation of Call Control and Bearer Control ..... | 54 | +| C.1.1 Outgoing call establishment ..... | 54 | +| C.1.2 Incoming bearer establishment ..... | 54 | +| C.1.3 Addition of bearers to an existing call..... | 54 | +| C.2 Interworking with simultaneous call and bearer establishment ..... | 54 | + +| | Page | +|------------------------------------------------------------------------|-------------| +| C.2.1 Outgoing call establishment ..... | 54 | +| C.2.2 Incoming call and bearer establishment..... | 55 | +| C.2.3 Addition of bearers to an existing call..... | 55 | +| Annex D – Transport mechanisms..... | 55 | +| D.1 Connection oriented-Bearer independent..... | 55 | +| D.2 Connectionless-Bearer independent..... | 55 | +| Appendix I – Information flow diagrams..... | 56 | +| I.1 Call Establishment using a two-message sequence ..... | 57 | +| I.2 Call Establishment using a three-message sequence ..... | 58 | +| I.3 Call Release ..... | 59 | +| Appendix II – Imported ASN.1 definitions..... | 59 | +| Appendix III – Object identifiers defined in this Recommendation ..... | 61 | + +## **BROADBAND INTEGRATED SERVICES DIGITAL NETWORK (B-ISDN) AND BROADBAND PRIVATE INTEGRATED SERVICES NETWORK (B-PISN) – CALL CONTROL PROTOCOL** + +*(Geneva, 1999)* + +# **1 Scope** + +This Recommendation specifies a signalling protocol for the purpose of call control at the QB, SB, TB, and co-incident SB/TB reference points within, between, and at the access to Broadband Private Integrated Services Networks and within, between, and at the access to Broadband Integrated Services Digital Networks. The protocol operates between two adjacent call control entities. The protocol is applicable to a terminal or network node in a separated call and bearer (connection) control environment for the support of calls having none, a single bearer or multiple bearers. The protocol is applicable to a two-party call. The protocol also provides forward compatibility to the extent that an implementation can also operate within a multi-party call with other implementations that use additional capabilities, provided the implementation is deployed where it does not need to be aware of more than two parties. + +This Recommendation is related to other Recommendations in this series which will describe the architecture of a separated call and bearer control environment and scenarios in which such an architecture can be applied. + +The protocol specified in this Recommendation is independent of the supporting transport service. + +The protocol specified in this Recommendation is independent of the protocol used for bearer establishment. + +# **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 X.680 (1997) | ISO/IEC 8824-1:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation.* +- [2] ITU-T Recommendation X.681 (1997) | ISO/IEC 8824-2:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Information object specification.* +- [3] ITU-T Recommendation X.682 (1997) | ISO/IEC 8824-3:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Constraint specification.* +- [4] ITU-T Recommendation X.683 (1997) | ISO/IEC 8824-4:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications.* +- [5] ITU-T Recommendation X.690 (1997) | ISO/IEC 8825-1:1998, *Information technology – ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER).* + +- [6] ITU-T Recommendation X.880 (1994) | ISO/IEC 13712:1995, *Information technology – Remote operations: Concepts, model and notation.* +- [7] ITU-T Recommendation Z.100 (1993), *CCITT specification and description language.* +- [8] ITU-T Recommendation Q.2932.1 (1996), *Digital subscriber signalling system No. 2 – Generic functional protocol: Core functions.* +- [9] ITU-T Recommendation Q.932 (1998), *Digital subscriber signalling system No. 1 – Generic procedures for the control of ISDN supplementary services.* + +# 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 **call:** An association between two or more users using a telecommunication service to communicate through one or more networks. +- 3.2 **call segment:** A part of a call located between two adjacent call control entities. +- 3.3 **call control:** Functionality and signalling in and between networks and terminals to effect the control of a call, excluding the control of individual bearers. +- 3.4 **call control entity (CC entity):** An entity that is located in a terminal or a network and that participates in call control. +- 3.5 **bearer control:** Functionality and signalling in and between networks and terminals to effect the control of a bearer, that bearer being part of a call. +- 3.6 **bearer control entity (BC entity):** An entity that is located in a terminal or a network and that participates in bearer control. +- 3.7 **bearer:** A connection for the transport of user plane information between users involved in a call. +- 3.8 **adjacent call control entities (adjacent CC entities):** Within the context of a single call, two CC entities that signal directly to each other with no intervening CC entity. +- 3.9 **preceding CC entity:** The CC entity that initiates call establishment across a given call segment. +- 3.10 **succeeding CC entity:** The CC entity at the opposite end of a call segment from the preceding CC entity. +- 3.11 **originating CC entity:** The CC entity that initiates call establishment and is located in a terminal or equipment that functions like a terminal (e.g. a server in the network). +- 3.12 **terminating CC entity:** The CC entity to which call establishment is directed and that is located in a terminal or equipment that functions like a terminal. +- 3.13 **transit CC entity:** A CC entity through which a call passes, excluding the originating and terminating CC entity. +- 3.14 **call control signalling service provider:** An entity which provides the signalling services of call control. +- 3.15 **call control signalling service user:** An entity within the CC entity to which the signalling services of call control are provided. + +NOTE – The call control signalling service user performs the Call Description handling, provides the interactions with bearer control, and in a network node, coordinates the incoming and outgoing side of the CC entity (Figure 6). + +**3.16 information model:** A representation of the service and abstract communications configuration using an object oriented technique. + +**3.17 party:** An addressable signalling endpoint. + +**3.18 calling party:** The party which initiates the call establishment. + +**3.19 called party:** Any party in a call other than the calling party. + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +APDU Application Protocol Data Unit + +ASN.1 Abstract Syntax Notation One + +B-ISDN Broadband Integrated Services Digital Network + +B-PISN Broadband Private Integrated Services Network + +BC Bearer Control + +CC Call Control + +M Mandatory + +O Optional + +PDU Protocol Data Unit + +ROSE Remote Operation Service Element + +# **5 Basic model** + +## **5.1 Separation of call control and bearer control** + +The protocol specified in this Recommendation is applicable to an environment in which the control of a call is separate from the control of the bearer or bearers that exist within the context of that call. + +In order for two users to communicate using a telecommunication service, an association, or call, is established between the two users. Within the context of the call, one or more bearers can be established for transporting user plane information between the users. However, bearers are not normally established until the call has been accepted by the called terminal, and therefore resources required by bearers are not occupied unnecessarily if the call cannot be established, e.g. if the called terminal is unable to accept the call because resources are not available. During the lifetime of the call, bearers can be added or cleared down as required. The call is terminated by one of the two users when there is no further need for communication. Termination of the call implies that all bearers (if any) are cleared down. + +Although for some telecommunication services a single bearer is sufficient, other telecommunication services benefit from the use of multiple bearers, each tailored to suit the characteristics of the user plane information to be transported. This is particularly true for multimedia applications involving audio, video and data. The call provides a context in which the various bearers can exist and a means of binding the bearers together. + +## **5.2 Point-to-point and multi-party call control** + +In a point-to-point configuration the protocol specified in this Recommendation operates between any two adjacent call control entities between the calling party and the called party. + +In a multi-party configuration the protocol specified in this Recommendation operates between any two adjacent call control entities on the point-to-point leg between a coordination point in the network and a called party. In this case, a network node in the calling party's network takes responsibility for coordinating the responses from multiple point-to-point signalling associations to the called parties into one signalling association to the calling party. Enhancements to be made to the Call Control protocol in order to make it suitable also for this signalling association to the calling party in case of a multi-party call are outside the scope of this Recommendation. + +Figure 1 shows an example configuration for a multi-party call with two called parties involved. + +![Diagram of a multi-party call configuration with two called parties.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +The diagram illustrates a multi-party call configuration. On the left, a circle labeled 'Calling party' is connected to a larger circle labeled 'Calling party's network'. Below this network circle, an arrow points to it from the text 'Call Coordination point'. From the 'Calling party's network' circle, two lines branch out to the right. The top line connects to a circle labeled 'Called party's network', which is then connected to a circle labeled 'Called party'. The bottom line connects to another circle labeled 'Called party's network', which is connected to another circle labeled 'Called party'. In the bottom right corner, the text 'T111102660-99' is present. + +Diagram of a multi-party call configuration with two called parties. + +**Figure 1/Q.2981 – Multi-party call with two called parties** + +## 5.3 Call control architecture + +Call control provides the means of establishing, maintaining and clearing down a call, including the operation of any supplementary services that relate to the call rather than to individual bearers. Control of a call is effected by means of a number of call control entities (CC entities) located in the users' terminals and in various network nodes. Whereas bearer control involves a bearer control entity (BC entity) at each network node through which a bearer passes, call control requires a CC entity only at those network nodes that provide call-related functionality, e.g. the nodes serving the terminals concerned or nodes that, in the context of the call, provide interworking between networks. In particular, CC entities are not required at nodes that would only provide transit functionality. The precise criteria for determining whether a network node needs to provide CC functionality for a given call are outside the scope of this Recommendation. + +The various CC entities involved in a given call are linked in series by signalling associations. These CC entities and signalling associations are created during call establishment and cleared down when the call is cleared down. The protocol specified in this Recommendation provides such an association between adjacent CC entities and conveys call-related signalling information between those CC entities. That part of a call between two CC entities that communicate directly via a single signalling association is known as a call segment. This is illustrated in Figure 2 for a call that involves four CC entities (e.g. one at each terminal and one at each node serving those terminals) and consequently three call segments. + +![Figure 2/Q.2981 – Call Control involving four CC entities (three call segments). The diagram shows four boxes labeled 'CC' connected in a horizontal line by three double-headed arrows. Each arrow is labeled 'Call segment'. Below the fourth 'CC' box is the text 'T11102670-99'.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 2/Q.2981 – Call Control involving four CC entities (three call segments). The diagram shows four boxes labeled 'CC' connected in a horizontal line by three double-headed arrows. Each arrow is labeled 'Call segment'. Below the fourth 'CC' box is the text 'T11102670-99'. + +**Figure 2/Q.2981 – Call Control involving four CC entities (three call segments)** + +## 5.4 Relationship to bearer control architecture + +Bearer control requires functionality, and hence a BC entity, at each terminal and at every network node through which the bearer is routed. This is in contrast to call control, which involves a CC entity only at the terminals and selected network nodes. Each bearer can be routed independently of other bearers and independently of the routing of call control signalling associations. However, each bearer is required to be routed through each network node at which there is a CC entity, and hence have a BC entity at each of these nodes, so that the CC entity can manage the bearer if required. This is illustrated in Figure 3 for the same call as in Figure 2 and a single bearer that has a BC entity collocated with each CC entity and an additional BC entity (e.g. at a transit node) located between the second and third CC entities. + +![Figure 3/Q.2981 – Relationship of call control and bearer control architecture. The diagram shows a sequence of nodes: Terminal, Edge Switch, Transit Switch, Edge Switch, and Terminal. Each node contains a box with 'CC' and 'BC' entities, except for the Transit Switch which only contains a 'BC' entity. The nodes are connected by lines labeled 'Call segment'. Below the last 'Terminal' box is the text 'T11102680-99'.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Figure 3/Q.2981 – Relationship of call control and bearer control architecture. The diagram shows a sequence of nodes: Terminal, Edge Switch, Transit Switch, Edge Switch, and Terminal. Each node contains a box with 'CC' and 'BC' entities, except for the Transit Switch which only contains a 'BC' entity. The nodes are connected by lines labeled 'Call segment'. Below the last 'Terminal' box is the text 'T11102680-99'. + +**Figure 3/Q.2981 – Relationship of call control and bearer control architecture** + +NOTE – Signalling between BC entities is outside the scope of this Recommendation. + +## 5.5 Screening function + +The model for call and bearer control functional entities (Figure 3) shows all call control (CC) entities existing at the same location as bearer control (BC) entities. While bearer control can exist independently of call control, the opposite does not apply. Each CC entity includes bearer coordination capabilities. + +Although at network boundaries, CC entities will normally be present, network boundaries can also be crossed without provision of a CC entity and the connections associated with those calls can be routed differently from each other and from the call, thereby crossing network boundaries at different locations or even being routed through different networks. + +Where a call crosses a network boundary, a number of functions will need to be performed within call control that do not require the presence of a connection. These include: + +- Service control. Control of the provision of basic and supplementary services, and subscription arrangements. Identification of correct service profile. +- Translation of numbering plans where the two networks use different numbering plans (e.g. public to private). Even where the same numbering plan is used, the addition of the country code may be necessary. +- Provision of some supplementary services that provide security control on a network basis, e.g. closed user group. + +- d) Support of supplementary services related to numbering (e.g. DDI, MSN) and restriction of numbers (CLIR, COLR). + +The functions listed above are outside the scope of this Recommendation. + +![Diagram of a call originating and terminating in different networks (Figure 4/Q.2981).](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +The diagram illustrates a call path between a 'Calling user' and a 'Called user' across two networks, 'Network 1' and 'Network 2'. +At the 'Calling user' end, a 'CC' (Call Control) entity is connected to a 'TE' (Terminal Equipment). This 'CC' is linked via a dashed line (call segment) to another 'CC' at node 'A' inside 'Network 1'. +'Network 1' contains several nodes, with 'A' being the ingress point and 'B' being the egress point. A thick solid line (physical link on path of call) connects node 'A' to node 'B'. +At node 'B', the call segment (dashed line) continues to a 'CC' at node 'C' inside 'Network 2'. +'Network 2' also contains several nodes, with 'C' as the ingress point and 'D' as the egress point. A thick solid line connects node 'C' to node 'D'. +At node 'D', the call segment (dashed line) connects to a 'CC' which is then connected to the 'Called user' via its 'TE'. +A legend at the bottom left defines the line types: + +- Physical link +- Physical link on path of call +- Call segment +- Allocation of CC to physical TE or network node + +The identifier 'T11102690-99' is located in the bottom right corner of the diagram area. + +Diagram of a call originating and terminating in different networks (Figure 4/Q.2981). + +**Figure 4/Q.2981 – Call originating and terminating in different networks** + +Figure 4 shows an example of a call originating and terminating in different networks. If calling line identification restriction (CLIR) applies to the call, this information will be known at the CC at node A, which can add a presentation restricted indicator to the calling party number forwarded on across the next call segment. Normally, on exit from one network to another, a calling party number with an associated presentation restricted indicator is not forwarded, but instead just the presentation restricted indicator is forwarded. The absence of a CC at node B (point of egress to network 2) means that there will be no opportunity to filter out the calling party number until the CC at node D is reached. This is clearly insecure. + +Possible alternatives are: + +- 1) Ensure that there is a CC at node B (and similarly at node C to handle this type of situation in the reverse direction). However, CCs are points of bearer coordination, and the presence of CCs at nodes B and C would force all bearers to go via nodes B and C. This would deny the possibility of using other routes between the two networks. For some bearers, the route via nodes B and C might not be the cheapest, or may be congested, or may not provide the desired quality of service. It is desirable to minimize the number of CCs in order to provide maximum flexibility for routing bearers. +- 2) Ensure that the CC at node A performs the filtering. However, this requires node A to have knowledge that the call segment leads to another network. This knowledge may not always be available. + +To solve the problem without introducing the disadvantages of alternatives 1 and 2, filtering (screening) functionality may be provided at node B (and node C). A functional entity (screening function) may optionally appear between call control entities, and is located as necessary at incoming and outgoing gateways between networks. Figure 5 shows an example. + +The screening functional entity has no impact on the information flows, except that this functional entity may impose itself as a transit point on an existing flow. + +![Diagram showing screening functional entities at network boundaries between User 1, Network 1, and Network 2, leading to User 2. The diagram illustrates two parallel paths: a top path with CC (Call Control) entities and a bottom path with BC (Bearer Control) entities. Network 1 contains two CC and four BC entities. Network 2 contains one CC and one BC entity. Screening functions are located at the boundaries between Network 1 and Network 2. A dashed line indicates a break in the sequence of BC entities between the two networks. The identifier T11102700-99 is shown in the bottom right corner.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Diagram showing screening functional entities at network boundaries between User 1, Network 1, and Network 2, leading to User 2. The diagram illustrates two parallel paths: a top path with CC (Call Control) entities and a bottom path with BC (Bearer Control) entities. Network 1 contains two CC and four BC entities. Network 2 contains one CC and one BC entity. Screening functions are located at the boundaries between Network 1 and Network 2. A dashed line indicates a break in the sequence of BC entities between the two networks. The identifier T11102700-99 is shown in the bottom right corner. + +**Figure 5/Q.2981 – Screening functional entities at network boundaries** + +# 6 Operational requirements + +## 6.1 Provision and withdrawal + +The provision of this capability within a network is a network provider option. + +The provision of this capability between networks or between a network and a user is by bilateral agreement. + +## 6.2 Transport mechanism + +The choice of the underlying transport mechanism within a network is a network provider option. + +The choice of the transport mechanism between networks or between a network and a user is by bilateral agreement. + +# 7 Primitive definitions and state definitions + +## 7.1 Service primitives + +### 7.1.1 Service primitive architecture + +The following services for call establishment and release are defined: + +| | | +|----------------|-------------| +| ESTABLISH-CALL | confirmed | +| RELEASE-CALL | confirmed | +| COMPLETE-CALL | unconfirmed | +| STATUS-CALL | unconfirmed | +| PROCEED-CALL | unconfirmed | +| ERROR | indication | + +Figure 6 shows the architecture which is assumed for two concatenated call segments. + +![Figure 6/Q.2981 – Architecture diagram showing three CC signalling service users connected to two CC signalling service providers via CC interfaces.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The diagram illustrates the architecture of the CC signalling service. It features three 'CC signalling service user' blocks at the top, each connected to a 'CC signalling service provider' block below it via a 'CC' interface. The first user connects to the first provider, the second user connects to the second provider, and the third user also connects to the second provider. The two providers are interconnected by a horizontal line. + +Figure 6/Q.2981 – Architecture diagram showing three CC signalling service users connected to two CC signalling service providers via CC interfaces. + +T11102710-99 + +**Figure 6/Q.2981 – Architecture** + +### 7.1.2 ESTABLISH-CALL + +This service is used by the call control signalling service user to establish a call and its information model. It is a confirmed service. See Figure 7. Table 1 shows the parameters of the ESTABLISH-CALL primitive. + +![Figure 7/Q.2981 – ESTABLISH-CALL service sequence diagram showing the interaction between a CC signalling service user, a CC signalling service provider, and another CC signalling service user.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +The sequence diagram shows the interaction for the ESTABLISH-CALL service. It starts with a 'CC signalling service user' on the left sending an 'ESTABLISH-CALL request' to a 'CC signalling service provider' in the middle. The provider then sends an 'ESTABLISH-CALL indication' to another 'CC signalling service user' on the right. The right user responds with an 'ESTABLISH-CALL response' back to the provider, which in turn sends an 'ESTABLISH-CALL confirm' back to the left user. Dashed lines indicate the logical flow of the service between the user and the provider. + +Figure 7/Q.2981 – ESTABLISH-CALL service sequence diagram showing the interaction between a CC signalling service user, a CC signalling service provider, and another CC signalling service user. + +T11102720-99 + +**Figure 7/Q.2981 – ESTABLISH-CALL service** + +**Table 1/Q.2981 – ESTABLISH-CALL parameters** + +| Parameter name | request | indication | response | confirmation | +|------------------------------|---------|------------|----------|--------------| +| Call segment ID | M | M | M | M | +| Bearer establishment address | M | M | O | O | +| Await complete indicator | M | M | – | – | +| Call description | M | M | O (Note) | O (Note) | +| Result | – | – | M | M | +| Diagnostics | – | – | M | M | + +NOTE – Mandatory if Result is positive, else optional. + +### 7.1.3 COMPLETE-CALL + +This service is used by the call control signalling service user to complete establishment of a call and its information model. It is an unconfirmed service. See Figure 8. Table 2 shows the parameters of the COMPLETE-CALL primitive. + +![Sequence diagram for COMPLETE-CALL service. A CC signalling service user sends a COMPLETE-CALL request to a CC signalling service provider, which then sends a COMPLETE-CALL indication to another CC signalling service user. Reference T11102730-99.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Sequence diagram for COMPLETE-CALL service: + +- CC signalling service user → CC signalling service provider: COMPLETE-CALL request +- CC signalling service provider → CC signalling service user: COMPLETE-CALL indication + +T11102730-99 + +Sequence diagram for COMPLETE-CALL service. A CC signalling service user sends a COMPLETE-CALL request to a CC signalling service provider, which then sends a COMPLETE-CALL indication to another CC signalling service user. Reference T11102730-99. + +**Figure 8/Q.2981 – COMPLETE-CALL service** + +**Table 2/Q.2981 – COMPLETE-CALL parameters** + +| Parameter name | request | indication | +|-----------------|---------|------------| +| Call segment ID | M | M | + +### 7.1.4 STATUS-CALL + +This service is used by the call control signalling service user to report a change to the information model. It is an unconfirmed service. See Figure 9. Table 3 shows the parameters of the STATUS-CALL primitive. + +![Sequence diagram for STATUS-CALL service. A CC signalling service user sends a STATUS-CALL request to a CC signalling service provider, which then sends a STATUS-CALL indication to another CC signalling service user. Reference T11102740-99.](21ad58fee90f2be50708ff541d225507_img.jpg) + +Sequence diagram for STATUS-CALL service: + +- CC signalling service user → CC signalling service provider: STATUS-CALL request +- CC signalling service provider → CC signalling service user: STATUS-CALL indication + +T11102740-99 + +Sequence diagram for STATUS-CALL service. A CC signalling service user sends a STATUS-CALL request to a CC signalling service provider, which then sends a STATUS-CALL indication to another CC signalling service user. Reference T11102740-99. + +**Figure 9/Q.2981 – STATUS-CALL service** + +**Table 3/Q.2981 – STATUS-CALL parameters** + +| Parameter name | request | indication | +|------------------------|---------|------------| +| Call segment ID | M | M | +| Call changed parameter | M | M | + +### 7.1.5 RELEASE-CALL + +This service is used by the call control signalling service user to release a call and its information model. It is a confirmed service. See Figure 10. Table 4 shows the parameters of the RELEASE-CALL primitive. + +![Sequence diagram for RELEASE-CALL service showing interactions between CC signalling service user, CC signalling service provider, and another CC signalling service user. The sequence starts with a RELEASE-CALL request from the first user to the provider. The provider then sends a RELEASE-CALL indication to the second user. The second user responds with a RELEASE-CALL response to the provider, which in turn sends a RELEASE-CALL confirm back to the first user. Reference code T111102750-99 is present.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Sequence diagram for RELEASE-CALL service showing interactions between CC signalling service user, CC signalling service provider, and another CC signalling service user. The sequence starts with a RELEASE-CALL request from the first user to the provider. The provider then sends a RELEASE-CALL indication to the second user. The second user responds with a RELEASE-CALL response to the provider, which in turn sends a RELEASE-CALL confirm back to the first user. Reference code T111102750-99 is present. + +**Figure 10/Q.2981 – RELEASE-CALL service** + +**Table 4/Q.2981 – RELEASE-CALL parameters** + +| Parameter name | request | indication | response | confirmation | +|-----------------|---------|------------|----------|--------------| +| Call segment ID | M | M | M | M | +| Release cause | M | M | – | – | + +### **7.1.6 PROCEED-CALL** + +This service is used by the call control signalling service user to indicate receipt of a call at the succeeding side of a call segment. It is an unconfirmed service. See Figure 11. Table 5 shows the parameters of the PROCEED-CALL primitive. + +![Sequence diagram for PROCEED-CALL service showing interactions between CC signalling service user, CC signalling service provider, and another CC signalling service user. The sequence starts with a PROCEED-CALL request from the first user to the provider. The provider then sends a PROCEED-CALL indication to the second user. Reference code T111102760-99 is present.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Sequence diagram for PROCEED-CALL service showing interactions between CC signalling service user, CC signalling service provider, and another CC signalling service user. The sequence starts with a PROCEED-CALL request from the first user to the provider. The provider then sends a PROCEED-CALL indication to the second user. Reference code T111102760-99 is present. + +**Figure 11/Q.2981 – PROCEED-CALL service** + +**Table 5/Q.2981 – PROCEED-CALL parameters** + +| Parameter name | request | indication | +|------------------------------|---------|------------| +| Call segment ID | M | M | +| Bearer establishment address | M | M | + +### **7.1.7 ERROR** + +This indication primitive is used by the call control signalling service provider to indicate the occurrence of an exceptional condition to the call control signalling service user. Table 6 shows the parameters of the ERROR indication primitive. + +**Table 6/Q.2981 – ERROR parameters** + +| Parameter name | indication | +|-----------------------|-------------------| +| Call segment ID | M | +| Diagnostics | M | + +## **7.2 Parameters** + +### **7.2.1 Call segment ID** + +A pair of values which together uniquely identify the call at the two adjacent CC entities bounding a call segment. + +### **7.2.2 Call description** + +The type CallDescription, as used in the operation callEstablish, contains an information model which describes the properties of a call. The information model comprises sequences of network relevant and end-to-end relevant object descriptions. An object description consists of: + +- an object reference, used to refer to particular instances of objects, which should therefore be unique within a particular call description; +- an object status, which is used for example to indicate whether the object is optional or mandatory; +- an identifier that identifies the class of object to which the instance belongs; and +- an argument of type specific to the class of object to which the instance belongs. + +A call control object class is a class of object that inherits the properties of the super class CALLCONTROL OBJECT. Each object class in this super class comprises an identifier and an optional argument. The type of the argument depends on the particular object class in the super class, as identified by the identifier. The argument defines the type of attributes of an object of this class. + +The OpenCall parameter indicates to the non-call owners in a communications configuration their rights to modify the configuration. The OpenCall parameter is an attribute of the call that is set by the user (call control signalling service user); it is stored in the information model and is transferred in the call description. The call control protocol provides the procedures for exchanging information in an orderly manner. The call status change report provides the mechanism for informing all call control signalling service users involved in the call of one or more changes in the call permissions. + +### **7.2.3 Call changed parameter** + +The type CallChangedParameter, as used in the operation callStatus, contains a list of those objects of the information model which have been modified and the modification of which has to be reported to the other call control signalling service users involved in the call. + +### **7.2.4 Await complete indicator** + +Has the value TRUE if call and information model establishment uses a three-message sequence or FALSE if call and information model establishment uses an two-message sequence. + +### **7.2.5 Bearer establishment address** + +The address of a network node/terminal to which bearer (connection) establishment shall be routed. + +### **7.2.6 Release cause** + +Reason for a call release request. + +### **7.2.7 Result** + +Positive/negative result for an ESTABLISH-CALL request or indication. + +### **7.2.8 Diagnostics** + +Further explanation of the result (e.g. error values) in an ESTABLISH-CALL response/confirm or the explanation of the exceptional condition that caused an ERROR indication. + +## **7.3 Call control states** + +This subclause describes the states which exist for a CC signalling service provider within a CC entity. + +### **7.3.1 Call Idle** + +No call exists. + +### **7.3.2 Call Initiated** + +This state exists at a preceding CC entity when a request for call establishment has been sent to the succeeding CC entity but no response has been received. + +### **7.3.3 Outgoing Call Proceeding** + +This state exists at a preceding call control entity when acknowledgement that the call is accepted for this call segment has been received from the succeeding call control entity. + +### **7.3.4 Call Ready** + +This state exists at a preceding call control entity when an indication has been received from the succeeding CC entity that it is ready to complete the establishment of the call and its information model. + +### **7.3.5 Call Present** + +This state exists at a succeeding call control entity that has not yet responded to the request for call establishment. + +### **7.3.6 Incoming Call Proceeding** + +This state exists at a succeeding call control entity that has sent to the preceding call control entity acknowledgement that the call is accepted for this call segment. + +### **7.3.7 Await Call Completion** + +This state exists at a succeeding call control entity that is awaiting an indication from the preceding CC entity that establishment of the call and its information model is to be completed. + +### **7.3.8 Call Active** + +This state exists at a preceding call control entity that has received an indication that the called user has answered from the succeeding call control entity. This state exists at a succeeding call control entity that has sent an indication that the called user has answered to the preceding call control entity. + +### **7.3.9 Call Release Request** + +This state exists when a call control entity has sent out a request for call release but a response has not yet been received. + +### 7.3.10 Call Release Indication + +This state exists when a call control entity has received a call release indication but the user has not yet answered. + +# 8 Coding requirements + +## 8.1 Abstract definition of the call control operations + +Table 7 shows the definition of the operations, errors and types required for the Call Control protocol using ASN.1 as defined in ITU-T Recommendations X.680, X.681, X.682 and X.683 and using the OPERATION and ERROR object classes as defined in ITU-T Recommendation X.880. + +APDUs based on these operations shall be of types invoke, returnResult, returnError and reject as defined in Table B.1/Q.2932.1. The Basic Encoding Rules (BER) as defined in ITU-T Recommendation X.690 shall be applied to the encoding of APDUs based on these operations and errors. + +**Table 7/Q.2981 – Definition of operations for the Call Control protocol** + +``` +CC-Operations {itu-t recommendation q 2981 cc-operations(1)} DEFINITIONS +AUTOMATIC TAGS ::= +BEGIN + +EXPORTS CcOperations, CallSegmentId; + +IMPORTS + OPERATION, ERROR + FROM Remote-Operations-Information-Objects {joint-iso-itu-t(2) + remote-operations(4) informationObjects(5) version1(0)} + PartyNumber + FROM Addressing-Data-Elements {itu-t recommendation q 932 + addressing-data-elements(7)} + -- The definition of PartyNumber is reproduced in Appendix II + CALLCONTROL OBJECT CLASS + FROM Call-Control-Object-Super-Class {itu-t recommendation q + 2981 call-control-object-super-class(4)} + -- The definition of CALLCONTROL OBJECT CLASS is given in subclause 8.2 + call, localPartyEP, remotePartyEP, directCallAssociation, + remoteCallAssociation, serviceComponent + FROM Call-Object-Class-Definitions {itu-t recommendation q 2981 + call-object-class-definitions(5)}; + +-- The definition of call, localPartyEP, remotePartyEP, directCallAssociation, +-- remoteCallAssociation, +-- serviceComponent is given in subclause 8.3 +CcOperations OPERATION ::= + {callEstablish | callProceeding | callComplete | callRelease | + callStatus} + +ccOperationsDefinitions OBJECT IDENTIFIER ::= + {itu-t recommendation q 2981 cc-operations-definitions(2)} + +-- The callEstablish operation is used to establish a call and its information +-- model. It is a confirmed operation. +callEstablish OPERATION ::= { + ARGUMENT + SEQUENCE {callSegmentId + callDescription + CallSegmentId, + CallDescription, +``` + +``` + + bearerEstablAddress BearerEstablishmentAddress, + awaitCompleteIndicator BOOLEAN, + parameterActionIndicator ParameterActionIndicator, + ...} + +RESULT + SEQUENCE {callSegmentId CallSegmentId, + callDescription CallDescription, + parameterActionIndicator ParameterActionIndicator, + bearerEstablAddress + BearerEstablishmentAddress OPTIONAL, + ...} + +ERRORS + {callDescriptionNotAccepted | unallocatedNumber | + noUserResponding | noAnswerFromUser | callRejected | + destinationOutOfOrder | addressIncomplete | networkOutOfOrder | + temporaryFailure | userBusy | userNotReachable | unspecified} +CODE + global:{ccOperationsDefinitions 1}} + +-- The callProceeding operation is used by the succeeding call control entity to +-- inform the preceding call control entity +-- that the call is in progress and connection establishment may start for this +-- segment. It is an unconfirmed operation. +callProceeding OPERATION ::= { + ARGUMENT + SEQUENCE {callSegmentId CallSegmentId, + bearerEstablAddress BearerEstablishmentAddress, + parameterActionIndicator ParameterActionIndicator, + ...} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE global:{ccOperationsDefinitions 2}} + +-- The callRelease operation is used to release an existing call and its +-- information model. It is a confirmed operation. +callRelease OPERATION ::= { + ARGUMENT + SEQUENCE {callSegmentId CallSegmentId, + releaseCause ReleaseCause, + parameterActionIndicator ParameterActionIndicator, + ...} + RESULT + SEQUENCE {callSegmentId CallSegmentId, + parameterActionIndicator ParameterActionIndicator, + ...} + CODE + global:{ccOperationsDefinitions 3}} + +-- The callComplete operation is used to indicate completion of establishment of +-- a call and its information model. +-- It is an unconfirmed operation. +callComplete OPERATION ::= { + ARGUMENT + SEQUENCE {callSegmentId CallSegmentId, + parameterActionIndicator ParameterActionIndicator, + ...} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE global:{ccOperationsDefinitions 4}} + +-- The callStatus operation is used to report a change to the information model. +-- It is an unconfirmed operation. +callStatus OPERATION ::= { + ARGUMENT + SEQUENCE {callSegmentId CallSegmentId, + callChangedParameter + +``` + +``` + + SEQUENCE OF CallChangedParameter, + parameterActionIndicator ParameterActionIndicator, + ...} + +RETURN RESULT FALSE +ALWAYS RESPONDS FALSE +CODE global:{ccOperationsDefinitions 5}} + +ParameterActionIndicator ::= ENUMERATED { + clearCallAndItsInformationModel(0), discardApduAndReject(1), + discardApduNoReject(2), + discardParameterAndPassApduToApplication(3), + ignoreParameterAndPassApduToApplication(4)} + +-- Used to indicate action to be taken if a parameter in an operation is not +-- recognized +BearerEstablishmentAddress ::= + PartyNumber + +NetworkRelevantObjectClassSet CALLCONTROL OBJECTCLASS ::= + {call | localPartyEP | remotePartyEP | directCallAssociation | + remoteCallAssociation, ...} + +EndToEndRelevantObjectClassSet CALLCONTROL OBJECTCLASS ::= + {serviceComponent, ...} + +CallDescription ::= SEQUENCE { + networkRelevantPart + SEQUENCE OF + NetworkRelevantObjectDescription{{NetworkRelevantObjectClassSet}}, + endToEndRelevantPart + SEQUENCE OF + EndToEndRelevantObjectDescription{{EndToEndRelevantObjectClassSet}} + OPTIONAL} + +NetworkRelevantObjectDescription{CALLCONTROL OBJECTCLASS:NetworkRelevantObjectClassSet} + ::= SEQUENCE { + objectReference INTEGER, + objectActionInd ObjectActionIndicator, + objectStatus ObjectStatus, + objectClassId + CALLCONTROL OBJECTCLASS.&objectClassIdentifier + ({NetworkRelevantObjectClassSet}), + objectArgument + CALLCONTROL OBJECTCLASS.&ArgumentType + ({NetworkRelevantObjectClassSet}{@objectClassId}) OPTIONAL, + ...} + +EndToEndRelevantObjectDescription{CALLCONTROL OBJECTCLASS:EndToEndRelevantObjectClassSet} + ::= SEQUENCE { + objectReference INTEGER, + objectActionInd ObjectActionIndicator, + objectStatus ObjectStatus, + objectClassId + CALLCONTROL OBJECTCLASS.&objectClassIdentifier + ({EndToEndRelevantObjectClassSet}), + objectArgument + CALLCONTROL OBJECTCLASS.&ArgumentType + ({EndToEndRelevantObjectClassSet}{@objectClassId}) OPTIONAL, + ...} + +CallChangedParameter ::= SEQUENCE { + modifiedNetworkRelevantPart + +``` + +``` + + SEQUENCE OF + ModifiedNetworkRelevantObjectDescription{{NetworkRelevantObjectClassSet}}, + modifiedEndToEndRelevantPart + SEQUENCE OF + ModifiedEndToEndRelevantObjectDescription{{EndToEndRelevantObjectClassSet}} + OPTIONAL} + +ModifiedNetworkRelevantObjectDescription{CALLCONTROL OBJECT CLASS:NetworkRelevantObjectClassSet} + ::= SEQUENCE { + operation + ENUMERATED {deleteObject(0), modifyAttributes(1), ... + }, + objectReference INTEGER, + objectActionInd ObjectActionIndicator, + modifiedArgument + CALLCONTROL OBJECT CLASS.&ArgumentType + ({NetworkRelevantObjectClassSet}) OPTIONAL} + +ModifiedEndToEndRelevantObjectDescription{CALLCONTROL OBJECT CLASS:EndToEndRelevantObjectClassSet} + ::= SEQUENCE { + operation + ENUMERATED {deleteObject(0), modifyAttributes(1), ... + }, + objectReference INTEGER, + objectActionInd ObjectActionIndicator, + modifiedArgument + CALLCONTROL OBJECT CLASS.&ArgumentType + ({EndToEndRelevantObjectClassSet}) OPTIONAL} + +ObjectActionIndicator ::= ENUMERATED { + clearCall(0), discardNotify(1), discardUnknown(2), + progressTransit(3), ... +} + +-- Used to indicate action to be taken if an object or object attribute is not +-- recognized +ObjectStatus ::= ENUMERATED { + mandatory(0), optional(1), conditional(2), ... +} + +CallSegmentId ::= SEQUENCE { + precedingSideCallSegId CallSegmentIdComponent, + succeedingSideCallSegId CallSegmentIdComponent} + +CallSegmentIdComponent ::= + INTEGER(-2147483648..2147483647) -- 4 octets + +-- The value 0 is to be used as a null value for the succeeding side call segment +-- identifier +-- in the callEstablish invoke APDU. +ReleaseCause ::= SEQUENCE { + causeValue CauseValue, + location Location, + ...} + +CauseValue ::= ENUMERATED { + callDescriptionNotAccepted(0), normalCallClearing(3), + temporaryFailure(11), recoveryOnTimerExpiry(12), unspecified(4), + ... +} + +``` + +``` + +Location ::= ENUMERATED { + unspecified(0), user(1), networkLocalCallSegment(2), + networkNonLocalCallSegment(3), ... +} + +ccOperationsErrors OBJECT IDENTIFIER ::= + {itu-t recommendation q 2981 cc-operations-errors(3)} + +callDescriptionNotAccepted ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + callDescription CallDescription OPTIONAL, + ...} + CODE + global:{ccOperationsErrors 1}} + +userBusy ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + callDescription CallDescription OPTIONAL, + ...} + CODE + global:{ccOperationsErrors 2}} + +unallocatedNumber ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE + global:{ccOperationsErrors 3}} + +noUserResponding ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE + global:{ccOperationsErrors 4}} + +noAnswerFromUser ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE + global:{ccOperationsErrors 5}} + +callRejected ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE + global:{ccOperationsErrors 6}} + +destinationOutOfOrder ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE + global:{ccOperationsErrors 7}} + +addressIncomplete ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} +} + +``` + +``` + +CODE global:{ccOperationsErrors 8}} + +networkOutOfOrder ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE global:{ccOperationsErrors 9}} + +temporaryFailure ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE global:{ccOperationsErrors 10}} + +userNotReachable ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE global:{ccOperationsErrors 11}} + +unspecified ERROR ::= { + PARAMETER + SEQUENCE {callSegmentId CallSegmentId, + location Location, + ...} + CODE global:{ccOperationsErrors 12}} + +END + +``` + +## 8.2 Definition of Call Control Object Super Class + +Table 8 shows the definition of the Call Control Object Super Class using ASN.1 as defined in ITU-T Recommendations X.680, X.681, X.682 and X.683. + +**Table 8/Q.2981 – Definition of Call Control Object Super Class** + +``` + +BEGIN + +EXPORTS CALLCONTROLOBJECTCLASS; + +CALLCONTROLOBJECTCLASS ::= CLASS { + &ArgumentType OPTIONAL, + &argumentTypeOptional BOOLEAN OPTIONAL, + &objectClassIdentifier OBJECT IDENTIFIER UNIQUE} +WITH SYNTAX { + [ARGUMENT &ArgumentType + [OPTIONAL &argumentTypeOptional]] + IDENTIFIER &objectClassIdentifier} + +END -- Call-Control-Object-Super-Class + +``` + +## 8.3 Definitions of Call Control Object Classes in the Information Model + +Call control object classes are inherited from the super class CALLCONTROLOBJECTCLASS, used for the purpose of object descriptions within the call description. For each object class, the ARGUMENT type and unique IDENTIFIER are defined. + +Table 9 shows the definition of the Call Control Object Classes in the information model using ASN.1 as defined in ITU-T Recommendations X.680, X.681, X.682 and X.683. + +###### Table 9/Q.2981 – Definition of Call Control Object Classes in the Information Model + +``` +BEGIN + +EXPORTS + call, localPartyEP, remotePartyEP, directCallAssociation, + remoteCallAssociation, serviceComponent, BearerId; + +IMPORTS + CALLCONTROL OBJECTCLASS + FROM Call-Control-Object-Super-Class {itu-t recommendation q + 2981 call-control-object-super-class(4)} + PresentedAddressScreened, PartyNumber, PartySubaddress + FROM Addressing-Data-Elements {itu-t recommendation q 932 + addressing-data-elements(7)}; + +ccObjectClasses OBJECT IDENTIFIER ::= + {itu-t recommendation q 2981 cc-object-classes(6)} + +call CALLCONTROL OBJECTCLASS ::= { + ARGUMENT + SEQUENCE {localPEPID ObjectReferenceId, + remotePEPID ObjectReferenceId, + serviceReference ObjectReferenceId OPTIONAL, + directCallAssociationIds ObjectReferenceIdList, + remoteCallAssociationIds + ObjectReferenceIdList OPTIONAL, + bearerIdList BearerIdList OPTIONAL, + telecomsServiceType TelecomsServiceType, + callPermissions OpenCall} + IDENTIFIER {ccObjectClasses 1}} + +ObjectReferenceId ::= INTEGER(-2147483648..2147483647) -- 4 octets + +-- refers to an object reference, unique to each object within a call +ObjectReferenceIdList ::= SEQUENCE OF ObjectReferenceId + +BearerIdList ::= SEQUENCE OF BearerId + +BearerId ::= OCTET STRING(SIZE (1..3)) + +OpenCall ::= BIT STRING { + reserved(7), externalPartyAddAllowed(6), + existingPartyAddAllowed(5), notifyAllPartiesFlag(4), + notifyOwnerFlag(3), permissionRequiredFlag(2), + addConnectionAllowed(1), addServiceComponentAllowed(0)} + +TelecomsServiceType ::= ENUMERATED { + realtimeMultiMedia(0), nonRealtimeMultiMedia(1), unspecified(2), + ... +} + +localPartyEP CALLCONTROL OBJECTCLASS ::= { + ARGUMENT PartyObjectArgument + IDENTIFIER {ccObjectClasses 2}} +``` + +``` + +remotePartyEP CALLCONTROL OBJECTCLASS ::= { + ARGUMENT PartyObjectArgument + IDENTIFIER {ccObjectClasses 3}} + +PartyObjectArgument ::= SEQUENCE { + partyAddress + SEQUENCE {presentedAddressScreened PresentedAddressScreened, + defaultAddress DefaultAddress OPTIONAL, + networkInternalAddress + NetworkInternalAddress OPTIONAL}, + partyOwnerPEPID ObjectReferenceId, + associatedResourcePEPIDs ObjectReferenceIdList OPTIONAL, + associatedPEPIDs ObjectReferenceIdList OPTIONAL, + partyType + ENUMERATED {initiator(0), receiver(1), callOwner(2), ... + }, + partyStatus + ENUMERATED {confirmed(0), virtual(1), alerting(2), ... + }} + +DefaultAddress ::= OCTET STRING(SIZE (1..21)) + +NetworkInternalAddress ::= OCTET STRING(SIZE (1..21)) + +directCallAssociation CALLCONTROL OBJECTCLASS ::= { + ARGUMENT SEQUENCE {remotePEPID ObjectReferenceId} + IDENTIFIER {ccObjectClasses 4}} + +remoteCallAssociation CALLCONTROL OBJECTCLASS ::= { + ARGUMENT + SEQUENCE {localPEPID ObjectReferenceId, + remotePEPID ObjectReferenceId} + IDENTIFIER {ccObjectClasses 5}} + +serviceComponent CALLCONTROL OBJECTCLASS ::= { + ARGUMENT + SEQUENCE {callPEPID ObjectReferenceId, + serviceComponentCharacteristics + ServiceComponentCharacteristics OPTIONAL, + communicationConfiguration + CommunicationConfiguration OPTIONAL, + serviceTrafficDescriptorRequirements + ServiceTrafficDescriptorRequirements OPTIONAL, + serviceComponentQoSRequirements + ServiceQoSRequirements OPTIONAL, + associatedServiceModuleId + ObjectReferenceId OPTIONAL, + associatedResourceComponentId + ObjectReferenceId OPTIONAL} + IDENTIFIER {ccObjectClasses 6}} + +ServiceComponentCharacteristics ::= OCTET STRING + +CommunicationConfiguration ::= ENUMERATED { + source(0), sink(1), biDirectional(2), ... +} + +ServiceTrafficDescriptorRequirements ::= OCTET STRING + +ServiceQoSRequirements ::= OCTET STRING + +END + +``` + +# 9 Procedures + +## 9.1 Call establishment request + +### 9.1.1 Preceding CC entity + +On receipt of an ESTABLISH-CALL request primitive from the call control signalling service user, the preceding CC entity shall initiate call establishment by sending a callEstablish invoke APDU towards the succeeding CC entity and start timer T703. Following the transmission of the APDU, the preceding CC entity shall enter the Call Initiated state. + +The preceding CC entity shall include element awaitCompleteIndicator in the callEstablish invoke APDU reflecting the value (TRUE or FALSE) of the Await Complete Indicator parameter within the ESTABLISH-CALL request primitive and store this value locally as "Await Complete Indicator". + +The callEstablish invoke APDU shall contain the callSegmentId with the precedingSideCallSegId set to the value provided by the call control signalling service user and the succeedingSideCallSegId set to the null value. Within the argument of the callEstablish invoke APDU, element bearerEstablishmentAddress shall contain an address which, when used as a destination address for bearer establishment in the backward direction from the subsequent CC entity, causes the bearer to be routed to the preceding CC entity's terminal or network node, i.e. to the terminal or network node at the start of the call segment. + +The preceding CC entity shall include element callDescription in the callEstablish invoke APDU, as provided by the call control signalling service user. + +Prior to sending the callEstablish invoke APDU towards the succeeding CC entity, the preceding CC entity shall initiate establishment of a transport mechanism connection to the succeeding CC entity or use an existing transport mechanism (e.g. an already existing connection or a permanently available transport mechanism). + +NOTE – The CC protocol is independent of the underlying transport mechanism. It is therefore out of the scope of this Recommendation which transport mechanism is used. + +### 9.1.2 Succeeding CC entity + +On receipt of a callEstablish invoke APDU, the succeeding CC entity shall enter the Call Present state. + +The succeeding CC entity shall store the contents of element awaitCompleteIndicator as "Await Complete Indicator". + +The receipt of the callEstablish invoke APDU is indicated to the call control signalling service user with an ESTABLISH-CALL indication primitive. + +## 9.2 Call Proceeding + +### 9.2.1 Preceding CC entity + +On receipt of a callProceeding invoke APDU while in state Call Initiated, the preceding CC entity shall stop timer T703, start timer T710, and enter the Outgoing Call Proceeding state. + +The receipt of the callProceeding invoke APDU is indicated to the call control signalling service user with a PROCEED-CALL indication primitive. + +NOTE – This is the earliest time at which the CC signalling service user can establish bearer connections across this segment. + +### 9.2.2 Succeeding CC entity + +On request of the call control signalling service user (PROCEED-CALL request primitive) and while in state Call Present, the succeeding CC entity shall send a callProceeding invoke APDU to the preceding CC entity and enter the Incoming Call Proceeding state. + +The callProceeding invoke APDU shall contain the element callSegmentId with the precedingSideCallSegId set to the value as received in the callEstablish invoke APDU and the succeedingSideCallSegId set to the value provided by the call control signalling service user. + +Within the argument of the callProceeding invoke APDU, element bearerEstablishmentAddress shall contain an address which, when used as a destination address for bearer establishment in the forward direction from the preceding CC entity, causes the bearer to be routed to the succeeding CC entity's terminal or network node, i.e. to the terminal or network node at the end of the call segment. + +NOTE 1 – This is the earliest time at which the CC signalling service user can establish bearer connections across this segment. + +NOTE 2 – A bearer establishment can be initiated from either the call originating user or from the call destination user. + +## 9.3 Call accepted + +### 9.3.1 Preceding CC entity + +On receipt of the callEstablish return result APDU while in state Call Initiated or Outgoing Call Proceeding, the preceding CC entity shall stop timer T703 or T710 and: + +- if the value of stored item "Await Complete Indicator" is TRUE, then enter state Call Ready; +- if the value of stored item "Await Complete Indicator" is FALSE, then enter state Call Active. + +The receipt of the callEstablish return result APDU is indicated to the call control signalling service user with an ESTABLISH-CALL confirm primitive. + +NOTE – If the callEstablish return result APDU was the first response received to a callEstablish invoke, this is the earliest time at which the CC signalling service user can establish bearer connections across this segment. + +### 9.3.2 Succeeding CC entity + +On request of the call control signalling service user (ESTABLISH-CALL response primitive), the succeeding CC entity shall send a callEstablish return result APDU to the preceding CC entity and: + +- if the value of stored item "Await Complete Indicator" is TRUE, then enter state Await Call Completion and start timer T701; +- if the value of stored item "Await Complete Indicator" is FALSE, then enter state Call Active. + +The callEstablish return result APDU shall contain the element callSegmentId. If the succeeding CC entity has not previously sent a callProceeding invoke APDU, the argument of the callEstablish return result APDU shall contain element callSegmentId with the precedingSideCallSegId set to the value as received in the callEstablish invoke APDU and the succeedingSideCallSegId set to the value provided by the call control signalling service user. If it has previously sent a callProceeding invoke APDU, the argument of the callEstablish return result APDU shall contain element callSegmentId as indicated by the CC signalling service user. + +The callEstablish return result APDU shall contain the element CallDescription, as provided by the call control signalling service user in the ESTABLISH-CALL response primitive. + +If the succeeding CC entity has not previously sent a callProceeding invoke APDU, the argument of the callEstablish return result APDU shall contain element bearerEstablishmentAddress. This element shall contain an address which, when used as a destination address for bearer establishment in the forward direction from the preceding CC entity, causes the bearer to be routed to the succeeding CC entity's terminal or network node, i.e. to the terminal or network node at the end of the call segment. + +NOTE – This is the earliest time at which the CC signalling service user can establish bearer connections across this segment. + +## **9.4 Completion of call establishment** + +### **9.4.1 Preceding CC entity** + +On receipt of a COMPLETE-CALL request primitive while in state Call Ready, the preceding CC entity shall send a callComplete invoke APDU to the succeeding CC entity and enter state Call Active. + +The preceding CC entity shall include element callSegmentId in the callComplete invoke APDU. + +### **9.4.2 Succeeding CC entity** + +On receipt of a callComplete invoke APDU in state Await Call Completion, the succeeding CC entity shall enter state Call Active, stop timer T701 and give a COMPLETE-CALL indication primitive to the call control signalling service user. + +## **9.5 Call status change report** + +### **9.5.1 General** + +A change of the information model of a call is reflected in the Call Description belonging to that call. In order to report such a change to the peer CC entity, the callStatus operation, which contains the element callChangedParameter, shall be used. This element indicates changes to the original call description: + +- addition and deletion of a service component object; +- changes to the attributes of a party object (i.e. modification of the status of a party); +- changes to the OpenCall attribute of the call object (i.e. modification of the call permissions). + +A call status change report indicates one or more changes, but any deleted object shall not be referenced in a modified attribute. + +### **9.5.2 Initiating CC entity** + +On receipt of a STATUS-CALL request primitive while in state Await Call Completion or Call Active, the initiating CC entity shall send a callStatus invoke APDU and remain in the same state. + +The initiating CC entity shall include elements callSegmentId and callChangedParameter in the callStatus invoke APDU as indicated by the CC signalling service user. + +The element callChangedParameter contains a list of the changed objects such that: + +- where an object specified in the original Call Description is deleted, the value "deleteObject" shall be used, the objectReference shall be included, and modifiedArgument shall not be included; +- where an object specified in the original Call Description is modified, the value "modifyAttributes" shall be used. + +### 9.5.3 Receiving CC entity + +On receipt of a callStatus invoke APDU in state Call Ready or Call Active, the receiving CC entity shall give a STATUS-CALL indication primitive to the call control signalling service user and remain in the same state. + +## 9.6 Call establishment failure + +### 9.6.1 Preceding CC entity + +On receipt of a callEstablish return error APDU while in state Call Initiated or Outgoing Call Proceeding, the preceding CC entity shall stop all timers (if timers are running) and enter the Call Idle state. + +Call establishment failure is indicated to the call control signalling service user by an ESTABLISH-CALL confirm primitive with negative Result parameter. + +NOTE – The call control signalling service user gives an indication to BC that the bearer connections for this call shall be cleared. + +Call establishment failure can also be indicated from the preceding CC entity while in state Call Ready to the succeeding CC entity by the use of the procedures for call clearing as defined in 9.7. + +### 9.6.2 Succeeding CC entity + +On call control signalling service user request (ESTABLISH-CALL response primitive with negative Result parameter) and while in state Call Present or Incoming Call Proceeding, the succeeding CC entity shall send a callEstablish return error APDU with a suitable error value and enter the Call Idle state. + +Suitable error values are: + +- callDescriptionNotAccepted, if the received call description was not accepted by the CC signalling service user. In this case an alternative call description may be returned together with the error value; +- userBusy, if the called user is busy. In this case, if the received call description was not acceptable by the CC signalling service user, an alternative call description may be returned as additional information together with the error value; +- unallocatedNumber, if the received call description contained an unallocated number; +- noUserResponding, if the called user did not respond to the callEstablish invoke APDU; +- noAnswerFromUser, if no answer from the called user to the callEstablish invoke APDU was received; +- callRejected, if the called user rejected the call; +- destinationOutOfOrder, if the called user's equipment is out of order; +- addressIncomplete, if an address contained in the received call description was incomplete; +- networkOutOfOrder, if equipment in the network is out of order; +- temporaryFailure, if a temporary failure has occurred; +- userNotReachable, if the called user is not reachable; +- unspecified in any other case. + +When sending the callEstablish return error APDU, the Location parameter shall indicate the location at which the failure occurred. When an Error is first generated in a user's terminal, the location value "user" shall be used. When an Error is first generated in a network node, the location value "networkLocalCallSegment" shall be used. If that Error is passed on by a CC entity to another call segment, the value shall be changed to "networkNonLocalCallSegment". + +The callEstablish return error APDU may contain a Call Description element if provided by the CC signalling service user. + +NOTE – The call control signalling service user gives an indication to BC that the bearer connections for this call shall be cleared. + +Call establishment failure can also be indicated from the preceding CC entity to the succeeding CC entity while in state Await Call Completion by the use of the procedures for call clearing as defined in 9.7. + +## 9.7 Call clearing + +### 9.7.1 Procedures at the CC entity that initiates call clearing + +On receipt of a RELEASE-CALL request primitive from the call control signalling service user, the CC entity initiating call clearing shall send a callRelease invoke APDU, stop all timers, start timer T708, and enter the Call Release Request state. + +The argument of the callRelease invoke APDU shall contain a causeValue and the appropriate location parameter in element releaseCause. Valid cause values are "normalCallClearing", "callDescriptionNotAccepted", or "temporaryFailure", depending on the reason why the call control signalling service user initiates call clearing. + +Cause values shall be used as follows: + +- normalCallClearing, if call release was initiated by one of the involved users; +- callDescriptionNotAccepted, if the received call description was not accepted by the CC signalling service user; +- temporaryFailure, if a temporary failure has occurred. + +The location parameter shall indicate the location at which the failure occurred. When a releaseCause is first generated in a user's terminal, the location value "user" shall be used. When a releaseCause is first generated in a network node, the location value "networkLocalCallSegment" shall be used. If that releaseCause is passed on by a CC entity to another call segment the value shall be changed to "networkNonLocalCallSegment". + +The callRelease invoke APDU shall only be sent with a complete callSegmentId. Therefore, a CC entity which has initiated a call establishment, i.e. has sent a callEstablish invoke APDU, shall not initiate call clearing before either a callEstablish return result or callProceeding invoke APDU has been received. + +On receipt of the callRelease return result APDU while in state Call Release Request, the CC entity initiating clearing shall stop timer T708 and enter the Call Idle state. + +The receipt of the callRelease return result APDU is indicated to the call control signalling service user with a RELEASE-CALL confirm primitive. + +NOTE – When sending the RELEASE-CALL request primitive to the CC signalling service provider, the call control signalling service user also requests BC that the bearer connections for this call shall be cleared. + +### 9.7.2 Procedures at the CC entity that responds to clearing + +In any state except Call Idle, Call Release Request, and Call Release Indication the CC entity receiving a callRelease invoke APDU shall stop any timers that are running and enter the Call Release Indication state. The receipt of the callRelease invoke APDU is indicated to the call control signalling service user with a RELEASE-CALL indication primitive. + +On call control signalling service user request (RELEASE-CALL response primitive), the receiving CC entity shall send a callRelease return result APDU and return to the Call Idle state. + +NOTE – When receiving the RELEASE-CALL indication primitive, the call control signalling service user requests BC that the bearer connections for this call shall be cleared. + +### **9.7.3 Call clearing collision** + +In case of call clearing collision, i.e. on receipt of a callRelease invoke APDU while in state Call Release Request, the CC entity shall stop timer T708 and enter the Call Idle state. + +## **9.8 Exceptional procedures** + +### **9.8.1 Timer expiry** + +#### **9.8.1.1 Procedures at the preceding CC entity** + +If timer T703 expires, i.e. if no response to the callEstablish invoke APDU is received, the preceding CC entity shall clear the call internally, release the CallSegmentId, and enter the Call Idle state. + +Call clearing is indicated to the call control signalling service user by an ESTABLISH-CALL confirm primitive with negative Result parameter. + +If timer T710 expires, i.e. if a callProceeding invoke APDU has been received as a response to the callEstablish invoke APDU, but no callEstablish return result or return error APDU is received, the preceding CC entity shall clear the call by sending a callRelease invoke APDU, stop all timers, start timer T708, and enter the Call Release Request state. The callRelease invoke APDU sent to initiate call clearing shall contain causeValue "recovery on timer expiry" and an appropriate location value in element releaseCause. + +Call clearing is indicated to the call control signalling service user by an ESTABLISH-CALL confirm primitive with negative Result parameter. + +#### **9.8.1.2 Procedures at the succeeding CC entity** + +If timer T701 expires, i.e. if no callComplete invoke APDU is received in the Await Call Completion state, the succeeding CC entity shall clear the call internally, release the CallSegmentId, and enter the Call Idle state. + +This exceptional condition is indicated to the call control signalling service user by an ERROR indication primitive with an appropriate Diagnostics parameter. + +#### **9.8.1.3 Procedures at the CC entity that initiates call clearing** + +If timer T708 expires, i.e. if no response to the callRelease invoke APDU is received, the CC entity shall release the call segment ID and enter the Call Idle state. + +A RELEASE-CALL confirm primitive is given to the call control signalling service user if call clearing has been initiated on user request. + +### **9.8.2 Receipt of APDUs with unknown Call Segment Id** + +If an APDU other than a callEstablish invoke is received containing an unknown CallSegmentId, this APDU shall be ignored. + +### **9.8.3 Receipt of APDUs with duplicated Call Segment Id** + +If a callEstablish invoke APDU is received containing a CallSegmentId which is already in use, this APDU shall be ignored. + +### **9.8.4 Receipt of APDUs out of sequence** + +If an APDU out of sequence is received, i.e. a callProceeding invoke after a callEstablish return result, with the same CallSegmentId, this APDU shall be ignored. + +### **9.8.5 Receipt of reject APDUs** + +#### **9.8.5.1 Receipt of a reject APDU that is correlated to a callEstablish invoke** + +On receipt of a reject APDU that is correlated to a callEstablish invoke APDU while in state Call Initiated, the preceding CC entity shall stop timer T703, clear the call internally, release the CallSegmentId, and enter the Call Idle state. + +Call establishment failure is indicated to the call control signalling service user by an ESTABLISH-CALL confirm primitive with negative Result parameter. + +#### **9.8.5.2 Receipt of a reject APDU that is correlated to a callProceeding invoke** + +On receipt of a reject APDU that is correlated to a callProceeding invoke APDU while in state Incoming Call Proceeding, the succeeding CC entity shall remain in this state. + +This exceptional condition is indicated to the call control signalling service user by an ERROR indication primitive with an appropriate Diagnostics parameter. + +#### **9.8.5.3 Receipt of a reject APDU that is correlated to a callComplete invoke** + +On receipt of a reject APDU that is correlated to a callComplete invoke APDU while in state Call Active, the preceding CC entity shall clear the call by sending a callRelease invoke APDU, start timer T708, and enter the Call Release Request state. The callRelease invoke APDU sent to initiate call clearing shall contain causeValue "temporary failure" and an appropriate location value in element releaseCause. + +This exceptional condition is indicated to the call control signalling service user by an ERROR indication primitive with an appropriate Diagnostics parameter. + +#### **9.8.5.4 Receipt of a reject APDU that is correlated to a callStatus invoke** + +On receipt of a reject APDU that is correlated to a callStatus invoke APDU while in state Await Call Completion or Call Active, the CC entity shall remain in the same state. + +This exceptional condition is indicated to the call control signalling service user by an ERROR indication primitive with an appropriate Diagnostics parameter. + +#### **9.8.5.5 Receipt of a reject APDU that is correlated to a callRelease invoke** + +On receipt of a reject APDU that is correlated to a callRelease invoke APDU while in state Call Release Request, the CC entity shall stop timer T708, release the call segment ID, and enter the Call Idle state. + +A RELEASE-CALL confirm primitive is given to the call control signalling service user if call clearing has been initiated on user request. + +#### **9.8.5.6 Receipt of a reject APDU that is correlated to a callEstablish return result** + +On receipt of a reject APDU that is correlated to a callEstablish return result APDU while in state Call Active or Await Call Completion, the succeeding CC entity shall clear the call internally, release the CallSegmentId, and enter the Call Idle state. + +This exceptional condition is indicated to the call control signalling service user by an ERROR indication primitive with an appropriate Diagnostics parameter. + +#### **9.8.5.7 Receipt of a reject APDU that is correlated to a callEstablish return error** + +On receipt of a reject APDU that is correlated to a callEstablish return error APDU, no action shall be taken. + +#### 9.8.5.8 Receipt of a reject APDU that is correlated to a callRelease return result + +On receipt of a reject APDU that is correlated to a callRelease return result APDU, no action shall be taken. + +### 9.8.6 Handling of unrecognized parameters within CC-Operations + +On receipt of an APDU containing a CC-Operation with one or more unrecognized parameters, the receiving CC entity shall examine the parameterActionIndicator contained in this operation and follow the procedures described below as appropriate: + +- If the parameterActionIndicator is set to "clearCallAndItsInformationModel", the receiving CC entity shall clear the call and its information model in accordance with the procedures specified in 9.7. +- If the parameterActionIndicator is set to "discardApduAndReject", the receiving CC entity shall discard the entire APDU and initiate sending of a reject APDU back to the peer CC entity. +- If the parameterActionIndicator is set to "discardApduNoReject", the CC entity shall discard the entire APDU and not initiate sending of a reject APDU. +- If the parameterActionIndicator is set to "discardParameterAndPassApduToApplication", the receiving CC entity shall discard the unrecognized parameter and pass the APDU without the unrecognized parameter on to the CC signalling service user. +- If the parameterActionIndicator is set to "ignoreParameterAndPassApduToApplication", the receiving CC entity shall ignore the unrecognized parameter and pass the APDU including the unrecognized parameter on to the CC signalling service user. + +# 10 Parameter values (Timers) + +| Timer number | Timer value | Call state | Cause for start | Normally terminated | Action to be taken when timer expires | Succeeding CC | Preceding CC | +|--------------|-----------------|--------------------------|--------------------------------------------------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------|--------------| +| T703 | 3 s-15 s (Note) | Call Initiated | On sending of a callEstablish invoke APDU | On receipt of a callEstablish return result/return error, or callProceeding invoke APDU | Clear call internally, release CallSegmentId, enter Call Idle state | – | M | +| T708 | 30 s | Call Release Request | On sending of a callRelease invoke APDU | On receiving a callRelease return result APDU | Release call segment ID and enter Call Idle state | M | M | +| T710 | 30 s | Outgoing Call Proceeding | callProceeding invoke APDU received | On receiving a callEstablish return result/return error APDU | Clear call | – | M | +| T701 | 180 s | Await Call Completion | On sending of a callEstablish return result APDU | On receipt of a callComplete invoke APDU | Clear call internally, release CallSegmentId, enter Call Idle state | M | – | + +NOTE – The value of T703 shall be chosen based on the underlying transport mechanism to be used. + +For timer value T703 the tolerance shall be $-300 \text{ ms}/+3 \text{ s}$ . + +For the other timer values specified in this clause, the tolerance shall be $\pm 10\%$ . + +# 11 Transport mechanism + +The design of this protocol does not demand for a special transport mechanism. However, a reliable transport mechanism is required. + +Transport mechanisms which can be used are listed in Annex D. Subclauses Annex D for the various transport mechanisms specify how a particular mechanism shall be used if it has been chosen. + +NOTE – Annex D is normative but not exclusive, i.e. other reliable transport mechanisms which are not mentioned there can be used as well. + +# 12 SDL Diagrams + +The diagrams in this Recommendation use the Specification and Description Language defined in ITU-T Recommendation Z.100 (1993). + +The diagrams represent the behaviour of the CC signalling service provider, which is split into outgoing CC-ASE and incoming CC-ASE (Application Service Element). + +Input signals from the left and output signals to the left represent primitives to and from the CC signalling service user. Also protocol timer expiry is indicated by an input signal from the left. + +Input signals from the right and output signals to the right represent APDUs sent to and received from the peer CC entity. + +The following abbreviations are used: + +| | | | | | | +|------|--------------------|------|-----------|-------|----------------------| +| inv. | invoke APDU | EST | ESTABLISH | req. | request primitive | +| res. | return result APDU | REL | RELEASE | ind. | indication primitive | +| err. | return error APDU | PROC | PROCEED | resp. | response primitive | +| rej. | reject APDU | | | conf. | confirm primitive | +| | | | | (+) | positive result | +| | | | | (-) | negative result | + +![Block diagram showing the CO-ORD entity connected to a CC signalling service user, Outgoing CC Ase, Incoming CC Ase, and ROSE. Arrows indicate bidirectional signal flow between CO-ORD and each connected entity.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +``` + +graph TD + CSU[CC signalling service user] <--> CO[CO-ORD] + CO <--> OCA[Outgoing CC Ase] + CO <--> ICA[Incoming CC Ase] + CO <--> ROSE + +``` + +T11102770-99 + +Block diagram showing the CO-ORD entity connected to a CC signalling service user, Outgoing CC Ase, Incoming CC Ase, and ROSE. Arrows indicate bidirectional signal flow between CO-ORD and each connected entity. + +**Figure 12-1/Q.2981 – Block diagram** + +**Table 12-1/Q.2981 – Signal routes** + +| CO-ORD_to_Outgoing-CC-ASE | Incoming-CC-ASE_to_CO-ORD | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Primitives:
ESTABLISH_CALL_request
COMPLETE_CALL_request
STATUS_CALL_request
RELEASE_CALL_request
RELEASE_CALL_response | Primitives:
ESTABLISH_CALL_indication
COMPLETE_CALL_indication
STATUS_CALL_indication
RELEASE_CALL_indication
RELEASE_CALL_confirm
ERROR_indication | +| APDUs:
callProceeding_invoke
callEstablish_return_result
callEstablish_return_error
callEstablish_reject
callStatus_invoke
callRelease_invoke
callRelease_return_result
callRelease_reject | APDUs:
callProceeding_invoke
callEstablish_return_result
callEstablish_return_error
callStatus_invoke
callRelease_invoke
callRelease_return_result | + +**Table 12-1/Q.2981 – Signal routes (concluded)** + +| Outgoing-CC-ASE_to_CO-ORD | CO-ORD_to_Incoming-CC-ASE | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Primitives:
ESTABLISH_CALL_confirm
PROCEED_CALL_indication
STATUS_CALL_indication
RELEASE_CALL_indication
RELEASE_CALL_confirm
ERROR_indication | Primitives:
ESTABLISH_CALL_response
PROCEED_CALL_request
STATUS_CALL_request
RELEASE_CALL_request
RELEASE_CALL_response | +| APDUs:
callEstablish_invoke
callComplete_invoke
callStatus_invoke
callRelease_invoke
callRelease_result | APDUs:
callEstablish_invoke
callComplete_invoke
callStatus_invoke
callRelease_invoke
callRelease_return_result
callRelease_reject
callEstablish_reject | + +## 12.1 Outgoing CC-ASE + +See Figures 12-2 to 12-9. + +![State transition diagram for Outgoing CC-ASE](e151d3468319b81f042ca232c4d82e4b_img.jpg) + +Process Outgoing CC-ASE + +``` +stateDiagram-v2 + [*] --> Call_Idle + Call_Idle --> EST_CALL_req + EST_CALL_req --> store_await_complete_indicator + store_await_complete_indicator --> start_timer_T703 + start_timer_T703 --> callEstablish_inv + callEstablish_inv --> Call_Initiated +``` + +The diagram illustrates the state transitions for the Outgoing CC-ASE process. It begins with an initial state leading to **Call\_Idle**. From **Call\_Idle**, a transition labeled **EST-CALL req.** leads to a state labeled **store await complete indicator**. This is followed by a transition labeled **start timer T703** to a state labeled **callEstablish inv.**, which finally leads to the **Call\_Initiated** state. + +State transition diagram for Outgoing CC-ASE + +Figure 12-2/Q.2981 – SDL for Call Control, outgoing call + +![State transition diagram for outgoing call control. It starts at 'Call_Initiated' and branches into five paths based on 'callProceed. inv.', 'callEstablish res.', 'callEstablish err.', 'callEstablish rej.', and 'timer T703 expiry'. The 'callProceed. inv.' path leads to 'Outg_Call_Proceeding'. The 'callEstablish res.' path leads to 'Call_Ready' or 'Call_Active'. The 'callEstablish err.' and 'callEstablish rej.' paths lead to 'Call_Idle'. The 'timer T703 expiry' path leads to 'Call_Idle' via 'clear call internally'.](9a5927586a691c4908aa2cf98bd47ebb_img.jpg) + +Process Outgoing CC-ASE + +``` + +stateDiagram-v2 + [*] --> Call_Initiated + Call_Initiated --> callProceed_inv : callProceed. inv. + Call_Initiated --> callEstablish_res : callEstablish res. + Call_Initiated --> callEstablish_err : callEstablish err. + Call_Initiated --> callEstablish_rej : callEstablish rej. + Call_Initiated --> timer_T703_expiry : timer T703 expiry + + callProceed_inv --> stop_timer_T703_1 : stop timer T703 + stop_timer_T703_1 --> start_timer_T710 : start timer T710 + start_timer_T710 --> PROC_CALL_ind : PROC-CALL ind. + PROC_CALL_ind --> Outg_Call_Proceeding + + callEstablish_res --> stop_timer_T703_2 : stop timer T703 + stop_timer_T703_2 --> EST_CALL_conf_plus : EST-CALL conf. (+) + EST_CALL_conf_plus --> await_compl_ind_TRUE : await compl. ind. TRUE + await_compl_ind_TRUE --> Call_Ready : y + await_compl_ind_TRUE --> Call_Active : n + + callEstablish_err --> stop_timer_T703_3 : stop timer T703 + stop_timer_T703_3 --> EST_CALL_conf_minus_1 : EST-CALL conf. (-) + EST_CALL_conf_minus_1 --> Call_Idle_1 : Call_Idle + + callEstablish_rej --> stop_timer_T703_4 : stop timer T703 + stop_timer_T703_4 --> clear_call_internally : clear call internally + clear_call_internally --> EST_CALL_conf_minus_2 : EST-CALL conf. (-) + EST_CALL_conf_minus_2 --> Call_Idle_2 : Call_Idle + + timer_T703_expiry --> clear_call_internally + +``` + +State transition diagram for outgoing call control. It starts at 'Call\_Initiated' and branches into five paths based on 'callProceed. inv.', 'callEstablish res.', 'callEstablish err.', 'callEstablish rej.', and 'timer T703 expiry'. The 'callProceed. inv.' path leads to 'Outg\_Call\_Proceeding'. The 'callEstablish res.' path leads to 'Call\_Ready' or 'Call\_Active'. The 'callEstablish err.' and 'callEstablish rej.' paths lead to 'Call\_Idle'. The 'timer T703 expiry' path leads to 'Call\_Idle' via 'clear call internally'. + +Figure 12-3/Q.2981 – SDL for Call Control, outgoing call + +![State transition diagram for Outgoing Call Control (CC-ASE). The process starts in the Outg_Call_Proceeding state. Three transitions are possible: callEstablish res. (leading to stop timer T710, then EST-CALL conf. (+), then a decision await compl.ind. TRUE), callEstablish err. (leading to stop timer T710, then EST-CALL conf. (-), then Call_Idle), and timer T710 expiry (leading to clear call, then start timer T708, then callRelease inv., then EST-CALL conf. (-), then Call_Release_Request). The await compl.ind. TRUE decision leads to Call_Ready if TRUE and Call_Active if not (n).](0b7849dae424b0dd33e6386d2384643a_img.jpg) + +Process Outgoing CC-ASE + +``` + +stateDiagram-v2 + [*] --> Outg_Call_Proceeding + Outg_Call_Proceeding --> callEstablish_res : callEstablish res. + Outg_Call_Proceeding --> callEstablish_err : callEstablish err. + Outg_Call_Proceeding --> timer_T710_expiry : timer T710 expiry + callEstablish_res --> stop_timer_T710_1 : stop timer T710 + stop_timer_T710_1 --> EST_CALL_conf_plus : EST-CALL conf. (+) + EST_CALL_conf_plus --> await_compl_ind_TRUE : await compl.ind. TRUE + await_compl_ind_TRUE --> Call_Ready : y + await_compl_ind_TRUE --> Call_Active : n + callEstablish_err --> stop_timer_T710_2 : stop timer T710 + stop_timer_T710_2 --> EST_CALL_conf_minus_1 : EST-CALL conf. (-) + EST_CALL_conf_minus_1 --> Call_Idle + timer_T710_expiry --> clear_call : clear call + clear_call --> start_timer_T708 : start timer T708 + start_timer_T708 --> callRelease_inv : callRelease inv. + callRelease_inv --> EST_CALL_conf_minus_2 : EST-CALL conf. (-) + EST_CALL_conf_minus_2 --> Call_Release_Request + +``` + +State transition diagram for Outgoing Call Control (CC-ASE). The process starts in the Outg\_Call\_Proceeding state. Three transitions are possible: callEstablish res. (leading to stop timer T710, then EST-CALL conf. (+), then a decision await compl.ind. TRUE), callEstablish err. (leading to stop timer T710, then EST-CALL conf. (-), then Call\_Idle), and timer T710 expiry (leading to clear call, then start timer T708, then callRelease inv., then EST-CALL conf. (-), then Call\_Release\_Request). The await compl.ind. TRUE decision leads to Call\_Ready if TRUE and Call\_Active if not (n). + +Figure 12-4/Q.2981 – SDL for Call Control, outgoing call + +![SDL diagram for Process Outgoing CC-ASE, Figure 12-5. It shows a state transition from Call_Ready to Call_Active via COMPLETE-CALL req. and callComplete inv. messages, and a self-loop on Call_Ready via callStatus inv. and STATUS-CALL ind. messages.](798679874d1c29f8343506a156c79d7e_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Call_Ready + Call_Ready --> COMPLETE-CALL req. + COMPLETE-CALL req. --> callComplete inv. + callComplete inv. --> Call_Active + Call_Ready --> callStatus inv. + callStatus inv. --> STATUS-CALL ind. + STATUS-CALL ind. --> Call_Ready + +``` + +SDL diagram for Process Outgoing CC-ASE, Figure 12-5. It shows a state transition from Call\_Ready to Call\_Active via COMPLETE-CALL req. and callComplete inv. messages, and a self-loop on Call\_Ready via callStatus inv. and STATUS-CALL ind. messages. + +Figure 12-5/Q.2981 – SDL for Call Control, outgoing call + +![SDL diagram for Process Outgoing CC-ASE, Figure 12-6. It shows transitions from Call_Active to four different message paths: STATUS-CALL req. (leading to Call_Active), callStatus inv. (leading to Call_Active), callStatus rej. (leading to Call_Active), and callComplete rej. (leading to clear call, start timer T708, callRelease inv., ERROR ind., and Call_Release_Request).](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Call_Active + Call_Active --> STATUS-CALL req. + STATUS-CALL req. --> callStatus inv. + callStatus inv. --> Call_Active + Call_Active --> callStatus inv. + callStatus inv. --> STATUS-CALL ind. + STATUS-CALL ind. --> Call_Active + Call_Active --> callStatus rej. + callStatus rej. --> ERROR ind. + ERROR ind. --> Call_Active + Call_Active --> callComplete rej. + callComplete rej. --> clear call + clear call --> start timer T708 + start timer T708 --> callRelease inv. + callRelease inv. --> ERROR ind. + ERROR ind. --> Call_Release_Request + +``` + +SDL diagram for Process Outgoing CC-ASE, Figure 12-6. It shows transitions from Call\_Active to four different message paths: STATUS-CALL req. (leading to Call\_Active), callStatus inv. (leading to Call\_Active), callStatus rej. (leading to Call\_Active), and callComplete rej. (leading to clear call, start timer T708, callRelease inv., ERROR ind., and Call\_Release\_Request). + +Figure 12-6/Q.2981 – SDL for Call Control, outgoing call + +![State transition diagram for Process Outgoing CC-ASE. It starts from 'any state' (except Call_Idle, Call_Rel_Req/Ind.) and branches into two paths. The left path goes through 'REL-CALL req.' to 'stop timers, if running' to 'start timer T708' to 'callRelease inv.' to 'Call_Release_Request'. The right path goes through 'callRelease inv.' to 'stop timers, if running' to 'REL-CALL ind.' to 'Call_Release_Indication'.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +Process Outgoing CC-ASE + +``` + +stateDiagram-v2 + [*] --> any_state : any state + any_state --> REL_CALL_req : REL-CALL req. + any_state --> callRelease_inv : callRelease inv. + REL_CALL_req --> stop_timers : stop timers, if running + stop_timers --> start_timer : start timer T708 + start_timer --> callRelease_inv : callRelease inv. + callRelease_inv --> Call_Release_Request : Call_Release_Request + callRelease_inv --> stop_timers : stop timers, if running + stop_timers --> REL_CALL_ind : REL-CALL ind. + REL_CALL_ind --> Call_Release_Indication : Call_Release_Indication + +``` + +State transition diagram for Process Outgoing CC-ASE. It starts from 'any state' (except Call\_Idle, Call\_Rel\_Req/Ind.) and branches into two paths. The left path goes through 'REL-CALL req.' to 'stop timers, if running' to 'start timer T708' to 'callRelease inv.' to 'Call\_Release\_Request'. The right path goes through 'callRelease inv.' to 'stop timers, if running' to 'REL-CALL ind.' to 'Call\_Release\_Indication'. + +Figure 12-7/Q.2981 – SDL for Call Control, outgoing call, call release + +![State transition diagram for outgoing call release. It starts with 'Call_Release_Request' leading to four parallel paths: 'callRelease res.', 'callRelease inv.', 'callRelease rej.', and 'timer T708 expiry'. Each path leads to 'stop timer T708' (except for the timer path which goes to 'release call'). All four paths then lead to 'REL-CALL conf.'. The 'REL-CALL conf.' for the first three paths leads to 'Call_Idle'. The 'REL-CALL conf.' for the fourth path has a guard 'only if clearing initiated by CC sign. serv. user' and leads to 'Call_Idle'. There is also a guard 'only if clearing initiated by CC sign. serv. user' on the transition from 'stop timer T708' to 'REL-CALL conf.' for the 'callRelease rej.' path.](e8e818455bb0d1a6153299a388b94868_img.jpg) + +Process Outgoing CC-ASE + +``` + +stateDiagram-v2 + [*] --> Call_Release_Request + Call_Release_Request --> callRelease_res + Call_Release_Request --> callRelease_inv + Call_Release_Request --> callRelease_rej + Call_Release_Request --> timer_T708_expiry + + callRelease_res --> stop_timer_T708_res + callRelease_inv --> stop_timer_T708_inv + callRelease_rej --> stop_timer_T708_rej + timer_T708_expiry --> release_call + + stop_timer_T708_res --> REL_CALL_conf_res + stop_timer_T708_inv --> REL_CALL_conf_inv + stop_timer_T708_rej --> REL_CALL_conf_rej + release_call --> REL_CALL_conf_expiry + + REL_CALL_conf_res --> Call_Idle_res + REL_CALL_conf_inv --> Call_Idle_inv + REL_CALL_conf_rej --> Call_Idle_rej + REL_CALL_conf_expiry --> Call_Idle_expiry + + note right of REL_CALL_conf_inv: only if clearing initiated by CC sign. serv. user + note right of REL_CALL_conf_expiry: only if clearing initiated by CC sign. serv. user + +``` + +State transition diagram for outgoing call release. It starts with 'Call\_Release\_Request' leading to four parallel paths: 'callRelease res.', 'callRelease inv.', 'callRelease rej.', and 'timer T708 expiry'. Each path leads to 'stop timer T708' (except for the timer path which goes to 'release call'). All four paths then lead to 'REL-CALL conf.'. The 'REL-CALL conf.' for the first three paths leads to 'Call\_Idle'. The 'REL-CALL conf.' for the fourth path has a guard 'only if clearing initiated by CC sign. serv. user' and leads to 'Call\_Idle'. There is also a guard 'only if clearing initiated by CC sign. serv. user' on the transition from 'stop timer T708' to 'REL-CALL conf.' for the 'callRelease rej.' path. + +Figure 12-8/Q.2981 – SDL for Call Control, outgoing call, call release + +![SDL for Call Control, outgoing call, call release](0a42e05c07941450f34e4f7117725834_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Call_Release_Indication + Call_Release_Indication --> REL_CALL_resp + REL_CALL_resp --> callRelease_res + callRelease_res --> Call_Idle + +``` + +The diagram is titled "Process Outgoing CC-ASE". It shows a vertical sequence of four states and transitions: + + +- An oval state labeled "Call\_Release\_Indication". +- A downward arrow to a chevron-shaped transition labeled "REL-CALL resp.". +- A downward arrow to a chevron-shaped transition labeled "callRelease res.". +- A downward arrow to an oval state labeled "Call\_Idle". + +SDL for Call Control, outgoing call, call release + +Figure 12-9/Q.2981 – SDL for Call Control, outgoing call, call release + +## 12.2 Incoming CC-ASE + +See Figures 12-10 to 12-18. + +![SDL for Call Control, incoming call](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Call_Idle + Call_Idle --> callEstablish_inv + callEstablish_inv --> store_await_complete_indicator + store_await_complete_indicator --> EST_CALL_ind + EST_CALL_ind --> Call_Present + +``` + +The diagram is titled "Process Incoming CC-ASE". It shows a vertical sequence of five states and transitions: + + +- An oval state labeled "Call\_Idle". +- A downward arrow to a chevron-shaped transition labeled "callEstablish inv.". +- A downward arrow to a rectangular state labeled "store await complete indicator". +- A downward arrow to a chevron-shaped transition labeled "EST-CALL ind.". +- A downward arrow to an oval state labeled "Call\_Present". + +SDL for Call Control, incoming call + +Figure 12-10/Q.2981 – SDL for Call Control, incoming call + +![State transition diagram for incoming call control. It starts at Call_Present and branches into three paths: PROC-CALL req. leading to Incom_Call_Proceeding; EST-CALL resp. (+) leading to a decision point 'await compl.ind. TRUE'; and EST-CALL resp. (-) leading to Call_Idle. The decision point has a 'y' path to 'start timer T701' and 'Await_Call_Completion', and an 'n' path to Call_Active.](c1df61cc3717e878a48e530218403403_img.jpg) + +Process Incoming CC-ASE + +``` + +stateDiagram-v2 + [*] --> Call_Present + Call_Present --> PROC_CALL_req : PROC-CALL req. + Call_Present --> EST_CALL_resp_plus : EST-CALL resp. (+) + Call_Present --> EST_CALL_resp_minus : EST-CALL resp. (-) + PROC_CALL_req --> callProceed_inv : callProceed. inv. + callProceed_inv --> Incom_Call_Proceeding + EST_CALL_resp_plus --> callEstablish_res : callEstablish res. + callEstablish_res --> await_compl_ind : await compl.ind. TRUE + await_compl_ind --> start_timer_T701 : y + start_timer_T701 --> Await_Call_Completion + await_compl_ind --> Call_Active : n + EST_CALL_resp_minus --> callEstablish_err : callEstablish err. + callEstablish_err --> Call_Idle + +``` + +State transition diagram for incoming call control. It starts at Call\_Present and branches into three paths: PROC-CALL req. leading to Incom\_Call\_Proceeding; EST-CALL resp. (+) leading to a decision point 'await compl.ind. TRUE'; and EST-CALL resp. (-) leading to Call\_Idle. The decision point has a 'y' path to 'start timer T701' and 'Await\_Call\_Completion', and an 'n' path to Call\_Active. + +Figure 12-11/Q.2981 – SDL for Call Control, incoming call + +![State transition diagram for incoming call control. It starts with 'Incom_Call_Proceeding' leading to three parallel paths: 'EST-CALL resp. (+)' leading to 'callEstablish res.' then a decision 'await compl.ind. TRUE'; 'EST-CALL resp. (-)' leading to 'callEstablish err.' then 'Call_Idle'; and 'callProceed. rej.' leading to 'ERROR ind.' then 'Incom_Call_Proceeding'. The decision 'await compl.ind. TRUE' has a 'y' path to 'start timer T701' then 'Await_Call_Completion', and an 'n' path to 'Call_Active'.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +Process Incoming CC-ASE + +``` + +stateDiagram-v2 + [*] --> Incom_Call_Proceeding + Incom_Call_Proceeding --> EST_CALL_resp_plus : EST-CALL resp. (+) + Incom_Call_Proceeding --> EST_CALL_resp_minus : EST-CALL resp. (-) + Incom_Call_Proceeding --> callProceed_rej : callProceed. rej. + EST_CALL_resp_plus --> callEstablish_res : callEstablish res. + EST_CALL_resp_minus --> callEstablish_err : callEstablish err. + callProceed_rej --> ERROR_ind : ERROR ind. + callEstablish_res --> await_compl_ind : await compl.ind. TRUE + callEstablish_err --> Call_Idle : Call_Idle + ERROR_ind --> Incom_Call_Proceeding : Incom_Call_Proceeding + await_compl_ind --> start_timer_T701 : start timer T701 (y) + await_compl_ind --> Call_Active : Call_Active (n) + start_timer_T701 --> Await_Call_Completion : Await_Call_Completion + +``` + +State transition diagram for incoming call control. It starts with 'Incom\_Call\_Proceeding' leading to three parallel paths: 'EST-CALL resp. (+)' leading to 'callEstablish res.' then a decision 'await compl.ind. TRUE'; 'EST-CALL resp. (-)' leading to 'callEstablish err.' then 'Call\_Idle'; and 'callProceed. rej.' leading to 'ERROR ind.' then 'Incom\_Call\_Proceeding'. The decision 'await compl.ind. TRUE' has a 'y' path to 'start timer T701' then 'Await\_Call\_Completion', and an 'n' path to 'Call\_Active'. + +Figure 12-12/Q.2981 – SDL for Call Control, incoming call + +![State transition diagram for incoming call control. It starts in 'Await_Call_Completion' and branches into four paths based on 'callComplete inv.', 'timer T701 expiry', 'STATUS-CALL req.', and 'callStatus rej.'. The first path leads to 'Call_Active', the second to 'Call_Idle', and the third and fourth back to 'Await_Call_Completion'.](12c19090355e19922e23044633b9d1ea_img.jpg) + +Process Incoming CC-ASE + +``` + +stateDiagram-v2 + [*] --> Await_Call_Completion + state "Await_Call_Completion" as Await_Call_Completion + state "Call_Active" as Call_Active + state "Call_Idle" as Call_Idle + + state "callComplete inv." as callComplete inv. + state "timer T701 expiry" as timer T701 expiry + state "STATUS-CALL req." as STATUS-CALL req. + state "callStatus rej." as callStatus rej. + + state "stop timer T701" as stop timer T701 + state "clear call internally" as clear call internally + state "callStatus inv." as callStatus inv. + + state "COMPLETE-CALL ind." as COMPLETE-CALL ind. + state "ERROR ind." as ERROR ind. + + Await_Call_Completion --> callComplete inv. + Await_Call_Completion --> timer T701 expiry + Await_Call_Completion --> STATUS-CALL req. + Await_Call_Completion --> callStatus rej. + + callComplete inv. --> stop timer T701 + stop timer T701 --> COMPLETE-CALL ind. + COMPLETE-CALL ind. --> Call_Active + + timer T701 expiry --> clear call internally + clear call internally --> ERROR ind. + ERROR ind. --> Call_Idle + + STATUS-CALL req. --> callStatus inv. + callStatus inv. --> Await_Call_Completion + + callStatus rej. --> ERROR ind. + ERROR ind. --> Await_Call_Completion + +``` + +State transition diagram for incoming call control. It starts in 'Await\_Call\_Completion' and branches into four paths based on 'callComplete inv.', 'timer T701 expiry', 'STATUS-CALL req.', and 'callStatus rej.'. The first path leads to 'Call\_Active', the second to 'Call\_Idle', and the third and fourth back to 'Await\_Call\_Completion'. + +**Figure 12-13/Q.2981 – SDL for Call Control, incoming call** + +![State transition diagram for incoming call control. It starts at Call_Active and branches into four paths based on incoming messages: STATUS-CALL req., callStatus inv., callStatus rej., and callEstablish rej. The first three paths lead back to Call_Active, while the fourth path leads to Call_Idle via an ERROR ind. message.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +Process Incoming CC-ASE + +``` + +stateDiagram-v2 + [*] --> Call_Active + Call_Active --> STATUS-CALL req. + Call_Active --> callStatus inv. + Call_Active --> callStatus rej. + Call_Active --> callEstablish rej. + STATUS-CALL req. --> callStatus inv. + callStatus inv. --> STATUS-CALL ind. + callStatus rej. --> ERROR ind. + callEstablish rej. --> clear call internally + callStatus inv. --> Call_Active + STATUS-CALL ind. --> Call_Active + ERROR ind. --> Call_Active + clear call internally --> ERROR ind. + ERROR ind. --> Call_Idle + +``` + +State transition diagram for incoming call control. It starts at Call\_Active and branches into four paths based on incoming messages: STATUS-CALL req., callStatus inv., callStatus rej., and callEstablish rej. The first three paths lead back to Call\_Active, while the fourth path leads to Call\_Idle via an ERROR ind. message. + +Figure 12-14/Q.2981 – SDL for Call Control, incoming call + +![State transition diagram titled 'Process Incoming CC-ASE'. It shows two parallel paths starting from 'any state' (with a guard 'except Call_Idle, Call_Rel_Req/Ind.'). The left path consists of 'REL-CALL req.' -> 'stop timers, if running' -> 'start timer T708' -> 'callRelease inv.' -> 'Call_Release_Request'. The right path consists of 'callRelease inv.' -> 'stop timers, if running' -> 'REL-CALL ind.' -> 'Call_Release_Indication'.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> any_state : any state + any_state --> REL_CALL_req : REL-CALL req. + any_state --> callRelease_inv : callRelease inv. + REL_CALL_req --> stop_timers_1 : stop timers, if running + stop_timers_1 --> start_timer_T708 : start timer T708 + start_timer_T708 --> callRelease_inv_2 : callRelease inv. + callRelease_inv_2 --> Call_Release_Request : Call_Release_Request + callRelease_inv --> stop_timers_2 : stop timers, if running + stop_timers_2 --> REL_CALL_ind : REL-CALL ind. + REL_CALL_ind --> Call_Release_Indication : Call_Release_Indication + +``` + +State transition diagram titled 'Process Incoming CC-ASE'. It shows two parallel paths starting from 'any state' (with a guard 'except Call\_Idle, Call\_Rel\_Req/Ind.'). The left path consists of 'REL-CALL req.' -> 'stop timers, if running' -> 'start timer T708' -> 'callRelease inv.' -> 'Call\_Release\_Request'. The right path consists of 'callRelease inv.' -> 'stop timers, if running' -> 'REL-CALL ind.' -> 'Call\_Release\_Indication'. + +Figure 12-15/Q.2981 – SDL for Call Control, incoming call, call release + +![State transition diagram for Call Control, incoming call, call release. It shows four main paths from Call_Release_Request: callRelease res., callRelease inv., callRelease rej., and timer T708 expiry. Each path leads to a stop timer T708, then a REL-CALL conf. message, and finally a Call_Idle state. The callRelease rej. and timer T708 expiry paths include a condition 'only if clearing initiated by CC sign. serv. user'.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +Process Incoming CC-ASE + +``` + +stateDiagram-v2 + [*] --> Call_Release_Request + Call_Release_Request --> callRelease_res + Call_Release_Request --> callRelease_inv + Call_Release_Request --> callRelease_rej + Call_Release_Request --> timer_T708_expiry + + callRelease_res --> stop_timer_T708_1 + stop_timer_T708_1 --> REL_CALL_conf_1 + REL_CALL_conf_1 --> Call_Idle_1 + + callRelease_inv --> stop_timer_T708_2 + stop_timer_T708_2 --> REL_CALL_conf_2 + REL_CALL_conf_2 --> Call_Idle_2 + + callRelease_rej --> stop_timer_T708_3 + stop_timer_T708_3 --> REL_CALL_conf_3 + REL_CALL_conf_3 --> Call_Idle_3 + + timer_T708_expiry --> release_call + release_call --> REL_CALL_conf_4 + REL_CALL_conf_4 --> Call_Idle_4 + +``` + +The diagram illustrates the state transitions for processing an incoming call release request. It starts with **Call\_Release\_Request** (initial state) leading to four possible events: **callRelease res.**, **callRelease inv.**, **callRelease rej.**, and **timer T708 expiry**. Each event leads to a **stop timer T708** state, which then leads to a **REL-CALL conf.** state, which finally leads to the **Call\_Idle** state. The **callRelease rej.** and **timer T708 expiry** paths include a condition **only if clearing initiated by CC sign. serv. user** before reaching the **REL-CALL conf.** state. + +State transition diagram for Call Control, incoming call, call release. It shows four main paths from Call\_Release\_Request: callRelease res., callRelease inv., callRelease rej., and timer T708 expiry. Each path leads to a stop timer T708, then a REL-CALL conf. message, and finally a Call\_Idle state. The callRelease rej. and timer T708 expiry paths include a condition 'only if clearing initiated by CC sign. serv. user'. + +Figure 12-16/Q.2981 – SDL for Call Control, incoming call, call release + +![State transition diagram for Call Control, incoming call, call release](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +The diagram illustrates a sequence of states and transitions for call control. It is titled "Process Incoming CC-ASE" and is enclosed in a rectangular box. The sequence of states and transitions is as follows: + +- Call\_Release\_Indication** (oval state) +- REL-CALL resp.** (chevron transition) +- callRelease res.** (chevron transition) +- Call\_Idle** (oval state) + +Arrows indicate a downward flow from the initial state to the final state. + +``` +graph TD; A([Call_Release_Indication]) --> B[/REL-CALL resp./]; B --> C[/callRelease res./]; C --> D([Call_Idle]) +``` + +State transition diagram for Call Control, incoming call, call release + +**Figure 12-17/Q.2981 – SDL for Call Control, incoming call, call release** + +![State transition diagram for handling unrecognized parameters within CC operations. The process starts in 'any state', receives 'any APDU', and checks if there is an 'unrecognized parameter?'. If 'n' (no), it proceeds as usual. If 'y' (yes), it evaluates the 'parameterAction Indicator'. Based on the indicator (0-4), it either clears the call, discards the APDU, or ignores the parameter, leading to various subsequent actions like stopping timers, starting timer T708, or sending error indications.](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +``` + +stateDiagram-v2 + [*] --> any_state_1 : any state + any_state_1 --> any_APDU : any APDU + any_APDU --> unrecognized_parameter : unrecognized parameter ? + unrecognized_parameter --> proceed_as_usual : n + proceed_as_usual --> any_state_2 : any state + unrecognized_parameter --> evaluate_indicator : y + evaluate_indicator --> clear_call : 0 + clear_call --> stop_timers : stop timers, if running + stop_timers --> start_timer : start timer T708 + start_timer --> callRelease_inv : callRelease inv. + callRelease_inv --> ERROR_ind : ERROR ind. + ERROR_ind --> Call_Release_Request : Call_Release_Request + evaluate_indicator --> discard_1 : 1 + discard_1 --> rej_APDU : rej. APDU + evaluate_indicator --> discard_2 : 2 + discard_2 --> any_state_3 : any state + evaluate_indicator --> discard_3 : 3 + discard_3 --> APDU_without : APDU without parameter + evaluate_indicator --> ignore_4 : 4 + ignore_4 --> APDU_with : APDU including parameter + rej_APDU --> any_state_3 + APDU_without --> any_state_3 + APDU_with --> any_state_3 + +``` + +State transition diagram for handling unrecognized parameters within CC operations. The process starts in 'any state', receives 'any APDU', and checks if there is an 'unrecognized parameter?'. If 'n' (no), it proceeds as usual. If 'y' (yes), it evaluates the 'parameterAction Indicator'. Based on the indicator (0-4), it either clears the call, discards the APDU, or ignores the parameter, leading to various subsequent actions like stopping timers, starting timer T708, or sending error indications. + +**Figure 12-18/Q.2981 – SDL for the handling of unrecognized parameters within CC operations** + +## Bearer coordination requirements for CC signalling service users + +Signalling for bearer control is outside the scope of this Recommendation. The way in which a CC entity coordinates the call's bearers is also outside the scope of this Recommendation, except that the following requirements shall be met. + +### A.1 Requirements at a CC entity that establishes a bearer towards an adjacent CC entity + +The requirements in this subclause apply to an end CC entity that initiates bearer establishment towards the adjacent CC entity on request of the application. An end CC entity can be an originating CC entity that initiates bearer establishment in the forward direction (with respect to the direction of call establishment) or a terminating CC entity that initiates bearer establishment in the backward direction (with respect to the direction of call establishment). + +The requirements in this subclause also apply to a transit CC entity that continues bearer establishment towards the subsequent CC entity following receipt of an incoming bearer from the preceding CC entity (such a bearer being in the forward direction with respect to the direction of call establishment), or that continues bearer establishment towards the preceding CC entity following receipt of an incoming bearer from the subsequent CC entity (such a bearer being in the backward direction with respect to the direction of call establishment). + +Bearer establishment in the forward direction shall not commence before one of the following APDUs has been received from the subsequent CC entity: + +- callProceeding invoke APDU; or +- callEstablish return result APDU. + +The contents of elements *bearerEstablishmentAddress* and *callSegmentId* in the first of the above APDUs to be received shall be used as the destination address and the call segment identifier respectively for bearer establishment. + +NOTE 1 – Omission of either of these elements from the first of these APDUs constitutes a protocol error. + +Bearer establishment in the backward direction shall not commence before one of the following APDUs has been sent to the preceding CC entity: + +- callProceeding invoke APDU; or +- callEstablish return result APDU. + +The contents of element *callSegmentId* in the first of the above APDUs to be transmitted and element *bearerEstablishmentAddress* in the received *callEstablish invoke* APDU shall be used as the call segment identifier and the destination address respectively for bearer establishment. + +NOTE 2 – For bearer establishment in either direction, the value used for the bearer destination address will cause the bearer to be routed to the terminal or network node where the CC entity at the opposite end of the call segment is located. + +NOTE 3 – For bearer establishment in either direction, the call segment identifier is conveyed transparently by bearer control signalling to the terminal or network node where the CC entity at the opposite end of the call segment is located, thereby allowing that terminal or network node to link the bearer to the call. + +NOTE 4 – Call control signalling service users should ensure that bearer connection elements established by associated bearer control prior to call acceptance are consistent with all variants of selectable options within the call description included in the call establishment request. After call establishment call control entities should ensure that bearer connection elements are consistent with the final call description. Bearer connection elements and bearer connection establishment requests failing these criteria should be rejected or released as appropriate. + +For bearer establishment in either direction, an address representing the local CC entity (i.e. the CC entity at the start of the segment) shall be used as the calling address of the bearer. + +For bearer establishment in either direction, a bearer identifier value by which the bearer is to be known by the two CC entities at either end of the call segment may be provided as part of the bearer establishment request. The bearer identifier value shall have significance across the call segment concerned. + +NOTE 5 – For bearer establishment in either direction, the bearer identifier value, if provided in the bearer establishment request, is conveyed transparently by bearer control signalling to the terminal or network node where the CC entity at the opposite end of the call segment is located. Its purpose is to allow that CC entity to associate the bearer establishment with a bearer reference conveyed within call control signalling (e.g. as an attribute of an Attachment object). If call control signalling has already made reference to this bearer, prior to its establishment, the bearer identifier value used in the bearer establishment request should be the same as the bearer reference already used by call control signalling. Any further call control signalling that needs to refer to this bearer should use the bearer identifier value used in the bearer establishment request. + +Bearer establishment shall not commence after a callRelease invoke APDU has been sent or received across the segment concerned. + +### **A.2 Requirements at a CC entity that receives a bearer establishment from an adjacent CC entity** + +The requirements in this subclause apply to a CC entity that receives an incoming bearer establishment from an adjacent CC entity. This can be from the preceding CC entity (in the case of a bearer established in the forward direction with respect to the direction of call establishment) or from the subsequent CC entity (in the case of a bearer established in the backward direction with respect to the direction of call establishment). + +A terminal or network node that receives an incoming bearer establishment signal containing a destination address that indicates that that terminal or network node is the destination of the bearer shall attempt to match the received call segment identifier with a call segment identifier assigned to a call segment that is associated with a CC entity on that terminal or network node. If a match is found, the CC entity concerned shall proceed with establishment of the bearer. + +NOTE 1 – In the case of a transit CC, the time at which bearer establishment is continued across the next call segment is outside the scope of this Recommendation, apart from being subject to the restrictions in A.1. + +NOTE 2 – In the case of an end CC, the bearer should be presented to the application. + +NOTE 3 – Call control signalling service users should ensure that bearer connection elements established by associated bearer control prior to call acceptance are consistent with all variants of selectable options within the call description included in the call establishment request. After call establishment call control entities should ensure that bearer connection elements are consistent with the final call description. Bearer connection elements and bearer connection establishment requests failing these criteria should be rejected or released as appropriate. + +If the terminal or network node is the destination of the bearer but is unable to match the received call segment identifier with a call segment identifier assigned to a call segment that is associated with a CC entity on that terminal or network node, the terminal or network node shall reject the bearer establishment request. + +Even though a succeeding CC entity is required to send a callProceeding invoke APDU or callEstablish return result APDU before commencing bearer establishment in the backward direction, it is possible for a bearer establishment request to arrive at a preceding CC entity before any of the above APDUs arrives. In this case, the preceding CC shall await the arrival of one of the above APDUs before continuing to process the bearer establishment request. If timer T703 expires, the bearer establishment request shall be released. + +NOTE 4 – If the received bearer establishment request contains a bearer identifier value, this value should be used by the CC entity in any future call control signalling relating to this bearer. If call control signalling has already made reference to this bearer, prior to its establishment, using this value, the incoming bearer establishment request should be associated with that bearer reference. + +### **A.3 Additional requirements at a transit CC** + +A transit CC shall relay an alerting or answer indication from the outgoing bearer on to the incoming bearer. + +A transit CC shall relay a release indication from either bearer on to the other bearer, except that a release indication from an outgoing bearer that is in the bearer establishment phase may instead, depending on the cause of release, result in re-routing of the outgoing bearer. + +A transit CC shall pass on any subaddress information from one bearer unchanged to the other bearer. + +A transit CC shall pass on any low layer or high layer compatibility information (e.g. Q.2931 B-HLI, B-LLI, N-HLC, N-LLC or N-BC information elements) from one bearer unchanged to the other bearer. + +A transit CC shall pass on any bearer-related supplementary service information from one bearer, unless acted upon at the network node concerned, unchanged to the other bearer. + +### **A.4 Requirement on call clearing** + +On sending or receiving a callRelease invoke APDU across a call segment, the CC entity shall immediately initiate the release of any bearers across that call segment that are not already in the process of being released. + +# **ANNEX B** + +## **Call description handling requirements for CC signalling service users** + +## **B.1 Call description handling at a CC signalling service user within an originating CC entity** + +When requesting the CC signalling service provider to send a callEstablish invoke APDU, a CC signalling service user within an originating CC shall include a call description containing the following objects: + +Network relevant objects: + +- one Call object, with status mandatory; +- two Call Party End Point objects, one indicated in the Call object as local and identifying the local user, the other indicated in the Call object as remote, and both with status mandatory; +- one Call Party End Point Association object referencing the two Call Party End Point objects, with status conditional; +- optionally one or more Service Component objects, each with status either mandatory or optional. + +End-to-end relevant objects: + +- for each Service Component object, two Participation objects (one per Call Party End Point object), each with status conditional. + +### **B.2 Call description handling at a CC signalling service user within a transit CC entity** + +A CC signalling service user within a transit CC may modify the network relevant objects contained in a call description received in a callEstablish invoke APDU prior to requesting the CC signalling service provider to pass it on in a callEstablish invoke APDU towards the next CC. Modification shall be limited to the following: + +- the removal of one or more objects with status optional; and +- the removal of any objects with status conditional that depend on other objects removed. + +NOTE 1 – This means, for example, that objects cannot be added, objects with status mandatory cannot be deleted, and object attributes cannot be modified. + +If a CC signalling service user within a transit CC is unable to accept the network relevant objects contained in the call description as received and is unable to achieve an acceptable call description by means of modification in accordance with the rules above, it shall reject the call with an appropriate error value, e.g. callDescriptionNotAccepted. + +NOTE 2 – A return error APDU with error value callDescriptionNotAccepted can contain an alternative call description that would be acceptable to the CC signalling service user. + +A CC signalling service user within a transit CC shall not modify a call description passed on in any other APDU (i.e. callEstablish return result or callEstablish return error), nor the callChangedParameter in a callStatus invoke APDU. + +A CC signalling service user within a transit CC shall pass on transparently the end-to-end relevant objects contained in a call description received in a callEstablish invoke APDU. + +### **B.3 Call description handling at a CC signalling service user within a terminating CC entity** + +A CC signalling service user within a terminating CC may modify the end-to-end and network relevant objects contained in call description received in a callEstablish invoke APDU prior to requesting the CC signalling service provider to send back a callEstablish return result APDU. Modification shall be limited to the following: + +- the removal of one or more objects with status optional; and +- the removal of any objects with status conditional that depend on other objects removed. + +NOTE 1 – This means, for example, that objects cannot be added, objects with status mandatory cannot be deleted, and object attributes cannot be modified. + +If a CC signalling service user within a terminating CC is unable to accept the call description as received and is unable to achieve an acceptable call description by means of modification in accordance with the rules above, it shall reject the call with an appropriate error value, e.g. callDescriptionNotAccepted, userBusy, callRejected. + +NOTE 2 – A return error APDU with error value callDescriptionNotAccepted or userBusy can contain an alternative call description that would be acceptable to the CC signalling service user. + +NOTE 3 – One reason for a received call description being unacceptable is that it has been sent by equipment that supports enhanced capabilities beyond the scope of this Recommendation and therefore contains additional objects (e.g. more than two Party End Point objects). + +### **B.4 Call description errors** + +When a call description parameter is received which has one or more unexpected object identifiers or object identifiers with unrecognized attributes (arguments), the receiving entity shall examine the object action indicator, and follow the procedures described in a), b), c), d) or e) below as appropriate. + +If more than one object identifiers and/or object attributes are received in error, only one response shall be given. The response shall be according to the handling of the object action indicator attribute according to the following order of priority: "clearCall" (highest priority), "discardNotify", "discardUnknown", "progressTransit". + +#### a) *Object action indicator attribute = clearCall* + +If the object action indicator attribute is equal to "clear call object model", the call shall be cleared according to the procedures defined in 9.7 except that the Cause information element shall contain the cause "call DescriptionNotAccepted". + +#### b) *If the object action indicator attribute = discardNotify* + +The call description shall be ignored and a *returnError* APDU with error value "callDescriptionNotAccepted" shall be returned. + +#### c) *Object action indicator attribute = discardUnknown* + +If the object action indicator attribute is equal to "discard unknown item and proceed", the unknown item (either the entire object or only the unknown attribute) shall be ignored and the call description shall be processed as if the unknown information was not received. No *returnError* APDU shall be sent. + +#### d) *Object action indicator attribute = progressTransit* + +The unknown object or unknown attribute shall be progressed as an octet string parameter to succeeding call control (if the operation requires so), but shall not be retained by the call control service user once the operation is complete. + +#### e) *Object action indicator attribute = unknown value* + +If an unknown object or unknown attribute has an associated object action indicator that contains an unknown value, then the receiver shall handle the call description as if the object action indicator attribute had been set to "progressTransit". + +### **B.5 End-to-end relevant object handling at a CC signalling service user within a transit CC entity** + +End-to-end relevant objects (service components) shall always be handled by a CC signalling service user within a transit CC entity as unknown objects with an object action indicator attribute set to "progressTransit", regardless of the value that the object action indicator attribute is actually set to. The operation shall always be progressed when this type of object is the only unknown error. + +## **B.6 Changes to the Information Model** + +The Call Control protocol provides a single mechanism to indicate changes to the information model, the Status Call procedure. This procedure provides for a single unconfirmed flow and therefore represents only non-negotiable changes that reflect events that have already happened. The changes to the information model that the CC signalling service user shall indicate using this procedure are: + +- addition and deletion of a service component object; +- changes to the attributes of a party object (i.e. modification of the status of a party); +- changes to the OpenCall attribute of the call object (i.e. modification of the call permissions). + +#### **B.6.1 Deletion of a Service Component Object** + +The deletion of a service component reflects the ability of any user application to discontinue using some portion of an implementation's functionality. Any CC signalling service user at an originating or terminating CC entity can delete a service component in the information model. An attempt to + +delete a service component that does not exist shall not cause an error, but shall be ignored by the CC signalling service user at the peer originating or terminating CC entity. + +#### **B.6.2 Addition of a Service Component Object** + +The addition of a service component using the Status Call procedure reflects the ability of an originating or terminating CC entity to begin using some portion of an implementation's functionality. The Status Call procedure does not support either confirmation or negotiation of this functionality and so it is assumed that this does not place any additional requirements on the bearer. The CC signalling service user at the peer originating or terminating CC entity, receiving an indication of an added service component, may choose to ignore the indication. + +### **B.6.3 Changes to the attributes of the Party Object** + +The changes to the attributes of a party object that the CC signalling service user shall indicate are: + +- changes to the status of a party (e.g. alerting); +- changes to the type of a party. + +The procedures associated with the status call require that the complete party object shall be provided. + +#### **B.6.4 Changes to the Open Call attribute of the Call Object** + +The OpenCall attribute of the call object defines the rights of parties to modify the call by the addition of parties, connections or service components. The permissions provide the requirements for notification and requesting call owner permission. + +The OpenCall parameter contains the following Boolean indications which shall take the values shown: + +- externalPartyAddAllowed: +Value: False. +Usage: Indicates that another party, not currently part of the call, shall not join the call configuration. +- existingPartyAddAllowed: +Value: False. +Usage: Indicates that a non-call owner party shall not introduce another party, not currently part of the configuration, into the call. +- notifyAllPartiesFlag: +Value: True. +Usage: Indicates whether a party successfully joining the call is required to be notified to all the existing members of the call. This indication is provided for future capability and is not currently used. It shall be set to true as this is more restrictive. +- notifyOwnerFlag: +Value: True. +Usage: Indicates whether a party successfully joining the call is required to be notified to the call owner. This indication is provided for future capability and is not currently used. It shall be set to true as this is more restrictive. + +– permissionRequiredFlag: + +Value: True. + +Usage: Indicates whether a party may join the call only after the call owners permission has been sought. This indication is provided for future capability and is not currently used. It is shall be set to true as this is more restrictive. + +– addConnectionAllowed: + +Value: True or False. + +Usage: Indicates whether the non-call owner is permitted to add a connection to an existing call. If the value is set to true then any party may add a connection and also the CC signalling service provider shall refuse any request to change this value from true to false. A change from false to true is permitted. + +– addServiceComponentAllowed: + +Value: True or False. + +Usage: Indicates whether the non-call owner is permitted to add a service component to an existing call. If the value is set to true then any party may add a service component to a connection. The CC signalling service provider shall refuse any request to change this value from true to false. A change from false to true is permitted. + +The call permissions are indicated to the non-call owner as part of the call description during call establishment. The call permissions are not a subject for negotiation and shall not be changed by any CC signalling service user except the call owner CC signalling service user. + +Changes to the call permissions that reduce or restrict the modification rights of non-call owners can result in conflicts. To prevent protocol clashes, any call control protocol service provider shall refuse to accept a request by a CC signalling service user to alter the OpenCall parameter if such an alteration removes a capability already granted. A refusal shall result in the changes to the OpenCall attribute of the call object being ignored and not being passed on to any succeeding CC signalling service user. + +A CC signalling service user that receives a STATUS-CALL indication primitive that alters the call modification permission shall store the new permissions and pass on unchanged the OpenCall parameter towards the next CC using the STATUS-CALL request. + +The CC signalling service user that initiated the call may allow another party to add either connections or service components at call establishment by initiating a call with either the addConnectionAllowed flag set to TRUE or the addServiceComponentAllowed flag to TRUE or both. The CC signalling service user that initiated the call may change the permissions to allow another party to add either connections or service components after call establishment using the call status procedure to change either of the above flags from false to true. The call status procedure shall not be used to change either of the flags from TRUE to FALSE. The call status procedure shall not be used to change any of the other flags in the OpenCall parameter. + +# ANNEX C + +## Interworking + +Interworking occurs with other networks, which do not support the separation of Call Control and Bearer Control or which send simultaneous call and bearer establishment requests. + +Interworking with such networks requires both Call Control and Bearer Control functions in the gateway node at the boundary to these networks. + +The interworking is performed by the CC signalling service user of the Call Control entity in the gateway node. + +## **C.1 Interworking with networks not supporting separation of Call Control and Bearer Control** + +### **C.1.1 Outgoing call establishment** + +In case of an outgoing call establishment to a network which does not support the separation of Call Control and Bearer Control, the Call Control entity in the gateway node shall act as the terminating CC entity for that call. When the call establishment has been accepted by the terminating CC entity in the gateway node, subsequent bearer establishment requests which match with that call shall be forwarded to the other network. + +### **C.1.2 Incoming bearer establishment** + +In case of an incoming bearer establishment from a network which does not support the separation of Call Control and Bearer Control, the establishment can optionally be progressed in accordance with this Recommendation. In this case the Call Control entity in the gateway node shall act as the originating CC entity and initiate establishment of a call, that matches with the required bearer. When the call establishment has been accepted, i.e. after receipt of a callProceeding invoke APDU or callEstablish return result APDU, the bearer establishment shall be progressed. + +### **C.1.3 Addition of bearers to an existing call** + +When a call exists between an originating CC entity and the CC entity in a gateway node to a network which does not support the separation of Call Control and Bearer Control, and a bearer has to be added to that call, the decision as to whether or not the additional bearer is supported is not taken in the gateway, but another bearer establishment shall be made across the other network to the same addressed terminal. + +## **C.2 Interworking with simultaneous call and bearer establishment** + +In this case of interworking the other network supports the separation of Call Control and Bearer Control but only the capability of simultaneous establishment of a call with one bearer is supported. + +### **C.2.1 Outgoing call establishment** + +In case of an outgoing call establishment to a network which only supports simultaneous call and bearer establishment, the Call Control entity in the gateway node shall act as the terminating CC entity for that call. When the call establishment has been accepted by the terminating CC entity in the gateway node and when a subsequent bearer establishment request belonging to that call is received, a simultaneous call and bearer establishment shall be initiated towards the other network. + +### **C.2.2 Incoming call and bearer establishment** + +In case of an incoming call and bearer establishment, the Call Control entity in the gateway node shall act as the originating CC entity and initiate separate establishment of a corresponding call. When the call establishment has been accepted, i.e. after receipt of a callProceeding invoke APDU or callEstablish return result APDU, the bearer establishment shall be progressed. + +### **C.2.3 Addition of bearers to an existing call** + +When a call exists between a CC entity and the CC entity in a gateway node to a network which only supports simultaneous call and bearer establishment, and a bearer in outgoing direction has to be added to that call, the decision as to whether or not the additional bearer is supported is not taken in the gateway, but another bearer establishment shall be made across the other network to the same addressed terminal. If a bearer in incoming direction has to be added to that call, i.e. if an incoming bearer establishment is received, the gateway shall forward it to the corresponding destination. + +# **ANNEX D** + +## **Transport mechanisms** + +This annex lists transport mechanisms which can be used with the call control protocol and specifies how to use them. + +NOTE – This annex is normative but not exclusive, i.e. other reliable transport mechanisms which are not mentioned here can be used as well. + +## **D.1 Connection oriented-Bearer independent** + +The connection oriented-bearer independent (CO-BI) transport mechanism is specified in ITU-T Recommendation Q.2932.1 [8] for the SB and coincident SB/TB reference point. If the CO-BI transport mechanism is chosen, the following shall apply: + +- The operations defined in 8.1 shall be coded in the Facility information element in accordance with ITU-T Recommendation Q.2932.1 [8]. +- The instruction indicator in the Facility information element shall be coded in accordance with ITU-T Recommendation Q.2932.1 [8]. +- The Facility information element shall be conveyed in the messages for the CO-BI transport mechanism as specified in ITU-T Recommendation Q.2932.1 [8]. +- The instruction indicator in the messages for the CO-BI transport mechanism shall be coded in accordance with ITU-T Recommendation Q.2932.1 [8]. + +Additionally for the QB reference point: + +- When conveying the invoke APDU of operations defined in 8.1, the NFE (Network Facility Extension) shall either be omitted or be included. +- When conveying the invoke APDU of operations defined in 8.1, the Interpretation APDU shall either be omitted or be included]. + +## **D.2 Connectionless-Bearer independent** + +The connectionless-bearer independent (CL-BI) transport mechanism is specified in ITU-T Recommendation Q.2932.1 [8] for the SB and coincident SB/TB reference point. If the CL-BI transport mechanism is chosen, the following shall apply: + +- The operations defined in 8.1 shall be coded in the Facility information element in accordance with ITU-T Recommendation Q.2932.1 [8]. + +- The instruction indicator in the Facility information element shall be coded in accordance with ITU-T Recommendation Q.2932.1 [8]. +- The Facility information element shall be conveyed in the FACILITY message for the CL-BI transport mechanism as specified in ITU-T Recommendation Q.2932.1 [8]. +- The instruction indicator in the FACILITY message for the CL-BI transport mechanism shall be coded in accordance with ITU-T Recommendation Q.2932.1 [8]. + +Additionally for the QB reference point: + +- When conveying the invoke APDU of operations defined in 8.1, the NFE (Network Facility Extension) shall either be omitted or be included. +- When conveying the invoke APDU of operations defined in 8.1, the Interpretation APDU shall either be omitted or be included. + +# APPENDIX I + +## **Information flow diagrams** + +This appendix describes some typical information flows for Call Control. The following conventions are used in the figures of this appendix: + +- The figures show APDUs exchanged between CC entities involved in Call Control. Only APDUs relevant to Call Control are shown. +- The figures show protocol states related to the incoming and outgoing side of the call control signalling service provider within a CC entity. +- The figures show the primitives to and from the call control signalling service user within the user CC which correspond to the exchanged APDUs. + +## I.1 Call Establishment using a two-message sequence + +See Figure I.1. + +![Sequence diagram showing call establishment between four Call Controllers (CCs): Originating CC, Transit CC, Transit CC, and Terminating CC. The process involves EST-CALL req, callEstablish inv., callProceeding inv., PROC-CALL req, callEstablish res., and EST-CALL resp messages, transitioning through states like Call Idle, Call Initiated, Call Present, Outg. Call Proceeding, Inc. Call Proc., and Call Active.](3ce04f1c7128814978c6b34d654a25cc_img.jpg) + +``` + +sequenceDiagram + participant OC as Originating CC + participant TC1 as Transit CC + participant TC2 as Transit CC + participant TerC as Terminating CC + + Note left of OC: Call Idle + Note left of TC1: Call Idle + Note left of TC2: Call Idle + Note left of TerC: Call Idle + + OC->>TC1: EST-CALL req (awaitCompleteInd.=FALSE) + Note right of OC: Call Initiated + Note right of TC1: Call Present/ Call Initiated + TC1->>TC2: callEstablish inv. + Note right of TC2: Call Present/ Call Initiated + TC2->>TerC: callEstablish inv. (awaitCompleteInd.=FALSE) + Note right of TerC: EST-CALL ind + Note right of TerC: Call Present + TerC->>OC: PROC-CALL req + Note right of TerC: Incom. Call Proceeding + Note right of TC2: Inc.Call Proc./ Outg. Call Proc. + Note right of TC1: Inc.Call Proc./ Call Initiated + Note right of OC: Outg. Call Proceeding + Note right of OC: PROC-CALL ind + TerC->>TC2: EST-CALL resp + Note right of TerC: Call Active + Note right of TC2: Call Active + TC2->>TC1: callEstablish res. + Note right of TC1: Call Active + TC1->>OC: callEstablish res. + Note right of OC: EST-CALL conf + Note right of OC: Call Active + +``` + +Sequence diagram showing call establishment between four Call Controllers (CCs): Originating CC, Transit CC, Transit CC, and Terminating CC. The process involves EST-CALL req, callEstablish inv., callProceeding inv., PROC-CALL req, callEstablish res., and EST-CALL resp messages, transitioning through states like Call Idle, Call Initiated, Call Present, Outg. Call Proceeding, Inc. Call Proc., and Call Active. + +T11102780-99 + +**Figure I.1/Q.2981 – Example information flow for a successful call establishment using a two-message sequence** + +## I.2 Call Establishment using a three-message sequence + +See Figure I.2. + +![Sequence diagram showing call establishment between four Call Controllers (CCs): Originating CC, Transit CC, Transit CC, and Terminating CC. The process involves EST-CALL, PROC-CALL, and COMP-CALL messages.](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) + +``` + +sequenceDiagram + participant OC as Originating CC + participant TC1 as Transit CC + participant TC2 as Transit CC + participant TerC as Terminating CC + + Note over OC: Call Idle + Note over TC1: Call Idle + Note over TC2: Call Idle + Note over TerC: Call Idle + + OC->>TC1: EST-CALL req (awaitCompleteInd.=TRUE) + Note over OC: Call Initiated + Note over TC1: Call Present/ Call Initiated + TC1->>TC2: callEstablish inv. + Note over TC2: Call Present/ Call Initiated + TC2->>TerC: callEstablish inv. (awaitCompleteInd.=TRUE) + Note over TerC: EST-CALL ind + Note over TerC: Call Present + TerC->>TC2: PROC-CALL req + Note over TC2: Inc.Call Proc./ Outg.Call Proc. + Note over TerC: Incom. Call Proceeding + TC2->>TC1: callProceeding inv. + Note over TC1: Inc.Call Proc./ Outg.Call Proc. + TC1->>OC: callProceeding inv. + Note over OC: Outg. Call Proceeding + Note over OC: PROC-CALL ind + TerC->>TC2: EST-CALL resp + Note over TC2: Aw. Call Compl./ Call Ready + Note over TerC: Await Call Completion + TC2->>TC1: callEstablish res. + Note over TC1: Aw. Call Compl./ Call Ready + TC1->>OC: callEstablish res. + Note over OC: EST-CALL conf + Note over OC: Call Ready + Note over TC1: Call Active + Note over TC2: Call Active + Note over TerC: Call Active + OC->>TC1: COMP-CALL req + Note over OC: Call Active + TC1->>TC2: callComplete inv. + TC2->>TerC: callComplete inv. + Note over TerC: COMP-CALL ind + Note over TerC: Call Active + +``` + +The diagram illustrates the information flow for a successful call establishment using a three-message sequence (EST-CALL, PROC-CALL, COMP-CALL) across four Call Controllers (CCs): Originating CC, Transit CC, Transit CC, and Terminating CC. The sequence starts with the Originating CC sending an EST-CALL req to the first Transit CC. The first Transit CC forwards the callEstablish inv. to the second Transit CC, which then forwards it to the Terminating CC. The Terminating CC responds with EST-CALL resp, which is forwarded back through the Transit CCs to the Originating CC. The Originating CC then sends a COMP-CALL req, which is forwarded through the Transit CCs to the Terminating CC. The Terminating CC responds with COMP-CALL ind. The diagram also shows various intermediate states and messages like PROC-CALL req, callProceeding inv., and callComplete inv. that occur during the establishment process. + +Sequence diagram showing call establishment between four Call Controllers (CCs): Originating CC, Transit CC, Transit CC, and Terminating CC. The process involves EST-CALL, PROC-CALL, and COMP-CALL messages. + +Figure I.2/Q.2981 – Example information flow for a successful call establishment using a three-message sequence + +## I.3 Call Release + +See Figure I.3. + +![Sequence diagram showing the information flow for call release between four Call Controllers (CCs): Originating CC, Transit CC, Transit CC, and Terminating CC. The process starts with the Originating CC sending a REL-CALL req to the first Transit CC. The first Transit CC sends a callRelease inv. to the second Transit CC, which in turn sends a callRelease inv. to the Terminating CC. The Terminating CC sends a REL-CALL ind. back to the second Transit CC. The second Transit CC sends a callRelease res. to the first Transit CC, which sends a callRelease res. back to the Originating CC. The Originating CC sends a REL-CALL conf. back to the first Transit CC. All CCs transition from 'Call Active' to 'Call Idle' after the release process is complete. A label T11102800-99 is present at the bottom right of the diagram.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) + +``` + +sequenceDiagram + participant OC as Originating CC + participant TC1 as Transit CC + participant TC2 as Transit CC + participant TerC as Terminating CC + + Note right of OC: Call Active + Note right of TC1: Call Active + Note right of TC2: Call Active + Note right of TerC: Call Active + + OC-->>TC1: REL-CALL req + TC1->>TC2: callRelease inv. + TC2->>TerC: callRelease inv. + TerC-->>TC2: REL-CALL ind + TC2->>TC1: callRelease res. + TC1->>OC: callRelease res. + OC-->>TC1: REL-CALL conf + Note right of OC: Call Idle + Note right of TC1: Call Idle + Note right of TC2: Call Idle + Note right of TerC: Call Idle + +``` + +T11102800-99 + +Sequence diagram showing the information flow for call release between four Call Controllers (CCs): Originating CC, Transit CC, Transit CC, and Terminating CC. The process starts with the Originating CC sending a REL-CALL req to the first Transit CC. The first Transit CC sends a callRelease inv. to the second Transit CC, which in turn sends a callRelease inv. to the Terminating CC. The Terminating CC sends a REL-CALL ind. back to the second Transit CC. The second Transit CC sends a callRelease res. to the first Transit CC, which sends a callRelease res. back to the Originating CC. The Originating CC sends a REL-CALL conf. back to the first Transit CC. All CCs transition from 'Call Active' to 'Call Idle' after the release process is complete. A label T11102800-99 is present at the bottom right of the diagram. + +**Figure I.3/Q.2981 – Example information flow for call release** + +# APPENDIX II + +## Imported ASN.1 definitions + +Table II.1 is an extract from module Addressing-Data-Elements in Q.932. + +**Table II.1/Q.2981 – Imported ASN.1 Definitions Addressing-Data-Elements** + +``` + +Addressing-Data-Elements {itu-t recommendation q 932 + addressing-data-elements(7)} DEFINITIONS ::= +BEGIN + +EXPORTS + PresentedAddressScreened, PartyNumber, PartySubaddress, + ScreeningIndicator; + +PresentedAddressScreened ::= CHOICE { + presentationAllowedAddress [0] IMPLICIT AddressScreened, + presentationRestricted [1] IMPLICIT NULL, + numberNotAvailableDueToInterworking [2] IMPLICIT NULL, + presentationRestrictedAddress [3] IMPLICIT AddressScreened} + +AddressScreened ::= SEQUENCE { + partyNumber PartyNumber, + screeningIndicator ScreeningIndicator, + partySubaddress PartySubaddress OPTIONAL} + +PartyNumber ::= CHOICE { + unknownPartyNumber [0] IMPLICIT NumberDigits, + -- the numbering plan is the default numbering plan of + -- the network. + +``` + +``` + +-- it is recommended that this value is used. +publicPartyNumber [1] IMPLICIT PublicPartyNumber, +-- the numbering plan is according to Rec. E.163 and +-- E.164 +nsapEncodedNumber [2] IMPLICIT NsapEncodedNumber, +-- ATM endsystem address encoded as an NSAP address +dataPartyNumber [3] IMPLICIT NumberDigits, +-- not used, value reserved +telexPartyNumber [4] IMPLICIT NumberDigits, +-- not used, value reserved +privatePartyNumber [5] IMPLICIT PrivatePartyNumber, +nationalStandardPartyNumber [8] IMPLICIT NumberDigits} + +-- not used, values reserved +PublicPartyNumber ::= SEQUENCE { + publicTypeOfNumber PublicTypeOfNumber, + publicNumberDigits NumberDigits} + +PrivatePartyNumber ::= SEQUENCE { + privateTypeOfNumber PrivateTypeOfNumber, + privateNumberDigits NumberDigits} + +NumberDigits ::= NumericString(SIZE (1..20)) + +PublicTypeOfNumber ::= ENUMERATED { + unknown(0), + -- if used number digits carry prefix indicating type of + -- number according to national recommendations. + internationalNumber(1), nationalNumber(2), + networkSpecificNumber(3), + -- not used, value reserved + subscriberNumber(4), abbreviatedNumber(6)} + +-- valid only for called party number at the outgoing access, +-- network substitutes appropriate number. +PrivateTypeOfNumber ::= ENUMERATED { + unknown(0), level2RegionalNumber(1), level1RegionalNumber(2), + pISNSpecificNumber(3), localNumber(4), abbreviatedNumber(6)} + +NsapEncodedNumber ::= OCTET STRING(SIZE (1..20)) + +PartySubaddress ::= CHOICE { + userSpecifiedSubaddress UserSpecifiedSubaddress, + -- not recommended + nSAPSubaddress NSAPSubaddress} + +-- according to Rec. X.213. +UserSpecifiedSubaddress ::= SEQUENCE { + subaddressInformation SubaddressInformation, + oddCountIndicator BOOLEAN OPTIONAL} + +-- used when the coding of subaddress is BCD +NSAPSubaddress ::= OCTET STRING(SIZE (1..20)) + +-- specified according to X.213. some networks may limit +-- the subaddress value to some other length, e.g. 4 octets. +SubaddressInformation ::= OCTET STRING(SIZE (1..20)) + +-- coded according to user requirements. some networks +-- may limit the subaddress value to some other length, +-- e.g. 4 octets. +ScreeningIndicator ::= ENUMERATED { + userProvidedNotScreened(0), + -- number was provided by a remote user terminal +} + +``` + +``` + +-- equipment, and has been screened by a network that +-- is not the local public or the local private network. +userProvidedVerifiedAndPassed(1), +-- number was provided by a remote user terminal +-- equipment (or by a remote private network), and has +-- been screened by the local public or the local private +-- network. +userProvidedVerifiedAndFailed(2), +-- not used, value reserved. +networkProvided(3) } + +-- number was provided by local public or local private +-- network. +END -- of Addressing-Data-Elements + +``` + +# APPENDIX III + +## Object identifiers defined in this Recommendation + +This appendix lists the object identifier values assigned in this Recommendation and data types, values and macros that are exported from any modules identified by those values. All the object identifiers in this Recommendation are defined using the ITU-T object identifier tree. This means that each object identifier value is assigned in the tree: + +ccObjectIdsTree ::= itu-t recommendation q 2981 + +Table III.1 lists the module number values and the data types, values and Macros which are exported from these modules. + +**Table III.1/Q.2981 – ASN.1 Module Object identifiers used in this Recommendation** + +| Object Identifier | Reference | Notes | +|---------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------------| +| { ccObjectIdsTree cc-operations (1) } | Table 7 | Exports: CcOperations, callSegmentId | +| { ccObjectIdsTree cc-operations-definitions (2) } | Table 7 | | +| { ccObjectIdsTree cc-operations-errors (3) } | Table 7 | | +| { ccObjectIdsTree call-control-object-super-class (4) } | Table 8 | Exports: CALLCONTROLOBJECTCLASS | +| { ccObjectIdsTree call-object-class-definitions (5) } | Table 9 | Exports: call, localPartyEP, remotePartyEP, directCallAssociation, remoteCallAssociation, serviceComponent, BearerId | +| { ccObjectIdsTree cc-object-classes (6) } | Table 9 | | + +# **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.30-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.30-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.30-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.3030-200802-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3030-200802-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/Q/T-REC-Q.3030-200802-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/Q/T-REC-Q.3030-200802-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.3030-200802-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d284f01cae74a24fe7ad8b1848472710bf83f2a --- /dev/null +++ b/marked/Q/T-REC-Q.3030-200802-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a89c687e7d680c1d188347093cbeeabc1be58d7a70a19fe083c196ba33c185e +size 316213 diff --git a/marked/Q/T-REC-Q.3030-200802-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3030-200802-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7eb56cb48cc10d93de16c29d7172d1238c6f875b --- /dev/null +++ b/marked/Q/T-REC-Q.3030-200802-I_PDF-E/raw.md @@ -0,0 +1,556 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3030** + +(02/2008) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Network signalling and control functional architecture + +# --- **Signalling architecture for the NGN service control plane** + +Recommendation ITU-T Q.3030 + +## 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.3030** + +# **Signalling architecture for the NGN service control plane** + +## **Summary** + +Recommendation ITU-T Q.3030 describes the overall signalling architecture for the NGN service control plane including the functional entities, interfaces and protocols. + +### **Source** + +Recommendation ITU-T Q.3030 was approved on 29 February 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 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 1 | +| 6 Service control functions ..... | 2 | +| 7 Service control architecture and interfaces..... | 2 | +| 7.1 Service control functional entities ..... | 4 | +| 7.2 Reference points ..... | 4 | +| 7.3 Reference points and interfaces description ..... | 6 | +| Appendix I..... | 11 | +| Bibliography..... | 12 | + + + +## Recommendation ITU-T Q.3030 + +# Signalling architecture for the NGN service control plane + +# 1 Scope + +This Recommendation describes the overall signalling architecture for the NGN service control plane. It identifies the functional entities (FEs), interfaces, and protocols that are required to model the control plane of the next generation 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 H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*. + +[ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. + +[ITU-T Y.2021] Recommendation ITU-T Y.2021 (2006), *IMS for Next Generation Networks*. + +[ITU-T Y.2031] Recommendation ITU-T Y.2031 (2006), *PSTN/ISDN emulation architecture*. + +# 3 Definitions + +No new definitions are needed. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|--------------------------------------| +| HTTP | HyperText Transfer Protocol | +| MSCML | Media Server Control Markup Language | +| NGN | Next Generation Network | +| PIEA | PSTN/ISDN emulation architecture | +| SIP | Session Initiation Protocol | +| VoiceXML | Voice eXtensible Markup Language | + +All other relevant abbreviations are contained in the above references. + +# 5 Conventions + +None. + +# 6 Service control functions + +The service control functions include call/session control, resource control, registration, and authentication and authorization functions at the service level for both mediated and non-mediated + +services. They may also include functions for controlling media resources, i.e., specialized resources and gateways at the service-signalling level. + +# **7 Service control architecture and interfaces** + +This clause describes the details of the signalling architecture for the NGN service control plane, including the functional entities, interfaces and protocols. This service control architecture supports SIP-based sessions and is independent of services. + +Figure 1 shows the generalized NGN functional architecture as defined in [ITU-T Y.2012]. The service control functional entities are bordered (highlighted) in Figure 1. The signalling architecture for the NGN service control plane is based on the service control functions outlined in clause 6. + +![A complex block diagram of the NGN service control signalling architecture. At the top, 'Applications' connect to 'Application support functions & service support functions'. Below this is a large grey box containing various 'Service control' and 'NACF' (Network Access Control Function) blocks. The 'Service control' section includes functions like S-1 (Serving call session control FE), S-2 (Proxy call session control FE), S-3 (Interrogating call session control FE), S-4 (Subscription locator FE), S-5 (S. user profile FE), S-6 (S. authentication and authorization FE), S-7 (Interconnection border gateway control FE), S-8 (Access GW control FE), S-9 (Media GW control FE), S-10 (Breakout gateway control FE), S-11 (User signalling interworking FE), S-12 (Network signalling interworking FE), S-13 (Media resource control FE), S-14 (Media resource broker FE), and S-15 (General services control FE). The 'NACF' section includes T-1 (Access media gateway FE), T-2 (Access node FE), T-3 (Edge node FE), T-4 (Access relay FE), T-5 (Access border gateway FE), T-6 (Interconnection border gateway FE), T-7 (Trunking media gateway FE), T-8 (Media resource processing FE), T-9 (Signalling gateway FE), T-10 (Network access configuration FE), T-11 (T. authentication & authorization FE), T-12 (T. user profile FE), T-13 (T. location management FE), T-14 (Access management FE), T-15 (Home gateway Configuration FE), T-16 (Policy decision FE), and T-17 (Transport resource control FE). Below these are 'Access transport' and 'Core transport' layers. On the left, 'End-user Function' includes 'Legacy terminal', 'RGW' (Customer network), and 'NGN terminal'. On the right, external networks include 'Other NGN', 'IP multimedia networks', and 'PSTN/ISDN'. A yellow double-headed arrow at the bottom indicates the 'Scope of NGN'.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +A complex block diagram of the NGN service control signalling architecture. At the top, 'Applications' connect to 'Application support functions & service support functions'. Below this is a large grey box containing various 'Service control' and 'NACF' (Network Access Control Function) blocks. The 'Service control' section includes functions like S-1 (Serving call session control FE), S-2 (Proxy call session control FE), S-3 (Interrogating call session control FE), S-4 (Subscription locator FE), S-5 (S. user profile FE), S-6 (S. authentication and authorization FE), S-7 (Interconnection border gateway control FE), S-8 (Access GW control FE), S-9 (Media GW control FE), S-10 (Breakout gateway control FE), S-11 (User signalling interworking FE), S-12 (Network signalling interworking FE), S-13 (Media resource control FE), S-14 (Media resource broker FE), and S-15 (General services control FE). The 'NACF' section includes T-1 (Access media gateway FE), T-2 (Access node FE), T-3 (Edge node FE), T-4 (Access relay FE), T-5 (Access border gateway FE), T-6 (Interconnection border gateway FE), T-7 (Trunking media gateway FE), T-8 (Media resource processing FE), T-9 (Signalling gateway FE), T-10 (Network access configuration FE), T-11 (T. authentication & authorization FE), T-12 (T. user profile FE), T-13 (T. location management FE), T-14 (Access management FE), T-15 (Home gateway Configuration FE), T-16 (Policy decision FE), and T-17 (Transport resource control FE). Below these are 'Access transport' and 'Core transport' layers. On the left, 'End-user Function' includes 'Legacy terminal', 'RGW' (Customer network), and 'NGN terminal'. On the right, external networks include 'Other NGN', 'IP multimedia networks', and 'PSTN/ISDN'. A yellow double-headed arrow at the bottom indicates the 'Scope of NGN'. + +Q.3030(08)\_F01 + +**Figure 1 – Signalling architecture for the NGN service control (Highlighted)** + +## 7.1 Service control functional entities + +The following FEs of the generalized NGN functional architecture are involved with the service control: + +- S-1 Serving call session control functional entity (S-CSC-FE) +- S-2 Proxy call session control functional entity (P-CSC-FE) +- S-3 Interrogating call session control functional entity (I-CSC-FE) +- S-4 Subscription locator functional entity (SL-FE) +- S-5 Service user profile functional entity (SUP-FE) +- S-6 Service authentication and authorization functional entity (SAA-FE) +- S-7 Interconnection border gateway control functional entity (IBC-FE) +- S-8 Access gateway control functional entity (AGC-FE) +- S-9 Media gateway control functional entity (MGC-FE) +- S-10 Breakout gateway control functional entity (BGC-FE) +- S-11 User signalling interworking functional entity (USIW-FE) +- S-12 Network signalling interworking functional entity (NSIW-FE) +- S-13 Media resource control functional entity (MRC-FE) +- S-14 Media resource broker functional entity (MRB-FE) +- S-15 General services control functional entity (GSC-FE). + +For detailed description of these FEs, refer to [ITU-T Y.2012]. + +## 7.2 Reference points + +The following reference points for the service control function are defined: + +- S-1 (S-CSC-FE) – S-3 (I-CSC-FE) +- S-1 (S-CSC-FE) – S-2 (P-CSC-FE) +- S-1 (S-CSC-FE) – S-9 (MGC-FE) +- S-1 (S-CSC-FE) – S-13 (MRC-FE) +- S-1 (S-CSC-FE) – S-10 (BGC-FE) +- S-1 (S-CSC-FE) – S-5 (SUP-FE), S-6 (SAA-FE) +- S-1 (S-CSC-FE) – S-4 (SL-FE) +- S-1 (S-CSC-FE) – S-8 (AGC-FE) +- S-1 (S-CSC-FE) – S-7 (IBC-FE) +- S-2 (P-CSC-FE) – S-3 (I-CSC-FE) +- S-2 (P-CSC-FE) – S-7 (IBC-FE) +- S-2 (P-CSC-FE) – S-11 (USIW-FE) +- S-2 (P-CSC-FE) – S-13 (MRC-FE) +- S-2 (P-CSC-FE) – S-10 (BGC-FE) +- S-3 (I-CSC-FE) – S-7 (IBC-FE) +- S-3 (I-CSC-FE) – S-9 (MGC-FE) +- S-3 (I-CSC-FE) – S-5 (SUP-FE), S-6 (SAA-FE) +- S-3 (I-CSC-FE) – S-4 (SL-FE) + +- S-3 (I-CSC-FE) – S-8 (AGC-FE) +- S-3 (I-CSC-FE) – S-10 (BGC-FE) +- S-7 (IBC-FE)/S-12 (NSIW-FE) – Other NGN/IP multimedia networks +- S-7 (IBC-FE) – S-12 (NSIW-FE) +- S-7 (IBC-FE) – S-10 (BGC-FE) +- S-7 (IBC-FE) – S-13 (MRC-FE) +- S-9 (MGC-FE) – S-10 (BGC-FE) +- S-9 (MGC-FE) – S-13 (MRC-FE) +- S-10 (BGC-FE) – S-10 (BGC-FE) +- S-10 (BGC-FE) – Other NGN/IP multimedia networks +- S-13 (MRC-FE) – S-10 (BGC-FE) +- S-15 (GSC-FE) – S-7 (IBC-FE) +- S-15 (GSC-FE) – S-5 (SUP-FE), S-6 (SAA-FE) +- S-15 (GSC-FE) – S-4 (SL-FE) +- S-15 (GSC-FE) – S-13 (MRC-FE) + +The following reference points between service control function and application support function/service support function (ASF/SSF) are defined: + +- S-1 (S-CSC-FE) – ASF/SSF +- S-4 (SL-FE), S-5 (SUP-FE) – ASF/SSF +- S-6 (SAA-FE) – ASF/SSF +- S-13 (MRC-FE) – ASF/SSF +- S-14 (MRB-FE) – ASF/SSF +- S-15 (GSC-FE) – ASF/SSF + +The following reference points between service control function and transport support function are defined: + +- S-2 (P-CSC-FE) – T-16 (Policy decision functional entity (PD-FE)) +- S-2 (P-CSC-FE) – T-13 (Transport location management functional entity (TLM-FE)) +- S-7 (IBC-FE) – T-6 (Interconnection border gateway functional entity (IBG-FE)) +- S-7 (IBC-FE) – T-16 (Policy decision functional entity (PD-FE)) +- S-8 (AGC-FE) – T-16 (Policy decision functional entity (PD-FE)) +- S-8 (AGC-FE) – T-1 (Access media gateway functional entity (AMG-FE)) +- S-9 (MGC-FE) – T-9 (Signalling gateway functional entity (SG-FE)) +- S-9 (MGC-FE) – T-7 (Trunking media gateway functional entity (TMG-FE)) +- S-13 (MRC-FE) – T-8 (Media resource processing functional entity (MRP-FE)) +- S-15 (GSC-FE) – T-16 (Policy decision functional entity (PD-FE)) + +The following reference points between service control function and end user function are defined: + +- S-2 (P-CSC-FE) – End User Function +- S-11 (USIW-FE) – End User Function +- S-15 (GSC-FE) – End User Function + +## **7.3 Reference points and interfaces description** + +This clause provides a description of the relevant reference points and interfaces specified in clause 7.2. However, description and protocol usage for the reference points and interfaces related to GSC-FE are not specified since the protocols used depend on the type of applications supported. + +#### **7.3.1 S-1 (S-CSC-FE) – S-3 (I-CSC-FE)** + +**S-1 (S-CSC-FE) – S-2 (P-CSC-FE)** + +**S-2 (P-CSC-FE) – S-3 (I-CSC-FE)** + +These reference points allow the communication and forwarding of signalling messaging between CSC-FEs, e.g., during registration and call/session control. + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.2 S-1 (S-CSC-FE) – S-7 (IBC-FE)** + +**S-2 (P-CSC-FE) – S-7 (IBC-FE)** + +**S-3 (I-CSC-FE) – S-7 (IBC-FE)** + +**S-7 (IBC-FE) – S-10 (BGC-FE)** + +These reference points allow communication between a CSC-FE and an IBC-FE, and a BGC-FE and an IBC-FE. + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.3 S-1 (S-CSC-FE) – S-5 (SUP-FE), S-6 (SAA-FE)** + +**S-3 (I-CSC-FE) – S-5 (SUP-FE), S-6 (SAA-FE)** + +These reference points allow information transfer between an S-CSC-FE/I-CSC-FE and an SUP-FE (with or without SAA-FE). + +The main procedures that require information transfer between an S-CSC-FE/I-CSC-FE and an SUP-FE (with or without SAA-FE) are: + +- 1) Procedures related to S-CSC-FE assignment. +- 2) Procedures related to routing information retrieval from an SUP-FE to an S-CSC-FE/I-CSC-FE. +- 3) Procedures related to authorization (e.g., checking of roaming agreement). +- 4) Procedures related to authentication: transfer of security parameters of the subscriber between an SUP-FE and an S-CSC-FE. +- 5) Procedures related to filter control: transfer of filter parameters of the subscriber from an SUP-FE to an S-CSC-FE. + +Interfaces supporting any of the above reference points will use the Diameter (\*) protocol. + +\* Whether other protocols may also be used need to be discussed as ITU-T has not agreed on a protocol for this reference point so far. + +#### **7.3.4 S-1 (S-CSC-FE) – S-4 (SL-FE)** + +**S-3 (I-CSC-FE) – S-4 (SL-FE)** + +These reference points between an S-CSC-FE/I-CSC-FE and an SL-FE are used to retrieve the address of an SUP-FE which holds the user's subscription. The reference points are always used in conjunction with the S-CSC-FE/I-CSC-FE – SUP-FE reference point. + +Interfaces supporting any of the above reference points will use the Diameter (\*) protocol. + +\* Whether other protocols may also be used need to be discussed as ITU-T has not agreed on a protocol for this reference point so far. + +#### **7.3.5 S-1 (S-CSC-FE) – S-10 (BGC-FE)** + +#### **S-3 (I-CSC-FE) – S-10 (BGC-FE)** + +#### **S-2 (P-CSC-FE) – S-10 (BGC-FE)** + +These reference points carry the call/session information between an S-CSC-FE and a BGC-FE for the purpose of interworking with the PSTN. + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.6 S-1 (S-CSC-FE) – S-9 (MGC-FE)** + +#### **S-3 (I-CSC-FE) – S-9 (MGC-FE)** + +The reference points allow the MGC-FE to forward incoming call/session signalling (from the PSTN) to an S-CSC-FE/I-CSC-FE for the purpose of interworking with PSTN networks. + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.7 S-1 (S-CSC-FE) – S-13 (MRC-FE)** + +#### **S-2 (P-CSC-FE) – S-13 (MRC-FE)** + +#### **S-7 (IBC-FE) – S-13 (MRC-FE)** + +These reference points allow interaction between an S-CSC-FE and a MRC-FE. + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.8 S-9 (MGC-FE) – S-10 (BGC-FE)** + +This reference points carry the call/session control information between a BGC-FE and a MGC-FE for the purpose of interworking with the PSTN. + +Interfaces supporting the above reference points will use the SIP protocol. + +#### **7.3.9 S-9 (MGC-FE) – T-7 (TMG-FE)** + +This reference point allows communication between a MGC-FE and a TMG-FE for call/session requests to/from a PSTN. + +Interfaces supporting the above reference point will use the H.248 protocol. + +#### **7.3.10 S-13 (MRC-FE) – T-8 (MRP-FE)** + +This reference point allows a MRC-FE to control media stream resources provided by a MRP-FE. + +Interfaces supporting the above reference point will use the H.248 protocol. + +#### **7.3.11 S-2 (P-CSC-FE) – End user function** + +This reference point supports the communication between an end user function and P-CSC-FE, e.g., related to registration and call/session control. + +Interfaces supporting the above reference point will use the SIP protocol. + +#### **7.3.12 S-2 (P-CSC-FE) – T-16 (PD-FE)** + +#### **S-7 (IBC-FE) – T-16 (PD-FE)** + +#### **S-8 (AGC-FE) – T-16 (PD-FE)** + +These reference points enable transport of application level session information from a P-CSC-FE/IBC-FE/AGC-FE to a PD-FE. Such information includes, but is not limited to: + +- Information to identify the service media/data flow for policy control and/or differentiated charging; +- Media/application bandwidth requirements for QoS control. + +Interfaces supporting any of the above reference points will use the Diameter protocol as indicated in [b-ITU-T Q.3301.1]. + +#### **7.3.13 S-2 (P-CSC-FE) – S-11 (USIW-FE)** + +This reference point allows communication between a P-CSC-FE and USIW-FE. + +Interfaces supporting the above reference point will use the SIP protocol. + +#### **7.3.14 S-11 (USIW-FE) – End user function** + +Access to end user functions not supporting SIP is performed at this reference point, via the USIW-FE. + +#### **7.3.15 S-7 (IBC-FE) – S-12 (NSIW-FE)** + +This reference point allows communication between an IBC-FE and NSIW-FE. + +Interfaces supporting the above reference point will use the SIP protocol. + +#### **7.3.16 S-12 (NSIW-FE) – Other NGN/IP multimedia networks** + +Interconnection with other NGN/IP multimedia networks supporting [b-ITU-T H.323] or a non-compatible version of SIP is performed at this reference point, via the NSIW-FE. + +#### **7.3.17 S-7 (IBC-FE) – T-6 (IBG-FE)** + +This reference point is used by the IBC-FE to control the IBG-FE, e.g., to request network address translation information. + +Interfaces supporting the above reference point will use the H.248 protocol. + +#### **7.3.18 S-8 (AGC-FE) – T-1 (AMG-FE)** + +This reference point is used by the AGC-FE to control the AMG-FE in case of supporting PSTN/ISDN services. + +Interfaces supporting the above reference point will use the H.248 protocol. + +#### **7.3.19 S-7 (IBC-FE) – Other NGN/IP multimedia networks** + +This reference point is an IP interface between an IBC-FE and other NGN/IP multimedia networks. This reference point is used for call/session control with another IP network using SIP. + +Interfaces supporting the above reference point will use the SIP protocol. + +#### **7.3.20 S-10 (BGC-FE) – S-10 (BGC-FE)** + +#### **S-10 (BGC-FE) – Other NGN/IP multimedia networks** + +These reference points allow a BGC-FE to exchange the call/session signalling with another BGC-FE in the same or another network, possibly via an IBC-FE. + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.21 S-1 (S-CSC-FE) – S-8 (AGC-FE)** + +#### **S-3 (I-CSC-FE) – S-8 (AGC-FE)** + +These reference points allow the communication and forwarding of call/session control signalling between an AGC-FE and S-CSC-FE/I-CSC-FE. + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.22 S-9 (MGC-FE) – S-13 (MRC-FE)** + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.23 S-13 (MRC-FE) – S-10 (BGC-FE)** + +Interfaces supporting any of the above reference points will use the SIP protocol. + +#### **7.3.24 S-2 (P-CSC-FE) – T-13 (TLM-FE)** + +This reference point enables a P-CSCF to obtain location information from the TLM-FE of the network attachment control functions (NACFs). + +Interfaces supporting the above reference point will use the Diameter (\*) protocol + +\*Whether other protocols may also be used need to be discussed as ITU-T has not agreed on a protocol for this reference point so far. + +#### **7.3.25 S-9 (MGC-FE) – T-9 (SG-FE)** + +This reference point enables the MGC-FE to exchange SS7 signalling information over IP with the SG-FE, according to the SIGTRAN architecture. + +#### **7.3.26 A-S1: S-14 (MRB-FE) – ASF/SSF** + +This reference point is used for MRB-FE to assign specific media server resources (i.e., MRC-FE and MRP-FE) to incoming calls at the request of service applications of the ASF/SSF. + +Interfaces supporting the above reference point could use SIP, HTTP, SOAP. + +#### **7.3.27 A-S4: S-1 (S-CSC-FE) – ASF/SSF** + +This reference point supports the interactions between the S-CSC-FE and ASF/SSF in order to provide various session-based application services. + +ASF/SSF may interact with the AGC-FE through the S-CSC-FE to provide access to the applications required to support the legacy terminal users. + +Interfaces supporting the above reference point will use SIP. + +#### **7.3.28 A-S5: S-6 (SAA-FE) – ASF/SSF** + +This reference point allows the ASF/SSF to query the SAA-FE the status of authentication, authorization, and accounting of users/terminals while it provides services. + +Interfaces supporting the above reference point will use the Diameter (\*) protocol. + +\*Whether other protocols may also be used need to be discussed as ITU-T has not agreed on a protocol for this reference point so far. + +#### **7.3.29 A-S6: S-4 (SL-FE), S-5 (SUP-FE) – ASF/SSF** + +This reference point allows the ASF/SSF to query subscriber's service profile and/or on the terminal capability information directly from SUP-FE, or indirectly from SUP-FE through SL-FE in case of multiple SUP-FEs. + +Interfaces supporting the above reference point will use the Diameter (\*) protocol. + +\* Whether other protocols may also be used need to be discussed as ITU-T has not agreed on a protocol for this reference point so far. + +#### **7.3.30 S-13 (MRC-FE) – Application support function (ASF)** + +This reference point enables the MRC-FE to interact with the ASF for enhanced services information, e.g., announcement. + +There are multiple protocols/languages and modes of transport options for interfaces supporting this reference point. A particular network provider's service types, equipment, traffic volumes, resource sharing strategies, etc., would determine the particular S-13 (MRC-FE) – ASF interface best options for that network. More than one control protocol/language can be used for the interactive media functionality. Example control protocols/languages for this interface include SIP, HTTP, voice extensible markup language (VoiceXML) and media server control markup language (MSCML). + +## Appendix I + +(This appendix does not form an integral part of this Recommendation) + +The purpose of this appendix is to highlight the relationship between reference points (as defined in various architecture Recommendations) and candidate protocols potentially for use in interfaces supporting these reference points. + +Table I.1 shows the interface mapping tables between ASF/SSF and SCF. It also includes candidate protocols. + +**Table I.1 – Correspondence among reference points of Y.2012, Y.2021, and Y.2031** + +| Y.2012 | Y.2021 and Y.2031
(IMS based PIEA)
| Y.2031 (CS-based
PIEA)
| Protocols | +|---------------------------|-----------------------------------------------|-----------------------------------|------------------| +| A-S1 (MRB-FE – ASF/SSF) | – | – | SIP, SOAP, HTTP | +| A-S3 (MRC-FE – ASF/SSF) | – | – | SIP | +| A-S4 (S-CSC-FE – ASF/SSF) | ISC | I9 | SIP | +| A-S5 (SAA-FE – ASF/SSF) | Sh | – | Diameter | +| A-S6 (SL-FE – ASF/SSF) | Dh | – | Diameter | +| A-S6 (SUP-FE – ASF/SSF) | Sh | I12 | Diameter | +| – | Ma (I-CSCF – AS) | – | SIP | +| – | – | I10 (SSF-ASF/SSF) | INAP/IP | + +# Bibliography + +- [b-ITU-T H.323] Recommendation ITU-T H.323 (2006), *Packet-based multimedia communications systems*. +- [b-ITU-T Q.3301.1] Recommendation ITU-T Q.3301.1 (2007), *Resource control protocol No. 1 – Protocol at the Rs interface between service control entities and the policy decision physical entity*. +- [b-IETF RFC 2616] IETF RFC 2616 (1999), *HyperText Transfer Protocol – HTTP/1.1* <>. +- [b-IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol* <>. +- [b-IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol* <>. +- [b-IETF RFC 5022] IETF RFC 5022 (2007), *Media Server Control Markup Language (MSCML) and Protocol* <>. +- [b-W3C VoiceXML2.0] W3C Recommendation (2004), *Voice Extensible Markup Language (VoiceXML) Version 2.0* <[http://www.w3.org/TR/2004/REC-voice\\_xml20-2004\\_0316](http://www.w3.org/TR/2004/REC-voice_xml20-2004_0316)>. +- [b-W3C VoiceXML2.1] W3C Recommendation (2007), *Voice Extensible Markup Language (VoiceXML) Version 2.1* <[http://www.w3.org/TR/2007/REC-voice\\_xml21-2004\\_0619](http://www.w3.org/TR/2007/REC-voice_xml21-2004_0619)>. + + + +## 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.3040-201008-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..210ca91aa7f5cdbb1e7003dbbe00a55d92c0fb01 --- /dev/null +++ b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/raw.md @@ -0,0 +1,794 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3040** + +(08/2010) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Network signalling and control functional architecture + +# --- **Signalling architecture for IPTV control plane** + +Recommendation ITU-T Q.3040 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +## ITU-T 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.3040 + +# Signalling architecture for IPTV control plane + +# Summary + +Recommendation ITU-T Q.3040 describes the overall signalling architecture for IPTV control plane. It identifies the functions, functional blocks, physical entities, interfaces, and protocols that will model the control plane for IPTV. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.3040 | 2010-08-06 | 11 | + +## Keywords + +Control plane, IPTV, signalling. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|--------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Control architecture and functions..... | 2 | +| 6.1 Functions ..... | 5 | +| 6.2 Functional blocks..... | 5 | +| 6.3 Reference points for NGN non-IMS IPTV architecture..... | 5 | +| 6.4 Reference points for NGN IMS IPTV architecture..... | 5 | +| 7 Physical entities and interfaces in IPTV architecture ..... | 6 | +| 7.1 Mapping functions and functional blocks into physical entities ..... | 7 | +| 7.2 Mapping reference points to interfaces ..... | 8 | +| 8 Protocols used for interfaces..... | 8 | +| 8.1 Interfaces in NGN non-IMS IPTV architecture ..... | 8 | +| 8.2 Interfaces in NGN IMS IPTV architecture..... | 9 | +| 10 Security considerations..... | 9 | +| Appendix I – Functions and reference points of non-NGN IPTV architecture ..... | 10 | +| I.1 Control architecture and functions ..... | 10 | +| I.2 Reference points ..... | 12 | +| Bibliography..... | 16 | + +# **Introduction** + +The service control functions include call/session control, resource control, registration, and authentication and authorization functions at the service level for both mediated and non-mediated services. They may also include functions for controlling media resources, i.e., specialized resources and gateways at the service-signalling level. Recommendation ITU-T Q.3040 describes the overall signalling architecture for the IPTV control plane. It identifies the functions, functional blocks, physical entities, interfaces, and protocols that will model the control plane for IPTV. + +## Recommendation ITU-T Q.3040 + +# Signalling architecture for IPTV control plane + +# 1 Scope + +This Recommendation describes the overall signalling architecture for IPTV control plane. It identifies the functions, functional blocks, physical entities, interfaces, and protocols that will model the control plane for IPTV. + +The interfaces identified in this Recommendation include: + +- interfaces between the service control entities and the IPTV application entities; +- interfaces between the service control entities and the control entities of service transport stratum; +- interfaces between the service control entities and the content delivery entities; +- interfaces between the service control entities and the end user. + +Other interfaces (such as the interfaces between two IPTV application entities, internal interfaces of service transport stratum, etc.) are outside the scope of this Recommendation. + +Appendix I provides functions and reference architecture of non-NGN IPTV architecture which are extracted from [ITU-T Y.1910]. This includes the reference points related and unrelated to service control functions, which may be helpful for the readers. + +# 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 Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*. + +[IETF RFC 2326] IETF RFC 2326 (1998), *Real Time Streaming Protocol (RTSP)*. + +[IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol – HTTP/1.1*. + +[IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol*. + +# 3 Definitions + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +CD&LCF Content Distribution and Location Control Functions + +CD&SF Content Delivery and Storage Functions + +DVBSTP DVB SD&S Transport Protocol + +| | | +|-------|-------------------------------------------------| +| FLUTE | File Delivery over Unidirectional Transport | +| IGMP | Internet Group Management Protocol | +| IMS | IP Multimedia Subsystem | +| IPTV | Internet Protocol TV | +| ITF | Internet Protocol Television Terminal Functions | +| MGCF | Media Gateway Control Function | +| MLD | Multicast Listener Discovery Protocol | +| NACF | Network Attachment Control Functions | +| NGN | Next Generation Networks | +| PE | Physical Entity | +| RACF | Resource and Admission Control Functions | +| RTP | Real-time Transport Protocol | +| SADS | Service and Application Discovery and Selection | +| SC&DF | Service Control and Delivery Functions | +| SCP | Service and Content Protection | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | + +# 5 Conventions + +None. + +# 6 Control architecture and functions + +This clause describes the details of the signalling architecture for IPTV. Figures 6-1 and 6-2 show respectively NGN non-IMS IPTV and NGN IMS IPTV architectural approaches as per [ITU-T Y.1910]. The service control functional entities are bordered (highlighted) in Figures 6-1 and 6-2. + +![Functional architecture diagram of NGN non-IMS IPTV showing layers for End-user functions, Application functions, Content delivery functions, and NGN transport stratum functions with various functional blocks and reference points.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the functional architecture of NGN non-IMS IPTV, organized into four main layers: + +- End-user functions (Left Column):** + - IPTV terminal functions:** + - Application client functions:** SADS client functional block, IPTV application client functional block. + - SCP client functions:** SCP client functions. + - Control client functions:** Control client functional block. + - Content delivery client functions:** Error recovery client functional block, Unicast content delivery client functional block, Multicast content delivery client functional block. + - Home network functions:** Delivery network gateway functional block. +- Application functions (Top Layer):** + - IPTV application functions:** SADS functional block, IPTV application functional block. + - Other functional blocks:** Application profile functional block, Content preparation functions, SCP functions. + - Reference points:** A1, A2, A3, A4, A5, A6, C1, C2, C3, M1. +- Content delivery functions (Middle Layer):** + - Service support functions:** S1, S5, S2, IPTV service control functional block. + - Content distribution and location control functions:** Location control functional block, Distribution control functional block. + - Content delivery and storage functions:** Content delivery control functional block, Cache/storage functional block, Distribution functional block, Error recovery functional block, Content processing functional block, Unicast delivery functional block, Multicast delivery functional block. + - Reference points:** D1, S3, Ud, Mc, Md. +- NGN transport stratum functions (Bottom Layer):** + - Control functions:** Network attachment control functions (NACF), Resource and admission control functions (RACF). + - Transport functions:** Access network functions, Edge functions, Core transport functions, Multicast transport functions (Multicast control point functional block, Multicast replication functional block), Unicast transport functions. + - Reference points:** E0, E1, E2, E3, E4, E5, E6, E7, H1, H2, H3, T1, R1. + +Functional architecture diagram of NGN non-IMS IPTV showing layers for End-user functions, Application functions, Content delivery functions, and NGN transport stratum functions with various functional blocks and reference points. + +Q.3040(10)\_F6-1 + +NOTE – This figure is an exact replica of Figure 11-2 of [ITU-T Y.1910]. + +**Figure 6-1 – Functions and reference points of NGN non-IMS IPTV architecture** + +![Functional architecture diagram of NGN IMS IPTV showing layers for End-user functions, Application functions, Content delivery functions, and NGN transport stratum functions with various functional blocks and reference points.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the functional architecture of NGN IMS IPTV, organized into four main layers: + +- End-user functions (Left Column):** + - IPTV terminal functions:** + - Application client functions: SADS client functional block, IPTV application client functional block. + - SCP client functions. + - Control client functional block. + - Content delivery client functions:** + - Error recovery client functional block. + - Unicast content delivery client functional block. + - Multicast content delivery client functional block. + - Home network functions:** + - Delivery network gateway functional block. +- Application functions (Top Layer):** + - IPTV application functions:** SADS functional block, IPTV application functional block. + - Application profile functional block.** + - Content preparation functions.** + - SCP functions.** +- Content delivery functions (Middle Layer):** + - Content distribution and location control functions:** Location control functional block, Distribution control functional block. + - Content delivery and storage functions:** + - Content delivery control functional block. + - Cache/storage functional block, Distribution functional block. + - Error recovery functional block, Content processing functional block. + - Unicast delivery functional block, Multicast delivery functional block. +- NGN transport stratum functions (Bottom Layer):** + - Service support functions:** S1, S5, S2, IPTV service control functional block, S4. + - Service control functions:** Service user profile functional block. + - Control functions:** Network attachment control functions (NACF), Resource and admission control functions (RACF). + - Transport functions:** + - Access network functions, Edge functions, Core transport functions. + - Multicast transport functions:** Multicast control point functional block, Multicast replication functional block. + - Unicast transport functions.** + +**Reference Points:** + +- E0:** Between IPTV terminal functions and IPTV application functions. +- E1:** Between IPTV application functions and IPTV application client functions. +- E2:** Between IPTV application functions and IPTV service control functional block. +- E3:** Between IPTV application functions and SCP functions. +- E4:** Between IPTV application functions and Content delivery client functions. +- E5:** Between IPTV application functions and NGN transport stratum functions. +- E6:** Between IPTV application functions and IPTV service control functional block. +- E7:** Between IPTV terminal functions and Home network functions. +- A1, A2, A3, A4, A5, A6:** Internal reference points within Application functions. +- C1, C2, C3:** Internal reference points within Content delivery functions. +- D1:** Internal reference point within Content distribution and location control functions. +- S1, S2, S3, S4, S5:** Internal reference points within NGN transport stratum functions. +- T1:** Internal reference point within Transport functions. +- R1:** Internal reference point within Control functions. +- Ud, Mc, Md:** External reference points on the right side of the diagram. +- H1, H2, H3:** Internal reference points within Home network functions. + +Functional architecture diagram of NGN IMS IPTV showing layers for End-user functions, Application functions, Content delivery functions, and NGN transport stratum functions with various functional blocks and reference points. + +Q.3040(10)\_F6-1 + +NOTE – This figure is an exact replica of Figure 11-3 of [ITU-T Y.1910]. + +**Figure 6-2 – Functions and reference points of NGN IMS IPTV architecture** + +## **6.1 Functions** + +Functions identified in Figures 6-1 and 6-2 are described in detail in [ITU-T Y.1910]. + +## **6.2 Functional blocks** + +Functional blocks identified in Figures 6-1 and 6-2 are described in detail in [ITU-T Y.1910]. + +## **6.3 Reference points for NGN non-IMS IPTV architecture** + +The reference points below are for NGN non-IMS IPTV architecture which is depicted in Figure 6-1. + +### **6.3.1 Reference point A1** + +The A1 reference point is between the IPTV application functional block and the IPTV service control functional block. + +### **6.3.2 Reference point E3** + +The E3 reference point is between the control client functional block and the IPTV service control functional block. + +### **6.3.3 Reference point S1** + +The S1 reference point is between the IPTV service control functional block and CD&LCF. + +### **6.3.4 Reference point S2** + +The S2 reference point is between the IPTV service control functional block and the service user profile functional block. + +### **6.3.5 Reference point S3** + +The S3 reference point is between the IPTV service control functional block and RACF. + +### **6.3.6 Reference point S4** + +The S4 reference point is between the IPTV service control functional block and NACF. + +### **6.3.7 Reference point S5** + +The S5 reference point is between the IPTV service control functional block and the content delivery control functional block. + +## **6.4 Reference points for NGN IMS IPTV architecture** + +The reference points below are for NGN IMS IPTV architecture which is depicted in Figure 6-2. + +### **6.4.1 Reference point A0** + +The A0 reference point is between the SADS functional block and core IMS functions. + +### **6.4.2 Reference point A1** + +The A1 reference point is between the IPTV application functional block and the core IMS functions. + +### **6.4.3 Reference point E3** + +The E3 reference point is between the session client functional block and the core IMS functions. + +### **6.4.4 Reference point S1** + +The S1 reference point is between core IMS functions and CD&LCF. + +### 6.4.5 Reference point S2 + +The S2 reference point is between core IMS functions and service user profile functional block. + +### 6.4.6 Reference point S3 + +The S3 reference point is between core IMS functions and RACF. + +### 6.4.7 Reference point S4 + +The S4 reference point is between core IMS functions providing IPTV service control and NACF. + +### 6.4.8 Reference point S5 + +The S5 reference point is between core IMS functions and content delivery control functional block. + +# 7 Physical entities and interfaces in IPTV architecture + +When implementing an IPTV architecture, some of the functional entities identified in clause 6 may be grouped and implemented in a number of physical entities. Figures 7-1 and 7-2 provide examples of how the functional entities could be grouped for both an IMS and non-IMS based NGN. These architectures are used to identify the signalling interfaces that are within the scope of this Recommendation. + +![Diagram of NGN non-IMS IPTV architecture showing physical entities and interfaces.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +The diagram illustrates the physical entities and interfaces for an NGN non-IMS IPTV architecture. It features several functional blocks and their interconnections: + +- End user** (pink vertical rectangle) is connected to the **AF-PE** (blue rectangle) via interface **I'e-a** (dashed line). It is also connected to the **SCF-PE** (yellow rectangle) via interface **I's-e** (dashed line). At the bottom, it connects to the **TCF-PE** (green rectangle) via **I'e-t1** (dashed line) and to the **TF-PE** (green rectangle) via **I'e-t2** (dashed line). +- AF-PE** (blue rectangle) is connected to the **CDF-PE** (orange rectangle) via interface **I'c-a** (solid line). It is also connected to the **SCF-PE** via interface **I's-a** (solid line). +- CDF-PE** (orange rectangle) is connected to the **SCF-PE** via interface **I's-c** (solid line). It is also connected to the **TCF-PE** via interface **I'e-c** (dashed line) and to the **TF-PE** via interface **I'c-t** (dashed line). +- A central yellow box labeled **NGN service stratum functions** contains the **SCF-PE** and **SUP-PE** (yellow rectangle), which are connected to each other via interface **I's-u** (solid line). +- The **SCF-PE** is connected to the **TCF-PE** via interface **I's-t** (solid line). +- A bottom green box labeled **NGN transport stratum functions** contains the **TCF-PE** and **TF-PE** (green rectangle). + +Diagram of NGN non-IMS IPTV architecture showing physical entities and interfaces. + +Q.3040(10)\_F7-1 + +Figure 7-1 – Physical entities and interfaces of NGN non-IMS IPTV architecture + +![Diagram of NGN IMS IPTV architecture showing physical entities and interfaces. The diagram includes End user functions (pink box), AF-PE (blue box), NGN service stratum functions (yellow box containing SCF-PE with Core IMS functions and SUP-PE), CDF-PE (orange box), and NGN transport stratum functions (green box containing TCF-PE and TF-PE). Interfaces are labeled as Is-a, Is-c, Is-u, Is-t, Is-e, Is-t1, Is-t2, Ic-a, Ic-c, Ic-t, Ie-a, Ie-c, Ie-t1, and Ie-t2.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Q.3040(10)\_F7-2 + +Diagram of NGN IMS IPTV architecture showing physical entities and interfaces. The diagram includes End user functions (pink box), AF-PE (blue box), NGN service stratum functions (yellow box containing SCF-PE with Core IMS functions and SUP-PE), CDF-PE (orange box), and NGN transport stratum functions (green box containing TCF-PE and TF-PE). Interfaces are labeled as Is-a, Is-c, Is-u, Is-t, Is-e, Is-t1, Is-t2, Ic-a, Ic-c, Ic-t, Ie-a, Ie-c, Ie-t1, and Ie-t2. + +**Figure 7-2 – Physical entities and interfaces of NGN IMS IPTV architecture** + +## 7.1 Mapping functions and functional blocks into physical entities + +The mapping of functions and functional blocks into physical entities is shown in Table 7-1. + +**Table 7-1 – Mapping functions and functional block into physical entities** + +| Physical entity | Description | Functions and functional blocks included | +|-----------------|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| AF-PE | Physical entity for application function | SADS, IPTV application, SCF functions, application profile, content preparation functions, etc. | +| SCF-PE | Physical entity for service control function | IPTV service control functional block/core IMS functions, service user profile functional block | +| SUP-PE | Physical entity for service user profile | Service user profile functional block | +| CDF-PE | Physical entity for content delivery function | Content distribution and location control functions, content delivery and storage functions | +| TCF-PE | Physical entity for transport control function | Network attachment control functions (NACF), resource and admission control functions (RACF) | +| TF-PE | Physical entity for transport function | Access network functions, edge functions, core transport functions | +| End user | Physical entity for end-user function | Application client functions, session client functional block, SCP client functions, content delivery client functions, home network functions | + +## 7.2 Mapping reference points to interfaces + +The mapping of reference points to interfaces is shown in Table 7-2. + +**Table 7-2 – Mapping reference points to interfaces** + +| NGN non-IMS IPTV architecture | | NGN IMS IPTV architecture | | Interface description | +|-------------------------------|--------------------------|---------------------------|--------------------------|---------------------------------------| +| Interfaces | Mapping reference points | Interfaces | Mapping reference points | | +| I's-a | A1 | Is-a | A0, A1 | Interface between SCF-PE and AF-PE | +| I's-e | E3 | Is-e | E3 | Interface between SCF-PE and end user | +| I's-c | S1, S5 | Is-c | S1, S5 | Interface between SCF-PE and CDF-PE | +| I's-u | S2 | Is-u | S2 | Interface between SCF-PE and SUP-PE | +| I's-t | S3, S4 | Is-t | S3, S4 | Interface between SCF-PE and TCF-PE | + +# 8 Protocols used for interfaces + +## 8.1 Interfaces in NGN non-IMS IPTV architecture + +The interfaces below are in NGN non-IMS IPTV architecture which is depicted in Figure 7-1. + +### 8.1.1 Interface I's-a + +For NGN non-IMS IPTV architecture, interface I's-a will use HTTP as per [IETF RFC 2616]. + +### 8.1.2 Interface I's-e + +For NGN non-IMS IPTV architecture, interface I's-e will use HTTP as per [IETF RFC 2616], and RTSP as per [IETF RFC 2326]. + +### 8.1.3 Interface I's-c + +For NGN non-IMS IPTV architecture, interface I's-c will use RTSP protocol as per [IETF RFC 2326]. + +### 8.1.4 Interface I's-u + +For NGN non-IMS IPTV architecture, interface I's-u will use DIAMETER protocol as per [IETF RFC 3588]. + +### 8.1.5 Interface I's-t + +For NGN non-IMS IPTV architecture, interface I's-t will use DIAMETER protocol as per [IETF RFC 3588]. + +## **8.2 Interfaces in NGN IMS IPTV architecture** + +The interfaces below are in the NGN IMS IPTV architecture which is depicted in Figure 7-2. + +### **8.2.1 Interface Is-a** + +For NGN IMS IPTV architecture, interface Is-a will use SIP as per [b-ETSI TS 124 229], as indicated in [ITU-T Q.1741.6]. + +### **8.2.2 Interface Is-e** + +For NGN IMS IPTV architecture, interface Is-e will use SIP as per [b-ETSI TS 124 229], as indicated in [ITU-T Q.1741.6]. + +NOTE – Is-e interface relates to UNI defined by [b-ITU-T Q.3402]; however, IPTV services are not covered by [b-ITU-T Q.3402]. The relationship is for further study. + +### **8.2.3 Interface Is-c** + +For NGN IMS IPTV architecture, interface Is-c will use SIP as per [b-ETSI TS 124 229], as indicated in [ITU-T Q.1741.6]. + +### **8.2.4 Interface Is-u** + +For NGN IMS IPTV architecture, interface Is-u will use DIAMETER protocol as per [IETF RFC 3588]. + +### **8.2.5 Interface Is-t** + +For NGN IMS IPTV architecture, interface Is-t will use DIAMETER protocol as per [IETF RFC 3588]. + +NOTE – Is-t interface partially relates to Rt interface defined in [b-ITU-T Q.3321.1]. Because some IPTV services use multicast capabilities, [b-ITU-T Q.3321.1] does not cover the multicast capabilities. The relationship is for further study. + +# **10 Security considerations** + +The signalling architecture for IPTV control plane is required to support security mechanisms of session control, as supported by the protocols identified in clause 8. These mechanisms can be applied in both non-IMS and IMS-based IPTV architectures. Other service specific security requirements are out of scope of this Recommendation. + +# **Appendix I** + +## **Functions and reference points of non-NGN IPTV architecture** + +(This appendix does not form an integral part of this Recommendation) + +This appendix provides functions and reference architecture for non-NGN IPTV architecture which are extracted from [ITU-T Y.1910]. This describes all reference points including the reference points related and unrelated to service control functions. + +## **I.1 Control architecture and functions** + +This clause describes the signalling and control plane architecture for non-NGN IPTV. Figure I.1 shows non-NGN IPTV architectural approach as per [ITU-T Y.1910]. + +![Functional architecture diagram of non-NGN IPTV showing layers for End-user functions, Application functions, Service control functions, Content delivery functions, and Network functions with their respective functional blocks and reference points.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +The diagram illustrates the functional architecture of non-NGN IPTV, organized into five main layers: + +- End-user functions (Left Column):** + - IPTV terminal functions:** + - Application client functions:** SADS client functional block, IPTV application client functional block. + - SCP client functions:** Control client functional block. + - Content delivery client functions:** Error recovery client functional block, Unicast content delivery client functional block, Multicast content delivery client functional block. + - Home network functions:** Delivery network gateway functional block. +- Application functions (Top Right):** + - IPTV application functions:** SADS functional block, IPTV application functional block. + - Application profile functional block.** + - Content preparation functions.** + - SCP functions.** +- Service control functions (Middle Left, Yellow):** + - Service user profile functional block.** + - IPTV service control functional block.** +- Content delivery functions (Middle Right, Orange):** + - Content distribution and location control functions:** Location control functional block, Distribution control functional block. + - Content delivery and storage functions:** Content delivery control functional block, Cache/storage functional block, Distribution functional block, Error recovery functional block, Content processing functional block, Unicast delivery functional block, Multicast delivery functional block. +- Network functions (Bottom Right, Green):** + - Authentication and IP allocation functional block.** + - Resource control functional block.** + - Access network functions.** + - Edge functions:** + - Multicast transport functions:** Multicast control point functional block, Multicast replication functional block. + - Unicast transport functions.** + - Core transport functions.** + +**Reference Points:** + +- E0, E1, E2, E3, E4, E5, E6, E7:** Located on the left side, marking interfaces between End-user functions and other layers. +- A1, A2, A3, A4, A5, A6:** Located within the Application functions layer. +- M1, C1, C2, C3:** Located within the Application functions layer. +- S1, S2, S3, S4, S5:** Located within the Service control functions layer. +- D1:** Located within the Content delivery functions layer. +- Ud, Mc, Md:** Located on the right side, marking interfaces between Content delivery functions and Network functions. +- T1, R1:** Located within the Network functions layer. + +Q.3040(10)\_Fi-1 + +Functional architecture diagram of non-NGN IPTV showing layers for End-user functions, Application functions, Service control functions, Content delivery functions, and Network functions with their respective functional blocks and reference points. + +NOTE – This figure is an exact replica of Figure 11-1 of [ITU-T Y.1910]. + +**Figure I.1 – Functions and reference points of non-NGN IPTV architecture** + +### **I.1.1 Functions** + +Functions identified in Figure I.1 are described in detail in [ITU-T Y.1910]. + +### **I.1.2 Functional blocks** + +Functional blocks identified in Figure I.1 are described in detail in [ITU-T Y.1910]. + +## **I.2 Reference points** + +The following reference points are those identified in [ITU-T Y.1910]. + +#### **I.2.1 Reference point A1** + +The A1 reference point is between the IPTV application functional block and the IPTV service control functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use HTTP as per [IETF RFC 2616]. + +#### **I.2.2 Reference point A2** + +The A2 reference point is between the IPTV application functional block and the content distribution and location control functions (CD&LCF). + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +### **I.2.3 Reference point A3** + +The A3 reference point is between the IPTV application functional block and the content preparation functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.4 Reference point A4** + +The A4 reference point is between the SADS functional block and the application profile functional block that is used by the SADS functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.5 Reference point A5** + +The A5 reference point is between the IPTV application functional block and the application profile functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.6 Reference point A6** + +The A6 reference point is between the IPTV application functional block and SCP functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.7 Reference point C1** + +The C1 reference point is between the content preparation functions and the content distribution and location control functions (CD&LCF). + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.8 Reference point C2** + +The C2 reference point is between the content preparation functions and the content delivery and storage functions (CD&SF). + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.9 Reference point C3** + +The C3 reference point is between the content preparation functions and the SCP functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.10 Reference point E0** + +The E0 reference point is between the ITF SADS client functional block and the SADS functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use DVBSTP as per [b-ETSI TS 102 034], HTTP as per [IETF RFC 2616], or FLUTE as per [b-IETF RFC 3926]. + +#### **I.2.11 Reference point E1** + +The E1 reference point is between the ITF application client functional block and the IPTV application functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use HTTP as per [IETF RFC 2616]. + +#### **I.2.12 Reference point E2** + +The E2 reference point is between the SCP client functions and the SCP functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.13 Reference point E3** + +The E3 reference point is between the control client functional block and the IPTV service control functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use HTTP, as per [IETF RFC 2616], or RTSP as per [IETF RFC 2326]. + +#### **I.2.14 Reference point E4** + +The E4 reference point is between error recovery functional block and error recovery client functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.15 Reference point E5** + +The E5 reference point is between the multicast content delivery client functional block and the multicast control point functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use IGMP V3 as per [b-IETF RFC 3376] or MLDv2 as per [b-IETF RFC 3810]. + +#### **I.2.16 Reference point E6** + +The E6 reference point is between the unicast content delivery client functional block and the content delivery control functional blocks. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use RTSP as per [IETF RFC 2326]. + +#### **I.2.17 Reference point H1** + +The H1 reference point is between the delivery network gateway functional block and the authentication and IP allocation functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.18 Reference point H2** + +The H2 reference point provides multicast-based IP connectivity between delivery network gateway functional blocks. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use MPEG-2 TS over RTP over UDP as per [b-ETSI TS 102 034], [b-IETF RFC 3550] and [b-IETF RFC 768]. + +#### **I.2.19 Reference point H3** + +The H3 reference point provides unicast-based IP connectivity between the delivery network gateway functional block and the access network functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use: + +- MPEG-2 TS over RTP over UDP as per [b-ETSI TS 102 034], [b-IETF RFC 3550] and [b-IETF RFC 768] for content flow streams. +- TCP as per [b-IETF RFC 793] for file delivery. + +#### **I.2.20 Reference point M1** + +The M1 reference point is between SCP functions and the application profile functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.21 Reference point Md** + +The Md reference point is between the multicast delivery functional block and the multicast transport functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point will use RTP over UDP as per [b-IETF RFC 3550] and [b-IETF RFC 768]. + +#### **I.2.22 Reference point R1** + +The R1 reference point is between the resource control functional block and the network transport functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.23 Reference point S1** + +The S1 reference point is between the IPTV service control functional block and CD&LCF. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.24 Reference point S2** + +The S2 reference point is between the IPTV service control functional block and the service user profile functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.25 Reference point S3** + +The S3 reference point is between the IPTV service control functional block and the resource control functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.26 Reference point S4** + +The S4 reference point is between the IPTV service control functional block and the authentication and IP allocation functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.27 Reference point S5** + +The S5 reference point is between the IPTV service control functional block and the content delivery control functional block. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.28 Reference point T1** + +The T1 reference point is between the authentication and IP allocation functional block and access network functions. + +For non-NGN IPTV architecture, interfaces supporting this reference point are for further study. + +#### **I.2.29 Reference point Ud** + +The Ud reference point is between the unicast delivery functional block and the unicast transport functions. + +The same protocols indicated for reference point H3 apply at reference point Ud. + +# Bibliography + +- [b-ITU-T Q.3321.1] Recommendation ITU-T Q.3321.1 (2010), *Resource control protocol No. 1 version 2 – Protocol at the Rs interface between service control entities and the policy decision physical entity.* +- [b-ITU-T Q.3402] Recommendation ITU-T Q.3402 (2008), *NGN UNI signalling profile (Protocol set 1).* +- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services.* +- [b-IETF RFC 768] IETF RFC 768 (1980), *User Datagram Protocol.* +- [b-IETF RFC 793] IETF RFC 793 (1981), *Transmission Control Protocol.* +- [b-IETF RFC 3376] IETF RFC 3376 (2002), *Internet Group Management Protocol, Version 3.* +- [b-IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications.* +- [b-IETF RFC 3810] IETF RFC 3810 (2004), *Multicast Listener Discovery Version 2 (MLDv2) for IPv6.* +- [b-IETF RFC 3926] IETF RFC 3926 (2004), *FLUTE – File Delivery over Unidirectional Transport.* +- [b-ETSI TS 102 034] ETSI TS 102 034 V1.3.1 (2007), *Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks.* +- [b-ETSI TS 124 229] ETSI TS 124 229 V8.6.0 (2009), *Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3.* + + + +## 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.3053-201703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3053-201703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9 --- /dev/null +++ b/marked/Q/T-REC-Q.3053-201703-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.3053-201703-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.3053-201703-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8988e212cac8bf8624cf39f1e4ae82a79e16587b --- /dev/null +++ b/marked/Q/T-REC-Q.3053-201703-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d493479666c13025726145bc1ce1df218941aff42f8d79a47e954a90859a1224 +size 47680 diff --git a/marked/Q/T-REC-Q.31-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.31-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fe89462c28670c70b705a1557d2be5ca9f61eb6e --- /dev/null +++ b/marked/Q/T-REC-Q.31-198811-I_PDF-E/raw.md @@ -0,0 +1,46 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.31** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**NOISE IN A NATIONAL 4-WIRE AUTOMATIC +EXCHANGE** + +**ITU-T Recommendation Q.31** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.31 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. + +## **Recommendation Q.31** + +## **NOISE IN A NATIONAL 4-WIRE AUTOMATIC EXCHANGE** + +It is desirable that the requirements concerning noise conditions for a national 4-wire automatic exchange be the same as for an international exchange (see Recommendation Q.45, § 5). \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a482f334200fb7778bcfb59d8f391161c8b573d7 --- /dev/null +++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/raw.md @@ -0,0 +1,557 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3203** + +(08/2011) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +Signalling requirements and protocols for the NGN – +Signalling and control requirements and protocols to +support attachment in NGN environments + +## --- **Signalling requirements and architecture of network attachment control functions to support IP mobility** + +Recommendation ITU-T Q.3203 + +## 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.3203 + +## Signalling requirements and architecture of network attachment control functions to support IP mobility + +## Summary + +The addition of IP mobility in access networks impacts the functionality of network attachment control functions (NACF), and raises additional signalling requirements of NACF with respect to the mechanism of IP address management and the signalling flows for mobility interface. Recommendation ITU-T Q.3203 proposes the generic signalling requirements and architecture for NACF functionality defined in Recommendation ITU-T Y.2014, with considerations of interfacing the mobility management functions described in Recommendation ITU-T Y.2018. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.3203 | 2011-08-06 | 11 | + +## Keywords + +IP mobility, NACF, NGN, signalling. + +## 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 Definition..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Overview of protocol supporting IP mobility on the NGN access network..... | 3 | +| 6.1 Network architecture ..... | 3 | +| 6.2 Host configuration ..... | 4 | +| 6.3 Handover management..... | 4 | +| 7 Mobility signalling requirements of NACF..... | 4 | +| 7.1 Data structure..... | 4 | +| 7.2 Movement detection ..... | 5 | +| 7.3 Location registration..... | 5 | +| 8 NACF signalling architecture and interfaces for IP mobility..... | 6 | +| 8.1 Functional entities of NACF ..... | 6 | +| 8.2 Relevant reference points ..... | 6 | +| 8.3 Interface description ..... | 7 | +| 9 Security considerations..... | 8 | +| Appendix I – Mapping to IETF mobility architecture ..... | 9 | +| Appendix II – Mapping to PMIP domain ..... | 10 | +| Appendix III – Mapping IPv6 user configuration for the mobility service ..... | 11 | +| III.1 Initial allocation of IP address ..... | 11 | +| III.2 Interaction with DHCP relay agent ..... | 11 | +| III.3 IPv6 address autoconfiguration ..... | 11 | +| Bibliography..... | 14 | + + + +## Recommendation ITU-T Q.3203 + +## Signalling requirements and architecture of network attachment control functions to support IP mobility + +# 1 Scope + +This Recommendation describes signalling architecture and relevant interfaces of network attachment control functions (NACF) to support IP mobility in access networks, considering interaction with signalling and functionality of mobility management and control functions (MMCF) defined in [ITU-T Y.2018]. Additional signalling requirements of NACF are identified to support IP mobility in next generation access (NGA) networks, with respect to the mechanism of IP address management and the signalling flows for mobility interface. This Recommendation addresses the signalling requirements and architecture of NACF for mobility service based on [ITU-T Y.2014]. Mobility signalling of other functions (such as MMCF and resource and admission control functions (RACF)) is out of the scope of this Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Q.1706] Recommendation ITU-T Q.1706/Y.2801 (2006), *Mobility management requirements for NGN*. +- [ITU-T Q.1707] Recommendation ITU-T Q.1707/Y.2804 (2008), *Generic framework of mobility management for next generation networks*. +- [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*. +- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. +- [IETF RFC 4862] IETF RFC 4862 (2007), *IPv6 Stateless Address Autoconfiguration*. + +# 3 Definition + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **handover**: [ITU-T Q.1706]. +- 3.1.2 **host-based mobility**: [ITU-T Y.2018]. +- 3.1.3 **network-based mobility**: [ITU-T Y.2018]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 mobility signalling:** Signalling flows for delivering information related to location registration and handover management to support the mobility service. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----------|----------------------------------------------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| AM-FE | Access Management Functional Entity | +| AR-FE | Access Relay Functional Entity | +| CoA | Care of Address | +| CPE | Customer Premises Equipment | +| DHCP | Dynamic Host Configuration Protocol | +| EUI | Extended Unique Identifier | +| HA | Home Agent | +| HCF | Handover Control Function | +| HDC-FE | Handover Decision and Control Functional Entity | +| HDF | Handover Decision Function | +| HoA | Home Address | +| IP | Internet Protocol | +| LMA | Local Mobility Anchor | +| MAG | Mobile Access Gateway | +| MIPv4 | Mobile IP for IPv4 | +| MIPv6 | Mobile IP for IPv6 | +| MLM-FE | Mobile Location Management Functional Entity | +| MLM-FE(C) | An instance of the MLM-FE performing the central mobile location management role | +| MLM-FE(P) | An Instance of the MLM-FE performing the proxy mobile location management role | +| MMCF | Mobility Management and Control Function | +| MN | Mobile Node | +| NACF | Network Attachment Control Functions | +| NAC-FE | Network Access Configuration Functional Entity | +| NGN | Next Generation Network | +| NID-FE | Network Information Distribution Functional Entity | +| PIA | Persistent IP Address | +| PMIP | Proxy Mobile IP | +| PMIPv6 | Proxy MIPv6 | + +| | | +|--------|--------------------------------------------------------------| +| RA | Router Advertisement | +| RACF | Resource and Admission Control Functions | +| TAA-FE | Transport Authentication and Authorization Functional Entity | +| TIA | Temporary IP Address | +| TLM-FE | Transport Location Management Functional Entity | +| TUP-FE | Transport User Profile Functional Entity | +| UE | User Equipment | + +# 5 Conventions + +This Recommendation does not use specific conventions. + +# 6 Overview of protocol supporting IP mobility on the NGN access network + +This Recommendation describes the signalling requirements and architecture of the network attachment control function (NACF) for both host- and network-based mobility management that rely on the signalling and functionality of the mobility management and control function (MMCF) added to support mobility management in the next generation network (NGN) transport stratum. NACF gives information about mobility management to MMCF, which is responsible for mobile location management and handover control. + +In the IETF-based network architecture, two entities are generally considered to support IP mobility: a home agent (HA) and an access gateway. The home agent manages IP addresses in addition to mobile-user profiles, and it delivers packets to mobile nodes (MN). In the case of network-based mobility management, the access gateway detects a user's movement to a new network and registers the user's care of address (CoA) with the HA. This approach does not require any additional protocol for the MN to support IP mobility. However, in the case of host-based mobility management, users have to configure their new CoA. Whenever a user moves to a new network, the user configures its CoA and then registers it with the home agent. Appendix I describes the network architecture based on IETF mobile protocols. + +The NGN mobility architecture, including components of NACF and MMCF, possibly applies to the general mobility architecture. In the NGN architecture model, NACF is responsible for allocating the IP address and performing authentication. NACF allocates two kinds of IP addresses: a persistent IP address (PIA) and a temporary IP address (TIA), and updates the UE's temporary IP address with the MMCF for mobility service. The NACF can optionally perform an authentication process when the UE changes network. + +## 6.1 Network architecture + +The MMCF defined in [ITU-T Y.2018] is required for mobility service in the NGN transport stratum [ITU-T Q.1707]. Also, mobility-specific transport functions are needed in the forwarding plane of the transport stratum, as shown in Figure 6.1. In the control plane, NACF has interaction with MMCF to transfer mobility service parameters. + +![Diagram illustrating the relationship between NACF and MMCF for IP mobility. The diagram shows a Network attachment control function (NACF) on the left, a Mobile Management Control Function (MMCF) in the center, and a User Equipment (UE) at the bottom. The MMCF is divided into a Control plane (containing C-MMCF and A-MMCF) and a Forwarding plane (containing a Transport function). The UE is connected to the Transport function. The NACF is connected to the C-MMCF via MM signalling (dashed blue arrows). The UE is connected to the C-MMCF via MM signalling (dashed blue arrows). The C-MMCF is connected to the A-MMCF via MM signalling (dashed blue arrows). The A-MMCF is connected to the Transport function via Control plane (dashed blue arrows). The Transport function is connected to the Other NGN (dashed blue arrows). The UE is connected to the Transport function via User data transport (solid green arrows). The Transport function is connected to the Other NGN via User data transport (solid green arrows). A legend at the bottom indicates that dashed blue arrows represent MM signalling and solid green arrows represent User data transport. The diagram is labeled Q.3203(11)_F6.1.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Diagram illustrating the relationship between NACF and MMCF for IP mobility. The diagram shows a Network attachment control function (NACF) on the left, a Mobile Management Control Function (MMCF) in the center, and a User Equipment (UE) at the bottom. The MMCF is divided into a Control plane (containing C-MMCF and A-MMCF) and a Forwarding plane (containing a Transport function). The UE is connected to the Transport function. The NACF is connected to the C-MMCF via MM signalling (dashed blue arrows). The UE is connected to the C-MMCF via MM signalling (dashed blue arrows). The C-MMCF is connected to the A-MMCF via MM signalling (dashed blue arrows). The A-MMCF is connected to the Transport function via Control plane (dashed blue arrows). The Transport function is connected to the Other NGN (dashed blue arrows). The UE is connected to the Transport function via User data transport (solid green arrows). The Transport function is connected to the Other NGN via User data transport (solid green arrows). A legend at the bottom indicates that dashed blue arrows represent MM signalling and solid green arrows represent User data transport. The diagram is labeled Q.3203(11)\_F6.1. + +**Figure 6.1 – Relationship between NACF and MMCF for IP mobility +(see [ITU-T Q.1707] and [ITU-T Y.2014])** + +## 6.2 Host configuration + +The UE initially sets its persistent IP address (PIA) with either a stateless or a stateful configuration. When using a stateless configuration, known as autoconfiguration based on [IETF RFC 4862], the UE builds an EUI-64-formatted IPv6 address using a network prefix contained in router advertisements (RAs) from transport function. In a stateful configuration, the IP address for PIA is obtained from a DHCP server. When an attachment between NACF and the mobile UE initially occurs, its PIA configuration is executed. Once a mobile UE has configured its IP address, it maintains its IP address within a home-agent domain. In the case of host-based mobility, the mobile node has to configure its temporary IP address (TIA) in addition to its PIA, while in the case of network-based mobility, the mobile node has its PIA maintained as user profile information. Whenever the mobile node is attached to a different access network, the mobile UE configures its TIA in a stateful or stateless manner (see clause 7.3.1). + +During the attachment process, mobility authentication is also performed between the mobile UE and the NACF. Either the pre-authentication or the re-authentication method may be used to reduce authentication latency. In a host-based mobility case, the information derived from the UE authentication process is transferred from NACF to MMCF. Otherwise, NACF indicates the network-based mobility service to MMCF. + +## 6.3 Handover management + +The MMCF has handover control functions (HCFs) which provide session continuity for the mobile UE's sessions. The HCF concentrates on minimizing data loss and handover latency during the UE's movement. Also, the forwarding plane of the transport stratum performs the handover execution function to support IP mobility. + +# 7 Mobility signalling requirements of NACF + +## 7.1 Data structure + +The mobility service parameters required to extend NACF for IP mobility are defined in [ITU-T Y.2014]; mobility service parameters consist of MLM-FEs' addresses, keying material, mobility protocol type (e.g., host-based or network-based mobility), an optional anchor point address, and an optional tunnel end point address. + +In the access authentication procedure, shown in Figure 7, AM-FE obtains an identifier from a UE and requests a mobile UE's authentication to TAA-FE. TAA-FE receives the mobile UE's policy profile from TUP-FE through Nb reference point. A user profile may be downloaded from + +the TAA-FE server in the home NGN network to the TAA-FE proxy in the visited NGN network. The TAA-FE responds to the AM-FE with the mobile node's policy profile. User data related to network location information in the policy profile may be transferred between TAA-FE and TLM-FE via the Nc reference point. + +![Sequence diagram showing NACF information flow for access authentication. The diagram involves five entities: AM-FE, TAA-FE proxy, TLM-FE, TAA-FE server, and TUP-FE. The sequence of messages is: 1. AM-FE sends an AAA request (MN-ID) to TAA-FE proxy. 2. TAA-FE proxy sends an AAA reply + policy profile to AM-FE. 3. TAA-FE proxy sends network location information to TLM-FE. There are also internal messages between TAA-FE server and TUP-FE, and between TAA-FE proxy and TAA-FE server. A label Q.3203(11)_F07 is present at the bottom right.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +``` + +sequenceDiagram + participant AM-FE + participant TAA-FE proxy + participant TLM-FE + participant TAA-FE server + participant TUP-FE + + AM-FE->>TAA-FE proxy: 1. AAA request (MN-ID) + TAA-FE proxy->>TAA-FE server: + TAA-FE server->>TUP-FE: + TUP-FE->>TAA-FE server: + TAA-FE server->>TAA-FE proxy: + TAA-FE proxy->>AM-FE: 2. AAA reply + policy profile + TAA-FE proxy->>TLM-FE: 3. Network location information + +``` + +Sequence diagram showing NACF information flow for access authentication. The diagram involves five entities: AM-FE, TAA-FE proxy, TLM-FE, TAA-FE server, and TUP-FE. The sequence of messages is: 1. AM-FE sends an AAA request (MN-ID) to TAA-FE proxy. 2. TAA-FE proxy sends an AAA reply + policy profile to AM-FE. 3. TAA-FE proxy sends network location information to TLM-FE. There are also internal messages between TAA-FE server and TUP-FE, and between TAA-FE proxy and TAA-FE server. A label Q.3203(11)\_F07 is present at the bottom right. + +**Figure 7 – NACF information flow for access authentication** + +## 7.2 Movement detection + +Handover decision can be made by either the mobile node or the handover decision and control functional entity (HDC-FE) in MMCF. After the network attachment point is determined, the mobile node performs authentication for the target access network. When a user attaches to the target network, AM-FE forwards the user's authentication request to TAA-FE. + +NACF may provide pre-authentication and re-authentication to reduce the handover latency. The user transport profile and mobility service parameters are sent from the TAA-FE in the home network to the TAA-FE in the target network. The mobility service parameters include the UE's PIA and the address of the MLM-FE (C). TAA-FE delivers mobility service parameters, including the keying material used between the mobile user and the MLM-FE (P), to TLM-FE. + +## 7.3 Location registration + +### 7.3.1 IP address allocation + +During the authentication procedure, TAA-FE may request an IP address allocation to NAC-FE or use the IP address of user profile information in TUP-FE. After authentication, the user profile, including mobility service parameters, is delivered to TLM-FE. In the case of network-based mobility, only an IP address maintained in TUP-FE is used for IP configuration, and in the case of host-based mobility, NAC-FE delivers the allocated IP address to TLM-FE. + +To communicate between the user and MLM-FE (P) in the target network, TLM-FE provides the address of the MLM-FE (P) as well as the user's IP address and keying material for the security associations between the user and MLM-FE (P), as well as HDC-FE and NID-FE. The TLM-FE stores the association between the allocated IP address and related network location information, including the mobility service parameters. TLM-FE also delivers mobility service parameters to NAC-FE after notification of binding information to MLM-FE. + +### 7.3.2 Notification of binding information + +In the host-based mobility service, a mobile node directly updates location information to MLM-FE (P). NAC-FE may bind the information between the mobility service subscriber ID and the persistent/temporary IP addresses. TLM-FE then sends the binding information to the MLM-FE (P): the user identity, the type of mobility service, and keying materials. However, TLM-FE delivers the indication of network-based mobility without keying material to MLM-FE (P). In the case of network-based mobility, the user has only the persistent address and no security association with MLM-FE (P). + +# 8 NACF signalling architecture and interfaces for IP mobility + +This clause describes the details of the NACF signalling architecture for IP mobility, including the functional entities and interfaces. + +Figure 8.1 shows reference points between NACF and MMCF as defined in [ITU-T Y.2018]. + +![Figure 8.1 – Functional entities and reference points of NACF. The diagram shows the internal functional entities of the NACF and their interfaces with the MMCF. The NACF contains T-15 (Home gateway configuration FE), T-12 (T. User profile FE), T-11 (T. Authentication and authorization FE), T-10 (Network access configuration FE), T-14 (Access management FE), and T-13 (T. Location management FE). External reference points include S-TC1, TC-Ux, TC-T1, and TC-TC1. Internal interfaces are Nb, Nc, Nk, Na, Nd, and Ne. External interfaces to MMCF are M1, M2, and M13. The MMCF contains MLM-FE (P), MLM-FE (C), HDC-FE, NID-FE, and NIRF.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 8.1 – Functional entities and reference points of NACF. The diagram shows the internal functional entities of the NACF and their interfaces with the MMCF. The NACF contains T-15 (Home gateway configuration FE), T-12 (T. User profile FE), T-11 (T. Authentication and authorization FE), T-10 (Network access configuration FE), T-14 (Access management FE), and T-13 (T. Location management FE). External reference points include S-TC1, TC-Ux, TC-T1, and TC-TC1. Internal interfaces are Nb, Nc, Nk, Na, Nd, and Ne. External interfaces to MMCF are M1, M2, and M13. The MMCF contains MLM-FE (P), MLM-FE (C), HDC-FE, NID-FE, and NIRF. + +**Figure 8.1 – Functional entities and reference points of NACF** + +## 8.1 Functional entities of NACF + +The following FEs of NACF are involved in the mobility service: + +- T-10 Network access configuration functional entity (NAC-FE) +- T-11 Transport authentication and authorization functional entity (TAA-FE) +- T-13 Transport location management functional entity (TLM-FE) + +In order to support mobility defined in [ITU-T Y.2014], NAC-FE allocates two kinds of IP addresses to UE: persistent IP address (PIA) and temporary IP address (TIA). NAC-FE allocates IP addresses in association with TAA-FE, when the address allocation is needed during the UE's movement, in order to provide authentication. + +TAA-FE may request NAC-FE to allocate an IP address in the case of host-based mobility, and it may use an IP address or IP prefix as user-profile information maintained in TUP-FE in both host-based and network-based mobility cases (see clause 7.2.4 of [ITU-T Y.2014]). + +TLM-FE identifies the current network location of UE and keeps track of it. When the point of attachment is changed in the network, the TLM-FE updates the association between the IP address allocated to the UE and related network location information (see clause 7.2.3 of [ITU-T Y.2014]). + +## 8.2 Relevant reference points + +The following external reference points between NACF and MMCF are defined for the mobility service: + +- M1 (TLM-FE, MLM-FE) +- M2 (TLM-FE, HDC-FE) +- M13 (TLM-FE, NID-FE) + +The following internal reference points of NACF are extensively defined for mobility service: + +- Nc (TAA-FE, TLM-FE) +- Ne (NAC-FE, TLM-FE) + +## 8.3 Interface description + +This clause provides the description of the relevant reference points and interfaces listed in clause 8.2. + +### 8.3.1 M1 + +This reference point is for the distribution of information from TLM-FE to MLM-FE (P). The information is prepared through the internal procedures of NACF, as follows: + +- 1) TLM-FE obtains persistent/temporary address from NAC-FE. +- 2) TAA-FE delivers the profile information, including mobility-service parameters as well as the address of MLM-FE (P), to the TLM-FE. +- 3) In the case of host-based mobility, TLM-FE obtains keying material from TAA-FE for the security associations between UE and MLM-FE (P). +- 4) In the case of network-based mobility, TLM-FE obtains the address of MLM-FE(C) and the address of tunnel end-point from TAA-FE. + +TLM-FE informs MLM-FE (P) of mobile-user ID, persistent-IP address, and anchor-point address (the tunnel-end-point address) in addition to the information listed from 1 to 4. Optionally, binding information between the mobility-service-user ID and persistent-IP address, as well as the type of mobility protocol (e.g., host-based or network-based mobility service) can be included in the information. + +### 8.3.2 M2 + +This reference point is for providing information from TLM-FE to HDC-FE, to support the security association required between the handover decision function (HDF) and the UE. The TLM-FE sends information including mobility-service-user ID and keying material to the HDC-FE. + +The M2 interface is used for information flow providing the keying material derived from the UE authentication procedure. + +### 8.3.3 M13 + +This reference point is for providing information from TLM-FE to the network information distribution functional entity (NID-FE) to support the security association. The TLM-FE sends information to the NID-FE, including mobility-service-user ID and keying material. + +M13 interface is used for the information flow providing the keying material derived from the UE authentication procedure. + +### 8.3.4 Nc + +The Nc reference point, between TAA-FE and TLM-FE, is extended for the mobility service according to [ITU-T Y.2014] to support TLM-FE for the location registration to MMCF. The procedures described in clause 8.3.1 show the information required for the provisioning of the TLM-FE, such as the address of MLM-FE, mobility protocol type, anchor point address, and the security association between UE and MMCF. This interface is extended in the format of transport resource information indication and transport resource information response information flows, from TAA-FE to TLM-FE. + +### **8.3.5 Ne** + +The Ne reference point is extended for the mobility service according to [ITU-T Y.2014] to deliver mobility-service parameters between NAC-FE and TLM-FE. NAC-FE registers TLM-FE with the binding information between the mobility-service subscriber ID and persistent/temporary IP addresses. The TLM-FE informs the NAC-FE of the UE's PIA, mobility-protocol type, the address of MLM-FE(P), and keying material for the security associations between the UE and the MMCF. This interface is extended in the format of the mobility-service parameters indication information flow, from TLM-FE to NAC-FE. + +# **9 Security considerations** + +Security requirements within the functional requirements and architecture of NACF are addressed by the security requirements for NGN [ITU-T Y.2701]. Interfaces of NACF related to the mobility service shall follow the security requirements of NACF. + +# Appendix I + +## Mapping to IETF mobility architecture + +(This appendix does not form an integral part of this Recommendation.) + +IETF has worked on IP mobility protocols, such as MIPv4 ([b-IETF RFC 3344]), MIPv6 ([b-IETF RFC 3775]), and proxy mobile IP (PMIP) ([b-IETF RFC 5213]). Generally, mobility architecture includes two physical entities in IP networks: a home agent and an access gateway (Figure I.1). The home agent is linked to all access gateways and manages user location information and profiles. The home agent can also be located in some access gateways. In this case, the function of the home agent is distributed to access gateways; access gateways have the function of the home agent in addition to their own function. The access gateway detects user movement to a new IP network. In the network-based mobility case, an IP address of the access gateway is used as a mobile node's CoA, so that packets destined to the mobile node are delivered to the access gateway on behalf of the mobile node. Then, the access gateway directly transfers them to the mobile node that just has an IPv6 specification. Within a domain, one home agent exists and more than one home agent will be considered in the future. However, in the case of host-based mobility, a mobile node has its own HoA and CoA and receives packets directly from the home agent or a sender. + +NACF is responsible for IP address management and authentication to support IP mobility as some parts of access gateway functionality. MMCF can perform control parts of functions in both the home agent and access gateways, as it manages mobile node binding information. + +![Diagram of network architecture for IP mobility showing CPEs connected to Access points, which are then connected to Access gateways, all of which are connected to a central Home agent.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +The diagram illustrates a network architecture for IP mobility. It features three horizontal paths at the bottom, each consisting of a 'CPE' box connected to an 'Access point' box. The first two 'Access point' boxes are connected to a single 'Access gateway' box. The third 'Access point' box is connected to its own 'Access gateway' box. Both 'Access gateway' boxes are then connected to a single 'Home agent' box on the right. A small label 'Q.3203(11)\_FI.1' is located in the bottom right corner of the diagram area. + +Diagram of network architecture for IP mobility showing CPEs connected to Access points, which are then connected to Access gateways, all of which are connected to a central Home agent. + +**Figure I.1 – Network architecture for IP mobility** + +# Appendix II + +## Mapping to PMIP domain + +(This appendix does not form an integral part of this Recommendation.) + +A mobile node in a proxy mobile IP (PMIP) domain is generally identified by an identifier (MN-Identifier) that has an associated policy profile. This information is typically configured in an AAA server. When a user accesses the network, the network needs to authenticate the user. NGN functions related to the access authentication in PMIP are shown in Figure II.1. + +![Functional architecture for access authentication diagram](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +The diagram shows two rectangular boxes connected by a horizontal line. The left box is labeled 'Transport functions' and the right box is labeled 'NACF (AAA Server)'. Above the connecting line is the label 'TC-T1'. Below the right box is the text 'Q.3203(11)\_FII.1'. + +Functional architecture for access authentication diagram + +**Figure II.1 – Functional architecture for access authentication** + +The data related to access authentication includes the subscriber identity, supported authentication methods, and authentication keys. Additionally, user data defined in the policy profile are needed in order to support PMIP [b-IETF RFC 5213]. The network entities in the PMIP domain have access to the mobile node's policy profile that contains the operational parameters required by the network entities for managing the mobile node's mobility service. Network entities, such as the mobile access gateway (MAG) and the local mobility anchor (LMA), can query this information using RADIUS [b-IETF RFC 2865] or DIAMETER [b-IETF RFC 3588] protocols. + +The policy profile has two mandatory fields and other optional fields, as shown in Table II.1. TUP-FE stores this information for policy profile in PMIP and may permanently store two of their mandatory parameters. Additional user data for the policy profile can be added to the transport-user profile described in [b-ITU-T Q-Sup. 58]. The network entities in a PMIP domain can identify a mobile using its MN-Identifier obtained as part of the access authentication. The MN-Identifier may be the same as the user identifier (Subscriber ID), unless it is used from more than one mobile node operating in the same PMIP domain. + +**Table II.1 – Mobile node's policy profile** + +| Field | Attribute | TUP-FE | +|---------------------------------------------------------------------|-----------|-----------| +| The mobile node's identifier (MN-Identifier) | Mandatory | Permanent | +| The IPv6 address of the local mobility anchor (LMAA) | Mandatory | Permanent | +| The mobile node's IP home network prefix(es) | Optional | | +| The mobile node's IP home network prefix lifetime | Optional | | +| Permitted address configuration mode (stateful, stateless, or both) | Optional | | + +# Appendix III + +## Mapping IPv6 user configuration for the mobility service + +(This appendix does not form an integral part of this Recommendation.) + +## III.1 Initial allocation of IP address + +A mobile CPE in the access network domain can configure one or more IP addresses on its interface using IPv6 stateless or stateful address autoconfiguration procedures. When stateless address autoconfiguration is supported on the link, the mobile node can generate one or more IPv6 addresses by combining the network prefix advertised on the access link with an interface identifier. When stateful address autoconfiguration is supported on the link, the mobile node obtains the address configuration from the DHCPv6 server using DHCPv6 client protocol. + +## III.2 Interaction with DHCP relay agent + +If stateful address configuration using DHCP is supported on the link on which the mobile node is attached, the DHCP relay agent needs to be configured on the access router (e.g., AM-FE function in NACF). When the mobile node sends a DHCPv6 Request message, the relay agent function on the AM-FE must set the link-address field in the DHCPv6 message to the mobile node's local home network prefix, so as to provide a prefix hint to the DHCP server. Since the access link is a point-to-point link with the configured mobile node's prefix as the on-link prefix, the normal DHCP relay agent configuration on the AM-FE will ensure that the prefix hint is set to the mobile node's home network prefix. + +If the mobile node is IPv4 enabled, the mobile CPE after the access authentication will be able to obtain the IPv4 address configuration for the connected interface by using DHCPv4. + +## III.3 IPv6 address autoconfiguration + +Functions related to the IP address allocation are shown in Figure III.1. CPE communicates with NACF via the AR-FE in the transport functions. T-U1 and TC-T1 reference points are related to the IP address allocation. The T-U1 reference point enables the CPE to initiate requests for IP address allocation and other network configuration parameters. These requests are received by the AR-FE and are relayed to the AM-FE in NACF via the TC-T1 reference point. These reference points also provide transport IP address and network configuration information to the CPE for connecting to the network. Either DHCP or PPP is used as a method for IP address allocation and network configuration. + +![Functional architecture for IP address allocation diagram](90ee16ccc0ad16aeca48087797d7b07f_img.jpg) + +The diagram illustrates the functional architecture for IP address allocation. It consists of three main components connected in a linear sequence: a box labeled 'CPE' on the left, a box labeled 'Transport functions' in the center, and a box labeled 'NACF' on the right. The 'CPE' is connected to the 'Transport functions' via a line labeled 'T-U1'. The 'Transport functions' are connected to the 'NACF' via a line labeled 'TC-T1'. Below the 'NACF' box, there is a small text label 'Q.3203(11)\_FIII.1'. + +Functional architecture for IP address allocation diagram + +**Figure III.1 – Functional architecture for IP address allocation** + +However, IPv6 defines both stateful address configuration and stateless address autoconfiguration, which requires no manual configuration of hosts. The stateless mechanism allows a host to generate its own addresses using a combination of locally available information and information advertised by routers. Both stateless address autoconfiguration and dynamic host configuration protocol for IPv6 (DHCPv6) [b-IETF RFC 3315] may be used simultaneously. + +In the case of IPv6 stateless address allocation, a CPE does not use DHCP for manual configuration. Instead, CPE generates its own address using subnet prefixes advertised by routers. As NACF is not involved in the IPv6 stateless address configuration, the NAC-FE cannot maintain a mapping between the CPE and the assigned IP address and cannot forward this information to the TLM-FE, causing the TLM-FE not to respond to location queries from service control functions. In the case of autoconfiguration, an additional information flow is needed in order to register a CPE's IPv6 address to NACF via T-U1 and TC-T1 reference points. When a CPE connects to the network, it can use DHCPv6 [b-IETF RFC 3315] for IPv6 address allocation via T-U1 and TC-T1 reference points, or can configure its own address using IPv6 stateless address autoconfiguration. After an autoconfiguration process, the CPE registers its IPv6 address information to NACF. + +IPv6 stateless address autoconfiguration mechanism [IETF RFC 4862] defines two functions mapped to the NGN functional architecture: + +- The Host is a function of the CPE that autoconfigures its IPv6 address. +- The Router is a function of transport functions in charge of advertising network information. + +As shown in Figure III.2, router solicitation (RS) and router advertisement (RA) are transmitted between the Host and the Router. + +![Figure III.2 – IPv6 autoconfiguration functional entities diagram. It shows three main components in a horizontal line: 'CPE (Host)' on the left, 'Transport functions (Router)' in the center, and 'NACF' on the right. A line labeled 'T-U1' connects 'CPE (Host)' to 'Transport functions (Router)'. Below this line, 'RS/RA' is written. Another line labeled 'TC-T1' connects 'Transport functions (Router)' to 'NACF'. In the bottom right corner of the diagram, there is a small label 'Q.3203(11)_FIII.2'.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +Figure III.2 – IPv6 autoconfiguration functional entities diagram. It shows three main components in a horizontal line: 'CPE (Host)' on the left, 'Transport functions (Router)' in the center, and 'NACF' on the right. A line labeled 'T-U1' connects 'CPE (Host)' to 'Transport functions (Router)'. Below this line, 'RS/RA' is written. Another line labeled 'TC-T1' connects 'Transport functions (Router)' to 'NACF'. In the bottom right corner of the diagram, there is a small label 'Q.3203(11)\_FIII.2'. + +**Figure III.2 – IPv6 autoconfiguration functional entities** + +Registration of the binding information between a configured IPv6 address and a CPE is needed via T-U1 and TC-T1 reference points. Table III.1 describes the elements contained in the registration information flow. + +**Table III.1 – Registration (CPE → NACF)** + +| Information element | Description | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------| +| Globally unique IP address information | A set of IP address information used for locating the access network to which the CPE is attached. | +| – Unique IP address | The IP address configured to the attached CPE. | +| – Address realm | The addressing domain in which the IP address is significant. | +| Physical connection identifier (optional) | A local identifier for physical connection of the access transport network to which the CPE is attached. | +| Logical connection identifier | A local identifier for logical connection of the access transport network to which the CPE is connected. | +| CPE type (optional) | The type of CPE. | + +The IPv6 stateful address allocation process can be completed by using DHCP messages. In DHCP mode, the transport functions include an AR-FE acting as a DHCP relay between the DHCP clients in the CPE and the DHCP server in NACF (see Figure III.3). To newly support IPv6 stateless address autoconfiguration, an additional registration flow is needed between a CPE and NACF. The CPE registers address information to the NAC-FE, after the CPE configures its own IPv6 address. This information is received by AR-FE and then relayed to the AM-FE via T-U1 and TC-T1 reference points. + +![Sequence diagram showing IPv6 address allocation flows for Stateful and Stateless configurations. Lifelines include CPE, TF (AR-FE), AM-FE, NACF (NAC-FE), and TLM-FE. The diagram is divided into two sections: Stateful address configuration and Stateless address configuration. Arrows indicate the sequence of messages between the entities.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates two IPv6 address allocation flows between a CPE and a network architecture involving TF, AM-FE, NACF, and TLM-FE. + +**Stateful address configuration:** + +- The CPE sends a **1. DHCP request** to the AR-FE (within TF). +- The AR-FE forwards this to the AM-FE. +- The AM-FE forwards it to the NAC-FE (within NACF). +- The NAC-FE sends a **2. DHCP response** back to the AR-FE. +- The AR-FE then sends a **3. Inform IP address** message to the TLM-FE (within NACF). + +**Stateless address configuration:** + +- The CPE sends a **1. Router solicitation** to the AR-FE (within TF). +- The AR-FE sends a **2. Router advertisement** back to the CPE. +- The CPE then sends a **3. Register IPv6 address** message to the AR-FE. +- The AR-FE forwards this to the AM-FE. +- The AM-FE forwards it to the NAC-FE (within NACF). +- The NAC-FE sends a **4. Inform IP address** message to the TLM-FE (within NACF). + +Q.3203(11)\_FIII.3 + +Sequence diagram showing IPv6 address allocation flows for Stateful and Stateless configurations. Lifelines include CPE, TF (AR-FE), AM-FE, NACF (NAC-FE), and TLM-FE. The diagram is divided into two sections: Stateful address configuration and Stateless address configuration. Arrows indicate the sequence of messages between the entities. + +**Figure III.3 – IPv6 address allocation flows** + +# Bibliography + +- [b-ITU-T Q.1708] Recommendation ITU-T Q.1708/Y.2805 (2008), *Framework of location management for NGN*. +- [b-ITU-T Q-Sup. 58] ITU-T Q-series Recommendations – Supplement 58 (2008), *Organization of NGN transport user data*. +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. +- [b-IETF RFC 2865] IETF RFC 2865 (2000), *Remote Authentication Dial In User Service (RADIUS)*. +- [b-IETF RFC 3315] IETF RFC 3315 (2003), *Dynamic Host Configuration Protocol for IPv6 (DHCPv6)*. +- [b-IETF RFC 3344] IETF RFC 3344 (2002), *IP Mobility Support for IPv4*. +- [b-IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol*. +- [b-IETF RFC 3775] IETF RFC 3775 (2004), *Mobility Support in IPv6*. +- [b-IETF RFC 5213] IETF RFC 5213 (2008), *Proxy Mobile IPv6*. + + + +# 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.3223-200906-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/Q/T-REC-Q.3223-200906-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..443546a00efe33f1530f28e338b2b652df065efd --- /dev/null +++ b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b455fc2f62deaf3b768623659e7e8be7df9681523cb79e19a51f4f76a17f6ff +size 26553 diff --git a/marked/Q/T-REC-Q.3223-200906-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d400812082fe34dabad6dfd2f357a31b2434fb5 --- /dev/null +++ b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26bc586d3ad1d404f40e79e0b806002ff1dd575b530ccda6b23634df79814243 +size 45111 diff --git a/marked/Q/T-REC-Q.3223-200906-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..05ec54d5840ba48958be26a92b15d0da45372249 --- /dev/null +++ b/marked/Q/T-REC-Q.3223-200906-I_PDF-E/raw.md @@ -0,0 +1,979 @@ + + +**ITU-T** + +**Q.3223** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(06/2009) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +Signalling requirements and protocols for the NGN – +Signalling and control requirements and protocols to +support attachment in NGN environments + +--- + +**Requirements and protocol for the interface +between a transport location management +physical entity and a policy decision physical +entity (Ru Interface)** + +Recommendation ITU-T Q.3223 + +## 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.3223** + +# **Requirements and protocol for the interface between a transport location management physical entity and a policy decision physical entity (Ru Interface)** + +## **Summary** + +Recommendation ITU-T Q.3223 describes requirements and protocol for the Ru interface between a transport location management physical entity (TLM-PE) in a network attachment control entity (NACE) and a policy decision physical entity (PD-PE) in a resource and admission control entity (RACE) of ITU-T next generation network (NGN) release 1. + +## **Source** + +Recommendation ITU-T Q.3223 was approved on 29 June 2009 by ITU-T Study Group 11 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## **Keywords** + +Network attachment, next generation network (NGN), Ru interface. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Ru interface..... | 3 | +| 5.1 Overview ..... | 3 | +| 5.2 Reference point..... | 3 | +| 5.3 Physical entities ..... | 3 | +| 6 Signalling requirements ..... | 4 | +| 6.1 Transport resource information ..... | 5 | +| 6.2 Transport resource information indication ..... | 7 | +| 6.3 Transport resource release notification ..... | 7 | +| 7 Procedure descriptions..... | 7 | +| 7.1 General ..... | 7 | +| 7.2 Procedures on the Ru interface..... | 8 | +| 8 Selection and the use of the protocol ..... | 13 | +| 8.1 Security ..... | 13 | +| 8.2 Accounting ..... | 13 | +| 8.3 Sessions ..... | 13 | +| 8.4 Transport protocol ..... | 13 | +| 8.5 Routing considerations ..... | 13 | +| 8.6 Application advertisement..... | 14 | +| 9 Ru protocol specification..... | 14 | +| 9.1 Commands ..... | 14 | +| 9.2 Result-Code AVP values ..... | 17 | +| 9.3 AVPs..... | 17 | +| 9.4 Use of namespaces ..... | 20 | +| 10 Security considerations ..... | 20 | +| Bibliography..... | 21 | + + + +# Recommendation ITU-T Q.3223 + +# Requirements and protocol for the interface between a transport location management physical entity and a policy decision physical entity (Ru Interface) + +# 1 Scope + +This Recommendation defines the requirements and protocol for the Ru interface (identical to the TC-TC1 interface defined in [ITU-T Y.2012]) between a transport location management physical entity (TLM-PE) in a network attachment control entity (NACE) and a policy decision physical entity (PD-PE) in a resource and admission control entity (RACE) of ITU-T NGN release 1 architecture. + +Whenever applicable, this Recommendation specifies the requirements for the Ru interface referring to the Diameter base specifications. Whenever needed, extensions to Diameter-based specifications are provided in this Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. +- [ITU-T Y.2014] Recommendation ITU-T Y.2014 (2008), *Network attachment control functions in next generation networks*. +- [ITU-T Y.2111] Recommendation ITU-T Y.2111 (2008), *Resource and admission control functions in next generation networks*. +- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. +- [ETSI TS 129 229] ETSI TS 129 229 v8.6.0 (2009), *Digital cellular telecommunication system (Phase 2+); Universal Mobile Telecommunications system (UMTS); LTE; Cx and Dx interfaces based on the Diameter protocol*. +- [ETSI TS 129 329] ETSI TS 129 329 (2006), *Digital cellular telecommunication system (Phase 2+); Universal Mobile Telecommunications system (UMTS); Sh interface based on the Diameter protocol; Protocol details*. +- [ETSI TS 183 017] ETSI TS 183 017 (2007), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification*. +- [ETSI ES 283 034] ETSI ES 283 034 v1.5.0 (2008), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the Diameter protocol*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 authentication** [ITU-T Y.2014]: A property by which the correct identifier 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.1.2 authorization** [b-ITU-T X.800]: The granting of permission based on authenticated identification. + +NOTE – In some contexts, authorization may be granted without requiring authentication or identification, e.g., emergency call services. + +**3.1.3 customer premises equipment (CPE)** [ITU-T Y.2014]: One or more devices allowing a user to access services delivered by NGN. + +NOTE – This includes devices under user control commonly referred to as home gateway (HGW) or terminals (TE), etc., but not network-controlled entities such as access gateways. + +**3.1.4 attribute-value pair (AVP)** [ETSI ES 283 034]: Corresponds to an information element in a Diameter message. + +NOTE – See [b-IETF RFC 3588] for details. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|----------------------------------------------| +| ABNF | Augmented Backus-Naur Form | +| AM-PE | Access Management Physical Entity | +| AVP | Attribute-Value Pair | +| CPE | Customer Premises Equipment | +| HGWC-PE | Home Gateway Configuration Physical Entity | +| IMS | Internet Protocol Multimedia Subsystem | +| IPSec | Internet Protocol Security | +| NACE | Network Attachment Control Entity | +| NACF | Network Attachment Control Function | +| NAC-PE | Network Access Configuration Physical Entity | +| NAPT | Network Address and Port Translation | +| NAS | Network Access Server | +| NASS | Network Attachment Sub-System | +| P-CSCF | Proxy Call Session Control Function | +| PD-PE | Policy Decision Physical Entity | +| PE-PE | Policy Enforcement Physical Entity | +| QoS | Quality of Service | +| RACE | Resource and Admission Control Entity | +| RACF | Resource and Admission Control Function | + +| | | +|--------|------------------------------------------------------------| +| RFC | Request For Comments | +| SCE | Service Control Entity | +| SCTP | Stream Control Transport Protocol | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| TAA-PE | Transport Authentication and Authorization Physical Entity | +| TLM-PE | Transport Location Management Physical Entity | +| TRC-PE | Transport Resource Control Physical Entity | +| TUP-PE | Transport User Profile Physical Entity | + +# 5 Ru interface + +## 5.1 Overview + +The network attachment control function (NACF) maintains information about IP-connectivity access sessions associated with user equipment connected to the NGN. This information is stored in the transport location management physical entity (TLM-PE) and it is pushed to or pulled from the PD-PE in the RACE when the initial attachment is established or the PD-PE needs the information to make a decision (see Figure 5-1): + +## 5.2 Reference point + +This clause describes the Ru reference point. + +![Diagram of the Ru reference point showing the NACE and RACE domains. The NACE domain contains HGWC-PE, TUP-PE, TAA-PE, AM-PE, NAC-PE, and TLM-PE. The RACE domain contains PD-PE. The Ru reference point is the interface between TLM-PE and PD-PE. SCE is connected to TLM-PE via S-TC1. A dashed box labeled 'Scope of this Recommendation' encompasses the Ru interface.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +The diagram illustrates the network architecture around the Ru reference point. On the left, the NACE (Network Attachment Control Entity) domain contains several physical entities: HGWC-PE, TUP-PE, TAA-PE, AM-PE, NAC-PE, and TLM-PE. These entities are interconnected. TLM-PE is connected to the SCE (Service Control Entity) via the S-TC1 interface. On the right, the RACE (Resource Allocation and Control Entity) domain contains the PD-PE. The Ru reference point is the interface between the TLM-PE in the NACE domain and the PD-PE in the RACE domain. A dashed box labeled 'Scope of this Recommendation' highlights the Ru interface. The diagram is labeled Q.3223(09)\_F5.1. + +Diagram of the Ru reference point showing the NACE and RACE domains. The NACE domain contains HGWC-PE, TUP-PE, TAA-PE, AM-PE, NAC-PE, and TLM-PE. The RACE domain contains PD-PE. The Ru reference point is the interface between TLM-PE and PD-PE. SCE is connected to TLM-PE via S-TC1. A dashed box labeled 'Scope of this Recommendation' encompasses the Ru interface. + +Figure 5-1 – Ru reference point + +## 5.3 Physical entities + +Table 5-1 indicates the mapping from the functional entities to the physical entities implementing them. + +**Table 5-1 – Mapping from functional to physical entities concerned with the Ru reference point** + +| Functional entity | Abbrev. | Physical entity | Abbrev. | +|-------------------------------------------------|----------------|---------------------------------------------------------|----------------| +| Service control functions | SCF | Service control entity (e.g., implementation of P-CSCF) | SCE | +| Network attachment control functions | NACF | Network attachment control entity | NACE | +| Resource and admission control functions | RACF | Resource and admission control entity | RACE | +| Policy decision functional entity | PD-FE | Policy decision physical entity | PD-PE | +| Transport location management functional entity | TLM-FE | Transport location management physical entity | TLM-PE | + +### 5.3.1 Transport location management physical entity (TLM-PE) + +The transport location management physical entity (TLM-PE) is a physical entity that implements the functionalities of the transport location management functional entity (TLM-FE) defined in the NACF. The TLM-PE registers the association between the IP address allocated to the terminal and related network location information provided by the NAC-PE, for example, access transport equipment characteristics, line identifier (logical access ID), IP edge identity, etc. The TLM-PE registers the association between network location information received from the NAC-PE and geographical location information. The TLM-PE may also store the identity of a user or a terminal to which the IP address has been allocated (information received from the TAA-PE), as well as the user network QoS profile and user preferences regarding the privacy of location information. In case the TLM-PE does not store the identity/profile of the user/terminal, the TLM-PE shall be able to retrieve this information from the TAA-PE. + +The TLM-PE responds to location queries from service control functions and applications. The actual information delivered by the TLM-PE may take various forms (e.g., network location, geographical coordinates, postal address, etc.), depending on agreements with the requestor and on user preferences regarding the privacy of its location. The TLM-PE interfaces with the NAC-PE to establish the association between the IP address, which is allocated by the NAC-FE to the end-user equipment, and the line ID. + +The TLM-PE also registers user network profile information (received from the TAA-PE at authentication) to make this profile information available to the RACE during authentication of the terminal. The TLM-PE is able to correlate the information received from NAC-PE and TAA-PE based on the logical access ID. + +### 5.3.2 Policy decision physical entity (PD-PE) + +The PD-PE is a physical entity that implements the functionalities of the policy decision functional entity (PD-FE) defined in [ITU-T Y.2111], which coordinates the resource reservation requests received from the SCE. The functionality of the PD-PE is further detailed in clause 7.2.3.2 of [ITU-T Y.2111]. + +# 6 Signalling requirements + +The Ru reference point should allow information exchange as follows: + +- The profile information is pushed by the TLM-PE to the PD-PE. +- The profile information is pulled by the PD-PE from the TLM-PE. + +The PD-PE and TLM-PE should use one of two selection mechanisms, either local static configuration or dynamic discovery, based on a globally unique IP address and/or transport subscriber ID to locate the respective communicating entities (i.e., PD-PE → TLM-PE, or TLM-PE → PD-PE). + +The following information flows shall be used on the Ru interface: + +- Transport resource information. +- Transport resource information indication. +- Transport resource release notification. + +Figure 6-1 shows the information flows between the TLM-PE and the PD-PE via the Ru interface. + +![Sequence diagram showing information flows between TLM-PE and PD-PE over the Ru interface. The diagram shows three horizontal arrows: 1. Transport resource information request/response flow (bidirectional), 2. Transport resource information indication flow (from TLM-PE to PD-PE), and 3. Transport resource release notification flow (from TLM-PE to PD-PE). The diagram is labeled Q.3223(09)_F6.1 at the bottom right.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Sequence diagram showing information flows between TLM-PE and PD-PE over the Ru interface. The diagram shows three horizontal arrows: 1. Transport resource information request/response flow (bidirectional), 2. Transport resource information indication flow (from TLM-PE to PD-PE), and 3. Transport resource release notification flow (from TLM-PE to PD-PE). The diagram is labeled Q.3223(09)\_F6.1 at the bottom right. + +**Figure 6-1 – Information flows over Ru interface** + +## 6.1 Transport resource information + +The information flow of the transport resource information request is sent by the PD-PE to the TLM-PE to request the access transport network profile information. Globally unique IP address information and/or a transport subscriber identifier should be used to discover the NACE and identify the user profile using the static configuration or dynamic discovery approaches. There are two scenarios for this pull mode: one is the failure recovery of the PD-PE, the other is the synchronization of the data in the PD-PE with the user data in the TLM-PE to avoid inconsistency. It contains the following information components (see Table 6-1). + +NOTE 1 – In the following tables, each information element is marked as (M) mandatory, (C) conditional or (O) optional. + +NOTE 2 – In this Recommendation, '(C)' implies 'Conditional mandatory'. The case of 'conditional option' is not applicable for this Recommendation. + +**Table 6-1 – Transport resource information request** + +| Information element name | Description | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Globally unique IP address information (M) | This information element contains the IP address of the user equipment used by the subscriber and the addressing domain in which the IP address is significant. | +| Transport subscriber ID (O) | A globally unique identifier for the CPE requesting the transport resource. This identifier can be used for locating the transport subscription information for the CPE. | +| RACF ID (O) | The identity of the RACF function requesting access profile information. | + +The transport resource information response information flow is sent by the TLM-PE to the PD-PE to provide the access transport network profile information during either a new resource initiation request from the SCE or the network failure recovery procedure. It contains the following information components (see Table 6-2). + +**Table 6-2 – Transport resource information response** + +| Information element name | Description | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Globally unique IP address information (M) | This information element contains the IP address of the user equipment used by the subscriber and the addressing domain in which the IP address is significant. | +| Logical access ID (M) | The identity of the logical access to which the user equipment is connected. | +| Access network type (O) | The type of access network over which network attachment is provided to the user equipment. | +| Transport subscriber ID (C) | The user who is attached to the network. This element shall be included if available in the TLM-PE. | +| Physical access ID (O) | The identity of the physical access to which the user equipment is connected. | +| Default configuration (O) | See Table 6-3. | +| Transport resource subscription (O) | See Table 6-4. | + +The default configuration information can be included optionally in the transport resource information response. The involved information elements are shown in Table 6-3. + +**Table 6-3 – Default configuration information elements** + +| Information element name | Description | +|----------------------------------------|----------------------------------------------------------------------------------------------------------| +| Default access control list (O) | The list of destination IP addresses, ports, prefixes and port ranges allowed to cut through by default. | +| Default maximum uplink bandwidth (O) | The maximum bandwidth that can be used for the upstream connections by default. | +| Default maximum downlink bandwidth (O) | The maximum bandwidth that can be used for the downstream connections by default. | + +The transport resource subscription information can be included optionally in the transport resource information response. The involved information elements are shown in Table 6-4. + +**Table 6-4 – Transport resource subscription information elements** + +| Information element name | Description | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Network class of service (O) | The transport class applicable to the QoS profile information. | +| Subscribed uplink bandwidth (O) | The maximum amount of bandwidth subscribed to by the attached user in the uplink direction for a specific network class of service. | +| Subscribed downlink bandwidth (O) | The maximum amount of bandwidth subscribed to by the attached user in the downlink direction for a specific network class of service. | +| Level of priority (O) | The maximum priority allowed for any reservation request. | + +## 6.2 Transport resource information indication + +The transport resource information indication information flow is sent by the TLM-PE to the PD-PE to push the access transport network profile information when an IP address assigned to a subscriber or the relevant profile is changed after the profile information has been sent to the PD-PE. It contains the following information components (see Table 6-5). + +**Table 6-5 – Access profile notification information elements** + +| Information element name | Description | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Globally unique IP address information (M) | This information element contains the IP address of the user equipment used by the subscriber and the addressing domain in which the IP address is significant. | +| Logical access ID (M) | The identity of the logical access to which the user equipment is connected. | +| Access network type (O) | The type of access network over which network attachment is provided to the user equipment. | +| Transport subscriber ID (C) | The user who is attached to the network. This element shall be included if available in TLM-PE. | +| Physical access ID (O) | The identity of the physical access to which the user equipment is connected. | +| Default configuration (O) | See Table 6-3. | +| Transport resource subscription (O) | See Table 6-4. | + +## 6.3 Transport resource release notification + +The transport resource release notification information flow is sent by the TLM-PE to notify the PD-PE to remove the resource profile information from the local repository when the assigned IP address is released (e.g., DHCP leased timer expiry or a release of the access transport resources). It contains the following information components (see Table 6-6). + +**Table 6-6 – Transport resource release notification information elements** + +| Information element name | Description | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Globally unique IP address information (M) | This information element contains the IP address of the user equipment used by the subscriber and the addressing domain in which the IP address is significant. | +| Transport subscriber ID (O) | The user who is attached to the network. | + +# 7 Procedure descriptions + +The following clauses describe the realization of the functional procedures defined in the NACF [ITU-T Y.2014] and RACF specifications [ITU-T Y.2111] using Diameter commands described in clause 9. + +## 7.1 General + +### 7.1.1 Mapping the information elements + +This clause describes a mapping of the information elements defined in the NACF specification onto the Diameter AVPs. + +In the tables that describe this mapping, each information element is marked as (M) mandatory or (O) optional: + +- A mandatory information element (marked as (M) in the table) shall always be present in the command. If this information element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER\_MISSING\_AVP. This message shall also include a Failed-AVP AVP containing the missing information element, i.e., the corresponding Diameter AVP defined by the AVP code and the other fields set as expected for this information element. +- An optional information element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this information element shall not cause an application error and may be ignored by the receiver. + +### 7.1.2 Subscriber profile + +Subscriber profile information sent over the Ru interface is structured into two groups: the transport resource subscription information and the default configuration information. + +Tables 7-1 and 7-2 detail the involved information elements as defined in the NACF specification [ITU-T Y.2014] and their mapping to Diameter AVPs. + +**Table 7-1 – Default configuration information** + +| Information element name | Mapping to Diameter AVP | Category | +|------------------------------|------------------------------|----------| +| Default access control list | NAS-Filter-Rule | O | +| Default upstream bandwidth | Maximum-Allowed-Bandwidth-UL | O | +| Default downstream bandwidth | Maximum-Allowed-Bandwidth-DL | O | + +**Table 7-2 – Transport resource subscription information** + +| Information element name | Mapping to Diameter AVP | Category | +|-------------------------------|------------------------------|----------| +| Network class of service | Transport-Class | O | +| Subscribed uplink bandwidth | Maximum-Allowed-Bandwidth-UL | O | +| Subscribed downlink bandwidth | Maximum-Allowed-Bandwidth-DL | O | +| Level of priority | Reservation-Priority | O | + +## 7.2 Procedures on the Ru interface + +### 7.2.1 Transport resource information exchange + +#### 7.2.1.1 Overview + +This procedure is used by the RACF to request the transport resource information from the TLM-PE. This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in clause 9. Tables 7-3 and 7-4 detail the involved information elements as defined in the NACF specification [ITU-T Y.2014] and their mapping to Diameter AVPs. + +**Table 7-3 – Transport resource information request** + +| Information element name | Mapping to Diameter AVP | Category | +|------------------------------------------------|-------------------------|----------| +| Globally unique IP address | Globally-Unique-Address | O | +| Transport subscriber ID | User-Name | O | +| NOTE – One of these elements shall be present. | | | + +**Table 7-4 – Transport resource information response** + +| Information element name | Mapping to Diameter AVP | Category | +|----------------------------------|---------------------------------|----------| +| Globally unique IP address | Globally-Unique-Address | O | +| Transport subscriber identifier | User-Name | O | +| Physical connection identifier | Physical-Access-Id | O | +| Logical connection identifier | Logical-Access-Id | M | +| Type of access transport network | Access-Network-Type | O | +| Transport resource subscription | Transport-Resource-Subscription | O | + +#### **7.2.1.2 Procedure at the RACF side** + +The RACF may use this procedure upon reception of the resource reservation request associated with an IP-Address for which no record is stored. + +The RACF shall populate the transport resource information request as follows: + +- 1) The User-Name AVP or the Globally-Unique-Address AVP shall be included. The Globally-Unique-Address AVP shall be included in configurations where more than one IP address may be assigned per subscriber identifier. +- 2) If present, the Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and an Address-Realm AVP. The Address-Realm AVP shall be included and set either using configuration data (in which case, all terminal equipment served by the RACF belong to the same addressing domain) or from the physical or logical interface over which was received the resource request that triggered the pull procedure. + +#### **7.2.1.3 Procedure at the TLM-PE side** + +Upon reception of the transport resource information request, the TLM-PE shall, in the following order: + +- 1) If the Globally-Unique-Address AVP is present, use this information as a key to retrieve the requested session information. +- 2) If the Globally-Unique-Address AVP is absent but the User-Name AVP is present, use the latter information as a key to retrieve the requested session information. +- 3) If both the Globally-Unique-Address AVP and the User-Name AVP are absent, return a transport resource information response with Result-Code set to DIAMETER\_MISSING\_AVF. +- 4) If more than one record include the same subscriber identity matching the value of the User-Name AVP and no Globally-Unique-Address AVP is included, return a transport resource information response with Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY. + +- 5) If no session record is stored for the Globally-Unique-Address AVP or the User-Name AVP, return a transport resource information response with the Experimental-Result-Code AVP be set to DIAMETER\_ERROR\_USER\_UNKNOWN. + +If a unique subscriber record can be retrieved, the TLM-PE shall: + +- 1) Check which session data can be returned to the RACF, based on local policy rules and per-subscriber privacy information stored in the TLM-PE. +- 2) Check whether the session data to be retrieved is currently being updated by another entity. If there is an update of the data in progress, the TLM-PE may delay the response message until the update has been completed and shall include in the response message the updated data requested. The TLM-PE shall ensure that the data returned is not corrupted by this conflict. + +If the TLM-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 set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY or an Experimental-Result-Code AVP set to DIAMETER\_USER\_DATA\_NOT\_AVAILABLE. + +Otherwise, the requested operation shall take place and the TLM-PE shall return the Result-Code AVP set to DIAMETER\_SUCCESS and the session data in the transport resource information response. + +### 7.2.2 Transport resource information indication + +#### 7.2.2.1 Overview + +This procedure is used to push session-related information from the TLM-PE to the RACF. This information flow occurs when an IP address has been allocated to a subscriber or in case a modification occurs on a profile that has already been pushed to the RACF. + +The TLM-PE should push session-related information to the RACF as soon as it is available to the TLM-PE. This may require the TLM-PE to pull part of the information from other components of the NACF. + +For the same subscriber, the TLM-PE may push several independent session records with different IP addresses, with or without the same logical access identifier. + +This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 9. Table 7-5 details the involved information elements as defined in the NACF specification [ITU-T Y.2014] and their mapping to Diameter AVPs. + +**Table 7-5 – Transport resource information indication** + +| Information element name | Mapping to Diameter AVP | Category | +|----------------------------------|---------------------------------|----------| +| Globally unique IP address | Globally-Unique-Address | O | +| Transport subscriber identifier | User-Name | O | +| Physical connection identifier | Physical-Access-Id | O | +| Logical connection identifier | Logical-Access-Id | M | +| Type of access transport network | Access-Network-Type | O | +| Transport resource subscription | Transport-Resource-Subscription | O | +| Default configuration | Initial-Gate-Setting | O | + +#### 7.2.2.2 Procedure at the TLM-PE side + +The TLM-PE knows the address of the RACF entity to which the information should be pushed, either from configuration data or from the user profile (i.e., received from the TAA-PE/TUP-PE). + +The TLM-PE shall populate the transport resource information indication as follows: + +- The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and an Address-Realm AVP. +- The Logical-Access-Id AVP shall be present. + +The presence of the other AVPs depends on the user profile and local policy rules. + +#### 7.2.2.3 Procedure at the RACF side + +If the logical access ID is not included or is invalid, the RACF shall return a transport resource information indication with a Result-Code AVP value set to DIAMETER\_INVALID\_AVP\_VALUE. + +If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the RACF shall: + +- Create an internal record to store the received information for future use (i.e., for processing resource reservation requests received from the SCE). +- Derive the following information from the logical access ID: + - The identification and bandwidth capacity of the layer 2 resources over which the subscriber traffic is carried. + - The address of the physical node(s) implementing the edge node FE and access node FE. +- If the received information contains an Initial-Gate-Setting AVP, perform any appropriate actions to enforce the policy information. This may involve interacting with the policy enforcement physical entity (PE-PE) through the Rw interface (defined in [ITU-T Y.2111]). + +If the globally unique identifier contained in the Globally-Unique-Address AVP is already known, the RACF shall: + +- Replace the entire content of the internal record with the received information for future use. +- If the received information contains a default configuration, perform any appropriate actions to enforce the new policy information. This may involve interacting with the PE-PE through the Rw interface. + +Such an update shall not have any impact on ongoing application sessions for which an authorization has already been provided by the RACF. + +If the contents of the request are invalid, the RACF shall return a transport resource information indication response with a Result-Code AVP value set to the appropriate value as described in clause 7.1. + +If the creation or modification of the session record is successful but a failure occurs during the processing of the default configuration (e.g., due to a failure in the interaction with the PE-PE), the RACF shall return a transport resource information indication response with a Result-Code AVP value set to DIAMETER\_LIMITED\_SUCCESS. + +If the RACF 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 transport resource information indication response with a Result-Code AVP value set to DIAMETER\_UNABLE\_TO\_COMPLY or an Experimental-Result-Code AVP set to DIAMETER\_SYSTEM\_UNAVAILABLE. In the latter case, the TLM-PE is expected to retry after a provisioned time period. + +Otherwise, the requested operation shall take place and the RACF shall return the Result-Code AVP set to DIAMETER\_SUCCESS in the transport resource information indication response. + +### 7.2.3 Transport resource release notification + +#### 7.2.3.1 Overview + +This procedure is used by the TLM-PE to report loss of IP connectivity. This enables the RACF to remove the access profile from its internal database. This event occurs in case the allocated IP address is released (e.g., DHCP leased timer expiry) or due to a release of the underlying layer 2 resources. + +This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 9. Tables 7-6 and 7-7 detail the involved information elements as defined in the RACF specification [ITU-T Y.2111] and their mapping to Diameter AVPs. + +**Table 7-6 – Transport resource release notification** + +| Information element name | Mapping to Diameter AVP | Category | +|----------------------------|-------------------------|----------| +| Globally unique IP address | Globally-Unique-Address | M | +| Transport subscriber ID | User-Name | O | + +**Table 7-7 – Transport resource release notification response** + +| Information element name | Mapping to Diameter AVP | Category | +|-------------------------------|---------------------------------|----------| +| Result (see Note) | Result-Code/Experimental-Result | M | +| NOTE – Result of the request. | | | + +Result-Code AVP shall be used for errors defined in the Diameter base protocol. + +Experimental-Result AVP shall be used for other errors. This is a grouped AVP which contains a Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. + +#### 7.2.3.2 Procedure at the TLM-PE side + +On receipt of an external event indicating that the allocated IP address has been released or the underlying layer 2 connection has been lost, the TLM-PE shall clear all information stored against the IP address and issue a Push-Notification-Request representing a transport resource release notification. + +NOTE – Receipt of an indication that a layer 2 connection has been lost may lead the TLM-PE to issue several notifications, in case multiple access sessions where associated with this connection. + +#### 7.2.3.3 Procedure at the RACF side + +If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the RACF shall stop processing the request and set the Experimental-Result-Code to DIAMETER\_ERROR\_USER\_UNKNOWN in the transport resource release notification response. + +If the globally unique identifier contained in the Globally-Unique-Address AVP is already known, the RACF shall: + +- remove the existing session record; +- interact with transfer layer entities (i.e., PE-PE) to remove transport policies associated with the session and clear associated resources; +- notify the SCE. + +If the RACF 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 set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY or an Experimental-Result-Code set to DIAMETER\_SYSTEM\_UNAVAILABLE. In the latter case, the TLM-PE is expected to retry after a provisioned time period. + +Otherwise, the requested operation shall take place and the RACF shall return an IP-Connectivity-Release-Indication response with the Result-Code AVP set to DIAMETER\_SUCCESS. + +# **8 Selection and the use of the protocol** + +The Diameter base protocol [b-IETF RFC 3588] shall be used for the Ru interface with the clarifications listed in the following clauses. + +## **8.1 Security** + +For secure transport of Diameter messages, Internet Protocol security (IPSec) may be used. Guidelines on the use of SCTP with IPSec can be found in [b-IETF RFC 3554]. + +## **8.2 Accounting** + +This functionality (accounting session state machine, related command codes and AVPs) is not used on the Ru interface. + +## **8.3 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. + +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 [b-IETF RFC 3588]. 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. + +## **8.4 Transport protocol** + +Diameter messages over the Ru interface shall make use of SCTP specified in [b-IETF RFC 2960] and shall utilize the new SCTP checksum method specified in [b-IETF RFC 3309]. + +## **8.5 Routing considerations** + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +Requests initiated by the TLM-PE towards the PD-PE shall include both Destination-Host and Destination-Realm AVPs. The TLM-PE obtains the Destination-Host AVP to use in requests towards a PD-PE from configuration data and/or the subscriber profile. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the TLM-PE. + +Requests initiated by the PD-PE towards the TLM-PE shall include both Destination-Host and Destination-Realm AVPs. The PD-PE obtains the Destination-Host AVP to use in requests towards + +a TLM-PE, from the configuration data. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the PD-PE. + +Destination-Realm AVP is declared as mandatory in the augmented Backus-Naur form (ABNF) for all requests. + +## 8.6 Application advertisement + +The TLM-PE and PD-PE shall advertise support of the Ru-specific application by including the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of ITU-T (11502) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. Additionally, support of ETSI AVPs and/or 3GPP AVPs shall be advertised by adding the vendor identifier value of ETSI (13019) and/or 3GPP (10415) to the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +NOTE – A Vendor-Id AVP included in the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above indicates the manufacturer of the Diameter node as per [b-IETF RFC 3588]. + +# 9 Ru protocol specification + +This clause specifies a Diameter application that allows a Diameter server and a Diameter client to exchange information related to IP-connectivity sessions. The Diameter application identifier assigned to this application is 16777262. + +The Diameter base protocol as specified in [b-IETF RFC 3588] is used to support information transfer on both interfaces. + +[b-IETF RFC 3588] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in this clause. Unless otherwise specified, the procedures (including error handling and unrecognized information handling) are unmodified. + +## 9.1 Commands + +This Recommendation re-uses and modifies commands defined in the Sh application [ETSI TS 129 329] for the Sh interface. Existing Diameter command codes from the Sh application are used. Only the following commands defined in the Sh application are used. Any other command defined in the Sh application shall be ignored. + +**Table 9-1 – Command-code values** + +| Command | Abbreviation | Defining reference | Command code | +|---------------------------|--------------|--------------------|--------------| +| User-Data-Request | UDR | [ETSI TS 129 329] | 306 | +| User-Data-Answer | UDA | [ETSI TS 129 329] | 306 | +| Push-Notification-Request | PNR | [ETSI TS 129 329] | 309 | +| Push-Notification-Answer | PNA | [ETSI TS 129 329] | 309 | + +AVPs defined in the Sh application and not used in this Recommendation are not shown in the following clauses. When received, these AVPs shall be ignored by the TLM-PE and the PD-PE. + +Table 9-2 defines the mapping between the information flows defined in clause 7.2 and Diameter commands. + +**Table 9-2 – Ru message mapping to Diameter command** + +| Ru message | Source | Destination | Command name | Command code | +|----------------------------------------------------|---------------|--------------------|---------------------------|---------------------| +| Transport resource information request | PD-PE | TLM-PE | User-Data-Request | 306 | +| Transport resource information response | TLM-PE | PD-PE | User-Data-Answer | 306 | +| Transport resource information indication | TLM-PE | PD-PE | Push-Notification-Request | 309 | +| Transport resource information indication response | PD-PE | TLM-PE | Push-Notifications-Answer | 309 | +| Transport resource release notification | TLM-PE | PD-PE | Push-Notification-Request | 309 | +| Transport resource release notification response | PD-PE | TLM-PE | Push-Notifications-Answer | 309 | + +### 9.1.1 User-Data-Request (UDR) command + +The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the "R" bit set in the command flags field, is sent by a Diameter client to a Diameter server in order to request user data. This command is defined in the Sh application and used with additional AVPs defined in the NASS e4 interface [ETSI ES 283 034]. + +Message format: + +``` +< User-Data-Request > ::= < Diameter Header: 306, REQ, PXY, 16777262 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [Globally-Unique-Address] + [User-Name] + * [ AVP ] + * [ Proxy-Info ] + * [ Route-Record ] +``` + +### 9.1.2 User-Data-Answer (UDA) command + +The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the "R" bit cleared in the command flags field, is sent by a server in response to the User-Data-Request command. This command is defined in the Sh application and used with additional AVPs defined in the NASS e4 interface. The Experimental-Result AVP may contain one of the values defined in clause 9.2 or in the Cx and Dx application [ETSI TS 129 229]. + +Message format: + +``` +< User-Data-Answer > ::= < Diameter Header: 306, PXY, 16777262 > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } +``` + +``` + +{ Origin-Realm } +[Globally-Unique-Address] +[User-Name] +[Logical-Access-Id] +[Physical-Access-Id] +[Access-Network-Type] +[Initial-Gate-Setting] +* [QoS-Profile] +* [ AVP ] +* [ Failed-AVP ] +* [ Proxy-Info ] +* [ Route-Record ] + +``` + +### 9.1.3 Push-Notification-Request (PNR) 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 the Sh application and used with additional AVPs defined in the NASS e4 interface. + +Message format: + +``` + +< Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777262 > +< Session-Id > +{ Vendor-Specific-Application-Id } +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +{ Destination-Host } +{ Destination-Realm } +[Globally-Unique-Address] +[User-Name] +[Logical-Access-Id] +[Physical-Access-Id] +[Access-Network-Type] +[Initial-Gate-Setting] +* [QoS-Profile] +* [ AVP ] +* [ Proxy-Info ] +* [ Route-Record ] + +``` + +### 9.1.4 Push-Notification-Answer (PNA) 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. This command is defined in the Sh application. The Experimental-Result AVP may contain one of the values defined in clause 9.2 or in the Cx and Dx application [ETSI TS 129 229]. + +Message format: + +``` + +< Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777262 > +< Session-Id > +{ Vendor-Specific-Application-Id } +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +* [ AVP ] +* [ Failed-AVP ] +* [ Proxy-Info ] +* [ Route-Record ] + +``` + +## 9.2 Result-Code AVP values + +This clause defines new result code values that must be supported by all Diameter implementations that conform to this Recommendation. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent. + +### 9.2.1 Success + +Result codes that fall within the success category are used to inform a peer that a request has been successfully completed. No result codes within this category have been defined so far. + +### 9.2.2 Permanent failures + +Errors that fall within the permanent failures category are used to inform the peer that the request failed, and should not be attempted again. + +No errors within this category have been defined so far. However, the following error defined in the Cx and Dx application is used in this Recommendation: + +- DIAMETER\_ERROR\_USER\_UNKNOWN (5001). + +When this result code is used, the 3GPP vendor ID shall be included in the vendor-Id AVP of the Experimental-Result AVP. + +### 9.2.3 Transient failures + +Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. + +This Recommendation defines the following error with this category: + +- DIAMETER\_SYSTEM\_UNAVAILABLE (4001). + +This error is returned when a request could not be satisfied at the time that it was received due to a temporary internal failure or congestion. When this result code is used, the ETSI vendor ID shall be included in the Vendor-Id AVP of the Experimental-Result AVP. + +The following error defined in the Sh application is also used in this Recommendation: + +- DIAMETER\_USER\_DATA\_NOT\_AVAILABLE (4100) + +When this result code is used, the 3GPP vendor ID shall be included in the Vendor-Id AVP of the Experimental-Result AVP. + +## 9.3 AVPs + +The following tables summarize the AVPs used in this Recommendation beyond those defined in the Diameter base protocol. + +Table 9-3 describes the Diameter AVPs defined in this Recommendation, their AVP code values, types, possible flag values and whether the AVP may or not be encrypted. The Vendor-Id header of all AVPs defined in this Recommendation shall be set to ETSI (13019). + +NOTE – In the following tables, AVP header bit denoted as "M" indicates that support of the AVP is mandatory. AVP header bit denoted as "V" indicates that the optional Vendor-ID field is present in the AVP header. + +**Table 9-3 – Diameter AVPs imported from the NASS e4 interface** + +| Attribute name | AVP code | Reference | Value type | AVP flag rules | | | | | +|------------------------------|----------|-------------------|-------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | May encrypt | +| Globally-Unique-Address | 300 | [ETSI ES 283 034] | Grouped | M, V | | | | Yes | +| Address-Realm | 301 | [ETSI ES 283 034] | OctetString | M, V | | | | Yes | +| Logical-Access-Id | 302 | [ETSI ES 283 034] | OctetString | V | M | | | Yes | +| Initial-Gate-Setting | 303 | [ETSI ES 283 034] | Grouped | V | M | | | Yes | +| QoS-Profile | 304 | [ETSI ES 283 034] | Grouped | V | M | | | Yes | +| IP-Connectivity-Status | 305 | [ETSI ES 283 034] | Enumerated | V | M | | | Yes | +| Access-Network-Type | 306 | [ETSI ES 283 034] | Grouped | V | M | | | Yes | +| Aggregation-Network-Type | 307 | [ETSI ES 283 034] | Enumerated | V | M | | | Yes | +| Maximum-Allowed-Bandwidth-UL | 308 | [ETSI ES 283 034] | Unsigned32 | V | M | | | Yes | +| Maximum-Allowed-Bandwidth-DL | 309 | [ETSI ES 283 034] | Unsigned32 | V | M | | | Yes | +| Transport-Class | 311 | [ETSI ES 283 034] | Unsigned32 | V | M | | | Yes | +| Application-Class-ID | 312 | [ETSI ES 283 034] | UTF8String | V | M | | | Yes | +| Physical-Access-ID | 313 | [ETSI ES 283 034] | UTF8String | V | M | | | Yes | + +Table 9-4 describes the Diameter AVPs defined for the NAS application [b-IETF RFC 4005] and used in this Recommendation, their AVP code values, types, possible flag values and whether the AVP may or not be encrypted. Flag values are described in the context of this Recommendation rather than in the context of the application where they are defined. AVPs defined in [b-IETF RFC 4005] but not listed in Table 9-4 should not be sent by Diameter conforming to this Recommendation and shall be ignored by receiving entities. No Vendor-Id shall be included in the AVP header. + +**Table 9-4 – Diameter AVPs imported from the NAS application** + +| Attribute name | AVP code | Reference | Value type | AVP flag rules | | | | | +|--------------------|----------|-----------------|--------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | May encrypt | +| NAS-Port-Type | 61 | [IETF RFC 4005] | Enumerated | | M | | V | Yes | +| NAS-Filter-Rule | 400 | [IETF RFC 4005] | IPFilterRule | | M | | V | Yes | +| Framed-IP-Address | 8 | [IETF RFC 4005] | OctetString | | M | | V | Yes | +| Framed-IPv6-Prefix | 97 | [IETF RFC 4005] | OctetString | | M | | V | Yes | + +Table 9-5 describes the Diameter AVPs defined for the Gq' application [ETSI TS 183 017] and used in this Recommendation, their AVP code values, types, possible flag values and whether the AVP may or not be encrypted. Flag values are described in the context of this Recommendation rather than in the context of the application where they are defined. AVPs defined in [ETSI TS 183 017] but not listed in Table 9-5 should not be sent by Diameter conforming to this Recommendation and shall be ignored by receiving entities. The Vendor-Id header for these AVPs shall be set to ETSI (13019). + +**Table 9-5 – Diameter AVPs imported from the Gq' specification** + +| Attribute name | AVP code | Reference | Value type | AVP flag rules | | | | | +|----------------------|----------|-------------------|------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | May encrypt | +| Reservation-Priority | 458 | [ETSI TS 183 017] | Unsigned32 | V | | | M | Yes | + +### **9.3.1 Globally-Unique-Address AVP** + +The Globally-Unique-Address AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.2 Address-Realm AVP** + +The Address-Realm AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.3 Logical-Access-Id AVP** + +The Logical-Access-Id AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.4 Initial-Gate-Setting AVP** + +The Initial-Gate-Setting AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.5 QoS-Profile AVP** + +The QoS-Profile AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.6 IP-Connectivity-Status AVP** + +The IP-Connectivity-Status AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.7 Access-Network-Type AVP** + +The Access-Network-Type AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.8 Aggregation-Network-Type AVP** + +The Aggregation-Network-Type AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.9 Maximum-Allowed-Bandwidth-UL AVP** + +The Maximum-Allowed-Bandwidth-UL AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.10 Maximum-Allowed-Bandwidth-DL AVP** + +The Maximum-Allowed-Bandwidth-DL AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.11 Transport-Class AVP** + +The Transport-Class AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.12 Application-Class-ID AVP** + +The Application-Class-ID AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.13 Physical-Access-ID AVP** + +The Physical-Access-ID AVP is defined in the NASS e4 interface, specified in [ETSI ES 283 034]. + +### **9.3.14 NAS-Port-Type AVP** + +The NAS-Port-Type AVP is defined in the NAS application, specified in [b-IETF RFC 4005]. + +### **9.3.15 NAS-Filter-Rule AVP** + +The NAS-Filter-Rule AVP is defined in the NAS application, specified in [b-IETF RFC 4005]. + +### **9.3.16 Framed-IP-Address AVP** + +The Framed-IP-Address AVP is defined in the NAS application, specified in [b-IETF RFC 4005]. + +### **9.3.17 Framed-IPv6-Prefix AVP** + +The Framed-IPv6-Prefix AVP is defined in the NAS application, specified in [b-IETF RFC 4005]. + +### **9.3.18 Reservation-Priority AVP** + +The Reservation-Priority AVP is defined in the 3GPP Gq' interface, specified in [ETSI TS 183 017]. + +## **9.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 IANA. + +### **9.4.1 AVP codes** + +This Recommendation uses AVP values from the AVP code namespace managed by ETSI for its Diameter vendor-specific applications. See clause 9.3, Tables 9-3 to 9-5. + +### **9.4.2 Experimental-Result-Code AVP values** + +This Recommendation uses the Experimental-Result-Code AVP values from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. + +### **9.4.3 Command code values** + +This Recommendation does not assign command code values but uses existing commands defined by the IETF, including those requested by 3GPP. + +### **9.4.4 Application-ID value** + +This Recommendation defines the Ru Diameter application with application ID 16777262. The vendor identifier assigned by IANA to ITU-T () is 11502. + +# **10 Security considerations** + +The security requirements within the functional requirements and architecture of the NACF are addressed by the security requirements for NGN [ITU-T Y.2701]. The Ru interface shall follow the security requirements of the NACF. + +Clause 8.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]. + +Further security considerations are provided in the security considerations section of [b-IETF RFC 3588], which operators are advised to consult. + +# Bibliography + +- [b-ITU-T X.800] Recommendation ITU-T X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*. +- [b-IETF RFC 2960] IETF RFC 2960 (2000), *Stream Control Transmission Protocol*. +- [b-IETF RFC 3309] IETF RFC 3309 (2002), *Stream Control Transmission Protocol (SCTP) Checksum Change*. +- [b-IETF RFC 3554] IETF RFC 3554 (2003), *On the Use of Stream Control Transmission Protocol (SCTP) with IPSec*. +- [b-IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol*. +- [b-IETF RFC 4005] IETF RFC 4005 (2005), *Diameter Network Access Server Application*. + + + + + +## 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.3230-201208-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..647c80548c08886c4187332e3c71529c97e7a092 --- /dev/null +++ b/marked/Q/T-REC-Q.3230-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.3230-201208-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..079f5ab72c7eef1d47a66fa7cb7983309c7ba904 --- /dev/null +++ b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:558b01c74dde5a47680e12738bb401e5448967f100e69f4bae0690225ae6f189 +size 133059 diff --git a/marked/Q/T-REC-Q.3230-201208-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf81a1b29b2680be45c546239f0e43c182fc4521 --- /dev/null +++ b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfd13e756b7226ec8896f7b29c80feeb2499178e5a85ecb1781e17fdc6254ef0 +size 66576 diff --git a/marked/Q/T-REC-Q.3230-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b0d04bdeb8d7c54d7fa58bcdee0c1ae4f30da76 --- /dev/null +++ b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f986eb1a15531cee9f25d546e5725c3c21454651bd5440105f8c545d6d74c9d +size 10598 diff --git a/marked/Q/T-REC-Q.3230-201208-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..834376bf99d8a462389dd68ead39e407d8f6c0ff --- /dev/null +++ b/marked/Q/T-REC-Q.3230-201208-I_PDF-E/raw.md @@ -0,0 +1,664 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3230** + +(08/2012) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +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 M13 +interface between the transport location +management and network information +distribution physical entities** + +Recommendation ITU-T Q.3230 + +## 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.3230** + +## **Signalling requirements and protocol at the M13 interface between the transport location management and network information distribution physical entities** + +## **Summary** + +Recommendation ITU-T Q.3230 provides the protocol for the interface between the transport location management physical entity (TLM-PE) of the network attachment control entity (NACE) and the network information distribution physical entity (NID-PE) of the mobility management control entity (MMCE). The M13 interface provides the keying material, derived from the user equipment (UE) authentication procedure, in support of the security association required between the NID-PE and the UE. This Recommendation supports information flows providing the keying material via the M13 reference point as specified in Recommendation ITU-T Y.2018. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.3230 | 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 ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 M13 interface..... | 3 | +| 6.1 Overview ..... | 3 | +| 6.2 M13 reference model..... | 3 | +| 6.3 Physical entities and capabilities ..... | 4 | +| 7 Signalling requirements ..... | 4 | +| 7.1 Network selection key transfer indication ..... | 5 | +| 8 Description of procedure ..... | 5 | +| 8.1 General ..... | 5 | +| 8.2 Procedure on the M13 interface ..... | 5 | +| 9 Use of Diameter base protocol ..... | 7 | +| 9.1 Securing Diameter messages ..... | 7 | +| 9.2 Accounting functionality ..... | 7 | +| 9.3 Use of sessions ..... | 8 | +| 9.4 Transport protocol ..... | 8 | +| 9.5 Routing considerations ..... | 8 | +| 9.6 Advertising application support ..... | 8 | +| 10 Message specification..... | 9 | +| 10.1 Commands..... | 9 | +| 10.2 Experimental-Result-Code AVP values ..... | 10 | +| 10.3 AVPs..... | 10 | +| 10.4 Use of namespaces ..... | 11 | +| 11 Security considerations ..... | 11 | +| Bibliography..... | 12 | + + + +## Recommendation ITU-T Q.3230 + +## Signalling requirements and protocol at the M13 interface between the transport location management and network information distribution physical entities + +# 1 Scope + +This Recommendation defines the protocol for the M13 interface between the transport location management physical entity (TLM-PE) and the network information distribution physical entity (NID-PE). The M13 reference point provides the keying material derived from the user equipment (UE) 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 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*. +- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. +- [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 TS 129 229] ETSI TS 129 229 V9.3.0 (2010), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Cx and Dx interfaces based on the Diameter protocol; Protocol details (3GPP TS 29.229 version 9.3.0 Release 9) Cx and Dx interfaces based on the Diameter protocol; Protocol details*. +- [ETSI TS 129 329] ETSI TS 129 329 V6.7.0 (2006), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329 version 6.7.0 Release 6)*. +- [IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol*. +- [IETF RFC 4960] IETF RFC 4960 (2007), *Stream Control Transmission Protocol*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 authentication** [ITU-T Y.2014]: A property by which the correct identifier 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.1.2 location information** [b-ITU-T Q.1001]: The location register should, as a minimum, contain the following information about a mobile station: + +- international mobile station identity; +- actual location of the mobile station (e.g., PLMN, MSC area, location area, as required). + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|----------------------------------------------------| +| ABNF | Augmented Backus-Naur Form | +| AM-PE | Access Management Physical Entity | +| AVP | Attribute-Value Pair | +| CEA | Capabilities-Exchange-Answer | +| CER | Capabilities-Exchange-Request | +| CPE | Customer Premises Equipment | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| HDC-PE | Handover Decision and Control Physical Entity | +| HGWC-PE | Home Gateway Configuration Physical Entity | +| IANA | Internet Assigned Numbers Authority | +| IETF | Internet Engineering Task Force | +| IPSec | IP Security protocol | +| MLM-PE | Mobile Location Management Physical Entity | +| MMCE | Mobility Management Control Entity | +| NACE | Network Attachment Control Entity | +| NACF | Network Attachment Control Functions | +| NAC-PE | Network Access Configuration Physical Entity | +| NID-PE | Network Information Distribution Physical Entity | +| NIR-PE | Network Information Repository Physical Entity | +| PD-PE | Policy Decision Physical Entity | +| PLMN | Public Land Mobile Network | +| PNA | Push-Notification-Answer | + +| | | +|--------|------------------------------------------------------------| +| PNR | Push-Notification-Request | +| RACE | Resource Admission and Control Entity | +| RFC | Request For Comments | +| SCE | Service Control Entity | +| SCTP | Stream Control Transmission Protocol | +| TAA-PE | Transport Authentication and Authorization Physical Entity | +| TLM-PE | Transport Location Management Physical Entity | +| TRC-PE | Transport Resource Control Physical Entity | +| TUP-PE | Transport User Profile Physical Entity | +| UE | User Equipment | +| WiMAX | Worldwide Interoperability for Microwave Access | +| WLAN | Wireless Local Area Network | + +# 5 Conventions + +None. + +# 6 M13 interface + +## 6.1 Overview + +The network attachment control entity (NACE) maintains information about the keying material derived from the user equipment (UE) authentication procedure. This information is stored in the transport location management physical entity (TLM-PE) and is pushed to the network information distribution physical entity (NID-PE) in the mobility management control entity (MMCE). + +## 6.2 M13 reference model + +This clause describes the M13 reference architecture. Figure 6-1 can be used as an initial architecture illustration: + +![Figure 6-1 – M13 reference model diagram showing the architecture of the M13 interface. It consists of three main functional blocks: NACE, MMCE, and RACE. The NACE block contains TUP-PE, HGWC-PE, TAA-PE, TLM-PE, NAC-PE, AM-PE, and NID-PE. The MMCE block contains MLM-PE, HDC-PE, NID-PE, NIR-PE, and MMCE. The RACE block contains PD-PE, TRC-PE, and RACE. Interfaces are labeled M1, M2, M8, M10, M11, M12, M13, Nx, Nc, Ne, Nk, Nd, Nb, Ni, Na, and Nx. A dashed box labeled 'Scope of this Recommendation' highlights the M13 interface between TLM-PE and NID-PE.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +The diagram illustrates the M13 reference model architecture. It is divided into three main functional blocks: NACE (Network Attachment Control Entity), MMCE (Mobility Management Control Entity), and RACE (Resource Admission and Control Entity). + +- NACE Block:** Contains the following Physical Entities (PEs): + - HGWC-PE + - TUP-PE + - TAA-PE + - TLM-PE + - NAC-PE + - AM-PE + - NID-PE +Interfaces within NACE: + - HGWC-PE connects to TLM-PE via Nx. + - TUP-PE connects to TAA-PE via Nb. + - TAA-PE connects to TLM-PE via Nc. + - TAA-PE connects to NAC-PE via Nk. + - TAA-PE connects to AM-PE via Na. + - TAA-PE has a self-loop labeled Ni. + - NAC-PE connects to TLM-PE via Ne. + - NAC-PE connects to AM-PE via Nd. +- MMCE Block:** Contains the following PEs: + - MLM-PE + - HDC-PE + - NID-PE + - NIR-PE + - MMCE +Interfaces within MMCE: + - MLM-PE connects to HDC-PE via M10. + - HDC-PE connects to NID-PE via M11. + - NID-PE connects to NIR-PE via M12. +- RACE Block:** Contains the following PEs: + - PD-PE + - TRC-PE + - RACE +Interfaces within RACE: + - PD-PE connects to TRC-PE via M8. + +**Inter-Block Interfaces:** + +- TLM-PE (NACE) connects to MLM-PE (MMCE) via M1. +- TLM-PE (NACE) connects to HDC-PE (MMCE) via M2. +- A dashed box labeled "Scope of this Recommendation" highlights the M13 interface between TLM-PE (NACE) and NID-PE (MMCE). + +Figure 6-1 – M13 reference model diagram showing the architecture of the M13 interface. It consists of three main functional blocks: NACE, MMCE, and RACE. The NACE block contains TUP-PE, HGWC-PE, TAA-PE, TLM-PE, NAC-PE, AM-PE, and NID-PE. The MMCE block contains MLM-PE, HDC-PE, NID-PE, NIR-PE, and MMCE. The RACE block contains PD-PE, TRC-PE, and RACE. Interfaces are labeled M1, M2, M8, M10, M11, M12, M13, Nx, Nc, Ne, Nk, Nd, Nb, Ni, Na, and Nx. A dashed box labeled 'Scope of this Recommendation' highlights the M13 interface between TLM-PE and NID-PE. + +Figure 6-1 – M13 reference model + +## 6.3 Physical entities and capabilities + +### 6.3.1 TLM-PE + +The TLM-PE responds to location queries from service control functions and applications. The actual information delivered by the TLM-PE may take various forms (e.g., network location, geographical coordinates, postal address, etc.) depending on the agreement with the requester and on user preferences regarding the privacy of its location. + +The TLM-PE may play several roles, i.e., the home role, the local role, or both. In its home role the TLM-PE stores a pointer to the TLM-PE instance that is playing the local role for the attachment. The current location information of the user/CPE in the access domain is stored and bound in the local TLM-PE. Thus, when the user/CPE moves in the same access domain, only the location binding information of the local TLM-PE needs to be updated; the location binding information of the home TLM-PE does not need to be updated. + +The local TLM-PE is in the access network to which the terminal equipment is attached. The home TLM-PE is in the network designated by the TUP-PE. Where these networks differ, communication between the local and home TLM-PE instances takes place over the Ng reference point. Namely, the home TLM-PE may provide the SCE with user network profile information through the local TLM-PE of the visited network in order to support mobility when the user is nomadic. + +Similarly, the home TLM-PE is able to provide the SCE with user network profile information through the local TLM-PE of another service provider for roaming on such an access network. + +The functionality of the TLM-PE is further detailed in clause 7.2.3 of [ITU-T Y.2014]. + +### 6.3.2 NID-PE + +The NID-PE communicates with the entity making the handover decision during the network discovery phase. The handover decision may be made by either the UE or the handover decision and control physical entity (HDC-PE). The NID-PE has the following responsibilities: + +- Distributing handover policy, which is a set of operator-defined rules and preferences that affect the handover decisions taken by the UE or HDC-PE. + +For example, a handover policy can indicate that vertical handover from E-UTRAN access to WLAN access is not allowed. It can also indicate, e.g., that WiMAX access is preferable to WLAN access. + +- Distributing other information provided by the NIR-PE. + +The functionality of the NID-PE is further detailed in clause 6.4 of [ITU-T Y.2018]. + +# 7 Signalling requirements + +The M13 reference point allows the TLM-PE to interact with the NID-PE for pushing mobility service parameters such as keying material, in support of the security association required between the NID-PE and the UE. + +The M13 reference point is an intra-domain reference point. + +The M13 reference point allows information exchange as follows: + +- The mobility service parameters information is pushed by the TLM-PE to the NID-PE (see Figure 7-1). + +For further information, refer to clause 8.5.3 of [ITU-T Y.2014]. + +![Diagram showing information flow from TLM-PE to NID-PE labeled 'Network selection key transfer indication'. Reference Q.3230(12)_F7.1](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +graph LR + TLM-PE -- "Network selection key transfer indication" --> NID-PE + style TLM-PE fill:#fff,stroke:#000 + style NID-PE fill:#fff,stroke:#000 + +``` + +Diagram showing information flow from TLM-PE to NID-PE labeled 'Network selection key transfer indication'. Reference Q.3230(12)\_F7.1 + +**Figure 7-1 – Information flow** + +## **7.1 Network selection key transfer indication** + +This information flow provides the keying material derived from the UE authentication procedure, in support of the security association required between the NID-PE and the UE. This security association is required for the ongoing network selection and decision process subsequent to attachment. + +The network selection key transfer indication flow contains the following information shown in Table 7-1. + +**Table 7-1 – Network selection key transfer indication (TLM-PE → NID-PE)** + +| Information Element | Explanation | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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. | +| Keying material | The material used for security association between the UE and NID-PE. | + +# **8 Description of procedure** + +## **8.1 General** + +The following clauses describe the realization of the functional procedures defined in the NACE specifications using Diameter commands described in clause 10. This involves describing a mapping between the information elements defined in the NACE specification and Diameter attribute-value pairs (AVPs). + +In the tables that describe this mapping, each information element is marked as (M) Mandatory, (C) Conditional or (O) Optional. See [ETSI ES 283 034]. + +## **8.2 Procedure on the M13 interface** + +### **8.2.1 Network selection key transfer indication** + +#### **8.2.1.1 Overview** + +This procedure is used by the TLM-PE to notify the NID-PE of the occurrence of the keying material information. + +This procedure is mapped to the commands Push-Notifications-Request/Answer in the Diameter application specified in the Sh interface [ETSI TS 129 329]. Tables 8-1 and 8-2 detail the involved information elements as defined in the NACE and their mapping to Diameter AVPs. + +**Table 8-1 – Network selection key transfer indication request** + +| Information Element name | Mapping to Diameter AVP | Category | +|---------------------------------|-------------------------|----------| +| Unique IP Address | Globally-Unique-Address | C | +| Address Realm | | | +| Transport Subscriber Identifier | User-Name | C | +| Keying material | Keying-Material | M | + +**Table 8-2 – Network selection key transfer indication response** + +| Information Element name | Mapping to Diameter AVP | Category | +|--------------------------|----------------------------------|----------| +| Result | Result-Code/Experimental_ Result | M | + +#### **8.2.1.2 Procedure at the TLM-PE** + +The TLM-PE shall request the network selection key transfer indication request by including the following information elements: + +- 1) At a minimum, a Globally-Unique-Address AVP or a User-Name AVP shall be included. The Globally-Unique-Address AVP shall contain a Frame-IP-Address AVP or a Frame-IPv6-Prefix AVP, and an Address-Realm AVP. +- 2) The Keying-Material AVP shall be present. + +#### **8.2.1.3 Procedure at the NID-PE** + +Upon reception of a network selection key transfer indication request (see Figure 8-1), the NID-PE shall: + +- 1) Check both the Globally-Unique-Address AVP and the User-Name AVP. +- 2) If the Globally-Unique-Address AVP is present, go to step 6). Otherwise, go to the next step. +- 3) If the Globally-Unique-Address AVP is absent, but the User-Name AVP is present, go to step 5). Otherwise, go to the next step. +- 4) Because both the Globally-Unique-Address AVP and the User-Name AVP are absent, return a network selection key transfer indication response with Result-Code set to DIAMETER\_MISSING\_AV and stop this procedure. Otherwise, go to the next step. +- 5) If more than one record include the same subscriber identity matching the value of the User-Name AVP and no Globally-Unique-Address AVP is included, return a network selection key transfer indication response with Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY and stop this procedure. Otherwise, go to the next step. +- 6) If no session record is stored for the Globally-Unique-Address AVP or the User-Name AVP, return network selection key transfer indication response with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_USER\_UNKNOWN and stop this procedure. Otherwise, go to the next step. +- 7) If the Keying-Material AVP is absent, return a network selection key transfer indication response with the Result-Code set to DIAMETER\_MISSING\_AV and stop this procedure. Otherwise, go to the next step. +- 8) Under temporary overload conditions, the NID-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 and stop this procedure. Otherwise, go to the next step. + +- 9) If the NID-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 NID-PE shall return the Result-Code AVP set to DIAMETER\_SUCCESS in the network selection key transfer indication response and stop this procedure. + +![Flowchart for network selection key transfer indication on the NID-PE side. The process starts with 'NULL', followed by checking Globally-Unique-Address AVP and User-Name AVP. It then enters a series of decision diamonds: 'Is Globally-Unique-Address AVP present?', 'Is User-Name AVP present?', 'Does Subscriber Identity Matching Globally-Unique-Address AVP exist?', 'Does Subscriber Identity Matching User-Name AVP exist?', 'Is Keying-Material AVP present?', 'Under temporary overload conditions?', and 'Database error or other error?'. Each decision leads to either a response box or the next decision step.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +``` + +graph TD + NULL([NULL]) --> CheckAVP[Check both Globally-Unique-Address AVP and User-Name AVP] + CheckAVP --> IsGUA{Is Globally-Unique-Address AVP present?} + IsGUA -- No --> IsUNA{Is User-Name AVP present?} + IsUNA -- No --> R1[Return the network selection key transfer indication response with Result-Code = DIAMETER_MISSING_AVP] + IsUNA -- Yes --> DoesSIM_UN{Does Subscriber Identity Matching User-Name AVP exist?} + DoesSIM_UN -- No --> R2[Return the network selection key transfer indication response with Experimental-Result-Code = DIAMETER_ERROR_USER_UNKNOWN] + DoesSIM_UN -- Yes --> IsKM{Is Keying-Material AVP present?} + IsKM -- No --> R3[Return the network selection key transfer indication response with Result-Code = DIAMETER_MISSING_AVP] + IsKM -- Yes --> Overload{Under temporary overload conditions?} + Overload -- Yes --> R4[Return the network selection key transfer indication response with Experimental-Result-Code = DIAMETER_USER_DATA_NOT_AVAILABLE] + Overload -- No --> Error{Database error or other error?} + Error -- Yes --> R5[Return the network selection key transfer indication response with Result-Code = DIAMETER_UNABLE_TO_COMPLY] + Error -- No --> R6[Return the network selection key transfer indication response with Result-Code = DIAMETER_SUCCESS] + IsGUA -- Yes --> DoesSIM_GUA{Does Subscriber Identity Matching Globally-Unique-Address AVP exist?} + DoesSIM_GUA -- No --> R7[Return the network selection key transfer indication response with Experimental-Result-Code = DIAMETER_ERROR_USER_UNKNOWN] + DoesSIM_GUA -- Yes --> IsKM + +``` + +Flowchart for network selection key transfer indication on the NID-PE side. The process starts with 'NULL', followed by checking Globally-Unique-Address AVP and User-Name AVP. It then enters a series of decision diamonds: 'Is Globally-Unique-Address AVP present?', 'Is User-Name AVP present?', 'Does Subscriber Identity Matching Globally-Unique-Address AVP exist?', 'Does Subscriber Identity Matching User-Name AVP exist?', 'Is Keying-Material AVP present?', 'Under temporary overload conditions?', and 'Database error or other error?'. Each decision leads to either a response box or the next decision step. + +Q.3230(12)\_F8-1 + +**Figure 8-1 – Procedure for network selection key transfer indication on the NID-PE side** + +# **9 Use of Diameter base protocol** + +With the clarifications listed in the following clauses the Diameter base protocol defined by [IETF RFC 3588] shall apply. + +## **9.1 Securing Diameter messages** + +For secure transport of Diameter messages, IP security (IPSec) may be used. Guidelines on the use of SCTP with IPSec can be found in [b-IETF RFC 3554]. + +## **9.2 Accounting functionality** + +Accounting functionality (i.e., accounting session state machine, related command codes and AVPs) is not used at the M13 interface. + +## 9.3 Use of sessions + +Diameter sessions are implicitly terminated. An implicitly terminated session is one in 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. See [IETF RFC 3588]. + +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 3588]. As a consequence, the server does not maintain state information about this session and the client does not need to send a 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 M13 interface shall make use of stream control transmission protocol (SCTP) as specified in [IETF RFC 4960] and shall utilize the new SCTP checksum method also 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 protocol used at the M13 interface, the TLM-PE acts as a Diameter server and the NID-PE acts as a Diameter client. + +Requests initiated by the TLM-PE towards the NID-PE shall include both Destination-Host and Destination-Realm AVPs. The TLM-PE obtains the Destination-Host AVP, to use in requests towards the NID-PE, from configuration data and/or the subscriber profile. Consequently, the Destination-Host AVP is declared as mandatory in the Augmented Backus-Naur Form (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 3588]. The Diameter base application identifier (0) shall be used in the Diameter message header of these messages. + +If the TLM-PE and NID-PE indicate support of the M13 application, then the M13 application identifier (16777307) shall be used in the Diameter message header of all subsequent messages exchanged within this association. + +Support of the M13 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 M13 (16777307). + +The TLM-PE and the NID-PE 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 for vendor identifiers for M13. + +**Table 9-1 – Vendor identifiers for M13** + +| Vendor | Vendor identifier | +|---------------|--------------------------| +| 3GPP | 10415 | +| ETSI | 13019 | +| ITU-T | 11502 | + +NOTE – The Vendor-Id AVP included in CER and CEA 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 3588]. + +# 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 the NID-PE. See the command code in 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 PNR 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 the client of changes to the user data in the server. This command is defined in [ETSI TS 129 329] and is used with additional AVPs defined in this Recommendation. + +*Message Format:* + +``` +< Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777307> + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [ Globally-Unique-Address ] + [ User-Name ] + { Keying-Material } + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +### 10.1.2 PNA 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 PNR command. The Experimental-Result AVP may contain one of the values defined in clause 10.2. + +*Message Format:* + +``` +< Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777307> + < 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 values are imported from 3GPP and ETSI specifications, as indicated in the clauses below. + +### 10.2.1 Experimental-Result-Code AVP values imported from ETSI TS 129 229 + +This clause defines the specific values of the Experimental-Result-Code AVP imported from [ETSI TS 129 229] (the 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 AVPs + +The following tables summarize the AVPs used in this Recommendation. These are, in addition to the AVPs, defined in [IETF RFC 3588]. + +Table 10-2 describes the Diameter AVPs defined by the e4 interface protocol [ETSI ES 283 034] and used within this Recommendation. These AVPs are described in this Recommendation for information; however, the normative details for these AVPs are 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 | + +Table 10-3 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-3 – Diameter AVPs defined in this Recommendation** + +| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt | +|-----------------|----------|----------------|--------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | | +| Keying-Material | 1040 | 10.3.2 | Octet String | M,V | | | | Y | + +### 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 Keying-Material AVP + +The Keying-Material AVP (AVP code 1040 11502) is of type Octet String, and provides the material used for security association between the UE and NID-PE. + +## 10.4 Use of namespaces + +This clause contains the values assigned to 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 M13 Diameter application with application ID 16777307. The vendor identifier assigned by IANA to ITU-T is 11502 (). + +# 11 Security considerations + +The security requirements within the functional requirements and architecture of the network attachment control functions (NACF) are addressed by the security requirements for NGN [ITU-T Y.2701]. The M13 interface shall follow the security requirements of the NACF as specified in [ITU-T Y.2014]. + +Clause 9.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]. + +Further considerations are provided in the security considerations section of [IETF RFC 3588]. + +# Bibliography + +- [b-ITU-T Q.1001] Recommendation ITU-T Q.1001 (1988), *General aspects of public land mobile networks.* +- [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 | 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.3303.0-200711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3303.0-200711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/Q/T-REC-Q.3303.0-200711-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.3303.0-200711-I_PDF-E/ee8536b235eb6aad21e2048fd5308900_img.jpg b/marked/Q/T-REC-Q.3303.0-200711-I_PDF-E/ee8536b235eb6aad21e2048fd5308900_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2ba5dffeda3d224271e6e8e0b7e3d99f768ba1a --- /dev/null +++ b/marked/Q/T-REC-Q.3303.0-200711-I_PDF-E/ee8536b235eb6aad21e2048fd5308900_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11a207f2c0d13caaf3b7a4feffa9f168eb9382bc33b9110d1620a915e8a60a0a +size 57305 diff --git a/marked/Q/T-REC-Q.3303.0-200711-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3303.0-200711-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..67b5788d5c878e44295d120298638f7a5cb9716d --- /dev/null +++ b/marked/Q/T-REC-Q.3303.0-200711-I_PDF-E/raw.md @@ -0,0 +1,429 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3303.0** + +(11/2007) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Resource control protocols + +--- + +**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 Recommendation Q.3303.0 + +# 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. + +## **ITU-T Recommendation Q.3303.0** + +## **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** + +## **Summary** + +Interface Rw defines an interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE). There are a number of signalling alternatives for Rw, each is defined in a protocol-specific Recommendation in the Q.3303.x-series of Recommendations. + +ITU-T Recommendation Q.3303.0 provides a protocol-independent introduction, describing the common material, which is relevant for all protocol specific signalling solutions. + +### **Source** + +ITU-T Recommendation Q.3303.0 was approved on 6 November 2007 by ITU-T Study Group 11 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Rw interface..... | 3 | +| 6.1 Overview ..... | 3 | +| 6.2 Rw reference model..... | 4 | +| 6.3 Functional elements and capabilities..... | 4 | +| Bibliography..... | 9 | + + + +# **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** + +## **1 Scope** + +Interface Rw defines an interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE). There are a number of signalling alternatives for Rw, defined in protocol-specific Recommendations in the Q.3303.x-series of Recommendations. + +This Recommendation provides a protocol-independent introduction, describing the common material, which is relevant for all protocol specific signalling solutions. In particular, the scope of this Recommendation includes the following aspects: + +- overview; +- Rw reference model; +- functional elements and capabilities. + +## **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] ITU-T Recommendation Q.3300 (2008), *Architectural framework for the Q.33xx series of Recommendations*. + +[ITU-T Y.2012] ITU-T Recommendation Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. + +[ITU-T Y.2111] ITU-T Recommendation Y.2111 (2006), *Resource and admission control functions in Next Generation Networks*. + +## **3 Definitions** + +## **3.1 Terms defined elsewhere** + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 policy decision physical entity (PD-PE)** [ITU-T Q.3300]: The PD-PE is an implemented instance of the policy decision functional entity (PD-FE) identified in [ITU-T Y.2111]. + +**3.1.2 policy enforcement physical entity (PE-PE)** [ITU-T Q.3300]: The PE-PE is an implemented instance of the policy enforcement functional entity (PE-FE) identified in [ITU-T Y.2111]. + +**3.1.3 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: + +| | | +|-------|--------------------------------------| +| BGW | Border Gateway | +| BRAS | Broadband Remote Access Server | +| CDMA | Code Division Multiple Access | +| CNPS | Core Network Path Selection | +| CMTS | Cable Modem Termination System | +| COPS | Common Open Policy Service | +| DSL | Digital Subscriber Line | +| DSLAM | DSL Access Multiplexer | +| FDP | Final Decision Point | +| FWMS | Firewall Working Mode Selection | +| GC | Gate Control | +| GGSN | Gateway GPRS Support Node | +| GPRS | General Packet Radio Service | +| IP | Internet Protocol | +| IPMC | IP Packet Marking Control | +| MG | Media Gateway | +| NAPT | Network Address and Port Translation | +| NAPTC | NAPT Control | +| NAT | Network Address Translation | +| NS | Network Selection | +| PDG | Packet Data Gateway | +| PDP | Packet Data Protocol | +| PDSN | Packet Data Serving Node | +| QMTI | QoS Mapping – Technology Independent | +| QoS | Quality of Service | +| RLC | Rate Limiting Control | +| SCE | Service Control Entity | +| SCF | Service Control Function | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| VLAN | Virtual LAN | + +| | | +|------|-----------------------------| +| VPN | Virtual Private Network | +| WLAN | Wireless Local Area Network | + +## 5 Conventions + +*None.* + +# 6 Rw interface + +## 6.1 Overview + +As defined in the stage 2 specifications [ITU-T Y.2111] and [b-ITU-T Q-Sup.51], the Rw interface is used for information exchange to apply policy decisions between the PD-PE and the PE-PE that may reside in various transport devices, e.g., BGW, DSLAM/BRAS and GGSN/PDSN. + +The Rw interface shall be an intra-operator interface. One PD-PE instance may be able to serve more than one PE-PE instance, and one given PE-PE instance may interact with more than one PD-PE instance. For any individual session, one PD-PE instance shall make the final policy decisions in a single operator domain. + +The Rw interface shall be understood by the both sides of PD-PE and PE-PE which means PD-PE shall know which protocol is bound with the given PE-PE. The binding relationship can be static using dedicated well-known transport ports. + +In the case when PE-PE resides in various transport devices, we can use other port value (outside the well-known port range), which is a subject of a mutual agreement (= provisioning) between PE-PE and PD-PE. Alternatively, we can establish a binding relationship between PE-FE and PD-FE according to the terminal type. + +The Rw interface allows the PD-PE to *push* the admission decisions to the PE-PE. It also allows the PE-PE to *request* admission decisions when path-coupled resource reservation mechanisms are in use. The PD-PE may specify: + +- resources to be reserved and/or committed for media flows; +- QoS handling such as packet marking and policing to use; +- gate control (opening/closing) for a media flow; +- insertion of a NAPT function, requesting the necessary address mapping information; +- resource usage information request and report for a media flow; +- dynamic firewall working mode selection for a media flow; +- technology-independent core network ingress/egress path information for a media flow. + +The following provides a brief description of the information exchange requirements for the Rw interface. + +- *Request-response "transactions":* + +The interface must allow the PD-PE or the PE-PE respectively to request an action to be performed by the PE-PE or the PD-PE respectively and get a response (that can be correlated with the request) in return. + +NOTE 1 – Some terms like "transaction", "message", "action", "command" and others are used in a generic manner in this Recommendation. These terms may have a protocol-specific meaning, and if they do, they will be defined in the relevant Q.3303.x-specific protocol Recommendation. + +- *Notifications:* + +The interface must allow for the notification of asynchronous events (from the PE-PE to the PD-PE). + +– *Reliable delivery:* + +The interface should provide reliable delivery of messages. + +– *Capabilities:* + +The PD-PE must be able to determine capabilities when requesting resources and other transport plane functions from the PE-PE. + +– *Security:* + +All messages between the PD-PE and the PE-PE should be authenticated such that requests to the PE-PE from unauthenticated sources will not be performed and such that notifications sent from the PE-PE to the PD-PE came from an authenticated PE-PE source. + +– *One-to-many/many-to-one:* + +Two modes shall be supported: + +- 1) One-to-many mode, a PD-PE shall be able to communicate with multiple PE-PEs. +- 2) Many-to-one mode, multiple PD-PEs shall be able to make requests to a given PE-PE. + +NOTE 2 – This mode is not supported when using COPS (ITU-T Rec. Q.3303.1). + +NOTE 3 – This mode requires the support of virtual MGs when using H.248 (ITU-T Rec. Q.3303.2). + +For either mode, only a single PD-PE shall make a request to a given PE-PE for a particular session. + +### 6.2 Rw reference model + +The Rw interface, as shown in Figure 1, is defined between the PD-PE and the PE-PE. + +![Figure 1 – Rw reference model diagram showing the interaction between Service, Transport, and Network strata. The Service stratum contains 'Service control functions'. The Transport stratum contains 'Network attachment control functions', 'TRC-FE', 'PD-PE', 'TRE-FE', and 'PE-PE'. The Network stratum contains 'RACF'. Interfaces are labeled Ru, Rd, Rs, Ri, Rp, Rt, Rn, Rc, and Rw. A dashed box on the left indicates the 'Scope of Q.3303.x-series Recommendations' covering the Transport and Network strata. A vertical bar on the right is labeled 'Other NGNs'.](ee8536b235eb6aad21e2048fd5308900_img.jpg) + +Figure 1 – Rw reference model diagram showing the interaction between Service, Transport, and Network strata. The Service stratum contains 'Service control functions'. The Transport stratum contains 'Network attachment control functions', 'TRC-FE', 'PD-PE', 'TRE-FE', and 'PE-PE'. The Network stratum contains 'RACF'. Interfaces are labeled Ru, Rd, Rs, Ri, Rp, Rt, Rn, Rc, and Rw. A dashed box on the left indicates the 'Scope of Q.3303.x-series Recommendations' covering the Transport and Network strata. A vertical bar on the right is labeled 'Other NGNs'. + +Q.3303.0(07)F\_01 + +NOTE – Figure derived from Figure 1 of [ITU-T Q.3300], which was taken from Figure 5 of [ITU-T Y.2111]. + +**Figure 1 – Rw reference model** + +## 6.3 Functional elements and capabilities + +#### 6.3.1 Policy decision physical entity (PD-PE) + +##### 6.3.1.1 Summary + +The PD-PE coordinates the resource requests from the SCE and/or the PE-PE, and makes policy decisions using a collection of information as described below. The PD-PE requests the resource availability information and resource admission control from the TRC-PE. Finally, the PD-PE shall request the policy enforcement operations to the PE-PE via the Rw interface. The functionality of the PD-PE is further detailed in clause 7.2.3 of [ITU-T Y.2111]. + +The PD-PE should be able to support both push mode and pull mode according to the configuration of network operator and/or the access network type in the process of resource reservation, gate control and policy enforcement. In the push mode, the PD-PE takes the initiative in pushing down policy decisions to the PE-PE upon receipt of a request from the SCE; in the pull mode, the PD-PE should re-authorize and retrieve policy decisions upon receipt of a request from the PE-PE. The push mode is typically used in transport networks that do not support or require transport signalling for establishing network resources dynamically on behalf of, or directly by, an individual service session of the UE, e.g., DSL broadband access and Ethernet. The pull mode is typically used in transport networks that support or require the use of transport signalling to establish the network resource dynamically on behalf of or directly by an individual service session of the UE, e.g., GPRS. + +In addition, the PD-PE may provision the static policy configuration onto the PE-PE upon the triggers of network policies, conditions and resource status. + +The dynamic policy decisions are produced by the PD-PE according to the following information: + +- Service information received from the SCE. It consists of: + - Media type. + - Application service class. + - Priority. + - QoS information (e.g., requested bandwidth). +- Transport subscription profile. It consists of: + - Maximum bandwidth per subscription (uplink/downlink). + - Subscribed network service class. + - Reservation priority. +- Service-based network policies, non-exhaustive examples such as: + - Mapping rules to network service class. + - Maximum sessions per network service class. + - Time of day. + - Source control mode (i.e., push or pull mode). +- Transport resource availability and admission decision information received from the TRC-PE. + +The *static* policy configuration may be triggered by certain conditions, e.g., + +- Network policies, e.g., time of day. +- Resource utilization. +- Network configuration. +- Transport subscription. + +##### 6.3.1.2 More details + +NOTE – The text in this clause is identical to that of clause 7.2.3.2 of [ITU-T Y.2111] with the following exceptions: + +- a) "functional entities" (FE) were replaced by "physical entities" (PE); +- b) "reference point" was replaced by "interface". + +The PD-PE handles the QoS resource requests received from the SCE via the Rs interface or from PE-PE via the Rw interface. The PD-PE contains the following functions: + +- *Final decision point (FDP)*: This function first checks the QoS resource request based on service information, network policy rules and transport subscription information, and then + +interacts with the TRC-PE via the Rt interface to detect and determine the requested QoS resource within the involved access and/or core transport networks. + +- The FDP makes the final admission decision for media flows of a given service based on network policy rules, service information, transport subscription information and decision on resource availability. + - The FDP indicates the loss of connectivity: It informs the SCE that the connectivity of the transport resource previously granted is lost. The SCE may request PD-PE to relinquish all resources associated with the session. +- *QoS mapping – Technology independent (QMTI)*: This function maps the service QoS parameters and priority received from the SCE via the Rs interface to network QoS parameters (e.g., Y.1541 class) and priority based on the network policy rules. + - *Gate control (GC)*: This function controls PE-PE to install and enforce the final admission decisions via the Rw interface (e.g., opening or closing the gate). The action to pass or drop IP packets is based on a set of IP gates (packet classifiers, e.g., IPv4 5-tuple) and transport interface identification information (e.g., VLAN/VPN ID) as needed. + - *IP packet marking control (IPMC)*: This function takes decisions on packet marking and remarking of flows. The marking may consider the priority of the flow and traffic engineering parameters. + - *NAPT control and NAT traversal (NAPTC)*: This function interacts with PE-PE and SCE to provide the address binding information for NAPT control and NAT traversal as needed. + - *Rate limiting control (RLC)*: This function makes decisions on the bandwidth limits of flows (e.g., for policing). + - *Firewall working mode selection (FWMS)*: This function selects the working mode of the firewall based on the service information. Four packet inspection modes could be identified (static packet filtering, dynamic packet filtering, stateful inspection, deep packet inspection, see also clause 7.2.4.1 of [ITU-T Y.2111]). + - *Core network path selection (CNPS)*: This function chooses the core network ingress and/or egress path for a media flow based on the service information and technology independent policy rules at the involved PD-PE. + - *Network selection (NS)*: This function locates core networks that are involved to offer the requested QoS resource. It locates the PE-PE instances that are involved to enforce the final admission decisions. + +The PD-PE shall make the final policy decisions based on the service information (e.g., service type, flow description, bandwidth and priority), transport network information (e.g., resource admission result and network policy rules) and transport subscription information (e.g., maximum upstream/downstream capacity). The policy decision shall provide sufficient information to make the PE-PE perform the resource control operation (e.g., gate opening/closing, bandwidth allocation/rate limiting, packet marking, traffic policing/shaping, NAPT and address latching). The policy decisions may be composed of flow identifier, IP addresses, bandwidth, gate status, time/volume limit, traffic descriptor, etc. + +The PD-PE can be stateful or stateless depending on the complexity of the specific network environment, application characteristics and deployment architecture. + +- The stateless PD-PE only maintains the transaction state information, e.g., state held for the duration of a request-response operation. In order to be stateless, the PD-PE shall generate the resource control session information for each resource control request from the SCF, which can be stored in the SCE, TRC-PE or PE-PE and used to retrieve the state information together with pertinent information flows. + +- The stateful PD-PE may maintain a variety of resource control session information within PD-PE, such as the session duration, the resource control session information (e.g., the association between SCE and PD-PE, PD-PE and TRC-PE, PD-PE and PE-PE), the resource reservation limit (e.g., time limit/volume limit), resource reservation status (i.e., authorized, reserved or committed) and physical/logical connection ID. + +#### 6.3.2 Policy enforcement physical entity (PE-PE) + +##### 6.3.2.1 Summary + +The PE-PE supports policy enforcement and flow-based charging. It provides the IP media flow handling and QoS control, packet filtering, marking and policing, rate limiting, flow detection and counting, NAPT and media relay, as well as online and offline charging interactions. + +The PE-PE should support both pull mode and push mode. In the pull mode, it shall interact with the transport signalling (e.g., PDP context in the GPRS case) to perform the resource reservation. + +The PE-PE should allow the IP media flow to pass through with appropriate treatment if and only if the corresponding gate is open. If the PE-PE receives an Authorization token and Flow Id(s) from a UE, the PE-PE shall report them to the PD-PE over the Rw interface. A default gate may be established for each UE during the initialization process to allow the default traffic (e.g., best effort) to pass through. + +The PE-PE is located at the network device (e.g., GGSN/PDSN in the GPRS/CDMA case, PDG in the WLAN case, DSLAM or BRAS in the xDSL case, CMTS in the cable network case and border gateway in general). + +##### 6.3.2.2 More details + +NOTE – The text in this clause is identical to clause 7.2.4.1 of [ITU-T Y.2111], with the following exceptions: + +- "functional entities" (FE) were replaced by "physical entities" (PE); +- "reference point" was replaced by "interface". + +The PE-PE enforces the network policy rules instructed by the PD-PE on a per-subscriber and per-IP flow basis. It should be able to perform the following functions based on flow information such as classifier (e.g., IPv4 5-tuple) and flow direction, as well as transport interface identification information (e.g., VLAN/VPN identifier and LSP label) as needed. The functions of the PE-PE include: + +- Opening and closing gate: enabling or disabling packet filtering for an IP media flow. +A gate is unidirectional, associated with a media flow in either the upstream or downstream direction. When a gate is open, all of the packets associated with the flow are allowed to pass through; when a gate is closed, all of the packets associated with the flow are blocked and dropped. +- Rate limiting and bandwidth allocation. +- Traffic classification and marking. +- Traffic policing and shaping. +- Mapping of IP-layer QoS information onto link layer QoS information based on predefined static policy rules (e.g., setting 802.1p priority values). +- Network address and port translation. +- Media relay (i.e., address latching) for NAT traversal. +- Collecting and reporting resource usage information (e.g., start-time, end-time, packets and octets of sent and received data). + +- Packet-filtering-based firewall: inspecting and dropping packets based on predefined static security policy rules and gates installed by PD-PE. + +There are four packet inspection modes for packet-filtering-based firewall: + +- Static packet filtering: +Inspecting packet header information and dropping packets based on static security policy rules. This is the default packet inspection mode applied for all flows. +- Dynamic packet filtering: +Inspecting packet header information and dropping packets based on static security policy rules and dynamic gate status. +- Stateful inspection: +Inspecting packet header information as well as TCP/UDP connection state information and dropping packets based on static security policy rules and dynamic gate status. +- Deep packet inspection: +Inspecting packet header information, TCP/UDP connection state information and the content of payload together, and dropping packets based on static security policy rules and dynamic gate status. + +## Bibliography + +- [b-ITU-T Q-Sup.51] ITU-T Q-series Recommendations – Supplement 51 (2004), +*Signalling requirements for IP-QoS.* + + + + + +## 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.3304.1-201206-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd5c61de81376410ef453e450f6481acee5e1f6d --- /dev/null +++ b/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4fcb86b27f53b022d3429ee998aa2d7c8731de070f3a71978a42e41228c9c41 +size 68582 diff --git a/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/ee8536b235eb6aad21e2048fd5308900_img.jpg b/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/ee8536b235eb6aad21e2048fd5308900_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3af3bdea4ddd59758eef8b572c0fb0026716b22 --- /dev/null +++ b/marked/Q/T-REC-Q.3304.1-201206-I_PDF-E/ee8536b235eb6aad21e2048fd5308900_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b1adac690f2f570cb5f7cba27bb9afd3c69a858e528fa17153eb6d85bdfade0 +size 42596 diff --git a/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95913af7d24ac7ff480884f8103efaaa72e221d0 --- /dev/null +++ b/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08898260c299c50501ef7ef52b859eedfa8fbba06415d295210605d97bfa402c +size 60877 diff --git a/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..647c80548c08886c4187332e3c71529c97e7a092 --- /dev/null +++ b/marked/Q/T-REC-Q.3308.1-201203-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.3308.1-201203-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f702139eaa6822b60e8a84a9a14ae7df2741dde --- /dev/null +++ b/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6228981df7f5bef2fa93906acd6c42c5ddc2b84063aadb9b0c32f377d6d8cbb9 +size 65634 diff --git a/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ced734d53c33214655d5b203a6a6b8f5d7d9895 --- /dev/null +++ b/marked/Q/T-REC-Q.3308.1-201203-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07766e1cf2e2e432e154b94dc526e5ea675822e5f00bdda707c137ec69c2bbc1 +size 49690 diff --git a/marked/Q/T-REC-Q.3311-201010-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ede3eecb8ae343d812488f5a2520458384681f39 --- /dev/null +++ b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:725e7b08cba94f3d7bcde4e6667a414cfd26c1cc6ee9cf9b3022c67b11412dba +size 36511 diff --git a/marked/Q/T-REC-Q.3311-201010-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efe6b34d3d82f112e3bd0b7b9335a2383bfc81af --- /dev/null +++ b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c57e04978f64cf9decba914fbb63f82ac523dd6451775e06690328ee6b517e1a +size 50756 diff --git a/marked/Q/T-REC-Q.3311-201010-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/Q/T-REC-Q.3311-201010-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c322c059299f03d52ffc28f9098340d3ecf262b6 --- /dev/null +++ b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:176b68489d603a5f23bd733398a634763ebda9622cb472686ec1938b7908790c +size 35441 diff --git a/marked/Q/T-REC-Q.3311-201010-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f748580749cc01772b5261167e755a5fe98edb89 --- /dev/null +++ b/marked/Q/T-REC-Q.3311-201010-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf0b906a4fbd27990bd991a8fd148516ff82f59af7950f57afe48e67d869f689 +size 34307 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..647c80548c08886c4187332e3c71529c97e7a092 --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-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.3314-201205-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..272591745f8d9680952d5662aface4a8c7a87ed8 --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c9ffdbc5258ed65347ec27a58b89bbdac21081524da84230aa412fc2b13d54d +size 51877 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd2f8dd95c77caed74212518b4c247c30a9337b --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:854ec45715c5c910bffdfa861dc8c291d73d9188cb485a78ee276d66d655ef85 +size 53432 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93f6967e83550a9878050fe82982649b4ca31662 --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:802b03c122aa218b2522db0e740c0821cf2ea37f2a88f83aea989daa251049ed +size 100591 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..993f32103fb54a19c41149e1f93d0810aac59e4e --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fd00822dfb3b0e8cccf855e92df294d60bd6455b4dc496a39797d08ccd92907 +size 41050 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dbf67fe3f9883a67952f35c856855afcbfc7ae9 --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e481b2b209df0b7aa5047a385fed175af1ab959767f644a4bc50664521a99fc +size 106205 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f655e6716befaa048a986c9212b6bf872e6289cd --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f074fd98b69dfe9a6e4eb0bebaa98d9378152dc75d2fd7dea28b6e9091630b5 +size 42705 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35bc8b2a10821efed261dbdb6e0b88bd875e5484 --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7d3c5a19068fe8f5ebbe04f436e8e4913d991d6b8772487b7d926ccc9f93189 +size 46057 diff --git a/marked/Q/T-REC-Q.3314-201205-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..71a76f88c39c2d68e0d36436612ed45838ef6e4a --- /dev/null +++ b/marked/Q/T-REC-Q.3314-201205-I_PDF-E/raw.md @@ -0,0 +1,953 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3314** + +(05/2012) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Resource control protocols + +--- + +**Requirements and protocol at the interface +between the mobile location management +physical entity used as a proxy and the central +instance of the mobile location management +physical entity (M9 interface)** + +Recommendation ITU-T Q.3314 + +# 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.3314 + +# Requirements and protocol at the interface between the mobile location management physical entity used as a proxy and the central instance of the mobile location management physical entity (M9 interface) + +## Summary + +Recommendation ITU-T Q.3314 provides the signalling requirements and protocol for the M9 interface between the mobile location management physical entity as proxy (MLM-PE(P)) and the MLM-PE as the central instance (MLM-PE(C)) specified in Recommendation ITU-T Y.2018. The M9 interface provides information from the MLM-PE(P) and the MLM-PE(C) to registration/update and query mobility location information in both host-based and network-based mobility cases. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.3314 | 2012-05-22 | 11 | + +## Keywords + +M9 interface, MMCF, mobility control. + +## 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 ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | M9 interface..... | 3 | +| 5.1 | Overview ..... | 3 | +| 5.2 | M9 reference model..... | 3 | +| 5.3 | Physical entities and capabilities ..... | 3 | +| 6 | Protocol specifications..... | 4 | +| 6.1 | Location binding registration/update request/response ..... | 5 | +| 6.2 | Mobility location query request/response ..... | 5 | +| 7 | Message specification..... | 7 | +| 7.1 | Use of Diameter base protocol ..... | 7 | +| 7.2 | Diameter base protocol message mapping on the M9 interface..... | 8 | +| 7.3 | Diameter base protocol message formats on the M9 interface..... | 10 | +| 8 | Security considerations ..... | 15 | +| | Appendix I – High-level information flow at M9 ..... | 16 | +| I.1 | Mobility location binding registration/update during network attachment.... | 16 | +| I.2 | Mobility location binding registration/update during handover..... | 17 | +| I.3 | Route optimization considerations for network-based handover ..... | 19 | +| | Bibliography..... | 22 | + + + +# Requirements and protocol at the interface between the mobile location management physical entity used as a proxy and the central instance of the mobile location management physical entity (M9 interface) + +# 1 Scope + +This Recommendation defines the protocol for the M9 interface between the mobile location management physical entity as proxy (MLM-PE(P)) and the MLM-PE as the central instance (MLM-PE(C)) specified in [ITU-T Y.2018]. The M9 reference point provides the information flows to register and update mobility location information in both host-based and network-based mobility cases specified in [ITU-T Y.2018]. In the network-based mobility case, the MLM-PE(P) sends the location registration and/or update request to the MLM-PE(C). In the host-based mobility case, the user equipment (UE) sends the location registration and/or update request to the MLM-PE(P), which will forward it to the MLM-PE(C). + +The M9 reference point also provides the information flows for retrieving the binding location information regarding UE's reachability. The MLM-PE(P) holds the binding information between mobile user ID (or persistent address) and temporary address (or lower tunnel end point address). The MLM-PE(C) holds the binding information between mobile user ID (or persistent address), and address of the MLM-PE(P). The MLM-PE(P) may identify the corresponding MLM-PE(C) by extracting the home domain from the mobile user ID. The MLM-PE(P) may initiate route optimization through this interface. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; 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.2018] Recommendation ITU-T Y.2018 (2009), *Mobility management and control framework and architecture within the NGN transport stratum*. +- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. +- [ETSI ES 283 034] ETSI ES 283 034 (2008), *e4 interface based on the Diameter protocol*. +- [ETSI ES 283 035] ETSI ES 283 035 (2008), *e2 interface based on the Diameter protocol*. +- [ETSI TS 129 229] ETSI TS 129 229 (2010), *Cx and Dx interfaces based on the Diameter protocol; Protocol details (3GPP TS 29.229 version 9.3.0 Release 9)*. +- [ETSI TS 129 272] ETSI TS 129 272 v9.2.0 (2010), *Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol (3GPP TS 29.272 version 9.2.0 Release 9)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +**3.1.1 authentication** [b-ITU-T Y.2014]: A property by which the correct identifier 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.2 Terms defined in this Recommendation + +**3.2.1 location information** (Based on the definition given in [b-ITU-T Q.1001]): Actual location of the mobile station (e.g., PLMN, MSC area, location area, as required). + +**3.2.2 location registration** (Based on the definition given in [b-ITU-T Q.1741.3]): The procedure to register its presence in a registration area when the user equipment enters a new registration area. + +**3.2.3 nomadism** (Based on the definition given in [b-ITU-T Q.1761]): Ability of the user to change his network access point after moving; when changing the network access point, the user's service session is completely stopped and then started again, i.e., there is no session continuity or hand-over possible. + +NOTE – It is assumed that the normal usage pattern is that users shutdown their service session before moving to another access point. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----------|----------------------------------------------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| AVP | Attribute-Value Pair | +| FQDN | Fully Qualified Domain Name | +| GPRS | General Packet Radio Service | +| GTP | GPRS Tunnelling Protocol | +| HDC-PE | Handover Decision and Control Physical Entity | +| ID | Identification | +| MLM-FE | Mobile Location Management Functional Entity | +| MLM-PE | Mobile Location Management Physical Entity | +| MMCF | Mobility Management Control Functions | +| MLM-PE(C) | An instance of the MLM-PE performing the Central mobile location management role | +| MLM-PE(P) | An instance of the MLM-PE performing the Proxy mobile location management role | +| MPLS | Multiprotocol Label Switching | +| NACF | Network Attachment Control Function | +| NAT | Network Address Translation | +| NID-PE | Network Information Distribution Physical Entity | +| NIR-PE | Network Information Repository Physical Entity | +| PD-PE | Policy Decision Physical Entity | + +| | | +|--------|-----------------------------------------------| +| PPP | Point-to-Point Protocol | +| RACF | Resource Admission and Control Function | +| SCTP | Stream Control Transport Protocol | +| TLM-PE | Transport Location Management Physical Entity | +| UE | User Equipment | +| VCI | Virtual Circuit Identifier | +| VPI | Virtual Path Identifier | + +# 5 M9 interface + +## 5.1 Overview + +This Recommendation specifies the protocol for the M9 reference point. + +The M9 reference point provides the information flows to register and update mobility location information via the M9 interface specified in [ITU-T Y.2018] in both the host-based and network-based mobility cases. The M9 reference point also provides the information flows for retrieving the binding location information regarding the UE's reachability. + +Therefore, two operations may occur at the M9 interface as follows: + +- mobility location binding registration and/or update +- mobility location query. + +## 5.2 M9 reference model + +Figure 5-1 describes the M9 reference architecture. This illustration can be used as the initial architecture. + +![Figure 5-1 – M9 reference model diagram showing the architecture of the M9 interface between MMCF(P) and MMCF(C).](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +The diagram illustrates the M9 reference model architecture. On the left, a 'UE' (User Equipment) is connected to an 'MMCF(P)' (Mobile Management Control Function - Provider) via the 'M3' interface. The 'UE' is also connected to a 'NACF' (Network Access Control Function) via the 'M1' interface. The 'NACF' contains a 'TLM-PE' (Transport Location Management Physical Entity). The 'NACF' is connected to an 'RACF' (Resource Admission and Control Function) via the 'M8' interface. The 'RACF' contains a 'PD-PE' (PD-PE). The 'MMCF(P)' contains a stack of physical entities: 'MLM-PE' (Mobile Location Management Physical Entity), 'HDC-PE' (HDC-PE), 'NID-PE' (NID-PE), and 'NIR-PE' (NIR-PE). These entities are connected via interfaces 'M10', 'M11', and 'M12'. The 'MLM-PE' in 'MMCF(P)' is connected to the 'MLM-PE' in 'MMCF(C)' via the 'M9' interface, which is highlighted in yellow. The 'MMCF(C)' (Mobile Management Control Function - Consumer) contains a similar stack of physical entities: 'MLM-PE', 'HDC-PE', 'NID-PE', and 'NIR-PE', connected via interfaces 'M10', 'M11', and 'M12'. + +Figure 5-1 – M9 reference model diagram showing the architecture of the M9 interface between MMCF(P) and MMCF(C). + +Figure 5-1 – M9 reference model + +## 5.3 Physical entities and capabilities + +### 5.3.1 Mobile location management physical entity (MLM-PE) + +The MLM-PE has the following responsibilities: + +- in the case of network-based mobility, initiating location registration on behalf of the UE; +- processing location registration messages sent from, or on behalf of the UE; +- optionally, maintaining the binding between the mobility service user ID and persistent IP address assigned to the UE; + +- management of the binding between the persistent IP address assigned to the UE and its temporary IP address, in the case of host-based mobility, or the address of the lower tunnel end point, in the case of network-based mobility; +- optionally, holding two location bindings for the mobile UE by marking the binding for the serving network as active state and marking the binding for target network as standby state; +- supporting separation of control and data plane by allowing the MLM-PE address and data forwarding end point address (i.e., tunnel end point address) to be different; +- indication of a new mobility location binding and distribution of binding information to the HDC-PE. + +The MLM-PE has two roles, as proxy (MLM-PE(P)) and as the central instance (MLM-PE(C)). The MLM-PE(P) and MLM-PE(C) roles may be co-located in specific deployments providing only host-based mobility. The MLM-PE(C) provides a central point of contact for correspondent nodes (e.g., the service control function (SCF)). The MLM-PE(P) and MLM-PE(C) together provide hierarchical location management. The MLM-PE(P) holds and updates the binding between mobile user ID, persistent address, and temporary/lower tunnel end point address. The MLM-PE(C) holds the binding between mobile user ID, persistent address, and address of the MLM-PE(P). The MLM-PE(P) may identify the corresponding MLM-PE(C) by extracting the home domain from the mobile user ID. + +The MLM-PE(P) consists of the following functions: + +- In the host-based case, it provides the first point of contact for location registration for mobile users. As such, it appears as a proxy for the MLM-PE(C) from the point of view of the UE, while appearing as a proxy for the UE from the point of view of the MLM-PE(C). The mobile UE obtains the address of the MLM-PE(P) in the attachment procedure. +- In the network-based mobility case, the MLM-PE(P) acts as a proxy for the UE from the point of view of the network side. +- The MLM-PE(P) supports IP-based paging to locate the mobile UE. +- In the host-based case, the MLM-PE(P) may interwork between different mobility signalling protocols (e.g., due to a difference in IP versions supported) at the UE and at the MLM-PE(C). +- Signalling for location registration in the host-based case is secured through the security association between the UE and the MLM-PE(P). The security association is dynamically created based on the keying materials generated in the attachment procedure. +- The MLM-PE(P) is responsible for requesting the HDC-PE to perform handover control as a consequence of mobile location registration or update. +- The MLM-PE(P) may be the proxy of the UE for initiating route optimization, especially in the case of interworking between signalling protocols. +- If there is a second anchor point between the UE and the anchor point to which the MLM-PE(C) corresponds, the MLM-PE(P) carries the additional address binding. +- The MLM-PE(P) may be used to transform addresses within the signalling because of intervening network address translations (NATs). +- The MLM-PE(P) may be used to provide address anonymity to the UE. + +# 6 Protocol specifications + +The M9 reference point enables the MLM-PE(P) to query and update binding location information from/to the MLM-PE(C). The primary parameter for retrieving the binding location information shall be the mobile user identification (ID), persistent address, and address of the MLM-PE(P). + +The following information primitives are used in this interface: + +- mobility location binding registration and/or update request and/or response; +- mobility location query request and/or response. + +## 6.1 Location binding registration/update request/response + +This information flow is used to register and update mobility location information in both the host-based and network-based mobility cases. In the network-based mobility case, the MLM-PE(P) will send the location registration/update request to the MLM-PE(C). In the host-based mobility case, the UE will send the location registration/update request to the MLM-PE(P), which will pass it on to the MLM-PE(C). + +The mobility service subscriber ID and information providing the location binding between the persistent location identifier and the location of the MLM-PE(P) are included in the messages for both host-based and network-based mobility. + +The reference point M9 supports the following two primitives for this operation: + +- mobility location binding registration/update request (see Table 6-1); +- mobility location binding registration/update response (see Table 6-2). + +**Table 6-1 – Mobility location binding registration/update request +(MLM-PE(P) → MLM-PE(C))** + +| Information element | Explanation | +|---------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Mobility service subscriber identifier (conditionally mandatory) (Note) | 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 | 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(P) | The address of the MLM-PE instance which sends the location registration. | +| NOTE – Mobility service subscriber identifier is required if persistent address is private. | | + +**Table 6-2 – Mobility location binding registration/update response +(MLM-PE(C) → MLM-PE(P))** + +| Information element | Explanation | +|----------------------------------------|------------------------------------------------------------------------------------| +| Mobility service subscriber identifier | The identifier of the subscriber for which the mobility service is to be provided. | +| Binding request result | Indication of the success or failure of the binding request. | + +## 6.2 Mobility location query request/response + +In the route optimization case (see clause 7.3.5 of [ITU-T Y.2018]), the MLM-PE(C) may query and obtain the mobile UE's current binding location information through this reference point in order to pass it to the MLM-PE(C) associated with a correspondent UE. + +If a related entity (e.g., a correspondent node) requests the MLM-PE(C) to provide an indication regarding UE reachability, the MLM-PE(C) may send a response to the MLM-PE(P) through this + +reference point to get that information. The MLM-PE(P) will send the location binding information to the related entity (e.g., correspondent node) via the MLM-PE(C). + +Reference point M9 supports two primitives for this purpose: + +- mobility location query request (see Table 6-3); +- mobility location query response (see Table 6-4). + +**Table 6-3 – Mobility location query request (MLM-PE(C) → MLM-PE(P))** + +| Information element | Explanation | +|----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| Mobility service subscriber identifier (Note) | The identifier of the subscriber for which the mobility service is to be provided. | +| Persistent IP address information (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. | +| Requested items | The item list to the requested information. | +| Address of MLM-PE(P) | The address of the MLM-PE instance which sends the location query. | +| NOTE – Either the mobility service subscriber identifier or the persistent IP address information is required. | | + +**Table 6-4 – Mobility location query response (MLM-PE(P) → MLM-PE(C))** + +| Information element | Explanation | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Mobility service subscriber identifier | The identifier of the subscriber for which the mobility service is to be provided. | +| Persistent IP address information | 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. | +| Temporary IP address information | A set of IP address information used for locating the access network to which the UE is attached. | +| – Unique IP address | The temporary IP address allocated to the attached mobile UE. | +| – Address realm | The addressing domain in which the IP address is significant. | +| Address of MLM-PE(P) | The address of the MLM-PE instance which the mobile UE is attached. | +| RACS contact point (optional) | The fully qualified domain name (FQDN) or IP address of the RACS where resource request shall be sent (i.e., PD-PE address). | +| Terminal type (optional) | The type of the mobile UE. | +| Type of access transport (optional) | The type of access network to which the mobile UE is attached. | +| IP connectivity status (optional) | Whether IP connectivity to/from the user equipment is currently available. | + +**Table 6-4 – Mobility location query response (MLM-PE(P) → MLM-PE(C))** + +| Information element | Explanation | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Physical connection identifier (optional) | A local identifier for physical connection of access transport network that the mobile UE is attached to (e.g., IP address of PE-PE device, and MAC address or link ID and physical port). | +| Logical connection identifier (optional) | A local identifier for logical connection of access transport network to which the mobile UE is connected (e.g., ATM VPI/VCI, PPP, MPLS label, GTP tunnel and logical port). It can be used to locate the layer 2 connection and pertinent network devices for a particular UE requesting the access transport resource. | + +# 7 Message specification + +## 7.1 Use of Diameter base protocol + +Along with the clarifications listed in the following clauses (i.e., 7.1.1-7.1.6), the Diameter base protocol defined in [b-IETF RFC 3588] shall apply. + +### 7.1.1 Securing Diameter messages + +For secure transport of Diameter messages, IPSec may be used. Guidelines on the use of stream control transport protocol (SCTP) with IPSec can be found in [b-IETF RFC 3554]. + +### 7.1.2 Accounting functionality + +Accounting functionality (accounting session state machine, related command codes and AVPs) is not used at the M9 interface. + +### 7.1.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 [b-IETF RFC 3588]. + +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 or responses, the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in [b-IETF RFC 3588]. As a consequence, the server does not maintain any state information about this session and the client does not need to send a session termination request. Neither the Authorization-Lifetime AVP, nor the Session-Timeout AVP shall be present in requests or responses. + +### 7.1.4 Transport protocol + +Diameter messages over the M9 interface shall make use of SCTP as defined in [b-IETF RFC 2960] and shall utilize the new SCTP checksum method specified in [b-IETF RFC 3554]. + +### 7.1.5 Routing considerations + +This clause specifies the use of the Diameter routing AVPs, Destination-Realm and Destination-Host. + +With reference to the Diameter protocol used at the M9 interface, the MLM-PE(P) acts as the Diameter client and the MLM-PE(C) acts as a Diameter server. + +Requests initiated by the MLM-PE(P) towards a MLM-PE(C) shall include both Destination-Host and Destination-Realm AVPs. The MLM-PE(P) obtains the Destination-Host AVP to use in requests towards a MLM-PE(C) from configuration data and/or the subscriber profile. Consequently, the Destination-Host AVP is declared as mandatory for all requests initiated by the MLM-PE. A Destination-Realm AVP is declared as mandatory for all requests initiated by the MLM-PE. + +### 7.1.6 Advertising application support + +The Capabilities-Exchange-Request (CER) and the Capabilities-Exchange-Answer (CEA) commands are specified in [b-IETF RFC 3588]. The Diameter-base application identifier (0) shall be used in the Diameter message header of these messages. + +If both MLM-PE(P) and MLM-PE(C) indicate support of the M9 application, then the M9 application identifier (16777306) shall be used in the Diameter message header of all subsequent messages exchanged within this association. + +Support of the M9 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 M9 (16777306). + +The vendor identifier value of ITU-T (11502) shall be included in the Vendor-Id AVP of the CER and CEA commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the CER and CEA commands. Additionally, the MLM-PE(C) and the MLM-PE(P) are required to advertise the support of AVPs specified in the Diameter related documents of 3GPP, ETSI and ITU-T, 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 7-1. + +**Table 7-1 – Vendor identifiers for M9** + +| Vendor | Vendor identifier | +|--------|-------------------| +| 3GPP | 10415 | +| ETSI | 13019 | +| ITU-T | 11502 | + +NOTE – The Vendor-Id AVP included in CER and CEA 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 [b-IETF RFC 3588]. + +## 7.2 Diameter base protocol message mapping on the M9 interface + +This Recommendation uses the four Diameter commands identified in Table 7-2 which are defined in [ETSI TS 129 229] and [ETSI TS 129 272]. Other commands are ignored by the MLM-PE(P) and the MLM-PE(C). + +**Table 7-2 – Command code** + +| Command | Abbreviation | Defining reference | Command code | See clause | +|------------------------------|--------------|--------------------|--------------|------------| +| Update-Location-Request | ULR | [ETSI TS 129 272] | 316 | 7.2.1 | +| Update-Location-Answer | ULA | [ETSI TS 129 272] | 316 | 7.2.2 | +| Location-Information-Request | LIR | [ETSI TS 129 229] | 302 | 7.2.3 | +| Location-Information-Answer | LIA | [ETSI TS 129 229] | 302 | 7.2.4 | + +Clauses 7.2.1 and 7.2.2 describe the mapping between information elements defined in the M9 interface and Diameter AVPs. + +Tables 7-3, 7-4, 7-5 and 7-6 describe this mapping, and each information element is marked as (M) mandatory, (C) conditional or (O) optional. See [ETSI ES 129 272]. + +### 7.2.1 Mobility location binding registration/update + +Mobility location binding registration/update request/response is mapped to the commands Update-Location-Request Answer in the Diameter application specified in S6a interface. See [ETSI TS 129 272]. Tables 7-3 and 7-4 detail the information elements involved and their mappings to Diameter AVPs. + +**Table 7-3 – Mapping of mobility location binding registration/update request to Diameter AVP** + +| Information element name | | Diameter AVP | Category | +|----------------------------------------|-------------------|-------------------------|----------| +| Mobility service subscriber identifier | | User-Name | C | +| Persistent IP address information | Unique IP Address | Globally-Unique-Address | C | +| | Address Realm | | | +| Address of MLM-PE(P) | | MLM-PE-Contact-Point | M | + +**Table 7-4 – Mapping of mobility location binding registration/update response to Diameter AVP** + +| Information element name | Diameter AVP | Category | +|----------------------------------------|---------------------|----------| +| Mobility service subscriber identifier | User-Name | C | +| Binding request result | Experimental_Result | M | + +### 7.2.2 Mobility location query + +Mobility location query request/response is mapped to the commands Location Information Request/Answer in the Diameter application specified in Cx interface defined in [ETSI TS 129 229]. Tables 7-5 and 7-6 detail the information elements involved and their mappings to Diameter AVPs. + +**Table 7-5 – Mapping of mobility location query request to Diameter AVP** + +| Information element name | | Diameter AVP | Category | +|----------------------------------------|-------------------|-------------------------|----------| +| Mobility service subscriber identifier | | User-Name | C | +| Persistent IP address information | Unique IP Address | Globally-Unique-Address | C | +| | Address Realm | | | +| Requested items | | Requested-Information | O | +| Address of MLM-PE(P) | | MLM-PE-Contact-Point | M | + +**Table 7-6 – Mapping of mobility location query response to Diameter AVP** + +| Information element name | | Diameter AVP | Category | +|----------------------------------------|-------------------|---------------------------------|----------| +| Result | | Result-Code/Experimental-Result | M | +| Mobility service subscriber identifier | | User-Name | O | +| Persistent IP address information | Unique IP Address | Globally-Unique-Address | C | +| | Address Realm | | | +| Temporary IP address information | Unique IP Address | Globally-Unique-Address | C | +| | Address Realm | | | +| Address of MLM-PE(P) | | MLM-PE-Contact-Point | O | +| RACS contact point | | RACS-Contact-Point | O | +| Access transport network type | | Access-Network-Type | O | +| Terminal type | | Terminal-Type | O | +| IP connectivity status | | IP-connectivity-status | O | +| Physical connection identifier | | Physical-Connection-Identifier | O | +| Logical connection identifier | | Logical-Connection-Identifier | O | + +## 7.3 Diameter base protocol message formats on the M9 interface + +### 7.3.1 Commands + +#### 7.3.1.1 Mobility location binding registration/update request + +The mobility location binding registration/update request, indicated by the Command-Code field set to 316 and the "R" bit set in the Command Flags field, is sent by the MLM-PE(C) to the MLM-PE(P) in order to notify changes in the user location data in the MLM-PE(C). This command is defined in [ETSI TS 129 272] and used with additional AVPs defined in this Recommendation. + +*Message format:* + +``` +< Update-Location-Request > ::= < Diameter Header: 316, REQ, PXY, 16777306> +< Session-Id > +{ Vendor-Specific-Application-Id } +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +[ User-Name ] +[ Globally-Unique-Address ] +{ MLM-PE-Contact-Point } +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +#### 7.3.1.2 Mobility location binding registration/update response + +The mobility location binding registration/update response, indicated by the Command-Code field set to 316 and the "R" bit cleared in the Command Flags field, is sent by a client in response to the Update-Location-Request (ULR) command. The Experimental-Result AVP may contain one of the values defined in clause 7.3.2. + +*Message format:* + +``` +< Update-Location-Answer > ::= < Diameter Header: 316, PXY, 16777306> + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Experimental_Result ] + *[ AVP ] + *[ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +#### 7.3.1.3 Mobility location query request + +The mobility location query request, indicated by the Command-Code field set to 302 and the "R" bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request user data. This command is defined in [ETSI TS 129 229] and used with the additional AVPs defined in this Recommendation. + +*Message format:* + +``` +< Location-Information-Request > ::= < Diameter Header: 302, REQ, PXY, 16777306> + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [ User-Name ] + [ Globally-Unique-Address ] + [ Requested-Information ] + { MLM-PE-Contact-Point } + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +#### 7.3.1.4 Mobility location query response + +The mobility location query response, indicated by the Command-Code field set to 302 and the "R" bit cleared in the Command Flags field, is sent by a server in response to the Location-Information-Request command. This command is defined in [ETSI TS 129 229] and used with the additional AVPs defined in this Recommendation. The Experimental-Result AVP may contain one of the values defined in clause 7.3.2. + +*Message format:* + +``` +< Location-Information-Answer > ::= < Diameter Header: 302, PXY, 16777306> + < Session-Id > + { Vendor-Specific-Application-Id } +``` + +``` + +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ User-Name ] +[ Globally-Unique-Address ] +[ Globally-Unique-Address ] +[ MLM-PE-Contact-Point ] +[ RACS-Contact-Point ] +[ Access-Network-Type ] +[ Terminal-Type ] +[ IP-Connectivity-status ] +[ Physical-Connection-Identifier ] +[ Logical-Connection-Identifier ] +*[ AVP ] +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 7.3.2 Experimental-Result-Code AVP values + +This clause defines specific values of the Experimental-Result-Code AVP used in this Recommendation. The Experimental-Result-Code AVP shall be used to indicate success/errors as defined in the Diameter base protocol. Most of the specific values are imported from 3GPP and ETSI specifications, as indicated in [ETSI TS 129 272]. + +### 7.3.3 Attribute value pairs (AVPs) + +Tables 7-7, 7-8 and 7-9 summarize the AVPs used in this Recommendation. These are in addition to the AVPs defined in [b-IETF RFC 3588]. + +Table 7-7 describes the Diameter AVPs that are used within this Recommendation that have been defined by ETSI [ETSI ES 283 035]. This table provides 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 this table shall be set to ETSI (13019). These AVPs are described in this Recommendation for information only; however, the normative detail for these AVPs is contained in [ETSI ES 283 035]. + +**Table 7-7 – Diameter AVPs imported from [ETSI ES 283 035]** + +| Attribute name | AVP code | Clause defined | Value type (Note 2) | AVP flag rules (Note 1) | | | | May encrypt | +|-----------------------|----------|----------------|---------------------|-------------------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | | +| RACS-Contact-Point | 351 | 7.3.3.5 | DiameterIdentity | V | M | | | Y | +| Terminal-Type | 352 | 7.3.3.6 | OctetString | V | M | | | Y | +| Requested-Information | 353 | 7.3.3.2 | Enumerated | V | | | M | Y | + +NOTE 1 – The AVP header bit denoted as 'M' indicates whether support of the AVP is required. The AVP header bit denoted as 'V' indicates whether the optional Vendor-Id field is present in the AVP header. For further details, see [b-IETF RFC 3588]. + +NOTE 2 – The value types are defined in [b-IETF RFC 3588]. + +Table 7-8 describes the Diameter AVPs defined by the e4 interface protocol [ETSI ES 283 034] and used within this Recommendation. These AVPs are described in this Recommendation for information only; however, the normative details for these AVPs are contained in [ETSI ES 283 034]. The Vendor-Id header of all AVPs defined in Table 7-8 shall be set to ETSI (13019). + +**Table 7-8 – 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 | 7.3.3.1 | Grouped | M,V | | | | Y | +| Logical-Connection-Identifier | 302 | 7.3.3.9 | OctetString | V | M | | | Y | +| Access-Network-Type | 306 | 7.3.3.3 | Grouped | V | M | | | Y | +| IP-Connectivity-Status | 305 | 7.3.3.7 | Enumerated | V | M | | | Y | +| Physical-Connection-Identifier | 313 | 7.3.3.8 | UTF8String | V | M | | | Y | + +Table 7-9 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 7-9 – Diameter AVPs defined in this Recommendation** + +| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt | +|----------------------|----------|----------------|------------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | | +| MLM-PE-Contact-Point | 1040 | 7.3.3.4 | DiameterIdentity | M,V | | | | Y | + +#### 7.3.3.1 Globally-Unique-Address AVP + +The Globally-Unique-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] +``` + +#### 7.3.3.2 Requested-Information AVP + +The Requested-Information AVP (AVP code 353 13019) is of type Enumerated. The following values are defined: + +- SUBSCRIBER-ID (0) +- LOCATION-INFORMATION (1) +- RACS-CONTACT-POINT (2) +- ACCESS-NETWORK-TYPE (3) +- Terminal-TYPE (4) +- LOGICAL-CONNECTION-IDENTIFIER (5) +- PHYSICAL-CONNECTION-IDENTIFIER (6) +- ACCESS-NETWORK-TYPE (7) +- DEFAULT-CONFIGURATION (8) +- TRANSPORT-RESOURCE-SUBSCRIPTION (9) + +- IP-CONNECTIVITY-STATUS (10). + +#### 7.3.3.3 Access-Network-Type AVP + +The Access-Network-Type AVP (AVP code 306 13019) is of type Grouped; it indicates the type of port on which the user equipment is connected and the type of aggregation network. + +*AVP format:* + +``` +Access-Network-Type ::= < AVP Header: 306 13019 > + {NAS-Port-Type} + [Aggregation-Network-Type] +``` + +#### 7.3.3.4 MLM-PE-Contact-Point AVP + +The MLM-PE-Contact-Point AVP (ITU-T AVP code 1040 11502) is of type DiameterIdentity and identifies the Local MLM-PE to which the mobile UE is attached. + +##### 7.3.3.5 RACS-Contact-Point AVP + +The RACS-Contact-Point AVP (AVP code 351 13019) is of type DiameterIdentity and identifies the Resource and Admission Control Subsystem (RACS) element to which the resource reservation requests shall be sent. + +##### 7.3.3.6 Terminal-Type AVP + +The Terminal-Type AVP (AVP code 352 13019) is of type OctetString and contains a value of the User Class DHCP Option (77). + +#### 7.3.3.7 IP-Connectivity-Status AVP + +The IP-Connectivity-Status AVP (AVP code 305 13019) is of type Enumerated. + +The following values are defined: + +- IP-CONNECTIVITY-ON (0) +- IP-CONNECTIVITY-LOST (1). + +#### 7.3.3.8 Physical-Connection-Identifier AVP + +The Physical-Connection-Identifier AVP (AVP code 313 13019) is of type UTF8String and identifies the physical access to which the user equipment is connected. It includes a port identifier and the identity of the access node where the port resides. + +#### 7.3.3.9 Logical-Connection-Identifier AVP + +The Logical-Connection-Identifier AVP (AVP code 302 13019) is of type OctetString. This AVP contains either a Circuit-ID (as defined in [b-IETF RFC 3046]) or a technology independent identifier. + +NOTE – In the xDSL/ATM case, the logical access ID may explicitly contain the identity of the VP (Virtual Path) and the VC (Virtual Circuit) carrying the traffic. + +#### 7.3.3.10 User-Name AVP + +The User-Name AVP is of type UTF8String according to [b-IETF RFC 3588]. This AVP shall contain the international Mobility Service Subscribe Identity, such as Mobile Equipment Identity specified in 3GPP. See [ETSI TS 129 272]. + +### **7.3.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). 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. + +#### **7.3.4.1 AVP codes** + +See clause 7.3.3. + +#### **7.3.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 7.3.2. + +#### **7.3.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. + +#### **7.3.4.4 Application-ID value** + +This Recommendation defines the M9 Diameter application with Application-ID 16777306. The vendor identifier assigned by IANA to ITU-T () is 11502. + +# **8 Security considerations** + +The security requirements within the requirements and protocol at the M9 interface are addressed by the security requirements for NGN as specified in [ITU-T Y.2701]. The M9 interface shall follow the security requirements specified in [ITU-T Y.2018]. + +# Appendix I + +## High-level information flow at M9 + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Mobility location binding registration/update during network attachment + +This clause describes the information flows required to achieve mobility location binding registration/update for a mobile UE. At each stage, the procedures vary depending on UE capabilities and network arrangements. Therefore, the scenarios in this Recommendation can be referred to as examples only. + +The procedures for network attachment of a mobile UE differ from those for a fixed or merely nomadic terminal because: + +- the part of the user profile that specifies the mobility service to be granted to the UE must be made available to the access network; and +- the functions related to mobility service must be engaged. + +The first task in this procedure is to obtain the user identifier for the purpose of authorizing mobility service, which will be an authentication, authorization and accounting (AAA) entity in the mobile subscriber's home network. This will, in general, lead to an authentication exchange between the UE and the AAA entity, relayed by the transport authentication and authorization physical entity (TAA-PE). After the new IP addresses are configured, the mobile UE is ready for mobility location update and new data path creation for the target network. If successful, the user traffic towards mobile UE may be forwarded to the serving network and the target network simultaneously. + +As noted in clause 6.4.1 in [ITU-T Y.2018], the MLM-PE(P) is the first point of contact for mobility location management signalling. The MLM-PE may hold two location bindings for the mobile UE; the binding for the serving network is marked as active while the binding for target network is marked as in standby state. To support separation of control and data plane, the MLM-PE address and the data forwarding end point address (i.e., tunnelling end point address) may be different. + +### I.1.1 Procedures for attachment in the case of host-based mobility + +Figure I.1 shows the message flow, which is divided into four phases: the mobility location registration request phase from the UE (see 1.1 in Figure I.1), the mobility location registration request phase to MLM-PE(C) (see 1.2 in Figure I.1), the mobility location registration response phase to the MLM-PE(P) (see 1.3 in Figure I.1) and the mobility binding registration response phase to the UE (see 1.4 in Figure I.1). If a hierarchical mobility mechanism is adopted and the UE moves within the scope of a single MLM-PE(P), the MLM-PE(P) will update its own mobility location bindings but does not need to notify the MLM-PE(C). + +![Sequence diagram for host-based mobility location binding registration. Lifelines: UE, HDC-PE, MLM-PE (P), TLM-PE, MLM-PE (C). The process starts with 'Authentication and IP configuration' between UE and MLM-PE (P). Then, 1.1 Mobility binding registration request from UE to MLM-PE (P). MLM-PE (P) sends 1.2 Mobility location binding registration request to MLM-PE (C). MLM-PE (C) returns 1.3 Mobility location binding registration response to MLM-PE (P). Finally, 1.4 Mobility binding registration response from MLM-PE (P) to UE. A yellow highlight covers steps 1.2 and 1.3. Reference Q.3314(12)_FI.1 is at the bottom right.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Sequence diagram for host-based mobility location binding registration. Lifelines: UE, HDC-PE, MLM-PE (P), TLM-PE, MLM-PE (C). The process starts with 'Authentication and IP configuration' between UE and MLM-PE (P). Then, 1.1 Mobility binding registration request from UE to MLM-PE (P). MLM-PE (P) sends 1.2 Mobility location binding registration request to MLM-PE (C). MLM-PE (C) returns 1.3 Mobility location binding registration response to MLM-PE (P). Finally, 1.4 Mobility binding registration response from MLM-PE (P) to UE. A yellow highlight covers steps 1.2 and 1.3. Reference Q.3314(12)\_FI.1 is at the bottom right. + +**Figure I.1 – Information flows for location binding registration in the case of host-based mobility** + +### I.1.2 Procedures for attachment in the case of network-based mobility + +Figure I.2 shows the information flows in the case of network-based mobility. The same phases apply as in the host-based case. However, because there is no potential race between a binding update from the UE and the configuration of the MLM-PE(P), the mobility location management is triggered by TLM-PE. The MLM-PE(P) initiates the mobility location management procedure at the MLM-PE(C). The mobility management functions are shown in Figure I.2. In this figure, the MLM-PE(P) pushes the mobility binding registration request to the MLM-PE(C) (see 2.2 in Figure I.2) and MLM-PE(C) replies the mobility binding registration response to the MLM-PE(P) (see 2.3 in Figure I.2). + +![Sequence diagram for network-based mobility location binding registration. Lifelines: UE, HDC-PE, MLM-PE (P), TLM-PE, MLM-PE (C). The process starts with 'Authentication and IP configuration' between TLM-PE and MLM-PE (C). Then, 2.1 Indication of network based mobility from TLM-PE to MLM-PE (P). MLM-PE (P) sends 2.2 Mobility location binding registration request to MLM-PE (C). MLM-PE (C) returns 2.3 Mobility location binding registration response to MLM-PE (P). A yellow highlight covers steps 2.2 and 2.3. Reference Q.3314(12)_FI.2 is at the bottom right.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Sequence diagram for network-based mobility location binding registration. Lifelines: UE, HDC-PE, MLM-PE (P), TLM-PE, MLM-PE (C). The process starts with 'Authentication and IP configuration' between TLM-PE and MLM-PE (C). Then, 2.1 Indication of network based mobility from TLM-PE to MLM-PE (P). MLM-PE (P) sends 2.2 Mobility location binding registration request to MLM-PE (C). MLM-PE (C) returns 2.3 Mobility location binding registration response to MLM-PE (P). A yellow highlight covers steps 2.2 and 2.3. Reference Q.3314(12)\_FI.2 is at the bottom right. + +**Figure I.2 – Information flows for location binding registration in the case of network-based mobility** + +## I.2 Mobility location binding registration/update during handover + +This clause describes the information flows required to achieve handover for a mobile UE. In each stage, the procedures vary depending on UE capabilities and network arrangements. Therefore, the scenarios in this Recommendation are provided as examples only. + +Before the UE can achieve handover to a new access point or network, the network discovery and decision procedure must be performed. Network discovery is performed by the UE when it detects alternative access points to which it may move. The handover decision is the process of choosing an access point to which to move. Network discovery and the handover decision must consider the following three cases: + +- the network makes the handover decision with input from the UE; +- the UE makes the handover decision with the assistance of information from the network; +- the UE makes the handover decision without assistance from the network. + +In the latter two cases the UE can request user input or can be constrained by user intervention. + +### I.2.1 Procedures for location binding update in the case of host-based mobility + +When the UE is acting together with the network, the UE makes the handover decision process. The UE may report a list of alternative access points to the HDC-PE. The UE may indicate its preference at this time regarding which entity makes the handover decision and which entity actually triggers the handover. Based on this information, the HDC-PE requests the RACF to check network resource availability on the potential path through each candidate network, and receives the resource check result from RACF. The HDC-PE then responds to the UE with a candidate access point list that is based on the UE's input, but reflects the results of the resource check and perhaps of local policy. + +The UE makes its selection about the target networks, and then informs the HDC-PE (see 3.1 in Figure I.3). The HDC-PE prepares the new access point, as described in the next two clauses, and responds to the UE (see 3.2 in Figure I.3). + +The UE sends the mobility location binding update request to the MLM-PE(P) (see 3.3 in Figure I.3). The mobility location binding update request is then relayed to the MLM-PE(C) (see 3.4 in Figure I.3) and the MLM-PE(C) replies the mobility binding registration response to the UE via the MLM-PE(P) (see 3.5 and 3.6 in Figure I.3). + +After the mobility location binding update is finished, the UE is ready for new data path creation for the target network. If successful, the user traffic towards mobile UE may be forwarded to the serving network and the target network simultaneously. + +![Sequence diagram showing information flows for location binding update during handover in the case of host-based mobility. The diagram involves five entities: UE, HDC-PE, MLM-PE(P), TLM-PE, and MLM-PE(C). The sequence starts with the UE selecting a new link. The UE sends a '3.1 UE handover decision request' to the HDC-PE. The HDC-PE responds with '3.2 UE handover decision response'. The UE then sends a '3.3 Location update request for handover' to the MLM-PE(P). The MLM-PE(P) relays this as '3.4 Mobility location binding update request' to the MLM-PE(C). The MLM-PE(C) responds with '3.5 Mobility location binding update response' back to the MLM-PE(P). Finally, the MLM-PE(P) sends a '3.6 Location update response for handover' back to the UE. The interaction between MLM-PE(P) and MLM-PE(C) is highlighted with a yellow background.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HDC-PE + participant MLM-PE(P) + participant TLM-PE + participant MLM-PE(C) + + Note left of UE: Select new link + UE->>HDC-PE: 3.1 UE handover decision request + HDC-PE-->>UE: 3.2 UE handover decision response + UE->>MLM-PE(P): 3.3 Location update request for handover + Note right of MLM-PE(P): Interaction with MLM-PE(C) + MLM-PE(P)->>MLM-PE(C): 3.4 Mobility location binding update request + MLM-PE(C)-->>MLM-PE(P): 3.5 Mobility location binding update response + MLM-PE(P)-->>UE: 3.6 Location update response for handover + +``` + +Q.3314(12)\_FI.3 + +Sequence diagram showing information flows for location binding update during handover in the case of host-based mobility. The diagram involves five entities: UE, HDC-PE, MLM-PE(P), TLM-PE, and MLM-PE(C). The sequence starts with the UE selecting a new link. The UE sends a '3.1 UE handover decision request' to the HDC-PE. The HDC-PE responds with '3.2 UE handover decision response'. The UE then sends a '3.3 Location update request for handover' to the MLM-PE(P). The MLM-PE(P) relays this as '3.4 Mobility location binding update request' to the MLM-PE(C). The MLM-PE(C) responds with '3.5 Mobility location binding update response' back to the MLM-PE(P). Finally, the MLM-PE(P) sends a '3.6 Location update response for handover' back to the UE. The interaction between MLM-PE(P) and MLM-PE(C) is highlighted with a yellow background. + +**Figure I.3 – Information flows for location binding update during handover in the case of host-based mobility** + +### I.2.2 Procedures for location binding update in the case of network-based mobility + +The HDC-PE prepares the new access point during handover. The HDC-PE retrieves static network information about the target networks from the NID-PE and checks network resource availability on the potential path through each candidate network and receives the resource check result from RACF. Based on this information, the HDC-PE sends the network handover decision request to the UE indicating its choice of deciding entity and triggering entity. The UE reports a list of alternative + +access points to the HDC-PE. The UE may indicate its preference at this time regarding which entity makes the handover decision and which entity actually triggers the handover. + +The HDC-PE sends the mobility location binding update request to the MLM-PE(P) (see 4.3 in Figure I.4). The mobility location binding update request is then relayed to the MLM-PE(C) (see 4.4 in Figure I.4) and the MLM-PE(C) replies the mobility binding registration response to the HDC-PE via the MLM-PE(P) (see 4.5 and 4.6 in Figure I.4). + +After the mobility location binding update is finished, the HDC-PE is ready for mobility location update and new data path creation for the target network. The actual triggering of handover execution is done by the HDC-PE. + +![Sequence diagram showing information flows for location binding update during handover. The diagram involves five entities: UE, HDC-PE, MLM-PE(P), TLM-PE, and MLM-PE(C). The process starts with the UE sending a '4.1 Network handover decision request' to the HDC-PE. The HDC-PE responds with '4.2 Network handover decision response'. The UE then sends a '4.3 Location update request for handover' to the HDC-PE. The HDC-PE sends a '4.4 Mobility location binding update request' to the MLM-PE(P), which is then relayed to the MLM-PE(C). The MLM-PE(C) responds with '4.5 Mobility location binding update response' to the MLM-PE(P), which is then relayed to the HDC-PE. Finally, the HDC-PE sends a '4.6 Location update response for handover' to the UE. A 'Select new link' box is shown above the MLM-PE(P) and TLM-PE entities. The diagram is labeled Q.3314(12)_FI.4 at the bottom right.](26d664119ad25250780f554633444e54_img.jpg) + +Sequence diagram showing information flows for location binding update during handover. The diagram involves five entities: UE, HDC-PE, MLM-PE(P), TLM-PE, and MLM-PE(C). The process starts with the UE sending a '4.1 Network handover decision request' to the HDC-PE. The HDC-PE responds with '4.2 Network handover decision response'. The UE then sends a '4.3 Location update request for handover' to the HDC-PE. The HDC-PE sends a '4.4 Mobility location binding update request' to the MLM-PE(P), which is then relayed to the MLM-PE(C). The MLM-PE(C) responds with '4.5 Mobility location binding update response' to the MLM-PE(P), which is then relayed to the HDC-PE. Finally, the HDC-PE sends a '4.6 Location update response for handover' to the UE. A 'Select new link' box is shown above the MLM-PE(P) and TLM-PE entities. The diagram is labeled Q.3314(12)\_FI.4 at the bottom right. + +**Figure I.4 – Information flows for location binding update during handover in the case of network-based mobility** + +### I.3 Route optimization considerations for network-based handover + +When a correspondent UE communicates with the mobile UE, normally packets from the correspondent UE will be intercepted by the transport function associated with the MLM-PE(C) (i.e., the L3HEF at the anchor point), then encapsulated and tunnelled to the current location of UE. For data path optimization, the MLM-PE(P) to which a correspondent UE is associated, may – based on administrative policies, cooperate with the MLM-PE(P) to which the mobile UE is associated to establish a direct tunnel between their respective networks. At this point the L3HEF at each end will encapsulate packets based on the location binding information exchanged between the two MLM-PE(P)s and will forward them directly to its peer L3HEF via the tunnel between them. The peer L3HEF delivers the de-capsulated packets to the correspondent or mobile UE respectively. + +The L3HEF is required to be aware of active communication between the mobile UE and correspondent UE. The process is triggered when it detects a flow that matches policy indicating that route optimization may be attempted. It then indicates route optimization to its associated MLM-PE(P)(A) via the HDC-PE (see 5.1 in Figure I.5). The MLM-PE(P)(A) sends a location binding query request message to the MLM-PE(C) which contains a route optimization (RO) indication (see 5.2 in Figure I.5). + +Upon receiving a location binding query request message including an RO request from MLM-PE(P)(A), MLM-PE(C) will perform route optimization operation and forward the location binding query request message to MLM-PE(P)(B) associated with the correspondent UE (see 5.3 in Figure I.5). MLM-PE(P)(B) replies with the location binding query response message including an RO response to MLM-PE(P)(A) via MLM-PE(C) (see 5.4 and 5.5 in Figure I.5). Upon receiving the RO response, MLM-PE(P)(A) sends the mobility location binding update request to + +MLM-PE(P)(B) via MLM-PE(C) (see 5.6 and 5.7 in Figure I.5). MLM-PE(P)(B) replies with a location binding update response message to MLM-PE(P)(A) via MLM-PE(C) (see 5.8 and 5.9 in Figure I.5). + +MLM-PE(C) may look up its location binding list and determine whether the two MLM-PE(P) instances have both registered to it. The MLM-PE(P)s are also registered to the correspondent MLM-PE(P) instance, indicating the location of each MLM-PE(P) to one another. + +After route optimization operations are completed between the two MLM-PE(P)s, the location binding cache in each MLM-PE(P) is updated and the optimized tunnel is installed. + +If the two MLM-PE(P) instances register to different MLM-PE(C) instances, the MLM-PE(C) associated with the mobile UE and MLM-PE(C) associated with the correspondent UE will coordinate with each other to provide the location of each MLM-PE(P) instance to the other. If the MLM-PE(C) associated with the mobile UE fails to retrieve the location of the MLM-PE(C) associated with the correspondent UE, it will notify the MLM-PE(P) associated with the mobile UE that route optimization is not available. The details for the different MLM-PE(C) case are shown in Figure I.6. + +![Sequence diagram illustrating route optimization considerations for the common MLM-PE(C).](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +The diagram shows the interaction between several network elements: UE, L3HEF, HDC-PE, MLM-PE(P)(A), MLM-PE(C)(A), MLM-PE(P)(B), and UE (B). The sequence of messages is as follows: + +- A "Route optimization" process is initiated between the L3HEF and the MLM-PE(P)(A). +- The L3HEF sends a "5.1 Route optimization indication" to the MLM-PE(P)(A). +- The MLM-PE(P)(A) sends a "5.2 Mobility location query request (route optimization)" to the MLM-PE(C)(A). +- The MLM-PE(C)(A) sends a "5.3 Mobility location query request (route optimization)" to the MLM-PE(P)(B). +- The MLM-PE(P)(B) sends a "5.4 Mobility location query response (route optimization)" to the MLM-PE(C)(A). +- The MLM-PE(C)(A) sends a "5.5 Mobility location query response" to the MLM-PE(P)(A). +- The MLM-PE(P)(A) sends a "5.6 Mobility location binding update request" to the MLM-PE(C)(A). +- The MLM-PE(C)(A) sends a "5.7 Mobility location binding update request" to the MLM-PE(P)(B). +- The MLM-PE(P)(B) sends a "5.8 Mobility location binding update response" to the MLM-PE(C)(A). +- The MLM-PE(C)(A) sends a "5.9 Mobility location binding update response" to the MLM-PE(P)(A). + +Legend: + +- Information flow (solid line with arrow) +- Media data connection (dashed line with arrow) + +Q.3314(12)\_FI.5 + +Sequence diagram illustrating route optimization considerations for the common MLM-PE(C). + +**Figure I.5 – Route optimization considerations for the common MLM-PE(C)** + +![Sequence diagram showing route optimization considerations for different MLM-PE(C)s. Lifelines: UE, HDC-PE, MLM-PE (P) (A), MLM-PE (C) (A), MLM-PE (P) (B), UE (B), MLM-PE (C) (B). The diagram illustrates the exchange of messages 6.1 through 6.9, with a yellow background highlighting the interaction between MLM-PE (C) (A) and MLM-PE (C) (B).](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +The sequence diagram illustrates the following interactions: + +- UE** and **HDC-PE** initiate a **Route optimization** process. +- HDC-PE** sends message **6.1 Route optimization indication** to **MLM-PE (P) (A)**. +- MLM-PE (P) (A)** sends message **6.2 Mobility location query request** to **MLM-PE (C) (A)**. +- MLM-PE (C) (A)** sends message **6.3 Mobility location query request** to **MLM-PE (C) (B)**. +- MLM-PE (C) (B)** sends message **6.4 Mobility location query response** to **MLM-PE (C) (A)**. +- MLM-PE (C) (A)** sends message **6.5 Mobility location query response** to **MLM-PE (P) (A)**. +- MLM-PE (P) (A)** sends message **6.6 Mobility location binding update request** to **MLM-PE (C) (A)**. +- MLM-PE (C) (A)** sends message **6.7 Mobility location binding update request** to **MLM-PE (C) (B)**. +- MLM-PE (C) (B)** sends message **6.8 Mobility location binding update response** to **MLM-PE (C) (A)**. +- MLM-PE (C) (A)** sends message **6.9 Mobility location binding update response** to **MLM-PE (P) (A)**. + +Legend: + +- Information flow (solid line with arrow) +- Media data connection (dashed line with arrow) + +Q.3314(12)\_Fl.6 + +Sequence diagram showing route optimization considerations for different MLM-PE(C)s. Lifelines: UE, HDC-PE, MLM-PE (P) (A), MLM-PE (C) (A), MLM-PE (P) (B), UE (B), MLM-PE (C) (B). The diagram illustrates the exchange of messages 6.1 through 6.9, with a yellow background highlighting the interaction between MLM-PE (C) (A) and MLM-PE (C) (B). + +**Figure I.6 – Route optimization considerations for the different MLM-PE(C)s** + +# Bibliography + +- [b-ITU-T Q.1001] Recommendation ITU-T Q.1001 (1988), *General aspects of public land mobile networks.* +- [b-ITU-T Q.1741.3] Recommendation ITU-T Q.1741.3 (2003), *IMT-2000 references to release 5 of GSM evolved UMTS core network.* +- [b-ITU-T Q.1761] Recommendation ITU-T Q.1761 (2004), *Principles and requirements for convergence of fixed and existing IMT-2000 systems.* +- [b-ITU-T Q.3222] Recommendation ITU-T Q.3222 (2010), *Requirements and protocol at the Ng interface between the transport location management physical entities.* +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional Requirements and Architecture of next generation networks.* +- [b-ITU-T Y.2014] Recommendation ITU-T Y.2014 (2010), *Network attachment control functions in next-generation networks.* +- [b-IETF RFC 2960] IETF RFC 2960 (2000), *Stream Control Transmission Protocol.* +- [b-IETF RFC 3046] IETF RFC 3046 (2001), *DHCP Relay Agent Information Option.* +- [b-IETF RFC 3220] IETF RFC 3220 (2002), *IP Mobility Support for IPv4.* +- [b-IETF RFC 3554] IETF RFC 3554 (2003), *On the Use of Stream Control Transmission Protocol (SCTP) with IPSec.* +- [b-IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol.* +- [b-IETF RFC 3775] IETF RFC 3775 (2004), *Mobility Support in IPv6.* +- [b-IETF RFC 4005] IETF RFC 4005 (2005), *Diameter Network Access Server Application.* +- [b-IETF RFC 5191] IETF RFC 5191 (2008), *Protocol for Carrying Authentication for Network Access (PANA).* +- [b-IETF RFC 5213] IETF RFC 5213 (2008), *Proxy Mobile IPv6.* + + + +## 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.3401-200703-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cb21a86d8d94f376e79d79231b4787f088cccff --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be48034f4838edb5a603a219249f04ca519a94bc083e5895f091f67ab51c68c0 +size 122401 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/12789c676288d43a4ea54847348ab275_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/12789c676288d43a4ea54847348ab275_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..373eb6d266a5b576f67e72cd4b5179301bbd7a21 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/12789c676288d43a4ea54847348ab275_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:218e9e7d3f87a68318c38097aff7fbe78719110112de4e8c76dae69c59f27477 +size 1606 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e6641cb9d140ab72e47256c6081cd47ff9425bf --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b787b09d7250847d1cbc6e330a915e8cffb815547f6fa934bd6c8f216aa1c214 +size 66794 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58b04e39744e7aa3aee01ac951966d43400f0a8b --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b24afeb4a8923df385ec3844cb85cb9773f36376f8eabd9606fab9c4add05f94 +size 138888 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e54d29bcadaa9cda8261f9440bad3454965ab69a --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f005f547b2033f63162dc84ec00001eb48ba206de402166ab9c6c5d8524c5794 +size 52620 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/32d3adccebdc60fbdd2af09f5b26f85c_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/32d3adccebdc60fbdd2af09f5b26f85c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64b1a9ae3a2dd585488774bdb1e93ee29288781b --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/32d3adccebdc60fbdd2af09f5b26f85c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7825fb5cc24569911f610792ada72f9328b98e2103886dbe54da63cdd78c5ce7 +size 1577 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/37a7ce3c67fa0cd0a7ec3d1652ec93c7_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/37a7ce3c67fa0cd0a7ec3d1652ec93c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a78250af8c2b825cb7ee5ca3bfd584e4cd8b785 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/37a7ce3c67fa0cd0a7ec3d1652ec93c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48e924b6fcd1d1f928d036a25a7c5dfe2e209bcadb39b9ae5a8fc587265401c7 +size 1740 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..545a6e21adccc4cad9981244b77887fff0a7fd40 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83709ecbd62a99206b6c3032b312ac8a3327b18e98d1d3aec4a84dc22a3fbbff +size 101151 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2083e3e8bb67d90e6a93ab6373c33869f806ad1 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e0145870d0fb86602f9a3153e150cd943f92f9bcd3181717fc3b1b659e4d47b +size 92512 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6681fa6acd7a2305bb4a565079f7406e777bfe16 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa8f1bcca904e91fba6b689a92095d6d64eee6b5e4f353e19bfa5fa69eae3e68 +size 52095 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/99667801a639ebdf2575f8e4c774d3f2_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/99667801a639ebdf2575f8e4c774d3f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a343e7e60fa1dda3ee186134568b06826b0a2ba --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/99667801a639ebdf2575f8e4c774d3f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59d20d57cab5524290f0766f137680deb8c559e86c80a34fed92bbe3e7d9ff5c +size 1107 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/9cc9adc413c10e9188032d5d4658ca65_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/9cc9adc413c10e9188032d5d4658ca65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..396ce1e69e1a32600c5d76dd87132df59c27f93e --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/9cc9adc413c10e9188032d5d4658ca65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a67bec72f32cfebd3d398c9f21a6b1605cd2c8f061606c42e0897898a0d7b2ac +size 1616 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3b2a2cafb3bd85e1e8e0d5e22619941747fb6db --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81e80fafae03925b0d2a1908d24f6840f5ff847fadfc297585214d25cdd98a2c +size 90329 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f58a5301a2ac8b92a3c4dd96ac146da5d146229 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47aea84edcf38cc52ab8d0a36feafc02d25728890beac3b886c3ffda487969f3 +size 26435 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4edf21ce73c607550b2ffe82d4fff28d3f4c6d26 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f72d8d79bb5d08df22343b11391029f11a9133894a5e113ae531b9378f440543 +size 44997 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/f8725ca1ae3037c427c5f3830a839ffe_img.jpg b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/f8725ca1ae3037c427c5f3830a839ffe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a500249719660976693ddec3099519f85770d72 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/f8725ca1ae3037c427c5f3830a839ffe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb8be7ec6c925daabcb6e9076a8974594e130f7bd49f7b7bf56a66bbb99f0a50 +size 1642 diff --git a/marked/Q/T-REC-Q.3401-200703-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a5b1f6faa8647de3ca503324dd4384a6a9055f92 --- /dev/null +++ b/marked/Q/T-REC-Q.3401-200703-I_PDF-E/raw.md @@ -0,0 +1,1525 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3401** + +(03/2007) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Service and session control protocols + +--- + +**NGN NNI signalling profile (protocol set 1)** + +ITU-T Recommendation Q.3401 + +# 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. + +## **ITU-T Recommendation Q.3401** + +# **NGN NNI signalling profile (protocol set 1)** + +## **Summary** + +ITU-T Recommendation Q.3401 defines the IP network-to-network interface (NNI) signalling profile for use between NGN carriers of protocol set 1 for voiceband services. + +## **Source** + +ITU-T Recommendation Q.3401 was approved on 9 March 2007 by ITU-T Study Group 11 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +NGN, profile, SDP, SIP, signalling. + +## 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 | +| 2.1 ITU-T references ..... | 1 | +| 2.2 IETF references ..... | 2 | +| 2.3 ETSI references ..... | 4 | +| 2.4 Other references..... | 4 | +| 3 Definitions ..... | 4 | +| 4 Abbreviations and acronyms ..... | 5 | +| 5 Reference model ..... | 6 | +| 6 Assumptions ..... | 7 | +| 7 Media availability in a SIP session..... | 8 | +| 8 Codec ..... | 8 | +| 8.1 Codec list ..... | 8 | +| 8.2 Packetization size ..... | 9 | +| 9 Routing and addressing..... | 9 | +| 10 Service level signalling profile ..... | 10 | +| 10.1 RFCs to be supported ..... | 10 | +| 10.2 SIP profile..... | 11 | +| 10.3 SDP profile ..... | 25 | +| 11 Transport-level profile ..... | 26 | +| 12 Call control signalling transport ..... | 27 | +| 13 IP protocol version..... | 27 | +| 14 Security considerations ..... | 27 | +| Appendix I – Call/signalling flows ..... | 28 | +| A.1 PSTN—IP—(NNI)—IP—PSTN ..... | 29 | +| A.2 PSTN—IP—(NNI)—IP—IP ..... | 31 | +| A.3 IP—IP—(NNI)—IP—PSTN ..... | 33 | +| A.4 IP—IP—(NNI)—IP—IP ..... | 34 | +| Bibliography..... | 36 | + + + +# NGN NNI signalling profile (protocol set 1) + +# 1 Scope + +This Recommendation contains a service-level profile, i.e., SIP/SDP interface description, between two network operators (NNI signalling profile), where the two different network operators may support different SIP/SDP profiles (i.e., they differ in terms of the SIP extensions, SIP information elements and SDP lines which are supported). Transport-level profile, e.g., RTP, is described as necessary as the media are described in the service-level signalling. + +NOTE 1 – Specification of the interworking between the SIP/SDP profile contained in this Recommendation and the SIP/SDP profiles in each operator's network (i.e., the functions contained inside the interworking entity/entities at the network boundary) is out of scope of this Recommendation. + +For the protocol set 1 of the NGN NNI signalling profile, this Recommendation covers the voiceband services such as VoIP (audio, text and so on), DTMF and T.38 fax. + +NOTE 2 – Support for a mobility management interface is not supported in this version of this interface. However, nomadicity of users between different networks is supported. + +# 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. + +## 2.1 ITU-T references + +- [ITU-T G.711] ITU-T Recommendation G.711 (1988), *Pulse code modulation (PCM) of voice frequencies*. +- [ITU-T G.722] ITU-T Recommendation G.722 (1988), *7 kHz audio-coding within 64 kbit/s*. +- [ITU-T G.722.1] ITU-T Recommendation G.722.1 (2005), *Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss*. +- [ITU-T G.722.2] ITU-T Recommendation G.722.2 (2003), *Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)*. +- [ITU-T G.726] ITU-T Recommendation G.726 (1990), *40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)*. +- [ITU-T G.729] ITU-T Recommendation G.729 (1996), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)*. +- [ITU-T G.729A] ITU-T Recommendation G.729 Annex A (1996), *Reduced complexity 8 kbit/s CS-ACELP speech codec*. +- [ITU-T G.729.1] ITU-T Recommendation G.729.1 (2006), *G.729-based embedded variable bit-rate coder: An 8-32 kbit/s scalable wideband coder bitstream interoperable with G.729*. +- [ITU-T Q.761] ITU-T Recommendation Q.761 (1999), *Signalling System No. 7 – ISDN User Part functional description*. + +- [ITU-T Q.762] ITU-T Recommendation Q.762 (1999), *Signalling System No. 7 – ISDN User Part general functions of messages and signals.* +- [ITU-T Q.763] ITU-T Recommendation Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes.* +- [ITU-T Q.764] ITU-T Recommendation Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures.* +- [ITU-T Q.1912.5] ITU-T Recommendation Q.1912.5 (2004), *Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part.* +- [ITU-T T.38] ITU-T Recommendation T.38 (2005), *Procedures for real-time Group 3 facsimile communication over IP networks.* +- [ITU-T T.140] ITU-T Recommendation T.140 (1998), *Protocol for multimedia application text conversation.* +- [ITU-T Y.2012] ITU-T Recommendation Y.2012 (2006), *Functional requirements and architecture of the NGN release 1.* + +## 2.2 IETF references + +### 2.2.1 Service-level signalling specifications + +- [RFC 2046] IETF RFC 2046 (1996), *Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types.* +- [RFC 2327] IETF RFC 2327 (1998), *SDP: Session Description Protocol.* +- [RFC 2976] IETF RFC 2976 (2000), *The SIP INFO Method.* +- [RFC 3087] IETF RFC 3087 (2001), *Control of Service Context using SIP Request-URI.* +- [RFC 3204] IETF RFC 3204 (2001), *MIME media types for ISUP and QSIG Objects.* +- [RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol.* +- [RFC 3262] IETF RFC 3262 (2002), *Reliability of Provisional Responses in the Session Initiation Protocol (SIP).* +- [RFC 3264] IETF RFC 3264 (2002), *An Offer/Answer Model with the Session Description Protocol (SDP).* +- [RFC 3265] IETF RFC 3265 (2002), *Session Initiation Protocol (SIP)-Specific Event Notification.* +- [RFC 3311] IETF RFC 3311 (2002), *The Session Initiation Protocol (SIP) UPDATE Method.* +- [RFC 3312] IETF RFC 3312 (2002), *Integration of Resource Management and Session Initiation Protocol (SIP).* +- [RFC 3323] IETF RFC 3323 (2002), *A Privacy Mechanism for the Session Initiation Protocol (SIP).* +- [RFC 3324] IETF RFC 3324 (2002), *Short Term Requirements for Network Asserted Identity.* +- [RFC 3325] IETF RFC 3325 (2002), *Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks.* +- [RFC 3326] IETF RFC 3326 (2002), *The Reason Header Field for the Session Initiation Protocol (SIP).* + +- [RFC 3398] IETF RFC 3398 (2002), *Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping*. +- [RFC 3420] IETF RFC 3420 (2002), *Internet Media Type message/sipfrag*. +- [RFC 3428] IETF RFC 3428 (2002), *Session Initiation Protocol (SIP) Extension for Instant Messaging*. +- [RFC 3455] IETF RFC 3455 (2003), *Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)*. +- [RFC 3515] IETF RFC 3515 (2003), *The Session Initiation Protocol (SIP) Refer Method*. +- [RFC 3824] IETF RFC 3824 (2004), *Using E.164 numbers with the Session Initiation Protocol (SIP)*. +- [RFC 3840] IETF RFC 3840 (2004), *Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)*. +- [RFC 3841] IETF RFC 3841 (2004), *Caller Preferences for the Session Initiation Protocol (SIP)*. +- [RFC 3891] IETF RFC 3891 (2004), *The Session Initiation Protocol (SIP) Replaces Header*. +- [RFC 3892] IETF RFC 3892 (2004), *The Session Initiation Protocol (SIP) Referred-By Mechanism*. +- [RFC 3893] IETF RFC 3893 (2004), *Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format*. +- [RFC 3911] IETF RFC 3911 (2004), *The Session Initiation Protocol (SIP) Join Header*. +- [RFC 3959] IETF RFC 3959 (2004), *The Early Session Disposition Type for the Session Initiation Protocol (SIP)*. +- [RFC 3960] IETF RFC 3960 (2004), *Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)*. +- [RFC 3966] IETF RFC 3966 (2004), *The tel URI for Telephone Numbers*. +- [RFC 4028] IETF RFC 4028 (2005), *Session Timers in the Session Initiation Protocol (SIP)*. +- [RFC 4032] IETF RFC 4032 (2005), *Update to the Session Initiation Protocol (SIP) Preconditions Framework*. +- [RFC 4235] IETF RFC 4235 (2005), *An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)*. +- [RFC 4244] IETF RFC 4244 (2005), *An Extension to the Session Initiation Protocol (SIP) for Request History Information*. +- [RFC 4412] IETF RFC 4412 (2006), *Communications Resource Priority for the Session Initiation Protocol (SIP)*. +- [RFC 4458] IETF RFC 4458 (2006), *Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)*. +- [RFC 4483] IETF RFC 4483 (2006), *A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages*. +- [RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*. +- [RFC 4694] IETF RFC 4694 (2006), *Number Portability Parameters for the tel URI*. + +### 2.2.2 Transport-level specifications + +- [RFC 2833] IETF RFC 2833 (2000), *RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals*. +- [RFC 3267] IETF RFC 3267 (2002), *Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs*. +- [RFC 3389] IETF RFC 3389 (2002), *Real-time Transport Protocol (RTP) Payload for Comfort Noise*. +- [RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*. +- [RFC 3551] IETF RFC 3551 (2003), *RTP Profile for Audio and Video Conferences with Minimal Control*. +- [RFC 4103] IETF RFC 4103 (2005), *RTP Payload for Text Conversation*. + +## 2.3 ETSI references + +- [EN 301 703] ETSI EN 301 703 V7.0.2 (1999), *Digital cellular telecommunications system (Phase 2+) (GSM); Adaptive Multi-Rate (AMR); Speech processing functions; General description (GSM 06.71 version 7.0.2 Release 1998)*. + +## 2.4 Other references + +- [TIA-127-A] TIA-127-A (2004), *Enhanced Variable Rate Codec Speech Service Option 3 for Wideband Spread Spectrum Digital Systems*. +- [TIA-1016] TIA-1016-A (2006), *Source-Controlled Variable-Rate Multimode Wideband Speech Codec (VMR-WB), Service Options 62 and 63 for Spread Spectrum Systems*. + +# 3 Definitions + +For SIP- and SDP-specific terminology, reference shall be made to [RFC 3261], [RFC 3264] and [RFC 2327]. For NGN-specific terminology, reference shall be made to [ITU-T Y.2012]. Definitions for additional terminology used in this Recommendation are as follows: + +**3.1 codec list:** A codec list defines the codecs that should be announced in SIP/SDP messages exchanged over the NNI based on a bilateral agreement established between the NGNs. + +NOTE – The purpose of the codec list is to promote interoperability, limit the number of transcodings on network connections and possibly improve network resource management. + +**3.2 service control functions (SCF):** The service control functions establish, monitor, support and release multimedia sessions, and manage the user's service interactions. + +**3.3 SIP back-to-back user agent (B2BUA):** A back-to-back user agent (B2BUA) is a concatenation of a SIP user agent client (UAC) and user agent server (UAS). + +NOTE – The IETF defines the B2BUA in [RFC 3261] as "a logical entity that receives a request and processes it as a user agent server (UAS). In order to determine how the request should be answered, it acts as a user agent client (UAC) and generates requests. Unlike a proxy server, it maintains dialog state and shall participate in all requests sent on the dialogs it has established. Since it is a concatenation of a UAC and UAS, no explicit definitions are needed for its behavior." (UAC and UAS behaviors are defined in [RFC 3261].) A B2BUA reformulates a message before sending it as a new request. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|----------------------------------------------------------| +| ACM | Address Complete Message | +| AMR | Adaptive Multirate (codec) | +| ANM | Answer Message | +| B2BUA | Back-to-Back User Agent | +| BGC-FE | Breakout Gateway Control Functional Entity | +| CSC-FE | Call Session Control Functional Entity | +| EVRC | Enhanced Variable Rate Codec | +| FQDN | Fully Qualified Domain Name | +| IAM | Initial Address Message | +| IBC-FE | Interconnection Border gateway Control Functional Entity | +| IBG-FE | Interconnection Border Gateway Functional Entity | +| ISUP | ISDN User Part | +| MG | Media Gateway | +| MGC-FE | Media Gateway Control Functional Entity | +| MIME | Multipurpose Internet Mail Extensions | +| NGN-TE | NGN Terminal Equipment | +| NNI | Network-to-Network Interface | +| PSTN | Public Switched Telephone Network | +| PT | Payload Type | +| REL | Release | +| RFC | Request For Comments | +| RLC | Release Complete | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| SCF | Service Control Functions | +| SCTP | Stream Control Transmission Protocol | +| SDP | Session Description Protocol | +| SG-FE | Signalling Gateway Functional Entity | +| SIP | Session Initiation Protocol | +| SIP-I | SIP with encapsulated ISUP | +| SIPS | Session Initiation Protocol Secure | +| TCP | Transmission Control Protocol | +| TMG-FE | Trunk Media Gateway Functional Entity | +| UA | User Agent | +| UAC | User Agent Client | + +| | | +|--------|-----------------------------------| +| UAS | User Agent Server | +| UDP | User Datagram Protocol | +| UNI | User-to-Network Interface | +| URI | Universal Resource Identifier | +| VMR-WB | Variable-Rate Multi-Mode Wideband | + +# 5 Reference model + +Figure 5-1 illustrates the interface covered by this Recommendation in the NGN architecture defined in [ITU-T Y.2012]. + +![Diagram of the NGN architecture reference model showing layers and interfaces.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the NGN architecture reference model, showing the following components and interfaces: + +- Applications**: Located at the top, connected to the Service stratum via the **ANI** (Application Network Interface). +- Service stratum**: The upper layer, containing: + - Application support functions and service support functions**: The top functional block. + - Service control functions**: The middle functional block, which includes **Service user profiles**. +- Transport stratum**: The lower layer, containing: + - Transport control functions**: The top functional block of this stratum, which includes **Network attachment control functions** (with **Transport user profiles**) and **Resource and admission control functions**. + - Transport functions**: The bottom functional block. +- Management functions**: A vertical block on the left side, connected to the Service and Transport strata via **Management** (green dashed lines). +- End-user functions**: A vertical block on the left, connected to the Service stratum via **Control** (black dashed lines) and to the Transport stratum via **Media** (blue hatched lines). It connects to the **UNI** (User-to-Network Interface). +- Other networks**: A vertical block on the right side, connected to the Service stratum via **Control** (black dashed lines) and to the Transport stratum via **Media** (blue hatched lines). It connects to the **NNI** (Network-to-Network Interface). +- Interfaces**: + - ANI**: Between Applications and the Service stratum. + - UNI**: Between End-user functions and the Transport stratum. + - NNI**: Between Other networks and the Transport stratum. +- Legend**: + - Control**: Represented by a black dashed line. + - Media**: Represented by a blue hatched line. + - Management**: Represented by a green dashed line. +- Scope Callout**: A box on the right points to the interface between the Service stratum and Other networks, stating: "This interface is the scope of this Recommendation". +- Reference**: Q.3401(07)\_F5-1 + +Diagram of the NGN architecture reference model showing layers and interfaces. + +Figure 5-1 – The interface covered by this Recommendation within the NGN architecture + +Figure 5-2 illustrates the interconnection reference model for the NNI. + +![Figure 5-2 – VoIP interconnection reference model diagram showing two providers (A and B) connected via logical interfaces. Provider A and B each have Service control functions, Transport functions, and MG (Media Gateway) components. The diagram shows connections to IP phones, Wireless networks, and PSTN. A callout box states 'This interface is the scope of this Recommendation' pointing to the logical interface between the Service control functions of both providers. A legend at the bottom indicates Bearer (RTP/IP) as a solid blue line and Signal (SIP) as a dashed red line.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +The diagram illustrates the VoIP interconnection reference model between two providers, Provider A and Provider B. Each provider's network is represented by a yellow cloud containing three main functional blocks: 'Service control functions' (green), 'Transport functions' (yellow), and 'MG' (Media Gateway, green). The 'Service control functions' are connected to 'Transport functions', which in turn are connected to the 'MG'. The 'MG' is connected to the 'PSTN' (green cloud) via an 'SS7' link. External connections include 'IP phone' and 'Wireless' (radio tower icons) connected to the 'Service control functions'. A central vertical dashed line represents the 'Logical interfaces' between the two providers. Specifically, the 'Service control functions' of Provider A and Provider B are connected via a dashed red line (Signal (SIP)), and their 'Transport functions' are connected via a solid blue line (Bearer (RTP/IP)). A callout box with a purple border points to this dashed red line and contains the text: 'This interface is the scope of this Recommendation'. A legend at the bottom left shows a solid blue line for 'Bearer (RTP/IP)' and a dashed red line for 'Signal (SIP)'. The identifier 'Q.3401(07)\_F5-2' is located at the bottom right of the diagram. + +Figure 5-2 – VoIP interconnection reference model diagram showing two providers (A and B) connected via logical interfaces. Provider A and B each have Service control functions, Transport functions, and MG (Media Gateway) components. The diagram shows connections to IP phones, Wireless networks, and PSTN. A callout box states 'This interface is the scope of this Recommendation' pointing to the logical interface between the Service control functions of both providers. A legend at the bottom indicates Bearer (RTP/IP) as a solid blue line and Signal (SIP) as a dashed red line. + +Figure 5-2 – VoIP interconnection reference model + +# 6 Assumptions + +This Recommendation is based on the following set of assumptions: + +- 1) It is recognized that data-oriented call control (e.g., http to a web portal on an application server), in addition to SIP-oriented call control, may occur across the NNI. For example, a network-based service may allow a user to initiate calls or control the disposition of incoming calls through a web browser interface using http. It is assumed that such data-oriented call control involves no differentiated treatment from other data traffic, and so is not described further in this Recommendation. Differentiated treatment may be desirable in some cases. +- 2) The logical interfaces associated with the service control functions in the service stratum and the transport functions in the transport stratum enable interconnection between two service provider networks in a peering environment. +- 3) Each provider may use a set of service control functions and transport functions to connect to multiple peer networks. +- 4) SIP back-to-back user agent (B2BUA) functions may be used in support of network interconnection. +- 5) Only the network-to-network interface (NNI) is supported between two peering VoIP carriers. There may be an IP transit network between two peering VoIP service providers. +- 6) SIP is used for service-level signalling. The SIP messages may contain MIME encapsulated ISUP in order to facilitate interoperability with the PSTN. ISUP is specified in [ITU-T Q.761]-[ITU-T Q.764]. + +- 7) RTP is used for voice transport. +- 8) IPv4 is supported at the NNI. Support for IPv6 is optional based on bilateral agreement. +- 9) The IPv6 operator is responsible for IPv4/IPv6 interworking. + +# 7 Media availability in a SIP session + +The following apply to any media session established across the NNI using SIP: + +- a) The terminating-side network of the NNI shall pass any media packets in the direction toward the originating party as soon as they are available. A primary reason is to allow the caller to hear inband call progress tones if PSTN interworking is encountered on a voice call. +- b) The originating-side network of the NNI: + - shall pass media packets from the originating party in the direction toward the terminating party upon and after receiving a final SDP answer within a SIP 2xx response to the INVITE for normal dialog; + - may pass media packets from the originating party in the direction toward the terminating party as early as the first SDP answer has occurred, which is in a SIP 1xx response to the INVITE when early dialog has been set up. A network, as a policy, may choose not to send media packets from the originating party until the final SDP offer/answer has been made in order to avoid theft-of-service in cases where usage-sensitive billing is employed. +- c) As per [RFC 3261], once a SIP dialog has ended, the flow of media packets shall be halted. +- d) The absence of media packets across the NNI over any time interval in either direction shall not be taken by either network as a sufficient reason to clear the SIP session. When the status of media flows is active according to the SDP negotiation, the absence of packets across the NNI for a given duration may constitute a reason to clear the SIP session. + +NOTE – The absence of packets across the NNI for a given duration can be a reason to clear the SIP session only when it is sure that it is because of the failure. + +# 8 Codec + +## 8.1 Codec list + +It is the responsibility of entities at the rim of the NGN (e.g., NGN-TE) and network equipment originating and terminating the NGN IP media flows to negotiate and select a common codec for each "end-to-end" media session. Therefore, the NGN shall allow end-to-end negotiation within the agreed codec list between NGN entities (terminals and network elements) and may allow it outside the list based on its network policy. + +NOTE 1 – In case a common codec cannot be negotiated, this Recommendation does not provide procedures for the NNI. + +NOTE 2 – In the interest of promoting interoperability, limiting the number of transcodings on network connections and possibly improving network resource management, it is desirable that the NGNs establish bilateral agreements about the codec list. SIP/SDP messages exchanged over the NNI indicate a request to use one or more of the codecs in this codec list. + +The way of handling messages with codecs that are not in the codec list or with no codec in the list depends on the network policy, i.e., some networks may allow the use of codecs that are not in the codec list, while others may reject such messages. + +Agreement on a codec list does not put any direct requirement on the codecs that have to be implemented in the network for transcoding purposes, nor does it mean that terminals shall support + +all the codecs in the list. Hence, conformance of a SIP/SDP offer to the agreed list does not ensure successful codec negotiation. + +NOTE 3 – When the codecs to be supported across an NNI is restricted, due to network policy, a bilateral agreement, as in Note 2 is desirable. When such a bilateral agreement cannot be established, the codec list shall contain G.711 A/mu law [ITU-T G.711]. + +NOTE 4 – While any codec may be used within the codec list based on the bilateral agreement, it is recommended that the list contain AMR NB [EN 301 703], EVRC [TIA-127-A], G.729 [ITU-T G.729], G.729A [ITU-T G.729A], G.722.1 [ITU-T G.722.1] and G.726 [ITU-T G.726]. To enable the provision of voice service with a superior quality, it is highly recommended that the list contain a wideband codec such as AMR-WB [ITU-T G.722.2], VMR-WB [TIA-1016], G.722 [ITU-T G.722], G.729.1 [ITU-T G.729.1]. To support hard of hearing, it is recommended that T.140 [ITU-T T.140] is supported as a codec in the codec list. Where the interconnect is to an existing PSTN/ISDN, it is recommended that T.140 [ITU-T T.140] is adapted to be carried over G.711 A/mu law [ITU-T G.711]. + +NOTE 5 – For individual sessions, a call signalling element, such as a CSC-FE, an application server or an IBC-FE, that has visibility of the end-to-end codec negotiation may determine the need and may initiate transcoding between the endpoints. + +NOTE 6 – Although transcoding should be avoided wherever possible, the network may support transcoding to increase the chance of session establishment (e.g., in configurations where the codecs supported by the endpoints belong to the agreed list but no common codec can be found). However, agreement on a codec list does not imply that the network should support transcoding between one of the codecs in the list and any other codec, nor between any combination of the codecs in the list. + +## 8.2 Packetization size + +When a packetization size is not selected by codec negotiation between terminals and/or network elements or agreed by bilateral arrangement, a speech packetization sampling size of 10 ms should be used for G.711 coded speech; this is recommended as an optimum value balancing end-to-end delay with network utilization. It is recognized that there may be network constraints that require that a higher value is agreed by bilateral arrangement; in such cases, a value of 20 ms is recommended. It is also recognized that there should be a bilateral agreement on an upper limit of packetization size that should not be exceeded, e.g., 60 ms. + +NOTE – Where a packetization size is selected by codec negotiation between terminals and/or network elements, this Recommendation places no requirements on the value to be selected. + +# 9 Routing and addressing + +Table 9-1 describes URI formats that shall be supported on the NNI. Other formats may be supported. + +**Table 9-1 – URI formats** + +| | | +|---------|------------------------------------------------------| +| SIP URI | sip:+[country code][national number]@host;user=phone | +| | Description: Global E.164 number | +| | Reference: [RFC 3966] | +| tel URI | tel:+[country code][national number] | +| | Description: Global E.164 number | +| | Reference: [RFC 3966] | + +There can be several ways for determining the destination of the SIP message based on the tel URI; ENUM-based routing, number-based routing, and so on. In this Recommendation, it is assumed that each network knows the address information of the peer network based on the number. + +# 10 Service level signalling profile + +## 10.1 RFCs to be supported + +M: Mandatory. The NNI shall comply with the listed RFC unless otherwise agreed bilaterally between carriers. For further information on the handling of elements in the mandatory RFCs, see the relevant clause below. + +O: Optional. The NNI may comply with the listed RFC unless otherwise agreed bilaterally between carriers. + +**Table 10-1 – RFCs to be supported** + +| SIP Extensions | Title | M/O | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------|------------| +| RFC 2046 [RFC 2046] | Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types | O | +| RFC 2327 [RFC 2327] | SDP: Session Description Protocol | M | +| RFC 2976 [RFC 2976] | The SIP INFO Method | O | +| RFC 3087 [RFC 3087] | Control of Service Context using SIP Request-URI | O | +| RFC 3204 [RFC 3204] | MIME media types for ISUP and QSIG Objects | O | +| RFC 3261 [RFC 3261] | SIP: Session Initiation Protocol | M | +| RFC 3262 [RFC 3262] | Reliability of Provisional Responses in the Session Initiation Protocol (SIP) | M | +| RFC 3264 [RFC 3264] | An Offer/Answer Model with the Session Description Protocol (SDP) | M | +| RFC 3265 [RFC 3265] | Session Initiation Protocol (SIP)-Specific Event Notification | O | +| RFC 3311 [RFC 3311] | The Session Initiation Protocol (SIP) UPDATE Method | M | +| RFC 3312 [RFC 3312] | Integration of Resource Management and Session Initiation Protocol (SIP) | O | +| RFC 3323 [RFC 3323] | A Privacy Mechanism for the Session Initiation Protocol (SIP) | M | +| RFC 3324 [RFC 3324] | Short Term Requirements for Network Asserted Identity | O | +| RFC 3325 [RFC 3325] | Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks | M | +| RFC 3326 [RFC 3326] | The Reason Header Field for the Session Initiation Protocol (SIP) | M | +| RFC 3398 [RFC 3398] | Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping | O | +| RFC 3420 [RFC 3420] | Internet Media Type message/sipfrag | O | +| RFC 3428 [RFC 3428] | Session Initiation Protocol (SIP) Extension for Instant Messaging | O | +| RFC 3455 [RFC 3455] | Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) | O | +| RFC 3515 [RFC 3515] | The Session Initiation Protocol (SIP) Refer Method | O | +| RFC 3824 [RFC 3824] | Using E.164 numbers with the Session Initiation Protocol (SIP) | O | +| RFC 3840 [RFC 3840] | Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) | O | +| RFC 3841 [RFC 3841] | Caller Preferences for the Session Initiation Protocol (SIP) | O | +| RFC 3891 [RFC 3891] | The Session Initiation Protocol (SIP) Replaces Header | O | +| RFC 3892 [RFC 3892] | The Session Initiation Protocol (SIP) Referred-By Mechanism | O | +| RFC 3893 [RFC 3893] | Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format | O | + +**Table 10-1 – RFCs to be supported** + +| SIP Extensions | Title | M/O | +|-----------------------|----------------------------------------------------------------------------------------------------------------|------------| +| RFC 3911 [RFC 3911] | The Session Initiation Protocol (SIP) Join Header | O | +| RFC 3959 [RFC 3959] | The Early Session Disposition Type for the Session Initiation Protocol (SIP) | O | +| RFC 3960 [RFC 3960] | Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) | O | +| RFC 3966 [RFC 3966] | The tel URI for Telephone Numbers | M | +| RFC 4028 [RFC 4028] | Session Timers in the Session Initiation Protocol (SIP) | M | +| RFC 4032 [RFC 4032] | Update to the Session Initiation Protocol (SIP) Preconditions Framework | O | +| RFC 4235 [RFC 4235] | An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP) | O | +| RFC 4244 [RFC 4244] | An Extension to the Session Initiation Protocol (SIP) for Request History Information | O | +| RFC 4412 [RFC 4412] | Communications Resource Priority for the Session Initiation Protocol (SIP) | O | +| RFC 4458 [RFC 4458] | Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR) | O | +| RFC 4483 [RFC 4483] | A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages | O | +| RFC 4566 [RFC 4566] | SDP: Session Description Protocol | M | +| RFC 4694 [RFC 4694] | Number Portability Parameters for the tel URI | O | + +## **10.2 SIP profile** + +### **10.2.1 SIP profile based on RFC 3261** + +This clause defines a SIP profile for the SCF at the NNI interface. This clause is structured to mirror [RFC 3261] and its section numbering. The following clauses are numbered such that the fourth digit (i.e., x of 10.2.1.x) tracks the section numbers of [RFC 3261], and clause titles track the section titles of [RFC 3261]. + +This clause defines the set of enhancements of, and restrictions on, a standard SIP implementation based on [RFC 3261]. + +Unless otherwise stated in this Recommendation, the SCF shall act in accordance with [RFC 3261]. + +#### **10.2.1.1 Introduction** + +RFC 3261 section 1 is informational. + +#### **10.2.1.2 Overview of SIP functionality** + +RFC 3261 section 2 is informational. + +#### **10.2.1.3 Terminology** + +RFC 3261 section 3 is informational. + +#### **10.2.1.4 Overview of operation** + +RFC 3261 section 4 is informational. + +#### **10.2.1.5 Structure of the protocol** + +The structure of the protocol can be found in RFC 3261 section 5, which is informational. + +#### **10.2.1.6 Definitions** + +RFC 3261 section 6 defines the terms that have special significance for SIP. Additional definitions can be found in clause 3. + +The reader should note that the term "client" in this clause covers both UACs and proxies. + +#### **10.2.1.7 SIP messages** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7 except as noted in this clause. + +##### **10.2.1.7.1 Requests** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7.1 except as noted in this clause. + +The INVITE, ACK, CANCEL, BYE, UPDATE and PRACK methods shall be supported. The OPTIONS and REGISTER methods may be supported. + +The Request-URI shall be a SIP URI, as defined in [RFC 3261], or a tel URI, as defined in [RFC 3966]. The SIPS URI format may be supported. + +The Request-URI in an initial INVITE for a basic telephone call1 shall identify the called party using a tel URI or by using the telephone-subscriber syntax (i.e., the dialled phone number) in a SIP URI. When the Request-URI is a SIP URI, the host part of the Request-URI shall identify the SCF or the entity to which the message is addressed. + +The Request-URI for other requests associated with a basic telephone call shall identify the targeted host using the IP address or FQDN, as given by the Contact header. + +The host part of the Request-URI typically agrees with one of the host names of the receiving server. However, if the Request-URI of a received INVITE does not so agree, the server should proxy the request to another entity based on saved translation information or pre-provisioned policy information. + +##### **10.2.1.7.2 Responses** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7.2. + +##### **10.2.1.7.3 Header fields** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7.3. + +##### **10.2.1.7.4 Bodies** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7.4 except as noted in this clause. + +###### **10.2.1.7.4.1 Message body types** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7.4.1 except as noted in this clause. + +The SCF shall set the SIP profile to support the message body type "application/sdp"; other message body types may be supported. + +--- + +1 This includes INVITEs generated as a result of forwarding. + +The message body type "application/sdp" shall be supported with the INVITE and UPDATE methods as well as any non-failure response to these methods. And it should be supported with the PRACK method as well as any non-failure response to the method in order to allow interworking with a H.323 network and support of services operating third party call control. + +The message body type "application/sdp" may be supported with failure responses, such as 488 (not acceptable here), to the above methods. + +###### **10.2.1.7.4.2 Message body length** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7.4.2. + +##### **10.2.1.7.5 Framing SIP messages** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 7.5. + +#### **10.2.1.8 General user agent behavior** + +This clause and its sub-clauses apply only if the SCF acts as a UA, i.e., B2BUA or redirect server. + +The SCF shall behave in accordance with RFC 3261 section 8 except as noted in this clause. + +Support for multiple simultaneous media streams for a single call is optional. + +Note that the behavior defined in this clause applies only to requests and responses outside a dialog. The behavior within a dialog is defined in 10.2.1.12. + +##### **10.2.1.8.1 UAC behavior** + +The SCF shall behave in accordance with RFC 3261 section 8.1 except as noted in this clause. + +###### **10.2.1.8.1.1 Generating the request** + +The SCF shall behave in accordance with RFC 3261 section 8.1.1 except as noted in this clause. + +Request-URI in the request contains the address of the called party. This will normally be a telephone number, but it may also be a general SIP URI. The From and To fields in the request might contain random strings that protect the privacy of the session originator. + +Refer to clause 10.2.1.20 for further details of various header field values to be used. + +###### **10.2.1.8.1.2 Sending the request** + +The SCF shall behave in accordance with RFC 3261 section 8.1.2. + +###### **10.2.1.8.1.3 Processing responses** + +The SCF shall behave in accordance with RFC 3261 section 8.1.3 except as noted in this clause. + +Support for the SIP authorization procedures, which is used when 401 (unauthorized) or 407 (proxy authentication required) is received, is optional. If the support is provided, it shall be as specified in RFC 3261 section 8.1.3.5. + +Support for the SIP retry procedures, which is used when 420 (bad extension) is received, is optional. If the support is provided, it shall be as specified in RFC 3261 section 8.1.3.5. + +##### **10.2.1.8.2 UAS behavior** + +The SCF shall behave in accordance with RFC 3261 section 8.2. + +##### **10.2.1.8.3 Redirect servers** + +The SCF shall behave in accordance with RFC 3261 section 8.3 except as noted in this clause. + +The SCF is not required to provide the redirect server function. However, it may provide the redirect server function and invoke redirections for a limited number of INVITE requests. The + +rationale for limiting the number of redirections is to control SIP signalling traffic across the NNI and processing complexity associated with redirections. The Max-Forwards header (see clause 10.2.1.20), which is mandatory in all SIP requests, serves to limit the number of hops a request can make on the way to its destination. If the redirection function is supported, then the SCF shall be in accordance with RFC 3261 section 8.3. + +3xx response codes may be supported at the NNI, based on bilateral agreements to support redirections that may take place in the interconnecting network or in a downstream network receiving the INVITE message. + +#### **10.2.1.9 Cancelling a request** + +In this clause and in its sub-clauses, the handling that is specific to a proxy applies only if the SCF acts as a SIP proxy, the handling that is specific to a UA applies only if the SCF acts as a UA, i.e., B2BUA or redirect server, and the handling that is specific to a registrar applies only if the SCF acts as a registrar. + +The SCF shall behave in accordance with RFC 3261 section 9. + +#### **10.2.1.10 Registrations** + +In this clause and in its sub-clauses, the handling that is specific to a proxy applies only if the SCF acts as a SIP proxy, the handling that is specific to a UA applies only if the SCF acts as a UA, i.e., B2BUA or redirect server, and the handling that is specific to a registrar applies only if the SCF acts as a registrar. + +Support for the registrations is optional. If the support is provided, it shall be as specified in RFC 3261 section 10. + +#### **10.2.1.11 Querying for capabilities** + +In this clause and in its sub-clauses, the handling that is specific to a proxy applies only if the SCF acts as a SIP proxy, the handling that is specific to a UA applies only if the SCF acts as a UA, i.e., B2BUA or redirect server, and the handling that is specific to a registrar applies only if the SCF acts as a registrar. + +Support for querying for capabilities is optional. If the support is provided, it shall be as specified in RFC 3261 section 11. + +#### **10.2.1.12 Dialogs** + +This clause and its sub-clauses apply only if the SCF acts as a UA, i.e., B2BUA or redirect server. + +The SCF shall behave in accordance with RFC 3261 section 12 except as noted in this clause. + +##### **10.2.1.12.1 Creation of a dialog** + +Support for SIPS URIs is optional. If the support is provided, it shall be as specified in RFC 3261 section 12.1. + +##### **10.2.1.12.2 Requests within a dialog** + +Support for SIPS URIs is optional. If the support is provided, it shall be as specified in RFC 3261 section 12.2. + +##### **10.2.1.12.3 Termination of a dialog** + +The SCF shall behave in accordance with RFC 3261 section 12.3. + +#### **10.2.1.13 Initiating a session** + +This clause and its sub-clauses apply only if the SCF acts as a UA, i.e., B2BUA or redirect server. + +The SCF shall behave in accordance with RFC 3261 section 13 except as noted in this sub-clause. + +The UAC should include a message body type "application/sdp" with the initial INVITE whenever possible. + +The support of initial INVITE without SDP offer is recommended in order to allow interworking with a H.323 network and support of services operating third party call control. + +To support codec selection: + +- When the initial INVITE includes an SDP offer, an SDP answer may be included either in the provisional reliable non-failure response to the INVITE (e.g., 183 Session Progress sent reliably) or in the final non-failure response to the INVITE (i.e., 2xx), and, if not included in the provisional reliable non-failure response, shall be included in the final non-failure response. +- When the initial INVITE does not include an SDP offer, the initial SDP offer shall be included in the first provisional reliable non-failure response to the INVITE, that is in the first 18x response sent reliably (e.g., 180 Ringing sent reliably) if any, or in the final non-failure response to the INVITE (i.e., 2xx) if not. If the initial SDP offer is included in a reliable provisional response, the SDP answer shall be included in the PRACK message acknowledging this response. If the initial SDP offer is included in the final non-failure response to the INVITE (i.e., 2xx), the SDP answer shall be included in the ACK message acknowledging this response. + +#### **10.2.1.14 Modifying an existing session** + +This clause and its sub-clauses apply only if the SCF acts as a UA, i.e., B2BUA or redirect server. + +The SCF shall behave in accordance with RFC 3261 section 14 except as noted in this clause. + +When constructing an SDP answer to a new received SDP offer contained in a re-INVITE or UPDATE method, if the SCF controls the transfer plane, listening IP address and port number negotiated during the initial SDP negotiation procedure for a given media stream should not be modified. + +#### **10.2.1.15 Terminating a session** + +This clause and its sub-clauses apply only if the SCF acts as a UA, i.e., B2BUA or redirect server. + +The SCF shall behave in accordance with RFC 3261 section 15. + +#### **10.2.1.16 Proxy bahavior** + +This clause and its sub-clauses apply only if the SCF acts as a SIP proxy. + +The SCF shall behave in accordance with RFC 3261 section 16 except as noted in this clause. + +Support for multiple simultaneous media streams for a single call is optional. Since parallel forking, as described in [RFC 3960], may result in multiple simultaneous media streams for a single call, the SCF should not use parallel forking. UA or outbound proxy server may restrict forking by using Request-Disposition header with 'no-fork' option tag as specified in [RFC 3841]. + +#### **10.2.1.17 Transactions** + +In this clause and in its sub-clauses, the handling that is specific to a proxy applies only if the SCF acts as a SIP proxy, the handling that is specific to a UA apply only if the SCF acts as a UA, i.e., B2BUA or redirect server, and the handling that is specific to a registrar applies only if the SCF acts as a registrar. + +The SCF shall behave in accordance with RFC 3261 section 17 except as noted in this clause. + +The SCF may return an error code 486 (busy here) to an INVITE request for a user if a dialog already exists for that user and the new INVITE is not part of that dialog. + +#### **10.2.1.18 Transport** + +The SCF shall behave in accordance with RFC 3261 section 18. However, clause 12 takes precedence over RFC 3261 section 18 in case of any conflicts. + +#### **10.2.1.19 Common message components** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 19 except as noted in this clause. + +Support for the SIPS URI is optional. If the support is provided, it shall be as specified in RFC 3261 section 19.1.1. + +#### **10.2.1.20 Header fields** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 20 except as noted in this clause. + +Below, the SIP headers defined in [RFC 3261] are listed, and the requirements for supporting them in the SCF are identified. + +##### **10.2.1.20.1 Accept** + +Support for the Accept header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.1. + +##### **10.2.1.20.2 Accept-Encoding** + +Support for the Accept-Encoding header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.2 except as noted below. + +The Accept-Encoding header may be used by the SCF. The "identity" encoding value shall be supported; other encodings may be supported. + +##### **10.2.1.20.3 Accept-Language** + +Support for the Accept-Language header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.3. + +##### **10.2.1.20.4 Alert-Info** + +Support for the Alert-Info header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.4. + +Note that there are security risks associated with acting on the Alert-Info header, as described in RFC 3261 section 20.4. + +##### **10.2.1.20.5 Allow** + +The Allow header shall be supported as specified in RFC 3261 section 20.5 except as noted below. + +The Allow header shall be present in the initial INVITE and the 2xx response to the initial INVITE. + +The header value shall list all supported methods, i.e., at a minimum, INVITE, ACK, CANCEL, BYE, UPDATE and PRACK. + +##### **10.2.1.20.6 Authentication-Info** + +Support for the Authentication-Info header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.6. + +##### **10.2.1.20.7 Authorization** + +Support for the Authorization header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.7. + +##### **10.2.1.20.8 Call-ID** + +The Call-ID header shall be supported as specified in RFC 3261 section 20.8 except as noted below. The Call-ID value shall be globally unique as described in RFC 3261 section 8.1.1.4, and it should use a suitably long random value (the value used as the 'tag' for the From header of the request might even be reused) instead of appending the IP address or hostname to the Call-ID as described in [RFC 3323] section 4.1 for protecting privacy. When privacy is requested by the session originator, the UA of the session originator should use a privacy protected Call-ID. In the case a B2BUA within the SCF is used in support of network interconnection, it may generate a privacy protected Call-ID. + +##### **10.2.1.20.9 Call-Info** + +Support for the Call-Info header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.9. + +Note that there are security risks associated with acting on the Call-Info header, as described in RFC 3261 section 20.9. + +##### **10.2.1.20.10 Contact** + +The Contact header shall be supported as specified in RFC 3261 section 20.10 except as noted below. + +The SCF shall set the SIP profile to populate the Contact header in an INVITE request, a reliable provisional response and in a 2xx response to an INVITE request, with a SIP URI. Support for any other type of URI is optional. + +When the user is requesting privacy, the Contact header should not contain any domain names; the IP address form should be used instead. It should be noted that, in systems with multiple network interfaces, use of the (single) IP address form can reduce the overall system reliability. If multiple interfaces exist and reliability is a concern, then refraining from use of the IP address form is considered to be a reasonable trade-off. + +The SCF shall set the SIP profile to populate the Contact header in a 3xx response to an INVITE request with a valid SIP URI or tel URI. If the new destination is a telephone number, it shall contain a tel URI with the number of the new destination, as described in clause 10.2.1.7.1. Support for any other type of URI is optional. + +##### **10.2.1.20.11 Content-Disposition** + +Support for the Content-Disposition header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.11 except as noted below. + +The Content-Disposition header may be used by the SCF. The value "session" shall be supported; other values may be supported. + +Note that the default value for message body type "application/sdp" is "session", whereas the default value for all other message body types (e.g., "message/sipfrag") is "render". If the default value is not desired, then the Content-Disposition header shall be included. + +##### **10.2.1.20.12 Content-Encoding** + +Support for the Content-Encoding header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.12 except as noted below. + +The Content-Encoding header may be used by the SCF. The "identity" encoding value shall be supported; other encodings may be supported. + +##### **10.2.1.20.13 Content-Language** + +Support for the Content-Language header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.13. + +##### **10.2.1.20.14 Content-Length** + +The Content-Length header shall be supported as specified in RFC 3261 section 20.14. + +##### **10.2.1.20.15 Content-Type** + +The Content-Type header shall be supported as specified in RFC 3261 section 20.15 except as noted below. + +The value "application/sdp" shall be supported; other values may be supported. + +##### **10.2.1.20.16 CSeq** + +The CSeq header shall be supported as specified in RFC 3261 section 20.16. + +##### **10.2.1.20.17 Date** + +Support for the Date header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.17. + +##### **10.2.1.20.18 Error-Info** + +Support for the Error-Info header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.18. + +Note that there are security risks associated with acting on the Error-Info header as described in RFC 3261 section 20.18. + +##### **10.2.1.20.19 Expires** + +Support for the Expires header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.19. + +##### **10.2.1.20.20 From** + +The From header shall be supported as specified in RFC 3261 section 20.20 except as noted below. + +In support of user privacy, the SCF restricts the allowable contents of the From header. + +When the session originator requests privacy, the SCF shall generate a From header according to the following rules: + +- The display-name may be "Anonymous". +- The addr-spec shall contain the identifier "anonymous" for userinfo. +- The addr-spec shall contain the non-identifying hostname "anonymous.invalid". + +##### **10.2.1.20.21 In-Reply-To** + +Support for the In-Reply-To header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.21. + +##### **10.2.1.20.22 Max-Forwards** + +The Max-Forwards header shall be supported as specified in RFC 3261 section 20.22 except as noted below. + +When a B2BUA within the SCF forwards a request, it shall use a Max-Forwards value equal to the incoming Max-Forwards value minus one. + +##### **10.2.1.20.23 Min-Expires** + +Support for the Min-Expires header is optional (because support for the REGISTER method is optional). If the support is provided, it shall be as specified in RFC 3261 section 20.23. + +##### **10.2.1.20.24 MIME-Version** + +Support for the MIME-Version header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.24 except as noted below. + +The version "1.0" value shall be supported; other values may be supported. + +##### **10.2.1.20.25 Organization** + +Support for the Organization header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.25. + +##### **10.2.1.20.26 Priority** + +Support for the Priority header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.26. + +Note that there are security ramifications for entities that act on this header. + +##### **10.2.1.20.27 Proxy-Authenticate** + +Support for the Proxy-Authenticate header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.27. + +##### **10.2.1.20.28 Proxy-Authorization** + +Support for the Proxy-Authorization header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.28. + +##### **10.2.1.20.29 Proxy-Require** + +The Proxy-Require header shall be supported as specified in RFC 3261 section 20.29 except as noted below. + +The option tag "privacy" shall be supported in accordance with [RFC 3323]; other option tags may be supported. + +##### **10.2.1.20.30 Record-Route** + +The Record-Route header shall be supported as specified in RFC 3261 section 20.30. + +##### **10.2.1.20.31 Reply-To** + +Support for the Reply-To header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.31. + +##### **10.2.1.20.32 Require** + +The Require header shall be supported as specified in RFC 3261 section 20.32 except as noted below. + +The option tags "100rel" and "timer" shall be supported in accordance with [RFC 3262] and [RFC 4028], respectively; other option tags may be supported. + +##### **10.2.1.20.33 Retry-After** + +Support for the Retry-After header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.33. + +##### **10.2.1.20.34 Route** + +The Route header shall be supported as specified in RFC 3261 section 20.34. + +##### **10.2.1.20.35 Server** + +Support for the Server header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.35. + +##### **10.2.1.20.36 Subject** + +Support for the Subject header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.36. + +##### **10.2.1.20.37 Supported** + +The Supported header shall be supported as specified in RFC 3261 section 20.37 except as noted below. + +The option tags "100rel" and "timer" shall be supported in accordance with [RFC 3262] and [RFC 4028], respectively; other option tags may be supported. + +##### **10.2.1.20.38 Timestamp** + +Support for the Timestamp header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.38 except as noted below. + +The SCF may send the Timestamp header in requests; if received, this header shall be processed as described in RFC 3261 section 20.38. + +##### **10.2.1.20.39 To** + +The To header shall be supported as specified in RFC 3261 section 20.39 except as noted below. + +In support of user privacy, the SCF may restrict the allowable contents of the To header. Typically, the To header indicates the dialled digits in a tel URI. This information is of end-to-end significance and might reveal information about the caller's location, e.g., enterprise, local, long-distance, or international. + +When the call originator requests privacy, the SCF may generate a To header according to the following rules: + +- The display-name shall be absent. +- If a global telephone number is used, then the userinfo part of the addr-spec shall contain a full E.164 number, including the country code. +- The host part of the addr-spec shall contain the non-identifying hostname "anonymous.invalid". + +If anonymity is not requested by the call originator and the user dialled a telephone number, then the To header should contain a tel URI with the dialled digits. + +##### **10.2.1.20.40 Unsupported** + +The Unsupported header shall be supported as specified in RFC 3261 section 20.40. + +##### **10.2.1.20.41 User-Agent** + +Support for the User-Agent header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.41. + +##### **10.2.1.20.42 Via** + +The Via header shall be supported as specified in RFC 3261 section 20.42. + +##### **10.2.1.20.43 Warning** + +Support for the Warning header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.43. + +##### **10.2.1.20.44 WWW-Authenticate** + +Support for the WWW-Authenticate header is optional. If the support is provided, it shall be as specified in RFC 3261 section 20.44. + +#### **10.2.1.21 Response codes** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 21. + +#### **10.2.1.22 Usage of HTTP authentication** + +Support for HTTP authentication is optional. If used, HTTP authentication shall be as specified in RFC 3261 section 22. + +#### **10.2.1.23 S/MIME** + +Support for S/MIME is optional. If used, S/MIME shall be as specified in RFC 3261 section 23. + +#### **10.2.1.24 Examples** + +RFC 3261 section 24 is informational. + +#### **10.2.1.25 Augmented BNF for the SIP protocol** + +The SCF shall set the SIP profile in accordance with RFC 3261 section 25. + +### **10.2.2 SIP profile for extensions to RFC 3261** + +This clause defines the extended methods, headers and response codes that are defined in the mandatorily supported RFCs except for RFC 3261, as listed in clause 10.1. If the support for the RFC is optional, then the support for the methods, headers and response codes defined in those RFCs is accordingly optional, and this clause does not describe those methods, headers and response codes individually. + +#### **10.2.2.1 Extended methods** + +The UPDATE and PRACK methods shall be supported. + +#### **10.2.2.2 Extended headers** + +##### **10.2.2.2.1 Min-SE** + +The Min-SE header shall be supported as specified in [RFC 4028]. + +##### **10.2.2.2.2 P-Asserted-Identity** + +The P-Asserted-Identity header shall be supported as specified in [RFC 3325]. + +##### **10.2.2.2.3 P-Preferred-Identity** + +Support for the P-Preferred-Identity header is not applicable because this header will not traverse the NNI. This header may be required for some SIP/SDP profiles, such as the UNI profile, but is not required for the NNI profile. + +##### **10.2.2.2.4 Privacy** + +The Privacy header shall be supported as specified in [RFC 3323] except as noted below. + +The application of the privacy option "id" shall be supported. Other privacy options may be supported based on a bilateral agreement. + +##### 10.2.2.2.5 RAck + +The RAck header shall be supported as specified in [RFC 3262]. + +##### 10.2.2.2.6 Reason + +Support for the reception of the Reason header is mandatory. However, support of sending the Reason header is optional. If the support is provided, it shall be as specified in [RFC 3326] except as noted below. + +The Reason header shall be supported in responses. + +##### 10.2.2.2.7 RSeq + +The RSeq header shall be supported as specified in [RFC 3262]. + +##### 10.2.2.2.8 Session-Expires + +The Session-Expires header shall be supported as specified in [RFC 4028]. + +#### 10.2.2.3 Extended response codes + +422 (session interval too small) shall be supported as specified in [RFC 4028]. + +### 10.2.3 Summary of SIP methods and headers + +Support for the following SIP methods and headers by the SCF is mandatory or optional, as specified in Tables 10-2, 10-3, 10-4 and 10-5. + +NOTE – For information about supporting the responses, see [RFC 3261]. + +**Table 10-2 – RFC 3261 methods** + +| Method | Send | Recv | Reference | +|----------|------|------|-----------------------| +| ACK | M | M | See clause 10.2.1.7.1 | +| BYE | M | M | See clause 10.2.1.7.1 | +| CANCEL | M | M | See clause 10.2.1.7.1 | +| INVITE | M | M | See clause 10.2.1.7.1 | +| OPTIONS | O | O | See clause 10.2.1.7.1 | +| REGISTER | O | O | See clause 10.2.1.7.1 | + +**Table 10-3 – Extended methods** + +| Method | Send | Recv | Reference | RFC | +|--------|------|------|-----------------------|----------| +| UPDATE | M | M | See clause 10.2.1.7.1 | RFC 3311 | +| PRACK | M | M | See clause 10.2.1.7.1 | RFC 3262 | + +**Table 10-4 – RFC 3261 headers** + +| Header | Send | Recv | Reference | +|-----------------|------|------|------------------------| +| Accept | O | O | See clause 10.2.1.20.1 | +| Accept-Encoding | O | O | See clause 10.2.1.20.2 | +| Accept-Language | O | O | See clause 10.2.1.20.3 | +| Alert-Info | O | O | See clause 10.2.1.20.4 | + +**Table 10-4 – RFC 3261 headers** + +| Header | Send | Recv | Reference | +|---------------------|-------------|-------------|-------------------------| +| Allow | M | M | See clause 10.2.1.20.5 | +| Authentication-Info | O | O | See clause 10.2.1.20.6 | +| Authorization | O | O | See clause 10.2.1.20.7 | +| Call-ID | M | M | See clause 10.2.1.20.8 | +| Call-Info | O | O | See clause 10.2.1.20.9 | +| Contact | M | M | See clause 10.2.1.20.10 | +| Content-Disposition | O | O | See clause 10.2.1.20.11 | +| Content-Encoding | O | O | See clause 10.2.1.20.12 | +| Content-Language | O | O | See clause 10.2.1.20.13 | +| Content-Length | M | M | See clause 10.2.1.20.14 | +| Content-Type | M | M | See clause 10.2.1.20.15 | +| CSeq | M | M | See clause 10.2.1.20.16 | +| Date | O | O | See clause 10.2.1.20.17 | +| Error-Info | O | O | See clause 10.2.1.20.18 | +| Expires | O | O | See clause 10.2.1.20.19 | +| From | M | M | See clause 10.2.1.20.20 | +| In-Reply-To | O | O | See clause 10.2.1.20.21 | +| Max-Forwards | M | M | See clause 10.2.1.20.22 | +| Min-Expires | O | O | See clause 10.2.1.20.23 | +| MIME-Version | O | O | See clause 10.2.1.20.24 | +| Organization | O | O | See clause 10.2.1.20.25 | +| Priority | O | O | See clause 10.2.1.20.26 | +| Proxy-Authenticate | O | O | See clause 10.2.1.20.27 | +| Proxy-Authorization | O | O | See clause 10.2.1.20.28 | +| Proxy-Require | M | M | See clause 10.2.1.20.29 | +| Record-Route | M | M | See clause 10.2.1.20.30 | +| Reply-To | O | O | See clause 10.2.1.20.31 | +| Require | M | M | See clause 10.2.1.20.32 | +| Retry-After | O | O | See clause 10.2.1.20.33 | +| Route | M | M | See clause 10.2.1.20.34 | +| Server | O | O | See clause 10.2.1.20.35 | +| Subject | O | O | See clause 10.2.1.20.36 | +| Supported | M | M | See clause 10.2.1.20.37 | +| Timestamp | O | O | See clause 10.2.1.20.38 | +| To | M | M | See clause 10.2.1.20.39 | +| Unsupported | M | M | See clause 10.2.1.20.40 | + +**Table 10-4 – RFC 3261 headers** + +| Header | Send | Recv | Reference | +|------------------|-------------|-------------|-------------------------| +| User-Agent | O | O | See clause 10.2.1.20.41 | +| Via | M | M | See clause 10.2.1.20.42 | +| Warning | O | O | See clause 10.2.1.20.43 | +| WWW-Authenticate | O | O | See clause 10.2.1.20.44 | + +**Table 10-5 – Extended headers** + +| Header | Send | Recv | Reference | RFC | +|----------------------|-------------|-------------|-----------------------|------------| +| Min-SE | M | M | See clause 10.2.2.2.1 | RFC 4028 | +| P-Asserted-Identity | M | M | See clause 10.2.2.2.2 | RFC 3325 | +| P-Preferred-Identity | N/A | N/A | See clause 10.2.2.2.3 | RFC 3325 | +| Privacy | M | M | See clause 10.2.2.2.4 | RFC 3323 | +| RAck | M | M | See clause 10.2.2.2.5 | RFC 3262 | +| Reason | O | M | See clause 10.2.2.2.6 | RFC 3326 | +| RSeq | M | M | See clause 10.2.2.2.7 | RFC 3262 | +| Session-Expires | M | M | See clause 10.2.2.2.8 | RFC 4028 | + +In the above tables, M, O, C and N/A have the following meanings: + +**Table 10-6 – Notations of the codes in Tables 10-2, 10-3, 10-4 and 10-5** + +| Code | Code name | Sending side | Receiving side | +|-------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M | Mandatory |

The capability shall be supported at NNI.

Supporting sending a SIP message or header at the NNI means that this message or header shall be sent over the NNI if received from the served network. It does not imply that network elements inside the served network or user equipment connected to this network shall support this message or header.

|

Supporting receiving a SIP message or header at the NNI means that, if received from the NNI, this message or header shall be forwarded to the served network. It does not imply that network elements inside the served network or user equipment connected to this network shall support this message or header.

Processing may not continue if required information is unavailable (suitable disconnection/release processing should be performed).

However, when a default value has been decided upon, processing is performed using the default value.

| + +**Table 10-6 – Notations of the codes in Tables 10-2, 10-3, 10-4 and 10-5** + +| Code | Code name | Sending side | Receiving side | +|------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| O | Optional | The capability may or may not be supported at NNI. It is an implementation choice. | Same as for the sending side with the following additions:
If possible, the processing expected by the sending side should be performed.
When the processing expected by the sending side cannot be performed, the received content should be ignored and processing should continue. | +| C | Conditional | The requirement on the capability ("M", "O") depends on the support of other optional or conditional items. is the identifier of the conditional expression. | Same as for the sending side. | +| N/A | Not applicable | It is impossible to use the capability. No answer in the support column is required. | Same as for the sending side. | + +Other SIP headers may be supported by the SCF. The SCF should transfer unsupported optional headers unchanged, if possible. + +## 10.3 SDP profile + +This clause defines an SDP profile for use in the SCF. It also defines the set of enhancements of and restrictions on a standard SDP implementation based on [RFC 2327] and [RFC 4566]. In Table 10-7, M, O and C have the same meanings as in Table 10-6. + +**Table 10-7 – SDP profile for usage** + +| Item | Send | Recv | +|-------------------------------------------------------|------|------| +| Session description | | | +| v = (protocol version) | M | M | +| o = (owner/creator and session identifier) | M | M | +| s = (session name) | M | M | +| i = (session information) | O | M | +| u = (URI of description) | O | O | +| e = (email address) | O | O | +| p = (phone number) | O | O | +| c = (connection information) | C1 | M | +| b = (bandwidth information) | O | M | +| Time description (one or more per description) | | | +| t = (time the session is active) | M | M | +| r = (zero or more repeat times) | O | O | + +**Table 10-7 – SDP profile for usage** + +| Item | Send | Recv | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------| +| Session level description (continue) | | | +| z = (time zone adjustments) | O | O | +| k = (encryption key) | O | O | +| a = (zero or more session attribute lines) | O | M | +| Media description (zero or more per description) | | | +| m = (media name and transport address) | C2 | M | +| i = (media title) | O | O | +| c = (connection information) | C1, C2 | M | +| b = (bandwidth information) | O | M | +| k = (encryption key) | O | O | +| a = (zero or more media attribute lines) | O | M | +| C1: At least one of the c lines in session and media descriptions shall be implemented.
C2: If media description is implemented, both m and c lines shall be implemented. | | | + +NOTE – Table 10-7 is described from an implementation point of view as described in Table 10-6, e.g., even if the c line in the media description is implemented, it does not mean that every media description in specific SIP/SDP message includes the c line. When the c line is included in the session description, the c line in the media description may not be included. + +# 11 Transport-level profile + +Media themselves are out of the scope of this Recommendation, but the following are supported because they are described in SIP/SDP messages. In Table 11-1, M and O have the same meanings as defined in clause 10.1. + +**Table 11-1 – Supported transport-level RFCs to be described in SIP/SDP messages** + +| RFC | Title | M/O | +|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| RFC 2833 [RFC 2833] | RTP payload for DTMF Digits, Telephony Tones and Telephony Signals | M (Note 1) | +| RFC 3267 [RFC 3267] | Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs | O | +| RFC 3389 [RFC 3389] | Real-time Transport Protocol (RTP) Payload for Comfort Noise | O (Note 2) | +| RFC 3550 [RFC 3550] | RTP: A Transport Protocol for Real-Time Applications | M | +| RFC 3551 [RFC 3551] | RTP Profile for Audio and Video Conferences with Minimal Control | M | +| T.38 [ITU-T T.38] | Procedures for real-time Group 3 facsimile communication over IP networks | O | +| RFC 4103 [RFC 4103] | RTP Payload for Text Conversion | O | +| NOTE 1 – When [ITU-T G.711] is used, [RFC 2833] is not mandatory. | | | +| NOTE 2 – For use with codecs such as G.711 [ITU-T G.711] and G.726 [ITU-T G.726] that do not themselves inherently support comfort noise. | | | + +# **12 Call control signalling transport** + +The NNI should use SIP transport over TCP unless, based on bilateral agreement, SIP transport over UDP or SCTP is used. + +NOTE – A service provider may have to support multiple types of SIP signalling transport depending on the peering relationships. + +# **13 IP protocol version** + +The following IP protocol versions are proposed: + +- 1) Support for IPv4 is mandatory. +- 2) Support for IPv6 is optional based on bilateral agreement. +- 3) When IPv4 and IPv6 networks interconnect, the IPv6 network shall perform addressing mapping. + +# **14 Security considerations** + +Signalling shall be secure and media may be secure based on a bilateral agreement. + +# Appendix I + +## Call/signalling flows + +(This appendix does not form an integral part of this Recommendation) + +This appendix gives example call flows for the following scenarios: + +- 1) PSTN—IP—(NNI)—IP—PSTN. +- 2) PSTN—IP—(NNI)—IP—IP. +- 3) IP—IP—NNI—IP—PSTN. +- 4) IP—IP—(NNI)—IP—IP. + +The example call flows for scenarios 1, 2 and 3 are based on the flows described in [ITU-T Q.1912.5]. The interworking between ISUP and SIP is shown at the diagrammatic level to illustrate interoperability. [ITU-T Q.1912.5] provides the details of interworking between ISUP (or BICC) and SIP, including the encapsulated ISUP and SIP header precedence rules. The example call flows for scenario 4 are based on [RFC 3261]. + +The following symbols are used in the figures below: + +| Symbol | Meaning | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| Symbol for tone generation: a circle with a sine wave inside. | Tone generation | +| Symbol for backward through connection: a circle with an X, where the left quadrant is filled black. | Through connection of the voice path in the backward direction | +| Symbol for bidirectional through connection: a circle with an X, where the left and right quadrants are filled black. | Through connection of the voice path in both directions | +| Symbol for forward through connection: a circle with an X, where the right quadrant is filled black. | Through connection of the voice path in the forward direction | +| Symbol for disconnection: a circle with an X, with no quadrants filled. | Disconnection of voice path through the node | +| Symbol for reservation: an empty circle. | Reservation of an incoming/outgoing call without through connection of the voice path | + +Q.3401(07)\_Symbol + +## A.1 PSTN—IP—(NNI)—IP—PSTN + +This clause illustrates typical interworking scenarios between ISUP and SIP-I. The example call flows assume a call originating and terminating in the PSTN and transiting two IP networks. + +#### A.1.1 Successful call setup (SIP preconditions not used) + +Figure A.1 shows a typical sequence of messages for successful call setup for an incoming ISUP call over SIP-I. The PSTN gateway (PSTN GW) performs the through-connection of the bearer path in both directions after the receipt of the SDP answer in the 180 Response. + +NOTE – Internal signalling messages within the PSTN gateway and IBC-FE and IBG-FEs are not shown. + +![Sequence diagram of successful call setup between two PSTN networks via an IP NNI. The diagram shows the flow of SIP-I messages (INVITE, 100 Trying, 180 Ringing, 200 OK, ACK) and ISUP messages (IAM, ACM, ANM) through various network elements including PSTN GWs, BGC-FEs, MGC-FEs, TMG-FEs, SG-FEs, IBC-FEs, and IBG-FEs. A large green arrow at the bottom indicates the RTP bearer path.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +The diagram illustrates the message sequence for a successful call setup. It starts with an incoming ISUP IAM message at the left PSTN GW, which is converted to a SIP INVITE (SDP, IAM) and sent to the first IBC-FE. This is followed by a 100 Trying response. The INVITE is then forwarded through an IP NNI to the second IBC-FE, which generates its own 100 Trying (Note). The INVITE is then sent to the right PSTN GW, which generates an ACM and a 180 Ringing (SDP, ACM) response. The 180 Ringing is forwarded back through the IBC-FEs, and a 200 OK (INVITE) (SDP, ANM) is generated by the right IBC-FE. The 200 OK is forwarded back through the IBC-FEs, and an ACK is generated by the left IBC-FE. The final ACK is sent to the right PSTN GW, which generates an ANM message. The RTP bearer path is shown as a large green arrow at the bottom, spanning from the left PSTN GW to the right PSTN GW. + +Sequence diagram of successful call setup between two PSTN networks via an IP NNI. The diagram shows the flow of SIP-I messages (INVITE, 100 Trying, 180 Ringing, 200 OK, ACK) and ISUP messages (IAM, ACM, ANM) through various network elements including PSTN GWs, BGC-FEs, MGC-FEs, TMG-FEs, SG-FEs, IBC-FEs, and IBG-FEs. A large green arrow at the bottom indicates the RTP bearer path. + +NOTE – The generation of the 100 Trying response is necessary if the PSTN gateway knows that it will not generate a provisional or final response. + +Q.3401(07)\_FA-1 + +Figure A.1 – Successful Call Setup + +#### A.1.2 Normal call release + +Figure A.2 shows a normal call release interworking procedure without tone provision. A REL message is mapped and encapsulated into a BYE request to preserve ISUP signalling transparency. + +NOTE 1 – Internal signalling messages within the PSTN gateway and IBC-FE and IBG-FEs are not shown. + +NOTE 2 – This procedure is applicable in those cases where in-band tones/announcements are not provided, e.g., 64 kbit/s unrestricted bearer service. + +![Sequence diagram of normal call release without tone provision](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +The diagram illustrates the sequence of messages for a normal call release without tone provision. It shows the interaction between two PSTN Gateways (GW) and several Front-End (FE) units. The PSTN GW on the left contains BGC-FE, MGC-FE, TMG-FE, and SG-FE. The PSTN GW on the right contains BGC-FE, MGC-FE, SG-FE, and TMG-FE. Between them are IBC-FE and IBG-FE units connected via an IP NNI. The sequence starts with a REL message from the left PSTN GW, which is mapped to a RLC message. This is followed by a BYE (REL) message from the left PSTN GW to the first IBC-FE. The IBC-FE then forwards the BYE (REL) message to the next IBC-FE. The second IBC-FE forwards it to the third IBC-FE. The third IBC-FE then sends a 200 OK (BYE) (RLC) message back to the second IBC-FE. The second IBC-FE forwards this back to the first IBC-FE. The first IBC-FE then sends a 200 OK (BYE) (RLC) message back to the left PSTN GW. Finally, the left PSTN GW sends a RLC message back to the external entity, completing the release. The right PSTN GW also sends a REL message, which is mapped to a RLC message, and receives a 200 OK (BYE) (RLC) message from the third IBC-FE. + +Q.3401(07)\_FA-2 + +Sequence diagram of normal call release without tone provision + +Figure A.2 – Normal call release without tone provision + +## A.2 PSTN—IP—(NNI)—IP—IP + +This clause illustrates typical interworking scenarios for successful call setup and release between ISUP and SIP. The call flows assume a call originating in the PSTN and terminating in an IP network. + +#### A.2.1 Successful call setup (SIP preconditions not used) + +Figure A.3 shows a typical sequence of messages for successful call setup at a gateway for an incoming ISUP call and an outgoing SIP call, without SIP preconditions. In this example, the PSTN gateway sends the INVITE message upon receipt of an IAM containing the indication "continuity check not required". Upon receipt of the 200 OK (INVITE), the PSTN gateway sends the ANM. + +NOTE – Internal signalling messages within the PSTN gateway and IBC-FE and IBG-FEs are not shown. + +![Sequence diagram showing successful call setup from ISUP to SIP. The diagram illustrates the message flow between a PSTN Gateway (PSTN GW), various Front-End (FE) components (BGC-FE, MGC-FE, TMG-FE, SG-FE, IBG-FE, IBC-FE), and a SIP User Agent (SIP UA). The process starts with an incoming ISUP IAM message at the PSTN GW, which triggers an INVITE message through a series of FEs to the SIP UA. Responses (100 Trying, 180 Ringing, 200 OK) are returned through the FEs back to the PSTN GW, which then sends ACM and ANM messages to the TDM trunk. A green arrow at the bottom indicates the RTP stream direction.](b2f5606b9c7184c1c6070a290080a3e3_img.jpg) + +The diagram shows the following message sequence: + +- ISUP IAM (Note)** arrives at the PSTN GW from the TDM trunk. +- The PSTN GW sends an **INVITE** message to the first IBC-FE. +- The first IBC-FE sends a **100 Trying** response back to the PSTN GW. +- The first IBC-FE forwards the **INVITE** to the second IBC-FE. +- The second IBC-FE sends a **100 Trying** response back to the first IBC-FE. +- The second IBC-FE forwards the **INVITE** to the SIP UA. +- The SIP UA sends a **100 Trying** response back to the second IBC-FE. +- The second IBC-FE sends a **180 Ringing** response back to the first IBC-FE. +- The first IBC-FE sends a **180 Ringing** response back to the PSTN GW. +- The PSTN GW sends an **ACM** (Address Complete Message) to the TDM trunk. +- The SIP UA sends a **200 OK (INVITE)** response back to the second IBC-FE. +- The second IBC-FE sends a **200 OK (INVITE)** response back to the first IBC-FE. +- The first IBC-FE sends a **200 OK (INVITE)** response back to the PSTN GW. +- The PSTN GW sends an **ANM** (Answer Message) to the TDM trunk. +- The PSTN GW sends an **ACK** message to the first IBC-FE. +- The first IBC-FE sends an **ACK** message to the second IBC-FE. +- The second IBC-FE sends an **ACK** message to the SIP UA. +- A green arrow labeled **RTP** indicates the media stream direction from the PSTN GW to the SIP UA. + +Sequence diagram showing successful call setup from ISUP to SIP. The diagram illustrates the message flow between a PSTN Gateway (PSTN GW), various Front-End (FE) components (BGC-FE, MGC-FE, TMG-FE, SG-FE, IBG-FE, IBC-FE), and a SIP User Agent (SIP UA). The process starts with an incoming ISUP IAM message at the PSTN GW, which triggers an INVITE message through a series of FEs to the SIP UA. Responses (100 Trying, 180 Ringing, 200 OK) are returned through the FEs back to the PSTN GW, which then sends ACM and ANM messages to the TDM trunk. A green arrow at the bottom indicates the RTP stream direction. + +Q.3401(07)\_FA-3 + +NOTE – The IAM contains the indication "continuity check not required". + +**Figure A.3 – Successful call setup from ISUP to SIP** + +#### A.2.2 Normal call release + +Figure A.4 shows a normal call release procedure initiated from the ISUP side of the call. This call flow assumes that no resource reservation teardown signalling is required on the SIP side of the call. + +NOTE – Internal signalling messages within the PSTN gateway and IBC-FE and IBG-FEs are not shown. + +![Sequence diagram of normal call release from ISUP to SIP](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates the sequence of messages for a normal call release initiated from the ISUP side. It features three main entities: a PSTN GW (containing BGC-FE, MGC-FE, TMG-FE, and SG-FE), a series of intermediate nodes (IBG-FE, IBC-FE, IP NNI, IBC-FE, IBG-FE), and a SIP UA. The process begins with a REL message from the PSTN GW, followed by a RLC message (indicated by a circle with an X). The PSTN GW then sends a BYE message to the first IBC-FE. This message is forwarded through the IP NNI to the next IBC-FE, then to the IBG-FE, and finally to the SIP UA. The SIP UA responds with a 200 OK (BYE) message, which is then forwarded back through the IBG-FE, IBC-FE, IP NNI, IBC-FE, and IBG-FE, and finally back to the PSTN GW, which sends a 200 OK (BYE) message back to the initiator. + +``` +sequenceDiagram + participant PSTN_GW as PSTN GW (BGC-FE, MGC-FE, TMG-FE, SG-FE) + participant IBG_FE1 as IBG-FE + participant IBC_FE1 as IBC-FE + participant IP_NNI as IP NNI + participant IBC_FE2 as IBC-FE + participant IBG_FE2 as IBG-FE + participant SIP_UA as SIP UA + + Note left of PSTN_GW: REL + PSTN_GW->>PSTN_GW: RLC (X) + PSTN_GW->>IBC_FE1: BYE + IBC_FE1->>IP_NNI: BYE + IP_NNI->>IBC_FE2: BYE + IBC_FE2->>IBG_FE2: BYE + IBG_FE2->>SIP_UA: BYE + SIP_UA->>IBG_FE2: 200 OK (BYE) + IBG_FE2->>IBC_FE2: 200 OK (BYE) + IBC_FE2->>IP_NNI: 200 OK (BYE) + IP_NNI->>IBC_FE1: 200 OK (BYE) + IBC_FE1->>IBG_FE1: 200 OK (BYE) + IBG_FE1->>PSTN_GW: 200 OK (BYE) +``` + +Sequence diagram of normal call release from ISUP to SIP + +Figure A.4 – Normal call release from ISUP to SIP + +### A.3 IP—IP—(NNI)—IP—PSTN + +This clause illustrates typical interworking scenarios for successful call setup and release between SIP and ISUP. The call flows assume a call originating in an IP network and terminating in the PSTN. + +#### A.3.1 Successful call setup (SIP preconditions not used) + +Figure A.5 shows a typical sequence of messages for successful call setup at a gateway for an incoming SIP call and an outgoing ISUP call. Since SIP preconditions are not in use, the PSTN gateway immediately sends out the IAM. Upon receipt of the ANM, the PSTN gateway sends the 200 OK (INVITE). + +NOTE – Internal signalling messages within the PSTN gateway and IBC-FE and IBG-FEs are not shown. + +![Sequence diagram of successful call setup from SIP to ISUP](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +The diagram illustrates the message sequence for a successful call setup from a SIP UA to a PSTN gateway. The components involved are: SIP UA, IBG-FE, IBC-FE, IP NNI, PSTN GW (containing BGC-FE, MGC-FE, SG-FE, TMG-FE), and TDM trunk. The sequence of messages is as follows: + +- The SIP UA sends an INVITE to the first IBG-FE. +- The first IBG-FE responds with 100 Trying. +- The first IBG-FE forwards the INVITE to the first IBC-FE. +- The first IBC-FE responds with 100 Trying. +- The first IBC-FE forwards the INVITE to the second IBG-FE. +- The second IBG-FE responds with 100 Trying. +- The second IBG-FE forwards the INVITE to the PSTN GW. +- The PSTN GW responds with IAM. +- The PSTN GW receives an ACM from the TDM trunk. +- The PSTN GW receives an ANM from the TDM trunk. +- The PSTN GW sends a 200 OK (INVITE) back to the second IBG-FE. +- The second IBG-FE forwards the 200 OK (INVITE) to the first IBC-FE. +- The first IBC-FE forwards the 200 OK (INVITE) to the first IBG-FE. +- The first IBG-FE sends a 200 OK (INVITE) to the SIP UA. +- The SIP UA sends an ACK to the first IBG-FE. +- The first IBG-FE forwards the ACK to the first IBC-FE. +- The first IBC-FE forwards the ACK to the second IBG-FE. +- The second IBG-FE forwards the ACK to the PSTN GW. +- A green double-headed arrow labeled RTP indicates the media path between the SIP UA and the PSTN GW. + +Q.3401(07)\_FA-5 + +Sequence diagram of successful call setup from SIP to ISUP + +Figure A.5 – Successful call setup from SIP to ISUP + +#### A.3.2 Normal call release + +Figure A.6 shows a sequence of messages for the normal call release procedure initiated from the SIP side of the call. This call flow assumes that no resource reservation teardown signalling is required on the SIP side. + +NOTE – Internal signalling messages within the PSTN gateway and IBC-FE and IBG-FEs are not shown. + +![Sequence diagram for normal call release from SIP to ISUP. The diagram shows a SIP UA sending a BYE message to an IBC-FE, which then passes it through an IP NNI to another IBC-FE, which then passes it to a PSTN GW. The PSTN GW sends a REL message to a TMG-FE, which then sends an RLC message. The response 200 OK (BYE) is passed back through the chain.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant SIP_UA as SIP UA + subgraph PSTN_GW [PSTN GW] + BGC-FE + MGC-FE + SG-FE + TMG-FE + end + Note right of PSTN_GW: RLC + SIP_UA->>IBC_FE1[IBC-FE]: BYE + IBC_FE1->>IBC_FE2[IBC-FE]: BYE + IBC_FE2->>PSTN_GW: BYE + PSTN_GW->>TMG-FE: REL + TMG-FE->>PSTN_GW: RLC + PSTN_GW->>IBC_FE2: 200 OK (BYE) + IBC_FE2->>IBC_FE1: 200 OK (BYE) + IBC_FE1->>SIP_UA: 200 OK (BYE) + +``` + +Q.3401(07)\_FA-6 + +Sequence diagram for normal call release from SIP to ISUP. The diagram shows a SIP UA sending a BYE message to an IBC-FE, which then passes it through an IP NNI to another IBC-FE, which then passes it to a PSTN GW. The PSTN GW sends a REL message to a TMG-FE, which then sends an RLC message. The response 200 OK (BYE) is passed back through the chain. + +Figure A.6 – Normal call release from SIP to ISUP + +### A.4 IP—IP—(NNI)—IP—IP + +This clause illustrates typical scenarios for successful call setup and release at the SIP IP-IP NNI. The call flows assume a call originating and terminating in IP networks without transiting a non-IP network. + +#### A.4.1 Successful call setup (SIP preconditions not used) + +Figure A.7 shows a typical sequence of messages for successful call setup for a basic call at the SIP NNI. No SIP preconditions or messages to support additional SIP services are shown. + +NOTE – Internal signalling messages within the IBC-FE and IBG-FEs are not shown. + +![Sequence diagram for successful call setup at IP-IP SIP NNI. The diagram shows an IBC-FE sending an INVITE message to another IBC-FE across an IP NNI. The response includes 100 Trying, 180 Ringing, 200 OK (INVITE), and ACK. A large green arrow labeled RTP indicates the media flow between the two IBC-FEs.](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +``` + +sequenceDiagram + participant IBC_FE1 as IBC-FE + participant IBC_FE2 as IBC-FE + Note left of IBC_FE1: IP NNI + IBC_FE1->>IBC_FE2: INVITE + IBC_FE2->>IBC_FE1: 100 Trying + IBC_FE2->>IBC_FE1: 180 Ringing + IBC_FE2->>IBC_FE1: 200 OK (INVITE) + IBC_FE1->>IBC_FE2: ACK + Note right of IBC_FE2: RTP + +``` + +Q.3401(07)\_FA-7 + +Sequence diagram for successful call setup at IP-IP SIP NNI. The diagram shows an IBC-FE sending an INVITE message to another IBC-FE across an IP NNI. The response includes 100 Trying, 180 Ringing, 200 OK (INVITE), and ACK. A large green arrow labeled RTP indicates the media flow between the two IBC-FEs. + +Figure A.7 – Successful call setup at IP-IP SIP NNI + +#### A.4.2 Normal call release + +Figure A.8 shows the sequence of messages for normal call release at the SIP NNI. + +NOTE – Internal signalling messages within the IBC-FE and IBG-FEs are not shown. + +![Sequence diagram for normal call release at the SIP NNI. It shows two entities, each containing an IBG-FE and an IBC-FE. The IBC-FEs are connected via an IP NNI. The sequence of messages is: BYE from the left IBC-FE to the right IBC-FE, and 200 OK (BYE) from the right IBC-FE back to the left IBC-FE.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` +sequenceDiagram + participant IBG-FE_L [IBG-FE] + participant IBC-FE_L [IBC-FE] + participant IBC-FE_R [IBC-FE] + participant IBG-FE_R [IBG-FE] + + Note left of IBG-FE_L: (Internal signalling not shown) + Note right of IBG-FE_R: (Internal signalling not shown) + + IBC-FE_L->>IBC-FE_R: BYE + IBC-FE_R-->>IBC-FE_L: 200 OK (BYE) +``` + +The diagram illustrates the message sequence for a normal call release at the SIP NNI. It features two entities, each enclosed in a dashed box. The left entity contains an IBG-FE and an IBC-FE. The right entity also contains an IBG-FE and an IBC-FE. The IBC-FEs are connected via an IP NNI. The sequence of messages is as follows: a BYE message is sent from the left IBC-FE to the right IBC-FE, and a 200 OK (BYE) message is sent from the right IBC-FE back to the left IBC-FE. The diagram is labeled Q.3401(07)\_FA-8. + +Sequence diagram for normal call release at the SIP NNI. It shows two entities, each containing an IBG-FE and an IBC-FE. The IBC-FEs are connected via an IP NNI. The sequence of messages is: BYE from the left IBC-FE to the right IBC-FE, and 200 OK (BYE) from the right IBC-FE back to the left IBC-FE. + +**Figure A.8 – Normal call release at IP-IP SIP NNI** + +# Bibliography + +- [b-ETSI ES 282 007] ETSI ES 282 007 V1.1.1 (2006), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture.* +- [b-ETSI TS 182 006] ETSI TS 182 006 V1.1.1 (2006), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Stage 2 description.* +- [b-ETSI ES 283 003] ETSI ES 283 003 V1.8.0 (2007), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3.* +- [b-3GPP TS 24.229] 3GPP TS 24.229 (2007), *Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3.* +- [b-ATIS-PP-1000009] ATIS-PP-1000009 (2006), *IP Network-to-Network Interface (NNI) Standard for VoIP.* + + + +# 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.3405-201810-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..40b75296fb679181be5ca1561090e24e88ab7e45 --- /dev/null +++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/raw.md @@ -0,0 +1,747 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3405** + +(10/2018) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for the NGN – +Service and session control protocols + +--- + +**IPv6 protocol procedures for broadband +services** + +Recommendation ITU-T Q.3405 + +# 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 | +| 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.3405 + +# IPv6 protocol procedures for broadband services + +## Summary + +Recommendation ITU-T Q.3405 identifies the Internet Protocol version 6 (IPv6) procedures which support broadband services with IPv6 transition. The protocol procedures are specified according to three basic IPv6 transition modes: dual stack, tunnelling and translation. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3405 | 2018-10-14 | 11 | 11.1002/1000/13696 | + +## Keywords + +DS-Lite, IPoE, IPv6, NAT, PPPoE. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Basic IPv6 transition modes to support broadband services ..... | 2 | +| 6.1 Dual stack + NAT mode with IPoE access ..... | 2 | +| 6.2 Dual stack + NAT mode with PPPoE access ..... | 3 | +| 6.3 DS-Lite with PPPoE access..... | 4 | +| 7 Protocol procedures ..... | 4 | +| 7.1 Procedures for dual stack + NAT with IPoE access..... | 4 | +| 7.2 Procedures for dual stack + NAT with PPPoE access..... | 8 | + + + +## Recommendation ITU-T Q.3405 + +## IPv6 protocol procedures for broadband services + +# 1 Scope + +This Recommendation identifies the Internet Protocol version 6 (IPv6) procedures which support broadband services with IPv6 transition. The protocol procedures are specified according to three basic IPv6 transition modes: dual stack, tunnelling and translation. + +# 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. + +[IETF RFC 3315] IETF RFC 3315 (2003), *Dynamic Host Configuration Protocol for IPv6 (DHCPv6)*. + +[IETF RFC 3633] IETF RFC 3633 (2003), *IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6*. + +[IETF RFC 4291] IETF RFC 4291 (2006), *IP Version 6 Addressing Architecture*. + +[IETF RFC 4861] IETF RFC 4861 (2007), *Neighbor Discovery for IP version 6 (IPv6)*. + +[IETF RFC 6333] IETF RFC 6333 (2011), *Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion*. + +[IETF RFC 6598] IETF RFC 6598 (2012), *IANA-Reserved IPv4 Prefix for Shared Address Space*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----------|-------------------------------------------------------------------| +| BRAS | Broadband Remote Access Server | +| CPE | Customer Premise Equipment | +| DHCP | Dynamic Host Configuration Protocol | +| DHCPv6 | Dynamic Host Configuration Protocol version 6 | +| DHCPv6-PD | Dynamic Host Configuration Protocol version 6 – Prefix Delegation | + +| | | +|---------|---------------------------------------| +| DNS | Domain Name Server | +| DS-Lite | Dual Stack-Lite | +| IP | Internet Protocol | +| IPoE | Internet Protocol over Ethernet | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| MAC | Media Access Control | +| NAT | Network Address Translation | +| NDP | Neighbour Discovery Protocol | +| PPPoE | Point-to-Point Protocol over Ethernet | +| WAN | Wide Area Network | + +# 5 Conventions + +In this Recommendation: + +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. + +# 6 Basic IPv6 transition modes to support broadband services + +## 6.1 Dual stack + NAT mode with IPoE access + +Figure 6-1 depicts the dual stack + network address translation (NAT) mode with Internet Protocol over Ethernet (IPoE) access to support end-to-end broadband services. Depending on the working mode of customer premise equipment (CPE), i.e., either route mode or bridge mode, the transition is divided into two further sub-modes. + +![Diagram of Dual stack + NAT mode with IPoE access showing network architecture and traffic flows for route and bridge modes.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +The diagram illustrates the network architecture for Dual stack + NAT mode with IPoE access. It is divided into five vertical zones: Terminal, Access, Metro, Core, and Servers. + +- Terminal:** Contains icons for TV, PC, and Phone connected to a CPE device. +- Access:** Contains an "Access node" icon. +- Metro:** Contains two "Edge node" icons within a cloud, labeled "IPv4/IPv6 dual stack". +- Core:** Contains two "Core node" icons within a cloud. +- Servers:** Contains two globe icons labeled "IPv4" and "IPv6". + +Below the zones, the diagram shows two traffic flow scenarios: + +- CPE route mode:** + - The NAT44 function is located at the CPE. + - IPv4 traffic from the CPE goes through NAT44 to a "Public IPv4" path. + - IPv6 traffic from the CPE goes through a "DS+NAT44+IPoE" path. +- CPE bridge mode:** + - The NAT44 function is located at the Edge node in the Metro zone. + - IPv4 traffic from the CPE goes through the Edge node's NAT44 to a "Public IPv4" path. + - IPv6 traffic from the CPE goes through a "DS+NAT44+IPoE" path. + +Diagram of Dual stack + NAT mode with IPoE access showing network architecture and traffic flows for route and bridge modes. + +Q.3405(18)\_F6-1 + +Figure 6-1 – Dual stack +NAT mode with IPoE access to support broadband services + +When the CPE works in route mode, user Internet Protocol version 4 (IPv4) traffic passes through two devices which perform NAT functions. The first NAT function is executed in the CPE to perform translation from the IPv4 address of the user private network to an IPv4 address of the carrier private network (see [IETF RFC 6598]). The second NAT function is executed in the carrier network to perform translation from the IPv4 address of the carrier private network to an IPv4 address in the public network. + +When the CPE works in bridge mode, user IPv4 traffic passes through only one device performing a NAT function. This NAT function is executed in the carrier network to perform translation from the IPv4 address of the user private network to an IPv4 address in the public network. + +For both sub-modes, the procedures for IPv6 traffic end-to-end transmission are described in clause 7.1. + +## 6.2 Dual stack + NAT mode with PPPoE access + +Figure 6-2 depicts the dual stack + NAT mode with point-to-point protocol over Ethernet (PPPoE) access to support end-to-end broadband services; both IPv4 and IPv6 access are required to support a PPPoE session. Depending on the working mode of the CPE, i.e., either route mode or bridge mode, the transition is divided into two further sub-modes. + +![Figure 6-2: Dual stack + NAT mode with PPPoE access to support broadband services. The diagram shows network architecture and traffic paths for IPv4 and IPv6.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +The diagram illustrates the network architecture and traffic paths for IPv4 and IPv6 in dual stack + NAT mode with PPPoE access. It is divided into three horizontal sections: Network Architecture, Traffic Path (CPE route mode), and Traffic Path (CPE bridge mode). + +- Network Architecture:** + - Terminal:** Contains icons for TV, PC, and Phone connected to a CPE. + - Access:** Contains an icon for an Access node. + - Metro:** Contains two Edge nodes, each labeled "IPv4/IPv6 dual stack". + - Core:** Contains two Core nodes. + - Servers:** Contains icons for IPv4 and IPv6 servers. +- Traffic Path (CPE route mode):** + - Shows two horizontal pipes representing traffic paths. + - The top pipe (IPv4) starts at the CPE, passes through a NAT44 function, then a PPPoE tunnel, then another NAT44 function in the Metro, and finally becomes "Public IPv4" in the Core. + - The bottom pipe (IPv6) starts at the CPE and passes through the Metro and Core without NAT functions, labeled as "DS+NAT44+PPPoE". +- Traffic Path (CPE bridge mode):** + - Shows two horizontal pipes representing traffic paths. + - The top pipe (IPv4) starts at the CPE, passes through a PPPoE tunnel, then a NAT44 function in the Metro, and finally becomes "Public IPv4" in the Core. + - The bottom pipe (IPv6) starts at the CPE and passes through the Metro and Core without NAT functions, labeled as "DS+NAT44+PPPoE". + +Figure 6-2: Dual stack + NAT mode with PPPoE access to support broadband services. The diagram shows network architecture and traffic paths for IPv4 and IPv6. + +Q.3405(18)\_F6-2 + +**Figure 6-2 – Dual stack +NAT mode with PPPoE access to support broadband services** + +When the CPE works in route mode, a PPPoE session, which is required to support IPv4 and IPv6 protocols, is initiated in the CPE and terminated in a carrier edge device, such as a broadband remote access server (BRAS). User IPv4 traffic passes through two devices performing NAT functions. The first NAT function is executed in the CPE to perform translation from the IPv4 address of the user private network to an IPv4 address of the carrier private network (see [IETF RFC 6598]). The second NAT function is executed in the carrier network to perform translation from the IPv4 address of the carrier private network to an IPv4 address in the public network. + +When the CPE works in bridge mode, a PPPoE session, which is required to support IPv4 and IPv6 protocols, is initiated in the user's terminal and terminated in a carrier edge device, such as a BRAS. User IPv4 traffic passes through only one device performing a NAT function. User traffic is initiated in user equipment and terminated in a carrier edge device, such as BRAS. The NAT function is + +executed on the carrier network side to perform translation from the IPv4 address of the user private network to an IPv4 address in the public network. + +For both sub-modes, IPv6 traffic is encapsulated into a PPPoE session in the CPE or in the user's terminal, and is decapsulated in a carrier edge device (e.g., BRAS). The procedures for IPv6 traffic end-to-end transmission are described in clause 7.2. + +## 6.3 DS-Lite with PPPoE access + +Figure 6-3 depicts dual stack-lite (DS-Lite) [IETF RFC 6333] mode with PPPoE access to support end-to-end broadband services. In this mode, the CPE is generally required to be configured to work in route mode. + +![Figure 6-3: DS-Lite with PPPoE access to support broadband services. The diagram shows a network architecture with five main components: Terminal, Access, Metro, Core, and Servers. The Terminal section includes a TV, PC, and Phone connected to a CPE. The Access section contains an Access node. The Metro section includes two BNGs (IPv6 only) and two Edge nodes (IPv4/IPv6 dual stack). The Core section contains two Core nodes. The Servers section includes IPv4 and IPv6 servers. Below the network diagram, a traffic flow diagram shows two modes: 'CPE route mode' where Private IPv4 traffic is encapsulated in a 4in6 tunnel over a Public IPv4 path, and 'DS-Lite+NAT44+PPPoE' where IPv6 traffic is encapsulated in a PPPoE session. A NAT44 device is shown between the 4in6 tunnel and the Public IPv4 path.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +Figure 6-3: DS-Lite with PPPoE access to support broadband services. The diagram shows a network architecture with five main components: Terminal, Access, Metro, Core, and Servers. The Terminal section includes a TV, PC, and Phone connected to a CPE. The Access section contains an Access node. The Metro section includes two BNGs (IPv6 only) and two Edge nodes (IPv4/IPv6 dual stack). The Core section contains two Core nodes. The Servers section includes IPv4 and IPv6 servers. Below the network diagram, a traffic flow diagram shows two modes: 'CPE route mode' where Private IPv4 traffic is encapsulated in a 4in6 tunnel over a Public IPv4 path, and 'DS-Lite+NAT44+PPPoE' where IPv6 traffic is encapsulated in a PPPoE session. A NAT44 device is shown between the 4in6 tunnel and the Public IPv4 path. + +Q.3405(18)\_F6-3 + +Figure 6-3 – DS-Lite with PPPoE access to support broadband services + +A DS-Lite tunnel established between the CPE and a carrier edge device (e.g., BRAS), and a PPPoE session supporting IPv6 is required. The user IPv4 traffic initiated from the CPE is encapsulated into a DS-Lite tunnel, and then transmitted to the carrier edge device in a PPPoE session. The carrier edge device (e.g., BRAS) terminates the PPPoE session and decapsulates the IPv4 traffic from the DS-Lite tunnel, and then performs translation from the IPv4 address of the user private network to an IPv4 address in the public network. User IPv6 traffic is also encapsulated into a PPPoE session in the CPE and decapsulated in the carrier edge device (e.g., BRAS). + +# 7 Protocol procedures + +## 7.1 Procedures for dual stack + NAT with IPoE access + +In the mode "dual stack + NAT with IPoE access", user IPv4 packets require one or two NAT operations to be performed when transmitted, but user IPv6 packet do not require any NAT operations. In this mode, the CPE and/or the edge node must maintain a NAT44 mapping table and implement the IP address mapping from private IPv4 addresses to public IPv4 addresses. + +![Sequence diagram showing the procedure for dual stack + NAT with IPoE access with CPE working in route mode. The diagram illustrates the flow of DHCP and IPv4 packets between a Terminal, CPE, Edge node, Core node, and Server. The CPE performs two levels of NAT mapping: first from Terminal private IP to Carrier private IP, and then from Carrier private IP to Public IP.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: Create NAT44 table: +Carrier private IP address <-> +Public IP address + Note left of Terminal: Create NAT44 table: +Terminal private IP address <-> +Carrier private IP address + + CPE->>Edge node: 1. DHCP request + Edge node-->>CPE: 2. DHCP response +IP address, DNS assignment + Terminal->>CPE: 3. DHCP request + CPE-->>Terminal: 4. DHCP response +IP address, DNS assignment + Terminal->>CPE: 5. IPv4 packet + CPE->>Edge node: 6. IPv4 packet + Edge node->>Core node: 7. IPv4 packet + Core node->>Server: 8. IPv4 packet + Server-->>Core node: 9. IPv4 packet + Core node-->>Edge node: 10. IPv4 packet + Edge node-->>CPE: 11. IPv4 packet + Note left of Terminal: Lookup NAT44 table: +Terminal private IP address <-> +Carrier private IP address + CPE->>Terminal: 12. IPv4 packet + +``` + +Sequence diagram showing the procedure for dual stack + NAT with IPoE access with CPE working in route mode. The diagram illustrates the flow of DHCP and IPv4 packets between a Terminal, CPE, Edge node, Core node, and Server. The CPE performs two levels of NAT mapping: first from Terminal private IP to Carrier private IP, and then from Carrier private IP to Public IP. + +Q.3405(18)\_F7-1 + +**Figure 7-1 – Procedure for dual stack + NAT with IPoE access with CPE working in route mode** + +Figure 7-1 depicts the procedure for user IPv4 packet transmission with the CPE working in route mode with the mode of "dual stack + NAT with IPoE access". In this mode, the CPE obtains IPv4 address and domain name server (DNS)-related information from the carrier edge device through the dynamic host configuration protocol (DHCP). The user then also obtains their IPv4 address and DNS-related information from the CPE through DHCP. When user traffic is transmitted end-to-end, it needs to go through two levels of NAT mapping. The first level of NAT mapping is executed in the CPE device and maps from the user private IPv4 address to the carrier private IPv4 address; the second level of NAT mapping is executed in the carrier edge device (e.g., BRAS) and maps from the carrier private IPv4 address to the public IPv4 address. In this case, both the CPE and the carrier edge device must maintain a NAT mapping table. + +![Sequence diagram illustrating the procedure for dual stack + NAT with IPoE access with CPE working in bridge mode. The diagram shows the interaction between a Terminal, CPE, Edge node, Core node, and Server. The process starts with a DHCP request from the Terminal to the Edge node, followed by a DHCP response from the Edge node to the Terminal. The CPE then creates a NAT44 table entry. Subsequent IPv4 packets are transmitted from the Terminal to the Edge node, then to the Core node, then to the Server, and back through the Core node and Edge node to the Terminal. The CPE performs NAT mapping at the Edge node.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: Create NAT44 table: +Terminal private IP address <-> Public IP address + + Terminal->>Edge node: 1. DHCP request + Edge node-->>Terminal: 2. DHCP response +IP address, DNS assignment + Terminal->>Edge node: 3. IPv4 packet + Note right of CPE: Lookup NAT44 table: +Terminal private IP address <-> Public IP address + Edge node->>Core node: 4. IPv4 packet + Core node->>Server: 5. IPv4 packet + Server-->>Core node: 6. IPv4 packet + Core node->>Edge node: 7. IPv4 packet + Edge node-->>Terminal: 8. IPv4 packet + +``` + +Q.3405(18)\_F7-2 + +Sequence diagram illustrating the procedure for dual stack + NAT with IPoE access with CPE working in bridge mode. The diagram shows the interaction between a Terminal, CPE, Edge node, Core node, and Server. The process starts with a DHCP request from the Terminal to the Edge node, followed by a DHCP response from the Edge node to the Terminal. The CPE then creates a NAT44 table entry. Subsequent IPv4 packets are transmitted from the Terminal to the Edge node, then to the Core node, then to the Server, and back through the Core node and Edge node to the Terminal. The CPE performs NAT mapping at the Edge node. + +**Figure 7-2 – Procedure for dual stack + NAT with IPoE access with CPE working in bridge mode** + +Figure 7-2 depicts the procedure for user IPv4 packet transmission with the CPE working in bridge mode with the mode of "dual stack + NAT with IPoE access". In this mode, the difference from the procedure described in Figure 7-1 is that the user IPv4 packet end-to-end transmission only needs to go through one level of NAT mapping. The NAT mapping is executed at the carrier edge device (e.g., BRAS), from the user private IPv4 address to the public IPv4 address. Only the carrier edge device needs to maintain a NAT mapping table. + +In the mode "dual stack + NAT with IPoE access", terminals can transmit IPv6 traffic directly without NAT. According to different CPE working modes and IPv6 address configuration methods, there are several IPv6 traffic transmission procedure options; for any one of these options, the basic procedure is similar. In this Recommendation, a CPE working in route mode is chosen as a typical mode to explain the IPv6 traffic transmission procedure. Referring to Figure 7-3 and Figure 7-4, two different IPv6 address configuration methods in the terminal are described. The first method uses neighbour discovery protocol (NDP) [IETF RFC 4861] while the second method uses dynamic host configuration protocol version 6 (DHCPv6) [IETF RFC 3315]. + +An IPv6 address consists of an IPv6 prefix and interface identifier (ID) [IETF RFC 4291]. The IPv6 prefix assigned for a terminal should be allocated by the carrier using dynamic host configuration protocol version 6 - prefix delegation (DHCPv6-PD) [IETF RFC 3633]. The terminal can then obtain its IPv6 prefix by the Router Advertisement message in NDP or by DHCPv6. An interface ID can be calculated based on the interface's media access control (MAC) value [IETF RFC 4291]. + +![Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode, and terminal IPv6 address assigned by NDP. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The sequence of messages is as follows: 1. CPE sends an ND RS/RA message to the Edge node. 2. Edge node responds with DHCPv6 information. 3. CPE sends an ND RS/RA message to the Terminal. 4. Terminal responds with DHCPv6 information. 5. Terminal sends an IPv6 packet to the CPE. 6. CPE forwards the IPv6 packet to the Edge node. 7. Edge node forwards the IPv6 packet to the Core node. 8. Core node forwards the IPv6 packet to the Server. 9. Server responds with an IPv6 packet. 10. Core node forwards the response to the Edge node. 11. Edge node forwards the response to the CPE. 12. CPE forwards the response to the Terminal.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: 1. ND RS/RA message (CPE WAN interface's IPv6 prefix) + CPE->>Edge node: 1. ND RS/RA message (CPE WAN interface's IPv6 prefix) + Note right of Edge node: 2. DHCPv6 (DNS-related information, host's IPv6 prefix) + Edge node->>CPE: 2. DHCPv6 (DNS-related information, host's IPv6 prefix) + Note right of CPE: 3. ND RS/RA message (IPv6 prefix assignment) + CPE->>Terminal: 3. ND RS/RA message (IPv6 prefix assignment) + Note right of Terminal: 4. DHCPv6 (DNS-related information) + Terminal->>CPE: 4. DHCPv6 (DNS-related information) + Note right of Terminal: 5. IPv6 packet + Terminal->>CPE: 5. IPv6 packet + Note right of CPE: 6. IPv6 packet + CPE->>Edge node: 6. IPv6 packet + Note right of Edge node: 7. IPv6 packet + Edge node->>Core node: 7. IPv6 packet + Note right of Core node: 8. IPv6 packet + Core node->>Server: 8. IPv6 packet + Note right of Server: 9. IPv6 packet + Server->>Core node: 9. IPv6 packet + Note right of Core node: 10. IPv6 packet + Core node->>Edge node: 10. IPv6 packet + Note right of Edge node: 11. IPv6 packet + Edge node->>CPE: 11. IPv6 packet + Note right of CPE: 12. IPv6 packet + CPE->>Terminal: 12. IPv6 packet + +``` + +Q.3405(18)\_F7-3 + +Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode, and terminal IPv6 address assigned by NDP. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The sequence of messages is as follows: 1. CPE sends an ND RS/RA message to the Edge node. 2. Edge node responds with DHCPv6 information. 3. CPE sends an ND RS/RA message to the Terminal. 4. Terminal responds with DHCPv6 information. 5. Terminal sends an IPv6 packet to the CPE. 6. CPE forwards the IPv6 packet to the Edge node. 7. Edge node forwards the IPv6 packet to the Core node. 8. Core node forwards the IPv6 packet to the Server. 9. Server responds with an IPv6 packet. 10. Core node forwards the response to the Edge node. 11. Edge node forwards the response to the CPE. 12. CPE forwards the response to the Terminal. + +**Figure 7-3 – Procedure for user IPv6 packet transmission with CPE working in route mode, and terminal IPv6 address assigned by NDP** + +Figure 7-3 depicts the mode of IPv4/IPv6 dual stack with the CPE working in route mode, and with the CPE obtaining its wide area network (WAN) IPv6 prefix from the network using NDP. At the same time, the CPE requests an IPv6 prefix delegation from the carrier edge device (e.g., BRAS) using DHCPv6. After obtaining an IPv6 prefix for the user network, a CPE can announce this IPv6 prefix to the terminal using NDP. When obtaining an IPv6 prefix, the CPE and terminal automatically generate an IPv6 address with an interface ID. The CPE and terminal can obtain DNS-related information using DHCPv6. User data are all encapsulated into IPv6 packets for transmission. + +![Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode, and terminal IPv6 address assigned by DHCPv6. The diagram involves five entities: Terminal, CPE, Edge node, Core node, and Server. The sequence of messages is: 1. ND RS/RA message (CPE WAN interface's IPv6 prefix) from CPE to Edge node; 2. DHCPv6 message (DNS-related information, host's IPv6 prefix assignment) from Edge node to CPE; 3. DHCPv6 message (IPv6 prefix and DNS-related information) from CPE to Terminal; 4. IPv6 packet from Terminal to CPE; 5. IPv6 packet from CPE to Edge node; 6. IPv6 packet from Edge node to Core node; 7. IPv6 packet from Core node to Server; 8. IPv6 packet from Server to Core node; 9. IPv6 packet from Core node to Edge node; 10. IPv6 packet from Edge node to CPE; 11. IPv6 packet from CPE to Terminal.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: 1. ND RS/RA message (CPE WAN interface's IPv6 prefix) + CPE->>Edge node: 1. ND RS/RA message (CPE WAN interface's IPv6 prefix) + Note right of Edge node: 2. DHCPv6 message (DNS-related information, host's IPv6 prefix assignment) + Edge node->>CPE: 2. DHCPv6 message (DNS-related information, host's IPv6 prefix assignment) + Note right of CPE: 3. DHCPv6 message (IPv6 prefix and DNS-related information) + CPE->>Terminal: 3. DHCPv6 message (IPv6 prefix and DNS-related information) + Note right of Terminal: 4. IPv6 packet + Terminal->>CPE: 4. IPv6 packet + Note right of CPE: 5. IPv6 packet + CPE->>Edge node: 5. IPv6 packet + Note right of Edge node: 6. IPv6 packet + Edge node->>Core node: 6. IPv6 packet + Note right of Core node: 7. IPv6 packet + Core node->>Server: 7. IPv6 packet + Note right of Server: 8. IPv6 packet + Server->>Core node: 8. IPv6 packet + Note right of Core node: 9. IPv6 packet + Core node->>Edge node: 9. IPv6 packet + Note right of Edge node: 10. IPv6 packet + Edge node->>CPE: 10. IPv6 packet + Note right of CPE: 11. IPv6 packet + CPE->>Terminal: 11. IPv6 packet + +``` + +Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode, and terminal IPv6 address assigned by DHCPv6. The diagram involves five entities: Terminal, CPE, Edge node, Core node, and Server. The sequence of messages is: 1. ND RS/RA message (CPE WAN interface's IPv6 prefix) from CPE to Edge node; 2. DHCPv6 message (DNS-related information, host's IPv6 prefix assignment) from Edge node to CPE; 3. DHCPv6 message (IPv6 prefix and DNS-related information) from CPE to Terminal; 4. IPv6 packet from Terminal to CPE; 5. IPv6 packet from CPE to Edge node; 6. IPv6 packet from Edge node to Core node; 7. IPv6 packet from Core node to Server; 8. IPv6 packet from Server to Core node; 9. IPv6 packet from Core node to Edge node; 10. IPv6 packet from Edge node to CPE; 11. IPv6 packet from CPE to Terminal. + +Q.3405(18)\_F7-4 + +**Figure 7-4 – Procedure for user IPv6 packet transmission with CPE working in route mode, and terminal IPv6 address assigned by DHCPv6** + +Figure 7-4 depicts the mode of IPv4/IPv6 dual stack with the CPE working in route mode. However, as differentiated from the procedure of Figure 7-3, in this case the terminal obtains an IPv6 prefix and DNS information from the CPE using DHCPv6, and automatically generates an IPv6 address with an interface ID. + +## 7.2 Procedures for dual stack + NAT with PPPoE access + +Figure 7-5 depicts the IPv4 traffic transmission procedure with the CPE working in route mode. IPv4 data sent along the transmission path will be processed by two NAT devices. The first NAT device is the CPE, which translates a user private network IPv4 address to a carrier private network IPv4 address; the second NAT device is a carrier edge node (e.g., BRAS), which translates a carrier private network IPv4 address to a public network IPv4 address. + +![Sequence diagram showing the procedure for dual stack + NAT with PPPoE access with CPE working in route mode. The diagram illustrates the interaction between Terminal, CPE, Edge node, Core node, and Server. It details the steps for PPPoE discovery, DHCP request/response, and IPv4 packet translation at both the CPE and Edge node using NAT44 tables.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: 1. PPPoE discovery + CPE->>Edge node: 1. PPPoE discovery + Note right of CPE: 2. PPPoE session (User authentication, carrier private network IP address and DNS assignment) + Edge node->>CPE: 2. PPPoE session (User authentication, carrier private network IP address and DNS assignment) + + Terminal->>CPE: 3. DHCP request + CPE->>Terminal: 4. DHCP response (Terminal private network IP address and DNS assignment) + + Note left of CPE: Create NAT44 table: Terminal private network IP <-> Carrier private network IP + Terminal->>CPE: 5. IPv4 packet + Note right of CPE: Create NAT44 table: Carrier private network IP <-> Public network IP + CPE->>Edge node: 6. IPv4 packet + Edge node->>Core node: 7. IPv4 packet + Core node->>Server: 8. IPv4 packet + Server->>Core node: 9. IPv4 packet + Core node->>Edge node: 10. IPv4 packet + Edge node->>CPE: 11. IPv4 packet + Note left of CPE: Lookup NAT44 table: Terminal private network IP <-> Carrier private network IP + CPE->>Terminal: 12. IPv4 packet + +``` + +Q.3405(18)\_F7-5 + +Sequence diagram showing the procedure for dual stack + NAT with PPPoE access with CPE working in route mode. The diagram illustrates the interaction between Terminal, CPE, Edge node, Core node, and Server. It details the steps for PPPoE discovery, DHCP request/response, and IPv4 packet translation at both the CPE and Edge node using NAT44 tables. + +**Figure 7-5 – Procedure for dual stack + NAT with PPPoE access with CPE working in route mode** + +In route mode, as shown in Figure 7-5, the CPE obtains a carrier private IPv4 address and DNS-related information from a carrier edge node using the PPPoE protocol. The terminal obtains a private IPv4 address and DNS-related information from the CPE using DHCP. When sending user data, the CPE executes the first level of NAT mapping from a user private IPv4 address to a carrier private IPv4 address. Then, the carrier edge node executes the second level of NAT mapping from a carrier private IPv4 address to a public IPv4 address. When receiving user data, the carrier edge node executes the first level of NAT mapping from the public IPv4 address to the carrier private IPv4 address. The CPE then executes the second level of NAT mapping from the carrier private IPv4 address to the user private IPv4 address. Both the CPE and carrier edge node must maintain NAT mapping tables. + +Figure 7-6 depicts the IPv4 traffic transmission procedure with CPE working in bridge mode. IPv4 data sent along the transmission path will be processed by one NAT device, the carrier edge node (e.g., BRAS), which translates a user private network IP address to a public network IP address. + +![Sequence diagram showing the procedure for dual stack + NAT with PPPoE access with CPE working in bridge mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The process starts with PPPoE discovery and session establishment between Terminal and Edge node. Then, a DHCP request and response are exchanged between Terminal and Edge node. Next, the CPE creates a NAT44 table entry. The Terminal sends an IPv4 packet to the CPE, which is then forwarded by the Edge node to the Core node, then to the Server. The Server responds with an IPv4 packet that is routed back through the Core node and Edge node to the CPE, which then forwards it to the Terminal. NAT mapping is performed at the Edge node for outgoing traffic and at the CPE for incoming traffic.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: Create NAT44 table: +Terminal private network IP <-> Public network IP + + Terminal->>Edge node: 1. PPPoE discovery + Edge node-->>Terminal: 2. PPPoE session (user authentication, terminal private IP address and DNS assignment) + Terminal->>Edge node: 3. DHCP request + Edge node-->>Terminal: 4. DHCP response (Terminal private IP address and DNS assignment) + Terminal->>CPE: 5. IPv4 packet + Note right of CPE: Lookup NAT44 table: +Carrier private network IP <-> Public network IP + CPE->>Edge node: 6. IPv4 packet + Edge node->>Core node: 7. IPv4 packet + Core node->>Server: 8. IPv4 packet + Server-->>Core node: 9. IPv4 packet + Core node-->>Edge node: 10. IPv4 packet + Edge node-->>CPE: 11. IPv4 packet + CPE-->>Terminal: 12. IPv4 packet + +``` + +Q.3405(18)\_F7-6 + +Sequence diagram showing the procedure for dual stack + NAT with PPPoE access with CPE working in bridge mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The process starts with PPPoE discovery and session establishment between Terminal and Edge node. Then, a DHCP request and response are exchanged between Terminal and Edge node. Next, the CPE creates a NAT44 table entry. The Terminal sends an IPv4 packet to the CPE, which is then forwarded by the Edge node to the Core node, then to the Server. The Server responds with an IPv4 packet that is routed back through the Core node and Edge node to the CPE, which then forwards it to the Terminal. NAT mapping is performed at the Edge node for outgoing traffic and at the CPE for incoming traffic. + +**Figure 7-6 – Procedure for dual stack + NAT with PPPoE access with CPE working in bridge mode** + +In bridge mode, as shown in Figure 7-6, the terminal obtains a user private network IPv4 address and DNS-related information from a carrier edge node using the PPPoE protocol or DHCP. When a terminal is transmitting user data, the carrier edge node executes the NAT mapping from a user private network IPv4 address to a public network IPv4 address. When the terminal is receiving data, the carrier edge node executes the NAT mapping from the public network IPv4 address to the user private network IPv4 address. The carrier edge node must maintain the NAT mapping table. + +Figure 7-7 and Figure 7-8 depict IPv6 traffic transmission procedures with the CPE working in route mode. The main difference between these two procedures is the method by which the terminal acquires its IPv6 prefix, either via NDP or DHCPv6 respectively. + +![Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The sequence starts with PPPoE discovery and session between CPE and Edge node. Then, ND RS/RA and DHCPv6 messages are sent from CPE to Terminal. Finally, IPv6 packets are transmitted from Terminal through CPE, Edge node, Core node, and Server, with a return path for the response.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: 1. PPPoE discovery + CPE->>Edge node: 1. PPPoE discovery + Note right of CPE: 2. PPPoE session (User authentication, CPE WAN interface's IPv6 prefix, host's IPv6 prefix and DNS-related information) + CPE->>Edge node: 2. PPPoE session (User authentication, CPE WAN interface's IPv6 prefix, host's IPv6 prefix and DNS-related information) + Note left of CPE: 3. ND RS/RA message (Host's IPv6 prefix) + CPE->>Terminal: 3. ND RS/RA message (Host's IPv6 prefix) + Note left of CPE: 4. DHCPv6 message (DNS-related information) + CPE->>Terminal: 4. DHCPv6 message (DNS-related information) + Note left of Terminal: 5. IPv6 packet + Terminal->>CPE: 5. IPv6 packet + Note right of CPE: 6. IPv6 packet + CPE->>Edge node: 6. IPv6 packet + Note right of Edge node: 7. IPv6 packet + Edge node->>Core node: 7. IPv6 packet + Note right of Core node: 8. IPv6 packet + Core node->>Server: 8. IPv6 packet + Note left of Server: 9. IPv6 packet + Server->>Core node: 9. IPv6 packet + Note right of Core node: 10. IPv6 packet + Core node->>Edge node: 10. IPv6 packet + Note right of Edge node: 11. IPv6 packet + Edge node->>CPE: 11. IPv6 packet + Note left of CPE: 12. IPv6 packet + CPE->>Terminal: 12. IPv6 packet + +``` + +Q.3405(18)\_F7-7 + +Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The sequence starts with PPPoE discovery and session between CPE and Edge node. Then, ND RS/RA and DHCPv6 messages are sent from CPE to Terminal. Finally, IPv6 packets are transmitted from Terminal through CPE, Edge node, Core node, and Server, with a return path for the response. + +**Figure 7-7 – Procedure for user IPv6 packet transmission with CPE working in route mode, IPv6 address of a terminal assigned by NDP** + +As shown in Figure 7-7, a CPE obtains a terminal IPv6 prefix and DNS-related information from a carrier edge node using PPPoE. The CPE then announces the IPv6 prefix to the terminal using NDP and assigns the DNS-related information to the terminal using DHCPv6 when the O flag in the Router Advertisement message of NDP is set [IETF RFC 4861]. The terminal automatically generates an IPv6 address based on the received IPv6 prefix and the calculated interface ID. User data are all encapsulated into IPv6 packets for transmission. + +![Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The sequence of messages is: 1. PPPoE discovery (CPE to Edge node), 2. PPPoE session (Edge node to CPE), 3. DHCPv6 message exchange (CPE to Terminal), 4. IPv6 packet (Terminal to CPE), 5. IPv6 packet (CPE to Edge node), 6. IPv6 packet (Edge node to Core node), 7. IPv6 packet (Core node to Server), 8. IPv6 packet (Server to Core node), 9. IPv6 packet (Core node to Edge node), 10. IPv6 packet (Edge node to CPE), 11. IPv6 packet (CPE to Terminal).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: 1. PPPoE discovery + CPE->>Edge node: 1. PPPoE discovery + Note right of Edge node: 2. PPPoE session (User authentication, CPE WAN interface's IPv6 prefix, host's IPv6 prefix and DNS assignment) + Edge node->>CPE: 2. PPPoE session... + Note left of CPE: 3. DHCPv6 message exchange (IPv6 prefix and DNS assignment) + CPE->>Terminal: 3. DHCPv6 message exchange... + Note left of Terminal: 4. IPv6 packet + Terminal->>CPE: 4. IPv6 packet + Note right of CPE: 5. IPv6 packet + CPE->>Edge node: 5. IPv6 packet + Note right of Edge node: 6. IPv6 packet + Edge node->>Core node: 6. IPv6 packet + Note right of Core node: 7. IPv6 packet + Core node->>Server: 7. IPv6 packet + Note right of Server: 8. IPv6 packet + Server->>Core node: 8. IPv6 packet + Note right of Core node: 9. IPv6 packet + Core node->>Edge node: 9. IPv6 packet + Note right of Edge node: 10. IPv6 packet + Edge node->>CPE: 10. IPv6 packet + Note left of CPE: 11. IPv6 packet + CPE->>Terminal: 11. IPv6 packet + +``` + +Q.3405(18)\_F7-8 + +Sequence diagram showing the procedure for user IPv6 packet transmission with CPE working in route mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The sequence of messages is: 1. PPPoE discovery (CPE to Edge node), 2. PPPoE session (Edge node to CPE), 3. DHCPv6 message exchange (CPE to Terminal), 4. IPv6 packet (Terminal to CPE), 5. IPv6 packet (CPE to Edge node), 6. IPv6 packet (Edge node to Core node), 7. IPv6 packet (Core node to Server), 8. IPv6 packet (Server to Core node), 9. IPv6 packet (Core node to Edge node), 10. IPv6 packet (Edge node to CPE), 11. IPv6 packet (CPE to Terminal). + +**Figure 7-8 – Procedure for user IPv6 packet transmission with CPE working in route mode, IPv6 address of a terminal assigned by DHCPv6** + +As differentiated from the procedure of Figure 7-7, in Figure 7-8, the terminal obtains the IPv6 prefix and DNS-related information from the CPE using DHCPv6. + +## 7.3 Procedures for DS-Lite with PPPoE access + +Figure 7-9 depicts the IPv4 traffic transmission procedure in DS-Lite + PPPoE mode. IPv4 data sent along the transmission path are orderly encapsulated in a DS-Lite tunnel (IPv4 in IPv6 tunnel) [IETF RFC 6333] and the PPPoE session at the CPE, and then decapsulated in the PPPoE session and DS-Lite tunnel. The user data IPv4 address is translated from a user private network IPv4 address to a public network IPv4 address at the carrier edge node (e.g., BRAS). + +![Sequence diagram showing the procedure for DS-Lite with PPPoE access when CPE working in route mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The process starts with PPPoE discovery and session establishment between CPE and Edge node. Then, a DS-Lite tunnel is established. The Terminal sends a DHCPv4 message exchange to the CPE for IP address and DNS assignment. When the Terminal sends an IPv4 packet, the CPE creates a NAT44 table entry (Terminal private network IP <-> Public network IP), encapsulates the packet as (IPv4 in IPv6) over PPPoE, and sends it to the Edge node. The Edge node decapsulates it to an IPv4 packet, which is routed through the Core node to the Server. The Server's response is routed back through the Core node to the Edge node. The Edge node looks up the NAT44 table, encapsulates the packet as (IPv4 in IPv6) over PPPoE, and sends it back to the CPE. Finally, the CPE decapsulates the packet and sends the IPv4 packet to the Terminal.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant CPE + participant Edge node + participant Core node + participant Server + + Note right of CPE: Create NAT44 table: +Terminal private network IP <-> +Public network IP + + CPE->>Edge node: 1. PPPoE discovery + Edge node-->>CPE: 2. PPPoE session (User authentication, CPE WAN interface's IPv6 prefix, host's IPv6 prefix and DNS assignment) + CPE->>Edge node: 3. DS-Lite tunnel establishment + Terminal->>CPE: 4. DHCPv4 message exchange (IPv4 address and DNS assignment) + Terminal->>CPE: 5. IPv4 packet + Note right of CPE: Lookup NAT44 table: +Terminal private network IP <-> +Public network IP + CPE->>Edge node: 6. (IPv4 in IPv6) over PPPoE + Edge node->>Core node: 7. IPv4 packet + Core node->>Server: 8. IPv4 packet + Server-->>Core node: 9. IPv4 packet + Core node->>Edge node: 10. IPv4 packet + Edge node->>CPE: 11. (IPv4 in IPv6) over PPPoE + CPE->>Terminal: 12. IPv4 packet + +``` + +Sequence diagram showing the procedure for DS-Lite with PPPoE access when CPE working in route mode. The diagram involves five lifelines: Terminal, CPE, Edge node, Core node, and Server. The process starts with PPPoE discovery and session establishment between CPE and Edge node. Then, a DS-Lite tunnel is established. The Terminal sends a DHCPv4 message exchange to the CPE for IP address and DNS assignment. When the Terminal sends an IPv4 packet, the CPE creates a NAT44 table entry (Terminal private network IP <-> Public network IP), encapsulates the packet as (IPv4 in IPv6) over PPPoE, and sends it to the Edge node. The Edge node decapsulates it to an IPv4 packet, which is routed through the Core node to the Server. The Server's response is routed back through the Core node to the Edge node. The Edge node looks up the NAT44 table, encapsulates the packet as (IPv4 in IPv6) over PPPoE, and sends it back to the CPE. Finally, the CPE decapsulates the packet and sends the IPv4 packet to the Terminal. + +Q.3405(18)\_F7-9 + +**Figure 7-9 – Procedure for DS-Lite with PPPoE access when CPE working in route mode** + +As shown in Figure 7-9, the CPE obtains IPv6 prefix and DNS-related information from a carrier edge node using PPPoE and then sets up a DS-Lite tunnel with the carrier edge node. The terminal obtains private IPv4 address and DNS-related information from the CPE using DHCP. When a terminal is sending user data, the CPE encapsulates these data into a DS-Lite tunnel. The carrier edge node decapsulates the packets, and translates a user private IPv4 address into a public IPv4 address which creates a NAT mapping item. When a terminal is receiving data, the carrier edge node translates a public IPv4 address into a user private network IPv4 address according to the NAT mapping table, and encapsulates the packet into a DS-Lite tunnel. A CPE decapsulates the packet by removing the IPv6 header and sends it to a terminal. + +Figure 7-10 and Figure 7-11 depicts the IPv6 traffic transmission procedure in DS-Lite + PPPoE mode. The main difference between these two procedures is the method used by the terminal to acquire the IPv6 prefix. + +![Sequence diagram for IPv6 packet transmission with CPE in route mode and terminal IPv6 address assigned by NDP. Lifelines: Terminal, CPE, Edge node, Core node, Server. The sequence shows 12 steps: 1. PPPoE discovery (CPE to Edge node), 2. PPPoE session (Edge node to CPE), 3. ND RS/RA message (CPE to Terminal), 4. DHCPv6 message (CPE to Terminal), 5. IPv6 packet (Terminal to CPE), 6. IPv6 over PPPoE (CPE to Edge node), 7. IPv6 packet (Edge node to Core node), 8. IPv6 packet (Core node to Server), 9. IPv6 packet (Server to Core node), 10. IPv6 packet (Core node to Edge node), 11. IPv6 over PPPoE (Edge node to CPE), 12. IPv6 packet (CPE to Terminal).](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +Q.3405(18)\_F7-10 + +Sequence diagram for IPv6 packet transmission with CPE in route mode and terminal IPv6 address assigned by NDP. Lifelines: Terminal, CPE, Edge node, Core node, Server. The sequence shows 12 steps: 1. PPPoE discovery (CPE to Edge node), 2. PPPoE session (Edge node to CPE), 3. ND RS/RA message (CPE to Terminal), 4. DHCPv6 message (CPE to Terminal), 5. IPv6 packet (Terminal to CPE), 6. IPv6 over PPPoE (CPE to Edge node), 7. IPv6 packet (Edge node to Core node), 8. IPv6 packet (Core node to Server), 9. IPv6 packet (Server to Core node), 10. IPv6 packet (Core node to Edge node), 11. IPv6 over PPPoE (Edge node to CPE), 12. IPv6 packet (CPE to Terminal). + +**Figure 7-10 – Procedure for user IPv6 packet transmission with CPE working in route mode, IPv6 address of terminal assigned by NDP** + +As shown in Figure 7-10, a CPE obtains IPv6 prefix and DNS-related information from the carrier edge node using PPPoE. The terminal obtains an IPv6 prefix using NDP, and automatically generates an IPv6 address based on the received IPv6 prefix and the calculated interface ID. The terminal configures DNS-related information using DHCP when the O flag in the Router Advertisement message of NDP is set. User data are all encapsulated into IPv6 packets for transmission. + +![Sequence diagram for IPv6 packet transmission with CPE in route mode and terminal IPv6 address assigned by DHCPv6. Lifelines: Terminal, CPE, Edge node, Core node, Server. The sequence shows 11 steps: 1. PPPoE discovery (CPE to Edge node), 2. PPPoE session (Edge node to CPE), 3. DHCPv6 message exchange (CPE to Terminal), 4. IPv6 packet (Terminal to CPE), 5. IPv6 packet over PPPoE (CPE to Edge node), 6. IPv6 packet (Edge node to Core node), 7. IPv6 packet (Core node to Server), 8. IPv6 packet (Server to Core node), 9. IPv6 packet (Core node to Edge node), 10. IPv6 packet over PPPoE (Edge node to CPE), 11. IPv6 packet (CPE to Terminal).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Q.3405(18)\_F7-11 + +Sequence diagram for IPv6 packet transmission with CPE in route mode and terminal IPv6 address assigned by DHCPv6. Lifelines: Terminal, CPE, Edge node, Core node, Server. The sequence shows 11 steps: 1. PPPoE discovery (CPE to Edge node), 2. PPPoE session (Edge node to CPE), 3. DHCPv6 message exchange (CPE to Terminal), 4. IPv6 packet (Terminal to CPE), 5. IPv6 packet over PPPoE (CPE to Edge node), 6. IPv6 packet (Edge node to Core node), 7. IPv6 packet (Core node to Server), 8. IPv6 packet (Server to Core node), 9. IPv6 packet (Core node to Edge node), 10. IPv6 packet over PPPoE (Edge node to CPE), 11. IPv6 packet (CPE to Terminal). + +**Figure 7-11 – Procedure for user IPv6 packet transmission with CPE working in route mode, IPv6 address of terminal assigned by DHCPv6** + +As differentiated from the procedure of Figure 7-10, in Figure 7-11 a terminal obtains IPv6 prefix and DNS-related information from a CPE using DHCPv6. + + + + + +## 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.3615-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3615-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/Q/T-REC-Q.3615-201504-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.3617-201506-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3617-201506-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59 --- /dev/null +++ b/marked/Q/T-REC-Q.3617-201506-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_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.3617-201506-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3617-201506-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1904b2d74711d8cfd6e37ff30bceff480de15e47 --- /dev/null +++ b/marked/Q/T-REC-Q.3617-201506-I_PDF-E/raw.md @@ -0,0 +1,193 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3617** + +(06/2015) + +# **SERIES Q: SWITCHING AND SIGNALLING** + +Signalling requirements and protocols for the NGN – +Service and session control protocols – supplementary +services + +--- + +**Terminating identification presentation and +terminating identification restriction using IP +multimedia core network subsystem. Protocol +specification; version 1** + +Recommendation ITU-T Q.3617 + +## 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.3617 + +### Terminating identification presentation and terminating identification restriction using IP multimedia core network subsystem. Protocol specification; version 1 + +## Summary + +Recommendation ITU-T Q.3617 specifies requirements for supplementary services such as terminating identification presentation (TIP) and terminating identification restriction (TIR) to be provided on the IMS platform. + +The version number "version 1", indicates that this is version one of Recommendation ITU-T Q.3617 and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +This Recommendation endorses ETSI TS 124 608 V10.1.0 (2013-07) "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 version 10.1.0 Release 10)". + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3617 | 2015-06-13 | 11 | 11.1002/1000/12493 | + +## Keywords + +IMS, SIP, SDP, TIP, TIR, testing, user side, network 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 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | | Page | +|---|----------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Endorsement ..... | 2 | + + + +### Recommendation ITU-T Q.3617 + +### Terminating identification presentation and terminating identification restriction using IP multimedia core network subsystem. Protocol specification; version 1 + +## 1 Scope + +This Recommendation specifies the requirements to protocols implementation for providing supplementary services such as terminating identification presentation (TIP) and terminating identification restriction (TIR) on the IMS basis. + +The Recommendation endorses ETSI TS 124 608 V10.1.0 (2013-07) "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 version 10.1.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 608 V10.1.0] ETSI TS 124 608 V10.1.0 (2013-07), "*Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 version 10.1.0 Release 10)*". + +## 3 Definitions + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-----------------------------------------| +| IP | Internet protocol | +| IMS | IP Multimedia Subsystem | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| TIP | Terminating Identification Presentation | +| TIR | Terminating Identification Restriction | + +## **5 Endorsement** + +[ETSI TS 124 608 V10.1.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 | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3618-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3618-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8c8ef290cbd72d8b1f34f581f71b8767884d399 --- /dev/null +++ b/marked/Q/T-REC-Q.3618-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed957fe3067ffdd7efbbc3bf42a8f159634c1c65a458ecc3813a4ec4f9644d92 +size 4119 diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9c501d095fb9e6d26e0a3b8cd1b0770e9d4f2c2c --- /dev/null +++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/raw.md @@ -0,0 +1,635 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3645** + +(09/2020) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for the NGN – +VoLTE/ViLTE network signalling + +--- + +**Protocol at the interface between two +distributed ENUM servers for IMS** + +Recommendation ITU-T Q.3645 + +# 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 P2P 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.3645 + +# Protocol at the interface between two distributed ENUM servers for IMS + +## Summary + +Recommendation ITU-T Q.3645 defines the protocol at the interface between two distributed ITU-T E.164 number mapping (ENUM) servers (DES) of a distributed ENUM system in support of IP multimedia core network subsystem (IMS) interconnection. Based on the functions and signalling requirements defined in Recommendation ITU-T Q.3643, this Recommendation provides the reference model, procedures, protocol and message specification for the interface between two DES. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3645 | 2020-09-29 | 11 | 11.1002/1000/14414 | + +## Keywords + +Distributed, ENUM, IMS, 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, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Interface between two distributed ENUM servers..... | 2 | +| 6.1 Overview ..... | 2 | +| 6.2 Idd reference model ..... | 2 | +| 6.3 Functional elements and capabilities..... | 3 | +| 7 DES procedures ..... | 3 | +| 7.1 DES node management procedures..... | 3 | +| 7.2 ENUM data profile management..... | 5 | +| 7.3 Error handling procedures ..... | 8 | +| 8 Protocol specification ..... | 8 | +| 9 Message specification..... | 9 | +| 9.1 Messages..... | 9 | +| 9.2 Message acknowledgement ..... | 9 | +| 9.3 Result code of the SOAP response message ..... | 10 | +| Bibliography..... | 11 | + + + +## Recommendation ITU-T Q.3645 + +## Protocol at the interface between two distributed ENUM servers for IMS + +# 1 Scope + +This Recommendation specifies the protocol at the interface between two distributed ENUM servers (DES) of distributed ENUM networking in support of IP Multimedia core network subsystem (IMS) interconnection. The functions and signalling requirements for this interface are contained in [ITU-T Q.3643]. + +Using the protocol specified in this Recommendation, the DES can: + +- initiate and provide a response to a DES node management request, including the requests for adding a DES node to and remove a DES node from a distributed ENUM system; +- initiate and provide a response to a DES ENUM data management request, including requests for ENUM data records adding, ENUM data records modification, ENUM data records cancellation, etc. + +# 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.3643] Recommendation ITU-T Q.3643 (2020), *Signalling architecture of distributed infrastructure ENUM networking for IMS*. +- [IETF RFC 7230] IETF RFC 7230 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing*. +- [IETF RFC 7231] IETF RFC 7231 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content*. +- [IETF RFC 7232] IETF RFC 7232 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests*. +- [IETF RFC 7235] IETF RFC 7235 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Authentication*. +- [W3C SOAP] W3C Recommendation (2007), *SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------| +| DES | Distributed ENUM server | +| ENUM | ITU-T E.164 Number Mapping | +| HTTP | Hypertext Transfer Protocol | +| IMS | IP Multimedia Core Network Subsystem | +| NAPTR | Naming Authority Pointer | +| SIP | Session Initiation Protocol | +| SOAP | Simple Object Access Protocol | +| URI | Uniform Resource Identifier | + +# 5 Conventions + +In this Recommendation: + +The phrase "is recommended" indicates a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be satisfied to claim conformance. + +In the body of this document, the word "should" sometimes appear, in which case it is to be interpreted, respectively, as the phrase "is recommended". + +# 6 Interface between two distributed ENUM servers + +## 6.1 Overview + +The Idd interface (defined in clause 6.2) is used for information exchange to synchronize the status and the ENUM data profile of the distributed ENUM servers. The information is used by the IMS SIP proxy for ENUM resolution. + +The Idd interface is an inter-operator interface. One distributed ENUM server shall be able to interact with a number of distributed ENUM servers via Idd interfaces in support of interconnection with ENUM servers in different IMS domains. + +## 6.2 Idd reference model + +The Idd interface, as shown in Figure 6-1, is defined between two distributed ENUM servers for IMS inter-domain connection. The Idd interface is used for node management and ENUM data management in the distributed ENUM networking environment. + +![Figure 6-1 – Idd reference model diagram showing the connection between two distributed ENUM servers (DES) via an Idd interface. The diagram is split into two halves, Operator a and Operator b, separated by a central Idd interface. On Operator a's side, an IMS node connects to an ENUM (Operator level) node, which connects to a Distributed ENUM server (DES). On Operator b's side, a Distributed ENUM server (DES) connects to an ENUM (Operator level) node, which connects to an IMS node. The Idd interface is shown as a horizontal line with a break in the middle, connecting the two DES nodes.](740442c999390734911677f01af0316d_img.jpg) + +``` +graph LR; subgraph Operator_a [Operator a]; IMS_a((IMS)) --- ENUM_a[ENUM (Operator level)]; ENUM_a --- DES_a[ Distributed ENUM server (DES) ]; end; subgraph Operator_b [Operator b]; DES_b[ Distributed ENUM server (DES) ] --- ENUM_b[ENUM (Operator level)]; ENUM_b --- IMS_b((IMS)); end; DES_a --- Idd[ Idd ]; Idd --- DES_b; +``` + +Figure 6-1 – Idd reference model diagram showing the connection between two distributed ENUM servers (DES) via an Idd interface. The diagram is split into two halves, Operator a and Operator b, separated by a central Idd interface. On Operator a's side, an IMS node connects to an ENUM (Operator level) node, which connects to a Distributed ENUM server (DES). On Operator b's side, a Distributed ENUM server (DES) connects to an ENUM (Operator level) node, which connects to an IMS node. The Idd interface is shown as a horizontal line with a break in the middle, connecting the two DES nodes. + +Q.3645(20)\_F6-1 + +Figure 6-1 – Idd reference model + +## 6.3 Functional elements and capabilities + +The DES is a functional element that serves for inter-operator IMS session establishment and provides mapping of ITU-T E.164 numbers to uniform resource identifiers (URIs). The DES stores the ENUM mapping data profile of the host operator and the connecting operators. It performs the ENUM data management procedures to synchronize the ENUM data profile of the connecting DES via Idd interface. + +# 7 DES procedures + +## 7.1 DES node management procedures + +### 7.1.1 DES node added to a distributed ENUM system + +Figure 7-1 shows the DES node adding procedure when a DES of a newly involved operator wants to broadcast its ENUM profile to and get ENUM profile from relevant DESs. + +![Sequence diagram showing the DES node adding procedure between an Originating DES and a Terminating DES. The steps are: 1. ADD_NODE_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating (T0 timer); 3. ADD_NODE_RESP from Terminating to Originating (T1 timer); 4. ACK (100) from Originating to Terminating.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +``` +sequenceDiagram + participant Originating DES + participant Terminating DES + Note left of Originating DES: T0 + Note left of Originating DES: T1 + Originating DES->>Terminating DES: 1. ADD_NODE_REQ + Terminating DES-->>Originating DES: 2. ACK (100) + Terminating DES-->>Originating DES: 3. ADD_NODE_RESP + Originating DES-->>Terminating DES: 4. ACK (100) +``` + +Q.3645(20)\_F7-1 + +Sequence diagram showing the DES node adding procedure between an Originating DES and a Terminating DES. The steps are: 1. ADD\_NODE\_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating (T0 timer); 3. ADD\_NODE\_RESP from Terminating to Originating (T1 timer); 4. ACK (100) from Originating to Terminating. + +**Figure 7-1 – DES node added to a distributed ENUM system** + +The following steps are performed: + +1. The originating DES sends an ADD\_NODE\_REQ message to the terminating DES for transferring the ENUM mapping data profile of the originating DES and requesting for the ENUM mapping data profile of terminating DES. T0 timer is started. + +NOTE 1 – T0 is the maximum duration between sending a request/response message and receiving the message acknowledgement. + +The ADD\_NODE\_REQ message should include: + +- 1) Message identifier + - 2) The originating operator identifier + - 3) The terminating operator identifier + - 4) The IP address of the originating DES + - 5) The IP address of the terminating DES + - 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) ENUM mapping data list which includes the ENUM mapping naming authority pointer (NAPTR) records + - 8) Timestamp of activation which presents the date and time of involving the ENUM mapping data of originating DES. +2. The originating DES starts timer T1 when receives an ACK (100) from the terminating DES. + +NOTE 2 – The timer T1 is the maximum duration between the originating DES receiving an ACK (100) for request message and receiving response message. + +3. The terminating DES stores and activates the receiving ENUM mapping data profile of the originating DES. It sends a response to the originating DES with an ADD\_NODE\_RESP message that contains the requested ENUM mapping data profile of the terminating DES. The originating DES stores and activates the receiving ENUM mapping data profile of the terminating DES. + +The ADD\_NODE\_RESP message should include: + +- 1) Message identifier + - 2) The originating operator identifier + - 3) The terminating operator identifier + - 4) The IP address of the originating DES + - 5) The IP address of the terminating DES + - 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The result code and result description of the activation of the originating DES. +4. The originating DES sends ACK (100) to the terminating DES with successful acknowledgement. + +### 7.1.2 DES node removed from a distributed ENUM system + +Figure 7-2 shows the DES node removed procedure when the operator of the originating DES decides to end the interconnection agreement with the operator of the terminating DES. + +![Sequence diagram showing the removal of a DES node from a distributed ENUM system. The diagram shows two lifelines: Originating DES and Terminating DES. The sequence of messages is: 1. REMOVE_NODE_REQ from Originating DES to Terminating DES; 2. ACK (100) from Terminating DES to Originating DES; 3. REMOVE_NODE_RESP from Terminating DES to Originating DES; 4. ACK (100) from Originating DES to Terminating DES. Two timers are shown on the Originating DES lifeline: T0 starts at the receipt of ACK (100) and ends at the receipt of REMOVE_NODE_RESP; T1 starts at the receipt of REMOVE_NODE_REQ and ends at the receipt of REMOVE_NODE_RESP.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +``` +sequenceDiagram + participant Originating DES + participant Terminating DES + Note left of Originating DES: T0 + Note left of Originating DES: T1 + Originating DES->>Terminating DES: 1. REMOVE_NODE_REQ + Terminating DES-->>Originating DES: 2. ACK (100) + Terminating DES-->>Originating DES: 3. REMOVE_NODE_RESP + Originating DES-->>Terminating DES: 4. ACK (100) +``` + +Q.3645(20)\_F7-2 + +Sequence diagram showing the removal of a DES node from a distributed ENUM system. The diagram shows two lifelines: Originating DES and Terminating DES. The sequence of messages is: 1. REMOVE\_NODE\_REQ from Originating DES to Terminating DES; 2. ACK (100) from Terminating DES to Originating DES; 3. REMOVE\_NODE\_RESP from Terminating DES to Originating DES; 4. ACK (100) from Originating DES to Terminating DES. Two timers are shown on the Originating DES lifeline: T0 starts at the receipt of ACK (100) and ends at the receipt of REMOVE\_NODE\_RESP; T1 starts at the receipt of REMOVE\_NODE\_REQ and ends at the receipt of REMOVE\_NODE\_RESP. + +Figure 7-2 – DES node removed from a distributed ENUM system + +The following steps are performed: + +1. The originating DES sends a REMOVE\_NODE\_REQ message to the terminating DES to leave the distributed ENUM system. + +The REMOVE\_NODE\_REQ message should include: + +- 1) Message identifier +- 2) The originating operator identifier +- 3) The terminating operator identifier +- 4) The IP address of the originating DES +- 5) The IP address of the terminating DES +- 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + +- 7) ENUM mapping data list which includes the ENUM mapping NAPTR records +2. The originating DES starts timer T1 when it receives an ACK (100) from the terminating DES. + 3. The terminating DES removes the ENUM mapping data profile related to the originating DES and sends a REMOVE\_NODE\_RESP message to confirm the deactivation of the originating DES. The originating DES removes the ENUM mapping data profile related to the terminating DES. The REMOVE\_NODE\_RESP message should include: + - 1) Message identifier + - 2) The originating operator identifier + - 3) The terminating operator identifier + - 4) The IP address of the originating DES + - 5) The IP address of the terminating DES + - 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The result code and result description of the deactivation of the originating DES. + 4. The originating DES sends ACK (100) to the terminating DES with successful acknowledgement. + +## 7.2 ENUM data profile management + +### 7.2.1 NAPTR records added to DES + +Figure 7-3 shows the ENUM data management procedure when the originating DES adds ENUM NAPTR records and broadcasts the request of adding NAPTR record to the relevant terminating DESs. + +![Sequence diagram showing the interaction between an Originating DES and a Terminating DES for adding NAPTR records. The steps are: 1. ADD_DATA_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating (with timer T0); 3. ADD_DATA_RESP from Terminating to Originating (with timer T1); 4. ACK (100) from Originating to Terminating.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant Originating DES + participant Terminating DES + Note left of Originating DES: T0 + Originating DES->>Terminating DES: 1. ADD_DATA_REQ + Terminating DES-->>Originating DES: 2. ACK (100) + Note left of Originating DES: T1 + Terminating DES-->>Originating DES: 3. ADD_DATA_RESP + Originating DES-->>Terminating DES: 4. ACK (100) + +``` + +Q.3645(20)\_F7-3 + +Sequence diagram showing the interaction between an Originating DES and a Terminating DES for adding NAPTR records. The steps are: 1. ADD\_DATA\_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating (with timer T0); 3. ADD\_DATA\_RESP from Terminating to Originating (with timer T1); 4. ACK (100) from Originating to Terminating. + +**Figure 7-3 – NAPTR records added to DES** + +The following steps are performed: + +1. The originating DES initiates an ADD\_DATA\_REQ message to indicate to the terminating DES to add new NAPTR records into the ENUM mapping data profile of the originating DES. + +The ADD\_DATA\_REQ message should include: + +- 1) Message identifier +- 2) The originating operator identifier +- 3) The terminating operator identifier +- 4) The IP address of the originating DES +- 5) The IP address of the terminating DES + +- 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The ENUM mapping NAPTR records to be added. +2. The originating DES initiates T1 timer when it receives an ACK (100) from the terminating DES. + 3. The terminating DES adds the new NAPTR records accordingly and sends the ADD\_DATA\_RESP message to inform the originating DES whether the result of adding existing ENUM NAPTR records is successful or not. + +The ADD\_DATA\_RESP message should include: + +- 1) Message identifier + - 2) The originating operator identifier + - 3) The terminating operator identifier + - 4) The IP address of the originating DES + - 5) The IP address of the terminating DES + - 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The result code and result description of the adding ENUM mapping NAPTR records. +4. The originating DES sends ACK (100) to the terminating DES with successful acknowledgement. + +### 7.2.2 NAPTR records modified in DES + +Figure 7-4 shows the self-management procedure when the key features of existing ENUM NAPTR records were modified in originating DES and the originating DES broadcasts the request of the modification of NAPTR record to relevant terminating DESs. + +![Sequence diagram showing the interaction between an Originating DES and a Terminating DES for NAPTR record modification. The sequence is: 1. MOD_DATA_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating; 3. MOD_DATA_RESP from Terminating to Originating; 4. ACK (100) from Originating to Terminating. Timers T0 and T1 are shown on the Originating DES side.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant Originating DES + participant Terminating DES + Originating DES->>Terminating DES: 1. MOD_DATA_REQ + Note left of Originating DES: T0 starts + Terminating DES-->>Originating DES: 2. ACK (100) + Note left of Originating DES: T1 starts + Terminating DES-->>Originating DES: 3. MOD_DATA_RESP + Originating DES-->>Terminating DES: 4. ACK (100) + +``` + +Q.3645(20)\_F7-4 + +Sequence diagram showing the interaction between an Originating DES and a Terminating DES for NAPTR record modification. The sequence is: 1. MOD\_DATA\_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating; 3. MOD\_DATA\_RESP from Terminating to Originating; 4. ACK (100) from Originating to Terminating. Timers T0 and T1 are shown on the Originating DES side. + +**Figure 7-4 – NAPTR records modified in DES** + +The following steps are performed: + +1. The originating DES initiates a MOD\_DATA\_REQ message to indicate to the terminating DES to modify the existing NAPTR records of ENUM mapping data profile of the originating DES. + +The MOD\_DATA\_REQ message should include: + +- 1) Message identifier +- 2) The originating operator identifier +- 3) The terminating operator identifier +- 4) The IP address of the originating DES +- 5) The IP address of the terminating DES + +- 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The ENUM mapping NAPTR records to be modified. +2. The originating DES initiates T1 timer when it receives an ACK (100) from the terminating DES. +3. The terminating DES modifies the requested ENUM NAPTR records accordingly and sends the MOD\_DATA\_RESP message to inform the originating DES whether the result of modification of existing ENUM NAPTR records is successful or not. + +The MOD\_DATA\_RESP message should include: + +- 1) Message identifier + - 2) The originating operator identifier + - 3) The terminating operator identifier + - 4) The IP address of the originating DES + - 5) The IP address of the terminating DES + - 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The result code and result description of the modification of requested ENUM mapping NAPTR records. +4. The originating DES sends ACK (100) to the terminating DES with successful acknowledgement. + +### 7.2.3 NAPTR records removed from DES + +Figure 7-5 shows the self-management procedure when the existing ENUM NAPTR record was removed in the originating DES and the originating DES broadcasts the request of removal of NAPTR record to relevant terminating DESs. + +![Sequence diagram showing the interaction between an Originating DES and a Terminating DES for NAPTR record removal. The steps are: 1. REMOVE_DATA_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating; 3. REMOVE_DATA_RESP from Terminating to Originating; 4. ACK (100) from Originating to Terminating. Timers T0 and T1 are shown on the Originating DES side.](410562339ce067fdc6fa41940c118658_img.jpg) + +``` + +sequenceDiagram + participant Originating DES + participant Terminating DES + Note left of Originating DES: T0 + Originating DES->>Terminating DES: 1. REMOVE_DATA_REQ + Terminating DES-->>Originating DES: 2. ACK (100) + Note left of Originating DES: T1 + Terminating DES-->>Originating DES: 3. REMOVE_DATA_RESP + Originating DES->>Terminating DES: 4. ACK (100) + +``` + +Q.3645(20)\_F7-5 + +Sequence diagram showing the interaction between an Originating DES and a Terminating DES for NAPTR record removal. The steps are: 1. REMOVE\_DATA\_REQ from Originating to Terminating; 2. ACK (100) from Terminating to Originating; 3. REMOVE\_DATA\_RESP from Terminating to Originating; 4. ACK (100) from Originating to Terminating. Timers T0 and T1 are shown on the Originating DES side. + +**Figure 7-5 – NAPTR records removed from DES** + +The following steps are performed: + +- 1. The originating DES initiates a request to remove existing NAPTR records of ENUM mapping data profile of the originating DES. + +The REMOVE\_DATA\_REQ message should include: + +- 1) Message identifier +- 2) The originating operator identifier +- 3) The terminating operator identifier + +- 4) The IP address of the originating DES + - 5) The IP address of the terminating DES + - 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The ENUM mapping NAPTR records to be cancelled. +2. The originating DES initiates T1 timer when receives an ACK (100) from the terminating DES. +3. The terminating DES cancels the requested ENUM NAPTR records accordingly and sends a REMOVE\_DATA\_RESP message to indicate to the originating DES whether the result of cancellation of existing ENUM NAPTR records is successful or not. + +The REMOVE\_DATA\_RESP message should include: + +- 1) Message identifier + - 2) The originating operator identifier + - 3) The terminating operator identifier + - 4) The IP address of the originating DES + - 5) The IP address of the terminating DES + - 6) The broadcast identifier which can associate the broadcast confirmation with the broadcast indication + - 7) The result code and result description of the cancellation of requested ENUM mapping NAPTR records. +4. The originating DES sends ACK (100) to the terminating DES with successful acknowledgement. + +## 7.3 Error handling procedures + +### 7.3.1 Message acknowledgement and response timeout + +When a DES sends a request/response message which does not receive an ACK message after a T0 timeout, it should retransmit the request/response message and wait for the acknowledgement accordingly. The DES should alarm when it does not receive any ACK message after five retransmits of the request/response message. + +When a DES sends a request message which does not receive the response after a T1 timeout, it should retransmit the request message and trigger a system alarm at the meanwhile. + +### 7.3.2 Message acknowledgement errors handling + +Table 2 in clause 9 lists the values of message acknowledgement errors in the sender system and receiver system. When the receiver recognizes an error of the sender system, an ACK with value 4XX should be sent to the sender. When a receiver error occurs, an ACK with value 5XX should be sent to the sender. + +### 7.3.3 Service errors handling + +Table 3 in clause 9 lists the values of service errors for dealing with the service request. When an error occurs in dealing with a service request, a response with a result code 6XX should be sent to the sender. + +# 8 Protocol specification + +The Simple Object Access Protocol (SOAP) defined by [W3C SOAP] is used to support information transfer on the Idd interface. [W3C SOAP] shall apply except as modified by the additional + +commands, results and event codes specified in this Recommendation. Unless otherwise indicated, the procedures of [W3C SOAP] (including error handling and unrecognized information handling) are unmodified. HTTP POST over TCP is required to apply in the Idd interface in this Recommendation, as per [IETF RFC 7230], [IETF RFC 7231], [IETF RFC 7232], [IETF RFC 7235]. + +A heartbeat mechanism is required over the network layer of Idd interface to detect the status of the peer DES. During heartbeat interruption, the sending of messages shall be suspended, and all messages that have not been processed shall be automatically resent after heartbeat recovery. + +# 9 Message specification + +## 9.1 Messages + +The messages that use the Idd interface are listed in Table 1. + +**Table1 – Messages that use the Idd interface** + +| Procedures | Message name | Command code | Results | +|-------------------------------------------------|--------------------------------|------------------|----------------------------------| +| all | Acknowledgement | ACK | Success: 1XX
Failure:4XX, 5XX | +| DES node added to a distributed ENUM system | Add DES node request | ADD_NODE_REQ | – | +| | Add DES node response | ADD_NODE_RESP | Success: 200
Failure:6XX | +| DES node removed from a distributed ENUM system | Remove DES node request | REMOVE_NODE_REQ | – | +| | Remove DES node response | REMOVE_NODE_RESP | Success: 200
Failure:6XX | +| NAPTR records added to DES | Add new NAPTR records request | ADD_DATA_REQ | – | +| | Add new NAPTR records response | ADD_DATA_RESP | Success: 200
Failure:6XX | +| NAPTR records modified in DES | Modify NAPTR records request | MOD_DATA_REQ | – | +| | Modify NAPTR records response | MOD_DATA_RESP | Success: 200
Failure:6XX | +| NAPTR records removed from DES | Remove NAPTR records request | REMOVE_DATA_REQ | – | +| | Remove NAPTR records response | REMOVE_DATA_RESP | Success: 200
Failure:6XX | + +## 9.2 Message acknowledgement + +The return codes of the ACK message are listed in Table 2. + +**Table 2 – Return codes of the ACK message** + +| Return code | Description | +|-------------|----------------------------------------------------| +| 1XX | Acknowledges the message was successfully received | +| 100 | Message and system are normal | +| 101 | Repeated message ID | +| 4XX | Sender system error | + +**Table 2 – Return codes of the ACK message** + +| Return code | Description | +|--------------------|--------------------------------------------------------------------------------------------------------------| +| 400 | Message parameter length error | +| 401 | Message format error, e.g. absence of a mandatory parameter, or mandatory parameter format error | +| 402 | Undefined command code | +| 403 | Protocol version error | +| 404 | Encoding format error | +| 405 | Unrecognized or incorrect identity of the sender | +| 406 | Invalid message received when timer was expired | +| 407 | Unexpected message, e.g. receive a MOD_DATA_RESP instead of an expected ADD_DATA_RESP | +| 408 | Received a response message does not have corresponding request message | +| 409 | Received a response message with unexpected result code | +| 410 | Mismatched parameters, e.g. mismatched originating operator identifier and IP address of the originating DES | +| 5XX | Other errors | +| 500 | Abnormal receiver | +| 501 | Receiver is too busy to reply to the request | + +## 9.3 Result code of the SOAP response message + +The result codes of the SOAP response message are listed in Table 3: + +**Table 3 – Result codes of the SOAP response message** + +| Result code | Description | +|--------------------|------------------------------------------------------------------| +| 2XX | Successful response | +| 200 | The request was accepted or operation was completed successfully | +| 6XX | Service error | +| 601 | Add DES node request is rejected | +| 602 | Remove DES node request is rejected | +| 603 | Add NAPTR record request is rejected | +| 604 | Modify NAPTR record request is rejected | +| 605 | Remove NAPTR record request is rejected | +| 699 | Other undefined service errors | + +# Bibliography + +- [b-ITU-T E.164] Recommendation ITU-T E.164 (2010), *The international public telecommunication numbering plan.* +- [b-ITU-T E.212] Recommendation ITU-T E.212 (2016), *The international identification plan for public networks and subscriptions.* +- [b-GSMA PRD IR.67] GSMA PRD IR.67 (2020), *DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers.* +- [b-GSMA PRD NG.105] GSMA PRD NG.105 (2018), *ENUM Guidelines for Service Providers and IPX Providers.* +- [b-IETF RFC 5067] IETF RFC 5067 (2007), *Infrastructure ENUM Requirements.* + + + + + +## 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.3722-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-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.3722-202504-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..951d5c2c8616886249a36961724dd340fe679268 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccda10d3a328b6520dec9472628629e85baa90a8a0d8007a448e7642035cbbdf +size 78729 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ba6af6f5647b5d075e8ab5d71b4f5a63a6a3c67 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:232fd1c1887eecd72231f20c624aae43a9ec1267ad1016fd84f54f78159c3b0f +size 83165 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b47a98ea198a31f82888c8050684beca7802c2b7 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:671cd8756417fbf93bcb57b2eead196179ee0ce80c17da12036c3def035ff268 +size 46198 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b4588e946abc225da27418996242f87f4fbad08 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:170d91aac5181bda00d5aa5c41d385dedb2d669e4a62db99451d8752e3159328 +size 22023 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00c2c211cb069ddebdfc6c1d6dd817690cc34735 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74d21e46886000e93d016d5e3a64c9feecf8c943ef3c230cc90da8c02b922e05 +size 37330 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0e28623134ff0307dc6275c9e7a06664f994b51 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9dfd38f6423162acb292a1ebaefd86d056b92726f9496844bfa094307a6235a +size 65170 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93e4c71c24494c604df6fbba1adbd9c6b5917eda --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52de490beb74f1941de5941a933d84df767f2fa16b75eea6d09ae95a3f45f84d +size 35728 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ace4d0a9c6d002a4f64d589b6c6d477da2b5c74 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:649fdac0602f788b6f3e7becfddca3a41df8cdcfe0d4b9c303b686be1d414ab2 +size 69626 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fc9370b76a13c0c0bffa9d05a3b3aeeb1ec6924 --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7d331236e1839fd7e9c1f7532d25b7d143050ba13686032e5d75441f2245a18 +size 70552 diff --git a/marked/Q/T-REC-Q.3722-202504-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..532f3a5cca925b892e6d2d22400a6cacd351116d --- /dev/null +++ b/marked/Q/T-REC-Q.3722-202504-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bf7ce9b86aff76ae321a8fa0fa0c75503e1c0aed41bc217da4fab06b583677d +size 74319 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52262c8931679e01bb151f67b293d396d6117cdb --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d90a08cc0065730984886b1846023699f0a66ff0bc0b7ce0488becc4889f4ffb +size 52983 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb954c772eab7f970561bc388a82c45ffb7c0fe5 --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c202c901d84351c2d6296d2bcb1a2b25716f2afc3e5a75bf700fb87e50d6f898 +size 57057 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04f7726e74ffde94606cc70e7542dfa29920667c --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:316979ed082a17c9a6fefa7f0c1784d9483837113591ee6eefc06e81c0ca8fdd +size 104952 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8e86c97e515a41b851edee2da7dded63c61f44a --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7f55287540ca9c33a94f704e7547ddab0137a43ff4f04e0869d2063907cba4b +size 123102 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d35922a660a1566f55f1cda68881903537e943a2 --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01ef078047241dd68978bbfde6c0fb97727300a9876f24f4d8458cb82876c168 +size 45541 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..594507d7d96e134b45e79ed6f38a80f8fd3e4fea --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb2581aad6b110ee62ad73b04aa20cdff34b5ae084272bac10e0eceb7734ae73 +size 97741 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..427bb6bab839e76a42b29453b9ef2299bd33be62 --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85672760704bfb48cd9b293727fde97c5dd2bf24cd3bec0cd7471f269ead7c71 +size 33720 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64352cec16dce6002bff7f5af7c52caf03961a75 --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:348365f74c0026a8f0c1ad9cfa002f22279564597e579cc7fd5d38a3b230eb03 +size 30084 diff --git a/marked/Q/T-REC-Q.3724-202601-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f25290061daec120688cf01796530f48893c79 --- /dev/null +++ b/marked/Q/T-REC-Q.3724-202601-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f9e7092a9664a2cb8eee48795a5973f500e1381410c55ce6837178a322aa3f0 +size 76676 diff --git a/marked/Q/T-REC-Q.3902-200801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3902-200801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/Q/T-REC-Q.3902-200801-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.3902-200801-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Q/T-REC-Q.3902-200801-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3c438cdc3a3935bd7d7e4e9b5858d0de034f45f --- /dev/null +++ b/marked/Q/T-REC-Q.3902-200801-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b0cb6f0fd7ab2fb305f9225bc215b59af472a01d45184b9d000610d718d0465 +size 73173 diff --git a/marked/Q/T-REC-Q.3902-200801-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3902-200801-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..92ca14203ea0c9f2f8a67b63cec4491437ca87c8 --- /dev/null +++ b/marked/Q/T-REC-Q.3902-200801-I_PDF-E/raw.md @@ -0,0 +1,436 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3902** + +(01/2008) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Testing for NGN networks + +--- + +**Operational parameters to be monitored when +implementing NGN technical means in public +telecommunication networks** + +Recommendation ITU-T Q.3902 + +# 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.3902** + +## **Operational parameters to be monitored when implementing NGN technical means in public telecommunication networks** + +## **Summary** + +Recommendation ITU-T Q.3902 describes the main requirements of an NGN monitoring system which could be used on the model networks for NGN technical means testing and as a part of operations support system (OSS) for monitoring operation flows on the existing provider's networks. + +The basic principles of NGN monitoring system building, the common parameters to be monitored and the requirements for NGN monitoring system usages on the public telecommunication networks are given in this Recommendation. + +## **Source** + +Recommendation ITU-T Q.3902 was approved on 23 January 2008 by ITU-T Study Group 11 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Model networks, monitoring system, next generation networks (NGN), OSS, PSTN, technical means, testing. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Compatibility issues ..... | 3 | +| 7 NGN monitoring system requirements..... | 3 | +| 8 NMS common measured values ..... | 5 | +| 8.1 SS7 MS NMS measured values..... | 6 | +| 8.2 SIP MS NMS measured values ..... | 6 | +| 8.3 H.248 MS NMS measured values ..... | 7 | +| 8.4 IP MS NMS measured values..... | 7 | +| 8.5 Requirements of monitoring NGN management system..... | 7 | +| Bibliography..... | 8 | + + + +## Recommendation ITU-T Q.3902 + +## Operational parameters to be monitored when implementing NGN technical means in public telecommunication networks + +# 1 Scope + +The concept of NGN [ITU-T Y.2001] is an evolutionary tendency in public telecommunication networks development. All stages of NGN evolution could be divided into networks which are realized by PES architecture, which employs interworking between CS and PS networks and networks whose architecture is based on IMS platform with a wide range of services and different types of content. + +Independent from the evolutionary state of the networks, network providers need to implement a network monitoring system which can manage the quality of network operations and prevent faults. + +The NGN monitoring system (NMS) has to be built in accordance with the NGN functional model and has to control all protocols implemented by it. For example, the control protocol list may include: services layer (SIP, H.323, H.248, MGCP, etc.), transport layer (MPLS, BGP, EGP, Diffserv, etc.), and application layer (Diameter, SIP, AAA, Parlay, etc.). Also in accordance with NGN evolution, the NMS could include protocols implemented by CS networks (SS7, DSS1, etc.). + +NMS could be also used as part of the OSS systems and take part in fault management and in performance management systems [b-ITU-T M.3060]. The monitored parameters form the fundamental data about the different layers (LLA) of the OSS architecture [b-ITU-T M.3060]. NMS could control and compare different parameters of protocols and operational interfaces and, in accordance with [ITU-T M.3010] could control all network elements and services. + +NMS allows the control of not only stand-alone elements, but also of different types of NGN call scenarios and maintenance parameters, which could be useful for QoS testing. + +As a result, NMS is an important and a basic measurement instrument which must be provided in the NGN network. NMS must be used in the model network in accordance with [ITU-T Q.3900] and is a basic requirement for testing of NGN technical means. + +This Recommendation describes the basic requirements of an NGN monitoring system and allows to understand what parameters have to be controlled by the NMS. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T Q.752] Recommendation ITU-T Q.752 (1997), *Monitoring and measurements for Signalling System No. 7 networks*. +- [ITU-T Q.3900] Recommendation ITU-T Q.3900 (2006), *Methods of testing and model network architecture for NGN technical means testing as applied to public telecommunication networks*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 model network** [b-ITU-T Q.3901]: A network which simulates the capabilities similar to those available in telecommunication networks; it has a similar architecture and functionality and uses the same telecommunication technical means. + +**3.1.2 NGN technical means** [b-ITU-T Q.3901]: The NGN network equipment which serves as a basis for building next generation network solutions, including applications in public telecommunication networks. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 NGN monitoring systems (NMS)**: A system which is responsible for online (under payload) measurement values of the NGN protocols carried out on the different NGN strata. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|---------|----------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| ACE | Application Creation Environment | +| AS | Application Server | +| BS | Billing System | +| CS | Circuit Switching network | +| GW | Gateway | +| GW-LTE | Media gateway for Legacy Terminal Equipment | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| LLA | Logical Layered Architecture | +| MeS | Messaging Server | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MPLS | MultiProtocol Label Switching | +| MS | Media Server | +| NMS | NGN Monitoring System | +| NGN | Next Generation Network | +| NGN-IAD | NGN Integrated Access devices | +| NGN-TD | NGN Terminal Devices | +| OSS | Operations Support System | + +| | | +|------|-----------------------------------| +| PES | PSTN/ISDN Emulation Service | +| PS | Packet Switching network | +| PSTN | Public Switched Telephone Network | +| SG | Signalling Gateway | +| SIP | Session Initiation Protocol | +| TM | Technical Means | +| TNE | Transport Network Environment | + +# 5 Conventions + +None. + +# 6 Compatibility issues + +None. + +# 7 NGN monitoring system requirements + +NMS has to be present at all stages of the NGN evolution. Basically, NMS has to be implemented from a hybrid environment: interworking between CS and PS networks. In this case, networks will include a wide range of different types of technical means. In accordance with [ITU-T Q.3900], the set of TM has to include: + +- Call session control system: + - Media gateway controller (MGC) + - Proxy server SIP (PS) + - IP multimedia subsystem (IMS) +- Voice and signalling transmit system: + - Media gateway (GW) + - Signalling gateway (SG) + - Transport network environment (TNE) +- Application servers: + - Application server (AS) + - Media server (MS) + - Messaging server (MeS) + - Application creation environment (ACE) +- Management and billing system: + - Management system (MS) + - Billing system (BS) +- Access environment: + - NGN integrated access devices (NGN-IAD) + - Media gateway for legacy terminal equipment (GW-LTE) + +From its initial installations, NMS, based on PES architecture, has to include measurement modes of both CS protocols and PS protocols. As an example, NMS must allow measurement of CS signalling protocols (SS7, DSS1, etc.) and PS signalling protocols (SIP, H.323, H.248, MGCP, etc.) + +For the second step of the NMS evolution, which is based only on the IMS architecture, the NMS must implement all kinds of NGN protocols on all NGN functional architecture strata. For example, the set of protocols could include MPLS, BGP, EGP, Diffserv, Diameter, SIP, AAA, Parlay, etc. + +As a result, all NGN TM in accordance with the NMS evolution would be divided into two parts: + +### *PES NGN TM part* + +- Call session control system: + - Media gateway controller (MGC) + - Proxy server SIP (PS) +- Voice and signalling transmit system +- Management and billing system +- Access environment: + - NGN integrated access devices (NGN-IAD) + - Media gateway for legacy terminal equipment (GW-LTE) + +### *IMS NGN TM part* + +- Call session control system: + - IP multimedia subsystem (IMS) +- Voice and signalling transmit system +- Application servers +- Management and billing system +- Access environment + - NGN terminal devices (NGN-TD) + +Each part could include different types of signalling protocols. The main difference between PES NGN TM and IMS NGN TM is the functionality and type of protocols implemented on it. In the PES part, the call session control system is based on the Softswitch technologies. In this case, the common issue of PES is interworking with the legacy TDM networks. The call session control system based on IMS is, on the other hand, responsible for call control between NGN terminal devices. + +The distribution of signalling protocols by different types of TM, which are monitored by NMS, is shown below. + +### *PES NGN TM part* + +- Call session control system (H.248, MGCP, SIP, SIP-I, SIP-T, BICC) +- Voice and signalling transmit system (H.248, MGCP, SIP, SIGTRAN, SS7, R1, R2, DSS1) +- Management and billing system (AAA, Diameter, SIP) +- Access environment (MGCP, H.248, H.323, SIP) + +### *IMS NGN TM part* + +- Call session control system (SIP, SIP-I) +- Voice and signalling transmit system (SIP, SS7, R1, R2, DSS1) +- Management and billing system (AAA, Diameter, SIP) +- Access environment (SIP) + +As illustrated, the basic set of protocols must be implemented on the initial phase (PES NGN) of NMS. + +The next step of NMS evolution includes the other signalling protocols and takes into account the specific signalling requirements implemented by IMS. + +The architecture of NMS includes different types of subsystems. Figure 1 shows the basic functional architecture of NMS. The NMS consists of the following subsystems: + +- SS7 monitoring subsystem; +- SIP protocol monitoring subsystem; +- H.248 protocol monitoring subsystem; +- voice (transfer) service level monitoring subsystem; +- streaming video service level monitoring subsystem; +- service level agreements performance monitoring subsystem; +- IP information flows monitoring subsystem (RTP/RTCP protocols level); +- application server monitoring subsystem; +- hardware faults and reconfiguring procedures monitoring subsystem. + +The signalling system monitoring subsystems shall be independent from the vendor's NGN TM (for example, MGC, PS, MG, etc.). In order to gather and initially process any other subsystem information, the vendor's NGN TM management systems shall be in use. The SNMP or NetFlow may be used as the interaction protocol among the monitoring system central elements. The message format shall be specified by the Telecommunication Administrations. + +The following architecture of NMS includes the two common blocks of NMS evolutionary stages (PES and IMS architecture). + +![Figure 1 – Basic architecture of NMS. The diagram shows a central 'NMS central element' connected to a 'NGN vendor's TM management system monitoring' block. This central block is connected to four monitoring subsystems on the left: 'SS7 monitoring subsystem', 'SIP monitoring subsystem', 'H.248 monitoring subsystem', and 'Faults monitoring subsystem'. On the right, the central block is connected to six monitoring subsystems: 'Faults and reconfiguring procedures monitoring subsystem', 'IP information flows monitoring subsystem', 'Voice (transfer) service level monitoring subsystem', 'Video streaming service level monitoring subsystem', 'SLA/SLS monitoring subsystem', and 'Application server monitoring subsystem'. A label 'Q.3902(08)_F01' is at the bottom right.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` +graph TD + NMS[NMS central element] --- NGN[NGN vendor's TM management system monitoring] + NGN --- SS7[SS7 monitoring subsystem] + NGN --- SIP[SIP monitoring subsystem] + NGN --- H248[H.248 monitoring subsystem] + NGN --- Faults[Faults monitoring subsystem] + NGN --- FaultsReconfig[Faults and reconfiguring procedures monitoring subsystem] + NGN --- IPFlows[IP information flows monitoring subsystem] + NGN --- Voice[Voice (transfer) service level monitoring subsystem] + NGN --- Video[Video streaming service level monitoring subsystem] + NGN --- SLA[SLA/SLS monitoring subsystem] + NGN --- AppServer[Application server monitoring subsystem] +``` + +Q.3902(08)\_F01 + +Figure 1 – Basic architecture of NMS. The diagram shows a central 'NMS central element' connected to a 'NGN vendor's TM management system monitoring' block. This central block is connected to four monitoring subsystems on the left: 'SS7 monitoring subsystem', 'SIP monitoring subsystem', 'H.248 monitoring subsystem', and 'Faults monitoring subsystem'. On the right, the central block is connected to six monitoring subsystems: 'Faults and reconfiguring procedures monitoring subsystem', 'IP information flows monitoring subsystem', 'Voice (transfer) service level monitoring subsystem', 'Video streaming service level monitoring subsystem', 'SLA/SLS monitoring subsystem', and 'Application server monitoring subsystem'. A label 'Q.3902(08)\_F01' is at the bottom right. + +**Figure 1 – Basic architecture of NMS** + +# **8 NMS common measured values** + +As mentioned above, NMS must include the CS protocols. In this case, the monitoring system must be built in accordance with [ITU-T Q.752]. + +According to [ITU-T Q.752], the following categories regarding the measured values should be defined in the NMS based on PES and IMS solutions: + +- **fault (F):** Measurement for reporting processes and detecting problems, as well as for finding out some abnormal situations in the SS7, SIP and H.248 signalling networks, and for NGN hardware, involving its reconfiguring and restarting procedures; +- **quality (Q):** Measurement for service level parameters intended for different traffic types involving voice and video under different services; for reporting processes; for assuming measures in providing the service level guaranteed, as well as for developing an operator's policy and strategy in the field of providing a certain service level. It should be also used to have the SLA and/or SLS performed and relevant reports drawn up; +- **traffic (T):** Measurement for real-time traffic parameters based on the IP flows information for the purpose of identifying any unwanted and unauthorized traffic; studying any internal and external impact on network security; finding out any network abnormal events; defining when requesting the user-to-user, user-to-network, network-to-user interaction parameters; studying traffic changes trends; and conducting prevention management; +- **accounting (A):** Measurement to estimate the reliability of accounting data; +- **network administration and planning (N):** Measurement for SS7 and NGN networks administration including the SIP and H.248 signalling systems; make decisions on networks development and further network planning; optimizing network infrastructure enhancement investment; planning applications and services; preparing traffic data to allow planning of future networks; +- **near-real-time measurements (R):** Measurement for finding out any faults in the network. It shall be considered supplementary to the above-mentioned measurements. + +## 8.1 SS7 MS NMS measured values + +The SS7 monitoring subsystem should provide the implementation of all the functions submitted for NMS based on PES and should be compatible with [ITU-T Q.752]. According to [ITU-T Q.752], the following categories of values measured by the SS7 monitoring subsystem NMS processes are selected: + +- **fault (F):** Measurements carried out to issue reports and detect faults as well as to reveal emergency situations in the SS7 signalling system; +- **configuration (C):** Measurements carried out in the course of dynamic reconfiguration due to faults elimination or administrative actions; +- **performance (P):** Measurements carried out to estimate a stability and a reliability of the SS7 signalling network when providing services; +- **accounting (A):** Measurements carried out to ensure the reliability of accounting, by comparison with subscribers billing data; +- **network administration and planning (N):** Measurements carried out to administer the SS7 signalling network, make decisions on its development and further planning; +- **near-real-time measurements (R):** Measurements carried out to reveal emergencies in network operation; they are considered as additional to those listed above. + +## 8.2 SIP MS NMS measured values + +The SIP monitoring subsystem should provide implementation in accordance with the basic NMS architecture based on PES solutions too. As a result, the SIP monitoring subsystem has to include: + +- **fault (F):** All, except for reconfiguring and restarting processes; +- **quality (Q):** All, except for the functions concerning the SLA and/or SLS execution monitoring; +- **traffic (T):** Detecting any unauthorized traffic, analysing internal and external impact on network security, finding out abnormal situations in the network; + +- **accounting (A):** All; +- **network administration and planning (N):** All. + +## 8.3 H.248 MS NMS measured values + +The H.248 monitoring subsystem should provide implementation in accordance with the basic NMS architecture based on PES solutions too. As a result, the H.248 monitoring subsystem has to include: + +- **fault (F):** All, except for reconfiguring and restarting processes; +- **quality (Q):** All, except for the SLA and/or SLS execution; +- **network administration and planning (N):** All; +- **near-real-time measurements (R):** All. + +## 8.4 IP MS NMS measured values + +The IP monitoring subsystem should provide implementation in accordance with the basic NMS architecture based on PES and IMS solutions too. IP monitoring subsystem specifies **traffic (T)** and **network administration and planning (N)** functions. + +## 8.5 Requirements of monitoring NGN management system + +Based on the functional division of the goals concerning the next generation network operations support system (NGN OSS) networks management and operation, the following functions may be provided in the monitoring systems: + +- service level monitoring both at the network management level and the resource management level; +- problems monitoring related to problem detection and problem response. Problem detection shall be related to the resource management level, and problem response shall meet the network management level requirements; +- Service level agreement (SLA) and service level specification (SLS) implementation monitoring; +- IP information and traffic performance flows monitoring. + +Quality of service monitoring subsystem for voice transmission should ensure execution of function **Q** as per voice data transmission. + +Quality of service monitoring subsystem for video bit rates should ensure execution of function **Q** as per video data transmission. + +SLA/SLS monitoring subsystem should ensure execution of function **Q** as per SLA/SLS performance and the relevant reporting. Application server monitoring subsystem should ensure execution of functions **F** and **R**. + +Failure and reconfiguration monitoring subsystems should ensure execution of functions **F** and **R**. + +## Bibliography + +- [b-ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401 (2006), *Principles for the Management of Next Generation Networks*. +- [b-ITU-T Q.3901] Recommendation ITU-T Q.3901 (2008), *Testing topology for networks and services based on NGN technical means*. +- [b-ITU-T X.295] Recommendation ITU-T X.295 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Protocol profile test specification*. +- [b-ITU-T Y.1540] Recommendation ITU-T Y.1540 (2007), *Internet protocol data communication service – IP packet transfer and availability performance parameters*. +- [b-ITU-T Y.1541] Recommendation ITU-T Y.1541 (2006), *Network performance objectives for IP-based services*. +- [b-ITU-T Y.1542] Recommendation ITU-T Y.1542 (2006), *Framework for achieving end-to-end IP performance objectives*. +- [b-ITU-T Y.2011] Recommendation ITU-T Y.2011 (2004), *General principles and general reference model for Next Generation Networks*. +- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. +- [b-ETSI TS 188 001] ETSI TS 188 001 V1.2.1 (2006), *Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); NGN management; Operations Support Systems Architecture*. +<[http://webapp.etsi.org/workprogram/Report\\_WorkItem.asp?WKI\\_ID=23518](http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=23518)>. + + + +## 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.3903-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3903-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/Q/T-REC-Q.3903-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.3903-200810-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Q/T-REC-Q.3903-200810-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e4f5d554cc600be9f8d18b4852fdc30268c8764 --- /dev/null +++ b/marked/Q/T-REC-Q.3903-200810-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eded075cd7318eb8ccbf5c2cd6f5d505a68bf9ba69fb550941149a80ab0eb35f +size 24158 diff --git a/marked/Q/T-REC-Q.3903-200810-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3903-200810-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f61ceabbe350478373bb74bdfae02dcc80db0ed2 --- /dev/null +++ b/marked/Q/T-REC-Q.3903-200810-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9021fbe50a51409802041bff49024627d4a7fea4b2a7c28c757b7a90ae85a0a +size 38949 diff --git a/marked/Q/T-REC-Q.3903-200810-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.3903-200810-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45490cdee8ce1b557fb97827b444dd924d572a86 --- /dev/null +++ b/marked/Q/T-REC-Q.3903-200810-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:256b27568cec96e1340dd0dd529d5a98930900264e460bc7ace0eca3f96961ea +size 81857 diff --git a/marked/Q/T-REC-Q.3905-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3905-201602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ac53833558d5def527e9975e8c775c463fdfdef0 --- /dev/null +++ b/marked/Q/T-REC-Q.3905-201602-I_PDF-E/raw.md @@ -0,0 +1,1730 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3905** + +(02/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for next generation networks + +--- + +**Conformance test plan for number portability requirements defined by ITU-T Q-Suppl.4** + +Recommendation ITU-T Q.3905 + +ITU-T + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a stylized globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a bold, blue font, and below it, "International Telecommunication Union" is written in a smaller, blue font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.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.3905 + +## Conformance test plan for number portability requirements defined by ITU-T Q-Suppl.4 + +## Summary + +Recommendation ITU-T Q.3905 describes the test specifications for compliance testing against ITU-T Q-Suppl.4 "*Number portability – Capability set 1 requirements for service provider portability (All call query and Onward routing)*". There are mandatory and optional test suites which can be used for testing of: + +- different network scenarios of number portability (the onward routing and all call query); +- signaling requirements for establishing the number portability; +- interconnection among providers and call routing between ported and non-ported end-users. + +Additionally, this Recommendation gives the operational procedures for organizing a particular test event. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3905 | 2016-02-13 | 11 | 11.1002/1000/12700 | + +## Keywords + +Call query, ITU-T E.164, number portability, numbering plan, onward routing, 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. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Network Scenarios..... | 3 | +| 7 Signalling requirements and conformance test cases ..... | 4 | +| 8 Test cases for the exchange of signalling information ..... | 7 | +| Appendix A – Verifying of the configuration of network service scenarios..... | 37 | +| Bibliography..... | 41 | + + + +## Recommendation ITU-T Q.3905 + +## Conformance test plan for number portability requirements defined by ITU-T Q-Suppl.4 + +# 1 Scope + +This Recommendation describes conformance test plan for number portability requirements defined by ITU-T Q-series Recommendations – Supplement 4. The conformance test plan for number portability includes test configurations, network scenarios and test cases to verify conformance number portability solutions against requirements defined by ITU-T Q-series Recommendations – Supplement 4. + +# 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.3933] ITU-T Recommendation Q.3933 (2015), *Reference benchmarking, background traffic profiles and KPIs for VoIP and FoIP in fixed networks*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined in [b-ITU-T Q-Suppl.4]: + +**3.1.1 address:** A string or combination of decimal digits, symbols and additional information which identifies the specific termination point(s) of connection in a public network(s) or, where applicable, in interconnected private network(s). + +**3.1.2 end user's number:** The ITU-T E.164 number used by the calling party to establish a call to the end user. This number is also used for presentation services like calling line identification (CLI) and connected line identification presentation (COLP). + +**3.1.3 donor network:** The initial network where a number was located before ever being ported. + +**3.1.4 donor service provider:** The service provider from whom the number was initially ported. + +**3.1.5 originating network:** The network serving a calling end user. + +**3.1.6 portable number:** An entire E.164 number identified by an appropriate authority which is subject to number portability. + +**3.1.7 ported number:** An end user's E.164 number that has been subject to number portability. + +**3.1.8 recipient network:** The network where a number is located after being ported. + +**3.1.9 recipient service provider:** The service provider to whom the number is ported. + +**3.1.10 routing number:** A number that is derived and used by the network to route the call towards a ported number. + +**3.1.11 initiating network:** A network that requires and obtains the routing information for number portability. + +**3.1.12 originating network:** The network serving a calling end user. + +**3.1.13 transit network(s):** A network between two networks. + +## **3.2 Terms defined in this Recommendation** + +None. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------------| +| ACQ | All Call Query | +| BS | Base Station | +| CCS | Common Channel Signaling | +| CdPN | Unchanged Called Party Number | +| CLI | Calling Line Identification | +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| COLP | Connected Line Identification Presentation | +| COLR | Connected Line Identification Restriction | +| DB | Database | +| DDI | Direct Dial-in | +| DLE | Destination Local Exchange | +| HLR | Home Location Register | +| IAM | Initial Address Message | +| ISDN | Integrated Services Digital Network | +| IN | Intelligent Network | +| MOS-a | Mean Opinion Score-audio | +| MSC | Mobile Switching Centre | +| MSN | Multiple Subscriber Number | +| NP | Number Portability | +| NPCDB | Number Portability Central Database | +| NPDB | Number Portability Database | +| NPLDB | Number Portability Local Database | +| NP ID | NP Indicator | +| OLE | Originating Local Exchange | +| OR | Onward Routing | +| POI | Point of Interconnection | +| PSTN | Public Switched Telephone Network | + +| | | +|--------|-------------------------------| +| REX | Recipient Exchange | +| RNID | Recipient Network ID | +| SCP | Service Control Point | +| SMS | Short Message Service | +| SMSC | Short Message Center | +| SMS-GW | Short Message Service Gateway | +| SRF | Signaling Relay Function | +| SSP | Service Switching Point | +| TS | Transit Exchange | +| QoS | Quality of Service | + +## 5 Conventions + +None. + +# 6 Network Scenarios + +[b-ITU-T Q-Suppl.4] describes three network service scenarios for implementing number portability. In accordance with the functionality, there are two groups of service scenarios: + +- The first group is based on the method "all call query"; +- The second is based on the method "onward routing". + +The first scenario deals with the originating network/exchange which is not connected directly to number portability database (NPDB). In this case, the originating network/exchange forwards a request to the initiating network/exchange to obtain routing information. + +The second scenario is based on the fact that the initiating network/exchange also plays the role of the originating network/exchange of the calling subscriber. In this scenario, the request for routing information has to be sent to the number portability central database (NPCDB) through the donor network/exchange. + +In the third scenario donor network/exchange acts as an initiating network/exchange and requests the routing information in their number portability local database (NPLDB). + +The first and second scenarios belong to the first group which is related to "all call query", while the third scenario belongs to the second group which is related to "onward routing". + +Accordingly, the signalling transfer for the methods "all call query" and "onward routing" are shown in Figures 6-1 and 6-2 accordingly [b-ITU-T E.164 Suppl.2]. + +![Diagram illustrating the signalling transfer for the method 'all call query'. A 'Calling subscriber' (represented by a telephone icon) is connected to an 'Originating network' (represented by a circle containing a 'DB' cylinder). The 'Originating network' has a 'Lasting relation' (solid line) to a 'Transit network' (circle) and a 'Temporary relation' (dashed line) to a 'Donor network' (circle). The 'Transit network' has a 'Lasting relation' (solid line) to a 'Recipient network' (circle). The 'Donor network' has a 'Temporary relation' (dashed line) to the 'Called subscriber' (represented by a telephone icon). The 'Recipient network' has a 'Lasting relation' (solid line) to the 'Called subscriber'. Signalling messages are shown: 'a1) IAM' from the Originating network to the Transit network, 'a2) IAM' from the Transit network to the Recipient network, and 'b) IAM' from the Originating network to the Recipient network. A legend at the bottom left indicates that solid lines represent 'Lasting relation' and dashed lines represent 'Temporary relation'. The diagram is labeled 'Q.3905(16)_F6-1' in the bottom right corner.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +Diagram illustrating the signalling transfer for the method 'all call query'. A 'Calling subscriber' (represented by a telephone icon) is connected to an 'Originating network' (represented by a circle containing a 'DB' cylinder). The 'Originating network' has a 'Lasting relation' (solid line) to a 'Transit network' (circle) and a 'Temporary relation' (dashed line) to a 'Donor network' (circle). The 'Transit network' has a 'Lasting relation' (solid line) to a 'Recipient network' (circle). The 'Donor network' has a 'Temporary relation' (dashed line) to the 'Called subscriber' (represented by a telephone icon). The 'Recipient network' has a 'Lasting relation' (solid line) to the 'Called subscriber'. Signalling messages are shown: 'a1) IAM' from the Originating network to the Transit network, 'a2) IAM' from the Transit network to the Recipient network, and 'b) IAM' from the Originating network to the Recipient network. A legend at the bottom left indicates that solid lines represent 'Lasting relation' and dashed lines represent 'Temporary relation'. The diagram is labeled 'Q.3905(16)\_F6-1' in the bottom right corner. + +**Figure 6-1 – The signalling transfer for the method "all call query"** + +![Diagram illustrating the signalling transfer for the method 'onward routing'. A calling subscriber connects to an originating network, which sends an IAM (Initial Address Message) to transit network(s) (A). Transit network(s) (A) then sends an IAM to the donor network. The donor network contains a DB (Database). From the DB, two possible paths are shown: a1) IAM to transit network(s) (B), and b) IAM to the recipient network. Finally, the recipient network sends an IAM to the called subscriber.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph LR + CS[Calling subscriber] --> ON(Originating network) + ON -- IAM --> TNA(Transit network(s) (A)) + TNA -- IAM --> DN(Donor network) + DN -- "a1) IAM" --> TNB(Transit network(s) (B)) + DN -- "b) IAM" --> RN(Recipient network) + TNB -- IAM --> RN + RN --> CSub[Called subscriber] + +``` + +Diagram illustrating the signalling transfer for the method 'onward routing'. A calling subscriber connects to an originating network, which sends an IAM (Initial Address Message) to transit network(s) (A). Transit network(s) (A) then sends an IAM to the donor network. The donor network contains a DB (Database). From the DB, two possible paths are shown: a1) IAM to transit network(s) (B), and b) IAM to the recipient network. Finally, the recipient network sends an IAM to the called subscriber. + +**Figure 6-2 – The signalling transfer for the method "onward routing"** + +This test specification shows the principle used to test all service scenarios mentioned above. + +## 7 Signalling requirements and conformance test cases + +This clause provides a list of requirements and relevant test specifications for number portability defined by [b-ITU-T Q-Suppl.4]. + +**Table 1 – List of requirements and relevant testing specifications for implementing number portability** + +| Category | Ref. ITU-T Q-Suppl.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O | +|----------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----| +| LNP | R-1 | The signaling mechanisms that support number portability should not place any restrictions on the PSTN and ISDN services, including basic, supplementary and non-circuit-related based services | 8.01 | O | +| MNP/LNP | R-2 | Number portability solutions shall allow that transit network(s) be used between originating and donor/initiating networks | 8.02 | M | +| MNP/LNP | R-3 | Number portability solutions shall allow that transit network(s) be used between donor/initiating and recipient networks | | | +| MNP/LNP | R-4 | Number portability solutions shall not interfere with carrier selection | 8.03 | O | +| MNP/LNP | R-5 | Interoperability of various methods must be provided e.g., the signalling must be capable of providing interworking between onward routing and other methods | 8.04 | M | +| MNP/LNP | R-6 | NP should not result in the looping of calls or messages | 8.05 | M | +| MNP/LNP | R-7 | Outgoing international calls or messages shall be unaffected | 8.06 | O | +| MNP/LNP | R-8 | It shall be possible to signal an indication that the NP status, if available, of the portable number | 8.07 | O | + +**Table 1 – List of requirements and relevant testing specifications for implementing number portability** + +| Category | Ref. ITU-T Q-Sup.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O | +|----------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----| +| | | has been determined. The indication may be included for either ported or non-ported numbers | | | +| MNP/LNP | R-9 | Only the E.164 number (not including prefixes, etc.) should be considered eligible to be ported | 8.08 | M | +| MNP/LNP | R-10 | The entire E.164 number and not only part of it should be ported | | M | +| LNP | R-11 | Single numbers within a MSN can only be ported if a different access is provided to the ported number | 8.09 | O | +| MNP/LNP | R-12 | Groups of contiguous numbers (e.g., DDI/multiline groups) can be ported | 8.10 | M | +| MNP/LNP | R-13 | Porting of single numbers within a DDI range is not allowed | | M | +| MNP/LNP | R-14 | The privacy of the user which has ported his/her number should be guaranteed. That means that the calling/called party should not be informed that the called/calling party has ported his number | 8.11 | M | +| MNP/LNP | R-15 | Number portability should not affect the dialing procedures for calls incoming to the ported number | 8.12 | M | +| MNP/LNP | R-16 | The dialing procedures for calls outgoing from the ported customer should be the same as those of non-ported customers served by the same service provider | 8.13 | M | +| MNP/LNP | R-17 | Introducing service provider portability must not adversely affect conformance with national or international propagation and echo standards | 8.14 | O | +| MNP/LNP | R-18 | Calling line identification presentation (CLIP) supplementary service and calling line identification restriction (CLIR) supplementary service shall work in the same way as for subscribers not porting the number. For the CLIP supplementary service, if the call is originated by a calling user which has been ported, the calling line identification is the ported number. This is valid for both PSTN and ISDN subscribers | 8.15 | O | +| MNP/LNP | R-19 | Connected Line Identification Presentation (COLP) supplementary service and Connected Line Identification Restriction (COLR) supplementary service shall work in the same way as for subscribers not porting the number. For the COLP supplementary service, if the called user's number has been ported, the | 8.16 | O | + +**Table 1 – List of requirements and relevant testing specifications for implementing number portability** + +| Category | Ref. ITU-T Q-Sup.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O | +|----------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----| +| | | connected line identity presented to the calling user is the ported number. This is valid for both PSTN and ISDN subscribers | | | +| MNP/LNP | R-20 | Calls from a ported number to the emergency services should be supported by the same functionality as calls from non-ported numbers to the emergency services | 8.17 | M | +| LNP | R-21 | Variable number length must be supported | 8.18 | O | +| LNP | R-22 | Overlap signalling must be supported before and after obtaining the routing number | 8.19 | O | +| MNP/LNP | R-23 | The redirection counter, used for the diversion services, must not be stopped at redirection by a number portability procedure | 8.20 | O | +| MNP/LNP | R-24 | There shall be transparent support for NP at transit nodes | | M | +| MNP/LNP | R-25 | It shall be possible to transfer both an unchanged called party number (CdPN) and a routing number (RN) unambiguously | 8.21 | M | +| MNP/LNP | R-26 | It shall be possible to indicate one or all of the following destinations with the routing number (RN):
i) Recipient network ID (RNID) and/or;
ii) point of interconnection (POI) and/or;
iii) recipient exchange (REX).
(NOTE – This list is not exhaustive.) | 8.22 | O | +| MNP/LNP | R-27 | An indication in the forward direction to indicate a call to a ported number | 8.23 | M | +| LNP | R-28 | In an environment of number portability, calls from ported numbers must convey both logical and physical calling party information | 8.24 | O | +| MNP/LNP | R-29 | RN need not be in E.164 format | 8.25 | O | +| MNP/LNP | R-30 | For incoming international calls, the incoming gateway in the network should be considered as the originating network for number portability | 8.26 | O | +| MNP/LNP | R-31 | The number used to route the call is constructed as one of the following:
i) Concatenated address = routing number + DN (as a single piece of information);
ii) separated address = routing number and DN (as two separate pieces of information);
iii) DN only. | 8.27 | M | + +**Table 1 – List of requirements and relevant testing specifications for implementing number portability** + +| Category | Ref. ITU-T Q-Suppl.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O | +|-----------------|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------| +| LNP | R-32 | SCCP addressing based on RN for the called party should be supported | 8.28 | O | +| MNP/LNP | R-33 | The sum total of the networks involved in addressing and routing non-circuit-related messages pertaining to a ported number shall be able to detect that the number has been ported and drive the identity of the appropriate destination of the message. The division of responsibilities of this among the networks depends on the architecture chosen | 8.29 | O | +| MNP/LNP | R-34 | Number portability solutions should be backward compatible with nodes and services not updated for NP | 8.30 | M | + +NOTE 1 – M: mandatory tests, O: optional tests, R: requirements which are defined by [b-ITU-T Q-Suppl.4]. + +NOTE 2 – For simplifying and unification of testing procedures below, it is proposed to use the term "NPDB" which specifies number portability database in general. + +## 8 Test cases for the exchange of signalling information + +This clause presents the test cases which describe a signal information exchange between an operator-recipient network/exchange, an operator-donor network/exchange and a NPDB for two methods of number portability – "all call query" and "onward routing". + +The signalling information in this case includes the information of the subscriber's number, information of number porting, the routing information and indication of the subscriber party number, received from a NPDB. + +During the provision of all tests, the transport of voice and data must be analysed. The compliance with quality of service (QoS) key performance indicators (KPIs) e.g., [ITU-T Q.3933] must be ensured according to the national requirements or standards. + +NOTE – The following test cases basically describe the testing scenario for MNP services. However these cases are also possible to be used for the testing of LNP services. + +### -----Test case # 8.01----- + +**Title:** Influence of signalling exchange mechanisms on public switched telephone network (PSTN) and integrated services digital network (ISDN) services + +"The signalling mechanisms that support number portability, should not place any restrictions on the PSTN and ISDN services, including: basic, supplementary and non-circuit-related based services". + +This is an optional test suite which is out of the scope of this Recommendation. + +#### -----End of the test----- + +### -----Test case # 8.02----- + +**Title:** Transit networks and exchanges scenarios + +**Keywords:** NPDB, transit node/exchange, call routing. + +#### **Purpose:** + +Verify the various types of transit networks/exchanges for NP. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +The testing model of the network contains two network scenarios: + +- 1) in the first scenario the transit networks/exchanges are not used between an originating network/exchange and the operator-donor's network/exchange. Also, they are not used between an initiating network/exchange and the operator-recipient's. In this regard, the routing of the voice-call from a calling party to the called party is established directly between customers; +- 2) in the second scenario the transit networks/exchanges are used between an originating network/exchange and the operator-donor's network/exchange. Also, transit networks/exchanges are used between an initiating network/exchange and the operator-recipient's network/exchange. In this regard, the routing of the voice-call from a calling party to the called party is established through the transit networks/exchanges. + +#### **Test set-up:** + +The network configurations for these scenarios are presented in Figures 8-1 and 8-2 (the path of transmission of a voice-call is highlighted in green for method "all call query" and blue for method "onward routing"). Green and blue colours highlight the traffic ways in case of using the methods "all call query" and "onward routing". The route of SMS transmission is also available for the above methods. + +![Figure 8-1: Network configuration for the first scenario of the test case 8.02. This diagram shows three main network domains: 'Initiating network/exchange', 'Donor network/exchange', and 'Recipient network/exchange'. The 'Initiating network/exchange' contains a 'Calling subscriber' connected to a 'BS', which is connected to an 'MSC'. The 'MSC' is connected to an 'SMS-GW', which is connected to an 'SMSC', which is connected to an 'SRF'. The 'SRF' is connected to an 'NPCDB' and an 'HLR'. The 'Donor network/exchange' contains an 'MSC' connected to an 'SRF', which is connected to an 'NPLDB', which is connected to an 'HLR', which is connected to an 'SMSC', which is connected to an 'SMS-GW'. The 'SMS-GW' is connected to a 'Service platform' and 'Content providers'. The 'Recipient network/exchange' contains an 'MSC' connected to a 'BS' (labeled 'Called (ported) subscriber'), which is connected to an 'SRF', which is connected to an 'NPLDB', which is connected to an 'HLR', which is connected to an 'SMSC', which is connected to an 'SMS-GW'. The 'SMS-GW' is connected to the 'Service platform' and 'Content providers'. The 'Initiating network/exchange' is connected to the 'Donor network/exchange' via a blue line. The 'Donor network/exchange' is connected to the 'Recipient network/exchange' via a green line. The 'Service platform' and 'Content providers' are connected to the 'Donor network/exchange' via a blue line.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Figure 8-1: Network configuration for the first scenario of the test case 8.02. This diagram shows three main network domains: 'Initiating network/exchange', 'Donor network/exchange', and 'Recipient network/exchange'. The 'Initiating network/exchange' contains a 'Calling subscriber' connected to a 'BS', which is connected to an 'MSC'. The 'MSC' is connected to an 'SMS-GW', which is connected to an 'SMSC', which is connected to an 'SRF'. The 'SRF' is connected to an 'NPCDB' and an 'HLR'. The 'Donor network/exchange' contains an 'MSC' connected to an 'SRF', which is connected to an 'NPLDB', which is connected to an 'HLR', which is connected to an 'SMSC', which is connected to an 'SMS-GW'. The 'SMS-GW' is connected to a 'Service platform' and 'Content providers'. The 'Recipient network/exchange' contains an 'MSC' connected to a 'BS' (labeled 'Called (ported) subscriber'), which is connected to an 'SRF', which is connected to an 'NPLDB', which is connected to an 'HLR', which is connected to an 'SMSC', which is connected to an 'SMS-GW'. The 'SMS-GW' is connected to the 'Service platform' and 'Content providers'. The 'Initiating network/exchange' is connected to the 'Donor network/exchange' via a blue line. The 'Donor network/exchange' is connected to the 'Recipient network/exchange' via a green line. The 'Service platform' and 'Content providers' are connected to the 'Donor network/exchange' via a blue line. + +Q.3905(16)\_F8-1 + +**Figure 8-1 – Network configuration for the first scenario of the test case 8.02** + +![Figure 8-2: Network configuration for the second scenario of the test case 8.02. This diagram is similar to Figure 8-1 but includes two 'Transit network' blocks, each containing two 'TS' (Traffic Switch) units. The 'Initiating network/exchange' is connected to the first 'Transit network', which is connected to the 'Donor network/exchange'. The 'Donor network/exchange' is connected to the second 'Transit network', which is connected to the 'Recipient network/exchange'. The 'Service platform' and 'Content providers' are connected to the 'Donor network/exchange' via a blue line.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 8-2: Network configuration for the second scenario of the test case 8.02. This diagram is similar to Figure 8-1 but includes two 'Transit network' blocks, each containing two 'TS' (Traffic Switch) units. The 'Initiating network/exchange' is connected to the first 'Transit network', which is connected to the 'Donor network/exchange'. The 'Donor network/exchange' is connected to the second 'Transit network', which is connected to the 'Recipient network/exchange'. The 'Service platform' and 'Content providers' are connected to the 'Donor network/exchange' via a blue line. + +Q.3905(16)\_F8-2 + +**Figure 8-2 – Network configuration for the second scenario of the test case 8.02** + +#### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +#### **Test procedure:** + +- 1) the request for establishing of a voice-call connection between calling and called party has to be sent from the originating network to the operator recipient; +- 2) the traffic generated between initiating network/exchange and the operator-recipient's network/exchange should be captured by the traffic analyser. The traffic analyser should be allowed to capture the signalling exchange between an initiating network/exchange and a NPDB-side. Among others, the information should include the E.164 number and optionally its status (ported or not-ported E.164 number); +- 3) establish a voice-call between subscribers of an originating network and the operator-recipient's network; +- 4) exchange messages (e.g., SMS/MMS) between subscribers of an originating network and the operator-recipient's network; +- 5) perform measurements of signalling traffic between the originating network/exchange and the operator-donor's network/exchange (repeat steps 1-4); +- 6) perform testing for the second scenario (repeat steps 1-5). + +#### **Pass/fail criteria:** + +The test can be considered successful if the connection between subscribers was established. + +The test is considered failed if the procedures mentioned above were not successfully carried out. + +-----**End of the test**----- + +### -----**Test case # 8.03**----- + +**Title:** Number portability solutions shall not interfere with carrier selection + +The carrier selection should not influence the establishment of voice-call connection in general. + +This is an optional test suite which is out of the scope of this Recommendation. + +-----**End of the test**----- + +### -----**Test case # 8.04**----- + +**Title:** Compatibility between various methods of number portability + +**Keywords:** onward routing, all call query, the indicator of the status of number porting. + +#### **Purpose:** + +Checking the compatibility of various methods of number portability. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +Network configuration for emulating methods of "onward routing" and "all call query". + +#### Test set-up: + +![Figure 8-3: Network configuration for the test case 8.04. The diagram illustrates a complex network setup involving multiple network domains: PSDN network, Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and Originating network/exchange. Key components include Calling and Called (ported) subscribers, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, BS, SMSC, SMS-GW, Service platform, and Content providers. A blue line represents the voice call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Donor network, and finally to the Called (ported) subscriber in the Recipient network. A green line represents the signaling path, starting from the Calling subscriber in the Originating network, through the BS, MSC, SMSC, and SMS-GW, to the Service platform, and then to the Called (ported) subscriber in the Recipient network. The Donor network contains an SRF connected to an NPLDB and an HLR, which is also connected to an SMSC and SMS-GW. The Recipient network contains an SRF connected to an NPLDB and an HLR, which is also connected to an SMSC and SMS-GW. The Initiating network contains an HLR, NPCDB, and SRF connected to an MSC, which is connected to two BSs. The PSDN network contains a Calling subscriber connected to an SSP, which is connected to an SCP/DB. The Originating network contains a Calling subscriber connected to a BS, which is connected to an MSC, which is connected to an SMSC and SMS-GW, which is connected to the Service platform.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg) + +Figure 8-3: Network configuration for the test case 8.04. The diagram illustrates a complex network setup involving multiple network domains: PSDN network, Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and Originating network/exchange. Key components include Calling and Called (ported) subscribers, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, BS, SMSC, SMS-GW, Service platform, and Content providers. A blue line represents the voice call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Donor network, and finally to the Called (ported) subscriber in the Recipient network. A green line represents the signaling path, starting from the Calling subscriber in the Originating network, through the BS, MSC, SMSC, and SMS-GW, to the Service platform, and then to the Called (ported) subscriber in the Recipient network. The Donor network contains an SRF connected to an NPLDB and an HLR, which is also connected to an SMSC and SMS-GW. The Recipient network contains an SRF connected to an NPLDB and an HLR, which is also connected to an SMSC and SMS-GW. The Initiating network contains an HLR, NPCDB, and SRF connected to an MSC, which is connected to two BSs. The PSDN network contains a Calling subscriber connected to an SSP, which is connected to an SCP/DB. The Originating network contains a Calling subscriber connected to a BS, which is connected to an MSC, which is connected to an SMSC and SMS-GW, which is connected to the Service platform. + +Q.3905(16)\_F8-3 + +**Figure 8-3 – Network configuration for the test case 8.04** + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +#### Test procedure: + +- 1) establish a connection between calling and called party for the methods "onward routing" and "all call query"; + +NOTE – The voice call to the called party (the ported subscriber) for the method "onward routing" should be sent from a fixed-line telephony network and/or a network of a foreign state. The voice call to the called party (the ported subscriber) for the method "all call query" should be sent from the calling party which is served in the same region as the called party (ported number); + +- 2) all responses received from NPLDB of the operator-donor for the method "onward routing" should be monitored by the traffic analyser. These responses should contain the routing information about the operator-recipient's network and optional the indicator of the porting number status; +- 3) all responses received from NPCDB for the method "all call query" should be monitored by the traffic analyser. These responses should contain the routing information about the operator-recipient's network and optionally, the indicator of the porting number status; +- 4) after collecting all data received from steps 2-3, the data should be analysed (syntaxes of NPDB for the methods "onward routing" and "all call query"); + +- 5) check the information contained in the responses during the establishment of the connection between the calling and called party user for two types of NPDB (NPLDB and NPCDB). + +#### **Pass/fail criteria:** + +The test can be considered successful if the interaction between NPLDB and NPCDB for the methods "onward routing" and "all call query" was possible. + +The test is considered failed if the response's syntax received from NPDB was not accepted by another NPDB. + +-----End of the test----- + +### -----Test case # 8.05----- + +**Title:** Influence of the call looping to the number portability solution. + +**Keywords:** Call looping, ported number, NPDB. + +#### **Purpose:** + +- 1) verify that in absence of looping the voice call establishment or the transfer of messages based on NP is successful; +- 2) verify that with looping the voice call establishment or the transfer of messages based on NP is successful. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +Ported and non-ported number subscriber should be available. + +#### **Test set-up:** + +![Network configuration diagram for test case 8.05 showing three network domains: Originating network/exchange, Initiating network/exchange, and Recipient network/exchange. The diagram illustrates the flow of a call from a calling subscriber through various network elements including Base Stations (BS), Mobile Switching Centers (MSC), and databases (NPLDB, NPCDB, HLR, SRF). A thick green line represents the call path, showing a loop between the Initiating and Recipient networks.](1320668e9151c5144f7e3696ae57e07f_img.jpg) + +The diagram illustrates the network configuration for test case 8.05, showing three main network domains connected in series: + +- Originating network/exchange:** Contains a **Calling subscriber** connected to a **BS**, which is connected to an **MSC**. +- Initiating network/exchange:** Contains the **MSC** from the originating network, which is connected to two **BS** units. Above the **MSC** is a database block containing **HLR**, **NPCDB**, and **SRF**. +- Recipient network/exchange:** Contains an **MSC** connected to a **BS**, which is connected to a **Called (ported) subscriber**. Below the **MSC** is a database block containing **SRF**, **NPLDB**, and **HLR**. +- Donor network/exchange:** Positioned between the Initiating and Recipient networks, it contains an **MSC** connected to a database block containing **SRF**, **NPLDB**, and **HLR**. + +The call path is indicated by a thick green line, showing a loop between the Initiating network/exchange and the Recipient network/exchange via the Donor network/exchange. + +Network configuration diagram for test case 8.05 showing three network domains: Originating network/exchange, Initiating network/exchange, and Recipient network/exchange. The diagram illustrates the flow of a call from a calling subscriber through various network elements including Base Stations (BS), Mobile Switching Centers (MSC), and databases (NPLDB, NPCDB, HLR, SRF). A thick green line represents the call path, showing a loop between the Initiating and Recipient networks. + +**Figure 8-4 – Network configuration for test case 8.05** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +#### **Test procedure:** + +- 1) in the first step, the request for establishing of a connection between calling and called party (a test call/message) has to be sent (in this case called party number is the ported number); +- 2) the traffic of the request should be analysed by the traffic analyser (between NPDB and calling user). It is considered that all calls are made with the same method "all call query"; +- 3) analyse the response from step 2 (response of NPDB) which contains the indicator of the status and the routing number of the operator-recipient; +- 4) based on the response establish a connection to the served user and analyse the signalling information; +- 5) checking the establishment with looping Steps 1-4 should be repeated with looping on the calling party side. The looping is based on a wrong data base routing information. The call shall be routed to a non-existing called party user; +- 6) repeat steps 1-5 for the case when the ported user is a fixed line user. + +#### **Pass/fail criteria:** + +The test can be considered successful if in the case of call looping the call was released. + +The test is considered failed if the tests described above were not successful. + +-----**End of the test**----- + +-----**Test case # 8.06**----- + +**Title:** Outgoing international calls + +**Keywords:** Verifying the influence of number portability on outgoing international calls. + +#### **Purpose:** + +Verifying the influence of number portability on outgoing international calls. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +In this test case the ported number belongs to another country. + +#### Test set-up: + +![Figure 8-5 – Network configuration for test case 8.06. The diagram shows a complex network topology with five main network domains: International network, Long-distance network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The International network contains a Calling subscriber, SMSC, and SSP. The Long-distance network contains an SSP and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, and HLR. The Originating network/exchange contains a BS and a Calling (ported subscriber). Connections are shown between these components across the network boundaries.](83852ec55d4802521a727926336bedab_img.jpg) + +The diagram illustrates the network configuration for test case 8.06. It consists of five main network domains represented by dashed boxes: + +- International network:** Contains a **Calling subscriber**, **SMSC**, and **SSP**. +- Long-distance network:** Contains an **SSP** and **SCP/DB**. +- Initiating network/exchange:** Contains an **HLR**, **NPCDB**, **SRF**, **MSC**, and two **BS**. +- Donor network/exchange:** Contains an **MSC**, **SRF**, **NPLDB**, and **HLR**. +- Recipient network/exchange:** Contains an **MSC**, **SRF**, **NPLDB**, and **HLR**. +- Originating network/exchange:** Contains a **BS** and a **Calling (ported subscriber)**. + +Connections are shown between these components across the network boundaries. A blue line represents the path from the **Calling subscriber** in the **International network** through the **SMSC**, **SSP**, and **SCP/DB** to the **MSC** in the **Initiating network/exchange**. A green line represents the path from the **Calling (ported subscriber)** in the **Originating network/exchange** through the **BS**, **MSC**, **SRF**, **NPLDB**, and **HLR** to the **MSC** in the **Recipient network/exchange**. + +Figure 8-5 – Network configuration for test case 8.06. The diagram shows a complex network topology with five main network domains: International network, Long-distance network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The International network contains a Calling subscriber, SMSC, and SSP. The Long-distance network contains an SSP and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, and HLR. The Originating network/exchange contains a BS and a Calling (ported subscriber). Connections are shown between these components across the network boundaries. + +Figure 8-5 – Network configuration for test case 8.06 + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +#### Test procedure: + +- 1) establish a connection with number portability based on an outgoing international call using the method "all call query"; +- 2) monitor the signalling traffic between the calling originating local exchange (OLE) and the destination local exchange (DLE) which is located in the other country; +- 3) repeat steps 1 and 2 for case of using the method "onward routing"; +- 4) repeat steps 1-3 for the case when the ported user is a fixed line user. + +#### Pass/fail criteria: + +The test can be considered successful if the establishment of a connection between called and calling party (the user of the other country and user with ported number) was established successfully. + +The test is considered failed if the outgoing international call was not successful. + +-----End of the test----- + +-----Test case # 8.07----- + +**Title:** Indication of number portability + +**Keywords:** Checking the possibility of an indication of the NP status of subscriber number. + +**Purpose:** + +Verify the NP status indication of the subscriber number. + +**Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +**Preconditions and dependencies:** + +The NPDB receives requests about the NP status of called number (from an originating or initiating network). Available NPDB methods: "onward routing" or "all call query". + +**Test set-up:** + +![Figure 8-6 – Network configuration for test case 8.07. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling messages between the networks.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +The diagram illustrates the network configuration for test case 8.07, showing three main network domains connected by dashed lines: + +- Initiating network/exchange:** Contains an **Originating network/exchange** with a **Calling subscriber** connected to a **BS**, which is connected to an **MSC**. The **MSC** is connected to an **SRF**, which is connected to an **NPCDB** and an **HLR**. There are also two **BS** units connected to the **MSC**. +- Donor network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**. +- Recipient network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**. The **MSC** is connected to a **BS**, which is connected to a **Called (ported) subscriber**. + +Connections between domains: A blue line connects the **MSC** in the Initiating network to the **MSC** in the Donor network. A green line connects the **MSC** in the Donor network to the **MSC** in the Recipient network. A green line also connects the **BS** in the Initiating network to the **BS** in the Recipient network. A label **Q.3905(16)\_F8-6** is present in the bottom right corner. + +Figure 8-6 – Network configuration for test case 8.07. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling messages between the networks. + +**Figure 8-6 – Network configuration for test case 8.07** + +**Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +**Test procedure:** + +- 1) OLE sends a request to the NPLDB for establishing a connection for the method "onward routing"; +- 2) this request should be monitored by the traffic analyser on the side of the operator-donor network; +- 3) monitor the NPLDB response by the traffic analyser and verify the correctness of the received information. The call number should have the status "the ported subscriber number" and the response should contain the routing information about the operator-recipient's network/exchange; +- 4) repeat steps 1-3 for method "all call query"; + +- 5) the information received from the NPDB for both methods should be the same – the NP status should indicate that the subscriber number is a ported number. + +#### **Pass/fail criteria:** + +The test can be considered successful if the responses received from the two NPDB contained the routing information about the operator-recipient's network/exchange and information that the number was ported. + +The test is considered failed if the NP status contained incorrect information. + +-----End of the test----- + +### -----Test case # 8.08----- + +**Title:** Verifying the possibility of porting when the called party has different ITU-T E.164 number formats + +**Keywords:** Number which has been written in format E.164; number which has been written in other format; telephone prefix. + +#### **Purpose:** + +Verify the possibility of porting when the called party has different E.164 number formats (e.g., length of the number or parts of it). + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +The OLE sends a request to the NPDB. + +#### **Test set-up:** + +OLE, NPDB, DLE. + +##### **Testing equipment:** + +- 1) The NPDB-based solution. + +#### **Test procedure:** + +- 1) Send two requests with two different profiles to NPDB; + - a) the first request should contain the telephone number using E.164 format; + - b) the second request should contain the telephone number using other format (non-E.164 format); + +NOTE – The requests specified above should contain the subscriber number without prefixes and other auxiliary or information signs. + +- 2) NPDB should analyse the first request and send to recipient's side the notification message. In the second request the NPDB should send a notification message which does not correspond to E.164 format; +- 3) analyse the NPDB notification messages; +- 4) repeat steps 1-3 for the case when a part of the E.164 number is in the request; +- 5) analyse the NPDB response in both case. + +#### **Pass/fail criteria:** + +The test can be considered successful if the NPDB sends a notification identifying a failure. + +The test is considered failed if one of the criteria mentioned above does not come true. + +-----**End of the test**----- + +-----**Test case # 8.09**----- + +**Title:** Porting of MSN + +**Keywords:** Porting of MSN + +**Purpose:** + +Verifying the possibility of porting when the called party has an MSN. + +**Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +**Preconditions and dependencies:** + +The OLE sends a request to the NPDB. + +**Test set-up:** + +OLE, NPDB, DLE. + +**Testing equipment:** + +- 1) The NPDB-based solution. + +**Test procedure:** + +- 1) a request is sent to the NPDB which should contain the information of a ported MSN user; +- 2) NPDB should analyse the request and send the correct response to the OLE. + +**Pass/fail criteria:** + +The test can be considered successful if the NPDB sent a response with the correct MSN Number. + +The test is considered failed if the criteria mentioned above does not come true. + +-----**End of the test**----- + +-----**Test case # 8.10**----- + +**Title:** Verifying the possibility to port a group of numbers + +**Keywords:** The request for number porting, the request for group number porting, NPDB. + +**Purpose:** + +Verify the possibility to port a group of numbers. The possibility to port one number from the group of numbers is not allowed. + +**Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +**Preconditions and dependencies:** + +The possibility to port a group of numbers, including some partial subscriber numbers. + +#### Test set-up: + +![Figure 8-7 – Network configuration for test case 8.10. The diagram shows four network domains: Originating network/exchange, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Originating network contains a BS connected to a Calling subscriber. The Initiating network contains an MSC connected to two BSs, one of which is connected to the Calling subscriber. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR, and a BS connected to a Called (ported) subscriber. Connections are shown between the Calling subscriber and the Initiating network, between the Initiating network and the Donor network, and between the Donor network and the Recipient network. A legend indicates that blue lines represent the traffic analyser and green lines represent the NPDB-based solution. The diagram is labeled Q.3905(16)_F8-7.](73b5cce955ba9415a98791db7b0080ad_img.jpg) + +Figure 8-7 – Network configuration for test case 8.10. The diagram shows four network domains: Originating network/exchange, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Originating network contains a BS connected to a Calling subscriber. The Initiating network contains an MSC connected to two BSs, one of which is connected to the Calling subscriber. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR, and a BS connected to a Called (ported) subscriber. Connections are shown between the Calling subscriber and the Initiating network, between the Initiating network and the Donor network, and between the Donor network and the Recipient network. A legend indicates that blue lines represent the traffic analyser and green lines represent the NPDB-based solution. The diagram is labeled Q.3905(16)\_F8-7. + +**Figure 8-7 – Network configuration for test case 8.10.** + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### Test procedure: + +- 1) The first request to NPDB contains the necessary default information for porting; +- 2) The second request should contain the information of group of numbers which are already ported; +- 3) verify the group requests and the possibility of porting; +- 4) ensure that the first response is correct and the group of number could be ported; +- 5) ensure that the second response consist of the failure and the group of numbers could not be ported; +- 6) establish a connection between the pre-configured subscriber number and one of the numbers which are from the ported group of numbers; +- 7) verify the possibility of porting the single number from the group of numbers. This result should be the same as that of step 5. + +#### Pass/fail criteria: + +The test can be considered successful if the request for group number porting was correctly answered from the NPDB and it was not possible to port one number from the group of numbers. + +The test is considered failed if one of the criteria mentioned above does not come true. + +-----End of the test----- + +-----Test case # 8.11----- + +**Title:** Verifying the privacy of subscribers with ported numbers + +**Keywords:** The ported subscriber number, non-ported subscriber number, NPDB. + +#### **Purpose:** + +Verifying the possibility to save the privacy of users after porting their subscriber number. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +OLE, NPDB, DLE. + +##### **Test set-up:** + +![Figure 8-8 – Network Configuration for test case 8.11. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. This MSC is connected to the Donor network. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. This MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling between the networks, with a blue line representing the signaling path and a green line representing the data path. The diagram is labeled Q.3905(16)_F8-8.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +The diagram illustrates the network configuration for test case 8.11, showing three main network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. This MSC is connected to the Donor network. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. This MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling between the networks, with a blue line representing the signaling path and a green line representing the data path. The diagram is labeled Q.3905(16)\_F8-8. + +Figure 8-8 – Network Configuration for test case 8.11. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. This MSC is connected to the Donor network. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. This MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling between the networks, with a blue line representing the signaling path and a green line representing the data path. The diagram is labeled Q.3905(16)\_F8-8. + +**Figure 8-8 – Network Configuration for test case 8.11** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) establish the connection between non-ported and ported number using the routing information contained in the NPDB; +- 2) trace the exchange of signalling between non-ported and ported number; +- 3) ensure that the user is informed with a tone and/or announcement if the number was successfully ported. + +##### **Pass/fail criteria:** + +The test can be considered successful if the user received a tone and/or announcement in case the number was successfully ported. + +The test is considered failed if the user did not receive an announcement. + +-----End of the test----- + +-----Test case # 8.12----- + +**Title:** Influence of number portability on incoming calls + +**Keywords:** Subscriber number, ported subscriber number, NPDB. + +**Purpose:** + +Checking the correctness of reception of an incoming call on ported number. + +**Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +**Preconditions and dependencies:** + +The (voice-call) connection has to be established between non-ported number and ported number. + +**Test set-up:** + +![Figure 8-9 – Network Configuration for test case 8.12. The diagram illustrates a network configuration for testing number portability. It consists of three main network domains: PSDN network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The PSDN network contains a Calling subscriber, SSP, and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, BS, Called (ported) subscriber, SRF, NPLDB, and HLR. A blue line represents the call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. A green line represents the call path from the Calling subscriber in the Initiating network/exchange, through the BS, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. The diagram is labeled Q.3905(16)_F8-9.](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +The diagram shows a network configuration for test case 8.12. It is divided into four main sections: PSDN network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The PSDN network contains a Calling subscriber, SSP, and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, BS, Called (ported) subscriber, SRF, NPLDB, and HLR. A blue line represents the call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. A green line represents the call path from the Calling subscriber in the Initiating network/exchange, through the BS, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. The diagram is labeled Q.3905(16)\_F8-9. + +Figure 8-9 – Network Configuration for test case 8.12. The diagram illustrates a network configuration for testing number portability. It consists of three main network domains: PSDN network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The PSDN network contains a Calling subscriber, SSP, and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, BS, Called (ported) subscriber, SRF, NPLDB, and HLR. A blue line represents the call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. A green line represents the call path from the Calling subscriber in the Initiating network/exchange, through the BS, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. The diagram is labeled Q.3905(16)\_F8-9. + +**Figure 8-9 – Network Configuration for test case 8.12** + +**Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +**Test procedure:** + +- 1) establish a connection between a non-ported and ported number. The request for establishing a connection between subscribers should be sent to NPDB for obtaining the routing information; + +- 2) verify that the NPDB sends the correct called party number in response to the OLE. The response should contain the routing information about the served called party (a ported subscriber number); +- 3) establish a connection between calling and called party; +- 4) ensure that the voice/data channel is correctly established; +- 5) repeat steps 1-4 for case when the calling party is a fixed telephone subscriber. + +#### **Pass/fail criteria:** + +The test can be considered successful if the voice call connection to the ported number was successfully established. + +The test is considered failed if one of the criteria mentioned above does not come true. + +-----End of the test----- + +-----Test case # 8.13----- + +**Title:** Number portability on outgoing calls + +**Keywords:** Subscriber number, ported subscriber number, NPDB. + +#### **Purpose:** + +Ensure that the calls from a ported number can be provided to fixed and mobile telephone numbers. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +The calling user is a ported number. + +##### **Test set-up:** + +![Network configuration diagram for test case 8.13 showing three network domains: Recipient network/exchange, Cellular network, and PSDN network. The Recipient network contains an MSC, BS, SRF, NPDB, and HLR, with a 'Calling subscriber' and 'Calling (ported) subscriber'. The Cellular network contains an HLR, NPDB, SRF, MSC, BS, and a 'Called subscriber'. The PSDN network contains an SSP, SCP/DB, and a 'Called subscriber'. Connections are shown between the calling subscribers in the Recipient network and the called subscribers in both the Cellular and PSDN networks, passing through the MSC and SSP respectively.](db7ae70402c81d140ae7df14b002e057_img.jpg) + +The diagram illustrates the network configuration for test case 8.13. It consists of three main network domains enclosed in dashed boxes: + +- Recipient network/exchange:** Contains an MSC (Mobile Switching Center), BS (Base Station), SRF (Service Resource Function), NPDB (Number Portability Database), and HLR (Home Location Register). It includes a 'Calling subscriber' and a 'Calling (ported) subscriber' connected to the BS. +- Cellular network:** Contains an HLR, NPDB, SRF, MSC, BS, and a 'Called subscriber' connected to the BS. +- PSDN network:** Contains an SSP (Service Switching Point), SCP/DB (Service Control Point/Database), and a 'Called subscriber' connected to the SSP. + +Connections are shown between the calling subscribers in the Recipient network and the called subscribers in both the Cellular and PSDN networks. The call from the 'Calling (ported) subscriber' in the Recipient network is routed through its MSC, then to the SSP in the PSDN network, and finally to the 'Called subscriber' in the PSDN network. Another call from the 'Calling (ported) subscriber' is routed through its MSC to the MSC in the Cellular network, and finally to the 'Called subscriber' in the Cellular network. + +Q.3905(16)\_F8-10 + +Network configuration diagram for test case 8.13 showing three network domains: Recipient network/exchange, Cellular network, and PSDN network. The Recipient network contains an MSC, BS, SRF, NPDB, and HLR, with a 'Calling subscriber' and 'Calling (ported) subscriber'. The Cellular network contains an HLR, NPDB, SRF, MSC, BS, and a 'Called subscriber'. The PSDN network contains an SSP, SCP/DB, and a 'Called subscriber'. Connections are shown between the calling subscribers in the Recipient network and the called subscribers in both the Cellular and PSDN networks, passing through the MSC and SSP respectively. + +**Figure 8-10 – Network configuration for test case 8.13** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) establish a call from a ported user to a non-ported mobile user; +- 2) establish a connection between calling and called party; +- 3) ensure that the voice/data channel is correctly established; +- 4) repeat steps 1-3 for case when the calling party is a fixed telephone subscriber. + +#### **Pass/fail criteria:** + +The test can be considered successful if the call from a ported call to a non-ported number was successfully established. + +The test is considered failed if one of the criteria mentioned above does not come true. + +-----End of the test----- + +-----Test case # 8.14----- + +**Title:** Influence of service provider portability on national or international radio resource allocation + +"Introducing service provider portability must not adversely affect conformance with national or international propagation and echo standards". + +The NPDB solution (in general) is a separate information system which does not have access to mechanisms of the radio resource's allocation and echo protection. It has no negative influence on allocation of national and international radio resources. + +This is an optional test suite which is out of the scope of this Recommendation. + +-----End of the test----- + +-----Test case # 8.15----- + +**Title:** Verifying the determination of ported number using the CLIP/CLIR service + +**Keywords:** NPDB, CLIP/CLIR. + +#### **Purpose:** + +Verify that the presentation and restriction of the calling party number is according to the CLIP/CLIR Recommendation for ported and not ported numbers + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +The non-ported and the ported user have been subscribed to the Supplementary services CLIP/CLIR. + +##### Test set-up: + +![Figure 8-11 – Network configuration for test case 8.15](2bacc162a73d75c43a7f90715832bd13_img.jpg) + +The diagram shows a network configuration for test case 8.15, involving three main network/exchange areas: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, BS, and a Calling subscriber. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, BS, SRF, NPLDB, HLR, and a Called (ported) subscriber. A PSDN network at the top contains a Calling subscriber, SSP, and SCP/DB. A blue line represents the call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Initiating network/exchange, then to the MSC in the Donor network/exchange, and finally to the MSC in the Recipient network/exchange. A green line represents the call path from the Calling subscriber in the Initiating network/exchange, through the BS, to the MSC in the Initiating network/exchange, then to the MSC in the Donor network/exchange, and finally to the MSC in the Recipient network/exchange. The diagram is labeled Q.3905(16)\_F8-11. + +Figure 8-11 – Network configuration for test case 8.15 + +**Figure 8-11 – Network configuration for test case 8.15** + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### Test procedure: + +- 1) establish a call from a ported to a non-ported user who subscribed to the supplementary service CLIP; +- 2) after establishing a connection, verify that the CLIP information was correctly transferred to the called user; +- 3) repeat steps 1-2 for the non-ported case; +- 4) repeat steps 1-3 establishing a call from a non-ported to a ported user who subscribed to CLIP; +- 5) repeat steps 1-4 for CLIR service. In this case the information concerning the calling party should not be displayed on the screen of the terminal device of the called party. + +##### Pass/fail criteria: + +The test can be considered successful if the verification of the supplementary service CLIP/CLIR was successful. + +The test is considered failed if the presentation and restriction of the calling party number was not provided in accordance with the CLIP/CLIR recommendation for ported and non-ported numbers. + +End of the test + +### -----Test case # 8.16----- + +**Title:** Influence of number portability on COLP/COLR service + +**Keywords:** NPDB, COLP/COLR + +#### **Purpose:** + +Verify that the connected number can be used according to the COLP/COLR recommendation for ported and not ported numbers. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +The non-ported and the ported user have been subscribed to the Supplementary services COLP/COLR. + +#### **Test set-up:** + +![Figure 8-12 – Network configuration for test case 8.16. The diagram shows a network architecture with four main components: Initiating network/exchange, Donor network/exchange, Transit network, and Recipient network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Transit network contains two TS (Transit Switches). The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and two BSs. A Calling subscriber is connected to the Initiating network/exchange. A Called (ported) subscriber and a Called subscriber are connected to the Recipient network/exchange. The diagram illustrates the flow of signaling and data between these components, with a specific call path highlighted in blue and green lines. The text 'Q.3905(16)_F8-12' is visible in the bottom right corner of the diagram area.](17a1ba23b641c01871b08f0a4f08ef48_img.jpg) + +Figure 8-12 – Network configuration for test case 8.16. The diagram shows a network architecture with four main components: Initiating network/exchange, Donor network/exchange, Transit network, and Recipient network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Transit network contains two TS (Transit Switches). The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and two BSs. A Calling subscriber is connected to the Initiating network/exchange. A Called (ported) subscriber and a Called subscriber are connected to the Recipient network/exchange. The diagram illustrates the flow of signaling and data between these components, with a specific call path highlighted in blue and green lines. The text 'Q.3905(16)\_F8-12' is visible in the bottom right corner of the diagram area. + +**Figure 8-12 – Network configuration for test case 8.16** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) establish a connection between non-ported number (which has been subscribed to COLP supplementary service) and the ported number which has been subscribed to the service of the calling user "A"; +- 2) ensure that the information of the subscriber number "B" is displayed correctly on the terminal device of calling party "A"; +- 3) repeat steps 1-2 for the case when the called party is a non-ported number; + +- 4) repeat steps 1-3 for the case when the called party number has been subscribed to COLR service. + +#### **Pass/fail criteria:** + +The test can be considered successful if COLP and COLR services worked correctly. + +The test is considered failed if the COLP/COLR information was not transferred correctly. + +-----End of the test----- + +-----Test case # 8.17----- + +**Title:** Influence of number portability on calls from ported numbers to emergency services + +**Keywords:** Emergency services, ported subscriber number, NPDB. + +#### **Purpose:** + +Verify that an outgoing call from a ported number can be provided successfully to an emergency service. + +#### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +The emergency call will be provided from a ported subscriber number. + +##### **Test set-up:** + +![Network configuration diagram for test case 8.17. It shows a 'Recipient network/exchange' on the left containing an MSC, BS, SRF, NPLDB, and HLR. Two subscribers, 'Calling subscriber' and 'Calling (ported) subscriber', are connected to the BS. A 'PSDN network' on the right contains an SSP, SCP/DB, and 'Number of emergency services'. The MSC is connected to the SSP. A call path is shown from the ported subscriber through the BS, MSC, SRF, NPLDB, HLR, and then to the SSP and emergency services. A reference code Q.3905(16)_F8-13 is present at the bottom right of the diagram.](8dd83c9e4e123aaaf3d521db1c4c416d_img.jpg) + +Q.3905(16)\_F8-13 + +Network configuration diagram for test case 8.17. It shows a 'Recipient network/exchange' on the left containing an MSC, BS, SRF, NPLDB, and HLR. Two subscribers, 'Calling subscriber' and 'Calling (ported) subscriber', are connected to the BS. A 'PSDN network' on the right contains an SSP, SCP/DB, and 'Number of emergency services'. The MSC is connected to the SSP. A call path is shown from the ported subscriber through the BS, MSC, SRF, NPLDB, HLR, and then to the SSP and emergency services. A reference code Q.3905(16)\_F8-13 is present at the bottom right of the diagram. + +**Figure 8-13 – Network configuration for test case 8.17** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) establish a connection between a ported number and number of the emergency service (for example, number 112); +- 2) monitor the signalling with the traffic analyser during the call establishment; +- 3) repeat steps 1-2 for the case when the calling party number is a non-ported number; + +- 4) ensure that the call routing from the ported number to the number of the emergency service is the same as the call from the non-ported number. + +#### **Pass/fail criteria:** + +The test can be considered successful if the call routing from the ported number to the number of the emergency service was established successfully. + +The test is considered failed if the connection establishment between ported number and the number of the emergency service failed or the ported number had limited access to the emergency service (e.g long delay, etc.). + +-----**End of the test**----- + +-----**Test case # 8.18**----- + +**Title:** Support of variable length of number + +"Variable number length must be supported". + +This is an optional test which is out of the scope of this Recommendation. + +-----**End of the test**----- + +-----**Test case # 8.19**----- + +**Title:** Support of overlap signalling before and after obtaining the routing number + +"Overlap signaling must be supported before and after obtaining the routing number". + +This is an optional test which is out of the scope of this Recommendation. + +-----**End of the test**----- + +-----**Test case # 8.20**----- + +**Title:** Influence on the redirection counter (during call forwarding) during the NP procedure + +**Keywords:** Readdressing, NPDB, ported subscriber, transit network/exchange. + +#### **Purpose:** + +Verify if the redirection counter will increase during the number portability procedure. + +##### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +##### **Preconditions and dependencies:** + +The ported number has subscribed and activated call forwarding unconditional (CFU). + +##### Test set-up: + +![Figure 8-14 – Network configuration for test case 8.20. The diagram shows a network architecture with four main network/exchange blocks: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and Originating network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains a TS, MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains a TS, MSC, SRF, NPLDB, and HLR. The Originating network/exchange contains a BS and a Calling subscriber. The Recipient network/exchange also contains a Called (ported) subscriber, Number B, and a Called subscriber. The diagram illustrates the flow of traffic and signaling between these components, with a specific call path highlighted in blue and green. A small note 'Q.3905(16)_F8-14' is visible in the bottom right corner of the diagram area.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +Figure 8-14 – Network configuration for test case 8.20. The diagram shows a network architecture with four main network/exchange blocks: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and Originating network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains a TS, MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains a TS, MSC, SRF, NPLDB, and HLR. The Originating network/exchange contains a BS and a Calling subscriber. The Recipient network/exchange also contains a Called (ported) subscriber, Number B, and a Called subscriber. The diagram illustrates the flow of traffic and signaling between these components, with a specific call path highlighted in blue and green. A small note 'Q.3905(16)\_F8-14' is visible in the bottom right corner of the diagram area. + +**Figure 8-14 – Network configuration for test case 8.20** + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### Test procedure: + +- 1) the calling user "A" is calling user B which is not ported and has activated CFU. The redirection counter has the value 1; +- 2) activate NP for user B; +- 3) the calling user "A" is calling user B which is ported and has activated CFU. The redirection counter has the value 1. + +##### Pass/fail criteria: + +The test can be considered successful if the redirection counter was not influenced by number portability procedure. + +The test is considered failed if the criteria mentioned above does not come true. + +-----**End of the test**----- + +-----**Test case # 8.21**----- + +**Title:** The unambiguous transmission of called number and routing network number + +**Keywords:** Unchanged called party number (CdPN), routing number, a NPDB. + +#### Purpose: + +Ensure that the transmission of the CdPN and the routing number has not been changed during the NP procedure. + +##### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +##### **Preconditions and dependencies:** + +The called party number is a ported subscriber number. + +##### **Test set-up:** + +The testing configuration corresponds on Figure 8-4. + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) establish a connection between non-ported and ported subscriber number; +- 2) check the CdPN on the NPDB side; +- 3) verify the response of the NPDB which contains the routing information; +- 4) ensure that the CdPN has not been changed; +- 5) repeat steps 1-4 for the case if a transit network/exchange has been used between the operator-donor and the operator-recipient network/exchange. + +##### **Pass/fail criteria:** + +The test can be considered successful if the routing number of the operator-recipient network/exchange and the CdPN were transferred correctly. + +The test is considered failed if one of the criteria mentioned above does not come true. + +-----**End of the test**----- + +-----**Test case # 8.22**----- + +**Title:** Support of various types of indications + +**Keywords:** routing number, point of interconnection, recipient exchange. + +#### **Purpose:** + +Verify that that the transport of the following types of indication are supported: + +- 1) recipient network ID (RNID) and/or; +- 2) point of interconnection (POI) and/or; +- 3) recipient exchange (REX). + +##### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +##### **Preconditions and dependencies:** + +The exchange and point of association to a network should be selected. + +##### Test set-up: + +![Figure 8-15 – Network configuration for test case 8.22. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a BS and Calling subscriber, connected to an MSC. The MSC is connected to an SRF, which is connected to an HLR and an NPCDB. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC in the Recipient network is connected to a BS and a Called (ported) subscriber. The MSC in the Initiating network is connected to the MSC in the Donor network, which is connected to the MSC in the Recipient network. The diagram is labeled Q.3905(16)_F8-15.](85e2327652d513a7fee8fdbf97ad06f1_img.jpg) + +The diagram illustrates the network configuration for test case 8.22, showing three main network domains connected in series: + +- Initiating network/exchange:** Contains an **Originating network/exchange** with a **BS** and **Calling subscriber**. This is connected to an **MSC**. The **MSC** is connected to an **SRF**, which is connected to an **HLR** and an **NPCDB**. +- Donor network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**. +- Recipient network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**. The **MSC** is connected to a **BS** and a **Called (ported) subscriber**. + +The connections between the domains are as follows: The **MSC** in the **Initiating network/exchange** is connected to the **MSC** in the **Donor network/exchange**, which is connected to the **MSC** in the **Recipient network/exchange**. The diagram is labeled **Q.3905(16)\_F8-15**. + +Figure 8-15 – Network configuration for test case 8.22. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a BS and Calling subscriber, connected to an MSC. The MSC is connected to an SRF, which is connected to an HLR and an NPCDB. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC in the Recipient network is connected to a BS and a Called (ported) subscriber. The MSC in the Initiating network is connected to the MSC in the Donor network, which is connected to the MSC in the Recipient network. The diagram is labeled Q.3905(16)\_F8-15. + +**Figure 8-15 – Network configuration for test case 8.22** + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### Test procedure: + +- 1) establish a call between the calling user "A" and the ported user "B"; +- 2) monitor the signalling between OLE and DLE; +- 3) verify that the request for establishment contains the routing information about the operator-recipient's network/exchange; +- 4) analyse the response from NPDB. The response should contain the following items: + - the information about the ported calling party number; + - the routing number and the presence of the identifier of the operator-recipient's network; + - the operator-recipient exchange; + - the point of interconnection. + +##### Pass/fail criteria: + +The test can be considered successful if the parameters describe above were transferred correctly. + +The test can be considered unsuccessful if the parameters describe above were not transferred correctly. + +-----**End of the test**----- + +-----**Test case # 8.23**----- + +**Title:** Indication of ported number in the forward direction + +**Keywords:** Call indication, NPDB, the ported subscriber number. + +#### **Purpose:** + +Checking of the ported number indication in the forward direction + +##### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +##### **Preconditions and dependencies:** + +The test configuration contains the OLE, the operator-recipient's network/exchange and transit network/exchange. + +##### **Test set-up:** + +![Figure 8-16 – Network configuration for test case 8.23. The diagram shows a network configuration with four main components: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and a central Transit network. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and a BS connected to a 'Called (ported) subscriber'. The Transit network is a shaded area between the Donor and Recipient networks. A 'Calling subscriber' is connected to a BS in the Initiating network/exchange. The diagram is labeled Q.3905(16)_F8-16.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +The diagram illustrates the network configuration for test case 8.23. It is divided into four main sections: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and a central Transit network. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and a BS connected to a 'Called (ported) subscriber'. The Transit network is a shaded area between the Donor and Recipient networks. A 'Calling subscriber' is connected to a BS in the Initiating network/exchange. The diagram is labeled Q.3905(16)\_F8-16. + +Figure 8-16 – Network configuration for test case 8.23. The diagram shows a network configuration with four main components: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and a central Transit network. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and a BS connected to a 'Called (ported) subscriber'. The Transit network is a shaded area between the Donor and Recipient networks. A 'Calling subscriber' is connected to a BS in the Initiating network/exchange. The diagram is labeled Q.3905(16)\_F8-16. + +**Figure 8-16 – Network configuration for test case 8.23** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) receive the routing information from the response of NPDB; +- 2) establish a connection between calling and called party (the ported number); +- 3) monitor the traffic during call forwarding from an OLE to the operator-recipient's network/exchange, with usage of a transit network/exchange; +- 4) analyse traces and verify that the indication of the operator-recipient exchange/network is correct; + +##### **Pass/fail criteria:** + +The test can be considered successful if the connection between subscribers was established using the received routing information. + +The test is considered failed if the connection was not established and/or the indication of the network was incorrect. + +-----End of the test----- + +-----Test case # 8.24----- + +**Title:** Verifying the possibility of the physical and logical information transmission in the case when the calling party is ported + +"In an environment of number portability, calls from ported numbers must convey both logical and physical calling party information". + +This is an optional test suite which is out the scope of this Recommendation. + +-----End of the test----- + +-----Test case # 8.25----- + +**Title:** Usage of different formats of routing numbers + +**Keywords:** Routing number, operator-recipient's network/exchange, operator-donor network/exchange. + +**Purpose:** + +Usage of different formats of routing numbers. + +**Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +**Preconditions and dependencies:** + +The called party number is a ported subscriber number. + +**Test set-up:** + +![Figure 8-17 – Network configuration for test case 8.25. The diagram shows a call flow from an originating network/exchange to a recipient network/exchange via a donor network/exchange. The originating network contains a calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an HLR and an NPCDB. The donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC is connected to a BS, which is connected to a called (ported) subscriber. The call flow is indicated by a thick green line connecting the calling subscriber to the called subscriber.](2c532a9bb51e081048d718316f509294_img.jpg) + +The diagram illustrates the network configuration for test case 8.25, showing the flow of a call from an originating network to a recipient network through a donor network. The components and connections are as follows: + +- Originating network/exchange:** Contains a **Calling subscriber** connected to a **BS** (Base Station). The **BS** is connected to an **MSC** (Mobile Switching Center). The **MSC** is connected to an **SRF** (Service Routing Function). The **SRF** is connected to an **NPLDB** (Number Portability Lookup Database) and an **HLR** (Home Location Register). The **HLR** is also connected to an **NPCDB** (Number Portability Control Database). +- Donor network/exchange:** Contains an **MSC** connected to an **SRF**. The **SRF** is connected to an **NPLDB** and an **HLR**. +- Recipient network/exchange:** Contains an **MSC** connected to an **SRF**. The **SRF** is connected to an **NPLDB** and an **HLR**. The **MSC** is connected to a **BS**, which is connected to a **Called (ported) subscriber**. + +The call flow is indicated by a thick green line connecting the **Calling subscriber** to the **Called (ported) subscriber**, passing through the **MSC** in the originating network, the **MSC** in the donor network, and the **MSC** in the recipient network. + +Q.3905(16)\_F8-17 + +Figure 8-17 – Network configuration for test case 8.25. The diagram shows a call flow from an originating network/exchange to a recipient network/exchange via a donor network/exchange. The originating network contains a calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an HLR and an NPCDB. The donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC is connected to a BS, which is connected to a called (ported) subscriber. The call flow is indicated by a thick green line connecting the calling subscriber to the called subscriber. + +**Figure 8-17 – Network configuration for test case 8.25** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) OLE has sent the request to the NPDB in order to establish a connection between calling (non-ported) party and called (ported) party; +- 2) NPDB should generate the response containing the routing information about the operator-recipient's network and information about called party number; +- 3) monitor and analyse the NPDB response. + +The response should contain the information about: + +- routing number; +- national number; + +these numbers should be written using the E.164 format; + +- 4) the routing number should contain the code number of the operator-recipient's network and, optionally, the code of exchange of the given network; +- 5) ensure that it is possible to use the syntax which is different from E.164 format, namely: the possibility of usage of hexadecimal digits, as in a range 0-F, and in a range 0-9. + +##### **Pass/fail criteria:** + +The test can be considered successful if an additional format (e.g., Hex) was supported. + +The test is considered failed if the usage of the additional syntax was impossible. + +**End of the test** + +**Test case # 8.26** + +**Title:** The incoming gateway in the network for incoming international calls should be considered as the OLE + +**Keywords:** Network of the foreign country, the international gateway, OLE, the ported number. + +#### **Purpose:** + +Verify that the incoming gateway for international call could be used as OLE during the NP procedure. + +##### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +##### **Preconditions and dependencies:** + +The international gateway fulfil the functions of an OLE. + +##### Test set-up: + +![Figure 8-18 – Network configuration for test case 8.26. The diagram shows a call path from a calling subscriber in an international network, through a long-distance network, to an originating network/exchange, then through a donor network/exchange, and finally to a recipient network/exchange where the called (ported) subscriber is located. The path includes various network elements like SMSC, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, NPLDB, and BS. The call is established via two routes: one direct (blue line) and one via the donor network (green line).](cc72b4769f15fe33763025416c1e274d_img.jpg) + +The diagram illustrates the network configuration for test case 8.26. It shows a call path from a calling subscriber in an international network, through a long-distance network, to an originating network/exchange, then through a donor network/exchange, and finally to a recipient network/exchange where the called (ported) subscriber is located. The path includes various network elements like SMSC, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, NPLDB, and BS. The call is established via two routes: one direct (blue line) and one via the donor network (green line). + +Q.3905(16)\_F8-18 + +Figure 8-18 – Network configuration for test case 8.26. The diagram shows a call path from a calling subscriber in an international network, through a long-distance network, to an originating network/exchange, then through a donor network/exchange, and finally to a recipient network/exchange where the called (ported) subscriber is located. The path includes various network elements like SMSC, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, NPLDB, and BS. The call is established via two routes: one direct (blue line) and one via the donor network (green line). + +**Figure 8-18 – Network configuration for test case 8.26** + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### Test procedure: + +- 1) establish a connection between a user in a foreign state (calling party) and ported subscriber (called party) for the methods "all call query" and "onward routing"; +- 2) monitor this establishment for both number portability methods; +- 3) repeat steps 1-2 for the case when the ported called party is in the foreign country. + +##### Pass/fail criteria: + +The test can be considered successful if the connection between the foreign state and the ported subscriber number was successfully established. + +The test is considered failed if the connection was not established. + +-----End of the test----- + +-----Test case # 8.27----- + +**Title:** Different call routing formats + +**Keywords:** Routing number, operator-recipient's network/exchange, operator-donor's network/exchange. + +#### Purpose: + +Ensure that the following types of number formats can be used during the call establishment: + +- 1) concatenated address (the routing and called party number are forwarded together); +- 2) separated address (the routing and called party number are forwarded separately); + +3) only the called party has been transferred. + +##### **Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +##### **Preconditions and dependencies:** + +The "all call query" method is used for NP. + +##### **Test set-up:** + +![Figure 8-19 – Number configuration for test case 8.27. The diagram illustrates a network configuration across four dashed boxes representing different network/exchange domains. 1. Originating network/exchange (bottom left): Contains a 'Calling subscriber' connected to a 'BS' (Base Station), which is connected to an 'MSC' (Mobile Switching Center). 2. Initiating network/exchange (top left): Contains the 'MSC' from the originating network, an 'HLR' (Home Location Register), an 'NPCDB' (Number Portability Database), and an 'SRF' (Service Request Function). The 'SRF' is connected to the 'NPCDB' and the 'HLR'. 3. Donor network/exchange (middle): Contains an 'MSC', an 'SRF', an 'NPLDB' (Number Portability Lookup Database), and an 'HLR'. The 'SRF' is connected to the 'NPLDB' and the 'HLR'. 4. Recipient network/exchange (top right): Contains an 'MSC', an 'SRF', an 'NPLDB', and an 'HLR'. The 'SRF' is connected to the 'NPLDB' and the 'HLR'. A 'Called (ported) subscriber' is connected to a 'BS' in this network. A thick green line represents the call path: Calling subscriber -> BS -> MSC (Originating) -> MSC (Initiating) -> SRF (Initiating) -> NPCDB -> SRF (Initiating) -> HLR (Initiating) -> MSC (Initiating) -> MSC (Donor) -> SRF (Donor) -> NPLDB (Donor) -> SRF (Donor) -> HLR (Donor) -> MSC (Donor) -> MSC (Recipient) -> SRF (Recipient) -> NPLDB (Recipient) -> SRF (Recipient) -> HLR (Recipient) -> MSC (Recipient) -> BS -> Called (ported) subscriber. A small label 'Q.3905(16)_F8-19' is in the bottom right corner of the diagram area.](107da2e3495b2f24352c9e3b26ec4841_img.jpg) + +Figure 8-19 – Number configuration for test case 8.27. The diagram illustrates a network configuration across four dashed boxes representing different network/exchange domains. 1. Originating network/exchange (bottom left): Contains a 'Calling subscriber' connected to a 'BS' (Base Station), which is connected to an 'MSC' (Mobile Switching Center). 2. Initiating network/exchange (top left): Contains the 'MSC' from the originating network, an 'HLR' (Home Location Register), an 'NPCDB' (Number Portability Database), and an 'SRF' (Service Request Function). The 'SRF' is connected to the 'NPCDB' and the 'HLR'. 3. Donor network/exchange (middle): Contains an 'MSC', an 'SRF', an 'NPLDB' (Number Portability Lookup Database), and an 'HLR'. The 'SRF' is connected to the 'NPLDB' and the 'HLR'. 4. Recipient network/exchange (top right): Contains an 'MSC', an 'SRF', an 'NPLDB', and an 'HLR'. The 'SRF' is connected to the 'NPLDB' and the 'HLR'. A 'Called (ported) subscriber' is connected to a 'BS' in this network. A thick green line represents the call path: Calling subscriber -> BS -> MSC (Originating) -> MSC (Initiating) -> SRF (Initiating) -> NPCDB -> SRF (Initiating) -> HLR (Initiating) -> MSC (Initiating) -> MSC (Donor) -> SRF (Donor) -> NPLDB (Donor) -> SRF (Donor) -> HLR (Donor) -> MSC (Donor) -> MSC (Recipient) -> SRF (Recipient) -> NPLDB (Recipient) -> SRF (Recipient) -> HLR (Recipient) -> MSC (Recipient) -> BS -> Called (ported) subscriber. A small label 'Q.3905(16)\_F8-19' is in the bottom right corner of the diagram area. + +**Figure 8-19 – Number configuration for test case 8.27** + +##### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### **Test procedure:** + +- 1) OLE should send the request to the NPDB for establishment of a connection between calling and called party (ported subscriber number) using the concatenated address; +- 2) the NPDB response should contain the information of the operator-recipient network and the number of the called party; +- 3) transport of this response should be monitored; +- 4) establish the connection between subscribers using the information which was received from NPDB; +- 5) Repeat steps 1-4 using the separated address format; +- 6) Repeat steps 1-4 when only the called party number has been transferred. + +##### **Pass/fail criteria:** + +The test can be considered successful if all three formats can be used for the call establishment. + +The test is considered failed if one of the types could not be used for the call establishment. + +-----**End of the test**----- + +-----**Test case # 8.28**----- + +**Title:** SCCP addressing + +"SCCP addressing based on RN for the called party should be supported". + +This is an optional test which is out of the scope of this Recommendation. + +-----**End of the test**----- + +-----**Test case # 8.29**----- + +**Title:** Identification of ported number for message transfer + +"The sum total of the networks involved in addressing and routing non-circuit-related messages pertaining to a ported number shall be able to detect that the number has been ported and drive the identity of the appropriate destination of the message. The division of responsibilities of this among the networks depend on the architecture chosen". + +This is an optional test which is out of the scope of this Recommendation. + +-----**End of the test**----- + +-----**Test case # 8.30**----- + +**Title:** Verifying that the exchanges which does not support NP can establish a connection without NPDB + +**Keywords:** Network node, network exchange, NPDB, the ported subscriber. + +**Purpose:** + +Verify that the exchanges which does not support NP can establish a connection without NPDB. + +**Standard (criteria):** + +Clause 8 of [b-ITU-T Q-Suppl.4]. + +**Preconditions and dependencies:** + +The exchange does not support the number portability solution. + +##### Test set-up: + +![Figure 8-20 – Network configuration for test case 8.30. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber and BS, connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. A Called (ported) subscriber and BS are connected to the Recipient network's MSC. A blue line represents the call path from the Calling subscriber to the Called (ported) subscriber. A green line represents the call path from the Calling subscriber to the Donor network's MSC. A red line represents the call path from the Donor network's MSC to the Recipient network's MSC. A yellow line represents the call path from the Recipient network's MSC to the Called (ported) subscriber. The diagram is labeled Q.3905(16)_F8-20.](4ae4505e885586e481a3ad3bff5198b7_img.jpg) + +The diagram illustrates the network configuration for test case 8.30, showing three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber and BS, connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. A Called (ported) subscriber and BS are connected to the Recipient network's MSC. A blue line represents the call path from the Calling subscriber to the Called (ported) subscriber. A green line represents the call path from the Calling subscriber to the Donor network's MSC. A red line represents the call path from the Donor network's MSC to the Recipient network's MSC. A yellow line represents the call path from the Recipient network's MSC to the Called (ported) subscriber. The diagram is labeled Q.3905(16)\_F8-20. + +Figure 8-20 – Network configuration for test case 8.30. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber and BS, connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. A Called (ported) subscriber and BS are connected to the Recipient network's MSC. A blue line represents the call path from the Calling subscriber to the Called (ported) subscriber. A green line represents the call path from the Calling subscriber to the Donor network's MSC. A red line represents the call path from the Donor network's MSC to the Recipient network's MSC. A yellow line represents the call path from the Recipient network's MSC to the Called (ported) subscriber. The diagram is labeled Q.3905(16)\_F8-20. + +Figure 8-20 – Network configuration for test case 8.30 + +##### Testing equipment: + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +##### Test procedure: + +- 1) establish a connection between the ported and non-ported number and monitor the forwarding of this call; +- 2) emulate a node/exchange which does not support the NP procedure. This exchange should be between the initiating network/exchange and the operator-recipient's network/exchange; +- 3) repeat step 1 for the case when the emulated node/exchange is used as an initiating network/exchange for calling party; +- 4) the call from the given exchange should be forwarded to the nearest exchange/node of the initiating network which supports NP and monitor the forwarding of this call. + +##### Pass/fail criteria: + +The test can be considered successful if the nodes/exchanges which are not supporting portability are forwarded to a network which supports NP. + +The test is considered failed if the criteria mentioned above does not come true. + +-----End of the test----- + +## Appendix A + +### Verifying of the configuration of network service scenarios + +(This appendix does not form an integral part of this Recommendation.) + +This appendix contains the test cases which are verifying "all call query" and "onward routing" procedures. + +NOTE – The test cases presented below correspond to mobile number portability procedures defined in [b-ITU-T Q-Suppl.4]. However, these NP tests can also be for local number portability, including all network(s)/exchange(s) of the fixed network(s) which are used for the voice-call routing. + +-----**Test case # A.01**----- + +**Title:** Standard procedure for the "all call query" method + +**Keywords:** Routing information, originating network/exchange, initiating network/exchange, NPDB. + +#### **Purpose:** + +Verify the routing information procedure for ported numbers for the "all call query" method. + +#### **Standard (criteria):** + +Clauses 6.1.2, 6.2.1.1 of [b-ITU-T Q-Suppl.4]. + +#### **Preconditions and dependencies:** + +The originating network/exchange (OLE) which is the host of the calling party, is not connected to NPDB. The called subscriber number is ported and stored in the operator-recipient's network. + +#### **Test set-up:** + +The network configuration should be allowed to transmit a voice/data call from an initiating network/exchange to an operator-recipient's network/exchange (the path is highlighted in green). All measured data have to be collected by protocol analyser at the reference points (see Figure A.1), which are highlighted in green. The network configuration is presented in Figure A.1. + +![Figure A.1 – Network configuration for test case A.01. The diagram illustrates a call flow across three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. A calling subscriber in an 'Originating network/exchange' connects via a BS to an MSC in the 'Initiating network/exchange'. This MSC is linked to an SRF, which connects to an HLR and an NPCDB. The call path (indicated by a thick green line with nodes) then traverses to an MSC in the 'Donor network/exchange' (linked to its own SRF, NPLDB, and HLR) and finally to an MSC in the 'Recipient network/exchange' (also linked to an SRF, NPLDB, and HLR). From the recipient MSC, the call goes through a BS to the 'Called (ported) subscriber'. Dashed boxes group the components of each network exchange. A small label 'Q.3905(16)_FA.1' is at the bottom right of the diagram.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +Figure A.1 – Network configuration for test case A.01. The diagram illustrates a call flow across three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. A calling subscriber in an 'Originating network/exchange' connects via a BS to an MSC in the 'Initiating network/exchange'. This MSC is linked to an SRF, which connects to an HLR and an NPCDB. The call path (indicated by a thick green line with nodes) then traverses to an MSC in the 'Donor network/exchange' (linked to its own SRF, NPLDB, and HLR) and finally to an MSC in the 'Recipient network/exchange' (also linked to an SRF, NPLDB, and HLR). From the recipient MSC, the call goes through a BS to the 'Called (ported) subscriber'. Dashed boxes group the components of each network exchange. A small label 'Q.3905(16)\_FA.1' is at the bottom right of the diagram. + +**Figure A.1 – Network configuration for test case A.01** + +#### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +#### **Test procedure:** + +- 1) a request from OLE for establishment of the connection to the NPDB has to be sent; +NOTE – In the case when the originating network/exchange has no access to NPDB, the call should be forwarded to the initiating network/exchange to verify whether the number of the called party belongs to an operator-recipient's network; +- 2) after establishing a test call, the request from the given network/exchange has to be sent to the NPDB to verify if the number of the called party is ported. Also, the request should provide information to obtain the routing information; +- 3) in case the called party number is ported, the NPDB should inform the initiating network/exchange and an operator-recipient's network/exchange with the routing information which is needed for further call establishment. In addition, the information might include the optional indicators of the ported number (e.g., NP ID, the name of the operator-donor, the name of the operator-recipient, number, etc.). In this regard, the test suite should be allowed to send the reply to the called party providing the necessary information for call routing; +- 4) In case the called party number is not ported the voice-call should be routed as a normal E.164 number. The relevant reply about the status of this number has to be provided from NPDB; +- 5) after obtaining the routing information (mostly based on the test call) the operator-recipient's network/exchange should route the voice-call, using received routing information. + +#### **Pass/fail criteria:** + +The test can be considered successful if the called party number was determined correctly by using NPDB and the connection between calling party and called party was established. + +The test is considered failed if one of the criteria mentioned above does not come true. + +-----**End of the test**----- + +-----**Test case # A.02**----- + +**Title:** Special procedures for call routing using the "onward routing" method + +**Keywords:** Routing information, initiating network/exchange, operator-donor network/exchange. + +**Purpose:** + +Verify the special procedures for call routing using the "onward routing". + +**Standard (criteria):** + +Clause 6.2.2 of [b-ITU-T Q-Suppl.4]. + +**Preconditions and dependencies:** + +Two network configurations are possible: + +- 1) the initiating network/exchange and the operator-donor network/exchange are not united in a network/exchange or a part of each other; +- 2) the initiating network/exchange and the operator-donor network/exchange are united in a network/exchange. + +**Test set-up:** + +The network configuration allow to transmit a voice call from an initiating network/exchange to an operator-recipient network/exchange (the path is highlighted in blue). All measured data have to be collected by traffic analyzer at the reference point, which are highlighted in green. The network configuration is presented on Figure A.2. + +![Figure A.2 – Network configuration for test case A.02. The diagram shows a call path from an originating network/exchange to a recipient network/exchange via a donor network/exchange. The path is highlighted in blue, and reference points for traffic analysis are highlighted in green. The originating network/exchange contains a calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The donor network/exchange contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The recipient network/exchange contains an MSC connected to a BS, which is connected to a called (ported) subscriber. The MSC is also connected to an SRF, which is connected to an NPLDB and an HLR. The call path is highlighted in blue, and the reference points are highlighted in green.](08e8bbb2a063a3935a0c649b39ade125_img.jpg) + +The diagram illustrates the network configuration for test case A.02. It consists of three main network domains: the Originating network/exchange, the Initiating network/exchange, the Donor network/exchange, and the Recipient network/exchange. The call path is highlighted in blue, and reference points for traffic analysis are highlighted in green. + +- Originating network/exchange:** Contains a Calling subscriber connected to a BS. The BS is connected to the Initiating network/exchange. +- Initiating network/exchange:** Contains an MSC connected to the Donor network/exchange. The MSC is also connected to an SRF, which is connected to an NPCDB and an HLR. The MSC is connected to two BSs, one of which is connected to the Originating network/exchange. +- Donor network/exchange:** Contains an MSC connected to the Recipient network/exchange. The MSC is also connected to an SRF, which is connected to an NPLDB and an HLR. +- Recipient network/exchange:** Contains an MSC connected to a BS, which is connected to a Called (ported) subscriber. The MSC is also connected to an SRF, which is connected to an NPLDB and an HLR. + +The call path is highlighted in blue, and the reference points are highlighted in green. The diagram is labeled Q.3905(16)\_FA.2. + +Figure A.2 – Network configuration for test case A.02. The diagram shows a call path from an originating network/exchange to a recipient network/exchange via a donor network/exchange. The path is highlighted in blue, and reference points for traffic analysis are highlighted in green. The originating network/exchange contains a calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The donor network/exchange contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The recipient network/exchange contains an MSC connected to a BS, which is connected to a called (ported) subscriber. The MSC is also connected to an SRF, which is connected to an NPLDB and an HLR. The call path is highlighted in blue, and the reference points are highlighted in green. + +**Figure A.2 – Network configuration for test case A.02** + +#### **Testing equipment:** + +- 1) the traffic analyser; +- 2) the NPDB-based solution. + +#### **Test procedure:** + +- 1) The test steps for the first configuration of circuit network are similar to standard procedure (which was described in previous test procedure); +- 2) The test steps for the second configuration of circuit network will be the following: + - a) A request for establishing a connection between calling and called party (a test call) from an initiating network/exchange has to be sent; +NOTE – In the case when the initiating network/exchange and an operator donor network/exchange is a united network/exchange, the call should not be forwarded for porting verifying to the initiating network/exchange. + - b) in this case if the called party number is in an operator-donor network (unported subscriber number) the connection between calling and called party should be established without any additional steps. The request for establishing a connection should be directly forwarded to the called party number side (in our case – to the operator-donor network/exchange); + - c) in a case when the called party number is not provided by an operator-donor network/exchange (ported subscriber number) then the test call cannot be served by the given initiating network/exchange. The call will be forwarded to another initiating network/exchange or NPDB; + - d) after obtaining the routing information from another initiating network/exchange of NPDB-side, the operator-recipient network/exchange should route the voice call, using received routing information, to the called party in order to establish the voice call connection between subscribers. + +#### **Pass/fail criteria:** + +The test can be considered successful if the connection between calling party and called party was established correctly. + +Test is considered failed if the establishment of a connection between the calling party and called party was impossible. + +-----End of the test----- + +# Bibliography + +- [b-ITU-T E.164 Suppl.2] Recommendation ITU-T E.164 – Supplement 2 (2014), *Number portability*. +- [b-ITU-T Q-Suppl.3] Recommendation ITU-T Q-Suppl.3 (1988), *Number portability – Scope and capability set 1 architecture*. +- [b-ITU-T Q-Suppl.4] Recommendation ITU-T Q-Suppl.4 (1998), *Number portability – Capability set 1 requirements for service provider portability (All call query and Onward routing)*. + + + + + +## 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.3906.1-201010-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..61932cbce2c05414a6f14541cf5d6b78d75ac513 --- /dev/null +++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/raw.md @@ -0,0 +1,1337 @@ + + +# **ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **Q.3906.1** + +(10/2010) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Testing for NGN networks + +--- + +**Test scenarios and catalogue for testing fixed +broadband access networks using a model +network – Part I** + +Recommendation ITU-T Q.3906.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.3906.1** + +# **Test scenarios and catalogue for testing fixed broadband access networks using a model network – Part I** + +## **Summary** + +Recommendation ITU-T Q.3906.1 describes main requirements to broadband testing on fixed networks. It could be useful as a basic Recommendation for interoperability testing on fixed broadband networks based on model networks. + +This Recommendation describes the principle of testing and describes the detailed procedures for testing and the expected results. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.3906.1 | 2010-10-14 | 11 | + +## **Keywords** + +Model networks, next generation networks (NGN), public switched telephone network (PSTN), testing. + +## 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 | 1 | +| 3.1 Terms defined elsewhere | 1 | +| 4 Abbreviations and acronyms | 1 | +| 5 Conventions | 3 | +| 6 General requirements for testing BBA networks | 3 | +| 6.1 Testing scheme | 3 | +| 6.2 Testing program | 4 | +| 6.3 Methods of testing | 11 | + + + +## Recommendation ITU-T Q.3906.1 + +# Test scenarios and catalogue for testing fixed broadband access networks using a model network – Part I + +# 1 Scope + +This Recommendation defines the list of checks to be performed during the functionality and interoperability testing of fixed broadband access (BBA) networks for PPPoE technology in operator and model networks. + +The Recommendation defines the tasks for testing BBA networks and provides a list of tests for a model network, while indicating the reason for choosing a type of network for specified test groups. + +# 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.3900] Recommendation ITU-T Q.3900 (2006), *Methods of testing and model network architecture for NGN technical means testing as applied to public telecommunication networks*. +- [ITU-T Q.3901] Recommendation ITU-T Q.3901 (2008), *Testing topology for networks and services based on NGN technical means*. +- [ITU-T Q.3903] Recommendation ITU-T Q.3903 (2008), *Formalized presentation of testing results*. +- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 model network** [ITU-T Q.3900]: A network which simulates the capabilities similar to those available in present telecommunication networks, has a similar architecture and functionality and uses the same telecommunication technical means. + +**3.1.2 NGN technical means** [ITU-T Q.3900]: The NGN basic equipment which serves as a basis for building new generation network solutions, including for application in public telecommunication networks. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +ABG-FE Access Border Gateway Functional Entity + +ADSL Asymmetric Digital Subscriber Line + +| | | +|----------|----------------------------------------------------------| +| AG | Access Gateway | +| AGC | Access Gateway Controller | +| AGC-FE | Access Gateway Control Functional Entity | +| AN | Access Node | +| ARP | Address Resolution Protocol | +| AS | Applications Server | +| AS-FE | Application Support Functional Entity | +| ATM | Asynchronous Transfer Mode | +| BBA | Broadband Access | +| BGC-FE | Breakout Gateway Control Functional Entity | +| BRAS | Broadband Remote Access Server | +| DHCP | Dynamic Host Configuration Protocol | +| DSLAM | Digital Subscriber Line Access Multiplexer | +| EAS | Ethernet Aggregation Switch | +| HG | Home Gateway | +| IBC-FE | Interconnection Border gateway Control Functional Entity | +| IBG-FE | Interconnection Border Gateway Functional Entity | +| ICMP | Internet Control Message Protocol | +| I-CSC-FE | Interrogating Call Session Control Functional Entity | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| KB | Knowledge Base | +| LID | Light-Weight Identity protocol | +| MAC | Media Access Control | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MGC-FE | Media Gateway Controller Functional Entity | +| MGCP | Media Gateway Control Protocol | +| MSAN | Multi-Service Access Node | +| NGN | Next Generation Network | +| NIT | Network Integration/Interconnection Testing | +| OLT | Optical Line Terminal | +| P-CSC-FE | Proxy Call Session Control Functional Entity | +| PON | Passive Optical Network | +| PPPoE | Point-to-Point Protocol over Ethernet | +| PS | Proxy-Server (SIP) | +| PSTN | Public Switched Telephone Network | + +| | | +|----------|------------------------------------------------| +| PVC | Permanent Virtual Circuit | +| QoS | Quality of Service | +| S-CSC-FE | Serving Call Session Control Functional Entity | +| SCTP | Stream Control Transmission Protocol | +| SG | Signalling gateway | +| SG-FE | Signalling Gateway Functional Entity | +| SIP | Session Initiation Protocol | +| SNMP | Simple Network Management Protocol | +| SMTP | Simple Mail Transfer Protocol | +| SP | Signalling Point | +| SS7 | Signalling System 7 | +| SSH | Secure Shell | +| STP | Signalling Transfer Point | +| TCP | Transmission Control Protocol | +| TE | Terminal Equipment | +| TLS | Transport Layer Security | +| TM | Technical Means | +| UDP | User Datagram Protocol | +| UNI | User Network Interface | +| URI | Uniform Resource Identifier | +| VDSL | Very-high data rate Digital Subscriber Line | +| VLAN | Virtual Local Area Network | + +# **5 Conventions** + +None. + +# **6 General requirements for testing BBA networks** + +There are several testing stages in the functional and interoperability testing of broadband access (BBA) networks and technical means (TM). These stages include the functional testing of the BBA networks and interoperability testing of the BBA TM. The results of each of these tests shall be delivered to the global database in a format that conforms to [ITU-T Q.3903]. + +## **6.1 Testing scheme** + +Tests are executed on the model network described in [ITU-T Q.3900]. The generalized testing scheme is shown in Figure 1. + +![Figure 1 – General scheme for BBA network testing. The diagram illustrates a symmetrical network testbed. At the top, two identical branches (A and B) consist of BRAS, AAA, DHCP, and PPPoE servers connected to an Ethernet Aggregation Switch. Each switch connects to three local hosts (Host_1, Host_2, Host_3) and an IP Network Core (Core-1 for A, Core-2 for B). Between the cores is a Network QoS parameters emulator. Below the cores, an IP Protocols Analyzer connects to a central 'Patch-panels and cross-cable equipment' block. This central block also connects to two DSLAM/MSAN/EAS/OLT units (A and B). Each DSLAM unit connects to three Home Gateways (HG1, HG2, HG3), and each HG connects to three hosts (Host_1, Host_2, Host_3).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph TD + subgraph Branch_A + BRAS_A --- EAS_A[Ethernet Aggregation Switch] + AAA_A --- EAS_A + DHCP_A --- EAS_A + PPPoE_A --- EAS_A + H1A[Host_1] --- EAS_A + H2A[Host_2] --- EAS_A + H3A[Host_3] --- EAS_A + EAS_A --- Core1[IP Network Core-1] + end + + subgraph Branch_B + BRAS_B --- EAS_B[Ethernet Aggregation Switch] + AAA_B --- EAS_B + DHCP_B --- EAS_B + PPPoE_B --- EAS_B + H1B[Host_1] --- EAS_B + H2B[Host_2] --- EAS_B + H3B[Host_3] --- EAS_B + EAS_B --- Core2[IP Network Core-2] + end + + Core1 --- QoS[Network QoS parameters emulator] --- Core2 + + Core1 --- IPA[IP Protocols Analyzer] + Core2 --- IPA + IPA --- PP[Patch-panels and cross-cable equipment] + + PP --- DSLAM_A[DSLAM_A/MSAN_A/EAS_A/OLT_A] + PP --- DSLAM_B[DSLAM_B/MSAN_B/EAS_B/OLT_B] + + subgraph Access_A + DSLAM_A --- HG1A[HG1] + DSLAM_A --- HG2A[HG2] + DSLAM_A --- HG3A[HG3] + HG1A --- H1_1[Host_1] + HG1A --- H1_2[Host_2] + HG1A --- H1_3[Host_3] + end + + subgraph Access_B + DSLAM_B --- HG1B[HG1] + DSLAM_B --- HG2B[HG2] + DSLAM_B --- HG3B[HG3] + HG1B --- H2_1[Host_1] + HG1B --- H2_2[Host_2] + HG1B --- H2_3[Host_3] + end + +``` + +Figure 1 – General scheme for BBA network testing. The diagram illustrates a symmetrical network testbed. At the top, two identical branches (A and B) consist of BRAS, AAA, DHCP, and PPPoE servers connected to an Ethernet Aggregation Switch. Each switch connects to three local hosts (Host\_1, Host\_2, Host\_3) and an IP Network Core (Core-1 for A, Core-2 for B). Between the cores is a Network QoS parameters emulator. Below the cores, an IP Protocols Analyzer connects to a central 'Patch-panels and cross-cable equipment' block. This central block also connects to two DSLAM/MSAN/EAS/OLT units (A and B). Each DSLAM unit connects to three Home Gateways (HG1, HG2, HG3), and each HG connects to three hosts (Host\_1, Host\_2, Host\_3). + +**Figure 1 – General scheme for BBA network testing** + +## 6.2 Testing program + +### 6.2.1 Programme for testing the basic functionality of the BBA network + +Table 1 shows the program of basic functional testing for BBA networks and indicates information about the functions tested for each group of tests. + +**Table 1 – Programme of basic functionality testing for BBA networks** + +| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier | +|---|---------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------| +| 1 | VLAN tags processing functionality checking | DSLAM/ MSAN | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Multi PVC model used in UNI interface | T2 | DSLAM_VLAN_01 | +| | | | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Single PVC/Untagged model used in UNI interface | T2 | DSLAM_VLAN_02 | + +**Table 1 – Programme of basic functionality testing for BBA networks** + +| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier | +|---|----------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------| +| | | | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Single PVC/VLAN tagged model used in UNI interface | T2 | DSLAM_VLAN_03 | +| | | | VLAN (S-Tag/C-Tag) tag pair assignment to Ethernet frames, transmitted in upstream direction | T2 | DSLAM_VLAN_04 | +| | | | TLS user port configuration, assuring transparent transmission of initial IEEE 802.1Q tags via communication network, as assigned by a user | T2 | DSLAM_VLAN_05 | +| | | | Configuration of a list of Ethernet frame types transmitted in upstream direction for a determined user port | T2 | DSLAM_VLAN_06 | +| | | EAS | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Untagged UNI architecture use on access stratum | T2 | EAS_VLAN_01 | +| | | | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of VLAN tagged UNI architecture use on access stratum | T2 | EAS_VLAN_02 | +| | | | VLAN (S-Tag/C-Tag) tag pair assignment to Ethernet frames, transmitted in upstream direction | T2 | EAS_VLAN_03 | + +**Table 1 – Programme of basic functionality testing for BBA networks** + +| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier | +|---|------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------| +| | | | TLS user port configuration, assuring transparent transmission of initial IEEE 802.1Q tags via communication network, as assigned by a user | T2 | EAS_VLAN_04 | +| | | | Configuration of a list of Ethernet frame types transmitted in upstream direction for a specific user port | T2 | EAS_VLAN_05 | +| | | BRAS | S-Tag tags assignment to unmarked Ethernet frames, transmitted downstream | T5 | BRAS_VLAN_01 | +| | | | S-Tag/C-Tag (QinQ) tag pair assignment to unmarked Ethernet frames, transmitted downstream | T5 | BRAS_VLAN_02 | +| 2 | QoS control functionality checking | DSLAM/MSAN | Priority bit marking in Ethernet frames, transmitted in upstream direction without IEEE 802.1Q tags assigned by user equipment | T2 | DSLAM_QOS_01 | +| | | | Priority bit marking in Ethernet frames, transmitted in upstream direction with IEEE 802.1Q tags assigned by customer equipment | T2 | DSLAM_QOS_02 | + +**Table 1 – Programme of basic functionality testing for BBA networks** + +| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier | +|---|--------------------------------------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------| +| | | EAS | Priority bit marking in Ethernet frames, transmitted in upstream direction without IEEE 802.1Q tags assigned by customer equipment | T2 | EAS_QOS_01 | +| | | | Priority bit marking in Ethernet frames, transmitted in upstream direction with 802.1Q tags assigned by customer equipment | T2 | EAS_QOS_02 | +| 3 | Security protection functionality checking | DSLAM/MSAN | Broadcast message blocking both in upstream and downstream directions | T2 | DSLAM_SEC_01 | +| | | | Limiting the number of MAC-addresses of sources connected to one user port | T2 | DSLAM_SEC_02 | +| | | | Ethernet frame filtering on the basis of MAC-source addresses and MAC-destination addresses | T2 | DSLAM_SEC_03 | +| | | | Detecting replicated MAC-user addresses and resorting to a relevant mechanism of such situation remedy | T2 | DSLAM_SEC_04 | +| | | EAS | Broadcast messages blocking both in upstream and downstream directions | T2 | EAS_SEC_01 | +| | | | Limiting the number of MAC-addresses of sources connected to one user port | T2 | EAS_SEC_02 | +| | | | Ethernet frame filtering on the basis of MAC-source addresses and MAC-destination addresses | T2 | EAS_SEC_03 | + +**Table 1 – Programme of basic functionality testing for BBA networks** + +| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier | +|---|-----------------------------------------------------------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------| +| | | | Detecting replicated MAC-user addresses and resorting to a relevant mechanism of such situation remedy | T2 | EAS_SEC_04 | +| | | BRAS | Preventing malicious user attacks due to IP-source address spoofing | T5 | BRAS_SEC_01 | +| 4 | Subscriber line identification functionality checking | DSLAM/ MSAN | Functioning as a second-level DHCP Relay Agent and ensuring identification of DHCP subscriber connection points using data option (option 82) of DHCP protocol | T4 | DSLAM_LID_01 | +| | | | Functioning as a PPPoE Intermediate Agent ensuring identification of subscriber lines | T4 | DSLAM_LID_02 | +| | | EAS | Functioning as a second-level DHCP Relay Agent and ensuring identification of DHCP subscriber connection points using data option (option 82) of DHCP protocol | T4 | EAS_LID_01 | +| | | | Functioning as a PPPoE Intermediate Agent ensuring identification of customer equipment | T4 | EAS_LID_02 | +| 5 | Statistics acquisition, monitoring and control functionality checking | DSLAM/ MSAN | Remote monitoring using communication network control system including SNMP protocol | T2 | DSLAM_MNG_01 | +| | | EAS | Remote monitoring using communication network control system including SNMP protocol | T2 | EAS_MNG_01 | + +**Table 1 – Programme of basic functionality testing for BBA networks** + +| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier | +|---|-----------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------| +| | | BRAS | Remote monitoring checking with the use of communication network control system including SNMP protocol | T5 | BRAS_MNG_01 | +| 6 | Multicast mode support functionality checking | DSLAM/ MSAN | Simultaneous connection of several users to one multicast group without subsequent load increase on the DSLAM/MSAN network interfaces | T2 | DSLAM_MC_01 | +| | | | Limiting the total number of multicast groups to which a user can be connected at a time | T2 | DSLAM_MC_02 | +| | | | Limiting the list of multicast groups available to a specific user | T2 | DSLAM_MC_03 | +| | | EAS | Simultaneous connection of several users to one multicast group without subsequent load increase on EAS network interfaces | T2 | EAS_MC_01 | +| | | | Limiting the total number of multicast groups to which a user can be connected at the same time | T2 | EAS_MC_02 | +| | | | Limiting the total number of multicast groups to which a user can be connected at the same time | T2 | EAS_MC_03 | +| | | BRAS | Limiting the total number of multicast groups transmitted within S-VLAN (MC-VLAN) | T5 | BRAS_MC_01 | +| | | | Grownup statistics for multicast traffic for each MC-VLAN and for each multicast group | T5 | BRAS_MC_02 | + +**Table 1 – Programme of basic functionality testing for BBA networks** + +| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier | +|---|-----------------------------------|----------------------------------------------|-----------------------------------------------------------------------------------|----------------------------------------|-----------------| +| 7 | Access policy control and account | BRAS | Establishing PPPoE user sessions | T5 | BRAS_ACC_01 | +| | | | Establishing IPoE (DHCP) user sessions | T5 | BRAS_ACC_02 | +| | | | Functioning as a LNS server during termination of L2TP user tunnels | T5 | BRAS_ACC_03 | +| | | | Account of rendered broadband access services for users initiating PPPoE sessions | T5 | BRAS_ACC_04 | +| | | | Disconnecting a user upon expiration of established quota of received data volume | T5 | BRAS_ACC_05 | +| | | | Limiting a bandwidth that is assigned to a user for data receiving/transmission | T5 | BRAS_ACC_06 | + +### 6.2.2 Programme for testing BBA TM interoperability + +Table 2 shows the programme for testing the interoperability of the BBA TM of the different vendors that compose the BBA network under test, instructions for the tests, purpose of the tests and lists the corresponding tests. + +**Table 2 – Program of interoperability testing for BBA TM** + +| # | Group of tests | Purpose | Test identifier | +|---|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| 1 | Interoperability testing of AN (access nodes) and BRAS of different vendors | DSLAM/MSAN/EAS/OLT access nodes equipment is compatible with BRAS equipment from different vendors including processing of DHCP option 82 and PPPoE TAG which are installed with the use of AN equipment | AN-BRAS_COMP_01
AN-BRAS_COMP_02
AN-BRAS_COMP_03 | +| 2 | Interoperability testing of AN equipment and home gateway equipment from different vendors | Equipment installed in user premises (home gateways, business routers, modems) is fully compatible with DSLAM/MSAN/OLT access nodes equipment from different vendors | DSL_COMP_01 | + +## 6.3 Methods of testing + +### 6.3.1 Methods of base functionality testing + +#### 6.3.1.1 Check of DSLAM/MSAN equipment functionality + +##### 6.3.1.1.1 Check of functions of VLAN tag processing + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_VLAN_01 | +| Test name | Multi PVC | +| Test purpose |

Check if the DSLAM/MSAN has the possibility to transport the S VLAN (S VID) identifier on Ethernet, which is transferred upstream using the UNI interface Multi PVC model

NOTE – The test is produced in case of use of ATM transport on UNI interface.

| +| Initial condition |
  1. 1) Prepare in KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, the two customer ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the customer side, the home gateway has to be connected via user network interfaces (HG1 and HG2, accordingly).
  4. 4) A.1 and A.2 hosts are connected to home gateway HG1.
  5. 5) B.1 and B.2 hosts are connected to home gateway HG2.
  6. 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation
  7. 7) A.1 and B.1 hosts use PPPoE sessions.
  8. 8) A.2 and B.2 hosts use IPoE sessions.
  9. 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
  10. 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
  11. 11) For termination of PPPoE sessions from A.1 and B.1 hosts the external router has to be connected to the Ethernet switch.
  12. 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
  13. 13) IP-addresses from one IP subnetwork are used on the hosts A.2, B.2 and X.2.
  14. 14) Two virtual connections are configured on HG1 and HG2 equipment:
    1. 15) PVC X1/Y1 for PPPoE traffic connected to A.1 and B.1 hosts, accordingly;
    2. 16) PVC X2/X2 for IPoE traffic connected to A.2 and B.2 hosts, accordingly.
  15. 17) Multi PVC (X1/Y1 and X2/Y2) on UNI interfaces are configured on the DSLAM/MSAN equipment.
  16. 18) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =1 for Ethernet frames which are transferred upstream from HG1 equipment on virtual connection PVC X1/Y1.
  17. 19) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =2 for Ethernet frames which are transferred upstream from HG1 equipment on virtual connection PVC X1/Y1.
| + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

20) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =3 for Ethernet frames which are transferred upstream from any user equipment on virtual connection PVC X2/Y2.

21) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols ICMP ARP.

| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) Perform traffic exchange between hosts A.2 and X.2.
  4. 4) Perform traffic exchange between hosts B.2 and X.2.
  5. 5) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_01.txt) and put the file into the corresponding section of the KB.
  6. 6) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
  2. 2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
  3. 3) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
  4. 4) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
  5. 5) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram showing Host A.1, Host A.2, Host B.1, Host B.2 connected to HG1 and HG2 modems. HG1 and HG2 are connected to a DSLAM via PVCs. The DSLAM is connected to an Ethernet switch via Port 1 and Port 2. Port 1 is connected to a Protocol analyzer and Host X.1. Port 2 is connected to Host X.2 and a Server DHCP. The DSLAM also has three virtual connections labeled S-VID '1' (PPPoEuser 1), S-VID '2' (PPPoEuser 2), and S-VID '3' (IPoEuser 1,2). A PPPoE Termination; DHCP relay agent is also shown.

| + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_VLAN_02 | +| Test name | Configuration of S-VLAN for Single PVC/Untagged architecture (model N:1+1:1) | +| Test purpose | Check if the DSLAM/MSAN has the possibility to assign the S VLAN (S-VID) identifier to the Ethernet frames, which are transferred upstream using the Single PVC/Untagged model on UNI interface | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two customer ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the customer side the home gateway has to be connected via user network interfaces (HG1 and HG2, accordingly).
  4. 4) A.1 and A.2 hosts are connected to home gateway HG1.
  5. 5) B.1 and B.2 hosts are connected to home gateway HG2.
  6. 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
  7. 7) A.1 and B.1 hosts use PPPoE sessions.
  8. 8) A.2 and B.2 hosts use IPoE sessions.
  9. 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
  10. 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
  11. 11) For termination of PPPoE sessions from A.1 and B.1 hosts, the external router has to be connected to the Ethernet switch.
  12. 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
  13. 13) IP-addresses from one IP subnetwork are used on the hosts A.2, B.2 and X.2.
  14. 14) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
  15. 15) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
  16. 16) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
  17. 17) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =1 for Ethernet frames which are transferred upstream depending on value of Ethertype field and user port number. Following options are configured:
    1. 18) assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) with the Ethertype value 0x8863 or 0x8864;
    2. 19) assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) with the Ethertype value 0x8863 or 0x8864;
    3. 20) assignment of "S-VID"=3 frames to Ethernet transferred from HG1 and HG2 equipment (any user port) with the Ethertype value 0x0800.
  18. 21) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols ICMP ARP.
| +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) Perform traffic exchange between hosts A.2 and X.2.
  4. 4) Perform traffic exchange between hosts B.2 and X.2.
  5. 5) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_02.txt) and put the file into the corresponding section of the KB.
  6. 6) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
  2. 2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
  3. 3) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
  4. 4) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
  5. 5) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme | Network diagram for test scheme. Hosts A.1 (PPPoE), A.2 (DHCP), B.1 (PPPoE), and B.2 (DHCP) connect to Home Gateways HG1 and HG2. HG1 and HG2 connect via PVC 0/35 to DSLAM ports 1 and 2. The DSLAM connects to a Protocol analyzer and an Ethernet switch. The Ethernet switch connects to Host X.1 (DHCP), Host X.2 (DHCP), a DHCP Server, and a PPPoE Termination/DHCP relay agent. S-VID tags 1, 2, and 3 are shown assigned to different traffic flows. | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_VLAN_03 | +| Test name | Configuration of S-VLAN for Single PVC/VLAN tagged architecture (model N:1+1:1) | +| Test purpose | Check if the DSLAM/MSAN has the possibility to assign the S VLAN (S VID) identifier to the Ethernet frames, which are transferred upstream using the Single PVC/VLAN tagged model on UNI interface | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side the home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
  4. 4) A.1 and A.2 hosts are connected to home getaway HG1.
  5. 5) B.1 and B.2 hosts are connected to home getaway HG2.
| + +- 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation. +- 7) A.1 and B.1 hosts use PPPoE sessions. +- 8) A.2 and B.2 hosts use IPoE sessions. +- 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected). +- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually. +- 11) For termination of PPPoE sessions from A.1 and B.1 hosts external router has to be connected to the Ethernet switch. +- 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually. +- 13) IP-addresses from one IP subnetwork are used on the hosts A.2, B.2 and X.2. +- 14) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment. +- 15) HG1 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=1 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=2 for IPoE sessions connected with host A.2. +- 16) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment. +- 17) HG2 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured as follows: there is assigned "C-VID"=1 for PPPoE sessions connected with host B.1, and "C-VID"=2 for IPoE sessions connected with host B.2. +- 18) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment. +- 19) The possibility of use VLAN identifiers for users' ports No. 1 and No. 2 is configured on the DSLAM/MSAN equipment. The VLAN Membership List is configured on the DSLAM/MSAN equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved values "C-VID"=1 and "C-VID"=2. +- 20) On the DSLAM/MSAN equipment there is a possibility to assign S VID identifiers for Ethernet frames which are transferred upstream depending on value of VLAN identifier in initial IEEE 802.1Q tag and user port number. The following configuration of VLAN translation table should be done: + - assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) and have "C-VID"=1 in IEEE 802.1Q tag; + - assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) and have "C-VID"=1 in IEEE 802.1Q tag; + - assignment of "S-VID"=3 to Ethernet frames which are transferred from HG2 equipment (any user port) and have "C-VID"=2 in IEEE 802.1Q tag. +- 21) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP || ARP. + +| | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1) Perform traffic exchange between hosts A.1 and X.1.
2) Perform traffic exchange between hosts B.1 and X.1.
3) Perform traffic exchange between hosts A.2 and X.2.
4) Perform traffic exchange between hosts B.2 and X.2.
5) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_03.txt) and put the file into the corresponding section of the KB.
6) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
3) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
4) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
5) The DSLAM/MSAN equipment deletes the Ethernet frames which contain C-VID identifiers in IEEE 802.1Q tag not matching VLAN Membership List.
6) The daily report form has been saved in the corresponding section of KB. | +| Test scheme | Network diagram for DSLAM_VLAN_04 test scheme showing hosts A.1, A.2, B.1, B.2 connected via home gateways HG1 and HG2 to a DSLAM. The DSLAM connects to a protocol analyzer and an Ethernet switch, which further connects to hosts X.1, X.2, and a DHCP server/PPPoE termination agent. Various VLAN tags (S-VID and C-VID) and PVC settings are indicated along the paths. | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_VLAN_04 | +| Test name | Configuration of S-VLAN/C-VLAN stack (QinQ) | +| Test purpose | Check if the DSLAM/MSAN has the possibility to assign the VLAN tag pair (S-Tag/C-Tag) to the Ethernet frame, which are transferred upstream | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side, the home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2. | + +| | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.

7) A.1 and B.1 hosts use IPoE sessions.

8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).

9) IP-addresses for hosts A.1, B.1, X.1 and X.2 are assigned dynamically with the allocated DHCP server, or are configured manually.

10) IP-addresses from one IP subnetwork are used on the hosts A.1, B.1 and X.2.

11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.

12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.

13) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.

14) On the DSLAM/MSAN equipment there is configured the possibility to assign VLAN tag pair (S-Tag/C-Tag) for Ethernet frames which are transferred upstream. The S-VID value identifies DSLAM/MSAN equipment (i.e., value S VID is identical for all users ports). C-VID value identifies number of user port on which Ethernet frame has arrived. The following configuration should be done:

  • – assignment of "S-VID"=1, "C-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1);
  • – assignment of "S-VID"=1, "C-VID"=2 to Ethernet frames which are transferred from HG1 equipment (user port No. 2)

15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |

1) Perform traffic exchange between hosts A.1 and X.1.

2) Perform traffic exchange between hosts B.1 and X.2.

3) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_04.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) The DSLAM/MSAN equipment has assigned the identifier "S-VID"=1, "C-VID"=1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.

2) The DSLAM/MSAN equipment has assigned the identifier "S-VID"=1, "C-VID"=2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.

3) The daily report form has been saved in the corresponding section of KB.

| + +![Network diagram for test scheme DSLAM_VLAN_05. It shows Host A.1 and Host B.1 connected to HG1 and HG2 (modemxDSL) respectively via IPoE. HG1 and HG2 connect to DSLAM ports 1 and 2 via PVC 0/35 (IPoE). The DSLAM connects to an Ethernet switch. Port 1 traffic is tagged with S-VID '1', C-VID '1' (user 1). Port 2 traffic is tagged with S-VID '1', C-VID '2' (user 2). The Ethernet switch connects to Host X.1 and Host X.2 (both using DHCP), a Server DHCP, and a DHCP relay agent.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test scheme

|

Detailed Diagram Description: The diagram illustrates a network test setup. On the left, Host A.1 and Host B.1 are connected to Home Gateways HG1 and HG2 respectively. HG1 and HG2 are labeled as modemxDSL. The connections between hosts and HGs are labeled 'IP: x.x.x.x (DHCP)'. The HGs connect to a DSLAM via 'PVC 0/35 (IPoE)'. HG1 connects to Port 1 and HG2 connects to Port 2 of the DSLAM. Inside the DSLAM, dashed lines show logical paths to an Ethernet switch. The path from Port 1 is labeled 'S-VID "1", C-VID "1" (user 1)' and the path from Port 2 is labeled 'S-VID "1", C-VID "2" (user 2)'. The Ethernet switch connects to Host X.1 and Host X.2, both labeled 'IP: x.x.x.x (DHCP)'. Additionally, the switch connects to a 'Server DHCP' and a 'DHCP relay agent' (indicated by a red crossed circle icon).

| +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Network diagram for test scheme DSLAM\_VLAN\_05. It shows Host A.1 and Host B.1 connected to HG1 and HG2 (modemxDSL) respectively via IPoE. HG1 and HG2 connect to DSLAM ports 1 and 2 via PVC 0/35 (IPoE). The DSLAM connects to an Ethernet switch. Port 1 traffic is tagged with S-VID '1', C-VID '1' (user 1). Port 2 traffic is tagged with S-VID '1', C-VID '2' (user 2). The Ethernet switch connects to Host X.1 and Host X.2 (both using DHCP), a Server DHCP, and a DHCP relay agent. + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_VLAN_05 | +| Test name | Configuration of TLS user port | +| Test purpose | Check if the DSLAM/MSAN has the possibility of TLS user port configuration providing transparent transfer of initial IEEE 802.1Q tags set by users over the network. | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side to the network termination of given user line there should be a connection from home gateway (business) (HG1 equipment).
  4. 4) Hosts A.1 and A.2 are connected to HG1 equipment.
  5. 5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
  6. 6) Host A.1 uses PPPoE sessions.
  7. 7) Host A.2 uses IPoE sessions.
  8. 8) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
  9. 9) IP-address for host A.1 is assigned dynamically with allocated PPPoE server or are configured manually.
  10. 10) For termination of PPPoE sessions from host A.1 external router has to be connected to the Ethernet switch.
  11. 11) IP-addresses for hosts A.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
  12. 12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
  13. 13) HG1 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=111 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=222 for IPoE sessions connected with host A.2.
  14. 14) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
  15. 15) User port No. 1 of DSLAM/MSAN equipment is configured as TLS port providing transparent transfer of VLAN tags assigned on user equipment.
| + +| | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

16) VLAN Membership List is configured on the DSLAM/MSAN equipment for user port No. 1. The VLAN Membership List should contain the list of C-VID identifiers which have not been related to TLS traffic transferred through user port No. 1 in an upstream direction. This list should contain "C-VID"=111. All Ethernet frames transferred upstream through user port No. 1 and not having "C-VID"=111, should be processed as TLS traffic.

17) On the DSLAM/MSAN equipment should be configured the VLAN translation table according to which the Ethernet frames transferred upstream and having initial identifier "C-VID"=111 (matching VLAN Membership List) should get "S-VID"=1 identifier. Initial identifier C-VID in this case should be deleted.

18) On the DSLAM/MSAN equipment there is a possibility to assign TLS "S-VID"=100 identifier for Ethernet frames which are transferred upstream through user port No. 1 and having initial IEEE 802.1Q tag, not matching VLAN Membership List. Thus initial IEEE 802.1Q tag, received from the user, remains as enclosed C-Tag.

19) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |

1) Perform traffic exchange between hosts A.1 and X.1.

2) Perform traffic exchange between hosts A.2 and X.2.

3) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_05.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1. Thus initial IEEE 802.1Q tag (including "C-VID"=111), received from the user, has been deleted.

2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =100 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2. Thus initial IEEE 802.1Q tag (including "C-VID"=222), received from the user, has remained as an enclosed C-Tag (having "C-VID"=222).

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram showing the test scheme. On the left, Host A.1 (IP: x.x.x.x PPPoE) and Host A.2 (IP: x.x.x.x DHCP) are connected to an HG1 (modem xDSL). The HG1 is connected to a DSLAM via two PVCs: PVC 0/35 for PPPoE (802.1Q Tag '111') and PVC 0/35 for IPoE (802.1Q Tag '222'). The DSLAM has 'User port#1 - TLS' configured with a VLAN Membership List containing C-VID=111 and a translation table mapping C-VID=111 to S-VID=1. The DSLAM is connected to an Ethernet switch via Port 1. The switch is connected to Host X.1 (IP: x.x.x.x DHCP), Host X.2 (IP: x.x.x.x DHCP), a Server DHCP, and a PPPoE Termination; DHCP relay agent. The switch is configured with S-VID '1' for the PPPoE path and S-VID '100', C-VID '222' for the IPoE path.

| + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_VLAN_06 | +| Test name | Configuration of admissible list of Ethernet frame types | +| Test purpose | Check if the DSLAM/MSAN has the possibility of admissible list of Ethernet frame types configuration for certain user port (for the upstream transfer) | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) have to be used. On the user side the home gateway equipment (HG1 equipment) has to be connected to network termination of the given user line.

4) Host A.1 is connected to HG1 equipment.

5) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.

6) Host A.1 uses IPoE sessions.

7) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).

8) IP-addresses for hosts A.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.

9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.

10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.

11) On the DSLAM/MSAN equipment there is a possibility to assign "S-VID"=1 identifiers to any Ethernet frames transferred upstream through user port No. 1.

12) Further adjustment of equipment should be provided according to one of the following configurations:

Configuration 1
On HG1 equipment there should be a disconnected function of VLAN tags assignment for Ethernet frames transferred upstream. Host A.1 also should not assign VLAN tags for Ethernet frames transferred upstream.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.

Configuration 2
Configuration of HG1 equipment is the same as in Configuration 1.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.

Configuration 3
Configuration of HG1 equipment is the same as in Configuration 1.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.

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

Configuration 4
Activate on HG1 equipment function of VLAN tags assignment to Ethernet frames transferred upstream. HG1 equipment should be configured to assign VLAN "C-VID"=1 identifier for IPoE sessions related with host A.1

On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.

Configuration 5
Configuration of HG1 equipment is same as in Configuration 4.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.

Configuration 6
Configuration of HG1 equipment is same as in Configuration 4.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.

13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |
  1. 1) Using Configuration 1 perform on host A.1 command ping for host X.1.
  2. 2) Using Configuration 2 perform on host A.1 command ping for host X.1.
  3. 3) Using Configuration 3 perform on host A.1 command ping for host X.1.
  4. 4) Using Configuration 4 perform on host A.1 command ping for host X.1.
  5. 5) Using Configuration 5 perform on host A.1 command ping for host X.1.
  6. 6) Using Configuration 6 perform on host A.1 command ping for host X.1.
  7. 7) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_06.txt) and put the file into the corresponding section of the KB.
  8. 8) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) Successful performance of command ping according to step 1 of test procedure.
  2. 2) Unsuccessful performance of command ping according to step 2 of test procedure.
  3. 3) Successful performance of command ping according to step 3 of test procedure.
  4. 4) Unsuccessful performance of command ping according to step 4 of test procedure.
  5. 5) Successful performance of command ping according to step 5 of test procedure.
  6. 6) Successful performance of command ping according to step 6 of test procedure.
  7. 7) The daily report form has been saved in the corresponding section of KB.
| + +![Network diagram for QoS testing. Host A.1 connects to HG1 (modem/DSL) via IPoE. HG1 connects to DSLAM Port 1 via 'Untagged or VLAN tagged frames, PVC 0/35'. A callout for User port#1 specifies frame variants: 1-st variant Untagged frames, 2-nd variant VLAN tagged frames, 3-rd variant any frames. DSLAM connects to Ethernet switch via S-VID '1'. Host X.1 and a Server DHCP connect to the Ethernet switch. A DHCP relay agent is shown with a red cross over its path.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +| | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test scheme

|
 graph LR     HostA1[Host A.1
IP: x.x.x.x DHCP] -- IPoE --> HG1[HG1
modem/DSL] HG1 -- "Untagged or VLAN tagged frames, PVC 0/35" --> DSLAM[DSLAM] subgraph DSLAM_Box [DSLAM] Port1[Port 1] Callout[User port#1
The admissible type of
Ethernet frame:
1-st variant Untagged
frames
2-nd variant
VLAN tagged frames
3-rd variant
any frames] end DSLAM -- "S-VID '1'" --> Switch[Ethernet switch] Switch --- HostX1[Host X.1
IP: x.x.x.x DHCP] Switch --- Server[Server
DHCP] Switch -.-> Relay[DHCP relay agent] style Relay stroke:#f00,stroke-width:4px
| +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Network diagram for QoS testing. Host A.1 connects to HG1 (modem/DSL) via IPoE. HG1 connects to DSLAM Port 1 via 'Untagged or VLAN tagged frames, PVC 0/35'. A callout for User port#1 specifies frame variants: 1-st variant Untagged frames, 2-nd variant VLAN tagged frames, 3-rd variant any frames. DSLAM connects to Ethernet switch via S-VID '1'. Host X.1 and a Server DHCP connect to the Ethernet switch. A DHCP relay agent is shown with a red cross over its path. + +##### 6.3.1.1.2 Check of QoS functions + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_QOS_01 | +| Test name | Marks of priority bits during processing of Ethernet frames which are not containing VLAN tags | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and not containing IEEE 802.1Q tags, assigned by user equipment | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side the home gateways equipment should be connected to network terminations of user lines (HG1 and HG2, accordingly).
  4. 4) Host A.1 is connected to home getaway HG1.
  5. 5) Host B.1 is connected to home getaway HG2.
  6. 6) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
  7. 7) A.1 and B.1 hosts use IPoE sessions.
  8. 8) HG1 and HG2 equipment work in the bridge mode (the function of local DHCP server is disconnected).
  9. 9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server, or are configured manually.
  10. 10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
  11. 11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
  12. 12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
  13. 13) A.1 and B.1 hosts should have possibility of priority assignment to Ethernet frames. A.1 and B.1 hosts should establish priority "6" for all transferred Ethernet frames.
| + +| | | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

14) HG1 and HG2 equipment should provide transparent translation of Ethernet frames priorities values configured on A.1 and B.1 hosts, accordingly. On HG1 equipment and HG2 there is disconnected the function of IEEE 802.1Q tags assignment to Ethernet frames transferred upstream.

15) On the DSLAM/MSAN equipment there should be configured possibility of S-Tag assignment, including identifier "S-VID"=1, to Ethernet frames transferred upstream through any of users ports. In this case the general VLAN (N:1) should be configured for all users ports.

16) On the DSLAM/MSAN equipment there should be configured user port No. 1 with the possibility of copying the priority value of Ethernet frame received from HG1 equipment, into the value of S-Tag priority.

17) On the DSLAM/MSAN equipment there should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:

  • – value of user port number (physical or logic);
  • – value of Ethertype field in the Ethernet frame;
  • – value of initial Ethernet frame priority received from HG2 equipment.

18) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) During traffic exchange between hosts B.1 and X.1 perform transfer of ARP message from host B.1 (for this purpose it is necessary to clear contents of ARP table on host B.1).
  4. 4) Save the captures of traces in separate files ([Vendor]-DSLAM_QOS_01.txt) and put the file into the corresponding section of the KB.
  5. 5) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
  2. 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the DSLAM/MSAN equipment for the given port.
  3. 3) Policy for different S-Tag definition criteria has been correctly performed.
  4. 4) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram showing the test scheme. Host A.1 (IP: x.x.x.x (DHCP)) connects via IPoE to HG1 (modem xDSL). Host B.1 (IP: x.x.x.x (DHCP)) connects via IPoE to HG2 (modem xDSL). Both HGs connect to a DSLAM via links labeled 'Priority tagged frames/No VLAN tag (PVC 0/35)'. The DSLAM has Port 1 (labeled 'Copying of value of priority') and Port 2 (labeled 'Applying of policy: Ingress to Egress'). The DSLAM connects via a link labeled 'S-Tag (S-VID

| + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_QOS_02 | +| Test name | Marks of priority bits during processing of Ethernet frames containing VLAN tags | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and containing IEEE 802.1Q tags, assigned by user equipment | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).

4) Host A.1 is connected to home gateway HG1.

5) Host B.1 is connected to home gateway HG2.

6) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.

7) A.1 and B.1 hosts use IPoE sessions.

8) HG1 and HG2 equipment work in the bridge mode (the function of local DHCP server is disconnected).

9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.

10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.

11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.

12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.

13) HG1 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.

14) HG2 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.

15) On the DSLAM/MSAN equipment should be configured the possibility of IEEE 802.1Q tags usage on users ports No. 1 and No. 2. The VLAN Membership List is configured on the DSLAM/MSAN equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved value "C-VID" =1.

16) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through any of users ports. In this case, the general S-VLAN (N:1) should be configured for all users ports.

17) On the DSLAM/MSAN equipment there should be configured user port No. 1 with the possibility of copying the priority value from IEEE 802.1Q tag, received from HG1 equipment, into the S-Tag priority value.

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

18) On the DSLAM/MSAN equipment should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:

  • – value of user port number (physical);
  • – C-VID value in the initial Ethernet frame;
  • – C-Tag priority value in the initial Ethernet frame.

19) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) Save the captures of traces in separate files ([Vendor]-DSLAM_QOS_02.txt) and put the file into the corresponding section of the KB.
  4. 4) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
  2. 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the DSLAM/MSAN equipment for the given port.
  3. 3) Policy for different S-Tag definition criteria has been correctly performed.
  4. 4) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 (modem xDSL) respectively. These are connected to a DSLAM. Port 1 of the DSLAM is connected to an Ethernet switch, and Port 2 is connected to a DHCP relay agent. Host X.1 is connected to the Ethernet switch. The diagram includes labels for IP addresses (IP: xxx.x (DHCP)), 802.1Q tags (C-VID '1', priority '6'), and policy actions like 'Copying of value of priority 802.1 Q Tag' and 'Applying of policy Ingress to Egress'.

Detailed description of the diagram: - Host A.1 (IP: xxx.x (DHCP)) connects via IPoE to HG1 (modem xDSL). - Host B.1 (IP: xxx.x (DHCP)) connects via IPoE to HG2 (modem xDSL). - HG1 connects to DSLAM Port 1 with label: 802.1Q Tag (C-VID '1', priority '6'), PVC 0/35. - HG2 connects to DSLAM Port 2 with label: 802.1Q Tag (C-VID '1', priority '6'), PVC 0/35. - DSLAM Port 1 has a box: 'Copying of value of priority 802.1 Q Tag'. - DSLAM Port 2 has a box: 'Applying of policy Ingress to Egress'. - DSLAM connects to an Ethernet switch via a link labeled 'S-Tag (S-VID '1'+priority)'. - Host X.1 (IP: xxx.x (DHCP)) connects to the Ethernet switch. - A DHCP relay agent (represented by a server icon with a red 'X' over it) is connected to the Ethernet switch, labeled 'Server DHCP'.
| + +##### 6.3.1.1.3 Check of security functions + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_SEC_01 | +| Test name | Blocking of broadcasting packages | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of blocking upstream and downstream broadcast messages | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect the equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side, the equipment of a home gateway (HG1 equipment) should be connected to network termination of a user line.
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
| + +| | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).

7) IP-addresses for hosts A.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.

8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.

9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.

10) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.

11) On the DSLAM/MSAN equipment there should be configured blocking of broadcasting packages in an upstream direction for user port No. 1.

12) On the DSLAM/MSAN equipment there should be configured blocking of broadcasting packages in downstream for "S-VID" =1.

13) Before beginning of carrying out of test procedure it is necessary to clear contents of ARP tables on hosts A.1 and X.1.

| +| Test procedure |

1) Perform on host A.1 command ping for host X.1.

2) Perform on host X.1 command ping for host A.1.

3) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_01.txt) and put the file into the corresponding section of the KB

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Command ping, performed on host A.1 for host X.1 has not passed (broadcasting ARP message transferred by host A.1 has been blocked on the DSLAM/MSAN equipment).

2) Command ping, performed on host X.1 for host A.1 has not passed (broadcasting ARP message transferred by host X.1 has been blocked on the DSLAM/MSAN equipment).

3) In ARP tables on hosts A.1 and X.1 there are no dynamic records.

4) There is a possibility of broadcasting packages blocking function configuration on the DSLAM/MSAN equipment in a downstream. Configuration of the given function is made on VLAN basis.

5) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme | Network diagram showing Host A.1 connected to HG1 (modemxDSL), which is connected via PVC 0/35 to Port 1 of a DSLAM. The DSLAM has a function of blocking broadcasting packages activated. Port 1 is connected via S-VID '1' to an Ethernet switch, which is connected to Host X.1. Both hosts have IP: xxxxx.
 graph LR     HostA1[Host A.1
IP: xxxxx] --- HG1["HG1
(modemxDSL)"] HG1 --- PVC 0/35 DSLAM subgraph DSLAM [DSLAM] Port1[Port 1] Note[Function of blocking broadcasting packages activated] end Port1 -.-> S-VID "1" EthernetSwitch[Ethernet switch] EthernetSwitch --- HostX1[Host X.1
IP: xxxxx]
| + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_SEC_02 | +| Test name | Restriction of the MAC-addresses table size | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of restriction of sources MAC-addresses number connected with one user port | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On party of user home gateway equipment (HG1 equipment) should be connected to network termination of a user line.
4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.
5) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
7) IP-addresses for hosts A.1, A.2, A.3 and X.1 are configured manually (statically) and should be from one IP subnetwork.
8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
10) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.
11) On the DSLAM/MSAN equipment should be configured the maximum number of MAC-addresses of the sources resolved for user port No. 1 equals to 2. | +| Test procedure | 1) Perform consecutive connections of hosts A.1, A.2 and A.3.
2) During connection of each host (A.1, A.2, A.3) perform from this host continuous command ping for host X.1.
3) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_02.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) Successful performance of commands ping from A.1 and A.2 hosts.
2) Unsuccessful performance of commands ping from host A.3.
3) There is a possibility of maximum resolved MAC-addresses number of sources configuration independently for each users ports.
4) The daily report form has been saved in the corresponding section of KB. | + +![Network diagram showing Host A.1, A.2, and A.3 connected to a central HG1 (modem xDSL) unit. HG1 is connected via a PVC 0/35 line to a DSLAM unit. The DSLAM has a 'User port #1' with a note 'Admissible number of MAC-address of source' and 'Port 1'. The DSLAM is connected via an S-VID '1' line to an Ethernet switch. Host X.1 is connected to the Ethernet switch. All hosts have IP: xxxxx.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +**Test scheme** + +Network diagram showing Host A.1, A.2, and A.3 connected to a central HG1 (modem xDSL) unit. HG1 is connected via a PVC 0/35 line to a DSLAM unit. The DSLAM has a 'User port #1' with a note 'Admissible number of MAC-address of source' and 'Port 1'. The DSLAM is connected via an S-VID '1' line to an Ethernet switch. Host X.1 is connected to the Ethernet switch. All hosts have IP: xxxxx. + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_SEC_03 | +| Test name | Filtration on MAC-addresses basis | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of Ethernet frames filtration on sources MAC-addresses basis and MAC-addresses of destinations. | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
  4. 4) A.1 and A.2 hosts are connected to home gateway HG1.
  5. 5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
  6. 6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
  7. 7) IP-addresses for hosts A.1, A.2, X.1 and X.2 are configured manually (statically) and should be from one IP subnetwork. Hosts A.1/A.2 should have the possibility to exchange traffic with hosts X.1/X.2 without router.
  8. 8) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
  9. 9) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
  10. 10) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including the identifier "S-VID"=1, to Ethernet frames transferred upstream through user port No. 1.
  11. 11) On the DSLAM/MSAN equipment there should be activated function of Ethernet frames filtration for user port No. 1 MAC-addresses. For the given user port there should be configured barring for access from source with MAC-address of host A.2, and also an barring for access to destination with MAC-address of host X.2.
| + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1) Perform on host A.1 command ping for host X.1.
2) Perform on host A.1 command ping for host X.2.
3) Perform on host A.2 command ping for host X.1.
4) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_03.txt) and put the file into the corresponding section of the KB.
5) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) Successful performance of command ping on host A.1 for host X.1.
2) Unsuccessful performance of command ping on host A.1 for host X.2.
3) Unsuccessful performance of command ping on host A.2 for host X.1.
4) The daily report form has been saved in the corresponding section of KB. | +| Test scheme |

Image: Network diagram showing Host A.1 and Host A.2 connected to HG1 (modem xDSL). HG1 is connected via PVC 0/35 to Port 1 of a DSLAM. Port 1 is connected via S-VID '1' to an Ethernet switch. Host X.1 and Host X.2 are connected to the Ethernet switch via S-VID '1'. The DSLAM has a 'User port #1' with 'Activated function of filtration on MAC-address'.

| + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_SEC_04 | +| Test name | Determination of duplicated users MAC-addresses | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of detecting the duplicated users MAC-addresses and the subsequent mechanism for resolution of the given situation | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2.
6) Configure for host B.1 MAC-address similar to that is used by host A.1.
7) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
8) HG1 and HG2 equipment works in a bridged mode (function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.
10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment. | + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.

12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.

13) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through users ports No. 1 and No. 2.

14) Further adjustment of equipment should be provided according to one of the following configurations.

Configuration 1
In case of detection of duplicated MAC-addresses work of all users having identical MAC-addresses is permitted.

Configuration 2
In case of detection of duplicated MAC addresses, one of the users with duplicated MAC addresses is blocked.

Configuration 3
In case of detection of duplicated MAC-addresses refusal of service should be given to both users with the duplicated MAC-addresses.

| +| Test procedure |

1) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 1).

2) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 2).

3) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 3).

4) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_04.txt) and put the file into the corresponding section of the KB.

5) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) In case of configuration 1:

  • – command ping, performed on host A.1 in direction to host X.1, passes;
  • – command ping, performed on host B.1 in direction to host X.1, passes.

2) In case of a configuration 2:

  • – command ping, performed on host A.1 in direction to host X.1, passes;
  • – command ping, performed on host B.1 in direction to host X.1, does not pass.

3) In case of configuration 3:

  • – command ping, performed on host A.1 in direction to host X.1, does not pass;
  • – command ping, performed on host B.1 in direction to host X.1, does not pass.

4) The daily report form has been saved in the corresponding section of KB.

| + +![Test scheme diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 modems respectively. HG1 and HG2 are connected to a DSLAM via PVC 0/35. The DSLAM is connected to an Ethernet switch via S-VID '1'. Host X.1 is connected to the Ethernet switch via S-VID '1'.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test scheme

|
 graph LR     HA1[Host A.1
IP: xxxxx] --- HG1["HG1
(modem xDSL)"] HB1[Host B.1
IP: xxxxx
MAC Address Spoofing] --- HG2["HG2
(modem xDSL)"] HG1 -- "PVC 0/35" --- DSLAM HG2 -- "PVC 0/35" --- DSLAM subgraph DSLAM P1[Port 1] P2[Port 2] end DSLAM -- "S-VID '1'" --- ES[Ethernet switch] HX1[Host X.1
IP: xxxxx] -- "S-VID '1'" --- ES
| +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Test scheme diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 modems respectively. HG1 and HG2 are connected to a DSLAM via PVC 0/35. The DSLAM is connected to an Ethernet switch via S-VID '1'. Host X.1 is connected to the Ethernet switch via S-VID '1'. + +##### 6.3.1.1.4 Check of functions of identification of subscriber lines + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_LID_01 | +| Test name | Support of DHCP Option 82 | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of functioning as DHCP Relay Agent second level and maintenance of DHCP clients identification connection points using an information option (an option 82) | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
  6. 6) Host A.1 uses IPoE sessions. IP-address for host A.1 is defined dynamically using allocated DHCP server connected to the Ethernet switch. DHCP server supports option 82.
  7. 7) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
  8. 8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
  9. 9) Router providing functionality (full) of DHCP Relay Agent should be connected to the Ethernet switch equipment.
  10. 10) DSLAM/MSAN equipment works as DHCP Relay Agent second level.
  11. 11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp.
| +| Test procedure |
  1. 1) Initiate on host A.1 an establishment of IPoE session (provide transfer of broadcasting DHCP request from host A.1).
  2. 2) Save the captures of traces in separate files ([Vendor]-DSLAM_LID_01.txt) and put the file into the corresponding section of the KB.
  3. 3) Fill in a daily report form with the testing results and save it in the KB.
| + +| | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected result |

1) Using information option of DHCP protocol (option 82) DSLAM/MSAN equipment has definitely identified to which client initiating DHCP request user line is connected within network of broadband access.

2) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme | Network diagram showing Host A.1 connected to HG1 via IPoE. HG1 connects to Port 1 of a DSLAM (Layer 2 DHCP Relay Agent) via IPoE (PVC 0/35). The DSLAM connects to an Ethernet switch, which connects to a DHCP Relay Agent (full relay agent) and a Server DHCP.
 graph LR     HostA1[Host A.1
IP: x.x.x.x
client DHCP] -- IPoE --> HG1[HG1
modem xDSL] HG1 -- "IPoE (PVC 0/35)" --> DSLAM[DSLAM
Layer 2 DHCP Relay Agent
Port 1] DSLAM --- Switch[Ethernet switch] Switch --- Server[Server DHCP] Switch --- Relay[DHCP Relay Agent
full relay agent]
| + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_LID_02 | +| Test name | PPPoE functions Intermediate Agent support | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of functioning as PPPoE Intermediate Agent for maintenance of user lines identification | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
  4. 4) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
  5. 5) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
  6. 6) Host A.1 is connected to home gateway HG1.
  7. 7) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
  8. 8) Host A.1 uses PPPoE sessions. IP-address for host A.1 is defined dynamically using allocated PPPoE server connected to the Ethernet switch.
  9. 9) Router providing functionality of PPPoE sessions termination is connected to the Ethernet switch equipment.
  10. 10) DSLAM/MSAN equipment works as PPPoE Intermediate Agent.
  11. 11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed.
| + +| | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1) Initiate on host A.1 establishment of PPPoE session (to provide PPPoE Discovery message transfer from host A.1).
2) Save the captures of traces in separate files ([Vendor]-DSLAM_LID_02.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) The DSLAM/MSAN equipment adds PPPoE-TAG tag into the PPPoE Discovery packages (PADI, PADR) transferred upstream.
2) The given tag allows to definitely identify user line on which package PPPoE, and also specify user who has transferred the given message:
  • – "Agent Circuit ID" option should identify definitely DSLAM/MSAN equipment within network of user's access, and also logic port of DSLAM/MSAN equipment through which package PPPoE has been received;
  • – "Agent Remote ID" option should identify definitely user connected with corresponding logic port of DSLAM/MSAN equipment through whom PPPoE package has been received.
3) The DSLAM/MSAN equipment has not changed the initial MAC-addresses of source and destination in the PPPoE Discovery packages transferred upstream.
4) The daily report form has been saved in the corresponding section of KB. | +| Test scheme | Test scheme diagram showing Host A.1 connected to HG1 (modem xDSL), which is connected to DSLAM/MSAN (PPPoE Intermediate Agent Port 1) via PPPoE (PVC0/35). DSLAM/MSAN is connected to an Ethernet switch, which is connected to a PPPoE Termination. A Server PPPoE is also connected to the Ethernet switch.
 graph LR     HostA1[Host A.1
IP: xxxxx
(client PPPoE)] -- PPPoE --> HG1["HG1
(modem xDSL)"] HG1 -- "PPPoE (PVC0/35)" --> DSLAM["DSLAM/MSAN
PPPoE Intermediate Agent
Port 1"] DSLAM --> Switch[Ethernet switch] Switch --> Termination[PPPoE Termination] Switch --> Server["Server PPPoE"]
| + +##### 6.3.1.1.5 Check of functions of management, monitoring and statistics gathering + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_MNG_01 | +| Test name | Equipment monitoring by SNMP protocol | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility for remote monitoring by means of control system using SNMP protocol | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user's ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side home gateways equipment should be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2. | + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

6) HG1 and HG2 equipment work in a bridged mode (function of local DHCP server is disconnected).

7) IP-addresses for A.1 and B.1 hosts are configured manually.

8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.

9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.

10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.

11) Host which functions as remote workstation of the control system is connected to the Ethernet switch. On the given host SNMP software is established. IP-address for specified host should be configured manually and there should be from the same subnetwork, as IP-address of DSLAM/MSAN equipment used for interaction with control system.

12) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: SNMP.

| +| Test procedure |

1) Initiate remote monitoring of DSLAM/MSAN equipment on host, carrying out functions of workstation of a control system.

2) Provide appearance of emergency and other non-standard situations on the DSLAM/MSAN equipment. Also it is necessary to simulate problems with powering (transition to the reserve block, return to mainframe), problems with interfaces (refusal of physical/channel level), connection of remote users to DSLAM/MSAN equipment on Telnet/SSH/SNMP, change of equipment configuration on Telnet/SSH/SNMP and other events.

3) Save the captures of traces in separate files ([Vendor]-DSLAM_MNG_01.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) During the process of monitoring, DSLAM/MSAN equipment gives the adequate information on condition of interfaces, operative memory and central processor.

2) The DSLAM/MSAN equipment provides transfer of adequate SNMP traps/informs messages in case of emergencies occurrence.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme | Test scheme diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 modems respectively, which are connected to a DSLAM via PVC 0/35. The DSLAM is connected to an Ethernet switch, which is connected to a Remote CLI. All hosts and the DSLAM have IP: xxxxx.
 graph LR     A1[Host A.1
IP: xxxxx] --- HG1["HG1
(modem xDSL)"] B1[Host B.1
IP: xxxxx] --- HG2["HG2
(modem xDSL)"] HG1 -- "PVC 0/35" --> DSLAM["DSLAM
Port 1"] HG2 -- "PVC 0/35" --> DSLAM["DSLAM
Port 2"] DSLAM --- ES["Ethernet switch"] ES --- RemoteCLI["Remote CLI
IP: xxxxx"] RemoteCLI -.-> SNMP DSLAM
| + +##### 6.3.1.1.6 Check of functions of Multicast mode support + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_MC_01 | +| Test name | Connection of several users to one multicasting group | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility to simultaneously connect several users to one multicasting group without subsequent load increase at network interfaces of DSLAM/MSAN equipment | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, three user ports on the DSLAM/MSAN equipment (three user lines) have to be used. On the user side, home gateway equipment has to be connected to network terminations of user lines (HG1 equipment, HG2 and HG3, accordingly).
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) Host B.1 is connected to home gateway HG2.
  6. 6) Host C.1 is connected to home gateway HG3.
  7. 7) HG1 equipment, HG2 and HG3 work in the bridged mode (function of local DHCP server is disconnected).
  8. 8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
  9. 9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
  10. 10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG3 equipment.
  11. 11) On hosts A.1, B.1 and C.1, IP STB software should be used. Hosts A.1, B.1 and C.1 are IGMP hosts. IP-addresses for hosts A.1, B.1 and C.1 are configured manually.
  12. 12) Hosts A.1, B.1 and C.1 use IPoE sessions.
  13. 13) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
  14. 14) Router equipment which functions as an IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM-SSM protocol is used.
  15. 15) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
  16. 16) DSLAM/MSAN equipment during processing of IGMP messages, works in the transparent IGMP Snooping mode.
  17. 17) On the DSLAM/MSAN equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the DSLAM/MSAN equipment should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from users IP-STB equipment.
  18. 18) Perform on the analyser of IP protocols for the corresponding interface, and set the following filter on protocols: IGMP.
| + +| | | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1) Hosts A.1, B.1 and C.1 should initiate IPoE sessions, transfer IGMP Membership Report messages and, thus, should consistently connect to the same multicasting group (observe one video channel).
2) Save the captures of traces in separate files ([Vendor]-DSLAM_MC_01.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) All users have connections to the same multicasting group (observe one video channel).
2) During consecutive connections of hosts B.1 and C.1, there is no additional load on network interfaces of DSLAM/MSAN equipment.
3) The daily report form has been saved in the corresponding section of KB. | +| Test scheme |

Image: Network diagram for Test scheme. Three hosts (Host A.1, Host B.1, Host C.1) are connected to three separate home gateways (HG1, HG2, HG3). Each host is an IPoE client with an IP address (IP:xxx.x). Each gateway is a modemxDSL unit. Each gateway is connected to a central DSLAM via a PVC035(IPoE) channel. The DSLAM has three ports (Port 1, Port 2, Port 3) corresponding to the three gateways. The DSLAM is configured for IGMP transparent snooping. The DSLAM is connected to an Ethernet switch via a MG-VLAN(S-VID 1) channel. The Ethernet switch is connected to a video server (HostX.1) with IP:xx.xx. The Ethernet switch is also connected to an IGMP router (PIM-SSM).

| + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_MC_02 | +| Test name | Restriction of channel numbers which are simultaneously observed by the user | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of multicasting groups total number restriction to which one user simultaneously can be connected | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side, home gateway equipment (HG1 equipment) should be connected to network termination of user line.
4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.
5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected). HG1 equipment should support the IGMP Snooping function.
6) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
7) On hosts A.1, A.2 and A.3 IP STB software should be used. Hosts A.1, A.2 and A.3 are IGMP hosts. IP-addresses for hosts A.1, A.2 and A.3 are configured manually.
8) Hosts A.1, A.2 and A.3 use IPoE sessions. | + +| | | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

9) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.

10) Router equipment performing functions of an IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM SSM protocol is used.

11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.

12) DSLAM/MSAN equipment during processing of IGMP messages works in the transparent IGMP Snooping mode.

13) On the DSLAM/MSAN equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the DSLAM/MSAN equipment there should be configured a possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.

14) On the DSLAM/MSAN equipment there should be configured for user port No. 1 restriction on total number of multicasting groups to which the given user can be connected. Maximum number of multicasting groups for the given user should be equal to 2.

15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.

| +| Test procedure |

1) Hosts A.1, A.2 and A.3 should consistently initiate IPoE sessions and transfer IGMP Membership Report messages, trying to be connected to various multicasting groups.

2) Save the captures of traces in separate files ([Vendor]-DSLAM_MC_02.txt) and put the file into the corresponding section of the KB.

3) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) A.1 and A.2 hosts are successfully connected to various multicasting groups.

2) Host A.3 has no connections to new multicasting group.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram for the test scheme. On the left, three Host IP-STBs (Host A.1, Host A.2, Host A.3) are connected to an HG1 (modem xDSL) unit. Each host is labeled with 'IP: xxxxx (IGMP host)'. The HG1 unit is connected via a 'PVC 0/35 (IPoE)' line to a DSLAM unit. The DSLAM unit has 'User port #1 Max two groups' and 'Port 1'. A dashed line labeled 'MC-VLAN (S/VID 1)' connects Port 1 of the DSLAM to an Ethernet switch. On the right, Host X.1 (video server) with 'IP: xxxxx' is connected to the Ethernet switch. Below the Ethernet switch is an IGMP router labeled 'PIM-SSM'.

| + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSLAM_MC_03 | +| Test name | Restriction of the multicasting groups list accessible to the user | +| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of restriction of the multicasting groups list accessible to the specified user | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side, home gateway equipment (HG1 equipment) should be connected to network termination of user line.
4) Host A.1 is connected to home gateway HG1.
5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
6) On HG1 equipment, one virtual channel (PVC X1/Y1) for carrying out of all traffic types (in case of ATM transport use on UNI interface) is configured.
7) On host A.1, IP-STB software should be used. Host A.1 should be IGMP host. IP-address for host A.1 should be configured manually.
8) Host A.1 uses IPoE sessions.
9) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
10) Router equipment performing functions of an IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM-SSM protocol is used.
11) One virtual channel (PVC X1/Y1) used to transfer all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
12) DSLAM/MSAN equipment during processing of IGMP messages functions in the transparent IGMP Snooping mode.
13) On the DSLAM/MSAN equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the DSLAM/MSAN equipment there should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.
14) On the DSLAM/MSAN equipment there should be configured for user port No. 1 the multicasting groups list accessible to user.
15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP. | +| Test procedure | 1) Host A.1 should initiate IPoE session and transfer IGMP Membership Report messages, trying to be consistently connected to various multicasting groups, matching the list of resolved groups, and not matching the given list.
2) Save the captures of traces in separate files ([Vendor]-DSLAM_MC_03.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) Host A.1 has been successfully connected to various multicasting groups matching list of groups, resolved for user port No. 1.
2) Host A.1 has no connections to any of multicasting groups which are not matching the list of groups, resolved for user port No. 1.
3) The daily report form has been saved in the corresponding section of KB. | + +![Network diagram showing Host A.1 (IP-STB) connected to HG1 (modemxDSL), which is connected to DSLAM via PVC 0/35 (IPoE). DSLAM Port 1 is connected via MC-VLAN (S-VID 1) to an Ethernet switch. Host X.1 (video server) is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router PIM-SSM. IP addresses are indicated for Host A.1 (IP:xxxxx (IGMP host)) and Host X.1 (IP:xxxxx).](e8e818455bb0d1a6153299a388b94868_img.jpg) + +| | | +|---------------------------|--| +|

Test scheme

| | +|---------------------------|--| + +Network diagram showing Host A.1 (IP-STB) connected to HG1 (modemxDSL), which is connected to DSLAM via PVC 0/35 (IPoE). DSLAM Port 1 is connected via MC-VLAN (S-VID 1) to an Ethernet switch. Host X.1 (video server) is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router PIM-SSM. IP addresses are indicated for Host A.1 (IP:xxxxx (IGMP host)) and Host X.1 (IP:xxxxx). + +#### 6.3.1.2 Check of EAS equipment functionality + +##### 6.3.1.2.1 Check of functions of VLAN tags processing + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_VLAN_01 | +| Test name | Configuration of S-VLAN for Untagged architecture (model N:1+1:1) | +| Test purpose | Check if the EAS has the possibility to assign the S VLAN (S-VID) identifier to the Ethernet frames,, which are transferred upstream using the Untagged model on UNI interface | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) have to be used. On the user side, the home gateway equipment has to be connected to the network terminations of user lines (HG1 and HG2, accordingly).
  4. 4) A.1 and A.2 hosts are connected to the home gateway equipment HG1.
  5. 5) B.1 and B.2 hosts are connected to the home gateway equipment HG2.
  6. 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
  7. 7) A.1 and B.1 hosts use PPPoE sessions.
  8. 8) A.2 and B.2 hosts use IPoE sessions.
  9. 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
  10. 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
  11. 11) For termination of PPPoE sessions from A.1 and B.1 hosts the external router should be connected to the Ethernet switch equipment.
  12. 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
  13. 13) On hosts A.2, B.2 and X.2 used IP-address from one IP subnetwork.
| + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

14) On the EAS equipment possibility of assignment of identifiers S-VID to Ethernet frames transferred upstream, depending on value of field Ethertype and number of port of the user is configured. Following options are configured:

  • – assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) with the Ethertype value 0x8863 or 0x8864;
  • – assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) with the Ethertype value 0x8863 or 0x8864;
  • – assignment of "S-VID"=3 frames to Ethernet transferred from HG1 and HG2 equipment (any user port) with the Ethertype value 0x0800.

15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) Perform traffic exchange between hosts A.2 and X.2.
  4. 4) Perform traffic exchange between hosts B.2 and X.2.
  5. 5) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_01.txt) and put the file into the corresponding section of the KB.
  6. 6) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) The EAS equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
  2. 2) The EAS equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
  3. 3) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
  4. 4) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
  5. 5) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram showing the test setup. Hosts A.1, A.2, B.1, and B.2 are connected to HG1 and HG2 (Ethernet WAN) units. HG1 and HG2 are connected to the EAS (Ethernet Aggregation Switch) via Port 1 and Port 2 respectively. The EAS is connected to an Ethernet switch via Port 3. The Ethernet switch is connected to Host X.1, Host X.2, and a Server DHCP. A Protocol analyzer is connected to the EAS. The diagram also shows IP addresses (IP:xxxx) and protocols (PPPoE, IPoE, DHCP) for the hosts and units.

| + +| | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_VLAN_02 | +| Test name | Configuration of S-VLAN for VLAN tagged architecture (model N:1+1:1) | +| Test purpose | Check if the EAS has the possibility to assign the S VLAN (S VID) identifier to the Ethernet frames, which are transferred upstream using the VLAN tagged model on UNI interface | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) have to be used. On the user side the home gateways equipment should be connected to the network terminations of user lines (HG1 and HG2, accordingly).
  4. 4) A.1 and A.2 hosts are connected to the home gateway equipment HG1.
  5. 5) B.1 and B.2 hosts are connected to the home gateway equipment HG2.
  6. 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
  7. 7) A.1 and B.1 hosts use PPPoE sessions.
  8. 8) A.2 and B.2 hosts use IPoE sessions.
  9. 9) HG1 and HG2 equipment works in a bridged mode (function of local DHCP server is disconnected).
  10. 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
  11. 11) For termination of PPPoE sessions from A.1 and B.1 hosts, the external router should be connected to the Ethernet switch equipment.
  12. 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
  13. 13) On hosts A.2, B.2 and X.2 are used IP-addresses from one IP subnetwork.
  14. 14) HG1 equipment supports the function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=1 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=2 for IPoE sessions connected with host A.2.
  15. 15) HG2 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured as follows: there is assigned "C-VID"=1 for PPPoE sessions connected with host B.1, and "C-VID"=2 for IPoE sessions connected with host B.2.
  16. 16) The possibility of use VLAN identifiers for users' ports No. 1 and No. 2 is configured on the EAS equipment. The VLAN Membership List is configured on the EAS equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved values "C-VID"=1 and "C-VID"=2.
  17. 17) On the EAS equipment there is a possibility to assign S VID identifiers for Ethernet frames which are transferred upstream depending on value of VLAN identifier in initial IEEE 802.1Q tag and user port number. The following configuration of VLAN translation table should be done:
    • – assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) and have "C-VID"=1 in IEEE 802.1Q tag;
    • – assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) and have "C-VID"=1 in IEEE 802.1Q tag;
    • – assignment of "S-VID"=3 to Ethernet frames which are transferred from HG2 equipment (any user port) and have "C-VID"=2 in IEEE 802.1Q tag.
  18. 18) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
| +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) Perform traffic exchange between hosts A.2 and X.2.
  4. 4) Perform traffic exchange between hosts B.2 and X.2.
  5. 5) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_02.txt) and put the file into the corresponding section of the KB.
  6. 6) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) The EAS equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to the PPPoE session of host A.1.
  2. 2) The EAS equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to the PPPoE session of host B.1.
  3. 3) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
  4. 4) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
  5. 5) The EAS equipment deletes the Ethernet frames which contain C-VID identifiers in IEEE 802.1Q tag not matching VLAN Membership List.
  6. 6) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram showing the test scheme. Hosts A.1 and A.2 are connected to HG1 (Ethernet WAN). Hosts B.1 and B.2 are connected to HG2 (Ethernet WAN). Both HG1 and HG2 are connected to the EAS (Ethernet Aggregation Switch) via Port 1 and Port 2 respectively. The EAS is connected to a Protocol analyzer and an Ethernet switch. The Ethernet switch is connected to Host X.1 and Host X.2 (both with IP: xxx.x (DHCP)), a Sever DHCP, and a PPPoE Termination/DHCP relay agent. The diagram shows various VLAN tags (C-VID, S-VID) being applied to frames at different points in the network.

| +| Test number | EAS_VLAN_03 | +| Test name | Configuration of S-VLAN/C-VLAN stack (QinQ) | +| Test purpose | Check if the EAS has the possibility to assign the VLAN tag pair (S-Tag/C-Tag) to the Ethernet frame, which are transferred upstream | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) have to be used. On the user side the home gateways equipment should be connected to the network terminations of user lines (HG1 and HG2, accordingly).
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) Host B.1 is connected to home gateway HG2.
  6. 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
  7. 7) A.1 and B.1 hosts use IPoE sessions.
| + +| | | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).

9) IP-addresses for hosts A.1, B.1, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.

10) IP-addresses from one IP subnetwork are used on the hosts A.1, B.1 and X.2.

11) On the EAS equipment there is configured the possibility to assign VLAN tag pair (S-Tag/C-Tag) for Ethernet frames which are transferred upstream. The S-VID value identifies EAS equipment (i.e., value S VID is identical for all users ports). C-VID value identifies number of user port on which Ethernet frame has arrived. The following configuration should be done:

  • – assignment of "S-VID"=1, "C-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1);
  • – assignment of "S-VID"=1, "C-VID"=2 to Ethernet frames which are transferred from HG1 equipment (user port No. 2)

12) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |

1) Perform traffic exchange between hosts A.1 and X.1.

2) Perform traffic exchange between hosts B.1 and X.2.

3) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_03.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) The EAS equipment has assigned the identifier "S-VID"=1, "C-VID"=1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.

2) The EAS equipment has assigned the identifier "S-VID"=1, "C-VID"=2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme | Network diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 (Ethernet WAN) respectively. HG1 and HG2 are connected to the EAS (Ethernet Access Switch) via PoE. The EAS has two ports, Port 1 and Port 2, connected to an Ethernet switch. Port 1 is labeled 'S-VID 1', 'C-VID 1' (user 1) and Port 2 is labeled 'S-VID 1', 'C-VID 2' (user 2). The Ethernet switch is connected to Host X.1 and Host X.2 (both labeled IP: xxxxx (DHCP)), a DHCP relay agent, and a Server DHCP. Host A.1 and Host B.1 are also labeled IP: xxxxx (DHCP). | + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_VLAN_04 | +| Test name | Configuration of TLS user port | +| Test purpose | Check if the EAS has the possibility of TLS user port configuration providing transparent transfer of initial IEEE 802.1Q tags set by users over the network. | + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) have to be used. On the user side to the network termination of given user line there should be a connection from home gateway (business) (HG1 equipment).
4) Hosts A.1 and A.2 are connected to HG1 equipment.
5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
6) Host A.1 uses PPPoE sessions.
7) Host A.2 uses IPoE sessions.
8) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
9) IP-address for host A.1 is assigned dynamically with allocated PPPoE server or are configured manually.
10) For termination of PPPoE sessions from host A.1, the external router should be connected to the Ethernet switch equipment.
11) IP-addresses for hosts A.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
12) HG1 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=111 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=222 for IPoE sessions connected with host A.2.
13) User port No. 1 of EAS equipment is configured as TLS port providing transparent transfer of VLAN tags assigned on user equipment.
14) VLAN Membership List is configured on the EAS equipment for user port No. 1. The VLAN Membership List should contain the list of C-VID identifiers which have not been related to TLS traffic transferred through user port No. 1 in an upstream direction. This list should contain "C-VID"=111. All Ethernet frames transferred upstream through user port No. 1 and not having "C-VID"=111, should be processed as TLS traffic.
15) On the EAS equipment should be configured the VLAN translation table according to which the Ethernet frames transferred upstream and having initial identifier "C-VID"=111 (matching VLAN Membership List) should get "S-VID"=1 identifier. Initial identifier C-VID in this case should be deleted.
16) On the EAS equipment there is a possibility to assign TLS "S-VID"=100 identifier for Ethernet frames which are transferred upstream through user port No. 1 and having initial IEEE 802.1Q tag, not matching VLAN Membership List. Thus initial IEEE 802.1Q tag, received from the user, remains as enclosed C-Tag.
17) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP. | +| Test procedure | 1) Perform traffic exchange between hosts A.1 and X.1.
2) Perform traffic exchange between hosts A.2 and X.2.
3) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_04.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. | + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected result | 1) The EAS equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1. Thus initial IEEE 802.1Q tag (including "C-VID"=111), received from the user, has been deleted.
2) The EAS equipment has assigned the identifier "S VID" =100 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2. Thus initial IEEE 802.1Q tag (including "C-VID"=222), received from the user, has remained as an enclosed C-Tag (having "C-VID"=222).
3) The daily report form has been saved in the corresponding section of KB. | +| Test scheme |

Image: Network diagram showing Host A.1 and Host A.2 connected to HG1 (Ethernet WAN). HG1 is connected to EAS via Port 1. EAS has a User port#1 - TLS with VLAN Membership List (C-VID=111) and VLAN translation table (C-VID=111 -> S-VID=1). EAS is connected to an Ethernet switch via Port 2. Host X.1 and Host X.2 are connected to the switch. A PPPoE Termination, DHCP relay agent is connected to the switch. The switch is also connected to a Server DHCP. Labels on the diagram include: Host A.1 (IP: x.x.x.x (PPPoE)), Host A.2 (IP: x.x.x.x (DHCP)), HG1 (Ethernet WAN), 802.1Q Tag '111' (PPPoE), 802.1Q Tag '222' (IPoE), EAS, Port 1, Port 2, TLS, S-VID '1', S-VID '100', C-VID '222', Host X.1 (IP: x.x.x.x (DHCP)), Host X.2 (IP: x.x.x.x (DHCP)), Ethernet switch, Server DHCP, PPPoE Termination, DHCP relay agent.

| + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_VLAN_05 | +| Test name | Configuration of admissible list of Ethernet frame types | +| Test purpose | Check if the EAS has the possibility of admissible list of Ethernet frame types configuration for certain user port (for the upstream transfer). | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side the equipment of a home gateway (HG1 equipment) should be connected to the network termination of the given user line.
4) Host A.1 is connected to HG1 equipment.
5) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
6) Host A.1 uses IPoE sessions.
7) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
8) IP-addresses for hosts A.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.
9) On the EAS equipment there is a possibility to assign "S-VID"=1 identifiers to any Ethernet frames transferred upstream through user port No. 1.
10) Further adjustment of equipment should be provided according to one of the following configurations.

Configuration 1
On HG1 equipment there should be a disconnected function of VLAN tags assignment for Ethernet frames transferred upstream. Host A.1 also should not assign VLAN tags for Ethernet frames transferred upstream. | + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.

Configuration 2
Configuration of HG1 equipment is same as in Configuration 1.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.

Configuration 3
Configuration of HG1 equipment is the same as in Configuration 1.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.

Configuration 4
Activate on HG1 equipment function of VLAN tags assignment to Ethernet frames transferred upstream. HG1 equipment should be configured to assign VLAN "C-VID"=1 identifier for IPoE sessions related with host A.1
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.

Configuration 5
Configuration of HG1 equipment is same as in Configuration 4.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.

Configuration 6
Configuration of HG1 equipment is the same as in Configuration 4.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.

11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |
  1. 1) Using Configuration 1 perform on host A.1 command ping for host X.1.
  2. 2) Using Configuration 2 perform on host A.1 command ping for host X.1.
  3. 3) Using Configuration 3 perform on host A.1 command ping for host X.1.
  4. 4) Using Configuration 4 perform on host A.1 command ping for host X.1.
  5. 5) Using Configuration 5 perform on host A.1 command ping for host X.1.
  6. 6) Using Configuration 6 perform on host A.1 command ping for host X.1.
  7. 7) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_05.txt) and put the file into the corresponding section of the KB.
  8. 8) Fill in a daily report form with the testing results and save it in the KB.
| + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected result | 1) Successful performance of command ping according to step 1 of test procedure.
2) Unsuccessful performance of command ping according to step 2 of test procedure.
3) Successful performance of command ping according to step 3 of test procedure.
4) Unsuccessful performance of command ping according to step 4 of test procedure.
5) Successful performance of command ping according to step 5 of test procedure.
6) Successful performance of command ping according to step 6 of test procedure.
7) The daily report form has been saved in the corresponding section of KB. | +| Test scheme |

Image: Network diagram for the test scheme. Host A.1 (IP: x.xxx (DHCP)) is connected via PoE to HG1 (Ethernet WAN). HG1 is connected to the EAS (Ethernet Aggregation Switch) via Port 1. The EAS is connected to an Ethernet switch via Port 1, labeled s-VID '1'. Host X.1 (IP: x.xxx (DHCP)) is connected to the Ethernet switch. A DHCP relay agent is connected to the Ethernet switch, which is also connected to a Server DHCP.

| + +##### 6.3.1.2.2 Check of QoS functions + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_QOS_01 | +| Test name | Marks of priority bits during processing of Ethernet frames which are not containing VLAN tags | +| Test purpose | Check if the EAS equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and not containing IEEE 802.1Q tags, assigned by user equipment | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user ports on the EAS equipment (two user lines) has to be used. On the user side the home gateway equipment has to be connected to the network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2.
6) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
7) A.1 and B.1 hosts use IPoE sessions.
8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually. | + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

10) A.1 and B.1 hosts should have possibility of priority assignment to Ethernet frames. A.1 and B.1 hosts should establish priority "6" for all transferred Ethernet frames.

11) HG1 and HG2 equipment should provide transparent translation of Ethernet frames priorities values configured on A.1 and B.1 hosts, accordingly. On HG1 equipment and HG2 there is disconnected the function of IEEE 802.1Q tags assignment to Ethernet frames transferred upstream.

12) On the EAS equipment there should be configured possibility of S-Tag assignment, including identifier "S-VID"=1, to Ethernet frames transferred upstream through any of users ports. In this case the general VLAN (N:1) should be configured for all users ports.

13) On the EAS equipment there should be configured user port No. 1 with the possibility of copying the priority value of Ethernet frame received from HG1 equipment, into the value of S-Tag priority.

14) On the EAS equipment should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:

  • – value of user port number (physical or logic);
  • – value of Ethertype field in the Ethernet frame;
  • – value of initial Ethernet frame priority received from HG2 equipment.

15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.

| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) During traffic exchange between hosts B.1 and X.1 perform transfer of ARP message from host B.1 (for this purpose it is necessary to clear contents of ARP table on host B.1).
  4. 4) Save the captures of traces in separate files ([Vendor]-EAS_QOS_01.txt) and put the file into the corresponding section of the KB.
  5. 5) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
  2. 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the EAS equipment for the given port.
  3. 3) Policy for different S-Tag definition criteria has been correctly performed.
  4. 4) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Test scheme diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 (Ethernet WAN) respectively. HG1 and HG2 are connected to Port 1 and Port 2 of an EAS device. Port 1 is labeled 'Copying of value of priority' and Port 2 is labeled 'Applying of policy Ingress to Egress'. The EAS device is connected to an Ethernet switch via Port 3, labeled 'S-Tag (S-VID 1*priority)'. Host X.1 is connected to the Ethernet switch via Port 4, labeled 'IP: xxxxx (DHCP)'. The Ethernet switch is also connected to a Server DHCP and a DHCP relay agent.

 graph LR     HA1[Host A.1
IP: xxxxx (DHCP)] -- "IPoE" --> HG1["HG1
(Ethernet WAN)"] HB1[Host B.1
IP: xxxxx (DHCP)] -- "IPoE" --> HG2["HG2
(Ethernet WAN)"] HG1 -- "Priority tagged frames/No VLAN tag" --> EAS["EAS"] HG2 -- "Priority tagged frames/No VLAN tag" --> EAS EAS -- "Port 1: Copying of value of priority" --> ES["Ethernet switch"] EAS -- "Port 2: Applying of policy Ingress to Egress" --> ES EAS -- "Port 3: S-Tag (S-VID 1*priority)" --> ES HX1[Host X.1
IP: xxxxx (DHCP)] -- "IP: xxxxx (DHCP)" --> ES ES --- SDHCP[Server DHCP] ES --- DRA[DHCP relay agent]
| + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_QOS_02 | +| Test name | Marks of priority bits during processing of Ethernet frames containing VLAN tags | +| Test purpose | Check if the EAS equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and containing IEEE 802.1Q tags, assigned by user equipment | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) has to be used. On the user side the home gateway equipment has to be connected to the network terminations of user lines (HG1 and HG2, accordingly).
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) Host B.1 is connected to home gateway HG2.
  6. 6) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
  7. 7) A.1 and B.1 hosts use IPoE sessions.
  8. 8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
  9. 9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.
  10. 10) HG1 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.
  11. 11) HG2 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.
  12. 12) On the EAS equipment should be configured the possibility of IEEE 802.1Q tags usage on users ports No. 1 and No. 2. The VLAN Membership List is configured on the EAS equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved value "C-VID" =1.
  13. 13) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through any of users ports. In this case, the general S-VLAN (N:1) should be configured for all users ports.
  14. 14) On the EAS equipment there should be configured user port No. 1 with the possibility of copying the priority value from IEEE 802.1Q tag, received from HG1 equipment, into the S-Tag priority value.
  15. 15) On the EAS equipment should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:
    • – value of user's port number (physical);
    • – C-VID value in the initial Ethernet frame;
    • – C-Tag priority value in the initial Ethernet frame.
  16. 16) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
| + +| | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.1.
  3. 3) Save the captures of traces in separate files ([Vendor]-EAS_QOS_02.txt) and put the file into the corresponding section of the KB.
  4. 4) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
  2. 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the EAS equipment for the given port.
  3. 3) Policy for different S-Tag definition criteria has been correctly performed.
  4. 4) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 respectively. HG1 and HG2 are connected to the EAS equipment. Host X.1 is connected to an Ethernet switch, which is connected to a Server DHCP and a DHCP relay agent. The EAS equipment has Port 1 and Port 2. Port 1 is connected to HG1 and Port 2 is connected to HG2. The diagram shows traffic flow from Host A.1 and Host B.1 through HG1 and HG2 to the EAS equipment, and then from the EAS equipment to Host X.1 via the Ethernet switch. The EAS equipment is configured with S-Tag (S-VID '1'+priority) for Port 1 and Port 2. The DHCP relay agent is connected to the Ethernet switch.

| + +##### 6.3.1.2.3 Check of security functions + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_SEC_01 | +| Test name | Blocking of broadcasting packages | +| Test purpose | Check if the EAS equipment has the possibility of blocking upstream and downstream broadcast messages | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the EAS equipment (one user lines) has to be used. On the user side the home gateway equipment has to be connected to the network terminations of user lines (HG1 equipment).
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
  6. 6) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
  7. 7) IP-addresses for hosts A.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.
  8. 8) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.
  9. 9) On the EAS equipment there should be configured blocking of broadcasting packages in an upstream direction for user port No. 1.
  10. 10) On the EAS equipment there should be configured blocking of broadcasting packages in downstream for "S-VID" =1.
| + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 11) Before beginning of carrying out of test procedure it is necessary to clear contents of ARP tables on hosts A.1 and X.1. | +| Test procedure | 1) Perform on host A.1 command ping for host X.1.
2) Perform on host X.1 command ping for host A.1.
3) Save the captures of traces in separate files ([Vendor]-EAS_SEC_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) Command ping, performed on host A.1 for host X.1 has not passed (broadcasting ARP message transferred by host A.1 has been blocked on the EAS equipment).
2) Command ping, performed on host X.1 for host A.1 has not passed (broadcasting ARP message transferred by host X.1 has been blocked on the EAS equipment).
3) In ARP tables on hosts A.1 and X.1 there are no dynamic records.
4) There is a possibility of broadcasting packages blocking function configuration on the EAS equipment in a downstream. Configuration of the given function is made on VLAN basis.
5) The daily report form has been saved in the corresponding section of KB. | +| Test scheme |

Image: Network diagram for the test scheme. Host A.1 (IP: xxxxx) is connected to HG1 (Ethernet WAN). HG1 is connected via Ethernet to Port 1 of the EAS equipment. The EAS equipment has a function of blocking broadcasting packages activated. Port 1 is connected via S-VID '1' to an Ethernet switch. Host X.1 (IP: xxxxx) is connected to the Ethernet switch.

| + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_SEC_02 | +| Test name | Restriction of the MAC-addresses table size | +| Test purpose | Check if the EAS equipment has the possibility of restriction of sources MAC-addresses number connected with one user port | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side the equipment of a home gateway (HG1 equipment) should be connected to the network termination of a user line.
4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.
5) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
6) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
7) IP-addresses for hosts A.1, A.2, A.3 and X.1 are configured manually (statically) and should be from one IP subnetwork. | + +| | | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

8) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.

9) On the EAS equipment should be configured the maximum number of MAC-addresses of the sources resolved for user port No. 1 equals to 2.

| +| Test procedure |

1) Perform consecutive connections of hosts A.1, A.2 and A.3.

2) During connection of each host (A.1, A.2, A.3) perform from this host continuous command ping for host X.1.

3) Save the captures of traces in separate files ([Vendor]-EAS_SEC_02.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Successful performance of commands ping from A.1 and A.2 hosts.

2) Unsuccessful performance of commands ping from host A.3.

3) There is a possibility of maximum resolved MAC-addresses number of sources configuration independently for each users ports.

4) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram for Test scheme. On the left, three hosts labeled Host A.1, Host A.2, and Host A.3, each with IP: xxxxx, are connected to a central box labeled HG1 (Ethernet WAN). HG1 is connected via an Ethernet cable to a box labeled EAS. The EAS box has a 'User port#1' with a note 'Admissible number of MAC-address of source' and 'Port 1'. A dashed line labeled 'S-VID '1'' connects Port 1 to an 'Ethernet switch' box. Host X.1, with IP: xxxxx, is connected to the Ethernet switch via a cable labeled 'S-VID '1''.

| + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_SEC_03 | +| Test name | Filtration on MAC-addresses basis | +| Test purpose | Check if the EAS equipment has the possibility to filter Ethernet frames based on source and destination MAC-addresses. | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side, the equipment of a home gateway (HG1 equipment) should be connected to the network termination of a user line.

4) A.1 and A.2 hosts are connected to home gateway HG1.

5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.

6) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).

7) IP-addresses for hosts A.1, A.2, X.1 and X.2 are configured manually (statically) and should be from one IP subnetwork. Hosts A.1/A.2 should have possibility to exchange traffic with hosts X.1/X.2 without router.

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

8) On the EAS equipment there should be configured S-Tag assignment possibility, including the identifier "S-VID"=1, to Ethernet frames transferred upstream through user port No. 1.

9) On the EAS equipment there should be activated function of Ethernet frames filtration for user port No. 1 MAC-addresses. For the given user port there should be configured barring for access from source with MAC-address of host A.2, and also barring for access to destination with MAC-address of host X.2.

| +| Test procedure |
  1. 1) Perform on host A.1 a command ping for host X.1.
  2. 2) Perform on host A.1 a command ping for host X.2.
  3. 3) Perform on host A.2 a command ping for host X.1.
  4. 4) Save the captures of traces in separate files ([Vendor]-EAS_SEC_03.txt) and put the file into the corresponding section of the KB.
  5. 5) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) Successful performance of command ping on host A.1 for host X.1.
  2. 2) Unsuccessful performance of command ping on host A.1 for host X.2.
  3. 3) Unsuccessful performance of command ping on host A.2 for host X.1.
  4. 4) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram for test scheme. Host A.1 and Host A.2 are connected to a home gateway labeled HG1 (Ethernet WAN). HG1 is connected via an Ethernet cable to the EAS equipment. The EAS equipment has a 'User port #1' which is activated for MAC address filtration. This port is connected via an S-VID '1' link to an Ethernet switch. Host X.1 and Host X.2 are connected to this switch. All hosts (A.1, A.2, X.1, X.2) are labeled with IP: xxxxx.

| + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_SEC_04 | +| Test name | Determination of duplicated users MAC-addresses | +| Test purpose | Check if the EAS equipment has the possibility of detecting duplicated user MAC-addresses and the subsequent mechanism for resolution of the given situation | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) has to be used. On user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) Host B.1 is connected to home gateway HG2.
  6. 6) Configure for host B.1 MAC-address similar to that is used by host A.1.
  7. 7) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
| + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).

9) IP-addresses for hosts A.1, B.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.

10) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through users ports No. 1 and No. 2.

11) Further adjustment of equipment should be provided according to one of the following configurations.

Configuration 1

In case of detection of duplicated MAC-addresses work of all users having identical MAC-addresses is permitted.

Configuration 2

In case of detection duplicated MAC addresses one of users with duplicated MAC addresses is blocked.

Configuration 3

In case of detection of duplicated MAC-addresses refusal in service should be given to both users with the duplicated MAC-addresses.

| +| Test procedure |

1) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 1).

2) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 2).

3) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 3).

4) Save the captures of traces in separate files ([Vendor]-EAS_SEC_04.txt) and put the file into the corresponding section of the KB.

5) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) In case of configuration 1:

  • – command ping, performed on host A.1 in direction to host X.1, passes;
  • – command ping, performed on host B.1 in direction to host X.1, passes.

2) In case of a configuration 2:

  • – command ping, performed on host A.1 in direction to host X.1, passes;
  • – command ping, performed on host B.1 in direction to host X.1, does not pass.

3) In case of configuration 3:

  • – command ping, performed on host A.1 in direction to host X.1, does not pass;
  • – command ping, performed on host B.1 in direction to host X.1, does not pass.

4) The daily report form has been saved in the corresponding section of KB.

| + +![Test scheme diagram showing network topology for DHCP Option 82 testing. Host A.1 and Host B.1 connect to HG1 and HG2 respectively. These connect to EAS ports 1 and 2. The EAS connects to an Ethernet switch, which also connects to Host X.1.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test scheme

|
 graph LR     subgraph " "     HA1[Host A.1
IP: x.x.x.x] -- Ethernet --- HG1[HG1
(Ethernet WAN)] HB1[Host B.1
IP: x.x.x.x
MAC Address Spoofing] -- Ethernet --- HG2[HG2
(Ethernet WAN)] end HG1 -- Ethernet --- EAS_P1[Port 1] HG2 -- Ethernet --- EAS_P2[Port 2] subgraph EAS EAS_P1 EAS_P2 end EAS_P1 -.-> EAS_OUT EAS_P2 -.-> EAS_OUT EAS_OUT[ ] -- S-VID '1' --- SW[Ethernet switch] SW -- S-VID '1' --- HX1[Host X.1
IP: x.x.x.x]
| +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Test scheme diagram showing network topology for DHCP Option 82 testing. Host A.1 and Host B.1 connect to HG1 and HG2 respectively. These connect to EAS ports 1 and 2. The EAS connects to an Ethernet switch, which also connects to Host X.1. + +##### 6.3.1.2.4 Check of functions of identification of subscriber lines + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_LID_01 | +| Test name | Support of DHCP Option 82 | +| Test purpose | Check if the EAS equipment has the possibility of functioning as DHCP Relay Agent second level and maintenance of DHCP clients identification connection points using an information option (option 82) | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
  6. 6) Host A.1 uses IPoE sessions. IP-address for host A.1 is defined dynamically using allocated DHCP server connected to the Ethernet switch. DHCP server supports option 82.
  7. 7) Router providing functionality (full) of DHCP Relay Agent should be connected to the Ethernet switch equipment.
  8. 8) EAS equipment works as DHCP Relay Agent second level.
  9. 9) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp.
| +| Test procedure |
  1. 1) Initiate on host A.1 an establishment of IPoE session (provide transfer of broadcasting DHCP request from host A.1).
  2. 2) Save the captures of traces in separate files ([Vendor]-EAS_LID_01.txt) and put the file into the corresponding section of the KB.
  3. 3) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) Using information option of DHCP protocol (option 82) EAS equipment has definitely identified to which client initiating DHCP request user line is connected within network of broadband access.
  2. 2) The daily report form has been saved in the corresponding section of KB.
| + +![Network diagram showing the test scheme. Host A.1 (IP: xxxxx (client DHCP)) is connected via IPoE to HG1 (Ethernet WAN). HG1 is connected via IPoE to the EAS (Layer 2 DHCP Relay Agent, Port 1). The EAS is connected to an Ethernet switch. The Ethernet switch is connected to a DHCP Relay Agent (full relay agent). The DHCP Relay Agent is connected to a Server DHCP.](7e14467740b2570a44379b347a697921_img.jpg) + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test scheme

|
 graph LR     HostA1[Host A.1
IP: xxxxx
(client DHCP)] -- IPoE --> HG1[HG1
(Ethernet WAN)] HG1 -- IPoE --> EAS[EAS
Layer 2 DHCP Relay Agent
Port 1] EAS --- ES[Ethernet switch] ES --- DRA[DHCP Relay Agent
(full relay agent)] DRA --- SDHCP[Server DHCP]
| +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Network diagram showing the test scheme. Host A.1 (IP: xxxxx (client DHCP)) is connected via IPoE to HG1 (Ethernet WAN). HG1 is connected via IPoE to the EAS (Layer 2 DHCP Relay Agent, Port 1). The EAS is connected to an Ethernet switch. The Ethernet switch is connected to a DHCP Relay Agent (full relay agent). The DHCP Relay Agent is connected to a Server DHCP. + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_LID_02 | +| Test name | PPPoE functions Intermediate Agent support | +| Test purpose | Check if the EAS equipment has the possibility of functioning as PPPoE Intermediate Agent for maintenance of user line identification | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
  4. 4) Host A.1 is connected to home gateway HG1.
  5. 5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
  6. 6) Host A.1 uses PPPoE sessions. IP-address for host A.1 is defined dynamically using allocated PPPoE server connected to the Ethernet switch.
  7. 7) Router providing functionality of PPPoE sessions termination is connected to the Ethernet switch equipment.
  8. 8) EAS equipment works as PPPoE Intermediate Agent.
  9. 9) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed.
| +| Test procedure |
  1. 1) Initiate on host A.1 an establishment of PPPoE session (perform PPPoE Discovery message transfer from host A.1).
  2. 2) Save the captures of traces in separate files ([Vendor]-EAS_LID_02.txt) and put the file into the corresponding section of the KB.
  3. 3) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) The EAS equipment adds PPPoE-TAG tag into the PPPoE Discovery packages (PADI, PADR) transferred upstream.
  2. 2) The given tag allows to definitely identify user line on which package PPPoE, and also specify user who has transferred the given message:
    • – "Agent Circuit ID" option should identify definitely EAS equipment within network of user's access, and also logic port of EAS equipment through which package PPPoE has been received;
    • – "Agent Remote ID" option should identify definitely user connected with corresponding logic port of EAS equipment through whom PPPoE package has been received.
| + +| | | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

3) The EAS equipment has not changed the initial MAC-addresses of source and destination in the PPPoE Discovery packages transferred upstream.

4) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme | Network diagram showing Host A.1 connected to HG1 via PPPoE, HG1 connected to EAS Port 1 via PPPoE, EAS connected to an Ethernet switch, and the switch connected to both a Server PPPoE and a PPPoE Termination icon.
 graph LR     HostA1["Host A.1
IP: x.x.x.x
(client PPPoE)"] -- PPPoE --> HG1["HG1
(Ethernet WAN)"] HG1 -- PPPoE --> EAS["EAS
PPPoE Intermediate Agent
Port 1"] EAS --- Switch[Ethernet switch] Switch --- Server[Server PPPoE] Switch --- Term[PPPoE Termination]
| + +##### 6.3.1.2.5 Check of functions of management, monitoring and statistics gathering + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_MNG_01 | +| Test name | Equipment monitoring by SNMP protocol | +| Test purpose | Check if the EAS equipment has the possibility for remote monitoring by means of control system using SNMP protocol | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) For carrying out the tests, two user's ports on the EAS equipment (two user lines) has to be used. On the user side home gateways equipment should be connected to network terminations of user lines (HG1 and HG2, accordingly).

4) Host A.1 is connected to home gateway HG1.

5) Host B.1 is connected to home gateway HG2.

6) HG1 and HG2 equipment work in a bridged mode (function of local DHCP server is disconnected).

7) IP-addresses for A.1 and B.1 hosts are configured manually.

8) Host which performs functions of remote workstation of control system is connected to the Ethernet switch. On the given host SNMP software is established. IP-address for specified host should be configured manually and there should be from the same subnetwork, as IP-address of EAS equipment used for interaction with control system.

9) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: SNMP.

| +| Test procedure |

1) Initiate remote monitoring of EAS equipment on host, carrying out functions of workstation of a control system.

2) Provide appearance of emergency and other non-standard situations on the EAS equipment. Also it is necessary to simulate problems with powering (transition to the reserve block, return to mainframe), problems with interfaces (refusal of physical / channel level), connection of remote users to EAS equipment on Telnet/SSH/SNMP, change of equipment configuration on Telnet/SSH/SNMP and other events.

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

3) Save the captures of traces in separate files ([Vendor]-EAS_MNG_01.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) During the process of monitoring EAS equipment gives the adequate information on condition of interfaces, operative memory and central processor.

2) The EAS equipment provides transfer of adequate SNMP traps/informs messages in case of emergencies occurrence.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Diagram of the test scheme. A central EAS device has two ports, Port 1 and Port 2. Port 1 is connected via Ethernet to an HG1 (Ethernet WAN) unit, which is connected to Host A.1 (IP: xxxxx). Port 2 is connected via Ethernet to an HG2 (Ethernet WAN) unit, which is connected to Host B.1 (IP: xxxxx). Additionally, the EAS device is connected via Ethernet to an Ethernet switch. A Remote CLI (laptop, IP: xxxxx) is connected to the Ethernet switch and has a dashed arrow labeled 'SNMP' pointing to the EAS device's IP: xxxxx.

| + +##### 6.3.1.2.6 Check of functions of Multicast mode support + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_MC_01 | +| Test name | Connection of several users to one multicasting group | +| Test purpose | Check if the EAS equipment has the possibility of simultaneous connection of several users to one multicasting group without subsequent load increase at network interfaces of EAS equipment | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) For carrying out the tests, three user ports on the EAS equipment (three user lines) has to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 equipment, HG2 and HG3, accordingly).

4) Host A.1 is connected to home gateway HG1.

5) Host B.1 is connected to home gateway HG2.

6) Host C.1 is connected to home gateway HG3.

7) HG1 equipment, HG2 and HG3 work in the bridged mode (function of local DHCP server is disconnected).

8) On hosts A.1, B.1 and C.1 IP STB software should be used. Hosts A.1, B.1 and C.1 are IGMP hosts. IP-addresses for hosts A.1, B.1 and C.1 are configured manually.

9) Hosts A.1, B.1 and C.1 use IPoE sessions.

10) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.

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

11) Router equipment performing functions of IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM-SSM protocol is used.

12) EAS equipment during processing of IGMP messages works in the transparent IGMP Snooping mode.

13) On the EAS equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the EAS equipment should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from users IP-STB equipment.

14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.

| +| Test procedure |

1) Hosts A.1, B.1 and C.1 should initiate IPoE sessions, transfer IGMP Membership Report messages and, thus, should consistently connect to the same multicasting group (observe one video channel).

2) Save the captures of traces in separate files ([Vendor]-EAS_MC_01.txt) and put the file into the corresponding section of the KB.

3) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) All users have connections to the same multicasting group (observe one video channel).

2) During consecutive connections of hosts B.1 and C.1 there is no additional load on network interfaces of EAS equipment.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram for Test scheme. Three hosts (Host A.1, Host B.1, Host C.1) labeled as IP-STB and IGMP host with IP:xxxx are connected via IPoE to home gateways HG1, HG2, and HG3 (labeled Ethernet WAN). These gateways are connected via Ethernet (IPoE) to the EAS equipment. The EAS equipment has three ports (Port 1, Port 2, Port 3) and is configured for IGMP transparent snooping. Port 3 is connected via MC-VLAN (S-VID 1) to an Ethernet switch. The switch is connected to an IGMP router labeled PIM-SSM. A video server (Host X.1) with IP:xxxx is also connected to the Ethernet switch.

| + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_MC_02 | +| Test name | Restriction of channels number which are simultaneously observed by the user | +| Test purpose | Check if the EAS equipment has the possibility of multicasting groups total number restriction to which one user simultaneously can be connected | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.

4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.

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

5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected). HG1 equipment should support the IGMP Snooping function.

6) On hosts A.1, A.2 and A.3 IP STB software should be used. Hosts A.1, A.2 and A.3 are IGMP hosts. IP-addresses for hosts A.1, A.2 and A.3 are configured manually.

7) Hosts A.1, A.2 and A.3 use IPoE sessions.

8) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.

9) Router equipment which performs functions of IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM SSM protocol is used.

10) EAS equipment during processing of IGMP messages functions in the transparent IGMP Snooping mode.

11) On the EAS equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the EAS equipment there should be configured a possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.

12) On the EAS equipment there should be configured for user port No. 1 restriction on total number of multicasting groups to which the given user can be connected. Maximum number of multicasting groups for the given user should be equal to 2.

13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.

| +| Test procedure |

1) Hosts A.1, A.2 and A.3 should consistently initiate IPoE sessions and transfer IGMP Membership Report messages, trying to be connected to various multicasting groups.

2) Save the captures of traces in separate files ([Vendor]-EAS_MC_02.txt) and put the file into the corresponding section of the KB.

3) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) A.1 and A.2 hosts are successfully connected to various multicasting groups.

2) Host A.3 has no connections to new multicasting group.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram showing the test scheme. On the left, three hosts (Host A.1, Host A.2, Host A.3) labeled as IP-STB and IGMP hosts with IP: x.x.x.x are connected to an HG1 (Ethernet WAN) device. The HG1 is connected via an Ethernet (PoE) cable to Port 1 of an EAS (Ethernet Aggregation Switch) device. The EAS device has a 'User port #1' and a 'Multicast VLAN (S-VID 1)'. The EAS is connected via a dashed line labeled 'MC-VLAN(S-VID 1)' to an Ethernet switch. Host X.1 (video server) with IP: x.x.x.x is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router labeled PIM-SSM.

| + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | EAS_MC_03 | +| Test name | Restriction of the multicast groups list accessible to the user | +| Test purpose | Check if the EAS equipment has the possibility of restriction of the multicast groups list accessible to the specified user | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.

4) Host A.1 is connected to home gateway HG1.

5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).

6) On host A.1 IP-STB software should be used. Host A.1 should be IGMP host. IP-address for host A.1 should be configured manually.

7) Host A.1 uses IPoE sessions.

8) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.

9) Router equipment which performs functions of IGMP router should be connected to the Ethernet switch equipment. For routing of multicast traffic PIM-SSM protocol is used.

10) EAS equipment during processing of IGMP messages functions in the transparent IGMP Snooping mode.

11) On the EAS equipment should be configured uniform multicast VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the EAS equipment there should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.

12) On the EAS equipment there should be configured for user port No. 1 the multicast groups list accessible to user.

13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.

| +| Test procedure |

1) Host A.1 should initiate IPoE session and transfer IGMP Membership Report messages, trying to be consistently connected to various multicast groups, matching the list of resolved groups, and not matching the given list.

2) Save the captures of traces in separate files ([Vendor]-EAS_MC_03.txt) and put the file into the corresponding section of the KB.

3) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Host A.1 has been successfully connected to various multicast groups matching list of groups, resolved for user port No. 1.

2) Host A.1 has no connections to any of multicast groups which are not matching the list of groups, resolved for user port No. 1.

3) The daily report form has been saved in the corresponding section of KB.

| + +![Network diagram showing the test scheme. Host A.1 (IP-STB) with IP: xxxxx (IGP host) is connected to HG1 (Ethernet WAN). HG1 is connected via Ethernet (IPoE) to Port 1 of the EAS (Ethernet Access Switch). The EAS has a 'User port#1' with a 'List of resolved multiexclusive groups'. Port 1 is connected via MC-VLAN (S-VID '1') to an Ethernet switch. Host X.1 (video server) with IP: xxxxx is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router PIM-SSM.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +**Test scheme** + +Network diagram showing the test scheme. Host A.1 (IP-STB) with IP: xxxxx (IGP host) is connected to HG1 (Ethernet WAN). HG1 is connected via Ethernet (IPoE) to Port 1 of the EAS (Ethernet Access Switch). The EAS has a 'User port#1' with a 'List of resolved multiexclusive groups'. Port 1 is connected via MC-VLAN (S-VID '1') to an Ethernet switch. Host X.1 (video server) with IP: xxxxx is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router PIM-SSM. + +#### 6.3.1.3 Check of functionality of BRAS equipment + +##### 6.3.1.3.1 Check of functions of VLAN tags processing + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_VLAN_01 | +| Test name | Assignment of the S-Tag tag to the Ethernet frames transferred downstream | +| Test purpose | Check if the BRAS equipment can assign the S-Tag to the unmarked Ethernet frames transferred downstream | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet Switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
  4. 4) For carrying out the tests, two user's ports on the DSLAM/MSAN/EAS equipment (two user lines) has to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
  5. 5) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
  6. 6) A.1 and A.2 hosts are connected to home gateway HG1.
  7. 7) B.1 and B.2 hosts are connected to the home gateway equipment HG2.
  8. 8) A.1 and B.1 hosts use PPPoE sessions.
  9. 9) A.2 and B.2 hosts use IPoE sessions.
  10. 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually. For termination of PPPoE sessions from A.1 and B.1 hosts BRAS equipment is used.
  11. 11) IP-addresses for A.2 and B.2 hosts are assigned dynamically with the allocated DHCP server or are configured manually. In case of dynamic assignment of IP-addresses for A.2 and B.2 hosts BRAS equipment works as DHCP Relay Agent.
  12. 12) X.1 and X.2 hosts are connected to the Ethernet switch equipment. IP-addresses for X.1 and X.2 hosts are configured manually.
| + +- 13) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic. +- 14) Further adjustment of equipment should be provided according to one of the following configurations. + +###### *Configuration 1 (1:1 VLAN)* + +BRAS equipment should be configured to enable the assignment of S-VLAN tags to unmarked Ethernet frames transferred downstream. Following options should be configured: + +- assignment "S-VID"=1 Ethernet frames connected with PPPoE session of host A.1 (user's port No. 1 on the access node equipment); +- assignment "S-VID"=2 Ethernet frames connected with IPoE session of host A.2 (user's port No. 1 on the access node equipment); +- assignment "S-VID"=3 Ethernet frames connected with PPPoE session of host B.1 (user's port No. 2 on the access node equipment); +- assignment "S-VID"=4 Ethernet frames connected with IPoE session of host B.2 (user's port No. 2 on the access node equipment). + +S-VLAN options for DSLAM/MSAN/EAS equipment, and also on the Ethernet switch equipment are configured according to S-VLAN options for BRAS equipment. + +###### *Configuration 2 (VLAN on the user)* + +BRAS equipment should be configured to enable assignment of S-VLAN tags to unmarked Ethernet frames transferred downstream. Following options should be configured: + +- assignment "S-VID"=1 Ethernet frames connected with all sessions (PPPoE/IPoE) of HG1 equipment (user port No. 1 on the access node equipment); +- assignment "S-VID"=2 Ethernet frames connected with all sessions (PPPoE/IPoE) of HG2 equipment (user port No. 2 on the access node equipment). + +S-VLAN options for DSLAM/MSAN/EAS equipment, and also on Ethernet switch equipment, are configured according to S-VLAN options for BRAS equipment. + +###### *Configuration 3 (VLAN on service)* + +BRAS equipment should be configured to enable assignment of S-VLAN tags to unmarked Ethernet frames transferred downstream. Following options should be configured: + +- assignment "S-VID"=1 Ethernet frames connected with PPPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment; +- assignment "S-VID"=2 Ethernet frames connected with IPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment. + +S-VLAN options for DSLAM/MSAN/EAS equipment, and also on the Ethernet switch equipment, are configured according to S-VLAN options for BRAS equipment. + +- 15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed || bootp || ICMP. + +| | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test procedure

|
  1. 1) For configuration 1 perform traffic exchange between hosts A.1 and X.1, A.2 and X.2, B.1 and X.1, B.2 and X.2.
  2. 2) For configuration 2 perform traffic exchange between hosts A.1 and X.1, A.2 and X.2, B.1 and X.1, B.2 and X.2.
  3. 3) For configuration 3 perform traffic exchange between hosts A.1 and X.1, A.2 and X.2, B.1 and X.1, B.2 and X.2.
  4. 4) Save the captures of traces in separate files ([Vendor]-BRAS_VLAN_01.txt) and put the file into the corresponding section of the KB.
  5. 5) Fill in a daily report form with the testing results and save it in the KB.
| +|

Expected result

|
  1. 1) During use of configuration 1 BRAS equipment performs assignment of S-VLAN identifiers as follows:
    • – assignment of identifier "S-VID"=1 Ethernet frames transferred downstream and connected with PPPoE session of host A.1;
    • – assignment of identifier "S-VID"=2 Ethernet frames transferred downstream and connected with IPoE session of host A.2;
    • – assignment of identifier "S-VID"=3 Ethernet frames transferred downstream and connected with PPPoE session of host B.1;
    • – assignment of identifier "S-VID"=4 Ethernet frames transferred downstream and connected with IPoE session of host B.2.
  2. 2) During use of configuration 2 BRAS equipment performs assignment of S-VLAN identifiers as follows:
    • – assignment of identifier "S-VID"=1 Ethernet frames transferred downstream and connected with all PPPoE/IPoE sessions of HG1 equipment (passing through user's port No. 1 DSLAM/MSAN/EAS equipment);
    • – assignment of identifier "S-VID"=2 Ethernet frames transferred downstream and connected with all PPPoE/IPoE sessions of HG2 equipment (passing through user's port No. 2 DSLAM/MSAN/EAS equipment).
  3. 3) BRAS equipment performs assignment of S-VLAN identifiers as follows:
    • – assignment of identifier "S-VID"=1 Ethernet frames transferred downstream and connected with PPPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment;
    • – assignment of identifier "S-VID"=2 Ethernet frames transferred downstream and connected with IPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment.
  4. 4) The daily report form has been saved in the corresponding section of KB.
| +|

Test scheme

|

Image: Test scheme diagram showing Host A.1, Host A.2, Host B.1, Host B.2 connected to HG1 and HG2 respectively. HG1 and HG2 are connected to a DSLAM/MSAN/EAS unit. The DSLAM/MSAN/EAS unit is connected to an Ethernet switch, which is connected to a BRAS unit. Host X.1 and Host X.2 are connected to the Ethernet switch. A protocol analyzer is connected to the BRAS unit. The diagram illustrates the network configuration for testing VLAN assignments.

The diagram illustrates the test scheme. On the left, Host A.1 (IP: xxxx (PPPoE)) and Host A.2 (IP: xxxx (IPoE)) are connected to HG1. Host B.1 (IP: xxxx (PPPoE)) and Host B.2 (IP: xxxx (IPoE)) are connected to HG2. HG1 and HG2 are connected to a DSLAM/MSAN/EAS unit via Ethertype PPP, IP. The DSLAM/MSAN/EAS unit has two ports, Port 1 and Port 2, connected to an Ethernet switch. The Ethernet switch is connected to a BRAS unit via an S-VLAN link. Host X.1 (IP: xxxx) and Host X.2 (IP: xxxx) are also connected to the Ethernet switch. A protocol analyzer is connected to the BRAS unit, which performs PPPoE Termination and IPoE. The Ethernet switch contains an S-VLAN bridge and an S-Tag attach point.

| + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_VLAN_02 | +| Test name | Configuration of S-VLAN/C-VLAN stack (QinQ) | +| Test purpose | Check if the BRAS has the possibility of assigning the VLAN tag pair (S-Tag/C-Tag) to the Ethernet frame, which is transferred upstream | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet Switch performs aggregation of the traffic from access nodes.
  4. 4) For carrying out the tests, one access node has to be used. As access node DSLAM/MSAN/EAS equipment can be used.
  5. 5) For carrying out the tests, two user's ports on the DSLAM/MSAN/EAS equipment (two user lines) has to be used. On the user side the home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
  6. 6) HG1 and HG2 equipment works in a bridged mode (function of local DHCP server is disconnected).
  7. 7) Host A.1 is connected to the home gateway equipment HG1.
  8. 8) Host B.1 is connected to the home gateway equipment HG2.
  9. 9) A.1 and B.1 hosts use IPoE sessions.
  10. 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically with the allocated DHCP server or are configured manually. In case of dynamic assignment of IP-addresses for A.2 and B.2 hosts BRAS equipment works as DHCP Relay Agent.
  11. 11) X.1 and X.2 hosts are connected to the Ethernet switch equipment. IP-addresses for X.1 and X.2 hosts are configured manually.
  12. 12) In the case when for carrying out of test there is DSLAM/MSAN equipment used, on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
  13. 13) BRAS equipment should be configured S-VLAN/C VLAN pair assignment to unmarked Ethernet frames transferred downstream. Following options should be configured:
    • – assignment "S-VID"=1, "C-VID"=1 Ethernet frames connected with all PPPoE sessions/IPoE of HG1 equipment (the identifier "S-VID"=1 is the general for all users connected to DSLAM/MSAN/EAS equipment; identifier "C-VID" =1 characterizes the concrete user – user's port No. 1 on the DSLAM/MSAN/EAS equipment);
    • – assignment "S-VID"=1, "C-VID"=2 Ethernet frames connected with all PPPoE sessions/IPoE of HG2 equipment (the identifier "S-VID"=1 is the general for all users connected to DSLAM/MSAN/EAS equipment; identifier "C-VID"=2 characterizes concrete user – user's port No. 2 on the DSLAM/MSAN/EAS equipment).
  14. 14) S-VLAN/C-VLAN options for DSLAM/MSAN/EAS equipment are configured according to S-VLAN/C-VLAN options for BRAS equipment.
  15. 15) Ethernet switch S-VLAN options are configured according to S-VLAN options for BRAS equipment and DSLAM/MSAN/EAS equipment.
  16. 16) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp ICMP.
| + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure |
  1. 1) Perform traffic exchange between hosts A.1 and X.1.
  2. 2) Perform traffic exchange between hosts B.1 and X.2.
  3. 3) Save the captures of traces in separate files ([Vendor]-BRAS_VLAN_02.txt) and put the file into the corresponding section of the KB.
  4. 4) Fill in a daily report form with the testing results and save it in the KB.
| +| Expected result |
  1. 1) The BRAS equipment has assigned the identifier "S-VID"=1, "C-VID"=1 for Ethernet frames which are transferred upstream and related to IPoE session of host A.1.
  2. 2) The BRAS equipment has assigned the identifier "S-VID"=1, "C-VID"=2 for Ethernet frames which are transferred upstream and related to IPoE session of host B.1.
  3. 3) The daily report form has been saved in the corresponding section of KB.
| +| Test scheme |

Image: Network diagram showing Host A.1 connected to HG1, which is connected to DSLAM/MSAN/EAS via IPoE. Host B.1 is connected to HG2, which is also connected to DSLAM/MSAN/EAS via IPoE. The DSLAM/MSAN/EAS is connected to an Ethernet switch via Port 1 and Port 2. The Ethernet switch is connected to a BRAS via S-VLAN-C-VLAN and S-Tag-C-Tag attach. The BRAS is connected to a Protocol analyzer and a Termination IPoE. Host X.1 and Host X.2 are connected to the Ethernet switch via IP:xxxx.

| + +##### 6.3.1.3.2 Check of security functions + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_SEC_01 | +| Test name | Prevention of substitution of user's IP-address | +| Test purpose | Check if the BRAS equipment has the possibility of prevention of attacks from outside the malicious users connected with substitution of the IP-address of a source (source IP spoofing) | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of the traffic from access nodes.
  4. 4) For carrying out the tests, one access node has to be used. As access node DSLAM/MSAN/EAS equipment can be used.
  5. 5) For carrying out the tests, one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used.
  6. 6) On the user side the equipment of a home gateway (HG1 equipment) should be connected to the network termination of a user line. HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
  7. 7) Host A.1 is connected to the home gateway equipment HG1. Host A.1 uses IPoE sessions.
  8. 8) IP-address for host A.1 is assigned dynamically with allocated DHCP server. BRAS equipment works as DHCP Relay Agent. DHCP server is connected to the Ethernet switch.
| + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

9) Host X.1 is connected to the Ethernet switch equipment. The IP-address for host X.1 should be configured manually.

10) In the case when for carrying out of test there is DSLAM/MSAN equipment used, on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.

11) On the DSLAM/MSAN/EAS equipment, BRAS equipment and Ethernet switch equipment should be configured S-VLAN with identifier "S-VID"=1.

12) On the DSLAM/MSAN/EAS equipment function of blocking of broadcasting messages should be disconnected.

13) Before beginning of the test host A.1 should establish IPoE session and using DHCP server should receive IP address.

14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ARP bootp ICMP.

| +| Test procedure |

1) Clear contents of ARP table on host A.1.

2) Clear contents of ARP table on BRAS equipment.

3) Perform on host A.1 command ping for host X.1.

4) Check-up records of ARP table on BRAS equipment.

5) Break off IPoE session for host A.1.

6) Perform repeated establishment of IPoE session for host A.1 (allocation of the IP address by means of DHCP).

7) Save the captures of traces in separate files ([Vendor]-BRAS_SEC_01.txt) and put the file into the corresponding section of the KB.

8) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) On termination of command ping passage in ARP table of BRAS equipment there is no record related with MAC-address of host A.1.

2) After repeated establishment of IPoE connection in ARP table of BRAS equipment should be generated new dynamic record related with MAC-address of host A.1

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram showing the test setup. Host A.1 (IP: x.xxx) is connected to HG1, which is connected to Port 1 of the DSLAM/MSAN/EAS. The DSLAM/MSAN/EAS is connected to an Ethernet switch via a dashed line labeled 'S-VID 1'. The Ethernet switch is connected to a Server DHCP and to a BRAS via a dashed line labeled 'S-VID 1'. The BRAS is connected to a DHCP Relay Agent. Host X.1 (IP: x.xxx) is connected to the Ethernet switch.

 graph LR     A1[Host A.1
IP: x.xxx] --- HG1[HG1] HG1 --- P1[Port 1] subgraph DSLAM [DSLAM/MSAN/EAS] P1 end P1 -.-> S-VID 1 ES[Ethernet switch] ES --- SDHCP[Server DHCP] ES -.-> S-VID 1 BRAS[BRAS] BRAS --- DRA[DHCP Relay Agent] X1[Host X.1
IP: x.xxx] --- ES
| + +##### 6.3.1.3.3 Check of functions of management, monitoring and statistics gathering + +| | | +|---------------------|--------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_MNG_01 | +| Test name | Equipment monitoring by SNMP protocol | +| Test purpose | Check if the BRAS equipment has the possibility for remote monitoring by means of the control system using SNMP protocol | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes.
4) Host which performs functions of a remote workstation of control system is connected to the Ethernet switch. On the given host SNMP software is established. IP-address for specified host should be configured manually and should be from the same subnetwork, as the IP-address of BRAS equipment used for interaction with the control system.
5) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: report SNMP. | +| Test procedure | 1) Initiate remote monitoring of BRAS equipment on host, carrying out functions of workstation of a control system.
2) Provide appearance of emergency and other non-standard situations on the BRAS equipment. Also it is necessary to simulate problems with powering (transition to the reserve block, return to mainframe), problems with interfaces (refusal of physical / channel level), connection of remote users to BRAS equipment on Telnet/SSH/SNMP, change of equipment configuration on Telnet/SSH/SNMP and other events.
3) Save the captures of traces in separate files ([Vendor]-BRAS_MNG_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) During the process of monitoring BRAS equipment gives the adequate information on condition of interfaces, operative memory and central processor.
2) The BRAS equipment provides transfer of adequate SNMP traps/informs messages in case of emergencies occurrence.
3) The daily report form has been saved in the corresponding section of KB. | +| Test scheme |

Image: Diagram of the test scheme showing a Remote CLI (laptop) connected to an Ethernet switch, which is connected to a DSLAM/MSAN/EAS and a BRAS. The Remote CLI is sending SNMP messages to the BRAS.

 graph LR     RemoteCLI[Remote CLI
IP:xxxx] --- EthernetSwitch[Ethernet switch] DSLAM[DSLAM/MSAN/EAS] --- EthernetSwitch EthernetSwitch --- BRAS[BRAS
IP:xxxx(MNG)] RemoteCLI -.-> SNMP BRAS
| + +##### 6.3.1.3.4 Check of functions of Multicast mode support + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_MC_01 | +| Test name | Restriction of number of multicasting groups | +| Test purpose | Check if the BRAS equipment has the possibility of restriction of total number of the multicasting groups transferred within S-VLAN (MC-VLAN) | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme. | + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.

4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.

5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.

6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected). HG1 equipment should support the IGMP Snooping function.

7) Hosts A.1, A.2 and A.3 are connected to home gateway HG1. On hosts A.1, A.2 and A.3 IP STB software should be used. Hosts A.1, A.2 and A.3 are IGMP hosts (clients). IP-addresses for hosts A.1, A.2 and A.3 are configured manually. Hosts A.1, A.2 and A.3 use IPoE sessions.

8) Host X.1 is connected to the Ethernet switch equipment. Host X.1 performs functionality of video server, being video traffic source. The IP-address for host X.1 should be configured manually.

9) BRAS equipment works as IGMP router. For routing of the multicasting traffic report PIM SSM is used.

10) DSLAM/MSAN/EAS equipment during processing of IGMP messages works in the mode of transparent IGMP Snooping. On the DSLAM/MSAN/EAS equipment function of restriction of number of multicasting groups accessible to users should disconnected.

11) On BRAS equipment, DSLAM/MSAN/EAS equipment and Ethernet switch equipment the S-VLAN (MC-VLAN: "S-VID"=1) should be configured, intended for carrying out of multicasting traffic to all users connected to access node.

12) On BRAS equipment for MC-VLAN ("S-VID"=1) should be configured restriction of total number of the multicasting groups transferred within MC-VLAN. Maximum number of multicasting groups for MC VLAN should equals to 2.

13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.

| +| Test procedure |

1) Hosts A.1, A.2 and A.3 should consistently initiate IPoE sessions, transfer IGMP Membership Report messages and try to connect to various multicasting groups.

2) Save the captures of traces in separate files ([Vendor]-BRAS_MC_01.txt) and put the file into the corresponding section of the KB.

3) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) A.1 and A.2 hosts are successfully connected to various multicasting groups.

2) Host A.3 has no connections to new multicasting group.

3) There is a possibility of configuration on BRAS equipment of maximum bandwidth with which it is supposed to occupy within MC-VLAN by transfer of multicasting streams.

4) The daily report form has been saved in the corresponding section of KB.

| + +![Network diagram showing the test scheme. On the left, three hosts (Host A.1, Host A.2, Host A.3) labeled as IP-STB and IGMP hosts are connected to a home gateway (HG1). HG1 is connected to Port 1 of a DSLAM/MSAN/EAS unit. A dashed line labeled 'MC-VLAN (S-VID 11)' connects Port 1 to an Ethernet switch. Host X.1 (video server) is connected to the Ethernet switch. The Ethernet switch is connected to a BRAS unit via another dashed line labeled 'MC-VLAN (S-VID 11)'. The BRAS unit is labeled as an IGMP router PIM-SSM.](e2dad48ec062e71202459a9ab82261e4_img.jpg) + +**Test scheme** + +Network diagram showing the test scheme. On the left, three hosts (Host A.1, Host A.2, Host A.3) labeled as IP-STB and IGMP hosts are connected to a home gateway (HG1). HG1 is connected to Port 1 of a DSLAM/MSAN/EAS unit. A dashed line labeled 'MC-VLAN (S-VID 11)' connects Port 1 to an Ethernet switch. Host X.1 (video server) is connected to the Ethernet switch. The Ethernet switch is connected to a BRAS unit via another dashed line labeled 'MC-VLAN (S-VID 11)'. The BRAS unit is labeled as an IGMP router PIM-SSM. + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_MC_02 | +| Test name | Providing statistics of multicasting traffic | +| Test purpose | Check if the BRAS equipment has the possibility of providing statistics concerning multicasting traffic for each MC-VLAN and each multicasting group | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of the traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
  4. 4) For carrying out the tests three user ports on the DSLAM/MSAN/EAS equipment (three user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 equipment, HG2 and HG3, accordingly).
  5. 5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 and HG3 equipment and DSLAM/MSAN equipment one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
  6. 6) HG1 equipment, HG2 and HG3 work in the bridge mode (function of local DHCP server is disconnected). HG1 equipment, HG2 and HG3 support function IGMP Snooping.
  7. 7) Host A.1 is connected to home gateway HG1.
  8. 8) Host B.1 is connected to home gateway HG2.
  9. 9) Host C.1 is connected to home gateway HG3.
  10. 10) On hosts A.1, B.1 and C.1 IP STB software should be used. Hosts A.1, B.1 and C.1 are IGMP hosts (clients). IP-addresses for hosts A.1, B.1 and C.1 are configured manually. Hosts A.1, B.1 and C.1 use IPoE sessions.
  11. 11) Host X.1 is connected to Ethernet switch equipment. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
  12. 12) BRAS equipment works as IGMP router. For routing of the multicasting traffic report PIM SSM is used.
  13. 13) DSLAM/MSAN/EAS equipment processing of IGMP messages works in the transparent IGMP Snooping mode.
| + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

14) On the DSLAM/MSAN/EAS equipment, and also on BRAS equipment function of restriction of admissible number of multicasting groups should be disconnected.

15) On BRAS equipment, DSLAM/MSAN/EAS equipment and Ethernet switch equipment the S VLAN (MC-VLAN: "S-VID"=1) should be configured to enable the delivery of multicasting traffic to all users connected to access node.

| +| Test procedure |

1) Perform consecutive connection of each host (A.1, B.1 and C.1) to various multicasting groups.

2) Perform periodic switching between multicasting groups on everyone each host (A.1, B.1 and C.1).

3) Save the captures of traces in separate files ([Vendor]-BRAS_MC_02.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) During test procedure performance BRAS equipment gives adequate information related with the following statistics:

  • – for each MC-VLAN: current number of active multicasting groups; total number of attempts for users joining to multicasting groups (including successful/unsuccessful); total number of messages related with switching-off from multicasting groups; total number of the transferred inquiries – Queries (including general queries/specific queries); total number of received incorrect messages IGMP;
  • – for each multicasting group (within defined MC VLAN): present total number of active hosts.

2) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram for the test scheme. On the left, three hosts (Host A.1, Host B.1, Host C.1) are connected to a central DSLAM/MSAN/EAS unit via HG1, HG2, and HG3 respectively. Each host is labeled as an IP-STB and an IGMP host with IP:xxxx. The DSLAM/MSAN/EAS unit has three ports (Port 1, Port 2, Port 3) connected to the hosts and a dashed line representing an MC-VLAN (S-VID 1) connection to an Ethernet switch on the right. The Ethernet switch is connected to a BRAS unit, which is further connected to an IGMP router (PIM-SSM). A video server (Host X.1) is also connected to the Ethernet switch.

| + +##### 6.3.1.3.5 Accounting and management of access policy + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_ACC_01 | +| Test name | Establishment of PPPoE session | +| Test purpose | Check if the BRAS equipment has the possibility of PPPoE user sessions establishment | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

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

3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.

4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side the equipment of a home gateway (HG1 equipment) should be connected to network termination of a user line.

5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.

6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).

7) Host A.1 is connected to the home gateway equipment HG1.

8) Host A.1 uses PPPoE sessions. The IP-address for host A.1 is assigned dynamically.

9) Host X.1 is connected to the Ethernet switch equipment. The IP-address for host X.1 should be configured manually.

10) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server. BRAS equipment contain IP-addresses pool for dynamic assignment during establishment of users' sessions.

11) Subscribers authentication performed on allocated AAA server.

12) AAA Server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on host A.1.

13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed bootp PPP ICMP RADIUS.

| +| Test procedure |

1) Initiate an establishment of PPPoE session on host A.1 (enter correct values of username and password).

2) Perform data exchange between hosts A.1 and X.1.

3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_01.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Successful user authentication on host A.1 and subsequent establishment of PPPoE session. Host A.1 has received the IP-address from pool of addresses located on BRAS equipment.

2) Correctness of PPPoE messages transferred by BRAS equipment in direction to host A.1.

3) Correctness of RADIUS messages transferred by BRAS equipment in direction to AAA server.

4) There is a data exchange possibility between hosts A.1 and X.1.

5) The daily report form has been saved in the corresponding section of KB.

| + +![Network diagram for the test scheme. Host A.1 (IP: xxxxx (client PPPoE)) is connected to HG1 (bridged mode). HG1 is connected to DSLAM/MSAN/EAS via PPPoE. DSLAM/MSAN/EAS has Port 1 connected to an Ethernet switch via S-VID '1'. Host X.1 (IP: xxxxx) is also connected to the Ethernet switch. The Ethernet switch is connected to a Server AAA and a BRAS (PPPoE Server) via S-VID '1-1'. The BRAS is connected to the Server AAA via RADIUS.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +| | | +|--------------------|--| +| Test scheme | | +|--------------------|--| + +Network diagram for the test scheme. Host A.1 (IP: xxxxx (client PPPoE)) is connected to HG1 (bridged mode). HG1 is connected to DSLAM/MSAN/EAS via PPPoE. DSLAM/MSAN/EAS has Port 1 connected to an Ethernet switch via S-VID '1'. Host X.1 (IP: xxxxx) is also connected to the Ethernet switch. The Ethernet switch is connected to a Server AAA and a BRAS (PPPoE Server) via S-VID '1-1'. The BRAS is connected to the Server AAA via RADIUS. + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_ACC_02 | +| Test name | Establishment of IPoE session | +| Test purpose | Check if the BRAS equipment has the possibility of establishment of user IPoE (DHCP) sessions | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node has to be used. As access node, DSLAM/MSAN/EAS equipment can be used.
  4. 4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
  5. 5) If there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN, one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
  6. 6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
  7. 7) Host A.1 is connected to home gateway HG1.
  8. 8) Host A.1 uses IPoE sessions. The IP-address for host A.1 is defined dynamically using allocated DHCP server connected to the Ethernet switch. DHCP server supports an option 82.
  9. 9) DSLAM/MSAN/EAS equipment works as Layer 2 DHCP Relay Agent. DSLAM/MSAN/EAS equipment supports an option 82 during transfer of broadcasting DHCP messages from users.
  10. 10) Host X.1 is connected to the Ethernet switch equipment. The IP-address for host X.1 should be configured manually.
  11. 11) BRAS equipment is configured for termination of IPoE sessions. BRAS equipment works as quality (full) DHCP Relay Agent. BRAS equipment comprises IP-addresses pool for dynamic assignment during establishment of users sessions.
  12. 12) On DHCP server should be configured new user profile where for user identification port number of access node (contains in DHCP option 82) is used.
  13. 13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed bootp PPP ICMP RADIUS.
| + +| | | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test procedure | 1) Initiate establishment of IPoE session on host A.1 (perform transfer of DHCP broadcasting messages from host A.1).
2) Perform data exchange between hosts A.1 and X.1.
3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_02.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. | +| Expected result | 1) Successful establishment of IPoE session. Host A.1 has received IP-address from pool of addresses located on BRAS equipment.
2) BRAS equipment correctly processes DHCP messages containing option 82 which are transferred from user side, and from DHCP server side.
3) During reception of broadcasting DHCP messages from users BRAS equipment directs them to DHCP server in a unicast mode.
4) There is a data exchange possibility between hosts A.1 and X.1.
5) The daily report form has been saved in the corresponding section of KB. | +| Test scheme |

Image: Network diagram for Test scheme. Host A.1 (IP: xxxxx client DHCP) is connected via IPoE to HG1 (bridged mode). HG1 is connected via IPoE to DSLAM/MSAN/EAS (Layer 2 DHCP Relay Agent, DHCP opt82 insertion, Port 1). DSLAM/MSAN/EAS is connected via S-VID '1' to an Ethernet switch. Host X.1 (IP: xxxxx) is also connected to the Ethernet switch. The Ethernet switch is connected to a Server DHCP (option 82) and a BRAS (IDHCP Relay Agent). Arrows show DHCP opt82 broadcast from Host A.1 to the switch, and DHCP opt82 unicast from the switch to the Server DHCP and BRAS.

| + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_ACC_03 | +| Test name | Establishment of L2TP tunnels | +| Test purpose | Check if the BRAS equipment has the possibility of functioning as LNS server during termination of L2TP tunnels of users | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests, one access node has to be used. As access node DSLAM/MSAN/EAS equipment can be used.
4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side equipment of a home gateway (HG1 equipment) should be connected to network termination of a user line.
5) If there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN, one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
7) Host A.1 is connected to home gateway HG1. | + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

8) Host A.1 uses PPPoE sessions. IP-address for host A.1 is assigned dynamically.

9) Host A.1 uses L2TP tunnel during interaction with BRAS equipment and transport of PPPoE messages.

10) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually.

11) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server.

12) BRAS equipment works as LNS server during establishment of L2TP tunnels between BRAS and users.

13) AAA Server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on host A.1.

14) Perform on the analyser of punctures IP the interface with filter on bootp PPP ICMP L2TP.

| +| Test procedure |

1) Initiate an establishment of PPPoE session on host A.1 (enter correct values of username and password).

2) Perform data exchange between hosts A.1 and X.1.

3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_03.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Successful user authentication on host A.1 and subsequent establishment of PPPoE session.

2) There is data exchange between hosts A.1 and X.1.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Network diagram showing Host A.1 connected to HG1 (bridged mode), which is connected to DSLAM/MSAN/EAS (Port 1). Host A.1 is labeled with 'IP:xxxx client PPPoE client L2TP'. A dashed line labeled 'L2TP tunnel' connects Host A.1 to BRAS (LNS PPPoE Server). DSLAM/MSAN/EAS is connected to an Ethernet switch via a link labeled 'S/VID 1'. The Ethernet switch is connected to Server AAA and to BRAS (LNS PPPoE Server) via a link labeled 'G 0/0/1'. Host X.1 is connected to the Ethernet switch and labeled with 'IP:xxxx'.

| + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_ACC_04 | +| Test name | Accounting of rendered services volume for PPPoE sessions | +| Test purpose | Check if the BRAS equipment has the possibility of rendered broadband services volume accounting for users initiating PPPoE sessions | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. DSLAM/MSAN/EAS can be used as access node.

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

4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.

5) If there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN, one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.

6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).

7) Host A.1 is connected to home gateway HG1.

8) Host A.1 uses PPPoE sessions. IP-address for host A.1 is assigned dynamically.

9) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually. Host X.1 is configured as FTP-server. There are several files of various volume on the FTP-server.

10) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server.

11) Subscribers authentication performed on allocated AAA server.

12) AAA server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on host A.1.

13) There should be configured on BRAS equipment periodical data transmission about volume of rendered services in direction to AAA server.

14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: RADIUS.

| +| Test procedure |

1) Initiate an establishment of PPPoE session on host A.1 (enter correct values of username and password).

2) On host A.1 perform download of several files from FTP server.

3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_04.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Correctness of RADIUS messages transferred by BRAS equipment in direction to AAA server. These messages should contain information about the volume of transferred data and should be transferred in beginning and in end of session, and also during all session through certain interval of time configured on BRAS equipment.

2) Correctness of CDR records formed on AAA server.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Test scheme diagram showing the network topology for the test. Host A.1 (client PPPoE) is connected to HG1 (bridged mode), which is connected to Port 1 of the DSLAM/MSAN/EAS. The DSLAM/MSAN/EAS is connected via S-VID '1' to an Ethernet switch. Host X.1 (FTP server) is also connected to the Ethernet switch. The Ethernet switch is connected to a BRAS (PPPoE Server), which is connected to a Server AAA via RADIUS. The BRAS is also connected to the Server AAA via RADIUS.

 graph LR     HostA1[Host A.1
IP:xxxxx
(client PPPoE)] -- PPPoE --> HG1[HG1
(bridged mode)] HG1 -- PPPoE --> Port1[Port 1] subgraph DSLAM_MSAN_EAS [DSLAM/MSAN/EAS] Port1 end Port1 -.-> S-VID "1" EthernetSwitch[Ethernet switch] HostX1[Host X.1
IP:xxxxx
(FTP server)] --> EthernetSwitch EthernetSwitch --> BRAS[BRAS
(PPPoE Server)] BRAS -- RADIUS --> ServerAAA[Server AAA] EthernetSwitch -- RADIUS --> ServerAAA
| + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_ACC_05 | +| Test name | Switching-off of the user after the quota reached | +| Test purpose | Check if the BRAS equipment has the possibility of switching-off the user after achievement of the configured quota of the received data volume | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node has to be used. DSLAM/MSAN/EAS equipment can be used as access node.
  4. 4) For carrying out the tests two user ports on the DSLAM/MSAN/EAS equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
  5. 5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
  6. 6) HG1 and HG2 equipment work in a bridged mode (function of local DHCP server is disconnected).
  7. 7) Host A.1 is connected to home gateway HG1.
  8. 8) Host B.1 is connected to home gateway HG2.
  9. 9) A.1 and B.1 hosts use PPPoE sessions. The IP-address for A.1 and B.1 hosts are assigned dynamically.
  10. 10) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually. Host X.1 is configured as FTP-server. There are several files of various volume on the FTP-server.
  11. 11) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server.
  12. 12) Subscribers authentication performed on allocated AAA server.
  13. 13) AAA server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on A.1 and B.1 hosts.
  14. 14) On AAA server for user of host A.1 there should be configured quota for as much as possible admissible volume of the received data. Establish the given quota equal to 10 Mb.
  15. 15) On AAA server for user of host B.1 there should be configured possibility of unlimited volume data reception.
  16. 16) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: RADIUS.
| +| Test procedure |
  1. 1) Initiate an establishment of PPPoE sessions on A.1 and B.1 hosts.
  2. 2) On host A.1 and B.1 perform download of several files from FTP server.
  3. 3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_05.txt) and put the file into the corresponding section of the KB.
  4. 4) Fill in a daily report form with the testing results and save it in the KB.
| + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected result | 1) User of host B.1 has possibility of reception of unlimited volume of data while session of user of host A.1 is broken off after reaching of configured quota.
2) Correctness of RADIUS messages transferred by BRAS equipment in direction to AAA server and also PPPoE messages transferred by BRAS equipment in direction to host A.1 during interruption of the established session.
3) The daily report form has been saved in the corresponding section of KB. | +| Test scheme | Network diagram for the test scheme. Host A.1 (IP: xxxxx client PPPoE) is connected to HG1 (bridged mode), which is connected via PPPoE to Port 1 of DSLAM/MSAN/EAS. Host B.1 (IP: xxxxx client PPPoE) is connected to HG2 (bridged mode), which is connected via PPPoE to Port 2 of DSLAM/MSAN/EAS. The DSLAM/MSAN/EAS has two S-VID channels (1 and 2) leading to an Ethernet switch. Host X.1 (FTP server, IP: xxxxx) is connected to the Ethernet switch. The Ethernet switch is connected to Server AAA and BRAS (PPPoE Server). A RADIUS connection is shown between BRAS and Server AAA. | + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | BRAS_ACC_06 | +| Test name | Restriction of bandwidth accessible to user | +| Test purpose | Check if the BRAS equipment has the possibility of user accessible bandwidth restriction for data reception/transmission | +| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
4) For carrying out the tests two user ports on the DSLAM/MSAN/EAS equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
6) HG1 and HG2 equipment work in a bridged mode (function of DHCP local server is disconnected).
7) Host A.1 is connected to home gateway HG1.
8) Host B.1 is connected to home gateway HG2.
9) A.1 and B.1 hosts use PPPoE sessions. IP-address for A.1 and B.1 hosts are assigned dynamically.
10) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually. Host X.1 is configured as FTP-server. There are several files of various volume on the FTP-server.
11) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server. | + +| | | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

12) Subscribers authentication performed on allocated AAA server.

13) Server AAA (server RADIUS) is connected to Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on A.1 and B.1 hosts.

14) On AAA server for user of host A.1 there should be configured restrictions on an accessible bandwidth: 500 Kbit/with – DL, 100 Kbit/with – UL.

15) On AAA server for user of host B.1 there should be configured restrictions on an accessible bandwidth: 5 Mbit/with – DL, 1 Mbit/with – UL.

16) On the DSLAM/MSAN/EAS equipment should be configured for both users greatest possible bandwidth in both directions DL and UL.

17) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: RADIUS.

| +| Test procedure |

1) Initiate establishment of PPPoE sessions on A.1 and B.1 hosts.

2) On host A.1 and B.1 perform download of several files from FTP server.

3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_06.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Real downloading speed of files on A.1 and B.1 hosts corresponds to the values configured on BRAS equipment.

2) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Test scheme diagram showing Host A.1 and Host B.1 connected via HG1 and HG2 (bridged mode) to a DSLAM/MSAN/EAS unit. The DSLAM/MSAN/EAS is connected to an Ethernet switch via S-VID 1 and S-VID 2. The Ethernet switch is connected to a Server AAA and a BRAS (PPPoE Server). Host X.1 (FTP server) is also connected to the Ethernet switch.

 graph LR     A1[Host A.1
IP:xxxx
(client PPPoE)] -- PPPoE --> HG1[HG1
(bridged mode)] B1[Host B.1
IP:xxxx
(client PPPoE)] -- PPPoE --> HG2[HG2
(bridged mode)] HG1 -- PPPoE --> DSLAM[DSLAM/MSAN/EAS
Port 1] HG2 -- PPPoE --> DSLAM DSLAM -- S-VID 1 --> SW[Ethernet switch] DSLAM -- S-VID 2 --> SW SW --> AAA[Server AAA] SW --> BRAS[BRAS
(PPPoE Server)] SW --> X1[Host X.1
(FTP server)
IP:xxxx]
| + +### 6.3.2 Methods of BBA TM interoperability testing + +#### 6.3.2.1 Check of compatibility of the access node and BRAS equipment of various vendors + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | AN-BRAS_COMP_01 | +| Test name | User's line identification on basis of DHCP option 82 | +| Test purpose | Check if there is compatibility of access node equipment (DSLAM/MSAN/EAS/OLT) and BRAS equipment of various vendors considering maintenance of user line identification procedure on basis of information presented in DHCP messages (option 82) | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) Vendor "X" represent access node equipment (e.g., DSLAM, MSAN, EAS and OLT PON).

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

4) In the case when access node equipment is presented by DSLAM, MSAN or OLT PON, Vendor "X" should represent the home gateway equipment HG1.

5) Vendor "Y" represent BRAS equipment and DHCP server equipment. DHCP server is external in relation to BRAS equipment and is connected by Ethernet interface (electric). DHCP server supports an option 82.

6) For connection establishment between access node equipment of Vendor "X" and BRAS equipment of Vendor "Y" Ethernet interface (electric) is used. Mirroring of traffic from given interface is provided by Vendor "X".

7) Vendor "Y" provides mirroring of traffic from Ethernet interface between BRAS equipment and DHCP server equipment.

8) Host A.1 is DHCP client. Host A.1 is connected to home gateway HG1 (by Ethernet interface) if technology of access is xDSL or PON, or directly to access node if technology of access is Ethernet. HG1 equipment works in a bridged mode.

9) Access node equipment works as Layer 2 DHCP relay agent, providing addition of an option 82 in all DHCP messages transferred by clients in direction to BRAS equipment. Function Layer 2 DHCP relay agent should be activated for that user's port of access node to which HG1 equipment/host A.1 is connected.

10) BRAS equipment works as quality (full) DHCP relay agent.

11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp RADIUS.

| +| Test procedure |

1) Initiate establishment of IPoE session from host A.1.

2) Save the captures of traces in separate files ([Vendor]-AN-BRAS_COMP_01.txt) and put the file into the corresponding section of the KB.

3) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Access node equipment during processing of DHCP messages provides additions of options 82 into these messages.

2) BRAS equipment, having received within DHCP option 82 information related with user line identification, correctly broadcasts given information in direction to DHCP server.

3) Successful establishment of IPoE session for host A.1.

4) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Test scheme diagram showing the network architecture for DHCP testing. Host A.1 (Client DHCP) is connected to HG1 (bridged mode) which is connected to an Access Node (Vendor 'X') via IPoE. The Access Node contains a Layer 2 DHCP Relay Agent and is connected to a DSLAM/MSAN/EAS. The Access Node is connected via Ethernet to a BRAS (Vendor 'Y') which contains a DHCP Relay Agent. The BRAS is connected to a Server DHCP. A Protocol analyzer is connected to the BRAS and Server DHCP interfaces with a 'filter: bootp'.

 graph LR     subgraph Vendor_X [Vendor "X"]         subgraph AN [Access Node]             L2RA[Layer 2 DHCP Relay Agent]         end         HG1[HG1
(bridged mode)] DSLAM[DSLAM/MSAN/EAS] HostA1[Host A.1
Client DHCP] HG1 --- IPoE((IPoE)) --- L2RA L2RA --- port1[port 1] --- DSLAM HostA1 --- HG1 end subgraph Vendor_Y [Vendor "Y"] BRAS[BRAS
DHCP Relay Agent] ServerDHCP[Server DHCP] end L2RA --- Ethernet((Ethernet)) --- BRAS BRAS --- ServerDHCP BRAS --- PA[Protocol analyzer
filter: bootp] ServerDHCP --- PA HostA1 -.-> DHCP > L2RA L2RA -.-> DHCPoption82 > BRAS BRAS -.-> DHCPoption82 > ServerDHCP
| + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | AN-BRAS_COMP_02 | +| Test name | User line identification on basis of PPPoE tag | +| Test purpose | Check if there is compatibility of access node equipment (DSLAM/MSAN/EAS/OLT) and BRAS equipment of various vendors, considering maintenance of user line identification procedure on basis of information presented in PPPoE tag | +| Initial condition |

1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.

2) Connect equipment under test and measurement equipment in accordance with testing scheme.

3) Vendor "X" represent access node equipment (e.g., DSLAM, MSAN, OLT PON and home gateway equipment HG1).

4) Vendor "Y" represent BRAS equipment and equipment of AAA server. AAA server is external in relation to BRAS equipment and is connected on Ethernet interface (electric). AAA server is RADIUS server.

5) For connection establishment between access node equipment of Vendor "X" and BRAS equipment of Vendor "Y" Ethernet interface (electric) is used. Mirroring of traffic from given interface is provided by Vendor "X".

6) Vendor "Y" provides mirroring of traffic from Ethernet interface between BRAS equipment and equipment of AAA server.

7) Host A.1 is PPPoE client. Host A.1 is connected to home gateway HG1 (by Ethernet interface). HG1 equipment works in a bridged mode.

8) Access node equipment works as PPPoE intermediate agent, providing addition PPPoE tag (0x0105 Vendor-Specific) in all PPPoE messages transferred by clients in direction to BRAS equipment during phase of connection establishment (discovery stage).

9) BRAS equipment works as PPPoE server, terminating corresponding client sessions. BRAS equipment hands over information on user line identification received within PPPoE tag framework from access node, in direction to AAA server using RADIUS protocol.

10) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoe RADIUS.

| +| Test procedure |

1) Initiate establishment of PPPoE session from host A.1.

2) Save the captures of traces in separate files ([Vendor]-AN-BRAS_COMP_02.txt) and put the file into the corresponding section of the KB.

3) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) On phase of connection establishment (discovery stage) access node equipment during processing of PPPoE discovery messages provides addition of PPPoE tag (0x0105 Vendor-Specific) into these messages.

2) BRAS equipment, having received in PPPoE tag framework information related with user line identification, correctly broadcasts given information in direction to AAA server inside attribute of RADIUS Access-Request message.

3) Successful establishment of PPPoE session for host A.1.

4) The daily report form has been saved in the corresponding section of KB.

| + +![Diagram of the test scheme showing the network architecture. On the left, Host A.1 (Client PPPoE) is connected to HG1 (bridged mode) which is part of AT&RONT. HG1 is connected to an Access Node (Vendor 'X') containing a PPPoE Intermediate Agent and a DSLAM/MSAN/VOLT. The Access Node is connected via Ethernet to a BRAS (Vendor 'Y') which contains a Server PPPoE. The BRAS is connected to a Server AAA. A Protocol analyzer is connected to the BRAS and Server AAA via RADIUS and PPPoE filters. The diagram shows the flow of PPPoE discovery stage packets from Host A.1 through the Access Node to the BRAS, and the subsequent RADIUS authentication process.](e8f5117fb031f413a836525061addd61_img.jpg) + +**Test scheme** + +Diagram of the test scheme showing the network architecture. On the left, Host A.1 (Client PPPoE) is connected to HG1 (bridged mode) which is part of AT&RONT. HG1 is connected to an Access Node (Vendor 'X') containing a PPPoE Intermediate Agent and a DSLAM/MSAN/VOLT. The Access Node is connected via Ethernet to a BRAS (Vendor 'Y') which contains a Server PPPoE. The BRAS is connected to a Server AAA. A Protocol analyzer is connected to the BRAS and Server AAA via RADIUS and PPPoE filters. The diagram shows the flow of PPPoE discovery stage packets from Host A.1 through the Access Node to the BRAS, and the subsequent RADIUS authentication process. + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | AN-BRAS_COMP_03 | +| Test name | Information transfer about characteristics of DSL user lines | +| Test purpose | Check if there is compatibility of access node equipment (DSLAM/MSAN/EAS/OLT) and BRAS equipment of various vendors, considering maintenance of DSL user lines characteristics information transfer procedure | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) Vendor "X" represents the access node equipment (e.g., DSLAM/MSAN and also the home gateways equipment HG1 and HG). Vendor "X" provides two user lines ADSL/ADSL2/ADSL2 +/VDSL2 for connection of the home gateway equipment to access node equipment.
  4. 4) Vendor "Y" provides BRAS equipment and the equipment of AAA server. AAA server is external in relation to BRAS equipment and is connected on Ethernet interface (electric). AAA server is RADIUS server. BRAS equipment supports functionality of PPPoE server, DHCP server (possibility of use of external DHCP server is supposed) and functionality of RADIUS client.
  5. 5) For connection establishment between access node equipment of vendor "X" and BRAS equipment of vendor "Y" Ethernet interface (electric) is used. Mirroring of the traffic from the given interface is provided with vendor "X".
  6. 6) Vendor "Y" provides mirroring of traffic from Ethernet interface between BRAS equipment and equipment of AAA server.
  7. 7) Host A.1 is DHCP client. Host A.1 is connected to home gateway HG1 (by Ethernet interface). HG1 equipment works in a bridged mode.
  8. 8) Host B.1 is PPPoE client. Host B.1 is connected to home gateway HG2 (by Ethernet interface). HG2 equipment works in a bridged mode.
  9. 9) Access node equipment works as Layer 2 DHCP relay agent, providing addition of option 82 in all DHCP messages transferred by clients in direction to BRAS equipment. Function Layer 2 DHCP relay agent should be activated for that user's port of access node to which HG1 equipment/host A.1 is connected.
| + +| | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

10) During functioning as Layer 2 DHCP relay agent access node equipment should provide an information transfer about characteristics of user line, including actual speed of data transmission in user line (upstream/downstream actual data rate) and minimum speed of data transmission in user line (upstream/downstream minimum data rate). Information on characteristics of user line should be transferred in option 82 inside field vendor-specific sub-option.

11) Access node equipment works as PPPoE intermediate agent, providing addition of PPPoE tag (0x0105 Vendor-Specific) in all PPPoE messages transferred by clients in direction to BRAS equipment during phase of connection establishment (discovery stage).

12) During functioning as PPPoE intermediate agent, the access node equipment should provide information about characteristics of user line, including actual speed of data transmission in user line (upstream/downstream actual data rate) and minimum speed of data transmission in user line (upstream/downstream minimum data rate). Information on characteristics of user line should be transferred in additional fields of PPPoE tag expansion (Vendor-Specific).

13) BRAS equipment performs reception of information on characteristics of user line transferred from access node inside DHCP option 82 or PPPoE tag, and provides transfer of given information to direction of AAA server inside Access-Request RADIUS message. Information transfer about characteristics of user line is performed inside RADIUS attributes 'Vendor Specific Attributes'.

14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed bootp RADIUS.

| +| Test procedure |

1) Initiate establishment of IPoE session from host A.1.

2) Initiate establishment of PPPoE session from host B.1.

3) Save the captures of traces in separate files ([Vendor]-AN-BRAS_COMP_03.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Access node equipment provides information transfer about characteristics of user line within limits of option 82 DHCP.

2) Access node equipment provides information transfer about characteristics of user line in frameworks PPPoE tag (Vendor-Specific).

3) BRAS equipment, having received information on characteristics of user line inside DHCP option 82 or PPPoE tag, correctly broadcasts given information in direction to AAA server inside Access-Request RADIUS message.

4) Successful establishment of IPoE and PPPoE sessions for A.1 and B.1 hosts, accordingly.

5) The daily report form has been saved in the corresponding section of KB.

| + +![Test scheme diagram showing network architecture with Vendor 'X' and Vendor 'Y' equipment. Vendor 'X' includes Host A.1 (Client DHCP), Host B.1 (Client PPPoE), HG1 (bridged mode), HG2 (bridged mode), and DSLAM/MSAN. Vendor 'Y' includes BRAS and Server AAA (RADIUS). A protocol analyzer is connected to the BRAS. Dashed lines show DHCP/PPPoE discovery and RADIUS traffic paths.](d1ad05f1189b0d80188fee24ae33c112_img.jpg) + +**Test scheme** + +The diagram illustrates a network test scheme. On the left, under 'Vendor "X"', Host A.1 (Client DHCP) is connected to HG1 (bridged mode, AT&RVTUR), which is connected to the DSLAM/MSAN via iPoE. Host B.1 (Client PPPoE) is connected to HG2 (bridged mode, AT&RVTUR), which is connected to the DSLAM/MSAN via PPPoE. The DSLAM/MSAN contains a Layer 2 DHCP Relay Agent on port 1 and a PPPoE Intermediate Agent on port 2. An Ethernet connection links the DSLAM/MSAN to the BRAS under 'Vendor "Y"'. The BRAS contains a Server PPPoE and a Server DHCP. The BRAS is also connected to a Server AAA (RADIUS). A Protocol analyzer is connected to the BRAS. Dashed lines indicate traffic paths: DHCP/PPPoE (discovery) from Host A.1 and Host B.1 through the DSLAM/MSAN to the BRAS; DHCPoption82 || PPPoE(discovery)+TAG from the BRAS to the Server AAA (RADIUS); and RADIUS traffic between the BRAS and the Server AAA (RADIUS). Filters are applied: 'filter: bootp || pppoe' on the path to the protocol analyzer, and 'filter: radius' on the path from the protocol analyzer to the Server AAA (RADIUS). + +Test scheme diagram showing network architecture with Vendor 'X' and Vendor 'Y' equipment. Vendor 'X' includes Host A.1 (Client DHCP), Host B.1 (Client PPPoE), HG1 (bridged mode), HG2 (bridged mode), and DSLAM/MSAN. Vendor 'Y' includes BRAS and Server AAA (RADIUS). A protocol analyzer is connected to the BRAS. Dashed lines show DHCP/PPPoE discovery and RADIUS traffic paths. + +#### 6.3.2.2 Check of compatibility of the access node and home gateway equipment of various vendors + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test number | DSL_COMP_01 | +| Test name | Check of compatibility of home gateway equipment and DSLAM/MSAN equipment | +| Test purpose | Check if there is a compatibility of home gateway DSL equipment (ATU R/VTU R) and access node equipment (DSLAM/MSAN) from various vendors | +| Initial condition |
  1. 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
  2. 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
  3. 3) Vendor "X" provides access node equipment DSLAM/MSAN with support of cards ADSL2/ADSL2 +/VDSL2/SHDSL. Vendor "X" provides user line (twisted pair) for connection of home gateway DSL equipment to access node equipment.
  4. 4) Vendor "Y" provides home gateway DSL equipment (ADSL2/ADSL2 +/VDSL2/SHDSL) – HG1.
  5. 5) Vendor "X" provides specification of DSLAM/MSAN access node equipment in the following style:
| + +| | | | +|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| | | | +| | General information on DSLAM/MSAN access node equipment | | +| | Name and product updating | _____ | +| | Version of hardware maintenance | _____ | +| | Software version | _____ | +| | Types of supported linear cards | _____ | +| | Supported standards DSL | _____ | +| | Characteristics ADSL2/ADSL2+ | | +| | Maximum supporting speed – downstream (Net Data Rate) | _____ | +| | Maximum supporting speed – upstream (Net Data Rate) | _____ | +| | Characteristics VDSL2 | | +| | Maximum supporting speed – downstream (Net Data Rate) | _____ | +| | Maximum supporting speed – upstream (Net Data Rate) | _____ | +| | Characteristics SHDSL | | +| | Maximum supporting speed – downstream (Net Data Rate) | _____ | +| | Maximum supporting speed – upstream (Net Data Rate) | _____ | +| | 6) Vendor "Y" provides specification of home gateway DSL equipment in the following style: | | +| | General information on home gateway DSL equipment | | +| | Name and product updating | _____ | +| | Supported standards DSL | _____ | +| | Version of hardware maintenance | _____ | +| | Software version | _____ | +| | Serial number | _____ | +| | Characteristics ADSL2/ADSL2+/VDSL2/SHDSL | | +| | Maximum supporting speed – downstream (Net Data Rate) | _____ | +| | Maximum supporting speed – upstream (Net Data Rate) | _____ | +| | 7) Home gateway equipment HG1 is connected to DSLAM/MSAN access node equipment on DSL interface taking into account specifications of equipment, provided by vendor "X" and vendor "Y".
8) Host A.1 is connected to home gateway HG1 on Ethernet interface.
9) Home gateway HG1 functions in the bridged mode.
10) Host X.1 is connected on Ethernet interface directly to (uplink) DSLAM/MSAN equipment. Possibility of connection of host X.1 to DSLAM/MSAN equipment through Ethernet switch is assumed. In the last case Ethernet switch is given by vendor "X". | | + +| | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

11) IP addresses of hosts A.1 and X.1 are from the same IP subnetwork.

12) Establish on hosts A.1 and X.1 IPerf utility, allowing testing of accessible throughput of data link. Further during start of IPerf utility as client part it is necessary to use host A.1, and as server part – host X.1.

| +| Test procedure |

1) Initiate establishment of DSL connection between home gateway equipment HG1 and access DSLAM/MSAN equipment.

2) Perform traffic transfer by means of IPerf utility between hosts A.1 and X.1 in both directions (upstream/downstream) within 15 minutes.

3) Save the captures of traces in separate files ([Vendor]-DSL_COMP_01.txt) and put the file into the corresponding section of the KB.

4) Fill in a daily report form with the testing results and save it in the KB.

| +| Expected result |

1) Interval of time from moment of initiation of DSL connection on HG1 equipment till the moment of showtime condition does not exceed 60 seconds (train time \leq 60s).

2) There is possibility of successful establishment of connection and data exchange between HG1 equipment and DSLAM/MSAN according to standards declared in specifications.

3) The daily report form has been saved in the corresponding section of KB.

| +| Test scheme |

Image: Test scheme diagram showing Host A.1 connected to HG1 (bridged mode) via Ethernet. HG1 is connected to DSLAM/MSAN via DSL. DSLAM/MSAN is connected to a Switch Ethernet via Ethernet. Switch Ethernet is connected to Host X.1 via Ethernet. A Simulator/Analyzer of traffic is connected to both Host A.1 and Host X.1 via dotted lines. The diagram is divided into two vendor regions: Vendor 'Y' (containing Host A.1 and HG1) and Vendor 'X' (containing DSLAM/MSAN, Switch Ethernet, and Host X.1).

 graph LR     subgraph Vendor_Y [Vendor "Y"]         HA1[Host A.1] -- Ethernet --> HG1["HG1
(bridged mode)
ATU-R/VTU-R"] end subgraph Vendor_X [Vendor "X"] DSLAM["DSLAM/MSAN"] -- DSL --> HG1 subgraph DSLAM内部 [ ] direction LR ATU["ATU-C/VTU-O"] --- FE["FE/GE"] end FE -- Ethernet --> SE["Switch Ethernet"] SE -- Ethernet --> HX1[Host X.1] end HA1 -.-> SAT["Simulator/Analyzer of traffic"] HX1 -.-> SAT style Vendor_Y fill:none,stroke-dasharray: 5 5 style Vendor_X fill:none,stroke-dasharray: 5 5 style DSLAM内部 fill:none,stroke:none
| + + + +# 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.3930-201208-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6641455ab8f6a4aa2368db84ad8e90ad33caf0e5 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e36e623674d0ffee33dcd5083f81bb72e0ef4be4933d253c01b0f7584ed88ebd +size 65898 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e48e11052ae36b8779f9acd5a057ae1cfc08570 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ed480ce68f2b323d263a1939fd64efab9c43ef1a27a73667ccb061048d93e7e +size 45269 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2f60a12dcbd226f5596a6902aeb5604d611cd67 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70024c6cfe1f8a121a77e0e800372eed6ba1c125ae63b274991f6dfa86c59b04 +size 19881 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d857c32bd6c9ddc1bf5d24181449cb9d3c29029e --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:725fcd6cbc19a7776a7236501c3c830a3d24458a8824622abd1e031cd305e39f +size 72937 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aedf1151177b786a92754a3222427d097592ffc8 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d281360d4faf6d13114cc31a9e721b94380ff8a3f7770ed8725a6161500be610 +size 46759 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eaa33367045c22e385853b196d878900a468583 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:705e15d71a71e303be7961ea9a92b79ce156fa01726c3614ae3dbdc78e1452bc +size 24973 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71494113597c55a39dbef7a3273fdb5be00315e2 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:651ab44cd96087a99b4e8aba0d6d95cd480d9a1e47081229a4a17f5e2b8e8bf3 +size 31977 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..485df638c6e101fe0a63d3ac94cf9c0805994b26 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cbd37aa093f5bf50e9dde45930b5228355ab3179aecfed33427bff13141e3be +size 35672 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08ae2ed4691a6ce36ebaa3fe83ac7c7835920730 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6122a3fe6934bd1f3fbb111d5d1606ac29e08053f16420bb24440981cc2140f +size 44421 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c5f48730703273a1fe46e2aab0b4cf74fa64e9 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fc1240177a17e3e16ecb3da95722da62298ce3b6039683f8dbab2cdda061012 +size 23036 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..864b316940d8761c5ff25f3d42ca26546cabe474 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:833da5cb93a5c0a2fa5c7d8f8e333fb82e2c77997af9aef399b0c8318a604dea +size 65595 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3164d908ad57995d1060010a86af560e961b11df --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c05eda72f36938f00f176341b4701c03bbc6841d583a5b28a1a8c32671fce9da +size 72988 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8416bfafaec02edcacf4798507305c60684b764a --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:234ef729d9b0f5252889c6c33cd628abbc0d3eea310cf42a5babff0aef71827a +size 14278 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66116619a68b4db80e001dfa686109fef54fcf98 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f2fe814dc80d404ca201e14f61304109b6f019609f7f3ea1c71aaeab4906851 +size 29495 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b4c65b053dd5dd9f65975ab5b2d63fc18883798 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfd0f7cd638deed8e323fbe6f90f2da50dc87bdfffc6a46e103325450ee21f76 +size 73027 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edd87c25a36d596417b4920bfcc50201790f0e25 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:721bb98a21d866057b5d9e8a1962df42a5c1cd0435593bef533ec7f9aca64be4 +size 56278 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb54f687029bb6633886fd8467eeb70d7a4d2cd8 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce9b41174749c17e436407be34c7ac2d4f306944c02101b0e1e82a6b4659e219 +size 44564 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d9c034cd43309288cb109b76ffb7418d_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d9c034cd43309288cb109b76ffb7418d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cb1d6723fbc96d993357b79a87a98c72f3f9732 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d9c034cd43309288cb109b76ffb7418d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a1563b7077f901cb7237aeb45ad0e34e8a2ba185161bcc483c115bc97f42f99 +size 39219 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..894b6cb4248564c648344c33f02f5fe09b7f7dfa --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75ca705154495937eef1bbff36f65791c16c4bcb3614e747594ffe6eba65a66d +size 69872 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c4557efdd9e1614e3715b39b7c2e91e3b9718e1 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63a0b50fc56e2ad5563c656cba72514d17cdf3ee0d2aa51396414d4ff9cd4559 +size 27783 diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43ee8bdd1942ab816e28a7b301a7c2090c9e2204 --- /dev/null +++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9c11a5e7e87d2a0da76d2372de6d0e10624e16a755f537166b54056678813e9 +size 34892 diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2db69df27dc6c6e9cde82b6d11cc060266ee8e7c --- /dev/null +++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/raw.md @@ -0,0 +1,622 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3932.1** + +(06/2015) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for next generation networks + +--- + +**IMS/NGN performance benchmark – Part 1: Core concept** + +Recommendation ITU-T Q.3932.1 + +ITU-T + +![ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'. + +# ITU-T 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.1 + +### IMS/NGN performance benchmark – Part 1: Core concept + +## Summary + +Recommendation ITU-T Q.3932.1 provides the first part of a multi-part deliverable covering the IP multimedia subsystem (IMS)/next generation networks (NGN) performance benchmark, as identified below: + +### **Part 1: Core concepts;** + +Part 2: Subsystem configurations and benchmarks; + +Part 3: Traffic sets and traffic profiles; + +Part 4: Reference load network quality parameters. + +This Recommendation describes the performance benchmark methodology for the IMS based services multimedia telephony (MMTel), video telephony and IMS/PES. The terminology and concepts are described in Recommendation ITU-T Q.3930. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3932.1 | 2015-06-13 | 11 | 11.1002/1000/12495 | + +--- + +\* 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 ..... | 3 | +| 5 Conventions ..... | 4 | +| 6 Benchmark information model ..... | 4 | +| 6.1 Use case ..... | 5 | +| 6.2 Benchmark test ..... | 7 | +| 6.3 Benchmark report ..... | 9 | +| 7 System under test (SUT)..... | 9 | +| 8 Test system ..... | 13 | +| 9 Benchmark metrics examples ..... | 13 | + + + +## Recommendation ITU-T Q.3932.1 + +## IMS/NGN Performance benchmark – Part 1: Core concept + +# 1 Scope + +Recommendation ITU-T Q.3932.1 provides the first part of a multi-part deliverable covering the IMS/NGN performance benchmark, as identified below: + +### **Part 1: Core concepts;** + +Part 2: Subsystem configurations and benchmarks; + +Part 3: Traffic sets and traffic profiles; + +Part 4: Reference load network quality parameters. + +The present Recommendation describes the performance benchmark methodology for the IMS based services MMTel, video telephony and IMS/PSTN emulation solution (PES). The terminology and concepts are described in [ITU-T Q.3930]. + +# 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 P.56] Recommendation ITU-T P.56 (2011), *Objective measurement of active speech level*. +- [ITU-T P.862] Recommendation ITU-T P.862 (2001), *Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs*. +- [ITU-T P.862.1] Recommendation ITU-T P.862.1 (2003), *Mapping function for transforming P.862 raw result scores to MOS-LQO*. +- [ITU-T P.863] Recommendation ITU-T P.863 (2014), *Perceptual objective listening quality assessment*. +- [ITU-T Q.3930] Recommendation ITU-T Q.3930 (2012), *Performance testing of distributed systems – Concepts and terminology*. +- [ITU-T Q.3932.2] Recommendation ITU-T Q.3932.2 (2015), *IMS/NGN performance benchmark – Part 2: Subsystem configurations and benchmarks*. +- [TS 101 563] ETSI TS 101 563 V.1.3.1 (2014), *Speech and multimedia Transmission Quality (STQ); IMS/PES/VoLTE exchange performance requirements*. +- [TS 123 002] ETSI TS 123 002 (V11.6.0) (2013), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 11.6.0 Release 11)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +The IMS benchmarking definitions are described in [ITU-T Q.3930]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 background load:** Workload applied to a system under test (SUT) during a benchmark test, for the purpose of consuming SUT resources during a benchmark test and changing the traffic intensity at which the capacity of the SUT is reached. + +**3.2.2 benchmark report:** Document generated at the conclusion of a test procedure containing the metrics measured during the execution of the test and/or computed from the data collected in the benchmark log. + +**3.2.3 benchmark test:** Procedure by which a test system interacts with a system under test (SUT) to measure its behaviour and produce a benchmark report. + +**3.2.4 configuration:** Specification of a subset of IMS/PES architectural elements and metrics for which collection of benchmark tests can be defined. + +**3.2.5 design objective (DO):** Probabilistic model of delay and failure requirements for SUT, associated with a use case, specified by threshold values and probabilities for delay and scenario failure. + +**3.2.6 design objective capacity (DOC):** Largest load a SUT can sustain while not exceeding design objectives (DOs) defined for a use case. + +**3.2.7 idle load:** Load that is not dependent on the traffic or other external activities. + +**3.2.8 maximum capacity:** maximum processor load that a processor can handle without rejecting new calls. + +**3.2.9 metric:** Performance measurement of a system under test (SUT) reported in a benchmark report. + +**3.2.10 parameter:** Attribute of a SUT, test system, system load, or traffic set whose value is set externally and prior to a benchmark test, and whose value affects the behaviour of the benchmark test. + +**3.2.11 processor load:** Amount of time the processor executes work. It is normally expressed in percent. + +NOTE – The processor load consists of idle load, traffic load and usage load. + +**3.2.12 reference call (RC):** Basic ISDN user part (ISUP) to ISUP call connected through two media gateways (MGWs) in the same media gateway controller (MGC) domain. + +**3.2.13 session attempts per second (SAPS) increase amount:** Increment by which the average SAPS changes between steps of a profile. + +**3.2.14 test parameters:** Parameters whose values determine the behaviour of a benchmark test. + +**3.2.15 test procedure:** Specification of the steps to be performed by a benchmark test. + +**3.2.16 test scenario:** Specific path through a use case, whose implementation by a test system creates a system load. + +**3.2.17 test system:** Collection of hardware and software which presents a system load to a system under test (SUT) and collects data on the SUT's performance, from which metrics can be computed. + +**3.2.18 traffic load:** Load that results from handling traffic events that are directly related to calls. + +NOTE – This load varies with the traffic intensity. + +**3.2.19 traffic-time profile:** Evolution of the average scenario over a time interval. + +**3.2.20 traffic set:** Mixture of traffic scenarios. + +**3.2.21 usage load:** Load that is reserved for the administration's operation and maintenance activities during busy hour. + +**3.2.22 workload:** Number of reference calls per second (RC/s). + +NOTE – It is calculated by multiplying calls per second by its corresponding workload factor (WLF). + +**3.2.23 workload factor (WLF):** Traffic load for different types of calls in relation to the traffic load of the reference call (ISUP call). + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|-----------------------------------------| +| AGCF | Access Gateway Control Function | +| BGCF | Breakout Gateway Control Function | +| BYE | BYE message | +| CN | Core Network | +| CPU | Central Processor Unit | +| CS | Circuit Switched | +| CSCF | Call Server Control Function | +| DO | Design Objective | +| DOC | Design Objective Capacity | +| ETH | Ethernet | +| HSS | Home Subscriber Server | +| FM | Fault Management | +| IBCF | Interconnection Border Control Function | +| II-NNI | Inter-IMS Network to Network Interface | +| IM | IP Multimedia | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| ISC | IP multimedia Service Control | +| ISDN | Integrated Service Digital Network | +| ISUP | ISDN User Part | +| LCS | Location Services | +| LRF | Location Retrieval Function | +| MCS | Modulation and Coding Scheme | +| MGC | Media Gateway Controller | +| MGW | Media Gateway | +| MHT | Mean Holding Time | + +| | | +|---------|---------------------------------------------------------------| +| MME | Mobile Management Entity | +| MMTel | Multimedia Telephony | +| MRB | Media Resource Broker | +| MRF | Media Resource Function | +| MRFP | Media Resource Function Processor | +| NGN | Next Generation Networks | +| NNI | Network-to-Network Interface | +| PES | PSTN Emulation Solution | +| PESQ | Perceptual Evaluation of Speech Quality | +| POLQA | Perceptual Objective Listening Quality Assessment | +| POTS | Plain old telephone service | +| RC | Reference Call | +| RTP | Real-Time Protocol | +| SAPS | Session Attempts Per Second | +| S-CSCF | Serving CSCF | +| SIGTRAN | Stream Control Transmission Protocol | +| SIP | Session Initiation Protocol | +| SIP-I | a mapping from SIP to ISUP | +| SLF | Subscription Locator Function | +| SUA | SCCP-User Adaptation Layer | +| SUT | System Under Test | +| TA | Tones and Announcement | +| TDM | Time-division multiplexing | +| UDI | Unrestricted Digital Information | +| UDI/TA | Unrestricted Digital Information with tones and announcements | +| UE | User Equipment | +| VGW | Voice Gateway | +| WLF | Workload factor | + +# 5 Conventions + +None. + +# 6 Benchmark information model + +In this clause, "benchmark information model" refers to the structure of the information elements that define the benchmark. This **information** model is depicted in Figure 1. + +The information model consists of three primary elements: use cases, which describe the behaviour of an individual user, and which in turn define scenarios; benchmark tests, which generate a workload by aggregating the behaviour of individual scenarios in a controlled manner, and collect log files of measurements during the test; and benchmark test reports, which report metrics interpreted from the benchmark test log files. + +![Diagram of the IP multimedia subsystem (IMS) benchmark information model showing the relationship between Use cases, Benchmark tests, and Test reports.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +The diagram illustrates the IP multimedia subsystem (IMS) benchmark information model, organized into three main columns: Use case, Benchmark test, and Test report. + +- Use case 1: MMTel - (registration)** + - Scenario 1.1: e.g., user not registered** + - Call flows + - Load profiles + - Design objectives + - Metrics + - SUT parameters + - Scenario 1.2: (e.g., user already registered)** +- Use case 2: MMTel - Session setup** + - Scenario 2.1: call successful** + - Call flows + - Load profiles + - Design objectives + - Metrics + - SUT parameters + - Scenario 2.2: user not found** +- Benchmark test** + - Traffic set** + - X % of scenario 1.1 + - X % of scenario 1.2 + - X % of scenario 2.1 + - X % of scenario 2.2 + - Traffic time profile + - SUT characteristic + - Background load +- Test report** + - Metrics and graphics with design objective capacity + - Call detail report + - Voice quality summary report + - Voice quality detail report + - Error summary report + - Error detail report + - Voice quality error summary report + - Voice quality error detail report + +Arrows indicate the flow from Use cases to Benchmark tests and from Benchmark tests to Test reports. Specifically, arrows from the scenarios in Use cases point to the Traffic set in the Benchmark test, and an arrow from the Benchmark test points to the Test report. + +Diagram of the IP multimedia subsystem (IMS) benchmark information model showing the relationship between Use cases, Benchmark tests, and Test reports. + +Q.3932.1(15)\_F01 + +**Figure 1 – IP multimedia subsystem (IMS) benchmark information model** + +## 6.1 Use case + +The top level of the individual behavioural model is the use case. A use case describes: The goal that a user has in interacting with a system, the various actors (e.g., other users, network elements) that participate in the use case, the basic course of events that are carried out by the user and the SUT, the design objective (DO) of the use case, the possible outcomes that apply to the use case, and the metrics to be collected. The goal and actors of a use case are documented in narrative text and diagrams; the other elements are complex information elements, which are described in their respective clauses. + +### **6.1.1 Call flow** + +The calls flows define the characteristic message flows, the tones and announcements (TAs) for a specific interface. + +### **6.1.2 Load profile** + +To facilitate the calculation of processing capacity and the appropriate load profile, the concept of workload factor (WLF) has been defined based on the reference call (RC) for each combination of traffic case and traffic signalling interface. The RC is defined as a basic ISDN user part (ISUP) to ISUP call connected through two media gateways (MGWs) in the same domain. + +Based on the WLFs for all different types of calls, the call intensities and the services used, one can express the total traffic load in an equivalent number of RCs per second. + +The dimensioning of any type of network depends on a number of different parameters such as utilization per channel, calls per second, mean holding time (MHT), type of accesses being involved and type of services being requested. + +#### **6.1.3 Metrics** + +The metrics of a use case describe the measurements collected from the execution of a scenario attempt. Typical metrics include response times and message rates. If a scenario is selected for execution in a benchmark test, its metrics are collected. See clause 8 for more detail. + +#### **6.1.4 Use case outcomes** + +A use case outcome is a set of possible outcomes of the scenarios of a use case. An outcome may be simply "correct", it may reflect an error or failure condition, or it may reflect a correct behaviour that took an excessive amount of time to occur. An instance of a scenario that experiences an error, failure, or timeout outcome is referred to as an inadequately handled scenario attempt. + +#### **6.1.5 Scenarios and scenario attempts** + +A scenario is a trace of a path through a use case. It is analogous to "call attempt", but applies to all interactions within an IMS/PES network, different bearer and application interactions. + +A scenario may succeed, fail, or succeed functionally. + +The terms "scenario attempt" and "scenario attempts per second" are used in the present document in place of "call attempt" and "call attempts per second" because IMS is a transaction-oriented system with transactions of a variety of types traffic sets, and in the real world do not operate according to only one transaction type, so the more generalized term is necessary. It would be incorrect and misleading to attempt to report the capacity of a system in "call attempts per second", "registration attempts per second", etc., for system loads that were other than purely call attempts, registration attempts, etc. + +#### **6.1.6 Design objective (DO)** + +The DO describes the maximal acceptable rate handled scenario attempts for a use case. + +#### **6.1.7 Scenario** + +A scenario describes a single interaction sequence among the actors of a use case. It is documented by a set of preconditions on its actors (typically specified by parameter values). In the case of IMS/PES the scenario is defined as a set of different bearer capabilities (e.g., speech, 3.1 kHz audio, unrestricted digital information (UDI), unrestricted digital information with tones and announcements (UDI/TA)), services (fax, modem), or dial modes. + +## 6.2 Benchmark test + +A benchmark by definition measures the behaviour of a population of users. To accomplish this, the behaviours of individual users shall be aggregated into input traffic to the SUT. The input traffic shall be realistic, in the sense that a population of users would perform such actions in the real world, and in the sense that statistical variation in user behaviour is similar to statistical variation that would occur in the real world. + +### 6.2.1 Traffic set + +The traffic set is a collection of scenarios which are determined to be likely to co-occur in a real-world scenario. The scenarios do not need to come from the same use case. Within a traffic set, each scenario has an associated relative occurrence frequency, interpreted as the probability with which it would occur in the course of the test procedure. + +### 6.2.2 Background load + +Background load is a workload presented to the SUT in order to consume its resources. It may consist of a stream of traffic presented to the SUT by an external system apart from the test system; or it may be a workload presented to the processing elements, network, or storage subsystem of the SUT. + +The purpose of background traffic is to make possible the measurement of a DOC in SUT when the capacity of the test system is insufficient to reach the DOC. + +If a benchmark test is published in which background load is used, then the following requirements apply: + +- the hardware used to generate the background load shall be fully specified. If the background load is generated by software running directly on the SUT, then the components of the SUT on which the background load is executed shall be fully specified; +- the software used to generate the background load shall be provided in source form, including makefiles and any other configuration files required to compile the software. + +#### 6.2.3 Traffic-time profile + +The traffic-time profile is a function describing the average scenario attempt arrival rate as a function of elapsed time during a benchmark test. A traffic-time profile should be chosen in such a manner so that, for a given scenario attempt arrival rate, sufficient samples are generated that metrics can be collected with an appropriate confidence bound. The following call profiler traffic patterns are used today: saw tooth, blast, ramp, steady call rate, rolling blast and Poisson distribution. To get a realistic scenario, a combination of at least two scenarios is needed. + +### 6.2.4 Test parameters + +The benchmark test parameters are used to control the behaviour of the test script. The data elements required to configure the test system are listed in Table 1. + +Table 1 is a non-exhaustive list of test parameters defined for the benchmark standard. The list is expected to grow over time, as additional subsystems and system configurations are developed. + +**Table 1 – Test parameters** + +| Parameter | Description | +|------------|--------------------------------------------------------------------------------| +| Start time | Amount of time that a system load is presented to a SUT at the start of a test | +| Stop time | Amount of time that a system load is presented to a SUT at the end of a test | + +**Table 1 – Test parameters** + +| Parameter | Description | +|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TotalProvisionedSubscribers | The number of simulated subscribers provisioned in the network | +| PercentSimulatedSubscriber | The average percentage of simulated subscribers | +| Simulated maximum simultaneous call legs | The number of simulated maximum simultaneous call legs | +| Traffic per subscriber | Traffic per subscriber; default value 0.1 Erlang | +| PX_PercentRegisteredSubscribers | The average percentage of simulated subscribers that are registered simultaneously | +| PX_PercentRoamingSubscribers | The average percentage of simulated subscribers that are roaming (i.e., registered in a non-local network) | +| PX_Simulated Subscriber Registration Parameters | Parameters and distributions of the probabilistic model of simulated subscriber operation | +| MHT | Mean holding time of a call; default value 110 seconds | +| Ringing time | Duration between (180 ringing and 200 OK INVITE )
Default value 1-5 s | +| NoS | Number of subscribers originating traffic per subscriber | +| CAPS/BHCA | Call attempts per second/busy hour call attempts | +| WLF for call controller | The WLF for call controller for a specific configuration. Default value 1-3 | +| WLF for gateway controller | The WLF for gateway controller for a specific configuration. Default value 1-3 | +| WLF for MGW | The WLF for MGs for a specific configuration. Default value 1-3 | +| Time-division multiplexing TDM trunks | Number of TDM trunks | +| Ethernet (ETH) | Number of ETH connections | +| Type of call | MMTel fixed access to MMTel fixed access
Video telephony
IMS/PES to IMS/PES
MMTel fixed access to IMS/PES | +| Protocol call type and interfaces | SIP-I
ISUP
Steam control transmission protocol (SIGTRAN) (M2PA; M2UA; M3UA; SCCP-user adaptation layer (SUA))
Session initiation protocol (SIP) inter-IMS network to network interface (II NNI) (Ici,Izi)
SIP NNI (Mx Interface)
Gm interface | +| MGCF/MGW/I-BCF/TrMGW performance tests | SIP-I to SIP-I
SIP-I to ISUP
SIP-I to network-to-network interface (NNI)
NNI to NNI | + +**Table 1 – Test parameters** + +| Parameter | Description | +|----------------------|-------------------------------------------------------------------------------------------------| +| | SIGTRAN to SIGTRAN (M2PA; M2UA; M3UA; SUA) | +| | ISUP (SIGTRAN) to NNI | +| Transport interfaces | Voice over LTE (VoLTE) (LTE-Uu, S1-U, S-11, S6a, S11, S5/S8, Rx, Gx, Mw, ISC and Ut interfaces) | +| | ETH | +| | xDSL | +| | Integrated services digital network (ISDN) | +| | Plain old telephone service (POTS) (Z) | + +## 6.3 Benchmark report + +A test report is a document, with accompanying data files, that provides a full description of an execution of a benchmark test on a test system. The SUT and test system, as well as their parameters, are described in sufficient detail that an independent test site can replicate the test. The results of the test include: Data, represented as charts and data sets, depicting the behaviour of the SUT over the elapsed time of the test; reports of the relevant metrics that are conventionally used to compare benchmark results of differing SUTs; and a full description of other observations and exceptions noted during the test. + +## 7 System under test (SUT) + +The IMS performance benchmark covers benchmark tests for the video telephony and multimedia telephony (MMTel) fixed access – IMS/PES. + +Figure 2 depicts the IMS reference architecture. The components of the architecture are the primary building blocks, which are either defined by the IMS standard, or defined by external standards and referenced by the IMS. The links between the primary building blocks represent reference points over which the building blocks communicate with each other. + +The reference architecture is a logical architecture; no mapping of functional elements to hardware or software components is mandated. And conversely, IMS products as deployed in the real world do not factor neatly into the elements of the reference architecture, which complicates the process of comparing similar products with a benchmark. + +The problem can be simplified by observing that there are classes of products which have common subsets of reference architecture elements. For classes defined in this manner, common sets of benchmarks can be defined. The classes defined in this manner are called IMSs, or simply subsystems, and are expected to grow over time, as the IMS marketplace becomes richer. + +[ITU-T Q.3932.2], which is part of this multi-part deliverable, maintains a list and description of subsystems. + +In order to proceed from a subsystem description to a benchmark test, a complete description of all aspects of the subsystem relevant to the performance of the benchmark shall be present; this is referred to as the system configuration, or SUT configuration. This description starts with an enumeration of the elements of the reference architecture and an enumeration of all reference points that are external to the subsystem (i.e., reference points between elements within the subsystem are "internal"). However, the configuration requires a specification of the hardware elements (e.g., servers, central processor units (CPUs), network configuration and bandwidth) and software elements (e.g., operating system, database system), because even though the metrics reported by the benchmark tests are + +measured with respect to such metrics as total round-trip delay of messages and system capacity, the behaviour of IMSs is still an area of study and a thorough understanding of how CPU and network bandwidth utilization behaves during operation is of interest. + +Figure 3 depicts the II NNI between two IP multimedia (IM) core network (CN) subsystem networks. + +Figure 4 depicts the IMS/LTE basic configuration. + +Figure 5 depicts the LTE end-to-end configuration. + +Figure 6 depicts the access gateway control function (AGCF)/voice gateway (VGW) session processing model for IMS PES. + +![Figure 2 – Overview of IMS functional entities [ETSI TS 123 002]. This diagram illustrates the architecture of an IP Multimedia Subsystem (IMS). At the top, a box labeled 'IP multimedia networks' spans across the top of the diagram. Below this, several functional entities are shown in boxes: CS network, IMS-MGW, MRFP, BGCF (two instances), MGCF, MRFC, P-CSCF, I-CSCF, S-CSCF, HSS, SLF, MRB, AS, E-CSCF, LRF, EATF, IBCF, and TrGW. At the bottom, a UE (User Equipment) is connected to the TrGW. On the right, an LCS client is connected to the LRF. Interfaces are represented by lines: solid lines for user traffic (e.g., Mb, CS, Mp, Gm, Ix, Izi, Ut) and dashed lines for signaling (e.g., Mg, Mk, Mj, Mn, Mr, Mw, Mm, Ma, Cx, C, D, Gc, Gr, Dh, ISC, RC, Cr, I4, Mi, Le, Mm, Ix, Izi). A legend at the bottom left clarifies the line types. A note on the right indicates the source as Q.3932.1(15)_F02.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +Figure 2 – Overview of IMS functional entities [ETSI TS 123 002]. This diagram illustrates the architecture of an IP Multimedia Subsystem (IMS). At the top, a box labeled 'IP multimedia networks' spans across the top of the diagram. Below this, several functional entities are shown in boxes: CS network, IMS-MGW, MRFP, BGCF (two instances), MGCF, MRFC, P-CSCF, I-CSCF, S-CSCF, HSS, SLF, MRB, AS, E-CSCF, LRF, EATF, IBCF, and TrGW. At the bottom, a UE (User Equipment) is connected to the TrGW. On the right, an LCS client is connected to the LRF. Interfaces are represented by lines: solid lines for user traffic (e.g., Mb, CS, Mp, Gm, Ix, Izi, Ut) and dashed lines for signaling (e.g., Mg, Mk, Mj, Mn, Mr, Mw, Mm, Ma, Cx, C, D, Gc, Gr, Dh, ISC, RC, Cr, I4, Mi, Le, Mm, Ix, Izi). A legend at the bottom left clarifies the line types. A note on the right indicates the source as Q.3932.1(15)\_F02. + +NOTE 1: The reference point CS (Circuit Switched) is not specified in the present document. + NOTE 2: The reference point I5 is not shown in this figure. + +**Figure 2 – Overview of IMS functional entities [ETSI TS 123 002]** + +![Diagram of II-NNI between two IM CN subsystem networks (A and B).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +This diagram illustrates the Interconnection of two IM CN subsystem networks, labeled 'IM CN subsystem network A' and 'IM CN subsystem network B'. The networks are connected via an 'II-NNI' (Interconnection Interface), which is highlighted with a red oval and contains the interfaces 'Ici' (signalling) and 'Izi' (bearer). + On the left side (Network A), the components include: S-CSCF, I-CSCF, BGCF, ATCF, P-CSCF, IBCF, TrGW, and an MSC server enhanced for ICS or SRVCC. Signalling paths (dashed lines) are shown between S-CSCF, I-CSCF, BGCF, ATCF, P-CSCF, and IBCF. Bearer paths (solid lines) connect the MSC server to TrGW and IBCF to TrGW. Interfaces 'Mx' and 'Ix' are indicated between various components. + The right side (Network B) has a similar architecture. The connection between the two networks' TrGWs is a solid line representing the bearer interface 'Izi'. + +----- Signalling + ————— Bearer + +Q.3932.1(15)\_F03 + +Diagram of II-NNI between two IM CN subsystem networks (A and B). + +NOTE: Interface (II-NNI) between two IM CN subsystem networks. + +**Figure 3 – II NNI between two IM CN subsystem networks** + +![Diagram of IMS/LTE basic configuration showing UE, eNodeB, MME, S-GW, P-GW, and IMS core components.](8307f6b04df072c9332f9987e034272c_img.jpg) + +This diagram shows the basic configuration of an IMS/LTE network. A UE (User Equipment) with an IMS UA is connected to an eNodeB via an 'LTE-Uu' interface. The eNodeB is connected to an MME via 'S1-MME' (signalling) and 'S1-U' (bearer) interfaces. The MME is connected to an S-GW via an 'S11' interface. The S-GW is connected to a P-GW via an 'S5' interface. The P-GW is connected to a PCRF via a 'Gx' interface and to the IMS core via an 'SGi' interface. The PCRF is also connected to the MME via an 'Rx' interface. + The IMS core contains the following components: HSS, P-CSCF (which includes IMS-ALG and IMS-AGW), I/S-CSCF, and MMTel AS. The HSS is connected to the MME via an 'S6a' interface. The P-CSCF is connected to the HSS via a 'Gm' interface and to the I/S-CSCF via an 'Mw' interface. The I/S-CSCF is connected to the MMTel AS via an 'ISC' interface. The MMTel AS is connected to the HSS via a 'Sh' interface and to the P-CSCF via a 'Cx' interface. Additionally, the UE is connected to the IMS core via 'Ut' interfaces. + +Q.3932.1(15)\_F04 + +Diagram of IMS/LTE basic configuration showing UE, eNodeB, MME, S-GW, P-GW, and IMS core components. + +**Figure 4 – IMS/LTE basic configuration** + +![Figure 5 – LTE end-to-end configuration diagram showing two network paths (HPLMN and VPLMN) with various components like UE, eNodeB, Sec-GW, MME, H-PCRF, Diameter agent, S-GW, P-GW, IMS core, ENUM server, and IPX. The diagram illustrates the flow of signaling and data between these elements across different network domains.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +This diagram illustrates the LTE end-to-end configuration for IMS services. It is divided into two main sections: HPLMN (Home PLMN) and VPLMN (Visited PLMN), separated by a dashed line. + In the HPLMN section, a UE (User Equipment) with an IMS UA (User Agent) connects via LTE-Uu to an eNodeB, which is connected to a Sec-GW. The Sec-GW connects to an MME via S1-MME and S1-U interfaces. The MME connects to an H-PCRF via S6a and to a Diameter agent via S11. The H-PCRF connects to the Diameter agent via Rx. The Diameter agent connects to the IMS core via S6a, S9, and SGI interfaces. The IMS core contains various components: MMTel/RCS Application servers, MRF, HSS, P-CSCF/IMS-ALG/IMS-AGW, I/S-CSCF, IBCF/TrGW, and MRFP. The Diameter agent also connects to an ENUM server, which in turn connects to an IPX. + In the VPLMN section, a similar setup exists but with a V-PCRF instead of an H-PCRF. The V-PCRF connects to the Diameter agent via Rx. The Diameter agent in the VPLMN connects to the IMS core via S6a, S9, and SGI interfaces. The IMS core in the VPLMN contains P-CSCF/IMS-ALG/IMS-AGW, IBCF/TrGW, and MRFP. The Diameter agent in the VPLMN also connects to an ENUM server, which connects to an IPX. + The diagram shows various interfaces: Ut (orange), S6a (blue), S9 (blue), Rx (blue), Gx (blue), S11 (blue), S1-MME (blue), S1-U (blue), S5 (blue), SGI (blue), Diameter App ID=0 (red), ENUM (red), Ici/Izi (red), and Gm (red). + +Figure 5 – LTE end-to-end configuration diagram showing two network paths (HPLMN and VPLMN) with various components like UE, eNodeB, Sec-GW, MME, H-PCRF, Diameter agent, S-GW, P-GW, IMS core, ENUM server, and IPX. The diagram illustrates the flow of signaling and data between these elements across different network domains. + +Figure 5 – LTE end-to-end configuration + +![Figure 6 – AGCF/VGW session processing models diagram showing two models (VGW and AGCF) connected to an RTP cloud. Each model includes components like AS, S-CSCF, P-CSCF, MGC, FM, SIP UA, and MGF. The diagram illustrates the flow of signaling and data between these elements.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +This diagram illustrates the AGCF/VGW session processing models. It shows two models: VGW and AGCF. Both models are connected to an RTP cloud. + In the VGW model, a UE connects 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, which contains MGC, FM, and SIP UA. The VGW is connected to an MGF, which is connected to the RTP cloud. + In the AGCF model, a UE connects to an AGCF, which contains SIP UA, FM, and MGC. The AGCF is connected to an S-CSCF, which is connected to an AS. The AGCF is also connected to an MGF, which is connected to the RTP cloud. + The diagram shows various components: AS (Application Server), S-CSCF (Serving CSCF), P-CSCF (PDN CSCF), MGC (Media Gateway Controller), FM (Function Module), SIP UA (SIP User Agent), VGW (VGW), AGCF (AGCF), and MGF (Media Gateway Function). + +Figure 6 – AGCF/VGW session processing models diagram showing two models (VGW and AGCF) connected to an RTP cloud. Each model includes components like AS, S-CSCF, P-CSCF, MGC, FM, SIP UA, and MGF. The diagram illustrates the flow of signaling and data between these elements. + +Figure 6 – AGCF/VGW session processing models + +### Creation of subscriber database + +The subscriber database is the data set required to configure the SUT in order to execute a benchmark test. Using the same data, the test system should be able to generate correct traffic. + +The present document does not try to specify a complete set, but rather just the subset that will ensure comparable results. All other provisioning information required for correct configuration of a SUT is to be set at the discretion of the SUT provider. + +One requirement for a fair benchmark is that the input data is similar for all test-runs. In order for this to happen we have two choices: + +- a) provide a database for the subscriber base. However, because we have to ensure scalability for the benchmark, this solution is not feasible; +- b) provide rules to generate this data and data generators. Algorithms using random generators will be avoided for data that could possibly influence the results. + +# **8 Test system** + +The test system is used to generate the appropriate load on the SUT. The present document does not mandate any specific test system to be used, although the details of the test system shall be reported in the benchmark report. + +The test system should have two main functions: + +- traffic generation: the test system shall be able to execute use cases' scenarios following the traffic-time profile. It shall also be able to reproduce the appropriate traffic set (a mix of scenarios with a weight for each of them); +- network emulation: optionally, network characteristics on the different interfaces should be emulated by the test system. + +## **9 Benchmark metrics examples** + +The metrics reported by a benchmark test are measured in real time during the execution of the test, or may be computed after completion of the test from event logs collected during the execution. Enclosed is a benchmark matrix based on [ETSI TS 101 563]. + +**Table 2 – Benchmark metrics examples** + +| Delay parameters | Description | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call request delay | 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 | +| Alerting sending | Call request delay is defined as the interval from the instant at which the 180 Ringing is received from the terminating subscriber until the 180 Ringing is passed back to the originating subscriber | +| Call set up delay | The time interval starts when the digit collection function determines that the address information received in the INFO or subsequent INVITE message is sufficient for session initiation, and ends when the INVITE message on the Ic or terminating Gm interface has been sent | +| Through connection delay | 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 | +| Connection release delay | Connection release delay is defined as the interval from the instant when a BYE message (BYE) is received at the originating or terminating Gm interface until the instant when 200 OK is sent and a corresponding BYE is sent at the terminating or originating Gm interface respectively | +| Speech quality analysis | | +| Speech quality | [ITU-T P.862] and [ITU-T P.862.1] | +| | [ITU-T P.863] | +| Speech level – active level | [ITU-T P.56] | +| Speech level – peak | | +| Speech level – noise | | +| Speech level – signal to interval noise | | + + + + + +## 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 | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbc06bf97d4bf33e26b453a1602ce986a75a31ba --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47399445e06db02d12c7c715d5acd09300ee2344a71be75d327ab150fa0d7462 +size 75577 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..525691cea0ea5ac3264b008fa5d7a582e11fe6dc --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454b98c591f24d851c93db0d49f8c19420534cad8210ace800342f2024492fa0 +size 23650 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c8f8c15b3f366b7d4080f7244c83b3f33d204ea --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:116e5017225839bb7324c06a74650855e6093dfeecdb090432eca9ee787510ba +size 57450 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dad02182b30e94f721c7f50726f60641c96df521 --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45bf920a7798c0111eed0c87f3f277105f8935167814eaedd42f96a3f983bba0 +size 4024 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..711545244bf9e5f9abddcd42f24ff2130d5c4f6a --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e6f14d9b6e5fd033b82eb4f9ec1b608d9942cfedfc34779383a119b5fcf7233 +size 100294 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d994add8213c96fc4e54a3010645088694f21b26 --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03762a50edd3a30af722b42b7244105f31743106ef8988f7ea04c0e24d74ed98 +size 36390 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4022393e79d76198e8a379c4e80941692d562031 --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e72a19206801ef55016d12cef4bc6c9e827c7bf8e2ee9ba5e66c9b9f3cf902c8 +size 182035 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..459d9fa4e72114fa7a9206b9e431e929f2097f26 --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccc435d3890d26bb8eb664ec64f3008c752a9afa9644e6ad5177cb07aaa5f72e +size 11494 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0ecdbad50db7844551dd0afccc92d489e073a6f --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d7cf346f94150790035a6c6944c212ef993b890c2a428b4badbc10cf2b66b95 +size 50921 diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bffc0c0116b562d041b8849c4c8e8642160bc19d --- /dev/null +++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7b7700e52e56cca92d58a243bf7837450ea392b8efa328287ac3d21efb93e2b +size 15537 diff --git a/marked/Q/T-REC-Q.3957-202504-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..243b3dd39541bdaa7869ecb9b678b3f32103ce51 --- /dev/null +++ b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/raw.md @@ -0,0 +1,899 @@ + + +# Recommendation**ITU-T Q.3957 (04/2025)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Testing specifications – Testing specifications for next generation networks + +--- + +### **Interoperability testing suite for cloud-based control plane and pooled user plane of virtualized broadband network gateway** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like design. + +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 | +| 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 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T Q.3957 + +# Interoperability testing suite for cloud-based control plane and pooled user plane of virtualized broadband network gateway + +## Summary + +Recommendation ITU-T Q.3957 aims to specify the interoperability testing suite for cloud-based control plane and pooled user plane (UP) of virtualized broadband network gateway (vBNG), which is based on the signalling requirements of vBNG in Recommendation ITU-T Q.4143. As a background, this Recommendation gives an overview of interoperability testing between the vBNG control plane (vBNG-CP) and vBNG pooled user plane (vBNG-PUP). This Recommendation also deals with interoperability testing of two target areas, including the interoperability testing between vBNG-CP and vBNG-PUP, interoperability testing between vBNG-PUPs, and all the test cases are designed around these two target areas. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.3957 | 2025-04-13 | 11 | 11.1002/1000/16291 | + +## Keywords + +Cloud-based control plane, interoperability testing, pooled user plane, virtualized broadband network gateway. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview of IOPT framework for vBNG-CP and vBNG-PUP..... | 2 | +| 7 Interoperability testing cases between vBNG-CP and vBNG-PUP ..... | 4 | +| 7.1 Test case: Establish the management channel..... | 4 | +| 7.2 Test case: Establish the control channel..... | 4 | +| 7.3 Test case: Establish the service channel..... | 5 | +| 7.4 Test case: PPPoE ..... | 5 | +| 7.5 Test case: IPoE ..... | 6 | +| 7.6 Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP ..... | 7 | +| 7.7 Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP ..... | 9 | +| 8 Interoperability testing cases between different vBNG-PUPs..... | 10 | +| 8.1 Test case: vBNG-PUP joins the warm standby group..... | 10 | +| 8.2 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the user accessing process) ..... | 11 | +| 8.3 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the forwarding process) ..... | 12 | +| 8.4 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the user accessing process) ..... | 13 | +| 8.5 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the forwarding process)..... | 13 | +| 8.6 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the user accessing process) ..... | 14 | +| 8.7 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the forwarding process) ..... | 15 | +| 8.8 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the user accessing process) ..... | 16 | +| 8.9 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the forwarding process)..... | 17 | +| 8.10 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the user accessing process) ..... | 18 | +| 8.11 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the forwarding process) ..... | 19 | + +| | Page | +|---------------------------------------------------------------------------------------------------------------------------------|-------------| +| 8.12 Test case: Interface switching in vBNG-PUP N:1 cold standby group
(Switch back during the user accessing process) ..... | 20 | +| 8.13 Test case: Interface switching in vBNG-PUP N:1 cold standby group
(Switch back during the forwarding process)..... | 21 | +| 8.14 Test case: CGN switching (cold standby) ..... | 22 | +| 8.15 Test case: CGN switching (warm standby) ..... | 23 | + +# Recommendation ITU-T Q.3957 + +# Interoperability testing suite for cloud-based control plane and pooled user plane of virtualized broadband network gateway + +# 1 Scope + +This Recommendation specifies the interoperability testing suite for cloud-based virtualized broadband network gateway control plane (vBNG-CP) and pooled user plane (vBNG-PUP). The following aspects are addressed in this Recommendation: + +- Overview of interoperability testing (IOPT) framework for vBNG-CP and vBNG-PUP. +- Interoperability testing cases between vBNG-CP and vBNG-PUP. +- Interoperability testing cases between different vBNG-PUPs. + +# 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.3315] Recommendation ITU-T Q.3315 (2015), *Signalling requirements for flexible network service combination on broadband network gateway*. +- [ITU-T Q.3719] Recommendation ITU-T Q.3719 (2019), *Signalling requirements for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG)*. +- [ITU-T Q.4064] Recommendation ITU-T Q.4064 (2020), *Interoperability testing requirements for a virtualized broadband network gateway*. +- [ITU-T Q.4143] Recommendation ITU-T Q.4143 (2024), *Signalling requirements for cloud-based control plane and pooled user plane of virtualized broadband network gateway (vBNG)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 broadband network gateway (BNG)** [ITU-T Q.3315]: The access point to the provider's IP network for wireline broadband services. + +**3.1.2 virtualized broadband network gateway (vBNG)** [ITU-T Q.4064]: A virtualized solution of a broadband network gateway, attained by using virtualization technologies. vBNG is responsible for user access and traffic forwarding to realize broadband services and is also called virtualized broadband remote access server (vBRAS). + +**3.1.3 vBNG control plane** [ITU-T Q.3719]: The vBNG control plane is in charge of the control functions, including authentication, authorization and accounting (AAA) management function, Internet protocol (IP) address management function, user management function, access protocol processing function, and vBNG user plane management function, etc. The vBNG control plane is implemented using the virtualization technologies and deployed in the mode of centralization. + +**3.1.4 vBNG user plane** [ITU-T Q.3719]: The vBNG user plane mainly provides user packets switching under the instruction of the vBNG control plane. The vBNG user plane (UP) can be implemented in different types of forwarding hardware, including NP-based dedicated equipment, ASIC-based dedicated equipment, or X86-based commercial equipment. + +## **3.2 Terms defined in this Recommendation** + +None. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| ACL | Access Control List | +| CGN | Carrier Grade NAT | +| CP | Control Plane | +| CPU | Central Processing Unit | +| CU | Control plane and User plane | +| CUSP | Control plane and User plane Separated Protocol | +| IOPT | Interoperability Testing | +| IP | Internet Protocol | +| IPoE | IP over Ethernet | +| IS-IS | Intermediate System-Intermediate System | +| NAT | Network Address Translation | +| PPP | Point-to-Point Protocol | +| PPPoE | Point-to-Point Protocol over Ethernet | +| UP | User Plane | +| vBIT | vBNG Interoperability Tester | +| vBNG | Virtual Broadband Network Gateway | + +## **5 Conventions** + +None. + +# **6 Overview of IOPT framework for vBNG-CP and vBNG-PUP** + +Virtual broadband network gateway (vBNG) serves as the access point to the provider's broadband network. Compared with the traditional vBNG architecture defined in [ITU-T Q.3719], the cloud-based control plane (CP) and pooled user plane vBNG concentrates on the reliability between vBNG-CP and vBNG-PUP. Hence, except for the basic layer 2 and layer 3 functions, the interoperability should include failure detection as well as switching of vBNG-CP and vBNG-PUP. + +Since [ITU-T Q.4143] defines the signalling requirements between vBNG-CP and vBNG-PUP, this Recommendation aims to verify whether the interactions are as expected as those described in [ITU-T Q.4143]. + +There are two target areas that should be considered during interoperability testing (IOPT), as shown in Figure 6-1: + +- target area 1: IOPT between vBNG-CP and vBNG-PUP. +- target area 2: IOPT between vBNG-PUPs. + +![Diagram of vBNG architecture showing the Control Plane (CP) connected to multiple User Plane (PUP) units (PUP1, PUP2, PUPn) within a pooled user plane. Red lines with circled numbers 1 and 2 indicate interoperability test areas: 1 between CP and PUP2, and 2 between PUP2 and PUPn. A legend at the bottom right indicates red lines represent 'Interoperability test'. The diagram is labeled Q.3957(25).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Diagram of vBNG architecture showing the Control Plane (CP) connected to multiple User Plane (PUP) units (PUP1, PUP2, PUPn) within a pooled user plane. Red lines with circled numbers 1 and 2 indicate interoperability test areas: 1 between CP and PUP2, and 2 between PUP2 and PUPn. A legend at the bottom right indicates red lines represent 'Interoperability test'. The diagram is labeled Q.3957(25). + +**Figure 6-1 – Interoperability testing areas for vBNG-CP and vBNG-PUP of vBNG** + +For the target area 1, the IOPT includes user accessing, failure detection and user switching under the instruction of vBNG-CP. + +For the target area 2, the IOPT between vBNG-PUPs include standby group switching as well as carrier grade NAT (CGN) backup switching. + +The test entities include vBNG-CP and vBNG-PUP, and the IOPT between the entities includes the IOPT of vBNG-CP and vBNG-PUP, vBNG-PUP and vBNG-PUP. + +For each target area, specific relevant test cases need to be provided to verify different capabilities in different functions. Noted that the basic test cases are described in [ITU-T Q.4064]. The test cases in this Recommendation concentrate on the new characteristics or different operation steps introduced by the pooling of vBNG-UPs. At the same time, this Recommendation follows the signalling requirements of [ITU-T Q.4143] and provides vBNG-CP and vBNG-PUP IOPT related test cases, as shown in Table 6-1. + +**Table 6-1 – Interoperability testing suite overview for cloud-based control plane and pooled user plane of vBNG** + +| Target area | Specific relevant test cases | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| Area 1: IOPT between vBNG-CP and vBNG-PUP | Establishing a management channel | +| | Establishing a control channel | +| | Establishing a service channel | +| | Point-to-point protocol over ethernet (PPPoE) | +| | IP over ethernet (IPoE) | +| | vBNG-CP switching (hot standby and cold standby) | +| Area 2: IOPT between vBNG-PUPs | Interface switching over or switching back during the process of the user accessing or forwarding in the warm/cold standby group | + +# 7 Interoperability testing cases between vBNG-CP and vBNG-PUP + +## 7.1 Test case: Establish the management channel + +Table 7-1 shows the test case for establishing the management channel in order to transmit configuration from vBNG-CP to vBNG-PUP. + +**Table 7-1 – Test case: Establish the management channel** + +| Test description | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test purpose | | To verify that vBNG supports establishing the management channel. | | | +| Reference | | [ITU-T Q.4143] clause 7.4 | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login to the configuration interface of vBNG-CP. | | +| | 2 | Stimulus | Configure the loopback addresses of vBNG-CP and vBNG-PUP for underlying Internet protocol (IP) interoperability between vBNG-CP and vBNG-PUP with intermediate system-intermediate system (IS-IS) or static routing. | | +| | 3 | Stimulus | Enable Netconf function on vBNG-PUP and vBNG-CP respectively and configure SSH connection policy and Netconf connection policy. | | +| | 4 | Stimulus | Enter the vBNG-PUP view. Create a control plane and user plane separated protocol (CUSP) agent, configure the IP address of the CUSP agent at vBNG-PUP and bind the CUSP agent, as well as the Netconf connection policy. There is the expected result 1. | | +| | 5 | Stimulus | vBNG-CP delivers the configuration to vBNG-PUP. There is the expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The management channel has been successfully established between vBNG-CP and vBNG-PUP. | | +| | 2 | Check | vBNG-PUP can receive the command. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +## 7.2 Test case: Establish the control channel + +Table 7-2 shows the test case for establishing the control channel in order to transmit the user table entry and report interface/board/device information. + +**Table 7-2 – Test case: Establish the control channel** + +| Test description | | +|-------------------------|----------------------------------------------------------------| +| Test purpose | To verify that vBNG supports establishing the control channel. | +| Reference | [ITU-T Q.4143] clause 7.4 | + +**Table 7-2 – Test case: Establish the control channel** + +| | | | | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP. | | +| | 2 | Stimulus | Configure the loopback addresses of vBNG-CP and vBNG-PUP for underlying IP interoperability between vBNG-CP and vBNG-PUP with intermediate system-intermediate system (IS-IS) or static route. | | +| | Step | Type | Description | | +| Expected results | 3 | Stimulus | Configure CUSP agent on vBNG-PUP and vBNG-CP, configure the IP address of the CUSP agent at the vBNG-PUP side, and bind the CUSP agent. There is expected result 1. | | +| | Step | Type | Description | Result | +| | 1 | Check | The control channel has been successfully established between vBNG-CP and vBNG-PUP. | | +| Notes | | | | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | | + +## 7.3 Test case: Establish the service channel + +Table 7-3 shows the test case for establishing the service channel in order to transmit accessing packet from users. + +**Table 7-3 – Test case: Establish the service channel** + +| | | | | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test description | | | | | +| Test purpose | To verify that vBNG supports establishing the service channel. | | | | +| Reference | [ITU-T Q.4143] clause 7.2 | | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP. | | +| | 2 | Stimulus | Configure the vBNG-CP and vBNG-PUP loopback addresses for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | Create and bind VxLAN channels on vBNG-PUP and vBNG-CP, configure the source and destination IP addresses. There is expected result 1. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The service channel has been successfully established between vBNG-CP and vBNG-PUP. | | +| Notes | | | | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | | + +### 7.4 Test case: PPPoE + +Table 7-4 shows the test case for the PPPoE access function. + +**Table 7-4 – Test case: PPPoE** + +| Test description | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test purpose | | To verify that vBNG provides PPPoE access function, which includes providing point-to-point protocol (PPP) connection with vBNG-CPE/vvBNG-CPE and allocating an IP address for the user to access the Internet. | | | +| Reference | | [ITU-T Q.4064] clause 8.2 | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG. | | +| | 2 | Stimulus | Configure user access domain name "pppoe" in vBNG-CP. Create a PPPoE user account "test1@pppoe". | | +| | 3 | Stimulus | Configure the authentication mode as local and configure the address allocation method as local assignment. | | +| | 4 | Stimulus | vBNG interoperability tester (vBIT) simulates as PPPoE user "test1" dialing in through vBNG-CPE/vvBNG-CPE.
NOTE – vBIT refers to the test tool which can simulate as a user or network equipment to help complete the IOPT of vBNG. | | +| | 5 | Stimulus | Capture the packets on vBNG-CP. There is expected result 1. | | +| | 6 | Stimulus | Check the user entry on vBNG-CP. Check whether user "test1" can obtain an IP address. There is expected result 2. | | +| | 7 | Stimulus | Check the forwarding table on vBNG-PUP. There is expected result 3. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | There are N PPPoE packets uploaded by vBNG-PUP (N depends on the number of vBNG-PUPs). | | +| | 2 | Check | User "test1" can obtain an IP address and access the Internet. | | +| | 3 | Check | Only the selected vBNG-PUP has the specific forwarding entry of user "test1". | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +## 7.5 Test case: IPoE + +Table 7-5 shows the test case for the IPoE access function. + +**Table 7-5 – Test case: IPoE** + +| IPoE test description | | | | | +|------------------------------|-------------|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|--| +| Test purpose | | To verify that vBNG supports IPoE service, including providing related access and control functions. | | | +| Reference | | [ITU-T Q.4064] clause 8.1 | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG. | | +| | 2 | Stimulus | Configure user access domain name "ipoe" in vBNG. Create an IP over ethernet (IPOE) user account "test2@ipoe". | | + +**Table 7-5 – Test case: IPoE** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------| +| | Step | Type | Description | | +| | 3 | Stimulus | Configure the authentication mode as local and configure the address allocation method as local assignment. | | +| | 4 | Stimulus | vBIT simulates as IPoE user "test2" dialing in through vBNG-CPE/vvBNG-CPE. | | +| | 5 | Stimulus | Capture the packets on vBNG-CP. There is expected result 1. | | +| | 6 | Stimulus | Check the user entry on vBNG-CP. Check whether user "test2" can obtain an IP address. There is expected result 2. | | +| | 7 | Stimulus | Check the forwarding table on vBNG-PUP. There exists result 3. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | There are N IPoE packets uploaded by vBNG-PUP (N depends on the number of vBNG-PUPs). | | +| | 2 | Check | User "test2" can obtain an IP address and access the Internet. | | +| | 3 | Check | Only the selected vBNG-PUP has the specific forwarding entry of user "test2". | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +## **7.6 Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP** + +Table 7-6 shows the vBNG-CP switching between the master vBNG-CP and backup vBNG-CP. + +**Table 7-6 – Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP** + +| | | | | | +|-------------------------|-------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Test description | | | | | +| Test purpose | To verify that vBNG supports vBNG-CP switching. | | | | +| Reference | [ITU-T Q.4143] clause 7.5 | | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup vBNG-PUP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route; Configure CU channel: service interface, control interface, and management interface. | | +| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | | + +**Table 7-6 – Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP** + +| | | | | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| | Step | Type | Description | | +| | 4 | Stimulus | Cut off the CU channel between vBNG-CP and UP (both service/control/management interfaces are cut off), observe the switching between the master and backup vBNG-CP, there is expected result 1; Check the user's accessing status and there is expected result 2. | | +| | 5 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | | +| | 6 | Stimulus | Cut off the heartbeat channel between the master and backup vBNG-CP, observe the switching situation of the master and backup vBNG-CP, there is expected result 3; Check the user's accessing status and there is expected result 4. | | +| | 7 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | | +| | 8 | Stimulus | Reboot the master vBNG-CP and observe the switching between the master and backup vBNG-CP, there is expected result 5; Check the user's accessing status and there is expected result 6. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The master vBNG-CP changes to backup vBNG-CP, the original backup vBNG-CP upgrades to master vBNG-CP. | | +| | 2 | Check | Newly accessing users will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP), there is no effect on the former users which have been authenticated and are online. | | +| | 3 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | | +| | 4 | Check | Newly accessing users will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP), there is no effect of the former users which have been authenticated and are online. | | +| | 5 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | | +| | 6 | Check | Newly accessing users will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP), there is no effect of the former users which have been authenticated and are online. | | +| Notes | | | | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | | + +## 7.7 Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP + +Table 7-7 shows the vBNG-CP switching between master vBNG-CP and backup vBNG-CP. + +**Table 7-7 – Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP** + +| Test description | | | | | +|-------------------------|-------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test purpose | | To verify that vBNG supports vBNG-CP switching. | | | +| Reference | | [ITU-T Q.4143] clause 7.5 | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route; Configure CU channel: service interface, control interface, and management interface. | | +| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | | +| | 4 | Stimulus | Cut off the CU channel between vBNG-CP and UP (both service/control/management interfaces are cut off), check the switching between the master and backup vBNG-CP, there is expected result 1; Check the user's accessing status and there is expected result 2. | | +| | 5 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | | +| | 6 | Stimulus | Cut off the heartbeat channel between the master and backup vBNG-CP, check the switching situation of the master and backup vBNG-CP, there is expected result 3; Check the user's accessing status and obtaining the result. | | +| | 7 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | | +| | 8 | Stimulus | Reboot the master vBNG-CP and observe the switching between the master and backup vBNG-CP, there is expected result 5; Check the user's accessing status and there is expected result 6. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | | +| | 2 | Check | Newly accessing users will not be online during the switching process. The original users will be booted offline. All the users have to redial and will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP). | | +| | 3 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | | + +**Table 7-7 – Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP** + +| | Step | Type | Description | Result | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | 4 | Check | Newly accessing users will not be online during the switching process. The original users will be booted offline. All the users have to redial and will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP). | | +| | 5 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | | +| | 6 | Check | Newly accessing users will not be online during the switching process. The original users will be booted offline. All the users have to redial and will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP). | | +| Notes | | | | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | | + +# 8 Interoperability testing cases between different vBNG-PUPs + +Here, the "warm standby group" of vBNG-PUP means a group of accessing interfaces from different vBNG-PUP with a warm standby mechanism defined in [ITU-T Q.4143]. + +The mechanism "warm standby" of vBNG-PUP means that users' entries will be synchronized after the interface within the warm standby group is fault. The mechanism "cold standby" of vBNG-PUP means the user entries will not be synchronized, and users have to redial to be online [ITU-T Q.4143]. + +The mechanism "warm standby" of the CGN card in vBNG-PUP means that the user entries will be synchronized to the other CGN cards within the device after the CGN card is at fault. The mechanism "cold standby" means the user entries will not be synchronized and have to be regenerated between different devices [ITU-T Q.4143]. + +The action "switch over" means that switching after the device is at fault, "switch back" means that switching after the fault device is recovered. + +### 8.1 Test case: vBNG-PUP joins the warm standby group + +Table 8-1 shows the test case for joining the warm standby group. + +**Table 8-1 – Test case: vBNG-PUP joins the warm standby group** + +| Test description | | | | | +|------------------------|------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------|--| +| Test purpose | To verify that vBNG-PUP supports joining the warm standby group. | | | | +| Reference | [ITU-T Q.4143] clause 8.2 | | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | There are four vBNG-PUPs, namely vBNG-PUP1~vBNG-PUP4. Enter the vBNG-CP configuration interface. | | + +**Table 8-1 – Test case: vBNG-PUP joins the warm standby group** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| | Step | Type | Description | | +| | 2 | Stimulus | Configure the number of vMAC (virtual MAC) addresses for interfaces within the warm standby group, vMAC address can be configured, or by default, vMAC address is automatically assigned if by default. | | +| | 3 | Stimulus | Add the interfaces of vBNG-PUP1~vBNG-PUP4 to the warm standby group in the vBNG-CP command window and check the vMAC address. There is expected result 1. | | +| | 4 | Stimulus | The vBIT sends a broadcast stream to the vBNG-PUPs and observes whether the interfaces in the warm standby group achieves load balancing. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The interface of vBNG-PUP1-vBNG-PUP4 have been joined to the same standby group. | | +| | 2 | Check | Load balancing of traffic in the standby group. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +## **8.2 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the user accessing process)** + +Table 8-2 shows the interface switching in the vBNG-PUP warm standby group. + +**Table 8-2 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | | | | +|-------------------------|--------------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Test description | | | | | +| Test purpose | To verify that vBNG supports interface switching in the vBNG-PUP warm standby group. | | | | +| Reference | [ITU-T Q.4143] clause 8.2 | | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join warm standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | | +| | 4 | Stimulus | Shutdown interface 1 of vBNG-PUP1 during the user's dialling process, observe the user's status. There is expected result 1. | | +| | 5 | Stimulus | Check the load balancing of traffic on other interfaces within the warm standby group. There is expected result 2. | | + +**Table 8-2 – Test case: Interface switching in vBNG-PUP warm standby group** + +| Expected results | Step | Type | Description | Result | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------|--------| +| | 1 | Check | A small number of users dialling packet loss and retransmission. Finally, all users were able to go online normally. | | +| | 2 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | | + +## **8.3 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the forwarding process)** + +Table 8-3 shows the test case for interface switching in vBNG-PUP warm standby group. + +**Table 8-3 – Test case: Interface switching in vBNG-PUP warm standby group** + +| Test description | | | | | +|-------------------------|----------------------------------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | | | | +| Reference | [ITU-T Q.4143] clause 8.2 | | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup user plane (UP)). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. | | +| | 4 | Stimulus | During the traffic forwarding process, shutdown interface 1 of vBNG-PUP1, observe the packet loss situation. There is expected result 1. | | +| | 5 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | Some packet loss in the traffic when the status is switching. After finishing the switching, the traffic forwards normally. | | +| | 2 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | | + +**Table 8-3 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notes | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | + +### 8.4 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the user accessing process) + +Table 8-4 shows the test case for interface switching in vBNG-PUP warm standby group. + +**Table 8-4 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | | | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test description | | | | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | | | | +| Reference | [ITU-T Q.4143] clause 8.2 | | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | | +| | 4 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | | +| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the user's accessing process, check the user's status on vBNG-CP. There is expected result 1. | | +| | 6 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | There is packet loss during accessing progress which affects new users. Old users will stay online. Finally, all users will be online. | | +| | 2 | Check | Load balancing of traffic in the standby group. | | +| Notes | | | | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | | + +### 8.5 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the forwarding process) + +Table 8-5 shows the test case for interface switching in vBNG-PUP warm standby group. + +**Table 8-5 – Test case: Interface switching in vBNG-PUP warm standby group** + +| Test description | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test purpose | | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | | | +| Reference | | [ITU-T Q.4143] clause 8.2 | | | +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | | +| | 4 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. There is expected result 1. | | +| | 5 | Stimulus | Reopen interface 1 of vBNG-PUP1. | | +| | 6 | Stimulus | Check the user accessing status on vBNG-CP. There is expected result 2. | | +| | 7 | Stimulus | Check the load balancing of the interface within the warm standby group. There is expected result 3. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | There is no packet loss in traffic and keeping normal forwarding on vBNG-PUP2~vBNG-PUP4. | | +| | 2 | Check | All users will be kept online. | | +| | 3 | Check | Load balancing of traffic in the standby group. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +### **8.6 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the user accessing process)** + +Table 8-6 shows the interface switching in vBNG-PUP warm standby group. + +**Table 8-6 – Test case: Interface switching in vBNG-PUP warm standby group** + +| Test description | | +|-------------------------|----------------------------------------------------------------------------------| +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-6 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | | +| | 4 | Stimulus | Shutdown interface 1 of vBNG-PUP1 during the user's dialling process, observe the user's status. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP1~vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. | | +| | 2 | Check | A small number of users dialling packet loss and retransmission. Finally, all users were able to go online normally. | | +| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +### 8.7 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the forwarding process) + +Table 8-7 shows the test case for interface switching in vBNG-PUP warm standby group. + +**Table 8-7 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | +|-------------------------|----------------------------------------------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-7 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | | | | +|-------------------------|-------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | | +| | 4 | Stimulus | During the traffic forwarding process, shutdown interface 1 of vBNG-PUP1, observe the packet loss situation. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP1~vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. | | +| | 2 | Check | Some packet loss in the traffic when the status is switching. After finishing the switching, the traffic forwards normally. | | +| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | + +### 8.8 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the user accessing process) + +Table 8-8 shows the test case for interface switching in vBNG-PUP warm standby group. + +**Table 8-8 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | +|-------------------------|----------------------------------------------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-8 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | | | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying Internet protocol (IP) interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | | +| | 4 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | | +| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the user's accessing process, check the user's status on vBNG-CP. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. | | +| | 2 | Check | There is packet loss during accessing progress. All users will stay online. | | +| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. | | +| Notes | | | | | +| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | | + +### 8.9 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the forwarding process) + +Table 8-9 shows the test case for interface switching in vBNG-PUP warm standby group. + +**Table 8-9 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | +|-------------------------|----------------------------------------------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-9 – Test case: Interface switching in vBNG-PUP warm standby group** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | | +| | 4 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | | +| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the packet forwarding process, check the user's status on vBNG-CP. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. | | +| | 2 | Check | All users will stay online. | | +| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +### **8.10 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the user accessing process)** + +Table 8-10 shows the interface switching in vBNG-PUP warm standby group. + +**Table 8-10 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | +|-------------------------|-----------------------------------------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-10 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | | +| | 4 | Stimulus | Shutdown interface 1 of vBNG-PUP1 during the user's dialling process, observe the user's status and forwarding table on vBNG-PUP4. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. | | +| | 2 | Check | When vBNG-PUP1 first switches to vBNG-PUP4, the forwarding table is empty and retrieves from vBNG-CP. A small number of users dialling packet loss and retransmission. Finally, all users were able to go online normally. | | +| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +### 8.11 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the forwarding process) + +Table 8-11 shows the test case for interface switching in vBNG-PUP cold standby group. + +**Table 8-11 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | +|-------------------------|-----------------------------------------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-11 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the forwarding table on vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | | +| | 4 | Stimulus | During the traffic forwarding process, shutdown interface 1 of vBNG-PUP1, observe the packet loss situation and observe the forwarding table on vBNG-PUP4. There is expected result 2. | | +| Expected results | 5 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 3. | | +| | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. There is no forwarding table on vBNG-PUP4. | | +| | 2 | Check | When vBNG-PUP1 first switches to vBNG-PUP4, the forwarding table is empty then it retrieves from vBNG-CP. All traffic is interrupted then gradually recovers. | | +| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +## **8.12 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch back during the user accessing process)** + +Table 8-12 shows the test case for interface switching in vBNG-PUP cold standby group. + +**Table 8-12 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | +|-------------------------|-----------------------------------------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-12 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | | +| | 4 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. Check the forwarding table on vBNG-PUP4. There is expected result 1. | | +| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the user's accessing process, check the user's status on vBNG-CP. There is expected result 2. | | +| | 6 | Stimulus | Check the load balancing of traffic between other interfaces within the standby group. Check the forwarding table on vBNG-PUP4. There is expected result 3. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. There is a forwarding table on vBNG-PUP4. | | +| | 2 | Check | There is packet loss during accessing progress. All users will stay online. | | +| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. The forwarding table will expire on vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +### 8.13 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch back during the forwarding process) + +Table 8-13 shows the test case for interface switching in vBNG-PUP cold standby group. + +**Table 8-13 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | +|-------------------------|-----------------------------------------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-13 – Test case: Interface switching in vBNG-PUP cold standby group** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | | +| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | | +| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | | +| | 4 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. Check the forwarding table on vBNG-PUP4. There is expected result 1. | | +| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the packet forwarding process, check the user's status on vBNG-CP. There is expected result 2. | | +| Expected results | 6 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 3. | | +| | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. There is a forwarding table on vBNG-PUP4. | | +| | 2 | Check | All users will stay online. | | +| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. The forwarding table will expire on vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +## 8.14 Test case: CGN switching (cold standby) + +Table 8-14 shows the test case for CGN switching. + +**Table 8-14 – Test case: CGN switching (cold standby)** + +| | | +|-------------------------|---------------------------------------------| +| Test description | | +| Test purpose | To verify that vBNG supports CGN switching. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-14 – Test case: CGN switching (cold standby)** + +| Test procedures | Step | Type | Description | | +|------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | 1 | Stimulus | >Login the vBNG-PUP. Config network address translation (NAT) service location (instruct load balance on vBNG-central processing unit (CPU) of CGN card), service instance group (binding the service location) and create NAT instance. Then config warm standby group on vBNG-PUP1~vBNG-PUP4. | | +| | 2 | Stimulus | Config the basic function of CGN, such as network segment, port block, traffic steering policy based on access control list (ACL) and NAT translation policy. The users on CGN cards of vBNG-PUP1~vBNG-PUP4 load balanced and normally access the Internet. | | +| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Record the CGN table of vBNG-PUP1. | | +| | 4 | Stimulus | Shutdown the CGN cards on vBNG-PUP1. | | +| | 5 | Stimulus | Check the user traffic. There is expected result 1. | | +| | 6 | Stimulus | Check the CGN table on vBNG-PUP2~vBNG-PUP4. There is expected result 2. | | +| | 7 | Stimulus | Check the user entries including mapping the relationship between public network address and private network address, as well as the corresponding port blocks. There is expected result 3. | | +| Expected results | Step | Type | Description | | +| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the CGN cards of vBNG-PUP1 has been shut down. | | +| | 2 | Check | vBNG-PUP2~vBNG-PUP4 regenerates CGN tables (Reassign private and public network mapping relationships and port blocks) of the original users carried by vBNG-PUP1, which means that the public network addresses have been reallocated. | | +| | 3 | Check | vBNG-CP has refreshed the mapping relationship between public network address and private network address, as well as the corresponding port blocks of user entries on vBNG-PUP2~vBNG-PUP4. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + +## 8.15 Test case: CGN switching (warm standby) + +Table 8-15 shows the test case for carrier grade NAT (CGN) switching (warm standby). + +**Table 8-15 – Test case: CGN switching (warm standby)** + +| Test description | | +|------------------|----------------------------------------------------------------------------| +| Test purpose | To verify that vBNG supports CGN warm-standby switching within the device. | +| Reference | [ITU-T Q.4143] clause 8.2 | + +**Table 8-15 – Test case: CGN switching (warm standby)** + +| | | | | | +|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Test procedures | Step | Type | Description | | +| | 1 | Stimulus | Login the vBNG-PUP. Config NAT service location (instruct load balance on vBNG-CPU of CGN card), service instance group (binding the service location) and create NAT instance. Then config warm standby group on vBNG-PUP1~vBNG-PUP4. | | +| | 2 | Stimulus | Config the basic function of CGN, such as network segment, port block, backup mode, traffic steering policy based on ACL and NAT translation policy. The users on CGN cards of vBNG-PUP1~vBNG-PUP4 load balanced and normally access the Internet. | | +| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1. Record the CGN table of vBNG-PUP1. | | +| | 4 | Stimulus | Shutdown one of the CGN cards on vBNG-PUP1. | | +| | 5 | Stimulus | Check the user traffic and resource utilization such as vBNG-CPU utilization or memory utilization. There is expected result 1. | | +| | 6 | Stimulus | Check the CGN table on vBNG-PUP2~vBNG-PUP4. There is expected result 2. | | +| Expected results | Step | Type | Description | Result | +| | 1 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP4, the vBNG-CPU utilization increases in vBNG-PUP1. | | +| | 2 | Check | There is no change to the CGN table on vBNG-PUP2~vBNG-PUP4. | | +| | 3 | Check | There is no change of user entries on vBNG-PUP2~vBNG-PUP4, including the mapping relationship between public network address and private network address, as well as the corresponding port blocks. | | +| Notes | | | | | +| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | + + + +# 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.4-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d4e668942e77f263cb9c1d080314402337405f43 --- /dev/null +++ b/marked/Q/T-REC-Q.4-198811-I_PDF-E/raw.md @@ -0,0 +1,384 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.4** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**INTERNATIONAL AUTOMATIC AND +SEMI-AUTOMATIC WORKING** + +--- + +**AUTOMATIC SWITCHING FUNCTIONS FOR +USE IN NATIONAL NETWORKS** + +**ITU-T Recommendation Q.4** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation Q.4 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. + +## Recommendation Q.4 + +# AUTOMATIC SWITCHING FUNCTIONS FOR USE IN NATIONAL NETWORKS + +## 1 Preamble + +The CCITT, + +*considering* + +(1) that a large amount of switching equipment will be installed in the next few years, especially in areas of low subscriber density; + +(2) the continuous rapid development of new switching techniques results in different generations of equipment having to co-exist; + +(3) that some degree of compatibility in the installed switching equipment is required in the world-wide automatic network; + +(4) that the introduction of newly developed switching systems presents Administrations with an ever increasing number of engineering, staff training, maintenance and other operational considerations, + +*and also considering* + +(5) that Recommendations originally intended for international application only are increasingly being applied to national networks, or could be so applied; + +(6) that many current studies are aimed at producing Recommendations primarily applicable to national networks, + +*recommends* + +the following guidelines for use by Administrations establishing national switching standards or, if desired, for updating existing standards. Each Administration may select those guidelines it deems applicable to its own situation. + +## 2 Automatic switching functions for use in national networks + +Table 1/Q.4 lists the functional switching capabilities of an exchange which will, or may in some instances, according to the role of the exchange in a network, need to be technically specified in order that the Administration concerned can be assured that the exchange will satisfy existing and foreseen future needs of the network. For the required capabilities, references are given to CCITT texts which should be taken into account when decisions on national standards are taken; some make positive recommendations, others give guidelines or background information. Table 2/Q.4 provides full titles for those referenced texts, and for others applicable to national switching, in order to provide more specific information about the subject matter. + +Some of the functions listed are required in all types of exchanges. Others may or may not be, according to the role of the exchange, e.g. local, combined local/transit, transit, international, etc. + +It is not always necessary that a precise technical specification be given, e.g., in a tender specification, for each switching function. In some instances, it may be sufficient to state the requirements broadly, possibly including desired ranges of parameter values, and to invite a tenderer to make his own specific proposals for evaluation. + +## 3 Requirements for ISDN + +As Recommendations for the ISDN are being developed concurrently, it is difficult to reference them in this Recommendation. All Recommendations relevant to the ISDN will be published in a single volume at the end of this Study Period 1981-1984 (Fascicle III.5). + +## **4 Requirements other than automatic switching functions** + +The technical specifications of the required automatic switching functions of an exchange do not, in themselves, constitute a complete specification. Other aspects possibly needing to be covered, which are particular to an exchange or to a group of exchanges and not included within the scope of automatic switching functions are: + +- traffic (dimensioning and service performance); +- specifications dictated by the equipment environment (building constraints, power supplies, climatic conditions, etc.); +- installation, including testing, acceptance, post-acceptance technical support, etc.; +- training and documentation; +- support of system design and software, e.g., CCITT Recommendation Z.100 (SDL) series and CCITT Recommendation Z.200 (CHILL) series. + +## **5 Technical cooperation possibilities** + +The CCITT Recommendations already established so far do not themselves suffice to cover all the points of a specification dealing with the functions to be performed by switching equipment. It is unavoidable, if national standards are to match the requirements and circumstances of a particular network, that the responsible Administration itself exercise a number of choices. + +An Administration seeking advice or guidance beyond that indicated in CCITT texts may, by approaching the ITU Secretariat, obtain information on the standards adopted by other Administrations. + +## **6 Definition of requirements in terms of services and facilities** + +6.1 Fundamental decisions as to range of service(s) and facilities to be provided must be made by the Administration. Descriptions and other information on the various services normally provided by a switching system may be found as indicated in the following: + +- types of services (GAS 6, Chapter II, § 3; Chapter III, § 3.2), +- basic services (GAS 6, Chapter IV, § 1.2), +- supplementary services (GAS 6, Chapter IV, § 1.4); Recommendations E.130, E.132, E.151; Supplement No. 1 to Series E Recommendations. + +6.2 A list of possible telephony subscriber services and facilities has been extracted from the GAS 6 Handbook, Chapter IX, § 1.3.2 and is shown in Annex A. + +TABLE 1/Q.4 + +## **CCITT texts (Recommendations and GAS Handbooks) relevant to the technical specification of automatic switching functions of exchanges in national networks** + +| Item | Reference | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| A. Switching | | +| Type of switch: analogue (2- or 4-wire)/digital, space or time division | GAS 6 II 1, VI 1.1
GAS 3 III, Annex 1
Recs. Q.501, Q.511 | +| Type of control: distributed/centralized | GAS 6 VI 1.2 | +| Subscriber classification | GAS 6 VI 1.2.1 | +| B. Routing and selection | | +| Classification of exchange inlets and outlets: according to types of inter-exchange circuits to be connected: taking into account the line, inter-register, etc., signalling arrangements and the transmission, operating, testing, network management, etc., requirements | GAS 6 IV 5.6-7
VI 1.4.1 and 4
Recs. E.543
Q.7, Q.48, Q.49, Q.108, Q.110,
Q.251-Q.300, Q.310-Q.331, Q.400-Q.480,
Q.501-Q.507, Q.511-Q.517 | +| Number analysis functions: required capacity and depth of analysis for routing, determination of number length, barring, digit insertion/deletion, charging, echo control, etc. | GAS 6 IV 6, VI 1.4.6
Recs. E.160, E.161, E.163
Q.103, Q.105, Q.106, Q.107, Q.107 bis,
Q.115 | +| Choice of outgoing circuit: search procedure, dual seizures, alternative routing, repeat attempts, etc. | GAS 6 VI 1.4.2, 3 and 5
Recs. E.170, E.171
Q.12, Q.263 | +| Network management functions: circuit group denial, alternative routing cancellation, exchange load control, etc. | GAS 6 VI 1.4.7
Recs. E.170, E.410, E.411, E.412, E.413
Q.506, Q.516 | +| C. Charging | | +| Methods: local, long-distance, international, non-chargeable, payphone, etc., calls | GAS 6 IV 7.1-2, VI 1.5.1
Recs. E.230-E.232 | +| Charge determination: principles and parameters | GAS 6 IV 7.3, VI 1.5.2 | +| D. Transmission characteristics | | +| Interfaces: specification of the transmission characteristics of the interfaces, or the identification of the standard interfaces, at which the exchange is to interconnect with external facilities and systems | GAS 3 III
Recs. G.703, G.704, G.705, G.731-G.739,
G.741-G.746,
Q.502, Q.512 | +| Exchange transmission performance: Limits for the levels of transmission impairments attributable to the exchange and for characteristics affecting performance, taking account of all possible types of connection through the exchange | GAS 6 VI 1.8
Recs. G.121, G.122, G.123
Q.45, Q.507, Q.517 | +| E. Synchronization and timing | Recs. G.811, G.822
Q.502, Q.503, Q.512, Q.513 | +| F. Tones and recorded announcements | | +| Scope and applications; tones; announcements | GAS 6 VI 1.7
Recs. E.180 (Q.35), E.181 (Q.36), E.182
Supplement No. 2 to
Series E Recommendations
Rec. Q.24 | + +TABLE 1/Q.4 (cont.) + +| Item | Reference | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| G. Subscriber line characteristics | | +| 1. Analogue subscriber line | | +| Subscriber line standards: limits for loop resistance, loop insulation, overall line attenuation, etc. | GAS 2 V 3.2, 3.3
GAS 6 VI 1.3.1
GAS 3 II 3.1
Recs. G.120-G.123 | +| Subscriber line signals.. supervision address information, ringing, metering, tones, etc. | GAS 2 V 6.2
GAS 6 IV 8, VI 1.3.2
Recs. E. 131
Q.16, Q.23, Q.35 (E.180), Q.118 | +| 2. Digital subscriber line | | +| Exchange interfaces signalling for digital access | Recs. I.412
Q.512, Q.920, Q.921, Q.930, Q.931 | +| H. Inter-exchange signalling | | +| Specification of required exchange functions by identification of existing and planned inter-exchange signalling arrangements
Signalling philosophies and types of signalling | GAS 6 II 2, IV 8, VI 1.6
GAS 3 II 3.2
Recs. Q.7, Q.21
Supplement No. 3 to
Series Q Recommendations
Recs. Q.101-Q.103, Q.105-Q.118 bis ,
Q.251-Q.300, Q.310-Q.331, Q.400-Q.490,
Q.701-Q.795 | +| Signalling system specifications (channel associated and common channel, as appropriate) | | +| Interworking of signalling systems | Recs. Q.601 -Q.685 | +| I. Operation | | +| The specification of exchange features designed to facilitate the operation of the exchange with respect to the administrations of: | GAS 6 IV 7.4-7, 9.1-2
VI 1.5.3-4, 1.9 | +| - subscribers | Recs. E.500 | +| - routing | Q.505, Q.506, Q.515, Q.516 | +| - traffic | Z.331-Z.333 | +| - tariffs and charging | | +| - recording and billing | | +| - system control | | +| taking into account remote control possibilities | | +| J. Maintenance | | +| The specification, with respect to maintenance, of: | GAS 6 IV 9.1, 9.3, VI 1.10
Recs. G.231 | +| - subscriber lines | M.565 | +| - inter-exchange circuits | O.22 (Q.49) | +| - switching network | Q.506, Q.516 | +| - control system | Z.301, Z.331-Z.333 | +| the specification of testing and maintenance features, taking into account the objectives of: | | +| - minimization of the fault rate | | +| - simplification of maintenance activities | | +| - adequate equipment repair facilities | | +| - maximization of immunity to failures | | +| - optimizing maintenance centralization | | +| L. Input/output devices for operation and maintenance | GAS 6 VI 1.11
Recs. E.220, E.221
Z.301-Z.302, Z.311-Z.317, Z.321-Z.323 | + +TABLE 2/Q.4 + +### **Titles of CCITT texts (Recommendations and GAS Handbooks) relevant to national switching applications** + +CCITT Manual *Local telephone networks*, ITU, Geneva, 1968 (Gas 2 Handbook). + +CCITT Manual *Transmission planning of switched telephone networks*, ITU, Geneva, 1976 (Gas 3 Handbook). + +CCITT Manual *Economic and technical aspects of the choice of telephone switching systems*, ITU, Geneva, 1981 (GAS 6 Handbook). + +CCITT Manual *Economic and technical aspects of the transition from analogue to digital telecommunication networks*, ITU, Geneva, 1984 (GAS 9 Handbook). + +CCITT Rec. E.130 *Choice of the most useful and desirable supplementary telephone services*. + +CCITT Rec. E.131 *Subscriber control procedures for supplementary services*. + +CCITT Rec. E.132 *Standardization of elements of control procedures for supplementary telephone services*. + +CCITT Rec. E.151 *Conference calls*. + +CCITT Rec. E.160 *Definitions relating to national and international numbering plans*. + +CCITT Rec. E.161 *Arrangement of figures, letters and symbols on rotary dials and pushbutton telephone sets*. + +CCITT Rec. E.163 *Numbering plan for the international telephone service*. + +CCITT Rec. E.170 *Overflow - alternative routing - rerouting - automatic repeat attempt*. + +CCITT Rec. E.171 *International routing plan*. + +CCITT Rec. E.180 *Characteristics of the dial tone, ringing tone, busy tone, congestion tone, special information tone and warning tone*. + +CCITT Rec. E.181 *Customer recognition of foreign tones*. + +CCITT Rec. E.182 *Application of tones and recorded announcements in telephone services*. + +CCITT Rec. E.211 *Numbering and dialling procedures for VHF/UHF and maritime mobile satellite services*. + +CCITT Rec. E.220 *Ergonomic aspects of visual display terminals*. + +CCITT Rec. E.221 *Human interface to visual display terminals*. + +CCITT Recs. E.230-E.232 *Charging (determination of collection charges) in the international telephone service*. + +CCITT Rec. E.500 *Measurement and recording of traffic*. + +CCITT Rec. E.521 *Calculation of the number of circuits in a group carrying overflow traffic*. + +CCITT Rec. E.543 *Grades of service in analogue/digital international telephone exchanges*. + +CCITT Rec. E.410, E.411, E.412 and E.413 *Network management*. + +CCITT Series E. Recommendations Supplement No. 1 *List of possible supplementary telephone services which may be offered to subscribers*. + +CCITT Series E. Recommendations Supplement No. 2 *Various tones used in national networks*. + +CCITT Recs. G.120-G. 123 *General characteristics of national systems forming part of international connections.* + +CCITT Rec. G.121 *Corrected reference equivalents (CREs) of national systems.* + +CCITT Rec. G.122 *Influence of national networks on stability and echo losses in national systems.* + +CCITT Rec. G.123 *Circuit noise in national networks.* + +CCITT Rec. G.231 (2) *Use of standard components in transmission equipment.* + +CCITT Rec. G.703 *General aspects of interfaces.* + +CCITT Rec. G.704 *Functional characteristics of interfaces associated with network nodes.* + +CCITT Rec. G.705 *Characteristics required to terminate digital paths on a digital exchange.* + +CCITT Recs. G.731-G.739 *Principal characteristics of primary multiplex equipment.* + +CCITT Recs. G.741-G.746 *Principal characteristics of second order multiplex equipments.* + +CCITT Rec. G.811 *Performance of clocks suitable for plesiochronous operation of international digital links.* + +CCITT Rec. G.822 *Controlled slip rate objectives on an international digital connection.* + +CCITT Rec. I.412 *ISDN user-network interfaces-channel structures and access capabilities.* + +CCITT Rec. M.565 *Access point for international telephone circuits.* + +CCITT Rec. O.22 *Specification for the CCITT automatic transmission measuring and signalling testing equipment ATME No. 2.* + +CCITT Rec. Q.7 *Signalling systems to be used for international automatic and semi-automatic telephone working* + +CCITT Rec. Q.12 *Overflow-alternative routing - rerouting - automatic repeat attempt.* + +CCITT Rec. Q.14 *Means to control the number of satellite links in an international telephone connection.* + +CCITT Rec. Q.15 *Nominal mean power during the busy hour.* + +CCITT Rec. Q.16 *Maximum permissible value for the absolute power level of a signalling pulse.* + +CCITT Rec. Q.21 *Systems recommended for out-band signalling.* + +CCITT Rec. Q.23 *Technical features of push-button telephone sets.* + +CCITT Rec. Q.24 *Multi-frequency push-button signal reception.* + +CCITT Rec. Q.33 *Protection against the effects of faulty transmission on groups of circuits.* + +CCITT Rec. Q.35 *Characteristics of the dial tone, ringing tone, busy tone, congestion tone, special information tone and warning tone.* + +CCITT Rec. Q.45 *Transmission characteristics of an international exchange.* + +CCITT Rec. Q.48 *Demand assignment signalling systems.* + +CCITT Rec. Q.49 *Specification for the CCITT automatic transmission measuring and signalling testing equipment ATME No. 2.* + +CCITT Recs. Q.101-Q.103, Q.105-Q.118 bis *Clauses applicable to CCITT standard systems.* + +CCITT Rec. Q.103 *Numbering used.* + +CCITT Rec. Q.105 *National (significant) number.* + +CCITT Rec. Q.106 *The sending-finished signal* + +CCITT Rec. Q.107 *Standard sending sequence of forward address information.* + +CCITT Rec. Q.107 bis *Analysis of forward address information for routing.* + +CCITT Rec. Q.108 *One-way or both-way operation of international circuits.* + +CCITT Rec. Q.110 *General aspects of the utilization of standardized CCITT signalling systems on PCM links.* + +CCITT Rec. Q.115 *Control of echo suppressors.* + +CCITT Recs. Q.118 *Special release arrangements.* + +CCITT Recs. Q.251-Q.300 *Specifications of Signalling System No. 6.* + +CCITT Rec. Q.263 *Double seizing with both-way operation.* + +CCITT Recs. Q.310-Q.331 *Specifications of Signalling System R1.* + +CCITT Recs. Q.400-Q.490 *Specifications of Signalling System R2.* + +CCITT Recs. Q.500-Q.554 *Digital local, transit, combined and international exchanges in integrated digital networks and mixed analogue-digital networks.* + +CCITT Recs. Q.601-Q.685 *Interworking of signalling systems.* + +CCITT Recs. Q.701-Q.795 *Specifications of Signalling System No. 7.* + +CCITT Rec. Q.920 *ISDN user-network interface data link layer - General aspects.* + +CCITT Rec. Q.921 *ISDN user-network interface data link layer specification.* + +CCITT Rec. Q.930 *ISDN user-network interface layer 3 - General aspects.* + +CCITT Rec. Q.931 *ISDN user-network interface layer 3 specification for basic call control* + +CCITT Series Q. Recommendations Supplement No. 3 *Information received on national voice-frequency signalling systems.* + +CCITT Rec. Z.100 Series *Functional specification and description language (SDL).* + +CCITT Rec. Z.200 Series *CCITT high level language (CHILL).* + +CCITT Rec. Z.300 Series *Man-machine language (MML).* + +CCITT Recs. Z.301-Z.302 *General principles.* + +CCITT Rec. Z.301 *Introduction to the CCITT man-machine language.* + +CCITT Recs. Z.311-Z.317 *Basic syntax and dialogue procedures.* + +CCITT Recs. Z.321-Z.323 *Extended MML for visual display terminals.* + +CCITT Recs. Z.331-Z.333 *Specification of man-machine interface.* + +## ANNEX A + +(to Recommendation Q.4) + +### **List of possible subscriber services and facilities** + +#### Subscriber services + +#### *Basic services* + +- subscriber dialled local, long distance, and international calling with automatic charging +- PBX line hunting, night service, and direct dialling-in +- payphone +- access to operators for assistance and information +- access to community services (police, fire brigade, etc.) +- access to recorded announcements +- call barring +- malicious call trace +- interception of calls +- absent subscriber +- line observation + +#### *Supplementary services* + +- abbreviated dialling +- alarm call +- hot line +- outgoing service restriction +- call diversion +- call waiting +- do not disturb +- call completion to busy subscribers +- switching-in not permitted +- call charge indicator at subscriber's premises +- immediate call charge announcement +- priority line +- two party line +- multiparty line +- multifrequency push-button (MFPB) dialling +- mobile subscriber +- conference service +- Centrex services +- other services \ No newline at end of file diff --git a/marked/Q/T-REC-Q.4001.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4001.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a308271fb239928318c461337c31936dd84fe604 --- /dev/null +++ b/marked/Q/T-REC-Q.4001.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.4010.1-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4010.1-201608-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..52f4934bd91bd8371b70738d632bdcb36f6b8825 --- /dev/null +++ b/marked/Q/T-REC-Q.4010.1-201608-I_PDF-E/raw.md @@ -0,0 +1,491 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4010.1** + +(08/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**Message waiting indication using IP multimedia +core network subsystem – Part 1: Protocol +implementation conformance statement** + +Recommendation ITU-T Q.4010.1 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with "ITU" in a larger, bold font above it. + +ITU logo + +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.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.4010.1 + +## Message waiting indication using IP multimedia core network subsystem – Part 1: Protocol implementation conformance statement + +## Summary + +Recommendation ITU-T Q.4010.1 v.1 (2016) provides the testing requirements for message waiting indication (MWI) using IP multimedia (IM) core network (CN) subsystem – Part 1: Protocol implementation conformance statement (PICS) (based on Recommendation ITU-T Q.3626 v.1). + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4010.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.4010.1 v.1 | 2016-08-29 | 11 | 11.1002/1000/13001 | + +## Keywords + +IMS, IP multimedia subsystem, message waiting indication, MWI, testing, test suite structure and test purposes, TSS&TP + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Guidance for completing the ICS proforma ..... | 2 | +| 6.1 General overview of ICS proforma ..... | 2 | +| 6.2 Identification of the implementation ..... | 4 | +| 6.3 Identification of the MWI specification ..... | 6 | +| 6.4 Global statement of conformance..... | 6 | +| 6.5 Roles ..... | 6 | +| 6.6 User role ..... | 6 | +| 6.7 Network role..... | 7 | + + + +## Recommendation ITU-T Q.4010.1 + +## Message waiting indication using IP multimedia core network subsystem – Part 1: Protocol implementation conformance statement + +# 1 Scope + +This Recommendation is part 1 of a multi-part deliverable covering message waiting indication (MWI) using IP multimedia (IM) core network (CN) subsystem – Part 1: Protocol implementation conformance statement (PICS), as identified below: + +**Part 1: "Protocol implementation conformance statement (PICS)";** + +Part 2: "Test suite structure and test purposes; Network side"; + +Part 3: "Test suite structure and test purposes (TSS&TP); User side". + +# 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.3626 v.1] Recommendation ITU-T Q.3626 v.1 (2016), *Message waiting indication using IP multimedia core network subsystem – Protocol specification*. +- [IETF RFC 3842] IETF RFC 3842 (2004), *A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)*. +- [ITU-T X.290] Recommendation ITU-T X.290 (1994), *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 + +For the purposes of this Recommendation, the terms and definitions given in [ITU-T Q.3626 v.1], [ITU-T X.290], [ITU-T X.296] and the following apply: + +**3.1.1 PICS proforma:** Document, in the form of a questionnaire, which when completed for an implementation or system becomes a PICS. + +**3.1.2 Protocol ICS (PICS):** ICS for an implementation or system claimed to conform to a given protocol specification. + +NOTE – This may contain additional information. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------------| +| ICS | Implementation Conformance Statement | +| IUT | Implementation Under Test | +| MA | Message Account | +| MIME | Multipurpose Internet Mail Extensions | +| MNUA | MWI Notifier User Agent | +| MSUA | MWI Subscriber User Agent | +| MWI | Message Waiting Indication | +| PDU | Protocol Data Unit | +| PICS | Protocol Implementation Conformance Statement | +| SCS | System Conformance Statement | +| SUT | System Under Test | + +# **5 Conventions** + +None. + +# **6 Guidance for completing the ICS proforma** + +## **6.1 General overview of ICS proforma** + +### **6.1.1 Purposes and structure** + +The purpose of this protocol implementation conformance statement (PICS) proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in [ITU-T Q.3626 v.1] may provide information about the implementation in a standardized manner. + +The implementation conformance statement (ICS) proforma is subdivided into clauses for the following categories of information: + +- guidance for completing the ICS proforma; +- identification of the implementation; +- identification of the ; +- global statement of conformance; +- roles; +- user role; +- network role. + +### **6.1.2 Abbreviations and conventions** + +The PICS proforma contained in this Recommendation 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. +- x prohibited (excluded) – there is a requirement not to use this capability in the given context. +- o.i qualified optional – for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. +- ci conditional – the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression which is defined immediately following the table. + +##### Reference column + +The reference column makes reference to [ITU-T Q.3626 v.1], except where explicitly stated otherwise. + +#### Support column + +The support column shall be filled in by the supplier of the implementation. The following common notations, defined in [ITU-T X.296], are used for the support column: + +- Y or y supported by the implementation. +- N or n not supported by the implementation. +- N/A, n/a or no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). + +If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able to answer that a capability is supported for one profile and not supported for another. In that case, the supplier shall enter the unique reference to a conditional expression, preceded by "?:" (e.g., ?3). This expression shall be given in the space for comments provided at the bottom of the table. It uses predicates defined in the system conformance statement (SCS), each of which refers to a single profile and which takes the value TRUE if and only if that profile is to be used. + +EXAMPLE 1: ?3: IF prof1 THEN Y ELSE N + +*In case of protocol, the following text should be added:* + +NOTE – As stated in [ITU-T X.296], support for a received protocol data unit (PDU) requires the ability to parse all valid parameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter is non-conformant. Support for a parameter on a PDU means that the semantics of that parameter are supported. + +##### 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. + +### **6.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 6.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 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. + +## **6.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 PICS should be named as the contact person. + +### **6.2.1 Date of the statement** + +..... + +### **6.2.2 Implementation Under Test (IUT) identification** + +IUT name: + +..... + +..... + +IUT version: + +..... + +### **6.2.3 System Under Test (SUT) identification** + +SUT name: + +..... + +..... + +Hardware configuration: + +..... + +..... + +..... + +Operating system: + +..... + +### **6.2.4 Product supplier** + +Name: + +..... + +Address: + +..... + +..... + +..... + +Telephone number: + +..... + +Facsimile number: + +..... + +E-mail address: + +..... + +Additional information: + +..... + +..... + +..... + +### **6.2.5 Client (if different from product supplier)** + +Name: + +..... + +Address: + +..... + +..... + +..... + +Telephone number: + +..... + +Facsimile number: + +..... + +E-mail address: + +..... + +Additional information: + +..... + +..... + +..... + +### 6.2.6 PICS contact person + +(A person to contact if there are any queries concerning the content of the ICS) + +Name: + +Telephone number: + +Facsimile number: + +E-mail address: + +Additional information: + +## 6.3 Identification of the MWI specification + +This PICS proforma applies to the following standard: [ITU-T Q.3626 v.1]. + +## 6.4 Global statement of conformance + +Are all mandatory capabilities implemented? (Yes/No)..... + +NOTE – Answering "No" to this question indicates non-conformance to the message waiting indication (MWI) 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. + +## 6.5 Roles + +**Table 6-1 – Roles** + +| Item | Role | Reference | Status | Support | +|------|----------------------------------|------------------------------------|--------|---------| +| 1 | MWI subscriber user agent (MSUA) | Clause 4.4.1 of [ITU-T Q.3626 v.1] | o | | +| 2 | MWI notifier user agent (MNUA) | Clause 4.4.2 of [ITU-T Q.3626 v.1] | m | | +| 3 | Message account (MA) | Clause 4.4.3 of [ITU-T Q.3626 v.1] | m | | + +Comments: + +## 6.6 User role + +This clause contains the PICS proforma tables related to the user role. They need to be completed only for user equipment implementations: + +Prerequisite: 6.1/1 -- user role + +### 6.6.1 Major capabilities + +**Table 6-2 – MWI subscriber user agent capabilities** + +| Item | Item description | Reference | Status | Support | +|------|---------------------------------------------------------------------------------------------|--------------------------------------|--------|---------| +| 1 | The user equipment is able to address the message account using the public service identity | Clause 4.4.3.2 of [ITU-T Q.3626 v.1] | o.1 | | +| 2 | The user equipment is able to address the message account using the public user identity | Clause 4.4.3.2 of [ITU-T Q.3626 v.1] | o.1 | | + +o.1: It is mandatory to support at least one of these items. + +Comments: + +## 6.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: 6.1/2 network role + +**Table 6.3 – MWI Notifier User Agent (MNUA) capabilities** + +| Item | Item description | Reference | Status | Support | +|------|---------------------------------------------------------------------------------------------------|-------------------------------|--------|---------| +| 1 | The MNUA includes the message account in the MIME body to identify the served user | Clause 3.5 of [IETF RFC 3842] | o | | +| 2 | The MNUA includes the message summary line in the MIME body to identify the served user | Clause 3.5 of [IETF RFC 3842] | o | | +| 3 | The MNUA append message headers, which further describe newly added messages as "opt-msg-headers" | Clause 3.5 of [IETF RFC 3842] | o | | + + + + + +## **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.4011.2-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4011.2-201608-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d848fb44b4c22bf227b2774bc666c11c1507b6e4 --- /dev/null +++ b/marked/Q/T-REC-Q.4011.2-201608-I_PDF-E/raw.md @@ -0,0 +1,1397 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4011.2** + +(08/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**Closed user group using IP multimedia core +network subsystem; Conformance test +specification – Part 2: Test suite structure and +test purposes; Network side** + +Recommendation ITU-T Q.4011.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.4011.2 + +## Closed user group using IP multimedia core network subsystem; Conformance test specification – Part 2: Test suite structure and test purposes; Network side + +## Summary + +Recommendation ITU-T Q.4011.2 provides the testing requirements for the supplementary service "Closed user group (CUG) using IP multimedia (IM) core network (CN) subsystem; Conformance Test Specification – Part 2: Test suite structure and test purposes (TSS&TP); Network side" (based on Recommendation ITU-T Q.3627 v.1). + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4011.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.4011.2 v.1 | 2016-08-29 | 11 | 11.1002/1000/13005 | + +## Keywords + +IMS, IP multimedia subsystem , malicious communication identification, MCID, testing, test suite structure and test purposes, TSS&TP. + +--- + +\* 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 | +| 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 Test suite structure..... | 3 | +| 7 Test purposes ..... | 4 | +| 7.1 Introduction ..... | 4 | +| 7.2 Test purposes for closed user group ..... | 5 | +| 7.3 Interaction with other services..... | 49 | + + + +## Recommendation ITU-T Q.4011.2 + +## Closed user group using IP multimedia core network subsystem; Conformance test specification – Part 2: Test suite structure and test purposes; Network side + +# 1 Scope + +This Recommendation is Part 2 of a multi-part deliverable covering closed user group (CUG) using IP multimedia (IM) core network (CN) subsystem; Conformance test specification, as identified below: + +Part 1: "Protocol implementation conformance statement (PICS)"; + +**Part 2: "Test suite structure and test purposes (TSS&TP); Network side";** + +Part 3: "Test suite structure and test purposes (TSS&TP); User side". + +# 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.3627 v.1] Recommendation ITU-T Q.3627 v.1 (2016): *Closed user group using IP multimedia core network subsystem – Protocol Specification.* + +[ITU-T Q.4011.1 v.1] Recommendation ITU-T Q.4011.1 v.1 (2016): *Closed user group using IP multimedia core network subsystem; Conformance test specification – Part 1: Protocol implementation conformance statement.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------------| +| AS | Application Server | +| CD | Communication Deflection | +| CDIV | Communication Diversion service | +| CFB | Communication Forwarding on Busy | +| CFNL | Communication Forwarding on Not Logged-in | +| CFNR | Communication Forwarding on no Reply | + +CFU Communication Forwarding Unconditional +CONF Conference calling +CSCF Call Session Control Function +CUG Closed User Group +ECT Explicit Communication Transfer +IA Incoming Access +ICB Incoming Communication Barring within a CUG +IMS IP Multimedia Subsystem +IP Internet Protocol +ISC Reference point between Serving CSCF and Application Server +IUT Implementation Under Test +NNI Network-to-Network Interface +OA Outgoing Access +OAE Outgoing Access, explicit request required +OAI Outgoing Access, implicit outgoing access for all communications +OCB Outgoing Communication Barring within a CUG +PIXIT Protocol Implementation extra Information for Testing +SIP Session Initiation Protocol +SUT System Under Test +TP Test Purposes +TSS Test Suite Structure +UE User Equipment + +# **5 Conventions** + +None. + +# 6 Test suite structure + +**Table 6-1 – Test suite structure** + +| | | | | +|-----|----------------|------------------------------|-------------| +| CUG | originating_AS | CUG without preference | CUG_N01_xxx | +| | | CUG without preference + OAE | CUG_N02_xxx | +| | | CUG without preference + OAI | CUG_N03_xxx | +| | | CUG with preference | CUG_N04_xxx | +| | | CUG with preference + OAE | CUG_N05_xxx | +| | | CUG with preference + OAI | CUG_N06_xxx | +| | | No CUG | CUG_N07_xxx | +| | | | | +| | terminating_AS | CUG with OA not allowed | CUG_N08_xxx | +| | | CUG with OA allowed | CUG_N09_xxx | +| | | No CUG | CUG_N10_xxx | +| | Services | | | +| | | CONF | CUG_N11_xxx | +| | | CDIV | CUG_N12_xxx | +| | | ECT | CUG_N13_xxx | + +### 6.1.1 Testing of the application server + +The application server (AS) entity is responsible for performing and managing services. The reference point between serving call session control function (CSCF) and application server (ISC) interface is the appropriate access point for testing, see Figure 6.1.1-1. + +![Diagram showing the applicable interface to test AS functionalities. A central green box labeled 'Application server' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system' via ISC interfaces.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +The diagram shows a central green rectangular block labeled "Application server" and "Implementation under test". To its left and right are cyan rectangular blocks labeled "Test system". Each "Test system" is connected to the central block via a horizontal line labeled "ISC" with a vertical tick mark on the line. + +Diagram showing the applicable interface to test AS functionalities. A central green box labeled 'Application server' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system' via ISC interfaces. + +Q.4011.2v1(16)\_F6.1.1-1 + +**Figure 6.1.1-1 – Applicable interface to test AS functionalities** + +If the ISC interface is not accessible it is also possible to perform the test of the AS using any network-to-network interface (NNI) (i.e., Mw, Mg, Mx) (see Figure 6.1.1-2). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible. + +![Diagram showing the applicable interfaces for tests using a (generic) NNI. A central green box labeled 'CSCF (and/or AS)' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system' via Mw, Mg, Mx interfaces.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +The diagram shows a central green rectangular block labeled "CSCF (and/or AS)" and "Implementation under test". To its left and right are cyan rectangular blocks labeled "Test system". Each "Test system" is connected to the central block via a horizontal line labeled "Mw, Mg, Mx" with a vertical tick mark on the line. + +Diagram showing the applicable interfaces for tests using a (generic) NNI. A central green box labeled 'CSCF (and/or AS)' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system' via Mw, Mg, Mx interfaces. + +Q.4011.2v1(16)\_F6.1.1-2 + +**Figure 6.1.1-2 – Applicable interfaces for tests using a (generic) NNI** + +# 7 Test purposes + +## 7.1 Introduction + +For each test requirement a test purpose (TP) is defined. + +### 7.1.1 TP naming convention + +Test purposes (TPs) are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see Table 1). + +**Table 1 – TP identifier naming convention scheme** + +| | | | +|-------------------------------------|--------------------------|-------------------------------------------------------------| +| Identifier: __ | | | +| | = supplementary service: | e.g. "CUG" | +| | = type of IUT: | U            User equipment
N            Network entity | +| | = group | 2 digit field representing group reference according to TSS | +| | = sequential number | (001-999) | + +### 7.1.2 Test strategy + +As the base standard [ITU-T Q.3627 v.1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification [ITU-T Q.4011.1 v.1]. The criteria applied include the following: + +- Whether or not a test case can be built from the TP is not considered. + +### 7.2 Test purposes for closed user group + +#### 7.2.1 Actions at the AS of the originating user + +##### 7.2.1.1 CUG without preference + +| | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------| +| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_001 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/1 [ITU-T Q.4011.1 v.1] | | | | | | | | | | +| Test purpose
CUG without preference: INVITE with CUG index, successful.
Ensure that the system under test (SUT) on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]



INVITE2:
Content-Disposition: ...;handling=required

[PIXIT]
[related to registered CUG index]
11
| | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 ➔
➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | | | ➔ | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | | +| INVITE1 | ➔ | | | | | | | | | | | | +| | ➔ | INVITE2 | | | | | | | | | | | + +Rec. ITU-T Q.4011.2 (08/2016) 5 + +| | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_002 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG without preference + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring (OCB). | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
603 Decline ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 603 Decline | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG without preference: INVITE with unallocated CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


FALSE
[unregistered CUG]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +6         **Rec. ITU-T Q.4011.2 (08/2016)** + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|-----------| +| CUG/originating_AS/CUG without preference | CUG_N01_004 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG without preference: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG index]



INVITE2:
Content-Disposition: ...;handling=required

[registered CUG index]
[related to registered CUG index]
11
| | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 ➔ ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | ➔ INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | | + +| | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG without preference +OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[registered CUG index]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
603 Decline ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 603 Decline | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_006 | CUG reference
clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG without preference: INVITE with unallocated CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[unregistered CUG]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +8         **Rec. ITU-T Q.4011.2 (08/2016)** + +| TSS | TP | CUG reference | Selection expression | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------| +| CUG/originating_AS/CUG without preference | CUG_N01_007 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG without preference: INVITE without CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
rejects the INVITE request by sending a 403 Forbidden due to missing CUGindex. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | +| SIP header values:
INVITE:


FALSE

| | | | +| Comments:
Test equipment (Gm) | | | | +| INVITE | AS | | | +| 403 Forbidden | ← | | | +| ACK | → | | | + +| TSS | TP | CUG reference | Selection expression | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------| +| CUG/originating_AS/CUG without preference | CUG_N01_008 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG without preference: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 403 Forbidden due to missing CUGindex. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | +| SIP header values:
INVITE:


TRUE

| | | | +| Comments:
Test equipment (Gm) | | | | +| INVITE | AS | | | +| 403 Forbidden | ← | | | +| ACK | → | | | + +| | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG without preference | | TP
CUG_N01_009 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/1 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG without preference: INVITE for non-CUG communication, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden due to missing cug XML element. | | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:
No xml element | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | + +### 7.2.1.2 CUG without preference + OAE + +| | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------| +| TSS
CUG/originating_AS/CUG without preference + OAE | | TP
CUG_N02_001 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | +| Test purpose
CUG without preference + OAE: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]



INVITE2:
Content-Disposition: ...;handling=required

[PIXIT]
[related to registered CUG index]
11
| | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 →
→ INVITE2
| | | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | | | → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | | | +| INVITE1 | → | | | | | | | | | | | | | +| | → | INVITE2 | | | | | | | | | | | | + +10 Rec. ITU-T Q.4011.2 (08/2016) + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_002 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/2 AND
PICS 4.7.1/10
[ITU-T Q.4011.111 v.1] | +| Test purpose
CUG without preference + OAE + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE:


FALSE
[registered CUG index]

| | | | +| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_003 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/2
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG without preference + OAE: INVITE with unallocated CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE:


FALSE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | +| Comments:
Test equipment (Gm) → AS
INVITE →
403 Forbidden ←
ACK → | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------| +| CUG/originating_AS/CUG without preference + OAE | CUG_N02_004 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG without preference + OAE: INVITE with CUG index and outgoingAccessRequest = true, successful non CUG communication.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG index]



INVITE2:

[PIXIT]
[related to registered CUG index]
10
| | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | → | INVITE2 | | | | | | | | + +| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------| +| Test purpose
CUG without preference + OAE + OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards the INVITE request containing no xml element cug. | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG index]



INVITE2:
No xml element | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 ➔                  ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔                  ➔ | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | ➔                  ➔ | INVITE2 | | | | | | | | + +| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--|--------|---|--|---------------|---|--|-----|---|--| +| Test purpose
CUG without preference + OAE: INVITE with unallocated CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE ➔
403 Forbidden ⬅
ACK ➔
| | | | Test equipment (Gm) | AS | | INVITE | ➔ | | 403 Forbidden | ⬅ | | ACK | ➔ | | +| Test equipment (Gm) | AS | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | +| 403 Forbidden | ⬅ | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | + +Rec. ITU-T Q.4011.2 (08/2016)     13 + +| TSS | TP | CUG reference | Selection expression | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------| +| CUG/originating_AS/CUG without preference + OAE | CUG_N02_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | +| Test purpose
CUG without preference + OAE: INVITE without CUG index, unsuccessful outgoing access not allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, rejects the INVITE request by sending a 403 Forbidden due to outgoing access not allowed. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE:


FALSE



403 Forbidden
Reason: ... | | | | +| Comments:
Test equipment (Gm) | | | | +| INVITE | AS | | | +| 403 Forbidden | ← | | | +| ACK | → | | | + +| TSS | TP | CUG reference | Selection expression | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------| +| CUG/originating_AS/CUG without preference + OAE | CUG_N02_008 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | +| Test purpose
CUG without preference + OAE: INVITE without CUG index and with outgoingAccessRequest = true, successful outgoing access allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, forwards the INVITE request containing no xml element cug due to outgoing access allowed. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE1:


TRUE



INVITE2:
No xml element | | | | +| Comments:
Test equipment (Gm) | | | | +| INVITE1 | AS | | Test equipment (ISC, Mw) | +| | → | | INVITE2 | + +| TSS | TP | CUG reference | Selection expression | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------| +| CUG/originating_AS/CUG without preference + OAE | CUG_N02_009 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/2
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG without preference + OAE: INVITE for non-CUG communication, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE:
No xml element

403 Forbidden
Reason: ... | | | | +| Comments:
Test equipment (ISC) | | | | +| INVITE | → | AS | | +| 403 Forbidden | ← | | | +| ACK | → | | | + +#### 7.2.1.3 CUG without preference + OAI + +| TSS | TP | CUG reference | Selection expression | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------| +| CUG/originating_AS/CUG without preference + OAI | CUG_N03_001 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/3
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG without preference + OAI: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]



INVITE2:

[PIXIT]
[related to registered CUG index]
10
| | | | +| Comments:
Test equipment (Gm) | | | | +| INVITE1 | → | AS | Test equipment (ISC, Mw) | +| | | → | INVITE2 | + +| | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------| +| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_002 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG without preference + OAI and OCB within CUG: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing no xml element cug. | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]



INVITE2:
No xml element | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 →                  → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | →                  → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | →                  → | INVITE2 | | | | | | | | + +| | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--------|---|---------------|---|-----|---| +| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | | | | +| Test purpose
CUG without preference + OAI: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | | | +| SIP header values:
INVITE:


FALSE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | AS | INVITE | → | 403 Forbidden | ← | ACK | → | +| Test equipment (Gm) | AS | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | +| ACK | → | | | | | | | | | | | + +16 Rec. ITU-T Q.4011.2 (08/2016) + + + +| | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------| +| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG without preference + OAI and OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing no xml element cug. | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG index]



INVITE2:
No xml element | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 →                  → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | →                  → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | →                  → | INVITE2 | | | | | | | | + +| | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--------|---|---------------|---|-----|---| +| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | | | | +| Test purpose
CUG without preference + OAI: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | AS | INVITE | → | 403 Forbidden | ← | ACK | → | +| Test equipment (Gm) | AS | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | +| ACK | → | | | | | | | | | | | + +18      Rec. ITU-T Q.4011.2 (08/2016) + +| | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|--------------|---------| +| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_007 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/3
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG without preference + OAI: INVITE without CUG index, successful outgoing access allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
forwards an INVITE request containing no xml element cug. | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE



INVITE2:
No xml element | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 →          → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | →          → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | →          → | INVITE2 | | | | | | | | + +| | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|--------------|---------| +| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_008 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/3
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG without preference + OAI: INVITE without CUG index and with outgoingAccessRequest = true, successful outgoing access allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
forwards an INVITE request containing no xml element cug. | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE



INVITE2:
No xml element | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 →          → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | →          → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | →          → | INVITE2 | | | | | | | | + +**Rec. ITU-T Q.4011.2 (08/2016)**      19 + + + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_002 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | +| SIP header values:
INVITE:


FALSE
[registered CUG index]

| | | | +| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_003 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | +| SIP header values:
INVITE:


FALSE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | +| Comments:
Test equipment (Gm) → AS
INVITE →
403 Forbidden ←
ACK → | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|-----------| +| CUG/originating_AS/CUG with preference | CUG_N04_004 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG with preference: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG index]



INVITE2:
Content-Disposition: ...;handling=required

[registered CUG index]
[related to registered CUG index]
11
| | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 ➔ ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | ➔ INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | | + +| | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/4 AND PICS 4.7.1/10 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with preference +OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[registered CUG index]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
603 Decline ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 603 Decline | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/4 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with preference: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +Rec. ITU-T Q.4011.2 (08/2016) 23 + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------| +| CUG/originating_AS/CUG with preference | CUG_N04_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG with preference: INVITE without CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE



INVITE2:
Content-Disposition: ...;handling=required

[registered CUG index]
[related to preferred CUG index]
11
| | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | → | INVITE2 | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_008 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 403 Forbidden due to outgoing access not allowed. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | +| SIP header values:
INVITE:


TRUE



403 Forbidden
Reason: ... | | | | +| Comments: | | | | +| Test equipment (Gm) | AS | | | +| INVITE | → | | | +| 403 Forbidden | ← | | | +| ACK | → | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_009 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference: INVITE for non-CUG communication, successful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | +| SIP header values:
INVITE1:
No xml element

INVITE2:
Content-Disposition: ...;handling=required

[registered CUG index]
[related to preferred CUG index]
11
| | | | +| Comments: | | | | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | +| INVITE1 | → | → | INVITE2 | + +Rec. ITU-T Q.4011.2 (08/2016) 25 + +#### 7.2.1.5 CUG with preference + OAE + +| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_001 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/5
[ITU-T Q.4011.1 v.1] | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------| +| Test purpose
CUG with preference + OAE: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]



INVITE2:
Content-Disposition: ...;handling=required

[PIXIT]
[related to registered CUG index]
11
| | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | → | INVITE2 | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_002 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/5 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference + OAE + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline to Outgoing Communication Barring. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE:


FALSE
[registered CUG index]

| | | | +| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_003 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/5
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference + OAE: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE:


FALSE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | +| Comments:
Test equipment (Gm) → AS
INVITE →
403 Forbidden ←
ACK → | | | | + + + +| | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------| +| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG with preference + OAE + OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing no xml element cug. | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG index]



INVITE2:
No xml element | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 →                  → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | →                  → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | →                  → | INVITE2 | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with preference + OAE: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[unregistered CUG]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | AS | | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | AS | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +Rec. ITU-T Q.4011.2 (08/2016) 29 + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------| +| CUG/originating_AS/CUG with preference + OAE | CUG_N05_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/5
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG with preference + OAE: INVITE without CUG index and with outgoingAccessRequest = false, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE



INVITE2:
Content-Disposition: ...;handling=required

[PIXIT]
[related to preferred CUG index]
11
| | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | → | INVITE2 | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------| +| CUG/originating_AS/CUG with preference + OAE | CUG_N05_008 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference + OAE: INVITE without CUG index and with outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
forwards an INVITE request containing no xml element cug. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE1:


TRUE


INVITE2:
No xml element | | | | +| Comments:
Test equipment (Gm) → AS → Test equipment (ISC, Mw)
INVITE1 → → INVITE2 | | | | + +| TSS | TP | CUG reference | Selection expression | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------| +| CUG/originating_AS/CUG with preference + OAE | CUG_N05_009 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference + OAE: INVITE for non-CUG communication, successful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug,
returns an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | +| SIP header values:
INVITE1:
No xml element
INVITE2:
Content-Disposition: ...;handling=required

[PIXIT]
[related to preferred CUG index]
11
| | | | +| Comments:
Test equipment (Gm) → AS → Test equipment (ISC, Mw)
INVITE1 → → INVITE2 | | | | + +**7.2.1.6 CUG with preference + OAI** + +| | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------| +| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_001 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/6 [ITU-T Q.4011.1 v.1] | | | | | | | | | | +| Test purpose
CUG with preference + OAI: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]



INVITE2:

[PIXIT]
[related to registered CUG index]
10
| | | | | | | | | | | | | +| Comments: | | | | | | | | | | | | | +|
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 ➠
➠ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➠ | | | ➠ | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | | +| INVITE1 | ➠ | | | | | | | | | | | | +| | ➠ | INVITE2 | | | | | | | | | | | + +32 Rec. ITU-T Q.4011.2 (08/2016) + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_002 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference + OAI and OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | +| SIP header values:
INVITE:


FALSE
[registered CUG index]

| | | | +| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with preference + OAI and OCB within CUG: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing no xml element cug is present | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]



INVITE2:
No xml element | | | | +| Comments:
Test equipment (Gm) → AS → INVITE2
INVITE1 → | | | | + +| | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_004 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/6 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with preference + OAI: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


FALSE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | | | | | | | | | | | | | +| Comments: | | | | | | | | | | | | | | | | +|
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +34 Rec. ITU-T Q.4011.2 (08/2016) + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------| +| CUG/originating_AS/CUG with preference + OAI | CUG_N06_005 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG with preference + OAI: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG]



INVITE2:

[PIXIT]
[related to registered CUG index]
10
| | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | → | INVITE2 | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|-------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|--------|---|--|-------------|---|--|-----|---|--| +| CUG/originating_AS/CUG with preference + OAI | CUG_N06_006 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/6 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with preference + OAI and OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE →
603 Decline ←
ACK →
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE | → | | 603 Decline | ← | | ACK | → | | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 603 Decline | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|-----------| +| CUG/originating_AS/CUG with preference + OAI | CUG_N06_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose
CUG with preference + OAI and OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing no xml element cug is present | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE
[registered CUG]



INVITE2:
No xml element | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 → → INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | → INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | +| INVITE1 | → | → INVITE2 | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_008 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/6 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with preference + OAI: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE
[unregistered CUG]



403 Forbidden
Reason: ... | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + + Rec. ITU-T Q.4011.2 (08/2016) 37 + +| | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------| +| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_009 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] | | | | | | | | | | +| Test purpose
CUG with preference + OAI: INVITE without CUG index and with outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | +| SIP header values:
INVITE1:


TRUE



INVITE2:

[PIXIT]
[related to preferred CUG index]
10
| | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 ➔
➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | | | ➔ | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | | +| INVITE1 | ➔ | | | | | | | | | | | | +| | ➔ | INVITE2 | | | | | | | | | | | + +| | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------|-----------|--------|---|-------------|---|-----|---| +| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_010 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | | +| Test purpose
CUG with preference + OAI and OCB: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE

| | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE ➔
603 Decline ⬅
ACK ➔
| | | | Test equipment (Gm) | AS | INVITE | ➔ | 603 Decline | ⬅ | ACK | ➔ | +| Test equipment (Gm) | AS | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | +| 603 Decline | ⬅ | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | + +38 Rec. ITU-T Q.4011.2 (08/2016) + + + +| | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/No CUG | TP
CUG_N07_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
No CUG: INVITE without CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
rejects the INVITE request by sending a 403 Forbidden. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has not subscribed to CUG | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


FALSE



403 Forbidden
Reason: ... | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE ➠
403 Forbidden ⬅
ACK ➠
| | | | Test equipment (Gm) | | AS | INVITE | ➠ | | 403 Forbidden | ⬅ | | ACK | ➠ | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | ➠ | | | | | | | | | | | | | | | +| 403 Forbidden | ⬅ | | | | | | | | | | | | | | | +| ACK | ➠ | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/originating_AS/No CUG | TP
CUG_N07_004 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
No CUG: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 403 Forbidden. | | | | | | | | | | | | | | | | +| Preconditions: Originating user has not subscribed to CUG | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:


TRUE



403 Forbidden
Reason: ... | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE ➠
403 Forbidden ⬅
ACK ➠
| | | | Test equipment (Gm) | | AS | INVITE | ➠ | | 403 Forbidden | ⬅ | | ACK | ➠ | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | +| INVITE | ➠ | | | | | | | | | | | | | | | +| 403 Forbidden | ⬅ | | | | | | | | | | | | | | | +| ACK | ➠ | | | | | | | | | | | | | | | + +40 Rec. ITU-T Q.4011.2 (08/2016) + +### 7.2.2 Actions at the AS of the terminating user + +#### 7.2.2.1 CUG with outgoing access (OA) not allowed + +| | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|----------------------------|---------|---|--|--|---|---------| +| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_001 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | +| Test purpose
CUG with IA not allowed: INVITE with interlock code matching registered CUG index and without outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
forwards an INVITE request containing no xml element cug. | | | | | | | | | | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-ICB)
Options for public identity in use:
Incoming access: not allowed | | | | | | | | | | | | | +| SIP header values:
INVITE1:
<cug>
    <networkIndicator>[PIXIT]</networkIndicator>
    <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode>
    <cugCommunicationIndicator>11</cugCommunicationIndicator>
</cug>

INVITE2:
No XML element | | | | | | | | | | | | | +| Comments:
Test equipment (ISC, Mw) AS Test equipment (Gm)
INVITE1 →
→ INVITE2
| | | | Test equipment (ISC, Mw) | AS | Test equipment (Gm) | INVITE1 | → | | | → | INVITE2 | +| Test equipment (ISC, Mw) | AS | Test equipment (Gm) | | | | | | | | | | | +| INVITE1 | → | | | | | | | | | | | | +| | → | INVITE2 | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|--|--------|---|--|-------------|---|--|-----|---|--| +| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_002 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with IA not allowed and ICB: INVITE with interlock code matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 603 Decline due to incoming calls barred. | | | | | | | | | | | | | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: ICB
Options for public identity in use:
Incoming access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:
<cug>
    <networkIndicator>[PIXIT]</networkIndicator>
    <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode>
    <cugCommunicationIndicator>11</cugCommunicationIndicator>
</cug> | | | | | | | | | | | | | | | | +| Comments:
Test equipment (ISC, Mw) AS
INVITE →
603 Decline ←
ACK →
| | | | Test equipment (ISC, Mw) | AS | | INVITE | → | | 603 Decline | ← | | ACK | → | | +| Test equipment (ISC, Mw) | AS | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 603 Decline | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +**Rec. ITU-T Q.4011.2 (08/2016)**      41 + +| | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|--|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_003 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with IA not allowed: INVITE with interlock code not matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode not related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 403 Forbidden due to not matched CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:

[PIXIT]
[not related to registered CUG index]
11
| | | | | | | | | | | | | | | | +| Comments:
Test equipment (ISC, Mw) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (ISC, Mw) | AS | | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (ISC, Mw) | AS | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|----------------------------|---------|---|--|--|---|---------| +| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_004 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | +| Test purpose
CUG with IA allowed: INVITE with interlock code matching registered CUG index and without outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
forwards an INVITE request containing no xml element cug. | | | | | | | | | | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-ICB)
Options for public identity in use:
Incoming access: allowed | | | | | | | | | | | | | +| SIP header values:
INVITE1:

[PIXIT]
[related to registered CUG index]
11


INVITE2:
No XML element | | | | | | | | | | | | | +| Comments:
Test equipment (ISC, Mw) AS Test equipment (Gm)
INVITE1 →
→ INVITE2
| | | | Test equipment (ISC, Mw) | AS | Test equipment (Gm) | INVITE1 | → | | | → | INVITE2 | +| Test equipment (ISC, Mw) | AS | Test equipment (Gm) | | | | | | | | | | | +| INVITE1 | → | | | | | | | | | | | | +| | → | INVITE2 | | | | | | | | | | | + +42 Rec. ITU-T Q.4011.2 (08/2016) + +| | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--| +| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_005 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with IA allowed and ICB: INVITE with interlock code matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 603 Decline due to incoming calls barred. | | | | | | | | | | | | | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: ICB
Options for public identity in use:
Incoming access: allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:

[PIXIT]
[related to registered CUG index]
11
| | | | | | | | | | | | | | | | +| Comments:
Test equipment (ISC, Mw) AS
INVITE →
603 Decline ←
ACK →
| | | | Test equipment (ISC, Mw) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | | +| Test equipment (ISC, Mw) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 603 Decline | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--| +| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_006 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with IA allowed: INVITE with interlock code not matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode not related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 403 Forbidden due to not matched CUG index. | | | | | | | | | | | | | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: allowed | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:

[PIXIT]
[not related to registered CUG index]
11
| | | | | | | | | | | | | | | | +| Comments:
Test equipment (ISC, Mw) AS
INVITE →
403 Forbidden ←
ACK →
| | | | Test equipment (ISC, Mw) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | | +| Test equipment (ISC, Mw) | | AS | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | + + Rec. ITU-T Q.4011.2 (08/2016) 43 + + + + + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------|---------------------------------------------------------------------| +| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_004 | CUG reference
Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with IA allowed: INVITE with interlock code matching registered CUG index and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-ICB)
Options for public identity in use:
Incoming access: allowed | | | | +| SIP header values:
INVITE1:

[PIXIT]
[related to registered CUG index]
10


INVITE2:
No XML element | | | | +| Comments:
Test equipment (ISC, Mw) → AS → Test equipment (Gm)
INVITE1 → INVITE2 | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------|---------------------------------------------------------------------| +| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_005 | CUG reference
Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with IA allowed and ICB: INVITE with interlock code matching registered CUG index and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: ICB
Options for public identity in use:
Incoming access: allowed | | | | +| SIP header values:
INVITE1:

[PIXIT]
[related to registered CUG index]
10


INVITE2:
No XML element | | | | +| Comments:
Test equipment (ISC, Mw) → AS → Test equipment (Gm)
INVITE1 → INVITE2 | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------| +| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_006 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with IA allowed: INVITE with interlock code not matching registered CUG index and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode not related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: allowed | | | | +| SIP header values:
INVITE1:

[PIXIT]
[not related to registered CUG index]
10


INVITE2:
No XML element | | | | +| Comments:
Test equipment (ISC, Mw)                                  AS                                  Test equipment (Gm)
INVITE1                                                  →                                  →                                  INVITE2 | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------| +| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_007 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | +| Test purpose
No CUG: INVITE with interlock code and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | | +| Preconditions: Terminating user has not subscribed to CUG | | | | +| SIP header values:
INVITE1:

[PIXIT]
[related to any CUG index]
10


INVITE2:
No XML element | | | | +| Comments:
Test equipment (ISC, Mw)                                  AS                                  Test equipment (Gm)
INVITE1                                                  →                                  →                                  INVITE2 | | | | + +Rec. ITU-T Q.4011.2 (08/2016)      47 + +#### 7.2.2.3 No CUG + +| TSS | TP | CUG reference | Selection expression | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------|--------------------------------------| +| CUG/ terminating _AS/No CUG | CUG_N10_001 | Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with IA not allowed: INVITE without xml element cug, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden. | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed | | | | +| SIP header values:
INVITE:
No xml element | | | | +| Comments: | | | | +| Test equipment (ISC) | AS | | | +| INVITE | → | | | +| 403 Forbidden | ← | | | +| ACK | → | | | + +| TSS | TP | CUG reference | Selection expression | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------|--------------------------------------| +| CUG/ terminating _AS/No CUG | CUG_N10_002 | Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with IA allowed: INVITE without xml element cug, successful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, forwards an INVITE request containing no xml element cug. | | | | +| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: allowed | | | | +| SIP header values:
INVITE1:
No xml element

INVITE2:
No XML element | | | | +| Comments: | | | | +| Test equipment (ISC, Mw) | AS | | Test equipment (Gm) | +| INVITE1 | → | | → INVITE2 | + +## 7.3 Interaction with other services + +### 7.3.1 Conference calling (CONF) + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|---------------------------------------------------------------------| +| TSS
CUG/Services/CONF | TP
CUG_N11_001 | CUG reference
Clause 4.6.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/7
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with OA not allowed: First added conferee join the conference, successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the conference focus allows to join the created conference as the first conferee. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | +| SIP header values:
INVITE:
Request Line


FALSE
[registered CUG index]

| | | | +| Comments:
Test equipment (Gm) AS
A conference is already created
INVITE →
200 OK ← | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|---------------------------------------------------------------------| +| TSS
CUG/Services/CONF | TP
CUG_N11_002 | CUG reference
Clause 4.6.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/7
[ITU-T Q.4011.1 v.1] | +| Test purpose
CUG with OA not allowed: Subsequent conferee added to the conference, successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the conference focus allows to join the created conference as a subsequent conferee and belongs to the same closed user group. | | | | +| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | +| SIP header values:
INVITE:
Request Line


FALSE
[registered CUG index]

| | | | +| Comments:
Test equipment (ISC, Mw) AS
A conference is already created
A CUG user is already added to the conference
INVITE →
200 OK ← | | | | + +### 7.3.2 Communication Diversion Services (CDIV) + +| | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------|--|-----------|--|---------------------------------|---------|---|--|---|---------| +| TSS
CUG/Services/CDIV | TP
CUG_N12_001 | CUG reference
Clause 4.6.7.1 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding unconditional (CFU) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFU. | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding Unconditional (CFU)
Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (ISC, Mw)
INVITE1 → → INVITE2
| | | | Test equipment (Gm) | | AS | | Test equipment (ISC, Mw) | INVITE1 | → | | → | INVITE2 | +| Test equipment (Gm) | | AS | | Test equipment (ISC, Mw) | | | | | | | | | | +| INVITE1 | → | | → | INVITE2 | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------| +| CUG/Services/CDIV | CUG_N12_002 | Clause 4.6.7.1 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose | | | | | | | | | | +|

CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFU successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
    cugCallOperation containing
        registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFU) and the communication to the forwarded-to party is successful.

| | | | | | | | | | +| Preconditions: | | | | | | | | | | +|

Originating user has subscribed to CUG
    Options for registered and preferred CUG index:
    Intra CUG restrictions: None designated (-OCB)
    Options for public identity in use:
    Preferential CUG: None designated
    Outgoing access: not allowed

Forwarding user has subscribed to CUG
    Options for public identity in use:
    Incoming access: not allowed

Forwarding user has subscribed to CDIV
    Communication Forwarding Unconditional (CFU)

Forwarded-to user has subscribed to CUG
    Options for public identity in use:
    Incoming access: not allowed

Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in the same CUG

| | | | | | | | | | +| SIP header values: | | | | | | | | | | +|

INVITE1:
<cug>
    <cugCallOperation>
        <outgoingAccessRequest>FALSE</outgoingAccessRequest>
        <cugIndex>[registered CUG index]</cugIndex>
    </cugCallOperation>
</cug>

| | | | | | | | | | +| Comments: | | | | | | | | | | +|
Test equipment (Gm) AS Test equipment (Gm)
INVITE1 ➔ ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | ➔ | ➔ INVITE2 | +| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | +| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|---------|---|--|--|--|--|---------------|---|--|-----|---|--| +| TSS
CUG/Services/CDIV | TP
CUG_N12_003 | CUG reference
Clause 4.6.7.1 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFU unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFU) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding Unconditional (CFU)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE1 ➠
403 Forbidden ⬅
ACK ➠
| | | | Test equipment (Gm) | | AS | INVITE1 | ➠ | | | | | 403 Forbidden | ⬅ | | ACK | ➠ | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | | | | +| INVITE1 | ➠ | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | +| 403 Forbidden | ⬅ | | | | | | | | | | | | | | | | | | +| ACK | ➠ | | | | | | | | | | | | | | | | | | + +52         Rec. ITU-T Q.4011.2 (08/2016) + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|---------|---|-----------|--|--|--|-----------------|--|--|--|-------|--|--|--|---|-----------| +| TSS
CUG/Services/CDIV | TP
CUG_N12_004 | CUG reference
Clause 4.6.7.2 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding on busy (CFB) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the communication diversion service CFB. | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Busy user (CFB)
Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw)
INVITE1 → → INVITE2
← 486 Busy Here
→ ACK
→ → INVITE3
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | INVITE1 | → | → INVITE2 | | | | ← 486 Busy Here | | | | → ACK | | | | → | → INVITE3 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | | +| | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | +| | | → | → INVITE3 | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|-----------|--|--|--|-----------------|--|--|--|-------|--|--|--|--|-----------| +| CUG/Services/CDIV | CUG_N12_005 | Clause 4.6.7.2 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | +| Test purpose | | | | | | | | | | | | | | | | | | | | | | | | +| CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFB successful. | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFB) and the communication to the forwarded-to party is successful. | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions: | | | | | | | | | | | | | | | | | | | | | | | | +| Originating user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | | | | | +| Options for registered and preferred CUG index: | | | | | | | | | | | | | | | | | | | | | | | | +| Intra CUG restrictions: None designated (-OCB) | | | | | | | | | | | | | | | | | | | | | | | | +| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | | | | | +| Preferential CUG: None designated | | | | | | | | | | | | | | | | | | | | | | | | +| Outgoing access: not allowed | | | | | | | | | | | | | | | | | | | | | | | | +| Forwarding user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | | | | | +| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | | | | | +| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | | | | | | +| Forwarding user has subscribed to CDIV | | | | | | | | | | | | | | | | | | | | | | | | +| Communication Forwarding on Busy user (CFB) | | | | | | | | | | | | | | | | | | | | | | | | +| Forwarded-to user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | | | | | +| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | | | | | +| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | | | | | | +| Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | +| Originating party and forwarded-to party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values: | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1: | | | | | | | | | | | | | | | | | | | | | | | | +|
 <cug>     <cugCallOperation>         <outgoingAccessRequest>FALSE</outgoingAccessRequest>         <cugIndex>[registered CUG index]</cugIndex>     </cugCallOperation> </cug> 
| | | | | | | | | | | | | | | | | | | | | | | | +| Comments: | | | | | | | | | | | | | | | | | | | | | | | | +|
Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm)
INVITE1 → → INVITE2
← 486 Busy Here
→ ACK
→ INVITE3
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | | ← 486 Busy Here | | | | → ACK | | | | | → INVITE3 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | | +| | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | +| | | | → INVITE3 | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------|--|--|-----------------|--|--|-------|---------------|---|--|-----|---|--| +| TSS
CUG/Services/CDIV | TP
CUG_N12_006 | CUG reference
Clause 4.6.7.2 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFB unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFB) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Busy user (CFB)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm)
INVITE1 → → INVITE2
← 486 Busy Here
→ ACK
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | ← 486 Busy Here | | | → ACK | 403 Forbidden | ← | | ACK | → | | +| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | +| | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|------------------------------------------------------|---|--------------------------------------------|--------|------------------------------------------------------|---|--------------------------------------------| +| CUG/Services/CDIV | CUG_N12_007 | Clause 4.6.7.3 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding on no reply (CFNR) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNR. | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on no Reply (CFNR)
Originating party and forwarding party are in the same CUG | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | +| Comments:
Test equipment (Gm)
INVITE1
➔ AS ➔
←
Test equipment (Gm)
INVITE2
180 Ringing
➔ Test equipment (ISC, Mw)
INVITE3
| | | | Test equipment (Gm)
INVITE1 | ➔ | AS | ➔
← | Test equipment (Gm)
INVITE2
180 Ringing | ➔ | Test equipment (ISC, Mw)
INVITE3 | +| Test equipment (Gm)
INVITE1 | ➔ | AS | ➔
← | Test equipment (Gm)
INVITE2
180 Ringing | ➔ | Test equipment (ISC, Mw)
INVITE3 | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|-----------|--|--|--|---------------|--|--|--|--|-----------| +| CUG/Services/CDIV | CUG_N12_008 | Clause 4.6.7.3 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | +| Test purpose | | | | | | | | | | | | | | | | | | | | +| CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNR successful. | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNR) and the communication to the forwarded-to party is successful. | | | | | | | | | | | | | | | | | | | | +| Preconditions: | | | | | | | | | | | | | | | | | | | | +| Originating user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | +| Options for registered and preferred CUG index: | | | | | | | | | | | | | | | | | | | | +| Intra CUG restrictions: None designated (-OCB) | | | | | | | | | | | | | | | | | | | | +| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | +| Preferential CUG: None designated | | | | | | | | | | | | | | | | | | | | +| Outgoing access: not allowed | | | | | | | | | | | | | | | | | | | | +| Forwarding user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | +| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | +| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | | +| Forwarding user has subscribed to CDIV | | | | | | | | | | | | | | | | | | | | +| Communication Forwarding on no Reply (CFNR) | | | | | | | | | | | | | | | | | | | | +| Forwarded-to user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | +| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | +| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | | +| Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | | | | | | +| Originating party and forwarded-to party are in the same CUG | | | | | | | | | | | | | | | | | | | | +| SIP header values: | | | | | | | | | | | | | | | | | | | | +| INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | +| Comments: | | | | | | | | | | | | | | | | | | | | +|
Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm)
INVITE1 → → INVITE2
← 180 Ringing
→ INVITE3
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | | ← 180 Ringing | | | | | → INVITE3 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | | +| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | +| | | ← 180 Ringing | | | | | | | | | | | | | | | | | | +| | | | → INVITE3 | | | | | | | | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|--|-----------|--|----------------------------|---------|---|--|---|---------|--|--|--|---|-------------|---------------|---|--|--|--|-----|---|--|--|--| +| CUG/Services/CDIV | CUG_N12_009 | Clause 4.6.7.3 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNR unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNR) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on no Reply (CFNR)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm)
INVITE1 → → INVITE2
← 180 Ringing
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | | AS | | Test equipment (Gm) | INVITE1 | → | | → | INVITE2 | | | | ← | 180 Ringing | 403 Forbidden | ← | | | | ACK | → | | | | +| Test equipment (Gm) | | AS | | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | | → | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------|---|-----------|---|--------------------------------------------| +| TSS
CUG/Services/CDIV | TP
CUG_N12_010 | CUG reference
Clause 4.6.7.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding on not logged-in (CFNL) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNL. | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Not Logged-in (CFNL)
Originating party and forwarding party are in the same CUG | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | +| Comments:
Test equipment (Gm)
INVITE1
➔ AS ➔ Test equipment (ISC, Mw)
INVITE2
| | | | Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (ISC, Mw)
INVITE2 | +| Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (ISC, Mw)
INVITE2 | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------| +| CUG/Services/CDIV | CUG_N12_011 | Clause 4.6.7.4 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | +| Test purpose | | | | | | | | | | +| CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNL successful. | | | | | | | | | | +| Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNL) and the communication to the forwarded-to party is successful. | | | | | | | | | | +| Preconditions: | | | | | | | | | | +| Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Not Logged-in (CFNL)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in the same CUG | | | | | | | | | | +| SIP header values: | | | | | | | | | | +| INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | +| Comments: | | | | | | | | | | +|
Test equipment (Gm) AS Test equipment (Gm)
INVITE1 ➔ ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | ➔ | ➔ INVITE2 | +| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | +| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|---------|---|--|--|--|--|---------------|---|--|-----|---|--| +| TSS
CUG/Services/CDIV | TP
CUG_N12_012 | CUG reference
Clause 4.6.7.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNL unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNL) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Not Logged-in (CFNL)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS
INVITE1 ➔
403 Forbidden ←
ACK ➔
| | | | Test equipment (Gm) | | AS | INVITE1 | ➔ | | | | | 403 Forbidden | ← | | ACK | ➔ | | +| Test equipment (Gm) | | AS | | | | | | | | | | | | | | | | | +| INVITE1 | ➔ | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | + +Rec. ITU-T Q.4011.2 (08/2016) 61 + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|---------------------------------------|---------------------------------|-----------|---|---------------------------------------|---------------------------------|--|--|--|--|--|-----------| +| CUG/Services/CDIV | CUG_N12_013 | Clause 4.6.7.5 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, CNRc successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNRc. | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Subscriber Not Reachable (CFNRc)
Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm)
INVITE1
➔ AS ➔ Test equipment (Gm)
INVITE2
Test equipment (ISC, Mw)
➔ INVITE3
| | | | Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (Gm)
INVITE2 | Test equipment (ISC, Mw) | | | | | | ➔ INVITE3 | +| Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (Gm)
INVITE2 | Test equipment (ISC, Mw) | | | | | | | | | | | +| | | | | | ➔ INVITE3 | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|---------|--|--|--|---|---------| +| TSS
CUG/Services/CDIV | TP
CUG_N12_014 | CUG reference
Clause 4.6.7.5 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNRc successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNRc) and the communication to the forwarded-to party is successful. | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Subscriber Not Reachable (CFNRc)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in the same CUG | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm)
INVITE1 → INVITE2
→ INVITE3
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | INVITE2 | | | | → | INVITE3 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | +| INVITE1 | → | INVITE2 | | | | | | | | | | | | | | +| | | → | INVITE3 | | | | | | | | | | | | | + +Rec. ITU-T Q.4011.2 (08/2016)      63 + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|---------|--|---------------|---|--|--|-----|---|--|--| +| CUG/Services/CDIV | CUG_N12_015 | Clause 4.6.7.5 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNRc unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNRc) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matching CUG data. | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Subscriber Not Reachable (CFNRc)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm)
INVITE1 → INVITE2
403 Forbidden ←
ACK →
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | INVITE2 | | 403 Forbidden | ← | | | ACK | → | | | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | | +| INVITE1 | → | INVITE2 | | | | | | | | | | | | | | | | | | +| 403 Forbidden | ← | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|---------|---|-----------|--|--|--|---------------|--|--|--|-------------------------|--|--|--|-------|--|--|--|--|-----------| +| CUG/Services/CDIV | CUG_N12_016 | Clause 4.6.7.6 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call setup between originating party and deflecting party, communication deflection (CD) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the deflecting party and performs the communication diversion service CD. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Deflecting user has subscribed to CDIV
Communication Deflection (CD)
Originating party and deflecting party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw)
INVITE1 → → INVITE2
← 180 Ringing
← 302 Moved Temporarily
→ ACK
→ INVITE3
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | INVITE1 | → | → INVITE2 | | | | ← 180 Ringing | | | | ← 302 Moved Temporarily | | | | → ACK | | | | | → INVITE3 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
CUG/Services/CDIV | TP
CUG_N12_017 | CUG reference
Clause 4.6.7.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|--------------------------------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|-----------|--|--|--|---------------|--|--|--|-------------------------|--|--|--|-------|--|--|--|--|-----------| +| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CD successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the deflecting party and the deflected-to party (CD) and the communication to the deflected-to party is successful. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Deflecting user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Deflected-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and deflecting party are in the same CUG
Originating party and deflected-to party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm)
INVITE1 ➔ ➔ INVITE2
← 180 Ringing
← 302 Moved Temporarily
➔ ACK
➔ INVITE3
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | ➔ | ➔ INVITE2 | | | | ← 180 Ringing | | | | ← 302 Moved Temporarily | | | | ➔ ACK | | | | | ➔ INVITE3 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
CUG/Services/CDIV | TP
CUG_N12_018 | CUG reference
Clause 4.6.7.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------|--|--|---------------|--|--|-------------------------|--|--|-------|-------------------|-------|--|-----|---|--| +| Test purpose
CUG with OA not allowed: Call setup between originating party and deflected-to party, CD unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the deflecting party and the deflected-to party (CD) and the communication to the deflected-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Deflecting user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
deflected-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and deflecting party are in the same CUG
Originating party and deflected-to party are in different CUG | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm)
INVITE1 → → INVITE2
← 180 Ringing
← 302 Moved Temporarily
→ ACK

403 Forbidden

←
ACK →
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | ← 180 Ringing | | | ← 302 Moved Temporarily | | | → ACK |
403 Forbidden |
← | | ACK | → | | +| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | +|
403 Forbidden |
← | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | + +### 7.3.3 Explicit communication transfer (ECT) + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|--------|---|----------|-------------|---|---------------|--------|---|----------|-----|---|-------| +| CUG/Services/ECT | CUG_N13_001 | Clause 4.6.10 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Communication transfer - transferor and transferee in the same CUG, successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferor and the transferee. The communication is successful | | | | | | | | | | | | | | | | | | | +| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE:
Request Line


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm)
INVITE ➔ ➔ INVITE
180 Ringing ⬅ ⬅ 180 Ringing
200 OK ⬅ ⬅ 200 OK
ACK ➔ ➔ ACK
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE | ➔ | ➔ INVITE | 180 Ringing | ⬅ | ⬅ 180 Ringing | 200 OK | ⬅ | ⬅ 200 OK | ACK | ➔ | ➔ ACK | +| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ 180 Ringing | | | | | | | | | | | | | | | | | +| 200 OK | ⬅ | ⬅ 200 OK | | | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ ACK | | | | | | | | | | | | | | | | | + +| TSS
CUG/Services/ECT | TP
CUG_N13_001 | CUG reference
Clause 4.6.10 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|------------------------------------------------------------------------|--|--|--|-------|---|--|--|--------------|---|--|--|-----|---|--|--|--------------|---|--|--|--|--|-----------|---------| +| Test purpose
CUG with OA not allowed: Call communication transfer transferee and transfer target in the same CUG, successful blind transfer.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferee and the transfer target and performs the communication transfer service (Blind transfer). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:
Request Line


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw)
A communication between transferor and transferee already exits
REFER ➔
202 Accepted ⬅
BYE ➔
200 OK (BYE) ⬅
INVITE1 ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | A communication between transferor and transferee already exits | | | | REFER | ➔ | | | 202 Accepted | ⬅ | | | BYE | ➔ | | | 200 OK (BYE) | ⬅ | | | | | INVITE1 ➔ | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| A communication between transferor and transferee already exits | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (BYE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE1 ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|-------------------------------------------------------------------------|--|--|--|-------|---|--|--|--------------|---|--|--|--|--|-----------|---------| +| CUG/Services/ECT | CUG_N13_001 | Clause 4.6.10 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call communication transfer transferee and transfer target in the same CUG, successful assured transfer.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferee and the transfer target and performs the communication transfer service (assured transfer). | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:
Request Line


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw)
A communication between transferor and transferee already exists
REFER ➔
202 Accepted ⬅
INVITE1 ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | A communication between transferor and transferee already exists | | | | REFER | ➔ | | | 202 Accepted | ⬅ | | | | | INVITE1 ➔ | INVITE2 | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | | +| A communication between transferor and transferee already exists | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | | +| | | INVITE1 ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|--|------------------------------------------------------------------------|--|--|--|-----------------------------------------------------------------------------|--|--|-------|---|--|--|--------------|---|--|--| +| CUG/Services/ECT | CUG_N13_001 | Clause 4.6.10 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CUG with OA not allowed: Call Communication transfer transferee and transfer target in the same CUG, successful consultative transfer.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferee and the transfer target and performs the communication transfer service (assured transfer). | | | | | | | | | | | | | | | | | | | | | | | | +| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values:
INVITE1:
Request Line


FALSE
[registered CUG index]

| | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw)
A communication between transferor and transferee already exits
A communication between transferor and transfer target already exits
REFER ➔
202 Accepted ⬅
INVITE1 ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | A communication between transferor and transferee already exits | | | | A communication between transferor and transfer target already exits | | | REFER | ➔ | | | 202 Accepted | ⬅ | | | +| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | | +| | A communication between transferor and transferee already exits | | | | | | | | | | | | | | | | | | | | | | | +| | A communication between transferor and transfer target already exits | | | | | | | | | | | | | | | | | | | | | | | +| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | | +| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | | + + + + + +## **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.4011.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/Q/T-REC-Q.4011.3-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.4011.3-201608-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0159f17f74c345c265ea824e976fe9eb8fab9e6d --- /dev/null +++ b/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f2d01f3d5c249e393eb2533eb660bacb3b30eccf94d1201834adfe4005e4fec +size 15510 diff --git a/marked/Q/T-REC-Q.4014.2-201904-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4014.2-201904-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..36e3400d2ee8b59eb3a05f9dbbf771b4f5fc587f --- /dev/null +++ b/marked/Q/T-REC-Q.4014.2-201904-I_PDF-E/raw.md @@ -0,0 +1,14879 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4014.2** + +(04/2019) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**PSTN/ISDN terminal equipment using IP +multimedia core network subsystem; +Conformance testing – Part 2: Test suite +structure and test purposes** + +Recommendation ITU-T Q.4014.2 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters 'ITU' are prominently displayed in blue and white within the globe. + +ITU logo + +International +Telecommunication +Union + +# 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.4014.2 + +# PSTN/ISDN terminal equipment using IP multimedia core network subsystem; Conformance testing – Part 2: Test suite structure and test purposes + +## Summary + +Recommendation ITU-T Q.4014.2 is part 2 of the testing specifications of the terminal equipment used in the IMS-based public switched telephone network/integrated services digital network (PSTN/ISDN) emulation subsystem based on the media gateway control protocol, the session initiation protocol and the associated session description protocol. + +The Recommendation specifies the test suite structure and test purposes (TSS and TP) to test PSTN/ISDN terminal equipment using Internet protocol (IP) multimedia core network subsystem. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4014.2 | 2019-04-29 | 11 | 11.1002/1000/13886 | + +## Keywords + +IAD, IMS, PES, SDP, SIP, testing, TP, TSS, 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 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 ..... | 3 | +| 3.1 Terms defined elsewhere ..... | 3 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 5 | +| 6 Test suite structure..... | 5 | +| 7 Test purposes ..... | 6 | +| 7.1 Introduction ..... | 6 | +| 7.2 Procedures at the user equipment..... | 6 | + + + +## Recommendation ITU-T Q.4014.2 + +# PSTN/ISDN terminal equipment using IP Multimedia core network subsystem; Conformance testing – Part 2: Test suite structure and test purposes + +# 1 Scope + +This Recommendation specifies the test suite structure and test purposes to test PSTN/ISDN terminal equipment using IP multimedia core network subsystem. + +# 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 H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*. +- [ITU-T Q.4014.1] Recommendation ITU-T Q.4014.1 (2019), *PSTN/ISDN terminal equipment using IP Multimedia core network subsystem; Conformance testing – Part 1: PICS*. +- [ISO/IEC 9646-1] Recommendation ISO/IEC 9646-1, *Information technology – Open systems interconnection – Conformance testing methodology and framework – Part 1: General concepts*. +- [ETSI TS 124 147] Recommendation ETSI TS 124 147 (2015-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3*. +- [ETSI TS 124 229] Recommendation ETSI TS 124 229 (2019), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 Release 10)*. +- [ETSI TS 124 605] Recommendation ETSI TS 124 605 (2013-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 version 10.1.0 Release 10)*. +- [ETSI TS 124 608] Recommendation ETSI TS 124 608 (2013-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 version 10.1.0 Release 10)*. + +- [ETSI TS 124 628] Recommendation ETSI TS 124 628 (2013), *Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.628 version 10.4.0 Release 10).* +- [ETSI TS 129 163] Recommendation ETSI TS 129 163 (2019), *Digital cellular telecommunications system (Phase 2+) (GSM);Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks.* +- [ETSI TS 183 036] Recommendation ETSI TS 183 036 (2012), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification.* +- [ETSI TS 183 043] Recommendation ETSI TS 183 043 (2011), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification.* +- [IETF RFC 768] Recommendation IETF RFC 768 (1980), *User Datagram Protocol.* +- [IETF RFC 793] Recommendation IETF RFC 793 (1981), *Transmission Control Protocol.* +- [IETF RFC 2327] Recommendation IETF RFC 2327 (1998), *SDP: Session Description Protocol.* +- [IETF RFC 2805] Recommendation IETF RFC 2805 (2000), *Media Gateway Control Protocol Architecture and Requirements.* +- [IETF RFC 3261] Recommendation IETF RFC 3261 (2002), *SIP: Session Initiation Protocol.* +- [IETF RFC 3262] Recommendation IETF RFC 3262 (2002), *Integration of Resource Management and Session Initiation Protocol (SIP).* +- [IETF RFC 3312] Recommendation IETF RFC 3312 (2002), *Reliability of Provisional Responses in the Session Initiation Protocol (SIP).* +- [IETF RFC 3323] Recommendation IETF RFC 3323 (2002), *A Privacy Mechanism for the Session Initiation Protocol (SIP).* +- [IETF RFC 3325] Recommendation IETF RFC 3325 (2002), *Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks.* +- [IETF RFC 5009] Recommendation IETF RFC 5009 (2007), *Private Header (P-Header) Extension to Session Initiation Protocol (SIP) for Authorization of Early Media.* +- [IETF RFC 6080] Recommendation IETF RFC 3312 (2011), *A Framework for Session Initiation Protocol User Agent Profile Delivery.* +- [IETF RFC 6140] Recommendation IETF RFC 6140 (2011), *Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP).* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 access gateway** [ETSI TS 183 043]: Gateway device that interworks a significant number of analogue lines/ISDN accesses (directly or via an V5 Access Network) to a packet network and is located at the operator's premises. + +**3.1.2 loose coupling** [ETSI TS 183 043]: On-hook and flash-hook are analyzed in the AGCF/VGW; much like a simulation endpoint would operate. + +**3.1.3 media gateway (MGW)** [ETSI TS 183 043]: Gateway device acting at the media/transport plane, providing the functions of an MGF. + +**3.1.4 media gateway controller (MGC)** [ITU-T H.248.1]: Controls the parts of the call state that pertain to connection control for media channels in an MG. + +**3.1.5 residential gateway** [ETSI TS 183 043]: Gateway device that interworks a small number of analogue lines/ISDN accesses. + +**3.1.6 tight coupling** [ETSI TS 183 043]: On-hook and flash-hook are interpreted by the AS. + +**3.1.7 voice over IP gateway (VGW)** [ETSI TS 183 043]: SIP-based gateway device that implements both a media gateway function and a media gateway controller function as defined in IETF RFC 2805 and supports the provision of voice based services to analogue lines/ISDN accesses. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------------| +| 3PTY | Three-Party Service | +| ACR | Anonymous Communication Rejection | +| AGCF | Access Gateway Control Function | +| AGW | Access Gateway | +| AOC-D | Advice of Charge During the call | +| AOC-E | Advice of Charge at the End of the call | +| AOC-S | Advice of Charge at call Set-up time | +| AS | Application Server | +| BC | Bearer Capability information element | +| BRI | Basic Rate Interface | +| CCBS | Call Completion on Busy Subscriber | +| CCNR | Call Completion on No Reply | +| CD | Call Deflection | +| CFB | Call Forwarding on Busy | +| CFU | Call Forwarding Unconditional | +| CLIP | Calling Line Identification Presentation | +| COLP | Connected Line identification Presentation | +| CSCF | Call Session Control Function | + +| | | +|--------|-----------------------------------------------| +| CUG | Closed User Group | +| CW | Communication Waiting | +| FQDN | Fully Qualified Domain Name | +| HLC | High Layer Compatibility | +| HOLD | call HOLD | +| IAD | Integrated Access Device | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| IUT | Implementation Under Test | +| MCID | Malicious Communication Identification | +| MGC | Media Gateway Controller | +| MGF | Media Gateway Function | +| MIME | Multimodal Internet Mail Extensions | +| MWI | Message Waiting Indication | +| OIP | Originating Identification Presentation | +| OIR | Originating Identification | +| PICS | Protocol Implementation Conformance Statement | +| POTS | Plain Old Telephone Service | +| PSTN | Public Switched Telephone Network | +| S-CSCF | Serving CSCF | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| SOC | Switching Order Command | +| SUT | System Under Test | +| TIP | Terminating Identification Presentation | +| TIR | Terminating Identification Restriction | +| TP | Test Purposes | +| TSS | Test Suite Structure | +| UA | User Agent | +| UE | User Equipment | +| URI | Uniform Resource Identifier | +| URN | User Requirements Notation | +| VGW | Voice over IP Gate Way | +| XML | Extensible Markup Language | + +# 5 Conventions + +- is "protocol"; +- is "ETSI TS 183 043"; +- is "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification"; +- is "IMS-based PSTN/ISDN Emulation; Stage 3 specification". + +# 6 Test suite structure + +**Table 6-1 – Test suite structure** + +| | | | +|-------------------------------------|------------------------------------------------|------------| +| Registration | Initial_registration | TP_101_xxx | +| | User-initiated_re-registration | TP_102_xxx | +| | User-initiated_deregistration | TP_103_xxx | +| | Network-initiated_deregistration | TP_104_xxx | +| | Subscription_and_notification | TP_105_xxx | +| Call initiation_UE-originating_case | Orig_Establishment_of_an_early_dialogue | TP_201_xxx | +| | Orig_Establishment_of_a_confirmed_dialogue | TP_202_xxx | +| | Orig_Release_initiated_by_the_terminating_user | TP_203_xxx | +| | Orig_Release_initiated_by_the_terminating_user | TP_204_xxx | +| | Orig_Timers | TP_205_xxx | +| | Orig_Abnormal_situations | TP_206_xxx | +| Call initiation_UE_terminating_case | Term_Establishment_of_an_early_dialogue | TP_301_xxx | +| | Term_Establishment_of_a_confirmed_dialogue | TP_302_xxx | +| | Term_Release_initiated_by_the_originating_user | TP_303_xxx | +| | Term_Release_initiated_by_the_terminating_user | TP_304_xxx | +| | Term_Timers | TP_305_xxx | +| | Term_Abnormal_situations | TP_306_xxx | +| Emergency_service | | TP_401_xxx | +| Supplementary_Service_control | OIP_OIR | TP_501_xxx | +| | TIP_TIR | TP_502_xxx | +| | HOLD | TP_503_xxx | +| | CDIV | TP_504_xxx | +| | 3PTY | TP_505_xxx | +| | CUG | TP_506_xxx | +| | CW | TP_507_xxx | +| | TP | TP_508_xxx | +| | ECT | TP_509_xxx | +| | UUS | TP_510_xxx | +| | SUB | TP_511_xxx | +| | MCID | TP_512_xxx | +| | MWI | TP_513_xxx | +| | CCBS_CCNR | TP_514_xxx | + +# 7 Test purposes + +## 7.1 Introduction + +For each test requirement, a test purpose (TP) is defined. + +All protocol implementation conformance statement (PICS) items referred to in this clause are as specified in [ITU-T Q.4014.1] unless indicated otherwise by another numbered reference. + +### 7.1.1 TP naming convention + +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 or not it applies to the network (see Table 7.1.1). + +**Table 7.1.1 – TP identifier naming convention scheme** + +| | +|-------------------------------------------------------------------------------| +| - Identifier: TP__ | +| - = group 3 digit field representing group reference according to TSS | +| - = sequential number (001-999) | + +### 7.1.2 Test strategy + +As the base standards [ETSI TS 124 229] and [ETSI TS 183 036] contain no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification [ITU-T Q.4014.1]. The criteria applied include the following: + +- Whether or not a test case can be built from the TP is not considered. + +## 7.2 Procedures at the user equipment + +### 7.2.1 Registration and authentication + +#### 7.2.1.1 Initial registration + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|-------------------|--|-----------------------|---------------------------|--|--|--|---|------------|--|---|------------------|--|---|------------|--|---|-------------------|-------------------------|--|--| +| TSS
Initial_registration | TP_101_001 | Reference
clause 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
REGISTER request have to be authorized receipt of 401

Ensure that the SUT sends a REGISTER request, receives a 401 Unauthorized and the WWW- Authenticate header is present. The SUT repeats the REGISTER request. The Authorization header is present including 'username', 'realm', 'nonce', 'digest-uri' and 'response' HTTP parameters. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
401
WWW-Authenticate:
REGISTER 2
Authorization: username[proper value];realm=[proper value];nonce=[proper value];digest-uri=[proper value] | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available
➔ REGISTER 1
⬅ 401 Unauthorized
➔ REGISTER 2
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | Make end device available | | | | ➔ | REGISTER 1 | | ⬅ | 401 Unauthorized | | ➔ | REGISTER 2 | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|---|------------|--|---|-----------------------------------|--|---|------------|--|---|-------------------|--------------------------------|--|--| +| TSS
Initial_registration | TP_101_002 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
REGISTER request have to be authorized, receipt of 407 | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT sends a REGISTER request, receives a 407 Proxy Authentication Required and the Proxy-Authenticate header is present. The SUT repeats the REGISTER request. The Proxy-Authorization header is present including 'username', 'realm', 'nonce', 'digest-uri' and 'response' HTTP parameters. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
407
Proxy-Authenticate:
REGISTER 2
Proxy-Authorization: username=[proper value];realm=[proper value];nonce=[proper value];digest-uri=[proper value] | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available
➔ REGISTER 1
⬅ 407 Proxy Authentication Required
➔ REGISTER 2
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | Make end device available | | | | ➔ | REGISTER 1 | | ⬅ | 407 Proxy Authentication Required | | ➔ | REGISTER 2 | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|---|------------|--|---|-----------------------------------|--|---|------------|--|---|-------------------|--------------------------------|--|--| +| TSS
Initial_registration | TP_101_003 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
REGISTER request have to be authorized, receipt of 407 the Cseq is incremented | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT sends a REGISTER request, receives a 407 Proxy Authentication Required and the Proxy-Authenticate header is present. The SUT repeats the REGISTER request. The Proxy-Authorization header is present and the Cseq header value is incremented. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
REGISTER 1
Call-ID [any value]
Cseq x REGISTER

REGISTER 2
Call-ID [same value as in REGISTER 1]
Cseq x+1 REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available
➔ REGISTER 1
⬅ 407 Proxy Authentication Required
➔ REGISTER 2
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | Make end device available | | | | ➔ | REGISTER 1 | | ⬅ | 407 Proxy Authentication Required | | ➔ | REGISTER 2 | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|--------------|--|--|--------------------|--|--|--------------|--|--|---------------------|--|--------------------------------|--|--| +| TSS
Initial_registration | TP_101_004 | Reference
section 10.2 and 22 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Request line in the REGISTER request

Ensure that the SUT sends a REGISTER request to its registrar and there is no 'userpart' in the SIP-URI of the Request-line. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
REGISTER
Request-line: sip:[hostpart=domain of location service] | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available
➔ REGISTER 1
⬅ 401 Unauthorized
➔ REGISTER 2
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | Make end device available | | | | ➔ REGISTER 1 | | | ⬅ 401 Unauthorized | | | ➔ REGISTER 2 | | | ⬅ 200 OK (REGISTER) | | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|--------------|--|--|--------------------|--|--|--------------|--|--|---------------------|--|--------------------------------|--|--| +| TSS
Initial_registration | TP_101_005 | Reference
section 10.3 and 22 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Successful final response to the REGISTER request

Ensure that the SUT receives a 200 OK Final response to the REGISTER request sent to its registrar and the Contact header and an 'expires' parameter in the Contact header. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (REGISTER)
Contact: sip:[any registered URI];expires=[any value] | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available
➔ REGISTER 1
⬅ 401 Unauthorized
➔ REGISTER 2
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | Make end device available | | | | ➔ REGISTER 1 | | | ⬅ 401 Unauthorized | | | ➔ REGISTER 2 | | | ⬅ 200 OK (REGISTER) | | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|------------------------------------| +| TSS
Initial_registration | TP_101_006 | Reference
section 10.2.6 of
[IETF RFC 3261] | Selection expression
PICS 5.2/1 | +| Test purpose
Successful registration using a preconfigured registrar address

Ensure that the SUT sends a REGISTER request addressed to a pre-configured registrar without a 'userpart' in the Request URI. | | | | + +| | | +|-------------------------------------------------------------------------------------------------------------|-----------------------| +| SIP header values
REGISTER
Request-line: sip:[hostpart=preconfigured registrar address] | | +| Message flow | | +| End device
Make end device available | Test equipment | +| → REGISTER 1
← 401 Unauthorized
→ REGISTER 2
← 200 OK (REGISTER)
Apply post test routine | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|------------------------------------| +| TSS
Initial_registration | TP_101_007 | Reference
section 10.2.6 of
[IETF RFC 3261] | Selection expression
PICS 5.2/2 | +| Test purpose
Successful registration using the 'multicast' mechanism | | | | +| Ensure that the SUT sends a REGISTER request to the "all SIP servers" multicast address "sip:mcast.net" without a 'userpart'. | | | | +| SIP header values
REGISTER
Request-line: sip:
OR
Request-line: sip: <224.0.1.75> | | | | +| Message flow | | | | +| End device
Make end device available. | Test equipment | | | +| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER)
Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_008 | Reference
section 10.2 of [IETF RFC 3261] | Selection expression | +| Test purpose
Successful registration To header | | | | +| Ensure that the SUT sends a REGISTER request to the registrar and the To header with the address of the registrant and the type of the To header is 'sip' | | | | +| SIP header values
REGISTER
To: sip:[address of registrant] | | | | + +| | | +|-----------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| Make end device available. | | +| ➔ | REGISTER | +| ⬅ | 401 Unauthorized | +| ➔ | REGISTER | +| ⬅ | 200 OK (REGISTER) | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|-------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_009 | Reference
section 10.2 of
[IETF RFC 3261] | Selection expression | +|-----------------------------|------------|-------------------------------------------------|----------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Successful registration From header | +| Ensure that the SUT sends a REGISTER request to the registrar and the 'From' header is set to the same value as the To header. | + +| | +|----------------------------------------------------------------------| +| SIP header values
REGISTER | +| To: sip:[address of registrant]
From: sip:[address of registrant] | + +| | | +|-----------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| Make end device available. | | +| ➔ | REGISTER | +| ⬅ | 401 Unauthorized | +| ➔ | REGISTER | +| ⬅ | 200 OK (REGISTER) | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|----------------------------------------------------------|------------------------------------| +| TSS
Initial_registration | TP_101_010 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/1 | +|-----------------------------|------------|----------------------------------------------------------|------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Successful registration Via header for UDP | +| Ensure that the SUT sends a REGISTER request to the registrar and the 'Via' header contains a sent-by field containing the IP address or fully qualified domain name (FQDN) of the UE and the port number where the UE expects to receive the response to this request when UDP is used. | + +| | +|--------------------------------------------------------------------------------------------------------| +| SIP header values
REGISTER | +| Via: SIP/2.0/UDP [IP Address]:[Port number];branch=z9hG4bK[branch]; sent-by=[IP Address]:[Port number] | + +| | | +|-----------------------------------------------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| Make end device available. | | +| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) | | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|----------------------------------------------------------|------------------------------------| +| TSS
Initial_registration | TP_101_011 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/2 | +|-----------------------------|------------|----------------------------------------------------------|------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Successful registration Via header for TCP | +| Ensure that the SUT sends a REGISTER request to the registrar and the 'Via' header contains a "rport" header field parameter with no value in the Via header field when TCP is used. | + +| | +|-------------------------------------------------------------------------------------------------------------------------| +| SIP header values
REGISTER
Via: SIP/2.0/UDP [IP Address]:[Port number];branch=z9hG4bK[branch];rport | +|-------------------------------------------------------------------------------------------------------------------------| + +| | | +|-----------------------------------------------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| Make end device available. | | +| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) | | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|----------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_012 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression | +|-----------------------------|------------|----------------------------------------------------------|----------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Successful registration option-tag 'path' in the Supported header | +| Ensure that the SUT sends a REGISTER request to the registrar and the 'Supported' header contains the option-tag "path". | + +| | +|----------------------------------------------------------------| +| SIP header values
REGISTER
Supported: path | +|----------------------------------------------------------------| + +| | | +|-----------------------------------------------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| Make end device available. | | +| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) | | +| Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------|-------------------|--|-----------------------|----------------------------|--|--|--|---|----------|--|---|------------------|--|---|----------|--|---|-------------------|--------------------------------|--|--| +| TSS
Initial_registration | TP_101_013 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/3 | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Successful registration option-tag 'gruu' in the Supported header

Ensure that the SUT sends a REGISTER request to the registrar and the 'Supported' header contains the option-tag "gruu" if the SUT supports GRUU. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
REGISTER
Supported: gruu | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available.
➔ REGISTER
⬅ 401 Unauthorized
➔ REGISTER
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | Make end device available. | | | | ➔ | REGISTER | | ⬅ | 401 Unauthorized | | ➔ | REGISTER | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Make end device available. | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|--------------------------------------------|-------------------|--|-----------------------|----------------------------|--|--|--|---|----------|--|---|------------------|--|---|----------|--|---|-------------------|--------------------------------|--|--| +| TSS
Initial_registration | TP_101_014 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/4 and 5.2 | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Successful registration option-tag 'gin' in the Require header

Ensure that the SUT sends a REGISTER request to the registrar and the 'Require' header contains the option-tag "gin" if the SUT performs the functions of an external attached network. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
REGISTER
Require: gin | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available.
➔ REGISTER
⬅ 401 Unauthorized
➔ REGISTER
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | Make end device available. | | | | ➔ | REGISTER | | ⬅ | 401 Unauthorized | | ➔ | REGISTER | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Make end device available. | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|--------------------------------------------| +| TSS
Initial_registration | TP_101_015 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/4 and 5.2 | +| Test purpose
Successful registration option-tag 'gin' in the Proxy-Require header

Ensure that the SUT sends a REGISTER request to the registrar and the 'Proxy-Require' header contains the option-tag "gin" if the SUT performs the functions of an external attached network. | | | | + +| | | +|-------------------------------------------------------------------|-----------------------------------------------------------------------| +| SIP header values
REGISTER
Proxy-Require: gin | | +| Message flow | | +| End device | Test equipment | +| Make end device available. | | +| | → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_016 | Reference
section 10.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Successful registration. No new registration before successful final response | | | | +| Ensure that the SUT does not send a new REGISTER request before it has received a successful final response to its previous REGISTER request or before expiration of the re-attempt timeout. | | | | +| SIP header values
REGISTER | | | | +| Message flow | | | | +| End device | Test equipment | | | +| Make end device available. | | | | +| | → REGISTER
← 401 Unauthorized
→ REGISTER | | | +| | Timeout initial request
→ REGISTER
← 200 OK (REGISTER) | | | +| Apply post test routine | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_017 | Reference
section 10.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Successful registration increments the Cseq in a new request | | | | +| Ensure that the SUT sends a new REGISTER request and increments the Cseq header and uses the same Call-ID value as in the initial REGISTER request. | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|-----------------------|---------------------------|--|--|--|---|------------|--|---|------------------|--|---|------------|--|---|-------------------|-------------------------|--|--| +| SIP header values
REGISTER 1
Call-ID [any value]
Cseq x REGISTER

REGISTER 2
Call-ID [same value as in REGISTER 1]
Cseq x+1 REGISTER | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SUT is already registered
→ REGISTER 1
← 401 Unauthorized
→ REGISTER 2
← 200 OK (REGISTER)
Apply post test routine
| End device | | Test equipment | SUT is already registered | | | | → | REGISTER 1 | | ← | 401 Unauthorized | | → | REGISTER 2 | | ← | 200 OK (REGISTER) | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SUT is already registered | | | | | | | | | | | | | | | | | | | | | | +| | → | REGISTER 1 | | | | | | | | | | | | | | | | | | | | +| | ← | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | +| | → | REGISTER 2 | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------|------------|------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_018 | Reference
section 10.2.4 of [IETF RFC 3261] | Selection expression | +|-----------------------------|------------|------------------------------------------------|----------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Successful registration. Refreshing of registration

Ensure that the SUT refreshes each Binding given in the expires parameter of the Contact header received in the previous 200 OK REGISTER final response. The Call-ID is the same as in the previous REGISTER request and the Cseq header value is incremented. | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|-----------------------|---------------------------|--|--|--|---|----------|--|---|------------------|--|---|------------|--|---|-------------------|-------------------------|--|--| +| SIP header values
REGISTER 1
Call-ID [any value]
Cseq x REGISTER

REGISTER 2
Call-ID [same value as in REGISTER 1]
Cseq x+1 REGISTER | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SUT is already registered
→ REGISTER
← 401 Unauthorized
→ REGISTER 2
← 200 OK (REGISTER)
Apply post test routine
| End device | | Test equipment | SUT is already registered | | | | → | REGISTER | | ← | 401 Unauthorized | | → | REGISTER 2 | | ← | 200 OK (REGISTER) | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SUT is already registered | | | | | | | | | | | | | | | | | | | | | | +| | → | REGISTER | | | | | | | | | | | | | | | | | | | | +| | ← | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | +| | → | REGISTER 2 | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|------------------------------------|-------------------|-----------------------|---------------------------|--|---|----------|---|------------------|---|----------|---|-------------------|-------------------------|--| +| TSS
Initial_registration | TP_101_019 | Reference
section 10.2.2 of [IETF
RFC 3261] | Selection expression
PICS 5.2/6 | | | | | | | | | | | | | | | +| Test purpose
Successful registration removing a Binding

Ensure that the SUT is able to deregister a particular Binding by sending a REGISTER request and the expires parameter for that Binding is set to '0' or the Expires header is set to '0'. | | | | | | | | | | | | | | | | | | +| SIP header values
REGISTER
Contact: sip:[any registered URI];expires=0
OR
Contact: *
Expires: 0 | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SUT is already registered
➔ REGISTER
⬅ 401 Unauthorized
➔ REGISTER
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | Test equipment | SUT is already registered | | ➔ | REGISTER | ⬅ | 401 Unauthorized | ➔ | REGISTER | ⬅ | 200 OK (REGISTER) | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | | | | | +| SUT is already registered | | | | | | | | | | | | | | | | | | +| ➔ | REGISTER | | | | | | | | | | | | | | | | | +| ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | +| ➔ | REGISTER | | | | | | | | | | | | | | | | | +| ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|------------------------------------|-------------------|-----------------------|---------------------------|--|---|----------|---|-------------------|-------------------------|--| +| TSS
Initial_registration | TP_101_020 | Reference
section 10.2.1 of [IETF
RFC 3261] | Selection expression
PICS 5.2/7 | | | | | | | | | | | +| Test purpose
The SUT gets its registered contacts

Ensure that the SUT, in order to get its registered contacts, sends a REGISTER request to its registrar without Contact header. | | | | | | | | | | | | | | +| SIP header values
REGISTER
[without Contact header] | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Make end device available
➔ REGISTER
⬅ 200 OK (REGISTER)
Apply post test routine
| | | | End device | Test equipment | Make end device available | | ➔ | REGISTER | ⬅ | 200 OK (REGISTER) | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | +| Make end device available | | | | | | | | | | | | | | +| ➔ | REGISTER | | | | | | | | | | | | | +| ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------|------------------------------------| +| TSS
Initial_registration | TP_101_021 | Reference
Annex A and section 17.1.2.2 of [IETF RFC 3261] | Selection expression
PICS 5.2/1 | +| Test purpose
REGISTER request is repeated if no response is received

Ensure that the SUT or the IUT, having sent a REGISTER request, repeats its request after timer E set to T1 value expires, if an unreliable transport is used. | | | | +| SIP header values | | | | +| Message flow
 sequenceDiagram     participant End device     participant Test equipment     Note over End device: Start timer E     End device->>Test equipment: REGISTER     Note over End device: Timeout timer E     End device->>Test equipment: REGISTER 

Apply post test routine

| | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------| +| TSS
Initial_registration | TP_101_022 | Reference
Annex A and section 17.1.3 of [IETF RFC 3261] | Selection expression
PICS 5.2/1 | +| Test purpose
REGISTER request is repeated if no response is received

Ensure that the SUT, having sent a REGISTER request twice, repeats its request after timer E set to the $MIN(2*T1,T2)$ value expires, if an unreliable transport is used. | | | | +| SIP header values | | | | +| Message flow
 sequenceDiagram     participant End device     participant Test equipment     Note over End device: Start timer E=T1     End device->>Test equipment: REGISTER     Note over End device: Timeout timer E     End device->>Test equipment: REGISTER     Note over End device: Start timer E=2*T1     Note over End device: Timeout timer E     End device->>Test equipment: REGISTER 

Apply post test routine

| | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------| +| TSS
Initial_registration | TP_101_023 | Reference
Annex A and section 17.1.3 of [IETF RFC 3261] | Selection expression
PICS 5.2/1 | +| Test purpose
REGISTER request is repeated if no response is received

Ensure that the SUT, having sent a REGISTER request three times, repeats its request after timer E set to the $MIN(4*T1,T2)$ value expires, If an unreliable transport is used. | | | | +| SIP header values | | | | + +| | | +|--------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| | → REGISTER | +| Start timer E= $T1$ | | +| Timeout timer E | | +| | → REGISTER | +| Start timer E= $2*T1$ | | +| Timeout timer E | | +| | → REGISTER | +| Start timer E= $4*T1$ | | +| Timeout timer E | | +| | → REGISTER | +| Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------------------|-----------------------------------------------|-------------------|-----------------------|--|------------|------------------------|--|--|------------|--|------------|--|------------|-----------------|--|--------------------------------|--| +| TSS
Initial_registration | TP_101_024 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression
PICS 5.2/2 and 5.2/12 | | | | | | | | | | | | | | | | | +|

Test purpose
The REGISTER is not repeated after timer F expires

Ensure that the SUT does not repeat a REGISTER request, after timer F set to 64*T1 expires, If an unreliable transport is used.

| | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | +|

Message flow

End device Test equipment
→ REGISTER
Start timer F=64*T1
→ REGISTER
→ REGISTER
→ REGISTER
Timeout timer F
Apply post test routine
| | | | End device | Test equipment | | → REGISTER | Start timer F= $64*T1$ | | | → REGISTER | | → REGISTER | | → REGISTER | Timeout timer F | | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | | | | | | | +| | → REGISTER | | | | | | | | | | | | | | | | | | | +| Start timer F= $64*T1$ | | | | | | | | | | | | | | | | | | | | +| | → REGISTER | | | | | | | | | | | | | | | | | | | +| | → REGISTER | | | | | | | | | | | | | | | | | | | +| | → REGISTER | | | | | | | | | | | | | | | | | | | +| Timeout timer F | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_025 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression | +|

Test purpose
REGISTER request in the Proceeding state is repeated if no response is received

Ensure that the SUT, when a REGISTER client transaction is in the Proceeding state, repeats its REGISTER request after timer E set to T1 value expires.

| | | | +| SIP header values | | | | + +![](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +| | | +|--------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| | → REGISTER | +| | ← 100 Trying | +| Start timer E=T1 | | +| Timeout timer E | | +| | → REGISTER | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|------------------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_026 | Reference
Annex A and
section 17.1.3 of [IETF
RFC 3261] | Selection expression | +|-----------------------------|------------|------------------------------------------------------------------|----------------------| + +**Test purpose** +*REGISTER request in the Proceeding state is repeated if no response is received* + +Ensure that the SUT, when a REGISTER client transaction is in the Proceeding state, repeats its REGISTER request after timer E set to T1 value expires. + +**SIP header values** + +![](4b87467ad9642943235f48f7d4b59449_img.jpg) + +| | | +|--------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| | → REGISTER | +| | ← 100 Trying | +| Start timer E=T1 | | +| Timeout timer E | | +| | → REGISTER | +| | ← 100 Trying | +| Start timer E=T2 | | +| Timeout timer E | | +| | → REGISTER | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|------------------------------------------------------------------|-------------------------------------| +| TSS
Initial_registration | TP_101_027 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression
PICS 5.2/12 | +|-----------------------------|------------|------------------------------------------------------------------|-------------------------------------| + +**Test purpose** +*REGISTER request in the Proceeding state is not repeated if no response is received* + +Ensure that the SUT, when a REGISTER client transaction is in the Proceeding state and REGISTER request have already been repeated in this state, repeats its REGISTER request after timer E set to T2 value expires. + +**SIP header values** + +![](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +| | | +|--------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| | → REGISTER | +| | ← 100 Trying | +| Start timer F=64*T1 | | +| | → REGISTER | +| | ← 100 Trying | +| | | +| | → REGISTER | +| | ← 100 Trying | +| Timeout timer F | | +| Apply post test routine | | + +| | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------|----------------------|-------------------|-----------------------|--|------------|--|-----------------|--|------------|--------------------------------|--| +| TSS
Initial_registration | TP_101_028 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression | | | | | | | | | | | +| Test purpose
Receipt of a 305 (Use Proxy) response to the unprotected REGISTER request | | | | | | | | | | | | | | +| Ensure that the SUT, on receipt of a 305 (Use Proxy) response to the unprotected REGISTER request, select a P-CSCF address from the address list, which is different from the previously used address, and perform the procedures for initial registration. | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | +| Message flow
End deviceTest equipment
→ REGISTER
← 305 Use Proxy
→ REGISTER
Apply post test routine
| | | | End device | Test equipment | | → REGISTER | | ← 305 Use Proxy | | → REGISTER | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | +| | → REGISTER | | | | | | | | | | | | | +| | ← 305 Use Proxy | | | | | | | | | | | | | +| | → REGISTER | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_029 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression | +| Test purpose
Receipt of a 423 (Interval Too Brief) response to the unprotected REGISTER request | | | | +| Ensure that the SUT, on receipt of a 423 (Interval Too Brief) response to the unprotected REGISTER request, send another REGISTER request populating the registration expiration interval value with an expiration timer of at least the value received in the Min-Expires header field of the 423 (Interval Too Brief) response. | | | | +| SIP header values | | | | +| 423:
Min-Expires:

INVITE2
Expires: | | | | + +| | | +|--------------------------------|------------------------| +| Message flow | | +| End device | Test equipment | +| → | REGISTER | +| ← | 423 Interval Too Brief | +| → | REGISTER2 | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|---------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_030 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression | +|-----------------------------|------------|---------------------------------------------------------|----------------------| + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Test purpose | | +| Receipt of a 408 (Request Timeout) response to the unprotected REGISTER request | | +| Ensure that the SUT, on receipt of a 408 (Request Timeout) response to the unprotected REGISTER request attempt to perform initial registration again. | | +| SIP header values | | +| Message flow | | +| End device | Test equipment | +| → | REGISTER | +| ← | 408 Request Timeout | +| → | REGISTER | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|---------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_031 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression | +|-----------------------------|------------|---------------------------------------------------------|----------------------| + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| Test purpose | | +| Receipt of a 500 (Server Internal Error) response to the unprotected REGISTER request | | +| Ensure that the SUT, on receipt of a 500 (Server Internal Error) response to the unprotected REGISTER request attempt to perform initial registration again. | | +| SIP header values | | +| Message flow | | +| End device | Test equipment | +| → | REGISTER | +| ← | 500 Server Internal Error | +| → | REGISTER2 | +| Apply post test routine | | + +| | | | | +|-----------------------------|------------|---------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_032 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression | +|-----------------------------|------------|---------------------------------------------------------|----------------------| + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Test purpose | | +| Receipt of a 504 (Server Time-Out) response to the unprotected REGISTER request | | +| Ensure that the SUT, on receipt of a 504 (Server Time-Out) response to the unprotected REGISTER request attempt to perform initial registration again. | | +| SIP header values | | + +| | | +|--------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| ➔ | REGISTER | +| ⬅ | 504 Server Time-Out | +| ➔ | REGISTER | +| Apply post test routine | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_033 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| Receipt of a 600 (Busy Everywhere) response to the unprotected REGISTER request | | | | +| Ensure that the SUT, on receipt of a 600 (Busy Everywhere) response to the unprotected REGISTER request attempt to perform initial registration again. | | | | +| SIP header values | | | | +| Message flow | | | | +| End device | Test equipment | | | +| ➔ | REGISTER | | | +| ⬅ | 600 Busy Everywhere | | | +| ➔ | REGISTER | | | +| Apply post test routine | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------------------|----------------------| +| TSS | TP_101_034 | Reference
Annex A and
section 17.1.3 of [IETF
RFC 3261] | Selection expression | +| Test purpose | | | | +| Receipt of a 403 (Forbidden) response to the unprotected REGISTER request | | | | +| Ensure that the SUT, on receipt of a 403 (Forbidden) response to the unprotected REGISTER request, considers the registration to have failed. | | | | +| SIP header values | | | | +| Message flow | | | | +| End device | Test equipment | | | +| ➔ | REGISTER | | | +| ⬅ | 403 Forbidden | | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|-----------------------------------|--|-------------------|--|-----------------------|--|--|---|----------|--|--|---|------------------|--|--|---|----------|--|--|---|-----------------|-------------------|--|-------|---------------|--|--|---|------------------|--|--|---|--------|--|--|---|---------------|-------------------|--|-------|---------------|--|--|---|-----------------------------------|--|--|---|-----------|--|--|---|------------------|--|--|---|--------|--|--|---|---------------| +| TSS
Initial_registration | TP_101_035 | Reference
subclause 5.1.1.3 of
[ETSI TS 124 229] | Selection expression
PICS VGW | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
Subscription to the registration-state event package

Ensure that the SUT, on receipt of a 200 OK REGISTER response, subscribes to the 'reg' event package. The SUT sends a SUBSCRIBE request to the resource to which the UE wants to be subscribed to.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIPheader values
SUBSCRIBE
Request URI: SIP URI which is the default public user identity used for subscription
From: [default public user identity used for subscription]
To: [default public user identity used for subscription]
Event: reg
Expires: 600000

200 OK SUBSCRIBE
Expires: [any value <=600000]

NOTIFY
Event: reg
Subscription-State: active; expires=<any value>

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

End device Test equipment
➔ REGISTER
⬅ 401 Unauthorized
➔ REGISTER
⬅ 200 OK REGISTER

CASE A

➔

SUBSCRIBE
⬅ 2xx OK SUBSCRIBE
⬅ NOTIFY
➔ 200 OK NOTIFY

CASE B

➔

SUBSCRIBE
⬅ 407 Proxy Authentication Required
➔ SUBSCRIBE
⬅ 2xx OK SUBSCRIBE
⬅ NOTIFY
➔ 200 OK NOTIFY

Apply post test routine

| | | | | End device | | Test equipment | | | ➔ | REGISTER | | | ⬅ | 401 Unauthorized | | | ➔ | REGISTER | | | ⬅ | 200 OK REGISTER |
CASE A | |
➔ |
SUBSCRIBE | | | ⬅ | 2xx OK SUBSCRIBE | | | ⬅ | NOTIFY | | | ➔ | 200 OK NOTIFY |
CASE B | |
➔ |
SUBSCRIBE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | SUBSCRIBE | | | ⬅ | 2xx OK SUBSCRIBE | | | ⬅ | NOTIFY | | | ➔ | 200 OK NOTIFY | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE A | |
➔ |
SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 2xx OK SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | |
➔ |
SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 2xx OK SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|----------------------|-------------------|--|-----------------------|--|----------------------------------|--|---------------|------------------------------------------------------------------|--|---------------|------------------------------------------------------------------------------------------------------------------------|--|--|--------------------------------|--| +| TSS
Initial_registration | TP_101_036 | Reference
subclause 5.1.1.3 of
[ETSI TS124 229] | Selection expression | | | | | | | | | | | | | | | | +| Test purpose
Re-subscription to the registration-state event package | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT, after the registration state event is subscribed and the expires time is reached, starts the re-subscription procedure. The SUT sends a new SUBSCRIPTION request to re-subscribe the registration state event. | | | | | | | | | | | | | | | | | | | +| SIPheader values
SUBSCRIBE
Request URI: SIP URI which is the default public user identity used for subscription
From: [default public user identity used for subscription]
To: [default public user identity used for subscription]
Event: reg
Expires: 600000

200 OK SUBSCRIBE
Expires: [any value <=600000] | | | | | | | | | | | | | | | | | | | +| NOTIFY
Event: reg
Subscription-State : active; expires= | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SUT is already registered
CASE A → SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY
CASE B → SUBSCRIBE
← 407 Proxy Authentication Required
→ SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY
Apply post test routine
| | | | End device | | Test equipment | | SUT is already registered | | CASE A | → SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | CASE B | → SUBSCRIBE
← 407 Proxy Authentication Required
→ SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | | Apply post test routine | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | +| | SUT is already registered | | | | | | | | | | | | | | | | | | +| CASE A | → SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | | | | | | | | | | | | | | | | | +| CASE B | → SUBSCRIBE
← 407 Proxy Authentication Required
→ SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------|----------------------| +| TSS
Initial_registration | TP_101_037 | Reference
subclause 5.1.1.5A and
5.1.1.4.1of
[ETSI TS124 229] | Selection expression | +| Test purpose
Network-initiated re-authentication | | | | +| Ensure that the SUT, upon receipt of a NOTIFY to a subscribed registration state event, starts the re-authentication procedures. | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|----------------------------------|--|---|--------|---|---------------|--|--|---|----------|---|------------------|---|----------|---|-------------------|--------------------------------|--| +| SIPheader values
NOTIFY
Event: reg
Subscription-State : active
Contact: ;event= shortened;expires=[any value] | | | | | | | | | | | | | | | | | | | | | +| REGISTER
Request-line: sip:[hostpart=domain of location service]
Call-ID [any value]
Cseq x REGISTER
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 600000 | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SUT is already registered
← NOTIFY
→ 200 OK NOTIFY
 
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER)
Apply post test routine
| End device | Test equipment | SUT is already registered | | ← | NOTIFY | → | 200 OK NOTIFY | | | → | REGISTER | ← | 401 Unauthorized | → | REGISTER | ← | 200 OK (REGISTER) | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | | | | | | | | +| SUT is already registered | | | | | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | | | | | +| → | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | +| → | REGISTER | | | | | | | | | | | | | | | | | | | | +| ← | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | +| → | REGISTER | | | | | | | | | | | | | | | | | | | | +| ← | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.1.2 User-initiated re-registration and registration of an additional public user identity + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------| +| TSS
User-initiated_re-registration | TP_102_001 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression | +| Test purpose
User initiated reregistration

Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity. | | | | +| SIP: Header values
REGISTER 1
Request-line: sip:[hostpart=domain of location service]
Call-ID [any value]
Cseq x REGISTER
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 600000 | | | | + +![](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +| | | +|----------------------------------------------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| SUT is already registered | | +| The SUT has determined that a continued registration is not required | | +| ➔ REGISTER | | +| ⬅ 401 Unauthorized | | +| ➔ REGISTER | | +| ⬅ 200 OK REGISTER | | +| Apply post test routine | | + +| | | | | +|---------------------------------------|------------|---------------------------------------------------------|------------------------------------| +| TSS
User-initiated_re-registration | TP_102_002 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/3 | +|---------------------------------------|------------|---------------------------------------------------------|------------------------------------| + +**Test purpose** +*User initiated reregistration – GRUU supported* + +Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity. + +**SIPheader values** +**REGISTER 1** + Supported: path,gruu + +![](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +| | | +|----------------------------------------------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| SUT is already registered | | +| The SUT has determined that a continued registration is not required | | +| ➔ REGISTER | | +| ⬅ 401 Unauthorized | | +| ➔ REGISTER | | +| ⬅ 200 OK REGISTER | | +| Apply post test routine | | + +| | | | | +|---------------------------------------|------------|---------------------------------------------------------|------------------------------------| +| TSS
User-initiated_re-registration | TP_102_003 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 | +|---------------------------------------|------------|---------------------------------------------------------|------------------------------------| + +**Test purpose** +*User initiated reregistration - multiple registrations is supported* + +Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity. + +**SIPheader values** +**REGISTER 1** + Supported: path,outbound + +![](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +| | | +|----------------------------------------------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| SUT is already registered | | +| The SUT has determined that a continued registration is not required | | +| ➔ REGISTER | | +| ⬅ 401 Unauthorized | | +| ➔ REGISTER | | +| ⬅ 200 OK REGISTER | | +| Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------|----------------------------------------------|---------------------|--|-------------------|-----------------------|----------------------------------|--|----------------------------------------------------------------------|--|------------|--|--------------------|--|------------|--|-------------------|--|--------------------------------|--| +| TSS
User-initiated_re-registration | TP_102_004 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 and 5.2/5 | | | | | | | | | | | | | | | | | | | +| Test purpose
User initiated reregistration - functions of an external attached network is supported | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity. | | | | | | | | | | | | | | | | | | | | | | +| SIPheader values
REGISTER 1
Require: gin | | | | | | | | | | | | | | | | | | | | | | +|
Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a continued registration is not required
➔ REGISTER
⬅ 401 Unauthorized
➔ REGISTER
⬅ 200 OK REGISTER
Apply post test routine
| | | | Message flow | | End device | Test equipment | SUT is already registered | | The SUT has determined that a continued registration is not required | | ➔ REGISTER | | ⬅ 401 Unauthorized | | ➔ REGISTER | | ⬅ 200 OK REGISTER | | Apply post test routine | | +| Message flow | | | | | | | | | | | | | | | | | | | | | | +| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | +| SUT is already registered | | | | | | | | | | | | | | | | | | | | | | +| The SUT has determined that a continued registration is not required | | | | | | | | | | | | | | | | | | | | | | +| ➔ REGISTER | | | | | | | | | | | | | | | | | | | | | | +| ⬅ 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | +| ➔ REGISTER | | | | | | | | | | | | | | | | | | | | | | +| ⬅ 200 OK REGISTER | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.1.3 User-initiated deregistration + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------| +| TSS
User-initiated_deregistration | TP_103_001 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression | +| Test purpose
User initiated deregistration – general procedure | | | | +| Ensure that the SUT, after the SUT is registered, starts the deregistration procedure of a previously registered public user identity. | | | | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| SIPheader values
REGISTER 1
Request-line: sip:[hostpart=domain of location service]
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 0 | | +| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------| +| TSS
User-initiated_deregistration | TP_103_002 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/3 | +| Test purpose
User initiated deregistration – GRUU supported

Ensure that the SUT, after the UE is registered, starts the deregistration procedure of a previously registered public user identity when GRUU is supported. | | | | +| SIPheader values
REGISTER 1
Supported: path,gruu
Expires: 0 | | | | +| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------| +| TSS
User-initiated_deregistration | TP_103_003 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 | +| Test purpose
User initiated deregistration - multiple registrations is supported

Ensure that the SUT, after the UE is registered, starts the deregistration procedure of a previously registered public user identity when multiple registration is supported. | | | | +| SIPheader values
REGISTER 1
Supported: path,outbound
Expires: 0 | | | | +| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------------------------------| +| TSS
User-initiated_deregistration | TP_103_004 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 and 5.2/5 | +| Test purpose
User initiated deregistration - functions of an external attached network is supported

Ensure that the SUT, after the UE is registered, starts the deregistration procedure of a previously registered public user identity when external attached network is performed. | | | | +| SIPheader values
REGISTER 1
Require: gin
Expires: 0 | | | | +| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| | | | + +#### 7.2.1.4 Network-initiated deregistration + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------|----------------------|-------------------|--|-----------------------|--|----------------------------------|--|--|----------|--|--|-----------------|--|--|----------------|--|--|--------------------|--|--|------------|--|--|---------------------|--|--|--------------------------------|--| +| TSS
Network-initiated_deregistration | TP_104_001 | Reference
subclause 5.1.1.7 of
[ETSI TS124 229] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Network-initiated deregistration

Ensure that the SUT, upon receipt of a NOTIFY to a subscribed registration state event, starts the deregistration procedures. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIPheader values
NOTIFY
Event: reg
Subscription-State: terminated
Contact: ;event= shortened;expires=[any value] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REGISTER 1
Request-line: sip:[hostpart=domain of location service]
Call-ID [any value]
Cseq x REGISTER
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SUT is already registered
← NOTIFY
→ 200 OK NOTIFY

→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER)
Apply post test routine
| | | | End device | | Test equipment | | SUT is already registered | | | ← NOTIFY | | | → 200 OK NOTIFY | | |
→ REGISTER | | | ← 401 Unauthorized | | | → REGISTER | | | ← 200 OK (REGISTER) | | | Apply post test routine | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | SUT is already registered | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| |
→ REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.1.5 Subscription and notification + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|------------------------------------| +| TSS
Subscription_and_notification | TP_105_001 | Reference
subclause 5.3.1 of
[ETSI TS183 043] | Selection expression
PICS 5.3/1 | +| Test purpose
Subscription to the User Agent Profile Delivery

Ensure that the SUT sends a SUBSCRIBE to the network to subscribe to the User Agent Profile Delivery. The SUT receives a dial-tone-management XML element. | | | | +| | | | | + +| | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|----------------------------------|--|---|-----------|---|--------------------|--|--|---|--------|---|-----------------|--------------------------------|--| +| SIPheader values
SUBSCRIBE
Event: ua-profile;profile-type=user ; vendor="[any reasonable value]";model="[any reasonable value]";version="[any reasonable value]" | | | | | | | | | | | | | | | | | +| NOTIFY
Event: ua-profile;profile-type=user ; vendor="[any reasonable value]";model="[any reasonable value]";version="[any reasonable value]"


standard-dial-tone (optional)
special-condition-tone (optional)
message-waiting-tone (optional)
| | | | | | | | | | | | | | | | | +| Message flow
End deviceTest equipment
SUT is already registered
→SUBSCRIBE
←200 OK (SUBSCRIBE)
←NOTIFY
→200 OK (NOTIFY)
Apply post test routine
| End device | Test equipment | SUT is already registered | | → | SUBSCRIBE | ← | 200 OK (SUBSCRIBE) | | | ← | NOTIFY | → | 200 OK (NOTIFY) | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | | | | +| SUT is already registered | | | | | | | | | | | | | | | | | +| → | SUBSCRIBE | | | | | | | | | | | | | | | | +| ← | 200 OK (SUBSCRIBE) | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | +| ← | NOTIFY | | | | | | | | | | | | | | | | +| → | 200 OK (NOTIFY) | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|------------------------------------| +| TSS
Subscription_and_notification | TP_105_002 | Reference
subclause 5.3.1 of
[ETSI TS183 043] | Selection expression
PICS 5.3/1 | +| Test purpose
Subscription to the Message waiting indication

Ensure that the SUT sends a SUBSCRIBE to the network to subscribe to the Message Waiting indication service. The SUT receives in a NOTIFY request a MIME body with new reports about waiting messages. | | | | +| SIPheader values
SUBSCRIBE
Accept: application/simple-message-summary
Expires:
Event: message-summary | | | | +| NOTIFY
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary

MIME body:
Messages-Waiting: yes
Message-Account: sip:served_user@Server
Voice-Message: 4/1 (2/0)
Video-Message: 3/1 (1/0)
Fax-Message: 2/1 (0/1) | | | | + +![](f57c7b37d7a05a99618104f390089f03_img.jpg) + +| | | +|--------------------------------|-----------------------| +| Message flow | | +| End device | Test equipment | +| SUT is already registered | | +| → | SUBSCRIBE | +| ← | 200 OK (SUBSCRIBE) | +| ← | NOTIFY | +| → | 200 OK (NOTIFY) | +| Apply post test routine | | + +| | | | | +|--------------------------------------|------------|-----------------------------------------------------|------------------------------------| +| TSS
Subscription_and_notification | TP_105_003 | Reference
subclause 5.3.1 of
[ETSI TS183 043] | Selection expression
PICS 5.3/1 | +|--------------------------------------|------------|-----------------------------------------------------|------------------------------------| + +**Test purpose** +*Subscription to the Message waiting indication rejected with 503* + +Ensure that the SUT sends a SUBSCRIBE to the network to subscribe to the Message Waiting indication service. The SUT receives a 503 (Service Unavailable) response to a SUBSCRIBE request containing a Retry-After header. The SUT does not automatically reattempt the request until after the period indicated by the Retry-After header contents + +**SIPheader values** +**SUBSCRIBE** + Accept: application/simple-message-summary + Expires:
+ Event: message-summary + +**503** + Retry-After: 20 + +![](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +| | | +|-------------------------------------------------------|-------------------------| +| Message flow | | +| End device | Test equipment | +| SUT is already registered | | +| → | SUBSCRIBE | +| ← | 200 OK (SUBSCRIBE) | +| ← | 503 Service Unavailable | +| Wait for the time indicated in the Retry-After header | | +| → | SUBSCRIBE | +| ← | 200 OK (SUBSCRIBE) | +| Apply post test routine | | + +### 7.2.2 Call initiation – UE-originating case + +#### 7.2.2.1 Establishment of an early dialogue + +##### 7.2.2.1.1 SIP basic procedures + +| | | | | +|------------------------------------------------|------------|--------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_001 | Reference
section 8.1.1 of
[IETF RFC 3261] | Selection expression | +|------------------------------------------------|------------|--------------------------------------------------|----------------------| + +**Test purpose** +*Sending of INVITE request containing all mandatory headers* + +Ensure that the SUT is able to send an INVITE request containing all mandatory SIP headers: + +| | | +|-------------------------------------------------------------------------------------------------------|--------------------------| +| SIP Header values
INVITE
To
From
CSeq
Call-ID
Max-Forwards
Contact
Via | | +| Message flow | | +| End device | Test equipment | +| Interworking POTS
Off hook
Dial number | | +| | → INVITE
← 100 Trying | +| ISDN interworking
SETUP | | +| | → INVITE
← 100 Trying | +| Apply post test routine | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_002 | Reference
section 8.1.1. of
[IETF RFC 3261] | Selection expression | +| Test purpose
The Request line is set to the same URI value of the To header | | | | +| Ensure that the IUT is able to establish a session and the Request line URI is set to the same value as the To header URI | | | | +| SIP header values
INVITE sip: [Request URI] SIP/2.0
To: < sip: [Request URI]> | | | | +| Message flow | | | | +| End device | Test equipment | | | +| Interworking POTS
Off hook
Dial number | | | | +| | → INVITE
← 100 Trying | | | +| ISDN interworking
SETUP | | | | +| | → INVITE
← 100 Trying | | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|------------|------------------------------|--|--|--|-------|--|---|--------|--|--|---|------------|--------------------------------|--|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_003 | Reference
section 8.1.1.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The To header does not contain a 'tag' parameter

Ensure that the IUT is able to establish a session and the 'To' header in the INVITE request does not contain the 'tag' parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
To: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying

ISDN interworking
SETUP ➔ INVITE
⬅ 100 Trying
Apply post test routine
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 100 Trying |
ISDN interworking | | | | SETUP | | ➔ | INVITE | | | ⬅ | 100 Trying | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|------------|------------------------------|--|--|--|-------|--|---|--------|--|--|---|------------|--------------------------------|--|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_004 | Reference
section 8.1.1.3 of [IETF RFC
3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The From header contains a 'tag' parameter

Ensure that the IUT is able to establish a session and the 'From' header in the INVITE request contains the 'tag' parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
From: ;tag=[any value] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying

ISDN interworking
SETUP ➔ INVITE
⬅ 100 Trying
Apply post test routine
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 100 Trying |
ISDN interworking | | | | SETUP | | ➔ | INVITE | | | ⬅ | 100 Trying | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_005 | Reference
section 8.1.1.5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|--|---|------------| +| Test purpose
The CSeq header contains the method INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE includes a CSeq header and the method parameter is set to 'INVITE'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
CSeq: INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying

ISDN interworking
SETUP ➔ INVITE
⬅ 100 Trying

Apply post test routine

| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying |
ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_006 | Reference
section 8.1.1.6 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|--|---|------------| +| Test purpose
Max-Forwards initial value | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE contains a Max-Forwards header set to the initial value '70' | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Max-Forwards: 70 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying

ISDN interworking
SETUP ➔ INVITE
⬅ 100 Trying

Apply post test routine

| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying |
ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_007 | Reference
section 8.1.1.7 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Coding of Via header in the INVITE

Ensure that the IUT is able to establish a session and the INVITE contains a Via header with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter set to a value beginning with "z9hG4bK". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Via:SIP 2.0 ;branch= z9hG4bK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying
ISDN interworking
SETUP ➔ INVITE
⬅ 100 Trying
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_008 | Reference
section 13.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Allow and Supported header in the INVITE

Ensure that the IUT is able to establish a session and the INVITE contains the Allow and Supported header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Allow:
Supported: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying
ISDN interworking
SETUP ➔ INVITE
⬅ 100 Trying
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|-------------------|---|------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_009 | Reference
sections 8, 8.1.3.2, 13.2.2.1
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
100 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Trying (100 Trying) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying
ISDN interworking
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|----------------------|--------------------------|--|--|-------|---|--------|-----------------|---|----------------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_010 | Reference
sections 8, 8.1.3.2, 13.2.2.1
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
183 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Session Progress (183 Session Progress) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 183 Session Progress
ISDN interworking
SETUP ➔ INVITE
CALL PROCEEDING ⬅ 183 Session Progress
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 183 Session Progress | ISDN interworking | | | SETUP | ➔ | INVITE | CALL PROCEEDING | ⬅ | 183 Session Progress | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CALL PROCEEDING | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|--------------------------|--|--|-------|---|--------|----------|---|-------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_011 | Reference
sections 8, 8.1.3.2, 13.2.2.1,
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
180 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Ringing (180 Ringing) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 180 Ringing
ISDN interworking
SETUP ➔ INVITE
ALERTING ⬅ 180 Ringing

Apply post test routine

| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 180 Ringing | ISDN interworking | | | SETUP | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|--------------------------|--|--|-------|---|--------|-------------------|---|-------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_012 | Reference
sections 8, 8.1.3.2, 13.2.2.1
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
198 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Unknown (198 Unknown) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 198 Unknown
ISDN interworking
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 198 Unknown

Apply post test routine

| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 198 Unknown | ISDN interworking | | | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 198 Unknown | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 198 Unknown | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 198 Unknown | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|-------------------|---|------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_013 | Reference
sections 8, 8.1.3.2, 13.2.2.1 and Figure 5 [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
100 received, the client remains the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Proceeding state, on receipt of a Trying (100 Trying) response stays in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 100 Trying

ISDN interworking
SETUP → INVITE
SETUP ACKNOWLEDGE ← 100 Trying
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 100 Trying |
ISDN interworking | | | SETUP | → | INVITE | SETUP ACKNOWLEDGE | ← | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_014 | Reference
section 20.14 and 13.2.1 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Content-Length header and SDP in the initial INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE request contains the Content-Length header set to the size of the body in the message that contains the session description. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE
Content-Length: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SDP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 100 Trying

ISDN interworking
SETUP → INVITE
← 100 Trying
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 100 Trying |
ISDN interworking | | | SETUP | → | INVITE | | ← | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_015 | Reference
section 20.15 and 13.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Content-Type header and SDP in the initial INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE request contains the Content-Type header in the message that contains the session description. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Content-Type: application/sdp

SDP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number➔INVITE
⬅100 Trying
ISDN interworking
SETUP➔INVITE
⬅100 Trying
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_016 | Reference
section 20.14 and 13.2.1 of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Content-Length header and SDP in the initial INVITE and TCP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE request contains the Content-Length header set to the size of the body in the message that contains the session description and a reliable transport (TCP) is used. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Content-Type: application/sdp

SDP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number➔INVITE
⬅100 Trying
ISDN interworking
SETUP➔INVITE
⬅100 Trying
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------|-------------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|----------|--|--|---|------------------|--|--|---|-----|--|--|---|----------|------------------------------|--|--|--|-------|--|---|----------|--|--|---|------------------|--|--|---|-----|--|--|---|----------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_017 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression on | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The CSeq in the repeated INVITE is incremented | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that the IUT is able to establish a session and the INVITE request, on receipt of an Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its INVITE request with an Authorization header and with an incremented Cseq value.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1:
CSeq: INVITE
INVITE2:
Authorization:
CSeq: INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE 1
⬅ 401 Unauthorized
➔ ACK
➔ INVITE 2

ISDN interworking
SETUP ➔ INVITE 1
⬅ 401 Unauthorized
➔ ACK
➔ INVITE 2

Apply post test routine

| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE 1 | | | ⬅ | 401 Unauthorized | | | ➔ | ACK | | | ➔ | INVITE 2 |
ISDN interworking | | | | SETUP | | ➔ | INVITE 1 | | | ⬅ | 401 Unauthorized | | | ➔ | ACK | | | ➔ | INVITE 2 | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | ➔ | INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_018 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Authorization header present in the repeated INVITE | | | | +|

Ensure that the IUT is able to establish a session and the INVITE request, on receipt of a 401 Unauthorized response including a WWW-Authenticate header, repeats its INVITE request with an Authorization header including proper values for username, realm nonce, digest-uri and response HTTP parameters.

| | | | +| SIP header values
INVITE2:
Authorization: Digest username="", realm="",nonce="",uri="", qop=auth, cnonce="",response="",algorithm= | | | | + +| Message flow | | | +|--------------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | ➔ | INVITE1 | +| | ⬅ | 401 Unauthorized | +| | ➔ | ACK | +| | ➔ | INVITE2 | +|
ISDN interworking | | | +| SETUP | ➔ | INVITE | +| | ⬅ | 401 Unauthorized | +| | ➔ | ACK | +| | ➔ | INVITE2 | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_019 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| The CSeq in the repeated INVITE is incremented | | | | +| Ensure that the IUT is able to establish a session and the INVITE request, on receipt of a 407 Proxy Authentication Required response including a Proxy-Authenticate header, repeats its INVITE request with an Proxy-Authorization header and with an incremented Cseq value. | | | | +| SIP header values | | | | +| INVITE1:
CSeq: INVITE | | | | +| INVITE2:
Proxy-Authenticate:
CSeq: INVITE | | | | +| Message flow | | | | +| | End device | Test equipment | | +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | ➔ | INVITE | | +| | ⬅ | 407 Proxy Authentication Required | | +| | ➔ | ACK | | +| | ➔ | INVITE2 | | +|
ISDN interworking | | | | +| SETUP | ➔ | INVITE | | +| | ⬅ | 407 Proxy Authentication Required | | +| | ➔ | ACK | | +| | ➔ | INVITE2 | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|-----------------------------------|-------------------|--|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|---------|--------------------------|--|--|--|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|---------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_020 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Proxy-Authorization header present in the repeated INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT is able to establish a session and the INVITE request, on receipt of an 407 Proxy Authentication Required response including a Proxy-Authenticate header, repeats its INVITE request with an Proxy-Authorization header including proper values for username, realm nonce, digest-uri and response HTTP parameters. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE2:
Proxy-Authorization: Digest username=""=" , realm=""=",nonce=""=",uri=""=", qop=auth, cnonce=""=",response=""=",algorithm= | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE2
ISDN interworking
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE2

Apply post test routine

| | | | End device | | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE2 | ISDN interworking | | | | SETUP | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE2 | +| End device | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_021 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression | +| Test purpose
Accept header with support of SDP in the initial INVITE | | | | +| Ensure that the IUT is able to generate an initial INVITE request, the UE shall include the Accept header field with "application/sdp". | | | | +| SIP header values
INVITE2:
Accept: < application/sdp > | | | | + +| Message flow | | +|--------------------------------|-----------------------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | +| ISDN interworking | | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | +| Apply post test routine | | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------------------------|-------------------------------------|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_022 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 | | | +| Test purpose
Precondition support in the initial INVITE | | | | | | +| Ensure that the IUT is able to generating an initial INVITE request with indication of support of resource reservation, the SUT shall include the Support header field with "precondition" and "100rel". | | | | | | +| SIP header values | | | | | | +| INVITE2:
Supported: precondition,100rel | | | | | | +| SDP
.
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory/optional local sendrecv
a=des:qos mandatory/optional remote sendrecv | | | | | | +| Message flow | | | | | | +| End device | | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | | | | | +| ISDN interworking | | | | | | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | | | | | +| Apply post test routine | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|-------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_023 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 | +|

Test purpose
Successful resource reservation procedure

Ensure that the IUT is able to complete the resource reservation procedure. The (reliable) 183 contains in the SDP the instruction to reserve the quality of service on the SUT side. The SUT indicates that resource is reserved in the UPDATE request and the remote side confirms the resource reservation in the 200 OK UPDATE.

SIP header values
INVITE2:
    Supported: precondition,100rel

SDP a=curr:qos local none
    a=curr:qos remote none
    a=des:qos mandatory/optional local sendrecv
    a=des:qos mandatory/optional remote sendrecv

183:
Require: precondition,100rel
SDP a=curr:qos local none
    a=curr:qos remote none
    a=des:qos mandatory/optional local sendrecv
    a=des:qos mandatory/optional remote sendrecv
    a=conf:qos remote sendrecv

UPDATE
SDP a=curr:qos local sendrecv
    a=curr:qos remote none
    a=des:qos mandatory/optional local sendrecv
    a=des:qos mandatory/optional remote sendrecv

200 OK UPDATE
SDP a=curr:qos local sendrecv
    a=curr:qos remote sendrecv
    a=des:qos mandatory/optional local sendrecv
    a=des:qos mandatory/optional remote sendrecv

| | | | + +![](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +| Message flow | | +|--------------------------------|-------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | 183 Session progress | +| | PRACK | +| | 200 OK PRACK | +| | UPDATE | +| | 200 OK UPDATE | +| ISDN interworking | | +| SETUP | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | 183 Session progress | +| | PRACK | +| | 200 OK PRACK | +| | UPDATE | +| | 200 OK UPDATE | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|-------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_024 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 | +| Test purpose
Successful resource reservation procedure

Ensure that the IUT upon receiving a 421 (Extension Required) response to an initial INVITE request in which the precondition mechanism was not used, including the "precondition" option-tag in the Require header field, the SUT sends a new INVITE request and the Supported header contains the precondition option tag. | | | | + +###### **SIP header values** + +INVITE3: + +Supported: precondition,100rel + +SDP a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv + +183: + +Require: precondition,100rel + +SDP a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv +a=conf:qos remote sendrecv + +UPDATE/PRACK + +SDP a=curr:qos local sendrecv +a=curr:qos remote none +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv + +200 OK UPDATE/200 OK PRACK + +SDP a=curr:qos local sendrecv +a=curr:qos remote sendrecv +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv + +| Message flow | | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 421 Extension Required
→ ACK
→ INVITE3
← 183 Session progress
→ PRACK
← 200 OK PRACK
→ UPDATE
← 200 OK UPDATE | +| ISDN interworking | | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 421 Extension Required
→ ACK
→ INVITE3
← 183 Session progress
→ PRACK
← 200 OK PRACK
→ UPDATE
← 200 OK UPDATE | +| Apply post test routine | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|-------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_025 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 | +| Test purpose
SUT wishes to receive early media authorization indications | | | | +| Ensure that the IUT, if it wishes to receive early media authorization indications, the SUT inserts the P-Early-Media header field with the "supported" parameter to the INVITE request. | | | | +| SIP header values
INVITE2:
P-Early-Media: supported | | | | + +| Message flow | | +|--------------------------------|-----------------------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | +| ISDN interworking | | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | +| Apply post test routine | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------|-------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_026 | Reference
section 4 of [IETF RFC 3262] | Selection expression
PICS 5.2/15 | +| Test purpose
SUT supports the reliable provisional response procedure | | | | +|

Ensure that the IUT supports the reliable provisional response procedure, the "supported" header set to '100rel' is present in the INVITE request.

Upon a 18x provisional response containing a Require header set to '100rel' and an RSeq header, the SUT sends a PRACK request containing the RAck header. The response-num is equal to the value in the received RSeq header. The CSeq-num is equal to the CSeq value in the sent INVITE. The Method parameter is set to 'INVITE'.

| | | | +| SIP header values
INVITE2:
Supported: 100rel
CSeq: 2 INVITE

183:
Require: 100rel
RSeq: 3

PRACK
RAck: 3 2 INVITE | | | | + +| Message flow | | +|--------------------------------|-----------------------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | +| CASE A | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) | +| CASE B | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) | +| ISDN interworking | | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | +| CASE A | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) | +| CASE B | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) | +| Apply post test routine | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_027 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
Section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT presents received early media to the user. 183 received, no P-Early-Media header present.

Ensure that the IUT upon receiving a 183 Session Progress provisional response without a P-Early-Media header field and SDP answer is received, the SUT presents the received early media to the user. Forward early media is not gated. | | | | + +**SIP header values** + INVITE2: + P-Early-Media: supported + SDP offer + + 183: + SDP answer + +![](a2251e3bbfcd726b68cc50b091e53b02_img.jpg) + +| Message flow | | | +|--------------------------------|------------|-----------------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE2 | +| | ← | 183 Session Progress | +| Media | ← | Media | +| Media | → | | +| ISDN interworking | | | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE2 | +| | ← | 183 Session Progress | +| Media | ← | Media | +| Media | → | | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_028 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT presents received early media to the user. 180 received, no P-Early-Media header present. | | | | +| Ensure that the IUT upon receiving a 180 Ringing provisional response without a P-Early-Media header field and an SDP answer is received, the SUT presents the received early media to the user. Forward early media is not gated. | | | | +| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer

183:
SDP answer | | | | + +![](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +| Message flow | | | +|--------------------------------|------------|-----------------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE2 | +| | ← | 183 Session Progress | +| Media | ← | Media | +| Media | → | | +| ISDN interworking | | | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE2 | +| | ← | 183 Session Progress | +| Media | ← | Media | +| Media | → | | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_029 | Reference
clause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT presents received early media to the user. 183 received, P-Early-Media header present.

Ensure that the IUT upon receiving a 180 Ringing provisional response with a P-Early-Media header field indicating authorized early media and SDP answer is received, the SUT presents the received early media to the user. In case of P-Early-Media sendrecv, early media generated by the user is presented to the network. | | | | + +**SIP header values** + +INVITE2: +P-Early-Media: supported +SDP offer + +180: +P-Early-Media: [sendonly]/[sendrecv] +SDP answer + +![](c0b9e5fc63e19306394e0d4249da62cd_img.jpg) + +| Message flow | | | +|--------------------------------|------------|-----------------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE2 | +| | ← | 180 Ringing | +| CASE A sendonly | | | +| Media | ← | Media | +| Media | → | | +| CASE A sendrecv | | | +| Media | ← | Media | +| Media | → | Media | +| ISDN interworking | | | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE2 | +| | ← | 180 Ringing | +| CASE A sendonly | | | +| Media | ← | Media | +| Media | → | | +| CASE A sendrecv | | | +| Media | ← | Media | +| Media | → | Media | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_030 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT presents received early media to the user. 183 received, P-Early-Media header present.

Ensure that the IUT upon receiving a 183 Session Progress provisional response with a P-Early-Media header field indicating authorized early media and SDP answer is received, the SUT presents the received early media to the user. In case of P-Early-Media sendrecv, early media generated by the user is presented to the network. | | | | + +###### **SIP header values** + +INVITE2: + +P-Early-Media: supported + +SDP offer + +183: + +P-Early-Media: [sendonly]/[sendrecv] + +SDP answer + +###### **Message flow** + +**End device** + +**Test equipment** + +###### **Interworking POTS** + +Off hook + +Dial number + +→ INVITE +← 407 Proxy Authentication Required +→ ACK +→ INVITE2 +← 183 Session Progress + +###### **CASE A sendonly** + +Media + +Media + +← Media +→ + +###### **CASE A sendrecv** + +Media + +Media + +← Media +→ Media + +###### **ISDN interworking** + +SETUP + +→ INVITE +← 407 Proxy Authentication Required +→ ACK +→ INVITE2 +← 183 Session Progress + +###### **CASE A sendonly** + +Media + +Media + +← Media +→ + +###### **CASE A sendrecv** + +Media + +Media + +← Media +→ Media + +**Apply post test routine** + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_031 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 [IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT does not present early media to the user. 183 received, no P-Early-Media header present.

Ensure that the IUT upon receiving a 183 Session Progress provisional response without receipt of a P-Early-Media header field, the SUT does not present early media to the user if no RTP is received from the network. Forward early media is not gated. | | | | + + + +| | | +|--------------------------|--| +| SIP header values | | +| INVITE2: | | +| P-Early-Media: supported | | +| SDP offer | | +| 183: | | +| SDP answer yes/no | | + + + +| | | +|--------------------------------|-------------------------------------| +| Message flow | | +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | ← 183 Session Progress | +| ISDN interworking | | +| SETUP | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | ← 183 Session Progress | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_032 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT does not present early media to the user. 183 received, P-Early-Media header present.

Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received, value sendonly or sendrecv, the SUT does not present early media to the user if no RTP is received from the network. Forward early media is not gated. | | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| +| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer

183:
P-Early-Media: [sendonly]/[sendrecv]
SDP answer yes/no | | +| Message flow | | +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | ➔     INVITE | +| | ⬅     407 Proxy Authentication Required | +| | ➔     ACK | +| | ➔     INVITE2 | +| | ⬅     183 Session Progress | +|
ISDN interworking | | +| SETUP | ➔     INVITE | +| | ⬅     407 Proxy Authentication Required | +| | ➔     ACK | +| | ➔     INVITE2 | +| | ⬅     183 Session Progress | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_033 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT does not present early media to the user. 183 received, P-Early-Media header present. | | | | +|

Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received, value inactive or recvonly, the SUT does not present early media to the user. Forward early media is not gated.

| | | | +| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer

183:
P-Early-Media: [sendonly]/[sendrecv]
SDP answer yes/no | | | | + +| Message flow | | +|--------------------------------|-------------------------------------------------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress | +| ISDN interworking | | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress | +| Apply post test routine | | + +| | | | | +|------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_034 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +|------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
SUT local ring back tone is presented to the user. 183 received, P-Early-Media header not present.

Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is not received, the SUT play ringing tones for the caller, indicating that the callee is being alerted. Forward early media is not gated. | +| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer

183:
SDP answer yes/no | + +| Message flow | | +|--------------------------------|-------------------------------------------------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress | +| ISDN interworking | | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_035 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT local ring back tone is presented to the user. 183 received, P-Early-Media header value sendonly or sendrecv present.

Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received value sendonly or sendrecv, the SUT plays ringing tones for the caller, indicating that the callee is being alerted if no media is received from the network. Forward early media is not gated. | | | | + + + +| | | +|--------------------------------------|--| +| SIP header values | | +| INVITE2: | | +| P-Early-Media: supported | | +| SDP offer | | +| | | +| 183: | | +| P-Early-Media: [sendonly]/[sendrecv] | | +| SDP answer yes/no | | + + + +| | | +|--------------------------------|-------------------------------------| +| Message flow | | +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | ← 183 Session Progress | +| Local Ring back Tone | ← | +| | | +| ISDN interworking | | +| SETUP | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | ← 183 Session Progress | +| Local Ring back Tone | ← | +| Apply post test routine | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_036 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 | +| Test purpose
SUT local ring back tone is presented to the user. 183 received, P-Early-Media header value sendonly or sendrecv present.

Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received value recvonly or inactive, the SUT plays ringing tones for the caller, indicating that the callee is being alerted. Forward early media is not gated. | | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer

183:
P-Early-Media: [recvonly]/[inactive]
SDP answer yes/no | | +| Message flow | | +| End device | Test equipment | +| Interworking POTS
Off hook
Dial number | | +| | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | ← 183 Session Progress | +| Local Ring back Tone | ← | +| ISDN interworking
SETUP | | +| | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE2 | +| | ← 183 Session Progress | +| Local Ring back Tone | ← | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_037 | Reference
subclause 6.1.2 of
[ETSI TS124 229] | Selection expression | +| Test purpose
Handling of SDP offer | | | | +| Ensure that the IUT when sending an INVITE request contains a SDP offer and at least one media description. This SDP offer shall reflect the calling user's terminal capabilities and user preferences for the session. | | | | +| SIP header values
INVITE2:
SDP offer | | | | +| Message flow | | | | +| End device | Test equipment | | | +| Interworking POTS
Off hook
Dial number | | | | +| | → INVITE | | | +| | ← 407 Proxy Authentication Required | | | +| | → ACK | | | +| | → INVITE2 | | | + +| | | +|--------------------------------|-------------------------------------| +| ISDN interworking | | +| SETUP | ➔ INVITE | +| | ← 407 Proxy Authentication Required | +| | ➔ ACK | +| | ➔ INVITE2 | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------------|-----------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_038 | Reference
subclause 6.1.2 of
[ETSI TS124 229] | Selection expression | +| Test purpose | | | | +| Handling of SDP answer | | | | +| Ensure that the IUT Upon generating the SDP offer for an INVITE request generated after receiving a 488 (Not Acceptable Here) response, the SDP offer contains a subset of the allowed media types, codecs and other parameters from the SDP message bodies of all 488 (Not Acceptable Here) responses so far received for the same session establishment attempt (i.e. a set of INVITE requests used for the same session establishment). For each media line, the SUT shall order the codecs in the SDP offer according to the order of the codecs in the SDP message bodies of the 488 (Not Acceptable Here) responses. | | | | +| SIP header values | | | | +| INVITE2:
SDP offer1

488
SDP answer1
INVITE3:
SDP offer2 equal SDP answer1 | | | | +| Message flow | | | | +| End device | | | Test equipment | +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | | | | +| | ➔ INVITE | | | +| | ← 407 Proxy Authentication Required | | | +| | ➔ ACK | | | +| | ➔ INVITE2 | | | +| | ← 488 (Not Acceptable Here) | | | +| | ➔ ACK | | | +| | ➔ INVITE3 | | | +| ISDN interworking | | | | +| SETUP | | | | +| | ➔ INVITE | | | +| | ← 407 Proxy Authentication Required | | | +| | ➔ ACK | | | +| | ➔ INVITE2 | | | +| | ← 488 Not Acceptable Here | | | +| | ➔ ACK | | | +| | ➔ INVITE3 | | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|----------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|--------------|--|---|--------------|--|---|------------------|--|---|-----|--|---|------|--|---|--------------|------------------------------|--|--|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|--------------|--|---|--------------|--|---|------------------|--|---|-----|--|---|------|--|---|--------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_039 | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SUT terminates the forked not confirmed dialogue with a BYE request.

Ensure that the IUT when a final answer is received for one of the (forked) early dialogues, the SUT proceeds to set up the SIP session. An ACK is sent to acknowledge the confirmed dialogue and a BYE is sent to terminate the remaining early dialogues. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer

180 1:
P-Early-Media: [recvonly]/[inactive]
SDP answer yes/no | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 180 Ringing1
← 180 Ringing2
← 200 OK (INVITE)2
→ ACK
→ BYE1
← 200 OK (BYE)

ISDN interworking
SETUP → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 180 Ringing1
← 180 Ringing2
← 200 OK (INVITE)2
→ ACK
→ BYE1
← 200 OK (BYE)

Apply post test routine

| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE2 | | ← | 180 Ringing1 | | ← | 180 Ringing2 | | ← | 200 OK (INVITE)2 | | → | ACK | | → | BYE1 | | ← | 200 OK (BYE) |
ISDN interworking | | | SETUP | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE2 | | ← | 180 Ringing1 | | ← | 180 Ringing2 | | ← | 200 OK (INVITE)2 | | → | ACK | | → | BYE1 | | ← | 200 OK (BYE) | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (INVITE)2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | BYE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (INVITE)2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | BYE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--|---|-------------------------|--|--|---|-----|--|--------------------------------------------------------------|--|--|--|--|---|--------|--|--------------------------|--|--|--|-------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--|---|-------------------------|--|--|---|-----|--|--------------------------------------------------------------|--|--|--|--|---|--------|--|--------------------------------|--|--|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_040 | Reference
section 8.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Retry of INVITE request after 503 with Retry-After header received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT Upon receiving a 503 (Service Unavailable) response to an initial INVITE request containing a Retry-After header does not automatically reattempt the request until after the period indicated by the Retry-After header contents. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
⬅ 503 Service Unavailable
➔ ACK
Wait for the time indicated in the Retry-After header
➔ INVITE
ISDN interworking
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
⬅ 503 Service Unavailable
➔ ACK
Wait for the time indicated in the Retry-After header
➔ INVITE
Apply post test routine
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | | ⬅ | 503 Service Unavailable | | | ➔ | ACK | | Wait for the time indicated in the Retry-After header | | | | | ➔ | INVITE | | ISDN interworking | | | | SETUP | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | | ⬅ | 503 Service Unavailable | | | ➔ | ACK | | Wait for the time indicated in the Retry-After header | | | | | ➔ | INVITE | | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 503 Service Unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Wait for the time indicated in the Retry-After header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 503 Service Unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Wait for the time indicated in the Retry-After header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|-------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_041 | Reference
subclause 5.3.1.5.1 of
[ETSI TS183 043] | Selection expression
PICS 5.2/19 | +| Test purpose
Sending of a P-Preferred-Identity or From header field | | | | +| Ensure that the SUT is able to include the default identity associated with the analogue termination where the off-hook event was detected a P-Preferred-Identity header field or the From header. | | | | +| SIP header values | | | | +| INVITE: | | | | +| P-Preferred-Identity: {default user identity} | | | | +| From: {default user identity} | | | | + +| Message flow | | +|--------------------------------|-------------------------------------| +| End device | Test equipment | +| Off hook | | +| Dial number | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_042 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression | +| Test purpose
Modifying SDP in early dialogue | | | | +| Ensure that the SUT is able to receive an UPDATE request to modify the SDP in early dialogue. A 200 OK UPDATE with SDP answer is sent. | | | | +| SIP header values
183/180
SDP answer 1

UPDATE
SDP offer 2

200 OK (UPDATE)
SDP answer 2 | | | | +| Message flow | | | | +| End device | | Test equipment | | +| Off hook | | | | +| Dial number | → | INVITE | | +| | ← | 407 Proxy Authentication Required | | +| | → | ACK | | +| | → | INVITE | | +| | ← | 183/180 | | +| | ← | UPDATE | | +| | → | 200 OK UPDATE | | +| Apply post test routine | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_043 | Reference
subclause 5.3.1.4 of
[ETSI TS183 043] | Selection expression
PICS 5.3/2 | +| Test purpose
Charging procedure with AOC-S | | | | +| Ensure that the SUT is able to receive charging information for a communication in the call setup phase. After sending the initial INVITE request, a 18x reliable provisional response is received containing a aoc-extended/ aoc-s XML element, a PRACK is sent. | | | | + +###### **SIP header values** + +###### **18x:** + +Require: 100rel + +Content-Type: application/vnd.etsi.aoc+xml + +``` + + + + + + + 1 + normal-charging + + 1 + ten-seconds + + + + + + + +``` + +###### **Message flow** + +###### **End device** + +###### **Test equipment** + +Off hook + +Dial number + +→ INVITE + ← 407 Proxy Authentication Required + → ACK + → INVITE + ← 18x + → PRACK + ← 200 OK (PRACK) + +**Apply post test routine** + +| | | | | +|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_044 | Reference
subclause 5.3.1.4 of
[ETSI TS183 043] | Selection expression
PICS 5.3/2 | +|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------| + +###### **Test purpose** + +*Charging procedure with AOC-D* + +Ensure that the SUT is able to receive charging information for a communication in the active call phase. After the communication is in the confirmed state, a NOTIFY is received containing a aoc-extended/ aoc-d XML element, a 200 OK (INFO) is sent. + +###### **SIP header values** + +INFO: + +Content-Type: application/vnd.etsi.aoc+xml + +``` + + + subtotal + + + UNIT + 2 + + + normal-charging + + +``` + +###### **Message flow** + +**End device** + +**Test equipment** + +Off hook + +Dial number + +➔ INVITE + +⬅ 407 Proxy Authentication Required + +➔ ACK + +➔ INVITE + +Ringing tone + +⬅ 180 Ringing + +Conversation + +⬅ 200 OK (INVITE) + +➔ ACK + +Update of charging info + +⬅ INFO + +➔ 200 OK (INFO) + +**Apply post test routine** + +| | | | | +|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_045 | Reference
subclause 5.3.1.4 of
[ETSI TS183 043] | Selection expression
PICS 5.3/2 | +|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------| + +###### **Test purpose** + +*Charging procedure with AOC-E* + +Ensure that the SUT is able to receive charging information after a communication is terminated. When a communication is terminated, a BYE or a 200 OK (BYE) is received containing a aoc-extended XML element. + +| | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------|-----------------------------------------------|--|---------------|--|-----------------------------------------|-------------------------|---------------|--|--------------------------------|-------------------------| +| SIP header values
BYE/200 OK:

Content-Type: application/vnd.etsi.aoc+xml

<aoc-extended>   < aoc-e >     < recorded-charges>       <recorded-currency-units>         <currency-id>UNIT</currency-id>         <currency-amount>2</currency-amount>       </recorded-currency-units>     </ recorded-charges>     <billing-id> normal-charging </billing-id>   </ aoc-e > </aoc-extended>
| | | | | | | | | | | | | | +| Message flow
End device Test equipment
A communication is already established
CASE A
Update of charging info in 200 OK (BYE) → BYE
← 200 OK (BYE)
CASE B
Update of charging info in BYE ← BYE
→ 200 OK (BYE)
| | End device | Test equipment | A communication is already established | | CASE A | | Update of charging info in 200 OK (BYE) | → BYE
← 200 OK (BYE) | CASE B | | Update of charging info in BYE | ← BYE
→ 200 OK (BYE) | +| End device | Test equipment | | | | | | | | | | | | | +| A communication is already established | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | +| Update of charging info in 200 OK (BYE) | → BYE
← 200 OK (BYE) | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | +| Update of charging info in BYE | ← BYE
→ 200 OK (BYE) | | | | | | | | | | | | | + +##### **7.2.2.1.2 Test purposes for POTS** + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_101 | Reference
subclause 4.9.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.1.1/2 and 5.3/4 | +| Test purpose
Overlap dialling using the multiple-INVITE method

Ensure that the SUT sends an additional INVITE request if an 404 or 484 final response is received on the previous sent INVITE request and the user dials further digits. The INVITE request contains the previous sent digits and the current dialled digit. The From header and the Call-ID are the same as used in the initial INVITE request. | | | | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| SIP header values
INVITE1
Request Line Dialled number1
From: [value initial invite]
Call-ID: [value initial invite]

INVITE2
Request Line Dialled number1 + dialled digit1
From: [value initial invite]
Call-ID: [value initial invite]

INVITE3
Request Line Dialled number1+ dialled digit1 + dialled digit2
From: [value initial invite]
Call-ID: [value initial invite] | | +| Message flow | | +| End device | Test equipment | +| Off hook | | +| Dial number1 | | +| | ➔    INVITE1 | +| | ⬅    407 Proxy Authentication Required | +| | ➔    ACK | +| | ➔    INVITE1 | +| | ⬅    404/484 | +| | ➔    ACK | +| Dial digit1 | | +| | ➔    INVITE2 | +| | ⬅    404/484 | +| | ➔    ACK | +| Dial digit2 | | +| | ➔    INVITE3 | +| Ringing tone | ⬅    180 | +| Apply post test routine | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_102 | Reference
subclause 4.9.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.1.1/2 and 5.3/5 | +| Test purpose
Overlap dialling using the in-dialogue method

Ensure that the SUT sends an additional INVITE request if an 404 or 484 final response is received on the previous sent INVITE request and the user dials further digits. The INVITE request contains the previous sent digits and the current dialled digit. The From header and the Call-ID are the same as used in the initial INVITE request.
Ensure that when a 183 without an SDP is received additional dialled digits are transferred in an INFO request. | | | | + +###### **SIP header values** + +INVITE1 + +Request Line Dialled number1 + +From: [value initial invite] + +Call-ID: [value initial invite] + +INVITE2 + +Request Line Dialled number1 + dialled digit1 + +From: [value initial invite] + +Call-ID: [value initial invite] + +INFO + +Request Line Dialled number1+ dialled digit1 + +From: [value initial invite] + +Call-ID: [value initial invite] + +Content-Type: application/session-info + +Content-Disposition : signal ; handling=optional + +SubsequentDigit : [Dial digit2] + +###### **Message flow** + +**End device** + +**Test equipment** + +Off hook + +Dial number1 + +→ INVITE1 +← 407 Proxy Authentication Required +→ ACK +→ INVITE1 +← 404/484 +→ ACK + +Dial digit1 + +→ INVITE2 +← 183 Session Progress + +Dial digit2 + +→ INFO +← 200 OK INFO + +Ringing tone + +← 180 + +**Apply post test routine** + +##### 7.2.2.1.3 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_201 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | +| Test purpose
Indication of support of the PSTN XML schema | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT supports the PSTN XML schema, the initial INVITE request contains the application/vnd.etsi.pstn+xml tag in the Accept header. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Accept: application/vnd.etsi.pstn+xml | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_202 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP without called party number IE received | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message and the Information Transfer Capability value for the BC is set to 'speech' or 'audio 3 kBit/s' and no called party number Information Element is present, no INVITE request is sent. The AGCF/VGW sends a SETUP ACKNOWLEDGE message and a Progress Indicator IE is present the Progress description is set to 8. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_203 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|--|--|-------------------|--|--|-------|--|--|-------|--|--|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|---------------|--|---|-----|-----------|-------|-------------|--|---|---------------|--|---|-----|-----------|-------|-------------|----------|---|-------------| +| Test purpose
Overlap sending using the multiple INVITE method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that an initial INVITE is sent after a called party number was received in a SETUP followed by several digits in INFO messages. All digits collected from the SETUP and INFO messages are present in the Request line of the INVITE request. The sending of the INVITE request depends on the configuration of the digit map.

Ensure that after sending of the initial INVITE the SUT is able to process a received 404 Not Found. The final response is not relayed to the DSS1 user equipment. An additional received INFO is sent in a new INVITE request. The Request URI of all additionally sent INVITE requests contain all collected digits received in the SETUP and INFO messages.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1:
Request URI (digits INFO 1 to 3)

INVITE2:
Request URI (digits INFO 1 to 4)

INVITE3:
Request URI (digits INFO 1 to 5) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP: Called party number
INFO: Called party number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End deviceTest equipment
SETUP
SETUP ACKNOWLEDGE
INFO1
INFO2
INFO3➔INVITE
⬅407 Proxy Authentication Required
➔ACK
➔INVITE1
⬅404 Not Found
➔ACK

INFO4

➔

INVITE2
⬅404 Not Found
➔ACK

INFO5

➔

INVITE3
ALERTING⬅180 Ringing
| | | | End device | | Test equipment | SETUP | | | SETUP ACKNOWLEDGE | | | INFO1 | | | INFO2 | | | INFO3 | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE1 | | ⬅ | 404 Not Found | | ➔ | ACK |
INFO4 |
➔ |
INVITE2 | | ⬅ | 404 Not Found | | ➔ | ACK |
INFO5 |
➔ |
INVITE3 | ALERTING | ⬅ | 180 Ringing | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO3 | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 404 Not Found | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INFO4 |
➔ |
INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 404 Not Found | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INFO5 |
➔ |
INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_204 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|--|--|-------------------|--|--|-------|--|--|-------|--|--|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|------------------------|--|---|-----|-----------|-------|-------------|--|---|------------------------|--|---|-----|-----------|-------|-------------|----------|---|-------------| +| Test purpose
Overlap sending using the multiple INVITE method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that an initial INVITE is sent after a called party number was received in a SETUP followed by several digits in INFO messages. All digits collected from the SETUP and INFO messages are present in the Request line of the INVITE request. The sending of the INVITE request depends on the configuration of the digit map.

Ensure that after sending of the initial INVITE the SUT is able to process a received 484 Address Incomplete. The final response is not relayed to the DSS1 user equipment. An additional received INFO is sent in a new INVITE request. The Request URI of all additionally sent INVITE requests contain all collected digits received in the SETUP and INFO messages.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1:
Request URI (digits INFO 1 to 3)

INVITE2:
Request URI (digits INFO 1 to 4)

INVITE3:
Request URI (digits INFO 1 to 5) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP: Called party number
INFO: Called party number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP
SETUP ACKNOWLEDGE
INFO1
INFO2
INFO3 → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE1
← 484 Address Incomplete
→ ACK

INFO4

→

INVITE2
← 484 Address Incomplete
→ ACK

INFO5

→

INVITE3
ALERTING ← 180 Ringing
Apply post test routine
| | | | End device | | Test equipment | SETUP | | | SETUP ACKNOWLEDGE | | | INFO1 | | | INFO2 | | | INFO3 | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE1 | | ← | 484 Address Incomplete | | → | ACK |
INFO4 |
→ |
INVITE2 | | ← | 484 Address Incomplete | | → | ACK |
INFO5 |
→ |
INVITE3 | ALERTING | ← | 180 Ringing | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO3 | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 484 Address Incomplete | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INFO4 |
→ |
INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 484 Address Incomplete | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INFO5 |
→ |
INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|--|--|-------------------|--|--|--|--------------------|--|-------|-------------|--|-------|-------------|--|-------|-------------|--|--|----------------------|--|--|----------|--|--|-------------------------------------|--|--|-------|--|--|-----------|--|--|-----------|--|--|-------|--|-----------|---------------|--|--|-----------|--|--|-------|--|-----------|---------------|--|----------|---------------|--|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_205 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Sending of initial INVITE based on timeout Tinfo

Ensure that an initial INVITE is sent after a called party number was received in a SETUP followed by several digits in INFO messages. All digits collected from the SETUP and INFO messages are present in the Request line of the INVITE request. The INVITE is sent after the timeout of timer Tinfo
Ensure that after sending of the initial INVITE the SUT is able to process a received 404 Not Found or 484 Address Incomplete. The final response is not relayed to the DSS1 user equipment. An additional received INFO is sent in a new INVITE request. The Request URI of all additionally sent INVITE requests contain all collected digits received in the SETUP and INFO messages. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1:
Request URI (digits INFO 1 to 3)

INVITE2:
Request URI (digits INFO 1 to 4)

INVITE3:
Request URI (digits INFO 1 to 5) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP: Called party number
INFO: Called party number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP
SETUP ACKNOWLEDGE
Start Tinfo
INFO1 Start Tinfo
INFO2 Start Tinfo
INFO3 Start Tinfo
Timeout Tinfo
→ INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE1
← 404/484
→ ACK

INFO4

→ INVITE2
← 404/484
→ ACK

INFO5

→ INVITE3
ALERTING ← 180 Ringing
Apply post test routine
| | | | End device | | Test equipment | SETUP | | | SETUP ACKNOWLEDGE | | | | Start Tinfo | | INFO1 | Start Tinfo | | INFO2 | Start Tinfo | | INFO3 | Start Tinfo | | | Timeout Tinfo | | | → INVITE | | | ← 407 Proxy Authentication Required | | | → ACK | | | → INVITE1 | | | ← 404/484 | | | → ACK | |
INFO4 |
→ INVITE2 | | | ← 404/484 | | | → ACK | |
INFO5 |
→ INVITE3 | | ALERTING | ← 180 Ringing | | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO1 | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO2 | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INFO3 | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Timeout Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 404/484 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INFO4 |
→ INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 404/484 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INFO5 |
→ INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_206 | Reference
subclause 5.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | +| Test purpose
INVITE is sent after receipt of "#" character in the called party number, XML sendingCompleteIndication is contained | | | | | | | | | | | | | | | | | | | +|

Ensure that after initiating the normal incoming call establishment procedures, determining the end of address signalling and selecting to route the call to the IMS domain, the originating SUT sends the initial INVITE.

The end of address is detemined by receipt of a "#" character Sending complete Information Element as a sending complete indication.

– The INVITE contains the XML sendingCompleteIndication element

| | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:

| | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP: Called Party number contained the "#" character
or
Sending complete | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE

Apply post test routine

| | | | | End device | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | +| | End device | Test equipment | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_207 | Reference
subclause 5.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | +| Test purpose
En-bloc sending is used, the complete called party number is contained in the called party number | | | | | | | | | | | | | | | | | | | +|

Ensure that if the SETUP message contains the complete called number information, the called party number information is included in the Called party number information element possibly completed by the Called party subaddress information element.

The SUT sends a CALL PROCEEDING message. This acknowledges the SETUP message and indicates that the call is being processed and that no further address information is expected.

| | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: Request URI Called party number digits
To: Called party number digits; isub= Called paery subaddress; isub-encoding=nsap-ia5 | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Called party number: Complete number information
Called party subaddress | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE

Apply post test routine

| | | | | End device | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | +| | End device | Test equipment | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_208 | Reference
subclause 5.1.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
One bearer capability information element is received. Mapped into the XML BearerCapability element | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the whole bearer capability information element, as received in the SETUP message, shall be mapped to the PSTN XML bearer capability body in SIP. A bearer capability information element is received. The Information transfer capability value is indicated in Table 7.2.2.1.4-1. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>ITC_value<
<   BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011< | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP:
bearer capability Information transfer capability = ITC_value | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | INVITE | | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_209 | Reference
subclause 5.1.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
Two bearer capability information element are received. Mapped into two XML BearerCapability element | | | | +| Ensure that if two bearer capability information elements are received and the information transfer capability of the first BC is set to speech or 3,1 kHz audio and the information transfer capability of the second BC is set to unrestricted digital information with tones and announcements, two XML BearerCapability elements are contained in the PSTN XML attachment. | | | | +|
  • • The InformationTransferCabability of the first is set to '00000' or '10000'.
  • • The InformationTransferCabability of the second is set to '10001'.
| | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------|-----------------------------------|-----------------------|-------|--|---|--------|-------------------|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--------------------------------|--|--|--| +| SIP header values
INVITE:

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
Apply post test routine
| | End device | | Test equipment | SETUP | | ➔ | INVITE | SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.1.4-1 – Mapping of bearer capability to PSTN XML BearerCapability** + +| ITC_value | BC Information transfer capability | XML InformationTransferCabability | +|-----------|------------------------------------|-----------------------------------| +| ITC_VA_1 | Speech | '00000' | +| ITC_VA_2 | 3,1 kHz audio | '10000' | +| ITC_VA_3 | unrestricted digital information | '01000' | + +| | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|--------------------------------|--|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_210 | Reference
subclause 5.1.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | +| Test purpose
Mapping of Progress Indicator

Ensure that the Progress Indicator received in the SETUP is mapped into the PSTN XML ProgressIndicator value as indicated in Table 7.2.2.1.4-2. An additionally ProgressIndicator element is is contained and the ProgressDescription value is set to '0000110' | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000110<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription>PI_value< | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP:
Progress Indicator Coding standard ='00', Location ='0000', Progress description='0000yyyy' | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.1.4-2 – Mapping of progress indicator information element to PSTN XML ProgressIndicator** + +| PI_value | DSS1 progress indicator value | XML ProgressIndicator
ProgressDescription | +|----------|--------------------------------------------------------------------------------------------|----------------------------------------------| +| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' | +| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' | +| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' | +| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' | +| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' | +| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|-------------------|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_211 | Reference
subclause 5.1.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
No Progress Indicator received

Ensure that if no progress indicator was received in the a ProgressIndicator element is is contained and the ProgressDescription value is set to '0000110' | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000110<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription>PI_value< | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
SETUP: | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE

Apply post test routine

| | | | | End device | | Test equipment | SETUP | | ➔ | INVITE | SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_212 | Reference
clause 5.1.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
Mapping of high layer compatibility information element

Ensure that the high layer compatibility information element received in the SETUP is mapped into the PSTN XML HighLayerCompatibility | | | | +| SIP header values
INVITE:

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value< | | | | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DSS1 parameter values
SETUP:
High layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=HLC_value as indicated in Table 7.2.2.1.4-3 | | +| Message flow | | +| End device | Test equipment | +| SETUP | → INVITE | +| SETUP ACKNOWLEDGE | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE | +| Apply post test routine | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_213 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
Two high layer compatibility information elements received | | | | +| Ensure that the first high layer compatibility information element received in the SETUP is mapped into the first PSTN XML HighLayerCompatibility and the second High layer compatibility information element received in the SETUP is mapped into the second PSTN XML HighLayerCompatibility | | | | +| SIP header values
INVITE:

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>0000001<
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value< | | | | +| DSS1 Parameter values
SETUP:
First High layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=Telephony
Second High layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=HLC_value as indicated in Table 7.2.2.1.4-3 | | | | +| Message flow | | | | +| End device | | | Test equipment | +| SETUP | | → | INVITE | +| SETUP ACKNOWLEDGE | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| Apply post test routine | | | | + +**Table 7.2.2.1.4-3 – Mapping of high layer compatibility information element to PSTN XML HighLayerCharacteristic** + +| HLC_value | DSS1 High layer characteristics identification | XML HighLayerCharacteristic | +|-----------|------------------------------------------------------------------------|-----------------------------| +| HLC_VA_1 | Telephony | '0000001' | +| HLC_VA_2 | Facsimile Group 2/3 | '0000100' | +| HLC_VA_3 | Facsimile Group 4 Class I | '0100001' | +| HLC_VA_4 | Facsimile service Group 4, Classes II ad III | '0100100' | +| HLC_VA_5 | Syntax based Videotex | '0110010' | +| HLC_VA_6 | International Videotex interworking via gateways or interworking units | '0110011' | +| HLC_VA_7 | Telex service | '0110101' | +| HLC_VA_8 | FTAM application | '1000010' | +| HLC_VA_9 | Videotelephony | '1100000' | + +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_214 | Reference
5.1.1.2.1, 5.1.1.2.1.1/
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|------------------------------------------------|------------|--|----------------|--|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|-------------|--| +| Test purpose
180 received, No PSTN XML body present, PI 1 is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 180 (Ringing) and a PSTN XML body is not present, an ALERTING message is sent to the calling user equipment that contains a Progress Indicator Information Element and the Progress description is set to value 1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 parameter values
ALERTING; Progress Indicator value 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 Ringing

Apply post test routine

| | | | End device | | Test equipment | | SETUP | ➔ | INVITE | | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | ALERTING | ⬅ | 180 Ringing | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_215 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
180 received, PSTN XML body present two XML PI set to value 7 and x an ALERTING is sent PI value x | | | | +| Ensure that on receipt of a 180 (Ringing) a PSTN XML body is present contains two ProgressIndicator elements set to x and 7, an ALERTING is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-4 | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------------------|-------------------|-----------------------|-------|--|----------|-------------------|--|-------------------------------------|--|--|-------|--|--|----------|----------|--|---------------|--|-------------------------|--| +| SIP header values
180 (Ringing): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: Progress Indicator value x | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
SETUP ACKNOWLEDGE ← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← 180 Ringing
Apply post test routine
| | | End device | Test equipment | SETUP | | → INVITE | SETUP ACKNOWLEDGE | | ← 407 Proxy Authentication Required | | | → ACK | | | → INVITE | ALERTING | | ← 180 Ringing | | Apply post test routine | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | +| SETUP | | → INVITE | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | +| | | → INVITE | | | | | | | | | | | | | | | | | | | | | +| ALERTING | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.1.4-4 – Mapping of progress indicator information element to PSTN XML ProgressIndicator** + +| PI_value | DSS1 progress indicator value | XML ProgressIndicator
ProgressDescription | +|----------|--------------------------------------------------------------------------------------------|----------------------------------------------| +| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' | +| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' | +| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' | +| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' | +| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' | +| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' | + +| | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|-------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_216 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | +| Test purpose
180 received, PSTN XML body present XML PI set to value 7

Ensure that on receipt of the first 180 (Ringing) and a PSTN XML body present the XML PI is set to value 7, an ALERTING message is sent to the calling user equipment does not contain a Progress Indicator Information Element. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180 (Ringing): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: No Progress Indicator present | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 Ringing

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_217 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
Subsequent 180 received, No PSTN XML body present, PI 1 is sent.

Ensure that on receipt of a subsequent 180 (Ringing) and a PSTN XML body is not present, a PROGRESS message is sent to the calling user equipment that contains a Progress Indicator Information Element and the Progress description is set to value 1 if a PROGRESS message was sent before that contains Progress Indicator value 4. | | | | + +| SIP header values
180 (Ringing) 1: no XML body present
180 (Ringing) 2: XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
180 (Ringing) 3 no XML body present | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------|----------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|--------------|------------|---|--------------|------------|---|--------------| +| DSS1 Parameter values
PROGRESS 1: Progress Indicator value 4
PROGRESS 2: Progress Indicator value 1 | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➠ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➠ ACK
➠ INVITE
ALERTING ⬅ 180 Ringing1
PROGRESS 1 ⬅ 180 Ringing2
PROGRESS 2 ⬅ 180 Ringing3

Apply post test routine

| End device | | Test equipment | SETUP | ➠ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➠ | ACK | | ➠ | INVITE | ALERTING | ⬅ | 180 Ringing1 | PROGRESS 1 | ⬅ | 180 Ringing2 | PROGRESS 2 | ⬅ | 180 Ringing3 | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➠ | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS 1 | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS 2 | ⬅ | 180 Ringing3 | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_218 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|--------------|----------|---|--------------| +| Test purpose
Subsequent 180 received and the P-Early-Media header set to sendonly, a PROGRESS message is sent.

Ensure that on receipt of a subsequent 180 (Ringing) that contains a P-Early-Media header set to sendonly, the SUT the Progress Indicator Information Element is present in the sent PROGRESS message and the Progress description is set to value 8. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180 (Ringing) 2: P-Early-Media: sendonly | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Progress Indicator value 8 | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➠ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➠ ACK
➠ INVITE
ALERTING ⬅ 180 Ringing1
PROGRESS ⬅ 180 Ringing2

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➠ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➠ | ACK | | ➠ | INVITE | ALERTING | ⬅ | 180 Ringing1 | PROGRESS | ⬅ | 180 Ringing2 | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➠ | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_219 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|--------------|--|----------|---|--------------|--| +| Test purpose
Subsequent 180 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x included

Ensure that on receipt of a subsequent 180 (Ringing) a PSTN XML body is present, which contains two Progress Indicator elements set to x and 7, a PROGRESS message is sent to the calling user equipment. A Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-5 and a second Progress Indicator Information Element is present, the Progress description is set to the value 4 if a 180 (Ringing) was received before and no PSTN XML body was present. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180 (Ringing) 1: no XML body present
180 (Ringing) 2: XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location
ProgressOctet4
ProgressDescription>PI_value<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Progress Indicator value x and a Progress Indicator value 4 Call has returned to the 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 Ringing1
PROGRESS ⬅ 180 Ringing2

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | INVITE | | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | ALERTING | ⬅ | 180 Ringing1 | | PROGRESS | ⬅ | 180 Ringing2 | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.1.4-5 – Mapping of progress indicator information element to PSTN XML ProgressIndicator** + +| PI_value | DSS1 Progress Indicator value | XML ProgressIndicator ProgressDescription | +|----------|--------------------------------------------------------------------------------------------|-------------------------------------------| +| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' | +| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' | +| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' | +| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' | +| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' | +| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' | + +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_220 | Reference subclauses 5.1.1.2.1 and 5.1.1.2.1.1 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|--------------|----------|---|--------------| +| Test purpose
180 received, PSTN XML body present XML PI set to value 7

Ensure that on receipt of a subsequent 180 (Ringing) and a PSTN XML body present the XML PI is set to value 7 and PROGRESS is sent toward the calling user equipment and a Progress Indicator Information Element is present the Progress description is set to the value 4 if a 180 (Ringing) was received without a PSTN XML body. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180 (Ringing) 1: no XML body present
180 (Ringing) 2: XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: No Progress Indicator present
PROGRESS: Progress Indicator value 4 Call has returned to the 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 Ringing1
PROGRESS ⬅ 180 Ringing2

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing1 | PROGRESS | ⬅ | 180 Ringing2 | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_221 | Reference
subclause 5.1.1.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
Receiving of PSTN XML HighLayerCompatibility fallback information an ALERTING is sent | | | | +| Ensure that on receipt of a 180 (Ringing) that contains a PSTN XML HighLayerCompatibility element that indicates fallback, the SUT sends an ALERTING message to the calling user equipment that does not contain a High Layer Compatibility Information Element. | | | | +| SIP header values
180 (Ringing): XML body

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value< | | | | +| DSS1 parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz
audio
Second Bearer Capability Information transfer capability = Unrestricted
digital information with tones/announcements
ALERTING: | | | | +| Message flow | | | | +| | End device | | Test equipment | +| SETUP | | ➔ | INVITE | +| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | +| | | ➔ | ACK | +| | | ➔ | INVITE | +| ALERTING | | ⬅ | 180 Ringing | +| Apply post test routine | | | | + +**Table 7.2.2.1.4-5 – Mapping of high layer compatibility information element to PSTN XML HighLayerCharacteristic** + +| HLC_value | DSS1 high layer characteristics identification | XML HighLayerCharacteristic | +|-----------|------------------------------------------------------------------------|-----------------------------| +| HLC_VA_1 | Telephony | '0000001' | +| HLC_VA_2 | Facsimile Group 2/3 | '0000100' | +| HLC_VA_3 | Facsimile Group 4 Class I | '0100001' | +| HLC_VA_4 | Facsimile service Group 4, Classes II ad III | '0100100' | +| HLC_VA_5 | Syntax based Videotex | '0110010' | +| HLC_VA_6 | International Videotex interworking via gateways or interworking units | '0110011' | +| HLC_VA_7 | Telex service | '0110101' | +| HLC_VA_8 | FTAM application | '1000010' | +| HLC_VA_9 | Videotelephony | '1100000' | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|-------------|--| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_222 | Reference
subclause 5.1.1.2.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
Receiving of PSTN XML BearerCapability fallback information an ALERTING is sent.

Ensure that on receipt of a 180 (Ringing) that contains a PSTN XML BearerCapability element that indicates fallback, the SUT sends an ALERTING message to the calling user equipment that does not contain a Bearer Capability Information Element.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
180 (Ringing): XML body
<?xml version="1.0" encoding="utf-8"?>
PSTN
  BearerCapability
    BCoctet3
      CodingStandard>00<
      InformationTransferCabability>00000<
    BCoctet4
      TransferMode>00<
      InformationTransferRate>10000<
    BCoctet5>
      Layer1Identification>01<
      UserInfoLayer1Protocol>00011<

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz
            audio
            Second Bearer Capability Information transfer capability = Unrestricted
            digital information with tones/announcements
ALERTING:

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

End device Test equipment
SETUP → INVITE
SETUP ACKNOWLEDGE ← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← 180 Ringing

Apply post test routine

| | | | | End device | | Test equipment | SETUP | → | INVITE | | SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | | ALERTING | ← | 180 Ringing | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_223 | Reference
subclause 5.1.1.2.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +|

Test purpose
No fallback information received, CLEARMODE codec not the preferred codec in the 180

Ensure that on receipt of 180 (Ringing) and the CLEARMODE codes is not the first codec in the codec list, the SUT sends an ALERTING toward the calling user equipment and fallback is not indicated. No BC is sent in the ALERTING.

| | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------------------| +| SIP header values | | | +| DSS1 Parameter values | | | +| SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
ALERTING: | | | +| Message flow | | | +| End device | | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| ALERTING | ← | 180 Ringing | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_224 | Reference
subclause 5.1.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose | | | | +| Receipt of first 183 with P-Early-Media header CALL PROCEEDING is sent | | | | +| Ensure that on receipt of the first 183 (Session Progress) with P-Early-Media header, the SUT does not send a local ringing tone to the calling user. The early media is passed through. A CALL PROCEEDING message is sent to the calling user contains a Progress Indicator Information Element and the Progress description is set to value 8. | | | | +| SIP header values | | | | +| 183 (Session Progress): P-Early-Media: sendonly, SDP | | | | +| DSS1 Parameter values | | | | +| CALL PROCEEDING: Progress Indicator value 8 | | | | +| Message flow | | | | +| End device | | | Test equipment | +| SETUP | | → | INVITE | +| SETUP ACKNOWLEDGE | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| CALL PROCEEDING | | ← | 183 (Session Progress) | +| Apply post test routine | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|-------------------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_225 | Reference
subclause 5.1.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.2/16 | +| Test purpose | | | | +| Receipt of 183 with P-Early-Media header PROGRESS is sent | | | | +| Ensure that on receipt of a 183 (Session Progress) with P-Early-Media header, the SUT does not send a local ringing tone to the calling user. The early media is passed through. A PROGRESS message is sent to the calling user contains a Progress Indicator Information Element and the Progress description is set to value 8. | | | | +| SIP header values | | | | +| 183 (Session Progress): P-Early-Media: sendonly, SDP | | | | + +| | | | +|--------------------------------------|---|-----------------------------------| +| DSS1 Parameter values | | | +| PROGRESS: Progress Indicator value 8 | | | +| Message flow | | | +| End device | | Test equipment | +| SETUP | ➔ | INVITE | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | +| | ➔ | ACK | +| | ➔ | INVITE | +| ALERTING | ⬅ | 180 (Ringing) | +| PROGRESS | ⬅ | 183 (Session Progress) | +| Apply post test routine | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_226 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose | | | | +| 183 received, PSTN XML body present two XML PI set to value 7 and x CALL PROCEEDING is sent PI value x | | | | +| Ensure that on receipt of a 183 (Session Progress), a PSTN XML body is present that contains two ProgressIndicator elements set to x and 7, a CALL PROCEEDING is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-6 | | | | +| SIP header values | | | | +| 180 (Ringing): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | +| DSS1 Parameter values | | | | +| CALL PROCEEDING: Progress Indicator value x | | | | +| Message flow | | | | +| End device | | | Test equipment | +| SETUP | ➔ | | INVITE | +| SETUP ACKNOWLEDGE | ⬅ | | 407 Proxy Authentication Required | +| | ➔ | | ACK | +| | ➔ | | INVITE | +| CALL PROCEEDING | ⬅ | | 183 (Session Progress) | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--|--------|-------------------|---|--|-----------------------------------|--|---|--|-----|--|---|--|--------|-----------------|---|--|------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_227 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
183 received, PSTN XML body present XML PI set to value 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of a subsequent 183 (Session Progress) and a PSTN XML body is present, the XML PI is set to value 7 a CALL PROCEEDING is sent toward the calling user equipment, and a Progress Indicator Information Element is present. The Progress description is set to the value 4 if a 180 (Ringing) was received without a PSTN XML body.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180 (Ringing): XML body
 <?xml version="1.0" encoding="utf-8"?> PSTN   ProgressIndicator     ProgressOctet3       CodingStandard>00<       Location>yyyy<     ProgressOctet4       ProgressDescription>0000111< 
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CALL PROCEEDING: Progress Indicator not present | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
CALL PROCEEDING ⬅ 183 (Session Progress)

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | | INVITE | SETUP ACKNOWLEDGE | ⬅ | | 407 Proxy Authentication Required | | ➔ | | ACK | | ➔ | | INVITE | CALL PROCEEDING | ⬅ | | 183 (Session Progress) | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | | ACK | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| CALL PROCEEDING | ⬅ | | 183 (Session Progress) | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|-------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_228 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.2/16 | +| Test purpose
183 received and the P-Early-Media header set to sendonly, a PROGRESS message is sent. | | | | +|

Ensure that on receipt of a 183 (Session Progress) that contains a P-Early-Media header set to sendonly, the SUT the Progress Indicator Information Element is present in the sent PROGRESS message and the Progress description is set to value 8.

| | | | +| SIP header values
183 (Session Progress): P-Early-Media: sendonly | | | | +| DSS1 Parameter values
ALERTING: No Progress Indicator present
PROGRESS: Progress Indicator value 8 | | | | + +| Message flow | | | +|--------------------------------|---|-----------------------------------| +| End device | | Test equipment | +| SETUP | ➔ | INVITE | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | +| | ➔ | ACK | +| | ➔ | INVITE | +| ALERTING | ⬅ | 180 Ringing1 | +| PROGRESS | ⬅ | 183 Session Progress | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_229 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
183 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x

Ensure that on receipt of a 183 (Session Progress) that contains a P-Early-Media header set to sendonly, in the SUT the Progress Indicator Information Element is present in the sent PROGRESS message and the Progress description is set to value 8.

| | | | +| SIP header values
180 (Ringing):

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
183 (Session Progress): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | +| DSS1 Parameter values
ALERTING: No Progress Indicator present
PROGRESS: Progress Indicator value 8 | | | | +| Comments
The Location value is don't care. The order of the received ProgressIndicator elements is accidental | | | | + +| Message flow | | | +|-------------------------|---|-----------------------------------| +| End device | | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| ALERTING | ← | 180 Ringing1 | +| PROGRESS | ← | 183 Session Progress | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_230 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
183 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x | | | | +| Ensure that on receipt of a 183 (Session Progress), a PSTN XML body is present, which contains two ProgressIndicator elements set to x and 7, a PROGRESS is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-6. In the previous 180 (Ringing) was a PSTN XML body. | | | | +| SIP header values
180 (Ringing):

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
183 (Session Progress): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | +| DSSI Parameter values
PROGRESS: Progress Indicator value x | | | | +| Comments
The Location value is don't care. The order of the received ProgressIndicator elements is accidental | | | | + +| Message flow | | | +|--------------------------------|---|-----------------------------------| +| End device | | Test equipment | +| SETUP | ➔ | INVITE | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | +| | ➔ | ACK | +| | ➔ | INVITE | +| ALERTING | ⬅ | 180 Ringing | +| PROGRESS | ⬅ | 183 Session Progress | +| Apply post test routine | | | + +| TSS
Orig_Establishment_of_a
n_early_dialogue | TP_201_231 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|-------------|----------|---|----------------------|--------------------------------|--|--| +| Test purpose
183 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x and value 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 183 (Session Progress) a PSTN XML body is present that contains two ProgressIndicator elements set to x and 7, a PROGRESS is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-6 and in addition a second Progress Indicator Information Element is present, the Progress description is set to the value 4. In the previous 180 (Ringing) there was no PSTN XML body. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180 (Ringing):
183 (Session Progress): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Progress Indicator value x and 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments
The Location value is don't care. The order of the received ProgressIndicator elements is accidental | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 Ringing
PROGRESS ⬅ 183 Session Progress
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing | PROGRESS | ⬅ | 183 Session Progress | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|-------------|----------|---|----------------------| +| TSS | TP_201_232 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
183 received, PSTN XML body present XML PI set to value 7 | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of the 183 (Session Progress) and if a PSTN XML body is present and the XML PI is set to value 7, a PROGRESS message is sent to the calling user equipment. A Progress Indicator Information Element is present, the Progress description is set to the value 4. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
183 (Session Progress):

ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Progress Indicator value x and 4 | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 Ringing
PROGRESS ⬅ 183 Session Progress

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing | PROGRESS | ⬅ | 183 Session Progress | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.1.4-6 – Mapping of progress indicator information element to PSTN XML ProgressIndicator** + +| PI_value | DSS1 Progress Indicator value | XML ProgressIndicator
ProgressDescription | +|----------|--------------------------------------------------------------------------------------------|----------------------------------------------| +| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' | +| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' | +| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' | +| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' | +| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' | +| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' | + +| | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|-----------------|---|----------------------| +| TSS | TP_201_233 | Reference
clause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | +| Test purpose
Receiving of PSTN XML BearerCapability fallback information in a 183 a CALL PROCEEDING is sent. | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML BearerCapability element that indicates fallback, the SUT sends a CALL PROCEEDING message to the calling user equipment that does not contain a Bearer Capability Information Element. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
183 (Session Progress):



00
00000


00
10000


01
00011

| | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
CALL PROCEEDING ← 183 Session Progress

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | CALL PROCEEDING | ← | 183 Session Progress | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| CALL PROCEEDING | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS | TP_201_234 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
Receiving of PSTN XML BearerCapability fallback information in a 183 a PROGRESS is sent. | | | | +| Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML BearerCapability element that indicates fallback, the SUT sends a PROGRESS message to the calling user equipment that does not contain a Bearer Capability Information Element. | | | | + +|

SIP header values
183 (Session Progress):
<?xml version="1.0" encoding="utf-8"?>
<BearerCapability>
    <BCoctet3>
        <CodingStandard>00</CodingStandard>
        <InformationTransferCabability>00000</InformationTransferCabability>
    </BCoctet3>
    <BCoctet4>
        <TransferMode>00</TransferMode>
        <InformationTransferRate>10000</InformationTransferRate>
    </BCoctet4>
    <BCoctet5>
        <Layer1Identification>01</Layer1Identification>
        <UserInfoLayer1Protocol>00011</UserInfoLayer1Protocol>
    </BCoctet5>
</BearerCapability>

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

DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
PROGRESS:

| | | | | | | | | | | | | | | | | | | | +|

Message flow

|
End deviceTest equipment
SETUP➔INVITE
SETUP ACKNOWLEDGE⬅407 Proxy Authentication Required
➔ACK
➔INVITE
PROGRESS⬅183 Session Progress

Apply post test routine

| End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | PROGRESS | ⬅ | 183 Session Progress | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------------------| +| TSS | TP_201_235 | Reference
subclause 5.1.1.2.2.3 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +|

Test purpose
Receiving of PSTN XML HighLayerCompatibility fallback information a CALL PROCEEDING is sent.

Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML HighLayerCompatibility element according to Table 7.2.2.1.4-5 and a ProgressIndicator value set to 5 that indicates fallback, the SUT sends a CALL PROCEEDING message to the calling user equipment that does not contain a High Layer Compatibility Information Element.

| | | | + +| | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|-----------------|---|----------------------| +| SIP header values
183 (Session Progress): PSTN XML MIME body

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000101< | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CALL PROCEEDING: | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
CALL PROCEEDING ⬅ 183 Session Progress

Apply post test routine

| | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | CALL PROCEEDING | ⬅ | 183 Session Progress | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | +| CALL PROCEEDING | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------| +| TSS | TP_201_236 | Reference
subclause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
Receiving of PSTN XML HighLayerCompatibility fallback information a PROGRESS is sent.

Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML HighLayerCompatibility element according to Table 7.2.2.1.4-5 and a ProgressIndicator value set to 5 that indicates fallback, the SUT sends a PROGRESS message to the calling user equipment that does not contain a High Layer Compatibility Information Element. | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|-----------|---|----------------------| +| SIP header values
183 (Session Progress): PSTN XML MIME body

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000101< | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
PROGRESS: | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
SETUP ACKNOWLEDGE ← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← 180 (Ringing)
PROGRESS: ← 183 Session Progress

Apply post test routine

| End device | | Test equipment | SETUP | → | INVITE | SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | ALERTING | ← | 180 (Ringing) | PROGRESS: | ← | 183 Session Progress | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | +| PROGRESS: | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------| +| TSS | TP_201_237 | Reference
subclause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
No fallback information received, CLEARMODE codec not the preferred codec in the 183. | | | | +| Ensure that on receipt of 183 (Session Progress) and the CLEARMODE codes is not the first codec in the codec list, the SUT sends a CALL PROCEEDING toward the calling user equipment and fallback is not indicated. No BC is sent in the CALL PROCEEDING | | | | +| SIP header values | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CALL PROCEEDING | | | | + +| Message flow | | | +|--------------------------------|---|-----------------------------------| +| End device | | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| CALL PROCEEDING | ← | 183 Session Progress | +| Apply post test routine | | | + +| TSS | TP_201_238 | Reference
subclause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------| +| Test purpose
No fallback information received, CLEARMODE codec not the preferred codec in the 183 | | | | +| Ensure that on receipt of 183 (Session Progress) and the CLEARMODE codes is not the first codec in the codec list, the SUT sends a PROGRESS toward the calling user equipment and fallback is not indicated. No BC is sent in the PROGRESS | | | | +| SIP header values
183 (Session Progress): CLEARMODE not the first codec | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
PROGRESS | | | | +| Message flow | | | | +| | End device | | Test equipment | +| SETUP | → | | INVITE | +| SETUP ACKNOWLEDGE | ← | | 407 Proxy Authentication Required | +| | → | | ACK | +| | → | | INVITE | +| ALERTING | ← | | 180 (Ringing) | +| PROGRESS | ← | | 183 Session Progress | +| Apply post test routine | | | | + +#### 7.2.2.2 Establishment of a confirmed dialogue + +##### 7.2.2.2.1 SIP basic procedures + +| TSS
Orig_Establishment_of_a_
confirmed_dialogue | TP_202_001 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------------------------------------------------------------------------|----------------------|------------|----------------|--------------------------|--|----------|--|-------------|----------|--|-----------------|--|-------|--------------------------|--|---------------|--|-------|----------|---------|-----------------|--|-------|---------------|--|-------|----------|---------|-----------------|---------------------|-------| +| Test purpose
200 OK received, an ACK is sent

Ensure that when an early dialogue is not established that on receipt of a Success (200 OK) response an ACK request is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number→ INVITE
← 200 OK INVITE
→ ACK
ISDN interworking
CASE A
SETUP→ INVITE
CONNECT← 200 OK INVITE
→ ACK
CASE B
SETUP→ INVITE
CONNECT← 200 OK INVITE
CONNECT ACKNOWLEDGE→ ACK
Apply post test routine
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | → INVITE | | ← 200 OK INVITE | | → ACK | ISDN interworking | | CASE A | | SETUP | → INVITE | CONNECT | ← 200 OK INVITE | | → ACK | CASE B | | SETUP | → INVITE | CONNECT | ← 200 OK INVITE | CONNECT ACKNOWLEDGE | → ACK | +| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACKNOWLEDGE | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a_
_confirmed_dialogue | TP_202_002 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
200 OK received in the Proceeding state an ACK is sent

Ensure that when the client transaction in the Proceeding state that on receipt of a Success (200 OK) response an ACK request is sent. | | | | +| SIP header values | | | | + +| Message flow | | +|--------------------------------|------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 100 Trying
← 200 OK INVITE
→ ACK | +| ISDN interworking | | +| CASE A | | +| SETUP | → INVITE | +| SETUP ACKNOWLEDGE | ← 100 Trying | +| CONNECT | ← 200 OK INVITE | +| | → ACK | +| CASE B | | +| SETUP | → INVITE | +| SETUP ACKNOWLEDGE | ← 100 Trying | +| CONNECT | ← 200 OK INVITE | +| CONNECT ACKNOWLEDGE | → ACK | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_003 | Reference
sections 12.2.1.1, 13.2.2.4, and 5
Figure 17.1.1.3 of
[IETF RFC 3261] | Selection expression | +|-------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
200 OK received in an early dialogue an ACK is sent

Ensure that when an early dialogue is established that on receipt of a Success (200 OK) response an ACK request is sent. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|--------------------------| +| SIP header values | +|--------------------------| + +| Message flow | | +|--------------------------|-------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK | +| ISDN interworking | | +| CASE A | | +| SETUP | → INVITE | +| ALERTING | ← 180 Ringing | +| CONNECT | ← 200 OK INVITE | +| | → ACK | + +| | | +|--------------------------------|---------------------| +| CASE B | | +| SETUP | ➔     INVITE | +| ALERTING | ←     180 Ringing | +| CONNECT | ←     200 OK INVITE | +| CONNECT ACKNOWLEDGE | ➔     ACK | +| Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------------|----------------------|-------------------|-----------------------|--------------------------|--|----------|--|-------------|--------------|--|------------------|--|---------------------|--------------------------|--|-------|--------------|-------------------|------------------|---------|---------------------|--------------------------------|--| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_004 | Reference
section 8.1.3.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
200 OK containing two Via header discarded | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that when the client transaction is in the Proceeding state that on receipt of a Success (200 OK) response with more than one Via header value no ACK request is sent, discards the response. | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK INVITE
Via:SIP 2.0 ;branch=
Via:SIP 2.0 ;branch= | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔     INVITE
←     100 Trying
←     200 OK INVITE
ISDN interworking
SETUP ➔     INVITE
SETUP ACKNOWLEDGE ←     100 Trying
CONNECT ←     200 OK INVITE
Apply post test routine
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | ➔     INVITE | | ←     100 Trying | | ←     200 OK INVITE | ISDN interworking | | SETUP | ➔     INVITE | SETUP ACKNOWLEDGE | ←     100 Trying | CONNECT | ←     200 OK INVITE | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔     INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←     100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | +| | ←     200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔     INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ←     100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ←     200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_005 | Reference
section 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
ACK is sent with the same CSeq as in the initial INVITE | | | | +| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response an ACK request is sent with the same CSeq sequence number as in the original INVITE request and the CSeq method field value set to "ACK". | | | | +| SIP header values
INVITE 1
CSeq: INVITE

ACK 1
CSeq: ACK | | | | + +| Message flow | | | +|--------------------------------|------------|----------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE 1 | +| | ← | 200 OK INVITE | +| | → | ACK 1 | +| ISDN interworking | | | +| CASE A | | | +| SETUP | → | INVITE 1 | +| CONNECT | ← | 200 OK INVITE | +| | → | ACK 1 | +| CASE B | | | +| SETUP | → | INVITE 1 | +| CONNECT | ← | 200 OK INVITE | +| CONNECT ACKNOWLEDGE | → | ACK 1 | +| Apply post test routine | | | + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|--|--| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_006 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | +| Test purpose | | | | | | +| ACK is sent with the same To header filed as received in the 200 OK | | | | | | +| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response an ACK request is sent with the To header set to the same value as in the received final response. | | | | | | +| SIP header values | | | | | | +| 200 OK INVITE
To: ;tag= | | | | | | +| ACK
To: ;tag= | | | | | | +| Message flow | | | | | | +| | End device | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | → | INVITE | | | | +| | ← | 200 OK INVITE | | | | +| | → | ACK 1 | | | | +| ISDN interworking | | | | | | +| CASE A | | | | | | +| SETUP | → | INVITE | | | | +| CONNECT | ← | 200 OK INVITE | | | | +| | → | ACK 1 | | | | + +| | | +|--------------------------------|-----------------| +| CASE B | | +| SETUP | ➔ INVITE | +| CONNECT | ← 200 OK INVITE | +| CONNECT ACKNOWLEDGE | ➔ ACK 1 | +| Apply post test routine | | + +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_007 | Reference
section 12.2.1.1, 13.2.2.4,
Figure 5 and 17.1.1.3 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|---------------|--|---|-----------------|--|---|-------|------------------------------|--|--|---------------|--|--|-------|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-------|-------------------|--|--|-------|---|--------|----------|---|---------------|---------|---|-----------------|---------------------|---|-------|--------------------------------|--|--| +|

Test purpose
ACK is sent with the same To header filed as received in the 180

Ensure that when the client transaction is in the Proceeding state that on receipt of a Success (200 OK) response an ACK request is sent with the To header set to the same value as in the received provisional response.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
200 OK INVITE
To: <any URI>;tag=<any 200 OK tag value>

ACK
To: <any URI>;tag=<any 200 OK tag value>

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
← 180 Ringing 1
← 200 OK INVITE 1
➔ ACK 1

ISDN interworking
CASE A
SETUP ➔ INVITE
ALERTING ← 180 Ringing 1
CONNECT ← 200 OK INVITE 1
➔ ACK 1

CASE B
SETUP ➔ INVITE
ALERTING ← 180 Ringing 1
CONNECT ← 200 OK INVITE 1
CONNECT ACKNOWLEDGE ➔ ACK 1
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ← | 180 Ringing 1 | | ← | 200 OK INVITE 1 | | ➔ | ACK 1 |
ISDN interworking | | | CASE A | | | SETUP | ➔ | INVITE | ALERTING | ← | 180 Ringing 1 | CONNECT | ← | 200 OK INVITE 1 | | ➔ | ACK 1 |
CASE B | | | SETUP | ➔ | INVITE | ALERTING | ← | 180 Ringing 1 | CONNECT | ← | 200 OK INVITE 1 | CONNECT ACKNOWLEDGE | ➔ | ACK 1 | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 Ringing 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | 200 OK INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 Ringing 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | 200 OK INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACKNOWLEDGE | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_008 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
ACK is sent without a To tag

Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response including a To header without tag an ACK request is sent with a To header without tag. | | | | + + + +| | | +|--------------------------|--| +| SIP header values | | +| 200 OK INVITE | | +| To: | | +| ACK | | +| To: | | + + + +| Message flow | | +|--------------------------------|-----------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE | +| | ← 200 OK INVITE 1 | +| | → ACK 1 | +| ISDN interworking | | +| CASE A | | +| SETUP | → INVITE | +| CONNECT | ← 200 OK INVITE 1 | +| | → ACK 1 | +| CASE B | | +| SETUP | → INVITE | +| CONNECT | ← 200 OK INVITE 1 | +| CONNECT ACKNOWLEDGE | → ACK 1 | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_009 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.2 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
ACK is sent for each received 200 OK

Ensure that when the client transaction is in the Calling state that on receipt of Success (200 OK) responses differing only on the tag in the To header, an ACK request is sent with a To header identical to the one received for each received Success (200 OK) responses. | | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| SIP header values
200 OK INVITE 1
To: ;tag=

ACK 1
To: ;tag=
200 OK INVITE 2
To: ;tag=
ACK 2
To: ;tag= | | +| Message flow | | +| End device | Test equipment | +| Interworking POTS | | +| Off hook | → INVITE | +| Dial number | ← 200 OK INVITE 1 | +| | → ACK 1 | +| | ← 200 OK INVITE 2 | +| | → ACK 2 | +| ISDN interworking | | +| CASE A | | +| SETUP | → INVITE | +| CONNECT | ← 200 OK INVITE 1 | +| | → ACK 1 | +| | ← 200 OK INVITE 2 | +| | → ACK 2 | +| CASE B | | +| SETUP | → INVITE | +| CONNECT | ← 200 OK INVITE 1 | +| CONNECT ACKNOWLEDGE | → ACK 1 | +| | ← 200 OK INVITE 2 | +| | → ACK 2 | +| Apply post test routine | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_010 | Reference
section 12.2.1.1, 13.2.2.4,
Figure 5 and 17.1.1.3 of
[IETF RFC 3261] | Selection expression | +| Test purpose
ACK is sent with the same Session identifier as in the sent INVITE

Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response an ACK request is sent with the same Call-ID and From headers as in the original INVITE request. | | | | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| SIP header values
INVITE 1
Call-ID:
From: ;tag=

ACK 1
Call-ID:
From: ;tag= | | +| Message flow | | +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE 1
← 200 OK INVITE
→ ACK 1 | +| ISDN interworking | | +| CASE A | | +| SETUP | → INVITE 1 | +| CONNECT | ← 200 OK INVITE
→ ACK 1 | +| CASE B | | +| SETUP | → INVITE 1 | +| CONNECT | ← 200 OK INVITE | +| CONNECT ACKNOWLEDGE | → ACK 1 | +| Apply post test routine | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_011 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
ACK is sent to the address indicated in the 200 OK Contact header | | | | +| Ensure, when the client transaction is in the Calling state , that on receipt of a Success (200 OK) response with no Record-Route header set, an ACK request is sent with the Request-URI set to the Contact URI included in the received final response and with no Route header set. | | | | +| SIP header values
200 OK
Contact:

ACK
ACK sip: SIP 2.0 | | | | + +| Message flow | | +|--------------------------------|------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 200 OK INVITE 1
→ ACK 1 | +| ISDN interworking | | +| CASE A | | +| SETUP | → INVITE | +| CONNECT | ← 200 OK INVITE 1
→ ACK 1 | +| CASE B | | +| SETUP | → INVITE | +| CONNECT | ← 200 OK INVITE 1 | +| CONNECT ACKNOWLEDGE | → ACK 1 | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_012 | Reference
sections 12.2.1.1, 13.2.2.4 and
Figure 5 of [IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| ACK is sent to the address indicated in the Record-Route header with 'lr' parameter | | | | +| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response with a Record-Route header set to a list in which the last element contains lr parameter, an ACK request is sent with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the received final response. | | | | +| SIP header values | | | | +| 200 OK 1
Record-Route: ,
Contact: | | | | +| ACK 1
ACK sip: SIP 2.0
Route: , | | | | +| Message flow | | | | +| End device | | Test equipment | | +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | → INVITE
← 200 OK INVITE
→ ACK 1 | | | +| ISDN interworking | | | | + +| | | +|--------------------------------|-------------------| +| CASE A | | +| SETUP | ➔ INVITE | +| CONNECT | ← 200 OK INVITE 1 | +| | ➔ ACK 1 | +| CASE B | | +| SETUP | ➔ INVITE | +| CONNECT | ← 200 OK INVITE 1 | +| CONNECT ACKNOWLEDGE | ➔ ACK 1 | +| Apply post test routine | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_013 | Reference
section 12.2.1.1, 13.2.2.4,
Figure 5 and 17.1.1.3 of
[IETF RFC 3261] | Selection expression | +| Test purpose
ACK is sent to the address indicated in the Record-Route header without 'lr' parameter | | | | +| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response with a Record-Route header set to a list in which the last element does not contain lr parameter, an ACK request is sent with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. | | | | +| SIP header values
200 OK
Record-Route: ,
Contact:

ACK
ACK sip: SIP 2.0
Route: , | | | | +| Message flow | | | | +| End device | | Test equipment | | +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | | | | +| | ➔ | INVITE | | +| | ← | 200 OK INVITE 1 | | +| | ➔ | ACK 1 | | +| ISDN interworking | | | | +| CASE A | | | | +| SETUP | ➔ | INVITE | | +| CONNECT | ← | 200 OK INVITE 1 | | +| | ➔ | ACK 1 | | +| CASE B | | | | +| SETUP | ➔ | INVITE | | +| CONNECT | ← | 200 OK INVITE 1 | | +| CONNECT ACKNOWLEDGE | ➔ | ACK 1 | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|---------------|------------------------------|--|--|-------|---|--------|--|---|---------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_014 | Reference
section 13.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SDP offer sent in the initial INVITE request | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that while the client is establishing a call, a unique session description offer is sent in the INVITE request to answer the initial offers given in the final 2XX response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
SDP
'm' line
'a' line
200 OK INVITE
SDP
'm' line
'a' line | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 200 OK INVITE

ISDN interworking
SETUP → INVITE
← 200 OK INVITE

Apply post test routine

| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 200 OK INVITE |
ISDN interworking | | | SETUP | → | INVITE | | ← | 200 OK INVITE | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_015 | Reference
section 13.2.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
SDP answer sent in the initial ACK request | | | | +| Ensure that while the client is establishing a call, a unique session description offer is sent in the ACK request to answer the initial offers given in the final 2XX response. | | | | +| SIP header values
200 OK 1
SDP
'm' line
'a' line

ACK 1
SDP
'm' line
'a' line | | | | + +| Message flow | | | +|--------------------------------|------------|-----------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 200 OK INVITE 1 | +| | → | ACK 1 | +| ISDN interworking | | | +| CASE A | | | +| SETUP | → | INVITE | +| CONNECT | ← | 200 OK INVITE 1 | +| | → | ACK 1 | +| CASE B | | | +| SETUP | → | INVITE | +| CONNECT | ← | 200 OK INVITE 1 | +| CONNECT ACKNOWLEDGE | → | ACK 1 | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_016 | Reference
sections 13.2.2.3, 17, 17.1.1.2,
17.1.1.3. and Figure 5 of
[IETF RFC 3261] | Selection expression | +|-------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------|----------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Update Record-Route header

Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response, with a different Record-Route as in previous response, but with the same Via branch parameter and CSeq header method as in the INVITE request, an ACK request is sent with a Route header set according to this new Record-Route. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------| +| SIP header values
200 OK 2
Record-Route:
ACK 2
Route: | +|----------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------------|------------|-----------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE 1 | +| | ← | 200 OK INVITE 1 | +| | → | ACK 1 | +| | ← | 200 OK INVITE 2 | +| | → | ACK 2 | +| ISDN interworking | | | +| SETUP | → | INVITE 1 | +| CONNECT | ← | 200 OK INVITE 1 | +| CONNECT ACKNOWLEDGE | → | ACK 1 | +| | ← | 200 OK INVITE 2 | +| | → | ACK 2 | +| Apply post test routine | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_017 | Reference
section 20.14 and 13.2.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Content-Length header present in the initial INVITE request | | | | +| Ensure that when the client transaction is establishing a call, a Content-Length header set to the size of the body in the message that contains the session description is sent. | | | | +| SIP header values
INVITE
Content-Length:

SDP
'm' line
'a' line | | | | +| Message flow | | | | +| End device | | Test equipment | | +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | → | INVITE | | +| ISDN interworking | | | | +| SETUP | → | INVITE | | +| Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_018 | Reference
section 20.14 and 13.2.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Content Type header indicated SDP | | | | +| Ensure when the client transaction is establishing a call, a Content-Type header in the message that contains the session description is sent. | | | | +| SIP header values
INVITE
Content-Type: application/sdp

SDP
'm' line
'a' line | | | | +| Message flow | | | | +| End device | | Test equipment | | +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | → | INVITE | | +| | ← | 200 OK INVITE 1 | | +| | → | ACK 1 | | +| ISDN interworking | | | | + +| | | | | | | +|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------|---|-------| +| CASE A | | | | | | +| SETUP | ➔ INVITE | | | | | +| CONNECT |
⬅200 OK INVITE 1
➔ACK 1
| ⬅ | 200 OK INVITE 1 | ➔ | ACK 1 | +| ⬅ | 200 OK INVITE 1 | | | | | +| ➔ | ACK 1 | | | | | +| CASE B | | | | | | +| SETUP | ➔ INVITE | | | | | +| CONNECT | ⬅ 200 OK INVITE 1 | | | | | +| CONNECT ACKNOWLEDGE | ➔ ACK 1 | | | | | +| Apply post test routine | | | | | | + +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_019 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------|--|------------|----------------|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-------------|--|--|---------------|--|--|-----|-------------------|--|--|--|---|--------|--|---|---------------|--|---|-----|-------------------|--|--|--|---|--------|--|---|---------------|--------------------------------|--|--| +| Test purpose
Modifying SDP in confirmed dialogue

Ensure that the SUT is able to receive an UPDATE request to modify the SDP in confirmed dialogue. A 200 OK UPDATE with SDP answer is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE/UPDATE
SDP offer 2

200 OK (INVITE/UPDATE)
SDP answer 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Off hook
Dial number ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
⬅ 180 Ringing
200 OK INVITE
ACK

CASE A
⬅ INVITE
➔ 200 OK INVITE
⬅ ACK

CASE B
⬅ UPDATE
➔ 200 OK UPDATE
Apply post test routine
| | | | | End device | Test equipment | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ⬅ | 180 Ringing | | | 200 OK INVITE | | | ACK |
CASE A | | | | ⬅ | INVITE | | ➔ | 200 OK INVITE | | ⬅ | ACK |
CASE B | | | | ⬅ | UPDATE | | ➔ | 200 OK UPDATE | Apply post test routine | | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 200 OK UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +##### 7.2.2.2.3 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|--|---|---------------|---------|--|---|-----------------|--|--|---|-----| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_201 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
200 OK received PSTN XML ProgressIndicator present value x, a CONNECT is sent PI x | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to PI_VA, a CONNECT message is sent to the calling user equipment and a Progress Indicator Information Element is included, the Progress description value is set to PI_VA as described in Table 7.2.2.2.3-1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← 180 (Ringing)
CONNECT ← 200 OK (INVITE)
→ ACK

Apply post test routine

| | | | | End device | | Test equipment | SETUP | | → | INVITE | | | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | ALERTING | | ← | 180 (Ringing) | CONNECT | | ← | 200 OK (INVITE) | | | → | ACK | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | | ← | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_202 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
200 OK received a PSTN XML ProgressIndicator value x present, a CONNECT is sent PI x | | | | +| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to PI_VA, a CONNECT message is sent to the calling user equipment and a Progress Indicator Information Element is included, the Progress description value is set to PI_VA. An additional Progress Indicator Information Element is present and the Progress description value is set to value 4 if a Progress Indicator value 1 was sent before in a ALERTING message as described in Table 7.2.2.2.3-1. | | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| SIP header values
180 (Ringing): no PSTN XML body present
200 OK (INVITE): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000100< | | +| DSS1 Parameter values
CONNECT: | | +| Message flow | | +| End device | Test equipment | +| SETUP | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE | +| ALERTING | ← 180 (Ringing) | +| CONNECT | ← 200 OK (INVITE) | +| | → ACK | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_203 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +|-------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
200 OK received PSTN XML ProgressIndicator present value 7, a CONNECT is sent.

Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to 7 and a CONNECT message is sent to the calling user equipment as described in Table 7.2.2.2.3-1. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
180 (Ringing): PSTN XML body present (PI #7)
200 OK (INVITE): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA< | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------------|-------------------|-----------------------------------| +| DSSI Parameter values | | | +| CONNECT: | | | +| Message flow | | | +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| ALERTING | ← | 180 (Ringing) | +| CONNECT | ← | 200 OK (INVITE) | +| | → | ACK | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_204 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose | | | | +| 200 OK received PSTN XML ProgressIndicator present value 7, a CONNECT is sent. | | | | +| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to 7 and a CONNECT message is sent to the calling user equipment as described in Table 7.2.2.2.3-1. | | | | +| SIP header values | | | | +| 180 (Ringing): PSTN XML body present (PI #7) | | | | +| 200 OK (INVITE): XML body | | | | +| | | | | +| PSTN | | | | +| ProgressIndicator | | | | +| ProgressOctet3 | | | | +| CodingStandard>00< | | | | +| Location>yyyy< | | | | +| ProgressOctet4 | | | | +| ProgressDescription>PI_VA< | | | | +| DSSI Parameter values | | | | +| CONNECT: | | | | +| Message flow | | | | +| | End device | | Test equipment | +| SETUP | → | INVITE | | +| | ← | 407 Proxy Authentication Required | | +| | → | ACK | | +| | → | INVITE | | +| ALERTING | ← | 180 (Ringing) | | +| CONNECT | ← | 200 OK (INVITE) | | +| | → | ACK | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-----|-------------------------|--|--| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_205 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
200 OK received PSTN XML ProgressIndicator present value 7, a CONNECT is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to 7 and a CONNECT message is sent to the calling user equipment. A Progress Indicator Information Element is present the Progress description value is set to value 4 if a Progress Indicator value 1 was sent before in a ALERTING message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180 (Ringing): PSTN XML body present (PI #7)
200 OK (INVITE): XML body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: PI #1
CONNECT: PI #4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← 180 (Ringing)
CONNECT ← 200 OK (INVITE)
→ ACK
Apply post test routine
| | | | | End device | Test equipment | SETUP | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | ALERTING | ← | 180 (Ringing) | CONNECT | ← | 200 OK (INVITE) | | → | ACK | Apply post test routine | | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.2.3-1 – Mapping of progress indicator information element to PSTN XML ProgressIndicator** + +| PI_value | DSS1 Progress Indicator value | XML ProgressIndicator
ProgressDescription | +|----------|--------------------------------------------------------------------------------------------|----------------------------------------------| +| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' | +| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' | +| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' | +| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' | +| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' | +| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|--|---|---------------|---------|--|---|-----------------|--|--|---|-----|-------------------------|--|--|--| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_206 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
PSTN XML body LowLayerCompatibility received in 200 OK. A CONNECT is sent LLC is present

Ensure that on receipt of a LowLayerCompatibility PSTN XML element present in a 200 OK INVITE, a DSS1 CONNECT message is sent to the calling user equipment and a HLC IE is present as described in Table 7.2.2.2.3-2.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE): PSTN XML MIME body




00
ITC_VA


00
10000


| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: HLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 (Ringing)
CONNECT ⬅ 200 OK (INVITE)
➔ ACK
Apply post test routine
| | | | | End device | | Test equipment | SETUP | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | ALERTING | | ⬅ | 180 (Ringing) | CONNECT | | ⬅ | 200 OK (INVITE) | | | ➔ | ACK | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.2.3-2 – Mapping of low layer compatibility to PSTN XML +LowLayerCompatibility** + +| ITC_value | LLC information transfer capability | XML LLC InformationTransferCabability | +|-----------|-------------------------------------|---------------------------------------| +| ITC_VA_1 | Speech | '00000' | +| ITC_VA_2 | 3,1 kHz audio | '10000' | +| ITC_VA_3 | Unrestricted digital info | '01001' | +| ITC_VA_3 | 7 kHz audio | '10001' | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-----|--------------------------------|--|--| +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_207 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
PSTN XML body BearerCapability received in 200 OK CONNECT is sent BC present

Fallback connection type indicated in the SETUP. Ensure that on receipt of a 200 OK (INVITE) that contains a PSTN XML BearerCapability indicating fallback, a CONNECT message is sent to the calling user equipment and a Bearer Capability Information Element is present set to the value of the received BearerCapability XML element as described in Table 5.2.1.3-5. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE): PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>ITC_VA<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5>
Layer1Identification>01<
UserInfoLayer1Protocol>00011<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<

SDP: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements

CONNECT: BC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 (Ringing)
CONNECT ⬅ 200 OK (INVITE)
➔ ACK
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 (Ringing) | CONNECT | ⬅ | 200 OK (INVITE) | | ➔ | ACK | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.2.3-3 – Mapping of bearer capability to PSTN XML BearerCapability** + +| ITC_value | BC information transfer capability | XML InformationTransferCapability | SDP m - line: first stated codec | +|-----------|-----------------------------------------|-----------------------------------|----------------------------------| +| ITC_VA_1 | Speech | '00000' | 0 or 8 | +| ITC_VA_2 | 3,1 kHz audio | '10000' | 0 or 8 | +| ITC_VA_3 | Unrestricted digital inf.
W/tone/ann | '10001' | CLEARMODE | + +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_208 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-----| +| Test purpose
200 OK received no PSTN XML ProgressIndicator present, a CONNECT BC included is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Fall-back connection type indicated in the SETUP. Ensure that on receipt of a 200 OK (INVITE) and no PSTN XML body is present, a CONNECT message is sent to the calling user equipment. A Bearer Capability Information Element is present set to the value speech or audio 3.1 kHz | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE):
no XML body present

SDP: | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements

CONNECT: BC speech or audio 3.1 kHz | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 (Ringing)
CONNECT ⬅ 200 OK (INVITE)
➔ ACK

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 (Ringing) | CONNECT | ⬅ | 200 OK (INVITE) | | ➔ | ACK | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_209 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|---------------|--|---------|---|-----------------|--|--|---|-----|--| +| Test purpose
Fallback information received as PSTN XML body HLC in the 200 a CONNECT contains the fall-back information

Fallback connection type indicated in the SETUP. Ensure that the SUT on receipt of a HighLayerCapability value set to HLC_VA and ProgressIndicator No. 5 PSTN XML body, a CONNECT message is sent to the calling user equipment. The CONNECT message contains a HLC Information Element derived from the received PSTN XML HighLayerCapability and a Progress Indicator Information Element derived from the received PSTN XML HighLayerCompatibility as described in Table 7.2.2.2.3-4.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000101<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements

CONNECT: BC speech or audio 3.1 kHz | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ 180 (Ringing)
CONNECT ⬅ 200 OK (INVITE)
➔ ACK

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | ALERTING | ⬅ | 180 (Ringing) | | CONNECT | ⬅ | 200 OK (INVITE) | | | ➔ | ACK | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.2.3-4 – Mapping of high layer compatibility information element to PSTN XML HighLayerCharacteristic** + +| HLC_value | DSS1 high layer characteristics identification | XML HighLayerCharacteristic | +|-----------|------------------------------------------------------------------------|-----------------------------| +| HLC_VA_1 | Telephony | '0000001' | +| HLC_VA_2 | Facsimile Group 2/3 | '0000100' | +| HLC_VA_3 | Facsimile Group 4 Class I | '0100001' | +| HLC_VA_4 | Facsimile service Group 4, Classes II and III | '0100100' | +| HLC_VA_5 | Syntax based Videotex | '0110010' | +| HLC_VA_6 | International Videotex interworking via gateways or interworking units | '0110011' | +| HLC_VA_7 | Telex service | '0110101' | +| HLC_VA_8 | FTAM application | '1000010' | +| HLC_VA_9 | Videotelephony | '1100000' | + +##### 7.2.2.2.3 Call release + +###### 7.2.2.2.3.1 Release initiated by the originating user + +###### 7.2.2.2.3.1.1 SIP basic procedures + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|--|--| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_001 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | | | +| Test purpose
To header in BYE is used from the last final response | | | | | | +| Ensure that once a dialogue has been established the IUT sends a BYE request to release it where a To header is set to the same value as in the last received final response. | | | | | | +| SIP header values
200 OK
To:
BYE
To: | | | | | | +| Message flow | | | | | | +| End device | | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | | | | | | +| | | → INVITE | | | | +| | | ← 180 Ringing | | | | +| | | ← 200 OK INVITE | | | | +| | | → ACK | | | | +| On hook | | | | | | +| | | → BYE | | | | +| | | ← 200 OK BYE | | | | +| ISDN interworking | | | | | | +| CASE A | | | | | | +| SETUP | | | | | | +| | | → INVITE | | | | +| ALERTING | | | | | | +| | | ← 180 Ringing | | | | +| CONNECT | | | | | | +| | | ← 200 OK INVITE | | | | +| DISCONNECT | | | | | | +| | | → ACK | | | | +| RELEASE | | | | | | +| | | → BYE | | | | +| RELEASE COMPLETE | | | | | | +| | | ← 200 OK BYE | | | | +| | | → | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|---------------|--|--|---|-----|---------|--|---|-----|--|--|---|------------|--------------------------|--|--|--|-------|--|---|--------|---------|--|---|---------------|--|--|---|-----|------------|--|---|-----|---------|--|---|------------|------------------|--|---|--| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_002 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
BYE is sent without To tag | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that if a dialog had been established with a final response in which the 'tag' in the To header was omitted, to release it the IUT sends a BYE request with an identical To header without 'tag' value. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK
To:
BYE
To: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 200 OK INVITE
➔ ACK
On hook ➔ BYE
⬅ 200 OK BYE
ISDN interworking
SETUP ➔ INVITE
CONNECT ⬅ 200 OK INVITE
➔ ACK
DISCONNECT ➔ BYE
RELEASE ⬅ 200 OK BYE
RELEASE COMPLETE ➔
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 200 OK INVITE | | | ➔ | ACK | On hook | | ➔ | BYE | | | ⬅ | 200 OK BYE | ISDN interworking | | | | SETUP | | ➔ | INVITE | CONNECT | | ⬅ | 200 OK INVITE | | | ➔ | ACK | DISCONNECT | | ➔ | BYE | RELEASE | | ⬅ | 200 OK BYE | RELEASE COMPLETE | | ➔ | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | | ➔ | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | | ➔ | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | | ⬅ | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_003 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | +| Test purpose
To header in BYE is used from the last final response | | | | +| Ensure that the IUT, once a dialogue has been established to release, it sends a BYE request with a To header set to the same value as in the last received final response. | | | | +| SIP header values
200 OK
To:
BYE
To: | | | | + +| Message flow | | | +|--------------------------|------------|----------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 180 Ringing | +| | ← | 200 OK INVITE | +| | → | ACK | +| On hook | → | BYE | +| | ← | 200 OK BYE | +| ISDN interworking | | | +| SETUP | → | INVITE | +| ALERTING | ← | 180 Ringing | +| CONNECT | ← | 200 OK INVITE | +| | → | ACK | +| DISCONNECT | → | BYE | +| RELEASE | ← | 200 OK BYE | +| RELEASE COMPLETE | → | | + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|--|--| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_004 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | | | +| Test purpose | | | | | | +| Call-ID is set to the value as in the original INVITE | | | | | | +| Ensure that the IUT, once a dialogue has been established to release, it sends a BYE request with the same Call-ID, From headers as in the original INVITE message. | | | | | | +| SIP header values | | | | | | +| 200 OK
Call-ID: | | | | | | +| BYE
Call-ID: | | | | | | +| Message flow | | | | | | +| | End device | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | → | INVITE | | | | +| | ← | 180 Ringing | | | | +| | ← | 200 OK INVITE | | | | +| | → | ACK | | | | +| On hook | → | BYE | | | | +| | ← | 200 OK BYE | | | | +| ISDN interworking | | | | | | +| SETUP | → | INVITE | | | | +| ALERTING | ← | 180 Ringing | | | | +| CONNECT | ← | 200 OK INVITE | | | | +| | → | ACK | | | | +| DISCONNECT | → | BYE | | | | +| RELEASE | ← | 200 OK BYE | | | | +| RELEASE COMPLETE | → | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|--|---|---------------|--|---|-----|---------|---|-----|--|---|------------|--------------------------|--|--|-------|---|--------|----------|---|-------------|---------|---|---------------|--|---|-----|------------|---|-----|---------|---|------------|------------------|---|--| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_005 | Reference
section 12.2.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CSeq in BYE is incremented | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, once a dialogue has been established to release, it sends a BYE request with an increment of one CSeq value, a method field in the CSeq header set to "BYE". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
CSeq: INVITE
BYE
CSeq: BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK
On hook → BYE
← 200 OK BYE
ISDN interworking
SETUP → INVITE
ALERTING ← 180 Ringing
CONNECT ← 200 OK INVITE
→ ACK
DISCONNECT → BYE
RELEASE ← 200 OK BYE
RELEASE COMPLETE →
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 180 Ringing | | ← | 200 OK INVITE | | → | ACK | On hook | → | BYE | | ← | 200 OK BYE | ISDN interworking | | | SETUP | → | INVITE | ALERTING | ← | 180 Ringing | CONNECT | ← | 200 OK INVITE | | → | ACK | DISCONNECT | → | BYE | RELEASE | ← | 200 OK BYE | RELEASE COMPLETE | → | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_006 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | +| Test purpose
BYE is sent to the address indicated in the 200 OK Contact header | | | | +| Ensure that the IUT, once a dialogue has been established with a Success (200 OK) response including no Record Route header set, to release it, sends a BYE request with the Request URI set to the Contact URI included in the received final response and with no Route header set. | | | | +| SIP header values
200 OK
Contact:
BYE: SIP/2.0 | | | | + +| Message flow | | +|--------------------------|-------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK | +| On hook | → BYE
← 200 OK BYE | +| ISDN interworking | | +| SETUP | → INVITE | +| ALERTING | ← 180 Ringing | +| CONNECT | ← 200 OK INVITE
→ ACK | +| DISCONNECT | → BYE | +| RELEASE | ← 200 OK BYE | +| RELEASE COMPLETE | → | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_007 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | +| Test purpose
BYE is sent to the address indicated in the Record-Route header with 'lr' parameter

Ensure that the IUT, once a dialogue has been established with a Success (200 OK) response including a Record-Route header set to a list in which the last element contains lr parameter, to release the call, sends a BYE request with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the received final response. | | | | +| SIP header values
200 OK
Record-Route: ,
Contact:

BYE
BYE sip: SIP 2.0
Route: , | | | | + +| Message flow | | | +|--------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 180 Ringing | +| | ← | 200 OK INVITE | +| | → | ACK | +| On hook | → | BYE | +| | ← | 200 OK BYE | +| ISDN interworking | | | +| SETUP | → | INVITE | +| ALERTING | ← | 180 Ringing | +| CONNECT | ← | 200 OK INVITE | +| | → | ACK | +| DISCONNECT | → | BYE | +| RELEASE | ← | 200 OK BYE | +| RELEASE COMPLETE | → | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_008 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Route set in BYE is derived from the Record-Route headers in revers order | | | | +| Ensure that the IUT, once a dialogue has been established with a Success (200 OK) response including a Record-Route header set to a list in which the last element does not contain lr parameter, to release the call, sends an BYE request with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. | | | | +| SIP header values
200 OK
Record-Route: ,
Contact:

BYE
BYE sip: SIP 2.0
Route: , | | | | + +| Message flow | | +|--------------------------|-------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK | +| On hook | → BYE
← 200 OK BYE | +| ISDN interworking | | +| SETUP | → INVITE | +| ALERTING | ← 180 Ringing | +| CONNECT | ← 200 OK INVITE
→ ACK | +| DISCONNECT | → BYE | +| RELEASE | ← 200 OK BYE | +| RELEASE COMPLETE | → | + +| | | | | +|----------------------------------------------------------------|------------|------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_009 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | +|----------------------------------------------------------------|------------|------------------------------------------------------------|----------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

Session in confirmed dialogue is terminated by sending a BYE message

Ensure that the IUT, when a dialogue has been established, having sent a BYE request, on receipt of a (200 OK) response considers the session and the dialogue terminated.

| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|--------------------------| +| SIP header values | +|--------------------------| + +| Message flow | | +|--------------------------|-----------------------------------------------------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE 1
← 180 Ringing
← 200 OK INVITE
→ ACK | +| On hook | → BYE
Start timer K
← 200 OK BYE
Timeout timer K
← BYE
→ 481 Call Leg Does Not Exist | + +| | | | +|--------------------------|-------------------|-------------------------------| +| ISDN interworking | | | +| SETUP | → | → INVITE 1 | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE | +| | | → ACK | +| DISCONNECT | → Start timer K | → BYE | +| RELEASE | ← | ← 200 OK BYE | +| RELEASE COMPLETE | → Timeout timer K | | +| | ← | ← BYE | +| | → | → 481 Call Leg Does Not Exist | + +| | | | | +|----------------------------------------------------------------|------------|----------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_010 | Reference
section 12.2.1.1 and 15.1.1 of
[IETF RFC 3261] | Selection expression | +|----------------------------------------------------------------|------------|----------------------------------------------------------------|----------------------| + +###### **Test purpose** + +*BYE received after 200 OK BYE was sent* + +Ensure that the IUT, when a dialogue has been established, having sent a BYE request, on receipt of a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) considers the session and the dialogue terminated. + +###### **SIP header values** + +###### **Message flow** + +| | End device | Test equipment | +|--------------------------|-------------------|-------------------------------| +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE 1 | +| | ← | 180 Ringing | +| | ← | 200 OK INVITE | +| | → | ACK | +| On hook | → | BYE | +| | Start timer K | | +| | ← | 200 OK BYE | +| | Timeout timer K | | +| | ← | ← BYE | +| | → | → 481 Call Leg Does Not Exist | +| ISDN interworking | | | +| SETUP | → | → INVITE 1 | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE | +| | | → ACK | +| DISCONNECT | → Start timer K | → BYE | +| RELEASE | ← | ← 200 OK BYE | +| RELEASE COMPLETE | → Timeout timer K | | +| | ← | ← BYE | +| | → | → 481 Call Leg Does Not Exist | + +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_011 | Reference
section 15 and 9.1, Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|---------|---|--------|--|---|---------------|--|---|------------------------|--|---|-----|------------------------------|--|--|-------|---|----------|--|--|--------------|---------|---|--------------|------------------|---|---------------------|--|--|--------------------------|--|--|-------| +| Test purpose
Session in early dialogue is terminated by sending a CANCEL or BYE message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number→INVITE
←100 Trying
On hook→CANCEL
←200 OK CANCEL
←487 Request Terminated
→ACK

ISDN interworking
SETUP→→ INVITE
← 100 Trying
RELEASE→→ CANCEL/BYE
RELEASE COMPLETE←← 200 OK CANCEL/BYE
← 487 Request Terminated
→ ACK
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 100 Trying | On hook | → | CANCEL | | ← | 200 OK CANCEL | | ← | 487 Request Terminated | | → | ACK |
ISDN interworking | | | SETUP | → | → INVITE | | | ← 100 Trying | RELEASE | → | → CANCEL/BYE | RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | ← 487 Request Terminated | | | → ACK | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | → | CANCEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK CANCEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | → | → CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_012 | Reference
section 15 and 9.1, Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Header in the CANCEL or BYE message | | | | +| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call, sends a CANCEL/BYE request with the same Request-URI, Call-ID, From, To headers as in the original INVITE message. | | | | +| SIP header values | | | | +| INVITE
INVITE sip:
From: sip:;tag=
To: sip: sip:
Call-ID:

CANCEL
INVITE sip:
From: sip:;tag=
To: sip: sip:
Call-ID: | | | | + +| Message flow | | | +|--------------------------|-------------------|--------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 100 Trying | +| On hook | → | CANCEL/BYE | +| | ← | 200 OK CANCEL/BYE | +| | ← | 487 Request Terminated | +| | → | ACK | +| ISDN interworking | | | +| SETUP | → | → INVITE | +| | | ← 100 Trying | +| RELEASE | → | → CANCEL/BYE | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | +| | | ← 487 Request Terminated | +| | | → ACK | + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------|----------------------|--|--| +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_013 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | +| Test purpose
CSeq method parameter in CANCEL or BYE | | | | | | +| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, sends a CANCEL request with the same numeric part of CSeq as in the original INVITE message with a method field in the CSeq header set to "CANCEL/BYE ". | | | | | | +| SIP header values | | | | | | +| INVITE
Call-ID: INVITE | | | | | | +| CANCEL
Call-ID: CANCEL | | | | | | +| Message flow | | | | | | +| | End device | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | → | INVITE | | | | +| | ← | 100 Trying | | | | +| On hook | → | CANCEL/BYE | | | | +| | ← | 200 OK CANCEL/BYE | | | | +| | ← | 487 Request Terminated | | | | +| | → | ACK | | | | +| ISDN interworking | | | | | | +| SETUP | → | → INVITE | | | | +| | | ← 100 Trying | | | | +| RELEASE | → | → CANCEL/BYE | | | | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | | +| | | ← 487 Request Terminated | | | | +| | | → ACK | | | | + +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_014 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|---------|---|------------|--|---|-------------------|--|---|------------------------|--|---|-----|------------------------------|--|--|-------|---|----------|--|--|--------------|---------|---|--------------|------------------|---|---------------------|--|--|--------------------------|--|--|-------| +| Test purpose
CANCEL or BYE contains the Via header from the initial INVITE request

Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, sends a CANCEL/BYE request with a single Via header value matching the top Via value of the Via header of the original INVITE message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Via: SIP/2.0/ ;branch=

CANCEL
Via: SIP/2.0/ ;branch= | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 100 Trying
On hook ➔ CANCEL/BYE
⬅ 200 OK CANCEL/BYE
⬅ 487 Request Terminated
➔ ACK

ISDN interworking
SETUP ➔ ➔ INVITE
⬅ 100 Trying
RELEASE ➔ ➔ CANCEL/BYE
RELEASE COMPLETE ⬅ ⬅ 200 OK CANCEL/BYE
⬅ 487 Request Terminated
➔ ACK
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | On hook | ➔ | CANCEL/BYE | | ⬅ | 200 OK CANCEL/BYE | | ⬅ | 487 Request Terminated | | ➔ | ACK |
ISDN interworking | | | SETUP | ➔ | ➔ INVITE | | | ⬅ 100 Trying | RELEASE | ➔ | ➔ CANCEL/BYE | RELEASE COMPLETE | ⬅ | ⬅ 200 OK CANCEL/BYE | | | ⬅ 487 Request Terminated | | | ➔ ACK | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | ➔ | CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | ➔ | ➔ CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | ⬅ | ⬅ 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_015 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| +| Test purpose
The CANCEL or BYE does not contain a Require or Proxy Require header

Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call, sends a CANCEL/BYE request without Require or Proxy-Require header. | | | | +| SIP header values
CANCEL
Require: [not present]
Proxy-Require: [not present] | | | | + +| Message flow | | | +|--------------------------|-------------------|--------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 100 Trying | +| On hook | → | CANCEL/BYE | +| | ← | 200 OK CANCEL/BYE | +| | ← | 487 Request Terminated | +| | → | ACK | +| ISDN interworking | | | +| SETUP | → | → INVITE | +| | | ← 100 Trying | +| RELEASE | → | → CANCEL/BYE | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | +| | | ← 487 Request Terminated | +| | | → ACK | + +| | | | | +|----------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_016 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|----------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

A CANCEL or BYE is sent after 180 was received

Ensure that the IUT, having received a 180 Ringing provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request.

| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------|-------------------|--------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE | +| | ← | 180 Ringing | +| On hook | → | CANCEL/BYE | +| | ← | 200 OK CANCEL/BYE | +| | ← | 487 Request Terminated | +| | → | ACK | +| ISDN interworking | | | +| SETUP | → | → INVITE | +| | | ← 180 Ringing | +| RELEASE | → | → CANCEL/BYE | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | +| | | ← 487 Request Terminated | +| | | → ACK | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_017 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| A CANCEL or BYE is sent after 181 was received | | | | +| Ensure that the IUT, having received a 181 Call Is Being Forwarded provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | | + + + +| Message flow | | | | | | +|--------------------------|---|---------------------------|--|--|--| +| End device | | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | | → INVITE | | | | +| | | ← Call Is Being Forwarded | | | | +| On hook | | → CANCEL/BYE | | | | +| | | ← 200 OK CANCEL/BYE | | | | +| | | ← 487 Request Terminated | | | | +| | | → ACK | | | | +| ISDN interworking | | | | | | +| SETUP | → | → INVITE | | | | +| | | ← 180 Ringing | | | | +| RELEASE | → | → CANCEL/BYE | | | | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | | +| | | ← 487 Request Terminated | | | | +| | | → ACK | | | | + +| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_018 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | +|------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|--|--| +| Test purpose | | | | | | +| A CANCEL or BYE is sent after 182 was received | | | | | | +| Ensure that the IUT, having received a 182 Queued provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | | | | +| Message flow | | | | | | +| End device | | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | | → INVITE | | | | +| | | ← 182 Queued | | | | +| On hook | | → CANCEL/BYE | | | | +| | | ← 200 OK CANCEL/BYE | | | | +| | | ← 487 Request Terminated | | | | +| | | → ACK | | | | + +| | | | +|--------------------------|---|----------------------------------------------------------| +| ISDN interworking | | | +| SETUP | → | → INVITE
← 182 Queued | +| RELEASE | → | → CANCEL/BYE | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE
← 487 Request Terminated
→ ACK | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------|----------------------|--|--| +| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_019 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | +| Test purpose | | | | | | +| A CANCEL or BYE is sent after 183 was received | | | | | | +| Ensure that the IUT, having received a 183 Session Progress provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | | | | +| Message flow | | | | | | +| End device | | Test equipment | | | | +| Interworking POTS | | | | | | +| Off hook | | | | | | +| Dial number | | | | | | +| | | → INVITE
← 183 Session Progress | | | | +| On hook | | | | | | +| | | → CANCEL/BYE
← 200 OK CANCEL/BYE
← 487 Request Terminated
→ ACK | | | | +| ISDN interworking | | | | | | +| SETUP | → | → INVITE
← 183 Session Progress | | | | +| RELEASE | → | → CANCEL/BYE | | | | +| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE
← 487 Request Terminated
→ ACK | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| +| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_020 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| A CANCEL or BYE is sent a 200 OK INVITE was received at the same time | | | | +| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call having sent a CANCEL/BYE request, on receipt of a 2XX response to the original INVITE sends an ACK request. | | | | +| SIP header values | | | | + +| Message flow | | | +|--------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | ➔ | INVITE | +| | ➔ | 100 Trying | +| On hook | ➔ | CANCEL/BYE | +| | ➔ | 200 OK INVITE | +| | ➔ | ACK | +| | ➔ | BYE | +| | ➔ | 200 OK BYE | +| ISDN interworking | | | +| SETUP | ➔ | ➔ INVITE | +| | | ➔ 100 Trying | +| RELEASE | ➔ | ➔ CANCEL/BYE | +| RELEASE COMPLETE | ➔ | ➔ 200 OK INVITE | +| | | ➔ ACK | +| | | ➔ BYE | +| | | ➔ 200 OK BYE | + +##### 7.2.2.3.2 Release initiated by the terminating user + +###### 7.2.2.3.2.1 SIP basic procedures + +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_001 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------|--------------------------------------|---------------------|--|--|--|-------------------|-----------------------|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-------------|--------------|---|---------------|--|---|-----|------------|---|-----|--|---|------------| +| Test purpose
A BYE is received, a 200 OK BYE is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, in the confirmed state when a BYE is received, a 200 OK BYE is sent. The connection is terminated. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Message flow
End device Test equipment
Off hook
Dial number ➔ INVITE
➔ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
➔ 180 Ringing
Conversation ➔ 200 OK INVITE
➔ ACK
Terminated ➔ BYE
➔ 200 OK BYE
| | | | Message flow | | | | End device | Test equipment | Off hook | | | Dial number | ➔ | INVITE | | ➔ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ➔ | 180 Ringing | Conversation | ➔ | 200 OK INVITE | | ➔ | ACK | Terminated | ➔ | BYE | | ➔ | 200 OK BYE | +| Message flow | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Conversation | ➔ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Terminated | ➔ | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-------------|--|---|--------------------|--|---|-----| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_002 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Receipt of a final response before a provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 180 Ringing was received and the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
← 180 Ringing
← SIP_FINAL_RESPONSE
➔ ACK
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ← | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ← | 180 Ringing | | ← | SIP_FINAL_RESPONSE | | ➔ | ACK | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-----------------------------|--|---|--------------------|--|---|-----| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_003 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Receipt of a final response after a 181 Call Is Being Forwarded provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 181 Call Is Being Forwarded was received and the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
← 181 Call Is Being Forwarded
← SIP_FINAL_RESPONSE
➔ ACK
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ← | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ← | 181 Call Is Being Forwarded | | ← | SIP_FINAL_RESPONSE | | ➔ | ACK | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 181 Call Is Being Forwarded | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|------------|--|---|--------------------|--|---|-----| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_004 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Receipt of a final response after a 182 Queued provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 182 Queued was received and the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
← 182 Queued
→ SIP_FINAL_RESPONSE
→ ACK
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | | ← | 182 Queued | | → | SIP_FINAL_RESPONSE | | → | ACK | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 182 Queued | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|----------------------|--|---|--------------------|--|---|-----| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_005 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Receipt of a final response after a 183 Session Progress provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 183 Session Progress was received, the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
← 183 Session Progress
→ SIP_FINAL_RESPONSE
→ ACK
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | | ← | 183 Session Progress | | → | SIP_FINAL_RESPONSE | | → | ACK | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.2.3.2-1 – 3xx/4xx/5xx/6xx final response** + +| CAUSE_VA | ←DISCONNECT (cause value) | ←SIP_FINAL_RESPONSE | +|-----------------|----------------------------------------------------------------|-------------------------------------| +| CAUSE_VA_01 | 127 (interworking unspecified) | 400 Bad Request | +| CAUSE_VA_02 | 127 (interworking unspecified) | 401 Unauthorized | +| CAUSE_VA_03 | 127 (interworking unspecified) | 402 Payment Required | +| CAUSE_VA_04 | 127 (interworking unspecified) | 403 Forbidden | +| CAUSE_VA_05 | 1 (Unallocated number) | 404 Not Found | +| CAUSE_VA_06 | 127 (interworking unspecified) | 405 Method Not Allowed | +| CAUSE_VA_07 | 127 (interworking unspecified) | 406 Not Acceptable | +| CAUSE_VA_08 | 127 (interworking unspecified) | 407 Proxy authentication required | +| CAUSE_VA_09 | 127 (interworking unspecified) | 408 Request Timeout | +| CAUSE_VA_10 | 22 (Number changed) | 410 Gone | +| CAUSE_VA_11 | 127 (interworking unspecified) | 413 Request Entity too long | +| CAUSE_VA_12 | 127 (interworking unspecified) | 414 Request-URI too long | +| CAUSE_VA_13 | 127 (interworking unspecified) | 415 Unsupported Media type | +| CAUSE_VA_14 | 127 (interworking unspecified) | 416 Unsupported URI scheme | +| CAUSE_VA_15 | 127 (interworking unspecified) | 420 Bad Extension | +| CAUSE_VA_16 | 127 (interworking unspecified) | 421 Extension required | +| CAUSE_VA_17 | 127 (interworking unspecified) | 423 Interval Too Brief | +| CAUSE_VA_18 | 24 (call rejected due to ACR supplementary service) | 433 Anonymity Disallowed | +| CAUSE_VA_19 | 20 Subscriber absent | 480 Temporarily Unavailable | +| CAUSE_VA_20 | 127 (interworking unspecified) | 481 Call/Transaction does not exist | +| CAUSE_VA_21 | 127 (interworking unspecified) | 482 Loop detected | +| CAUSE_VA_22 | 127 (interworking unspecified) | 483 Too many hops | +| CAUSE_VA_23 | 28 (Invalid Number format) | 484 Address Incomplete | +| CAUSE_VA_24 | 127 (interworking unspecified) | 485 Ambiguous | +| CAUSE_VA_25 | 17 (User busy) | 486 Busy Here | +| CAUSE_VA_26 | 127 (Interworking unspecified) or not interworked.
(Note 1) | 487 Request terminated | +| CAUSE_VA_27 | 127 (interworking unspecified) | 488 Not acceptable here | +| CAUSE_VA_28 | 127 (interworking unspecified) | 493 Undecipherable | +| CAUSE_VA_29 | 127 (interworking unspecified) | 500 Server Internal error | +| CAUSE_VA_30 | 127 (interworking unspecified) | 501 Not implemented | +| CAUSE_VA_31 | 127 (interworking unspecified) | 502 Bad Gateway | +| CAUSE_VA_32 | 127 (interworking unspecified) | 503 Service Unavailable | +| CAUSE_VA_33 | 127 (interworking unspecified) | 504 Server timeout | +| CAUSE_VA_34 | 127 (interworking unspecified) | 505 Version not supported | + +**Table 7.2.2.3.2-1 – 3xx/4xx/5xx/6xx final response** + +| CAUSE_VA | ←DISCONNECT (cause value) | ←SIP_FINAL_RESPONSE | +|-------------|--------------------------------|-----------------------------| +| CAUSE_VA_35 | 127 (interworking unspecified) | 513 Message too large | +| CAUSE_VA_36 | 127 (interworking unspecified) | 580 Precondition failure | +| CAUSE_VA_37 | 17 (User busy) | 600 Busy Everywhere | +| CAUSE_VA_38 | 21 (Call rejected) | 603 Decline | +| CAUSE_VA_39 | 1 (unallocated number) | 604 Does not exist anywhere | +| CAUSE_VA_40 | 127 (interworking unspecified) | 606 Not acceptable | + +###### 7.2.2.3.2.3 Test purposes for ISDN + +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_101 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|--|------------|--|----------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|---|---|-------------|---------|---|---|---------------|--|--|---|-----|------------|---|---|-----|---------|---|---|------------|------------------|---|--|--| +| Test purpose
Receipt of BYE, a DSSI DISCONNECT is sent cause value 16

Ensure that on receipt of a BYE request a DSS1 DISCONNECT is sent to the calling user equipment. The cause value of the DISCONNECT is set to '16'. The location of the cause IE is set to '1010' network beyond interworking point. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
DISCONNECT: Cause IE cause value=16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← ← 180 Ringing
CONNECT ← ← 200 OK INVITE
→ ACK
DISCONNECT ← ← BYE
RELEASE → → 200 OK BYE
RELEASE COMPLETE →
| | | | | End device | | Test equipment | SETUP | → | → | INVITE | | | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | ALERTING | ← | ← | 180 Ringing | CONNECT | ← | ← | 200 OK INVITE | | | → | ACK | DISCONNECT | ← | ← | BYE | RELEASE | → | → | 200 OK BYE | RELEASE COMPLETE | → | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | ← | ← | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | → | → | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_102 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
Receipt of a final response before a provisional response was received Reason header not included.

Ensure that when a final response is received before an early dialogue was established and if no Reason header is included, a DISCONNECT is sent to the calling user equipment. The cause value of the DISCONNECT is derived according the mapping in Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | | + +| | | | +|-----------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------| +| SIP header values | | | +| DSS1 Parameter values
DISCONNECT: Cause IE cause value = CAUSE_VA | | | +| Message flow | | | +| | End device | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| DISCONNECT | ← | ← SIP_FINAL_RESPONSE | +| RELEASE | → | → ACK | +| RELEASE COMPLETE | → | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|----------------------------------------------------------------------| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_103 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
Receipt of a final response after a 180 provisional response was received Reason header not included. | | | | +| Ensure that when a final response is received after a 180 Ringing is received to establish an early dialogue and a no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping in Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | | +| SIP header values | | | | +| DSS1 Parameter values
DISCONNECT: Cause IE cause value = CAUSE_VA | | | | +| Message flow | | | | +| | End device | | Test equipment | +| SETUP | → | | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | | ← 180 Ringing | +| DISCONNECT | ← | | ← SIP_FINAL_RESPONSE | +| RELEASE | → | | → ACK | +| RELEASE COMPLETE | → | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_104 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
Receipt of a final response after a 181 provisional response was received Reason header not included. | | | | +| Ensure that when a final response is received after a 181 Call Is Being Forwarded is received to establish an early dialogue and a no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point | | | | +| SIP header values | | | | + +| | | | +|---------------------------------------------|-------------------|-------------------------------------| +| DSSI Parameter values | | | +| DISCONNECT: Cause IE cause value = CAUSE_VA | | | +| Message flow | | | +| | End device | Test equipment | +| SETUP | → | → INVITE | +| | | ← 407 Proxy Authentication Required | +| | | → ACK | +| | | → INVITE | +| NOTIFY | ← | ← 181 Call Is Being Forwarded | +| DISCONNECT | ← | ← SIP_FINAL_RESPONSE | +| RELEASE | → | → ACK | +| RELEASE COMPLETE | → | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_105 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose | | | | +| Receipt of a final response after a 182 provisional response was received Reason header not included. | | | | +| Ensure that when a final response is received after a 182 Queued is received to establish an early dialogue and no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | | +| SIP header values | | | | +| DSSI Parameter values | | | | +| DISCONNECT: Cause IE cause value = CAUSE_VA | | | | +| Message flow | | | | +| | End device | | Test equipment | +| SETUP | → | | → INVITE | +| | | | ← 407 Proxy Authentication Required | +| | | | → ACK | +| | | | → INVITE | +| NOTIFY/ CALL PROCEEDING | ← | | ← 182 Queued | +| DISCONNECT | ← | | ← SIP_FINAL_RESPONSE | +| RELEASE | → | | → ACK | +| RELEASE COMPLETE | → | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_106 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose | | | | +| Receipt of a final response after a 183 provisional response was received Reason header not included. | | | | +| Ensure that when a final response is received after a 183 Session Progress is received to establish an early dialogue and a no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | | +| SIP header values | | | | + +| | | | +|---------------------------------------------|-------------------|-------------------------------------| +| DSS1 Parameter values | | | +| DISCONNECT: Cause IE cause value = CAUSE_VA | | | +| Message flow | | | +| | End device | Test equipment | +| SETUP | → | → INVITE | +| | | ← 407 Proxy Authentication Required | +| | | → ACK | +| | | → INVITE | +| CALL PROCEEDING | ← | ← 183 Session Progress | +| DISCONNECT | ← | ← SIP_FINAL_RESPONSE | +| RELEASE | → | → ACK | +| RELEASE COMPLETE | → | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------| +| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_107 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose | | | | +| DISCONNECT received, a BYE is sent | | | | +| Ensure that the IUT, while the dialogue is in a confirmed state, of an ISDN DISCONNECT message sends a BYE request. | | | | +| SIP header values | | | | +| DSS1 Parameter values | | | | +| DISCONNECT: Cause IE cause value= | | | | +| Message flow | | | | +| | End device | | Test equipment | +| Interworking POTS | | | | +| SETUP | → | | → INVITE | +| | | | ← 407 Proxy Authentication Required | +| | | | → ACK | +| | | | → INVITE | +| | ← | | ← | +| DISCONNECT | ← | | ← SIP_FINAL_RESPONSE | +| RELEASE | → | | → ACK | +| RELEASE COMPLETE | → | | | + +#### 7.2.2.4 Timers + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_001 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +| Test purpose | | | | +| UDP: INVITE is repeated if timer T1 expires | | | | +| Ensure that the IUT, when an INVITE client transaction is in the Calling state repeats its INVITE request on the timeout condition of timer A set with a value of T1 if an unreliable transport (UDP) is used. | | | | + +| Message flow | | | +|--------------------------------|-------------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | Start timer A
1*T1 | → INVITE | +| Dial number | Timeout timer A | → INVITE | +| ISDN interworking | | | +| SETUP | → Start timer A
1*T1 | → INVITE | +| | Timeout timer A | → INVITE | +| Apply post test routine | | | + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_002 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| + +| Test purpose | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------| +| TCP: INVITE is not repeated if timer T1 expires | | | +| Ensure that the IUT, when an INVITE client transaction is in the Calling state, does not repeat its INVITE request on the timeout condition of timer A set with a value of T1 if a reliable transport (TCP) is used. | | | +| Message flow | | | +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | Start timer A
1*T1 | → INVITE | +| | Timeout timer A | | +| ISDN interworking | | | +| SETUP | → Start timer A
1*T1 | → INVITE | +| | Timeout timer A | | +| Apply post test routine | | | + +| | | | | +|--------------------|------------|--------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_003 | Reference
section 17.1.1.1 and
Annex A/[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|--------------------------------------------------------------|--------------------------------------| + +| Test purpose | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| UDP: INVITE is retransmitted if timer T1 expires repeatedly | | | +| Ensure that the IUT, when an INVITE client transaction is in the Calling state having already repeated its INVITE, wait for a timer A set with a value of 2*T1 before sending it again if an unreliable transport (UDP) is used. | | | + +| Message flow | | | +|--------------------------------|-------------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | Start timer A
1*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A
2*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A
4*T1 | → INVITE | +| ISDN interworking | | | +| SETUP | → Start timer A
1*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A
2*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A
4*T1 | → INVITE | +| Apply post test routine | | | + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_004 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
UDP: the INVITE is retransmitted with intervals that double after each transmission | +| Ensure that the IUT, when an INVITE client transaction is in the Calling state, retransmits its INVITE request with intervals that double after each transmission if an unreliable transport (UDP) is used. | + +| Message flow | | | +|--------------------------|---------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | Start timer A 1*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A 2*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A 4*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A 8*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A 16*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A 32*T1 | → INVITE | +| | Timeout timer A | | +| | Start timer A 64*T1 | → INVITE | + +| | | | +|--------------------------------|----------------------|----------| +| ISDN interworking | | | +| SETUP | → Start timer A 1*T1 | → INVITE | +| | Timeout timer A | → INVITE | +| | Start timer A 2*T1 | | +| | Timeout timer A | → INVITE | +| | Start timer A 4*T1 | | +| | Timeout timer A | → INVITE | +| | Start timer A 32*T1 | | +| | Timeout timer A | → INVITE | +| | Start timer A 64*T1 | | +| Apply post test routine | | | + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|----------------------| +| TSS
Orig_Timers | TP_205_005 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression | +|--------------------|------------|--------------------------------------------------------------------|----------------------| + +**Test purpose** +*Timer B expires no ACK is sent* + +Ensure that the IUT, when an INVITE client transaction is in the Calling state, when timer B set to a value of 64\*T1 expires, does not send an ACK. + +| Message flow | | +|--------------------------|--------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | | +| | Start timer A → INVITE | +| | Start timer B | +| | Timeout timer B | +| | ← 200 OK INVITE | +| ISDN interworking | | +| SETUP | → Start timer A → INVITE | +| | Start timer B | +| | Timeout timer B | +| | ← 200 OK INVITE | + +| | | | | +|--------------------|------------|--------------------------------------------------------------|----------------------| +| TSS
Orig_Timers | TP_205_006 | Reference
section 17.1.1.1 and
Annex A/[IETF RFC 3261] | Selection expression | +|--------------------|------------|--------------------------------------------------------------|----------------------| + +**Test purpose** +*Timer B expires, Transaction is in terminated state* + +Ensure that the IUT, when an INVITE client transaction is in the Calling state, when timer B set to a value of 64\*T1 expires, considers the transaction terminated. + +![](fc7c83167c4e9e614f40e52b39ef735d_img.jpg) + +**Message flow** + +| | End device | | Test equipment | +|--------------------------|----------------------------------|---|-------------------------------------| +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | Start timer A
Start timer B | → | INVITE | +| | Timeout timer B | | | +| | | ← | BYE | +| | | → | 481 Call/Transaction Does Not Exist | +| | | → | ACK | +| ISDN interworking | | | | +| SETUP | → Start timer A
Start timer B | → | INVITE | +| | Timeout timer B | | | +| | | ← | BYE | +| | | → | 481 Call/Transaction Does Not Exist | +| | | → | ACK | + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_007 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| + +**Test purpose** +*100 received, the INVITE is not repeated* + +Ensure that the IUT, when an INVITE client transaction is in the Proceeding state, does not repeat its INVITE request. + +![](2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg) + +**Message flow** + +| | End device | | Test equipment | +|--------------------------|-------------------|---|-----------------------| +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | | → | INVITE | +| | | ← | 100 Trying | +| ISDN interworking | | | | +| SETUP | → | → | INVITE | +| | | ← | 100 Trying | + +**Apply post test routine** + +| TSS
Orig_Timers | TP_205_008 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--------------------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|----------------------|---------------|--|---|-----|--|--|--|--|---|---------------|--|---|-----|--------------------------|--|--|-------|---|----------|--|----------------------|---------------|--|---|-----|--|--|--|--|---|---------------|--|---|-----| +|

Test purpose
486 received, timer D is started ACK is repeated

Ensure that the IUT, when an INVITE client transaction is in the Completed state, on receipt of final responses that matches the transaction, still answer with an ACK request until timer D set to at least 32 second expires if an unreliable transport is used.

Message flow

End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
Start timer D      ➔ 486 Busy Here
➔ ACK
➔ 486 Busy Here
➔ ACK
ISDN interworking
SETUP ➔ ➔ INVITE
Start timer D      ➔ 486 Busy Here
➔ ACK
➔ 486 Busy Here
➔ ACK
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | Start timer D      ➔ | 486 Busy Here | | ➔ | ACK | | | | | ➔ | 486 Busy Here | | ➔ | ACK | ISDN interworking | | | SETUP | ➔ | ➔ INVITE | | Start timer D      ➔ | 486 Busy Here | | ➔ | ACK | | | | | ➔ | 486 Busy Here | | ➔ | ACK | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Start timer D      ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Start timer D      ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Timers | TP_205_009 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--------------------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|----------------------|---------------|--|---|-----|--|--|--|--|---|---------------| +|

Test purpose
486 received, timer D is started ACK is not repeated

Ensure that the IUT, when an INVITE client transaction is in the Completed state, on receipt of a final response that matches the transaction, does not repeat its ACK request if a reliable transport is used.

Message flow

End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
Start timer D      ➔ 486 Busy Here
➔ ACK
➔ 486 Busy Here
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | Start timer D      ➔ | 486 Busy Here | | ➔ | ACK | | | | | ➔ | 486 Busy Here | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Start timer D      ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | + +![](f512ae9c630f2fb53197fa77a1bda0e8_img.jpg) + +**ISDN interworking** + +``` + +SETUP → → INVITE + Start timer D ← 486 Busy Here + → ACK + ← 486 Busy Here + +``` + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_010 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| + +**Test purpose** +*486 repeated Via with different values, ACK is not sent* + +Ensure that the IUT, when an INVITE client transaction is in the Completed state, on receipt of new final responses with different Via branch parameter value, does not repeat its ACK request until timer D set to at least 32 second expires if an unreliable transport is used. + +**SIP header values** + +486 1 + Via: ;branch= + +486 2 + Via: ;branch= + +![](044798c7c60889988b9f9a2a3f7dc64a_img.jpg) + +**Message flow** + +| End device | | Test equipment | +|--------------------------------|---------------|-------------------| +| Interworking POTS | | | +| Off hook | | | +| Dial number | | → INVITE | +| | Start timer D | ← 486 Busy Here 1 | +| | | → ACK | +| | | ← 486 Busy Here 2 | +| ISDN interworking | | | +| SETUP | → | → INVITE | +| | Start timer D | ← 486 Busy Here 1 | +| | | → ACK | +| | | ← 486 Busy Here 2 | +| Apply post test routine | | | + +| TSS
Orig_Timers | TP_205_011 | Reference
section 13.2.2.4 and
Annex A of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|----------------------|------------|----------------|--------------------------|--|----------|--|-------------|----------|---------------------|-----------------|--|-------|--|--|--|-----------------|--|-------|--------------------------|--|---------|----------|---------------------|-----------------|--|-------|--|--|--|-----------------|--|-------|--------------------------------|--| +| Test purpose
200 OK received, ACK is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, when an INVITE client transaction has been in the Terminated state, on receipt of a retransmitted Success (200 OK) response sends an ACK request until $64*T1$ duration expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
Start timer 64*T1 ← 200 OK INVITE
→ ACK
← 200 OK INVITE
→ ACK
ISDN interworking
SETUP → → INVITE
Start timer 64*T1 ← 200 OK INVITE
→ ACK
← 200 OK INVITE
→ ACK
Apply post test routine
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | → INVITE | Start timer $64*T1$ | ← 200 OK INVITE | | → ACK | | | | ← 200 OK INVITE | | → ACK | ISDN interworking | | SETUP → | → INVITE | Start timer $64*T1$ | ← 200 OK INVITE | | → ACK | | | | ← 200 OK INVITE | | → ACK | Apply post test routine | | +| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Start timer $64*T1$ | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Start timer $64*T1$ | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Timers | TP_205_012 | Reference
section 13.2.2.4 and
Annex A of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|----------------------|------------|----------------|--------------------------|--|----------|--|-------------|----------|---------------------|-----------------|--|-------|--|--|-----------------|--|--|-----------------| +| Test purpose
Timeout 64*T1 ACK is not repeated | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, when an INVITE client transaction has been in the Terminated state, after $64*T1$ duration expires, on receipt of a retransmitted Success (200 OK) response does not send an ACK request. | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
Start timer 64*T1 ← 200 OK INVITE
→ ACK
Timeout 64*T1
← 200 OK INVITE
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | → INVITE | Start timer $64*T1$ | ← 200 OK INVITE | | → ACK | | | Timeout $64*T1$ | | | ← 200 OK INVITE | +| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → INVITE | | | | | | | | | | | | | | | | | | | | | +| Start timer $64*T1$ | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | +| Timeout $64*T1$ | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | + +| | | | +|--------------------------------|-------------------|-----------------| +| ISDN interworking | | | +| SETUP | → | → INVITE | +| | Start timer 64*T1 | ← 200 OK INVITE | +| | | → ACK | +| | Timeout 64*T1 | ← 200 OK INVITE | +| Apply post test routine | | | + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_013 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
BYE was sent start timer E; on timeout timer E the BYE is repeated | +| Ensure that the IUT, having sent a BYE request on an established dialog, repeats its request after timer E set to T1 value expires if an unreliable transport is used. | + +| Message flow | | +|--------------------------|-------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK | +| On hook | Start timer E → BYE
Timeout timer E → BYE | +| ISDN interworking | | +| SETUP | → INVITE | +| ALERTING | ← 180 Ringing | +| CONNECT | ← 200 OK INVITE
→ ACK | +| DISCONNECT | → Start timer E → BYE
Timeout timer E → BYE | + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_014 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
BYE is repeated after timeout 2 x timer E | +| Ensure that the IUT, having transmitted a BYE request on an established dialogue, repeats its request after timer E set to the MIN(2*T1,T2) value expires if an unreliable transport is used. | + +| | +|--------------------------| +| SIP header values | +|--------------------------| + +| Message flow | | | +|--------------------------|---------------------------------------------------------------------------------|-------------------------------------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK | +| On hook | Start timer E
Timeout timer E
Start timer E 2*T1 +T2
Timeout timer E | → BYE
→ BYE
→ BYE | +| ISDN interworking | | | +| SETUP | → | → INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| DISCONNECT | → Start timer E
Timeout timer E
Start timer E 2*T1 +T2
Timeout timer E | → BYE
→ BYE
→ BYE | + +| | | | | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_015 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|--------------------------------------------------------------------|--------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
BYE is repeated after timeout 3 x timer E | +| Ensure that the IUT, having transmitted three times a BYE request on an established dialogue, repeats its request after timer E set to the MIN(4*T1,T2) value expires, if an unreliable transport is used. | + +| | +|--------------------------| +| SIP header values | +|--------------------------| + +| Message flow | | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK | +| On hook | Start timer E
Timeout timer E
Start timer E 2*T1 +T2
Timeout timer E
Start timer E 4*T1+T2
Timeout timer E | → BYE
→ BYE
→ BYE
→ BYE | + +| | | | +|--------------------------------|------------------------|-----------------| +| ISDN interworking | | | +| SETUP | → | → INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE | +| | | → ACK | +| DISCONNECT | → | → BYE | +| | Start timer E | | +| | Timeout timer E | → BYE | +| | Start timer E 2*T1 +T2 | | +| | Timeout timer E | → BYE | +| | Start timer E 4*T1+T2 | | +| | Timeout timer E | → BYE | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
Orig_Timers | TP_205_016 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +| Test purpose | | | | +| Timeout timer F, the BYE is not repeated | | | | +| Ensure that the IUT does not repeat a BYE request on an established dialogue after timer F set to 64*T1 expires, if an unreliable transport is used. | | | | +| SIP header values | | | | +| Message flow | | | | +| | End device | | Test equipment | +| Interworking POTS | | | | +| Off hook | | | | +| Dial number | | | → INVITE | +| | | | ← 180 Ringing | +| | | | ← 200 OK INVITE | +| | | | → ACK | +| On hook | | Start timer F | → BYE | +| | | Timeout timer F | | +| ISDN interworking | | | | +| SETUP | → | | → INVITE | +| ALERTING | ← | | ← 180 Ringing | +| CONNECT | ← | | ← 200 OK INVITE | +| | | | → ACK | +| DISCONNECT | → | Start timer F | → BYE | +| | | Timeout timer F | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|-------------------------------------|-------------------|--|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|-------------|---------|---------------|---|-----|--|-----------------|---|-----|--------------------------|--|--|--|-------|---|---|--------|----------|---|---|-------------|------------|---|-------------------|-----|--|--|---------------------|-----| +| TSS
Orig_Timers | TP_205_017 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
BYE is sent and timer E is started; on timeout timer E, the BYE is repeated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, when a BYE client transaction is in the Proceeding state , repeats its BYE request after timer E set to T1 value expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 180 Ringing
On hook Start timer E → BYE
Timeout timer E → BYE
ISDN interworking
SETUP → → INVITE
ALERTING ← ← 180 Ringing
DISCONNECT → Start timer E   → BYE
Timeout timer E   → BYE
| | | | End device | | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | → | INVITE | | | ← | 180 Ringing | On hook | Start timer E | → | BYE | | Timeout timer E | → | BYE | ISDN interworking | | | | SETUP | → | → | INVITE | ALERTING | ← | ← | 180 Ringing | DISCONNECT | → | Start timer E   → | BYE | | | Timeout timer E   → | BYE | +| End device | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | Start timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Timeout timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | → | Start timer E   → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Timeout timer E   → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------------------------------------------------------------|-------------------------------------|-------------------|--|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|-------------|---------|---------------|---|-----|--|-----------------|---|-----|--|------------------|---|-----|--|-----------------|---|-----|--------------------------|--|--|--|-------|---|---|--------|----------|---|-------------------|-----|------------|---|---------------------|-----|--|--|----------------------|-----|--|--|---------------------|-----| +| TSS
Orig_Timers | TP_205_018 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
BYE is repeated after timeout 2 x timer E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, when a BYE client transaction is in the Proceeding state and BYE request have been already repeated in this state, repeats its BYE request after timer E set to T2 value expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 180 Ringing
On hook Start timer E → BYE
Timeout timer E → BYE
Start timer E T2 → BYE
Timeout timer E → BYE
ISDN interworking
SETUP → → INVITE
ALERTING ← Start timer E   → BYE
DISCONNECT → Timeout timer E   → BYE
Start timer E T2   → BYE
Timeout timer E   → BYE
| | | | End device | | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | → | INVITE | | | ← | 180 Ringing | On hook | Start timer E | → | BYE | | Timeout timer E | → | BYE | | Start timer E T2 | → | BYE | | Timeout timer E | → | BYE | ISDN interworking | | | | SETUP | → | → | INVITE | ALERTING | ← | Start timer E   → | BYE | DISCONNECT | → | Timeout timer E   → | BYE | | | Start timer E T2   → | BYE | | | Timeout timer E   → | BYE | +| End device | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | Start timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Timeout timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Start timer E T2 | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Timeout timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | Start timer E   → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | → | Timeout timer E   → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Start timer E T2   → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Timeout timer E   → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Timers | TP_205_019 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------|-------------------------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|---------|-----------------|-----|--|-----------------|--|--------------------------|--|--|-------|---|--------|----------|---|-------------|------------|-------------------|-----|--|-----------------|--| +| Test purpose
BYE is nit repeated after timeout timer F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, when a BYE client transaction is in the Proceeding state , does not repeat a BYE request on an established dialogue, after timer F set to 64*T1 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
← 180 Ringing
On hook Start timer F → BYE
Timeout timer F
ISDN interworking
SETUP → INVITE
ALERTING ← 180 Ringing
DISCONNECT → Start timer F → BYE
Timeout timer F
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 180 Ringing | On hook | Start timer F → | BYE | | Timeout timer F | | ISDN interworking | | | SETUP | → | INVITE | ALERTING | ← | 180 Ringing | DISCONNECT | → Start timer F → | BYE | | Timeout timer F | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | Start timer F → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Timeout timer F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | → Start timer F → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Timeout timer F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Orig_Timers | TP_205_020 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|-------------------------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|---------|-----------------|-----|--|-----------------|--| +| Test purpose
Timeout timer F, the BYE is not repeated | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, when a BYE client transaction is in the Trying state , considers the transaction terminated after timer F set to 64*T1 duration expires without receiving any final response. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number → INVITE
On hook Start timer F → BYE
Timeout timer F
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | On hook | Start timer F → | BYE | | Timeout timer F | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | +| On hook | Start timer F → | BYE | | | | | | | | | | | | | | | | | | | | +| | Timeout timer F | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------|---|---------------|--------| +| ISDN interworking | | | | +| SETUP | → | → | INVITE | +| RELEASE | → | Start timer F | → BYE | +| Timeout timer F | | | | + +#### 7.2.2.5 Abnormal situations + +| | | | | +|---------------------------------|------------|-------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_001 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5, of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|-------------------------------------------------------------------------------------------|----------------------| + +##### Test purpose + +*404 received in calling state; setting of Call-ID, From headers and Request-URI* + +Ensure that when the client transaction is in the **Calling state** that on receipt of a Not Found (404 Not Found) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. + +##### SIP header values + +INVITE 1 sip: [Request URI] SIP/2.0 + +Call-ID: + +From: ;tag= + +ACK 1 sip: [Request URI] SIP/2.0 + +Call-ID: + +From: ;tag= + +##### Message flow + +| | End device | Test equipment | +|--------------------------|------------|-----------------| +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE 1 | +| Busy tone | ← | 404 Not Found | +| On hook | → | ACK 1 | +| ISDN interworking | | | +| SETUP | → | INVITE 1 | +| DISCONNECT | ← | 404 Not Found 1 | +| RELEASE | → | ACK 1 | +| RELEASE COMPLETE | ← | | + +| | | | | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_002 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| + +##### Test purpose + +*404 received in proceeding state; setting of Call-ID, From headers and Request-URI* + +Ensure that when the client transaction is in the **Proceeding state**, that on receipt of a Not Found (404 Not Found) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|----------|--|---|----------------------|-----------|---|---------------|---------|---|-------|------------------------------|--|--|-------|---|----------|-----------------|---|----------------------|------------|---|-----------------|---------|---|-------|------------------|---|--| +| SIP header values
INVITE 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=

404 1
To: ;tag=

ACK 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=
To: ;tag= | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE 1
⬅ 183 Session Progress
Busy tone ⬅ 404 Not Found
On hook ➔ ACK 1

ISDN interworking
SETUP ➔ INVITE 1
CALL PROCEEDING ⬅ 183 Session Progress
DISCONNECT ⬅ 404 Not Found 1
RELEASE ➔ ACK 1
RELEASE COMPLETE ⬅
| | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE 1 | | ⬅ | 183 Session Progress | Busy tone | ⬅ | 404 Not Found | On hook | ➔ | ACK 1 |
ISDN interworking | | | SETUP | ➔ | INVITE 1 | CALL PROCEEDING | ⬅ | 183 Session Progress | DISCONNECT | ⬅ | 404 Not Found 1 | RELEASE | ➔ | ACK 1 | RELEASE COMPLETE | ⬅ | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Busy tone | ⬅ | 404 Not Found | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| On hook | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CALL PROCEEDING | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | ⬅ | 404 Not Found 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_003 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
410 received in calling state; setting of Call-ID, From headers and Request-URI

Ensure that when the client transaction is in the Calling state that on receipt of a Gone (410 Gone) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. | +| SIP header values
INVITE 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=

410 1
To: ;tag=

ACK 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=
To: ;tag= | + +| Message flow | | +|--------------------------------|---------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE 1
← 410 Gone 1
→ ACK 1 | +| ISDN interworking | | +| SETUP | → INVITE 1 | +| DISCONNECT | ← 410 Gone 1 | +| RELEASE | → ACK 1 | +| RELEASE COMPLETE | ← | +| Apply post test routine | | + +| | | | | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_004 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose
480 received in calling state; setting of Call-ID, From headers and Request-URI

Ensure that when the client transaction is in the Calling state that on receipt of a Temporarily Unavailable (480 Temporarily Unavailable) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response.

| +|

SIP header values

INVITE 1 sip: [Request URI] SIP/2.0
Call-ID: <any invite Call ID>
From: <any invite URI>;tag=<any invite tag>

480 1
To: <any 480 URI>;tag=<any 480 tag>

ACK 1 sip: [Request URI] SIP/2.0
Call-ID: <any invite Call ID>
From: <any invite URI>;tag=<any invite tag>
To: <any 480 URI>;tag=<any 480 tag>

| + +| Message flow | | +|--------------------------|--------------------------------------------------------| +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE 1
← 480 Temporarily Unavailable
→ ACK 1 | +| ISDN interworking | | +| SETUP | → INVITE 1 | +| DISCONNECT | ← 480 Temporarily Unavailable | +| RELEASE | → ACK 1 | +| RELEASE COMPLETE | ← | + +| | | | | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_005 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| + +##### **Test purpose** + +*486 received in calling state; setting of Call-ID, From headers and Request-URI* + +Ensure that when the client transaction is in the **Calling state** that, on receipt of a Busy Here (486 Busy Here) response an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. + +###### **SIP header values** + +INVITE 1 sip: [Request URI] SIP/2.0 + +Call-ID: + +From: ;tag= + +486 1 + +To: ;tag= + +ACK 1 sip: [Request URI] SIP/2.0 + +Call-ID: + +From: ;tag= + +To: ;tag= + +###### **Message flow** + +**End device** + +**Test equipment** + +###### **Interworking POTS** + +Off hook + +Dial number + +![](f9b85f8fdfcd1f89bbd3f7c87b30d32b_img.jpg) + +→ INVITE 1 +← 486 Busy Here +→ ACK 1 + +###### **ISDN interworking** + +SETUP + +![](a8596cd587442ee1497c47998cdbfc42_img.jpg) + +→ INVITE 1 + +DISCONNECT + +![](b75ca7f8f28a141553fc412ee433e508_img.jpg) + +← 486 Busy Here + +RELEASE + +![](cc5272728a9ad92131c7231eec1bb533_img.jpg) + +→ ACK 1 + +RELEASE COMPLETE + +![](24667d782140f80b061aa0eabb9b1689_img.jpg) + +← + +| | | | | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_006 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| + +###### **Test purpose** + +*500 received in calling state; setting of Call-ID, From headers and Request-URI* + +Ensure that when the client transaction is in the **Calling state** and that on receipt of a Server Internal Error (500 Server Internal Error) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request, and the same Tag in the To header as in this response. + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| SIP header values
INVITE 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=

500 1
To: ;tag=

ACK 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=
To: ;tag= | | +| Message flow | | +| End device | Test equipment | +| Interworking POTS | | +| Off hook | | +| Dial number | → INVITE 1 | +| | ← 500 Server Internal Error | +| | → ACK 1 | +| ISDN interworking | | +| SETUP | → INVITE 1 | +| DISCONNECT | ← 500 Server Internal Error | +| RELEASE | → ACK 1 | +| RELEASE COMPLETE | ← | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_007 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
600 and 500 with different branch parameter value received in calling state; only one ACK is sent | | | | +| Ensure that when the client transaction is in the Calling state , that on receipt of a Busy Everywhere (600 Busy Everywhere) and a Server Internal Error (500 Server Internal Error) responses with different branch parameter value on the top Via header, send only one ACK request. | | | | +| SIP header values
600
Via: SIP 2.0 ; branch=

500
Via: SIP 2.0 ; branch=

ACK 1 sip: [Request URI] SIP/2.0 | | | | + +| Message flow | | | +|--------------------------|-------------------|---------------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE 1 | +| | ← | 600 Busy Everywhere | +| | ← | 500 Server Internal Error | +| | → | ACK 1 | +| ISDN interworking | | | +| SETUP | → | INVITE 1 | +| DISCONNECT | ← | 600 Busy Everywhere | +| | ← | 500 Server Internal Error | +| RELEASE | → | ACK 1 | +| RELEASE COMPLETE | ← | | + +| | | | | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_008 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose
603 received an ACK is sent

Ensure that when the client transaction is in the Calling state, that on receipt of a Decline (603 Decline) response an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response.

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

SIP header values
INVITE 1 sip: [Request URI] SIP/2.0
Call-ID: <any invite Call ID>
From: <any invite URI>;tag=<any invite tag>

603
To: <any 603 URI>;tag=<any 603 tag>

ACK 1 sip: [Request URI] SIP/2.0
Call-ID: <any invite Call ID>
From: <any invite URI>;tag=<any invite tag>
To: <any 603 URI>;tag=<any 603 tag>

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE 1 | +| | ← | 603 Decline | +| | → | ACK 1 | +| ISDN interworking | | | +| SETUP | → | INVITE 1 | +| DISCONNECT | ← | 603 Decline | +| RELEASE | → | ACK 1 | +| RELEASE COMPLETE | ← | | + +| TSS
Orig_Abnormal_situations | TP_206_009 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|--|---|-----|------------------------------|--|--|-------|---|--------|------------|---|-------------|---------|---|-----|------------------|---|--| +| Test purpose
603 received. The same branch parameter value is sent in the ACK as received in the initial INVITE request

Ensure that when the client transaction is in the Calling state , that on receipt of a Busy Everywhere (600 Busy Everywhere) and a Server Internal Error (500 Server Internal Error) responses with different branch parameter value on the top Via header, send only one ACK request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Via: SIP 2.0 ; branch=

ACK:
Via: SIP 2.0 ; branch=< any invite branch value > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 603 Decline
➔ ACK

ISDN interworking
SETUP ➔ INVITE
DISCONNECT ⬅ 603 Decline
RELEASE ➔ ACK
RELEASE COMPLETE ⬅
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 603 Decline | | ➔ | ACK |
ISDN interworking | | | SETUP | ➔ | INVITE | DISCONNECT | ⬅ | 603 Decline | RELEASE | ➔ | ACK | RELEASE COMPLETE | ⬅ | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 603 Decline | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | ⬅ | 603 Decline | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_010 | Reference
sections 8.1.3.2, 13.2.2.3,
17.1.1.2, 17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Unknown unsuccessful final response received.

Ensure that when the client transaction is in the Calling state , that on receipt of an Unknown (699 Unknown) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. | | | | + +**SIP header values** + +INVITE: + INVITE sip: [invite Request URI] SIP/2.0 + Call-ID: + From: ;tag= + +699: + To: ;tag= + +ACK: + INVITE sip: [invite Request URI] SIP/2.0 + Call-ID: + From: ;tag= + To: ;tag= + +![](afadddeb3fc15146e0758d5212f4fbce_img.jpg) + +**Message flow** + +| | End device | Test equipment | +|--------------------------|-------------------|-----------------------| +| Interworking POTS | | | +| Off hook | | | +| Dial number | → | INVITE 1 | +| | ← | 699 Unknown | +| | → | ACK 1 | +| ISDN interworking | | | +| SETUP | → | INVITE 1 | +| DISCONNECT | ← | 699 Unknown | +| RELEASE | → | ACK 1 | +| RELEASE COMPLETE | ← | | + +| | | | | +|---------------------------------|------------|----------------------------------------------------------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_011 | Reference
sections 12.2.1.1, 13.2.2.3,
17.1.1.2, 17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|----------------------------------------------------------------------------------------------------|----------------------| + +**Test purpose** +*Not acceptable SDP answer. Call is released.* + +Ensure when the IUT is establishing a call on receipt of in 2XX a not acceptable session description, sends an ACK request immediately followed by a BYE request. + +**SIP header values** + +200 OK + SDP + 'm' line + 'a' line + +| Message flow | | | +|--------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | ➔ | INVITE | +| | ← | 200 OK INVITE | +| | ➔ | ACK | +| | ➔ | BYE | +| | ← | 200 OK BYE | +| ISDN interworking | | | +| SETUP | ➔ | INVITE | +| CONNECT | ← | 200 OK INVITE | +| | ➔ | ACK | +| DISCONNECT | ➔ | BYE | +| RELEASE | ← | 200 OK BYE | +| RELEASE COMPLETE | ← | | + +| | | | | +|---------------------------------|------------|---------------------------------------------------|----------------------| +| TSS
Orig_Abnormal_situations | TP_206_012 | Reference
section 13.2.1 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|---------------------------------------------------|----------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

Route header in the ACK is sent with the address of the last received Record-Route header.

The IUT having already received a 2XX final response to its INVITE request, ensure that on receipt of a Success (200 OK) response, with a different Record-Route as in previous response, but with the same Via branch parameter and CSeq header method as in the INVITE request, sends an ACK request with a Route header set according to this new Record-Route.

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

SIP header values

180:
Record-Route: <sip: record_route_180;lr>

200:
Record-Route: <sip: record_route_200;lr>

ACK:
Route: <sip: record_route_200;lr>

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| Off hook | | | +| Dial number | ➔ | INVITE | +| | ← | 180 Ringing | +| | ← | 200 OK INVITE | +| | ➔ | ACK | +| Apply post test routine | | | + +| | | +|--------------------------------|-----------------| +| ISDN interworking | | +| SETUP | → INVITE | +| ALERTING | 180 Ringing | +| CONNECT | ← 200 OK INVITE | +| | → ACK | +| Apply post test routine | | + +### 7.2.3 Call initiation – UE terminating case + +#### 7.2.3.1 Establishment of an early dialogue + +| | | | | +|--------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_001 | Reference
sections 8, 8.2, and
13.3.1.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
The IUT sends a 180 Ringing | | | | +| Ensure that the IUT on receipt of an INVITE request, sends a provisional (180 Ringing) response. | | | | +| Message flow | | | | +| | Test equipment | End device | | +| Interworking POTS | | | | +| INVITE | → | | | +| 180 Ringing | ← | Ringing | | +| ISDN interworking | | | | +| INVITE | → | → SETUP | | +| 180 Ringing | ← | ← ALERTING | | +| Apply post test routine | | | | + +| | | | | +|-----------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_002 | Reference
sections 8, 8.2, and
13.3.1.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
The IUT sends a 200 OK INVITE | | | | +| Ensure that the IUT on receipt of an INVITE request, sends a Success (200 OK) response. | | | | +| Message flow | | | | +| | Test equipment | End device | | +| Interworking POTS | | | | +| INVITE | → | Ringing | | +| 180 Ringing | ← | | | +| 200 OK INVITE | ← | Off hook | | +| ACK | → | | | +| ISDN interworking | | | | +| INVITE | → | → SETUP | | +| 200 OK INVITE | ← | ← CONNECT | | +| ACK | → | | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|----------------------|--|-----------------------|--|-------------------|--------------------------|--|--|--|--------|---|--|---------|------------|---|--|--|--|--|--|--|--------------------------|--|--|--|--------|---|---|-------|------------|---|--|--| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_003 | Reference
section 8 and 8.2.6.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The Timestamp header value in the response is increased

Ensure that the IUT on receipt of an INVITE request with a Timestamp header, when it answers with a provisional response Trying (100 Trying), set a Timestamp header with an increased value of the received Timestamp in its response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Timestamp:

100:
Timestamp: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
100 Trying ⬅
 
ISDN interworking
INVITE ➔ ➔ SETUP
100 Trying ⬅

Apply post test routine

| | | | | Test equipment | | End device | Interworking POTS | | | | INVITE | ➔ | | Ringing | 100 Trying | ⬅ | | | | | | | ISDN interworking | | | | INVITE | ➔ | ➔ | SETUP | 100 Trying | ⬅ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_004 | Reference
section 13.2.1 and
13.3.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Initial offer in the 200 OK INVITE, initial answer in the ACK

Ensure that the IUT on receipt of an INVITE request including no message body, includes in its first 2xx response an initial offer session description. | | | | +| SIP header values
200 OK:
SDP
m – line offer
a – line offer
ACK
SDP
m – line answer
a – line answer | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 200 OK INVITE | ← | On hook | +| ACK | → | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_005 | Reference
section 13.2.1 and
13.3.1 of
[IETF RFC 3261] | Selection expression | +|----------------------------------------------------|------------|-----------------------------------------------------------------|----------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose
Initial offer in the initial INVITE, initial answer in the 200 OK INVITE

Ensure that the IUT on receipt of an INVITE request including an initial offer session description in its message body, includes the answer in its first 2xx response in a session description.

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

SIP header values

INVITE:
SDP
m – line offer
a – line offer

200 OK:
SDP
m – line answer
a – line answer

| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 200 OK INVITE | ← | On hook | +| ACK | → | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| Apply post test routine | | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_006 | Reference
section 8.2.6.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------|-----------------------|--|-------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|--------------------------------|--|--|------------------------------|--|--|--------|---|---------|-------------|---|------------|--------------------------------|--|--| +| Test purpose
From, Call-ID, CSeq and Via headers copy from the INVITE

Ensure that the IUT on receipt of an INVITE request, sends a provisional (101-199) response including the headers From, Call-ID, CSeq and Via headers copy from the INVITE request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
From:
Call-ID:
CSeq:
Via:

180:
From:
Call-ID:
CSeq:
Via: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
180 Ringing ⬅
Apply post test routine

ISDN interworking
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 180 Ringing | ⬅ | | Apply post test routine | | |
ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_007 | Reference
sections 8.2.6.2, 12.2.2 and
13.3.1 of [IETF RFC 3261] | Selection expression | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------|----------------------| +| Test purpose
To tag is sent in the response

Ensure that the IUT on receipt of an INVITE request with no TAG set on the To header, sends a provisional (101-199) response including the same URI and an additional TAG for the To header. | | | | +| SIP header values
INVITE:
To:

180:
To: ;tag=to_tag | | | | + +![](f97782852c7474fa58fcf5cd0bd96a7e_img.jpg) + +| Message flow | | | +|--------------------------|--------------------------------|------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| | Apply post test routine | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| | Apply post test routine | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_an_early_dialogue | TP_301_008 | Reference
section 8.2.6.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| To tag in the INVITE request | | | | +| Ensure that the IUT on receipt of an INVITE request with a TAG set on the To header, either: | | | | +|
  • sends a provisional (101-199) response including the same URI and the same TAG for the To header (recommended for robustness),
  • or reject the INVITE request with a Call/Transaction does not exist (481 Call/Transaction does not exist).
| | | | +| SIP header values | | | | +| INVITE:
To: ;tag=to_tag_value | | | | +| 180:
To: ;tag=to_tag_value | | | | +| Message flow | | | | +| | Test equipment | | End device | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| | CASE A | | | +| 180 Ringing | ← | | | +| | Apply post test routine | | | +| CASE B | | | | +| 481 Call/Transaction does not exist | ← | | | +| ACK | → | | | +| ISDN interworking | | | | +| INVITE | → | → | SETUP | +| CASE A | | | | +| 180 Ringing | ← | ← | ALERTING | +| | Apply post test routine | | | +| CASE B | | | | +| 481 Call/Transaction does not exist | ← | | | +| ACK | → | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|--|--------------------------------|--|--------------------------|--|--|--------|---|---------|-------------|---|------------|--|--------------------------------|--| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_009 | Reference
section 12.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Contact header in the response.

Ensure that the IUT on receipt of an INVITE request, sends a provisional (101-199) response including a single Contact header. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180:
Contact: contact_value > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
180 Ringing ⬅
Apply post test routine
ISDN interworking
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 180 Ringing | ⬅ | | | Apply post test routine | | ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|--|--------------------------------|--|--------------------------|--|--|--------|---|---------|-------------|---|------------|--|--------------------------------|--| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_010 | Reference
section 12.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Record-Route header copied from the INVITE request into the response

Ensure that the IUT on receipt of an INVITE request including a Record-Route header, sends a provisional (101-199) response including a Record-Route header copy from the INVITE request, in the same order. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Record-Route: invite_record_route >;lr

180:
Record-Route: invite_record_route >;lr | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
180 Ringing ⬅
Apply post test routine
ISDN interworking
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 180 Ringing | ⬅ | | | Apply post test routine | | ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_011 | Reference
section 12.1.1of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------|----------------------|----------------|--|------------|--------------------------|--|--|--------|---|---------|-------------|---|--|--|--------------------------------|--|--------------------------|--|--|--------|---|---------|-------------|---|------------|--|--------------------------------|--| +| Test purpose
Record-Route header with unknown parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT on receipt of an INVITE request including a Record-Route header with parameters that it does not understand, sends a provisional (101-199) response including a Record-Route header copy from the INVITE request, with the unknown parameters. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Record-Route:

180:
Record-Route: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE → Ringing
180 Ringing ←
Apply post test routine
ISDN interworking
INVITE → → SETUP
180 Ringing ← ← ALERTING
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | → | Ringing | 180 Ringing | ← | | | Apply post test routine | | ISDN interworking | | | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | | Apply post test routine | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_012 | Reference
section 12.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------|----------------------|----------------|--|------------|--------------------------|--|--|--------|---|---------|-------------|---|--|--|--------------------------------|--|--------------------------|--|--|--------|---|---------|-------------|---|------------|--|--------------------------------|--| +| Test purpose
From header without "tag" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT on receipt of an INVITE request including From header without tag, sends a provisional (101-199) response including a From header without tag. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
From:

180:
From: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE → Ringing
180 Ringing ←
Apply post test routine
ISDN interworking
INVITE → → SETUP
180 Ringing ← ← ALERTING
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | → | Ringing | 180 Ringing | ← | | | Apply post test routine | | ISDN interworking | | | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | | Apply post test routine | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_013 | Reference
section 17.2.1 and
17.2.3 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------------------|----------------------|----------------|--|------------|--------------------------|--|--|---------|---|---------|-------------|---|--|-------------|-------|--|-------------|---|--|--|--------------------------------|--|------------------------------|--|--|---------|---|---------|-------------|---|------------|-------------|-------|--|-------------|---|--|--|--------------------------------|--| +| Test purpose
Additional identical INVITE received, the previous sent response is repeated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of an INVITE request, including a Via header set with the same branch parameter and sent-by value in the topmost list value, repeats its last response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1:
Via: any_invite1_via_value;branch=any_invite1_branch_value
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq

INVITE2:
Via: any_invite1_via_value;branch=any_invite1_branch_value
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE1 → Ringing
180 Ringing ←

INVITE2

→
180 Ringing ←
Apply post test routine

ISDN interworking
INVITE1 → → SETUP
180 Ringing ← ← ALERTING

INVITE2

→
180 Ringing ←
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE1 | → | Ringing | 180 Ringing | ← | |
INVITE2 |
→ | | 180 Ringing | ← | | | Apply post test routine | |
ISDN interworking | | | INVITE1 | → | → SETUP | 180 Ringing | ← | ← ALERTING |
INVITE2 |
→ | | 180 Ringing | ← | | | Apply post test routine | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INVITE2 |
→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INVITE2 |
→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_014 | Reference
section 17.2.1 and
17.2.3 of [IETF RFC 3261] | Selection expression | +| Test purpose
Additional identical INVITE and Via header without branch parameter received, the previous sent response is repeated | | | | +| Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of an INVITE request, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via identical as in the first INVITE request, repeats its last response. | | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------| +| SIP header values
INVITE1:
Via: any_invite1_via_value ;branch=z9hG4bK any_invite1_branch_value
From: any_invite1_from_value ;tag= any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq

INVITE2:
Via: any_invite1_via_value ;branch=z9hG4bK any_invite1_branch_value
Via: any_invite2_via_value
From: any_invite1_from_value ;tag= any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq | | | +| Message flow | | | +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| INVITE2 | → | | +| 180 Ringing | ← | | +| | Apply post test routine | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| INVITE2 | → | | +| 180 Ringing | ← | | +| | Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_015 | Reference
section 17.2.1 and
17.2.3 of [IETF RFC 3261] | Selection expression | +| Test purpose
Additional identical INVITE and Via header without magic cookie in the branch parameter received, the previous sent response is repeated

Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of an INVITE request, including a Via header set with a branch parameter without the magic cookie "z9hG4bK" but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via identical as in the first INVITE request, repeats its last response. | | | | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------| +| SIP header values
INVITE1:
Via: any_invite1_via_value;branch=z9hG4bK any_invite1_branch_value
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq

INVITE2:
Via: any_invite1_via_value;branch=z9hG4bK any_invite1_branch_value
Via: any_invite1_via_value;branch= any_invite2_branch_value
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq | | | +| Message flow | | | +| Test equipment | | End device | +| Interworking POTS | | | +| INVITE | ➔ | Ringing | +| 180 Ringing | ⬅ | | +|
INVITE2 |
➔ | | +| 180 Ringing | ⬅ | | +| Apply post test routine | | | +|
ISDN interworking | | | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ ALERTING | +|
INVITE2 |
➔ | | +| 180 Ringing | ⬅ | | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_016 | Reference
section 22.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
INVITE without Authorization header received a 401 is sent containing a WWW-Authenticate header | | | | +| Ensure that the IUT on receipt of an INVITE request not including an Authorization header field, sends an Unauthorized (401 Unauthorized) response, containing a WWW-Authenticate header. | | | | +| SIP header values
401:
WWW-Authenticate: | | | | + +![](cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg) + +| Message flow | | | +|--------------------------|-------------------------|------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | | +| 401 Unauthorized | ← | | +| ACK | → | | +| | Apply post test routine | | +| ISDN interworking | | | +| INVITE | → | | +| 401 Unauthorized | ← | | +| ACK | → | | +| | Apply post test routine | | + +| | | | | +|----------------------------------------------------|------------|-------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_017 | Reference
section 22.2 of
[IETF RFC 3261] | Selection expression | +|----------------------------------------------------|------------|-------------------------------------------------|----------------------| + +**Test purpose** +*INVITE without Authorization header received a 401 is sent containing a WWW-Authenticate header with proper values* + +Ensure that the IUT on receipt of an INVITE request not including an Authorization header field, sends an Unauthorized (401 Unauthorized) response, containing a WWW-Authenticate header including proper value for realm and nonce HTTP parameters. + +**SIP header values** + 401: + WWW-Authenticate: Digest realm="[any value]",nonce="[any value]",algorithm=MD5,qop="auth" + +![](6ba19a99fb96f0139505f0992544a2cf_img.jpg) + +| Message flow | | | +|--------------------------|-------------------------|------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | | +| 401 Unauthorized | ← | | +| ACK | → | | +| | Apply post test routine | | +| ISDN interworking | | | +| INVITE | → | | +| 401 Unauthorized | ← | | +| ACK | → | | +| | Apply post test routine | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_018 | Reference
section 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|----------|---|--|------------------|---|--|-----|---|--|----------|---|---------|---------------|---|----------|-----|---|--|--|--------------------------------|--|--------------------------|--|--|--------|---|--|------------------|---|--|-----|---|--|----------|---|---------|---------------|---|-----------|-----|---|--|--|--------------------------------|--| +| Test purpose
INVITE with valid Authorization header received, a 200 OK INVITE is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT having sent an Unauthorized (401 Unauthorized) response to an INVITE request, on receipt of a INVITE request including a valid Authorization header field, sends a Success (200 OK) response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
401:
WWW-Authenticate: Digest realm="[any value]",nonce="[any value]",algorithm=MD5,qop="auth"

INVITE 2
Authorization: Digest username="[any value]", realm="[any value]", nonce="[any value]",
uri="sip:tel0.ver.sul.t-online.de", qop=auth, nc=[any value], cnonce="[any value]",
response="[any value]", algorithm=MD5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE 1 ➔
401 Unauthorized ⬅
ACK ➔
INVITE 2 ➔ Ringing
200 OK INVITE ⬅ Off hook
ACK ➔
Apply post test routine
ISDN interworking
INVITE ➔
401 Unauthorized ⬅
ACK ➔
INVITE 2 ➔ ➔ SETUP
200 OK INVITE ⬅ ⬅ CONNECT
ACK ➔
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE 1 | ➔ | | 401 Unauthorized | ⬅ | | ACK | ➔ | | INVITE 2 | ➔ | Ringing | 200 OK INVITE | ⬅ | Off hook | ACK | ➔ | | | Apply post test routine | | ISDN interworking | | | INVITE | ➔ | | 401 Unauthorized | ⬅ | | ACK | ➔ | | INVITE 2 | ➔ | ➔ SETUP | 200 OK INVITE | ⬅ | ⬅ CONNECT | ACK | ➔ | | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE 1 | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 401 Unauthorized | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE 2 | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 401 Unauthorized | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE 2 | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | ⬅ CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|-------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_019 | Reference
subclause 5.1.4.1 of
[ETSI TS 124 229] | Selection expression
PICS: 5.2/14 and 5.2/15 | +| Test purpose
INVITE with support for preconditions received. Preconditions supported. | | | | +| Ensure that upon the IUT receiving an INVITE request containing the precondition and the100rel option-tag in the Supported header, the SUT sends a (reliable) 183 that contains, in the SDP, the instruction to reserve the quality of service on the remote side and the required preconditions and a reliable transport of provisional responses. The remote entity indicates that the resource is reserved in the UPDATE request and the SUT confirms the resource reservation in the 200 OK UPDATE. The user is alerted. | | | | + +##### **SIP header values** + +INVITE: + +Supported: precondition,100rel + +SDP a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv + +183: + +Require: precondition,100rel + +SDP a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv +a=conf:qos remote sendrecv + +UPDATE + +SDP a=curr:qos local sendrecv +a=curr:qos remote none +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv + +200 OK UPDATE + +SDP a=curr:qos local sendrecv +a=curr:qos remote sendrecv +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv + +##### **Message flow** + +**Test equipment** + +**End device** + +###### **Interworking POTS** + +INVITE → +183 Session Progress ← +PRACK → +200 OK PRACK ← +UPDATE → +200 OK UPDATE ← +180 Ringing ← Ringing +Apply post test routine + +###### **ISDN interworking** + +INVITE → +183 Session Progress ← +PRACK → +200 OK PRACK ← +UPDATE → +200 OK UPDATE ← +→ SETUP +← ALERTING +180 Ringing ← +Apply post test routine + +| | | | | +|----------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_020 | Reference
subclause 5.1.4.1 of
[ETSI TS 124 229] | Selection expression
PICS: NOT 5.2/14 | +|----------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------| + +##### Test purpose + +*INVITE with support for preconditions received. Preconditions supported.* + +Ensure that the upon the IUT receiving an INVITE request containing the precondition and the 100rel option-tag in the Supported header, the SUT sends a (reliable) 183 session Progress or 180 Ringing and the SDP that does not contain information that preconditions are supported. A Require header requesting preconditions is not included. + +##### SIP header values + +INVITE: + +Supported: precondition, 100rel + +SDP a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory/optional local sendrecv +a=des:qos mandatory/optional remote sendrecv + +183/180: + +##### Message flow + +**Test equipment** + +**End device** + +###### Interworking POTS + +INVITE + +![](12e423b0703611c6366d33dd372eaf3e_img.jpg) + +→ + +###### CASE A + +183 Session Progress + +![](13fca204036d2d8455b95f47d31bfe6c_img.jpg) + +← + +###### CASE B + +180 Ringing + +![](04089d4a36707dfdd501f0e181939ef1_img.jpg) + +← + +Ringing + +**Apply post test routine** + +###### ISDN interworking + +INVITE + +![](5be2aff716ae8efd08e429cc35bff205_img.jpg) + +→ + +![](2c65f14b66a43cb6976c1536e3328fda_img.jpg) + +→ + +SETUP + +180 Ringing + +![](9f77c87c595ece51522c33becece235e_img.jpg) + +← + +![](c94b319d12f571b5a4b42b445f50216d_img.jpg) + +← + +ALERTING + +**Apply post test routine** + +| | | | | +|----------------------------------------------------|------------|--------------------------------------------------------|-------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_021 | Reference
subclause 5.1.4.1 of
[ETSI TS 124 229] | Selection expression
PICS: 5.2/14 AND 5.2/15 | +|----------------------------------------------------|------------|--------------------------------------------------------|-------------------------------------------------| + +###### Test purpose + +*INVITE without SDP offer received.* + +Ensure that the IUT upon receiving an INVITE request without an SDP offer and transport of reliable provisional responses, send a reliable 183 Session Progress containing an SDP offer. The SDP answer is received in an UPDATE request or ACK request + +###### **SIP header values** + +INVITE: +Supported: 100rel + +183 +SDP offer + +###### **CASE A** + +ACK +SDP answer + +###### **CASE B** + +UPDATE +SDP answer + +###### **Message flow** + +**Test equipment** + +**End device** + +###### **Interworking POTS** + +INVITE + +→ + +183 Session Progress + +← + +Ringing + +PRACK + +→ + +200 OK PRACK + +← + +###### **CASE A** + +200 OK INVITE + +← + +Off hook + +ACK + +→ + +###### **CASE B** + +UPDATE + +→ + +200 OK UPDATE + +← + +**Apply post test routine** + +###### **ISDN interworking** + +INVITE + +→ + +→ SETUP + +183 Session Progress + +← + +← ALERTING + +PRACK + +→ + +200 OK PRACK + +← + +###### **CASE A** + +200 OK INVITE + +← + +← CONNECT + +ACK + +→ + +###### **CASE B** + +UPDATE + +→ + +200 OK UPDATE + +← + +**Apply post test routine** + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_022 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------|----------------|------------|--------------------------|--|----------|--|------------------------|---------|---------|--|----------------|--|---------------|--|-----------------|----------|-------|--|---------------|--|----------|--|-----------------|--|-------------------------|--|--------------------------|--|----------|---------|------------------------|------------|---------|--|----------------|--| +|

Test purpose
INVITE without SDP offer received.

Ensure that the IUT upon receipt of an INVITE request without an SDP offer and transport of reliable provisional responses, send a reliable 183 Session Progress containing an SDP offer. The SDP answer is received in an UPDATE request or ACK request

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
INVITE:
    Supported: 100rel

183
SDP offer

CASE A
ACK
    SDP answer

CASE B
UPDATE
    SDP answer

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
Interworking POTS
INVITE →
183 Session Progress ← Ringing
PRACK →
200 OK PRACK ←
CASE A
200 OK INVITE ← Off hook
ACK →
CASE B
UPDATE →
200 OK UPDATE ←
Apply post test routine
ISDN interworking
INVITE → → SETUP
183 Session Progress ← ← ALERTING
PRACK →
200 OK PRACK ←
| | | | Test equipment | End device | Interworking POTS | | INVITE → | | 183 Session Progress ← | Ringing | PRACK → | | 200 OK PRACK ← | | CASE A | | 200 OK INVITE ← | Off hook | ACK → | | CASE B | | UPDATE → | | 200 OK UPDATE ← | | Apply post test routine | | ISDN interworking | | INVITE → | → SETUP | 183 Session Progress ← | ← ALERTING | PRACK → | | 200 OK PRACK ← | | +| Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress ← | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK PRACK ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE ← | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UPDATE → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK UPDATE ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK PRACK ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|-------------------------|---|-----------| +| CASE A | | | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| CASE B | | | +| UPDATE | → | | +| 200 OK UPDATE | ← | | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_023 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression | +| Test purpose
Modifying SDP in early dialogue | | | | +| Ensure that the SUT is able to receive an UPDATE request to modify the SDP in early dialogue. A 200 OK UPDATE with SDP answer is sent. | | | | +| SIP header values | | | | +| 183/180
SDP answer 1 | | | | +| UPDATE
SDP offer 2 | | | | +| 200 OK (UPDATE)
SDP answer 2 | | | | +| Message flow | | | | +| | Test equipment | | End device | +| Interworking POTS | | | | +| INVITE | → | | | +| 180/183 | ← | | Ringing | +| UPDATE | → | | | +| 200 OK UPDATE | ← | | | +| Apply post test routine | | | | +| ISDN interworking | | | | +| INVITE | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| UPDATE | → | | | +| 200 OK UPDATE | ← | | | +| Apply post test routine | | | | + +##### 7.2.3.1.2 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|-------------------|--------|---|---------|------------|---|--|--|--------------------------------|--| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_101 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | +| Test purpose
A BearerCapability speech is included in the PSTN XML element

Ensure that when a PSTN XML element is included in a received INVITE request and the BearerCapability value is set to ITC_VA as indicated in Table 7.2.3.1-1, a SETUP is sent where the Bearer Capability is derived from the received PSTN XML BearerCapability. | | | | | | | | | | | | | | | | +| SIP header values
INVITE: PSTN XML MIME body




00
ITC_value


00
10000


01
00011



If ITC_value = '01000' the SDP m line contains CLEARMODE as preferred codec | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Bearer Capability = PSTN XML BearerCapability | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 100 Trying | ⬅ | | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_102 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
A BearerCapability speech and a BearerCapability UDI with tones/annount. is included in the PSTN XML element

Ensure that AGCF/VGW is able to send two Bearer Capability IE in the SETUP to the called user equipment in the same order as received in the PSTN BearerCapability XML. The first PSTN BearerCapability element is sent in the first Bearer Capability IE in the SETUP and the second PSTN BearerCapability element is sent in the second Bearer Capability IE in the SETUP. | | | | +| | | | | + +| | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------|-------------------|--------|---|---------|------------|---|--|--|--------------------------------|--| +|

SIP header values

INVITE: PSTN XML MIME body

<?xml version="1.0" encoding="utf-8"?> PSTN   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCabability>00000<       or       InformationTransferCabability>10000<     BCoctet4       TransferMode>00<       InformationTransferRate>10000<     BCoctet5       Layer1Identification>01<       UserInfoLayer1Protocol>00011<   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCabability>10001<     BCoctet4       TransferMode>00<       InformationTransferRate>10000<     BCoctet5       Layer1Identification>01<       UserInfoLayer1Protocol>00011<

SDP: m line contains as the first codec CLEARMODE and as the second codec an ITU-T G.711 codec

| | | | | | | | | | | | | +|

DSS1 Parameter values

SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements

| | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE → → SETUP
100 Trying ←
Apply post test routine
| | Test equipment | End device | INVITE | → | → SETUP | 100 Trying | ← | | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | + +**Table 7.2.3.1-1 – Mapping of PSTN XML BearerCapability to Bearer Capability** + +| ITC_value | XML InformationTransferCabability | BC Information transfer capability | +|-----------|-----------------------------------|------------------------------------| +| ITC_VA_1 | '00000' | Speech | +| ITC_VA_2 | '10000' | 3,1 kHz audio | +| ITC_VA_3 | '01000' | unrestricted digital information | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_103 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
INVITE received, no PSTN XML instance present | | | | +| Ensure that if an INVITE request is received and no PSTN BearerCapability XML element is present, the Bearer Capability IE is set according Table 7.2.3.1-2. | | | | +| SIP header values
INVITE: SDP m line = SDP_VA | | | | +| DSSI Parameter values
SETUP: Bearer Capability | | | | +| Message flow
Test equipment
INVITE
100 Trying
→
←
End device
→ SETUP
Apply post test routine
| | | | + +**Table 7.2.3.1-2 – Coding of from SDP: SIP to BC DSSI** + +| SDP_VA | | m= line | | a= line | | Bearer Capability IE | | +|-----------|-------|-------------|----------------|--------------------------------------------------------------------------------|------------------------------------------------|---------------------------------------------------------|--| +| | | | | Rtpmap:
/rate>/encoding
parameters> | Information
transport
capability | User
information
Layer 1
Protocol
Indicator | | +| SDP_VA_01 | Audio | RTP/AVP | 0 | N/A | "3.1 kHz audio" | "G.711 A-law" | | +| SDP_VA_02 | Audio | RTP/AVP | 0 | N/A | "3.1 kHz audio" | "G.711 μ-law" | | +| SDP_VA_03 | Audio | RTP/AVP | Dynamic
PT | rtpmap:
PCMU/8000 | "3.1 kHz audio" | "G.711 A-law" | | +| SDP_VA_04 | Audio | RTP/AVP | Dynamic
PT | rtpmap:
PCMU/8000 | "3.1 kHz audio" | "G.711 μ-law" | | +| SDP_VA_05 | Audio | RTP/AVP | 8 | N/A | "3.1 kHz audio" | "G.711 A-law" | | +| SDP_VA_06 | Audio | RTP/AVP | 8 | N/A | "3.1 kHz audio" | "G.711 μ-law" | | +| SDP_VA_07 | Audio | RTP/AVP | Dynamic
PT | rtpmap:
PCMA/8000 | "3.1 kHz audio" | "G.711 A-law" | | +| SDP_VA_08 | Audio | RTP/AVP | Dynamic
PT | rtpmap:
PCMA/8000 | "3.1 kHz audio" | "G.711 μ-law" | | +| SDP_VA_09 | Audio | RTP/AVP | Dynamic
PT, | rtpmap:
CLEARMODE/8000 | "Unrestricted
digital inf.
W/tone/ann.") | | | +| SDP_VA_10 | Audio | RTP/AVP | Dynamic
PT | Rtpmap:
CLEARMODE/8000 | "Unrestricted
digital
information" | | | +| SDP_VA_11 | Image | Udptl | t38 | Based on [ITU-T T.38] | "3.1 kHz audio" | "G.711 A-law" | | +| SDP_VA_12 | Image | Tcptl | t38 | Based on [ITU-T T.38] | "3.1 kHz audio" | "G.711 A-law" | | +| SDP_VA_13 | Image | Udptl | t38 | Based on [ITU-T T.38] | "3.1 kHz audio" | "G.711 μ-law" | | +| SDP_VA_14 | Image | Tcptl | t38 | Based on [ITU-T T.38] | "3.1 kHz audio" | "G.711 μ-law" | | + +| | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|--------|---|--|---------|------------|---|--|--|--|-------------------------|--|--| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_104 | Reference
subclause 5.1.2.1/
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | +| Test purpose
INVITE received, no PSTN XML instance present | | | | | | | | | | | | | | | | | | | | +| Ensure that if an INVITE request is received and no PSTN BearerCapability XML element is present, the High Layer Compatibility IE if present is set according Table 7.2.3.1-3. | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: SDP m line = SDP_VA | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values
SETUP: High Layer Compatibility, High Layer Characteristics Identification value | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
100 Trying ←
Apply post test routine
| | | | | Test equipment | | End device | INVITE | → | | → SETUP | 100 Trying | ← | | | | Apply post test routine | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | +| INVITE | → | | → SETUP | | | | | | | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | + +**Table 7.2.3.1-3 – Coding of from SDP: SIP to HLC DSSI** + +| SDP_VA | | m= line | | a= line | HLC parameter
(optional) | +|-----------|-------------|-----------------|------------|-----------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| | > | > | | Rtpmap:<dynamic-PT>
<encoding name>/<clock
rate>/encoding parameters>
| High Layer
Characteristics
Identification
| +| SDP_VA_01 | Image | Udptl | t38 | Based on ITU-T T.38 | "Facsimile Group 2/3" | +| SDP_VA_02 | Image | Tcptl | t38 | Based on ITU-T T.38 | "Facsimile Group 2/3" | +| SDP_VA_03 | Image | Udptl | t38 | Based on ITU-T T.38 | "Facsimile Group 2/3" | +| SDP_VA_04 | Image | Tcptl | t38 | Based on ITU-T T.38 | "Facsimile Group 2/3" | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_105 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
Mapping of PSTN XML ProgressIndicator into DSSI Progress Indicator IE | | | | +| Ensure that on receipt of an INVITE request and the PSTN XML contains the ProgressIndicator, a SETUP is sent. A Progress Indicator IE is present derived from the received ProgressIndicator PI_value according to Table 7.2.3.1-4. | | | | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| SIP header values
INVITE:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000110<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription>PI_value< | | +| DSS1 Parameter values
SETUP: Progress Indicator Coding standard ='00', Location ='0000', Progress description= PI_value | | +| Message flow | | +|
Test equipment End device
INVITE → → SETUP
100 Trying ←
Apply post test routine
| | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_106 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
Receipt of PSTN XML ProgressIndicator value 6

Ensure that on receipt of an INVITE request and the PSTN XML contains the ProgressIndicator value set to 6, a SETUP is sent and no Progress Indicator IE is present. | | | | +| SIP header values
INVITE:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000110< | | | | +| DSS1 Parameter values | | | | +| Message flow | | | | +|
Test equipment End device
INVITE → → SETUP
100 Trying ←
Apply post test routine
| | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_107 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
INVITE request no PSTN XML instance present. | | | | +| Ensure that on receipt of an INVITE request and no PSTN is present, a SETUP is sent. A Progress Indicator IE is present and the Progress Description value is set to 1. | | | | +| SIP header values | | | | +| DSS1 Parameter values | | | | +| Message flow
Test equipment
INVITE                               →
100 Trying                       ←
End device
→ SETUP

Apply post test routine

| | | | + +**Table 7.2.3.1-4 – Mapping of PSTN XML ProgressIndicator to DSS1 Progress Indicator information element** + +| PI_value | XML ProgressIndicator
ProgressDescription | DSS1 Progress Indicator value | +|----------|----------------------------------------------|--------------------------------------------------------------------------------------------| +| PI_VA_1 | '0000001' | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | +| PI_VA_2 | '0000010' | Destination address is non-5.1.1/2 | +| PI_VA_3 | '0000011' | Origination address is non-5.1.1/2 | +| PI_VA_4 | '0000100' | Call has returned to the 5.1.1/2 | +| PI_VA_5 | '0000101' | Interworking has occurred and has resulted in a telecommunication service change | +| PI_VA_6 | '0001000' | In-band information or an appropriate pattern is now available | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_108 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
Mapping of PSTN XML LowLayerCompatibility into DSS1 Low Layer Compatibility IE | | | | +| Ensure that on receipt of an INVITE request and the PSTN XML contains the LowLayerCompatibility, a SETUP is sent. A Low Layer Compatibility IE is present derived from the received LowLayerCompatibility ITC_value according to Table 7.2.3.1-5. | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------|-------------------|-------------------|--|--------|---|--|---|-------|------------|---|--|--|--|--|-------------------------|--|--|--| +|

SIP header values

INVITE:
<?xml version="1.0" encoding="utf-8"?>
<PSTN>
    <LowLayerCompatibility>
        <LLOctet3>
            <CodingStandard>00</CodingStandard>
            <InformationTransferCapability>ITC_VA</InformationTransferCapability>
        </LLOctet3>
        <LLOctet4>
            <TransferMode>00</TransferMode>
            <InformationTransferRate>10000</InformationTransferRate>
        </LLOctet4>
    </LowLayerCompatibility>

| | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values

SETUP: Low Layer Compatibility

| | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
Apply post test routine
| | Test equipment | | End device | | INVITE | ➔ | | ➔ | SETUP | 100 Trying | ⬅ | | | | | Apply post test routine | | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.3.1-5 – Mapping of PSTN XML LowLayerCompatibility to DSS1 low layer compatibility** + +| ITC_value | XML LLC
InformationTransferCabability | LLC Information transfer capability | +|-----------|------------------------------------------|-------------------------------------| +| ITC_VA_1 | '00000' | Speech | +| ITC_VA_2 | '10000' | 3,1 kHz audio | +| ITC_VA_3 | '01001' | Unrestricted digital info | +| ITC_VA_3 | '10001' | 7 kHz audio | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_109 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +|

Test purpose

Mapping of PSTN XML HighLayerCompatibility into DSS1 High Layer Compatibility IE

Ensure that on receipt of an INVITE request and the PSTN XML contains the HighLayerCompatibility, a SETUP is sent. A High Layer Compatibility IE is present derived from the received HighLayerCompatibility HLC_value according Table 7.2.3.1-6.

| | | | +|

SIP header values

INVITE:
PSTN XML MIME body
<?xml version="1.0" encoding="utf-8"?>
<PSTN>
    <HighLayerCompatibility>
        <HLOctet3>
            <CodingStandard>00</CodingStandard>
            <Interpretation>100</Interpretation>
            <PresentationMethod>01</PresentationMethod>
        </HLOctet3>
        <HLOctet4>
            <HighLayerCharacteristics>HLC_value</HighLayerCharacteristics>
        </HLOctet4>
    </HighLayerCompatibility>

| | | | + +| | | +|-----------------------------------------------------------------|--------------------------------| +| DSSI Parameter values
SETUP: High Layer Compatibility | | +| Message flow | | +| Test equipment | End device | +| INVITE | →                      → SETUP | +| 100 Trying | ← | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_110 | Reference
subclause 5.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +|----------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Two High layer compatibility information elements received

Ensure that the first PSTN XML HighLayerCompatibility received in the INVITE request is mapped into the first High layer compatibility information element in the sent SETUP and the second PSTN XML HighLayerCompatibility received in the INVITE request is mapped into the second High layer compatibility information element in the sent SETUP | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
INVITE:
PSTN XML MIME body

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>0000001<
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value< | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DSSI parameter values
SETUP:
First high layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=Telephony
Second high layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=HLC_value as indicated in Table 7.2.3.1-6 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|--------------------------------|--------------------------------| +| Message flow | | +| Test equipment | End device | +| INVITE | →                      → SETUP | +| 100 Trying | ← | +| Apply post test routine | | + +**Table 7.2.3.1-6 – Mapping of PSTN XML HighLayerCharacteristic to DSS1 High layer compatibility information element** + +| HLC_value | XML HighLayerCharacteristic | DSS1 High layer characteristics identification | +|-----------|-----------------------------|------------------------------------------------------------------------| +| HLC_VA_1 | '0000001' | Telephony | +| HLC_VA_2 | '0000100' | Facsimile Group 2/3 | +| HLC_VA_3 | '0100001' | Facsimile Group 4 Class I | +| HLC_VA_4 | '0100100' | Facsimile service Group 4, Classes II ad III | +| HLC_VA_5 | '0110010' | Syntax based Videotex | +| HLC_VA_6 | '0110011' | International Videotex interworking via gateways or interworking units | +| HLC_VA_7 | '0110101' | Telex service | +| HLC_VA_8 | '1000010' | FTAM application | +| HLC_VA_9 | '1100000' | Videotelephony | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|------------|---|--|--|----------------------|---|---|-----------------|--|--------------------------------|--|--| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_111 | Reference
subclause 5.1.2.1/
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CALL PROCEEDING received Progress Indicator is present

Ensure that on receipt of a DSS1 CALL PROCEEDING and a Progress Indicator value PI_value, as described in Table 7.2.3.1-4, is present, a 183 Session Progress is sent. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CALL PROCEEDING: Progress Indicator Progress Description = PI_value | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
100 Trying ←
183 Session Progress ← ← CALL PROCEEDING
Apply post test routine
| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 100 Trying | ← | | | 183 Session Progress | ← | ← | CALL PROCEEDING | | Apply post test routine | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ← | ← | CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_112 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
CALL PROCEEDING received Progress Indicator is present

Ensure that on receipt of a DSS1 CALL PROCEEDING, and a Progress Indicator value PI_value is present, as described in Table 7.2.3.1-4, a 183 Session Progress is sent. The 183 Session Progress contains a PSTN XML ProgressIndicator ProgressDescription = PI_value. An additional ProgressIndicator element with value = 7 is present. | | | | +| | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|-------------------|--------|---|---|-------|------------|---|--|--|----------------------|---|---|-----------------|--------------------------------|--|--|--| +| SIP header values
183 Session Progress:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription>PI_value< | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CALL PROCEEDING: Progress Indicator Progress Description = PI_value | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
183 Session Progress ⬅ ⬅ CALL PROCEEDING
Apply post test routine
| | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 100 Trying | ⬅ | | | 183 Session Progress | ⬅ | ⬅ | CALL PROCEEDING | Apply post test routine | | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | ⬅ | CALL PROCEEDING | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_113 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
CALL PROCEEDING received Progress Indicator is not present | | | | +| Ensure that on receipt of a DSS1 CALL PROCEEDING and no Progress Indicator is present, a 183 Session Progress is sent. The 183 Session Progress contains a PSTN XML ProgressIndicator ProgressDescription = 7. | | | | +| SIP header values
183 Session Progress:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | +| DSS1 Parameter values
CALL PROCEEDING: | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 100 Trying | ⬅ | | +| 183 Session Progress | ⬅ | ⬅ CALL PROCEEDING | +| Apply post test routine | | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_114 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.2/4 | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|-------------------|--------|---|---------|------------|---|--|----------------------|---|-------------------|--------------------------------|--|--| +| Test purpose
183 is sent after the SUT has determined independently of access indications that the complete called party number has been received | | | | | | | | | | | | | | | | | | | +| Ensure that the AGCF/VGW is able to send a 183 Session Progress independently of access indications that the complete called party number has been received. | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
183 Session Progress ⬅ ⬅ CALL PROCEEDING
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 100 Trying | ⬅ | | 183 Session Progress | ⬅ | ⬅ CALL PROCEEDING | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | ⬅ CALL PROCEEDING | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_115 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.2/16 | +| Test purpose
The SUT sends a P-Early-Media header if an INVITE (audio) is received | | | | +| Ensure that on receipt of an INVITE request containing a PSTN XML BearerCapability set to speech or audio 3 kBit/s, a P-Early-Media header is sent in a 183 Session Progress response authorize early-media if a CALL PROCEEDING message is received from the terminating user equipment. | | | | + +| | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------|-------------------|--------|----------------------------------|-------|------------|---|--|----------------------|----------------------------------|-----------------|--|--------------------------------|--| +| SIP header values
INVITE: PSTN XML MIME body
P-Erly-Media: supported

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>00000<
or
InformationTransferCabability>10000<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011<

183 Session Progress: P-Early-Media:
SDP answer | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔                              ➔ SETUP
100 Trying ⬅
183 Session Progress ⬅                              ⬅ CALL PROCEEDING
Apply post test routine
| | Test equipment | End device | INVITE | ➔                              ➔ | SETUP | 100 Trying | ⬅ | | 183 Session Progress | ⬅                              ⬅ | CALL PROCEEDING | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | +| INVITE | ➔                              ➔ | SETUP | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅                              ⬅ | CALL PROCEEDING | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_116 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1
and 5.1.3/1 | +| Test purpose
Handling of fallback information BC speech (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback to speech if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives a CALL PROCEEDING. A Bearer Capability IE is present and the Information Transfer Capability indicator is set to speech and a Progress Indicator IE value 5 is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML BearerCapability is present and the InformationTransferCabability element is set to speech and a ProgressIndicator element is present set to value 5. The first stated codec in the SDP answer is not equal CLEARMODE

| | | | + +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<

183 Session Progress: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
ProgressIndicator
ProgressOctet4
ProgressDescription>0000101<
SDP: m= audio xxxx RTP/AVP 8 | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|-----------------------|--|-------------------|--------|---|---|-------|------------|---|--|--|----------------------|---|---|-----------------| +| DSS1 Parameter values
CALL PROCEEDING: Bearer Capability: Information Transfer Capability = speech, Progress Indicator Progress description = 5 | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➠ ➠ SETUP
100 Trying ⬅
183 Session Progress ⬅ ⬅ CALL PROCEEDING

Apply post test routine

| | | Test equipment | | End device | INVITE | ➠ | ➠ | SETUP | 100 Trying | ⬅ | | | 183 Session Progress | ⬅ | ⬅ | CALL PROCEEDING | +| | Test equipment | | End device | | | | | | | | | | | | | | | +| INVITE | ➠ | ➠ | SETUP | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | ⬅ | CALL PROCEEDING | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_117 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1
and 5.1.3/1 | +| Test purpose
Handling of fallback information BC audio (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback to 3.1 kHz audio if the user equipment is not able to support the UDI/TA . The AGCF/VGW receives a CALL PROCEEDING. A Bearer Capability IE is present and the Information Transfer Capability indicator is set to 3.1 kHz audio and a Progress Indicator IE value 5 is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML BearerCapability is present and the InformationTransferCapability element is set to 3.1 kHz audio and a ProgressIndicator element is present set to value 5. The first stated codec in the SDP answer is not equal to CLEARMODE. | | | | + +| SIP header values
INVITE: PSTN XML MIME body
 <?xml version="1.0" encoding="utf-8"?> PSTN   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>10000<   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>10001< 
183 Session Progress: PSTN XML MIME body
 <?xml version="1.0" encoding="utf-8"?> PSTN   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>10000<   ProgressIndicator     ProgressOctet4       ProgressDescription>0000101< 
SDP: m= audio xxxx RTP/AVP 8 | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|--------|---|---------|------------|---|--|----------------------|---|-------------------| +| DSS1 Parameter values
CALL PROCEEDING: Bearer Capability: Information Transfer Capability = speech, Progress Indicator Progress description = 5 | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
100 Trying ←
183 Session Progress ← ← CALL PROCEEDING

Apply post test routine

| | Test equipment | End device | INVITE | → | → SETUP | 100 Trying | ← | | 183 Session Progress | ← | ← CALL PROCEEDING | +| | Test equipment | End device | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | +| 183 Session Progress | ← | ← CALL PROCEEDING | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_118 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1
and 5.1.3/1 | +| Test purpose
Handling of fallback information HLC (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives a CALL PROCEEDING. The High Layer Compatibility IE is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML HighLayerCompatibility is mapped from the DSS1 High Layer Compatibility IE. | | | | + +| | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|-------------------|--------|---|--|---------|------------|---|--|--|----------------------|---|--|-------------------|--------------------------------| +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001< | | | | | | | | | | | | | | | | | | +| 183 Session Progress: HighLayerCompatibility | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CALL PROCEEDING: High Layer Compatibility High Layer Characteristics | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
183 Session Progress ⬅ ⬅ CALL PROCEEDING
| | Test equipment | | End device | INVITE | ➔ | | ➔ SETUP | 100 Trying | ⬅ | | | 183 Session Progress | ⬅ | | ⬅ CALL PROCEEDING | Apply post test routine | +| | Test equipment | | End device | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ SETUP | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | | ⬅ CALL PROCEEDING | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|----------------------------------------------------|-------------------|--------|---|--|---------|------------|---|--|--|----------------------|---|--|-------------------|----------------------|---|--|------------|--------------------------------|--|--| +| TSS
Term_Establishment_of_an_early_dialogue | TP_301_119 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND NOT 5.4/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
PROGRESS received Progress Indicator is present

Ensure that on receipt of a DSS1 PROGRESS and a Progress Indicator value PI_value is present, as described in Table 7.2.3.1-4, a 183 Session Progress is sent. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Progress Indicator Progress Description = PI_value | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
183 Session Progress ⬅ ⬅ CALL PROCEEDING
183 Session Progress ⬅ ⬅ PROGRESS
| | Test equipment | | End device | INVITE | ➔ | | ➔ SETUP | 100 Trying | ⬅ | | | 183 Session Progress | ⬅ | | ⬅ CALL PROCEEDING | 183 Session Progress | ⬅ | | ⬅ PROGRESS | Apply post test routine | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | | ⬅ CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | | ⬅ PROGRESS | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|-----------------|-----------------------|--|-------------------|--|--------|---|--|---|-------|------------|---|--|--|--|-----------------------|---|--|---|-----------------|-----------------------|---|--|---|----------|--------------------------------|--|--|--|--| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_120 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
PROGRESS received Progress Indicator is present | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a DSS1 PROGRESS and a Progress Indicator value PI_value is present, as described in Table 7.2.3.1-4, a 183 Session Progress is sent. The 183 Session Progress contains a PSTN XML ProgressIndicator ProgressDescription = PI_value. An additional ProgressIndicator element with value = 7 is present. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
183 Session Progress2
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription> 0000111 <
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription> PI_value < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Progress Indicator Progress Description = PI_value | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
183 Session Progress1 ⬅ ⬅ CALL PROCEEDING
183 Session Progress2 ⬅ ⬅ PROGRESS
Apply post test routine
| | | | | Test equipment | | End device | | INVITE | ➔ | | ➔ | SETUP | 100 Trying | ⬅ | | | | 183 Session Progress1 | ⬅ | | ⬅ | CALL PROCEEDING | 183 Session Progress2 | ⬅ | | ⬅ | PROGRESS | Apply post test routine | | | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress1 | ⬅ | | ⬅ | CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress2 | ⬅ | | ⬅ | PROGRESS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_121 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | +| Test purpose
PROGRESS received Progress Indicator is not present | | | | +| Ensure that on receipt of a DSS1 PROGRESS and if no Progress Indicator is present, a 183 Session Progress is sent. The 183 Session Progress contains a PSTN XML ProgressIndicator ProgressDescription = 7 | | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| SIP header values
183 Session Progress2
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | +| DSS1 Parameter values
PROGRESS: | | +| Message flow | | +| Test equipment | End device | +| INVITE | ➔ SETUP | +| 100 Trying | ⬅ | +| 183 Session Progress1 | ⬅ CALL PROCEEDING | +| 183 Session Progress2 | ⬅ PROGRESS | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_122 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1
and 5.2/16 | +| Test purpose
The SUT sends a P-Early-Media header if an INVITE (audio) is received | | | | +| Ensure that on receipt of an INVITE request containing a PSTN XML BearerCapability set to speech or audio 3 kBit/s, a P-Early-Media header is sent in a 183 Session Progress response authorize early-media if a CALL PROCEEDING message is received from the terminating user equipment. | | | | +| SIP header values
INVITE: PSTN XML MIME body
P-Early-Media: supported

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011<

183 Session Progress2: P-Early-Media:
SDP answer | | | | + +| | | | +|--------------------------------|-----------------------|-------------------| +| DSSI Parameter values | | | +| PROGRESS: | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 100 Trying | ← | | +| 183 Session Progress1 | ← | ← CALL PROCEEDING | +| 183 Session Progress2 | ← | ← PROGRESS | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_123 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +|----------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Handling of fallback information BC speech (only applicable at T reference point) | +| Ensure that the called user is able to indicate the Fallback to speech if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives a PROGRESS. A Bearer Capability IE is present and the Information Transfer Capability indicator is set to speech and a Progress Indicator IE value 5 is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML BearerCapability is present and the InformationTransferCapability element is set to speech and a ProgressIndicator element is present and set to value 5. The first stated codec in the SDP answer is not equal CLEARMODE. | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10001<
BCoctet4

183 Session Progress2: HighLayerCompatibility | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------| +| DSSI Parameter values
PROGRESS: Bearer Capability: Information Transfer Capability = speech, Progress Indicator Progress description = 5 | +|----------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------------|-----------------------|-------------------| +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 100 Trying | ← | | +| 183 Session Progress1 | ← | ← CALL PROCEEDING | +| 183 Session Progress2 | ← | ← PROGRESS | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|------------|---|--|--|-----------------------|---|---|-----------------|-----------------------|---|---|----------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_124 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Handling of fallback information HLC (only applicable at T reference point) | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that the called user is able to indicate the Fallback if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives a PROGRESS. The High Layer Compatibility IE is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML HighLayerCompatibility is mapped from the DSS1 High Layer Compatibility IE.

| | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10001<
BCoctet4 | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress2: HighLayerCompatibility | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Bearer Capability: Information Transfer Capability = speech, Progress Indicator Progress description = 5 | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➡ ➡ SETUP
100 Trying ⬅
183 Session Progress1 ⬅ ⬅ CALL PROCEEDING
183 Session Progress2 ⬅ ⬅ PROGRESS
Apply post test routine
| | | | | Test equipment | | End device | INVITE | ➡ | ➡ | SETUP | 100 Trying | ⬅ | | | 183 Session Progress1 | ⬅ | ⬅ | CALL PROCEEDING | 183 Session Progress2 | ⬅ | ⬅ | PROGRESS | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➡ | ➡ | SETUP | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress1 | ⬅ | ⬅ | CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress2 | ⬅ | ⬅ | PROGRESS | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_125 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND NOT 5.4/1 | +| Test purpose
ALERTING received Progress Indicator is present | | | | +|

Ensure that on receipt of a DSS1 ALERTING, and if a Progress Indicator value PI_value as described in Table 7.2.3.1-4 is present, a 180 Ringing is sent.

| | | | +| SIP header values | | | | +| DSS1 Parameter values
ALERTING: Progress Indicator Progress Description = PI_value | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 100 Trying | ← | | +| 180 Ringing | ← | ← ALERTING | +| Apply post test routine | | | + +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_126 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|-------------------|--------|---|---------|------------|---|--|-------------|---|------------|--------------------------------|--|--| +| Test purpose
ALERTING received Progress Indicator is not present | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a DSS1 ALERTING and if no Progress Indicator is present, a 180 Ringing is sent. The 180 Ringing contains a PSTN XML ProgressIndicator ProgressDescription = 7 | | | | | | | | | | | | | | | | | | | +| SIP header values
180 Ringing:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ←
180 Ringing ← ← ALERTING
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 100 Trying | ← | | 180 Ringing | ← | ← ALERTING | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_127 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.2/16 | +| Test purpose
ALERTING received Progress Indicator is not present P-Early-Media header is present | | | | +| Ensure that on receipt of a DSS1 ALERTING and if no Progress Indicator is present, a 180 Ringing is sent. The 180 Ringing contains a PSTN XML ProgressIndicator ProgressDescription = 7 and a PSTN XML ProgressIndicator ProgressDescription = 8 and the P-Early-Media authorize the early-media | | | | + +| | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------------------|--|-------------------|--------|----------------------|-------|------------|---|--|-------------|----------------------|----------| +| SIP header values
INVITE:
P-Early-Media: supported

180 Ringing:
P-Early-Media:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0001000<
SDP answer | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: | | | | | | | | | | | | | | +| Message flow | | | | | | | | | | | | | | +|
Test equipment End device
INVITE →                  → SETUP
100 Trying ←
180 Ringing ←                  ← ALERTING
Apply post test routine
| | Test equipment | | End device | INVITE | →                  → | SETUP | 100 Trying | ← | | 180 Ringing | ←                  ← | ALERTING | +| Test equipment | | End device | | | | | | | | | | | | +| INVITE | →                  → | SETUP | | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | | +| 180 Ringing | ←                  ← | ALERTING | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_128 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
ALERTING received Progress Indicator is present

Ensure that on receipt of a DSS1 ALERTING and a Progress Indicator value PI_value as described in Table 7.2.3.1-4 is present, a 180 Ringing is sent. The 180 Ringing contains a PSTN XML ProgressIndicator ProgressDescription = PI_value. An additional ProgressIndicator element with value = 7 is present. | | | | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| SIP header values
180 Ringing:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription> PI_value < | | +| DSS1 Parameter values
ALERTING: Progress Indicator Progress Description = PI_value | | +| Message flow | | +| Test equipment | End device | +| INVITE | → SETUP | +| 100 Trying | ← | +| 180 Ringing | ← ALERTING | +| Apply post test routine | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_129 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of fallback information BC speech (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback to speech if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives an ALERTING. A Bearer Capability IE is present and the Information Transfer Capability indicator is set to speech and a Progress Indicator IE value 5 is present. A 180 Ringing is sent to the calling user equipment, the PSTN XML BearerCapability is present and the InformationTransferCabability element is set to speech and a ProgressIndicator element that is present is set to value 5. The first stated codec in the SDP answer is not equal to CLEARMODE. | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|-------------------|--|--------|---|--|---|-------|------------|---|--|--|--|-------------|---|--|---|----------| +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>00000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10001<

180 Ringing: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>00000<
BCoctet4
ProgressIndicator
ProgressOctet4
ProgressDescription>0000101<
SDP: m= audio xxxx RTP/AVP 8 | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: Bearer Capability: Information Transfer Capability = speech , Progress Indicator Progress description = 5 | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅
180 Ringing ⬅ ⬅ ALERTING

Apply post test routine

| | Test equipment | | End device | | INVITE | ➔ | | ➔ | SETUP | 100 Trying | ⬅ | | | | 180 Ringing | ⬅ | | ⬅ | ALERTING | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_130 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of fallback information HLC (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives an ALERTING. The High Layer Compatibility IE is present. A 180 Ringing is sent to the calling user equipment, the PSTN XML HighLayerCompatibility is mapped from the DSS1 High Layer Compatibility IE. | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------|-------------------|--|-------------------|--------|---|---|-------|------------|---|--|--|-------------|---|---|----------|--------------------------------|--|--|--| +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>00000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10001<

180 Ringing: HighLayerCompatibility | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: Bearer Capability: Information Transfer Capability = speech , Progress Indicator Progress description = 5 | | | | | | | | | | | | | | | | | | | | | | +| Message flow | | | | | | | | | | | | | | | | | | | | | | +|
Test equipment End device
INVITE → → SETUP
100 Trying ←
180 Ringing ← ← ALERTING
Apply post test routine
| | Test equipment | | | End device | INVITE | → | → | SETUP | 100 Trying | ← | | | 180 Ringing | ← | ← | ALERTING | Apply post test routine | | | | +| Test equipment | | | End device | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_131 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of fallback information PI (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives an ALERTING. The Progress Indicator IE value 5 is present. A 180 Ringing is sent to the calling user equipment, the PSTN XML ProgressIndicator is mapped from the DSS1 Progress Indicator IE. | | | | + +**SIP header values** +**INVITE:** PSTN XML MIME body + + PSTN + BearerCapability + BCoctet3 + CodingStandard>00< + InformationTransferCabability>00000< + BCoctet4 + TransferMode>00< + InformationTransferRate>10000< + BCoctet5 + Layer1Identification>01< + UserInfoLayer1Protocol>00011< + BearerCapability + BCoctet3 + CodingStandard>00< + InformationTransferCabability>10001< + BCoctet4 + TransferMode>00< + InformationTransferRate>10000< + BCoctet5 + Layer1Identification>01< + UserInfoLayer1Protocol>00011< + +**180 Ringing:** ProgressIndicator ProgressDescription 5 + +**DSSI Parameter values** +**ALERTING:** Bearer Capability: Information Transfer Capability = **speech**, Progress Indicator Progress description = **5** + +![](89d5117b5c8c5209f100f1f0bf8ef540_img.jpg) + +**Message flow** + +| | Test equipment | | End device | +|-------------|-----------------------|---|-------------------| +| INVITE | → | → | SETUP | +| 100 Trying | ← | | | +| 180 Ringing | ← | ← | ALERTING | + +**Apply post test routine** + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------------------------------------| +| TSS
Term_Establishment_of_an_early_dialogue | TP_301_132 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND NOT 5.4/1 | +| Test purpose
PROGRESS received Progress Indicator is present | | | | +| Ensure that on receipt of a DSSI PROGRESS and a Progress Indicator value PI_value, as described in Table 7.2.3.1-4, is present, a 183 Session Progress is sent. | | | | +| SIP header values | | | | +| DSSI Parameter values
PROGRESS: Progress Indicator Progress Description = PI_value | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ ALERTING | +| 183 Session Progress | ⬅ | ⬅ PROGRESS | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_133 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
PROGRESS received Progress Indicator is present | | | | +| Ensure that on receipt of a DSS1 PROGRESS and a Progress Indicator value PI_value is present as described in Table 7.2.3.1-4, a 183 Session Progress is sent. The 183 Session Progress contains a PSTN XML ProgressIndicator ProgressDescription = PI_value. An additional ProgressIndicator element is present value = 7 | | | | +| SIP header values
183 Session Progress:
PSTN XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription>PI_value< | | | | +| DSS1 Parameter values
PROGRESS: Progress Indicator Progress Description = PI_value | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | ➔ | ➔ | SETUP | +| 180 Ringing | ⬅ | ⬅ | ALERTING | +| 183 Session Progress | ⬅ | ⬅ | PROGRESS | +| Apply post test routine | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_134 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +| Test purpose
PROGRESS received Progress Indicator is not present | | | | +| Ensure that on receipt of a DSS1 PROGRESS and if no Progress Indicator is present, a 183 Session Progress is sent. The 183 Session Progress contains a PSTN XML ProgressIndicator ProgressDescription = 7 | | | | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| SIP header values
183 Session Progress:
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription> 0000111 < | | | +| DSS1 Parameter values
PROGRESS: | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ ALERTING | +| 183 Session Progress | ⬅ | ⬅ PROGRESS | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_135 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.2/16 | +| Test purpose
The SUT sends a P-Early-Media header if an INVITE (audio) is received | | | | +| Ensure that on receipt of an INVITE request containing a PSTN XML BearerCapability set to speech or audio 3 kBit/s , a P-Early-Media header is sent in a 183 Session Progress response authorize early-media if a CALL PROCEEDING message is received from the terminating user equipment. | | | | +| SIP header values
INVITE: PSTN XML MIME body
P-Early-Media: supported


PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability> 00000 <
or
InformationTransferCabability> 10000 <
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011< | | | | +| 183 Session Progress: P-Early-Media: | | | | +| DSS1 Parameter values
PROGRESS: | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ ALERTING | +| 183 Session Progress | ⬅ | ⬅ PROGRESS | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_136 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +|----------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| + +**Test purpose** +*Handling of fallback information BC speech (only applicable at T reference point)* + +Ensure that the called user is able to indicate the Fallback to speech if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives a PROGRESS. A Bearer Capability IE is present and the Information Transfer Capability indicator is set to speech and a Progress Indicator IE value 5 is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML BearerCapability is present and the InformationTransferCapability element is set to speech, and a ProgressIndicator element set to value 5 is present. The first stated codec in the SDP answer is not equal to CLEARMODE. + +**SIP header values** +**INVITE:** PSTN XML MIME body + + PSTN + BearerCapability + BCoctet3 + CodingStandard>00< + InformationTransferCabability>00000< + BearerCapability + BCoctet3 + CodingStandard>00< + InformationTransferCabability>10001< + +**183 Session Progress:** PSTN XML MIME body + + PSTN + BearerCapability + BCoctet3 + CodingStandard>00< + InformationTransferCabability>00000< + ProgressIndicator + ProgressOctet4 + ProgressDescription>0000101< + SDP: m= audio xxxx RTP/AVP 8 + +**DSS1 Parameter values** +**PROGRESS:** Bearer Capability: Information Transfer Capability = speech, Progress Indicator Progress description = 5 + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ ALERTING | +| 183 Session Progress | ⬅ | ⬅ PROGRESS | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|---------------------------------------------------------------|-------------------|-----------------------|--|--|-------------------|--------|---|--|---|-------|-------------|---|--|---|----------|----------------------|---|--|---|----------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_137 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
Handling of fallback information BC audio (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback to 3,1 kHz audio if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives a PROGRESS. A Bearer Capability IE is present and the Information Transfer Capability indicator is set to 3,1 kHz audio and a Progress Indicator IE value 5 is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML BearerCapability is present and the InformationTransferCapability element is set to 3,1 kHz audio and a ProgressIndicator element is present set to value 5. The first stated codec in the SDP answer is not equal to CLEARMODE.

| | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
INVITE: PSTN XML MIME body
<?xml version="1.0" encoding="utf-8"?>
PSTN
  BearerCapability
    BCoctet3
      CodingStandard>00<
      InformationTransferCabability>10000<
  BearerCapability
    BCoctet3
      CodingStandard>00<
      InformationTransferCabability>10001<

183 Session Progress: PSTN XML MIME body
<?xml version="1.0" encoding="utf-8"?>
PSTN
  BearerCapability
    BCoctet3
      CodingStandard>00<
      InformationTransferCabability>10000<
  ProgressIndicator
    ProgressOctet4
      ProgressDescription>0000101<
SDP: m= audio xxxx RTP/AVP

| | | | | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
PROGRESS: Bearer Capability: Information Transfer Capability = 3,1 kHz audio, Progress Indicator Progress description = 5

| | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
183 Session Progress ⬅ ⬅ PROGRESS

Apply post test routine

| | | | | Test equipment | | | End device | INVITE | ➔ | | ➔ | SETUP | 180 Ringing | ⬅ | | ⬅ | ALERTING | 183 Session Progress | ⬅ | | ⬅ | PROGRESS | +| | Test equipment | | | End device | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | | ⬅ | PROGRESS | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|----------------------|---|---|----------| +| TSS
Term_Establishment_of_
an_early_dialogue | TP_301_138 | Reference
subclause 5.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | | | | | | | | | | | | | | | | | +| Test purpose
Handling of fallback information HLC (only applicable at T reference point)

Ensure that the called user is able to indicate the Fallback if the user equipment is not able to support the UDI/TA. The AGCF/VGW receives a PROGRESS. The High Layer Compatibility IE is present. A 183 Session Progress is sent to the calling user equipment, the PSTN XML HighLayerCompatibility is mapped from the DSS1 High Layer Compatibility IE.

| | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: PSTN XML MIME body
<?xml version="1.0" encoding="utf-8"?> PSTN   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCabability>10000<     BCoctet4       TransferMode>00<       InformationTransferRate>10000<     BCoctet5       Layer1Identification>01<       UserInfoLayer1Protocol>00011<   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCabability>10001<     BCoctet4       TransferMode>00<       InformationTransferRate>10000<     BCoctet5       Layer1Identification>01<       UserInfoLayer1Protocol>00011<
183 Session Progress: HighLayerCompatibility | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: High Layer Compatibility High Layer Characteristics | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
183 Session Progress ⬅ ⬅ PROGRESS
Apply post test routine
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 180 Ringing | ⬅ | ⬅ | ALERTING | 183 Session Progress | ⬅ | ⬅ | PROGRESS | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | +| 183 Session Progress | ⬅ | ⬅ | PROGRESS | | | | | | | | | | | | | | | | | + +#### 7.2.3.2 Establishment of a confirmed dialogue + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|---------------|---|----------|-----|---|--|--------------------------------------------|--|--|--------------------------|--|--|--------|---|---------|---------------|---|-----------|-----|---|--|------------------------------------|--|--| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_001 | Reference
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
From, Call-ID, CSeq and Via headers copy from the INVITE

Ensure that the IUT on receipt of an INVITE request, sends a Success (200 OK) including the headers From, Call-ID, CSeq and Via headers copy from the INVITE request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
From:
Call-ID:
CSeq:
Via:

200 OK:
From:
Call-ID:
CSeq:
Via: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE → Ringing
200 OK INVITE ← Off hook
ACK →

Apply post test routine

ISDN interworking
INVITE → → SETUP
200 OK INVITE ← ← CONNECT
ACK →

Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | → | Ringing | 200 OK INVITE | ← | Off hook | ACK | → | |
Apply post test routine

| | | ISDN interworking | | | INVITE | → | → SETUP | 200 OK INVITE | ← | ← CONNECT | ACK | → | |
Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Apply post test routine

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_002 | Reference
sections 8.2.6.2, 12.2.2
and 13.3.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
To tag is sent in the response

Ensure that the IUT on receipt of an INVITE request with no TAG set on the To header, sends a Success (200 OK) response including the same URI and an additional TAG for the To header. | | | | + +| | | | +|-------------------------------------------------------------------------------------------------------|---|-------------------| +| SIP header values
INVITE:
To:

200 OK:
To: ;tag=to_tag | | | +| Message flow | | | +| Test equipment | | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| Apply post test routine | | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| Apply post test routine | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_003 | Reference
section 8.2.6.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
To tag in the INVITE request | | | | +| Ensure that the IUT on receipt of an INVITE request with a TAG set on the To header, either: | | | | +| – sends a Success (200 OK) response including the same URI and the same TAG for the To header (recommended for robustness),
– or reject the INVITE request with a Call/Transaction does not exist (481 Call/Transaction does not exist). | | | | +| SIP header values
INVITE:
To: ;tag=to_tag_value

200 OK:
To: ;tag=to_tag_value | | | | +| Message flow | | | | +| Test equipment | | | End device | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| CASE A | | | | +| 200 OK INVITE | ← | | Off hook | +| ACK | → | | | +| Apply post test routine | | | | +| CASE B | | | | +| 481 Call/Transaction does not exist | ← | | | +| ACK | → | | | + +| | | | +|-------------------------------------|---|-----------| +| ISDN interworking | | | +| INVITE | ➔ | ➔ SETUP | +| CASE A | | | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | ➔ | | +| Apply post test routine | | | +| CASE B | | | +| 481 Call/Transaction does not exist | ← | | +| ACK | ➔ | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|---------------|---|----------|-----|---|--|--------------------------------|--|--|--------------------------|--|--|--------|---|---------|---------------|---|-----------|-----|---|--|--------------------------------|--|--| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_004 | Reference
section 12.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Contact header in the response.

Ensure that the IUT on receipt of an INVITE request, sends a Success (200 OK) response including a single Contact header. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK:
Contact: contact_value > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE➔Ringing
200 OK INVITE←Off hook
ACK➔
Apply post test routine
ISDN interworking
INVITE➔➔ SETUP
200 OK INVITE←← CONNECT
ACK➔
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 200 OK INVITE | ← | Off hook | ACK | ➔ | | Apply post test routine | | | ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 200 OK INVITE | ← | ← CONNECT | ACK | ➔ | | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_005 | Reference
section 12.1.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Record-Route header copied from the INVITE request into the response

Ensure that the IUT on receipt of an INVITE request including a Record-Route header, sends a Success (200 OK) response including a Record-Route header copy from the INVITE request, in the same order. | | | | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------| +| SIP header values
INVITE:
Record-Route: ;lr

200 OK:
Record-Route: ;lr | | | +| Message flow | | | +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| | Apply post test routine | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| | Apply post test routine | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_006 | Reference
section 12.1.1 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Record-Route header with unknown parameter | | | | +| Ensure that the IUT on receipt of an INVITE request including a Record-Route header with parameters that it does not understand, sends a Success (200 OK) response including a Record-Route header copy from the INVITE request, with the unknown parameters. | | | | +| SIP header values
INVITE:
Record-Route:

200 OK:
Record-Route: | | | | +| Message flow | | | | +| | Test equipment | | End device | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| 200 OK INVITE | ← | | Off hook | +| ACK | → | | | +| | Apply post test routine | | | +| ISDN interworking | | | | +| INVITE | → | → | SETUP | +| 200 OK INVITE | ← | ← | CONNECT | +| ACK | → | | | +| | Apply post test routine | | | + +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_007 | Reference
section 12.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------|----------------|--|------------|--------------------------|--|--|--------|---|---------|---------------|---|----------|-----|---|--|-------------------------|--|--|--------------------------|--|--|--------|---|---------|---------------|---|-----------|-----|---|--|-------------------------|--|--| +| Test purpose
From header without "tag"

Ensure that the IUT on receipt of an INVITE request including From header without tag, sends a Success (200 OK) response including a From header without tag . | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
From:

200 OK:
From: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
200 OK INVITE ⬅ Off hook
ACK ➔
Apply post test routine
ISDN interworking
INVITE ➔ ➔ SETUP
200 OK INVITE ⬅ ⬅ CONNECT
ACK ➔
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 200 OK INVITE | ⬅ | Off hook | ACK | ➔ | | Apply post test routine | | | ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 200 OK INVITE | ⬅ | ⬅ CONNECT | ACK | ➔ | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | ⬅ CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_008 | Reference
section 13.3.1.4 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|----------------------|----------------|--|------------|--------------------------|--|--|--------|---|---------|---------------|---|----------|-----|---|--|-------------------------|--|--| +| Test purpose
Allow and a Supported headers sent in response

Ensure that the IUT having received an INVITE request, sends a Success (200 OK) including an Allow and a Supported headers. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK:
Allow:
Supported: | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
200 OK INVITE ⬅ Off hook
ACK ➔
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 200 OK INVITE | ⬅ | Off hook | ACK | ➔ | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | Off hook | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|--------------------------------|---|-----------| +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------|----------------------| +| TSS
Term_Establishment_of_a_confirmed_dialogue | TP_302_009 | Reference
section 6.3.2.4 of
[ETSI TS 183 043] | Selection expression | +| Test purpose
Modifying SDP in confirmed dialogue | | | | +| Ensure that the SUT is able to receive an UPDATE request to modify the SDP in confirmed dialogue. A 200 OK UPDATE with SDP answer is sent. | | | | +| SIP header values | | | | +| 200 OK:
Allow:
Supported: | | | | +| Message flow | | | | +| | Test equipment | | End device | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| 180/183 | ← | | | +| 200 OK INVITE | ← | | Off hook | +| ACK | → | | | +| CASE A | | | | +| INVITE | → | | | +| 200 OK INVITE | ← | | | +| ACK | → | | | +| CASE B | | | | +| UPDATE | → | | | +| 200 OK UPDATE | ← | | | +| Apply post test routine | | | | +| ISDN interworking | | | | +| INVITE | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| 200 OK INVITE | ← | ← | CONNECT | +| ACK | → | | | +| CASE A | | | | +| INVITE | → | | | +| 200 OK INVITE | ← | | | +| ACK | → | | | + +| | | +|--------------------------------|---| +| CASE B | | +| UPDATE | ➔ | +| 200 OK UPDATE | ⬅ | +| Apply post test routine | | + +##### 7.2.3.2.2 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|-------------|-----------------------|--|-------------------|--|--------|---|--|---|-------|-------------|---|--|---|----------|--|--|--|--|--|-----------------|---|--|---|---------|-----|---|--|---|-------------|--------------------------------|--|--|--|--| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_101 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Sending of 200 OK (INVITE) PSTN XML ProgressIndicator is present

Ensure that on receipt of a DSS1 CONNECT message a SIP 200 OK (INVITE) is sent to the calling user equipment. Ensure that if a Progress Indicator IE is present in the CONNECT message, a PSTN XML ProgressIndicator is present in the 200 OK (INVITE) the ProgressDescription is derived from the Progress Description indicator as indicated in Table 7.2.3.2.2-1. Also, an additional PSTN XML ProgressIndicator is present with the ProgressDescription value set to 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE):
PSTM XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription> 0000111 <
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription> PI_value < | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Progress Indicator Progress Description PI_value | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
 
200 OK (INVITE) ⬅ ⬅ CONNECT
ACK ➔ ➔ CONNECT ACK
Apply post test routine
| | | | | Test equipment | | End device | | INVITE | ➔ | | ➔ | SETUP | 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | 200 OK (INVITE) | ⬅ | | ⬅ | CONNECT | ACK | ➔ | | ➔ | CONNECT ACK | Apply post test routine | | | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ | | ⬅ | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | ➔ | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.3.2.2-1 – Mapping of DSS1 Progress Indicator information to PSTN XML ProgressIndicator element** + +| PI_value | XML ProgressIndicator ProgressDescription | DSS1 Progress Indicator value | +|----------|-------------------------------------------|--------------------------------------------------------------------------------------------| +| PI_VA_1 | '0000001' | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | +| PI_VA_2 | '0000010' | Destination address is non-5.1.1/2 | +| PI_VA_3 | '0000011' | Origination address is non-5.1.1/2 | +| PI_VA_4 | '0000100' | Call has returned to the 5.1.1/2 | +| PI_VA_5 | '0000101' | Interworking has occurred and has resulted in a telecommunication service change | +| PI_VA_6 | '0001000' | In-band information or an appropriate pattern is now available | + +| TSS
Term_Establishment_of_a_confirmed_dialogue | TP_302_102 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------------------------------------------------------|------------------------------------------------|--|----------------|--|------------|--------|---|--|---------|-------------|---|--|------------|-----------------|---|--|-----------|-----|---|--|---------------| +| Test purpose
Sending of 200 OK (INVITE) PSTN XML LowLayerCompatibility is present | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a DSS1 CONNECT message a SIP 200 OK (INVITE) is sent to the calling user equipment.
Ensure that if a Low Layer Compatibility IE is present in the CONNECT message, a PSTN XML LowLayerCompatibility is present in the 200 OK (INVITE) the InformationTransferCapability is derived from the Information Transfer Capability indicator as indicated in Table 7.2.3.2.2-2. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE):
PSTN XML MIME body

PSTN
LowLayerCompatibility>
LLOctet3>
CodingStandard>00<
InformationTransferCapability>ITC_VA<
LLOctet4>
TransferMode>00<
InformationTransferRate>10000< | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Low Layer Compatibility Information Transfer Capability ITC_value | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK (INVITE) ← ← CONNECT
ACK → → CONNECT ACK

Apply post test routine

| | | | | Test equipment | | End device | INVITE | → | | → SETUP | 180 Ringing | ← | | ← ALERTING | 200 OK (INVITE) | ← | | ← CONNECT | ACK | → | | → CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | → SETUP | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | ← ALERTING | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | | ← CONNECT | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | → CONNECT ACK | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.3.2.2-2 – DSS1 Low Layer Compatibility to Mapping of PSTN XML +LowLayerCompatibility** + +| ITC_value | LLC Information transfer capability | XML LLC InformationTransferCabability | +|-----------|-------------------------------------|---------------------------------------| +| ITC_VA_1 | Speech | '00000' | +| ITC_VA_2 | 3,1 kHz audio | '10000' | +| ITC_VA_3 | Unrestricted digital info | '01001' | +| ITC_VA_3 | 7 kHz audio | '10001' | + +| | | | | +|-------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_103 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | +|-------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| + +###### **Test purpose** + +*Sending of 200 OK (INVITE) PSTN XML HighLayerCompatibility is present* + +Ensure that on receipt of a DSS1 CONNECT message a SIP 200 OK (INVITE) is sent to the calling user equipment. Ensure that if a High Layer Compatibility IE is present in the CONNECT message, a PSTN XML HighLayerCompatibility is present in the 200 OK (INVITE) the HighLayerCharacteristics element is derived from the High Layer Characteristics indicator as indicated in Table 7.2.3.2.2-3. + +###### **SIP header values** + +###### **200 OK (INVITE):** + + + +PSTN + +###### **HighLayerCompatibility** + +HLOctet3 + +CodingStandard>00< + +Interpretation>100< + +PresentationMethod>01< + +HLOctet4 + +HighLayerCharacteristics>**HLC\_value**< + +###### **DSS1 Parameter values** + +**CONNECT:** High Layer Compatibility High Layer Characteristics **HLC\_value** + +###### **Message flow** + +| | Test equipment | | End device | +|-----------------|-----------------------|---|-------------------| +| INVITE | ➔ | ➔ | SETUP | +| 180 Ringing | ⬅ | ⬅ | ALERTING | +| 200 OK (INVITE) | ⬅ | ⬅ | CONNECT | +| ACK | ➔ | ➔ | CONNECT ACK | + +**Apply post test routine** + +**Table 7.2.3.2.2-3 – Mapping of DSS1 High layer compatibility information element to PSTN XML HighLayerCharacteristic** + +| HLC_value | DSS1 High layer characteristics identification | XML HighLayerCharacteristic | +|-----------|------------------------------------------------------------------------|-----------------------------| +| HLC_VA_1 | Telephony | '0000001' | +| HLC_VA_2 | Facsimile Group 2/3 | '0000100' | +| HLC_VA_3 | Facsimile Group 4 Class I | '0100001' | +| HLC_VA_4 | Facsimile service Group 4, Classes II ad III | '0100100' | +| HLC_VA_5 | Syntax based Videotex | '0110010' | +| HLC_VA_6 | International Videotex interworking via gateways or interworking units | '0110011' | +| HLC_VA_7 | Telex service | '0110101' | +| HLC_VA_8 | FTAM application | '1000010' | +| HLC_VA_9 | Videotelephony | '1100000' | + +| TSS
Term_Establishment_of_a_confirmed_dialogue | TP_302_104 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|-----------------|---|---|---------|-----|---|---|-------------| +| Test purpose
Sending of 200 OK (INVITE) PSTN XML BearerCapability is present

Ensure that on receipt of a DSS1 CONNECT message a SIP 200 OK (INVITE) is sent to the calling user equipment. Ensure that if a Bearer Capability IE is present in the CONNECT message, a PSTN XML BearerCapability is present in the 200 OK (INVITE) the InformationTransferCapability element is derived from the Information Transfer Capability indicator as indicated in Table 7.2.3.2.2-4. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE):

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>ITC_value<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011< | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Bearer Capability Information Transfer Capability ITC_value | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK (INVITE) ← ← CONNECT
ACK → → CONNECT ACK

Apply post test routine

| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 180 Ringing | ← | ← | ALERTING | 200 OK (INVITE) | ← | ← | CONNECT | ACK | → | → | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | ← | CONNECT | | | | | | | | | | | | | | | | | | | | | +| ACK | → | → | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.3.2.2-4 – Mapping of Bearer Capability to PSTN XML BearerCapability** + +| ITC_value | XML InformationTransferCapability | BC Information Transfer Capability | +|-----------|-----------------------------------|------------------------------------| +| ITC_VA_1 | '00000' | Speech | +| ITC_VA_2 | '10000' | 3,1 kHz audio | +| ITC_VA_3 | '01000' | unrestricted digital information | + +| TSS
Term_Establishment_of_a_confirmed_dialogue | TP_302_105 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|-----------------|---|---|---------|-----|---|---|-------------| +| Test purpose
PSTN XML ProgressIndicator value 7 is sent | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the PSTN XML ProgressIndicator is present in the 200 OK (INVITE) if no DSS1 Progress Indicator IE was received in the CONNECT message. The ProgressDescription element is set to value 7 | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK (INVITE):
PSTN XML MIME body

PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK (INVITE) ← ← CONNECT
ACK → → CONNECT ACK

Apply post test routine

| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 180 Ringing | ← | ← | ALERTING | 200 OK (INVITE) | ← | ← | CONNECT | ACK | → | → | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | ← | CONNECT | | | | | | | | | | | | | | | | | | | | | +| ACK | → | → | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_a_confirmed_dialogue | TP_302_106 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of Fallback connection type at the Coincident S and T reference point, fallback does not occur. | | | | +| Ensure that on receipt of a Fallback connection type in the initial INVITE a Bearer Capability IE is received in a CONNECT message and the Information Transfer Capability is set to 7 kHz audio. A 200 OK (INVITE) is sent and a PSTN XML BearerCapability element is present the InformationTransferCapability element is set to 7 kHz audio. The first stated codec is the CLEARMODE codec. | | | | + +| | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------|-------------------|--------|---|---------|-------------|---|------------|---------------------|-------|---------------|-----|---|---------------|--|--------------------------------|--| +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE):

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability> 10001 <
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK (INVITE)

⬅

⬅ CONNECT
ACK ➔ ➔ CONNECT ACK
Apply post test routine
| | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING |
200 OK (INVITE) |
⬅ |
⬅ CONNECT | ACK | ➔ | ➔ CONNECT ACK | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
⬅ |
⬅ CONNECT | | | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ CONNECT ACK | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_107 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/2 | +| Test purpose
Handling of Fallback connection type at the Coincident S and T reference point, fallback to speech occurs.

Ensure that on receipt of a Fallback connection type in the initial INVITE a Bearer Capability IE is received in a CONNECT message and the Information Transfer Capability is set to speech. A 200 OK (INVITE) is sent and a PSTN XML BearerCapability element is present the InformationTransferCapability element is set to speech. The first stated codec is not the CLEARMODE codec | | | | + +###### **SIP header values** + +INVITE: PSTN XML MIME body + +<?xml version="1.0" encoding="utf-8"?> + +PSTN + +BearerCapability + +BCoctet3 + +CodingStandard>00< + +InformationTransferCapability>00000< + +or + +InformationTransferCapability>10000< + +BearerCapability + +BCoctet3 + +CodingStandard>00< + +InformationTransferCapability>10001< + +SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec + +###### **200 OK (INVITE):** + +<?xml version="1.0" encoding="utf-8"?> + +PSTN + +**BearerCapability** + +BCoctet3 + +CodingStandard>00< + +      InformationTransferCapability>**00000**< + +###### **DSS1 Parameter values** + +**CONNECT: Bearer Capability Information Transfer Capability =speech** + +###### **Message flow** + +| | Test equipment | | End device | +|-----------------|-----------------------|---|-------------------| +| INVITE | ➔ | ➔ | SETUP | +| 180 Ringing | ⬅ | ⬅ | ALERTING | +| 200 OK (INVITE) | ⬅ | ⬅ | CONNECT | +| ACK | ➔ | ➔ | CONNECT ACK | + +**Apply post test routine** + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_108 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/2 | +|

Test purpose
Handling of Fallback connection type at the Coincident S and T reference point, fallback to audio occurs.

Ensure that on receipt of a Fallback connection type in the initial INVITE a Bearer Capability IE is received in a CONNECT message and the Information Transfer Capability is set to 3.1 kHz audio. A 200 OK (INVITE) is sent and a PSTN XML BearerCapability element is present the InformationTransferCapability element is set to 3.1 kHz audio. The first stated codec is not the CLEARMODE codec.

| | | | + +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|-----------------------|-------------------|--------|---|---------|-------------|---|------------|---------------------|-------|---------------|-----|---|---------------| +| 200 OK (INVITE):

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability> 10000 < | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Bearer Capability Information Transfer Capability =3.1 kHz audio | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ← ← ALERTING

200 OK (INVITE)

←

← CONNECT
ACK ➔ ➔ CONNECT ACK

Apply post test routine

| | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 180 Ringing | ← | ← ALERTING |
200 OK (INVITE) |
← |
← CONNECT | ACK | ➔ | ➔ CONNECT ACK | +| | Test equipment | End device | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
← |
← CONNECT | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ CONNECT ACK | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------------------| +| TSS
Term_Establishment_of_a_confirmed_dialogue | TP_302_109 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 AND 5.1.3/2 | +| Test purpose
Handling of Fallback connection type at the Coincident S and T reference point, no BC IE received

Ensure that on receipt of a Fallback connection type in the initial INVITE no Bearer Capability IE is received in a CONNECT message. A 200 OK (INVITE) is sent and a PSTN XML BearerCapability element is present the InformationTransferCapability element is set to the value indicated in the INVITE (speech or 3.1 kHz audio). The first stated codec is not the CLEARMODE codec. | | | | + +###### **SIP header values** + +INVITE: PSTN XML MIME body + +<?xml version="1.0" encoding="utf-8"?> + +PSTN + +BearerCapability + +BCoctet3 + +CodingStandard>00< + +InformationTransferCabability>00000< + +or + +InformationTransferCabability>10000< + +BearerCapability + +BCoctet3 + +CodingStandard>00< + +InformationTransferCabability>10001< + +SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec + +###### **200 OK (INVITE):** + +<?xml version="1.0" encoding="utf-8"?> + +PSTN + +**BearerCapability** + +BCoctet3 + +CodingStandard>00< + +      InformationTransferCabability>**10000**< + +###### **DSSI Parameter values** + +###### **Message flow** + +| | Test equipment | | End device | +|-----------------|-----------------------|---|-------------------| +| INVITE | ➔ | ➔ | SETUP | +| 180 Ringing | ⬅ | ⬅ | ALERTING | +| 200 OK (INVITE) | ⬅ | ⬅ | CONNECT | +| ACK | ➔ | ➔ | CONNECT ACK | + +**Apply post test routine** + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_110 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/2 | +| Test purpose
Handling of Fallback connection type at the Coincident S and T reference point, HLC IE received

Ensure that on receipt of a Fallback connection type in the initial INVITE and a High Layer Compatibility IE is received in a CONNECT message, a 200 OK (INVITE) is sent and a PSTN XML HighLayerCompatibility is present with the HighLayerCharacteristics element set to the value indicated in Table 7.2.3.2.2-3. The first stated codec is not the CLEARMODE codec. | | | | + +| | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|--------|---|---------|-------------|---|------------|---------------------|-------|---------------|-----|---|---------------| +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>00000<
or
InformationTransferCabability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10001<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | +| 200 OK (INVITE):

PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics> HLC_VA < | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: High Layer Compatibility High Layer Characteristics=HLC_VA | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK (INVITE)

⬅

⬅ CONNECT
ACK ➔ ➔ CONNECT ACK

Apply post test routine

| | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING |
200 OK (INVITE) |
⬅ |
⬅ CONNECT | ACK | ➔ | ➔ CONNECT ACK | +| | Test equipment | End device | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | +|
200 OK (INVITE) |
⬅ |
⬅ CONNECT | | | | | | | | | | | | | | +| ACK | ➔ | ➔ CONNECT ACK | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_111 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/2 | +| Test purpose
Handling of Fallback connection type at the Coincident S and T reference point, HLC IE not received

Ensure that on receipt of a Fallback connection type in the initial INVITE and a High Layer Compatibility IE is not received in a CONNECT message. A 200 OK (INVITE) is sent and a PSTN XML HighLayerCompatibility is present the HighLayerCharacteristics element is set to the value received in the initial INVITE as indicated in Table 7.2.3.2.2-3. The first stated codec is not the CLEARMODE codec | | | | + +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>00000<
or
InformationTransferCabability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>10001<
HighLayerCompatibility
HLOctet4
HighLayerCharacteristics> HLC_VA <
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec

200 OK (INVITE):

PSTN
HighLayerCompatibility
..
HLOctet4
HighLayerCharacteristics> HLC_VA < | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|-------------------|--------|---|---|-------|-------------|---|---|----------|---------------------|-------|-------|-------------|-----|---|---|-------------| +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK (INVITE)

⬅

⬅

CONNECT
ACK ➔ ➔ CONNECT ACK

Apply post test routine

| | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 180 Ringing | ⬅ | ⬅ | ALERTING |
200 OK (INVITE) |
⬅ |
⬅ |
CONNECT | ACK | ➔ | ➔ | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
⬅ |
⬅ |
CONNECT | | | | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ | CONNECT ACK | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_112 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of Fallback connection type at the T reference point, fallback does not occur.

Ensure that on receipt of a Fallback connection type in the initial INVITE a Bearer Capability IE is received in a CONNECT message and the Information Transfer Capability is set to 7 kHz audio. A 200 OK (INVITE) is sent and a PSTN XML BearerCapability element is present the InformationTransferCabability element is set to 7 kHz audio. The first stated codec is the CLEARMODE codec. | | | | + +|

SIP header values

INVITE: PSTN XML MIME body

<?xml version="1.0" encoding="utf-8"?> PSTN   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>00000<       or       InformationTransferCapability>10000<   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>10001<

SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec

200 OK (INVITE):

<?xml version="1.0" encoding="utf-8"?>   BearerCapability     BCoctet3       CodingStandard>00<       InformationTransferCapability>10001<

SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec

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

DSS1 Parameter values

CONNECT: Bearer Capability Information Transfer Capability =7 kHz audio, Progress Indicator Progress description = 5

| | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING

200 OK (INVITE) ← ← CONNECT
ACK → → CONNECT ACK

Apply post test routine

| | | | Test equipment | | End device | INVITE | → | → | SETUP | 180 Ringing | ← | ← | ALERTING |
| | | | 200 OK (INVITE) | ← | ← | CONNECT | ACK | → | → | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | ← | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | → | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_113 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +|

Test purpose

Handling of Fallback connection type at the T reference point, fallback to speech occurs.

Ensure that on receipt of a Fallback connection type in the initial INVITE a Bearer Capability IE is received in a CONNECT message and the Information Transfer Capability is set to speech and a ProgressIndicator element is present which is set to value 5. A 200 OK (INVITE) is sent and a PSTN XML BearerCapability element is present which the InformationTransferCapability element is set to speech. The first stated codec is not the CLEARMODE codec

| | | | + +| | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|--------|---|---------|-------------|---|------------|---------------------|-------|---------------|-----|---|---------------| +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | +| 200 OK (INVITE):

BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability> 00000 <
ProgressIndicator
ProgressOctet4
ProgressDescription> 0000101 < | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Bearer Capability Information Transfer Capability = speech, Progress Indicator Progress description = 5 | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK (INVITE)

⬅

⬅ CONNECT
ACK ➔ ➔ CONNECT ACK

Apply post test routine

| | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING |
200 OK (INVITE) |
⬅ |
⬅ CONNECT | ACK | ➔ | ➔ CONNECT ACK | +| | Test equipment | End device | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | +|
200 OK (INVITE) |
⬅ |
⬅ CONNECT | | | | | | | | | | | | | | +| ACK | ➔ | ➔ CONNECT ACK | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_114 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of Fallback connection type at the T reference point, fallback to audio occurs.

Ensure that on receipt of a Fallback connection type in the initial INVITE a Bearer Capability IE is received in a CONNECT message and the Information Transfer Capability is set to 3.1 kHz audio and a ProgressIndicator element is present which is set to value 5. A 200 OK (INVITE) is sent and where a PSTN XML BearerCapability element is present the InformationTransferCapability element is set to 3.1 kHz audio. The first stated codec is not the CLEARMODE codec | | | | + +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|-----------------------|-------------|-------------------|--|--------|---|--|---|-------|-------------|---|--|---|----------|---------------------|-------|--|-------|-------------|-----|---|--|---|-------------| +| 200 OK (INVITE):

BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability> 10000 <
ProgressIndicator
ProgressOctet4
ProgressDescription> 0000101 < | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Bearer Capability Information Transfer Capability = speech, Progress Indicator Progress description = 5 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK (INVITE)

⬅

⬅

CONNECT
ACK ➔ ➔ CONNECT ACK

Apply post test routine

| | | Test equipment | | End device | | INVITE | ➔ | | ➔ | SETUP | 180 Ringing | ⬅ | | ⬅ | ALERTING |
200 OK (INVITE) |
⬅ | |
⬅ |
CONNECT | ACK | ➔ | | ➔ | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
⬅ | |
⬅ |
CONNECT | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | ➔ | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_a_confirmed_dialogue | TP_302_115 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of Fallback connection type at the T reference point, no BC IE received

Ensure that on receipt of a Fallback connection type in the initial INVITE no Bearer Capability IE is received in a CONNECT message. A 200 OK (INVITE) is sent and if a PSTN XML BearerCapability element is present, the InformationTransferCapability element is set to the value indicated in the INVITE (speech or 2.1 kHz audio). The first stated codec is not the CLEARMODE codec | | | | + +**SIP header values** + INVITE: PSTN XML MIME body + + PSTN +   **BearerCapability** +     BCoctet3 +       CodingStandard>00< +       InformationTransferCapability>00000< +       or +       InformationTransferCapability>10000< +   **BearerCapability** +     BCoctet3 +       CodingStandard>00< +       InformationTransferCapability>10001< + +SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec + +**200 OK (INVITE):** + +   **BearerCapability** +     BCoctet3 +       CodingStandard>00< +       InformationTransferCapability>**10000**< +   **ProgressIndicator** +     ProgressOctet4 +     ProgressDescription>**0000101**< + +###### **DSS1 Parameter values** + +![](4d6060683ee37bbcddee47a4710c16d1_img.jpg) + +**Message flow** + +| | Test equipment | | End device | +|-----------------|-----------------------|---|-------------------| +| INVITE | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| 200 OK (INVITE) | ← | ← | CONNECT | +| ACK | → | → | CONNECT ACK | + +**Apply post test routine** + +| | | | | +|-------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_116 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +|-------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| + +**Test purpose** +*Handling of Fallback connection type at the T reference point, HLC IE received* + +Ensure that on receipt of a Fallback connection type in the initial INVITE and if a High Layer Compatibility IE is received in a CONNECT message, a 200 OK (INVITE) is sent and a PSTN XML HighLayerCompatibility is present the HighLayerCharacteristics element is set to the value indicated in Table 7.2.3.2.2-3. The first stated codec is not the CLEARMODE codec. + +| SIP header values
INVITE: PSTN XML MIME body

PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|-------------------|--|--------|---|--|---|-------|-------------|---|--|---|----------|---------------------|-------|--|-------|-------------|-----|---|--|---|-------------| +| 200 OK (INVITE):

HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics> HLC_VA < | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: High Layer Compatibility, High Layer Characteristics=HLC_VA | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK (INVITE)

⬅

⬅

CONNECT
ACK ➔ ➔ CONNECT ACK

Apply post test routine

| | Test equipment | | End device | | INVITE | ➔ | | ➔ | SETUP | 180 Ringing | ⬅ | | ⬅ | ALERTING |
200 OK (INVITE) |
⬅ | |
⬅ |
CONNECT | ACK | ➔ | | ➔ | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
⬅ | |
⬅ |
CONNECT | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | ➔ | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
Term_Establishment_of_
a_confirmed_dialogue | TP_302_117 | Reference
subclause 5.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1
AND 5.1.3/1 | +| Test purpose
Handling of Fallback connection type at the T reference point, HLC IE not received

Ensure that on receipt of a Fallback connection type in the initial INVITE and no High Layer Compatibility IE is received in a CONNECT message. A 200 OK (INVITE) is sent and no PSTN XML HighLayerCompatibility is present. The first stated codec is not the CLEARMODE codec. | | | | + +|

SIP header values
INVITE: PSTN XML MIME body
<?xml version="1.0" encoding="utf-8"?>
PSTN
  BearerCapability
    BCoctet3
      CodingStandard>00<
      InformationTransferCabability>00000<
      or
      InformationTransferCabability>10000<
  BearerCapability
    BCoctet3
      CodingStandard>00<
      InformationTransferCabability>10001<

SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec

200 OK (INVITE):

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

DSS1 Parameter values
CONNECT: High Layer Compatibility, High Layer Characteristics=HLC_VA

| | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ➔ ➔ ALERTING

200 OK (INVITE)

➔

➔

CONNECT
ACK ➔ ➔ CONNECT ACK

Apply post test routine

| | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 180 Ringing | ➔ | ➔ | ALERTING |
200 OK (INVITE) |
➔ |
➔ |
CONNECT | ACK | ➔ | ➔ | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | +| 180 Ringing | ➔ | ➔ | ALERTING | | | | | | | | | | | | | | | | | | +|
200 OK (INVITE) |
➔ |
➔ |
CONNECT | | | | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ | CONNECT ACK | | | | | | | | | | | | | | | | | | + +#### 7.2.3.3 Call release + +##### 7.2.3.3.1 Release initiated by the originating user + +|

TSS
Term_Release_initiated_
by_the_originating_user

| TP_303_001 | Reference
section 15 of
[IETF RFC 3261]
and
5.1.2.4 of [ETSI TS 183 036] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------------------------------------|----------------------|--|-----------------------|--|-------------------|--------------------------|--|--|--|--------|---|--|---------|-------------|---|--|--|---------------|---|--|----------|-----|---|--|--|-----|---|--|--|------------|---|--|--| +|

Test purpose
BYE received in the confirmed dialogue

Ensure that that the IUT, while a session has been established, on receipt of a BYE request sends a Success (200 OK) response.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
Interworking POTS
INVITE ➔ Ringing
180 Ringing ➔
200 OK INVITE ➔ Off hook
ACK ➔
BYE ➔
200 OK BYE ➔
| | | | | Test equipment | | End device | Interworking POTS | | | | INVITE | ➔ | | Ringing | 180 Ringing | ➔ | | | 200 OK INVITE | ➔ | | Off hook | ACK | ➔ | | | BYE | ➔ | | | 200 OK BYE | ➔ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ➔ | | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|--------------------------|---|--------------------| +| ISDN interworking | | | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | ➔ | | +| BYE | ➔ | ➔ DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | ➔ RELEASE COMPLETE | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------------|----------------------|---------------------|--|--|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|-----|---|--|------------|---|--|------------------------|---|--|-----|---|--|------------------------------|--|--|--------|---|---------|-------------|---|------------|-----|---|-----------|------------|---|--------------------|------------------------|---|--|-----|---|--| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_002 | Reference
sections 15 and 12 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
BYE received in the early dialogue

Ensure that the IUT, while the dialogue is in an early stage, on receipt of a BYE request sends a response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
180 Ringing ←
BYE ➔
200 OK BYE ←
487 Request Terminated ←
ACK ➔

ISDN interworking
INVITE ➔ ➔ SETUP
180 Ringing ← ← ALERTING
BYE ➔ ➔ RELEASE
200 OK BYE ← ← RELEASE COMPLETE
487 Request Terminated ←
ACK ➔
| | | | Message flow | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 180 Ringing | ← | | BYE | ➔ | | 200 OK BYE | ← | | 487 Request Terminated | ← | | ACK | ➔ | |
ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 180 Ringing | ← | ← ALERTING | BYE | ➔ | ➔ RELEASE | 200 OK BYE | ← | ← RELEASE COMPLETE | 487 Request Terminated | ← | | ACK | ➔ | | +| Message flow | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ➔ | ➔ RELEASE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | ← RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|----------------------| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_003 | Reference
sections 8.2.2 and
15.1.2/[IETF RFC 3261] | Selection expression | +| Test purpose
BYE received with unknown header field

Ensure that the IUT, once a dialogue has been established, on receipt of a BYE request including a header that it does not understand sends a Success (200 OK) response. | | | | +| SIP header values | | | | +| BYE:
Unknown-Header: testing | | | | + +| Message flow | | | +|--------------------------|----------------|--------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | | +| ACK | → | | +| BYE | → | | +| 200 OK BYE | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | → | → DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | → RELEASE COMPLETE | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------------------------------------------------------|----------------------| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_004 | Reference
sections 8.2.6.2 and 15.1.2
of [IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| 200 OK BYE contains the same From, Call-Id, CSeq and Via header as in the request | | | | +| Ensure that the IUT, once a dialogue has been established, on receipt of a BYE request, sends a Success (200 OK) response with From, Call-ID, CSeq and Via headers set to the same value as in the request. | | | | +| SIP header values | | | | +| BYE:
Via: any_bye_via_value;branch=z9hG4bK any_bye_branch_value
From: any_bye_from_value;tag=any_bye_from_tag_value
Call-ID: any_bye_call-id_value
CSeq: any_bye_cseq | | | | +| 200 OK BYE
Via: any_bye_via_value;branch=z9hG4bK any_bye_branch_value
From: any_bye_from_value;tag=any_bye_from_tag_value
Call-ID: any_bye_call-id_value
CSeq: any_bye_cseq | | | | +| Message flow | | | | +| | Test equipment | End device | | +| Interworking POTS | | | | +| INVITE | → | Ringing | | +| 180 Ringing | ← | | | +| 200 OK INVITE | ← | | | +| ACK | → | | | +| BYE | → | | | +| 200 OK BYE | ← | | | + +| | | | +|--------------------------|---|--------------------| +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | → | → DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | → RELEASE COMPLETE | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------|----------------------|---------------------|--|--|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|--------|---|--|---------------|---|--|------------------------|---|--|-----|---|--|--------------------------|--|--|--------|---|---------|-------------|---|------------|--------|---|----------------------------|---------------|---|--|------------------------|---|--|-----|---|--| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_005 | Reference
section 9.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CANCEL received in the early dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL answers to the original INVITE request with a Request Terminated (487 Request Terminated) response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Message flow
Test equipmentEnd device
Interworking POTS
INVITE→Ringing
180 Ringing←
CANCEL→
200 OK CANCEL←
487 Request Terminated←
ACK→
ISDN interworking
INVITE→→ SETUP
180 Ringing←← ALERTING
CANCEL→→ RELEASE/RELEASE COMPLETE
200 OK CANCEL←
487 Request Terminated←
ACK→
| | | | Message flow | | | | Test equipment | End device | Interworking POTS | | | INVITE | → | Ringing | 180 Ringing | ← | | CANCEL | → | | 200 OK CANCEL | ← | | 487 Request Terminated | ← | | ACK | → | | ISDN interworking | | | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | CANCEL | → | → RELEASE/RELEASE COMPLETE | 200 OK CANCEL | ← | | 487 Request Terminated | ← | | ACK | → | | +| Message flow | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CANCEL | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK CANCEL | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CANCEL | → | → RELEASE/RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK CANCEL | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### 7.2.3.3.1.2 Test purposes for ISDN + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_101 | Reference
subclause 5.1.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
BYE received in the confirmed dialogue | | | | +| Ensure that on receipt of a BYE request in the confirmed dialogue a DISCONNECT message is sent to the called user equipment. The location is coded '1010' network beyond interworking point. | | | | +| SIP header values | | | | + +| | | | +|-----------------------------------------------------------------|-----------------------|--------------------| +| DSS1 Parameter values | | | +| DISCONNECT: location='1010' (network beyond interworking point) | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK (INVITE) | ← | ← CONNECT | +| ACK | → | → CONNECT ACK | +| BYE | → | → DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | → RELEASE COMPLETE | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_102 | Reference
subclause 5.1.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose | | | | +| BYE received before an early dialogue is established | | | | +| Ensure that on receipt of a BYE request, before an early dialogue is established, a RELEASE or RELEASE COMPLETE message is sent to the called user equipment. The location is coded '1010' network beyond interworking point. | | | | +| SIP header values | | | | +| RELEASE or RELEASE COMPLETE: location='1010' (network beyond interworking point) | | | | +| DSS1 Parameter values | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | → | | → SETUP | +| 100 Trying | ← | | | +| BYE | → | | | +| 200 OK BYE | ← | | | +| CASE A | | | → RELEASE | +| | | | ← RELEASE COMPLETE | +| CASE B | | | → RELEASE COMPLETE | +| 487 Request Terminated | ← | | | +| ACK | → | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|------------|---|--|--|--------|---|--|--|---------------|---|--|--|-------------------|--|-------|-------------|--|--|---|------------------|-------------------|--|--|--|--|--|---|------------------|----------------------------|-------|--|--|-----|---|--|--| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_103 | Reference
subclause 5.1.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CANCEL received before an early dialogue is established | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a CANCEL request, before an early dialogue is established, a RELEASE or RELEASE COMPLETE message is sent to the called user equipment. The location is coded '1010' network beyond interworking point. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
RELEASE or RELEASE COMPLETE: location='1010' (network beyond interworking point) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
100 Trying ←
CANCEL →
200 OK CANCEL ←

CASE A

→

RELEASE
← RELEASE COMPLETE

CASE B
→ RELEASE COMPLETE

487 Request Terminated

←
ACK →
| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 100 Trying | ← | | | CANCEL | → | | | 200 OK CANCEL | ← | | |
CASE A | |
→ |
RELEASE | | | ← | RELEASE COMPLETE |
CASE B | | | | | | → | RELEASE COMPLETE |
487 Request Terminated |
← | | | ACK | → | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CANCEL | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK CANCEL | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE A | |
→ |
RELEASE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
487 Request Terminated |
← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|----------------------|---|---|-----------------|---------|-------|--|--|------------|---|--|--| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_104 | Reference
subclause 5.1.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
BYE received after an early dialogue is established | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a BYE request, after an early dialogue by means of sending a 183 Session Progress is established, a RELEASE or RELEASE COMPLETE message is sent to the called user equipment. The location is coded '1010' network beyond interworking point. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
RELEASE or RELEASE COMPLETE: location='1010' (network beyond interworking point) | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
183 Session Progress ← ← CALL PROCEEDING

BYE

→
200 OK BYE ←
| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 183 Session Progress | ← | ← | CALL PROCEEDING |
BYE |
→ | | | 200 OK BYE | ← | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ← | ← | CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | +|
BYE |
→ | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|------------------------|---|------------------| +| CASE B | ➔ | RELEASE | +| | ➔ | RELEASE COMPLETE | +| CASE C | | | +| | ➔ | RELEASE COMPLETE | +| 487 Request Terminated | ➔ | | +| ACK | ➔ | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|----------------------|---|---|-----------------|------------|-------|--|--|---------------|---|--|--|-------------------|--|-------|-------------|--|--|---|------------------|-------------------|--|--|--|--|--|---|------------------|----------------------------|-------|--|--|-----|---|--|--| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_105 | Reference
subclause 5.1.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CANCEL received after an early dialogue is established | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a CANCEL request, after an early dialogue by means of sending a 183 Session Progress is established, a RELEASE or RELEASE COMPLETE message is sent to the called user equipment. The location is coded '1010' network beyond interworking point. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
RELEASE or RELEASE COMPLETE: location='1010' (network beyond interworking point) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
183 Session Progress ➔ ➔ CALL PROCEEDING

CANCEL

➔
200 OK CANCEL ➔

CASE A

➔

RELEASE
➔ RELEASE COMPLETE

CASE B
➔ RELEASE COMPLETE

487 Request Terminated

➔
ACK ➔
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 183 Session Progress | ➔ | ➔ | CALL PROCEEDING |
CANCEL |
➔ | | | 200 OK CANCEL | ➔ | | |
CASE A | |
➔ |
RELEASE | | | ➔ | RELEASE COMPLETE |
CASE B | | | | | | ➔ | RELEASE COMPLETE |
487 Request Terminated |
➔ | | | ACK | ➔ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Session Progress | ➔ | ➔ | CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CANCEL |
➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK CANCEL | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE A | |
➔ |
RELEASE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
487 Request Terminated |
➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_106 | Reference
subclause 5.1.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
BYE received after an early dialogue is established | | | | +| Ensure that on receipt of a BYE request, after an early dialogue by means of sending a 180 Ringing is established, a RELEASE or RELEASE COMPLETE message is sent to the called user equipment. The location is coded '1010' network beyond interworking point. | | | | + +| | | | +|----------------------------------------------------------------------------------|-----------------------|--------------------| +| SIP header values | | | +| RELEASE or RELEASE COMPLETE: location='1010' (network beyond interworking point) | | | +| DSSI Parameter values | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 183 Session Progress | ← | ← CALL PROCEEDING | +| BYE | → | | +| 200 OK BYE | ← | | +| CASE B | | | +| | | → RELEASE | +| | | ← RELEASE COMPLETE | +| CASE C | | | +| | | → RELEASE COMPLETE | +| 487 Request Terminated | ← | | +| ACK | → | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------| +| TSS
Term_Release_initiated_
by_the_originating_user | TP_303_107 | Reference
subclause 5.1.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose | | | | +| CANCEL received after an early dialogue is established | | | | +| Ensure that on receipt of a CANCEL request, after an early dialogue by means of sending a 180 Ringing is established, a RELEASE or RELEASE COMPLETE message is sent to the called user equipment. The location is coded '1010' network beyond interworking point. | | | | +| SIP header values | | | | +| RELEASE or RELEASE COMPLETE: location='1010' (network beyond interworking point) | | | | +| DSSI Parameter values | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | → | | → SETUP | +| 183 Session Progress | ← | | ← CALL PROCEEDING | +| CANCEL | → | | | +| 200 OK CANCEL | ← | | | +| CASE A | | | | +| | | → RELEASE | | +| | | ← RELEASE COMPLETE | | +| CASE B | | | | +| | | → RELEASE COMPLETE | | +| 487 Request Terminated | ← | | | +| ACK | → | | | + +##### 7.2.3.3.2 Release initiated by the terminating user + +| TSS
Term_Release_initiated_
by_the_terminating_user | TP_304_001 | Reference
sections 17.2.3.1, 13.3.1.4
and Figure 7 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------------------------------------------------------------------|----------------------|-----------------------|-------------------|--------------------------|--|----------|---------|---------------|--|----------------|-------------|-------------------------------|--|--------------------------|--|----------|---------|---------------|------------|----------------|--------------------|-------------------------------|--| +| Test purpose
The transaction enters the completed state | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT when a server INVITE transaction is in the Proceeding state, after sending a unsuccessful final response, enters in the Completed state. | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE → Ringing
180 Ringing ←
4xx response ← Reject call
Verify completed state
ISDN interworking
INVITE → → SETUP
180 Ringing ← ← ALERTING
4xx response ← ← RELEASE_COMPLETE
Verify completed state
| | | | Test equipment | End device | Interworking POTS | | INVITE → | Ringing | 180 Ringing ← | | 4xx response ← | Reject call | Verify completed state | | ISDN interworking | | INVITE → | → SETUP | 180 Ringing ← | ← ALERTING | 4xx response ← | ← RELEASE_COMPLETE | Verify completed state | | +| Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing ← | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4xx response ← | Reject call | | | | | | | | | | | | | | | | | | | | | | | | | +| Verify completed state | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | +| 4xx response ← | ← RELEASE_COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | +| Verify completed state | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Release_initiated_
by_the_terminating_user | TP_304_002 | Reference
sections 17.2.3.1, 13.3.1.4
and Figure 7 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------------------------------------------------------------------|----------------------|-----------------------|-------------------|--------------------------|--|----------|---------|---------------|--|----------------|-------------|-------|--|-------------------------------|--|--------------------------|--|----------|---------|---------------|------------|----------------|--------------------|-------|--|-------------------------------|--| +| Test purpose
The transaction enters the confirmed state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT when a server INVITE transaction is in the Completed state, on receipt of an ACK request, enters in the Confirmed transaction state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE → Ringing
180 Ringing ←
4xx_response ← Reject call
ACK →
Verify confirmed state
ISDN interworking
INVITE → → SETUP
180 Ringing ← ← ALERTING
4xx_response ← ← RELEASE_COMPLETE
ACK →
Verify confirmed state
| | | | Test equipment | End device | Interworking POTS | | INVITE → | Ringing | 180 Ringing ← | | 4xx_response ← | Reject call | ACK → | | Verify confirmed state | | ISDN interworking | | INVITE → | → SETUP | 180 Ringing ← | ← ALERTING | 4xx_response ← | ← RELEASE_COMPLETE | ACK → | | Verify confirmed state | | +| Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4xx_response ← | Reject call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Verify confirmed state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4xx_response ← | ← RELEASE_COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Verify confirmed state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Release_initiated_
by_the_terminating_user | TP_304_003 | Reference
section 12.2.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|----------------------|----------------|--|------------|--------------------------|--|--|--------|---|---------|-------------|---|--|---------------|---|----------|-----|---|--|-----|---|---------|------------|---|--|--------------------------|--|--|--------|---|---------|-------------|---|------------|---------------|---|-----------|-----|---|--|-----|---|-----------|------------|---|--------------------| +| Test purpose
To header in the BYE is set to the From header in the previous received request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, once a dialogue has been established to release it, sends a BYE request with a To header set to the same value as in the From header of the previous received request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
From: any_invite_from_value;tag=any_invite1_from_tag_value

BYE:
To: any_invite_from_value;tag=any_invite1_from_tag_value | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
180 Ringing ⬅
200 OK INVITE ⬅ Off hook
ACK ➔
BYE ⬅ On hook
200 OK BYE ➔
ISDN interworking
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
200 OK INVITE ⬅ ⬅ CONNECT
ACK ➔
BYE ⬅ ⬅ RELEASE
200 OK BYE ➔ ➔ RELEASE COMPLETE
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 180 Ringing | ⬅ | | 200 OK INVITE | ⬅ | Off hook | ACK | ➔ | | BYE | ⬅ | On hook | 200 OK BYE | ➔ | | ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING | 200 OK INVITE | ⬅ | ⬅ CONNECT | ACK | ➔ | | BYE | ⬅ | ⬅ RELEASE | 200 OK BYE | ➔ | ➔ RELEASE COMPLETE | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ⬅ | On hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | ⬅ CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ⬅ | ⬅ RELEASE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ➔ | ➔ RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
Term_Release_initiated_
by_the_terminating_user | TP_304_004 | Reference
section 12.2.1.1/
[IETF RFC 3261] | Selection expression | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------| +| Test purpose
BYE is sent with the From header set to value set in the last sent response | | | | +| Ensure that the IUT, once a dialogue has been established to release, it sends a BYE request with a From header set to the same value as in the To header of the last sent response. | | | | +| SIP header values
180:
To: any_180_to_value;tag=any_180_to_tag_value

BYE:
From: any_180_to_value;tag=any_180_to_tag_value | | | | + +| Message flow | | | +|--------------------------|-----------------------|--------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE | ← | On hook | +| 200 OK BYE | → | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | ← | ← RELEASE | +| 200 OK BYE | → | → RELEASE COMPLETE | + +| | | | | +|-----------------------------------------------------------|------------|-----------------------------------------------------|----------------------| +| TSS
Term_Release_initiated_
by_the_terminating_user | TP_304_005 | Reference
section 12.2.1.1 of
[IETF RFC 3261] | Selection expression | +|-----------------------------------------------------------|------------|-----------------------------------------------------|----------------------| + +###### Test purpose + +*Request line in the sent BYE is set to the value of the Contact header in the received request* + +Ensure that the IUT, once a dialogue has been established with an INVITE request including no Record-Route header set to release it, sends a BYE request with the Request-URI set to the Contact URI included in the original INVITE request and with no Route header set. + +###### SIP header values + +INVITE: + +Contact: + +BYE: + +BYE sip: any\_invite\_contact\_value SIP/2.0 + +| Message flow | | | +|--------------------------|-----------------------|--------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE | ← | On hook | +| 200 OK BYE | → | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | ← | ← RELEASE | +| 200 OK BYE | → | → RELEASE COMPLETE | + +| | | | | +|-------------------------------------------------------|------------|-----------------------------------------------------|----------------------| +| TSS
Term_Release_initiated_by_the_terminating_user | TP_304_006 | Reference
section 12.2.1.1 of
[IETF RFC 3261] | Selection expression | +|-------------------------------------------------------|------------|-----------------------------------------------------|----------------------| + +###### **Test purpose** + +*Request line in the sent BYE is set to the value of the Contact header in the received request* + +Ensure that the IUT, once a dialogue has been established with an INVITE request including a Record-Route header set to a list in which the last element does not contain a lr parameter to release the call, sends a BYE request with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the original INVITE request. + +###### **SIP header values** + +INVITE: + +Contact: +Record-Route: +Record-Route: + +BYE: + +BYE sip: any\_invite\_contact\_value SIP/2.0 +Route: +Route: + +###### **Message flow** + +**Test equipment** + +**End device** + +###### **Interworking POTS** + +| | | | +|---------------|---|----------| +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE | ← | On hook | +| 200 OK BYE | → | | + +###### **ISDN interworking** + +| | | | +|---------------|---|--------------------| +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | ← | ← RELEASE | +| 200 OK BYE | → | → RELEASE COMPLETE | + +| | | | | +|-------------------------------------------------------|------------|-----------------------------------------------------|----------------------| +| TSS
Term_Release_initiated_by_the_terminating_user | TP_304_007 | Reference
section 12.2.1.1 of
[IETF RFC 3261] | Selection expression | +|-------------------------------------------------------|------------|-----------------------------------------------------|----------------------| + +###### **Test purpose** + +*Request line in the sent BYE is set to the value of the Record-Route header in the received request* + +Ensure that the IUT, once a dialogue has been established with an INVITE request including a Record-Route header set to a list in which the last element contains a lr parameter to release the call, sends a BYE request with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| SIP header values
INVITE:
Contact:
Record-Route:
Record-Route:

BYE:
BYE sip: any_invite_value1 SIP/2.0
Route:
Route: | | | +| Message flow | | | +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE | ← | On hook | +| 200 OK BYE | → | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | ← | ← RELEASE | +| 200 OK BYE | → | → RELEASE COMPLETE | + +###### 7.2.3.3.2.1 Test purposes for ISDN + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------|----------------------| +| TSS
Term_Release_initiated_
by_the_terminating_user | TP_304_101 | Reference
sections 17.2.3.1, 13.3.1.4
and Figure 7 of
[IETF RFC 3261]
Subclause 5.1.2.5/
[ETSI TS 183 036] | Selection expression | +| Test purpose
Session terminated by the called party before an early dialogue is established | | | | +| Ensure that a final response is sent to the calling user equipment if a DSS1 RELEASE or RELEASE COMPLETE is received from the called user equipment before a Provisional response was sent to the calling user equipment. The Status code to be sent is determined by examining the Cause code value received in the RELEASE or RELEASE COMPLETE message as indicated in Table 7.2.3.3.2.2-1. | | | | +| SIP header values
Status code : SIP_final_response_VA | | | | +| DSS1 Parameter values
RELEASE:
Cause - Cause value
or
RELEASE COMPLETE:
Cause - Cause value | | | | + +| Message flow | | | +|-----------------------|-----------------------|--------------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 100 Trying | ← | | +| CASE A | | | +| SIP_final_response_VA | ← | ← RELEASE | +| ACK | → | → RELEASE COMPLETE | +| CASE B | | | +| SIP_final_response_VA | ← | ← RELEASE COMPLETE | +| ACK | → | | + +| | | | | +|-------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------|----------------------| +| TSS
Term_Release_initiated_by_the_terminating_user | TP_304_102 | Reference sections 17.2.3.1, 13.3.1.4 and Figure 7 of [IETF RFC 3261]
Subclause 5.1.2.5 of [ETSI TS 183 036] | Selection expression | +|-------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------|----------------------| + +**Test purpose** +*Session terminated by the called party after an early dialogue (183) is established* + +Ensure that a final response is sent to the calling user equipment if a DSS1 RELEASE or RELEASE COMPLETE is received from the called user equipment after a 183 Session Progress provisional response was sent to the calling user equipment. The Status code to be sent is determined by examining the Cause code value received in the RELEASE or RELEASE COMPLETE message as indicated in Table 7.2.3.3.2.2-2. + +**SIP header values** + Status code + +**DSS1 Parameter values** + RELEASE: + Cause - Cause value + or + RELEASE COMPLETE: + Cause - Cause value + +| Message flow | | | +|-----------------------|-----------------------|------------------------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 183 Session Progress | ← | ← CALL PROCEEDING / PROGRESS | +| CASE A | | | +| SIP_final_response_VA | ← | ← RELEASE | +| ACK | → | → RELEASE COMPLETE | +| CASE B | | | +| SIP_final_response_VA | ← | ← RELEASE COMPLETE | +| ACK | → | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------|--|-----------------------|--|-------------------|--------|---|---|-------|------------|---|---|----------|-------------------|--|--|--|-----------------------|---|---|---------|-----|---|---|------------------|-------------------|--|--|--|-----------------------|---|---|------------------|-----|---|--|--| +| TSS
Term_Release_initiated_
by_the_terminating_user | TP_304_103 | Reference
sections 17.2.3.1, 13.3.1.4
and Figure 7 of
[IETF RFC 3261]
Subclause 5.1.2.5 of
[ETSI TS 183 036] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
Session terminated by the called party before an early dialogue is established

Ensure that a final response is sent to the calling user equipment if a DSS1 RELEASE or RELEASE COMPLETE is received from the called user equipment before a provisional response was sent to the calling user equipment. The Status code to be sent is determined by examining the Cause code value received in the RELEASE or RELEASE COMPLETE message as indicated in Table 7.2.3.3.2.2-2.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
Status code

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
RELEASE:
    Cause - Cause value
or
RELEASE COMPLETE:
    Cause - Cause value

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
100 Trying ⬅ ⬅ ALERTING

CASE A
SIP_final_response_VA ⬅ ⬅ RELEASE
ACK ➔ ➔ RELEASE COMPLETE

CASE B
SIP_final_response_VA ⬅ ⬅ RELEASE COMPLETE
ACK ➔
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 100 Trying | ⬅ | ⬅ | ALERTING |
CASE A | | | | SIP_final_response_VA | ⬅ | ⬅ | RELEASE | ACK | ➔ | ➔ | RELEASE COMPLETE |
CASE B | | | | SIP_final_response_VA | ⬅ | ⬅ | RELEASE COMPLETE | ACK | ➔ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 100 Trying | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP_final_response_VA | ⬅ | ⬅ | RELEASE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ | RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP_final_response_VA | ⬅ | ⬅ | RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.3.3.2.2-1 – Interworking of release causes to SIP status codes** + +| | ←SIP final response | ← DISCONNECT, RELEASE, RELEASE COMPLETE | +|-----------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| SIP_final_response_VA | Status code | Cause value | +| VA_01 | 404 Not Found | Cause value No. 1 (unallocated (unassigned) number) | +| VA_02 | 486 Busy Here | Cause value No. 17 (user busy) | +| VA_03 | 480 Temporarily unavailable | Cause value No 18 (no user responding) | +| VA_04 | 480 Temporarily unavailable | Cause value No 19 (no answer from the user) | +| VA_05 | 480 Temporarily unavailable | Cause value No. 20 (subscriber absent) | +| VA_06 | 603 Decline | Cause value No 21 (call rejected) | +| VA_07 | 502 Bad Gateway | Cause value No 27 (destination out of order) | +| VA_08 | 484 Address Incomplete | Cause value No. 28 invalid number format (address incomplete) | +| VA_09 | 501 (Not Implemented) | Cause value No 29 (facility rejected) | +| VA_10 | 480 Temporarily unavailable | Cause value No 31 (normal unspecified) (class default) (Note 1) | +| VA_11 | 486 Busy here if CCBS-T-
Available invoke component
is present)
else 503 Service Unavailable | Cause value in the Class 010 (resource unavailable, Cause value No 34) | +| VA_12 | 500 Server Internal error | Cause value No 38 (Network out of order) | +| VA_13 | 503 Service Unavailable | Cause value No 41 (Temporary failure) | +| VA_14 | 500 Server Internal error | Cause value No 43 (Access information discarded) | +| VA_15 | 503 Service Unavailable | Cause value No 44 (Requested channel not available) | +| VA_16 | 500 Server Internal error | Cause value No 46 (Precedence call blocked) | +| VA_17 | 503 Service Unavailable | Cause value No 47 (Resource unavailable, unspecified) (class default) | +| VA_18 | 488 Not acceptable here | Cause value No 50 (requested facility no subscribed) | +| VA_19 | 603 Decline | Cause value No 57 (bearer capability not authorised) | +| VA_20 | 503 Service Unavailable | Cause value No 58 (bearer capability not presently) | +| VA_21 | 501 (Not Implemented) | Cause value No 63 (service option not available, unspecified) (class default) | +| VA_22 | 500 Server Internal error | Cause value No 65 (Bearer capability not implemented) | +| VA_23 | 501 Not Implemented | Cause value No 69 (Requested facility not implemented) | +| VA_24 | 501 Not Implemented | Cause value No 70 (Only restricted digital information capability is available) | +| VA_25 | 501 Not Implemented | Cause value No 79 (Service or option not implemented,unspecified) (class default) | +| VA_26 | 606 Not Acceptable | Cause value No 88 (incompatible destination) | +| VA_27 | 513 Message too large | Cause value No 95 (invalid message) (class default) | +| VA_28 | 480 Temporarily unavailable | Cause value No. 102 (recovery on timer expiry) | +| VA_29 | 501 Not Implemented | Cause value No 110 (Message with unrecognised Parameter, discarded) | +| VA_30 | 400 Bad Request | Cause value No. 111 (protocol error, unspecified) (class default) | +| VA_31 | 500 Server Internal error | Cause value No. 127 (interworking unspecified) (class default) | + +**Table 7.2.3.3.2.2-2 – Interworking of Release causes to SIP status codes** + +| | ←SIP final response | ← DISCONNECT, RELEASE, RELEASE COMPLETE | +|-----------------------|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| SIP_final_response_VA | Status code | Cause value | +| VA_01 | 486 Busy Here | Cause value No. 17 (user busy) | +| VA_02 | 480 Temporarily unavailable | Cause value No 18 (no user responding) | +| VA_03 | 603 Decline | Cause value No 21 (call rejected), Location = 000 / user (U) | +| VA_04 | 502 Bad Gateway | Cause value No 27 (destination out of order) | +| VA_05 | 484 Address Incomplete | Cause value No. 28 invalid number format (address incomplete) | +| VA_06 | 480 Temporarily unavailable | Cause value No 31 (normal unspecified) (class default) (Note 1) | +| VA_07 | 486 Busy here if CCBS-T-
Available invoke component
is present)
else 503 Service Unavailable | Cause value in the Class 010 (resource unavailable, Cause value No 34) | +| VA_08 | 503 Service Unavailable | Cause value No 41 (Temporary failure) | +| VA_09 | 500 Server Internal error | Cause value No 43 (Access information discarded) | +| VA_10 | 503 Service Unavailable | Cause value No 47 (Resource unavailable, unspecified) (class default) | +| VA_11 | 501 (Not Implemented) | Cause value No 63 (service option not available, unspecified) (class default) | +| VA_12 | 606 Not Acceptable | Cause value No 88 (incompatible destination) | +| VA_13 | 500 Server Internal error | Cause value No. 127 (interworking unspecified) (class default) | + +#### 7.2.3.4 Timers + +| TSS
Term_Timers | TP_305_001 | Reference
section 17.2.1 and Annex A
of [IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------|--------------------------------------|------------|--|----------------|--|--------------------------|--|--|--|--------|---|---------|--|-------------|---|--|--|---------------|---|---------------|---------|---------------|---|-----------------|--|-----|---|--|--| +| Test purpose
Timeout timer G 200 OK is repeated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that if an unreliable transport is used, the IUT, when an INVITE server transaction is in the Completed state repeats its response on the timeout condition of timer G set with a value of T1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
End deviceTest equipment
Interworking POTS
INVITE→Ringing
180 Ringing←
200 OK INVITE←Start timer GOn hook
200 OK INVITE←Timeout timer G
ACK→
| | | | End device | | Test equipment | | Interworking POTS | | | | INVITE | → | Ringing | | 180 Ringing | ← | | | 200 OK INVITE | ← | Start timer G | On hook | 200 OK INVITE | ← | Timeout timer G | | ACK | → | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Start timer G | On hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Timeout timer G | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|--------------------------------|-------------------|------------| +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← Start timer G | ← CONNECT | +| 200 OK INVITE | ← Timeout timer G | | +| ACK | → | | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|---------------|------------------------------------|---------|-----|---|--|--------------------------|--|--|--------|---|---------|-------------|---|------------|---------------|------------------------------------|-----------|-----|---|--|--------------------------------|--|--| +| TSS
Term_Timers | TP_305_002 | Reference
section 17.2.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Timeout timer G 200 OK is not repeated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that if a reliable transport (TCP) is used, the IUT, when an INVITE server transaction is in the Completed state does not repeat its response on the timeout condition of timer G set with a value of T1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
End device Test equipment
Interworking POTS
INVITE→Ringing
180 Ringing←
200 OK INVITE← Start timer G
Timeout timer G
On hook
ACK→
ISDN interworking
INVITE→→ SETUP
180 Ringing←← ALERTING
200 OK INVITE← Start timer G
Timeout timer G
← CONNECT
ACK→
Apply post test routine
| | | | | End device | Test equipment | Interworking POTS | | | INVITE | → | Ringing | 180 Ringing | ← | | 200 OK INVITE | ← Start timer G
Timeout timer G | On hook | ACK | → | | ISDN interworking | | | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | 200 OK INVITE | ← Start timer G
Timeout timer G | ← CONNECT | ACK | → | | Apply post test routine | | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← Start timer G
Timeout timer G | On hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← Start timer G
Timeout timer G | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------|--------------------------------------| +| TSS
Term_Timers | TP_305_003 | Reference
section 17.2.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +| Test purpose | | | | +| Timer G is started 2 time | | | | +| Ensure that if an unreliable transport is used, the IUT, when an INVITE server transaction is in the Completed state and having already sent its response twice, repeats it after timer G set MIN(2*T1,T2) value expires. | | | | +| SIP header values | | | | + +| Message flow | | | +|--------------------------------|------------------------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← Start timer G | On hook | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | +| ACK | → | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← Start timer G | ← CONNECT | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | +| ACK | → | | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------|--------------------------------------| +| TSS
Term_Timers | TP_305_004 | Reference
section 17.2.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +| Test purpose | | | | +| Timer G is started 3 time | | | | +| Ensure that if an unreliable transport is used, the IUT, when an INVITE server transaction is in the Completed state and having already sent its response three times, repeats it after timer G set the MIN(4*T1,T2) value expires. | | | | +| SIP header values | | | | +| Message flow | | | | +| | End device | | Test equipment | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| 180 Ringing | ← | | | +| 200 OK INVITE | ← Start timer G | | On hook | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | | +| ACK | → | | | + +| | | | +|--------------------------------|------------------------------------|------------| +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← Start timer G | ← CONNECT | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | +| 200 OK INVITE | ← Timeout timer G
Start timer G | | +| 200 OK INVITE | ← Timeout timer G | | +| ACK | → | | +| Apply post test routine | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------|-----------------------| +| TSS
Term_Timers | TP_305_005 | Reference
section 17.2.1 and
Annex A of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| Timeout timer H an ACK is sent | | | | +| Ensure that the IUT, when an INVITE server transaction is in the Completed state, it enters the Terminated state after the timer H, which is set to value 64*T1, expires. | | | | +| SIP header values | | | | +| Message flow | | | | +| | End device | | Test equipment | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| 180 Ringing | ← | | | +| 200 OK INVITE | ← Start timer H
Timeout timer H | | On hook | +| ACK | → | | | +| 481 Call/Transaction does Not Exist | | | | +| ISDN interworking | | | | +| INVITE | → | → SETUP | | +| 180 Ringing | ← | ← ALERTING | | +| 200 OK INVITE | ← Start timer H
Timeout timer H | ← CONNECT | | +| ACK | → | | | +| 481 Call/Transaction does Not Exist | ← | → DISCONNECT
← RELEASE
→ RELEASE COMPLETE | | + +| | | | | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| +| TSS
Term_Timers | TP_305_006 | Reference
section 17.2.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| + +##### **Test purpose** + +*Timeout timer H an ACK is sent* + +Ensure that the IUT, when an INVITE server transaction is in the Completed state, does not repeat its response after timer H, which is set to 64\*T1, expires. + +###### **SIP header values** + +###### **Message flow** + +**End device** + +**Test equipment** + +###### **Interworking POTS** + +| | | | | +|-------------------------------------|---|-----------------|---------| +| INVITE | → | | Ringing | +| 180 Ringing | ← | | | +| 200 OK INVITE | ← | Start timer H | On hook | +| 200 OK INVITE | ← | | | +| | | Timeout timer H | | +| ACK | → | | | +| 481 Call/Transaction does Not Exist | ← | | | + +###### **ISDN interworking** + +| | | | | +|-------------------------------------|---|-----------------|--------------------| +| INVITE | → | | → SETUP | +| 180 Ringing | ← | | ← ALERTING | +| 200 OK INVITE | ← | Start timer H | ← CONNECT | +| 200 OK INVITE | ← | | | +| | | Timeout timer H | | +| ACK | → | | → DISCONNECT | +| 481 Call/Transaction does Not Exist | ← | | ← RELEASE | +| | | | → RELEASE COMPLETE | + +| | | | | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| +| TSS
Term_Timers | TP_305_007 | Reference
section 17.2.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| + +###### **Test purpose** + +*Timeout timer I an ACK is sent* + +Ensure that the IUT, when the IUT, when an INVITE server transaction is in the Confirmed state, enters in the Terminated state after timer I set to T4 value expires + +###### **SIP header values** + +| Message flow | | | +|-------------------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | On hook | +| ACK | → Start timer I | | +| | Timeout timer I | | +| ACK | → | | +| 481 Call/Transaction does Not Exist | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → Start timer I | | +| | Timeout timer I | | +| ACK | → | | +| 481 Call/Transaction does Not Exist | ← | → DISCONNECT | +| | | ← RELEASE | +| | | → RELEASE COMPLETE | + +| | | | | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| +| TSS
Term_Timers | TP_305_008 | Reference
section 17.2.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Timeout timer I an ACK is sent | +| Ensure that the IUT, when an INVITE server transaction is in the Confirmed state, enters immediately in the Terminated state. | + +| | +|--------------------------| +| SIP header values | +|--------------------------| + +| Message flow | | | +|-------------------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | On hook | +| ACK | → Start timer I | | +| | Timeout timer I | | +| ACK | → | | +| 481 Call/Transaction does Not Exist | ← | | + +| | | | +|-------------------------------------|---|--------------------| +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | Start timer I | +| | | Timeout timer I | +| ACK | → | | +| 481 Call/Transaction does Not Exist | ← | → DISCONNECT | +| | | ← RELEASE | +| | | → RELEASE COMPLETE | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------|-----------------------| +| TSS
Term_Timers | TP_305_009 | Reference
section 13.3.1.4 and
Annex A of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| 200 OK INVITE received Timer T1 is started | | | | +| Ensure that the IUT, when it has answered to an INVITE request with 2XX response, repeats it after T1 duration expires without receiving an ACK request. | | | | +| SIP header values | | | | +| Message flow | | | | +| | End device | | Test equipment | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| 180 Ringing | ← | | | +| 200 OK INVITE | ← | Start timer T1 | On hook | +| 200 OK INVITE | ← | Timeout timer T1 | | +| ACK | → | | | +| Apply post test routine | | | | +| ISDN interworking | | | | +| INVITE | → | | → SETUP | +| 180 Ringing | ← | | ← ALERTING | +| 200 OK INVITE | ← | Start timer T1 | ← CONNECT | +| 200 OK INVITE | ← | Timeout timer T1 | | +| ACK | → | | | +| Apply post test routine | | | | + +| TSS
Term_Timers | TP_305_010 | Reference
section 13.3.1.4 and
Annex A of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|--------|---|--|---------|-------------|---|--|--|---------------|---|----------------|---------|---------------|---|--------------------------------------|--|---------------|---|------------------|--|-----|---|--|--|--------------------------------|--|--|--|--------------------------|--|--|--|--------|---|--|---------|-------------|---|--|------------|---------------|---|----------------|-----------|---------------|---|--------------------------------------|--|---------------|---|------------------|--|-----|---|--|--|--------------------------------|--|--|--| +| Test purpose
200 OK INVITE received Timer T1 is started 2 time

Ensure that the IUT, when it has already answered twice to an INVITE request with a 2XX response, repeats it after 2*T1 duration expires without receiving an ACK request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Interworking POTS
INVITE ➔ Ringing
180 Ringing ←
200 OK INVITE ← Start timer T1 On hook
200 OK INVITE ← Timeout timer T1
Start timer 2*T1
200 OK INVITE ← Timeout timer T1
ACK ➔
Apply post test routine
ISDN interworking
INVITE ➔ ➔ SETUP
180 Ringing ← ← ALERTING
200 OK INVITE ← Start timer T1 ← CONNECT
200 OK INVITE ← Timeout timer T1
Start timer 2*T1
200 OK INVITE ← Timeout timer T1
ACK ➔
Apply post test routine
| | | | | End device | | Test equipment | Interworking POTS | | | | INVITE | ➔ | | Ringing | 180 Ringing | ← | | | 200 OK INVITE | ← | Start timer T1 | On hook | 200 OK INVITE | ← | Timeout timer T1
Start timer 2*T1 | | 200 OK INVITE | ← | Timeout timer T1 | | ACK | ➔ | | | Apply post test routine | | | | ISDN interworking | | | | INVITE | ➔ | | ➔ SETUP | 180 Ringing | ← | | ← ALERTING | 200 OK INVITE | ← | Start timer T1 | ← CONNECT | 200 OK INVITE | ← | Timeout timer T1
Start timer 2*T1 | | 200 OK INVITE | ← | Timeout timer T1 | | ACK | ➔ | | | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Start timer T1 | On hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Timeout timer T1
Start timer 2*T1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Timeout timer T1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Start timer T1 | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Timeout timer T1
Start timer 2*T1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | Timeout timer T1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------|----------------------| +| TSS
Term_Timers | TP_305_011 | Reference
section 13.3.1.4 and
Annex A of
[IETF RFC 3261] | Selection expression | +| Test purpose
Timer T1 was started 64 time

Ensure that the IUT, does not repeat its 2XX response to an INVITE request after 64*T1 duration expires without receiving an ACK request. | | | | +| SIP header values | | | | + +![](ba596ecf0bd3f3520b7b5c2c857a9ec3_img.jpg) + +| Message flow | | | +|--------------------------------|--------------------|----------------| +| | End device | Test equipment | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← Start timer T1 | On hook | +| 200 OK INVITE | ← Timeout timer T1 | | +| | Start timer 64*T1 | | +| | Timeout timer T1 | | +| Apply post test routine | | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← Start timer T1 | ← CONNECT | +| 200 OK INVITE | ← Timeout timer T1 | | +| | Start timer 64*T1 | | +| | Timeout timer T1 | | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------------------------------------------------------|----------------------| +| TSS
Term_Timers | TP_305_012 | Reference
section 13.3.1.4 and
Annex A of
[IETF RFC 3261] | Selection expression | +| Test purpose | | | | +| A BYE is sent after expiry 64*T1 | | | | +| Ensure that the IUT, when it has received no ACK to its 2XX responses during a duration of 64*T1 seconds, sends a BYE request. | | | | +| SIP header values | | | | +| Message flow | | | | +| | End device | | Test equipment | +| Interworking POTS | | | | +| INVITE | → | | Ringing | +| 180 Ringing | ← | | | +| 200 OK INVITE | ← Start timer T1 | | On hook | +| 200 OK INVITE | ← Timeout timer T1 | | | +| | Start timer 64*T1 | | | +| | Timeout timer T1 | | | +| BYE | ← | | → DISCONNECT | +| 200 OK BYE | → | | ← RELEASE | +| | | | → RELEASE COMPLETE | + +| | | | +|--------------------------|--------------------|--------------------| +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← Start timer T1 | ← CONNECT | +| 200 OK INVITE | ← Timeout timer T1 | | +| | Start timer 64*T1 | | +| | Timeout timer T1 | | +| BYE | ← | → DISCONNECT | +| 200 OK BYE | → | ← RELEASE | +| | | → RELEASE COMPLETE | + +| | | | | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| +| TSS
Term_Timers | TP_305_013 | Reference
section 17.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | +|--------------------|------------|------------------------------------------------------------------|--------------------------------------| + +**Test purpose** +*BYE is retransmitted after expiry of 64\*T1* + +Ensure that the IUT, when a BYE server transaction is in the Completed state, on receipt of the repetitions of the BYE request, retransmits its response until the timer J set to 64\*T1 expires. + +###### **SIP header values** + +| End device | | Test equipment | +|--------------------------|-----------------------|--------------------| +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | On hook | +| ACK | → | | +| BYE | → Start timer J 64*T1 | | +| 200 OK BYE | ← | | +| | Wait 31.5 sec | | +| BYE | → | | +| 200 OK BYE | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | → Start timer J 64*T1 | → DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | → RELEASE COMPLETE | +| BYE | → Wait 31.5 sec | | +| 200 OK BYE | ← | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------|--------------------------------------|---------------------|--|--|--|--|-------------------|--|-----------------------|--------------------------|--|--|--|--------|---|--|---------|-------------|---|--|--|---------------|---|--|---------|-----|---|--|--|---------|-------|-------------------------|--|------------|---|--|--|--|--|-----------------|--|-----|---|--|--|---------------|--|--|--|-------------------|--|--|--|-------------------------------------|---|--|--|------------------------------|--|--|--|--------|---|--|---------|-------------|---|--|------------|---------------|---|--|-----------|-----|---|--|--|---------|-------|-------------------------|--------------|------------|---|--|-----------|--|--|-----------------|--------------------|-----|---|--|--|---------------|--|--|--|-------------------|--|--|--|-------------------------------------|---|--|--| +| TSS
Term_Timers | TP_305_014 | Reference
section 17.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Timeout timer J

Ensure that the IUT, when a BYE server transaction is in the Completed state, on receipt of the repetitions of the BYE request, retransmits its response until the timer J set to 64*T1 expires. After expiry of timer J the 200 OK response is not retransmitted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Message flow
End device Test equipment
Interworking POTS
INVITE → Ringing
180 Ringing ←
200 OK INVITE ← On hook
ACK →

BYE

→

Start timer J 64*T1
200 OK BYE ←
Timeout timer J
BYE →
Case A

CASE B
481 Call/Transaction does Not Exist ←

ISDN interworking
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK INVITE ← ← CONNECT
ACK →

BYE

→

Start timer J 64*T1
→ DISCONNECT
200 OK BYE ← ← RELEASE
Timeout timer J → RELEASE COMPLETE
BYE →
Case A

CASE B
481 Call/Transaction does Not Exist ←
| | | | Message flow | | | | | End device | | Test equipment | Interworking POTS | | | | INVITE | → | | Ringing | 180 Ringing | ← | | | 200 OK INVITE | ← | | On hook | ACK | → | | |
BYE |
→ |
Start timer J 64*T1 | | 200 OK BYE | ← | | | | | Timeout timer J | | BYE | → | | | Case A | | | |
CASE B | | | | 481 Call/Transaction does Not Exist | ← | | |
ISDN interworking | | | | INVITE | → | | → SETUP | 180 Ringing | ← | | ← ALERTING | 200 OK INVITE | ← | | ← CONNECT | ACK | → | | |
BYE |
→ |
Start timer J 64*T1 | → DISCONNECT | 200 OK BYE | ← | | ← RELEASE | | | Timeout timer J | → RELEASE COMPLETE | BYE | → | | | Case A | | | |
CASE B | | | | 481 Call/Transaction does Not Exist | ← | | | +| Message flow | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | | On hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
BYE |
→ |
Start timer J 64*T1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Timeout timer J | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Case A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 481 Call/Transaction does Not Exist | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
BYE |
→ |
Start timer J 64*T1 | → DISCONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | | ← RELEASE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Timeout timer J | → RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Case A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 481 Call/Transaction does Not Exist | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.3.5 Abnormal situations + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|--|----------------------------|---|--|-----|---|--|------------------------------|--|--|--------|---|--|----------------------------|---|--|-----|---|--| +| TSS
Term_Abnormal_situations | TP_306_001 | Reference
section 8.2.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
A call setup is rejected due to an unknown URI scheme | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT on receipt of an INVITE request with a Request-URI set with a scheme that it does not support, sends an Unsupported URI scheme (416 Unsupported URI scheme) response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
INVITE got: SIP/2.0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔
416 Unsupported URI scheme ⬅
ACK ➔

ISDN interworking
INVITE ➔
416 Unsupported URI scheme ⬅
ACK ➔
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | | 416 Unsupported URI scheme | ⬅ | | ACK | ➔ | |
ISDN interworking | | | INVITE | ➔ | | 416 Unsupported URI scheme | ⬅ | | ACK | ➔ | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 416 Unsupported URI scheme | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 416 Unsupported URI scheme | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|--|---------------|---|--|-----|---|--|------------------------------|--|--|--------|---|--|---------------|---|--|-----|---|--| +| TSS
Term_Abnormal_situations | TP_306_002 | Reference
section 8.2.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
A call setup is rejected due to an unknown destination user address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT on receipt of an INVITE request with a Request-URI set with an address that it does not accept, sends a Not Found (404 Not Found) response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
INVITE sip: SIP/2.0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔
404 Not Found ⬅
ACK ➔

ISDN interworking
INVITE ➔
404 Not Found ⬅
ACK ➔
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | | 404 Not Found | ⬅ | | ACK | ➔ | |
ISDN interworking | | | INVITE | ➔ | | 404 Not Found | ⬅ | | ACK | ➔ | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 404 Not Found | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 404 Not Found | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------|-----------------------|--|-------------------|--------------------------|--|--|--------|---|--|------------------------|---|--|-----|---|--|------------------------------|--|--|--------|---|--|------------------------|---|--|-----|---|--| +| TSS
Term_Abnormal_situations | TP_306_003 | Reference
section 13.3.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
A call setup is rejected due to an Expires header set to 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT on receipt of an INVITE request including an Expires header set to 0, sends a Request Terminated (487 Request Terminated) response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Expires: 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔
487 Request Terminated ⬅
ACK ➔

ISDN interworking
INVITE ➔
487 Request Terminated ⬅
ACK ➔
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | ➔ | | 487 Request Terminated | ⬅ | | ACK | ➔ | |
ISDN interworking | | | INVITE | ➔ | | 487 Request Terminated | ⬅ | | ACK | ➔ | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_004 | Reference
sections 8.2.3, 13.2.1,
13.3.1 and 20.11 of
[IETF RFC 3261] | Selection expression | +| Test purpose
A call setup is rejected due to a Content-Disposition header handling parameter empty | | | | +| Ensure that the IUT on receipt of an INVITE request including a Content-Language header value that it cannot understand, a Content-Disposition header including a handling empty sends an Unsupported Media Type (415 Unsupported Media Type) response with an Accept header that lists the types of all bodies it understands. | | | | +| SIP header values
INVITE
Content-Language: by
Content-Disposition: session | | | | +| 415:
Accept:
Accept-Language: | | | | + +| Message flow | | +|--------------------------------|-------------------| +| Test equipment | End device | +| Interworking POTS | | +| INVITE | → | +| 415 Unsupported Media Type | ← | +| ACK | → | +| ISDN interworking | | +| INVITE | → | +| 415 Unsupported Media Type | ← | +| ACK | → | +| Apply post test routine | | + +| | | | | +|---------------------------------|------------|--------------------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_005 | Reference sections 8.2.3, 21.4.13, 13.2.1, 13.3.1 and 20.11 of [IETF RFC 3261] | Selection expression | +|---------------------------------|------------|--------------------------------------------------------------------------------|----------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

A call setup is rejected due to a Content-Disposition handlingparameter set to required

Ensure that the IUT on receipt of an INVITE request including a Content-Language header value that it cannot understand, a Content-Disposition with a handling set to "required" and a disposition-types set to session, sends an Unsupported Media Type (415 Unsupported Media Type) response with an Accept header that lists the types of all bodies it understands.

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

SIP header values

INVITE
          Content-Language: by
          Content-Disposition: session;handling= required

415:
          Accept:
          Accept-Language:

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | +|--------------------------------|-------------------| +| Test equipment | End device | +| Interworking POTS | | +| INVITE | → | +| 415 Unsupported Media Type | ← | +| ACK | → | +| ISDN interworking | | +| INVITE | → | +| 415 Unsupported Media Type | ← | +| ACK | → | +| Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------|-----------------------|--|-------------------|--------------------------|--|--|--------|---|--|----------------------------|---|--|-----|---|--|------------------------------|--|--|--------|---|--|----------------------------|---|--|-----|---|--|--------------------------------|--|--| +| TSS
Term_Abnormal_situations | TP_306_006 | Reference
sections 8.2.3, 21.4.13,
13.2.1, 13.3.1 and 20.11 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Initial offer not supported, rejected with 415 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT on receipt of an INVITE request including a Content-Encoding header set to content-coding values that it does not support, sends an Unsupported Media Type (415 Unsupported Media Type) response with an Accept-Encoding header that list the types of coding that it understands. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Content-Encoding: unsupported

415:
Accept-Encoding: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔
415 Unsupported Media Type ⬅
ACK ➔

ISDN interworking
INVITE ➔
415 Unsupported Media Type ⬅
ACK ➔
Apply post test routine
| | | | Test equipment | | End device | Interworking POTS | | | INVITE | ➔ | | 415 Unsupported Media Type | ⬅ | | ACK | ➔ | |
ISDN interworking | | | INVITE | ➔ | | 415 Unsupported Media Type | ⬅ | | ACK | ➔ | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 415 Unsupported Media Type | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 415 Unsupported Media Type | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_007 | Reference
section 13.2.1 and 13.3 of
[IETF RFC 3261] | Selection expression | +| Test purpose
Initial offer not set to session, initial offer sent in 200 OK | | | | +| Ensure that the IUT on receipt of an INVITE request including a message body with a Content-Disposition header not set to session value, includes in its first 2xx response an initial offer session description. | | | | +| SIP header values
INVITE
Content- Disposition: renter;handling=optional

200 OK:
SDP | | | | + +| Message flow | | | +|--------------------------|--------------------------------|-------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 200 OK INVITE | ← | On hook | +| ACK | → | | +| | Apply post test routine | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| | Apply post test routine | | + +| | | | | +|---------------------------------|------------|----------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_008 | Reference
sections 13.2.1, 13.3.1 and
20.11 of [IETF RFC 3261] | Selection expression | +|---------------------------------|------------|----------------------------------------------------------------------|----------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

Content language not understood, initial offer in 200 OK INVITE

Ensure that the IUT on receipt of an INVITE request including a Content-Language header value that it cannot understand and a Content-Disposition header including a handling set to "optional", includes in its first 2xx response an initial offer session description.

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

SIP header values

INVITE

    Content-Language: unknown

    Content- Disposition: session;handling=optional

200 OK:

    SDP

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------|--------------------------------|-------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 200 OK INVITE | ← | On hook | +| ACK | → | | +| | Apply post test routine | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| | Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|--|-------------------------|---|--|-----|---|--|------------------------------|--|--|--------|---|--|-------------------------|---|--|-----|---|--| +| TSS
Term_Abnormal_situations | TP_306_009 | Reference
section 13.3.1.3 and
21.4.13 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SDP not acceptable, rejected with 488 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT on receipt of an INVITE request including a session description that it can understand but it cannot accept, a Content-Disposition with a handling set to "required" and a disposition-types set to session, sends a Not Acceptable Here (488 Not Acceptable Here) response including a Warning header. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Content- Disposition: session;handling=required
SDP not acceptable

488:
Warning: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE →
488 Not Acceptable Here ←
ACK →

ISDN interworking
INVITE →
488 Not Acceptable Here ←
ACK →
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | → | | 488 Not Acceptable Here | ← | | ACK | → | |
ISDN interworking | | | INVITE | → | | 488 Not Acceptable Here | ← | | ACK | → | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 488 Not Acceptable Here | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 488 Not Acceptable Here | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-----------------------------------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|---------------|---|---------|-----|---|--|--|---------------------------------|--|--|--------------------------------|--| +| TSS
Term_Abnormal_situations | TP_306_010 | Reference
sections 17.2.3, 8.2.2.3
and Figure 7 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Proxy-Require header with an unsupported option-tag in ACK | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT when a server INVITE transaction is in the Completed state, on receipt of an ACK request including a Proxy-Require header set with an option-tag that it does not support, enters in the Confirmed transaction state. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
ACK
Proxy-Require: unsupported | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE → Ringing
200 OK INVITE ← On hook
ACK →
Check confirmed dialogue
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | → | Ringing | 200 OK INVITE | ← | On hook | ACK | → | | | Check confirmed dialogue | | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | On hook | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | +| | Check confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|-------------------------------------------------------------------|---|-----------| +| ISDN interworking | | | +| INVITE | ➔ | ➔ SETUP | +| 200 OK INVITE | ⬅ | ⬅ CONNECT | +| ACK | ➔ | | +| Check confirmed dialogue
Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|---------------|---|---------|-----|---|--|-------------------------------------------------------------------|--|--|--------------------------|--|--|--------|---|---------|---------------|---|-----------|-----|---|--|-------------------------------------------------------------------|--|--| +| TSS
Term_Abnormal_situations | TP_306_011 | Reference
section 17.2.3, 8.2.2.3 and Figure 7 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Require header with an unsupported option-tag in ACK

Ensure that the IUT when a server INVITE transaction is in the Completed state, on receipt of an ACK request including a Require header set with an option-tag that it does not support, enters in the Confirmed transaction state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
ACK
Require: unsupported | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE➔Ringing
200 OK INVITE⬅On hook
ACK➔
Check confirmed dialogue
Apply post test routine
ISDN interworking
INVITE➔➔ SETUP
200 OK INVITE⬅⬅ CONNECT
ACK➔
Check confirmed dialogue
Apply post test routine
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 200 OK INVITE | ⬅ | On hook | ACK | ➔ | | Check confirmed dialogue
Apply post test routine | | | ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 200 OK INVITE | ⬅ | ⬅ CONNECT | ACK | ➔ | | Check confirmed dialogue
Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | On hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Check confirmed dialogue
Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | ⬅ CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Check confirmed dialogue
Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_012 | Reference
section 17.2.1 and 17.2.3 of [IETF RFC 3261] | Selection expression | +| Test purpose
Additional identical INVITE received, the previous sent final response is repeated

Ensure that the IUT when a server INVITE transaction is in the Completed state, on receipt of an INVITE request, including a Via header set with the same branch parameter and sent-by value in the topmost list value, repeat its last response. | | | | + +###### **SIP header values** + +###### INVITE1: + +Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### INVITE2: + +Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### **Message flow** + +**Test equipment** + +**End device** + +###### **Interworking POTS** + +| | | | +|--------------------|---|---------| +| INVITE1 | → | Ringing | +| 3xx – 6xx response | ← | | +| INVITE2 | → | | +| 3xx – 6xx response | ← | | +| ACK | → | | + +###### **ISDN interworking** + +| | | | | +|--------------------|---|---|------------------| +| INVITE1 | → | → | SETUP | +| 3xx – 6xx response | ← | ← | RELEASE_COMPLETE | +| INVITE2 | → | | | +| 3xx – 6xx response | ← | | | +| ACK | → | | | + +| | | | | +|---------------------------------|------------|--------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_013 | Reference
section 17.2.1 and 17.2.3
of [IETF RFC 3261] | Selection expression | +|---------------------------------|------------|--------------------------------------------------------------|----------------------| + +###### **Test purpose** + +*Additional identical INVITE and Via header without branch parameter received, the previous sent final response is repeated* + +Ensure that the IUT when a server INVITE transaction is in the Completed state, on receipt of an INVITE request, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via identical as in the first INVITE request, repeat its last response. + +**SIP header values** + +INVITE1: + Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +INVITE2: + Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + Via: *any\_invite2\_via\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +![](9707839366bb5cf01a4a5b4abd8c1264_img.jpg) + +**Message flow** + +| | Test equipment | | End device | +|--------------------------|-----------------------|---|-------------------| +| Interworking POTS | | | | +| INVITE1 | → | | Ringing | +| 3xx – 6xx response | ← | | | +| INVITE2 | → | | | +| 3xx – 6xx response | ← | | | +| ACK | → | | | +| ISDN interworking | | | | +| INVITE2 | → | → | SETUP | +| 3xx – 6xx response | ← | ← | RELEASE_COMPLETE | +| INVITE2 | → | | | +| 3xx – 6xx response | ← | | | +| ACK | → | | | + +| | | | | +|---------------------------------|------------|--------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_014 | Reference
section 17.2.1 and 17.2.3
of [IETF RFC 3261] | Selection expression | +|---------------------------------|------------|--------------------------------------------------------------|----------------------| + +**Test purpose** +*Additional identical INVITE and Via header without magic cookie in the branch parameter received, the previous sent final response is repeated* + +Ensure that the IUT when a server INVITE transaction is in the Completed state, on receipt of an INVITE request, including a Via header set with a branch parameter without the magic cookie "z9hG4bK" but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via identical as in the first INVITE request, repeat its last response. + +###### **SIP header values** + +Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### INVITE2: + +Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + Via: *any\_invite1\_via\_value*;branch=*any\_invite2\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### **Message flow** + +**Test equipment** + +**End device** + +###### **Interworking POTS** + +| | | | +|--------------------|---|---------| +| INVITE1 | → | Ringing | +| 3xx – 6xx response | ← | | +| INVITE2 | → | | +| 3xx – 6xx response | ← | | +| ACK | → | | + +###### **ISDN interworking** + +| | | | | +|--------------------|---|---|------------------| +| INVITE2 | → | → | SETUP | +| 3xx – 6xx response | ← | ← | RELEASE_COMPLETE | +| INVITE2 | → | | | +| 3xx – 6xx response | ← | | | +| ACK | → | | | + +| | | | | +|---------------------------------|------------|---------------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_015 | Reference
sections 8.2.2.2, 17.2.1
and 17.2.3 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|---------------------------------------------------------------------------|----------------------| + +###### **Test purpose** + +*Additional identical INVITE and Via header branch parameter different from the previous request 482 is sent* + +Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of an INVITE request, including a Via header set with a different branch parameter starting with the magic cookie "z9hG4bK" but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the first INVITE request, sends a Loop Detected (482 Loop Detected) response. + +**SIP header values** + +INVITE1: + Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +INVITE2: + Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite2\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +![](650ab7a23f57431810f5fa1598e10d91_img.jpg) + +**Message flow** + +| | Test equipment | | End device | +|--------------------------------|-----------------------|---|-------------------| +| Interworking POTS | | | | +| INVITE1 | → | | Ringing | +| 180 Ringing | ← | | | +| INVITE2 | → | | | +| 482 Loop Detected | ← | | | +| ACK | → | | | +| Apply post test routine | | | | +| ISDN interworking | | | | +| INVITE1 | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| INVITE2 | → | | | +| 482 Loop Detected | ← | → | RELEASE | +| ACK | → | ← | RELEASE_COMPLETE | + +| | | | | +|---------------------------------|------------|---------------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_016 | Reference
sections 8.2.2.2, 17.2.1
and 17.2.3 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|---------------------------------------------------------------------------|----------------------| + +**Test purpose** + +*Additional identical INVITE and Via header sent-by value different from the previous request 482 is sent* + +Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of an INVITE request, including a Via header set to an identical branch parameter starting with the magic cookie "z9hG4bK" and a different sent-by value, but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the first INVITE request, sends a Loop Detected (482 Loop Detected) response. + +###### **SIP header values** + +###### INVITE1: + +Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### INVITE2: + +Via: *any\_invite2\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### **Message flow** + +**Test equipment** + +**End device** + +###### **Interworking POTS** + +| | | | +|-------------------|---|---------| +| INVITE1 | → | Ringing | +| 180 Ringing | ← | | +| INVITE2 | → | | +| 482 Loop Detected | ← | | +| ACK | → | | + +###### **ISDN interworking** + +| | | | | +|-------------------|---|---|------------------| +| INVITE1 | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| INVITE2 | → | | | +| 482 Loop Detected | ← | → | RELEASE | +| ACK | → | ← | RELEASE_COMPLETE | + +| | | | | +|---------------------------------|------------|---------------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_017 | Reference
sections 8.2.2.2, 17.2.1
and 17.2.3 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|---------------------------------------------------------------------------|----------------------| + +###### **Test purpose** + +*Additional identical INVITE and Via header different from the previous request 482 is sent* + +Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of an INVITE request, including a top Via header set to a different value but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the first INVITE request, sends a Loop Detected (482 Loop Detected) response. + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------------------| +| SIP header values
INVITE1:
Via: any_invite1_via_value;branch=z9hG4bK any_invite1_branch_value
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq

INVITE2:
Via: any_invite2_via_value;branch=z9hG4bK_any_invite2_branch_value
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value
Call-ID: any_invite1_call-id_value
CSeq: any_invite1_cseq | | | +| Message flow | | | +| Test equipment | | End device | +| Interworking POTS | | | +| INVITE | ➔ | Ringing | +| 180 Ringing | ⬅ | | +| INVITE2 | ➔ | | +| 482 Loop Detected | ⬅ | | +| ACK | ➔ | | +| ISDN interworking | | | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ ALERTING | +| INVITE2 | ➔ | | +| 482 Loop Detected | ⬅ | ➔ RELEASE | +| ACK | ➔ | ⬅ RELEASE_COMPLETE | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_018 | Reference
section 8.2.2.3 of
[IETF RFC 3261] | Selection expression | +| Test purpose
INVITE option value in the Supported header unknown a 420 is sent | | | | +| Ensure that the IUT, on receipt of an INVITE request with a Require header set to an option value that the IUT does not support, sends a Bad Extension (420 Bad Extension) response including those options in the Unsupported header. | | | | +| SIP header values
INVITE:
Require: unsupported

420:
Unsupported: unsupported | | | | + +| Message flow | | +|--------------------------|-------------------| +| Test equipment | End device | +| Interworking POTS | | +| INVITE | → | +| 420 Bad Extension | ← | +| ACK | → | +| ISDN interworking | | +| INVITE | → | +| 420 Bad Extension | ← | +| ACK | → | + +| TSS
Term_Abnormal_situations | TP_306_019 | Reference
section 8.2.2 and 15.1.2 of
[IETF RFC 3261] | Selection expression | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------| +| Test purpose
BYE option value in the Supported header unknown a 420 is sent

Ensure that the IUT, once a dialogue has been established, on receipt of a BYE request including a Require header set with an option-tag that it does not support, sends a Bad Extension (420 Bad Extension) response including an Unsupported set with this option-tag. | | | | +| SIP header values
BYE:
Require: unsupported

420:
Unsupported: unsupported | | | | +| Message flow | | End device | | +| Test equipment | | | | +| Interworking POTS | | | | +| INVITE | → | | | +| 180 Ringing | ← | Ringing | | +| 200 OK INVITE | ← | Off hook | | +| ACK | → | | | +| BYE | → | | | +| 420 Bad Extension | ← | | | +| ISDN interworking | | | | +| INVITE | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| 200 OK INVITE | ← | ← | CONNECT | +| ACK | → | | | +| BYE | → | | | +| 420 Bad Extension | ← | | | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|----------------------|--|-----------------------|-------------------|-----|---|--|-------------------------------------|---|--| +| TSS
Term_Abnormal_situations | TP_306_020 | Reference
section 15.1.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | +| Test purpose
BYE received no dialogue exist | | | | | | | | | | | | | +| Ensure that the IUT, while no dialogue has been established, on receipt of a BYE request, sends a Call/Transaction does not exist (481 Call/Transaction does not exist). | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | +| Message flow
Test equipment End device
BYE ➔
481 Call/Transaction does not exist ⬅
| | | | | Test equipment | End device | BYE | ➔ | | 481 Call/Transaction does not exist | ⬅ | | +| | Test equipment | End device | | | | | | | | | | | +| BYE | ➔ | | | | | | | | | | | | +| 481 Call/Transaction does not exist | ⬅ | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|---------------|---|----------|-----|---|--|-----|---|--|-------------------------------------|---|--|------------------------------|--|--|--------|---|---------|-------------|---|------------|---------------|---|-----------|-----|---|--|-----|---|--|-------------------------------------|---|--| +| TSS
Term_Abnormal_situations | TP_306_021 | Reference
section 15.1.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
BYE To header tag not received, 481 is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the IUT, while a dialogue has been established, on receipt of a BYE request without TAG in the To header, sends a Call/Transaction does not exist (481 Call/Transaction does not exist). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value

BYE:
From: any_invite1_from_value;tag=any_invite1_from_tag_value
To: any_invite1_to_value | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE ➔ Ringing
180 Ringing ⬅
200 OK INVITE ⬅ Off hook
ACK ➔
BYE ➔
481 Call/Transaction does not exist ⬅

ISDN interworking
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
200 OK INVITE ⬅ ⬅ CONNECT
ACK ➔
BYE ➔
481 Call/Transaction does not exist ⬅
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | ➔ | Ringing | 180 Ringing | ⬅ | | 200 OK INVITE | ⬅ | Off hook | ACK | ➔ | | BYE | ➔ | | 481 Call/Transaction does not exist | ⬅ | |
ISDN interworking | | | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING | 200 OK INVITE | ⬅ | ⬅ CONNECT | ACK | ➔ | | BYE | ➔ | | 481 Call/Transaction does not exist | ⬅ | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 481 Call/Transaction does not exist | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | ⬅ CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 481 Call/Transaction does not exist | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_022 | Reference
section 12.2.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
BYE CSeq value in BYE higher than in INVITE request

Ensure that the IUT, once a dialogue has been established, on receipt of a BYE request including a CSeq header set with a more than one higher value as in the previous request, sends a Success (200 OK) response with the same CSeq value.
SIP header values
INVITE1:
CSeq: any_invite1_cseq

BYE:
CSeq: any_invite1_cseq+x

200 OK BYE
CSeq: any_invite1_cseq+x | | | | + + + +| Test equipment | | End device | +|--------------------------|---|--------------------| +| Interworking POTS | | | +| INVITE | → | | +| 180 Ringing | ← | Ringing | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE | → | | +| 200 OK BYE | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | → | → DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | → RELEASE_COMPLETE | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_023 | Reference
section 9.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
CANCEL with different branch in the Via header received a 481 is sent

Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request including a Via header set with a different branch parameter starting with the magic cookie "z9hG4bK" but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the original INVITE request, sends a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) response. | | | | + +###### **SIP header values** + +###### INVITE1: + +Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### INVITE2: + +Via: *any\_invite2\_via\_value*;branch=z9hG4bK *any\_cancel\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### **Message flow** + +###### **Test equipment** + +###### **End device** + +###### **Interworking POTS** + +| | | | +|-----------------------------------------|---|---------| +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| CANCEL | → | | +| 481 Call Leg/Transaction Does Not Exist | ← | | + +###### **ISDN interworking** + +| | | | +|-----------------------------------------|---|------------| +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| CANCEL | → | | +| 481 Call Leg/Transaction Does Not Exist | ← | | + +| | | | | +|---------------------------------|------------|-----------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_024 | Reference
section 9.2 and 17.2.3 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|-----------------------------------------------------------|----------------------| + +###### **Test purpose** + +*CANCEL with different Via send-by value received a 481 is sent* + +Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request including a Via header set to an identical branch parameter starting with the magic cookie "z9hG4bK" and a different sent-by value, but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the original INVITE request, sends a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) response. + +###### **SIP header values** + +###### INVITE1: + +Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### INVITE2: + +Via: *any\_cancel\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +###### **Message flow** + +**Test equipment** + +**End device** + +###### **Interworking POTS** + +| | | | +|-----------------------------------------|---|---------| +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| CANCEL | → | | +| 481 Call Leg/Transaction Does Not Exist | ← | | + +###### **ISDN interworking** + +| | | | +|-----------------------------------------|---|------------| +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| CANCEL | → | | +| 481 Call Leg/Transaction Does Not Exist | ← | | + +| | | | | +|---------------------------------|------------|-----------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_025 | Reference
section 9.2 and 17.2.3 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|-----------------------------------------------------------|----------------------| + +###### **Test purpose** + +*CANCEL received with different Via header value a 481 is sent* + +Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request, including a top Via header set to a different value but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the original INVITE request, sends a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) response. + +**SIP header values** + +INVITE1: + Via: *any\_invite1\_via\_value*;branch=z9hG4bK *any\_invite1\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +INVITE2: + Via: *any\_cancel\_via\_value*;branch=z9hG4bK *any\_cancel\_branch\_value* + From: *any\_invite1\_from\_value*;tag=*any\_invite1\_from\_tag\_value* + To: *any\_invite1\_to\_value* + Call-ID: *any\_invite1\_call-id\_value* + CSeq: *any\_invite1\_cseq* + +![](ed0efcbe18c231dc77677b24288a5148_img.jpg) + +**Message flow** + +| | Test equipment | End device | +|-----------------------------------------|-----------------------|-------------------| +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| CANCEL | → | | +| 481 Call Leg/Transaction Does Not Exist | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| CANCEL | → | | +| 481 Call Leg/Transaction Does Not Exist | ← | | + +| | | | | +|---------------------------------|------------|------------------------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_026 | Reference
sections 17.2.3, 17.2.2,
12.2.1.1 and 15.1.2 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|------------------------------------------------------------------------------------|----------------------| + +**Test purpose** +*BYE received Via header with the same branch parameter after BYE was answered last response is repeated* + +Ensure that the IUT, having already answered to a BYE request, on receipt of a BYE request, before timer J fires, including a Via header set with the same branch parameter in the topmost list value, repeat its last response. + +**SIP header values** + +BYE1: + Via: *any\_bye1\_via\_value*;branch=z9hG4bK *any\_bye1\_branch\_value* + +BYE2: + Via: *any\_bye1\_via\_value*;branch=z9hG4bK *any\_bye1\_branch\_value* + +| Message flow | | | +|--------------------------|----------------|--------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | | +| 180 Ringing | ← | Ringing | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE1 | → | | +| 200 OK BYE | ← | | +| BYE2 | → | | +| 200 OK BYE | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE1 | → | → DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | → RELEASE_COMPLETE | +| BYE2 | → | | +| 200 OK BYE | ← | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_027 | Reference
sections 17.2.3, 17.2.2 and
15.1.2 of [IETF RFC
3261] | Selection expression | +| Test purpose
BYE received Via header without branch parameter after BYE was answered last response is repeated

Ensure that the IUT, having already answered to a BYE request, on receipt of a BYE request, before timer J fires, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the first BYE request, repeat its last response.
SIP header values
BYE1:
Via: any_bye1_via_value;branch=z9hG4bK any_bye1_branch_value

BYE2:
Via: any_bye1_via_value | | | | + +| Message flow | | | +|--------------------------|-----------------------|--------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | | +| 180 Ringing | ← | Ringing | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE1 | → | | +| 200 OK BYE | ← | | +| BYE2 | → | | +| 200 OK BYE | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE1 | → | → DISCONNECT | +| 200 OK BYE | ← | ← RELEASE | +| | | → RELEASE_COMPLETE | +| BYE2 | → | | +| 200 OK BYE | ← | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_028 | Reference
section 12.2.2 of
[IETF RFC 3261] | Selection expression | +| Test purpose
BYE CSeq value in BYE lower than in INVITE request

Ensure that the IUT on receipt of a BYE request with a CSeq number set to a lower value than in the preceding INVITE request, sends a 500 (Server Internal Error) response. | | | | +| SIP header values
INVITE:
CSeq: any_invite_cseq

BYE:
CSeq: any_invite1_cseq-1 | | | | + +| Message flow | | | +|---------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | | +| 180 Ringing | ← | Ringing | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| BYE | → | | +| 500 Server Internal Error | ← | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| BYE | → | | +| 500 Server Internal Error | ← | | + +| | | | | +|---------------------------------|------------|----------------------------------------------------|----------------------| +| TSS
Term_Abnormal_situations | TP_306_029 | Reference
section 8.2.2.3 of
[IETF RFC 3261] | Selection expression | +|---------------------------------|------------|----------------------------------------------------|----------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
CANCEL received Require header contains not supported value | +| Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request including a Require header set with an option-tag that it does not support, sends a Success (200 OK) response. | + +| | +|-----------------------------------------------------| +| SIP header values
Require: 100unsupported | +|-----------------------------------------------------| + +| Message flow | | | +|--------------------------|-----------------------|----------------------------| +| | Test equipment | End device | +| Interworking POTS | | | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| CANCEL | → | | +| 200 OK CANCEL | ← | | +| 487 Request Terminated | ← | | +| ACK | → | | +| ISDN interworking | | | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| CANCEL | → | → RELEASE/RELEASE COMPLETE | +| 200 OK CANCEL | ← | | +| 487 Request Terminated | ← | | +| ACK | → | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|----------------------|--|-----------------------|-------------------|--------------------------|--|--|--------|---|---------|-------------|---|--|--------|---|--|---------------|---|--|------------------------|---|--|-----|---|--|------------------------------|--|--|--------|---|---------|-------------|---|------------|--------|---|----------------------------|---------------|---|--|------------------------|---|--|-----|---|--| +| TSS
Term_Abnormal_situations | TP_306_030 | Reference
section 8.2.2.3 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
CANCEL received Proxy-Require header contains not supported value

Ensure that the IUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request including a Proxy-Require header set with an option-tag that it does not support, sends a Success (200 OK) response.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
Proxy-Require: 100unsupported | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE → Ringing
180 Ringing ←
CANCEL →
200 OK CANCEL ←
487 Request Terminated ←
ACK →

ISDN interworking
INVITE → → SETUP
180 Ringing ← ← ALERTING
CANCEL → → RELEASE/RELEASE COMPLETE
200 OK CANCEL ←
487 Request Terminated ←
ACK →
| | | | | Test equipment | End device | Interworking POTS | | | INVITE | → | Ringing | 180 Ringing | ← | | CANCEL | → | | 200 OK CANCEL | ← | | 487 Request Terminated | ← | | ACK | → | |
ISDN interworking | | | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | CANCEL | → | → RELEASE/RELEASE COMPLETE | 200 OK CANCEL | ← | | 487 Request Terminated | ← | | ACK | → | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CANCEL | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK CANCEL | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CANCEL | → | → RELEASE/RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK CANCEL | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 487 Request Terminated | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------|----------------------|--|-----------------------|-------------------|--------|---|--|-------------------------------------|---|--| +| TSS
Term_Abnormal_situations | TP_306_031 | Reference
section 9.2 and 15.1.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | +|

Test purpose
CANCEL received no dialogue exists

Ensure that the IUT while no session has been initiated, on receipt of a CANCEL request, sends a Call/transaction Does Not Exist (481 Call/transaction Does Not Exist) response.

| | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | +| Message flow
Test equipment End device
CANCEL →
481 Call/transaction Does Not Exist ←
| | | | | Test equipment | End device | CANCEL | → | | 481 Call/transaction Does Not Exist | ← | | +| | Test equipment | End device | | | | | | | | | | | +| CANCEL | → | | | | | | | | | | | | +| 481 Call/transaction Does Not Exist | ← | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|--------------------------|--|--|--|--------|---|--|--|-------------|---|--|---------|---------------|---|--|----------|-----|---|--|--|------|---|---------------|--|------------|---|--|--|--|--|-----------------|--|------|---|--|--|-------------------------------------|---|--|--|------------------------------|--|--|--|--------|---|--|---------|-------------|---|--|------------|---------------|---|--|-----------|-----|---|--|--|------|---|---------------|--------------|------------|---|--|-----------|--|--|-----------------|--------------------|------|---|--|--|-------------------------------------|---|--|--| +| TSS
Term_Abnormal_situations | TP_306_032 | Reference
section 15.1.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
BYE received after session is released

Ensure that the IUT, while a session has been released, on receipt of a BYE request, sends a Call/transaction Does Not Exist (481 Call/transaction Does Not Exist) response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP_CC_TE_CR_I_005 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Interworking POTS
INVITE →
180 Ringing ← Ringing
200 OK INVITE ← Off hook
ACK →
BYE1 → Start timer J
200 OK BYE ←
Timeout timer J
BYE2 →
481 Call/transaction Does Not Exist ←

ISDN interworking
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK INVITE ← ← CONNECT
ACK →
BYE1 → Start timer J → DISCONNECT
200 OK BYE ← ← RELEASE
Timeout timer J → RELEASE_COMPLETE
BYE2 →
481 Call/transaction Does Not Exist ←
| | | | | Test equipment | | End device | Interworking POTS | | | | INVITE | → | | | 180 Ringing | ← | | Ringing | 200 OK INVITE | ← | | Off hook | ACK | → | | | BYE1 | → | Start timer J | | 200 OK BYE | ← | | | | | Timeout timer J | | BYE2 | → | | | 481 Call/transaction Does Not Exist | ← | | |
ISDN interworking | | | | INVITE | → | | → SETUP | 180 Ringing | ← | | ← ALERTING | 200 OK INVITE | ← | | ← CONNECT | ACK | → | | | BYE1 | → | Start timer J | → DISCONNECT | 200 OK BYE | ← | | ← RELEASE | | | Timeout timer J | → RELEASE_COMPLETE | BYE2 | → | | | 481 Call/transaction Does Not Exist | ← | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE1 | → | Start timer J | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Timeout timer J | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 481 Call/transaction Does Not Exist | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE1 | → | Start timer J | → DISCONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ← | | ← RELEASE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Timeout timer J | → RELEASE_COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 481 Call/transaction Does Not Exist | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### 7.2.4 Emergency service + +| TSS
Emergency_service | TP_401_001 | Reference
subclause 5.1.6.8.4 of
[ETSI TS 124 229] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|----------------------|--|------------|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|------------------------------|--|--|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------| +|

Test purpose
Emergency session setup within a non-emergency registration

Ensure that the SUT in case of an emergency call and non-emergency registration sends an INVITE request that contains:

  • • a service URN in the Request-URI
  • • a To header field with the same emergency service URN as in the Request-URI
  • • a From header field that includes the public user identity or the tel URI associated with the public user identity
  • • if available to the SUT, and if defined for the access type, the SUT shall insert in the P-Access-Network-Info header field
  • • one P-Preferred-Identity header field that include the public user identity or the tel URI associated with the public user identity
  • • if the UE has its location information available, or a URI that points to the location information, then the UE shall include a Geolocation header field
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
INVITE
Request Line: urn:service:{sos/sos.ambulance/sos.animal-control/sos.fire/sos.marine/sos.mountain/sos.physician/sos.police
or
operator specific emergency digits

To: urn:service:{sos/sos.ambulance/sos.animal-control/sos.fire/sos.marine/sos.mountain/sos.physician/sos.police
or
operator specific emergency digits

From: public user identity

P-Access-Network-Info

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

End device Test equipment
Interworking POTS
Off hook
Dial number ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE

ISDN interworking
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE

Apply post test routine

| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE |
ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### 7.2.5 Supplementary service control + +#### 7.2.5.1 Originating identification presentation and originating identification restriction + +##### 7.2.5.1.1 Test purposes for POTS + +| | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------------|--------------------------------------|--|-----------------------|-------------------|--------|---|--|-------------|---|--------------------------------|--|--------------------------------|--| +| TSS
OIP_OIR | TP_501_101 | Reference
subclause C.1.2.1 and C5
of [TS183 043] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | +| Test purpose
User Identification information received in an INVITE request

User Identification information received in an INVITE request ("P-Asserted-Id" and "From" headers) is used by the SUT. The SUT requests the media gateways to send this message over the analogue line using the Display Data Block parameter of the Display. | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
From: [A user identification]
P-Asserted-Identification: [A user identification] | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE →
180 Ringing ← Ringing, A user identification
Apply post test routine
| | | | | Test equipment | End device | INVITE | → | | 180 Ringing | ← | Ringing, A user identification | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | +| INVITE | → | | | | | | | | | | | | | | | +| 180 Ringing | ← | Ringing, A user identification | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|--------------------------------|--| +| TSS
OIP_OIR | TP_501_102 | Reference
subclause C.1.2.1, C5 of
[TS183 043] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The calling user wishes to override the default privacy setting

A service code command may be received by the SUT in case the calling user wishes to override the default privacy setting for a particular call, in which case the called party number is embedded in the command code as part of the supplementary information. The SUT generates an INVITE and the service code commands and the destination number is present in the Request Line. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: Request Line START PX SC (SR SI) SX" or "PX SC (SR SI) SX FINISH@pes-scc.operator.com
Note : The command syntax is described in subclause C.1.2.1.1 of [ETSI TS183 043] | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Off hook
Dial number → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
Apply post test routine
| | | | | End device | Test equipment | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | | Apply post test routine | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------------------|--------------------------------------|--|-------------------|--|-----------------------|--|----------|--|--|--|--|-------------|--|---|--------|--|--|--|---|-----------------------------------|--|--|--|---|-----|--|--|--|---|--------|--|--|--------------------------------|--|--|--| +| TSS
OIP_OIR | TP_501_103 | Reference
subclause C.1.2.1 and C5 of
[ETSI TS183 043] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
User Name information received in an INVITE request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that when user Name information is received in an INVITE request ("From" header /or "P-Asserted-Identity") it is used by the SUT to generate the appropriate Call Setup message. The SUT requests the media gateways to send this message over the analogue line using the Display Data Block.
parameter of the Display. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
From: [A user Name]
P-Asserted-Identification: [A user Name] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Off hook
Dial number → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
Apply post test routine
| | | | | End device | | Test equipment | | Off hook | | | | | Dial number | | → | INVITE | | | | ← | 407 Proxy Authentication Required | | | | → | ACK | | | | → | INVITE | | | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +##### 7.2.5.1.2 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|--|--------|--|---|---------|--|-------------|--|---|------------|--|--|--------------------------------|--|--|--| +| TSS
OIP_OIR | TP_501_201 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
INVITE received, no P-Asserted-Identity and no Privacy header present | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of an INVITE request and the P-Asserted-Identity is not present and no Privacy header is present, a SETUP is sent and a Calling party number Information Element is not included. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
183 Ringing ← ← ALERTING
Apply post test routine
| | | | | Test equipment | | End device | | INVITE | | → | → SETUP | | 183 Ringing | | ← | ← ALERTING | | | Apply post test routine | | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | | → | → SETUP | | | | | | | | | | | | | | | | | | | | | +| 183 Ringing | | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|-------------------|--------|---|---------|-------------|---|------------|--------------------------------|--|--| +| TSS
OIP_OIR | TP_501_202 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | +| Test purpose
INVITE received, no P-Asserted-Identity present and Privacy header present From header Anonymous | | | | | | | | | | | | | | | | +| Ensure that on receipt of an INVITE request and the P-Asserted-Identity is not present and a Privacy header is present the priv-value is set to 'id' or 'header' or 'user' the From header is set to an Anonymous value, a SETUP is sent and a Calling party number Information Element is included and coded as follows: | | | | | | | | | | | | | | | | +| Calling party number
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Screening indicator = Network provided
Number digits not present | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From: ; tag= | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Presentation indicator = Presentation restricted | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
183 Ringing ⬅ ⬅ ALERTING
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 183 Ringing | ⬅ | ⬅ ALERTING | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | +| 183 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
OIP_OIR | TP_501_203 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
INVITE received, no P-Asserted-Identity present and no Privacy header present From header Unavailable | | | | +| Ensure that on receipt of an INVITE request and the P-Asserted-Identity is not present and a Privacy header is present the priv-value is se to 'id' or 'header' or 'user' the From header is set to an Unavailable value, a SETUP is sent and a Calling party number Information Element is included and coded as follows: | | | | +| Calling party number
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Not available due to interworking
Screening indicator = Network provided
Number digits not present | | | | +| SIP header values
INVITE: From: ; tag= | | | | +| DSS1 Parameter values
SETUP: Calling party number
Presentation indicator = Not available due to interworking | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 183 Ringing | ⬅ | ⬅ ALERTING | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
OIP_OIR | TP_501_204 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +|----------------|------------|--------------------------------------------------------|--------------------------------------| + +|

Test purpose
INVITE received, P-Asserted-Identity present and no Privacy header present From header not in the format of an E.164 address

Ensure that on receipt of an INVITE request and the P-Asserted-Identity is present, the URI in the format of an E.164 address in the local number format and a no Privacy header is present, the URI of the From header is not in the format of an E.164 address, a SETUP is sent and a Calling party number Information Element is included and coded as follows:

Calling party number
Type of number = National number
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = User provided, verified and passed
Number digits:
    Number digits are derived from userinfo of the P-Asserted-Identity header. In case for local number format the userinfo is sent as digits

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

SIP header values
INVITE: P-Asserted-Identity: userinfo in local number format

| | | | | | | | | | | | | +|

DSS1 Parameter values
SETUP: Calling party number
    Type of number = National number
    Number digits derived from the P-Asserted-Identity

| | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
183 Ringing ⬅ ⬅ ALERTING
Apply post test routine
| | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 183 Ringing | ⬅ | ⬅ ALERTING | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | +| 183 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | + +| TSS
OIP_OIR | TP_501_205 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|-------------------|--------|---|---------|-------------|---|------------| +|

Test purpose
INVITE received, P-Asserted-Identity present and no Privacy header present From header not in the format of an E.164 address

Ensure that on receipt of an INVITE request and the P-Asserted-Identity is present, the URI in the format of an E.164 address in the global number format and a no Privacy header is present, the URI of the From header is not in the format of an E.164 address, a SETUP is sent and a Calling party number Information Element is included and coded as follows:

Calling party number
Type of number = National number
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = User provided, verified and passed
Number digits:
    Number digits are derived from userinfo of the P-Asserted-identity. In case for global number and the country code is the same as the SUT or the ISDN line is located, the country code is removed from the userinfo.

| | | | | | | | | | | | | +|

SIP header values
INVITE: P-Asserted-Identity: userinfo in local number format

| | | | | | | | | | | | | +|

DSS1 Parameter values
SETUP: Calling party number
    Type of number = National number
    Number digits derived from the P-Asserted-Identity

| | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
183 Ringing ⬅ ⬅ ALERTING

Apply post test routine

| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 183 Ringing | ⬅ | ⬅ ALERTING | +| | Test equipment | End device | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | +| 183 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | + +| TSS
OIP_OIR | TP_501_206 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +|

Test purpose
INVITE received, P-Asserted-Identity present and Privacy header not present From header not in the format of an E.164 address

Ensure that on receipt of an INVITE request and the P-Asserted-Identity is present, the URI in the format of an E.164 address in the global number format and a no Privacy header is present, the URI of the From header is not in the format of an E.164 address, a SETUP is sent and a Calling party number Information Element is included and coded as follows:

Calling party number
Type of number = International number
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = User provided, verified and passed
Number digits:
    Number digits are derived from userinfo of the P-Asserted-Identity header. In case for global number and the country code is not the same as the SUT or the ISDN line is located, the userinfo is sent as digits.

| | | | + +| | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------|--|-----------------------|-------------------|--------|---|---------|-------------|---|------------|--|--------------------------------|--| +| SIP header values
INVITE: P-Asserted-Identity: userinfo in global number format | | | | | | | | | | | | | | | +| DSSI Parameter values
SETUP: Calling party number
Type of number = International number
Number digits derived from the P-Asserted-Identity | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
INVITE→→ SETUP
183 Ringing←← ALERTING
Apply post test routine
| | | | Test equipment | End device | INVITE | → | → SETUP | 183 Ringing | ← | ← ALERTING | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | +| 183 Ringing | ← | ← ALERTING | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|-------------------|--|--------|---|---------|--|-------------|---|------------|--|--|--------------------------------|--|--| +| TSS
OIP_OIR | TP_501_207 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | +| Test purpose
INVITE received, P-Asserted-Identity present and Privacy header present From header not in the format of an E.164 address

Ensure that on receipt of an INVITE request and the P-Asserted-Identity is present the URI in the format of an E.164 address and a Privacy header is present the priv-value is set to 'id' or 'header' or 'user' the URI of the From header is not in the format of an E.164 address, a SETUP is sent and a Calling party number Information Element is included and coded as follows:

Calling party number
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Screening indicator = Network provided
Number digits not present | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: P-Asserted-Identity
Privacy: id | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values
SETUP: Calling party number
Presentation indicator
Presentation restricted | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
INVITE→→ SETUP
183 Ringing←← ALERTING
Apply post test routine
| | | | | Test equipment | End device | | INVITE | → | → SETUP | | 183 Ringing | ← | ← ALERTING | | | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | +| 183 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | + +| TSS
OIP_OIR | TP_501_208 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------| +|

Test purpose
INVITE received, P-Asserted-Identity not equal From header not in the format of an E.164 address Privacy header present

Ensure that on receipt of an INVITE request and the P-Asserted-Identity is present the URI in the format of an E.164 address and a no Privacy header is present the URI of the From header is in the format of an E.164 address and the userinfo is not equal to the userinfo of the P-Asserted-Identity, a SETUP is sent and two Calling party number Information Elements are included and coded as follows:

1st Calling party number
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = User provided, not verified
Number digits:
    Number digits are derived from userinfo of the From header. In case for global number and the country code is not the same as the SUT or the ISDN line is located, the userinfo is sent as digits

2nd Calling party number
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = User provided, verified and passed
Number digits:
    Number digits are derived from userinfo of the P-Asserted-Identity header. In case for global number and the country code is not the same as the SUT or the ISDN line is located, the userinfo is sent as digits

| | | | | | | | | | | | | | | | +|

SIP header values
INVITE: From:
          P-Asserted-Identity:

| | | | | | | | | | | | | | | | +|

DSS1 Parameter values
SETUP: Calling party number
          Screening indicator
          User provided, not verified
          Calling party number
          Screening indicator
          User provided, verified and passed

| | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE → → SETUP
183 Ringing ← ← ALERTING

Apply post test routine

| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 183 Ringing | ← | ← | ALERTING | +| | Test equipment | | End device | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | +| 183 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
OIP_OIR | TP_501_209 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
INVITE received, P-Asserted-Identity equal From header present no Privacy header present

Ensure that on receipt of an INVITE request and if the P-Asserted-Identity is present, the URI is in the format of an E.164 address and a no Privacy header is present, the URI of the From header is in the format of an E.164 address and the userinfo is equal to the userinfo of the P-Asserted-Identity, a SETUP is sent and one Calling party number Information Elements is included and coded as follows:

Calling party number
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = User provided, verified and passed
Number digits:
Number digits are derived from userinfo of the P-Asserted-Identity header . In a case where the global number and the country code is not located the same as the SUT or the ISDN line , the userinfo is sent as digits. | | | | +| SIP header values
INVITE: From:
P-Asserted-Identity: | | | | +| DSS1 Parameter values
SETUP: Calling party number
Screening indicator
User provided, verified and passed | | | | +| Message flow
Test equipment End device
INVITE ➠ ➠ SETUP
183 Ringing ⬅ ⬅ ALERTING
| | | | +| Apply post test routine | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------| +| TSS
OIP_OIR | TP_501_210 | Reference
subclause 5.2.3.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | +| Test purpose
INVITE received, P-Asserted-Identity present and From header present Privacy header present

Ensure that on receipt of an INVITE request and if the P-Asserted-Identity is present, the URI is in the format of an E.164 address and a Privacy header is present, the URI of the From header is in the format of an E.164 address, a SETUP is sent and a Calling party number Information Elements is included and coded as follows:

Calling party number
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Screening indicator = Network provided
Number digits not present | | | | +| SIP header values
INVITE: From:
P-Asserted-Identity:
Privacy: id,header,user | | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| DSS1 Parameter values
SETUP: Calling party number
Presentation indicator
Presentation restricted | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 183 Ringing | ← | ← ALERTING | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_211 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +| Test purpose
SETUP received, Calling party number national significant Presentation Restriction Indicator is set to restricted | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation restricted , an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Preferred Identity header field is present, the userinfo is set to the identified Public user identity. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid. A Privacy header is present set to 'id' and 'header' and 'user'. | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: id, header, user | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation restricted
Address digits present | | | | +| Message flow | | | | +| | End device | | Test equipment | +| SETUP | | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| SETUP ACKNOWLEDGE | | ← | 100 Trying | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|-------------------|--|---|------------| +| TSS
OIP_OIR | TP_501_212 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number national significant Presentation Restriction Indicator is set to restricted

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, a P Preferred Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid. A Privacy header is present set to 'id' and 'header' and 'user'.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From: anonymous@anonymous.invalid>
P Preferred Identity:
Privacy: id, header, user | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation restricted
Address digits present | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | | End device | | Test equipment | SETUP | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | SETUP ACKNOWLEDGE | | ⬅ | 100 Trying | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_213 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +| Test purpose
SETUP received, Calling party number international Presentation Restriction Indicator is set to restricted

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'International number', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If a P Preferred Identity header field is present, the userinfo is derived from the Address digits. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid. A Privacy header is present set to 'id' and 'header' and 'user'

| | | | +| SIP header values
INVITE: From: anonymous@anonymous.invalid>
P Preferred Identity:
Privacy: id, header, user | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = International number
Presentation Restriction Presentation restricted
Address digits present | | | | + +| Message flow | | | +|--------------------------------|---|-----------------------------------| +| End device | | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_214 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +**Test purpose** +*SETUP received, Calling party number Subscriber Presentation Restriction Indicator is set to restricted* + +Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Preferred Identity header field is present, the userinfo is derived from the Address digits. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid. A Privacy header is present set to 'id' and 'header' and 'user'. + +**SIP header values** + INVITE: From: + P Preferred Identity: + Privacy: id, header, user + +**DSSI Parameter values** + SETUP: Calling party number + Type of number = Subscriber + Presentation Restriction Presentation restricted + Address digits present + +| Message flow | | | +|--------------------------------|---|-----------------------------------| +| End device | | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|--|-----------------------|--|-------|---|--|--------|--|--|---|--|-----------------------------------|--|--|---|--|-----|--|--|---|--|--------|--|-------------------|---|--|------------|--| +| TSS
OIP_OIR | TP_501_215 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number Subscriber Presentation Restriction Indicator is set to restricted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, a P Preferred Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid. A Privacy header is present set to 'id' and 'header' and 'user'

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From: anonymous@anonymous.invalid>
P Preferred Identity:
Privacy: id, header, user | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = Subscriber
Presentation Restriction Presentation restricted
Address digits present | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
SETUP ACKNOWLEDGE ← 100 Trying
Apply post test routine
| | | | | End device | | Test equipment | | SETUP | → | | INVITE | | | ← | | 407 Proxy Authentication Required | | | → | | ACK | | | → | | INVITE | | SETUP ACKNOWLEDGE | ← | | 100 Trying | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_216 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +| Test purpose
SETUP received, Calling party number Unknown Presentation Restriction Indicator is set to restricted | | | | +|

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits matches with a registered Public identity a P Preferred Identity header field is present, the userinfo is derived from the Address digits. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid. A Privacy header is present set to 'id' and 'header' and 'user'

| | | | +| SIP header values
INVITE: From: anonymous@anonymous.invalid>
P Preferred Identity:
Privacy: id, header, user | | | | + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DSSI Parameter values
SETUP: Calling party number
Type of number = Unknown
Presentation Restriction Presentation restricted
Address digits present | | +| Message flow | | +| End device | Test equipment | +| SETUP | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE | +| SETUP ACKNOWLEDGE | ← 100 Trying | +| Apply post test routine | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_217 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +| Test purpose
SETUP received, Calling party number Unknown Presentation Restriction Indicator is set to restricted | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, a P Preferred Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid. A Privacy header is present set to 'id' and 'header' and 'user'. | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: id, header, user | | | | +| DSSI Parameter values
SETUP: Calling party number
Type of number = Unknown
Presentation Restriction Presentation restricted
Address digits present | | | | +| Message flow | | | | +| End device | | | Test equipment | +| SETUP | | | → INVITE | +| | | | ← 407 Proxy Authentication Required | +| | | | → ACK | +| | | | → INVITE | +| SETUP ACKNOWLEDGE | | | ← 100 Trying | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|-------------------|---|------------|--| +| TSS
OIP_OIR | TP_501_218 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number Presentation Restriction Indicator is set to restricted Address digits not present | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number, if Address digits are not present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If a P Preferred Identity header field is present, the userinfo is set to the default Public user identity. The Userinfo of the From header is set to unavailable@unknown.invalid, and if a Privacy header is present, set to 'id' and 'header' and 'user'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP Header values
INVITE: From:
P Preferred Identity:
Privacy: id, header, user | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation restricted
Address digits not present | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
SETUP ACKNOWLEDGE ← 100 Trying

Apply post test routine

| | | | | End device | | Test equipment | SETUP | → | INVITE | | | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | | SETUP ACKNOWLEDGE | ← | 100 Trying | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|-------------------|---|------------|--| +| TSS
OIP_OIR | TP_501_219 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number absent, Privacy header is present | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message and if the Calling party number IE is absent, an INVITE request is sent. If a P Preferred Identity header field is present, the userinfo is set to the default Public user identity. The Userinfo of the From header is set to unavailable@unknown.invalid. If a Privacy header is present set to 'id' and 'header' and 'user'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: id, header, user | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number not present | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
SETUP ACKNOWLEDGE ← 100 Trying

Apply post test routine

| | | | | End device | | Test equipment | SETUP | → | INVITE | | | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | | SETUP ACKNOWLEDGE | ← | 100 Trying | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|-------------------|--|---|------------|--------------------------------|--|--|--| +| TSS
OIP_OIR | TP_501_220 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number absent, Privacy header is absent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message and if the Calling party number IE is absent, an INVITE request is sent. If a P Preferred Identity header field is present, the userinfo is set to the default Public user identity. The Userinfo of the From header is set. A Privacy header is not present. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Preferred Identity: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number not present | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | | End device | | Test equipment | SETUP | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | SETUP ACKNOWLEDGE | | ⬅ | 100 Trying | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|-------------------|--|---|------------|--------------------------------|--|--|--| +| TSS
OIP_OIR | TP_501_221 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number NOA national significant Presentation Restriction Indicator is set to allowed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity and a P Preferred Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format, and if a Privacy header is present, set to 'none'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: none | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | | End device | | Test equipment | SETUP | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | SETUP ACKNOWLEDGE | | ⬅ | 100 Trying | Apply post test routine | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------|--------------------------------|--|--| +| TSS
OIP_OIR | TP_501_222 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number NOA national significant Presentation Restriction Indicator is set to allowed | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity and a P Preferred Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format and a Privacy header is present, set to 'none'. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: none | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | | End device | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | Apply post test routine | | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_223 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +| Test purpose
SETUP received, Calling party number NOA international Presentation Restriction Indicator is set to allowed | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'International number', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Preferred Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the global format and a Privacy header is present, set to 'none'. | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: none | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = International number
Presentation Restriction Presentation allowed
Address digits present | | | | + +| Message flow | | | +|--------------------------------|-------------------|-----------------------------------| +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_224 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +**Test purpose** +*SETUP received, Calling party number NOA international Presentation Restriction Indicator is set to allowed* + +Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'International number', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, if a P Preferred Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the global number format and a Privacy header is present, set to 'none'. + +**SIP header values** + INVITE: From: + P Preferred Identity: + Privacy: none + +**DSSI Parameter values** + SETUP: Calling party number + Type of number = 'International number' + Presentation Restriction Presentation allowed + Address digits present + +| Message flow | | | +|--------------------------------|-------------------|-----------------------------------| +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------|--------------------------------|--|--| +| TSS
OIP_OIR | TP_501_225 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number NOA subscriber Presentation Restriction Indicator is set to allowed | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity and a P Preferred Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format and a Privacy header is present, set to 'none'.

| | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: none | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = Subscriber
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➠ INVITE
⬅ 407 Proxy Authentication Required
➠ ACK
➠ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➠ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➠ | ACK | | ➠ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | +| | ➠ | ACK | | | | | | | | | | | | | | | | | | | | | | | +| | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_226 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +| Test purpose
SETUP received, Calling party number NOA subscriber Presentation Restriction Indicator is set to allowed | | | | +|

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity and a P Preferred Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format And a Privacy header is present, set to 'none'.

| | | | +| SIP header values
SETUP: Calling party number
Type of number = Subscriber
Presentation Restriction Presentation allowed
Address digits present | | | | +| DSS1 Parameter values
INVITE: From:
P Preferred Identity:
Privacy: none | | | | + +| Message flow | | | +|--------------------------------|-------------------|-----------------------------------| +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_227 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +**Test purpose** +*SETUP received, Calling party number NOA unknown Presentation Restriction Indicator is set to allowed* + +Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity and a P Preferred Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format and a Privacy header is present, set to 'none'. + +**SIP header values** + INVITE: From: + P Preferred Identity: + Privacy: none + +**DSSI Parameter values** + SETUP: Calling party number + Type of number = Unknown + Presentation Restriction Presentation allowed + Address digits present + +| Message flow | | | +|--------------------------------|-------------------|-----------------------------------| +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------| +| TSS
OIP_OIR | TP_501_228 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number NOA national significant Presentation Restriction Indicator is set to allowed | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity and a P Preferred Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format and a Privacy header is present, set to 'none'.

| | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Preferred Identity:
Privacy: none | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = Unknown
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_229 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
Mw interface. SETUP received, Calling party number national significant Presentation Restriction Indicator is set to restricted | | | | +|

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation restricted, and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity and a P Asserted Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid and a Privacy header is present, set to 'id' and 'header' and 'user'

| | | | +| SIP header values
INVITE: From: anonymous@anonymous.invalid>
P Asserted Identity:
Privacy: id, header, user | | | | + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| DSS1 Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation restricted
Address digits present | | +| Message flow | | +| End device | Test equipment | +| SETUP | ➔     INVITE | +| SETUP ACKNOWLEDGE | ⬅     100 Trying | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_230 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
Mw interface. SETUP received, Calling party number national significant Presentation Restriction Indicator is set to restricted | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation restricted, and an INVITE request is sent. If the Calling party number digits does not matche with a registered Public identity and a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid , and a Privacy header is present, set to 'id' and 'header' and 'user'. | | | | +| SIP header values
INVITE: | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation restricted
Address digits present | | | | +| Message flow | | | | +| End device | Test equipment | | | +| SETUP | ➔     INVITE | | | +| SETUP ACKNOWLEDGE | ⬅     100 Trying | | | +| Apply post test routine | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_231 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
Mw interface. SETUP received, Calling party number international Presentation Restriction Indicator is set to restricted | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'International number', Presentation Restriction Indicator is set to Presentation restricted, and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity and a P Asserted Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the global number format or set to anonymous@anonymous.invalid anda Privacy header is present, set to 'id' and 'header' and 'user'. | | | | + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: id, header, user | | +| DSS1 parameter values
SETUP: Calling party number
Type of number = International number
Presentation Restriction Presentation restricted
Address digits present | | +| Message flow | | +| End device | Test equipment | +| SETUP | → INVITE | +| SETUP ACKNOWLEDGE | ← 100 Trying | +| Apply post test routine | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_232 | Reference
subclause 5.2.3.2/
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
Mw interface. SETUP received, Calling party number international Presentation Restriction Indicator is set to restricted | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'International number', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. The Calling party number digits does not matche with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. If the userinfo of the From header is derived from the address digits of the calling party number IE in the global number format or set to anonymous@anonymous.invalid, a Privacy header is present, set to 'id' and 'header' and 'user'. | | | | +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: id, header, user | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = International number
Presentation Restriction Presentation restricted
Address digits present | | | | +| Message flow | | | | +| End device | Test equipment | | | +| SETUP | → INVITE | | | +| SETUP ACKNOWLEDGE | ← 100 Trying | | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|------------|--------------------------------|--|--| +| TSS
OIP_OIR | TP_501_233 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | | | | | | | | | | | | | +|

Test purpose
Mw interface. SETUP received, Calling party number Subscriber Presentation Restriction Indicator is set to restricted

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P-Asserted-Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid, a Privacy header is present, set to 'id' and 'header' and 'user'.

SIP header values
INVITE: From: <derived from the Calling party number Address digits or
                        anonymous@anonymous.invalid>
            P Asserted Identity: <matched Public user identity>
            Privacy: id, header, user

DSS1 Parameter values
SETUP: Calling party number
            Type of number = Subscriber
            Presentation Restriction Presentation restricted
            Address digits present

Message flow

End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ← 100 Trying
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ← | 100 Trying | Apply post test routine | | | +| End device | | Test equipment | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ← | 100 Trying | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_234 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|

Test purpose
Mw interface. SETUP received, Calling party number Subscriber Presentation Restriction Indicator is set to restricted

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits does not matche with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to anonymous@anonymous.invalid, a Privacy header is present, set to 'id' and 'header' and 'user'.

SIP header values
INVITE: From: <derived from the Calling party number Address digits or
                        anonymous@anonymous.invalid>
            P Asserted Identity: <Default Public user identity>
            Privacy: id, header, user

DSS1 Parameter values
SETUP: Calling party number
            Type of number = Subscriber
            Presentation Restriction Presentation restricted
            Address digits present

| | | | + +| Message flow | | | +|--------------------------------|---|-----------------------| +| End device | | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_235 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +**Test purpose** +*Mw interface. SETUP received, Calling party number Unknown Presentation Restriction Indicator is set to restricted* + +Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the identified Public user identity. If the userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to [anonymous@anonymous.invalid](mailto:anonymous@anonymous.invalid), a Privacy header is present, set to 'id' and 'header' and 'user'. + +**SIP header values** + INVITE: From: + P Asserted Identity: + Privacy: id, header, user + +**DSS1 Parameter values** + SETUP: Calling party number + Type of number = Unknown + Presentation Restriction Presentation restricted + Address digits present + +| Message flow | | | +|--------------------------------|---|-----------------------| +| End device | | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_236 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +**Test purpose** +*Mw interface. SETUP received, Calling party number Unknown Presentation Restriction Indicator is set to restricted* + +Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If the Calling party number digits does not matche with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format or set to [anonymous@anonymous.invalid](mailto:anonymous@anonymous.invalid), a Privacy header is present, set to 'id' and 'header' and 'user' + +**SIP header values** + INVITE: From: + P Asserted Identity: + Privacy: id, header, user + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------| +| DSSI Parameter values
SETUP: Calling party number
Type of number = Unknown
Presentation Restriction Presentation restricted
Address digits present | | | +| Message flow | | | +| | End device | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_237 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
Mw interface. SETUP received, Calling party number Address digits not present Presentation Restriction Indicator is set to restricted | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits not present, Presentation Restriction Indicator is set to Presentation restricted, an INVITE request is sent. If a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is set to 'unavailable@unknown.invalid'. If a Privacy header is present set to 'id' and 'header' and 'user' | | | | +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: id, header, user | | | | +| DSSI Parameter values
SETUP: Calling party number
Presentation Restriction Presentation restricted
Address digits not present | | | | +| Message flow | | | | +| | End device | | Test equipment | +| SETUP | → | | INVITE | +| SETUP ACKNOWLEDGE | ← | | 100 Trying | +| Apply post test routine | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_238 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
Mw interface. SETUP received, Calling party number is not present | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Information Element not present Presentation, an INVITE request is sent. If a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is set to 'unavailable@unknown.invalid'. If a Privacy header is present set to 'id' and 'header' and 'user'. | | | | +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: id, header, user | | | | + +| | | | +|-------------------------------------------------------------------------|-------------------|-----------------------| +| DSSI Parameter values
SETUP: Calling party number not present | | | +| Message flow | | | +| | End device | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_239 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| Test purpose
Mw interface. SETUP received, Calling party number is not present | | +| Ensure that on receipt of a SETUP message containing a Calling party number Information Element not present Presentation, an INVITE request is sent. If a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is set to 'unavailable@unknown.invalid'. A Privacy header is not present. | | +| SIP header values
INVITE: From:
P Asserted Identity: | | +| DSSI Parameter values
SETUP: Calling party number not present | | +| Message flow | | +| | End device | +| SETUP | → | +| SETUP ACKNOWLEDGE | ← | +| Test equipment | | +| INVITE | | +| 100 Trying | | +| Apply post test routine | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_240 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Test purpose
SETUP received, Calling party number NOA national significant Presentation Restriction Indicator is set to allowed | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation allowed, an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format a Privacy header is present set to 'none'. | | +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: none | | +| DSSI Parameter values
SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation allowed
Address digits present | | + +| Message flow | | | +|--------------------------------|---|-----------------------| +| End device | | Test equipment | +| SETUP | ➔ | INVITE | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_241 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

SETUP received, Calling party number NOA national significant Presentation Restriction Indicator is set to allowed

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'National number', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format,a Privacy header is present set to 'none'.

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

SIP header values

INVITE: From: <derived from the Calling party number Address digits>
P Asserted Identity: <Default Public user identity>
Privacy: none

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

DSS1 Parameter values

SETUP: Calling party number
Type of number = National number
Presentation Restriction Presentation allowed
Address digits present

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------------|---|-----------------------| +| End device | | Test equipment | +| SETUP | ➔ | INVITE | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_242 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

SETUP received, Calling party number NOA international Presentation Restriction Indicator is set to allowed

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'International number', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the global format, a Privacy header is present set to 'none'.

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

SIP header values

INVITE: From: <derived from the Calling party number Address digits>
P Asserted Identity: <matched Public user identity>
Privacy: none

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------| +| DSSI Parameter values
SETUP: Calling party number
Type of number = International number
Presentation Restriction Presentation allowed
Address digits present | | | +| Message flow | | | +| End device | | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_243 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
SETUP received, Calling party number NOA international Presentation Restriction Indicator is set to allowed

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'International number', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the global number format, a Privacy header is present set to 'none'. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: none | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DSSI Parameter values
SETUP: Calling party number
Type of number = International number'
Presentation Restriction Presentation allowed
Address digits present | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------------|---|-----------------------| +| Message flow | | | +| End device | | Test equipment | +| SETUP | → | INVITE | +| SETUP ACKNOWLEDGE | ← | 100 Trying | +| Apply post test routine | | | + +| | | | | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| +| TSS
OIP_OIR | TP_501_244 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|--------------------------------------------------------|--------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
SETUP received, Calling party number NOA subscriber Presentation Restriction Indicator is set to allowed

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the identified Public user identity. If the Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format,a Privacy header is present set to 'none'. | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------|-----------------------|-----------------------|--|-------|---|--|--------|--|-------------------|---|--|------------|--|--------------------------------|--|--|--|--| +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: none | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = Subscriber
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | End device | | Test equipment | | SETUP | ➔ | | INVITE | | SETUP ACKNOWLEDGE | ⬅ | | 100 Trying | | Apply post test routine | | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | | INVITE | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | | 100 Trying | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|--|-----------------------|--|-------|---|--|--------|--|-------------------|---|--|------------|--|--------------------------------|--|--|--|--| +| TSS
OIP_OIR | TP_501_245 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number NOA subscriber Presentation Restriction Indicator is set to allowed

Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Subscriber', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format. A Privacy header is present set to 'none'. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: none | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = Subscriber
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | | End device | | Test equipment | | SETUP | ➔ | | INVITE | | SETUP ACKNOWLEDGE | ⬅ | | 100 Trying | | Apply post test routine | | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | | INVITE | | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | | 100 Trying | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|-------------------|---|------------|--------------------------------|--|--| +| TSS
OIP_OIR | TP_501_246 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number NOA unknown Presentation Restriction Indicator is set to allowed | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits matches with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the identified Public user identity. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format. A Privacy header is present set to 'none'. | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: none | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = Unknown
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | | End device | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | Apply post test routine | | | +| | End device | Test equipment | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|-------------------|---|------------|--------------------------------|--|--| +| TSS
OIP_OIR | TP_501_247 | Reference
subclause 5.2.3.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | | | | | | | | | | | | | +| Test purpose
SETUP received, Calling party number NOA national significant Presentation Restriction Indicator is set to allowed | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a Calling party number Address digits present and the Type of number is set to 'Unknown', Presentation Restriction Indicator is set to Presentation allowed and an INVITE request is sent. If the Calling party number digits does not match with a registered Public identity, a P Asserted Identity header field is present, the userinfo is set to the Default Public user identity. The Userinfo of the From header is derived from the address digits of the calling party number IE in the local number format. A Privacy header is present set to 'none'. | | | | | | | | | | | | | | | | +| SIP header values
INVITE: From:
P Asserted Identity:
Privacy: none | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Calling party number
Type of number = Unknown
Presentation Restriction Presentation allowed
Address digits present | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying
Apply post test routine
| | | | | End device | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | Apply post test routine | | | +| | End device | Test equipment | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | + +#### 7.2.5.2 Terminating identification presentation and terminating identification restriction) + +##### 7.2.5.2.1 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|--------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|---------------|---|---|---------|-----|---|---|-------------| +| TSS
TIP_TIR | TP_502_101 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CONNECT no Connected number or no valid Connected number received, 200 OK (INVITE) is sent

Ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. The P-Asserted-Identity contains the value saved from the P-Called-Party-ID header that was received in the INVITE request if no Connected number or no valid Connected number is present in the received CONNECT. No "from-change" tag in the supported header. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
P-Called-Party-ID =

200 OK (INVITE):
P-Asserted-Identity = | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK INVITE ← ← CONNECT
ACK → → CONNECT ACK
Apply post test routine
| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 180 Ringing | ← | ← | ALERTING | 200 OK INVITE | ← | ← | CONNECT | ACK | → | → | CONNECT ACK | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | ← | CONNECT | | | | | | | | | | | | | | | | | | | | | +| ACK | → | → | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|--------------------------------------------------| +| TSS
TIP_TIR | TP_502_102 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
CONNECT unknown or Subscriber number received, 200 OK (INVITE) is sent

Ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. The P-Asserted-Identity is present with that value, including the display name if previously stored during registration representing the terminating user indicated in the connected number type of number: unknown or Subscriber number . No "from-change" tag in the supported header | | | | +| SIP header values
200 OK (INVITE):
P-Asserted-Identity = | | | | +| DSS1 Parameter values
CONNECT: Connected number
Nature of address = unknown or Subscriber number
Number Digits = | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ ALERTING | +|
200 OK INVITE |
⬅ |
⬅ CONNECT | +| ACK | ➔ | ➔ CONNECT ACK | +| Apply post test routine | | | + +| | | | | +|----------------|------------|----------------------------------------------------------|--------------------------------------------------| +| TSS
TIP_TIR | TP_502_103 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|----------------------------------------------------------|--------------------------------------------------| + +|

Test purpose
CONNECT National number received, 200 OK (INVITE) is sent

When an INVITE is received and no 'from-change' tag is contained in the Supported header,ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. The P-Asserted-Identity is present with that value, including the display name if previously stored during registration representing the terminating user indicated in the connected number type of number: National number. No "from-change" tag in the supported header.

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

SIP header values
200 OK (INVITE):
P-Asserted-Identity = <registered number>

| | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
CONNECT: Connected number
    Nature of address = National number
    Number Digits = <connected number>

| | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK INVITE

⬅

⬅ CONNECT
ACK ➔ ➔ CONNECT ACK
Apply post test routine
| | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING |
200 OK INVITE |
⬅ |
⬅ CONNECT | ACK | ➔ | ➔ CONNECT ACK | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | +|
200 OK INVITE |
⬅ |
⬅ CONNECT | | | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ CONNECT ACK | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------|------------|----------------------------------------------------------|--------------------------------------------------| +| TSS
TIP_TIR | TP_502_104 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +|----------------|------------|----------------------------------------------------------|--------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose
CONNECT international number received, 200 OK (INVITE) is sent

When an INVITE is received and no 'from-change' tag contained in the Supported header,ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. The P-Asserted-Identity is present with that value, including the display name if previously stored during registration representing the terminating user indicated in the connected number type of number: international number. No "from-change" tag in the supported header.

| +|

SIP header values
200 OK (INVITE):
P-Asserted-Identity = <registered number>

| + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| DSSI Parameter values
CONNECT: Connected number
Nature of address = international number
Number Digits = | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | → CONNECT ACK | +| Apply post test routine | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|-------------------------------------------------------------------| +| TSS
TIP_TIR | TP_502_105 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1
AND NOT 5.4/2 | +| Test purpose
CONNECT National number received, 200 OK (INVITE) is sent | | | | +| When an INVITE is received and a 'from-change' tag contained in the Supported header, ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. The P-Asserted-Identity is present with that value, including the display name if previously stored during registration representing the terminating user indicated in the connected number type of number: National number . No "from-change" tag in the supported header. | | | | +| SIP header values
200 OK (INVITE):
P-Asserted-Identity = | | | | +| DSSI Parameter values
CONNECT: Connected number
Nature of address = National number
Number Digits = | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | → | | → SETUP | +| 180 Ringing | ← | | ← ALERTING | +| 200 OK INVITE | ← | | ← CONNECT | +| ACK | → | | → CONNECT ACK | +| Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|-------------------------------------------------------------------| +| TSS
TIP_TIR | TP_502_106 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1
AND NOT 5.4/2 | +| Test purpose
CONNECT international number received, 200 OK (INVITE) is sent | | | | +| If an INVITE is received and a 'from-change' tag contained in the Supported header, ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. If the P-Asserted-Identity is present with that value, including the display name if previously stored during registration, representing the terminating user indicated in the connected number type of number: international number , no "from-change" tag in the supported header. | | | | + +| SIP header values
200 OK (INVITE):
P-Asserted-Identity = | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|----------------|--|------------|--------|----------|-------|-------------|----------|----------|-------------------|--------------|-------------|-----|----------|-------------|--------------------------------|--|--| +| DSS1 Parameter values
CONNECT: Connected number
Nature of address = international number
Number Digits = | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
INVITE→      →SETUP
180 Ringing←      ←ALERTING

200 OK INVITE

←      ←

CONNECT
ACK→      →CONNECT ACK
Apply post test routine
| | | Test equipment | | End device | INVITE | →      → | SETUP | 180 Ringing | ←      ← | ALERTING |
200 OK INVITE |
←      ← |
CONNECT | ACK | →      → | CONNECT ACK | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | +| INVITE | →      → | SETUP | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ←      ← | ALERTING | | | | | | | | | | | | | | | | | | | +|
200 OK INVITE |
←      ← |
CONNECT | | | | | | | | | | | | | | | | | | | +| ACK | →      → | CONNECT ACK | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +| TSS
TIP_TIR | TP_502_107 | Reference
subclause 5.2.2.1.1 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 AND 5.4/2 | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------|------------------------------------------------------------|----------------|--|------------|--------|----------|-------|-------------|----------|----------|-------------------|--------------|-------------|-----|----------|-------------|------------|-------|--|---------------|---|--|--------------------------------|--|--| +| Test purpose
CONNECT National number received, 200 OK (INVITE) is sent

If an INVITE is received and a 'from-change' tag contained in the Supported header,ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. If the P-Asserted-Identity is present with that value, including the display name if previously stored during registration, representing the terminating user indicated in the connected number type of number: National number,a "from-change" tag is present in the supported header. An UPDATE is sent and the From header contains the digits received in the Connected Number. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Supported: from-change

200 OK (INVITE):
P-Asserted-Identity =

UPDATE:
From: | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Connected number
Nature of address = National number
Number Digits = | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
INVITE→      →SETUP
180 Ringing←      ←ALERTING

200 OK INVITE

←      ←

CONNECT
ACK→      →CONNECT ACK

UPDATE

←
200 OK UPDATE→
Apply post test routine
| | | | Test equipment | | End device | INVITE | →      → | SETUP | 180 Ringing | ←      ← | ALERTING |
200 OK INVITE |
←      ← |
CONNECT | ACK | →      → | CONNECT ACK |
UPDATE |
← | | 200 OK UPDATE | → | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | →      → | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ←      ← | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | +|
200 OK INVITE |
←      ← |
CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | →      → | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +|
UPDATE |
← | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK UPDATE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Rec. ITU-T Q.4014.2 (04/2019)**     317 + +| TSS
TIP_TIR | TP_502_108 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1
AND 5.4/2 | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|-------------------|--------|---|---------|-------------|---|------------|-------------------|-------|---------------|-----|---|---------------|------------|-------|--|---------------|---|--| +| Test purpose
CONNECT international number received, 200 OK (INVITE) is sent

If an INVITE is received and a 'from-change' tag contained in the Supported header,ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. If the P-Asserted-Identity is present with that value, including the display name if previously stored during registration, representing the terminating user indicated in the connected number type of number: international number,a "from-change" tag is present in the supported header, an UPDATE is sent and the From header contains the digits received in the Connected Number. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Supported: from-change

200 OK (INVITE):
P-Asserted-Identity =

UPDATE:
From: | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Connected number
Nature of address = international number
Number Digits = | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING

200 OK INVITE

⬅

⬅ CONNECT
ACK ➔ ➔ CONNECT ACK

UPDATE

⬅
200 OK UPDATE ➔
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING |
200 OK INVITE |
⬅ |
⬅ CONNECT | ACK | ➔ | ➔ CONNECT ACK |
UPDATE |
⬅ | | 200 OK UPDATE | ➔ | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | | | | | | | +|
200 OK INVITE |
⬅ |
⬅ CONNECT | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | ➔ CONNECT ACK | | | | | | | | | | | | | | | | | | | | | | | +|
UPDATE |
⬅ | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK UPDATE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
TIP_TIR | TP_502_109 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1
AND 5.4/2 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| Test purpose
No 'from-change' tag in the INVITE received, 200 OK (INVITE) is sent and no 'from-change' tag is present

If an INVITE is received and no 'from-change' tag contained in the Supported header,ensure that a 200 OK (INVITE) is sent when a CONNECT message was received. a "from-change" tag is not present in the supported header nor UPDATE is sent | | | | +| SIP header values
200 OK (INVITE):
P-Asserted-Identity = | | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| DSSI Parameter values
CONNECT: Connected number
Nature of address = national number
Number Digits = | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | → CONNECT ACK | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|--------------------------------------------------| +| TSS
TIP_TIR | TP_502_110 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2 | +| Test purpose
No 'from-change' tag in the INVITE received, CONNECT received, 200 OK (INVITE) is sent no 'from-change' tag present | | | | +| Ensure that no 'from-change' tag in a Supported header in the sent 200 OK INVITE is present if no 'from-change' tag was received in the supported header in the received INVITE. No P-Asserted-Identity or P-Preferred-Identity header is present in the 200 OK INVITE. No UPDATE is sent. | | | | +| SIP header values | | | | +| DSSI Parameter values | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | → | | → SETUP | +| 180 Ringing | ← | | ← ALERTING | +| 200 OK INVITE | ← | | ← CONNECT | +| ACK | → | | → CONNECT ACK | +| Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
TIP_TIR | TP_502_111 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2
AND 5.4/2 | +| Test purpose
'from-change' tag in the INVITE received, CONNECT received, 200 OK (INVITE) is sent no 'from-change' tag present | | | | +| Ensure that no 'from-change' tag in a Supported header in the sent 200 OK INVITE is present if a 'from-change' tag was received in the supported header in the received INVITE and the nature of address of the received CONNECT is set to Nature_of_address as indicated in Table 7.2.5.2.1-1 | | | | +| No P-Asserted-Identity or P-Preferred-Identity header is present in the 200 OK INVITE. No UPDATE is sent. | | | | +| SIP header values | | | | +| DSSI Parameter values | | | | + +| Message flow | | | +|-------------------------|----------------|---------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | → CONNECT ACK | +| Apply post test routine | | | + +| TSS
TIP_TIR | TP_502_112 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2
AND 5.4/2 | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------------------------------------------------|---------------------------------------------------------------|--|----------------|------------|--------|---|---------|-------------|---|------------|---------------|---|-----------|-----|---|---------------|-------------------------|--|--| +| Test purpose
'from-change' tag in the INVITE received, CONNECT received, 200 OK (INVITE) is sent no 'from-change' tag present | | | | | | | | | | | | | | | | | | | | | | +| Ensure that no 'from-change' tag in a Supported header in the sent 200 OK INVITE is present if a 'from-change' tag was received in the supported header in the received INVITE and no or invalid connected number information element was present in the received CONNECT. | | | | | | | | | | | | | | | | | | | | | | +| No P-Asserted-Identity or P-Preferred-Identity header is present in the 200 OK INVITE. No UPDATE is sent. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: 'from-change'
200 OK INVITE: no 'from-change' tag | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: no or invalid connected number information element | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
INVITE→→ SETUP
180 Ringing←← ALERTING
200 OK INVITE←← CONNECT
ACK→→ CONNECT ACK
Apply post test routine
| | | | | Test equipment | End device | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | 200 OK INVITE | ← | ← CONNECT | ACK | → | → CONNECT ACK | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | ← CONNECT | | | | | | | | | | | | | | | | | | | | +| ACK | → | → CONNECT ACK | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.5.2.1-1 – Handling of Nature of Address indicator** + +| Nature_of_address | Nature of address value | +|-------------------|-------------------------| +| VA_1 | Unknown | +| VA_2 | Subscriber number | + +| TSS
TIP_TIR | TP_502_113 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2
AND 5.4/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|---------------|---|---|---------|-----|---|---|-------------|--------|---|--|--|---------------|---|--|--| +| Test purpose
'from-change' tag in the INVITE received, CONNECT received, 200 OK (INVITE) is sent 'from-change' tag present | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that the 'from-change' tag in a Supported header in the sent 200 OK INVITE is present if a 'from-change' tag was received in the supported header in the received INVITE and the nature of address of the received CONNECT is set to Nature_of_address as indicated in Table 7.2.5.2.1-2

No P-Asserted-Identity or P-Preferred-Identity header is present in the 200 OK INVITE. An UPDATE is sent and the From header contains the digits received in the Connected Number.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: Supported: from-change
200 OK (INVITE):
Supported: from-change
UPDATE: From: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Connected number
Nature of address = National number or international number
Number Digits = | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK INVITE ← ← CONNECT
ACK → → CONNECT ACK
UPDATE ←
200 OK UPDATE →

Apply post test routine

| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 180 Ringing | ← | ← | ALERTING | 200 OK INVITE | ← | ← | CONNECT | ACK | → | → | CONNECT ACK | UPDATE | ← | | | 200 OK UPDATE | → | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | ← | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | → | CONNECT ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UPDATE | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK UPDATE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
TIP_TIR | TP_502_114 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2
AND 5.4/2 | +| Test purpose
Connected Sub-address is transported in the From header of the UPDATE | | | | +|

Ensure that on receipt of a Connected Sub-Address in the received CONNECT message, an as isub parameter is sent in the From header of the sent UPDATE.

| | | | +| SIP header values
INVITE: Supported: from-change
200 OK (INVITE):
Supported: from-change
UPDATE: From: URI, isub = | | | | +| DSS1 Parameter values
CONNECT: Connected Sub-Address | | | | + +| Message flow | | | +|-------------------------|----------------|---------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | → CONNECT ACK | +| UPDATE | ← | | +| 200 OK UPDATE | → | | +| Apply post test routine | | | + +**Table 7.2.5.2.1-2 – Mapping of Nature of Address indicator into From header in the UPDATE** + +| Nature_of_address | Nature of address value | Connected number digits | Form header URI | +|-------------------|-------------------------|-------------------------|-----------------| +| VA_1 | National number | NDC+SN | '+' CC+NDC+SN | +| VA_2 | international number | CC+NDC+SN | '+' CC+NDC+SN | + +| TSS
TIP_TIR | TP_502_115 | Reference
subclause 5.2.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/2
AND 5.4/3 | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------------------------------------------------|---------------------------------------------------------------|--|----------------|------------|--------|---|---------|-------------|---|------------|---------------|---|-----------|-----|---|---------------|-------------------------|--|--| +| Test purpose
CONNECT Connected number Presentation restricted received, 200 OK (INVITE) is sent | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a CONNECT message containing a Connected number Information Element and the Presentation restriction indicator is set to 'Presentation restricted', a 200 OK INVITE is sent, a Privacy header contains the values "id" and "header" and "user". | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK: Privacy: id, header, user | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Connected number
Presentation restriction = Presentation restricted | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
INVITE→→ SETUP
180 Ringing←← ALERTING
200 OK INVITE←← CONNECT
ACK→→ CONNECT ACK
Apply post test routine
| | | | | Test equipment | End device | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | 200 OK INVITE | ← | ← CONNECT | ACK | → | → CONNECT ACK | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | ← CONNECT | | | | | | | | | | | | | | | | | | | | +| ACK | → | → CONNECT ACK | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|---|--------|----------|---|---|-------------|-------------|-------|-------|-------------------|-------------|---|---|-----| +| TSS
TIP_TIR | TP_502_116 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/2 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
A 'from-change' tag is contained in the initial INVITE request if a SETUP message was received

Ensure that on receipt of a SETUP message an INVITE message is sent to the terminating user and a 'from-change' tag is contained in the Supported header. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: Supported: from-change | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➠ ➠ INVITE
ALERTING ⬅ ⬅ 180 Ringing

CONNECT

⬅

⬅

200 OK INVITE
CONNECT ACK ➠ ➠ ACK
Apply post test routine
| | | | | End device | | Test equipment | SETUP | ➠ | ➠ | INVITE | ALERTING | ⬅ | ⬅ | 180 Ringing |
CONNECT |
⬅ |
⬅ |
200 OK INVITE | CONNECT ACK | ➠ | ➠ | ACK | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➠ | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | +|
CONNECT |
⬅ |
⬅ |
200 OK INVITE | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | ➠ | ➠ | ACK | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|--------------------------------------------------| +| TSS
TIP_TIR | TP_502_117 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.1.3/1 | +| Test purpose
The Userinfo of the P-Asserted-Identity is sent in a connected number. No Privacy header present or Privacy value 'none' 'from-change' tag not present in the 200 OK (INVITE).

Ensure that on receipt of a 200 OK INVITE where the 'from-change' tag is not present in the Supported header and no Privacy header is present, the Userinfo of the P-Asserted-Identity is in the form of a tel URI containing a E.164 number, a CONNECT message is sent to the calling user and a Connected number is present coded as described below. | | | | +| Connected number
Type of number
National number
sip: local-number-digits; phone-context=nat@hostportion; user=phone
International number
sip: global-number-digits@hostportion; user=phone
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = Network provided
Number digits derived from the userinfo of the P-Asserted-Identity.
In case where the global number and the country code is the same as the SUT or line is located, the country code is removed from the number of the Type of number is set to "national number." | | | | +| SIP header values
200 OK: P-Asserted-Identity | | | | +| DSS1 Parameter values
CONNECT: Connected number | | | | + +| Message flow | | | +|-------------------------|------------|-----------------| +| | End device | Test equipment | +| SETUP | → | → INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE | +| CONNECT ACK | → | → ACK | +| Apply post test routine | | | + +| | | | | +|----------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
TIP_TIR | TP_502_118 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | +|----------------|------------|----------------------------------------------------------|------------------------------------------------| + +**Test purpose** +*The Userinfo of the P-Asserted-Identity is sent in a connected number. No Privacy header present or Privacy value 'none' 'from-change' tag present in the 200 OK (INVITE).* + +Ensure that on receipt of a 200 OK INVITE where the 'from-change' tag is present in the Supported header and no Privacy header is present, the sending of the CONNECT message is held until the UPDATE is received. If the Userinfo in the From header in the UPDATE is in the form of a tel URI containing a E.164 number a CONNECT message is sent to the calling user and a Connected number is present coded as described below. + +Connected number + Type of number + National number + sip: local-number-digits; phone-context=nat@hostportion; user=phone + International number + sip: global-number-digits@hostportion; user=phone + Numbering plan identification = ISDN/Telephony numbering plan + Presentation indicator = **Presentation allowed** + Screening indicator = User provided, not verified + Number digits derived from the userinfo of the From header. + In case where the global number and the country code is the same as the SUT or line is located, the country code is removed from the number of the Type of number is set to "national number." + +**SIP header values** + UPDATE:From + +**DSSI Parameter values** + CONNECT: Connected number + +| Message flow | | | +|-------------------------|------------|-----------------| +| | End device | Test equipment | +| SETUP | → | → INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE | +| CONNECT ACK | → | → ACK | +| UPDATE | ← | | +| 200 OK UPDATE | → | | +| Apply post test routine | | | + +| TSS
TIP_TIR | TP_502_119 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|--|------------|--|----------------|-------|---|---|--------|----------|---|---|-------------|------|--|--|--|---------|---|---|---------------|-------------|---|---|-----| +|

Test purpose
The Userinfo of the From header is sent in a connected number. Privacy header value 'id' or 'header' 'from-change' tag not present in the 200 OK (INVITE).

Ensure that on receipt of a 200 OK INVITE where the 'from-change' tag is not present in the Supported header and a Privacy header is present, the priv-value set to 'id' or 'header' the Userinfo of the P-Asserted-Identity is in the form of a tel URI containing a E.164 number and a CONNECT message is sent to the calling user and a Connected number is present coded as described below.

Connected number
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Screening indicator = Network provided
Number digits derived from the userinfo of the P-Asserted-Identity.
Number digits not present

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
200 OK:
P-Asserted-Identity
Privacy: id,header,user

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
CONNECT: Connected number

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

End device Test equipment
SETUP ➔ ➔ INVITE
ALERTING ⬅ ⬅ 180 Ringing

CONNECT ⬅ ⬅ 200 OK INVITE
CONNECT ACK ➔ ➔ ACK

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 Ringing |
| | | | CONNECT | ⬅ | ⬅ | 200 OK INVITE | CONNECT ACK | ➔ | ➔ | ACK | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | ➔ | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
TIP_TIR | TP_502_120 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +|

Test purpose
The Userinfo of the From header is sent in a connected number. Privacy header value 'id' or 'header' 'from-change' tag present in the 200 OK (INVITE).

Ensure that on receipt of a 200 OK INVITE and the 'from-change' tag is present in the Supported header and a Privacy header is present the priv-value set to 'id' or 'header', the sending of the CONNECT message is held until the UPDATE is received. If the Userinfo in the From header in the UPDATE is in the form of a tel URI containing a E.164 number a CONNECT message is sent to the calling user and a Connected number is present coded as described below.

Connected number
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Screening indicator = Network provided
Number digits not present

| | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------|-----------------------|-----------------------|-------|---|---|--------|----------|---|---|-------------|--|--|---|---------------|--|--|---|-----|---------|---|---|--------|-------------|---|---|---------------|--|--------------------------------|--|--| +| SIP header values
UPDATE:From: anonymous
Privacy: id,header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Connected number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → → INVITE
ALERTING ← ← 180 Ringing
← 200 OK INVITE
→ ACK
CONNECT ← ← UPDATE
CONNECT ACK → → 200 OK UPDATE
Apply post test routine
| | End device | | Test equipment | SETUP | → | → | INVITE | ALERTING | ← | ← | 180 Ringing | | | ← | 200 OK INVITE | | | → | ACK | CONNECT | ← | ← | UPDATE | CONNECT ACK | → | → | 200 OK UPDATE | | Apply post test routine | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← | UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | → | → | 200 OK UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|---|--------|----------|---|---|-------------|--|--|---|---------------|--|--|---|-----|---------|---|---|--------|-------------|---|---|---------------|--|--------------------------------|--|--| +| TSS
TIP_TIR | TP_502_121 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The Userinfo of the From header is sent in a connected number. Privacy header value 'id' or 'header 'from-change' tag present in the 200 OK (INVITE). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of a 200 OK INVITE where the 'from-change' tag is present in the Supported header and a Privacy header is present, the priv-value set to 'id' or 'header', the sending of the CONNECT message is held until the UPDATE is received. If the Userinfo in the From header in the UPDATE is in the form of a tel URI containing a E.164 number, a CONNECT message is sent to the calling user and a Connected number is present coded as described below.

Connected number
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Screening indicator = Network provided
Number digits not present

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
UPDATE:From: anonymous
Privacy: id,header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Connected number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → → INVITE
ALERTING ← ← 180 Ringing
← 200 OK INVITE
→ ACK
CONNECT ← ← UPDATE
CONNECT ACK → → 200 OK UPDATE
Apply post test routine
| | | | | End device | | Test equipment | SETUP | → | → | INVITE | ALERTING | ← | ← | 180 Ringing | | | ← | 200 OK INVITE | | | → | ACK | CONNECT | ← | ← | UPDATE | CONNECT ACK | → | → | 200 OK UPDATE | | Apply post test routine | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← | UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | → | → | 200 OK UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|---|--------|----------|---|---|-------------|------|--|--|--|---------|---|---|---------------|-------------|---|---|-----| +| TSS
TIP_TIR | TP_502_122 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
No P-Asserted-Identity header and no Privacy id or header received, no Connected number is sent

Ensure that on receipt of a 200 OK INVITE where no P-Asserted-Identity and no Privacy value 'id' or 'header' is present, a CONNECT message is sent to the calling user and no Connected number is present.
NOTE – This is the indication, the calling user has not subscribed to the COLP service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ ➔ INVITE
ALERTING ⬅ ⬅ 180 Ringing

CONNECT ⬅ ⬅ 200 OK INVITE
CONNECT ACK ➔ ➔ ACK

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 Ringing |
| | | | CONNECT | ⬅ | ⬅ | 200 OK INVITE | CONNECT ACK | ➔ | ➔ | ACK | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | ➔ | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|---|--------|----------|---|---|-------------|------|--|--|--|---------|---|---|---------------|-------------|---|---|-----| +| TSS
TIP_TIR | TP_502_123 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
No P-Asserted-Identity header and no Privacy id or header received, no Connected number is sent

Ensure that on receipt of a 200 OK INVITE and no P-Asserted-Identity and no Privacy value 'id' or 'header' is present, a CONNECT message is sent to the calling user and no Connected number is present.
NOTE: This is the indication, the calling user has not subscribed to the COLP service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ ➔ INVITE
ALERTING ⬅ ⬅ 180 Ringing

CONNECT ⬅ ⬅ 200 OK INVITE
CONNECT ACK ➔ ➔ ACK

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 Ringing |
| | | | CONNECT | ⬅ | ⬅ | 200 OK INVITE | CONNECT ACK | ➔ | ➔ | ACK | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | ➔ | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|---|--------|----------|---|---|-------------|------|--|--|--|---------|---|---|---------------|-------------|---|---|-----| +| TSS
TIP_TIR | TP_502_124 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
'from-change' tag in 200 OK (INVITE) received, expiry of timer TTIR1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of a 200 OK INVITE and the 'from-change' tag is present in the Supported header and no Privacy header is present, timer TTIR1 is started and the CONNECT message is held. After expiry of TTIR1, the CONNECT message is sent, the Userinfo of the P-Asserted-Identity is mapped into the Connected number and coded as described below:

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Connected number
Type of number
National number
sip: local-number-digits; phone-context=nat@hostportion; user=phone
International number
sip: global-number-digits@hostportion; user=phone
Numbering plan identification = ISDN/Telephony numbering plan
Presentation indicator = Presentation allowed
Screening indicator = User provided, not verified
Number digits derived from the userinfo of the From header.
In case where the global number and the country code is the same as the SUT or line is located, the country code is removed from the number of the Type of number is set to "national number." | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Connected number | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ ➔ INVITE
ALERTING ← ← 180 Ringing

CONNECT ← ← 200 OK INVITE
CONNECT ACK ➔ ➔ ACK

Apply post test routine

| | | | | End device | | Test equipment | SETUP | ➔ | ➔ | INVITE | ALERTING | ← | ← | 180 Ringing |
| | | | CONNECT | ← | ← | 200 OK INVITE | CONNECT ACK | ➔ | ➔ | ACK | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | ➔ | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
TIP_TIR | TP_502_125 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | +| Test purpose
Several identities received in different responses. | | | | +|

Ensure that on receipt of several P-Asserted-Identity headers in different responses, the Connected number sent to the calling party is derived from the latest received P-Asserted header.

| | | | +| SIP header values | | | | +| 180: P-Asserted-Identity identity 1
200 OK: P-Asserted-Identity identity 2 | | | | +| DSS1 Parameter values | | | | +| CONNECT: Connected number identity 2 | | | | + +| Message flow | | | +|--------------------------------|-------------------|-----------------------| +| | End device | Test equipment | +| SETUP | → | → INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE | +| CONNECT ACK | → | → ACK | +| Apply post test routine | | | + +| TSS
TIP_TIR | TP_502_126 | Reference
subclause 5.2.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/3 | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|-----------------------|-------|---|----------|----------|---|---------------|---------|---|-----------------|-------------|---|-------|--------------------------------|--|--| +| Test purpose
Mapping of isub parameter in the UPDATE From header into Connected subaddress | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of several P-Asserted-Identity headers in different responses, the Connected number sent to the calling party is derived from the latest received P-Asserted header. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180: P-Asserted-Identity identity 1
200 OK: P-Asserted-Identity identity 2 | | | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values
CONNECT: Connected number identity 2 | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End deviceTest equipment
SETUP→→ INVITE
ALERTING←← 180 Ringing
CONNECT←← 200 OK INVITE
CONNECT ACK→→ ACK
Apply post test routine
| | | | | End device | Test equipment | SETUP | → | → INVITE | ALERTING | ← | ← 180 Ringing | CONNECT | ← | ← 200 OK INVITE | CONNECT ACK | → | → ACK | Apply post test routine | | | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → INVITE | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | +| CONNECT ACK | → | → ACK | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.5.3 Communication HOLD + +##### 7.2.5.3.1 Test purposes for POTS + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
HOLD | TP_503_101 | Reference
subclause B.4.2.2 and C.1.2.1 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 | +| Test purpose
Originating user sets the remote party on hold | | | | +| Ensure that when a ReINVITE or UPDATE request is received, the SDP description for the active media stream is set to a=sendonly, a 200 OK is sent the a line in the SDP is set to "recvonly". | | | | +| SIP header values
INVITE/UPDATE
SDP
a=sendonly

200 OK
SDP
a=recvonly | | | | + +| Message flow | | | +|------------------------------------|---|-------------------| +| Test equipment | | End device | +| A confirmed dialogue exists | | | +| CASE A | | | +| INVITE | → | | +| 200 OK INVITE | ← | | +| ACK | → | | +|
CASE B | | | +| UPDATE | → | | +| 200 OK UPDATE | ← | | +| Apply post test routine | | | + +| | | | | +|-------------|------------|--------------------------------------------------------------------|--------------------------------------| +| TSS
HOLD | TP_503_102 | Reference
subclause B.4.2.2 and C.1.2.1 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 | +|-------------|------------|--------------------------------------------------------------------|--------------------------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose

User resumes the remote party

Ensure that when the user is set on hold, upon receipt of a ReINVITE or UPDATE request, the SDP description for the held media stream is set to a=sendrecv, a 200 OK is sent and the a line in the SDP is set to “sendrecv”.

NOTE – sendrecv is the default value.

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

SIP header values

INVITE

SDP

a=sendrecv (or absent)


200 OK

SDP

a=sendrecv (or absent)

| +|--------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|------------------------------------|---|-------------------| +| Test equipment | | End device | +| A confirmed dialogue exists | | | +| CASE A | | | +| INVITE1 | → | | +| 200 OK INVITE1 | ← | | +| ACK | → | | +| | | | +| INVITE2 | → | | +| 200 OK INVITE2 | ← | | +| ACK | → | | +|
CASE B | | | +| UPDATE1 | → | | +| 200 OK UPDATE1 | ← | | +| | | | +| UPDATE2 | → | | +| 200 OK UPDATE3 | ← | | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|--------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|--|------------------------------------|--|------------|----------|--|--|-----------------|--|--|-------|--|--|--------------------------------|--| +| TSS
HOLD | TP_503_103 | Reference
subclause 5.3.1.4 of
[TS183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6 | | | | | | | | | | | | | | | | | | | +| Test purpose
User sets the remote party on hold

Ensure that when flash-hook notification from the MGC component is received a ReINVITE request is sent. The SDP description for the active media stream is set to a=sendonly. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
SDP
a=sendonly

200 OK
SDP
a=recvonly | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
A confirmed dialogue exists
flash-hook → INVITE
← 200 OK INVITE
→ ACK
Apply post test routine
| | | | End device | | Test equipment | | A confirmed dialogue exists | | flash-hook | → INVITE | | | ← 200 OK INVITE | | | → ACK | | | Apply post test routine | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| | A confirmed dialogue exists | | | | | | | | | | | | | | | | | | | | | +| flash-hook | → INVITE | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-----------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|--|------------------------------------|--|------------|-----------|--|--|------------------|--|--|-------|--|----------------|---------------|--|--|------------------|--|--|-------|--|--|--------------------------------|--| +| TSS
HOLD | TP_503_104 | Reference
subclause 5.3.1.4 of [TS183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
User resumes the remote held party

Ensure that if the remote party is on hold when flash-hook notification from the MGC component is received a ReINVITE request is sent. The SDP description for the active media stream is set to a=sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE2
SDP
a=sendrecv

200 OK2
SDP
a=sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
A confirmed dialogue exists
flash-hook → INVITE1
← 200 OK INVITE1
→ ACK

flash-hook

→ INVITE2
← 200 OK INVITE2
→ ACK
Apply post test routine
| | | | End device | | Test equipment | | A confirmed dialogue exists | | flash-hook | → INVITE1 | | | ← 200 OK INVITE1 | | | → ACK | |
flash-hook |
→ INVITE2 | | | ← 200 OK INVITE2 | | | → ACK | | | Apply post test routine | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A confirmed dialogue exists | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| flash-hook | → INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
flash-hook |
→ INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← 200 OK INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +##### 7.2.5.3.2 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------|----------------------|-----------------------|--|--|-------------------|--------|---|--|---|-------|-------------|---|--|---|----------|---------------|---|--|---|---------|-----|---|--|--|--|--|--|--|--|--|-------------------|---|--|---|----------------------|-----------------|---|--|--|--|-----|---|--|--|--| +| TSS
HOLD | TP_503_201 | Reference
subclause 5.2.1.1.1 of [ETSI TS
183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
HOLD requested by the calling party in an reINVITE request (a=sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that the calling party is able to set the communication on HOLD. The received reINVITE contains an a attribute in the SDP set to 'sendonly'. The SUT sends a 200 OK (INVITE) containing an a attribute in the SDP set to 'recvonly'. A DSS1 NOTIFY message is sent to the terminating user equipment and the Notification indicator information element is set to 'Remote hold'.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: SDP a=sendonly
200 OK (INVITE): SDP a=recvonly | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Notification indicator = Remote hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
183 Ringing ⬅ ⬅ ALERTING
200 OK INVITE ⬅ ⬅ CONNECT
ACK ➔
 
INVITE (sendonly) ➔ ➔ NOTIFY (Remote hold)
200 OK (INVITE) ⬅
ACK ➔

Apply post test routine

| | | | | Test equipment | | | End device | INVITE | ➔ | | ➔ | SETUP | 183 Ringing | ⬅ | | ⬅ | ALERTING | 200 OK INVITE | ⬅ | | ⬅ | CONNECT | ACK | ➔ | | | | | | | | | INVITE (sendonly) | ➔ | | ➔ | NOTIFY (Remote hold) | 200 OK (INVITE) | ⬅ | | | | ACK | ➔ | | | | +| | Test equipment | | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 183 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | | ⬅ | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE (sendonly) | ➔ | | ➔ | NOTIFY (Remote hold) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_202 | Reference
subclause 5.2.1.1.1 of [ETSI TS
183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +| Test purpose
HOLD requested by the calling party in an UPDATE request (a=sendonly) | | | | +|

Ensure that the calling party is able to set the communication on HOLD. The received UPDATE contains an a attribute in the SDP set to 'sendonly'. The SUT sends a 200 OK (UPDATE) containing an a attribute in the SDP set to 'recvonly'. A DSS1 NOTIFY message is sent to the terminating user equipment and the Notification indicator information element is set to 'Remote hold'.

| | | | +| SIP header values
UPDATE: SDP a=sendonly
200 OK (UPDATE): SDP a=recvonly | | | | +| DSS1 Parameter values
NOTIFY: Notification indicator = Remote hold | | | | + +| Message flow | | | +|--------------------------------|-----------------------|------------------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| UPDATE (sendonly) | → | → NOTIFY (Remote hold) | +| 200 OK (UPDATE) | ← | | +| Apply post test routine | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_203 | Reference
subclause 5.2.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +| Test purpose
HOLD requested by the calling party in an reINVITE request (a=inactive) | | | | +| Ensure that the calling party is able to set the communication on HOLD. The received reINVITE contains an a attribute in the SDP set to 'inactive'. The SUT sends a 200 OK (INVITE) containing an a attribute in the SDP set to 'inactive'. A DSS1 NOTIFY message is sent to the terminating user equipment and the Notification indicator information element is set to 'Remote hold'. The communication was previously set on HOLD by the called party. | | | | +| SIP header values
INVITE: SDP a=inactive
200 OK (INVITE): SDP a=inactive | | | | +| DSS1 Parameter values
NOTIFY: Notification indicator = Remote hold | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| 200 OK INVITE | ← | ← | CONNECT | +| ACK | → | | | +| | | ← | NOTIFY (Remote hold) | +| CASE A | | | | +| INVITE (sendonly) | ← | | | +| 200 OK INVITE | → | | | +| ACK | ← | | | +| CASE B | | | | +| UPDATE (sendonly) | ← | | | +| 200 OK (UPDATE) | → | | | +| INVITE (inactive) | → | → | NOTIFY (Remote hold) | +| 200 OK INVITE | ← | | | +| ACK | → | | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|---------------|---|---|---------|-----|---|--|--|--|--|---|----------------------|---------------|--|--|--|-------------------|---|--|--|---------------|---|--|--|-----|---|--|--|---------------|--|--|--|-------------------|---|--|--|-----------------|---|--|--|-----------------------|-------|-------|--------------------------|-----------------|---|--|--| +| TSS
HOLD | TP_503_204 | Reference
subclause 5.2.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
HOLD requested by the calling party in an UPDATE request (a=inactive)

Ensure that the calling party is able to set the communication on HOLD. The received UPDATE contains an a attribute in the SDP set to 'inactive'. The SUT sends a 200 OK (UPDATE) containing an a attribute in the SDP set to 'inactive'. A DSS1 NOTIFY message is sent to the terminating user equipment and the Notification indicator information element is set to 'Remote hold'. The communication was previously set on HOLD by the called party.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
UPDATE: SDP a=inactive
200 OK (UPDATE): SDP a=inactive | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Notification indicator = Remote hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
200 OK INVITE ⬅ ⬅ CONNECT
ACK ➔
⬅ NOTIFY (Remote hold)
CASE A
INVITE (sendonly) ⬅
200 OK INVITE ➔
ACK ⬅
CASE B
UPDATE (sendonly) ⬅
200 OK (UPDATE) ➔

UPDATE (inactive)

➔

➔

NOTIFY (Remote hold)
200 OK (UPDATE) ⬅
Apply post test routine
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 180 Ringing | ⬅ | ⬅ | ALERTING | 200 OK INVITE | ⬅ | ⬅ | CONNECT | ACK | ➔ | | | | | ⬅ | NOTIFY (Remote hold) | CASE A | | | | INVITE (sendonly) | ⬅ | | | 200 OK INVITE | ➔ | | | ACK | ⬅ | | | CASE B | | | | UPDATE (sendonly) | ⬅ | | | 200 OK (UPDATE) | ➔ | | |
UPDATE (inactive) |
➔ |
➔ |
NOTIFY (Remote hold) | 200 OK (UPDATE) | ⬅ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | ⬅ | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | NOTIFY (Remote hold) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE (sendonly) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UPDATE (sendonly) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (UPDATE) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
UPDATE (inactive) |
➔ |
➔ |
NOTIFY (Remote hold) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (UPDATE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_205 | Reference
subclause 5.2.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +| Test purpose
RETRIEVE requested by the calling party in an INVITE request

Ensure that the calling party is able to retrieve an earlier communication previously set on HOLD. The received INVITE contains an attribute in the SDP set to 'sendrecv'. The SUT sends a 200 OK (UPDATE) containing an a attribute in the SDP set to 'sendrecv'. A DSS1 NOTIFY message is sent to the terminating user equipment and the Notification indicator information element is set to 'Remote retrieval'.

| | | | +| SIP header values
INVITE: SDP a=sendrecv
200 OK (INVITE): SDP a=sendrecv | | | | + +| | | | +|---------------------------------------------------|-----------------------|-----------------------------| +| DSSI Parameter values | | | +| NOTIFY: Notification indicator = Remote retrieval | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| INVITE (sendonly) | → | → NOTIFY (Remote hold) | +| 200 OK INVITE | ← | | +| ACK | → | | +| INVITE (sendrecv) | → | → NOTIFY (Remote retrieval) | +| 200 OK INVITE | ← | | +| ACK | → | | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_206 | Reference
subclause 5.2.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +|-------------|------------|----------------------------------------------------------|------------------------------------------------| + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------| +| Test purpose | | | +| RETRIEVE requested by the calling party in an UPDATE request | | | +| Ensure that the calling party is able to retrieve an earlier communication previously set on HOLD. The received UPDATE contains an attribute in the SDP set to 'sendrecv'. The SUT sends a 200 OK (INVITE) containing an a attribute in the SDP set to 'sendrecv'. A DSSI NOTIFY message is sent to the terminating user equipment and the Notification indicator information element is set to 'Remote retrieval'. | | | +| SIP header values | | | +| UPDATE: SDP a=sendrecv
200 OK (UPDATE): SDP a=sendrecv | | | +| DSSI Parameter values | | | +| NOTIFY: Notification indicator = Remote retrieval | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| UPDATE (sendonly) | → | → NOTIFY (Remote hold) | +| 200 OK (UPDATE) | ← | | +| UPDATE (sendrecv) | → | → NOTIFY (Remote retrieval) | +| 200 OK (UPDATE) | ← | | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|---------------|---|---|---------|-----|---|--|--|--|--|---|------|---------------|--|--|--|-------------------|---|--|--|---------------|---|--|--|-----|---|--|--|---------------|--|--|--|-------------------|---|--|--|-----------------|---|--|--| +| TSS
HOLD | TP_503_207 | Reference
subclause 5.2.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
HOLD requested by the called party a reINVITE or UPDATE is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the called party is able to set the communication on HOLD. A HOLD message is received from the called party. The SUT sends a reINVITE request or an UPDATE request and the a attribute in the SDP is set to 'sendonly'. A 200 OK (INVITE) or a 200 OK (UPDATE) is received and the a attribute in the SDP is set to 'recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE/UPDATE: SDP a=sendonly
200 OK (INVITE/UPDATE): SDP a=recvonly | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
HOLD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
200 OK INVITE ⬅ ⬅ CONNECT
ACK ➔
⬅ HOLD
CASE A
INVITE (sendonly) ⬅
200 OK INVITE ➔
ACK ⬅
CASE B
UPDATE (sendonly) ⬅
200 OK (UPDATE) ➔
Apply post test routine
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 180 Ringing | ⬅ | ⬅ | ALERTING | 200 OK INVITE | ⬅ | ⬅ | CONNECT | ACK | ➔ | | | | | ⬅ | HOLD | CASE A | | | | INVITE (sendonly) | ⬅ | | | 200 OK INVITE | ➔ | | | ACK | ⬅ | | | CASE B | | | | UPDATE (sendonly) | ⬅ | | | 200 OK (UPDATE) | ➔ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | ⬅ | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | HOLD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE (sendonly) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UPDATE (sendonly) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (UPDATE) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
HOLD | TP_503_208 | Reference
subclause 5.2.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4
AND 5.1.3/1 | +| Test purpose
HOLD requested by the called party in a private network | | | | +| Ensure that the called party is able to set the communication on HOLD. A HOLD message is received from the called party. The SUT sends a reINVITE request or an UPDATE request and the a attribute in the SDP is set to 'sendonly'. A 200 OK (INVITE) or a 200 OK (UPDATE) is received and the a attribute in the SDP is set to 'recvonly'. | | | | +| SIP header values
INVITE/UPDATE: SDP a=sendonly
200 OK (INVITE/UPDATE): SDP a=recvonly | | | | +| DSS1 Parameter values
HOLD | | | | + +| Message flow | | | +|--------------------------------|-----------------------|------------------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| | | ← NOTIFY (Remote hold) | +| CASE A | | | +| INVITE (sendonly) | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| CASE B | | | +| UPDATE (sendonly) | ← | | +| 200 OK (UPDATE) | → | | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
HOLD | TP_503_209 | Reference
subclause 5.2.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4
AND 5.1.3/1 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +**Test purpose** +*HOLD requested by the called party in a private network* + +Ensure that the called party in a private network is able to set a communication on HOLD. A NOTIFY message is received and the Notification indicator information element is set to 'Remote hold'. A reINVITE request or an UPDATE request is sent and the a attribute in the SDP is set to 'inactive', A 200 OK (INVITE) or 200 OK (UPDATE) is received and the a attribute in the SDP is set to 'inactive')if the session was previously set on HOLD by the calling user. + +**SIP header values** + INVITE/UPDATE: SDP a= sendrecv + 200 OK (INVITE/UPDATE): SDP a= sendrecv + +**DSS1 Parameter values** + NOTIFY: Notification indicator = Remote retrieval + +| Message flow | | | +|---------------------|-----------------------|------------------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK INVITE | ← | ← CONNECT | +| ACK | → | | +| | | ← NOTIFY (Remote hold) | +| CASE A | | | +| INVITE (sendonly) | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | + +| | | +|--------------------------------|-----------------------------| +| CASE B | | +| UPDATE (sendonly) | ← | +| 200 OK (UPDATE) | → | +| CASE A | ← NOTIFY (remote retrieval) | +| INVITE (sendrecv) | ← | +| 200 OK INVITE | → | +| ACK | ← | +| CASE B | | +| UPDATE (sendrecv) | ← | +| 200 OK (UPDATE) | → | +| Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------|------------------------------------------------|--|-----------------------|-----------------------|-------|---|----------------------------------------------------------------------|----------|---|---------------|---------|---|--------------------------|--------------------------|-------|----------------------------------------------------|--------------------------------|--|--| +| TSS
HOLD | TP_503_210 | Reference
subclause 5.2.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | | | | | | | | | | | | | | | | | | | +| Test purpose
HOLD requested by the called party. INVITE was received | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT is able to send a DSS1 NOTIFY message and the Notification indicator information element is set to 'Remote hold' if an INVITE request was received and the a attribute in the SDP is set to 'sendonly'. A 200 OK (INVITE) is send and the a attribute in the SDP is set to 'recvonly'. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: SDP a=sendonly
200 OK (INVITE) SDP a=recvonly | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Remote hold | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← ← 180 Ringing
CONNECT ← ← 200 OK INVITE
→ ACK

NOTIFY (Remote hold)

←

← INVITE(sendonly)
→ 200 OK INVITE
← ACK
Apply post test routine
| | | | | Test equipment | Test equipment | SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | ALERTING | ← | ← 180 Ringing | CONNECT | ← | ← 200 OK INVITE
→ ACK |
NOTIFY (Remote hold) |
← |
← INVITE(sendonly)
→ 200 OK INVITE
← ACK | Apply post test routine | | | +| | Test equipment | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | | | | | | | | | | | | | | | | | | | | +|
NOTIFY (Remote hold) |
← |
← INVITE(sendonly)
→ 200 OK INVITE
← ACK | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-----------------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|---|---|-------------|---------|---|---|---------------|--|--|---|-----|--------------------------|-------|-------|-----------------------|--|--|---|-----------------|--------------------------------|--|--|--| +| TSS
HOLD | TP_503_210 | Reference
subclause 5.2.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
HOLD requested by the called party. UPDATE was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT is able to send a DSS1 NOTIFY message and the Notification indicator information element is set to 'Remote hold' if an UPDATE request was received and the a attribute in the SDP is set to 'sendonly'. A 200 OK (UPDATE) is send and the a attribute in the SDP is set to 'recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: SDP a=sendonly
200 OK (INVITE) SDP a=recvonly | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Remote hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ ⬅ 180 Ringing
CONNECT ⬅ ⬅ 200 OK INVITE
➔ ACK

NOTIFY (Remote hold)

⬅

⬅

UPDATE (sendonly)
➔ 200 OK (UPDATE)
Apply post test routine
| | | | | Test equipment | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 Ringing | CONNECT | ⬅ | ⬅ | 200 OK INVITE | | | ➔ | ACK |
NOTIFY (Remote hold) |
⬅ |
⬅ |
UPDATE (sendonly) | | | ➔ | 200 OK (UPDATE) | Apply post test routine | | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
NOTIFY (Remote hold) |
⬅ |
⬅ |
UPDATE (sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | 200 OK (UPDATE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_211 | Reference
subclause 5.2.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +| Test purpose
HOLD requested by the called party. INVITE was received | | | | +| Ensure that the SUT is able to send a DSS1 NOTIFY message and the Notification indicator information element is set to 'Remote hold' if an INVITE request was received and the a attribute in the SDP is set to 'inactive'. A 200 OK (INVITE) is send and the a attribute in the SDP is set to 'inactive' if the session was previously set on HOLD by the called user. | | | | +| SIP header values
INVITE: SDP a=inactive
200 OK (INVITE) SDP a=inactive | | | | +| DSS1 Parameter values
NOTIFY: Remote hold | | | | + +![](6347ebb7bc58aba4272fc340a410bd97_img.jpg) + +| Message flow | | | +|-------------------------|----------------|----------------------------------------------------------------------| +| | Test equipment | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| HOLD | → | | +| CASE A | | → INVITE(sendonly)
← 200 OK INVITE
→ ACK | +| CASE B | | → UPDATE (sendonly)
← 200 OK (UPDATE) | +| NOTIFY (Remote hold) | ← | ← INVITE(inactive)
→ 200 OK INVITE
← ACK | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_212 | Reference
subclause 5.2.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +| Test purpose
HOLD requested by the called party. UPDATE was received

Ensure that the SUT is able to send a DSS1 NOTIFY message and the Notification indicator information element is set to 'Remote hold' if an UPDATE request was received and the a attribute in the SDP is set to 'inactive'. A 200 OK (UPDATE) is send and the a attribute in the SDP is set to 'inactive' if the session was previously set on HOLD by the called user. | | | | +| SIP header values
UPDATE: SDP a=inactive
200 OK (UPDATE) SDP a=inactive | | | | +| DSS1 Parameter values
NOTIFY: Remote hold | | | | + +![](a5bca582e073ba0d94ca0a4fbc3ca3e5_img.jpg) + +| Message flow | | | +|-------------------------|----------------|----------------------------------------------------------------------| +| | Test equipment | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| HOLD | → | | +| CASE A | | → INVITE(sendonly)
← 200 OK INVITE
→ ACK | +| CASE B | | → UPDATE (sendonly)
← 200 OK (UPDATE) | +| NOTIFY (Remote hold) | ← | ← UPDATE (inactive)
→ 200 OK (UPDATE) | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_213 | Reference
subclause 5.2.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +| Test purpose
Retrieve requested by the called party. INVITE was received

Ensure that the SUT is able to send a DSS1 NOTIFY message and the Notification indicator information element is set to 'Remote retrieval' if an INVITE request was received and the a attribute in the SDP is set to 'sendrecv'. A 200 OK (INVITE) is send and the a attribute in the SDP is set to 'sendrecv'. | | | | +| SIP header values
INVITE: SDP a=sendrecv
200 OK (INVITE) SDP a=sendrecv | | | | +| DSS1 Parameter values
NOTIFY: Remote retrieval | | | | + +| Message flow | | | +|--------------------------------|-----------------------|----------------------------------------------------------------------| +| | Test equipment | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| NOTIFY(Remote hold) | ← | ← INVITE(sendonly)
→ 200 OK INVITE
← ACK | +| NOTIFY (Remote retrieval) | ← | ← INVITE(sendonly)
→ 200 OK INVITE
← ACK | +| Apply post test routine | | | + +| TSS
HOLD | TP_503_214 | Reference
subclause 5.2.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------|------------------------------------------------| +| Test purpose
Retrieve requested by the called party. UPDATE was received | | | | +| Ensure that the SUT is able to send a DSS1 NOTIFY message and the Notification indicator information element is set to 'Remote retrieval' if an UPDATE request was received and the a attribute in the SDP is set to 'sendrecv'. A 200 OK (UPDATE) is send and the a attribute in the SDP is set to 'sendrecv'. | | | | +| SIP header values
UPDATE: SDP a=sendrecv
200 OK (UPDATE) SDP a=sendrecv | | | | +| DSS1 Parameter values
NOTIFY: Remote retrieval | | | | +| Message flow | | | | +| | Test equipment | | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | | +| ALERTING | ← | ← 180 Ringing | | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | | +| NOTIFY(Remote hold) | ← | ← UPDATE (sendonly)
→ 200 OK (UPDATE) | | +| NOTIFY (Remote retrieval) | ← | ← UPDATE (sendrecv)
→ 200 OK (UPDATE) | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-----------------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|---|---|-------------|---------|---|---|---------------|--|--|---|-----|----------|-------|--|--|---------------|--|---|------------------|--|--|---|---------------|--|--|---|-----|-------------------|--|-------|-----------------------|--|--|---|-----------------| +| TSS
HOLD | TP_503_215 | Reference
subclause 5.2.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
HOLD requested by the calling party

Ensure that the SUT is able to send a reINVITE request or UPDATE request and the a attribute in the SDP is set to 'sendonly' if a DSS1 HOLD message was received. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE/UPDATE: SDP a=sendonly
200 OK (INVITE/UPDATE) SDP a=recvonly | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ ⬅ 180 Ringing
CONNECT ⬅ ⬅ 200 OK INVITE
➔ ACK

HOLD

➔
CASE A ➔ INVITE(sendonly)
⬅ 200 OK INVITE
➔ ACK

CASE B

➔

UPDATE (sendonly)
⬅ 200 OK (UPDATE)

Apply post test routine

| | | | | Test equipment | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 Ringing | CONNECT | ⬅ | ⬅ | 200 OK INVITE | | | ➔ | ACK |
HOLD |
➔ | | | CASE A | | ➔ | INVITE(sendonly) | | | ⬅ | 200 OK INVITE | | | ➔ | ACK |
CASE B | |
➔ |
UPDATE (sendonly) | | | ⬅ | 200 OK (UPDATE) | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ⬅ | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
HOLD |
➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | ➔ | INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | |
➔ |
UPDATE (sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK (UPDATE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
HOLD | TP_503_216 | Reference
subclause 5.2.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4 | +| Test purpose
Retrieve requested by the calling party

Ensure that the SUT is able to send a reINVITE request or UPDATE request and the a attribute in the SDP is set to 'sendrecv' if a DSS1 RETRIVE message was received. | | | | +| SIP header values
INVITE/UPDATE: SDP a=sendrecv
200 OK (INVITE/UPDATE) SDP a=sendrecv | | | | +| DSS1 Parameter values | | | | + +![](1b683c1801ad8e24cf113cede25b36f0_img.jpg) + +| Message flow | | | +|-------------------------|----------------|----------------------------------------------------------------------| +| | Test equipment | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| HOLD | → | | +| CASE A | | → INVITE(sendonly)
← 200 OK INVITE
→ ACK | +| CASE B | | → UPDATE (sendonly)
← 200 OK (UPDATE) | +| RETRIVE | → | | +| CASE A | | → INVITE(sendrecv)
← 200 OK INVITE
→ ACK | +| CASE B | | → UPDATE (sendrecv)
← 200 OK (UPDATE) | +| Apply post test routine | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
HOLD | TP_503_217 | Reference
subclause 5.2.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4
AND 5.1.3/1 | +| Test purpose
HOLD requested by the calling party

Ensure that the SUT is able to send a reINVITE request or UPDATE request and the a attribute in the SDP is set to 'sendonly' if a DSS1 NOTIFY message was received from an user in a private network and the Notification description is set to 'Remote Hold'. | | | | +| SIP header values
INVITE/UPDATE: SDP a=sendonly
200 OK (INVITE/UPDATE) SDP a=recvonly | | | | +| DSS1 Parameter values
NOTIFY: Remote Hold | | | | + +| Message flow | | | +|--------------------------------|-----------------------|----------------------------------------------------------------------| +| | Test equipment | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| NOTIFY (Remote Hold) | → | | +| CASE A | | → INVITE(sendonly)
← 200 OK INVITE
→ ACK | +| CASE B | | → UPDATE (sendonly)
← 200 OK (UPDATE) | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------|---------------------------------------------------------------| +| TSS
HOLD | TP_503_218 | Reference
subclause 5.2.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4
AND 5.1.3/1 | +| Test purpose
HOLD requested by the calling party | | | | +| Ensure that the SUT is able to send a reINVITE request or UPDATE request and the a attribute in the SDP is set to 'inactive' if a DSS1 NOTIFY message was received from an user in a private network and the Notification description is set to 'Remote Hold'. | | | | +| SIP header values
INVITE/UPDATE: SDP a=sendonly
200 OK (INVITE/UPDATE) SDP a=recvonly | | | | +| DSS1 Parameter values
NOTIFY: Remote Hold | | | | +| Message flow | | | | +| | Test equipment | | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | | +| ALERTING | ← | ← 180 Ringing | | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | | +| NOTIFY (Remote Hold) | → | | | + +| | | +|--------------------------------|------------------------------------------------| +| CASE A | → INVITE(sendonly)
← 200 OK INVITE
→ ACK | +| CASE B | → UPDATE (sendonly)
← 200 OK (UPDATE) | +| Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------|-----------------------|--|-----------------------|-------|---|----------|--|--|-------------------------------------|--|--|-------|--|--|----------|----------|---|---------------|---------|---|-----------------|--|--|-------|--------------------------|-------|--|---------------|--|--------------------|--|--|-----------------|--|--|-------|-------------------|--|-------------------------|--|--|-------------------|-------------------------------|-------|--|---------------|--|--------------------|--|--|-----------------|--|--|-------| +| TSS
HOLD | TP_503_219 | Reference
subclause 5.2.1.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/4
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Retrieve requested by the calling party. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT is able to retrive the held session if a DSS1 NOTIFY message is received and the Notification description is set to 'Remote retrieval'. A SIP reINVITE or UPDATE request is sent to the called user and the a attribute of the SDP is set to 'sendrecv'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE/UPDATE: SDP a= sendrecv
200 OK (INVITE/UPDATE) SDP a= sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Remote retrieval | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← ← 180 Ringing
CONNECT ← ← 200 OK INVITE
→ ACK

NOTIFY (Remote Hold)

→
CASE A → INVITE(sendonly)
← 200 OK INVITE
→ ACK

CASE B

→ UPDATE (sendonly)
← 200 OK (UPDATE)

NOTIFY (remote retrieval)

→
CASE A → INVITE(sendrecv)
← 200 OK INVITE
→ ACK
| | | | Test equipment | | Test equipment | SETUP | → | → INVITE | | | ← 407 Proxy Authentication Required | | | → ACK | | | → INVITE | ALERTING | ← | ← 180 Ringing | CONNECT | ← | ← 200 OK INVITE | | | → ACK |
NOTIFY (Remote Hold) |
→ | | CASE A | | → INVITE(sendonly) | | | ← 200 OK INVITE | | | → ACK |
CASE B | |
→ UPDATE (sendonly) | | | ← 200 OK (UPDATE) |
NOTIFY (remote retrieval) |
→ | | CASE A | | → INVITE(sendrecv) | | | ← 200 OK INVITE | | | → ACK | +| Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
NOTIFY (Remote Hold) |
→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | → INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B | |
→ UPDATE (sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 200 OK (UPDATE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
NOTIFY (remote retrieval) |
→ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | → INVITE(sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | +|--------------------------------|------------------------------------------| +| CASE B | ➔ UPDATE (sendrecv)
⬅ 200 OK (UPDATE) | +| Apply post test routine | | + +#### 7.2.5.4 Communication Diversion (CDIV) + +##### 7.2.5.4.1 Test purposes for POTS + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------|------------------------------------------------|--|-----------------------|-------------------|--------|---|--|-------------|---|----------------------------------------------| +| TSS
CDIV | TP_504_101 | Reference
clause C.7 and D.2 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/7 | | | | | | | | | | +| Test purpose
First call line identity | | | | | | | | | | | | | +| Ensure that Call forwarding information received in an INVITE request ("history-info" header) is used by the SUT to generate the appropriate Call Setup message to be delivered to the called terminal, using the ITU-T H.248 andisp package. | | | | | | | | | | | | | +| SIP header values
INVITE:
History-Info: [;user=phone>];index=1, [;user=phone>];index=1.1 | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔
180 Ringing ⬅ Ringing, display call forwarding information
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | | 180 Ringing | ⬅ | Ringing, display call forwarding information | +| | Test equipment | End device | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | +| 180 Ringing | ⬅ | Ringing, display call forwarding information | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------|--------------------------------------|--|-------------------|-----------------------|----------|--|--|---------------------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------| +| TSS
CDIV | TP_504_102 | Reference
clause C.7 of [ETSI TS183 043] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | +| Test purpose
Activate, deactivate or interrogate the call forwarding service | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT is able to send an INVITE request to activate, deactivate or interrogate the call forwarding service. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Request-Line: PX SC (SR SI) SX@pes-scc.operator.com | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Off hook
Dial service code command ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
Apply post test routine
| | | | | End device | Test equipment | Off hook | | | Dial service code command | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | +| Dial service code command | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | + +##### 7.2.5.4.2 Test purposes for ISDN + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|-----------------------------------|-----------------------|--|--|-----------------------|-------|--|---|---|--------|--|--|--|---|-----------------------------------|--|--|--|---|-----|--|--|--|---|--------|--------|--|---|---|----------------------------|--------------------------------|--|--|--|--| +| TSS
CDIV | TP_504_201 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
181 received, a NOTIFY is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 181 Call Being Forwarded provisional response, a NOTIFY message is sent to the DSS1 User equipment. The Notification indicator is set to 'Call is diverting'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Notification indicator
Call is diverting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
NOTIFY ⬅ ⬅ 181 (Call Being Forwarded)
Apply post test routine
| | | | | Test equipment | | | Test equipment | SETUP | | ➔ | ➔ | INVITE | | | | ⬅ | 407 Proxy Authentication Required | | | | ➔ | ACK | | | | ➔ | INVITE | NOTIFY | | ⬅ | ⬅ | 181 (Call Being Forwarded) | Apply post test routine | | | | | +| | Test equipment | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | | ⬅ | ⬅ | 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|-----------------------------------|-----------------------|--|--|-----------------------|-------|--|---|---|--------|--|--|--|---|-----------------------------------|--|--|--|---|-----|--|--|--|---|--------|-----------------|--|---|---|------------------------|----------|--|---|---|----------------------------|--------------------------------|--|--|--|--| +| TSS
CDIV | TP_504_202 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
181 received, a PROGRESS is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 181 Call Being Forwarded provisional response where a 183 (Session Progress) containing a P-Early-Media header authorizing early media was previously received, a PROGRESS message is sent to the DSS1 User equipment. The Notification indicator is set to 'Call is diverting'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Notification indicator
Call is diverting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
CALL PROCEEDING ⬅ ⬅ 183 (Session Progress)
PROGRESS ⬅ ⬅ 181 (Call Being Forwarded)
Apply post test routine
| | | | | Test equipment | | | Test equipment | SETUP | | ➔ | ➔ | INVITE | | | | ⬅ | 407 Proxy Authentication Required | | | | ➔ | ACK | | | | ➔ | INVITE | CALL PROCEEDING | | ⬅ | ⬅ | 183 (Session Progress) | PROGRESS | | ⬅ | ⬅ | 181 (Call Being Forwarded) | Apply post test routine | | | | | +| | Test equipment | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CALL PROCEEDING | | ⬅ | ⬅ | 183 (Session Progress) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | | ⬅ | ⬅ | 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-----------------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|---|---|---------------|----------|---|---|----------------------------|--------------------------------|--|--|--| +| TSS
CDIV | TP_504_203 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
181 received, a PROGRESS is sent

Ensure that on receipt of a 181 Call Being Forwarded provisional response where a 180 (Ringing) was previously received, a PROGRESS message is sent to the DSS1 User equipment. The Notification indicator is set to 'Call is diverting'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Notification indicator
Call is diverting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ ⬅ 180 (Ringing)
PROGRESS ⬅ ⬅ 181 (Call Being Forwarded)
Apply post test routine
| | | | | Test equipment | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 (Ringing) | PROGRESS | ⬅ | ⬅ | 181 (Call Being Forwarded) | Apply post test routine | | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | ⬅ | 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-----------------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|---|---|---------------|----------|---|---|----------------------------|--------------------------------|--|--|--| +| TSS
CDIV | TP_504_204 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Subsequent diversion cause 487 and 408, a notification is sent

Ensure that on receipt of a subsequent 181 provisional response indicating a subsequent diversion, only the cause parameter value 487 (Deflection during alerting) or 408 (No reply) in the History-Info header, the notification 'Call is diverting' is sent to the DSS1 User equipment. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
181: History-Info: ; index=1,
; index=1.1
or
; index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Notification indicator
Call is diverting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ ⬅ 180 (Ringing)
PROGRESS ⬅ ⬅ 181 (Call Being Forwarded)
Apply post test routine
| | | | | Test equipment | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 (Ringing) | PROGRESS | ⬅ | ⬅ | 181 (Call Being Forwarded) | Apply post test routine | | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | ⬅ | 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------|------------------------------------------------|--|-----------------------|-----------------------|-------|---|----------------------------------------------------------------------|----------|---|-----------------|--------|---|------------------------------------------------------------------| +| TSS
CDIV | TP_504_205 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | +| Test purpose
Subsequent diversion cause not equal to 487 and 408, no notification is sent

Ensure that on receipt of a subsequent 181 provisional response indicating a subsequent diversion no notification 'Call is diverting' is sent to the DSS1 User equipment if the cause parameter value other than 487 (Deflection during alerting) or 408 (No reply) in the History-Info header as indicated in Table 7.2.5.4.2-1. | | | | | | | | | | | | | | | | +| SIP header values
181 2: History-Info:
; index=1, ; index=1.1 | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Notification indicator
Call is diverting | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
ALERTING ← ← 180 (Ringing)
NOTIFY ← ← 181 (Call Being Forwarded) 1
← 181 (Call Being Forwarded) 2
Apply post test routine
| | | | | Test equipment | Test equipment | SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | ALERTING | ← | ← 180 (Ringing) | NOTIFY | ← | ← 181 (Call Being Forwarded) 1
← 181 (Call Being Forwarded) 2 | +| | Test equipment | Test equipment | | | | | | | | | | | | | | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | | | | | | | | | | | | | | +| ALERTING | ← | ← 180 (Ringing) | | | | | | | | | | | | | | +| NOTIFY | ← | ← 181 (Call Being Forwarded) 1
← 181 (Call Being Forwarded) 2 | | | | | | | | | | | | | | + +**Table 7.2.5.4.2-1 – Cause values not sent to the DSS1 UE** + +| Reason | Value | +|-----------|-------| +| Reason_01 | 486 | +| Reason_02 | 302 | +| Reason_03 | 480 | +| Reason_04 | 404 | +| Reason_05 | 503 | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-----------------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--------|---|---|----------------------------|--|--------------------------------|--|--| +| TSS
CDIV | TP_504_206 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
181 received. Mapping of latest History-Info entry into the Redirection number if no Privacy value is present in the entry

Ensure that on receipt of a 181 (Call Being Forwarded) provisional response where a History-Info header is present and no Privacy header is present in the latest hist-entry, a NOTIFY is sent to the DSS1 User equipment. The NOTIFY contains a Redirection number Information Element coded as described below:

Type of number
    National number if Userinfo of latest entry is in the local number format or if in global
        number format and the country code of the URI is equal to the country where the
        SUT is located.
    International number if Userinfo of latest entry is in the global number format and the
        country code of the URI is not equal to the country where the SUT is located

Numbering plan identification = ISDN (telephony) numbering plan
Presentation indicator = Presentation allowed
Number digits
    User portion received in the URI of the latest entry; if the country code of the URI: In
    case where global number and the country code is the same as the AGCF/VGW or line is
    located, the country code is removed from the number.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
181: History-Info:
    <URI>; index=1, <diverted-to URI; cause=any appropriate value>; index=1.1

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
NOTIFY: Redirection number
Presentation indicator = Presentation allowed

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
NOTIFY ⬅ ⬅ 181 (Call Being Forwarded)
Apply post test routine
| | | | | Test equipment | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | NOTIFY | ⬅ | ⬅ | 181 (Call Being Forwarded) | | Apply post test routine | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ⬅ | ⬅ | 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|--|-----------------------|-------|---|--|----------|--|--|--|-------------------------------------|--|--|--|-------|--|--|--|----------|----------|---|--|-----------------|--|--------------------------------|--|--| +| TSS
CDIV | TP_504_207 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
180 received. Mapping of latest History-Info entry into the Redirection number if no Privacy value is present in the entry

Ensure that on receipt of a 180 (Ringing) provisional response where a History-Info header is present and no Privacy header is present in the latest hist-entry, an ALERTING is sent to the DSS1 User equipment. The ALERTING contains a Redirection number Information Element coded as described below:

Type of number
    National number if Userinfo of latest entry is in the local number format or if in global number format and the country code of the URI is equal to the country where the SUT is located.
    International number if Userinfo of latest entry is in the global number format and the country code of the URI is not equal to the country where the SUT is located

Numbering plan identification = ISDN (telephony) numbering plan

Presentation indicator = Presentation allowed

Number digits
    User portion received in the URI of the latest entry; if the country code of the URI: In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
180: History-Info:
    <URI>; index=1, <diverted-to URI; cause=any appropriate value>; index=1.1

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
ALERTING: Redirection number
Presentation indicator = Presentation allowed

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment Test equipment
SETUP ➔ ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ← ← 180 (Ringing)
Apply post test routine
| | | | | Test equipment | | Test equipment | SETUP | ➔ | | ➔ INVITE | | | | ← 407 Proxy Authentication Required | | | | ➔ ACK | | | | ➔ INVITE | ALERTING | ← | | ← 180 (Ringing) | | Apply post test routine | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | | ← 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
CDIV | TP_504_208 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|------------------------------------------------|--|-----------------------|-----------------------|-------|---|----------|--|--|-------------------------------------|--|--|-------|--|--|----------|----------|---|-----------------|---------|---|-----------------|--|--|-------| +|

Test purpose
200 OK received. Mapping of latest History-Info entry into the Redirection number if no Privacy value is present in the entry

Ensure that on receipt of a 200 OK (INVITE) provisional response where a History-Info header is present and no Privacy header is present in the latest hist-entry, a CONNECT is sent to the DSS1 User equipment. The CONNECT contains a Redirection number Information Element coded as described below:

Type of number
    National number if Userinfo of latest entry is in the local number format or if in global number format and the country code of the URI is equal to the country where the SUT is located.
    International number if Userinfo of latest entry is in the global number format and the country code of the URI is not equal to the country where the SUT is located

Numbering plan identification = ISDN (telephony) numbering plan

Presentation indicator = Presentation allowed

Number digits
    User portion received in the URI of the latest entry; if the country code of the URI: In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
200: History-Info:
    <URI>; index=1, <diverted-to URI>; cause=any appropriate value>; index=1.1

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

DSS1 Parameter values
CONNECT: Redirection number
Presentation indicator = Presentation allowed

| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipmentTest equipment
SETUP➔➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING←← 180 (Ringing)
CONNECT←← 200 OK INVITE
➔ ACK

Apply post test routine

| | | | | Test equipment | Test equipment | SETUP | ➔ | ➔ INVITE | | | ← 407 Proxy Authentication Required | | | ➔ ACK | | | ➔ INVITE | ALERTING | ← | ← 180 (Ringing) | CONNECT | ← | ← 200 OK INVITE | | | ➔ ACK | +| | Test equipment | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-----------------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--------|---|---|----------------------------|--------------------------------|--|--|--| +| TSS
CDIV | TP_504_209 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
181 received. Mapping of latest History-Info entry into the Redirection number if a Privacy value history is present in the entry | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 181 (Call Being Forwarded) provisional response where a History-Info header is present and a Privacy header is present in the latest hist-entry value set to 'history', a NOTIFY is sent to the DSS1 User equipment. The NOTIFY contains a Redirection number Information Element coded as described below:
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Number digits not present | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
181: History-Info:
; index=1, ?Privacy=history; index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY: Redirection number
Presentation indicator = Presentation restricted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
NOTIFY ⬅ ⬅ 181 (Call Being Forwarded)
Apply post test routine
| | | | | Test equipment | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | NOTIFY | ⬅ | ⬅ | 181 (Call Being Forwarded) | Apply post test routine | | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTIFY | ⬅ | ⬅ | 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_504_210 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
180 received. Mapping of latest History-Info entry into the Redirection number if a Privacy value history is present in the entry | | | | +| Ensure that on receipt of a 180 (Ringing) provisional response where a History-Info header is present and a Privacy header is present in the latest hist-entry value set to 'history', an ALERTING is sent to the DSS1 User equipment. The ALERTING contains a Redirection number Information Element coded as described below:
Type of number = Unknown
Numbering plan identification = Unknown
Presentation indicator = Presentation restricted
Number digits not present | | | | +| SIP header values
180: History-Info:
; index=1, ?Privacy=history; index=1.1 | | | | +| DSS1 Parameter values
ALERTING: Redirection number
Presentation indicator = Presentation restricted | | | | + +![](0641b75ac7ecc32029c69994f47214cf_img.jpg) + +| | | | +|--------------------------------|-----------------------|----------------------------------------------------------------------| +| Message flow | | | +| | Test equipment | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 (Ringing) | +| Apply post test routine | | | + +| | | | | +|-------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_504_211 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|--------------------------------------------------------|---------------------------------------------------------------| + +###### **Test purpose** + +*200 received. Mapping of latest History-Info entry into the Redirection number if a Privacy value history is present in the entry* + +Ensure that on receipt of a 200 OK (INVITE) provisional response where a History-Info header is present and a Privacy header is present in the latest hist-entry value set to 'history', a CONNECT is sent to the DSS1 User equipment. The CONNECT contains a Redirection number Information Element coded as described below: + +Type of number = Unknown + +Numbering plan identification = Unknown + +Presentation indicator = **Presentation restricted** + +Number digits not present + +###### **SIP header values** + +200: History-Info: + +; index=1, ?Privacy=history; index=1.1 + +###### **DSS1 Parameter values** + +CONNECT: Redirection number + +Presentation indicator = Presentation restricted + +![](e0d9ed042580309bcceddbb6b70d2380_img.jpg) + +| | | | +|--------------------------------|-----------------------|----------------------------------------------------------------------| +| Message flow | | | +| | Test equipment | Test equipment | +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 (Ringing) | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|--------------------------------------|--|-----------------------|--|-----------------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|---|---|---------------|----------|---|---|----------------------------| +| TSS
CDIV | TP_504_212 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
181 received. Sending of Redirection number 'not available' if no History-Info header is present. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

A 180 Ringing was already received. Ensure that on receipt of a 181 (Call Being Forwarded) provisional response and a History-Info header is not present, a NOTIFY is sent to the DSS1 User equipment. The PROGRESS contains a Redirection number Information Element coded as described below:

Type of number = Unknown

Numbering plan identification = Unknown

Presentation indicator = Number not available due to interworking

Number digits not present

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Redirection number
Presentation indicator = Presentation restricted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ⬅ ⬅ 180 (Ringing)
PROGRESS ⬅ ⬅ 181 (Call Being Forwarded)

Apply post test routine

| | | | | Test equipment | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | ALERTING | ⬅ | ⬅ | 180 (Ringing) | PROGRESS | ⬅ | ⬅ | 181 (Call Being Forwarded) | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅ | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ⬅ | ⬅ | 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_504_213 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
Mapping of the DivertingLegInformation2 invoke component into the History-Info header first diversion | | | | +|

Ensure that on receipt of a SETUP message and a Facility Information Element DivertingLegInformation2 invoke component is present, the diversionCounter is set to '1', an INVITE request is sent the History-Info header contains two history entries.

  • The first history entry is derived from the 'divertingNr' Parameter - index=1
  • The second entry is derived from Request URI - index=1.1
  • The cause parameter in the second entry is derived from the 'diversionReason' parameter Reason_VA as described in Table 7.2.5.4.2-2
| | | | +| SIP header values | | | | +| INVITE: Request URI
History-Info:
< divertingNr >; index=1,
; cause= Reason_VA>; index=1.1 | | | | + +| | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------|-----------------------|-------|---|----------|--|--|-------------------------------------|--|--|-------|--|--|----------|--------------------------------|--|--| +| DSS1 Parameter values
SETUP: Facility
diversionCounter
diversionReason
divertingNr
originalCalledNr
Called party number | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
Apply post test routine
| | Test equipment | Test equipment | SETUP | → | → INVITE | | | ← 407 Proxy Authentication Required | | | → ACK | | | → INVITE | Apply post test routine | | | +| | Test equipment | Test equipment | | | | | | | | | | | | | | | | | +| SETUP | → | → INVITE | | | | | | | | | | | | | | | | | +| | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | +| | | → INVITE | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_504_214 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|--------------------------------------------------------|---------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Mapping of the DivertingLegInformation2 invoke component into the History-Info header second diversion

Ensure that on receipt of a SETUP message and a Facility Information Element DivertingLegInformation2 invoke component is present, the diversionCounter is set to '2', an INVITE request is sent the History-Info header contains two history entries.
  • The first history entry is derived from the 'originalCalledNr' Parameter - index=1
  • The second entry is derived from 'divertingNr' parameter - index=1.1
  • The cause parameter in the second entry is set to '404'
  • The third history entry is derived from Request URI - index=1.1.1
  • The cause parameter in the third entry is derived from the 'diversionReason' parameter Reason_VA as described in Table 7.2.5.4.2-2
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
INVITE: Request URI
History-Info:
< divertingNr >; index=1,
< divertingNr; cause=404>; index=1.1,
< Request URI>; cause= Reason_VA>; index=1.1.1 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------| +| DSS1 Parameter values
SETUP: Facility
diversionCounter
diversionReason
divertingNr
originalCalledNr
Called party number | +|--------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------|-----------------------|-------|---|----------|--|--|-------------------------------------|--|--|-------|--|--|----------|--------------------------------|--|--| +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
Apply post test routine
| | Test equipment | Test equipment | SETUP | → | → INVITE | | | ← 407 Proxy Authentication Required | | | → ACK | | | → INVITE | Apply post test routine | | | +| | Test equipment | Test equipment | | | | | | | | | | | | | | | | | +| SETUP | → | → INVITE | | | | | | | | | | | | | | | | | +| | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | +| | | → ACK | | | | | | | | | | | | | | | | | +| | | → INVITE | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | + +**Table 7.2.5.4.2-2 – Mapping of diversionReason value into cause parameter value in the second history entry** + +| Reason_VA | diversionReason | cause | +|--------------|-----------------|-------| +| Reason_VA_01 | unknown | "404" | +| Reason_VA_02 | cfu | "302" | +| Reason_VA_03 | cfb | "486" | +| Reason_VA_04 | cfnr | "408" | +| Reason_VA_05 | cdAlerting | "487" | +| Reason_VA_06 | cdImmediate | "480" | + +| TSS
CDIV | TP_504_215 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-----------------------|--|-------|---|--|----------|--|--|--|--|-------------------------------------|--|--|--|--|-------|--|--|--|--|----------|--|----------|---|--|------------------------------|--| +| Test purpose
181 received. Mapping of the value of the Privacy parameter in latest History Entry into the DivertingLegInformation3 invoke component

Ensure that on receipt of a 181 (Call Being Forwarded) provisional response, the privacy requirements in the latest history entry are mapped into Facility Information Element DivertingLegInformation3 presentationAllowedIndicator parameter in an FACILITY as described in Table 7.2.5.4.2-3. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
181: History-Info:
< divertingNr >; index=1,
; cause= privacy_VA>; index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values
FACILITY: Facility
DivertingLegInformation3
presentationAllowedIndicator = privacy_VA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
FACILITY ← ← 181 (Call Being Forwarded)

Apply post test routine

| | | | | Test equipment | | Test equipment | | SETUP | → | | → INVITE | | | | | ← 407 Proxy Authentication Required | | | | | → ACK | | | | | → INVITE | | FACILITY | ← | | ← 181 (Call Being Forwarded) | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| FACILITY | ← | | ← 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_504_216 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
180 received. Mapping of the value of the Privacy parameter in latest History Entry into the DivertingLegInformation3 invoke component

Ensure that on receipt of a 180 (Ringing) provisional response the privacy requirements in the latest history entry are mapped into Facility Information Element DivertingLegInformation3 presentationAllowedIndicator parameter in an ALERTING as described in Table 7.2.5.4.2-3. | | | | +| | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------|-----------------------|-------|---|----------|--|--|-------------------------------------|--|--|-------|--|--|----------|----------|---|------------------------------|--------------------------------|--|--| +| SIP header values
180: History-Info:
< divertingNr >; index=1,
; cause= privacy_VA>; index=1.1 | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: Facility
DivertingLegInformation3
presentationAllowedIndicator = privacy_VA | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ← ← 181 (Call Being Forwarded)
Apply post test routine
| | Test equipment | Test equipment | SETUP | ➔ | ➔ INVITE | | | ← 407 Proxy Authentication Required | | | ➔ ACK | | | ➔ INVITE | ALERTING | ← | ← 181 (Call Being Forwarded) | Apply post test routine | | | +| | Test equipment | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | +| | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | +| | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← 181 (Call Being Forwarded) | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|-----------------------|-------|---|----------|--|--|-------------------------------------|--|--|-------|--|--|----------|----------|---|-----------------|---------|---|-----------------|--|--|-----|--------------------------------|--|--| +| TSS
CDIV | TP_504_217 | Reference
subclause 5.2.5.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
200 received. Mapping of the value of the Privacy parameter in latest History Entry into the DivertingLegInformation3 invoke component | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 200 OK (INVITE) final response the privacy requirements in the latest history entry are mapped into Facility Information Element DivertingLegInformation3 presentationAllowedIndicator parameter in a CONNECT as described in Table 7.2.5.4.2-3. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200: History-Info:
< divertingNr >; index=1,
; cause= privacy_VA>; index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT: Facility
DivertingLegInformation3
presentationAllowedIndicator = privacy_VA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP ➔ ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
ALERTING ← ← 180 (Ringing)
CONNECT ← 200 OK (INVITE)
ACK
Apply post test routine
| | | | | Test equipment | Test equipment | SETUP | ➔ | ➔ INVITE | | | ← 407 Proxy Authentication Required | | | ➔ ACK | | | ➔ INVITE | ALERTING | ← | ← 180 (Ringing) | CONNECT | ← | 200 OK (INVITE) | | | ACK | Apply post test routine | | | +| | Test equipment | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | ← 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.5.4.2-3 – Mapping of the value of the Privacy parameter in latest History Entry into the DivertingLegInformation3 invoke component** + +| privacy_VA | Privacy header in SIP response | presentationAllowedIndicator | +|---------------|--------------------------------|------------------------------| +| privacy_VA_01 | No Privacy parameter | true | +| privacy_VA_02 | history | false | + +| | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|-------------------|--------|---|---------|-------------|---|------------|--|--------------------------------|--| +| TSS
CDIV | TP_503_218 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | +| Test purpose
ALERTING received. Mapping of DivertingLegInformation1 into History-Info header No History-Info header is sent.

Ensure that on receipt of an ALERTING and a Facility Information Element DivertingLegInformation1 is present, the diversionReason as indicated in Table 5.3.6.2-1, the subscriptionOption is set to 'noNotification', a 180 (Ringing) provisional response is sent and no History-Info header is present. | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | +| DSSI Parameter values
ALERTING: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = noNotification
divertedToNumber = diverted to number (PIXIT) | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
Apply post test routine
| | | | | Test equipment | End device | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_219 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
FACILITY received. Mapping of DivertingLegInformation1 into History-Info header No History-Info header is sent.

Ensure that on receipt of an FACILITY and a Facility Information Element DivertingLegInformation1, the diversionReason as indicated in Table 7.2.5.4.2-2 is present, the subscriptionOption is set to 'noNotification', no SIP response is sent. | | | | +| SIP header values | | | | +| DSSI Parameter values
ALERTING: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = noNotification
divertedToNumber = diverted to number (PIXIT) | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 180 Ringing | ⬅ | ⬅ FACILITY | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_220 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +| Test purpose
PROGRESS received. Mapping of DivertingLegInformation1 into History-Info header No History-Info header is sent.

Ensure that on receipt of an PROGRESS and a Facility Information Element DivertingLegInformation1, the diversionReason as indicated in Table 7.2.5.4.2-2 is present, the subscriptionOption is set to 'noNotification', a 183 (Session Progress) provisional response is sent and no History-Info header is present. | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-------------------|--------|---|---------|--|--|------------|--------------------------------|--|--| +| SIP header values | | | | | | | | | | | | | +| DSS1 Parameter values
PROGRESS: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = noNotification
divertedToNumber = diverted to number (PIXIT) | | | | | | | | | | | | | +| Message flow

Test equipment End device
INVITE ➔ ➔ SETUP
⬅ FACILITY
Apply post test routine
| | Test equipment | End device | INVITE | ➔ | ➔ SETUP | | | ⬅ FACILITY | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | +| | | ⬅ FACILITY | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_221 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
ALERTING received. Mapping of DivertingLegInformation1 into History-Info header a restricted History-Info header is sent.

Ensure that on receipt of an ALERTING and a Facility Information Element DivertingLegInformation1, the diversionReason as indicated in Table 7.2.5.4.2-2 is present, the subscriptionOption is set to 'notificationWithoutDivertedToNr', a 180 (Ringing) provisional response is sent and a History-Info header is present a Privacy header is escaped in the last entry coded as follows:
First entry: URI not significant; index=1
Second entry URI derived from the 'divertedToNumber'; Privacy= history; cause=reason_VA; index=1.1. | +| SIP header values | +| 180: History-Info:
< divertedToNumber?Privacy=history; cause=reason_VA; index=1.1 | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| DSSI Parameter values
ALERTING: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = notificationWithoutDivertedToNr
divertedToNumber = diverted to number (PIXIT) | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_222 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
PROGRESS received. Mapping of DivertingLegInformation1 into History-Info header a restricted History-Info header is sent.

Ensure that on receipt of an PROGRESS and a Facility Information Element DivertingLegInformation1, the diversionReason as indicated in Table 7.2.5.4.2-2 is present, the subscriptionOption is set to 'notificationWithoutDivertedToNr', a 183 (Session Progress) provisional response is sent and a History-Info header is present a Privacy header is escaped in the last entry coded as follows:
First entry: URI not significant; index=1
Second entry URI derived from the 'divertedToNumber'; Privacy= history; cause=reason_VA; index=1.1. | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
183: History-Info:
< divertedToNumber?Privacy=history; cause=reason_VA; index=1.1 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DSSI Parameter values
PROGRESS: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = notificationWithoutDivertedToNr
divertedToNumber = diverted to number (PIXIT) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------------|-----------------------|-------------------| +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 183 (Session Progress) | ← | ← PROGRESS | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|---------------|---|---|----------|--------------------------------|--|--|--| +| TSS
CDIV | TP_503_223 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | +| Test purpose
ALERTING received. Mapping of DivertingLegInformation1 into History-Info header a restricted History-Info header is sent. | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of an ALERTING and a Facility Information Element DivertingLegInformation1, the diversionReason as indicated in Table 7.2.5.4.2-2 is present, the subscriptionOption is set to 'notificationWithDivertedToNr', a 180 (Ringing) provisional response is sent and a History-Info header is present no Privacy header is present in the last entry coded as follows:
First entry: URI not significant; index=1
Second entry URI derived from the 'divertedToNumber'; cause=reason_VA; index=1.1.

| | | | | | | | | | | | | | | | | | | | +| SIP header values
180: History-Info:
< divertedToNumber?Privacy=history; cause=reason_VA; index=1.1 | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = notificationWithDivertedToNr
divertedToNumber = diverted to number (PIXIT) | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 (Ringing) ⬅ ⬅ ALERTING
Apply post test routine
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 180 (Ringing) | ⬅ | ⬅ | ALERTING | Apply post test routine | | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | +| 180 (Ringing) | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_224 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
FACILITY received. Mapping of DivertingLegInformation1 into History-Info header a restricted History-Info header is sent. | | | | +|

Ensure that on receipt of an FACILITY and a Facility Information Element DivertingLegInformation1, the diversionReason as indicated in Table 7.2.5.4.2-2 is present, the subscriptionOption is set to 'notificationWithDivertedToNr', a 181 (Being forwarded) provisional response is sent and a History-Info header is present no Privacy header is present in the last entry coded as follows:
First entry: URI not significant; index=1
Second entry URI derived from the 'divertedToNumber'; cause=reason_VA; index=1.1.

| | | | +| SIP header values
181: History-Info:
< divertedToNumber?Privacy=history; cause=reason_VA; index=1.1 | | | | +| DSS1 Parameter values
FACILITY: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = notificationWithDivertedToNr
divertedToNumber = diverted to number (PIXIT) | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 181 (Being forwarded) | ← | ← FACILITY | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_225 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose
PROGRESS received. Mapping of DivertingLegInformation1 into History-Info header a restricted History-Info header is sent.

Ensure that on receipt of an PROGRESS and a Facility Information Element DivertingLegInformation1, the diversionReason as indicated in Table 7.2.5.4.2-2 is present, the subscriptionOption is set to 'notificationWithDivertedToNr', a 183 (Session Progress) provisional response is sent and a History-Info header is present no Privacy header is present in the last entry coded as follows:
First entry: URI not significant; index=1
Second entry URI derived from the 'divertedToNumber'; cause=reason_VA; index=1.1.

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

SIP header values
183: History-Info:
<URI non significant value; index=1,
< divertedToNumber?Privacy=history; cause=reason_VA; index=1.1

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

DSS1 Parameter values
PROGRESS: Facility
DivertingLegInformation1
diversionReason = reason_VA
subscriptionOption = notificationWithDivertedToNr
divertedToNumber = diverted to number (PIXIT)

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 183 (Session Progress) | ← | ← PROGRESS | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_226 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Test purpose
DivertingLegInformation3 received in an ALERTING and History-Info header is send in the 180

Ensure that on receipt of a Facility Information Element containing a DivertingLegInformation3 invoke component and the presentationAllowedIndicator is set to 'true', a 180 (Ringing) is sent and a History-Info header is present. The latest entry in the History-Info header does not contain a Privacy header field.

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--|-----------------------|-------------------|--|-------------------|--------|---|--|---|-------|---------------|---|--|---|----------|--|--------------------------------|--|--|--| +| SIP header values
INVITE: History-Info:
index=1
; index=1.1
180: History-Info:
index=1
; index=1.1 | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: Facility
DivertingLegInformation3
presentationAllowedIndicator=true | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➠ ➠ SETUP
180 (Ringing) ⬅ ⬅ ALERTING
Apply post test routine
| | | Test equipment | | | End device | INVITE | ➠ | | ➠ | SETUP | 180 (Ringing) | ⬅ | | ⬅ | ALERTING | | Apply post test routine | | | | +| | Test equipment | | | End device | | | | | | | | | | | | | | | | | | +| INVITE | ➠ | | ➠ | SETUP | | | | | | | | | | | | | | | | | | +| 180 (Ringing) | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------|---------------------------------------------------------------|-------------------|-----------------------|--|--|-------------------|--------|---|--|---|-------|---------------|---|--|---|----------|--|--------------------------------|--|--|--| +| TSS
CDIV | TP_503_227 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
DivertingLegInformation3 received in an ALERTING and History-Info header is send in the 180 | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a Facility Information Element containing a DivertingLegInformation3 invoke component and the presentationAllowedIndicator is set to privacy_VA in an ALERTING message, a 180 (Ringing) is sent and a History-Info header is present. A Privacy header field in the latest entry in the History-Info header is processed as described in Table 7.2.5.4.2-4. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: History-Info:
index=1
; index=1.1
180: History-Info:
index=1
; index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
ALERTING: Facility
DivertingLegInformation3
presentationAllowedIndicator= privacy_VA | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➠ ➠ SETUP
180 (Ringing) ⬅ ⬅ ALERTING
Apply post test routine
| | | | | Test equipment | | | End device | INVITE | ➠ | | ➠ | SETUP | 180 (Ringing) | ⬅ | | ⬅ | ALERTING | | Apply post test routine | | | | +| | Test equipment | | | End device | | | | | | | | | | | | | | | | | | | | +| INVITE | ➠ | | ➠ | SETUP | | | | | | | | | | | | | | | | | | | | +| 180 (Ringing) | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-----------------------|---|---|----------| +| TSS
CDIV | TP_503_228 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | +| Test purpose
DivertingLegInformation3 received in an FACILITY and History-Info header is send in the 181 | | | | | | | | | | | | | | | | +| Ensure that on receipt of a Facility Information Element containing a DivertingLegInformation3 invoke component and the presentationAllowedIndicator is set to privacy_VA in a FACILITY message, a 181 (Being forwarded) is sent and a History-Info header is present. A Privacy header field in the latest entry in the History-Info header is processed as described in Table 7.2.5.4.2-4. | | | | | | | | | | | | | | | | +| SIP header values
INVITE: History-Info:
index=1
; index=1.1
181: History-Info:
index=1
; index=1.1 | | | | | | | | | | | | | | | | +| DSS1 Parameter values
FACILITY: Facility
DivertingLegInformation3
presentationAllowedIndicator= privacy_VA | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
181 (Being forwarded) ⬅ ⬅ FACILITY

Apply post test routine

| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 181 (Being forwarded) | ⬅ | ⬅ | FACILITY | +| | Test equipment | | End device | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | +| 181 (Being forwarded) | ⬅ | ⬅ | FACILITY | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_229 | Reference
subclause 5.2.5.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
DivertingLegInformation3 received in an CONNECT and History-Info header is send in the 180 | | | | +| Ensure that on receipt of a Facility Information Element containing a DivertingLegInformation3 invoke component and the presentationAllowedIndicator is set to privacy_VA in a CONNECT message, a 180 (Ringing) is sent and a History-Info header is present. A Privacy header field in the latest entry in the History-Info header is processed as described in Table 7.2.5.4.2-4. | | | | +| SIP header values
INVITE: History-Info:
index=1
; index=1.1
200 OK: History-Info:
index=1
;
index=1.1 | | | | +| DSS1 Parameter values
CONNECT: Facility
DivertingLegInformation3
presentationAllowedIndicator= privacy_VA | | | | + +| Message flow | | | +|-------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE | ➔ | ➔ SETUP | +| 180 (Ringing) | ← | ← ALERTING | +| 200 OK (INVITE) | ← | ← CONNECT | +| ACK | ➔ | | +| Apply post test routine | | | + +**Table 7.2.5.4.2-4 – Mapping of the value of the Privacy parameter in latest History Entry into the DivertingLegInformation3 invoke component** + +| privacy_VA | presentationAllowedIndicator | Privacy header in SIP response | +|-------------------|-------------------------------------|---------------------------------------| +| privacy_VA_01 | true | No Privacy parameter | +| privacy_VA_02 | false | Privacy=history | + +| TSS
CDIV | TP_503_230 | Reference
subclause 5.2.5.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------|--|-----------------------|-------------------|--------|---|---------|-------------------------|--|--| +| Test purpose
INVITE received History-Info header contains two entries not restricted, Redirecting number sent in SETUP | | | | | | | | | | | | | +|

Ensure that on receipt of an INVITE request and a History-Info header is present containing two entries and the first entry is not escaped with an Privacy header, a SETUP is sent and the Redirecting number address signals is derived from the URI of the first entry of the History-Info header and the Reason of diversion is derived from the cause parameter of the last entry coded as described below and in Table 7.2.5.4.2-5:

| | | | | | | | | | | | | +| Redirecting number
Type of number
National if the URI is coded as follows sip: local-number@hostportion
international if the URI is coded as follows sip: global –number@hostportion and CC is
not the same as the country where the user or line is located
Numbering plan identification: ISDN numbering plan
Presentation indicator: presentation allowed
Reason of diversion: reason_VA
Number digits:
Userinfo as received in the first URI; global-number-digits: if the country code of the URI is the same as the country where the user or line is located, the country code is removed from the Userinfo | | | | | | | | | | | | | +| SIP header values
INVITE: History-Info:
index=1
; index=1.1 | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP: Redirecting number
Presentation indicator: presentation allowed
Reason of diversion: reason_VA | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
CDIV | TP_503_231 | Reference
subclause 5.2.5.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | +| Test purpose
INVITE received History-Info header contains two entries restricted, Redirecting number sent in SETUP

Ensure that on receipt of an INVITE request and a History-Info header is present containing two entries and the first entry is escaped with an Privacy header value 'history', a SETUP is sent and the Redirecting number address signals are absent and coded as described below and in Table 7.2.5.4.2-5:

Redirecting number
Type of number: unknown
Numbering plan identification: unknown
Presentation indicator: presentation restricted
Reason of diversion: reason_VA
Number digits: not present | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------| +| TSS
CDIV | TP_503_232 | Reference
subclause 5.2.5.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | +| Test purpose
INVITE received History-Info header contains one entry, Redirecting number sent in SETUP

Ensure that on receipt of an INVITE request and a History-Info header is present containing only the entry index=1.1, a SETUP is sent and the Redirecting number address signals are absent and coded as described below and in Table 7.2.5.4.2-5:

Redirecting number
Type of number: unknown
Numbering plan identification: unknown
Presentation indicator: number not available due to interworking
Reason of diversion: reason_VA
Number digits: not present | | | | + +![](ac3afa2e555b328432e17d1e942e1bf6_img.jpg) + +| | | | +|--------------------------------|-----------------------|-------------------| +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| Apply post test routine | | | + +| | | | | +|-------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
CDIV | TP_503_233 | Reference
subclause 5.2.5.2.2/
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | +|-------------|------------|--------------------------------------------------------|------------------------------------------------| + +###### Test purpose + +*INVITE received History-Info header contains more than two entries not restricted, Redirecting number sent in SETUP* + +Ensure that on receipt of an INVITE request and a History-Info header is present containing more than two entries and the second last entry is not escaped with a Privacy header, a SETUP is sent and the first Redirecting number address signals are derived from the URI of the second last entry of the History-Info header and the Reason of diversion is derived from the cause parameter of the last entry, the second Redirecting number address signals are derived from the URI of the first entry of the History-Info header and the Reason of diversion is derived from the cause parameter of the second entry coded as described below and in Table 7.2.5.4.2-5: + +###### First Redirecting number + +Type of number + +National if the URI is coded as follows sip: local-number@hostportion + +international if the URI is coded as follows sip: global -number@hostportion and CC is not the same as the country where the user or line is located + +Numbering plan identification: ISDN numbering plan + +Presentation indicator: **presentation allowed** + +Reason of diversion: **reason\_VA** + +Number digits: + +Userinfo as received in the second last URI; global-number-digits: if the country code of the URI is the same as the country where the user or line is located, the country code is removed from the Userinfo + +###### Second Redirecting number + +Type of number + +National if the URI is coded as follows sip: local-number@hostportion + +international if the URI is coded as follows sip: global -number@hostportion and CC is not the same as the country where the user or line is located + +Numbering plan identification: ISDN numbering plan + +Presentation indicator: presentation allowed + +Number digits: + +Userinfo as received in the first URI; global-number-digits: if the country code of the URI is the same as the country where the user or line is located, the country code is removed from the Userinfo + +###### SIP header values + +INVITE: History-Info: + +index=1 + +; index=1.1 + +; index=1.1.1 + +###### DSSI Parameter values + +SETUP: **Redirecting number** + +Presentation indicator: presentation allowed + +Reason of diversion: reason\_VA + +**Redirecting number** + +Presentation indicator: presentation allowed + +![](d294f950ce24d9ecf2eedfc7ddba7411_img.jpg) + +| | | | +|--------------------------------|-----------------------|-------------------| +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|------------------------------------------------| +| TSS
CDIV | TP_503_234 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5 | +| Test purpose
INVITE received History-Info header contains more than two entries restricted, Redirecting number sent in SETUP | | | | +| Ensure that on receipt of an INVITE request and a History-Info header is present containing two entries and the second last entry is escaped with an Privacy header value 'history', a SETUP is sent and the first Redirecting number address signals are not present and the Reason of diversion is derived from the cause parameter of the last entry coded as described below and in Table 7.2.5.4.2-5: | | | | +| 1st Redirecting number
Type of number: unknown
Numbering plan identification: unknown
Presentation indicator: presentation restricted
Reason of diversion: reason_VA
Number digits: not present | | | | +| 2nd Redirecting number | | | | +| SIP header values
INVITE: History-Info:
index=1
;index=1.1
; index=1.1.1 | | | | +| DSSI Parameter values
SETUP: Redirecting number
Presentation indicator: presentation restricted
Reason of diversion: reason_VA
Redirecting number | | | | +| Message flow | | | | +| | Test equipment | End device | | +| INVITE | → | → SETUP | | +| Apply post test routine | | | | + +**Table 7.2.5.4.2-5 – Mapping of cause parameter in the history-entry into reason of diversion** + +| reason_VA | cause parameter | Reason of diversion | +|------------------|------------------------|-------------------------------| +| reason_VA_01 | "404" | Unknown | +| reason_VA_02 | "302 " | Call forwarding unconditional | +| reason_VA_03 | "486" | Call forwarding busy | +| reason_VA_04 | "408" | Call forwarding no reply | +| reason_VA_05 | "487" | Deflection | +| reason_VA_06 | "480" | Deflection | +| reason_VA_07 | "503" | Unknown | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_235 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
INVITE received a History-Info header present with more than two entries, a SETUP is sent at the T Reference point | | | | +| Ensure that on receipt of an INVITE request and a History-Info header is present, a SETUP message is sent. The SETUP contains a Facility Information Element with a DivertingLegInformation2 invoke component. The diversionCounter is derived from the number of dots in the index parameter of the last entry of the History-Info header. The diversionReason is derived from the cause parameter of the last entry as described in Table 7.2.5.4.2-6, the divertingNr is derived from the URI of second last entry and the originalCalledNr is derived from the URI of the first entry in the History-Info header. | | | | +| SIP header values
INVITE: History-Info:
index=1
; index=1.1
reason_VA >; index=1.1.1 | | | | +| DSS1 Parameter values
SETUP: Facility
DivertingLegInformation2
diversionCounter: 1
diversionReason: reason_VA
divertingNr: derived from the first entry | | | | +| Message flow
Test equipment

Image: Flow diagram: INVITE from Test equipment to End device, then SETUP from End device to Test equipment. Below the arrows is the text 'Apply post test routine'.

| | | | + +**Table 7.2.5.4.2-6 – Mapping of cause parameter in the history-entry into reason of diversion in the DivertingLegInformation2 component** + +| reason_VA | cause | diversionReason | +|------------------|--------------|------------------------| +| reason_VA_01 | "404" | unknown | +| reason_VA_02 | "302" | cfu | +| reason_VA_03 | "486" | cfb | +| reason_VA_04 | "408" | cfnr | +| reason_VA_05 | "487" | cdAlerting | +| reason_VA_06 | "480" | cdImmediate | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_236 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
No further diversion occurs a 180 is sent | | | | +| When an INVITE is received and a History-Info header is present, ensure that on receipt of an ALERTING message a 180 Ringing provisional response is sent. The 180 Ringing contains a History-Info header and the value is the same as received in the initial INVITE, a Privacy header is escaped in the last entry and the value is set to 'history'. | | | | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| SIP header values
INVITE: History-Info:
index=1
;
index=1.1

180: History-Info:
index=1
cause=any appropriate value>; index=1.1 | | | +| DSSI Parameter values | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_237 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
No further diversion occurs a 183 is sent | | | | +| When an INVITE is received and a History-Info header is present, ensure that on receipt of a PROGRESS message a 183 Session Progress provisional response is sent. The 183 Session Progress contains a History-Info header and the value is the same as received in the initial INVITE, a Privacy header is escaped in the last entry and the value is set to 'history'. | | | | +| SIP header values
INVITE: History-Info:
index=1
;
index=1.1

180: History-Info:
index=1
cause=any appropriate value>; index=1.1 | | | | +| DSSI Parameter values | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | → | | → SETUP | +| 180 Ringing | ← | | ← ALERTING | +| 183 Session Progress | ← | | ← PROGRESS | +| Apply post test routine | | | | + +| TSS
CDIV | TP_503_238 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|-------------------|--------|---|---------|-------------|---|------------|-----------------|---|-----------|-----|---|--| +| Test purpose
No further diversion occurs a 200 OK is sent | | | | | | | | | | | | | | | | | | | +|

When an INVITE is received and a History-Info header is present,ensure that on receipt of a CONNECT message a 200 OK INVITE final response is sent. The 200 OK INVITE contains a History-Info header and the value is the same as received in the initial INVITE, a Privacy header is escaped in the last entry and the value is set to 'history'.

| | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: History-Info:
index=1
;
index=1.1 | | | | | | | | | | | | | | | | | | | +| 200 OK: History-Info:
index=1
Privacy=history ;
cause=any appropriate value>; index=1.1 | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
200 OK (INVITE) ⬅ ⬅ CONNECT
ACK ➔
Apply post test routine
| | | | | Test equipment | End device | INVITE | ➔ | ➔ SETUP | 180 Ringing | ⬅ | ⬅ ALERTING | 200 OK (INVITE) | ⬅ | ⬅ CONNECT | ACK | ➔ | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ SETUP | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ ALERTING | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ | ⬅ CONNECT | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_239 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +| Test purpose
A call diversion occurs in the private network a 180 is sent | | | | +|

When an INVITE is received and a History-Info header is present, ensure that on receipt of an ALERTING message containing a Facility Information Element with a DivertingLegInformation1 invoke component, a 180 (Ringing) provisional response is sent. The 180 (Ringing) contains a History-Info header the value is the same as received in the initial INVITE. A further entry is added and the URI of the added entry is derived from the divertedToNumber element, the cause parameter is derived from the diversionReason element as described in Table 7.2.5.4.2-7, the Privacy header in the entry is derived from the subscriptionOption element as described in Table 7.2.5.4.2-8. If the subscriptionOption is set to 'noNotification' no History-Info header is present in the 180 (Ringing).

| | | | +| SIP header values
INVITE: History-Info:
index=1
;
index=1.1 | | | | +| 180: History-Info:
index=1
cause=any appropriate value>; index=1.1
Privacy_VA ]; cause= reason_VA >;index=1.1.1 | | | | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------| +| DSSI Parameter values
ALERTING: Facility
DivertingLegInformation1
diversionReason
subscriptionOption
divertedToNumber | | | +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
CDIV | TP_503_240 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
A call diversion occurs in the private network a 183 is sent

When an INVITE is received and a History-Info header is present, ensure that on receipt of a PROGRESS message containing a Facility Information Element with a DivertingLegInformation1 invoke component, a 183 (Session Progress) provisional response is sent. If the 183 (Session Progress) contains a History-Info header the value is the same as received in the initial INVITE. If a further entry is added and the URI of the added entry is derived from the divertedToNumber element, the cause parameter is derived from the diversionReason element as described in Table 7.2.5.4.2-7, the Privacy header in the entry is derived from the subscriptionOption element as described in Table 7.2.5.4.2-8. If the subscriptionOption is set to 'noNotification' no History-Info header is present in the 183 (Session Progress). | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
INVITE: History-Info:
index=1
;
index=1.1

183: History-Info:
index=1
cause=any appropriate value>; index=1.1
;index=1.1.1 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------| +| DSSI Parameter values
PROGRESS: Facility
DivertingLegInformation1
diversionReason
subscriptionOption
divertedToNumber | +|----------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|-------------------------|-----------------------|-------------------| +| Message flow | | | +| | Test equipment | End device | +| INVITE | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 183 Session Progress | ← | ← PROGRESS | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-----------------------|---|---|----------|--|--------------------------------|--|--| +| TSS
CDIV | TP_503_241 | Reference
subclause 5.2.5.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | +| Test purpose
A call diversion occurs in the private network a 181 is sent | | | | | | | | | | | | | | | | | | | | +| When an INVITE is received and a History-Info header is present, ensure that on receipt of a FACILITY message containing a Facility Information Element with a DivertingLegInformation1 invoke component, a 181 (Being Forwarded) provisional response is sent. The 181 (Being Forwarded) contains a History-Info header the value is the same as received in the initial INVITE. A further entry is added and the URI of the added entry is derived from the divertedToNumber element, the cause parameter is derived from the diversionReason element as described in Table 7.2.5.4.2-7, the Privacy header in the entry is derived from the subscriptionOption element as described in Table 7.2.5.4.2-8. If the subscriptionOption is set to 'noNotification' no provisional response is sent. | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: History-Info:
index=1
;
index=1.1

181: History-Info:
index=1
cause=any appropriate value>; index=1.1
Privacy_VA ]; cause= reason_VA >;index=1.1.1 | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values
FACILITY: Facility
DivertingLegInformation1
diversionReason
subscriptionOption
divertedToNumber | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
181 (Being Forwarded) ← ← FACILITY
Apply post test routine
| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 181 (Being Forwarded) | ← | ← | FACILITY | | Apply post test routine | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | +| 181 (Being Forwarded) | ← | ← | FACILITY | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | + +**Table 7.2.5.4.2-7 – Mapping of the DivertingLegInformation1 invoke component into added history entry** + +| reason_VA | cause | diversionReason | +|------------------|--------------|------------------------| +| reason_VA_01 | "404" | unknown | +| reason_VA_02 | "302" | cfu | +| reason_VA_03 | "486" | cfb | +| reason_VA_04 | "408" | cfnr | +| reason_VA_05 | "487" | cdAlerting | +| reason_VA_06 | "480" | cdImmediate | + +**Table 7.2.5.4.2-8 – Mapping of subscriptionOption into the Privacy header in the latest history entry** + +| Privacy_VA | subscriptionOptio | Privacy header | +|---------------|---------------------------------|-----------------------------------------------------------------------| +| Privacy_VA_01 | noNotification | No History-Info header present or in case of FACILITY not interworked | +| Privacy_VA_02 | notificationWithoutDivertedToNr | Privacy=history" | +| Privacy_VA_03 | notificationWithDivertedToNr | No Privacy parameter present | + +| | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|--|-------------------------|--|--| +| TSS
CDIV | TP_503_242 | Reference
subclause 5.2.5.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | +| Test purpose
A further call diversion beyond the private network | | | | | | | | | | | | | | | | | | | | +|

When an INVITE is received and a History-Info header is present, ensure that on receipt of an ALERTING message and a Facility Information Element is present containing a DivertingLegInformation3 invoke component with a presentationAllowedIndicator set to privacy_VA as described in Table 7.2.5.4.2-9, a 180 (Ringing) is sent. The 180 (Ringing) contains the History-Info header as received in the initial INVITE, according the privacy requirements described in Table 7.2.5.4.2-9 a Privacy header is escaped in the last entry and set to 'history' or not present.

| | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: History-Info:
index=1
; index=1.1

180: History-Info:
index=1
cause= any appropriate value >; index=1.1 | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values
ALERTING: Facility
DivertingLegInformation3
presentationAllowedIndicator: privacy_VA | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
Apply post test routine
| | | | | Test equipment | | End device | INVITE | → | → | SETUP | 180 Ringing | ← | ← | ALERTING | | Apply post test routine | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | +| INVITE | → | → | SETUP | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | + +**Table 7.2.5.4.2-9 – Mapping of the value of the DivertingLegInformation3 invoke component into the Privacy parameter in latest History Entry** + +| privacy_VA | presentationAllowedIndicator | Privacy header in SIP response | +|---------------|------------------------------|--------------------------------| +| privacy_VA_01 | true | No Privacy parameter | +| privacy_VA_02 | false | Privacy=history | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------|---------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------------------|---|---|----------|-----|---|--|--|--|--------------------------------|--|--| +| TSS
CDIV | TP_503_243 | Reference
subclause 5.2.5.2.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/5
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
'CallRerouteing invoke' received, rerouteingCounter is set to 1 302 is sent | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of FACILITY message containing a Facility Information Element CallRerouteing invoke component, a 302 (Moved Temporarily) final response is sent. The URI of the Contact header is derived from the calledAddress element, the PSTN XML BearerCapability is derived from the q931InfoElemen Bearer Capability, the PSTN XML Low layer compatibility is derived from the q931InfoElemen Low layer compatibility, the PSTN XML High layer compatibility is derived from the q931InfoElemen High layer compatibility, the User-to-User header is derived from the q931InfoElemen User-user information.

| | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
302: Contact:
PSTN XML MIME body

PSTN
BearerCapability derived from the q931InfoElemen Bearer Capability
LowLayerCompatibility derived from the q931InfoElemen Low layer compatibility
HighLayerCompatibility derived from the q931InfoElemen High layer compatibility
User-to-User derived from the q931InfoElemen User-user information
History-Info:
index=1
reason_VA >; index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
FACILITY: Facility
CallRerouteing invoke
rerouteingReason: reason_VA
calledAddress
rerouteingCounter
q931InfoElement
Bearer Capability
Low layer compatibility
High layer compatibility
User-user information
lastRerouteingNr
subscriptionOption: any appropriate value | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
302 (Moved Temporarily) ⬅ ⬅ FACILITY
ACK ➔
Apply post test routine
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 302 (Moved Temporarily) | ⬅ | ⬅ | FACILITY | ACK | ➔ | | | | Apply post test routine | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | +| 302 (Moved Temporarily) | ⬅ | ⬅ | FACILITY | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.5.4.2-10 – Mapping of the CallRerouteing invoke component into added history entry** + +| reason_VA | rerouteingReason | cause | +|------------------|-------------------------|--------------| +| reason_VA_01 | unknown | "404" | +| reason_VA_02 | cfu | "302" | +| reason_VA_03 | cfb | "486" | +| reason_VA_04 | cfnr | "408" | +| reason_VA_05 | cdAlerting | "487" | +| reason_VA_06 | cdImmediate | "480" | + +#### 7.2.5.5 Three Party Service (3PTY) + +##### 7.2.5.5.1 Test purposes for POTS + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------------------| +| TSS
3PTY | TP_505_101 | Reference
subclause C.14.1.1 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6 | +|

Test purpose
The user establishes a three party conversation

Ensure that when the initial party is on hold and On receipt of a flash-hook event, the SUT performs the following actions:

  • • Request the media gateway to play a dial tone and collect digits
  • • Send a re-INVITE request to place the current call on hold.

On receipt of the dialled digits, the AGCF opens a new dialogue by sending an INVITE request with the following elements:

  • • The dialled digits used as a Request-URI.
  • • An SDP Offer for a voice call.

On receipt of 180 (Ringing) without P Early Media header or with a P Early Media header set to a value different from "sendonly" or from "sendreceive", the AGCF performs the following actions:

  • • Request the media gateway to play a ringback tone

On receipt of 180 (Ringing) or 183 (Session Progress) with a P Early Media header set to "sendonly" or "sendreceive", the AGCF performs the following actions:

  • • Request the media gateway to modify the configuration of the ephemeral termination so as to ensure that the end user will perceive early media.

On receipt of an SDP Answer in a 200 (OK) or in one of the above provisional responses, the AGCF performs the following actions:

  • • Request the media gateway to modify the Remote Descriptor of the ephemeral termination associated with the physical termination representing the analogue line.
| | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------|-------------------|-------------------------------------------------------------|--|--|--|--|------------|--|--|-----------|--|--|------------------------------|-------------------------|---|--|----------------|---|--|-----|---|--|--|--|--|----------------------------|---|--|------------------------------------|---|--|----------------|---|--|-----|---|--|--|--|--|-------------------------|---|---------------------------|----------------|---|--|-----|---|--|--------------------------------|--|--| +| SIP header values
INVITE1 (initial party)
SDP
a=sendonly

200 OK 1
SDP
a=recvonly

INVITE3 (initial party)
SDP
a=sendrecv

200 OK 3
SDP
a=sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Terminating user is connected with the initial party
Flash hook
Dial tone
Dial switching order command
INVITE1 (initial party) ←
200 OK INVITE1 →
ACK ←
 
INVITE2 (additional party) ←
180 Ringing2/183 Session Progress2 →
200 OK INVITE2 →
ACK ←
 
INVITE3 (initial party) ← Three party communication
200 OK INVITE4 →
ACK ←
Apply post test routine
| Test equipment | | End device | Terminating user is connected with the initial party | | | | | Flash hook | | | Dial tone | | | Dial switching order command | INVITE1 (initial party) | ← | | 200 OK INVITE1 | → | | ACK | ← | | | | | INVITE2 (additional party) | ← | | 180 Ringing2/183 Session Progress2 | → | | 200 OK INVITE2 | → | | ACK | ← | | | | | INVITE3 (initial party) | ← | Three party communication | 200 OK INVITE4 | → | | ACK | ← | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Terminating user is connected with the initial party | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (additional party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing2/183 Session Progress2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE3 (initial party) | ← | Three party communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE4 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|------------------------------------------------| +| TSS
3PTY | TP_505_102 | Reference
subclause C.14.2 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6 | +| Test purpose
The served user wishes to reject one of the parties

Ensure that when the three-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If the switching order command indicates that the served user wishes to reject one of the parties, the SUT performs the following actions:
  • • Send a BYE request towards the held party
  • • Request the media gateway to:
    • – Remove the corresponding ephemeral termination
| | | | + +###### **SIP header values** + +INVITE1 (additional party) + SDP + a=sendonly + +200 OK 1 + SDP + a=recvonly + +INVITE2 (initial party) + SDP + a=sendrecv + +200 OK 2 + SDP + a=sendrecv + +###### **Message flow** + +**Test equipment** + +**End device** + +**The initial party is set on hold** + +**A three party conversation is established** + +Flash hook + +INVITE1 (initial party) + +![](44b4968c33b88a9d52190266e51259c5_img.jpg) + +← + +Dial tone + +200 OK INVITE1 + +![](1413e177fe36156824fb4fcf3afdd111_img.jpg) + +→ + +ACK + +![](31ce546ba5115b8bc9b867c394afcf23_img.jpg) + +← + +Dial switching order command + +BYE (additional party) + +![](94fb7d4206117d2241428daf74564257_img.jpg) + +← + +200 OK BYE + +![](6356319d86991e17bd9cc9de978f3635_img.jpg) + +→ + +INVITE2 (initial party) + +![](a7921a00f0d1dda6f9a79ef7c46e09fa_img.jpg) + +← + +Two party ommunication + +200 OK INVITE2 + +![](e61bd54f51868417ae42cfa111083485_img.jpg) + +→ + +ACK + +![](e9d248b85701b0f98ce231ab8786aba1_img.jpg) + +← + +**Apply post test routine** + +| TSS
3PTY | TP_505_103 | Reference
subclause C.14.2 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6
AND 5.3/9 AND 5.3/11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------|--|-----------------------|-------------------|--|-----------------------------------------|--|--|-----------------------------------------------------------------------------------|--|--|--|------------|-----------------------------------|---|-----------|----------------|---|--|-----|---|--|--|--|------------------------------|----------------------------|---|--|----------------|---|--|-----|---|--|-------------------------|---|---------------------------|----------------|---|--|-----|---|--|--|--------------------------------|--| +|

Test purpose
The user establishes a three party conversation (Loose coupling, INVITE method)

Ensure that when the initial party is on hold and a confirmed session with the waiting party exists, a flash hook event applies followed by a switching order command. If the switching order command indicates that the user wishes to establish a three-party conference with the held parties.

  • • Request the media gateway to:
    • – Add a termination to the current context based on SDP information associated with the held party
  • • Send a re INVITE request towards the first held party (i.e., the party that was already held when the flash hook event was detected). The re INVITE request is built as follows:
    • – The Request URI is set to the held party's identity.
    • – The SDP description is set to a=sendrecv. The address and port are set according to the contents of the local descriptor of the new termination.
  • • Send a re INVITE request towards the second held party (i.e., the party that has been held for the purpose of collecting the switch order command). The re INVITE request is built as follows:
    • – The Request URI is set to the held party's identity.
    • – The SDP description is set to a=sendrecv.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
INVITE2 (additional party)
SDP
a=sendrecv

200 OK 2
SDP
a=sendrecv

INVITE3 (initial party)
SDP
a=sendrecv

200 OK 3
SDP
a=sendrecv

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
The initial party is set on hold
Terminating user is connected with the active party (hold or call waiting)
Flash hook
INVITE1 (initial party, sendonly) ← Dial tone
200 OK INVITE1 →
ACK ←
Dial switching order command
INVITE2 (additional party) ←
200 OK INVITE2 →
ACK ←
INVITE3 (initial party) ← Three party communication
200 OK INVITE3 →
ACK ←
Apply post test routine
| | | | | Test equipment | End device | | The initial party is set on hold | | | Terminating user is connected with the active party (hold or call waiting) | | | | Flash hook | INVITE1 (initial party, sendonly) | ← | Dial tone | 200 OK INVITE1 | → | | ACK | ← | | | | Dial switching order command | INVITE2 (additional party) | ← | | 200 OK INVITE2 | → | | ACK | ← | | INVITE3 (initial party) | ← | Three party communication | 200 OK INVITE3 | → | | ACK | ← | | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | The initial party is set on hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Terminating user is connected with the active party (hold or call waiting) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party, sendonly) | ← | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (additional party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE3 (initial party) | ← | Three party communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE3 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
3PTY | TP_505_104 | Reference
subclause C.14.2 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6
AND 5.3/9 AND 5.3/11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|------------------------------------------------------------------------|----------------|--|------------|-----------------------------------------|--|--|--------------------------------------------------|--|--|--|--|------------|-------------------------|---|-----------|----------------|---|--|-----|---|--|--|--|------------------------------|------------------------|---|--|------------|---|--|-------------------------|---|------------------------|----------------|---|--|-----|---|--|--------------------------------|--|--| +| Test purpose
The served user wishes to reject one of the parties(Loose coupling, INVITE method)

Ensure that when the three-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If the switching order command indicates that the served user wishes to reject one of the parties, the SUT performs the following actions:

  • • Send a BYE request towards the held party
  • • Request the media gateway to:
    • – Remove the corresponding ephemeral termination
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1 (additional party)
SDP
a=sendonly

200 OK 1
SDP
a=recvonly

INVITE2 (initial party)
SDP
a=sendrecv

200 OK 2
SDP
a=sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
The initial party is set on hold
A three party conversation is established
Flash hook
INVITE1 (initial party) ← Dial tone
200 OK INVITE1 →
ACK ←
Dial switching order command
BYE (additional party) ←
200 OK BYE →
INVITE2 (initial party) ← Two party ommunication
200 OK INVITE2 →
ACK ←
Apply post test routine
| | | | Test equipment | | End device | The initial party is set on hold | | | A three party conversation is established | | | | | Flash hook | INVITE1 (initial party) | ← | Dial tone | 200 OK INVITE1 | → | | ACK | ← | | | | Dial switching order command | BYE (additional party) | ← | | 200 OK BYE | → | | INVITE2 (initial party) | ← | Two party ommunication | 200 OK INVITE2 | → | | ACK | ← | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| The initial party is set on hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| A three party conversation is established | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party) | ← | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (additional party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (initial party) | ← | Two party ommunication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------|------------------------------------------------------------------------|--|-----------------------|-------------------|--|-----------------------------------------|--|--|-----------------------------------------------------------------------------------|--|--|--|------------|-----------------------------------|---|-----------|----------------|---|--|-----|---|--|--|--|------------------------------|-----------------------------|---|--|----------------|---|--|-----|---|--|-------------------------------|-------|--|--------------|---|--|----------------------------|-------|--| +| TSS
3PTY | TP_505_105 | Reference
subclause C.14.2A of [ETSI TS
183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6
AND 5.3/9 AND 5.3/12 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Test purpose
The user establishes a three party conversation (Loose coupling, REFER method)

Ensure that when the initial party is on hold and a confirmed session with the waiting party exists, a flash hook event applies followed by a switching order command. If the switching order command indicates that the user wishes to establish a three-party conference with the held parties.

  • • Request the media gateway to:
    • – Add a termination to the current context based on SDP information associated with the held party
  • • Send an initial INVITE with the To and the Request URI containing the Conference bridge URI provisioned in the SUT.
  • • Send a REFER request within the existing dialogue with user B with the Refer To header containing the Conference bridge contact URI and the dialogue associated with the B party. The ReferredBy header field is set to the served user's identity.
  • • Send a REFER request within the existing dialogue with user C with the Refer To header containing the Conference bridge contact URI and the dialogue associated with the C party. The ReferredBy header field is set to the served user's identity.

When the SIP end point receives 202 ACCEPTED response to each sent REFER request, it:

  • • performs conference establishment notification;
  • • considers only the call established with the conference bridge as active.

The SIP end point will receive a BYE message in both calls established.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIP header values
INVITE1 (additional party)
SDP
a=sendonly

200 OK 2
SDP
a=recvonly

INVITE2 (Conference bridge URI)

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Message flow

Test equipment End device
The initial party is set on hold
Terminating user is connected with the active party (hold or call waiting)
Flash hook
INVITE1 (initial party, sendonly) ← Dial tone
200 OK INVITE1 →
ACK ←
Dial switching order command
INVITE2 (Conference bridge) ←
200 OK INVITE1 →
ACK ←

REFER1 (additional party)

←
202 ACCEPTED →

REFER2 (initial party)

←
| | | | | Test equipment | End device | | The initial party is set on hold | | | Terminating user is connected with the active party (hold or call waiting) | | | | Flash hook | INVITE1 (initial party, sendonly) | ← | Dial tone | 200 OK INVITE1 | → | | ACK | ← | | | | Dial switching order command | INVITE2 (Conference bridge) | ← | | 200 OK INVITE1 | → | | ACK | ← | |
REFER1 (additional party) |
← | | 202 ACCEPTED | → | |
REFER2 (initial party) |
← | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | The initial party is set on hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Terminating user is connected with the active party (hold or call waiting) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party, sendonly) | ← | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (Conference bridge) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
REFER1 (additional party) |
← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 202 ACCEPTED | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
REFER2 (initial party) |
← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|--------------------------------|---|---------------------------| +| 202 ACCEPTED | → | | +| BYE (initial party) | → | | +| 200 OK BYE | ← | | +| BYE (additional party) | → | | +| 200 OK BYE | ← | Three party communication | +| Apply post test routine | | | + +| TSS
3PTY | TP_505_106 | Reference
subclause C.14.2A of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6
AND 5.3/9 AND 5.3/12 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------------------------------|----------------|--|------------|---------------------------------------------------------------------------------------------|--|--|--|--|------------|-------------------------|---|-----------|----------------|---|--|-----|---|--|--|--|------------------------------|------------------------|---|--|------------|---|--|-------------------------|---|-------------------------|----------------|---|--|-----|---|--|--------------------------------|--|--| +| Test purpose
The served user wishes to reject one of the parties (Loose coupling, REFER method) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that when the three-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If the switching order command indicates that the served user wishes to reject one of the parties, the SUT performs the following actions:

  • • Send a BYE request towards the held party
  • • Request the media gateway to:
    • – Remove the corresponding ephemeral termination
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1 (additional party)
SDP
a=sendonly

200 OK 1
SDP
a=recvonly

INVITE2 (initial party)
SDP
a=sendrecv

200 OK 2
SDP
a=sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
The initial party is set on hold
A three party conversation is established
Flash hook
INVITE1 (initial party) ← Dial tone
200 OK INVITE1 →
ACK ←
Dial switching order command
BYE (additional party) ←
200 OK BYE →
INVITE2 (initial party) ← Two party communication
200 OK INVITE2 →
ACK ←
Apply post test routine
| | | | Test equipment | | End device | The initial party is set on hold
A three party conversation is established | | | | | Flash hook | INVITE1 (initial party) | ← | Dial tone | 200 OK INVITE1 | → | | ACK | ← | | | | Dial switching order command | BYE (additional party) | ← | | 200 OK BYE | → | | INVITE2 (initial party) | ← | Two party communication | 200 OK INVITE2 | → | | ACK | ← | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| The initial party is set on hold
A three party conversation is established | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party) | ← | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (additional party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (initial party) | ← | Two party communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------------------------------|-----------------------|--|-------------------|-----------------------------------------|--|--|-----------------------------------------------------------------------------------|--|--|--|--|------------|-----------------------------------|---|-----------|----------------|---|--|-----|---|--|--|--|------------------------------|-----------------------------|---|--|----------------|---|--|-----|---|--|--|--|---------------------------|--------------------------------|--|--| +| TSS
3PTY | TP_505_107 | Reference
subclause C.14.2B of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6
AND 5.3/9 AND 5.3/13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The user establishes a three party conversation (Loose coupling INVITE request with URI list)

Ensure that when the initial party is on hold and a confirmed session with the waiting party exists, a flash hook event applies followed by a switching order command if the switching order command indicates that the user wishes to establish a three-party conference with the held parties.
SUT creates a conference and invites user B and user C to the conference by sending an INVITE to the Conference Factory URI including URI list in the INVITE request. SUT indicates the particular dialogues which can be re used for this conference in the uri list by ? mechanism. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1 (additional party)
SDP
a=sendonly

200 OK 2
SDP
a=recvonly

INVITE2 (Conference bridge URI)




| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
The initial party is set on hold
Terminating user is connected with the active party (hold or call waiting)
Flash hook
INVITE1 (initial party, sendonly) ← Dial tone
200 OK INVITE1 →
ACK ←
Dial switching order command
INVITE2 (Conference bridge) ←
200 OK INVITE1 →
ACK ←
Three party communication
Apply post test routine
| | | | Test equipment | | End device | The initial party is set on hold | | | Terminating user is connected with the active party (hold or call waiting) | | | | | Flash hook | INVITE1 (initial party, sendonly) | ← | Dial tone | 200 OK INVITE1 | → | | ACK | ← | | | | Dial switching order command | INVITE2 (Conference bridge) | ← | | 200 OK INVITE1 | → | | ACK | ← | | | | Three party communication | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| The initial party is set on hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Terminating user is connected with the active party (hold or call waiting) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party, sendonly) | ← | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (Conference bridge) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Three party communication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
3PTY | TP_505_108 | Reference
subclause C.14.2B of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND
5.3/6 AND 5.3/9 AND
5.3/13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|---------------------------------------------------------------------------|----------------|--|------------|---------------------------------------------------------------------------------------------|--|--|--|--|------------|-------------------------|---|-----------|----------------|---|--|-----|---|--|--|--|------------------------------|------------------------|---|--|------------|---|--|-------------------------|---|------------------------|----------------|---|--|-----|---|--|--------------------------------|--|--| +| Test purpose
The served user wishes to reject one of the parties (Loose coupling INVITE request with URI list)

Ensure that when the three-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If the switching order command indicates that the served user wishes to reject one of the parties, the SUT performs the following actions:
  • Send a BYE request towards the held party
  • Request the media gateway to:
    • Remove the corresponding ephemeral termination
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1 (additional party)
SDP
a=sendonly

200 OK 1
SDP
a=recvonly

INVITE2 (initial party)
SDP
a=sendrecv

200 OK 2
SDP
a=sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
The initial party is set on hold
A three party conversation is established
Flash hook
INVITE1 (initial party) ➔ Dial tone
200 OK INVITE1 ➔
ACK ➔
Dial switching order command
BYE (additional party) ➔
200 OK BYE ➔
INVITE2 (initial party) ➔ Two party ommunication
200 OK INVITE2 ➔
ACK ➔
Apply post test routine
| | | | Test equipment | | End device | The initial party is set on hold
A three party conversation is established | | | | | Flash hook | INVITE1 (initial party) | ➔ | Dial tone | 200 OK INVITE1 | ➔ | | ACK | ➔ | | | | Dial switching order command | BYE (additional party) | ➔ | | 200 OK BYE | ➔ | | INVITE2 (initial party) | ➔ | Two party ommunication | 200 OK INVITE2 | ➔ | | ACK | ➔ | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| The initial party is set on hold
A three party conversation is established | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party) | ➔ | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (additional party) | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (initial party) | ➔ | Two party ommunication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|-------------------------------------------------------------| +| TSS
3PTY | TP_505_109 | Reference
clause C.14.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6
AND 5.3/9 | +|

Test purpose
The user establishes a three party conversation (Tight coupling)

Ensure that when the initial party is on hold and a confirmed session with the waiting party exists, a flash hook event applies. On receipt of a notification of Register RECALL from the SUT, the SUT opens a new dialogue (D3) and sends an INVITE (flash) to an originating AS. This INVITE includes the following:

  • • The Request URI is structured as follows:
    • – A user part containing "flash".
    • – A domain name that together with the user part provides sufficient information for the AS Network to forward the request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g. "flash@pes.operator.com"
  • • A From header containing the public identity of the line on which the RECALL occurred.
  • • An SDP offer for a speech call.

The AGCF now awaits receipt of a 484 Address Incomplete from the originating AS, and when received the AGCF takes the following actions:

  • • Requests the A MGW to play Dial Tone and collect one digit.
  • • Sends an INVITE (D3) containing this single digit (as this is a Recall sequence with more than one active dialogue) and await receipt of 200 OK (Invite) or a failure response code. This INVITE is built in the same way as the previous INVITE except that the dialled digit replaces "flash".

The AGCF then awaits a re INVITE (D2) with the SDP of a Media Server in the AS Network (acting as a 3 party bridge) and when received it takes the following actions:

  • • Sends an instruction to the A MGW to change the address to which RTP packets are sent and from which they are received (e.g. it modifies the ITU-T H.248 Remote Descriptor).

Sends a 200 OK (Invite) to the AS, awaits receipt of a BYE to end dialogue D3, and when this is received it sends a 200 OK (Bye).

SIP header values
INVITE D2-1
Request-Line: flash@pes.operator.com

INVITE D2-2
Request-Line: flash@pes.operator.com

INVITE3 (additional party)
SDP
a=sendrecv

200 OK 3
SDP
a=sendrecv

INVITE4 (initial party)
SDP
a=sendrecv

200 OK 4
SDP
a=sendrecv

| | | | + +![](a9fa083478f6c517e7970c46d1b928e9_img.jpg) + +| Message flow | | | +|-----------------------------------|-----------------------------------------------------------------------------------|------------------------------| +| | Test equipment | End device | +| | The initial party is set on hold | | +| | Terminating user is connected with the active party (hold or call waiting) | | +| | | Flash hook | +| INVITE1 (initial party, sendonly) | ← | | +| 200 OK INVITE1 | → | | +| ACK | ← | | +| INVITE D2-1 | ← | | +| 484 Address Incomplete | → | | +| ACK | ← | | +| | | Dial tone | +| INVITE D2-2 | ← | Dial switching order command | +| 180 Ringing | → | | +| 200 OK INVITE2 | → | | +| ACK | ← | | +| | | Flash hook | +| INVITE1 (D2-2) | ← | | +| 200 OK INVITE1 | → | | +| ACK | ← | | +| INVITE (D3-1) | ← | | +| 484 Address Incomplete | → | | +| ACK | ← | | +| INVITE3 (additional party) | ← | | +| 200 OK INVITE3 | → | | +| ACK | ← | | +| INVITE4 (initial party) | ← | Three party communication | +| 200 OK INVITE4 | → | | +| ACK | ← | | +| | Apply post test routine | | + +| TSS
3PTY | TP_505_110 | Reference
C.14.2B of [ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/6
AND 5.3/9 AND 5.3/13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------|------------------------------------------------------------------------|----------------|--|------------|-----------------------------------------|--|--|--------------------------------------------------|--|--|--|--|------------|-------------------------|---|-----------|----------------|---|--|-----|---|--|--|--|------------------------------|------------------------|---|--|------------|---|--|-------------------------|---|------------------------|----------------|---|--|-----|---|--|--------------------------------|--|--| +| Test purpose
The served user wishes to reject one of the parties (Loose coupling INVITE request with URI list)

Ensure that when the three-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If the switching order command indicates that the served user wishes to reject one of the parties, the SUT performs the following actions:

  • • Send a BYE request towards the held party
  • • Request the media gateway to:
    • – Remove the corresponding ephemeral termination
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1 (additional party)
SDP
a=sendonly

200 OK 1
SDP
a=recvonly

INVITE2 (initial party)
SDP
a=sendrecv

200 OK 2
SDP
a=sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
The initial party is set on hold
A three party conversation is established
Flash hook
INVITE1 (initial party) ← Dial tone
200 OK INVITE1 →
ACK ←
Dial switching order command
BYE (additional party) ←
200 OK BYE →
INVITE2 (initial party) ← Two party ommunication
200 OK INVITE2 →
ACK ←
Apply post test routine
| | | | Test equipment | | End device | The initial party is set on hold | | | A three party conversation is established | | | | | Flash hook | INVITE1 (initial party) | ← | Dial tone | 200 OK INVITE1 | → | | ACK | ← | | | | Dial switching order command | BYE (additional party) | ← | | 200 OK BYE | → | | INVITE2 (initial party) | ← | Two party ommunication | 200 OK INVITE2 | → | | ACK | ← | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| The initial party is set on hold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| A three party conversation is established | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party) | ← | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE (additional party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (initial party) | ← | Two party ommunication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +##### 7.2.5.5.2 Test purposes for ISDN + +| | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------------|----------|--------------------------------------------------------------------------------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------------------------------------------------------------|----------|---------------------------------------------------------------| +| TSS
3PTY | TP_505_201 | Reference
subclause 5.2.13 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/6
AND 5.6/7 | | | | | | | | | +|

Test purpose
Conference creation by three-way session creation. REFER request to the Focus, Conference notification service is subscribed

The conference creator is participating in two SIP sessions (S1 and S2) which are put on hold and wants to join together two of these active sessions to a so-called three-way session. The conference notification service is subscribed. The conference creator shall perform the following steps:

  • • Create a conference at the conference factory by sending an INVITE request with the conference factory URI. Receive and store the conference URI in the 200 OK response.
  • • For each of the active sessions, that are requested to be joined to a three-way session, send two REFER requests with the Request URI indicating the previously received conference URI and the Refer-To header indicating the SIP URI or tel URL of the respective remote user.
  • • The conference creator releases the sessions 1 and 2 after the receipt of NOTIFY requests indicating that the remote users have successfully joined the three-way session.

SIP header values
INVITE1
Request Line user inactive idle stae
SDP a=sendonly

INVITE2
Request Line = conference factory URI
Contact: ; isfocus

SUBSCRIBE
Request URI contained the conference URI
Event: conference"

NOTIFY 1 Event contains conference; Subscription-State contains active; expires=[any value]

REFER1
Request URI indicating the conference URI
Refer-to header contains URI of remote user 1

REFER2
Request URI indicating the conference URI
Refer-to header contains URI of remote user 2

NOTIFY 2 Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying
NOTIFY 3 Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 200 OK
application/conference-info+xml contains (S1) connected, dialled-in
NOTIFY 4 Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying
NOTIFY 5 Event contains conference; Subscription-State contains active
| | | | NOTIFY 2 | Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying | NOTIFY 3 | Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 200 OK
application/conference-info+xml contains (S1) connected, dialled-in | NOTIFY 4 | Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying | NOTIFY 5 | Event contains conference; Subscription-State contains active | +| NOTIFY 2 | Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying | | | | | | | | | | | +| NOTIFY 3 | Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 200 OK
application/conference-info+xml contains (S1) connected, dialled-in | | | | | | | | | | | +| NOTIFY 4 | Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying | | | | | | | | | | | +| NOTIFY 5 | Event contains conference; Subscription-State contains active | | | | | | | | | | | + +###### **DSS1 Parameter values** + +FACILITY + +Begin3PTY-Inv + +Call reference of call A-B + +###### **Message flow** + +**Test equipment****Test equipment** + +Session 1 is in active hold state + +Session 2 is in active idle state + +FACILITY + +→ + +→ INVITE1 + +← 200 OK + +→ ACK + +→ SUBSCRIBE + +← 200 OK + +← NOTIFY 1 + +→ 200 OK NOTIFY + +→ INVITE2 + +← 200 OK + +→ ACK + +→ REFER1 + +← 200 OK REFER + +← NOTIFY 2 (S1, 100) + +→ 200 OK NOTIFY + +← NOTIFY 3 (S1, 200) + +→ 200 OK NOTIFY + +DISCONNECT 1 + +← + +← BYE S1 + +RELEASE COMPLETE + +→ + +→ 200 OK (BYE) + +→ REFER2 + +← 200 OK REFER + +← NOTIFY 4 (S2, 100) + +→ 200 OK NOTIFY + +← NOTIFY 5 (S1, 200) + +→ 200 OK NOTIFY + +DISCONNECT 2 + +← + +← BYE S2 + +RELEASE COMPLETE + +→ + +→ 200 OK (BYE) + +**Apply post test routine** + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------|-------------------------------------------------------------| +| TSS
3PTY | TP_505_202 | Reference
5.2.13 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/6
AND 5.6/7 | +|

Test purpose
Conference creation by three-way session creation. REFER request to the user, Conference notification service is subscribed.

The conference creator is participating in two SIP sessions (S1 and S2) which are put on hold and wants to join two of these active sessions to a so-called three-way session. The conference notification service is subscribed. The conference creator shall perform the following steps:

  • • Create a conference at the conference factory by sending an INVITE request with the conference factory URI. Receive and store the conference URI in the 200 OK response.
  • • For each of the active sessions, that are requested to be joined to a three-way session, send two REFER requests with the Request URI indicating SIP URI or tel URL of the respective remote user and the Refer-To header indicating the previously received conference URI.
  • • The conference creator releases the sessions 1 and 2 after the receipt of NOTIFY requests indicating that the remote users have successfully joined the three-way session.

SIP header values
INVITE1
Request Line user inactive idle state
SDP a=sendonly

INVITE2
Request Line = conference factory URI
Contact: ; isfocus

SUBSCRIBE
Request URI contained the conference URI
Event: conference"

NOTIFY 1 Event contains conference; Subscription-State contains active; expires=[any value]

REFER1
Request URI indicating the conference URI
Refer-to header contains URI of remote user 1

REFER2
Request URI indicating the conference URI
Refer-to header contains URI of remote user 2

NOTIFY 2 Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying

NOTIFY 3 Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 200 OK
application/conference-info+xml contains (S1) connected, dialled-in

NOTIFY 4 Event contains conference; Subscription-State contains active
message/sipfrag contains SIP/2.0 100 Trying

NOTIFY 5 Event contains conference; Subscription-State contains active

DSS1 Parameter values
FACILITY
Begin3PTY-Inv
Call reference of call A-B

| | | | + +![](de70c0659dc06d1b83269bbc0279e314_img.jpg) + +**Message flow** + +| | Test equipment | | Test equipment | +|-------------------|-----------------------|------------------------------------------|-----------------------| +| | | Session 1 is in active hold state | | +| | | Session 2 is in active idle state | | +| FACILITY | → | → | INVITE1 | +| | | ← | 200 OK | +| | | → | ACK | +| | | → | SUBSCRIBE | +| | | ← | 200 OK | +| | | ← | NOTIFY 1 | +| | | → | 200 OK NOTIFY | +| | | → | INVITE2 | +| | | ← | 200 OK | +| | | → | ACK | +| | | → | REFER1 | +| | | ← | 200 OK REFER | +| | | ← | NOTIFY 2 (S1, 100) | +| | | → | 200 OK NOTIFY | +| | | ← | NOTIFY 3 (S1, 200) | +| | | → | 200 OK NOTIFY | +| RELEASE COMPLETE1 | → | → | BYE S1 | +| | | ← | 200 OK (BYE) | +| | | → | REFER2 | +| | | ← | 200 OK REFER | +| | | ← | NOTIFY 4 (S2, 100) | +| | | → | 200 OK NOTIFY | +| | | ← | NOTIFY 5 (S1, 200) | +| | | → | 200 OK NOTIFY | +| RELEASE COMPLETE2 | → | → | BYE S2 | +| | | ← | 200 OK (BYE) | +| | | Apply post test routine | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------------|-----------------------------------------------------------------|--|-----------------------|--|-----------------------|--|--|------------------------------------------|--|--|--|------------------------------------------|--|----------|---|---|---------|--|--|---|--------|--|--|---|-----|------|--|--|--|--|--|---|---------|--|--|---|--------|--|--|---|-----|------|--|--|--|--|--|---|--------|--|--|---|--------------| +| TSS
3PTY | TP_505_203 | Reference
subclause 5.2.13 of [ETSI
TS 183 036] | Selection expression
PICS 5.1.1/2 AND NOT 5.4/6
AND 5.6/7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Conference creation by three-way session creation. REFER request to the Focus, Conference notification service not subscribed

The conference creator is participating in two SIP sessions (S1 and S2) which are put on hold and wants to join two of these active sessions to a so-called three-way session. The conference notification service is not subscribed. The conference creator shall perform the following steps:

  • • Create a conference at the conference factory by sending an INVITE request with the conference factory URI. Receive and store the conference URI in the 200 OK response.
  • • For each of the active sessions, that are requested to be joined to a three-way session, send two REFER requests with the Request URI indicating the previously received conference URI and the Refer-To header indicating the SIP URI or tel URI of the respective remote user.

The remote instance disconnects the previously held sessions.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1
SDP a=sendonly

INVITE2
Request Line = conference factory URI
Contact: ...; isfocus

REFER1
Request URI indicating the conference URI
Refer-to header contains URI of remote user 1

REFER2
Request URI indicating the conference URI
Refer-to header contains URI of remote user 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
FACILITY
Begin3PTY-Inv
Call reference of call A-B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
Session 1 is in active hold state
Session 2 is in active idle state
FACILITY ➔ ➔ INVITE1
⬅ 200 OK
➔ ACK

➔ INVITE2
⬅ 200 OK
➔ ACK

➔ REFER1
⬅ 200 OK REFER
| | | | | Test equipment | | Test equipment | | | Session 1 is in active hold state | | | | Session 2 is in active idle state | | FACILITY | ➔ | ➔ | INVITE1 | | | ⬅ | 200 OK | | | ➔ | ACK |
| | | | | | ➔ | INVITE2 | | | ⬅ | 200 OK | | | ➔ | ACK |
| | | | | | ➔ | REFER1 | | | ⬅ | 200 OK REFER | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Session 1 is in active hold state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Session 2 is in active idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| FACILITY | ➔ | ➔ | INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | REFER1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 200 OK REFER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|--------------------------------|---|----------------| +| DISCONNECT 2 | ← | ← BYE S1 | +| RELEASE COMPLETE | → | → 200 OK (BYE) | +| | | → REFER2 | +| | | ← 200 OK REFER | +| DISCONNECT 2 | ← | ← BYE S2 | +| RELEASE COMPLETE | → | → 200 OK (BYE) | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|-------------------------------------------------------------| +| TSS
3PTY | TP_505_204 | Reference
subclause 5.2.13 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/6
AND 5.6/7 | +| Test purpose
Conference creation by three-way session creation. REFER request to the Focus, Conference notification service not subscribed | | | | +|

The conference creator is participating in two SIP sessions (S1 and S2) which are put on hold and wants to join two of these active sessions to a so-called three-way session. The conference notification service is not subscribed. The conference creator shall perform the following steps:

| | | | +|
  • • Create a conference at the conference factory by sending an INVITE request with the conference factory URI. Receive and store the conference URI in the 200 OK response.
  • • For each of the active sessions, that are requested to be joined to a three-way session, send two REFER requests with the Request URI indicating the previously received conference URI and the Refer-To header indicating the SIP URI or tel URI of the respective remote user.
| | | | +|

The SUT disconnects the previously held sessions.

| | | | +| SIP header values
INVITE1
SDP a=sendonly

INVITE2
Request Line = conference factory URI
Contact: ...; isfocus

REFER1
Request URI indicating the conference URI
Refer-to header contains URI of remote user 1

REFER2
Request URI indicating the conference URI
Refer-to header contains URI of remote user 2 | | | | +| DSS1 Parameter values
FACILITY
Begin3PTY-Inv
Call reference of call A-B | | | | + +| Message flow | | | +|------------------------------------------------------------------------|----------------|--------------------------------| +| | Test equipment | Test equipment | +| Session 1 is in active hold state
Session 2 is in active idle state | | | +| FACILITY | → | → INVITE1
← 200 OK
→ ACK | +| | | → INVITE2
← 200 OK
→ ACK | +| | | → REFER1
← 200 OK REFER | +| RELEASE COMPLETE1 | → | → BYE S1
← 200 OK (BYE) | +| | | → REFER2
← 200 OK REFER | +| RELEASE COMPLETE2 | → | → BYE S2
← 200 OK (BYE) | +| Apply post test routine | | | + +| TSS
3PTY | TP_505_205 | Reference
subclause 5.2.13 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND
5.6/7AND 5.4/8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------------------|------------------------------------------------------------|--|----------------|------------|--|-----------------------------------|--|-------|---|--|--------------|---|--|-----------|---|--|--------|---|--|-----|---|--|--------|---|--------------------|--------------|---|--|-------------------------|--|--| +| Test purpose
The user equipment has the capability join a conference. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the user equipment on receipt of a REFER request that contains a Refer-To header indicating a conference URI including the “method” parameter set to INVITE and contains a Referred-By header, sends an INVITE request to the conference URI including the received Referred-By header.
The SUT disconnects the previously held session. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
REFER: Refer-To=conference URI; method=INVITE
Referred-By=Remote user equipment URI
INVITE S2: Request URI indicating the received conference URI
Referred-By=Remote user equipment URI | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
A session is in active hold state
REFER→
200 OK REFER←
INVITE S2←
200 OK→
ACK←
BYE S1←← RELEASE COMPLETE
200 OK (BYE)→
Apply post test routine
| | | | | Test equipment | End device | | A session is in active hold state | | REFER | → | | 200 OK REFER | ← | | INVITE S2 | ← | | 200 OK | → | | ACK | ← | | BYE S1 | ← | ← RELEASE COMPLETE | 200 OK (BYE) | → | | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A session is in active hold state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK REFER | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE S2 | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE S1 | ← | ← RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (BYE) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|----------------------------------------------------|----------------------------------------------------------|--|-----------------------|-------------------|--|------------------------------------------|--|-------|---|--|--------------|---|--|---------------|-------|--|--------|---|--|-----|---|--|------------|-------|------------------|--------------|---|--------------------|--|--------------------------------|--| +| TSS | TP_505_206 | Reference
subclause 5.2.13 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.6/7 AND 5.4/8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The user equipment has the capability join a conference.

Ensure that the user equipment on receipt of a REFER request that contains a Refer-To header indicating a conference URI including the “method” parameter set to INVITE and contains a Referred-By header, sends an INVITE request to the conference URI including the received Referred-By header.
The remote instance disconnects the previously held session. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
REFER: Refer-To=conference URI; method=INVITE
Referred-By=Remote User Equipment URI
INVITE S2: Request URI indicating the received conference URI
Referred-By=Remote User Equipment URI | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
A session is in active hold state
REFER ➔
200 OK REFER ⬅

INVITE S2

⬅
200 OK ➔
ACK ⬅

BYE S1

➔

➔ DISCONNECT
200 OK (BYE) ⬅ ⬅ RELEASE COMPLETE
Apply post test routine
| | | | | Test equipment | End device | | A session is in active hold state | | REFER | ➔ | | 200 OK REFER | ⬅ | |
INVITE S2 |
⬅ | | 200 OK | ➔ | | ACK | ⬅ | |
BYE S1 |
➔ |
➔ DISCONNECT | 200 OK (BYE) | ⬅ | ⬅ RELEASE COMPLETE | | Apply post test routine | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | A session is in active hold state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK REFER | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
INVITE S2 |
⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
BYE S1 |
➔ |
➔ DISCONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (BYE) | ⬅ | ⬅ RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|---------------------------------------------------------------------| +| TSS
3PTY | TP_505_207 | Reference
subclause 5.2.13 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/6 AND 5.6/7 AND 5.3/13 | +| Test purpose
The user equipment has the capability to invite a participant to the conference. Resource list is used

Ensure that the SUT is able to send a resource list to the conference AS to invite participant(s) to a conference. The remote instance disconnects the previously held sessions. | | | | +| | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--|-----------------------|--|-----------------------|--|-----------------------|--|-----------------------------------|--|--|--|-----------------------------------|--|--|----------|---|--|-----------|--|--|--|----------|--|--|--|-------|--|--|--|---------------|--|--|--|----------|--|--|--|-------|--------------|---|--|----------|------------------|---|--|----------------|--------------|---|--|----------|------------------|---|--|----------------|--|--------------------------------|--|--| +| SIP header values
INVITE1
SDP a=sendonly

INVITE2
Request Line = conference factory URI
Contact: ...; isfocus
Content-Type: application/resource-lists+xml
Content-Disposition: recipient-list






| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
FACILITY
Begin3PTY-Inv
Call reference of call A-B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentTest equipment
Session 1 is in active hold state
Session 2 is in active idle state
FACILITY➔➔ INVITE1
⬅ 200 OK
➔ ACK

➔ INVITE2
⬅ 200 OK
➔ ACK
DISCONNECT 2⬅⬅ BYE S1
RELEASE COMPLETE➔➔ 200 OK (BYE)
DISCONNECT 2⬅⬅ BYE S2
RELEASE COMPLETE➔➔ 200 OK (BYE)
Apply post test routine
| | | | | Test equipment | | Test equipment | | Session 1 is in active hold state | | | | Session 2 is in active idle state | | | FACILITY | ➔ | | ➔ INVITE1 | | | | ⬅ 200 OK | | | | ➔ ACK | | | |
➔ INVITE2 | | | | ⬅ 200 OK | | | | ➔ ACK | DISCONNECT 2 | ⬅ | | ⬅ BYE S1 | RELEASE COMPLETE | ➔ | | ➔ 200 OK (BYE) | DISCONNECT 2 | ⬅ | | ⬅ BYE S2 | RELEASE COMPLETE | ➔ | | ➔ 200 OK (BYE) | | Apply post test routine | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Session 1 is in active hold state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Session 2 is in active idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| FACILITY | ➔ | | ➔ INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | |
➔ INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT 2 | ⬅ | | ⬅ BYE S1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | ➔ | | ➔ 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT 2 | ⬅ | | ⬅ BYE S2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | ➔ | | ➔ 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|------------------------------------------------------------------------| +| TSS
3PTY | TP_505_208 | Reference
subclause 5.2.13 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/6
AND 5.6/7 AND 5.3/13 | +| Test purpose
The user equipment has the capability to invite a participant to the conference. Resource list is used

Ensure that the SUT is able to send a resource list to the conference AS to invite participant(s) to a conference. The SUT disconnects the previous held sessions. | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--|-----------------------|-----------------------|--|-----------------------|--|-----------------------------------|--|--|--|-----------------------------------|--|--|----------|---|--|-----------|--|--|--|----------|--|--|--|-------|--|--|--|-----------|--|--|--|----------|--|--|--|-------|-------------------|---|--|----------|--|--|--|----------------|-------------------|---|--|----------|--|--|--|----------------|--|--------------------------------|--|--| +| SIP header values
INVITE1
SDP a=sendonly

INVITE2
Request Line = conference factory URI
Contact: ...; isfocus
Content-Type: application/resource-lists+xml
Content-Disposition: recipient-list






| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
FACILITY
Begin3PTY-Inv
Call reference of call A-B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
Session 1 is in active hold state
Session 2 is in active idle state
FACILITY ➔ ➔ INVITE1
⬅ 200 OK
➔ ACK
➔ INVITE2
⬅ 200 OK
➔ ACK
RELEASE COMPLETE1 ➔ ➔ BYE S1
⬅ 200 OK (BYE)
RELEASE COMPLETE2 ➔ ➔ BYE S2
⬅ 200 OK (BYE)
Apply post test routine
| | | | Test equipment | | Test equipment | | Session 1 is in active hold state | | | | Session 2 is in active idle state | | | FACILITY | ➔ | | ➔ INVITE1 | | | | ⬅ 200 OK | | | | ➔ ACK | | | | ➔ INVITE2 | | | | ⬅ 200 OK | | | | ➔ ACK | RELEASE COMPLETE1 | ➔ | | ➔ BYE S1 | | | | ⬅ 200 OK (BYE) | RELEASE COMPLETE2 | ➔ | | ➔ BYE S2 | | | | ⬅ 200 OK (BYE) | | Apply post test routine | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Session 1 is in active hold state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Session 2 is in active idle state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| FACILITY | ➔ | | ➔ INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE1 | ➔ | | ➔ BYE S1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE2 | ➔ | | ➔ BYE S2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ⬅ 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.5.6 Closed User Group (CUG) + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
CUG | TP_506_001 | Reference
subclause 5.2.9.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/9 | +| Test purpose
Setup for a CUG call with outgoing access request CUG index present

Ensure that on receipt of an DSS1 SETUP message containing a Facility Information Element with CUGCallOperation invoke component, an SIP INVITE request is sent. The INVITE request contains an 'cug' XML MIME body. The cugCallOperation element contains the outgoingAccessRequest element is mapped from the DSS1 outgoingAccessRequest parameter set to 'TRUE' and the cugIndex element is mapped from the DSS1 cUGIndex parameter. | | | | + +| SIP header values
INVITE:
cug
cugCallOperation
outgoingAccessRequest>true<
cugIndex>[mapped from cUGIndex]< | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------------------|------------|--|----------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------| +| DSS1 Parameter values
SETUP:
Facility
CUGCallOperation invoke
outgoingAccessRequest TRUE
cUGIndex configured index value | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying

Apply post test routine

| | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | + +| TSS
CUG | TP_505_002 | Reference
subclasue 5.2.9.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/9 | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------| +| Test purpose
Setup for a CUG call with outgoing access request CUG index not present | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a DSS1 SETUP message containing a Facility Information Element with CUGCallOperation invoke component, a SIP INVITE request is sent. The INVITE request contains an 'cug' XML MIME body. The cugCallOperation element that contains the outgoingAccessRequest element is mapped from the DSS1 outgoingAccessRequest parameter set to 'TRUE' and the DSS1 cUGIndex parameter is not present. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
cug
cugCallOperation
outgoingAccessRequest>true< | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP:
Facility
CUGCallOperation invoke
outgoingAccessRequest TRUE | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying

Apply post test routine

| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------| +| TSS
CUG | TP_505_003 | Reference
subclause 5.2.9.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/9 | | | | | | | | | | | | | | | | | | | +|

Test purpose
Setup for a CUG call without outgoing access request CUG index present

Ensure that on receipt of a DSS1 SETUP message containing a Facility Information Element with CUGCallOperation invoke component, a SIP INVITE request is sent. The INVITE request contains a 'cug' XML MIME body. The cugCallOperation element that contains the outgoingAccessRequest element is mapped from the DSS1 outgoingAccessRequest parameter set to 'FALSE' and the cugIndex element is mapped from the DSS1 cUGIndex parameter.

SIP header values
INVITE:
1)            cug
              cugCallOperation
                  outgoingAccessRequest>false<
                  cugIndex>[mapped from cUGIndex]<

DSS1 Parameter values
SETUP:
              Facility
                  CUGCallOperation invoke
                      outgoingAccessRequest FALSE
                      cUGIndex configured index value

Message flow

End device Test equipment
SETUP ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
SETUP ACKNOWLEDGE ⬅ 100 Trying

Apply post test routine

| | | | | End device | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | +| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|------------------------------------------------| +| TSS
CUG | TP_505_004 | Reference
clause 5.2.9.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/9 | +|

Test purpose
Setup for a CUG call without outgoing access request CUG index not present

Ensure that on receipt of a DSS1 SETUP message containing a Facility Information Element with CUGCallOperation invoke component, a SIP INVITE request is sent. The INVITE request contains a 'cug' XML MIME body. The cugCallOperation element that contains the outgoingAccessRequest element is mapped from the DSS1 outgoingAccessRequest parameter set to 'FALSE' and the DSS1 cUGIndex parameter is not present.

SIP header values
INVITE:
1)            cug
              cugCallOperation
                  outgoingAccessRequest>false<

| | | | + +| | | +|---------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DSS1 Parameter values
SETUP:
Facility
CUGCallOperation invoke
outgoingAccessRequest FALSE | | +| Message flow | | +| End device | Test equipment | +| SETUP | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE | +| SETUP ACKNOWLEDGE | ← 100 Trying | +| Apply post test routine | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------| +| TSS
CUG | TP_505_005 | Reference
subclause 5.2.9.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/9 | +| Test purpose
Setup for a CUG call with outgoing access request is rejected | | | | +| Ensure that on receipt of a DSS1 SETUP message containing a Facility Information Element with CUGCallOperation invoke component, the DSS1 outgoingAccessRequest element is set to 'TRUE' and the DSS1 cUGIndex parameter is not present. If the AGCF/VGW receives a 403 Forbidden final response a DSS1 RELEASE COMPLETE message is sent and a Facility Information Element is present. The CUGCallOperation Return Error component is set to 'inconsistencyInDesignatedFacilityAndSubscriberClass'. | | | | +| SIP header values
INVITE:
Cug
cugCallOperation
outgoingAccessRequest>true< | | | | +| DSS1 Parameter values
SETUP:
Facility
CUGCallOperation invoke
outgoingAccessRequest TRUE

RELEASE COMPLETE
CUGCallOperation Return Error
inconsistencyInDesignatedFacilityAndSubscriberClass | | | | +| Message flow | | | | +| End device | | | Test equipment | +| SETUP | | → INVITE | | +| | | ← 407 Proxy Authentication Required | | +| | | → ACK | | +| | | → INVITE | | +| | | ← 403 Forbidden | | +| CASE A | | | | +| RELEASE COMPLETE | | ← | | + +| | | +|------------------|-------| +| CASE B | | +| DISCONNECT | ← | +| RELEASE COMPLETE | → | +| | → ACK | + +| TSS
CUG | TP_505_006 | Reference
subclause 5.2.9.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--|---|---------------|---------------|--|--|--|------------------|--|---|--|---------------|--|--|--|------------|--|---|--|------------------|--|---|--|--|--|---|-----| +| Test purpose
Setup for a CUG call without outgoing access request is rejected

Ensure that on receipt of a DSS1 SETUP message containing a Facility Information Element with CUGCallOperation invoke component, the DSS1 outgoingAccessRequest element is set to 'FALSE' and the DSS1 cUGIndex parameter is not present. If the AGCF/VGW receives a 403 Forbidden final response a DSS1 RELEASE COMPLETE message is sent and a Facility Information Element is present. The CUGCallOperation Return Error component is set to 'inconsistencyInDesignatedFacilityAndSubscriberClass'

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE:
Cug
cugCallOperation
outgoingAccessRequest>false< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP:
Facility
CUGCallOperation invoke
outgoingAccessRequest FALSE

RELEASE COMPLETE
CUGCallOperation Return Error
inconsistencyInDesignatedFacilityAndSubscriberClass | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
SETUP → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
← 403 Forbidden
CASE A
RELEASE COMPLETE ←
CASE B
DISCONNECT ←
RELEASE COMPLETE →
→ ACK
| | | | | End device | | Test equipment | SETUP | | → | INVITE | | | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | | | ← | 403 Forbidden | CASE A | | | | RELEASE COMPLETE | | ← | | CASE B | | | | DISCONNECT | | ← | | RELEASE COMPLETE | | → | | | | → | ACK | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 403 Forbidden | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DISCONNECT | | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.5.7 Communication waiting + +##### 7.2.5.7.1 Test purposes for POTS + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|-------------------------------------------------|--|-----------------------|--|-------------------|---------|---|--|---------|-------------|---|--|--|---------------|---|--|----------|-----|---|--|--|--|--|--|--|---------|---|--|--|-------------|---|--|-------------------------| +| TSS
CW | TP_507_101 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The terminating user receives indication “a call is waiting”

Ensure that when a terminating user in a confirmed session receives an INVITE request to another dialogue, the SUT sends a 180 Ringing. The user is informed that a call is waiting. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 → Ringing
180 Ringing ←
200 OK INVITE ← Off hook
ACK →
 
INVITE2 →
180 Ringing ← Call waiting indication
Apply post test routine
| | | | | Test equipment | | End device | INVITE1 | → | | Ringing | 180 Ringing | ← | | | 200 OK INVITE | ← | | Off hook | ACK | → | | | | | | | INVITE2 | → | | | 180 Ringing | ← | | Call waiting indication | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | Call waiting indication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------|-------------------------------------------------|--|-----------------------|--|-------------------|---------|---|--|---------|-------------|---|--|--|---------------|---|--|----------|-----|---|--|--|--|--|--|--|---------|---|--|--|-------------|---|------------------------------|-------------------------|--|--|-------------------------------|--|----------------|---|--|--|-----|---|--|--| +| TSS
CW | TP_507_102 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The terminating user receives indication “a call is waiting” ignored

Ensure that when a terminating user in a confirmed session receives an INVITE request to another dialogue, the SUT sends a 180 Ringing. The user ignores the waiting call, when the answer timer expires the SUT sends a 486 (Busy Here) response. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 → Ringing
180 Ringing ←
200 OK INVITE ← Off hook
ACK →
 
INVITE2 →
180 Ringing ← Start Tno answer Call waiting indication
Expiry Tno answer
486 Busy Here2 ←
ACK →
Apply post test routine
| | | | | Test equipment | | End device | INVITE1 | → | | Ringing | 180 Ringing | ← | | | 200 OK INVITE | ← | | Off hook | ACK | → | | | | | | | INVITE2 | → | | | 180 Ringing | ← | Start T no answer | Call waiting indication | | | Expiry T no answer | | 486 Busy Here2 | ← | | | ACK | → | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ← | | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | Start T no answer | Call waiting indication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Expiry T no answer | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 486 Busy Here2 | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------|-------------------------------------------------|--|-----------------------|--|-------------------|--------|---|--|---------|-------------|---|--|--|---------------|---|--|----------|-----|---|--|--|--|--|--|--|--------|---|--|--|-------------|---|--|-------------------------| +| TSS
CW | TP_507_103 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
The terminating user receives indication ‘‘a call is waiting’’. Terminal based communication waiting (CW) is supported | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that when a terminating user in a confirmed session receives an INVITE request to another dialogue, the SUT sends a 180 Ringing. The user is informed that a call is waiting. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180
Alert-Info: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ Ringing
180 Ringing ⬅
200 OK INVITE ⬅ Off hook
ACK ➔
 
INVITE ➔
180 Ringing ⬅ Call waiting indication

Apply post test routine

| | | | | Test equipment | | End device | INVITE | ➔ | | Ringing | 180 Ringing | ⬅ | | | 200 OK INVITE | ⬅ | | Off hook | ACK | ➔ | | | | | | | INVITE | ➔ | | | 180 Ringing | ⬅ | | Call waiting indication | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | Call waiting indication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|--------------------------------------------------------------| +| TSS
CW | TP_507_104 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14
AND 5.3/9 | +| Test purpose
The terminating user confirms the waiting call | | | | +| Ensure that when a terminating user in a confirmed session receives an INVITE request to another dialogue, the SUT sends a 180 Ringing. The SUT evaluates the switch order command based on a provisioned mapping table. The SOC indicates that the served user wishes the be connected to the waiting party, the AGCF performs the following actions: | | | | +|
  • • Send a 200 OK response to the INVITE request received from the waiting party
  • • Request the media gateway to:
    • – Modify the Remote Descriptor of the ephemeral termination according to the SDP information received from the waiting party.
| | | | +| The AGCF also sends a re-INVITE request on the initial dialogue to hold the associated media stream. | | | | +| SIP header values
INVITE3 (initial party)
SDP
a=sendonly

200 OK 3
SDP
a=recvonly | | | | + +![](b94fceb26b1b04b1c28ea44e12221aaa_img.jpg) + +| Message flow | | | +|-------------------------|----------------|------------------------------| +| | Test equipment | End device | +| INVITE1 | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE1 | ← | Off hook | +| ACK | → | | +| | | | +| INVITE2 | → | | +| 180 Ringing2 | ← | Call waiting indication | +| | | Flash hook | +| | | Dial tone | +| | | Dial switching order command | +| INVITE3 | ← | | +| 200 OKINVITE3 | → | | +| ACK | ← | | +| | | | +| 200 OK INVITE2 | ← | | +| ACK | → | | +| Apply post test routine | | | + +| | | | | +|-----------|------------|-------------------------------------------------|--------------------------------------------------------------| +| TSS
CW | TP_507_105 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14
AND 5.3/9 | +|-----------|------------|-------------------------------------------------|--------------------------------------------------------------| + +###### Test purpose + +*The terminating user rejects the waiting call* + +Ensure that when a terminating user in a confirmed session receives an INVITE request to another dialogue, the SUT sends a 180 Ringing. The SUT evaluates the switch order command based on a provisioned mapping Table. + +SOC indicates that the served user wishes to reject the waiting call, the AGCF performs the following actions: + +- Send a provisioned error response code (e.g. 603) to the INVITE request received from the waiting party. +- Request the media gateway to: + - Set the stream mode to send-receive. + - Monitor the flash-hook event. +- Send a re-INVITE request towards the held party (i.e., the party that has been held for the purpose of collecting the switching order command). The re-INVITE request is built as follows: + - The Request-URI is set to the held party's identity. + - The SDP description for the active media stream is set to a=sendrecv. + +###### **SIP header values** + +INVITE3 (initial party) +SDP +a=sendonly200 OK 3 +SDP +a=recvonlyINVITE4 (initial party) +SDP +a=sendrecv200 OK 4 +SDP +a=sendrecv + +###### **Message flow** + +| Test equipment | | End device | +|-----------------------|---|------------------------------| +| INVITE | ➔ | Ringing | +| 180 Ringing | ⬅ | | +| 200 OK INVITE | ⬅ | Off hook | +| ACK | ➔ | | +| | | | +| INVITE | ➔ | | +| 180 Ringing | ⬅ | Call waiting indication | +| | | Flash hook | +| | | Dial tone | +| | | Dial switching order command | +| | | | +| INVITE3 | ⬅ | | +| 200 OKINVITE3 | ➔ | | +| ACK | ⬅ | | +| | | | +| 603 Decline | ⬅ | | +| ACK | ➔ | | +| | | | +| INVITE4 | ⬅ | | +| 200 OKINVITE4 | ➔ | | +| ACK | ⬅ | | + +**Apply post test routine** + +| TSS
CW | TP_507_106 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14
AND 5.3/9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|--------------------------------------------------------------|----------------|--|------------|--|--|-------------------------------------------------------------|--|--|------------|--|--|-----------|--|--|------------------------------|-------------------------|---|--|----------------|---|--|-----|---|--|--|--|--|-------------------------|---|--|----------------|---|--|-----|---|--|--|--|--------------------------------| +| Test purpose
The terminating user decide to switch back to the initial party

Ensure that when the initial party is on hold and a confirmed session with the waiting party exists, a flash hook event applies followed by a switching order command. If the value of the switching order command indicates that the initial party is to be switched back, the AGCF performs the following actions:
  • • Send a re-INVITE request towards the held party. The re-INVITE request is built as follows:
    • – The Request-URI is set to the held party's identity.
    • – The SDP description for the active media stream is set to a=sendrecv.
  • • Send a re-INVITE request towards the active party. The re-INVITE request is built as follows:
    • – The Request URI is set to the active party's identity.
    • – The SDP description for the active media stream is set to a=sendonly.
  • • Request the media gateway to:
    • – Modify the Remote Descriptor of the ephemeral termination according to the SDP information associated with the held party.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE1 (initial party)
SDP
a=sendrecv

200 OK 3
SDP
a=sendrecv

INVITE4 (waiting party)
SDP
a=sendonly

200 OK 4
SDP
a=recvonly | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Terminating user is connected with the waiting party
Flash hook
Dial tone
Dial switching order command
INVITE1 (initial party) ←
200 OK INVITE1 →
ACK ←
 
INVITE2 (waiting party) ←
200 OK INVITE2 →
ACK ←
Apply post test routine
| | | | Test equipment | | End device | | | Terminating user is connected with the waiting party | | | Flash hook | | | Dial tone | | | Dial switching order command | INVITE1 (initial party) | ← | | 200 OK INVITE1 | → | | ACK | ← | | | | | INVITE2 (waiting party) | ← | | 200 OK INVITE2 | → | | ACK | ← | | | | Apply post test routine | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Terminating user is connected with the waiting party | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (waiting party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
CW | TP_507_107 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14
AND 5.3/10 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|---------------------------------------------------------------|----------------|--|------------|---------|---|---------|-------------|---|--|----------------|---|----------|-----|---|--|--|--|--|---------|---|--|--------------|---|-------------------------|--|--|------------|--|--|-----------|--|--|------------------------------|---------|---|--|----------------|---|--|-----|---|--|--|--|--|----------------|---|--|-----|---|--| +| Test purpose
The terminating user confirms the waiting call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Ensure that when a terminating user in a confirmed session receives an INVITE request to another dialogue, the SUT sends a 180 Ringing. The SUT evaluates the switch order command (SOC) based on a provisioned mapping table. The SOC indicates that the served user wishes to be connected to the waiting party, the AGCF performs the following actions:

  • Send a 200 OK response to the INVITE request received from the waiting party
  • Request the media gateway to:
    • Modify the Remote Descriptor of the ephemeral termination according to the SDP information received from the waiting party.

The AGCF also sends a re-INVITE request on the initial dialogue to hold the associated media stream.

  • The Request URI is structured as follows:
    • A user part containing a provisioned prefix followed by the switching order command without the start and finish fields.
    • A domain name that provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g. SOC- "SO (SR SI)"@pes.operator.com
    • A P-Asserted-Identity containing the public identity of the subscriber issuing the switching control command.
    • An SDP offer for a voice call.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE3
Request-Line: SO (SR SI)@pes.operator.com
SDP
a=sendonly

200 OK 3
SDP
a=recvonly | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 ➔ Ringing
180 Ringing ⬅
200 OK INVITE1 ⬅ Off hook
ACK ➔
 
INVITE2 ➔
180 Ringing2 ⬅ Call waiting indication
Flash hook
Dial tone
Dial switching order command
INVITE3 ⬅
200 OK INVITE3 ➔
ACK ⬅
 
200 OK INVITE2 ⬅
ACK ➔

Apply post test routine

| | | | Test equipment | | End device | INVITE1 | ➔ | Ringing | 180 Ringing | ⬅ | | 200 OK INVITE1 | ⬅ | Off hook | ACK | ➔ | | | | | INVITE2 | ➔ | | 180 Ringing2 | ⬅ | Call waiting indication | | | Flash hook | | | Dial tone | | | Dial switching order command | INVITE3 | ⬅ | | 200 OK INVITE3 | ➔ | | ACK | ⬅ | | | | | 200 OK INVITE2 | ⬅ | | ACK | ➔ | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | ➔ | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | ⬅ | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing2 | ⬅ | Call waiting indication | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE3 | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE3 | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|---------------------------------------------------------------| +| TSS
CW | TP_507_108 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14
AND 5.3/10 | +|

Test purpose
The terminating user rejects the waiting call

Ensure that when a terminating user in a confirmed session receives an INVITE request to another dialogue, the SUT sends a 180 Ringing. The SUT evaluates the switch order command based on a provisioned mapping table. SOC indicates that the served user wishes to reject the waiting call, the AGCF performs the following actions:

  • • Send a provisioned error response code (e.g. 603) to the INVITE request received from the waiting party.
  • • Request the media gateway to:
    • – Set the stream mode to send-receive.
    • – Monitor the flash-hook event.
  • • Send a re-INVITE request towards the held party (i.e. the party that has been held for the purpose of collecting the switching order command). The re-INVITE request is built as follows:
    • – The Request-URI is set to the held party's identity.
    • – The SDP description for the active media stream is set to a=sendrecv. An SDP offer for a voice call.

The AGCF also sends a re-INVITE request on the initial dialogue to hold the associated media stream.

  • – A user part containing a provisioned prefix followed by the switching order command without the start and finish fields.
  • – A domain name that provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g. SOC- "SO (SR SI)"@pes.operator.com
  • – A P-Asserted-Identity containing the public identity of the subscriber issuing the switching control command.

SIP header values
INVITE3 (initial party)
Request-Line: SO (SR SI)@pes.operator.com
SDP
a=sendonly

200 OK 3
SDP
a=recvonly

INVITE4 (initial party)
SDP
a=sendrecv

200 OK 4
SDP
a=sendrecv

| | | | + +| Message flow | | | +|--------------------------------|-----------------------|------------------------------| +| | Test equipment | End device | +| INVITE | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| | | | +| INVITE | → | | +| 180 Ringing | ← | Call waiting indication | +| | | Flash hook | +| | | Dial tone | +| | | Dial switching order command | +| INVITE3 | ← | | +| 200 OKINVITE3 | → | | +| ACK | ← | | +| | | | +| 603 Decline | ← | | +| ACK | → | | +| | | | +| INVITE4 | ← | | +| 200 OKINVITE4 | → | | +| ACK | ← | | +| Apply post test routine | | | + +| | | | | +|-----------|------------|-------------------------------------------------|---------------------------------------------------------------| +| TSS
CW | TP_507_109 | Reference
clause C.9 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/14
AND 5.3/10 | +|-----------|------------|-------------------------------------------------|---------------------------------------------------------------| + +###### Test purpose + +*The terminating user decide to switch back to the initial party* + +Ensure that when the initial party is on hold and a confirmed session with the waiting party exists a flash hook event applies followed by a switching order command. If the value of the switching order command indicates that the initial party is to be switched back, the AGCF performs the following actions: + +- Send a re-INVITE request towards the held party. The re-INVITE request is built as follows: + - The Request-URI is set to the held party's identity. + - The SDP description for the active media stream is set to a=sendrecv. +- Send a re-INVITE request towards the active party. The re-INVITE request is built as follows: + - The Request URI is set to the active party's identity. + - The SDP description for the active media stream is set to a=sendonly. +- Request the media gateway to: + - Modify the Remote Descriptor of the ephemeral termination according to the SDP information associated with the held party. + +The AGCF also sends a re-INVITE request on the initial dialogue to hold the associated media stream. + +- A user part containing a provisioned prefix followed by the switching order command without the start and finish fields. +- A domain name that provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g. SOC- "SO (SR SI)"@pes.operator.com + +A P-Asserted-Identity containing the public identity of the subscriber issuing the switching control command. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-----------------------|-------------------|-------------------------------------------------------------|--|--|------------|--|-----------|--|------------------------------|-------------------------|---|----------------|---|-----|---|-------------------------|---|----------------|---|-----|---|--------------------------------|--| +| SIP header values
INVITE1 (initial party)
Request-Line: SO (SR SI)@pes.operator.com
SDP
a=sendrecv

200 OK 3
SDP
a=sendrecv

INVITE4 (waiting party)
SDP
a=sendonly

200 OK 4
SDP
a=recvonly | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
Terminating user is connected with the waiting party
Flash hook
Dial tone
Dial switching order command
INVITE1 (initial party) ←
200 OK INVITE1 →
ACK ←
INVITE2 (waiting party) ←
200 OK INVITE2 →
ACK ←
Apply post test routine
| | Test equipment | End device | Terminating user is connected with the waiting party | | | Flash hook | | Dial tone | | Dial switching order command | INVITE1 (initial party) | ← | 200 OK INVITE1 | → | ACK | ← | INVITE2 (waiting party) | ← | 200 OK INVITE2 | → | ACK | ← | Apply post test routine | | +| Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | +| Terminating user is connected with the waiting party | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Flash hook | | | | | | | | | | | | | | | | | | | | | | | | | +| | Dial tone | | | | | | | | | | | | | | | | | | | | | | | | | +| | Dial switching order command | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 (initial party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE1 | → | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 (waiting party) | ← | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE2 | → | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | + +##### 7.2.5.7.2 Test purposes for ISDN + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|-------------------------------------------------| +| TSS
CW | TP_507_201 | Reference
subclause 5.2.11.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10 | +| Test purpose
Call waiting indication received in a 183 Session Progress | | | | +| Ensure that on receipt of a 183 Session Progress containing an Alert-Info header set to the urn '' and no provisional response was received before, a PROGRESS message is sent and a Notification indicator Information Element is present set to 'Call is a waiting call'. | | | | +| SIP header values
183
Alert-Info: | | | | +| DSS1 Parameter values
PROGRESS
Notification indicator
Call is a waiting call | | | | + +| Message flow | | | +|--------------------------------|-------------------|-----------------------------------| +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| PROGRESS | ← | 183 (Session Progress) | +| Apply post test routine | | | + +| | | | | +|-----------|------------|---------------------------------------------------------|-------------------------------------------------| +| TSS
CW | TP_507_202 | Reference
subclause 5.2.11.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10 | +|-----------|------------|---------------------------------------------------------|-------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Call waiting indication received in a 180 Ringing

Ensure that on receipt of a 180 Ringing containing an Alert-Info header set to the urn '', an ALERTING message is sent and a Notification indicator Information Element is present set to 'Call is a waiting call'. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|---------------------------------------------------------------------------------| +| SIP header values
180
Alert-Info: | +|---------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------| +| DSSI Parameter values
ALERTING
Notification indicator
Call is a waiting call | +|----------------------------------------------------------------------------------------------| + +| Message flow | | | +|--------------------------------|-------------------|-----------------------------------| +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| ALERTING | ← | 180 (Ringing) | +| Apply post test routine | | | + +| | | | | +|-----------|------------|---------------------------------------------------------|-------------------------------------------------| +| TSS
CW | TP_507_203 | Reference
subclause 5.2.11.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10 | +|-----------|------------|---------------------------------------------------------|-------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test purpose
Call waiting indication received in a 180 Ringing a 183 session Progress was received before

Ensure that on receipt of a 180 Ringing containing an Alert-Info header set to the urn '' and a provisional response was received before, an ALERTING message is sent and a Notification indicator Information Element is present set to 'Call is a waiting call'. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|---------------------------------------------------------------------------------| +| SIP header values
180
Alert-Info: | +|---------------------------------------------------------------------------------| + +| | | | +|----------------------------------------------------------------------------------------------|-------------------|-----------------------------------| +| DSSI Parameter values
ALERTING
Notification indicator
Call is a waiting call | | | +| Message flow | | | +| | End device | Test equipment | +| SETUP | → | INVITE | +| | ← | 407 Proxy Authentication Required | +| | → | ACK | +| | → | INVITE | +| PROGRESS | ← | 183 (Session Progress) | +| ALERTING | ← | 180 (Ringing) | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------|----------------------------------------------------------------| +| TSS
CW | TP_507_204 | Reference
subclause 5.2.11.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10
AND 5.1.3/2 | +| Test purpose
CW indication received in the INVITE busy condition met a CW notification is sent | | | | +| Ensure that on receipt of a CW indication in an INVITE request due to the 'ims-cw' XML element where the busy condition is met (two communication are already established), a SETUP is sent. The Channel identification is set to 'no channel'. | | | | +| Ensure that on receipt of the ALERTING message a 180 Ringing is sent containing an Alert-Info header set to 'urn:alert:service:call-waiting'. | | | | +| SIP header values
INVITE





180
Alert-Info: | | | | +| DSSI Parameter values
SETUP
Channel identification
no channel | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------------|----------------------------------------------------------------|--|-----------------------|--|-------------------|--------|---|---|-------|-------------|---|---|----------|--|--------------------------------|--|--| +| TSS
CW | TP_507_205 | Reference
subclause 5.2.11.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10
AND 5.1.3/2 | | | | | | | | | | | | | | | | | +| Test purpose
CW indication received in the INVITE busy condition not met a CW notification is not sent | | | | | | | | | | | | | | | | | | | | +|

Ensure that on receipt of a CW indication in an INVITE request due to the 'ims-cw' XML element where the busy condition is not met, a SETUP is sent. The Channel identification is not set to 'no channel'.

Ensure that on receipt of the ALERTING message a 180 Ringing is sent containing and the Alert-Info header set to 'urn:alert:service:call-waiting' is not present.

| | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
 <?xml version="1.0"?> <ims-cw xmlns="urn:3gpp:ns:cw:1.0">     <communication-waiting-indication/> </ims-cw>
| | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
Apply post test routine
| | | | | Test equipment | | End device | INVITE | ➔ | ➔ | SETUP | 180 Ringing | ⬅ | ⬅ | ALERTING | | Apply post test routine | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | +| INVITE | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------------------------------------------------| +| TSS
CW | TP_507_206 | Reference
subclause 5.2.11.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10
AND 5.1.3/2 | +| Test purpose
CW indication received in the INVITE busy condition met a CW notification is sent Call Waiting condition terminated after expiry of TUE-CW | | | | +|

Ensure that on receipt of a CW indication in an INVITE request due to the 'ims-cw' XML element and an Expires header where the busy condition is met (two communication are already established), a SETUP is sent. The Channel identification is set to 'no channel'.

The TUE-CW timer is started.

Ensure that on receipt of the ALERTING message a 180 Ringing is sent containing an Alert-Info header set to 'urn:alert:service:call-waiting'.

Ensure that on expiry of TUE-CW a 480 Temporarily Unavailable is sent containing a Reason header set to 'Q.850' and 'cause=19'

| | | | +| SIP header values
INVITE
     Expires: <any value>     <?xml version="1.0"?>     <ims-cw xmlns="urn:3gpp:ns:cw:1.0">         <communication-waiting-indication/>     </ims-cw>

180
Alert-Info: <urn:alert:service:call-waiting>

480
Reason: Q.850; cause=19

| | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------------|---|-------------------|-------------------|--------|---|--|---|-------|-------------|---|--|---|----------|--|--------------------------|--|--|--|--|---------------------------|--|--|--|-------------------------------|---|--|---|------------------|-----|---|--|--|--|--------------------------------|--|--|--|--| +| DSS1 Parameter values
SETUP
Channel identification
no channel | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
Start TUE-CW
Expiry TUE-CW
480 (Temporarily Unavailable) ⬅ ➔ RELEASE COMPLETE
ACK ➔
Apply post test routine
| | Test equipment | | | End device | INVITE | ➔ | | ➔ | SETUP | 180 Ringing | ⬅ | | ⬅ | ALERTING | | Start T UE-CW | | | | | Expiry T UE-CW | | | | 480 (Temporarily Unavailable) | ⬅ | | ➔ | RELEASE COMPLETE | ACK | ➔ | | | | Apply post test routine | | | | | +| | Test equipment | | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Start T UE-CW | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Expiry T UE-CW | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 480 (Temporarily Unavailable) | ⬅ | | ➔ | RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------|----------------------------------------------------------------|-------------------|-----------------------|--|--|-------------------|--------|---|--|---|-------|-------------|---|--|---|----------|--------------------------------|--|--|--|--| +| TSS
CW | TP_507_207 | Reference
subclause 5.2.11.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10
AND 5.1.3/2 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CW indication not received in the INVITE busy condition met a CW notification is sent

Ensure that on receipt of an INVITE request where the CW indication is not present and the busy condition is met (two communication are already established), a SETUP is sent. The Channel identification is set to 'no channel'.
Ensure that on receipt of the ALERTING message a 180 Ringing is sent containing an Alert-Info header set to 'urn:alert:service:call-waiting'. | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
180
Alert-Info: | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP
Channel identification
no channel | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
Apply post test routine
| | | | | Test equipment | | | End device | INVITE | ➔ | | ➔ | SETUP | 180 Ringing | ⬅ | | ⬅ | ALERTING | Apply post test routine | | | | | +| | Test equipment | | | End device | | | | | | | | | | | | | | | | | | | | +| INVITE | ➔ | | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------------------------------------------------| +| TSS
CW | TP_507_208 | Reference
subclause 5.2.11.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/10
AND 5.1.3/2 | +| Test purpose
CW notification received from the private network

Ensure that on receipt of an ALERTING message or a PROGRESS message or a NOTIFY message containing a Notification indicator Information Element, the Notification description is set to 'Call is a waiting call' a 180 Ringing is sent containing an Alert-Info header set to 'urn:alert:service:call-waiting'. | | | | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| SIP header values
180
Alert-Info:

183
Alert-Info: | | | +| DSSI Parameter values
ALERTING
Notification indicator
Notification description
Call is a waiting call

PROGRESS
Notification indicator
Notification description
Call is a waiting call

NOTIFY
Notification indicator
Notification description
Call is a waiting call | | | +| Message flow

INVITE
CASE A
180 Ringing

CASE B
183 (Session Progress)

CASE C
183 (Session Progress) | Test equipment

→

←

←

← | End device

→ SETUP

← ALERTING

← PROGRESS

← NOTIFY

Apply post test routine | + +#### 7.2.5.8 Terminal Portability (TP) + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
TP | TP_508_001 | Reference
subclause 5.2.12.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11 | +| Test purpose
Suspend initiated

Ensure that on receipt of a SUSPEND message in the confirmed state an INVITE request or UPDATE request is sent.
A 'a' line in the SDP is set to 'sendonly' or 'inactive' | | | | +| SIP header values
INVITE
SDP
a= sendonly
or
a=inactive | | | | + +| DSSI Parameter values | | +|--------------------------------|-----------------------------------------------------------------------| +| SUSPEND | | +| Call identity | | +| End device | Test equipment | +| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE1 | +| ALERTING | ← 180 Ringing | +| CONNECT | ← 200 OK INVITE
→ ACK | +| SUSPEND | → | +| SUSPEND ACKNOWLEDGE | ← | +| CASE A | → INVITE
← 200 OK INVITE
→ ACK | +| CASE B | → UPDATE
← 200 OK UPDATE | +| Apply post test routine | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|----------------------------------------------------------------| +| TSS
TP | TP_508_002 | Reference
subclause 5.2.12.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/2 | +| Test purpose
Resumed initiated | | | | +| Ensure that on receipt of a RESUME message in the confirmed state and the ISDN connection is in the suspended state an INVITE request or UPDATE request is sent. A 'a' line in the SDP is set to 'sendrecv' | | | | +| SIP header values
INVITE1/UPDATE 1
SDP
a=sendonly

INVITE2/UPDATE 2
SDP
a=sendrecv | | | | +| DSSI Parameter values
SUSPEND
Call identity

RESUME
Call identity | | | | + +| End device | | Test equipment | | +|--------------------------------|---|----------------|-----------------------------------| +| SETUP | → | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| ALERTING | ← | ← | 180 Ringing | +| CONNECT | ← | ← | 200 OK INVITE | +| | | → | ACK | +| CASE A | | | | +| SUSPEND | → | → | INVITE1 | +| SUSPEND ACKNOWLEDGE | ← | ← | 200 OK INVITE | +| | | → | ACK | +| | | → | INVITE2 | +| RESUME | → | ← | 200 OK INVITE | +| SUSPEND ACKNOWLEDGE | ← | → | ACK | +| CASE B | | | | +| SUSPEND | → | → | UPDATE1 | +| SUSPEND ACKNOWLEDGE | ← | ← | 200 OK UPDATE | +| | | | | +| RESUME | → | → | UPDATE2 | +| SUSPEND ACKNOWLEDGE | ← | ← | 200 OK UPDATE | +| Apply post test routine | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|----------------------------------------------------------------| +| TSS
TP | TP_508_003 | Reference
subclause 5.2.12.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/2 | +| Test purpose
Suspend initiated T307 expiry | | | | +| Ensure that on receipt of a SUSPEND message timer T307 is started. After the expiry of timer T307 the SIP communication is terminated. A CANCEL or BYE is sent. A Reason header is present set to 'Q.850' and the cause parameter set to '102'. | | | | +| SIP header values
INVITE
SDP
a=sendonly
or
a=inactive

CANCEL/BYE
Reason: Q.850; cause=102 | | | | +| DSS1 Parameter values
SUSPEND
Call identity            Call identity | | | | + +![](06871b31aeaeae83d5624b8ca7bf0177_img.jpg) + +| End device | | Test equipment | | +|--------------------------------|---|----------------|-----------------------------------| +| SETUP | → | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| ALERTING | ← | ← | 180 Ringing | +| CONNECT | ← | ← | 200 OK INVITE | +| | | → | ACK | +| CASE A | | | | +| SUSPEND | → | Start T307 | → INVITE1 | +| SUSPEND ACKNOWLEDGE | ← | | ← 200 OK INVITE | +| | | | → ACK | +| | | T307 expiry | → CANCEL/BYE | +| | | | ← 200 OK CANCEL/BYE | +| | | | ← 487 Request Terminated | +| | | | → ACK | +| CASE B | | | | +| SUSPEND | → | Start T307 | → UPDATE1 | +| SUSPEND ACKNOWLEDGE | ← | | ← 200 OK UPDATE | +| | | T307 expiry | → CANCEL/BYE | +| | | | ← 200 OK CANCEL/BYE | +| | | | ← 487 Request Terminated | +| | | | → ACK | +| Apply post test routine | | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|----------------------------------------------------------------| +| TSS
TP | TP_508_004 | Reference
subclause 5.2.12.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/1 | +| Test purpose
Suspend initiated by the private network | | | | +| Ensure that on receipt of a NOTIFY message the Notification indicator Information Element is set to 'User suspended' in the confirmed state and an INVITE request or UPDATE request is sent. A 'a' line in the SDP is set to 'sendonly' or 'inactive' | | | | +| SIP header values
INVITE
SDP
a= sendonly | | | | +| DSSI Parameter values
NOTIFY
Notification indicator
Notification description
User suspended | | | | + +| | End device | Test equipment | +|--------------------------------|------------|----------------------------------------------------------------------| +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| NOTIFY | → | | +| CASE A | | → INVITE1
← 200 OK INVITE
→ ACK | +| CASE B | | → UPDATE1
← 200 OK UPDATE | +| Apply post test routine | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|----------------------------------------------------------------| +| TSS
TP | TP_508_005 | Reference
subclause 5.2.12.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/1 | +| Test purpose
Resumed initiated from the private network | | | | +| Ensure that on receipt of a NOTIFY message, the Notification indicator Information Element is set to 'User resumed' in the confirmed state, the ISDN connection is in the suspended state and an INVITE request or UPDATE request is sent. A 'a' line in the SDP is set to 'sendrecv' | | | | +| SIP header values
INVITE1/UPDATE 1
SDP
a=sendonly

INVITE2/UPDATE 2
SDP
a=sendrecv | | | | +| DSS1 Parameter values
NOTIFY 1
Notification indicator
Notification description
User suspended

NOTIFY 2
Notification indicator
Notification description
User resumed | | | | + +| | End device | Test equipment | +|--------------------------------|------------|----------------------------------------------------------------------| +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| ALERTING | ← | ← 180 Ringing | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| CASE A | | | +| NOTIFY 1 | → | → INVITE1
← 200 OK INVITE
→ ACK | +| NOTIFY 2 | → | → INVITE2
← 200 OK INVITE
→ ACK | +| CASE B | | | +| NOTIFY 1 | → | → UPDATE1
← 200 OK UPDATE | +| NOTIFY 2 | → | → UPDATE2
← 200 OK UPDATE | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|----------------------------------------------------------------| +| TSS
TP | TP_508_006 | Reference
subclause 5.2.12.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/2 | +| Test purpose
Suspend initiated | | | | +| Ensure that on receipt of an INVITE or UPDATE message in the confirmed state the 'a' line in the SDP is set to 'sendonly' and a SUSPEND message is sent to the end device. | | | | +| SIP header values
INVITE2/UPDATE
SDP
a= sendonly | | | | +| DSS1 Parameter values
SUSPEND
Call identity | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-----------------------| +| | Test equipment | End device | +| INVITE1 | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK (INVITE) | ← | ← CONNECT | +| ACK | → | | +| CASE A | | | +| INVITE2 | → | → SUSPEND | +| 200 OK (INVITE) | ← | ← SUSPEND ACKNOWLEDGE | +| ACK | → | | +| CASE B | | | +| UPDATE | → | → SUSPEND | +| 200 OK UPDATE | ← | ← SUSPEND ACKNOWLEDGE | +| Apply post test routine | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------|----------------------------------------------------------------| +| TSS
TP | TP_508_007 | Reference
subclause 5.2.12.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/2 | +| Test purpose
Resumed initiated | | | | +| Ensure that on receipt of an INVITE or UPDATE message in the confirmed state the 'a' line in the SDP is set to 'sendrecv' and a SUSPEND message is sent to the end device. | | | | +| SIP header values
INVITE3/UPDATE2
SDP
a= sendonly | | | | +| DSSI Parameter values
RESUME
Call identity | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE1 | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| 200 OK (INVITE) | ← | ← | CONNECT | +| ACK | → | | | +| CASE A | | | | +| INVITE2 | → | → | SUSPEND | +| 200 OK (INVITE) | ← | ← | SUSPEND ACKNOWLEDGE | +| ACK | → | | | +| INVITE3 | → | → | RESUME | +| 200 OK (INVITE) | ← | ← | SUSPEND ACKNOWLEDGE | +| ACK | → | | | + +| | | | +|--------------------------------|---|-----------------------| +| CASE B | | | +| UPDATE1 | → | → SUSPEND | +| 200 OK UPDATE | ← | ← SUSPEND ACKNOWLEDGE | +| CASE B | | | +| UPDATE2 | → | → RESUME | +| 200 OK UPDATE | ← | ← SUSPEND ACKNOWLEDGE | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------|----------------------------------------------------------------| +| TSS
TP | TP_508_008 | Reference
subclause 5.2.12.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/1 | +| Test purpose
Suspend initiated from the private network | | | | +| Ensure that on receipt of an INVITE or UPDATE message in the confirmed state the 'a' line in the SDP is set to 'sendonly'. A NOTIFY message the Notification indicator Information Element is set to 'User suspended' is sent to the end device. | | | | +| SIP header values
INVITE2/UPDATE
SDP
a= sendonly | | | | +| DSS1 Parameter values
NOTIFY
Notification indicator
Notification description
User suspended | | | | +| Message flow | | | | +| | Test equipment | | End device | +| INVITE1 | → | → | SETUP | +| 180 Ringing | ← | ← | ALERTING | +| 200 OK (INVITE) | ← | ← | CONNECT | +| ACK | → | | | +| CASE A | | | | +| INVITE2 | → | → | NOTIFY | +| 200 OK (INVITE) | ← | | | +| ACK | → | | | +| CASE B | | | | +| UPDATE | → | → | NOTIFY | +| 200 OK UPDATE | ← | | | +| Apply post test routine | | | | + +| TSS
TP | TP_508_009 | Reference
5.2.12.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/11
AND 5.1.3/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------|----------------------------------------------------------------|---------|-----------------------|---|-------------------|-----------------|---|---|-------|-------------|---|---|----------|-----------------|---|---|---------|---------------|---|---|---------|-----------------|---|--|--|-----|---|--|--| +| Test purpose
Resumed initiated from the private network

Ensure that on receipt of an INVITE or UPDATE message in the confirmed state, the 'a' line in the SDP is set to 'sendrecv'. A NOTIFY message the Notification indicator Information Element is set to 'User resumed' is sent to the end device. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE2/UPDATE
SDP
a= sendrecv | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
NOTIFY 2
Notification indicator
Notification description
User resumed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
200 OK (INVITE) ⬅ ⬅ CONNECT
ACK ➔
| | | | | Test equipment | | End device | INVITE1 | ➔ | ➔ | SETUP | 180 Ringing | ⬅ | ⬅ | ALERTING | 200 OK (INVITE) | ⬅ | ⬅ | CONNECT | ACK | ➔ | | | | | | | | | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ | ⬅ | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A
INVITE2 ➔ ➔ NOTIFY1
200 OK (INVITE) ⬅
ACK ➔
 
INVITE2 ➔ ➔ NOTIFY2
200 OK (INVITE) ⬅
ACK ➔
| | | | INVITE2 | ➔ | ➔ | NOTIFY1 | 200 OK (INVITE) | ⬅ | | | ACK | ➔ | | | | | | | INVITE2 | ➔ | ➔ | NOTIFY2 | 200 OK (INVITE) | ⬅ | | | ACK | ➔ | | | +| INVITE2 | ➔ | ➔ | NOTIFY1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 | ➔ | ➔ | NOTIFY2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE B
UPDATE ➔ ➔ NOTIFY1
200 OK UPDATE ⬅
 
UPDATE ➔ ➔ NOTIFY2
200 OK UPDATE ⬅
| | | | UPDATE | ➔ | ➔ | NOTIFY1 | 200 OK UPDATE | ⬅ | | | | | | | UPDATE | ➔ | ➔ | NOTIFY2 | 200 OK UPDATE | ⬅ | | | | | | | | | | | +| UPDATE | ➔ | ➔ | NOTIFY1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK UPDATE | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UPDATE | ➔ | ➔ | NOTIFY2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK UPDATE | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.5.9 Explicit Communication Transfer (ECT) + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| TSS
ECT | TP_509_001 | Reference
subclause 5.2.7.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12 | +| Test purpose
Activation of ECT using the EctExecute invoke component in active state | | | | +|

A call to a user in active state is on hold and a call to an additional user is in active state.
Ensure that on receipt of a FACILITY message containing a 'EctExecute' invoke component regarding the Call Reference to the user in held state a REFER is sent.

  • • The request line is set to the address of the held user.
  • • The Refer-To header is set to the address of the active user, the method parameter is set to 'invite', the Replaces header is set to the session identification values of the active connection.
  • • The Referred-By header is set to the Public user identity of the served user

After an NOTIFY containing the message/sipfrag 'SIP/2.0 200 OK' a DISCONNECT is sent for all connection to the ISDN equipment, the DISCONNECT regarding the Call Reference of the received FACILIT message contains the EctExecute return result component.

| | | | +| SIP header values
REFER: [Connection CR 1]
Refer-To: ; method=invite?Replaces=[Call CR 2]
Referred-By: | | | | +| NOTIFY 1:
Content-Type: message/sipfrag
SIP/2.0 100 Trying | | | | +| NOTIFY 2:
Content-Type: message/sipfrag
SIP/2.0 200 OK | | | | +| DSS1 Parameter values
FACILITY:
CR 1
EctExecute invoke | | | | +| DISCONNECT 1
EctExecute return result | | | | +| End device | | Test equipment | | +| A call is established in held state CR 1
A call is established in active state CR2 | | | | +| FACILITY | → | → INVITE (CR2, sendonly)
← 200 OK INVITE
→ ACK

→ REFER
← 202 Accepted

← NOTIFY 1
→ 200 OK NOTIFY

← NOTIFY 2 | | + +![](b57a7a090805d3dfef36a0130a473432_img.jpg) + +``` + + ➔ 200 OK NOTIFY + + + ← BYE (CR 2) + ➔ 200 OK BYE + + ➔ BYE (CR 1) +DISCONNECT 1 ← ← 200 OK BYE +RELEASE ➔ +RELEASE COMPLETE ← + +DISCONNECT 2 ← +RELEASE ➔ +RELEASE COMPLETE ← ← 200 OK UPDATE + Apply post test routine + +``` + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|-------------------------------------------------| +| TSS
ECT | TP_509_002 | Reference
subclause 5.2.7.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12 | +|

Test purpose
Activation of ECT using the EctExecute invoke component in alerting state

A call to a user in active state is on hold and a call to a additional user is in alerting state.
Ensure that on receipt of a FACILITY message containing a 'EctExecute' invoke component regarding the Call Reference to the user in held state a REFER is sent.

  • • The request line is set to the address of the held user.
  • • The Refer-To header is set to the address of the active user, the method parameter is set to 'invite', the Replaces header is set to the session identification values of the active connection.
  • • The Referred-By header is set to the Public user identity of the served user

After a NOTIFY containing the message/sipfrag 'SIP/2.0 200 OK' a DISCONNECT is sent for all connection to the ISDN equipment, the DISCONNECT regarding the Call Reference of the received FACILIT message contains the EctExecute return result component.

SIP header values
REFER: [Connection CR 1]
    Refer-To: <sip:[Connection CR 2]>; method=invite?Replaces=[Call CR 2]
    Referred-By: <sip:[Public user identity]>

NOTIFY 1:
    Content-Type: message/sipfrag
    SIP/2.0 100 Trying

NOTIFY 2:
    Content-Type: message/sipfrag
    SIP/2.0 200 OK

| | | | + +| DSS1 Parameter values
FACILITY:
CR 1
EctExecute invoke

DISCONNECT 1
EctExecute return result | | +|------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| End device | Test equipment | +| A call is established in held state CR 1 | | +| A call is alerting state CR2 | | +| FACILITY | →
→ INVITE (CR2, sendonly)
← 200 OK INVITE
→ ACK

→ REFER
← 202 Accepted

← NOTIFY 1
→ 200 OK NOTIFY

← NOTIFY 2
→ 200 OK NOTIFY

← BYE (CR 2)
→ 200 OK BYE

→ BYE (CR 1)
← 200 OK BYE | +| DISCONNECT 1 | ← | +| RELEASE | → | +| RELEASE COMPLETE | ← | +|
DISCONNECT 2 |
← | +| RELEASE | → | +| RELEASE COMPLETE | ←      ← 200 OK UPDATE | +| Apply post test routine | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------------------------------------------------| +| TSS
ECT | TP_509_003 | Reference
subclause 5.2.7.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12
AND 5.1.3/1 | +| Test purpose
Activation of ECT performed in a private network using the EctInform invoke component set to alerting, no mapping

One or two sessions are established. Ensure that on receipt of a DSS1 FACILITY message for a Call Reference containing a EctInform invoke component set to Alerting, no SIP message is sent and no SIP action occurs. | | | | +| SIP header values | | | | + +| | | +|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| DSSI Parameter values
FACILITY:
EctInform invoke
Alerting | | +| End device | Test equipment | +| | A call is established CR 1
A call is established CR2
→ | +| FACILITY | | +| Apply post test routine | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------|----------------------------------------------------------------| +| TSS
ECT | TP_509_004 | Reference
subclause 5.2.7.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12
AND 5.1.3/1 | +| Test purpose
Activation of ECT performed in a private network using the EctInform invoke component set to active, no mapping | | | | +| One or two sessions are established. Ensure that on receipt of a DSSI FACILITY message for a Call Reference containing a EctInform invoke component set to Active, no SIP message is sent and no SIP action occurs. | | | | +| SIP header values | | | | +| DSSI Parameter values
FACILITY:
EctInform invoke
Active
redirectionNumber | | | | +| End device | Test equipment | | | +| | A call is established CR 1
A call is established CR2
→ | | | +| FACILITY | | | | +| Apply post test routine | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------------------------------------------------| +| TSS
ECT | TP_509_005 | Reference
subclause 5.2.7.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12
AND 5.1.3/1 | +| Test purpose
Request of Subaddress using the SubaddressTransfer invoke component set to active, no mapping | | | | +| One or two sessions are established. Ensure that on receipt of a DSSI FACILITY message for a Call Reference containing a RequestSubaddress invoke component, no SIP message is sent and no SIP action occurs. | | | | +| SIP header values | | | | +| DSSI Parameter values
FACILITY:
RequestSubaddress invoke | | | | + +![](d186ab1411a29b6f0938ab43178e9f0d_img.jpg) + +| | | +|-------------------|---------------------------------------------------------| +| End device | Test equipment | +| | A call is established CR 1
A call is established CR2 | +| FACILITY | ➔ | +| | Apply post test routine | + +| | | | | +|-----|------------|--------------------------------------------------------|-------------------------------------------------| +| TSS | TP_509_006 | Reference
subclause 5.2.7.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12 | +|-----|------------|--------------------------------------------------------|-------------------------------------------------| + +**Test purpose** +*Receipt of an INVITE request to a call in held state* + +A communication is in the held state. +Ensure that on receipt of an INVITE request, the line in the SDP is set to 'sendrecv', a DSS1 NOTIFY message is sent to the user equipment indicating the user is resumed. + +**SIP header values** +INVITE: +SDP +a=sendrecv + +**DSS1 Parameter values** +NOTIFY: Notification description +User resumed + +![](eda842e37041ac9b9b80099251e40bb8_img.jpg) + +| | | +|-----------------------|-------------------------------------| +| Message flow | | +| Test equipment | End device | +| | A call is established in held state | +| INVITE | ➔ NOTIFY | +| 200 OK INVITE | ⬅ | +| ACK | ➔ | +| | Apply post test routine | + +| | | | | +|------------|------------|--------------------------------------------------------|-------------------------------------------------| +| TSS
ECT | TP_509_007 | Reference
subclause 5.2.7.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12 | +|------------|------------|--------------------------------------------------------|-------------------------------------------------| + +**Test purpose** +*Receipt of an UPDATE request to a call in held state* + +A communication is in the held state. +Ensure that on receipt of an UPDATE request and the a line in the SDP is set 'sendrecv' a DSS1 NOTIFY message is sent to the user equipment indicating the user is resumed. + +**SIP header values** +UPDATE: +SDP +a=sendrecv + +**DSS1 Parameter values** +NOTIFY: Notification description +User resumed + +| | | | +|--------------------------------------------|-----------------------|-------------------| +| Message flow | | | +| | Test equipment | End device | +| A call is established in held state | | | +| UPDATE | ➔ | ➔ NOTIFY | +| 200 OK UPDATE | ⬅ | | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|-------------------------------------------------| +| TSS
ECT | TP_509_008 | Reference
subclause 5.2.7.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12 | +| Test purpose | | | | +| Receipt of an INVITE request to a call in active state | | | | +| A communication is in the active state.
Ensure that on receipt of an INVITE request the SDP is not different from the previously received SDP containing a: | | | | +|
  • • P-Asserted-Identity
  • • Privacy absent or not "id"
  • • isub parameter in the P-Asserted-Identity
| | | | +| No Message is sent to the DSS1 user equipment. | | | | +| SIP header values | | | | +| INVITE:
P-Asserted-Identity
Isub | | | | +| DSS1 Parameter values | | | | +| Message flow | | | | +| | Test equipment | End device | | +| A call is established in held state | | | | +| INVITE | ➔ | | | +| 200 OK INVITE | ⬅ | | | +| ACK | ➔ | | | +| Apply post test routine | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|-------------------------------------------------| +| TSS
ECT | TP_509_009 | Reference
subclause 5.2.7.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/12 | +| Test purpose | | | | +| Receipt of an UPDATE request to a call in active state | | | | +| A communication is in the active state.
Ensure that on receipt of an UPDATE request, the SDP is not different from the previously received SDP containing a: | | | | +|
  • • P-Asserted-Identity
  • • Privacy absent or not "id"
  • • isub parameter in the P-Asserted-Identity
| | | | +| No Message is sent to the DSS1 user equipment. | | | | + +| | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-------------------|-------------------|--|--------------------------------------------|--|--------|---|--|---------------|---|--|--|--------------------------------|--| +| SIP header values
UPDATE:
P-Asserted-Identity
Isub | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
A call is established in held state
UPDATE ➔
200 OK UPDATE ←
Apply post test routine
| Test equipment | | End device | | A call is established in held state | | UPDATE | ➔ | | 200 OK UPDATE | ← | | | Apply post test routine | | +| Test equipment | | End device | | | | | | | | | | | | | | +| | A call is established in held state | | | | | | | | | | | | | | | +| UPDATE | ➔ | | | | | | | | | | | | | | | +| 200 OK UPDATE | ← | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | + +#### 7.2.5.10 User User Service (UUS) + +| | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------------------------|-------------------------------------------------|-------------------|--|-----------------------|-------|---|----------|--|--|-------------------------------------|--|--|-------|--|--|-----------|--|--------------------------------|--| +| TSS
UUS | TP_510_001 | Reference
subclause 5.2.10.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | | | | | | | | | | | | | | | | | | | +| Test purpose
Call setup contains a DSS1 User-user service Information Element implicit request

Ensure that on receipt of a DSS1 SETUP an INVITE request is sent. The User information and the Protocol discriminator in the User-user Information Element is mapped into the uuidata parameter in the User-to-User header present in the sent INVITE request. | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
User-to-User
uuidata | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP
User-user
Protocol discriminator
User information | | | | | | | | | | | | | | | | | | | | | | +|
End device Test equipment
SETUP ➔ ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE1
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | ➔ INVITE | | | ← 407 Proxy Authentication Required | | | ➔ ACK | | | ➔ INVITE1 | | Apply post test routine | | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | +| | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | +| | | ➔ INVITE1 | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_002 | Reference
subclause 5.2.10.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +| Test purpose
Call setup contains a DSS1 User-user Information Element implicit request, response in 180 Ringing

Ensure that on receipt of a 180 Ringing an ALERTING is sent. The uuidata parameter in the User-to-User header is mapped into the User information and the Protocol discriminator in the User-user Information Element is present in the sent ALERTING. | | | | + +432 + +Rec. ITU-T Q.4014.2 (04/2019) + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| SIP header values
INVITE
User-to-User
Uuidata

180
User-to-User
uuidata | | +| DSSI Parameter values
SETUP
User-user
Protocol discriminator
User information

ALERTING
User-user
Protocol discriminator
User information | | +| End device

SETUP




ALERTING | Test equipment

→ INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE1
← 180 Ringing

Apply post test routine | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_003 | Reference
5.2.10.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +| Test purpose
Call setup contains a DSSI User-user Information Element implicit request, response in 183 Session Progress | | | | +| Ensure that on receipt of a 183 Session Progress a PROGRESS is sent. The uuidata parameter in the User-to-User header is mapped into the User information and the Protocol discriminator in the User-user Information Element is present in the sent PROGRESS. | | | | +| SIP header values
INVITE
User-to-User
Uuidata

180
User-to-User
uuidata | | | | + +| DSS1 Parameter values
SETUP
User-user
Protocol discriminator
User information

PROGRESS
User-user
Protocol discriminator
User information | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------------------------------| +| End device | | Test equipment | +| SETUP | → | → INVITE | +| | ← | ← 407 Proxy Authentication Required | +| | → | → ACK | +| | → | → INVITE1 | +| ALERTING | ← | ← 180 Ringing | +| PROGRESS | ← | ← 183 (Session Progress) | +| Apply post test routine | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_004 | Reference
subclause 5.2.10.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +| Test purpose
Call setup contains a DSS1 User-user Information Element implicit request, response in 200 OK | | | | +| Ensure that on receipt of a 200 OK INVITE a PROGRESS is sent. The uuidata parameter in the User-to-User header is mapped into the User information and the Protocol discriminator in the User-user Information Element is present in the sent CONNECT. | | | | +| SIP header values
INVITE
User-to-User
Uuidata

180
User-to-User
uuidata | | | | +| DSS1 Parameter values
SETUP
User-user
Protocol discriminator
User information

CONNECT
User-user
Protocol discriminator
User information | | | | + +| End device | | Test equipment | | +|--------------------------------|---|----------------|-----------------------------------| +| SETUP | → | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE1 | +| ALERTING | ← | ← | 180 Ringing | +| CONNECT | ← | ← | 200 OK INVITE | +| | | → | ACK | +| Apply post test routine | | | | + +| TSS
UUS | TP_510_005 | Reference
subclause 5.2.10.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| Test purpose | | | | +| Call setup contains a DSS1 User-user Information Element implicit request, response in BYE | | | | +| Ensure that on receipt of a BYE request a PROGRESS is sent. The uuidata parameter in the User-to-User header is mapped into the User information and the Protocol discriminator in the User-user Information Element the present in the sent DISCONNECT in backward direction. | | | | +| SIP header values | | | | +| INVITE
User-to-User
uuidata | | | | +| BYE
User-to-User
uuidata | | | | +| DSS1 Parameter values | | | | +| SETUP
User-user
Protocol discriminator
User information | | | | +| DISCONNECT
User-user
Protocol discriminator
User information | | | | +| End device | | Test equipment | | +| SETUP | → | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE1 | +| ALERTING | ← | ← | 180 Ringing | +| CONNECT | ← | ← | 200 OK INVITE | +| | | → | ACK | +| DISCONNECT | ← | ← | BYE | +| RELEASE | → | → | 200 OK BYE | +| RELEASE COMPLETE | ← | | | +| Apply post test routine | | | | + +| TSS
UUS | TP_510_006 | Reference
subclause 5.2.10.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------|--|------------|--|----------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|---------|-----------------|---|---|------------------------| +| Test purpose
Call setup with User-to-user request service 1 explicit request preferred rejected in CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a User-user Information Element and a Facility Information Element UserUserService request invoke Service 1 preferred an INVITE request is sent. Upon receipt of a 183 (Session Progress) provisional response a CALL PROCEEDING message is sent. To reject the requested User to User service a Facility Information element is present and is set to UserUserService return error rejectedByNetwork | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP
User-user
Protocol discriminator
User information
Facility
UserUserService request invoke
Service 1 preferred

CALL PROCEEDING
Facility
UserUserService return error
rejectedByNetwork | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
End device Test equipment
SETUP ➔ ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE1
CALL PROCEEDING ⬅ ⬅ 183 (Session Progress)
Apply post test routine
| | | | | End device | | Test equipment | SETUP | ➔ | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE1 | CALL PROCEEDING | ⬅ | ⬅ | 183 (Session Progress) | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔ | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | +| CALL PROCEEDING | ⬅ | ⬅ | 183 (Session Progress) | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_007 | Reference
5.2.10.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +| Test purpose
Call setup with User-to-user request service 1 explicit request preferred rejected in ALERTING | | | | +| Ensure that on receipt of a SETUP message containing a user-user Information Element and a Facility Information Element UserUserService request invoke Service 1 preferred an INVITE request is sent. Upon receipt of a 180 (Ringing) provisional response an ALERTING message is sent. To reject the requested User to User service a Facility Information element is present set to UserUserService return error rejectedByNetwork | | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| DSS1 Parameter values
SETUP
User-user
Protocol discriminator
User information
Facility
UserUserService request invoke
Service 1 preferred

ALERTING
Facility
UserUserService return error
rejectedByNetwork | | +|
End device ➠

SETUP





ALERTING ⬅
|
Test equipment

➠ INVITE
⬅ 407 Proxy Authentication Required
➠ ACK
➠ INVITE
⬅ 180 Ringing | +| Apply post test routine | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_008 | Reference
subclause 5.2.10.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +| Test purpose
Call setup with user-to-user request service 1 explicit request preferred rejected in CONNECT

Ensure that on receipt of a SETUP message containing a user-user Information Element and a Facility Information Element UserUserService request invoke Service 1 preferred an INVITE request is sent. Upon receipt of a 200 OK INVITE final response a CONNECT message is sent. To reject the requested User to User service a Facility Information element is present set to UserUserService return error rejectedByNetwork | | | | +| DSS1 Parameter values
SETUP
User-user
Protocol discriminator
User information
Facility
UserUserService request invoke
Service 1 preferred

CONNECT
Facility
UserUserService return error
rejectedByNetwork | | | | + +| | End device | | Test equipment | +|--------------------------------|------------|---|-----------------------------------| +| SETUP | → | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| ALERTING | ← | ← | 180 Ringing | +| CONNECT | ← | ← | 200 OK INVITE | +| | | → | ACK | +| Apply post test routine | | | | + +| TSS
UUS | TP_510_009 | Reference
5.2.10.1.2 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------|-------------------------------------------------| +| Test purpose | | | | +| Call setup with user-to-user request service 1 explicit request required rejected in DISCONNECT | | | | +| Ensure that on receipt of a SETUP message containing an User-user Information Element and a Facility Information Element UserUserService request invoke Service 1 required a DISCONNECT message is sent. To reject the requested User to User service a Facility Information element is present set to UserUserService return error rejectedByNetwork and the Cause Information Element set 69 (requested facility not implemented) | | | | +| DSSI Parameter values | | | | +| SETUP
User-user
Protocol discriminator
User information
Facility
UserUserService request invoke
Service 1 required

DISCONNECT
Facility
UserUserService return error
rejectedByNetwork
Cause
Value 69 (requested facility not implemented) | | | | +| | End device | | Test equipment | +| SETUP | → | | | +| DISCONNECT | ← | | | +| RELEASE | → | | | +| RELEASE COMPLETE | ← | | | + +| TSS
UUS | TP_510_010 | Reference
subclause 5.2.10.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/14 | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------|-------------------------------------------------|-------------------|--|-----------------------|-------|-------------------|----------------------------------------------------------------------|-----------------|---|--------------------------| +| Test purpose
Call setup with user-to-user request service 2 explicit request preferred rejected in CALL PROCEEDING | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a Facility Information Element UserUserService request invoke Service 2 preferred an INVITE request is sent. Upon receipt of a 183 (Session Progress) provisional response a CALL PROCEEDING message is sent. To reject the requested User to User service a Facility Information element is present set to UserUserService return error rejectedByNetwork | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | +| SETUP
Facility
UserUserService request invoke
Service 2 preferred | | | | | | | | | | | | | +| CALL PROCEEDING
Facility
UserUserService return error
rejectedByNetwork | | | | | | | | | | | | | +|
End device Test equipment
SETUP ➔



➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE
CALL PROCEEDING ← ← 183 (Session Progress)
| | | | End device | | Test equipment | SETUP | ➔



| ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE | CALL PROCEEDING | ← | ← 183 (Session Progress) | +| End device | | Test equipment | | | | | | | | | | | +| SETUP | ➔



| ➔ INVITE
← 407 Proxy Authentication Required
➔ ACK
➔ INVITE | | | | | | | | | | | +| CALL PROCEEDING | ← | ← 183 (Session Progress) | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_011 | Reference
subclause 5.2.10.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/14 | +| Test purpose
Call setup with user-to-user request service 2 explicit request preferred rejected in ALERTING | | | | +| Ensure that on receipt of a SETUP message containing a Facility Information Element UserUserService request invoke Service 2 preferred an INVITE request is sent. Upon receipt of a 180 (Ringing) provisional response an ALERTING message is sent. To reject the requested User to User service a Facility Information element is present set to UserUserService return error rejectedByNetwork | | | | +| DSS1 Parameter values | | | | +| SETUP
Facility
UserUserService request invoke
Service 2 preferred | | | | +| ALERTING
Facility
UserUserService return error
rejectedByNetwork | | | | + +| End device | | Test equipment | | +|--------------------------------|---|----------------|-----------------------------------| +| SETUP | → | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| ALERTING | ← | ← | 180 Ringing | +| Apply post test routine | | | | + +| TSS
UUS | TP_510_012 | Reference
subclause 5.2.10.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/14 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| Test purpose | | | | +| Call setup with user-to-user request service 2 explicit request preferred rejected in CONNECT | | | | +| Ensure that on receipt of a SETUP message containing a Facility Information Element UserUserService request invoke Service 2 preferred an INVITE request is sent. Upon receipt of a 200 OK INVITE final response a CONNECT message is sent. To reject the requested User to User service a Facility Information element is present set to UserUserService return error rejectedByNetwork. | | | | +| DSSI Parameter values | | | | +| SETUP
Facility
UserUserService request invoke
Service 2 preferred | | | | +| CONNECT
Facility
UserUserService return error
rejectedByNetwork | | | | +| End device | | Test equipment | | +| SETUP | → | → | INVITE | +| | | ← | 407 Proxy Authentication Required | +| | | → | ACK | +| | | → | INVITE | +| CONNECT | ← | ← | 200 OK INVITE | +| | | → | ACK | +| Apply post test routine | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_013 | Reference
subclause 5.2.10.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/14 | +| Test purpose | | | | +| Call setup with user-to-user request service 2 explicit request required rejected in DISCONNECT | | | | +| Ensure that on receipt of a SETUP message containing a user-user Information Element and a Facility Information Element UserUserService request invoke Service 1 required, a DISCONNECT message is sent. To reject the requested User to User service a Facility Information element is present and is set to UserUserService return error rejectedByNetwork and the Cause Information Element set 69 (requested facility not implemented). | | | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| DSSI Parameter values
SETUP
Facility
UserUserService request invoke
Service 2 required

DISCONNECT
Facility
UserUserService return error
rejectedByNetwork
Cause
Value 69 (requested facility not implemented) | | +| | End device | +| SETUP | → | +| | Test equipment | +| DISCONNECT | ← | +| RELEASE | → | +| RELEASE COMPLETE | ← | + +| | | | | +|------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_014 | Reference
subclause 5.2.10.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/15 | +|------------|------------|-----------------------------------------------------------|-------------------------------------------------| + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| Test purpose
Call setup with user-to-user request service 3 explicit request preferred rejected in CALL PROCEEDING

Ensure that on receipt of a SETUP message containing a Facility Information Element UserUserService request invoke Service 3 preferred an INVITE request is sent. Upon receipt of a 183 (Session Progress) provisional response a CALL PROCEEDING message is sent. To reject the requested User to User service a Facility Information element is present set to UserUserService return error rejectedByNetwork | | +| DSSI Parameter values
SETUP
Facility
UserUserService request invoke
Service 3 preferred

CALL PROCEEDING
Facility
UserUserService return error
rejectedByNetwork | | +| | End device | +| SETUP | → | +| | Test equipment | +| | → INVITE | +| | ← 407 Proxy Authentication Required | +| | → ACK | +| | → INVITE | +| CALL PROCEEDING | ← | +| | ← 183 (Session Progress) | +| Apply post test routine | | + +| TSS
UUS | TP_510_015 | Reference
5.2.10.1.3 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/15 | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------|-------------------------------------------------|------------|--|----------------|-------|--------------|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|----------|--------------|-------------| +| Test purpose
Call setup with user-to-user request service 3 explicit request preferred rejected in ALERTING | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a SETUP message containing a Facility Information Element UserUserService request invoke Service 3 preferred an INVITE request is sent. Upon receipt of a 180 (Ringing) provisional response an ALERTING message is sent. To reject the requested User to User service a Facility Information element is present and set to UserUserService return error rejectedByNetwork | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP
Facility
UserUserService request invoke
Service 3 preferred | | | | | | | | | | | | | | | | | | | | | | +| ALERTING
Facility
UserUserService return error
rejectedByNetwork | | | | | | | | | | | | | | | | | | | | | | +|
End device Test equipment
SETUP ➔          ➔ INVITE
             ⬅ 407 Proxy Authentication Required
             ➔ ACK
             ➔ INVITE
ALERTING ⬅          ⬅ 180 Ringing
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔          ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅          ⬅ | 180 Ringing | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | +| SETUP | ➔          ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | +| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | +| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | +| ALERTING | ⬅          ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_016 | Reference
5.2.10.1.3 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/15 | +| Test purpose
Call setup with user-to-user request service 3 explicit request preferred rejected in CONNECT | | | | +| Ensure that on receipt of a SETUP message containing a Facility Information Element UserUserService request invoke Service 3 preferred an INVITE request is sent. Upon receipt of a 200 OK INVITE final response a CONNECT message is sent. To reject the requested user to user service a facility information element is present and set to UserUserService return error rejectedByNetwork | | | | +| DSS1 Parameter values
SETUP
Facility
UserUserService request invoke
Service 3 preferred | | | | +| CONNECT
Facility
UserUserService return error
rejectedByNetwork | | | | + +| | End device | Test equipment | +|--------------------------------|------------|----------------------------------------------------------------------| +| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE | +| CONNECT | ← | ← 200 OK INVITE
→ ACK | +| Apply post test routine | | | + +| | | | | +|------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_017 | Reference
subclause 5.2.10.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/15 | +|------------|------------|-----------------------------------------------------------|-------------------------------------------------| + +##### Test purpose + +*Call setup with user-to-user request service 3 explicit request required rejected in DISCONNECT* + +Ensure that on receipt of a SETUP message containing a Facility Information Element UserUserService request invoke Service 3 required a DISCONNECT message is sent. To reject the requested user to user service a facility information element is present, it is set to UserUserService return error rejectedByNetwork and the Cause Information Element set to 69 (requested facility not implemented). + +###### DSS1 Parameter values + +SETUP + +Facility +    UserUserService request invoke +    Service 3 required + +DISCONNECT + +Facility +    UserUserService return error +    rejectedByNetwork +Cause +    Value 69 (requested facility not implemented) + +| | End device | Test equipment | +|------------------|------------|----------------| +| SETUP | → | | +| DISCONNECT | ← | | +| RELEASE | → | | +| RELEASE COMPLETE | ← | | + +| | | | | +|------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_018 | Reference
subclause 5.2.10.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +|------------|------------|-----------------------------------------------------------|-------------------------------------------------| + +##### Test purpose + +*Call setup INVITE contains a user-to-user header response in ALERTING* + +An INVITE request containing a user-to-user header was received. Ensure that on receipt of an ALERTING message where a user-user information element is present, the Protocol discriminator and user information is mapped into the uidata parameter of the user-to-user header in the sent 180 Ringing. + + + +| Message flow | | | +|--------------------------------|-----------------------|-------------------| +| | Test equipment | End device | +| INVITE1 | → | → SETUP | +| 180 Ringing | ← | ← ALERTING | +| 200 OK (INVITE) | ← | ← CONNECT | +| ACK | → | | +| Apply post test routine | | | + +| TSS
UUS | TP_510_020 | Reference
5.2.10.2.1 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------|-------------------------------------------------|--|-----------------------|-------------------|---------|---|---------|-------------|---|------------|-----------------|---|-----------|-----|---|--|---------|-------|---------------|------------|---|--------------------| +| Test purpose
Call setup INVITE contains a User-to-User header response in RELEASE in confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | +| An INVITE request containing a user-to-user header was received. Ensure that on receipt of a RELEASE message in confirmed dialogue where a user-user information element is present, the Protocol discriminator and user information is mapped into the uuidata parameter of the user-to-user header in the sent BYE request. | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
User-to-User
uuidata

BYE
User-to-User
uuidata | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP
User-user
Protocol discriminator
User information

RELEASE
User-user
Protocol discriminator
User information | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 → → SETUP
180 Ringing ← ← ALERTING
200 OK (INVITE) ← ← CONNECT
ACK →

BYE

←

← RELEASE
200 OK BYE → → RELEASE COMPLETE
| | | | | Test equipment | End device | INVITE1 | → | → SETUP | 180 Ringing | ← | ← ALERTING | 200 OK (INVITE) | ← | ← CONNECT | ACK | → | |
BYE |
← |
← RELEASE | 200 OK BYE | → | → RELEASE COMPLETE | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | +|
BYE |
← |
← RELEASE | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | → | → RELEASE COMPLETE | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_021 | Reference
subclause 5.2.10.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +| Test purpose
Call setup INVITE contains a user-to-user header response in RELEASE COMPLETE in confirmed dialogue

An INVITE request containing a user-to-user header was received. Ensure that on receipt of a RELEASE COMPLETE message in confirmed dialogue where a user-user information element is present, the Protocol discriminator and user information is mapped into the uuidata parameter of the user-to-user header in the sent BYE request. | | | | + + + +| | | | | +|-------------------------------------------------------------------------|--|--|--| +| SIP header values | | | | +| INVITE
User-to-User
uuidata

BYE
User-to-User
uuidata | | | | + + + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------|--|--|--| +| DSS1 Parameter values | | | | +| SETUP
User-user
Protocol discriminator
User information

RELEASE
User-user
Protocol discriminator
User information | | | | + + + +| | | | | +|---------------------|-----------------------|--------------------|--| +| Message flow | | | | +| | Test equipment | End device | | +| INVITE1 | → | → SETUP | | +| 180 Ringing | ← | ← ALERTING | | +| 200 OK (INVITE) | ← | ← CONNECT | | +| ACK | → | | | +| BYE | ← | ← RELEASE COMPLETE | | +| 200 OK BYE | → | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|-------------------------------------------------| +| TSS
UUS | TP_510_022 | Reference
subclause 5.2.10.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/13 | +| Test purpose
Call setup INVITE contains a user-to-user header response in RELEASE COMPLETE

An INVITE request containing a user-to-user header was received. Ensure that on receipt of a RELEASE COMPLETE message in confirmed dialogue where a user-user information element is present, the Protocol discriminator and user information is mapped into the uuidata parameter of the user-to-user header in the sent BYE request. | | | | + + + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------| +| TSS
SUB | TP_511_002 | Reference
subclause 5.2.8.1 and
Table 5.2.8.1-1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/16
AND 5.1.3/2 | +| Test purpose
Mapping of Calling party sub-address into INVITE | | | | +| Ensure that on receipt of a SETUP message where a Calling party sub-address is present, an INVITE request is sent and the From header contains an 'isub' parameter set to the 'Subaddress information' parameter as received in the SETUP. | | | | +| SIP header values
INVITE:
From: ; isub= Subaddress information; isub-encoding=nsap-ia5
or
P-Preferred-Identity: ; isub= Subaddress information; isub-encoding=nsap-ia5 | | | | +| DSS1 Parameter values
SETUP:
Calling party subaddress
Type of subaddress = NSAP
Subaddress information | | | | +| SETUP | End device
→ | Test equipment | | +| | | → INVITE | | +| | | ← 407 Proxy Authentication Required | | +| | | → ACK | | +| | | → INVITE1 | | +| Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------------------------------------------------|----------------------------------------------------------------| +| TSS
SUB | TP_511_003 | Reference
5.2.8.1:
Table 5.2.8.1-1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/16
AND 5.1.3/1 | +| Test purpose
Mapping of Calling party sub-address into INVITE | | | | +| Ensure that on receipt of a SETUP message and a Calling party sub-address is present, an INVITE request is sent and the From header contains an 'isub' parameter set to the 'Subaddress information' parameter as received in the SETUP. | | | | +| SIP header values
INVITE:
P-Asserted-Identity: ; isub= Subaddress information; isub-encoding=nsap-ia5 | | | | +| DSS1 Parameter values
SETUP:
Calling party subaddress
Type of subaddress = NSAP
Subaddress information | | | | +| SETUP | End device
→ | Test equipment | | +| | | → INVITE | | +| | | ← 407 Proxy Authentication Required | | +| | | → ACK | | +| | | → INVITE1 | | +| Apply post test routine | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------------------------|-------------------------------------------------|--|-------------------|--|-----------------------|--|-------|---|--|----------|--|--|--|--|-------------------------------------|--|--|--|--|-------|--|--|--|--|-----------|--|----------|---|--|---------------|--|---------|---|--|-------------------|--|--|--|--|-------|--|--------------------------------|--|--|--|--| +| TSS
SUB | TP_511_004 | Reference
subclause 5.2.8.1 and
Table 5.2.8.1-2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
Mapping of Connected party sub-address from 200 OK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a 200 OK INVITE response containing an isub parameter in the P-Asserted-Identity header, a CONNECT message is sent to the DSS1 user equipment and a Connected subaddress. The Type of subaddress is set according to variable ToSUB_VA in Table 7.2.5.11-1 and the subaddress information is set to isub value received in the 200 OK INVITE. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
UPDATE:
P-Asserted-Identity: ; isub= Subaddress information;isub-encoding= ToSUB_VA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT:
Connected subaddress
Type of subaddress = NSAP
Subaddress information | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
End device Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE1
ALERTING ← ← 180 Ringing
CONNECT ← ← 200 OK (INVITE)
→ ACK
Apply post test routine
| | | | | End device | | Test equipment | | SETUP | → | | → INVITE | | | | | ← 407 Proxy Authentication Required | | | | | → ACK | | | | | → INVITE1 | | ALERTING | ← | | ← 180 Ringing | | CONNECT | ← | | ← 200 OK (INVITE) | | | | | → ACK | | Apply post test routine | | | | | +| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ALERTING | ← | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONNECT | ← | | ← 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Table 7.2.5.11-1 – Mapping of isub-encoding value into Type of Subaddress** + +| ToSUB_VA | isub-encoding | Type of Subaddress | +|-------------|---------------------------|--------------------| +| ToSUB_VA_01 | isub-encoding not present | "NSAP" (000) | +| ToSUB_VA_02 | "isub-encoding=nsap-ia5" | "NSAP" (000) | +| ToSUB_VA_03 | "isub-encoding=nsap-bcd" | "NSAP" (000) | +| ToSUB_VA_04 | "isub-encoding=nsap" | "NSAP" (000) | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------|-------------------------------------------------| +| TSS
SUB | TP_511_005 | Reference
5.2.8.2:
Table 5.2.8.2-1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/16 | +| Test purpose
Mapping of Called party subaddress into SETUP | | | | +| Ensure that on receipt of an INVITE request containing a isup parameter in the To header, a SETUP message is sent and a Called party subaddress is present. The type of subaddress is set according to variable ToSUB_VA indicated in Table 7.2.5.11-2 and the subaddress information is set to isub value. | | | | +| SIP header values
INVITE:
To: ; isub= isub value; isub-encoding= ToSUB_VA | | | | + +| | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|-------------------|---------|----------------------|-------|--------------------------------|--|--| +| DSS1 Parameter values
SETUP:
Called party sub-address
Type of subaddress = ToSUB_VA
Subaddress information = isub value | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 →                  → SETUP
Apply post test routine
| Test equipment | | End device | INVITE1 | →                  → | SETUP | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | +| INVITE1 | →                  → | SETUP | | | | | | | | +| Apply post test routine | | | | | | | | | | + +| | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------------------------------------------------------------|-------------------------------------------------|-----------------------|--|-------------------|---------|----------------------|-------|--------------------------------|--|--| +| TSS
SUB | TP_511_006 | Reference
subclause 5.2.8.2 and Table 5.2.8.2-1 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/16 | | | | | | | | | | +| Test purpose
Mapping of calling party subaddress into SETUP

Ensure that on receipt of an INVITE request containing a isup parameter in the To header, a SETUP message is sent and a Called party subaddress is present. The Type of subaddress is set according to variable ToSUB_VA indicated in Table 7.2.5.11-2 and the subaddress information is set to isub value. | | | | | | | | | | | | | +| SIP header values
INVITE:
P-Asserted-Identity: ; isub= isub value; isub-encoding = ToSUB_VA | | | | | | | | | | | | | +| DSS1 Parameter values
SETUP:
Calling party subaddress
Type of subaddress = ToSUB_VA
Subaddress information | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 →                  → SETUP
Apply post test routine
| | | | Test equipment | | End device | INVITE1 | →                  → | SETUP | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | +| INVITE1 | →                  → | SETUP | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | + +**Table 7.2.5.11-2 – Mapping of isub-encoding value into Type of Subaddress** + +| ToSUB_VA | isub-encoding | Type of Subaddress | +|-------------|---------------------------|--------------------| +| ToSUB_VA_01 | isub-encoding not present | "NSAP" (000) | +| ToSUB_VA_02 | "isub-encoding=nsap-ia5" | "NSAP" (000) | +| ToSUB_VA_03 | "isub-encoding=nsap-bcd" | "NSAP" (000) | +| ToSUB_VA_04 | "isub-encoding=nsap" | "NSAP" (000) | + +450      **Rec. ITU-T Q.4014.2 (04/2019)** + +| TSS
SUB | TP_511_007 | Reference
subclause 5.2.8.2 and
Table 5.2.8.2-1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/16 | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------------------------------------|-------------------------------------------------|--|-----------------------|--|-------------------|---------|---|---|-------|-------------|---|---|----------|-----------------|---|---|---------|-----|---|--|--| +| Test purpose
Mapping of Connected subaddress from CONNECT | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a CONNECT message containing a Connected subaddress and the Type of subaddress is set to NSAP, a 200 OK INVITE is sent. An isub parameter is present in the P-Asserted-Identity header set to the value of the Subaddress information of the received Connected subaddress. The isub-encoding parameter is set to nsap-ia5 | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
200 OK INVITE:
P-Asserted-Identity: ; isub= isub value; isub-encoding =nsap-ia5 | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
CONNECT:
Connected subaddress
Type of subaddress = NSAP
Subaddress information | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 ➔ ➔ SETUP
180 Ringing ⬅ ⬅ ALERTING
200 OK (INVITE) ⬅ ⬅ CONNECT
ACK ➔

Apply post test routine

| | | | | Test equipment | | End device | INVITE1 | ➔ | ➔ | SETUP | 180 Ringing | ⬅ | ⬅ | ALERTING | 200 OK (INVITE) | ⬅ | ⬅ | CONNECT | ACK | ➔ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | ➔ | ➔ | SETUP | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | ⬅ | ALERTING | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ⬅ | ⬅ | CONNECT | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.5.12 Malicious communication identification + +##### 7.2.5.12.1 Test purposes for POTS + +| TSS
MCID | TP_512_101 | Reference
subclause C.11.4 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/15 | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------------|-------------------------------------------------|--|-----------------------|--|-------------------|---------|---|--|---------|-------------|---|--|--|---------------|---|--|----------|-----|---|--|--|-----|---|--|------------|---|--| +| Test purpose
The user requires the register of details of the last incoming call in a special record | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT is able to send an INVITE request after a session was terminated and a flash hook event was detected. The Request-Line of the INVITE request contains the special service code command dialled by the user. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE2:
Request-Line: Public user identity of SUT@pes.operator.com | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 ➔ Ringing
180 Ringing ⬅
200 OK INVITE ⬅ Off hook
ACK ➔

CASE A
BYE ➔
200 OK BYE ⬅
| | | | | Test equipment | | End device | INVITE1 | ➔ | | Ringing | 180 Ringing | ⬅ | | | 200 OK INVITE | ⬅ | | Off hook | ACK | ➔ | | | BYE | ➔ | | 200 OK BYE | ⬅ | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | ➔ | | Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | | Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK BYE | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|-----------------------------------|---|-----------------------------------| +| CASE B | | | +| BYE | ← | On hook | +| 200 OK BYE | → | | +| | | Off hook | +| | | Play a dial tone | +| | | Dial special service code command | +| INVITE | → | | +| 407 Proxy Authentication Required | ← | | +| ACK | → | | +| INVITE2 | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|-------------------------------------------------| +| TSS
MCID | TP_512_102 | Reference
subclause B.4.2.2.2.4 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/15 | +|

Test purpose
The user requires the register of details of the last incoming call in a special record

Ensure that the SUT is able to send an INVITE while a session is active and a flash hook event was detected. If the malicious communication identification (MCID) service is provisioned and requires initial flash-hook detection then the Feature Manager on receipt of flash-hook notification from the MGC component shall follow one of the following options:

  • • assume direct invocation of MCID

The SUT send a re INVITE request towards the AS. The re INVITE request is built as follows:

  • • the Request URI is set to the served user's identity, and
  • • include no Body in the re-INVITE

SIP header values
INVITE2 (initial party)
Request-Line: Public user identity of remote user
SDP
a=sendonly

200 OK 2
SDP
a=recvonly

INVITE3:
Request-Line: Public user identity of SUT

| | | | + +![](5f127fc0b2f4aabd5403ebdad4915b09_img.jpg) + +| Message flow | | | +|-------------------------|----------------|------------| +| | Test equipment | End device | +| INVITE1 | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| | | flash hook | +| INVITE2 | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| INVITE3 | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|-------------------------------------------------| +| TSS
MCID | TP_512_103 | Reference
subclause B.4.2.2.2 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/15 | +| Test purpose
The user requires the register of details of the last incoming call in a special record

Ensure that the SUT is able to send an INVITE while a session is active and a flash hook event was detected. If the collected feature code indicates MCID, the Feature Manager shall request the SIP UA to send a re INVITE request towards the AS. The re INVITE request is built as follows:
  • the Request URI is set to the served user's identity, and
  • include no Body in the re-INVITE
SIP header values
INVITE2 (initial party)
Request-Line: Public user identity of remote user
SDP
a=sendonly

200 OK 2
SDP
a=recvonly

INVITE3:
Request-Line: Public user identity of SUT | | | | + +| Message flow | | | +|--------------------------------|-----------------------|-----------------------------------| +| | Test equipment | End device | +| INVITE1 | ➔ | Ringing | +| 180 Ringing | ⬅ | | +| 200 OK INVITE | ⬅ | Off hook | +| ACK | ➔ | | +| | | flash hook | +| | | Play a dial tone | +| | | Dial special service code command | +| INVITE2 | ⬅ | | +| 200 OK INVITE | ➔ | | +| ACK | ⬅ | | +|
INVITE3 |
⬅ | | +| 200 OK INVITE | ➔ | | +| ACK | ⬅ | | +| Apply post test routine | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------|---------------------------------------------------------------| +| TSS
MCID | TP_512_104 | Reference
B.4.2.2.2.4 of [ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/15
AND 5.3/17 | +| Test purpose
The user requires the register of details of the last incoming call in a special record, McidRequestIndicator is used

Ensure that the SUT is able to send an INVITE while a session is active and a flash hook event was detected. If the MCID service is provisioned and requires initial flash-hook detection then the Feature Manager on receipt of flash-hook notification from the MGC component shall follow one of the following options:

  • • assume direct invocation of MCID

The SUT send a re INVITE request towards the AS. The re INVITE request is built as follows:

  • • the Request URI is set to the served user's identity, and
  • • include no Body in the re-INVITE
  • • the re-INVITE including a XML-MIME with XML mcid body with MCID XML Request schema containing a McidRequestIndicator set to 1.
| | | | +| SIP header values
INVITE2 (initial party)
Request-Line: Public user identity of remote user
SDP
a=sendonly

200 OK 2
SDP
a=recvonly

INVITE3:
Request-Line: Public user identity of SUT
mcid
request
McidRequestIndicator = 1
HoldingIndicator= | | | | + +![](32a27df3a5b5d00932c1feabedc034ce_img.jpg) + +| Message flow | | | +|-------------------------|----------------|------------| +| | Test equipment | End device | +| INVITE1 | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| | | flash hook | +| INVITE2 | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| INVITE3 | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| Apply post test routine | | | + +| | | | | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| +| TSS
MCID | TP_512_105 | Reference
subclause B.4.2.2.2 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/15
AND 5.3/17 | +|-------------|------------|----------------------------------------------------------|---------------------------------------------------------------| + +**Test purpose** +*The user requires the register of details of the last incoming call in a special record McidRequestIndicator is used* + +Ensure that the SUT is able to send an INVITE while a session is active and a flash hook event was detected. If the collected feature code indicates MCID, the Feature Manager shall request the SIP UA to send a re INVITE request towards the AS. The re INVITE request is built as follows: + +- the Request URI is set to the served user's identity, and +- include no Body in the re-INVITE +- the re-INVITE including a XML-MIME with XML mcid body with MCID XML Request schema containing a McidRequestIndicator set to 1. + +**SIP header values** + +INVITE2 (initial party) + Request-Line: Public user identity of remote user + SDP + a=sendonly + +200 OK 2 + SDP + a=recvonly + +INVITE3: + Request-Line: Public user identity of SUT + mcid + request + McidRequestIndicator = 1 + HoldingIndicator= + +| Message flow | | | +|-------------------------|----------------|-----------------------------------| +| | Test equipment | End device | +| INVITE1 | → | Ringing | +| 180 Ringing | ← | | +| 200 OK INVITE | ← | Off hook | +| ACK | → | | +| | | flash hook | +| | | Play a dial tone | +| | | Dial special service code command | +| INVITE2 | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| INVITE3 | ← | | +| 200 OK INVITE | → | | +| ACK | ← | | +| Apply post test routine | | | + +##### 7.2.512.2 Test purposes for ISDN + +| TSS
MCID | TP_512_201 | Reference
5.2.6.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/17
AND 5.4/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------------------------------------|---------------------------------------------------------------|--|----------------|------------|---------|---|---------|-------------|---|------------|-----------------|---|-----------|-----|---|--|---------|---|------------|-----------------|---|------------|-----|---|--|-------------------------|--|--| +| Test purpose
MCID Invocation during the active state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that on receipt of a FACILITY message containing a Facility Information Element with a McidRequest invoke component, an INVITE request is sent. A MCID XML MIME body is present and the McidRequestIndicator element is set to 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE2:
MCID XML MIME body
<?xml version="1.0" encoding="utf-8"?>   mcid     request>       McidRequestIndicator>1</       HoldingIndicator>0</
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSSI Parameter values
FACILITY: Facility
McidRequest invoke | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipmentEnd device
INVITE1→→ SETUP
180 Ringing←← ALERTING
200 OK (INVITE)←← CONNECT
ACK→
INVITE2←← FACILITY
200 OK (INVITE)→→ FACILITY
ACK←
Apply post test routine
| | | | | Test equipment | End device | INVITE1 | → | → SETUP | 180 Ringing | ← | ← ALERTING | 200 OK (INVITE) | ← | ← CONNECT | ACK | → | | INVITE2 | ← | ← FACILITY | 200 OK (INVITE) | → | → FACILITY | ACK | ← | | Apply post test routine | | | +| | Test equipment | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | ← CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 | ← | ← FACILITY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | → | → FACILITY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
MCID | TP_512_202 | Reference
subclause 5.2.6.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/17
AND NOT 5.4/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------|-------------------------------------------------------------------|--|-----------------------|--|-------------------|---------|---|---|-------|-------------|---|---|----------|-----------------|---|---|---------|-----|--|--|--|---------|---|---|----------|-----------------|---|---|----------|-----|---|--|--| +| Test purpose
MCID Invocation during the active state

Ensure that on receipt of a FACILITY message containing a Facility Information Element with a McidRequest invoke component, an INVITE request is sent. A MCID XML mMIME body is present and the McidRequestIndicator element is set to 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE2: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values
FACILITY: Facility
McidRequest invoke | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 → → SETUP
180 Ringing ← ← ALERTING
200 OK (INVITE) ← ← CONNECT
ACK
INVITE2 ← ← FACILITY
200 OK (INVITE) → → FACILITY
ACK ←

Apply post test routine

| | | | | Test equipment | | End device | INVITE1 | → | → | SETUP | 180 Ringing | ← | ← | ALERTING | 200 OK (INVITE) | ← | ← | CONNECT | ACK | | | | INVITE2 | ← | ← | FACILITY | 200 OK (INVITE) | → | → | FACILITY | ACK | ← | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | → | → | SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← | ALERTING | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | ← | CONNECT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INVITE2 | ← | ← | FACILITY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | → | → | FACILITY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +#### 7.2.5.13 Message waiting indication (MWI) + +##### 7.2.5.13.1 Test purposes for POTS + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|-------------------------------------------------| +| TSS
MWI | TP_513_101 | Reference
clause C.12.1 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 AND 5.3/19 | +| Test purpose
Update of message waiting information

Ensure that after an update of the information of waiting messages the user is indicated. On receipt of a NOTIFY request reporting the "message-summary" event, the SUT requests the following actions from the media gateway:
  • • Modify the default dial tone.
  • • Send a Message Waiting Indicator message using the ITU-T H.248 andisp/data signal.
| | | | +| SIP header values
NOTIFY
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary

MIME body:
Messages-Waiting: yes
Message-Account: sip:served_user@Server
Voice-Message: 4/1 (2/0)
Video-Message: 3/1 (1/0)
Fax-Message: 2/1 (0/1) | | | | + +| Message flow | Test equipment | End device | +|--------------------------------|-----------------------|-----------------------------| +| NOTIFY | ➔ | | +| 200 OK (NOTIFY) | ← | Display of waiting messages | +| Apply post test routine | | | + +##### 7.2.5.13.2 Test purposes for ISDN + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|-------------------------------------------------| +| TSS
MWI | TP_513_201 | Reference
clause 5.2.17 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/19 | +| Test purpose
Update of message waiting information

Ensure that after an update of the information of waiting messages the user is indicated. On receipt of a NOTIFY request reporting the "message-summary" event, the SUT requests the following actions from the media gateway:
  • • Modify the default dial tone.
  • • Send a facility information element: MWIIndicate invoke
| | | | +| SIP header values
NOTIFY
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary | | | | +| MIME body:
Messages-Waiting: yes
Message-Account: sip:served_user@Server
Voice-Message: 4/1 (2/0)
Video-Message: 3/1 (1/0)
Fax-Message: 2/1 (0/1) | | | | +| DSS1 Parameter values
FACILITY: Facility
MWIIndicate invoke
controllingUserProvidedNr= served_user
basicService
speech
telefaxGroup2-3
videotelephony | | | | +| Message flow | | | | +| | Test equipment | | End device | +| The user has subscribed the MWI Service | | | | +| NOTIFY | ➔ | ➔ | FACILITY | +| 200 OK (NOTIFY) | ← | | | +| Apply post test routine | | | | + +#### 7.2.5.14 Completion of communications to busy subscriber (CCBS) and completion of communications by no reply (CCNR) + +##### 7.2.5.14.1 Test purposes for POTS + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------|--------------------------------------|--|-----------------------|--|-------------------|---------|---|--|---------|-------------|---|--|--|---------------|---|--|----------|-----|---|--|--| +| TSS
CCBS_CCNR | TP_514_101 | Reference
clauses C.18.5 and C.18.6 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CC recall after INVITE was received

Ensure that the SUT is able to send an INVITE request and the Request line contained a 'm' parameter set to 'BS' or 'NR' | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Request-Line URI ; m=BS
or
URI ; m=NR | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE1 ➔ Ringing
180 Ringing ⬅
200 OK INVITE ⬅ Off hook
ACK ➔

Apply post test routine

| | | | | Test equipment | | End device | INVITE1 | ➔ | | Ringing | 180 Ringing | ⬅ | | | 200 OK INVITE | ⬅ | | Off hook | ACK | ➔ | | | +| | Test equipment | | End device | | | | | | | | | | | | | | | | | | | | | +| INVITE1 | ➔ | | Ringing | | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ⬅ | | | | | | | | | | | | | | | | | | | | | | | +| 200 OK INVITE | ⬅ | | Off hook | | | | | | | | | | | | | | | | | | | | | +| ACK | ➔ | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------------------------|--------------------------------------|-------------------|--|--|-----------------------|----------|--|--|--|-------------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--|---|----------------------|--|--------------------------------|--|--|--|--|---|---------------|--|--|---|-----| +| TSS
CCBS_CCNR | TP_514_102 | Reference
subclause C.18.1 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CCBS invocation

Ensure that the SUT receives, in case a called user is busy and CCBS is possible (in the network), a 183 Session Progress and in succession an announcement with the prompt to activate the call completion procedure. After the activation procedure is completed, the call is terminated by receiving a 486 Busy Here. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Off hook
Dial number ➔ INVITE
⬅ 407 Proxy Authentication Required
➔ ACK
➔ INVITE
⬅ 183 Session Progress
CCBS activation in-band
⬅ 486 Busy Here
➔ ACK
| | | | End device | | | Test equipment | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | | ⬅ | 183 Session Progress | | CCBS activation in-band | | | | | ⬅ | 486 Busy Here | | | ➔ | ACK | +| End device | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CCBS activation in-band | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ⬅ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
CCBS_CCNR | TP_514_103 | Reference
subclause C.18.1 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|--------------------------------------|------------|--|----------------|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|----------------------|--------------------------------|--|--|--|---|-------------------------------| +| Test purpose
CCNR invocation

Ensure that the SUT receives in case a called user is not responding and CCNR is possible (in the network) a 183 Session Progress is received and in succession an announcement with the prompt to activate the call completion procedure. After the activation procedure is completed, the call is terminated by receiving a 199 Early Dialogue Terminated. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
End device Test equipment
Off hook
Dial number → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
← 183 Session Progress
CCBS activation in-band
← 199 Early Dialogue Terminated
| | | | End device | | Test equipment | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | | ← | 183 Session Progress | CCBS activation in-band | | | | ← | 199 Early Dialogue Terminated | +| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CCBS activation in-band | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 199 Early Dialogue Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +##### 7.2.5.14.2 Test purposes for ISDN + +| TSS
CCBS_CCNR | TP_514_201 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|----------------|--|------------|--------|---|---------|-------------|---|------------|-----------------|---|-----------|-----|---|--|--------------------------------|--|--| +| Test purpose
CC recall after INVITE was received

Ensure that SUT sends a SETUP to the ISDN user equipment after an INVITE request was received and the Request line contained a 'm' parameter set to 'BS' or 'NR' | | | | | | | | | | | | | | | | | | | | | | +| SIP header values
INVITE
Request-Line URI ; m=BS
or
URI ; m=NR | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment End device
INVITE → → SETUP
180 Ringing ← ← ALERTING
200 OK (INVITE) ← ← CONNECT
ACK →
Apply post test routine
| | | | Test equipment | | End device | INVITE | → | → SETUP | 180 Ringing | ← | ← ALERTING | 200 OK (INVITE) | ← | ← CONNECT | ACK | → | | Apply post test routine | | | +| Test equipment | | End device | | | | | | | | | | | | | | | | | | | | +| INVITE | → | → SETUP | | | | | | | | | | | | | | | | | | | | +| 180 Ringing | ← | ← ALERTING | | | | | | | | | | | | | | | | | | | | +| 200 OK (INVITE) | ← | ← CONNECT | | | | | | | | | | | | | | | | | | | | +| ACK | → | | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|--------------------------------------|-----------------------------------|-----------------------|--|-----------------------|--|-------|---|--|---|--------|--|--|--|---|-----------------------------------|--|--|--|---|-----|--|--|--|---|--------|----------|---|--|---|----------------------|--|--|--------------------------------|--|--|---------|---|--|---|---------------|------------------|---|--|---|-----| +| TSS
CCBS_CCNR | TP_514_202 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CCBS invocation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT receives, in case a called user is busy and CCBS is possible (in the network), a 183 Session Progress and in succession an announcement with the prompt to activate the call completion procedure. After the activation procedure is completed, the call is terminated by receiving a 486 Busy Here. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
PROGRESS ← ← 183 Session Progress
CCBS activation in-band
RELEASE ← ← 486 Busy Here
RELEASE COMPLETE → → ACK
| | | | | Test equipment | | Test equipment | | SETUP | → | | → | INVITE | | | | ← | 407 Proxy Authentication Required | | | | → | ACK | | | | → | INVITE | PROGRESS | ← | | ← | 183 Session Progress | | | CCBS activation in-band | | | RELEASE | ← | | ← | 486 Busy Here | RELEASE COMPLETE | → | | → | ACK | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ← | | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CCBS activation in-band | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | ← | | ← | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | → | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------|--------------------------------------|-----------------------------------|-----------------------|--|-----------------------|--|-------|---|--|---|--------|--|--|--|---|-----------------------------------|--|--|--|---|-----|--|--|--|---|--------|----------|---|--|---|----------------------|--|--|--------------------------------|--|--|---------|---|--|---|-------------------------------|------------------|---|--|--|--| +| TSS
CCBS_CCNR | TP_514_203 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose
CCNR invocation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ensure that the SUT receives, in case a called user is not responding and CCNR is possible (in the network), a 183 Session Progress and in succession an announcement with the prompt to activate the call completion procedure. After the activation procedure is completed, the call is terminated by receiving a 199 Early Dialogue Terminated. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DSS1 Parameter values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Message flow
Test equipment Test equipment
SETUP → → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE
PROGRESS ← ← 183 Session Progress
CCNR activation in-band
RELEASE ← ← 199 Early Dialogue Terminated
RELEASE COMPLETE →
| | | | | Test equipment | | Test equipment | | SETUP | → | | → | INVITE | | | | ← | 407 Proxy Authentication Required | | | | → | ACK | | | | → | INVITE | PROGRESS | ← | | ← | 183 Session Progress | | | CCNR activation in-band | | | RELEASE | ← | | ← | 199 Early Dialogue Terminated | RELEASE COMPLETE | → | | | | +| | Test equipment | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SETUP | → | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PROGRESS | ← | | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CCNR activation in-band | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE | ← | | ← | 199 Early Dialogue Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RELEASE COMPLETE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + + + + + +# 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.4040-201602-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/Q/T-REC-Q.4040-201602-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7912e5bb9036a20601ef6d9b25c5939931915f43 --- /dev/null +++ b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deab86d9e7bff5a027677b379ab7b7a1ef39960595d9943ab4bab791d5085be9 +size 115304 diff --git a/marked/Q/T-REC-Q.4040-201602-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05af5deffef47f959a93b4dd13ebbe469887b46a --- /dev/null +++ b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17f360c980f0fedbd8b1265036bc1a1516e10423891e779ee2fecbd1100751f1 +size 162228 diff --git a/marked/Q/T-REC-Q.4040-201602-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0158c2afd2c1f03ef74cd096b125f820e9725c --- /dev/null +++ b/marked/Q/T-REC-Q.4040-201602-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cea35f678e5436c555551b77287796b918172942565bbfe639b7dbb0c44b568 +size 44647 diff --git a/marked/Q/T-REC-Q.4043-201907-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4043-201907-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6c2e98d46359c471ab397aab19cfa534f3502766 --- /dev/null +++ b/marked/Q/T-REC-Q.4043-201907-I_PDF-E/raw.md @@ -0,0 +1,597 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4043** + +(07/2019) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Testing specifications – Testing specifications for Cloud +computing + +--- + +**Interoperability testing requirements of a virtual +switch** + +Recommendation ITU-T Q.4043 + +ITU-T + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters 'ITU' are prominently displayed in blue and white within the globe. + +ITU logo + +International +Telecommunication +Union + +# 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.4043 + +# Interoperability testing requirements of a virtual switch + +## Summary + +Recommendation ITU-T Q.4043 specifies virtual switch (vswitch) interoperability testing requirements. This Recommendation introduces an overview of a vswitch and vswitch interoperability testing . This includes, but is not limited to, the definition, characteristics and general capabilities of vswitches, as well as an overview of interoperability testing of vswitches. The description of cloud-related use cases of vswitches, given in the appendix, describes the related interaction processes. Based on an analysis of involved vswitch capabilities in cloud-related use cases, the corresponding derived requirements of a vswitch's interoperability testing are introduced. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4043 | 2019-07-29 | 11 | 11.1002/1000/13979 | + +## Keywords + +Interoperability, requirements, testing, virtual switch. + +--- + +\* 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 ..... | 3 | +| 6 | Concept of a virtual switch ..... | 3 | +| 7 | Overview of virtual switch interoperability testing ..... | 4 | +| 8 | IOPT requirements of a virtual switch..... | 5 | +| 8.1 | IOPT requirements between a virtual switch and a VM ..... | 5 | +| 8.2 | IOPT requirements between a virtual switch and other network equipment ..... | 7 | +| 8.3 | IOPT requirements for control plane coordination aspect ..... | 8 | +| 8.4 | IOPT requirements between a virtual switch and computing virtualization .. | 8 | +| | Appendix I – Typical use cases of a virtual switch..... | 9 | +| I.1 | Virtual switch use cases on network connectivity..... | 9 | +| I.2 | Virtual switch use cases on network security ..... | 11 | +| I.3 | Virtual switch use cases on QoS ..... | 12 | +| I.4 | Virtual switch use cases on tunnelling ..... | 13 | +| I.5 | Virtual switch use cases on control plane coordination ..... | 14 | +| I.6 | Virtual switch use cases on reference points ..... | 15 | +| I.7 | Virtual switch use cases on computing virtualization compatibility..... | 16 | +| | Bibliography..... | 17 | + + + +## Recommendation ITU-T Q.4043 + +## Interoperability testing requirements of a virtual switch + +# 1 Scope + +This Recommendation covers the following: + +- conceptual overview of a virtual switch; +- overview of interoperability testing of a virtual switch; +- interoperability testing requirements of a virtual switch. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 cloud interoperability** [b-ITU-T Q.4040]: The capability to interact between CSCs and CSPs or between different CPSs, including the ability of CSCs to interact with cloud services and exchange information, the ability for one cloud service to work with other cloud services, and the ability for CSCs to interact with the cloud service management facilities of the CSPs. + +**3.1.2 cloud interoperability testing** [b-ITU-T Q.4040]: Verifying functions and interaction that realize the cloud interoperability. + +**3.1.3 interoperability** [b-ITU-T Y.101]: The ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 virtual switch**: Resource abstraction and control function abstracting physical network resources to offer virtual network capabilities. + +**3.2.2 virtual switch user**: Entity (e.g., a person or a program) that uses or operates a virtual switch. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +ARP Address Resolution Protocol + +AS Autonomous System + +| | | +|--------|------------------------------------------------------------| +| BGP | Border Gateway Protocol | +| DDOS | Distributed Denial of Service | +| DOS | Denial of Service | +| EGP | Exterior Gateway Protocol | +| GRE | Generic Routing Encapsulation | +| ICMP | Internet Control Message Protocol | +| ID | Identifier | +| IGP | Interior Gateway Protocol | +| IOPT | Interoperability Testing | +| IP | Internet Protocol | +| IS-IS | Intermediate System-to-Intermediate System | +| L2 | Layer 2 | +| LAN | Local Area Network | +| MAC | Media Access Control | +| MPLS | Multi-Protocol Label Switching | +| MTU | Maximum Transmission Unit | +| NAT | Network Address Translation | +| NFV | Network Function Virtualization | +| NIC | Network Interface Card | +| NSH | Network Service Header | +| NVGRE | Network Virtualization using Generic Routing Encapsulation | +| OSPF | Open Shortest Path First | +| OVSDDB | OpenvSwitch Database | +| QoS | Quality of Service | +| RIP | Routing Information Protocol | +| SDN | Software Defined Network | +| SF | Service Function | +| SFC | Service Function Chaining | +| SFF | Service Function Forwarder | +| SNMP | Simple Network Management Protocol | +| STP | Spanning Tree Protocol | +| STT | Stateless Transport Tunneling | +| TCP | Transport Control Protocol | +| UDP | User Datagram Protocol | +| VLAN | Virtual Local Area Network | +| VM | Virtual Machine | +| VNF | Virtual Network Function | + +| | | +|-------|------------------------| +| VS | Virtual switch | +| VSU | Virtual switch user | +| VXLAN | Virtual Extensible LAN | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +# 6 Concept of a virtual switch + +A virtual switch, which belongs to the resource abstraction and control function, abstracts physical network resources to enable a cloud service provider to offer virtual network capabilities for a virtual machine (VM) with capabilities of rapid elasticity, resource pooling and on-demand self-service. A virtual switch is a software implementation, which can be deployed as a part of hypervisor or as a VM. As shown in Figure 6-1, a virtual switch provides network access to the VM through the VM's virtual network interface cards (NICs), as well as network access to physical hosts through the physical NIC which is used as the uplink port of the virtual switch. + +NOTE 1 – A virtual switch only refers to the virtual switch used to provide connectivity for VMs in virtualized environments. Some variant implementations of a virtual switch can be used in other technical areas, such as containers, and are beyond the scope of this Recommendation. + +![Diagram of a virtual switch architecture. A large rectangle labeled 'Host' contains three 'VM' boxes at the top. Each 'VM' box has a 'Virtual NIC' box below it. All three 'Virtual NIC' boxes are connected to a central 'Virtual switch' box. The 'Virtual switch' box is connected to a 'Physical NIC' box at the bottom. The 'Physical NIC' box is connected to the bottom edge of the 'Host' rectangle. The diagram is labeled Q.4043(19)_F6-1.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +Diagram of a virtual switch architecture. A large rectangle labeled 'Host' contains three 'VM' boxes at the top. Each 'VM' box has a 'Virtual NIC' box below it. All three 'Virtual NIC' boxes are connected to a central 'Virtual switch' box. The 'Virtual switch' box is connected to a 'Physical NIC' box at the bottom. The 'Physical NIC' box is connected to the bottom edge of the 'Host' rectangle. The diagram is labeled Q.4043(19)\_F6-1. + +**Figure 6-1 – Overview of a virtual switch** + +Compared to physical switches, virtual switches have the following key characteristics: + +- need to provide the compatibility for computing virtualization platforms; +- can be deployed without changing the hardware environment; +- convenient to deploy new functions through software upgrades. + +Virtual switches mainly implement layer 2 (L2) network switching to meet the L2 connectivity requirements between VMs, including L2 network connectivity with VMs on the same host, and L2 network connectivity between VMs on different hosts. Virtual switches also provide additional functions for connectivity between VMs, such as virtual local area networks (LANs), traffic filtering, etc. + +Virtual switches are basic components of the resource layer in high-level architecture of software defined networks (SDNs) defined in [ITU-T Y.3300]. Through a tunnelling function, a virtual switch + +creates virtual networks decoupled from physical network. A virtual switch provides L2 network switching and layer 3 (L3) Internet protocol (IP) routing for VMs, while providing capabilities related to network isolation, quality of service (QoS) and network operation and maintenance. The virtual switch could run on mainstream server virtualization platforms. Virtual switches are basic components of an infrastructure network domain in a high-level network function virtualization (NFV) framework defined in [b-ETSI NFV-INF 003]. It provides basic network forwarding functions and advanced network functions for a VNF such as service function chain (SFC) support. + +NOTE 2 – SFC, defined in [b-IETF RFC 7498], is one of the key functions of a virtual switch for NFV. In SFC networks, virtual switches can serve as classifiers and as a service function forwarder (SFF) or SFF proxy nodes, which can forward or terminate network service header (NSH) [b-IETF RFC 8300] messages for service function (SF) and provide end-to-end NSH forwarding capabilities. [b-IETF RFC 7665]. + +# 7 Overview of virtual switch interoperability testing + +![Diagram illustrating the target areas of virtual switch interoperability testing. A central 'Virtual switch' box is connected to four other entities: 'Management entity' (top), 'Network equipment' (left), 'VM' (bottom, part of 'Computing virtualization'), and 'Computing virtualization' (bottom). Four target areas are defined: 1. VS-VM target area (Network connectivity, Network security, Network QoS); 2. VS-network equipment target area (Network connectivity, Network security, Network QoS, Tunnelling, Control plane coordination); 3. VS-management target area (Reference points); 4. VS-computing virtualization target area (Computing virtualization, Compatibility).](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram shows a central 'Virtual switch' box connected to four other entities. Each connection is associated with a specific target area for interoperability testing: + +- Management entity (top):** Connected via a vertical line. Target area 3: **VS-management** target area: Reference points. +- Network equipment (left):** Connected via a horizontal line. Target area 2: **VS-network equipment** target area: Network connectivity, Network security, Network QoS, Tunnelling, Control plane coordination. +- VM / Computing virtualization (bottom):** Connected via a vertical line. Target area 1: **VS-VM** target area: Network connectivity, Network security, Network QoS. Target area 4: **VS-computing virtualization** target area: Computing virtualization, Compatibility. + +Q.4043(19)\_F7-1 + +Diagram illustrating the target areas of virtual switch interoperability testing. A central 'Virtual switch' box is connected to four other entities: 'Management entity' (top), 'Network equipment' (left), 'VM' (bottom, part of 'Computing virtualization'), and 'Computing virtualization' (bottom). Four target areas are defined: 1. VS-VM target area (Network connectivity, Network security, Network QoS); 2. VS-network equipment target area (Network connectivity, Network security, Network QoS, Tunnelling, Control plane coordination); 3. VS-management target area (Reference points); 4. VS-computing virtualization target area (Computing virtualization, Compatibility). + +**Figure 7-1 – Target areas of virtual switch interoperability** + +Interoperability testing of a virtual switch is to verify that the virtual switch can interact with other entities as expected. As shown in Figure 7-1, according to the way a virtual switch works, there are four different target areas that need to be considered in interoperability testing (IOPT) of virtual switch as follows: + +- Target area 1: "**virtual switch – VM**", dealing with interaction between virtual switch and VM; +- Target area 2: "**virtual switch – network equipment**", dealing with interaction between virtual switch and other network equipment; +- Target area 3: "**virtual switch – management entity**", dealing with interaction between virtual switch and management entity; +- Target area 4: "**virtual switch – computing virtualization**", dealing with interaction between virtual switch and computing virtualization. + +As shown in Figure 7-1, for each target area, the IOPT should verify that the virtual switch provides specific relevant capabilities, which can be classified into the following categories: + +- **network connectivity:** The capabilities to provide access for VMs at multiple levels of the network including link layer, network layer and transport layer. Verification of network connectivity capabilities should be considered in target area 1 and 2; +- **network security:** Multi-level network security protection through the detection and processing of packet header information of each layer network to prevent spoofed traffic, + +dangerous traffic, distributed denial of service (DDOS) attacks and other threats. Verification of network security capability should be considered in target area 1 and 2; + +- **network QoS:** Control and manage capabilities of network resources by traffic classification, rate limiting, bandwidth grantee. Verification of network QoS capabilities should be considered in target area 1 and 2; + - **tunnelling:** End-to-end tunnel encapsulation capabilities to enable network communication independent of the underlying layer and provide logical isolated networks. Verification of tunneling capability should be considered in target area 2; +- NOTE – Tunnelling can be realized base on different protocols, such as virtual extensible local area network (VXLAN), multi-protocol label switching (MPLS) over generic routing encapsulation (GRE), stateless transport tunnelling (STT), network virtualization using generic routing encapsulation (NVGRE). +- **control plane coordination:** Cooperation with other network equipment on control plane to enable automated multi-device collaboration, such as distributed traffic processing logic, automated complex networking, etc. Additional logic centralized controllers are the usual implementation for control plane coordination. Verification of control plane coordination capability should be considered in target area 2; + - **reference points:** Conceptual points at the conjunction of virtual switch and management entities. Verification of reference points should be considered in target area 3; + - **computing virtualization compatibility:** The capability of virtual switch supporting deployment on computing virtualization and cooperation with computing virtualization. Verification of computing virtualization compatibility should be considered in target area 4. + +# 8 IOPT requirements of a virtual switch + +Clauses 8.1 to 8.4 provide the IOPT requirements for a virtual switch. + +## 8.1 IOPT requirements between a virtual switch and a VM + +Clauses 8.1.1 to 8.1.3 give the IOPT requirements between a virtual switch and a virtual machine. + +#### 8.1.1 IOPT requirements for network connectivity aspect + +The IOPT requirements for the network connectivity aspect are given as follows: + +- **data frame forwarding:** It is required that a virtual switch provides data frame forwarding function, which forwards data frames from virtual ports base on address information in data frames; + +NOTE – For received frames with broadcast, multicast, and unknown unicast media access control (MAC) addresses, virtual switch floods the frames to each other ports in the same broadcast domain. + +- **VLAN:** It is required that a virtual switch provides VLAN function in order to create partitioned and isolated broadcast domain in a computer network at the data link layer; +- **MTU:** It is recommended that virtual switch limits the maximum frame size allowed through the ports; +- **port aggregation:** It is recommended that a virtual switch logically uses multiple independent links as a single link to achieve flexible high bandwidth and link redundancy; +- **jumbo frame:** It is recommended that a virtual switch recognise and forward jumbo frames to reduce the number of packets and the overhead of frame header processing; +- **IP protocol:** It is required that a virtual switch supports the IP protocol [b-IETF RFC 791] and functions related to the IP protocol, including IP packet forwarding, IP subnetting [b-IETF RFC 950], IP broadcast [b-IETF RFC 922], and classless inter-domain routing (CIDR) [b-IETF RFC 4632]; + +- **transport protocol:** It is required that a virtual switch supports the transmission control protocol (TCP) protocol and the user datagram protocol (UDP) protocol; +- **ARP proxy:** It is recommended that a virtual switch provides address resolution protocol (ARP) response to VMs in order to reduce ARP broadcast packet in the broadcast domain; +- **forwarding acceleration:** It is recommended that a virtual switch supports forwarding acceleration in order to meet high forwarding performance of VNF; +- **ethernet interface:** It is recommended that a virtual switch supports Ethernet interface, including 10 Mbps Ethernet interface, 100 Mbps fast Ethernet interface, gigabit Ethernet interface, 10 G Ethernet interface, 40 G Ethernet interface and 100 G Ethernet interface; +- **Ethernet auto-negotiation:** It is recommended that a virtual switch supports a port to communicate with the device on the other end of the link to determine the optimal duplex mode and speed for the connection; +- **STP:** It is recommended that a virtual switch implements spanning tree protocol (STP) protocols [b-IEEE Std 802.1D]; +- **QinQ:** It is recommended that a virtual switch supports to encapsulate the private network VLAN tag in the public network VLAN so that the packet can be forwarded with two VLAN tags [b-IEEE 802.1q]; +- **ICMP:** It is recommended that a virtual switch supports sending Internet message control protocol (ICMP) destination unreachable messages and can choose a code that is closest to the reason for unreachable [b-IETF RFC 792] [b-IETF RFC 1122]; +- **IGMP:** It is recommended that a virtual switch supports the Internet group management protocol (IGMP) v2 [b-IETF RFC 3376]; +- **IGP:** It is recommended that a virtual switch supports interior gateway protocol (IGP) to distribute routing information within a specific autonomous system (AS), such as open shortest path first (OSPF) [b-IETF RFC 2328], Intermediate System to Intermediate System (IS-IS) [b-IETF RFC 1142] and [b-IETF RFC 1195], and routing information protocol (RIP) [b-IETF RFC 2453]; +- **EGP:** It is recommended that a virtual switch supports exterior gateway protocol (EGP) to distribute routing information between autonomous systems (ASs), such as border gateway protocol version 4 (BGP-4) [b-IETF RFC 4271]; +- **static route:** It is recommended that a virtual switch supports to define static routes to specific destinations defined by network prefix; +- **routing policy:** It is recommended that a virtual switch supports routing policy with route filtering and attributes setting to control traffic forwarding; +- **NAT:** It is recommended that a virtual switch supports network address translation (NAT) by converting the internal network address (possibly a private address) to an external network address in order to complete the communication between the internal network and the external network, and ensure the independence and privacy of the internal network; + +#### 8.1.2 IOPT requirements for network security aspect + +The IOPT requirements for the network security aspect are given as follows: + +- **traffic filtering:** It is recommended that a virtual switch filter each port's traffic according to specific filtering rules; + +NOTE 1 – The virtual switch supports various packet header information based filtering rules, including MAC address, IP address, TCP/UDP port. + +- **anti-MAC spoofing:** It is recommended that a virtual switch allow only incoming and outgoing frames with specific MAC addresses. Frames with unexpected MAC addresses will be blocked; + +- **security group:** It is recommended that a virtual switch supports security group which is a group of traffic filtering rules in order to simplify management; +NOTE 2 – Security group is provided as a function of virtual switch for SDN scenario in order to realize network isolation and access controlling by controller. Once the virtual port is associated with the security group, the internal and external traffic of the VM would be filtered with security group's rules. The security group can distinguish the traffic according to protocol, port and state to prevent the attack of unknown protocol and illegal traffic. Only traffic that meets the rules is allowed to be forward. +- **network security:** It is recommended that a virtual switch provides network layer-based security protection and supports network protection for IPv4, IPv6 and dual stacks, such as preventing a request for an IP from the source, limiting the number of concurrent requests generated by each source IP address; +- **ACL:** It is recommended that a virtual switch support IPv4, IPv6 and dual stack access control lists (ACLs), based on quintuple (source/destination IP address, source/destination port, protocol type); +- **Anti-DOS/DDOS:** It is recommended that a virtual switch supports traffic restrictions and filtering for specific protocols (e.g., TCP, UDP, ICMP) to prevent denial of service (DOS)/DDOS attacks. + +#### 8.1.3 IOPT requirements for QoS aspect + +The IOPT requirements for the QoS aspect are given as follows: + +- **traffic classification:** It is recommended that a virtual switch can assign a QoS priority tag in the header of the frame for a specified virtual port; +- **rate limiting:** It is recommended that a virtual switch limits the uplink or downlink rate of specified virtual port and flow to specific value. + +## 8.2 IOPT requirements between a virtual switch and other network equipment + +IOPT requirements for network connectivity aspect, network security aspect and network QoS aspect are given in clauses 8.1.1, 8.1.2 and 8.1.3 respectively. + +#### 8.2.1 IOPT requirements for tunnelling aspect + +- **tunnelling protocol:** It is required that a virtual switch supports a tunnel protocol in order to encapsulate frames with tunnel header, recognise and utilizes tunnel header information for forwarding, filtering and other functions; +- **bridging tunnelling-based network and VLAN network:** A virtual switch bridges specified tunnelling based network and VLAN network by maintaining the tunnelling identifier (ID) and VLAN ID mapping, and also frames encapsulating and forwarding. + +#### 8.2.2 IOPT requirements for control plane coordination aspect + +- **distributed virtual switch:** It is recommended that a virtual switch supports distributed virtual switch that extends virtual switch's ports and management across multiple servers; +NOTE – A VM remain connected to the same network as it migrates among multiple hosts connecting to same distributed virtual switch. +- **distributed routing:** It is recommended that a virtual switch supports distributed routing function in order to perform L3 routing at virtual switch without another router; +- **service function chain:** It is recommended that a virtual switch supports service function chain, including service function chain related encapsulation recognition, service classification as a service chain (SC) and service function forwarding as an SFF. + +## 8.3 IOPT requirements for control plane coordination aspect + +Clause 8.3.1 provides the IOPT requirements for the reference point aspect. + +#### 8.3.1 IOPT requirements for reference point aspect + +The IOPT requirements for the reference point aspect are given as follows: + +- **reference points for network functions:** It is recommended that a virtual switch provides reference points for network functions, including VLAN, QoS, speed limit, anti MAC spoofing, maximum transmission unit (MTU), port aggregation, jumbo frame; +- **reference points for network operation:** It is recommended that a virtual switch provides operational reference points for network operation configuration and network operation data receiving, including port traffic monitoring, port status monitoring, port mirroring, port traffic statistics, traffic alarm, fault alarm, running log; +- **reference points' format:** It is recommended that a virtual switch's reference points are implemented according to industry specifications; + +NOTE – Examples of virtual switch reference point industry specifications are OpenFlow protocol, open vswitch database management protocol (OVSDB) protocol and simple network management protocol (SNMP). + +- **change configuration remotely:** It is recommended that a virtual switch provides ability to change the configuration remotely and associated authorization mechanism. + +## 8.4 IOPT requirements between a virtual switch and computing virtualization + +Clause 8.4.1 provides the IOPT requirements for the computing virtualization aspect. + +#### 8.4.1 IOPT requirements for computing virtualization compatibility aspect + +The IOPT requirements for the computing virtualization aspect are given as follows: + +- **deploy on server virtualization platform:** It is recommended that a virtual switch supports deployment on mainstream implementations of computing virtualization technology; +- **accessing VM's virtual port:** It is recommended that a virtual switch supports accessing of VM's virtual ports while maintaining the isolation of each port; +- **VM status awareness:** It is recommended that a virtual switch be aware of the status (start, stop, migrated, etc.) of the VM's on the computing virtualization platform so that can adjust the network configuration according to the VMs' status; +- **monitoring resource allocation:** It is recommended that a virtual switch monitor resource allocation information of computing virtualization platform. + +# Appendix I + +## Typical use cases of a virtual switch + +(This appendix does not form an integral part of this Recommendation.) + +This appendix identifies use cases of a virtual switch. The table below shows the template used for the description of the use cases. + +**Table I.1 – Template for the description of a use case** + +| Use case | | +|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Title of use case | +| Abstract | Overview and features of use case | +| Figure | Figure to present the use case.
(A UML-like diagram is suggested for clarifying relations between roles) | +| Pre-conditions (optional) | Pre-conditions represent the necessary conditions or use cases that should be achieved before starting the described use case.
NOTE – As dependencies may exist among different use cases, pre-conditions and post-conditions are introduced to help understand the relationships among use cases. | +| Post-conditions (optional) | As the same for pre-condition, the post-condition describes conditions or use cases that will be carried out after the termination of a currently described use case. | +| Requirements | The title of requirements derived from the use case. | + +## I.1 Virtual switch use cases on network connectivity + +**Table I.2 – Virtual switch use case on network connectivity** + +| Use case | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Virtual switch use case on network connectivity | +| Abstract | Virtual switch provides network connectivity capabilities to VM and network equipment | +| Figure |

Image: Diagram illustrating the Virtual switch use case on network connectivity. A VSU (Virtual Switch Unit) is shown on the left, connected to a central 'Virtual switch' box. The VSU sends 'Configure traffic forwarding' to the Virtual switch. The Virtual switch contains a 'Configuration interface' and a 'Protocol stack' with 'Link layer', 'Network layer', and 'Transport layer'. The Virtual switch is connected to a 'VM' and 'Network equipment' on the right. The VM and Network equipment both receive 'Network access' and 'Traffic forwarding' from the Virtual switch. The diagram is labeled Q.4043(19)_FTab-I.2.

| + +**Table I.2 – Virtual switch use case on network connectivity** + +| | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Description |

Virtual switch user (VSU) login the configuration interface of virtual switch for configure traffic forwarding.

VSU configure virtual switch to provide basic network connections for VM or network devices, including those deployed in the form of virtual machines, by configuration interface. Virtual switch can be configured to provide network connection for different layers of network connection, such as link layer (port type, MTU, STP, VLAN, QinQ, jumbo frame), network layer (ARP, IP, NAT, routing protocol) and transport layer (TCP).

VM or network devices and virtual switches achieve network access through network access negotiation.

Virtual switch forwards traffic between VM or network devices at different layers of network.

| +| Requirements |
  • – Data frame forwarding (See clause 8.1.1)
  • – VLAN (See clause 8.1.1)
  • – MTU (See clause 8.1.1)
  • – Port aggregation (See clause 8.1.1)
  • – Jumbo frame (See clause 8.1.1)
  • – IP protocol (See clause 8.1.1)
  • – Transport protocol (See clause 8.1.1)
  • – ARP proxy (See clause 8.1.1)
  • – Forwarding acceleration (See clause 8.1.1)
  • – Ethernet interface (See clause 8.1.1)
  • – Ethernet auto-negotiation (See clause 8.1.1)
  • – STP (See clause 8.1.1)
  • – QinQ (See clause 8.1.1)
  • – ICMP (See clause 8.1.1)
  • – IGMP (See clause 8.1.1)
  • – IGP (See clause 8.1.1)
  • – EGP (See clause 8.1.1)
  • – Static route (See clause 8.1.1)
  • – Route policy (See clause 8.1.1)
  • – NAT (See clause 8.1.1)
| + +### I.2 Virtual switch use cases on network security + +**Table I.3 – Virtual switch use case on network security** + +| Use case | | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Virtual switch use case on network security | +| Abstract | Virtual switch provides network security capabilities to VM and network equipment | +| Figure |

Image: Diagram of Virtual switch use case on network security. A VSU (Virtual Switch Unit) sends 'Configure network security' to the 'Configuration interface' of a 'Virtual switch'. The 'Virtual switch' contains 'Rules' (Match fields -> processing) and 'Rule based matching'. If a match is found, 'Traffic forwarding' occurs to a 'VM'. If a 'Not match' (indicated by a red X), 'Default processing' occurs, followed by 'Traffic forwarding' to 'Network equipment'. Source: Q.4043(19)_FTab-I.3

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Description |

VSU login the configuration interface of virtual switch for network security.

VSU configure virtual switch to provide network security capabilities for VM or network devices, including those deployed in the form of virtual machines, by configuration interface. Virtual switch can be configured to provide different security related capabilities, such as traffic filtering, anti mac spoofing, security group, network security and ACL.

Virtual switch analyze incoming packets and process them accordingly according to security rules.

| +| Requirements |
  • – Traffic filtering (See clause 8.1.2)
  • – Anti MAC spoofing (See clause 8.1.2)
  • – Security group (See clause 8.1.2)
  • – Network security (See clause 8.1.2)
  • – ACL (See clause 8.1.2)
  • – Anti-DOS/DDOS (See clause 8.1.2)
| + +### I.3 Virtual switch use cases on QoS + +**Table I.4 –Virtual switch use case on QoS** + +| Use case | | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Virtual switch use case on QoS | +| Abstract | Virtual switch provides network QoS capabilities to VM and network equipment | +| Figure |

Image: Diagram showing the Virtual Switch (VSU) configuration interface with QoS tagging rules and speed limits, connected to VMs and Network equipment via traffic forwarding.

The diagram illustrates the architecture of a virtual switch (VSU) for QoS management. On the left, a grey box labeled 'VSU' has an arrow labeled 'Configure network QoS' pointing to a central grey box labeled 'Virtual switch'. Inside the 'Virtual switch' box, there is a 'Configuration interface' at the top, 'QoS tagging rules' in the middle (represented by three colored squares: red, yellow, and blue), and a 'Speed limit' section at the bottom. Below 'Speed limit' is a 'queue' represented by three stacked white rectangles. Arrows connect the 'Configuration interface' to 'QoS tagging rules', 'QoS tagging rules' to 'Speed limit', and 'Speed limit' to 'queue'. From the 'Virtual switch' box, two arrows labeled 'Traffic forwarding' point to two separate grey boxes on the right: the top one is labeled 'VM' and the bottom one is labeled 'Network equipment'. A small text label 'Q.4043(19)_FTab-I.4' is located in the bottom right corner of the diagram area.

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Description |

VSU login the configuration interface of virtual switch for network QoS.
VSU configure virtual switch to provide network QoS capabilities for VM or network devices, including those deployed in the form of virtual machines, by configuration interface. The virtual switch can be configured to classify the traffic of ports. Rate limiting can be configured for a specified port of the virtual switch. For traffic classification, the virtual switch assigns specified a QoS priority tag for received packets before forwarding. For rate limiting, the virtual switch limits the forwarding speed according to the configuration by putting the packets into queues with different priorities.

| +| Requirements |
  • – Traffic classification (See clause 8.1.3)
  • – Rate limiting (See clause 8.1.3)
| + +## I.4 Virtual switch use cases on tunnelling + +**Table I.5 – Virtual switch use case on tunnelling** + +| Use case | | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Virtual switch use case on tunnelling | +| Abstract | Virtual switch provides tunnelling capabilities between virtual switch and other network equipment. | +| Figure |

Image: Diagram illustrating the virtual switch use case on tunnelling. A VSU (Virtual Switch Unit) sends a 'Configure tunnelling' message to the 'Configuration interface' of a 'Virtual switch'. The 'Configuration interface' is connected to a 'tunnel' box, which is linked to a 'Tunnel forwarding flow table'. The 'Tunnel forwarding flow table' is also connected to another 'tunnel' box. This second 'tunnel' box is connected to 'Network equipment' via 'Traffic forwarding' and 'packets'. A blue arrow labeled 'Forward to other network equipment' points from the second 'tunnel' box to the 'Network equipment'. The 'Network equipment' contains its own 'tunnel' box and 'packets'. A small note 'Q.4043(19)_FTab-I.5' is visible in the bottom right of the diagram area.

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Description |

VSU login the configuration interface of virtual switch for tunnelling.

VSU configure virtual switch to provide tunnelling for network equipment, including those deployed in the form of virtual machines, by configuration interface.

Virtual switch can be configured to provide tunnel between virtual switch and network equipment. The virtual switch also can be configured to provide bridging between tunnelling based network and VLAN network.

Virtual switch forwarding network traffic between network equipment through tunnel. Virtual switch supports tunnelling protocol including recognise and utilizes tunnel header information for forwarding, filtering and other functions.

Virtual switch bridge network traffic between tunnelling based network and VLAN network.

| +| Requirements |
  • – Tunnelling protocol (See clause 8.2.1)
  • – Bridging tunnelling based network and VLAN network (See clause 8.2.1)
| + +## I.5 Virtual switch use cases on control plane coordination + +Table I.6 – Virtual switch use case on control plane coordination + +| Use case | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Virtual switch use case on control plane coordination | +| Abstract | Virtual switch performs control plane coordination between virtual switch and other network equipment. | +| Figure |

Image: Diagram illustrating the virtual switch use case on control plane coordination. A VSU (Virtual Switch Unit) is shown on the left, with an arrow labeled 'Configure control plan coordination' pointing to a 'Configuration interface' on a 'Virtual switch'. The 'Virtual switch' contains a 'Distributed switch/routing' block, 'L2/3 forward information', and 'SFC orchestration'. It is connected to 'Network equipment' which also contains 'L2/3 forward information' and 'SFC orchestration'. A 'Service function chain' is shown between the 'Virtual switch' and 'Network equipment'. Below this, a cloud contains two 'Virtual switch/SC/SFF' units, each connected to two 'VM/VNF' units. A red arrow points from the 'Service function chain' in the main diagram to the 'VM/VNF' units in the cloud. The diagram is labeled Q.4043(19)_FTab-I.6.

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Description |

VSU login the configuration interface of virtual switch for control plan coordination.

VSU configure virtual switch to interchange control plane information with other network equipment to achieve distributed switch/routing and service function chain.

For distributed switch/routing, Virtual machines migrating between different switches can achieve consistent forwarding capabilities without additional configuration modifications

For service function chaining, virtual switch act as SC to classify services and act as SFF to forward packets to specify next hop VM/VNF.

| +| Requirements |
  • – Distributed virtual switch (See clause 8.2.2)
  • – Distributed routing (See clause 8.2.2)
  • – Service function chain (See clause 8.2.2)
| + +## I.6 Virtual switch use cases on reference points + +**Table I.7 – Virtual switch use case on reference points** + +| Use case | | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Virtual switch use case on reference points | +| Abstract | VSU uses and operates virtual switch through the virtual switch's reference points. | +| Figure |

Image: Diagram showing the interaction between VSU, Virtual switch, VM, and Network equipment. VSU accesses a reference point on the Virtual switch. The Virtual switch contains three steps: 'Receive reference point call request', 'Translate receive reference point call request', and 'Apply'. The 'Apply' step sends traffic forwarding to both a VM and Network equipment.

 graph LR     subgraph VSU         VSU[VSU]     end     subgraph Virtual_switch [Virtual switch]         R[Receive reference point call request] --> T[Translate receive reference point call request]         T --> A[Apply]     end     subgraph VM         VM[VM]     end     subgraph Network_equipment [Network equipment]         NE[Network equipment]     end     VSU -- "Accessing reference point" --> R     A -- "Traffic forwarding" --> VM     A -- "Traffic forwarding" --> NE     

Q.4043(19)_FTab-I.7

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Description |

VSU uses and operates virtual switch through the virtual switch's reference points which are implemented according to industry specifications. Through the reference points, VSU can:

  • manages and monitors virtual switch, including port traffic monitoring, port status monitoring, port mirroring, port traffic statistics, traffic alarm, fault alarm, running log.
  • utilizes reference points of virtual switch to configure network functions and obtaining/receiving monitoring data, log and alarm.
| +| Requirements |
  • – Reference points for network functions (See clause 8.3.1)
  • – Reference points for network operation (See clause 8.3.1)
  • – Reference points' format (See clause 8.3.1)
| + +## I.7 Virtual switch use cases on computing virtualization compatibility + +**Table I.8 – Virtual switch use cases on computing virtualization compatibility** + +| Use case | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Virtual switch use cases on computing virtualization compatibility | +| Abstract | Virtual switch provide compatibility for computing virtualization platform. | +| Figure |

Image: Diagram illustrating the use case of a virtual switch (VSU) on a computing virtualization platform. The diagram shows a VSU (Virtual Switch Unit) on the left, which is connected to a 'Deploy virtual switch into computing virtualization' action. This action leads to a 'Computing virtualization' platform on the right. Inside the platform, there are two VMs (Virtual Machines) and a 'Virtual switch'. Arrows indicate 'VM accessing to virtual switch' and 'Monitoring resource allocation' from the VMs to the virtual switch. The diagram is labeled Q.4043(19)_FTab-I.8.

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Description |

VSU deploy virtual switch on computing virtualization platform. The deployment can be achieved in different way, such as to deploy as an embedded component of hypervisor, or deploy as a VM.

Virtual switch provide accessing for the VMs.

Virtual switch monitor computing virtualization platform's resource allocation.

| +| Requirements |
  • – Deploy on server virtualization platform (See clause 8.4.1)
  • – Accessing VM's virtual port (See clause 8.4.1)
  • – VM status awareness (See clause 8.4.1)
  • – Monitoring resource allocation (See clause 8.4.1)
| + +## Bibliography + +- [b-ITU-T Q.4040] Recommendation ITU-T Q.4040 (2016), *The framework and overview of cloud computing interoperability testing.* +- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.* +- [b-ETSI NFV-INF 003] ETSI GS NFV-INF 003 V1.1.1 (2014), *Network Functions Virtualisation (NFV); Infrastructure; Compute Domain.* +- [b-IEEE Std 802.1D] IEEE Std 802.1D (2004), *Standard for Local and Metropolitan Area-Media Access.* +- [b-IEEE Std 802.1q] IEEE Std 802.1q (2014), *802.1Q - Virtual LANs.* +- [b-IETF RFC 791] IETF RFC 791 (1981), *Internet Protocol.* +- [b-IETF RFC 792] IETF RFC 792 (1981), *INTERNET CONTROL MESSAGE PROTOCOL.* +- [b-IETF RFC 950] IETF RFC 950 (1985), *Internet Standard Subnetting Procedure.* +- [b-IETF RFC 922] IETF RFC 922 (1984), *Broadcasting Internet Datagrams in the Presence of Subnets.* +- [b-IETF RFC 1122] IETF RFC 1122 (1989), *Requirements for Internet Hosts -- Communication Layers.* +- [b-IETF RFC 1142] IETF RFC 1142 (1990), *OSI IS-IS Intra-domain Routing Protocol.* +- [b IETF RFC 1195] IETF RFC 1195 (1990), *Use of OSI IS-IS for Routing in TCP/IP and Dual Environments.* +- [b-IETF RFC 2328] IETF RFC 2328 (1998), *OSPF Version 2.* +- [b-IETF RFC 2453] IETF RFC 2453 (1998), *RIP Version 2.* +- [b-IETF RFC 3376] IETF RFC 2236 (1997), *Internet Group Management Protocol, Version 2.* +- [b-IETF RFC 4632] IETF RFC 4632 (2006), *Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan.* +- [b-IETF RFC 4271] IETF RFC 4271 (2006), *A Border Gateway Protocol 4 (BGP-4).* +- [b-IETF RFC 7498] IETF RFC 7498 (2015), *Problem Statement for Service Function Chaining.* +- [b-IETF RFC 7665] IETF RFC 7665 (2015), *Service Function Chaining (SFC) Architecture.* +- [b-IETF RFC 8300] IETF RFC 8300 (2018), *Network Service Header (NSH).* + + + + + +## 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.4046-202312-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4046-202312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b8c2efee44987e15626aad242a6a145ac05b8dc0 --- /dev/null +++ b/marked/Q/T-REC-Q.4046-202312-I_PDF-E/raw.md @@ -0,0 +1,427 @@ + + +# Recommendation**ITU-T Q.4046 (12/2023)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Testing specifications – Testing specifications for Cloud computing + +# --- **Interoperability testing requirements of blockchain as a service** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +## Switching and signalling, and associated measurements and tests + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| 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 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T Q.4046 + +# Interoperability testing requirements of blockchain as a service + +## Summary + +Recommendation ITU-T Q.4046 aims to provide an overview of blockchain as a service (BaaS) interoperability testing and specifies BaaS interoperability testing requirements which are derived from use cases. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4046 | 2023-12-14 | 11 | 11.1002/1000/15722 | + +## Keywords + +BaaS, interoperability testing. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview of interoperability testing of BaaS ..... | 2 | +| 6.1 Introduction of BaaS..... | 2 | +| 6.2 Interoperability testing of BaaS..... | 3 | +| 7 Interoperability testing requirements of BaaS between CSP:BaaS provider and CSN: BaaS developer ..... | 4 | +| 8 Interoperability testing requirements of BaaS between CSP: BaaS provider and CSP: BaaS provider ..... | 5 | +| 9 Interoperability testing requirements of BaaS between CSP: BaaS provider and CSC:BaaS customer..... | 5 | +| 10 Interoperability testing requirements of BaaS between CSP:BaaS provider and management entity ..... | 6 | +| Appendix I – Use cases of interoperability of blockchain as a service..... | 7 | +| I.1 Use case between CSP:BaaS provider and CSN: BaaS developer..... | 7 | +| I.2 Use case between CSP:BaaS provider and CSC:BaaS provider ..... | 8 | +| I.3 Use case between CSP:BaaS provider and CSC: BaaS customer ..... | 9 | +| I.4 Use case between CSP:BaaS provider and management entity ..... | 10 | + + + +# Recommendation ITU-T Q.4046 + +## Interoperability testing requirements of blockchain as a service + +## 1 Scope + +The scope of this Recommendation consists of: + +- 1) Overview of interoperability testing (IOPT) of blockchain as a service (BaaS) based on [ITU-T Y.3530]. +- 2) IOPT requirements of BaaS between CSP:BaaS provider and CSN:BaaS developer. +- 3) IOPT requirements of BaaS between CSP:BaaS provider and CSP:BaaS provider. +- 4) IOPT requirements of BaaS between CSP:BaaS provider and CSC:BaaS customer. +- 5) IOPT requirements of BaaS between CSP:BaaS provider and management entity. + +This Recommendation also gives typical use cases of BaaS to derive the IOPT requirements. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T F.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems*. +- [ITU-T Q.4040] Recommendation ITU-T Q.4040 (2016), *The framework and overview of cloud computing interoperability testing*. +- [ITU-T X.1400] Recommendation ITU-T X.1400 (2020), *Terms and definitions for distributed ledger technology*. +- [ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions*. +- [ITU-T Y.3502] Recommendation ITU-T Y.3502 (2014), *Information technology – Cloud computing – Reference architecture*. +- [ITU-T Y.3530] Recommendation ITU-T Y.3530 (2020), *Cloud computing – Functional requirements for blockchain as a service*. + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 blockchain** [ITU-T F.751.0]: A type of distributed ledger that is composed of digitally recorded data arranged as a successively growing chain of blocks with each block cryptographically linked and hardened against tampering and revision. + +**3.1.2 blockchain as a service (BaaS)** [ITU-T Y.3530]: A cloud service category in which the capabilities provided to the cloud service customer are the ability of setting up blockchain platforms, and developing decentralized applications using blockchain technologies. + +NOTE – Blockchain technology includes consensus algorithms, smart contracts, cryptography, etc. + +**3.1.3 interoperability** [ITU-T Y.101]: The ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged. + +### **3.2 Terms defined in this Recommendation** + +None. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------| +| API | Application Programming Interface | +| BaaS | Blockchain as a Service | +| BDaaS | Big data as a Service | +| CSC | Cloud Service Customer | +| CSN | Cloud Service Partner | +| CSP | Cloud Service Provider | +| DL | Distributed Ledger | +| DLT | Distributed Ledger Technology | +| IaaS | Infrastructure as a Service | +| IDE | Integrated Development Environment | +| IOPT | Interoperability Testing | +| P2P | Peer-to-Peer | +| PaaS | Platform as a Service | +| SaaS | Software as a Service | + +## **5 Conventions** + +In this Recommendation: + +The keywords "is required to" and "could" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. + +The keywords "is recommended" and "could" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +# **6 Overview of interoperability testing of BaaS** + +### **6.1 Introduction of BaaS** + +Blockchain as a service (BaaS) is defined as a cloud service category in which the capabilities provided to the cloud service customer (CSC) are the ability of setting up blockchain platforms, and developing decentralized applications using blockchain technologies [ITU-T Y.3530]. + +As a cloud service category, BaaS supports blockchain core features based on cloud computing infrastructure, in which an integrated development environment (IDE) for users to create, develop, + +test, host, deploy and operate blockchain related applications is provided. Blockchain users (e.g., cloud service customers) can utilize and reuse this BaaS service platform and may focus more on the selection of consensus algorithms and smart contract programming aspects rather than rebuilding their own blockchain platform from scratch. In addition, seamless service provisioning, interoperability with other platform as a service (PaaS) services, and simple development experience are also benefits of BaaS. + +The ecosystem of BaaS [ITU-T Y.3530] consists of roles, sub-roles and their activities based on cloud computing reference architecture defined in [ITU-T Y.3502] as shown in Figure 6-1, including: + +- CSN:BaaS partner (CSN:BaaS developer); +- CSP:BaaS provider (CSP:BaaS provider); +- CSC:BaaS customer (CSC:BaaS customer). + +![Diagram of the BaaS ecosystem and roles. It consists of three vertical boxes representing different roles: Cloud service partner (CSN), Cloud service provider (CSP), and Cloud service customer (CSC). The CSN box contains 'CSN: BaaS developer' and an oval with 'Design, create and maintain component for BaaS'. The CSP box contains 'CSP: BaaS provider' and three ovals: 'Provide DApp development tools', 'Provide blockchain platform', and 'Manage resource'. The CSC box contains 'CSC: BaaS customer' and an oval with 'Use BaaS'. A small code 'Q.4046(23)' is at the bottom right.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Q.4046(23) + +Diagram of the BaaS ecosystem and roles. It consists of three vertical boxes representing different roles: Cloud service partner (CSN), Cloud service provider (CSP), and Cloud service customer (CSC). The CSN box contains 'CSN: BaaS developer' and an oval with 'Design, create and maintain component for BaaS'. The CSP box contains 'CSP: BaaS provider' and three ovals: 'Provide DApp development tools', 'Provide blockchain platform', and 'Manage resource'. The CSC box contains 'CSC: BaaS customer' and an oval with 'Use BaaS'. A small code 'Q.4046(23)' is at the bottom right. + +**Figure 6-1 – BaaS ecosystem and roles [ITU-T Y.3530]** + +CSN:BaaS developer is the sub-role of cloud service partner (CSN) which is engaged in supporting activities of CSP: BaaS provider and developing blockchain services. + +CSP:BaaS provider is the sub-role of CSP performing and managing blockchain related core features (i.e., consensus mechanism, smart contract, transaction, cryptography, peer-to-peer (P2P) connectivity, ledger management) and supporting the provision of blockchain services. + +CSC:BaaS customer is the sub-role of CSC performed by end users in order to use the blockchain services from the CSP:BaaS provider. + +## 6.2 Interoperability testing of BaaS + +BaaS interoperability is a capability to interact between CSP:BaaS provider and CSN:BaaS developer, CSP:BaaS provider and CSC:BaaS customer, among different CSP:BaaS providers or between CSP:BaaS provider and management entity. During the interaction, CSN:BaaS developer allocates resources to support BaaS services development, the CSC:BaaS customer interacts with BaaS services and exchange information, one BaaS service works with other BaaS services to meet the CSC:BaaS customer's demands, and the management entity of the CSP interacts with CSP:BaaS provider to manage, monitor, maintain and optimize BaaS services. + +BaaS IOPT is used to verify functions and interaction capabilities that realize the BaaS interoperability. + +As described in [ITU-T Q.4040], the interoperability testing in different cloud capabilities types is different. There are three major IOPT scenarios: infrastructure capabilities type IOPT, platform capabilities type IOPT, and application capabilities type IOPT [ITU-T Q.4040]. Since BaaS is regarded as one of the capabilities of the PaaS, BaaS IOPT should be considered as a platform capability type IOPT. + +According to Figure 6-2, there are 4 different target areas of IOPT of BaaS in this document as follows: + +- 1 "CSP:BaaS provider-CSN:BaaS developer", dealing with interactions between CSP:BaaS provider and CSN:BaaS developer. +- 2 "CSP:BaaS provider -CSP:BaaS provider", dealing with collaboration among different CSP: BaaS providers. +- 3 "CSP:BaaS provider-CSC:BaaS customer", dealing with interactions between CSP: BaaS provider and CSC:BaaS customer. +- 4 "CSP:BaaS provider-management entity", dealing with interactions with CSP management functions. + +![Diagram illustrating the target areas of BaaS IOPT. It shows three main entities: CSN: BaaS developer, CSP: BaaS provider, and CSC: BaaS customer, represented by hexagons. Above the CSP: BaaS provider is a Management entity box containing Integration, Security, Operational support systems, Business support systems, and Development function. Arrows indicate target areas: Target area 1 between CSN and CSP; Target area 2 within the CSP; Target area 3 between CSP and CSC; and Target area 4 between the Management entity and the CSP.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram shows three hexagonal nodes arranged horizontally: CSN: BaaS developer (left), CSP: BaaS provider (center), and CSC: BaaS customer (right). Above the CSP node is a rectangular box labeled 'Management entity' containing five sub-components: 'Integration' and 'Security' (top row), 'Operational support systems' (second row), 'Business support systems' (third row), and 'Development function' (bottom row). Arrows indicate four target areas: 'Target area 1' is a double-headed arrow between CSN and CSP; 'Target area 2' is a double-headed arrow within the CSP node; 'Target area 3' is a double-headed arrow between CSP and CSC; and 'Target area 4' is a double-headed arrow between the Management entity and the CSP node. A small label 'Q.4046(23)' is at the bottom right. + +Diagram illustrating the target areas of BaaS IOPT. It shows three main entities: CSN: BaaS developer, CSP: BaaS provider, and CSC: BaaS customer, represented by hexagons. Above the CSP: BaaS provider is a Management entity box containing Integration, Security, Operational support systems, Business support systems, and Development function. Arrows indicate target areas: Target area 1 between CSN and CSP; Target area 2 within the CSP; Target area 3 between CSP and CSC; and Target area 4 between the Management entity and the CSP. + +**Figure 6-2 – Target areas of BaaS IOPT** + +It is necessary to consider these four target areas in BaaS IOPT. For each target area, specific relevant use cases need to be provided to derive testing requirements in different aspects. These requirements can be classified into the following 12 aspects: service design and development, resource management, scalability and portability, node management, smart contract, P2P connectivity, transaction processing, block record storage, data storage, consensus mechanism, authentication management and security. + +# 7 Interoperability testing requirements of BaaS between CSP:BaaS provider and CSN: BaaS developer + +It is required that CSP:BaaS provider could record the transactions in new blocks after consensus by blockchain nodes. + +NOTE – Blockchain nodes are devices or processes that participate in a distributed ledger network. + +It is required that CSP:BaaS provider could average block generation time in the initial design to ensure the stable interoperation of the BaaS. + +It is required that CSP:BaaS provider could provide a unified application programming interface (API) for accessing cloud resources and monitoring resource allocation. + +It is required that CSP:BaaS provider could provide scalability and portability for CSN:BaaS developer, such as dynamic adjustment of consensus algorithm, portability of data and portability of smart contracts. + +It is required that CSN:BaaS developer could provide a BaaS component request interface for CSP:BaaS provider. + +It is required that CSP:BaaS provider could integrate blockchain services for general demand by interacting with CSN:BaaS developers. + +It is recommended that CSP:BaaS provider could provide development tools and the ability of remote deployment for CSN:BaaS developer. + +It is recommended that CSP:BaaS provider could provide cross cloud deployment of blockchain nodes for CSN:BaaS developer to reduce the costs of deployment. + +# **8 Interoperability testing requirements of BaaS between CSP: BaaS provider and CSP: BaaS provider** + +It is required that CSP:BaaS provider could provide access rights of the blockchain network for other CSP:BaaS providers and could access the blockchain network of other CSP:BaaS providers. + +It is required that CSP:BaaS provider could provide an interface for querying BaaS information for other CSP:BaaS providers. + +NOTE 1 – The BaaS information includes blockchain type, blockchain capability, consensus type, etc. + +It is required that CSP:BaaS provider could query the information of current transaction records for other CSP:BaaS providers. + +NOTE 2 – Information includes information of the block header and transaction, which contains a timestamp, a hash of the previous block, transaction fees, etc. [ITU-T X.1400]. + +It is required that CSP:BaaS provider could query the history information of transaction records for interoperable CSP:BaaS providers. + +NOTE 3 – Transaction information contains all the information exchanged between blockchain nodes, including the transaction initiator, the transaction recipient, the interaction content, and the digital signature of the transaction initiator, etc. + +It is required that CSP:BaaS provider could provide smart contracts deployment and debug capability to other CSP:BaaS providers. + +It is required that CSP:BaaS provider could provide consensus configuration capability to other CSP:BaaS providers. + +# **9 Interoperability testing requirements of BaaS between CSP: BaaS provider and CSC:BaaS customer** + +It is required that CSP:BaaS provider could provide a service interface and interconnect with CSC:BaaS customer. + +It is required that CSP:BaaS provider could provide CSC:BaaS customer with user account management. + +It is required that CSP:BaaS provider could authenticate and authorize the CSC:BaaS customer. + +It is required that CSP:BaaS provider could provide encryption key management function for CSC:BaaS customer. + +It is required that CSP:BaaS provider could provide the ability to query transaction information. + +It is required that CSC:BaaS customer could query the status of the service, including the status of smart contracts, the status of consensus algorithms, etc. + +It is required that CSP:BaaS provider could design, debug, deploy and invoke a smart contract for CSC:BaaS customer. + +It is recommended that CSP:BaaS provider could design and configure consensus algorithms for the CSC:BaaS customer to confirm and record the transactions into a distributed ledger (DL). + +# **10 Interoperability testing requirements of BaaS between CSP:BaaS provider and management entity** + +It is required that CSP:BaaS provider could provide a connection and management interface for management entity. + +It is required that CSP:BaaS provider could execute the management instructions received from management entity. + +NOTE – Management instructions are a series of control instructions issued by the management entity to CSP:BaaS provider, including data collection instructions, function configuration instructions, etc. + +It is required that the management entity could integrate multiple CSP:BaaS providers and manage them in a unified manner. + +It is required that the management entity could monitor, manage, maintain and optimize the services provided by CSP:BaaS providers. + +It is required that the management entity could balance business hosting among CSP:BaaS providers. + +It is recommended that the management entity and CSP:BaaS provider could provide encryption and decryption mechanisms supporting encrypted transmission and storage. + +## Appendix I + +## Use cases of interoperability of blockchain as a service + +(This appendix does not form an integral part of this Recommendation.) + +This appendix presents the following blockchain as a service interoperability use cases: + +- use case of service design and development between CSP:BaaS provider and CSN:BaaS developer, +- use case of block record storage between CSP:BaaS provider and CSP:BaaS provider, +- use case of authentication management between CSP:BaaS provider and CSC:BaaS customer, +- use case of security management between CSP:BaaS providers and management entity. + +### I.1 Use case between CSP:BaaS provider and CSN: BaaS developer + +| | | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of service design and development between CSP:BaaS provider and CSN:BaaS developer | +| Description | Service design and development is important for the interoperability of the CSP:BaaS provider and CSN:BaaS developer. CSP:BaaS provider launches service component demands to CSN:BaaS developer. CSN:BaaS developer receives the demands and provides the service design and development function including service customization, service integration, service development and service deployment to develop corresponding services. Then the corresponding distributed ledger (DL) data structure, smart contract, consensus algorithm, encryption algorithm, etc. can be supplied to CSP:BaaS provider. | +| Roles | CSP:BaaS provider
CSN:BaaS developer | +| Figure and operational flows |

Image: Diagram illustrating the interoperability between CSP:BaaS provider and CSN:BaaS developer. The CSN:BaaS developer (left) contains modules for DL data structure, Smart contract, Consensus algorithm, and Encryption algorithm. The CSP:BaaS provider (right) contains nodes A, B, C, and D. Arrows show the flow: New service demand from CSP to CSN, Service customization, Service integration, and Service development from CSN to CSP, and Service deployment from CSN to the nodes.

Figure I.1 – Interoperability between CSP:BaaS provider and CSN: BaaS developer

  1. 1 CSP:BaaS provider launches a new BaaS service demand to CSN:BaaS developer.
  2. 2 CSN:BaaS developer receives and analyzes the service demand, and starts the service customization process to develop corresponding BaaS function modules, including DL data structure, smart contract, consensus algorithm, etc.
  3. 3 CSN:BaaS developer integrates the BaaS function modules as a service and deploys the service to CSP:BaaS provider.
| +| Derived requirements | It is required that CSP:BaaS provider could provide scalability and portability for CSN:BaaS developer, such as dynamic adjustment of consensus algorithms, portability of data and portability of smart contracts. | + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

It is required that CSN:BaaS developer could provide a BaaS component request interface for CSP:BaaS provider.

It is required that CSP:BaaS provider could integrate blockchain services for general demand by interacting with CSN:BaaS developers.

It is recommended that CSP:BaaS provider could provide development tools and the ability of remote deployment for CSN:BaaS developer.

It is recommended that CSP:BaaS provider could provide cross cloud deployment of blockchain nodes for CSN:BaaS developer to reduce the cost of deployment.

| +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### I.2 Use case between CSP:BaaS provider and CSC:BaaS provider + +| | | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of block record storage between CSP:BaaS provider and CSP:BaaS provider | +| Description |

Blockchain is a type of distributed ledger technology (DLT) in which nodes can create new blocks containing the transactions and smart contracts.

This use case provides a scenario for block record storage, demonstrating the storage capability by sending transactions between CSP:BaaS provider A and CSP:BaaS provider B.

| +| Roles | CSP:BaaS provider | +| Figure and operational flows |

Image: Diagram illustrating the interoperability between CSP:BaaS provider A and CSP:BaaS provider B. CSP:BaaS provider B has nodes A, B, C, and D. Node D is shown creating a new block with a 'Block header' (Previous hash, Data hash, ..., Block body, Smart contract, Transactions) and 'Transactions'. A 'Making new block' icon is next to it. CSP:BaaS provider A has nodes A, B, C, and D. Node B is shown sending a transaction to Node D of CSP:BaaS provider B. A large arrow points from CSP:BaaS provider A to CSP:BaaS provider B. A smaller arrow points from the 'Transactions' box in CSP:BaaS provider B to the 'Block header' box. A small label 'Q.4046(23)' is in the bottom right corner of the diagram area.

Figure I.2 – Interoperability between CSP:BaaS provider and CSP:BaaS provider

  1. 1 CSP:BaaS providers could interconnect firstly and create at least one BaaS user on each platform.
  2. 2 CSP:BaaS provider A sends a transaction to CSP:BaaS provider B using cross-chain technology.
  3. 3 CSP:BaaS provider B receives and collects transaction details per Node, such as Node D.
  4. 4 Node D creates a block and records the information of the previous block, transaction, etc. As shown in the figure, the block header contains the previous hash, root hash generated from transactions, data hash, etc.
  5. 5 CSP:BaaS provider A queries the details information and history information of the record to trace the transaction status.
| +| Derived requirements |

It is required that CSP:BaaS provider could provide access rights of the blockchain network for other CSP:BaaS providers and could access the blockchain network of other CSP:BaaS providers.

It is required that CSP:BaaS provider could provide an interface for querying BaaS information for other CSP:BaaS providers.

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

It is required that CSP:BaaS provider could query the information of the current transaction record for other CSP:BaaS providers.

It is required that CSP:BaaS provider could query the history information of the transaction record for interoperable CSP:BaaS provider.

| +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### I.3 Use case between CSP:BaaS provider and CSC: BaaS customer + +| | | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of authentication management between CSP:BaaS provider and CSC: BaaS customer | +| Description | Authentication management is fundamental to interoperability. BaaS with access management capabilities can better allocate resources according to a permission level list. This use case provides a cloud resource sharing scenario of authentication management capability between a CSP:BaaS provider and CSC: BaaS customer. | +| Roles | CSP:BaaS provider
CSC:BaaS customer | +| Figure and operational flows |

Image: Diagram illustrating the interoperability between CSP:BaaS provider and CSC: BaaS customer. The CSP:BaaS provider side shows a network of nodes (A, B, C, D) connected by dashed lines. A 'Execute contract' action leads to a block structure containing 'Block header' (Previous hash, Data hash, ...) and 'Block body' (Smart contract, Transactions). The CSC: BaaS customer side shows a user interface with a contract code snippet: '</> contract{ Address [] = ... } </>'. Arrows indicate the flow of 'Output resource API' from the CSP to the CSC, and 'Resource API' from the CSC to a 'Cloud resource' icon. A small label 'Q.4046(23)' is present in the bottom right of the diagram area.

Figure I.3 – Interoperability between CSP:BaaS provider and CSC: BaaS customer

  1. 1 CSC:BaaS customer requests a cloud resource by metadata of resource, which are provided by CSP:BaaS provider.
  2. 2 CSC:BaaS customer writes the resource request into the contract code according to the contract rules and sends it to the CSP:BaaS provider.
  3. 3 CSP:BaaS provider receives this contract request and records it to a new block and estimates the resource access authority of CSC:BaaS customer.
  4. 4 The resource API is sent to the CSC:BaaS customer automatically from the CSP:BaaS provider if the permissions are met.
  5. 5 CSC:BaaS customer uses this API to acquire the cloud resource.
| +| Derived requirements |

It is required that CSP:BaaS provider could provide a service interface and interconnect with the CSC:BaaS customer.

It is required that CSP:BaaS provider could provide CSC:BaaS customer with user account management.

It is required that CSP:BaaS provider could authenticate and authorize the CSC:BaaS customer.

It is required that CSP:BaaS provider could provide an encryption key management function for CSC:BaaS customer.

It is required that CSP:BaaS provider could provide the ability to query transaction information.

| + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | It is required that CSC: BaaS customer could query the status of the service, including the status of smart contracts, the status of consensus algorithms, etc. | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### I.4 Use case between CSP:BaaS provider and management entity + +| | | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Use case of security management between CSP:BaaS providers and management entity | +| Description |

Management entity can monitor and manage multiple CSP:BaaS providers. CSP:BaaS providers can adjust the security configuration (e.g., encryption mechanism) according to the directives of the management entity.

This use case shows the security management capability of the management entity to adjust the security configuration between CSP:BaaS providers.

| +| Roles |

CSP:BaaS provider

Management entity

| +| Figure and operational flows |
Diagram of interoperability between CSP:BaaS providers and a management entity.

The diagram illustrates a hierarchical management structure. At the top is a 'Management entity' box containing sub-functions: 'Integration', 'Security', 'Operational support systems', 'Business support systems', and 'Development function'. Below this, there are three hexagonal blocks representing 'CSP: BaaS provider A', 'CSP: BaaS provider B', and a third unnamed provider indicated by dots. Each provider contains a network of nodes labeled A, B, C, and D. A bidirectional arrow labeled 'Management instruction' connects the Management entity to the providers, indicating a flow of instructions down and status information up. The diagram is indexed as Q.4046(23).

Figure I.4 – Interoperability between CSP:BaaS provider and management entity

  1. 1 Management entity monitors multiple CSP:BaaS providers and collects their status information.
  2. 2 Management entity delivers the encryption and decryption mechanism configuration instruction.
  3. 3 CSP:BaaS providers receive the instruction and configures the mechanism.
  4. 4 CSP:BaaS providers realize encrypted transmission and storage based on the set of encryption and decryption mechanisms.
| +| Derived requirements |

It is required that CSP:BaaS provider could provide a connection and management interface for the management entity.

It is required that CSP:BaaS provider can execute the encryption and decryption mechanism configuration instructions received from the management entity.

It is required that management entity could integrate multiple CSP:BaaS providers and manage them in a unified manner.

It is recommended that the management entity and CSP:BaaS provider could provide encryption and decryption mechanisms supporting encrypted transmission and storage.

| + + + +## 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.4064-202009-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4064-202009-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d8e0db6750233e2cd75dc3ee80fd9d8f0c3ce0d0 --- /dev/null +++ b/marked/Q/T-REC-Q.4064-202009-I_PDF-E/raw.md @@ -0,0 +1,709 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4064** + +(09/2020) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Testing specifications – Testing specifications for +IMT-2020 and IoT + +--- + +**Interoperability testing requirements for a +virtualized broadband network gateway** + +Recommendation ITU-T Q.4064 + +# 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 P2P 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.4064 + +# Interoperability testing requirements for a virtualized broadband network gateway + +## Summary + +Recommendation ITU-T Q.4064 specifies virtualized broadband network gateway (vBNG) interoperability testing requirements. As a background, Recommendation ITU-T Q.4064 gives an overview of the vBNG and its interoperability testing, which includes, but is not limited to, the definition, characteristics and general capabilities of vBNG. Use cases of a vBNG are provided in an appendix. Based on an analysis of the vBNG capabilities involved in use cases, the corresponding requirements for vBNG interoperability testing are introduced. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4064 | 2020-09-29 | 11 | 11.1002/1000/14418 | + +## Keywords + +Interoperability, requirements, testing, virtual BNG. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------------|------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 4 | +| 6 | Overview of vBNG..... | 4 | +| 6.1 | Concept of vBNG ..... | 4 | +| 6.2 | Framework of vBNG..... | 5 | +| 7 | IOPT framework of vBNG ..... | 6 | +| 8 | IOPT requirements of vBNG..... | 7 | +| 8.1 | IOPT requirements between vBNG and CPE/vCPE ..... | 7 | +| 8.2 | IOPT requirements between vBNG and BNG/vBNG/PE ..... | 9 | +| 8.3 | IOPT requirements between vBNG and management system ..... | 10 | +| Appendix I | – Typical use cases of vBNG..... | 12 | +| I.1 | PPPoE access use case..... | 12 | +| I.2 | IPoE access use case..... | 14 | +| I.3 | VPN service use case..... | 16 | +| I.4 | Multicast service use case ..... | 18 | +| I.5 | SR use case ..... | 20 | +| I.6 | Network management use case ..... | 21 | +| | Bibliography..... | 23 | + + + +## Recommendation ITU-T Q.4064 + +# Interoperability testing requirements for a virtualized broadband network gateway + +# 1 Scope + +This Recommendation gives: + +- 1) an overview of the virtualized broadband network gateway (vBNG) comprising: + - a) the concept of vBNG, including its definition, characteristics and general capabilities, + - b) the framework for vBNG, which consists of control and data planes; +- 2) an interoperability testing (IOPT) framework for vBNG based on its the target areas; +- 3) IOPT requirements for vBNG. + +NOTE – The IOPT requirements of vBNG should include those derived from analysis of typical use cases, which should address the need to verify cloud-related vBNG capabilities. + +# 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.3315] Recommendation ITU-T Q.3315 (2015), *Signalling requirements for flexible network service combination on broadband network gateway*. +- [ITU-T Q.4040] Recommendation ITU-T Q.4040 (2016), *The framework and overview of cloud computing interoperability testing*. +- [ITU-T Y.3011] Recommendation ITU-T Y.3011 (2012), *Framework of network virtualization for future networks*. +- [ITU-T Y.3500] Recommendation ITU-T Y.3500 (2014), *Information technology – Cloud computing – Overview and vocabulary*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 broadband network gateway (BNG)** [ITU-T Q.3315]: The access point to the provider's IP network for wireline broadband services. +- 3.1.2 cloud service customer (CSC)** [b-ITU-T Y.3502]: A party which is in a business relationship for the purpose of using cloud services. +- 3.1.3 cloud service provider (CSP)** [b-ITU-T Y.3502]: A party which makes cloud services available. +- 3.1.4 network virtualization** [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.1.5 cloud computing** [ITU-T Y.3500]: Paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand. + +**3.1.6 cloud interoperability** [ITU-T Q.4040]: The capability to interact between CSCs and CSPs or between different CSPs, including the ability of CSCs to interact with cloud services and exchange information, the ability for one cloud service to work with other cloud services, and the ability for CSCs to interact with the cloud service management facilities of the CSPs. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 virtualized broadband network gateway (vBNG)**: A virtualized solution of a broadband network gateway, attained by using virtualization technologies, which is responsible for user access and traffic forwarding to realize broadband services. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|-------------------------------------------------------------------| +| 6VPE | Internet protocol version 6 Virtual private network Provider Edge | +| AAA | Authentication, Authorization and Accounting | +| ACK | Acknowledgement | +| ACL | Access Control List | +| ARP | Address Resolution Protocol | +| ASIC | Application Specific Integrated Circuit | +| BGP | Border Gateway Protocol | +| BGP-FS | BGP-Flow Specification | +| BNG | Broadband Network Gateway | +| BSS | Business Support System | +| CHAP | Challenge Handshake Authentication Protocol | +| CPE | Customer Premises Equipment | +| CPU | Central Processing Unit | +| CSC | Cloud Service Customer | +| CSP | Cloud Service Provider | +| CVLAN | Customer Virtual Local Area Network | +| DDoS | Distributed Denial of Service | +| DHCP | Dynamic Host Configuration Protocol | +| DPI | Deep Packet Inspection | +| DNS | Domain Name System | +| DoS | Denial of service | +| FW | Firewall | + +| | | +|-------------|-----------------------------------------------| +| GRE | Generic Routing Encapsulation | +| HQoS | Hierarchical Quality of Service | +| ICMP | Internet Control Message Protocol | +| IGMP | Internet Group Management Protocol | +| IGP | Interior Gateway Protocol | +| IOPT | Interoperability Testing | +| IP | Internet Protocol | +| IPCP | Internet Protocol Control Protocol | +| IPoE | IP over Ethernet | +| IPvn | Internet Protocol version n | +| IPTV | Internet Protocol Television | +| ISIS | Intermediate System-Intermediate System | +| ITMS | Integrated Terminal Management System | +| L2TP | Layer 2 Tunnelling Protocol | +| LCP | Link Control Protocol | +| MAC | Media Access Control | +| MANO | Management and Orchestration | +| MLD | Multicast Listener Discovery | +| MPLS | Multi-Protocol Label Switching | +| MSDP | Multicast Source Discovery Protocol | +| MTU | Maximum Transmission Unit | +| MVPN | Multicast Virtual Private Network | +| NAS-Port-ID | Network Access Server Port Identifier | +| NAT | Network Address Translation | +| NCP | Network Control Protocol | +| NFVO | Network Function Virtualization Orchestration | +| NP | Network Processor | +| OSPF | Open Shortest Path First | +| OSS | Operation Support System | +| PAP | Password Authentication Protocol | +| PE | Provider Edge | +| PIM-DM | Protocol Independent Multicast-Dense Mode | +| PIM-SM | Protocol Independent Multicast-Sparse Mode | +| PPP | Point-to-Point Protocol | +| PPPoE | Point-to-Point Protocol over Ethernet | +| QinQ | 802.1Q-in-802.1Q | +| QoS | Quality of Service | + +| | | +|--------|--------------------------------------------| +| RADIUS | Remote Authentication Dial-In User Service | +| SFC | Service Function Chain | +| SID | Segment Identifier | +| SNMP | Simple Network Management Protocol | +| SR | Segment Routing | +| SR-TE | Segment Routing-Traffic Engineering | +| SVLAN | Service Virtual Local Area Network | +| TCP | Transmission Control Protocol | +| TE | Traffic Engineering | +| UDP | User Datagram Protocol | +| URPF | Unicast Reverse Path Forwarding | +| VAS | Value-Added Service | +| vBNG | virtualized Broadband Network Gateway | +| vCPE | virtual Customer Premises Equipment | +| VIM | Virtual Infrastructure Manager | +| VLL | Virtual Leased Line | +| VLAN | Virtual Local Area Network | +| VM | Virtual Machine | +| VNFM | Virtual Network Function Manager | +| VPLS | Virtual Private Local area network Service | +| VPN | Virtual Private Network | +| VxLAN | Virtual extensible Local Area Network | +| WAN | Wide Area Network | + +# 5 Conventions + +The keywords "is required" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. + +# 6 Overview of vBNG + +## 6.1 Concept of vBNG + +A broadband network gateway (BNG) is defined as the access point to a provider's Internet protocol (IP) network for wireline broadband services [ITU-T Q.3315]. vBNG is the virtualization of a BNG by using virtualization technologies, which include network virtualization [ITU-T Y.3011] and compute virtualization technologies. Virtualization technologies aggregate multiple resources, which can be distributed in different equipment in a provider and appear as a single resource. vBNG should meet the signalling requirements between a vBNG and service platform for flexible network service combination on the BNG specified in [ITU-T Q.3315], and the on-demand service based on flexible function provision. + +NOTE – The service platform acts as an intermediate layer between the network services and the BNG. + +Cloud computing is defined in clause 3.1.5. As a virtualized network element, vBNG can be deployed in a scalable and elastic pool of shared physical or virtual resources, and can provide self-service and administration based on the management system, such as management and orchestration (MANO). vBNG belongs to cloud computing, and its IOPT is a kind of cloud IOPT. Compared to BNG, the characteristics of vBNG can be summarized as follows. + +- vBNG can provide such service functions as VNF, so it should provide compatibility for a network function virtualization platform. +- vBNG can provide service functions on demand and customized functions for specific requirements such as deep packet inspection (DPI), firewall (FW) and service function chain (SFC) functions. +- vBNG can provide flexible extensibility of a logical isolated partition to improve service capabilities. One example is that vBNG can extend a data plane by adding forwarding equipment both in virtualized and traditional forms to improve bandwidth. + +vBNG usually provides both layer 2 (L2) and layer 3 (L3) network functions. For L2 network functions, it includes user access services and L2 virtual private network (VPN) services, such as a virtual private local area network service (VPLS) and virtual leased line (VLL). For L3 network functions, it refers to routing and multi-protocol label switching (MPLS) services, such as L3 VPN services. + +vBNG often interacts with customer premises equipment/virtual customer premises equipment (CPE/vCPE) to provide user access services, and interacts with BNG/vBNG/provider edge (PE) to realize L3 network functions and L2 VPN service. In order to realize the control and management functions of network and service, a vBNG should also interact with a management system such as an operation support system/business support system (OSS/BSS) and MANO. + +## 6.2 Framework of vBNG + +The framework of vBNG in this Recommendation is shown in Figure 6-1. It consists of control and data planes. + +![Diagram of the vBNG framework showing control and data planes.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +The diagram illustrates the internal architecture of a vBNG. It is contained within a large rectangular box labeled 'vBNG' at the top. Inside this box, there are two main horizontal sections. The upper section is labeled 'vBNG control plane' and contains two smaller boxes labeled 'Control VM', with an ellipsis between them. The lower section is labeled 'vBNG data plane'. A vertical blue line separates the control plane from the data plane. At the bottom right of the diagram, there is a small text label: 'Q.4064(20)\_F6-1'. + +Diagram of the vBNG framework showing control and data planes. + +Figure 6-1 – The framework of vBNG + +The vBNG control plane is responsible for user access management, user management, address management, authentication management, service management, etc. The vBNG data plane is responsible for packet forwarding. + +NOTE 1 – User access management establishes connections with users, including point-to-point protocol over Ethernet (PPPoE), IP over Ethernet (IPoE). + +NOTE 2 – User management is responsible for the unified management of user authority, status and business information, such as accounting information. + +NOTE 3 – Address management realizes unified allocation and management of user address and service address based on local or external address pools. + +NOTE 4 – Authentication management achieves user authentication, which can be implemented locally or remotely. Remotely, vBNG is used as authentication agent by interacting with authentication, authorization and accounting (AAA) systems to realize authentication. Locally, vBNG acts as authentication server to provide the authentication function. + +NOTE 5 – Service management is responsible for management of Internet access, L2 or L3 VPN, multicast services, etc. + +The vBNG control plane is responsible for functions that need flexible programming of network function and elastic computing capacity, so the control plane is usually deployed as virtual machines (VMs). The vBNG data plane sometimes needs low forwarding capacity when carrying low traffic services like an integrated terminal management system (ITMS), while sometimes it requires high forwarding performance for large capacity and low latency when carrying heavy traffic and delay-sensitive services such as video and Internet protocol television (IPTV). According to the different application scenarios, there are a few kinds of implementation mode for data planes, including equipment based on the central processing unit (CPU), application specific integrated circuit (ASIC) and network processor (NP) chips. + +NOTE 6 – Network equipment carried by CPU chips, such as a router deployed on an x86 server, can provide flexible deployment of network functions for more open architecture. A VM is deployed on shared physical resources based on virtualization technology, thus a VM can flexibly expand of functions and performance. Based on the preceding advantages, a vBNG control plane is usually deployed as a VM to flexibly program network function and elastic computing capacity. + +# 7 IOPT framework of vBNG + +According to the framework and overview of cloud computing IOPT in [ITU-T Q.4040], which consists of interaction between cloud service customer-cloud service provider (CSC-CSP), CSP-CSP and CSP-management system corresponding to three different target areas, there also are three target areas of vBNG IOPT. + +- Target area A: dealing with the interaction between vBNG and access users to provide user access services. + +NOTE 1 – One example of target area A interaction is PPPoE or IPoE access service. + +- Target area B: dealing with the interaction between vBNG and BNG/vBNG/PE to provide network services. + +NOTE 2 – One example of target area B interaction is VPN service. + +- Target area C: dealing with the interaction between vBNG and a management entity to provide operation- and business-supporting capabilities. + +NOTE 3 – One example of target area C interaction is AAA service. + +Based on these three target areas, The IOPT framework of vBNG is as shown in Figure 7-1. + +![Diagram of the IOPT architecture of vBNG. The diagram shows a central vBNG unit connected to three external entities: CPE/vCPE on the left, BNG/vBNG/PE on the right, and a Management system at the top. The vBNG unit is divided into a 'vBNG control plane' (containing two 'Control VM' boxes) and a 'vBNG data plane'. Red lines with circled numbers indicate the interoperability test points: 1) between CPE/vCPE and the vBNG control plane, 2) within the vBNG unit, 3) between the vBNG control plane and BNG/vBNG/PE, and 4) between the Management system and the vBNG control plane. A legend at the bottom indicates that red lines represent 'Interoperability test'. The text 'Q.4064(20)_F7-1' is in the bottom right corner.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Diagram of the IOPT architecture of vBNG. The diagram shows a central vBNG unit connected to three external entities: CPE/vCPE on the left, BNG/vBNG/PE on the right, and a Management system at the top. The vBNG unit is divided into a 'vBNG control plane' (containing two 'Control VM' boxes) and a 'vBNG data plane'. Red lines with circled numbers indicate the interoperability test points: 1) between CPE/vCPE and the vBNG control plane, 2) within the vBNG unit, 3) between the vBNG control plane and BNG/vBNG/PE, and 4) between the Management system and the vBNG control plane. A legend at the bottom indicates that red lines represent 'Interoperability test'. The text 'Q.4064(20)\_F7-1' is in the bottom right corner. + +**Figure 7-1 – The IOPT architecture of vBNG** + +The test entities include CPE/vCPE, vBNG, BNG/vBNG/PE and a management system. + +- 1) CPE/vCPE: Equipment deployed on the customer side by service providers to provide wide area network (WAN) services, such as border gateways, network address translation (NAT), and other value-added services (VASS) to customers, especially enterprise customers. +- 2) vBNG: The IOPT subject. +- 3) BNG/vBNG/PE: The network device deployed on the WAN side to provide network services, such as those for routing, MPLS and VPN. In the IOPT framework, this entity is peer network equipment interacting with the vBNG under test. +- 4) Management system: The management system includes the service and operation management system such as OSS/BSS and MANO. It mainly provides device, network and service management functions, including billing management, performance management, fault management, configuration management and security management. + +NOTE 4 – The MANO system includes network function virtualization orchestration (NFVO), virtual network function manager (VNFM) and virtual infrastructure manager (VIM). + +The IOPT between those entities includes the IOPT of vBNG-CPE/vCPE, vBNG-BNG/vBNG/PE and vBNG-management system. + +- vBNG-CPE/vCPE: The IOPT between a vBNG and CPE/vCPE, including verification that user access and authentication functions can be provided through interaction between vBNG and CPE/vCPE. +- vBNG-BNG/vBNG/PE: The IOPT between a vBNG and BNG/vBNG/PE, including verification that routing and tunnel functions can be established between vBNG-BNG/vBNG/PE. +- vBNG-management system: The IOPT between a vBNG and management system, including verification that a vBNG can be managed by an OSS/BSS and MANO to support device management, service management and network management functions. + +# 8 IOPT requirements of vBNG + +## 8.1 IOPT requirements between vBNG and CPE/vCPE + +According to different access modes of user and service, IOPT requirements between vBNG and CPE/vCPE include at least the following aspects. + +– **PPPoE:** It is required that a vBNG support PPPoE service, including provision of a point-to-point protocol (PPP) connection with CPE/vCPE and allocation of an IP address for a user to access the Internet through CPE/vCPE [b-IETF RFC 2516]. The service should provide both IPv4 and IPv6 access functions. + +– **IPoE:** It is required that vBNG support IPoE service, including provision of related access and control functions. The service should provide both IPv4 and IPv6 access functions. + +NOTE 1 – Dedicated access service can also be involved in IPoE service, the dedicated access service can provide a fixed IP address to customer. + +– **Multicast group management protocol:** It is required that vBNG support access and control functions of multicast users based on the Internet group management protocol (IGMP) [b-IETF RFC 3376] or multicast listener discovery (MLD) protocol [b-IETF RFC 3810]. The service should provide both IPv4 and IPv6 access functions. + +– **NAT:** It is required that vBNG support NAT by converting the internal network address (possibly a private address) to an external network address in order to complete the communication between the internal and external networks, and ensure the independence and privacy of the internal network. + +– **QoS:** It is required that vBNG support quality of service (QoS) functions for grantee network and service demands, such as traffic classification, bandwidth guarantee, queue scheduling, congestion control and hierarchical quality of service (HQoS). + +NOTE 2 – HQoS service refers to multilevel traffic scheduling, such as port, service virtual local area network (SVLAN), customer virtual local area network (CVLAN), and session. + +– **VLAN:** It is required that vBNG support a virtual local area network (VLAN) function in order to create a partitioned and isolated broadcast domain at the data link layer. + +– **QinQ (802.1Q-in-802.1Q):** It is required that vBNG support encapsulation of the private network VLAN tag in the public network VLAN so that the packet can be forwarded with two VLAN tags [b-IEEE 802.1Q]. + +– **VAS:** It is recommended that vBNG support VASs, such as FW and DPI. + +NOTE 3 – VASs are premium features and add-ons to basic functions like user access; this kind of function can be deployed on demand. + +– **ACL:** It is required that vBNG support an access control list (ACL) function to help to realize the packets filtering and forwarding control by permitting or denying the matched packets. + +– **ARP:** It is required that vBNG support provision of an address resolution protocol (ARP) response to CPE/vCPE in order to shrink the ARP domain size and consequently reduce the number of ARP broadcast packets that will cause ARP flooding when it is too large. + +– **DNS:** It is recommended that vBNG support provision of a domain name system (DNS) function by creating a mapping between the domain name (host) and the address (IP). + +– **Access redirection:** It is required that vBNG support redirecting users to a specific web page or IP address. + +NOTE 4 – When a customer intends to access the Internet, the network provider can redirect the web page of the customer to a fixed site once the customer logged in, such as a welcome page. + +– **MTU (maximum transmission unit):** It is required that vBNG support the limitation of the maximum frame size allowed through the port. + +– **Port aggregation:** It is required that vBNG support a port aggregation function by logically using multiple independent links as a single link to achieve flexible high bandwidth and link redundancy. + +– **Jumbo frame:** It is required that vBNG support jumbo frames to reduce the number of packets and the overhead of frame header processing. + +- **Anti-DoS/DDoS:** It is required that vBNG support traffic restrictions and filtering for specific protocols (such as the transmission control protocol (TCP), user datagram protocol (UDP) and Internet control message protocol (ICMP)) to prevent denial of service or distributed denial of service (DoS/DDoS) attacks. +- **URPF:** It is required that vBNG support unicast reverse path forwarding (URPF) to prevent network attacks based on source address spoofing. + +## 8.2 IOPT requirements between vBNG and BNG/vBNG/PE + +According to the different routing protocol and tunnel protocol, the IOPT requirements between vBNG and BNG/vBNG/PE include at least the following aspects. + +- **IGP routing protocols:** It is required that vBNG support the interior gateway protocol (IGP) for routing, including the open shortest path first (OSPF) [b-IETF RFC 2328], intermediate system-intermediate system (ISIS) [b-IETF RFC 1142] protocols. IGP can realize route discovery and path computing, and generate network topology based on the link state collection. +- **BGP routing protocol:** It is required that vBNG support aBGP routing protocol [b-IETF RFC 4273]. BGP is a dynamic routing protocol between AS, whose focus is not to find and calculate routes, but to choose the best route between AS and control the propagation of routes. +- **Multicast routing protocols:** It is required that vBNG support multicast routing protocols such as protocol independent multicast-dense mode (PIM-DM) [b-IETF RFC 3973], protocol independent multicast-sparse mode (PIM-SM) [b-IETF RFC 7761], multicast source discovery protocol (MSDP) [b-IETF RFC 3618], etc. +- **Static route:** It is required that vBNG support configuration of static routes to specific destinations defined by network prefix. +- **MPLS protocol:** It is required that vBNG support the MPLS protocol [b-IETF RFC 4364]. +- **Tunnelling protocol:** It is required that vBNG support a tunnelling protocol in order to encapsulate frames with tunnel header, recognize and utilizes tunnel header information for forwarding, filtering and other functions, such as generic routing encapsulation (GRE), layer 2 tunnelling protocol (L2TP), L2 VPN and L3 VPN. + +NOTE – VPN is a kind of tunnelling technology, including L2 VPN and L3 VPN services specifically, which include at least: VPLS, VLL, L2TP, MPLS VPN, multicast virtual private network (MVPN), IPv6 VPN provider edge (6VPE), virtual extensible local area network (VxLAN). + +- **SR protocol:** It is required that vBNG support segment routing (SR) services to realize packet fast forwarding by encapsulation of segment labels such as node segment, prefix segment and adjacent segment in packet. The service includes MPLS-based SR and IPv6-based SR [b-IETF RFC 8402] [b-IETF RFC 8663] [b-IETF RFC 8754]. +- **Policy-based routing:** It is required that vBNG support policy-based routing functions to control packet forwarding, including ACL and BGP-flow specification (BGP-FS). +- **MTU:** It is required that vBNG support limitation of the maximum frame size allowed through the ports. +- **QoS:** It is required that vBNG support QoS functions for grantee network and service demands, such as traffic classification, bandwidth guarantee, queue scheduling, congestion control and HQoS. +- **Port aggregation:** It is required that vBNG support a port aggregation function by logically using multiple independent links as a single link to achieve flexible high bandwidth and link redundancy. + +- **Jumbo frame:** It is required that vBNG support jumbo frames to improve network throughput and efficiency. +- **Anti-DoS/DDoS:** It is required that vBNG support traffic restrictions and filtering for specific protocols (such as TCP, UDP and ICMP) to prevent DoS/DDoS attacks. +- **URPF:** It is required that vBNG support URPF to prevent network attacks based on source address spoofing. + +## 8.3 IOPT requirements between vBNG and management system + +The IOPT requirements between vBNG and management system include at least the following aspects, + +- **AAA:** It is required that vBNG support AAA functions. + +NOTE 1 – The authentication function refers to user identity verification, such as the remote authentication dial-in user service (RADIUS) protocol [b-IETF RFC 2865]. vBNG should support at least the password authentication protocol (PAP) and challenge handshake authentication protocol (CHAP) algorithms. + +NOTE 2 – The authorization is used to grant user specific permissions and provide relevant network service according to service demand, and is usually based on authentication results. + +NOTE 3 – The accounting function is used to record the user's usage of various network services and provide the results to the billing system. vBNG should support multiple billing methods, including billing based on time and traffic. + +- **DHCP:** It is required that vBNG support the dynamic host configuration protocol (DHCP) relay function. vBNG acts as DHCP relay, and interacts with a DHCP server to allocate addresses [b-IETF RFC 2131]. + +- **SNMP:** It is required that vBNG support a simple network management protocol (SNMP) function to manage network devices, including at least inspection of device information, modification of device parameter values, monitoring device status, automatic discovery of network faults and report generation. + +- **Flow sampling:** It is required that vBNG support a flow-sampling function to monitor the traffic status. + +- **Port mirror:** It is required that vBNG support a port mirror function to realize fault location, traffic analysis and traffic backup. + +- **Alarm:** It is required that vBNG support an alarm function to report device and service fault information. + +NOTE 4 – Faults are due to multiple causes, such as equipment failure, network connection failure and the exhaustion of a network resource. + +- **Telemetry:** It is required that vBNG support a telemetry function to collect device and service information, including interface traffic, CPU utilization and bandwidth utilization, and upload it to a collection platform. + +- **Virtualized resource management:** It is required that vBNG support virtualized resource management functions by a MANO system, including VNF orchestration based on VNF allocation on demand, lifecycle management of VNF, virtualization infrastructure management by virtual resource allocation, such as virtual computing, virtual storage and virtual network. + +NOTE 5 – Virtualized resource management also includes the flexible expansion and contraction function of VNFs in vBNG. For example, the vBNG expands the user management VNF to meet service needs when the number of access users is too large. + +- **Basic device configuration:** It is required that vBNG support basic device configuration through a management system, such as IP address configuration of the interface. + +- **Service configuration:** It is required that the vBNG support service configuration through a management system to realize service function, such as L2 VPN and L3 VPN service. + +# Appendix I + +## Typical use cases of vBNG + +(This appendix does not form an integral part of this Recommendation.) + +This appendix identifies use cases of vBNG. Table I.1 shows the template used for the description of the use cases. + +**Table I.1 – Template for the description of a use case** + +| Use case | | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Title of the use case. | +| Abstract | Overview and features of the use case. | +| Description and illustration | Description of the use case and illustration to represent it.
(A unified modelling language-like diagram is suggested to clarify relations between roles.) | +| Pre-conditions (optional) | Pre-conditions represent the necessary conditions or use cases that should be achieved before starting the described use case.
NOTE – As dependency may exist among different use cases, pre-conditions and post-conditions are introduced to help understand the relationships among use cases. | +| Post-conditions (optional) | Post-conditions describe conditions or use cases that are carried out after the termination of a currently described use case. | +| Requirements | The title of requirements derived from the use case. | + +### I.1 PPPoE access use case + +Table I.2 describes a PPPoE access use case. + +**Table I.2 – PPPoE access use case** + +| Use case | | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | PPPoE access service | +| Abstract | vBNG interacts with CPE/vCPE to provide PPPoE access service to end user for Internet connection | +| Description and illustration |

Image: Sequence diagram of PPPoE access process showing four steps: Step 1: PPPoE Active Discovery (PADI, PADO, PADR, PADS); Step 2: Link Establishment (Configuration-Req, Configuration-Ack); Step 3: Authentication (Challenge, Response, Success); Step 4: Address assignment (IP address request, IP address assign). Lifelines: CPE/vCPE, vBNG, Management system (AAA, DHCP server).

The diagram illustrates the PPPoE access process between a CPE/vCPE and a vBNG, involving a Management system (AAA and DHCP server). The process is divided into four steps:

  • Step 1: PPPoE Active Discovery: The CPE/vCPE sends a PADI (PPPoE Active Discovery Initiation) to the vBNG. The vBNG responds with PADO (PPPoE Active Discovery Offer). The CPE/vCPE then sends a PADR (PPPoE Active Discovery Request) to the vBNG, which responds with PADS (PPPoE Active Discovery Session-Assignment).
  • Step 2: Link Establishment: The CPE/vCPE sends a Configuration-Req to the vBNG, which responds with a Configuration-Ack.
  • Step 3: Authentication: The vBNG sends a Challenge to the CPE/vCPE. The CPE/vCPE responds with a Response. The vBNG then sends a Response to the AAA server, which responds with a Success. The vBNG then sends a Success to the CPE/vCPE.
  • Step 4: Address assignment: The CPE/vCPE sends an IP address request to the vBNG. The vBNG sends an IP address assign to the CPE/vCPE.

Q.4064(20)_FI.1

| + +**Figure I.1 – PPPoE access process** + +**Table I.2 – PPPoE access use case** + +| Use case | | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

The PPPoE access process can be divided into discovery and session phases.

1) Discovery phase
vBNG establishes a PPPoE connection with CPE/vCPE and assigns a session ID to the user. In Figure I.1, the discovery phase is step 1.

2) Session phase
The session phase includes three parts: link control protocol (LCP); authentication; and network control protocol (NCP) negotiation, corresponding to steps 2-4 in Figure I.1.

a) Step 2: The LCP stage establishes a link connection. CPE/vCPE and vBNG establish a PPP connection and then negotiate LCP configuration parameters. Only after successful LCP negotiation, will the process come to the authentication or NCP stage, it is usually an Internet protocol control protocol (IPCP) negotiation.

b) Step 3: The authentication stage is not necessary in the PPPoE protocol. However, for network security and user management, it is necessary that service providers do it. Authentication of vBNG is usually done in two ways: locally and remotely through an AAA system (such as a RADIUS server). In local authentication, the interaction is only between vBNG and CPE/vCPE. In remote authentication, which is based on an AAA system, the interaction of this function involves CPE/vCPE, vBNG and AAA system entities. Take RADIUS authentication for example, vBNG acts as authentication agent, converses and transmits the PPPoE authentication packet from CPE/vCPE, and the RADIUS packet from the RADIUS server. In addition, authentication algorithms mainly include PAP and CHAP etc. Only once the authentication succeeds can the IPCP negotiation phase start, otherwise PPPoE access fails.

c) Step 4: The IPCP stage assigns an IP address. CPE/vCPE and vBNG negotiate the IP address and DNS information for the user through a PPPoE configuration packet. The address allocation mode can be done in two ways: by vBNG or by DHCP server. For address management purposes, service providers often choose the second method. After this stage, vBNG configures the network interface and sync user forwarding table, thus the user can access the Internet.

NOTE – From the logical aspect, AAA and DHCP server functions lie within the management system scope. vBNG acts as a proxy to forward user access packets to the AAA and DHCP client.

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Requirements |

The IOPT requirements between CPE/vCPE and vBNG include at least:

  • – PPPoE (see clause 8.1)
  • – NAT (see clause 8.1)
  • – QoS (see clause 8.1)
  • – VLAN (see clause 8.1)
  • – QinQ (see clause 8.1)
  • – VAS (see clause 8.1)
  • – ACL (see clause 8.1)
  • – ARP (see clause 8.1)
  • – DNS (see clause 8.1)
  • – Access redirection (see clause 8.1)
| + +**Table I.2 – PPPoE access use case** + +| Use case | | +|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
  • – MTU (see clause 8.1)
  • – Port aggregation (see clause 8.1)
  • – Jumbo frame (see clause 8.1)
  • – Anti-DoS/DDoS (see clause 8.1)
  • – URPF (see clause 8.1)

The IOPT requirements between vBNG and management system include at least:

  • – AAA (see clause 8.3)
  • – DHCP (see clause 8.3)
| + +### **I.2 IPoE access use case** + +**Table I.3 – IPoE access use case** + +| Use case | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | IPoE access service | +| Abstract | vBNG interacts with CPE/vCPE to provide IPoE access service to end user for Internet connection. | +| Description and illustration |

The main purpose of IPoE access service is to obtain an IP address for the user to connect to the Internet. IPoE access service mainly includes IPoE user access, authentication and address allocation functions. IPoE access process comprises four steps:

  1. 1) user identification and authentication initiation;
  2. 2) identity authentication;
  3. 3) address allocation;
  4. 4) accounting.

For 3), the DHCP dynamic address allocation method is used to allocate an address, and the IP address is released through the DHCP release protocol. The DHCP address allocation process includes the following four principal steps:

  1. 1) DHCP discovery;
  2. 2) DHCP offer;
  3. 3) DHCP request;
  4. 4) DHCP ACK (acknowledgement).

See Figure I.2.

| + +![Sequence diagram of the IPoE access process showing interactions between CPE/vCPE, vBNG, AAA, and DHCP server. The process is divided into four steps: 1) User identification and authentication initiation, 2) Identity authentication, 3) Address allocation, and 4) Accounting. The diagram uses color-coded background blocks for each step: grey for Step 1, blue for Step 2, yellow for Step 3, and green for Step 4. Arrows indicate the flow of messages: DHCP discovery, Access-request, Access-reject, Access-accept, DHCP relay, DHCP offer, DHCP request, DHCPACK, Accounting-start, and Accounting-response.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Q.4064(20)\_FI.2 + +Sequence diagram of the IPoE access process showing interactions between CPE/vCPE, vBNG, AAA, and DHCP server. The process is divided into four steps: 1) User identification and authentication initiation, 2) Identity authentication, 3) Address allocation, and 4) Accounting. The diagram uses color-coded background blocks for each step: grey for Step 1, blue for Step 2, yellow for Step 3, and green for Step 4. Arrows indicate the flow of messages: DHCP discovery, Access-request, Access-reject, Access-accept, DHCP relay, DHCP offer, DHCP request, DHCPACK, Accounting-start, and Accounting-response. + +**Figure I.2 – IPoE access process** + +The signalling interaction process of IPoE access service can be described as follows. + +#### 1) Step 1: user identification and authentication initiation + +- a) User terminals or CPE initiate DHCP requests with the corresponding option 60 information (it usually uses a fixed media access control (MAC) address as username to initiate requests). +- b) Intermediate network devices label option 82 information according to relevant specifications. +- c) On receipt of a user request message, vBNG extracts the MAC address, option 60, option 82 information, and forms a username format: MAC@Option 60. It also converts option 82 information into network access server port identifier (NAS-Port-ID) information and sends it to RADIUS authentication. + +NOTE – Option 82 and option 60 are both DHCP options. Option 82, which is specified in [b-IETF RFC 3046], is a relay agent information option to identify user location by carrying relay agent information in the packet. Option 60, which is specified in [b-IETF RFC 2132] is used to report manufacturer and configuration information of a terminal. + +#### 2) Step 2: identity authentication + +The RADIUS server returns a rejection message if authentication fails and vBNG terminates the user session. + +If authentication succeeds, vBNG sends back the authenticated information with the relevant service policy attributes of the user. + +#### 3) Step 3: address allocation + +- a) vBNG relays DHCP requests to the DHCP server for address allocation. +- b) DHCP server assigns corresponding addresses to users according to different service information. +- c) vBNG gets the user address and sends DHCP ACK information to the end user or CPE, and the user can surf the Internet. + +#### 4) Step 4: accounting + +- a) vBNG sends an accounting start message to the AAA system. +- b) AAA system completes the relevant processing and sends a response message to vBNG. + +**Table I.3 – IPoE access use case** + +| Use case | | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Requirements |

The IOPT requirements between CPE/vCPE and vBNG include at least:

  • – IPoE (see clause 8.1)
  • – NAT (see clause 8.1)
  • – QoS (see clause 8.1)
  • – VLAN (see clause 8.1)
  • – QinQ (see clause 8.1)
  • – VAS (see clause 8.1)
  • – ACL (see clause 8.1)
  • – ARP (see clause 8.1)
  • – DNS (see clause 8.1)
  • – Access redirection (see clause 8.1)
  • – MTU (see clause 8.1)
  • – Port aggregation (see clause 8.1)
  • – Jumbo frame (see clause 8.1)
  • – Anti-DoS/DDoS (see clause 8.1)
  • – URPF (see clause 8.1)

The IOPT requirements between vBNG and management system include at least:

  • – AAA (see clause 8.3)
  • – DHCP (see clause 8.3)
| + +### I.3 VPN service use case + +**Table I.4 – VPN service use case** + +| Use case | | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | VPN service | +| Abstract | vBNG interacts with BNG/vBNG/PE to provide private communication over a public network for VPN service. | +| Description and illustration |

VPN service consists of different types as described in clause 8.2, the realization principle of different VPN services also varies, but the idea is similar. In this clause, the MPLS VPN use case is taken as an example to make the description.

MPLS VPN is the use of MPLS technology in the backbone of a broadband IP network to build an IP private network especially for enterprises, so as to achieve cross-regional, secure, high-speed, reliable communication for data, voice, image and video.

See Figure I.3.

| + +**Table I.4 – VPN service use case** + +| Use case | | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Figure I.3 – MPLS VPN service topology diagram showing multiple VPN instances (VPN A, VPN B) connected to Customer Edge (CE) devices, which are in turn connected to various routers (R, vBNG, BNG, PE) within a central cloud representing the MPLS network. iBGP sessions are shown between the routers.

Q.4064(20)_FI.3

| +| |

Figure I.3 – MPLS VPN service topology

VPN services are provided by vBNG and vBNG/BNG/PE. The process of VPN service is shown in Figure I.4.

Figure I.4 – VPN service process diagram showing three steps: Step 1: Routing protocol, Step 2: Tunnel establish, and Step 3: Traffic forwarding between a vBNG and a BNG/vBNG/PE.

Q.4064(20)_FI.4

| +| |

Figure I.4 – VPN service process

  • – Step 1: vBNG runs a routing protocol with BNG/vBNG/PE to establish an L3 network connection.
  • – Step 2: vBNG and BNG/vBNG/PE establish a tunnel connection through a VPN instance.
  • – Step 3: vBNG imports user traffic into the VPN tunnel. Users cannot feel the existence of public networks, just as they have independent network resources.

NOTE – VPN service can be realized with QoS and traffic engineering (TE)

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Requirements |

The IOPT requirements of a VPN service include the interaction between vBNG and BNG/vBNG/PE. The requirements are as follows.
Requirements between vBNG and BNG/vBNG/PE include at least:

  • – IGP routing protocols (see clause 8.2)
  • – BGP routing protocol (see clause 8.2)
  • – Static route (see clause 8.2)
  • – MPLS protocol (see clause 8.2)
| + +**Table I.4 – VPN service use case** + +| Use case | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
  • – Tunnelling Protocol (see clause 8.2)
  • – Policy-based routing (see clause 8.2)
  • – MTU (see clause 8.2)
  • – QoS (see clause 8.2)
  • – Port aggregation (see clause 8.2)
  • – Jumbo frame (see clause 8.2)
  • – Anti-DoS/DDoS (see clause 8.2)
  • – URPF (see clause 8.2)
| + +### **I.4 Multicast service use case** + +**Table I.5 – Multicast service use case** + +| Use case | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Multicast service use case | +| Abstract | vBNG interacts with CPE/vCPE to provide a multicast service to the end user. | +| Description and illustration |

Multicast service is efficient data transmission from point to multi-point based on a multicast group management protocol (e.g., IGMP) and multicast routing protocol (e.g., PIM).

A multicast service uses a multicast routing protocol to transfer information in a WAN and a multicast group management protocol to manage the multicast group. The typical multicast model is shown in Figure I.5, it consists of a user, vBNG and IP backbone network.

Image: Diagram of the multicast service model. On the left, four hosts (Host A, B, C, D) are connected to a central vBNG (R). IGMP messages are shown between the hosts and the vBNG. The vBNG is connected to a central CR (R), which is part of an IP backbone cloud. The CR is connected to another CR (R), which is connected to a Source. A third vBNG (R) is also connected to the central CR. The diagram is labeled Q.4064(20)_FI.5.

Figure I.5 – Multicast service model

Multicast service is provided by CPE/vCPE, vBNG and vBNG/BNG/PE, the process of multicast service is as shown in Figure I.6.

| + +**Table I.5 – Multicast service use case** + +| Use case | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------|-----------------------|--------|---------------------------------|--|--------|--------------------------------|--|--------| +| |
CPE/vCPE
CPE/vCPE icon
vBNG
vBNG icon
BNG/vBNG/PE
BNG/vBNG/PE icon
Step 1 ↔ Multicast group management ↔ ↔ Multicast routing ↔
Step 2 ↔ Multicast distribution tree ↔
Step 3 ← Multicast traffic forwarding Source

Q.4064(20)_FI.6

Figure I.6 – Multicast service process

  1. 1) Step 1: vBNG runs a multicast group management protocol to establish a multicast user connection by CPE/vCPE, and manages the multicast group. vBNG runs a multicast routing protocol between vBNG and BNG/vBNG/PE to realize multicast routing and forwarding.
  2. 2) Step 2: vBNG establishes the multicast routing table based on the multicast distribution tree.
  3. 3) Step 3: vBNG can replicate and forward multicast traffic to users through CPE/vCPE.

NOTE 1 – Multicast VPN should be supported.
NOTE 2 – L2 multicast should be supported.

| CPE/vCPE
CPE/vCPE icon | vBNG
vBNG icon | BNG/vBNG/PE
BNG/vBNG/PE icon | Step 1 | ↔ Multicast group management ↔ | ↔ Multicast routing ↔ | Step 2 | ↔ Multicast distribution tree ↔ | | Step 3 | ← Multicast traffic forwarding | | Source | +| CPE/vCPE
CPE/vCPE icon | vBNG
vBNG icon | BNG/vBNG/PE
BNG/vBNG/PE icon | | | | | | | | | | | | | +| Step 1 | ↔ Multicast group management ↔ | ↔ Multicast routing ↔ | | | | | | | | | | | | | +| Step 2 | ↔ Multicast distribution tree ↔ | | | | | | | | | | | | | | +| Step 3 | ← Multicast traffic forwarding | | Source | | | | | | | | | | | | +| Pre-conditions (optional) | User already accesses the Internet through PPPoE or IPoE. | | | | | | | | | | | | | | +| Post-conditions (optional) | | | | | | | | | | | | | | | +| Requirements |

The IOPT requirements of multicast service include interactions between: vBNG and BNG/vBNG/PE; and CPE/vCPE and vBNG.

The IOPT requirements between vBNG and BNG/vBNG/PE include at least:

  • – IGP routing protocols (see clause 8.2)
  • – BGP routing protocol (see clause 8.2)
  • – Multicast routing protocols (see clause 8.2)
  • – Policy based routing (see clause 8.2)
  • – MTU (see clause 8.2)
  • – QoS (see clause 8.2)
  • – Port aggregation (see clause 8.2)
  • – Jumbo frame (see clause 8.2)
  • – Anti-DoS/DDoS (see clause 8.2)
  • – URPF (see clause 8.2)

The IOPT requirements between vBNG and CPE/vCPE include at least:

  • – Multicast group management protocol (see clause 8.1)
  • – NAT (see clause 8.1)
  • – QoS (see clause 8.1)
  • – VLAN (see clause 8.1)
  • – QinQ (see clause 8.1)
  • – VAS (see clause 8.1)
| | | | | | | | | | | | | | + + + +**Table I.6 – SR use case** + +| Use case | | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

Image: Diagram of SR service process showing three steps between vBNG and BNG/vBNG/PE. Step 1: Routing protocol, Step 2: SR protocol, Step 3: Traffic forwarding. Source: Q.4064(20)_FI.8

Figure I.8 – SR service process

  • – Step 1: vBNG and BNG/vBNG/PE run an IGP protocol to establish an L3 network connection.
  • – Step 2: vBNG and BNG/vBNG/PE run an SR protocol; usually MPLS protocol is needed as basic. The SID is distributed by the controller or IGP protocol. Based on the routing table and SID, vBNG establishes the SR label forwarding table.
  • – Step 3: vBNG and BNG/vBNG/PE forward SR traffic.

NOTE – Segment routing-traffic engineering (SR-TE) controls the service path by labelling the path in the packet at the head node. The intermediate nodes do not need to retain the path information.

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Requirements |

The IOPT requirements of SR service are mainly the interaction between vBNG and BNG/vBNG/PE.

The IOPT requirements between vBNG and BNG/vBNG/PE include at least:

  • – IGP routing protocols (see clause 8.2)
  • – BGP routing protocol (see clause 8.2)
  • – Static route (see clause 8.2)
  • – SR protocol (see clause 8.2)
  • – Policy based routing (see clause 8.2)
  • – MTU (see clause 8.2)
  • – QoS (see clause 8.2)
  • – Port aggregation (see clause 8.2)
  • – Jumbo frame (see clause 8.2)
  • – Anti-DoS/DDoS (see clause 8.2)
  • – URPF (see clause 8.2)
| + +## **I.6 Network management use case** + +**Table I.7 – Network management use case** + +| Use case | | +|-------------|-----------------------------| +| Name | Network management use case | + +**Table I.7 – Network management use case** + +| Use case | | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Abstract | vBNG interacts with a management system to support its fault management, configuration management, performance management, security management and billing management functions. | +| Description and illustration |

Network management includes the management of network equipment hardware, software and network services in order to monitor, test, configure, analyse, evaluate and control network resources, so that network operation status and service quality can be grasped in real time. When there is a network failure, operators can deal with it in time, so as to ensure the stable operation of the network system.

vBNG interacts with management system to realize management functions as shown in Figure I.9.

Diagram showing the interaction between vBNG and a Management system for five network management functions: Configuration management, Performance management, Fault management, Security management, and Billing management. Each function is represented by a horizontal double-headed arrow between the two entities, set against a colored background band.

Q.4064(20)_FI.9

Figure I.9 – Network management functions

| +| Pre-conditions (optional) | | +| Post-conditions (optional) | | +| Requirements |

The IOPT requirements of network management mainly refer to the interaction between vBNG and the management system.

The IOPT requirements between vBNG and management system include at least:

  • – AAA (see clause 8.3)
  • – DHCP (see clause 8.3)
  • – SNMP (see clause 8.3)
  • – Flow sampling (see clause 8.3)
  • – Port mirror (see clause 8.3)
  • – Telemetry (see clause 8.3)
  • – Virtualized resource management (see clause 8.3)
  • – Basic device configuration (see clause 8.3)
  • – Service configuration (see clause 8.3)
| + +# Bibliography + +- [b-ITU-T Y.3502] Recommendation ITU-T Y.3502 (2014), *Information technology – Cloud computing – Reference architecture.* +- [b-IEEE 802.1Q] IEEE 802.1Q-2018, *IEEE Standard for local and metropolitan area networks – Virtual bridged local area networks.* +- [b-IETF RFC 1142] IETF RFC 1142 (1990), *OSI IS-IS intra-domain routing protocol.* +- [b-IETF RFC 2131] IETF RFC 2131 (1997), *Dynamic host configuration protocol.* +- [b-IETF RFC 2132] IETF RFC 2132 (1997), *DHCP options and BOOTP vendor extensions.* +- [b-IETF RFC 2328] IETF RFC 2328 (1998), *OSPF version 2.* +- [b-IETF RFC 2516] IETF RFC 2516 (1999), *A method for transmitting PPP over Ethernet (PPPoE).* +- [b-IETF RFC 2865] IETF RFC 2865 (2000), *Remote authentication dial in user service (RADIUS).* +- [b-IETF RFC 3046] IETF RFC 3046 (2001), *DHCP relay agent information option.* +- [b-IETF RFC 3376] IETF RFC 3376 (2002), *Internet group management protocol, version 3.* +- [b-IETF RFC 3618] IETF RFC 3618 (2003), *Multicast source discovery protocol (MSDP).* +- [b-IETF RFC 3810] IETF RFC 3810 (2004), *Multicast listener discovery version 2 (MLDv2) for IPv6.* +- [b-IETF RFC 3973] IETF RFC 3973 (2005), *Protocol independent multicast-dense mode (PIM-DM): Protocol specification (revised).* +- [b-IETF RFC 4273] IETF RFC 4273 (2006), *Definitions of managed objects for BGP-4.* +- [b-IETF RFC 4364] IETF RFC 4364 (2006), *BGP/MPLS IP virtual private networks (VPNs).* +- [b-IETF RFC 7761] IETF RFC 7761 (2016), *Protocol independent multicast-sparse mode (PIM-SM): Protocol specification (Revised).* +- [b-IETF RFC 8402] IETF RFC 8402 (2018), *Segment routing architecture.* +- [b-IETF RFC 8663] IETF RFC 8663 (2019), *MPLS segment routing over IP.* +- [b-IETF RFC 8754] IETF RFC 8754 (2020), *IPv6 segment routing header (SRH).* + + + + + +## 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.4068-202108-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c395c4bbde83b1e232652a43f51538278c116f51f710c37e20a073f7333726c8 +size 6134 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79e7e92ac4bf4c83f24b56a75a9029bb88ee76b4 --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:290cdeed38a1e4ddee60077a66c624d0d072f3ebe48163ca4c7b16a9820adc48 +size 158473 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5738294aa34aacbb1107e26cc6814483ac361ff3 --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b5f8ccf96a87c13b597a92943f43093f3ab23bf3dafbe66d7a3251884fd26ea +size 26388 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ad3e552201ef6a0d21674b884031e45d8c99d7a --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c345cd11087f9211f464b65745faf02f8ee2d3eddfbf6e91b488b0720ae560cd +size 177697 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d437d491a9fc8aeb2c7d4b82ad9dc4beadcffa8d --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b007d79d923bf7ce0f3bcd960324c7d864dc29993eaded52a699062f92876d9 +size 81418 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0db87fc3ec421cfa518bb7119c137252d8e9b441 --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4313c77746c4590b7d12b5733fb1a9e6e7064b86cf2a00441d2a82b22fd32890 +size 56552 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1117485e8649895ca806fdc232eb261ccdbcefba --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5c0aee77a1302786084a594d27bb1fae6809d8aff5bf62244a5e197dca1900a +size 128147 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e128bdad31f595a0a58d1fd86beceddc57c7fd8e --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a333f630aa43a03dc95424f9cb5e92b99329f6ab0893829f5e625f0067ac65b3 +size 12319 diff --git a/marked/Q/T-REC-Q.4068-202108-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d900d57cf4b581f47e9ff90c9ad6ebbbfa75e6ed --- /dev/null +++ b/marked/Q/T-REC-Q.4068-202108-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f6a2bec118ecd0ea68c898128667c7b1ea189f8b0221c9cdabdea173a50b114 +size 128859 diff --git a/marked/Q/T-REC-Q.4078-202504-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4078-202504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9748a60e7b3711baffd9a62cb3d1a567b487288a --- /dev/null +++ b/marked/Q/T-REC-Q.4078-202504-I_PDF-E/raw.md @@ -0,0 +1,282 @@ + + +# Recommendation + +## **ITU-T Q.4078 (04/2025)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Testing specifications – Testing specifications for IMT-2020 and IoT + +--- + +## **User requirements and reference model for testbed as a service** + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like grid 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 | +| 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 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T Q.4078 + +## User requirements and reference model for testbed as a service + +## Summary + +Recommendation ITU-T Q.4078 elaborates on requirements and reference model, with properties of relevance for delivering testbed as a service (TaaS) in the context of federated testbeds, aiming to complement and extend Recommendation ITU-T Q.4068. It is more particularly focused on the user interface, services, and requirements to address end-user needs when remotely accessing testbeds in order to deliver an adequate user experience. From this point, this Recommendation is reporting the elaboration of the related terms and definitions, requirements, reference model with properties of relevance for TaaS, and interoperability specifications for virtualizing and delivering modular and scalable TaaS on top of existing and future testbed infrastructures, including federated ones. Furthermore, the TaaS will be able to list the assets provided by the different testbeds and expose them through dedicated application programming interfaces (APIs) based on Recommendation ITU-T Q.4068. Generic key performance indicators (KPIs) are defined in a generic manner in the corresponding Recommendation; for instance, the exposure of capabilities is a generic KPI, so agnostic from the TaaS, and is common to all the parts of a testbed federation. Some KPIs concerning specially the TaaS are determined in this Recommendation such as dynamic discovery, availability and reputation based on a scoring of each testbed. Integration, interoperability and extensibility of the TaaS are also defined. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4078 | 2025-04-13 | 11 | 11.1002/1000/16294 | + +## Keywords + +Reference model, requirements, testbed as a service (TaaS), testbed federation. + +--- + +\* 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 User requirements and reference model for testbed as a service..... | 2 | +| Bibliography..... | 5 | + + + +### Recommendation ITU-T Q.4078 + +### User requirements and reference model for testbed as a service + +## 1 Scope + +This Recommendation defines the specific user requirements and reference model for testbed as a service (TaaS). It also describes the interconnection of testbeds through the testbed management system and considers other aspects like business, policies and monetization. + +## 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.4068](#)] Recommendation ITU-T Q.4068 (2021), *Open application program interfaces (APIs) for interoperable testbed federations*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 experiment** [b-ISO 3534-3]: Purposive investigation of a system through selective adjustment of controllable conditions and allocation of resources. + +**3.1.2 resource** [b-ITU-R BT.1699]: A network data object or a service which is uniquely identified in a network. – A well-defined capability or asset of a system entity, which can be used to contribute to the realization of a service. Examples: MPEG decoder, graphics system. + +**3.1.3 testbed** [ITU-T Q.4068]: Platform to realise scientific tests with new technologies on an environment fully controlled by experimenters. + +**3.1.4 testbed as a service** [b-ITU-T QSTR.FTT]: Refers to the offering of a testbed by its owner to users based on a defined policy framework. This framework may include service level agreements (SLAs), pricing models, usage time frames, and testbed availability. Users can access the testbed to run tests, analyze results, and utilize the findings while adhering to the established policies. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------| +| AI | Artificial Intelligence | +| API | Application Programming Interface | +| CPU | Central Processing Unit | +| FTTH | Fiber to the Home | + +| | | +|------|-------------------------------------| +| GDPR | General Data Protection Regulation | +| GUI | Graphical User Interface | +| IoT | Internet of Things | +| KPI | Key Performance Indicator | +| ML | Machine Learning | +| QoS | Quality of Service | +| RAM | Random-Access Memory | +| SDN | Software-Defined Networking | +| TaaS | Testbed as a Service | +| xDSL | Any type of Digital Subscriber Line | + +## 5 Conventions + +None. + +## 6 User requirements and reference model for testbed as a service + +There are two types of users to be involved in the testbed as a service (TaaS): + +1. The experimenters or researchers, simply called users throughout this Recommendation; +2. The testbed providers which are responsible for the implementation and the maintenance of the TaaS. + +There are the following functional requirements pertaining to the TaaS users' needs: + +- Resource discovery: The users should be able to discover the specific resources for all available federated testbeds. +- Resource provisioning: Mechanisms for provisioning resources by the users should be implemented, including the access and the orchestration of resources. +- Resource configuration: The users should be able to configure the resource by changing the value or range of values of one or several parameters before an experiment. +- Resource description: An understandable description of each resource should be provided to the users. +- Resource reservation: Users should be able to reserve the resources in different modes such as a scheduled reservation or on-demand. +- Experiment control and orchestration: The users should be able to control various parameters during the execution of an experiment. The users should be able to manage the full lifecycle of their experiments through a dashboard. +- Authentication: The users should authenticate themselves to access the TaaS. +- Authorization: The users should receive authorization to use the resources provided by the testbeds. +- Monitoring, results gathering and reporting: The users should be able to track which parameters should be monitored during an experiment and to collect the results of the experiment, including generation of an experiment's report. +- Interconnection of testbeds: The users should be able to select resources distributed among several testbeds. +- User interface: The users should be able to manage their experiments through a graphical user interface (GUI). + +- Remote access: The users should be able to access the TaaS remotely. +- Data analytics tools: The users should be able to use data analytics tools offered by the TaaS. +- Experiment discovery and selection: The users should be able to find and use past experiments. A clear description of an experiment and related test suites are also required as prerequisite. +- Experiment storage: The users should be able to store finished experiments and their results in order to execute them again later, if needed. +- Automated experiment scheduling: The users should have the ability to automate the scheduling of experiments based on predefined criteria, such as recurring tests or experiments triggered by external events (e.g., data threshold reached, network status change). +- Notifications and alerts: The users should be able to set up custom notifications or alerts for certain conditions (e.g., experiment status changes, resource availability, or experiment completion). + +The functional requirements concerning the testbed providers are: + +- Resource description, catalogue provisioning: The testbed providers should describe and list their testbeds in their catalogue, including the available resources and their capabilities. A common description/advertisement scheme should be applied for all the resources of all the testbeds available under publish/subscribe model. +- Resource identification: The resources should be clearly identified by unique identifiers used across all the testbeds. +- Resource reservation: The testbed providers should continuously update the information related to the status of the reservation of their resources. +- Resource provisioning: The testbed providers should operate provisioning systems and expose them through open APIs/interfaces to the rest of the testbed federation. +- Experiment control: The testbeds should be able to work with tools used to control the experiments. +- Management of testbeds: A testbed management system should be owned by the testbed providers. A testbed provider can change the policies of the testbed management system. Network programmability and software-defined networking (SDN) solutions could be envisioned to control in fine-grained manner the interworking aspects between the testbeds. +- Documentation: The testbed providers should make the TaaS manual publicly available. It should be updated on a regular basis. +- Consumption of the service: The testbed providers should provide a usage and billing services which inform the users about the utilisation of the TaaS. This service should also handle the invoices to be addressed to the users. +- Scalability: The testbed providers should ensure the scalability of the TaaS, allowing the execution of experiments to scale based on needs. +- High availability: The testbeds should be designed with high availability, minimizing downtime and ensuring continuous service availability. +- Access control: The system should support different user roles (e.g., administrator, researcher, testbed provider) with specific access control policies, ensuring that users can access only the resources and features they are authorized to use. +- Artificial intelligence (AI) / machine learning (ML) integration: The TaaS should support AI/ML models to optimize resource allocation and experiment configuration, as well as help predict potential issues in experiments based on historical data. + +The non-functional requirements are listed below: + +- User-friendliness: The users should utilise the TaaS GUI according to the guidelines and the best practices in terms of user-friendliness. +- Security and confidentiality: The TaaS should comply with relevant standards in this area, the best practices about security and the applicable regulation for data protection, such as the general data protection regulation (GDPR) and other data protection regulations. An approach following the security and privacy by design principles is recommended (e.g., the critical data shall be encrypted). +- Visualization: The users should be able to see real-time information during the execution of an experiment. After the completion of an experiment, they should be able to have access to the results and the logs for further analysis and other purposes (e.g., downloading results). The formats of the results should be generic enough in order to be customised for various purposes. +- Latency optimization: TaaS should minimize latency between testbed resources and experimenters' actions, especially for real-time or time-sensitive experiments, by optimizing data transfer, resource allocation, and orchestration mechanisms. + +For the TaaS, there are the following key performance indicators (KPIs): + +- Dynamic discovery: The discovery of all the resources provided by all the testbeds is realized dynamically and all the discovered resources are displayed in the TaaS GUI in real time. It will permit to evaluate the number of resources provided by the testbeds. +- Availability: The availability of the testbeds and their resources are also shown in the TaaS GUI. It will allow the detection of problems per testbed, notably network disconnections. This KPI can be used to improve the quality of service (QoS). +- Reputation based on testbed rating: The broker is maintaining and updating the rating of each testbed. In the same manner, the collection of the information provided by the users is done in order to rate each testbed. +- Number of open user sessions (active or idle): This KPI permits to know how many users are currently using the TaaS. +- Resource utilization efficiency: This KPI tracks the efficiency of resource utilization in the testbed, providing insights into over-provisioning or under-utilization of resources, which could drive cost reduction and better planning. + +In the context of the TaaS, a conformity assessment of testbeds should be based on some criteria such as data protection, security, audit of the components, specifications and standards including those defined in [ITU-T Q.4068]. A test tool offered by the TaaS can be used to assess whether reserved resources are in conformity with the regulation or not (e.g., data processed in different locations/countries, insufficient central processing unit (CPU) / random-access memory (RAM) or detected congestions), which can be used as evidence in reconciliations before trials on the implications of third-party testing. + +A tool can be declared compliant to carry out tests, for example diagnostic tests, by all the actors agreeing or having the tools recommended/prescribed by a regulator to the different stakeholders such as operators, regulators themselves, auditors, test manufacturers. An important point is to know if the tests are to be carried out and on which specification releases (4G, 5G, 6G, fibre to the home (FTTH), any type of digital subscriber line (xDSL), cloud, etc.) but also whether they comply with relevant legislations (e.g., related to cloud, AI, data protection like GDPR). + +## Bibliography + +- [b-ITU-T QSTR.FTT] ITU-T Technical Report QSTR.FTT, *Federated testbeds taxonomy* +- [b-ITU-R BT.1699] Recommendation ITU-R BT.1699 (2005), *Harmonization of declarative application formats for interactive TV*. + +- [b-ISO 3534-3] ISO 3534-3:2013, *Statistics – Vocabulary and symbols – Part 3: Design of experiments*. + + + + + + +## 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.4080-202601-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.4080-202601-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bdd7bc1d3581fbdc3cf6b035f618693dbe3846 --- /dev/null +++ b/marked/Q/T-REC-Q.4080-202601-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75efa8e3513a799767c04a0bb7bcd87a550f2378f5880629068581808c1c9f7f +size 7353 diff --git a/marked/Q/T-REC-Q.4080-202601-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.4080-202601-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d7dec604ab7ee9a927db9f0cca2d4b75a30df41 --- /dev/null +++ b/marked/Q/T-REC-Q.4080-202601-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbaf94e9bb93c5f371f04d9e51127d19bfb618b2c7664ababec77ee5b63f5d7e +size 39476 diff --git a/marked/Q/T-REC-Q.4101-202108-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4101-202108-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0163c55146cffbb274be85c67d7820315d7156bd --- /dev/null +++ b/marked/Q/T-REC-Q.4101-202108-I_PDF-E/raw.md @@ -0,0 +1,557 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4101** + +(08/2021) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Protocols and signalling for peer-to-peer communications + +# --- **Hybrid peer-to-peer (P2P) communications: Tree and data recovery procedures** + +Recommendation ITU-T Q.4101 + +## 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.4101 + +# Hybrid peer-to-peer (P2P) communications: Tree and data recovery procedures + +## Summary + +Recommendation ITU-T Q.4101 specifies procedures for the construction and recovery of a hybrid overlay network. The hybrid overlay network constructs a data broadcast tree among peers and calibrates the topology of the overlay network whenever peers are joining or leaving. On calibrating the hybrid overlay network, it needs to be stable even during the reconstruction process. To do this, this Recommendation specifies the procedures for construction and recovery of the tree-based hybrid overlay network, and also specifies the procedures for recovering data that may be lost during the tree recovery procedures. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4101 | 2021-08-29 | 11 | 11.1002/1000/14766 | + +## Keywords + +Data recovery, hybrid peer-to-peer, overlay network, procedures, tree recovery. + +--- + +\* 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 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..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview ..... | 2 | +| 7 Procedures for hybrid overlay network construction and recovery..... | 2 | +| 7.1 Hybrid overlay network construction procedures ..... | 3 | +| 7.2 Hybrid overlay network recovery procedures ..... | 6 | +| 8 Data recovery procedures ..... | 7 | +| 8.1 Configurations on hybrid overlay network caching and recovery policy ..... | 8 | +| 8.2 Data caching and recovery in the hybrid peer ..... | 8 | +| Bibliography..... | 15 | + + + +## Recommendation ITU-T Q.4101 + +# Hybrid peer-to-peer (P2P) communications: Tree and data recovery procedures + +# 1 Scope + +This Recommendation describes the data and tree recovery procedures of a hybrid overlay network as follows: + +- overlay network construction procedures; +- overlay network recovery procedures; +- data recovery 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. + +[ITU-T Q.4100] Recommendation ITU-T Q.4100 (2020), *Hybrid peer-to-peer communications: Functional architecture*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 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.2 peer** [b-ITU-T X.1161]: Communication node on P2P network that functions simultaneously as both "client" and "server" to the other nodes on the network. + +**3.1.3 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.4 hybrid overlay network** [ITU-T Q.4100]: A peer-to-peer overlay network that participating peers exchange data using 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.5 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.1.6 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.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|----------------------------------| +| HOMS | Hybrid Overlay Management Server | +| HON | Hybrid Overlay Network | +| HP2P | Hybrid Peer-to-Peer | +| P2P | Peer-to-Peer | +| TCP | Transmission Control Protocol | +| WebRTC | Web Real-Time Communications | + +# **5 Conventions** + +None. + +# **6 Overview** + +The hybrid overlay network that is specified in [ITU-T Q.4100] maintains a tree-based hybrid overlay network, described in clause 6 of [ITU-T Q.4100], that is used for broadcasting data. Whenever a new hybrid peer joins the overlay network, it needs to be ensured that a loop does not occur within the tree-based overlay network. In order to keep the tree resilient, it needs to reconstruct the tree-based overlay network as soon as possible when any peer leaves the hybrid overlay network. + +[ITU-T Q.4100] classifies the type of the path into a primary path and a candidate path, and the candidate path can be further classified as follows: + +- Incoming candidate path: a candidate path established by a remote hybrid peer. +- Outgoing candidate path: a candidate path established by the hybrid peer itself. + +The tree-based hybrid overlay network (HON) consists of hybrid peers with primary paths. To continue being resilient to any failure of peers within a tree-based hybrid overlay network, the peers in the hybrid overlay network make multiple candidate paths for rapid recovery. If any primary path of a peer fails, the peer immediately switches one of its candidate paths to a primary path. In this switching process, special consideration is also needed to avoid loops in the tree. In addition, it needs to recover data that has been lost during the tree recovery procedures. This Recommendation provides the following procedures for supporting the recovery of tree and data: + +- Hybrid overlay network construction procedures; +- Hybrid overlay network recovery procedures; +- Hybrid overlay network data recovery procedures. + +# **7 Procedures for hybrid overlay network construction and recovery** + +This clause describes procedures for building a tree-based hybrid overlay network and procedures for recovering from failures in any intermediate peer that provide data broadcasting services. + +The shape of a hybrid overlay network will change with every joining of a new peer. It needs to guarantee that there is no loop and provide robustness on the failure of single or multiple node failures. + +For fast recovery of a network, each peer establishes multiple candidate paths during the joining procedure and chooses one of them as a primary path. The primary path is used to distribute data among each other. + +## 7.1 Hybrid overlay network construction procedures + +Hybrid overlay network is constructed through (1) overlay network joining (2) overlay network participation request propagation (3) candidate path establishment through peer-to-peer connection and (4) primary path establishment process as shown in Figure 7-1. + +![Figure 7-1: Hybrid P2P network construction procedures. The diagram illustrates the four-step process of joining a hybrid overlay network. A new peer (P) sends a 'HOMP request: Join' to the HOMS (Hybrid Overlay Management Server). The HOMS responds with a 'HOMP response: Peer list'. Peer P then sends 'HELLO PEER' and 'ESTAB PEER' messages to existing peers (A, B, C). Existing peers respond with 'ESTAB PEER' messages. Finally, peer P sends a 'SET PRIMARY' message to one of the existing peers. The diagram shows existing peers as grid circles and joining peers as solid grey circles. Solid arrows represent primary paths (Core Tree), dashed arrows represent peer protocol messages, and dotted arrows represent overlay management protocol messages. A thick grey arrow indicates the new primary path.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the four-step process of joining a hybrid overlay network: + +- HOMP request: Join**: A new peer (P) sends a request to the HOMS (Hybrid Overlay Management Server). +- HOMP response: Peer list**: The HOMS responds with a list of existing peers. +- HELLO PEER / ESTAB PEER**: Peer P sends 'HELLO PEER' and 'ESTAB PEER' messages to existing peers (A, B, C). Existing peers respond with 'ESTAB PEER' messages. +- SET PRIMARY**: Peer P sends a 'SET PRIMARY' message to one of the existing peers. + +**Legend:** + +- Existing peer**: Grid circle +- Joining peer**: Solid grey circle +- Peer protocol messages**: Dashed arrow +- Overlay management protocol messages**: Dotted arrow +- Primary path (Core Tree)**: Solid arrow +- New primary path**: Thick grey arrow + +Q.4101(21) + +Figure 7-1: Hybrid P2P network construction procedures. The diagram illustrates the four-step process of joining a hybrid overlay network. A new peer (P) sends a 'HOMP request: Join' to the HOMS (Hybrid Overlay Management Server). The HOMS responds with a 'HOMP response: Peer list'. Peer P then sends 'HELLO PEER' and 'ESTAB PEER' messages to existing peers (A, B, C). Existing peers respond with 'ESTAB PEER' messages. Finally, peer P sends a 'SET PRIMARY' message to one of the existing peers. The diagram shows existing peers as grid circles and joining peers as solid grey circles. Solid arrows represent primary paths (Core Tree), dashed arrows represent peer protocol messages, and dotted arrows represent overlay management protocol messages. A thick grey arrow indicates the new primary path. + +**Figure 7-1 – Hybrid P2P network construction procedures** + +### 7.1.1 Hybrid overlay network joining + +When a new peer joins an existing hybrid overlay network, it firstly sends a request message for joining a hybrid overlay management server (HOMS). This request message includes the following information: + +- peer's identifier; +- network address information that other peers can access; +- authentication information if necessary. + +The network address information describes the network address where other peers can access the peer and contains information necessary for connection establishment such as transport method (Transmission control protocol (TCP), web real-time communications (WebRTC), etc.), transmission port number, etc. + +On receiving this request, HOMS provides an appropriate entry peer list that contains part of the participants' list of the overlay network and issues a new *ticket-id* sequentially to the newly joining peer. This procedure ensures that all peers have a unique *ticket-id* that will be used within that overlay + +network, and a balanced tree shape. Through this step, an early joined peer has the *ticket-id* lower than that of the peer joining later. + +When it comes to selecting the entry peers, HOMS shall not compose the peer list with the peers having low *ticket-id* values to prevent the failure of joining incurred by the possibility that the peers with low *ticket-id* have already consumed their resources to establish primary paths with other peers. If the HOMS composes the peer list with the peers having high *ticket-id*, it also leads to failure of the joining procedures since the peers within the list may not yet be attached to the tree. Hence, it is important to provide an appropriate entry peer list. + +When a new peer joins, the HOMS sends a response message with a *ticket-id* *T* and an *entry\_peer\_list* composed of the following rules given below: + +![Diagram illustrating the selection of entry peers. A horizontal bar represents the 'Peers' list of length M. A segment of length K is highlighted and labeled 'Entry peer list'. A blue box indicates the starting position as ROUND(M x R(j)/100). The formula for the entry peer list is shown on the right.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram shows a horizontal bar representing the 'Peers' list of length *M*. A segment of length *K* is highlighted and labeled 'Entry peer list'. A blue box indicates the starting position as $\text{ROUND}(M \times R(j)/100)$ . The formula for the entry peer list is shown on the right: + +$$\text{entry peer list} = [$$ +$$\text{PI}[\text{ROUND}(M \times R(j)/100)],$$ +$$\text{PI}[\text{ROUND}(M \times R(j)/100)+1],$$ +$$\dots$$ +$$\text{PI}[\text{ROUND}(M \times R(j)/100)+K]$$ +$$]$$ + +Diagram illustrating the selection of entry peers. A horizontal bar represents the 'Peers' list of length M. A segment of length K is highlighted and labeled 'Entry peer list'. A blue box indicates the starting position as ROUND(M x R(j)/100). The formula for the entry peer list is shown on the right. + +- PI: The full set of peers currently remaining in the overlay network, sorted by *ticket-id* in ascending order; +- M: The number of PI's element; +- *R(j)*: The relative position of peer within *M*, and it is expressed in percentage (%). This value is configured by an administrator of HOMS. For example, if 100 peers are currently participating and the value of *R(j)* is 80, this means the peer is located in the 80th position in the PI; +- K: This value indicates the maximum number of peers to be included in the *entry peer list*. + +### 7.1.2 Participation request propagation + +When the newly joining peer *P(j)* receives the peer list and its *ticket-id*, it chooses one peer *P(n)* from the *entry peer list* and sends a HELLO\_PEER request message to let other peers know its participation. If *P(j)* fails to establish a connection with the chosen peer, it resumes with the next peer in the *entry peer list*. If successful, *P(j)* does not try to send the request message anymore. HELLO\_PEER request message includes the following information: + +- *overlay-id*: is a unique overlay identifier; +- *ttl*: describes how many peers this message propagates up to. Whenever a peer forwards the message, it decrements this value by 1. If the decremented value is 0, the peer does not forward anymore and discards the message; +- *conn\_num*: describes the maximum number of connections with other peers that *P(j)* wants to establish; +- *peer's network address information*: network address information that other peers can access to *P(j)*. + +On receiving the HELLO\_PEER request message, *P(n)* sends a success response and adds *P(j)*'s information into its incoming candidate path list. On receiving the success response, *P(j)* adds the *P(n)*'s information into its outgoing candidate path list. + +If $P(n)$ has an available capacity on its resource, it sends an ESTAB\_PEER request message to $P(j)$ including following information: + +- overlay-id; +- peer-id; +- ticket-id. + +In order to prevent overhead, each peer maintains the following information and uses them to calculate its availabilities: + +- the number of maximum/current primary paths; +- the number of incoming/current candidate paths; +- the number of outgoing/current candidate paths. + +In addition, $P(n)$ is also required to send the received HELLO\_PEER request message from $P(j)$ to other peers that are connected as a primary path by conducting the following operations: + +- decrements the value of *ttl* if it is not zero. If the value is zero, $P(n)$ does not send the HELLO\_PEER request message and discards the message. +- If $P(n)$ has multiple primary paths with other peers except for a newly established peer, it forwards the HELLO\_PEER request message to other peers. +- If $P(n)$ decides to send an ESTAB\_PEER request message to $P(j)$ , it subtracts the value of *conn\_num* and divides the number of $P(n)$ 's primary peers and replaces the *conn\_num* value of a HELLO\_PEER with the calculated value. That is, when the *conn\_num* value in the received HELLO\_PEER message from $P(j)$ is $N$ , and $P(n)$ has sent an ESTAB\_PEER message, and the number of the primary path is $P$ , the *conn\_num* value in the HELLO\_PEER request message sent to each primary peer is set to $(N-1)/P$ . If $P(n)$ does not have any subordinate peers that are connected as a primary path, the operation is terminated without further forwarding. + +Through these procedures, $P(j)$ secures multiple outgoing candidate paths, and it sends a SET\_PRIMARY request message to the most appropriate peer among the candidate peers to establish a primary path. To select the most appropriate peer, $P(j)$ can figure out the metrics by sending the PROBE\_PEER message to all candidate peers. + +On sending a PROBE\_PEER message, $P(j)$ inserts its local timestamp into the message, and other peers respond with the timestamp embedded. When $P(j)$ receives the response, it calculates the time difference. Figure 7-2 shows an example of a constructed shape of a hybrid overlay network. + +![Figure 7-2: Example shape of a constructed hybrid P2P network. The diagram shows a network of 10 nodes (0-9) arranged in a roughly circular fashion. Node 0 is the central node. Solid double-headed arrows represent 'Primary paths', connecting node 0 to nodes 2, 4, 8, 7, 6, 3, and 1. Node 1 is connected to node 0 and node 3. Dashed double-headed arrows represent 'Outgoing candidate paths', connecting nodes 5, 2, 8, 4, 7, 6, 3, and 9 to node 0. Node 5 is connected to nodes 2 and 9. Node 2 is connected to nodes 5 and 8. Node 8 is connected to nodes 2 and 4. Node 4 is connected to nodes 8 and 7. Node 7 is connected to nodes 4 and 6. Node 6 is connected to nodes 7 and 3. Node 3 is connected to nodes 6 and 1. Node 9 is connected to nodes 5 and 0. A legend at the bottom right indicates that a dashed line with an arrow represents an 'Outgoing candidate path' and a solid line with an arrow represents a 'Primary path'.](d4af765160d04ecef538e5066006dc77_img.jpg) + +Figure 7-2: Example shape of a constructed hybrid P2P network. The diagram shows a network of 10 nodes (0-9) arranged in a roughly circular fashion. Node 0 is the central node. Solid double-headed arrows represent 'Primary paths', connecting node 0 to nodes 2, 4, 8, 7, 6, 3, and 1. Node 1 is connected to node 0 and node 3. Dashed double-headed arrows represent 'Outgoing candidate paths', connecting nodes 5, 2, 8, 4, 7, 6, 3, and 9 to node 0. Node 5 is connected to nodes 2 and 9. Node 2 is connected to nodes 5 and 8. Node 8 is connected to nodes 2 and 4. Node 4 is connected to nodes 8 and 7. Node 7 is connected to nodes 4 and 6. Node 6 is connected to nodes 7 and 3. Node 3 is connected to nodes 6 and 1. Node 9 is connected to nodes 5 and 0. A legend at the bottom right indicates that a dashed line with an arrow represents an 'Outgoing candidate path' and a solid line with an arrow represents a 'Primary path'. + +Q.4101(21) + +**Figure 7-2 – Example shape of a constructed hybrid P2P network** + +## 7.2 Hybrid overlay network recovery procedures + +A tree-based hybrid overlay network is a shape of a spanning tree that has no loop, and the shape needs to be maintained against any peer dynamics which means peers join and leave during service. That is, all hybrid peers are connected into a tree without a loop. Therefore, it is required that the network supports fast recovery on any possible events such as graceful leave of peer and abnormal termination of peer. + +When peer $P(p)$ detects a leave of peer $P(j)$ that is attached as a primary path, it establishes a new primary path by choosing one of its outgoing candidate paths. However, if $P(p)$ tries to re-establish a primary connection on every candidate path, it may lead to a collapse of the tree by the occurrence of a loop. In order to prevent the loop, $P(p)$ does not perform a recovery operation, if it has a *ticket-id* value lower than that of $P(j)$ . If $P(p)$ has *ticket-id* value higher than that of $P(j)$ and it has outgoing candidate paths, it sends a SET\_PRIMARY message to the most appropriate candidate. If $P(p)$ has no more outgoing candidate paths, it requests HOMS to send the latest *entry peer list*, and to do the same procedures with the joining procedures described in clause 7.1 except adding a *recovery* parameter into a HELLO\_PEER request message to let the other peers know that this message is for recovery. In this case, HOMS may use a different $R(j)$ value from the value of initial joining. For example, if an entry peer selects a node in the bottom 80% at the time of initial participation, the peer may select the node in the top 20% for reconstruction. + +When creating an entry peer list, if there is no peer whose *ticket-id* precedes the requesting peer, the HOMS informs that the peer is at the top position by sending an empty list or an error response message. In both cases, the peer does not perform an additional operation. + +When $P(n)$ , included in the entry peer list from HOMS, receives the HELLO\_PEER message having *recovery* parameter from $P(p)$ , it adds $P(p)$ to its incoming candidate path list. If its incoming candidate capacity is full, $P(n)$ disconnects the incoming candidate path with the peer with the lowest *ticket-id* that is lower than $P(p)$ 's *ticket-id* and adds $P(p)$ to its incoming candidate path list. + +Figure 7-3 shows an example of a recovered network on leaving peer 4. If peer 4 of Figure 7-3 leaves, peer 0 and peer 8, which were connected as a primary path with peer 4, detects the leave event. This event can be detected by a timeout or an explicit release message from a leaving peer. Peer 0 does not perform any operation because the *ticket-id* of the leaving peer is lower than itself. Since peer 8 + +has a higher *ticket-id*, peer 8 sends a SET\_PRIMARY message to peer 0 to establish a new primary path with peer 0. + +![Figure 7-3: Example shape of a recovered hybrid P2P network. The diagram shows two states of a network with 10 nodes (0-9). Node 0 is the central node. In the left state, node 4 is black, and there are 'X' marks on the edges (0,4) and (4,8). In the right state, node 4 is white, and a new solid primary path is shown from node 0 to node 8. Dashed arrows represent outgoing candidate paths, and solid arrows represent primary paths. A legend at the bottom right indicates: dashed arrow = Outgoing candidate path, solid double-headed arrow = Primary path. The text Q.4101(21) is also present.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +Figure 7-3: Example shape of a recovered hybrid P2P network. The diagram shows two states of a network with 10 nodes (0-9). Node 0 is the central node. In the left state, node 4 is black, and there are 'X' marks on the edges (0,4) and (4,8). In the right state, node 4 is white, and a new solid primary path is shown from node 0 to node 8. Dashed arrows represent outgoing candidate paths, and solid arrows represent primary paths. A legend at the bottom right indicates: dashed arrow = Outgoing candidate path, solid double-headed arrow = Primary path. The text Q.4101(21) is also present. + +Figure 7-3 – Example shape of a recovered hybrid P2P network + +# 8 Data recovery procedures + +Any peer in a hybrid overlay network can be a data source. This means that data generated by any peer is propagated to all other peers. However, in the process of recovering the tree through the process described in clause 7.2, peers can generate data asynchronously, which leads to a segmentation problem where the data generated and distributed in each segment during the tree recovery process is not fully distributed all over the tree as shown in Figure 8-1. + +![Figure 8-1: Cache synchronization among segments after tree recovery. The diagram shows two segments, Segment 1 (nodes A, B, C, D) and Segment 2 (nodes E, F, G, H), connected by a link between D and E. In the left state, the link (D,E) is broken, marked with an orange starburst. In the right state, the link is restored, and a new primary path (highlighted in green) is shown from node C to node E. A legend at the bottom indicates: solid black line = Primary path, solid green line = New primary path. The text Q.4101(21) is also present.](410562339ce067fdc6fa41940c118658_img.jpg) + +Figure 8-1: Cache synchronization among segments after tree recovery. The diagram shows two segments, Segment 1 (nodes A, B, C, D) and Segment 2 (nodes E, F, G, H), connected by a link between D and E. In the left state, the link (D,E) is broken, marked with an orange starburst. In the right state, the link is restored, and a new primary path (highlighted in green) is shown from node C to node E. A legend at the bottom indicates: solid black line = Primary path, solid green line = New primary path. The text Q.4101(21) is also present. + +Figure 8-1 – Cache synchronization among segments after tree recovery + +When peer E-D's primary path is cut off, the segment {E, F, G, H} and the segment {A, B, C, D} may have different cache due to the newly generated and partially distributed data packets that are not shared between segments. Even though the primary path between two segments is restored, there may be data loss between them. Hence, cache synchronization between two segments is required to complete segment merging. + +In order to support the segments merging, it is necessary to cache a certain amount of data transmitted and received by each peer for data recovery. + +This clause specifies the caching and recovery policy when creating an overlay network, caching buffer management of peers, data transmission / reception procedures, and data recovery procedures. + +## 8.1 Configurations on hybrid overlay network caching and recovery policy + +When an overlay network is being created through reference point R3 described in [ITU-T Q.4100], a peer provides two policies: caching policy and recovery policy. When a peer joins a particular hybrid overlay network, the HOMS provides the policies, and all participating peers follow the same caching and recovery policies on the same hybrid overlay network. + +### 8.1.1 Caching policy + +An owner peer that creates a hybrid overlay network specifies a caching policy that includes the following: + +- Minimum number of cached data(*mN\_Cache*): This parameter specifies the minimum size of caching buffer. Each peer should keep the circular queue with a size larger than the minimum value. If the value is 0, it means that the circular queue is not maintained. That is, the data recovery function is not provided. The data recovery function is disabled when data that has already been delayed is no longer valid in the delay-sensitive service such as a multimedia streaming service. +- Minimum duration of cached data(*mD\_Cache*): This parameter specifies the retention time for cached data. Each peer guarantees a minimum retention time for each cached data. + +If one of the two values (*mN\_Cache*, *mD\_Cache*) is not satisfied with respect to the caching policy, the corresponding cached data can be deleted; however, the cached data can be further maintained depending on the implementation i.e., when the value of *mD\_Cache* is 10 minutes and the value of *mN\_Cache* is 100. When the 101st packet arrives at the caching buffer, the oldest cached data can be deleted from the cache even though the retention time of each data packet to be erased is less than 10 minutes. In addition, even if 15 minutes of time has elapsed while there are still 50 data packets in the circular queue, the data packet older than the specified retention time can be deleted from the cache. + +### 8.1.2 Recovery policy + +The cached data can be exchanged in two ways; push and pull method. In pull mode, a peer that needs to get cached data from another peer, requests the data specifically. In push mode, a peer holding cached data broadcasts it to another peer that does not possess the data. + +An owner peer that creates a hybrid overlay network specifies a recovery policy that includes the following: + +- **recovery-by**: When the value is set to "push", data recovery is performed only through the primary path. This is useful when 1) the real-time data is important, 2) the frequency of data occurrence is not high, and 3) the data size is not large. When this value is set to 'pull', data recovery uses both the primary path and the candidate path. The newly created data is sent along the primary path in an existing way, and only the data to be used for recovery is delivered along the candidate path. This method is useful when data latency is not important and the size of the data is relatively large. + +## 8.2 Data caching and recovery in the hybrid peer + +In a hybrid overlay network, each hybrid peer needs to store a certain amount of data in a cache for data recovery. All peers maintain a caching buffer list consisting of a set of caching buffers in the form of a circular queue for each data source, and each caching buffer includes the following information as shown in Figure 8-2: + +- a) Source Peer ID; + +- b) DataPacket includes +- i) sequence number; + - ii) datetime that indicates the NTP time of being cached; + - iii) payload. + +![Diagram illustrating the Peer's cache buffer shape. It shows three circular buffers for Source PeerID #1, Source PeerID #2, and Source PeerID #3. Each buffer is a ring with a shaded segment representing cached data. A callout box for DataPacket lists its components: Sequence number, Datetime, and Payload. The text Q.4101(21) is at the bottom right.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +The diagram shows three circular cache buffers, each associated with a source peer: Source PeerID #1, Source PeerID #2, and Source PeerID #3. Each buffer is represented by a ring with a shaded segment indicating the amount of data currently cached. A callout box labeled 'DataPacket' lists its internal structure: 'Sequence number', 'Datetime', and 'Payload'. The text 'Q.4101(21)' is located at the bottom right of the diagram. + +Diagram illustrating the Peer's cache buffer shape. It shows three circular buffers for Source PeerID #1, Source PeerID #2, and Source PeerID #3. Each buffer is a ring with a shaded segment representing cached data. A callout box for DataPacket lists its components: Sequence number, Datetime, and Payload. The text Q.4101(21) is at the bottom right. + +Figure 8-2 – Peer's cache buffer shape + +If more than a certain number (or a certain size) is accumulated during the caching process, the oldest data will be deleted first. Also, if the difference between *datetime* of a cached data and the current NTP time exceeds the value of *mD\_Cache*, the cached data will be cleared. + +### 8.2.1 Data caching on broadcasting + +In a hybrid overlay network, when a peer receives a BROADCAST\_DATA message from the primary path, the peer immediately delivers the message to the other primary path. On receiving a BROADCAST\_DATA message from another peer, it checks whether the DataPacket with the same source peer ID and the same sequence number already exists in the caching buffer. If it does exist, the message is received again, and the peer does not propagate to other primary paths. Otherwise, the BROADCAST\_DATA message is propagated to another primary path and copied to the internal caching buffer. In addition, if the value of *mD\_Cache* exists in the corresponding overlay network, it records into the *datetime* of the cached DataPacket by adding *mD\_Cache* value to the current NTP time. + +### 8.2.2 Data recovery after re-establishment of primary path + +This clause describes the procedures for recovering lost data after the re-establishment of a new primary path. The recovery mode is pre-configured by an owner of the hybrid overlay network in HOMS as specified in clause 8.1. + +#### 8.2.2.1 Data recovery with push mode + +This clause describes the data recovery operation after tree recovery when the value of *recovery-by* is "push". This operation is performed when the peer establishes a primary path with another peer after one of its primary paths is disconnected. In a hybrid overlay network, each peer receives a *ticket-id* from the HOMS when joining the hybrid overlay network, which is then used for tree recovery. When the primary path is disconnected, the tree recovery operation is not performed when the disappeared peer has a *ticket-id* value higher than that of itself. However, the peer switches the + +candidate path to the primary path or attempts to establish a new primary path with the new peer when the peer with a lower *ticket-id* value disappears. + +Figure 8-3 shows procedures for data recovery when a tree is being reconstructed. + +![Sequence diagram illustrating data recovery procedures in push mode between two peers, P(a) and P(b).](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +The diagram shows a sequence of interactions between two peers, P(a) and P(b), represented by vertical lifelines. The sequence of messages is as follows: + +- 1** P(a) sends a **SET\_PRIMARY** message with *buf(a)* to P(b). +- 2** P(b) responds with **200** with *buf(b)* to P(a). +- 3** P(a) sends a **BROADCAST\_DATA** message with *(n)* to P(b). +- 4** P(b) receives the message and sends a **BROADCAST\_DATA** message with *(k)* to the right (outward propagation). +- 3** P(b) also sends a **BROADCAST\_DATA** message with *(k)* to P(a). +- 4** P(a) receives the message and sends a **BROADCAST\_DATA** message with *(k)* to the left (outward propagation). + +The diagram is labeled Q.4101(21) at the bottom right. + +Sequence diagram illustrating data recovery procedures in push mode between two peers, P(a) and P(b). + +**Figure 8-3 – Data recovery procedures in push mode** + +- ① *P(a)* sends its buffermap *buf(a)* when sending a **SET\_PRIMARY** message by including a *cache-recovery* parameter with '*true*' value. If the parameter does not exist, it does not proceed with the data recovery hereinafter. +- ② *P(b)* that receives a **SET\_PRIMARY** request from *P(a)* sends its buffermap *buf(b)* while sending 200 responses. +- ③ *P(a)* and *P(b)* send data that the corresponding peer does not have using the **BROADCAST\_DATA** message just like normal propagations. +- ④ *P(a)* and *P(b)* that have received these **BROADCAST\_DATA** messages pass the message to other primary paths as usual. + +Figure 8-4 shows an example of data recovery using push mode. When peer 1 disappears, peers 0, 3, 6, and 7 that have a primary path with peer 1 initiate the path recovery procedures. In the case of peer 0, since it has a *ticket-id* value lower than that of peer 1, it does not perform the recovery procedure. In contrary, peers 3, 6, and 7 have higher *ticket-id* values, so one of the candidate paths they have secured should be converted to a primary path by sending a **SET\_PRIMARY** message. Peers 3, 6 and 7 send their buffermap using response messages of **SET\_PRIMARY**, and then peers 2, 0, and 4 send the **BROADCAST\_DATA** message with the data that peers 3, 6 and 7 do not possess. + +![Figure 8-4: Data recovery procedures in push mode. The diagram shows two network states. The left state shows a network of nodes 0-9, A, B, C, and D. Node 0 is the central node, connected to nodes 2, 3, 4, 6, 7, and 9. Node 1 is connected to nodes 0, 3, 6, and 7. Node 2 is connected to nodes 0, 5, and 8. Node 3 is connected to nodes 0, 1, 6, and 9. Node 4 is connected to nodes 0, 8, and 7. Node 5 is connected to nodes 2 and 9. Node 6 is connected to nodes 1, 3, and 7. Node 7 is connected to nodes 1, 4, and 6. Node 8 is connected to nodes 2 and 4. Node 9 is connected to nodes 0 and 5. Node A is connected to node 7. Node B is connected to node A. Node C is connected to node 3. Node D is connected to node C. Solid lines represent primary paths, and dashed lines represent candidate paths. The right state shows the same network after a failure. Node 1 is now a green circle, indicating it is the new primary path. Solid lines represent the new primary path, and dashed lines represent candidate paths. Blue arrows indicate data recovery by push. The legend shows: Primary path (solid line), Candidate path (dashed line with arrow), New primary path (green line), and Data recovery by push (blue arrow).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Q.4101(21) + +Figure 8-4: Data recovery procedures in push mode. The diagram shows two network states. The left state shows a network of nodes 0-9, A, B, C, and D. Node 0 is the central node, connected to nodes 2, 3, 4, 6, 7, and 9. Node 1 is connected to nodes 0, 3, 6, and 7. Node 2 is connected to nodes 0, 5, and 8. Node 3 is connected to nodes 0, 1, 6, and 9. Node 4 is connected to nodes 0, 8, and 7. Node 5 is connected to nodes 2 and 9. Node 6 is connected to nodes 1, 3, and 7. Node 7 is connected to nodes 1, 4, and 6. Node 8 is connected to nodes 2 and 4. Node 9 is connected to nodes 0 and 5. Node A is connected to node 7. Node B is connected to node A. Node C is connected to node 3. Node D is connected to node C. Solid lines represent primary paths, and dashed lines represent candidate paths. The right state shows the same network after a failure. Node 1 is now a green circle, indicating it is the new primary path. Solid lines represent the new primary path, and dashed lines represent candidate paths. Blue arrows indicate data recovery by push. The legend shows: Primary path (solid line), Candidate path (dashed line with arrow), New primary path (green line), and Data recovery by push (blue arrow). + +**Figure 8-4 – Data recovery procedures in push mode** + +In addition, peers 2, 0, and 4 transmit the received *BROADCAST\_DATA* messages to synchronize data to the opposite direction simultaneously. Peers 3, 6 and 7 that receive the *BROADCAST\_DATA* message deliver it to other peers A, B, C, and D that have a primary path with them. Through these procedures, data synchronization among the segments is finished. + +#### 8.2.2.2 Data recovery with pull mode + +This clause describes the data recovery operation when the recovery-by value is "pull". According to the construction procedures specified in clause 8.1, the *ticket-id* of a peer's primary peer and candidate peer is designed to be higher than its own *ticket-id*. That is, candidate peers connected to a specific peer have *ticket-ids* lower than that of the specific peer. On establishing a new primary path, the peer with the higher *ticket-id* retrieves the lost data by the pull method, and the lower peer recovers by the push method as specified in clause 8.2.2.1. This clause describes the pull method in detail in accordance with Figure 8-5. + +![Sequence diagram illustrating data recovery procedures in pull mode among five peers: P(a), P(b), P(c), P(d), and P(e). The process involves five steps: 1. SET_PRIMARY from P(a) to P(b); 2. BUFFERMAP w. buf(a) from P(a) to P(b), P(c), P(d), and P(e); 3. 200 OK w. buf(b), buf(c), buf(d), buf(e) from P(b), P(c), P(d), and P(e) back to P(a); 4. GET_DATA from P(a) to P(b), P(c), P(d), and P(e); 5. BROADCAST_DATA from P(b) to P(a) and other peers. A shaded region highlights the interaction between P(a) and the other peers. A label 'Q.4101(21)' is at the bottom right.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant Pa as P(a) + participant Pb as P(b) + participant Pc as P(c) + participant Pd as P(d) + participant Pe as P(e) + + Note over Pa, Pe: 1 SET_PRIMARY + Pa->>Pb: SET_PRIMARY + + Note over Pa, Pe: 2 BUFFERMAP w. buf(a) + Pa->>Pb: BUFFERMAP + Pa-->>Pc: + Pa-->>Pd: + Pa-->>Pe: + + Note over Pa, Pe: 3 200 OK w. buf(b), buf(c), buf(d), buf(e) + Pb->>Pa: 200 OK + Pc-->>Pa: + Pd-->>Pa: + Pe-->>Pa: + + Note over Pa, Pe: 4 GET_DATA + Pa->>Pb: GET_DATA + Pa-->>Pc: + Pa-->>Pd: + Pa-->>Pe: + + Note over Pa, Pe: 5 BROADCAST_DATA + Pb->>Pa: BROADCAST_DATA + Pb->>Pc: BROADCAST_DATA + Pb->>Pd: BROADCAST_DATA + Pb->>Pe: BROADCAST_DATA + +``` + +Sequence diagram illustrating data recovery procedures in pull mode among five peers: P(a), P(b), P(c), P(d), and P(e). The process involves five steps: 1. SET\_PRIMARY from P(a) to P(b); 2. BUFFERMAP w. buf(a) from P(a) to P(b), P(c), P(d), and P(e); 3. 200 OK w. buf(b), buf(c), buf(d), buf(e) from P(b), P(c), P(d), and P(e) back to P(a); 4. GET\_DATA from P(a) to P(b), P(c), P(d), and P(e); 5. BROADCAST\_DATA from P(b) to P(a) and other peers. A shaded region highlights the interaction between P(a) and the other peers. A label 'Q.4101(21)' is at the bottom right. + +**Figure 8-5 – Data recovery procedures in pull mode** + +When a new primary path is established, the peer recovers the lost data with the following steps: + +- ① $P(a)$ sends a SET\_PRIMARY request message that does not contain its buffermap to $P(b)$ . +- ② $P(a)$ sends a BUFFERMAP request message including its buffermap to other primary paths and candidate paths connected to it. +- ③ All the peers that receive the BUFFERMAP message send 200 responses with their own buffermap. +- ④ $P(a)$ preferentially sends a GET\_DATA request message to candidate peers to request data that they do not have, and if there is data not acquired from candidate peers, it requests the primary peer. That is, by comparing the buffermap collected from all peers, requesting data that they do not have, and when both the candidate peer and the primary peer have it, the candidate peers are used first. + +$P(b)$ transmits data that the other peer does not have through the BROADCAST\_DATA request message when there is no data held by $P(a)$ . That is, push mode is used to send to a peer whose *ticket-id* value is lower than itself. + +When one peer goes out, peers connected to the primary path perform tree recovery and data recovery at the same time. In this process, duplicated data can be propagated along the tree. Therefore, before transmitting to the lower level, it is checked whether the corresponding data already exists in its buffer map, and if not, it is cached in its cache buffer. If it already exists, the data is not distributed. This is a safeguard to minimize the spread of duplicated data. + +Figure 8-6 shows procedures for data recovery using pull/push mode. When peer 1 disappears, peers 0, 3, 6, and 7, which are connected to the primary path with peer 1, initiate path recovery procedures. In the case of peer 0, since it has a lower value than peer 1, no additional action is performed, and peers 3, 6 and 7 convert one of the secured candidate paths to a primary path. Data generated in the segment {3}, {6, C, D} and {7, A, B} when the tree is being disconnected is propagated to all segments through peers 2, 0 and 4. In these processes, peers 3, 6, and 7 figure out the list of data they do not have through the buffermap exchanges with peers 2, 0, and 4, and request the data to the peers + +connected to the candidate path parallelly. The peer that received the recovered data completes all segment synchronization by passing it to other peers connected as the primary path. + +![Figure 8-6: Data recovery procedures in pull mode. The diagram shows two network states. The left state shows a network with nodes 0-9, A, B, C, and D. Node 0 is the root, connected to nodes 1, 2, 3, 4, 5, 6, 7, 8, and 9. Node 1 is connected to nodes 3, 6, and 7. Node 3 is connected to node 9. Node 6 is connected to node 0. Node 7 is connected to node A. Node 9 is connected to node D. Node 4 is connected to node 8. Node 2 is connected to node 5. Node 5 is connected to node 8. Node 8 is connected to node 4. Node 4 is connected to node 0. Node 0 is connected to node 1. Node 1 is connected to node 3. Node 3 is connected to node 9. Node 9 is connected to node D. Node 6 is connected to node 0. Node 7 is connected to node A. Node 8 is connected to node 4. Node 4 is connected to node 0. Node 2 is connected to node 5. Node 5 is connected to node 8. Node 8 is connected to node 4. Node 4 is connected to node 0. The right state shows the same network with a new primary path highlighted in green, connecting node 0 to node 3, node 3 to node 6, and node 6 to node 7. Data recovery by pull is shown with purple arrows pointing from node 3 to node 9, node 6 to node 0, and node 7 to node A. Data recovery by push is shown with blue arrows pointing from node 0 to node 3, node 3 to node 6, and node 6 to node 7. The legend indicates: Candidate path (dashed line with arrow), Primary path (solid line), Data recovery by push (blue arrow), New primary path (green line), and Data recovery by pull (purple arrow).](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +Figure 8-6: Data recovery procedures in pull mode. The diagram shows two network states. The left state shows a network with nodes 0-9, A, B, C, and D. Node 0 is the root, connected to nodes 1, 2, 3, 4, 5, 6, 7, 8, and 9. Node 1 is connected to nodes 3, 6, and 7. Node 3 is connected to node 9. Node 6 is connected to node 0. Node 7 is connected to node A. Node 9 is connected to node D. Node 4 is connected to node 8. Node 2 is connected to node 5. Node 5 is connected to node 8. Node 8 is connected to node 4. Node 4 is connected to node 0. Node 0 is connected to node 1. Node 1 is connected to node 3. Node 3 is connected to node 9. Node 9 is connected to node D. Node 6 is connected to node 0. Node 7 is connected to node A. Node 8 is connected to node 4. Node 4 is connected to node 0. Node 2 is connected to node 5. Node 5 is connected to node 8. Node 8 is connected to node 4. Node 4 is connected to node 0. The right state shows the same network with a new primary path highlighted in green, connecting node 0 to node 3, node 3 to node 6, and node 6 to node 7. Data recovery by pull is shown with purple arrows pointing from node 3 to node 9, node 6 to node 0, and node 7 to node A. Data recovery by push is shown with blue arrows pointing from node 0 to node 3, node 3 to node 6, and node 6 to node 7. The legend indicates: Candidate path (dashed line with arrow), Primary path (solid line), Data recovery by push (blue arrow), New primary path (green line), and Data recovery by pull (purple arrow). + +Figure 8-6 – Data recovery procedures in pull mode + +### 8.2.3 Data synchronization of a new peer + +When a new peer joins a hybrid overlay network, it needs to fully synchronize its caching buffer with other peers after establishing a primary path. Since the new peer may have multiple candidate paths and one primary path. It can make use of candidate paths for fetching data using pull mode and use the primary path for receiving newly generated latest data from the tree. Figure 8-7 shows procedures for filling the cache buffer of a newly joining peer. In this Figure, it is assumed that $P(a)$ has candidate paths with $P(b)$ , $P(c)$ , $P(d)$ and $P(e)$ . + +![Sequence diagram illustrating the procedures for filling the cache buffer of a newly joining peer. The diagram shows five peers: P(a), P(b), P(c), P(d), and P(e). P(a) is the newly joining peer with an empty buffer. P(e) is the primary path. P(b), P(c), and P(d) are candidate peers. The process involves: 1. P(a) sends a SET_PRIMARY request to P(e). 2. P(e) responds with a 200 OK w. buf(e). 3. P(a) sends GET_DATA requests to P(b), P(c), and P(d). 4. P(b), P(c), and P(d) respond with BROADCAST_DATA. Below the diagram, three source peers (Src PeerID #1, #2, #3) are shown with circular icons representing their buffers, which are being filled. A bracket indicates that the GET_DATA requests are repeated until all data embedded in BUFFERMAP(e) is received.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +Q.4101(21) + +Sequence diagram illustrating the procedures for filling the cache buffer of a newly joining peer. The diagram shows five peers: P(a), P(b), P(c), P(d), and P(e). P(a) is the newly joining peer with an empty buffer. P(e) is the primary path. P(b), P(c), and P(d) are candidate peers. The process involves: 1. P(a) sends a SET\_PRIMARY request to P(e). 2. P(e) responds with a 200 OK w. buf(e). 3. P(a) sends GET\_DATA requests to P(b), P(c), and P(d). 4. P(b), P(c), and P(d) respond with BROADCAST\_DATA. Below the diagram, three source peers (Src PeerID #1, #2, #3) are shown with circular icons representing their buffers, which are being filled. A bracket indicates that the GET\_DATA requests are repeated until all data embedded in BUFFERMAP(e) is received. + +**Figure 8-7 – Procedures for filling the cache buffer of a newly joining peer** + +- ① $P(a)$ selects $P(e)$ as a primary path among the candidate peers and sends a `SET_PRIMARY` request message. In this case, buffermap is not included. +- ② $P(e)$ includes its buffermap when sending a response message for a `SET_PRIMARY` request message to $P(a)$ . +- ③ $P(a)$ sends a `GET_DATA` request message requesting the data it needs to other candidate peers. In this process, $P(a)$ specifies the source peer ID and the sequence number of the data packet for the required data. +- ④ Candidate peers $P(b)$ , $P(c)$ , and $P(d)$ deliver the requested data. In this process, each peer transmits the data using the `BROADCAST_DATA` request message. + +## 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.* + + + +## 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.4104-202406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4104-202406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c80eef8760b13853767c4e33d17cbf437c8b51a8 --- /dev/null +++ b/marked/Q/T-REC-Q.4104-202406-I_PDF-E/raw.md @@ -0,0 +1,432 @@ + + +# Recommendation**ITU-T Q.4104 (06/2024)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Protocols and signalling for peer-to-peer communications + +--- + +# **Hybrid peer-to-peer (P2P) communications: Signalling requirements for data streaming services** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like design. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +## **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.4104 + +# Hybrid peer-to-peer (P2P) communications: Signalling requirements for data streaming services + +## Summary + +Recommendation ITU-T Q.4104 describes the signalling requirements for data streaming services over hybrid peer-to-peer networks. The hybrid overlay network may have multiple data sources which send different types of data. Thus, source peers and peers conduct the several specific operations for data streaming over hybrid peer-to-peer communications, and those operations define the requirements for the relevant protocols such as overlay management protocol and peer protocol. This Recommendation includes service architecture for data streaming services over hybrid peer-to-peer networks, high-level procedures and signalling requirements for the relevant protocols. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4104 | 2024-06-29 | 11 | 11.1002/1000/15963 | + +## Keywords + +Data streaming service, hybrid P2P, requirement. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 1 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 2 | +| 6 | Overview ..... | 2 | +| 7 | Procedures and components ..... | 4 | +| 7.1 | Procedures for data streaming service over HP2P network ..... | 4 | +| 7.2 | Roles of HP2P components for data streaming services ..... | 5 | +| 8 | Signalling requirements of each reference point ..... | 5 | +| 8.1 | Signalling requirements of reference point R1 (HOMS-source peer)..... | 6 | +| 8.2 | Signalling requirements of reference point R2 (Source peer-H-PEER)..... | 6 | +| 8.3 | Signalling requirements of reference point R3 (H-PEER-M-PEER)..... | 6 | +| 8.4 | Signalling requirements of reference point R4 (Data source-source peer) .... | 7 | +| | Appendix I – Distributed data storage over HP2P network..... | 8 | +| I.1 | Introduction ..... | 8 | +| I.2 | Scenario ..... | 8 | +| | Bibliography..... | 10 | + + + +###### Recommendation ITU-T Q.4104 + +## Hybrid peer-to-peer (P2P) communications: Signalling requirements for data streaming services + +# 1 Scope + +This Recommendation describes the signalling requirements for data streaming services over hybrid peer-to-peer networks including the following: + +- service architecture and each component; +- high-level procedures; +- signalling requirements. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T Q.4100] Recommendation ITU-T Q.4100 (2020), *Hybrid peer-to-peer communications: functional architecture*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 fragment** [b-ITU-T X.609]: A piece of the shared content. + +**3.1.2 hybrid overlay network** [ITU-T Q.4100]: A peer-to-peer overlay network that participating peers use to exchange data applying 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 obtaining data from other peers simultaneously. + +**3.1.3 hybrid peer** [ITU-T Q.4100]: A peer capable of exchanging data using the mesh-based and tree-based methods running over a hybrid overlay network. + +**3.1.4 overlay network** [b-ITU-T X.1162]: An overlay network is a virtual network that runs on top of another network. Like any other network, the overlay network comprises a set of nodes and links between them. Because the links are logical ones, they may correspond to many physical links of the underlying network. + +**3.1.5 peer-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.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|----------------------------------| +| HOMS | Hybrid Overlay Management Server | +| H-PEER | Hybrid Peer | +| HP2P | Hybrid Peer-to-Peer | +| M-PEER | Managed Peer | + +# 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Overview + +A data streaming service is a service for delivering data which a data source generates continuously or for a specific event. The types of deliverable data include binary data, text data, etc., which each data source generates. This differs from audio or video frames in multimedia streaming services, as each data stream generated by the data source in the data streaming service can be processed independently. For example, a data source can continuously generate data which is composed of text in a predefined format such as humidity or temperature of a certain place. + +[b-ITU-T X.609.10] defines signalling requirements for data streaming services over managed peer-to-peer (MP2P) networks which consider mesh topology only. In a hybrid peer-to-peer (HP2P) network, one or more source peers connected with data sources organize a CoreTree. Then sub-meshes or subtrees can be organized for streaming data. Thus, this Recommendation considers signalling requirements over a data streaming service over multiple types of networks, including tree topology and mesh topology and also considering interoperation between two types of networks. Figure 6-1 shows an example configuration of a data streaming service over an HP2P network. Each source peer may have different types of data, and each source peer can be a source of a sub-mesh or a subtree. + +![Figure 6-1: Example configuration of data streaming service over HP2P network. The diagram shows three network clouds: 'Hybrid P2P networks - CoreTree' (top left), 'Managed P2P networks - SubMesh' (top right), and 'Hybrid P2P networks - SubTree' (bottom). Each cloud contains nodes, some labeled 'S'. Arrows show data flow from a source in the CoreTree cloud, through the SubMesh cloud, to nodes in the SubTree cloud. Each cloud is associated with a yellow bar containing icons for snowflakes, a speedometer, a sun, a lightning bolt, and a thermometer. The CoreTree cloud also has two green gears. The SubMesh cloud has a green database icon. The SubTree cloud has a green line graph icon. A small text 'Q.4104(24)' is in the bottom right corner.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Figure 6-1: Example configuration of data streaming service over HP2P network. The diagram shows three network clouds: 'Hybrid P2P networks - CoreTree' (top left), 'Managed P2P networks - SubMesh' (top right), and 'Hybrid P2P networks - SubTree' (bottom). Each cloud contains nodes, some labeled 'S'. Arrows show data flow from a source in the CoreTree cloud, through the SubMesh cloud, to nodes in the SubTree cloud. Each cloud is associated with a yellow bar containing icons for snowflakes, a speedometer, a sun, a lightning bolt, and a thermometer. The CoreTree cloud also has two green gears. The SubMesh cloud has a green database icon. The SubTree cloud has a green line graph icon. A small text 'Q.4104(24)' is in the bottom right corner. + +**Figure 6-1 – Example configuration of data streaming service over HP2P network [ITU-T Q.4100]** + +Figure 6-2 shows reference points between components. [ITU-T Q.4100] defines three reference points which are R1 to R3, and this Recommendation additionally defines a new reference point between a source peer and a data source. + +![Figure 6-2: Reference points for data streaming service over HP2P network. The diagram is divided into three vertical domains: 'Data streaming service provider domain' (left), 'HP2P service provider domain' (middle), and 'User domain' (right). In the Data streaming service provider domain, there is a 'Source peer' and a 'Data source' connected by reference point R4. In the HP2P service provider domain, there is a 'HOMS' component. In the User domain, there are three stacked clouds: 'CoreTree' (top), 'SubTree' (middle), and 'SubMesh' (bottom). Each cloud contains an 'H-peer' (CoreTree and SubTree) or an 'M-peer' (SubMesh). Reference point R1 is between the Source peer and HOMS, and between HOMS and the top H-peer. Reference point R2 is between the Source peer and the top H-peer, and between the top H-peer and the middle H-peer. Reference point R3 is a vertical line connecting the top H-peer and the M-peer. A small text 'Q.4104(24)' is in the bottom right corner.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Figure 6-2: Reference points for data streaming service over HP2P network. The diagram is divided into three vertical domains: 'Data streaming service provider domain' (left), 'HP2P service provider domain' (middle), and 'User domain' (right). In the Data streaming service provider domain, there is a 'Source peer' and a 'Data source' connected by reference point R4. In the HP2P service provider domain, there is a 'HOMS' component. In the User domain, there are three stacked clouds: 'CoreTree' (top), 'SubTree' (middle), and 'SubMesh' (bottom). Each cloud contains an 'H-peer' (CoreTree and SubTree) or an 'M-peer' (SubMesh). Reference point R1 is between the Source peer and HOMS, and between HOMS and the top H-peer. Reference point R2 is between the Source peer and the top H-peer, and between the top H-peer and the middle H-peer. Reference point R3 is a vertical line connecting the top H-peer and the M-peer. A small text 'Q.4104(24)' is in the bottom right corner. + +**Figure 6-2 – Reference points for data streaming service over HP2P network** + +# 7 Procedures and components + +## 7.1 Procedures for data streaming service over HP2P network + +Figure 7-1 shows an overall procedure for a data streaming service over an HP2P network. As shown in Figure 7-1, the data streaming service is composed of three phases: initiation, distribution and termination. + +![Sequence diagram showing the overall procedure for data streaming service over HP2P network. The diagram is divided into three phases: Initiation, Distribution, and Termination. Lifelines include Data source, Source peer, HOMS, CoreTree (stack of Peers), SubMesh (stack of Peers), and SubTree (stack of Peers).](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the interaction between various components during a data streaming service over an HP2P network, organized into three distinct phases: + +- Initiation phase:** + - The **Data source** sends a message to the **Source peer**. + - The **Source peer** interacts with **HOMS** to perform **Overlay network creation**. + - Subsequently, **CoreTree organization** occurs between the **Source peer** and the **CoreTree** (represented as a stack of **Peer** boxes). +- Distribution phase:** + - The **Data source** sends **Data ingestion** to the **Source peer**. + - The **Source peer** then performs **Data distribution for CoreTree**, **Data distribution for SubMesh**, and **Data distribution for SubTree**, interacting with each respective stack of **Peer** boxes. +- Termination phase:** + - The **Source peer** sends **Overlay network termination** to **HOMS**. + - Finally, **Overlay network termination for SubMesh and SubTree** occurs between the **Source peer** and the corresponding **SubMesh** and **SubTree** stacks of **Peer** boxes. + +Q.4104(24) + +Sequence diagram showing the overall procedure for data streaming service over HP2P network. The diagram is divided into three phases: Initiation, Distribution, and Termination. Lifelines include Data source, Source peer, HOMS, CoreTree (stack of Peers), SubMesh (stack of Peers), and SubTree (stack of Peers). + +**Figure 7-1 – Overall procedure for data streaming service over HP2P network** + +### 7.1.1 Initiation phase + +In the initiation phase, an HP2P service provider prepares a streaming session by establishing a P2P network corresponding to the streaming session. A data source commands a source peer to create a streaming session. Then the source peer creates an overlay network that is the CoreTree by interacting with the hybrid overlay management server (HOMS). When a second data source needs to join the streaming session, which means that the second data source will generate a data stream pertaining to the data stream from the first data source, the second data source commands a source peer that may be different from the source peer linked to the first data source to join the streaming session as a member of the CoreTree. + +NOTE – Each source peer in a CoreTree becomes a source peer of either a SubTree or SubMesh. + +### 7.1.2 Distribution phase + +In the distribution phase, a data source sends a data stream to its source peer. The source peer injects the received data stream into the overlay network. The data stream will be distributed along with the CoreTree. If the source peer receiving the data stream is acting as a source peer of either the SubTree or SubMesh, the source peer sends the received data stream to the peers in a corresponding subnetwork, which is either SubTree or SubMesh. + +### **7.1.3 Termination phase** + +In the termination phase, the HP2P service provider can terminate a specific overlay network by interacting with the HOMS. The termination does not depend on a request from a specific data source, since multiple source peers linked to corresponding data sources can belong to an overlay network. A source peer can leave a streaming session according to the command from the linked data source, and every source peer leaving a streaming session shall notify the HOMS that it is leaving. The HOMS may terminate a streaming session and remove the corresponding overlay network, if no source peer is in the CoreTree. + +## **7.2 Roles of HP2P components for data streaming services** + +### **7.2.1 Data source** + +The data source generates a data stream and sends the generated data stream to one or more source peers. To send the data stream to the source peer, a signalling protocol such as [b-ITU-T X.609.8] can be used. + +### **7.2.2 Source peer** + +The source peer is responsible for encapsulating the data stream into a BROADCAST\_DATA message and sending the encapsulated data stream to H-PEERs with a primary connection relationship. + +### **7.2.3 H-PEER** + +H-PEERs forward the received encapsulated data stream to other H-PEERs with a primary connection relationship. + +### **7.2.4 HOMS** + +The HOMS manages the information about the overlay network. The information of each overlay network includes network information of peers including the source peer and H-PEERs in each overlay network. As part of the information about the overlay network, the HOMS also manages session information for data streaming sessions, such as title and human-readable descriptions. + +### **7.2.5 CoreTree** + +The CoreTree is composed of the peers which can broadcast their data at any time. Thus, the CoreTree is a backbone of HP2P networks for data streaming services. + +### **7.2.6 SubTree** + +The SubTree is composed of one source peer as a root node and other peers. The source peer gets data from one of the peers of the CoreTree and delivers the data to its child nodes. Then the data is broadcast along with the tree hierarchy of the SubTree. Thus, the SubTree is a distribution network of an HP2P network for data streaming services. + +### **7.2.7 SubMesh** + +The SubMesh is composed of one source peer as a root node and other peers. The source peer gets data from one of the peers of the CoreTree and delivers the data to its neighbouring nodes. Then the data is shared among peers in the SubMesh with the pull/push-pull method. Thus, the SubMesh is another type of distribution network of an HP2P network for data streaming services. + +# **8 Signalling requirements of each reference point** + +This clause describes the requirements to be considered in developing relevant protocols for providing data streaming services. This Recommendation assumes that any other existing protocols and its combinations can be used if they can meet the requirements that are listed in this clause. + +## **8.1 Signalling requirements of reference point R1 (HOMS-source peer)** + +Through reference point R1, a peer interacts with the HOMS to join a particular HP2P network and get a list of H-PEERs in the network. + +The following are requirements for reference point R1: + +When a source peer creates a data streaming session, it is required to create a corresponding overlay network by interacting with the HOMS. The HOMS responds with an identifier of the new overlay network, if the request from the source peer is accepted. + +HS-01: R1 is required to enable the HOMS to allow a source peer to create a new overlay network corresponding to a new data streaming session. + +HS-02: R1 is required to enable the HOMS to provide a unique identifier for the new overlay network if the request from the source peer is accepted. + +HS-03: R1 is required to enable the HOMS to provide the refresh expiration time for each overlay network and remove the overlay network if no refresh message from the corresponding source peer is received prior to the expiration time. + +HS-04: R1 is recommended to enable a source peer to send a refresh message prior to the expiration time for preventing the removal of its overlay network. + +To create a closed session, a source peer can specify a list of peers which are eligible to join the session or a password to be used for joining the session. + +HS-05: R1 is required to enable a source peer to provide a peer list when the source peer creates a closed session where only particular H-PEERs can join. + +NOTE – The peer list includes a set of peer identifiers. + +HS-06: R1 is required to enable a source peer to provide security information such as a password when the source peer creates a closed session where only the peers with the predefined password can join. + +## **8.2 Signalling requirements of reference point R2 (Source peer-H-PEER)** + +Through reference point R2, peers including a source peer and H-PEERs interact with each other for streaming data. + +HH-01: R2 is required to enable an H-PEER to request other H- PEERs to send fragments when they have the fragment which the peer needs. + +HH-02: R2 is required to enable an H-PEER to send fragments to a requesting H- PEER, if it can send the requested fragments. + +Various transport protocols can be used when peers interact with each other. + +HH-03: R2 is required to support TCP as a transport protocol. + +HH-04: R2 can optionally support WebRTC to interact with each peer running as a web application. + +## **8.3 Signalling requirements of reference point R3 (H-PEER-M-PEER)** + +Through reference point R3, H-PEERs and M-PEERs interact with each other for streaming data. + +HM-01: R3 is required to enable an H-PEER/M-PEER to request M-PEERs/H-PEERs to send fragments when they have the fragment which the peer needs. + +HM-02: R3 is required to enable an H-PEER/M-PEER to send fragments to a requesting peer that is either an H-PEER or an M-PEER, if it can send the requested fragments. + +Various transport protocols can be used when peers interact with each other. + +HM-03: R3 is required to support TCP as a transport protocol. + +HM-04: R3 can optionally support WebRTC to interact with each peer running as a web application. + +## **8.4 Signalling requirements of reference point R4 (Data source-source peer)** + +Through reference point R4, a data source gathers data from various devices like IoT devices and sends the data to a certain source peer. It is also possible for data sources to send data directly to the source peer, if the data sources can generate data. The source peer then shares the received data with other peers instantly through reference point R2 or R3. Unlike multimedia streaming and content distribution services, multiple data sources can exist at the same time within an overlay network. + +DS-01: R4 is required to enable a source peer to receive data from various sources, and convert them to a specified format to be distributed over an overlay network in a unified manner. + +DS-02: R4 is recommended to enable a source peer to accommodate multiple data sources at the same time. + +DS-03: R4 is required to enable a data source to provide its identifier to the source peer. + +DS-04: R4 is required to enable a source peer to be able to identify multiple data sources using their identifiers. + +DS-05: R4 is required to enable a data source to register itself on a source peer as its initiation operation. + +DS-06: R4 is required to enable a source peer to support the registration of data sources. + +DS-07: R4 is required to enable a data source to send its data to a source peer which the data source registered. + +# Appendix I + +## Distributed data storage over HP2P network + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Introduction + +A data streaming service is a service for delivering multiple independent data streams which a data source generates continuously or for a specific event. Among the various types of data, there is data to be stored for data analysis. The data can be stored in local dedicated servers or the cloud servers of a certain cloud service. Instead of using dedicated servers or cloud services which incur monetary costs, possibly linear to the volume of total data, voluntary devices can store the data. The voluntary devices are geographically distributed and thus the distribution of devices can prevent a single failure of service. However, sending data to each voluntary device may have a huge burden on the data source devices. To reduce the delivery burden, data source devices and voluntary device can be attached to a hybrid peer-to-peer (HP2P) network. Data source devices send data to peers in the HP2P network once and then the peers in the P2P network spread to voluntary devices. + +## I.2 Scenario + +Figure I.1 shows an example configuration of distributed data storage. One or more data source devices can attach to an HP2P network. When multiple data source devices attach to an HP2P network, they can be connected to distinct hybrid peers or to a single hybrid peer. To store the data, at least one storage device needs to be attached to the HP2P network. When a storage device voluntarily attaches to the HP2P network by connecting to a hybrid peer in the HP2P network, it needs to interact with a management server, depicted as "Mgmt server" in Figure I.1, for registration. After the registration, data source devices can be aware of the availability of storage devices by interacting with the management server. With this awareness, data source devices start data streaming to a connected hybrid peer(s). When a hybrid peer which is connected to any storage device receives a data stream, it forwards the data stream to the attached storage device(s). + +![Diagram illustrating the example configuration of distributed data storage over an HP2P network. The diagram shows a central cloud labeled 'HP2P network' containing four 'Hybrid peer' nodes. Three 'Data source device' nodes (A, B, and C) are connected to the network via hybrid peers. Four 'Storage device' nodes (A, B, C, and D) are also connected to the network via hybrid peers. A 'Mgmt server' node is shown outside the network, connected to one of the hybrid peers.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` +graph TD + subgraph HP2P_network [HP2P network] + HP1((Hybrid peer)) + HP2((Hybrid peer)) + HP3((Hybrid peer)) + HP4((Hybrid peer)) + end + DS_A((Data source device A)) --- HP1 + DS_B((Data source device B)) --- HP1 + DS_C((Data source device C)) --- HP1 + SD_A((Storage device A)) --- HP2 + SD_B((Storage device B)) --- HP3 + SD_C((Storage device C)) --- HP3 + SD_D((Storage device D)) --- HP4 + MS((Mgmt server)) --- HP2 +``` + +Diagram illustrating the example configuration of distributed data storage over an HP2P network. The diagram shows a central cloud labeled 'HP2P network' containing four 'Hybrid peer' nodes. Three 'Data source device' nodes (A, B, and C) are connected to the network via hybrid peers. Four 'Storage device' nodes (A, B, C, and D) are also connected to the network via hybrid peers. A 'Mgmt server' node is shown outside the network, connected to one of the hybrid peers. + +Q.4104(24) + +Figure I.1 – Example configuration of distributed data storage + +Each storage device needs to report to the management server on the status of its stored data. The report may include: 1) its ID, 2) the sequence number of the first data stored, 3) the sequence number of the last data stored. On the basis of the reported information, the management server can provide a list of storage devices which store a specific range of data. In other words, any device which wants to access the stored data for analysis interacts with the management server to get the list of storage devices. Then the device can connect to any storage device on the list to get the data. + +# Bibliography + +- [b-ITU-T X.609] Recommendation ITU-T X.609 (2015), *Managed peer-to-peer (P2P) communications: functional architecture*. +- [b-ITU-T X.609.8] Recommendation ITU-T X.609.8 (2019), *Managed P2P communications: Management protocol for live data sources*. +- [b-ITU-T X.609.10] Recommendation ITU-T X.609.10 (2020), *Managed P2P communications: signalling requirements for data streaming*. +- [b-ITU-T X.1162] Recommendation ITU-T X.1162 (2008), *Security architecture and operations for peer-to-peer networks*. +- [b-ITU-T Y.2206] Recommendation ITU-T Y.2206 (2010), *Requirements for distributed service networking capabilities*. +- [b-ISO/IEC TR 20002] ISO/IEC TR 20002:2012, *Information technology – Telecommunications and information exchange between systems – Managed P2P: 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.4105-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bdd7bc1d3581fbdc3cf6b035f618693dbe3846 --- /dev/null +++ b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75efa8e3513a799767c04a0bb7bcd87a550f2378f5880629068581808c1c9f7f +size 7353 diff --git a/marked/Q/T-REC-Q.4105-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c7bf14cea271f93d7662b9374f3a522f5a98475 --- /dev/null +++ b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e330a8224c2cbffc86f42ebd4ebfeadd1d1dbc69dda1d4a31fb4960889c60ee7 +size 53716 diff --git a/marked/Q/T-REC-Q.4105-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41248b14716937267bc3b403d0d0ddb09ccf79c7 --- /dev/null +++ b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb0dc0b5168be51690ec6229cd3716a30be0481999960e16e4627f22751c83b6 +size 84140 diff --git a/marked/Q/T-REC-Q.4105-202406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..30ef17b760b57a1a2d6378427838d63d7c955339 --- /dev/null +++ b/marked/Q/T-REC-Q.4105-202406-I_PDF-E/raw.md @@ -0,0 +1,558 @@ + + +# Recommendation**ITU-T Q.4105 (06/2024)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Protocols and signalling for peer-to-peer communications + +--- + +# **Hybrid peer-to-peer (P2P) communications: Signalling requirements for feature-based video services** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like design. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +## **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.4105 + +# Hybrid peer-to-peer (P2P) communications: Signalling requirements for feature-based video services + +## Summary + +Recommendation ITU-T Q.4105 specifies signalling requirements for feature-based video services. The feature-based video services share features rather than fully encoded video data. The feature is used to recreate images at the remote end points connected to a hybrid overlay network. Since the hybrid overlay network constructs a backbone tree for distributing live data asynchronously, it can be used for video streaming, virtual conference, metaverse, etc. This Recommendation specifies signalling requirements for developing protocol specifications. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4105 | 2024-06-29 | 11 | 11.1002/1000/15964 | + +## Keywords + +Feature, hybrid peer-to-peer, requirements, signalling, video. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------------|------| +| 1 Scope ..... | 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 Feature-based video services ..... | 2 | +| 6.1 Overview ..... | 2 | +| 6.2 Feature-based video service mode..... | 3 | +| 7 Signalling requirements for feature-based video session control protocol..... | 4 | +| 7.1 Signalling requirements for supporting session owner ..... | 4 | +| 7.2 Signalling requirements for supporting session users ..... | 8 | +| 8 Signalling requirements for feature-based video transport protocol ..... | 10 | +| 8.1 Requirements for transporting control information..... | 11 | +| 8.2 Requirements for transporting reference image ..... | 14 | +| 8.3 Requirements for transporting video features ..... | 14 | +| Bibliography..... | 16 | + + + +## Recommendation ITU-T Q.4105 + +## Hybrid peer-to-peer (P2P) communications: Signalling requirements for feature-based video services + +# 1 Scope + +This Recommendation describes the signalling requirements for feature-based video services using a hybrid peer-to-peer network as follows: + +- overview of feature-based video services; +- protocol requirements for controlling feature-based video sessions; +- protocol requirements for transporting video features. + +# 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.4100] Recommendation ITU-T Q.4100 (2020), *Hybrid peer-to-peer communications: Functional architecture*. +- [ITU-T Q.4101] Recommendation ITU-T Q.4101 (2021), *Hybrid peer-to-peer communications: Tree and data recovery procedures*. +- [ITU-T Q.4102] Recommendation ITU-T Q.4102 (2022), *Hybrid peer-to-peer communications: Peer protocol*. +- [ITU-T Q.4102Amd1] Recommendation ITU-T Q.4102 (2022) Amd.1 (2024), *Hybrid peer-to-peer communications: Peer protocol – Amendment 1*. +- [ITU-T Q.4103] Recommendation ITU-T Q.4103 (2022), *Hybrid peer-to-peer communications: Overlay management protocol*. +- [ITU-T Q.4103Amd1] Recommendation ITU-T Q.4103 (2022) Amd.1 (2024), *Hybrid peer-to-peer communications: Overlay management protocol – Amendment 1*. + +# 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 that participating peers use to exchange data applying 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 obtaining data from other peers simultaneously. + +**3.1.2 hybrid peer** [ITU-T Q.4100]: A peer capable of exchanging data using the mesh-based and tree-based methods running over a hybrid overlay network. + +**3.1.3 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.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 feature:** A measurable and descriptive characteristic of content that represents an interesting part of an image, providing task-relevant information in computer vision and captured in an n-dimensional feature vector for machine learning. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|----------------------------------| +| FVS | Feature-based Video Service | +| HOMS | Hybrid Overlay Management Server | +| HP2P | Hybrid Peer-to-Peer | +| HPEER | Hybrid Peer | +| KDM | Key points Description Mode | +| P2P | Peer-to-Peer | +| SNNM | Shared Neural Network Mode | + +# 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. +- The keywords "peer" means a hybrid peer. +- The keywords "HP2P network" means a hybrid overlay network. + +# 6 Feature-based video services + +This clause describes the overview of feature-based video services and two types of service modes. + +## 6.1 Overview + +The feature-based video communication approach does not strive to restore the original video. Rather, it employs AI technologies to regenerate scene images. This allows for generating lifelike images and character animations from features, which can be tailored to specific service models. The shape of the features is closely associated with the target service. For instance, in a video conferencing service, + +features would predominantly represent facial details, whereas a service focused on dance videos would emphasize the representation of body rig information. + +In addition, the feature can be exchanged over an HP2P network, specified in [ITU-T Q.4100], to support many concurrent users. To support this, it needs to specify new protocols running on top of the overlay management protocol and peer protocol, specified in [ITU-T Q.4102] and [ITU-T Q.4103], respectively. This Recommendation specifies signalling requirements for the feature-based video service. These requirements will be used to specify the protocol specification. + +## 6.2 Feature-based video service mode + +There are two modes for providing video services with features derived from machine learning: shared neural network mode (SNNM) and key points description mode (KDM). This clause describes the two modes in detail. + +### 6.2.1 Shared neural network mode (SNNM) + +In SNNM mode, each end point shares the same neural network and shares features derived from the neural network. To use this mode, each participant needs to have a neural network model that includes the shape of the neural network and a pretrained model. + +Figure 6-1 shows an overall concept of a shared neural network model in which each end point uses the same neural network architecture and pretrained data. A remote end point creates the image using the feature and reference image that is the base image for the newly created image. In this case, the feature may be the output data of a particular neural network layer. + +![Diagram illustrating the Shared Neural Network Mode (SNNM) for facial video communication. It shows two end points (represented by faces) connected by a central horizontal bar. Above the bar, a blue double-headed arrow labeled 'Neural network metadata' is shown. Above this arrow, two light blue boxes indicate the 'Feature-based video session control protocol' and 'Feature-based video transport protocol'. Below the central bar, a sequence of seven orange boxes is shown, labeled 'Feature', 'Feature', 'Feature', 'Feature', 'Feature', 'Feature', and 'Ref. Image'. Below each of these boxes is a small thumbnail image: the first six are heatmaps, and the seventh is a reference face image. The entire diagram is labeled 'Q.4104(24)' in the bottom right corner.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Diagram illustrating the Shared Neural Network Mode (SNNM) for facial video communication. It shows two end points (represented by faces) connected by a central horizontal bar. Above the bar, a blue double-headed arrow labeled 'Neural network metadata' is shown. Above this arrow, two light blue boxes indicate the 'Feature-based video session control protocol' and 'Feature-based video transport protocol'. Below the central bar, a sequence of seven orange boxes is shown, labeled 'Feature', 'Feature', 'Feature', 'Feature', 'Feature', 'Feature', and 'Ref. Image'. Below each of these boxes is a small thumbnail image: the first six are heatmaps, and the seventh is a reference face image. The entire diagram is labeled 'Q.4104(24)' in the bottom right corner. + +Figure 6-1 – Example of SNNM for facial video communication + +### 6.2.2 Key points description mode (KDM) + +In KDM mode, sharing the same neural network model is unnecessary. Each end point extracts key points of their input stream, converts them into a unified form, and sends them to other end points. Figure 6-2 shows a concept of a key points model that uses landmarks as a feature. A remote end point receiving the key points data recreates the image using the landmark and reference image that is the base image for the newly created image. + +![Diagram illustrating the KDM for facial video communication. On the left, three participants (CFL 1, CFL 2, CFL 3) are shown with their respective face landmarks. Each participant has a 'Plug-in' box. Arrows from these plug-ins point to a central 'Face landmark metadata' box. Above this box are three callouts: 'Convert CFL ↔ SFL', 'Feature-based video session control protocol', and 'Feature-based video transport protocol'. The 'Face landmark metadata' box contains a sequence of elements: 'Ref. Image', 'SFL', 'SFL', 'SFL', 'Ref. Image', 'SFL', 'SFL', and so on. Below this sequence is a 'SFL' (Standard face landmark) image. Arrows from the 'Face landmark metadata' box point to another set of 'Plug-in' boxes on the right, which in turn point to three participants (CFL 1, CFL 2, CFL 3) on the right side. A legend at the bottom right indicates: '* CFL: Custom face landmark' and '* SFL: Standard face landmark'. The text 'Q.4104(24)' is also present.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Diagram illustrating the KDM for facial video communication. On the left, three participants (CFL 1, CFL 2, CFL 3) are shown with their respective face landmarks. Each participant has a 'Plug-in' box. Arrows from these plug-ins point to a central 'Face landmark metadata' box. Above this box are three callouts: 'Convert CFL ↔ SFL', 'Feature-based video session control protocol', and 'Feature-based video transport protocol'. The 'Face landmark metadata' box contains a sequence of elements: 'Ref. Image', 'SFL', 'SFL', 'SFL', 'Ref. Image', 'SFL', 'SFL', and so on. Below this sequence is a 'SFL' (Standard face landmark) image. Arrows from the 'Face landmark metadata' box point to another set of 'Plug-in' boxes on the right, which in turn point to three participants (CFL 1, CFL 2, CFL 3) on the right side. A legend at the bottom right indicates: '\* CFL: Custom face landmark' and '\* SFL: Standard face landmark'. The text 'Q.4104(24)' is also present. + +**Figure 6-2 – Example of KDM for facial video communication** + +# 7 Signalling requirements for feature-based video session control protocol + +This clause describes the signalling requirements for controlling the feature-based video session, such as creation, modification, joining, leaving, etc. Each clause describes the necessity with simple scenarios for a better understanding and the requirements to support it. + +## 7.1 Signalling requirements for supporting session owner + +This clause specifies the signalling requirements for the features used by a session owner. + +### 7.1.1 FVS session creation + +A single hybrid overlay service session operates exclusively on one HP2P network. Furthermore, only one overlay service is present in a given HP2P network. If a service client requires multiple services, it can receive them by participating in a separate HP2P network. The HPEER that creates the service session becomes the owner and possesses full control over the service. The service session owner creates the session using the *HybridOverlayCreation* request message specified in [ITU-T Q.4103] and [ITU-T Q.4103Amd1]. Table 7-1 lists the requirements related to session creation. + +**Table 7-1 – Requirements related to session creation** + +| Req.ID | Requirements | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCR-001 | It is required to assign a feature-based video service session to a single HP2P network. | +| SCR-002 | It is required to concurrently create a feature-based video session and an HP2P network. | +| SCR-003 | It is required to provide the following information by the service owner to create a feature-based video session:
  • – session initiation and termination time;
  • – preferences on public or private;
  • – session title;
| + +**Table 7-1 – Requirements related to session creation** + +| Req.ID | Requirements | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | – etc. | +| SCR-004 |

It is recommended that the session owner specify the valid period of the service session when creating a feature-based video session.

NOTE 1 – The session is valid for the same length of time as the overlay. If not specified, the default validity period is one day.

| +| SCR-005 |

It is recommended to support setting up a policy for participation when creating a service session by a service session owner.

NOTE 2 – The service owner controls the access rights for the service session using the access_key and peerlist field values of OVERLAY_AUTH specified in [ITU-T Q.4103].

NOTE 3 – The service owner controls the access rights by specifying a block list that contains a list of users that are prevented from accessing the service session.

NOTE 4 – In the case that peerlist and access_key exist at the same time in an OVERLAY_AUTH, the user is treated as having access rights, if any of the access rights are satisfied.

| +| SCR-006 |

It is recommended to support setting up a policy for transmission rights when creating a service session by a service session owner.

NOTE 5 – The service owner has the floor control function for the service session by specifying a source list that includes a list of users authorized to send data.

| + +Feature-based video services can be provided using either SNNM or KDM. The feature, transmitted during the service, is applied to the pre-delivered reference images to generate new images. The newly generated sequence of images is then serialized to create a video. Table 7-2 shows the requirements related to session modes on creation. + +**Table 7-2 – Requirements related to session modes on creation** + +| Req.ID | Requirements | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCR-010 |

It is required of a session owner to specify the feature-based video mode on session creation.

NOTE 1 – When the service session owner creates a service session, it designates the feature mode it wants to use for each channel included in the service, and this mode is maintained until the session ends.

NOTE 2 – The service session owner selects one of SNNM and KDM for the feature mode.

| +| SCR-011 |

In SNNM, it is required to provide sufficient information to participate in the feature-based video session when it is created by the session owner. This information includes the following:

  • – shape of neural network;
  • – URI of neural network model;
  • – shape of feature;
  • – etc.
| + +**Table 7-2 – Requirements related to session modes on creation** + +| | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCR-012 | In SNNM, it is recommended to provide the architecture of the neural network in the neural network model file. | +| SCR-013 | In KDM, it is required to provide sufficient information to participate in the feature-based video session. The information includes the following:
  • – feature format;
  • – transmission interval;
  • – size of feature;
  • – tamper prevention method;
  • – etc.
NOTE 3 – Unlike SNNM, the feature will be expressed in a well-known unified format. However, this may lead to tampering by malicious peers located in the CoreTree. Therefore, it needs to provide a method to prevent the feature from being forged. | + +### 7.1.2 FVS in-session controls + +The service session owner can modify information related to the service session, and in some cases, it may be necessary to communicate these changes to participating users. The service session owner controls the session using the *HybridOverlayModification* request message specified in [ITU-T Q.4103] and [ITU-T Q.4103Amd1]. + +**Table 7-3 – Requirements related to in-session control** + +| Req.ID | Requirements | +|---------|--------------------------------------------------------------------------------------------------------| +| ISC-001 | It is required of the session owner to participate in the HP2P network to control the service session. | + +#### 7.1.2.1 Transfer of session ownership + +The service session owner can transfer ownership to another user. This can provide flexibility to the service scenarios. Table 7-4 lists the requirements for the transfer of the services session ownership. When the ownership of a service session is changed, the session owner notifies the HOMS that the ownership has been changed and broadcasts a notification message to the HP2P network to inform other HPEERs that the service session ownership has been changed. + +**Table 7-4 – Requirements related to ownership transfer** + +| Req.ID | Requirements | +|---------|-----------------------------------------------------------------------------------------------------| +| ISC-011 | It is required to support the ownership transfer of a session to another user by the session owner. | + +#### 7.1.2.2 Access control + +The service session owner has full authority on the access control of the specific service session. It is possible to block or unblock specific users and switch the service type between open and closed. Table 7-5 lists the requirements for the access control. When the access rights of a service session are modified, the session owner notifies the HOMS of the change and broadcasts a notification message + +across the HP2P network to inform other HPEERs that the access rights for the service session have been updated. + +**Table 7-5 – Requirements related to access control** + +| Req.ID | Requirements | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ISC-021 | It is required to support the service session owner to block or unblock specific users from the service session, regardless of whether the session is open or closed. | +| ISC-022 | It is required that the HOMS provides the functionality to manage blocked users in a block list to prevent them from attempting to participate in the session.
NOTE – All peers associated with a blocked user are excluded from the session and cannot participate again in the same network. | +| ISC-023 | It is recommended to support the service session owner to switch the service types between open and closed, and it is notified to the session participants. | +| ISC-024 | It is required to support the service session owner to control the access rights of specific users when the service type is closed, and it is notified to the session participants. | +| ISC-025 | It is required that the service session owner has the capability to modify access rights for the service session after its creation. | + +#### 7.1.2.3 Floor control + +The service session owner can do floor control on a specific service session. The user who has permission can send its message or data to the service session. It is also possible to designate multiple users to broadcast its data at any time. Table 7-6 lists the requirements related to this floor control. When the transmission rights for a service session are altered, the session owner informs the HOMS of the change and broadcasts a notification message to the HP2P network to notify other HPEERs that the transmission rights for the service session have been changed. + +**Table 7-6 – Requirements related to floor control** + +| Req.ID | Requirements | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ISC-031 | It is required that HOMS and HPEER support the control of transmission permission by the service session owner.
NOTE – The service session owner registers transmission permission to the HOMS. Other peers obtain this information from the HOMS when joining the session. | + +#### 7.1.2.4 Modifications on session attributes + +The service session owner has modification capabilities on the attributes of the specific service session. + +When the attributes of a service session are modified, the session owner notifies HOMS about the changes and broadcasts a notification message to the HP2P network, informing other HPEERs that the service session's attributes have been updated. + +Table 7-7 lists the requirements related to the session attributes. + +**Table 7-7 – Requirements related to session attributes** + +| Req.ID | Requirements | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ISC-041 | It is recommended to modify the following information of a feature-based video session by the service session owner.
  • – session initiation and termination time;
  • – service type which includes public or private;
  • – session title.
| + +### 7.1.3 FVS session termination + +The owner can explicitly terminate the service session, or it may end due to a timeout. When the service session is terminated, the service session owner notifies the HOMS that the session has ended and broadcasts a notification message to the HP2P network to inform other HPEERs that the service has been completed. HPEERs that receive this message propagate it to others while discontinuing any ongoing tree recovery process and terminating any secured primary and candidate paths. The service session owner terminates the session using the *HybridOverlayRemoval* request message specified in [ITU-T Q.4103] and [ITU-T Q.4103Amd1]. Table 7-8 lists the requirements related to the session termination by the owner or the HOMS. + +**Table 7-8 – Requirements related to session termination** + +| Req.ID | Requirements | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| STR-001 | It is required that when the owner of a service session ends the session, the HOMS also deletes any overlay information associated with that service session. | +| STR-002 | It is required that when the validity period of a service session has expired, the HOMS also deletes any overlay information associated with that service session. | + +## 7.2 Signalling requirements for supporting session users + +This clause describes the signalling requirements for the functionalities to be used by a session user. + +### 7.2.1 FVS session query + +The HOMS provides service information connected to the HP2P network and information on the HP2P network. For the query of the service session, it uses the *HybridOverlayQuery* request message specified in [ITU-T Q.4103] and [ITU-T Q.4103Amd1]. In response to this *HybridOverlayQuery* request message, the HOMS transmits service information and information about the HP2P network. Table 7-9 lists the requirements for the session query. Any user can query the service and session information of ongoing sessions. + +**Table 7-9 – Requirements related to session query** + +| Req.ID | Requirements | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USQ-001 | It is required for the HOMS to support the query of the feature-based video session in progress by use of the following keywords:
  • – title;
  • – description;
  • – etc.
| + +### 7.2.2 FVS session join + +Not only service users but also the session owner who created the service session is required to participate in the HP2P network. The HOMS determines whether the HPEER sending this message is the owner and sends a different response message. Like general HPEERs, the owner HPEER can freely join or leave the service session. When rejoining, it should be able to obtain all information about the current status of the HP2P network, as well as the status of the service. The service session user joins a specific session using the *HybridOverlayJoin* request message specified in [ITU-T Q.4103] and [ITU-T Q.4103Amd1]. Table 7-10 lists the requirements related to the service session joining by a peer. + +**Table 7-10 – Requirements related to service session joining** + +| Req.ID | Requirements | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USJ-001 | It is required for the HPEER to join the HP2P network mapped to a specific service session for participating in a FVS session. | +| USJ-002 | It is required for the HOMS to support, join and leave an FVS session at any time while the session is valid. | +| USJ-003 | When the HOMS receives a join request from HPEER, it is required for the HOMS to provide the following information necessary for the user to participate in the corresponding service session:
  • – start date and time of service session;
  • – end date and time of service session;
  • – detailed information on the channels constituting the service session;
  • – etc.
| + +Since data from various channels transmitted by HPEERs participating in the same hybrid overlay service session are transmitted through HPEERs participating in the HP2P network, ensuring security and integrity in the transmission process is necessary. Table 7-11 lists the requirements for securing integrity on service session joining. + +**Table 7-11 – Requirements related to secure integrity on service session joining** + +| Req.ID | Requirements | +|---------|----------------------------------------------------------------------------------------------| +| USJ-011 | When an HPEER joins the HP2P network, it is required to register its public key in the HOMS. | + +### 7.2.3 FVS session data exchange + +Refer to clause 8. + +### 7.2.4 FVS session leave + +HPEERs in the HP2P network may leave the service session through explicit or implicit procedures. Even if all HPEERs depart, the HP2P network remains valid for a specified period. The service session users leave the session using the *HybridOverlayLeave* request message specified in [ITU-T Q.4103] and [ITU-T Q.4103Amd1]. Table 7-12 lists the signalling requirements for the session leave procedures. + +**Table 7-12 – Requirements related to session leave** + +| Req.ID | Requirements | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USL-001 | It is required for the session to be valid for a designated period even if the service session owner leaves. If the owner returns to the session, it resumes control. | +| USL-002 | It is required that the HOMS removes all information related to the service session and the associated HP2P network, when a specific service session times out. | + +### 7.2.5 FVS session user query + +The HPEER participating in a service broadcasts its information by establishing a primary path with existing HPEERs participating in the HP2P network and receives data from other HPEERs from the existing HPEER. Therefore, it is possible to obtain information necessary for the service without interactions with the HOMS. However, when information on a specific service user is unavailable, a user can obtain it from the HOMS. Table 7-13 lists the requirements related to the session user query. + +**Table 7-13 – Requirements related to the session user query** + +| Req.ID | Requirements | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UQU-001 | It is required for the HOMS to support a query on a specific user with a peer-id, and the following information is provided as a response:
  • – public key;
  • – display-name;
  • – etc.
| + +# 8 Signalling requirements for feature-based video transport protocol + +This clause describes the requirements related to the feature-based video transport protocol for exchanging control messages and data messages among HPEERs in an HP2P network corresponding to a feature-based video service. By use of the feature-based video transport protocol, HPEERs can send and receive a unit of container, which includes the following: + +- control information; +- feature; +- reference image. + +The feature-based video transport protocol uses *BROADCAST\_DATA*, specified in [ITU-T Q.4102], and the payload format specified in [ITU-T Q.4102Amd1] on exchanging control information, + +reference image and features. The video application uses the reference image and features for reconstructing the video using artificial intelligence, such as generative AI. + +## 8.1 Requirements for transporting control information + +This clause describes the requirements relevant to transmission control among HPEERs in an HP2P network. The transmission control includes permission adjustment, negotiation between peers, etc. + +A peer that has newly joined an HP2P network can get the service information for participating in a service by communicating with the HOMS and the HPEERs already participating. The HPEERs provide the service information generated or changed dynamically. Table 8-1 lists the requirements for handling the service information. + +**Table 8-1 – Requirements related to the service information** + +| Req.ID | Requirements | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-101 | It is required for a new peer to broadcast a message to inform that the peer has successfully joined by establishing a primary path. | +| CTRL-102 | It is required for a new peer to broadcast a message, including its identifier, user name, public key, reference image, etc., used to receive data and generate the peer's video. | +| CTRL-103 | It is required for a peer establishing a primary path with a new peer to send every reference image of each source, peer list, public key, etc., used for feature-based video services. | +| CTRL-104 | It is recommended that peer uses PGP for signing the control information to be sent to guarantee the integrity of the control information. | + +The HPEER with data transmission permission can be a source, and the service session owner controls the permission. The owner of the service session has control over it, and participating peers adhere to this control. The session owner can authorize the peers to send information during the session. Table 8-2 lists the requirements related to the transmission of permission. + +**Table 8-2 – Requirements related to transmission permission** + +| Req.ID | Requirements | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-201 | It is required for a service session owner to be capable of giving transmission permission to a peer during the service session. | +| CTRL-202 | It is required for a peer to be capable of checking whether its transmission permission is granted. | +| CTRL-203 | It is required for a peer to broadcast its reference image when a peer recognizes that it gets transmission permission. | +| CTRL-204 | It is required for the service session owner to broadcast the change of transmission permission when it adjusts the transmission permission. | + +**Table 8-2 – Requirements related to transmission permission** + +| Req.ID | Requirements | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-205 | It is required for the service session owner to include a list of service session permission holders and a list of permit holders for a specific channel in the message announcing the permission change. | +| CTRL-206 | It is required for the transmission control information to include a list of users consisting of peer-ids that hold transmission control. | +| CTRL-207 | It is required that the message regarding transmission control includes a signature, using the service session owner's private key, on the hash value of the header to prevent any modification of the message. | + +When the service session owner explicitly terminates its service session, it informs the peers participating in the HP2P network and removes the registered service session from the HOMS. Table 8-3 lists the requirements related to service session termination. + +**Table 8-3 – Requirements related to service session termination** + +| Req.ID | Requirements | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-301 | It is required for a service session owner to broadcast a message notifying that their service session has been terminated. | +| CTRL-302 | It is required that the peer receiving the message about service session termination ignores any disconnection with other peers to prevent conducting tree recovery. | +| CTRL-303 | It is required to sign the headers and extension headers of the service session termination message with the private key of the service session owner to prevent message tampering. | + +It is necessary that the service session owner notifies all peers in the HP2P network when transferring the control of a service session to another peer. Table 8-4 lists the requirements related to the notifications when ownership of the session changes. + +**Table 8-4 – Requirements related to notifications on ownership transfer** + +| Req.ID | Requirements | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-311 | It is required to specify that the owner should broadcast the related control information message to the HP2P network immediately when transferring the control of the service session. | +| CTRL-312 | It is required to include a signature of the message header and extension header using the service session owner's private key in the message that notifies the transfer of service session control to another peer, along with information such as the peer ID of the peer who will have control. | + +The service session owner needs to notify all peers participating in the HP2P network when changing the service session information. Table 8-5 lists the requirements related to notifications on the change of the service session information. + +**Table 8-5 – Requirements related to notifications on the session modification** + +| Req.ID | Requirements | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-321 | It is required that the session owner broadcasts a relevant control information message to the HP2P network immediately upon changing the information of the service session. | +| CTRL-322 | It is required that the message notifying the change of information in a service session includes only non-impactful information on the peers' behaviour, such as title, description, and start and end time. Additionally, the header and extension header of the message should be signed with the service session owner's private key. | + +A peer in a service session needs to check the status of other participants to maintain the HP2P network and to provide the latest list of participants to the user corresponding to the peer. When a peer leaves the HP2P network without following the normal leave procedure, the peers with a primary relationship with the peer conduct the connection recovery as specified in [ITU-T Q.4101]. However, the HOMS cannot recognize the leave of the peer before the expiration of the information of the peer or receiving a report from other peers that have recovered a primary relationship. After recognition of the leave of a specific peer, the HOMS gives a list of peers except for the left peer upon the request from a newly-joined peer. Table 8-6 lists the requirements related to service session maintenance for keeping up-to-date information on the HP2P network. + +**Table 8-6 – Requirements related to service session maintenance** + +| Req.ID | Requirements | +|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-331 | It is recommended that a peer is capable of sending a SCAN_TREE message periodically or on a specific event to get the list of peers currently participating in a service session and to provide the latest list to the user corresponding to the peer. | +| CTRL-332 | It is required for a peer to broadcast its leave when it leaves an HP2P network. | +| CTRL-333 | It can optionally skip the broadcast peer's leave when a service session owner excludes it. | +| CTRL-334 | It is required that the message notifying the leave should include the user's ID and a signature using the user's private key to sign the hash value of the header. | +| CTRL-335 | It is recommended that a peer leaves gracefully by notifying its leave to decrease any possible instability in providing a service and unnecessary exchange of control messages. | + +It is necessary to provide the service session owner with the ability to remove a specific user from the session. Given the nature of the HP2P network, all peers are expected to relay not only their own data but also that of other peers. However, it is essential to establish procedures for removing peers that are negligent or engaging in malicious behaviour. Table 8-7 lists the requirements related to user expulsion. + +**Table 8-7 – Requirements related to user expulsion** + +| Req.ID | Requirements | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTRL-341 | It is required for the service session owner to be able to broadcast information about a malicious user to the HP2P network to exclude them immediately. | +| CTRL-342 | It is required to include the peer ID of the user to be excluded, as well as the hash value of the header and extension header signed with the service session owner's private key, in the message notifying the user's exclusion. | +| CTRL-343 | It is required to provide a way for the message to be delivered to all peers, despite any interference from malicious peers. | +| CTRL-344 | It is required that the receiving peer of this message should terminate its connection with the excluded peer if they are connected via a primary path. | +| CTRL-345 | It is required for peers to maintain an exclusion list to avoid re-establishing a primary path relationship with peers on the list within the same HP2P network. | +| CTRL-346 | It is required that a service session owner sends an encrypted message to the peers with a primary relationship with the peer to be evicted by the service session owner to command the peers to start the recovery process specified in [ITU-T Q.4101]. | + +## 8.2 Requirements for transporting reference image + +In providing a feature-based video service, the receiver client recreates an image that reflects the user's intention by combining the received reference image and feature. This clause describes the requirements for transmitting features. Table 8-8 lists the requirements related to sharing the reference image of a peer. + +**Table 8-8 – Requirements related to sharing reference image** + +| Req.ID | Requirements | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| TVF-101 | It is required that a peer broadcasts its reference image immediately after establishing a primary path. | +| TVF-102 | It can optionally be arranged for a peer to transmit their reference images on the primary path that the recovery procedure has set up. | +| TVF-103 | It is required to propagate the reference image to the HP2P network whenever it is updated. | + +## 8.3 Requirements for transporting video features + +The video feature takes different forms depending on the service mode used. In other words, in the SNNM, it will be a feature vector generated based on the structure of the neural network used by participating peers; while in the KDM, it will be data aligned with the notational syntax describing the key points. Table 8-9 lists the requirements related to the video feature. + +**Table 8-9 – Requirements related to the video feature** + +| Req.ID | Requirements | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VF-101 |

It is required to include information regarding the format of the feature used along with the feature.

NOTE 1 – When the service mode is SNNM, the transmitted feature is a feature vector for the frame derived from the neural network.

NOTE 2 – When the service mode is KDM, the transmitted feature includes key points information for the image.

| + +## Bibliography + +[b-ITU-T Y.2206] Recommendation ITU-T Y.2206 (2010), *Requirements for distributed service networking capabilities*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.45-198410-I_PDF-E/raw.md b/marked/Q/T-REC-Q.45-198410-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..78d906a67af9269ff24fb3054f0f27a35dbd9b6a --- /dev/null +++ b/marked/Q/T-REC-Q.45-198410-I_PDF-E/raw.md @@ -0,0 +1,297 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.45** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +SERIES Q: SWITCHING AND SIGNALLING + +International automatic and semi-automatic working – +General characteristics for international telephone +connections and circuits + +--- + +**Transmission characteristics of an analogue +international exchange** + +ITU-T Recommendation Q.45 + +Extract of **Red Book Fascicle VI.1 (1984)** + +--- + +# NOTES + +1 ITU-T Recommendation Q.45 was published in Fascicle VI.1 of the *Red Book*. This file is an extract from the *Red Book*. While the presentation and layout of the text might be slightly different from the *Red Book* version, the contents of the file are identical to the *Red Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# TRANSMISSION CHARACTERISTICS OF AN ANALOGUE INTERNATIONAL EXCHANGE 1) + +## 1 Introduction + +1.1 For the purposes of this Recommendation, an international exchange is a collection of equipment regarded as an entity by the Administration concerned. In the case of an international transit centre, it extends from the end of the incoming international line to the beginning of the outgoing international line (e.g. between such points as A and D in Figure 1/Q.45 or any other suitable pair of points). + +In the absence of an international agreement on the choice of the points delimiting an international exchange, it has proved impossible to draw up model specifications showing the limits to be observed for quantities measured between these points. The CCITT recommendations given hereafter have been issued regardless of the actual arrangement. + +Automatic international exchanges should be provided with circuit test access points (see Recommendation M.700 [1]) complying with the Recommendation cited in [2]. This Recommendation will ensure that circuit line-up and maintenance testing procedures are referred to points at or near the switchblock (Points B and C of Figure 1/Q.45). + +![Diagram of an international exchange showing equipment blocks 1, 2, and 3, with points X, A, B, C, D, and Y marked. A heavy line indicates a 'connection through the international exchange' between points A and D. Arrows indicate 'International line' and 'International circuit' paths.](2df09d249c38abee55dbf0526dd6da0a_img.jpg) + +The diagram illustrates the internal components of an international exchange. It consists of several blocks: '1' (channel translating equipment) at the far left and far right; '2' (incoming and outgoing relay set) blocks on either side of the central equipment; and '3' (automatic switching equipment) in the center. Points are marked as follows: X and A on the left, B and C in the center near the switching equipment, and D and Y on the right. A heavy horizontal line at the top spans from point A to point D, labeled 'The heavy line indicates a "connection through the international exchange"'. Below the diagram, arrows indicate the 'International line' entering from the left and exiting to the right, and the 'International circuit' paths between points A and B, and between points C and D. The code 'CCITT-48451' is in the bottom right corner. + +Diagram of an international exchange showing equipment blocks 1, 2, and 3, with points X, A, B, C, D, and Y marked. A heavy line indicates a 'connection through the international exchange' between points A and D. Arrows indicate 'International line' and 'International circuit' paths. + +- 1 = channel translating equipment +- 2 = incoming and outgoing relay set +- 3 = automatic switching equipment + +*Note* – Between points X and A and points D and Y, there may be equipment such as echo suppressors, compandors, equalizers, line signal receivers, etc., in addition to the cabling. + +FIGURE 1/Q.45 +International exchange + +1) The transmission characteristics of a digital international exchange are specified in Recommendation Q.507. + +1.2 The essential transmission requirements for an international exchange are: + +- a) The *transmission loss* through the centre should be substantially constant with time and independent of the routing through the centre. +- b) *Crosstalk and noise* should be negligible. +- c) The *distortions* introduced should be small. These include attenuation distortion, non-linear distortion and intermodulation products. +- d) *Impedance and balance with respect to earth* at the points in the international exchange to which the lines are connected should be closely controlled. + +1.3 The following recommendations apply to new automatic 4-wire international exchanges of the electro-mechanical type. It is desirable that they should apply to new national 4-wire exchanges. They may also be applicable to electronic exchanges having metallic contact crosspoints. + +These recommendations are intended to be used only as type tests, acceptance tests, or for special investigations. They do not constitute a complete specification. Generally the recommended tests should be conducted on a sampling basis. + +## 2 Definitions + +2.1 *Definition of a “connection through an exchange”* + +Crosstalk and noise conditions for a 4-wire international exchange are defined by reference to a “connection through this exchange”. By **connection through an exchange** is to be understood the pair of wires corresponding to one direction of transmission (GO direction or RETURN direction) and connecting the input point of one circuit incoming in the exchange and the output point of a different circuit outgoing from the exchange (these input or output points are often taken at the test-jack frame). + +A connection through the international exchange is shown by a heavy line in Figure 1/Q.45. + +2.2 *Definition of switching equipment input and output points* + +Although the virtual switching points, which are points at which the two circuits are considered to be directly connected, are theoretical points, in practice it will always be possible to choose a point considered as the *switching equipment input* for the receive channel of a circuit and a point considered as the *switching equipment output* for the transmit channel of a circuit. + +The exact position of each of these points depends on national practice and it is unnecessary for the CCITT to define it. Only the national authority responsible for each international transit centre can fix the position of these points in each case. + +The switching equipment input point associated with a receive channel may be such that the nominal relative level is different from $-4.0$ dBr. Let this nominal relative level be $R^2$ ). + +The switching equipment output point associated with a transmit channel may be such that the nominal relative level is different from $-3.5$ dBr. Let this nominal relative level be $S^2$ ). + +Consider a circuit between the switching centre concerned and the adjacent centre. Let $T$ be the nominal transmission loss between virtual switching points at the two ends of the channel of this circuit, which is the receive channel in the centre concerned. + +When a transit connection is established through a centre by connecting the receive and transmit channels of one circuit to the transmit and receive channels respectively of another circuit, in order to ensure that the virtual switching points have been connected together with additional loss or gain, the *nominal* value of the attenuation (loss) to be introduced between the switching equipment input and the switching equipment output is $R - S + T$ . + +2.3 *Definition of the net switching loss* + +Let the actual value of the attenuation introduced between the switching equipment input and output points be $A$ . The net switching loss is defined to be equal to the difference between this *actual* value and the *nominal* value of the attenuation. Thus: + +$$\begin{aligned}\text{Net switching loss} &= \text{actual loss} - \text{nominal loss} \\ &= A - (R - S + T).\end{aligned}$$ + +--- + +2) If the value of $R$ is chosen to be higher than the value of $S$ , the level difference can be used to offset any inherent transmission loss in the switching equipment and the requirements of the transmission plan can be met without any need to install supplementary audio-frequency amplifiers. + +## 3 Recommendations concerning transmission loss + +### 3.1 Net switching loss + +Ideally, the net switching loss of an international exchange would always be zero. That is, the *actual* loss (*A*) should equal the *nominal* loss ( $R - S + T$ ). + +*Example* – The relationship between the actual switching points and the virtual switching points in a practical international exchange is illustrated in Figure 2/Q.45. In this arrangement: + +$$R = +7 \text{ dBr},$$ + +$$S = -16 \text{ dBr},$$ + +and *T* is assumed to be 0.5 dB + +so that the nominal transmission loss needed between the +7 and -16 dBr points is: + +$$(+7) - (-16) + (0.5) = 23.5 \text{ dB}.$$ + +In practice, different connections established by the switching equipment will introduce different values of net switching loss so that a distribution of net switching losses will arise. The mean value of this distribution should be very close to zero but does not need to be specified. + +### 3.2 Loss dispersion + +According to the Recommendation cited in [2], circuit test-access points are located at or near the switchblock (points B and C of Figure 1/Q.45). Moreover, the dispersion of loss is mainly due to the diversity of paths in the switchblock. It is therefore only necessary to consider the dispersion of loss between the points B and C. + +The standard deviation of loss measured at 800 Hz of all possible paths between points B and C should be as small as possible. For purposes of calculation a value of 0.2 dB may be assumed. + +In order to conform to this value, it is considered sufficient that, for purposes of design and acceptance testing, the difference between the losses at 800 Hz of the shortest and longest paths from point B to point C in no case exceeds 0.8 dB. For a practical assessment of the average value of net switching loss, the contribution from the switchblock can be taken as the mean of the maximum and minimum values of loss between points B and C. + +These values apply for connections routed directly, and once only, through the switchblock. Due to the fact that the switchblock contains only switches and associated cabling, the actual loss between points B and C in any case can only have positive values. + +If special re-entrant trunking arrangements are used, requiring the connection to pass through the switchblock twice (this may be a convenient way to extend the availability of the switching network or to introduce additional equipment, e.g. echo suppressors), the maximum loss and loss dispersion will be increased. In view of this, the re-entrant technique should not be used to such an extent as to increase significantly the mean net switching loss of the exchange. + +### 3.3 Nonlinear distortion + +The transmission loss measured on any “connection through the international exchange” should not vary by more than 0.2 dB when the level of the test-tone is varied from -40 dBm0 to +3.5 dBm0. + +### 3.4 Loss-frequency distortion referred to 800 Hz + +The difference between the transmission loss measured on any “connection through the international exchange” over the frequency bands indicated below and that measured at 800 Hz3), should lie within the following limits: + +$$\begin{aligned} 300-400 \text{ Hz: } & -0.2 \text{ dB to } +0.5 \text{ dB}, \\ 400-2400 \text{ Hz: } & -0.2 \text{ dB to } +0.3 \text{ dB}, \\ 2400-3400 \text{ Hz: } & -0.2 \text{ dB to } +0.5 \text{ dB}. \end{aligned}$$ + +3) 1000 Hz is an acceptable alternative frequency. + +![Figure 2/Q.45: Example showing a simplified representation of a transit connection in an international exchange with actual arrangement and possible location of virtual switching points. The diagram is divided into two parts: (a) Actual arrangement and (b) Hypothetical arrangement. Part (a) shows two parallel lines representing circuits. The top circuit has points R (+7 dBr), S (-16 dBr), and switching points with levels -2.5 dBr and -2 dBr. The bottom circuit has points S (-16 dBr), R (+7 dBr), and switching points with levels -2 dBr and -2.5 dBr. Attenuation values of 9.5 dB and 14 dB are shown between points. Part (b) shows the same circuits with 'Virtual switching points' added. It labels 'International circuit' and 'Receive/Send' points. Attenuation values include T = 0.5 dB, 1.5 dB, and 14 dB. Relative levels at virtual switching points are marked as -3.5 dBr*.](547f726730e589392f239257a833ede3_img.jpg) + +a) Actual arrangement + +b) Hypothetical arrangement indicating possible position of the virtual switching points of the two circuits + +\* These are the only values that are the subject of CCITT Recommendations; the other values are given as examples only. + +CCITT-36870 + +Figure 2/Q.45: Example showing a simplified representation of a transit connection in an international exchange with actual arrangement and possible location of virtual switching points. The diagram is divided into two parts: (a) Actual arrangement and (b) Hypothetical arrangement. Part (a) shows two parallel lines representing circuits. The top circuit has points R (+7 dBr), S (-16 dBr), and switching points with levels -2.5 dBr and -2 dBr. The bottom circuit has points S (-16 dBr), R (+7 dBr), and switching points with levels -2 dBr and -2.5 dBr. Attenuation values of 9.5 dB and 14 dB are shown between points. Part (b) shows the same circuits with 'Virtual switching points' added. It labels 'International circuit' and 'Receive/Send' points. Attenuation values include T = 0.5 dB, 1.5 dB, and 14 dB. Relative levels at virtual switching points are marked as -3.5 dBr\*. + +*Note* – Underlined values of relative level refer to the circuit on the right of the point concerned. Values of relative level not underlined refer to the circuit on the left of the point concerned. In an actual switching centre the virtual switching points would not physically exist. + +FIGURE 2/Q.45 + +Example showing a simplified representation of a transit connection in an international exchange with actual arrangement and possible location of virtual switching points + +## 4 Crosstalk recommendations + +4.1 Crosstalk should be measured in exchanges at a frequency of 1100 Hz in accordance with Recommendation G.134 [3]. + +4.2 *Crosstalk between connections established (between points A and D)* + +In an international 4-wire exchange the signal to crosstalk ratio measured at points A and D between any two “connections through the international exchange” (see definition in § 2.1 above) should be 70 dB or better. + +This limit of 70 dB should normally apply to the most unfavourable case, in which two “connections” have parallel paths throughout the international exchange. It should be noted that this does not occur in practice, because normal cabling layout is such that when, at one switching stage, two “connections” use adjacent switches, in the following stage the two “connections” generally use switches which are not adjacent. + +4.3 *GO to RETURN crosstalk of the same path (between points A and D)* + +The signal-to-crosstalk ratio between the two “connections” which constitute the GO and RETURN channels of a 4-wire path established through the international exchange should be 60 dB or better. + +## 5 Noise recommendations + +For a 4-wire international exchange, noise measurements should be performed on a “connection through the exchange” during the busy-hour. (The *busy-hour* is defined in [4].) Each channel of the connection should be terminated at points A and D of Figure 1/Q.45, in 600 ohms. The noise should be measured at the downstream end of each channel and should be referred to a point zero relative level in that channel. Thus, in Figure 1/Q.45 the noise in the upper channel is measured at D and the noise in the lower channel is measured at A. + +### 5.1 Mean noise power during the busy-hour + +The mean of the noise over a long period during the busy-hour should not exceed the following values: + +- Psophometrically weighted noise: $-67 \text{ dBm0p}$ ( $200 \text{ pW0p}$ ), +- Unweighted noise: $-40 \text{ dBm0}$ ( $100\,000 \text{ pW0}$ ) measured with a device with a uniform response curve throughout the band $30\text{--}20\,000 \text{ Hz}$ . + +*Note* – A sufficient variety of connections should be chosen to ensure that the measurements are representative of the various possible routes through the exchange. + +### 5.2 Impulsive noise during the busy-hour + +Noise counts should not exceed 5 counts in 5 minutes at a threshold level of $-35 \text{ dBm0}$ (see Annex A to this Recommendation for measurement procedure). + +*Note* – Figure 3/Q.45 shows the maximum number of impulsive noise counts acceptable on a 5-minute period. + +![Figure 3/Q.45: Impulsive noise requirements for 4-wire exchanges. A log-log graph showing the average number of impulsive noise counts per 5 minutes (y-axis, 0.1 to 100) versus threshold level in dBm0 (x-axis, -50 to 0).](797231cfee084ca299de599340240401_img.jpg) + +The graph plots the average number of impulse noise counts per 5 minutes (logarithmic scale from 0.1 to 100) against the threshold level in dBm0 (linear scale from -50 to 0). It identifies specific requirement zones: + +- Recommendation Q.45:** Represented by a solid black rectangular area. The limit is 5 counts at a threshold level of $-35 \text{ dBm0}$ . +- Recommendation V.53, § 4 [5]:** Represented by a hatched rectangular area. The limit is 8 counts at a threshold level of $-21 \text{ dBm0}$ . +- For special quality leased circuits:** A further hatched area is shown to the right of the V.53 region, extending towards higher threshold levels. + +The graph is identified by the code CCITT-48462. + +Figure 3/Q.45: Impulsive noise requirements for 4-wire exchanges. A log-log graph showing the average number of impulsive noise counts per 5 minutes (y-axis, 0.1 to 100) versus threshold level in dBm0 (x-axis, -50 to 0). + +FIGURE 3/Q.45 +**Impulsive noise requirements for 4-wire exchanges** + +## 6 Other transmission recommendations + +### 6.1 *Intermodulation products (measured at A and D)* + +The intermodulation products to be taken into account for end-to-end multifrequency signalling and for data transmission are those of the third order, of type $(2f_1 - f_2)$ and $(2f_2 - f_1)$ where $f_1$ and $f_2$ are two signalling frequencies. + +For a measurement of the intermodulation products, the two frequencies to be used are 900 Hz and 1020 Hz (see [6]). With each frequency $f_1$ and $f_2$ at a level of $-6$ dBm0, the difference between the level of either frequency $f_1$ or $f_2$ and the level of either of the intermodulation products at $(2f_1 - f_2)$ or $(2f_2 - f_1)$ should be at least 40 dB. + +### 6.2 *Group delay distortion (measured between A and D)* + +The group delay distortion measured on any “connection through the international exchange” over the band 600-3000 Hz should not exceed 100 microseconds. + +### 6.3 *Return loss (measured at A and D, from A towards D and from D towards A)* + +At any frequency from 300-600 Hz the return loss measured against 600 ohms should be not less than 15 dB. The corresponding value from 600-3400 Hz should be not less than 20 dB. + +### 6.4 *Impedance unbalance to earth* + +6.4.1 The impedance unbalance to earth measured, at points A and D, should not be worse than: + +300- 600 Hz: 40 dB; + +600-3400 Hz: 46 dB. + +*Note* – Some Administrations guided by their knowledge of local conditions may feel a need to specify a figure for a lower frequency, for instance, 50 Hz. + +6.4.2 The degree of unbalance to earth is defined as the ratio $u/U$ measured as shown in a) and b) of Figure 4/Q.45 and is expressed in decibels as the reciprocal of this ratio in transmission units. + +The diagrams of Figure 4/Q.45 used for measurement of unbalance differ only in respect of the presence or absence of an earth at the mid-point of the termination. Unbalance measurements according to a) and b) of Figure 4/Q.45 can give quite different results according to the nature of the unbalance. + +6.4.3 The CCITT has recommended in 1968 that the set of limit values of § 6.4.1 above should be met for unbalance to earth measured with *both* measuring diagrams according to Figure 4/Q.45. + +## 7 Use of cables specified by the IEC + +The cables for telephone exchanges in accordance with the IEC (International Electrotechnical Commission) publication cited in [7] will meet the electrical characteristics required by the CCITT (especially as regards crosstalk) for ordinary exchanges, but this may no longer hold good for larger exchanges with considerable lengths of cable. + +In accordance with Recommendation G.231 [8], it will be for the Administrations or the contractors to check whether standard cables will be satisfactory in equipping an exchange which requires telephone cables of exceptional length. + +![Two circuit diagrams, (a) and (b), showing the measurement of unbalance to Earth. Both diagrams feature a central 'Equipment being tested' block. On the left side, two 300 Ω resistors are connected in series between the top and bottom lines, with a measuring unit 'U' connected in parallel across them and grounded. On the right side, two 300 Ω resistors are similarly connected, with a measuring unit 'U' connected across them. Arrows indicate the direction of measurement. Diagram (b) includes the text 'CCITT-48472'.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Two circuit diagrams, (a) and (b), showing the measurement of unbalance to Earth. Both diagrams feature a central 'Equipment being tested' block. On the left side, two 300 Ω resistors are connected in series between the top and bottom lines, with a measuring unit 'U' connected in parallel across them and grounded. On the right side, two 300 Ω resistors are similarly connected, with a measuring unit 'U' connected across them. Arrows indicate the direction of measurement. Diagram (b) includes the text 'CCITT-48472'. + +FIGURE 4/Q.45 +Measurement of the degree of unbalance to Earth + +## ANNEX A + +(to Recommendation Q.45, § 5.2) + +### Procedure for impulsive noise measurements + +A.1 A test circuit should be formed by setting up a connection across the switching unit and terminating the connection on one side of the exchange by the appropriate closing impedance and on the other by the impulse measuring device in parallel to the closing impedance. Those terminating points should be points A and D in the diagram of Figure 1/Q.45 (or equivalent points) to include the switching equipment of the exchange. Where it is the desire of an Administration, measurements may be made at points X and Y if precautions are taken to ensure that the results apply only to the automatic switching equipment, signalling equipment, echo suppressors, relay sets, pads and cabling of the exchange. + +A.2 The measurements should be made using the device specified in Recommendation O.71 [9]. The 600-3000 Hz filter network described in [10] should be in the circuit. + +A.3 The measurements should be made at times when the probability of noise occurring is at its highest, that is normally during the busy-hour. + +A.4 The time of observation for each test should be five minutes. + +*Note* – The number of different test circuits set up across the exchange for measuring should take into account the size and complexity of the switching unit and should be a number sufficient to represent the various possible types of calls and routes through the exchange. + +See also the document cited in [11]. + +## References + +- [1] CCITT Recommendation *Definitions for the maintenance organization*, Vol. IV, Rec. M.700. +- [2] CCITT Recommendation *Four-wire switched connections and four-wire measurements on circuits*, Vol. IV, Rec. M.640, § 2. +- [3] CCITT Recommendation *Linear crosstalk*, Vol. III, Rec. G.134. +- [4] CCITT Definitions: *Busy hour*, Vol. X, Fascicle X.1 (Terms and Definitions). +- [5] CCITT Recommendation *Limits for the maintenance of telephone-type circuits used for data transmission*, Vol. VIII, Rec. V.53, § 4. +- [6] CCITT Recommendation *Characteristics of compandors for telephony*, Vol. III, Rec. G.162, § 5.2. +- [7] Publication 189 of the I.E.C. +- [8] CCITT Recommendation *Arrangement of carrier equipment*, Vol. III, Rec. G.231. +- [9] CCITT Recommendation *Specification for an impulsive noise measuring instrument for telephone-type circuits*, Vol. IV, Rec. O.71. +- [10] *Ibid.*, § 3.5. +- [11] *Measurements of impulsive noise in a four-wire telephone exchange*, Green Book, Vol. VI-4, Supplement No. 7, ITU, Geneva, 1973. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.5009-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/Q/T-REC-Q.5009-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.5009-202406-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..644a0d10ead2f1bdc52e085f27dee5adfbb879d5 --- /dev/null +++ b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:257004c9063965af1ac2d004655c01e8428699c0c1073e263f76a71ccfd39318 +size 90357 diff --git a/marked/Q/T-REC-Q.5009-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..154617713185e0bc3daf6f5477b7eaf11aaa7843 --- /dev/null +++ b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cd011fe9c9e7636f27dd464a415e73ad64093a06e6b88b84675c7a0f6b8ff3c +size 71524 diff --git a/marked/Q/T-REC-Q.5009-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ef224627f13949f35451de8cb160012b4f46f81 --- /dev/null +++ b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00d966f67f7cdcfdb72ad948ee289c85ac8f4ced05df4a2659d461619007e4fb +size 49308 diff --git a/marked/Q/T-REC-Q.5009-202406-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33651bc2255e74b503fa93a2fd682accbe4e5fe6 --- /dev/null +++ b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b9a6de23a2c64cdd4206790295fa42c6ed0014c024a0bc09ff325605821d8e5 +size 84369 diff --git a/marked/Q/T-REC-Q.5009-202406-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6db5461801e7761e6aa759573296fd549fd3bca --- /dev/null +++ b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:137feb5d0ac30dea7d4f051ef0a0b0337c69115a3e20f31e20baddabcb7e8669 +size 80389 diff --git a/marked/Q/T-REC-Q.5009-202406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0c51796cb056e12fe5b80a1100b938b99a366362 --- /dev/null +++ b/marked/Q/T-REC-Q.5009-202406-I_PDF-E/raw.md @@ -0,0 +1,587 @@ + + +# Recommendation **ITU-T Q.5009 (06/2024)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Signalling requirements and protocols for IMT-2020 – +Signalling requirements and architecture of IMT-2020 + +--- + +## **Signalling requirements and protocols for enhanced quality assured connections in IMT-2020 networks and beyond** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +### Switching and signalling, and associated measurements and tests + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| 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.5009 + +# Signalling requirements and protocols for enhanced quality assured connections in IMT-2020 networks and beyond + +## Summary + +Recommendation ITU-T Q.5009 specifies the signalling requirements, signalling flows and message format for enhanced quality assured connections in IMT-2020 networks and beyond. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.5009 | 2024-06-29 | 11 | 11.1002/1000/15975 | + +## Keywords + +Connection service assurance, enhanced mobility, IMT-2020 networks. + +--- + +\* 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 ..... | 3 | +| 6.1 General ..... | 3 | +| 6.2 Scenario requirements ..... | 4 | +| 7 Signalling requirements for enhanced quality assured connections in IMT-2020 networks and beyond ..... | 4 | +| 7.1 General ..... | 4 | +| 7.2 Signalling requirements for enhanced mobility ..... | 5 | +| 8 Signalling flows ..... | 6 | +| 8.1 Enhanced quality of connection service assurance ..... | 6 | +| 8.2 Enhanced quality of the high reliability ..... | 8 | +| 9 Message format..... | 9 | +| 9.1 Enhanced quality of connection service assurance ..... | 9 | +| 9.2 Enhanced quality of the high reliability ..... | 10 | +| Bibliography..... | 13 | + + + +# Recommendation ITU-T Q.5009 + +# Signalling requirements and protocols for enhanced quality assured connections in IMT-2020 networks and beyond + +## 1 Scope + +This Recommendation specifies the signalling requirements, signalling flows and message format for enhanced quality assured connections in IMT-2020 networks and beyond. + +This Recommendation addresses the following aspects of enhanced quality assured connections in IMT-2020 networks and beyond: + +- Overview; +- Signalling requirements; +- Signalling flows; +- Message format. + +# 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.3102] Recommendation ITU-T Y.3102 (2018), *Framework of the IMT-2020 network*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 IMT-2020** [b-ITU-T Y.3100]: Systems, system components, and related technologies that provide far more enhanced capabilities than those described in [b-ITU-R M.1645]. + +NOTE – [b-ITU-R M.1645] defines the framework and overall objectives of the future development of IMT-2000 and systems beyond IMT-2000 for the radio access network. + +**3.1.2 control plane** [b-ITU-T Y.2011]: The set of functions that controls the operation of entities in the stratum or layer under consideration, plus the functions required to support this control. + +**3.1.3 data plane** [b-ITU-T Y.2011]: The set of functions used to transfer data in the stratum or layer under consideration. + +**3.1.4 user plane** [b-ITU-T Y.2011]: A synonym for data plane. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------------|--------------------------------------------------| +| AN | Access Network | +| ARP | Address Resolution Protocol | +| DNN | Data Network Name | +| eMBB | enhanced Mobile Broadband | +| IMT-2000 | International Mobile Telecommunication 2000 | +| IMT-2020 | International Mobile Telecommunication 2020 | +| IMT Advanced | International Mobile Telecommunications-Advanced | +| MMF | Mobility Management Function | +| MTC | Machine Type Communication | +| NACF | Network Access Control Function | +| NF | Network Function | +| NFR | Network Function Registry | +| PCF | Policy Control Function | +| PDU | Protocol Data Unit | +| QFI | Quality Flow Indicator | +| QoS | Quality of Service | +| RAN | Radio Access Network | +| RP | Reference Point | +| SLA | Service Level Agreement | +| SMF | Session Management Function | +| SQI | Quality Identification | +| UE | User Equipment | +| UP | User Plane | +| UPF | User Plane Function | +| URLLC | Ultra-Reliable low-delay Communication | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Overview + +## 6.1 General + +The IMT-2020 network provides a variety of services over network and computing infrastructure, including enhanced mobile broadband (eMBB) services, services based on large-scale machine type communication (MTC) and services based on ultra-reliable low-delay communication (URLLC). It can support large-scale network access, flexible connectivity and topology, fixed/mobile convergence, and user plane optimization. Meanwhile, the IMT-2020 network has many features that can help improve the efficiency and flexibility of network services, such as distributed architecture based on software-based network functions, software-defined networking, access network agnostic common core network, network slicing, intelligent resource management, etc. + +The IMT-2020 networks include core network, access network, user equipment, application function and data networks. The functional parts of the IMT-2020 network, except for the application function, are divided into control plane and data plane. As shown in Figure 6-1, considering the framework of the IMT-2020 network defined in [ITU-T Y.3102], the IMT-2020 network provides different network services by using different access networks, core networks and functional entities. + +![Figure 6-1 – Framework in the IMT-2020 network. The diagram shows the architecture of the IMT-2020 network, including the User Equipment (UE), Access Network (AN), Core Network (CN), and Data Networks. The CN is divided into Control plane and User plane. The Control plane includes the IMT-2020 core network with Capability exposure function, Network function registry, Policy control function, Unified subscription management function, and Application function. The User plane includes Network access control function, Network slice selection function, Auth. server function, and Session management function. Signalling flows are shown between UE and CN, and AN and CN. Data transport flows are shown between UE and AN, and AN and CN.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +The diagram illustrates the framework of the IMT-2020 network. It is divided into three main components: User Equipment (UE), Access network (AN), and Core network (CN). The CN is further divided into Control plane and User plane. The Control plane contains the IMT-2020 core network, which includes five functions: Capability exposure function, Network function registry, Policy control function, Unified subscription management function, and Application function. The User plane contains four functions: Network access control function, Network slice selection function, Auth. server function, and Session management function. Signalling flows are indicated by dashed arrows: UE-CN signalling and AN-CN signalling. Data transport flows are indicated by solid arrows: UE-AN data transport and AN-CN data transport. The AN connects to the CN, which in turn connects to Data networks. A stack of three 'User' icons is shown above the User plane functions. A small label 'Q.5009(24)' is in the bottom right corner. + +Figure 6-1 – Framework in the IMT-2020 network. The diagram shows the architecture of the IMT-2020 network, including the User Equipment (UE), Access Network (AN), Core Network (CN), and Data Networks. The CN is divided into Control plane and User plane. The Control plane includes the IMT-2020 core network with Capability exposure function, Network function registry, Policy control function, Unified subscription management function, and Application function. The User plane includes Network access control function, Network slice selection function, Auth. server function, and Session management function. Signalling flows are shown between UE and CN, and AN and CN. Data transport flows are shown between UE and AN, and AN and CN. + +Figure 6-1 – Framework in the IMT-2020 network + +Traditional connectivity services struggle to meet the demands of enterprise users for high-speed access, secure interconnection, service isolation and flexible networking. Considering the different access networks with varying connection requirements, ensuring service level agreement (SLA) service quality has become a high priority. Nowadays, there are numerous applications that require terminal mobility, such as mobile office and media broadcast scenarios. In these scenarios, it is essential to support data transmission quality via not only IMT-2020 AN but also other ANs (such as IMT-2000 or IMT Advanced). Therefore, flexible switching between different ANs is necessary to guarantee high-quality and high-reliability service transmission when switching between different ANs. Currently, signalling quality is enhanced by using quality of service (QoS) and slicing technologies to ensure large bandwidth, strong isolation and high reliability of services. + +The IMT-2020 network is supposed to enhance network connection quality to support terminal mobility and ensure reliable transmission. It supports non-IMT-2020 network access modes and facilitates active-passive disaster recovery switchover. In cases of switching between multiple access + +modes and recovery switchover from network faults, seamless switchover is implemented to ensure service transmission quality. + +## **6.2 Scenario requirements** + +### **6.2.1 Scenario requirements for enhanced mobility** + +In mobile office and other scenarios, it is necessary to realize flexible switching between various network access modes while ensuring the differentiated service quality of the network. + +To support the enhancement of mobility capability in IMT-2020 networks and future networks, policies can be implemented through the network access control function (NACF). This enables flexible switching between IMT-2020 AN and other ANs (such as IMT-2000 or IMT Advanced). Enhancing the internal signalling interactions between NACF and the session management function (SMF) is required to effectively report pertinent information. By improving the interactions among the aforementioned function modules, it is possible to enhance QoS and optimize other parameters when interfacing between different ANs, such as IMT-2000 or IMT Advanced, and the IMT-2020 network. This will result in a high-quality and flexible handoff of network access, ensuring seamless transitions for users across various ANs. + +### **6.2.2 Scenario requirements for enhanced reliability** + +For end-to-end network connection, it is usually necessary to support active-passive disaster recovery to ensure the high reliability of service quality. The service flow on the data plane extends from the base station to the IMT-2020 user plane function (UPF) through the fixed network segment. In the event of a fault of the active UPF, ensuring the uninterrupted forwarding of service flows is imperative to achieve high end-to-end network reliability in the active/standby UPF disaster recovery scenario, which involves session switchover. + +# **7 Signalling requirements for enhanced quality assured connections in IMT-2020 networks and beyond** + +## **7.1 General** + +Figure 7-1 shows the core network functions of the IMT-2020 network and highlights enhancements of the functionalities of SMF. These enhancements include improving interaction between SMF and QoS mapping function, enhancing mobility management communication between IMT-2020 network and other ANs (such as IMT-2000 or IMT Advanced), and improving reliability communication between SMF and UPF. As the core function of session management within the IMT-2020 network, the policy control function (PCF) is responsible for interacting with the access and mobility policy enforcement in NACF and the mobility management function (MMF), and provides the associated policies. The SMF is responsible for tunnel maintenance, IP address allocation and management, policy enforcement, QoS control, roaming, etc. It selects and manages the UPF, configures UPF traffic and direction, and forwards the traffic to the appropriate destination network. + +![Figure 7-1: Signalling architecture for enhanced quality in IMT-2020 networks and beyond. The diagram shows the flow of signalling between a UE, RAN, NACF, Enhanced-SMF, UPF, Data networks, and an Other network (IMT-2000/IMT advanced).](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram illustrates the signalling architecture for enhanced quality in IMT-2020 networks and beyond. It shows the following components and their interactions: + +- UE (User Equipment)** connects to **RAN (Radio Access Network)**. +- RAN** connects to **NACF (Network Access Function)** within the **IMT-2020 network**. +- NACF** has three reference points: + - RP-ns** connects to the **Enhanced-SMF**. + - RP-nm** connects to the **Mobility management function** in the **Other network (IMT-2000/IMT advanced)**. + - RP-sm** connects to the **Local domain name server function** in the **Other network (IMT-2000/IMT advanced)**. +- The **Enhanced-SMF** contains: + - SMF (Session Management Function)**. + - RP-sq** reference point connecting to the **UPF**. + - QoS mapping function**. +- UPF (User Plane Function)** connects to **Data networks** via the **RP-ud** reference point. +- The **Other network (IMT-2000/IMT advanced)** contains: + - Mobility management function**. + - Local domain name server function**. + +Figure 7-1: Signalling architecture for enhanced quality in IMT-2020 networks and beyond. The diagram shows the flow of signalling between a UE, RAN, NACF, Enhanced-SMF, UPF, Data networks, and an Other network (IMT-2000/IMT advanced). + +Q.5009(24) + +**Figure 7-1 – Signalling architecture for enhanced quality in IMT-2020 networks and beyond** + +When the user equipment (UE) accesses the IMT-2020 network, it initially connects to the first core network. If the UE moves into the coverage area of other networks access, it connects to the second core network. NACF of the first core network and the mobility management function (MMF) of the second core network interact with each other based on the fallback information of the target terminal. This fallback information includes session information of the target terminal. The SMF of the first core network receives the fallback information sent by the MMF. To enhance the mobility and reliability of the IMT-2020 network, it is required to improve communication capabilities of SMF and add the QoS mapping function. This addition is crucial to meet the flexible migration requirements of the IMT-2020 network and other network services. The SMF is required to obtain user information of the target terminal based on the session information and query the target QoS mapping strategy from the pre-stored QoS mapping strategy based on the user information after the target terminal switches to the target network. Subsequently, the target QoS mapping strategy is pushed down to the target terminal. To prevent service flow forwarding anomalies caused by UPF failures, the main and standby UPF disaster recovery mechanism is adopted. The communication processes and session detection of SMF and UPF are enhanced to achieve the synchronous switching of sessions and routes, enabling service-level main/standby UPF disaster recovery. + +## 7.2 Signalling requirements for enhanced mobility + +### 7.2.1 Signalling requirements for enhanced quality of connection service assurance + +To achieve enhanced quality of connection service assurance of the IMT-2020 network and realize flexible switching between various access modes and guarantee its network service quality, the following capabilities are required: + +- **Quality of service assurance:** The communication mechanism through signalling of the RP-sq reference points is required to support service-level quality of service assurance and realize QoS mapping between different network access modes. The pre-stored QoS mapping policies are categorized based on service types. These policies entail the correspondence between various QoS parameters and then the terminal performs network switching. The QoS parameters primarily encompass service quality identification, address resolution protocol (ARP), preemption attribute, preempted attribute, and upstream and downstream bit rate information. + +### 7.2.2 Signalling requirements for enhanced mobility management + +To enhance the mobility guarantee of the IMT-2020 network and realize flexible switching between various access modes, the following capabilities are required: + +- Mobility management: The RP-ns reference point and the RP-nm reference point are required to support seamless migration between IMT-2020 AN and other ANs. +- Session state maintenance: The communication mechanism through signalling of the RP-sm reference point is required to support the ability to maintain the state of the session. + +### 7.2.3 Signalling requirements for the high reliability of connection service assurance + +To enhance the high reliability of connection service assurance and support the active/standby user disaster recovery scenario, the following capabilities of the first interface (namely RP-su) of the main UPF and the second interface (namely RP-ud) of the user plane function are required: + +- **Support user plane redundancy transmission based on dual connections:** The RP-su reference point is required to support the session communication between the main UPF and SMF, which provides redundant user plane resources for a given protocol data unit (PDU) session through dual connections. It also supports Ethernet PDU session anchor recovery. +- **Support redundant data network transmission:** RP-ud is required to implement communication between the main UPF and the gateway device. The RP-ud reference point and the RP-su reference point are required to be bound to the PDU session, enabling the monitoring of the operational status of the RP-su and RP-ud. + +NOTE – This monitoring of UPF involves adding a session exception reporting process in the signalling flow to facilitate session monitoring and dynamic switching of service flows. + +# 8 Signalling flows + +## 8.1 Enhanced quality of connection service assurance + +### 8.1.1 Connected state to support quality of service assurance + +Figure 8-1 shows the signalling flow for supporting quality of service assurance during connected state. + +![Sequence diagram showing signalling flows for connected state to support quality of service assurance. The diagram involves seven entities: UE, RAN, MMF, NACF, SMF, QS mapping function, and UPF. The sequence of messages is: 1. Session establishment request (UE to UPF); 2. Deliver the user IP address (UPF to SMF); 3. Activation successful (SMF to RAN); 4. Transmission tunnel established (RAN to UPF); 5. Nacf_Notification_Request in connected state (SMF to NACF); 6. Nacf_Notification_Response (NACF to SMF); 7. Report to SMF (SMF to NACF); 8. Nsmf_QoS Mapping_Request (SMF to QS mapping function); 9. Nsmf_QoS Mapping_Response (QS mapping function to SMF); 10. Deliver QoS policy (SMF to RAN); 11. Service message transmission (RAN to UE).](fbfa653853daf5541118a9ddecb92284_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant MMF + participant NACF + participant SMF + participant QS as QS mapping function + participant UPF + + Note over UE, UPF: 1. Session establishment request + Note over SMF, UPF: 2. Deliver the user IP address + Note over RAN, SMF: 3. Activation successful + Note over RAN, UPF: 4. Transmission tunnel established + Note over SMF, NACF: 5. Nacf_Notification_Request in connected state + Note over NACF, SMF: 6. Nacf_Notification_Response + Note over SMF, NACF: 7. Report to SMF + Note over SMF, QS: 8. Nsmf_QoS Mapping_Request + Note over QS, SMF: 9. Nsmf_QoS Mapping_Response + Note over RAN, SMF: 10. Deliver QoS policy + Note over RAN, UE: 11. Service message transmission + +``` + +Q.5009(24) + +Sequence diagram showing signalling flows for connected state to support quality of service assurance. The diagram involves seven entities: UE, RAN, MMF, NACF, SMF, QS mapping function, and UPF. The sequence of messages is: 1. Session establishment request (UE to UPF); 2. Deliver the user IP address (UPF to SMF); 3. Activation successful (SMF to RAN); 4. Transmission tunnel established (RAN to UPF); 5. Nacf\_Notification\_Request in connected state (SMF to NACF); 6. Nacf\_Notification\_Response (NACF to SMF); 7. Report to SMF (SMF to NACF); 8. Nsmf\_QoS Mapping\_Request (SMF to QS mapping function); 9. Nsmf\_QoS Mapping\_Response (QS mapping function to SMF); 10. Deliver QoS policy (SMF to RAN); 11. Service message transmission (RAN to UE). + +Figure 8-1 – Connected state to support quality of service assurance + +1. UE initiates an activation request, requesting the establishment of a session. SMF sends the activation request to UPF. +2. UPF assigns and issues an IP address to the terminal. +3. UE activation is successful. +4. User plane channel is successfully established. +5. If UE is in a connected state and moves from the IMT-2020 access network area to other ANs (such as IMT-2000 or IMT Advanced), NACF sends a fallback notification to MMF with information regarding the terminal's fallback, by invoking Nacf\_Notification\_Request in connected state, including SMF information, user context information and bearer information. +6. NACF receives the fallback response information (Nacf\_Notification\_Response) sent by MMF. +7. MMF reports the fallback information to SMF. +8. SMF sends the Nsmf\_QoS Mapping\_Request to the QoS mapping function. +9. The QoS mapping function responds to SMF with the Nsmf\_QoS Mapping\_Response, carrying QoS mapping policies and parameter information, including QoS parameters such as service quality identification (SQI), address resolution protocol (ARP), preemption attribute, preempted attribute and uplink/downlink bit rates. +10. SMF delivers the obtained QoS policies to NACF, RAN and UE. +11. UE transmits the service message carrying the QoS policy information. + +### 8.1.2 Idle state to support quality of service assurance + +Figure 8-2 shows the signalling flow for supporting quality of service assurance during idle state. + +![Sequence diagram showing the signalling flow for supporting quality of service assurance during idle state. The diagram involves seven entities: UE, RAN, MMF, NACF, SMF, QS mapping function, and UPF. The sequence of messages is: 1. Session establishment request (UE to UPF); 2. Deliver the user IP address (UPF to SMF); 3. Activation successful (SMF to UE); 4. Transmission tunnel established (SMF to UPF); 5. Nacf_Notification_Request in idle state (NACF to MMF); 6. Nacf_Notification_Response (MMF to NACF); 7. Report to SMF (MMF to SMF); 8. Nsmf_QoS Mapping_Request (SMF to QS mapping function); 9. Nsmf_QoS Mapping_Response (QS mapping function to SMF); 10. Deliver QoS policy (SMF to RAN and UE); 11. Service message transmission (UE to UPF).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant MMF + participant NACF + participant SMF + participant QS_mapping_function as QS mapping function + participant UPF + + Note over UE, UPF: 1. Session establishment request + Note over SMF, UPF: 2. Deliver the user IP address + Note over UE, SMF: 3. Activation successful + Note over SMF, UPF: 4. Transmission tunnel established + Note over NACF, MMF: 5. Nacf_Notification_Request in idle state + Note over MMF, NACF: 6. Nacf_Notification_Response + Note over MMF, SMF: 7. Report to SMF + Note over SMF, QS_mapping_function: 8. Nsmf_QoS Mapping_Request + Note over QS_mapping_function, SMF: 9. Nsmf_QoS Mapping_Response + Note over SMF, RAN, UE: 10. Deliver QoS policy + Note over UE, UPF: 11. Service message transmission + +``` + +Q.5009(24) + +Sequence diagram showing the signalling flow for supporting quality of service assurance during idle state. The diagram involves seven entities: UE, RAN, MMF, NACF, SMF, QS mapping function, and UPF. The sequence of messages is: 1. Session establishment request (UE to UPF); 2. Deliver the user IP address (UPF to SMF); 3. Activation successful (SMF to UE); 4. Transmission tunnel established (SMF to UPF); 5. Nacf\_Notification\_Request in idle state (NACF to MMF); 6. Nacf\_Notification\_Response (MMF to NACF); 7. Report to SMF (MMF to SMF); 8. Nsmf\_QoS Mapping\_Request (SMF to QS mapping function); 9. Nsmf\_QoS Mapping\_Response (QS mapping function to SMF); 10. Deliver QoS policy (SMF to RAN and UE); 11. Service message transmission (UE to UPF). + +**Figure 8-2 – Idle state to support quality of service assurance** + +1. The UE initiates an activation request, requesting to establish a session. SMF sends the activation request to UPF. +2. UPF assigns and issues an IP address to the terminal. + +3. UE activation is successful. +4. The user plane channel is established successfully. +5. When the UE moves from IMT-2020 access network area to another access network (such as IMT-2000 or IMT Advanced) in idle mode, NACF receives a fallback request from MMF for the target terminal sent by the MMF. The fallback request includes fallback information, by invoking Nacf\_Notification\_Request in idle state, which includes SMF information for the connection, user context information and bearer information. +6. NACF sends a fallback response message to MMF by invoking Nacf\_Notification\_Response. +7. MMF reports the fallback information to SMF. +8. SMF sends the Nsmf\_QoS Mapping\_Request to the QoS mapping function. +9. The QoS mapping function returns the Nsmf\_QoS Mapping\_Response to SMF, carrying QoS mapping policies and parameter information. QoS parameters include service quality identification, address resolution protocol (ARP), preemptive attributes, preempted attributes, and uplink and downlink bit rate information. +10. SMF transfers the obtained QoS policy to NACF, RAN and UE. +11. The UE transmits the business message carrying QoS policy information. + +## 8.2 Enhanced quality of the high reliability + +Figure 8-3 shows the signalling flow for supporting high reliability of connection service assurance. + +![Sequence diagram showing the signalling flow for supporting high reliability of connection service assurance. The diagram involves seven entities: UE, RAN, NACF, SMF, UPF (Standby-UPF), UPF (Main-UPF), and DN. The sequence of messages is: 1. Path switch request (from RAN to DN); 2. PDU session update request (from NACF to SMF); 3. PDU session modification request (from SMF to UPF (Main-UPF)); 4. PDU session modification response (from UPF (Main-UPF) to SMF); 5. PDU session establishment request (from SMF to UPF (Standby-UPF)); 6. PDU session establishment response (from UPF (Standby-UPF) to SMF); 7. PDU session update response (from SMF to NACF); 8. Path switch response (from DN to RAN). A 'Target UPF select' block is shown between steps 2 and 3, indicating the SMF's selection process.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant NACF + participant SMF + participant UPF_S as UPF (Standby-UPF) + participant UPF_M as UPF (Main-UPF) + participant DN + + Note right of DN: 1. Path switch request + NACF->>SMF: 2. PDU session update request + Note right of SMF: Target UPF select + SMF->>UPF_M: 3. PDU session modification request + UPF_M-->>SMF: 4. PDU session modification response + SMF->>UPF_S: 5. PDU session establishment request + UPF_S-->>SMF: 6. PDU session establishment response + SMF-->>NACF: 7. PDU session update response + Note right of DN: 8. Path switch response + +``` + +Sequence diagram showing the signalling flow for supporting high reliability of connection service assurance. The diagram involves seven entities: UE, RAN, NACF, SMF, UPF (Standby-UPF), UPF (Main-UPF), and DN. The sequence of messages is: 1. Path switch request (from RAN to DN); 2. PDU session update request (from NACF to SMF); 3. PDU session modification request (from SMF to UPF (Main-UPF)); 4. PDU session modification response (from UPF (Main-UPF) to SMF); 5. PDU session establishment request (from SMF to UPF (Standby-UPF)); 6. PDU session establishment response (from UPF (Standby-UPF) to SMF); 7. PDU session update response (from SMF to NACF); 8. Path switch response (from DN to RAN). A 'Target UPF select' block is shown between steps 2 and 3, indicating the SMF's selection process. + +**Figure 8-3 – The high reliability of connection service assurance** + +1. Real-time running status monitoring of the first and second interfaces of the main UPF. When detecting that the running status of one interface of the main UPF is abnormal, NACF initiates a path switching procedure. +2. NACF sends a session update request to the SMF to cut off the other interface of the main UPF and switch to the standby UPF. +3. SMF can select the target UPF when one of the interfaces is abnormal. When detecting that the running status of the first interface of the main UPF is abnormal, the SMF sends a Nsmf\_PDU\_Session\_Modification\_request to the main UPF and cuts off the second interface of the main UPF to switch to the standby UPF. When the running status of the second interface of the main UPF is abnormal, the main UPF sends the session fault notification to + +the SMF, and the SMF initiates PDU session modification procedure to the main UPF, so that the SMF disconnects the first interface connected to the main UPF and anchors the session to the standby UPF. + +4. The main UPF sends the Nsmf\_PDU\_Session\_Modification\_Response to the SMF. +5. The SMF sends Nsmf\_PDU\_Session\_Establishment\_request to the standby UPF and anchors the session to the standby UPF. The SMF provides tunnel information to the standby UPF and instructs the standby UPF to perform packet replication on the downlink QoS traffic through the forwarding rule. +6. The standby UPF sends the Nsmf\_PDU\_Session\_Establishment\_Response to the SMF. +7. The SMF sends the PDU session update response to the NACF. +8. The path switching procedure is complete. + +# 9 Message format + +## 9.1 Enhanced quality of connection service assurance + +NACF sends the fallback notification to MMF with information regarding the terminal's fallback by invoking Nacf\_Notification\_Request. Table 9-1 describes in detail Nacf\_Notification\_Request in connected state. + +**Table 9-1 – Nacf\_Notification\_Request in connected state** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|----------------------------------------------------------------------| +| NACF ID | M | string | 1..N | Indicate the notification in connected state | +| Access type | M | string | 1..N | Indicate the access type of notification | +| PDU session status | O | string | 1..N | Indicate connected state or the idle state of the PDU session status | + +Table 9-2 describes in detail Nacf\_Notification\_Request in idle state. + +**Table 9-2 – Nacf\_Notification\_Request in idle state** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|----------------------------------------------------------------------| +| MMF ID | M | string | 1..N | Indicate the notification in idle state | +| Access type | M | string | 1..N | Indicate the access type of notification | +| PDU session status | O | string | 1..N | Indicate connected state or the idle state of the PDU session status | + +Table 9-3 describes in detail Nacf\_Notification\_Response in connected state and idle state. + +**Table 9-3 – Nacf\_Notification\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the NACF notification:
200 OK
400 Input parameter error
500 Server internal error | + +Table 9-4 describes Nsmf\_QoS Mapping\_Request in detail. + +**Table 9-4 – Nsmf\_QoS Mapping\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|-------------------------------------------------------------------| +| QoS flow identity | M | string | 1..N | Indicates QoS flow descriptions information to be used by the UE | +| Quality flow indicator (QFI) | O | string | 1..N | Indicates the QoS flow identifier. | +| Data network name (DNN) | O | string | 1..N | Indicates data network names being serviced by the UPF. | +| PDU session status | O | string | 1..N | Indicates connected state or idle state of the PDU session status | + +Table 9-5 describes Nsmf\_QoS Mapping\_Response in detail. + +**Table 9-5 – Nsmf\_QoS Mapping\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the NACF notification:
200 OK
400 Input parameter error
500 Server internal error | + +## 9.2 Enhanced quality of the high reliability + +SMF reports the PDU session modification request to UPF by invoking Nsmf\_PDU\_Session\_Modification\_request. Table 9-6 describes Nsmf\_PDU\_Session\_Modification\_request in detail. + +**Table 9-6 – Nsmf\_PDU\_Session\_Modification\_request** + +| Information element | Status | Data type | Cardinality | Description | +|-----------------------------------------|--------|-----------|-------------|---------------------------------------------------------------------------| +| PDU session update information | M | string | 1..N | Indicates PDU session update information including the elected target UPF | +| The port association update information | M | string | 1..N | Indicates the new association between SMF and the target UPF | +| DNN | O | string | 1..N | Indicates data network names being serviced by UPF | +| UPF ID | O | string | 1 | Indicates the identifier of the serving UPF | +| UPF address | O | string | 1 | Indicates the ipv4 or ipv6 address of the serving UPF | +| Service serving area | O | string | 1..N | Indicates the serving area of each updated UPF service instance | + +Table 9-7 describes Nsmf\_PDU\_Session\_Modification\_Response in detail. + +**Table 9-7 – Nsmf\_PDU\_Session\_Modification\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the SMF PDU session modification request.
200 OK
400 Input parameter error
500 Server internal error | + +Table 9-8 describes Nsmf\_PDU\_Session\_Establishment\_request in detail. + +**Table 9-8 – Nsmf\_PDU\_Session\_Establishment\_request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|-----------------------------------------------------------------------------------------------| +| UPF service instance | M | string | 1..N | Indicates the list of UPF service instances registered in the network function registry (NFR) | +| DNN | M | string | 1..N | Indicates the names of the data network being served by the UPF | +| UPF ID | M | string | 1 | Indicates the identifier of the serving UPF | +| UPF address | M | string | 1 | Indicates the ipv4 or ipv6 address of the serving UPF | +| PDU Session ID | M | string | 1..N | Indicates the identifier of the PDU session | + +**Table 9-8 – Nsmf\_PDU\_Session\_Establishment\_request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|-------------------------------------------------------| +| Rules | M | String | 1..N | Indicates rules such as QoS, charging rules, etc. | +| Tunnel parameters | O | string | 1 | Indicates the tunnel parameters that allocated by UPF | + +Table 9-9 describes Nsmf\_PDU\_Session\_Establishment\_Response in detail. + +**Table 9-9 – Nsmf\_PDU\_Session\_Establishment\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the SMF PDU session modification request:
200 OK
400 Input parameter error
500 Server internal error | + +## Bibliography + +- [b-ITU-T Y.2011] Recommendation ITU-T Y.2011 (2004), *General principles and general reference model for Next Generation Networks.* +- [b-ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network.* +- [b-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.* + + + + + +## 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.5012-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/Q/T-REC-Q.5012-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.5012-202406-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3974dd899c11e816032ecd21c4ce79d04bff44ff --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2672e86cd45d58be993d42902d3dbd7e6677172e3155700ea5c56a0442870066 +size 21471 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9df4a2323b3425e469c1b9c4204b1749230c416 --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bd1ae074fa3cb4a57b4cab293db5cc78fc56c32a460a639e1aae500d5731c20 +size 151987 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f58a0fc3f1a6e7ad69675d4cb5da2dcc4e2c641c --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a134369c2c2d91016fa485cf9038a00230fa86584660e7fba252452fcb241b7 +size 84083 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..664bdd19c5705e19f64b9ede2cc4ebd51eb10e99 --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1b038c65e1b01168e05e58f2acd191dd9bce2b87ca452c78ca64b022d20db0d +size 65037 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3f31dcd6eee886cbe525879370ba9ff33389acc --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f80e5648ab5d08499d3a9f48612056f7114241fa15facb1c0775f07c63294379 +size 9657 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0558b3dbf99314a9b765815452379ebb48383c9 --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0a8fcb1b4a40812b7f4bd8f7ee8b689d1297778bb394d8bf05ba64eb2ab38ec +size 65476 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..558e1815a6594f8b8f0f2b551336baf91bcc21da --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56cb89c303211e3955076a14f6e880ff7ad8fa28273faf7309c7abd2e76993c0 +size 48008 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..157618f102de318295760ad7ca3e55b416f08acd --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5603f78fb1c20b2f58279ce7b8605fc2b02ca253d9dac1e068dd967a1536fb2e +size 54849 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cd4f4596da3532569cd478aeafcb21ee8d15b4c --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e19c19a4b1d406a92ac373011e8d8017ffcb2263fc766cd035ab0522a2c2bf23 +size 65042 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60018bea26a2f9d9ce3ebd0981cf69b684769568 --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f76669dd32f70714264656b336e49f531adbb4c510b13b70b5edf2af82794ea +size 61373 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b13408421377a97eef9b839eea366353b28d0969 --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b3bc47e8f45b04fa5dff5e69429bbd92e5330b1d646f3e70cecfce66e247df9 +size 50948 diff --git a/marked/Q/T-REC-Q.5012-202406-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e20ed34916a82f102a2468c8bddc8b31bafe00a --- /dev/null +++ b/marked/Q/T-REC-Q.5012-202406-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be0c4de73c01dcc99cc6aa4ab61c318f3f886a2421cbed2b43379b46ed8df063 +size 22205 diff --git a/marked/Q/T-REC-Q.5021-201907-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5021-201907-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..84a6dd538fdc3d017aa9856be3baaf4eb6992fdf --- /dev/null +++ b/marked/Q/T-REC-Q.5021-201907-I_PDF-E/raw.md @@ -0,0 +1,918 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.5021** + +(07/2019) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for IMT-2020 – +Protocols for IMT-2020 + +--- + +**Protocol for managing capability exposure APIs +in IMT-2020 networks** + +Recommendation ITU-T Q.5021 + +# 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 | +| 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.5021 + +## Protocol for managing capability exposure APIs in IMT-2020 networks + +# Summary + +Recommendation ITU-T Q.5021 describes the protocol for managing capability exposure application programming interfaces (APIs) in International Mobile Telecommunications (IMT)-2020 networks. It includes signalling architecture, API management functions, signalling flows and their message format, and definition for management APIs. It also describes gap analysis and use cases for API management. + +This protocol can be used by network operators and third parties to manage capability exposure APIs. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.5021 | 2019-07-29 | 11 | 11.1002/1000/13980 | + +## Keywords + +Capability exposure, capability exposure APIs, IMT-2020, managing API. + +--- + +\* 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 ..... | 2 | +| 6 | Signalling architecture for API management ..... | 2 | +| 7 | Functions for API management ..... | 3 | +| 7.1 | API registration ..... | 3 | +| 7.2 | API discovery ..... | 3 | +| 7.3 | API authorization..... | 4 | +| 7.4 | API authentication ..... | 4 | +| 7.5 | API deregistration..... | 4 | +| 7.6 | API suspension ..... | 4 | +| 7.7 | API recovery..... | 4 | +| 7.8 | API charging and monitoring ..... | 4 | +| 7.9 | API topology hiding ..... | 4 | +| 7.10 | API location query..... | 5 | +| 8 | Signalling flow..... | 5 | +| 8.1 | API registration procedure ..... | 5 | +| 8.2 | API discovery procedure ..... | 5 | +| 8.3 | API authorization procedure..... | 6 | +| 8.4 | API authentication procedure ..... | 6 | +| 8.5 | API deregistration procedure..... | 7 | +| 8.6 | API suspension procedure ..... | 7 | +| 8.7 | API recovery procedure..... | 8 | +| 8.8 | API charging and monitoring procedure ..... | 9 | +| 8.9 | API topology hiding procedure ..... | 9 | +| 8.10 | API location query procedure..... | 10 | +| 9 | Message format and API definition ..... | 10 | +| 9.1 | CE_API_Registration ..... | 10 | +| 9.2 | CE_API_Discovery ..... | 11 | +| 9.3 | CE_API_Authorization ..... | 12 | +| 9.4 | CE_API_Authentication..... | 12 | +| 9.5 | CE_API_Deregistration..... | 13 | +| 9.6 | CE_API_Suspension ..... | 14 | +| 9.7 | CE_API_Suspension_Notify ..... | 14 | + +| | Page | +|---------------------------------------|------| +| 9.8 CE_API_Recovery ..... | 15 | +| 9.9 CE_API_Recovery_Notify ..... | 16 | +| 9.10 CE_API_Charging_Monitoring ..... | 17 | +| 9.11 CE_API_Topology_Hiding ..... | 17 | +| 9.12 CE_API_Location_Query ..... | 18 | +| Bibliography ..... | 20 | + +## Recommendation ITU-T Q.5021 + +## Protocol for managing capability exposure APIs in IMT-2020 networks + +# 1 Scope + +This Recommendation describes the protocol for managing capability exposure application programming interfaces (APIs) in International Mobile Telecommunications (IMT)-2020 networks. It includes signalling architecture, API management functions, signalling flows and their message format, and definition for management APIs. It also describes gap analysis and use cases for API management. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 IMT-2020** [b-ITU-T Y.3100]: (Based on [b-ITU-R M.2083-0]) Systems, system components, and related technologies that provide far more enhanced capabilities than those described in [b-ITU-R M.1645]. + +**3.1.2 management** [b-ITU-T Y.3100]: In the context of IMT-2020, the processes aiming at fulfilment, assurance, and billing of services, network functions, and resources in both physical and virtual infrastructure including compute, storage, and network resources. + +**3.1.3 network function** [b-ITU-T Y.3100]: In the context of IMT-2020, a processing function in a network. + +**3.1.4 third party (3rd party)** [b-ITU-T Y.3100]: In the context of IMT-2020, with respect to a given network operator and network end-users, an entity which consumes network capabilities and/or provides applications and/or services. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-----------------------------------| +| AF | Application Function | +| API | Application Programming Interface | +| CEF | Capability Exposure Function | + +| | | +|------|--------------------------------------------| +| IMT | International Mobile Telecommunications | +| OA&M | Operations, Administration, and Management | +| UE | User Equipment | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keywords "cardinality" indicate the number of parameter in message. "1" indicates only one parameter while "N" indicates multiple parameter. "1..N" indicates one or more parameters. + +# 6 Signalling architecture for API management + +To avoid duplication and inconsistency of capability exposure APIs to various third-party application functions (AFs), development of a common capability exposure API framework was needed that includes common aspects (e.g., API registration, API discovery, API authorization) that were applicable to any functional APIs when used by a third-party. + +Figure 6-1 shows the architecture model for the capability exposure API management system and the relationship with the capability exposure function (CEF), the third-party application and the IMT-2020 core network functions. + +The capability exposure function provides functionalities to expose its capabilities as a service externally and capability exposure APIs to the third-party. For high-level descriptions of the functionalities and APIs refer to [b-ITU-T Y.IMT2020-CEF]. + +The API management function is mainly responsible for management of the capability exposure API, including API registration, API deregistration, API discovery, API authorization, API authentication, API suspension, API recovery, API charging and monitoring and API topology hiding. + +The IF1 reference point is the southbound interface, which exists between the CEF and the IMT-2020 core network functions. It supports: + +- subscription and unsubscription of network capabilities; +- query and reporting of network capabilities; + +The IF2 reference point is the northbound interface, which exists between the CEF and the third-party application. It supports exposure of network capabilities to the third-party application through the invocation of capability exposure APIs. + +The IF3 reference point is the northbound interface, which exists between the API management function and the third-party application. It supports discovery of capability exposure API. + +The IF4 reference point exists between the CEF and the API management function. It supports: + +- registration and deregistration of capability exposure API; +- invocation event report of capability exposure API; +- suspension and recovery of capability exposure API. + +![Architecture of capability exposure API management system diagram](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the architecture of a capability exposure API management system. At the top, three stacked boxes represent 'Third party applications'. Below them, a large light blue rectangle contains two internal components: 'Capability exposure function' on the left and 'API management function' on the right. These two components are connected by a horizontal line labeled 'IF4'. Above the 'Capability exposure function', a line labeled 'IF2' connects it to the 'Third party applications'. Above the 'API management function', a line labeled 'IF3' connects it to the 'Third party applications'. Below the 'Capability exposure function', a line labeled 'IF1' connects it to a stack of boxes at the bottom labeled 'IMT-2020 core network functions'. The reference code 'Q.5021(19)\_F6-1' is located in the bottom right corner of the diagram area. + +Architecture of capability exposure API management system diagram + +**Figure 6-1 – Architecture of capability exposure API management system** + +# 7 Functions for API management + +## 7.1 API registration + +For the API management function to properly maintain the information of available CEF instances and their supported capability exposure APIs, each CEF instance informs the API management function of the list of capability exposure APIs that it supports. + +The CEF instance may make this information available to API management function when the CEF instance becomes operative for the first time (registration operation) or upon individual CEF service instance activation/de-activation within the CEF instance (update operation), e.g., triggered after a scaling operation. The CEF instance may also update or delete the CEF service related parameters. Alternatively, another authorised entity (such as an operations, administration, and management (OA&M) function) may inform the API management function on behalf of an CEF instance triggered by an CEF service instance lifecycle event (register or de-registration operation depending on instance instantiation, termination, activation, or de-activation). Registration with the API management function includes capacity and configuration information at time of instantiation. + +## 7.2 API discovery + +The API discovery enables the third-party applications to discover a set of CEF instance(s) with specific capability exposure APIs. + +Unless the expected CEF instance and capability exposure APIs information are locally configured on requester third-party applications, the API discovery is implemented via the API management function. + +In order to access to the target CEF instance and get information of target capability exposure API, the requester third-party application initiates the API discovery procedures by providing the specific information of the third-party and APIs. The detailed service parameter(s) used for specific API discovery are defined in clause 9. + +The API management function may provide the IP address or the node name of CEF instance(s) to the requester third-party application. Based on that information, the requester third-party application can select one specific CEF instance that is able to provide a particular capability exposure API. + +## **7.3 API authorization** + +The API authorization is required to ensure the third-party application is authorized to access the capability exposure API provided by CEF, according to the API authorization information. The API authorization information is configured as one of the components in the CEF profile and provide to the API management function during the API registration procedures. It includes the type and other parameters of the third-party application such as the third-party application identity. + +The API management function will check whether the third-party application is permitted to discover the requested capability exposure API during the API discovery procedure according to the API authorization information. + +## **7.4 API authentication** + +The API authentication is required to ensure the mutual authentication between the third-party application and API management function, before the exposure of capability exposure APIs to the third-party application. The authentication method is used to provide integrity protection, replay protection and confidentiality protection via the IF3 reference point. + +The API management function will authenticate the third-party application based on the identity and key of the third-party application. + +## **7.5 API deregistration** + +APIs are required to be deregistered through API management, e.g., the operator may not provide the invocation of the API to third-party applications, the API is about to shutdown or disconnect from the network or API is expired. The API management indicates the deregistration of the API to the CEF. The CEF will delete the API context and inform the third-party application of the API deregistration. + +## **7.6 API suspension** + +An API is required to be suspended according to the suspension indication from API management, e.g., API management preconfigures the time window of the permitted of the API usage, operator cannot provide the invocation of the API temporarily. The API management indicates the suspension of the API, and the CEF suspends the API from running state and stores the context of the API accordingly. Once the API runs into suspension state, the CEF will notify the suspension state of the API to the third-party applications. + +## **7.7 API recovery** + +An API can be recovered from suspension state, e.g., operator resume the invocation of the API to the third-party applications, API management preconfigures the time of API resumption. The API management indicates the CEF that the API has been recovered to the running state. Accordingly, the CEF resumes the API based on the context of the API previously stored at the moment of the API suspended. And then the CEF notifies the third-party applications the permitted usage of the API. + +## **7.8 API charging and monitoring** + +When the third-party application invokes CEF API, the CEF will send this API invocation event to the API management function. + +The API management function will monitor the invoking event and charge based on it. + +## **7.9 API topology hiding** + +The API topology hiding is required to ensure the API management function act as the entry point for service API invocation when the third-party application is not in the IMT-2020 network trust domain. + +CEF invokes the topology hiding API before communication with the third party for first time. The API management function will hide the address of CEF and other related network functions, network inside topology and path information from the third-party application which is not in the trust domain of IMT-2020 network. + +## 7.10 API location query + +Specific kinds of third-party applications need to know the location of user equipment (UE), like map application, navigation application. CEF queries IMT-2020 core network for the location of UE and return it to the third-party. + +# 8 Signalling flow + +## 8.1 API registration procedure + +Figure 8-1 illustrates the procedure for registration of the capability exposure API. + +![Sequence diagram for API registration procedure](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` +sequenceDiagram + participant CEF as Capability exposure function + participant AMF as API management function + Note right of AMF: 2. Store API(s) information + CEF->>AMF: 1. CE_API_Registration_request + AMF->>AMF: 2. Store API(s) information + AMF->>CEF: 3. CE_API_Registration_response + Note right of AMF: Q.5021(19)_F8-1 +``` + +The diagram illustrates the API registration procedure. It features two main participants: the Capability exposure function (CEF) and the API management function (AMF). The sequence of interactions is as follows: 1. The CEF sends a 'CE\_API\_Registration\_request' message to the AMF. 2. The AMF performs an internal action labeled 'Store API(s) information'. 3. The AMF sends a 'CE\_API\_Registration\_response' message back to the CEF. A reference label 'Q.5021(19)\_F8-1' is located at the bottom right of the diagram. + +Sequence diagram for API registration procedure + +**Figure 8-1 – API registration procedure** + +1. The capability exposure function sends a CE\_API\_Registration\_request to the API management function. It includes the list of capability exposure function instance and API list. +2. The API management function stores the information of capability exposure function and marks the capability exposure function available. +3. The API management function sends a CE\_API\_Registration\_response to the capability exposure function. + +## 8.2 API discovery procedure + +Figure 8-2 illustrates the procedure for discovery of the capability exposure API. + +![Sequence diagram for API discovery procedure](b3c108e7145f2017957569d06ea359cb_img.jpg) + +``` +sequenceDiagram + participant TPA as The third party application + participant AMF as API management function + Note right of AMF: 2. Retrieve API(s) information + TPA->>AMF: 1. CE_API_Discovery_request + AMF->>AMF: 2. Retrieve API(s) information + AMF->>TPA: 3. CE_API_Discovery_response + Note right of AMF: Q.5021(19)_F8-2 +``` + +The diagram illustrates the API discovery procedure. It features two main participants: The third party application (TPA) and the API management function (AMF). The sequence of interactions is as follows: 1. The TPA sends a 'CE\_API\_Discovery\_request' message to the AMF. 2. The AMF performs an internal action labeled 'Retrieve API(s) information'. 3. The AMF sends a 'CE\_API\_Discovery\_response' message back to the TPA. A reference label 'Q.5021(19)\_F8-2' is located at the bottom right of the diagram. + +Sequence diagram for API discovery procedure + +**Figure 8-2 – API discovery procedure** + +1. The third-party application sends a CE\_API\_Discovery\_request to the API management function. It includes the third-party application identity, type of the third-party application identity, name of the third-party application vendor and query information. + +2. Upon receiving the CE\_API\_Discovery\_request, the API management function verifies the identity of the third-party application (via authentication procedure). The API management function retrieves the stored API(s) information. Further, the API management function applies the discovery policy and performs filtering of service APIs information retrieved from the API management function. +3. The API management function sends a CE\_API\_Discovery\_response to the third-party application with the list of CEF instance for which the third-party application has the required authorization. + +## 8.3 API authorization procedure + +Figure 8-3 illustrates the procedure for authorization of the capability exposure API. + +![Sequence diagram for API authorization procedure](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +sequenceDiagram + participant ThirdPartyApplication as The third party application + participant APIManagementFunction as API management function + Note right of APIManagementFunction: 2. Check authority + ThirdPartyApplication->>APIManagementFunction: 1. CE_API_Authorization_request + APIManagementFunction-->>ThirdPartyApplication: 3. CE_API_Authorization_response + Note right of APIManagementFunction: Q.5021(19)_F8-3 +``` + +The diagram shows a sequence of interactions between 'The third party application' and 'API management function'. The third party application sends a '1. CE\_API\_Authorization\_request' to the API management function. The API management function then performs a '2. Check authority' step. Finally, the API management function sends a '3. CE\_API\_Authorization\_response' back to the third party application. The diagram is labeled 'Q.5021(19)\_F8-3'. + +Sequence diagram for API authorization procedure + +**Figure 8-3 – API authorization procedure** + +1. The third-party application sends a CE\_API\_Authorization\_request to the API management function. It includes the type of the third-party application, the third-party application identity, name of the third-party application vendor and query information. +2. The API management function checks the authorization information to make sure whether the third-party application is authorized to access the capability exposure API provided by CEF. +3. The API management function sends a CE\_API\_Authorization\_response to the third-party application. + +## 8.4 API authentication procedure + +Figure 8-4 illustrates the procedure for authentication of the capability exposure API. + +![Sequence diagram for API authentication procedure](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` +sequenceDiagram + participant ThirdPartyApplication as The third party application + participant APIManagementFunction as API management function + Note right of APIManagementFunction: 2. Third party application identity verification + ThirdPartyApplication->>APIManagementFunction: 1. CE_API_Authentication_request + APIManagementFunction-->>ThirdPartyApplication: 3. CE_API_Authentication_response + Note left of ThirdPartyApplication: 4. API management function identity verification + Note right of APIManagementFunction: Q.5021(19)_F8-4 +``` + +The diagram shows a sequence of interactions between 'The third party application' and 'API management function'. The third party application sends a '1. CE\_API\_Authentication\_request' to the API management function. The API management function then performs a '2. Third party application identity verification' step. Next, the API management function sends a '3. CE\_API\_Authentication\_response' back to the third party application. Finally, the third party application performs a '4. API management function identity verification' step. The diagram is labeled 'Q.5021(19)\_F8-4'. + +Sequence diagram for API authentication procedure + +**Figure 8-4 – API authentication procedure** + +1. The third-party application sends a CE\_API\_Authentication\_request to the API management function. It includes the third-party application identity and key. + +2. Then the API management function receives the authentication request, it verifies the identity information and validity of the key. +3. The API management function returns a CE\_API\_Authentication\_response to the third-party application. The response message also contains the key of the API management function. +4. The third-party application checks the validity of the key of the API management function. + +## 8.5 API deregistration procedure + +Figure 8-5 illustrates the procedure for deregistration of the capability exposure API. + +![Sequence diagram for API deregistration procedure. Lifelines: Capability exposure function, API management function. Steps: 1. CE_API_Deregistration_request from Capability exposure function to API management function; 2. Delete API(s) information (internal to API management function); 3. CE_API_Deregistration_response from API management function to Capability exposure function. Reference: Q.5021(19)_F8-5](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant Capability exposure function + participant API management function + Note right of API management function: 2. Delete API(s) information + Capability exposure function->>API management function: 1. CE_API_Deregistration_request + API management function-->>Capability exposure function: 3. CE_API_Deregistration_response + Note right of API management function: Q.5021(19)_F8-5 + +``` + +Sequence diagram for API deregistration procedure. Lifelines: Capability exposure function, API management function. Steps: 1. CE\_API\_Deregistration\_request from Capability exposure function to API management function; 2. Delete API(s) information (internal to API management function); 3. CE\_API\_Deregistration\_response from API management function to Capability exposure function. Reference: Q.5021(19)\_F8-5 + +**Figure 8-5 – API deregistration procedure** + +1. The capability exposure function sends a CE\_API\_Deregistration\_request to the API management function. It includes the API name, API function description, capability exposure function instance, serving the third-party application list. +2. The API management function deletes the API-related information. +3. The API management function sends a CE\_API\_Deregistration\_response to the capability exposure function. + +## 8.6 API suspension procedure + +Figure 8-6 illustrates the procedure for suspension of the capability exposure API. + +![Sequence diagram for API suspension procedure. Lifelines: The third party application, Capability exposure function, API management function. Steps: 1. CE_API_Suspension_request from API management function to Capability exposure function; 2. CE_API_Suspension_Notify_request from Capability exposure function to The third party application; 3. CE_API_Suspension_Notify_response from The third party application to Capability exposure function; 4. Change the API state (internal to Capability exposure function); 5. CE_API_Suspension_response from Capability exposure function to API management function; 6. Change the API state (internal to API management function). Reference: Q.5021(19)_F8-6](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +``` + +sequenceDiagram + participant The third party application + participant Capability exposure function + participant API management function + Note right of Capability exposure function: 4. Change the API state + Note right of API management function: 6. Change the API state + API management function->>Capability exposure function: 1. CE_API_Suspension_request + Capability exposure function->>The third party application: 2. CE_API_Suspension_Notify_request + The third party application-->>Capability exposure function: 3. CE_API_Suspension_Notify_response + Capability exposure function-->>API management function: 5. CE_API_Suspension_response + Note right of API management function: Q.5021(19)_F8-6 + +``` + +Sequence diagram for API suspension procedure. Lifelines: The third party application, Capability exposure function, API management function. Steps: 1. CE\_API\_Suspension\_request from API management function to Capability exposure function; 2. CE\_API\_Suspension\_Notify\_request from Capability exposure function to The third party application; 3. CE\_API\_Suspension\_Notify\_response from The third party application to Capability exposure function; 4. Change the API state (internal to Capability exposure function); 5. CE\_API\_Suspension\_response from Capability exposure function to API management function; 6. Change the API state (internal to API management function). Reference: Q.5021(19)\_F8-6 + +**Figure 8-6 – API suspension procedure** + +1. The API management function sends a CE\_API\_Suspension\_request to the capability exposure function. It includes the API name, API function description, capability exposure function instance, serving the third-party application list, duration of suspension. + +2. The capability exposure function sends a CE\_API\_Suspension\_Notify\_request to the third-party applications according to the list. It includes the API name, API function description, capability exposure function instance, duration of suspension. +3. The third-party application sends a CE\_API\_Suspension\_Notify\_response to the capability exposure function. +4. The capability exposure function changes the API into suspension state and stop to support capability exposure to the third-party applications temporarily. +5. The capability exposure function sends a CE\_API\_Suspension\_response to the API management function. +6. The API management function changes the API into suspension state and stop to support capability exposure temporarily. + +## 8.7 API recovery procedure + +Figure 8-7 illustrates the procedure for recovery of the capability exposure API. + +![Sequence diagram of the API recovery procedure. Lifelines: The third party application, Capability exposure function, and API management function. The sequence starts with the API management function performing '1. Change the API state', then sending '2. CE_API_Recovery_request' to the Capability exposure function. The Capability exposure function performs '3. Change the API state', then sends '4. CE_API_Recovery_Notify_request' to the third party application. The third party application sends '5. CE_API_Recovery_Notify_response' back to the Capability exposure function, which finally sends '6. CE_API_Recovery_response' to the API management function. The diagram is labeled Q.5021(19)_F8-7.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant Application as The third party application + participant Capability as Capability exposure function + participant Management as API management function + Note right of Management: 1. Change the API state + Management->>Capability: 2. CE_API_Recovery_request + Note right of Capability: 3. Change the API state + Capability->>Application: 4. CE_API_Recovery_Notify_request + Application->>Capability: 5. CE_API_Recovery_Notify_response + Capability->>Management: 6. CE_API_Recovery_response + +``` + +Q.5021(19)\_F8-7 + +Sequence diagram of the API recovery procedure. Lifelines: The third party application, Capability exposure function, and API management function. The sequence starts with the API management function performing '1. Change the API state', then sending '2. CE\_API\_Recovery\_request' to the Capability exposure function. The Capability exposure function performs '3. Change the API state', then sends '4. CE\_API\_Recovery\_Notify\_request' to the third party application. The third party application sends '5. CE\_API\_Recovery\_Notify\_response' back to the Capability exposure function, which finally sends '6. CE\_API\_Recovery\_response' to the API management function. The diagram is labeled Q.5021(19)\_F8-7. + +**Figure 8-7 – API recovery procedure** + +1. The API management function changes the API into active state. +2. The API management function sends a CE\_API\_Recovery\_request to the capability exposure function. It includes the API name, API function description, capability exposure function instance, serving the third-party application list, duration of suspension. +3. The capability exposure function change the API into active state and recovery the third-party application to invoke it. +4. The capability exposure function sends a CE\_API\_Recovery\_Notify\_request to the third-party application. It includes the API name, API function description, capability exposure function instance, duration of suspension. +5. The third-party application sends a CE\_API\_Recovery\_Notify\_response to the capability exposure function. +6. The capability exposure function sends a CE\_API\_Recovery\_response to the API management function. + +## 8.8 API charging and monitoring procedure + +Figure 8-8 illustrates the procedure for monitoring of the capability exposure API. + +![Sequence diagram for API charging and monitoring procedure](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +``` +sequenceDiagram + participant CEF as Capability exposure function + participant AMF as API management function + Note right of AMF: 2. Store charging/monitoring event + CEF->>AMF: 1. CE_API_Charging_Monitoring_request + AMF->>CEF: 3. CE_API_Charging_Monitoring_response + Note right of AMF: Q.5021(19)_F8-8 +``` + +The diagram shows a sequence of three messages between the Capability exposure function and the API management function. The first message is a request from the capability exposure function to the API management function. The API management function then stores the charging/monitoring event. Finally, the API management function sends a response back to the capability exposure function. The diagram is labeled Q.5021(19)\_F8-8. + +Sequence diagram for API charging and monitoring procedure + +**Figure 8-8 – API charging and monitoring procedure** + +1. The capability exposure function sends a CE\_API\_Charging\_Monitoring\_request to the API management function. It includes the third-party application identity, request capability exposure API. +2. The API management function stores the monitoring event information and charge based on it. +3. The API management function sends a CE\_API\_Charging\_Monitoring\_response to the capability exposure function. + +## 8.9 API topology hiding procedure + +Figure 8-9 illustrates the procedure for topology hiding of the capability exposure API. + +![Sequence diagram for topology hiding procedure](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` +sequenceDiagram + participant CEF as Capability exposure function + participant AMF as API management function + Note right of AMF: 2. Apply topology hiding policy + CEF->>AMF: 1. CE_API_Topology_Hiding_request + AMF->>CEF: 3. CE_API_Topology_Hiding_response + Note right of AMF: Q.5021(19)_F8-9 +``` + +The diagram shows a sequence of three messages between the Capability exposure function and the API management function. The first message is a request from the capability exposure function to the API management function. The API management function then applies the topology hiding policy. Finally, the API management function sends a response back to the capability exposure function. The diagram is labeled Q.5021(19)\_F8-9. + +Sequence diagram for topology hiding procedure + +**Figure 8-9 – Topology hiding procedure** + +1. The capability exposure function sends a CE\_API\_Topology\_Hiding\_request. It includes the list of capability exposure function instance, and the API list. +2. The API management function applies the policy of topology hiding and determines itself as the entry point for service API invocation. +3. The API management function sends a CE\_API\_Topology\_Hiding\_response to the capability exposure function. + +## 8.10 API location query procedure + +Figure 8-10 illustrates the procedure for location query of the capability exposure API. + +![Sequence diagram of the API location query procedure. The diagram shows three messages between the Capability exposure function and the IMT-2020 core network. 1. CE_API_Location_Query_request is sent from the Capability exposure function to the IMT-2020 core network. 2. Location information query is sent from the IMT-2020 core network to itself. 3. CE_API_Location_Query_response is sent from the IMT-2020 core network back to the Capability exposure function. The diagram is labeled Q.5021(19)_F8-10.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +``` + +sequenceDiagram + participant CEF as Capability exposure function + participant IMT as IMT-2020 core network + Note right of IMT: 2. Location information query + CEF->>IMT: 1. CE_API_Location_Query_request + IMT->>IMT: 2. Location information query + IMT->>CEF: 3. CE_API_Location_Query_response + +``` + +Sequence diagram of the API location query procedure. The diagram shows three messages between the Capability exposure function and the IMT-2020 core network. 1. CE\_API\_Location\_Query\_request is sent from the Capability exposure function to the IMT-2020 core network. 2. Location information query is sent from the IMT-2020 core network to itself. 3. CE\_API\_Location\_Query\_response is sent from the IMT-2020 core network back to the Capability exposure function. The diagram is labeled Q.5021(19)\_F8-10. + +**Figure 8-10 – API location query procedure** + +1. The capability exposure function sends a CE\_API\_Location\_Query request to IMT-2020 core network. It includes the third-party application identity, type of the third-party application identity, name of the third-party application vendor and UE information. +2. The IMT-2020 core network queries the location information based on the UE information. +3. The IMT-2020 core network sends a CE\_API\_Location\_Query response to the capability exposure function. + +# 9 Message format and API definition + +This clause specifies the details of each message for API management. 'M' in status field of each table in this clause means mandatory. + +## 9.1 CE\_API\_Registration + +This API enables the capability exposure function to communicate with the API management function to register CEF instance(s) with specific capability exposure APIs over IF4. + +Table 9-1 describes the detailed information of CE\_API\_Registration\_request. + +**Table 9-1 – CE\_API\_Registration\_request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------------------------|--------|-----------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| capability exposure function instance | M | string | 1..N | List of capability exposure function instance corresponding to the request, including the IP address, port number of the capability exposure function instance | +| API list | M | string | 1..N | List of APIs that the capability exposure function support, including the API name, API function description, serving user list | + +Table 9-2 describes the detailed information of CE\_API\_Registration\_response. + +**Table 9-2 – CE\_API\_Registration\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the service API information
201 Created
400 Input Parameter Error
500 Server Internal Error | + +## 9.2 CE\_API\_Discovery + +This API enables the third-party application to communicate with the API management function to discover CEF instance(s) with specific capability exposure APIs over IF3. + +Table 9-3 describes the detailed information of CE\_API\_Discovery\_request. + +**Table 9-3 – CE\_API\_Discovery\_request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------------------------------------------|--------|-----------|-------------|---------------------------------------------------------------------------| +| third-party application identity information | M | string | 1 | Identity information of the third-party application | +| type of the third-party application identity information | M | string | 1 | The type of the third-party application identity information | +| name of the third-party application vendor | M | string | 1..N | The name of the third-party application vendor | +| query information | M | string | 1..N | Criteria for discovering matching service APIs (e.g., API type, API name) | + +Table 9-4 describes the detailed information of CE\_API\_Discovery\_response. + +**Table 9-4 – CE\_API\_Discovery\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the discovery of the service API information
200 OK
400 Input Parameter Error
500 Server Internal Error | +| capability exposure function instance | M | string | 1..N | N/A | List of capability exposure function instance corresponding to the request, including the IP address, port number of the capability exposure function instance | +| API list | M | string | 1..N | N/A | List of APIs that the capability exposure function support, including the API name, API description, serving user list | + +## 9.3 CE\_API\_Authorization + +This API enables the third-party application to communicate with the API management function to check whether the third-party application is authorized to access the capability exposure APIs over IF3. + +Table 9-5 describes the detailed information of CE\_API\_Authorization\_request. + +**Table 9-5 – CE\_API\_Authorization\_request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------------------------------------------|--------|-----------|-------------|--------------------------------------------------------------------------| +| third-party application identity information | M | string | 1 | Identity information of the third-party application | +| type of the third-party application identity information | M | string | 1 | The type of the third-party application identity information | +| name of the third-party application vendor | M | string | 1..N | The name of the third-party application vendor | +| query information | M | string | 1..N | Criteria for authorized matching service APIs (e.g., API type, API name) | + +Table 9-6 describes the detailed information of CE\_API\_Authorization\_response. + +**Table 9-6 – CE\_API\_Authorization\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the authorization of the service API information
200 OK
400 Input Parameter Error
500 Server Internal Error | + +## 9.4 CE\_API\_Authentication + +This API enables the third-party application to communicate with the API management function to obtain mutual authentication over IF3. + +Table 9-7 describes the detailed information of CE\_API\_Authentication\_request. + +**Table 9-7 – CE\_API\_Authentication\_request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------------------------------------------|--------|-----------|-------------|--------------------------------------------------------------| +| third-party application identity information | M | string | 1 | Identity information of the third-party application | +| type of the third-party application identity information | M | string | 1 | The type of the third-party application identity information | +| third-party application key information | M | string | 1..N | Key information of third-party application | + +Table 9-8 describes the detailed information of CE\_API\_Authentication\_response. + +**Table 9-8 – CE\_API\_Authentication\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|-----------------------------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the authorization of the service API information
200 OK
400 Input Parameter Error
500 Server Internal Error | +| API management function key information | M | string | 1..N | N/A | Key information of API management function, e.g., server-side certificate or key | + +## 9.5 CE\_API\_Deregistration + +This API enables the capability exposure function to communicate with the API management function to unregister CEF instance(s) with specific capability exposure APIs over IF4. + +Table 9-9 describes the detailed information of CE\_API\_Deregistration\_request. + +**Table 9-9 – CE\_API\_Deregistration\_request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------------------|--------|-----------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API name | M | string | 1 | The name of deregistration API | +| API function description | M | string | 1 | The function description of deregistration API | +| capability exposure function instance | M | string | 1..N | List of capability exposure function instance support the deregistration API, including the IP address, port number of the capability exposure function instance | +| serving the third-party application list | M | string | 1..N | List of serving the third-party applications that the deregistration API support, including the application name, vendor name | + +Table 9-10 describes the detailed information of CE\_API\_Deregistration\_response. + +**Table 9-10 – CE\_API\_Deregistration\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the deregister of the API
200 OK
400 Input Parameter Error
500 Server Internal Error | + +## 9.6 CE\_API\_Suspension + +This API enables the capability exposure function to communicate with the API management function to suspended API invocation over IF4. + +Table 9-11 describes the detailed information of CE\_API\_Suspension\_request. + +**Table 9-11 – CE\_API\_Suspension\_request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------------------|--------|-----------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API name | M | string | 1 | The name of suspension API | +| API function description | M | string | 1 | The function description of suspension API | +| capability exposure function instance | M | string | 1..N | List of capability exposure function instance support the suspension API, including the IP address, port number of the capability exposure function instance | +| serving the third-party application list | M | string | 1..N | List of serving the third-party applications that the suspension API supports, including the application name, vendor name | +| duration of suspension | M | num | 1 | Duration of API suspension, from 0 to maximum number. 0 represents indefinite duration | + +Table 9-12 describes the detailed information of CE\_API\_Suspension\_response. + +**Table 9-12 – CE\_API\_Suspension\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the suspension of the API
200 OK
400 Input Parameter Error
500 Server Internal Error | + +## 9.7 CE\_API\_Suspension\_Notify + +This API enables the capability exposure function to communicate with the third-party application to notify the suspension state of CEF instance(s) with specific capability exposure APIs over IF2. + +Table 9-13 describes the detailed information of CE\_API\_Suspension\_Notify\_request. + +**Table 9-13 – CE\_API\_Suspension\_Notify\_request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------------------------|--------|-----------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API name | M | string | 1 | The name of suspension API | +| API function description | M | string | 1 | The function description of suspension API | +| capability exposure function instance | M | string | 1..N | List of capability exposure function instance support the suspension API, including the IP address, port number of the capability exposure function instance | +| duration of suspension | M | num | 1 | Duration of API suspension, from 0 to maximum number. 0 represents indefinite duration | + +Table 9-14 describes the detailed information of CE\_API\_Suspension\_Notify\_response. + +**Table 9-14 – CE\_API\_Suspension\_Notify\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the suspension notification of the API
200 OK
400 Input Parameter Error
500 Server Internal Error | + +## 9.8 CE\_API\_Recovery + +This API enables the capability exposure function to communicate with the API management function to recover the invocation of API over IF4. + +Table 9-15 describes the detailed information of CE\_API\_Recovery\_request. + +**Table 9-15 – CE\_API\_Recovery\_request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------------------------|--------|-----------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API name | M | string | 1 | The name of recovery API | +| API function description | M | string | 1 | The function description of recovery API | +| capability exposure function instance | M | string | 1..N | List of capability exposure function instance support the recovery API, including the IP address, port number of the capability exposure function instance | + +**Table 9-15 – CE\_API\_Recovery\_request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------------------|--------|-----------|-------------|--------------------------------------------------------------------------------------------------------------------------| +| serving the third-party application list | M | string | 1..N | List of serving the third-party applications that the recovery API supports, including the application name, vendor name | +| duration of suspension | M | num | 1 | Duration of API suspension, from 0 to maximum number. 0 represents indefinite duration | + +Table 9-16 describes the detailed information of CE\_API\_Recovery\_response. + +**Table 9-16 – CE\_API\_Recovery\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the recovery of the API
200 OK
400 Input Parameter Error
500 Server Internal Error | + +## 9.9 CE\_API\_Recovery\_Notify + +This API enables the capability exposure function to communicate with the third-party application to notify recovery of CEF instance(s) with specific capability exposure APIs over IF2. + +Table 9-17 describes the detailed information of CE\_API\_Recovery\_Notify\_request. + +**Table 9-17 – CE\_API\_Recovery\_Notify\_request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------------------------|--------|-----------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API name | M | string | 1 | The name of recovery API | +| API function description | M | string | 1 | The function description of recovery API | +| capability exposure function instance | M | string | 1..N | List of capability exposure function instance support the recovery API, including the IP address, port number of the capability exposure function instance | +| duration of suspension | M | num | 1 | Duration of API suspension, from 0 to maximum number. 0 represents indefinite duration | + +Table 9-18 describes the detailed information of CE\_API\_Recovery\_Notify\_response. + +**Table 9-18 – CE\_API\_Recovery\_Notify\_response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the recovery notification of the API
200 OK
400 Input Parameter Error
500 Server Internal Error | + +## **9.10 CE\_API\_Charging\_Monitoring** + +This API enables the capability exposure function to communicate with the API management function to notify the invocation of APIs and charge based on it over IF4. + +Table 9-19 describes the detailed information of CE\_API\_Charging\_Monitoring\_request. + +**Table 9-19 – CE\_API\_Charging\_Monitoring\_request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------------------------------------------|--------|-----------|-------------|--------------------------------------------------------------| +| third-party application identity information | M | string | 1 | Identity information of the third-party application | +| type of the third-party application identity information | M | string | 1 | The type of the third-party application identity information | +| API list | M | string | 1..N | List of APIs that the third-party application invoke | + +Table 9-20 describes the detailed information of CE\_API\_Charging\_Monitoring\_response. + +**Table 9-20 – CE\_API\_Charging\_Monitoring\_response** + +| Information element | Status | Data type | Cardinality | Code Value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 201
400
500 | Indicates the success or failure of the invocation event notification response of the service API information
201 Created
400 Input Parameter Error
500 Server Internal Error | + +## **9.11 CE\_API\_Topology\_Hiding** + +This API enables the capability exposure function to communicate with the API management function to determine API management function as the entry point for service API invocation for third-party application outside the IMT-2020 network trust domain. + +Table 9-21 describes the detailed information of CE\_API\_Topology\_Hiding\_request. + +**Table 9-21 – CE\_API\_Topology\_Hiding\_request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------------------------------------------|--------|-----------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| third-party application identity information | M | string | 1 | Identity information of the third-party application | +| type of the third-party application identity information | M | string | 1 | The type of the third-party application identity information | +| capability exposure function instance | M | string | 1..N | List of capability exposure function instance corresponding to the request, including the IP address, port number of the capability exposure function instance | +| API list | M | string | 1..N | List of APIs that the capability exposure function support | + +Table 9-22 describes the detailed information of CE\_API\_Topology\_Hiding\_response. + +**Table 9-22 – CE\_API\_Topology\_Hiding\_response** + +| Information element | Status | Data type | Cardinality | Code Value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the topology hiding of capability exposure function from the third-party application
200 OK
400 Input Parameter Error
500 Server Internal Error | + +## 9.12 CE\_API\_Location\_Query + +This API enables the capability exposure function communicate with the IMT-2020 core network to query UE location over IF1. + +Table 9-23 describes the details information of CE\_API\_Location\_Query request. + +**Table 9-23 – CE\_API\_Location\_Query request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------------------------------------------|--------|-----------|-------------|--------------------------------------------------------------| +| third-party application identity information | M | string | 1 | Identity information of the third-party application | +| type of the third-party application identity information | M | string | 1 | The type of the third-party application identity information | +| name of the third-party application vendor | M | string | 1..N | The name of the third-party application vendor | +| UE information | M | string | 1..N | UE ID which CEF query location information for | + +Table 9-24 describes the details information of CE\_API\_Location\_Query response. + +**Table 9-24 – CE\_API\_Location\_Query response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|----------------------------|---------------|------------------|--------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| result | M | num | 1 | 200
400
500 | Indicates the success or failure of the discovery of the service API information
200 OK
400 Input Parameter Error
500 Server Internal Error | +| location information | M | string | 1..N | N/A | Location information of UE which CEF query for. | +| time information | M | string | 1..N | N/A | Time information of the location information. | + +# Bibliography + +- [b-ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network.* +- [b-ITU-T Y.3101] Recommendation ITU-T Y.3101 (2018), *Requirements of the IMT-2020 network.* +- [b-ITU-T Y.3105] Recommendation ITU-T Y.3105 (2018), *Requirements of capability exposure in the IMT-2020 network.* +- [b-ITU-T Y.IMT2020-CEF] Draft Recommendation ITU-T Y.IMT2020-CEF, *Network capability exposure function in the IMT-2020 networks.* +- [b-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.* +- [b-ITU-R M.2083-0] Recommendation ITU-R M.2083-0 (2015), *IMT Vision – Framework and overall objectives of the future development of IMT for 2020 and beyond.* + + + +## 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.5025-202209-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5025-202209-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f523c3333bc7cf461bc71654070e813927517589 --- /dev/null +++ b/marked/Q/T-REC-Q.5025-202209-I_PDF-E/raw.md @@ -0,0 +1,1384 @@ + + +# Recommendation + +## **ITU-T Q.5025 (09/2022)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Signalling requirements and protocols for IMT-2020 – +Protocols for IMT-2020 + +## --- **Protocol for managing the user plane function in IMT-2020 networks** + +![ITU logo](4f4b52340aaccb1bcf733468dca9ee03_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T 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.5025 + +## Protocol for managing the user plane function in IMT-2020 networks + +## Summary + +Recommendation ITU-T Q.5025 specifies the protocol for managing user plane function (UPF) in the IMT-2020 network. It describes the communication mechanism inside the UPF. It also describes the application programming interface (API) management, procedure, signalling flow and message format between the UPF and other core network functions or third-party applications. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.5025 | 2022-09-29 | 11 | 11.1002/1000/15047 | + +## Keywords + +API management, IMT-2020, user plane function. + +--- + +\* 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..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | Overview ..... | 2 | +| 7 | Modularized UPF architecture..... | 3 | +| 8 | Signalling flow..... | 4 | +| 8.1 | UPF service registration ..... | 4 | +| 8.2 | UPF service update..... | 4 | +| 8.3 | UPF service deregistration ..... | 5 | +| 8.4 | UPF service discovery ..... | 5 | +| 8.5 | UPF node transmission path set-up ..... | 6 | +| 8.6 | UPF node transmission path update ..... | 7 | +| 8.7 | UPF node transmission path release..... | 7 | +| 8.8 | Session establishment..... | 8 | +| 8.9 | Session update ..... | 8 | +| 8.10 | Session release..... | 9 | +| 8.11 | Local area network tunnel set-up between UPFs ..... | 9 | +| 8.12 | UPF event exposure..... | 10 | +| 8.13 | Customized UPF service registration ..... | 11 | +| 8.14 | Customized UPF service deregistration ..... | 12 | +| 8.15 | DAF subscription to periodic UPF information ..... | 12 | +| 8.16 | DAF unsubscription to UPF information ..... | 13 | +| 8.17 | DAF request for the UPF information..... | 13 | +| 8.18 | UPF information notification ..... | 13 | +| 8.19 | Network management triggered UPF energy saving..... | 14 | +| 9 | Message format..... | 15 | +| 9.1 | UPF service registration ..... | 15 | +| 9.2 | UPF service update..... | 16 | +| 9.3 | UPF service deregistration ..... | 16 | +| 9.4 | UPF service discovery ..... | 17 | +| 9.5 | UPF node transmission path set-up ..... | 18 | +| 9.6 | UPF node transmission path update ..... | 19 | +| 9.7 | UPF node transmission path release..... | 20 | +| 9.8 | Session establishment..... | 21 | + +| | Page | +|----------------------------------------------------------|------| +| 9.9 Session update ..... | 22 | +| 9.10 Session release..... | 23 | +| 9.11 Local area network tunnel set-up between UPFs ..... | 23 | +| 9.12 UPF event exposure..... | 25 | +| 9.13 Customized UPF service registration ..... | 25 | +| 9.14 Customized UPF service deregistration ..... | 27 | +| 9.15 DAF subscription to periodic UPF information ..... | 28 | +| 9.16 DAF unsubscription to UPF information ..... | 28 | +| 9.17 DAF request for UPF information..... | 29 | +| 9.18 UPF information notification ..... | 30 | +| 9.19 Network management triggered UPF energy saving..... | 31 | +| Bibliography..... | 34 | + +# Recommendation ITU-T Q.5025 + +###### Protocol for managing the user plane function in IMT-2020 networks + +# 1 Scope + +This Recommendation specifies the protocol for managing user plane function (UPF) in the International mobile telecommunications (IMT)-2020 network. It describes the communication mechanisms inside UPF. It also describes the application programming interface (API) management, procedure, signalling flow and message format between UPF and other core network functions or third-party applications. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 data analysis function** [b-ITU-T Q.5023]: A network function that can collect, analyse, and provide data from/to International Mobile Telecommunications 2020 (IMT-2020) core network functions, network management and third-party applications. + +**3.1.2 IMT-2020** [b-ITU-T Y.3100]: (Based on [b-ITU-R M.2083-0]) Systems, system components, and related technologies that provide far more enhanced capabilities than those described in [b-ITU-R M.1645]. + +**3.1.3 management** [b-ITU-T Y.3100]: In the context of IMT-2020, the processes aiming at fulfilment, assurance, and billing of services, network functions, and resources in both physical and virtual infrastructure including compute, storage, and network resources. + +**3.1.4 network function** [b-ITU-T Y.3100]: In the context of IMT-2020, a processing function in a network. + +**3.1.5 user plane** [b-ITU-T Y.2011]: A synonym for the data plane. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +API            Application Programming Interface + +CEF            Capability Exposure Function + +| | | +|------|------------------------------------------| +| DAF | Data Analysis Function | +| DN | Data Network | +| DNN | Data Network Name | +| FQDN | Fully Qualified Domain Name | +| IMT | International Mobile Telecommunications | +| IP | Internet Protocol | +| LAN | Local Area Network | +| NF | Network Function | +| NFR | Network Function Registry function | +| OAM | Operation Administration and Maintenance | +| PCF | Policy Control Function | +| PDU | Protocol Data Unit | +| QoS | Quality of Service | +| RAN | Radio Access Network | +| SMF | Session Management Function | +| SUPI | Subscription Permanent Identifier | +| UE | User Equipment | +| UPF | User Plane Function | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +The keywords "M" indicate the element is mandatory. The keywords "O" indicate the element is optional. The keywords "C" indicate the element is conditional. + +# 6 Overview + +With the increasing requirement for an IMT-2020 network in edge environments from vertical industries, the demand for user plane function (UPF) is diverse and urgent. Service-based UPF is proposed to meet the needs of verticals. + +Based on the internal function modularization of UPF, clear and independent services lead to easy deployment and reorganization. In addition, open application programming interface (API) offers 3rd party applications to develop functions independently, such as secondary authentication in the industry and autonomous internet protocol (IP) address allocation. The customized function + +management service will manage and orchestrate customized functions from 3rd party applications in the UPF. Based on the internal and external modularization, UPF is easy to be customized and reorganized. + +# 7 Modularized UPF architecture + +Figure 7-1 shows the architecture reference model of service based UPF and open API in the IMT-2020 network. It includes the UPF native function services and customized services from 3rd party applications. It also shows the relationship between UPF and other core network functions (NF) of IMT-2020 and 3rd party applications. UPF interacts with the network function registry function (NFR) by invoking service based interfaces. + +Native function / services of UPF includes traffic routing and forwarding, protocol data unit (PDU) session tunnel management, policy control, anchor point, event exposure, security management and other customized functions, like packet inspection and collection of UPF traffic for lawful intercept and interworking functionalities among different network domains, e.g., interworking between IP-based core network and non-IP based access network. These UPF services can be invoked by other network functions to achieve related functionalities, and these UPF services can be created, updated, or removed. + +Traffic routing and forwarding: UPF supports + +- traffic forwarding, dropping and buffering, including IPv4, IPv6 and Ethernet type; +- forwarding traffic to the session management function (SMF), radio access network (RAN), data network (DN) and 3rd party applications; +- classifier for traffic based on traffic forwarding rules. + +PDU session tunnel management: UPF supports + +- encapsulation and decapsulation of the packet for tunnel; +- enforcement of tunnel establishment and release based on the rules received from SMF. + +Policy control: UPF supports + +- predefined rules configured by network management; +- dynamic policies configured for traffic flows by the policy control function (PCF) via SMF, e.g., Quality of service (QoS) enforcement rule, traffic forwarding rule with SMF invoking UPF policy control services; +- traffic usage report based on traffic volume, usage time and event. + +Anchor point: UPF supports + +- act as a PDU session anchor point providing access to the DN; +- multiple session anchors in a single PDU session; +- construct end marker when RAN handover. + +Event exposure: UPF supports + +- Expose PDU session related information; +- Expose UPF load information. + +Security management: UPF supports + +- Clear user personal information, such as a subscription permanent identifier (SUPI), etc., after the session ends; +- Access device security monitoring and access address security verification; +- Interface filtering and security protection. + +Customized services are developed independently by 3rd party based on an open API offered by UPF, which are managed and orchestrated by a customized service management. + +![Figure 7-1: Architecture reference model for user plane function in IMT-2020 network. The diagram shows the UPF connected to SMF and CEF. The UPF is divided into two main functional groups: a standard group (Traffic routing and forwarding, PDU session tunnel management, Policy enforcement, Anchor point, Security management, Event exposure) and a customized group (Customized module 1, Customized module 2, Customized module management). A Third party application in DN is connected to the CEF.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +The diagram illustrates the architecture reference model for the user plane function (UPF) in an IMT-2020 network. At the top, the SMF (Session Management Function) and CEF (Customized Element Function) are shown. Below them, the UPF (User Plane Function) is depicted as a large box containing two dashed-line enclosed areas. The left area represents standard UPF functions: Traffic routing and forwarding, PDU session tunnel management, Policy enforcement, Anchor point, Security management, and Event exposure. The right area represents customized functions: Customized module 1, Customized module 2, and Customized module management. To the right of the UPF, a box labeled 'Third party application in DN' (Data Network) is connected to the CEF. + +Figure 7-1: Architecture reference model for user plane function in IMT-2020 network. The diagram shows the UPF connected to SMF and CEF. The UPF is divided into two main functional groups: a standard group (Traffic routing and forwarding, PDU session tunnel management, Policy enforcement, Anchor point, Security management, Event exposure) and a customized group (Customized module 1, Customized module 2, Customized module management). A Third party application in DN is connected to the CEF. + +Q.5025(22) + +**Figure 7-1 – Architecture reference model for user plane function in IMT-2020 network** + +# 8 Signalling flow + +## 8.1 UPF service registration + +UPF service registers in the NFR by invoking the service based interface Nfr\_NFService\_Registration which is shown in Figure 8-1. + +![Figure 8-1: UPF services registration procedure. The sequence diagram shows the UPF sending a registration request to the NFR, the NFR storing the information, and the NFR sending a response back to the UPF.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +The sequence diagram illustrates the UPF services registration procedure. It involves two main entities: UPF and NFR. The sequence of messages is as follows: 1. The UPF sends an 'Nfr\_NFService\_Registration\_Request' message to the NFR. 2. The NFR performs an internal action labeled 'Store UPF information'. 3. The NFR sends an 'Nfr\_NFService\_Registration\_Response' message back to the UPF. + +Figure 8-1: UPF services registration procedure. The sequence diagram shows the UPF sending a registration request to the NFR, the NFR storing the information, and the NFR sending a response back to the UPF. + +Q.5025(22) + +**Figure 8-1 – UPF services registration procedure** + +- 1 UPF sends Nfr\_NFService\_Registration\_Request message to NFR to inform of the available UPF services. The message includes information on the available UPF services (e.g., traffic routing and forwarding, PDU session tunnel management, policy enforcement, anchor point, and other customized functions), UPF serving area, network slice type indicator, data network name (DNN), interface, UPF ID and UPF address. +- 2 NFR stores information about the UPF services and marks the UPF services available. +- 3 The NFR sends Nfr\_NFService\_Registration\_Response message to the UPF to inform of the accomplishment of UPF services registration. + +## 8.2 UPF service update + +UPF updates its service information in the NFR by invoking the service based interface Nfr\_NFService\_Update which is shown in Figure 8-2. + +![Sequence diagram for UPF service update procedure. The diagram shows two lifelines: UPF and NFR. The sequence of messages is: 1. Nfr_NFService_Update_Request from UPF to NFR; 2. Update UPF information (internal message on NFR); 3. Nfr_NFService_Update_Response from NFR to UPF. The diagram is labeled Q.5025(22).](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +sequenceDiagram + participant UPF + participant NFR + Note right of NFR: 2. Update UPF information + UPF->>NFR: 1. Nfr_NFService_Update_Request + NFR-->>UPF: 3. Nfr_NFService_Update_Response + Note right of NFR: Q.5025(22) + +``` + +Sequence diagram for UPF service update procedure. The diagram shows two lifelines: UPF and NFR. The sequence of messages is: 1. Nfr\_NFService\_Update\_Request from UPF to NFR; 2. Update UPF information (internal message on NFR); 3. Nfr\_NFService\_Update\_Response from NFR to UPF. The diagram is labeled Q.5025(22). + +**Figure 8-2 – UPF service update procedure** + +- 1 UPF sends Nfr\_NFService\_Update\_Request message to the NFR when the UPF service updating is needed, e.g., UPF scaling. The message includes updated information of the UPF services (e.g., traffic routing and forwarding, PDU session tunnel management, policy enforcement, anchor point, and other customized functions), UPF serving area, network slice type indicator, DNN, interface, UPF ID and UPF address. +- 2 NFR updates the information on the UPF services and sends a UPF services update notification to the UPF services consumers. +- 3 The NFR sends Nfr\_NFService\_Update\_Response message to the UPF to inform of the accomplishment of the update. + +## 8.3 UPF service deregistration + +UPF service deregisters in the NFR by invoking a service based interface Nfr\_NFService\_Deregistration which is shown in Figure 8-3. + +![Sequence diagram for UPF service deregistration procedure. The diagram shows two lifelines: UPF and NFR. The sequence of messages is: 1. Nfr_NFService_Deregistration_Request from UPF to NFR; 2. Delete UPF information (internal message on NFR); 3. Nfr_NFService_Deregistration_Response from NFR to UPF. The diagram is labeled Q.5025(22).](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` + +sequenceDiagram + participant UPF + participant NFR + Note right of NFR: 2. Delete UPF information + UPF->>NFR: 1. Nfr_NFService_Deregistration_Request + NFR-->>UPF: 3. Nfr_NFService_Deregistration_Response + Note right of NFR: Q.5025(22) + +``` + +Sequence diagram for UPF service deregistration procedure. The diagram shows two lifelines: UPF and NFR. The sequence of messages is: 1. Nfr\_NFService\_Deregistration\_Request from UPF to NFR; 2. Delete UPF information (internal message on NFR); 3. Nfr\_NFService\_Deregistration\_Response from NFR to UPF. The diagram is labeled Q.5025(22). + +**Figure 8-3 – UPF service deregistration procedure** + +- 1 UPF sends Nfr\_NFService\_Deregistration\_Request message to the NFR to inform of the unavailable UPF services. The message includes the list of unavailable services of the UPF. +- 2 NFR deletes the information of the unavailable UPF services and sends an unavailable notification to the UPF services consumers. +- 3 The NFR sends Nfr\_NFService\_Deregistration\_Response message to the UPF to inform of the accomplishment of the deregistration. + +## 8.4 UPF service discovery + +Consumer NF discovers the target UPF service by NFR as shown in Figure 8-4. + +![Sequence diagram for UPF service discovery procedure between NF and NFR.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +sequenceDiagram + participant NF + participant NFR + Note right of NFR: 2. Authorize UPF discovery + NF->>NFR: 1. Nfr_NFService_Discovery_Request + NFR-->>NF: 2. Nfr_NFService_Discovery_Response + Note right of NFR: Q.5025(22) + +``` + +The diagram shows a sequence of messages between an NF (Network Function) and an NFR (NF Repository). The NF sends a '1. Nfr\_NFService\_Discovery\_Request' message to the NFR. The NFR then performs an internal step labeled '2. Authorize UPF discovery' and returns a '2. Nfr\_NFService\_Discovery\_Response' message to the NF. The reference 'Q.5025(22)' is noted at the bottom right. + +Sequence diagram for UPF service discovery procedure between NF and NFR. + +**Figure 8-4 – UPF service discovery procedure** + +- 1 Consumer NF invokes Nfr\_NFService\_Discovery\_Request to the NFR to the discovery UPF services, UPF serving area, network slice type indicator, DNN, interface, UPF ID, UPF IP address or a fully qualified domain name (FQDN), UE IP address, NF type, UPF instance ID, PLMN ID and application ID. +- 2 NFR authorizes the UPF discovery request based on the UPF registration information or local information of the operator. +- 3 NFR returns the UPF lists to the consumer NF, which match the discovery request. + +## 8.5 UPF node transmission path set-up + +The UPF node transmission path set-up procedure shall be used to set-up an invocation path between the SMF and the UPF which is shown in Figure 8-5, to enable the SMF to use the resources of the UPF subsequently, e.g., establish a session for a user equipment (UE), or based on this path to support the invocation of the UPF policy control service. + +![Sequence diagram for UPF node transmission path set-up procedure between SMF and UPF.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant UPF + SMF->>UPF: 1. Nupf_Node_Transmission_path_Setup_Request + UPF-->>SMF: 2. Nupf_Node_Transmission_path_Setup_Response + Note right of UPF: Q.5025(22) + +``` + +The diagram shows a sequence of messages between an SMF (Session Management Function) and a UPF (User Plane Function). The SMF sends a '1. Nupf\_Node\_Transmission\_path\_Setup\_Request' message to the UPF. The UPF then returns a '2. Nupf\_Node\_Transmission\_path\_Setup\_Response' message to the SMF. The reference 'Q.5025(22)' is noted at the bottom right. + +Sequence diagram for UPF node transmission path set-up procedure between SMF and UPF. + +**Figure 8-5 – UPF node transmission path set-up procedure** + +- 1 SMF sends Nupf\_Node\_Transmission\_path\_Setup\_Request message to the UPF with the Node ID of the SMF and the list of optional features supported by the SMF which may affect the UPF behaviour. +- 2 When the UPF receives the Nupf\_Node\_Transmission\_path\_Setup\_Request message and determines to accept the request, the UPF shall store the Node ID of the SMF as the identifier of the node transmission path, and send a Nupf\_Node\_Transmission\_path\_Setup\_Response with a successful cause, including all the supported optional features in the UPF and optionally including the available user plane resources, e.g., IP address(es). If the UPF determines not to accept the request, then the UPF shall send a Nupf\_Node\_Transmission\_path\_Setup\_Response with an appropriate error cause to indicate why to reject the node transmission path set-up. + +## 8.6 UPF node transmission path update + +The UPF node transmission path update procedure shall be used to modify an existing node level path between the SMF and the UPF which is shown in Figure 8-6. + +![Sequence diagram for UPF node transmission path update procedure](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +``` +sequenceDiagram + participant SMF + participant UPF + Note right of UPF: Q.5025(22) + SMF->>UPF: 1. Nupf_Node_Transmission_path_Update_Request + UPF-->>SMF: 2. Nupf_Node_Transmission_path_Update_Response +``` + +The diagram illustrates the interaction between the SMF and the UPF for a transmission path update. The SMF sends a 'Nupf\_Node\_Transmission\_path\_Update\_Request' message to the UPF. The UPF responds with a 'Nupf\_Node\_Transmission\_path\_Update\_Response' message. The reference 'Q.5025(22)' is noted at the bottom right of the diagram. + +Sequence diagram for UPF node transmission path update procedure + +**Figure 8-6 – UPF node transmission path update procedure** + +- 1 SMF sends Nupf\_Node\_Transmission\_path\_Update\_Request message to the UPF with the Node ID of the SMF and the list of optional features supported by the SMF which need to be updated that may affect the UPF behaviour. +- 2 When the UPF receives the Nupf\_Node\_Transmission\_path\_Update\_Request message and determines to accept the request, the UPF shall update the parameters of the node transmission path and send a Nupf\_Node\_Transmission\_path\_Update\_Response with a successful cause. If the UPF determines not to accept the request such as if the Node ID is not known by the UPF, then the UPF shall send a Nupf\_Node\_Transmission\_path\_Update\_Response with an appropriate error cause to indicate why to reject the node transmission path update. + +## 8.7 UPF node transmission path release + +The UPF node transmission path release procedure shall be used to release a node level path between the SMF and the UPF due to for example, operation administration and maintenance (OAM) reasons, and the procedure is shown in Figure 8-7. + +![Sequence diagram for UPF node transmission path release procedure](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +``` +sequenceDiagram + participant SMF + participant UPF + Note right of UPF: Q.5025(22) + SMF->>UPF: 1. Nupf_Node_Transmission_path_Release_Request + UPF-->>SMF: 2. Nupf_Node_Transmission_path_Release_Response +``` + +The diagram illustrates the interaction between the SMF and the UPF for a transmission path release. The SMF sends a 'Nupf\_Node\_Transmission\_path\_Release\_Request' message to the UPF. The UPF responds with a 'Nupf\_Node\_Transmission\_path\_Release\_Response' message. The reference 'Q.5025(22)' is noted at the bottom right of the diagram. + +Sequence diagram for UPF node transmission path release procedure + +**Figure 8-7 – UPF node transmission path release procedure** + +- 1 SMF sends Nupf\_Node\_Transmission\_path\_Release\_Request message to the UPF with the Node ID of the SMF to release a node level path between the SMF and the UPF. +- 2 When the UPF receives the Nupf\_Node\_Transmission\_path\_Release\_Request message, the UPF shall delete all the UE sessions related to that node transmission path and delete the node transmission path and any related information (e.g., Node ID of the SMF). Then the UPF shall send a Nupf\_Node\_Transmission\_path\_Release\_Response with a successful cause. + +## 8.8 Session establishment + +The session establishment procedure shall be used to set up a session between the SMF and the UPF and configure the rules in the UPF so that the UPF can handle the incoming packets. This procedure can also be used to establish a core network tunnel between UPFs in the same group for the local area networks between two UPFs. The detail of the procedure is shown in Figure 8-8. + +![Sequence diagram of the session establishment procedure between SMF, UPF1, and UPF2.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +``` +sequenceDiagram + participant SMF + participant UPF1 + participant UPF2 + Note right of UPF1: 2. Configure the related parameters + SMF->>UPF1: 1. Nupf_Session_Establish_Request + UPF1-->>SMF: 3. Nupf_Session_Establish_Response + SMF->>UPF2: 4. Nupf_Session_Establish_Request + UPF2-->>SMF: 5. Nupf_Session_Establish_Response +``` + +The diagram illustrates the session establishment procedure involving three entities: SMF, UPF1, and UPF2. The sequence of messages is as follows: 1. SMF sends a Nupf\_Session\_Establish\_Request message to UPF1. 2. UPF1 internally configures the related parameters. 3. UPF1 sends a Nupf\_Session\_Establish\_Response message back to SMF. 4. SMF sends a Nupf\_Session\_Establish\_Request message to UPF2. 5. UPF2 sends a Nupf\_Session\_Establish\_Response message back to SMF. The diagram is labeled Q.5025(22) at the bottom right. + +Sequence diagram of the session establishment procedure between SMF, UPF1, and UPF2. + +**Figure 8-8 – Session establishment procedure** + +- 1 SMF sends Nupf\_Session\_Establish\_Request message to the UPF to set up a session between the SMF and the UPF. The SMF assigns a new session ID and the related parameters such as QoS and provides them to the UPF in this message. The session ID is stored by both the entities and is used to identify the session context during their interaction. The SMF also stores the relation between the session ID and the PDU session for a UE. +- 2 Once received the Nupf\_Session\_Establish\_Request message, the UPF will save the related parameters received from the SMF, and set up a context for the new PDU session. +- 3 The UPF sends a Nupf\_Session\_Establish\_Response message containing any information that the UPF has to provide to the SMF, such as the UE IP address if it is allocated by the UPF. +- 4 (Optional) If a core network tunnel for the local area networks between two UPFs is needed to be established and the tunnel parameters are allocated by the UPF, then the parameters will not be included in the Nupf\_Session\_Establish\_Request message to the UPF1, and the UPF1 will allocate the parameters and send them to the SMF in the response message, then the SMF will forward them to the UPF2 in the Nupf\_Session\_Establish\_Request message. +- 5 The UPF2 will also allocate the parameters and send them to the SMF in the Nupf\_Session\_Establish\_Response message and the SMF will forward them to the UPF1. + +## 8.9 Session update + +The session update procedure shall be used to update a session between the SMF and the UPF and update the related rules in the UPF so that the UPF can handle the incoming packets using new rules. + +![Sequence diagram for Session update procedure between SMF and UPF. The SMF sends a Nupf_Session_Update_Request to the UPF. The UPF performs an internal step 'Update the related parameters' and then sends a Nupf_Session_Update_Response back to the SMF. The diagram is labeled Q.5025(22).](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant UPF + Note right of UPF: 2. Update the related parameters + SMF->>UPF: 1. Nupf_Session_Update_Request + UPF-->>SMF: 3. Nupf_Session_Update_Response + Note right of UPF: Q.5025(22) + +``` + +Sequence diagram for Session update procedure between SMF and UPF. The SMF sends a Nupf\_Session\_Update\_Request to the UPF. The UPF performs an internal step 'Update the related parameters' and then sends a Nupf\_Session\_Update\_Response back to the SMF. The diagram is labeled Q.5025(22). + +**Figure 8-9 – Session update procedure** + +- 1 SMF sends Nupf\_Session\_Update\_Request message to the UPF to set up a session between the SMF and the UPF. The SMF assigns new parameters such as a new QoS and provides them to the UPF. +- 2 Once received the Nupf\_Session\_Update\_Request message, the UPF will save the related new parameters received from the SMF and update the context for the PDU session. +- 3 The UPF sends a Nupf\_Session\_Establishment\_Response message containing any information that the UPF shall provide to the SMF, such as the UE IP address if it is allocated by the UPF. + +## 8.10 Session release + +The session release procedure shall be used to release the session between the SMF and the UPF and release the related context in the SMF and the UPF. The detail of the procedure is shown in Figure 8-10. + +![Sequence diagram for Session release procedure between SMF and UPF. The SMF sends a Nupf_Session_Release_Request to the UPF. The UPF performs an internal step 'Release the related context' and then sends a Nupf_Session_Release_Response back to the SMF. The diagram is labeled Q.5025(22).](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant UPF + Note right of UPF: 2. Release the related context + SMF->>UPF: 1. Nupf_Session_Release_Request + UPF-->>SMF: 3. Nupf_Session_Release_Response + Note right of UPF: Q.5025(22) + +``` + +Sequence diagram for Session release procedure between SMF and UPF. The SMF sends a Nupf\_Session\_Release\_Request to the UPF. The UPF performs an internal step 'Release the related context' and then sends a Nupf\_Session\_Release\_Response back to the SMF. The diagram is labeled Q.5025(22). + +**Figure 8-10 – Session release procedure** + +- 1 SMF sends Nupf\_Session\_Release\_Request message to the UPF to release the session between the SMF and the UPF and release the related context in the SMF and the UPF. +- 2 The UPF deletes any context related to the PDU session. Optionally, the core network tunnel for local area networks can also be released when the release message is received. +- 3 The UPF sends a Nupf\_Session\_Release\_Response message to the SMF. + +## 8.11 Local area network tunnel set-up between UPFs + +This procedure will be used to establish an IMT-2020 local area network (LAN) tunnel between UPFs. An IMT-2020 local area can provide a group of users with a local area network through an IMT-2020 network. When users within the group communicate with each other, they can directly exchange data packets within the network. When this group of users is under two different PDU session anchor UPFs which provide IMT-2020 local area network type services, a core network tunnel + +for the IMT-2020 local area network needs to be established between them to forward data for the group of users. The detail of the procedure is shown in Figure 8-11. + +![Sequence diagram showing the local area network tunnel set-up procedure between SMF, UPF1, and UPF2. The steps are: 1. SMF sends Nupf_LAN_Tunnel_Establish_Request to UPF1; 2. UPF1 sends Nupf_LAN_Tunnel_Establish_Response to SMF; 3. SMF sends Nupf_LAN_Tunnel_Establish_Request to UPF2; 4. UPF2 sends Nupf_LAN_Tunnel_Establish_Response to SMF; 5. SMF sends Nupf_LAN_Tunnel_Establish_Completion to UPF1. The diagram is labeled Q.5025(22) at the bottom right.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant UPF1 + participant UPF2 + Note right of UPF2: Q.5025(22) + SMF->>UPF1: 1. Nupf_LAN_Tunnel_Establish_Request + UPF1-->>SMF: 2. Nupf_LAN_Tunnel_Establish_Response + SMF->>UPF2: 3. Nupf_LAN_Tunnel_Establish_Request + UPF2-->>SMF: 4. Nupf_LAN_Tunnel_Establish_Response + SMF->>UPF1: 5. Nupf_LAN_Tunnel_Establish_Completion + +``` + +Sequence diagram showing the local area network tunnel set-up procedure between SMF, UPF1, and UPF2. The steps are: 1. SMF sends Nupf\_LAN\_Tunnel\_Establish\_Request to UPF1; 2. UPF1 sends Nupf\_LAN\_Tunnel\_Establish\_Response to SMF; 3. SMF sends Nupf\_LAN\_Tunnel\_Establish\_Request to UPF2; 4. UPF2 sends Nupf\_LAN\_Tunnel\_Establish\_Response to SMF; 5. SMF sends Nupf\_LAN\_Tunnel\_Establish\_Completion to UPF1. The diagram is labeled Q.5025(22) at the bottom right. + +**Figure 8-11 – Local area network tunnel set-up between UPFs procedure** + +- 1 In order to set up a core network tunnel between two UPFs for the IMT-2020 local area network, SMF firstly sends a Nupf\_LAN\_Tunnel\_Establish\_Request message to UPF1. Since the tunnel parameters can be allocated by the UPF, then the parameters will not be included in the Nupf\_LAN\_Tunnel\_Establish\_Request message to UPF1. +- 2 UPF1 receives the request message and allocates the tunnel parameters and sends them back to the SMF in the response message. +- 3 Then the SMF sends the Nupf\_LAN\_Tunnel\_Establish\_Request message including the tunnel parameters to UPF2. +- 4 UPF2 receives the request message and saves the parameters allocated by UPF1, from which the UPF2 knows the destination when forwarding data packets. Then UPF2 allocates the tunnel parameters and sends them back to the SMF in the response message. +- 5 SMF forwards the tunnel parameters allocated by UPF2 to UPF1. + +## 8.12 UPF event exposure + +UPF can expose real-time network information to a 3rd party via the capability exposure function (CEF), e.g., PDU session information (QoS profile) or end-to-end latency. CEF may establish a session with the UPF based on the UPF ID / FQDN and communicate directly with the UPF to get the corresponding PDU session information in order to achieve low latency information exposure. The procedure is shown in Figure 8-12. + +![Sequence diagram for UPF information exposure procedure. Lifelines: UPF, NFR, CEF, Third party. The sequence starts with the Third party sending a '1. Subscribe UPF exposure information' message to the CEF. The CEF then sends a '2. Request UPF address' to the NFR, which responds with '3. Response UPF address'. The CEF then sends a '4. Nupf_Eventexposure_Subscribe' message to the UPF. The UPF responds with '5. Nupf_Eventexposure_Notify' to the CEF, which finally sends '6. Response exposure information' to the Third party. The diagram is labeled Q.5025(22) at the bottom right.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant Third party + participant CEF + participant NFR + participant UPF + Note right of Third party: Q.5025(22) + Third party->>CEF: 1. Subscribe UPF exposure information + CEF->>NFR: 2. Request UPF address + NFR-->>CEF: 3. Response UPF address + CEF->>UPF: 4. Nupf_Eventexposure_Subscribe + UPF-->>CEF: 5. Nupf_Eventexposure_Notify + CEF-->>Third party: 6. Response exposure information + +``` + +Sequence diagram for UPF information exposure procedure. Lifelines: UPF, NFR, CEF, Third party. The sequence starts with the Third party sending a '1. Subscribe UPF exposure information' message to the CEF. The CEF then sends a '2. Request UPF address' to the NFR, which responds with '3. Response UPF address'. The CEF then sends a '4. Nupf\_Eventexposure\_Subscribe' message to the UPF. The UPF responds with '5. Nupf\_Eventexposure\_Notify' to the CEF, which finally sends '6. Response exposure information' to the Third party. The diagram is labeled Q.5025(22) at the bottom right. + +**Figure 8-12 – UPF information exposure procedure** + +- 1 3rd party applications request / subscribe to the CEF for PDU information exposure of specific UE and a specific PDU session. It may include the UE IP address, network exposure information indication which indicates information 3rd party request, e.g., QoS profile, end-to-end latency for specific QoS flow, or air-interface latency for specific QoS flow. +- 2 When the CEF receives the UPF ID, the CEF may request the NFR to get the UPF address. +- 3 NFR responds to the UPF address to CEF. +- 4 CEF may initiate a session establishment (an interface) with the UPF based on the UPF address. The CEF may request the PDU session information e.g., user plane latency or QoS profile, directly to the UPF for specific a UE PDU session by invoking Nupf\_Eventexposure\_Subscribe. +- 5 The UPF responds to the related required information to the CEF. +- 6 CEF responds to the related required information to the 3rd party applications. + +## 8.13 Customized UPF service registration + +Customized UPF service registration is implemented by the NFR as shown in Figure 8-13. NFR will notify the 3rd party via CEF. + +![Sequence diagram for Customized UPF service registration procedure. Lifelines: UPF, NFR, CEF, Third party. The sequence starts with '0. Customized service installation' in the UPF. The UPF then sends a '1. Nnfr_CustomizedService_Registration_Request' to the NFR, which responds with '2. Nnfr_CustomizedService_Registration_Response'. The NFR then sends a '3. CustomizedService_Registration_Notify' message to the CEF, which finally sends a '4. Customized UPF service registration notify' message to the Third party. The diagram is labeled Q.5025(22) at the bottom right.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +``` + +sequenceDiagram + participant Third party + participant CEF + participant NFR + participant UPF + Note right of UPF: 0. Customized service installation + Note right of Third party: Q.5025(22) + UPF->>NFR: 1. Nnfr_CustomizedService_Registration_Request + NFR-->>UPF: 2. Nnfr_CustomizedService_Registration_Response + NFR->>CEF: 3. CustomizedService_Registration_Notify + CEF-->>Third party: 4. Customized UPF service registration notify + +``` + +Sequence diagram for Customized UPF service registration procedure. Lifelines: UPF, NFR, CEF, Third party. The sequence starts with '0. Customized service installation' in the UPF. The UPF then sends a '1. Nnfr\_CustomizedService\_Registration\_Request' to the NFR, which responds with '2. Nnfr\_CustomizedService\_Registration\_Response'. The NFR then sends a '3. CustomizedService\_Registration\_Notify' message to the CEF, which finally sends a '4. Customized UPF service registration notify' message to the Third party. The diagram is labeled Q.5025(22) at the bottom right. + +**Figure 8-13 – Customized UPF service registration procedure** + +- 0 Customized services from a 3rd party are installed in the UPF. +- 1 UPF invokes Nnfr\_CustomizedService\_Registration\_Request to send services information to the NFR. The message includes information of the available customized UPF services + +(e.g., UPF time-sensitive network translator service), UPF serving area, network slice type indicator, DNN, interface, UPF ID and the UPF address. + +- 2 NFR invokes Nnfr\_CustomizedService\_Registration\_Response to inform the UPF of the success or failure of the customized services registration. +- 3 NFR invokes CustomizedService\_Registration\_Notify to notify the CEF of the complement of customized service registration. +- 4 CEF informs the 3rd party of the success of the customized services registration. + +## 8.14 Customized UPF service deregistration + +Customized UPF service deregistration is implemented by the NFR as shown in Figure 8-14. NFR will notify the 3rd party via CEF. + +![Sequence diagram for Customized UPF service deregistration procedure. Lifelines: UPF, NFR, CEF, Third party. 1. UPF to NFR: Nnfr_CustomizedService_Deregistration_Request. 2. NFR to UPF: Nnfr_CustomizedService_Deregistration_Response. 3. NFR to CEF: CustomizedService_Deregistration_Notify. 4. CEF to Third party: Customized UPF service deregistration notify. Q.5025(22)](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +``` +sequenceDiagram + participant UPF + participant NFR + participant CEF + participant Third party + Note right of Third party: Q.5025(22) + UPF->>NFR: 1. Nnfr_CustomizedService_Deregistration_Request + NFR-->>UPF: 2. Nnfr_CustomizedService_Deregistration_Response + NFR->>CEF: 3. CustomizedService_Deregistration_Notify + CEF->>Third party: 4. Customized UPF service deregistration notify +``` + +Sequence diagram for Customized UPF service deregistration procedure. Lifelines: UPF, NFR, CEF, Third party. 1. UPF to NFR: Nnfr\_CustomizedService\_Deregistration\_Request. 2. NFR to UPF: Nnfr\_CustomizedService\_Deregistration\_Response. 3. NFR to CEF: CustomizedService\_Deregistration\_Notify. 4. CEF to Third party: Customized UPF service deregistration notify. Q.5025(22) + +**Figure 8-14 – Customized UPF service deregistration procedure** + +- 1 UPF invokes Nnfr\_CustomizedService\_Deregistration\_Request to send services information to NFR. The message includes a list of unavailable customized services of the UPF. +- 2 NFR deregisters customized services and sends a response to the UPF to inform of the success or failure of the customized services deregistration by invoking Nnfr\_CustomizedService\_Deregistration\_Response. +- 3 NFR invokes CustomizedService\_Deregistration\_notify to notify CEF of the customized service deregistration. +- 4 CEF informs the 3rd party of the result of customized services deregistration. + +## 8.15 DAF subscription to periodic UPF information + +Data analysis function (DAF) subscribes to the UPF information for data analysis and resource dispatch as shown in Figure 8-15. + +![Sequence diagram for DAF subscription to periodic UPF information procedure. Lifelines: Data analysis function, UPF. 1. Data analysis function to UPF: Nupf_Information_Subscribe. 2. UPF to Data analysis function: Nupf_Information_Notify. Q.5025(22)](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +``` +sequenceDiagram + participant DAF as Data analysis function + participant UPF + Note right of UPF: Q.5025(22) + DAF->>UPF: 1. Nupf_Information_Subscribe + UPF-->>DAF: 2. Nupf_Information_Notify +``` + +Sequence diagram for DAF subscription to periodic UPF information procedure. Lifelines: Data analysis function, UPF. 1. Data analysis function to UPF: Nupf\_Information\_Subscribe. 2. UPF to Data analysis function: Nupf\_Information\_Notify. Q.5025(22) + +**Figure 8-15 – DAF subscription to periodic UPF information procedure** + +- 1 Data analysis function subscribes to the UPF information by invoking Nupf\_Information\_Subscribe to create a new subscription. It includes the UPF node information, e.g., UPF throughout, node computing resource, node storage, session number, latency, access UPF or UPF service number of the UE, periodicity of subscription, UPF instance ID, UE location and other information DAF subscribes. +- 2 UPF notifies the data analysis function by invoking Nupf\_Information\_Notify service operation. + +## 8.16 DAF unsubscription to UPF information + +DAF unsubscribes to the UPF information as shown in Figure 8-16. + +![Sequence diagram for DAF unsubscription to UPF information procedure. The diagram shows two lifelines: 'Data analysis function' on the left and 'UPF' on the right. The interaction consists of two messages: 1. Nupf_Information_Unsubscribe_Request from the Data analysis function to the UPF, and 2. Nupf_Information_Unsubscribe_Response from the UPF back to the Data analysis function. The diagram is labeled Q.5025(22) at the bottom right.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant DAF as Data analysis function + participant UPF + Note right of UPF: Q.5025(22) + DAF->>UPF: 1. Nupf_Information_Unsubscribe_Request + UPF-->>DAF: 2. Nupf_Information_Unsubscribe_Response + +``` + +Sequence diagram for DAF unsubscription to UPF information procedure. The diagram shows two lifelines: 'Data analysis function' on the left and 'UPF' on the right. The interaction consists of two messages: 1. Nupf\_Information\_Unsubscribe\_Request from the Data analysis function to the UPF, and 2. Nupf\_Information\_Unsubscribe\_Response from the UPF back to the Data analysis function. The diagram is labeled Q.5025(22) at the bottom right. + +**Figure 8-16 – DAF unsubscription to the UPF information procedure** + +- 1 Data analysis function unsubscribes to the UPF information by invoking Nupf\_Information\_Unsubscribe\_Request. +- 2 UPF informs the data analysis function of the result of the unsubscription by invoking Nupf\_Information\_Unsubscribe\_Response. + +## 8.17 DAF request for the UPF information + +DAF requests for the UPF information as needed as shown in Figure 8-17. + +![Sequence diagram for DAF request for the UPF information procedure. The diagram shows two lifelines: 'Data analysis function' on the left and 'UPF' on the right. The interaction consists of two messages: 1. Nupf_Information_Request from the Data analysis function to the UPF, and 2. Nupf_Information_Response from the UPF back to the Data analysis function. The diagram is labeled Q.5025(22) at the bottom right.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +``` + +sequenceDiagram + participant DAF as Data analysis function + participant UPF + Note right of UPF: Q.5025(22) + DAF->>UPF: 1. Nupf_Information_Request + UPF-->>DAF: 2. Nupf_Information_Response + +``` + +Sequence diagram for DAF request for the UPF information procedure. The diagram shows two lifelines: 'Data analysis function' on the left and 'UPF' on the right. The interaction consists of two messages: 1. Nupf\_Information\_Request from the Data analysis function to the UPF, and 2. Nupf\_Information\_Response from the UPF back to the Data analysis function. The diagram is labeled Q.5025(22) at the bottom right. + +**Figure 8-17 – DAF request for the UPF information procedure** + +- 1 Data analysis function requests for the UPF information by invoking Nupf\_Information\_Request. It may include the UPF node information or the UPF service information. +- 2 UPF sends a response to the DAF by invoking Nupf\_Information\_Response. + +## 8.18 UPF information notification + +UPF reports the KPI information to the network management by invoking UPF\_Information\_Notification. + +![Sequence diagram for Figure 8-18: UPF reports the KPI to the network management procedure. The diagram shows two lifelines: UPF and Network management. The UPF sends a '1. Nupf_Information_Notification_Request' message to the Network management. The Network management responds with a '2. Nupf_Information_Notification_Response' message. The diagram is labeled Q.5025(22).](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +sequenceDiagram + participant UPF + participant Network management + Note right of Network management: Q.5025(22) + UPF->>Network management: 1. Nupf_Information_Notification_Request + Network management-->>UPF: 2. Nupf_Information_Notification_Response + +``` + +Sequence diagram for Figure 8-18: UPF reports the KPI to the network management procedure. The diagram shows two lifelines: UPF and Network management. The UPF sends a '1. Nupf\_Information\_Notification\_Request' message to the Network management. The Network management responds with a '2. Nupf\_Information\_Notification\_Response' message. The diagram is labeled Q.5025(22). + +**Figure 8-18 – UPF reports the KPI to the network management procedure** + +- 1 UPF invokes Nupf\_Information\_Notification\_Request to send the KPI to the network management. It includes the UPF key performance information, e.g., UPF throughout, node computing resource, node storage, session number, latency, and access UPF/UPF service number of the UE. +- 2 Network management sends Nupf\_Information\_Notification\_Response to the UPF to inform the result of the KPI report. + +## 8.19 Network management triggered UPF energy saving + +Network management monitors the resource usage of the UPFs and would trigger the UPF energy saving service when the resource usage is low (e.g., resource usage is less than a certain threshold). + +![Sequence diagram for Figure 8-19: Network management triggered UPF energy saving procedure. The diagram shows three lifelines: UPFs, Network management, and Data analysis function. The process starts with '0. UPF information monitoring' by Network management. Network management sends '1. Ndaf_Energy_Saving_Analysis_Request' to the Data analysis function. The Data analysis function performs '2. UPFs resource requirement and energy saving analysis' and sends '3. Ndaf_Energy_Saving_Analysis_Response' back to Network management. Network management then performs '4. Decide energy-saving policies for UPF instances' and sends '5. Nupf_Energy_Saving_Request' to the UPFs. The UPFs respond with '6. Nupf_Energy_Saving_Response'. The diagram is labeled Q.5025(22).](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` + +sequenceDiagram + participant UPFs + participant Network management + participant Data analysis function + Note right of Data analysis function: Q.5025(22) + Network management->>Data analysis function: 0. UPF information monitoring + Network management->>Data analysis function: 1. Ndaf_Energy_Saving_Analysis_Request + Data analysis function->>Data analysis function: 2. UPFs resource requirement and energy saving analysis + Data analysis function-->>Network management: 3. Ndaf_Energy_Saving_Analysis_Response + Network management->>Network management: 4. Decide energy-saving policies for UPF instances + Network management->>UPFs: 5. Nupf_Energy_Saving_Request + UPFs-->>Network management: 6. Nupf_Energy_Saving_Response + +``` + +Sequence diagram for Figure 8-19: Network management triggered UPF energy saving procedure. The diagram shows three lifelines: UPFs, Network management, and Data analysis function. The process starts with '0. UPF information monitoring' by Network management. Network management sends '1. Ndaf\_Energy\_Saving\_Analysis\_Request' to the Data analysis function. The Data analysis function performs '2. UPFs resource requirement and energy saving analysis' and sends '3. Ndaf\_Energy\_Saving\_Analysis\_Response' back to Network management. Network management then performs '4. Decide energy-saving policies for UPF instances' and sends '5. Nupf\_Energy\_Saving\_Request' to the UPFs. The UPFs respond with '6. Nupf\_Energy\_Saving\_Response'. The diagram is labeled Q.5025(22). + +**Figure 8-19 – Network management triggered UPF energy saving procedure** + +- 0 Network management monitors the UPF KPI information and justifies the energy-saving requirements of the UPF instances. +- 1 Network management invokes Ndaf\_Energy\_Saving\_Analysis\_Request to trigger the energy-saving analysis for those UPF instances with low resource usage. +- 2 DAF analyses and predicts resource requirements and the consumed energy for the UPF instances based on the UPF information (e.g., UPF throughout, session number and resource usage) provided by the UPF, and energy consumption provided by the network management. +- 3 DAF sends Ndaf\_Energy\_Saving\_Analysis\_Response to the network management to inform the analysis result of the resource and energy for the UPF instances. + +- 4 Network management decides the energy saving policies for the UPF instances, which may include decreasing at least one type of the resources configuration, load migration and redirection, deactivating the idle UPF instances, or other energy-saving mechanisms. +- 5 Network management sends Nupf\_Energy\_Saving\_Request to the UPF to trigger energy saving operations. +- 6 UPF gives the energy saving policies execution feedback by invoking Nupf\_Energy\_Saving\_Response. + +# 9 Message format + +## 9.1 UPF service registration + +This message is sent to the network function registry function (NFR) to register the UPF services in the core network. Core network function can be discovered and interact with the UPF. + +Table 9-1 describes the detailed information of Nfr\_NFService\_Registration\_Request: + +**Table 9-1 – Nfr\_NFService\_Registration\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|----------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates a list of UPF service instances which register in the NFR | +| Network slice type indicator | M | string | 1... N | Indicates the network slices to which the UPF services are serving for | +| DNN | M | string | 1... N | Indicates the data network names to which the UPF services are serving for | +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | +| Service serving area | M | string | 1... N | Indicates the serving area of each UPF services instance | + +Table 9-2 describes the detailed information of Nfr\_NFService\_Registration\_Response: + +**Table 9-2 – Nfr\_NFService\_Registration\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the UPF services.
201 Created
400 Input parameter error
500 Server internal error | + +## 9.2 UPF service update + +This message is sent to the NFR to update the UPF services in the core network. Table 9-3 describes the detailed information of Nfr\_NFService\_Update\_Request: + +**Table 9-3 – Nfr\_NFService\_Update\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|------------------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of UPF service instances which are updated | +| Network slice type indicator | O | string | 1... N | Indicates the network slices to which the updated UPF services are serving for | +| DNN | O | string | 1... N | Indicates the data network names to which the updated UPF services are serving for | +| UPF ID | O | string | 1 | Indicates the UPF identifier to which the updated UPF services belong to | +| UPF address | O | string | 1 | Indicates the UPF address to which the updated UPF services belong to | +| Service serving area | O | string | 1... N | Indicates the serving area of each updated UPF services instance | + +Table 9-4 describes the detailed information of Nfr\_NFService\_Update\_Response: + +**Table 9-4 – Nfr\_NFService\_Update\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the update of the UPF service.
201 Created
400 Input parameter error
500 Server internal error | + +## 9.3 UPF service deregistration + +This message is sent to the NFR to the deregistered UPF services in the core network. Table 9-5 describes the detailed information of Nfr\_NFService\_Deregistration\_Request: + +**Table 9-5 – Nfr\_NFService\_Deregistration\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|-----------------------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of the UPF service instances which is deregistered | +| Network slice type indicator | O | string | 1... N | Indicates the network slices to which the deregistered UPF services are serving for | +| DNN | O | string | 1... N | Indicates the data network names to which the deregistered UPF services are serving for | + +Table 9-6 describes the detailed information of Nfr\_NFService\_Deregistration\_Response: + +**Table 9-6 – Nfr\_NFService\_Deregistration\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
500 | Indicates the success or failure of the deregistration of the UPF service.
200 OK
400 Input parameter error
500 Server internal error | + +## 9.4 UPF service discovery + +This message is sent to the NFR to discover the UPF services. Table 9-7 describes the detailed information of Nfr\_NFService\_Discovery\_Request: + +**Table 9-7 – Nfr\_NFService\_Discovery\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|------------------------------------------------------------------------------| +| NF type | M | string | 1... N | Indicates the NF type of the NF discovery which is the UPF in this procedure | +| UPF ID | O | string | 1... N | Indicates the UPF identifier of the target UPF | +| UPF service instance | O | string | 1... N | Indicates the instance of the UPF service which is the NF consumer discovery | +| UPF serving area | O | string | 1... N | Indicates the serving area of the target UPF | +| Network slice type indicator | O | string | 1... N | Indicates the network slices to which the target UPF services belong to | +| DNN | O | string | 1... N | Indicates the data network names to which the target UPF services belong to | + +**Table 9-7 – Nfr\_NFService\_Discovery\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|-----------------------------------------------------------------------------------------------| +| UPF address | O | string | 1... N | Indicates the UPF address which can be either the IP address or the FQDN | +| UE IP address | O | string | 1... N | Indicates the IP address of the UE which established the PDU session in the target UPF | +| PLMN ID | O | string | 1... N | Indicates the PLMN identifier of the UPF | +| Application ID | O | string | 1... N | Indicates the application identifier to which the target UPF has the PDU session to serve for | + +Table 9-8 describes the detailed information of Nfr\_NFService\_Discovery\_Response: + +**Table 9-8 – Nfr\_NFService\_Discovery\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
500 | Indicates the success or failure of the UPF service discovery.
200 OK
400 Input parameter error
500 Server internal error | +| UPF lists | M | string | 1... N | N/A | Indicates the discovery results of the UPF discovery. | + +## 9.5 UPF node transmission path set-up + +These messages are used to set up a node level path between the SMF and the UPF, then the SMF can use the resources of the UPF subsequently. + +Table 9-9 describes the detailed information of Nupf\_Node\_Transmission\_path\_Setup\_Request: + +**Table 9-9 – Nupf\_Node\_Transmission\_path\_Setup\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of the UPF service instances which register in NFR | +| Transmission path ID | M | num | 1 | Indicates the number of this node association. | +| Network slice type indicator | M | string | 1... N | Indicates the network slices to which the UPF services are serving for | +| SMF ID | M | string | 1... N | Indicates the SMF identifier | + +**Table 9-9 – Nupf\_Node\_Transmission\_path\_Setup\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|------------------------------------------------------------------| +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | +| SMF features | M | string | 1... N | Indicates the list of optional features that the SMF supports | + +Table 9-10 describes the detailed information of Nupf\_Node\_Transmission\_path\_Setup\_Response: + +**Table 9-10 – Nupf\_Node\_Transmission\_path\_Setup\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|----------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the UPF service.
201 Created
400 Input parameter error
500 Server internal error | +| Transmission path ID | M | num | 1 | N/A | Indicates the number of this node transmission path. | +| UPF features | M | string | 1... N | N/A | Indicates the list of optional features that the UPF supports | + +## 9.6 UPF node transmission path update + +These messages are used to update a node level path between the SMF and the UPF. Table 9-11 describes the detailed information of Nupf\_Node\_Transmission\_path\_Update\_Request: + +**Table 9-11 – Nupf\_Node\_Transmission\_path\_Update\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|--------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of the UPF service instance which register in the NFR | +| Transmission path ID | M | num | 1 | Indicates the number of this node transmission path. | +| Network slice type indicator | M | string | 1... N | Indicates the network slices to which the UPF services are serving for | +| SMF ID | M | string | 1... N | Indicates the SMF identifier | + +**Table 9-11 – Nupf\_Node\_Transmission\_path\_Update\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|------------------------------------------------------------------| +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | +| SMF features | M | string | 1... N | Indicates the list of optional features that the SMF supports | + +Table 9-12 describes the detailed information of Nupf\_Node\_Transmission\_path\_Update\_Response: + +**Table 9-12 – Nupf\_Node\_Transmission\_path\_Update\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|----------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the UPF service.
201 Created
400 Input parameter error
500 Server internal error | +| Transmission path ID | M | num | 1 | N/A | Indicates the number of this node transmission path. | +| UPF features | M | string | 1... N | N/A | Indicates the list of optional features that the UPF supports | + +## 9.7 UPF node transmission path release + +These messages are used to release a node level path between the SMF and the UPF due to e.g., OAM reasons. + +Table 9-13 describes the detailed information of Nupf\_Node\_Transmission\_path\_Release\_Request: + +**Table 9-13 – Nupf\_Node\_Transmission\_path\_Release\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|----------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of UPF service instance which register in the NFR | +| SMF ID | M | string | 1... N | Indicates the SMF identifier | +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | + +Table 9-14 describes the detailed information of Nupf\_Node\_Transmission\_path\_Release\_Response: + +**Table 9-14 – Nupf\_Node\_Transmission\_path\_Release\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
500 | Indicates the success or failure of the registration of the UPF service.
200 OK
400 Input parameter error
500 Server internal error | + +## 9.8 Session establishment + +These messages are used to set up a session between the SMF and the UPF and configured the rules in the UPF so that the UPF can handle the incoming packets. This message can also be used to establish a core network tunnel for local area networks between two UPFs. + +Table 9-15 describes the detailed information of Nupf\_Session\_Establish\_Request: + +**Table 9-15 – Nupf\_Session\_Establish\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|----------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of UPF service instances which register in the NFR | +| Network slice type indicator | M | string | 1... N | Indicates the network slices to which the UPF services are serving for | +| DNN | M | string | 1... N | Indicates the data network names to which the UPF services are serving for | +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | +| PDU session ID | M | string | 1... N | Indicates the identifier of the PDU session | +| Rules | M | string | 1... N | Indicates the rules such as QoS, charging rules | +| Tunnel parameters | O | string | 1 | Indicates the tunnel parameters that the UPF allocated | + +Table 9-16 describes the detailed information of Nupf\_Session\_Establish\_Response: + +**Table 9-16 – Nupf\_Session\_Establish\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the UPF service.
201 Created
400 Input parameter error | + +**Table 9-16 – Nupf\_Session\_Establish\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|------------|--------------------------------------------------------| +| | | | | | 500 Server internal error | +| UE IP address | O | string | 1 | N/A | Indicates the UE IP address that the UPF allocated | +| Tunnel parameters | O | string | 1 | N/A | Indicates the tunnel parameters that the UPF allocated | + +## 9.9 Session update + +These messages are used to update a session between the SMF and the UPF and update the related rules in the UPF so that the UPF can handle the incoming packets using new rules. + +Table 9-17 describes the detailed information of Nupf\_Session\_Update\_Request: + +**Table 9-17 – Nupf\_Session\_Update\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|----------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of UPF service instances which register in the NFR | +| Network slice type indicator | M | string | 1... N | Indicates the network slices to which the UPF services are serving for | +| DNN | M | string | 1... N | Indicates the data network names to which the UPF services are serving for | +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | +| PDU session ID | M | string | 1... N | Indicates the identifier of the PDU session | +| Rules | M | string | 1... N | Indicates the rules such as QoS, charging rules | +| Tunnel parameters | O | string | 1 | Indicates the tunnel parameters that UPF allocated | + +Table 9-18 describes the detailed information of Nupf\_Session\_Update\_Response: + +**Table 9-18 – Nupf\_Session\_Update\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the UPF service.
201 Created
400 Input parameter error
500 Server internal error | +| UE IP address | O | string | 1 | N/A | Indicates the UE IP address that the UPF allocated | +| Tunnel parameters | O | string | 1 | N/A | Indicates the tunnel parameters that the UPF allocated | + +## 9.10 Session release + +These messages are used to release the session between the SMF and the UPF and release the related context in the SMF and the UPF. + +Table 9-19 describes the detailed information of Nupf\_Session\_Release\_Request: + +**Table 9-19 – Nupf\_Session\_Release\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|-----------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of UPF service instances which register in the NFR | +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | +| PDU session ID | M | string | 1... N | Indicates the identifier of the PDU session | + +Table 9-20 describes the detailed information of Nupf\_Session\_Release\_Response: + +**Table 9-20 – Nupf\_Session\_Release\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
500 | Indicates the success or failure of the registration of the UPF service.
200 OK
400 Input parameter error
500 Server internal error | + +## 9.11 Local area network tunnel set-up between UPFs + +These messages are used to establish a core network tunnel for the IMT-2020 local area network, then users can directly exchange data packets within the network. + +Table 9-21 describes the detailed information of Nupf\_LAN\_Tunnel\_Establish\_Request: + +**Table 9-21 – Nupf\_LAN\_Tunnel\_Establish\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|---------------------------------------------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of UPF service instances which register in the NFR | +| Network slice type indicator | M | string | 1... N | Indicates the network slices to which the UPF services are serving for | +| DNN | M | string | 1... N | Indicates the data network names to which the UPF services are serving for | +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the UPF services belong to | +| UPF address | M | string | 1 | Indicates the UPF address to which services belong to | +| PDU session ID | M | string | 1... N | Indicates the identifier of the PDU session | +| Rules | M | string | 1... N | Indicates the rules such as QoS, charging rules | +| Tunnel parameters | O | string | 1 | Indicates the parameters that the UPF allocated of the core network tunnel between the UPFs in the same group | + +Table 9-22 describes the detailed information of Nupf\_LAN\_Tunnel\_Establish\_Response: + +**Table 9-22 – Nupf\_LAN\_Tunnel\_Establish\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the UPF service.
201 Created
400 Input parameter error
500 Server internal error | +| Tunnel parameters | O | string | 1 | N/A | Indicates the parameters of the core network tunnel between the UPFs in the same group that the UPF allocated | + +Table 9-23 describes the detailed information of Nupf\_LAN\_Tunnel\_Establish\_Completion: + +**Table 9-23 – Nupf\_LAN\_Tunnel\_Establish\_Completion** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the UPF service.
201 Created
400 Input parameter error
500 Server internal error | +| Tunnel parameters | O | string | 1 | N/A | Indicates the parameters of the core network tunnel between the UPFs in the same group that the UPF allocated | + +## 9.12 UPF event exposure + +This message is for CEF, 3rd party applications or other network functions to get the UPF information based on some events. Table 9-24 and Table 9-25 describes the detailed information of Nupf\_Eventexposure\_Subscribe and Nupf\_Eventexposure\_Notify: + +**Table 9-24 – Nupf\_Eventexposure\_Subscribe** + +| Information element | Status | Data type | Cardinality | Description | +|--------------------------------|--------|-----------|-------------|----------------------------------------------------------------------------| +| Request information indication | M | string | 1... N | Indicates the list of information which the UPF can expose. | +| IP address | M | string | 1... N | Indicates which PDU session is the target for such information exposure. | +| DNN | M | string | 1... N | Indicates the data network names to which the UPF services are serving for | +| Network slice type indicator | M | string | 1 | Indicates which network slice is related to such exposure request. | + +**Table 9-25 – Nupf\_Eventexposure\_Notify** + +| Information element | Status | Data type | Cardinality | Description | +|-----------------------------------|--------|-----------|-------------|--------------------------------------------------------------------------------| +| The requested network information | M | string | 1 | The information that the consumer NF requested for the UPF exposure. | +| Correlation ID | M | num | 1... N | The correlation ID for such interaction between the UPF and the requested NFs. | + +## 9.13 Customized UPF service registration + +This message is sent to the NFR to register the customized UPF services. Core network functions can be discovered and interact with the customized services. + +Table 9-26 describes the detailed information of Nnfr\_CustomizedService\_Registration\_Request. + +**Table 9-26 – Nnfr\_CustomizedService\_Registration\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|-------------------------------------------------------------------------------------| +| Customized UPF service | M | string | 1... N | Indicates the list of customized service instances which register in the NFR | +| Network slice type indicator | M | string | 1... N | Indicates the network slices which the customized UPF services are serving for | +| DNN | M | string | 1... N | Indicates the data network names which the customized UPF services are serving for | +| Service serving area | M | string | 1... N | Indicates the serving area of each customized UPF services instances | +| 3 rd party | M | string | 1 | Indicates the 3 rd party name to which the customized services belong to | + +Table 9-27 describes the detailed information of Nnfr\_CustomizedService\_Registration\_Response: + +**Table 9-27 – Nnfr\_CustomizedService\_Registration\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the registration of the customized UPF service.
201 Created
400 Input parameter error
500 Server internal error | + +Table 9-28 describes the detailed information of CustomizedService\_Registration\_Notify. + +**Table 9-28 – CustomizedService\_Registration\_Notify** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|-------------------------------------------------------------------------------------| +| Customized UPF service | M | string | 1... N | Indicates the list of customized service instances which register in the NFR | +| Network slice type indicator | M | string | 1... N | Indicates the network slices which the customized UPF services are serving for | +| DNN | M | string | 1... N | Indicates the data network names which the customized UPF services are serving for | +| Service serving area | M | string | 1... N | Indicates the serving area of each customized UPF services instances | +| UPF ID | M | string | 1 | Indicates the UPF identifier to which the customized UPF services belong to | +| 3 rd party | M | string | 1 | Indicates the 3 rd party name to which the customized services belong to | + +## 9.14 Customized UPF service deregistration + +This message is sent to the NFR to deregister the customized UPF services. Table 9-29 describes the detailed information of Nnfr\_CustomizedService\_Deregistration\_Request: + +**Table 9-29 – Nnfr\_CustomizedService\_Deregistration\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|--------------------------------------------------------------------------------------------------| +| Customized UPF service | M | string | 1... N | Indicates the list of customized UPF service instances which are deregistered | +| Network slice type indicator | O | string | 1... N | Indicates the network slices which the deregistered customized UPF services are serving for | +| DNN | O | string | 1... N | Indicates the data network names which the deregistered customized UPF services are serving for | +| 3 rd party | M | string | 1 | Indicates the 3 rd party name to which the deregistered customized services belong to | + +Table 9-30 describes the detailed information of Nnfr\_CustomizedService\_Deregistration\_Response: + +**Table 9-30 – Nnfr\_CustomizedService\_Deregistration\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
500 | Indicates the success or failure of the deregistration of the customized UPF service.
200 OK
400 Input parameter error
500 Server internal error | + +Table 9-31 describes the detailed information of CustomizedService\_Deregistration\_Notify. + +**Table 9-31 – CustomizedService\_Deregistration\_Notify** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------------|--------|-----------|-------------|-------------------------------------------------------------------------------------------------| +| Customized UPF service | M | string | 1... N | Indicates the list of customized UPF service instances which are deregistered | +| Network slice type indicator | O | string | 1... N | Indicates the network slices which the deregistered customized UPF services are serving for | +| DNN | O | string | 1... N | Indicates the data network names which the deregistered customized UPF services are serving for | + +**Table 9-31 – CustomizedService\_Deregistration\_Notify** + +| Information element | Status | Data type | Cardinality | Description | +|-----------------------|--------|-----------|-------------|-----------------------------------------------------------------------------------------------| +| 3 rd party | M | string | 1 | Indicates the 3 rd party name which the deregistered customized services belong to | + +## 9.15 DAF subscription to periodic UPF information + +This message is sent to the UPF to subscribe for information. Table 9-32 describes the details information of Nupf\_Information\_Subscribe: + +**Table 9-32 – Nupf\_Information\_Subscribe** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the UPF services instance which the DAF requests for | +| UPF information | M | string | 1... N | Indicates the UPF information report to the DAF. It may be UPF throughout, node computing resource, node storage, session number, latency, access UPF/UPF service number of the UE, UPF instance ID, UE location and other information of the UPF or UPF services | +| Periodicity | M | string | 1 | Periodicity of the UPF information report | + +Table 9-33 describes the detailed information of Nupf\_Information\_Notify: + +**Table 9-33 – Nupf\_Information\_Notify** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the UPF information subscription.
201 Created
400 Input parameter error
500 Server internal error | +| Time information | M | string | 1... N | N/A | Time information of the UPF information. | + +## 9.16 DAF unsubscription to UPF information + +This message is sent to the UPF to unsubscribe from the UPF information. + +Table 9-34 describes the detailed information of Nupf\_Information\_Unsubscribe\_Request: + +**Table 9-34 – Nupf\_Information\_Unsubscribe\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the UPF services instance which the DAF requests for | +| UPF information | M | string | 1... N | Indicates the UPF information which the DAF request for unsubscription | + +Table 9-35 describes the detailed information of Nupf\_Information\_Unsubscribe\_Response: + +**Table 9-35 – Nupf\_Information\_Unsubscribe\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
500 | Indicates the success or failure of the UPF information unsubscription
200 OK
400 Input parameter error
500 Server internal error | + +## 9.17 DAF request for UPF information + +This message is sent to the UPF to request for the UPF information as needed. + +Table 9-36 describes the detailed information of Nupf\_Information\_Request: + +**Table 9-36 – Nupf\_Information\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the UPF services instance which the DAF requests for | +| UPF information | M | string | 1... N | Indicates the UPF information which the DAF requests for. It may be UPF throughout, node computing resource, node storage, session number, latency, access UPF/UPF service number of the UE and other information of the UPF or UPF services | + +Table 9-37 describes the detailed information of Nupf\_Information\_Response: + +**Table 9-37 – Nupf\_Information\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the UPF information request.
201 Created
400 Input parameter error
500 Server internal error | +| UPF information | M | string | 1... N | N/A | Indicates the data and report sent by the UPF to the DAF. It may be UPF throughout, node computing resource, node storage, session number, latency, access UPF/UPF service number of the UE, UPF instance ID, UE location and other information of the UPF or UPF services | +| Time information | M | string | 1... N | N/A | Time information of the UPF information | + +## 9.18 UPF information notification + +This message is sent to the network management to report the KPI of the UPF through Nupf\_Information\_Notification. Table 9-38 describes the detailed information of Nupf\_Information\_Notification\_Request: + +**Table 9-38 – Nupf\_Information\_Notification\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UPF service instance | M | string | 1... N | Indicates the list of UPF service instances which report KPI information | +| UPF KPI | M | string | 1... N | Indicates the KPI information UPF services report to the network management. KPI information may be UPF throughout, node computing resource, node storage, session number, latency, access UPF/UPF service number of the UE and other information of the UPF or UPF services | + +Table 9-39 describes the detailed information of Nupf\_Information\_Notification\_Response: + +**Table 9-39 – Nupf\_Information\_Notification\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the core network data collection subscribe
201 Created
400 Input parameter error
500 Server internal error | + +## **9.19 Network management triggered UPF energy saving** + +This message of Ndaf\_Energy\_Saving\_Analysis\_Request is sent to the DAF to request energy-saving analysis for the UPF instances. + +Table 9-40 describes the detailed information of Ndaf\_Energy\_Saving\_Analysis\_Request. + +**Table 9-40 – Ndaf\_Energy\_Saving\_Analysis\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| UPF instance ID | M | string | 1... N | Indicates the UPF instance identifiers that triggered the UPF energy saving analysis | +| UPF EnSaReq | M | string | 1... N | Indicates the UPF energy saving analysis requirements. It may include the requirements of the predicted load and the corresponding resource and energy. | + +Table 9-41 describes the detailed information of Ndaf\_Energy\_Saving\_Analysis\_Response. + +**Table 9-41 – Ndaf\_Energy\_Saving\_Analysis\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the UPF energy saving analysis.
201 Created
400 Input parameter Error
500 Server internal error | +| UPF instance ID | M | string | 1... N | N/A | Indicate the UPF instance identifiers that have energy saving analysis in the response. | +| Analysis result | M | string | 1... N | N/A | Indicates the analysis result of the resource and energy for the energy-saving UPF. | +| Time information | M | string | 1... N | N/A | The time information of the UPF energy saving analysis. | + +This message of Nupf\_Energy\_Saving\_Request is sent to the UPF to issue the energy-saving policies. + +Table 9-42 describes the detailed information of Nupf\_Energy\_Saving\_Request. + +**Table 9-42 – Nupf\_Energy\_Saving\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| UPF instance ID | M | string | 1... N | Indicates the UPF instance identifiers that need to execute energy saving operations. | +| SMF instance ID | O | string | 1... N | Indicates the SMF instance identifiers that need to execute energy saving operations. | +| UPF PolExeReq | M | string | 1... N | Indicates the UPF energy saving policy execution requirements. It may include the UPF deactivating command. | +| SMF PolExeReq | O | string | 1... N | Indicates the UPF energy saving policy execution requirements in the SMF. It may include the load migration to increase resource usage. | + +Table 9-43 describes the detailed information of Nupf\_Energy\_Saving\_Response. + +**Table 9-43 – Nupf\_Energy\_Saving\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|----------------------------|---------------|------------------|--------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of the energy saving policies execution for the UPF.
201 Created
400 Input parameter error
500 Server internal error | + +# Bibliography + +- [b-ITU-T Q.5023] Recommendation ITU-T Q.5023 (2021), *Protocol for managing intelligent network slicing with AI-assisted analysis in IMT-2020 networks.* +- [b-ITU-T Q.5024] Recommendation ITU-T Q.5024 (2022), *Protocol for providing intelligent analysis services in IMT-2020 network.* +- [b-ITU-T Y.2011] Recommendation ITU-T Y.2011 (2004), *General principles and general reference model for Next Generation Networks.* +- [b-ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network.* +- [b-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.* +- [b-ITU-R M.2083-0] Recommendation ITU-R M.2083-0 (2015), *IMT Vision – Framework and overall objectives of the future development of IMT for 2020 and beyond.* + + + +## 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.5054-202502-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5054-202502-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ba77813b7d30b19a16061a60a0a15bc6da6aed2d --- /dev/null +++ b/marked/Q/T-REC-Q.5054-202502-I_PDF-E/raw.md @@ -0,0 +1,631 @@ + + +# Recommendation**ITU-T Q.5054 (02/2025)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Combating counterfeiting and stolen ICT devices + +--- + +### **Consumer-centric framework for combating counterfeit and stolen information and communication technology mobile devices** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +## **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.5054 + +# Consumer-centric framework for combating counterfeit and stolen information and communication technology mobile devices + +## Summary + +Recommendation ITU-T Q.5054 provides a consumer-centric framework through a unified platform considering possible scenarios and a multipronged approach for combating counterfeit and stolen mobile telecommunication/ICT devices. + +This Recommendation builds upon Recommendation ITU-T Q.5050, which offers a reference framework with high-level challenges and requirements that should be considered when deploying solutions to combat the circulation and use of counterfeit information and communication technology (ICT) devices. Furthermore, Recommendation ITU-T Q.5051 presents a 'Framework for combating the use of stolen mobile devices'. It also defines possible communication channels and consumer interfaces with platform, indicative query and response formats including approaches for consumer education and awareness. The Recommendation also covers key features of the platform, key security considerations, implementation scenarios and possible technical challenges related inter alia to vendor agnostic interfaces, mobile equipment bulk verification, dealing with devices with replicated unique identifiers and the reporting and handling of stolen or lost mobile telecommunication/ICT devices and their restoration upon recovery. + +With the rapid growth in the reach of the Internet and accelerated adoption and usage of ICT during the COVID-19 pandemic, the circulation and use of counterfeit ICT devices has increased considerably. According to an OECD report published in 2017, at that time already nearly one in five mobile phones shipped internationally was fake or counterfeit. The growing trade in counterfeit IT and communications hardware burdens on consumers, manufacturers and public finances. + +A counterfeit ICT device is a product that explicitly infringes the trademarks, copies hardware or software designs, or infringes brand or packaging rights of an original or authentic product and, in general, infringes applicable national and/or international technical standards, regulatory requirements or conformity processes, manufacturing licensing agreements or other applicable policy requirements. Major mobile telecommunication/ICT devices include inter alia smartphones, tablets, IoT devices, wearables, modems, dongles and wireless local area network (WLAN) routers with cellular network connectivity. In addition to counterfeit mobile telecommunication/ICT devices, the use of stolen devices in mobile network also poses a serious security and law and order problem. + +The unchecked proliferation of counterfeit and stolen mobile telecommunication/ICT devices in public land mobile networks (PLMNs) poses a serious challenge to regulators, law enforcement agencies (LEA) and end consumers and adversely affects the economy in general. The supply and demand economics of counterfeit and stolen devices complicate attempts to check the local as well as global market scenario for such devices. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.5054 | 2025-02-28 | 11 | 11.1002/1000/15946 | + +## Keywords + +Combat counterfeit ICT and stolen devices, unified framework. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 2 | +| 6 | General aspects ..... | 3 | +| 7 | Reference unified platform framework (RUPF) requirements..... | 4 | +| 7.1 | Type allocation code (TAC) database ..... | 4 | +| 7.2 | ICT device verification repository of brand owner or original equipment manufacturers ..... | 4 | +| 7.3 | National and international stolen device database..... | 5 | +| 7.4 | National unified platform with central EIR..... | 5 | +| 7.5 | Mobile network operator's equipment identity register..... | 6 | +| 7.6 | Stakeholder interface(s) for mobile telecommunication/ICT device verification..... | 6 | +| 8 | Reference unified platform framework (RUPF)..... | 7 | +| 8.1 | Reference unified platform framework overview ..... | 8 | +| 8.2 | Key platform features ..... | 11 | +| 9 | RUPF security and privacy considerations..... | 12 | +| Annex A | – Issues (aspects) and scenarios for the implementation of a reference unified platform framework..... | 13 | +| A.1 | Key considerations when implementing a reference unified platform framework..... | 13 | +| A.2 | Possible approaches for RUPF implementation ..... | 15 | +| Appendix I | – Analysis of the mobile telecommunication/ICT device ecosystem and the main stakeholders involved in the use of counterfeit and tampered mobile telecommunication/ICT devices ..... | 18 | +| I.1 | Mobile telecommunication/ICT device ecosystem and key stakeholders..... | 18 | +| I.2 | Impact of counterfeit and tampered devices on consumers..... | 20 | +| I.3 | Measures for mitigation of adverse impact on consumers ..... | 21 | +| Bibliography | ..... | 23 | + + + +## Recommendation ITU-T Q.5054 + +# Consumer-centric framework for combating counterfeit and stolen information and communication technology mobile devices + +# 1 Scope + +This Recommendation provides a framework to enable consumers to ubiquitously verify the authenticity of mobile telecommunication/ICT devices and provide a comprehensive overview to law enforcement agencies and regulators while enabling other stakeholders. The Recommendation will cover possible scenarios under which such mobile telecommunication/ICT devices may enter the mobile network ecosystem through any channel, emphasizing the need for a consumer centric approach to combat counterfeit, tampered and stolen mobile telecommunication/ICT devices including detection mechanisms for such devices with tampered/replicated unique identifiers. + +# 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.5050] Recommendation ITU-T Q.5050 (2019), *Framework for solutions to combat counterfeit ICT devices*. +- [ITU-T Q.5051] Recommendation ITU-T Q.5051 (2020), *Framework for combating the use of stolen mobile devices*. +- [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 terms defined elsewhere: + +**3.1.1 counterfeit ICT device** [ITU-T Q.5050]: An information and communication technology (ICT) device that explicitly infringes the trademark, copies hardware or software designs, or infringes brand or packaging rights of an original or authentic product and, in general, infringes applicable national and/or international technical standards, regulatory requirements or conformity processes, manufacturing licensing agreements, or other applicable legal requirements. + +**3.1.2 tampered ICT device** [ITU-T Q.5050]: An information and communication technology (ICT) device that had components, software, unique identifier, items protected by intellectual-protected rights or trademarks tentatively or effectively altered without the explicit consent of the manufacturer or its legal representative. + +**3.1.3 unique identifier** [ITU-T Q.5050]: An identifier associated with a single device that aims to uniquely identify it. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 replicated unique identifier:** A valid device identifier properly assigned by the responsible management entity to one device, but which is being used by other devices. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|----------------------------------------------------------| +| CEIR | Central Equipment Identity Register | +| CLI | Calling Line Identification | +| EIR | Equipment Identity Register | +| eUICC | embedded Universal Integrated Circuit Card | +| ICT | Information and Communications Technology | +| IMEI | International Mobile Equipment Identity | +| IMSI | International Mobile Subscriber Identity | +| IoT | Internet of things | +| IT | Information Technology | +| LEA | Law Enforcement Agencies | +| M2M | Machine-to-Machine | +| MNO | Mobile Network Operator | +| MSISDN | Mobile Station International Subscriber Directory Number | +| OEM | Original Equipment Manufacturers | +| OTP | One-Time Password | +| PLMN | Public Land Mobile Network | +| QoE | Quality of Experience | +| RUPF | Reference Unified Platform Framework | +| SIM | Subscriber Identification Module | +| SMS | Short Message Service | +| TAC | Type Allocation Code | +| TBT | Technical Barrier to Trade | +| TRIPS | Trade-Related Aspects of Intellectual Property Rights | +| UICC | Universal Integrated Circuit Card | +| USSD | Unstructured Supplementary Service Data | +| WLAN | Wireless Local Area Network | + +## 5 Conventions + +This Recommendation applies the following verbal forms for the expression of provisions: + +- a) The keyword "is required to" indicates a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- b) 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. +- c) 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 General aspects + +With the rapid growth in the reach of the Internet and accelerated adoption and usage of information and communication technology during the COVID-19 pandemic, the circulation and use of counterfeit and tampered mobile telecommunication/ICT devices has increased considerably. Mobile telecommunication/ICT devices include smartphones and other mobile devices such as tablets with a cellular network interface. In addition to mobile counterfeit ICT devices, the use of stolen devices in mobile networks also poses security and law-and-order problems. + +The unchecked proliferation of counterfeit and tampered mobile telecommunication/ICT devices in the public land mobile network (PLMN) is a serious challenge to regulators, law enforcement agencies (LEA) and end consumers that also adversely affects revenue collection and therefore the economy in general. The supply and demand economics of counterfeit and tampered mobile telecommunication/ICT devices complicate the efforts to check the local as well as global market scenario for such devices. + +[ITU-T Q.5050] has already considered possible approaches to solving the problem of counterfeit ICT products. In order to have a general understanding of possible directions for creating solutions to combat counterfeit, tampered and stolen telecommunication/ICT devices, Appendix I (clause I.1) provides a general analysis of the mobile telecommunication/ICT device ecosystem and the main stakeholders involved. Knowledge of the stakeholders and their roles in the ecosystem will allow us to define the general contours of the reference unified platform framework (RUPF). + +This Recommendation aims to provide a comprehensive approach for combating counterfeit, tampered and stolen mobile telecommunication/ICT devices with a consumer-centric unified platform framework. By this proposed approach, the source of counterfeit and tampered mobile telecommunication products can also be assisted in tackling such issues, to the extent possible, in the markets where they are manufactured and from which they are exported and in the countries in which they are sold. + +It is very difficult for anyone to differentiate between authentic and counterfeit or tampered mobile telecommunication/ICT devices by inspecting or testing them because counterfeiters attempt to create products very similar to the genuine device and even provide similar documentation and packaging. It is crucial that these factors are considered when deploying technology solutions to avoid creating more problems for users and genuine manufacturers than those the solutions aim to address. + +However, in order to effectively check the proliferation and to combat the induction of counterfeit and tampered ICT including stolen devices in the mobile network, the information technology (IT) solution framework should enable consumers to verify the authenticity of any mobile telecommunication/ICT device ubiquitously while making purchasing decisions. + +Consumers are the most affected and vulnerable stakeholder in the telecommunication/ICT mobile device ecosystem and a consumer-centric approach can play an important role in combating the proliferation of counterfeit and tampered mobile telecommunication/ICT devices. This is because + +they often pay similar prices for the counterfeit devices while suffering consequences including compromised performance, security and privacy. Thus, the success of any solution to combat counterfeit or tampered mobile telecommunication/ICT and stolen devices lies in the empowerment of the end consumer through tools and awareness so that they can take informed decision while buying mobile telecommunication/ICT devices. Such a solution should cover all possible local and global scenarios through which counterfeit mobile telecommunication/ICT devices may enter the mobile network ecosystem through unauthorized channels. Further, the rejection of such devices by consumers, based on their awareness and empowerment with enabling tools, will also create a huge disincentive to the unauthorized manufacturing and trade of counterfeit and tampered telecommunication/ICT devices. + +The ecosystem of counterfeit and tampered mobile telecommunication/ICT devices is focused on exploiting susceptible consumers. Due to a lack of consumer awareness and ignorance combined with the cheaper cost of counterfeit and tampered devices, consumers are enticed to buy them. Thus, consumers may suffer possible negative impacts when using counterfeit and tampered device. (Appendix I (clause I.2)). + +Therefore, the Member States either planning or implementing countermeasures for restricting the usage and proliferation of counterfeit and tampered telecommunication/ICT device should consider a holistic multipronged, consumer-centric approach while implementing a relevant IT solution framework. + +# **7 Reference unified platform framework (RUPF) requirements** + +Considering the above stakeholder analysis of the counterfeit and tampered telecommunication/ICT device ecosystem and possible roles of that can be played by the different stakeholders in combating this menace, the requirement for RUPF and different reference data sources are discussed below. + +### **7.1 Type allocation code (TAC) database** + +The type allocation code (TAC)1 is the first 8 digits of the international mobile equipment identity (IMEI) (which is 14 digits plus 1 check digit in length) which identifies the device model, brand owner and original equipment manufacturers (OEM). A TAC is allocated for a specific device model and brand owner. The TAC database and IMEI are important for the functioning of mobile devices and the mobile ecosystem. Device brand owners have to apply for TAC even for outsourced manufacturing. Therefore, access to the consolidated global TAC database provides the basic reference data for TAC codes against which the validity of any TAC code, used in any mobile telecommunication/ICT device, can be verified. A TAC database can provide important information about a device including its manufacturer, model name, TAC allocation date, OEM, subscriber identification module (SIM) slots, type of universal integrated circuit card (UICC) or embedded universal integrated circuit card (eUICC) operating system, frequency bands and radio interfaces. These details may be used effectively by RUPF and thereby help customs, LEAs and other stakeholders to differentiate counterfeit devices from genuine ones. + +### **7.2 ICT device verification repository of brand owner or original equipment manufacturers** + +The TAC database is made up of the first 8 digits of the IMEI based on the details of ICT devices provided by the device brand owners or manufacturers concerned. The remaining six digits and one check digit of IMEI are assigned by the brand owners or manufacturers themselves according to the actual utilization or production of the respective model of that device. Therefore, it is possible that + +--- + +1 Global System for Mobile Communications Association (GSMA) is responsible for allocating type approval codes (TAC) to mobile device manufacturers. + +the TAC database may show the device manufacturer or brand owner, model and other device related details, as filed by brand owner or manufacturer for allocation of TAC, even when the actual mobile telecommunication/ICT device may not have been produced or shipped to market. Therefore, only the device brand owner/OEM can provide the authentic reference database or repository of actually manufactured and shipped mobile telecommunication/ICT devices in the market. Thus, a more reliable verification of an IMEI may be made by combining the TAC database and the OEM's manufactured device repository or database. + +This device repository may be queried on demand or periodically synced by the unified platform for the verification of ICT devices by LEAs, customs and excise, regulators and consumers. The brand owners/OEMs may already be maintaining such a device database internally for the purpose of sales and after-sale warranties or lifecycle support for their telecommunication/ICT devices. Therefore, this can easily be made available to the authorized agency of Member States in a secure manner to facilitate the implementation of a unified reference platform framework. Member States may consider addressing this requirement through enabling a techno-policy framework if necessary. Measures are required to ensure security of the data. + +### **7.3 National and international stolen device database** + +To create disincentives for theft of mobile telecommunication/ICT devices and mitigate the use of stolen mobile devices, the unified platform should be used effectively to track and create a block list of stolen or lost devices to enforce the policy with the help of mobile network operator (MNO) - equipment identity register (EIR) capabilities. To implement this feature, a user interface may be used for consumers to report stolen or lost devices. Based on the applicable framework, the entry in the stolen/lost device database can be made for example by an LEA or by the device owner after due authentication of device ownership. For example, a consumer could register a stolen device on the online platform by filing its details along with a copy of the report filed with a LEA and proof of identity. As soon as the complaint has been verified by the LEA concerned, the entry is pushed to the relevant stolen device list of the central EIR. Per LEA requirements, the device can either be placed in a blocked list or in a tracked list, which are further replicated to the MNO-EIRs at a national and international level. + +If the mobile telecommunication/ICT device is tracked and recovered by an LEA or by users themselves, the IMEI of the device may be removed from the stolen or lost device database and from the blocked list through the same user interface. This process provides flexibility and convenience to consumers in lodging complaints and to LEAs in effectively dealing with increasing numbers of cases of stolen or lost mobile telecommunication/ICT devices. + +The IMEIs of non-recovered devices can be placed in the permanent blocked list of the central EIR so that valid unique mobile device identifiers cannot be replicated in counterfeit or tampered ICT mobile devices in future. + +### **7.4 National unified platform with central EIR** + +The central EIR will have interfaces with relevant reference data sources and will update or synchronize data with a defined periodicity or query online as per agreed arrangements between Member State and reference data providers concerned. The main reference data source will be the TAC database. Based on the overall functional requirements, central EIR may also maintain additional details, which may include but not limited to: + +- a) Permitted list, for devices that are allowed to register in the mobile network. +- b) Blocked list, for devices that are prohibited to register in the mobile network based on defined criteria by the Member State concerned. +- c) Tracked list, for devices with an intermediate status (when it has not yet been defined in which of the lists – blocked list or permitted list – the device should be placed). For example, + +a recently stolen mobile device may be placed in the tracked list so that it can be tracked when it connects to a mobile network. + +- d) Lost or stolen device list, for lost or stolen devices in the country, with periodic updates in status. +- e) Lost or stolen device list, for lost or stolen devices in other countries, with periodic updates in status. This interface could be established via the central equipment identity register (CEIR) or via each MNO-EIR. +- f) Subscriber number or mobile station international subscriber directory number (MSISDN), to link the device and user or owner at any given point of time for lost, stolen or counterfeit devices. +- g) Details of the importer or local manufacturer who brought the device into the country/market. + +The majority of these lists are dynamic in nature and devices may move from one list to another based on defined criteria that can be applied using events detected or reported through the unified platform. For example, when a lost or stolen device is recovered and returned to its authorized owner, it is removed from the lost/stolen device list and/or the tracked list and moved to the permitted list so that it can be used in mobile networks. These centralized lists will be synchronized by MNO-EIRs with a defined periodicity for making decisions on whether to allow the device in the mobile network or not. The frequency of the update from source reference data and MNO-EIR update and the type of lists to be maintained in central EIR may be decided based on national requirements. These are the critical input parameters for platform architecture and hardware dimensioning and should be given due consideration when finalizing platform functional requirements and solution architecture. + +### 7.5 Mobile network operator's equipment identity register + +Third generation partnership project (3GPP) Technical Specifications provide that network operators can make use of IMEIs to exercise control on the entry of mobile devices to the MNO network. It specifies requirements for three registers, i.e., a permitted list, tracked list and blocked list. The permitted list is composed of all number series of equipment identities i.e., TAC that are permitted for use. This can be sourced from the TAC database. The blocked list contains all equipment identities i.e., IMEIs that belong to equipment that need to be barred. This list can be generated at the central database according to the regulatory frameworks in the respective Member State. Equipment on the tracked list is not barred (unless it is on the blocked list or not on the permitted list) but is tracked by the network (for evaluation or other purposes). + +While central EIR may have multiple lists to provide a wide range of information to LEAs and consumers, it ultimately derives the permitted, blocked and tracked lists through overall information. These three lists are replicated or copied in the MNO-EIR for exercising actual control for allowing or denying access in the mobile network. Per 3GPP specifications, it shall be possible to perform the IMEI check at any access attempt, except international mobile subscriber identity (IMSI) detach and even during an established call at any time when a dedicated radio resource is available. The network is required to terminate any access attempt or ongoing call when receiving the answers "blocklisted" (i.e., on the blocked list) or "unknown" equipment (i.e., not on the permitted list) from the EIR. The MNO can capture logs and pass relevant data sets such as geographical details and MSISDN to the RUPF in case of an access attempt by blocklisted or tracked-listed devices, per policy. This will enable the performing of analytics and tracking of counterfeit devices through the unified platform. + +### 7.6 Stakeholder interface(s) for mobile telecommunication/ICT device verification + +Countermeasures against the proliferation of tampered or counterfeit and stolen ICT devices will require considerable collaborative efforts by all stakeholders, especially TAC allocating bodies, OEMs, LEAs, MNOs, customs and excise and regulators. Therefore, the platform should be designed to facilitate collaboration and provide intuitive, easy to use and secure interfaces. The unified platform + +interfaces can broadly be grouped into two categories, i.e., system-system interfaces and system-user interfaces, as depicted in Figure 1. + +The interfaces should provide secure role-based access to users based on their reasonable requirements as permitted under the techno-policy framework. For example, at the user-system interface, the platform may provide authorized access to LEAs or customs officials for the verification of individual devices as well as bulk verification, but the consumer may only have access to check individual devices and may have a possible limit on the number of verification attempts allowed per day. Depending on the purpose and use, the interfaces need to be secured through encryption and authentication to protect the data available on the platform. The relevant access logs and audit trails may be recorded in the platform and analysed in near real-time to track and mitigate any malicious activities trying to misuse these interfaces. + +![Diagram of Reference unified platform interfaces showing User-system and System-system interfaces.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +The diagram illustrates the 'Reference unified platform' as a central orange horizontal bar. Above this bar, four boxes represent external entities: 'LEA', 'Custom and excise', 'Consumer', and 'Regulator'. Below the bar, four boxes represent internal components: 'TAC database', 'Stolen device DB', 'OEM device repository', and 'MNO-EIR'. On the right side, two boxes labeled 'User-system interfaces' and 'System-system interfaces' have arrows pointing to the 'Regulator' and 'MNO-EIR' respectively. A small label 'Q.5054(25)' is located at the bottom right of the diagram. + +Diagram of Reference unified platform interfaces showing User-system and System-system interfaces. + +**Figure 1 – Reference unified platform interfaces** + +The system-system interfaces may also include interface for sourcing international blocked list in the platform as per national requirement. + +# **8 Reference unified platform framework (RUPF)** + +Considering the roles of different key stakeholders and unified platform requirements discussed in Appendix I, a proposed reference framework is given in Figure 2. + +With the implementation of this RUPF, it will be possible for key stakeholders i.e., LEAs, customs and excise, and regulators to effectively implement comprehensive countermeasures to combat counterfeit and tampered telecommunication/ICT devices. Customs and excise authorities or other enforcement entities will be able to check against the device permitted list to verify whether the identifiers of the devices, whether produced locally or imported, have been legitimately allocated and that their make and model match with the details recorded in the TAC database and OEM repository. The data sourced from the TAC database and OEM repository of devices actually manufactured will provide a reliable reference against which any mobile telecommunication/ICT device can be verified using secure interfaces provided by the RUPF. + +The RUPF can also be used effectively to track the lost or stolen devices and restrict their use in mobile networks by integrating national and international lost or stolen device databases with the platform. This database can be integrated with the RUPF, if already available or it can be implemented as one of the modules of RUPF. + +The ubiquitous access of RUPF to consumers will enable them to check whether the mobile telecommunication/ICT device (which may be new, second-hand or refurbished) that they are buying is counterfeit or stolen. If it is stolen or counterfeit, consumers will be protected from buying counterfeit, tampered or stolen devices and will also be able to report to LEAs that could take action to track and recover such devices. This will act as a strong deterrent against thieves and counterfeiters. + +The RUPF concept is based on a consumer-centric approach. The counterfeit mobile telecommunication/ICT device ecosystem has sustained itself over a certain period and is further proliferating mainly due to the cost advantage such devices command over genuine devices. Generally, counterfeiters target low- and middle-income group consumers for selling counterfeit or + +tampered devices. Due to a lack of awareness about the risks associated with using counterfeit devices and because of the price advantage, consumers are attracted to buy such mobile telecommunication/ICT devices. + +To empower the consumer and ensure adoption, the simplicity and ease of use of the RUPF, preferably provided in the local languages, is an important consideration. Therefore, the platform should provide secure and simple interfaces for interaction with the end consumers of mobile telecommunication/ICT devices. + +![Figure 2 – Proposed reference unified platform framework. The diagram illustrates the architecture of the RUPF, showing its integration with various databases, external systems, and user groups. At the top, three databases (National stolen mobile DB, TAC database, and OEM repository-1,2...n) are connected via 'System-system interfaces'. The 'National unified platform' is the central component, containing lists for lost/stolen, permitted, blocked, and tracked devices, as well as MSISDN-IMEI mapping and query logs. It connects to 'Financial institutions (Optional)', 'MNO-1 EIR', 'MNO-2 EIR', and 'MNO-n EIR' through 'System-system interfaces'. 'System-user interfaces' connect the platform to 'Consumers' (via mobile and web), the 'Internet', and 'Customs, excise, LEA, regulator'. A 'Query and user log analytics and alert' module is also shown. A text box at the bottom left lists supported channels (SMS, USSD, Internet), sample query/response formats, and supported consumer device types.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +1. Channels supported: SMS, USSD, Internet +2. Sample query format: +3. Sample response format: +4. Query supported from consumers of: Feature phones, smartphone and Internet + +Q.5054(25) + +Figure 2 – Proposed reference unified platform framework. The diagram illustrates the architecture of the RUPF, showing its integration with various databases, external systems, and user groups. At the top, three databases (National stolen mobile DB, TAC database, and OEM repository-1,2...n) are connected via 'System-system interfaces'. The 'National unified platform' is the central component, containing lists for lost/stolen, permitted, blocked, and tracked devices, as well as MSISDN-IMEI mapping and query logs. It connects to 'Financial institutions (Optional)', 'MNO-1 EIR', 'MNO-2 EIR', and 'MNO-n EIR' through 'System-system interfaces'. 'System-user interfaces' connect the platform to 'Consumers' (via mobile and web), the 'Internet', and 'Customs, excise, LEA, regulator'. A 'Query and user log analytics and alert' module is also shown. A text box at the bottom left lists supported channels (SMS, USSD, Internet), sample query/response formats, and supported consumer device types. + +Figure 2 – Proposed reference unified platform framework + +### 8.1 Reference unified platform framework overview + +The brief overview of key framework components is given below: + +- i) **TAC database:** List of TAC codes allocated for a specific device model and brand owner. +- ii) **National/international stolen device database:** This is the module for reporting lost or stolen devices and for their subsequent lifecycle management. + +- iii) **OEM repository (1,2...n):** OEM repositories are the databases maintained by OEMs to provide reference data about devices that were actually manufactured or shipped to the market against the TAC code(s) allocated to them. +- iv) **Customs and excise, LEA, regulator:** Customs and excise, LEA, regulator use the platform for taking counter measures against the proliferation of tampered telecommunication/ICT and stolen devices. +- v) **Consumer:** Consumers may seek information about authenticity or status (i.e., stolen or not) of any telecommunication/ICT device. +- vi) **National unified platform:** The national unified platform consists of the following submodules. + - a) **Imported device IMEI list:** The imported device list consists of the IMEI or IMEI range(s) of devices imported with authorization to the country. This list may be provided by the customs authorities or by any other authority responsible in the Member State concerned. With this list, it can be verified whether the device has been imported with authorization to the Member State or not. It is also possible to integrate the RUPF for automatic fetching of these details from the system maintaining such a list, if it is maintained by the stakeholders concerned. + - b) **Locally manufactured device IMEI list:** The locally manufactured device IMEI list is the database of IMEIs or IMEI range(s) of mobile telecommunication/ICT devices that have been manufactured within the Member State. A Member State may mandate local manufacturers to update such details in the platform itself if no separate reporting system is implemented for this. + - c) **Lost and stolen device list:** This database is replicated from the national and **international** stolen device database if it is implemented outside the RUPF, otherwise it can be a module within the RUPF with the features described in clause 7.3. + - d) **Permitted list:** The permitted list is created in the central equipment identity register (CEIR) based on the regulatory framework in Member State. It is a list of mobile telecommunication/ICT devices that are allowed to register in the mobile network. This list is synced or updated by MNO-EIR at a defined frequency or upon defined events (see clause A.2.3). + - e) **Blocked list:** The blocked list is created in the CEIR based on the approved regulatory framework of the Member State. It is the list of devices that are prohibited to register in the mobile network. This list is synced or updated by MNO-EIR at a defined frequency or upon defined events (see clause A.2.3). + - f) **Tracked list:** The track list is the list of mobile telecommunication/ICT devices that are to be tracked for further action e.g., stolen or lost devices. Such devices are allowed to register in the mobile network for a defined period (see clause A.2.3). + - g) **MSISDN-IMEI map:** In order to handle the cases of devices with tampered or replicated unique identifiers such as the IMEI, it is a pre-requisite to ascertain genuine and counterfeit or tampered devices and only allow registration by genuine devices. In such cases, the devices with combination of IMEI and MSISDN may only be allowed (see clause 7.4). + - h) **Query logs:** Query logs contain raw meta data that can be used for further analytics and correlation. For example, when a query is made with by a consumer, the following logs may be generated if response is or . + +#### **IMEI, MSISDN, 'N', 'L', location latitude/longitude** + +Similar logs in the required format may also be generated for different relevant scenarios. These logs can be analysed to generate time alerts to concerned agencies and discover patterns such as geo-hotspots of usage of stolen or lost devices. + +- vii) **MNO-EIR:** The MNO-EIR holds various lists of mobile devices, such as the permitted list, blocked list or tracked list, per 3GPP Technical Specifications. It interfaces with the CEIR for the replication of these lists based on specified interfaces [b-ITU-T Q Suppl. 76]. The MNO-EIR holds the updated lists for enforcement in the mobile network per the regulatory policy (see clause 7.5). +- viii) **System–system interfaces:** System-system interfaces are the interfaces through which the RUPF interacts with other systems (see clause 7.6). +- ix) **System–user interfaces:** System-user interfaces are the interfaces through which RUPF users such as consumers, LEAs and regulators interact with the RUPF (see clause 7.6). +- x) **Query and user log analytics and alert:** The interactions of different categories of users with the platform will result in the generation of various activity and query logs. The correlation and analytics of such logs may be used to discover actionable patterns that may be used for pre-emptive actions by LEAs. For example, the spatial correlation of the queries in which the device was found to be counterfeit may reveal geographical hotspots for counterfeit, stolen or tampered devices. +- xi) **Consumer interfaces and interactions:** The suggested RUPF architecture is aligned with the objective of consumer empowerment as an anytime, anywhere tool for verifying any mobile telecommunication/ICT device. Therefore, consumer interfaces should be designed to provide simple and intuitive interaction. The consumer should be able to use platform in the following interaction scenarios: + - a) **Online through desktop/mobile:** For consumers who may not have access to an MNO subscription and want to verify details of any mobile telecommunication/ICT device, the platform should provide a secure interface through a website that can be used through the Internet. The suggested query and response mechanism is already covered in Figure 2. + - b) **Mobile application:** To provide a better user experience and comprehensive tools to the consumer, a mobile application, closely integrated with the RUPF, may serve as a good tool for the consumer interface, as well as for relevant data capture in a platform-like location with the permission of consumers. The mobile app may bundle relevant features for mobile telecommunication/ICT device verification querying, reporting of lost or stolen devices, reporting of details about any counterfeit devices with due verification and reporting recovery of stolen or lost devices etc. The mobile application can be used by both types of consumers, i.e., those with an MNO subscription or those with only having Wi-Fi Internet access. + - c) **Short message service (SMS) interface:** Since a significant number of feature phones are still in use, especially in developing countries, an SMS interface is an essential requirement of the RUPF. The query format for the SMS-based interface should be simple and require a minimum number of input text or numbers, for example, only the IMEI. The response should be provided in a simple format, and preferably in a local language for better understanding and to have the desired impact on consumers. Member States may waive SMS charges for consumers for one or two queries per day or week if required under consumer awareness programmes. + - d) **Unstructured supplementary service data (USSD) interface:** Though an SMS-based query service for consumers can be used on both smartphones and feature phones, a USSD interface may be considered as an alternate interface. Consumers can use such an interface to query the RUPF to obtain details only for the mobile telecommunication/ICT device through which the query is triggered. The possibility to provide simple USSD code to invoke a USSD query exclusively to the RUPF may be explored. On invoking a query through the USSD code of the service, IMEI details may be automatically fetched from the device, which will eliminate any wrong input scenarios. This consumer interface + +will enable queries even by the consumers with the lowest literacy and will bridge the possible awareness divide about the risks involved in counterfeit mobile telecommunication/ICT devices. + +## 8.2 Key platform features + +The following key guiding principles may be considered while preparing the solution architecture of the RUPF. + +- i) The platform should provide simple and intuitive interfaces to stakeholders covering possible scenarios such as the limited availability of Internet access and the absence of an MNO subscription. +- ii) To overcome the limited availability of Internet access, SMS/USSD channels may be made part of network interfaces for consumers to access the platform. This will broaden accessibility to consumers and other stakeholders. +- iii) In scenarios where a consumer has no MNO subscription, Wi-Fi/Internet channels may be used by them to access the platform through desktop or mobile device. This will enable a wider range of access channels for different types of mobile telecommunication/ICT devices especially for rural populations using low-cost feature phones. +- iv) The platform should have secure interfaces with the national and international stolen device database, the OEM's IMEI repository of manufactured devices, the OEM's country-specific export, locally manufactured IMEI device database and TAC database. +- v) If OEMs do not have online reference repositories of mobile telecommunication/ICT devices that have actually been manufactured, they can be provided with secure interfaces in the platform to upload IMEI range(s) of manufactured mobile devices against their reference entry in the TAC database. +- vi) The LEA, customs and excise and regulator should be able to access the platform with the facility for single as well as bulk mobile telecommunication/ICT device verification. +- vii) Consumers may be provided with only single device enquiries, with required checks such as one-time password (OTP) or captcha to avoid automated query attempts on platform and consumer traceability. +- viii) The query to the platform may be sent in a form such as through any device, e.g., computer, mobile or laptop. +- ix) A single query to platform may automatically split in multiple queries internally e.g., to the stolen and lost device database, the OEM repository or the TAC database. The platform may return a consolidated response to the user with relevant details in a format such as , as applicable. +- x) The unified platform may expose secure APIs to LEAs, customs and excise authorities, and regulators for bulk or IMEI range verification. +- xi) The verification logs generated in the platform through consumer queries and use by LEAs and customs and excise may be used to feed an analytics module that may be built upon the platform to find patterns to identify the players involved in these unauthorized activities. +- xii) The consumer queries to the platform, if in the stolen or lost device database, may also be used to trigger alerts to concerned LEAs to geolocate the stolen or lost ICT devices and their users. +- xiii) To encourage OEMs to support the verification of ICT devices, security or trust rating assignment may be considered by regulators. The ratings may be based on objective and measurable criteria evolved after stakeholder consultation. + +- xiv) To avoid inconvenience to international in-roamers, their mobile telecommunication/ICT devices may be kept outside the framework of the valid IMEI check while they are roaming in foreign MNOs networks. + +# **9 RUPF security and privacy considerations** + +The national unified platform implementation based on the framework provided in Figure 2 will host important data sourced from different stakeholders and consumers, including from the IMEI database and OEMs. Therefore, the platform is likely to be a target of cyberattacks by different sources and impacted parties. Since it is a countermeasure against counterfeit and stolen ICT devices, the entities involved in such activities will also target the system. Counterfeiters may also try to gather the details of TAC codes and valid IMEI range being maintained in CEIR to use them for IMEI replication or cloning. Therefore, the platform implementation should adopt a security-by-design approach. The platform security may consider the latest practices and standards regarding cybersecurity, including role-based access, secure APIs and dual-factor authentication. + +The RUPF is not expected to store any consumer-specific data such as name, address, date of birth or any other personal identifier. Only IMEI-MSISDN combinations may be captured on a case-to-case basis for stolen or blocklisted devices per the requirements of platform features and functionalities. Therefore, the platform framework duly safeguards the privacy of individual consumers. The location details of only blocklisted or permitted devices may be required by LEAs as permitted by the legal framework to act against unauthorized activities. + +## Annex A + +## Issues (aspects) and scenarios for the implementation of a reference unified platform framework + +(This annex is an integral part of this Recommendation.) + +### A.1 Key considerations when implementing a reference unified platform framework + +#### A.1.1 Stakeholder consultation and onboarding + +The implementation of a RUPF is a collaborative effort by key stakeholders, which include consumers, regulators, MNOs, TAC allocating bodies, OEMs, customs and excise, and LEAs. Therefore, it is important to establish ongoing communication channels with all stakeholders involved prior to actual implementation so that agreements can be reached on the role and responsibilities of each stakeholder. This will enable faster roll-out and implementation of the technology platform with minimal disruption in the ecosystem, especially to the consumers and OEMs of genuine devices. + +#### A.1.2 Enabling regulatory frameworks + +The enforcement of any countermeasure affecting consumers or other stakeholders, such as disabling existing identified counterfeit devices in the MNO network or disallowing the entry of new counterfeit ICT devices into the MNO network, will require the enabling support of an appropriate regulatory framework. The enabling regulatory framework may include but is not limited to the following provisions to: + +- i) Allow restrictions on the entry of any new counterfeit or tampered devices with replicated identifiers or stolen telecommunication/ICT devices in MNO networks; +- ii) Allow restrictions on the import, manufacturing, circulation and sale of counterfeit mobile telecommunication/ICT devices and accessories in the market that are not compliant with a country's legislative and regulatory framework; +- iii) Allow the establishment of a unified platform and stakeholder responsibilities to support measures to combat the proliferation of tampered and counterfeit ICT devices; +- iv) Allow action against the tampering and replication of unique identifiers. + +Member States may also consider technical regulation, if required, to ensure compliance with the IMEI format and requirement of their online verifiability in collaboration with OEMs to minimize IMEI tampering and prevent devices with tampered or replicated identifiers from accessing mobile networks. + +#### A.1.3 Consumer awareness and participation + +Consumer education and their active participation supported by a RUPF can play central a central role in combating the proliferation of counterfeit, tampered and stolen mobile telecommunication/ICT devices. Due to their lack of awareness of the possible adverse effects of using counterfeit ICT devices, consumers are the most vulnerable stakeholder. The use of tampered and counterfeit ICT devices impacts consumer safety, security and privacy including quality of experience and network performance. Therefore, consumers should be encouraged, through awareness campaigns and consumer education, to participate and play an active role in combating the proliferation of tampered, counterfeit and stolen ICT devices. The RUPF will further empower them by providing tools for verifying devices at any time in any place through simple user interface(s). Easy access to a tool to check if a device is reported stolen may prevent a consumer from buying it. + +Regulators and MNOs may run awareness campaigns periodically for different target groups of consumers and arrange workshops for consumer self-help groups. The campaigns may provide information on tools available to check whether an ICT device is counterfeit or reported stolen and + +on the reporting mechanism(s) upon detection of any device flagged by the RUPF as tampered or counterfeit or stolen or as being a device with replicated unique identifier. The MNOs may be mandated to include relevant information in their customer welcome kit, welcome message and post-paid bills. Retail stores and OEMs should be encouraged to participate in raising consumer awareness about risks associated with using counterfeit ICT devices. Additionally, consumers can be made aware of their obligations and rights regarding the use and acquisition of mobile telecommunication/ICT devices. Remedial actions, such as disallowing the devices in mobile networks or disabling existing devices, should be considered only after consumer awareness campaigns and following advance notice, so that there is zero or minimal impact on consumers. + +#### **A.1.4 Identification and enforcement actions against producers and traffickers of counterfeit devices** + +In order to break the vicious cycle of production and trafficking of counterfeit mobile telecommunication/ICT devices, stakeholders are required to take coordinated actions at every possible checkpoint in line with enabling the regulatory framework of the Member State. To enable better coordination, there is a need to establish an agreed process to implement countermeasures. To trace back the source and remove producers and traffickers from the market, checks at the following points are important: + +- Local manufacturing units before products enter the local market or are exported; +- Ports of entry for imported mobile telecommunication/ICT devices; +- Entry to the mobile network. + +In addition, analytics on consumer complaints and feedback captured as a result of online verification on the RUPF and market surveillance, as used in [ITU-T Q.5050], can play an important role. + +Since counterfeit mobile telecommunication/ICT devices often cross different countries before being sold in the market, it is crucial to establish strong collaborations between the agencies concerned in other countries of origin or transit to trace the source of production and the channel(s) of trafficking. + +#### **A.1.5 Implementation of a reliable unique identifier** + +The secure, verifiable, and persistent unique identifier is the cornerstone of any solution to combat tampered or counterfeit mobile telecommunication/ICT devices. The lack of such reliable tamperproof unique identifiers in mobile telecommunication/ICT devices is being extensively exploited by counterfeiters and is the biggest bottleneck in initiating effective countermeasures. With the widespread use of the latest ICT mobile devices using 5G and Internet of things (IoT) / machine-to-machine (M2M) technology, the impact of counterfeit devices may pose a greater challenge for the security and privacy of consumers; an additional impact is the foregone tax revenue. Therefore, it is imperative that standardization bodies and OEMs are recommended to take urgent actions to ensure the implementation of secure, verifiable and persistent unique identifiers in mobile telecommunication/ICT devices that cannot be changed by unauthorized entities. Since IMEI is an identifier that is used by the mobile network and is visible on mobile telecommunication/ICT devices, it is currently easily used for the replication and manufacturing of counterfeit mobile telecommunication/ICT devices. + +Therefore, OEMs and manufacturers are recommended to store the unique identifier on a secure element on the mobile device and implement security measures, to the extent technologically feasible, to detect tampering. The identifier issuer entity is recommended to implement a process that ensures the verifiable, correct and secure implementation and use of these unique identifiers. Further, standard development organizations such as 3GPP may consider the issue and develop a roadmap for the improvement or revision of an existing scheme for the unique identification of mobile telecommunication/ICT devices based on only IMEI, which are being extensively used for replication or production of counterfeit ICT devices. + +#### **A.1.6 Collaboration with authentic ICT device manufacturers** + +Sometimes, action against counterfeit ICT devices may result in undesired effects on authentic ICT device manufacturers caused by compliance, enforcement and surveillance. + +Therefore, collaboration and active support of OEMs is important to ensure the effective implementation of technical solutions and to ensure action towards the implementation of tamperproof and verifiable unique device identifiers. Efforts should be made to minimize any additional cost to manufacturers to comply with the regulatory requirements while meeting the overall objectives of driving the counterfeit, tampered and stolen ICT devices out of circulation and use in mobile networks. + +#### **A.1.7 Avoiding technical barriers to trade** + +Though the measures to combat the proliferation of counterfeit or stolen devices is in the interest of global consumers and Member States, regulatory measures to counter the issue of counterfeit mobile telecommunication/ICT devices should also be evaluated to ensure that they do not result in undesired effects on the import, export and use of genuine ICT devices, which may constitute a technical barrier to trade (TBT) as defined by the World Trade Organization (WTO) trade-related aspects of intellectual property rights (TRIPS) [b-WTO-TRIPS]. + +#### **A.1.8 Collaboration with law enforcement agencies to mitigate negative impacts on consumers** + +Since current mobile devices store sensitive personal data and allow access to various financial and governmental services, it is recommended that LEAs are connected to the RUPF not only to request the inclusion of counterfeit, tampered and stolen devices on databases but also to receive up-to-date information on irregular devices included by other sources and, based on this information, are able to notify relevant stakeholders to avoid additional negative impacts for the consumer, such as irregular financial or governmental transactions using the data and applications on the stolen device. + +### **A.2 Possible approaches for RUPF implementation** + +Unified platform implementation may be carried out in a phased manner or in one go based on the requirements of the Member State in question. The implementation options described in clauses A.2.1 to A.5 may be considered while rolling out a unified platform framework. + +#### **A.2.1 Full implementation** + +In the full implementation option, all modules of the platform including central and MNO-EIR, integration with TAC database, stolen or lost device database and OEM repositories will be required for system-system interfaces. The user-system interfaces will be required to support stakeholder queries through various channels as elaborated in the framework. The advantage of this approach is that stakeholders can obtain complete details of the device under verification. + +For example, when a consumer tries to lodge a complaint about a stolen device, an alert may be sent to the consumer and LEA that the device is counterfeit or tampered and that a report is being made. In this scenario, to discourage the use of counterfeit or tampered devices, LEAs may give priority to tracking genuine devices while further analysis on purchase history may be carried out for counterfeit or tampered devices. The platform will enable a progressive build-up of a national database of counterfeit, tampered and lost devices that can be shared with other Member States for blocklisting in their network based on mutual collaboration. Suitable interfaces may be developed in the platform for the secure exchange of blocklisted unique identifiers across Member States for the seamless exchange of updated lists periodically at an agreed frequency based on operational considerations. + +#### **A.2.2 Phased implementation** + +In a phased implementation, Member States may identify the problem statements to be addressed in order of priority and pick the relevant modules from the reference framework for implementation. + +However, the solution architecture should be prepared considering future module addition to avoid architectural rework. System–system and user–system interfaces may be chosen per requirements for initial implementation, with a suitable provision of horizontal and vertical scalability. + +For example, if the priority is to address the issue of stolen mobile devices, the stolen device database, consumer and LEA interfaces may be developed and rolled out initially. In one or more subsequent phases, the solution may be scaled up to implement a TAC database and relevant interfaces including the required expansion of IT infrastructure to host the additional central EIR Database. + +If OEM repositories are not readily available, the following alternate options may be considered in the interim period: + +- Creation of a reference OEM repository database in the RUPF by integrating a database of imported and locally manufactured devices; or +- OEMs may be mandated to upload the manufactured or imported device details in the form in the national database for devices imported in the country or manufactured locally. + +#### A.2.3 CEIR-MNO-EIR data exchange + +The national CEIR and MNO-EIR need to exchange data seamlessly for the successful implementation of the RUPF in multi-operator scenarios. In the national unified platform, CEIR is responsible for the generation of different lists, i.e., the permitted list, tracked list and blocked list, based on various input and reference data sourced by RUPF. The MNO-EIRs will periodically sync these lists from CEIR in their respective network as soon as possible, preferably within 24 hours or less. The following criteria may be considered by CEIR for the generation of various lists: + +- i) **Permitted list:** To start with, a permitted list may be generated through the specific TAC codes or range of valid TAC as provided by the TAC database. This list may be narrowed down further by maintaining the range of valid IMEIs against the respective TAC code as updated by respective OEM. Any IMEI without a valid TAC code and valid IMEI range, as provided by the entity to which the TAC code is allocated, may be considered a counterfeit mobile telecommunication/ICT device and may be denied access to the MNO network. To facilitate the availability of information of the IMEI range of devices actually manufactured against the allocated TAC codes and its uniform dissemination globally, TAC allocating bodies may consider maintaining the list of IMEIs. +- ii) **Blocked list:** The mobile telecommunication/ICT devices that do not fall in the criteria of the permitted list as decided by a Member State in line with the regulatory framework may be denied access by the MNOs per the local regulation and after providing a grace period for old or existing mobile telecommunication/ICT devices and consumer awareness. However, there are scenarios in which even devices with valid IMEIs or specific types of invalid IMEIs are required to be denied network access. For example, a stolen mobile device will pass the permitted list check, but it needs to be denied access if required by LEAs. Such IMEIs will be entered in the 'blocked list' of the CEIR which will be replicated by MNO-EIRs. The default blocked list may include: + - a) All zero IMEI; + - b) Null IMEI; + - c) IMEIs of stolen or lost devices as approved by LEAs in a framework of regulation subject to dynamic update based on their recovery. + +Based on the regulatory framework, the conditions for mobile network access by mobile telecommunication/ICT devices may further be tightened by treating the IMEI range, provided by a brand owner or manufacturer of mobile telecommunication/ICT devices against respective TAC codes, as valid a reference rather than only checking against the valid TAC codes. + +- iii) **Tracked list:** Sometimes it may be required to allow access to mobile telecommunication/ICT devices though they may be suspected of replicating of unique identifiers or cloning. For example, a mobile device, though valid per the permitted list, may be available in the network for a given IMEI-IMSI combination while one or more other devices are also accessing the network with the same IMEI but with different IMSIs. In this scenario, the MNO must perform analysis and due diligence before blocking access to a specific device. Therefore, such mobile devices may be placed initially in the tracked list for collection and analysis of their usage and user data. In such a scenario, the blocked list entry may require a combination of IMEI-IMSI for blocking a specific mobile telecommunication/ICT device. + +#### **A.2.4 Tampering and replication of unique mobile telecommunication/ICT device identifiers** + +The consumer-centric national unified platform based on the RUPF can be effectively utilized as a tool to detect the tampering and replication of a unique mobile telecommunication/ICT device identifier. The use of invalid IMEIs in mobile telecommunication/ICT devices will be reduced to a large extent with the effective implementation of a RUPF in Member States. However, counterfeiters may still try to use replicated IMEIs, which will pass the criteria of being on the permitted list as discussed in clause A.2.3. Therefore, OEMs, in collaboration with standard development organizations, need to consider innovative ways to distinguish between their own genuine product and one with a tampered or replicated IMEI with the highest degree of assurance. + +One possible option could be to use, along with the IMEI number, a combination of one more unique identifiers that can be assigned by the OEM. Such an identifier is to be securely stored on a device in an encrypted form and should only be accessible to the respective OEM. To check whether the mobile telecommunication/ICT device has a tampered or replicated IMEI, OEMs can provide a facility for online verification by MNOs or LEAs or through the national unified platform, in line with a national regulatory framework, so that the mobile telecommunication/ICT devices with replicated or tampered IMEIs can be detected and identified for denial of access by MNOs. The reporting and alerting feature of the platform can be used for the timely dissemination of information to LEAs for tracking and identifying culprits. [ITU-T Q.5052] describes a broader set of actions to address this issue. + +#### **A.2.5 Use of platform to control the unauthorized use of SIM boxes** + +SIM boxes are being used for conducting telecom frauds. In such frauds, the SIM box is used to divert international calls to a mobile telecommunication/ICT device through the Internet. The SIM box uses many SIMs in the same device, which will also have Internet connectivity at the other side to collect calls from the Internet. For each incoming international call placed through the Internet, the SIM box will originate a mobile call to the destination number in the local network and patch the call. The called party will obtain calling line identification of the local mobile number used in the SIM box, which amounts to calling line identification (CLI) tampering. The SIM box generally uses invalid IMEIs, which can be disallowed through block list entries. Further, platform analytics may be used to identify the use of IMEI patterns in SIM boxes and restrict the unauthorized use of SIM boxes and allow only authorized use through permitted listing. + +## Appendix I + +## **Analysis of the mobile telecommunication/ICT device ecosystem and the main stakeholders involved in the use of counterfeit and tampered mobile telecommunication/ICT devices** + +(This appendix does not form an integral part of this Recommendation.) + +### **I.1 Mobile telecommunication/ICT device ecosystem and key stakeholders** + +The understanding of ecosystem stakeholders and their roles will enable a visualization of the broad contours of a unified reference framework. This analysis will help further in the planning and implementation of the solution to address counterfeit, tampered or stolen telecommunication/ICT devices under the reference unified framework. The key stakeholders in this ecosystem and their roles are analysed in clause 7. + +#### **I.1.1 Original equipment manufacturers** + +Original equipment manufacturers (OEMs) invest time and money in the research, design and development of hardware and software to develop telecommunication/ICT products while counterfeiters copy these products, as closely as possible, to be able to sell their product in markets around the world. The counterfeiters try to tamper or replicate unique mobile/telecommunication device identifiers and software to make a product as close to the genuine device as possible. + +Considering the profit margins to such unauthorized entities, it is an economically viable option for counterfeiters to invest in infrastructure and resources to copy the type approval logos and icons, as well as unique device identifiers. The unique device identifiers are often deliberately subverted or even set in blank to be self-programmed in local markets, to evade customs and law enforcement checks at borders. Therefore, consumers, customs and law enforcement officials face a challenge in distinguishing fake identifying marks on such devices from genuine ones. + +To evade the monitoring and identification of counterfeit or tampered ICT devices in the mobile network, a common practice of such entities is to tamper with unique identifiers and replicate with one that some genuine devices use so as to authenticate on the telecommunication network in such a way that the counterfeit or tampered ICT devices are recognized by the network as genuine devices. + +Considering this, it is recommended that OEMs need to consider innovative ways to be able to distinguish between their own genuine or tampered product and a counterfeit device with the highest degree of assurance. + +One possible option could be to use a combination of identifier(s) with the international mobile equipment identity (IMEI) number, which can be assigned by the OEM while securely storing it on the device in an encrypted form. Such additional identifiers should be only accessible to OEMs. To check whether the mobile telecommunication/ICT device is counterfeit or not, OEMs can provide a facility for the online verification of such telecommunication/ICT device by customs, LEAs or agencies authorized by Member States. Thus, OEMs can protect their own interests by implementing reliable mechanisms for device verification and by collaborating with the concerned Member States in the implementation of effective IT solutions. The standards development organizations relevant to these matters, such as 3GPP, may consider developing standards to address the ever-increasing growth of counterfeit and tampered devices in mobile networks. + +#### **I.1.2 Counterfeit or tampered mobile telecommunication/ICT device producers and traffickers** + +The counterfeit or tampered telecommunication/ICT device producers invest in manufacturing and make efforts to proliferate such devices, mostly through unauthorized channels and using traffickers, to make a profit. With the active support of OEMs in making their devices verifiable online and + +authorized enforcement actions by respective Member State including raising consumer awareness, it is possible to identify counterfeit and tampered devices. Accordingly, enforcement actions can be taken against producers and traffickers. This will help OEMs and Member States to reduce economic losses. Such effective measures will prevent consumers from being misled by such counterfeiters and also protect them from possible performance, quality of service, safety, security and privacy related concerns. + +#### **I.1.3 Custom and excise agencies** + +The customs and excise authorities of Member States are the first point of entry of mobile telecommunication/ICT devices in a country or local market, and therefore, they can play an important role to effectively limit the circulation, import and sale of new counterfeit ICT devices. They need to establish a close collaboration between the authorities responsible for implementing and managing the IT solution per the reference unified platform framework (RUPF) provided in this Recommendation and also with customs counterpart of other countries. Similarly, for the mobile telecommunication/ICT devices produced and sold locally, excise departments of Member States may use the IT platform to ensure that no counterfeit or tampered ICT device is allowed to enter the local market bypassing authorized channels. + +Customs and excise authorities, in collaboration with LEAs, can make good use of analytics on consumer query or feedback data generated through their queries to the unified national platform for tracking the entities involved in production and trafficking of counterfeit or tampered telecommunication/ICT devices. + +#### **I.1.4 Consumer** + +Consumers are the most important stakeholder in the mobile telecommunication/ICT device ecosystem, as they are the party most affected by the use of counterfeit ICT devices and suffer from possible consequences including compromised performance, safety, security and privacy. It is more likely that consumers buy counterfeit or tampered telecommunication/ICT devices unknowingly due to a lack of awareness about possible implications, but they sometimes buy them knowingly due to possible cost advantages. Therefore, to combat the proliferation of counterfeit and tampered ICT devices, the empowerment of the end consumer through tools and awareness is critical. Empowering these consumers with tools and awareness will enable them to take informed decisions when buying any mobile telecommunication/ICT device. Consumer-centric technology solutions may also generate a cascading effect in controlling the proliferation of counterfeit, tampered and stolen mobile telecommunication/ICT devices as the rejection of such mobile telecommunication/ICT devices by end consumers will create a huge disincentive and substantial uncertainties for players involved in the unauthorized manufacturing and trade of counterfeit and tampered ICT devices. In the absence of unified technology solutions, different stakeholders are working in silos and counterfeiters are enjoying some sort of assured global market for counterfeit, tampered and stolen mobile telecommunication/ICT devices. + +#### **I.1.5 Law enforcement agencies** + +Counterfeit and tampered telecommunication/ICT devices are either imported through authorized channels or generally routed to the destination Member State(s) through unauthorized and fragmented channels. Further, the counterfeit devices may also be assembled or manufactured locally to push them in the local market without authorization or sent to other Member State(s) through different channels. Thus, LEAs have an important role in detecting and curbing the unauthorized local manufacturing or importation of counterfeit devices through unauthorized channels in collaboration with relevant stakeholders. However, in absence of a unified national platform, which can provide mobile telecommunication/ICT device related information verification and related analytics, LEAs may find it very challenging to effectively play their role in curbing unauthorized trade in counterfeit, tampered and stolen ICT devices. RUPF can be used as an effective collaboration platform to serve + +concerned stakeholders for the verification, detection, tracking and retrieval of counterfeit, tampered and stolen devices. + +LEA should also use the RUPF to receive updated information on stolen and tampered devices and notify other relevant stakeholders (such as financial and governmental service institutions) in order to protect the device owner from negative impacts. + +#### **I.1.6 Regulator and government authorities** + +Though the technology solutions may provide an enabling framework for disabling the access of counterfeit and tampered mobile telecommunication/ICT devices, regulators and governments may find it difficult to block or restrict the use of such devices in the mobile network operator (MNO) network once they have been purchased by consumers. The increasing volume of unauthorized trade in counterfeit and tampered ICT devices also impacts the revenue collection of Member States by way of avoidance of applicable taxes, and these devices pose a threat to the privacy, security and safety of their citizens. It may also become a threat to national security. The non-availability of a comprehensive techno-policy framework is being exploited by the players involved in these unauthorized activities. Therefore, breaking this vicious cycle through global collaboration for the implementation of techno-policy measures is critical from the point of view of Member States. In a consumer-centric approach, consumers are empowered with tools and awareness so that they can participate actively in combating the proliferation of counterfeit and tampered devices along with other stakeholders. With consumer education and enabling tools, it will be easier for regulators and governments to implement techno-policy measures effectively without any significant negative impact on consumers and authorized manufacturers. + +#### **I.1.7 Mobile network operators** + +The MNOs manage the network in which ICT devices are used by consumers to avail themselves of telecommunication services. In countries where governments conduct initiatives to block tampered or counterfeit ICT devices, the MNOs are the stakeholders responsible for implementing technical means, through their equipment identity registers (EIRs), to effectively block the use of these devices in the public land mobile network. Therefore, MNOs may play an important role in the effective implementation of RUPF. + +#### **I.1.8 Financial institutions** + +Nowadays, mobile devices carry a lot of valuable assets such as personal data and access to financial services, including online payment and Internet banking. Taking that into account, the RUPF information about stolen devices may be used by financial institutions so that anti-fraud measures can be taken in a timely manner (e.g., temporary limitation for mobile transactions). The information could be accessed directly from the RUPF or provided by LEA, depending on the national strategy. Financial institutions may also consider sourcing an authentic stolen device list from the RUPF in their fraud management systems to block stolen or tampered ICT devices from making financial transactions. Additionally, further restrictions to a consumer's account may be implemented at the discretion of their financial institution, because of the potential loss of personal data. Such collaborative steps across different sectors will enable the effective mitigation of negative impacts of stolen or tampered ICT devices on consumers. + +### **I.2 Impact of counterfeit and tampered devices on consumers** + +The ecosystem of counterfeit and tampered mobile telecommunication/ICT devices is focused on exploiting susceptible consumers. Due to lack of consumer awareness and ignorance combined with the cheaper cost of counterfeit and tampered devices, consumers are enticed to buy them. The following are possible negative impacts consumers may suffer when using counterfeit and tampered telecommunication/ICT devices: + +- i) **Lack of technical support and warranty:** Counterfeit and tampered mobile telecommunication/ICT devices are generally bought and sold through unauthorized channels bypassing applicable tax and without proper invoicing and therefore warranty and after-sales support are not assured. +- ii) **Absence of recourse in case of fault:** In absence of a proof of purchase and invoice, consumers cannot avail themselves of any recourse for redressing their grievance and enforcing their rights. +- iii) **Compromise on quality of service and quality of experience (QoE):** The quality of telecom services and consumer experience depend not only on the performance of the MNO's network but also on the quality and performance of the user device. Thus, consumers may be deprived of expected QoE when using a counterfeit or tampered mobile telecommunication/ICT device in spite of spending money on the device and the and MNO service subscription. +- iv) **Consumer safety:** Counterfeit or tampered ICT devices may not be subjected to routine safety tests and compliance with national standards in the way that genuine OEM brands are as they do not operate within regulatory manufacturing framework. Non-enforcement of safety standards may lead to safety risks to the end consumers. +- v) **Consumer security and privacy:** Counterfeit mobile telecommunication/ICT device manufacturers do not have any incentive in development of quality software and applications. It is likely that the operating system or preloaded bundled applications may be used for data collection that may compromise consumer data security and may result in a breach of consumer privacy. A breach of data security may also have other financial or non-financial implications for end consumers. + +### I.3 Measures for mitigation of adverse impact on consumers + +Considering the number of possible risks emanating from the use of counterfeit or tampered mobile telecommunication/ICT devices, it is imperative for Member States to take steps to mitigate or minimize adverse impacts of end consumers. The following are some key measures to minimize the adverse impact on end consumers of counterfeit or tampered mobile telecommunication/ICT devices. + +- i) **Consumer awareness:** The ecosystem of counterfeit and tampered mobile telecommunication/ICT devices is centred on the consumer to exploit them monetarily. The use of such devices may also result in costs associated with compromise of data and privacy. Consumers are attracted towards such devices due to a perceived cost advantage vis-à-vis genuine devices with similar features. However, due to lack of awareness among consumers of other possible risks and costs associated with use of these devices, the proliferation of counterfeit and tampered devices is increasing day by day. + +Therefore, the first and most important need is to make consumers aware of possible risks and costs associated with the use of counterfeit devices. The proliferation of counterfeit and tampered mobile devices not only has risks for consumers but also has cost implications to Member States in the form of foregone taxes, for OEMs as an opportunity cost due to market share captured by such devices and for MNOs in the form of impact on consumer experience and quality of service. + +Thus, it is in the interest of Member States, OEMs and MNOs to invest in consumer awareness and education campaigns through their respective channels and touch points. For example, MNOs can send awareness message to their customers periodically, display posters at their outlets or include this aspect in their customer welcome kit. Similarly, OEMs may run awareness campaigns through social and electronic media including their own or partner outlets. Member States may also run awareness and education campaigns through their consumer protection departments. Considering the fact that the target consumer of such devices may belong to low- and middle-income groups with an average level of education, + +awareness campaigns should be simple and easy to understand without complicated technical details. Such awareness campaigns may also include simple checks and questions to be asked while purchasing any mobile telecommunication/ICT device. The unified technology platform per the RUPF framework can become an important tool for consumer empowerment and education as well as a collaboration platform for all stakeholders. + +- ii) **Enabling the regulatory framework:** While consumer education and awareness is the most important measure for the mitigation of adverse impact on consumers, the enabling regulatory framework is equally important to deter the counterfeiters and enable LEAs to act swiftly against the traffickers and counterfeiter ecosystem. It should empower the LEAs by enabling criminal provisions and use of technical platforms like RUPF. +- iii) **Collaboration among stakeholders:** To mitigate the adverse impact of counterfeit or tampered mobile telecommunication/ICT devices on consumers, close collaboration among LEAs, customs and excise, OEMs and Member States will be required to take effective measures for arresting the trend of an increasing rate of proliferation of such devices. Considering the role to be played by multiple stakeholders for taking effective measures, one-to-one collaboration may not be sufficient as coordinated actions will be required to break the fragmented supply chains operated by traffickers and manufacturers of counterfeit devices. Therefore, technology platforms can effectively be used for effective collaboration. +- iv) **Implementation of a comprehensive technology platform based on the RUPF:** To enable consumer empowerment through tools and awareness, collaboration amongst key stakeholders such as LEAs, customs and excise, OEMs and MNOs, and for timely action against counterfeiters, RUPF based technology solution with an enabling regulatory framework can play a pivotal role. The unified technology platform enables a timely exchange of information required to trigger countermeasures upon the detection or reporting of counterfeit devices at different touch points in the ecosystem. Consumer queries and logs, along with other data available on the platform, can be used for analytics to discover trends and patterns for taking preventive measures against the proliferation of counterfeit devices. The RUPF is likely to increase the cost and risks associated with the manufacturing and trafficking of counterfeit devices, which will reduce the price advantage currently enjoyed by counterfeit mobile telecommunication/ICT devices over genuine ones. Such a reduction in the price gap between genuine and counterfeit devices may result in the increased use and adoption of genuine mobile telecommunication/ICT devices. +- v) **Development of standards for unique, reliable and verifiable device identifiers:** Currently, IMEI seems to be only unique identifier in use that is part of any standard and used to distinguish between genuine and counterfeit ICT device. This unique identifier is used by the network and visible on the device and thus can be copied and used as a replicated unique identifier. The counterfeit mobile telecommunication/ICT devices are so close to genuine ones in look and features that it is not possible to identify a genuine device if they have a replicated unique identifier. Only a unique and verifiable identifier can play an effective role in the detection of counterfeit devices to keep them out of mobile networks. Therefore, there is an urgent need to evolve standards and mechanisms for adoption in the mobile telecommunication/ICT device ecosystem to make them unique and verifiable to consumers and mitigate the adverse impact on them. + +## Bibliography + +- [b-ITU-T Q Suppl. 76] ITU-T Q Suppl. 76, *Common approaches and interfaces for data exchange between the central equipment identity register and the equipment identity register.* +- [b-WTO-TRIPS] WTO-TRIPS (1994), *Agreement on Trade-Related Aspects of Intellectual Property Rights*, Marrakesh Agreement Establishing the World Trade Organization. + + + + + +## 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.5056-202511-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a52ae3faaffe73550110b28bc5f5772c8aaf81a --- /dev/null +++ b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7515d114f607dad8fb9227cfa8edcb40b7f1f1307354c09c086709ad064aa414 +size 69679 diff --git a/marked/Q/T-REC-Q.5056-202511-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b +size 7190 diff --git a/marked/Q/T-REC-Q.5056-202511-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f14cdb9c00ec55b6946c76297dbe1466eeaa1d69 --- /dev/null +++ b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e5f91ebaf25aa4f4f28bfccddf23cc5a11f761c2edbe4baf5fab0c262e98ca +size 92610 diff --git a/marked/Q/T-REC-Q.5056-202511-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ca59f9b4dc355dae083a69e5a05db2ac4631288 --- /dev/null +++ b/marked/Q/T-REC-Q.5056-202511-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4a028caf2455a91a1b38a13976fbcce386105f8efb6f1e5e2cfacf00255b590 +size 251978 diff --git a/marked/Q/T-REC-Q.512-199502-I_PDF-E/raw.md b/marked/Q/T-REC-Q.512-199502-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a68b4931bcd06d882974101f94963a08d17c20ff --- /dev/null +++ b/marked/Q/T-REC-Q.512-199502-I_PDF-E/raw.md @@ -0,0 +1,428 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.512** + +(02/95) + +**DIGITAL EXCHANGES** + +--- + +**DIGITAL EXCHANGE INTERFACES +FOR SUBSCRIBER ACCESS** + +**ITU-T Recommendation Q.512** + +(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.512 was revised by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 7th of February 1995. + +# --- NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +Page + +| | | | +|-------|--------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Terms and definitions ..... | 3 | +| 4 | Abbreviations ..... | 4 | +| 5 | Characteristics of digital interfaces for subscriber access ..... | 4 | +| 5.1 | General ..... | 4 | +| 5.2 | Interface V 1 ..... | 4 | +| 5.2.1 | General ..... | 4 | +| 5.2.2 | Functional characteristics ..... | 4 | +| 5.2.3 | Electrical characteristics ..... | 5 | +| 5.2.4 | Channel types, channel allocation and signalling ..... | 5 | +| 5.3 | Interface V 2 ..... | 6 | +| 5.3.1 | General ..... | 6 | +| 5.3.2 | Functional characteristics ..... | 6 | +| 5.3.3 | Electrical characteristics ..... | 6 | +| 5.3.4 | Channel types, channel allocation and signalling ..... | 6 | +| 5.4 | Interface V 3 ..... | 6 | +| 5.4.1 | General ..... | 6 | +| 5.4.2 | Functional characteristics ..... | 6 | +| 5.4.3 | Electrical characteristics ..... | 6 | +| 5.4.4 | Channel types, channel allocation and signalling ..... | 6 | +| 5.5 | Interface V 4 ..... | 7 | +| 5.6 | Interface V 5 ..... | 7 | +| 5.6.1 | General ..... | 7 | +| 5.6.2 | Functional characteristics ..... | 7 | +| 5.6.3 | Electrical characteristics ..... | 9 | +| 5.6.4 | Channel types, channel allocation and signalling ..... | 9 | +| 6 | Characteristics of analogue interfaces for subscriber access ..... | 9 | +| 6.1 | Interface Z ..... | 9 | +| | Appendix I – Bibliography ..... | 10 | + +# SUMMARY + +This Recommendation describes the subscriber side interface characteristics of digital exchanges. It applies to digital local and combined exchanges for telephony in Integrated Digital Networks (IDN) and to local and combined exchanges in an Integrated Services Digital Network (ISDN), and also to mixed (analogue/digital) networks. + +This Recommendation is part of the Q.510-Series of Recommendations which defines the interface functions for digital exchanges in Integrated Digital Networks (IDN), mixed analogue/digital networks, 64 kbit/s-based Integrated Services Digital Network (ISDN). + +# BACKGROUND + +## Preamble to the Q.500-Series of Recommendations + +In 1980, CCITT Study Group XI published the first series of Q.500 Recommendations related to “Digital transit exchanges for national and international applications”. + +In 1984, CCITT Study Group XI approved two sets of Recommendations on digital exchanges: + +- “Digital transit exchanges in integrated digital networks and mixed analogue/digital networks” – Q.500-Series of Recommendations; and +- “Digital local and combined exchanges” – Q.510-Series of Recommendations. + +In 1988, CCITT Study Group XI combined the Series Q.500 and Q.510 Recommendations into a single set applicable to digital local, combined, transit and international exchanges 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). + +In 1994, ITU-T Study Group 11 revised the Q.500-Series of Recommendations in order to include a new exchange interface for subscriber access – the V5 interface (i.e. the V5.1 interface). The V3 interface is to the case of an ISDN primary rate access and the case that this interface is used not structured according to the ISDN principles is considered as not subject to ITU-T Recommendations. The V4 interface is marked as not subject to ITU-T Recommendations; reference should be made to interface V5.1 which covers static multiplexed ISDN basic accesses. The V4 interface was a digital interface used to connect a digital access link which includes a static multiplexer supporting several basic access digital sections. For this interface, the specification (i.e. CV1 channel structure) was not completed. + +ITU-T will continue to further develop and complete these Recommendations in areas where there are unresolved issues and develop additional Recommendations on digital exchanges in the Q.500-Series and other series in the future. + +The structure for the Q.500-Series of digital switching Recommendations is provided in Recommendation Q.500. + +# DIGITAL EXCHANGE INTERFACES FOR SUBSCRIBER ACCESS + +(Melbourne, 1988; revised in 1994) + +## 1 Scope + +It applies to digital local and combined exchanges for telephony in Integrated Digital Networks (IDN) and to local and combined exchanges in an Integrated Services Digital Network (ISDN), and also to mixed (analogue/digital) networks. The field of application of this Recommendation is more fully defined in Recommendation Q.500 [B6]. + +Exchange interfaces for subscriber access that have been considered are described, and illustrated in Figure 1 and Table 1, but they are not intended to specify every interface. Other interfaces are for further study. + +This Recommendation is not intended to define any transmission system, network or subscriber equipment in or connected to, a digital exchange via these interfaces. Therefore only the characteristics of the interfaces are described. + +## 2 References + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation G.703 (1991), *Physical/electrical characteristics of hierarchical digital interfaces.* +- [2] CCITT Recommendation G.704 (1991), *Synchronous frame structures used at primary and secondary hierarchical levels.* +- [3] CCITT Recommendation G.706 (1991), *Frame alignment and Cyclic Redundancy Check (CRC) procedures relating to basic frame structures defined in Recommendation G.704.* +- [4] ITU-T Recommendation G.960 (1993), *Digital section for ISDN basic rate access.* +- [5] ITU-T Recommendation G.961 (1993), *Digital transmission system on metallic local lines for ISDN basic rate access.* +- [6] ITU-T Recommendation G.962 (1993), *Access digital section for ISDN primary rate at 2048 kbit/s.* +- [7] ITU-T Recommendation G.963 (1993), *Access digital section for ISDN primary rate at 1544 kbit/s.* +- [8] ITU-T Recommendation G.964 (1994), *V Interfaces at the digital Local Exchange (LE) – V5.1 interface (based on 2048 kbit/s) for the support of Access Network (AN).* +- [9] ITU-T Recommendation G.965 (1995), *V interfaces at the digital Local Exchange (LE) – V5.2 interface (based on 2048 kbit/s) for the support of Access Network (AN).* +- [10] CCITT Recommendation M.3603 (1992), *Application of maintenance principles to ISDN basic rate access.* +- [11] CCITT Recommendation M.3604 (1992), *Application of maintenance principles to ISDN primary rate access.* +- [12] CCITT Recommendation M.3605 (1992), *Application of maintenance principles to static multiplexed ISDN rate access.* + +![Diagram illustrating possible access configurations. It shows six horizontal access paths connecting to an Exchange Termination (ET) block on the right. 1. Basic access digital section: connects interface T to V1 to ET. 2. Generic digital section: connects V2 to V2 to ET. 3. Primary rate access digital section: connects T to V3 to ET. 4. Digital access link (static multiplex): connects multiple T interfaces (1..n) to V4 to ET. 5. Access line configuration (static multiplexing and/or concentration): connects Z, T, and Leased line port interfaces to V5 to ET. 6. Subscriber analogue line (2-wire): connects Z interface to ET. A legend defines symbols: double vertical lines for Interface, a dot on a line for Reference point, and ET for Exchange Termination functions. Diagram code T1171350-95/d01 is present.](547f726730e589392f239257a833ede3_img.jpg) + +Diagram illustrating possible access configurations. It shows six horizontal access paths connecting to an Exchange Termination (ET) block on the right. 1. Basic access digital section: connects interface T to V1 to ET. 2. Generic digital section: connects V2 to V2 to ET. 3. Primary rate access digital section: connects T to V3 to ET. 4. Digital access link (static multiplex): connects multiple T interfaces (1..n) to V4 to ET. 5. Access line configuration (static multiplexing and/or concentration): connects Z, T, and Leased line port interfaces to V5 to ET. 6. Subscriber analogue line (2-wire): connects Z interface to ET. A legend defines symbols: double vertical lines for Interface, a dot on a line for Reference point, and ET for Exchange Termination functions. Diagram code T1171350-95/d01 is present. + +a) Interface T is defined in Recommendation I.411. + +b) The characteristics of a digital transmission system on metallic local lines for ISDN basic rate access which may form part of the basic access digital section are defined in Recommendation G.961. + +c) The differences among $V_2$ , $V_3$ , $V_4$ and $V_5$ are essential multiplexing and signalling requirements. The transmission requirements are substantially identical (e.g. Recommendations G.703 and G.704). + +d) See information provided in "Background". + +e) May be basic rate or primary rate access. Primary rate access only supported by $V_{5.2}$ interface. + +f) For reserved connections established under control of the local exchange without control plane signalling between user and local exchange. + +NOTE – Not all interfaces will necessarily exist in every implementation. + +FIGURE 1/Q.512 +**Illustration of possible access configurations** + +TABLE 1/Q.512 + +## **Interface references** + +| Access type | Interface/
reference
points | Paragraph | Related physical and
functional Recs. | Related OAM Recs. | Application
to connect | +|---------------------------------------------------|-----------------------------------|-----------|----------------------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Basic access digital section | V 1 | 5.2 | G.960 a) | M.3603 | ISDN basic access (2B + D) | +| Generic digital section | V 2 | 5.3 | G.703 G.704 | None | Digital network equipment, supporting any combination of access types | +| Primary rate access digital section b) | V 3 | 5.4 | G.703
G.704
G.706
G.962
G.963 | M.3604 | ISDN primary rate access | +| Digital access link (Static multiplex) | V 4 | 5.5 | Not subject to ITU-T Recommendations c) | | | +| Access network configurations | V 5 | 5.6 | G.703
G.704
G.706
G.964
G.965 | M.3603
M.3604 d) | A multiple of analogue subscriber lines, ISDN basic accesses and ISDN primary rate accesses with multiplexing and/or concentration capability for bearer channels | +| Generic analogue subscriber access | Z | 6.1 | None e) | None | Analogue subscriber lines | + +a) Recommendation G.961 specifies the characteristics of a digital transmission system on metallic local lines which may form part of the basic access digital section. + +b) In the case of ISDN access this is the primary rate access digital section. + +c) See information in "Background". + +d) For ISDN application through the V5 interfaces. + +e) Characteristics other than those defined in Recommendations Q.551 and Q.552 are not subject to ITU-T Recommendations. + +## 3 Terms and definitions + +For the purposes of this Recommendation, the following definitions apply: + +**3.1 digital section:** A digital section is defined as the whole of the means of digital transmission of a digital signal of specified rate between two consecutive reference points. A digital link comprises one or more digital sections and may include either a multiplexer or concentrator, but not switching. + +**3.2 access digital section:** The functional requirements to transmit the information from/to the user-network interface and to transmit, multiplex, demultiplex and process information required for operation and maintenance from/to the associated V-reference point related to that particular user-network interface. This excludes the extraction, concentration and multiplexing/demultiplexing of channels with hierarchies other than the one being concerned (as these are considered by the V-reference point). + +In addition, this Recommendation uses terms defined in Recommendations G.962 [6], G.963 [7], G.964 [8], G.965 [9] and Q.9 [B5]. + +In this Recommendation the term “exchange” or “local exchange” is used for conciseness to indicate both a (digital) local exchange and a (digital) combined exchange. A (digital) combined exchange is one which includes both local exchange and transit/toll exchange functions. + +## 4 Abbreviations + +For the purposes of this Recommendation, the following abbreviations are used: + +| | | +|------|-------------------------------------| +| AN | Access Network | +| CRC | Cyclic Redundancy Check | +| ET | Exchange Termination | +| IDN | Integrated Digital Network | +| ISDN | Integrated Services Digital Network | +| NT1 | Network Termination Type 1 | +| PABX | Private Automatic Branch Exchange | +| PCM | Pulse code modulation | +| PSTN | Public Switched Telephone Network | + +## 5 Characteristics of digital interfaces for subscriber access + +### 5.1 General + +Digital interfaces for subscriber access are defined at the V-reference point which is the boundary between the Exchange Termination (ET) and the digital access section or link. These interfaces are designated interface V and are defined to allow flexibility of implementation for different exchange and transmission equipment realizations. However, a physical interface will not be specified for all subscriber access types identified (see Figure 1). + +As an objective, the characteristics of digital interfaces on the subscriber side of the exchange should be aligned with the characteristics of ISDN user/network access structures (see Recommendation I.411 [B1]). + +However, in many countries, digital access arrangements not structured according to ISDN principles are used, e.g. to ensure compatibility with existing networks and services and it is expected that these arrangements will continue to be used for several years. These types of interfaces not structured according to the ISDN principles are not subject to ITU-T Recommendations. + +### 5.2 Interface V1 + +#### 5.2.1 General + +Interface V1 may be used at the V1 reference point to connect to an ISDN basic access digital section for the provision of a single basic access. The characteristics of the basic access digital section are defined in Recommendation G.960 [4] and the characteristics and parameters of a digital transmission system which may form part of the digital section for the ISDN basic rate access are given in Recommendation G.961 [5]. + +#### 5.2.2 Functional characteristics + +The functional description is illustrated in Figure 2 and the following functional requirements are defined: + +- 1) *(2B + D) channels* +To provide the bidirectional transmission capability for two B-channels and one 16 kbit/s D-channel as described in Recommendation I.412 [B2]. +- 2) *Bit timing* +To provide bit (signal element) timing to enable the digital section to recover information from the aggregate bit stream. + +##### 3) *Frame timing* + +To provide frame timing to enable digital section and ET to recover the time division multiplexed channels. + +##### 4) *CV1 channel* + +The CV1 channel provides, for each direction of transmission, the capability to transfer management functions required for the digital section as specified in Recommendations G.960 [4] and M.3603 [10]. The CV1 channel may carry one or more functional links. These functions include activation from network side, activation request from a digital section, deactivation from ET side, operation and maintenance signals. + +##### 5) *Power feed* + +This function provides for remote power feeding for the digital section and possibly terminal equipment. This function is optional. + +![Diagram of Functions at interface V1 showing various channels and functions between a Basic access digital section and Exchange Termination (ET) functions.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +The diagram illustrates the functions at interface V1. On the left, a box labeled 'Basic access digital section' is connected to a central stack of horizontal double-headed arrows. On the right, a box labeled 'Exchange Termination (ET) functions' is also connected to this stack. The arrows, from top to bottom, are labeled: '2 B + D-channel', 'Bit timing', 'Frame timing', 'Activationb)', 'Deactivationb)', 'Operation and maintenanceb)', and 'Power feeda)'. Below the arrows, a line points to the bottom of the stack, labeled 'V1 reference point'. In the bottom right corner of the diagram area, the text 'T1164720-94/d02' is present. + +Diagram of Functions at interface V1 showing various channels and functions between a Basic access digital section and Exchange Termination (ET) functions. + +a) The provision of power feed function is optional. + +b) These functions are conveyed by the CV1 channel. + +FIGURE 2/Q.512 +**Functions at interface V1** + +#### 5.2.3 Electrical characteristics + +The electrical characteristics of interface V1 are not subject to ITU-T Recommendations. + +#### 5.2.4 Channel types, channel allocation and signalling + +The channel types associated with interface V1 include two B-channels and one D-channel as defined at the user network interface in Recommendation I.412 [B2]. In addition, the CV1 channel is required to support the operational and maintenance functions. + +The channel allocation is not subject to ITU-T Recommendations. + +The D-channel signalling procedures are defined in the Q.920 and Q.930-Series Recommendations. + +### **5.3 Interface V2** + +#### **5.3.1 General** + +Interface V2 is a generic digital interface used to connect remote or local digital network equipment via a first or second order digital section. This network equipment may support any combination of analogue, digital and ISDN subscriber access. The characteristics of this interface may not be structured according to the ISDN principles. + +#### **5.3.2 Functional characteristics** + +The functional characteristics depend on the specific application of the V2 interface. These are not generally subject to ITU-T Recommendations. + +#### **5.3.3 Electrical characteristics** + +The electrical characteristics of interface V2 are described in Recommendation G.703 [1]. The basic frame structure at interface V2 should be identical to that of the first or second order rate multiplexes described in Recommendation G.704 [2]. + +#### **5.3.4 Channel types, channel allocation and signalling** + +The channel types, channel allocation and signalling depend on the specific application of the V2 interface. These are not generally subject to ITU-T Recommendations. + +### **5.4 Interface V3** + +#### **5.4.1 General** + +Interface V3 is a digital interface used to connect digital subscriber equipment (e.g. PABX) via a generic digital subscriber section for the provision of a single primary rate access. The use of this interface to connect subscriber equipment with characteristics not structured according to the ISDN principles is not subject to ITU-T Recommendations. + +#### **5.4.2 Functional characteristics** + +Recommendations G.962 [6] and G.963 [7] define the access digital section which covers the functional and procedural aspects. The maintenance procedures, defined in Recommendation M.3604 [11] are taken into account in Recommendations G.962 [6] and G.963 [7]. + +#### **5.4.3 Electrical characteristics** + +The electrical characteristics of interface V3 are described in Recommendation G.703 [1]. + +The frame structure at interface V3 should be identical to that described in Recommendation G.704 [2]. + +#### **5.4.4 Channel types, channel allocation and signalling** + +The channel types and allocation associated with interface V3 are 30 B + 1 D at 2048 kbit/s or 23 B + 1 D at 1544 kbit/s as described in Recommendation I.431 [B4]. + +The channel allocation should also consider that: + +- a) When the signalling for the B-channels in one primary rate structure is carried by the D-channel in another primary rate structure, the channel timeslot normally used for signalling may be used to provide an additional B-channel. +- b) At interface V3 the designated number of B-channels is always present within the multiplexed channel structure, but one or more of the B-channels may not be used in any given application. + +The D-channel signalling procedures are defined in the Q.920 and Q.930-Series Recommendations. + +### 5.5 Interface V4 + +This interface is not considered to be a matter for ITU-T Recommendations. + +NOTE – See information provided in “Background”. + +### 5.6 Interface V5 + +#### 5.6.1 General + +Interface V5 is a digital interface (based on 2048 kbit/s) between an Access Network (AN) and the Local Exchange for the support of the following access types: + +- analogue telephone access; +- ISDN basic access with a line transmission system conforming to Recommendation G.960 [4] for the case with an NT1 separate from the AN; +- ISDN basic access with a user network interface according to Recommendation I.430 [B3] at the user side of the AN (i.e. the interface at the T reference point); +- ISDN primary rate access with a line transmission system conforming to Recommendation G.962 [6] for the case with an NT1 separate from the AN (V5.2 interface only); +- ISDN primary rate access with a user network interface according to Recommendation I.431 [B4] at the user side of the AN (i.e. the interface at the T reference point) (V5.2 interface only); +- other analogue or digital accesses for semi-permanent connections without associated outband signalling information. + +These access types are supported by interface V5 using flexible information channel (bearer channel) allocation with (for V5.2 interface as specified in Recommendation G.965 [9]) or without (for V5.1 interface as specified in Recommendation G.964 [8]) concentration capability within the AN. + +The AN is defined as a system implemented between the Local Exchange and the user, replacing part or the whole of the local line distribution network. The functions associated with the V5 interface of an AN can be configured and operated flexibly via a management Q interface. The detailed specification of the Q3 interface specifications for the V5 environment are contained in the Q.570-Series of Recommendations. The AN may consist of multiplexing, cross connect and transmission functions. + +The V5 interface may be implemented as a V5.1 or a V5.2 interface supporting different access types and providing different bearer channel handling capabilities as given above. The V5.1 interface consists of a single 2048 kbit/s interface while the V5.2 interface can be a multiple of 2048 kbit/s interface links with a maximum number of 16 interface links. + +#### 5.6.2 Functional characteristics + +The functional and procedural requirements of the interface shall conform to Recommendation G.704 [2] and G.706 [3], 2048 kbit/s case. The CRC-4 (CRC) procedure specified in Recommendations G.704 [2] and G.706 [3] shall be applied including the CRC error reporting using bit E in the CRC-multiframe. + +The functional description is illustrated in Figure 3. The following functional requirements are defined: + +- *Bearer channels* – To provide the bidirectional transmission capability for allocated B-channels from basic access user ports or PCM encoded 64 kbit/s channels from PSTN user ports. +- *ISDN D-channel information* – To provide the bidirectional transmission capability for D-channel information from basic access user ports (including Ds-, p- and f-type data). +- *PSTN signalling information* – To provide the bidirectional transmission capability for signalling information of PSTN user ports. + +- *Control of user ports* – To provide the bidirectional transmission capability to carry the status and control of each individual user port. +- *Control of the 2048 kbit/s link* – Frame alignment, multiframe alignment, alarm indication and CRC information of the 2048 kbit/s. +- *Control of layer 2 links* – To provide bidirectional communication capabilities to carry the various protocols. +- *Control for the support of common functions* – To provide synchronized application of provisioning data and restart capability. +- *Timing* – To provide the necessary timing information for bit transmission, octet identification and frame synchronization. +- *Control of 2048 kbit/s link related procedures* – To provide link identification and link blocking and unblocking capability ( $V_{5.2}$ only). +- *Control of bearer channel connections* – To provide on-demand bearer channel connection allocation and deallocation for the concentration function ( $V_{5.2}$ only). +- *Communication channel protection* – To control protection switching for communication channels affected by 2048 kbit/s link failure ( $V_{5.2}$ only). + +![Diagram showing the functional description of the V5 interface between an Access Network (AN) and a Local Exchange (LE). The diagram consists of 12 horizontal double-headed arrows representing different functional channels, stacked vertically between the AN and LE. From top to bottom, they are: Bearer channels, ISDN D channel information, PSTN signalling information, Port access control, Timing, Common control, Bearer channel connectiona), Link controla), Communication channel protectiona), Control of the 2048 kbit/s link, and two additional unlabeled arrows at the bottom. The label 'T1171360-95/d03' is in the bottom right corner.](007b053fe94a8348f75128a584503fd0_img.jpg) + +T1171360-95/d03 + +Diagram showing the functional description of the V5 interface between an Access Network (AN) and a Local Exchange (LE). The diagram consists of 12 horizontal double-headed arrows representing different functional channels, stacked vertically between the AN and LE. From top to bottom, they are: Bearer channels, ISDN D channel information, PSTN signalling information, Port access control, Timing, Common control, Bearer channel connectiona), Link controla), Communication channel protectiona), Control of the 2048 kbit/s link, and two additional unlabeled arrows at the bottom. The label 'T1171360-95/d03' is in the bottom right corner. + +a) For $V_{5.2}$ interface only. + +FIGURE 3/Q.512 +Functional description of the $V_5$ interface + +#### **5.6.3 Electrical characteristics** + +The V5.1 interface consists of a single 2048 kbit/s interface as defined in Recommendation G.703 [1]. + +The V5.2 interface may consist of a maximum of 16 times 2 048 kbit/s interface links as defined in Recommendation G.703 [1]. + +The electrical and physical characteristics of the interface for each interface link shall conform to Recommendation G.703 [1], 2048 kbit/s case. + +#### **5.6.4 Channel types, channel allocation and signalling** + +The information provided below is an excerpt of the detailed V5 interface specifications as contained in Recommendations G.964 [8] and G.965 [9]. + +##### **5.6.4.1 Channel types** + +The V5.1 interface or any link of the V5.2 interface shall be structured according to Recommendations G.704 [2] and G.706 [3]. Timeslots 1 to 31 shall be used for channel types allocated by provisioning: + +- timeslots which carry ISDN and PSTN bearer channels; +- communication channels which carry ISDN D-channel information, PSTN signalling information and control information; +- communication channels which carry information for the link control, the bearer connection control and the link protection (V5.2 only). + +##### **5.6.4.2 Channel allocation** + +There may be 1, 2 or 3 communication channels provisioned in the V5.1 interface. Only timeslots 16, 15 and 31 shall be assigned for communication channels. All timeslots not allocated for a communication channel may be allocated to bearer channels by provisioning. + +There may be 0, 1, 2 or 3 communication channels provisioned for any link of a V5.2 interface. Only timeslots 16, 15 and 31 shall be assigned for communication channels. All timeslots not allocated for a communication channel may be allocated to bearer channels under control of the bearer channel connection protocol. + +##### **5.6.4.3 Signalling** + +Signalling information for PSTN user ports are carried by a PSTN signalling protocol allocated to one of the provisioned communication channels. + +Signalling information for ISDN user ports, as well as p-type and f-type data, are frame relayed into the provisioned communication channels. + +Information for the control of user ports, links, bearer channel connections and protection of communication channels are carried by the relevant protocols in the assigned communication channels. + +The related Recommendations for the protocols are given in Recommendations G.964 [8] and G.965 [9]. + +## **6 Characteristics of analogue interfaces for subscriber access** + +### **6.1 Interface Z** + +Interface Z is a generic analogue interface defined at the exchange side of an analogue subscriber line used to connect subscriber equipment (e.g., single telephone set or PABX). + +It is recognized that the characteristics of analogue interfaces (generally designated Z-interface) vary considerably from country to country and therefore it is not intended that those interfaces be the subject of ITU-T Recommendations beyond those aspects covered in Recommendations Q.551 [B7] and Q.552 [B8]. + +## Appendix I + +# Bibliography + +(This appendix does not form an integral part of this Recommendation) + +- [B1] ITU-T Recommendation I.411 (1993), *ISDN user-network interfaces – Reference configurations.* +- [B2] CCITT Recommendation I.412 (1988), *ISDN user-network interfaces – Interface structures and access capabilities.* +- [B3] ITU-T Recommendation I.430 (1993), *Basic user-network interface – Layer 1 specification.* +- [B4] ITU-T Recommendation I.431 (1993), *Primary rate user-network interface – Layer 1 specification.* +- [B5] CCITT Recommendation Q.9 (1988), *Vocabulary of switching and signalling terms.* +- [B6] CCITT Recommendation Q.500 (1988), *Digital local, combined, transit and international exchanges, introduction and field of application.* +- [B7] ITU-T Recommendation Q.551 (1994), *Transmission characteristics of digital exchanges.* +- [B8] ITU-T Recommendation Q.552 (1994), *Transmission characteristics at 2-wire analogue interfaces of digital exchange.* \ No newline at end of file diff --git a/marked/Q/T-REC-Q.513-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.513-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2fd56c412107265037dcccbc5b3a53e7efdff13 --- /dev/null +++ b/marked/Q/T-REC-Q.513-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:916919c492b3fc6084b32dcfc0e658dfb84d5e6999bf565ab8c104950bc01bab +size 8276 diff --git a/marked/Q/T-REC-Q.513-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.513-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49d5b4d7ef3c13b4ce4d86bedf164dd138cf49e1 --- /dev/null +++ b/marked/Q/T-REC-Q.513-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e537060c8cd95f341df8c92fee4dda5e123b7ccb3311a63483afb13107084416 +size 69667 diff --git a/marked/Q/T-REC-Q.52-200103-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Q/T-REC-Q.52-200103-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..301cbc1a0fc7a39092197cac43f7fd9748a048d7 --- /dev/null +++ b/marked/Q/T-REC-Q.52-200103-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:253fb873a73dd168acebaf5d1203defd86e161d3c14fa6dd6dceb91556103a84 +size 22618 diff --git a/marked/Q/T-REC-Q.52-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.52-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/Q/T-REC-Q.52-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c +size 8232 diff --git a/marked/Q/T-REC-Q.52-200103-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/Q/T-REC-Q.52-200103-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62867530212f36e8c166fe8e6ac0ce036ce8e5da --- /dev/null +++ b/marked/Q/T-REC-Q.52-200103-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f91111620650beb01248dd0f94d6cf8b8f7a428680b7e4598824571cc7cd78e +size 32518 diff --git a/marked/Q/T-REC-Q.52-200103-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/Q/T-REC-Q.52-200103-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a854aade1870dc913944b65ae252caaaccfbbf9c --- /dev/null +++ b/marked/Q/T-REC-Q.52-200103-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a7e0ce3893d4e848d207b975e071968ff470f99549a8845ea84852133c8530a +size 19854 diff --git a/marked/Q/T-REC-Q.52-200103-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Q/T-REC-Q.52-200103-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8917801bb5a4230ac403a2cec116929c907fa47 --- /dev/null +++ b/marked/Q/T-REC-Q.52-200103-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c565ee55c033fe4f83fe8f31b3b8d4cac25d02854b309224b8a8e72c1fd0fa16 +size 16739 diff --git a/marked/Q/T-REC-Q.544-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.544-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cb601975a46b1521d52d66736b4703a0ec48847 --- /dev/null +++ b/marked/Q/T-REC-Q.544-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1366c1f376d9aa95f399105a2d3a970895c3d47cfe3027a59b3004724028b4ae +size 31072 diff --git a/marked/Q/T-REC-Q.544-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.544-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.544-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.544-198811-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/Q/T-REC-Q.544-198811-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77176f61bb80824183d342ba7a7527578f04fbc5 --- /dev/null +++ b/marked/Q/T-REC-Q.544-198811-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22a254ca05e8cb652794a9271395363ac462842a31b7f7d6ee3e3c7cb93958c5 +size 19018 diff --git a/marked/Q/T-REC-Q.544-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.544-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4456998828ef6a5825c446d6976185ba66e6877 --- /dev/null +++ b/marked/Q/T-REC-Q.544-198811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0faa4b9c45754469bbba678d084b8da7366d02e5d7d12ca20e44920f6b2cb329 +size 216780 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..932669ada36d2c139142fc17f1d89386f80009c8 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:358941becf5fd730d4eee98ccf0480f39801a54e151c04956ab83f126b9e5c3d +size 30562 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9a73fc11201dfc5f3a9752bed19c95ba2cf83ef --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f94b812f63e7cf07dcea14b1f97569343a4bfb00f31ddcb34802ca7e87e2dd7 +size 19570 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/157e8c1d80a02c8eee893c2ea60a77a8_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/157e8c1d80a02c8eee893c2ea60a77a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..946d53b70f149a538cc55b7494f38151921b8e96 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/157e8c1d80a02c8eee893c2ea60a77a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ced76ff60fe4ae24b2649bd368feb6fbb4f938371d3e39914d66821a1aa82773 +size 37838 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e32bbdd10fb37e9662d6c98cc6a7e93f03b23d62 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdddfc95e866ecb92fc6a47a83f559c62ea16c00764ecfceea514ae80d8f02cb +size 55711 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2405e00951651d913524b54a0749de9846b81c39 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2baab15a56b913b87dd3bd61dff65409df99e0ee2be2e75368f4a3efa7d13ca +size 45720 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/27b22513fc27a0ff5f230b062ad3112f_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/27b22513fc27a0ff5f230b062ad3112f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4b348ab589e37866a18167310f71a31c6d0a332 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/27b22513fc27a0ff5f230b062ad3112f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5974a63fbfc9564657185e8f47a3c89304db6c4f96be5410153b6939df6dac0 +size 24148 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-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.552-200111-I_PDF-E/333c2aedd53d78a421f9ec6517b0f47b_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/333c2aedd53d78a421f9ec6517b0f47b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1568fcad7f80c1fa4f89b5547828064ac4094023 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/333c2aedd53d78a421f9ec6517b0f47b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50cba1a4a5085c1d5e4e32dca8a1505abf7519f4f7797179f94972a0476d3e9d +size 6120 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9e17a5bec50c5178cd7d5d4de233a834d8d6b0f --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d160c7f628f3b849003c0ae90bca338aa6f938d43a56fb2ba6cdd1436b4b392 +size 29073 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daa85e799ea3d6c11a3176848ebe84d41d309c4b --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3483197eb7ce9c3a649aea08e00ab2b9cb36287933a4a74078c7be40f91a4c3 +size 46649 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/5500ab73cf84ccc0055eecf28889b4db_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/5500ab73cf84ccc0055eecf28889b4db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f9b4bb5b27494b08b6daa71aff6602055aa2f29 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/5500ab73cf84ccc0055eecf28889b4db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d8788a604a3e3c0288aab9470e2c631e2b0c1b0ac67d831084c945ef2a390f0 +size 48585 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c552c98c9525256fadff6e4782939b86cd913f90 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:789c5cd48cc77c47cacecfbbd17969e40e48c7d64b71c90c7f3b280bb7037aab +size 42576 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/65a73373b57df71e5c2ce1ce0eb7b65d_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/65a73373b57df71e5c2ce1ce0eb7b65d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e710fe998e879476ee7b138bbe6ddd101950693f --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/65a73373b57df71e5c2ce1ce0eb7b65d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e24e3cfaff57a03df2888ba42544fbafbd2eb40cd8d0d5d92d79691ff1b00b3c +size 72726 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bce66b89f7682f6eab8dc4768cf819c8b8c2a7f --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70f376edfb2167d795c5bee9f61417975800195a1f28e92ecc2654300b5aa690 +size 56841 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3443089ad1100e97a4ec3fc5c71d5daf0c66abce --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c199d4c12eacf9c44f756204a17cba0d44aec184bd03008eb7d2bf624cc2f0f9 +size 46780 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b050078d5be6bfc78d43b2b8012da45bed4c768 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5e277dec112b489f8e8e9b2ce1d172368f69f1da2462b7a6adc5b91cdd3c02a +size 44482 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ce8788dd47e5618094ac36dc43a81dbe41cdf6c --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f088b70cafcb2ccab861343f99e977d94b2dcad6504f528d70f0b2a1d2f3d936 +size 49548 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/96a7eac66ef72bb016c280278506ac63_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/96a7eac66ef72bb016c280278506ac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..524c453ee486f52ae13e00e864c5e29738a033b5 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/96a7eac66ef72bb016c280278506ac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22e302c297ff42cfb827ca9587718a9a67a2a694b70e62963d480367cecc7278 +size 23563 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/9b5411fa2d169b66f6185fbf67b49766_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/9b5411fa2d169b66f6185fbf67b49766_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f48c4f58aa4f5d32c49a48f045848a913597ab9 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/9b5411fa2d169b66f6185fbf67b49766_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:738224875dcc6c632200c4b44d4c8c97de2c0d296a47106d35ea52f576553c69 +size 23819 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/9db774ce7e2ae9d89f439a41156214dd_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/9db774ce7e2ae9d89f439a41156214dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5528b78a8f5e851cc6c0f2526f84651c648d4d2 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/9db774ce7e2ae9d89f439a41156214dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b086dddab9b2c4f69734133cdae7f383be99cc0737a5d96d8ab741ec2c509306 +size 68865 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccbf21d36553396fba1dad240ad68d46661db6b2 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0afb946b720eba1b676c4d6911bcd873097ece19fe2c3f9251cc1e13b7204e1d +size 60437 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef8de5ad4c05f163d9f298298318a721b3e5eaf9 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43c0d146150eba002c4ca0632c6aba0f0f409307ac9da9cb8291fe5e746d984d +size 25924 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffd84ef6c60ba00e470da083191b6f50a4c97671 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4927dae09f6055eba26b3806400d5163a3c15a0123b808e20b90284d779cab8 +size 47682 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..329365431405cf4ba4717da5f31bfbcf85d310fd --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d48f07dd75b9954d413bd5cdadb1c3bb5404844bfd3d3829893784b51171356 +size 23254 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56d0f6fef7c771856fbbbf0398ac293206e31460 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cffbdf86302828c9f4ddeedfd3487d2425bc333d052f2194e94e6437062322c +size 25552 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab81fca6bd03e0b4b07435aed44344dddf81da9f --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afd971ccdd498e7dcec868896c38f9aa6ec90f80cc78ca4885b158f503e2ff41 +size 9238 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30f19efa761f8b77eac49a1420e60bb415f00da6 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bf4cfcc21f472ad843b740f4568d7a4804a0154a086dffafc7bf52bfecaa228 +size 48541 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f77c167490130fd779c1680892a15f40b72fb95 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74e19564a59cd309cf45466b3094e717d069ef4e8dfce53b78424ebd6ef8c7c6 +size 30745 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/f899c67120dc04a5e5a5c2d94461a077_img.jpg b/marked/Q/T-REC-Q.552-200111-I_PDF-E/f899c67120dc04a5e5a5c2d94461a077_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c9b6075a9919466eb694cd2b4ac95ffbedb2bc7 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/f899c67120dc04a5e5a5c2d94461a077_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c11cfb2c19cdcdbcf5976725bd3d5033747751dba2affed226e549a30d686611 +size 70492 diff --git a/marked/Q/T-REC-Q.552-200111-I_PDF-E/raw.md b/marked/Q/T-REC-Q.552-200111-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e1378205635747e68863a8558b5af7ae340ffc29 --- /dev/null +++ b/marked/Q/T-REC-Q.552-200111-I_PDF-E/raw.md @@ -0,0 +1,1264 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.552** + +(11/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Digital exchanges – Transmission characteristics + +--- + +**Transmission characteristics at 2-wire analogue +interfaces of digital exchanges** + +ITU-T Recommendation Q.552 + +--- + +# 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 | +| Introduction and field of application | Q.500-Q.509 | +| Exchange interfaces, functions and connections | Q.510-Q.539 | +| Design objectives and measurement | Q.540-Q.549 | +| Transmission characteristics | Q.550-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.552** + +# **Transmission characteristics at 2-wire analogue interfaces of digital exchanges** + +## **Summary** + +This Recommendation provides characteristics for 2-wire analogue interfaces, input and output connections with 2-wire analogue interfaces and half-connections with 2-wire analogue interfaces in accordance with definitions given in ITU-T Q.551. + +This Recommendation is valid for equipment that may terminate an international long-distance connection via 4-wire circuits interconnected by 4-wire exchange. It also includes, in a separate category, characteristics for interfaces which cannot terminate an international connection and are therefore entirely national in application. + +## **Source** + +ITU-T Recommendation Q.552 was prepared by ITU-T Study Group 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 November 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, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +###### Page + +| | | | +|------------|---------------------------------------------------------------------------------|----| +| 1 | General ..... | 1 | +| 2 | Characteristics of interfaces ..... | 1 | +| 2.1 | Characteristics of interface $C_2$ ..... | 1 | +| 2.1.1 | Exchange impedance ..... | 1 | +| 2.1.2 | Impedance unbalance about earth ..... | 2 | +| 2.1.3 | Relative levels ..... | 3 | +| 2.2 | Characteristics of interface $Z$ ..... | 4 | +| 2.2.1 | Exchange impedance ..... | 4 | +| 2.2.2 | Impedance unbalance about earth ..... | 5 | +| 2.2.3 | Relative levels ..... | 5 | +| 3 | Characteristics of half-connections ..... | 7 | +| 3.1 | Characteristics common to all 2-wire analogue interfaces ..... | 7 | +| 3.1.1 | Transmission loss ..... | 7 | +| 3.1.2 | Group delay ..... | 9 | +| 3.1.3 | Single frequency noise ..... | 10 | +| 3.1.4 | Crosstalk ..... | 10 | +| 3.1.5 | Total distortion including quantizing distortion ..... | 12 | +| 3.1.6 | Discrimination against out-of-band signals applied to the input interface ..... | 12 | +| 3.1.7 | Spurious out-of-band signals received at the output interface ..... | 12 | +| 3.1.8 | Echo and stability ..... | 12 | +| 3.2 | Characteristics of interface $C_2$ ..... | 15 | +| 3.2.1 | Nominal value of transmission loss ..... | 15 | +| 3.2.2 | Noise ..... | 15 | +| 3.2.3 | Values of total distortion ..... | 16 | +| 3.3 | Characteristics of interface $Z$ ..... | 17 | +| 3.3.1 | Nominal value of transmission loss ..... | 17 | +| 3.3.2 | Noise ..... | 18 | +| 3.3.3 | Values of total distortion ..... | 18 | +| Appendix I | – Impedance strategy in 2-wire networks ..... | 19 | +| I.1 | Introduction ..... | 19 | +| I.2 | General equations for unloaded cables ..... | 22 | +| I.3 | General impedance considerations of a hybrid ..... | 23 | +| I.3.1 | Cable input impedance $Z_2$ and the hybrid input impedance $Z_T$ ..... | 23 | +| I.3.2 | Balance impedance $Z_B$ ..... | 23 | +| I.4 | Echo considerations ..... | 23 | +| I.4.1 | Talker echo loudness rating TELR ..... | 23 | + +| | Page | | +|-------|--------------------------------------------------------------------------------------|----| +| I.4.2 | Sidetone masking rating STMR and listener sidetone rating LSTR..... | 24 | +| I.5 | Applications ..... | 25 | +| I.6 | Analysis of loop impedance variation by means of a special impedance diagram ..... | 25 | +| I.7 | Conclusions..... | 27 | +| I.8 | Examples of impedances $Z_2$ and compromise nominal impedances $Z_T$ and $Z_B$ ..... | 27 | +| I.8.1 | Cable input impedance $Z_2$ and hybrid input impedance $Z_T$ ..... | 28 | +| I.8.2 | Balance impedance $Z_B$ ..... | 30 | +| I.8.3 | Application of the special impedance diagram..... | 30 | +| I.8.4 | Echo considerations ..... | 32 | + +# Transmission characteristics at 2-wire analogue interfaces of digital exchanges + +# 1 General + +This Recommendation provides characteristics for: + +- 2-wire analogue interfaces (Type C2 and Z); +- input and output connections with 2-wire analogue interfaces; and +- half-connections with 2-wire analogue interfaces; + +in accordance with definitions given in ITU-T Q.551 particularly in Figure 1/Q.551. + +The characteristics of the input and output connections of a given interface are not necessarily the same. The characteristics of half-connections are not necessarily identical for different types of interfaces. + +This Recommendation is valid for equipment that may terminate an international long-distance connection via 4-wire circuits interconnected by 4-wire exchanges. It also includes, in a separate category, characteristics for interfaces which cannot terminate an international connection and are therefore entirely national in application. + +## 2 Characteristics of interfaces + +NOTE – For measuring 2-wire analogue interface conditions it is necessary to apply a quiet code, i.e. a PCM signal corresponding to decoder output value 0 ( $\mu$ -law) or output value 1 (A-law), with the sign bit in a fixed state, to the exchange test point Ti, when no test signal is stipulated. + +### 2.1 Characteristics of interface C2 + +The recommended values of interfaces C2 are valid for digital exchanges including PABXs with transit functions and routing capabilities for originating and terminating traffic. Depending on the type of traffic to be handled, two different sets of relative levels are required. This suggests subdivision into C21 and C22 interface specifications. The interface C21 provides the termination of outgoing and incoming international long-distance connections and possible national connections, with the exchange acting as transit switch. The interface C22 provides for the connection of a 2-wire trunk line. A typical example is the interconnection of a Z interface with a C22 interface in a local exchange for routing through the 2-wire analogue trunk network. A C22 interface cannot be part of the international 4-wire chain (see Figure 2/Q.551). + +#### 2.1.1 Exchange impedance + +##### 2.1.1.1 Nominal value + +Nominal values of exchange impedance should be defined depending on national conditions. The definition shall include a test network for the exchange impedance. Network operators may want to adopt different test networks corresponding to the cable types used (e.g. unloaded and loaded). + +##### 2.1.1.2 Return loss + +The return loss of the impedance presented by a C2 interface against the test network for the exchange impedance should comply with the limits given in Figure 1. + +![Figure 1/Q.552: Minimum value of return loss against the test network for the exchange impedance at a 2-wire interface. The graph shows Return loss (dB) on the y-axis (14 to 18) versus Frequency (f) in Hz on the x-axis (300 to 3400). The return loss is 14 dB at 300 Hz, rises to 18 dB at 500 Hz, stays at 18 dB until 2000 Hz, and then falls back to 14 dB at 3400 Hz. A shaded region indicates the minimum required return loss.](c3c305cefbac2e7b13be34ab87054d1e_img.jpg) + +| Frequency (f) [Hz] | Return loss [dB] | +|--------------------|------------------| +| 300 | 14 | +| 500 | 18 | +| 2000 | 18 | +| 3400 | 14 | + +Figure 1/Q.552: Minimum value of return loss against the test network for the exchange impedance at a 2-wire interface. The graph shows Return loss (dB) on the y-axis (14 to 18) versus Frequency (f) in Hz on the x-axis (300 to 3400). The return loss is 14 dB at 300 Hz, rises to 18 dB at 500 Hz, stays at 18 dB until 2000 Hz, and then falls back to 14 dB at 3400 Hz. A shaded region indicates the minimum required return loss. + +**Figure 1/Q.552 – Minimum value of return loss against the test network for the exchange impedance at a 2-wire interface** + +#### 2.1.2 Impedance unbalance about earth + +The Longitudinal Conversion Loss (LCL) at the interface, defined in 4.1.3/G.117, should exceed the minimum values of Figure 2 with the equipment under test in the normal talking state, in accordance with ITU-T K.10. + +NOTE 1 – A network operator may adopt other values and in some cases a wider bandwidth, depending on actual conditions in its telephone network. + +NOTE 2 – A limit may also be required for the Transverse Conversion Loss (TCL), as defined in 4.1.2/G.117, if the exchange termination is not reciprocal with respect to the transverse and longitudinal paths. A suitable limit would be 40 dB to ensure an adequate near-end crosstalk attenuation between interfaces. + +![Figure 2/Q.552: Minimum values of LCL measured in the arrangement shown in Figure 3. The graph shows LCL (dB) on the y-axis (0 to 50) versus Frequency (f) in Hz on the x-axis (300 to 3400). The LCL is 40 dB from 300 Hz to 600 Hz, then rises to 46 dB from 600 Hz to 3400 Hz. A shaded region indicates the minimum required LCL.](27b22513fc27a0ff5f230b062ad3112f_img.jpg) + +| Frequency (f) [Hz] | LCL [dB] | +|--------------------|----------| +| 300 | 40 | +| 600 | 46 | +| 3400 | 46 | + +Figure 2/Q.552: Minimum values of LCL measured in the arrangement shown in Figure 3. The graph shows LCL (dB) on the y-axis (0 to 50) versus Frequency (f) in Hz on the x-axis (300 to 3400). The LCL is 40 dB from 300 Hz to 600 Hz, then rises to 46 dB from 600 Hz to 3400 Hz. A shaded region indicates the minimum required LCL. + +**Figure 2/Q.552 – Minimum values of LCL measured in the arrangement shown in Figure 3** + +##### Test method + +Longitudinal conversion loss at the $C_2$ equipment port should be measured in accordance with the principles given in 4.1/O.9. Figure 3 shows an example of the basic measuring arrangement for digital exchanges. Arrangements containing two resistors each of value $R/2$ may also be used (see 5.1/O.9). + +Measurements of the longitudinal and transverse voltages should preferably be done with a frequency-selective level meter. + +![Circuit diagram for measuring Longitudinal Conversion Loss (LCL). A sinusoidal oscillator is connected to a balance network consisting of a resistor R/4, an inductor, a resistor R, and a variable capacitor VT1. The oscillator output is VL1. The balance network is connected to an interface labeled 'C2 or Z'. The 'Item under test' is connected to this interface and has two output terminals labeled 'Exchange test points', with voltages T0 and T1 indicated. The diagram is labeled T1515500-94.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Circuit diagram for measuring Longitudinal Conversion Loss (LCL). A sinusoidal oscillator is connected to a balance network consisting of a resistor R/4, an inductor, a resistor R, and a variable capacitor VT1. The oscillator output is VL1. The balance network is connected to an interface labeled 'C2 or Z'. The 'Item under test' is connected to this interface and has two output terminals labeled 'Exchange test points', with voltages T0 and T1 indicated. The diagram is labeled T1515500-94. + +R should be in the range of 600-900 Ω + +$$\text{Longitudinal conversion loss (LCL)} = 20 \log_{10} \left| \frac{V_{LI}}{V_{TI}} \right| \text{ dB}$$ + +NOTE 1 – Provisions should be made for representative DC currents to be present. + +NOTE 2 – Special care must be taken in those applications using active hybrids. + +**Figure 3/Q.552 – Arrangement for measuring LCL** + +#### 2.1.3 Relative levels + +##### 2.1.3.1 Nominal levels + +###### 2.1.3.1.1 Interface C21 + +C21 interfaces should meet the recommended values for Z interfaces in 2.2.3.1 if no loss compensation comparable to 2.2.3.3 is provided. + +###### 2.1.3.1.2 Interface C22 + +To adjust the transmission loss of a digital transmission section to the values of national transmission planning for local or national traffic, depending on the relative levels given in 2.1.3.1.1 and 2.2.3.1, the following ranges encompass the requirements for C22 interfaces of a large number of network operators: + +- input level: $L_i = +3.0$ to $-7.0$ dBr in 0.5 dB steps; +- output level: $L_o = +1.0$ to $-8.0$ dBr in 0.5 dB steps. + +In order to compensate loss on long toll or junction lines, a network operator may, to satisfy local conditions, choose values of relative levels derived from the basic values as follows: + +$$L'_i = L_i + x \text{ dB}$$ + +$$L'_o = L_o - x \text{ dB}$$ + +where $x$ should take a negative value. The value of $x$ is in national competence. Such compensation of loss requires careful selection and application of balance networks. + +It has been recognized that it is not necessary for a particular design of equipment to be capable of operating over the entire level range. + +##### 2.1.3.2 Tolerances of relative levels + +The difference between the actual relative level and the nominal relative level should lie within the following values: + +- input relative level: –0.3 to +0.7 dB; +- output relative level: –0.7 to +0.3 dB. + +These differences may arise, for example, from design tolerances, cabling between analogue ports and the (DF), and adjustment increments. + +NOTE – Level adjustment procedures are given in clause 3/G.712. + +### 2.2 Characteristics of interface Z + +The recommended values of interface Z are valid for digital local exchanges, PABXs and digital remote units. For PABXs, see 2.1.1/Q.551. + +#### 2.2.1 Exchange impedance + +Guidance for network operators can be found in Appendix I. + +##### 2.2.1.1 Nominal value + +The principal criterion governing the choice of the nominal value of the exchange impedance is to ensure an adequate sidetone performance for telephone sets, particularly those operated on short lines. If this criterion is met, the impedance will also be suitable for subscriber lines fitted with voiceband modems. + +As a general rule a complex exchange impedance with a capacitive reactance is necessary to achieve satisfactory values of stability, echo and sidetone. For additional information, see ITU-T G.111 and ITU-T G.121. + +The use of the preferred configuration below will minimize the diversity of types of exchange impedances. At present no unique component values can be recommended. However, to provide guidance for network operators, examples of nominal values chosen by some network operators are given in Table 1. + +**Table 1/Q.552 – Test networks for exchange impedances being considered** + +| | Rs (ohms) | Rp (ohms) | Cp (farads) | +|--------------|------------------|------------------|--------------------| +| Austria, FRG | 220 | 820 | 115 n | +| BT | 300 | 1000 | 220 n | +| NTT | 600 | infinity | 1 μ | +| USA | 900 | infinity | 2.16 μ | +| ETSI | 270 | 750 | 150 n | + +![Circuit diagram of the test network for exchange impedances. It shows a series resistor Rs connected to a parallel combination of a resistor Rp and a capacitor Cp. The input and output terminals are on the left and right respectively. The label T1515510-94 is present below the diagram.](333c2aedd53d78a421f9ec6517b0f47b_img.jpg) + +NOTE 1 – The test network and the component values represent a configuration that exhibits the required exchange impedance. It need not necessarily correspond to any actual network provided in the exchange interface. + +**Table 1/Q.552 – Test networks for exchange impedances being considered** + +NOTE 2 – The range of component values reflects the fact that there are substantial differences in the sensitivity and sidetone performance of the various telephone instruments throughout the world. In general, the combination of short lines and sensitive telephone sets might be rather common in the future due to increased use of remote concentration. In order to control sidetone performance, network operators need to take into account telephone set parameters. Not only should the parameters of existing telephone sets be considered but also the parameters that may be desirable in the future to allow improvement in sidetone performance to be achieved. + +NOTE 3 – It may be necessary to group the subscriber lines of a particular exchange into classes, each requiring a different exchange impedance of the Z interface. + +##### 2.2.1.2 Return loss + +Tolerances are needed for values of exchange impedance. For this purpose, the return loss of the impedance presented by a 2-wire interface against the test network for the exchange impedance should comply with limits which depend on the particular conditions of the subscriber network considered. These are given in the template of Figure 1. + +Some network operators may want to specify higher values. Examples of limit values for the return loss, currently accepted by some network operators, are given in Table 2 for guidance. + +**Table 2/Q.552 – Examples of limit values of return loss against the exchange impedance** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Austria | 14.5 dB at 300 Hz, rising ( $\log f$ scale) to 18 dB at 500 Hz remaining at 18 dB to 2500 Hz and then falling ( $\log f$ scale) to 14.5 dB at 3400 Hz. | +| BT | 18 dB: 200-800 Hz; 20 dB: 800-2000 Hz; 24 dB: 2000-4000 Hz. | +| FRG, ETSI | 14 dB at 300 Hz, rising ( $\log f$ scale) to 18 dB at 500 Hz remaining at 18 dB to 2000 Hz and then falling ( $\log f$ scale) to 14 dB at 3400 Hz. | +| NTT | 22 dB: 300-3400 Hz. | +| USA | 20 dB: 200-500 Hz; 26 dB: 500-3400 Hz. | +| NOTE – The 12 dB spread in values stems from the difference in telephone sets and subscriber loops characteristics. See also Appendix I. | | + +#### 2.2.2 Impedance unbalance about earth + +The Longitudinal Conversion Loss (LCL) at the equipment post of the Z interface should meet the values given in 2.1.2 and Figure 2, measured in accordance with the test method given in Figure 3. + +#### 2.2.3 Relative levels + +Operation of the Z interface in the ranges of relative levels given below is recommended when the interface terminates an entirely 4-wire international long-distance connection. Pairs of input and output levels can be chosen for internal, local, or national long-distance traffic in a wider range if these connections can be discriminated from international ones for correct level switching. If digital pads are used, the additional distortion must be considered (see Table 1/G.113). + +In assigning the relative levels for international long-distance connections to the interface, it should be noted that: + +- The limiting of "difference in transmission loss between the two directions of transmission" in 2.2/G.121 must be taken into account. For the national extension, this is the value "loss (t-b)-loss(a-t)". (See the text in the cited Recommendation for guidance.) This difference is + +limited to $\pm 4$ dB. However, to allow for additional asymmetry of loss in the rest of the national network, only part of this difference can be used by the digital exchange. + +- If within the ranges of $L_i$ and $L_o$ given under 2.2.3.1.1 and 2.2.3.1.2, the values are chosen such that $L_i - L_o \geq 6$ dB and if adequate balance networks are used (e.g. 3.1.8 and Figure 10), the requirements of clause 6/G.121 (Incorporation of PCM digital processes in national extensions) as well as for ITU-T G.122 (Stability and echo loss) will be satisfied. + +##### 2.2.3.1 Nominal levels + +###### 2.2.3.1.1 Input relative level + +According to Annex C/G.121 (columns 3, 5 and 7 of Table C.1/G.121), the following range of input relative level for all types of connections (internal, local, national and international) encompasses the requirements of a large number of network operators: + +$$L_i = 0 \text{ to } +2.0 \text{ dBr}$$ + +NOTE – Clause 3.6/G.101 and clause 3/G.121 indicate that if the minimum nominal Send Loudness Rating (SLR) of the local system under the same conditions is not less than $+2$ dB, then the peak power of the speech will be suitably controlled. It follows that, for instance, the value $L_i = 0$ dBr (lower limit of the range for $L_i$ ) is suited to a send loudness rating $\geq +2$ dB. + +###### 2.2.3.1.2 Output relative level + +According to Annex C/G.121 (column 6 of Table C.1/G.121), the following range of output relative level for international long-distance connections encompasses the requirements of a large number of network operators: + +$$L_o = -5.0 \text{ to } -8.0 \text{ dBr}$$ + +The chosen value may be used for connections entirely within a national network as well. + +The nominal output relative levels for local or national connections can take other values in accordance with national transmission planning. According to Annex C/G.121 (columns 2 and 4 of Table C.1/G.121), the following range encompasses the requirements of a large number of network operators: + +$$L_o = 0 \text{ to } -8.0 \text{ dBr}$$ + +It has been recognized that it is not necessary for a particular design of equipment to be capable of operating over the entire range. + +##### 2.2.3.2 Tolerances of relative levels + +The difference between the actual relative level and the nominal relative level should lie within the following limits: + +- input relative level: $-0.3$ to $+0.7$ dB; +- output relative level: $-0.7$ to $+0.3$ dB. + +These differences may arise, for example, from design tolerances, cabling (between analogue ports and the DF) and adjustment increments. Short-term variation of loss with time as discussed in 3.1.1.3 is not included. + +NOTE – Procedures for adjusting relative level are given in clause 3/G.712. + +##### 2.2.3.3 Consideration of short and long subscriber lines + +In order to compensate for the loss of short or long subscriber lines, a network operator may choose values of the relative levels derived from the basic values as follows: + +$$L'_i = L_i + x \text{ dB}$$ + +$$L'_o = L_o - x \text{ dB}$$ + +The value of $x$ is within national competence (e.g. $x = 3 \text{ dB}$ for short subscriber lines). + +The use of values of $x < 0$ requires careful selection of balance networks; values of $x < -3 \text{ dB}$ are not recommended. + +## 3 Characteristics of half-connections + +For interfaces $C_2$ , this Recommendation is valid for digital local and transit exchanges and for $C_{21}$ interfaces of PABXs connected to the digital local exchange by a digital transmission system. + +For interface $Z$ , this Recommendation is valid for digital local and combined local/transit exchanges, for PABXs and for digital remote units, each connected to the digital local exchange by a digital transmission system. For further information concerning PABXs, see 2.1.1/Q.551. + +NOTE – In measuring an input connection it is necessary to apply a quiet code, i.e. a PCM signal corresponding to decoder output value 0 ( $\mu$ -law) or output value 1 (A-law) with the sign bit in a fixed state to the exchange test point $T_i$ . (See 1.2.3.1/Q.551.) + +### 3.1 Characteristics common to all 2-wire analogue interfaces + +#### 3.1.1 Transmission loss + +##### 3.1.1.1 Nominal value + +The nominal transmission loss according to 1.2.4.1/Q.551 is defined in 3.2.1 and 3.3.1 for input and output connections of half-connections with a 2-wire analogue interface. + +##### 3.1.1.2 Tolerances of transmission loss + +The difference between the actual transmission loss and the nominal transmission loss of an input or output connection, according to 2.1.3.2 and 2.2.3.2 should lie within the following range: + +$$-0.3 \text{ to } +0.7 \text{ dB}$$ + +These differences may arise, for example, from design tolerances, cabling (between analogue interfaces and the DF) and adjustment increments. Short-term variation of loss with time as discussed in 3.1.1.3 is not included. + +##### 3.1.1.3 Short-term variation of loss with time + +When a sine wave test signal at the reference frequency of 1020 Hz and at a level of $-10 \text{ dBm}0$ is applied to the 2-wire analogue interface of any input connection, or a digitally simulated sine wave signal of the same characteristic is applied to the exchange test point $T_i$ of any output connection, the level at the corresponding exchange test point $T_o$ and the 2-wire analogue interface respectively should not vary by more than $\pm 0.2 \text{ dB}$ during any 10-minute interval of typical operation under the steady state condition of permitted variations in the power supply voltage and temperature. + +##### 3.1.1.4 Variation of gain with input level + +With a sine wave test signal at the reference frequency 1020 Hz and at a level between $-55 \text{ dBm}0$ and $+3 \text{ dBm}0$ applied to the 2-wire analogue interface of any input connection, or with a digitally simulated sine wave signal of the same characteristic applied to the exchange test point $T_i$ of any output connection, the gain variation of that connection, relative to the gain at an input level of $-10 \text{ dBm}0$ , should lie within the limits given in Figure 4. + +The measurement should be made with a frequency-selective level meter to reduce the effect of the exchange noise. This requires a sinusoidal test signal. + +![Figure 4/Q.552 – Variation of gain with input level. A graph showing gain variation in dB versus input level in dBm0. The y-axis ranges from -1.6 to 1.6 dB with major ticks at -1.6, -0.6, -0.3, 0, 0.3, 0.6, and 1.6. The x-axis ranges from -55 to +3 dBm0 with major ticks at -55, -50, -40, -10, and +3. A shaded region represents the gain variation limits. The upper limit is 1.6 dB from -55 to -50 dBm0, then drops to 0.6 dB from -50 to -40 dBm0, then to 0.3 dB from -40 to +3 dBm0. The lower limit is -1.6 dB from -55 to -50 dBm0, then drops to -0.6 dB from -50 to -40 dBm0, then to -0.3 dB from -40 to +3 dBm0. A circled 'X' is marked on the 0 dB line at -10 dBm0. The text 'T1515530-94' is in the bottom right corner.](0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg) + +Gain variation + +dB + +1.6 + +0.6 + +0.3 + +0 + +-0.3 + +-0.6 + +-1.6 + +-55 -50 -40 -10 +3 dBm0 + +Input level + +T1515530-94 + +Figure 4/Q.552 – Variation of gain with input level. A graph showing gain variation in dB versus input level in dBm0. The y-axis ranges from -1.6 to 1.6 dB with major ticks at -1.6, -0.6, -0.3, 0, 0.3, 0.6, and 1.6. The x-axis ranges from -55 to +3 dBm0 with major ticks at -55, -50, -40, -10, and +3. A shaded region represents the gain variation limits. The upper limit is 1.6 dB from -55 to -50 dBm0, then drops to 0.6 dB from -50 to -40 dBm0, then to 0.3 dB from -40 to +3 dBm0. The lower limit is -1.6 dB from -55 to -50 dBm0, then drops to -0.6 dB from -50 to -40 dBm0, then to -0.3 dB from -40 to +3 dBm0. A circled 'X' is marked on the 0 dB line at -10 dBm0. The text 'T1515530-94' is in the bottom right corner. + +**Figure 4/Q.552 – Variation of gain with input level** + +##### **3.1.1.5 Loss distortion with frequency** + +The loss distortion with frequency of any input or output connection according to 1.2.5/Q.551 should lie within the limits shown in the mask of Figure 5 a) or 5 b) respectively using an input level of $-10$ dBm0. + +NOTE – The limits of this clause shall not apply to Z half-connections which include equalization for the loss distortion in the subscriber line. + +![Graph of Loss (dB) vs Frequency (f) in kHz for input connection. The y-axis ranges from -0.3 to 1.7 dB with major ticks at -0.3, 0, 0.35, 0.45, 0.55, 0.7, 0.75, 1.0, 1.5, and 1.7. The x-axis ranges from 0 to 3.6 kHz with major ticks at 0, 0.2, 0.3, 0.4, 0.6, 1.0, 2.0, 2.4, 3.0, 3.4, and 3.6. The graph shows a shaded region representing loss limits. From 0 to 0.2 kHz, the loss is 0 dB. At 0.2 kHz, it drops to -0.3 dB. At 0.3 kHz, it rises to 1.7 dB. At 0.4 kHz, it drops to 1.0 dB. At 0.6 kHz, it drops to 0.75 dB. At 1.0 kHz, it drops to 0.45 dB. At 2.0 kHz, it drops to 0.35 dB. At 2.4 kHz, it rises to 0.75 dB. At 3.0 kHz, it rises to 1.7 dB. At 3.4 kHz, it rises to 1.7 dB. At 3.6 kHz, it drops to 0 dB. There are 'Note' labels in the regions [0.6, 2.0] at 0.45 dB, [2.0, 3.0] at 0.75 dB, and [3.0, 3.6] at 1.7 dB. A small circle with an 'x' is at 1.0 kHz, 0 dB.](71ab4df17511d75261da8d462d643b1a_img.jpg) + +Graph of Loss (dB) vs Frequency (f) in kHz for input connection. The y-axis ranges from -0.3 to 1.7 dB with major ticks at -0.3, 0, 0.35, 0.45, 0.55, 0.7, 0.75, 1.0, 1.5, and 1.7. The x-axis ranges from 0 to 3.6 kHz with major ticks at 0, 0.2, 0.3, 0.4, 0.6, 1.0, 2.0, 2.4, 3.0, 3.4, and 3.6. The graph shows a shaded region representing loss limits. From 0 to 0.2 kHz, the loss is 0 dB. At 0.2 kHz, it drops to -0.3 dB. At 0.3 kHz, it rises to 1.7 dB. At 0.4 kHz, it drops to 1.0 dB. At 0.6 kHz, it drops to 0.75 dB. At 1.0 kHz, it drops to 0.45 dB. At 2.0 kHz, it drops to 0.35 dB. At 2.4 kHz, it rises to 0.75 dB. At 3.0 kHz, it rises to 1.7 dB. At 3.4 kHz, it rises to 1.7 dB. At 3.6 kHz, it drops to 0 dB. There are 'Note' labels in the regions [0.6, 2.0] at 0.45 dB, [2.0, 3.0] at 0.75 dB, and [3.0, 3.6] at 1.7 dB. A small circle with an 'x' is at 1.0 kHz, 0 dB. + +a) Input connection + +![Graph of Loss (dB) vs Frequency (f) in kHz for output connection. The axes and shaded regions are identical to the input connection graph. The y-axis ranges from -0.3 to 1.7 dB. The x-axis ranges from 0 to 3.6 kHz. The loss limits are: 0 to 0.2 kHz at 0 dB; 0.2 to 0.3 kHz at -0.3 dB; 0.3 to 0.4 kHz at 1.7 dB; 0.4 to 0.6 kHz at 1.0 dB; 0.6 to 1.0 kHz at 0.75 dB; 1.0 to 2.0 kHz at 0.45 dB; 2.0 to 2.4 kHz at 0.35 dB; 2.4 to 3.0 kHz at 0.75 dB; 3.0 to 3.4 kHz at 1.7 dB; 3.4 to 3.6 kHz at 1.7 dB; 3.6 kHz and above at 0 dB. 'Note' labels are present in the same regions as the input graph. A small circle with an 'x' is at 1.0 kHz, 0 dB. A small text 'T1515540-94' is at the bottom right.](177e8bc1c595b7fe3461d9919f87e044_img.jpg) + +Graph of Loss (dB) vs Frequency (f) in kHz for output connection. The axes and shaded regions are identical to the input connection graph. The y-axis ranges from -0.3 to 1.7 dB. The x-axis ranges from 0 to 3.6 kHz. The loss limits are: 0 to 0.2 kHz at 0 dB; 0.2 to 0.3 kHz at -0.3 dB; 0.3 to 0.4 kHz at 1.7 dB; 0.4 to 0.6 kHz at 1.0 dB; 0.6 to 1.0 kHz at 0.75 dB; 1.0 to 2.0 kHz at 0.45 dB; 2.0 to 2.4 kHz at 0.35 dB; 2.4 to 3.0 kHz at 0.75 dB; 3.0 to 3.4 kHz at 1.7 dB; 3.4 to 3.6 kHz at 1.7 dB; 3.6 kHz and above at 0 dB. 'Note' labels are present in the same regions as the input graph. A small circle with an 'x' is at 1.0 kHz, 0 dB. A small text 'T1515540-94' is at the bottom right. + +b) Output connection + +NOTE – In the marked frequency ranges relaxed limits are shown which apply if the maximum length of exchange cabling (see clause 2/Q.551) is used. The more stringent limits shown apply if no such cabling is present. + +Figure 5/Q.552 – Loss distortion with frequency + +#### 3.1.2 Group delay + +"Group delay" is defined in the ITU-T Q.9 (1988). + +##### 3.1.2.1 Absolute group delay + +See 3.3.1/Q.551. + +##### 3.1.2.2 Group delay distortion with frequency + +Taking as the reference the minimum group delay, in the frequency range between 500 Hz and 2800 Hz, of the input or output connection, the group delay distortion of that connection should lie within the limits shown in the template of Figure 6. Group delay distortion is measured in accordance with ITU-T O.81. + +These requirements should be met at an input level of $-10$ dBm0. + +![Figure 6/Q.552 – Group delay distortion limits with frequency. The graph shows group delay distortion in microseconds (μs) on the y-axis (0 to 900) against frequency (f) in Hz on the x-axis (0 to 2800). The limits are defined by a shaded region: from 500 Hz to 600 Hz, the limit is 900 μs; from 600 Hz to 1000 Hz, it drops to 450 μs; from 1000 Hz to 2600 Hz, it drops further to 150 μs; and from 2600 Hz to 2800 Hz, it rises back to 900 μs.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg) + +| Frequency (Hz) | Group delay distortion limit (μs) | +|----------------|-----------------------------------| +| 500 - 600 | 900 | +| 600 - 1000 | 450 | +| 1000 - 2600 | 150 | +| 2600 - 2800 | 900 | + +Figure 6/Q.552 – Group delay distortion limits with frequency. The graph shows group delay distortion in microseconds (μs) on the y-axis (0 to 900) against frequency (f) in Hz on the x-axis (0 to 2800). The limits are defined by a shaded region: from 500 Hz to 600 Hz, the limit is 900 μs; from 600 Hz to 1000 Hz, it drops to 450 μs; from 1000 Hz to 2600 Hz, it drops further to 150 μs; and from 2600 Hz to 2800 Hz, it rises back to 900 μs. + +Figure 6/Q.552 – Group delay distortion limits with frequency + +#### 3.1.3 Single frequency noise + +The level of any single frequency (in particular the sampling frequency and its multiples), measured selectively at the interface of an output connection, should not exceed $-50$ dBm0. Between 300 and 3400 Hz, the level of any single frequency measured selectively and corrected by the psophometric weighting factor (see Table 1/O.41) should not exceed $-73$ dBm0 (provisional value). + +NOTE – See 1.2.3.1/Q.551 with regard to common measurement conditions. + +#### 3.1.4 Crosstalk + +For crosstalk measurements, auxiliary signals are injected as indicated in Figures 7 and 8. These signals are: + +- the quiet code (see 1.2.3.1/Q.551); +- a low-level activating signal, e.g. a sine wave at a level in the range from $-33$ to $-40$ dBm0. Care must be taken in the choice of frequency and the filtering characteristics of the measuring apparatus in order that the activating signal does not significantly affect the accuracy of the crosstalk measurement. + +##### 3.1.4.1 Far-end and near-end crosstalk measured with analogue test signal + +A sine wave test signal at the reference frequency of 1020 Hz and at a level of 0 dBm0, applied to an analogue 2-wire interface, should not produce a level in any other half-connection exceeding $-73$ dBm0 for near-end crosstalk (NEXT) and $-70$ dBm0 for far-end crosstalk (FEXT) (see Figure 7). + +![Figure 7/Q.552 – FEXT and NEXT measurements with analogue test signal. The diagram shows three stacked half-connections. Each is divided by a vertical dashed line into 'Analogue' (left) and 'Digital' (right) sections. Each connection contains an A/D converter (top path) and a D/A converter (bottom path). In the top connection, an 'Activating signal' is applied to the analogue input; the digital output goes to a 'FEXT' meter, and the digital input receives a 'Quiet code'. In the middle connection, a 'Test signal 0 dBm0' is applied to the analogue input; the digital input receives a 'Quiet code'. In the bottom connection, the analogue output goes to a 'NEXT' meter; the digital input receives a 'Quiet code'. Curved arrows indicate crosstalk paths from the middle connection's analogue input to the top connection's digital output (FEXT) and the bottom connection's analogue output (NEXT). Reference T1515560-94 is at the bottom right.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Figure 7/Q.552 – FEXT and NEXT measurements with analogue test signal. The diagram shows three stacked half-connections. Each is divided by a vertical dashed line into 'Analogue' (left) and 'Digital' (right) sections. Each connection contains an A/D converter (top path) and a D/A converter (bottom path). In the top connection, an 'Activating signal' is applied to the analogue input; the digital output goes to a 'FEXT' meter, and the digital input receives a 'Quiet code'. In the middle connection, a 'Test signal 0 dBm0' is applied to the analogue input; the digital input receives a 'Quiet code'. In the bottom connection, the analogue output goes to a 'NEXT' meter; the digital input receives a 'Quiet code'. Curved arrows indicate crosstalk paths from the middle connection's analogue input to the top connection's digital output (FEXT) and the bottom connection's analogue output (NEXT). Reference T1515560-94 is at the bottom right. + +**Figure 7/Q.552 – FEXT and NEXT measurements with analogue test signal** + +##### 3.1.4.2 Far-end and near-end crosstalk measured with digital test signal + +A digitally simulated sine wave test signal at the reference frequency of 1020 Hz applied at a level of 0 dBm0 to an exchange test point $T_i$ , should not produce a level in any other half-connection exceeding $-70$ dBm0 for near-end crosstalk (NEXT) and $-73$ dBm0 for far-end crosstalk (FEXT) (see Figure 8). + +![Figure 8/Q.552 – FEXT and NEXT measurements with digital test signal. The diagram shows three stacked half-connections divided into 'Analogue' and 'Digital' sections. In the top connection, an 'Activating signal' is applied to the analogue input; the digital output goes to a 'NEXT' meter, and the digital input receives a 'Quiet code'. In the middle connection, the analogue input is terminated with impedance 'Z_T'; a 'Test signal 0 dBm0' is applied to the digital input. In the bottom connection, the analogue output goes to a 'FEXT' meter; the digital input receives a 'Quiet code'. Curved arrows indicate crosstalk paths from the middle connection's digital input to the top connection's digital output (NEXT) and the bottom connection's analogue output (FEXT). Reference T1515570-94 is at the bottom right.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +Figure 8/Q.552 – FEXT and NEXT measurements with digital test signal. The diagram shows three stacked half-connections divided into 'Analogue' and 'Digital' sections. In the top connection, an 'Activating signal' is applied to the analogue input; the digital output goes to a 'NEXT' meter, and the digital input receives a 'Quiet code'. In the middle connection, the analogue input is terminated with impedance 'Z\_T'; a 'Test signal 0 dBm0' is applied to the digital input. In the bottom connection, the analogue output goes to a 'FEXT' meter; the digital input receives a 'Quiet code'. Curved arrows indicate crosstalk paths from the middle connection's digital input to the top connection's digital output (NEXT) and the bottom connection's analogue output (FEXT). Reference T1515570-94 is at the bottom right. + +**Figure 8/Q.552 – FEXT and NEXT measurements with digital test signal** + +#### **3.1.5 Total distortion including quantizing distortion** + +With a sine wave test signal at the reference frequency of 1020 Hz (see ITU-T O.132) applied to the 2-wire interface of an input connection, or with a digitally simulated sine wave signal of the same characteristic applied to the exchange test point $T_i$ of an output connection, the signal-to-total-distortion ratio, measured at the corresponding outputs of the half-connection with a proper noise weighting (see Table 1/O.41) should lie above the limits given in 3.2.3, Figures 12 and 13 for interface $C_2$ and in 3.3.3, Figure 14 for interface $Z$ . + +NOTE – The sinusoidal test signal is chosen to obtain results independent of the spectral content of the exchange noise. + +#### **3.1.6 Discrimination against out-of-band signals applied to the input interface** + +(Only applicable to input connections.) + +##### **3.1.6.1 Input signals above 4.6 kHz** + +With a sine-wave signal in the range from 4.6 kHz to 72 kHz applied to the 2-wire interface of an input connection at a level of $-25$ dBm0, the level of any image frequency produced in the time slot corresponding to the input connection should be at least 25 dB below the level of the test signal. This value may need to be more stringent to meet the overall requirement. + +##### **3.1.6.2 Overall requirement** + +Under the most adverse conditions encountered in a national network, the half-connection should not contribute more than 100 pW0p of additional noise in the band 10 Hz to 4 kHz at the output of the input connection, as a result of the presence of out-of-band signals at the 2-wire interface of the input connection. + +#### **3.1.7 Spurious out-of-band signals received at the output interface** + +(Only applicable to an output connection.) + +##### **3.1.7.1 Level of individual components** + +With a digitally simulated sine wave signal in the frequency range 300 to 3400 Hz and at a level of 0 dBm0 applied to the exchange test point $T_i$ of a half-connection, the level of spurious out-of-band image signals measured selectively at the 2-wire interface of the output connection should be lower than $-25$ dBm0. This value may need to be more stringent to meet the overall requirement. + +##### **3.1.7.2 Overall requirement** + +Spurious out-of-band signals should not give rise to unacceptable interference in equipment connected to the digital exchange. In particular, the intelligible and unintelligible crosstalk in a connected FDM channel should not exceed a level of $-65$ dBm0 as a consequence of spurious out-of-band signals at the half-connections. + +#### **3.1.8 Echo and stability** + +Terminal Balance Return Loss (TBRL) as defined in 3.1.8.1 is introduced in order to characterize the exchange performance required to comply with the network performance objective of ITU-T G.122 with respect to echo and stability. The TBRL of an interface is measured in the talking state as in an established connection through a digital exchange. + +The parameter "Stability Loss", as defined in ITU-T G.122, applies to the worst terminating conditions encountered at a 2-wire interface in normal operation. + +##### 3.1.8.1 Terminal Balance Return Loss (TBRL) + +The term TBRL is used to characterize an impedance balancing property of the 2-wire analogue interface. + +The expression for TBRL is: + +$$TBRL = 20 \log \frac{Z_o + Z_b}{2Z_o} \times \frac{Z_t + Z_o}{Z_t - Z_b}$$ + +where: + +$Z_o$ is the exchange impedance of a 2-wire equipment port; + +$Z_b$ is the impedance of the balance network; + +$Z_t$ is the impedance of the balance test network presented at a 2-wire interface + +Some network operators have found that it is advantageous to choose $Z_o = Z_b$ in order to optimize TBRL. In this case the expression is reduced to: + +$$TBRL = 20 \log \left| \frac{Z_t + Z_b}{Z_t + Z_o} \right|$$ + +and the balance test network will be identical to the test network for the exchange impedance. + +The balance test network should be representative of the impedance conditions to be expected from a population of terminated lines connected to 2-wire interfaces, as determined by the national transmission planning. + +The TBRL is related to the loss $a_{io}$ between the exchange test point $T_i$ and $T_o$ of a half-connection as follows: + +$$TBRL = a_{io} - (a_o + a_i)$$ + +where $a_o$ and $a_i$ are the losses between the exchange test point $T_i$ and the 2-wire interface and between the 2-wire interface and the exchange test point $T_o$ , respectively. + +TBRL can thus be determined by measurement of $a_{io}$ provided the sum $(a_o + a_i)$ is known. This can be derived in several ways: + +- a) $a_o$ and $a_i$ are assigned their nominal values $NL_o$ and $NL_i$ as defined in 3.2.1 and 3.3.1. Then: + +$$TBRL = a_{io} - (NL_o + NL_i)$$ + +- b) $a_o$ and $a_i$ are measured with the load matched to the exchange impedance as actual transmission loss $AL_o$ and $AL_i$ (see 3.1.1.2). Then: + +$$TBRL = a_{io} - (AL_o + AL_i)$$ + +- c) the loss $a_{io}$ is measured with the 2-wire equipment port open- and short-circuited, giving losses $a'_{io}$ and $a''_{io}$ respectively. + +$$TBRL = a_{io} - \frac{a'_{io} + a''_{io}}{2}$$ + +Method b) provides the most accurate results. + +Using the arrangement of Figure 9 and sinusoidal test signals, the measured TBRL should exceed the limits shown in Figure 10. + +![Figure 9/Q.552 – Arrangement for measuring the loss a_io](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram shows a bridge circuit arrangement. On the left, there are two 'Exchange test points' labeled $T_i$ and $T_o$ . These connect through capacitors to a central diamond-shaped bridge. The top capacitor is labeled $a_o$ and the bottom one $a_i$ . Inside the bridge area, there is a 'Balance network' labeled $Z_b$ on the left and a 'Balance test network' labeled $Z_t$ on the right. The central component is labeled 'Item under test'. Reference number T1515580-94 is in the bottom right. + +Figure 9/Q.552 – Arrangement for measuring the loss a\_io + +**Figure 9/Q.552 – Arrangement for measuring the loss $a_{io}$** + +![Figure 10/Q.552 – Limits for TBRL](96a7eac66ef72bb016c280278506ac63_img.jpg) + +A graph of TBRL (dB) versus Frequency (f) in Hz. The limits are defined by a shaded area with the following coordinates: + +| Frequency (Hz) | TBRL Limit (dB) | +|----------------|-----------------| +| 300 | 16 | +| 500 | 20 | +| 2500 | 20 | +| 3400 | 16 | + +Reference number T1515590-94 is in the bottom right. + +Figure 10/Q.552 – Limits for TBRL + +**Figure 10/Q.552 – Limits for TBRL** + +![Figure 11/Q.552 – Examples of test networks](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +The diagram shows six circuit diagrams for different network operators. Each circuit consists of resistors and capacitors in various series/parallel combinations. Below the circuits, the following impedance values are provided: + +| USA | Austria
Fed. Rep. of Germany | NTT | British Telecom
New Zealand | Italy | ETSI | +|------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------------------------| +| 800 $\Omega$ | 820 $\Omega$ | 830 $\Omega$ | 620 $\Omega$ | 1100 $\Omega$ | 750 $\Omega$ | +| (Circuit: 100 $\Omega$ in series with parallel 800 $\Omega$ and 50 nF) | (Circuit: 220 $\Omega$ in series with parallel 820 $\Omega$ and 115 nF) | (Circuit: 150 $\Omega$ in series with parallel 830 $\Omega$ and 72 nF) | (Circuit: 370 $\Omega$ in series with parallel 620 $\Omega$ and 310 nF) | (Circuit: Parallel 1100 $\Omega$ and 33 nF) | (Circuit: 270 $\Omega$ in series with parallel 750 $\Omega$ and 150 nF) | +| Impedance at 1000 Hz: | | | | | | +| $770 \Omega \angle -14.0^\circ$ | $902 \Omega \angle -23.5^\circ$ | $919 \Omega \angle -17.3^\circ$ | $693 \Omega \angle -26.1^\circ$ | $1072 \Omega \angle -12.8^\circ$ | $847 \Omega \angle -24.7^\circ$ | + +Reference number T1515600-94 is in the bottom right. + +Figure 11/Q.552 – Examples of test networks + +**Figure 11/Q.552 – Examples of test networks to be used by some network operators +(applicable to unloaded subscriber lines)** + +Figure 11 gives examples of balance test networks adopted by some network operators for unloaded subscriber lines. These examples may provide guidance for other network operators in order to minimize the diversity of types of test networks; see also Appendix I. + +NOTE – Some network operators may need to adopt several balance test networks to cover the various types of unloaded and loaded cables. + +##### 3.1.8.2 Stability loss + +The stability loss should be measured between the exchange test points $T_i$ and $T_o$ of a half-connection (see Figure 9) by terminating the 2-wire interface with stability test networks representing the "worst terminating condition encountered in normal operation". Some network operators may find that open- and short-circuit terminations are sufficiently representative of worst-case conditions. Other network operators may need to specify, for example, an inductive termination to represent the worst-case condition. + +Where the digital exchange is connected to the international chain using only 4-wire switching and transmission, the half-connection of the digital exchange may provide the total stability loss of the national extension. The value of Stability Loss (SL) that is required for a 2-wire interface is a matter of national control provided that the requirements of ITU-T G.122 are met. A SL value of at least 6 dB at all frequencies between 200 Hz and 3600 Hz will ensure that the G.122 requirements are met. However, SL values of between 6 dB and 0 dB will formally comply with the present requirements of G.122. One network operator has found that a value of 3 dB is satisfactory in its environment. + +NOTE – It is suggested that the half-connection of a digital PABX, or of a digital remote unit, when connected to the digital local exchange by a digital transmission system, should also meet the requirements of 3.1.8. + +### 3.2 Characteristics of interface $C_2$ + +#### 3.2.1 Nominal value of transmission loss + +According to the relative levels defined in 2.1.3.1, the nominal transmission losses of input or output connections $NL_i$ and $NL_o$ of a half-connection with $C_2$ interfaces are in the following ranges: + $C_{21}$ interfaces + +$NL_i = 0$ to 2.0 dB for all types of connections + +$NL_o = 5.0$ to 8.0 dB for international connections +0 to 8.0 dB for local or national connections + +$C_{22}$ interfaces + +$$\left. \begin{array}{l} NL_i = -7.0 \text{ to } 3.0 \text{ dB} \\ NL_o = -1.0 \text{ to } 8.0 \text{ dB} \end{array} \right\} \text{ for all types of connections}$$ + +It has been recognized that it is not necessary for a particular design of equipment to be capable of operating over the entire range of nominal transmission losses. + +If a loss compensation is applied the nominal loss $NL_i$ and $NL_o$ should be corrected by the value of $x$ dB chosen in connection with 2.1.3.1.2 or 2.2.3.3. + +#### 3.2.2 Noise + +##### 3.2.2.1 Weighted noise + +For the calculation of noise, worst-case conditions at the $C_2$ interface are assumed. The band limiting effect of the encoder on the noise has not been taken into account. + +###### 3.2.2.1.1 Output connection + +Two components of noise must be considered. One of these is the noise arising from the quiet decoder, the other comes from analogue sources, such as signalling equipment and the analogue circuit for impedance and level adaptation. The first component is limited to $-70$ dBm0p or $-75$ dBmp respectively in accordance with Table 7/G.712; the other component is limited to + +-67 dBm0p (200 pW0p) in accordance with Annex A/G.120, i.e. $-(67 + 3)$ dBm0p = -70 dBm0p for one 2-wire analogue interface. + +This results in the maximum values for the overall weighted noise in the talking state at the $C_2$ interface of a digital exchange: + +- equipment with signalling on separate wires: + - 70 dBm0p for output relative levels $L_o \geq -5$ dBr; + - 75 dBmp for output relative levels $L_o < -5$ dBr; +- equipment with signalling on the speech wires: + - 67 dBm0p for output relative levels $L_o \geq -5$ dBr; + +i.e. -72.5 dBmp and -73.2 dBmp respectively for output relative levels $L_o = -6$ dBr and $-8$ dBr. + +Values for other output relative levels cited in 2.1.3.1 can be calculated by using the formula given in 3.4.1/Q.551. + +###### 3.2.2.1.2 Input connection + +Two components of noise must be considered. One of these arises from the encoding process, the other from analogue sources, such as signalling equipment and the analogue circuit for impedance and level adaptation. The first component is limited to -67 dBm0p as idle channel noise in accordance with Table 7/G.712; the other component is limited to -67 dBm0p (200 pW0p) in accordance with Annex A/G.120, i.e. $-(67 + 3)$ dBm0p = -70 dBm0p for one 2-wire analogue interface. + +The maximum values for the overall weighted noise in the talking state at the exchange test point $T_o$ of a digital exchange should be not more than: + +- 67.0 dBm0p for equipment with signalling on separate wires; +- 65.2 dBm0p for equipment with signalling on the speech wires. + +##### 3.2.2.2 Unweighted noise + +This noise will be more dependent on the noise from the power supply and on the rejection ratio. + +#### 3.2.3 Values of total distortion + +The total distortion including quantizing distortion of a half-connection with a $C_2$ interface is measured in accordance with 3.1.5. + +The signal-to-total distortion ratio for a half-connection at interface $C_2$ should lie above the limits shown in Figure 12 for equipment with signalling on separate wires, and in Figure 13 for equipment with signalling on the speech wires both measured in the talking state. + +![Figure 12/Q.552: Limits for signal-to-total distortion ratio as a function of input level; input or output connection with signalling on separate wires. The graph shows the signal-to-total distortion ratio in dB on the y-axis (0 to 35) against input level in dBm0 on the x-axis (-45 to 0). The ratio is 24 dB for input levels from -45 to -40 dBm0, then increases linearly to 35 dB at -30 dBm0, and remains constant at 35 dB for input levels from -30 to 0 dBm0. A shaded region indicates the tolerance limits around the main curve. Reference T1515610-94 is shown.](0f79a59f3766fc341ff688a23692c1d9_img.jpg) + +Figure 12/Q.552: Limits for signal-to-total distortion ratio as a function of input level; input or output connection with signalling on separate wires. The graph shows the signal-to-total distortion ratio in dB on the y-axis (0 to 35) against input level in dBm0 on the x-axis (-45 to 0). The ratio is 24 dB for input levels from -45 to -40 dBm0, then increases linearly to 35 dB at -30 dBm0, and remains constant at 35 dB for input levels from -30 to 0 dBm0. A shaded region indicates the tolerance limits around the main curve. Reference T1515610-94 is shown. + +**Figure 12/Q.552 – Limits for signal-to-total distortion ratio as a function of input level; input or output connection with signalling on separate wires** + +![Figure 13/Q.552: Limits for signal-to-total distortion ratio as a function of input level; input or output connection with signalling on the speech wires. The graph shows the signal-to-total distortion ratio in dB on the y-axis (0 to 35.0) against input level in dBm0 on the x-axis (-45 to 0). The ratio is 21.5 dB for input levels from -45 to -40 dBm0, then increases linearly to 33.8 dB at -30 dBm0, and remains constant at 33.8 dB for input levels from -30 to 0 dBm0. A shaded region indicates the tolerance limits around the main curve. Reference T1515620-94 is shown.](9b5411fa2d169b66f6185fbf67b49766_img.jpg) + +Figure 13/Q.552: Limits for signal-to-total distortion ratio as a function of input level; input or output connection with signalling on the speech wires. The graph shows the signal-to-total distortion ratio in dB on the y-axis (0 to 35.0) against input level in dBm0 on the x-axis (-45 to 0). The ratio is 21.5 dB for input levels from -45 to -40 dBm0, then increases linearly to 33.8 dB at -30 dBm0, and remains constant at 33.8 dB for input levels from -30 to 0 dBm0. A shaded region indicates the tolerance limits around the main curve. Reference T1515620-94 is shown. + +**Figure 13/Q.552 – Limits for signal-to-total distortion ratio as a function of input level; input or output connection with signalling on the speech wires** + +The values of Figure 13 include the limits for the encoding process given in Figure 12/G.712 and the allowance for the noise contributed via signalling circuits from the exchange power supply and other analogue sources (e.g. analogue coupling), which is limited to $-67$ dBm0p (200 pW0p) in accordance with Annex A/G.120, i.e. $-(67 + 3)$ dBm0p $= -70$ dBm0p for one $C_2$ analogue interface. + +### 3.3 Characteristics of interface Z + +#### 3.3.1 Nominal value of transmission loss + +According to the relative levels defined in 2.2.3.1, the nominal transmission losses of input or output connections $NL_i$ and $NL_o$ of a half-connection with Z interfaces are in the following ranges: + +$NL_i = 0$ to $2.0$ dB for all types of connections + +$NL_o = 5.0$ to $8.0$ dB for international connections + +$0$ to $8.0$ dB for internal, local or national connections. + +If a compensation for the loss of short or long subscriber lines is applied, the nominal loss $NL_i$ and $NL_o$ should be corrected by the value of $x$ dB chosen in connection with 2.2.3.3. + +#### 3.3.2 Noise + +##### 3.3.2.1 Weighted noise + +For the calculation of noise, worst-case conditions at the Z interface are assumed. The band limiting effect of the encoder on the noise has not been taken into account. + +###### 3.3.2.1.1 Output connection + +Two components of noise must be considered. One of these, namely noise arising from the decoding process, is dependent upon the output relative level. The other, for example power supply noise from the feeding bridge and circuit noise, is independent of the output relative level. The first component is limited to $-70$ dBm0p in accordance with Table 7/G.712; the other component is limited to $200$ pWp ( $-67$ dBmp) in accordance with Annex A/G.120. Possible sources of this latter component are the main DC power supply, auxiliary DC-DC converters and the circuit for 4-wire to 2-wire conversion with impedance and level adaptation. + +For an output relative level of $L_o = -7.0$ dBr, the resulting total noise level for the output connection is: + +$$L_{TNo} \leq -66.6 \text{ dBmp}$$ + +Values for other output relative levels cited in 2.2.3.1.2 can be calculated by using the formula given in 3.4.1/Q.551. + +###### 3.3.2.1.2 Input connection + +Two components of noise must be considered. One of these, namely noise arising from the encoding process is independent to the input relative level. The other, for example power supply noise from the feeding bridge and the circuit noise, is dependent upon the input relative level. The first component is limited to $-67$ dBm0p as idle channel noise in accordance with Table 7/G.712; the other component is limited to $200$ pWp ( $-67$ dBmp) in accordance with Annex A/G.120. For an input relative level of $L_i = 0$ dBr the resulting total noise level for the input connection is: $L_{TNi} = -64.0$ dBm0p. + +The total psophometric power allowed at the exchange test point $T_o$ with an input relative level of $L_i = 0$ dBr is: + +$$P_{TNi} = P_{AN} \cdot 10^{\frac{-L_i}{10}} + 10^{\frac{90+L_{TNi}}{10}} \text{ pWp}$$ + +and the total noise level is: + +$$L_{TNi} = -64.0 \text{ dBm0p}$$ + +Values for other input relative levels cited in 2.2.3.1.1 can be calculated by using the formula given in 3.4.1/Q.551. + +##### 3.3.2.2 Unweighted noise + +This noise will be more dependent on the noise from the power supply and on the rejection ratio. + +#### 3.3.3 Values of total distortion + +The total distortion including quantizing distortion on half-connections with Z interfaces is measured in accordance with 3.1.5. + +Resulting templates for the signal-to-total distortion ratio of input and output connections in a local exchange are shown in Figure 14 a) and 14 b) as an example where $L_i = 0$ dBr and $L_o = -7$ dBr respectively. + +Values for other relative levels cited in 2.2.3.1 can be calculated by using the formula given in 3.4.2/Q.551. + +The values of Figure 14 include the limits for the coding process given in Figure 12/G.712 and the allowance for the noise contributed via signalling circuits from the exchange power supply and other analogue sources, which is limited to $-67$ dBmp (200 pWp) for a Z interface (with feeding) by Annex A/G.120. + +![Figure 14/Q.552 – Limits for signal-to-total distortion ratio as a function of input level including analogue noise. The figure contains two graphs, (a) and (b). Both graphs plot 'Signal-to-total distortion ratio' in dB on the y-axis against 'Input level' in dBm0 on the x-axis. The x-axis ranges from -45 to 0 dBm0 with major ticks every 10 dB. The y-axis ranges from 0 to 35.0 dB with major ticks at 0, 19.9, 24.9, 32.9, and 35.0 dB. Both graphs show a shaded region representing the allowed limits. In graph (a) for input connection L_i = 0 dBr, the lower limit starts at 19.9 dB for input levels below -40 dBm0, rises to 32.9 dB at -30 dBm0, and reaches 35.0 dB at -20 dBm0. In graph (b) for output connection L_o = -7 dBr, the lower limit starts at 14.5 dB for input levels below -40 dBm0, rises to 28.8 dB at -30 dBm0, and reaches 33.8 dB at -20 dBm0. Both graphs have a horizontal upper limit line at 35.0 dB.](5500ab73cf84ccc0055eecf28889b4db_img.jpg) + +| Input level (dBm0) | Signal-to-total distortion ratio (dB) | | +|--------------------|----------------------------------------------|------------------------------------------------| +| | (a) Input connection: L i = 0 dBr | (b) Output connection: L o = −7 dBr | +| −45 to −40 | 19.9 | 14.5 | +| −40 to −30 | Linear increase to 32.9 | Linear increase to 28.8 | +| −30 to −20 | Linear increase to 35.0 | Linear increase to 33.8 | +| −20 to 0 | 35.0 | 33.8 (up to −10), then 35.0 | + +Figure 14/Q.552 – Limits for signal-to-total distortion ratio as a function of input level including analogue noise. The figure contains two graphs, (a) and (b). Both graphs plot 'Signal-to-total distortion ratio' in dB on the y-axis against 'Input level' in dBm0 on the x-axis. The x-axis ranges from -45 to 0 dBm0 with major ticks every 10 dB. The y-axis ranges from 0 to 35.0 dB with major ticks at 0, 19.9, 24.9, 32.9, and 35.0 dB. Both graphs show a shaded region representing the allowed limits. In graph (a) for input connection L\_i = 0 dBr, the lower limit starts at 19.9 dB for input levels below -40 dBm0, rises to 32.9 dB at -30 dBm0, and reaches 35.0 dB at -20 dBm0. In graph (b) for output connection L\_o = -7 dBr, the lower limit starts at 14.5 dB for input levels below -40 dBm0, rises to 28.8 dB at -30 dBm0, and reaches 33.8 dB at -20 dBm0. Both graphs have a horizontal upper limit line at 35.0 dB. + +**Figure 14/Q.552 – Limits for signal-to-total distortion ratio as a function of +input level including analogue noise** + +# Appendix I + +## Impedance strategy in 2-wire networks + +## I.1 Introduction + +The aim of this appendix is to describe in more detail the methodologies which can be applied to determine termination impedances and balance networks. While termination impedance may affect sidetone on some telephones, echo which is controlled by the balance network is of much greater importance. Therefore, balance network selection is very critical no matter what termination impedance is selected. Additional information is also available in [1]. + +In order to provide a network with good echo and sidetone performance, it is necessary to employ a certain impedance strategy in the 2-wire analogue parts of the network where the signals are transmitted simultaneously in both directions on the same pair of wires. It is of course necessary to separate the signals – transmit and receive – from each other at the ends of a 2-wire section and this is done by means of so-called hybrids which have in principle four ports (see Figure I.1): + +- the 2-wire port (2); +- the 4-wire transmit port (T); +- the 4-wire receive port (R); +- the balance network port (B). + +![Diagram of a general hybrid. On the left, Port (2) is shown with an input impedance Z_T indicated by a right-pointing arrow and a balance impedance Z_2 indicated by a left-pointing arrow. On the right, there are three ports: Port (T) at the top, Port (B) in the middle, and Port (R) at the bottom. A horizontal line connects Port (2) to Port (B).](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Diagram of a general hybrid. On the left, Port (2) is shown with an input impedance Z\_T indicated by a right-pointing arrow and a balance impedance Z\_2 indicated by a left-pointing arrow. On the right, there are three ports: Port (T) at the top, Port (B) in the middle, and Port (R) at the bottom. A horizontal line connects Port (2) to Port (B). + +T1527050-97 + +**Figure I.1/Q.552 – General hybrid** + +NOTE 1 – The balance port may not always be physically accessible in the hybrid, i.e. it may exist only notionally. + +The transmission properties of the hybrid are specified by the following parameters: + +- 2-wire impedance connected to the 2-wire port of the hybrid $Z_2$ +- input impedance at the port (2) of the hybrid $Z_T$ +- balance impedance at the port (B) $Z_B$ +- matched loss between ports (R) and (2) $L_R$ +- matched loss between ports (2) and (T) $L_T$ +- balance return loss $L_{br}$ + +NOTE 2 – "Matched loss" implies that the loss is to be measured for the special case when the impedance $Z_2$ is made equal to $Z_T$ . + +The separation between transmit and receive signals by means of a hybrid depends mainly on the impedance matching at the 2-wire port of the hybrid between: + +- the impedance $Z_2$ connected to the 2-wire port of the hybrid; and +- the so-called balance impedance $Z_B$ of the hybrid. + +The loss $L_{TR}$ between ports (T) and (R) is given by the relation: + +$$L_{TR} = L_T + L_{br} + L_R \quad (I-1)$$ + +where: + +$$L_{br} = 20 \cdot \log \left| \frac{Z_T + Z_B}{2Z_T} \cdot \frac{Z_2 + Z_T}{Z_2 - Z_B} \right| \text{dB} \quad (I-2)$$ + +NOTE 3 – $L_{br}$ is in general a function of frequency. Equations (I-1) and (I-2) apply for all possible designs of hybrids. + +In case of impedance $Z_T$ being equal to $Z_B$ , $L_{br}$ results in: + +$$L_{br} = 20 \cdot \log \left| \frac{Z_2 + Z_B}{Z_2 - Z_B} \right| \quad (I-3)$$ + +NOTE 4 – This equation is similar to the "return loss"-equation used for the comparison of two impedances. + +A connection in a digital PSTN in principle consists of two analogue telephone sets which include the microphone and the earphone, the 2-wire analogue subscriber lines and the 4-wire digital connection. The transitions from 2-wire to 4-wire and vice versa are made by hybrids which are situated in the telephone set and in the exchange line circuit (see Figure I.2). + +![Schematic diagram of a telephone connection via 2-wire analogue subscriber lines. The diagram shows two telephone sets connected through a 4-wire national/international connection via 2-wire analogue subscriber lines. Impedances Z_B_set, Z_T_set, Z_T_ex, and Z_2_ex are indicated at various points. The bottom part of the diagram is a table defining the segments.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +| | | | | | | | +|--------------------------------|---------------------------|---------------------------|------------------------------------------------|---------------------------|---------------------------|--------------------------------| +| telephone set
4-wire/2-wire | subscriber line
2-wire | exchange
2-wire/4-wire | 4-wire
national/international
connection | exchange
4-wire/2-wire | subscriber line
2-wire | telephone set
2-wire/4-wire | +|--------------------------------|---------------------------|---------------------------|------------------------------------------------|---------------------------|---------------------------|--------------------------------| + +Schematic diagram of a telephone connection via 2-wire analogue subscriber lines. The diagram shows two telephone sets connected through a 4-wire national/international connection via 2-wire analogue subscriber lines. Impedances Z\_B\_set, Z\_T\_set, Z\_T\_ex, and Z\_2\_ex are indicated at various points. The bottom part of the diagram is a table defining the segments. + +T1527060-97 + +Figure I.2/Q.552 – Telephone connection via 2-wire analogue subscriber lines + +At the telephone set, port (T) corresponds to the microphone, port (R) to the earphone receiver. The impedance $Z_{2_{set}}$ is the cable input impedance of the subscriber line terminated by the 2-wire input impedance $Z_{T_{ex}}$ of the digital exchange (nominal input impedance for open 4-wire loop). The loss $L_{TR}$ corresponds to the sidetone loss. + +At the exchange line circuit, ports (T) and (R) correspond to the digital 4-wire ports. The impedance $Z_{2_{ex}}$ is the cable input impedance of the subscriber line terminated by the 2-wire input impedance $Z_{T_{set}}$ of the telephone set. The loss $L_{TR}$ corresponds to the echo loss at the listener's exchange. + +It is immediately apparent that the impedance $Z_2$ (i.e. $Z_{2_{ex}}$ or $Z_{2_{set}}$ respectively) must not vary too much from the balance impedance $Z_B$ (i.e. $Z_{B_{ex}}$ or $Z_{B_{set}}$ respectively) if the balance return loss is to be kept high. To achieve this with different cable types of varying lengths the terminating impedances have to be chosen with care. This will be discussed in I.3 and I.4. An example will be given in I.8. + +## I.2 General equations for unloaded cables + +For the sake of completeness, the impedance equations for cables will be presented. + +For uniformly distributed lines the transmission characteristics are calculated from the electrical primary cable constants per unit length: + +$$R' \text{ in } \frac{\Omega}{\text{km}}; L' \text{ in } \frac{H}{\text{km}}; G' \text{ in } \frac{S}{\text{km}}; C' \text{ in } \frac{F}{\text{km}}; f \text{ in Hz}; \omega = 2\pi f$$ + +NOTE – $L'$ and $G'$ can be disregarded for unloaded cables in the range of voiceband frequencies. + +The **image (characteristics) impedance** of a cable is: + +$$Z_C = \sqrt{\frac{R' + j\omega L'}{G' + j\omega C'}} \quad (\text{I-4})$$ + +The **propagation constant** of a cable is: + +$$\gamma = \alpha + j\beta = \sqrt{(R' + j\omega L')(G' + j\omega C')} \quad (\text{I-5})$$ + +and expresses the attenuation $\alpha$ in nepers per unit length and the phase shift $\beta$ in radians per unit length. + +If the cable is terminated by an impedance $Z_T = Z_C$ the cable input impedance $Z_2$ will also be equal to $Z_C$ and therefore independent of the cable length. If the cable is terminated by an impedance $Z_T \neq Z_C$ its **input impedance** $Z_2$ is dependent on the loop length ( $l$ ) and will be: + +$$Z_2 = \frac{Z_T + Z_C \cdot \tan h(\gamma \cdot l)}{1 + \frac{Z_T}{Z_C} \cdot \tan h(\gamma \cdot l)} \quad (\text{I-6})$$ + +Two impedances at port (2) can be compared by the **reflection coefficient**: + +$$r = \frac{Z_2 - Z_T}{Z_2 + Z_T} \quad (\text{I-7})$$ + +## I.3 General impedance considerations of a hybrid + +The separation characteristic of a hybrid is defined by the impedances $Z_2$ , $Z_T$ and $Z_B$ (see equation I-2). The impedance $Z_2$ is connected to the hybrid and is given by the subscriber line network while the impedances $Z_T$ and $Z_B$ are part of the hybrid itself and are to be chosen carefully. + +### I.3.1 Cable input impedance $Z_2$ and the hybrid input impedance $Z_T$ + +If the cable is not terminated by its characteristic impedance $Z_C$ , the cable input impedance $Z_2$ depends on the cable parameters and the input impedance $Z_T$ of the cable termination equipment (telephone set or exchange line circuit) (see equation I-6). + +At the port (2) of the telephone set, the input impedance $Z_{2_{set}}$ is determined by the subscriber cable parameters and $Z_{T_{ex}}$ of the exchange. + +At the port (2) of the exchange line circuit, the input impedance $Z_{2_{ex}}$ is determined by the subscriber cable and $Z_{T_{set}}$ of the telephone set (normally in a network different types of telephone sets with different input impedances exist). + +The better the termination impedance $Z_T$ approximate to the characteristic impedance $Z_C$ of the cable, the less the cable input impedance $Z_2$ vary with the length. With regard to the balance impedance (see next clause) and due to the capacitive complex property of the characteristic impedance in the voice frequency range, it is advantageous to define also a capacitive complex impedance $Z_T$ for the cable termination, i.e. $Z_{T_{set}}$ for the telephone set or $Z_{T_{ex}}$ respectively for the exchange line circuit. (However, in practice it is not always possible to choose an "optimum" terminating impedance as the only alternative because one must also consider what already exists in the real network. See the discussion in I.7.) + +### I.3.2 Balance impedance $Z_B$ + +The fixed balance network $Z_{B_{ex}}$ in the exchange line circuit has direct consequences for the talker echo performance at the listener's exchange while $Z_{B_{set}}$ effects the sidetone for the telephone set. For practical reasons it is desirable to have only one balance impedance $Z_B$ to make a balancing of the whole range of impedances $Z_2$ in a network. (However, in those circumstances, when the impedance range seen by the exchange is very wide, one may need to choose several options for balance impedance.) + +In order to choose a suitable balance impedance $Z_B$ , it is necessary to consider the network with regard to: + +- the types of cables and their cumulative length distribution; +- the range of termination impedances and their tolerances; +- the required balance return loss with regard to the transmission plan and the permissible echo limits. + +## I.4 Echo considerations + +### I.4.1 Talker echo loudness rating TELR + +The talker echo loudness rating TELR is calculated according to equation I-8 (see ITU-T G.111). + +$$TELR = SLR + RLR + L_e \quad (I-8)$$ + +where SLR, RLR are the send and receive loudness ratings from the talker's side, referred to the 0 dBr digital transmit and receive ports of the exchange, and the echo loss $L_e$ is the weighted average of $L_{TR}$ (see equation I-1). + +NOTE – In ITU-T G.122, the weighting equation for TELR is specified for a linear frequency scale. + +### I.4.2 Sidetone masking rating STMR and listener sidetone rating LSTR + +The sidetone masking rating STMR can be computed for analogue terminals in a similar way, according to Annex A/G.111: + +$$STMR = SLR(set) + RLR(set) - 1 + L_{st} \quad (I-9)$$ + +where SLR (set) and RLR (set) refer to the telephone set itself and $L_{st}$ is the weighted average of $L_{TR}$ (see equation I-1). + +The listener sidetone rating LSTR is: + +$$LSTR = STMR + D \quad (I-10)$$ + +where $D$ is the difference in sensitivity between direct and diffuse sound of the handset microphone. + +However, $L_e$ and $L_{st}$ can also be computed – according to ITU-T G.111 – as averages over a logarithmic frequency scale, preferably using a third-octave division, giving 14 points between 200 and 4000 Hz. The general equation is: + +$$L = -\frac{10}{m} \cdot \log \left\{ \sum_{i=1}^{14} K_i 10^{-0.1 \cdot m \cdot L_{TR}} \right\} \quad (I-11)$$ + +In Table I.1 the weighting coefficients $K_i$ for sidetone (from Table A.1/G.111) and $K_i$ for echo (calculated with equation A.4-8/G.111) are summarized; for calculation of $L_e$ (echo loss), $m = 1$ ; for calculation of $L_{st}$ (sidetone), $m = 0.2$ . + +**Table I.1/Q.552 – Weighting coefficients $K_i$ +for talker echo ( $L_e$ ) and sidetone ( $L_{st}$ )** + +| i | $f_i$ [Hz] | $K_i(L_e)$ | $K_i(L_{st})$ | +|----|------------|------------|---------------| +| 1 | 200 | 0 | 0 | +| 2 | 250 | 0 | 0.01 | +| 3 | 315 | 0.05 | 0.02 | +| 4 | 400 | 0.1 | 0.03 | +| 5 | 500 | 0.1 | 0.04 | +| 6 | 630 | 0.1 | 0.05 | +| 7 | 800 | 0.1 | 0.08 | +| 8 | 1000 | 0.1 | 0.12 | +| 9 | 1250 | 0.1 | 0.12 | +| 10 | 1600 | 0.1 | 0.12 | +| 11 | 2000 | 0.1 | 0.12 | +| 12 | 2500 | 0.1 | 0.12 | +| 13 | 3150 | 0.05 | 0.12 | +| 14 | 4000 | 0 | 0.05 | + +Between echo and sidetone calculation there is a difference in the weighting. The talker echo weighting is flat, while the sidetone weighting emphasizes the frequencies above 800 Hz. This implies that for the talker echo, an impedance matching is needed over the total speech band, while for the sidetone only the range above 800 Hz is of importance. + +## I.5 Applications + +A transmission plan for a telephone network must include, among a multitude of items, considerations for the loop plant design and the parameters of the telephone sets. As these factors differ among network operators, it is not surprising that different exchanges and balance impedances have been chosen as evidenced from Table 1 and Figure 11. + +In this context, it is useful to consider the limit for satisfactory sidetone and talker echo performance. + +For sidetone, the limiting parameter is the listener side tone rating LSTR, which should be higher than 13 dB. This guarantees that the listener will not be disturbed by room noise picked up via the listener sidetone path even under rather noisy conditions. + +For talker echo, the requirements on the talker echo loudness rating TELR depends on the particular network rule for applying echo cancellers, i.e. above which mean one-way transmission time $T$ [ms] they must be deployed. ITU-T G.131 gives TELR as function of $T$ [ms] for acceptable echo performance without echo control. + +## I.6 Analysis of loop impedance variation by means of a special impedance diagram + +Knowledge about the actual loop impedance conditions in a network can be obtained in several ways, for instance by field measurements. Another method is to collect the statistical data for the terminals and for the cables, types and lengths and then compute the impedances. + +One can proceed in several ways to analyse the impedance data and arrive to suitable impedance matchings. A fairly simple method for a quick analysis is to plot the impedances in a special type of diagram which is so designed that a certain distance between two impedance points always corresponds to the same return loss. This is achieved by making the abscissa and the ordinate + +$$X = k \cdot \ln |Z| \qquad Y = k \cdot \arg \{Z\} \text{ radians; } k \text{ is a constant}$$ + +Figure I.3 shows the principle. The scale at the bottom of the figure can be used to estimate return losses. (For the sake of clarity, the impedance angles are graduated in degrees, not in radians.) Thus, in a plot containing several impedances their mutual return losses can be roughly estimated by inspection. + +The calibration for the scale with regard to a return loss $A$ is derived from the expression: + +$$R = \frac{k}{2} \{R_x + R_y\}$$ + +where: + +$$R_x = \ln \left\{ \frac{1 + 10^{-\frac{A}{20}}}{1 - 10^{-\frac{A}{20}}} \right\} \qquad R_y = 2 \cdot \text{arctg} \left\{ 10^{-\frac{A}{20}} \right\}$$ + +Figure I.4 shows as an example impedance curves for constant return losses against 600 $\Omega$ . Note that the curves are almost circles for loss values $> 10$ dB. + +![Figure I.3/Q.552: A special impedance diagram showing two dashed curves representing constant return loss. The top horizontal axis is Z [kΩ] from 0.3 to 1.5. The left vertical axis is φ(Z) [degrees] from 0 to -50. The bottom horizontal axis is Return Loss [dB] from ∞ to 6. A horizontal double-headed arrow between two points on the curves indicates a return loss of 20 dB.](48a08e5cabec8b75386679d8a57dec3e_img.jpg) + +Figure I.3/Q.552: A special impedance diagram showing two dashed curves representing constant return loss. The top horizontal axis is Z [kΩ] from 0.3 to 1.5. The left vertical axis is φ(Z) [degrees] from 0 to -50. The bottom horizontal axis is Return Loss [dB] from ∞ to 6. A horizontal double-headed arrow between two points on the curves indicates a return loss of 20 dB. + +T1524020-96 + +X-axis absolute value in kΩ + Y-axis argument in degrees + +**Figure I.3/Q.552 – A special impedance diagram where the return loss between two-impedance points can be read from the "return loss" distance scale (20 dB shown)** + +![Figure I.4/Q.552: A diagram showing constant return loss curves as concentric circles. The top horizontal axis is Z [kΩ] from 0.3 to 1.5. The left vertical axis is φ(Z) [degrees] from 50 to -50. The bottom horizontal axis is Return Loss [dB] from ∞ to 6. The circles are centered on the Z-axis at approximately 0.6 kΩ.](5bf611979ab0126ebd219a1c6eda6b1e_img.jpg) + +Figure I.4/Q.552: A diagram showing constant return loss curves as concentric circles. The top horizontal axis is Z [kΩ] from 0.3 to 1.5. The left vertical axis is φ(Z) [degrees] from 50 to -50. The bottom horizontal axis is Return Loss [dB] from ∞ to 6. The circles are centered on the Z-axis at approximately 0.6 kΩ. + +T1524030-96 + +**Figure I.4/Q.552 – Constant return loss curves for 10, 15, 20, 30 dB against 600 Ω** + +Applications of this special diagram are also given in I.8. + +When a large amount of impedance data have to be analysed, it is more convenient to make separate impedance diagrams for frequency points included in the survey in order to find an optimum balance impedance point for that frequency. In principle, this optimum can be chosen according to different criteria. One way would be to choose the point as "the centre of gravity" which give the best "r.m.s." average of echo (or sidetone) suppression at that frequency for the cases considered. Another way would be to enclose the points with the smallest circle and choose the centre of this circle as the optimum impedance point. + +When it comes to match these points with a suitable impedance function, the echo loss or sidetone weighting should be considered. + +## 1.7 Conclusions + +By the methods shown here, a network planner can find optimum terminating and balancing impedances for the networks he is responsible for. In general, if unloaded cable are used in a controlled network, a capacitive complex impedance as a compromise may be preferred as the nominal impedance. Then, quite high echo losses can be obtained which may reduce the need of echo cancellors. However, for many networks it may not be very critical to obtain very high echo losses in the subscriber network because, for other reasons, echo cancellors must be/are inserted in many trunks anyhow. Likewise, the levels in the network can be such that the send and receive sensitivity of the telephone sets on short lines need not be too high, i.e. the nominal exchange impedance need not be complex. In that case, for regulated telephones the sidetone circuit is designed for a medium-to-long cable, terminated with for instance 600 $\Omega$ . Moreover, in deregulated telecom markets the network operator may not have a very close control of what terminals are used in their network and what their parameters are. + +For other networks, however, one may wish to avoid a widespread of echo cancellors and/or use more sensitive telephone sets near the exchange. Then the rules and observations mentioned earlier in this appendix are worth noticing when choosing input and balance impedances. + +### 1.8 Examples of impedances $Z_2$ and compromise nominal impedances $Z_T$ and $Z_B$ + +Only to illustrate the subject given in 1.1 to 1.7 to the reader, this clause gives some detailed numerical examples for a chosen limited range of subscriber cables. It is also assumed that the network operator had the authority to prescribe a common nominal impedance to be used for future equipment. However, the operator also had to consider equipment with 600 $\Omega$ resistive input impedance. + +The problem for the operator is to choose the input impedance $Z_{T_{ex}}$ of the digital exchange in such a way that the sidetone performance of the telephone set becomes adequate, and to choose the input impedance $Z_{T_{set}}$ of the telephone set so that the talker echo for the subscriber at the other end is adequately suppressed. + +Some network operators have found that by their telephone set designs, sidetone and therefore input impedance is not a very critical parameter such as it is with more sensitive telephones. + +It can be seen from equation (I-4) that the characteristic impedance of the unloaded cable is inversely proportional to the cable diameter and inversely proportional to the square root of the cable capacitance. Therefore, it is not possible to find one unique nominal impedance to match exactly all the types of cables that usually are found in the network of a service provider. Moreover, many analogue networks contain equipment with an impedance of nominally 600 $\Omega$ resistive. For the determination of a compromise nominal impedance $Z_T$ these impedances must also be considered. An overview of the problems and discussion of the methodology is given in [1] and [2]. + +Some calculated curves will be presented as an illustration for a typical unloaded 0.5 mm-Cu-subscriber cable with: + +$$R' = 168 \frac{\Omega}{\text{km}}, L' = 0.7 \frac{\text{mH}}{\text{km}}, G' = 1 \frac{\mu\text{S}}{\text{km}}, C' = 50 \frac{\text{nF}}{\text{km}}, 300 \text{ Hz} \leq f \leq 3.4 \text{ kHz} \text{ (data see [3])}$$ + +#### 1.8.1 Cable input impedance $Z_2$ and hybrid input impedance $Z_T$ + +The cable input impedance $Z_2$ is calculated for a terminating impedance: + +- $Z_T = 600 \Omega$ resistive termination, representing the nominal impedance of many existing telephone sets; +- $Z_T = Z_{\text{ETSI}} = 270 \Omega + (750 \Omega \parallel 150 \text{ nF})$ , representing the nominal impedance of future telephone sets. + +The ETSI-impedance is a compromise which has been recommended to be used both as the nominal input impedance of equipment in the 2-wire network (exchanges and terminals) and as balance impedance in exchanges. + +NOTE – The input impedance of telephone sets has a rather wide tolerance, some sets are often slightly inductive. + +Figure I.5 shows the input impedance of a cable with length variation $0 \text{ km} \leq l \leq 4 \text{ km}$ and terminated with $600 \Omega$ resistive, and similarly Figure I.6 for the ETSI-impedance $Z_{\text{ETSI}}$ as termination. + +![Figure I.5/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by ZT = 600 Ω resistive load. The plot shows Re(Z) [Ω] on the x-axis (0 to 1400) and Im(Z) [Ω] on the y-axis (0 to -800). Curves are shown for lengths 0 km, 1 km, 2 km, 3 km, and 4 km. Frequency markers (300 Hz, 500 Hz, 1000 Hz, 2000 Hz, 3400 Hz) are indicated on the curves.](7f7976a4f76d8a3fe55dbf1e2f50973f_img.jpg) + +The figure is a complex impedance plot with the real part $\text{Re}(Z)$ on the horizontal axis and the imaginary part $\text{Im}(Z)$ on the vertical axis. The horizontal axis ranges from 0 to 1400 $\Omega$ with major ticks every 200 $\Omega$ . The vertical axis ranges from 0 to -800 $\Omega$ with major ticks every 200 $\Omega$ . Five curves represent different cable lengths: 0 km, 1 km, 2 km, 3 km, and 4 km. All curves start at $(600, 0)$ on the real axis. As length increases, the curves move further into the negative imaginary region. Frequency markers are placed along the curves: 3400 Hz at the top-left of the 0 km curve, 2000 Hz at the top-left of the 1 km curve, 1000 Hz at the bottom of the 2 km curve, 500 Hz at the bottom of the 3 km curve, and 300 Hz at the bottom of the 4 km curve. A small label 'T1527070-97' is in the bottom right corner. + +Figure I.5/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by ZT = 600 Ω resistive load. The plot shows Re(Z) [Ω] on the x-axis (0 to 1400) and Im(Z) [Ω] on the y-axis (0 to -800). Curves are shown for lengths 0 km, 1 km, 2 km, 3 km, and 4 km. Frequency markers (300 Hz, 500 Hz, 1000 Hz, 2000 Hz, 3400 Hz) are indicated on the curves. + +**Figure I.5/Q.552 – Input impedance $Z_2$ of a 0.5 mm cable with different lengths terminated by $Z_T = 600 \Omega$ resistive load** + +![Figure I.6/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by ZT = ZETSI = 270 Ω + (750 Ω || 150 nF). The plot shows Re(Z) [Ω] on the x-axis (0 to 1400) and Im(Z) [Ω] on the y-axis (0 to -800). Solid curves represent cable lengths of 0 km, 1 km, 2 km, 3 km, and 4 km. Dotted lines connect points of the same frequency (300 Hz, 500 Hz, 1000 Hz, 2000 Hz, 3400 Hz) across different lengths. The impedance curves generally show a decrease in resistance and an increase in capacitive reactance with frequency and length.](24b549c0c4b79c515b244625cf4f4978_img.jpg) + +Figure I.6/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by ZT = ZETSI = 270 Ω + (750 Ω || 150 nF). The plot shows Re(Z) [Ω] on the x-axis (0 to 1400) and Im(Z) [Ω] on the y-axis (0 to -800). Solid curves represent cable lengths of 0 km, 1 km, 2 km, 3 km, and 4 km. Dotted lines connect points of the same frequency (300 Hz, 500 Hz, 1000 Hz, 2000 Hz, 3400 Hz) across different lengths. The impedance curves generally show a decrease in resistance and an increase in capacitive reactance with frequency and length. + +NOTE – The dotted lines connect points of the same frequency but different cable length. + +**Figure I.6/Q.552 – Input impedance $Z_2$ of a 0.5 mm cable with different lengths terminated by $Z_T = Z_{ETSI} = 270 \text{ } \Omega + (750 \text{ } \Omega \parallel 150 \text{ nF})$** + +To compare the effect of different cable terminations, Figure I.7 shows the range of the magnitude of the reflection coefficient versus the frequency with the cable length as parameter (calculated with equation I-7). A general aim is to have a reflection coefficient of "Zero" all over the frequency- and length-range under consideration. + +![Figure I.7/Q.552: Reflection coefficient |r| versus frequency (0 to 3600 Hz). The plot compares two termination impedances: ZT = 600 Ω (dashed lines) and ZT = ZETSI = 270 Ω + (750 Ω || 150 nF) (solid lines). Cable lengths shown are 0.5 km, 1 km, 2 km, 3 km, and 4 km. For ZT = 600 Ω, |r| increases with frequency and length. For ZT = ZETSI, |r| is significantly lower, remaining below 0.15 across the entire frequency and length range.](9db774ce7e2ae9d89f439a41156214dd_img.jpg) + +- $Z_T = 600 \text{ } \Omega$ +- $Z_T = Z_{ETSI} = 270 \text{ } \Omega + (750 \text{ } \Omega \parallel 150 \text{ nF})$ + +Figure I.7/Q.552: Reflection coefficient |r| versus frequency (0 to 3600 Hz). The plot compares two termination impedances: ZT = 600 Ω (dashed lines) and ZT = ZETSI = 270 Ω + (750 Ω || 150 nF) (solid lines). Cable lengths shown are 0.5 km, 1 km, 2 km, 3 km, and 4 km. For ZT = 600 Ω, |r| increases with frequency and length. For ZT = ZETSI, |r| is significantly lower, remaining below 0.15 across the entire frequency and length range. + +**Figure I.7/Q.552 – Reflection coefficient: Impedance $Z_T$ compared to cable input impedance $Z_2$ (cable terminated by the impedance $Z_T$ ) versus frequency** + +#### I.8.2 Balance impedance $Z_B$ + +If only terminals with the ETSI input impedance are used, it is possible to obtain a better average balance return loss by choosing a $Z_B$ that differs from $Z_{ETSI}$ . + +A three-element balance network $Z_{B_{calc}}$ was found by an iterative calculation process with the following preconditions regarding the echo loss $L_e$ : + +- cable lengths and type: $0 \text{ km} \leq l \leq 4 \text{ km}$ , 0.5 mm-Cu; +- cable termination impedance $Z_T = Z_{ETSI} = 270 \Omega + (750 \Omega \parallel 150 \text{ nF})$ ; +- $L_e$ should be a maximum in the range of the average length (resulting of the cumulative length-distribution of a network; in this example an average length of 1.7 km is assumed); +- for $l = 0 \text{ km}$ and $l = 4 \text{ km}$ : $L_e$ should be a minimum but the value should be as high as possible and nearly the same. + +The result of the calculation is: + +$$Z_{B_{calc}} = 230 \Omega + (1040 \Omega \parallel 160 \text{ nF})$$ + +NOTE – For low frequencies $|Z_{B_{calc}}| \approx |Z_{ETSI}| + (1.7 \text{ km} \cdot R')$ . + +Figure I.8 shows the locus of the balance impedance $Z_{B_{calc}}$ in comparison with the ETSI-impedance $Z_{ETSI}$ . + +![Figure I.8/Q.552: Loci of Z_Bcalc and Z_ETSI in the complex impedance plane. The horizontal axis is Re(Z) [Ω] from 0 to 1400. The vertical axis is Im(Z) [Ω] from 0 to -800. Two curves are shown: a solid line for Z_Bcalc = 230 Ω + (1040 Ω || 160 nF) and a dashed line for Z_ETSI = 270 Ω + (750 Ω || 150 nF). Points on the curves are marked for frequencies 300 Hz, 500 Hz, 1000 Hz, 2000 Hz, and 3400 Hz. The Z_ETSI curve starts at (270, 0) for 0 km and ends at (300, -600) for 4 km. The Z_Bcalc curve starts at (230, 0) for 0 km and ends at (300, -750) for 4 km. A shaded region between the curves represents the input impedance range of the cable terminated by Z_ETSI.](7275fd1dcf74a5eb83ac081f11e0ab7c_img.jpg) + +Figure I.8/Q.552: Loci of Z\_Bcalc and Z\_ETSI in the complex impedance plane. The horizontal axis is Re(Z) [Ω] from 0 to 1400. The vertical axis is Im(Z) [Ω] from 0 to -800. Two curves are shown: a solid line for Z\_Bcalc = 230 Ω + (1040 Ω || 160 nF) and a dashed line for Z\_ETSI = 270 Ω + (750 Ω || 150 nF). Points on the curves are marked for frequencies 300 Hz, 500 Hz, 1000 Hz, 2000 Hz, and 3400 Hz. The Z\_ETSI curve starts at (270, 0) for 0 km and ends at (300, -600) for 4 km. The Z\_Bcalc curve starts at (230, 0) for 0 km and ends at (300, -750) for 4 km. A shaded region between the curves represents the input impedance range of the cable terminated by Z\_ETSI. + +NOTE – The area shown represents the input impedance range of the cable terminated by $Z_{ETSI}$ (see Figure I.6). + +**Figure I.8/Q.552 – Loci of $Z_{B_{calc}} = 230 \Omega + (1040 \Omega \parallel 160 \text{ nF})$ and $Z_{ETSI} = 270 \Omega + (750 \Omega \parallel 150 \text{ nF})$** + +### I.8.3 Application of the special impedance diagram + +Figures I.9 and I.10 show the same input impedance curves as depicted in Figures I.5 and I.6; however, in the special impedance diagram mentioned above, the same type of cable is terminated with $Z_{ETSI}$ and $600 \Omega$ respectively. + +Also depicted are two examples of balance impedances, namely $Z_{ETSI}$ and $Z_{B_{calc}}$ . As can be seen directly, $Z_{B_{calc}}$ is more optimal if the $Z_{ETSI}$ -termination is the only one allowed. However, if only 600 $\Omega$ -termination have to be considered, $Z_{ETSI}$ is the better choice. It is also apparent that a complex impedance termination results in much less impedance deviations so that better balancing with a single 3-element-impedance-network is possible. + +Note that the ETSI-impedance was obtained from more data than just 0.5 mm Cu-cables. + +![Figure I.9/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by Z0 = 600 Ohm resistive load in comparison to ZETSI (a) and ZBcalc (b).](65a73373b57df71e5c2ce1ce0eb7b65d_img.jpg) + +The figure is a graph showing the input impedance $Z_2$ of a 0.5 mm cable. The vertical axis represents the phase $\phi(Z)$ in degrees, ranging from 0 to 50. The top horizontal axis shows the magnitude of the impedance $Z$ in $k\Omega$ , ranging from 0.3 to 1.5. The bottom horizontal axis shows the Return Loss in dB, ranging from $\infty$ to 6. The graph displays several curves for different cable lengths: 0 km, 1 km, 2 km, 3 km, and 4 km. Two specific curves are labeled 'a' and 'b', corresponding to $Z_{ETSI}$ and $Z_{B_{calc}}$ respectively. Frequency markers are present at 300 Hz, 500 Hz, 1000 Hz, 2000 Hz, and 3400 Hz. The curves show that as the cable length increases, the input impedance deviates more from the ideal 600 $\Omega$ termination, especially at higher frequencies. + +Figure I.9/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by Z0 = 600 Ohm resistive load in comparison to ZETSI (a) and ZBcalc (b). + +T1527110-97 + +Figure I.9/Q.552 – Input impedance $Z_2$ of a 0.5 mm cable with different lengths terminated by $Z_0 = 600 \Omega$ resistive load in comparison to $Z_{ETSI}$ (a) and $Z_{B_{calc}}$ (b) + +![Figure I.10/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by Z0 = ZETSI = 270 Ω + (750 Ω || 150 nF) in comparison to ZETSI (a) and ZBcalc (b).](f899c67120dc04a5e5a5c2d94461a077_img.jpg) + +The graph plots the phase $\phi(Z)$ in degrees on the y-axis (0 to 50, increasing downwards) against the input impedance $Z$ in $\text{k}\Omega$ on the top x-axis (0.3 to 1.5). A secondary x-axis at the bottom shows Return Loss in dB ( $\infty$ to 6). Solid curves represent different cable lengths: 0 km, 1 km, 2 km, 3 km, and 4 km. Dotted lines represent frequency markers: 300 Hz, 500 Hz, 1000 Hz, 2000 Hz, and 3400 Hz. Two specific curves are labeled 'a' and 'b'. + +Figure I.10/Q.552: Input impedance Z2 of a 0.5 mm cable with different lengths terminated by Z0 = ZETSI = 270 Ω + (750 Ω || 150 nF) in comparison to ZETSI (a) and ZBcalc (b). + +T1527120-97 + +NOTE – The dotted lines for different frequency marks in Figures I.9 and I.10 refer only to the input impedance $Z_2$ curves. + +**Figure I.10/Q.552 – Input impedance $Z_2$ of a 0.5 mm cable with different lengths terminated by $Z_0 = Z_{\text{ETSI}} = 270 \Omega + (750 \Omega \parallel 150 \text{ nF})$ in comparison to $Z_{\text{ETSI}}$ (a) and $Z_{\text{Bcalc}}$ (b)** + +The $Z_{\text{ETSI}}$ and $Z_{\text{Bcalc}}$ impedance curve results of the same frequency range $300 \text{ Hz} \leq f \leq 3400 \text{ Hz}$ ; however, due to a better representation the frequencies 500 Hz, 1000 Hz and 2000 Hz are not marked for $Z_{\text{ETSI}}$ and $Z_{\text{Bcalc}}$ in Figure I.9 and for $Z_{\text{Bcalc}}$ in Figure I.10 (the deviation can be seen in Figure I.8). + +#### I.8.4 Echo considerations + +##### I.8.4.1 Echo loss $L_e$ + +The echo loss $L_e$ is the weighted average of $L_{TR} = L_T + L_{br} + L_R$ (see equation I-1). + +Figure I.11 shows the echo loss at the listener's exchange for different combinations of impedances. At the exchange line circuit, the losses $L_T = 0 \text{ dB}$ and $L_R = 7 \text{ dB}$ are assumed. + +![Figure I.11/Q.552: A line graph showing Echo loss (dB) on the y-axis (0 to 50) versus Length (km) on the x-axis (0 to 4). Four curves are plotted: curve a) is a dotted line starting at ~18 dB at 0 km and decreasing to ~26 dB at 4 km; curve b) is a dashed line starting at ~50 dB at 0 km and decreasing to ~21 dB at 4 km; curve c) is a dotted line starting at ~15 dB at 0 km, peaking at ~40 dB at 3.8 km, and ending at ~39 dB at 4 km; curve d) is a solid line starting at ~27 dB at 0 km, peaking at ~46 dB at 1.5 km, and ending at ~27 dB at 4 km. The curves intersect at various points, notably around 1.5 km and 2.5 km.](bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg) + +Figure I.11/Q.552: A line graph showing Echo loss (dB) on the y-axis (0 to 50) versus Length (km) on the x-axis (0 to 4). Four curves are plotted: curve a) is a dotted line starting at ~18 dB at 0 km and decreasing to ~26 dB at 4 km; curve b) is a dashed line starting at ~50 dB at 0 km and decreasing to ~21 dB at 4 km; curve c) is a dotted line starting at ~15 dB at 0 km, peaking at ~40 dB at 3.8 km, and ending at ~39 dB at 4 km; curve d) is a solid line starting at ~27 dB at 0 km, peaking at ~46 dB at 1.5 km, and ending at ~27 dB at 4 km. The curves intersect at various points, notably around 1.5 km and 2.5 km. + +T1527130-97 + +**Figure I.11/Q.552 – Echo loss in a network versus different cable length with different hybrid impedances as parameter:** + +- curve a)** $Z_{T_{set}} = 600 \Omega$    $Z_{B_{ex}} = Z_{ETSI}$ +**curve b)** $Z_{T_{set}} = Z_{ETSI}$    $Z_{B_{ex}} = Z_{ETSI}$ +**curve c)** $Z_{T_{set}} = 600 \Omega$    $Z_{B_{ex}} = Z_{B_{calc}}$ +**curve d)** $Z_{T_{set}} = Z_{ETSI}$    $Z_{B_{ex}} = Z_{B_{calc}}$ + +##### I.8.4.2 Sidetone loss $L_{st}$ + +The sidetone loss $L_{st}$ is the weighted average of $L_{TR} = L_T + L_{br} + L_R$ (see equation I-1). Figure I.12 shows the sidetone loss at the hybrid of a telephone set for different balance networks. At the telephone set, the losses $L_T = L_R = 0$ dB are assumed. + +The sidetone loss $L_{st}$ can be transformed into a STMR value for the set in the following way. Referred to the 0 dBr point of the exchange, the "target value" is $(SLR + RLR) = 10$ dB. The sum of the T and R-pads usually is $(T + R) = 7$ dB. Suppose the line attenuation is 3 dB, then for the set itself $\{SLR(set) + RLR(set)\} = 10$ dB $- 7$ dB $- 2 \times 3$ dB $= -3$ dB. Thus, using equation (I-9): $STMR = L_{st} - 4$ . Judging from the $L_{st}$ – values of Figure I.8, there is no problem with a too loud sidetone. + +![Graph showing Sidetone loss [dB] versus Length [km] for two different balance networks. Curve 'a' (dashed line) starts at 50 dB at 0 km and decreases to approximately 16 dB at 4 km. Curve 'b' (solid line) starts at 21 dB at 0 km, peaks at 40 dB at 1.5 km, and decreases to approximately 23 dB at 4 km. The x-axis ranges from 0 to 4 km, and the y-axis ranges from 0 to 50 dB. A small label 'T1527140-97' is present in the bottom right corner of the graph area.](157e8c1d80a02c8eee893c2ea60a77a8_img.jpg) + +Graph showing Sidetone loss [dB] versus Length [km] for two different balance networks. Curve 'a' (dashed line) starts at 50 dB at 0 km and decreases to approximately 16 dB at 4 km. Curve 'b' (solid line) starts at 21 dB at 0 km, peaks at 40 dB at 1.5 km, and decreases to approximately 23 dB at 4 km. The x-axis ranges from 0 to 4 km, and the y-axis ranges from 0 to 50 dB. A small label 'T1527140-97' is present in the bottom right corner of the graph area. + +**Figure I.12/Q.552 – Sidetone loss for different balance networks in the telephone set** + +**curve a)** $Z_{T_{ex}} = Z_{ETSI}$    $Z_{B_{set}} = Z_{ETSI}$ +**curve b)** $Z_{T_{ex}} = Z_{ETSI}$    $Z_{B_{set}} = Z_{B_{calc}}$ + +# Bibliography + +- [1] ITU-T G.100-series Supplement 31 (1993), *Principles of determining an impedance strategy for the local network*. +- [2] ADLER (K.), RAHMIG (G.): Unterdrückung des Sprecherechos in gemischt analog/digitalen Netzen *Frequenz*, Band 46, pp. 210-216, July-August 1992. +- [3] ETSI ETR 004 (1990), *Overall transmission plan aspects of a private branch network for voice connections with access to the public 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.553-200111-I_PDF-E/raw.md b/marked/Q/T-REC-Q.553-200111-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..aa189406882568368c23d5ea4cc2a60a83eaa74d --- /dev/null +++ b/marked/Q/T-REC-Q.553-200111-I_PDF-E/raw.md @@ -0,0 +1,573 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.553** + +(11/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Digital exchanges – Transmission characteristics + +--- + +**Transmission characteristics at 4-wire analogue +interfaces of digital exchanges** + +ITU-T Recommendation Q.553 + +--- + +# 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 | +| Introduction and field of application | Q.500-Q.509 | +| Exchange interfaces, functions and connections | Q.510-Q.539 | +| Design objectives and measurement | Q.540-Q.549 | +| Transmission characteristics | Q.550-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. + +# **Transmission characteristics at 4-wire analogue interfaces of digital exchanges** + +## **Summary** + +This Recommendation provides characteristics for 4-wire analogue interfaces, input and output connections with 4-wire analogue interfaces and half-connections with 4-wire analogue interfaces in digital transit and combined local and transit exchanges in accordance with definitions given in ITU-T Rec. Q.551. + +This Recommendation is intended for switching connections that may be part of an international long-distance connection via 4-wire line circuits interconnected by 4-wire exchanges. Since 4-wire analogue interfaces on digital exchanges may connect with circuits which are used for both international and national traffic, the same values recommended for international connections may also be used for connections entirely within the national network. + +## **Source** + +ITU-T Recommendation Q.553 was revised by ITU-T Study Group 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 November 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 | General..... | 1 | +| 2 | Characteristics of interfaces..... | 1 | +| 2.1 | Characteristics common to all 4-wire analogue interfaces ..... | 1 | +| 2.1.1 | Exchange impedance ..... | 1 | +| 2.1.2 | Impedance unbalance about earth..... | 1 | +| 2.1.3 | Relative levels..... | 2 | +| 2.2 | Characteristics of interface $C_{11}$ ..... | 3 | +| 2.2.1 | Values of nominal levels ..... | 3 | +| 2.3 | Characteristics of interface $C_{12}$ ..... | 4 | +| 2.3.1 | Values of nominal levels ..... | 4 | +| 2.4 | Characteristics of interface $C_{13}$ ..... | 4 | +| 2.4.1 | Values of nominal levels ..... | 4 | +| 3 | Characteristics of half connections ..... | 5 | +| 3.1 | Characteristics common to all 4-wire analogue interfaces ..... | 5 | +| 3.1.1 | Transmission loss ..... | 5 | +| 3.1.2 | Group delay ..... | 7 | +| 3.1.3 | Noise..... | 8 | +| 3.1.4 | Crosstalk ..... | 8 | +| 3.1.5 | Total distortion including quantizing distortion ..... | 10 | +| 3.1.6 | Discrimination against out-of-band signals applied to the input interface.... | 11 | +| 3.1.7 | Spurious out-of-band signals received at the output interface..... | 12 | +| 3.2 | Characteristics for interface $C_{11}$ ..... | 12 | +| 3.2.1 | Nominal value of transmission loss..... | 12 | +| 3.3 | Characteristics for interface $C_{12}$ ..... | 12 | +| 3.3.1 | Nominal value of transmission loss..... | 12 | +| 3.4 | Characteristics for interface $C_{13}$ ..... | 12 | +| 3.4.1 | Nominal value of transmission loss..... | 12 | + + + +# **Transmission characteristics at 4-wire analogue interfaces of digital exchanges** + +# **1 General** + +This Recommendation provides characteristics for: + +- 4-wire analogue interfaces (Type C11, C12 and C13); +- input and output connections with 4-wire analogue interfaces; and +- half connections with 4-wire analogue interfaces + +in digital transit and combined local and transit exchanges, in accordance with the definitions given in ITU-T Rec. Q.551, particularly in Figures 1/Q.551 and 2/Q.551. + +The characteristics of the input and output connections of a given interface are not necessarily the same. The characteristics of half connections are not necessarily identical for different types of interfaces. + +This Recommendation is intended for switched connections that may be part of an international long-distance connection via 4-wire line circuits interconnected by 4-wire exchanges. Since 4-wire analogue interfaces of digital exchanges may connect with circuits which are used for both international and national traffic, the same values recommended for international connections may also be used for connections entirely within the national network. + +## **2 Characteristics of interfaces** + +### **2.1 Characteristics common to all 4-wire analogue interfaces** + +### **2.1.1 Exchange impedance** + +#### **2.1.1.1 Nominal value** + +The nominal impedance at the analogue input and output interfaces should be 600 ohms, balanced. + +#### **2.1.1.2 Return loss** + +The return loss at the equipment ports, measured against the nominal impedance, should not be less than 20 dB over the frequency range 300 Hz to 3400 Hz. + +NOTE – For output measurement, the exchange test point Ti must be driven by a PCM signal corresponding to the decoder output value number 0 for the $\mu$ -law or decoder output value number 1 for the A-law. (See 1.2.3.1/Q.551.) + +### **2.1.2 Impedance unbalance about earth** + +The value for the Longitudinal Conversion Loss (LCL) at the equipment ports as defined in 4.1.3/G.117, with the circuit under test in the normal talking state, should exceed the minimum values of Figure 1, in accordance with ITU-T Rec. K.10. + +NOTE 1 – A network operator may adopt other values and, in some cases, a wider bandwidth, depending upon actual conditions in its telephone network. + +NOTE 2 – A limit may also be required for the Transverse Conversion Loss (TCL) as defined in 4.1.2/G.117, if the exchange termination is not reciprocal with respect to the transverse and longitudinal connections. A suitable limit would be 40 dB to ensure an adequate near-end crosstalk attenuation between interfaces. + +![Figure 1/Q.553: A graph showing the minimum values of LCL (Loss in dB) versus Frequency (f in Hz). The y-axis ranges from 0 to 50 dB. The x-axis ranges from 0 to 3400 Hz. The graph shows a shaded region representing the minimum loss values. The loss is 40 dB from 0 to 300 Hz, then increases to 46 dB at 600 Hz, and remains constant at 46 dB up to 3400 Hz. The shaded area is bounded by the lines f=300, f=600, and f=3400.](c3c305cefbac2e7b13be34ab87054d1e_img.jpg) + +Figure 1/Q.553: A graph showing the minimum values of LCL (Loss in dB) versus Frequency (f in Hz). The y-axis ranges from 0 to 50 dB. The x-axis ranges from 0 to 3400 Hz. The graph shows a shaded region representing the minimum loss values. The loss is 40 dB from 0 to 300 Hz, then increases to 46 dB at 600 Hz, and remains constant at 46 dB up to 3400 Hz. The shaded area is bounded by the lines f=300, f=600, and f=3400. + +**Figure 1/Q.553 – Minimum values of LCL measured in the arrangement shown in Figure 2** + +#### Test method + +LCL should be measured in accordance with the principles given in 4.1/O.9. Figure 2 shows the basic measuring arrangement. Arrangements containing two resistors each of value $R/2$ may also be used (see clause 5/O.9). + +Measurements of the longitudinal and transverse voltages should be performed by means of a frequency-selective level meter. + +![Figure 2/Q.553: A circuit diagram showing the arrangement for measuring LCL. A sinusoidal oscillator is connected to a series combination of a resistor R/4 and a parallel combination of a resistor R and a voltmeter V_L1. This is followed by a C1 interface. The 'Item under test' is connected to the interface. The input connection of the item under test is connected to a series combination of a resistor R and a voltmeter V_T1. The output connection of the item under test is connected to a series combination of a resistor R and a voltmeter V_T1. The item under test has two exchange test points, T_o and T_i, indicated by arrows.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +Figure 2/Q.553: A circuit diagram showing the arrangement for measuring LCL. A sinusoidal oscillator is connected to a series combination of a resistor R/4 and a parallel combination of a resistor R and a voltmeter V\_L1. This is followed by a C1 interface. The 'Item under test' is connected to the interface. The input connection of the item under test is connected to a series combination of a resistor R and a voltmeter V\_T1. The output connection of the item under test is connected to a series combination of a resistor R and a voltmeter V\_T1. The item under test has two exchange test points, T\_o and T\_i, indicated by arrows. + +$R = 600$ ohms + +T1515680-94 + +$$\text{Longitudinal conversion loss (LCL)} = 20 \log_{10} \left| \frac{V_{L1}}{V_{T1}} \right| \text{ dB}$$ + +**Figure 2/Q.553 – Arrangement for measuring LCL** + +### 2.1.3 Relative levels + +In assigning the relative levels to the interfaces, the limiting of "difference in transmission loss between the two directions of transmission" in Annex A/G.121 has been taken into account. For the national extension, this is the value "loss (t-b)–loss (a-t)". (See the text in the cited + +Recommendation for guidance.) This difference is limited to $\pm 4$ dB. However, to allow for additional asymmetry of loss in the rest of the national network, only part of this difference can be used by the digital exchange. + +#### 2.1.3.1 Nominal levels + +The nominal relative levels at the analogue input and output interfaces of the digital exchange depend on the type of equipment which is connected to the exchange. (See Figure 1/Q.551.) + +In practice, it may be necessary to compensate for the loss between the output interfaces of the digital exchange and the input ports of the connected equipment to fulfil transmission plan conditions. The definition of adjustable steps for and the location of this compensation (digital exchange or connected equipment) is within national competence. + +Nominal values of relative levels are given in 2.2.1, 2.3.1 and 2.4.1 for the different types of half connections. + +#### 2.1.3.2 Tolerances of relative levels + +The difference between the actual relative level and the nominal relative level should lie within the following ranges: + +- input relative level: $-0.3$ to $+0.7$ dB; +- output relative level: $-0.7$ to $+0.3$ dB. + +These differences may arise, for example, from design tolerances, cabling (between analogue equipment ports and the DF) and adjustment increments. + +NOTE – Adjustment of the relative level should be made in accordance with clause 3/G.712. + +### 2.2 Characteristics of interface C11 + +According to Figure 1/Q.551, the interface C11 of a digital exchange is intended to interwork with the channel translating equipment of an FDM system. + +### 2.2.1 Values of nominal levels + +The nominal values of relative levels at the channel translating equipment are specified in Table 2/G.232 for the two recommended cases. With the pads in the channel translating equipment set to zero, these values are: + +| | Case 1 | Case 2 | +|-----|-------------|-------------| +| $R$ | $+4.0$ dBr | $+7.0$ dBr | +| $S$ | $-14.0$ dBr | $-16.0$ dBr | + +The nominal values of relative levels at the digital exchange must be adjusted to compensate for the total loss between the interface of the digital exchange and the channel translating equipment. Therefore: + +$$L_i = R - A_R$$ + +$$L_o = S + A_S$$ + +where: + +$A_R$ is the total loss in the receive path, e.g. direction of transmission from channel translating equipment to digital exchange. + +$A_S$ is the total loss in the send path, e.g. direction of transmission from digital exchange to channel translating equipment. + +## 2.3 Characteristics of interface C12 + +According to Figure 1/Q.551, the interface C12 of a digital exchange is intended to interwork with the incoming and outgoing relay set of an analogue 4-wire exchange. (See Figure 1/Q.45 *bis.*) + +### 2.3.1 Values of nominal levels + +The nominal values of relative levels at the relay set of an analogue exchange are consistent with Table 2/G.232 for the two recommended cases. These values are: + +| | Case 1 | Case 2 | +|-----|------------|------------| +| $R$ | – 14.0 dBr | – 16.0 dBr | +| $S$ | + 4.0 dBr | + 7.0 dBr | + +The nominal values of relative levels at the digital exchange must be adjusted to compensate for the total loss between the interface of the digital exchange and the relay sets of the analogue exchange. + +Therefore: + +$$L_i = R - A_R$$ + +$$L_o = S + A_S$$ + +where: + +$A_R$ is the total loss in the receive path, e.g. direction of transmission from relay set to digital exchange. + +$A_S$ is the total loss in the send path, e.g. direction of transmission from digital exchange to relay set. + +### 2.4 Characteristics of interface C13 + +According to Figure 1/Q.551, the interface C13 of a digital exchange is intended to connect to a 4-wire analogue switching stage. (See Figure 1/G.142, case 5.) + +### 2.4.1 Values of nominal levels + +The nominal values of relative levels are determined by the relative levels of the analogue 4-wire switching stages in the national transmission plans. For example, if these relative levels are –3.5 dBr in both directions of transmission, the nominal input and output levels of a C13 interface should be: + +$$L_i \quad L_o \quad 3.5 \text{ dBr}$$ + +Different levels at the switching stages and transmission loss between interface C13 and the switching stages can require adjusting these levels. + +## **3 Characteristics of half connections** + +## **3.1 Characteristics common to all 4-wire analogue interfaces** + +### **3.1.1 Transmission loss** + +#### **3.1.1.1 Nominal value** + +The nominal transmission loss, according to 1.2.4.1/Q.551 is defined for input and output connections of a half connection with 4-wire analogue interface in 3.2.1, 3.3.1 and 3.4.1. + +#### **3.1.1.2 Tolerances of transmission loss** + +The difference between the actual transmission loss and the nominal transmission loss of an input or output connection of the same half connection according to 2.1.3.2 should lie within the following values: + +$$- 0.3 \text{ to } + 0.7 \text{ dB}$$ + +These differences may arise for example, from design tolerances, cabling (between analogue equipment ports and the DF) or adjustment increments. + +#### **3.1.1.3 Short-term variation of loss with time** + +When a sine-wave test signal at the reference frequency of 1020 Hz and at a level of $-10 \text{ dBm}0$ (if preferred, the value $0 \text{ dBm}0$ may be used) is applied to an analogue interface of any input connection, or a digitally simulated sine-wave signal of the same characteristics is applied to the exchange test point $T_i$ of any output connection, the level at the corresponding exchange test point $T_o$ and the level at the analogue interface of the output connection respectively, should not vary by more than $\pm 0.2 \text{ dB}$ during any 10-minute interval of typical operation under the steady state condition permitted variations in the power supply voltage and temperature. + +#### **3.1.1.4 Variation of gain with input level** + +With a sine-wave test signal at the reference frequency of 1020 Hz and at a level between $-55 \text{ dBm}0$ and $+3 \text{ dBm}0$ applied to the analogue interface of any input connection, or with a digitally simulated sine-wave signal of the same characteristic applied to the exchange test point $T_i$ of any output connection, the gain variation of that connection, relative to the gain at the input level of $-10 \text{ dBm}0$ , should lie within the limits given in Figure 3. + +The measurement should be made with a frequency selective meter to reduce the effect of the exchange noise. This requires a sinusoidal test signal. + +![Figure 3/Q.553 – Variation of gain with input level. The graph shows gain variation in dB on the y-axis (from -1.6 to 1.6) against input level in dBm0 on the x-axis (from -55 to +3). The gain is 1.6 dB for input levels from -55 to -50 dBm0. At -50 dBm0, the gain drops to 0.6 dB until -40 dBm0, then to 0.3 dB until +3 dBm0. At -50 dBm0, the gain also drops to -0.6 dB until -40 dBm0, then to -0.3 dB until +3 dBm0. At +3 dBm0, the gain returns to 1.6 dB. A preferred input level of -10 dBm0 is marked with a circled cross on the 0 dB line.](36ac3e730a00d3f42d3400f5709f641a_img.jpg) + +Figure 3/Q.553 – Variation of gain with input level. The graph shows gain variation in dB on the y-axis (from -1.6 to 1.6) against input level in dBm0 on the x-axis (from -55 to +3). The gain is 1.6 dB for input levels from -55 to -50 dBm0. At -50 dBm0, the gain drops to 0.6 dB until -40 dBm0, then to 0.3 dB until +3 dBm0. At -50 dBm0, the gain also drops to -0.6 dB until -40 dBm0, then to -0.3 dB until +3 dBm0. At +3 dBm0, the gain returns to 1.6 dB. A preferred input level of -10 dBm0 is marked with a circled cross on the 0 dB line. + +T1515690-94 + +**Figure 3/Q.553 – Variation of gain with input level** + +#### 3.1.1.5 Loss distortion with frequency + +According to 1.2.5/Q.551, the loss distortion with frequency of any input or output connection should lie within the limits shown in the mask of Figure 4 a) and b), respectively. The preferred input level is $-10$ dBm0. + +![Graph (a) Input connection showing Loss (dB) vs Frequency (f) in kHz. The y-axis ranges from -0.25 to 1.1 dB with major ticks at -0.25, 0, 0.25, 0.35, 0.5, 0.9, and 1.1. The x-axis ranges from 0 to 3.6 kHz with major ticks at 0, 0.2, 0.3, 1.0, 2.0, 2.4, 3.0, 3.4, and 3.6. The graph shows several loss limits: a top limit of 1.1 dB from 0.3 to 3.6 kHz; a limit of 0.9 dB from 0.3 to 3.0 kHz; a limit of 0.5 dB from 0.3 to 2.4 kHz; a limit of 0.35 dB from 0.3 to 2.0 kHz; and a limit of 0.25 dB from 0.3 to 2.4 kHz. A shaded region is shown between 0.3 and 0.5 dB from 0.3 to 2.0 kHz. A bottom limit of -0.25 dB is shown from 0.3 to 3.6 kHz. A point marked with an 'X' is at 1.0 kHz on the 0 dB line. The label '(Note)' appears twice in the upper right area.](dd0f5301a5a6dd7c319701302110de88_img.jpg) + +Graph (a) Input connection showing Loss (dB) vs Frequency (f) in kHz. The y-axis ranges from -0.25 to 1.1 dB with major ticks at -0.25, 0, 0.25, 0.35, 0.5, 0.9, and 1.1. The x-axis ranges from 0 to 3.6 kHz with major ticks at 0, 0.2, 0.3, 1.0, 2.0, 2.4, 3.0, 3.4, and 3.6. The graph shows several loss limits: a top limit of 1.1 dB from 0.3 to 3.6 kHz; a limit of 0.9 dB from 0.3 to 3.0 kHz; a limit of 0.5 dB from 0.3 to 2.4 kHz; a limit of 0.35 dB from 0.3 to 2.0 kHz; and a limit of 0.25 dB from 0.3 to 2.4 kHz. A shaded region is shown between 0.3 and 0.5 dB from 0.3 to 2.0 kHz. A bottom limit of -0.25 dB is shown from 0.3 to 3.6 kHz. A point marked with an 'X' is at 1.0 kHz on the 0 dB line. The label '(Note)' appears twice in the upper right area. + +a) Input connection + +![Graph (b) Output connection showing Loss (dB) vs Frequency (f) in kHz. The axes and limits are identical to graph (a). The label '(Note)' appears twice in the upper right area. A small code 'T1515710-94' is visible in the bottom right corner of the graph area.](b05a8a3551db31147979064952179990_img.jpg) + +Graph (b) Output connection showing Loss (dB) vs Frequency (f) in kHz. The axes and limits are identical to graph (a). The label '(Note)' appears twice in the upper right area. A small code 'T1515710-94' is visible in the bottom right corner of the graph area. + +b) Output connection + +NOTE – In the marked frequency ranges, relaxed limits are shown which apply if the maximum length of exchange cabling (see clause 2/Q.551) is used. The more stringent limits shown apply if no such cabling is present. + +**Figure 4/Q.553 – Loss distortion with frequency** + +### 3.1.2 Group delay + +#### 3.1.2.1 Absolute group delay + +See 3.3.1/Q.551. + +#### 3.1.2.2 Group delay distortion with frequency + +Taking the minimum group delay, in the frequency range between 500 Hz and 2800 Hz, of the input or output connection as the reference, the group delay distortion of that connection should lie within + +the limits shown in the template of Figure 5. Group delay distortion is measured in accordance with ITU-T Rec. O.81. + +![Figure 5/Q.553 – Group delay distortion limits with frequency. The graph shows group delay distortion in ms on the y-axis (0.13, 0.38, 0.75) against frequency in Hz on the x-axis (0, 500, 600, 1000, 2600, 2800). The limits are: 0.13 ms from 0 to 1000 Hz, 0.38 ms from 600 to 1000 Hz, and 0.75 ms from 2600 to 2800 Hz. The regions between 0.13 and 0.38 ms (1000-2600 Hz) and between 0.38 and 0.75 ms (600-2600 Hz) are shaded with diagonal lines.](0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg) + +Figure 5/Q.553 – Group delay distortion limits with frequency. The graph shows group delay distortion in ms on the y-axis (0.13, 0.38, 0.75) against frequency in Hz on the x-axis (0, 500, 600, 1000, 2600, 2800). The limits are: 0.13 ms from 0 to 1000 Hz, 0.38 ms from 600 to 1000 Hz, and 0.75 ms from 2600 to 2800 Hz. The regions between 0.13 and 0.38 ms (1000-2600 Hz) and between 0.38 and 0.75 ms (600-2600 Hz) are shaded with diagonal lines. + +**Figure 5/Q.553 – Group delay distortion limits with frequency** + +#### 3.1.3 Noise + +#### 3.1.3.1 Weighted noise + +Two components of noise should be considered: noise arising from the coding process, and noise from analogue sources such as signalling equipment and the analogue circuit for impedance and level adaptation. The first component is limited to $-67$ dBm0p for input connections and to $-70$ dBm0p for output connections in accordance with Table 7/G.712; the other component to $-(67 + 3)$ dBm0p $= -70$ dBm0p for one 4-wire analogue interface including circuit noise in accordance with clause 3/G.123. + +This results in the maximum values for the overall weighted noise in the talking state at the $C_1$ -interface of a digital exchange: + +- Equipment with signalling on separate wires: + - input connection: $-67.0$ dBm0p; + - output connection: $-70.0$ dBm0p. +- Equipment with signalling on the speech wires: + - input connection: $-65.2$ dBm0p; + - output connection: $-67.0$ dBm0p. + +#### 3.1.3.2 Single frequency noise + +The level of any single frequency (in particular the sampling frequency and its multiples), measured selectively at the interface of an output connection should not exceed $-50$ dBm0. Between 300 and 3400 Hz, the level of any single frequency measured selectively and corrected by the psophometric weighting factor (see Table 1/O.41) should not exceed $-73$ dBm0 (provisional value). + +NOTE – See 1.2.3.1/Q.551 with regard to common measurement conditions. + +### 3.1.4 Crosstalk + +For crosstalk measurements, auxiliary signals are injected as indicated in Figures 6 to 9. These signals are: + +- the quiet code (see 1.2.3.1/Q.551); +- a low level activating signal. A suitable activating signal is, for example, a sine-wave signal at a level in the range from $-33$ to $-40$ dBm0. Care must be taken in the choice of frequency + +and the filtering characteristics of the measuring apparatus in order that the activating signal does not significantly affect the accuracy of the crosstalk measurement. + +#### 3.1.4.1 Crosstalk measured with analogue test signal + +###### 3.1.4.1.1 Far-end and near-end crosstalk + +A sine-wave test signal at the reference frequency of 1020 Hz and at a level of 0 dBm0, applied to an analogue input interface, should not produce a level exceeding -73 dBm0 for Near-End Crosstalk (NEXT) or -73 dBm0 for Far-End Crosstalk (FEXT), at the output of any other half connection. (See Figure 6.) + +![Diagram of Figure 6/Q.553 showing crosstalk measurement between different input connections.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram illustrates a measurement setup for crosstalk between different input connections. It is divided into 'Analogue' and 'Digital' sections by a vertical dashed line. On the analogue side, there are three input sources: an 'Activating signal' (represented by a sine wave symbol), a 'Test signal' at '0 dBm0' (also a sine wave symbol), and a 'NEXT' measurement point (represented by a meter symbol). These signals enter three separate half-connections, each containing an A/D converter (labeled 'A' and 'D'). On the digital side, the outputs of these converters are shown. The top output is labeled 'FEXT' and is connected to a meter. The middle output is a dashed line. The bottom output is connected to a 'Quiet code' block. A curved arrow indicates crosstalk from the middle input connection to the top output connection. The diagram is labeled 'T1515730-94'. + +Diagram of Figure 6/Q.553 showing crosstalk measurement between different input connections. + +Figure 6/Q.553 – Measurement with analogue test signal between different input connections of half connections + +##### 3.1.4.1.2 Go-to-return crosstalk + +A sine-wave test signal at any frequency in the range 300 to 3400 Hz and at a level of 0 dBm0, applied to the analogue interface of an input connection, should not produce a level exceeding -66 dBm0 at the analogue output of the same half connection. See Figure 7. + +![Diagram of Figure 7/Q.553 showing crosstalk measurement between go and return directions of the same half connection.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +The diagram illustrates a measurement setup for go-to-return crosstalk. It is divided into 'Analogue' and 'Digital' sections by a vertical dashed line. On the analogue side, there are two input sources: a 'Test signal' at '0 dBm0' (represented by a sine wave symbol) and a 'Go-to-return crosstalk' measurement point (represented by a meter symbol). These signals enter two separate half-connections, each containing an A/D converter (labeled 'A' and 'D'). On the digital side, the outputs of these converters are shown. The top output is a dashed line. The bottom output is connected to a 'Quiet code' block. A curved arrow indicates crosstalk from the top input connection to the bottom output connection of the same half connection. The diagram is labeled 'T1515740-94'. + +Diagram of Figure 7/Q.553 showing crosstalk measurement between go and return directions of the same half connection. + +Figure 7/Q.553 – Measurement with analogue test signals between go and return directions of the same half connection + +#### 3.1.4.2 Crosstalk measured with digital test signal + +###### 3.1.4.2.1 Far-end and near-end crosstalk + +A digitally simulated sine-wave test signal at the reference frequency of 1020 Hz and at a level of 0 dBm0, applied to an exchange test point $T_i$ , should not produce a level exceeding $-70$ dBm0 for Near-End Crosstalk (NEXT) or $-73$ dBm0 for Far-End Crosstalk (FEXT), at the output of any other half connection. (See Figure 8.) + +![Figure 8: Measurement with digital test signal between different output connections of half connections. The diagram shows three half-connections between Analogue and Digital domains. The top connection has an 'Activating signal' (sine wave) entering the Analogue side and a 'NEXT' (Near-End Crosstalk) measurement point on the Digital side. The middle connection has a 'Test signal 0 dBm0' entering the Digital side and a 'Z_T' (impedance) measurement point on the Analogue side. The bottom connection has a 'Quiet code' entering the Digital side and a 'FEXT' (Far-End Crosstalk) measurement point on the Analogue side. Each connection contains an A/D converter. A dashed vertical line separates the Analogue and Digital domains. The text 'T1515750-94' is at the bottom right.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 8 shows a measurement setup for crosstalk between different output connections of half connections. It consists of three half-connections. The top connection has an activating signal (sine wave) entering the Analogue side and a NEXT (Near-End Crosstalk) measurement point on the Digital side. The middle connection has a test signal 0 dBm0 entering the Digital side and a ZT (impedance) measurement point on the Analogue side. The bottom connection has a quiet code entering the Digital side and a FEXT (Far-End Crosstalk) measurement point on the Analogue side. Each connection contains an A/D converter. A dashed vertical line separates the Analogue and Digital domains. The text 'T1515750-94' is at the bottom right. + +Figure 8: Measurement with digital test signal between different output connections of half connections. The diagram shows three half-connections between Analogue and Digital domains. The top connection has an 'Activating signal' (sine wave) entering the Analogue side and a 'NEXT' (Near-End Crosstalk) measurement point on the Digital side. The middle connection has a 'Test signal 0 dBm0' entering the Digital side and a 'Z\_T' (impedance) measurement point on the Analogue side. The bottom connection has a 'Quiet code' entering the Digital side and a 'FEXT' (Far-End Crosstalk) measurement point on the Analogue side. Each connection contains an A/D converter. A dashed vertical line separates the Analogue and Digital domains. The text 'T1515750-94' is at the bottom right. + +**Figure 8/Q.553 – Measurement with digital test signal between different output connections of half connections** + +##### 3.1.4.2.2 Go-to-return crosstalk + +A digitally simulated sine-wave test signal, at any frequency in the range 300 to 3400 Hz and at a level of 0 dBm0, applied to an exchange test point $T_i$ of an output connection, should not produce a crosstalk level exceeding $-66$ dBm0 at the exchange test point $T_o$ of the same half connection. (See Figure 9.) + +![Figure 9: Measurement with digital test signals between go and return directions of the same half connection. The diagram shows two half-connections between Analogue and Digital domains. The top connection has an 'Activating signal' (sine wave) entering the Analogue side and a 'Go-to-return crosstalk' measurement point on the Digital side. The bottom connection has a 'Test signal 0 dBm0' entering the Digital side and a 'Z_T' (impedance) measurement point on the Analogue side. Each connection contains an A/D converter. A dashed vertical line separates the Analogue and Digital domains. The text 'T1515760-94' is at the bottom right.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +Figure 9 shows a measurement setup for go-to-return crosstalk. It consists of two half-connections. The top connection has an activating signal (sine wave) entering the Analogue side and a Go-to-return crosstalk measurement point on the Digital side. The bottom connection has a test signal 0 dBm0 entering the Digital side and a ZT (impedance) measurement point on the Analogue side. Each connection contains an A/D converter. A dashed vertical line separates the Analogue and Digital domains. The text 'T1515760-94' is at the bottom right. + +Figure 9: Measurement with digital test signals between go and return directions of the same half connection. The diagram shows two half-connections between Analogue and Digital domains. The top connection has an 'Activating signal' (sine wave) entering the Analogue side and a 'Go-to-return crosstalk' measurement point on the Digital side. The bottom connection has a 'Test signal 0 dBm0' entering the Digital side and a 'Z\_T' (impedance) measurement point on the Analogue side. Each connection contains an A/D converter. A dashed vertical line separates the Analogue and Digital domains. The text 'T1515760-94' is at the bottom right. + +**Figure 9/Q.553 – Measurement with digital test signals between go and return directions of the same half connection** + +### 3.1.5 Total distortion including quantizing distortion + +With a sine-wave test signal at the reference frequency of 1020 Hz (see ITU-T Rec. O.132) applied to the analogue interface of an input connection, or with a digitally simulated sine-wave signal of the same characteristic applied to the exchange test point $T_i$ of an output connection, the signal-to-total distortion ratio, measured at the respective outputs of the half connection with a proper noise + +weighting (see Table 4/G.223) should lie above the limits shown in Figure 10 for signalling on separate wires and in Figure 11 for signalling on the speech wires. + +![Figure 10: Limits for signal-to-distortion ratio as a function of input level for input or output connection with signalling on separate wires. The graph shows a limit line with shaded area above it. The coordinates are: (-45 dBm0, 24 dB), (-40 dBm0, 29 dB), (-30 dBm0, 35 dB), and (0 dBm0, 35 dB).](af06598cfb31b517e79b50d74f72a0ca_img.jpg) + +| Input level (dBm0) | Signal-to-total-distortion ratio (dB) | +|--------------------|---------------------------------------| +| < -45 | 24 | +| -45 to -40 | 24 to 29 (linear) | +| -40 to -30 | 29 to 35 (linear) | +| -30 to 0 | 35 | + +Figure 10: Limits for signal-to-distortion ratio as a function of input level for input or output connection with signalling on separate wires. The graph shows a limit line with shaded area above it. The coordinates are: (-45 dBm0, 24 dB), (-40 dBm0, 29 dB), (-30 dBm0, 35 dB), and (0 dBm0, 35 dB). + +**Figure 10/Q.553 – Limits for signal-to-distortion ratio as a function of input level for input or output connection with signalling on separate wires** + +![Figure 11: Limits for signal-to-total distortion ratio as a function of input level for input or output connection with signalling on the speech wires. The graph shows a limit line with shaded area above it. The coordinates are: (-45 dBm0, 21.5 dB), (-40 dBm0, 26.5 dB), (-30 dBm0, 33.8 dB), (-20 dBm0, 35.0 dB), and (0 dBm0, 35.0 dB).](fed39b841ae2dce01088b84bfc1e2789_img.jpg) + +| Input level (dBm0) | Signal-to-total-distortion ratio (dB) | +|--------------------|---------------------------------------| +| < -45 | 21.5 | +| -45 to -40 | 21.5 to 26.5 (linear) | +| -40 to -30 | 26.5 to 33.8 (linear) | +| -30 to -20 | 33.8 to 35.0 (linear) | +| -20 to 0 | 35.0 | + +Figure 11: Limits for signal-to-total distortion ratio as a function of input level for input or output connection with signalling on the speech wires. The graph shows a limit line with shaded area above it. The coordinates are: (-45 dBm0, 21.5 dB), (-40 dBm0, 26.5 dB), (-30 dBm0, 33.8 dB), (-20 dBm0, 35.0 dB), and (0 dBm0, 35.0 dB). + +**Figure 11/Q.553 – Limits for signal-to-total distortion ratio as a function of input level for input or output connection with signalling on the speech wires** + +The values of Figure 11 include the limits for the coding process given in Figure 12/G.712 and the allowance for the noise contributed via signalling circuits from the exchange power supply and other analogue sources which is limited to $-(67 + 3)$ dBm0p = $-70$ dBm0p for one 4-wire analogue interface by clause 3/G.123. + +### 3.1.6 Discrimination against out-of-band signals applied to the input interface + +(Applicable only to input connections.) + +#### 3.1.6.1 Input signals above 4.6 kHz + +With any sine-wave signal in the range from 4.6 kHz to 72 kHz applied to the analogue interface of an input connection at a level of $-25$ dBm0, the level of any image frequency measured at the exchange test point $T_0$ of the input connection should be at least 25 dB below the level of the test signal. This value may need to be more stringent to meet the overall requirement. + +#### 3.1.6.2 Overall requirement + +Under the most adverse conditions encountered in a national network, the half connection should not contribute more than 100 pW0p of additional noise in the band 10 Hz to 4 kHz at the output of the input connection, as a result of the presence of out-of-band signals at the input port of the input connection. + +### 3.1.7 Spurious out-of-band signals received at the output interface + +(Applicable only to an output connection.) + +#### 3.1.7.1 Level of individual components + +With a digitally simulated sine-wave test signal in the frequency range 300 to 3400 Hz and at a level of 0 dBm0 applied to the exchange test point $T_i$ of a half connection, the level of spurious out-of-band image signals measured selectively at the analogue interface of the output connection should be lower than $-25$ dBm0. This value may need to be more stringent to meet the overall requirement. + +#### 3.1.7.2 Overall requirement + +Spurious out-of-band signals should not give rise to unacceptable interference in the equipment connected to the digital exchange. In particular, the intelligible and unintelligible crosstalk in a connected FDM channel should not exceed a level of $-65$ dBm0 as a consequence of the spurious out-of-band signals at the half connection. + +## 3.2 Characteristics for interface $C_{11}$ + +### 3.2.1 Nominal value of transmission loss + +According to the relative levels defined in 2.2.1, the nominal transmission losses of a half connection with a $C_{11}$ interface are: + +- input connection: $R - A_R$ ; +- output connection: $-S - A_S$ . + +See 2.2.1 for definitions for $R$ , $S$ , $A_R$ and $A_S$ . + +## 3.3 Characteristics for interface $C_{12}$ + +### 3.3.1 Nominal value of transmission loss + +According to the relative levels defined in 2.3.1, the nominal transmission losses of a half connection with a $C_{12}$ interface are: + +- input connection: $R - A_R$ ; +- output connection: $-S - A_S$ . + +See 2.2.1 for definitions for $R$ , $S$ , $A_R$ and $A_S$ . + +## 3.4 Characteristics for interface $C_{13}$ + +### 3.4.1 Nominal value of transmission loss + +According to the relative levels defined in 2.4.1, the nominal transmission losses of a half connection with a $C_{13}$ interface are: + +- input connection: $-3.5$ dB; +- output connection: $3.5$ dB. + +Different levels at the switching stages and transmission loss between interface C13 and the switching stages can require adjusting these losses. + + + + + +# 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 | + +\*21584\* \ No newline at end of file diff --git a/marked/Q/T-REC-Q.554-199611-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.554-199611-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..597350198bf183a462cef91611cc21dc746957d4 --- /dev/null +++ b/marked/Q/T-REC-Q.554-199611-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.606-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.606-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.606-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.606-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.606-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..934219a44ebc4e7739908be02587d3ce833d7888 --- /dev/null +++ b/marked/Q/T-REC-Q.606-198811-I_PDF-E/raw.md @@ -0,0 +1,126 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.606** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES** + +**ITU-T Recommendation Q.606** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation Q.606 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. + +## **6 LOGIC PROCEDURES** + +The logic procedures are prepared as: + +- a) logic procedures for incoming signalling systems, +- b) interworking logic procedures, +- c) logic procedures for outgoing signalling systems. + +A state overview diagram is provided with each procedure. The state overview diagram: + +- lists the states for the logic, +- provides a sheet reference for each state, and +- shows permitted transitions between states. + +In addition, notes and timers are provided. + +### **6.1      *Incoming signalling system logic procedures*** + +In specifying the logic procedures the following elements are used: + +- a) inputs in the form of forward signals, +- b) outputs in the form of FITEs, +- c) inputs in the form of BITEs, +- d) outputs in the form of backward signals, +- e) time supervision arrangements, +- f) routing and switching aspects that are needed for interworking (SPITEs). + +Incoming signalling system logic procedures are provided for: + +- Signalling System No. 4 in Recommendation Q.611, +- Signalling System No. 5 in Recommendation Q.612, +- Signalling System No. 6 in Recommendation Q.613, +- Signalling System No. 7 (TUP) in Recommendation Q.614, +- Signalling System R1 in Recommendation Q.615, +- Signalling System R2 in Recommendation Q.616. + +In specifying the logic procedures the following elements are used: + +- a) inputs in the form of FITEs from the incoming signalling system, +- b) outputs in the form of FITEs to the outgoing signalling system, +- c) inputs in the form of BITEs from the outgoing signalling system, +- d) outputs in the form of BITEs to the incoming signalling system, +- e) routing and switching aspects that are needed for interworking (SPITEs). + +Interworking logic procedures can be provided for every possible combination of CCITT Signalling Systems. + +The following interworking combinations are provided: + +- Signalling System No. 4 to R2 in Recommendation Q.634, +- Signalling System No. 5 to No. 6 in Recommendation Q.642, +- Signalling System No. 5 to No. 7 (TUP) in Recommendation Q.643, +- Signalling System No. 5 to R1 in Recommendation Q.644, +- Signalling System No. 5 to R2 in Recommendation Q.645, +- Signalling System No. 6 to No. 5 in Recommendation Q.652, +- Signalling System No. 6 to No. 7 (TUP) in Recommendation Q.653, +- Signalling System No. 6 to R1 in Recommendation Q.654, +- Signalling System No. 6 to R2 in Recommendation Q.655, +- Signalling System No. 7 (TUP) to No. 5 in Recommendation Q.662, +- Signalling System No. 7 (TUP) to No. 6 in Recommendation Q.663, +- Signalling System No. 7 (TUP) to No. 7 in Recommendation Q.664, +- Signalling System No. 7 (TUP) to R1 in Recommendation Q.665, +- Signalling System No. 7 (TUP) to R2 in Recommendation Q.666, +- Signalling System R1 to No. 5 in Recommendation Q.671, +- Signalling System R1 to No. 6 in Recommendation Q.672, +- Signalling System R1 to No. 7 (TUP) in Recommendation Q.673, +- Signalling System R1 to R2 in Recommendation Q.674, +- Signalling System R2 to No. 4 in Recommendation Q.681, +- Signalling System R2 to No. 5 in Recommendation Q.682, +- Signalling System R2 to No. 6 in Recommendation Q.683, +- Signalling System R2 to No. 7 (TUP) in Recommendation Q.684, +- Signalling System R2 to R1 in Recommendation Q.685. + +### 6.3 *Outgoing signalling system logic procedures* + +In specifying the logic procedures, the following elements are used: + +- a) inputs in the form of FITEs, +- b) outputs in the form of forward signals, +- c) inputs in the form of backward signals, +- d) outputs in the form of BITEs, +- e) time supervision arrangements, +- f) routing and switching aspects that are needed for interworking (SPITEs). + +Outgoing logic procedures are provided for: + +- Signalling System No. 4 in Recommendation Q.621, +- Signalling System No. 5 in Recommendation Q.622, +- Signalling System No. 6 in Recommendation Q.623, +- Signalling System No. 7 (TUP) in Recommendation Q.624, +- Signalling System R1 in Recommendation Q.625, +- Signalling System R2 in Recommendation Q.626. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.607-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.607-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.607-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.607-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.607-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d270a6d7520b465e18a68db8051d95aa968cbaeb --- /dev/null +++ b/marked/Q/T-REC-Q.607-198811-I_PDF-E/raw.md @@ -0,0 +1,73 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.607** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**INTERWORKING OF SIGNALLING SYSTEMS - +INTERWORKING REQUIREMENTS FOR NEW +SIGNALLING SYSTEMS** + +**ITU-T Recommendation Q.607** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.607 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. + +## **7 INTERWORKING REQUIREMENTS FOR NEW SIGNALLING SYSTEMS** + +### **7.1 *Treatment of new signals in another signalling system*** + +In order to facilitate the interworking between new signalling systems and existing ones, it is desirable to elaborate rules to be taken into account when specifying the new signalling system(s). Since compatibility between all CCITT Signalling Systems must be ensured, any newly developed system has to meet the following requirements with regard to interworking: + +- a) new signalling systems should be capable of processing all interworking events specified for the existing signalling systems without losing or adding information elements. + +This is best achieved by the concept of transparency, whereby the signals of all existing systems have a unique translation into the new system and back again. In this way a tandem connection via an interposed link employing the new signalling system will neither add nor subtract from the information transfer that would otherwise have occurred had the new signalling system not been present; + +- b) newly developed systems should not lead to any modification to the specifications covering the present signalling systems except that the translation of new interworking events arising from the meanings of new signals in the new system will need to be defined for the existing signalling systems. + +In order that the new signals should cause the minimum loss or gain of information when interworking with existing signalling systems, any new signals should, if possible, not contain any information elements already existing. Hence it is better that these new signals convey only a single meaning rather than a multiple meaning as occurs in some existing systems (e.g. Signalling System R2 signal I-14 corresponds to FITE 8 which combines the elements of FITE 3 and FITE 5). Therefore, only one new information element will be associated with the new signal and only one new FITE or BITE will be needed. + +In some cases the new signal will be translated into a presently defined signal of an existing system and hence will cause the addition or, more often, the loss of information. In some cases, no electrical signal being available, all the information may be lost or a tone may need to be used. In the case of Signalling Systems R2, No. 6 and No. 7, some reserved signals exist within the capacity of these systems and such signals may be introduced to enhance the signalling system and provide an interworking capability. + +However it should be borne in mind that with such existing systems, it may not be easy or desirable to modify existing equipment, and even if such modification were possible, in the transitional period the interworking of existing and enhanced signalling equipment of the same system must also be considered. + +In view of the difficulties of interworking with existing signalling systems, new features of signals should only be introduced in a new system if there are good operational reasons for doing so. + +### **7.2 *Reserve for national use*** + +In practice, provision of appropriate spare signalling capacity in a new system reserved for national/regional use cannot be avoided. In such a case, precautions must be taken to prevent signals with an individual national meaning from entering the international network. + +One general objective of a new signalling system should be to meet also the national requirements in order to avoid national versions of a given signalling system as far as possible. + +### 7.3 *Unambiguous specifications* + +After a clear specification of a new feature to be included in a signalling system, the related signalling procedures should be specified in a unique and standard form. The same applies to the signals involved. + +The designation of signals of different signalling systems, which carry the same information, should be the same. + +### 7.4 *Escape codes* + +It is obvious that appropriate spare capacity should be provided in order to cope with future demands. One way of doing so is the provision of escape codes. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.608-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.608-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec927aa28872ab95f0a5b889515cd45616085677 --- /dev/null +++ b/marked/Q/T-REC-Q.608-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32842e55f1f7e5fae5b4d9e35bbd3dbc54ce125577b374e28bcca57790328a04 +size 7513 diff --git a/marked/Q/T-REC-Q.612-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg b/marked/Q/T-REC-Q.612-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d5a0934da269c5d74bc8c88b3e6f68e23361c5a --- /dev/null +++ b/marked/Q/T-REC-Q.612-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d3566afc08e74edf5aa557c6d99f18006aaaf8c53b2298cbc74d9b5b36d8b75 +size 168536 diff --git a/marked/Q/T-REC-Q.612-198811-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg b/marked/Q/T-REC-Q.612-198811-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..805e1052a40321ce392d4d81c49a66097abca3fc --- /dev/null +++ b/marked/Q/T-REC-Q.612-198811-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e67489da0ef53064983d66415632629c7b939ec39a2773c2c8b80c03e1f5578 +size 156092 diff --git a/marked/Q/T-REC-Q.612-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.612-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afaf297aa61f0493790604dde8d9d86e43ca7032 --- /dev/null +++ b/marked/Q/T-REC-Q.612-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90241b66e5220aa451d28476f4b15c1cf690e71bb698f6ab95b1937955743946 +size 155230 diff --git a/marked/Q/T-REC-Q.612-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.612-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.612-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.612-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg b/marked/Q/T-REC-Q.612-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f7f1fbf45a8804d6e2edabe1b7348794a14fe36 --- /dev/null +++ b/marked/Q/T-REC-Q.612-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9914d8a93460593b8d64e825e156cf10cc2f3e88765e91faf9e846b1278d1742 +size 159189 diff --git a/marked/Q/T-REC-Q.612-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.612-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b10e3483f42815c5041de1e22e294ab703cebb3d --- /dev/null +++ b/marked/Q/T-REC-Q.612-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec62c23cbd94143dd86b4033582627c848aa72f7a54c30ada657f83ce3f34d07 +size 42070 diff --git a/marked/Q/T-REC-Q.612-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.612-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..14c88d54280e72353ccca8d170d8cc25c8234d62 --- /dev/null +++ b/marked/Q/T-REC-Q.612-198811-I_PDF-E/raw.md @@ -0,0 +1,300 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.612** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR INCOMING +SIGNALLING SYSTEM No. 5** + +**ITU-T Recommendation Q.612** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.612 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 INCOMING SIGNALLING SYSTEM No. 5 + +![State overview diagram for incoming Signalling System No. 5. It shows 14 states (00-13) and their transitions. State 00 is Idle, leading to 01 (Wait for register activation), then 02 (Wait for register signal), 03 (Wait for next register signal), 04 (Wait for digit analysis), 05 (Wait for acknowledgement), 06 (Wait for next register signal), 07 (Wait for register deactivation), 08 (Wait for answer), 09 (Wait for acknowledgement), 10 (Answered), 11 (Wait for acknowledgement), 12 (Clear-back), and 13 (Wait for clear-forward). Transitions are shown as arrows between these states. CCITT - 48550 is noted at the bottom right.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +State overview diagram for incoming Signalling System No. 5. It shows 14 states (00-13) and their transitions. State 00 is Idle, leading to 01 (Wait for register activation), then 02 (Wait for register signal), 03 (Wait for next register signal), 04 (Wait for digit analysis), 05 (Wait for acknowledgement), 06 (Wait for next register signal), 07 (Wait for register deactivation), 08 (Wait for answer), 09 (Wait for acknowledgement), 10 (Answered), 11 (Wait for acknowledgement), 12 (Clear-back), and 13 (Wait for clear-forward). Transitions are shown as arrows between these states. CCITT - 48550 is noted at the bottom right. + +| State number | State description | Sheet reference | Running timers | +|--------------|--------------------------------|-----------------|----------------| +| 00 | Idle | 1,4 | | +| 01 | Wait for register activation | 1 | | +| 02 | Wait for register signal | 1 | $t_1+t_2$ | +| 03 | Wait for next register signal | 1 | $t_2$ | +| 04 | Wait for digit analysis | 2 | $t_2$ | +| 05 | Wait for acknowledgement | 2 | $t_3$ | +| 06 | Wait for next register signal | 3 | $t_2$ | +| 07 | Wait for register deactivation | 3 | | +| 08 | Wait for answer | 3 | | +| 09 | Wait for acknowledgement | 4 | $t_3$ | +| 10 | Answered | 4 | | +| 11 | Wait for acknowledgement | 4 | $t_3$ | +| 12 | Clear-back | 4 | | +| 13 | Wait for clear-forward | 2 | | + +FIGURE 1/Q.612 + +State overview diagram for incoming Signalling System No. 5 + +## Supervisory timers + +| | | +|-----------------|---------------------------------------------------------| +| $t_1 = 10-20$ s | Recommendation Q.141, § 2.1.3.1, e); Q.141, § 2.1.6, d) | +| $t_2 = 20-40$ s | Recommendation Q.156, § 3.6.2, b) | +| $t_3 = 10-20$ s | Recommendation Q.141, § 2.1.3.1, e) | + +## Procedures not shown + +The following procedures, not directly relevant to interworking, are not shown in the logic procedures. + +- $P_1$ - Procedure for timeout of receipt of busy flash acknowledgement signal +- $P_2$ - Procedure for timeout of receipt of answer acknowledgement signal +- $P_3$ - Procedure for timeout of receipt of clearback acknowledgement signal + +FIGURE 2/Q.612 + +Notes to incoming Signalling System N°. 5 + +![Flowchart for Incoming Signalling System No. 5 (Q.612). The process starts at '00 Idle', proceeds through 'Seizing', 'SPITE 1 Activate register function', and '01 Wait for register activation'. It then branches into 'SPITE 2 register function activated' and 'Clear-forward'. From 'SPITE 2', it goes to 'Proceed-to-send', which starts timers t1 (10-20 s) and t2 (20-40 s). It then enters '02 Wait for register signal'. From here, it can receive 'Register signal «KP2»' or 'Register signal «KP1»', which leads to 'Stop t1'. 'Clear-forward' leads to 'Stop t1'. 'τ1' leads to 'Stop t2'. Both 'Stop t1' and 'Stop t2' lead to '03 Wait for next register signal'. From '03', it can receive a 'Register signal'. If 'ST-signal' is 'No', it goes to 'SPITE 11'. If 'SPITE 11' is 'Yes', it goes to 'SPITE 3 Deactivate register function', then 'Release-guard', and back to '00 Idle'. If 'SPITE 11' is 'No', it loops back to '03'. If 'ST-signal' is 'Yes', it goes to 'Stop t2', then 'SPITE 35 Ignore further register signals', then 'SPITE 12 Perform digit analysis', and to connector '7'. 'Clear-forward' from 'Register signal' leads to 'Stop t2', then 'SPITE 3 Deactivate register function', then 'Release-guard', and back to '00 Idle'. 'τ2' leads to 'SPITE 3 Deactivate register function', then 'Busy-flash', then 'Start t3' (10-20 s), and to connector '8'. Various connectors (1, 2, 3, 4, 5, 6, 7, 8) are marked with subscripts 1 or 2. Connector reference numbers 00, 01, 02, 03, 1, 2, 3, 4, 5, 6, 7, 8 are listed on the left margin.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +Connector reference + +``` + +graph TD + Idle00_1((00 Idle)) --> Seizing[/Seizing/] + Seizing --> SPITE1[SPITE 1 +Activate register function] + SPITE1 --> Wait01((01 Wait for register activation)) + Wait01 --> SPITE2[SPITE 2 +register function activated] + Wait01 --> ClearForward1[/Clear-forward/] + ClearForward1 --> C3_1((3 1)) + SPITE2 --> ProceedToSend[/Proceed-to-send/] + ProceedToSend --> StartT1[/Start t1/] + StartT1 -.-> T1Range["t1 = 10-20 s"] + StartT1 --> StartT2[/Start t2/] + StartT2 -.-> T2Range["t2 = 20-40 s"] + StartT2 --> Wait02((02 Wait for register signal)) + Wait02 --> RegisterSignalKP2[/Register signal «KP2»/] + Wait02 --> RegisterSignalKP1[/Register signal «KP1»/] + Wait02 --> ClearForward2[/Clear-forward/] + Wait02 --> Tau1[/τ1/] + RegisterSignalKP2 --> StopT1_1[/Stop t1/] + RegisterSignalKP1 --> StopT1_1 + ClearForward2 --> StopT1_2[/Stop t1/] + StopT1_2 --> C2_1((2 1)) + Tau1 --> StopT2_1[/Stop t2/] + StopT2_1 --> C5_1((5 1)) + StopT1_1 --> Wait03((03 Wait for next register signal)) + StopT2_1 --> Wait03 + Wait03 --> RegisterSignal[/Register signal/] + RegisterSignal --> STSignal{ST-signal} + STSignal -- No --> SPITE11{SPITE 11} + SPITE11 -- No --> C1_1((1 1)) + SPITE11 -- Yes --> SPITE3_1[SPITE 3 +Deactivate register function] + SPITE3_1 --> ReleaseGuard[/Release-guard/] + ReleaseGuard --> Idle00_2((00 Idle)) + STSignal -- Yes --> StopT2_2[/Stop t2/] + StopT2_2 --> SPITE35[SPITE 35 +Ignore further register signals] + SPITE35 --> SPITE12[SPITE 12 +Perform digit analysis] + SPITE12 --> C7_2((7 2)) + RegisterSignal --> ClearForward3[/Clear-forward/] + ClearForward3 --> StopT2_3[/Stop t2/] + StopT2_3 --> SPITE3_2[SPITE 3 +Deactivate register function] + SPITE3_2 --> ReleaseGuard + RegisterSignal --> Tau2[/τ2/] + Tau2 --> SPITE3_3[SPITE 3 +Deactivate register function] + SPITE3_3 --> BusyFlash[/Busy-flash/] + BusyFlash --> StartT3[/Start t3/] + StartT3 -.-> T3Range["t3 = 10-20 s"] + StartT3 --> C8_2((8 2)) + +``` + +00 Idle + +Seizing + +SPITE 1 Activate register function + +01 Wait for register activation + +SPITE 2 register function activated + +Clear-forward + +3 1 + +Proceed-to-send + +Start t1 — t1 = 10-20 s + +Start t2 — t2 = 20-40 s + +02 Wait for register signal + +Register signal «KP2» + +Register signal «KP1» + +Clear-forward + +τ1 + +Stop t1 + +2 1 + +Stop t2 + +5 1 + +03 Wait for next register signal + +Register signal + +ST-signal + +No + +SPITE 11 + +No + +1 1 + +Yes + +SPITE 3 Deactivate register function + +Release-guard + +00 Idle + +Yes + +Stop t2 + +SPITE 35 Ignore further register signals + +SPITE 12 Perform digit analysis + +7 2 + +Clear-forward + +Stop t2 + +SPITE 3 Deactivate register function + +Release-guard + +00 Idle + +τ2 + +SPITE 3 Deactivate register function + +Busy-flash + +Start t3 — t3 = 10-20 s + +8 2 + +CCITT - 40730 + +Flowchart for Incoming Signalling System No. 5 (Q.612). The process starts at '00 Idle', proceeds through 'Seizing', 'SPITE 1 Activate register function', and '01 Wait for register activation'. It then branches into 'SPITE 2 register function activated' and 'Clear-forward'. From 'SPITE 2', it goes to 'Proceed-to-send', which starts timers t1 (10-20 s) and t2 (20-40 s). It then enters '02 Wait for register signal'. From here, it can receive 'Register signal «KP2»' or 'Register signal «KP1»', which leads to 'Stop t1'. 'Clear-forward' leads to 'Stop t1'. 'τ1' leads to 'Stop t2'. Both 'Stop t1' and 'Stop t2' lead to '03 Wait for next register signal'. From '03', it can receive a 'Register signal'. If 'ST-signal' is 'No', it goes to 'SPITE 11'. If 'SPITE 11' is 'Yes', it goes to 'SPITE 3 Deactivate register function', then 'Release-guard', and back to '00 Idle'. If 'SPITE 11' is 'No', it loops back to '03'. If 'ST-signal' is 'Yes', it goes to 'Stop t2', then 'SPITE 35 Ignore further register signals', then 'SPITE 12 Perform digit analysis', and to connector '7'. 'Clear-forward' from 'Register signal' leads to 'Stop t2', then 'SPITE 3 Deactivate register function', then 'Release-guard', and back to '00 Idle'. 'τ2' leads to 'SPITE 3 Deactivate register function', then 'Busy-flash', then 'Start t3' (10-20 s), and to connector '8'. Various connectors (1, 2, 3, 4, 5, 6, 7, 8) are marked with subscripts 1 or 2. Connector reference numbers 00, 01, 02, 03, 1, 2, 3, 4, 5, 6, 7, 8 are listed on the left margin. + +FIGURE 3/Q.612 (Sheet 1 of 4) +Incoming Signalling System No. 5 + +Connector reference + +![Flowchart for Incoming Signalling System No. 5 (Figure 3/Q.612 Sheet 2 of 4). The diagram shows two main entry points, 7 and 8, leading to state machines 04 and 05 respectively. State machine 04 handles digit analysis, while state machine 05 handles acknowledgement. Both include various processing steps like SPITE, FITE, and signal handling, with connectors 1 through 13 indicating links to other parts of the system.](690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg) + +The flowchart illustrates the logic for Incoming Signalling System No. 5. It begins with two entry points: connector 7 (labeled 1, 2) and connector 8 (labeled 1). + - **State Machine 04 (Wait for digit analysis):** This path starts at connector 7. It branches into several processing blocks: SPITE 14 (Routing information), SPITE 13, SPITEs 15, 16, 17, SPITEs 18, 19, Register signal, Clear-forward, and $\tau_2$ . SPITE 14 leads to 'Activate inter-working', which then leads to FITE 1. FITE 1 leads to a decision 'Any more digits?'. If 'Yes', it loops back to 'Activate inter-working'. If 'No', it leads to SPITE 23. SPITE 23 leads to a decision 'Which Z-digit?'. If 'Yes', it leads to connector 12 (labeled 3). If 'No', it leads to a horizontal bus with FITE 9, FITE 10, FITE 11, FITE 12, FITE 13, and FITE 17. This bus leads to a decision 'ST received?'. If 'Yes', it leads to connector 11 (labeled 3). If 'No', it leads to connector 10 (labeled 3). SPITE 13 leads to connector 1 (labeled 1). SPITEs 15, 16, 17 lead to 'Stop $t_2$ ', which then leads to connector 5 (labeled 1). SPITEs 18, 19 lead to 'Stop $t_2$ ', which then leads to connector 9 (labeled 2). Register signal leads to a decision 'ST-signal?'. If 'No', it leads to connector 2 (labeled 1). If 'Yes', it leads to 'Stop $t_2$ ', which then leads to connector 7 (labeled 2). Clear-forward leads to connector 2 (labeled 1). $\tau_2$ leads to connector 5 (labeled 1). + - **State Machine 05 (Wait for acknowledgement):** This path starts at connector 8. It branches into Acknowledgement, Clear-forward, and $\tau_3$ . Acknowledgement leads to 'Stop $t_3$ ', which then leads to connector 9 (labeled 2, 3). 'Stop $t_3$ ' leads to connector 13 (labeled 13), which leads to 'Wait for clear-forward', which then leads to Clear-forward, which leads to connector 4 (labeled 1). Clear-forward leads to 'Stop $t_3$ ', which then leads to connector 4 (labeled 1). $\tau_3$ leads to connector P1 (labeled 1), which is associated with 'Procedures for time-out routine'. + - **Connector References:** A vertical list on the left side provides connector references for various points in the flowchart: 7, 8; 1, 2, 5; 5, 9; 9, 7, 4; 12; 10, 11. + +Flowchart for Incoming Signalling System No. 5 (Figure 3/Q.612 Sheet 2 of 4). The diagram shows two main entry points, 7 and 8, leading to state machines 04 and 05 respectively. State machine 04 handles digit analysis, while state machine 05 handles acknowledgement. Both include various processing steps like SPITE, FITE, and signal handling, with connectors 1 through 13 indicating links to other parts of the system. + +CCITT - 40740 + +FIGURE 3/Q.612 (Sheet 2 of 4) + Incoming Signalling System No. 5 + +![Flowchart for Incoming Signalling System No. 5, Figure 3/Q.612 (Sheet 3 of 4). The diagram shows a sequence of operations starting from connector 10, through various signal processing steps like 'Wait for next register signal', 'Register signal', 'SPITE 24', 'FITE 1', 'ST signal', 'Stop t2', 'SPITE 35', 'Wait for register deactivation', 'BITE 27', 'BITE 8', 'BITE 28', 'Clear forward', 'BITE 30', 'SPITE 4a', 'SPITE 4', 'SPITE 3', 'Wait for answer', 'BITE 22', 'BITE 8', 'Forward transfer', 'Clear-forward', 'Answer', 'Start t3', and ending at connector 17. Connector references are provided on the left margin.](191a4a245a7d36d03be9a990d0f758f5_img.jpg) + +The flowchart illustrates the signaling process for Incoming Signalling System No. 5. It begins at connector 10 (labeled 2,3) and proceeds through a series of logical and functional blocks. Key components include: + + +- 06/ Wait for next register signal**: Initial wait state. +- Register signal**: Input signal processing. +- SPITE 24**: Decision point for register signal handling. +- FITE 1**: Filter/Interface block. +- ST signal**: State transition signal. +- Stop t2**: Timer control block. +- SPITE 35**: Ignore further register signals. +- 07/ Wait for register deactivation**: Second wait state. +- BITE 27, BITE 8, BITE 28, Clear forward, BITE 30**: Parallel processing branches for signal routing and monitoring. +- SPITE 4a**: Speech path setup monitoring. +- SPITE 4**: Set up speech condition. +- SPITE 3**: Deactivate register function. +- 08/ Wait for answer**: Final wait state before answer. +- BITE 22, BITE 8, Forward transfer, Clear-forward**: Parallel processing branches for answer handling. +- Answer**: Output signal. +- Start t3**: Timer control block with duration t3 = 10 - 20 s. +- Final connector 17 (labeled 4). + + Connector references on the left margin include: 10, 12, 13, 14, 5, 11, 13, 11, 14, 5, 15, 3, 16, 19, 6, 15, 17. + +Flowchart for Incoming Signalling System No. 5, Figure 3/Q.612 (Sheet 3 of 4). The diagram shows a sequence of operations starting from connector 10, through various signal processing steps like 'Wait for next register signal', 'Register signal', 'SPITE 24', 'FITE 1', 'ST signal', 'Stop t2', 'SPITE 35', 'Wait for register deactivation', 'BITE 27', 'BITE 8', 'BITE 28', 'Clear forward', 'BITE 30', 'SPITE 4a', 'SPITE 4', 'SPITE 3', 'Wait for answer', 'BITE 22', 'BITE 8', 'Forward transfer', 'Clear-forward', 'Answer', 'Start t3', and ending at connector 17. Connector references are provided on the left margin. + +CCITT-40 751 + +FIGURE 3/Q.612 (Sheet 3 of 4) + +## Incoming Signalling System No. 5 + +![Flowchart for Incoming Signalling System No. 5, Figure 3/Q.612 (Sheet 4 of 4).](1956f44611abd5c3c41049836aa78ad8_img.jpg) + +The flowchart illustrates the signaling process for Incoming Signalling System No. 5. It begins at connector 17 (3, 4) leading to state 09 'Wait for acknowledgement'. From here, four paths emerge: 'Acknowledgement' leading to 'Stop t3' and then to connector 18 (4); 'Clear-forward' leading to 'Stop t3' and then to connector 19 (4); 'BITE 25' leading to connector 17 (4); and a timeout path $\bar{t}_3$ leading to connector P2 (4), which is part of 'Procedures for time-out routine'. From connector 18 (4), the path goes to decision 'BITE 25 received'. If 'Yes', it goes to connector 20 (4). If 'No', it goes to connector 18 (4) and loops back to state 09. From connector 20 (4), the path goes to state 10 'Answered'. From state 10, three paths emerge: 'Clear-forward' leading to connector 19 (3, 4 (3x)) and then to state FITE 22; 'BITE 25' leading to connector 20 (4) and then to state 'Clear-back'; and 'Forward-transfer' leading to state FITE 23 and then to connector 18 (4). From state FITE 22, the path goes to state SPITE 8 'Release all equipment', then to state 'Release-guard', and finally to state 00 'Idle'. From state 'Clear-back', the path goes to state 'Start t3' (with $t_3 = 10-20\text{ s}$ ), then to connector 21 (4), and then to state 11 'Wait for acknowledgement'. From state 11, four paths emerge: 'Acknowledgement' leading to 'Stop t3' and then to connector 19 (4); 'Clear-forward' leading to 'Stop t3' and then to connector 19 (4); 'BITE 22' leading to connector 21 (4); and a timeout path $\bar{t}_3$ leading to connector P3 (4), which is part of 'Procedures for time-out routine'. From connector 21 (4), the path goes to decision 'BITE 22 received'. If 'Yes', it goes to connector 19 (4). If 'No', it goes to connector 22 (4) and then to state 12 'Clear-back'. From state 12, three paths emerge: 'BITE 22' leading to connector 16 (3) and then to connector 16 (19); 'Forward-transfer' leading to state FITE 23 and then to connector 22 (4); and 'Clear-forward' leading to connector 19 (4). The text 'CCITT - 40760' is located at the bottom right of the diagram. + +Flowchart for Incoming Signalling System No. 5, Figure 3/Q.612 (Sheet 4 of 4). + +FIGURE 3/Q.612 (Sheet 4 of 4) +Incoming Signalling System No. 5 \ No newline at end of file diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bc42d5fac1babcf2a7551e859e2cafd1dce1100 --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b16f62c24c6a0b6f772cd2e2a84dcc20803e977e510588bfc58d1b20218369 +size 117136 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf8d7a324424fb839ea5e03c8078b5b0ea096156 --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8ece7dc0eaf7611f5d186cedd01598e59d3f7ac5c13ce4d1d78d34eb67fff1f +size 133260 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.613-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.613-198811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48a13e6afb3a8006d335677830bbe0f73b24eac3 --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d09c7b8592e03de5986b9a6e5510dae4b7a841f6627e12147f910ef5d004397 +size 149079 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..431f214612b7fd44ef376a8a30d5acb1d7ab95ce --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:131917fc9a7c6548c78727d62376a2c982e439e555502220e62ba32901a40352 +size 186901 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a9907e9cc730b9f66f967dc8199ed80459d0e16 --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:265bf68a398caf86136ff5bfbf5ec234f6be9f11d2d0330e7e0690aa7de98972 +size 49792 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac7c50fec8d1955fe26183fe9e0cddadb171a68a --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90f7bf5214da00274a64fc314f918ea15c3443655fc203546fce4a69b6798776 +size 151523 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77bb1f83b7d8aa6088bdb308b13d8aab4ba770a6 --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d3af1a4bd0b7e0da121874aac18546c9c54b73dee66df9ccbf3e4748522d4aa +size 136337 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4570733ddcd769140cde94554da22cc70c69344a --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c633fb436c13ee3bb46633dfb3254f0a565e6d66a4e73f08405b014e9b523e0 +size 171090 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/Q/T-REC-Q.613-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..115612f3fb7a5e3d8459b1987a01c054719dac69 --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef91c933056c55b54a66982f97067e52b32789ef47d2589c21c1378e67ab916d +size 141993 diff --git a/marked/Q/T-REC-Q.613-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.613-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..11b0c64bc5b74b7933932012680a13ab190d0320 --- /dev/null +++ b/marked/Q/T-REC-Q.613-198811-I_PDF-E/raw.md @@ -0,0 +1,785 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.613** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR INCOMING +SIGNALLING SYSTEM No. 6** + +**ITU-T Recommendation Q.613** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.613 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 INCOMING SIGNALLING SYSTEM No. 6 + +![State transition diagram for incoming Signalling System No. 6. States are numbered 00 to 18. Transitions include: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, 05 to 06, 06 to 07, 07 to 08, 08 to 09, 09 to 10, 10 to 18, 11 to 12, 12 to 13, 13 to 14, 14 to 15, 15 to 16, 16 to 17, 17 to 00. There are also diagonal transitions from 01 to 04, 02 to 05, 03 to 06, 04 to 07, 05 to 08, 06 to 09, 07 to 10, 08 to 11, 09 to 12, 10 to 13, 11 to 14, 12 to 15, 13 to 16, 14 to 17, 15 to 00, 16 to 01, 17 to 02, 18 to 00. CCITT - 48560 is noted at the bottom right.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +State transition diagram for incoming Signalling System No. 6. States are numbered 00 to 18. Transitions include: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, 05 to 06, 06 to 07, 07 to 08, 08 to 09, 09 to 10, 10 to 18, 11 to 12, 12 to 13, 13 to 14, 14 to 15, 15 to 16, 16 to 17, 17 to 00. There are also diagonal transitions from 01 to 04, 02 to 05, 03 to 06, 04 to 07, 05 to 08, 06 to 09, 07 to 10, 08 to 11, 09 to 12, 10 to 13, 11 to 14, 12 to 15, 13 to 16, 14 to 17, 15 to 00, 16 to 01, 17 to 02, 18 to 00. CCITT - 48560 is noted at the bottom right. + +| State number | State description | Sheet reference | Timers running | +|--------------|--------------------------------------------------------|-----------------|---------------------------------------------------| +| 00 | Idle | 1, 8 | | +| 01 | Wait for further digits | 1 | t 1 , t 2 | +| 02 | Wait for digit analysis | 3 | t 1 , t 2 or t 3 | +| 03 | Wait for continuity check (COT) | 4 | t 1 , t 2 or t 3 | +| 04 | Wait for further digits (COT received) | 2 | t 2 | +| 05 | Wait for digit analysis (COT received) | 2 | t 2 or t 3 | +| 06 | Wait for address complete (COT received) | 5 | t 2 or t 3 | +| 07 | Wait for register deactivation | 5 | | +| 08 | Address complete – Wait for answer | 7 | | +| 09 | Address complete, subscriber free –
Wait for answer | 7 | | +| 10 | Call unsuccessful – wait for clear-forward | 6 | t 4 | +| 11 | Answered | 7 | | +| 12 | Clear-back 1 | 7 | | +| 13 | Reanswer 1 | 7 | | +| 14 | Clear-back 2 | 8 | | +| 15 | Reanswer 2 | 8 | | +| 16 | Clear-back 3 | 8 | | +| 17 | Reanswer 3 | 8 | | +| 18 | Call failure – wait for clear-forward | 6 | t 4 , t 5 | + +FIGURE 1/Q.613 +State overview diagram for incoming Signalling System No. 6 + +## *Supervisory timers for incoming Signalling System No. 6* + +$t_1$ = 10-15 s      Recommendation Q.268, § 4.8.5.3, a) + $t_2$ = 15-20 s      Recommendation Q.261, § 4.1.6 + $t_3$ = 20-30 s      Recommendation Q.268, § 4.8.5.3, a) + $t_4$ = 4-15 s       Recommendation Q.268, § 4.8.5.3, b) + $t_5$ = 1 min      Recommendation Q.268, § 4.8.5.3, b) + +### *Procedures not shown* + +The following procedures, not directly relevant to interworking, are not shown in the logic procedures: + +- Dual seizure, +- Blocking and unblocking sequences, +- Unreasonable sequences, +- Confusion and message refusal signals, +- Reset circuit/band procedures, +- Test call procedures, +- Out of service. + +## *Signal abbreviations used* + +The signal abbreviations used correspond to those of the Signalling System No. 6 specifications unless otherwise indicated on the same sheet. + +#### FIGURE 2/Q.613 + +## **Notes to incoming Signalling System No. 6** + +![](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +Connector reference + +``` + +graph TD + Idle00_1([00 Idle]) --> IAM[/IAM/] + IAM --> StoreIAM[Store IAM] + StoreIAM --> SPITE1[SPITE 1 +Activate register function] + SPITE1 --> SPITE32[SPITE 32 +Insert check loop] + SPITE32 --> Startt1[Start t1] + Startt1 -- "t1 = 10-15 s" --> STreceived{ST received} + STreceived -- Yes --> Startt3[Start t3] + STreceived -- No --> Startt2[Start t2] + Startt2 -- "t2 = 15-20 s" --> SPITE11{SPITE 11} + SPITE11 -- Yes --> SPITE12[SPITE 12 +Perform digit analysis] + SPITE11 -- No --> Waitforfurtherdigits([01 Wait for further digits]) + Startt3 -- "t3 = 20-30 s" --> SPITE12 + Waitforfurtherdigits --> Junction(( )) + SPITE12 --> Junction + Junction --> SAM[/SAM/] + Junction --> COT[/COT/] + Junction --> CLF[/CLF/] + Junction --> T1bar[/t1 bar/] + Junction --> T2bar[/t2 bar/] + SAM --> Stopt2_1[Stop t2] + Stopt2_1 --> Connector1_1((1)) + COT --> Stopt1_2[Stop t1] + Stopt1_2 --> SPITE34_2[SPITE 34 +Remove check loop] + SPITE34_2 --> Connector3_2((3)) + CLF --> Stopt1_3[Stop t1] + Stopt1_3 --> Stopt2_3[Stop t2] + Stopt2_3 --> SPITE34_3[SPITE 34 +Remove check loop] + SPITE34_3 --> RLG[/RLG/] + RLG --> SPITE3_3[SPITE 3 +Deactivate register function] + SPITE3_3 --> Idle00_2([00 Idle]) + T1bar --> Stopt2_4[Stop t2] + Stopt2_4 --> CFL[/CFL/] + CFL --> SPITE34_4[SPITE 34 +Remove check loop] + SPITE34_4 --> SPITE3_4[SPITE 3 +Deactivate register function] + SPITE3_4 --> Connector5_6((5)) + T2bar --> Stopt1_5[Stop t1] + Stopt1_5 --> ADI[/ADI/] + +``` + +00 Idle + +IAM + +Store IAM + +SPITE 1 +Activate register function + +SPITE 32 +Insert check loop + +Start $t_1$ [ $t_1 = 10-15$ s + +1 + +ST received + +Yes + +No + +Start $t_2$ [ $t_2 = 15-20$ s + +Start $t_3$ [ $t_3 = 20-30$ s + +SPITE 11 + +Yes + +No + +SPITE 12 +Perform digit analysis + +10 + +01 +Wait for further digits + +2 + +3 + +4, 12, 11 + +SAM + +COT + +CLF + +$\bar{t}_1$ + +$\bar{t}_2$ + +Stop $t_2$ + +Stop $t_1$ + +Stop $t_1$ + +Stop $t_2$ + +Stop $t_2$ + +Stop $t_1$ + +1 + +SPITE 34 +Remove check loop + +3 + +6 + +2(2x) +5(2x) + +RLG + +SPITE 3 +Deactivate register function + +5 + +6 + +00 Idle + +CCITT - 40770 + +FIGURE 3/Q.613 (Sheet 1 of 8) +Incoming Signalling System No. 6 + +Connector reference + +![Flowchart for Incoming Signalling System No. 6. The diagram shows a sequence of operations starting from connector 3, through various processing steps like digit analysis and routing information handling, to various output connectors including 6, 5, 7, 9, and 8. It includes decision points for 'ST received' and 'SPITE' functions.](191a4a245a7d36d03be9a990d0f758f5_img.jpg) + +``` + +graph TD + Start((3)) -- "1 +2(2x)" --> Wait04([04 +Wait for further +digits, COT +received]) + Wait04 --> SAM1[SAM] + Wait04 --> CLF1[CLF] + Wait04 --> T2_1[T2] + SAM1 --> StopT2_1[Stop t2] + StopT2_1 --> STReceived1{ST +received} + STReceived1 -- Yes --> StartT3_1[Start t3] + STReceived1 -- No --> StartT2_2[Start t2] + StartT2_2 --> SPITE11{SPITE 11} + SPITE11 -- Yes --> SPITE12[SPITE 12 +Perform digit +analysis] + SPITE11 -- No --> Connector3_2((3 +2)) + StartT3_1 --> SPITE12 + SPITE12 --> Wait05([05 +Wait for +digit analysis, +COT received]) + Wait05 --> SAM2[SAM] + Wait05 --> CLF2[CLF] + Wait05 --> T2_2[T2] + Wait05 --> T3_1[T3] + Wait05 --> SPITE14[SPITE 14 +Routing +information] + Wait05 --> SPITE13[SPITE 13] + SPITE14 --> Connector7_4((7 +4)) + SPITE13 --> STReceived2{ST +received} + STReceived2 -- Yes --> StopT3_2[Stop t3] + StopT3_2 --> Connector9_2((9 +2)) + STReceived2 -- No --> Connector3_3((3 +2)) + StopT3_2 --> STReceived3{ST +received} + STReceived3 -- Yes --> StartT2_3[Start t2] + STReceived3 -- No --> StartT3_2[Start t3] + StartT2_3 --> Connector8_2((8 +2)) + StartT3_2 --> Connector8_2 + CLF2 --> StopT2_3[Stop t2] + StopT2_3 --> StopT3_3[Stop t3] + StopT3_3 --> Connector6_1((6 +1)) + T2_2 --> Connector9_3((9 +2)) + T3_1 --> Connector18_5((18 +5)) + Connector18_5 --> CFL[CFL] + CFL --> SPITE3_1[SPITE 3 +Deactivate +register function] + SPITE3_1 --> Connector5_6((5 +6)) + CLF1 --> StopT2_2[Stop t2] + StopT2_2 --> Connector6_1 + T2_1 --> ADI{ADI} + ADI --> SPITE3_2[SPITE 3 +Deactivate +register function] + SPITE3_2 --> Connector5_6 + SPITE3_2 --> Connector9_5((9 +5)) + SPITE3_2 --> ConnectorA_3((A +3)) + CCITT[CCITT - 40780] + +``` + +Flowchart for Incoming Signalling System No. 6. The diagram shows a sequence of operations starting from connector 3, through various processing steps like digit analysis and routing information handling, to various output connectors including 6, 5, 7, 9, and 8. It includes decision points for 'ST received' and 'SPITE' functions. + +FIGURE 3/Q.613 (Sheet 2 of 8) +Incoming Signalling System No. 6 + +Connector +reference + +2 + +A + +7, 11 + +10 + +4, 12, 12 + +11, 8 + +2 + +A + +![Flowchart for Incoming Signalling System No. 6. The process starts with 'Wait for digit analysis' (02) and branches into various SPITE functions (14, 13, SAM, COT, CLF, t1, t2, t3) leading to Stop or Start timers and subsequent SPITE functions (15, 16, 17, 18, 19) leading to UNN, SST, SEC, or CGC. It then proceeds to 'Deactivate register function' and a 'COT received' decision loop.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +``` + +graph TD + Entry2((2)) -- "1, 3" --> Wait02([02 +Wait for digit analysis]) + Wait02 --- Bus1[ ] + Bus1 --> SPITE14{{SPITE 14 +Routing +information}} + SPITE14 --> Exit7_4((7 4)) + + Bus1 --> SPITE13{{SPITE 13}} + SPITE13 --> ST_Rec1{ST +received} + ST_Rec1 -- No --> Exit10_1((10 1)) + ST_Rec1 -- Yes --> StopT3_1[Stop t3] + StopT3_1 --> Exit11_1((11 1)) + + Bus1 --> SAM{{SAM}} + SAM --> StopT2_1[Stop t2] + StopT2_1 --> ST_Rec2{ST + +``` + +Flowchart for Incoming Signalling System No. 6. The process starts with 'Wait for digit analysis' (02) and branches into various SPITE functions (14, 13, SAM, COT, CLF, t1, t2, t3) leading to Stop or Start timers and subsequent SPITE functions (15, 16, 17, 18, 19) leading to UNN, SST, SEC, or CGC. It then proceeds to 'Deactivate register function' and a 'COT received' decision loop. + +CCITT - 40790 + +FIGURE 3/Q.613 (Sheet 3 of 8) +**Incoming Signalling System No. 6** + +![Flowchart for Incoming Signalling System No. 6. The process starts at connector 7, proceeds through 'Activate relevant interworking' and 'Which CPCI' decision. It branches based on CPCI values (1-5, 10-12, 13) leading to various FITE blocks (9, 10, 11, 12, 13; 17, 18, 19) or a 'Test call procedure. No interworking' path. The main flow continues through FITE 1, 'Any more digits' decision, 'COT received' decision, and 'Wait for COT' or 'FITE 24' paths. It then reaches a parallel section with COT, SAM, CLF, t1, t2, and t3 paths, each with corresponding FITE and Stop/Start timer blocks. The flowchart concludes with 'SPITE 34 Remove check loop', 'Stop t1', 'ST received' decision, 'CCSS' decision, 'Start t2', 'Start t3', and a final 'FITE 1' and 'Any more digits' loop leading to connector 14.](2ee59e629035d641140e55f4d215b0d7_img.jpg) + +Connector Reference + +7 + +2, 3 (7) + +Activate relevant interworking + +Which CPCI + +1-5 + +10-12 + +13 + +FITEs 9, 10, 11, 12, 13 + +FITEs 17, 18, 19 + +P1 + +Test call procedure. No interworking + +FITE 1 + +Yes + +Any more digits + +No + +COT received + +Yes + +No + +14 (4) + +Wait for COT (03) + +FITE 24 + +13 (5) + +B (6) + +COT + +SAM + +CLF + +t1 + +t2 + +t3 + +FITE 24 + +Stop t2 + +FITE 22 + +Stop t3 + +Stop t3 + +FITE 22 + +11 (1) + +Stop t1 + +FITE 22 + +12 (1) + +CCITT - 40800 + +11 + +4 + +12 + +SPITE 34 Remove check loop + +Stop t1 + +13 (5) + +ST received + +Yes + +No + +Note + +CCSS + +Yes + +No + +Start t2 + +Start t3 + +FITE 1 + +Yes + +Any more digits + +No + +14 (4) + +13 + +14 + +Flowchart for Incoming Signalling System No. 6. The process starts at connector 7, proceeds through 'Activate relevant interworking' and 'Which CPCI' decision. It branches based on CPCI values (1-5, 10-12, 13) leading to various FITE blocks (9, 10, 11, 12, 13; 17, 18, 19) or a 'Test call procedure. No interworking' path. The main flow continues through FITE 1, 'Any more digits' decision, 'COT received' decision, and 'Wait for COT' or 'FITE 24' paths. It then reaches a parallel section with COT, SAM, CLF, t1, t2, and t3 paths, each with corresponding FITE and Stop/Start timer blocks. The flowchart concludes with 'SPITE 34 Remove check loop', 'Stop t1', 'ST received' decision, 'CCSS' decision, 'Start t2', 'Start t3', and a final 'FITE 1' and 'Any more digits' loop leading to connector 14. + +Note - Is outgoing link a common channel signalling system ? + +FIGURE 3/Q.613 (Sheet 4 of 8) +Incoming Signalling System No. 6 + +![SDL Flowchart for Incoming Signalling System No. 6, Sheet 5 of 8. The process starts from state 06 'Wait for address complete' (connector 13). It branches into nine parallel input paths: SAM, BITE 30, BITE 2, BITE 3, BITE 4, BITE 5, BITE 6, BITE 7, and CLF. The SAM path involves stopping t2, checking for ST received and CCSS, starting t2 or t3, and sending FITE 1. The BITE paths involve various tasks like ADC, ADN, ADX, AFC, AFN, AFX, stopping timers t2 and t3, and deactivating/setting up speech paths (SPITE 3/4). The CLF path sends FITE 22 and stops timers. Connectors lead to other sheets or parts of the diagram (e.g., 13, 28, 15, 16, 17, 6, B, 9, 18).](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Connector reference + +13 + +4(2x) +5(2x) + +(13) + +06 Wait for address complete + +SAM + +Stop $t_2$ + +BITE 30 + +SPITE 4A Speech path may be set up + +(13)5 + +BITE 2 + +ADC + +Stop $t_2$ + +Stop $t_3$ + +(28)6 + +BITE 3 + +ADN + +Stop $t_2$ + +Stop $t_3$ + +(15)6 + +SPITE 3 Deactivate register function + +Is speech path set up + +Yes + +No + +SPITE 4 Set up speech condition + +(16)7 + +BITE 4 + +ADX + +BITE 5 + +AFC + +Stop $t_2$ + +Stop $t_3$ + +SPITE 3 Deactivate register function + +Is speech path set up + +Yes + +No + +SPITE 4 Set up speech condition + +(17)7 + +BITE 6 + +AFN + +BITE 7 + +AFX + +CLF + +FITE 22 + +Stop $t_2$ + +Stop $t_3$ + +(6)1 + +(B)6 + +$\bar{t}_2$ + +FITE 22 + +(9)2 + +$\bar{t}_3$ + +FITE 22 + +(18)2 CCITT - 40812 + +ST received + +Yes + +No + +See Note, Sheet 4 + +CCSS + +Start $t_2$ + +Start $t_3$ + +FITE 1 + +Any more digits + +Yes + +No + +(13)5 + +15 + +6 + +28 + +B + +16, 17 +3, 9, 18 + +SDL Flowchart for Incoming Signalling System No. 6, Sheet 5 of 8. The process starts from state 06 'Wait for address complete' (connector 13). It branches into nine parallel input paths: SAM, BITE 30, BITE 2, BITE 3, BITE 4, BITE 5, BITE 6, BITE 7, and CLF. The SAM path involves stopping t2, checking for ST received and CCSS, starting t2 or t3, and sending FITE 1. The BITE paths involve various tasks like ADC, ADN, ADX, AFC, AFN, AFX, stopping timers t2 and t3, and deactivating/setting up speech paths (SPITE 3/4). The CLF path sends FITE 22 and stops timers. Connectors lead to other sheets or parts of the diagram (e.g., 13, 28, 15, 16, 17, 6, B, 9, 18). + +FIGURE 3/Q.613 (Sheet 5 of 8) + +### Incoming Signalling System No. 6 + +![Flowchart for Incoming Signalling System No. 6, Figure 3/Q.613 (Sheet 6 of 8).](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +The flowchart illustrates the logic for Incoming Signalling System No. 6. It begins with a connector reference 'B' and a list of input conditions: BITE 9 (SEC), BITE 10 (CGC), BITE 12 (NNC), BITE 14 (ADI), BITE 15 (UNN), BITE 16 (SSB), BITE 17 (LOS), BITE 19 (CFL), and BITE 20 (SST). These inputs feed into a decision block 'Is speech path set up'. If 'No', it proceeds to 'SPITE 5 Release speech conditions' and then 'Stop t2'. If 'Yes', it proceeds to 'SPITE 3 Deactivate register function'. From 'SPITE 3', the flow goes to connector '28' (labeled '07 Wait for register deactivation'). + +From connector '28', the flowchart branches based on BITE 27, BITE 10 (CGC), BITE 12 (NNC), BITE 19 (CFL), and CLF. BITE 27 leads to connector '15'. BITE 10 and BITE 12 lead to a decision 'Is speech path set up'. If 'No', it goes to 'SPITE 5 Release speech conditions' and then 'SPITE 3 Deactivate register function', leading to connector '5'. If 'Yes', it goes to 'Start t4'. BITE 19 (CFL) leads to connector '6'. CLF leads to 'FITE 22' and then connector '6'. + +From 'Start t4' (with a duration of t4 = 4 - 15 s), the flow goes to '10 Call unsuccessful wait for clear-forward'. From there, it branches based on CLF, $\bar{t}_4$ , and CFL. CLF leads to 'Stop t4' and then connector '19'. $\bar{t}_4$ leads to 'CFL' and then 'Start t5' (with a duration of t5 = 1 min.), leading to connector '20'. CFL leads to connector '19'. + +Another 'Start t4' block is shown, leading to '18 Call fail wait for clear-forward'. This block branches based on CLF, $\bar{t}_4$ , and $\bar{t}_5$ . CLF leads to 'Stop t4' and then 'Stop t5', leading to connector '19'. $\bar{t}_4$ leads to 'CFL' and then connector '20'. $\bar{t}_5$ leads to 'Stop t4' and then connector 'P2', which is labeled 'Out of service'. + +Other connectors and labels include '4, 5' at the top left, '28' at the top, '15', '19', '6', '20', '5', '6', '19', '20', '19', '20' at the bottom, and 'CCITT-t0822' at the bottom right. + +Flowchart for Incoming Signalling System No. 6, Figure 3/Q.613 (Sheet 6 of 8). + +FIGURE 3/Q.613 (Sheet 6 of 8) + +### Incoming Signalling System No. 6 + +Connector reference + +![State transition diagram for Incoming Signalling System No. 6. It shows three main states: 08 (Address complete, wait for answer), 09 (ADC sub. free W.F. answer), and 11 (Answered). Transitions are triggered by various signals like BITE 22, BITE 23, BITE 10, BITE 12, BITE 19, CLF, FOT, SPITE 5, and Clear-back. Each state has associated output actions such as ANC, ANN, CGC, NNC, CFL, FITE 22, FITE 23, RA 1, CB 1, and CB 2. Connector references are provided for many of the transitions.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +**State 08: Address complete, wait for answer** + +- Entry: Connector 16 (5, 7) +- Transitions: + - BITE 22 → ANC → Connector 27 (7) + - BITE 23 → ANN + - BITE 10 → CGC + - BITE 12 → NNC + - BITE 19 → CFL + - CLF → FITE 22 → Connector 19 (8) + - FOT → FITE 23 → Connector 16 (7) +- SPITE 5 Release speech condition (from CGC and NNC) → Connector 5 (6) + +**State 09: ADC sub. free W.F. answer** + +- Entry: Connector 17 (5, 7) +- Condition: Address complete, subscriber free, wait for answer +- Transitions: + - BITE 22 → ANC → Connector 27 (7(2x)) + - BITE 23 → ANN + - BITE 19 → CFL + - CLF → FITE 22 → Connector 19 (8) + - FOT → FITE 23 → Connector 17 (7) +- SPITE 5 Release speech condition (from CFL) → Connector 5 (6) + +**State 11: Answered** + +- Entry: Connector 27 (7(2x)) +- Transitions: + - BITE 25 → CB 1 → Connector 21 (7) + - CLF → FITE 22 → Connector 19 (8) + - FOT → FITE 23 → Connector 27 (7) + +**State 12: Clear-back** + +- Entry: Connector 21 (7(2x), 8) +- Transitions: + - BITE 24 → RA 1 → Connector 22 (7) + - CLF → FITE 22 → Connector 19 (8) + - FOT → FITE 23 → Connector 21 (7) +- RA 1 → Connector 22 (7) + +**State 13: Reanswer** + +- Entry: Connector 22 (7) +- Transitions: + - BITE 25 → CB 2 → Connector 23 (8) + - CLF → FITE 22 → Connector 19 (8) + - FOT → FITE 23 → Connector 22 (7) + +State transition diagram for Incoming Signalling System No. 6. It shows three main states: 08 (Address complete, wait for answer), 09 (ADC sub. free W.F. answer), and 11 (Answered). Transitions are triggered by various signals like BITE 22, BITE 23, BITE 10, BITE 12, BITE 19, CLF, FOT, SPITE 5, and Clear-back. Each state has associated output actions such as ANC, ANN, CGC, NNC, CFL, FITE 22, FITE 23, RA 1, CB 1, and CB 2. Connector references are provided for many of the transitions. + +FIGURE 3/Q.613 (Sheet 7 of 8) +Incoming Signalling System No. 6 + +CCITT - 40830 + +Connector reference + +![State transition diagram for Incoming Signalling System No. 6. The diagram shows a sequence of states and transitions between BITE, RA, CB, and FITE components, leading to an Idle state. Connector references are listed on the left side of the diagram.](007b053fe94a8348f75128a584503fd0_img.jpg) + +The diagram illustrates the state transitions for Incoming Signalling System No. 6. The states and transitions are as follows: + +- Initial State:** Connector reference 23. Transition to state **14 Clear-back 2** (Connector reference 7, 8). +- State 14 Clear-back 2:** Transitions to **BITE 24**, **CLF**, and **FOT**. + - BITE 24** leads to **RA 2**, which leads to state **15 Reanswer 2** (Connector reference 24, 19, 23). + - CLF** leads to **FITE 22**, which leads to state **19** (Connector reference 8). + - FOT** leads to **FITE 23**, which leads to state **23** (Connector reference 8). +- State 15 Reanswer 2:** Transitions to **BITE 25**, **CLF**, and **FOT**. + - BITE 25** leads to **CB 3**, which leads to state **16 Clear-back 3** (Connector reference 25, 19, 24). + - CLF** leads to **FITE 22**, which leads to state **19** (Connector reference 8). + - FOT** leads to **FITE 23**, which leads to state **24** (Connector reference 8). +- State 16 Clear-back 3:** Transitions to **BITE 24**, **CLF**, and **FOT**. + - BITE 24** leads to **RA 3**, which leads to state **17 Reanswer 3** (Connector reference 26, 19, 25). + - CLF** leads to **FITE 22**, which leads to state **19** (Connector reference 8). + - FOT** leads to **FITE 23**, which leads to state **25** (Connector reference 8). +- State 17 Reanswer 3:** Transitions to **BITE 25**, **CLF**, and **FOT**. + - BITE 25** leads to **CB1**, which leads to state **21** (Connector reference 19, 21, 26). + - CLF** leads to **FITE 22**, which leads to state **19** (Connector reference 8). From state 19, there is a transition to **SPITE 8 Release all equipment** (Connector reference 6 (2x), 7 (5x), 8 (3x)). + - FOT** leads to **FITE 23**, which leads to state **26** (Connector reference 8). +- SPITE 8 Release all equipment:** Leads to **RLG**, which leads to the final state **00 Idle**. + +State transition diagram for Incoming Signalling System No. 6. The diagram shows a sequence of states and transitions between BITE, RA, CB, and FITE components, leading to an Idle state. Connector references are listed on the left side of the diagram. + +CCITT - 40840 + +FIGURE 3/Q.613 (Sheet 8 of 8) +**Incoming Signalling System No. 6** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.615-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.615-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.615-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.615-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/Q/T-REC-Q.615-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..193c5abf74645d9065bc0e1348abf7a450354728 --- /dev/null +++ b/marked/Q/T-REC-Q.615-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8209a0ae23cd0e2e49ca1685846767efeffea5ddf79f1584f985ecd300e6b83 +size 157678 diff --git a/marked/Q/T-REC-Q.615-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.615-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..806bb705901cf592e2e675e407f402e5f7a59933 --- /dev/null +++ b/marked/Q/T-REC-Q.615-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:046cc0313dd082dff2cf0730a275c784449d931f278977baedb395b9b2634345 +size 24097 diff --git a/marked/Q/T-REC-Q.615-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/Q/T-REC-Q.615-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7723daf303eb376befd05b7af6bb5c4933f78c96 --- /dev/null +++ b/marked/Q/T-REC-Q.615-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35e21a1fb71875dac60fc7a2645a170525f83761e98f7ca5ab70e765ededca49 +size 162929 diff --git a/marked/Q/T-REC-Q.627-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.627-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e8800d43f4dd80ec7cd8efbc7b06fedee191b58c --- /dev/null +++ b/marked/Q/T-REC-Q.627-199303-I_PDF-E/raw.md @@ -0,0 +1,383 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.627** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +# **INTERWORKING OF SIGNALLING SYSTEMS** --- + +## **INTERWORKING OF SIGNALLING SYSTEMS – LOGIC PROCEDURES FOR OUTGOING SIGNALLING SYSTEM No. 7 (ISUP)** + +**ITU-T Recommendation Q.627** + +(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.627 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 OUTGOING SIGNALLING SYSTEM No. 7 (ISUP)** + +*(Helsinki, 1993)* + +![State overview diagram for outgoing Signalling System No. 7 (ISUP) showing states 00, 01, 02, 03, 04, 05, 07, and 09 with transitions between them. The diagram shows a sequence of states: 00 -> 01 -> 03 -> 04 -> 07 -> 09. State 02 is connected to 01 and 03. State 05 is connected to 04 and 07. There are also transitions from 02 to 05, 03 to 05, 04 to 05, 07 to 05, and 09 to 05. Transitions from 00, 01, 03, 04, 07, and 09 lead to a common bottom line, which then leads to 09. Transitions from 02, 05, and 09 lead to a common top line, which then leads to 00.](69edc2887e907309499ac95b47ab6905_img.jpg) + +State overview diagram for outgoing Signalling System No. 7 (ISUP) showing states 00, 01, 02, 03, 04, 05, 07, and 09 with transitions between them. The diagram shows a sequence of states: 00 -> 01 -> 03 -> 04 -> 07 -> 09. State 02 is connected to 01 and 03. State 05 is connected to 04 and 07. There are also transitions from 02 to 05, 03 to 05, 04 to 05, 07 to 05, and 09 to 05. Transitions from 00, 01, 03, 04, 07, and 09 lead to a common bottom line, which then leads to 09. Transitions from 02, 05, and 09 lead to a common top line, which then leads to 00. + +T1141360-92/d01 + +| State number | State description | Sheet reference | Timers | +|--------------|-------------------------------|-----------------|------------| +| 00 | Idle | 1, 8 | | +| 01 | Wait for call setup info | 1 | | +| 02 | Wait for continuity check | 2 | $t_1, t_2$ | +| 03 | Wait for continuity indicator | 3 | $t_2$ | +| 04 | Wait for address complete | 5 | $t_2$ | +| 05 | Wait for answer | 5 | | +| 07 | Answered | 6 | | +| 09 | Wait for RLC | 8 | $t_3, t_7$ | + +FIGURE 1/Q.627 +State overview diagram for outgoing Signalling System No. 7 (ISUP) + +### **Supervisory timers for outgoing Signalling System No. 7 (ISUP)** + +| | | +|-------------------|-------------------------------------------------| +| $t_1 = 2$ s | Waiting for continuity check | +| $t_2 = 20 - 30$ s | Waiting for address signal | +| $t_3 = 4 - 15$ s | Waiting for Release Complete after Release | +| $t_7 = 1$ minute | Stop repeat sending of Release on $t_3$ timeout | + +### **Information contents of FITEs and BITEs** + +For the information contents of the following FITEs and BITEs see the contents of the corresponding messages in Recommendation Q.763: + +| | | +|---------|--------------------------------| +| FITE A | Initial Address Message (IAM) | +| BITE 47 | Call Progress Message (CPG) | +| BITE 48 | Connect Message (CON) | +| BITE X | Address Complete Message (ACM) | +| BITE Y | Answer Message (ANM) | + +### **Procedures not shown** + +Procedures related to the following messages are not shown in the logic procedures because of no relevancy for interworking or no usage defined yet: + +| | | | | +|------|------|-----|------| +| BLO | CGU | FRJ | UBA | +| BLA | CGUA | GRA | UBL | +| CCR | CQM | GRS | UCIC | +| CFN | CQR | LPA | USR | +| CGB | FAA | OLM | | +| CGBA | FAR | RSC | | + +### **Indicated fault procedures** + +| | | +|------------------|----------------------------| +| $P_1$ (State 02) | Continuity check failure | +| $P_2$ (State 02) | Cross office check failure | +| $P_3$ (State 07) | Failure to receive RES | + +FIGURE 2/Q.627 + +### **Notes to outgoing Signalling System No. 7 (ISUP)** + +![Flowchart for Outgoing Signalling System No. 7 (ISUP) call setup. The process starts at state '00 Idle', followed by 'Activate outgoing SS No. 7 (ISUP)', state '01 Wait for call set up info.', 'FITE (A) Call set up info', 'Construct IAM', 'IAM', 'Start t2', a decision 'CCH' leading to state '1' (outlets 0, 2) or state '3' (outlet 1), 'SPITE 31 Perform cont. check', 'Start t1', and finally state '3'. Vertical lines on the left are labeled 1 and 3. A reference code T1141370-92/d02 is at the bottom right.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +``` + +graph TD + 00([00 +Idle]) --> A[/Activate +outgoing +SS No. 7 (ISUP)/] + A --> 01([01 +Wait for +call set up +info.]) + 01 --> FITE[/FITE (A) +Call set up +info/] + FITE --> Construct[Construct +IAM] + Construct --> IAM[/IAM/] + IAM --> Startt2[/Start t2/] + Startt2 --> CCH{CCH} + CCH -- "0, 2" --> 1((1)) + CCH -- "1" --> SPITE[SPITE 31 +Perform +cont. check] + SPITE --> Startt1[/Start t1/] + Startt1 --> 3((3)) + +``` + +Vertical line labels: 1, 3 + +Reference code: T1141370-92/d02 + +Flowchart for Outgoing Signalling System No. 7 (ISUP) call setup. The process starts at state '00 Idle', followed by 'Activate outgoing SS No. 7 (ISUP)', state '01 Wait for call set up info.', 'FITE (A) Call set up info', 'Construct IAM', 'IAM', 'Start t2', a decision 'CCH' leading to state '1' (outlets 0, 2) or state '3' (outlet 1), 'SPITE 31 Perform cont. check', 'Start t1', and finally state '3'. Vertical lines on the left are labeled 1 and 3. A reference code T1141370-92/d02 is at the bottom right. + +FIGURE 3/Q.627 (sheet 1 of 8) +**Outgoing Signalling System No. 7 (ISUP)** + +![Flowchart for Outgoing Signalling System No. 7 (ISUP)](191a4a245a7d36d03be9a990d0f758f5_img.jpg) + +The flowchart illustrates the logic for Outgoing Signalling System No. 7 (ISUP). It begins at the top with state 3 (labeled 1, 2(3x)). The process enters a loop labeled '02 Wait for continuity check'. From this loop, five parallel paths emerge, each leading to a different state or condition: + +- SPITE 33 Continuity check OK** leads to state 3 (labeled C). +- FITE 1** leads to a decision diamond **SAM Complete?**. + - If **No**, it leads to state 3 (labeled 2). + - If **Yes**, it leads to **Start t2**, then **SAM** (with a **Note**), and finally to state 3 (labeled 2). +- FITE Z** leads to **SPITE 54**, then **Stop t1**, then **Stop t2**, and finally to state 12 (labeled 8). +- FITE 24** leads directly to state 3 (labeled 2). +- t1** leads directly to state P1. + +From the **SPITE 33 Continuity check OK** path, the flow continues to **Stop t1** (labeled 3, P1 (2x)). From **Stop t1**, the flow leads to a decision diamond **Cross office check?**. + + +- If **No**, it leads to state 1 (labeled 1). +- If **Yes**, it leads to a decision diamond **CCH?**. + - If **0**, it leads to state P2. + - If **1, 2**, it leads to state 9 (labeled 3). + + From state 9 (labeled 3), the flow leads to a decision diamond **FITE 24 received?**. + + +- If **Yes**, it leads to state 2 (labeled 3). +- If **No**, it leads to state 4 (labeled 3). + +Other states and labels include: + + +- Top left: 1, 2(3x), 3, C. +- Left side: 3, P1 (2x), 1, 3, P2, 9, 3, 12, 2, 4. +- Bottom left: 1, 1, 2, 3, 2, 3, 4, 3. +- Bottom middle: 3, 2, 12, 8. +- Bottom right: 3, 2, P1. +- Far right: C, T1141380-92/d03. + +Flowchart for Outgoing Signalling System No. 7 (ISUP) + +NOTE – Digits should be forwarded to the outgoing link as soon as they are available. Multi-digit SAMs should only be sent if more than one address digit is waiting. + +FIGURE 3/Q.627 (sheet 2 of 8) +Outgoing Signalling System No. 7 (ISUP) + +![Flowchart for Outgoing Signalling System No. 7 (ISUP) call processing. The process starts at a circle labeled '4' with input '2, 3(2x)'. It goes to a process '03 Wait for continuity indicator'. From there, it branches into four parallel paths: 1) FITE 24 leads to a circle '2' (input '2'), then to 'COT successful', then to a circle '5' (input '5, 4, 12'). 2) FITE 1 leads to a decision 'SAM complete?'. If 'No', it goes to a circle '4' (input '3'). If 'Yes', it goes to 'Start t2', then to 'SAM' (with a 'Note' attached), then to a circle '4' (input '3'). 3) FITE Z leads to 'SPITE 54', then to 'Stop t2', then to a circle '12' (input '8'). 4) t2 leads to 'SPITE 54 Cause 31', then to 'BITE Z', then to 'Stop t2'. All paths converge to a circle 'C' (input '4').](fc46871d72c65d3381d9201646d23439_img.jpg) + +``` + +graph TD + Start((4 +2, 3(2x))) --> Wait[03 Wait for continuity indicator] + Wait --> FITE24[/FITE 24/] + Wait --> FITE1[/FITE 1/] + Wait --> FITEZ[/FITE Z/] + Wait --> t2[/t2/] + FITE24 --> Circle2((2 +2)) + Circle2 --> COT[/COT successful/] + COT --> Circle5((5 +5, 4, 12)) + FITE1 --> SAMComplete{SAM complete?} + SAMComplete -- No --> Circle4_3((4 +3)) + SAMComplete -- Yes --> Startt2[/Start t2/] + Startt2 --> SAM[/SAM/] + Note[Note] -.-> SAM + SAM --> Circle4_3 + FITEZ --> SPITE54[SPITE 54] + SPITE54 --> Stopt2[/Stop t2/] + t2 --> SPITE54Cause31[SPITE 54 Cause 31] + SPITE54Cause31 --> BITEZ[/BITE Z/] + BITEZ --> Stopt2 + Stopt2 --> Circle12((12 +8)) + Circle5 --> CircleC((C +4)) + Circle4_3 --> CircleC + Circle12 --> CircleC + +``` + +Flowchart for Outgoing Signalling System No. 7 (ISUP) call processing. The process starts at a circle labeled '4' with input '2, 3(2x)'. It goes to a process '03 Wait for continuity indicator'. From there, it branches into four parallel paths: 1) FITE 24 leads to a circle '2' (input '2'), then to 'COT successful', then to a circle '5' (input '5, 4, 12'). 2) FITE 1 leads to a decision 'SAM complete?'. If 'No', it goes to a circle '4' (input '3'). If 'Yes', it goes to 'Start t2', then to 'SAM' (with a 'Note' attached), then to a circle '4' (input '3'). 3) FITE Z leads to 'SPITE 54', then to 'Stop t2', then to a circle '12' (input '8'). 4) t2 leads to 'SPITE 54 Cause 31', then to 'BITE Z', then to 'Stop t2'. All paths converge to a circle 'C' (input '4'). + +T1141390-92/d04 + +NOTE – Digits should be forwarded to the outgoing link as soon as they are available. Multi-digit SAMs should only be sent if more than one address digit in waiting. + +FIGURE 3/Q.627 (sheet 3 of 8) +Outgoing Signalling System No. 7 (ISUP) + +![Flowchart for Outgoing Signalling System No. 7 (ISUP)](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +``` + +graph TD + C((C)) -- "2, 3, 5" --> REL[REL] + REL --> BITEZ{BITE Z} + BITEZ --> StopT2{Stop t2} + StopT2 --> CCH{CCH} + CCH -- "0, 2" --> Join(( )) + CCH -- "1" --> ContCheck{Cont. check OK?} + ContCheck -- Yes --> Join + ContCheck -- No --> StopT1{Stop t1} + StopT1 --> Join + Join --> 10((10)) + +``` + +The flowchart illustrates the logic for Outgoing Signalling System No. 7 (ISUP). It begins with a start node 'C' (circle), which leads via an arrow labeled '2, 3, 5' to a process block 'REL' (parallelogram). This is followed by a decision block 'BITE Z' (pentagon pointing left). The next step is a process block 'Stop t2' (pentagon pointing left). A decision block 'CCH' (diamond) follows. If the result is '0, 2', the flow proceeds to a junction point. If the result is '1', the flow proceeds to a decision block 'Cont. check OK?' (diamond). If 'Yes', it proceeds to the junction point. If 'No', it proceeds to a process block 'Stop t1' (pentagon pointing left), which then leads to the junction point. From the junction point, the flow proceeds to an end node '10' (circle). The number '10' is also written to the left of the end node, and the number '8' is written below it. The identifier 'T1141400-92/d05' is located at the bottom right of the diagram. + +Flowchart for Outgoing Signalling System No. 7 (ISUP) + +FIGURE 3/Q.627 (sheet 4 of 8) +**Outgoing Signalling System No. 7 (ISUP)** + +![Flowchart for Outgoing Signalling System No. 7 (ISUP)](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +The flowchart illustrates the logic for Outgoing Signalling System No. 7 (ISUP). It begins at the top with a circle containing '3, 5(x2)' and '5'. An arrow points down to a rounded rectangle labeled '04 Wait for address complete'. From here, the path splits into several branches: + +- Left branch:** From '04 Wait for address complete', an arrow points down to a parallelogram labeled 'ACM'. Below it is a diamond labeled 'BITE X', then a chevron labeled 'Stop t2'. This leads to a circle containing '6' and '5'. From this circle, an arrow labeled '(x2)' points to a rounded rectangle labeled '05 Wait for answer'. Below '05 Wait for answer' is a parallelogram labeled 'ANM', then a diamond labeled 'BITE Y', which leads to a circle containing '8' and '6'. +- Central branch:** From '04 Wait for address complete', an arrow points to a parallelogram labeled 'FITE 1'. Below it is a decision diamond labeled 'SAM complete?'. If 'No', it leads to a circle containing '5'. If 'Yes', it leads to a chevron labeled 'Start t2', then a parallelogram labeled 'SAM'. A dashed line from 'SAM' points to a 'Note'. Below 'SAM' is a circle containing '5' and '5'. +- Right branches:** + - From 'FITE 1', an arrow points to a parallelogram labeled 'FITE Z', then a chevron labeled 'Stop t2', then a rectangle labeled 'SPITE 54', which leads to a circle containing '12' and '8'. + - From 'FITE Z', an arrow points to a double-lined parallelogram labeled 't2', then a diamond labeled 'BITE Z', then a rectangle labeled 'SPITE 54 Cause 31', which also leads to the circle containing '12' and '8'. + - From 't2', an arrow points to a parallelogram labeled 'CON', then a chevron labeled 'Stop t2', then a diamond labeled 'BITE 48', which leads to a circle containing '8' and '6'. +- Bottom branches:** From the circle containing '5' and '5' (below 'SAM'), an arrow points to a horizontal line. From this line, five branches descend: + - Parallelogram 'REL' → diamond 'BITE Z' → circle '10' and '8'. + - Parallelogram 'BITE 47' → diamond 'BITE 47' → circle '6' and '5'. + - Parallelogram 'FITE 23' → diamond 'FOT' → circle '6' and '5'. + - Parallelogram 'FITE Z' → rectangle 'SPITE 54' → circle '12' and '8'. + +On the far left, a vertical line has labels '5', 'C', '12, 8', '6', '5', '8, 10, 6, 6, 12'. On the far right, a circle labeled 'C' and '4' is connected to the top horizontal line. A 'Note' is indicated by a dashed line from the 'SAM' parallelogram. The bottom right corner contains the text 'T1141410-92/d06'. + +Flowchart for Outgoing Signalling System No. 7 (ISUP) + +NOTE – Digits should be forwarded to the outgoing link as soon as they are available. Multi-digit SAMs should only be sent if more than one address digit is waiting. + +FIGURE 3/Q.627 (sheet 5 of 8) +Outgoing Signalling System No. 7 (ISUP) + +![Flowchart of Outgoing Signalling System No. 7 (ISUP)](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the flow of signalling messages in an Outgoing Signalling System No. 7 (ISUP). It begins with a circle labeled '8' at the top left, with an arrow pointing down to a box labeled '07 Answered'. Above this arrow is the text '5(x2), 6, 7'. From the 'Answered' box, a horizontal line extends to the right, with a circle labeled 'H' at its end. Below this line, four boxes are arranged horizontally: 'REL', 'FITE 23', 'FITE 34', and 'FITE 35'. Each of these boxes has a downward-pointing arrow to a corresponding box below it: 'BITE Z', 'FOT', 'SUS (User)', and 'RES (User)'. Below 'BITE Z' is a circle labeled '10' with the number '8' below it. Below 'FOT' is a circle labeled '8' with the number '6' below it. Below 'SUS (User)' and 'RES (User)' is a horizontal line with an arrow pointing left to the 'FOT' box. To the right of this line is the text 'T1141420-92/d07'. On the far left, there are vertical labels '8', 'H', and '10, 8'. + +Flowchart of Outgoing Signalling System No. 7 (ISUP) + +FIGURE 3/Q.627 (sheet 6 of 8) +**Outgoing Signalling System No. 7 (ISUP)** + +![Functional block diagram of Outgoing Signalling System No. 7 (ISUP) showing various components like H, t4, SUS (User), RES (User), SUS (Network), RES (Network), FITE Z, and various BITES connected to interfaces H, P3, and 8, 12.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram illustrates the functional architecture of Outgoing Signalling System No. 7 (ISUP). On the left, vertical lines represent interfaces H, P3, and 8, 12. At the top, a horizontal line connects several functional paths. From left to right: + +- A circle labeled 'H' with a '6' below it. +- A block containing $\bar{t}_4$ which outputs to a circle labeled P3. +- An input block 'SUS (User)' followed by an output block 'BITE 38'. +- An input block 'RES (User)' followed by an output block 'BITE 39'. +- An input block 'SUS (Network)' followed by an output block 'BITE 25'. +- An input block 'RES (Network)' followed by an output block 'BITE 24'. +- An input block 'FITE Z' followed by an output block 'SPITE 54'. + +The outputs from BITE 38, 39, 25, and 24 are joined and lead to a connector circle labeled '8' with a '6' below it. The output from SPITE 54 leads to a connector circle labeled '12' with an '8' below it. The reference code T1141430-92/d08 is in the bottom right corner. + +Functional block diagram of Outgoing Signalling System No. 7 (ISUP) showing various components like H, t4, SUS (User), RES (User), SUS (Network), RES (Network), FITE Z, and various BITES connected to interfaces H, P3, and 8, 12. + +FIGURE 3/Q.627 (sheet 7 of 8) +**Outgoing Signalling System No. 7 (ISUP)** + +![Flowchart for Outgoing Signalling System No. 7 (ISUP) showing two main paths starting from nodes 10 and 12. Path 10 leads to 'SPITE 8 Release all equipment' then 'RLC' then 'Idle'. Path 12 leads to 'REL' then 'Start t7' then 'Start t3' (with node 13/8) then 'Wait for RLC' (node 09). From 'Wait for RLC', four branches emerge: 1) 'RLC' -> 'Stop t3' -> 'Stop t7' -> 'Idle'; 2) 't3' -> 'REL' -> node 13/8; 3) 't7' -> 'Stop t3' -> node P6; 4) 'REL' -> 'RLC' -> node 16/8. Vertical labels on the left include 10, 12, 13, 16, and 13, P6, 16. A document code 'T1130550-91/d09' is at the bottom right.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph TD + subgraph LeftLabels + L1[10, 12] + L2[13] + L3[16] + L4[13, P6, 16] + end + + 10((10)) -- "4, 5, 6(x2)" --> SPITE8[SPITE 8 +Release all +equipment] + SPITE8 --> RLC1[RLC] + RLC1 --> Idle1([00 +Idle]) + + 12((12)) -- "2, 3, 5(x2), 6, 7" --> REL1[REL] + REL1 --> StartT7[Start t7] + StartT7 --> StartT3[Start t3] + 13_8((13 +8)) --> StartT3 + StartT3 --> WaitRLC([09 +Wait for RLC]) + 16_8((16 +8)) --> WaitRLC + + WaitRLC --- Branch(( )) + Branch --> RLC2[RLC] + Branch --> T3[" $\bar{t}_3$ "] + Branch --> T7[" $\bar{t}_7$ "] + Branch --> REL2[REL] + + RLC2 --> StopT3_1[Stop t3] + StopT3_1 --> StopT7[Stop t7] + StopT7 --> Idle2([00 +Idle]) + + T3 --> REL2_2[REL] + REL2_2 --> 13_8_end((13 +8)) + + T7 --> StopT3_2[Stop t3] + StopT3_2 --> P6((P6)) + + REL2 --> RLC3[RLC] + RLC3 --> 16_8_end((16 +8)) + + style LeftLabels fill:none,stroke:none + +``` + +T1130550-91/d09 + +Flowchart for Outgoing Signalling System No. 7 (ISUP) showing two main paths starting from nodes 10 and 12. Path 10 leads to 'SPITE 8 Release all equipment' then 'RLC' then 'Idle'. Path 12 leads to 'REL' then 'Start t7' then 'Start t3' (with node 13/8) then 'Wait for RLC' (node 09). From 'Wait for RLC', four branches emerge: 1) 'RLC' -> 'Stop t3' -> 'Stop t7' -> 'Idle'; 2) 't3' -> 'REL' -> node 13/8; 3) 't7' -> 'Stop t3' -> node P6; 4) 'REL' -> 'RLC' -> node 16/8. Vertical labels on the left include 10, 12, 13, 16, and 13, P6, 16. A document code 'T1130550-91/d09' is at the bottom right. + +FIGURE 3/Q.627 (sheet 8 of 8) +**Outgoing Signalling System No. 7 (ISUP)** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b944433ad57ea200de484a9aabcc9d4f33ef34db --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48287aaa58c566f54c15a6b2f9166c762d29afc29f82cab19056008198c53117 +size 35764 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/06df9aca87a8374023a12f4395994a13_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/06df9aca87a8374023a12f4395994a13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e033f2eb03e599bf4a6771786b47eb8e3c0758c1 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/06df9aca87a8374023a12f4395994a13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0ce315d7c5e19397e891f0a0e629c0431b0a573db3351ff7c10caf6c9d5acf6 +size 1663 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d1e67f8b909cd0d6ce788a592ef72639db6ccad --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5755201728c06fc7fcfe40632eaa1c0491569e699aa4860d69ca48114c9a46ce +size 13302 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec046297f5e7beac0877baa7f2fecce9b56c6f92 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44e1d0091324efb45afdb62547fd67ca0866396f3224c19e72ea6366ebd82594 +size 22035 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/195c5cad0a3078b504853b94d547697e_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/195c5cad0a3078b504853b94d547697e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3932347cf12d8f3cc81c41f2eeb06020310d75b8 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/195c5cad0a3078b504853b94d547697e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4ec474f24d783886ba44aa8ce1795a990b91c5dfca40f2a4099bf4604cec4c6 +size 1346 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a40cddeda69a593abaf4e2474bcb4b57012b2cce --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0416b868373534cc06219985547a9f7ddbb0608328401c84612fe0ecc5821a93 +size 48300 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/25e0dce5ed3984a08ddd42f4e61c08f9_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/25e0dce5ed3984a08ddd42f4e61c08f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..574959462c9ab29ee1bb0aaff4e00d9d4b4c2275 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/25e0dce5ed3984a08ddd42f4e61c08f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5de33dfbda2df8b8205aa6bc7ba562cfb5182ac5a77bdcacf79215894ce7dc48 +size 1725 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c557bf7f434af2d23b3d632dd63b8f4ea24863c --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a71083df6eed2f3988576ed12b112341614c39d1c96cded5e9531d2f292158c4 +size 7912 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/2de4b53c36e79c93eefe63cb247e67d5_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/2de4b53c36e79c93eefe63cb247e67d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6a8a4e377c9154e57908cbee216b41dacc257d2 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/2de4b53c36e79c93eefe63cb247e67d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:002e9252c236c8509619dcdb6b0bbdddd1020203c5190305c6749fd69e681761 +size 1712 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-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.65-200006-I_PDF-E/2f89cacbfb2e6a746b649e7d04bf347e_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/2f89cacbfb2e6a746b649e7d04bf347e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..786ed8e515793dd4b7a0489523ea614e666b0345 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/2f89cacbfb2e6a746b649e7d04bf347e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a49d3776d164628cbc5e7b25d427a2531d2526366da7f0c5cef23b4f4d4640ab +size 1699 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/323d0c55943cd94afdad61df6e196435_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/323d0c55943cd94afdad61df6e196435_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6618ccf652960e9e62892a4a1e94c05f881bc48d --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/323d0c55943cd94afdad61df6e196435_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8893c73d07ebab54761d005ad2f083fbac82a90e062edadfc2fa7726d4a6add4 +size 1461 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d8260b2bf005c5b452b0efc0bdbc1e1c58d1a1d --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7476184e88b2466b146802024c8f038246bfb3343970d20bef3b437a058fcef7 +size 16437 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96faa730bf7011512ea58aa5b6858b6d881d6c77 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c2c3525c99c854a41af339cc145f4ee125be0fab71d7521d5e2b23a0a558369 +size 16484 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49d25f2a6efb1f17aa5a276135b8adc9d36aafe7 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e75ef82f52fe43185d6abf5be6a38ac7e8abeca404fd3ffc5d720beb679049dc +size 6624 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd8b7ae8c74011d05ae59fb27c7766ebdb1ca63f --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73d37d172dbc686777af6a235538e397c68d31783d11a328a605a2b319e1038f +size 45333 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afbd204171065b94f0c81a429efe12760b5b3a69 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f350a6f44367bacaa39d185e63934b6af0ee6e0e909bac6d669ba718bf3e051 +size 53959 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39ea176558c2aebe66cd875df23fad2be7888e65 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f713fac462a339624b28e62c8908c39f981b2401f94b7845668fde7d069a5fd7 +size 20350 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae093957b833327372e83e41b0053bd59294eb63 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec8e00c8be8a2116398944e90deb27e00285593549d7d433cce907728261abf6 +size 89768 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07f19d4a22dd54c21978b0c6751616814872ab02 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcba7d8d47de93e49ca964bf5ee402d37f4cc2f3519784ad1a40912952187c73 +size 34755 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..126f647e42359f795b69e7a5b8ad45d3890143b2 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3000051ed9cc5f424e016edaf68a4e681401f56132777ac6a89af97a06289b5d +size 54618 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/6faa3c4e336150b66e9995c45d68e755_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/6faa3c4e336150b66e9995c45d68e755_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29a0a9976f2b58696bfa84b158889cae8caaeb72 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/6faa3c4e336150b66e9995c45d68e755_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c0a0402101c27b8034f8c3ccab392955bb68d33d17c462c0f78167e80a170b1 +size 1621 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a3cad1fff1d0203733b335498b83b6a30abbbd3 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efd718eaa7d6289ce555eac9b1c1fbf6b558ed4f9a718bc823d895e10f7d3b2c +size 90886 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeda2fc7662a9a4792a19000b364a7b25bd1a400 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f4694757afa775c4f83171e0a23de36e3571edfc9a5df26621ebe83f7743a7c +size 59844 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f12243c6bbd7ac1e6f3663495dfbf7a8897850e7 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:865093867870a144237c1c793efdd3bd1514d51ee4a6f504717e2543164e74ba +size 39463 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/74b613cf54b3b80fbc31a3d4db312474_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/74b613cf54b3b80fbc31a3d4db312474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60629b0816ef5025f696e23e58cfcbadbd4b73b6 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/74b613cf54b3b80fbc31a3d4db312474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1be0e4aa9070aa98ecf5a065a495833f2058e05311813d78eb153f277e2b025e +size 1622 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e07ccf4458d77205a562c5b24e24efbdd348dc38 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81cbbc16d99461c527193d5ad4b7a0c930b5a2c7ed64edfb16c14d113e53c931 +size 110520 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39610efaabd590f3f3d6c4a86dfd280bace5593b --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c9498fa6ee6b927da1105a7067f4319ce1f6c0df416071c64ab2b8fd7988546 +size 93080 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46ffdb0da78d0e37e6d449267de18957f0fbe809 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff9512a46123ba0500dd5ab7a3e4cbbf018a5bae4201b20eb7d587b556931ba3 +size 137279 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/7c34a9b0c79d5f7ad4eae7348d12277a_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7c34a9b0c79d5f7ad4eae7348d12277a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a65842e5296279141dbdc217ebcd397bc456ea26 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7c34a9b0c79d5f7ad4eae7348d12277a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acaf5cb10c6490180faf231137f117d6668ac5a4c54c33683d7704d7ef5931d5 +size 1486 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/7c77261c051f118c26d17e159534376f_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7c77261c051f118c26d17e159534376f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc5e70221a05a61d1d579bbb85fa0bb413ae0a0f --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7c77261c051f118c26d17e159534376f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9e13ee1bed5369ac23a13479721e501bd08e12656e3ee1c7f3450e3cc543737 +size 39245 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e4d7c971a909228538d440992425ce14c210c8d --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:725168dbf88404c89b3b7d8c64d78b6dff652a4ef733d6de21005c01f4289a24 +size 44442 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d8d14b0261c0f281b08143b016230aeb7f0b20a --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdfb93416f3b0b2f9b90b6ffeb43bf9dd76d59f72d7728bd04672d82229744c2 +size 88267 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/8fbd17a99ee7e69f85c3f6f36c84a3a8_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/8fbd17a99ee7e69f85c3f6f36c84a3a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04429a5fe3e7d7a2a8ad04be300be9907b5d6782 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/8fbd17a99ee7e69f85c3f6f36c84a3a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b06d18f8a75df64c635fbc6da9b277af222ee9b74b317a6c939205ee8515e42 +size 1816 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..994ff53fade02dec932e44b603e0d2b3c5c0329b --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97d231ee1298b9d7a5f41dab8a702cf25118c1e9e6269faba3419865a2d490d7 +size 49090 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/9297e7665861e466392c4c56155f5d7d_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9297e7665861e466392c4c56155f5d7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8f0a49b4e0bcf17d3dcf9bc107b6692f6118311 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9297e7665861e466392c4c56155f5d7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9dfd5c0b3e097bef5c00abdadff7a25112c8ec75a1d7779027dfaf21514b0de +size 1329 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/98e25d0e3a034d2f131431d044b2c525_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/98e25d0e3a034d2f131431d044b2c525_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c1c45f71e6da81ad50ef43095b89a3526db793d --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/98e25d0e3a034d2f131431d044b2c525_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f3834cb3d5e5675c55687665f0064ea025f6b8bf13ff74b5e980c2469819dc0 +size 1651 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/9e9354524e793755d1da734c12cd5996_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9e9354524e793755d1da734c12cd5996_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f0eca126f91a5ba05900b212bfe8b90a931a01a --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9e9354524e793755d1da734c12cd5996_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75a8a2914933728e76db3f04ba47055d41f4852b556569bda6a2808acd7b0218 +size 1573 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd34156ac074fe249723f67222b57d988e2a0154 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:007b8e5e6f17f327041b965b2ca6a039fc29a950c0d879aa8f5cef622ed06e8e +size 12114 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/9f26b34949af1f143ede6b326df959c5_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9f26b34949af1f143ede6b326df959c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaeb0cd9330d39d29775688c2a752c131c105775 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/9f26b34949af1f143ede6b326df959c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4e0eddf1473a216ecb35fc600b82294f5bde44a9755e7f87c7deb8b88655771 +size 1232 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a16264826b6318f4702763cb2d5a5a924c05a991 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebf790d86cc02d152ec78c6adcaf18204108120da06fc6a5bde86c29c3899cf4 +size 149572 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/b388ceed29ab9b308c6ecbf2f777bd2a_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/b388ceed29ab9b308c6ecbf2f777bd2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d44f6a3fbd5e28ab295990d6eabad5586b32893e --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/b388ceed29ab9b308c6ecbf2f777bd2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0e03aa21656d61aaaf6fd9e4b51a0618b58f540d6fc93b7c4681b00218fdf52 +size 2486 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2117389c35508a11e8613df9a3a5eaeef988568e --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b89477c2d2490fba1f3aa05e55e85a65b7cbce70de2e2d963339cc8c524af37 +size 23485 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..364493d1c2b40a411b9a9aa4dd47142158a552e0 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b2708dc069d677ef068d1007e05ec14c15a1967332b00ba6069c533de11d225 +size 83789 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b599192ad7cfe02b14d541d362990d7b53d0431b --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd378dd8c3e60d64eccf930dcfca4b69db09c84575a784470f832eefaa57a91c +size 231707 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f865fc96cb84d0602d6a4625a92dd550de5fd2c4 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:967825129123d81e5843ff08717e00997ff331ad88d34354f1f16b408d1be8d3 +size 88998 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/cfef1e45de6cad3de24b78d54ef65268_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cfef1e45de6cad3de24b78d54ef65268_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dba216927c347edde7f89ba09b1f6a152e8fc66e --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/cfef1e45de6cad3de24b78d54ef65268_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d722dc5d1aff9ff7b16f3a44765485e054735f59b5eb4f4196b027b8d9ca415 +size 1527 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/d968c6c4fcd1da0750ad3670d8e3de60_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/d968c6c4fcd1da0750ad3670d8e3de60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bffad49c13e7382c9da90d1642e0c600b047047 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/d968c6c4fcd1da0750ad3670d8e3de60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fba3d29ecec0529d07465733de42e2c1c7727b6464a1902adbe76c9948d9d7aa +size 1850 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bbbc3e053d373a0613b4948bea3a849a4f082f7 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46c5db9dd7bc015bbc40f87049ea857f50b1df0bacb754ef34cf38c9c16d324a +size 11867 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/e0b4aa47303b494d727a4dde48e0e432_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/e0b4aa47303b494d727a4dde48e0e432_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5c1179fa3e006a2134fe089fd82f1ade4b377da --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/e0b4aa47303b494d727a4dde48e0e432_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfedf4f0fe5578ce44f29cdcfe7de196a51434c832e6aa59f270a70121d12350 +size 1557 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6111b4eda07ad6446ce36e64cff3929dd962d9f6 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f900bb969d6a0e5db7bd3cb944e04e0a88fb6041e1693631d432f9d0461fa0ec +size 27175 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98a3efad9a324c6a9bbfd547e99abe33c0c973a5 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1c472db8922a540b86073209fbaca3081109ba0b7b91b2f8a6aabf4b64bd2f0 +size 69597 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccec95a85968a76253278fe6ab6508642040b1a2 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ad1a7ad6e8c75797fc5ba1a84e1ac7d739fc87f2d7ff86008d92aa56a408a12 +size 98344 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74f85151adf14f19bc5e345883ff6080c4b93317 --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:341418a7feeb8bfe2fcea13cdd9e645ccbe4678803d8ac0369f7db639bb0f15a +size 35475 diff --git a/marked/Q/T-REC-Q.65-200006-I_PDF-E/fa58e38f62eaf28be7b11adc8c2ad5c7_img.jpg b/marked/Q/T-REC-Q.65-200006-I_PDF-E/fa58e38f62eaf28be7b11adc8c2ad5c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f6ee6d931a60251e154316e72aa1fc46fb9794d --- /dev/null +++ b/marked/Q/T-REC-Q.65-200006-I_PDF-E/fa58e38f62eaf28be7b11adc8c2ad5c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d0187ea31b832a6a2bd55fa4dedc16042c6453158feb7fae6b5c3da9a4a59b8 +size 1624 diff --git a/marked/Q/T-REC-Q.656-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.656-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ec00761e9fa1f8c8b0e722c909934e190bdcd5f3 --- /dev/null +++ b/marked/Q/T-REC-Q.656-199303-I_PDF-E/raw.md @@ -0,0 +1,368 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.656** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +# **INTERWORKING OF SIGNALLING SYSTEMS** --- + +## **INTERWORKING OF SIGNALLING SYSTEMS – LOGIC PROCEDURES FOR INTERWORKING OF SIGNALLING SYSTEM No. 6 TO SIGNALLING SYSTEM No. 7 (ISUP)** + +**ITU-T Recommendation Q.656** + +(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.656 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. 6 TO SIGNALLING SYSTEM No. 7 (ISUP)** + +*(Helsinki, 1993)* + +![State overview diagram showing states 00 to 05 with transitions. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for address-complete, 03 is Wait for answer, 04 is Answered, and 05 is Wait for resume. Transitions are: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, and 05 back to 00. A curved transition also exists from 02 to 04. A label 'T1141470-92/d01' is present near state 05.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 00 + 00 --> 01 + 01 --> 02 + 02 --> 03 + 02 --> 04 + 03 --> 04 + 04 --> 05 + 05 --> 00 + state "00" as 00 + state "01" as 01 + state "02" as 02 + state "03" as 03 + state "04" as 04 + state "05" as 05 + +``` + +State overview diagram showing states 00 to 05 with transitions. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for address-complete, 03 is Wait for answer, 04 is Answered, and 05 is Wait for resume. Transitions are: 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, and 05 back to 00. A curved transition also exists from 02 to 04. A label 'T1141470-92/d01' is present near state 05. + +| State number | State description | Sheet number | +|---------------------|---------------------------|---------------------| +| 00 | Idle | 1, 2, 3, 4, 5 | +| 01 | Wait for CPCI-FITE | 1 | +| 02 | Wait for address-complete | 2 | +| 03 | Wait for answer | 4 | +| 04 | Answered | 4 | +| 05 | Wait for resume | 5 | + +FIGURE 1/Q.656 +State overview diagram for interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP) + +FIGURE 2/Q.656 + +(Reserved for future notes) + +![Flowchart showing the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). The steps are: 00 Idle -> Activate SS No. 6 SS No. 7 (ISUP) interworking procedure -> 01 Wait for CPCI-FITE -> FITEs 9-13, 17-19 -> Activate outgoing SS No. 7 procedure -> SPITE 52 -> FITE A (Table 1) -> 1. A vertical line on the left is labeled 1, and a circle at the bottom is labeled 1 and 2. The text T1141480-92/d02 is at the bottom right.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +``` + +graph TD + 00([00 Idle]) --> A[/Activate SS No. 6 +SS No. 7 (ISUP) +interworking procedure/] + A --> 01([01 Wait for +CPCI-FITE]) + 01 --> B[/FITEs 9-13, +17-19/] + B --> C[/Activate outgoing SS No. 7 +procedure/] + C --> D[SPITE 52] + D --> E[/FITE A +(Table 1)/] + E --> 1((1)) + +``` + +T1141480-92/d02 + +Flowchart showing the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). The steps are: 00 Idle -> Activate SS No. 6 SS No. 7 (ISUP) interworking procedure -> 01 Wait for CPCI-FITE -> FITEs 9-13, 17-19 -> Activate outgoing SS No. 7 procedure -> SPITE 52 -> FITE A (Table 1) -> 1. A vertical line on the left is labeled 1, and a circle at the bottom is labeled 1 and 2. The text T1141480-92/d02 is at the bottom right. + +FIGURE 3/Q.656 (sheet 1 of 5) +**Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +![Flowchart for interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). The process starts at node 1 (1, 2 (x 2), 3) leading to state 02 'Wait for address complete'. From there, it branches to FITE 1, FITE 22, and FITE 24. FITE 1 leads to a decision 'Country Code FITE?'. If 'No', it goes to node 2 (3). If 'Yes', it goes to decision 'SPITE 22?'. If 'SPITE 22?' is 'No', it goes to 'Omit Country Code FITE'. If 'SPITE 22?' is 'Yes', it goes to FITE 1. Both 'Omit Country Code FITE' and 'FITE 1' lead to node 1 (2). FITE 22 leads to (Note) and then FITE Z, which leads to state 00 'Idle'. FITE 24 leads to FITE 24 and then node 1 (2). A reference T1124970-90/d03 is present.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +``` + +graph TD + Start((1 1, 2 (x 2), 3)) --> State02([02 Wait for address complete]) + State02 --> FITE1_1[/FITE 1/] + State02 --> FITE22_1[/FITE 22/] + State02 --> FITE24_1[/FITE 24/] + State02 --> Node2_3((2 3)) + + FITE1_1 --> CC_FITE{Country Code FITE?} + CC_FITE -- No --> Node2_3 + CC_FITE -- Yes --> SPITE_22{SPITE 22?} + + SPITE_22 -- No --> Omit[Omit Country Code FITE] + SPITE_22 -- Yes --> FITE1_2[/FITE 1/] + + Omit --> Node1_2_1((1 2)) + FITE1_2 --> Node1_2_1 + + FITE22_1 -- (Note) --> FITEZ[/FITE Z/] + FITEZ --> State00([00 Idle]) + + FITE24_1 --> FITE24_2[/FITE 24/] + FITE24_2 --> Node1_2_2((1 2)) + + T1124970-90/d03 + +``` + +Flowchart for interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). The process starts at node 1 (1, 2 (x 2), 3) leading to state 02 'Wait for address complete'. From there, it branches to FITE 1, FITE 22, and FITE 24. FITE 1 leads to a decision 'Country Code FITE?'. If 'No', it goes to node 2 (3). If 'Yes', it goes to decision 'SPITE 22?'. If 'SPITE 22?' is 'No', it goes to 'Omit Country Code FITE'. If 'SPITE 22?' is 'Yes', it goes to FITE 1. Both 'Omit Country Code FITE' and 'FITE 1' lead to node 1 (2). FITE 22 leads to (Note) and then FITE Z, which leads to state 00 'Idle'. FITE 24 leads to FITE 24 and then node 1 (2). A reference T1124970-90/d03 is present. + +NOTE – In principle, FITE 22 should result in cause 16. However, in cases where FITE 22 results from a timeout expiry, cause 127 should be sent. + +FIGURE 3/Q.656 (sheet 2 of 5) +**Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +![Flowchart showing the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP).](547f726730e589392f239257a833ede3_img.jpg) + +The diagram illustrates the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). It features four vertical paths originating from a common horizontal line at the top, which is marked with a circled '2' and a subscript '2'. + +- Path 1 (Leftmost):** Passes through a chevron-shaped block labeled 'BITE X', then a rectangular block labeled 'SPITE 53 (Table 2)', then a chevron-shaped block labeled 'BITE n', and finally terminates at a circled '3' with a subscript '4'. +- Path 2:** Passes through a chevron-shaped block labeled 'BITE 30', then a chevron-shaped block labeled 'BITE 30', and terminates at a circled '1' with a subscript '2'. +- Path 3:** Passes through a chevron-shaped block labeled 'BITE Z', then a rectangular block labeled 'SPITE 53 (Table 5)', then a chevron-shaped block labeled 'BITE n', then a double-lined oval block labeled '00 Idle', and finally terminates at a circled '4' with a subscript '4'. +- Path 4 (Rightmost):** Passes through a chevron-shaped block labeled 'BITE 48', then a rectangular block labeled 'SPITE 53 (Table 4)', then a chevron-shaped block labeled 'BITE j', then a chevron-shaped block labeled 'BITE k', and finally terminates at a circled '4' with a subscript '4'. + +On the left side of the diagram, there are vertical labels: '2' at the top, '1' in the middle, and '3, 4' at the bottom, corresponding to the levels of the various blocks. + +Flowchart showing the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). + +T1124980-90/d04 + +FIGURE 3/Q.656 (sheet 3 of 5) +**Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +![Flowchart showing the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). The process starts at state 3, proceeds to 'Wait for answer' (03), then branches into four paths: BITE Y, FITE 23, FITE 22, and BITE Z. BITE Y leads to SPITE 53, then BITE n (Table 3), then state 4, then 'Answered' (04), and finally state 5. FITE 23 leads to FITE 23, then state 3. FITE 22 leads to FITE Z, which has a note, then state 00 'Idle'. BITE Z leads to SPITE 53, then BITE n (Table 6), then state 00 'Idle'. Various connector symbols (circles and hexagons) with numbers and subscripts are used throughout the flow.](fc46871d72c65d3381d9201646d23439_img.jpg) + +``` + +graph TD + 3((3)) -- "3, 4" --> 03{{03 +Wait for answer}} + 03 --> BITE_Y[/BITE Y/] + 03 --> FITE_23_1[/FITE 23/] + 03 --> FITE_22[/FITE 22/] + 03 --> BITE_Z[/BITE Z/] + BITE_Y --> SPITE_53_1[SPITE 53] + SPITE_53_1 --> BITE_n_3[/BITE n +(Table 3)/] + BITE_n_3 --> 4((4)) + 4 -- "3, 5" --> 04{{04 +Answered}} + 04 --> 5((5)) + 5 -- "5" --> 5 + FITE_23_1 --> FITE_23_2[/FITE 23/] + FITE_23_2 --> 3_2((3)) + 3_2 -- "4" --> 3_2 + FITE_22 --> FITE_Z[/FITE Z/] + FITE_Z -- "(Note)" --> 00_1{{00 +Idle}} + BITE_Z --> SPITE_53_2[SPITE 53] + SPITE_53_2 --> BITE_n_6[/BITE n +(Table 6)/] + BITE_n_6 --> 00_2{{00 +Idle}} + 00_2 -- "T1141490-92/d05" --> 00_2 + +``` + +Flowchart showing the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). The process starts at state 3, proceeds to 'Wait for answer' (03), then branches into four paths: BITE Y, FITE 23, FITE 22, and BITE Z. BITE Y leads to SPITE 53, then BITE n (Table 3), then state 4, then 'Answered' (04), and finally state 5. FITE 23 leads to FITE 23, then state 3. FITE 22 leads to FITE Z, which has a note, then state 00 'Idle'. BITE Z leads to SPITE 53, then BITE n (Table 6), then state 00 'Idle'. Various connector symbols (circles and hexagons) with numbers and subscripts are used throughout the flow. + +NOTE – In principle, FITE 22 should result in cause 16. However, in cases where FITE 22 results from a timeout expiry, cause 127 should be sent. + +FIGURE 3/Q.656 (sheet 4 of 5) +**Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +![Flowchart showing interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP).](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +The diagram illustrates the interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). It is divided into two horizontal sections. + +**Top Section:** At the top, a circle containing the number '5' with a subscript '4' points down to a horizontal line. Below this line are four chevron-shaped boxes: 'BITE Z', 'FITE 22', 'FITE 23', and 'BITE 25'. Below 'BITE Z' is a parallelogram 'BITE 25'. Below 'FITE 22' is a parallelogram 'FITE Z'. Below 'FITE 23' is a parallelogram 'FITE 23'. Below 'BITE 25' is a parallelogram 'BITE 25'. A bracket labeled '(Note)' is next to the 'BITE 25' parallelogram. Arrows from 'BITE 25' (parallelogram), 'FITE 23' (parallelogram), and 'BITE 25' (parallelogram) point to terminal states: '00 Idle', a circle with '4' and subscript '4', and '05 Wait for resume' respectively. A circle with '6' and subscript '5' points to the arrow leading to '05 Wait for resume'. + +**Bottom Section:** Below the top section, another horizontal line connects to four chevron-shaped boxes: 'FITE 22', 'FITE 23', 'BITE 24', and 'BITE Z'. Below 'FITE 22' is a parallelogram 'FITE Z' with a bracket labeled '(Note)' next to it. Below 'FITE 23' is a parallelogram 'FITE 23'. Below 'BITE 24' is a parallelogram 'BITE 24'. Below 'BITE Z' is a terminal state '00 Idle'. Arrows from 'FITE Z' (parallelogram), 'FITE 23' (parallelogram), and 'BITE 24' (parallelogram) point to terminal states: '00 Idle', a circle with '6' and subscript '5', and a circle with '4' and subscript '4' respectively. The text 'T1125000-90/d06' is in the bottom right corner. + +On the far left, vertical labels '5', '6', '4', and '6, 4' are present. + +Flowchart showing interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP). + +NOTE – In principle, FITE 22 should result in cause 16. However, in cases where FITE 22 results from a timeout expiry, cause 127 should be sent. + +FIGURE 3/Q.656 (sheet 5 of 5) +**Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +TABLE 1/Q.656 + +### **FITE A construction – Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +| Received FITE | CPC | +|---------------|-----| +| 9 | 1 | +| 10 | 2 | +| 11 | 3 | +| 12 | 4 | +| 13 | 5 | +| 17 | 10 | +| 18 | 11 | +| 19 | 12 | + +| SPITE 36 | CCH | +|----------|-----| +| Yes | 01 | +| No | 10 | + +| SPITE 22 | NAI | +|----------|-----| +| Yes | 100 | +| No | 011 | + +| SPITE 20 | SI | +|----------|----| +| Yes | 01 | +| No | 00 | + +| SPITE 21 | ECI | +|----------|-----| +| Yes | 1 | +| No | 0 | + +| | +|-------------------------------------| +| TMR = 11 | +| CPC Calling party's category | +| CCH Continuity check indicator | +| NAI Nature of address indicator | +| SI Satellite indicator | +| ECI Echo control indicator | +| TMR Transmission medium requirement | + +TABLE 2/Q.656 + +### **BITE X analysis – Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +| Received BITE X | | | BITE n to be sent | +|---------------------------------------|----|-----|-------------------| +| CH | ST | CAT | | +| 00 | 00 | 00 | BITE 2 + BITE 27 | +| 00 | 00 | 01 | BITE 2 + BITE 27 | +| 00 | 00 | 10 | BITE 4 | +| 00 | 01 | 00 | BITE 5 | +| 00 | 01 | 01 | BITE 5 | +| 00 | 01 | 10 | BITE 7 | +| 01 | 00 | 00 | BITE 3 | +| 01 | 00 | 01 | BITE 3 | +| 01 | 00 | 10 | BITE 4 | +| 01 | 01 | 00 | BITE 6 | +| 01 | 01 | 01 | BITE 6 | +| 01 | 01 | 10 | BITE 7 | +| 10 | 00 | 00 | BITE 2 + BITE 27 | +| 10 | 00 | 01 | BITE 2 + BITE 27 | +| 10 | 00 | 10 | BITE 4 | +| 10 | 01 | 00 | BITE 5 | +| 10 | 01 | 01 | BITE 5 | +| 10 | 01 | 10 | BITE 7 | +| CH Charge indicator | | | | +| ST Called party's status indicator | | | | +| CAT Called party's category indicator | | | | + +TABLE 3/Q.656 + +### **BITE Y analysis – Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +| Received BITE Y
CH | BITE n to be sent | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| – | BITE 22 | +| 00 | BITE 22 | +| 01 | BITE 23 | +| 10 | BITE 22 | +| NOTE – With this proposal, BITE 22 (answer, charge) may be sent for a call where an address complete no charge message was previously sent. It is assumed that it does result in charging the call. | | + +TABLE 4/Q.656 + +### **CONNECT analysis – Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +| Received CONNECT fields | | | BITE J | BITE K | +|-------------------------|----|-----|------------------|---------| +| CH | ST | CAT | | | +| 00 | 00 | 00 | BITE 2 + BITE 27 | BITE 22 | +| 00 | 00 | 01 | BITE 2 + BITE 27 | BITE 22 | +| 00 | 00 | 10 | BITE 4 | BITE 22 | +| 00 | 01 | 00 | BITE 5 | BITE 22 | +| 00 | 01 | 01 | BITE 5 | BITE 22 | +| 00 | 01 | 10 | BITE 7 | BITE 22 | +| 01 | 00 | 00 | BITE 3 | BITE 23 | +| 01 | 00 | 01 | BITE 3 | BITE 23 | +| 01 | 00 | 10 | BITE 4 | BITE 23 | +| 01 | 01 | 00 | BITE 6 | BITE 23 | +| 01 | 01 | 01 | BITE 6 | BITE 23 | +| 01 | 01 | 10 | BITE 7 | BITE 23 | +| 10 | 00 | 00 | BITE 2 + BITE 27 | BITE 22 | +| 10 | 00 | 01 | BITE 2 + BITE 27 | BITE 22 | +| 10 | 00 | 10 | BITE 4 | BITE 22 | +| 10 | 01 | 00 | BITE 5 | BITE 22 | +| 10 | 01 | 01 | BITE 5 | BITE 22 | +| 10 | 01 | 10 | BITE 7 | BITE 22 | + +NOTE – In this proposal, an answer, no charge BITE is generated when a no charge information is carried through the connect message. + +TABLE 5/Q.656 + +### **Received RELEASE analysis before ACM – Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +| Received BITE Z
Cause | Sent BITE n | +|--------------------------|-------------| +| 42 | 9 | +| 34 | 10 | +| 28 | 14 | +| 1 | 15 | +| 17 | 16 | +| 27 | 17 | +| 31 | 19 | +| 4 | 20 | +| Other | 19 | + +TABLE 6/Q.656 + +### **Received RELEASE analysis, after ACM and before ANM – Interworking of Signalling System No. 6 to Signalling System No. 7 (ISUP)** + +| Received BITE Z
Cause | Sent BITE n | | +|--------------------------|----------------|-------------------------| +| Any | 19 | if ST = subscriber free | +| 34
31
Other | 10
19
19 | if ST ≠ subscriber free | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.662-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.662-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3f6ee786c57a41db45aa7421ae0f71324fb85faa --- /dev/null +++ b/marked/Q/T-REC-Q.662-198811-I_PDF-E/raw.md @@ -0,0 +1,244 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.662** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR +INTERWORKING OF SIGNALLING +SYSTEM No. 7 (TUP) TO No. 5** + +**ITU-T Recommendation Q.662** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.662 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. 7 (TUP) TO No. 5 + +![State overview diagram showing a sequence of states from 00 to 07. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for COT, 03 is Wait for address-complete, 04 is Wait for register deactivation, 05 is Wait for answer, 06 is Answered, and 07 is Clear-back. Transitions are shown between consecutive states, with additional lines from 01, 02, 03, 04, 05, and 06 pointing to a common line above the states. A self-loop is shown on state 07. The diagram is labeled CCITT-48680.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +State overview diagram showing a sequence of states from 00 to 07. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for COT, 03 is Wait for address-complete, 04 is Wait for register deactivation, 05 is Wait for answer, 06 is Answered, and 07 is Clear-back. Transitions are shown between consecutive states, with additional lines from 01, 02, 03, 04, 05, and 06 pointing to a common line above the states. A self-loop is shown on state 07. The diagram is labeled CCITT-48680. + +| State number | State description | Sheet reference | +|---------------------|--------------------------------|------------------------| +| 00 | Idle | 1, 2 | +| 01 | Wait for CPCI-FITE | 1 | +| 02 | Wait for COT | 1 | +| 03 | Wait for address-complete | 2 | +| 04 | Wait for register deactivation | 2 | +| 05 | Wait for answer | 2 | +| 06 | Answered | 2 | +| 07 | Clear-back | 2 | + +FIGURE 1/Q.662 + +State overview diagram for interworking of Signalling System No. 7 (TUP) to No. 5 + +FIGURE 2/Q.662 + +(Reserved for future notes) + +![Flowchart showing the interworking of Signalling System No. 7 (TUP) to No. 5. The process starts at 'Idle' (00), proceeds to 'Activate I/W No. 7 (TUP)/No. 5', then 'Wait for CPCI-FITE' (01). It branches into FITEs 9-13, 17-19; FITE 22 (leading to Idle 00); and FITE 30 (leading to connector 8). From 'Wait for COT' (02), it branches into FITE 1, FITE 25, FITE 24, and FITE 22 (leading to Idle 00). All lead to 'Activate outgoing No. 5', which leads to 'Which CPCI-FITE'. Options are 9-13 (FITE 9-13) and 17-19 (FITE 17). Both lead to 'SPITE 22'. If 'Yes', it goes to FITE 3; if 'No', it goes to FITE 2. Both lead to 'Any more FITE 1s'. If 'Yes', it goes to connector 2; if 'No', it goes to connector 1.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +Connector reference + +``` + +graph TD + Idle00_1((00 Idle)) --> ActI[Activate I/W No. 7 (TUP)/No. 5] + ActI --> WaitCPCI((01 Wait for CPCI-FITE)) + WaitCPCI --> FITEs913[FITEs 9-13, 17-19] + WaitCPCI --> FITE22_1[FITE 22] + WaitCPCI --> FITE30[FITE 30] + FITE22_1 --> Idle00_2((00 Idle)) + FITE30 --> Connector8_1((8 1)) + FITEs913 --> WaitCOT((02 Wait for COT)) + WaitCOT --> FITE1[FITE 1] + WaitCOT --> FITE25[FITE 25] + WaitCOT --> FITE24[FITE 24] + WaitCOT --> FITE22_2[FITE 22] + FITE22_2 --> Idle00_3((00 Idle)) + FITE1 --> ActOut[Activate outgoing No. 5] + FITE25 --> ActOut + FITE24 --> ActOut + ActOut --> WhichCPCI{Which CPCI-FITE} + WhichCPCI -- 9-13 --> FITE913[FITE 9-13] + WhichCPCI -- 17-19 --> FITE17[FITE 17] + FITE913 --> SPITE22{SPITE 22} + FITE17 --> SPITE22 + SPITE22 -- Yes --> FITE3[FITE 3] + SPITE22 -- No --> FITE2[FITE 2] + FITE2 --> MoreFITE{Any more FITE 1s} + FITE3 --> MoreFITE + MoreFITE -- Yes --> Connector2((2 2)) + MoreFITE -- No --> Connector1((1 2)) + +``` + +8 1 + +8 1 + +4 2 + +2, 1 + +T1104850-87 + +Flowchart showing the interworking of Signalling System No. 7 (TUP) to No. 5. The process starts at 'Idle' (00), proceeds to 'Activate I/W No. 7 (TUP)/No. 5', then 'Wait for CPCI-FITE' (01). It branches into FITEs 9-13, 17-19; FITE 22 (leading to Idle 00); and FITE 30 (leading to connector 8). From 'Wait for COT' (02), it branches into FITE 1, FITE 25, FITE 24, and FITE 22 (leading to Idle 00). All lead to 'Activate outgoing No. 5', which leads to 'Which CPCI-FITE'. Options are 9-13 (FITE 9-13) and 17-19 (FITE 17). Both lead to 'SPITE 22'. If 'Yes', it goes to FITE 3; if 'No', it goes to FITE 2. Both lead to 'Any more FITE 1s'. If 'Yes', it goes to connector 2; if 'No', it goes to connector 1. + +FIGURE 3/Q.662 (Sheet 1 of 2) +**Interworking of Signalling System No. 7 (TUP) to No. 5** + +Connector +reference + +1 + + 2 +3 + + 4, 3 +5 + + 3 +6 +5 + +3 + +7 + +7, 6 + +3 + +6, 7 + +![Flowchart showing the interworking of Signalling System No. 7 (TUP) to No. 5.](01141eb99b707de5aead56f84afe3b1f_img.jpg) + +``` + + graph TD + C1((1)) -- 1 --> S00([00 Wait for address-complete COT received]) + S00 --> FITE1_1[FITE 1] + S00 --> BITE26[BITE 26] + S00 --> FITE22_1[FITE 22] + S00 --> BITE8_1[BITE 8] + + C2((2)) -- 1 --> FITE1_1 + FITE1_1 --> D1{Country code FITE} + D1 -- Yes --> D2{SPITE 22} + D1 -- No --> FITE1_2[FITE 1] + D2 -- Yes --> FITE1_2 + D2 -- No --> Omit[Omit country code] + FITE1_2 --> C4((4)) + Omit --> C4 + C4 -- 1 --> C4_end + + BITE26 --> BITE2[BITE 2] + BITE2 --> S04([04 Wait for register deactivation]) + S04 --> BITE27_1[BITE 27] + S04 --> BITE8_2[BITE 8] + S04 --> FITE22_2[FITE 22] + + BITE27_1 --> BITE27_2[BITE 27] + BITE27_2 --> C5((5)) + C5 -- 2 --> S05([05 Wait for answer]) + + BITE8_2 --> BITE10_1[BITE 10] + BITE10_1 --> S00_Idle1([00 Idle]) + + FITE22_2 --> C3_1((3)) + C3_1 -- 2 --> C3_end + + FITE22_1 --> C3_2((3)) + C3_2 -- 2 --> C3_end + + BITE8_1 --> BITE10_2[BITE 10] + BITE10_2 --> S00_Idle2([00 Idle]) + + S05 --> BITE22_1[BITE 22] + S05 --> BITE8_3[BITE 8] + S05 --> FITE23_1[FITE 23] + S05 --> FITE22_3[FITE 22] + + BITE22_1 --> BITE22_2[BITE 22] + BITE22_2 --> C6((6)) + C6 -- 2 (2X) --> S06([06 Answered]) + + BITE8_3 --> BITE10_3[BITE 10] + BITE10_3 --> S00_Idle3([00 Idle]) + + FITE23_1 --> FITE23_2[FITE 23] + FITE23_2 --> C5_2((5)) + C5_2 -- 2 --> C5_end + + FITE22_3 --> C3_3((3)) + C3_3 -- 2 --> C3_end + + S06 --> BITE25_1[BITE 25] + S06 --> FITE23_3[FITE 23] + S06 --> FITE22_4[FITE 22] + + BITE25_1 --> BITE25_2[BITE 25] + BITE25_2 --> C7_1((7)) + C7_1 -- 2 --> C7_end + + FITE23_3 --> FITE23_4[FITE 23] + FITE23_4 --> C6_2((6)) + C6_2 -- 2 --> C6_end + + FITE22_4 --> C3_4((3)) + C3_4 -- 2 --> C3_end + + C7_2((7)) -- 2 (2X) --> S07([07 Clear-back]) + S07 --> BITE22_3[BITE 22] + S07 --> FITE23_5[FITE 23] + S07 --> FITE22_5[FITE 22] + + BITE22_3 --> BITE24[BITE 24] + BITE24 --> C6_3((6)) + C6_3 -- 2 --> C6_end + + FITE23_5 --> FITE23_6[FITE 23] + FITE23_6 --> C7_3((7)) + C7_3 -- 2 --> C7_end + + FITE22_5 --> C3_5((3)) + C3_5 -- 2 (4X) --> FITE22_6[FITE 22] + FITE22_6 --> S00_Idle4([00 Idle]) + +``` + +Flowchart showing the interworking of Signalling System No. 7 (TUP) to No. 5. + +T1104862-87 + +FIGURE 3/Q.662 (Sheet 2 of 2) + +**Interworking of Signalling System No. 7 (TUP) to No. 5** +**Fascicle VI.6 - Rec. Q.662**          3 \ No newline at end of file diff --git a/marked/Q/T-REC-Q.663-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.663-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.663-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.663-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg b/marked/Q/T-REC-Q.663-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75524ce1593e1a7292d0dae78414831cb2dccdee --- /dev/null +++ b/marked/Q/T-REC-Q.663-198811-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7fb2ccc3d441052e56f34ec238811136d8399ecc457a8d3578f1aba2fa7b8f4 +size 118596 diff --git a/marked/Q/T-REC-Q.663-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.663-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4900a1515f8ad714f08238b7a19cdea9d5e8612d --- /dev/null +++ b/marked/Q/T-REC-Q.663-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db54c40af921113c695c98a24fea88d237c139f632187d3f20bc8561137ed6a1 +size 14754 diff --git a/marked/Q/T-REC-Q.663-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg b/marked/Q/T-REC-Q.663-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f9735b445654bb90b5d043862f571c5abe40978 --- /dev/null +++ b/marked/Q/T-REC-Q.663-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb2720f476e93b7942c90d6caf1740a054ea838df30b41c5b162d45e61121663 +size 190367 diff --git a/marked/Q/T-REC-Q.663-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.663-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4ec2936181d79c303c4a986efc4031c49e69c876 --- /dev/null +++ b/marked/Q/T-REC-Q.663-198811-I_PDF-E/raw.md @@ -0,0 +1,141 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.663** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR +INTERWORKING OF SIGNALLING +SYSTEM No. 7 (TUP) TO No. 6** + +**ITU-T Recommendation Q.663** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.663 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. 7 (TUP) TO No. 6 + +![State overview diagram showing six states (00 to 05) in a linear sequence with feedback loops. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for address-complete, 03 is Wait for answer, 04 is Answered, and 05 is Clear-back. Arrows show transitions between states, with feedback from 05 to 00, 02, 03, and 04.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +``` + + graph LR + 00((00)) --> 01((01)) + 01 --> 02((02)) + 02 --> 03((03)) + 03 --> 04((04)) + 04 --> 05((05)) + 05 --> 00 + 05 --> 02 + 05 --> 03 + 05 --> 04 + +``` + +CCITT-48661 + +State overview diagram showing six states (00 to 05) in a linear sequence with feedback loops. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for address-complete, 03 is Wait for answer, 04 is Answered, and 05 is Clear-back. Arrows show transitions between states, with feedback from 05 to 00, 02, 03, and 04. + +| State number | State description | Sheet reference | +|--------------|---------------------------|-----------------| +| 00 | Idle | 1, 2 | +| 01 | Wait for CPCI-FITE | 1 | +| 02 | Wait for address-complete | 1 | +| 03 | Wait for answer | 1 | +| 04 | Answered | 2 | +| 05 | Clear-back | 2 | + +FIGURE 1/Q.663 +State overview diagram for interworking of Signalling System No. 7 (TUP) to No. 6 + +## *Procedures not shown* + +The following procedure, not directly relevant to interworking, is not shown in the logic: + +P1 - Procedure for repeat attempt. + +FIGURE 2/Q.663 +Notes to interworking of Signalling System No. 7 (TUP) to No. 6 + +2 Fascicle VI.6 - Rec. Q.663 + + Connector +reference +![FIGURE 3/Q.663 (Sheet 1 of 2) Interworking of Signalling System No. 7 (TUP) to No. 6](9e6062272bbe3ddbb7c0606721d64cf0_img.jpg) + +The diagram is a flowchart representing the interworking between Signalling System No. 7 (TUP) and Signalling System No. 6. It consists of several states and transitions: + +- State 00 (Idle):** Leads to a task 'Activate I/W No. 7 (TUP)/No. 6'. +- State 01 (Wait for CPCI-FITE):** Follows the activation task. It has multiple output paths based on received signals like FITEs 9-13, 17-19, and FITE 30. +- State 02 (Wait for address complete):** Entered from connector 1. It handles various BITE (Backward Interworking Telephony Event) and FITE (Forward Interworking Telephony Event) signals. +- State 03 (Wait for answer):** Entered from connector 2. It handles BITE 22, BITE 23, BITEs 10, 12, 19, FITE 22, and FITE 23. +- Decision Points:** Includes checks for 'Country code FITE', 'SPITE 22', 'SPITE 21', and 'SPITE 20'. +- Connectors:** Circular markers labeled 1, 2, 3, 4, and A are used to link different parts of the flowchart across the page and potentially to other sheets. + +FIGURE 3/Q.663 (Sheet 1 of 2) Interworking of Signalling System No. 7 (TUP) to No. 6 + + FIGURE 3/Q.663 (Sheet 1 of 2) +**Interworking of Signalling System No. 7 (TUP) to No. 6** + +T1104870-87 + +Connector reference + +![Flowchart showing interworking of Signalling System No. 7 (TUP) to No. 6. It includes states like 'Answered', 'Clear-back', 'Idle', and 'Repeat attempt', and message types like BITE 12, 14, 15, 16, 17, 20, 25, FITE 22, 23, 24, 9, 10, 19. Connector references A, 3, P1, 4, 3, 4, 3 are on the left. A callout 'CCITT - 60 300' is at the bottom right.](690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg) + +The diagram illustrates the interworking of Signalling System No. 7 (TUP) to No. 6. It is divided into two main sections. + +**Left Section (Connector reference A, 3, P1, 4, 3, 4, 3):** + +- Starts with a call attempt (3) leading to an **Answered** state (04). +- From **Answered**, three paths are possible: + - BITE 25** leads to another **BITE 25** state, which then leads to a **Clear-back** state (05). + - FITE 22** leads to another **FITE 22** state, which then leads to an **Idle** state (00). + - FITE 23** leads to another **FITE 23** state, which then leads to a call termination (3). +- From **Clear-back** (05), three paths are possible: + - FITE 22** leads to another **FITE 22** state, which then leads to an **Idle** state (00). + - FITE 23** leads to another **FITE 23** state, which then leads to a call termination (4). + - BITE 24** leads to another **BITE 24** state, which then leads to a call termination (3). +- From **Idle** (00), the path leads to a call termination (4). + +**Right Section (Connector reference A):** + +- Starts with a call attempt (1) leading to a series of message states: **BITE 12**, **BITE 14**, **BITE 15**, **BITE 16**, **BITE 17**, **BITE 20**, and **BITEs 9, 10, 19**. +- Each message state has a corresponding return message state: **BITE 12**, **BITE 14**, **BITE 15**, **BITE 16**, **BITE 17**, **BITE 20**, and **BITEs 9, 10, 19**. +- From the return message states, the flow leads to a decision diamond: **Repeat attempt**. +- If **Yes**, it leads to a **Repeat attempt procedure** (P1), which loops back to the initial message states. +- If **No**, it leads to a decision diamond: **Which BITE**. +- From **Which BITE**, three paths are possible based on connector references 9, 10, and 19: + - BITE 9** leads to an **Idle** state (00). + - BITE 10** leads to an **Idle** state (00). + - BITE 19** leads to an **Idle** state (00). + +CCITT - 60 300 + +Flowchart showing interworking of Signalling System No. 7 (TUP) to No. 6. It includes states like 'Answered', 'Clear-back', 'Idle', and 'Repeat attempt', and message types like BITE 12, 14, 15, 16, 17, 20, 25, FITE 22, 23, 24, 9, 10, 19. Connector references A, 3, P1, 4, 3, 4, 3 are on the left. A callout 'CCITT - 60 300' is at the bottom right. + +FIGURE 3/Q.663 (Sheet 2 of 2) + Interworking of Signalling System No. 7 (TUP) to No. 6 \ No newline at end of file diff --git a/marked/Q/T-REC-Q.664-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg b/marked/Q/T-REC-Q.664-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7dbda6c25d5a8997e8aa0b1f96147be82b342b1 --- /dev/null +++ b/marked/Q/T-REC-Q.664-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc0dc68cbf0f10c11da0d30e1fffdf7b32f4aa51f207365b911407be1ac90312 +size 131524 diff --git a/marked/Q/T-REC-Q.664-198811-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg b/marked/Q/T-REC-Q.664-198811-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..365f6c98f6967f306af789009269ea6df139347a --- /dev/null +++ b/marked/Q/T-REC-Q.664-198811-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b44675c5c004c61250161a66e50ad7cf32452c50eb2d056d63de2e75d799fab3 +size 120167 diff --git a/marked/Q/T-REC-Q.664-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.664-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.664-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.664-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/Q/T-REC-Q.664-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..919c670cb21120e5781edcaf79c8064010fced8c --- /dev/null +++ b/marked/Q/T-REC-Q.664-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:631b9b8e23423396e6b14afa80a946bc6db9a22503a3af807bbd6c40b648e455 +size 97414 diff --git a/marked/Q/T-REC-Q.664-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.664-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9be395f2e29e67388dc05415fd73d1291444906 --- /dev/null +++ b/marked/Q/T-REC-Q.664-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3618c13de8a7539d4f395aeb5945a0b4f6304c8b0a8594c7f468a936a64d915 +size 20239 diff --git a/marked/Q/T-REC-Q.664-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/Q/T-REC-Q.664-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4318997f8f6e48cc87e5d377f47a14e35b5d17ed --- /dev/null +++ b/marked/Q/T-REC-Q.664-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1eec5564efb0a8bd63b70aac521fcf7c8dc3ee5f69bfc300786435b1653d5afb +size 100942 diff --git a/marked/Q/T-REC-Q.665-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.665-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ba55fa8e1dc8f08601f64d5b30f999f7c84e9987 --- /dev/null +++ b/marked/Q/T-REC-Q.665-198811-I_PDF-E/raw.md @@ -0,0 +1,214 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.665** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR +INTERWORKING OF SIGNALLING +SYSTEM No. 7 (TUP) TO R1** + +**ITU-T Recommendation Q.665** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.665 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. 7 (TUP) TO R1 + +![State overview diagram showing states 00 through 06 with transitions between them. State 00 is Idle, 01 is Wait for continuity check, 02 is Wait for address-complete, 03 is Wait for register deactivation, 04 is Wait for answer, 05 is Answered, and 06 is Clear-back. Transitions are shown as arrows between states, with some states (01-06) having self-loops.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +``` + + graph LR + 00((00)) --> 01((01)) + 01 --> 02((02)) + 02 --> 03((03)) + 03 --> 04((04)) + 04 --> 05((05)) + 05 --> 06((06)) + 06 --> 00 + 01 --> 01 + 02 --> 02 + 03 --> 03 + 04 --> 04 + 05 --> 05 + 06 --> 06 + +``` + +CCITT-48690 + +State overview diagram showing states 00 through 06 with transitions between them. State 00 is Idle, 01 is Wait for continuity check, 02 is Wait for address-complete, 03 is Wait for register deactivation, 04 is Wait for answer, 05 is Answered, and 06 is Clear-back. Transitions are shown as arrows between states, with some states (01-06) having self-loops. + +| State number | State description | Sheet reference | +|---------------------|--------------------------------|------------------------| +| 00 | Idle | 1, 2 | +| 01 | Wait for continuity check | 1 | +| 02 | Wait for address-complete | 1 | +| 03 | Wait for register deactivation | 1 | +| 04 | Wait for answer | 2 | +| 05 | Answered | 2 | +| 06 | Clear-back | 2 | + +FIGURE 1/Q.665 +State overview diagram for interworking of Signalling System No. 7 (TUP) to R1 + +*Procedures not shown* + +P1 - No transit working is defined for R1. + +FIGURE 2/Q.665 +Note to the interworking of Signalling System No. 7 (TUP) to R1 + +Connector reference + +![Flowchart for the interworking of Signalling System No. 7 (TUP) to R1. The process starts at 'Idle', proceeds to 'Activate I/W No. 7 (TUP)/R1', then 'Wait for continuity check'. It then branches into FITE 1, FITE 25, FITE 24, FITE 22, and FITE 30. FITE 1 leads to connector 6_1. FITE 25 leads to 'Activate outgoing R1', which then leads to a decision 'SPITE 22'. If 'Yes', it goes to P1 and a note 'No transit working is specified for Signalling System R1'. If 'No', it goes to 'Any more FITE 1'. If 'Yes', it goes to 'Country code FITE'. If 'Yes', it goes to 'Omit country code FITE'. If 'No', it goes to FITE 1. FITE 24 leads to 'Idle'. FITE 22 leads to 'Idle'. FITE 30 leads to connector 6_1. 'Omit country code FITE' leads to FITE 1. 'Wait for address complete' (labeled 02) leads to FITE 1, BITE 26, and FITE 22. FITE 1 leads to connector 1_1. BITE 26 leads to BITE 2, which leads to connector 7_2. FITE 22 leads to connector 2_2. Connector references 6, 1, 1, 2, 7 are indicated on the left margin.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> A[/Activate I/W No. 7 (TUP)/R1/] + A --> W[01 Wait for continuity check] + W --> F1_1[/FITE 1/] + W --> F25[/FITE 25/] + W --> F24[/FITE 24/] + W --> F22_1[/FITE 22/] + W --> F30[/FITE 30/] + F1_1 --> C6_1((6 1)) + F25 --> AO[Activate outgoing R1] + AO --> SPITE22{SPITE 22} + SPITE22 -- Yes --> P1((P1)) + P1 -.-> Note1[No transit working is specified for Signalling System R1] + SPITE22 -- No --> AnyMoreFITE1{Any more FITE 1} + AnyMoreFITE1 -- Yes --> CountryCodeFITE{Country code FITE} + CountryCodeFITE -- Yes --> Omit[Omit country code FITE] + CountryCodeFITE -- No --> F1_2[/FITE 1/] + Omit --> F1_2 + F24 --> Idle2([Idle]) + F22_1 --> Idle3([Idle]) + F30 --> C6_2((6 1)) + F1_2 --> C1_1((1 1)) + WAC[02 Wait for address complete] --> F1_3[/FITE 1/] + WAC --> BITE26[/BITE 26/] + WAC --> F22_2[/FITE 22/] + F1_3 --> C1_2((1 1)) + BITE26 --> BITE2[/BITE 2/] + BITE2 --> C7_2((7 2)) + F22_2 --> C2_2((2 2)) + Note2[Artificial] -.-> WAC + +``` + +Flowchart for the interworking of Signalling System No. 7 (TUP) to R1. The process starts at 'Idle', proceeds to 'Activate I/W No. 7 (TUP)/R1', then 'Wait for continuity check'. It then branches into FITE 1, FITE 25, FITE 24, FITE 22, and FITE 30. FITE 1 leads to connector 6\_1. FITE 25 leads to 'Activate outgoing R1', which then leads to a decision 'SPITE 22'. If 'Yes', it goes to P1 and a note 'No transit working is specified for Signalling System R1'. If 'No', it goes to 'Any more FITE 1'. If 'Yes', it goes to 'Country code FITE'. If 'Yes', it goes to 'Omit country code FITE'. If 'No', it goes to FITE 1. FITE 24 leads to 'Idle'. FITE 22 leads to 'Idle'. FITE 30 leads to connector 6\_1. 'Omit country code FITE' leads to FITE 1. 'Wait for address complete' (labeled 02) leads to FITE 1, BITE 26, and FITE 22. FITE 1 leads to connector 1\_1. BITE 26 leads to BITE 2, which leads to connector 7\_2. FITE 22 leads to connector 2\_2. Connector references 6, 1, 1, 2, 7 are indicated on the left margin. + +FIGURE 3/Q.665 (Sheet 1 of 2) + Interworking of Signalling System No. 7 (TUP) to R1 + +TI104880-87 + +![State transition diagram for Signalling System No. 7 (TUP) to R1 interworking. The diagram shows two main state transition paths. The left path starts at state 03 (Wait for register deactivation), transitions through BITE 27 and FITE 22 to state 04 (Wait for answer), then through BITE 22, FITE 23, and FITE 22 to terminal states 4 and 3. The right path starts at state 05 (Answered), transitions through BITE 25, FITE 23, and FITE 22 to state 06 (Clear-back), then through BITE 22, FITE 23, and FITE 22 to state Idle. Various connector references (7, 4, 2, 3, 5) and multiplicities (1, 2, 3X) are indicated on the transitions.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +Connector +reference + +7, 4 + +2, 2 + +5 +3 +4 + +2 +2 + +3, 4 +4, 5 + +``` + +stateDiagram-v2 + direction TB + + %% Left Flow + [*] --> 03 : 7 (1) + state 03 { + Wait for register deactivation + } + 03 --> BITE27_in + BITE27_in --> FITE22_out : FITE 22 + FITE22_out --> [*] : 2 (2) + BITE27_in --> BITE27_out : BITE 27 + BITE27_out --> 04 : 3 (2) + + state 04 { + Wait for answer + } + 04 --> BITE22_in + 04 --> FITE23_in + 04 --> FITE22_in_2 : FITE 22 + FITE22_in_2 --> [*] : 2 (2) + BITE22_in --> BITE22_out : BITE 22 + FITE23_in --> FITE23_out : FITE 23 + BITE22_out --> [*] : 4 (2) + FITE23_out --> [*] : 3 (2) + + %% Right Flow + [*] --> 05 : 4 (2 (3X)) + state 05 { + Answered + } + 05 --> BITE25_in + 05 --> FITE23_in_2 + 05 --> FITE22_in_3 : FITE 22 + FITE22_in_3 --> [*] : 2 (2) + BITE25_in --> BITE25_out : BITE 25 + FITE23_in_2 --> FITE23_out_2 : FITE 23 + FITE23_out_2 --> [*] : 4 (2) + BITE25_out --> 06 : 5 (2) + + state 06 { + Clear-back + } + 06 --> BITE22_in_2 + 06 --> FITE23_in_3 + 06 --> FITE22_in_4 : FITE 22 + FITE22_in_4 --> 2_X3 : 2 (1, 2 (X3)) + 2_X3 --> FITE22_out_2 : FITE 22 + FITE22_out_2 --> Idle + BITE22_in_2 --> BITE24_out : BITE 24 + FITE23_in_3 --> FITE23_out_3 : FITE 23 + BITE24_out --> [*] : 4 (2) + FITE23_out_3 --> [*] : 5 (2) + +``` + +T1104885-87 + +State transition diagram for Signalling System No. 7 (TUP) to R1 interworking. The diagram shows two main state transition paths. The left path starts at state 03 (Wait for register deactivation), transitions through BITE 27 and FITE 22 to state 04 (Wait for answer), then through BITE 22, FITE 23, and FITE 22 to terminal states 4 and 3. The right path starts at state 05 (Answered), transitions through BITE 25, FITE 23, and FITE 22 to state 06 (Clear-back), then through BITE 22, FITE 23, and FITE 22 to state Idle. Various connector references (7, 4, 2, 3, 5) and multiplicities (1, 2, 3X) are indicated on the transitions. + +FIGURE 3/Q.665 (Sheet 2 of 2) +Interworking of Signalling System No. 7 (TUP) to R1 \ No newline at end of file diff --git a/marked/Q/T-REC-Q.671-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.671-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2da5eed29c3555cd1112aa3e8052b379bc5607de --- /dev/null +++ b/marked/Q/T-REC-Q.671-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ea8cbfe9027ff1527f3a936add437b63fd94e8a499e5c74e0f608786b32f2a4 +size 7270 diff --git a/marked/Q/T-REC-Q.671-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/Q/T-REC-Q.671-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e07eacbc75764c57400db3361faef44add4055d7 --- /dev/null +++ b/marked/Q/T-REC-Q.671-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:979dec395fcffbee60f88bd1e331d6fdb306e75b3babc64053bcf0d20a664ad0 +size 106683 diff --git a/marked/Q/T-REC-Q.671-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.671-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..390d5777edf28491c164be5b712fc01164d52ed8 --- /dev/null +++ b/marked/Q/T-REC-Q.671-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f831c413179206086bbb4a15e5b76a599491efa08d0612934c31d21399d998d +size 14708 diff --git a/marked/Q/T-REC-Q.671-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/Q/T-REC-Q.671-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79dd16a4e8b9e3e43833a1c44f2ff3ad0f459409 --- /dev/null +++ b/marked/Q/T-REC-Q.671-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdec8067c5edcfb256ad9620d7439718e6c18d7ee8dfd96ce69eb4d0b025de8a +size 65922 diff --git a/marked/Q/T-REC-Q.68-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.68-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2fd56c412107265037dcccbc5b3a53e7efdff13 --- /dev/null +++ b/marked/Q/T-REC-Q.68-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:916919c492b3fc6084b32dcfc0e658dfb84d5e6999bf565ab8c104950bc01bab +size 8276 diff --git a/marked/Q/T-REC-Q.681-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.681-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.681-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.681-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/Q/T-REC-Q.681-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83585f1ecf945252ab7922e1bbb868c63b7dd85c --- /dev/null +++ b/marked/Q/T-REC-Q.681-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a09f792003d8f0d137e7adc85b87a9dc6fc8a09df690ff01d5985e5316e50ee6 +size 147246 diff --git a/marked/Q/T-REC-Q.681-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.681-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b2fcafd88b184848550c0e9fd2b188f57c0bbf7 --- /dev/null +++ b/marked/Q/T-REC-Q.681-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7789a0403361f4066f91f6ef3f7725de59bce3f05ee43f7b457ff0913b336a54 +size 19849 diff --git a/marked/Q/T-REC-Q.702-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.702-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b995186cf3e809643923f59e6417b6a0487e96ff --- /dev/null +++ b/marked/Q/T-REC-Q.702-198811-I_PDF-E/raw.md @@ -0,0 +1,207 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.702** + +**SPECIFICATIONS OF SIGNALLING SYSTEM No. 7** + +--- + +**SIGNALLING DATA LINK** + +**ITU-T Recommendation Q.702** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.702 was published in Fascicle VI.7 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# SIGNALLING DATA LINK + +## 1 General + +1.1 A *signalling data link* is a bidirectional transmission path for signalling, comprising two *data channels* operating together in opposite directions at the same data rate. It constitutes the lowest functional level (level 1) in the Signalling System No. 7 functional hierarchy. + +1.2 Functional configuration of a signalling data link is shown in Figure 1/Q.702. + +1.3 A digital signalling data link is made up of digital *transmission channels*1) and digital switches or their terminating equipment providing an interface to signalling terminals. The digital transmission channels may be derived from a digital multiplex signal at 1544, 2048 or 8448 kbit/s having a frame structure as defined in Recommendation G.704 [1], or from digital multiplex streams having a frame structure specified for data circuits (Recommendations X.50 [4], X.51 [5], X.50 bis [6], X.51 bis [7]). + +1.4 An analogue signalling data link is made up of voice-frequency analogue transmission channels either 4 kHz or 3 kHz spaced, and modems. + +1.5 Signalling System No. 7 is capable of operating over both terrestrial and satellite *transmission links*1). + +--- + +1) The terms *transmission channel* and *transmission link* are used in Signalling System No. 7 instead of transfer channel and transfer link used in Signalling System No. 6. + +![Diagram a) Example 1 – Digital signalling data link via digital switch block. The diagram shows two 'Level 2' blocks connected to 'Digital switch block' units. These units are connected to a central 'Transmission link' (dashed box) via 'Transmission channel (digital)' lines. The entire setup is enclosed in a 'Data channel' (top) and 'Level 1 signalling data link (digital)' (bottom) boundary.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +Diagram a) Example 1 – Digital signalling data link via digital switch block. The diagram shows two 'Level 2' blocks connected to 'Digital switch block' units. These units are connected to a central 'Transmission link' (dashed box) via 'Transmission channel (digital)' lines. The entire setup is enclosed in a 'Data channel' (top) and 'Level 1 signalling data link (digital)' (bottom) boundary. + +a) Example 1 – Digital signalling data link via digital switch block + +![Diagram b) Example 2 – Signalling data link (digital or analogue) via interface equipment. The diagram shows two 'Level 2' blocks connected to 'Interface function (see Note)' units. These units are connected to a central 'Transmission link' (dashed box) via 'Transmission channel' lines. The entire setup is enclosed in a 'Data channel' (top) and 'Level 1 signalling data link (digital or analogue)' (bottom) boundary. The text 'CCITT-34980' is visible in the bottom right corner of the diagram area.](9e6062272bbe3ddbb7c0606721d64cf0_img.jpg) + +Diagram b) Example 2 – Signalling data link (digital or analogue) via interface equipment. The diagram shows two 'Level 2' blocks connected to 'Interface function (see Note)' units. These units are connected to a central 'Transmission link' (dashed box) via 'Transmission channel' lines. The entire setup is enclosed in a 'Data channel' (top) and 'Level 1 signalling data link (digital or analogue)' (bottom) boundary. The text 'CCITT-34980' is visible in the bottom right corner of the diagram area. + +*Note* – The interface function is provided, for example, by a modem in an analogue signalling data link, a data circuit terminating equipment (DCE) or a time slot access equipment in a digital signalling data link. + +b) Example 2 – Signalling data link (digital or analogue) via interface equipment + +FIGURE 1/Q.702 +Functional configuration of a signalling data link + +1.6 The operational signalling data link shall be exclusively dedicated to the use of a Signalling System No. 7 signalling link between two signalling points. No other information should be carried by the same channel together with the signalling information. + +1.7 Equipment such as echo suppressors, digital pads, or A/μ law convertors attached to the transmission link must be disabled in order to assure full duplex operation and bit integrity of the transmitted data stream. + +1.8 64-kbit/s digital signalling channels entering a digital exchange via a multiplex structure shall be switchable as semi-permanent channels in the exchange. + +## 2 Signalling bit rate + +### 2.1 General + +2.1.1 The standard bit rate on a digital bearer will be 64 kbit/s. + +2.1.2 Lower bit rates may be adopted for each application, taking into account the User Part requirements and the capability of available transmission links. + +2.1.3 The minimum signalling bit rate for telephone call control applications will be 4.8 kbit/s. For other applications such as network management, bit rates lower than 4.8 kbit/s can also be used. + +### 2.2 *Use of bit rates lower than 64 kbit/s* + +2.2.1 For national telephone call control applications, use of Signalling System No. 7 at bit rates lower than 64 kbit/s shall take account of the requirement to minimize the answer signal delay when in-band line signalling systems are involved (Recommendation Q.27 [8]). + +2.2.2 Signalling System No. 7 can be used for direct international application at bit rates lower than 64 kbit/s between countries which have no in-band line signalling systems in their national extension networks (see § 2.1.3). + +2.2.3 The possible use of Signalling System No. 7 at bit rates lower than 64 kbit/s between countries which have in-band line signalling systems in their national extension networks is for further study. + +## 3 **Error characteristics and availability** + +Error characteristics and availability requirements will conform to relevant Recommendations (for example, Recommendation G.821 [9] on digital circuits). No additional characteristics or requirements will be specified in this Recommendation. + +## 4 **Interface specification points** + +4.1 Interface requirements may be specified at one of three points, A, B or C in Figure 2/Q.702. The appropriate point depends on the nature of transmission links used and the approach toward the implementation of interface equipment adopted by each Administration. + +4.2 For the international application, interface requirements at either Point B or Point C will apply. + +4.3 Interface requirements for an international digital signalling data link will be specified at Point C in accordance with the specific multiplex structure used (see § 5.) + +4.4 Interface requirements for an international analogue signalling data link will be specified at Point B on a single channel basis, and thus are independent of multiplex equipment used. (See § 6.) + +4.5 Interface at Point A may or may not appear in particular implementations, as each Administration may adopt different approaches towards the implementation of interface equipment. If it does appear in implementations, then the interface requirements specified in Recommendations V.10 [10], V.11 [11], V.24 [12], V.28 [13], V.35 [14], V.36 [15], X.24 [16] and G.703 [17] (for 64-kbit/s interface) should be followed as appropriate. + +4.6 Implementations which do not follow all the requirements in the relevant Recommendations cited above should nevertheless take into account those requirements that are specified for testing and maintenance actions which require communication between the two ends of a data link. Interface requirements for testing and maintenance are specified in Recommendation Q.707. + +![Diagram of Example 1: Digital signalling data link via a digital switch block. A 'Signalling terminal' is connected to a 'Digital switch block'. Point C is marked on the output of the switch block, which is connected to a 'Multiplexed transmission link'.](547f726730e589392f239257a833ede3_img.jpg) + +Diagram of Example 1: Digital signalling data link via a digital switch block. A 'Signalling terminal' is connected to a 'Digital switch block'. Point C is marked on the output of the switch block, which is connected to a 'Multiplexed transmission link'. + +a) Example 1 – Digital signalling data link via a digital switch block + +![Diagram of Example 2: Signalling data link (digital or analogue) via interface equipment. A 'Signalling terminal' is connected to 'Interface equipment' at Point A. 'Interface equipment' is connected to 'Multiplex equipment' at Point B. Point C is marked on the output of the multiplex equipment, which is connected to a 'Multiplexed transmission link'. 'Other channels' are also shown entering the multiplex equipment. The diagram is labeled CCITT-34990.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) + +Diagram of Example 2: Signalling data link (digital or analogue) via interface equipment. A 'Signalling terminal' is connected to 'Interface equipment' at Point A. 'Interface equipment' is connected to 'Multiplex equipment' at Point B. Point C is marked on the output of the multiplex equipment, which is connected to a 'Multiplexed transmission link'. 'Other channels' are also shown entering the multiplex equipment. The diagram is labeled CCITT-34990. + +b) Example 2 – Signalling data link (digital or analogue) via interface equipment + +FIGURE 2/Q.702 +Interface specification points + +## 5 Digital signalling data link + +### 5.1 Signalling data link derived from the 2048-kbit/s digital path + +When a signalling data link is to be derived from a 2048-kbit/s digital path, the following shall apply: + +- The interface requirements, specified at Point C in Figure 2/Q.702, should comply with Recommendations G.703 [17] for the electrical characteristics and G.704 [1] for the functional characteristics, in particular the frame structure. +- The signalling bit rate shall be 64 kbit/s. +- The standard channel time slot for the use of a signalling data link is time slot 16. When time slot 16 is not available, any channel time slot available for 64-kbit/s user transmission may be used. +- No bit inversion is performed. + +### 5.2 Signalling data link derived from the 8448-kbit/s digital path + +When a signalling data link is to be derived from a 8448-kbit/s digital link, the following shall apply: + +- The interface requirements, specified at Point C in Figure 2/Q.702, should comply with Recommendations G.703 [23] for the electrical characteristics and G.704 [1] for the functional characteristics, in particular the frame structure. +- The signalling bit rate shall be 64 kbit/s. +- The standard channel time slots for the use of a signalling data link are time slots 67 to 70 in descending order of priority. When they are not available, any channel time slot available for 64-kbit/s user transmission may be used. +- No bit inversion is performed. + +### 5.3 *Signalling data link derived from the 1544-kbit/s digital path* + +(For further study.) + +*Note* - When a signalling bit rate of 64 kbit/s is adopted, the values of bits should be inverted within the signalling terminal or the interface equipment in order to meet the minimum mark density requirements of the Recommendation G.733 [2] based PCM systems. + +### 5.4 *Signalling data link established over a digital path made up by digital sections based on different digital hierarchies* + +When a signalling data link is to be established between networks based on different digital hierarchies and speech encoding laws, the following shall apply: + +- a) The interface requirements, specified at Point C in Figure 2/Q.702, should comply with Recommendations G.703 [17] for the electrical characteristics and G.802 [3] for other aspects, e.g., for interworking arrangements. +- b) The signalling bit rate shall be 64 kbit/s. +- c) No bit inversion is performed. + +### 5.5 *Signalling data link established over data circuits* + +When a signalling data link is to be established over data circuits derived from a 64-kbit/s digital stream having a frame structure as specified in such Recommendations as X.50 [10], X.51 [11], X.50 *bis* [12] and X.51 *bis* [13] the following shall apply: + +- a) The interface requirements, specified at Point C in Figure 2/Q.702, should comply with relevant requirements in one of the above-mentioned Recommendations, applicable to the environment of the intended use. +- b) When 64-kbit/s multiplexed streams are carried on 2048-kbit/s or 1544-kbit/s digital links, Recommendation G.704 [1], should apply + +## 6 **Analogue signalling data link** + +### 6.1 *Signalling bit rate* + +6.1.1 Applications of the analogue signalling data link must take account of the delay requirements described in § 2.2. + +6.1.2 For telephone call control applications, the signalling bit rate over an analogue signalling data link shall be higher or equal to 4.8 kbit/s. + +### 6.2 *Interface requirements* + +In case of 4.8-kbit/s operation, interface requirements specified at the interface point B in Figure 2/Q.702 should comply with relevant requirements specified for 4.8-kbit/s modems in Recommendations V.27 [18] and V.27 *bis* [19]. In addition, the following shall apply: + +- a) Application of either Recommendations V.27 [18] or V.27 *bis* [19] depends on the quality of the analogue transmission channels used. Recommendation V.27 [18] shall apply only to transmission channels conforming to Recommendation M.1020 [20], while Recommendation V.27 *bis* [19] to transmission channels conforming to Recommendation M.1020 [20] or of lower quality. +- b) Full duplex operation over a 4-wire transmission link should be adopted. +- c) If a separate modem is to be used, the interface requirements specified in Recommendations V.10 [10], V.11 [11], V.24 [12] and V.28 [13], applicable at Point A in Figure 2/Q.702, should be followed as much as possible. + +## References + +- [1] CCITT Recommendation *Functional characteristics of interfaces associated with network nodes*, Vol. III, Rec. G.704. +- [2] CCITT Recommendation *Characteristics of primary PCM multiplex equipment operating at 1544 kbit/s*, Vol. III, Rec. G.733. +- [3] CCITT Recommendation *Interconnection of digital paths using different techniques*, Vol. III, Rec. G.802. +- [4] CCITT Recommendation *Fundamental parameters of a multiplexing scheme for the international interface between synchronous data networks*, Vol. VIII, Rec. X.50. +- [5] CCITT Recommendation *Fundamental parameters of a multiplexing scheme for the international interface between synchronous data networks*, Vol. VIII, Rec. X.51. +- [6] CCITT Recommendation *Fundamental parameters of a 48-kbit/s user data signalling rate transmission scheme for the international interface between synchronous data networks*, Vol. VIII, Rec. X.50 bis. +- [7] CCITT Recommendation *Fundamental parameters of a 48-kbit/s user data signalling rate transmission scheme for the international interface between synchronous data networks using 10-bit envelope structure*, Vol. VIII, Rec. X.51 bis. +- [8] CCITT Recommendation *Transmission of the answer signal*, Vol. VI, Rec. Q.27. +- [9] CCITT Recommendation *Error performance on an international digital connection forming part of an integrated services digital network*, Vol. III, Rec. G.821. +- [10] CCITT Recommendation *Electrical characteristics for unbalanced double-current interchange circuits for general use with integrated circuit equipment in the field of data communications*, Vol. VIII, Rec. V.10. +- [11] CCITT Recommendation *Electrical characteristics for balanced double-current interchange circuits for general use with integrated circuit equipment in the field of data communications*, Vol. VIII, Rec. V.11. +- [12] CCITT Recommendation *List of definitions for interchange circuits between data-terminal equipment and data circuit-terminating equipment*, Vol. VIII, Rec. V.24. +- [13] CCITT Recommendation *Electrical characteristics for unbalanced double-current interchange circuits*, Vol. VIII, Rec. V.28. +- [14] CCITT Recommendation *Data transmission at 48 kbit/s per second using 60-108 kHz group band circuits*, Vol. VIII, Rec. V.35. +- [15] CCITT Recommendation *Modems for synchronous data transmission using 60-108 kHz group band circuits*, Vol. VIII, Rec. V.36. +- [16] CCITT Recommendation *List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) on public data networks*, Vol. VIII, Rec. X.24. +- [17] CCITT Recommendation *Physical/electrical characteristics of hierarchical digital interfaces*, Vol. III, Rec. G.703. +- [18] CCITT Recommendation *4800 bit/s per second modems with manual equalizer standardized for use on leased telephone-type circuits*, Vol. VIII, Rec. V.27. +- [19] CCITT Recommendation *4800/2400 bit/s per second modem with automatic equalizer standardized for use on leased telephone-type circuits*, Vol. VIII, Rec. V.27 bis. +- [20] CCITT Recommendation *Characteristics of special quality international leased circuits with special band-width conditioning*, Vol. IV, Rec. M.1020. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.710-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.710-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2cc0f04847e37b670b4b14f0c0d6550836e0e48 --- /dev/null +++ b/marked/Q/T-REC-Q.710-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5759a13aff238ae1fbbdf6b727cc89f8314cf40a07bd667c905d6a85f2075501 +size 25955 diff --git a/marked/Q/T-REC-Q.710-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.710-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/Q/T-REC-Q.710-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.710-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Q/T-REC-Q.710-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1709ff3847c6840e4d4ca48476623aca9993981 --- /dev/null +++ b/marked/Q/T-REC-Q.710-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bde67483b2031c4644e4574f17c13c676e5c977a274313cbc5c3483bd9c9a9d +size 47194 diff --git a/marked/Q/T-REC-Q.710-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.710-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5fcad01493bda132ecad8718931f430bc39b4c9f --- /dev/null +++ b/marked/Q/T-REC-Q.710-198811-I_PDF-E/raw.md @@ -0,0 +1,276 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.710** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**SPECIFICATIONS OF SIGNALLING SYSTEM No. 7** + +--- + +**SIMPLIFIED MTP VERSION FOR SMALL +SYSTEMS** + +**ITU-T Recommendation Q.710** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.710 was published in Fascicle VI.7 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. + +# **SIMPLIFIED MTP VERSION FOR SMALL SYSTEMS** + +## **1 Field of application** + +1.1 This Recommendation is applicable for systems using a simplified MTP version to interface to the public network(s). + +1.2 The MTP functions specified in § 3 of this Recommendation may be applied in general for small systems, e.g., PABX's, remote concentrators, etc., interfacing with the message transfer part described in Recommendations Q.702, Q.703, Q.704 and Q.707. + +1.3 The Recommendation applies only for digital access arrangements. + +1.3.1 In case one channel carries signalling information for more than one multiplex system, at least one additional channel should be pre-assigned as a stand-by signalling link in a multiplex system other than that which contains the active channel. This allows the changeover and changeback procedures specified in §§ 3.4.4 and 3.4.5 to be performed. + +1.3.2 The stand-by channel(s) should not be used as B-channel(s). + +1.4 Only the associated mode of signalling is applicable. + +1.5 A variety of information types may be supported by the signalling system, e.g., relating to circuit switched call control and packet communication. + +## **2 Functional content** + +The functional requirements are as follows: + +2.1 The network call control functions are as specified in Recommendation Q.930 (I.451). + +*Note* - Different network layer protocols (circuit switching and packet switching) may be supported by using the protocol discriminator included in Recommendation Q.930. As an alternative, different network layer entities may access the interface functions directly. In that case, the interface functions will use separate service indicator codes to discriminate the applicable network layer entity. This will be similar to the use of SAPI specified in Recommendation Q.920. Which principle to be applied is determined by the Administration/RPOA. + +2.2 The minimum set of Message Transfer Part functions are specified in Recommendations Q.702, Q.703, Q.704 and Q.707, with the qualifications specified in § 3 of this Recommendation. + +2.3 The additional interface functions required for the proper operation of the D-channel call control functions in combination with the message transfer part functions, are specified in § 4 of this Recommendation (see Figure 1/Q.710). + +![A vertical stack of three rectangular boxes representing function layers. The top box is labeled 'D-CHANNEL CALL CONTROL FUNCTIONS' and has a dashed line pointing to the text 'Defined in Recommendation Q.930 (I.451)'. The middle box is labeled 'INTERFACE FUNCTIONS' and has a dashed line pointing to the text 'Defined in § 4'. The bottom box is labeled 'MTP FUNCTIONS' and has a dashed line pointing to the text 'Defined in § 3'. The boxes are connected by solid vertical lines.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +A vertical stack of three rectangular boxes representing function layers. The top box is labeled 'D-CHANNEL CALL CONTROL FUNCTIONS' and has a dashed line pointing to the text 'Defined in Recommendation Q.930 (I.451)'. The middle box is labeled 'INTERFACE FUNCTIONS' and has a dashed line pointing to the text 'Defined in § 4'. The bottom box is labeled 'MTP FUNCTIONS' and has a dashed line pointing to the text 'Defined in § 3'. The boxes are connected by solid vertical lines. + +CCITT-72960 + +FIGURE 1/Q.710 + +## 3 Message Transfer Part (MTP) functions + +### 3.1 General + +The MTP functions as specified in Recommendations Q.702, Q.703, Q.704 and Q.707 are applicable. However, the following exceptions and modifications to those Recommendations may be applied for the PABX system, see §§ 3.2-3.4. + +In order to prevent fraudulent use of the signalling network, it has to be ensured that no signalling messages generated by a PABX can be routed further than the public exchange to which the PABX has access. The manner in which this is made may be dependent on national circumstances and system implementations. An example of how such a function could be implemented is given in § 3.5. + +### 3.2 Level 1 (Recommendation Q.702) + +Only digital signalling data links are relevant. Recommendation Q.702, § 6, is not applicable. + +### 3.3 Level 2 (Recommendation Q.703) + +#### 3.3.1 Initial alignment procedure (Recommendation Q.703, § 7) + +In the initial alignment procedure specified in Recommendation Q.703, § 7, only the emergency proving is applicable. Thus, in states "aligned" and "proving" of the initial alignment procedure status indication "N" is not sent. + +#### 3.3.2 Processor outage (Recommendation Q.703, § 8) + +The processor outage function specified in Recommendation Q.703, § 8, is not applicable. + +When the level 2 function receives an indication that a processor outage situation exists at the remote and (through the reception of status signal units indicating processor outage), it transmits status signal units indicating "out of service". + +#### 3.3.3 *Flow control* (Recommendation Q.703, § 9) + +The sending of the link status indication "B" from the PABX is not applicable. + +When the level 2 function of the PABX receives the link status indication "B", no action is taken by the PABX. + +### 3.4 *Level 3* (Recommendation Q.704) + +#### 3.4.1 *Routing label* (Recommendation Q.704, § 2.2) + +The signalling link selection (SLS) field defined in § 2.2.4 is always coded 0000. + +#### 3.4.2 *Message routing function* (Recommendation Q.704, § 2.3) + +The load sharing function between link sets and within a link set defined in § 2.3.2 is not applicable. + +#### 3.4.3 *Message discrimination* (Recommendation Q.704, § 2.4) + +The discrimination function defined in § 2.4.1 is not applicable. + +#### 3.4.4 *Changeover* (Recommendation Q.704, § 5) + +Changeover between link sets is not applicable. + +Initiation of changeover at the reception of a changeover order from the remote end of a link is not applicable (c.f. Recommendation Q.704, § 3.2.2). + +The buffer updating procedure defined in § 5.4 is not applicable. + +At reception of a changeover order (or emergency changeover order) an emergency changeover acknowledgement is sent in response. + +The message retrieval procedure defined in § 5.5 is not applicable. + +Diversion of traffic is performed at expiry of a time-out T1 (c.f. Recommendation Q.704, § 16.8) is started when the changeover is initiated. + +#### 3.4.5 *Changeback* (Recommendation Q.704, § 6) + +Changeback between link sets is not applicable. + +The sequence control procedure defined in § 6.3 is not applicable. At reception of a changeback declaration, a changeback acknowledgement is sent in response. + +For the purpose of ensuring message sequence integrity, the time controlled diversion procedure specified in § 6.4 is used. + +#### 3.4.6 *Forced rerouting* (Recommendation Q.704, § 7) + +Forced rerouting is not applicable. + +#### 3.4.7 *Controlled rerouting* (Recommendation Q.704, § 8) + +Controlled rerouting is not applicable. + +#### 3.4.8 *Signalling point restart* (Recommendation Q.704, § 9) + +Signalling point restart is not applicable. + +#### 3.4.9 *Management inhibiting* (Recommendation Q.704, § 10) + +Management inhibiting is not applicable. + +#### 3.4.10 *Signalling traffic flow control* (Recommendation Q.704, § 11) + +Signalling route set congestion (Recommendation Q.704, § 11.2.3) is not applicable. + +MTP User flow control (Recommendation Q.704, § 11.2.7) is not applicable. + +#### 3.4.11 *Signalling link management* (Recommendation Q.704, § 12.2) + +Only basic link management procedures are applicable. + +#### 3.4.12 *Link set activation* (Recommendation Q.704, § 12.2.4) + +Link set normal activation defined in § 12.2.4.1 is not applicable. + +Link set emergency restart is used in all cases. + +#### 3.4.13 *Transfer prohibited* (Recommendation Q.704, § 13.2) + +The transfer prohibited function is not applicable. At the reception of a TFP message, no action should be taken. + +#### 3.4.14 *Transfer allowed* (Recommendation Q.704, § 13.3) + +The transfer allowed function is not applicable. At the reception of a TFA-message, no action should be taken. + +#### 3.4.15 *Transfer restricted* (Recommendation Q.704, § 13.4) + +The transfer restricted function is not applicable for the PABX. At the reception of the TFR message no action is taken by the PABX. + +#### 3.4.16 *Signalling-route-set-test* (Recommendation Q.704, § 13.5) + +The signalling-route-set-test procedure is not applicable. + +#### 3.4.17 *Transfer controlled* (Recommendation Q.704, §§ 13.7, 13.8) + +The transfer controlled function is not applicable for the PABX. At the reception of the TFC message, no action is taken by PABX. + +#### 3.4.18 *Signalling route-set-congestion-test* (Recommendation Q.704, § 13.9) + +The signalling route-set-congestion-test function is not applicable for the PABX. + +At the reception of signalling-route-set-congestion-test message no action is taken by the PABX. + +#### 3.4.19 *Signalling link test* (Recommendation Q.707, § 2.2) + +The ability to respond to a signalling link test message with a signalling link test acknowledge message must always be provided by the PABX. + +### 3.5 *Example of "Screening Function"* + +*Note* - This paragraph is provided for illustration purposes only. + +At an exchange (which has the capability of acting as an STP) each message received on a PABX access link is + +passed through a "screening function" that checks that the DPC of the message is the same as the SP code of the exchange. If that is the case, the message is sent to the normal MTP message handling functions. Otherwise, the message is discarded. + +## 4 Interface functions + +### 4.1 General + +The task of the interface functions is to provide the layer-to-layer interfaces according to what is specified in Recommendations Q.920, Q.930 on the one hand and in Recommendation Q.704 on the other, see the Figure 2/Q.710. This will include some conversion functions which are specified in § 4.4. + +![Diagram of Figure 2/Q.710 showing the interaction between three entities: D-CHANNEL NETWORK LAYER ENTITY (Q.930), INTERFACE ENTITY (Q.710), and MESSAGE TRANSFER PART - LEVEL 3 (Q.704).](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram illustrates the interaction between three entities in a layered protocol structure. At the top is the **D-CHANNEL NETWORK LAYER ENTITY (Q.930)**. Below it is the **INTERFACE ENTITY (Q.710)**. At the bottom is the **MESSAGE TRANSFER PART - LEVEL 3 (Q.704)**. Vertical arrows indicate bidirectional communication between adjacent entities. A dashed horizontal line separates the top entity from the middle one, labeled "Layer-to-layer interface specified in Recommendations Q.920, Q.930". Another dashed horizontal line separates the middle entity from the bottom one, labeled "Layer-to-layer interface specified in Recommendation Q.704". The code "CCITT-72970" is located at the bottom right of the diagram. + +Diagram of Figure 2/Q.710 showing the interaction between three entities: D-CHANNEL NETWORK LAYER ENTITY (Q.930), INTERFACE ENTITY (Q.710), and MESSAGE TRANSFER PART - LEVEL 3 (Q.704). + +FIGURE 2/Q.710 + +### 4.2 Interactions with the network layer entity (Q.930) + +The layer-to-layer interactions between the network layer and the data link layer of the D-channel protocol are specified in Recommendation Q.920, § 4. The interactions are specified in the form of primitives. The primitive applicable for the primary rate interface structure are: + +DL-DATA-REQUEST/INDICATION + +The DL-DATA-REQUEST primitive is used to request that a network layer message unit be sent. The + +DL-DATA-INDICATION indicates the arrival of a message unit. + +### 4.3 *Interactions with the message transfer part* + +The layer-to-layer interactions between the MTP and the User Parts of Signalling System No. 7 are specified in Recommendations Q.701 and Q.704, Figures 23/Q.704 and 27/Q.704. + +The following primitives are used: + +- a) MTP-TRANSFER (see Recommendation Q.701, § 8.1), +- b) MTP-PAUSE (see Recommendation Q.701, § 8.2), +- c) MTP-RESUME (see Recommendation Q.701, § 8.3). + +### 4.4 *Conversion functions* + +The Table 1/Q.710 shows the association between the D-channel primitives and the Signalling System No. 7 interactions. + +TABLE 1/Q.710 + +| | D-channel | SS No. 7 | +|----------------------|-----------|----------------------------------------| +| Information transfer | DL-DATA | MTP-TRANSFER | +| Flow control | -
- | MTP-PAUSE (STOP)
MTP-RESUME (START) | + +#### 4.4.1 *Information transfer* + +When receiving a DL-DATA-REQUEST primitive from the network layer entity, the interface entity generates a MTP-TRANSFER Request primitive which contains: + +- The message unit associated with the primitive. +- A label consisting of DPC, OPC and SLS. The label is generated by the interface entity on the basis of information regarding the destination of the message. The SLS is coded 0000. + +*Note* - In some implementations where the label is not used for routing purposes, the entire label may be coded "all zeros". + +- A service information octet (SIO) is generated by the interface entity in accordance with a predetermined rule and, as a national option, on the basis of priority information associated with the primitive. The NI is coded 10 or 11. The SI code is determined by the Administration or RPOA. + +*Note* - In the case when the interface functions provide direct access to more than one network layer entity, the SI code will depend on the network layer entity to which the message is associated. + +When receiving a MTP-TRANSFER Indication from the MTP, the interface entity sends a DL-DATA-INDICATION primitive to the network layer entity. + +#### 4.4.2 *Flow control* + +When receiving a MTP-PAUSE indication from the MTP, the interface entity will generate a DL-PAUSE-INDICATION primitive to the network layer entity. + +When receiving a MTP-RESUME indication from the MTP, the interface entity will generate a DL-RESUME-INDICATION primitive to the network layer entity. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.711-200103-I_PDF-E/raw.md b/marked/Q/T-REC-Q.711-200103-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..328014850813528812ffc229de6454e08a99b26a --- /dev/null +++ b/marked/Q/T-REC-Q.711-200103-I_PDF-E/raw.md @@ -0,0 +1,1408 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.711** + +(03/2001) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Signalling +connection control part (SCCP) + +--- + +**Functional description of the signalling +connection control part** + +ITU-T Recommendation Q.711 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701-Q.709 | +| Signalling connection control part (SCCP) | Q.711-Q.719 | +| Telephone user part (TUP) | Q.720-Q.729 | +| ISDN supplementary services | Q.730-Q.739 | +| Data user part | Q.740-Q.749 | +| Signalling System No. 7 management | Q.750-Q.759 | +| ISDN user part | Q.760-Q.769 | +| Transaction capabilities application part | Q.770-Q.779 | +| Test specification | Q.780-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +# **Functional description of the signalling connection control part** + +# **Summary** + +The Q.71X-series Recommendations defines the services of the SCCP. The SCCP is part of SS No. 7 and provides, above the MTP network or networks, connectionless, connection-oriented, routing and management services. + +## **Source** + +ITU-T Recommendation Q.711 was revised by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 1 March 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 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 and field of application ..... | 1 | +| 2 | References..... | 2 | +| 2.1 | Normative references..... | 2 | +| 2.2 | Informative references ..... | 2 | +| 3 | Definitions ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | General characteristics..... | 4 | +| 5.1 | Technique of description ..... | 4 | +| 5.2 | Primitives..... | 5 | +| 5.3 | Peer-to-peer communication..... | 5 | +| 5.4 | Model of the connection-oriented network service ..... | 6 | +| 5.5 | Model of the connectionless network service..... | 6 | +| 5.6 | Contents of the Q.71X-series Recommendations ..... | 7 | +| 6 | Services provided by the SCCP ..... | 7 | +| 6.1 | Connection-oriented services..... | 7 | +| 6.1.1 | Temporary signalling connections..... | 8 | +| 6.1.2 | Permanent signalling connections ..... | 19 | +| 6.2 | Connectionless services ..... | 20 | +| 6.2.1 | Description..... | 20 | +| 6.2.2 | Primitives and parameters of the connectionless service ..... | 21 | +| 6.2.3 | State transition diagram ..... | 24 | +| 6.3 | SCCP management ..... | 24 | +| 6.3.1 | Description..... | 24 | +| 6.3.2 | Primitives and parameters of the SCCP management..... | 24 | +| 7 | Definition of the lower boundary of the SCCP..... | 27 | +| 7.1 | MTP-SAP..... | 27 | +| 7.2 | MTP primitives and parameters..... | 27 | +| 7.2.1 | TRANSFER..... | 28 | +| 7.2.2 | PAUSE..... | 28 | +| 7.2.3 | RESUME..... | 29 | +| 7.2.4 | STATUS ..... | 29 | +| 7.2.5 | Notification of completion of MTP restart procedure ..... | 29 | +| 7.3 | State transition diagram ..... | 29 | +| 8 | Functions provided by the SCCP..... | 33 | + +| | Page | +|------------------------------------------------------------|-------------| +| 8.1 Connection-oriented functions..... | 33 | +| 8.1.1 Functions for temporary signalling connections ..... | 33 | +| 8.1.2 Functions for permanent signalling connections ..... | 33 | +| 8.2 Connectionless service functions..... | 34 | +| 8.3 Management functions..... | 34 | +| 8.4 Routing and translation functions ..... | 34 | + +# **Functional description of the signalling connection control part** + +# **1 Scope and field of application** + +The Signalling Connection Control Part (SCCP) provides additional functions to the Message Transfer Part (MTP) to cater for both connectionless as well as connection-oriented network services to transfer circuit-related and non-circuit-related signalling information and other types of information between exchanges and specialized centres in telecommunication networks (e.g. for management and maintenance purposes) via a Signalling System No. 7 network. + +A functional block above the message transfer part performs the functions and procedures of the SCCP. The SCCP is capable of using the services of the MTP as described in ITU-T Q.701 to ITU-T Q.707, and/or in ITU-T Q.2210. The combination of the MTP and the SCCP is called "network service part" (NSP). + +The network service part follows the principles of the OSI-reference model as defined in ITU-T X.200, providing a subset of the layer 3 services defined in ITU-T X.213. + +It is the intent of ITU-T Q.711, ITU-T Q.712, ITU-T Q.713 and ITU-T Q.714 to specify protocol entities which perform the functions according to the SCCP of the Signalling System No. 7. These protocol entities conform at their lower boundary to the upper boundary conditions specified in ITU-T Q.704 or ITU-T Q.2210 for use of the service offered by the underlying layers. + +The SCCP making use of the services of the MTP, as specified in ITU-T Q.2210, provides the connectionless network service as specified in this Recommendation. A connection-oriented network service can only use the services which are common to ITU-T Q.2210 and ITU-T Q.704 for the MTP. + +ITU-T Q.715 gives guidance on a number of specific issues related to the incorporation of SCCP in actual networks. These guidelines are in their entirety informal and do not specify any requirement. + +The SCCP congestion control procedures may be subject to improvement pending further analysis of the impact of these procedures in different network scenarios and based on the results of operational experience. The overall objectives of the signalling connection control part are to provide the means for: + +- a) logical signalling connections within the Signalling System No. 7 network; +- b) a transfer capability for network service data units with or without the use of logical signalling connections. + +Functions of the SCCP are also used for the transfer of circuit-related and call-related signalling information of the ISDN user part with or without setup of end-to-end logical signalling connections. These functions are described in ITU-T Q.714 and ITU-T Q.730. Figure 1 illustrates the embedding of the SCCP within the Signalling System No. 7. + +![Functional diagram for the SCCP in Signalling System No. 7. The diagram shows three user parts at the top: 'User part type B', 'Other SCCP user', and 'User part type A'. These are connected to a central 'SCCP' block. The 'SCCP' block is connected to a bottom 'MTP' block. A dashed line with a '(Note)' label connects the 'Other SCCP user' to the 'User part type A'.](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +``` + +graph TD + UPB[User part type B] --- SCCP[SCCP] + OSU[Other SCCP user] --- SCCP + UPA[User part type A] --- SCCP + SCCP --- MTP[MTP] + OSU -.->|(Note)| UPA + +``` + +Functional diagram for the SCCP in Signalling System No. 7. The diagram shows three user parts at the top: 'User part type B', 'Other SCCP user', and 'User part type A'. These are connected to a central 'SCCP' block. The 'SCCP' block is connected to a bottom 'MTP' block. A dashed line with a '(Note)' label connects the 'Other SCCP user' to the 'User part type A'. + +T1157170-93 + +NOTE – Interface using the signals as defined in 6.1.1.3.3, i.e. for the connection-oriented network service. + +The ISDN-UP that provides end-to-end signalling as defined in ITU-T Q.730 is a type A user part. + +**Figure 1/Q.711 – Functional diagram for the SCCP in Signalling System No. 7** + +# 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 references contained in 2.1 and 2.2 contain the reference list for ITU-T Q.711, ITU-T Q.712, ITU-T Q.713 and ITU-T Q.714. + +## 2.1 Normative references + +- CCITT *Blue Book*, Fascicle VI.7, Glossary (1988), *Glossary of terms used in Signalling System No. 7*. +- ITU-T Q.701 (1993), *Functional description of the message transfer part (MTP) of Signalling System No. 7*. +- ITU-T Q.704 (1996), *Signalling network functions and messages*. +- ITU-T Q.712 (1996), *Definition and function of signalling connection control part messages*. +- ITU-T Q.713 (2001), *Signalling connection control part formats and codes*. +- ITU-T Q.714 (1996), *Signalling connection control part procedures*. +- ITU-T Q.2210 (1996), *Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140*. +- ITU-T X.210 (1993), *Information technology – Open Systems Interconnection – Basic Reference Model: Conventions for the definition of OSI services*. + +## 2.2 Informative references + +- ITU-T Q.700 (1993), *Introduction to CCITT Signalling System No. 7*. +- ITU-T Q.706 (1993), *Message transfer part signalling performance*. + +- ITU-T Q.715 (1996), *Signalling connection control part user guide*. +- ITU-T Q.716 (1993), *Signalling System No. 7 – Signalling Connection Control Part (SCCP) performance*. +- ITU-T Q.1400 (1993), *Architecture framework for the development of signalling and OA&M protocols using OSI concepts*. +- ITU-T Q.2110 (1994), *B-ISDN ATM adaptation layer – Service specific connection oriented protocol (SSCOP)*. +- ITU-T Q.2140 (1995), *B-ISDN ATM adaptation layer – Service specific coordination function for signalling at the network node interface (SSCF at NNI)*. +- ITU-T X.200 (1994), *Information Technology – Open Systems Interconnection – Basic Reference Model: The basic model*. +- ITU-T X.213 (1995), *Information technology – Open Systems Interconnection – Network service definition (Note)*. + +NOTE – Further study is required to see which new parts of SCCP can use this Recommendation normatively. + +# 3 Definitions + +Definitions of SCCP terms are provided in the glossary of CCITT *Blue Book*, Fascicle VI.7. + +In addition to the definitions referenced, the following definitions apply: + +**3.1 MTP-SAP instance:** A logical point in the MTP network at which an MTP user can access the services provided by the MTP-3 or the MTP-3b and the MTP can deliver its services to the MTP user. + +**3.2 SCCP-SAP instance:** A logical point in the SCCP network at which an SCCP user can access the services provided by the SCCP and the SCCP can deliver its services to the SCCP user. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|---------|-----------------------------------------------| +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband Integrated Services Digital Network | +| B-ISUP | Broadband ISDN User Part (of SS No. 7) | +| DPC | Destination Point Code | +| ISUP | Integrated Services User Part (of SS No. 7) | +| L3 | Level 3 | +| LSB | Least Significant Bit | +| MSB | Most Significant Bit | +| MTP | Message Transfer Part | +| MTP-SAP | SAP to access the services provided by MTP | +| MTP-3 | MTP Level 3 according to ITU-T Q.704 | +| MTP-3b | MTP Level 3 according to ITU-T Q.2210 | +| NI | Network Indicator | + +| | | +|----------|--------------------------------------------------| +| NNI | Network Node Interface | +| NPCI | Network Protocol Control Information | +| NSDU | Network Service Data Unit | +| NSP | Network Service Part | +| OPC | Originating Point Code | +| SAAL | Signalling ATM Adaptation Layer | +| SAP | Service Access Point | +| SCCP | Signalling Connection Control Part (of SS No. 7) | +| SCCP-SAP | SAP to access the services provided by SCCP | +| SDU | Service Data Unit | +| SI | Service Indicator | +| SIO | Service Information Octet | +| SLC | Signalling Link Code | +| SLS | Signalling Link Selection | +| SSCF | Service Specific Coordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| SS No. 7 | ITU-T Signalling System No. 7 | +| STP | Signalling Transfer Point | +| TUP | Telephone User Part (of SS No. 7) | +| UP | User Part (of SS No. 7) | + +# 5 General characteristics + +## 5.1 Technique of description + +The Signalling Connection Control Part (SCCP) is described in terms of: + +- services provided by the SCCP; +- services assumed from the MTP; +- functions of the SCCP. + +The functions of the SCCP are performed by means of the SCCP protocol between two systems that provide the NSP service to the upper layers. + +The service interfaces to the upper layers and to the MTP are described by means of primitives and parameters, as recommended in ITU-T X.200. Figure 2 illustrates the relationship between the SCCP protocol specification and the definition of adjacent services. + +![Figure 2/Q.711 – Relationship between the SCCP protocol specification and the definition of adjacent services. The diagram shows a box on the left labeled 'SCCP protocol specification'. To its right are two boxes: 'Network service definition' at the top and 'MTP service definition' at the bottom. Solid arrows point from the SCCP specification box to both service definition boxes. Dashed lines between the SCCP specification and the service definitions are labeled 'Reference to aims' and 'Reference to assumptions'. A reference code 'T1157180-93' is at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Figure 2/Q.711 – Relationship between the SCCP protocol specification and the definition of adjacent services. The diagram shows a box on the left labeled 'SCCP protocol specification'. To its right are two boxes: 'Network service definition' at the top and 'MTP service definition' at the bottom. Solid arrows point from the SCCP specification box to both service definition boxes. Dashed lines between the SCCP specification and the service definitions are labeled 'Reference to aims' and 'Reference to assumptions'. A reference code 'T1157180-93' is at the bottom right. + +**Figure 2/Q.711 – Relationship between the SCCP protocol specification and the definition of adjacent services** + +## 5.2 Primitives + +Primitives define the information flow associated with the services requested of the SCCP and of the MTP (see Figure 3). + +![Figure 3/Q.711 – Service primitives. This diagram illustrates the interaction between protocol layers. At the top is 'Upper layers'. Below it is a horizontal line labeled 'Services of the SCCP'. Between the upper layers and this line is an oval representing a Service Access Point (SAP), with 'N-Service primitives SCCP-SAP' written above it. Below the SCCP services line is a box labeled 'Signalling connection control part'. Below this box is another horizontal line labeled 'Services of the MTP'. Between the signalling connection control part and the MTP services line is another oval representing an SAP, with 'MTP-SAP' and 'MTP-Service primitives' written to its left. Below the MTP services line is a box labeled 'Message transfer part', with 'Service primitives' written above it. Dashed lines from the text 'Service access points (SAP)' point to both ovals. A reference code 'T1157190-93' is at the bottom right.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Figure 3/Q.711 – Service primitives. This diagram illustrates the interaction between protocol layers. At the top is 'Upper layers'. Below it is a horizontal line labeled 'Services of the SCCP'. Between the upper layers and this line is an oval representing a Service Access Point (SAP), with 'N-Service primitives SCCP-SAP' written above it. Below the SCCP services line is a box labeled 'Signalling connection control part'. Below this box is another horizontal line labeled 'Services of the MTP'. Between the signalling connection control part and the MTP services line is another oval representing an SAP, with 'MTP-SAP' and 'MTP-Service primitives' written to its left. Below the MTP services line is a box labeled 'Message transfer part', with 'Service primitives' written above it. Dashed lines from the text 'Service access points (SAP)' point to both ovals. A reference code 'T1157190-93' is at the bottom right. + +**Figure 3/Q.711 – Service primitives** + +This diagram shows the points at which service primitives are invoked. It is not intended to constrain the architecture. For the architectural considerations, some information is provided in ITU-T Q.1400. + +## 5.3 Peer-to-peer communication + +Exchange of information between two peers of the SCCP is performed by means of a protocol. The protocol is a set of rules and formats by which the control information (and user data) is exchanged between the two peers. The protocol caters for: + +- the set-up of logical signalling connection; +- the release of logical signalling connections; +- the transfer of data with or without logical signalling connections. + +## 5.4 Model of the connection-oriented network service + +A signalling connection is modelled in the abstract by a pair of queues. The protocol elements are objects on that queue added by the origination SCCP user and removed by the destination SCCP user. Each queue represents a flow control function. Figure 4 illustrates the modes described above. + +![Diagram of the connection-oriented network service model between Node A and Node B.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +The diagram illustrates the connection-oriented network service model between Node A and Node B. Both nodes have a 'User of the network service' block. Below this, a large rectangular box represents the network. Inside this box, there are two horizontal queues, each represented by a dashed cylinder. The top queue is labeled 'Queue B to A' and has an arrow pointing from Node B to Node A. The bottom queue is labeled 'Queue A to B' and has an arrow pointing from Node A to Node B. The identifier 'T1157200-93' is located at the bottom right of the diagram. + +Diagram of the connection-oriented network service model between Node A and Node B. + +**Figure 4/Q.711 – Model for the internode communication with the SCCP (connection-oriented services)** + +## 5.5 Model of the connectionless network service + +This service definition uses the abstract model for a layer service defined in clause 5/X.210. The model defines the interactions between the user and the provider of the connectionless network service. These interactions take place at the two SCCP-SAPs (see Figure 5). + +![Diagram of the connectionless network service model between Node X and Node Y.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +The diagram illustrates the connectionless network service model between Node X and Node Y. Both nodes have a 'User of the network service' block. Below Node X is 'SCCP-SAP A' and below Node Y is 'SCCP-SAP B'. A large rectangular box labeled 'Service provider' contains a 'Virtual transient association between A and B', represented by a horizontal line with diagonal lines connecting to the SAPs. The identifier 'T1178310-96' is located at the bottom right of the diagram. + +Diagram of the connectionless network service model between Node X and Node Y. + +**Figure 5/Q.711 – Model of a network connectionless transmission** + +A defining characteristic of network-connectionless transmission is the independent nature of each invocation of the connectionless network service. This basic service has been enhanced to provide sequence integrity between SDUs (see protocol class 1 service). + +The connectionless network service, as provided between SCCP-SAPs, can be modelled in the abstract as a virtual transient association between the SCCP-SAPs (see Note). + +NOTE – This model is intended solely to describe the appearance of the connectionless-mode network service to the SCCP users. It is not intended to be a model of the internal operation of the service provider in providing the connectionless network service. + +Only one type of object, the Unitdata, can be exchanged between the users of the service. This relationship is illustrated in Figure 5. + +## **5.6 Contents of the Q.71X-series Recommendations** + +ITU-T Q.711 contains a general description of the services provided by the MTP, the services provided by the SCCP and the functions within the SCCP. + +ITU-T Q.712 defines the function of the messages, the set of protocol elements and their embedding into messages. + +ITU-T Q.713 describes the formats and codes used for the SCCP messages. + +ITU-T Q.714 is a detailed description of the SCCP procedures as a protocol specification. + +ITU-T Q.715 is the SCCP user guide. Implementation-dependent aspects may be found in ITU-T Q.715. + +ITU-T Q.716 defines and specifies values for the SCCP performance parameters, including quality of service parameters and internal parameters. + +# **6 Services provided by the SCCP** + +The overall set of services is grouped into: + +- connection-oriented services; +- connectionless services. + +Four classes of service are provided by the SCCP protocol, two for connectionless services and two for connection-oriented services. + +The four classes are: + +- 0 basic connectionless class; +- 1 in-sequence delivery connectionless class; +- 2 basic connection-oriented class; +- 3 flow control connection-oriented class. + +In the tables defining individual primitives, the notations given below are used: + +- M indicates a mandatory parameter; +- O indicates an SCCP implementation option; +- C indicates that the parameter is conditional; +- U indicates a user option; +- n.a. not applicable; +- = indicates that the parameter must have the same value in the indication primitive, or confirm primitive as provided in the corresponding request primitive, or response primitive, respectively. + +## **6.1 Connection-oriented services** + +A distinction has to be made between: + +- temporary signalling connections; +- permanent signalling connections. + +Temporary signalling connections are under control (establishment, data transfer including reset, release) of the SCCP user. Further details are given in 6.1.1. + +Permanent signalling connections are established and released by Management (O&M function or management function) and are provided to the SCCP user on a semi-permanent basis, while data transfer including reset is under control of the SCCP user. Further details are given in 6.1.2. + +### **6.1.1 Temporary signalling connections** + +#### **6.1.1.1 Description** + +The control of a signalling connection is divided into the following phases: + +- connection establishment phase; +- data transfer phase; +- connection release phase. + +##### **6.1.1.1.1 Connection establishment phase** + +Connection establishment procedures provide the mechanism for establishing temporary signalling connections between users of the SCCP. + +A signalling connection between two SCCP users may consist of one or more connection sections. A signalling connection between two SCCP users in the same node is considered an implementation-dependent matter. + +During connection establishment, routing functions are provided by the SCCP, in addition to those provided by the MTP. + +At intermediate nodes, SCCP routing determines whether a signalling connection should be realized by one connection or by concatenated connection sections (i.e. coupling of connections). The criteria for deciding on coupling are implementation dependent. + +For connection establishment there are two alternative boundaries between SCCP and SCCP user with different procedures: + +- the "X.213-like" boundary that is described further in 6.1.1.2; +- the "ISUP-embedded" boundary that is described further in 6.1.1.3. + +The "X.213-like" boundary requires that establishment procedures are performed by SCCP while in the case of "ISUP-embedded" boundary the ISUP provides the routing of the request for the set-up of a connection section. + +The connection refusal procedure is invoked if the SCCP or the SCCP user is unable to establish a signalling connection. + +##### **6.1.1.1.2 Data transfer phase** + +The data transfer service provides for an exchange of user data, called Network Service Data Units (NSDUs), in either direction or in both directions simultaneously on a signalling connection. An SCCP message between two peers consists of: + +- Network Protocol Control Information (NPCI); +- Network Service Data Unit (NSDU). + +The network protocol control information supports the joint operating of the SCCP-peer entities within the two nodes communicating with each other. It contains a connection reference parameter which allocates the message to a certain signalling connection. + +The network service data unit contains a certain amount of information from the SCCP user which has to be transferred between two nodes using the service of the SCCP. + +The network protocol control information and the network service data unit are put together and transferred as a message (Figure 6). If the size of user data is too big to be transferred within one + +message, user data are segmented into a number of portions. Each portion is mapped to a separate message, consisting of the NPCI and an NSDU (Figure 7). + +![Diagram showing the relation between NSDU and message without segmentation or blocking. At the top, two boxes labeled 'NPCI' and 'NSDU' are shown. Arrows from both boxes point down to a single, larger box labeled 'Message'. This indicates that one NSDU is mapped directly to one message, with the NPCI added as control information.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +Diagram showing the relation between NSDU and message without segmentation or blocking. At the top, two boxes labeled 'NPCI' and 'NSDU' are shown. Arrows from both boxes point down to a single, larger box labeled 'Message'. This indicates that one NSDU is mapped directly to one message, with the NPCI added as control information. + +T1157210-93 + +NPCI Network Protocol Control Information + NSDU Network Service Data Unit + Message Protocol data unit + +**Figure 6/Q.711 – Relation between NSDU and message + neither segmenting nor blocking** + +![Diagram showing the segmentation of an NSDU into multiple messages. At the top, two boxes labeled 'NPCI' and 'NSDU' are shown. Arrows from the 'NPCI' box point down to two separate boxes labeled 'Message 1' and 'Message 2'. Arrows from the 'NSDU' box are split, with one part pointing to 'Message 1' and another part pointing to 'Message 2'. This indicates that the NSDU is segmented into two messages, each with its own NPCI.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +Diagram showing the segmentation of an NSDU into multiple messages. At the top, two boxes labeled 'NPCI' and 'NSDU' are shown. Arrows from the 'NPCI' box point down to two separate boxes labeled 'Message 1' and 'Message 2'. Arrows from the 'NSDU' box are split, with one part pointing to 'Message 1' and another part pointing to 'Message 2'. This indicates that the NSDU is segmented into two messages, each with its own NPCI. + +T1157220-93 + +**Figure 7/Q.711 – Segmenting** + +The data transfer service caters for sequence control and flow control depending on the quality of service required by the SCCP user (two different classes of the connection-oriented service are provided by the protocol; see ITU-T Q.714). + +##### 6.1.1.1.3 Connection release phase + +Connection release procedures provide the mechanism for disconnecting temporary signalling connections between users of the SCCP. + +#### 6.1.1.2 Network service primitives and parameters applicable to the X.213-like connection-oriented boundary + +##### 6.1.1.2.1 Overview + +Table 1 gives an overview of the primitives to the upper layers and the corresponding parameters for the (temporary) connection-oriented network service. Figure 8 shows an overview state transition diagram for the sequence of primitives at a connection endpoint. Refer to the ITU-T X.213 network service definition for open systems interconnection for ITU-T application. + +**Table 1/Q.711 – Network service primitives for X.213-like connection-oriented services** + +| Primitives | | Parameters | +|------------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Generic name | Specific name | | +| N-CONNECT | Request
Indication
Response
Confirm | Called address
Calling address
Responding address
Expedited data selection
Quality of service parameter set
User data
Importance
Connection identification a) | +| N-DATA | Request
Indication | Importance
User data
Connection identification a) | +| N-EXPEDITED DATA | Request
Indication | User data
Connection identification a) | +| N-DISCONNECT | Request
Indication | Originator
Reason
User data
Responding address
Importance
Connection identification a) | +| N-RESET | Request
Indication
Response
Confirm | Originator
Reason
Connection identification a) | +| N-INFORM b) | Request
Indication | Reason
Connection identification
Quality of service parameter set | + +a) In 5.3/X.213, this parameter is implicit. +b) This primitive is not in ITU-T X.213. + +![State transition diagram for the sequence of primitives at a connection endpoint (basic transitions).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +The diagram illustrates the state transitions between five states: Idle, Outgoing connection pending, Incoming connection pending, Data transfer, and User requested reset pending (also labeled as Provider initiated reset pending). Transitions are triggered by N-DISCONNECT, N-CONNECT, N-RESET, and N-DATA primitives. + +- Idle to Outgoing connection pending:** N-DISCONNECT request, indication +- Outgoing connection pending to Idle:** N-DISCONNECT request, indication +- Outgoing connection pending to Data transfer:** N-CONNECT request REQUEST type 1a), b) +- Data transfer to Outgoing connection pending:** N-CONNECT confirm +- Idle to Incoming connection pending:** N-DISCONNECT request, indication +- Incoming connection pending to Idle:** N-DISCONNECT request, indication +- Incoming connection pending to Data transfer:** N-CONNECT indication REQUEST type 2a), b) +- Data transfer to Incoming connection pending:** N-CONNECT response +- Idle to User requested reset pending:** N-DISCONNECT request, indication +- User requested reset pending to Idle:** N-DISCONNECT request, indication +- User requested reset pending to Data transfer:** N-RESET request +- Data transfer to User requested reset pending:** N-RESET confirm +- Data transfer self-loops:** N-DATA N-EXPEDITED DATA N-INFORMa) (request, indication) +- User requested reset pending self-loop:** N-DATA N-EXPEDITED DATA request, indication +- Provider initiated reset pending self-loop:** N-DATA N-EXPEDITED DATA request, indication +- Outgoing connection pending self-loop:** REPLYa), b) +- Incoming connection pending self-loop:** N-CONNECT indicationb) +- Provider initiated reset pending to Data transfer:** N-RESET response +- Data transfer to Provider initiated reset pending:** N-RESET indication + +T1178320-96 + +State transition diagram for the sequence of primitives at a connection endpoint (basic transitions). + +a) This primitive is not in ITU-T X.213. (See 6.1.1.3.2.) + +b) For user part type A only. + +**Figure 8/Q.711 – State transition diagram for the sequence of primitives at a connection endpoint (basic transitions)** + +A more detailed description for the primitives and their parameters is given in the following clauses. + +##### 6.1.1.2.2 Connection establishment phase + +An SCCP user (calling user) initiates the set-up of the connection by means of the primitive "N-CONNECT request" to the SCCP. The SCCP entity evaluates the primitive and adds the protocol control information. The SCCP message [consisting of the Protocol Control Information (PCI) and possibly an NSDU] is transmitted by means of the MTP-services to the remote peer entity of the SCCP. It evaluates and strips the PCI and sends a primitive "N-CONNECT indication" to the local SCCP user. On both ends of the connection, the status "pending" is assumed. + +The responding SCCP user answers with the primitive "N-CONNECT response" to the local SCCP, which sends the response SCCP message including PCI to the calling SCCP. The calling SCCP sends the primitive "N-CONNECT confirm" to the calling SCCP user. The connection is now ready for data transfer. + +The four types of N-CONNECT applicable to the X.213-like boundary, the request, the indication, the response and the confirm contain the parameters as shown and further described in Table 2. + +**Table 2/Q.711 – Parameters of the primitive N-CONNECT applicable to the X.213-like boundary** + +| Parameter | Primitive | | | | +|-----------------------------------------|-------------------|----------------------|--------------------|---------------------| +| | N-CONNECT request | N-CONNECT indication | N-CONNECT response | N-CONNECT confirm | +| Called address | M | M a2) | n.a. | n.a. | +| Calling address | U a1) | C c1) | n.a. | n.a. | +| Responding address | n.a. | n.a. | U a3) | C c1) | +| Expedited data selection | U | n.a. | U | n.a. | +| Quality of service parameter set | M | M | M | M(=) | +| User data | U | C(=) c1) | U | C(=) c1) | +| Connection identification b) | O | O | O | O | +| Importance | U | O | U | O | + +a1)) This parameter is associated with the SCCP service access point at which this primitive is issued if the calling address is absent. +a2)) This parameter is associated with the SCCP service access point at which this primitive is issued if the called address is absent. +a3)) This parameter is associated with the SCCP service access point at which this primitive is issued if the responding address is absent. +b)) In 5.3/X.213, this parameter is implicit. +c1)) If present in the received SCCP message. + +The parameters "called address/calling address" convey addresses identifying the destination/source of a communication. There are three types of address information elements: + +- global title; +- subsystem number; +- signalling point code (together with the MTP-SAP instance). + +The global title is an address such as dialled digits which does not explicitly contain information that would allow routing in the signalling network, i.e. a translation function is required. The subsystem number is an identification of a specific user function within a certain signalling point (SP), like the ISDN-user part, the SCCP-management, etc. + +The parameter "responding address" identifies the SCCP user to which the connection has been established or refused. + +The "responding address" parameter in the N-CONNECT primitive conveys the address of the SCCP service access point to which the signalling connection has been established. Under certain circumstances (e.g. a general global title identifying replicated subsystems), the value of this parameter may be different from the "called address" in the corresponding N-CONNECT request. + +The "responding address" parameter is present in the N-DISCONNECT primitive only in the case where the primitive is used to indicate rejection of a signalling connection establishment attempt by an SCCP user function. The parameter conveys the address of the service access point from which the N-DISCONNECT request was issued and under circumstances like that mentioned above the "responding address" may be different from the "called address" in the corresponding N-CONNECT request primitive. + +The parameter "expedited data selection" may be used to indicate during set-up whether expedited data can be transferred via the connection. A negotiation will be performed between SCCP users, local and remote. + +The quality of service parameter set is used during call set-up to negotiate the protocol class for the connection and, if applicable, the flow control window size. + +The N-CONNECT primitives may or may not contain user data. + +The parameter "connection identification" is used to allocate a primitive to a certain connection. The connection identification is an internal representation of the "connection endpoint identifier" defined in the OSI-RM. Its use and format is implementation dependent. + +The "importance" parameter is a user optional parameter in request and response primitives that result in the transmission of SCCP messages. Its use allows the SCCP user to assign and indicate to SCCP a certain importance to the primitive. During MTP and/or SCCP congestion, SCCP will take decisions to send out or reject the resulting message, based on this importance and on the severity of the congestion. Its presence in the indication and confirmation primitive is an SCCP implementation option. + +In principle, the connection establishment has to be completed (i.e. data transfer status has to be reached) before sending or receiving data messages. If data messages arrive at the calling user before the connection establishment is finished, these data messages are discarded. + +In addition, user data can also be transferred to and from the SCCP within the primitives N-CONNECT and N-DISCONNECT. + +##### 6.1.1.2.3 Data transfer phase + +During this phase three different primitives may occur: + +- a) N-DATA (Table 3); +- b) N-EXPEDITED DATA (Table 4); +- c) N-RESET (Table 5). + +**Table 3/Q.711 – Parameters of the primitive N-DATA** + +| Parameter | Primitive | | +|---------------------------|----------------|-------------------| +| | N-DATA request | N-DATA indication | +| User data | M | M(=) | +| Connection identification | O | O | +| Importance | U | O | + +**Table 4/Q.711 – Parameters of the primitive N-EXPEDITED DATA** + +| Parameter | Primitive | | +|---------------------------|--------------------------|-----------------------------| +| | N-EXPEDITED DATA request | N-EXPEDITED DATA indication | +| User data | M | M(=) | +| Connection identification | O | O | + +**Table 5/Q.711 – Parameters of the primitive N-RESET** + +| Parameter | Primitive | | | | +|---------------------------|-----------------|--------------------|------------------|-----------------| +| | N-RESET request | N-RESET indication | N-RESET response | N-RESET confirm | +| Originator | (Always NSU) | M | n.a. | n.a. | +| Reason | M | M | n.a. | n.a. | +| Connection identification | O | O | O | O | + +The primitive "N-DATA" (Table 3) exists only as a "request", i.e. from the SCCP user to the local SCCP and as an "indication" at the remote end of the connection, i.e. from the SCCP to the local SCCP user. N-DATA can occur bidirectionally, i.e. from the calling as well as the called user of the SCCP-connection. + +The primitive "N-EXPEDITED DATA" may only be used by the SCCP user in case of protocol class 3 connections. + +The primitive N-RESET (Table 5) can occur in the data transfer state of a connection with a protocol class including flow control. N-RESET overrides all other activities and causes the SCCP to start a re-initialization procedure for sequence numbering. N-RESET appears as a request, an indication, a response and a confirm. After reception of an N-RESET request and before the sending of an N-RESET confirm, all NSDUs from the remote SCCP and the local SCCP user are discarded by the local SCCP. + +The parameter "originator" indicates the source of the reset and can be any of the following: the "network service provider" (network originated), the "network service user" (user originated), or "undefined". The parameter "reason" indicates "network service provider congestion", "reason unspecified" or "local SCCP originated1" for a network originated reset, and indicates "user synchronization" for a user originated reset. The "reason" parameter is "undefined" when the "originator" parameter is "undefined". + +##### 6.1.1.2.4 Release phase + +The primitives for the release phase are N-DISCONNECT request and N-DISCONNECT indication. These primitives are also used for the connection refusal during connection establishment phase. Parameters are included to notify the reason for connection release/refusal and the initiator of the connection release/refusal procedure. User data may be also be included (see Table 6). + +1 These values may be used locally at the originating/initiating node as an implementation option. + +**Table 6/Q.711 – Parameters of the primitive N-DISCONNECT** + +| Parameter | Primitive | | +|-----------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------------| +| | N-DISCONNECT request | N-DISCONNECT indication | +| Originator | (Always NSU) | M | +| Responding address | U a) | C c2), a) | +| Reason | M | M | +| User data | U | C(=) c2) | +| Connection identification | O | O | +| Importance | U | O | +| a) Only applicable in the case of connection refusal.
c2) If present in the received SCCP message. | | | + +The parameter "originator" indicates the initiator of the connection release or the connection refusal. It may assume the following values: + +- the network service provider; +- the network service user; +- undefined. + +The parameter "reason" gives information about the cause of the connection release or the connection refusal. It may assume any of the following values in accordance with the value of the "originator": + +- 1) When the "originator" parameter indicates the "network service provider": + - disconnection – abnormal condition of non-transient nature; + - disconnection – abnormal condition of transient nature; + - disconnection – invalid state1; + - disconnection – release in progress1; + - connection refusal2 – destination address unknown (non-transient condition); + - connection refusal2 – destination inaccessible/non-transient condition; + - connection refusal2 – destination inaccessible/transient condition; + - connection refusal2 – QOS not available/non-transient condition; + - connection refusal2 – QOS not available/transient condition; + - connection refusal2 – reason unspecified/non-transient condition; + - connection refusal2 – reason unspecified/transient condition; + - connection refusal2 – local error1; + - connection refusal2 – invalid state1; + - connection refusal2 – no translation1; + - connection refusal2 – in restart phase1; + - connection refusal2 – hop counter violation. + +2 It is noted that the term "connection rejection" is used in ITU-T X.213 for the "reason" parameter values. + +- 2) When the "originator" parameter indicates the "network service user": + - disconnection – normal condition; + - disconnection – abnormal condition; + - disconnection – end user congestion; + - disconnection – end user failure; + - disconnection – SCCP user originated; + - disconnection – access congestion; + - disconnection – access failure; + - disconnection – subsystem congestion; + - connection refusal2 – non-transient condition; + - connection refusal2 – transient condition; + - connection refusal2 – incompatible information in NSDUs; + - connection refusal2 – end user originated; + - connection refusal2 – end user congestion; + - connection refusal2 – end user failure; + - connection refusal2 – SCCP user originated; + - connection refusal2 – access congestion; + - connection refusal2 – access failure; + - connection refusal2 – subsystem congestion. +- 3) When the "originator" parameter is "undefined", then the "reason" parameter is also "undefined". + +#### **6.1.1.3 Network service primitives, interface elements and parameters applicable to the ISUP-embedded connection-oriented boundary** + +##### **6.1.1.3.1 Overview** + +Table 7 gives an overview of the primitives to the SCCP user layer and the corresponding parameters for the (temporary) "ISUP-embedded" connection-oriented network service. The state transition diagram for the sequences of the primitives at a connection endpoint is left for further study. + +**Table 7/Q.711 – Network service primitives and interface elements for ISUP embedded connection-oriented services** + +| Primitives | | Parameters | +|------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Generic name | Specific name | | +| N-CONNECT | Indication
Response
Confirm | Called address
Calling address
Responding address
Expedited data selection
Quality of service parameter set
User data
Importance
Connection identification a) | +| N-DATA | Request
Indication | Importance
User data
Connection identification a) | +| N-EXPEDITED DATA | Request
Indication | User data
Connection identification a) | +| N-DISCONNECT | Request
Indication | Originator
Reason
User data
Responding address
Importance
Connection identification a) | +| N-RESET | Request
Indication
Response
Confirm | Originator
Reason
Connection identification a) | +| N-INFORM | Request
Indication | Reason
Connection identification
Quality of service parameter set | +| REQUEST type 1 | – | Connection identification
Expedited data selection
Quality of service parameter set | +| REQUEST type 2 | – | Quality of service parameter set
Connection identification
Source local reference
Originating signalling point code
Reply request | +| REPLY | – | Source local reference
Quality of service parameter set
Connection identification a) | + +a) In 5.3/X.213, this parameter is implicit. + +##### 6.1.1.3.2 Notice service + +The provision of the notice service by use of the "N-INFORM" primitive is implementation dependent. + +The primitive N-INFORM (Table 8) is used during data transfer to convey relevant network/user information. The primitive "N-INFORM" will contain the parameters "reason", "connection identification" and "QOS parameter set". + +**Table 8/Q.711 – Parameters of the primitive N-INFORM** + +| Parameter | Primitive | | +|---------------------------|------------------|---------------------| +| | N-INFORM request | N-INFORM indication | +| Reason | M | M | +| Connection identification | O | O | +| QOS parameter set | C c3) | C c3) | + +c3) Present in inform reasons that lead to a QOS parameter set change. + +The primitive "N-INFORM request" is provided to inform the local SCCP of the connection user failure/congestion, or anticipated QOS changes. A further primitive "N-INFORM indication" is provided to indicate actual failures of the local SCCP to the SCCP-user functions or anticipated quality of service changes or other indications to the SCCP-user functions. + +The parameter "reason" contains the network/user information to be conveyed. It may assume the following values: + +- network service provider failure; +- network service congestion; +- network service provider QOS change; +- network service user failure; +- network service user congestion; +- network service user QOS change; +- reason unspecified. + +##### 6.1.1.3.3 Connection establishment making use of the ISUP-embedded procedures + +An SCCP user (calling user) may, instead of using the N-CONNECT request thereby requesting SCCP to transmit an appropriate PDU, use the REQUEST to solicit the SCCP to provide in the REPLY information relevant for connection establishment. The forward direction of the connection is established hop-by-hop making use of PDUs of ISUP thereby is embedded in the forward call set-up. In the backward direction, normal SCCP PDUs are used. The N-CONNECT request is replaced at the origin by the two interface elements REQUEST type 1 and REPLY. Within intermediate nodes the two interface elements REQUEST type 2 and REPLY are required. + +The three types of N-CONNECT applicable to the ISUP embedded boundary, the indication, the response and the confirm contain the parameters as shown in Table 9. + +**Table 9/Q.711 – Parameters of the primitive N-CONNECT applicable to the ISUP embedded boundary** + +| Parameter | Primitive | | | +|----------------------------------|----------------------|--------------------|---------------------| +| | N-CONNECT indication | N-CONNECT response | N-CONNECT confirm | +| Called address | O | n.a. | n.a. | +| Calling address | n.a. | n.a. | n.a. | +| Responding address | n.a. | U a1) | C c3) | +| Expedited data selection | n.a. | U | n.a. | +| Quality of service parameter set | O | M | M(=) | +| User data | n.a. | U | C(=) c3) | +| Connection identification | O | O | O | +| Importance | n.a. | U | O | + +a1) This parameter is associated with the SCCP service access point at which this primitive is issued if the responding address is absent. +c3) If present in the received SCCP message. + +Three interface elements are defined for the information flow between SCCP and ISDN-user part: + +- a) REQUEST to the SCCP, type 1 and type 2; +- b) REPLY from the SCCP. + +The REQUEST type 1 contains the following parameters: + +- connection identification (O); +- expedited data selection (U); +- quality of service parameter set (U). + +The REQUEST type 2 contains the following parameters: + +- quality of service parameter set (M); +- connection identification (O); +- source local reference (M); +- originating signalling point code (M); +- reply request (U); +- refusal indicator (U). + +The REPLY contains the following parameters: + +- source local reference (M); +- quality of service parameter set (M); +- connection identification (O). + +### 6.1.2 Permanent signalling connections + +#### 6.1.2.1 Description + +The set-up/release service is controlled by the administration (e.g. OMAP). The functions for set-up and release may be similar to those provided for temporary signalling connections. The classes of service are the same. + +Permanently established signalling connections may require additional safeguarding mechanisms within the endpoints (relay points) of the connection in order to guarantee their re-establishment in case of a malfunction followed by a recovery. + +#### 6.1.2.2 Primitives and parameters + +The primitives and their parameters are listed in Table 10. Their content and functionality correspond to the description within 6.1.1.2.3. + +**Table 10/Q.711 – Primitives for the data transfer on permanent connections** + +| Primitives | | Parameters | +|------------------|----------------------------------------------|------------------------------------------------------| +| Generic name | Specific name | | +| N-DATA | Request
Indication | Importance
User data
Connection identification | +| N-EXPEDITED DATA | Request
Indication | User data
Connection identification | +| N-RESET | Request
Indication
Response
Confirm | Originator
Reason
Connection identification | + +## 6.2 Connectionless services + +The SCCP provides the SCCP user with the ability to transfer signalling messages via the signalling network without set-up of a signalling connection. In addition to the MTP capability, a "routing" function has to be provided within the SCCP, which maps the called address to the signalling point codes of the MTP service. + +This mapping function is provided within each node, or is distributed over the network or is provided in some special translation centres. + +The SCCP also includes the ability to segment/reassemble user data that cannot be transferred in one MTP message. More details can be found in 4.1.1/Q.714. + +Under certain conditions of congestion and unavailability of subsystems and/or signalling points, connectionless messages in support of SCCP-SDUs could be discarded instead of being transferred. If the SCCP user wishes to be informed of the non-delivery of a SCCP-SDU caused by the discard of a message, the return option parameter must be set to "return SCCP-SDU on error" in the primitive to the SCCP. + +### 6.2.1 Description + +The connectionless SCCP offers two services: + +- Class 0: The basic connectionless class without guaranteed in-sequence delivery of SCCP-SDUs. The SCCP user can invoke this service by means of the parameter "sequence control" in the N-UNITDATA request primitive being absent; and + +Class 1: The in-sequence delivery connectionless class with guaranteed3 in-sequence delivery of SCCP-SDUs. The SCCP user can invoke this service by means of the parameter "sequence control" in the N-UNITDATA request primitive being present. + +NOTE – These two services are provided by SCCP making use of the sequence control mechanisms provided by the MTP in a distinct way: + +- a) The class 0 service allows the SCCP to insert SLS values randomly, or with the aim to achieve an appropriate load sharing within the underlying MTP network. +- b) The class 1 service requires the SCCP to insert the same SLS for all the SCCP-SDUs associated with given parameters "sequence control" and "called address". + +The rules to achieve load sharing in the MTP network are not defined in the SCCP Recommendations. + +### 6.2.2 Primitives and parameters of the connectionless service + +#### 6.2.2.1 Overview + +Table 11 gives an overview of the primitives to the upper layers and the corresponding parameters for the connectionless service. + +**Table 11/Q.711 – Primitives and parameters of the connectionless service** + +| Primitives | | Parameters | +|--------------|-----------------------|---------------------------------------------------------------------------------------------------| +| Generic name | Specific name | | +| N-UNITDATA | Request
Indication | Called address
Calling address
Sequence control
Return option
Importance
User data | +| N-NOTICE | Indication | Called address
Calling address
Reason for return
User data
Importance | + +#### 6.2.2.2 Parameters + +##### 6.2.2.2.1 Address + +The parameters "called address" and "calling address" serve to identify the destination and origination respectively, of the SCCP-SDU to be conveyed in connectionless messages. It should be noted that the called and calling addresses may be different at the origination and destination. These parameters may contain some combination of global title, subsystem number and signalling point code. + +3 By the MTP network or by concatenated MTP networks concerned (for further information, see ITU-T Q.706). + +The global title is an address such as dialled digits which does not explicitly contain information that would allow routing in the signalling network, i.e. a translation function is required. The subsystem number is an identification of a specific user function within a certain signalling node, like the ISDN-user part, the SCCP-management, etc. + +##### **6.2.2.2.2 Sequence control** + +The presence of the parameter "sequence control" indicates to the SCCP that the user requires to invoke the "sequence guaranteed" service. In the case of "sequence guaranteed" service, this parameter is an indication to the SCCP that a given stream of SCCP-SDUs has to be delivered in sequence. The value of this parameter together with the called address is also used to distinguish different streams of messages so that the SCCP can allocate SLS codes appropriately to help the MTP in achieving an even distribution of signalling traffic. If the SCCP user does not provide a sequence control parameter, then the SCCP assumes protocol class 0. + +##### **6.2.2.2.3 Return option** + +The parameter "return option" is used to determine the handling of SCCP-SDUs encountering transport problems. + +"Return option" may assume the following values: + +- discard SCCP-SDU on error; +- return SCCP-SDU on error. + +If the SCCP user does not provide a return option parameter, then the SCCP assumes messages will be discarded on error, causing loss of SCCP-SDUs. + +##### **6.2.2.2.4 Reason for return** + +The parameter "reason for return" identifies the reason why a SCCP-SDU was not able to be delivered to its final destination. + +"Reason for return" may assume the following values: + +- no translation for an address of such nature; +- no translation for this specific address; +- subsystem congestion; +- subsystem failure; +- unequipped user; +- MTP failure; +- network congestion; +- SCCP unqualified; +- error in message transport; +- error in local processing; +- destination cannot perform reassembly; +- SCCP failure; +- hop counter violation; +- segmentation not supported; +- segmentation failed. + +##### **6.2.2.2.5 User data** + +The parameter "user data" is information which is to be transferred transparently between SCCP users. In the case of the N-NOTICE primitive, the "user data" parameter may be incomplete. + +##### 6.2.2.2.6 Importance + +The "importance" parameter is a user optional parameter in request primitives that result in the transmission of SCCP messages. Its use allows the SCCP user to assign and indicate to SCCP a certain importance to the primitive. During MTP and/or SCCP congestion, SCCP will take decisions to send out or reject the resulting message, based on this importance and on the severity of the congestion. Its presence in the indication primitives is an SCCP implementation option. + +#### 6.2.2.3 Primitives + +##### 6.2.2.3.1 UNITDATA + +The "N-UNITDATA request" primitive is the means by which an SCCP user requests the SCCP to transfer SCCP-SDUs to a peer SCCP user. + +The "N-UNITDATA indication" primitive informs a user that a SCCP-SDU is being delivered to it from the peer SCCP user. + +Table 12 indicates the parameters of the primitive N-UNITDATA. + +**Table 12/Q.711 – Parameters of the primitive N-UNITDATA** + +| Parameter | Primitive | | +|---------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------| +| | N-UNITDATA request | N-UNITDATA indication | +| Called address | M | M | +| Calling address | U a) | M | +| Sequence control | U | O | +| Return option | U | O | +| User data | M | M(=) | +| Importance | U | O | +| a) This parameter is associated with the SCCP service access point at which the primitive is issued if the calling address is absent. | | | + +##### 6.2.2.3.2 NOTICE + +The "N-NOTICE indication" primitive is the means by which the SCCP returns to the originating user a SCCP-SDU which could not reach the final destination. + +Table 13 indicates the parameters of the primitive N-NOTICE. + +**Table 13/Q.711 – Parameters of the primitive N-NOTICE** + +| Parameter | Primitive | +|-------------------|---------------------| +| | N-NOTICE indication | +| Called address | M | +| Calling address | M | +| Reason for return | M | +| User data | M | +| Importance | O | + +### 6.2.3 State transition diagram + +The network-connectionless transmission service primitive can be used to transmit a self-contained SCCP-SDU from one SCCP-SAP to another SCCP-SAP in a single service access; thus no initial establishment or subsequent release of a network-connection is required. This SCCP-SDU can be independent (class 0) or appear in a sequence where sequence integrity is preserved (class 1). + +The state transition diagram, as seen by the SCCP user using the services provided by the connectionless SCCP, is shown in Figure 9. + +![State transition diagram for sequence of connectionless service primitives at one SCCP-SAP. It shows two states: 'Idle' and a state for 'N-UNITDATA request/indication N-NOTICE indication'. Transitions are shown as curved arrows between the two states.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> N-UNITDATA_request_indication_N-NOTICE_indication : N-UNITDATA request/indication N-NOTICE indication + N-UNITDATA_request_indication_N-NOTICE_indication --> Idle + state "N-UNITDATA request/indication N-NOTICE indication" as N-UNITDATA_request_indication_N-NOTICE_indication + state "Idle" as Idle + +``` + +T1178330-96 + +State transition diagram for sequence of connectionless service primitives at one SCCP-SAP. It shows two states: 'Idle' and a state for 'N-UNITDATA request/indication N-NOTICE indication'. Transitions are shown as curved arrows between the two states. + +**Figure 9/Q.711 – State transition diagram for sequence of connectionless service primitives at one SCCP-SAP** + +## 6.3 SCCP management + +### 6.3.1 Description + +The SCCP provides SCCP management procedures (see clause 5/Q.714) to maintain network performances by rerouting or throttling traffic in the event of failure or congestion in the network. These SCCP management procedures apply to both the connection-oriented and the connectionless services of the SCCP. + +### 6.3.2 Primitives and parameters of the SCCP management + +#### 6.3.2.1 Overview + +Table 14 gives an overview of the primitives to the upper layers and the corresponding parameters for the SCCP management. + +**Table 14/Q.711 – Primitives and parameters of the SCCP management** + +| Primitives | | Parameters | +|---------------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Generic name | Specific name | | +| N-COORD | Request
Indication
Response
Confirm | Affected subsystem
Subsystem multiplicity indicator | +| N-STATE | Request
Indication | Affected subsystem
User status
Subsystem multiplicity indicator | +| N-PCSTATE | Indication | Affected signalling point (together with the MTP-SAP instance)
Signalling point status
Restricted importance level
Remote SCCP status | + +#### 6.3.2.2 Parameters + +##### 6.3.2.2.1 Affected subsystem + +The parameter "affected subsystem" identifies a user which is failed, withdrawn, or allowed. The "affected subsystem" parameter contains the same type of information as the "called address" and "calling address", except the global title portion. + +##### 6.3.2.2.2 User status + +The parameter "user status" is used to inform a SCCP user of the status of the affected subsystem. + +"User status" may assume one of the following values: + +- User-in-service (UIS); +- User-out-of-service (UOS). + +##### 6.3.2.2.3 Subsystem multiplicity indicator + +The parameter "Subsystem multiplicity indicator" identifies the number of replications of a subsystem. This parameter is reserved for national application. + +##### 6.3.2.2.4 Affected signalling point + +The parameter "affected signalling point" identifies a signalling point or SCCP which is failed, congested, or allowed. The "affected signalling point" parameter contains unique identification of a signalling point. + +##### 6.3.2.2.5 Signalling point status + +The parameter "signalling point status" is used to inform a user of the status of an affected signalling point. + +"Signalling point status" may assume the following values: + +- signalling point inaccessible; +- signalling point congested; +- signalling point accessible. + +##### 6.3.2.2.6 Remote SCCP status + +The parameter "remote SCCP status" is used to inform a user of the status of a remote SCCP. + +"Remote SCCP status" may assume the following values: + +- remote SCCP available; +- remote SCCP unavailable, reason unknown; +- remote SCCP unequipped; +- remote SCCP inaccessible; +- remote SCCP congested. + +##### 6.3.2.2.7 Restricted importance level + +The parameter "restricted importance level" is used to inform an SCCP user of the importance level at which traffic is being restricted by SCCP towards a remote signalling point or SCCP. When the user is able to identify the remote signalling point or SCCP, it may decide not to send any primitives of importance numerically below the level indicated that will result in messages towards the (SCCP at that) remote signalling point. Primitives of importance numerically equal to or greater than the level indicated will still be sent (to ensure equitable treatment with users not in a position to identify the remote signalling point or SCCP). + +#### 6.3.2.3 Primitives + +##### 6.3.2.3.1 COORD + +The "N-COORD" primitive (Table 15) is used by replicated subsystems to coordinate the withdrawal of one of the subsystems. + +**Table 15/Q.711 – Parameters of the primitive N-COORD** + +| Parameter | Primitive | | | | +|----------------------------------|-----------------|--------------------|------------------|-----------------| +| | N-COORD request | N-COORD indication | N-COORD response | N-COORD confirm | +| Affected subsystem | M | M | M | M | +| Subsystem multiplicity indicator | n.a. | O | n.a. | O | + +The primitive exists as: a "request" when the originating user is requesting permission to go out-of-service; an "indication" when the request to go out-of-service is delivered to the originator's replicate; a "response" when the originator's replicate announced it has sufficient resources to let the originator go out-of-service; and as a "confirm" when the originator is informed that it may go out-of-service. + +##### 6.3.2.3.2 STATE + +The "N-STATE request" primitive (Table 16) is used to inform the SCCP management about the status of the originating user. The "N-STATE indication" primitive is used to inform an SCCP user accordingly. + +**Table 16/Q.711 – Parameters of the primitive N-STATE** + +| Parameter | Primitive | | +|----------------------------------|-----------------|--------------------| +| | N-STATE request | N-STATE indication | +| Affected subsystem | M | M | +| User status | M | M | +| Subsystem multiplicity indicator | n.a. | O | + +##### 6.3.2.3.3 PCSTATE + +The "N-PCSTATE primitive" (Table 17) is used to inform a user about the status of a signalling point or a remote SCCP. + +**Table 17/Q.711 – Parameters of the primitive N-PCSTATE** + +| Parameter | Primitive | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| | N-PCSTATE indication | +| Affected signalling point | M | +| Signalling point status | M | +| Remote SCCP status | C c5) | +| Restricted importance level | C c6) | +| c5) Present if this is the result of an MTP-STATUS reporting user part unavailability or the reception of an SSC message reporting a change of restricted importance level, or a time-out ( $T_{con}$ ) to detect the abatement of SCCP congestion. | | +| c6) Present if this is the result of a change in the restricted importance level of the affected signalling point or remote SCCP. | | + +# 7 Definition of the lower boundary of the SCCP + +## 7.1 MTP-SAP + +The services provided by the MTP are offered at two different MTP-SAPs: + +- a) An MTP-SAP that supports a maximum MTP-SDU size of 272 octets, including the MTP routing label (see 2.3.8/Q.703). +- b) An MTP-SAP that supports a maximum MTP-SDU size of 4095 octets, including the MTP routing label (see 9.1/Q.2210). + +With the exception of the maximum supported SDU size, these two SAPs offer equivalent services. + +## 7.2 MTP primitives and parameters + +The primitives supported by the MTP are specified in Table 1/Q.701 (MTP-3), and Table 1/Q.2210 (MTP-3b), respectively. Table 18 specifies how the MTP primitives apply when SCCP is using the services of the MTP. In the case of conflicting statements between this Recommendation and ITU-T Q.701 or ITU-T Q.2210, ITU-T Q.701 and ITU-T Q.2210 take precedence. + +**Table 18/Q.711 – Message transfer part service primitives** + +| Primitives | | Parameters | +|--------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| Generic name | Specific name | | +| MTP-TRANSFER | Request
Indication | OPC (2.2/Q.704)
DPC (2.2/Q.704)
SLS (2.2/Q.704) a)
SIO (14.2/Q.704)
User data c) | +| MTP-PAUSE (stop) | Indication | Affected DPC | +| MTP-RESUME (start) | Indication | Affected DPC | +| MTP-STATUS | Indication | Affected DPC
Cause b) | + +a) The SCCP should assist load sharing within the underlying MTP network by making use of an appropriate choice of SLS values (distributed as equally as possible). Where in-sequence delivery is required, the same SLS value should be used. + +b) The cause parameter has, at present, four values: + +- i) Signalling network congested (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 are implemented. +- ii) User part unavailability: unknown (user part identity is SCCP). +- iii) User part unavailability: unequipped remote user (user part identity is SCCP). +- iv) User part unavailability: inaccessible remote user (user part identity is SCCP). +If the cause was "unknown", "inaccessible remote user" or "signalling network congestion" without "level", it is the responsibility of the SCCP to determine when the remote SCCP is again available. + +c) If the selected MTP-SAP instance is an MTP as described in ITU-T Q.701 to ITU-T Q.707, the "user data" parameter is defined in 2.3.8/Q.703. If the selected MTP-SAP instance is an MTP as described in ITU-T Q.2210 ("MTP-3b"), the parameter "user data" is as defined in 9.1/Q.2210. + +### 7.2.1 TRANSFER + +The primitive "MTP-TRANSFER" is used between SCCP and MTP to provide the MTP message transfer service. + +### 7.2.2 PAUSE + +The primitive "MTP-PAUSE" indicates to the SCCP the total inability of providing the MTP service to the specified destination4. + +NOTE – 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. + +4 If MTP provides services according to ITU-T Q.704, see 7.2.6/Q.701, items iii), iv) and v); otherwise, this reference to ITU-T Q.701 does not apply. + +### **7.2.3 RESUME** + +The primitive "MTP-RESUME" indicates to the SCCP the ability of providing the MTP service to the specified destination4. + +This primitive corresponds to the destination accessible state as defined in ITU-T Q.704. + +NOTE – 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. + +### **7.2.4 STATUS** + +The primitive "MTP-STATUS" indicates to the SCCP 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). + +In the case of national option with congestion priorities and multiple signalling link congestion states without priorities, as in ITU-T Q.704, 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 ITU-T Q.704. + +NOTE – 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 user 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. + +### **7.2.5 Notification of completion of MTP restart procedure** + +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 clause 9/Q.704), but it is modelled by the MTP-RESUME indications or MTP-PAUSE indications at the appropriate MTP-SAP instance in the state transition diagrams of 7.3. + +## **7.3 State transition diagram** + +The state transition diagrams, as seen by the SCCP using the services provided by the MTP, are shown in Figures 10, 11 and 12. + +Each state transition diagram applies to a single signalling relation; therefore, there exist as many state transition diagrams as there are signalling relations. Figure 10 is an abstract model of the interface between the MTP and the SCCP. It is not reflected in the management procedures and the SDL diagrams in ITU-T Q.714. + +![State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation. The diagram shows three states: 1. MTP signalling relation not initialized, 2. MTP signalling relation available, and 3. MTP signalling relation unavailable. Transitions are triggered by various MTP primitives like Failure, MTP-PAUSE, MTP-RESUME, MTP-TRANSFER, and MTP-STATUS.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : MTP-TRANSFER request (Note 1) + State1 --> State2 : MTP-RESUME indication (Note 2) + State2 --> State1 : Failure + State2 --> State3 : MTP-PAUSE indication (Note 2) + State3 --> State2 : MTP-RESUME indication + State3 --> State1 : Failure + State3 --> State2 : MTP-TRANSFER indication (Note 1) + State3 --> State2 : MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion) (Note 3) + State3 --> State3 : MTP-TRANSFER indication (Note 1) + State3 --> State3 : MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion) (Note 3) + + state "MTP signalling relation not initialized" as State1 + state "MTP signalling relation available" as State2 + state "MTP signalling relation unavailable" as State3 + +``` + +MTP-TRANSFER indication (Note 1) +MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion) + +T1178340-96 + +State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation. The diagram shows three states: 1. MTP signalling relation not initialized, 2. MTP signalling relation available, and 3. MTP signalling relation unavailable. Transitions are triggered by various MTP primitives like Failure, MTP-PAUSE, MTP-RESUME, MTP-TRANSFER, and MTP-STATUS. + +NOTE 1 – MTP-TRANSFER indication in state 3 is a result of the availability of the signalling relation towards the local MTP, but the unavailability of the signalling relation towards the remote MTP. + +NOTE 2 – These transitions are implicitly triggered by the MTP restart procedure. The end of the MTP restart is communicated to the local MTP users by means of implementation-dependent indications showing each signalling point's accessibility or inaccessibility. + +NOTE 3 – The MTP itself does not keep track of the status of the remote MTP users, so the SCCP is responsible for detecting the availability of its remote peer SCCP. + +**Figure 10/Q.711 – State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation that is managed by the SCCP-MTP international method of congestion reporting** + +![State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation. The diagram shows three states: 1. MTP signalling relation not initialized, 2. MTP signalling relation available, and 3. MTP signalling relation unavailable. Transitions are triggered by MTP primitives like MTP-TRANSFER, MTP-PAUSE, MTP-RESUME, and MTP-STATUS. State 1 transitions to State 2 on MTP-RESUME (Note 2). State 2 transitions to State 3 on Failure or MTP-PAUSE (Note 2). State 3 transitions to State 1 on MTP-TRANSFER indication (Note 1) or MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3). State 3 also has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3). State 2 has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3).](f57c7b37d7a05a99618104f390089f03_img.jpg) + +``` + +stateDiagram-v2 + State1 --> State2 : MTP-RESUME indication (Note 2) + State2 --> State1 : Failure + State2 --> State3 : MTP-PAUSE indication (Note 2) + State3 --> State1 : Failure + State3 --> State2 : MTP-RESUME indication + State3 --> State3 : MTP-PAUSE indication (Note 2) + State2 --> State2 : MTP-TRANSFER request, MTP-TRANSFER indication, MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3) + State3 --> State3 : MTP-TRANSFER indication (Note 1), MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) + + state "MTP signalling relation not initialized\n1" as State1 + state "MTP signalling relation available\n2" as State2 + state "MTP signalling relation unavailable\n3" as State3 + +``` + +MTP-TRANSFER indication (Note 1) +MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) + +MTP-TRANSFER request +MTP-TRANSFER indication +MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3) + +State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation. The diagram shows three states: 1. MTP signalling relation not initialized, 2. MTP signalling relation available, and 3. MTP signalling relation unavailable. Transitions are triggered by MTP primitives like MTP-TRANSFER, MTP-PAUSE, MTP-RESUME, and MTP-STATUS. State 1 transitions to State 2 on MTP-RESUME (Note 2). State 2 transitions to State 3 on Failure or MTP-PAUSE (Note 2). State 3 transitions to State 1 on MTP-TRANSFER indication (Note 1) or MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3). State 3 also has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3). State 2 has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (for a remote unavailable SCCP or to indicate MTP congestion + level) (Note 3). + +NOTE 1 – MTP-TRANSFER indication in state 3 is a result of the availability of the signalling relation towards the local MTP, but the unavailability of the signalling relation towards the remote MTP. + +NOTE 2 – These transitions are implicitly triggered by the MTP restart procedure. The end of the MTP restart is communicated to the local MTP users by means of implementation-dependent indications showing each signalling point's accessibility or inaccessibility. + +NOTE 3 – The MTP itself does not keep track of the status of the remote MTP users, so the SCCP is responsible for detecting the availability of its remote peer SCCP. + +**Figure 11/Q.711 – State transition diagram for sequence of MTP-primitives +across the upper boundary of the MTP-3 for one MTP signalling +relation that is managed by the SCCP-MTP multiple +congestion levels without priorities** + +![State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation. The diagram shows four states: 1. MTP signalling relation not initialized, 2. MTP signalling relation available, 3. MTP signalling relation unavailable, and 4. MTP signalling relation congested. Transitions are triggered by various MTP primitives like Failure, MTP-PAUSE indication, MTP-RESUME indication, MTP-TRANSFER request, and MTP-STATUS indication. State 2 has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (unavailable remote SCCP). State 3 has a self-loop for MTP-PAUSE indication. State 4 has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (unavailable remote SCCP or MTP congestion level ≠ 0).](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : MTP signalling relation not initialized 1 + State1 --> State2 : MTP-RESUME indication (Note 2) + State1 --> [*] : Failure + State2 --> State1 : Failure + State2 --> State2 : MTP-TRANSFER request, MTP-TRANSFER indication, MTP-STATUS indication (unavailable remote SCCP) (Note 3) + State2 --> State3 : MTP-PAUSE indication (Note 2) + State2 --> State4 : MTP-STATUS indication, level ≠ 0 + State3 --> State1 : MTP-PAUSE indication (Note 2) + State3 --> [*] : Failure + State3 --> State2 : MTP-RESUME indication + State4 --> State1 : Failure + State4 --> State2 : MTP-STATUS indication, level = 0 + State4 --> State3 : MTP-PAUSE indication + State4 --> [*] : MTP-STATUS indication, level ≠ 0 + +``` + +State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation. The diagram shows four states: 1. MTP signalling relation not initialized, 2. MTP signalling relation available, 3. MTP signalling relation unavailable, and 4. MTP signalling relation congested. Transitions are triggered by various MTP primitives like Failure, MTP-PAUSE indication, MTP-RESUME indication, MTP-TRANSFER request, and MTP-STATUS indication. State 2 has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (unavailable remote SCCP). State 3 has a self-loop for MTP-PAUSE indication. State 4 has a self-loop for MTP-TRANSFER request, MTP-TRANSFER indication, and MTP-STATUS indication (unavailable remote SCCP or MTP congestion level ≠ 0). + +T1178350-96 + +MTP-TRANSFER indication (Note 1) + MTP-STATUS indication (for unavailable remote SCCP or MTP congestion level ≠ 0) + +MTP-TRANSFER request + MTP-TRANSFER indication + MTP-STATUS indication (for unavailable remote SCCP or MTP congestion level ≠ 0) (Note 4) + +NOTE 1 – MTP-TRANSFER indication in state 3 is a result of the availability of the signalling relation towards the local MTP, but the unavailability of the signalling relation towards the remote MTP. + +NOTE 2 – These transitions are implicitly triggered by the MTP restart procedure. The end of the MTP restart is communicated to the local MTP users by means of implementation-dependent indications showing each signalling point's accessibility or inaccessibility. + +NOTE 3 – The MTP itself does not keep track of the status of the remote MTP users, then, the SCCP is responsible for detecting the availability of its remote peer SCCP. + +NOTE 4 – Further study is required to take into account the MTP level congestion procedure into the SCCP congestion procedures. + +**Figure 12/Q.711 – State transition diagram for sequence of MTP-primitives across the upper boundary of the MTP-3 for one MTP signalling relation that is managed by the SCCP-MTP multiple congestion levels with congestion priorities** + +# **8 Functions provided by the SCCP** + +This clause is an overview of the functional blocks within the SCCP. + +## **8.1 Connection-oriented functions** + +### **8.1.1 Functions for temporary signalling connections** + +#### **8.1.1.1 Connection establishment functions** + +The connection establishment service primitives defined in 6.1 are used to set up a signalling connection. + +The main functions of the connection establishment phase are listed below: + +- set up of a signalling connection; +- establish the optimum size of NPDUs (network protocol data unit); +- map network address onto signalling relations; +- select functions operational during data transfer phase (for instance, layer service selection); +- provide means to distinguish network connections; +- transport user data (within the request). + +#### **8.1.1.2 Data transfer phase function** + +The data transfer phase functions provide means for a two-way simultaneous transport of messages between the two endpoints of the signalling connection. + +The main functions of the data transfer phase as listed below are used or not used in accordance with the result of the selection performed in the connection establishment phase: + +- segmenting/reassembling; +- flow control; +- connection identification; +- NSDU delimiting (Mbit); +- expedited data; +- missequence detection; +- reset; +- others. + +#### **8.1.1.3 Release phase functions** + +These functions provide disconnection of the signalling connection, regardless of the current phase of the connection. The release may be performed by an upper layer stimulus or by maintenance of the SCCP itself. The release can start at each end of the connection (symmetrical procedure). + +The main function of the release phase is the disconnection. + +### **8.1.2 Functions for permanent signalling connections** + +#### **8.1.2.1 Connection establishment phase and connection release phase functions** + +The stimuli for set-up and release of permanent connections are originated from the administration function. + +#### **8.1.2.2 Data transfer phase functions** + +The functions for the data transfer on permanent signalling connections correspond to that for temporary connections. Differences may exist regarding the quality of service. + +## **8.2 Connectionless service functions** + +The functions of the connectionless service are listed below: + +- mapping the network address to signalling relations; +- sequence service; +- segmenting. + +## **8.3 Management functions** + +The SCCP provides functions which manage the status of the SCCP subsystems. These functions allow other nodes in the network to be informed of the change in status of SCCP subsystems at a node, and to modify SCCP translation data if appropriate. + +SCCP management also keeps track of the congestion status of MTP destinations and remote SCCPs. + +For subsystems running in dominant mode or loadshared mode, a possibility is foreseen to negotiate taking one replicated subsystem out of service with the other subsystem remaining in service. This allows to check whether the other side is capable (i.e. has enough resources, real time) to receive the extra traffic load. The replicated subsystem initiating the procedure is taken out of service only after the other subsystem has answered positively to the request. + +When a subsystem is out of service, SCCP test functions are activated at nodes receiving unavailability information. At periodic intervals the status of the unavailable subsystem is checked by an SCCP management procedure. + +Broadcast functions within SCCP management broadcast subsystem status changes to nodes within the network which have an immediate need to be informed of a particular signalling point/subsystem status change. + +Notification functions to local subsystems within the node (local broadcast) are also provided. + +The capability of a remote SCCP node to test the availability of a subsystem at a restarting SCCP node before resuming traffic to that node or subsystem is for further study. The capability of a remote SCCP node to test the availability of the SCCP when the signalling point becomes accessible, before resuming traffic to/via that node, is for further study. In addition, the application of these tests and the protocol specification are for further study. See 5.2.3/Q.714 and 5.3.4.2/Q.714. + +## **8.4 Routing and translation functions** + +The SCCP routing provides a powerful address translation function, which is asked for connectionless and connection-oriented service. The SCCP routing provides a powerful addressing information translation function on behalf of its users. This function makes it unnecessary for SCCP users to store knowledge of SCCP signalling routing information. The routing function also responds to the MTP and SCCP congestion reports. Detailed description of the SCCP routing function can be found in 2.3/Q.714 and 2.4/Q.714. + +# 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.72-199303-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80f1cf6cdf04d70c07cef9359ce75e6a0e224f0d --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bede5d86ac43e2b1003d1b506515cae47b8192ca940e735edb0ab788f4380c1c +size 22307 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b7766363780b0500dcb71a201bf5f3670861ebd --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e283622005cd49b97b2c8f521579c83a73b84964f19e91c360197fae76af22e +size 119845 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3a1a446d7347ba7be83d725e636b6c5edc6e1bf --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41fe79afee483fd0475e3445372e7ebd53e472dfdfeac0e93a4b79a1ac815c69 +size 8221 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3533c9ac7fdc7d6106c075d80a77c2040d843f5b --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22286108748b39b1fbe74fb7935c54c8239c343c91eae7482ed043d990dc532a +size 73086 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8714a2353d3b254451c11c198933638b13582e4 --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fce1c19dac0730d6f8a3679796dd9bd2690d93590d6256efca1df82163a7a5d6 +size 124413 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45881bb622d467f0789bcc7fb04e85c91df5f826 --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f42f776e2f985e02fad331dca5377bccb668f80f24c572ea817a7c5fb21c09f5 +size 74831 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfda54b720bcc43e45bdcc4aea4e4f4b7ff9700e --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6698327905dd60c0151f64ed9876061155b0f1e683608b64ce5bd728069d1774 +size 42300 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1336cd5613cf9a2f18f016dc0ec064bfaa4e31b --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a8c8ff0d1a62df6ad35520cac3e1dec0e76ab3f09f9ede93f951b9d855ee836 +size 45072 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c47c9901c903bc38f41121fda14a6a1fec20710a --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f22204335f3f1011a7b621354f9b460cb5d4ed4bd488f30f0ee9a220a685c42 +size 110916 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b59a07eefa20b824f97c34ef985f008bff16532 --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d2935ab1f299c18833956d06585b49f502e48b25df3a55ccce25186786d0a79 +size 76006 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e64a8cd2efca4648637d0f5787a93c080c487cc --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a32f33476984d5b4af032607cf4bfcbf96c2821af889a8c99d2aa3fb7800c177 +size 73337 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61747b2d4eab742e15639db74c424a274972d741 --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13db27abd3d4db5b76b004b796d9722918076d64fe547f2cbbd3877b8e0eb780 +size 99512 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..215b85af46e8af352c82d8c8c2d2b5d710e02a04 --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d01b92d16a35dc257fb69fb11889709dea89da36fa147626f1724a5a1269228 +size 88284 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2e379c3fa4a24b1d666859c2a16fc928b735e68 --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0ad9eb8184993f10f7e63be9285990e9a1256860ec5dde76477941edf114108 +size 69415 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84c37395aa505b7b5234b575471e03560066b3dd --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ef94aa633af691ad6101a52d2166e20b35e1085ef1aa78fafe38d54056fd63f +size 71045 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c290c97369092e39e2dc8f24735b4fedffed0e9f --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27896d4bf55598231a67c94865a0c7039be02d7474ba488468db4cfb5fd0b4bf +size 66753 diff --git a/marked/Q/T-REC-Q.72-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.72-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baea989d9c2d1781d116444bd00b3cb4860e21c6 --- /dev/null +++ b/marked/Q/T-REC-Q.72-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0597f2a075cf351f4b38f1d8e1cb3f776e7e8312c221b2b1fcbf9e39c825e815 +size 24528 diff --git a/marked/Q/T-REC-Q.725-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.725-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28fd5a3b873cda6e70e9af627ef16717162228e1 --- /dev/null +++ b/marked/Q/T-REC-Q.725-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcbf8c34e850f359544b7d0b829f979102070c3153974105c6cb3da030b41730 +size 8240 diff --git a/marked/Q/T-REC-Q.725-199303-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg b/marked/Q/T-REC-Q.725-199303-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbcc11860f4fe59f5a477483008db758e8fb9e32 --- /dev/null +++ b/marked/Q/T-REC-Q.725-199303-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aac775dcc48568797388c4192a657c8c1bdabb33c29292c17e4152d3514fe762 +size 66506 diff --git a/marked/Q/T-REC-Q.725-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.725-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4ab3ac21aae69a6a289b990443d72d92c80f708 --- /dev/null +++ b/marked/Q/T-REC-Q.725-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9df7bbb5e358d12aee55e4c5df94ea1dfebfd277814869e3ac2f106eb564c7b0 +size 52389 diff --git a/marked/Q/T-REC-Q.725-199303-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg b/marked/Q/T-REC-Q.725-199303-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0325e82af58a86622cc3c6ed3f1bf2f2dfc8d395 --- /dev/null +++ b/marked/Q/T-REC-Q.725-199303-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ead8efd968bf71dfec84976e3fcce06c9edcec84e8ce0848670d8aa556a91a00 +size 65703 diff --git a/marked/Q/T-REC-Q.725-199303-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg b/marked/Q/T-REC-Q.725-199303-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccc16c41f7c7f3a85af8a5785d69043dfdcd42ce --- /dev/null +++ b/marked/Q/T-REC-Q.725-199303-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:514b5cdb9ac572c9a2d7c531feb23a64e63825bb6ca65f1d36ed12cb84f4d1b9 +size 71016 diff --git a/marked/Q/T-REC-Q.725-199303-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg b/marked/Q/T-REC-Q.725-199303-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4ef77f1ff6290ca8065d378b256aad27ac90075 --- /dev/null +++ b/marked/Q/T-REC-Q.725-199303-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f9597fa5a439e30805c9bbf28abd5b1e442e91651405932d40766f4b554368a +size 65416 diff --git a/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca182572adf78b908c0f9b70fac06faeb1596d8e --- /dev/null +++ b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac3911cd9796275a265c8fe637334de102f7e3e705cbf5c7befae7fe3855862a +size 156672 diff --git a/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8812f9af35f2669a13bd285e74ca1d969d86ddf6 --- /dev/null +++ b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3b9f5d26d331cfb40b1791037c977e3597e5372877aa4caffef4173db14946d +size 72160 diff --git a/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18ad8504a6240fe0fa77d135c31b32daa99826d3 --- /dev/null +++ b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9fa9e8d0a068d9963e907c4e380b649f9058989021d48fe064422f5efde6e1 +size 161025 diff --git a/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f63f3faefffe64c2d1e62d933de69b77babdf5c --- /dev/null +++ b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf2489722ba2d7ae1048dd444ac074da995fb53f65f4e9969d92f5d11a0c6391 +size 177063 diff --git a/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/raw.md b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f2143305ac39d5ef185f0eb205e231bb01fa2408 --- /dev/null +++ b/marked/Q/T-REC-Q.731.3-201904-I_PDF-E/raw.md @@ -0,0 +1,875 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.731.3** + +(04/2019) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Specifications of Signalling System No. 7 – ISDN +supplementary services + +--- + +**Stage 3 description for number identification +supplementary services using Signalling +System No. 7 – Calling line identification +presentation** + +Recommendation ITU-T Q.731.3 + +# 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 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.710 | +| 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 | +| 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 | +| 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.731.3 + +## Stage 3 description for number identification supplementary services using Signalling System No. 7 – Calling line identification presentation + +## Summary + +Recommendation ITU-T Q.731.3 provides a signalling procedure for calling line identification presentation (CLIP). The Recommendation specifies service description, operation requirements and coding requirements of CLIP. It also presents the signalling requirements for originating local exchange, transit exchange, international gateway exchange and destination local exchange. Interaction with other supplementary services, interaction with other networks and dynamic description are also considered. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.731.3 | 1993-03-12 | XI | 11.1002/1000/2199 | +| 2.0 | ITU-T Q.731.3 | 2019-04-29 | 11 | 11.1002/1000/13878 | + +## Keywords + +Calling line identification presentation, procedure, Signalling System No. 7. + +--- + +\* 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 ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Calling line identification presentation..... | 3 | +| 6.1 Description ..... | 3 | +| 6.2 Operational requirements ..... | 4 | +| 6.3 Coding requirements ..... | 4 | +| 6.4 Signalling requirements..... | 6 | +| 6.5 Interaction with other supplementary services ..... | 11 | +| 6.6 Interactions with other networks ..... | 13 | +| 6.7 Signalling flows..... | 14 | +| 6.8 Parameter values (timers) ..... | 14 | +| 6.9 Dynamic description..... | 14 | + + + +## Recommendation ITU-T Q.731.3 + +## Stage 3 description for number identification supplementary services using Signalling System No. 7 – Calling line identification presentation + +# 1 Scope + +This Recommendation provides a signalling procedure for calling line identification presentation (CLIP). It specifies service description, operation requirements and coding requirements of CLIP. It also presents the signalling requirements for originating local exchange, transit exchange, international gateway exchange and destination local exchange. Interaction with other supplementary services, interaction with other networks and dynamic description are also considered. + +# 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 references to a document within this Recommendation do not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T E.164] Recommendation ITU-T E.164 (2010), *The international public telecommunication numbering plan*. +- [ITU-T I.251.3] Recommendation ITU-T I.251.3 (1992), *Number identification supplementary services: Calling Line Identification Presentation*. +- [ITU-T I.251.4] Recommendation ITU-T I.251.4 (1992), *Number identification supplementary services: Calling Line Identification Restriction*. +- [ITU-T Q.81.3] Recommendation ITU-T Q.81.3 (1991), *Stage 2 description for number identification supplementary services: Calling line identification presentation (CLIP) and calling line identification restriction (CLIR)*. +- [ITU-T Q.730] Recommendation ITU-T Q.730 (1999), *ISDN User Part supplementary services*. +- [ITU-T Q.731.4] Recommendation ITU-T Q.731.4 (2019), *Stage 3 description for number identification supplementary services using signalling system No. 7 – Calling line identification restriction*. +- [ITU-T Q.761] Recommendation ITU-T Q.761 (1999), *Signalling System No. 7 – ISDN User Part functional description*. +- [ITU-T Q.762] Recommendation ITU-T Q.762 (1999), *Signalling System No. 7 – ISDN User Part general functions of messages and signals*. +- [ITU-T Q.763] Recommendation ITU-T Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes*. +- [ITU-T Q.764] Recommendation ITU-T Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures*. +- [ITU-T Q.767] Recommendation ITU-T Q.767 (1991), *Application of the ISDN User Part of CCITT signalling system No. 7 for international ISDN interconnections*. + +- [ITU-T Q.931] Recommendation ITU-T Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control.* +- [ITU-T Q.951.3] Recommendation ITU-T Q.951.3 (1993), *Stage 3 description for number identification supplementary services using DSS 1: Calling line identification presentation.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 calling line identification presentation (CLIP):** A supplementary service offered to the called user which provides the calling user's number, with additional address information (e.g., calling party sub-address) if any, to the called user. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|-----------------------------------------------| +| 3PTY | Three-Party service | +| AOC | Advice Of Charge | +| CCBS | Completion of Calls to Busy Subscriber | +| CD | Call Deflection | +| CDIV | Call Diversion services | +| CFB | Call Forwarding Busy | +| CFNR | Call Forwarding No Reply | +| CFU | Call Forwarding Unconditional | +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| COLP | Connected Line Identification Presentation | +| COLR | Connected Line Identification Restriction | +| CONF | Conference calling | +| CPE | Customer Premises Equipment | +| CPE-SS7 | CPE Connected Signalling System No. 7 | +| CUG | Closed User Group | +| CW | Call Waiting | +| DDI | Direct Dialling-In | +| DSS1 | Digital Subscriber Signalling System No. 1 | +| HOLD | call Hold | +| ISDN | Integrated Services Digital Network | +| ISUP | Integrated Services Digital Network User Part | + +| | | +|------|----------------------------------------| +| LH | Line Hunting | +| MCID | Malicious Call Identification | +| MLPP | Multi-Level Precedence and Pre-Emption | +| MSN | Multiple Subscriber Number | +| PNP | Private Numbering Plan | +| REV | Reverse charging | +| SS | Signalling System | +| SUB | Sub-addressing | +| TP | Terminal Portability | +| 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 | + +# 5 Conventions + +None. + +# 6 Calling line identification presentation + +## 6.1 Description + +### 6.1.1 General description + +The CLIP supplementary service is a supplementary service offered to the called user. It presents the calling user's number, with additional address information (e.g., the calling party sub-address) if any, to the called user. When provided, the facility applies to all incoming calls except for when the calling user has activated the calling line identification restriction (CLIR) supplementary service (see [ITU-T Q.731.4]) or the complete number of the calling user is not available at the destination exchange. + +The calling party number may be provided by the originating local exchange or by the access signalling system of the calling user. The calling party number may also be provided by transit exchange which is connected to the customer premises equipment (CPE) using Signalling System No. 7. + +The calling party sub-address (if provided by the access signalling system) shall be transported transparently by the network in the access transport parameter. The network cannot be responsible for the content of this sub-address. + +Information indicating that a subscriber has the CLIP supplementary service facility is available in the exchange to which the subscriber is connected to. + +The stage 1 service description is given in [ITU-T I.251.3], and the stage 2 functional capabilities and information flows are given in [ITU-T Q.81.3]. The stage 3 DSS1 description is given in [ITU-T Q.951.3]. This stage 3 description of the CLIP supplementary service uses the integrated services digital network (ISDN) user part protocol as defined in [ITU-T Q.761], [ITU-T Q 764] and [ITU-T Q.730]. + +### 6.1.2 Specific terminology + +In addition to the term defined in clause 3, this Recommendation uses the following specific terminology: + +**ISDN number** – A number conforming to the numbering plan and structure specified in [ITU-T E.164]. + +**National (ISDN) number; National significant (ISDN) number** – See [ITU-T E.164]. + +**International (ISDN) number** – See [ITU-T E.164]. + +**Sub-address** – See [ITU-T E.164]. + +**Served user** – The user of a particular ISDN number who has subscribed to the presentation of the calling line identification information in association with incoming calls. The served user is also known as the called user. + +**Calling user** – The user that initiated an incoming call at the served user. The calling user needs not to have subscribed to the CLIP supplementary service. + +**Default number** – A national significant ISDN number registered within the public ISDN following prior arrangement between the calling user and the public ISDN. + +**Special connection arrangement** – An arrangement between a customer and a public network operator whereby customer supplied calling party numbers are not screened by the public network. + +**Access signalling system** – A part in the local exchange that handles the user-network interface protocol. It also includes the screening functions. + +**CPE connected signalling system No. 7** – A part in the transit exchange that handles the SS No. 7 protocol used between transit exchange and CPE. It also includes the screening functions. + +### 6.1.3 Provision/withdrawal + +See clause 2.3 of [ITU-T I.251.3]. + +### 6.1.4 State definitions + +No specific state definitions are required. + +## 6.2 Operational requirements + +### 6.2.1 Provision/withdrawal + +See clause 3.1 of [ITU-T I.251.3]. + +### 6.2.2 Requirements on the originating network side + +Not applicable. + +### 6.2.3 Requirements in the network + +No specific requirements are needed in the network. + +### 6.2.4 Requirements on the terminating network side + +Not applicable. + +## 6.3 Coding requirements + +- i) Coding requirements if a special connection arrangement does not apply +- Clause 3.10 of [ITU-T Q.763] and clause 3.2 of [ITU-T Q.763] give the coding for the calling party number and the access transport parameter which are required to support this service. +- The purpose of the calling party number parameter is to identify the origin of a call. + +- The access transport parameter transports the calling party sub-address information element as defined in clause 4.5.11 of [ITU-T Q.931], which is to identify a sub-address associated with the origin of the call. +- ii) Coding requirements if a special connection arrangement applies + - In addition to the coding requirements of i) above, the generic number parameter as specified in clause 3.26c) of [ITU-T Q.763] is required. + - The purpose of the generic number parameter is to transport a calling party number provided by the calling user with a special connection arrangement. + - The generic number parameter is accompanied by the parameter compatibility information parameter as specified in clause 3.41 b) of [ITU-T Q.763]. The procedures for the compatibility are defined in clause 2.9.5 of [ITU-T Q.764]. + - The allowed coding for the generic number parameter is as follows: + - a) Number qualifier indicator +00000110 additional calling party number + - b) Odd/even indicator +See clause 3.9 a) of [ITU-T Q.763] + - c) Nature of address indicator +0000001 subscriber number (for national use) +0000010 unknown (for national use) +0000011 national (significant) number +0000100 international number + - d) Internal network number indicator/number incomplete indicator (not used) +0 + - e) Numbering plan indicator +001 ISDN (Telephony) numbering plan [ITU-T E.164] + - f) Address presentation restricted (Pres. Restric.) indicator +00 presentation allowed +01 presentation restricted + - g) Screening indicator +00 user provided, not verified +10 user provided, verified and failed (for national use) + - h) Address signals +0000 digit 0 +0001 digit 1 +0010 digit 2 +0011 digit 3 +0100 digit 4 +0101 digit 5 +0110 digit 6 +0111 digit 7 +1000 digit 8 +1001 digit 9 + +i) Filler + +See clause 3.9 h) of [ITU-T Q.763]. + +## **6.4 Signalling requirements** + +### **6.4.1 Activation/deactivation/registration** + +Not applicable. + +### **6.4.2 Invocation and operation** + +#### **6.4.2.1 Actions at the originating local exchange** + +###### **6.4.2.1.1 Normal operation** + +All information pertaining to the CLIP supplementary service shall be inserted in the initial address message sent as part of the basic call procedures according to [ITU-T Q.764]. + +The calling party sub-address (if provided by the access signalling system) shall be transported transparently by the network in the access transport parameter. + +If the numbering plan indicator received from the access signalling system together with a calling party number is coded other than "ISDN (Telephony) numbering plan [ITU-T E.164]" or "unknown", then the calling party number received from the access signalling system shall be discarded and the processing of the call shall continue as if no calling party number was received. If the numbering plan indicator received from the access signalling system is coded "unknown", then the originating local exchange shall treat this value as if the value "ISDN (Telephony) numbering plan [ITU-T E.164]" was received. + +If the screening indicator received from the access signalling system together with the calling party number is coded "user provided, not verified", then the calling party number shall be entered in the generic number parameter. In this parameter, the number qualifier indicator shall be set to "additional calling party number" and the screening indicator to "user provided, not verified". If the numbering plan indicator received is coded "ISDN (Telephony) numbering plan [ITU-T E.164]" or "unknown", then the nature of address indicator shall be set to "international number" or "national (significant) number" as received from the access signalling system. + +NOTE 1 – As a national option, some networks may allow for the screening indicator "user provided, verified and failed". If this screening indicator is supported, then the originating local exchange shall treat this value in the same manner as the value "user provided, not verified". + +In addition, the originating local exchange shall enter the default number associated with that access in the calling party number parameter. In this parameter, the screening indicator shall be set to "network provided" and the nature of address indicator to "national (significant) number". + +If the screening indicator received from the access signalling system together with the calling party number is coded other than "user provided, not verified", then the originating local exchange shall enter the calling party number as received from the access signalling system in the calling party number parameter. The screening indicator of the calling party number parameter shall be set as received from the access signalling system. + +NOTE 2 – In the latter case, allowed values for the screening indicator are "network provided" and "user provided, verified and passed". + +If no calling party number is received from the access signalling system, the originating local exchange shall enter the default number associated with that access in the calling party number parameter. The screening indicator shall be set to "network provided" and the nature of address indicator to "national (significant) number". + +The calling party number incomplete indicator of the calling party number parameter shall be set to "complete". + +The numbering plan indicator of the calling party number parameter shall be set to "ISDN (Telephony) numbering plan [ITU-T E.164]". + +The numbering plan indicator of the generic number parameter shall be set to "ISDN (Telephony) numbering plan [ITU-T E.164]" if this value or "unknown" was received from the access signalling system. + +The address presentation restricted indicators of the calling party number and the generic number parameter shall both be set to the value "presentation allowed" or "presentation restricted" as received from the access signalling system. + +The actions at the originating local exchange and the resulting codepoints are summarized in Table 6-1. + +**Table 6-1 – Calling party number, codepoints at the original local exchange** + +| Information provided by the access signalling system | | | Information transported by the network | | | | +|------------------------------------------------------|-----------------------------------------|------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------|-------------------------------------------------------------------------------------------------------|------------------------------------------------------------| +| Calling party number | Numbering plan | Screening indicator | Calling party number | Numbering plan | Nature of address indicator | Screening indicator | +| | | | Calling party number parameter | | | | +| None | | | Default number | "[ITU-T E.164]" | "national (significant) number" | "network provided" | +| | | | No generic number parameter indicating "additional calling party number" is sent | | | | +| | | | Calling party number parameter | | | | +| Any number a) | Other than "[ITU-T E.164]" or "unknown" | | Default number | "[ITU-T E.164]" | "national (significant) number" | "network provided" | +| | | | No generic number parameter indicating "additional calling party number" is sent | | | | +| | | | Calling party number parameter | | | | +| Any digit sequence conforming to [ITU-T E.164] | "[ITU-T E.164]" or "unknown" | "network provided" or "user provided, verified and passed" | Number provided by the access signalling system | "[ITU-T E.164]" | "national (significant) number" or "international number" as provided by the access signalling system | "network provided" or "user provided, verified and passed" | +| | | | No generic number parameter indicating "additional calling party number" is sent | | | | +| | | | Calling party number parameter | | | | +| | | | Default number | "[ITU-T E.164]" | "national (significant) number" | "network provided" | +| | | | Generic number parameter for "additional calling party number" | | | | +| Any digit sequence conforming to [ITU-T E.164] | "[ITU-T E.164]" or "unknown" | "user provided, not verified" b) | Number provided by the access signalling system | "[ITU-T E.164]" | "national (significant) number" or "international number" as provided by the access signalling system | "user provided, not verified" b) | + +**Table 6-1 – Calling party number, codepoints at the original local exchange** + +| Information provided by the access signalling system | Information transported by the network | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| a) In this case, the calling party number received from the access signalling system shall be discarded, but the address presentation restricted indicator shall (as in all other cases) be set to the value as received from the access signalling system.
b) As a national option, some networks may allow for the screening indicator "user provided, verified and failed". If this screening indicator is supported, then the originating local exchange shall treat this value in the same manner as the value "user provided, not verified". | | + +###### 6.4.2.1.2 Exceptional procedures + +No exceptional procedures are identified. + +#### 6.4.2.2 Actions at the transit exchange + +###### 6.4.2.2.1 Normal operation + +A transit exchange shall transfer all information relating to the CLIP and CLIR supplementary services transparently to the succeeding exchange. + +NOTE – In interworking with the mobile network, the mobile telephony exchange may provide the transit exchange with an international calling party number that has a country code other than the country code of the transit exchange. + +###### 6.4.2.2.2 Exceptional procedures + +When transit exchange connects to a customer premises equipment through SS No. 7, following actions (e.g., ignore the information, use a default value) shall be taken. + +If no CLI parameter is received from the CPE connected signalling system No. 7 (CPE-SS7) or number incomplete indicator of the CLI parameter is "incomplete", the transit exchange shall enter the default number associated with the CPE-SS7 in the calling party number parameter. The screening indicator shall be set to "network provided" and the nature of address indicator shall be set to "national (significant) number". + +If the numbering plan indicator received from the CPE-SS7 together with a calling party number is coded other than "ISDN (Telephony) numbering plan [ITU-T E.164]" or "unknown", then the calling party number received from the CPE-SS7 shall be discarded and the processing of the call shall continue as if no CLI parameter was received. If the numbering plan indicator received from the CPE-SS7 is coded "unknown", then the transit exchange shall treat this value as if the value "ISDN (Telephony) numbering plan [ITU-T E.164]" was received. + +If the screening indicator received from the CPE-SS7 together with the calling party number is coded "user provided, not verified" or "user provided, verified and failed", then the transit exchange shall enter the default number associated with the CPE-SS7 in the calling party number parameter. The screening indicator of the calling party number parameter shall be set to "network provided" and the nature of address indicator shall be set to "national (significant) number". The calling party number can be entered in the generic number parameter according to pre-defined policy. In generic number parameter, number qualifier indicator shall be set to "additional calling party number" and screening indicator shall be set as received. In other cases, generic number parameter "number qualifier indicator" set to "additional calling party number" shall not be sent even if it is received from CPE-SS7. + +If the screening indicator received from the CPE-SS7 is "network provided" or "user provided, verified and passed", then: + +- if the received calling party number is associated with the CPE-SS7, then the transit exchange shall enter the calling party number as received from CPE-SS7 in the calling party number parameter. The screening indicator of the calling party number parameter shall be set as received from the CPE-SS7. +- if the received calling party number is not associated with the CPE-SS7, then the transit exchange shall enter the calling party number as the default number associated with the CPE-SS7 in the calling party number parameter. The screening indicator of the calling party number parameter shall be set to "network provided" and the nature of address indicator shall be set to "national (significant) number". + +The calling party number incomplete indicator of the calling party number parameter shall be set to "complete". + +The address presentation restricted indicators of the calling party number shall be set to the value associated with the CPE-SS7. + +The actions at the transit exchange that connect to CPE-SS7 and the resulting codepoints are summarized in Table 6-2. + +**Table 6-2 – Calling party number, codepoints at the transit exchange** + +| Information provided by CPE-SS7 | | | Information transported by the network | | | | +|------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------|------------------------------------------------------------| +| Calling party number | Numbering plan | Screening indicator | Calling party number | Numbering plan | Nature of address indicator | Screening indicator | +| | | | Calling party number parameter | | | | +| None or incomplete | | | Default number | "[ITU-T E.164]" | "national (significant) number" | "network provided" | +| | | | No generic number parameter indicating "additional calling party number" is sent | | | | +| | | | Calling party number parameter | | | | +| Any number | Other than "[ITU-T E.164]" or "unknown" | | Default number | "[ITU-T E.164]" | "national (significant) number" | "network provided" | +| | | | No generic number parameter indicating "additional calling party number" is sent | | | | +| | | | Calling party number parameter | | | | +| digit sequence conforming to [ITU-T E.164] and associated with the CPE-SS7 | "[ITU-T E.164]" or "unknown" | "network provided" or "user provided, verified and passed" | Number provided by that CPE-SS7 | "[ITU-T E.164]" | "national (significant) number" or "international number" as provided by the CPE-SS7 | "network provided" or "user provided, verified and passed" | +| | | | No generic number parameter indicating "additional calling party number" is sent | | | | +| | | | Calling party number parameter | | | | +| Any digit sequence conforming to [ITU-T E.164] but not associated with the CPE-SS7 | "[ITU-T E.164]" or "unknown" | "network provided" or "user provided, verified and passed" | Default number | "[ITU-T E.164]" | "national (significant) number" | "network provided" | +| | | | No generic number parameter indicating "additional calling party number" is sent | | | | +| | | | Calling party number parameter | | | | + +**Table 6-2 – Calling party number, codepoints at the transit exchange** + +| Information provided by CPE-SS7 | | | Information transported by the network | | | | +|------------------------------------------------|------------------------------|---------------------------------------------------------------------|-------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| | | | Default number | "[ITU-T E.164]" | "national (significant) number" | "network provided" | +| | | | Generic number parameter for "additional calling party number" a) | | | | +| Any digit sequence conforming to [ITU-T E.164] | "[ITU-T E.164]" or "unknown" | "user provided, not verified" or user provided, verified and failed | Number provided by the CPE-SS7 | "[ITU-T E.164]" | "national (significant) number" or "international number" as provided by the CPE-SS7 | "user provided, not verified" or user provided, verified and failed | + +a) Generic number parameter indicating "additional calling party number" with the screening indicator "user provided, not verified" can be sent under pre-defined policy. In other case, it shall not be sent. + +#### 6.4.2.3 Actions at the outgoing international gateway exchange + +###### 6.4.2.3.1 Normal operation + +If the address presentation restricted indicator of the received calling party number parameter is set to "presentation restricted", the outgoing international gateway exchange shall act according to the bilateral agreement between the two networks (see clauses 2.1 and 5 of [ITU-T I.251.4]). If the address presentation restricted indicator of the received calling party number parameter is set to "address not available", then the calling party number parameter shall be omitted from the initial address message. If the calling party number parameter is not sent across the international section, then the generic number parameter shall be omitted from the initial address message if its number qualifier indicates "additional calling party number". + +The exchange shall convert the calling party number conveyed in the calling party number parameter to an international number (if necessary) and set the nature of address indicator to "international number". The address presentation restricted indicator and the screening indicator shall be transferred transparently. + +If the generic number parameter is received and its number qualifier indicates "additional calling party number" and the numbering plan indicator is coded "ISDN (Telephony) numbering plan [ITU-T E.164]", then the generic number parameter shall be treated in the same manner as the calling party number parameter. + +NOTE 1 – Without bilateral agreement for the transport of "user provided, verified and failed" numbers between networks, the generic number parameter shall be discarded if its number qualifier indicates "additional calling party number" and the screening indicator is coded "user provided, verified and failed". + +NOTE 2 – The address presentation restricted indicator in both the calling party number and generic number parameters are set to the same value. They can have the values "presentation allowed" or "presentation restricted" (based on the bilateral agreement). + +###### 6.4.2.3.2 Exceptional procedures + +If no calling party number parameter is received from the incoming network, then no calling party number parameter shall be sent to the succeeding exchange. + +If the calling party number incomplete indicator is set to "incomplete", then no calling party number parameter shall be sent to the succeeding exchange. + +#### **6.4.2.4 Actions at the incoming international gateway exchange** + +###### **6.4.2.4.1 Normal operation** + +The exchange shall check if the country code of the calling party number is the network's own country code. If this is the case, then the country code shall be removed. The nature of address indicator shall be set to "national (significant) number". The address presentation restricted indicator and the screening indicator shall be transferred transparently. + +NOTE – As a national option, the incoming international gateway exchange may add a prefix to the calling party number. In this case the nature of address indicator shall be set to "unknown". + +If the generic number parameter is received and its number qualifier indicates "additional calling party number" and the numbering plan indicator is coded "ISDN (Telephony) numbering plan [ITU-T E.164]", then the generic number parameter shall be treated in the same manner as the calling party number parameter. + +###### **6.4.2.4.2 Exceptional procedures** + +If no calling party number parameter is received from the preceding exchange, then no calling party number parameter shall be sent to the outgoing network. + +If the address presentation restricted indicator of the received calling party number parameter is set to "address not available", then this value shall be passed on transparently. The screening indicator shall be set to "network provided". + +NOTE – As a national option, the nature of address indicator in the calling party number parameter can be set to "unknown". + +#### **6.4.2.5 Actions at the destination local exchange** + +###### **6.4.2.5.1 Normal operation** + +When the destination local exchange receives an initial address message, basic call handling shall occur and the exchange shall send a set-up request to the access signalling system. + +It is a function of the user-network interface to check whether the called user has subscribed to the CLIP supplementary service or not and not to present the calling party sub-address, where appropriate, to the user. + +If the generic number parameter with a number qualifier set to "additional calling party number" is provided, then the information conveyed in this parameter shall be presented first to the access signalling system. The information conveyed in the calling party number parameter shall be sent to the access signalling system immediately following the information of the generic number parameter. + +Where the generic number parameter is not provided but the calling party number parameter is present, then the information conveyed in the calling party number parameter shall be sent to the access signalling system. + +All the available information shall be sent to the access signalling system. + +###### **6.4.2.5.2 Exceptional procedures** + +No exceptional procedures are identified. + +## **6.5 Interaction with other supplementary services** + +### **6.5.1 Call waiting (CW)** + +No impact on ISUP. + +### **6.5.2 Call transfer services** + +No applicable interaction at this time. + +### **6.5.3 Connected line identification presentation (COLP)** + +No impact on ISUP. + +### **6.5.4 Connected line identification restriction (COLR)** + +No impact on ISUP. + +### **6.5.5 Calling line identification presentation (CLIP)** + +Not applicable. + +### **6.5.6 Calling line identification restriction (CLIR)** + +The CLIR supplementary service (see [ITU-T Q.731.4]) shall take precedence over the CLIP supplementary service. + +Depending on bilateral agreement, the originating network may restrict the information conveyed in the generic number and/or calling party number parameter from being sent to the destination network when the CLIR supplementary service is applicable. + +### **6.5.7 Closed user group (CUG)** + +No impact on ISUP. + +### **6.5.8 Conference calling (CONF)** + +No impact on ISUP. + +### **6.5.9 Direct dialling-in (DDI)** + +No impact on ISUP. + +### **6.5.10 Call diversion services (CDIV)** + +#### **6.5.10.1 Call forwarding busy (CFB)** + +An exchange forwarding a call shall also forward the generic number parameter (if present). + +#### **6.5.10.2 Call forwarding no reply (CFNR)** + +An exchange forwarding a call shall also forward the generic number parameter (if present). + +#### **6.5.10.3 Call forwarding unconditional (CFU)** + +An exchange forwarding a call shall also forward the generic number parameter (if present). + +#### **6.5.10.4 Call deflection (CD)** + +An exchange deflecting a call shall also deflect the generic number parameter (if present). + +### **6.5.11 Line hunting (LH)** + +No impact on ISUP. + +### **6.5.12 Three-party service (3PTY)** + +No impact on ISUP. + +### **6.5.13 User-to-user signalling (UUS)** + +#### **6.5.13.1 User-to-user signalling, service 1 (UUS1)** + +No impact on ISUP. + +#### **6.5.13.2 User-to-user signalling, service 2 (UUS2)** + +No impact on ISUP. + +#### **6.5.13.3 User-to-user signalling, service 3 (UUS3)** + +No impact on ISUP. + +### **6.5.14 Multiple subscriber number (MSN)** + +No impact on ISUP. + +### **6.5.15 Call hold (HOLD)** + +No impact on ISUP. + +### **6.5.16 Advice of charge (AOC)** + +No impact on ISUP. + +### **6.5.17 Sub-addressing (SUB)** + +No impact on ISUP. + +### **6.5.18 Terminal portability (TP)** + +No impact on ISUP. + +### **6.5.19 Completion of calls to busy subscriber (CCBS)** + +No applicable interaction at this time. + +### **6.5.20 Malicious call identification (MCID)** + +No impact on ISUP. + +### **6.5.21 Reverse charging (REV)** + +No applicable interaction at this time. + +### **6.5.22 Multi-level precedence and preemption (MLPP)** + +No impact on ISUP. + +### **6.5.23 Private numbering plan (PNP)** + +No applicable interaction at this time. + +### **6.5.24 International telecommunication charge card** + +No applicable interaction at this time. + +## **6.6 Interactions with other networks** + +On calls to or via non-ISDNs or an ISUP as defined in [ITU-T Q.767], where the succeeding signalling section supports only one calling party number to be carried, the information contained in the calling party number parameter shall be forwarded. The generic number parameter shall be discarded. + +Interworking exchanges may generate only part of the calling line identity for inclusion in the initial address message (e.g., trunk code). This shall be indicated in the number incomplete indicator in the calling party number parameter. + +On calls incoming from some non-ISDNs, the calling party number may be delivered to the destination ISDN without an indication of calling line identity restriction or the calling party number may be incomplete. In the case where there is no indication of presentation allowed or restricted, the interworking exchange shall act according to its rules and regulations. In the case where the number incomplete indicator received together with the calling party number indicates "incomplete", the information conveyed in the calling party number parameter is passed to the access signalling system. + +## **6.7 Signalling flows** + +No CLIP supplementary service specific signalling flow is necessary in addition to the basic call control according to [ITU-T Q.764]. + +## **6.8 Parameter values (timers)** + +No specific timers are required. + +## **6.9 Dynamic description** + +The dynamic description is specified in Figure 3-1 o Figure 3-4. + +![Flowchart of the ISUP protocol dynamic description for an originating local exchange. The process starts at 'Idle', goes to 'Setup IAM', then checks if CLI is provided. If 'No', it sets default CPN parameters. If 'Yes', it checks the NPI. If 'Other', it discards CLI. If 'ITU-T E.164' or 'unknown', it checks if SI is 'user provided, not verified'. If 'No', it sets default CPN parameters. If 'Yes', it sets GN or CPN parameters based on NOTE 1, then sets presentation restrictions and sends 'IAM' to end at 'Idle'.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> SetupIAM[Setup IAM] + SetupIAM --> CLIProvided{CLI provided by the access sign. system?} + CLIProvided -- No --> DefaultCPN[CPN parameter = default number, set SI = "network provided", set NPI = "ISDN/Telephony (ITU-T E.164)", set nature of address = "national (sign.) number", set NI = "complete"] + CLIProvided -- Yes --> NPI + NPI -- Other --> DiscardCLI[Discard CLI provided by the access signalling system] + NPI -- "ITU-T E.164" or "unknown" --> SIUserProvided{SI = "user provided, not verified"?} + SIUserProvided -- No --> DefaultCPN + SIUserProvided -- Yes --> NOTE1[NOTE 1] + NOTE1 --> GN[GN parameter = access signalling system provided number, set number qualifier = "additional calling party number" set NPI = "ISDN/Telephony (ITU-T E.164)", set nature of address to "national (sign.) number" or "international number"] + NOTE1 --> CPN[CPN parameter = access signalling system provided number, set SI as received set NPI = "ISDN/Telephony (ITU-T E.164)", set nature of address to "national (sign.) number" or "international number", set NI = "complete"] + DefaultCPN --> Join1(( )) + DiscardCLI --> Join1 + GN --> Join1 + CPN --> Join1 + Join1 --> SetRestrictions[Set presentation restriction indicator in CPN and GN parameters as received from access signalling system] + SetRestrictions --> IAM[IAM] + IAM --> Idle2([Idle]) + +``` + +CLI Calling line identity + CPN Calling party number + GN Generic number + SI Screening indicator + NPI Numbering plan indicator + IAM Initial address message + NI Number incomplete indicator + +Q.731.3(19)\_F6-1 + +Flowchart of the ISUP protocol dynamic description for an originating local exchange. The process starts at 'Idle', goes to 'Setup IAM', then checks if CLI is provided. If 'No', it sets default CPN parameters. If 'Yes', it checks the NPI. If 'Other', it discards CLI. If 'ITU-T E.164' or 'unknown', it checks if SI is 'user provided, not verified'. If 'No', it sets default CPN parameters. If 'Yes', it sets GN or CPN parameters based on NOTE 1, then sets presentation restrictions and sends 'IAM' to end at 'Idle'. + +NOTE 1 – As a national option, some networks may allow for the screening indicator "user provided and failed". If this screening indicator is supported, then the originating local exchange shall treat this value in the same manner as the value "user provided, not verified". + +NOTE 2 – This procedure operates independently from any CLIP subscription by the calling user and is provided as part of the basic service. + +NOTE 3 – This transition specifies additional processing to that described in Annex H of [ITU-TQ.764]. + +**Figure 6-1 – Originating local exchange dynamic description of the ISUP protocol** + +![Flowchart for Outgoing international gateway exchange dynamic description. The process starts at 'Idle', goes to 'set up IAM', then checks if 'CPN parameter present?'. If 'Yes', it checks 'PR in CPN parameter = "address not available"?'. If 'No', it checks 'Number complete?'. If 'Yes', it checks 'Presentation allowed?'. If 'No', it checks 'Special agreement on presentation?'. If 'Yes', it checks 'NPI = "ISDN/Telephony ITU-T E.164"?'. If 'No', it checks 'International number?'. If 'Yes', it performs 'Delete prefix digits (if any), add originating country code, set nature of address indicator to "international number"'. If 'No', it performs 'Omit GN parameter from IAM if Number qualifier = "additional calling party number"'. If 'Yes', it checks 'Number qualifier = "add. calling party number"?'. If 'Yes', it checks 'NPI = "ISDN/Telephony ITU-T E.164"?'. If 'No', it checks 'International number?'. If 'Yes', it performs 'Delete prefix digits (if any), add originating country code, set Nature of address indicator to "international number"'. If 'No', it performs 'Omit CPN parameter from IAM'. If 'Yes', it checks 'GN parameter present?'. If 'Yes', it performs 'Keep PR, SI and NI as provided by the incoming network'. If 'No', it performs 'Keep PR and SI as provided by the incoming network'. Finally, it goes to 'IAM' and then 'Idle'.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> set_up_IAM[/set up IAM/] + set_up_IAM --> CPN_present{CPN parameter present? (NOTE 1)} + CPN_present -- No --> IAM_out[/IAM/] + CPN_present -- Yes --> PR_address{PR in CPN parameter = "address not available"?} + PR_address -- Yes --> Number_qualifier{Number qualifier = "additional calling party number"?} + PR_address -- No --> Number_complete{Number complete?} + Number_complete -- No --> Number_qualifier + Number_complete -- Yes --> Presentation_allowed{Presentation allowed? (NOTE 2)} + Presentation_allowed -- No --> Special_agreement{Special agreement on presentation?} + Special_agreement -- Yes --> NPI_164_1{NPI = "ISDN/Telephony ITU-T E.164"? (NOTE 3)} + Special_agreement -- No --> International_number_1{International number?} + NPI_164_1 -- Yes --> Keep_PR_SI_NI_1[Keep PR, SI and NI as provided by the incoming network] + NPI_164_1 -- No --> International_number_1 + International_number_1 -- Yes --> Delete_prefix_1[Delete prefix digits (if any), add originating country code, set nature of address indicator to "international number"] + International_number_1 -- No --> Omit_GN[Omit GN parameter from IAM if Number qualifier = "additional calling party number"] + Delete_prefix_1 --> Number_qualifier + Omit_GN --> Number_qualifier + Number_qualifier -- Yes --> NPI_164_2{NPI = "ISDN/Telephony ITU-T E.164"?} + Number_qualifier -- No --> Omit_CPN[Omit CPN parameter from IAM] + NPI_164_2 -- Yes --> International_number_2{International number?} + NPI_164_2 -- No --> GN_present{GN parameter present? (NOTE 4)} + International_number_2 -- Yes --> Delete_prefix_2[Delete prefix digits (if any), add originating country code, set Nature of address indicator to "international number"] + International_number_2 -- No --> Keep_PR_SI_2[Keep PR and SI as provided by the incoming network] + Delete_prefix_2 --> Keep_PR_SI_2 + Keep_PR_SI_2 --> IAM_out + GN_present -- Yes --> Keep_PR_SI_NI_1 + GN_present -- No --> Keep_PR_SI_2 + IAM_out --> Idle2([Idle]) + +``` + +CLI Calling line identity      PR Presentation restrictions + CPN Calling party number    NI Number incomplete indicator + GN Generic number            NPI Numbering plan indicator + SI Screening indicator      IAM Initial address message + +Q.731.3(19)\_F6-2 + +Flowchart for Outgoing international gateway exchange dynamic description. The process starts at 'Idle', goes to 'set up IAM', then checks if 'CPN parameter present?'. If 'Yes', it checks 'PR in CPN parameter = "address not available"?'. If 'No', it checks 'Number complete?'. If 'Yes', it checks 'Presentation allowed?'. If 'No', it checks 'Special agreement on presentation?'. If 'Yes', it checks 'NPI = "ISDN/Telephony ITU-T E.164"?'. If 'No', it checks 'International number?'. If 'Yes', it performs 'Delete prefix digits (if any), add originating country code, set nature of address indicator to "international number"'. If 'No', it performs 'Omit GN parameter from IAM if Number qualifier = "additional calling party number"'. If 'Yes', it checks 'Number qualifier = "add. calling party number"?'. If 'Yes', it checks 'NPI = "ISDN/Telephony ITU-T E.164"?'. If 'No', it checks 'International number?'. If 'Yes', it performs 'Delete prefix digits (if any), add originating country code, set Nature of address indicator to "international number"'. If 'No', it performs 'Omit CPN parameter from IAM'. If 'Yes', it checks 'GN parameter present?'. If 'Yes', it performs 'Keep PR, SI and NI as provided by the incoming network'. If 'No', it performs 'Keep PR and SI as provided by the incoming network'. Finally, it goes to 'IAM' and then 'Idle'. + +**Figure 6-2 – Outgoing international gateway exchange dynamic description** + +![Flowchart for incoming international gateway exchange dynamic description. It starts at 'Idle', goes to 'Set up IAM', then checks if 'CPN parameter field present?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'CLI in CPN parameter?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'Is country code = own country code?'. If 'Yes', it goes to 'IAM'. If 'No', it performs actions: 'Add international prefix (optional)', 'Set Nature of address ind. accordingly to "international number" or "unknown"', and 'Keep PR, SI and NI as provided'. Then it checks 'GN parameter present?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'Number qualifier = "add. calling party number"?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'NPI = "ISDN/Telephony ITU-T E.164"?'. If 'Yes', it goes to 'IAM'. If 'No', it checks 'Is country code = own country code?'. If 'Yes', it goes to 'IAM'. If 'No', it performs actions: 'Remove country code', 'Add national prefix (optional)', 'Set nature of address ind. accordingly to "national (sign.) number" or "unknown"', and 'Keep PR and SI as provided'. All action blocks lead to 'IAM', which then leads to 'Idle'.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> SetUpIAM[Set up IAM] + SetUpIAM --> CPNPresent{CPN parameter field present?} + CPNPresent -- No --> IAM1[IAM] + CPNPresent -- Yes --> CLIPresent{CLI in CPN parameter?} + CLIPresent -- No --> IAM1 + CLIPresent -- Yes --> CCOwn{Is country code = own country code?} + CCOwn -- Yes --> IAM1 + CCOwn -- No --> CPNAction["In CPN parameter : +- Set PR to "address not available" +- Set SI to "network provided" +- Set Nature of address ind. +to "unknown" (optional)"] + CPNAction --> GNPresent{GN parameter present?} + GNPresent -- No --> IAM1 + GNPresent -- Yes --> NQ{Number qualifier = "add. calling party number"?} + NQ -- No --> IAM1 + NQ -- Yes --> NPI{NPI = "ISDN/Telephony ITU-T E.164"?} + NPI -- Yes --> IAM1 + NPI -- No --> CCOwn2{Is country code = own country code?} + CCOwn2 -- Yes --> IAM1 + CCOwn2 -- No --> NQAction["- Remove country code +- Add national prefix (optional) +- Set nature of address ind. +accordingly to "national (sign.) +number" or "unknown" +- Keep PR and SI as provided"] + NQAction --> IAM1 + Action2["- Add international prefix (optional) +- Set Nature of address ind. +accordingly to "international +number" or "unknown" +- Keep PR, SI and NI as provided"] --> IAM1 + IAM1 --> Idle2([Idle]) + +``` + +CLI Calling line identity      PR Presentation restrictions + CPN Calling party number    NI Number incomplete indicator + GN Generic number            IAM Initial address message + SI Screening indicator      NPI Numbering plan indicator + +Q.731.3(19)\_F6-3 + +Flowchart for incoming international gateway exchange dynamic description. It starts at 'Idle', goes to 'Set up IAM', then checks if 'CPN parameter field present?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'CLI in CPN parameter?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'Is country code = own country code?'. If 'Yes', it goes to 'IAM'. If 'No', it performs actions: 'Add international prefix (optional)', 'Set Nature of address ind. accordingly to "international number" or "unknown"', and 'Keep PR, SI and NI as provided'. Then it checks 'GN parameter present?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'Number qualifier = "add. calling party number"?'. If 'No', it goes to 'IAM'. If 'Yes', it checks 'NPI = "ISDN/Telephony ITU-T E.164"?'. If 'Yes', it goes to 'IAM'. If 'No', it checks 'Is country code = own country code?'. If 'Yes', it goes to 'IAM'. If 'No', it performs actions: 'Remove country code', 'Add national prefix (optional)', 'Set nature of address ind. accordingly to "national (sign.) number" or "unknown"', and 'Keep PR and SI as provided'. All action blocks lead to 'IAM', which then leads to 'Idle'. + +NOTE – This transition specifies additional processing to that described in Annex H of [ITU-T Q.764]. + +**Figure 6-3 – Incoming international gateway exchange dynamic description** + +![Flowchart of Destination local exchange dynamic description of the ISUP protocol. The process starts at 'Idle', proceeds to 'Set up IAM', then checks if the 'CPN parameter is present?'. If 'No', 'No information is sent to the access signalling system'. If 'Yes', it checks if the 'GN parameter is present?'. If 'No', it proceeds to 'SETUP or IAM'. If 'Yes', it checks if 'Number qualifier = "add. calling party number"?'. If 'No', it proceeds to 'SETUP or IAM'. If 'Yes', it sends information from the GN parameter, then the CPN parameter, and finally proceeds to 'SETUP or IAM'.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> SetUpIAM[/Set up IAM/] + SetUpIAM --> CPN_Present{CPN parameter is present?} + CPN_Present -- No --> NoInfo[No information is sent to the access signalling system] + CPN_Present -- Yes --> GN_Present{GN parameter is present?} + GN_Present -- No --> SetupIAM[/SETUP or IAM/] + GN_Present -- Yes --> NumberQualifier{Number qualifier = "add. calling party number"?} + NumberQualifier -- No --> SetupIAM + NumberQualifier -- Yes --> SendGN[Send the information conveyed in the GN parameter to the access signalling system] + SendGN --> SendCPN[Send the information conveyed in the CPN parameter to the access signalling system] + SendCPN --> SetupIAM + NoInfo --> SetupIAM + SetupIAM --> Idle2([Idle]) + +``` + +CPN Calling party number + GN Generic number + IAM Initial address message + +Q.731.3(19)\_F6-4 + +Flowchart of Destination local exchange dynamic description of the ISUP protocol. The process starts at 'Idle', proceeds to 'Set up IAM', then checks if the 'CPN parameter is present?'. If 'No', 'No information is sent to the access signalling system'. If 'Yes', it checks if the 'GN parameter is present?'. If 'No', it proceeds to 'SETUP or IAM'. If 'Yes', it checks if 'Number qualifier = "add. calling party number"?'. If 'No', it proceeds to 'SETUP or IAM'. If 'Yes', it sends information from the GN parameter, then the CPN parameter, and finally proceeds to 'SETUP or IAM'. + +NOTES 1 – It is a function of the access signalling system to check if the CLIP supplementary service is applicable and not to present presentation restricted numbers to the called user. + +NOTES 2 – The request option is not supported by private networks (identity always included). The request procedure can only be used to obtain the calling line identity in case of the malicious call identification supplementary service. + +NOTES 3 – This transition specifies additional processing to that described in Annex H of [ITU-T Q.764]. + +**Figure 6-4 – Destination local exchange dynamic description of the ISUP protocol** + + + +## 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.731.4-201904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.731.4-201904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..440b5d512bab4fb1e26801ae5b786b4434d93919 --- /dev/null +++ b/marked/Q/T-REC-Q.731.4-201904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05aab38e2f90b742763279bc89b1c956bf705bdaa14efa4c332c2e75dc30236b +size 4114 diff --git a/marked/Q/T-REC-Q.731.5-201904-I_PDF-E/raw.md b/marked/Q/T-REC-Q.731.5-201904-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..974c8a451feebb034dff0d3fa4c16a55c91acf34 --- /dev/null +++ b/marked/Q/T-REC-Q.731.5-201904-I_PDF-E/raw.md @@ -0,0 +1,967 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.731.5** + +(04/2019) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Specifications of Signalling System No. 7 – ISDN +supplementary services + +--- + +**Stage 3 description for number identification +supplementary services using Signalling +system No.7 – Connected line identification +presentation** + +Recommendation ITU-T Q.731.5 + +# 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 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.710 | +| 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 | +| 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 | +| 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.731.5 + +## Stage 3 description for number identification supplementary services using Signalling system No.7 – Connected line identification presentation + +## Summary + +Recommendation ITU-T Q.731.5 provides a signalling procedure for connected line identification presentation (COLP). It specifies service description, coding requirements and operation requirements of COLP. It also presents the signalling requirements for originating local exchange, transit exchange, international gateway exchange and destination local exchange. Interaction with other supplementary services, interaction with other network and dynamic description are also considered. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.731.5 | 1993-03-12 | XI | 11.1002/1000/2201 | +| 2.0 | ITU-T Q.731.5 | 2019-04-29 | 11 | 11.1002/1000/13880 | + +## Keywords + +Number identification, COLP, COLR, Signalling system No. 7. + +--- + +\* 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 ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Connected line identification presentation ..... | 3 | +| 6.1 Description ..... | 3 | +| 6.2 Operational requirements ..... | 4 | +| 6.3 Coding requirements ..... | 4 | +| 6.4 Signalling requirements..... | 5 | +| 6.5 Interaction with other supplementary services ..... | 8 | +| 6.6 Interaction with other networks..... | 10 | +| 6.7 Signalling flows..... | 10 | +| 6.8 Parameter value (timers)..... | 10 | +| 6.9 Dynamic description..... | 10 | + + + +## Recommendation ITU-T Q.731.5 + +## Stage 3 description for number identification supplementary services using Signalling system No.7 – Connected line identification presentation + +# 1 Scope + +This Recommendation provides signalling procedure for connected line identification presentation (COLP). It specifies service description, coding requirements and operation requirements of COLP. It also presents the signalling requirements for originating local exchange, transit exchange, international gateway exchange and destination local exchange. Interaction with other supplementary services, interaction with other network and dynamic description are included as well. + +# 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 references to a document within this Recommendation do not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T E.164] Recommendation ITU-T E.164 (2010), *The international public telecommunication numbering plan*. +- [ITU-T I.251.5] Recommendation ITU-T I.251.5 (1995), *Number identification supplementary services: Connected Line Identification Presentation (COLP)*. +- [ITU-T I.330] Recommendation ITU-T I.330 (1988), *ISDN numbering and addressing principles*. +- [ITU-T Q.81.5] Recommendation ITU-T Q.81.5 (1991), *Stage 2 description for number identification supplementary services: Connected line identification, presentation and restriction (COLP) and (COLR)*. +- [ITU-T Q.730] Recommendation ITU-T Q.730 (1999), *ISDN User Part supplementary services*. +- [ITU-T Q.761] Recommendation ITU-T Q.761 (1999), *Signalling System No. 7 – ISDN User Part functional description*. +- [ITU-T Q.762] Recommendation ITU-T Q.762 (1999), *Signalling System No. 7 – ISDN User Part general functions of messages and signals*. +- [ITU-T Q.763] Recommendation ITU-T Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes*. +- [ITU-T Q.764] Recommendation ITU-T Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures*. +- [ITU-T Q.767] Recommendation ITU-T Q.767 (1991), *Application of the ISDN User Part of CCITT signalling system No. 7 for international ISDN interconnections*. +- [ITU-T Q.951.5] Recommendation ITU-T Q.951.5 (1993), *Stage 3 description for number identification supplementary services using DSS 1: Connected line identification presentation*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 connected line identification presentation (COLP):** A supplementary service offered to the calling party which provides the connected party's ISDN number, with additional address information (e.g., connected party sub-address) if any, to the calling party at the call establishment phase. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------------| +| 3PTY | Three-Party service | +| AOC | Advice Of Charge | +| CCBS | Completion of Calls to Busy Subscriber | +| CD | Call Deflection | +| CFB | Call Forwarding Busy | +| CFNR | Call Forwarding No Reply | +| CFU | Call Forwarding Unconditional | +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| COL | Connected Line identity | +| COLP | Connected Line identification Presentation | +| COLR | Connected Line identification Restriction | +| CONF | Conference calling | +| CUG | Closed User Group | +| DDI | Direct Dialling-In | +| HOLD | call Hold | +| ISDN | Integrated Services Digital Network | +| ISUP | Integrated Services Digital Network User Part | +| LH | Line Hunting | +| MCID | Malicious Call Identification | +| MLPP | Multi-Level Precedence and Pre-Emption | +| MSN | Multiple Subscriber Number | +| PNP | Private Numbering Plan | +| PNX | Private Network exchange | +| REV | Reverse charging | + +| | | +|------|------------------------------------| +| SS | Signalling System | +| SUB | Sub-addressing | +| TP | Terminal Portability | +| 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 | + +# 5 Conventions + +None. + +# 6 Connected line identification presentation + +## 6.1 Description + +### 6.1.1 General description + +Connected line identification presentation (COLP) is a user facility that enables a user to be informed, on outgoing calls, of the address of the connected party. When provided, the facility applies to all outgoing calls except for when the connected party has the connected line identity restriction (COLR) facility active. + +The connected number may be provided by the destination local exchange or by the access signalling system of the connected user. If the connected number is received from the connected user, the information is normally verified and passed to the originating exchange. If no information is received from the connected user, the destination exchange shall generate the connected number. + +By special arrangement, verification of the connected number information provided by the user may be inhibited. The information is conveyed by the network in the generic number parameter field of the answer (ANM) or connect (CON) message. The service has no impact on the signalling procedures. + +The connected line identity (COL) is the ISDN number of the connected party (with additional address information, + +e.g., connected party sub-address, if any) which may be provided by the network or by the connected party or partially by the network with the rest provided by the connected party. + +Only full international number, i.e., including the country code, should be passed across the international boundary. + +Moreover, the information on the COL may include address information generated by the connected user and transparently transported by the network. The sub-address is subject to a maximum of 20 octets. The network is not responsible for the content of this additional address information. + +The stage 1 CCITT definition for the COLP service is given in [ITU-T I.251.5]. The stage 2 CCITT description is contained in [ITU-T Q.81.5]. The stage 3 DSS 1 description is given in [ITU-T Q.951.5]. This stage 3 description of COLP and COLR uses the ISDN user part protocol as defined in [ITU-T Q.761] to [ITU-T Q.764] and [ITU-T Q.730]. + +### 6.1.2 Specific terminology + +In addition to the term defined in clause 3, this Recommendation uses the following specific terminology: + +**ISDN number** – A number conforming to the numbering plan and structure specified in [ITU-T E.164]. + +**Sub-address** – See Clause 5.4 of [ITU-T I.330]. + +**Served access** – It is the user of a particular ISDN number who has subscribed to the presentation of the connected line identification information in association with outgoing calls. The served user may also be known as the calling access. + +**Connected access** – It is the user that receives an incoming call from the served user. The connected access need not have subscribed to the COLP supplementary service. + +**Default number** – A national significant ISDN number registered within the public ISDN following prior arrangement between the connected access and the public ISDN. + +**Special arrangement** – An arrangement between a customer and a public network operator whereby customer supplied connected numbers are not screened by the public network. + +**Access signalling system** – A part in the local exchange which handles the user-network interface protocol. It also includes the screening functions. + +### **6.1.3 Qualification on the applicability to telecommunication services** + +Not applicable. + +### **6.1.4 State definitions** + +No specific state definitions are required. + +## **6.2 Operational requirements** + +### **6.2.1 Provision/withdrawal** + +See clause 3.1 of [ITU-T I.251.5]. + +### **6.2.2 Requirements on the originating network side** + +Not applicable. + +### **6.2.3 Requirements in the network** + +No specific requirements are needed in the network. + +### **6.2.4 Requirements on the terminating network side** + +Not applicable. + +## **6.3 Coding requirements** + +Clause 3.16 of [ITU-T Q.763], clause 3.38 of [ITU-T Q.763] and clause 3.26 of [ITU-T Q.763] give the coding for the connected number, optional forward call indicators, generic number parameters and the access transport parameter fields which are required to support this service. + +The purpose of the generic number parameter field is to transport a connected number provided by the connected user with a special arrangement. This screening indicator shall be set to "user provided, not verified". + +The generic number parameter is accompanied by the parameter compatibility information parameter. The procedures for compatibility are defined in [ITU-T Q.764]. + +### **Allowed codings for the generic number parameter** + +- a) *Number qualifier indicator* +00000101 additional connected number + +- b) *Odd/even indicator* +See clause 3.26 b) of [ITU-T Q.763] +- c) *Nature of address indicator* +0000001 subscriber number (for national use) +0000010 unknown (national use) +0000011 national (significant) number +0000100 international number +- d) *Internal network number indicator/number incomplete indicator* +0 (not used) +- e) *Numbering plan indicator* +001 ISDN (Telephony) numbering plan ([ITU-T E.164]) +- f) *Address presentation restricted indicator* +1 presentation allowed +2 presentation restricted +- g) *Screening indicator* +00 user provided, not verified +- h) *Address signals* +0000 digit 0 +0001 digit 1 +0010 digit 2 +0011 digit 3 +0100 digit 4 +0101 digit 5 +0110 digit 6 +0111 digit 7 +1000 digit 8 +1001 digit 9 +- i) *Filler* +See clause 3.26 i) of [ITU-T Q.763]. + +## **6.4 Signalling requirements** + +### **6.4.1 Activation/deactivation/registration** + +Not applicable. + +### **6.4.2 Invocation and operation** + +#### **6.4.2.1 Actions at the originating local exchange** + +##### **6.4.2.1.1 Normal operation** + +When the calling party has subscribed to the COLP facility, the exchange shall include in the optional forward call indicator in the IAM, a request to use the COLP facility for this call. + +The COL information is conveyed by the network in the connected number parameter field of the answer (ANM) or connect (CON) message, unless the user has an agreement to provide unscreened information, in which case the connected number parameter field will convey the network default + +number, and the user provided unscreened information will be carried as received from the access signalling system in the generic number parameter also conveyed in the ANM or CON message. + +When the generic number parameter field with a number qualifier set to "additional connected number" is provided together with the connected number, then this number shall be sent in addition, to the calling access. The address presentation restricted indicator and screening indicator sent to the calling access shall be passed transparently. + +When the calling party has not subscribed to the COLP facility no particular actions are required. When a request for the COL is not included in the IAM, the connected number parameter should not be included in either the answer or connect message. However, if this information is included, it shall not be considered as a protocol error and the call should continue. + +It is a function of the user-network interface to check whether the calling user has subscribed to the COLP supplementary service, and not to present the COL or sub-address if no subscription exists. + +##### **6.4.2.1.2 Exceptional procedures** + +No exceptional procedures are identified. + +#### **6.4.2.2 Actions at the transit exchange** + +##### **6.4.2.2.1 Normal operation** + +The transit exchange shall transparently pass on all information related to the COLP supplementary service. + +##### **6.4.2.2.2 Exceptional procedures** + +No exceptional procedures are identified. + +#### **6.4.2.3 Actions at the outgoing international gateway exchange** + +##### **6.4.2.3.1 Normal operation** + +The exchange shall check if the country code of the connected number is the network's own country code. If this is the case then the country code shall be removed. The nature of address indicator shall be set to "national (significant) number". The address presentation restricted indicator and the screening indicator shall be transferred transparently. + +NOTE – As a national option, the outgoing international gateway exchange may add a prefix to the connected number. In this case the nature of address indicator shall be set to "unknown". + +If the generic number parameter field is received and its number qualifier indicates "additional connected number", and the numbering plan indicator is coded "ISDN (Telephony) numbering plan ([ITU-T E.164])", then the generic number parameter shall be treated in the same manner as the connected number parameter. + +##### **6.4.2.3.2 Exceptional procedures** + +No exceptional procedures are identified. + +#### **6.4.2.4 Actions at the incoming international gateway exchange** + +##### **6.4.2.4.1 Normal operation** + +At the international boundary, the destination gateway can remove the COL digits if it cannot be released to the originating network and set the address presentation restricted indicator to "address not available". + +If the address presentation restricted indicator of the received connected number parameter field is set to "presentation restricted", the destination international gateway exchange shall act according to the bilateral agreement between the two networks. If the connected number parameter field is not + +sent across the international section, then the generic number parameter field shall also be omitted from the CON or ANM message if its number qualifier indicates "additional connected number". + +The exchange shall convert the connected number parameter field to an international number (if necessary) and set the nature of address indicator to "international number". The address presentation restricted indicator and the screening indicator shall be transferred transparently. + +If the generic number parameter field is received and its number qualifier indicates "additional connected number" and the numbering plan indicator is coded "ISDN (Telephony) numbering plan ([ITU-T E.164])", then the generic number parameter shall be treated in the same manner as the connected number parameter. + +##### **6.4.2.4.2 Exceptional procedures** + +No exceptional procedures identified. + +#### **6.4.2.5 Actions at the destination local exchange** + +##### **6.4.2.5.1 Normal operation** + +The exchange shall deliver the COL only if it was requested at call set-up. However, if it is included in the answer or connect message when it has not been requested it should not be considered as a protocol error and the call should be allowed to continue. + +In the case where a connected party is a PNX, the network sends the ISDN number and the DDI number of the extension as the COL if the extension digits are provided by the connected party. If the extension digits are not provided the network sends the ISDN default number. The default number is stored within the network but the value is agreed between the Administration and the customer concerned. + +When the COL is provided by the user or PNX, it might be verified or screened for validity by the network, i.e., the COL provided by the user is within the known number range for that user. + +- i) If the user provided COL is valid the connected number parameter field contains the COL in the address signals with the screening indicator set to "user provided verified and passed". +- ii) If the user provided COL is not valid the destination exchange inserts the default number for the address signals with the screening indicator set to "network provided". +- iii) If the user has a special arrangement with the network, that the user provided COL is not screened, then the destination local exchange shall disregard any value of the screening indicator, if received from the connected access. + +The connected number received from the called access shall be entered in the generic number parameter field. In this parameter field, the number qualifier indicator shall be set to "additional connected number", the screening indicator set to "user provided, not verified". The numbering plan indicator is coded "ISDN (Telephony) numbering plan ([ITU-T E.164])" if the numbering plan indicator received from the access signalling system indicates "unknown". The nature of address indicator shall be set to "international number" or "national (significant) number" as received from the connected access. + +In addition, the destination local exchange shall enter the default number associated with the connected user in the connected number parameter field. In this parameter field, the screening indicator shall be set to "network provided" and the nature of address indicator to "national (significant) number". + +- iv) If there is no agreement and the user provided COL is not valid, the destination exchange defaults to the network provided COL for the address signals of the connected number parameter field with the screening indicator set to "network provided". + +Optionally, a connected party sub-address may be included, if received from the called access, in the connected sub-address information element which is transported in the access transport parameter. + +If the COL cannot be transferred (because it is not allowed to be passed or because the national network cannot provide the number) then the connected number parameter should be included in the ANM or CON messages with the indication "presentation restricted" or "address not available" set as appropriate in the address presentation restriction indicator and set the screening indicator to "network provided". + +The numbering plan indicator of the connected number parameter field shall be set to "ISDN (Telephony) numbering plan ([ITU-T E.164])". + +The numbering plan indicator of the generic number parameter field shall be set to "ISDN (Telephony) numbering plan ([ITU-T E.164])" if the numbering plan indicator received from the access signalling system indicates "unknown". + +The address presentation restricted indicators of the connected number and the generic number parameter fields shall be set to "presentation allowed" or "presentation restricted" as received from the access signalling system. + +##### **6.4.2.5.2 Exceptional procedures** + +No exceptional procedures are identified. + +## **6.5 Interaction with other supplementary services** + +### **6.5.1 Call waiting (CW)** + +No impact on ISUP. + +### **6.5.2 Call transfer services** + +No applicable interaction at this time. + +### **6.5.3 Connected line identification presentation (COLP)** + +Not applicable. + +### **6.5.4 Connected line identification restriction (COLR)** + +The COLR supplementary service shall take precedence over the COLP supplementary service. + +The COLP supplementary service can take precedence over the COLR supplementary service when the calling access has an override category. This is a national option. + +### **6.5.5 Calling line identification presentation (CLIP)** + +No impact on ISUP. + +### **6.5.6 Calling line identification restriction (CLIR)** + +No impact on ISUP. + +### **6.5.7 Closed user group (CUG)** + +No impact on ISUP. + +### **6.5.8 Conference calling (CONF)** + +No impact on ISUP. + +### **6.5.9 Direct dialling-in (DDI)** + +No impact on ISUP. + +### **6.5.10 Call diversion services** + +#### **6.5.10.1 Call forwarding busy (CFB)** + +No impact on ISUP. + +#### **6.5.10.2 Call forwarding no reply (CFNR)** + +No impact on ISUP. + +#### **6.5.10.3 Call forwarding unconditional (CFU)** + +No impact on ISUP. + +#### **6.5.10.4 Call deflection (CD)** + +No impact on ISUP. + +### **6.5.11 Line hunting (LH)** + +No impact on ISUP. + +### **6.5.12 Three party service (3PTY)** + +No impact on ISUP. + +### **6.5.13 User-to-user signalling (UUS)** + +#### **6.5.13.1 User-to-user signalling, service 1 (UUS1)** + +No impact on ISUP. + +#### **6.5.13.2 User-to-user signalling, service 2 (UUS2)** + +No impact on ISUP. + +#### **6.5.13.3 User-to-user signalling, service 3 (UUS3)** + +No impact on ISUP. + +### **6.5.14 Multiple subscriber number (MSN)** + +If the multiple subscriber number supplementary service is applicable to the public network access interface of the connected party, then this party can provide the appropriate connected party multiple subscriber number digits or full ISDN number on call answer. If no special arrangement has been made with the connected subscriber, then the network shall check the user provided connected number information for validity on the corresponding access. If the check fails or if no connected number information is provided by the user, then the network shall apply the default number of the connected number. + +If the multiple subscriber number supplementary service is applicable to the public network access interface of the calling access, then neither supplementary service shall affect the operation of the other supplementary service. + +### **6.5.15 Call hold (HOLD)** + +No impact on ISUP. + +### **6.5.16 Advice of charge (AOC)** + +No impact on ISUP. + +### **6.5.17 Sub-addressing (SUB)** + +No impact on ISUP. + +### **6.5.18 Terminal portability (TP)** + +No impact on ISUP. + +### **6.5.19 Completion of calls to busy subscriber (CCBS)** + +No applicable interaction at this time. + +### **6.5.20 Malicious call identification (MCID)** + +No impact on ISUP. + +### **6.5.21 Reverse charging (REV)** + +No applicable interaction at this time. + +### **6.5.22 Multi-level precedence and preemption (MLPP)** + +No impact on ISUP. + +### **6.5.23 Private numbering plan (PNP)** + +No applicable interaction at this time. + +### **6.5.24 Charge card** + +No applicable interaction at this time. + +## **6.6 Interaction with other networks** + +On calls from ISDN networks where the preceding signalling section supports only one connected number to be carried, the information contained in the connected number parameter field shall be returned. The generic number parameter field shall be discarded. + +On calls incoming from non-ISDNs, the COL will be discarded, if received. + +On a call where COL has been requested, to networks not supporting the service, the request will be discarded. + +## **6.7 Signalling flows** + +Indicated in Figures 6-1 to 6-4. + +## **6.8 Parameter value (timers)** + +No specific timers are required. + +## **6.9 Dynamic description** + +The dynamic description is specified in Figures 6-5 to 6-8. + +![](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +| | Calling user | Originating exchange | Transit exchange | Destination exchange | Called user | +|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|--------------------------------------------------------------------|-------------------------------------------|----------------------|-------------| +| Connected line identity provided by the called user | SETUP → | IAM → | IAM → | SETUP → | | +| | | COLP-request → | COLP-request → | | | +| | ← ALERTING | ← ACM | ← ACM
(NOTE 2) | ← ALERTING | | +| | ← CONNECT | ← ANM/CON | ← ANM/CON | ← CONNECT | | +| Connected number + sub-address (optional) | Connected number + sub-address (if provided)
PR = 00
SI = 01 | Connected number + sub-address (if provided)
PR = 00
SI = 01 | Connected number + sub-address (optional) | | | +| Connected line identity, not provided by the called user or provided but not valid or screened | SETUP → | IAM → | IAM → | SETUP → | | +| | | COLP-request → | COLP-request → | | | +| | ← ALERTING | ← ACM | ← ACM | ← ALERTING | | +| | ← CONNECT | ← ANM/CON | ← ANM/CON | ← CONNECT | | +| Connected number | Connected number
PR = 00
SI = 11 | Connected number
PR = 00
SI = 11 | | | | + +Q.731.5(19)\_F6-1 + +NOTE 1 – This service subscribed by the calling user and the request is included by originating exchange. + +NOTE 2 – The connect message is appropriate only if the answer condition is detected prior to the return of the address complete message. + +**Figure 6-1 – Connected line identification presentation** + +![](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Sequence diagram illustrating Connected line identification presentation across five entities: Calling user, Originating exchange, Transit exchange, Destination exchange, and Called user. + +Timeline: + +- SETUP:** Calling user → Originating exchange → Transit exchange → Destination exchange → Called user. +- COLP-request:** Originating exchange → Transit exchange → Destination exchange. +- ALERTING:** Destination exchange → Called user → Transit exchange → Originating exchange → Calling user. +- ACM:** Destination exchange → Transit exchange → Originating exchange. +- CONNECT:** Destination exchange → Called user → Transit exchange → Originating exchange → Calling user. +- Connected number:** + - Originating exchange → Calling user (NOTE 4) + - Transit exchange → Originating exchange (NOTE 5) + - Destination exchange → Transit exchange (NOTE 3 and 5) + +Connected number details: + +- Originating exchange:** + - Connected number PR = 00, SI = 11 + - Generic number (+ sub-address if provided) PR = 00, SI = 00 +- Transit exchange:** + - Connected number PR = 00, SI = 11 + - Generic number (+ sub-address if provided) PR = 00, SI = 00 + +Connected line identity provided by the called user. User has agreement with the network provider that COL will not be verified + +Q.731.5(19)\_F6-2 + +NOTE 1 – This service is subscribed by the calling user and the request is included by the originating exchange. + +NOTE 2 – The connect message is appropriate only if the answer condition is detected prior to the return of the address complete message. + +NOTE 3 – It is the responsibility of the calling party access or private network ISDN to determine which COL to present to the calling user. + +NOTE 4 – If the setting of the presentation restriction indicator in the connected number parameter is in conflict with the setting of the presentation restriction indicator in the generic number, the presentation will be assumed to be restricted. + +NOTE 5 – Subaddress is conveyed in the ATP. + +**Figure 6-2 – Connected line identification presentation** + +![Sequence diagrams for connected line identification restriction. The top diagram shows the case where the identity is provided by the called user. The bottom diagram shows the case where the identity is not provided or invalid. Both diagrams show message exchanges between Calling user, Originating exchange, Transit exchange, Destination exchange, and Called user.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +**Top Diagram: Connected line identity provided by the called user** + +| Calling user | Originating exchange | Transit exchange | Destination exchange | Called user | +|--------------|--------------------------------------------------------------------|--------------------------------------------------------------------|-------------------------------------------|-------------| +| SETUP → | | | | | +| | IAM → | | | | +| | COLP-request → | | | | +| | | IAM → | | | +| | | COLP-request → | | | +| ← ALERTING | | | | | +| | ← ACM | | | | +| | | ← ACM (NOTE 3) | | | +| | | | ← ALERTING | | +| ← CONNECT | | | | | +| | ← ANM/CON | | | | +| | | ← ANM/CON | | | +| | | | ← CONNECT | | +| | Connected number + sub-address (if provided)
PR = 01
SI = 01 | Connected number + sub-address (if provided)
PR = 01
SI = 01 | Connected number + sub-address (optional) | | + +**Bottom Diagram: Connected line identity, not provided by the called user or provided but not valid or screened** + +| Calling user | Originating exchange | Transit exchange | Destination exchange | Called user | +|--------------|----------------------------------------|----------------------------------------|----------------------|-------------| +| SETUP → | | | | | +| | IAM → | | | | +| | COLP-request → | | | | +| | | IAM → | | | +| | | COLP-request → | | | +| ← ALERTING | | | | | +| | ← ACM | | | | +| | | ← ACM | | | +| | | | ← ALERTING | | +| ← CONNECT | | | | | +| | ← ANM/CON | | | | +| | | ← ANM/CON | | | +| | | | ← CONNECT | | +| | Connected number
PR = 01
SI = 11 | Connected number
PR = 01
SI = 11 | | | + +Sequence diagrams for connected line identification restriction. The top diagram shows the case where the identity is provided by the called user. The bottom diagram shows the case where the identity is not provided or invalid. Both diagrams show message exchanges between Calling user, Originating exchange, Transit exchange, Destination exchange, and Called user. + +Q.731.5(19)\_F6-3 + +NOTE 1 – This service subscribed by the calling user and the request is included by the originating exchange. + +NOTE 2 – This service is subscribed by the called user and stored at the destination exchange. + +NOTE 3 – The connect message is appropriate only if the answer condition is detected prior to the return of the address complete message. + +**Figure 6-3 – Connected line identification restriction** + +![Sequence diagram for Connected line identification restriction showing message exchanges between Calling user, Originating exchange, Transit exchange, Destination exchange, and Called user. The diagram shows the flow of SETUP, IAM, COLP-request, ALERTING, ACM, CONNECT, and ANM/CON messages, with specific details on connected and generic numbers in the ANM/CON messages.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +sequenceDiagram + participant CU as Calling user + participant OE as Originating exchange + participant TE as Transit exchange + participant DE as Destination exchange + participant CD as Called user + + Note left of CU: Connected line identity +provided by the called user. +User has agreement with the +network provider that +COL will not be verified + + CU->>OE: SETUP + OE->>TE: IAM + OE->>TE: COLP-request + TE->>DE: IAM + TE->>DE: COLP-request + DE->>CD: SETUP + + CD-->>DE: ALERTING + DE-->>TE: ACM + TE-->>OE: ACM + OE-->>CU: ALERTING + + CD-->>DE: CONNECT + DE-->>TE: ANM/CON + Note over DE,TE: Connected number +PR = 01 +SI = 11 +Generic number +(+ sub-address +if provided) +PR = 01 +SI = 00 +(NOTE 3 and 5) + TE-->>OE: ANM/CON + Note over TE,OE: Connected number +PR = 01 +SI = 11 +Generic number +(+ sub-address +if provided) +PR = 01 +SI = 00 +(NOTE 5) + OE-->>CU: CONNECT + Note over OE,CU: Connected number + +(NOTE 4) + +``` + +Q.731.5(19)\_F6-4 + +Sequence diagram for Connected line identification restriction showing message exchanges between Calling user, Originating exchange, Transit exchange, Destination exchange, and Called user. The diagram shows the flow of SETUP, IAM, COLP-request, ALERTING, ACM, CONNECT, and ANM/CON messages, with specific details on connected and generic numbers in the ANM/CON messages. + +NOTE 1 – This service is subscribed by the calling user and the request is included by the originating exchange. + +NOTE 2 – The connect message is appropriate only if the answer condition is detected prior to the return of the address complete message. + +NOTE 3 – It is the responsibility of the calling party access or private network ISDN to determine which COL to present to the calling user. + +NOTE 4 – If the setting of the presentation restriction indicator in the connected number parameter is in conflict with the setting of the presentation restriction indicator in the generic number, the presentation will be assumed to be restricted. + +NOTE 5 – Sub-address is conveyed in the ATP. + +**Figure 6-4 – Connected line identification restriction** + +![Flowchart of nodal signalling functions for COLP and COLR. The process starts at 'Idle', receives 'CON or ANM', checks if COL is requested. If not, it omits the party number. If requested, it checks if COL is available. If not, it sets PR=10, SI=11. If available, it checks if supplied by the user. If not, it uses a default number (SI=11). If supplied, it checks if SI=00. If not, it uses the user-provided number (SI=01). If SI=00, it uses a generic CPN (SI=00). Finally, it checks for presentation restrictions and sets the nature of address indicator before returning to 'CON or ANM' and 'Idle'.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> CONANM1[CON or ANM] + CONANM1 --> WasRequested{Was COL requested on this call?} + WasRequested -- No --> Omit[Omit connected party number parameter field from CON or ACM] + WasRequested -- Yes --> Available{COL available?} + Available -- No --> SetPR10[Set PR = 10 +SI = 11] + Available -- Yes --> Supplied{COL supplied by connected user?} + Supplied -- No --> Default[CPN = default number (NOTE) +set SI = 11] + Supplied -- Yes --> SI00{User provided SI = 00?} + SI00 -- No --> Generic[Generic CPN user provided number +(keep PR, set SI = 00)] + SI00 -- Yes --> UserProvided[CPN = user provided number keep PR +set SI = 01] + Default --> Restriction{Any presentation restriction?} + Generic --> Restriction + UserProvided --> Restriction + Restriction -- Yes --> SetPR01[Set PR = 01] + Restriction -- No --> SetPR00[Set PR = 00] + SetPR10 --> Nature[Set nature of address and incomplete number indicator] + SetPR01 --> Nature + SetPR00 --> Nature + Omit --> Nature + Nature --> CONANM2[CON or ANM] + CONANM2 --> Idle2([Idle]) + +``` + +Q.731.5(19)\_F6-5 + +COL Connected line identity + PR Presentation restriction + SI Screening indicator + +Flowchart of nodal signalling functions for COLP and COLR. The process starts at 'Idle', receives 'CON or ANM', checks if COL is requested. If not, it omits the party number. If requested, it checks if COL is available. If not, it sets PR=10, SI=11. If available, it checks if supplied by the user. If not, it uses a default number (SI=11). If supplied, it checks if SI=00. If not, it uses the user-provided number (SI=01). If SI=00, it uses a generic CPN (SI=00). Finally, it checks for presentation restrictions and sets the nature of address indicator before returning to 'CON or ANM' and 'Idle'. + +NOTE – The default number is a network supplied default number. + +**Figure 6-5 – Nodal signalling functions for COLP and COLR Destination local exchange** + +![Flowchart of nodal signalling functions for COLP and COLR incoming international gateway. The process starts at 'Idle', receives 'CON or ANM', checks if COL was requested. If 'No', it checks if COL should be provided anyway (NOTE 2). If 'No', it omits the connected party number and generic number parameter field. If 'Yes', it checks if COL is present in the connected number field. If 'No', it sets the CNP field to 'number not available'. If 'Yes' (NOTE 1), it checks if presentation is allowed. If 'No', it checks for a special agreement on PR (NOTE 2). If 'No', it omits the field. If 'Yes', it checks if it's an international number. If 'Yes', it keeps PR and SI. If 'No', it processes the number (delete trunk prefix, add country code, set nature of address). Then it checks the COL generic number param field. If 'Yes', it checks if it's an international number. If 'Yes', it keeps PR, NI and SI. If 'No', it omits the add CPN parameter field. Finally, it sends 'CON or ANM' and returns to 'Idle'.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> CONANM1[CON or ANM] + CONANM1 --> WasCOLRequested{Was COL requested on this call?} + WasCOLRequested -- No --> IsCOLProvided{Is COL to be provided anyway? (NOTE 2)} + WasCOLRequested -- Yes --> COLPresent{COL present in connected number field?} + IsCOLProvided -- No --> OmitCNP[Omit connected party number and generic number parameter field from CON and ANM] + IsCOLProvided -- Yes --> COLPresent + COLPresent -- No --> CNPField[CNP field = "number not available" omit generic number parameter] + COLPresent -- Yes (NOTE 1) --> PresentationAllowed{Presentation allowed?} + PresentationAllowed -- No --> SpecialAgreement{Special agreement on PR? (NOTE 2)} + PresentationAllowed -- Yes --> InternationalNumber1{International number?} + SpecialAgreement -- No --> OmitCNP + SpecialAgreement -- Yes --> InternationalNumber1 + InternationalNumber1 -- Yes --> KeepPRSI[Keep PR and SI as provided by the I/C network] + InternationalNumber1 -- No --> ProcessNumber["- Delete trunk prefix (IF any) +- Add terminating country code +- Set nature of address indication to 'international number'"] + ProcessNumber --> KeepPRSI + KeepPRSI --> COLGenericParam{COL generic number param field?} + COLGenericParam -- Yes --> InternationalNumber2{International number?} + COLGenericParam -- No --> OmitCPN[Omit add CPN parameter field from IAM] + InternationalNumber2 -- Yes --> ProcessNumber2["- Delete trunk prefix (if any) +- Set nature of address indicator to 'international number' +- Add terminating country code"] + InternationalNumber2 -- No --> KeepPRNISI[Keep PR, NI and SI as provided by the incoming network] + ProcessNumber2 --> KeepPRNISI + OmitCNP --> CONANM2[CON or ANM] + CNPField --> CONANM2 + OmitCPN --> CONANM2 + KeepPRNISI --> CONANM2 + CONANM2 --> Idle2([Idle]) + +``` + +Q.731.5(19)\_F6-6 + +COL Connected line identity + PR Presentation restriction + SI Screening indicator + NI Number incomplete indicator + +Flowchart of nodal signalling functions for COLP and COLR incoming international gateway. The process starts at 'Idle', receives 'CON or ANM', checks if COL was requested. If 'No', it checks if COL should be provided anyway (NOTE 2). If 'No', it omits the connected party number and generic number parameter field. If 'Yes', it checks if COL is present in the connected number field. If 'No', it sets the CNP field to 'number not available'. If 'Yes' (NOTE 1), it checks if presentation is allowed. If 'No', it checks for a special agreement on PR (NOTE 2). If 'No', it omits the field. If 'Yes', it checks if it's an international number. If 'Yes', it keeps PR and SI. If 'No', it processes the number (delete trunk prefix, add country code, set nature of address). Then it checks the COL generic number param field. If 'Yes', it checks if it's an international number. If 'Yes', it keeps PR, NI and SI. If 'No', it omits the add CPN parameter field. Finally, it sends 'CON or ANM' and returns to 'Idle'. + +NOTE 1 – This flow assumes that there is no restriction on passing non-restricted COL's across the international boundary. If no such agreement exists then any COL in the incoming CON or ANM will be removed and the PR indicator set to 10, "COL not available". + +NOTE 2 – Based on bilateral agreement. + +**Figure 6-6 – Nodal signalling functions for COLP and COLR Incoming international gateway** + +![Flowchart of nodal signalling functions for COLP and COLR outgoing international gateway exchange. The process starts at 'Idle', receives 'CON or ANM', checks if COL is requested. If not, it omits party number fields. If requested, it checks if COL identity is in the CON number param field. If yes, it checks if the country code is the own country code. If yes, it removes the country code and adds a national prefix. If no, it adds an international prefix. If COL identity is not in the CON number param field, it checks if COL is in a generic number field. If yes, it again checks if the country code is the own country code and follows similar logic. If no, it sets PR=10 and SI=11. All paths lead to a final 'CON or ANM' and 'Idle' state.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> CONANM1[CON or ANM] + CONANM1 --> WasCOLRequested{Was COL requested on this call?} + WasCOLRequested -- No --> OmitParty[Omit connected party number parameter field from CON or ACM
Delete generic number COL] + WasCOLRequested -- Yes --> COLIdentityPresent{COL identity present in CON number param field?} + COLIdentityPresent -- No --> PRSI1011[PR = 10
SI = 11] + COLIdentityPresent -- Yes --> IsOwnCountryCode1{Is country code = own country code?} + IsOwnCountryCode1 -- Yes --> RemoveCC1[Remove country code
Add national prefix (optional)
Set nature of address indicator = national significant number
Keep PR and SI as provided] + IsOwnCountryCode1 -- No --> AddIP1[Add international prefix (optional)
Set nature of address indication to "international number" or "unknown"
Keep PR and SI as provided] + AddIP1 --> COLGenericField{COL in generic number field?} + RemoveCC1 --> COLGenericField + COLGenericField -- No --> PRSI1011 + COLGenericField -- Yes --> IsOwnCountryCode2{Is country code = own country code?} + IsOwnCountryCode2 -- Yes --> RemoveCC2[Remove country code
Add national prefix (optional)
Set nature of address indicator = national significant number
Keep PR and SI as provided] + IsOwnCountryCode2 -- No --> AddIP2[Add international prefix (optional)
Set nature of address indication to "international number" or "unknown"
Keep PR and SI as provided] + AddIP2 --> CONANM2[CON or ANM] + RemoveCC2 --> CONANM2 + CONANM2 --> Idle2([Idle]) + OmitParty --> CONANM2 + PRSI1011 --> CONANM2 + +``` + +Q.731.5(19)\_F6-7 + +COL Connected line identity + PR Presentation restriction + SI Screening indicator + +Flowchart of nodal signalling functions for COLP and COLR outgoing international gateway exchange. The process starts at 'Idle', receives 'CON or ANM', checks if COL is requested. If not, it omits party number fields. If requested, it checks if COL identity is in the CON number param field. If yes, it checks if the country code is the own country code. If yes, it removes the country code and adds a national prefix. If no, it adds an international prefix. If COL identity is not in the CON number param field, it checks if COL is in a generic number field. If yes, it again checks if the country code is the own country code and follows similar logic. If no, it sets PR=10 and SI=11. All paths lead to a final 'CON or ANM' and 'Idle' state. + +**Figure 6-7 – Nodal signalling functions for COLP and COLR Outgoing international gateway exchange** + +![Flowchart for originating local exchange. It starts with 'Idle', followed by 'SETUP or CON or ANM'. A decision diamond asks 'CPN parameter field is present?'. If 'No', it goes to 'No information is sent to the access signalling system'. If 'Yes', it goes to another decision diamond 'CPN parameter field is present?'. If this second 'No', it loops back to the first decision. If 'Yes', it goes to a decision 'Number qualifier = "add. connected party number"?'. If 'No', it loops back to the first decision. If 'Yes', it goes to 'Send the information conveyed in the CN parameter field to the access signalling system'. Both 'No information is sent...' and 'Send the information...' lead to 'SETUP CON or ANM', which then leads to 'Idle'.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> SETUP1[SETUP or CON or ANM] + SETUP1 --> CPN1{CPN parameter field is present?} + CPN1 -- No --> NoInfo[No information is sent to the access signalling system] + CPN1 -- Yes --> CPN2{CPN parameter field is present?} + CPN2 -- No --> CPN1 + CPN2 -- Yes --> NumQual{Number qualifier = "add. connected party number"?} + NumQual -- No --> CPN1 + NumQual -- Yes --> SendInfo[Send the information conveyed in the CN parameter field to the access signalling system] + NoInfo --> SETUP2[SETUP CON or ANM] + SendInfo --> SETUP2 + SETUP2 --> Idle2([Idle]) + +``` + +CN    Connected number + GN    Generic number + IAM   Initial address message + +Q.731.5(19)\_F6-8 + +Flowchart for originating local exchange. It starts with 'Idle', followed by 'SETUP or CON or ANM'. A decision diamond asks 'CPN parameter field is present?'. If 'No', it goes to 'No information is sent to the access signalling system'. If 'Yes', it goes to another decision diamond 'CPN parameter field is present?'. If this second 'No', it loops back to the first decision. If 'Yes', it goes to a decision 'Number qualifier = "add. connected party number"?'. If 'No', it loops back to the first decision. If 'Yes', it goes to 'Send the information conveyed in the CN parameter field to the access signalling system'. Both 'No information is sent...' and 'Send the information...' lead to 'SETUP CON or ANM', which then leads to 'Idle'. + +NOTE 1 – It is a function of the access signalling system to check if the COLP supplementary service is applicable and not to present presentation restricted numbers to the calling user. + +NOTE 2 – The request option is not supported by private networks (identity always included). The request procedure can only be used to obtain the connected line identity. + +NOTE 3 – This transition specifies additional processing to that described in Annex B of [ITU-T Q.764]. + +**Figure 6-8 – Originating local exchange** + + + +# 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.731.8-199202-I_PDF-E/raw.md b/marked/Q/T-REC-Q.731.8-199202-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9b7c176a1296651ad4704a64005a9ab765756c3c --- /dev/null +++ b/marked/Q/T-REC-Q.731.8-199202-I_PDF-E/raw.md @@ -0,0 +1,263 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**Q.731.8** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +(02/92) + +# **SPECIFICATIONS OF SIGNALLING SYSTEM No. 7** --- + +## **STAGE 3 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES USING SIGNALLING SYSTEM No. 7** + +**SECTION 8 – SUB-ADDRESSING (SUB)** + +**Recommendation Q.731.8** + +--- + +![CEPT logo: A globe with the letters CEPT.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +CEPT logo: A globe with the letters CEPT. + +Geneva, 1992 + +## FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation Q.731, § 8 was prepared by Study Group XI and was approved under the Resolution No. 2 procedure on the 4th of February 1992. + +## --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. + +## Recommendation Q.731.8 + +## STAGE 3 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES USING SIGNALLING SYSTEM No. 7 – SUB-ADDRESSING (SUB) + +## 8 Sub-addressing (SUB) + +### 8.1 *Definition* + +The Sub-address supplementary service allows the called (served) user to expand his addressing capacity beyond the one given by the ISDN number. + +The stage 1 service description is given in Recommendation I.251.8 and the stage 2 functional capabilities and information flows are given in Recommendation Q.81, § 8. The stage 3 description of the sub-address supplementary service uses the ISDN user part protocol as defined in Recommendations Q.761 to Q.764 and Q.767. + +### 8.2 *Description* + +#### 8.2.1 *General description* + +The sub-address information is access significant information which is transported transparent through the network in the access transport parameter in the initial address message (IAM). + +#### 8.2.2 *Specific terminology* + +None. + +#### 8.2.3 *Qualification on the applicability to telecommunication services* + +This supplementary service is applicable to all telecommunication services. + +#### 8.2.4 *State definitions* + +No specific state definitions are required. + +### 8.3 *Operational requirements* + +#### 8.3.1 *Provision/withdrawal* + +Not applicable. + +#### 8.3.2 *Requirements on the originating network side* + +Not applicable. + +#### 8.3.3 *Requirements in the network* + +No specific requirements are needed in the network. + +#### 8.3.4 *Requirements on the terminating network side* + +Not applicable. + +### 8.4 *Coding requirements* + +The sub-address is an information element in the access transport parameter. The coding of the information element is according to Recommendation Q.931, § 4.5.9. + +The maximum length of the sub-address information element is 23 octets, allowing for the transport of 20 octets sub-address information. + +### 8.5 *Signalling requirements* + +#### 8.5.1 *Activation/deactivation/registration* + +Not applicable. + +#### 8.5.2 *Invocation and operation* + +##### 8.5.2.1 *Actions at the originating local exchange* + +###### 8.5.2.1.1 *Normal operations* + +The basic call control procedures as described in Recommendation Q.764 are applicable. + +The sub-address information is transported in the access transport parameter of the initial address message (even in the case when the overlap sending procedure is used). + +###### 8.5.2.1.2 *Exceptional procedures* + +No exceptional procedures are identified. + +##### 8.5.2.2 *Actions at the transit exchange* + +###### 8.5.2.2.1 *Normal operation* + +The sub-address information contained in the access transport parameter, is passed on transparently to the succeeding exchange. + +###### 8.5.2.2.2 *Exceptional procedures* + +No exceptional procedures are identified. + +##### 8.5.2.3 *Actions at the outgoing international gateway exchange* + +###### 8.5.2.3.1 *Normal operation* + +The sub-address information contained in the access transport parameter, is passed on transparently in the international network. + +###### 8.5.2.3.2 *Exceptional procedures* + +No exceptional procedures are identified. + +##### 8.5.2.4 *Actions at the incoming international gateway exchange* + +###### 8.5.2.4.1 *Normal operation* + +The sub-address information, contained in the access transport parameter, is passed on transparently in the national network. + +###### 8.5.2.4.2 *Exceptional procedures* + +No exceptional procedures are identified. + +##### 8.5.2.5 *Actions at the destination local exchange* + +###### 8.5.2.5.1 *Normal operation* + +The sub-address information is passed on to the user network interface. + +###### 8.5.2.5.2 *Exceptional procedures* + +No exceptional procedures are identified. + +- 8.6 *Interaction with other supplementary services* +- 8.6.1 *Call Waiting (CW)* +No impact on ISUP. +- 8.6.2 *Call Transfer (CT)* +No applicable interaction at this time. +- 8.6.3 *Connected Line Identification Presentation (COLP)* +No impact on ISUP. +- 8.6.4 *Connected Line Identification Restriction (COLR)* +No impact on ISUP. +- 8.6.5 *Calling Line Identification Presentation (CLIP)* +No impact on ISUP. +- 8.6.6 *Calling Line Identification Restriction (CLIR)* +No impact on ISUP. +- 8.6.7 *Closed User Group (CUG)* +No impact on ISUP. +- 8.6.8 *Conference Calling (CONF)* +No impact on ISUP. +- 8.6.9 *Direct-Dialling-In (DDI)* +No impact on ISUP. +- 8.6.10 *Call diversion services (CDIV)* +- 8.6.10.1 *Call Forwarding Busy (CFB)* +No impact on ISUP. +- 8.6.10.2 *Call Forwarding No Reply (CFNR)* +No impact on ISUP. +- 8.6.10.3 *Call Forwarding Unconditional (CFU)* +No impact on ISUP. +- 8.6.10.4 *Call Deflection (CD)* +No impact on ISUP. +- 8.6.11 *Line Hunting (LH)* +No impact on ISUP. +- 8.6.12 *Three-Party-Service (3PTY)* +No impact on ISUP. +- 8.6.13 *User-to-User Signalling (UUS)* +- 8.6.13.1 *User-to-User Signalling, service 1 (UUS1)* +No impact on ISUP. + +##### 8.6.13.2 *User-to-User Signalling, service 2 (UUS2)* + +No impact on ISUP. + +##### 8.6.13.3 *User to User Signalling, service 3 (UUS3)* + +No impact on ISUP. + +#### 8.6.14 *Multiple Subscriber Number (MSN)* + +No impact on ISUP. + +#### 8.6.15 *Call Hold (CH)* + +No impact on ISUP. + +#### 8.6.16 *Advice of Charge (AOC)* + +No applicable interaction at this time. + +#### 8.6.17 *Sub-addressing (SUB)* + +Not applicable. + +#### 8.6.18 *Terminal Portability (TP)* + +No impact on ISUP. + +#### 8.6.19 *Completion of Call to Busy Subscriber (CCBS)* + +No applicable interaction at this time. + +#### 8.6.20 *Malicious Call Identification (MCID)* + +No impact on ISUP. + +#### 8.6.21 *Reverse Charging (REV)* + +No impact on ISUP. + +#### 8.6.22 *Multi-Level Precedence and Pre-emption (MLPP)* + +No impact on ISUP. + +#### 8.6.23 *Private Numbering Plan (PNP)* + +No applicable interaction at this time. + +#### 8.6.24 *Charge Card* + +No applicable interaction at this time. + +### 8.7 *Interaction with other networks* + +In the case of interaction with a network which does not support the Sub-address supplementary service or which cannot support the sub-address length supplied, the network shall discard the sub-address information and continue the call establishment procedures without notification to the originating exchange. + +### 8.8 *Signalling flows* + +The signalling flows of the basic call procedures are applicable. + +### 8.9 *Parameter values (timers)* + +No specific timers are required. + +### 8.10 *Dynamic description* + +The specification and description languages (SDLs) of the basic call procedures are applicable as described in Recommendation Q.764. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/0019f09403376d6444ee323591fa2e98_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/0019f09403376d6444ee323591fa2e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d632df5d3937de3a6abf3d266ee7d0c4df05e37 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/0019f09403376d6444ee323591fa2e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e04f625aceebe071fee49b2b34adeac9cb8ae91a17552273ade584b6ae00028 +size 50069 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aed073627c184d837b6fc347ff3d01be0ac037a3 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbb85154bf2305992718c42401293e99cbe4e9e37ad8434fab56f092a8dbe4c5 +size 63262 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..129e1ece44b43392e4d324b0669e852a13d1f68e --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e99309a61148567f49b287c83a59313286493a55906beeef9ae111896560092e +size 8225 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67d822be1c61c2d7c215a6eb80c9136c780f2f1e --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcfc84ee87ec8b7b7fbea2a75e10a67d83c1d5b46ee4b965e713d2ad0505169d +size 73550 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2cd1f55be8d7de6c9f06361be06563c65c2e098 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2cf6987902ac380537258a5b2dc7a9049bda93e923d52836b8a9fd61fd0ebd1 +size 60157 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..598eff1b7e79799b5bfb206ccf039d0890417a8a --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:359264fa26870eef5778b322ef2a8054df99c4f10d61bd13b2341aa4fbe3f26d +size 61258 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1c3cccb4de42aed4ff08744f09ba38944b58f7e --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed2d502e53fdfdbde351aa9458ccf942317cd8222d15f2d6f18662081520c543 +size 53886 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc569192875a2ef82c62db76dba9f6b2285554d7 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c52c2f255215f254d720a71d83f33ab5fc13f039f2e0aecc58ee3ff013a9d356 +size 69346 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..314ee46184f857f600fbfa1291f63940917c00bc --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50c37e7ceb3e3a63bf6d69919ecf8b9fa7f69988f49bc32a41ef3aa5fc5943d8 +size 52104 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0e00a83ef1f1fe7fba6551d8f27575ad1868744 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbb6e56616d16321c4ec489ec98dbc0026d707d3fcb3aec45d2f8dc52c796e5e +size 62395 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cc86e15f1702b6e4b0c0df7f1d2faf1fe34d381 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7dfbba77a87f13d0b44ddad99aface00c2180f25c4ce45d90079f21aa2fa6ff +size 56636 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64e65fa20151b3a0d0ae43f7cbf8df24539f4157 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae51ae8b3e37cf1e26b29354c949b2d9084cfca09a8ea1d159986bc53efef5ea +size 67514 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c82594d5070f5d58b1c955bcdf03d2521f95abe8 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb3ed7970ddb87a93b34076c03bd145cc01e8b52a20e46a1adacadabdfc925f7 +size 52993 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e93388b3fffde4d9d06273afa56699ca4efff1e --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76796ba02a850cc7e1cebf0c33a301d124a4ecedea2697d122621d5a37340915 +size 77121 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c59613c6f93cad07f643ab8520dba9eea185b9d6 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1af61837fac75f4c371a44df13b3b354056a362763ecdb435a961ab309f63ff1 +size 66626 diff --git a/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5e4b6cde25418efa10e6804ef1905e42d5660c3 --- /dev/null +++ b/marked/Q/T-REC-Q.734.1-199303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb81adc02a9b6e4c990811da2046b697dcd6a596fa5b4a3a99a4103f18b21ffe +size 70951 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54af6e7efd8f9cd7201a606acbfae553d48644c0 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5e44e1a9560ffef5f4dc4fa06e130f033eeaf1530c87311f0671a5bb4f5e976 +size 10540 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3e6de0720f76e1c9fd0cc7256bd11c0fdda4ff7 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7c969d4998184bf31d0091c9482369922d3b078ef99066241b0fd7d8a5b3951 +size 45688 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec9a633049e3ed34d4a24c815f43080980b2c4c3 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f30ca8a4730c7a78c831c9159f837096c6928679c1f23f80384e6a160a5fd4d6 +size 47754 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/Q/T-REC-Q.750-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.750-199706-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..deb607950df111a298e6e6c9195bfc2bfd59a275 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63d9d4fd7f3d4d7b4284eec670e12b9979ffa927505df26a398c648ae6aa9e8a +size 27322 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cd2200085da16d6c57e80d0e05187ffafa287a1 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0ba8bbd4a92914e2dd7a47b464b92b7fd18d2bb73ef7af048d9b612686fe81 +size 47578 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea060c5f55513357e52f584957a6b2250746a07e --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99296325e68d7aed14975642cd8bf77583fcd70892387416552097006ac87c96 +size 112375 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..507fe43de8e92dceb98295fc1723ac7afff04dfb --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbe82a91763ec652026a04a661629de08d8e49e6dc59f65a472ec9d9eded4ad4 +size 103292 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b287d42a26179d14047820e6af9f6303aa3ef205 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d21c2ea98fa55c2bcb91bd638e9104b5bc197df7bd20b2c101e6ebba5ce089c +size 17039 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b71038bdbcd3e98228b33cabc2abfe6dced0e2fd --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bef9b38ae2944136ade744f7a0e063d7cf5dedd0bd80693438f882783cd9410d +size 107275 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f07e7df2a05ea6b7596e8b25114fcfbceaf36729 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39f60a9354eb9952639e3809c13e9ca6d933bfb0e1277b149e6161dd8f70e335 +size 20172 diff --git a/marked/Q/T-REC-Q.750-199706-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.750-199706-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3b18dff1d4b4e36b6a53172ac4336e46a622857 --- /dev/null +++ b/marked/Q/T-REC-Q.750-199706-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4437f96370345c48db92377358e052bc040771695d0f8a077e5d09d3b8e3fb9 +size 75857 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c1dfa8ee22ad063471e82648f8515dd37ce784d --- /dev/null +++ b/marked/Q/T-REC-Q.751.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.751.2-199706-I_PDF-E/31b824cd2882d0c2f82022527d58ec28_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/31b824cd2882d0c2f82022527d58ec28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c6b55962e2ac54027900b409dda81b88732072c --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/31b824cd2882d0c2f82022527d58ec28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82084fba4b2be174d686eadba21043655ab24154d1aef361aa1b3885f5edc02d +size 262317 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42d546ecde385eb8beff787058943e3eb3cf2f96 --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a47bd36a3c26d75f1b091445fa8a36f519fc2801c57ec4fc4fb1e6b23bdf4d18 +size 71147 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0564a5cf08bc561095280bb6d9fb713c7c5b2a8c --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7abf100616851c5a25aa5890b5ef6461e0363e5bb2db2c8f808d67602007b4c7 +size 291017 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2eade426f56bc8c13751f014ebeebacc53a071 --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1b0eda0d8fadd219f6501d22676279c0214f81c88111d5c543d627977c1f713 +size 12701 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02cbc0a1f747c9c235ff0c66570bdca23d89d488 --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:333fa8713cfa404a48004d0b6822b6d7521b5d430fab3c6a8303bc067ff77e70 +size 224106 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c878d049578170571ccc7e42c068bd9fb6ec2f00 --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c48e44f4de801f9aeb957931d81013b42243cbee0356a9c68ab50939e29983e0 +size 6578 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fac26bd2dc9cd0ada482e886204c740d443efae --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:633cb808b11e9b41a5e9ea6d6d8853752176fa1fd2bb4e839a582348e0170bce +size 39346 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e192d3f7108c8c56cb53683e775674ab90e97268 --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1d5eff05c85ddb51659d6f03ae36d0a3459a75733f18572d0472f02606d5c5e +size 8856 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/eae05333c9188c830bd0ebe58c50453a_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/eae05333c9188c830bd0ebe58c50453a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f75919a910f0e5357c7ab56356c7157331e1bd3 --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/eae05333c9188c830bd0ebe58c50453a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89076157d5e253a23283741db94eb4b839ea7734e2b2544756af9cf74b1d97d3 +size 16716 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd1d5844a84a0761f4ec4e137184b801f168c4cf --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/f796c4b6ef101faa39b887a86820c3d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:419b54a32192920a9825201ba07513d9b5b359b313e58f40a09d055c9d8d3137 +size 19745 diff --git a/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbb713256d0cc562ecd50aaeb5b62471f4de7c52 --- /dev/null +++ b/marked/Q/T-REC-Q.751.2-199706-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a839ce7538fd23093aff36b9b7974ee35d6a3257d06c4e771831d64447a0909 +size 220644 diff --git a/marked/Q/T-REC-Q.755-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.755-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e0d2b869b39a1de23c45cd44a71a34c53b67e3c8 --- /dev/null +++ b/marked/Q/T-REC-Q.755-199303-I_PDF-E/raw.md @@ -0,0 +1,428 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.755** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +**SPECIFICATIONS OF SIGNALLING SYSTEMS No. 7 +SIGNALLING SYSTEM No. 7 MANAGEMENT** + +--- + +**SIGNALLING SYSTEM No. 7 +PROTOCOL TESTS** + +**ITU-T Recommendation Q.755** + +(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.755 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. + +# CONTENTS + +| | Page | +|------------------------------------------------------------------|-------------| +| 1 Introduction ..... | 1 | +| 2 MTP tester (MT) ..... | 1 | +| 2.1 Functions ..... | 1 | +| 2.1.1 Objectives and scope..... | 1 | +| 2.1.2 Main functions ..... | 3 | +| 2.1.3 Architectural model..... | 3 | +| 2.1.4 Implementation ..... | 3 | +| 2.1.5 Traffic modes ..... | 3 | +| 2.1.6 Functional blocks ..... | 3 | +| 2.1.7 Identification of test sequences ..... | 4 | +| 2.1.8 Message rate considerations..... | 4 | +| 2.2 Procedures ..... | 4 | +| 2.2.1 Test set-up ..... | 4 | +| 2.2.2 Test duration ..... | 5 | +| 2.2.3 Termination..... | 5 | +| 2.2.4 Reaction to MTP management primitives and MTP restart..... | 6 | +| 2.3 Formats and codes ..... | 7 | +| 2.3.1 SIO ..... | 7 | +| 2.3.2 Label ..... | 7 | +| 2.3.3 Header codes..... | 7 | +| 2.3.4 Timers ..... | 9 | +| 2.3.5 Interface requirements..... | 9 | +| 3 SCCP tester (ST) ..... | 10 | +| 4 References ..... | 10 | + + + +# SIGNALLING SYSTEMS No. 7 PROTOCOL TESTS + +(Helsinki, 1993) + +# 1 Introduction + +The protocol testers may be used as an aid when testing the Message Transfer Part (MTP) and the Signalling Connection Control Part (SCCP) of Signalling System No. 7 (SS No. 7), either when performing validation testing of an implementation or compatibility testing between two implementations. The tester's main function is simulation of an ordinary user part or sub-system, as seen from the MTP or SCCP respectively, for the generation of test traffic. + +Recommendations I.320 and I.321 specify the ISDN protocol reference model to be used for N-ISDN and B-ISDN. User plane (U-plane), Control plane (C-plane) and Management plane (M-plane) are identified. The layering principles apply in each of these planes. The U-plane provides the user information flow transfer with associated controls. The C-plane handles the call and connection control information. The M-plane is divided into two portions, the Layer Management functions and the Plane Management functions. The Plane Management performs management functions related to a system as a whole, it provides coordination between all the planes and has no layered structure. The Layer Management plane contains Layer Management Entities (LME). Each of them provides management functions relating to resources and parameters residing in its own protocol entity. Layer Management handles the operation and maintenance information flows. The interface between adjacent layers within a plane and between LME and its associated layer have to be defined in terms of service primitives. The interface between the LMEs and Plane Management has not to be specified, it is implementation dependent. + +Thus the MT is contained in the LME of the MTP-3 (MTP-3 LME) and the ST is within the LME of the SCCP (SCCP LME). The service primitives between MTP-3 LME and the MTP-3, and between SCCP LME and the SCCP is described, as well as the procedures, the messages and the MT and ST substructures. The undefined primitives between the Plane Management (MIB) and the MT and ST are only required to activate/deactivate the concerned testing functions (see Figure 1). + +# 2 MTP tester (MT) + +The MT is connected to the MTP as a user part, i.e. identified by a service indicator. It generates Message Signal Units (MSUs) containing a serial number (and possibly additional information) in the Signalling Information Field (SIF). On reception of these messages a check is performed to verify that the messages are delivered according to the defined performance criteria for the MTP. + +## 2.1 Functions + +### 2.1.1 Objectives and scope + +The MT is: + +- a possible tool for validation testing when traffic generation is needed whilst performing tests. However, other traffic generators may be used and not all test cases may be covered with the MT when performing validation tests; +- the preferred traffic generator for compatibility tests between different network operators. However, other traffic generators may be used for compatibility testing between different versions of the same system inside one national network; +- a useful possible tool when performing network performance verification tests for SS No. 7 networks which are in service. If international network performance verification should be needed, it would be the preferred traffic generator. + +![Diagram of SS No. 7 management and internal configuration of an SP. It shows various components like Part of OMAP, e.g. MAP, Call Control application services, ISDN UP, TUP, SCCP (Level 4), and MTP (Levels 1-3) connected via LMI and AMI interfaces. A vertical MIB is on the left. Connections are marked with 'x' and 'y'. A note at the bottom right indicates this is for communication between SS No. 7 nodes.](547f726730e589392f239257a833ede3_img.jpg) + +The diagram illustrates the internal configuration and management of a Signaling Point (SP) for SS No. 7. On the left, a vertical 'MIB' (Management Information Base) is shown. To its right, several functional blocks are stacked vertically, connected by a common horizontal bus structure. At the top, 'Part of OMAP' is connected to an 'AE' (Application Entity) containing 'LME', 'OMASE', and 'TCASE'. This AE is linked via 'SMSI' and 'OM-prim' to 'e.g. MAP' and 'Call Control application services'. The 'Call Control application services' block contains 'ISDN UP' and 'TUP', each with its own 'LME'. Below the top AE, there are two dashed boxes labeled '(Note 6)'. A connection point 'x' leads to the 'SCCP (Level 4)' block, which includes an 'ST' (Signaling Transfer) and 'LME'. Another connection point 'y' leads to the 'MTP (Levels 1-3)' block, which includes an 'MT' (Message Transfer) and 'LME'. Dashed lines labeled 'LMI' (Link Management Interface) connect the MIB and various LMEs. Dashed lines labeled 'AMI' (Alarm Management Interface) connect the top blocks. At the bottom right, a note states 'For communication between SS No. 7 nodes' with the reference 'T1143300-92/d01'. + +Diagram of SS No. 7 management and internal configuration of an SP. It shows various components like Part of OMAP, e.g. MAP, Call Control application services, ISDN UP, TUP, SCCP (Level 4), and MTP (Levels 1-3) connected via LMI and AMI interfaces. A vertical MIB is on the left. Connections are marked with 'x' and 'y'. A note at the bottom right indicates this is for communication between SS No. 7 nodes. + +FIGURE 1/Q.755 +**SS No. 7 management and internal configuration of an SP** + +![Architectural model diagram showing a hierarchy of functional blocks. At the top is a box labeled 'TEST control'. Below it are three boxes: 'Message generator', 'Message verification', and 'Turnaround function'. Below these three boxes is a box labeled 'MTP specific portion'. All four boxes are contained within a larger rectangular frame. Below this frame is a separate box labeled 'MTP'.](fc46871d72c65d3381d9201646d23439_img.jpg) + +``` + +graph TD + subgraph TopFrame [ ] + TC[TEST control] + MG[Message generator] + MV[Message verification] + TF[Turnaround function] + MSP[MTP specific portion] + end + TopFrame --- MTP[MTP] + style TopFrame fill:none,stroke:none + style MTP fill:none,stroke:none + +``` + +Architectural model diagram showing a hierarchy of functional blocks. At the top is a box labeled 'TEST control'. Below it are three boxes: 'Message generator', 'Message verification', and 'Turnaround function'. Below these three boxes is a box labeled 'MTP specific portion'. All four boxes are contained within a larger rectangular frame. Below this frame is a separate box labeled 'MTP'. + +T1136720-91/d02 + +### 2.1.2 Main functions + +The main function is the generation of bidirectional test traffic, giving the possibility at the receiving node of analysing the received test traffic (e.g. detection of missequencing, duplication or loss of messages, verification of transfer delays ...). Errors may be introduced in the SS No. 7 network (by external means to the testers) during the transmission of test traffic. + +### 2.1.3 Architectural model + +The architectural model is as given in Figure 1. + +All procedures are located in the Layer Management Entity (LME), all other functions are located within the Management Information Base (MIB) and the Management Process (MP). + +### 2.1.4 Implementation + +Only one implementation mode is to be described, and this will perform message generation, “turn around”, verification and termination. + +### 2.1.5 Traffic modes + +There will be only one traffic mode, the “turn around” mode. However, the tester performing the “turn around” function will fulfil basic message verification such as sequence checking and message counting. + +### 2.1.6 Functional blocks + +Whilst keeping the single implementation mode, there are two functional roles which are identified during a test; the tester generating the traffic and the tester turning around the test messages. It is perfectly possible for a tester to be generating traffic towards one signalling point whilst performing the “turn around” role in another test to a different signalling point. + +#### 2.1.6.1 Generator + +The Generator role uses the services of various blocks within the MT. The test control function will confirm that the remote end is ready and able to start a test, then control the duration and termination of the test. The message generation function will then generate the appropriate traffic messages at the rate requested in the test set-up. The generator will also control the message lengths. The message verification function receives the messages returning from the turn around end and checks them for corruption, loss, missequencing and duplication. The MTP specific portion deals with generating the MTP transfer primitives and handling the incoming MTP primitives. The OMAP interface handles test requests from TMN, test supervision and control and the presentation and interpretation of test results. + +#### **2.1.6.2 Turn around** + +The turn around role uses the test control function to control the acceptance and supervision of a test. Test traffic arriving from the generator is checked by the message verification block, before being returned to the generator via the turn around function. The MTP specific portion again deals with the sending and receiving of MTP primitives. The OMAP interface deals with test acceptance, test control and the presentation and interpretation of results. + +### **2.1.7 Identification of test sequences** + +A particular test sequence is identified by the point codes and network indicators of the two testers involved. Thus it is only possible to have one test at a time running between two point codes. The GPC, the point code of the generating tester is included as an additional security feature. + +### **2.1.8 Message rate considerations** + +To secure delivery in sequence via MTP all test traffic messages use the identical code within the SLS-field. Thus they will use only one link of every linkset passed. This should be considered when defining the actual message rate. Using the same SLS-code after turn-around may or may not define the same links in the backward direction as in the forward direction as the load-sharing key is implementation dependent. + +## **2.2 Procedures** + +### **2.2.1 Test set-up** + +There are three possible phases during test set-up: test request, test acceptance and test refusal. + +#### **2.2.1.1 Test request** + +Once a test request has been received by the tester from OMAP a check will be made to ensure that no test already exists for the requested point code (turn around point code TPC). If a clash is detected an error is returned to OMAP with an appropriate reason, the test already in place will not be affected. If a valid request is received then the necessary counters are initialized, and a guard timer is started to control test set-up T1. A test request message is then sent to the TPC. The information provided by the OMAP will include an indication of the required response to the receipt of an MTP status with cause network congestion. The conditions applying to the setting of this indication are to be defined within Recommendation Q.751. The default action is to stop the test. It may be specifically requested by OMAP to report congestion indications, but continue the test. The indication is passed in the test request message and must be accepted by the turn around tester. + +NOTE – This procedure should only be used with extreme caution. + +#### **2.2.1.2 Test acceptance** + +##### **2.2.1.2.1 By the turn around tester** + +On reception of a test request message a check is performed to ensure that a test with the originating tester is not already in progress. If a test is found to be in progress then a test termination request message is sent, a report is made to OMAP and the original test is terminated. + +If no test is found to be in progress then the turn around tester will request from OMAP to start a test from the respective point code. On receiving a negative response from OMAP (e.g. due to local conditions), a test refusal message is sent. A positive response will initiate the sending of a test acceptance message and the initialization of the necessary counters. OMAP also specifies criteria for test termination. See 2.2.2.1 apart from a). + +##### **2.2.1.2.2 By the generator** + +The reception of a test acceptance message by the generator will cause the termination of the set-up timer T1. The OMAP will be informed that a test is in progress, the generation of test traffic will begin. + +#### **2.2.1.3 Test refusal** + +If a test refusal message is received then the set-up timer T1 is terminated, any counters initialized will be cleared and a report is made to OMAP. + +#### **2.2.1.4 Timer T1 Expiry** + +If timer T1 expires then any counters initialized will be cleared and a report is made to OMAP. It is assumed that the test request was lost and any subsequent test acceptance or refusal messages will be dealt with as an unexpected message. + +### **2.2.2 Test duration** + +#### **2.2.2.1 At the generator** + +On receipt of a test acceptance message the test duration timer T2 is started, the messages are generated according to the rate information supplied by OMAP. As each message is sent, the Messages Sent count is incremented. The value of this count is given as the serial number field within the test traffic message. The need for a supervision timer for each message is implementation dependent. The generating tester may place further information (e.g. a time stamp) in the additional data field of the test traffic message, this is not looked at by the turn around tester, however the additional data field should contain sufficient filler octets (coded all zeros) to give an overall message length as requested during test set-up by OMAP. + +When test traffic messages are received at the generator, the messages are checked by comparing the Generating Point Code field (GPC) with the tester's own point code. As messages are terminated at the MT the messages received counter is incremented, and the message serial number is checked as a means of sequence validation. Any further checking may be done using the information in the additional octets field. + +#### **2.2.2.2 At the turn around tester** + +Incoming messages are checked as in the generating tester. If the GPC is not the tester's own point code, and a current test to the relevant point code is in existence, then the messages are turned around. The messages received counter is incremented and the serial number checked for missequencing. The OPC and DPC of the MTP transfer indication are then swapped and the message formed into an MTP transfer request. + +#### **2.2.2.3 Response to missequencing** + +If on checking the message serial number an error in sequence is detected then a report is made to OMAP which includes the message serial number and any additional filler octets. However, to stop a message loss causing all remaining messages to be seen as missequenced the message counter must be reset to the serial number of the message detected as missequenced. + +### **2.2.3 Termination** + +#### **2.2.3.1 By the generator** + +The test ends by either: + +- a) expiry of T2 (where the value of T2 was specified during test set-up by OMAP); or +- b) congestion indication if OMAP has not specifically instructed it to be ignored; or +- c) specific request from OMAP. + +The test termination procedure involves the sending of a test termination request message and the starting of a test termination timer T3. + +On receipt of a test termination acknowledgment message the test results and reason for test end are sent to OMAP and the counters are cleared. If timer T3 expires then the local OMAP is informed. + +If a test termination request message is received then a test termination acknowledgement message is sent, the test results and reason for end are sent to OMAP and the counters are cleared. + +#### **2.2.3.2 By the turn around tester** + +The procedure for terminating a test by the turn-around tester is the same as at the generator, except that T2 expiry is not possible. After sending a test termination request the turn-around tester continues its turn-around function until it either receives a test termination acknowledgement or T3 expires. If T3 expires, the local OMAP is informed. + +#### **2.2.3.3 Test termination acknowledgement** + +Upon receipt of a test termination request, the local test is stopped and a test termination acknowledgement is sent. + +### **2.2.4 Reaction to MTP management primitives and MTP restart** + +#### **2.2.4.1 MTP pause** + +If the affected point code is currently performing the generator function in one of the current tests then the test is paused, no more messages are generated and the timers and counts are held. If a local request to terminate the test whilst in this held state is received then a notification of the inability to terminate the test is returned to OMAP and the test termination procedure is started, however the test termination procedure will be held until the remote end becomes available (i.e. receipt of an MTP resume or an MT message from the unavailable tester). + +If the MTP pause is received by a tester performing the turn-around function for the affected point code then no action is necessary, except where the local OMAP requests to terminate the test. In this case OMAP is again informed, the test termination procedure remains started but held until the remote end becomes available. + +#### **2.2.4.2 MTP resume** + +If a local test termination request has been received for the affected point code during the period the remote tester was unavailable, then an MTP resume will release the test termination procedure. + +If there is a held test to the affected point code (i.e. the affected point code is the TPC) then the test will resume. + +Otherwise the MTP resume is ignored. + +#### **2.2.4.3 MTP status** + +The MTP status primitive contains two parameters, the affected point code and a cause. + +The cause may be: + +- signalling network congestion (a national option allows a level to be included); +- remote user unavailable; +- remote user unequipped. + +On receiving remote user unavailable or remote user unequipped for a point code currently in use by the tester, the MT will stop sending messages to the destination, and inform OMAP. The normal test termination procedure will not take place. + +- Signalling network congestion indication. + +If an MTP status is received with cause network congestion, for a point code currently involved in a test, then the congestion response indication provided by OMAP will determine the tester's response to this indication. The default action is to stop the test and report to OMAP. If the test request specified "report congestion indication but continue test", the tester will report congestion indication to OMAP, but continue the test. + +#### **2.2.4.4 MTP restart** + +If the tester detects a local MTP restart, then the test termination procedure is started for all current tests, but held until the restart is finished. + +NOTE – Where the termination procedure is held the timer T3 is also held. + +## 2.3 Formats and codes + +### 2.3.1 SIO + +The service information octet is made up of the service indicator and the sub-service field (see Figure 2). + +| | | +|-------------------|-------------------| +| DCBA | 1000 | +| Sub-service field | Service indicator | + +FIGURE 2/Q.755 + +The following codes are used in the field of the service information octet. + +- a) The service indicator is coded 1000. +- b) Sub-service field: + - bits BA Spare + - bits DC + - 00 International network + - 01 Spare (for international use only) + - 10 National network + - 11 Reserved for national use + +### 2.3.2 Label + +The label has a length of 32 bits and is placed at the beginning of the signalling information field. + +The label structure is shown in Figure 3 + +| | | | +|-----|-----|-----| +| SLS | OPC | DPC | +| 4 | 14 | 14 | + +OPC Originating Point Code +DPC Destination Point Code +SLS Signalling Link Selection Field + +FIGURE 3/Q.755 + +#### Label structure + +### 2.3.3 Header codes + +The first header code is the H0 header code; this is a four bit field that follows the label and identifies the message group. The H1 header code field occupies the next four bits and indicates the actual message within each group. The H0 field is coded as follows: + +- 0000 Test control messages +- 0001 Test traffic messages +- 0010-1111 Spare + +#### 2.3.3.1 Test control + +The H0 = 0000 group represents the test control messages. For this group the H1 codes are as follows: + +| | | +|-----------|--------------------------------------| +| 0000 | Test request message | +| 0001 | Test acceptance message | +| 0010 | Test refusal message | +| 0011 | Test termination request message | +| 0100 | Test termination acknowledge message | +| 0101-1111 | Spare | + +The test control messages are formatted as follows (see Figure 4). + +| BA | | DCBA | 0000 | | +|-----------|-----|------|------|-------| +| Indicator | GPC | H1 | H0 | Label | +| 2 | 14 | 4 | 4 | 32 | + +GPC The point code of the tester initiating the test and generating the traffic + +FIGURE 4/Q.755 +**Test control messages** + +The test request message additionally uses the indicator field; this is coded as follows: + +| | | +|-------|-----------------------------------------------| +| BA | | +| 00 | Stop test on congestion indication | +| 01 | Report and then ignore congestion indications | +| 10-11 | Spare | + +#### 2.3.3.2 Test traffic + +The H0 = 0001 group represents the test traffic messages, for this group the H1 codes are as follows: + +| | | +|-----------|----------------------| +| 0000 | Test traffic message | +| 0001-1111 | Spare | + +The test traffic messages are formatted as follows (see Figure 5). + +| | | | | | | | +|---------------------|---------------|-------|-----|------|------|-------| +| | | BA | | 0000 | 0001 | | +| Filler Octets | Serial Number | Spare | GPC | H1 | H0 | Label | +| $m * 8$ | 32 | 2 | 14 | 4 | 4 | 32 | +| $0 \leq m \leq 261$ | | | | | | | + +GPC The point code of the tester initiating the test and generating the traffic +Serial number The serial number assigned to the message +Filler octets Additional octets of information i.e. a time stamp + +FIGURE 5/Q.755 +**Test traffic messages** + +### 2.3.4 Timers + +- T1 3-5 sec This timer controls the setting up of a test. +- T2 10-500 000 sec (provisional) This timer measures the duration of the test. +- T3 5-10 sec This timer governs the frequency at which test termination request messages are sent. + +### 2.3.5 Interface requirements + +The description of the interface between the MT and OMAP is outlined in Table 1. + +There will be additional notifications from the tester to OMAP; these contain the appropriate information. Table 1 is only a guide as this interface is not for specification, (see Recommendation Q.751). + +TABLE 1/Q.755 + +| | | | +|------------------------------|---------|---------------------------------------------------------------------------------------| +| Test request | OMAP-MT | DPC, NI, SLS, message lengths, test duration.
Message rate and congestion response | +| | MT-OMAP | OPC, NI, SLS, message lengths, test duration.
Message rate and congestion response | +| Test acceptance | OMAP-MT | DPC, NI | +| | MT-OMAP | OPC, NI | +| Test refusal | OMAP-MT | DPC, NI | +| | MT-OMAP | OPC, NI | +| Test termination request | OMAP-MT | DPC, NI | +| Test termination acknowledge | MT-OMAP | OPC, NI, Test results and reason for end | + +# **3 SCCP tester (ST)** + +For further study. + +# **4 References** + +CCITT Recommendation *ISDN protocol reference model*, Rec. I.320 + +CCITT Recommendation *B-ISDN protocol reference model and its application*, Rec. I.321 \ No newline at end of file diff --git a/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.765bis-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.765bis-199912-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ca20a9b54ab374168a12a20d086c4c747f1905c --- /dev/null +++ b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92b6795e70862810c5ea03beb7cc0ffaa771d93e718cd640a23e1a86c31475e1 +size 35418 diff --git a/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..142fec6793ac24d58217e587e746cf772500d69e --- /dev/null +++ b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:695ec3bb81cbf1bfddb22a05709bae9b7e8fca2231c48de9e3d72fe0a1570c9a +size 32463 diff --git a/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b06af8762257f5d5a01808620969c39f89ea50ec --- /dev/null +++ b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb6459e95b883520643794c38eedfd8a0310952d14c001c92e4ecd1e0fb1281e +size 32420 diff --git a/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9119c377b72a42470aed5446724ca59aa83f1828 --- /dev/null +++ b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e91f639946bc407dea1c7992a140d992e5d5b4d5bb1977d79b2a7fe2dfe301cb +size 26766 diff --git a/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a05c3a75bebd715dee931f5017ec8f89d89e4be2 --- /dev/null +++ b/marked/Q/T-REC-Q.765bis-199912-I_PDF-E/raw.md @@ -0,0 +1,935 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.765 *bis*** + +(12/99) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – ISDN user part + +--- + +**Signalling System No. 7 – Application Transport +Mechanism: Test Suite Structure and Test +Purposes (TSS & TP)** + +ITU-T Recommendation Q.765 *bis* + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.709 | +| Signalling connection control part (SCCP) | Q.711–Q.719 | +| Telephone user part (TUP) | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +## **SIGNALLING SYSTEM No. 7 – APPLICATION TRANSPORT MECHANISM: TEST SUITE STRUCTURE AND TEST PURPOSES (TSS & TP)** + +## **Summary** + +This Recommendation contains the conformance test specification for ISUP'97 application transport mechanism. The main body of this Recommendation presents the requirements regarding the chosen test method, the test suite structure and the test purposes. + +### **Source** + +ITU-T Recommendation Q.765 *bis* was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 3 December 1999. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2000 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU, except as noted in footnote 1 in Annex A. + +## CONTENTS + +| | | Page | +|---------|--------------------------------------------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Implementation under test and test methods..... | 4 | +| 5.1 | Identification of the system and implementation under test ..... | 4 | +| 5.2 | ATM and testing configuration for ISUP'97 – Application Transport Mechanism.... | 5 | +| 5.3 | Local exchanges – PIN/PAN ..... | 5 | +| 5.4 | Transit exchanges – PIN/PAN ..... | 6 | +| 5.5 | Transit exchanges – ISUP ..... | 6 | +| 6 | Test Suite Structure (TSS) ..... | 8 | +| 7 | Test Purposes (TP)..... | 9 | +| 7.1 | Introduction..... | 9 | +| 7.2 | Test Purpose (TP) naming convention..... | 9 | +| 7.2.1 | Source of test purpose definition ..... | 9 | +| 7.2.2 | Test purpose structure..... | 9 | +| 7.3 | Test purposes for the Signalling System No. 7, Application Transport Mechanism (APM) ..... | 9 | +| 7.3.1 | Application Transport Mechanism (APM ASE) ..... | 10 | +| 7.3.2 | Unidentified Context and Error Handling (UCEH ASE) ..... | 17 | +| 8 | Test coverage ..... | 20 | +| 9 | Conformance to the PICS proforma specification ..... | 21 | +| Annex A | – PICS proforma for ISDN User Part 1997 (ISUP'97) – Signalling System No. 7, Application Transport Mechanism ..... | 21 | +| A.1 | Instructions for completing the PICS proforma..... | 21 | +| A.1.1 | Purposes and structure ..... | 22 | +| A.1.2 | Abbreviations and conventions ..... | 22 | +| A.2 | Identification of the implementation..... | 23 | +| A.2.1 | Date of the statement ..... | 23 | +| A.2.2 | Implementation Under Test (IUT) identification..... | 23 | +| A.2.3 | System Under Test (SUT) identification ..... | 23 | +| A.2.4 | Product supplier..... | 23 | +| A.2.5 | Client ..... | 24 | +| A.2.6 | ICS contact person..... | 24 | + +| | Page | +|--------------------------------------------------------|-------------| +| A.3 Identification of the reference specification..... | 24 | +| A.4 PICS proforma tables..... | 24 | +| A.4.1 Global statement of conformance..... | 24 | +| A.4.2 Roles ..... | 24 | +| A.4.3 Capabilities ..... | 25 | + +# **SIGNALLING SYSTEM No. 7 – APPLICATION TRANSPORT MECHANISM: TEST SUITE STRUCTURE AND TEST PURPOSES (TSS & TP)** + +*(Geneva, 1999)* + +# **1 Scope** + +This Recommendation contains the validation (conformance) test specification for the Application Transport Mechanism defined in Recommendation Q.765 [1]. This Recommendation applies only to exchanges having implemented the ISUP'97 protocol specification for the Application Transport Mechanism of the exchange. It is applicable for validation testing of all types of exchanges as defined in the ISUP'97 protocol specification. It does not deal with compatibility testing. + +The main body of this Recommendation presents the Test Suite Structure and Test Purposes (TSS & TP) for the Application Transport Mechanism (APM). + +Annex A provides the Protocol Implementation Conformance Statement (PICS) proforma for the Application Transport Mechanism defined in compliance with the relevant requirements and in accordance with the guidance given in ISO/IEC 9646-7 [8]. This statement indicates which capabilities and options of a telecommunication specification have been implemented. It is necessary for evaluating the conformance of a particular implementation. + +The supplier of an implementation that is claimed to comply with the reference specification for the Signalling System No. 7, Application Transport Mechanism [1], is required to complete a copy of the PICS proforma provided in Annex A. + +# **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.765 (1998), *Signalling System No. 7 – Application transport mechanism.* +- [2] ITU-T Recommendation Q.763 (1997), *Signalling System No. 7 – ISDN User Part formats and codes.* +- [3] ITU-T Recommendation Q.764 (1997), *Signalling System No. 7 – ISDN User Part signalling procedures.* +- [4] ISO/IEC 9646-1:1994, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 1: General concepts.* +- [5] ISO/IEC 9646-2:1994, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 2: Abstract Test Suite specification.* +- [6] ISO/IEC 9646-3:1998, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 3: The Tree and Tabular Combined Notation (TTCN).* + +- [7] ISO/IEC 9646-5:1994, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 5: Requirements on test laboratories and clients for the conformance assessment process.* +- [8] ISO/IEC 9646-7:1995, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 7: Implementation Conformance Statements.* +- [9] ITU-T Recommendation Q.784.1 (1996), *ISUP basic call test specification: Validation and compatibility for ISUP'92 and Q.767 protocols.* +- [10] CCITT Recommendation E.164 (1988), *Numbering plan for the ISDN era.* + +# 3 Definitions + +For the purposes of the ATS specification, the following definitions apply: + +- terms defined in ISDN User Part (ISUP) reference specification [1] to [3]; +- terms defined in ISO/IEC 9646-1 [4], ISO/IEC 9646-3 [6] and in ISO/IEC 9646-7 [8]. + +In particular, the following terms apply: + +**3.1 Abstract Test Case (ATC):** A complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and ending in a stable testing state (see [4], § 3.3.3). + +**3.2 Abstract Test Method (ATM):** The description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract test cases to be specified for this method (see [4], § 3.3.5). + +**3.3 Implementation Under Test (IUT):** An implementation of one or more OSI protocols in an adjacent user/provider relationship, being part of a real open system which is to be studied by testing (see [4], § 3.3.43). + +**3.4 ISDN number:** A number conforming to the numbering and structure specified in CCITT Recommendation E.164 [10]. + +**3.5 Means of Testing (MOT):** The combination of equipment and procedures that can perform the derivation, selection, parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a conformance log (see [4], § 3.3.54). + +**3.6 point of control and observation:** A point within a testing environment where the occurrence of test events is to be controlled and observed, as defined in an Abstract Test Method (see [4], § 3.3.64). + +**3.7 pre-test condition:** A setting or state in the IUT which cannot be achieved by providing stimulus from the test environment. + +**3.8 Protocol Implementation Conformance Statement (PICS):** A statement made by the supplier of a protocol claimed to conform to a given specification, stating which capabilities have been implemented (see [4], § 3.3.39 and § 3.3.80). + +**3.9 Protocol Implementation eXtra Information for Testing (PIXIT):** A statement made by a supplier or implementor of an IUT (protocol) which contains or references all of the information related to the IUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT (see [4], § 3.3.41 and § 3.3.81). + +**3.10 System Under Test (SUT):** The real open system in which the IUT resides (see [4], § 3.3.103). + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|----------|-----------------------------------------------------------| +| APM | Application Transport Mechanism | +| ASE | Application Service Entity | +| ASP | Abstract Service Primitive | +| ATM | Abstract Test Method | +| ATS | Abstract Test Suite | +| ICS | Implementation Conformance Statement | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | +| IUT | Implementation Under Test | +| LT | Lower Tester | +| MOT | Means Of Testing | +| MTC | Main Test Component | +| MTP | Message Transfer Part | +| PAN | Public Addressed Node | +| PCO | Point of Control and Observation | +| PICS | Protocol Implementation Conformance Statement | +| PIN | Public Initiating Node | +| PIXIT | Protocol Implementation eXtra Information for Testing | +| PSS1 | Private network Q reference point Signalling System No. 1 | +| PTC | Parallel Test Component | +| SP | Signalling Point | +| SUT | System Under Test | +| TCP | Test Coordination Procedures | +| TE_P | Transit Exchange PIN/PAN | +| TP | Test Purpose (context dependent) | +| TSS | Test Suite Structure | +| TSS & TP | Test Suite Structure and Test Purposes | +| TTCN | Tree and Tabular Combined Notation | +| UCEH | Unidentified Context and Error Handling | +| UT | Upper Tester | +| VPN | Virtual Private Network | + +The ISUP message acronyms can be found in Table 2/Q.762. The APM primitives acronyms can be found in the different tables of Q.765 [1]. The following abbreviations apply for ISUP parameters and parameter values: + +| | | +|------|---------------------------------------------| +| ACI | Application Context Identifier | +| APP | Application Transport Parameter | +| ATII | Application Transport Instruction Indicator | +| PRI | Pre-Release | +| SLR | Segmentation Local Reference | + +# 5 Implementation under test and test methods + +## 5.1 Identification of the system and implementation under test + +The System Under Test (SUT) is an exchange. The Implementation Under Test (IUT) is the ISUP'97 implementation in this exchange, mainly the part responsible for the Application Transport Mechanism (APM), as shown in Figure 1. + +![Diagram of the system under test (SUT) showing the hierarchy of protocols. The SUT (Exchange) contains the IUT, which contains APM_user, APM, and ISUP Basic Call ISUP'97. Arrows show the flow of information between these layers and external ISUP connections.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates the system under test (SUT) architecture. The SUT is represented by a large outer rectangle labeled 'Exchange' at the top and 'SUT' at the bottom right. Inside the SUT is a smaller rectangle labeled 'IUT' at its bottom right. Within the IUT, there are three stacked boxes: 'APM\_user' at the top, 'APM' in the middle, and 'ISUP Basic Call ISUP'97' at the bottom. A vertical double-headed arrow labeled 'APM\_user Information Flow' passes through the APM\_user box, extending above the Exchange boundary. Two horizontal double-headed arrows labeled 'ISUP' enter the IUT from the left and right sides, pointing towards the ISUP Basic Call ISUP'97 box. A small code 'T11103520-99' is located at the bottom right of the diagram. + +Diagram of the system under test (SUT) showing the hierarchy of protocols. The SUT (Exchange) contains the IUT, which contains APM\_user, APM, and ISUP Basic Call ISUP'97. Arrows show the flow of information between these layers and external ISUP connections. + +| | | +|----------|------------------------------------------------------------------| +| APM_user | Application Transport Mechanism user Protocol Control, e.g. PSS1 | +| APM | Application Transport Mechanism Protocol Control | +| ISUP | ISDN User Part | +| IUT | Implementation Under Test | +| SUT | System Under Test | + +Figure 1/Q.765 bis – The system under test + +The protocol functions for the Application Transport Mechanism relates to the signalling associations with a bearer (ISUP). Therefore the defined ISUP Basic Call and its associated formats and codes are required to support the Application Transport Mechanism. The following main subjects have to be considered in this area: + +- a) APM-user Protocol Control (APM-user Application Service Element). +- b) Application Transport Mechanism Protocol Control (APM Application Service Element). +- c) ISUP Basic Call (ISUP Application Service Element). + +The APM user primitives or APM user information flow can be observed through the individual reference point defined for each APM user or application process, respectively. In case of a PSS1 ASE (APM-user ASE for the VPN application) for example, the Q reference point is applicable. + +The ISUP signalling protocol can be observed on the SS No. 7 link on the Network Nodal Interface (NNI). + +From the ISUP/APM reference standard several types of exchanges (or roles) can be identified: + +- Local Exchanges in case of a Public Initiating Node (PIN) or a Public Addressed Node (PAN) with several APM-users. +- Transit Exchanges in the role of a PIN or PAN with several APM-users. +- National Transit Exchanges as defined in Recommendation Q.761. + +The National Transit Exchanges pass on the APM messages without checking the messages. In the case of a PIN or PAN the messages related to an APM call are checked according to the corresponding APM user. If the peer APM user is not residing in the exchange the call is passed on to the destination or to the addressed location (PAN). + +## **5.2 ATM and testing configuration for ISUP'97 – Application Transport Mechanism** + +The Abstract Test Method (ATM) chosen for the Application Transport Mechanism specification is the distributed multi-party test method. The ATM is defined at an appropriate level of abstraction so that the test cases may be specified appropriately, without adding restrictions to the implementation under test. + +The ATS is written in concurrent TTCN. + +## **5.3 Local exchanges – PIN/PAN** + +As mentioned above, the IUT can be tested within different configurations. The following text describes the test configuration for the IUT where the software for ISUP V3 and also the APM part reside in a local exchange. + +Figure 2 shows the logical test components of the adopted test configuration. The main test component is located on the right side of the IUT; it contains the ISUP part. On the left side there is a parallel test component which covers the APM part. + +![Figure 2/Q.765 bis – APM test configuration for local exchanges. The diagram shows a test setup with two main vertical paths. The left path consists of a 'TCP' block connected to a 'UT' (Upper Tester) block. Inside the 'UT' block are 'Application Process' and 'AI X'. Below the 'UT' block is an 'IUT' (Implementation Under Test) block, which contains 'SP A'. A double-headed arrow labeled 'UAX' connects the 'UT' block to the 'IUT' block. The right path consists of an 'LT' (Lower Tester) block connected to a 'SP B' block. Inside the 'LT' block is an 'ISUP link'. Below the 'SP B' block is a 'LAB' block. A double-headed arrow labeled 'LAB' connects the 'SP B' block to the 'LAB' block. Both the 'IUT' block and the 'LAB' block are connected to a common 'Network service provider' block at the bottom. The text 'T11103530-99' is located at the bottom right of the diagram.](d4af765160d04ecef538e5066006dc77_img.jpg) + +Figure 2/Q.765 bis – APM test configuration for local exchanges. The diagram shows a test setup with two main vertical paths. The left path consists of a 'TCP' block connected to a 'UT' (Upper Tester) block. Inside the 'UT' block are 'Application Process' and 'AI X'. Below the 'UT' block is an 'IUT' (Implementation Under Test) block, which contains 'SP A'. A double-headed arrow labeled 'UAX' connects the 'UT' block to the 'IUT' block. The right path consists of an 'LT' (Lower Tester) block connected to a 'SP B' block. Inside the 'LT' block is an 'ISUP link'. Below the 'SP B' block is a 'LAB' block. A double-headed arrow labeled 'LAB' connects the 'SP B' block to the 'LAB' block. Both the 'IUT' block and the 'LAB' block are connected to a common 'Network service provider' block at the bottom. The text 'T11103530-99' is located at the bottom right of the diagram. + +| | | | | +|-----|----------------------------------------|-----|------------------------------| +| AI | Application Interface for the APM-user | SP | Signalling Point | +| IUT | Implementation Under Test | TCP | Test Coordination Procedures | +| LAB | PCO for signalling link AB | UAX | Access to an APM-user | +| LT | Lower Tester | UT | Upper Tester | +| PCO | Point of Control and Observation | | | + +**Figure 2/Q.765 bis – APM test configuration for local exchanges** + +To observe and control the message flow on the ISUP and APM side for each side a Point of Control and Observation (PCO) is needed. The PCO for the ISUP link is abbreviated with an "L" followed by two letters indicating the interface. The naming convention for the PCO, specifying the Upper Tester, is the same but having an "U" instead of the "L" as the first character. + +There is no defined interface from ISUP (the IUT) towards the APM user side. For testing the primitives specified in [1], which are sent between the APM Application Service Element (ASE) and the APM user ASE, the above-mentioned Upper Tester (UT) is needed. It is therefore necessary to make use of an Application Interface (AI) including a PCO and to use the specified primitive names given in [1] for the Abstract Service Primitives (ASPs) to be used on this PCO. + +The LAB PCO is used by the Lower Tester (LT) to control and observe the ISUP on the signalling to the exchange. The other UAX PCO is needed to check if the expected primitives for the APM user are correctly generated by the exchange. The PDUs on this PCO are chosen at an appropriate level of abstraction. + +The Test Coordination Procedures (TCP) allow for communication between the testers. The test components are mostly implicitly coordinated (asynchronously); the TCPs are only used when it is necessary to obtain the verdict from the parallel test component. + +This configuration to test the local exchanges is presented in Figure 2. + +## 5.4 Transit exchanges – PIN/PAN + +For this configuration the same rules and definitions are applicable as used in 5.3, Local exchanges. + +## 5.5 Transit exchanges – ISUP + +The configuration proposed for testing transit exchanges is shown in Figure 3. In order to test the protocol and functionality of transit exchanges, one needs to consider the incoming and outgoing side of the SUT. + +![Diagram of APM test configuration for transit exchanges. It shows two Lower Testers (LT) connected to a central Implementation Under Test (IUT) via ISUP links. The LT on the left is connected to SP C, which is connected to a Network service provider via LAC. The LT on the right is connected to SP B, which is connected to a Network service provider via LAB. The IUT is connected to SP A, which is also connected to the Network service provider. Above the IUT is an Upper Tester (UT) with an Application Process (AIX) connected via UAX. The LTs are also connected to the UT via TCP.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Diagram of APM test configuration for transit exchanges. It shows two Lower Testers (LT) connected to a central Implementation Under Test (IUT) via ISUP links. The LT on the left is connected to SP C, which is connected to a Network service provider via LAC. The LT on the right is connected to SP B, which is connected to a Network service provider via LAB. The IUT is connected to SP A, which is also connected to the Network service provider. Above the IUT is an Upper Tester (UT) with an Application Process (AIX) connected via UAX. The LTs are also connected to the UT via TCP. + +T11103540-99 + +| | | | | +|-----|----------------------------------------------|-----|----------------------------------| +| AI | Application Interface for the APM-user | PCO | Point of Control and Observation | +| IUT | Implementation Under Test | SP | Signalling Point | +| LAB | PCO for signalling link AB | TCP | Test Coordination Procedures | +| LAC | Access signalling PCO (e.g. PSS1 signalling) | UAX | Access to an APM-user | +| LT | Lower Tester | UT | Upper Tester | + +**Figure 3/Q.765 bis – APM test configuration for transit exchanges** + +The IUT is observed and controlled from two ISUP links with associated circuits. The Points of Control and Observation (PCO) are labelled LAB on the one side and LAC on the other. + +The LAB and LAC PCOs are used by the Lower Testers (LT) for controlling the ISUP signalling links. + +The underlying network service provider is the Message Transfer Part (MTP) protocol as specified in Recommendations Q.701 to Q.707. + +The Test Coordination Procedures (TCP) allow for communication between the testers. The test components are mostly implicitly coordinated (asynchronously); the TCPs are only used when it is necessary to obtain the verdict from the parallel test component. + +The Upper Tester (UT) and its UAX PCO is not used in this configuration. + +# 6 Test Suite Structure (TSS) + +![A hierarchical diagram showing the Test Suite Structure (TSS) for APM. The root is APM, which branches into five main categories: 1 NP_S, 2 NP_R, 3 S_ACK, 4 SEG, and 5 ERR_H. NP_R branches into 1 CEST, 2 OT, and 3 SAT. SEG branches into 1 SG_PROC and 2 RA_PROC. ERR_H branches into 1 UC_PAN, 2 UC_PIN, 3 RAE, 4 EP_COI, and 5 EP_URV.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg) + +``` + +graph TD + APM --- NP_S + APM --- NP_R + APM --- S_ACK + APM --- SEG + APM --- ERR_H + NP_R --- CEST + NP_R --- OT + NP_R --- SAT + SEG --- SG_PROC + SEG --- RA_PROC + ERR_H --- UC_PAN + ERR_H --- UC_PIN + ERR_H --- RAE + ERR_H --- EP_COI + ERR_H --- EP_URV + +``` + +T111103550-99 + +A hierarchical diagram showing the Test Suite Structure (TSS) for APM. The root is APM, which branches into five main categories: 1 NP\_S, 2 NP\_R, 3 S\_ACK, 4 SEG, and 5 ERR\_H. NP\_R branches into 1 CEST, 2 OT, and 3 SAT. SEG branches into 1 SG\_PROC and 2 RA\_PROC. ERR\_H branches into 1 UC\_PAN, 2 UC\_PIN, 3 RAE, 4 EP\_COI, and 5 EP\_URV. + +**Figure 4/Q.765 bis – Test suite structure** + +Test Suite Structure (TSS) naming conventions are: + +| | | +|---------|----------------------------------------------------| +| NP_S | Normal Procedures Sending | +| NP_R | Normal Procedures Receiving | +| CEST | Call Establishment | +| OT | Procedures at Other Times | +| SAT | Send_APM_Transit | +| S_ACK | S ending of ACK nowledgement | +| SEG | SEG mentation | +| SG_PROC | PROC edures for SeG mentation | +| RA_PROC | PROC edures for ReAssembly | +| ERR_H | ERR or H andling with UCEH | +| UC_PAN | Unidentified Context Handling (PAN) | +| UC_PIN | Unidentified Context Handling (PIN) | +| RAE | ReAssembly Error Handling | +| EP_COI | Exceptional Procedures – Context identifier error | +| EP_URV | Exceptional Procedures – Unrecognized Reason value | +| V | Valid behaviour stimulus | + +# 7 Test Purposes (TP) + +## 7.1 Introduction + +For each test requirement a Test Purpose (TP) is defined. + +## 7.2 Test Purpose (TP) naming convention + +Test Purposes are numbered ascending within each group. Groups are organized according to the TSS down to the last but one level. The classification in the V/I groups is done by the inclusion of V or I in the test case name. Additional qualifiers, in form of lower case letters, are added to identify variants within one generic test case (see Table 1). + +**Table 1/Q.765 bis – TP Identifier naming convention scheme** + +| | | +|-------------|----------------------------------------------------------------------------------------------| +| Identifier: | APM_<group>_<N>_<n>_{<n>}_{<a>} | +| APM | = Application Transport Mechanism | +| | = One character representing the test group:
V: Valid stimulus
I: Inopportune stimulus | +| | = Sequence number in the test suite structure | +| | = Sequence number used within the group | +| {} | = Optional additional number used | +| {} | = Optional lower-case character distinguishing tests with same reference number | + +### 7.2.1 Source of test purpose definition + +The test purposes cover validation testing aspects and were developed within ETSI. + +### 7.2.2 Test purpose structure + +The test purpose structure overlaps with the Test Suite Structure (TSS). + +Test purposes that test normal behaviour have been grouped in the **V** – Valid behaviour group. + +Test purposes that test the IUT behaviour in situations that are not normal operation have been grouped in the **I** – Inopportune stimulus group. + +## 7.3 Test purposes for the Signalling System No. 7, Application Transport Mechanism (APM) + +All of the following test purposes belong to the main group ISUP\_97\_APM. Each test purpose is presented in a separate table. The first row of the table contains the following items: + +| | | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TSS | Identifier in the test suite structure (test group/subgroup identifier). | +| TP | Identifier of the test purpose. | +| Q.765 reference | The reference to the requirement in the Signalling System No. 7, application transport mechanism [1], which led to the test purpose. | +| Selection expression | Selection criterion for the test purpose taking into account the exchange's role and the answers to the specified PICS questions (see Annex A). If there is no selection expression specified, the TP is valid for all roles of exchanges. | +| Configuration | This is a reference to the test configuration used. | + +The next row defines the test purpose itself, each having a *title* in *italics* and a text body. + +The ISUP **messages**, **parameters**, the APM **primitives** are highlighted in **bold** to ease the readability. + +In order to check the specified behaviour for some test purposes, a special prerequisite test condition has to be fulfilled. If such a condition is needed, it is presented after the test purpose under the heading "Pre-test conditions". + +### 7.3.1 Application Transport Mechanism (APM ASE) + +#### 7.3.1.1 Normal procedures – Sending + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------|----------------------|-----------------------------| +| TSS
/NP_S/ | TP
APM_V_1_1 | Q.765 reference
10.2.1/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Mapping of application transport parameter
To verify that the IUT can successfully construct the Application Transport Parameter (APP) in case of reception of an APM_Data request primitive from the APM-user and map this in an Initial Address Message (IAM) .
Pre-test conditions: Do nothing, keep quiet!! | | | | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------|----------------------|-----------------------------| +| TSS
/NP_S/ | TP
APM_V_1_2 | Q.765 reference
10.2.1/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Pass on of an APM Transit primitive
To verify that the IUT can successfully pass on the APM_Transit request from the APM user and does not change the contents which is mapped into an Application Transport Message (APM) .
Pre-test conditions: None | | | | | + +#### 7.3.1.2 Normal procedures – Receiving + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|----------------------|-----------------------------| +| TSS
/NP_R/CEST | TP
APM_V_2_1_3 | Q.765 reference
10.2.2.1/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Mapping of the application transport parameter – Context supported/no reassembly
To verify that the IUT can successfully map the Application Transport Parameter (APP) in the received Initial Address Message (IAM) into an APM_Data indication primitive which is sent to the APM-user.
Note that the Application Transport Parameter (APP) contains the following data:
– Application Context Identifier: specified by the person who executes the test e.g. 1 (PSS1);
– APM segmentation indicator: 0 (final segment);
– Sequence indicator field: 0 (Subsequent segment to first segment).
Pre-test conditions: None | | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|----------------------|-----------------------------| +| TSS
/NP_R/CEST | TP
APM_V_2_1_4 | Q.765 reference
10.2.2.1/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose
Mapping of the application transport parameter – Context not supported/no reassembly

To verify that the IUT can successfully map the Application Transport Parameter (APP) with the Application Context Identifier set to '63' (spare value) in the received Initial Address Message (IAM) into an APM_UCEH_Error indication primitive which is sent to the APM-user. The Application Context and Application Transport Instruction Indicators (ATII) are set as received in the APM_Transfer primitive and the Reason is set to 'Unidentified Context'.

Note that the Application Transport Parameter (APP) contains the following data:

  • – Application Context Identifier: 63 (spare)/the context should not be supported;
  • – APM segmentation indicator: 0 (final segment);
  • – Sequence indicator field: 0 (Subsequent segment to first segment).

Pre-test conditions: None

| | | | | + +###### 7.3.1.2.1 Procedures at other times + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|----------------------|--------------------------| +| TSS
/NP_R/OT | TP
APM_V_2_2_5 | Q.765 reference
10.2.2.2/Q.765 | Selection expression | Configuration
Transit | +|

Test purpose
Pass on of the application transport parameter

To verify that the IUT can successfully pass on the received Application Transport Parameter (APP) in an Initial Address Message (IAM) if the context does not belong to this node. The IUT shall not verify and change the contents of the Transit_Data parameter of the APM_Transfer indication primitive.

Pre-test conditions: None

| | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------|-----------------------------------|-----------------------------| +| TSS
/NP_R/OT | TP
APM_V_2_2_6 | Q.765 reference
10.2.2.2/Q.765
10.2.4/Q.765
7.2.3.3.1/Q.765 | Selection expression
PICS A1/3 | Configuration
Local/TE_P | +|

Test purpose
Context supported – Segmentation applies/PIN is not sending any APM messages before acknowledgement received

To verify that the IUT (PIN) shall not send subsequent segments to an Initial Address Message (IAM) until a Address Complete Message (ACM) is received containing an Application Transport Parameter (APP), which implicitly indicates that a path has been successfully routed to the PAN. To trigger that behaviour, an APM_Data primitive with the parameter set to:

  • – Application Context Identifier: specified by a person who executes the test, e.g. 1 (PSS1);
  • – Application Transport Instruction Indicator: 0 (do not release call);
  • – Application Information: some garbage data with more than 2048 bytes,

is sent from the tester to the IUT.

Pre-test conditions: None

| | | | | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------|----------------------|-----------------------------| +| TSS
/NP_R/OT | TP
APM_V_2_2_7 | Q.765 reference
10.2.2.2/Q.765
7.2.3.3.1/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Context supported – Segmentation reassembly applies/PAN
To verify that the IUT can successfully map the Initial Address Message (IAM) with an Application Transport Parameter (APP) set to:
  • – Application Context Identifier (ACI): specified by a person who execute the test, e.g. 1 (PSS1 ASE );
  • – Application Transport Instruction Indicators (ATII): 0 (do not release);
  • – APM segmentation indicator: 2 (indicates 2 following segments);
  • – Sequence indicator (SI): 1 (New sequence),
into a More_APP_Info primitive and send it to the APM-user.
Pre-test conditions: None | | | | | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|----------------------|-----------------------------| +| TSS
/NP_R/OT | TP
APM_V_2_2_8 | Q.765 reference
10.2.2.2/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Context supported – Segmentation applies
To verify that the IUT sends the completely reassembled Application Information in an APM_Data indication primitive to the APM-user, after reception of an Application Transport Message (APM) which contains an Application Transport Parameter (APP) indicating the APM segmentation indicator set to 'final segment'.
Pre-test conditions: None | | | | | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|----------------------|--------------------------| +| TSS
/NP_R/OT | TP
APM_V_2_2_9 | Q.765 reference
10.2.2.2/Q.765 | Selection expression | Configuration
Transit | +| Test purpose
Context not supported – Pass-on node
To verify that the IUT can successfully map the Initial Address Message (IAM) with the Application Transport Parameter (APP) indicating an unsupported context into an APM_Transit indication primitive including the same Application Transport Parameter (APP) and send it to the PAN.
Pre-test conditions: None | | | | | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------------------|----------------------|-----------------------------| +| TSS
/NP_R/OT | TP
APM_V_2_2_10 | Q.765 reference
10.2.2.2/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Context not supported – 1st segment of sequence
To verify that the IUT sends an APM_UCEH_Error indication primitive with the Application Context and Application Transport Instruction Indicators (ATII) set as received in the APM_Transfer primitive and the Reason indicates 'Unidentified Context' to the APM-user in case of receiving an Initial Address Message (IAM) with the Application Transport Parameter (APP) indicating a context which is not supported by the IUT.
Pre-test conditions: None | | | | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------------------|----------------------|-----------------------------| +| TSS
/NP_R/OT | TP
APM_V_2_2_11 | Q.765 reference
10.2.2.2/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Context not supported – 2nd segment of sequence
To verify that the IUT discards an APM_Transfer primitive which is a subsequent segment to an Initial Address Message (IAM) containing an Application Transport Parameter (APP) with a context which was not supported by the IUT.
Note that the tester sends the Application Transport Message (APM) for the second segment.
Pre-test conditions: None | | | | | + +###### 7.3.1.2.2 Reception of the Send\_APM\_Transit primitive + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------------------|----------------------|-----------------------------| +| TSS
/NP_R/SAT | TP
APM_V_2_3_12 | Q.765 reference
10.2.2.3/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Send_APM_Transit – Pass on transparently
To verify that the IUT can successfully pass on unchanged the contents of the Send_APM_Transit primitive send by the APM-user to an APM_Transit primitive which is mapped into an Application Transport Message (APM) on the ISUP side.
Pre-test conditions: None | | | | | + +##### 7.3.1.3 Send of acknowledgement + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------|----------------------|-----------------------------| +| TSS
/S_ACK | TP
APM_V_3_1 | Q.765 reference
10.2.3/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
APM_Acknowledgement request – Construction of related APP
To verify that the IUT is able to construct the appropriate Application Transport Parameter (APP) to a given context (e.g. VPN) received in an APM_Acknowledgement request primitive and send it in an APM_Transfer request primitive or Application Transport Message (APM), respectively to the PAN. The Application Transport Parameter (APP) shall be coded as follows:
Application Transport Instruction Indicator (ATII): Bit A=1 (release call) Bit B=0 (do not send notification)
The Application Information field shall be empty.
Pre-test conditions: None | | | | | + +#### 7.3.1.4 Segmentation + +###### 7.3.1.4.1 Procedures for segmentation + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +| TSS
/SEG/SG_PROC | TP
APM_V_4_1_1 | Q.765 reference
10.2.4.1 a)/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Segmentation – Splitting into 3 segments
To verify that the IUT can successfully apply the segmentation procedure, an APM_Data request primitive is received by the APM-user with an application data parameter containing 3 segments (about 4200 bytes). The IUT should map this primitive into an Initial Address Message (IAM) which is followed by the Application Transport Messages (APM).
Pre-test conditions: None | | | | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|---------------------------------------|-----------------------------| +| TSS
/SEG/SG_PROC | TP
APM_V_4_1_2 | Q.765 reference
10.2.4.1 a)/Q.765 | Selection expression
NOT PICS A1/4 | Configuration
Local/TE_P | +|

Test purpose
Segmentation – Discarding of IAM
To verify that the IUT discards an APM_Data request primitive containing an Application Data parameter which is greater than 10 segments, e.g. >2 Mbytes.

Pre-test conditions: None

| | | | | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|-----------------------------------|-----------------------------| +| TSS
/SEG/SG_PROC | TP
APM_V_4_1_3 | Q.765 reference
10.2.4.1 a)/Q.765 | Selection expression
PICS A1/4 | Configuration
Local/TE_P | +|

Test purpose
Segmentation – Discarding of IAM
To verify that the IUT discards an APM_Data request primitive containing an Application Data parameter which is greater than 9 segments, e.g. >1.8 Mbytes.

Pre-test conditions: None

| | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +| TSS
/SEG/SG_PROC | TP
APM_V_4_1_4 | Q.765 reference
10.2.4.1 b)/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose
Segmentation – Generation of IAM with appropriate application transport parameter
To verify that the IUT can successfully map the application data parameter of the APM_Data request primitive into an Initial Address Message (IAM) followed by associated Application Transport Messages (APM). The IAM should include the Application Transport Parameter (APP) containing the Segmentation indicator field with 'new sequence' and the Number of Segments Remaining field indicating the number of segments that remains to be sent to the PAN with the appropriated Application Transport Messages (APM).

Pre-test conditions: None

| | | | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +| TSS
/SEG/SG_PROC | TP
APM_V_4_1_5 | Q.765 reference
10.2.4.1 c)/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose
Segmentation – Segmentation indicator field set to 'subsequent segment to first segment'
To verify that the IUT can successfully segment the received APM_Data request primitive into an Initial Address Message (IAM) and the associated Application Transport Messages (APM) with the following coding rules:
The encapsulated information field in each Application Transport Message (APM) shall begin with the first octet following the last octet transmitted in the previous segment. The APM segmentation indicator field shall indicate 'subsequent segment to first segment' and the Number of Segments Remaining field shall be decremented to indicate the number of segments that remain to be sent. The Segmentation Local Reference (SLR) shall have the same value as sent in the Initial Address Message (IAM) or first Application Transport Message (APM).

Pre-test conditions: None

| | | | | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +| TSS
/SEG/SG_PROC | TP
APM_V_4_1_6 | Q.765 reference
10.2.4.1 f)/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose
Segmentation – Continuity of the ATII parameter
To verify that the IUT is able to provide the Application Transport Instruction Indicators (ATII) parameter as received in the APM_Data request primitive from the APM-user. This is applicable for the first and all subsequent segments, i.e. the Initial Address Message (IAM) and the following Application Transport Messages (APM) send by the IUT to the PAN.

Pre-test conditions: None

| | | | | + +###### 7.3.1.4.2 Procedures for reassembly + +| TSS
/SEG/RA_PROC | TP
APM_V_4_2_1 | Q.765 reference
10.2.4.2 a), b), d)/Q.765 | Selection expression | Configuration
Local/TE_P | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------|----------------------|-----------------------------| +|

Test purpose

Reassembly – Basic rules

To verify that the IUT can successfully apply the reassembly function, on receiving of an Initial Address Message (IAM) which is followed by a sequence of two associated Application Transport Message (APM) where the first Application Transport Message (APM) is received with the Sequence Indicator field indicating 'subsequent segment to first segment' and the Number of Segments Remaining field set to a value one less than the value in the previously received segment and the same Segmentation Local Reference (SLR) value as received in the Initial Address Message (IAM). The second Application Transport Message (APM) includes the Application Transport Parameter (APP) with the Number of Segments Remaining field having value equal to zero and 'final segment'; then the IUT shall deliver the accumulated segments, including the last segment, as the complete Application Information to the APM-user with the APM_Data indication primitive.

Note that the Initial Address Message (IAM) and Application Transport Messages (APM) are sent by the tester.

Pre-test conditions: None

| | | | | + +| TSS
/SEG/RA_PROC | TP
APM_V_4_2_2 | Q.765 reference
10.2.4.2 e)/Q.765 | Selection expression | Configuration
Local/TE_P | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +|

Test purpose

Reassembly – No reassembly active/Send APM_UCEH_Error Indication (Subsequent segment to first segment)

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' in case no reassembly process is active and an Application Transport Message (APM) is received with a Sequence Indicator coded 'Subsequent segment to first segment'.

Note that the previous message, e.g. an Initial Address Message (IAM), to this Application Transport Message (APM) indicates 'final segment' in the APM segmentation indicator.

Pre-test conditions: None

| | | | | + +| TSS
/SEG/RA_PROC | TP
APM_V_4_2_3 | Q.765 reference
10.2.4.2 e)/Q.765 | Selection expression | Configuration
Local/TE_P | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +|

Test purpose

Reassembly – No reassembly active/Send APM_UCEH_Error Indication (number of segments >9)

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' in case no reassembly process is active and an Application Transport Message (APM) is received with a Number of Segments Remaining field value exceeding 9.

Pre-test conditions: None

| | | | | + +| TSS
/SEG/RA_PROC | TP
APM_V_4_2_4 | Q.765 reference
10.2.4.2 f)/Q.765 | Selection expression | Configuration
Local/TE_P | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +|

Test purpose

Reassembly – Reassembly active/Send APM_UCEH_Error Indication (decrementation error)

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' and discards the received and any saved segments on receipt of an Application Transport Message (APM) including an Application Transport Parameter (APP) with a Number of Segments Remaining field value that is not decremented from the value of the previous messages. There shall be no APM_Data indication primitive sent to the APM-user.

Pre-test conditions: None

| | | | | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +| TSS
/SEG/RA_PROC | TP
APM_V_4_2_5 | Q.765 reference
10.2.4.2 f)/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Reassembly – Reassembly active/Send APM_UCEH_Error Indication (different Segmentation Local Reference)

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' and discards the received and any saved segments on receipt of an Application Transport Message (APM) including an Application Transport Parameter (APP) with a Segmentation Local Reference (SLR) which differs from the received Segmentation Local Reference (SLR) in the first messages [e.g. an Initial Address Message (IAM)]. There shall be no APM_Data indication primitive sent to the APM-user.

Pre-test conditions: None

| | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +| TSS
/SEG/RA_PROC | TP
APM_V_4_2_6 | Q.765 reference
10.2.4.2 g)/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Reassembly – Reassembly active/Send APM_UCEH_Error Indication (Segments with a Sequence Indicator indicating 'New sequence')

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' and discards the received and any saved segments on receipt of an Application Transport Message (APM) including an Application Transport Parameter (APP) with a Sequence Indicator coded 'New Sequence'. There shall be no APM_Data indication primitive sent to the APM-user.

Note that the first message of the sequence, e.g. an Initial Address Message (IAM), shall include the Sequence Indicator indicating 'New Sequence', the following Application Transport Messages (APM) shall indicate 'Subsequent segment to first segment' in that parameter.

Pre-test conditions: None

| | | | | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------|----------------------|-----------------------------| +| TSS
/SEG/RA_PROC | TP
APM_V_4_2_7 | Q.765 reference
10.2.4.2 h)/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Reassembly – No reassembly active/Send APM_UCEH_Error Indication

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' and discard all received segments for the current sequence on expiry of timer T-reass. There shall be no APM_Data indication primitive sent to the APM-user.

Pre-test conditions: None

| | | | | + +### 7.3.2 Unidentified Context and Error Handling (UCEH ASE) + +#### 7.3.2.1 Unidentified Context handling (PAN) + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/UC_PAN | TP
APM_V_5_1_1 | Q.765 reference
13.1.1/Q.765
7.2.3.3.2/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Unidentified Context handling – Unidentified context identifier, release call/Send APM_UCEH_Error Indication

To verify that the IUT (PAN) sends an APM_UCEH_Error indication primitive to the APM-user in case of receiving an Initial Address Message (IAM) which includes an unknown context identifier and an Application Transport Instruction Indicator (ATII) set to 'release call' in the Application Transport Parameter (APP). The IUT shall release the call with a Release (REL) message. The value of the Reason in the UCEH_Release indication primitive is be mapped into the Cause parameter of the Release (REL) message, indicating the cause value #79, 'Unidentified Context'. Also an UCEH_Release indication primitive shall be sent to the APM-user (application). Note that before the Release (REL) is sent, a Pre_Release (PRI) message is sent which carries the Application Transport Parameter (APP) with the appropriate data.

Pre-test conditions: None

| | | | | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/UC_PAN | TP
APM_V_5_1_2 | Q.765 reference
13.1.1/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Unidentified Context handling – Unidentified context identifier, allowed to proceed/Send APM_UCEH_Error Indication

To verify that the IUT (PAN) sends an APM_UCEH_Error indication primitive to the APM-user in case of receiving an Initial Address Message (IAM) which includes an unknown context identifier and an Application Transport Instruction Indicator (ATII) set to 'do not release call' in the Application Transport Parameter (APP). The IUT shall not release the call.

Pre-test conditions: None

| | | | | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/UC_PAN | TP
APM_V_5_1_3 | Q.765 reference
13.1.1/Q.765
7.2.3.3.2/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Unidentified Context handling – Unidentified context identifier, do not send notification/Send APM_UCEH_Error Indication

To verify that the IUT (PAN) sends an APM_UCEH_Error indication primitive to the APM-user in case of receiving an Initial Address Message (IAM) which includes an unknown context identifier and an Application Transport Instruction Indicator (ATII) set to 'release call' and 'do not send notification' in the Application Transport Parameter (APP). The IUT shall release the call with a Release (REL) message. The value of the Reason in the UCEH_Release indication primitive is be mapped into the Cause parameter of the Release (REL) message, indicating the cause value #79, 'Unidentified Context'. The IUT shall not send an Application Transport Message (APM) including an Application Context Identifier indicating 'Unidentified Context and Error Handling (UCEH) ASE' in the Application Transport Parameter (APP). Note that before the Release (REL) is sent, a Pre_Release (PRI) message is sent which carries the Application Transport Parameter (APP) with the appropriate data.

Pre-test conditions: None

| | | | | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/UC_PAN | TP
APM_V_5_1_4 | Q.765 reference
13.1.1/Q.765
7.2.3.2/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Unidentified Context handling – Unidentified context identifier, send notification/Send APM_UCEH_Error Indication

To verify that the IUT (PAN) sends an APM_UCEH_Error indication primitive to the APM-user in case of receiving an Initial Address Message (IAM) which includes an unknown context identifier and an Application Transport Instruction Indicator (ATII) set to 'release call' and 'send notification' in the Application Transport Parameter (APP). The IUT shall release the call with a Release (REL) message. The value of the Reason in the UCEH_Release indication primitive is be mapped into the Cause parameter of the Release (REL) message, indicating the cause value #79, 'Unidentified Context'. The IUT shall send the Application Transport Parameter (APP) set as below, in an backward message [Application Transport Message (APM)] to the PIN.

Application Transport Parameter (APP) settings:

  • – Application Context Identifier: 0 [Unidentified Context and Error Handling (UCEH)] ASE;
  • – Application Transport Instruction Indicator: Bit A=1 (release call) Bit B=0 (do not send notification).

The Encapsulated Application Information includes the 'Application Transport Notification Information' with the abused 'Application Context Identifier' and the reason set to 'Unidentified Context'.

An APM_Data indication primitive shall be sent to the APM-user (application).

Note that before the Release (REL) is sent, a Pre_Release (PRI) message is sent which carries the Application Transport Parameter (APP) with the appropriate data.

Pre-test conditions: None

| | | | | + +#### 7.3.2.2 Unidentified Context handling (PIN) + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------|----------------------|--------------------------| +| TSS
/ERR_H/UC_PIN | TP
APM_V_5_2_1 | Q.765 reference
13.1.2/Q.765 | Selection expression | Configuration
Transit | +|

Test purpose

Unidentified Context handling – APP 'pass on' to the APM-user

To verify that the IUT (PIN) is able to pass on unchanged the Application Transport Parameter (APP) of the received Application Transport Message (APM), if the IUT is a 'pass on' node for the Context Identifier.

Pre-test conditions: None

| | | | | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/UC_PIN | TP
APM_V_5_2_2 | Q.765 reference
13.1.2/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Unidentified Context handling – APP not 'pass on' to the APM-user

To verify that the IUT (PIN) is able to send an APM_Error indication primitive to the APM-user identified by the Context Identifier in the Application Transport Parameter (APP) of the received Application Transport Message (APM). The APM_Error indication primitive is indicating that the reason for the error was that the peer APM-user was not present at the PAN.

Pre-test conditions: None

| | | | | + +#### 7.3.2.3 Reassembly Error Handling + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/RA | TP
APM_V_5_3_1 | Q.765 reference
13.2/Q.765
7.2.3.3.2/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Reassembly – Reassembly active/Send APM_UCEH_Error Indication (different Segmentation Local Reference)

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' and discards the received and any saved segments on receipt of an Application Transport Message (APM) including an Application Transport Parameter (APP) with an Application Transport Instruction Indicator (ATII) set to 'release call' and a Segmentation Local Reference (SLR) which differs from the received Segmentation Local Reference (SLR) in the first messages [e.g. an Initial Address Message (IAM)]. There shall be no APM_Data indication primitive send to the APM-user.

The IUT shall release the call with a Release (REL) message. The value of the Reason parameter in the UCEH_Release indication primitive is be mapped into the Cause parameter of the Release (REL) message indicating the cause value #111 (reassembly error). Also, an UCEH_Release indication primitive shall be sent to the APM-user (application).

Note that before the Release (REL) is sent, a Pre_Release (PRI) message is sent which carries the Application Transport Parameter (APP) with the appropriate data.

Pre-test conditions: None

| | | | | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/RA | TP
APM_V_5_3_2 | Q.765 reference
13.2/Q.765
13.4.2/Q.765
7.2.3.3.2/Q.765 | Selection expression | Configuration
Local/TE_P | +|

Test purpose

Reassembly – Reassembly active/Send APM_UCEH_Error Indication (different Segmentation Local Reference)

To verify that the IUT sends an APM_UCEH_Error Indication primitive indicating 'reassembly error' and discards the received and any saved segments on receipt of an Application Transport Message (APM) including an Application Transport Parameter (APP) with an Application Transport Instruction Indicator (ATII) set to 'release call', 'send notification' and a Segmentation Local Reference (SLR) which differs from the received Segmentation Local Reference (SLR) in the first messages [e.g. an Initial Address Message (IAM)]. No APM_Data indication primitive shall be sent to the APM-user.

The IUT shall release the call with a Release (REL) message. The value of the Reason parameter in the UCEH_Release indication primitive is be mapped into the Cause parameter of the Release (REL) message indicating the cause value #111.

The IUT shall send the Application Transport Parameter (APP) set as below, in a backward message [PRE-Release (PRI)] to the PIN.

Application Transport Parameter (APP) settings:

  • – Application Context Identifier: 0 [Unidentified Context and Error Handling (UCEH)] ASE;
  • – Application Transport Instruction Indicator: Bit A=1 (release call) Bit B=0 (do not send notification).

The Encapsulated Application Information includes the 'Application Transport Notification Information' with the abused 'Application Context Identifier' and the reason set to 'Reassembly Error'.

An APM_Data indication primitive shall be sent to the APM-user (application).

Note that before the Release (REL) is sent, a Pre_Release (PRI) message is sent which carries the Application Transport Parameter (APP) with the appropriate data.

Pre-test conditions: None

| | | | | + +#### 7.3.2.4 Exceptional Procedures – Context identifier error + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/EP_COI | TP
APM_V_5_4_1 | Q.765 reference
13.4.3/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Context identifier error – Context identifier set to 'no information'
To verify that the IUT (PIN) discards the ' Application Transport Notification Information ' if it indicates a context identifier with 'no information' in the Encapsulated Application Information of an Application Transport Parameter (APP). The Application Transport Parameter (APP) is received from the PAN in an Application Transport Message (APM).
Note that the tester sends the Application Transport Message (APM) to the IUT.
Pre-test conditions: None | | | | | + +##### 7.3.2.5 Exceptional Procedures – Unrecognized Reason value + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------|----------------------|-----------------------------| +| TSS
/ERR_H/EP_URV | TP
APM_V_5_5_1 | Q.765 reference
13.4.4/Q.765 | Selection expression | Configuration
Local/TE_P | +| Test purpose
Context identifier error – Context identifier with unrecognized Reason
To verify that the IUT (PIN) discards the ' Application Transport Notification Information ' if it indicates a Reason with 'spare' in the Encapsulated Application Information of an Application Transport Parameter (APP). The Application Transport Parameter (APP) is received from the PAN in an Application Transport Message (APM).
Note that the tester sends the Application Transport Message (APM) to the IUT.
Pre-test conditions: None | | | | | + +# 8 Test coverage + +The test purposes defined in this test specification cover most main capabilities of the Application Transport Mechanism (APM). For this purpose, the essential components of the Q.765 specification, i.e. the Application Transport Mechanism protocol control (APM Application Service Element), the ISUP Basic Call (ISUP Application Service Element), the Unidentified Context and Error Handling control (UCEH ASE), and the associated procedures are tested. + +A list containing the number of test purposes for the related requirements of Recommendation Q.765 is provided in Table 2. + +Whenever it was possible, the test purposes have been described such that they bundle related requirements of Recommendation Q.765. Due to this fact, a test purpose may lead to implementing several test cases for the ATS. + +The test purposes concentrate on valid behaviour. This means that there is no invalid behaviour test purposes specified. An expansion of the invalid behaviour test purposes is left for further study. + +**Table 2/Q.765 bis – Number of tests for the Application Transport Mechanism (APM)** + +| Item | APM procedures | Group | Number of test purposes | +|-------------|-------------------------------------|---------|-------------------------| +| | APM ASE | | | +| 1 | Normal procedures | NP | 12 | +| 2 | Send of acknowledgement | S_ACK | 1 | +| 3 | Procedures for Segmentation | SG_PROC | 6 | +| 4 | Procedures for Reassembly | RA_PROC | 7 | +| | Error Handling with UCEH ASE | | | +| 5 | Unidentified Context handling (PAN) | UC_PAN | 4 | +| 6 | Unidentified Context handling (PIN) | UC_PIN | 2 | +| 7 | Reassembly Error Handling | RA | 2 | +| 8 | Exceptional Procedures | EP | 2 | +| Grand total | | | 36 | + +# 9 Conformance to the PICS proforma specification + +A PICS proforma that conforms to this PICS proforma specification shall be technically equivalent to Annex A, and shall preserve the numbering and ordering of the items in Annex A. + +A PICS that conforms to this PICS proforma specification shall: + +- describe an implementation which is claimed to conform to ISDN User part 1997 (ISUP'97) reference specification [1] to [3]; +- be a conforming PICS proforma which has been completed in accordance with the instructions for completion given in A.1; +- include the information necessary to uniquely identify both the supplier and the implementation. + +# ANNEX A1 + +## PICS proforma for ISDN User Part 1997 (ISUP'97) – Signalling System No. 7, Application Transport Mechanism + +### A.1 Instructions for completing the PICS proforma + +The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately. + +More detailed instructions are given at the beginning of the different subclauses of the PICS proforma. + +--- + +1 Copyright release for PICS proforma + +Users of this Recommendation may freely reproduce the PICS proforma in this annex so that it can be used for its intended purpose, and may further publish the completed PICS. + +#### A.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 ISDN User Part 1997 (ISUP'97) reference specification [1] to [3] may provide information about the implementation in a standardized manner. + +The PICS proforma is subdivided into subclauses for the following categories of information: + +- instructions for completing the PICS proforma; +- identification of the implementation; +- identification of the reference protocol specification; +- PICS proforma tables (containing the global statement of conformance). + +#### A.1.2 Abbreviations and conventions + +The PICS proforma contained in this annex is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [8]. + +##### Item column + +It contains a number that identifies the item in the table. + +##### Item description column + +It describes each respective item (e.g. parameters, timers, etc.). + +##### Reference column + +It gives reference to the ISUP'97 specification for the Application Transport Mechanism [1], except where explicitly stated otherwise. + +##### Status column + +The following notations, defined in ISO/IEC 9646-7 [8], are used for the status column: + +- m mandatory – The capability is required to be supported. +- n/a not applicable – In the given context, it is impossible to use the capability. No answer in the support column is required. +- o optional – The capability may or may not be supported. +- o.i qualified optional – For mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. +- ci conditional – The requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression that is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE n/a" shall be implied. + +NOTE – Support of a capability means that the capability is implemented in conformance to the ISUP'97 specification [1] to [3]. + +##### Support column + +The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [8], are used for the support column: + +- Y or y Supported by the implementation. +- N or n Not supported by the implementation. +- N/A or – No answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status). + +##### **Values allowed column** + +This column contains the values or the ranges of values allowed. + +##### **Values supported column** + +The support column shall be filled in by the supplier of the implementation. In this column the values or the ranges of values supported by the implementation shall be indicated. + +##### **References to items** + +For each possible item answer (answer in the support column) within the PICS proforma a unique reference exists. It is defined as the table identifier, followed by a slash character "/", followed by the item number in the table. If there is more than one support column in a table, the columns shall be discriminated by letters (a, b, etc.) respectively. + +Example 1: A.5/4 would indicate the reference to the answer of item 4 in Table A.5 of Annex A. + +Example 2: A.6/3b would indicate the reference to the second answer (i.e. in the second support column) of item 3 in Table A.6 of Annex A. + +### **A.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. + +#### **A.2.1 Date of the statement** + +| | | +|------------------------|--| +| Date of the statement: | | +|------------------------|--| + +#### **A.2.2 Implementation Under Test (IUT) identification** + +| | | +|--------------|--| +| IUT name: | | +| IUT version: | | + +#### **A.2.3 System Under Test (SUT) identification** + +| | | +|-------------------------|--| +| SUT name: | | +| Hardware configuration: | | +| Operating system: | | + +#### **A.2.4 Product supplier** + +| | | +|-------------------------|--| +| Name: | | +| Address: | | +| Telephone number: | | +| Facsimile number: | | +| Additional information: | | + +#### A.2.5 Client + +| | | +|-------------------------|--| +| Name: | | +| Address: | | +| Telephone number: | | +| Facsimile number: | | +| Additional information: | | + +#### A.2.6 ICS contact person + +| | | +|-------------------------|--| +| Name: | | +| Telephone number: | | +| Facsimile number: | | +| Additional information: | | + +### A.3 Identification of the reference specification + +This PICS proforma applies to the following standard: ITU-T Recommendations Q.73x (1997). + +Note that as prerequisite it is necessary to support the basic services described in [9]. A separate PICS proforma has been specified for ISUP'92 basic services [9]. + +### A.4 PICS proforma tables + +#### A.4.1 Global statement of conformance + +| | | +|---------------------------------------------|----------| +| | (Yes/No) | +| Are all mandatory capabilities implemented? | | + +NOTE – Answering "No" to this question indicates non-conformance to the reference protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming. + +#### A.4.2 Roles + +**Table A.1/Q.765 bis – Roles** + +| Item | Is the implementation ... | Reference | Status | Support | +|--------------------------------------------------------------|----------------------------------------------|-----------|--------|---------| +| 1 | Local – Local exchange PIN or PAN? | 6.1/Q.765 | o.1 | | +| 2 | TE_P – National transit exchange PIN or PAN? | 6.1/Q.765 | o.1 | | +| 3 | Transit – National transit exchange? | Q.761 | o.1 | | +| o.1: It is mandatory to support at least one of these items. | | | | | + +#### A.4.3 Capabilities + +**Table A.2/Q.765 bis – APM major capabilities** + +| Item | Is the exchange able to ... | Reference | Status | Support | +|------|------------------------------------------------------------------------------------------------------------------------------|---------------------|--------|---------| +| 1 | carry data in the first message (Initial Address Message (IAM)) during the establishment phase? (no segmentation necessary) | 7.2.1/Q.765 | | | +| 2 | acknowledge the receipt of an IAM with an Address Complete Message (ACM) as the first backward message? | 7.2.3.3.1/
Q.765 | | | +| 3 | transport the data in the initial segment if the segmentation procedure applies? (This means the size is not of zero length) | 10.2.4.1/
Q.765 | | | +| 4 | reassemble the message of the first segment if there are more than zero octets of Encapsulated Application Information? | 10.2.4.2/
Q.765 | | | +| 5 | send an early Address Complete Message? | | | | + +o.1: It is mandatory to support at least one of these items. + +**Table A.3/Q.765 bis – APM timers** + +| Item | Use of ... | Reference | Status | Support | Values in seconds | | +|------|------------|----------------|--------|---------|-------------------|-----------| +| | | | | | Allowed | Supported | +| 1 | T - reass | Table 30/Q.765 | m | | 10-18 | | + + + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Languages and general software aspects for telecommunication systems | + +\*18114\* \ No newline at end of file diff --git a/marked/Q/T-REC-Q.781-200204-I_PDF-E/06da11ab76cacc38bbcd714e437797ea_img.jpg b/marked/Q/T-REC-Q.781-200204-I_PDF-E/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80769f969617ac947f1a3f69d892f719ed98c13e --- /dev/null +++ b/marked/Q/T-REC-Q.781-200204-I_PDF-E/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9b0675c431aa29d4211b8def8db5d0b8a709d75fc6edb3327abd5bf3c43cb99 +size 15074 diff --git a/marked/Q/T-REC-Q.781-200204-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.781-200204-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.781-200204-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.781-200204-I_PDF-E/raw.md b/marked/Q/T-REC-Q.781-200204-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..54fdb17b7d9d7f91151da431836f490247e429fb --- /dev/null +++ b/marked/Q/T-REC-Q.781-200204-I_PDF-E/raw.md @@ -0,0 +1,2928 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.781** + +(04/2002) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Test +specification + +--- + +**MTP level 2 test specification** + +ITU-T Recommendation Q.781 + +--- + +# 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 | +| 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 | +| 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.781** + +# **MTP level 2 test specification** + +## **Summary** + +This Recommendation contains a set of detailed tests of Signalling System No. 7 MTP level 2 protocol. These tests intend to validate the protocol specified in ITU-T Rec. Q.703. + +This Recommendation conforms to ITU-T Rec. Q.780 which describes the basic rules of the Test Specification. In addition, the conditions which are specific to level 2 tests are described. + +## **Source** + +ITU-T Recommendation Q.781 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 13 April 2002. + +## 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 | Introduction ..... | 1 | +| 2 | General principles of level 2 tests ..... | 1 | +| 2.1 | Presentation of test descriptions ..... | 1 | +| 2.2 | Presentation of the test list ..... | 1 | +| 3 | Test configuration..... | 1 | +| 4 | Test environment ..... | 1 | +| 5 | Test list ..... | 2 | +| 6 | Test descriptions..... | 6 | + + + +## MTP level 2 test specification + +# 1 Introduction + +This Recommendation contains a set of detailed tests of signalling system No. 7 MTP level 2 protocol. These tests intend to validate the protocol specified in ITU-T Rec. Q.703. + +This Recommendation conforms to ITU-T Rec. Q.780 which describes the basic rules of the Test Specification. In addition, the conditions which are specific to level 2 tests are described in the following clauses. + +## 2 General principles of level 2 tests + +## 2.1 Presentation of test descriptions + +The level 2 tests aim at testing the level 2 protocol conformance in a given implementation. + +Each test description indicates in the "type of test" column; "Validation" (VAT) or "Compatibility" (CPT). + +Although signal units are transmitted and received continuously on level 2, only the signal units which cause and/or indicate the changes of level 2 status are shown in the EXPECTED SIGNAL UNIT SEQUENCE column of each test description. + +## 2.2 Presentation of the test list + +These tests as a whole, aim at a complete validation of the level 2 protocol without redundancies. Each test is described as simply as possible to check precisely each elementary function of the protocol, which is referred in the columns "reference", "title" and "subtitle" of each test description. + +This list is presented in the form of a succession of tests. The presentation order is essentially functional. However, the operator performing these tests may change this order, taking into account some other practical criteria such as: use pre-test conditions to order the list, the end of a given test may be the pre-test condition of another test. + +## 3 Test configuration + +A single link will be used for level 2 tests. Figure 1 shows a single link between SP A and SP B. Test specifications are written to test the level 2 of the SP A. + +![Diagram of test configuration showing SP B and SP A connected by a link. SP B has Tx and Rx ports. SP A has Rx and Tx ports and is labeled '(under test)'. The link is labeled 'Link 1 - 0 (Note)'. A small diagram shows two parallel lines with an oval in the middle representing the link. The text 'T1157160-93' is near SP A.](06da11ab76cacc38bbcd714e437797ea_img.jpg) + +Diagram of test configuration showing SP B and SP A connected by a link. SP B has Tx and Rx ports. SP A has Rx and Tx ports and is labeled '(under test)'. The link is labeled 'Link 1 - 0 (Note)'. A small diagram shows two parallel lines with an oval in the middle representing the link. The text 'T1157160-93' is near SP A. + +NOTE – First digit: linkset number. +Second digit: link number. + +Figure 1/Q.781 – Test configuration of MTP level 2 test configuration 1 + +## 4 Test environment + +See 6.2/Q.780. + +## 5 Test list + +NOTE – Compatibility test items are indicated in this list by an asterisk (\*). + +The abbreviations *PO*, *LPO*, *RPO*, *EM* and *EDA* are used for processor outage, local processor outage, remote processor outage, emergency and expected delay of acknowledgement, respectively. + +### 1 *Link State Control – Expected signal units/orders* (see Figures 8 and 9/Q.703) + +- \* 1.1 Initialisation (Power-up) +- \* 1.2 Timer T2 +- 1.3 Timer T3 +- 1.4 Timer T1 and T4 (Normal) +- \* 1.5 Normal alignment – correct procedure (FISU) +- 1.6 Normal alignment – correct procedure (MSU) +- 1.7 SIO received during normal proving period +- 1.8 Normal alignment with PO set (FISU) +- 1.9 Normal alignment with PO set (MSU) +- 1.10 Normal alignment with PO set and clear +- 1.11 Set RPO when "Aligned not ready" +- 1.12 SIOS received when "Aligned not ready" +- 1.13 SIO received when "Aligned not ready" +- 1.14 Set and clear LPO when "Initial alignment" +- 1.15 Set and clear LPO when "Aligned ready" +- 1.16 Timer T1 in "Aligned not ready" state +- 1.17 No SIO sent during normal proving period +- 1.18 Set and cease emergency prior to "start alignment" +- \* 1.19 Set emergency while in "not aligned state" +- 1.20 Set emergency when "aligned" +- 1.21 Both ends set emergency +- 1.22 Individual end sets emergency +- 1.23 Set emergency during normal proving +- 1.24 No SIO sent during emergency alignment +- \* 1.25 Deactivation during initial alignment +- 1.26 Deactivation during aligned state +- 1.27 Deactivation during aligned not ready +- 1.28 SIO received during link in service +- \* 1.29 Deactivation during link in service +- 1.30 Deactivation during LPO +- 1.31 Deactivation during RPO +- \* 1.32 Deactivation during the proving period + +- 1.33 SIO received instead of FISUs +- 1.34 SIOS received instead of FISUs +- 1.35 SIPO received instead of FISUs +- 2 *Link State Control – Unexpected signal units/orders* (see Figure 8/Q.703) + - 2.1 Unexpected signal units/orders in "Out of service" state + - 2.2 Unexpected signal units/orders in "Not aligned" state + - 2.3 Unexpected signal units/orders in "Aligned" state + - 2.4 Unexpected signal units/orders in "Proving" state + - 2.5 Unexpected signal units/orders in "Aligned ready" state + - 2.6 Unexpected signal units/orders in "Aligned not ready" state + - 2.7 Unexpected signal units/orders in "In service" state + - 2.8 Unexpected signal units/orders in "Processor outage" state +- 3 *Transmission failure* (see Figure 8/Q.703) + - 3.1 Link aligned ready (Break Tx path) + - 3.2 Link aligned ready (Corrupt FIBs – Basic) + - 3.3 Link aligned not ready (Break Tx path) + - 3.4 Link aligned not ready (Corrupt FIBs – Basic) + - \* 3.5 Link in service (Break Tx path) + - 3.6 Link in service (Corrupt FIBs – Basic) + - 3.7 Link in processor outage (Break Tx path) + - 3.8 Link in processor outage (Corrupt FIBs – Basic) +- 4 *Processor Outage Control* (see Figure 10/Q.703) + - 4.1 Set and clear LPO while link in service + - 4.2 RPO during LPO + - 4.3 Clear LPO when "Both processor outage" +- 5 *SU Delimitation, Alignment, Error Detection and Correction* (see Figures 11 and 12/Q.703) + - 5.1 Seven or more "1"s between MSU opening and closing flags + - 5.2 Greater than maximum signal unit length + - 5.3 Below minimum signal unit length + - 5.4 Reception of single and multiple flags between FISUs + - 5.5 Reception of single and multiple flags between MSUs +- 6 *SUERM Check* (see Figure 18/Q.703) + - 6.1 Error rate of 1 in 256 – Link remains in service + - 6.2 Error rate of 1 in 254 – Link into out of service + - 6.3 Consecutive corrupted SUs + - 6.4 Time controlled break of the link + +- 7 *AERM check* (see Figure 17/Q.703) + - 7.1 Error rate below the normal threshold + - 7.2 Error rate at the normal threshold + - 7.3 Error rate above the normal threshold + - 7.4 Error rate at the emergency threshold +- 8 *Transmission and reception control (Basic)* (see Figures 13 and 14/Q.703) + - 8.1 MSU transmission and reception + - 8.2 Negative acknowledgement of MSU + - 8.3 Check RTB full + - 8.4 Single MSU with erroneous FIB + - 8.5 Duplicated FSN + - 8.6 Erroneous retransmission – Single MSU + - 8.7 Erroneous retransmission – Multiple FISUs + - 8.8 Single FISU with corrupt FIB + - 8.9 Single FISU prior to RPO being set + - 8.10 Abnormal BSN – Single MSU + - 8.11 Abnormal BSN – Two consecutive FISUs + - 8.12 Excessive delay of acknowledgement + - 8.13 Level 3 Stop Command +- 9 *Transmission and reception control (PCR)* (see Figures 15 and 16/Q.703) + - \* 9.1 MSU transmission and reception + - 9.2 Priority control + - 9.3 Forced retransmission with the value N1 + - 9.4 Forced retransmission with the value N2 + - 9.5 Forced retransmission cancel + - 9.6 Repetition of forced retransmission + - 9.7 MSU transmission while RPO set + - 9.8 Abnormal BSN – Single MSU + - 9.9 Abnormal BSN – Two MSUs + - 9.10 Unexpected FSN + - 9.11 Excessive delay of acknowledgement + - 9.12 FISU with FSN expected for MSU + - 9.13 Level 3 Stop Command + +### 10 *Congestion Control* (see Figure 19/Q.703) + +10.1 Congestion abatement + +10.2 Timer T7 + +10.3 Timer T6 + +10.4 Congestion and RTB empty + +## **6 Test descriptions** + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------------------|--------------|-------|------------|---|--|----|---|--|------|--|--|--|------|--|--|-------|------|--|---|--|------------|--|--|--|--|---|-------|------|--| +| TEST NUMBER: 1.1 | | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 8; Fig. 12; Fig. 13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Initialization (Power-up) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the No. 7 terminal equipment enters the correct state on power-up | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Line equipment – ON; No. 7 equipment – OFF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 SIOS > : Power ON
< 1 – 0 SIOS
| | | | | SP | B | | SP | A | | Link | | | | Link | | | 1 – 0 | SIOS | | > | | : Power ON | | | | | < | 1 – 0 | SIOS | | +| | SP | B | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | : Power ON | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Check link enters correct state.
  2. 2. At "Power – On" or Initialization the FIB, BIB, FSN, and BSN shall be as follows:
    FIN = BIB = 1 : FSN = BSN = 127 (HEX 7F).
  3. 3. Repeat test in reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------|-------|---------|------|--|--|------|--|------|--|--|------|--|--|-------|------|---|--|--|--|--|--|---|-------|------|--|--|--|--|--|---------|--|--|--|---|-------|-----|--|--|--|--|--|----|--|--|--|---|-------| +| TEST NUMBER: 1.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 8; Fig. 9; Fig. 11; Fig. 13; Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Timer T2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check "Not Aligned" Timer T2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 SIOS >
< 1 – 0 SIOS
: start
< 1 – 0 SIO
T2
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | 1 – 0 | SIOS | > | | | | | | < | 1 – 0 | SIOS | | | | | | : start | | | | < | 1 – 0 | SIO | | | | | | T2 | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | T2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Timer T2 shall be in the range 5 secs to 150 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|-------------------|-------|-------|------|--|------|--|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|--|---|-------|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|-----|--|--|--|--|----|--|--|---|-------|------| +| TEST NUMBER: 1.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 9; Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Timer T3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check "Aligned" Timer T3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
T3
< 1 – 0 SIOS
| | | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | : | start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | < | 1 – 0 | SIN | | | | | T3 | | | < | 1 – 0 | SIOS | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | T3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Timer T3 shall be in the range 1 sec to 1.5 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|---------|------|--|------|--|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|--|--|---------|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|-----|-------|-----|---|--|---------|--|--|--|--|--|--|---|-------|------|--|--|--|--|----|--|--|---|-------|------| +| TEST NUMBER: 1.4 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703 STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Timer T1 and Timer T4 (Normal) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check "Aligned ready" Timer T1 and "Proving period" Timer T4 (Normal) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN > T4 (Pn)
< 1 – 0 FISU
T1
< 1 – 0 SIOS
| | | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | : start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | < | 1 – 0 | SIN | 1 – 0 | SIN | > | | T4 (Pn) | | | | | | | < | 1 – 0 | FISU | | | | | T1 | | | < | 1 – 0 | SIOS | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | T4 (Pn) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | T1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | At 64 kbit/s Timer T4 shall be in the range 7.5 secs to 9.5 secs (nominally 8.2 secs) and Timer T1 shall be in the range 40 secs to 50 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | At 4.8 kbit/s Timer T4 shall be in the range 100 secs to 120 secs (nominally 110 secs) and Timer T1 shall be in the range 500 secs to 600 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------|---------|------|--|------|--|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|--|--|---------|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|------|-------|------|---|--|--| +| TEST NUMBER: 1.5 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703      STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Normal alignment – correct procedure (FISU) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check normal alignment procedure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MESSAGE SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
1 – 0 FISU >
| | | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | : start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | < | 1 – 0 | SIN | 1 – 0 | SIN | > | | | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start normal alignment procedure. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check link aligns and enters "In service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that "In service" state is maintained. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | In VAT only check it is possible to perform a normal alignment procedure in the following cases:
  • – use LSSU in point B with a status field of 8 bits;
  • – use LSSU in point B with a status field of 16 bits.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------|-------|---------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--|--|--|--|--|---------|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|------|--|-------|-----|---|--| +| TEST NUMBER: 1.6 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703 STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Normal alignment – correct procedure (MSU) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check normal alignment procedure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
1 – 0 MSU >
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | | | | | | : start | | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | FISU | | 1 – 0 | MSU | > | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start normal alignment procedure. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check link aligns and enters "In service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that "In service" state is maintained. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-------------------|-------|---------|------|--|--|------|------|--|---|------|--|--|--|--|-------|------|-------|------|--|--|--|--|--|--|--|---------|--|--|---|-------|-----|-------|-----|--|--|--|--|--|---|-------|-----|-------|-----|--|--|----|--|--|--|--|---------|-------|----------------|--|--|--|-------|-----|--|--|--|--|--|---|-------|-----|--|--|--|--|--------|--|--|---|-------|------| +| TEST NUMBER: 1.7 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7, 10.3/Q.703     STD: Fig. 9; Fig. 17 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SIO received during normal proving period | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to the reception of an SIO during the normal proving period | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link < Link
1 – 0 SIOS
1 – 0 SIOS
: start
< 1 – 0 SIO
1 – 0 SIO
< 1 – 0 SIN
1 – 0 SIN T4
Stopped
1 – 0 SIO (one only)
1 – 0 SIN
< 1 – 0 SIN
T4(Pn)
< 1 – 0 FISU
| | | | | SP B | | | SP A | Link | | < | Link | | | | | 1 – 0 | SIOS | 1 – 0 | SIOS | | | | | | | | : start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | | | | | | < | 1 – 0 | SIN | 1 – 0 | SIN | | | T4 | | | | | Stopped | 1 – 0 | SIO (one only) | | | | 1 – 0 | SIN | | | | | | < | 1 – 0 | SIN | | | | | T4(Pn) | | | < | 1 – 0 | FISU | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | < | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | T4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | Stopped | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO (one only) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | T4(Pn) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send an SIO at B during normal proving period. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that new normal period is entered. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------------|---|-------|----|-----------|--|------|----|---|--|--|--|---|-------|--|------|-------|------|--|--|--|--|-----------|--|--|--|--|--|--|---------|--|--|--|---|-------|--|-----|-------|-----|--|--|--|--|--|--|--|--|---|-------|--|-----|-------|-----|--|--|--|--|--|--|--|--|---|-------|--|------|-------|------|--|--|--|--|--|--|--|--|---|-------| +| TEST NUMBER: 1.8 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Normal alignment with PO set (FISU) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response following normal alignment when PO has been set | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

Link SP B Link SP A
< 1 – 0 SIOS
1 – 0 SIOS : set LPO
: start
< 1 – 0 SIO
1 – 0 SIO
< 1 – 0 SIN
1 – 0 SIN
< 1 – 0 SIPO
1 – 0 FISU
< 1 – 0 SIPO
| | | | Link | SP | B | | Link | SP | A | | | | < | 1 – 0 | | SIOS | 1 – 0 | SIOS | | | | | : set LPO | | | | | | | : start | | | | < | 1 – 0 | | SIO | 1 – 0 | SIO | | | | | | | | | < | 1 – 0 | | SIN | 1 – 0 | SIN | | | | | | | | | < | 1 – 0 | | SIPO | 1 – 0 | FISU | | | | | | | | | < | 1 – 0 | +| Link | SP | B | | Link | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that normal alignment is carried out with LPO set at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that SIPO is returned when aligned, and that A stays in "processor outage" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Repeat test with LPO set at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------------|-------------|-----------|-------------|--|-------------|--|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|--|--|-----------|--|--|--|--|---------|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|------|-------|-----|---|--|--|--|--|---|-------|------| +| TEST NUMBER: 1.9 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Normal alignment with PO set (MSU) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response following normal alignment when PO has been set | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: set LPO
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 SIPO
1 – 0 MSU >
< 1 – 0 SIPO
| | | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | : set LPO | | | | | : start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | < | 1 – 0 | SIN | 1 – 0 | SIN | > | | | | | < | 1 – 0 | SIPO | 1 – 0 | MSU | > | | | | | < | 1 – 0 | SIPO | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that normal alignment is carried out with LPO set at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that SIPO is returned when aligned, and that A stays in "processor outage" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Repeat test with LPO set at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|-------------------|-------|------|-------------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|--|------|-------|------|---|--|--|--|--|--|--|--|--|-----------|--|--|--|--|--|-------------|--|--|--|--|--|---------|--|--|---|-------|--|-----|-------|-----|---|--|--|--|--|--|---|-------|--|-----|-------|-----|---|--|--|--|--|--|---|-------|--|------|-------|------|---|--| +| TEST NUMBER: 1.10 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Normal alignment with PO set and clear | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response following normal alignment when PO has been set and cleared | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: set LPO
: clear LPO
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
1 – 0 FISU >
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | | SIOS | 1 – 0 | SIOS | > | | | | | | | | | : set LPO | | | | | | : clear LPO | | | | | | : start | | | < | 1 – 0 | | SIO | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | | SIN | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | | FISU | 1 – 0 | FISU | > | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : clear LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that normal alignment is carried out. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that link aligns and enters "In service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------|---|-------|----|---------|--|--|----|---|------|--|--|--|------|--|--|--|--|--|---|-------|--|------|-------|--|------|---|--|--|--|--|---|---------|--|--|---|---------|--|--|--|--|--|---|-------|--|--|--|---|-------|--|-----|-------|--|-----|---|--|--|--|--|--|--|---|-------|--|-----|-------|--|-----|---|--|--|--|--|--|--|---|-------|--|------|-------|--|------|---|--|--|--| +| TEST NUMBER: 1.11 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set RPO when "Aligned not ready" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response following normal alignment when PO has been set | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service; ability to set PO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: set LPO : set LPO
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 SIPO
1 – 0 SIPO >
| | | | | SP | B | | | SP | A | Link | | | | Link | | | | | | < | 1 – 0 | | SIOS | 1 – 0 | | SIOS | > | | | | | : | set LPO | | | : | set LPO | | | | | | : | start | | | | < | 1 – 0 | | SIO | 1 – 0 | | SIO | > | | | | | | | < | 1 – 0 | | SIN | 1 – 0 | | SIN | > | | | | | | | < | 1 – 0 | | SIPO | 1 – 0 | | SIPO | > | | | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : | set LPO | | | : | set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIPO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set LPO at A and B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Start alignment. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that both LPO and RPO after alignment completes. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-------------------|-------|------|-----------|--|------|------|--|--|--|---|-------|------|--|-------|------|--|--|--|--|--|--|--|--|--|-----------|--|--|--|--|--|---------|--|--|---|-------|-----|--|-------|-----|--|--|--|--|--|--|---|-------|-----|--|-------|-----|--|--|--|--|--|--|---|-------|------|--|-------|----------------|--|--|--|--|--|--|---|-------|------|--| +| TEST NUMBER: 1.12 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SIOS received when "Aligned not ready" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response following normal alignment when PO has been set | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

Link SP B Link SP A
< 1 – 0 SIOS
1 – 0 SIOS
: set LPO
: start
< 1 – 0 SIO
1 – 0 SIO
< 1 – 0 SIN
1 – 0 SIN
< 1 – 0 SIPO
1 – 0 : stop
SIOS
< 1 – 0 SIOS
| | | | Link | SP B | | Link | SP A | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | | | | | | | | | | : set LPO | | | | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | | | < | 1 – 0 | SIPO | | 1 – 0 | : stop
SIOS | | | | | | | < | 1 – 0 | SIOS | | +| Link | SP B | | Link | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | : stop
SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Soon after alignment completes, A enters "Aligned not ready". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Before alignment completes, stop command is given at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that, on reception of SIOS, A enters "Out of service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat test with LPO set at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------|---|-------|-----------|---|--|----|---|--|------|--|--|---|------|--|--|--|--|--|--|-------|------|--|-------|------|--|--|--|--|--|--|--|--|--|--|-----------|--|--|--|--|--|--|---------|--|--|--|--|---|-------|-----|--|-------|-----|--|--|--|--|--|--|--|--|---|-------|-----|--|-------|-----|--|--|--|--|--|--|--|--|---|-------|------|--|-------|-----|--|--|--|--|--|--|--|--|---|-------|------|--| +| TEST NUMBER: 1.13 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SIO received when "Aligned not ready" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response following normal alignment when PO has been set | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link < Link
1 – 0 SIOS
1 – 0 SIOS
: set LPO
: start
< 1 – 0 SIO
1 – 0 SIO
< 1 – 0 SIN
1 – 0 SIN
< 1 – 0 SIPO
1 – 0 SIO
< 1 – 0 SIOS
| | | | | SP | B | | SP | A | | Link | | | < | Link | | | | | | | 1 – 0 | SIOS | | 1 – 0 | SIOS | | | | | | | | | | | : set LPO | | | | | | | : start | | | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | | | | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | | | | | < | 1 – 0 | SIPO | | 1 – 0 | SIO | | | | | | | | | < | 1 – 0 | SIOS | | +| | SP | B | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | < | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Soon after alignment completes, A enters "Aligned not ready". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Before alignment completes at B, SIO is sent to A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that, on reception of SIO, A enters "Out of service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat test with LPO set at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------------|--|-------|-------------|--|--|------|--|------|--|---|--|------|--|--|--|--|--|-------|------|-------|------|---|--|--|--|--|--|--|--|--|---------|--|--|---|--|-------|-----|-------|-----|---|--|--|--|--|--|---|--|-------|-----|--|--|--|--|--|-----------|-------|-----|---|--|--|--|--|--|--|--|--|-------------|--|--|---|--|-------|------|-------|------|---|--|--|--|--|--|---|--| +| TEST NUMBER: 1.14 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set and clear LPO when "Initial alignment" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check normal alignment when PO set and clear during "Initial alignment" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link < Link
1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
: set LPO
1 – 0 SIN >
: clear LPO
< 1 – 0 FISU
1 – 0 FISU >
< 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | < | | Link | | | | | | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | | | : start | | | < | | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | | < | | 1 – 0 | SIN | | | | | | : set LPO | 1 – 0 | SIN | > | | | | | | | | | : clear LPO | | | < | | 1 – 0 | FISU | 1 – 0 | FISU | > | | | | | | < | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | < | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : clear LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set LPO at A during "Initial alignment" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check A remains in "Initial alignment" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Clear LPO before alignment completes at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check A enters "In service" state after normal alignment. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Repeat the test at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-------------------|---|-------|------|---|----------------|--|----|---|--|------|--|--|--|------|--|--|--|--|--|--|---|-------|------|--|--|-------|------|--|---|--|--|--|--|--|--|--|--|--|--|--|---------|--|--|--|---|-------|-----|--|--|-------|-----|--|---|--|--|--|--|--|--|--|---|-------|-----|--|--|-------|-----|--|---|--|--|--|--|--|--|--|---|-------|------|--|--|--|--|--|--|--|--|--|-----------|--|--|--|---|-------|------|--|--|--|--|--|--|--|--|--|----------------|--|--|--|--|--|--|--|-------------|--|--|--|---|-------|------|--|--| +| TEST NUMBER: 1.15 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703   STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set and clear LPO when "Aligned ready" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to LPO when "aligned ready" and to ensure that the aligned ready state resumes when LPO is cleared | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
: set LPO
< 1 – 0 SIPO
: wait 5 secs.
: clear LPO
< 1 – 0 FISU
| | | | | SP | B | | | SP | A | | Link | | | | Link | | | | | | | < | 1 – 0 | SIOS | | | 1 – 0 | SIOS | | > | | | | | | | | | | | | : start | | | | < | 1 – 0 | SIO | | | 1 – 0 | SIO | | > | | | | | | | | < | 1 – 0 | SIN | | | 1 – 0 | SIN | | > | | | | | | | | < | 1 – 0 | FISU | | | | | | | | | | : set LPO | | | | < | 1 – 0 | SIPO | | | | | | | | | | : wait 5 secs. | | | | | | | | : clear LPO | | | | < | 1 – 0 | FISU | | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | : wait 5 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | : clear LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start link at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | At "aligned ready" state set LPO at A.
(Suppress return of FISUs at B to maintain "aligned ready" state.) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Clear LPO at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check A resumes "aligned ready" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------|--|-------|-----------|--|--|------|--|------|--|--|--|------|--|--|--|---|--|-------|------|-------|------|---|--|--|--|--|--|--|--|--|-----------|--|--|--|--|--|---------|--|--|---|--|-------|-----|-------|-----|---|--|--|--|--|--|---|--|-------|-----|-------|-----|---|--|--|--|--|--|---|--|-------|------|--|--|--|--|--|----|--|--|---|--| +| TEST NUMBER: 1.16 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Timer T1 in "Aligned not ready" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the operation of Timer T1 when in the "aligned not ready" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: set LPO
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 SIPO
T1
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | | Link | | | | < | | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | | | : set LPO | | | | | | : start | | | < | | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | | < | | 1 – 0 | SIN | 1 – 0 | SIN | > | | | | | | < | | 1 – 0 | SIPO | | | | | | T1 | | | < | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | T1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set LPO and start link at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check A enters the "aligned not ready" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check A takes the link out of service after time T1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Timer T1 shall be in the range 40 secs to 50 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------------|-------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----|--------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|---------|--|--|---|-------|-----------------|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----|--------|--|--|---|-------|------|--| +| TEST NUMBER: 1.17 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703      STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: No SIO sent during normal proving period | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To ensure that normal alignment still occurs when SIO is omitted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : start
< 1 – 0 SIO not aligned
1 – 0 SIN >
< 1 – 0 SIN
1 – 0 SIN >
T3
T4(Pn)
< 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : start | | | < | 1 – 0 | SIO not aligned | | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | > | | |
T3
T4(Pn)
| | T3 | T4(Pn) | | | < | 1 – 0 | FISU | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO not aligned | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | |
T3
T4(Pn)
| | T3 | T4(Pn) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | T3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | T4(Pn) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check normal alignment occurs with no SIO sent from SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|-------------------|---|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--|------|----|---|--|--|--|---|-------|--|------|-------|------|--|---|--|--|--|--|--|--|--|--|---|--------|--|--|--|--|--|---|----------|--|--|--|--|--|---|-------|--|--|--|---|-------|--|-----|-------|-----|--|---|--|--|--|--|--|--|---|-------|--|-----|-------|-----|--|---|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|---|-------|--|------| +| TEST NUMBER: 1.18 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set and cease emergency prior to "start alignment" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the normal proving period is employed having "emergency" set and cleared | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

Link SP B Link SP A
< 1 – 0 SIOS
1 – 0 SIOS >
: set EM
: clear EM
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
T4(Pn)
< 1 – 0 FISU
| | | | Link | SP | B | | Link | SP | A | | | | < | 1 – 0 | | SIOS | 1 – 0 | SIOS | | > | | | | | | | | | : | set EM | | | | | | : | clear EM | | | | | | : | start | | | | < | 1 – 0 | | SIO | 1 – 0 | SIO | | > | | | | | | | < | 1 – 0 | | SIN | 1 – 0 | SIN | | > | |
T4(Pn)
| | | | | < | 1 – 0 | | FISU | +| Link | SP | B | | Link | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | set EM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | clear EM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | > | |
T4(Pn)
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check emergency set and cleared prior to start of alignment. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check normal proving period is carried out. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------------------|-------|------|----------|--|------|------|--|--|--|---|-------|------|--|-------|------|---|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|----------|--|--|---|-------|-----|--|-------|-----|---|--|--|--------|--|--|---| +| TEST NUMBER: 1.19 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set emergency while in "not aligned state" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test that emergency proving can be set during normal initial alignment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

Link SP B Link SP A
< 1 – 0 SIOS
1 – 0 SIOS > : start
< 1 – 0 SIO
1 – 0 SIO > : set EM
< 1 – 0 SIE
1 – 0 SIN > T4(Pe)
< 1 – 0 FISU
| | | | Link | SP B | | Link | SP A | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | : set EM | | | < | 1 – 0 | SIE | | 1 – 0 | SIN | > | | | T4(Pe) | | | < | +| Link | SP B | | Link | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | : set EM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | T4(Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Check that emergency proving period is used after set EM during normal initial alignment.
  2. 2. The timing of this test is critical, emergency must be set once the start command has been given and before SIO is received (i.e. during Timer T2 operation).
  3. 3. At 64 kbit/s Timer T4 shall be in the range 0.4 sec to 0.6 sec (nominally 0.5 sec).
  4. 4. At 4.8 kbit/s Timer T4 shall be in the range 6 secs to 8 secs (nominally 7 secs).
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|-------------------|-------|------|----------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|--|--|--|--|--|----------|--|--|---|-------|-----|--|-------|-----|---|--|--|--------|--|--|---|-------|------|--| +| TEST NUMBER: 1.20 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703      STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set emergency when "aligned" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test that emergency proving period is used when emergency set prior to receiving SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
: set EM
< 1 – 0 SIE
1 – 0 SIN > T4(Pe)
< 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | | | | | | : set EM | | | < | 1 – 0 | SIE | | 1 – 0 | SIN | > | | | T4(Pe) | | | < | 1 – 0 | FISU | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : set EM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | T4(Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that emergency proving period is used after SIE sent during "aligned" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | The timing of this test is critical. Emergency must be set once SIN has been sent but before Timer T3 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------------|-------|------|----------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|----------|--|--|--|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|--|--|--|--------|--|--|---|-------| +| TEST NUMBER: 1.21 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703      STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Both ends set emergency | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the emergency alignment procedure and Timer T4(Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : set EM
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIE
1 – 0 SIE >
T4(Pe)
< 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : set EM | | | | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIE | | 1 – 0 | SIE | > | | | | | | | | | T4(Pe) | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : set EM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIE | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | T4(Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check correct emergency alignment procedure is performed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------|---------|--|------|------|--|--|--|---|-------|--|------|-------|------|---|--|--|--|-------|-----|---|--|--|--|--|--|--|--|--|---------|--|--|---|-------|--|-----|-------|-----|---|--|--|--|--|--|---|-------|--|-----|--|--|--|--|--|--------|--|--|---|-------|--|------| +| TEST NUMBER: 1.22 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Individual end sets emergency | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check emergency alignment procedure, Emergency set at the other end | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

Link SP B Link SP A
< 1 – 0 SIOS
1 – 0 SIOS >
1 – 0 SIO >
: start
< 1 – 0 SIO
1 – 0 SIE >
< 1 – 0 SIN
T4(Pe)
< 1 – 0 FISU
| | | | Link | SP B | | Link | SP A | | | | < | 1 – 0 | | SIOS | 1 – 0 | SIOS | > | | | | 1 – 0 | SIO | > | | | | | | | | | : start | | | < | 1 – 0 | | SIO | 1 – 0 | SIE | > | | | | | | < | 1 – 0 | | SIN | | | | | | T4(Pe) | | | < | 1 – 0 | | FISU | +| Link | SP B | | Link | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIE | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | T4(Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1.
2.
3. | Emergency alignment set at B.
Start alignment at A.
Check that alignment occurs with the emergency proving period. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------|---|-------|----|--------|--|--|----|---|------|--|--|--|------|--|--|--|--|--|---|-------|--|------|-------|------|--|---|--|--|--|--|--|--|--|--|---|-------|--|--|--|---|-------|--|-----|-------|-----|--|---|--|--|--|--|--|--|---|-------|--|-----|-------|-----|--|---|--|--|--|--|--|--|--|--|---|--------|--|--|--|---|-------|--|-----|-------|-----|--|---|--|--|--|--|--|--|--|--|--|--------|--|--|--|---|-------|--|------| +| TEST NUMBER: 1.23 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703   STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set emergency during normal proving | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test that setting emergency during normal proving stops normal proving and starts the emergency proving | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
: set EM
< 1 – 0 SIE
1 – 0 SIN >
T4(Pe)
< 1 – 0 FISU
| | | | | SP | B | | | SP | A | Link | | | | Link | | | | | | < | 1 – 0 | | SIOS | 1 – 0 | SIOS | | > | | | | | | | | | : | start | | | | < | 1 – 0 | | SIO | 1 – 0 | SIO | | > | | | | | | | < | 1 – 0 | | SIN | 1 – 0 | SIN | | > | | | | | | | | | : | set EM | | | | < | 1 – 0 | | SIE | 1 – 0 | SIN | | > | | | | | | | | | | T4(Pe) | | | | < | 1 – 0 | | FISU | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | set EM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | T4(Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set emergency during normal proving period at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check A sends SIE. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Repeat test in reverse direction. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------|-------|------------------------------------------------------------------------------|----------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|----------|--|--|--|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|--|--|--|--|------------------------------------------------------------------------------|--|--|--|---|-------| +| TEST NUMBER: 1.24 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703      STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: No SIO sent during emergency alignment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To ensure that emergency alignment still occurs when SIE is received following SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : set EM
: start
< 1 – 0 SIO
1 – 0 SIE >
< 1 – 0 SIE
T4(Pe)
< 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : set EM | | | | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIE | > | | | | | | < | 1 – 0 | SIE | | | | | | T4(Pe) | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : set EM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIE | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | T4(Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set emergency and start link at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | A receives SIE after sending SIO. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that link aligns OK after emergency proving. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|------------------------|---|-------|------|--------------|--|----|---|--|------|--|--|--|------|--|--|--|--|--|---|-------|------|--|-------|------|--|---|--|--|--|--|--|--|--|--|---|-------|--|--|--|---|-------|-----|--|--|--|--|--|--|---|--------------|--|--|--|--|--|---|------|--|--|--|---|-------|------|--| +| TEST NUMBER: 1.25 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Deactivation during initial alignment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to the receipt of the stop command while in the initial alignment state (initial alignment is Not Aligned State) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
: wait 5 secs.
: stop
< 1 – 0 SIOS
| | | | | SP | B | | SP | A | | Link | | | | Link | | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | | > | | | | | | | | | : | start | | | | < | 1 – 0 | SIO | | | | | | | : | wait 5 secs. | | | | | | : | stop | | | | < | 1 – 0 | SIOS | | +| | SP | B | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | wait 5 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that alignment ceases after Stop command given. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | The stop command must be issued before timer T2 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Timer T2 shall be in the range 5 secs to 150 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-------------------|---|-------|----|------|---------|--|----|---|--|------|--|--|--|------|--|--|--|--|--|--|---|-------|--|------|--|-------|--|------|--|--|--|--|---------|--|--|--|---|-------|--|-----|--|-------|--|-----|--|--|--|--|--|--|--|--|---|-------|--|-----|--|--|--|--|--|--|--|--|--------|--|--|--|---|-------|--|------|--| +| TEST NUMBER: 1.26 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703 STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Deactivation during aligned state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to the receipt of the stop command while in the initial alignment state (initial alignment is aligned state) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS : start
< 1 – 0 SIO
1 – 0 SIO
< 1 – 0 SIN
: stop
< 1 – 0 SIOS
| | | | | SP | B | | | SP | A | | Link | | | | Link | | | | | | | < | 1 – 0 | | SIOS | | 1 – 0 | | SIOS | | | | | : start | | | | < | 1 – 0 | | SIO | | 1 – 0 | | SIO | | | | | | | | | < | 1 – 0 | | SIN | | | | | | | | | : stop | | | | < | 1 – 0 | | SIOS | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIOS | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that alignment ceases after STOP command given. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | The stop command must be issued before timer T3 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Timer T3 shall be in the range 1 sec to 1.5 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------------------|-------|------|-----------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|-----------|--|--|--|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|------|--|--|--|--|--|--|--------|--|--|---|-------|------|--| +| TEST NUMBER: 1.27 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Deactivation during aligned not ready | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response following normal alignment when PO has been set | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : set LPO
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 SIPO
: stop
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : set LPO | | | | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | SIPO | | | | | | | : stop | | | < | 1 – 0 | SIOS | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Soon after alignment completes, A enters "Aligned not ready".
  2. 2. Before alignment completes at B, stop command is given at A.
  3. 3. Check that A enters "Out of service" state.
  4. 4. Repeat test with LPO set at B.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------|--|-------|----|------|--|--|----|---|------|--|--|--|------|--|--|-------|------|--|--|--|--|--|--|--|--|--|-------|--|------|-------|-----|--|--|--|--|--|--|--|--|--|-------| +| TEST NUMBER: 1.28 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 8; Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SIO received during link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the deactivation of a signalling link from the "In Service" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 FISU
1 – 0 FISU
1 – 0 SIO
1 – 0 SIOS
| | | | | SP | B | | | SP | A | Link | | | | Link | | | 1 – 0 | FISU | | | | | | | | | | 1 – 0 | | FISU | 1 – 0 | SIO | | | | | | | | | | 1 – 0 | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | SIO is sent to A during link in service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that an "in service" link can be taken out of service at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------|-------|------|------|--|--|------|--|------|--|--|------|--|--|-------|------|--|--|--|--|--|--|--|-------|------|--|--|--------|--|--|--|--|-------|------|--|--|--|--|--|--|--|-------| +| TEST NUMBER: 1.29 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 8; Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Deactivation during link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the deactivation of a signalling link from the "In Service" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 FISU
1 – 0 FISU
: stop
1 – 0 SIOS
1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | 1 – 0 | FISU | | | | | | | | 1 – 0 | FISU | | | : stop | | | | | 1 – 0 | SIOS | | | | | | | | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that an "In service" link can be taken out of service by command at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Repeat test, command given at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-------------------|-------|------|-----------|--|--|------|--|------|--|--|------|--|--|--|--|--|-------|------|--|-------|------|--|--|--|-----------|--|--|--|-------|------|--|-------|------|--|--|--|--------|--|--|--|-------| +| TEST NUMBER: 1.30 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703      STD: Fig. 10 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Deactivation during LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to the stop command during LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 FISU
1 – 0 FISU : set LPO
1 – 0 SIPO
1 – 0 FISU : stop
1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | | 1 – 0 | FISU | | 1 – 0 | FISU | | | | : set LPO | | | | 1 – 0 | SIPO | | 1 – 0 | FISU | | | | : stop | | | | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | SIPO sent from A, stop command given at A, check link enters out of service state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Repeat test, SIPO sent from B, stop command at B, check link enters out of service state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-------------------|-------|------|--------|--|--|------|--|------|--|--|------|--|--|-------|------|---|--|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--------|--|--|---|-------|------|--| +| TEST NUMBER: 1.31 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7and 8/Q.703      STD: Fig. 10 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Deactivation during RPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to the stop command during RPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
SP B SP A
Link Link
1 – 0 FISU →
← 1 – 0 FISU
1 – 0 SIPO → : stop
← 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | 1 – 0 | FISU | → | | | | | | ← | 1 – 0 | FISU | | 1 – 0 | SIPO | → | | | : stop | | | ← | 1 – 0 | SIOS | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIPO | → | | | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ← | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | SIPO received at A, stop command given at A, check link enters out of service state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Repeat test, SIPO received at B, stop command given at B, check link enters out of service state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|------------------------|---|-------|------|---|-------|--|----|---|--|------|--|--|--|------|--|--|--|--|--|--|---|-------|------|--|--|-------|------|--|---|--|--|--|--|--|--|--|--|--|--|---|-------|--|--|--|---|-------|-----|--|--|-------|-----|--|---|--|--|--|--|--|--|--|---|-------|-----|--|--|-------|-----|--|---|--|--|--|--|--|---|------|--|--|--|--|--|-------|------|--|---|--|--|--|--|--|--|--|---|-------|------| +| TEST NUMBER: 1.32 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7, 10.3/Q.703   STD: Fig. 8; Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Deactivation during the proving period | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to the receipt of SIOS during the proving period | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
: stop
1 – 0 SIOS >
< 1 – 0 SIOS
| | | | | SP | B | | | SP | A | | Link | | | | Link | | | | | | | < | 1 – 0 | SIOS | | | 1 – 0 | SIOS | | > | | | | | | | | | | | : | start | | | | < | 1 – 0 | SIO | | | 1 – 0 | SIO | | > | | | | | | | | < | 1 – 0 | SIN | | | 1 – 0 | SIN | | > | | | | | | : | stop | | | | | | 1 – 0 | SIOS | | > | | | | | | | | < | 1 – 0 | SIOS | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : | stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check link enters out of service state when SIOS is received at A during the proving period. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Repeat test, SIOS received at B during proving period. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------------|---|-------|----|-------|--|----|---|--|------|--|--|--|------|--|--|--|--|--|---|-------|--|------|-------|--|------|---|--|--|--|--|--|--|---|-------|---|-------|-------|--|-----|---|-------|--|-----|--|--|--|---|-------|--|-----|-------|--|-----|---|--|--|--|--|--|--|---|-------|--|------|-------|--|-----|---|--|--|--|--|--|--|---|-------| +| TEST NUMBER: 1.33 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SIO received instead of FISUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to the receipt of SIO instead of FISUs in the aligned ready state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
< 1 – 0 : start
1 – 0 SIO > 1 – 0 SIO
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
1 – 0 SIO >
< 1 – 0 SIOS
| | | | | SP | B | | SP | A | | Link | | | | Link | | | | | | < | 1 – 0 | | SIOS | 1 – 0 | | SIOS | > | | | | | | | < | 1 – 0 | : | start | 1 – 0 | | SIO | > | 1 – 0 | | SIO | | | | < | 1 – 0 | | SIN | 1 – 0 | | SIN | > | | | | | | | < | 1 – 0 | | FISU | 1 – 0 | | SIO | > | | | | | | | < | 1 – 0 | +| | SP | B | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIO | > | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check link enters out of service state when SIO is received at A instead of FISUs in the aligned ready state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|-------------------|-------|------|---------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|------|--|--|--------|--|--|--|--|-------|------|---|--|--|--|--|--|---|-------| +| TEST NUMBER: 1.34 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703 STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SIOS received instead of FISUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to the receipt of SIOS instead of FISUs in the aligned ready state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
: stop
1 – 0 SIOS >
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | FISU | | | : stop | | | | | 1 – 0 | SIOS | > | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check link enters out of service state when SIOS is received at A instead of FISUs in the aligned ready state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|-------------------|---|-------|----|---------|--|--|----|---|------|--|--|--|------|--|--|--|--|--|---|-------|--|------|-------|--|------|---|--|--|---------|--|--|--|---|-------|--|-----|-------|--|-----|---|--|--|--|--|--|--|---|-------|--|-----|-------|--|-----|---|--|--|--|--|--|--|---|-------|--|------|--|--|-----------|--|--|--|--|-------|--|------|---|--|--|--|--|--|--|---|-------|--|------| +| TEST NUMBER: 1.35 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 8/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Expected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SIPO received instead of FISUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to the receipt of SIPO instead of FISUs in the aligned ready state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
: set LPO
1 – 0 SIPO >
< 1 – 0 FISU
| | | | | SP | B | | | SP | A | Link | | | | Link | | | | | | < | 1 – 0 | | SIOS | 1 – 0 | | SIOS | > | | | : start | | | | < | 1 – 0 | | SIO | 1 – 0 | | SIO | > | | | | | | | < | 1 – 0 | | SIN | 1 – 0 | | SIN | > | | | | | | | < | 1 – 0 | | FISU | | | : set LPO | | | | | 1 – 0 | | SIPO | > | | | | | | | < | 1 – 0 | | FISU | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIOS | > | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | SIPO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check link enters processor outage state when SIPO is received at A instead of FISUs in the aligned ready state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|----------------|------|--|--|------|--|------|--|--|------|--|--|--|--|--|-------|------|--|-------|------|--|--|--|--|--|-----|--|--|--|--|--|--|--|-------|----------------|--|-------|-----|--|-------|-----|--|--|--|--|--|--|--|-------|-----|--|-------|-----|--|--|--|--|--|--|--|-------|------|--|-------|------|--|--|--|--|--|--|--| +| TEST NUMBER: 2.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "Out of service" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 SIOS
1 – 0 SIOS
xxx
1 – 0 yyy
: start
1 – 0 SIO 1 – 0 SIO
1 – 0 SIN 1 – 0 SIN
1 – 0 FISU 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | | Link | | | | | | 1 – 0 | SIOS | | 1 – 0 | SIOS | | | | | | xxx | | | | | | | | 1 – 0 | yyy
: start | | 1 – 0 | SIO | | 1 – 0 | SIO | | | | | | | | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | | | | 1 – 0 | FISU | | 1 – 0 | FISU | | | | | | | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | xxx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | yyy
: start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that the unexpected signal units xxx received from B are ignored without impact on the system. xxx are successively SIO, SIN, SIE, SIPO, SIB, aberrant LSSU (non-existing status, one and two octets), FISU and MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the unexpected orders yyy = Stop from level 3 are ignored without impact on system (if applicable). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|---------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--|--|--|--|--|---------|--|--|--|---|-------|-----|--|--|-----|---|--|--|--|--|--|--|--|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--| +| TEST NUMBER: 2.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703      STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "Not aligned" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
xxx >
yyy
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
1 – 0 FISU >
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | | | | | | : start | | | | < | 1 – 0 | SIO | | | xxx | > | | | | | | | | yyy | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | > | | | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | xxx | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | yyy | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that the unexpected signal units xxx received from B are ignored without impact on the system.
xxx are successively SIOS, SIPO, SIB, aberrant LSSU, FISU and MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the unexpected orders yyy received from level 3 are ignored without impact on the system.
yyy are successively clear EM and start (if applicable). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------|---------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|--|-----|---|--|--|-----|-------|-----|---|--|--|--|--|--|---|-------|------|--|-------|------|---|--| +| TEST NUMBER: 2.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703   STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "Aligned" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
xxx > yyy
1 – 0 SIN >
< 1 – 0 FISU
1 – 0 FISU >
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | | xxx | > | | | yyy | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | > | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | xxx | > | | | yyy | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that the unexpected signal units xxx received from B are ignored without impact on the system. xxx are successively SIO, SIPO, SIB, aberrant LSSU, FISU and MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the unexpected orders yyy received from level 3 are ignored without impact on the system. yyy are successively clear EM and start (if applicable). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------|-------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|--|------|-------|------|---|--|--|--|--|--|--|--|---|-------|--|--|---|-------|--|-----|-------|-----|---|--|--|--|--|--|---|-------|--|-----|-------|-----|---|--|--|--|--|-----|---|--|--|--|--|--|--|--|--|-----|--|--|---|-------|--|------|-------|------|---|--|--|--| +| TEST NUMBER: 2.4 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703     STD: Fig. 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "Proving" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
xxx >
yyy
< 1 – 0 FISU
1 – 0 FISU >
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | | SIOS | 1 – 0 | SIOS | > | | | | | | | | : | start | | | < | 1 – 0 | | SIO | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | | SIN | 1 – 0 | SIN | > | | | | | xxx | > | | | | | | | | | yyy | | | < | 1 – 0 | | FISU | 1 – 0 | FISU | > | | | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : | start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | xxx | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | yyy | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that the unexpected signal units xxx received from B are ignored without impact on the system. xxx are successively SIPO, SIB, aberrant LSSU, FISU and MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the unexpected orders yyy received from level 3 are ignored without impact on the system. yyy are successively clear EM and start (if applicable).
NOTE – The reception of SIB in "Initial alignment" state may possibly cause link failure after transferring to "In service" state because of the T6 expiration. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------|---------|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--|--|--|---|-------|-----|---------|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|------|--|--|-----|---|--|--|-----|-------|------|---|--|--|--| +| TEST NUMBER: 2.5 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "Aligned ready" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:
SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
< 1 – 0 SIO : start
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
xxx > yyy
1 – 0 FISU >
| | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | | | | < | 1 – 0 | SIO | : start | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | FISU | | | xxx | > | | | yyy | 1 – 0 | FISU | > | | | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | xxx | > | | | yyy | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1.

2. |

Check that the unexpected signal units xxx received from B are ignored without impact on the system. xxx are successively SIB and aberrant LSSU.

Check that the unexpected orders yyy received from level 3 are ignored without impact on the system. yyy are successively set EM, clear EM, clear LPO and start (if applicable).

NOTE – The reception of SIB in "Aligned ready" state may possibly cause link failure after transferring to "In service" state because of the T6 expiration.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|-----------|------|--|------|--|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|--|--|-----------|--|--|--|--|---------|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|------|--|-----|---|--|--|--|--|--|--|-----|-------|------|---|--|--|--|--|---|-------|------| +| TEST NUMBER: 2.6 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "Aligned not ready" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: set LPO
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 SIPO
xxx >
yyy
1 – 0 FISU >
< 1 – 0 SIPO
| | | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | : set LPO | | | | | : start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | < | 1 – 0 | SIN | 1 – 0 | SIN | > | | | | | < | 1 – 0 | SIPO | | xxx | > | | | | | | | yyy | 1 – 0 | FISU | > | | | | | < | 1 – 0 | SIPO | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | xxx | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | yyy | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that the unexpected signal units xxx received from B are ignored without impact on the system. xxx are successively SIB and aberrant LSSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the unexpected orders yyy received from level 3 are ignored without impact on the system. yyy are successively set EM, clear EM, clear LPO and start (if applicable). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|---------------|---|--|--|--|--|--|--|-----|--|--|---|-------|------|-------|------|---|--|--| +| TEST NUMBER: 2.7 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "In service" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
aberrant LSSU >
yyy
< 1 – 0 FISU
1 – 0 FISU >
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | | aberrant LSSU | > | | | | | | | yyy | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | aberrant LSSU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | yyy | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that an aberrant LSSU received from B is ignored without impact on the system. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the unexpected orders yyy received from level 3 are ignored without impact on the system. yyy are successively set EM, clear EM, clear LPO and start (if applicable). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------|----|---------|--|--|----|---|------|--|--|--|------|--|--|--|--|--|--|--|---|---------|--|--|--|---|-------|--|------|--|--|-----|--|--|--|--|--|--|--|--|--|--|-----|-------|--|------|--|--|--|--| +| TEST NUMBER: 2.8 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clauses 7 and 11/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Link State Control – Unexpected signal units/orders | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected signal units/orders in "Processor outage" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the unexpected signal units/orders are ignored | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
: set LPO
< 1 – 0 SIPO
xxx
yyy
1 – 0 FISU
| | | | | SP | B | | | SP | A | Link | | | | Link | | | | | | | | : | set LPO | | | | < | 1 – 0 | | SIPO | | | xxx | | | | | | | | | | | yyy | 1 – 0 | | FISU | | | | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : | set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | xxx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | yyy | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that the unexpected signal units xxx received from B are ignored without impact on the system. xxx are successively SIB and aberrant LSSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that the unexpected orders yyy received from level 3 are ignored without impact on the system. yyy are successively set EM, clear EM and start (if applicable). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------|------|---------|--|----|---|--|------|--|--|--|------|--|--|--|--|--|---|-------|------|--|-------|------|--|---|--|--|---------|--|--|--|---|-------|-----|--|-------|-----|--|---|--|--|--|--|--|--|---|-------|-----|--|-------|-----|--|---|--|--|--|--|--|--|---|-------|------|--|--|--|------------|--|--|--|--|--|--|--|---|-------|------|--| +| TEST NUMBER: 3.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 4, 10.2/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link aligned ready (Break Tx path) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to a transmission failure – detected by SUERM – when in "Aligned ready" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS > : start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
< 1 – 0 FISU
: break Tx
< 1 – 0 SIOS
| | | | | SP | B | | SP | A | | Link | | | | Link | | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | | > | | | : start | | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | | > | | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | | > | | | | | | | < | 1 – 0 | FISU | | | | : break Tx | | | | | | | | < | 1 – 0 | SIOS | | +| | SP | B | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | > | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | : break Tx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Break Tx path at B when in "Aligned ready" state, check that the SUERM detects the failure and the link is taken out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Repeat test, break Tx at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|---------------------------|--|-------|------|--|--|------|--|------|--|--|--|------|--|--|--|--------------------------|--|-------|------|-------|--------------------------------------|---------------------------|--|--|--|-------|--------------------------------------|---------------------------|--|--|--|--|--|--------------------------|--| +| TEST NUMBER: 3.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link aligned ready (Corrupt FIBs – Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to a link failure after corruption of two FIBs – detected by reception control – while in Aligned ready State | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Aligned ready | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link

Image: Left arrow

1 – 0 FISU
1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)

Image: Right arrow

1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)

Image: Right arrow

Image: Left arrow

1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | | Link | | | |

Image: Left arrow

| | 1 – 0 | FISU | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) |

Image: Right arrow

| | | | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) |

Image: Right arrow

| | | | | |

Image: Left arrow

| | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | |

Image: Left arrow

| | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) |

Image: Right arrow

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) |

Image: Right arrow

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | |

Image: Left arrow

| | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that receipt of two FISUs at A with corrupt FIB's at link aligned ready state causes the link to be taken out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------|-------|------|-----------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|-----------|--|--|--|--|--|---------|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|-----|--|-------|-----|---|--|--|--|--|--|---|-------|------|--|--|------------|--|--|--|--|--|--|---|-------|------|--| +| TEST NUMBER: 3.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 8, 10.3/Q.703   STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link aligned not ready (Break Tx path) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to a break in the transmission path – detected by SUERM – in "Aligned not ready" state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP BSP A
LinkLink
< 1 – 0SIOS
1 – 0SIOS >: set LPO
: start
< 1 – 0SIO
1 – 0SIO >
< 1 – 0SIN
1 – 0SIN >
< 1 – 0SIPO
: break Tx
< 1 – 0SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | > | | | : set LPO | | | | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | > | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | > | | | | | | < | 1 – 0 | SIPO | | | : break Tx | | | | | | | < | 1 – 0 | SIOS | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : break Tx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set LPO at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Start link alignment at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | In link aligned not ready state break Tx at B and check link is taken out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat test for B with break in Tx at A, check link is taken out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | The Tx path must be broken before Timer T1 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------|-------|------|-----------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|--|--|--|-----------|--|--|--|--|--|---------|--|--|---|-------|-----|--|-------|-----|--|--|--|--|--|--|---|-------|-----|--|-------|-----|--|--|--|--|--|--|---|-------|------|--|-------|--------------------------------------|--|--|--|--|-------|--------------------------------------|--|--|--|--|--|--|---|-------| +| TEST NUMBER: 3.4 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 8, 5.3/Q.703   STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link aligned not ready (Corrupt FIBs – Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to a link failure after corruption of two FIBs – detected by reception control – while in "Aligned not ready" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS : set LPO
: start
< 1 – 0 SIO
1 – 0 SIO
< 1 – 0 SIN
1 – 0 SIN
< 1 – 0 SIPO
1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)
1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | | | | : set LPO | | | | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | | | < | 1 – 0 | SIPO | | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | | | | | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set LPO at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Start link alignment at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Send two corrupt FISUs (corrupt FIBs) on link aligned not ready. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check link is taken out of service at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|------------------------|-------|------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--|--|------------|--|--|--|--|--|--|---|--| +| TEST NUMBER: 3.5 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 4, 10.2/Q.703   STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link in service (Break Tx path) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to a transmission failure when the link is "In service" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
: break Tx
< SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | > | | | | | : break Tx | | | | | | | < | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : break Tx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Break Tx at B, check SIOS returned from A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Repeat test, break at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|--------------------------|---|--|--|--|-------|--------------------------------------|---|--|--|--|-------|--------------------------------------|---|--|--|--|--|--|---|-------| +| TEST NUMBER: 3.6 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703      STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link in service (Corrupt FIBs – Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to a link failure after corruption of two FIBS – detected by reception control – while "In service" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU
(FIB + FSN = FF)
>
1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)
>
1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)
>
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU
(FIB + FSN = FF) | > | | | | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that receipt of two FISUs at A with corrupt FIBs at link in service state causes the link to be taken out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|-----------|------|--|------|--|------|--|--|------|--|--|--|--|-------|------|-------|------|--|--|--|--|--|--|--|-----------|--|--|--|-------|------|--|------------|--|--|--|--|--|--|-------|------| +| TEST NUMBER: 3.7 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 8, 10.2/Q.703     STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link in processor outage (Break Tx path) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to a transmission failure when the link is "Processor outage" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 FISU
1 – 0 FISU
: set LPO
1 – 0 SIPO
: break Tx
1 – 0 SIOS








| | | | | SP B | | SP A | | Link | | | Link | | | | | 1 – 0 | FISU | 1 – 0 | FISU | | | | | | | | : set LPO | | | | 1 – 0 | SIPO | | : break Tx | | | | | | | 1 – 0 | SIOS | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : break Tx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Break Tx path at B when in "Processor outage" state, check that the SUERM detects the failure and the link is taken out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Repeat test, break Tx at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------|-----------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--|--|--|--|--|--|-----------|--|--|---|-------|------|--|-------|--------------------------------------|---|--|--|--|-------|--------------------------------------|---|--|--|--|--|--|---|-------| +| TEST NUMBER: 3.8 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 8, 5.3/Q.703 STD: Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Link in processor outage (Corrupt FIBs – Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the response to a link failure after corruption of two FIBs – detected by reception control – while in "Processor outage" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
: set LPO
< 1 – 0 SIPO
1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)
>
1 – 0 FISU corrupt FIB
(FIB + FSN = 7F)
>
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | > | | | | | | | | | : set LPO | | | < | 1 – 0 | SIPO | | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU corrupt FIB
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Check that receipt of two FISUs at A with corrupt FIBs on processor outage state causes the link to be taken out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|--------------------------------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------------------------------|--|-------|------------------------------|---|--|--|--|--|--|----------|--|--|--|--|--|---|-------|--------------------------------|--|--|--|---|-------|--------------------------------|--|--|--|--|--|-----------|--|-------|---------------------------|---|--|--|--|--|--|---|-------|-----------------------------|--|-------|----------------------------|---|--|--|--|--|--|--|--|-------------|--|--|--|---|-------|-------------------------------|--| +| TEST NUMBER: 4.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 8/Q.703      STD: Fig. 10 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Processor outage control | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Set and clear LPO while link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the ability to perform correctly when LPO is set and recovered | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
accepted
< 1 – 0 MSU (1)
(FSN = 0, BSN = 7F)
< 1 – 0 MSU (2)
(FSN = 1, BSN = 7F)
: set LPO
1 – 0 MSU
(FSN = 0, BSN = 0)
>
< 1 – 0 SIPO
(FSN = 1, BSN = 7F)
1 – 0 FISU
(FSN = 0, BSN = 0)
>
: clear LPO
< 1 – 0 MSU (3)
(FSN = 1, BSN = x)
| | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | accepted | | | | | | < | 1 – 0 | MSU (1)
(FSN = 0, BSN = 7F) | | | | < | 1 – 0 | MSU (2)
(FSN = 1, BSN = 7F) | | | | | | : set LPO | | 1 – 0 | MSU
(FSN = 0, BSN = 0) | > | | | | | | < | 1 – 0 | SIPO
(FSN = 1, BSN = 7F) | | 1 – 0 | FISU
(FSN = 0, BSN = 0) | > | | | | | | | | : clear LPO | | | | < | 1 – 0 | MSU (3)
(FSN = 1, BSN = x) | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | accepted | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU (1)
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU (2)
(FSN = 1, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 0) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO
(FSN = 1, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 0, BSN = 0) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : clear LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU (3)
(FSN = 1, BSN = x) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set LPO at A while link in service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that MSU from B is discarded. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Clear LPO at A after at least 1.2 s. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that "old" messages are flushed from level 2 buffers and not transmitted on the link. Check that new MSUs are sent correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-------------------|-------|-----------|------|--|------|--|------|--|--|------|--|--|--|--|--|-----------|--|--|---|-------|------|-------|------|---|--|--|--|--|---|-------|------|--|-------------|--|--|--|-------|-----|---|--|--|--|--|---|-------|------| +| TEST NUMBER: 4.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 8/Q.703     STD: Fig. 10 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Processor outage control | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: RPO during LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to RPO is set and cleared when "LPO" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service. LPO set at B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
: set LPO
< 1 – 0 SIPO
1 – 0 SIPO >
< 1 – 0 SIPO
: clear LPO
1 – 0 TSR >
< 1 – 0 SIPO
| | | | | SP B | | SP A | | Link | | | Link | | | | | | : set LPO | | | < | 1 – 0 | SIPO | 1 – 0 | SIPO | > | | | | | < | 1 – 0 | SIPO | | : clear LPO | | | | 1 – 0 | TSR | > | | | | | < | 1 – 0 | SIPO | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : set LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIPO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : clear LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | TSR | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Set LPO at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Clear LPO at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check is SIPO sent from A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-------------------|-------|-------------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--|--|--|--|--|-------------|--|--|--|---|-------|------|--|--|-------------|--|--|--|--|-------|------|---|--|--|--|--|--|---|-------|------|--| +| TEST NUMBER: 4.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 8/Q.703     STD: Fig. 10 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Processor outage control | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Clear LPO when "Both processor outage" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to LPO, RPO recovered when "Both processor outage" | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: LPO set at A and B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIPO
1 – 0 SIPO >
: clear LPO
< 1 – 0 FISU
: clear LPO
1 – 0 FISU >
< 1 – 0 FISU










| | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIPO | | 1 – 0 | SIPO | > | | | | | | | | : clear LPO | | | | < | 1 – 0 | FISU | | | : clear LPO | | | | | 1 – 0 | FISU | > | | | | | | < | 1 – 0 | FISU | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIPO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : clear LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : clear LPO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Clear LPO at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Clear LPO at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check is FISU sent from A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|-------------------|---|-------|--------------------------------------------------------------------|----|---------------------------------------------------------------------------|----|--------------------------------------------------------------------------------------------------------------------|--|------|--|--|--|------|--|--|--|--|--|---|-------|------|--|-------|------|--|---|--|--|--|-------|--------------------------------------------------------------------------------|--|---|--|--|--|--|--|--|---|-------|-------------------------|--|-------|------|--|---|--|--|--| +| TEST NUMBER: 5.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 4.1/Q.703     STD: Fig. 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: SU delimitation, alignment, error detection and correction | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Seven or more '1's between MSU opening and closing flags | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the signal unit delimitation, alignment, and error detection action on receipt of an MSU containing seven or more consecutive '1's | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
1 – 0 corrupt MSU
(FIB + FSN = 80)
(containing seven or more consecutive '1's)
>
< 1 – 0 FISU
(BSN unchanged)
1 – 0 FISU >
| | | | | SP | B | | SP | A | | Link | | | | Link | | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | | > | | | | 1 – 0 | corrupt MSU
(FIB + FSN = 80)
(containing seven or more consecutive '1's) | | > | | | | | | | < | 1 – 0 | FISU
(BSN unchanged) | | 1 – 0 | FISU | | > | | | | +| | SP | B | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt MSU
(FIB + FSN = 80)
(containing seven or more consecutive '1's) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU
(BSN unchanged) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
1. Send a corrupt MSU at B containing seven or more consecutive '1's.
2. Check that A discards the signal unit, and goes into octet counting mode.
3. On reception of a correct FISU, check that A leaves the octet counting mode and remains in the "in service" state.
| | | | 1. | Send a corrupt MSU at B containing seven or more consecutive '1's. | 2. | Check that A discards the signal unit, and goes into octet counting mode. | 3. | On reception of a correct FISU, check that A leaves the octet counting mode and remains in the "in service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send a corrupt MSU at B containing seven or more consecutive '1's. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A discards the signal unit, and goes into octet counting mode. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | On reception of a correct FISU, check that A leaves the octet counting mode and remains in the "in service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|-------------------|--|-------|-------------------------|--|--|------|--|------|--|--|--|------|--|--|--|---|--|-------|------|-------|------|---|--|--|--|-------|---------------------------------------------------------------------------|---|--|--|--|--|--|---|--|-------|-------------------------|-------|------|---|--| +| TEST NUMBER: 5.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 4.1/Q.703     STD: Fig. 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: SU delimitation, alignment, error detection and correction | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Greater than maximum signal unit length | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the signal unit delimitation, alignment, error detection action on receipt of signal unit greater than the maximum length | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
1 – 0 corrupt MSU
(FIB + FSN = 80)
(signal unit length
> max. Allowed)
>
< 1 – 0 FISU
(BSN unchanged)
1 – 0 FISU >
| | | | | SP B | | | SP A | | Link | | | | Link | | | | < | | 1 – 0 | FISU | 1 – 0 | FISU | > | | | | 1 – 0 | corrupt MSU
(FIB + FSN = 80)
(signal unit length
> max. Allowed) | > | | | | | | < | | 1 – 0 | FISU
(BSN unchanged) | 1 – 0 | FISU | > | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt MSU
(FIB + FSN = 80)
(signal unit length
> max. Allowed) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | FISU
(BSN unchanged) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send corrupt MSU at B with maximum length plus extra bits and good sumcheck. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check A discards the signal unit, and goes into octet counting mode. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | On reception of a correct FISU, check that A leaves the octet counting mode and remains in the "in service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|------------------|-----------|--|--|-----------|------|--|--|------|--|--|--|---|-------|------|--|--|--|--|------------------|-------|------|---|--|--|-------|-------------|---|--|--|--|------------------|--|--|--|--|-------------------|--|--|--|--|----------------|--|--|--|--|--|---|-------|------|--|--|--|--|-----------------|-------|------|---|--|--| +| TEST NUMBER: 5.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 4.1/Q.703      STD: Fig. 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: SU delimitation, alignment, error detection and correction | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Below minimum signal unit length | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the signal unit delimitation, alignment and error detection action on receipt of signal unit less than the minimum length | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP      B SP      A
Link Link
< 1 – 0 FISU
(BIB + BSN = FF)
1 – 0 FISU >
1 – 0 corrupt MSU >
(FIB + FSN = 80)
(signal unit less
than 6 octets)
< 1 – 0 FISU
(BSN unchanged)
1 – 0 FISU >
| | | | | SP      B | | | SP      A | Link | | | Link | | | | < | 1 – 0 | FISU | | | | | (BIB + BSN = FF) | 1 – 0 | FISU | > | | | 1 – 0 | corrupt MSU | > | | | | (FIB + FSN = 80) | | | | | (signal unit less | | | | | than 6 octets) | | | | | | < | 1 – 0 | FISU | | | | | (BSN unchanged) | 1 – 0 | FISU | > | | | +| | SP      B | | | SP      A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | (BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt MSU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (FIB + FSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (signal unit less | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | than 6 octets) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | (BSN unchanged) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate a corrupt MSU at B of less than 6 octet (i.e. less than 5 octets between flags). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check A discards the signal unit and may go into octet counting mode. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | On reception of a correct FISU, check that A leaves the octet counting mode if it was entered and remains in the "in service" state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------| +| TEST NUMBER: 5.4 | | PAGE: 1 OF 1 | +| REFERENCE: Clause 2/Q.703      STD: Fig. 11 | | | +| TITLE: SU delimitation, alignment, error detection and correction | | | +| SUBTITLE: Reception of single and multiple flags between FISUs | | | +| PURPOSE: To check that single and multiple flags between FISUs can be received | | | +| PRE-TEST CONDITIONS: Link in service | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | +|

EXPECTED SIGNAL UNIT SEQUENCE:

Link              SP              B

1 – 0      FISU              ----->

             case 1              FISU F FISU

             case 2              FISU F F
FISU

                                         n(\geq 2)

1 – 0      FISU              ----->

Link              SP              A

F: Flag

n = number of flags

| | | +| TEST DESCRIPTION | | | +| 1. | Check that single and n flags, case 1 and case 2 respectively, can be received. | | + +###### **MTP, LEVEL 2** + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------|-----------|----------------| +| TEST NUMBER: 5.5 | | PAGE: 1 OF 1 | | | +| REFERENCE: Clause 2/Q.703      STD: Fig. 11 | | | | | +| TITLE: SU delimitation, alignment, error detection and correction | | | | | +| SUBTITLE: Reception of single and multiple flags between MSUs | | | | | +| PURPOSE: To check that single and multiple flags between MSUs can be received | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

Link              SP              B

1 – 0      FISU      >

             case 1             
MSU F MSU

             case 2             
MSU F F
MSU

n(\geq 2)

1 – 0      FISU      >

Link              SP              A



F: Flag

n = number of flags

| | | MSU F MSU | MSU F F
MSU | +| MSU F MSU | | | | | +| MSU F F
MSU | | | | | +| TEST DESCRIPTION | | | | | +| 1. | Check that single and n flags, case 1 and case 2 respectively, can be received. | | | | + +###### **MTP, LEVEL 2** + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| TEST NUMBER: 6.1 | | PAGE: 1 OF 1 | +| REFERENCE: 10.2/Q.703      STD: Fig. 11; Fig. 18; Fig. 8 | | | +| TITLE: SUERM check | | | +| SUBTITLE: Error rate of 1 in 256 – Link remains in service | | | +| PURPOSE: To check the SUERM at a link error rate of 1 in 256 units | | | +| PRE-TEST CONDITIONS: Link in service | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP      B
Link

1 – 0      FISU
Ct          : corrupt 1
             in 256
<
>
SP      A
Link

1 – 0      FISU
| | | +| TEST DESCRIPTION | | | +| 1.
2. | Check that "In service" state is maintained. The test should run for several minutes.

Ct = the count of corrupted FISUs.
NOTE – 1) The number (x) of corrupt signal units before an SIOS returned is calculated according to the following formula (a = number of correct signal units):
$x = \frac{1}{1+a} \left( \frac{256 \times 64}{\frac{256}{1+a} - 1} \right) \quad \text{for } a < 256$
2) In this case as $a = 255$ , so $x = \text{infinity}$ . | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------------|-------|------|------|--|--|------|--|------|--|--|------|--|--|--|--|------|-------|------|--|-------|------|--|--|--|--|----|-----------------------|--|--|--|--|--|--|--|-------| +| TEST NUMBER: 6.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 10.2/Q.703     STD: Fig. 11; Fig. 18; Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: SUERM check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Error rate of 1 in 254 – Link into out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the SUERM at a link error rate of 1 in 254 units | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link

1 – 0 FISU
1 – 0 FISU
Ct : corrupt 1
in 254
1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | |
| 1 – 0 | FISU | | 1 – 0 | FISU | | | | | Ct | : corrupt 1
in 254 | | | | | | | | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | |
| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ct | : corrupt 1
in 254 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | SIOS should be returned after approx. 8192 corrupt FISUs (e.g. CRC error). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Ct = the count of corrupted FISUs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-------------------|-------|------|--|------|--|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|----|---------------------|--|--|--|--|--|---|-------|------| +| TEST NUMBER: 6.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 10.2/Q.703     STD: Fig. 11; Fig. 18; Fig. 8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: SUERM check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Consecutive corrupted SUS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the SUERM on consecutive corrupted signal units | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
Ct : corrupt 1
  in 1
< 1 – 0 SIOS












| | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | Ct | : corrupt 1
in 1 | | | | | | < | 1 – 0 | SIOS | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ct | : corrupt 1
in 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | SIOS should be returned after approx. 64 corrupt FISUs (e.g. CRC error). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Ct = the count of corrupted FISUs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|-------|------|--|--|------|--|------|--|--|--|------|--|--|--|---|--|-------|------|-------|------|---|--|--|--|--|------------|--|--|--|--|--|--------------|--|--|--|--|--|------|---|--|--|--|--|--|---|--|-------|------| +| TEST NUMBER: 6.4 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 10.2/Q.703     STD: Fig. 11; Fig. 18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: SUERM check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Time controlled break of the link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check response to a range of time controlled breaks of Tx or Rx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
: break Tx
: restore Tx
FISU >
< 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | | | Link | | | | < | | 1 – 0 | FISU | 1 – 0 | FISU | > | | | | | : break Tx | | | | | | : restore Tx | | | | | | FISU | > | | | | | | < | | 1 – 0 | FISU | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : break Tx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | : restore Tx | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Break the transmission link, and restore before level 2 goes out of service. (Break time is less than approx. 128 ms for 64 kbit/s). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A enters and leaves the octet counting mode on reception of an FISU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------------|-------|---------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|--|--|---------|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|-----|-------|-----|---|--|----|-------|---------------|---|--|-------|-----|---|--|--|--|---|-------|------| +| TEST NUMBER: 7.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 10.3/Q.703     STD: Fig. 9; Fig. 11; Fig. 17 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: AERM check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Error rate below the normal threshold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the AERM on error rates below the normal threshold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN > T4
1 – 0 corrupt LSSUs >
1 – 0 SIN >
< 1 – 0 FISU
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | : start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | < | 1 – 0 | SIN | 1 – 0 | SIN | > | | T4 | 1 – 0 | corrupt LSSUs | > | | 1 – 0 | SIN | > | | | | < | 1 – 0 | FISU | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | T4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt LSSUs | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start link at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Generate x number of corrupt LSSUs (e.g. CRC error) at B ( $x < T_{in}$ ). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the proving period continues and the link aligns successfully. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-------------------|-------|---------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|--|--|---------|--|--|---|-------|-----|-------|-----|---|--|--|--|--|---|-------|-----|-------|-----|---|--|--|-------|------------------|---|--|--|--|-----|---|--|----|--|--|---|-------|------| +| TEST NUMBER: 7.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 10.3/Q.703      STD: Fig. 9; Fig. 11; Fig. 17 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: AERM check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Error rate at the normal threshold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the AERM at an error rate equal to the normal threshold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS >
: start
< 1 – 0 SIO
1 – 0 SIO >
< 1 – 0 SIN
1 – 0 SIN >
1 – 0 corrupt
LSSUs
>
SIN > T4
< 1 – 0 FISU
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | SIOS | 1 – 0 | SIOS | > | | | | | | | : start | | | < | 1 – 0 | SIO | 1 – 0 | SIO | > | | | | | < | 1 – 0 | SIN | 1 – 0 | SIN | > | | | 1 – 0 | corrupt
LSSUs | > | | | | SIN | > | | T4 | | | < | 1 – 0 | FISU | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt
LSSUs | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | SIN | > | | T4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start link at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Generate x number of corrupt LSSUs (e.g. CRC error) at B ( $x \geq T_{in}$ ). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the proving period is aborted, then restarted and link aligns successfully. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------|-------|------|---------|--|--|------|--|------|--|--|------|--|--|--|--|--|-------|------|--|-------|------|--|--|--|---------|--|--|--|-------|-----|--|-------|-----|--|--|--|--|--|--|--|-------|-----|--|-------|-----|--|--|--|--|-------|---------------|--|--|--|--|--|--|--|-------|-----|--|-------|-----|--|--|--|--|-------|---------------|--|--|--|--|--|--|--|-------|-----|--|-------|-----|--|--|--|--|-------|---------------|--|--|--|--|--|--|--|-------|-----|--|-------|-----|--|--|--|--|-------|---------------|--|--|--|--|--|--|--|-------|-----|--|-------|-----|--|--|--|--|-------|---------------|--|--|--|--|--|--|--|-------| +| TEST NUMBER: 7.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 10.3/Q.703     STD: Fig. 9; Fig. 11; Fig. 17 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: AERM check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Error rate above the normal threshold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the AERM at an error rate above the threshold over five proving periods | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 SIOS
1 – 0 SIOS : start
1 – 0 SIO
1 – 0 SIO
1 – 0 SIN
1 – 0 SIN
1 – 0 corrupt LSSUs
1 – 0 SIN
1 – 0 SIN
1 – 0 corrupt LSSUs
1 – 0 SIN
1 – 0 SIN
1 – 0 corrupt LSSUs
1 – 0 SIN
1 – 0 SIN
1 – 0 corrupt LSSUs
1 – 0 SIN
1 – 0 SIN
1 – 0 corrupt LSSUs
1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | | 1 – 0 | SIOS | | 1 – 0 | SIOS | | | | : start | | | | 1 – 0 | SIO | | 1 – 0 | SIO | | | | | | | | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | 1 – 0 | corrupt LSSUs | | | | | | | | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | 1 – 0 | corrupt LSSUs | | | | | | | | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | 1 – 0 | corrupt LSSUs | | | | | | | | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | 1 – 0 | corrupt LSSUs | | | | | | | | 1 – 0 | SIN | | 1 – 0 | SIN | | | | | 1 – 0 | corrupt LSSUs | | | | | | | | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt LSSUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt LSSUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt LSSUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt LSSUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt LSSUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start link at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Generate x number of corrupt LSSUs (e.g. CRC error) at B ( $x \geq T_{in}$ ). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Observe that 5 proving period attempts are made before link out of service state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------|-------|------|---------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|--|--|--|--|--|--|--|--|--|---------|--|--|---|-------|-----|--|-------|-----|--|--|--|--|--|--|---|-------|-----|--|-------|-----|--|--|--|--|-------|--------------|--|--|--|--|-------|-----|--|--|--|--|----|--|---|-------|-----|--|------|--|--|--|--|--|--|--|---|-------| +| TEST NUMBER: 7.4 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 10.3/Q.703     STD: Fig. 9; Fig. 11; Fig. 17 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: AERM check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Error rate at the emergency threshold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the AERM at the emergency threshold | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link out of service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 SIOS
1 – 0 SIOS
: start
< 1 – 0 SIO
1 – 0 SIO
< 1 – 0 SIN
1 – 0 SIE
1 – 0 corrupt LSSU
1 – 0 SIE
T4 < 1 – 0 SIN
(Pe)
< 1 – 0 FISU
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | SIOS | | 1 – 0 | SIOS | | | | | | | | | | : start | | | < | 1 – 0 | SIO | | 1 – 0 | SIO | | | | | | | < | 1 – 0 | SIN | | 1 – 0 | SIE | | | | | 1 – 0 | corrupt LSSU | | | | | 1 – 0 | SIE | | | | | T4 | | < | 1 – 0 | SIN | | (Pe) | | | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : start | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | corrupt LSSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| T4 | | < | 1 – 0 | SIN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (Pe) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Start link at A, check emergency proving started from B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Generate x number of corrupt LSSUs (e.g. CRC error) at B ( $5 > x \geq \text{Tie}$ ). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that link aligns successfully. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------|-------|----------------------------------------------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|-------|---------------------------------------------|---|--|--|--|--|---|-------|----------------------------------------------|-------|----------------------------------------------|---|--|--|--|--|---|-------|---------------------------------------------|-------|----------------------------------------------|---|--|--|--|--|---| +| TEST NUMBER: 8.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.2/Q.703     STD: Fig. 13; Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: MSU transmission and reception | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check basic MSU transmission and reception | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
1 – 0 MSU
(FIB + FSN = 80)
(BIB + BSN = FF)
>
< 1 – 0 FISU
(FIB + FSN = FF)
(BIB + BSN = 80)
1 – 0 FISU
(FIB + FSN = 80)
(BIB + BSN = FF)
>
< 1 – 0 MSU
(FIB + FSN = 80)
(BIB + BSN = 80)
1 – 0 FISU
(FIB + FSN = 80)
(BIB + BSN = 80)
>
< 1 – 0 FISU
(FIB + FSN = 80)
(BIB + BSN = 80)
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | 1 – 0 | MSU
(FIB + FSN = 80)
(BIB + BSN = FF) | > | | | | | < | 1 – 0 | FISU
(FIB + FSN = FF)
(BIB + BSN = 80) | 1 – 0 | FISU
(FIB + FSN = 80)
(BIB + BSN = FF) | > | | | | | < | 1 – 0 | MSU
(FIB + FSN = 80)
(BIB + BSN = 80) | 1 – 0 | FISU
(FIB + FSN = 80)
(BIB + BSN = 80) | > | | | | | < | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 80)
(BIB + BSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FIB + FSN = FF)
(BIB + BSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 80)
(BIB + BSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 80)
(BIB + BSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 80)
(BIB + BSN = 80) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FIB + FSN = 80)
(BIB + BSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A receives the MSU correctly, and returns a positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Generate an MSU at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that B receives the MSU correctly, and returns a positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-------------------|-------|-------------------------|------|--|------|--|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|--|--|---|-------|-------------------------|--|--|---|-------|-------------------------|-------|--------------------------|---|--|--|--|--|---|-------|-------------------------|--|--|---|-------|-------------------------| +| TEST NUMBER: 8.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703      STD: Fig. 13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Negative acknowledgement of MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to a negatively acknowledged MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
< 1 – 0 MSU
(FIB + FSN = 80)
< 1 – 0 MSU
(FIB + FSN = 81)
1 – 0 FISU
(BIB + BSN = 7F)
>
< 1 – 0 MSU
(FIB + FSN = 00)
< 1 – 0 MSU
(FIB + FSN = 01)
| | | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | | | < | 1 – 0 | MSU
(FIB + FSN = 80) | | | < | 1 – 0 | MSU
(FIB + FSN = 81) | 1 – 0 | FISU
(BIB + BSN = 7F) | > | | | | | < | 1 – 0 | MSU
(FIB + FSN = 00) | | | < | 1 – 0 | MSU
(FIB + FSN = 01) | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 81) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(BIB + BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 01) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Send MSU from A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Reply with negative acknowledgement from B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that A retransmits the MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------|--------------------------|--|-------------|--|------|--|--|------|--|--|--|---|-------|------|-------|--------------------------|---|--|--|--|--|---|-------|-------------------------|--|--|--|--|--------|--|--|---|-------|-------------------------|--|--|---|-------|--------------------------|-------|--------------------------|---|--|--|--|--|---|-------|-------------------------|--|--|--|--|--------|--|--|---|-------|-------------------------| +| TEST NUMBER: 8.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703      STD: Fig. 13 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Check RTB full | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that MSUs are buffered when no acknowledgements are received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU
(BIB + BSN = FF)
>
< 1 – 0 MSU
(FIB + FSN = 80)
•
•
< 1 – 0 MSU
(FIB + FSN = FE)
< 1 – 0 FISU
(FIB + FSN = FE)
1 – 0 FISU
(BIB + BSN = 7F)
>
< 1 – 0 MSU
(FIB + FSN = 00)
•
•
< 1 – 0 MSU
(FIB + FSN = 7E)
| | | | SP B | | SP A | | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU
(BIB + BSN = FF) | > | | | | | < | 1 – 0 | MSU
(FIB + FSN = 80) | | | | | •
• | | | < | 1 – 0 | MSU
(FIB + FSN = FE) | | | < | 1 – 0 | FISU
(FIB + FSN = FE) | 1 – 0 | FISU
(BIB + BSN = 7F) | > | | | | | < | 1 – 0 | MSU
(FIB + FSN = 00) | | | | | •
• | | | < | 1 – 0 | MSU
(FIB + FSN = 7E) | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(BIB + BSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = FE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FIB + FSN = FE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(BIB + BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FIB + FSN = 7E) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate MSUs at A, at a rate of 100 per second, in order to fill the RTB before the EDA timer T7 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | No acknowledgements are sent from B until the last message is received, then send negative acknowledgement to the first message received. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the complete contents of the RTB are retransmitted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-------------------|-------|--------------------------|--|--|------|------|--|--|------|--|--|--|---|-------|--------------------------|-------|--------------------------|---|--|--|-------|-------------------------|---|--|--|--|--|---|-------|--------------------------|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|--|--|---|-------|--------------------------|-------|-------------------------|---|--|--|--|--|---|-------|--------------------------| +| TEST NUMBER: 8.4 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.2/Q.703     STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Single MSU with erroneous FIB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To ensure correct performance when an MSU with erroneous FIB is received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:
SP B SP A
Link Link
< 1 – 0 FISU
(BIB + BSN = 7F)
1 – 0 FISU
(FIB + FSN = 7F)
>
1 – 0 MSU
(FIB + FSN = 80)
>
< 1 – 0 FISU
(BIB + BSN = 7F)
1 – 0 FISU
(FIB + FSN = 00)
>
1 – 0 FISU
(FIB + FSN = 00)
>
< 1 – 0 FISU
(BIB + BSN = FF)
1 – 0 MSU
(FIB + FSN = 80)
>
< 1 – 0 FISU
(BIB + BSN = 80)
| | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | FISU
(BIB + BSN = 7F) | 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | < | 1 – 0 | FISU
(BIB + BSN = 7F) | 1 – 0 | FISU
(FIB + FSN = 00) | > | | | 1 – 0 | FISU
(FIB + FSN = 00) | > | | | | | < | 1 – 0 | FISU
(BIB + BSN = FF) | 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | < | 1 – 0 | FISU
(BIB + BSN = 80) | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 00) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 00) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU at B with FIB inverted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check A discards the MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Generate 2 FISUs at B with correct FIB. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check A discards the FISU and negative acknowledgement returned. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that B retransmits the MSU correctly, and positive acknowledgement returned. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-------------------|-------|--------------------------|-----------|--|--|-----------|------|--|--|------|--|--|--|---|-------|------|-------|------|---|--|--|-------|-------------------------|---|--|--|--|--|---|-------|--------------------------|-------|-------------------------|---|--|--|-------|--------------------------|---|--|--|--|--|---|-------|--------------------------|-------|-------------------------|---|--|--|--|--|---| +| TEST NUMBER: 8.5 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.2/Q.703      STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Duplicated FSN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the reception control response to duplicated FSNs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP      B SP      A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
1 – 0 MSU
(FIB + FSN = 80)
>
< 1 – 0 FISU
(BIB + BSN = 80)
1 – 0 MSU
(FIB + FSN = 80)
>
1 – 0 FISU
(FIB + FSN = 81)
>
< 1 – 0 FISU
(BIB + BSN = 00)
1 – 0 MSU
(FIB + FSN = 01)
>
< 1 – 0 FISU
(BIB + BSN = 01)
| | | | | SP      B | | | SP      A | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | < | 1 – 0 | FISU
(BIB + BSN = 80) | 1 – 0 | MSU
(FIB + FSN = 80) | > | | | 1 – 0 | FISU
(FIB + FSN = 81) | > | | | | | < | 1 – 0 | FISU
(BIB + BSN = 00) | 1 – 0 | MSU
(FIB + FSN = 01) | > | | | | | < | +| | SP      B | | | SP      A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 81) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 01) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 01) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU at B, check A receives the MSU correctly and returns a positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Duplicate the FSN at B, check that A responds with a negative acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Retransmit the MSU with correct FSN, check that A replies with a positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-------------------|-------|--------------------------|-----------|--|--|-----------|------|--|------|------|--|--|--|--|-------|--------------------------|-------|--------------------------|------|--|--|-------|-------------------------|------|--|--|-------|--------------------------|------|--|--|-------|--------------------------|------|--|--|--|--|------|-------|--------------------------|-------|-------------------------|------|--|--|--|--|------|-------|--------------------------| +| TEST NUMBER: 8.6 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.2/Q.703     STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Erroneous retransmission – Single MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the reception control response to retransmission of a single MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP      B SP      A
Link <--- Link
1 – 0 FISU
(BIB + BSN = FF)
1 – 0 FISU
(FIB + FSN = FF)
--->
1 – 0 MSU
(FIB + FSN = 00)
--->
1 – 0 FISU
(FIB + FSN = 80)
--->
1 – 0 FISU
(FIB + FSN = 80)
--->
<--- 1 – 0 FISU
(BIB + BSN = 7F)
1 – 0 MSU
(FIB + FSN = 00)
--->
<--- 1 – 0 FISU
(BIB + BSN = 00)
| | | | | SP      B | | | SP      A | Link | | <--- | Link | | | | | 1 – 0 | FISU
(BIB + BSN = FF) | 1 – 0 | FISU
(FIB + FSN = FF) | ---> | | | 1 – 0 | MSU
(FIB + FSN = 00) | ---> | | | 1 – 0 | FISU
(FIB + FSN = 80) | ---> | | | 1 – 0 | FISU
(FIB + FSN = 80) | ---> | | | | | <--- | 1 – 0 | FISU
(BIB + BSN = 7F) | 1 – 0 | MSU
(FIB + FSN = 00) | ---> | | | | | <--- | 1 – 0 | FISU
(BIB + BSN = 00) | +| | SP      B | | | SP      A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | <--- | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | FISU
(BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = FF) | ---> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 00) | ---> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 80) | ---> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 80) | ---> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | <--- | 1 – 0 | FISU
(BIB + BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 00) | ---> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | <--- | 1 – 0 | FISU
(BIB + BSN = 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | A single MSU with FIB inverted in error is sent to A, followed by FISUs with correct FIBs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A returns a negative acknowledgement for the MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Retransmit the MSU correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that A receives the MSU correctly and returns a positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-------------------|-------|------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|--|--|---| +| TEST NUMBER: 8.7 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703     STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Erroneous retransmission – Multiple FISUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test reception control response to retransmission of multiple FISUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU
(FIB + FSN = FF)
>
1 – 0 FISU
(FIB + FSN = 7F)
>
1 – 0 FISU
(FIB + FSN = FF)
>
1 – 0 FISU
(FIB + FSN = 7F)
>
< 1 – 0 SIOS
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU
(FIB + FSN = FF) | > | | | 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | 1 – 0 | FISU
(FIB + FSN = FF) | > | | | 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | | | < | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate FISUs with the FIB inverted at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A responds with link out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------------|-------|------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|--|--|---|-------|------|-------|--------------------------|---|--|--|--|--|---|-------|------| +| TEST NUMBER: 8.8 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703     STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Single FISU with corrupt FIB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to receive an FISU with a corrupt FIB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU
(FIB + FSN = FF)
>
1 – 0 FISU
(FIB + FSN = 7F)
>
< 1 – 0 FISU
1 – 0 FISU
(FIB + FSN = FF)
>
< 1 – 0 FISU
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU
(FIB + FSN = FF) | > | | | 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | | | < | 1 – 0 | FISU | 1 – 0 | FISU
(FIB + FSN = FF) | > | | | | | < | 1 – 0 | FISU | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate one FISU with a corrupt FIB at B, and check that the link status remains in service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|--------------------------|------|--|------|------|--|--|---|-------|------|-------|------|---|--|--|-------|-------------------------------------|---|--|--|-------|------|---|--|--|-------|-------------------------|---|--|--|-------|--------------------------|----------|--|--|-------|--------------------------|---|--|--|--|--|---|-------|--------------------------|-------|-------------------------|---|--|--|--|--|---|-------|--------------------------| +| TEST NUMBER: 8.9 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.2/Q.703     STD: Fig. 10; Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Single FISU prior to RPO being set | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to RPO while in the abnormal FIB state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:
Link SP B Link SP A
< 1 – 0 FISU
1 – 0 FISU >
1 – 0 FISU (one only)
(FIB + FSN = 7F)
>
1 – 0 SIPO >
1 – 0 MSU
(FIB + FSN = 80)
>
1 – 0 FISU
(FIB + FSN = 80)
> (Note)
1 – 0 FISU
(FIB + FSN = 80)
>
< 1 – 0 FISU
(BIB + BSN = 7F)
1 – 0 MSU
(FIB + FSN = 00)
>
< 1 – 0 FISU
(BIB + BSN = 00)

NOTE – RPO at A has recovered, but this FISU is discarded.

| | | | Link | SP B | | Link | SP A | | | < | 1 – 0 | FISU | 1 – 0 | FISU | > | | | 1 – 0 | FISU (one only)
(FIB + FSN = 7F) | > | | | 1 – 0 | SIPO | > | | | 1 – 0 | MSU
(FIB + FSN = 80) | > | | | 1 – 0 | FISU
(FIB + FSN = 80) | > (Note) | | | 1 – 0 | FISU
(FIB + FSN = 80) | > | | | | | < | 1 – 0 | FISU
(BIB + BSN = 7F) | 1 – 0 | MSU
(FIB + FSN = 00) | > | | | | | < | 1 – 0 | FISU
(BIB + BSN = 00) | +| Link | SP B | | Link | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU (one only)
(FIB + FSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIPO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 80) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 80) | > (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FIB + FSN = 80) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FIB + FSN = 00) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(BIB + BSN = 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1.
2.
3. | Generate one FISU at B with abnormal FIB.
Send SIPO from B, followed by an MSU.
Check A responds correctly with negative acknowledgement and a retransmission is received correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------|-------|------------------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|--|--|--|--|--|------------------|--|--|--|--|--|------------------|--|--|--|--|-------|-----|--|--|--|--|--|------------------|--|--|--|--|--|------------------|--|--|--|--|-------|------|----------|--|--|--|--|------------------|--|--|--|--|--|------------------|--|--|--|--|-------|------|--|--|--|--|--|------------------|--|--|--|--|--|------------------|--|--|--|--|--|--|---|-------|------|--|--|--|--|--|------------------|--|-------|-----|--|--|--|--|--|------------------|--|--|--|--|--|------------------|--|--|--|--|--|--|---|-------|------|--|--|--|--|--| +| TEST NUMBER: 8.10 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703   STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Abnormal BSN – Single MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to an abnormal BSN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:
SP BSP A
LinkLink
< 1 – 0FISU
1 – 0FISU
(FIB + FSN = FF)
(BIB + BSN = FF)
1 – 0MSU
(FIB + FSN = 80)
(BIB + BSN = BF)
1 – 0FISU > (Note)
(FIB + FSN = 80)
(BIB + BSN = FF)
1 – 0FISU
(FIB + FSN = 80)
(BIB + BSN = FF)
< 1 – 0FISU
(BIB + BSN = 7F)
1 – 0MSU
(FIB + FSN = 00)
(BIB + BSN = FF)
< 1 – 0FISU
(BIB + BSN = 00)
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | | | | | | (FIB + FSN = FF) | | | | | | (BIB + BSN = FF) | | | | | 1 – 0 | MSU | | | | | | (FIB + FSN = 80) | | | | | | (BIB + BSN = BF) | | | | | 1 – 0 | FISU | > (Note) | | | | | (FIB + FSN = 80) | | | | | | (BIB + BSN = FF) | | | | | 1 – 0 | FISU | | | | | | (FIB + FSN = 80) | | | | | | (BIB + BSN = FF) | | | | | | | < | 1 – 0 | FISU | | | | | | (BIB + BSN = 7F) | | 1 – 0 | MSU | | | | | | (FIB + FSN = 00) | | | | | | (BIB + BSN = FF) | | | | | | | < | 1 – 0 | FISU | | | | | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (FIB + FSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (FIB + FSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (BIB + BSN = BF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > (Note) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (FIB + FSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (FIB + FSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | (BIB + BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (FIB + FSN = 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | (BIB + BSN = 00) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE – Though UNB: =1, abnormal BSNR is not cancelled. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate a single MSU with abnormal BSN at B, followed by FISUs with correct BSN. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A responds with a negative acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Retransmit the MSU correctly at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that the MSU is received correctly and positive acknowledgement is given. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|---|-------------------|------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|-------|--------------------------|---|--|--|--|--|---|-------|------| +| TEST NUMBER: 8.11 | | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703     STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Abnormal BSN – Two consecutive FISUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to abnormal BSNs in two consecutive FISUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU
(BIB + BSN = FF)
>
1 – 0 FISU
(BIB + BSN = BF)
>
1 – 0 FISU
(BIB + BSN = BF)
>
1 – 0 FISU
(BIB + BSN = FF)
>
< 1 – 0 SIOS
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | FISU | 1 – 0 | FISU
(BIB + BSN = FF) | > | | | 1 – 0 | FISU
(BIB + BSN = BF) | > | | | 1 – 0 | FISU
(BIB + BSN = BF) | > | | | 1 – 0 | FISU
(BIB + BSN = FF) | > | | | | | < | 1 – 0 | SIOS | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(BIB + BSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(BIB + BSN = BF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(BIB + BSN = BF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(BIB + BSN = FF) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate two consecutive FISUs at B with abnormal BSNs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A responds by taking the link out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|-------------------|-------|------------------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------|--|-------|------|---|--|--|--|--|------------------|--|--|--|--|--|--|---|-------|-----|--|--|--|--|--|------------------|--|--|--|--|--|----|--|--|--|---|-------|------|--| +| TEST NUMBER: 8.12 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 5.3/Q.703      STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Excessive delay of acknowledgement | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the transmission control response to the expiration of EDA timer T7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
(BIB + BSN = FF)
< 1 – 0 MSU
(FIB + FSN = 80)
T7
< 1 – 0 SIOS

| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | > | | | | | (BIB + BSN = FF) | | | | | | | < | 1 – 0 | MSU | | | | | | (FIB + FSN = 80) | | | | | | T7 | | | | < | 1 – 0 | SIOS | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | (BIB + BSN = FF) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | (FIB + FSN = 80) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | T7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Discard the received MSU at B and send no acknowledgement to A for more than T7 period. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that the link is taken out of service by SIOS generated at A after T7 has expired. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Timer T7 shall be in the range 0.5 secs to 2.0 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-------------------|---|-------|------|--------|--|----|---|--|------|--|--|--|------|--|--|--|--|--|---|-------|------|--|-------|------|--|---|--|--|--------|--|--|--|---|-------|------|--| +| TEST NUMBER: 8.13 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703     STD: Fig. 14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (Basic) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Level 3 Stop command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to a Stop command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU > : stop
< 1 – 0 SIOS
| | | | | SP | B | | SP | A | | Link | | | | Link | | | | | | < | 1 – 0 | FISU | | 1 – 0 | FISU | | > | | | : stop | | | | < | 1 – 0 | SIOS | | +| | SP | B | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | > | | | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Give Stop command at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A responds with link out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|------------------------|-------|------------------------------|------|--|--|------|------|--|--|------|--|--|--|---|-------|------------------------------|-------|------------------------------|---|--|--|--|--|---|-------|----------------------------|--|--|---|-------|----------------------------|--|--|--|--|---|--|--|--|--|---|-------|-----------------------------|---|--|--|--|--|---|-------|-----------------------------|-------|---------------------------|---|--|--|--|--|---|-------|----------------------------| +| TEST NUMBER: 9.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.2/Q.703      STD: Fig. 15; Fig. 16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: MSU transmission and reception | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check basic MSU transmission and reception | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT, CPT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
1 – 0 FISU
(FSN = 7F, BSN = 0)
>
< 1 – 0 FISU
(FSN = 0, BSN = 7F)
1 – 0 MSU
(FSN = 0, BSN = 0)
>
< 1 – 0 FISU
(FSN = 0, BSN = 0)
| | | | | SP B | | | SP A | Link | | | Link | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | • | | | | | • | 1 – 0 | FISU
(FSN = 7F, BSN = 0) | > | | | | | < | 1 – 0 | FISU
(FSN = 0, BSN = 7F) | 1 – 0 | MSU
(FSN = 0, BSN = 0) | > | | | | | < | 1 – 0 | FISU
(FSN = 0, BSN = 0) | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 0) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 0) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 0, BSN = 0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that B receives the MSU correctly. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that A sends FISUs after receiving an FISU with a positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Generate an MSU at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that A receives the MSU correctly and returns a positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | +|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------|--|--| +| TEST NUMBER: 9.2 | | PAGE: 1 OF 1 | | | | +| REFERENCE: 6.3/Q.703 | | STD: Fig. 15; Fig. 16 | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | +| SUBTITLE: Priority control | | | | | | +| PURPOSE: To check the preventive retransmission procedure | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | +| EXPECTED SIGNAL UNIT SEQUENCE: | | | | | | +| Link | SP      B | Link | SP      A | | | +| | <----- | 1 - 0 | FISU
(FSN = 7F, BSN = 7F) | | | +| 1 - 0 | FISU
(FSN = 7F, BSN = 7F) -----> | | | | | +| | <----- | 1 - 0 | MSU
(FSN = 0, BSN = 7F) | | | +| | <----- | 1 - 0 | MSU
(FSN = 1, BSN = 7F) | | | +| | | | • | | | +| | | | • | | | +| | <----- | 1 - 0 | MSU
(FSN = 2, BSN = 7F) | | | +| | | | • | | | +| | | | • | | | +| | <----- | 1 - 0 | MSU
(FSN = 0, BSN = 7F) | | | +| | <----- | 1 - 0 | MSU
(FSN = 1, BSN = 7F) | | | +| | <----- | 1 - 0 | MSU
(FSN = 2, BSN = 7F) | | | +| | | | • | | | +| | | | • | | | +| 1 - 0 | FISU
(FSN = 7F, BSN = 0) -----> | | | | | +| 1 - 0 | FISU
(FSN = 7F, BSN = 1) -----> | | | | | +| 1 - 0 | FISU
(FSN = 7F, BSN = 2) -----> | | | | | +| | <----- | 1 - 0 | FISU
(FSN = 2, BSN = 7F) | | | +| TEST DESCRIPTION | | | | | | +| 1. | Generate two MSUs at A. | | | | | +| 2. | No positive acknowledgement is sent from B. | | | | | +| 3. | Check that MSUs are retransmitted at A. | | | | | +| 4. | Generate another MSU at A. | | | | | +| 5. | Check that B receives MSUs correctly. | | | | | +| 6. | Reply with positive acknowledgement at B. | | | | | +| 7. | Check that A stops retransmission after receiving the positive acknowledgement for the last MSU in RTB and sends FISU. | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|--------------------------------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------------------------------|--|-------|------------------------------|---|--|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|--------|--|--|--|---|-------|-----------------------------|--|--|--|---|-------|----------------------------|--|--|--|--|--|--------|--|--|--|---|-------|----------------------------|--|-------|-----------------------------|---|--|--|--|--|--|---|-------|--------------------------------|--|--|--|--|--|--------|--|--|--|---|-------|-----------------------------|--| +| TEST NUMBER: 9.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.4/Q.703     STD: Fig. 15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Forced retransmission with the value N 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that "RTB full" is detected by N 1 and forced retransmission occurs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = 7E, BSN = 7F)
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = X, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 0)
>
< 1 – 0 MSU
(FSN = X + 1, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = 7F, BSN = 7F)
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | •
• | | | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | •
• | | | | < | 1 – 0 | MSU
(FSN = X, BSN = 7F) | | 1 – 0 | FISU
(FSN = 7F, BSN = 0) | > | | | | | | < | 1 – 0 | MSU
(FSN = X + 1, BSN = 7F) | | | | | | •
• | | | | < | 1 – 0 | MSU
(FSN = 7F, BSN = 7F) | | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = X, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 0) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = X + 1, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate 128 MSUs at A, at a rate of 100 per second, in order to fill the RTB before the EDA timer T7 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | No positive acknowledgement is sent from B until a forced retransmission starts at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Reply with a positive acknowledgement with BSN = 0 before T7 expires at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Check that the forced retransmission is cancelled after the transmission of the last MSU in RTB. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | NOTE – N 1 is the maximum number of MSUs which are available for retransmission.
(The value of N 1 is normally 127.) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------|---------------------------------------|---|--|--|----|---|--|------|--|--|--|------|--|--|--|--|--|--|---|-------|------------------------------|--|--|-------|------------------------------|--|---|--|--|--|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|--|--|--------|--|--|--|--|--|---|-------|--------------------------------|--|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|--|--|--------|--|--|--|--|--|---|-------|----------------------------|--|--|-------|---------------------------------|--|---|--|--|--|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|---|-------|---------------------------------------|--|--| +| TEST NUMBER: 9.4 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.4/Q.703     STD: Fig. 15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Forced retransmission with the value N 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that "RTB full" is detected by N 2 and forced retransmission starts | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:
SP B SP A
Link Link
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = N – 1, BSN = 7F)
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = X, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = a – 1)
>
< 1 – 0 MSU
(FSN = a, BSN = 7F)
< 1 – 0 MSU
(FSN = N, BSN = 7F)
(a > X)
| | | | | SP | B | | | SP | A | | Link | | | | Link | | | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | > | | | | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | •
• | | | | | | < | 1 – 0 | MSU
(FSN = N – 1, BSN = 7F) | | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | •
• | | | | | | < | 1 – 0 | MSU
(FSN = X, BSN = 7F) | | | 1 – 0 | FISU
(FSN = 7F, BSN = a – 1) | | > | | | | | | | | < | 1 – 0 | MSU
(FSN = a, BSN = 7F) | | | | | | < | 1 – 0 | MSU
(FSN = N, BSN = 7F)
(a > X) | | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = N – 1, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = X, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = a – 1) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = a, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = N, BSN = 7F)
(a > X) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate N + 1 MSUs at A (the octet count of N MSUs is larger than N 2 ). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Send no positive acknowledgement at B until a forced retransmission starts at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that B receives the MSUs with FSN = 0 up to FSN = N – 1 but does not receive the MSU with FSN = N. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Reply with a positive acknowledgement with BSN = a – 1 at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that the retransmission restarts from the next value of FSN which is acknowledged by B when the retransmission is interrupted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Check that B receives the MSU with FSN = N. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | NOTE – N 2 is the maximum number of octets which are available for retransmission. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-------------------|-------|------------------------------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------------------------------|--|-------|------------------------------|---|--|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|---|--|--|--|--|--|---|--|--|--|---|-------|-----------------------------|--|--|--|---|-------|----------------------------|--|--|--|--|--|---|--|--|--|--|--|---|--|--|--|---|-------|----------------------------|--|-------|------------------------------|---|--|--|--|--|--|---|-------| +| TEST NUMBER: 9.5 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.4/Q.703 STD: Fig. 15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Forced retransmission cancel | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the forced retransmission is cancelled when BSN equal to FSNL is received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:
SP B SP A
Link Link
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = 7E, BSN = 7F)
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = X, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7E)
>
< 1 – 0 MSU
(FSN = 7F, BSN = 7F)
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | • | | | | | | • | | | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | • | | | | | | • | | | | < | 1 – 0 | MSU
(FSN = X, BSN = 7F) | | 1 – 0 | FISU
(FSN = 7F, BSN = 7E) | > | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = X, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7E) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Generate N1 + 1 MSUs at A (e.g. 128).
  2. 2. Send no positive acknowledgement at B until a retransmission occurs at A.
  3. 3. Reply with a positive acknowledgement with BSN = 7E at B.
  4. 4. Check that a forced retransmission is cancelled and the MSU with FSN = 7F is sent at A.

NOTE 1 – FSNL is the FSN of the last MSU in RTB.

NOTE 2 – Alternatively, the number of octets threshold (N2), instead of the number of MSUs threshold (N1), could be used to start forced retransmission.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### MTP, LEVEL 2 + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------|------------------------------|---|--|--|----|---|------|--|--|--|------|--|--|--|--|--|---|-------|------------------------------|--|-------|------------------------------|--|---|--|--|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|--|---|--|--|--|--|--|--|---|--|--|--|--|---|-------|-----------------------------|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|--|---|--|--|--|--|--|--|---|--|--|--|--|---|-------|-----------------------------|--|--|--|--|---|-------|----------------------------|--|--|--|--|--|--| +| TEST NUMBER: 9.6 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.4/Q.703      STD: Fig. 15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Repetition of forced retransmission | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the forced retransmission repeats when "RTB full" is still detected after finishing a forced retransmission | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:
SP B SP A
Link Link
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = 7E, BSN = 7F)
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
•
< 1 – 0 MSU
(FSN = 7E, BSN = 7F)
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
| | | | | SP | B | | | SP | A | Link | | | | Link | | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | > | | | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | • | | | | | | | • | | | | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | • | | | | | | | • | | | | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = 7E, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate MSUs at A at a rate of N per second, in order to make A repeat a forced retransmission.
( $N \geq 127 + T$ , where T = lower limit of T7). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | No acknowledgement is sent from B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that A repeats a forced retransmission. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | +|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------|--|--| +| TEST NUMBER: 9.7 | | PAGE: 1 OF 1 | | | | +| REFERENCE: 6.2/Q.703 | | STD: Fig. 15 | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | +| SUBTITLE: MSU transmission while RPO set | | | | | | +| PURPOSE: To ensure correct performance while RPO is set | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | +| EXPECTED SIGNAL UNIT SEQUENCE: | | | | | | +| Link | SP B | Link | SP A | | | +| | <----- | 1 - 0 | FISU
(FSN = 7F, BSN = 7F) | | | +| 1 - 0 | FISU
(FSN = 7F, BSN = 7F)
-----> | | | | | +| | <----- | 1 - 0 | MSU
(FSN = 0, BSN = 7F)
:
: | | | +| | : set LPO | | | | | +| 1 - 0 | SIPO
(FSN = 7F, BSN = 7F)
-----> | | | | | +| | <----- | 1 - 0 | FISU
(FSN = 0, BSN = 7F)
:
: | | | +| | : clear LPO | | | | | +| 1 - 0 | MSU
(FSN = 0, BSN = 7F)
-----> | | | | | +| | <----- | 1 - 0 | FISU
(FSN = 7F, BSN = 0) | | | +| 1 - 0 | MSU
(FSN = 0, BSN = 7F)
-----> | | | | | +| | <----- | 1 - 0 | FISU
(FSN = 7F, BSN = 0) | | | +| TEST DESCRIPTION | | | | | | +| 1. | Generate an MSU at A. | | | | | +| 2. | Instead of sending positive acknowledgement, set and keep PO at B for at least 1.2 s. | | | | | +| 3. | Check A stops a retransmission of the MSU and sends FISUs and does not detect link failure by the expiration of T7. | | | | | +| 4. | Cease PO after at least 1.2 s and send an MSU with no positive acknowledgement at B. | | | | | +| 5. | Check A flushed its buffer and no old MSU is sent. | | | | | +| 6. | Generate an MSU at B. | | | | | +| 7. | Check A receives the MSU and responds correctly. | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-------------------|-------|------------------------------|-----------|--|--|-----------|------|--|--|------|--|--|--|---|-------|------------------------------|-------|------------------------------|---|--|--|-------|---------------------------|---|--|--|-------|----------------------------|---|--|--|-------|----------------------------|---|--|--|--|--|---|-------|-----------------------------| +| TEST NUMBER: 9.8 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.3/Q.703     STD: Fig. 16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Abnormal BSN – Single MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to an abnormal BSN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP      B SP      A
Link Link
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
1 – 0 MSU
(FSN = 0, BSN = 0)
>
1 – 0 MSU
(FSN = 0, BSN = 7F)
>
1 – 0 MSU
(FSN = 0, BSN = 7F)
>
< 1 – 0 FISU
(FSN = 7F, BSN = 0)
| | | | | SP      B | | | SP      A | Link | | | Link | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | 1 – 0 | MSU
(FSN = 0, BSN = 0) | > | | | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | > | | | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | > | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 0) | +| | SP      B | | | SP      A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 0) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate a single MSU at B with abnormal BSN followed by retransmission of that MSU with normal BSN. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A responds with a positive acknowledgement and not detect link failure. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-------------------|-------|------------------------------|------|--|--|------|------|--|---|------|--|--|--|--|-------|------------------------------|-------|------------------------------|--|--|--|-------|----------------------------|--|--|--|-------|----------------------------|--|--|--|-------|----------------------------|--|--|--|--|--|---|-------|------------------------------| +| TEST NUMBER: 9.9 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.3/Q.703     STD: Fig. 16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Abnormal BSN – Two MSUs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to two consecutive MSUs with an MSU having normal BSN between them | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link < Link
1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 MSU
(FSN = 0, BSN = 7E)
1 – 0 MSU
(FSN = 0, BSN = 7F)
1 – 0 MSU
(FSN = 0, BSN = 7E)
< 1 – 0 SIOS
(FSN = 7F, BSN = 7F)
| | | | | SP B | | | SP A | Link | | < | Link | | | | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | 1 – 0 | MSU
(FSN = 0, BSN = 7E) | | | | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | 1 – 0 | MSU
(FSN = 0, BSN = 7E) | | | | | | < | 1 – 0 | SIOS
(FSN = 7F, BSN = 7F) | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | < | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 7E) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 7E) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate two consecutive MSUs at B with abnormal BSN with an MSU having normal BSN between them. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that all MSUs are discarded at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that A responds by taking the link out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------------|-------|------------------------------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|------------------------------|--|-------|------------------------------|---|--|--|--|-------|----------------------------|---|--|--|--|-------|----------------------------|---|--|--|--|--|--|---|-------| +| TEST NUMBER: 9.10 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.2/Q.703      STD: Fig. 16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unexpected FSN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the reception control response to an MSU with unexpected FSN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP BSP A
LinkLink
< 1 – 0FISU
(FSN = 7F, BSN = 7F)
1 – 0FISU
(FSN = 7F, BSN = 7F)
>
1 – 0MSU
(FSN = 0, BSN = 7F)
>
1 – 0MSU
(FSN = 2, BSN = 7F)
>
< 1 – 0FISU
(FSN = 7F, BSN = 0)
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | > | | | | 1 – 0 | MSU
(FSN = 2, BSN = 7F) | > | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 0, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | MSU
(FSN = 2, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU with unexpected FSN at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check A discards the MSU with unexpected FSN and does not send acknowledgement for that MSU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------|-------|------------------------------|------|--|--|------|------|--|---|------|--|--|--|--|-------|------------------------------|-------|------------------------------|---|--|--|--|--|---|-------|----------------------------|--|--|--|--|---|--|--|--|--|------|--|--|--|--|---|--|--|---|-------|-----------------------------| +| TEST NUMBER: 9.11 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.3/Q.703     STD: Fig. 15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Excessive delay of acknowledgement | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the transmission control response to the expiration of EDA timer T7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link < Link
1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
< 1 – 0 MSU
(FSN = 0, BSN = 7F)
•
T7 •
•
< 1 – 0 SIOS
(FSN = 0, BSN = 7F)
| | | | | SP B | | | SP A | Link | | < | Link | | | | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | • | | | | | T7 • | | | | | • | | | < | 1 – 0 | SIOS
(FSN = 0, BSN = 7F) | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | < | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | T7 • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS
(FSN = 0, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Suspend sending positive acknowledgement at B for more than T7 period. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that A sends SIOSs instead of retransmission of MSU after T7 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Timer T7 shall be in the range 0.5 secs to 2.0 secs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------------|-------|------------------------------|------|--|--|------|--|------|--|--|------|--|--|-------|------------------------------|---|--|--|--|--|--|---|-------|------------------------------|--|-------|-----------------------------|---|--|--|--|--|--|---|-------| +| TEST NUMBER: 9.12 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 6.2/Q.703 STD: Fig. 16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: FISU with FSN expected for MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check that the received FISU having FSN expected for MSU is discarded | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
1 – 0 FISU
(FSN = 7F, BSN = 7F)
>
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
1 – 0 FISU
(FSN = 0, BSN = 7F)
>
< 1 – 0 FISU
(FSN = 7F, BSN = 7F)
| | | | | SP B | | | SP A | | Link | | | Link | | | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | 1 – 0 | FISU
(FSN = 0, BSN = 7F) | > | | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU
(FSN = 0, BSN = 7F) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | FISU
(FSN = 7F, BSN = 7F) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an FISU with FSN expected for MSU at B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A discards the FISU and responds with an FISU with correct BSN. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-------------------|---|-------|--------|---|--|--|----|---|--|------|--|--|--|------|--|--|--|--|--|--|---|-------|------|--|--|-------|------|--|---|--|--|--|--|--|--|--|--|--|--------|--|--|--|--|--|---|-------|------|--|--| +| TEST NUMBER: 9.13 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 7/Q.703   STD: Fig. 16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Transmission and reception control (PCR) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Level 3 Stop command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To test the response to a Stop command | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 FISU
1 – 0 FISU >
: stop
< 1 – 0 SIOS
| | | | | SP | B | | | SP | A | | Link | | | | Link | | | | | | | < | 1 – 0 | FISU | | | 1 – 0 | FISU | | > | | | | | | | | | | : stop | | | | | | < | 1 – 0 | SIOS | | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | : stop | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Give Stop command at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check that A responds with link out of service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------------|--------------------------|-----|------|--|------|------|--|------|--|--|--|--|-------------------------|--|---|-------|-----|--|--|----|--|--|---|-------|-----|--|--|--|--------|--|--|--|--------------------------|--|---|-------|------| +| TEST NUMBER: 10.1 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Clause 9/Q.703     STD: Fig. 19 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Congestion Control | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Congestion abatement | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check the congestion abatement procedure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
: make congestion state
< 1 – 0 SIB
T5
< 1 – 0 SIB
•
•
: clear congestion state
< 1 – 0 FISU
| | | | | SP B | | SP A | Link | | Link | | | | | : make congestion state | | < | 1 – 0 | SIB | | | T5 | | | < | 1 – 0 | SIB | | | | •
• | | | | : clear congestion state | | < | 1 – 0 | FISU | +| | SP B | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | : make congestion state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | 1 – 0 | SIB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | T5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | | 1 – 0 | SIB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | •
• | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | : clear congestion state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | 1 – 0 | FISU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make congestion state at A and check A sends SIB.
(Implementation of congestion control is not specified.) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Check B receives SIBs at the interval of T5. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Clear congestion state at A and check A stops sending SIBs. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Timer T5 shall be in the range 80 ms to 120 ms. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------------|---|-------|-----|---|----|--|----|---|--|------|--|--|--|------|--|--|--|--|--|--|---|-------|-----|--|--|-------|-----|--|---|--|--|--|--|-------|-----|----|---|--|--|--|--|---|--|--|--|--|--|---|--|--|--|--|-------|-----|----|---|--|--|----|--|--|--|--|--|--|--|--|-------|------|--|---|--|--| +| TEST NUMBER: 10.2 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 9.2/Q.703   STD: Fig. 19 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Congestion Control | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Timer T7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check timer T7 is restarted at the reception of SIB (without expiring of T6) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 MSU
1 – 0 SIB >
1 – 0 SIB Ct >
•
•
1 – 0 SIB Bt > T6
1 – 0 FISU >
| | | | | SP | B | | | SP | A | | Link | | | | Link | | | | | | | < | 1 – 0 | MSU | | | 1 – 0 | SIB | | > | | | | | 1 – 0 | SIB | Ct | > | | | | | • | | | | | | • | | | | | 1 – 0 | SIB | Bt | > | | | T6 | | | | | | | | | 1 – 0 | FISU | | > | | | +| | SP | B | | | SP | A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | < | 1 – 0 | MSU | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIB | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIB | Ct | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIB | Bt | > | | | | T6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | FISU | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Generate an MSU at A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Generate SIBs at B with the time intervals of T5 for Ct, instead of positive acknowledgement. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Check that link remains in service during Ct. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Send FISU with positive acknowledgement from B after Bt expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Check that link remains in service. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | Ct = more than T7 and less than T6. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | Bt = less than T7. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | (Ct + Bt) is less than T6. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------------------|-------|------|------|--|--|------|--|------|--|--|------|--|--|--|--|---|-------|-----|----|-------|-----|---|--|--|-------|-----|---|--|--|--|---|--|--|--|--|---|--|--|--|-------|-----|---|--|--|--|---|--|--|--|--|---|--|--|--|-------|-----|---|--|--|--|--|---|-------| +| TEST NUMBER: 10.3 | | PAGE: 1 OF 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: 9.3/Q.703   STD: Fig. 19 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Congestion Control | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Timer T6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To check "Remote Congestion" Timer T6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Link in service | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED SIGNAL UNIT SEQUENCE:

SP B SP A
Link Link
< 1 – 0 MSU T6
1 – 0 SIB >
1 – 0 SIB >
•
•
1 – 0 SIB >
•
•
1 – 0 SIB >
< 1 – 0 SIOS
| | | | | SP B | | | SP A | | Link | | | Link | | | | | < | 1 – 0 | MSU | T6 | 1 – 0 | SIB | > | | | 1 – 0 | SIB | > | | | | • | | | | | • | | | | 1 – 0 | SIB | > | | | | • | | | | | • | | | | 1 – 0 | SIB | > | | | | | < | 1 – 0 | +| | SP B | | | SP A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Link | | | Link | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | MSU | T6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIB | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIB | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIB | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | • | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 – 0 | SIB | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | 1 – 0 | SIOS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION
  1. 1. Generate an MSU at A.
  2. 2. Generate SIB at B until Timer T6 expires.
  3. 3. Check link becomes out of service.
  4. 4. Timer T6 shall be in the range 3 secs to 6 secs (8 to 12 secs for 4.8 kbit/s).
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +###### **MTP, LEVEL 2** + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------|--| +| TEST NUMBER: 10.4 | | PAGE: 1 OF 1 | | +| REFERENCE: 9.3/Q.703      STD: Fig. 19 | | | | +| TITLE: Congestion Control | | | | +| SUBTITLE: Congestion and RTB empty | | | | +| PURPOSE: Check first receipt of LSSU with SI "B" does not start Timer T6 or T7 if RTB empty (i.e. does not cause link failure) | | | | +| PRE-TEST CONDITIONS: Link in service | | | | +| CONFIGURATION: 1 | | TYPE OF TEST: VAT | | +| EXPECTED SIGNAL UNIT SEQUENCE:

Link SP B
: make
congestion
state
1 – 0 SIB
>
Link SP A
: make RTB empty
Check T6, T7 not started
(i.e. link does not fail for
period > T6 from receipt
of first SIB)
| | | | +| TEST DESCRIPTION | | | | +| 1. | Make RTB of A empty | | | +| 2. | Make congestion state at B and ensure B sends at least one SIB (the multiple sending of SIB from SPB is not critical to this test). | | | +| 3. | Check A receives SIB | | | +| 4. | Confirm T6, T7 are not started on receipt of SIB (i.e. link stays in service for period > T6) | | | + + + +## 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.783-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.783-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d13a1aca5f58f66b46b20084b73931d31b86aee7 --- /dev/null +++ b/marked/Q/T-REC-Q.783-198811-I_PDF-E/raw.md @@ -0,0 +1,2029 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.783** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**SPECIFICATIONS OF SIGNALLING SYSTEM No. 7** + +--- + +**TUP TEST SPECIFICATION** + +**ITU-T Recommendation Q.783** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.783 was published in Fascicle VI.9 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. + +# **TUP TEST SPECIFICATION** + +## **1 Introduction** + +This Recommendation contains a set of detailed tests for the Signalling System No. 7 Telephony User Part (TUP). These tests are intended to validate the protocol specified in Q.721-Q.724 Recommendations. This Recommendation conforms to Q.780 Recommendations which describes the basic rules of the test specification. + +## **2 General principles of TUP tests** + +The TUP tests aim at testing TUP protocol conformance in a given implementation. The tests are described as "Validation" tests or "Validation" and "Compatibility" tests. Each test description indicates in the field "type of test" whether the test is "Validation" or "Validation" and "Compatibility". As the TUP also describes the required call control actions resulting from TUP message transfer the TUP tester also checks the result of those call control actions, e.g. that speech/information transfer is possible. + +## **3 Test configuration** + +A stable signalling relation is required between "SP A" and "SP B" in order to effectively test the TUP. In addition telephony circuits are required for some of the tests. + +## **4 TUP test list** + +All tests may be validation tests. Tests marked "\*" are compatibility tests. Tests marked "fs" are for further study. + +### *1 Circuit supervision* + +- \* 1.1 Non allocated circuits +- 1.2 Reset of circuits + - 1.2.1 RSC received on an idle circuit + - 1.2.2 RSC sent on an idle circuit + - 1.2.3 Group reset received + - 1.2.4 Group reset sent +- 1.3 Blocking of circuits + - 1.3.1 Group blocking/unblocking + - 1.3.1.1 HGB received + - 1.3.1.2 HGB sent + - \* 1.3.1.3 MGB received + - \* 1.3.1.4 MGB sent + - 1.3.2 Circuit blocking/unblocking + - \* 1.3.2.1 BLO received + - \* 1.3.2.2 BLO sent + +- \* 1.3.2.3 Circuit blocking from both ends; removal of blocking from one end +- 1.3.2.4 Interruption for FDM circuits +- 1.4 Continuity check test call + - \* 1.4.1 CCTC received: successful + - \* 1.4.2 CCTC sent: successful + - 1.4.3 CCTC received: unsuccessful + - 1.4.4 CCTC sent: unsuccessful +- 1.5 Receipt of unreasonable signalling information + - 1.5.1 Received +- 2 *Normal call set-up* + - 2.1 Both way circuit selection + - \* 2.1.1 IAM sent by controlling SP + - \* 2.1.2 IAM sent by non controlling SP + - 2.2 Called address sending + - \* 2.2.1 "en bloc" operation + - \* 2.2.2 Overlap operation + - 2.3 Successful call set-up + - 2.3.1 Ordinary call (with various ACM and ANS) + - \* 2.3.2 Call switched via satellite + - \* 2.3.3 Test for echo suppressor call set-up + - \* 2.3.4 Blocking and unblocking during a call (initiated) + - \* 2.3.5 Blocking and unblocking during a call (received) + +## 3 *Normal call release* + +- \* 3.1 Calling party clears: before ACM +- \* 3.2 Calling party clears: before ANS +- \* 3.3 Calling party clears: after ANS +- \* 3.4 Calling party clears: after CLEAR BACK +- \* 3.5 Reanswer + +## 4 *Unsuccessful set-up* + +- 4.1 SEC + - 4.1.1 SEC received + +- 4.1.2 SEC sent +- 4.2 CGC + - 4.2.1 CGC received + - 4.2.2 CGC sent +- 4.3 NNC + - 4.3.1 NNC received + - 4.3.2 NNC sent +- 4.4 ADI + - \* 4.4.1 ADI received + - \* 4.4.2 ADI sent +- 4.5 CFL + - 4.5.1 CFL received + - 4.5.2 CFL sent +- 4.6 SSB + - \* 4.6.1 SSB received + - \* 4.6.2 SSB sent +- 4.7 UNN + - \* 4.7.1 UNN received + - \* 4.7.2 UNN sent +- 4.8 LOS + - 4.8.1 LOS received + - 4.8.2 LOS sent +- 4.9 SST + - 4.9.1 SST received + - 4.9.2 SST sent +- 4.10 ACB + - 4.10.1 ACB received + - 4.10.2 ACB sent +- 4.11 DPN + - 4.11.1 DPN received + - 4.11.2 DPN sent + +## 5 *Abnormal situation during a call* + +5.1 Inability to release in response to a CLF + +5.2 Inability to release in response to a backward signal + +5.3 Timers + +5.3.1 T2 + +5.3.2 T3 + +5.3.3 T4 + +5.3.4 T5 + +5.3.5 T6 + +\* 5.3.6 ANS signal not received (Q.118 Timer) + +\* 5.3.7 Delay in clearing by calling party (Q.118 Timer) + +5.4 Reset of circuits during a call + +5.4.1 Of an outgoing circuit + +5.4.2 Of an incoming circuit + +5.5 Receipt of unreasonable signalling information + +5.5.1 (Now test No. 1.5.1) + +fs 5.5.2 Received + +5.6 Interruption of signalling relation + +## 6 *Special call set-up* + +6.1 Continuity check call + +\* 6.1.1 COT applied on an outgoing circuit + +\* 6.1.2 COT applied on previous circuit + +\* 6.1.3 COT on a satellite circuit + +6.1.4 Calling party clears during a COT + +\* 6.1.5 Delay of through connect + +6.1.6 COT unsuccessful + +6.1.7 COT received on incoming circuit + +6.2 Automatic repeat attempt + +6.2.1 Dual seizure + +6.2.2 Circuit reset + +6.2.3 Reception of unreasonable signal information + +- \* 6.2.4 Blocking of the circuit +- 6.2.5 Continuity check failure +- 6.3 Dual seizure + - 6.3.1 Dual seizure for controlling side + +## 7 *Supplementary services* + +- fs 7.1 CUG +- fs 7.2 User access to the calling line identity +- fs 7.3 User access to the called line identity +- fs 7.4 Redirection of calls +- fs 7.5 CCBS +- fs 7.6 Network access to calling line identity + +## 8 *Performance tests* + +*Note* - For further study. + +![Diagram showing two signaling points, SP A (under test) and SP B, connected by two parallel lines with arrows indicating signaling relations. Note 1 is placed between the lines.](d793cf7c174b89eb024d132f00679787_img.jpg) + +The diagram shows two rectangular boxes, SP A and SP B, connected by two horizontal lines. SP A is on the left and has the text "(under test)" below it. SP B is on the right. The top line has an arrow pointing from SP A to SP B. The bottom line has an arrow pointing from SP B to SP A. The text "Note 1" is centered between the two lines. In the bottom right corner of the diagram area, there is a small code "TI109850-48". + +Diagram showing two signaling points, SP A (under test) and SP B, connected by two parallel lines with arrows indicating signaling relations. Note 1 is placed between the lines. + +*Note 1* - The arrows indicate a signalling relation, and any necessary telephone circuits. + +**FIGURE 1/Q.783** +**Test configuration for TUP level 4 tests** +**Configuration 1** + +## **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER : 1.1 | | | +| REFERENCE : | | | +| TITLE : Circuit supervision | | | +| SUBTITLE : Non-allocated circuits | | | +| PURPOSE : To verify that on receipt of a CIC relating to a circuit which does not exist, SP A will discard the message and alert maintenance personnel | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point B such that the CIC identifies a circuit that does not exist between SP A and SP B | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | +| EXPECTED MESSAGE SEQUENCE :

SP A < IAM SP B
| | | +| TEST DESCRIPTION | | | +| 1. | Arrange for SP B to send an initial address message.
Record the message sequence using a signal monitor. | | +| 2. | CHECK A: IS THE CIRCUIT IDLE ? | | +| 3. | CHECK B: WAS THE MESSAGE SEQUENCE AS SHOWN ABOVE? | | +| 4. | CHECK C: WAS THE INDICATION GIVEN TO THE MAINTENANCE PERSONNEL? | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------| +| TEST NUMBER : 1.2.1 | | | +| REFERENCE : Q.724 § 1.15.1 | | | +| TITLE : Reset of circuits | | | +| SUBTITLE : RSC received on an idle circuit | | | +| PURPOSE : To verify that on receipt of a reset circuit signal SP A will respond by sending a release guard signal | | | +| PRE-TEST CONDITIONS : The circuit is idle | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B

<
RSC
RLG
>
| | | +| TEST DESCRIPTION | | | +|
  1. 1. Arrange for SP B to send a reset-circuit signal.
    Record the message sequence using a signal monitor.

  2. 2. CHECK A: IS THE CIRCUIT IDLE ?

  3. 3. CHECK B : WAS THE MESSAGE SEQUENCE AS ABOVE ?
| | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|-----|---|--|--|---|-----| +| TEST NUMBER : 1.2.2 | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.15.1 | | | | | | | | | | | | +| TITLE : Reset of circuits | | | | | | | | | | | | +| SUBTITLE : RSC sent on an idle circuit | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate reset-circuit signal | | | | | | | | | | | | +| PRE-TEST CONDITIONS : The circuit is idle | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
RSC >
< RLG

| | | SP A | | SP B | RSC | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | +| RSC | > | | | | | | | | | | | +| | < | RLG | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | +| 1. | Arrange for SP A to send a reset-circuit signal.

Record the message sequence using a signal monitor. | | | | | | | | | | | +| 2. | CHECK A: IS THE CIRCUIT IDLE ? | | | | | | | | | | | +| 3. | CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|--|---|-----|--|---|-----|-----|---|--| +| TEST NUMBER: 1.2.3 | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.15.2 | | | | | | | | | | | | | | | +| TITLE : Reset of circuits | | | | | | | | | | | | | | | +| SUBTITLE : Group reset received | | | | | | | | | | | | | | | +| PURPOSE : To verify that on receipt of two circuit group reset message within a period of 5 seconds, SP A will respond by sending a circuit reset acknowledge message | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
< GRS
< GRS
GRA >

| | | SP A | | SP B | | < | GRS | | < | GRS | GRA | > | | +| SP A | | SP B | | | | | | | | | | | | | +| | < | GRS | | | | | | | | | | | | | +| | < | GRS | | | | | | | | | | | | | +| GRA | > | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send two circuit group reset messages within a period of 5 seconds.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | +| 2. | CHECK A : IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | +| 3. | CHECK B : WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----|---|--|----|---|-----|--|--|--|--|-----|--|--|--|--|--|--|--|-----|--| +| TEST NUMBER : 1.2.4 | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.15.2 | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Reset of circuits | | | | | | | | | | | | | | | | | | | | | | | +| SUBTILE : Group reset sent | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate a circuit group reset message | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
GRS
GRS
GRA
| | | SP | A | | SP | B | GRS | | | | | GRS | | | | | | | | GRA | | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | +| GRS | | | | | | | | | | | | | | | | | | | | | | | +| GRS | | | | | | | | | | | | | | | | | | | | | | | +| | | | GRA | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send two circuit group reset messages within a period of 5 seconds. Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A : IS THE CIRCUIT GROUP IDLE ? | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|--|---|-----|--|---|-----|-----|---|--|--|---|-----|--|---|-----|-----|---|--| +| TEST NUMBER : 1.3.1.1 | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5.2 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Group blocking/unblocking | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : HGB received | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the hardware failure group blocking procedure can be correctly initiated | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
< HGB
< HGB
HBA >
< HGU
< HGU
HUA >
| | | SP A | | SP B | | < | HGB | | < | HGB | HBA | > | | | < | HGU | | < | HGU | HUA | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | +| | < | HGB | | | | | | | | | | | | | | | | | | | | | | +| | < | HGB | | | | | | | | | | | | | | | | | | | | | | +| HBA | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | HGU | | | | | | | | | | | | | | | | | | | | | | +| | < | HGU | | | | | | | | | | | | | | | | | | | | | | +| HUA | > | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send two hardware failure oriented group blocking messages within a period of 5 seconds. Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: VERIFY THAT CAN ONLY BE ORIGINATED FROM SP B ON THE CIRCUITS INDICATED BY THE RANGE FIELD IN THE HGB MESSAGE | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send two hardware failure oriented group unblocking messages within a period of 5 seconds. | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT A CALL CAN BE ORIGINATED FROM EITHER SP ON THE CIRCUITS INDICATED BY THE RANGE FIELD | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|-----|---|--|-----|---|--|--|---|-----|---------|-------|--|-----|---|--|--|---|-----| +| TEST NUMBER : 1.3.1.2 | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5.2 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Group blocking/unblocking | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : HGB sent | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate both hardware failure oriented group blocking messages and hardware failure oriented group unblocking messages | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
HGB >
HGB >
< HGB

HGU

>
HGU >
< HUA
| | | SP A | | SP B | HGB | > | | HGB | > | | | < | HGB |
HGU |
> | | HGU | > | | | < | HUA | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | +| HGB | > | | | | | | | | | | | | | | | | | | | | | | | +| HGB | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | HGB | | | | | | | | | | | | | | | | | | | | | | +|
HGU |
> | | | | | | | | | | | | | | | | | | | | | | | +| HGU | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | HUA | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send two hardware failure oriented group blocking messages within a period of 5 seconds. Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: VERIFY THAT A CALL CAN ONLY BE ORIGINATED FROM SP A ON THE CIRCUITS INDICATED BY THE RANGE FIELD IN THE HGB MESSAGE | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP A to send two hardware failure oriented group unblocking messages within a period of 5 seconds. | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT A CALL CAN BE ORIGINATED FROM EITHER SP ON THE CIRCUITS INDICATED BY THE RANGE FIELD | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|--|---|-----|--|---|-----|-----|---|--|--|---|-----|--|---|-----|-----|---|--| +| TEST NUMBER : 1.3.1.3 | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5.1 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Group blocking/unblocking | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : MGB received | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the maintenance oriented group blocking procedure can be correctly initiated | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
< MGB
< MGB
MBA >
< MGU
< MGU
MUA >
| | | SP A | | SP B | | < | MGB | | < | MGB | MBA | > | | | < | MGU | | < | MGU | MUA | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | +| | < | MGB | | | | | | | | | | | | | | | | | | | | | | +| | < | MGB | | | | | | | | | | | | | | | | | | | | | | +| MBA | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | MGU | | | | | | | | | | | | | | | | | | | | | | +| | < | MGU | | | | | | | | | | | | | | | | | | | | | | +| MUA | > | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send two maintenance oriented group blocking messages within a period of 5 seconds. Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: VERIFY THAT A CALL CAN ONLY BE ORIGINATED FROM SP B ON THE CIRCUITS INDICATED BY THE RANGE FIELD IN THE MGB MESSAGE | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP B to send two maintenance oriented group unblocking messages within a period of 5 seconds. | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT A CALL CAN BE ORIGINATED FROM EITHER SP ON THE CIRCUITS INDICATED BY THE RANGE FIELD | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|-----|---|--|-----|---|--|--|---|-----|---------|-------|--|-----|---|--|--|---|-----| +| TEST NUMBER : 1.3.1.4 | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5.1 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Group blocking/unblocking | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : MGB sent | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate both maintenance oriented group blocking messages and maintenance oriented group unblocking messages | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
MGB >
MGB >
< MGA

MGU

>
MGU >
< MUA
| | | SP A | | SP B | MGB | > | | MGB | > | | | < | MGA |
MGU |
> | | MGU | > | | | < | MUA | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | +| MGB | > | | | | | | | | | | | | | | | | | | | | | | | +| MGB | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | MGA | | | | | | | | | | | | | | | | | | | | | | +|
MGU |
> | | | | | | | | | | | | | | | | | | | | | | | +| MGU | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | MUA | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP A to send two maintenance oriented group blocking messages within a period of 5 seconds. Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: VERIFY THAT A CALL CAN ONLY BE ORIGINATED FROM SP A ON THE CIRCUITS INDICATED BY THE RANGE FIELD IN THE MGB MESSAGE | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for SP A to send two maintenance oriented group unblocking messages within a period of 5 seconds. | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT A CALL CAN BE ORIGINATED FROM EITHER SP ON THE CIRCUIT INDICATED BY THE RANGE FIELD | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER : 1.3.2.1 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5.1 | | | | | | | | | | | | | | | | | | +| TITLE : Group blocking/unblocking | | | | | | | | | | | | | | | | | | +| SUBTITLE : BLO received | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the blocking/unblocking procedure can be correctly initiated | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
< BLO
BLA >
< UBL
UBA >
| | | SP A | | SP B | | < | BLO | BLA | > | | | < | UBL | UBA | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | < | BLO | | | | | | | | | | | | | | | | +| BLA | > | | | | | | | | | | | | | | | | | +| | < | UBL | | | | | | | | | | | | | | | | +| UBA | > | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a blocking signal.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | +| 2. | CHECK A: VERIFY THAT A CALL CAN ONLY BE ORIGINATED FROM SP B ON THIS CIRCUIT | | | | | | | | | | | | | | | | | +| 3. | Arrange SP B to send an unblocking signal. | | | | | | | | | | | | | | | | | +| 4. | CHECK B: VERIFY THAT A CALL CAN BE ORIGINATED FROM EITHER EXCHANGE ON THIS CIRCUIT | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|--|------|-----|---|--|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER : 1.3.2.2 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5.1 | | | | | | | | | | | | | | | | | | +| TITLE : Circuit blocking/unblocking | | | | | | | | | | | | | | | | | | +| SUBTITLE : BLO sent | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate blocking messages | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
BLO >
< BLA
UBL >
< UBA
| | | SP A | | SP B | BLO | > | | | < | BLA | UBL | > | | | < | UBA | +| SP A | | SP B | | | | | | | | | | | | | | | | +| BLO | > | | | | | | | | | | | | | | | | | +| | < | BLA | | | | | | | | | | | | | | | | +| UBL | > | | | | | | | | | | | | | | | | | +| | < | UBA | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|

1.


2.

3.


4.

5.

|

Arrange for SP A to send a blocking signal.
Record the message sequence using a signal monitor.

CHECK A: VERIFY THAT A CALL CAN ONLY BE ORIGINATED FROM SP A ON THIS CIRCUIT

Arrange for SP A to send an unblocking signal.

CHECK B: VERIFY THAT A CALL CAN BE ORIGINATED FROM EITHER SP ON THIS CIRCUIT

CHECK C: WAS THE MESSAGE SEQUENCE AS SHOWN ABOVE ?

| | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|-----|---|--|----|---|-----|--|--|--|--|--|--|--|-----|--|--|--|--|-----|--|-----|--|--|--|--|-----|--|--|--|--|--|--|--|-----|--|--|--|--|-----|--|-----|--|--|--|--| +| TEST NUMBER : 1.3.2.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Circuit blocking/unblocking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Blocking from both ends : removal of blocking from one end | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the blocking/unblocking procedure can be correctly initiated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
BLO
BLA
BLO
BLA
UBL
UBA
UBL
UBA
| | | SP | A | | SP | B | BLO | | | | | | | | BLA | | | | | BLO | | BLA | | | | | UBL | | | | | | | | UBA | | | | | UBL | | UBA | | | | | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BLO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | BLA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | BLO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BLA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UBL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | UBA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | UBL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UBA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Arrange for SP A to send a blocking signal.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: VERIFY THAT A CALL CAN ONLY BE ORIGINATED FROM SP A ON THIS CIRCUIT
  3. 3. Arrange for SP B to send an unblocking signal.
  4. 4. CHECK B: VERIFY THAT A CALL CANNNOT BE ORIGINATED ON THIS CIRCUIT EITHER SP
  5. 5. Arrange for SP A to send an unblocking signal.
  6. 6. CHECK C: VERIFY THAT A CALL CAN ONLY BE ORIGINATED BY SP B
  7. 7. Arrange for SP B to send an unblocking signal.
  8. 8. CHECK D : WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----|---|--|----|---|-----|--|---|--|--|--|--|---|-----|--|-----|--|---|--|--|--|--|---|-----|--| +| TEST NUMBER : 1.3.2.4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 9.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Circuit blocking/unblocking | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Interruption from FDM circuits | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that an interruption of the pilot in FDM system causes a blocking signal to be sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : The signalling points must be linked by a transmission system using FDM | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
BLO >
< BLA
UBL >
< UBA
| | | SP | A | | SP | B | BLO | | > | | | | | < | BLA | | UBL | | > | | | | | < | UBA | | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| BLO | | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | BLA | | | | | | | | | | | | | | | | | | | | | | | | | +| UBL | | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | UBA | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for the reception of the pilot signal at SP A to be interrupted more than 4-15 seconds. Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: CONFIRM THAT A CALL CANNOT BE INITIATED BY EITHER SP | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Arrange for the interruption of the pilot tone to be terminated. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: CONFIRM THAT A CALL CAN BE INITIATED BY EITHER SP AFTER A PERIOD OF 4-15 SECONDS | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|--|--|------------|--|--|--|--|---|-----|-----|---|--| +| TEST NUMBER : 1.4.1 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 7.5 | | | | | | | | | | | | | | | | | | | | | +| TITLE : Continuity check test call | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : CCTC received : Successful | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the continuity test call procedure can be correctly performed | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Circuit must be idle | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
< CCR
Check tone
< CLF
RLG >
| | | SP A | | SP B | | < | CCR | | | Check tone | | | | | < | CLF | RLG | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| | < | CCR | | | | | | | | | | | | | | | | | | | +| | | Check tone | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | +| | < | CLF | | | | | | | | | | | | | | | | | | | +| RLG | > | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate the continuity test call procedure at SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-----------------|-----|---|--|----|---|--|-----|---|--|--|--|------------|--|--|--|--|--|--|--|--|--|-----|---|--|--|--|--|---|-----|--| +| TEST NUMBER : 1.4.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 7.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Continuity check test call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : CCTC send : successful | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the continuity test call procedure can be correctly performed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Circuit must be idle | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
CCR >
Check tone
CLF >
< RLG
| | | SP | A | | SP | B | | CCR | > | | | | Check tone | | | | | | | | | | CLF | > | | | | | < | RLG | | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CCR | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Check tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Initiate the continuity test call procedure at SP A
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER : 1.4.3 | | | +| REFERENCE : Q.724 § 7.5 | | | +| TITLE : Continuity check test call | | | +| SUBTITLE : CCTC received : unsuccessful | | | +| PURPOSE : To verify that the continuity check procedure can be correctly received | | | +| PRE-TEST CONDITIONS : Ensure that no backward check tone is detected within the specified time out | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B

Image: Sequence diagram showing message exchange between SP B and SP A. SP B sends CCR and Check tone. SP A responds with CCF. This repeats twice with 1-3 minute intervals. After the second failure, maintenance staff are alerted at SP A.

 sequenceDiagram     participant A as SP A     participant B as SP B     Note over B: CCR
Check tone B-->>A: A-->>B: CCF Note right of B: 1-3 minutes (T10) Note over B: CCR
Check tone B-->>A: A-->>B: CCF Note left of A: Maintenance staff alerted Note right of B: 1-3 minutes (T10) Note over B: CCR
Check tone B-->>A: A-->>B: CCF
| | | +| TEST DESCRIPTION | | | +|

1.


2.

3.


4.

5.

|

Initiate the continuity test call procedure at SP B.
Record the message sequence using a signal monitor.

CHECK A: WAS THE SECOND CONTINUITY CHECK INITIATED WITHIN 1 TO 3 MINUTES?

CHECK B: WERE THE MAINTENANCE STAFF ALERTED ON FAILURE OF THE SECOND CONTINUITY CHECK?

CHECK C: WAS THE CHECK REPEATED AT INTERVALS OF 1 TO 3 MINUTES?

CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?

| | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------| +| TEST NUMBER : 1.4.4 | | | +| REFERENCE : Q.724 § 7.5.3 | | | +| TITLE : Continuity check test call | | | +| SUBTITLE : CCTC sent : unsuccessful | | | +| PURPOSE : To verify that the continuity test call procedure can be correctly invoked | | | +| PRE-TEST CONDITIONS : Ensure that no backward tone is detected within the specified timeout | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | +|

EXPECTED MESSAGE SEQUENCE:

SP    A SP    B

Image: Sequence diagram showing message exchange between SP A and SP B. SP A sends CCR, Check tone, CCF, waits 1-3 minutes (T10), sends CCR, Check tone, CCF. SP B receives CCR, Check tone, CCF, waits 1-3 minutes (T10), receives CCR, Check tone, CCF. After the second CCF from SP A, SP B sends a message to 'Maintenance staff alerted'.

 sequenceDiagram     participant SP_A as SP A     participant SP_B as SP B     Note left of SP_A: T10 1-3 minutes     SP_A->>SP_B: CCR     SP_A->>SP_B: Check tone     SP_A->>SP_B: CCF     Note right of SP_B: T10 1-3 minutes     SP_B->>SP_A: CCR     SP_B->>SP_A: Check tone     SP_B->>SP_A: CCF     Note left of SP_A: Maintenance staff alerted     
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate the continuity test call procedure at SP A. Record the message sequence using a signal monitor. | | +| 2. | CHECK A: WAS THE SECOND CONTINUITY CHECK INITIATED WITHIN 1 TO 3 MINUTES?... | | +| 3. | CHECK B: WERE THE MAINTENANCE STAFF ALERTED ON FAILURE OF THE SECOND CONTINUITY CHECK?.... | | +| 4. | CHECK C: WAS THE CHECK REPEATED AT INTERVALS OF 1 TO 3 MINUTES?.... | | +| 5. | CHECK D: WAS THE MESSAGE SEQUENCES AS ABOVE?... | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-----------------|------|------|--|------|----|--|--|--|--|--|---|-----|--|-----|---|--|----|--|--|--|--|--|---|-----|----|--|--|--|--|--|---|-----|--|-----|---|--| +| TEST NUMBER : 1.5.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 6.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Receipt of unreasonable information | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the action taken by a signalling point upon receipt of unreasonable signalling information is as stated in Q.724 § 6.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS :

a) Arrange the data in signalling point B such that CLF, RLG, and UBL messages may be initiated
b) The circuit should be idle and unblocked | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP ASP B
a)
< CLF
RLG >
b)
< RLG
c)
< UBL
UBA >
| | | | SP A | | SP B | a) | | | | | | < | CLF | | RLG | > | | b) | | | | | | < | RLG | c) | | | | | | < | UBL | | UBA | > | | +| | SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | RLG | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | UBL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | UBA | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Arrange for SP B to send a clear forward signal. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE MESSAGE SEQUENCE AS IN a) ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Arrange for SP B to send a release guard signal. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WAS THE MESSAGE SEQUENCE AS IN b) ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | Arrange for SP B to send an unblocking signal. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK E: IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9. | CHECK F: WAS THE MESSAGE SEQUENCE AS IN c) ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +*Note - This test covers only some of the ambiguous messages which could be received* + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------|----|--------------|--|----|---|--|-----|--|--|--|--|--|--|--|-----|--|--|--|--|--------------|--|--|--|--|-----|--|--------|--|--|--------|--|-----|--|--|--|--|--|--|--|-----| +| TEST NUMBER : 2.1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Both way circuit selection | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : IAM sent by controlling SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that signalling point A can initiate an outgoing call on a circuit capable of bothway operation when the controlling SP is A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS :

a) Called termination is free
b) Circuit selected is capable of bothway operation
c) Circuit selected is as in test number 2.1.2
d) SP A is the controlling signalling point | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM
ACM
Ringing tone
ANC
Speech Speech
CLF
RLG
| | | SP | A | | SP | B | | IAM | | | | | | | | ACM | | | | | Ringing tone | | | | | ANC | | Speech | | | Speech | | CLF | | | | | | | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Speech | | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A TO SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: CAN RINGING TONE BE HEARD ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | The called party should answer the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: IS SPEECH POSSIBLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | The calling party should clear the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------|------|--|------|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--|-----|---|--|--|---|-----| +| TEST NUMBER : 2.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Bothway circuit selection | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : IAM sent by non-controlling SP | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that signalling point A can initiate an outgoing call on a circuit capable of bothway when the non-controlling SP is A | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS :
a) Called termination is free
b) Circuit selected is capable of bothway operation
c) Circuit selected is as in test number 2.1.1
d) SP B is the controlling signalling point | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM >
< ACM
Ringing tone
< ANC
Speech
CLF >
< RLG
| | | SP A | | SP B | IAM | > | | | < | ACM | | | Ringing tone | | < | ANC | Speech | | | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANC | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: CAN RINGING TONE BE HEARD? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | The called party should answer the call. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: IS SPEECH POSSIBLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | The calling party should clear the call. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: IS THE CIRCUIT IDLE ? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE ? | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------|------|--|------|--|--------|--|-----|--------|-----|--|-------|--------------|--|--------|-----|--------|-------|--------|--|--------|--|-----|--------|-----| +| TEST NUMBER : 2.2.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Called address sending | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : "EN BLOC" operation | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that a call can be successfully established (all included in the IAM) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS :

a) Called termination is free
b) The exchange data is arranged such that all digits are included in the IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP ASP B
----->
IAM<-----ACM
-----Ringing tone
<-----ANC
Speech-----Speech
----->
CLF<-----RLG
| | | SP A | | SP B | | -----> | | IAM | <----- | ACM | | ----- | Ringing tone | | <----- | ANC | Speech | ----- | Speech | | -----> | | CLF | <----- | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| | -----> | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | <----- | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | ----- | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | +| | <----- | ANC | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | ----- | Speech | | | | | | | | | | | | | | | | | | | | | | | | | +| | -----> | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | <----- | RLG | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. Make a call from SP A to SP B.
Record the message sequence using a signal monitor.
2. CHECK A: IS RINGING TONE BE HEARD?....
3. The called party should answer the call.
4. CHECK B: IS SPEECH POSSIBLE ?.....
5. The calling party should clear the call.
6. CHECK C: IS THE CIRCUIT IDLE ?.....
7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE ?.....
8. For validation testing repeat this test in the reverse direction

Where SPA is in a position to know, by digit analysis that the final digit has been sent. Confirm that an End-of-pulsing (ST) signal is included in the IAM. | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|---|--|-----|---|--|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER : 2.2.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Called address sending | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Overlap operation (with SAM and SAO) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that signalling point A can initiate a call using an IAM followed by SAM and a SAO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS :
a) Called termination is free
b) The signalling point data is arranged such that digits are generated in a IAM followed by a SAM and a SAO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM 〉
SAM 〉
SAO 〉
〈 ACM
Ringing tone
〈 ANC
Speech Speech
CLF 〉
〈 RLG
| | | SP A | | SP B | IAM | 〉 | | SAM | 〉 | | SAO | 〉 | | | 〈 | ACM | | | Ringing tone | | 〈 | ANC | Speech | | Speech | CLF | 〉 | | | 〈 | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SAM | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SAO | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. CHECK A: IS RINGING TONE HEARD?
  3. The called party should answer the call.
  4. CHECK B: IS SPEECH POSSIBLE ?
  5. The calling party should clear the call.
  6. CHECK C: IS THE CIRCUIT IDLE ?
  7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE ?
  8. For validation testing repeat this test in the reverse direction.

Note - The message flown may not be as above
(There may be various SAMs and SAOs).

Where SPA is in position to know by digit analysis that the final digit has been sent. Confirm that an end-of-pulsing (ST) signal is included in the last address message.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------|------|--|------|-----|--|--|--|--|-----|--|--|--------------|--|--|-----|--------|--|--------|-----|--|--|--|--|-----| +| TEST NUMBER : 2.3.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.6 and 1.10 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE :Successful call set-up | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Ordinary call (with various ACM and ANS) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that a call can be successful completed using various combinations of address complete messages and answer messages | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM
ACM
Ringing tone
ANC
Speech Speech
CLF
RLG
| | | SP A | | SP B | IAM | | | | | ACM | | | Ringing tone | | | ANC | Speech | | Speech | CLF | | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. CHECK A: CAN RINGING TONE BE HEARD?
  3. The called party should answer the call.
  4. CHECK B: IS SPEECH POSSIBLE ?
  5. The calling party should clear the call.
  6. CHECK C: IS THE CIRCUIT IDLE ?
  7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE ?
  8. Repeat steps 1-7 with all combinations of bits A&B in the address complete message.
  9. Repeat steps 1-8 with ANC replaced with an ANN.
  10. Repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------| +| TEST NUMBER : 2.3.2 | | | +| REFERENCE : Q.724 § 1 | | | +| TITLE :Successful call set-up | | | +| SUBTITLE : Call switched via a satellite | | | +| PURPOSE : To verify the satellite indicator in the initial address message is correctly set | | | +| PRE-TEST CONDITIONS :
a) Called termination is free
b) The signalling point data is arranged such that the call is switched via satellite connection or has a satellite connection already included in the path | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | +| EXPECTED MESSAGE SEQUENCE :
    SP A                                         SP B     IAM  -------------------------------------->         <--------------------------------------  ACM                                                  Ringing tone         <--------------------------------------  ANC     Speech                                        Speech     CLF  -------------------------------------->         <--------------------------------------  RLG 
| | | +| TEST DESCRIPTION | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE ?
  5. 5. The calling party should clear the call.
  6. 6. CHECK C: IS THE CIRCUIT IDLE ?
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE ?
  8. 8. CHECK E: WAS THE SATELLITE INDICATOR BIT IN THE IAM SET TO 1?
  9. 9. For validation testing repeat this in the reverse direction?
| | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER : 2.3.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 11 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Successful call set-up | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Test for echo suppressor call set-up | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that a call can be successfully established with the inclusion of echo suppressors | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS :
a) Called termination is free
b) The signalling point data is arranged such that the call is routed over a route requiring echo suppressors or already has an echo suppressor included in the connection | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM >
< ACM
Ringing tone
< ANC
Speech Speech
CLF >
< RLG
| | | SP A | | SP B | IAM | > | | | < | ACM | | | Ringing tone | | < | ANC | Speech | | Speech | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANC | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. CHECK C: IS ECHO PERCEIVED BY EITHER PARTY?
  6. 6. The calling party should clear the call.
  7. 7. CHECK D: IS THE CIRCUIT IDLE?
  8. 8. CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE?
  9. 9. CHECK F: WAS THE MESSAGE INDICATOR BIT G (OUTGOING HALF ECHO SUPPRESSOR INCLUDED) IN THE IAM SET TO 1?
  10. 10. CHECK G: WAS THE MESSAGE INDICATOR BIT D (INCOMING HALF ECHO SUPPRESSOR INCLUDED) IN THE ACM SET TO 1?
  11. 11. For validation testing repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|--|--|--|--|-----|--|--|--------------|--|--|-----|--------|--|--------|-----|--|--|--|--|-----|-----|--|--|--|--|-----|-----|--|--|--|--|-----| +| TEST NUMBER : 2.3.4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Successful call set-up | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Blocking and unblocking during a call (initiated) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the circuit blocking and unblocking procedure can be correctly initiated during a call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :
SP A SP B
IAM
ACM
Ringing tone
ANC
Speech Speech
BLO
BLA
CLF
RLG
UBL
UBA
| | | SP A | | SP B | IAM | | | | | ACM | | | Ringing tone | | | ANC | Speech | | Speech | BLO | | | | | BLA | CLF | | | | | RLG | UBL | | | | | UBA | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BLO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | BLA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UBL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | UBA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: CAN RINGING TONE BE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. SP A should initiate circuit blocking relating to the circuit used for this call.
  6. 6. CHECK C: IS SPEECH STILL POSSIBLE?
  7. 7. The calling party should clear the call.
  8. 8. CHECK D: VERIFY THAT A CALL CAN ONLY BE ORIGINATED ON THIS CIRCUIT BY SPA?
  9. 9. SP A should send an unblocking signal.
  10. 10. CHECK E: VERIFY THAT A CALL CAN BE SUCCESSFULLY ORIGINATED FROM EITHER SP.
  11. 11. CHECK F: WAS THE MESSAGE SEQUENCE AS ABOVE?
  12. 12. Repeat this test in the reverse direction.

Note - The blocking signal may be generated after the call has cleared.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|--|--|--|--|-----|--|--|--------------|--|--|-----|--------|--|--------|--|--|-----|-----|--|--|-----|--|--|--|--|-----|--|--|-----|-----|--|--| +| TEST NUMBER : 2.3.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Successful call set-up | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : blocking and unblocking during a call (received) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the circuit blocking and unblocking procedure can be correctly received during a call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP ASP B
IAM
ACM
Ringing tone
ANC
Speech Speech
BLO
BLA
CLF
RLG
UBL
UBA
| | | SP A | | SP B | IAM | | | | | ACM | | | Ringing tone | | | ANC | Speech | | Speech | | | BLO | BLA | | | CLF | | | | | RLG | | | UBL | UBA | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | BLO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BLA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | UBL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| UBA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: CAN RINGING TONE BE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. SP B should initiate circuit blocking relating to the circuit used for this call.
  6. 6. CHECK C: IS SPEECH STILL POSSIBLE?
  7. 7. The calling party should clear the call.
  8. 8. CHECK D: VERIFY THAT A CALL CAN ONLY BE ORIGINATED ON THIS CIRCUUIT BY SPB?
  9. 9. SP B should send an unblocking signal.
  10. 10. CHECK E: VERIFY THAT A CALL CAN BE SUCCESSFULLY ORIGINATED FROM EITHER SP.
  11. 11. CHECK F: WAS THE MESSAGE SEQUENCE AS ABOVE?
  12. 12. Repeat this test in the reverse direction.

Note - The blocking signal may be generated after the call has cleared.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|---|--|-----|---|--|--|---|-----| +| TEST NUMBER : 3.1 | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.14 | | | | | | | | | | | | | | | +| TITLE : Normal call release | | | | | | | | | | | | | | | +| SUBTITLE : Calling party clears before address complete | | | | | | | | | | | | | | | +| PURPOSE : To verify that calling party can successfully release a call prior to receipt of an address complete message | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM >
CLF >
< RLG
| | | SP A | | SP B | IAM | > | | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.

  2. 2. The calling party should clear the call prior to receipt of the address complete signal.

  3. 3. CHECK A: IS THE CIRCUIT IDLE?

  4. 4. CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE?

  5. 5. Repeat this test in the reverse direction.
| | | | | | | | | | | | | | | + +###### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|---|--|--|--|-----|--|--|--------------|-----|---|--|--|--|-----| +| TEST NUMBER : 3.2 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.14 | | | | | | | | | | | | | | | | | | | | | +| TITLE : Normal call release | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Calling party clears before answer | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that calling party can successfully release a call prior to receipt answer | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination is free | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM )
ACM
Ringing tone
CLF )
RLG
| | | SP A | | SP B | IAM | ) | | | | ACM | | | Ringing tone | CLF | ) | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| IAM | ) | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | +| CLF | ) | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The calling party should clear the call prior to receipt of an answer signal.
  4. 4. CHECK B: IS THE CIRCUIT IDLE?
  5. 5. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
  6. 6. For validation testing this test should be repeat in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | + +## **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER : 3.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.14 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Normal call release | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Calling party clears before answer | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the calling party can successfully release a call in the speech state | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM 〉
〈 ACM
Ringing tone
〈 ANC
Speech Speech
CLF 〉
〈 RLG
| | | SP A | | SP B | IAM | 〉 | | | 〈 | ACM | | | Ringing tone | | 〈 | ANC | Speech | | Speech | CLF | 〉 | | | 〈 | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | ANC | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | RLG | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The calling party should clear the call.
  6. 6. CHECK C: IS THE CIRCUIT IDLE?
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
  8. 8. For validation testing this test should be repeated in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | + +## **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER : 3.4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Normal call release | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Called party clears | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the calling party can successfully release a call in the clear back state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :
SP A SP B
IAM >
< ACM
Ringing tone
< ANC
Speech Speech
< CBK
CLF >
< RLG
| | | SP A | | SP B | IAM | > | | | < | ACM | | | Ringing tone | | < | ANC | Speech | | Speech | | < | CBK | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CBK | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?...
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The called party should clear the call.
  6. 6. The calling party should clear the call.
  7. 7. CHECK C: IS THE CIRCUIT IDLE?
  8. 8. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
  9. 9. For validation testing repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### TUP LEVEL 4 TEST SPECIFICATION + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------|------|--|------|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|--|---|-----|--|---|-----|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER : 3.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.14 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : Normal call release | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : Called party clears and reanswers | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the called subscriber can successfully clear and reanswer a call in the speech state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP ASP B
IAM >
< ACM
Ringing tone
< ANC
Speech Speech
< CBK
< RAN
Speech Speech
CLF >
< RLG
| | | SP A | | SP B | IAM | > | | | < | ACM | | | Ringing tone | | < | ANC | Speech | | Speech | | < | CBK | | < | RAN | Speech | | Speech | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CBK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RAN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS RINGING TONE HEARD? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | The called party should answer the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: IS SPEECH POSSIBLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | The called party should clear the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | The called party should reanswer the call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK C: IS SPEECH STILL POSSIBLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | The calling party should clear the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9. | CHECK D: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 10. | CHECK E: WAS THE MESSAGE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 11. | For validation testing repeat this test in the reverse direction. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----|-----|--|----|---|--|-----|---|--|--|--|--|---|--|-----|--|-----|---|--|--|--|--|---|--|-----| +| TEST NUMBER : 4.1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : SEC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : SEC received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify the call will be immediately release by the outgoing signalling point if a switching equipment congestion signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point B such that switching equipment congestion is returned to the request | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM >
< SEC
CLF >
< RLG
| | | SP | A | | SP | B | | IAM | > | | | | | < | | SEC | | CLF | > | | | | | < | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| | IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | SEC | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | RLG | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Attempt to make a call from SP A to SP B.
Record the message sequence using with a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received. | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------|----|-----|--|----|---|--|--|---|--|-----|-----|--|--|--|--|--|--|---|--|-----|-----|--|--|--|--| +| TEST NUMBER : 4.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : SEC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : SEC sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate a equipment congestion message | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in SP A such tha switching equipment congestion is returned to the call request | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
< IAM
SEC
< CLF
RLG
| | | SP | A | | SP | B | | | < | | IAM | SEC | | | | | | | < | | CLF | RLG | | | | | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | IAM | | | | | | | | | | | | | | | | | | | | | | | | +| SEC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | CLF | | | | | | | | | | | | | | | | | | | | | | | | +| RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Attempt to make a call from SP B to SP A.
    Record the message sequence using with a signal monitor.
  2. 2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?
  3. 3. CHECK B: IS THE CIRCUIT IDLE?
  4. 4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----|-----|--|----|---|--|-----|--|--|--|--|--|--|--|-----|--|-----|--|--|--|--|--|--|--|-----| +| TEST NUMBER : 4.2.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : CGC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : CGC received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that a call will be immediately released by the outgoing signalling point if a circuit group congestion signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point B such that a circuit group congestion signal is returned to the call request | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM
CGC
CLF
RLG

| | | SP | A | | SP | B | | IAM | | | | | | | | CGC | | CLF | | | | | | | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | CGC | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | RLG | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Attempt to make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| |

Note 1 - An address complete signal (without subscriber free) may be sent in the backward direction before a CGC signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--|--------------|-----|-----|---------------|--|--|--------------|-----|-----|---------------|--| +| TEST NUMBER : 4.2.2 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.8 | | | | | | | | | | | | | | | | | | +| TITLE : CGC | | | | | | | | | | | | | | | | | | +| SUBTITLE : CGC sent | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate a circuit group congestion signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point A such that a circuit group congestion signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :
SP A SP B
\leftarrow IAM
CGC \rightarrow
\leftarrow CLF
RLG \rightarrow
| | | SP A | | SP B | | $\leftarrow$ | IAM | CGC | $\rightarrow$ | | | $\leftarrow$ | CLF | RLG | $\rightarrow$ | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | $\leftarrow$ | IAM | | | | | | | | | | | | | | | | +| CGC | $\rightarrow$ | | | | | | | | | | | | | | | | | +| | $\leftarrow$ | CLF | | | | | | | | | | | | | | | | +| RLG | $\rightarrow$ | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
1. Attempt to make a call from SP B to SP A.
Record the message sequence using a signal monitor.

2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?

3. CHECK B: IS THE CIRCUIT IDLE?

4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ?

Note 1 - An address complete signal (without subscriber free) may be sent in the backward direction before a CGC signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | 1. Attempt to make a call from SP B to SP A.
Record the message sequence using a signal monitor.

2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?

3. CHECK B: IS THE CIRCUIT IDLE?

4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? |

Note 1 - An address complete signal (without subscriber free) may be sent in the backward direction before a CGC signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | +| 1. Attempt to make a call from SP B to SP A.
Record the message sequence using a signal monitor.

2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?

3. CHECK B: IS THE CIRCUIT IDLE?

4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE ? |

Note 1 - An address complete signal (without subscriber free) may be sent in the backward direction before a CGC signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------|----|-----|--|----|---|--|-----|---|--|--|--|--|---|--|-----|--|-----|---|--|--|--|--|---|--|-----| +| TEST NUMBER : 4.3.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : NNC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : NNC received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the call will be immediately released by the outgoing signalling point if a national network congestion signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in SP B such that a national network congestion signal is returned to the call request | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM >
< NNC
CLF >
< RLG
| | | SP | A | | SP | B | | IAM | > | | | | | < | | NNC | | CLF | > | | | | | < | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| | IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | NNC | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | RLG | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. Attempt to make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?
  3. CHECK B: IS THE CIRCUIT IDLE ?
  4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - An address complete signal (without subscriber free) may be sent in the backward direction before a NNC signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER : 4.3.2 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.8 | | | | | | | | | | | | | | | | | | +| TITLE : NNC | | | | | | | | | | | | | | | | | | +| SUBTITLE : NNC sent | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that SP A is able to generate a national network congestion signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point A such that a national network congestion signal is returned to the call request, where SP A is now an I/C exchange | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
< IAM
NNC >
< CLF
RLG >
| | | SP A | | SP B | | < | IAM | NNC | > | | | < | CLF | RLG | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | +| NNC | > | | | | | | | | | | | | | | | | | +| | < | CLF | | | | | | | | | | | | | | | | +| RLG | > | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. 1. Attempt to make a call from SP B to SP A
  2. 2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUCEMENT RETURNED TO THE CALLING PARTY?
  3. 3. CHECK B: IS THE CIRCUIT IDLE?
  4. 4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - An address complete signal (without subscriber free) may be sent in the backward direction before a NNC signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----|-----|--|----|---|-----|--|---|--|--|--|--|---|--|-----|-----|--|---|--|--|--|--|---|--|-----| +| TEST NUMBER :4.4.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : ADI | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : ADI received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that on receipt of an address incomplete message the call is immediately released and the correct indication given to the calling party | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Signalling point B should be able to determine that the proper number of digits has not been received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM >
< ADI
CLF >
< RLG
| | | SP | A | | SP | B | IAM | | > | | | | | < | | ADI | CLF | | > | | | | | < | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | ADI | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | RLG | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B, but do not enter the final digit. Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE CORRECT TONE OR ANNOUNCEMENT SENT TO THE CALLING SUBSCRIBER? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In the case it must be verified that the signalling point under test retransmis the signal received. | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### TUP LEVEL 4 TEST SPECIFICATION + +| | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|--|--------------|-----|-----|---------------|--|--|--------------|-----|-----|---------------|--| +| TEST NUMBER : 4.4.2 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.7 | | | | | | | | | | | | | | | | | | +| TITLE : ADI | | | | | | | | | | | | | | | | | | +| SUBTITLE : ADI sent | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that signalling point A is able to generate an address incomplete signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : SP A should be able to determine that the proper number of digits has not been received | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
\leftarrow IAM
ADI \rightarrow
\leftarrow CLF
RLG \rightarrow
| | | SP A | | SP B | | $\leftarrow$ | IAM | ADI | $\rightarrow$ | | | $\leftarrow$ | CLF | RLG | $\rightarrow$ | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | $\leftarrow$ | IAM | | | | | | | | | | | | | | | | +| ADI | $\rightarrow$ | | | | | | | | | | | | | | | | | +| | $\leftarrow$ | CLF | | | | | | | | | | | | | | | | +| RLG | $\rightarrow$ | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION
  1. Make a call from SP B to SP A, but do not enter the final digit.
    Record message sequence using a signal monitor.
  2. CHECK A: WAS THE CORRECT TONE OR ANNOUCEMENT SENT TO THE CALLING SUBSCRIBER?
  3. CHECK B: IS THE CIRCUIT IDLE?
  4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified tha the signalling point under test retransmis the signal received.

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------|------|--|------|-----|--|--|--|--|-----|-----|--|--|--|--|-----| +| TEST NUMBER : 4.5.1 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 6.3 | | | | | | | | | | | | | | | | | | +| TITLE : CFL | | | | | | | | | | | | | | | | | | +| SUBTITLE : CFL received | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the call will be immediately released by the outgoing signalling point if a call failure signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point B such that a call failure signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM
CFL
CFL
RLG

Image: Diagram showing message sequence between SP A and SP B. IAM is sent from A to B. CFL is sent from B to A. CFL is then sent from A to B. RLG is sent from B to A.

| | | SP A | | SP B | IAM | | | | | CFL | CFL | | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | +| | | CFL | | | | | | | | | | | | | | | | +| CFL | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. 1. Attempt to make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?
  3. 3. CHECK B: IS THE CALL IDLE?
  4. 4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - An address complete signal may be sent in the backward direction before a CFL signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER : 4.5.2 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 6.3 | | | | | | | | | | | | | | | | | | +| TITLE : CFL | | | | | | | | | | | | | | | | | | +| SUBTITLE : CFL sent | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the signalling point A is able to generate a call failure signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in SP A such that a call failure signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
< IAM
CLF >
< CLF
RLG >
| | | SP A | | SP B | | < | IAM | CLF | > | | | < | CLF | RLG | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | +| | < | CLF | | | | | | | | | | | | | | | | +| RLG | > | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. 1. Attempt to make a call from SP B to SP A.
    Record the message sequence using a signal monitor.

  2. 2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?

  3. 3. CHECK B: IS THE CALL IDLE?

  4. 4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - An address complete signal may be sent in the backward direction before a CFL signal is sent.

Note 2 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----|-----|--|----|---|--|-----|---|--|--|--|--|---|--|-----|--|-----|---|--|--|--|--|---|--|-----| +| TEST NUMBER : 4.6.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE : SSB | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : SSB Received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the call will be immediately released by SP A if a Subscriber-busy signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Called termination must be busy | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :
SP A SP B
IAM >
< SSB
CLF >
< RLG
| | | SP | A | | SP | B | | IAM | > | | | | | < | | SSB | | CLF | > | | | | | < | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| | IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | SSB | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | RLG | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Attempt to make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

Note 2 - This sequence may not be possible at International Gateways | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|------|--|------|--|--------------|-----|-----|---------------|--|--|--------------|-----|-----|---------------|--| +| TEST NUMBER : 4.6.2 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 § 1.9 | | | | | | | | | | | | | | | | | | +| TITLE : SSB | | | | | | | | | | | | | | | | | | +| SUBTITLE : SSB Sent | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that signalling point A is able to generate or retransmit a subscriber busy signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : The called termination must be busy | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
\leftarrow IAM
SSB \rightarrow
\leftarrow CLF
RLG \rightarrow
| | | SP A | | SP B | | $\leftarrow$ | IAM | SSB | $\rightarrow$ | | | $\leftarrow$ | CLF | RLG | $\rightarrow$ | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | $\leftarrow$ | IAM | | | | | | | | | | | | | | | | +| SSB | $\rightarrow$ | | | | | | | | | | | | | | | | | +| | $\leftarrow$ | CLF | | | | | | | | | | | | | | | | +| RLG | $\rightarrow$ | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. Attempt to make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?
  3. CHECK B: IS THE CIRCUIT IDLE?
  4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

Note 2 - This sequence may not be possible at International Gateways

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|-----------|--|-----------|-----|--------|--|--|--------|-----|-----|--------|--|--|--------|-----| +| TEST NUMBER : 4.7.1 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 | | | | | | | | | | | | | | | | | | +| TITLE : UNN | | | | | | | | | | | | | | | | | | +| SUBTITLE : UNN Received | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that the call will be immediately released by SP A if a Unallocated-number signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point B such that a UNN Signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP      ASP      B
IAM----->
<-----UNN
CLF----->
<-----RLG
| | | SP      A | | SP      B | IAM | -----> | | | <----- | UNN | CLF | -----> | | | <----- | RLG | +| SP      A | | SP      B | | | | | | | | | | | | | | | | +| IAM | -----> | | | | | | | | | | | | | | | | | +| | <----- | UNN | | | | | | | | | | | | | | | | +| CLF | -----> | | | | | | | | | | | | | | | | | +| | <----- | RLG | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. Attempt to make a call from SP A to SP B.
Record the message sequence using a signal monitor.

2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?.....

3. CHECK B: IS THE CIRCUIT IDLE?.....

4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?.....

Note 1 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

Note 2 - This sequence may not be possible at International Gateways | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|----------------| +| TEST NUMBER : 4.7.2 | | | +| REFERENCE : Q.724 | | | +| TITLE : UNN | | | +| SUBTITLE : UNN Sent | | | +| PURPOSE : To verify that signalling point A is able to generate an Unallocated-number signal | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point A such that a UNN Signal is returned to the call request | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE :

 SP      A                                       SP      B                      <                                   IAM UNN                 >                     <                                   CLF RLG                 > 
| | | +| TEST DESCRIPTION | | | +|
  1. 1. Attempt to make a call from SP B to SP A.
    Record the message sequence using a signal monitor.

  2. 2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?

  3. 3. CHECK B: IS THE CIRCUIT IDLE?

  4. 4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

Note 2 - This sequence may not be possible at International Gateways

| | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------|------|--|------|-----|---|--|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER : 4.8.1 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 | | | | | | | | | | | | | | | | | | +| TITLE : LOS | | | | | | | | | | | | | | | | | | +| SUBTITLE : LOS Received | | | | | | | | | | | | | | | | | | +| PURPOSE : Verify that the call will be immediately released by SP A if a Line out of service signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS : Arrange the data in signalling point B such that a LOS Signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE :

SP A SP B
IAM >
< LOS
CLF >
< RLG
| | | SP A | | SP B | IAM | > | | | < | LOS | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | +| | < | LOS | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. Attempt to make a call from SP A to SP B.
    Record the message sequence using a signal monitor.

  2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?

  3. CHECK B: IS THE CIRCUIT IDLE?

  4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER : 4.8.2 | | | | | | | | | | | | | | | | | | +| REFERENCE : Q.724 | | | | | | | | | | | | | | | | | | +| TITLE : LOS | | | | | | | | | | | | | | | | | | +| SUBTITLE : LOS Sent | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that signalling point A is able to retransmit a Line-out-of-service signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS :Arrange the data in signalling point A such that a LOS Signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST : VAT | TYPE OF SP : SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE :

SP A SP B
< IAM
LOS >
< CLF
RLG >
| | | SP A | | SP B | | < | IAM | LOS | > | | | < | CLF | RLG | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | +| LOS | > | | | | | | | | | | | | | | | | | +| | < | CLF | | | | | | | | | | | | | | | | +| RLG | > | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. Attempt to make a call from SP B to SP A.
    Record the message sequence using a signal monitor.
  2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?
  3. CHECK B: IS THE CIRCUIT IDLE?
  4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note 1 - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

Note 2 - This sequence may not be possible at International Gateways

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----|-----|--|----|---|--|-----|--|--|--|--|--|--|--|-----|--|-----|--|--|--|--|--|--|--|-----| +| TEST NUMBER: 4.9.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: SST | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: SST received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a call will be immediately released by the outgoing signalling point if a send-special-information-tone signal is received and the correct indication is given to the calling party | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point B such that a SST signal is returned to the call request | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
SST
CLF
RLG
| | | SP | A | | SP | B | | IAM | | | | | | | | SST | | CLF | | | | | | | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | SST | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | RLG | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Attempt to make a call from SP A to SP B
Record the message sequence with a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE APPROPRIATE TONE RETURNED TO THE CALLING PARTY? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received. | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 4.9.2 | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 | | | | | | | | | | | | | | | | | | +| TITLE: SST | | | | | | | | | | | | | | | | | | +| SUBTITLE: SST sent | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to generate a send-special-information-tone signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point A such that a SST signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
SST >
< CLF
RLG >
| | | SP A | | SP B | | < | IAM | SST | > | | | < | CLF | RLG | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | +| SST | > | | | | | | | | | | | | | | | | | +| | < | CLF | | | | | | | | | | | | | | | | +| RLG | > | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. Attempt to make a call from SP B to SP A
    Record the message sequence with a signal monitor.
  2. CHECK A: IS THE APPROPRIATE TONE RETURNED TO THE CALLING PARTY?
  3. CHECK B: IS THE CIRCUIT IDLE?
  4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----|-----|--|----|---|-----|--|----|--|--|--|--|---|--|-----|-----|--|----|--|--|--|--|---|--|-----| +| TEST NUMBER: 4.10.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 10.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: ACB | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: ACB received | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that because of incompatible CUG information the call is rejected and an access barred signal is returned to the call request | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the signalling point data such that the CUG information contained in the IAI is compatible with the information stored at SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAI >)
( ACB
CLF >)
( RLG

| | | SP | A | | SP | B | IAI | | >) | | | | | ( | | ACB | CLF | | >) | | | | | ( | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | +| IAI | | >) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ( | | ACB | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | >) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ( | | RLG | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a CUG call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------| +| TEST NUMBER: 4.10.2 | | | +| REFERENCE: Q.724 § 10.2 | | | +| TITLE: ACB | | | +| SUBTITLE: ACB sent | | | +| PURPOSE: To verify that SP A is able to generate or receive an access barred signal | | | +| PRE-TEST CONDITIONS: | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

       SP      A                                            SP      B                                  <                             IAI       ACB                       >                                 <                             CLF       RLG                       > 
| | | +| TEST DESCRIPTION | | | +|
  1. Make a CUG call from SP B to SP A.
    Record the message sequence using a signal monitor.
  2. CHECK A: IS THE APPROPRIATE TONE OR ANNOUNCEMENT RETURNED TO THE CALLING PARTY?
  3. CHECK B: IS THE CIRCUIT IDLE?
  4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is returned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------|--|------|-----|---|--|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 4.11.1 | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 10.7 | | | | | | | | | | | | | | | | | | +| TITLE: DPN | | | | | | | | | | | | | | | | | | +| SUBTITLE: DPN received | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the call will be immediately released by the SP A if a digital path not provided signal is received and the correct indicator is given to the calling party | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Ensure the IAM is set to indicate that an all digital path is required.
b) Ensure the data in signalling point B is configured such that a digital path not provided signal is returned to the call request. | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM 〉
〈 DPN
CLF 〉
〈 RLG
| | | SP A | | SP B | IAM | 〉 | | | 〈 | DPN | CLF | 〉 | | | 〈 | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | +| IAM | 〉 | | | | | | | | | | | | | | | | | +| | 〈 | DPN | | | | | | | | | | | | | | | | +| CLF | 〉 | | | | | | | | | | | | | | | | | +| | 〈 | RLG | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. 1. Attempt to make a call from SP A to SP B.
    Ensuring that the IAM is set to indicate that an all digital path is required. Record the message sequence using a signal monitor.

  2. 2. CHECK A: IS THE CIRCUIT IDLE?

  3. 3. CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE?
| Note - It may not be possible to confirm that the appropriate tone is retuned to the calling party. In this case it must be verified that the signalling point under tes retransmits the signal received. | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 4.11.2 | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 10.7 | | | | | | | | | | | | | | | | | | +| TITLE: DPN | | | | | | | | | | | | | | | | | | +| SUBTITLE: DPN sent | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that signalling point A is able to generate a digital path not provided signal | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point A such that a DPN signal is returned to the call request | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
DPN >
< CLF
RLG >
| | | SP A | | SP B | | < | IAM | DPN | > | | | < | CLF | RLG | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | +| DPN | > | | | | | | | | | | | | | | | | | +| | < | CLF | | | | | | | | | | | | | | | | +| RLG | > | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +|
  1. 1. Attempt to make a call from SP B to SP A.
    Record the message sequence with a signal monitor.
  2. 2. CHECK B: IS THE CIRCUIT IDLE?
  3. 3. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - It may not be possible to confirm that the appropriate tone is retuned to the calling party. In this case it must be verified that the signalling point under test retransmits the signal received.

| | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|--|--------------|-----|-----|---------------|--|--------------|--|--|-----|---------------|--|--------|--|--------|--|--------------|-----|-----|---------------|--|--|--------------|-----|-----|---------------|--| +| TEST NUMBER: 5.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 6.2.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inability to release in response to a CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that if the signalling point is unable to return a circuit to the idle condition in response to a clear forward signal, the circuit will be blocked | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point A such that it is unable to return the circuit to the idle condition in response to a clear forward signal | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
\leftarrow IAM
ACM \rightarrow
Ringing tone
ANC \rightarrow
Speech Speech
\leftarrow CLF
BLO \rightarrow
\leftarrow BLA
RLG \rightarrow
| | | SP A | | SP B | | $\leftarrow$ | IAM | ACM | $\rightarrow$ | | Ringing tone | | | ANC | $\rightarrow$ | | Speech | | Speech | | $\leftarrow$ | CLF | BLO | $\rightarrow$ | | | $\leftarrow$ | BLA | RLG | $\rightarrow$ | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | $\leftarrow$ | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | $\rightarrow$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANC | $\rightarrow$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | $\leftarrow$ | CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BLO | $\rightarrow$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | $\leftarrow$ | BLA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLG | $\rightarrow$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer the call
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The calling party should release the call.
  6. 6. CHECK C: VERIFY THAT A CALL CAN NOT BE ORIGINATED FROM EITHER SP
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
  8. 8. Repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|----------------|----|-----|--|----|---|--|-----|---|--|--|--|--|---|--|-----|--|-----|---|--|--|--|--|---|--|-----|--|-----|---|--|--|--|--|---|--|-----| +| TEST NUMBER: 5.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 6.2.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Inability to release in response to a backward signal | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE : To verify that if signalling point is unable to return the circuit to an idle condition in response to a backward signal, the circuit will be blocked | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point A such that it is unable to return the circuit to an idle condition in response to a backward signal | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM >
< ADI
BLO >
< BLA
CLF >
< RLG
| | | SP | A | | SP | B | | IAM | > | | | | | < | | ADI | | BLO | > | | | | | < | | BLA | | CLF | > | | | | | < | | RLG | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | ADI | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | BLO | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | BLA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B, but do not enter the final digit. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: VERIFY THAT A CALL CAN NOT BE ORIGINATED FROM EITHER EXCHANGE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | Repeat this test the reverse direction. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------| +| TEST NUMBER: 5.3.1 | | | +| REFERENCE: Q.724 § 6.4.3a | | | +| TITLE: Timers | | | +| SUBTITLE: T2 | | | +| PURPOSE: To check the value of timer T2 | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point B such that an address complete message is not returned to the call request | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:


SP A


IAM

T2 20-30 seconds

CLF

>



>

<

SP B






RLG

| | | +| TEST DESCRIPTION | | | +|
  1. 1. Attempt to make a call from SP A to SP B.
    Record the message sequence with a signal monitor.
  2. 2. CHECK A: WAS THE CLEAR FORWARD SIGNAL SENT BEFORE 20-30 SECONDS?
  3. 3. CHECK B: IS THE CIRCUIT IDLE?
  4. 4. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 5.3.2 | | | +| REFERENCE: Q.724 § 6.4.3b | | | +| TITLE: Timers | | | +| SUBTITLE: T3 | | | +| PURPOSE: To check the value of timer T3 | | | +| PRE-TEST CONDITIONS:
a) Signalling point A should be able to determine that the proper number of digits have not been received.
b) Arrange the data in signalling point B such that a clear forward signal is not returned in response to an address incomplete message. | | | +| CONFIGURATION: 1 | TYPE OF TYPE: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:

SP A


ADI
T3 4-15 seconds
CFL

RLG
<
>



>
<
>
SP B


IAM




CLF
| | | +| TEST DESCRIPTION | | | +| 1.


2.


3.

4. | Attempt to make a call from SP B to SP A but do not dial the last digit.
Record the message sequence using a signal monitor.

CHECK A: WAS A CALL FAILURE SIGNAL SENT BETWEEN 4-15 SECONDS AFTER SENDING OF THE ADDRESS INCOMPLETE MESSAGE?

CHECK B: IS THE CIRCUIT IDLE?

CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------------|------------------------------------------------------------------------------------------------|----------------------------------------------|------------------------| +| TEST NUMBER: 5.3.3 | | | | | | +| REFERENCE: Q.724 § 6.4.3b | | | | | | +| TITLE: Timers | | | | | | +| SUBTITLE: T4 | | | | | | +| PURPOSE: To check the value of timer T4 | | | | | | +| PRE-TEST CONDITIONS:

a) Signalling point A should be able to determine that the proper number of digits have not been received.
b) Arrange the data in signalling point B such that a clear forward signal is not returned in response to an address incomplete message.
c) Arrange the data in signalling point B such that a clear forward signal is not returned in response to a call failure signal. | | | | | | +| CONFIGURATION :1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A

ADI

T3 4-15 seconds

CFL

T4 4-15 seconds

CFL
<-----
----->

----->

----->
SP B

IAM
| | | SP A

ADI

T3 4-15 seconds

CFL

T4 4-15 seconds

CFL | <-----
----->

----->

-----> | SP B

IAM | +| SP A

ADI

T3 4-15 seconds

CFL

T4 4-15 seconds

CFL | <-----
----->

----->

-----> | SP B

IAM | | | | +| TEST DESCRIPTION | | | | | | +| 1. Attempt to make a call from SP B to SP A but do not send the last digit. Record the message sequence using a signal monitor.

2. CHECK A: WAS THE CALL FAILURE SIGNAL REPEATED BETWEEN 4-15 SECONDS AFTER SENDING THE INITIAL CALL FAILURE SIGNAL?....

3. CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE?..... | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 5.3.4 | | | +| REFERENCE: Q.724 § 6.4.3b | | | +| TITLE: Timers | | | +| SUBTITLE: T5 | | | +| PURPOSE: To check the value of timer T5 | | | +| PRE-TEST CONDITIONS:
a) Signalling point A should be able to determine that the proper number of digits have not been received.
b) Arrange the data in signalling point B such that a clear forward signal is not returned in response to an address incomplete message.
c) Arrange the data in signalling point B such that a clear forward signal is not returned in response to a call failure signal. | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:

SP A
SP B
                                <--------------------------- IAM  ADI                           --------------------------->             T3   4-15 seconds  CFL                           --------------------------->             T4   4-15 seconds  CFL                           --------------------------->             T4   4-15 seconds  CFL                           --------------------------->       T5    1 minute  RSC                           ---------------------------> 
| | | +| TEST DESCRIPTION | | | +| 1. | Attempt to make a call from SP B to SP A but do not send the last digit. Record the message sequence using a signal monitor. | | +| 2. | CHECK A: WAS THE CALL FAILURE SIGNAL REPEATED BETWEEN 4-15 SECONDS AFTER SENDING THE INITIAL CALL FAILURE SIGNAL? | | +| 3. | CHECK B: WAS THE CALL FAILURE SIGNAL REPEATED FOR A PERIOD OF ONE MINUTE? | | +| 4. | CHECK C: WAS A RESET CIRCUIT SIGNAL SENT ON THE EXPIRY OF TIMER T5? | | +| 5. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|-----|---|--|--|---|-----|--|--|--------------|-----|---|--|----|--------------|--|-----|---|--| +| TEST NUMBER: 5.3.5 | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 6.23 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Timers | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: T6 | | | | | | | | | | | | | | | | | | | | | | | | +| Purpose: To check the value of timer T6 | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point B such that a release guard is not returned in response to a clear forward signal | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM >
< ACM
Ringing tone
CLF >
T6 4-15 seconds
CLF >
| | | SP A | | SP B | IAM | > | | | < | ACM | | | Ringing tone | CLF | > | | T6 | 4-15 seconds | | CLF | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | +| T6 | 4-15 seconds | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B, record the message sequence using a signal monitor.
  2. 2. CHECK A : IS RINGING TONE HEARD?
  3. 3. The calling party should clear the call.
  4. 4. CHECK B: WAS THE CLEAR FORWARD SIGNAL REPEATED BEFORE 4-15 SECONDS AFTER SENDING THE INITIAL CLEAR FORWARD SIGNAL?
  5. 5. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------| +| TEST NUMBER: 5.3.6 | | | +| REFERENCE: Q.118 | | | +| TITLE: Q.118 timers | | | +| SUBTITLE: Answer signal not received | | | +| PURPOSE: To verify that if an answer signal is not received within 2-4 minutes after receiving an address complete signal the connection is reloaded by the outgoing signalling point | | | +| PRE-TEST CONDITIONS: The called party should not answer the call | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP A

IAM

2-4 minutes

CLF

----->

<-----


----->

<-----

SP B

ACM


RLG

| | | +| TEST DESCRIPTION | | | +|
  1. 1. Attempt to make a call from SP A to SP B. Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?.....
  3. 3. The called party should NOT answer the call.
  4. 4. CHECK B: WAS THE CLEAR FORWARD SEND WITHIN A PERIOD OF 2 To 4 MINUTES SIGNAL?.....
  5. 5. CHECK C: IS THE CIRCUIT IDLE?.....
  6. 6. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?.....

Note - The timer need only be run at the going international exchange.

| | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| TEST NUMBER: 5.3.7 | | | | | | +| REFERENCE: Q.118 | | | | | | +| TITLE: Q.118 timers | | | | | | +| SUBTITLE: Delay in clearing by calling party | | | | | | +| PURPOSE: Verify that the call will be released if the calling party has not cleared the call within 1-2 minutes after the called party clears | | | | | | +| PRE-TEST CONDITIONS: The called party should not answer the call | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A


IAM





Speech


[ 1-2 minutes

CLF



>

<

<


<


>

<

SP B



ACM

Ringing tone

ANC


Speech

CBK



RLG

| | |

SP A


IAM





Speech


[ 1-2 minutes

CLF

|

>

<

<


<


>

<

|

SP B



ACM

Ringing tone

ANC


Speech

CBK



RLG

| +|

SP A


IAM





Speech


[ 1-2 minutes

CLF

|

>

<

<


<


>

<

|

SP B



ACM

Ringing tone

ANC


Speech

CBK



RLG

| | | | +| TEST DESCRIPTION | | | | | | +|
  1. 1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The called party should clear the call.
  6. 6. CHECK C: WAS THE CLEAR FORWARD SENT WITHIN A PERIOD OF BETWEEN 1 AND 2 MINUTES?
  7. 7. CHECK D: IS THE CIRCUIT IDLE?
  8. 8. CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 5.4.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 1.15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Reset of circuits during a call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Of an outgoing circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on receipt of a reset circuit signal the call is immediately released | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM 〉
〈 ACM
Ringing tone
〈 ANC
Speech Speech
〈 RSC
CLF 〉
〈 RLG
| | | SP A | | SP B | IAM | 〉 | | | 〈 | ACM | | | Ringing tone | | 〈 | ANC | Speech | | Speech | | 〈 | RSC | CLF | 〉 | | | 〈 | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | RSC | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | 〉 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | 〈 | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. Make a call for SP A to SP B.
Record the message sequence using a signal monitor.
2. CHECK A: IS RINGING TONE HEARD?
3. The called party should answer the call.
4. CHECK B: IS SPEECH POSSIBLE?
5. Arrange for SP B to send a reset-circuit signal.
6. CHECK C: IS THE CIRCUIT IDLE?
7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|----------------|----|--------|--|----|---|--|--|---|--|-----|-----|--|--|--|--|--------------|--|--|--|--|-----|--|--|--|--|--------|--|--|--|--------|--|--|---|--|-----|-----|--|--|--|--| +| TEST NUMBER: 5.4.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 1.15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Reset of circuit during call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Of an incoming circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the circuit reset procedure can be correctly initiated during a call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Called termination is free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
ACM
Ringing tone
ANC
Speech Speech
< RSC
RLG
| | | SP | A | | SP | B | | | < | | IAM | ACM | | | | | Ringing tone | | | | | ANC | | | | | Speech | | | | Speech | | | < | | RSC | RLG | | | | | +| SP | A | | SP | B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | | RSC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A.
Record the message sequence with a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS RINGING TONE HEARD? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | The called party should answer the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: IS SPEECH POSSIBLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | Arrange for SP B to send a reset circuit signal. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------|--|-----------|-----|--------|--|--|--------|-----|--|-------|--------------|--|--------|------------------|--|--------|-----|--|-------|--------|--|--------|------------------|-----|--------|--|--|--------|-----| +| TEST NUMBER: 5.5.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 6.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Receipt of unreasonable information during a call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the action taken by a signalling point upon receipt of unreasonable signalling information is as stated in Q.724 Section 6.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Circuit idle and unblocked | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP      A SP      B
IAM ----->
<----- ACM
----- Ringing tone
<----- See Item 3 below
<----- ANC
----- Speech
<----- See Item 6 below
CLF ----->
<----- RLG
| | | SP      A | | SP      B | IAM | -----> | | | <----- | ACM | | ----- | Ringing tone | | <----- | See Item 3 below | | <----- | ANC | | ----- | Speech | | <----- | See Item 6 below | CLF | -----> | | | <----- | RLG | +| SP      A | | SP      B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | -----> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <----- | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ----- | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <----- | See Item 3 below | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <----- | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ----- | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <----- | See Item 6 below | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | -----> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | <----- | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS RINGING TONE HEARD?..... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | Send a message which would be unreasonable at this point in the call (i.e COT) and confirm that message is discarded. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | The called party should answer the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: IS SPEECH POSSIBLE?..... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | SP B should send such a message which would be unreasonable at this point in the call (i.e ACM) and confirm that the message is discarded. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | The calling point should clear the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK C: IS THE CIRCUIT IDLE?..... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9. | CHECK D: WAS THE MESSAGE AS SHOWN ABOVE. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +*Note - This test covers only some of the ambiguous messages which could be received.* + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------|------|--|------|-----|--|--|------------|--|--|-----|--|--|--|--|-----|--|--|--------------|--|--|-----|--------|--|--------|-----|--|--|--|--|-----| +| TEST NUMBER: 6.1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 7.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Continuity check call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COT applied on an outgoing circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a call can be set up on a circuit requiring a continuity check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point A such that a continuity check is required on this circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
Check tone
COT
ACM
Ringing tone
ANC
Speech Speech
CLF
RLG
| | | SP A | | SP B | IAM | | | Check tone | | | COT | | | | | ACM | | | Ringing tone | | | ANC | Speech | | Speech | CLF | | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Check tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| COT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer the call
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The calling party should clear the call.
  6. 6. CHECK C: IS THE CIRCUIT IDLE?
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS SHOWN ABOVE?
  8. 8. For validation testing repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------------|------|--|------|-----|---|--|--|--|--|--|-------------------------------------------------|--|--|--|--|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER: 6.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 7.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Special call set up | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COT applied on a previous circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a call can be set up if a continuity check is being performed on a previous circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point A such that the signalling information indicates that a continuity check has been performed on a previous circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM )
delay while check performed on previous circuit
COT )
( ACM
Ringing tone
( ANC
Speech Speech
CLF )
( RLG
| | | SP A | | SP B | IAM | ) | | | | | | delay while check performed on previous circuit | | | | | COT | ) | | | ( | ACM | | | Ringing tone | | ( | ANC | Speech | | Speech | CLF | ) | | | ( | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | delay while check performed on previous circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| COT | ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ( | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ( | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ( | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: IS RINGING TONE HEARD? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | The called party should answer the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: IS SPEECH POSSIBLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | The calling party should clear the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK C: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK E: WAS THE CONTINUITY CHECK INDICATOR SET TO A BINARY VALUE OF TWO (MESSAGE INDICATOR BITS E and F IN IAM)? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9. | For validation testing repeat this test in the reverse direction. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------|------|--|------|-----|---|--|------------|--|--|-----|---|--|--|--|-----|--|--|--------------|--|--|-----|--------|--|--------|-----|---|--|--|--|-----| +| TEST NUMBER: 6.1.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 7.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Continuity check call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COT on a satellite circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a continuity check can be performed on a satellite circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point A such that the call is routed over a satellite circuit, with a continuity check applied for | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM )
Check tone
COT )
ACM
Ringing tone
ANC
Speech Speech
CLF )
RLG
| | | SP A | | SP B | IAM | ) | | Check tone | | | COT | ) | | | | ACM | | | Ringing tone | | | ANC | Speech | | Speech | CLF | ) | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Check tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| COT | ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. Make a call from SP A to SP B.
    Record the message sequence using a signal monitor.
  2. CHECK A: IS RINGING TONE HEARD?
  3. The called party should answer the call.
  4. CHECK B: IS SPEECH POSSIBLE?
  5. The calling party should clear the call.
  6. CHECK C: IS THE CIRCUIT IDLE?
  7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
  8. CHECK E: WAS THE SATELLITE INDICATOR BIT IN THE IAM SET TO 1?
  9. For validation testing repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|------|--|------|-----|--|--|------------|--|--|-----|--|--|--|--|-----| +| TEST NUMBER: 6.1.4 | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 6.1 | | | | | | | | | | | | | | | | | | +| TITLE: Continuity check call | | | | | | | | | | | | | | | | | | +| SUBTITLE: Calling party clears during COT | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the calling party can successfully clear during the continuity check phase of the call | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point B such that a continuity check is applied on this call | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
Check tone
CLF
RLG
| | | SP A | | SP B | IAM | | | Check tone | | | CLF | | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | +| Check tone | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | +| 2. | The calling party should clear the call during the continuity check phase. | | | | | | | | | | | | | | | | | +| 3. | CHECK A: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | +| 5. | For validation testing repeat this test in the reverse direction. | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------|------|--|------|-----|---|--|------------|--|--|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER: 6.1.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 7.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Continuity check call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Delay of through connect | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the switching though of the speech path is delayed until the residual check-tone has propated through the return of the speech path | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) The called termination is free
b) Arrange the data in signalling point A such that a continuity check is applied on this call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM >
Check tone
COT >
< ACM
Ringing tone
< ANC
Speech Speech
CLF >
< RLG
| | | SP A | | SP B | IAM | > | | Check tone | | | COT | > | | | < | ACM | | | Ringing tone | | < | ANC | Speech | | Speech | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Check tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| COT | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B.
Record the message sequence using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | CHECK A: WAS THE CONTINUITY CHECK TONE HEARD BY EITHER CALLED OR CALLING PARTY? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK B: IS RINGING TONE HEARD? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | The called party should answer the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK B: IS SPEECH POSSIBLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | The calling party should clear the call. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK C: IS THE CIRCUIT IDLE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 8. | CHECK D: WAS THE MESSAGE SEQUENCE AS SHOWN ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 9. | For validation testing repeat this test in the reverse direction. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 6.1.6 | | | +| REFERENCE: Q.724 § 7.3 | | | +| TITLE: Continuity check call | | | +| SUBTITLE: COT unsuccessful | | | +| PURPOSE: To verify that a repeat attempt of the continuity check is made on the failed circuit | | | +| PRE-TEST CONDITIONS: Ensure that no backward tone is detected within the specified timeout | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B

Image: Sequence diagram showing message exchange between SP A and SP B. SP A sends IAM, Check tone, CCF, then after timer T9 (1-10 seconds), sends CCR and Check tone. SP B responds with Check tone, CCF, then after timer T10 (1-3 minutes), sends CCR and Check tone. Maintenance staff is alerted at SP B after the second failure.

sequenceDiagram     participant A as SP A     participant B as SP B     A->>B: IAM     A->>B: Check tone     Note over A,B:      A->>B: CCF     Note left of A: T9 (1-10 seconds)     A->>B: CCR     A->>B: Check tone     Note over A,B:      A->>B: CCF     Note left of A: T10 (1-3 minutes)     Note right of B: Maintenance staff alerted     A->>B: CCR     A->>B: Check tone
| | | +| TEST DESCRIPTION | | | +| 1. | Initiate the continuity test call procedure at SP A.
Record the message sequence using a signal monitor. | | +| 2. | CHECK A: WAS THE SECOND CONTINUITY CHECK INITIATED WITHIN 1 TO 10 SECONDS? | | +| 3. | CHECK B: WERE THE MAINTENANCE STAFF ALERTED ON FAILURE OF THE SECOND CONTINUITY CHECK? | | +| 4. | CHECK C: WAS THE CHECK REPEATED AT INTERVALS OF 1 TO 3 MINUTES? | | +| 5. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
Note 1 - The repeated check will only finish when continuity is detected.
Note 2 - On failure of the COT an automatic repeat attempt will be made -see test No. 6.2.5 | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------|------|--|------|--|---|-----|--|--|------------|--|---|-----|-----|---|--|--------------|--|--|-----|---|--|--------|--|--------|--|---|-----|-----|---|--| +| TEST NUMBER: 6.1.7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 7.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Continuity check call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COT received on an incoming circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a call can be set up on an incoming circuit requiring a continuity check | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point such that a continuity check is required on this circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
Check tone
< COT
ACM >
Ringing tone
ANC >
Speech Speech
< CLF
RLG >
| | | SP A | | SP B | | < | IAM | | | Check tone | | < | COT | ACM | > | | Ringing tone | | | ANC | > | | Speech | | Speech | | < | CLF | RLG | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Check tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | COT | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANC | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLG | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP B to SP A.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS THE RINGING TONE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The calling party should clear the call.
  6. 6. CHECK C: IS THE CIRCUIT IDLE?
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
  8. 8. For validation testing repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|-------------|-----|-------------|-------------|---|--|--------------|---|--|-------------|---|--|--------|--|--------|-------------|---|--|--|---|-------------|--|--|--------------|--|---|-------------|--------|--|--------|-------------|---|--|--|---|-------------|--|---|-------------|-------------|---|--| +| TEST NUMBER: 6.2.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Automatic repeat attempt | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dual seizure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an automatic repeat attempt will be made on detection of a dual seizure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the signalling point data such that SP B is the controlling exchange | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM (cic=x) > < IAM (cic=x)
ACM (cic=x) >
Ringing tone >
ANC (cic=x) >
Speech Speech
IAM (cic=y) >
< ACM (cic=y)
Ringing tone
< ANC (cic=y)
Speech Speech
CLF (cic=y) >
< RLG (cic=y)
< CLF (cic=x)
RLG (cic=x) >
| | | SP A | | SP B | IAM (cic=x) | > < | IAM (cic=x) | ACM (cic=x) | > | | Ringing tone | > | | ANC (cic=x) | > | | Speech | | Speech | IAM (cic=y) | > | | | < | ACM (cic=y) | | | Ringing tone | | < | ANC (cic=y) | Speech | | Speech | CLF (cic=y) | > | | | < | RLG (cic=y) | | < | CLF (cic=x) | RLG (cic=x) | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM (cic=x) | > < | IAM (cic=x) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM (cic=x) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ringing tone | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANC (cic=x) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM (cic=y) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM (cic=y) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANC (cic=y) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF (cic=y) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG (cic=y) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CLF (cic=x) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLG (cic=x) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Simultaneously transmit an IAM (containing the same value of cic) from each end of the link for a both way circuit. Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD ON THE CALL ORIGINATED FROM SP B?....
  3. 3. The called party at SP A should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?....
  5. 5. CHECK C: WAS THE REPEAT ATTEMPT MADE BY SP A, WITH A DIFFERENT VALUE OF CIC IN THE IAM?.....
  6. 6. CHECK D: IS RINGING TONE HEARD ON THE CALL ORIGINATED FROM SP A?.....
  7. 7. The called party at SP B should answer the call.
  8. 8. CHECK E: IS SPEECH POSSIBLE?...
  9. 9. Clear both calls down.
  10. 10. CHECK F: ARE THE CIRCUITS IDLE?....
  11. 11. CHECK G: WAS THE MESSAGE SEQUENCE AS ABOVE?....

Note - The message sequence may not be as shown above.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|-----|---|--|--|---|-----|-----|---|--|--|---|-----|-----|---|--|--|---|-----|--|--|--------------|--|---|-----|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER: 6.2.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Automatic repeat attempt | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Circuit reset | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an automatic repeat attempt will be made on receipt of circuit reset after sending of an initial address message and before a backward signal has been received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the data in signalling point B such that a circuit reset signal is sent in response to the initial address mesage of the first call request
b) The called termination should be free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM >
< RSC
CLF >
< RLG
IAM >
< ACM
Ringing tone
< ANC
Speech Speech
CLR >
< RLG
| | | SP A | | SP B | IAM | > | | | < | RSC | CLF | > | | | < | RLG | IAM | > | | | < | ACM | | | Ringing tone | | < | ANC | Speech | | Speech | CLR | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RSC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLR | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call for SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The calling party should clear the call.
  6. 6. CHECK C: IS THE CIRCUIT IDLE?
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
Note - The message sequence may not be as shown above. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------|------|--|------|-----|--|--|--|--|------------------|-----|--|--|--|--|-----|-----|--|--|--|--|-----|--|--|--------------|--|--|-----|--------|--|--------|-----|--|--|--|--|-----| +| TEST NUMBER: 6.2.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Automatic repeat attempt | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Reception of unreasonable signalling information | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a repeat attempt will be made on receipt of unreasonable signalling information after sending the initial address message and before one of the backward signals has been received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the data in signalling point B such that unreasonable signalling information (see note below) is returned in response to the initial address message of the first call request
b) The called termination should be free | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
see Note 1 below
RSC
RLG
IAM
ACM
Ringing tone
ANC
Speech Speech
CLF
RLG
| | | SP A | | SP B | IAM | | | | | see Note 1 below | RSC | | | | | RLG | IAM | | | | | ACM | | | Ringing tone | | | ANC | Speech | | Speech | CLF | | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | see Note 1 below | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RSC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. Make a call for SP A to SP B.
Record the message sequence using a signal monitor.
2. CHECK A: IS RINGING TONE HEARD?
3. The called party should answer the call.
4. CHECK B: IS SPEECH POSSIBLE?....
5. The calling party should clear the call.
6. CHECK C: IS THE CIRCUIT IDLE?....
7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?.....

Note 1 - This may be any message that if received at this point would be either ambiguous or inappropriate

Note 2 - The message sequence may not be as shown above. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|-----|--|--|--|--|-----|-----|--|--|-----|--|--|--|--|-----|-----|--|--|--|--|-----|--|--|--------------|--|--|-----|--------|--|--------|-----|--|--|--|--|-----| +| TEST NUMBER: 6.2.4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Automatic repeat attempt | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Blocking of a circuit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an automatic repeat attempt will be made on receipt of the blocking signal after sending an initial address message and before any backward messages have been received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point B such that a blocking signal is returned in response to the initial address message of the first call request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B
IAM
BLO
BLA
CLF
RLG
IAM
ACM
Ringing tone
ANC
Speech Speech
CLF
RLG
| | | SP A | | SP B | IAM | | | | | BLO | BLA | | | CLF | | | | | RLG | IAM | | | | | ACM | | | Ringing tone | | | ANC | Speech | | Speech | CLF | | | | | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | BLO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| BLA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call for SP A to SP B.
    Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD?
  3. 3. The called party should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The calling party should clear the call.
  6. 6. CHECK C: IS THE CIRCUIT IDLE?
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?

Note - The message sequence may not be as shown above.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 6.2.5 | | | +| REFERENCE: Q.724 § 6 | | | +| TITLE: Automatic repeat attempt | | | +| SUBTITLE: Continuity check failure | | | +| PURPOSE: To verify that an automatic repeat attempt will be made if on continuity check failure | | | +| PRE-TEST CONDITIONS: Arrange the data in signalling point B such that check tone is not returned within the specified limits to the first call request | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | +|

EXPECTED MESSAGE SEQUENCE:

    SP A                                                     SP B     IAM                      >    Check tone                                                 CCF                      >        A repeat of the continuity check of the failed circuit will be made within 1-10 seconds see Q.724 Section 7.3     IAM                      >    Check tone                                                                          <                               ACM                                                             Ringing tone                             <                               ANC     Speech                                                   Speech     CLF                      >                             <                               RLG 
| | | +| TEST DESCRIPTION | | | +| 1. | Make a call for SP A to SP B.
Record the message sequence using a signal monitor. | | +| 2. | CHECK A: IS RINGING TONE HEARD? | | +| 3. | The called party should clear the call? | | +| 4. | CHECK B: IS SPEECH POSSIBLE | | +| 5. | The calling party should clear the call. | | +| 6. | CHECK C: IS THE CIRCUIT IDLE? | | +| 7. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | +| | Note - The message sequence may not be as shown above. | | + +### **TUP LEVEL 4 TEST SPECIFICATION** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|-----|-----|-----|-----|---|--|--|--|--------------|-----|---|--|--------|--|--------|-----|---|--|--|---|-----| +| TEST NUMBER: 6.3.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.724 § 2.5 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Dual seizure | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Dual seizure for controlling side | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that on detection of dual seizure, the call initiated by the controlling signalling point is completed | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the signalling point data such that SP B is the controlling signalling point | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION : 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM > < IAM
ACM >
Ringing tone
ANC >
Speech Speech
CLF >
< RLG
| | | SP A | | SP B | IAM | > < | IAM | ACM | > | | | | Ringing tone | ANC | > | | Speech | | Speech | CLF | > | | | < | RLG | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ringing tone | | | | | | | | | | | | | | | | | | | | | | | | | +| ANC | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| Speech | | Speech | | | | | | | | | | | | | | | | | | | | | | | | | +| CLF | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLG | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Simultaneously transmit an IAM (containing the same value of cic) from each end of the link for a both way circuit. Record the message sequence using a signal monitor.
  2. 2. CHECK A: IS RINGING TONE HEARD ON THE CALL ORIGINATED FROM SP B?
  3. 3. The called party at SP A should answer the call.
  4. 4. CHECK B: IS SPEECH POSSIBLE?
  5. 5. The calling party at SP B should clear the call.
  6. 6. CHECK C: IS THE CIRCUIT IDLE?
  7. 7. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
  8. 8. CHECK E: WAS A REPEAT ATTEMPT MADE BY SP A ON ANOTHER CIRCUIT?
  9. 9. Repeat this test in the reverse direction.
| | | | | | | | | | | | | | | | | | | | | | | | | | | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.785-199109-I_PDF-E/raw.md b/marked/Q/T-REC-Q.785-199109-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..19a41a1656ae129ef95e92b16f8aa1a661e6b5c9 --- /dev/null +++ b/marked/Q/T-REC-Q.785-199109-I_PDF-E/raw.md @@ -0,0 +1,1400 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**Q.785** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +**SPECIFICATIONS +OF SIGNALLING SYSTEM No. 7** + +--- + +**ISUP PROTOCOL TEST SPECIFICATION +FOR SUPPLEMENTARY SERVICES** + +**Recommendation Q.785** + +--- + +![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +Geneva, 1991 + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation Q.785 was prepared by Study Group XI and was approved under the Resolution No. 2 procedure on the 10th of September 1991. + +# --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. + +# **ISUP PROTOCOL TEST SPECIFICATION FOR SUPPLEMENTARY SERVICES** + +## **1 Introduction** + +This Recommendation contains a detailed set of tests for the supplementary services supported by Signalling System No. 7 Integrated Services Digital Network User Part (ISUP). + +Details of the supplementary services supported by ISUP can be found in *Blue Book* (1988) Recommendation Q.730. It should be noted that this test Recommendation covers those services which can be regarded as stable and clearly specified in *Blue Book* (1988) Recommendation Q.730. + +This Recommendation also covers supplementary services supported by Recommendation Q.767. + +The basic rules for the test specification can be found in Recommendation Q.780. + +## **2 Objective of the test specification** + +The objective of this test specification is to check that the ISUP protocol supported by a given implementation has the ability to correctly convey the necessary signalling information to support the supplementary services specified in *Blue Book* (1988) Recommendation Q.730 and Recommendation Q.767 (1991). Therefore this test list only covers areas of supplementary services where there is a direct impact on the ISUP protocol. However some call control functions are also verified, i.e. the transfer of speech/information is possible. + +It should be noted that this test specification does not attempt to test the operation of the supplementary services (end-to-end function tests), as these tests are outside the scope of this test specification. + +This test specification does not intend to provide exhaustive testing of *Blue Book* (1988) Recommendation Q.730 and Recommendation Q.767 (1991) supplementary services, but does intent to provide a reasonable level of confidence that the protocol required to support *Blue Book* (1988) Recommendation Q.730 and Recommendation Q.767 (1991) supplementary services has been implemented at a signalling point. + +This test specification does not address interactions between supplementary services. + +## **3 General principles of tests** + +The tests are described as “validation” tests or “validation” and “compatibility” tests. Each test description indicates in the field “type of test” whether the test is a “validation” (VAT) or a “validation” and “compatibility” (VAT & CPT) test. In addition to protocol testing, some call control functions are also checked, e.g. that the transfer of speech/information is possible. + +The test specification assumes a tested MTP for compatibility tests. + +## **4 Test environment** + +### **4.1 *Signalling relation*** + +A stable signalling relation is required between “SP A” and “SP B” in order to carry out effective tests. In addition telephony circuits are required for some of the tests. + +### 4.2 Configuration + +Only one configuration is required for the performance of these tests. This is shown in Figure 1/Q.785. + +![Diagram showing the test configuration for ISUP protocol tests for supplementary services. It consists of two main boxes, SP A and SP B. SP A is on the left and contains a smaller box labeled 'SP A'. SP B is on the right. A dashed arrow points from SP A to SP B, and another dashed arrow points from SP B to SP A. The word '(Note)' is written below the arrows. The text 'Configuration: 1' is written below the diagram. The code 'T1124620-90' is written in the bottom right corner of the diagram area.](9e6062272bbe3ddbb7c0606721d64cf0_img.jpg) + +Configuration: 1 + +T1124620-90 + +Diagram showing the test configuration for ISUP protocol tests for supplementary services. It consists of two main boxes, SP A and SP B. SP A is on the left and contains a smaller box labeled 'SP A'. SP B is on the right. A dashed arrow points from SP A to SP B, and another dashed arrow points from SP B to SP A. The word '(Note)' is written below the arrows. The text 'Configuration: 1' is written below the diagram. The code 'T1124620-90' is written in the bottom right corner of the diagram area. + +*Note* – The arrows indicate a signalling relation, and any necessary telephone/data circuits. + +FIGURE 1/Q.785 + +**Test configuration for ISUP protocol tests for supplementary services** + +### 4.3 Provision of stimulus at a signalling point + +This test specification requires the setting of various ISUP parameters at both the SP A (SP under test) and SP B. The setting of these parameters should be performed by an “appropriate stimulus” at the appropriate SP. + +No attempt is made in this Recommendation to specify the form of the “appropriate stimulus”, but instead the functional requirements are stated in general terms. + +The stimulus should be capable of setting the appropriate fields, parameters, and indicators in the ISUP *Blue Book* (1988) Recommendation Q.763 in the correct manner to support the supplementary services of *Blue Book* (1988) Recommendation Q.730. This equally applies to the amendments made by Recommendation Q.767 (1991) to *Blue Book* (1988) Recommendation Q.763 and to the supplementary services as described in Recommendation Q.767 (1991). + +It should be observed that depending on a number of factors the functions of the “appropriate stimulus” could be performed by various mechanisms. A number of possibilities are listed below : + +The stimulus could be: + +- i) an intrinsic part of a signalling point; +- ii) provided by a network connected to the signalling point; +- iii) provided by a “test box” connected to the signalling point; +- iv) provided by exchange data set at the signalling point; +- v) provided by user-network signalling. + +This list is not intended to be exhaustive. The choice of stimulus is a matter for the Administration concerned and does not necessarily require bilateral agreement. + +### 4.4 Checking of correct reception of parameters at signalling point under test + +This test specification requires the checking of the correct reception of various ISUP parameters at SP A (SP under test). + +No attempt is made in this Recommendation to specify how to perform this function, however depending on a number of factors the function of the “checking of receiving correctly of messages and parameters” could be performed by various mechanisms. A number of possibilities are listed below. + +The check could be performed by: + +- i) an intrinsic part of the SP A; +- ii) a network connected to SP A; +- iii) a “test box” connected to SP A; +- iv) monitoring/printout at the SP A; +- v) monitoring of the messages and information elements at the user-network interface. + +The list is not intended to be exhaustive. The choice of the method is a matter for Administration concerned and does not necessarily require bilateral agreement. + +### 4.5 *Check table* + +Many test scripts within the test specification include a check table. The check table lists specific indicators which must be checked. + +The check table does not necessarily include all the parameters and indicators that should be carried within any message. + +## 5 **ISUP protocol test list for supplementary services** + +All tests may be validation tests. Tests marked “\*” are compatibility tests. Tests marked “F.S” are for further study. + +## 1 *User-to-User Signalling (UUS)* + +### 1.1 User-to-User Signalling service 1 + +#### 1.1.1 Implicit request + +- \* 1.1.1.1.1 Successful – UUI in the forward message: sent +- \* 1.1.1.1.2 Successful – UUI in the forward message: received +- \* 1.1.1.2.1 Successful – UUI in the backward message: sent +- \* 1.1.1.2.2 Successful – UUI in the backward message: received +- \* 1.1.1.3.1 Unsuccessful – Explicit network rejection: sent +- \* 1.1.1.3.2 Unsuccessful – Explicit network rejection: received + +#### 1.1.2 Explicit request – F.S + +## 2 *Closed User Group (CUG)* + +### 2.1 Closed User Group (CUG) decentralized + +- \* 2.1.1 CUG call with outgoing access allowed: sent +- \* 2.1.2 CUG call, with outgoing access allowed: received +- \* 2.1.3 CUG call, with outgoing access not allowed, to a network offering the CUG supplementary service: sent +- \* 2.1.4 CUG call, with outgoing access not allowed, to a network offering the CUG supplementary service: received +- \* 2.1.5 CUG call, with outgoing access not allowed, to a network not offering the CUG supplementary service: sent +- \* 2.1.6 CUG call, with outgoing access not allowed, to a network not offering the CUG supplementary service: received +- \* 2.1.7 CUG call, international interlock code included: sent +- \* 2.1.8 CUG call, international interlock code included: received + +### 2.2 Closed User Group (CUG) centralized + +For further study. + +## 3 *Calling Line Identification (CLI)* + +- \* 3.1.1 CLIP – network provided: sent +- \* 3.1.2 CLIP – network provided: received +- \* 3.2.1 CLIP – user provided: sent +- \* 3.2.2 CLIP – user provided: received +- \* 3.3.1 CLIR – network provided: sent +- \* 3.3.2 CLIR – network provided: received +- \* 3.4.1 CLIR – user provided: sent +- \* 3.4.2 CLIR – user provided: received +- \* 3.5.1 CLI – not available: sent +- \* 3.5.2 CLI – not available: received +- \* 3.6.1 CLI – not sent in IAM, available with INR/INF +- \* 3.6.2 CLI – not received in IAM, available with INR/INF +- \* 3.6.3 CLI – not sent in IAM, not available with INR/INF +- \* 3.6.4 CLI – not received in IAM, not available with INR/INF +- 3.7.1 CLI – international address included: sent +- 3.7.2 CLI – international address included: received + +## 4 *Direct Dialling In* + +The Direct Dialling In (DDI) service has no impact on the ISUP protocol. Therefore no test scripts are provided for this supplementary service. + +## 5 *Call Forwarding* + +Further study. + +## 6 *Connected Line Identification (Col)* + +*Note* – These tests are only applicable to White Book Recommendation Q.767. + +- \* 6.1.1 COL – request: sent +- \* 6.1.2 COL – request: received +- \* 6.2.1 COLP – network provided: sent +- \* 6.2.2 COLP – network provided: received +- \* 6.3.1 COLP – user provided: sent +- \* 6.3.2 COLP – user provided: received +- \* 6.4.1 COLR – network provided: sent +- \* 6.4.2 COLR – network provided: received +- \* 6.5.1 COLR – user provided: sent +- \* 6.5.2 COLR – user provided: received +- \* 6.6.1 COL – not available: sent +- \* 6.6.2 COL – not available: received +- 6.7.1 COL – international address included: sent +- 6.7.2 COL – international address included: received +- \* 6.8.1 COL – received, but not requested + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------|-------|--|--|------|--|---------|--|--|-----------|--|---|--|--|--|---|-----|--|--|---|-------|--|--|---|-----|-----------|--|---|--|--|--|---|-----|--|---------|--|--|-----------|--|---|--|--|--|---|-----|-----------|--|---|--|--|--|---|-----| +| TEST NUMBER: 1.1.1.1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 2.2.1.6; Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: User-to-User Signalling service 1 – Implicit request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Successful – UUI in the forward messages: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that user-to-user information can be correctly sent in the forward call control messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM and REL generated at SP A contains a UUI parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
case a)
IAM (UUI) >
< ACM
< (CPG)
< ANM
REL (UUI) >
< RLC
case b)
IAM (UUI) >
< CON
REL (UUI) >
< RLC
| | | SP A | | | SP B | | case a) | | | IAM (UUI) | | > | | | | < | ACM | | | < | (CPG) | | | < | ANM | REL (UUI) | | > | | | | < | RLC | | case b) | | | IAM (UUI) | | > | | | | < | CON | REL (UUI) | | > | | | | < | RLC | +| SP A | | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM (UUI) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | (CPG) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL (UUI) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM (UUI) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL (UUI) | | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS A UUI PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS A UUI PARAMETER INCLUDED IN THE REL BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

IAM and REL

User-to-user Information parameter
Check that the parameter exists.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|------|--|------|--|---------|--|--|---|-----------|-----|---|--|-------|---|--|-----|---|--|--|---|-----------|-----|---|--|--|---------|--|--|---|-----------|-----|---|--|--|---|-----------|-----|---|--| +| TEST NUMBER: 1.1.1.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 2.2.1.6; Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: User-to-User Signalling service 1 – Implicit request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Successful – UUI in the forward messages: received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that user-to-user information can be correctly received in the forward call control messages | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM and REL generated at SP A contains a UUI parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
case a)
< IAM (UUI)
ACM >
(CPG) >
ANM >
< REL (UUI)
RLC >
case b)
< IAM (UUI)
CON >
< REL (UUI)
RLC >
| | | SP A | | SP B | | case a) | | | < | IAM (UUI) | ACM | > | | (CPG) | > | | ANM | > | | | < | REL (UUI) | RLC | > | | | case b) | | | < | IAM (UUI) | CON | > | | | < | REL (UUI) | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM (UUI) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (CPG) | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL (UUI) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM (UUI) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL (UUI) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP B to SP A.
  2. 2. Record the message sequence and parameters using a signal monitor.
  3. 3. CHECK A: WAS A UUI PARAMETER IN THE IAM CORRECTLY RECEIVED BY SP A?
  4. 4. CHECK B: WAS A UUI PARAMETER IN THE REL CORRECTLY RECEIVED BY SP A?
  5. 5. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

IAM and REL

User-to-user Information parameter
Check that the parameter exists.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| TEST NUMBER: 1.1.1.2.1 | | | | | | +| REFERENCE: Q.730, § 2.1.3; Q.767 | | | | | | +| TITLE: User-to-User Signalling service 1 – Implicit request | | | | | | +| SUBTITLE: Successful – UUI in the backward messages: sent | | | | | | +| PURPOSE: To verify that user-to-user information can be correctly sent in the backward call control messages | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B contains a UUI parameter
b) Arrange the stimulus such that the backward messages generated at SP A contains a UUI parameter | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A

case a)

ACM*(UUI)

(CPG (UUI))
ANM (UUI)
REL (UUI)

case b)

CON (UUI)
REL (UUI)



<

>


>
>
>
<


<

>
>
<
SP B


IAM (UUI)
*: UUI can be included in ACM if received from accesss




RLC


IAM (UUI)


RLC
| | | SP A

case a)

ACM*(UUI)

(CPG (UUI))
ANM (UUI)
REL (UUI)

case b)

CON (UUI)
REL (UUI) |


<

>


>
>
>
<


<

>
>
< | SP B


IAM (UUI)
*: UUI can be included in ACM if received from accesss




RLC


IAM (UUI)


RLC | +| SP A

case a)

ACM*(UUI)

(CPG (UUI))
ANM (UUI)
REL (UUI)

case b)

CON (UUI)
REL (UUI) |


<

>


>
>
>
<


<

>
>
< | SP B


IAM (UUI)
*: UUI can be included in ACM if received from accesss




RLC


IAM (UUI)


RLC | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | +| 3. | CHECK A: WAS A UUI PARAMETER IN THE IAM CORRECTLY RECEIVED BY SP A? | | | | | +| 4. | CHECK B: WERE ANY UUI PARAMETERS INCLUDED IN THE BACKWARD MESSAGES BY SP A? | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | +| CHECK TABLE | | | | | | +| ACM, CPG, ANM, CON and REL

User-to-user Information parameter
Check that the parameter exists. | | | | | | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TEST NUMBER: 1.1.1.2.2 | | | | | | +| REFERENCE: Q.730, § 2.1.3; Q.767 | | | | | | +| TITLE: User-to-User Signalling service 1 – Implicit request | | | | | | +| SUBTITLE: Successful – UUI in the backward messages: received | | | | | | +| PURPOSE: To verify that user-to-user information can be correctly received in the backward call control messages. | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A contains a UUI parameter.
b) Arrange the stimulus such that the backward messages generated at SP B contains UUI parameter. | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A
case a)

IAM (UUI)





RLC
case b)
IAM (UUI)



RLC










SP B





ACM* (UUI) *: UUI can be
(CPG (UUI)) included in ACM
ANM (UUI) if received from
REL (UUI) access.



CON (UUI)
REL (UUI)
| | | SP A
case a)

IAM (UUI)





RLC
case b)
IAM (UUI)



RLC |









| SP B





ACM* (UUI) *: UUI can be
(CPG (UUI)) included in ACM
ANM (UUI) if received from
REL (UUI) access.



CON (UUI)
REL (UUI) | +| SP A
case a)

IAM (UUI)





RLC
case b)
IAM (UUI)



RLC |









| SP B





ACM* (UUI) *: UUI can be
(CPG (UUI)) included in ACM
ANM (UUI) if received from
REL (UUI) access.



CON (UUI)
REL (UUI) | | | | +| TEST DESCRIPTION | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | +| 3. | CHECK A: WAS A UUI PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | +| 4. | CHECK B: WERE ANY UUI PARAMETERS INCLUDED IN THE BACKWARD MESSAGES CORRECTLY RECEIVED BY SP A? | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | +| CHECK TABLE | | | | | | +| ACM, CPG, ANM, CON and REL
User-to-User Information parameter
Check that the parameter exists. | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|--|---|-----------|-----|--|--|-------|--|--|-----|--|--|--|---|-----|-----|--|--|---------|--|--|--|---|-----------|-----|--|--|--|---|-----|-----|--|--| +| TEST NUMBER: 1.1.1.3.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: User-to-User Signalling service 1 – Implicit request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: Unsuccessful – Explicit network rejection: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the UUS service 1 explicit network rejection can be correctly sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B contains a UUI parameter.
b) Arrange the data at SP A such that the requested UUS service 1 is rejected by the network. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT and CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
< IAM (UUI)
ACM
(CPG)
ANM
< REL
RLC
case b)
< IAM (UUI)
CON
< REL
RLC
| | | SP A | | SP B | case a) | | | | < | IAM (UUI) | ACM | | | (CPG) | | | ANM | | | | < | REL | RLC | | | case b) | | | | < | IAM (UUI) | CON | | | | < | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM (UUI) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| (CPG) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM (UUI) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE USER-TO-USER INDICATORS PARAMETER INCLUDED IN THE ACM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: CONFIRM THAT A UUI PARAMETER WAS NOT INCLUDED IN THE BACKWARD MESSAGES BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM or CON
User-to-User Indicators parameter
  • – Type: 1 (response)
  • – Service 1: 00 (no information)
  • – Service 2: 00 (no information)
  • – Service 3: 00 (no information)
  • – Network discard indicator: 1 (UUI discarded by the network)
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 1.1.1.3.2 | | | | | +| REFERENCE: Q.767 | | | | | +| TITLE: User-to-User Signalling service 1 – Implicit request | | | | | +| SUBTITLE: Unsuccessful – Explicit network rejection: received | | | | | +| PURPOSE: To verify that the UUS service 1 explicit network rejection can be correctly received. | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A contains a UUI parameter.
b) Arrange the data at SP B such that the requested UUS service 1 is rejected by the network. | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE SEQUENCE: | | | | | +| SP A | | SP B | | | +| case a) | | | | | +| IAM (UUI) | -----> | | | | +| | <----- | ACM | | | +| | <----- | (CPG) | | | +| | <----- | ANM | | | +| REL | -----> | | | | +| | <----- | RLC | | | +| case b) | | | | | +| IAM (UUI) | -----> | | | | +| | <----- | CON | | | +| REL | -----> | | | | +| | <----- | RLC | | | +| TEST DESCRIPTION | | | | | +| 1. | Make a call from SP A to SP B. | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | +| 3. | CHECK A: WAS THE USER-TO-USER INDICATORS PARAMETER RECEIVED IN THE ACM (CON) BY SP A? | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | +| CHECK TABLE | | | | | +| ACM or CON
User-to-User Indicators parameter
– Type: 1: 1 (response)
– Service 1: 00 (no information)
– Service 2: 00 (no information)
– Service 3: 00 (no information)
– Network discard indicator: 1 (UUI discarded by the network) | | | | | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.1 | | | | | +| REFERENCE: Q.730, § 3; Q.767 | | | | | +| TITLE: Closed User Group – Decentralized | | | | | +| SUBTITLE: CUG call with outgoing access allowed: sent | | | | | +| PURPOSE: To verify that the parameters necessary for a CUG call with outgoing access allowed can be correctly sent (even if the receiving network does not offer the CUG supplementary service). | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains the optional forward call indicators parameter field with the CUG call indicator set to “CUG call, outgoing access allowed”, and the CUG interlock code parameter field. | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE SEQUENCE: | | | | | +| SP A | | SP B | | | +| IAM | -----> | | | | +| | <----- | ACM | | | +| | - - - - - | Ring tone | | | +| | <----- | ANM | | | +| Connectivity | - - - - - | Connectivity | | | +| REL | -----> | | | | +| | <----- | RLC | | | +| TEST DESCRIPTION | | | | | +| 1. | Make a call from SP A to SP B. | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | +| 3. | CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATOR PARAMETER INCLUDED IN THE IAM BY SP A? | | | | +| 4. | CHECK B: WAS THE CUG INTERLOCK CODE PARAMETER INCLUDED IN THE IAM BY SP A? | | | | +| 5. | CHECK C: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | +| 6. | CHECK D: WAS THE CONNECTION ESTABLISHED? | | | | +| 7. | CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | +| | Note – This test is valid even if SP B belongs to a network which does not offer the CUG supplementary service. | | | | +| CHECK TABLE | | | | | +| IAM | | | | | +| 1) | Optional Forward Call Indicators parameter
CUG Call Indicator: 10 (CUG call, outgoing access allowed) | | | | +| 2) | Closed User Group Interlock Code parameter
CUG Interlock Code: interlock code included | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|-----|--|--|-----------|--|--|-----|--|--|--------------|--|--------------|--|---|-----|-----|--|--| +| TEST NUMBER: 2.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 3; Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Closed User Group – Decentralized | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CUG call with outgoing access allowed: received | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the parameters necessary for a CUG call with outgoing access allowed can be correctly received (even if the receiving network does not offer the CUG supplementary service). | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains the optional forward call indicators parameter field with the CUG call indicator set to “CUG call, outgoing access allowed”, and the CUG interlock code parameter field. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
< IAM
ACM
Ring tone
ANM
Connectivity Connectivity
< REL
RLC
| | | SP A | | SP B | | < | IAM | ACM | | | Ring tone | | | ANM | | | Connectivity | | Connectivity | | < | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ring tone | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Connectivity | | Connectivity | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATORS PARAMETER RECEIVED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS THE CUG INTERLOCK CODE PARAMETER RECEIVED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WERE THE PARAMETER FIELDS CORRECTLY RECEIVED AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WAS THE CONNECTION ESTABLISHED? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Note – This test is valid even if SP A belongs to a network which does not offer the CUG supplementary service. | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1) | Optional Forward Call Indicators parameter
CUG Call Indicator: 10 (CUG call, outgoing access allowed) | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2) | Closed User Group Interlock Code parameter
CUG Interlock Code: interlock code included | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----------------|------|--|------|-----|--|--|--|--|-----|--|--|-----------|--|--|-----|--------------|--|--------------|-----|--|--|--|--|-----| +| TEST NUMBER: 2.1.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 3; Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Closed User Group – Decentralized | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CUG call with outgoing access not allowed, to a network offering the CUG supplementary service: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that the parameters necessary for a CUG call with outgoing access not allowed can be correctly sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) SP A and SP B should belong to networks which offer the CUG supplementary service.
b) Arrange the stimulus such that the IAM generated at SP A contains the Optional Forward Call Indicators parameter set to “CUG call outgoing access not allowed”, and a CUG interlock code that is acceptable at SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
ACM
Ring tone
ANM
Connectivity Connectivity
REL
RLC
| | | SP A | | SP B | IAM | | | | | ACM | | | Ring tone | | | ANM | Connectivity | | Connectivity | REL | | | | | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | | Ring tone | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANM | | | | | | | | | | | | | | | | | | | | | | | | | +| Connectivity | | Connectivity | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLC | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATORS PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WAS THE CUG INTERLOCK CODE PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WERE THE PARAMETER FIELDS SET CORRECTLY BY SP A AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK D: WAS THE CONNECTION ESTABLISHED? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 7. | CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM
1) Optional Forward Call Indicators parameter
CUG Call Indicator: 11 (CUG call, outgoing access allowed)
2) Closed User Group Interlock Code parameter
CUG Interlock Code: interlock code included | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.4 | | | +| REFERENCE: Q.730, § 3; Q.767 | | | +| TITLE: Closed User Group – Decentralized | | | +| SUBTITLE: CUG call with outgoing access not allowed, to a network offering the CUG supplementary service: received | | | +| PURPOSE: To verify that the parameters necessary for a CUG call with outgoing access not allowed can be correctly received. | | | +| PRE-TEST CONDITIONS:
a) SP A and SP B should belong to networks which offer the CUG supplementary service.
b) Arrange the stimulus such that the IAM generated at SP B contains the Optional Forward Call Indicators parameter set to “CUG call outgoing access not allowed”, and a CUG interlock code that is acceptable at SP A. | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:

SP A


ACM
Ring tone
ANM
Connectivity

RLC
 <    >   >   >   <    >           

Image: Sequence diagram showing message flow between SP A and SP B. IAM flows from SP B to SP A. ACM, Ring tone, ANM, and Connectivity flow from SP A to SP B. REL flows from SP B to SP A, followed by RLC from SP A to SP B.

 sequenceDiagram     participant SPA as SP A     participant SPB as SP B     SPB->>SPA: IAM     SPA->>SPB: ACM     Note over SPA,SPB: Ring tone     SPA->>SPB: ANM     Note over SPA,SPB: Connectivity     SPB->>SPA: REL     SPA->>SPB: RLC           
SP B

IAM




Connectivity
REL
| | | +| TEST DESCRIPTION | | | +| 1. | Make a call from SP B to SP A. | | +| 2. | Record the message sequence and parameters using a signal monitor. | | +| 3. | CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATORS PARAMETER RECEIVED IN THE IAM BY SP A? | | +| 4. | CHECK B: WAS THE CUG INTERLOCK CODE PARAMETER RECEIVED IN THE IAM BY SP A? | | +| 5. | CHECK C: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | +| 6. | CHECK D: WAS THE CONNECTION ESTABLISHED? | | +| 7. | CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | +| CHECK TABLE | | | +| IAM

1) Optional Forward Call Indicators parameter
CUG Call Indicator: 11 (CUG call, outgoing access not allowed)

2) Closed User Group Interlock Code parameter
CUG Interlock Code: interlock code included | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|----------------|--|--| +| TEST NUMBER: 2.1.5 | | | | | +| REFERENCE: Q.730, § 3; Q.767 | | | | | +| TITLE: Closed User Group – Decentralized | | | | | +| SUBTITLE: CUG call with outgoing access not allowed, to a network not offering the CUG supplementary service:
sent | | | | | +| PURPOSE: To verify that the parameters necessary for a CUG call with outgoing access not allowed can be correctly sent, to a network not offering the CUG service, and that a release can be accepted in response by SP A. | | | | | +| PRE-TEST CONDITIONS:
a) SP A should belong to a network which offers the CUG supplementary service.
b) SP B belongs to a network which does not offer the CUG service.
c) Arrange the stimulus such that the IAM generated at SP A contains the optional forward call indicators parameter field with the CUG call indicator set to “outgoing access not allowed”, and the CUG interlock code parameter field. | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | +| EXPECTED MESSAGE SEQUENCE: | | | | | +| SP A | | SP B | | | +| IAM | -----> | | | | +| | <----- | REL | | | +| RLC | -----> | | | | +| TEST DESCRIPTION | | | | | +| 1. | Make a call from SP A to SP B. | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | +| 3. | CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATORS PARAMETER INCLUDED IN THE IAM BY SP A? | | | | +| 4. | CHECK B: WAS THE CUG INTERLOCK CODE PARAMETER INCLUDED IN THE IAM BY SP A? | | | | +| 5. | CHECK C: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | +| 6. | CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | +| CHECK TABLE | | | | | +| IAM | | | | | +| 1) | Optional Forward Call Indicators parameter
CUG Call Indicator: 11 (CUG call, outgoing access not allowed) | | | | +| 2) | Closed User Group Interlock Code parameter
CUG Interlock Code: interlock code included | | | | + +| | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 2.1.6 | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 3; Q.767 | | | | | | | | | | | | | | | +| TITLE: Closed User Group – Decentralized | | | | | | | | | | | | | | | +| SUBTITLE: CUG call with outgoing access not allowed, to a network not offering the CUG supplementary service: received | | | | | | | | | | | | | | | +| PURPOSE: To verify that the parameters necessary for a CUG call with outgoing access not allowed can be correctly received, by a network not offering the CUG service, and rejected with a release message. | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) SP B should belong to a network which offers the CUG supplementary service.
b) SP A belongs to a network which does not offer the CUG service.
c) Arrange the stimulus such that the IAM generated at SP B contains the optional forward call indicators parameter field with the CUG call indicator set to “outgoing access not allowed”, and the CUG interlock code parameter field. | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
REL >
< RLC
| | | SP A | | SP B | | < | IAM | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP B to SP A.
  2. 2. Record the message sequence and parameters using a signal monitor.
  3. 3. CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATORS PARAMETER RECEIVED IN THE IAM BY SP A?
  4. 4. CHECK B: WAS THE CUG INTERLOCK CODE PARAMETER RECEIVED IN THE IAM BY SP A?
  5. 5. CHECK C: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
  6. 6. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | +| IAM
1) Optional Forward Call Indicators parameter
CUG Call Indicator: 11 (CUG call, outgoing access not allowed)
2) Closed User Group Interlock Code parameter
CUG Interlock Code: interlock code included | | | | | | | | | | | | | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 2.1.7 | | | +| REFERENCE: Q.730, § 3; Q.767 | | | +| TITLE: Closed User Group – Decentralized | | | +| SUBTITLE: CUG call, international interlock code included: sent | | | +| PURPOSE: To verify that an international interlock code is included for a call that crosses the international interface. | | | +| PRE-TEST CONDITIONS:
a) SP A and SP B should belong to networks which offer the CUG supplementary service.
b) Arrange the stimulus such that the IAM generated at SP A contains the optional forward call indicators parameter field indicating a CUG call, and the CUG interlock code parameter indicating an international interlock code that is acceptable to SP B. | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:

SP A

IAM




REL


—>
<—

<—

—>
<—
SP B


ACM
Ring tone
ANM
Connectivity

RLC
| | | +| TEST DESCRIPTION | | | +| 1. | Make a call from SP A to SP B. | | +| 2. | Record the message sequence and parameters using a signal monitor. | | +| 3. | CHECK A: WAS THE CUG INTERLOCK CODE PARAMETER INCLUDED IN THE IAM BY SP A? | | +| 4. | CHECK C: WAS THE PARAMETER FIELD SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | +| 5. | CHECK D: WAS THE CONNECTION ESTABLISHED? | | +| 6. | CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | +| CHECK TABLE | | | +| IAM
Closed User Group Interlock Code parameter
CUG Interlock Code: international interlock code included and coded as per Recommendation E.167 | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------|------|--|------|--|--|-----|-----|--|--|-----------|--|--|-----|--|--|--------------|--|--------------|--|--|-----|-----|--|--| +| TEST NUMBER: 2.1.8 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 3; Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Closed User Group – Decentralized | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CUG call, international interlock code included: received | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that for an international CUG call, that an international interlock can be correctly received. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) SP A and SP B should belong to networks which offer the CUG supplementary service.
b) Arrange the stimulus such that the IAM generated at SP B contains the optional forward call indicators parameter field indicating a CUG call, and the CUG interlock code parameter indicating an international interlock code that is acceptable to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
ACM
Ring tone
ANM
Connectivity Connectivity
REL
RLC
| | | SP A | | SP B | | | IAM | ACM | | | Ring tone | | | ANM | | | Connectivity | | Connectivity | | | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ring tone | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Connectivity | | Connectivity | | | | | | | | | | | | | | | | | | | | | | | | | +| | | REL | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CUG INTERLOCK CODE PARAMETER RECEIVED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK C: WAS THE PARAMETER FIELD RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK D: WAS THE CONNECTION ESTABLISHED? | | | | | | | | | | | | | | | | | | | | | | | | | | +| 6. | CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM
Closed User Group Interlock Code parameter
CUG Interlock Code: international interlock code included and coded as per Recommendation E.167 | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 3.1.1 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.1; Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLIP – Network provided: sent | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLIP (network provided) can be correctly sent in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI-network provided, presentation allowed. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B
IAM >
< ACM
< ANM
REL >
< RLC
| | | SP A | | SP B | IAM | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM

Calling Party Number parameter

  • – Presentation restriction indicator: 00 (presentation allowed)
  • – Screening indicator: 11 (network provided)
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|------|--|------|--|--|-----|--|---|--|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.1.2 | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.1; Q.767 | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLIP — Network provided: received | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLIP (network provided) can be correctly received in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains a CLI-network provided, presentation allowed. | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
<
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | | IAM | | < | | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | +| | < | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP B to SP A.
  2. 2. Record the message sequence and parameters using a signal monitor.
  3. 3. CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IN THE IAM BY SP A?
  4. 4. CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
  5. 5. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | +| IAM
Calling Party Number parameter
  • — Presentation restriction indicator: 00 (presentation allowed)
  • — Screening indicator: 11 (network provided)
| | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------| +| TEST NUMBER: 3.2.1 | | | +| REFERENCE: Q.730, § 4.1.1.1; Q.767 | | | +| TITLE: Calling Line Identification | | | +| SUBTITLE: CLIP – User provided: sent | | | +| PURPOSE: To verify that CLIP (user provided) can be correctly sent in the Calling Party Number parameter. | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI-user provided, presentation allowed. | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:

SP A

IAM


REL


->
<-
<-
->
<-
SP B


ACM
ANM

RLC
| | | +| TEST DESCRIPTION | | | +|
  1. 1.Make a call from SP A to SP B.
  2. 2.Record the message sequence and parameters using a signal monitor.
  3. 3.CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER INCLUDED IN THE IAM BY SP A?
  4. 4.CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
  5. 5.CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | +| CHECK TABLE | | | +| IAM
Calling Party Number parameter
  • – Presentation restriction indicator: 00 (presentation allowed)
  • – Screening indicator: 01 (user provided, verified and passed)
| | | + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.2.2 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.1; Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLIP – User provided: received | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLIP (user provided) can be correctly received in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains a CLI-user provided, presentation allowed. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | < | IAM | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +| IAM
Calling Party Number parameter
– Presentation restriction indicator: 00 (presentation allowed)
– Screening indicator: 01 (user provided, verified and passed) | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 3.3.1 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.2; Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLIP – Network provided: sent | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLIR (network provided) can be correctly sent in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI-network provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM →
← ACM
← ANM
REL →
← RLC
| | | SP A | | SP B | IAM | → | | | ← | ACM | | ← | ANM | REL | → | | | ← | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| IAM | → | | | | | | | | | | | | | | | | | | | | +| | ← | ACM | | | | | | | | | | | | | | | | | | | +| | ← | ANM | | | | | | | | | | | | | | | | | | | +| REL | → | | | | | | | | | | | | | | | | | | | | +| | ← | RLC | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM

Calling Party Number parameter

  • – Presentation restriction indicator: 01 (presentation restricted)
  • – Screening indicator: 11 (network provided)
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|------|--|------|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.3.2 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.2; Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLIR – Network provided: received | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLIR (network provided) can be correctly received in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains a CLI-network provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B
< IAM
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | < | IAM | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +|
  1. 1.Make a call from SP B to SP A.
  2. 2.Record the message sequence and parameters using a signal monitor.
  3. 3.CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IN THE IAM BY SP A?
  4. 4.CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
  5. 5.CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM

Calling Party Number parameter

  • – Presentation restriction indicator: 01 (presentation restricted)
  • – Screening indicator: 11 (network provided)
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|-----|----|--|--|----|-----|--|----|-----|-----|----|--|--|----|-----| +| TEST NUMBER: 3.4.1 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.2; Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLIR – User provided: sent | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLIR (user provided) can be correctly sent in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI-user provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM —>
<— ACM
<— ANM
REL —>
<— RLC
| | | SP A | | SP B | IAM | —> | | | <— | ACM | | <— | ANM | REL | —> | | | <— | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| IAM | —> | | | | | | | | | | | | | | | | | | | | +| | <— | ACM | | | | | | | | | | | | | | | | | | | +| | <— | ANM | | | | | | | | | | | | | | | | | | | +| REL | —> | | | | | | | | | | | | | | | | | | | | +| | <— | RLC | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM

Calling Party Number parameter

  • – Presentation restriction indicator: 01 (presentation restricted)
  • – Screening indicator: 01 (user provided, verified and passed)
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.4.2 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.2; Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLIR – User provided: received | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLIR (user provided) can be correctly received in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains a CLI-user provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B
< IAM
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | < | IAM | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +| IAM
Calling Party Number parameter
  • – Presentation restriction indicator: 01 (presentation restricted)
  • – Screening indicator: 01 (user provided, verified and passed)
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 3.5.1 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.1 b) | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI — Not available: sent | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a CLI (address not available) can be correctly sent in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI address not available. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM >
< ACM
< ANM
REL >
< RLC
| | | SP A | | SP B | IAM | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM

Calling Party Number parameter

  • — Odd/even indicator: 0 (even number of address signals)
  • — Nature of address signals: 0000000 (spare)
  • — Numbering plan indicator: 000 (spare)
  • — Calling party number incomplete indicator: 0 (complete)
  • — Presentation restriction indicator: 10 (address not available)
  • — Screening indicator: 11 (network provided)
  • — Address signal: none
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.5.2 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.1 b) | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI — Not available: received | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that CLI (address not available) can be correctly received in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains a CLI address not available. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | < | IAM | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM

Calling Party Number parameter

  • — Odd/even indicator: 0 (even number of address digits)
  • — Nature of address signals: 0000000 (spare)
  • — Numbering plans indicator: 000 (spare)
  • — Calling party number incomplete indicator: 0 (complete)
  • — Presentation restriction indicator: 10 (address not available)
  • — Screening indicator: 11 (network provided)
  • — Address signal: none
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------|--|------|-----|---|--|--|---|-----|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 3.6.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI — Not sent in IAM, available with INR/INF. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a CLI can be correctly sent in the INF message in response to an INR. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A doesn't contain a CLI parameter.
b) Arrange the stimulus such that the INR generated at SP B contains a request for the CLI.
c) Arrange the stimulus such that the INF generated at SP A contains a CLI parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE DE SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM >
< INR
INF >
< ACM
< ANM
REL >
< RLC
| | | SP A | | SP B | IAM | > | | | < | INR | INF | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | INR | | | | | | | | | | | | | | | | | | | | | | | | | +| INF | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1.
2.
3.
4.
5.
6.
7. | Make a call from SP A to SP B.
Record the message sequence and parameters using a signal monitor.
CHECK A: WAS THE INFORMATION REQUEST INDICATORS PARAMETER RECEIVED IN THE INR BY SP A?
CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
CHECK C: WAS THE CALLING PARTY NUMBER PARAMETER INCLUDED IN THE INF BY SP A?
CHECK D: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INR
Information Request Indicators parameter
Calling party address request indicator: 1 (calling party address requested) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INF
1) Information Indicators parameter
Calling party address response indicator: 11 (calling party address included)
2) Calling Party Number parameter
Presentation restriction indicator: 00/01 (presentation allowed/restricted)
Screening indicator: 11/01 (network provided/user provided) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.6.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI — Not received in IAM, available with INR/INF. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a CLI can be requested in the INR message and correctly received in the INF message. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B does not contain a CLI parameter.
b) Arrange the stimulus such that the INR generated at SP A contains a request for the CLI.
c) Arrange the stimulus such that the INF generated at SP B contains a CLI parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE DE SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
< IAM
INR >
< INF
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | < | IAM | INR | > | | | < | INF | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | +| INR | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | INF | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1.
2.
3.
4.
5.
6.
7. | Make a call from SP B to SP A.
Record the message sequence and parameters using a signal monitor.
CHECK A: WAS THE INFORMATION REQUEST INDICATORS PARAMETER RECEIVED IN THE INR BY SP A?
CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
CHECK C: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IN THE INF BY SP A?
CHECK D: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
CHECK E: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INR
Information Request Indicators parameter
Calling party address request indicator: 1 (calling party address requested) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INF
1) Information Indicators parameter
Calling party address response indicator: 11 (calling party address included)
2) Calling Party Number parameter
Presentation restriction indicator: 00/01 (presentation allowed/restricted)
Screening indicator: 11/01 (network provided/user provided) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|------|--|------|-----|--|--|--|--|-----|-----|--|--|--|--|-----|--|--|-----|-----|--|--|--|--|-----| +| TEST NUMBER: 3.6.3 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI — Not sent in IAM, not available with INR/INF. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an indication of calling party address not available can be sent in the INF message in response to an INR message. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A does not contain a CLI parameter.
b) Arrange the stimulus such that the INR generated at SP B contains a request for the CLI.
c) Arrange the stimulus such that the INF generated at SP A contains an indication that the calling party is not available. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE DE SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
IAM
INR
INF
ACM
ANM
REL
RLC
 --------> <-------- --------> <-------- <-------- --------> <-------- 
| | | SP A | | SP B | IAM | | | | | INR | INF | | | | | ACM | | | ANM | REL | | | | | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | INR | | | | | | | | | | | | | | | | | | | | | | | | | +| INF | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANM | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLC | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. Make a call from SP A to SP B.
2. Record the message sequence and parameters using a signal monitor.
3. CHECK A: WAS THE INFORMATION REQUIRED INDICATORS PARAMETER RECEIVED IN THE INR BY SP A?
4. CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
5. CHECK C: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
6. CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INR
Information Request Indicators parameter
Calling party address request indicator: 1 (calling party address requested) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INF
Information Indicators parameter
Calling party response indicator: 01 (calling party address not available) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|-----|---|--|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.6.4 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.730, § 4.1.1.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI — Not received in IAM, not available in INR/INF. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an indication of calling party address not available can be correctly received in the INF message. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B does not contain a CLI parameter.
b) Arrange the stimulus such that the INR generated at SP A contains a request for the CLI.
c) Arrange the stimulus such that the INF generated at SP B contains an indication that the calling party address is not available. | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE DE SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
< IAM
INR >
< INF
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | < | IAM | INR | > | | | < | INF | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | +| INR | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | INF | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1.
2.
3.
4.
5.
6. | Make a call from SP B to SP A.
Record the message sequence and parameters using a signal monitor.
CHECK A: WAS THE INFORMATION REQUEST INDICATORS PARAMETER INCLUDED IN THE INR BY SP A?
CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
CHECK C: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INR
Information Request Indicators parameter
Calling party address request indicator: 1 (calling party address requested) | | | | | | | | | | | | | | | | | | | | | | | | | | | +| INF
Information Indicators parameter
Calling party response indicator: 01 (calling party address not available) | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|-----|--|--|--|--|-----|--|--|-----|-----|--|--|--|--|-----| +| TEST NUMBER: 3.7.1 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI – International address included: sent | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a country code is included in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains a CLI. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM
ACM
ANM
REL
RLC
IAM   —>
<—   ACM
<—   ANM
REL   —>
<—   RLC
Re-rendering diagram for clarity
 SP A                                        SP B  IAM             ----------------->                 <-----------------          ACM                 <-----------------          ANM REL             ----------------->                 <-----------------          RLC       
| | | SP A | | SP B | IAM | | | | | ACM | | | ANM | REL | | | | | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | +| | | ANM | | | | | | | | | | | | | | | | | | | +| REL | | | | | | | | | | | | | | | | | | | | | +| | | RLC | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER INCLUDED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +| IAM
Calling Party Number parameter
– Nature of address signals: 0000100 (international number)
– Numbering plan indicator: 001 (Recommendation E.164/E.163)
– Address signal: CC + NDC + SN | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|------|--|------|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 3.7.2 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Calling Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: CLI — International address included: received | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an international address can be correctly received in the Calling Party Number parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains an international CLI. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
< IAM
ACM >
ANM >
< REL
RLC >
| | | SP A | | SP B | | < | IAM | ACM | > | | ANM | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP B to SP A.
  2. 2. Record the message sequence and parameters using a signal monitor.
  3. 3. CHECK A: WAS THE CALLING PARTY NUMBER PARAMETER RECEIVED IN THE IAM BY SP A?
  4. 4. CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
  5. 5. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +| IAM
Calling Party Number parameter
  • — Nature of address indicator: 0000100 (international number)
  • — Numbering plan indicator: 001 (Recommendation E.164/E.163)
  • — Address signal: CC + NDC + SN
| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|------|--|------|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 6.1.1 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COL — Request: sent | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a request for COL can be correctly sent in the Optional Forward Call Indicators parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP A contains the request for COL. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
IAM >
< ACM
< ANM
REL >
< RLC
| | | SP A | | SP B | IAM | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +|
  1. 1. Make a call from SP A to SP B.
  2. 2. Record the message sequence and parameters using a signal monitor.
  3. 3. CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATORS PARAMETER INCLUDED IN THE IAM BY SP A?
  4. 4. CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW?
  5. 5. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE?
| | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM

Optional Forward Call Indicators parameters

Connected line identity request indicator: 1 (requested)

| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|--|---|-----|-----|--|--|-----|--|--|--|---|-----|-----|--|--| +| TEST NUMBER: 6.1.2 | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COL — Request: received | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a request for COL can be correctly received in the Optional Forward Call Indicators parameter. | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the IAM generated at SP B contains the request for COL. | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B
< IAM
ACM
ANM
< REL
RLC
| | | SP A | | SP B | | < | IAM | ACM | | | ANM | | | | < | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE OPTIONAL FORWARD CALL INDICATORS PARAMETER RECEIVED IN THE IAM BY SP A? | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | +|

IAM
Optional Forward Call Indicators parameters
Connected line identity request indicator: 1 (requested)

| | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|--|--|-----|-----|--|--|-----|--|--|--|--|-----|-----|--|--|---------|--|--|--|--|-----|-----|--|--|--|--|-----|-----|--|--| +| TEST NUMBER: 6.2.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COLP — Network provided: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COLP (network provided) can be correctly sent in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP A contains a COL — network provided, presentation allowed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
IAM
ACM
ANM
REL
RLC
case b)
IAM
CON
REL
RLC
| | | SP A | | SP B | case a) | | | | | IAM | ACM | | | ANM | | | | | REL | RLC | | | case b) | | | | | IAM | CON | | | | | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER INCLUDED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 00 (presentation allowed)
— Screening indicator: 11 (network provided) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------| +| TEST NUMBER: 6.2.2 | | | +| REFERENCE: Q.767 | | | +| TITLE: Connected Line Identification | | | +| SUBTITLE: COLP — Network provided: received | | | +| PURPOSE: To verify that a COLP (network provided) can be correctly received in the Connected Number parameter. | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP B contains a COL — network provided, presentation allowed. | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
case a)
 IAM             — >                              < —             ACM                 < —             ANM REL             — >                              < —             RLC 
case b)
 IAM             — >                              < —             CON REL             — >                              < —             RLC 
| | | +| TEST DESCRIPTION | | | +| 1. | Make a call from SP A to SP B. | | +| 2. | Record the message sequence and parameters using a signal monitor. | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER RECEIVED IN THE ANM (CON) BY SP A? | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | +| CHECK TABLE | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 00 (presentation allowed)
— Screening indicator: 11 (network provided) | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--|---------|--|--|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 6.3.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COLP — User provided: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COLP (user provided) can be correctly sent in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP A contains a COL — user provided, presentation allowed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
< IAM
ACM >
ANM >
< REL
RLC >
case b)
< IAM
CON >
< REL
RLC >
| | | SP A | | SP B | case a) | | | | < | IAM | ACM | > | | ANM | > | | | < | REL | RLC | > | | case b) | | | | < | IAM | CON | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER INCLUDED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 00 (presentation allowed)
— Screening indicator: 01 (user provided, verified and passed) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|-----|--|--|--|--|-----|--|--|-----|-----|--|--|--|--|-----|-------------|--|--|-----|--|--|--|--|-----|-----|--|--|--|--|-----| +| TEST NUMBER: 6.3.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COLP — User provided: received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COLP (user provided) can be correctly received in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP B contains a COL — user provided, presentation allowed. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
case a)
IAM
ACM
ANM
REL
RLC

case b)
IAM
CON
REL
RLC
| | | SP A | | SP B | case a) | | | IAM | | | | | ACM | | | ANM | REL | | | | | RLC |
case b) | | | IAM | | | | | CON | REL | | | | | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER RECEIVED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 00 (presentation allowed)
— Screening indicator: 01 (user provided, verified and passed) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|--|--|-----|-----|--|--|-----|--|--|--|--|-----|-----|--|--|---------|--|--|--|--|-----|-----|--|--|--|--|-----|-----|--|--| +| TEST NUMBER: 6.4.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COLR — Network provided: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COLR (network provided) can be correctly sent in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP A contains a COL — network provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
IAM
ACM
ANM
REL
RLC
case b)
IAM
CON
REL
RLC
| | | SP A | | SP B | case a) | | | | | IAM | ACM | | | ANM | | | | | REL | RLC | | | case b) | | | | | IAM | CON | | | | | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER INCLUDED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 01 (presentation allowed)
— Screening indicator: 11 (network provided) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|-----|--|--|--|--|-----|--|--|-----|-----|--|--|--|--|-----|---------|--|--|-----|--|--|--|--|-----|-----|--|--|--|--|-----| +| TEST NUMBER: 6.4.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COLR — Network provided: received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COLR (network provided) can be correctly received in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP B contains a COL — network provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
IAM
ACM
ANM
REL
RLC
case b)
IAM
CON
REL
RLC
| | | SP A | | SP B | case a) | | | IAM | | | | | ACM | | | ANM | REL | | | | | RLC | case b) | | | IAM | | | | | CON | REL | | | | | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER RECEIVED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 01 (presentation restricted)
— Screening indicator: 11 (network provided) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|--|--|-----|-----|--|--|-----|--|--|--|--|-----|-----|--|--|---------|--|--|--|--|-----|-----|--|--|--|--|-----|-----|--|--| +| TEST NUMBER: 6.5.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COLR — User provided: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COLR (user provided) can be correctly sent in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP B contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP A contains a COL — user provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
IAM
ACM
ANM
REL
RLC
case b)
IAM
CON
REL
RLC
| | | SP A | | SP B | case a) | | | | | IAM | ACM | | | ANM | | | | | REL | RLC | | | case b) | | | | | IAM | CON | | | | | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER INCLUDED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 01 (presentation restricted)
— Screening indicator: 01 (user provided, verified and passed) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----|---------|--|--|-----|---|--|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 6.5.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COLR — User provided: received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COLR (user provided) can be correctly received in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS:
a) Arrange the stimulus such that the IAM generated at SP A contains the request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP B contains a COL — user provided, presentation restricted. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
IAM >
< ACM
< ANM
REL >
< RLC
case b)
IAM >
< CON
REL >
< RLC
| | | SP A | | SP B | case a) | | | IAM | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | case b) | | | IAM | > | | | < | CON | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM or CON
Connected Number parameter
— Presentation restriction indicator: 01 (presentation restricted)
— Screening indicator: 01 (user provided, verified and passed) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|--|---|-----|-----|--|--|-----|--|--|--|---|-----|-----|--|--|---------|--|--|--|---|-----|-----|--|--|--|---|-----|-----|--|--| +| TEST NUMBER: 6.6.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COL — Not available: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COL (address not available) can be correctly sent in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the ANM (CON) generated at SP A contains a COL — address not available. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
< IAM
ACM
ANM
< REL
RLC
case b)
< IAM
CON
< REL
RLC
| | | SP A | | SP B | case a) | | | | < | IAM | ACM | | | ANM | | | | < | REL | RLC | | | case b) | | | | < | IAM | CON | | | | < | REL | RLC | | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER INCLUDED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

ANM or CON

Connected Number parameter

  • — Odd/even indicator: 0 (even number of address digits)
  • — Nature of address indication: 0000000 (spare)
  • — Numbering plan indicator: 000 (spare)
  • — Connected number incomplete indicator: 0 (complete)
  • — Presentation restriction indicator: 10 (address not available)
  • — Screening indicator: 11 (network provided)
  • — Address signal: none
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----|---------|--|--|-----|---|--|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 6.6.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COL — Not available: received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a COL (address not available) can be correctly received in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the ANM (CON) generated at SP B contains a COL — address not available. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
case a)
IAM >
< ACM
< ANM
REL >
< RLC
case b)
IAM >
< CON
REL >
< RLC
| | | SP A | | SP B | case a) | | | IAM | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | case b) | | | IAM | > | | | < | CON | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED PARTY NUMBER PARAMETER RECEIVED IN THE ANM (CON) RECEIVED BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

ANM or CON

Connected Number parameter

  • — Odd/even indicator: 0 (even number of address signals)
  • — Nature of address indicator: 0000000 (spare)
  • — Numbering plan indicator: 000 (spare)
  • — Connected number incomplete indicator: 0 (complete)
  • — Presentation restriction indicator: 10 (address not available)
  • — Screening indicator: 11 (network provided)
  • — Address signal: none
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|--|---|-----|-----|---|--|-----|---|--|--|---|-----|-----|---|--|---------|--|--|--|---|-----|-----|---|--|--|---|-----|-----|---|--| +| TEST NUMBER: 6.7.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COL — International address included: sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that a country code is added to the national number and sent in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the ANM (CON) generated at SP A contains a COL. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP A SP B
case a)
< IAM
ACM >
ANM >
< REL
RLC >
case b)
< IAM
CON >
< REL
RLC >
| | | SP A | | SP B | case a) | | | | < | IAM | ACM | > | | ANM | > | | | < | REL | RLC | > | | case b) | | | | < | IAM | CON | > | | | < | REL | RLC | > | | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ACM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ANM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | IAM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CON | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | REL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| RLC | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP B to SP A. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER INCLUDED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

ANM or CON

Connected Number parameter

  • — Nature of address indicator: 0000100 (international number)
  • — Numbering plan indicator: 001 (Recommendation E.164/E.163)
  • — Address signal: CC + NDC + SN
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|----------------|------|--|------|---------|--|--|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----|---------|--|--|-----|---|--|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 6.7.2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: COL — International address included: received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PURPOSE: To verify that an international address can be correctly received in the Connected Number parameter. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| PRE-TEST CONDITIONS: Arrange the stimulus such that the ANM (CON) generated at SP B contains a COL. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

EXPECTED MESSAGE SEQUENCE:

SP ASP B
case a)
IAM >
< ACM
< ANM
REL >
< RLC
case b)
IAM >
< CON
REL >
< RLC
| | | SP A | | SP B | case a) | | | IAM | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | case b) | | | IAM | > | | | < | CON | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. | Make a call from SP A to SP B. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2. | Record the message sequence and parameters using a signal monitor. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 3. | CHECK A: WAS THE CONNECTED NUMBER PARAMETER RECEIVED IN THE ANM (CON) BY SP A? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4. | CHECK B: WERE THE PARAMETER FIELDS RECEIVED CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5. | CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CHECK TABLE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

ANM or CON

Connected Number parameter

  • — Nature of address indicator: 10000100 (international number)
  • — Number plan indicator: 001 (Recommendation E.164/E.163)
  • — Address signal: CC + NDC + SN
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|------|--|------|---------|--|--|-----|---|--|--|---|-----|--|---|-----|-----|---|--|--|---|-----|---------|--|--|-----|---|--|--|---|-----|-----|---|--|--|---|-----| +| TEST NUMBER: 6.8.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REFERENCE: Q.767 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TITLE: Connected Line Identification | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| SUBTITLE: 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:
a) Arrange the stimulus such that the IAM generated at SP A does not contain a request for COL.
b) Arrange the stimulus such that the ANM (CON) generated at SP B contains a COL. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CONFIGURATION: 1 | TYPE OF TEST: VAT & CPT | TYPE OF SP: SP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| EXPECTED MESSAGE SEQUENCE:

SP A SP B
case a)
IAM >
< ACM
< ANM
REL >
< RLC
case b)
IAM >
< CON
REL >
< RLC
| | | SP A | | SP B | case a) | | | IAM | > | | | < | ACM | | < | ANM | REL | > | | | < | RLC | case b) | | | IAM | > | | | < | CON | REL | > | | | < | RLC | +| SP A | | SP B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case a) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ACM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | ANM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| case b) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| IAM | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | CON | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| REL | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | < | RLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TEST DESCRIPTION | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1. Make a call from SP A to SP B.
2. Record the message sequence and parameters using a signal monitor.
3. The calling party should clear the call.
4. CHECK A: WAS THE CONNECTED NUMBER PARAMETER RECEIVED IN THE ANM (CON) BY SP A?
5. CHECK B: DID THE CALL COMPLETE?
6. CHECK C: WAS THE MESSAGE SEQUENCE AS ABOVE? | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c35df6b9e58097dfe67b47e1cdb48a3b1e46c62 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:456a3d8e73d3f11e087fd16107222218902728d9b3a6993ba69a6f1bbc7d9c80 +size 65434 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1ee858dc230171597d270d275c79fb57d1feac7 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1311cbc029f75ee16d5070196b7f4f8cf87fa0918228404bf9acff2725db96d +size 13734 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec93cb6faeabd0488c84afd92b4e94213083acb1 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:523acb7f439ac6941560c8ebbf8aec0b74a005f7425be44660e723b4fc800acd +size 60535 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..318ee6ce2457f611d7987e02486e9d8ec9073045 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9edacb23e8ec23130f27dfef97baf4e26b3fcb0e690180813d92507a41337c8 +size 6004 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d2dfe00f4cf9e5686d207d6a909d4a9686cefe1 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b133508a80d1c9aa0d8d0acc0b8b606980d791f3a4679fa615e58e6c84726b96 +size 7306 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5001aa2ede195fc2f2dc0a93f8bde2db97814005 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e73f50d14befb0735b35fe20a50a8b07f967c01cc310ce8f51b6d6df4e670350 +size 80255 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10ed244230bfba752f9c74abd7d0fd5034c41b0e --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4de80d701cce6fb848d3217c2f9cf08af48e679cb0911e1dd5d5849ad008f7bf +size 11866 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fccccebc2dfcd96e0d79e087218577b5482caf32 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c686e1a0a3c15330befdb5e1e1872d2d5aa5a3fc8cfecc87314e11b2ab4cdb58 +size 26414 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcdee1ec955613844f3a53e62d0dd6fa7237b2da --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f8d4fc05fc1eafa75429321f883603108e17176869cd02e3a10aed3c95ecc1 +size 86805 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0281c93bb570e50924107ec5320ac29043e13ea2 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c25dd4a05022facf37ac1511cdcb2bf89cc6a52274eed777f96ee1b7f5a16e2b +size 26744 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aeb2235ea85c08ab337341eff830afd71c0988b4 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e5db5d0b946aa2f54ffd4cd8f30405d346b8081034739061ba97435ff80eaf8 +size 14034 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c99c236642916948cd338d168dec8309e62571a6 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8fa0811f17dad4c413e52c8c8f43c073f253beca16a70d1376908504e17e106 +size 78155 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9035fa3942597cfc031be3f8b96dee04be7c2f4 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef504fc92c781fed8d27fed0002832ae7c6e9f70ee68a991a385e5ff0b0c3b6e +size 76772 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63ee2e15fe8bcfe40f8182d1997bb0842b2b40bf --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e27b6a253e8ad12ccb29f075f889e8ae280277769e9513d0a76a083f4e278bd6 +size 18989 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79dc05c72938d742659de822c5b8c7bcd87c8849 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60f2afed0d1f61783d13c16aa95ff065939f500020a68756e351156481a7d6f0 +size 13665 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81bfa14715b625c6be2e35e651242af1c7b7d477 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dc9a6a1074918eff6a70b9dadf4037101df086fd6cfad30f65030f6a1b1731f +size 83426 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd212b131e978889c8ff8ec2c8785ce53cef69bd --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:727851458b79031fe6e7c75042387e1ef0968e753a29efcc9f2b0f3d597ff049 +size 12189 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6281caaeab22a24886e41eb57436f0cf9c35141c --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92bf6e890a8ccdb465b51b764f963661167603102c470445f2b6e34e675278a9 +size 115143 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..678b1a5cab3db3f42fe74a7057f9279370420fa4 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dcf4d9df718a5bede0f5bcc16acd9fd1f388febabc2a02e512ee98e2599b2ae +size 12467 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fa5aff996ef2bd82d105c81874295cba135961c --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:735de7c21ae39c6292894a88f2455966d4653cb9692b42e32d9ea98b2e4cfe4e +size 96390 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b345b0f73f0ce27935acd67a3c25882eaaffbbe --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dccc91e1cff7f0c76d780840ab6b65689a27c8f111e0989a00be58fcc9a7279 +size 76560 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0437dc5e87ff816bbe270b484ae47f72471103f1 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af8f19812cde1ef96320f1e64f5e9f27c55b3f367d37d06f32b17953c162b7da +size 13693 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6039969f59fda4302ac37463e9b73f1e831f6d8f --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eaff9fc643416ee00e4d4e885da66d0c1a4f64995790cc16a5929e2289d6ef15 +size 14004 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61ad84e1ec7c66f8aac98e069d22a4b6b5a2465c --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f369381bfce7b470b87776844dfdbc37266fdde047441977babe8f46b52d4ba +size 8628 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..017b9561a33a75c7d433054e63cee2e472cb9643 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17e3950e8df19ddca1afd37be09f634b6d401887adf1b07d70e003312e44f376 +size 13520 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fa17fabbff3b6e01953f910097eac28902fb94e --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ecea09e535d308468566f2c225ff71c9cc1a98cdb36ed4615b7440997e33135 +size 13824 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06e97790969904497099b43f7b5e3a2f89dabe71 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a51144bf10a5a8a076310d50c72f44b74c604c0c0e813618387c1f7f411201c +size 108160 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01e87dd472615ad5ce03d252b27c3e6b99769952 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b894d85a093c344a3cc8a9ba9bba6de43333e8fe3b94075fbc6d58fdb9a295c1 +size 90102 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6842c0e153e8ce88a0414e0cff24752edcd3a8eb --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cee059d327cd4d9e0a007ebe08b15ea2d87d24c856320da33618c137745a22bd +size 14145 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..355ac071c3abbcad4324d1993d200cb2e222db56 --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eb5295e4befa966cbd5f08c1bba1a74a52a64f60e01ae2b815e01887168eba4 +size 19210 diff --git a/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/raw.md b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..510b9e8ad135c25aadae4b08e67ae22d1979906c --- /dev/null +++ b/marked/Q/T-REC-Q.81.3-199109-I_PDF-E/raw.md @@ -0,0 +1,1447 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**Q.81** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +# **FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN** --- + +## **STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES** + +SECTION 3 – CALLING LINE IDENTIFICATION PRESENTATION (CLIP) +AND CALLING LINE IDENTIFICATION RESTRICTION (CLIR) + +SECTION 5 – CONNECTED LINE IDENTIFICATION, PRESENTATION +AND RESTRICTION (COLP AND COLR) + +**Modifications to +Recommendation Q.81** + +--- + +![CCITT logo: A globe with the letters CCITT.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +Geneva, 1991 + +## FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation Q.81, §§ 3 and 5 was prepared by Study Group XI and was approved under the Resolution No. 2 procedure on the 10th of September 1991. + +## --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. + +## **STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES** + +*(revised 1991)* + +## **3 Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR)** + +### **3.1 Scope** + +This Recommendation defines the stage 2 of the integrated services digital network (ISDN) as provided by the telecommunications operators for the Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR) supplementary services. Stage 2 identifies the functional capabilities and the information flows needed to support the service description. The stage 2 description also identifies user operations not directly associated with a call (see Recommendation I.130 [1]). + +This Recommendation is defined according to the methodology specified in Recommendation Q.65 [2]. + +This Recommendation does not formally describe the relationship between these supplementary services and the basic call but, where possible, this information is included for guidance. + +In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities within a private ISDN; it does however define which functional entities may be allocated to a private ISDN. + +This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. + +The CLIP supplementary service provides the called party with the possibility to receive identification of the calling party. + +The CLIR supplementary service enables the calling party to prevent presentation of its ISDN number to the called party. + +The CLIP and CLIR supplementary services are applicable to all telecommunication services. + +This Recommendation is applicable to the stage 3 Recommendations for the ISDN CLIP and CLIR supplementary services, as defined in Recommendation I.130 [1]. + +### **3.2 References** + +These references are cited at the appropriate places in the text and the publications are listed hereafter. Dated references, subsequent amendments to, or revisions of any of these publications apply to this Recommendation only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. + +- [1] CCITT Rec. I.130 (1988) – Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. +- [2] CCITT Rec. Q.65 (1988) – Stage 2 of the method for the characterization of services supported by an ISDN. +- [3] CCITT Rec. I.251.3 – Calling Line Identification Presentation (CLIP). + +- [4] CCITT Rec. I.251.4 – Calling Line Identification Restriction (CLIR). +- [5] CCITT Rec. Q.71 – ISDN 64 kbit/s circuit mode switched bearer services. +- [6] CCITT Rec. I.112 (1988) – Vocabulary of terms for ISDNs. +- [7] CCITT Rec. I.210 (1988) – Principles of telecommunication services supported by an ISDN and the means to describe them. +- [8] CCITT Rec. E.164 (1991) – Numbering plan for the ISDN era. +- [9] CCITT Rec. I.330 (1988) – ISDN numbering and addressing principles. + +### 3.3 *Definitions* + +For the purposes of this Recommendation, the following definitions apply: + +#### **integrated services digital network (ISDN)** + +See definition 308 of § 2.3 of Recommendation I.112 [6]. + +#### **service: telecommunication service** + +See definition 201 of § 2.2 of Recommendation I.112 [6]. + +#### **supplementary service** + +See § 2.4 of Recommendation I.210 [7]. + +#### **ISDN number** + +A number conforming to the numbering plan and structure specified in Recommendation E.164 [8]. + +#### **PNP number** + +A number conforming to the numbering plan and structure in a private network. + +#### **sub-address** + +See § 5.4 of Recommendation I.330 [9]. + +#### **calling line identity** + +The address (the ISDN number, and if supplied the sub-address) of the calling line, and the screening indicator. If these are not available the reason is indicated, via the presentation indicator. + +#### **presentation indicator (PI)** + +The PI provides instructions on whether or not the provided calling line identity is allowed to be presented, or indicates that the number is not available. + +#### **screening indicator (SI)** + +The SI provides information on the source and the quality of the provided information. + +### 3.4 *Symbols and abbreviations* + +| | | +|--------|------------------------------------------| +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| PI | Presentation Indicator | +| SI | Screening indicator | +| ISDN | Integrated services digital network | +| TE | Terminal equipment | +| PNX | Private network exchange | +| LE | Local exchange | +| INT TR | International transit exchange | +| FEA | Functional entity action | +| SDL | Specification and description language | +| PNP | Private Numbering Plan | + +### 3.5 *Description* + +The relationship between the CLIP and CLIR supplementary services is described in § 3.6.6 of Recommendation I.251.3 [3] and in Recommendation I.251.4 [4]. + +The provisions for overriding the CLIP supplementary service are described in §§ 3.3.4.2 and 3.6.6 of Recommendation I.251.3 [3] and in Recommendation I.251.4 [4]. + +### 3.6 *Derivation of a functional model* + +#### 3.6.1 *Functional model description* + +The model for the CLIP and CLIR supplementary services is shown in Figure 3-1/Q.81. + +![Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. FE1 is connected to FE2 via interface r_a. FE2 is connected to FE3 via interface r_b. FE3 is connected to FE4 via interface r_c. FE4 is connected to FE5 via interface r_d.](d980a3f9608055996a07f31788baf827_img.jpg) + +``` +graph LR; FE1[FE1] -- r_a --> FE2[FE2]; FE2 -- r_b --> FE3[FE3]; FE3 -- r_c --> FE4[FE4]; FE4 -- r_d --> FE5[FE5]; +``` + +Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. FE1 is connected to FE2 via interface r\_a. FE2 is connected to FE3 via interface r\_b. FE3 is connected to FE4 via interface r\_c. FE4 is connected to FE5 via interface r\_d. + +T1126230-90 + +FIGURE 3-1/Q.81 + +**Functional model** + +#### 3.6.2 *Description of the functional entities* + +The functional entities required by the CLIP and CLIR supplementary services above those of the basic call are as follows: + +- FE1: caller provided information and CLIR requesting entity; +- FE2: service information checking entity; +- FE3: handling of calling line identity at international gateway; +- FE4: service providing entity; +- FE5: service requesting entity. + +#### 3.6.3 *Relationship with a basic service* + +The relationship with a basic service is shown in Figure 3-2/Q.81. The model for basic call handling is defined in Recommendation Q.71. + +### 3.7 *Information flows* + +#### 3.7.1 *Information flow diagrams* + +Figure 3-3/Q.81 shows the information flow diagrams for the CLIP and the CLIR supplementary services. + +#### 3.7.2 *Definition of individual information flows* + +Within the definitions below, the PI can take one of the following three rules: + +- a) presentation allowed; +- b) presentation restricted; or +- c) number not available. + +Within the definitions below, the SI can take one of the following three rules: + +- a) user provided, verified and passed; +- b) network provided; or +- c) user provided, not screened. + +![Functional model diagram showing five functional entities (FE1 to FE5) and their corresponding control entities (CCA, CC). FE1 is connected to FE2 via interface r_a, FE2 to FE3 via r_b, FE3 to FE4 via r_c, and FE4 to FE5 via r_d. Below the FE line, CCA is connected to CC via r_1, CC to CC via r_2, and CC to CCA via r_3. A label T1126241-91 is present at the bottom right.](fc46871d72c65d3381d9201646d23439_img.jpg) + +Functional model diagram showing five functional entities (FE1 to FE5) and their corresponding control entities (CCA, CC). FE1 is connected to FE2 via interface r\_a, FE2 to FE3 via r\_b, FE3 to FE4 via r\_c, and FE4 to FE5 via r\_d. Below the FE line, CCA is connected to CC via r\_1, CC to CC via r\_2, and CC to CCA via r\_3. A label T1126241-91 is present at the bottom right. + +FIGURE 3-2/Q.81 +**Example of a mapping of the functional model + on a model for the basic call** + +![Information flows diagram showing the sequence of messages between FE1 and FE5. FE1 sends SETUP (910, 911, 915, 916, 917, 918) and INFORM 1 (req. ind.) to FE2. FE2 sends SETUP (920, 921, 922, 923, 924, 925, 926, 927) and INFORM 2 (req. ind.) to FE3. FE3 sends SETUP (930, 931, 932, 933, 934) and INFORM 3 (req. ind.) to FE4. FE4 sends SETUP (940, 941, 942, 943, 944) and INFORM 4 (req. ind.) to FE5. FE5 sends INFORM 4 (ind.) out. A label T1126250-90 is present at the bottom right.](a738993919a50143787084ee7ce6e2f2_img.jpg) + +Information flows diagram showing the sequence of messages between FE1 and FE5. FE1 sends SETUP (910, 911, 915, 916, 917, 918) and INFORM 1 (req. ind.) to FE2. FE2 sends SETUP (920, 921, 922, 923, 924, 925, 926, 927) and INFORM 2 (req. ind.) to FE3. FE3 sends SETUP (930, 931, 932, 933, 934) and INFORM 3 (req. ind.) to FE4. FE4 sends SETUP (940, 941, 942, 943, 944) and INFORM 4 (req. ind.) to FE5. FE5 sends INFORM 4 (ind.) out. A label T1126250-90 is present at the bottom right. + +FIGURE 3-3/Q.81 +**Information flows** + +##### 3.7.2.1 Relationship $r_a$ + +###### 3.7.2.1.1 Contents of INFORM 1 + +The contents of the INFORM 1 are shown in Table 3-1/Q.81. + +The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 3-1/Q.81 + +###### **INFORM 1 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|--------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Opt. (Note 1) | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | Partial number
Subscriber number
National number
International number
(Note 2)
(Note 5) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 3) | +| Presentation indicator | Presentation allowed
Presentation restricted | Opt. (Note 4) | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – Included if FE1 provides information. + +*Note 2* – When a special arrangement exists only national or international number is allowed. + +*Note 3* – May be omitted even if number information is provided. + +*Note 4* – This information flow is mandatory only in the case that the CLIR supplementary service temporary mode applies and FE1 wants to override the default PI stored in FE2. + +*Note 5* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +##### 3.7.2.2 Relationship $r_b$ + +###### 3.7.2.2.1 Contents of INFORM 2 + +The contents of the INFORM 2 are shown in Table 3-2/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 3-2/Q.81 + +###### **INFORM 2 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 2) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted | Mand. | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE1 provides the information. + +*Note 2* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +##### 3.7.2.3 Relationship $r_c$ + +###### 3.7.2.3.1 Contents of INFORM 3 + +The contents of the INFORM 3 are shown in Table 3-3/Q.81. The contents for SETUP are as specified for basic call. + +TABLE 3-3/Q.81 + +###### **INFORM 3 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.
(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE1 provides the information. + +*Note 2* – No number information is provided in the case that the CLIR supplementary service applies and no bilateral agreement exists between the networks for the handling of restricted information. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +##### 3.7.2.4 Relationship *rd* + +###### 3.7.2.4.1 Contents of INFORM 4 + +The contents of the INFORM 4 are shown in Table 3-4/Q.81. The contents for SETUP are as specified for basic call. + +TABLE 3-4/Q.81 + +###### **INFORM 4 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.
(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE1 provides the information. + +*Note 2* – No number information is provided in the case that the CLIR supplementary service applies. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +![SDL diagram for functional entities CLIP and CLIR – FE1. The diagram starts with an initial state (oval) leading to a decision diamond 'Special arrangement?'. If 'Yes', it goes to a process box 'Provide a complete national or international ISDN number?'. If 'No', it goes to a process box 'See Note 1'. Both process boxes lead to a decision diamond 'CLIR invoked?'. If 'Yes', it goes to a process box 'Include presentation indicator See Note 4'. If 'No', it goes directly to a transition box 'INFORM 1 req. ind.'. All three process boxes lead to the transition box. The transition box leads to a final state (crossed circle). Reference numbers 915, 910, 911, 916, 917, 918, and 910 FE2 are shown next to various elements. A code T1126261-91 is also present.](007b053fe94a8348f75128a584503fd0_img.jpg) + +``` + +stateDiagram-v2 + [*] --> SpecialArrangement{Special arrangement?} + SpecialArrangement --> Note1[See Note 1] + SpecialArrangement --> ISDN[Provide a complete national or international ISDN number?] + Note1 --> CLIRInvoked{CLIR invoked?} + ISDN --> Note23[See Note 2 See Note 3] + Note23 --> CLIRInvoked + CLIRInvoked --> Indicator[Include presentation indicator See Note 4] + CLIRInvoked --> Inform1[INFORM 1 req. ind.] + Indicator --> Inform1 + Inform1 --> [*] + +``` + +SDL diagram for functional entities CLIP and CLIR – FE1. The diagram starts with an initial state (oval) leading to a decision diamond 'Special arrangement?'. If 'Yes', it goes to a process box 'Provide a complete national or international ISDN number?'. If 'No', it goes to a process box 'See Note 1'. Both process boxes lead to a decision diamond 'CLIR invoked?'. If 'Yes', it goes to a process box 'Include presentation indicator See Note 4'. If 'No', it goes directly to a transition box 'INFORM 1 req. ind.'. All three process boxes lead to the transition box. The transition box leads to a final state (crossed circle). Reference numbers 915, 910, 911, 916, 917, 918, and 910 FE2 are shown next to various elements. A code T1126261-91 is also present. + +*Note 1* – Provide a -partial, or -subscriber, or -national, or -international number according to originating user's request. + +*Note 2* – Set type of numbers – national or international number and set numbering plan identification – ISDN number or Private Numbering Plan. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +*Note 4* – This information is applicable to CLIR temporary mode. + +FIGURE 3-4/Q.81 +**CLIP and CLIR – FE1** + +![Flowchart showing the sequence of call hooks for FE1. It starts with a circle labeled CLI1 connected to a 'Note' box by a dashed line. An arrow points down from CLI1 to a rectangle labeled CLIP/CLIR1. Another arrow points down from CLIP/CLIR1 to a circle labeled CLI2, which is also connected to a 'Note' box by a dashed line. The text 'T1129460-91' is next to CLI2.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +graph TD + Note1[Note] -.-> CLI1((CLI1)) + CLI1 --> CLIP[CLIP/CLIR1] + CLIP --> CLI2((CLI2)) + Note2[Note] -.-> CLI2 + T1129460-91[T1129460-91] + +``` + +Flowchart showing the sequence of call hooks for FE1. It starts with a circle labeled CLI1 connected to a 'Note' box by a dashed line. An arrow points down from CLI1 to a rectangle labeled CLIP/CLIR1. Another arrow points down from CLIP/CLIR1 to a circle labeled CLI2, which is also connected to a 'Note' box by a dashed line. The text 'T1129460-91' is next to CLI2. + +*Note* – CLI1 and CLI2 break the basic call transition: + +- during FEA211 (see Figure 2-13 (sheet 1 of 5) of Recommendation Q.71 [5]), immediately following the task “Process service request connect”. +CLI2 reconnects at the same point; +- after sending SETUP req. ind. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]). +CLI2 reconnects at the same point; or +- during FEA221 (see Figure 2-14 (sheet 1 of 7) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. +CLI2 reconnects at the same point. + +FIGURE 3-5/Q.81 +**Basic call hooks for FE1** + +![Flowchart for CLIP and CLIR - FE2. The process starts with INFORM 1 req. ind. (FE1). It then checks if the calling id. is supplied by the user (920). If Yes, it checks for a special arrangement (921). If No, it checks for verification of calling line identity (921). Depending on these checks, it sets the SI to default number, network provided, user provided verified and passed, or user provided not screened. All paths lead to a connector labeled 12 2.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM1[INFORM 1 req. ind.] + INFORM1 --> Q1{Calling id. suppl. by the user?} + Q1 -- Yes --> Q2{Special arrangement?} + Q1 -- No --> Q3{Verification of calling line identity} + Q2 -- Yes --> SETSI3[SET SI = user provided not screened] + Q2 -- No --> Q3 + Q3 -- Not OK --> Q1 + Q3 -- OK --> SETSI2[SET SI = user provided verified and passed] + SETSI2 --> Note[Note] + Note --> Connector((12 2)) + SETSI3 --> Connector + SETSI1[SET SI = default number] --> SETSI4[SET SI = network provided] + SETSI4 --> Connector + +``` + +Flowchart details: The process begins with an oval connector leading to a parallelogram labeled 'INFORM 1 req. ind.' with a dashed line from 'FE1'. This leads to a decision diamond 'Calling id. suppl. by the user?' with a dashed line from '920'. If 'Yes', it goes to 'Special arrangement?' (dashed line from '921'). If 'No', it goes to 'Verification of calling line identity' (dashed line from '921'). From 'Special arrangement?', 'Yes' leads to 'SET SI = user provided not screened' (dashed line from '924') and 'No' leads to 'Verification...'. From 'Verification...', 'Not OK' loops back to 'Calling id. suppl...' and 'OK' leads to 'SET SI = user provided verified and passed' (dashed line from '924'). This leads to 'Note' (dashed lines from '922', '925', '926'). 'SET SI = user provided not screened' also leads to the final connector. 'SET SI = default number' (dashed line from '920') leads to 'SET SI = network provided' (dashed line from '920'), which then leads to the final connector. All paths converge to a circular connector labeled '12 2'. The text 'T1126271-91' is at the bottom right. + +Flowchart for CLIP and CLIR - FE2. The process starts with INFORM 1 req. ind. (FE1). It then checks if the calling id. is supplied by the user (920). If Yes, it checks for a special arrangement (921). If No, it checks for verification of calling line identity (921). Depending on these checks, it sets the SI to default number, network provided, user provided verified and passed, or user provided not screened. All paths lead to a connector labeled 12 2. + +*Note* – Complete partial number or subscriber number to a national number. Put the number into the format used in the current ISDN. Set type of number and numbering plan identifier. + +FIGURE 3-6/Q.81 (sheet 1 of 2) + +#### **CLIP and CLIR – FE2** + +![Flowchart for CLIP and CLIR - FE2. It starts with a circle containing '12' and '1'. A dashed line labeled '923' leads to a 'Subscriber restrict option' triangle. From this triangle, three paths emerge: 'Not subscribed' (left), 'Permanent (active for all calls)' (right), and 'Temporary (specified by user per call)' (right, separated by a dashed line). The 'Permanent' and 'Temporary' paths lead to an 'Entered value?' diamond. From this diamond, 'Allowed' leads left and 'Restricted' leads right. The 'None' path from the 'Subscriber restrict option' triangle leads to a 'Default value?' diamond, also with 'Allowed' (left) and 'Restricted' (right) paths. All 'Allowed' paths lead to a 'SET PI = presentation allowed' box. All 'Restricted' paths lead to a 'SET PI = presentation restricted' box. Both boxes have a dashed line labeled '923' next to them. Both boxes lead to an 'INFORM 2 req. ind.' pentagon, which has a dashed line labeled '923 FE3' next to it. The flowchart ends with a crossed-out arrow pointing down. The text 'T1126281-91' is in the bottom right corner.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +graph TD + Start((12 1)) -- "923" --> SRO{Subscriber restrict option} + SRO -- "Not subscribed" --> SV{Entered value?} + SRO -- "923" --> SV + SRO -- "Permanent (active for all calls)" --> SV + SRO -.-> "Temporary (specified by user per call)" -.-> SV + SV -- "Allowed" --> SPA[SET PI = presentation allowed] + SV -- "Restricted" --> SPR[SET PI = presentation restricted] + SRO -- "None" --> DV{Default value?} + DV -- "Allowed" --> SPA + DV -- "Restricted" --> SPR + SPA -- "923" --> I2{INFORM 2 req. ind.} + SPR -- "923" --> I2 + I2 -- "923 FE3" --> End((X)) + +``` + +Flowchart for CLIP and CLIR - FE2. It starts with a circle containing '12' and '1'. A dashed line labeled '923' leads to a 'Subscriber restrict option' triangle. From this triangle, three paths emerge: 'Not subscribed' (left), 'Permanent (active for all calls)' (right), and 'Temporary (specified by user per call)' (right, separated by a dashed line). The 'Permanent' and 'Temporary' paths lead to an 'Entered value?' diamond. From this diamond, 'Allowed' leads left and 'Restricted' leads right. The 'None' path from the 'Subscriber restrict option' triangle leads to a 'Default value?' diamond, also with 'Allowed' (left) and 'Restricted' (right) paths. All 'Allowed' paths lead to a 'SET PI = presentation allowed' box. All 'Restricted' paths lead to a 'SET PI = presentation restricted' box. Both boxes have a dashed line labeled '923' next to them. Both boxes lead to an 'INFORM 2 req. ind.' pentagon, which has a dashed line labeled '923 FE3' next to it. The flowchart ends with a crossed-out arrow pointing down. The text 'T1126281-91' is in the bottom right corner. + +FIGURE 3-6/Q.81 (sheet 2 of 2) +**CLIP and CLIR – FE2** + +![Flowchart showing the sequence of call hooks for FE2. It starts with a circle labeled 'CLI3' connected to a 'Note' box by a dashed line. An arrow points down from 'CLI3' to a rectangle labeled 'CLIP/CLIR2'. Another arrow points down from 'CLIP/CLIR2' to a circle labeled 'CLI4', which is also connected to a 'Note' box by a dashed line. The text 'T1129470-91' is next to the 'CLI4' circle.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph TD + Note1[Note] -.-> CLI3((CLI3)) + CLI3 --> CLIP[CLIP/CLIR2] + CLIP --> CLI4((CLI4)) + Note2[Note] -.-> CLI4 + T1129470-91[T1129470-91] + +``` + +Flowchart showing the sequence of call hooks for FE2. It starts with a circle labeled 'CLI3' connected to a 'Note' box by a dashed line. An arrow points down from 'CLI3' to a rectangle labeled 'CLIP/CLIR2'. Another arrow points down from 'CLIP/CLIR2' to a circle labeled 'CLI4', which is also connected to a 'Note' box by a dashed line. The text 'T1129470-91' is next to the 'CLI4' circle. + +*Note* – CLI3 and CLI4 break the basic call transition: + +- after sending SETUP req. ind. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]). +CLI4 reconnects at the same point; or +- during FEA221 (see Figure 2-14 (sheet 1 of 7) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. +CLI4 reconnects at the same point. + +FIGURE 3-7/Q.81 +**Basic call hooks for FE2** + +![Flowchart for CLIP and CLIR - FE3. The process starts with 'INFORM 2 req. ind.' (FE2). A decision 'Calling id. present?' (930 Note 2) follows. If 'No', 'No information sent' (930) is output. If 'Yes', a decision 'Presentation allowed?' (931) is made. If 'No', 'Spec. agreement on presentation?' (931 Note 1) is checked. If 'Yes', 'CLI = ISDN number?' is checked. If 'No', 'International number?' (932) is checked. If 'Yes', 'Convert national number to international number' (932) is done. Finally, 'Keep PI and SI, as provided by FE2' is output, followed by 'INFORM 3 req. ind.' (934 FE4).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM2[INFORM 2 req. ind.] + INFORM2 --> CallingIdPresent{Calling id. present?} + CallingIdPresent -- No --> NoInfo[No information sent] + CallingIdPresent -- Yes --> PresentationAllowed{Presentation allowed?} + PresentationAllowed -- No --> SpecAgreement{Spec. agreement on presentation?} + SpecAgreement -- No --> SetPI[SET PI = presentation restricted. Erase calling identity] + SpecAgreement -- Yes --> CLIIsDN{CLI = ISDN number?} + CLIIsDN -- Yes --> InternationalNumber{International number?} + CLIIsDN -- No --> KeepPI[Keep PI and SI, as provided by FE2] + InternationalNumber -- Yes --> KeepPI + InternationalNumber -- No --> ConvertNational[Convert national number to international number] + ConvertNational --> KeepPI + NoInfo --> INFORM3[INFORM 3 req. ind.] + SetPI --> INFORM3 + KeepPI --> INFORM3 + INFORM3 --> End([X]) + +``` + +Note 1 – Based on bilateral agreements. + Note 2 – Calling id. present = “No” when: + – an incomplete number is received, or + – no information is received. + +T1126291-91 + +Flowchart for CLIP and CLIR - FE3. The process starts with 'INFORM 2 req. ind.' (FE2). A decision 'Calling id. present?' (930 Note 2) follows. If 'No', 'No information sent' (930) is output. If 'Yes', a decision 'Presentation allowed?' (931) is made. If 'No', 'Spec. agreement on presentation?' (931 Note 1) is checked. If 'Yes', 'CLI = ISDN number?' is checked. If 'No', 'International number?' (932) is checked. If 'Yes', 'Convert national number to international number' (932) is done. Finally, 'Keep PI and SI, as provided by FE2' is output, followed by 'INFORM 3 req. ind.' (934 FE4). + +FIGURE 3-8/Q.81 +CLIP and CLIR – FE3 + +![Flowchart showing the sequence of call hooks: CLI5 (Note), CLIP/CLIR3, and CLI6 (Note).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` +graph TD; CLI5((CLI5)) -- Note --- CLI5; CLI5 --> CLIP[CLIP/CLIR3]; CLIP --> CLI6((CLI6)); CLI6 -- Note --- CLI6; +``` + +The diagram illustrates a vertical sequence of three components. At the top is a circle labeled 'CLI5', with a dashed line connecting it to a rectangular box labeled 'Note'. An arrow points down from 'CLI5' to a double-bordered rectangle labeled 'CLIP/CLIR3'. Another arrow points down from 'CLIP/CLIR3' to a second circle labeled 'CLI6', which is also connected by a dashed line to a rectangular box labeled 'Note'. To the right of the bottom circle is the text 'T1129480-91'. + +Flowchart showing the sequence of call hooks: CLI5 (Note), CLIP/CLIR3, and CLI6 (Note). + +*Note* – CLI5 and CLI6 break the basic call transition during FEA231 (see Figure 2-15 (sheet 1 of 4) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. CLI6 reconnects at the same point. + +FIGURE 3-9/Q.81 +**Basic call hooks for FE3** + +![Flowchart for CLIP et CLIR - FE4. The process starts with an oval connector, followed by 'INFORM 3 req. ind.' (FE3). A decision diamond 'CLIP Sub. or CLIP general. avail.?' (940) follows. If 'No', it goes to 'Note 1' (940). If 'Yes', it goes to 'Any info. about CLI available?' (941). If 'No', it goes to 'SET PI = number not available' (941). If 'Yes', it goes to 'Any presentation restrictions?' (942). If 'Yes', it goes to 'Note 2' (942). If 'No', it goes to 'Include received PI and SI' (942). Both 'Note 2' and 'Include received PI and SI' lead to 'Convert to format to be presented to user' (943). All three paths ('Note 1', 'Convert to format...', and 'SET PI...') lead to 'INFORM 4 req. ind.' (944 FE5), which ends at a cross symbol.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM3[INFORM 3 req. ind.] + subgraph FE3 + INFORM3 + end + INFORM3 --> D1{CLIP Sub. or CLIP general. avail.?} + D1 -- No --> Note1[Note 1] + D1 -- Yes --> D2{Any info. about CLI available?} + D2 -- No --> SETPI[SET PI = number not available] + D2 -- Yes --> D3{Any presentation restrictions?} + D3 -- Yes --> Override{Override?} + D3 -- No --> IncludePI[Include received PI and SI] + Override -- No --> Note2[Note 2] + Override -- Yes --> IncludePI + Note1 --> Join1(( )) + Note2 --> Join1 + IncludePI --> Convert[Convert to format to be presented to user] + Convert --> Join1 + SETPI --> Join1 + Join1 --> INFORM4[INFORM 4 req. ind.] + subgraph FE5 + INFORM4 + end + INFORM4 --> End((X)) + +``` + +Flowchart for CLIP et CLIR - FE4. The process starts with an oval connector, followed by 'INFORM 3 req. ind.' (FE3). A decision diamond 'CLIP Sub. or CLIP general. avail.?' (940) follows. If 'No', it goes to 'Note 1' (940). If 'Yes', it goes to 'Any info. about CLI available?' (941). If 'No', it goes to 'SET PI = number not available' (941). If 'Yes', it goes to 'Any presentation restrictions?' (942). If 'Yes', it goes to 'Note 2' (942). If 'No', it goes to 'Include received PI and SI' (942). Both 'Note 2' and 'Include received PI and SI' lead to 'Convert to format to be presented to user' (943). All three paths ('Note 1', 'Convert to format...', and 'SET PI...') lead to 'INFORM 4 req. ind.' (944 FE5), which ends at a cross symbol. + +*Note 1* – No information about the calling line identity is sent to the called party. + +*Note 2* – SET PI = presentation restricted. Numbering information will not be presented to the called party. + +T1126301-91 + +FIGURE 3-10/Q.81 + +**CLIP et CLIR – FE4** + +![Flowchart showing a call hook sequence: CL17 (circle) with a 'Note' label, followed by CLIP/CLIR4 (double rectangle), followed by CL18 (circle) with a 'Note' label. A small code T1129490-91 is at the bottom right.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +graph TD + Note1[Note] -.- CL17((CL17)) + CL17 --> CLIPCLIR4[CLIP/CLIR4] + CLIPCLIR4 --> CL18((CL18)) + Note2[Note] -.- CL18 + subgraph " " + style CLIPCLIR4 stroke-width:4px + end + T1129490-91 + +``` + +Flowchart showing a call hook sequence: CL17 (circle) with a 'Note' label, followed by CLIP/CLIR4 (double rectangle), followed by CL18 (circle) with a 'Note' label. A small code T1129490-91 is at the bottom right. + +*Note* – CL17 and CL18 break the basic call transition: + +- during FEA241 (see Figure 2-16 (sheet 1 of 5) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. CL18 reconnects at the same point; or +- during FEA241 (see Figure 2-16 (sheet 1 of 5) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Supplementary services provided”. CL18 reconnects on the “No” branch of the same decision. + +FIGURE 3-11/Q.81 +**Basic call hooks for FE4** + +![Flowchart for FE5 showing steps: INFORM 4 req. ind., Transfer received information into correct format, and INFORM 4 ind. Reference numbers 951, FE4, and 952 are shown. A small code T1126311-91 is at the bottom right.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM4req{INFORM 4 +req. ind.} + INFORM4req --> Transfer[Transfer received +information +into correct format] + Transfer --> INFORM4ind{INFORM 4 +ind.} + INFORM4ind --> End((X)) + + 951_FE4[951 +FE4] -.- INFORM4req + 951[951] -.- Transfer + 952[952] -.- INFORM4ind + + T1126311-91 + +``` + +Flowchart for FE5 showing steps: INFORM 4 req. ind., Transfer received information into correct format, and INFORM 4 ind. Reference numbers 951, FE4, and 952 are shown. A small code T1126311-91 is at the bottom right. + +FIGURE 3-12/Q.81 +**CLIP and CLIR – FE5** + +![Flowchart showing the sequence of call hooks for FE5. It starts with a circle labeled 'CLI9' connected to a 'Note' box, followed by a rectangle labeled 'CLIP/CLIR5', and finally a circle labeled 'CLI10' connected to another 'Note' box. The diagram is labeled T1129500-91.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +graph TD + Note1[Note] -.-> CLI9((CLI9)) + CLI9 --> CLIP[CLIP/CLIR5] + CLIP --> CLI10((CLI10)) + Note2[Note] -.-> CLI10 + T1129500-91[T1129500-91] + +``` + +Flowchart showing the sequence of call hooks for FE5. It starts with a circle labeled 'CLI9' connected to a 'Note' box, followed by a rectangle labeled 'CLIP/CLIR5', and finally a circle labeled 'CLI10' connected to another 'Note' box. The diagram is labeled T1129500-91. + +*Note* – CLI9 and CLI10 break the basic call transition: + +- during FEA251 (see Figure 2-17 (sheet 1 of 4) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. CLI8 reconnects at the same point; +- during FEA251 (see Figure 2-17 (sheet 1 of 4) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Supplementary services provided”. CLI8 reconnects on the “No” branch of the same decision. + +FIGURE 3-13/Q.81 +**Basic call hooks for FE5** + +### 3.9 *Functional entity actions (FEAs)* + +#### 3.9.1 *FEAs for FE1* + +- 910: FE1 shall receive and shall forward originating users service requests to FE2; +- 911: FE1 shall request the CLIR supplementary service temporary mode (override of network stored value of presentation indicator); +- 915: in the case of a special arrangement, FE1 shall screen the number to be provided; +- 916: in the case of a special arrangement, FE1 shall complete the number to national or international format (for ISDN-numbers); +- 917: FE1 shall set the type of number; +- 918: FE1 shall set the numbering plan identification. + +#### 3.9.2 *FEAs of FE2* + +- 920: FE2 shall check if calling line identity is provided by FE1 and if not, shall include the default calling line identity with presentation indicator set to "network provided"; +- 921: FE2 shall verify calling line identity (unless a special arrangement for not screening the number exists); +- 922: FE2 shall complete a partial number or a subscriber number to a national number. FE2 shall put the number into the format used in the current ISDN; +- 923: FE2 shall set the presentation indicator; +- 924: FE2 shall set the screening indicator; +- 925: FE2 shall set the type of number (when a special arrangement exists, FE1 shall also set the type of number); +- 926: FE2 shall set the numbering plan identification (when a special arrangement exists, FE1 shall also set the numbering plan identification); +- 927: FE2 shall forward the information to FE3. + +#### 3.9.3 *FEAs of FE3* + +In the case of a national call, FE3 has null functionality. + +- 930: FE3 shall check if a partial number, or no information, is received. In this case no information is sent to FE4; +- 931: FE3 shall check if the calling line identity may be passed between the networks; +- 932: FE3 shall convert national ISDN-number to an international significant ISDN number if not already in this form. Number belonging to other numbering plans shall be passed transparently; +- 933: if a number cannot be passed to FE4, FE3 shall erase the number and sub-address information and shall set the presentation indicator to "number not available"; +- 934: FE3 shall forward the information to FE4. + +#### 3.9.4 *FEAs for FE4* + +- 940: FE4 shall check if the CLIP supplementary service is subscribed; +- 941: FE4 shall check if calling line identity is provided. If the number is not available, then FE4 shall set the presentation indicator to "number not available"; + +- 942: FE4 shall check if presentation restrictions exist. If presentation restrictions exist, the number and sub-address information shall be erased, no number information shall be sent to the calling party and the received presentation indicator (PI) showing "presentation restricted" shall be sent to FE5 unless FE5 has the override category. If FE5 has such a category, then all the received information shall be sent to FE5; +- 943: FE4 shall transfer the received information into a format that makes it usable by FE5 (e.g. adding prefixes); +- 944: FE4 shall forward the information to FE5. + +#### 3.9.5 *FEAs for FE5* + +- 950: FE5 shall receive the service information from FE4; +- 951: FE5 shall transfer the received information into a format that makes it usable for returning a call; +- 952: FE5 shall present the received information to the served user. + +### 3.10 *Allocation of functional entities to physical locations* + +The possible locations of functional entities FE1, FE2, FE3, FE4 and FE5 are shown in Table 3-5/Q.81. + +TABLE 3-5/Q.81 + +#### Locations of functional entities + +| Scenarios | FE1 | FE2 | FE3 | FE4 | FE5 | +|-----------|-----|-----|--------|-----|-----| +| 1 | TE | LE | – | LE | TE | +| 2 | TE | LE | INT TR | LE | TE | +| 3 | PNX | LE | – | LE | TE | +| 4 | PNX | LE | INT TR | LE | PNX | +| 5 | PNX | LE | – | LE | TE | +| 6 | PNX | LE | INT TR | LE | TE | +| 7 | TE | LE | – | LE | PNX | +| 8 | TE | LE | INT TR | LE | PNX | + +## ANNEX A (to § 3 of Recommendation Q.81) + +#### **Two calling-line-identities delivery option** + +#### A.1 *Scope* + +This annex specifies the additional procedures of the CLIP supplementary service that may be supported as a national network option. + +These national procedures shall have no impact and shall place no requirements whatsoever on the provision and operation of the CLIP supplementary service defined in this Recommendation by public ISDNs that do not support these additional procedures, nor on the interchangeability of terminals. + +#### A.2 *Additional procedures of FE4* + +If the procedures for delivery of the calling line identity as described in § 3.8 (SDL diagram for FE4) apply and the screening indicator is set to “user provided not screened”, then the FE4 shall send the second calling line identity immediately following the first calling line identity. The second calling line identity shall be the default calling line identity of the access of the calling party. The second calling line identity shall be provided according to procedures described in this Recommendation. + +In all other cases, only the first calling line identity shall be sent. + +## 5 Connected Line Identification, presentation and restriction (COLP and COLR) + +### 5.1 Scope + +This Recommendation defines the stage 2 of the integrated services digital network (ISDN) as provided by public telecommunications operators for the Connected Line Identification Presentation (COLP) and Connected Line Identification Restriction (COLR) supplementary services. Stage 2 identifies the functional capabilities and the information flows needed to support the service description. The stage 2 description also identifies user operations not directly associated with a call (see Recommendation I.130 [1]). + +This Recommendation is defined according to the methodology specified in Recommendation Q.65 [2]. + +This Recommendation does not formally describe the relation between these supplementary services and the basic call but, where possible, this information is included for guidance. + +In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities within a private ISDN; it does however define which functional entities may be allocated to a private ISDN. + +This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. + +The COLP supplementary service provides the calling party with the possibility to receive identification of the connected party. + +The COLR supplementary service enables the connected party to prevent presentation of its ISDN number to the calling party. + +The COLP and COLR supplementary services are applicable to all telecommunication services. + +This Recommendation is applicable to the stage 3 standards for the ISDN COLP and COLR supplementary services. The term "stage 3" is defined in Recommendation I.130 [1]. + +### 5.2 References + +These references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to, or revisions of any of these publications apply to this Recommendation only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. + +- [1] CCITT Rec. I.130 [1988] – Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. +- [2] CCITT Rec. Q.65 – Stage 2 of the method for the characterization of services supported by an ISDN. +- [3] CCITT Rec. I.251.5 – Connected Line Identification Presentation (COLP). +- [4] CCITT Rec. I.251.6 – Connected Line Identification Restriction (COLR). + +- [5] CCITT Rec. Q.71 – ISDN 64 kbit/s circuit mode switched beared services. +- [6] CCITT Rec. I.112 – Vocabulary of terms for ISDNs. +- [7] CCITT Rec. I.210 – Principles of telecommunication services supported by an ISDN and the means to describe them. +- [8] CCITT Rec. E.164 – Numbering plan for the ISDN era. +- [9] CCITT Rec. I.330 – ISDN numbering and addressing principles. +- [10] CCITT Rec. Q.86, Section 4 – Integrated Services Digital Network (ISDN); Freephone (FPH) supplementary service; Functional capabilities and information flows. + +### 5.3 *Definitions* + +For the purpose of this Recommendation, the following definitions apply: + +#### **integrated services digital network (ISDN)** + +See definition 308 of § 2.3 of Recommendation I.112 [6]. + +#### **service, telecommunications service** + +See definition 201 of § 2.2 of Recommendation I.112 [6]. + +#### **supplementary service** + +See § 2.4 of Recommendation I.210 [7]. + +#### **ISDN number** + +A number conforming to the numbering plan and structure specified in Recommendation E.164 [8]. + +#### **PNP number** + +A number conforming to the numbering plan and structure in a private network. + +#### **sub-address** + +See § 5.4 of Recommendation I.330 [9]. + +#### **connected line identity** + +The address (the ISDN number, and if supplied the sub-address) of the connected line, and the screening indicator. If these are not available the reason is indicated, via the presentation indicator. + +#### **presentation indicator (PI)** + +The PI presentation indicator provides instructions on whether or not the provided connected line identity is allowed to be presented or not, or indicates that the number is not available. + +#### **screening indicator (SI)** + +The SI provides information on the source and the quality of the provided information. + +### 5.4 *Symbols and abbreviations* + +| | | +|--------|--------------------------------------------| +| COLP | Connected Line Identification Presentation | +| COLR | Connected Line Identification Restriction | +| PI | Presentation indicator | +| SI | Screening indicator | +| ISDN | Integrated services digital network | +| TE | Terminal equipment | +| PNX | Private network exchange | +| LE | Local exchange | +| INT TR | International transit exchange | +| FEA | Functional entity action | +| SDL | Specification and description language | +| PNP | Private Numbering Plan | + +### 5.5 *Description* + +The relationship between the COLP and the COLR supplementary services is described in § 5.3.4.2 of Recommendation I.251.5 [3], and in Recommendation I.251.6 [4]. + +The provisions for overriding the COLR supplementary service are described in § 5.3.4.2 of Recommendations I.251.5 [3], and in Recommendation I.251.6 [4]. + +### 5.6 *Derivation of a functional model* + +#### 5.6.1 *Functional model description* + +The model for the COLP and COLR supplementary services is shown in Figure 5-1/Q.81. + +![Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. The connections are labeled r_a, r_b, r_c, and r_d. A small text 'T1126320-90' is located below FE5.](356eb99ab9489bbd647223390a913903_img.jpg) + +``` +graph LR; FE1[FE1] --- r_a --- FE2[FE2]; FE2 --- r_b --- FE3[FE3]; FE3 --- r_c --- FE4[FE4]; FE4 --- r_d --- FE5[FE5]; +``` + +T1126320-90 + +Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. The connections are labeled r\_a, r\_b, r\_c, and r\_d. A small text 'T1126320-90' is located below FE5. + +FIGURE 5-1/Q.81 + +**Functional model** + +#### 5.6.2 Description of the functional entities + +The functional entities required by the COLP and COLR supplementary services above those of the basic call are as follows: + +- FE1: service requesting entity +- FE2: service providing entity +- FE3: handling of connected line identity at international gateway +- FE4: service information checking entity +- FE5: connected party provided information and COLR requesting entity. + +#### 5.6.3 Relationship with a basic service + +The relationship with a basic service is shown in Figure 5-2/Q.81. The model for basic call handling is defined in Recommendation Q.71. + +![Figure 5-2/Q.81: Example of a mapping of the functional model on a model for the basic call. The diagram shows a sequence of five functional entities (FE1 to FE5) and their corresponding call control (CC) or call connection (CCA) components. FE1 is connected to FE2 via interface r_a (top) and r_1 (bottom). FE2 is connected to FE3 via interface r_b (top) and r_2 (bottom). FE3 is connected to FE4 via interface r_c (top) and r_2 (bottom). FE4 is connected to FE5 via interface r_d (top) and r_3 (bottom). The bottom row consists of CCA, CC, CC, CC, and CCA blocks. A small code 'T1126330-90' is visible at the bottom right of the diagram.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Figure 5-2/Q.81: Example of a mapping of the functional model on a model for the basic call. The diagram shows a sequence of five functional entities (FE1 to FE5) and their corresponding call control (CC) or call connection (CCA) components. FE1 is connected to FE2 via interface r\_a (top) and r\_1 (bottom). FE2 is connected to FE3 via interface r\_b (top) and r\_2 (bottom). FE3 is connected to FE4 via interface r\_c (top) and r\_2 (bottom). FE4 is connected to FE5 via interface r\_d (top) and r\_3 (bottom). The bottom row consists of CCA, CC, CC, CC, and CCA blocks. A small code 'T1126330-90' is visible at the bottom right of the diagram. + +FIGURE 5-2/Q.81 + +Example of a mapping of the functional model on a model +for the basic call + +### 5.7 Information flows + +#### 5.7.1 Information flow diagrams + +Figure 5-3/Q.81 shows the information flow diagrams for the COLP and COLR supplementary services. + +![Sequence diagram showing information flow between FE1 and FE5. FE1 sends INFORM 4 ind. to FE2. FE2 sends SETUP resp. conf. (920-922) and INFORM 4 req. ind. (923-924) to FE1. FE2 also sends SETUP resp. conf. (930-931) and INFORM 3 req. ind. (932-933) to FE3. FE3 sends INFORM 2 req. ind. to FE4. FE4 sends SETUP resp. conf. (940-947) to FE3. FE4 also sends INFORM 1 req. ind. (957-958) to FE5. FE5 sends SETUP resp. conf. (950-956) to FE4. FE1 also has messages 910, 911, 912.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +The diagram illustrates the information flow between five functional entities (FE1 to FE5) over time, indicated by vertical lifelines. Horizontal arrows represent messages, with some grouped by brackets and associated with specific message numbers. + +- FE1 to FE2:** INFORM 4 ind. (message 224). +- FE2 to FE1:** + - SETUP resp. conf. (messages 920, 921, 922). + - INFORM 4 req. ind. (messages 923, 924). +- FE2 to FE3:** + - SETUP resp. conf. (messages 930, 931). + - INFORM 3 req. ind. (messages 932, 933). +- FE3 to FE4:** INFORM 2 req. ind. (message 245). +- FE4 to FE3:** SETUP resp. conf. (messages 940, 941, 942, 943, 944, 945, 946, 947). +- FE4 to FE5:** INFORM 1 req. ind. (messages 957, 958). +- FE5 to FE4:** SETUP resp. conf. (messages 950, 951, 955, 956). +- FE1 internal/initial:** Messages 910, 911, 912. + +Sequence markers $r_a$ , $r_b$ , $r_c$ , and $r_d$ are shown above the lifelines between FE1-FE2, FE2-FE3, FE3-FE4, and FE4-FE5 respectively. + +Sequence diagram showing information flow between FE1 and FE5. FE1 sends INFORM 4 ind. to FE2. FE2 sends SETUP resp. conf. (920-922) and INFORM 4 req. ind. (923-924) to FE1. FE2 also sends SETUP resp. conf. (930-931) and INFORM 3 req. ind. (932-933) to FE3. FE3 sends INFORM 2 req. ind. to FE4. FE4 sends SETUP resp. conf. (940-947) to FE3. FE4 also sends INFORM 1 req. ind. (957-958) to FE5. FE5 sends SETUP resp. conf. (950-956) to FE4. FE1 also has messages 910, 911, 912. + +T1126341-90 + +FIGURE 5-3/Q.81 +**Information flow diagrams for COLP and COLR** + +#### 5.7.2 *Definition of individual information flows* + +Within the definitions below, PI can take one of the following three rules: + +- a) presentation allowed; +- b) presentation restricted; or +- c) number not available. + +Within the definitions below, SI can take one of the following three rules: + +- a) user provided, verified and passed; +- b) network provided; or +- c) user provided, not-screened. + +##### 5.7.2.1 *Relationship $r_a$* + +###### 5.7.2.1.1 *Contents of INFORM 4* + +The contents of the INFORM 4 are shown in Table 5-1/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-1/Q.81 + +###### **INFORM 4 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.

(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number, verified and passed.
User provided number, not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE5 provides the information. + +*Note 2* – No number information is provided in the case that the COLR supplementary service applies. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +##### 5.7.2.2 Relationship $r_b$ + +###### 5.7.2.2.1 Contents of INFORM 3 + +The contents of the INFORM 3 are shown in Table 5-2/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-2/Q.81 + +###### **INFORM 3 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.

(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number, verified and passed.
User provided number, not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE5 provides the information. + +*Note 2* – No number information is provided in the case that the COLR supplementary service applies and no bilateral agreement exists between the networks for the handling of restricted information. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +##### 5.7.2.3 *Relationship $r_c$* + +###### 5.7.2.3.1 *Contents of INFORM 2* + +The contents of the INFORM 2 are shown in Table 5-3/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-3/Q.81 + +###### **INFORM 2 contents** + +| Parameter | Allowed value | Req. ind. | +|------------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Mand. | +| – Numbering plan
identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 2) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted | Mand. | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE5 provides the information. + +*Note 2* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +##### 5.7.2.4 Relationship *rd* + +###### 5.7.2.4.1 Contents of INFORM 1 + +The contents of the INFORM 1 are shown in Table 5-4/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-4/Q.81 + +###### **INFORM 1 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|--------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Opt. (Note 1) | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | Partial number
Subscriber number
National number
International number
(Note 2)
(Note 5) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 3) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted | Opt. (Note 4) | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – Included if FE5 provides information. + +*Note 2* – When a special arrangement exists, only the national or international number is allowed. + +*Note 3* – May be omitted even if number information is provided. + +*Note 4* – This information flow is included only in the case that the CLOR supplementary service temporary mode applies and FE5 wants to override the default PI stored in FE4. + +*Note 5* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +![SDL diagram for functional entity FE1 (Figure 5-4/Q.81). The diagram shows a sequence of states and transitions. It starts with an initial state (oval), followed by a transition 'INFORM 4 req. ind.' (trapezoid) with an input 'FE2 910'. This leads to a state 'Transfer received information into correct format' (rectangle) with an output '911'. This is followed by a transition 'INFORM 4 ind.' (trapezoid) with an output '912'. The sequence ends at a final state (crossed circle). The diagram is labeled 'T1126351-91'.](399a5af4f606059626c92c92279d54b7_img.jpg) + +``` + +graph TD + Start([ ]) --> Input[INFORM 4 +req. ind.] + Input --- FE2_910[FE2 +910] + Input --> Task[Transfer received +information into +correct format] + Task --- Ref911[911] + Task --> Output[INFORM 4 +ind.] + Output --- Ref912[912] + Output --> End((X)) + +``` + +SDL diagram for functional entity FE1 (Figure 5-4/Q.81). The diagram shows a sequence of states and transitions. It starts with an initial state (oval), followed by a transition 'INFORM 4 req. ind.' (trapezoid) with an input 'FE2 910'. This leads to a state 'Transfer received information into correct format' (rectangle) with an output '911'. This is followed by a transition 'INFORM 4 ind.' (trapezoid) with an output '912'. The sequence ends at a final state (crossed circle). The diagram is labeled 'T1126351-91'. + +FIGURE 5-4/Q.81 +**COLP and COLR – FE1** + +![SDL diagram showing hooks to the basic call for FE1 (Figure 5-5/Q.81). It shows a vertical sequence: a circle labeled 'COL1' with a dashed line to a 'Note' bracket, a downward arrow to a rectangle labeled 'COLP/COLR1', a downward arrow from the rectangle to a circle labeled 'COL2' with a dashed line to another 'Note' bracket. The diagram is labeled 'T1129520-91'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +graph TD + COL1((COL1)) --- Note1{Note} + COL1 --> Box[COLP/COLR1] + Box --> COL2((COL2)) + COL2 --- Note2{Note} + +``` + +SDL diagram showing hooks to the basic call for FE1 (Figure 5-5/Q.81). It shows a vertical sequence: a circle labeled 'COL1' with a dashed line to a 'Note' bracket, a downward arrow to a rectangle labeled 'COLP/COLR1', a downward arrow from the rectangle to a circle labeled 'COL2' with a dashed line to another 'Note' bracket. The diagram is labeled 'T1129520-91'. + +*Note* – COL1 and COL2 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-13 (sheet 1 of 5) of Recommendation Q.71 [5]), following state “1 CALL SENT” and “2 CONNECTION PROCEEDING”. COL2 reconnects at the same point; +- following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]), following state “1 $r_1$ - $r_2$ CALL SENT” and following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 3 of 7) of Recommendation Q.71 [5]), following state “26 $r_1$ - $r_2$ CALL SENT (alerting)”. COL2 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-9 (sheet 11 of 19) of Recommendation Q.71 [5]), following state “18 $r_2$ - $r_2$ CALL SENT”. COL2 reconnects at the same point. + +FIGURE 5-5/Q.81 +**Hooks to basic call for FE1** + +![Flowchart for COLP and COLR - FE2. The process starts with an oval connector, followed by 'INFORM 3 req. ind.' (FE3). A decision diamond asks 'COLP Sub. or COLP generally available?'. If 'No', it leads to 'Note 1' (920). If 'Yes', it asks 'Any info. about COL. id. available?' (921). If 'No', it leads to 'SET PI = number not available' (921). If 'Yes', it asks 'Any presentation restrictions?' (922). If 'Yes', it leads to 'Override category?' (922). If 'No', it leads to 'Include received PI and SI' (922). From 'Override category?', 'Yes' leads to 'Include received PI and SI' and 'No' leads to 'Note 2' (922). Both 'Note 1' and 'Note 2' lead to 'INFORM 4 req. ind.' (924, FE1). 'Include received PI and SI' leads to 'Convert to format to be presented to user' (923), which then leads to 'INFORM 4 req. ind.'.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM3[INFORM 3 req. ind.] + INFORM3 -.-> FE3[FE3] + INFORM3 --> D1{COLP Sub. or COLP generally available?} + D1 -- No --> Note1[Note 1] + Note1 -.-> 920[920] + D1 -- Yes --> D2{Any info. about COL. id. available?} + D2 -- No --> SETPI[SET PI = number not available] + SETPI -.-> 921[921] + D2 -- Yes --> D3{Any presentation restrictions?} + D3 -- Yes --> D4{Override category?} + D3 -- No --> IncludePI[Include received PI and SI] + D4 -- Yes --> IncludePI + D4 -- No --> Note2[Note 2] + Note2 -.-> 922[922] + IncludePI -.-> 922[922] + IncludePI --> Convert[Convert to format to be presented to user] + Convert -.-> 923[923] + Convert --> INFORM4[INFORM 4 req. ind.] + Note1 --> INFORM4 + Note2 --> INFORM4 + SETPI --> INFORM4 + INFORM4 -.-> 924[924] + INFORM4 -.-> FE1[FE1] + INFORM4 --> End(( )) + +``` + +Flowchart for COLP and COLR - FE2. The process starts with an oval connector, followed by 'INFORM 3 req. ind.' (FE3). A decision diamond asks 'COLP Sub. or COLP generally available?'. If 'No', it leads to 'Note 1' (920). If 'Yes', it asks 'Any info. about COL. id. available?' (921). If 'No', it leads to 'SET PI = number not available' (921). If 'Yes', it asks 'Any presentation restrictions?' (922). If 'Yes', it leads to 'Override category?' (922). If 'No', it leads to 'Include received PI and SI' (922). From 'Override category?', 'Yes' leads to 'Include received PI and SI' and 'No' leads to 'Note 2' (922). Both 'Note 1' and 'Note 2' lead to 'INFORM 4 req. ind.' (924, FE1). 'Include received PI and SI' leads to 'Convert to format to be presented to user' (923), which then leads to 'INFORM 4 req. ind.'. + +T1126361-91 + +Note 1 – No information about the COL identity is sent to the calling party. + +Note 2 – SET PI – presentation restricted. Erase number information. No number information shall be presented to the calling party. + +FIGURE 5-6/Q.81 +COLP and COLR – FE2 + +![A flow diagram showing a sequence of states. At the top is a circle labeled 'COL3' with a dashed line to a 'Note' box. An arrow points down to a rectangle labeled 'COLP/COLR2'. Another arrow points down from this rectangle to a circle labeled 'COL4', which also has a dashed line to a 'Note' box.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +``` + +graph TD + COL3((COL3)) -.- Note1[Note] + COL3 --> COLP_COLR2[COLP/COLR2] + COLP_COLR2 --> COL4((COL4)) + COL4 -.- Note2[Note] + +``` + +T1129530-91 + +A flow diagram showing a sequence of states. At the top is a circle labeled 'COL3' with a dashed line to a 'Note' box. An arrow points down to a rectangle labeled 'COLP/COLR2'. Another arrow points down from this rectangle to a circle labeled 'COL4', which also has a dashed line to a 'Note' box. + +*Note* – COL3 and COL4 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]), following state “1 r1-r2 CALL SENT” and following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 3 of 7) of Recommendation Q.71 [5]), following state “26 r1-r2 CALL SENT (alerting)”. COL4 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “18 r2-r2 CALL SENT”. COL4 reconnects at the same point. + +FIGURE 5-7/Q.81 +**Hooks to basic call for FE2** + +![Flowchart for COLP and COLR - FE3. The process starts with INFORM 2 req. ind. (FE4). It then checks if COL. id. is present. If Yes, it goes to connector 931. If No, it checks if presentation is allowed. If Presentation allowed is No, it checks for a special agreement. If Spec. agreement on presentation is Yes, it goes to connector 931. If No, it sets PI = presentation restricted and erases number information (933). If Presentation allowed is Yes, it checks if COL. id. = ISDN number. If Yes, it checks if it's an international number. If No, it converts the national number to an international number (932). Both Yes and No paths lead to connector 931. If COL. id. = ISDN number is No, it leads to connector 931. All paths lead to INFORM 3 req. ind. (934 FE2).](f57c7b37d7a05a99618104f390089f03_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM2[INFORM 2 req. ind. FE4] + INFORM2 --> COLidPresent{COL. id. present?} + COLidPresent -- Yes --> 931((931)) + COLidPresent -- No --> NoInfo[No information sent 930] + NoInfo --> INFORM3[INFORM 3 req. ind. 934 FE2] + COLidPresent -- No --> PresAllowed{Presentation allowed?} + PresAllowed -- No --> SpecAgree{Spec. agreement on presentation? 931 Note 1} + SpecAgree -- Yes --> 931 + SpecAgree -- No --> SetPI[SET PI = presentation restricted. Erase the number information 933] + PresAllowed -- Yes --> COLidISDN{COL. id. = ISDN number?} + COLidISDN -- Yes --> IntNum{International number? 932} + IntNum -- Yes --> 931 + IntNum -- No --> ConvertNum[Convert national number to international number 932] + ConvertNum --> 931 + COLidISDN -- No --> 931 + SetPI --> INFORM3 + 931 --> INFORM3 + +``` + +Flowchart for COLP and COLR - FE3. The process starts with INFORM 2 req. ind. (FE4). It then checks if COL. id. is present. If Yes, it goes to connector 931. If No, it checks if presentation is allowed. If Presentation allowed is No, it checks for a special agreement. If Spec. agreement on presentation is Yes, it goes to connector 931. If No, it sets PI = presentation restricted and erases number information (933). If Presentation allowed is Yes, it checks if COL. id. = ISDN number. If Yes, it checks if it's an international number. If No, it converts the national number to an international number (932). Both Yes and No paths lead to connector 931. If COL. id. = ISDN number is No, it leads to connector 931. All paths lead to INFORM 3 req. ind. (934 FE2). + +Note 1 – Based on bilateral agreements. + Note 2 – COL. id. present = “No” when: + – an incomplete number is received, or + – no information is received. + +FIGURE 5-8/Q.81 +**COLP and COLR – FE3** + +![Diagram showing hooks to a basic call for FE3. It consists of a circle labeled COL5 at the top, a rectangle with double horizontal lines labeled COLP/COLR3 in the middle, and a circle labeled COL6 at the bottom. Arrows point from COL5 to the rectangle and from the rectangle to COL6. To the right of each circle is a bracket labeled 'Note'.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +``` + +graph TD + COL5((COL5)) --> COLP_COLR3[COLP/COLR3] + COLP_COLR3 --> COL6((COL6)) + subgraph Note1 [ ] + direction TB + N1[Note] + end + subgraph Note2 [ ] + direction TB + N2[Note] + end + COL5 -.- Note1 + COL6 -.- Note2 + +``` + +T1129540-91 + +Diagram showing hooks to a basic call for FE3. It consists of a circle labeled COL5 at the top, a rectangle with double horizontal lines labeled COLP/COLR3 in the middle, and a circle labeled COL6 at the bottom. Arrows point from COL5 to the rectangle and from the rectangle to COL6. To the right of each circle is a bracket labeled 'Note'. + +*Note* – COL5 and COL6 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “ $18\ r_2 - r_2\ \text{CALL SENT}$ ”, COL6 reconnects at the same point. + +FIGURE 5-9/Q.81 +**Hooks to basic call for FE3** + +![Flowchart for COLP and COLR - FE4. It starts with an oval connector, followed by 'INFORM 1 req. ind.' (FE5). A decision diamond 'Conn. id. suppl. by the user?' (940) has 'Yes' and 'No' paths. The 'Yes' path leads to 'Special arrangement?' (941). The 'No' path from 'Conn. id. suppl. by the user?' leads to 'Connected number = default number' (940). The 'Yes' path from 'Special arrangement?' leads to 'SET SI = user provided not screened' (944). The 'No' path from 'Special arrangement?' leads to 'Verification of connected line identity?' (941). From 'Verification of connected line identity?', 'not OK' leads back to 'Connected number = default number' and 'OK' leads to 'SET SI = user provided verified and passed' (944). Both 'SET SI = user provided verified and passed' and 'SET SI = user provided not screened' lead to a 'Note' block (942, 945, 946). All three paths ('Connected number = default number', 'SET SI = network provided' (940), and 'Note') lead to a final connector circle '12'.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM1[INFORM 1 req. ind.] + INFORM1 -.-> FE5[FE5] + INFORM1 --> ConnId{Conn. id. suppl. by the user?} + ConnId -.-> 940_1[940] + ConnId -- Yes --> SpecialArr{Special arrangement?} + ConnId -- No --> DefaultNum[Connected number = default number] + DefaultNum -.-> 940_2[940] + SpecialArr -.-> 941_1[941] + SpecialArr -- Yes --> NotScreened[SET SI = user provided not screened] + SpecialArr -- No --> VerifId{Verification of connected line identity?} + VerifId -.-> 941_2[941] + VerifId -- not OK --> DefaultNum + VerifId -- OK --> Verified[SET SI = user provided verified and passed] + Verified -.-> 944_1[944] + NotScreened -.-> 944_2[944] + Verified --> Note[Note] + Note -.-> 942[942] + Note -.-> 945[945] + Note -.-> 946[946] + NotScreened --> Note + DefaultNum --> NetworkProvided[SET SI = network provided] + NetworkProvided -.-> 940_3[940] + NetworkProvided --> End((12)) + Note --> End + NotScreened --> End + +``` + +Flowchart for COLP and COLR - FE4. It starts with an oval connector, followed by 'INFORM 1 req. ind.' (FE5). A decision diamond 'Conn. id. suppl. by the user?' (940) has 'Yes' and 'No' paths. The 'Yes' path leads to 'Special arrangement?' (941). The 'No' path from 'Conn. id. suppl. by the user?' leads to 'Connected number = default number' (940). The 'Yes' path from 'Special arrangement?' leads to 'SET SI = user provided not screened' (944). The 'No' path from 'Special arrangement?' leads to 'Verification of connected line identity?' (941). From 'Verification of connected line identity?', 'not OK' leads back to 'Connected number = default number' and 'OK' leads to 'SET SI = user provided verified and passed' (944). Both 'SET SI = user provided verified and passed' and 'SET SI = user provided not screened' lead to a 'Note' block (942, 945, 946). All three paths ('Connected number = default number', 'SET SI = network provided' (940), and 'Note') lead to a final connector circle '12'. + +T1126381-91 + +*Note* – Complete partial number or subscriber number to a national number. Put the number into the format used in the current ISDN. Set type of number and numbering plan identification. + +FIGURE 5-10/Q.81 +**COLP and COLR – FE4** + +![Flowchart for COLP and COLR - FE4. It starts at node 12, leading to 'Subscriber restricted option'. From there, three paths emerge: 'Not subscribed', 'Temporary (specified by user per call)', and 'Permanent (active for all calls)'. The 'Temporary' path leads to a decision 'Entered value?'. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. If 'None', it leads to another decision 'Default value?'. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. Both 'SET PI' boxes lead to 'INFORM 2 req. ind.'.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +``` + +graph TD + Start((12)) -- 943 --> SRO{Sub-scriber restricted option} + SRO -- Not subscribed --> SPA[SET PI = presentation allowed] + SRO -- "Temporary (specified by user per call)" -- 943 --> EV{Entered value?} + SRO -- "Permanent (active for all calls)" --> SPR[SET PI = presentation restricted] + + EV -- Allowed --> SPA + EV -- Restricted --> SPR + EV -- None -- 943 --> DV{Default value?} + + DV -- Allowed --> SPA + DV -- Restricted --> SPR + + SPA -- 943 --> Join(( )) + SPR -- 943 --> Join + + Join -- "947 FE3" --> I[INFORM 2 req. ind.] + I --> End(X) + +``` + +Flowchart details: The process begins at node 12, passing through a point labeled 943. It proceeds to the 'Sub-scriber restricted option' decision. From this block, three options are available: 'Not subscribed', 'Temporary (specified by user per call)', and 'Permanent (active for all calls)'. The 'Not subscribed' path leads directly to 'SET PI = presentation allowed'. The 'Permanent' path leads directly to 'SET PI = presentation restricted'. The 'Temporary' option leads through point 943 to a decision diamond 'Entered value?'. If 'Allowed', the flow goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. If 'None', it leads through point 943 to another decision diamond 'Default value?'. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. Both 'SET PI' blocks (which are also associated with point 943) lead to a junction point. From this junction, the flow proceeds to 'INFORM 2 req. ind.', which is associated with '947 FE3'. The flowchart ends at a terminal cross symbol. + +Flowchart for COLP and COLR - FE4. It starts at node 12, leading to 'Subscriber restricted option'. From there, three paths emerge: 'Not subscribed', 'Temporary (specified by user per call)', and 'Permanent (active for all calls)'. The 'Temporary' path leads to a decision 'Entered value?'. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. If 'None', it leads to another decision 'Default value?'. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. Both 'SET PI' boxes lead to 'INFORM 2 req. ind.'. + +T1126391-91 + +FIGURE 5-11/Q.81 +**COLP and COLR – FE4** + +![A flow diagram showing a sequence of call components. At the top is a circle labeled 'COL7' with a dashed line leading to a bracket labeled 'Note'. An arrow points down from 'COL7' to a rectangle labeled 'COLP/COLR4'. Below this rectangle, an arrow points down to a circle labeled 'COL8', which also has a dashed line leading to a bracket labeled 'Note'.](9a5927586a691c4908aa2cf98bd47ebb_img.jpg) + +A flow diagram showing a sequence of call components. At the top is a circle labeled 'COL7' with a dashed line leading to a bracket labeled 'Note'. An arrow points down from 'COL7' to a rectangle labeled 'COLP/COLR4'. Below this rectangle, an arrow points down to a circle labeled 'COL8', which also has a dashed line leading to a bracket labeled 'Note'. + +T1129550-91 + +*Note* – COL7 and COL8 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “18 r $\frac{1}{2}$ CALL SENT”. COL8 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-16 (sheet 2 of 5) of Recommendation Q.71 [5]), following state “17 r $\frac{1}{2}$ CALL SENT”. COL8 reconnects at the same point. + +FIGURE 5-12/Q.81 +**Hooks to basic call for FE4** + +![Flowchart for COLP and COLR - FE5. The process starts with an oval connector, leading to a decision diamond 'Special arrangement?'. If 'Yes', it goes to a box 'Provide a complete national or international ISDN number' (linked to 955, 956), then to 'See Note 2 See Note 3' (linked to 957, 958). If 'No', it goes to 'See Note 1' (linked to 950). Both paths lead to a decision diamond 'COLR invoke?'. If 'Yes', it goes to 'Include presentation indicator See Note 4' (linked to 951). If 'No', it goes directly to 'INFORM 1 req. ind.' (linked to FE4). All three paths converge to a final connector symbol.](0b7849dae424b0dd33e6386d2384643a_img.jpg) + +``` + +graph TD + Start([ ]) --> SA{Special arrangement?} + SA -- Yes --> P[Provide a complete national or international ISDN number] + SA -- No --> SN1[See Note 1] + P --> SN23[See Note 2 +See Note 3] + SN23 --> CI{COLR invoke?} + SN1 --> CI + CI -- Yes --> PI[Include presentation indicator +See Note 4] + CI -- No --> I[INFORM 1 req. ind.] + PI --> I + I --> End([X]) + +``` + +Flowchart for COLP and COLR - FE5. The process starts with an oval connector, leading to a decision diamond 'Special arrangement?'. If 'Yes', it goes to a box 'Provide a complete national or international ISDN number' (linked to 955, 956), then to 'See Note 2 See Note 3' (linked to 957, 958). If 'No', it goes to 'See Note 1' (linked to 950). Both paths lead to a decision diamond 'COLR invoke?'. If 'Yes', it goes to 'Include presentation indicator See Note 4' (linked to 951). If 'No', it goes directly to 'INFORM 1 req. ind.' (linked to FE4). All three paths converge to a final connector symbol. + +T1126401-91 + +*Note 1* – Provide a partial, subscriber, national or international number according to destination user's request. + +*Note 2* – Set type of number – national or international number and set numbering plan identification – ISDN number. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP) other types of numbers may be required. Those will be specified in Recommendation Q.85, § 2. + +*Note 4* – This information is applicable to COLR temporary mode. + +FIGURE 5-13/Q.81 +**COLP and COLR – FE5** + +![Diagram showing the flow of call control messages. A circle labeled COL9 has a dashed line to a 'Note' and a solid arrow pointing down to a rectangle labeled COLP/COLR5. The rectangle has a solid arrow pointing down to a circle labeled COL10, which also has a dashed line to a 'Note'.](798679874d1c29f8343506a156c79d7e_img.jpg) + +``` + +graph TD + COL9((COL9)) -.-> Note1[Note] + COL9 --> COLP_COLR5[COLP/COLR5] + COLP_COLR5 --> COL10((COL10)) + COL10 -.-> Note2[Note] + +``` + +Diagram showing the flow of call control messages. A circle labeled COL9 has a dashed line to a 'Note' and a solid arrow pointing down to a rectangle labeled COLP/COLR5. The rectangle has a solid arrow pointing down to a circle labeled COL10, which also has a dashed line to a 'Note'. + +T1131020-91 + +*Note* – COL9 and COL10 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “ $\tau_2$ - $\tau_2$ CALL SENT”. COL10 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-16 (sheet 2 of 5) of Recommendation Q.71 [5]), following state “ $\tau_2$ - $\tau_1$ CALL SENT”. COL10 reconnects at the same point; or +- following the receipt of the SETUP resp. (see Figure 2-17 (sheet 2 of 6) of Recommendation Q.71 [5]), following state “INCOMING SETUP”. COL10 reconnects at the same point. + +FIGURE 5-14/Q.81 +**Hooks to basic call for FE5** + +### 5.9 Functional entity actions (FEAs) + +#### 5.9.1 FEAs of FE1 + +- 910: FE1 shall receive the service information from FE2; +- 911: FE1 shall transfer the received information into a format that makes it usable for establishing a call; +- 912: FE1 shall present the received information to the served user. + +#### 5.9.2 FEAs of FE2 + +- 920: FE2 shall check if the COLP supplementary service is subscribed to; +- 921: FE2 shall check if the connected line identity is provided. If the number is not available, then FE2 shall set the presentation indicator to “number not available”; +- 922: FE2 shall check if presentation restrictions exist. If presentation restrictions exist, the number and sub-address information shall be erased, no number information shall be sent to the calling party and the received presentation indicator (PI) showing “presentation restricted” shall be sent to FE1 unless FE5 has the override category. If FE1 has such a category, then all the received information shall be sent to FE1; + +- 923: FE2 shall transfer the received information into a format that makes it usable by FE1 (e.g. adding prefixes); +- 924: FE2 shall forward the information to FE1. + +#### 5.9.3 *FEAs of FE3* + +In the case of a national call, FE3 has null functionality. + +- 930: FE3 shall check if a partial number or no information is received. In this case no information is sent to FE2; +- 931: FE3 shall check if the connected line identity may be passed between the networks; +- 932: FE3 shall convert a national number to an international ISDN number if not already in this form. Number belonging to other numbering plans shall be passed transparently; +- 933: if a number cannot be passed to FE2, FE3 shall erase the number and sub-address information and shall set the presentation indicator to “number not available”. +- 934: FE3 shall forward the information to FE2. + +#### 5.9.4 *FEAs of FE4* + +- 940: FE4 shall check if the connected line identity is provided by FE5 and if not, shall include the default connected line identity with the presentation indicator set to “network provided”; +- 941: FE4 shall verify connected line identity (unless a special arrangement for not screening the number exists); +- 942: FE4 shall complete a partial number or a subscriber number to a national number. FE4 shall put the number into the format used in the current ISDN; +- 943: FE4 shall set the presentation indicator; +- 944: FE4 shall set the screening indicator; +- 945: FE4 shall set the type of number (when a special arrangement exists, FE5 shall also set the type of number); +- 946: FE4 shall set the numbering plan identification (when a special arrangement exists, FE5 shall also set the numbering plan identification); +- 947: FE4 shall forward the information to FE3. + +#### 5.9.5 *FEAs of FE5* + +- 950: FE5 shall receive and shall forward destination users service requests to FE4; +- 951: FE5 shall request the COLR supplementary service temporary mode (override of network stored value of presentation indicator); +- 955: in the case of a special arrangement, FE5 shall screen the number to be provided; +- 956: in the case of a special arrangement, FE5 shall complete the number to national or international format (for ISDN numbers); +- 957: FE5 shall set the type of number; +- 958: FE5 shall set the numbering plan identification. + +### 5.10 *Allocation of functional entities to physical locations* + +The possible locations of functional entities FE1, FE2, FE3, FE4 and FE5 are shown in Table 5-5/Q.81. + +TABLE 5-5/Q.81 + +| Scenarios | FE1 | FE2 | FE3 | FE4 | FE5 | +|-----------|-----|-----|--------|-----|-----| +| 1 | TE | LE | – | LE | TE | +| 2 | TE | LE | INT TR | LE | TE | +| 3 | PNX | LE | – | LE | PNX | +| 4 | PNX | LE | INT TR | LE | PNX | +| 5 | PNX | LE | – | LE | TE | +| 6 | PNX | LE | INT TR | LE | TE | +| 7 | TE | LE | – | LE | PNX | +| 8 | TE | LE | INT TR | LE | PNX | + +### 5.11 *Interactions with other supplementary services* + +The COLP supplementary service interacts with the freephone supplementary service in such a way that when the freephone supplementary service is used, the served user shall receive the freephone number as the connected line identification. The description of this is included in the stage 2 description of the freephone supplementary service (see Recommendation Q.86, Section 4 [10]). \ No newline at end of file diff --git a/marked/Q/T-REC-Q.81.5-199109-I_PDF-E/raw.md b/marked/Q/T-REC-Q.81.5-199109-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f6697ea01c6e4977bde8b1c9272939982d007a4a --- /dev/null +++ b/marked/Q/T-REC-Q.81.5-199109-I_PDF-E/raw.md @@ -0,0 +1,1550 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**Q.81** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +# **FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN** --- + +## **STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES** + +SECTION 3 – CALLING LINE IDENTIFICATION PRESENTATION (CLIP) +AND CALLING LINE IDENTIFICATION RESTRICTION (CLIR) + +SECTION 5 – CONNECTED LINE IDENTIFICATION, PRESENTATION +AND RESTRICTION (COLP AND COLR) + +**Modifications to +Recommendation Q.81** + +--- + +![CCITT logo: A globe with the letters CCITT.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +Geneva, 1991 + +## FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation Q.81, §§ 3 and 5 was prepared by Study Group XI and was approved under the Resolution No. 2 procedure on the 10th of September 1991. + +## --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. + +## **STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES** + +*(revised 1991)* + +## **3 Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR)** + +### **3.1 Scope** + +This Recommendation defines the stage 2 of the integrated services digital network (ISDN) as provided by the telecommunications operators for the Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR) supplementary services. Stage 2 identifies the functional capabilities and the information flows needed to support the service description. The stage 2 description also identifies user operations not directly associated with a call (see Recommendation I.130 [1]). + +This Recommendation is defined according to the methodology specified in Recommendation Q.65 [2]. + +This Recommendation does not formally describe the relationship between these supplementary services and the basic call but, where possible, this information is included for guidance. + +In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities within a private ISDN; it does however define which functional entities may be allocated to a private ISDN. + +This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. + +The CLIP supplementary service provides the called party with the possibility to receive identification of the calling party. + +The CLIR supplementary service enables the calling party to prevent presentation of its ISDN number to the called party. + +The CLIP and CLIR supplementary services are applicable to all telecommunication services. + +This Recommendation is applicable to the stage 3 Recommendations for the ISDN CLIP and CLIR supplementary services, as defined in Recommendation I.130 [1]. + +### **3.2 References** + +These references are cited at the appropriate places in the text and the publications are listed hereafter. Dated references, subsequent amendments to, or revisions of any of these publications apply to this Recommendation only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. + +- [1] CCITT Rec. I.130 (1988) – Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. +- [2] CCITT Rec. Q.65 (1988) – Stage 2 of the method for the characterization of services supported by an ISDN. +- [3] CCITT Rec. I.251.3 – Calling Line Identification Presentation (CLIP). + +- [4] CCITT Rec. I.251.4 – Calling Line Identification Restriction (CLIR). +- [5] CCITT Rec. Q.71 – ISDN 64 kbit/s circuit mode switched bearer services. +- [6] CCITT Rec. I.112 (1988) – Vocabulary of terms for ISDNs. +- [7] CCITT Rec. I.210 (1988) – Principles of telecommunication services supported by an ISDN and the means to describe them. +- [8] CCITT Rec. E.164 (1991) – Numbering plan for the ISDN era. +- [9] CCITT Rec. I.330 (1988) – ISDN numbering and addressing principles. + +### 3.3 *Definitions* + +For the purposes of this Recommendation, the following definitions apply: + +#### **integrated services digital network (ISDN)** + +See definition 308 of § 2.3 of Recommendation I.112 [6]. + +#### **service: telecommunication service** + +See definition 201 of § 2.2 of Recommendation I.112 [6]. + +#### **supplementary service** + +See § 2.4 of Recommendation I.210 [7]. + +#### **ISDN number** + +A number conforming to the numbering plan and structure specified in Recommendation E.164 [8]. + +#### **PNP number** + +A number conforming to the numbering plan and structure in a private network. + +#### **sub-address** + +See § 5.4 of Recommendation I.330 [9]. + +#### **calling line identity** + +The address (the ISDN number, and if supplied the sub-address) of the calling line, and the screening indicator. If these are not available the reason is indicated, via the presentation indicator. + +#### **presentation indicator (PI)** + +The PI provides instructions on whether or not the provided calling line identity is allowed to be presented, or indicates that the number is not available. + +#### **screening indicator (SI)** + +The SI provides information on the source and the quality of the provided information. + +### 3.4 *Symbols and abbreviations* + +| | | +|--------|------------------------------------------| +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| PI | Presentation Indicator | +| SI | Screening indicator | +| ISDN | Integrated services digital network | +| TE | Terminal equipment | +| PNX | Private network exchange | +| LE | Local exchange | +| INT TR | International transit exchange | +| FEA | Functional entity action | +| SDL | Specification and description language | +| PNP | Private Numbering Plan | + +### 3.5 *Description* + +The relationship between the CLIP and CLIR supplementary services is described in § 3.6.6 of Recommendation I.251.3 [3] and in Recommendation I.251.4 [4]. + +The provisions for overriding the CLIP supplementary service are described in §§ 3.3.4.2 and 3.6.6 of Recommendation I.251.3 [3] and in Recommendation I.251.4 [4]. + +### 3.6 *Derivation of a functional model* + +#### 3.6.1 *Functional model description* + +The model for the CLIP and CLIR supplementary services is shown in Figure 3-1/Q.81. + +![Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. FE1 is connected to FE2 via interface r_a. FE2 is connected to FE3 via interface r_b. FE3 is connected to FE4 via interface r_c. FE4 is connected to FE5 via interface r_d.](d980a3f9608055996a07f31788baf827_img.jpg) + +``` +graph LR; FE1[FE1] -- r_a --> FE2[FE2]; FE2 -- r_b --> FE3[FE3]; FE3 -- r_c --> FE4[FE4]; FE4 -- r_d --> FE5[FE5]; +``` + +Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. FE1 is connected to FE2 via interface r\_a. FE2 is connected to FE3 via interface r\_b. FE3 is connected to FE4 via interface r\_c. FE4 is connected to FE5 via interface r\_d. + +T1126230-90 + +FIGURE 3-1/Q.81 + +**Functional model** + +#### 3.6.2 *Description of the functional entities* + +The functional entities required by the CLIP and CLIR supplementary services above those of the basic call are as follows: + +- FE1: caller provided information and CLIR requesting entity; +- FE2: service information checking entity; +- FE3: handling of calling line identity at international gateway; +- FE4: service providing entity; +- FE5: service requesting entity. + +#### 3.6.3 *Relationship with a basic service* + +The relationship with a basic service is shown in Figure 3-2/Q.81. The model for basic call handling is defined in Recommendation Q.71. + +### 3.7 *Information flows* + +#### 3.7.1 *Information flow diagrams* + +Figure 3-3/Q.81 shows the information flow diagrams for the CLIP and the CLIR supplementary services. + +#### 3.7.2 *Definition of individual information flows* + +Within the definitions below, the PI can take one of the following three rules: + +- a) presentation allowed; +- b) presentation restricted; or +- c) number not available. + +Within the definitions below, the SI can take one of the following three rules: + +- a) user provided, verified and passed; +- b) network provided; or +- c) user provided, not screened. + +![Functional model diagram showing five functional entities (FE1 to FE5) and their corresponding control entities (CCA, CC, CC, CC, CCA) connected by interfaces r_a, r_b, r_c, r_d and r_1, r_2, r_2, r_3. A label T1126241-91 is present at the bottom right.](fc46871d72c65d3381d9201646d23439_img.jpg) + +T1126241-91 + +Functional model diagram showing five functional entities (FE1 to FE5) and their corresponding control entities (CCA, CC, CC, CC, CCA) connected by interfaces r\_a, r\_b, r\_c, r\_d and r\_1, r\_2, r\_2, r\_3. A label T1126241-91 is present at the bottom right. + +FIGURE 3-2/Q.81 +**Example of a mapping of the functional model + on a model for the basic call** + +![Information flows diagram showing the sequence of messages (SETUP, INFORM) between functional entities FE1 to FE5. The diagram includes message details such as '211 SETUP 221', '910 911 >>> req.ind >>>', and 'INFORM 1 req.ind.' with associated line numbers. A label T1126250-90 is present at the bottom right.](a738993919a50143787084ee7ce6e2f2_img.jpg) + +T1126250-90 + +Information flows diagram showing the sequence of messages (SETUP, INFORM) between functional entities FE1 to FE5. The diagram includes message details such as '211 SETUP 221', '910 911 >>> req.ind >>>', and 'INFORM 1 req.ind.' with associated line numbers. A label T1126250-90 is present at the bottom right. + +FIGURE 3-3/Q.81 +**Information flows** + +##### 3.7.2.1 Relationship $r_a$ + +###### 3.7.2.1.1 Contents of INFORM 1 + +The contents of the INFORM 1 are shown in Table 3-1/Q.81. + +The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 3-1/Q.81 + +###### **INFORM 1 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|--------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Opt. (Note 1) | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | Partial number
Subscriber number
National number
International number
(Note 2)
(Note 5) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 3) | +| Presentation indicator | Presentation allowed
Presentation restricted | Opt. (Note 4) | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – Included if FE1 provides information. + +*Note 2* – When a special arrangement exists only national or international number is allowed. + +*Note 3* – May be omitted even if number information is provided. + +*Note 4* – This information flow is mandatory only in the case that the CLIR supplementary service temporary mode applies and FE1 wants to override the default PI stored in FE2. + +*Note 5* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +##### 3.7.2.2 Relationship $r_b$ + +###### 3.7.2.2.1 Contents of INFORM 2 + +The contents of the INFORM 2 are shown in Table 3-2/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 3-2/Q.81 + +###### **INFORM 2 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 2) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted | Mand. | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE1 provides the information. + +*Note 2* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +##### 3.7.2.3 Relationship $r_c$ + +###### 3.7.2.3.1 Contents of INFORM 3 + +The contents of the INFORM 3 are shown in Table 3-3/Q.81. The contents for SETUP are as specified for basic call. + +TABLE 3-3/Q.81 + +###### **INFORM 3 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.
(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE1 provides the information. + +*Note 2* – No number information is provided in the case that the CLIR supplementary service applies and no bilateral agreement exists between the networks for the handling of restricted information. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +##### 3.7.2.4 Relationship *rd* + +###### 3.7.2.4.1 Contents of INFORM 4 + +The contents of the INFORM 4 are shown in Table 3-4/Q.81. The contents for SETUP are as specified for basic call. + +TABLE 3-4/Q.81 + +###### **INFORM 4 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.
(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE1 provides the information. + +*Note 2* – No number information is provided in the case that the CLIR supplementary service applies. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +![SDL diagram for CLIP and CLIR functional entities. The process starts with an initial state leading to a decision 'Special arrangement?'. If 'Yes', it goes to 'Provide a complete national or international ISDN number?'. If 'No', it goes to 'See Note 1'. Both lead to a decision 'CLIR invoked?'. If 'Yes', it goes to 'Include presentation indicator See Note 4'. If 'No', it goes to 'INFORM 1 req. ind.'. All three lead to a final state. Various notes and reference numbers (915, 910, 911, 916, 917, 918, T1126261-91, 910 FE2) are associated with the blocks.](007b053fe94a8348f75128a584503fd0_img.jpg) + +``` + +graph TD + Start([ ]) --> Special{Special +arrangement?} + Special --|No| Note1[See Note 1] + Special --|Yes| Provide[Provide a complete +national or +international +ISDN number?] + Note1 --> CLIR{CLIR +invoked?} + Provide --> Note23[See Note 2 +See Note 3] + CLIR --|Yes| Include[Include presentation +indicator +See Note 4] + CLIR --|No| Merge1(( )) + Include --> Merge1 + Note23 --> Merge1 + Merge1 --> Inform{{INFORM 1 +req. ind.}} + Inform --> End(X) + + subgraph References + direction LR + R915[915] -.- Special + R910[910] -.- Note1 + R911[911] -.- Include + R915_916[915 +916] -.- Provide + R917_918[917 +918] -.- Note23 + R910_FE2[910 +FE2] -.- Inform + end + +``` + +T1126261-91 + +SDL diagram for CLIP and CLIR functional entities. The process starts with an initial state leading to a decision 'Special arrangement?'. If 'Yes', it goes to 'Provide a complete national or international ISDN number?'. If 'No', it goes to 'See Note 1'. Both lead to a decision 'CLIR invoked?'. If 'Yes', it goes to 'Include presentation indicator See Note 4'. If 'No', it goes to 'INFORM 1 req. ind.'. All three lead to a final state. Various notes and reference numbers (915, 910, 911, 916, 917, 918, T1126261-91, 910 FE2) are associated with the blocks. + +*Note 1* – Provide a -partial, or -subscriber, or -national, or -international number according to originating user's request. + +*Note 2* – Set type of numbers – national or international number and set numbering plan identification – ISDN number or Private Numbering Plan. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP-Recommendation. + +*Note 4* – This information is applicable to CLIR temporary mode. + +FIGURE 3-4/Q.81 +**CLIP and CLIR – FE1** + +![Flowchart showing the sequence of call hooks for FE1. It starts with a circle labeled CLI1 connected to a rectangle labeled CLIP/CLIR1, which then connects to a circle labeled CLI2. Each circle is preceded by a 'Note' label connected by a dashed line. The diagram is labeled T1129460-91.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +graph TD + Note1[Note] -.-> CLI1((CLI1)) + CLI1 --> CLIP[CLIP/CLIR1] + CLIP --> CLI2((CLI2)) + Note2[Note] -.-> CLI2 + T1129460-91[T1129460-91] + +``` + +Flowchart showing the sequence of call hooks for FE1. It starts with a circle labeled CLI1 connected to a rectangle labeled CLIP/CLIR1, which then connects to a circle labeled CLI2. Each circle is preceded by a 'Note' label connected by a dashed line. The diagram is labeled T1129460-91. + +*Note* – CLI1 and CLI2 break the basic call transition: + +- during FEA211 (see Figure 2-13 (sheet 1 of 5) of Recommendation Q.71 [5]), immediately following the task “Process service request connect”. +CLI2 reconnects at the same point; +- after sending SETUP req. ind. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]). +CLI2 reconnects at the same point; or +- during FEA221 (see Figure 2-14 (sheet 1 of 7) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. +CLI2 reconnects at the same point. + +FIGURE 3-5/Q.81 +**Basic call hooks for FE1** + +![Flowchart for CLIP and CLIR - FE2. The process starts with an oval start shape leading to an INFORM 1 req. ind. block. This leads to a decision: 'Calling id. suppl. by the user?'. If 'No', it goes to 'Calling number = default number' and then 'SET SI = network provided'. If 'Yes', it goes to another decision: 'Special arrangement?'. If 'Yes' to special arrangement, it goes to 'SET SI = user provided not screened'. If 'No' to special arrangement, it goes to 'Verification of calling line identity'. If 'Not OK', it goes back to 'Calling number = default number'. If 'OK', it goes to 'SET SI = user provided verified and passed'. Both 'SET SI' paths lead to a 'Note' block and then to a connector circle labeled '12 2'.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM1[INFORM 1 +req. ind.] + INFORM1 --> Q1{Calling +id. suppl. by +the user?} + Q1 -- Yes --> Q2{Special +arrangement?} + Q1 -- No --> SETSI1[Calling number = +default number] + Q2 -- Yes --> SETSI3[SET SI = +user provided +not screened] + Q2 -- No --> Q3{Verification +of calling line +identity} + Q3 -- Not OK --> SETSI1 + Q3 -- OK --> SETSI2[SET SI = +user provided +verified and passed] + SETSI1 --> SETSI4[SET SI = +network provided] + SETSI2 --> Note[Note] + SETSI3 --> Note + Note --> Connector((12 2)) + SETSI4 --> Connector + + subgraph Labels + FE1 --- INFORM1 + 920 --- Q1 + 921 --- Q2 + 921 --- Q3 + 920 --- SETSI1 + 920 --- SETSI4 + 924 --- SETSI2 + 924 --- SETSI3 + 922 --- Note + 925 --- Note + 926 --- Note + end + +``` + +T1126271-91 + +Flowchart for CLIP and CLIR - FE2. The process starts with an oval start shape leading to an INFORM 1 req. ind. block. This leads to a decision: 'Calling id. suppl. by the user?'. If 'No', it goes to 'Calling number = default number' and then 'SET SI = network provided'. If 'Yes', it goes to another decision: 'Special arrangement?'. If 'Yes' to special arrangement, it goes to 'SET SI = user provided not screened'. If 'No' to special arrangement, it goes to 'Verification of calling line identity'. If 'Not OK', it goes back to 'Calling number = default number'. If 'OK', it goes to 'SET SI = user provided verified and passed'. Both 'SET SI' paths lead to a 'Note' block and then to a connector circle labeled '12 2'. + +*Note* – Complete partial number or subscriber number to a national number. Put the number into the format used in the current ISDN. Set type of number and numbering plan identifier. + +FIGURE 3-6/Q.81 (sheet 1 of 2) + +##### **CLIP and CLIR – FE2** + +![Flowchart for CLIP and CLIR - FE2. It starts with a circle containing '12' and '1'. A dashed line labeled '923' leads to a decision diamond 'Subscriber restrict option'. From this diamond, three paths emerge: 'Not subscribed' (left), 'Permanent (active for all calls)' (right), and 'Temporary (specified by user per call)' (right). The 'Permanent' and 'Temporary' paths both lead to a dashed line labeled '923'. Both 'Not subscribed' and the '923' line from 'Temporary' lead to a decision diamond 'Entered value?'. From 'Entered value?', three paths emerge: 'Allowed' (left), 'Restricted' (right), and 'None' (down). The 'Allowed' path from 'Entered value?' leads to a box 'SET PI = presentation allowed'. The 'Restricted' path from 'Entered value?' leads to a box 'SET PI = presentation restricted'. The 'None' path from 'Entered value?' leads to a dashed line labeled '923', which then leads to a decision diamond 'Default value?'. From 'Default value?', two paths emerge: 'Allowed' (left) leading to 'SET PI = presentation allowed', and 'Restricted' (right) leading to 'SET PI = presentation restricted'. Both 'SET PI' boxes lead to a dashed line labeled '923', which then leads to a pentagon 'INFORM 2 req. ind.'. A bracket labeled '923 FE3' is next to the pentagon. The pentagon leads to a dashed line labeled '923', which then leads to a crossed-out circle (exit).](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +graph TD + Start((12 1)) -- "923" --- SRO{Subscriber +restrict option} + SRO -- "Not subscribed" --- EV{Entered +value?} + SRO -- "Permanent +(active for +all calls)" --- P923[923] + SRO -- "Temporary +(specified +by user +per call)" --- T923[923] + P923 --- EV + T923 --- EV + EV -- "Allowed" --- SPIA[SET PI = +presentation +allowed] + EV -- "Restricted" --- SPIR[SET PI = +presentation +restricted] + EV -- "None" --- N923[923] + N923 --- DV{Default +value?} + DV -- "Allowed" --- SPIA + DV -- "Restricted" --- SPIR + SPIA -- "923" --- I2{{INFORM 2 +req. ind.}} + SPIR -- "923" --- I2 + I2 -- "923 FE3" --- Exit((X)) + +``` + +Flowchart for CLIP and CLIR - FE2. It starts with a circle containing '12' and '1'. A dashed line labeled '923' leads to a decision diamond 'Subscriber restrict option'. From this diamond, three paths emerge: 'Not subscribed' (left), 'Permanent (active for all calls)' (right), and 'Temporary (specified by user per call)' (right). The 'Permanent' and 'Temporary' paths both lead to a dashed line labeled '923'. Both 'Not subscribed' and the '923' line from 'Temporary' lead to a decision diamond 'Entered value?'. From 'Entered value?', three paths emerge: 'Allowed' (left), 'Restricted' (right), and 'None' (down). The 'Allowed' path from 'Entered value?' leads to a box 'SET PI = presentation allowed'. The 'Restricted' path from 'Entered value?' leads to a box 'SET PI = presentation restricted'. The 'None' path from 'Entered value?' leads to a dashed line labeled '923', which then leads to a decision diamond 'Default value?'. From 'Default value?', two paths emerge: 'Allowed' (left) leading to 'SET PI = presentation allowed', and 'Restricted' (right) leading to 'SET PI = presentation restricted'. Both 'SET PI' boxes lead to a dashed line labeled '923', which then leads to a pentagon 'INFORM 2 req. ind.'. A bracket labeled '923 FE3' is next to the pentagon. The pentagon leads to a dashed line labeled '923', which then leads to a crossed-out circle (exit). + +T1126281-91 + +FIGURE 3-6/Q.81 (sheet 2 of 2) +**CLIP and CLIR – FE2** + +![Flowchart showing the sequence of call hooks for FE2. It starts with a circle labeled 'CLI3' with a dashed line from a 'Note' box. An arrow points down to a rectangle labeled 'CLIP/CLIR2'. Another arrow points down to a circle labeled 'CLI4' with a dashed line from a 'Note' box. The text 'T1129470-91' is next to the CLI4 circle.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph TD + Note1[Note] -.-> CLI3((CLI3)) + CLI3 --> CLIP[CLIP/CLIR2] + CLIP --> CLI4((CLI4)) + Note2[Note] -.-> CLI4 + T1129470-91[T1129470-91] + +``` + +Flowchart showing the sequence of call hooks for FE2. It starts with a circle labeled 'CLI3' with a dashed line from a 'Note' box. An arrow points down to a rectangle labeled 'CLIP/CLIR2'. Another arrow points down to a circle labeled 'CLI4' with a dashed line from a 'Note' box. The text 'T1129470-91' is next to the CLI4 circle. + +*Note* – CLI3 and CLI4 break the basic call transition: + +- after sending SETUP req. ind. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]). +CLI4 reconnects at the same point; or +- during FEA221 (see Figure 2-14 (sheet 1 of 7) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. +CLI4 reconnects at the same point. + +FIGURE 3-7/Q.81 +**Basic call hooks for FE2** + +![Flowchart for CLIP and CLIR - FE3. The process starts with 'INFORM 2 req. ind.' (FE2). A decision 'Calling id. present?' (930 Note 2) follows. If 'No', 'No information sent' (930) is output. If 'Yes', a decision 'Presentation allowed?' (931) is made. If 'No', 'Spec. agreement on presentation?' (931 Note 1) is checked. If 'Yes', 'CLI = ISDN number?' is checked. If 'No', 'International number?' (932) is checked. If 'Yes', 'Convert national number to international number' (932) is done. Finally, 'Keep PI and SI, as provided by FE2' is output, followed by 'INFORM 3 req. ind.' (934 FE4).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM2[INFORM 2 req. ind.] + INFORM2 --> CallingIdPresent{Calling id. present?} + CallingIdPresent -- No --> NoInfo[No information sent] + CallingIdPresent -- Yes --> PresentationAllowed{Presentation allowed?} + PresentationAllowed -- No --> SpecAgreement{Spec. agreement on presentation?} + SpecAgreement -- No --> SetPI[SET PI = presentation restricted. Erase calling identity] + SpecAgreement -- Yes --> CLIIsdn{CLI = ISDN number?} + CLIIsdn -- Yes --> International{International number?} + CLIIsdn -- No --> KeepPI[Keep PI and SI, as provided by FE2] + International -- Yes --> Convert[Convert national number to international number] + International -- No --> KeepPI + Convert --> KeepPI + NoInfo --> INFORM3[INFORM 3 req. ind.] + SetPI --> INFORM3 + KeepPI --> INFORM3 + INFORM3 --> End([X]) + +``` + +Note 1 – Based on bilateral agreements. + Note 2 – Calling id. present = “No” when: + – an incomplete number is received, or + – no information is received. + +T1126291-91 + +Flowchart for CLIP and CLIR - FE3. The process starts with 'INFORM 2 req. ind.' (FE2). A decision 'Calling id. present?' (930 Note 2) follows. If 'No', 'No information sent' (930) is output. If 'Yes', a decision 'Presentation allowed?' (931) is made. If 'No', 'Spec. agreement on presentation?' (931 Note 1) is checked. If 'Yes', 'CLI = ISDN number?' is checked. If 'No', 'International number?' (932) is checked. If 'Yes', 'Convert national number to international number' (932) is done. Finally, 'Keep PI and SI, as provided by FE2' is output, followed by 'INFORM 3 req. ind.' (934 FE4). + +FIGURE 3-8/Q.81 +CLIP and CLIR – FE3 + +![Flowchart showing the sequence of call hooks: CLI5, CLIP/CLIR3, and CLI6. CLI5 and CLI6 are circles with 'Note' labels, and CLIP/CLIR3 is a double-bordered rectangle. Arrows show the flow from CLI5 to CLIP/CLIR3 to CLI6.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` +graph TD; CLI5((CLI5)) -- Note --- CLI5; CLI5 --> CLIP[CLIP/CLIR3]; CLIP --> CLI6((CLI6)); CLI6 -- Note --- CLI6; +``` + +T1129480-91 + +Flowchart showing the sequence of call hooks: CLI5, CLIP/CLIR3, and CLI6. CLI5 and CLI6 are circles with 'Note' labels, and CLIP/CLIR3 is a double-bordered rectangle. Arrows show the flow from CLI5 to CLIP/CLIR3 to CLI6. + +*Note* – CLI5 and CLI6 break the basic call transition during FEA231 (see Figure 2-15 (sheet 1 of 4) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. CLI6 reconnects at the same point. + +FIGURE 3-9/Q.81 +**Basic call hooks for FE3** + +![Flowchart for CLIP et CLIR - FE4. The process starts with INFORM 3 req. ind. (FE3). It then checks if CLIP Sub. or CLIP general. avail.? (940). If No, it goes to Note 1 (940). If Yes, it checks if Any info. about CLI available? (941). If No, it goes to SET PI = number not available (941). If Yes, it checks if Any presentation restrictions? (942). If Yes, it goes to Override? (942). If No, it goes to Include received PI and SI (942). If Override? is Yes, it goes to Note 2 (942). If Override? is No, it goes to Convert to format to be presented to user (943). All paths lead to INFORM 4 req. ind. (944 FE5).](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM3[INFORM 3 req. ind.] + INFORM3 -.-> FE3[FE3] + INFORM3 --> CLIPSub{CLIP Sub. or CLIP general. avail.?} + CLIPSub -.-> 940[940] + CLIPSub -- No --> Note1[Note 1] + Note1 -.-> 940[940] + CLIPSub -- Yes --> AnyInfo{Any info. about CLI available?} + AnyInfo -.-> 941[941] + AnyInfo -- No --> SETPI[SET PI = number not available] + SETPI -.-> 941[941] + AnyInfo -- Yes --> AnyRestrictions{Any presentation restrictions?} + AnyRestrictions -.-> 942[942] + AnyRestrictions -- Yes --> Override{Override?} + Override -.-> 942[942] + Override -- Yes --> Note2[Note 2] + Note2 -.-> 942[942] + Override -- No --> NoRestrictions[No] + NoRestrictions --> IncludePI[Include received PI and SI] + IncludePI -.-> 942[942] + IncludePI --> ConvertFormat[Convert to format to be presented to user] + ConvertFormat -.-> 943[943] + ConvertFormat --> INFORM4[INFORM 4 req. ind.] + INFORM4 -.-> 944[944] + INFORM4 -.-> FE5[FE5] + INFORM4 --> End([X]) + +``` + +Flowchart for CLIP et CLIR - FE4. The process starts with INFORM 3 req. ind. (FE3). It then checks if CLIP Sub. or CLIP general. avail.? (940). If No, it goes to Note 1 (940). If Yes, it checks if Any info. about CLI available? (941). If No, it goes to SET PI = number not available (941). If Yes, it checks if Any presentation restrictions? (942). If Yes, it goes to Override? (942). If No, it goes to Include received PI and SI (942). If Override? is Yes, it goes to Note 2 (942). If Override? is No, it goes to Convert to format to be presented to user (943). All paths lead to INFORM 4 req. ind. (944 FE5). + +T1126301-91 + +Note 1 – No information about the calling line identity is sent to the called party. + +Note 2 – SET PI = presentation restricted. Numbering information will not be presented to the called party. + +FIGURE 3-10/Q.81 + +##### CLIP et CLIR – FE4 + +![Flowchart showing a call hook sequence: CL17 (circle) connected to CLIP/CLIR4 (rectangle) connected to CL18 (circle). Notes are attached to CL17 and CL18 via dashed lines. The code T1129490-91 is at the bottom right.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +graph TD + CL17((CL17)) --> CLIP[CLIP/CLIR4] + CLIP --> CL18((CL18)) + Note1[Note] -.-> CL17 + Note2[Note] -.-> CL18 + T1129490-91[T1129490-91] + +``` + +Flowchart showing a call hook sequence: CL17 (circle) connected to CLIP/CLIR4 (rectangle) connected to CL18 (circle). Notes are attached to CL17 and CL18 via dashed lines. The code T1129490-91 is at the bottom right. + +*Note* – CL17 and CL18 break the basic call transition: + +- during FEA241 (see Figure 2-16 (sheet 1 of 5) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. CL18 reconnects at the same point; or +- during FEA241 (see Figure 2-16 (sheet 1 of 5) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Supplementary services provided”. CL18 reconnects on the “No” branch of the same decision. + +FIGURE 3-11/Q.81 +**Basic call hooks for FE4** + +![Flowchart for FE4 showing steps: INFORM 4 req. ind., Transfer received information into correct format, and INFORM 4 ind. Annotations include 951 FE4, 951, and 952. The code T1126311-91 is at the bottom right.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM1[INFORM 4 req. ind.] + INFORM1 --> TRANSFER[Transfer received information into correct format] + TRANSFER --> INFORM2[INFORM 4 ind.] + INFORM2 --> End((X)) + 951FE4[951 FE4] -.-> INFORM1 + 951[951] -.-> TRANSFER + 952[952] -.-> INFORM2 + T1126311-91[T1126311-91] + +``` + +Flowchart for FE4 showing steps: INFORM 4 req. ind., Transfer received information into correct format, and INFORM 4 ind. Annotations include 951 FE4, 951, and 952. The code T1126311-91 is at the bottom right. + +FIGURE 3-12/Q.81 +**CLIP and CLIR – FE5** + +![Flowchart showing the sequence of call hooks for FE5. It starts with a circle labeled 'CLI9' connected to a 'Note' box, followed by a rectangle labeled 'CLIP/CLIR5', and ending with a circle labeled 'CLI10' connected to another 'Note' box. The identifier 'T1129500-91' is shown below the final circle.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +graph TD + Note1[Note] -.-> CLI9((CLI9)) + CLI9 --> CLIP[CLIP/CLIR5] + CLIP --> CLI10((CLI10)) + CLI10 -.-> Note2[Note] + T1129500-91 + +``` + +Flowchart showing the sequence of call hooks for FE5. It starts with a circle labeled 'CLI9' connected to a 'Note' box, followed by a rectangle labeled 'CLIP/CLIR5', and ending with a circle labeled 'CLI10' connected to another 'Note' box. The identifier 'T1129500-91' is shown below the final circle. + +*Note* – CLI9 and CLI10 break the basic call transition: + +- during FEA251 (see Figure 2-17 (sheet 1 of 4) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Successful?”. CLI8 reconnects at the same point; +- during FEA251 (see Figure 2-17 (sheet 1 of 4) of Recommendation Q.71 [5]), immediately following the “Yes” branch of the decision “Supplementary services provided”. CLI8 reconnects on the “No” branch of the same decision. + +FIGURE 3-13/Q.81 +**Basic call hooks for FE5** + +### 3.9 *Functional entity actions (FEAs)* + +#### 3.9.1 *FEAs for FE1* + +- 910: FE1 shall receive and shall forward originating users service requests to FE2; +- 911: FE1 shall request the CLIR supplementary service temporary mode (override of network stored value of presentation indicator); +- 915: in the case of a special arrangement, FE1 shall screen the number to be provided; +- 916: in the case of a special arrangement, FE1 shall complete the number to national or international format (for ISDN-numbers); +- 917: FE1 shall set the type of number; +- 918: FE1 shall set the numbering plan identification. + +#### 3.9.2 *FEAs of FE2* + +- 920: FE2 shall check if calling line identity is provided by FE1 and if not, shall include the default calling line identity with presentation indicator set to "network provided"; +- 921: FE2 shall verify calling line identity (unless a special arrangement for not screening the number exists); +- 922: FE2 shall complete a partial number or a subscriber number to a national number. FE2 shall put the number into the format used in the current ISDN; +- 923: FE2 shall set the presentation indicator; +- 924: FE2 shall set the screening indicator; +- 925: FE2 shall set the type of number (when a special arrangement exists, FE1 shall also set the type of number); +- 926: FE2 shall set the numbering plan identification (when a special arrangement exists, FE1 shall also set the numbering plan identification); +- 927: FE2 shall forward the information to FE3. + +#### 3.9.3 *FEAs of FE3* + +In the case of a national call, FE3 has null functionality. + +- 930: FE3 shall check if a partial number, or no information, is received. In this case no information is sent to FE4; +- 931: FE3 shall check if the calling line identity may be passed between the networks; +- 932: FE3 shall convert national ISDN-number to an international significant ISDN number if not already in this form. Number belonging to other numbering plans shall be passed transparently; +- 933: if a number cannot be passed to FE4, FE3 shall erase the number and sub-address information and shall set the presentation indicator to "number not available"; +- 934: FE3 shall forward the information to FE4. + +#### 3.9.4 *FEAs for FE4* + +- 940: FE4 shall check if the CLIP supplementary service is subscribed; +- 941: FE4 shall check if calling line identity is provided. If the number is not available, then FE4 shall set the presentation indicator to "number not available"; + +942: FE4 shall check if presentation restrictions exist. If presentation restrictions exist, the number and sub-address information shall be erased, no number information shall be sent to the calling party and the received presentation indicator (PI) showing “presentation restricted” shall be sent to FE5 unless FE5 has the override category. If FE5 has such a category, then all the received information shall be sent to FE5; + +943: FE4 shall transfer the received information into a format that makes it usable by FE5 (e.g. adding prefixes); + +944: FE4 shall forward the information to FE5. + +#### 3.9.5 *FEAs for FE5* + +950: FE5 shall receive the service information from FE4; + +951: FE5 shall transfer the received information into a format that makes it usable for returning a call; + +952: FE5 shall present the received information to the served user. + +### 3.10 *Allocation of functional entities to physical locations* + +The possible locations of functional entities FE1, FE2, FE3, FE4 and FE5 are shown in Table 3-5/Q.81. + +TABLE 3-5/Q.81 + +#### **Locations of functional entities** + +| Scenarios | FE1 | FE2 | FE3 | FE4 | FE5 | +|-----------|-----|-----|--------|-----|-----| +| 1 | TE | LE | – | LE | TE | +| 2 | TE | LE | INT TR | LE | TE | +| 3 | PNX | LE | – | LE | TE | +| 4 | PNX | LE | INT TR | LE | PNX | +| 5 | PNX | LE | – | LE | TE | +| 6 | PNX | LE | INT TR | LE | TE | +| 7 | TE | LE | – | LE | PNX | +| 8 | TE | LE | INT TR | LE | PNX | + +## ANNEX A (to § 3 of Recommendation Q.81) + +#### **Two calling-line-identities delivery option** + +#### A.1 *Scope* + +This annex specifies the additional procedures of the CLIP supplementary service that may be supported as a national network option. + +These national procedures shall have no impact and shall place no requirements whatsoever on the provision and operation of the CLIP supplementary service defined in this Recommendation by public ISDNs that do not support these additional procedures, nor on the interchangeability of terminals. + +#### A.2 *Additional procedures of FE4* + +If the procedures for delivery of the calling line identity as described in § 3.8 (SDL diagram for FE4) apply and the screening indicator is set to "user provided not screened", then the FE4 shall send the second calling line identity immediately following the first calling line identity. The second calling line identity shall be the default calling line identity of the access of the calling party. The second calling line identity shall be provided according to procedures described in this Recommendation. + +In all other cases, only the first calling line identity shall be sent. + +## 5 Connected Line Identification, presentation and restriction (COLP and COLR) + +### 5.1 Scope + +This Recommendation defines the stage 2 of the integrated services digital network (ISDN) as provided by public telecommunications operators for the Connected Line Identification Presentation (COLP) and Connected Line Identification Restriction (COLR) supplementary services. Stage 2 identifies the functional capabilities and the information flows needed to support the service description. The stage 2 description also identifies user operations not directly associated with a call (see Recommendation I.130 [1]). + +This Recommendation is defined according to the methodology specified in Recommendation Q.65 [2]. + +This Recommendation does not formally describe the relation between these supplementary services and the basic call but, where possible, this information is included for guidance. + +In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities within a private ISDN; it does however define which functional entities may be allocated to a private ISDN. + +This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. + +The COLP supplementary service provides the calling party with the possibility to receive identification of the connected party. + +The COLR supplementary service enables the connected party to prevent presentation of its ISDN number to the calling party. + +The COLP and COLR supplementary services are applicable to all telecommunication services. + +This Recommendation is applicable to the stage 3 standards for the ISDN COLP and COLR supplementary services. The term "stage 3" is defined in Recommendation I.130 [1]. + +### 5.2 References + +These references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to, or revisions of any of these publications apply to this Recommendation only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. + +- [1] CCITT Rec. I.130 [1988] – Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. +- [2] CCITT Rec. Q.65 – Stage 2 of the method for the characterization of services supported by an ISDN. +- [3] CCITT Rec. I.251.5 – Connected Line Identification Presentation (COLP). +- [4] CCITT Rec. I.251.6 – Connected Line Identification Restriction (COLR). + +- [5] CCITT Rec. Q.71 – ISDN 64 kbit/s circuit mode switched beared services. +- [6] CCITT Rec. I.112 – Vocabulary of terms for ISDNs. +- [7] CCITT Rec. I.210 – Principles of telecommunication services supported by an ISDN and the means to describe them. +- [8] CCITT Rec. E.164 – Numbering plan for the ISDN era. +- [9] CCITT Rec. I.330 – ISDN numbering and addressing principles. +- [10] CCITT Rec. Q.86, Section 4 – Integrated Services Digital Network (ISDN); Freephone (FPH) supplementary service; Functional capabilities and information flows. + +### 5.3 *Definitions* + +For the purpose of this Recommendation, the following definitions apply: + +#### **integrated services digital network (ISDN)** + +See definition 308 of § 2.3 of Recommendation I.112 [6]. + +#### **service, telecommunications service** + +See definition 201 of § 2.2 of Recommendation I.112 [6]. + +#### **supplementary service** + +See § 2.4 of Recommendation I.210 [7]. + +#### **ISDN number** + +A number conforming to the numbering plan and structure specified in Recommendation E.164 [8]. + +#### **PNP number** + +A number conforming to the numbering plan and structure in a private network. + +#### **sub-address** + +See § 5.4 of Recommendation I.330 [9]. + +#### **connected line identity** + +The address (the ISDN number, and if supplied the sub-address) of the connected line, and the screening indicator. If these are not available the reason is indicated, via the presentation indicator. + +#### **presentation indicator (PI)** + +The PI presentation indicator provides instructions on whether or not the provided connected line identity is allowed to be presented or not, or indicates that the number is not available. + +#### **screening indicator (SI)** + +The SI provides information on the source and the quality of the provided information. + +### 5.4 *Symbols and abbreviations* + +| | | +|--------|--------------------------------------------| +| COLP | Connected Line Identification Presentation | +| COLR | Connected Line Identification Restriction | +| PI | Presentation indicator | +| SI | Screening indicator | +| ISDN | Integrated services digital network | +| TE | Terminal equipment | +| PNX | Private network exchange | +| LE | Local exchange | +| INT TR | International transit exchange | +| FEA | Functional entity action | +| SDL | Specification and description language | +| PNP | Private Numbering Plan | + +### 5.5 *Description* + +The relationship between the COLP and the COLR supplementary services is described in § 5.3.4.2 of Recommendation I.251.5 [3], and in Recommendation I.251.6 [4]. + +The provisions for overriding the COLR supplementary service are described in § 5.3.4.2 of Recommendations I.251.5 [3], and in Recommendation I.251.6 [4]. + +### 5.6 *Derivation of a functional model* + +#### 5.6.1 *Functional model description* + +The model for the COLP and COLR supplementary services is shown in Figure 5-1/Q.81. + +![Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. The connections are labeled r_a, r_b, r_c, and r_d. A reference number T1126320-90 is shown below FE5.](356eb99ab9489bbd647223390a913903_img.jpg) + +``` +graph LR; FE1[FE1] --- r_a --- FE2[FE2]; FE2 --- r_b --- FE3[FE3]; FE3 --- r_c --- FE4[FE4]; FE4 --- r_d --- FE5[FE5]; +``` + +T1126320-90 + +Functional model diagram showing five functional entities (FE1 to FE5) connected in a linear sequence. The connections are labeled r\_a, r\_b, r\_c, and r\_d. A reference number T1126320-90 is shown below FE5. + +FIGURE 5-1/Q.81 + +**Functional model** + +#### 5.6.2 Description of the functional entities + +The functional entities required by the COLP and COLR supplementary services above those of the basic call are as follows: + +- FE1: service requesting entity +- FE2: service providing entity +- FE3: handling of connected line identity at international gateway +- FE4: service information checking entity +- FE5: connected party provided information and COLR requesting entity. + +#### 5.6.3 Relationship with a basic service + +The relationship with a basic service is shown in Figure 5-2/Q.81. The model for basic call handling is defined in Recommendation Q.71. + +![Figure 5-2/Q.81: Example of a mapping of the functional model on a model for the basic call. The diagram shows a sequence of five functional entities (FE1 to FE5) and their corresponding call control (CC) or call connection (CCA) components. FE1 is connected to FE2 via interface r_a, and CCA is connected to CC via interface r_1. FE2 is connected to FE3 via interface r_b, and CC is connected to CC via interface r_2. FE3 is connected to FE4 via interface r_c, and CC is connected to CC via interface r_2. FE4 is connected to FE5 via interface r_d, and CC is connected to CCA via interface r_3. The diagram is labeled T1126330-90.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +``` +graph LR; FE1[FE1] ---|r_a| FE2[FE2]; FE2 ---|r_b| FE3[FE3]; FE3 ---|r_c| FE4[FE4]; FE4 ---|r_d| FE5[FE5]; CCA1[CCA] ---|r_1| CC2[CC]; CC2 ---|r_2| CC3[CC]; CC3 ---|r_2| CC4[CC]; CC4 ---|r_3| CCA5[CCA]; +``` + +Figure 5-2/Q.81: Example of a mapping of the functional model on a model for the basic call. The diagram shows a sequence of five functional entities (FE1 to FE5) and their corresponding call control (CC) or call connection (CCA) components. FE1 is connected to FE2 via interface r\_a, and CCA is connected to CC via interface r\_1. FE2 is connected to FE3 via interface r\_b, and CC is connected to CC via interface r\_2. FE3 is connected to FE4 via interface r\_c, and CC is connected to CC via interface r\_2. FE4 is connected to FE5 via interface r\_d, and CC is connected to CCA via interface r\_3. The diagram is labeled T1126330-90. + +FIGURE 5-2/Q.81 + +Example of a mapping of the functional model on a model for the basic call + +### 5.7 Information flows + +#### 5.7.1 Information flow diagrams + +Figure 5-3/Q.81 shows the information flow diagrams for the COLP and COLR supplementary services. + +![Sequence diagram showing information flow between FE1, FE2, FE3, FE4, and FE5 for COLP and COLR services. The diagram shows a series of SETUP and INFORM messages propagating from right to left (FE5 to FE1).](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +sequenceDiagram + participant FE1 + participant FE2 + participant FE3 + participant FE4 + participant FE5 + Note over FE1,FE2: r_a + Note over FE2,FE3: r_b + Note over FE3,FE4: r_c + Note over FE4,FE5: r_d + FE5->>FE4: SETUP resp. conf. (950, 951, 955, 956) + FE5->>FE4: INFORM 1 req. ind. (957, 958) + FE4->>FE3: SETUP resp. conf. (940-945) + FE4->>FE3: INFORM 2 req. ind. (946, 947) + FE3->>FE2: SETUP resp. conf. (930, 931) + FE3->>FE2: INFORM 3 req. ind. (932, 933) + FE2->>FE1: SETUP resp. conf. (920, 921, 922) + FE2->>FE1: INFORM 4 req. ind. (923, 924) + FE1->>out: INFORM 4 ind. (910, 911, 912) + +``` + +The diagram illustrates the information flow for COLP and COLR across five entities: FE1, FE2, FE3, FE4, and FE5. Dashed lines at the top connect the entities with labels $r_a$ , $r_b$ , $r_c$ , and $r_d$ . Messages flow from right to left. FE5 sends SETUP resp. conf. (950, 951, 955, 956) and INFORM 1 req. ind. (957, 958) to FE4. FE4 sends SETUP resp. conf. (940, 941, 942, 943, 944, 945) and INFORM 2 req. ind. (946, 947) to FE3. FE3 sends SETUP resp. conf. (930, 931) and INFORM 3 req. ind. (932, 933) to FE2. FE2 sends SETUP resp. conf. (920, 921, 922) and INFORM 4 req. ind. (923, 924) to FE1. Finally, FE1 outputs INFORM 4 ind. (910, 911, 912). Specific numbers like 245, 252, 224 are noted near the message arrows. + +Sequence diagram showing information flow between FE1, FE2, FE3, FE4, and FE5 for COLP and COLR services. The diagram shows a series of SETUP and INFORM messages propagating from right to left (FE5 to FE1). + +T1126341-90 + +FIGURE 5-3/Q.81 +**Information flow diagrams for COLP and COLR** + +#### 5.7.2 *Definition of individual information flows* + +Within the definitions below, PI can take one of the following three rules: + +- a) presentation allowed; +- b) presentation restricted; or +- c) number not available. + +Within the definitions below, SI can take one of the following three rules: + +- a) user provided, verified and passed; +- b) network provided; or +- c) user provided, not-screened. + +##### 5.7.2.1 *Relationship $r_a$* + +###### 5.7.2.1.1 *Contents of INFORM 4* + +The contents of the INFORM 4 are shown in Table 5-1/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-1/Q.81 + +###### **INFORM 4 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.

(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number, verified and passed.
User provided number, not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE5 provides the information. + +*Note 2* – No number information is provided in the case that the COLR supplementary service applies. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +##### 5.7.2.2 Relationship $r_b$ + +###### 5.7.2.2.1 Contents of INFORM 3 + +The contents of the INFORM 3 are shown in Table 5-2/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-2/Q.81 + +###### **INFORM 3 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|-----------------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 3) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted
Number not available | Mand.

(Note 2) | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE5 provides the information. + +*Note 2* – No number information is provided in the case that the COLR supplementary service applies and no bilateral agreement exists between the networks for the handling of restricted information. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +#### 5.7.2.3 *Relationship $r_c$* + +###### 5.7.2.3.1 *Contents of INFORM 2* + +The contents of the INFORM 2 are shown in Table 5-3/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-3/Q.81 + +###### **INFORM 2 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Mand. | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | National number
International number
(Note 2) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 1) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted | Mand. | +| Screening indicator (SI) | Network provided number
User provided number,
verified and passed.
User provided number,
not screened | Mand. | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – This information flow is included only in the case that FE5 provides the information. + +*Note 2* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +##### 5.7.2.4 Relationship *rd* + +###### 5.7.2.4.1 Contents of INFORM 1 + +The contents of the INFORM 1 are shown in Table 5-4/Q.81. The contents for SETUP are as specified for basic call (see Recommendation Q.71 [5]). + +TABLE 5-4/Q.81 + +###### **INFORM 1 contents** + +| Parameter | Allowed value | Req. ind. | +|---------------------------------|--------------------------------------------------------------------------------------------------------|---------------| +| Number information | | Opt. (Note 1) | +| – Numbering plan identification | ISDN number
Private Numbering Plan | Mand. | +| – Type of number | Partial number
Subscriber number
National number
International number
(Note 2)
(Note 5) | Mand. | +| – Number digits | | Mand. | +| – Sub-address | | Opt. (Note 3) | +| Presentation indicator (PI) | Presentation allowed
Presentation restricted | Opt. (Note 4) | + +Mand. Mandatory + +Opt. Optional + +*Note 1* – Included if FE5 provides information. + +*Note 2* – When a special arrangement exists, only the national or international number is allowed. + +*Note 3* – May be omitted even if number information is provided. + +*Note 4* – This information flow is included only in the case that the CLOR supplementary service temporary mode applies and FE5 wants to override the default PI stored in FE4. + +*Note 5* – In the case of the supplementary service Private Numbering Plan (PNP), other types of number may be required and will be specified in the PNP Recommendation. + +![SDL diagram for functional entity FE1 showing a sequence from an initial state to a stop symbol.](399a5af4f606059626c92c92279d54b7_img.jpg) + +``` + +graph TD + Start([ ]) --> Input + subgraph " " + direction LR + FE2_910[FE2 +910] -.- Input + end + Input{INFORM 4 +req. ind.} --> Task + Task[Transfer received +information into +correct format] --- Ref911[911] + Task --> Output + Output{INFORM 4 +ind.} --- Ref912[912] + Output --> Stop((X)) + style Start fill:none,stroke:#000 + style Input fill:none,stroke:#000 + style Task fill:none,stroke:#000 + style Output fill:none,stroke:#000 + style Stop fill:none,stroke:#000 + style FE2_910 fill:none,stroke:none + style Ref911 fill:none,stroke:none + style Ref912 fill:none,stroke:none + +``` + +T1126351-91 + +SDL diagram for functional entity FE1 showing a sequence from an initial state to a stop symbol. + +FIGURE 5-4/Q.81 +**COLP and COLR – FE1** + +![Diagram showing hooks to the basic call for FE1 with COL1 and COL2 connectors.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +graph TD + COL1((COL1)) -.- Note1[Note] + COL1 --> Process[COLP/COLR1] + Process --> COL2((COL2)) + COL2 -.- Note2[Note] + style COL1 fill:none,stroke:#000 + style COL2 fill:none,stroke:#000 + style Process fill:none,stroke:#000 + style Note1 fill:none,stroke:none + style Note2 fill:none,stroke:none + +``` + +T1129520-91 + +Diagram showing hooks to the basic call for FE1 with COL1 and COL2 connectors. + +*Note* – COL1 and COL2 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-13 (sheet 1 of 5) of Recommendation Q.71 [5]), following state “1 CALL SENT” and “2 CONNECTION PROCEEDING”. COL2 reconnects at the same point; +- following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]), following state “1 $r_1$ - $r_2$ CALL SENT” and following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 3 of 7) of Recommendation Q.71 [5]), following state “26 $r_1$ - $r_2$ CALL SENT (alerting)”. COL2 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-9 (sheet 11 of 19) of Recommendation Q.71 [5]), following state “18 $r_2$ - $r_2$ CALL SENT”. COL2 reconnects at the same point. + +FIGURE 5-5/Q.81 +**Hooks to basic call for FE1** + +![Flowchart for COLP and COLR - FE2. The process starts with 'INFORM 3 req. ind.' (FE3). It then checks if 'COLP Sub. or COLP generally available?' (920). If No, it goes to 'Note 1' (920). If Yes, it checks if 'Any info. about COL. id. available?' (921). If No, it goes to 'SET PI = number not available' (921). If Yes, it checks if 'Any presentation restrictions?' (922). If Yes, it goes to 'Override category?' (922). If No, it goes to 'Include received PI and SI' (922). From 'Override category?', if Yes, it goes to 'Include received PI and SI' (922). If No, it goes to 'Note 2' (922). Both 'Note 1' and 'Note 2' lead to 'INFORM 4 req. ind.' (924, FE1). 'Include received PI and SI' leads to 'Convert to format to be presented to user' (923), which then leads to 'INFORM 4 req. ind.' (924, FE1). The process ends with a crossed-out arrow.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM3[INFORM 3 req. ind.] + INFORM3 -.-> FE3[FE3] + INFORM3 --> D1{COLP Sub. or COLP generally available?} + D1 -- No --> Note1[Note 1] + Note1 -.-> 920[920] + D1 -- Yes --> D2{Any info. about COL. id. available?} + D2 -- No --> SETPI[SET PI = number not available] + SETPI -.-> 921[921] + D2 -- Yes --> D3{Any presentation restrictions?} + D3 -- Yes --> D4{Override category?} + D3 -- No --> IncludePI[Include received PI and SI] + D4 -- Yes --> IncludePI + D4 -- No --> Note2[Note 2] + Note2 -.-> 922[922] + IncludePI -.-> 922[922] + IncludePI --> Convert[Convert to format to be presented to user] + Convert -.-> 923[923] + Convert --> INFORM4[INFORM 4 req. ind.] + Note1 --> INFORM4 + Note2 --> INFORM4 + INFORM4 -.-> 924[924] + INFORM4 -.-> FE1[FE1] + INFORM4 --> End(( )) + +``` + +Flowchart for COLP and COLR - FE2. The process starts with 'INFORM 3 req. ind.' (FE3). It then checks if 'COLP Sub. or COLP generally available?' (920). If No, it goes to 'Note 1' (920). If Yes, it checks if 'Any info. about COL. id. available?' (921). If No, it goes to 'SET PI = number not available' (921). If Yes, it checks if 'Any presentation restrictions?' (922). If Yes, it goes to 'Override category?' (922). If No, it goes to 'Include received PI and SI' (922). From 'Override category?', if Yes, it goes to 'Include received PI and SI' (922). If No, it goes to 'Note 2' (922). Both 'Note 1' and 'Note 2' lead to 'INFORM 4 req. ind.' (924, FE1). 'Include received PI and SI' leads to 'Convert to format to be presented to user' (923), which then leads to 'INFORM 4 req. ind.' (924, FE1). The process ends with a crossed-out arrow. + +T1126361-91 + +Note 1 – No information about the COL identity is sent to the calling party. + +Note 2 – SET PI – presentation restricted. Erase number information. No number information shall be presented to the calling party. + +FIGURE 5-6/Q.81 +COLP and COLR – FE2 + +![A flow diagram showing a sequence of states. At the top is a circle labeled 'COL3' with a dashed line to a 'Note' box. An arrow points down to a rectangle labeled 'COLP/COLR2'. Another arrow points down from this rectangle to a circle labeled 'COL4', which also has a dashed line to a 'Note' box.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +``` + +graph TD + COL3((COL3)) --> Note1[Note] + COL3 --> COLP_COLR2[COLP/COLR2] + COLP_COLR2 --> COL4((COL4)) + COL4 --> Note2[Note] + +``` + +A flow diagram showing a sequence of states. At the top is a circle labeled 'COL3' with a dashed line to a 'Note' box. An arrow points down to a rectangle labeled 'COLP/COLR2'. Another arrow points down from this rectangle to a circle labeled 'COL4', which also has a dashed line to a 'Note' box. + +T1129530-91 + +*Note* – COL3 and COL4 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 2 of 7) of Recommendation Q.71 [5]), following state “1 $r_1$ - $r_2$ CALL SENT” and following the receipt of the SETUP resp. conf. (see Figure 2-14 (sheet 3 of 7) of Recommendation Q.71 [5]), following state “26 $r_1$ - $r_2$ CALL SENT (alerting)”. COL4 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “18 $r_2$ - $r_2$ CALL SENT”. COL4 reconnects at the same point. + +FIGURE 5-7/Q.81 +**Hooks to basic call for FE2** + +![Flowchart for COLP and COLR - FE3. The process starts with INFORM 2 req. ind. (FE4). It then checks if COL. id. present? (930 Note 2). If Yes, it goes to connector 931. If No, it checks if Presentation allowed? (931). If No, it checks Spec. agreement on presentation? (931 Note 1). If Yes, it checks if COL. id. = ISDN number? (932). If Yes, it checks if International number? (932). If No, it converts national number to international number (932). Both paths lead to Keep PI and SI as provided by FE4. If Presentation allowed? is No, it leads to SET PI = presentation restricted. Erase the number information (933). All three paths lead to INFORM 3 req. ind. (934 FE2).](f57c7b37d7a05a99618104f390089f03_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM2[INFORM 2 req. ind. FE4] + INFORM2 --> COLidPresent{COL. id. present? 930 Note 2} + COLidPresent -- Yes --> Connector931((931)) + COLidPresent -- No --> NoInfo[No information sent 930] + NoInfo --> INFORM3[INFORM 3 req. ind. 934 FE2] + Connector931 --> PresAllowed{Presentation allowed? 931} + PresAllowed -- No --> SpecAgree{Spec. agreement on presentation? 931 Note 1} + SpecAgree -- No --> SetPI[SET PI = presentation restricted. Erase the number information 933] + SpecAgree -- Yes --> COLidISDN{COL. id. = ISDN number? 932} + PresAllowed -- Yes --> COLidISDN + COLidISDN -- Yes --> IntNum{International number? 932} + IntNum -- Yes --> KeepPI[Keep PI and SI as provided by FE4] + IntNum -- No --> ConvertNum[Convert national number to international number 932] + ConvertNum --> KeepPI + COLidISDN -- No --> KeepPI + KeepPI --> INFORM3 + SetPI --> INFORM3 + +``` + +Flowchart for COLP and COLR - FE3. The process starts with INFORM 2 req. ind. (FE4). It then checks if COL. id. present? (930 Note 2). If Yes, it goes to connector 931. If No, it checks if Presentation allowed? (931). If No, it checks Spec. agreement on presentation? (931 Note 1). If Yes, it checks if COL. id. = ISDN number? (932). If Yes, it checks if International number? (932). If No, it converts national number to international number (932). Both paths lead to Keep PI and SI as provided by FE4. If Presentation allowed? is No, it leads to SET PI = presentation restricted. Erase the number information (933). All three paths lead to INFORM 3 req. ind. (934 FE2). + +T1126371-91 + +Note 1 – Based on bilateral agreements. + Note 2 – COL. id. present = “No” when: + – an incomplete number is received, or + – no information is received. + +FIGURE 5-8/Q.81 +**COLP and COLR – FE3** + +![Diagram showing hooks to the basic call for FE3. It consists of three main components connected vertically: a circle labeled COL5 at the top, a rectangle labeled COLP/COLR3 in the middle, and a circle labeled COL6 at the bottom. Arrows point from COL5 to COLP/COLR3 and from COLP/COLR3 to COL6. To the right of COL5 and COL6 are dashed lines leading to brackets labeled 'Note'.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +``` + +graph TD + COL5((COL5)) --> COLP_COLR3[COLP/COLR3] + COLP_COLR3 --> COL6((COL6)) + COL5 -.- Note1[Note] + COL6 -.- Note2[Note] + +``` + +T1129540-91 + +Diagram showing hooks to the basic call for FE3. It consists of three main components connected vertically: a circle labeled COL5 at the top, a rectangle labeled COLP/COLR3 in the middle, and a circle labeled COL6 at the bottom. Arrows point from COL5 to COLP/COLR3 and from COLP/COLR3 to COL6. To the right of COL5 and COL6 are dashed lines leading to brackets labeled 'Note'. + +*Note* – COL5 and COL6 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “18 $r_2$ - $r_2$ CALL SENT”, COL6 reconnects at the same point. + +FIGURE 5-9/Q.81 +**Hooks to basic call for FE3** + +![Flowchart for COLP and COLR - FE4. The process starts with an oval connector, followed by 'INFORM 1 req. ind.' (FE5). A decision diamond 'Conn. id. suppl. by the user?' (940) has a 'Yes' path to 'Special arrangement?' (941) and a 'No' path to 'Connected number = default number' (940). 'Special arrangement?' (941) has a 'Yes' path to 'SET SI = user provided not screened' (944) and a 'No' path to 'Verification of connected line identity?' (941). 'Verification of connected line identity?' (941) has a 'not OK' path back to the 'No' of the first decision and an 'OK' path to 'SET SI = user provided verified and passed' (944). Both 'SET SI' boxes lead to a 'Note' box (942, 945, 946). All three paths (from 'SET SI = network provided' (940), 'Note', and 'SET SI = user provided not screened') lead to a final connector circle (12).](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph TD + Start([ ]) --> INFORM1[INFORM 1 +req. ind.] + INFORM1 -.- FE5[FE5] + INFORM1 --> ConnId{Conn. id. +suppl. by the +user?} + ConnId -.- 940_1[940] + ConnId -- Yes --> SpecialArr{Special +arrangement?} + ConnId -- No --> DefaultNum[Connected +number = default +number] + DefaultNum -.- 940_2[940] + SpecialArr -.- 941_1[941] + SpecialArr -- Yes --> SI_NotScreened[SET SI = +user provided +not screened] + SpecialArr -- No --> VerifIdentity{Verifica- +tion of connected +line identity?} + VerifIdentity -.- 941_2[941] + VerifIdentity -- not OK --> DefaultNum + VerifIdentity -- OK --> SI_Verified[SET SI = +user provided veri- +fied and passed] + SI_Verified -.- 944_1[944] + SI_Verified --> NoteBox[Note] + NoteBox -.- 942[942 +945 +946] + DefaultNum --> SI_NetworkProvided[SET SI = +network provided] + SI_NetworkProvided -.- 940_3[940] + SI_NetworkProvided --> Join1(( )) + NoteBox --> Join1 + SI_NotScreened -.- 944_2[944] + SI_NotScreened --> Join2(( )) + Join1 --> Join2 + Join2 --> End((12)) + +``` + +Flowchart for COLP and COLR - FE4. The process starts with an oval connector, followed by 'INFORM 1 req. ind.' (FE5). A decision diamond 'Conn. id. suppl. by the user?' (940) has a 'Yes' path to 'Special arrangement?' (941) and a 'No' path to 'Connected number = default number' (940). 'Special arrangement?' (941) has a 'Yes' path to 'SET SI = user provided not screened' (944) and a 'No' path to 'Verification of connected line identity?' (941). 'Verification of connected line identity?' (941) has a 'not OK' path back to the 'No' of the first decision and an 'OK' path to 'SET SI = user provided verified and passed' (944). Both 'SET SI' boxes lead to a 'Note' box (942, 945, 946). All three paths (from 'SET SI = network provided' (940), 'Note', and 'SET SI = user provided not screened') lead to a final connector circle (12). + +T1126381-91 + +*Note* – Complete partial number or subscriber number to a national number. Put the number into the format used in the current ISDN. Set type of number and numbering plan identification. + +FIGURE 5-10/Q.81 +**COLP and COLR – FE4** + +![Flowchart for COLP and COLR - FE4. It starts at node 12, leading to 'Subscriber restricted option'. From there, three branches: 'Not subscribed', 'Temporary (specified by user per call)', and 'Permanent (active for all calls)'. The 'Temporary' branch leads to 'Entered value?' decision. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. If 'None', it leads to 'Default value?' decision. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. Both 'SET PI' boxes lead to 'INFORM 2 req. ind.' which then leads to the exit. Various boxes are labeled with 943, and the 'INFORM 2' box is labeled with 947 FE3. A reference code T1126391-91 is present.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +``` + +graph TD + 12((12)) -- 943 --> SRO{Sub-scriber restricted option} + SRO -- Not subscribed --> SPA[SET PI = presentation allowed] + SRO -- "Temporary (specified by user per call)" -- 943 --> EV{Entered value?} + SRO -- "Permanent (active for all calls)" --> SPR[SET PI = presentation restricted] + EV -- Allowed --> SPA + EV -- Restricted --> SPR + EV -- None -- 943 --> DV{Default value?} + DV -- Allowed --> SPA + DV -- Restricted --> SPR + SPA -- 943 --> INF[INFORM 2 req. ind.] + SPR -- 943 --> INF + INF -- 947 FE3 --> Exit(X) + +``` + +Flowchart details: The process begins at node 12. It proceeds to the 'Subscriber restricted option' block. From this block, three paths emerge: 'Not subscribed' (left), 'Temporary (specified by user per call)' (middle), and 'Permanent (active for all calls)' (right). The 'Temporary' path leads to a decision diamond 'Entered value?'. From this diamond, three paths emerge: 'Allowed' (left), 'Restricted' (right), and 'None' (down). The 'Allowed' and 'Restricted' paths lead to 'SET PI = presentation allowed' and 'SET PI = presentation restricted' blocks respectively. The 'None' path leads to another decision diamond 'Default value?'. From this diamond, two paths emerge: 'Allowed' (left) and 'Restricted' (right), both leading to the same 'SET PI' blocks as the 'Entered value?' decision. Both 'SET PI' blocks lead to a block labeled 'INFORM 2 req. ind.'. This block then leads to the exit. Various boxes are labeled with the number 943, and the 'INFORM 2' block is labeled with 947 FE3. A reference code T1126391-91 is present on the right side. + +Flowchart for COLP and COLR - FE4. It starts at node 12, leading to 'Subscriber restricted option'. From there, three branches: 'Not subscribed', 'Temporary (specified by user per call)', and 'Permanent (active for all calls)'. The 'Temporary' branch leads to 'Entered value?' decision. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. If 'None', it leads to 'Default value?' decision. If 'Allowed', it goes to 'SET PI = presentation allowed'. If 'Restricted', it goes to 'SET PI = presentation restricted'. Both 'SET PI' boxes lead to 'INFORM 2 req. ind.' which then leads to the exit. Various boxes are labeled with 943, and the 'INFORM 2' box is labeled with 947 FE3. A reference code T1126391-91 is present. + +FIGURE 5-11/Q.81 +**COLP and COLR – FE4** + +![A flow diagram showing a sequence of call processing steps. At the top is a circle labeled 'COL7' with a dashed line and a bracket pointing to the word 'Note'. An arrow points down from 'COL7' to a rectangular box labeled 'COLP/COLR4'. Another arrow points down from the box to a circle labeled 'COL8', which also has a dashed line and a bracket pointing to the word 'Note'.](9a5927586a691c4908aa2cf98bd47ebb_img.jpg) + +A flow diagram showing a sequence of call processing steps. At the top is a circle labeled 'COL7' with a dashed line and a bracket pointing to the word 'Note'. An arrow points down from 'COL7' to a rectangular box labeled 'COLP/COLR4'. Another arrow points down from the box to a circle labeled 'COL8', which also has a dashed line and a bracket pointing to the word 'Note'. + +T1129550-91 + +*Note* – COL7 and COL8 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “18 r $\frac{1}{2}$ CALL SENT”. COL8 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-16 (sheet 2 of 5) of Recommendation Q.71 [5]), following state “17 r $\frac{1}{3}$ CALL SENT”. COL8 reconnects at the same point. + +FIGURE 5-12/Q.81 +**Hooks to basic call for FE4** + +![Flowchart for COLP and COLR - FE5. It starts with an oval connector, leading to a decision diamond 'Special arrangement?'. If 'Yes', it goes to a box 'Provide a complete national or international ISDN number' (linked to 955, 956), then to 'See Note 2 See Note 3' (linked to 957, 958). If 'No', it goes to 'See Note 1' (linked to 950). Both paths lead to a decision diamond 'COLR invoke?'. If 'Yes', it goes to 'Include presentation indicator See Note 4' (linked to 951). If 'No', it bypasses this box. All three paths (from 'See Note 1', 'See Note 2/3', and 'Include presentation indicator') lead to a pentagon 'INFORM 1 req. ind.' (linked to FE4), which then leads to a downward arrow.](0b7849dae424b0dd33e6386d2384643a_img.jpg) + +``` + +graph TD + Start([ ]) --> SA{Special arrangement?} + SA -- Yes --> P[Provide a complete national or international ISDN number] + SA -- No --> SN1[See Note 1] + P --- 955_956[955 956] + SN1 --- 950[950] + P --> SN23[See Note 2 See Note 3] + SN23 --- 957_958[957 958] + SN1 --> CI{COLR invoke?} + SN23 --> CI + CI -- Yes --> IP[Include presentation indicator See Note 4] + CI -- No --> I[INFORM 1 req. ind.] + IP --- 951[951] + IP --> I + I --- FE4[FE4] + I --> End([ ]) + +``` + +Flowchart for COLP and COLR - FE5. It starts with an oval connector, leading to a decision diamond 'Special arrangement?'. If 'Yes', it goes to a box 'Provide a complete national or international ISDN number' (linked to 955, 956), then to 'See Note 2 See Note 3' (linked to 957, 958). If 'No', it goes to 'See Note 1' (linked to 950). Both paths lead to a decision diamond 'COLR invoke?'. If 'Yes', it goes to 'Include presentation indicator See Note 4' (linked to 951). If 'No', it bypasses this box. All three paths (from 'See Note 1', 'See Note 2/3', and 'Include presentation indicator') lead to a pentagon 'INFORM 1 req. ind.' (linked to FE4), which then leads to a downward arrow. + +T1126401-91 + +*Note 1* – Provide a partial, subscriber, national or international number according to destination user's request. + +*Note 2* – Set type of number – national or international number and set numbering plan identification – ISDN number. + +*Note 3* – In the case of the supplementary service Private Numbering Plan (PNP) other types of numbers may be required. Those will be specified in Recommendation Q.85, § 2. + +*Note 4* – This information is applicable to COLR temporary mode. + +FIGURE 5-13/Q.81 +**COLP and COLR – FE5** + +![Diagram showing the flow of call control messages. A circle labeled COL9 has a dashed line to a 'Note' and a solid arrow pointing down to a rectangle labeled COLP/COLR5. The rectangle has a solid arrow pointing down to a circle labeled COL10, which also has a dashed line to a 'Note'.](798679874d1c29f8343506a156c79d7e_img.jpg) + +``` + +graph TD + COL9((COL9)) -.-> Note1[Note] + COL9 --> COLP_COLR5[COLP/COLR5] + COLP_COLR5 --> COL10((COL10)) + COL10 -.-> Note2[Note] + +``` + +Diagram showing the flow of call control messages. A circle labeled COL9 has a dashed line to a 'Note' and a solid arrow pointing down to a rectangle labeled COLP/COLR5. The rectangle has a solid arrow pointing down to a circle labeled COL10, which also has a dashed line to a 'Note'. + +T1131020-91 + +*Note* – COL9 and COL10 break the basic call transition: + +- following the receipt of the SETUP resp. conf. (see Figure 2-15 (sheet 2 of 4) of Recommendation Q.71 [5]), following state “ $\tau_2$ - $\tau_2$ CALL SENT”. COL10 reconnects at the same point; or +- following the receipt of the SETUP resp. conf. (see Figure 2-16 (sheet 2 of 5) of Recommendation Q.71 [5]), following state “ $\tau_2$ - $\tau_1$ CALL SENT”. COL10 reconnects at the same point; or +- following the receipt of the SETUP resp. (see Figure 2-17 (sheet 2 of 6) of Recommendation Q.71 [5]), following state “INCOMING SETUP”. COL10 reconnects at the same point. + +FIGURE 5-14/Q.81 +**Hooks to basic call for FE5** + +### 5.9 Functional entity actions (FEAs) + +#### 5.9.1 FEAs of FE1 + +- 910: FE1 shall receive the service information from FE2; +- 911: FE1 shall transfer the received information into a format that makes it usable for establishing a call; +- 912: FE1 shall present the received information to the served user. + +#### 5.9.2 FEAs of FE2 + +- 920: FE2 shall check if the COLP supplementary service is subscribed to; +- 921: FE2 shall check if the connected line identity is provided. If the number is not available, then FE2 shall set the presentation indicator to “number not available”; +- 922: FE2 shall check if presentation restrictions exist. If presentation restrictions exist, the number and sub-address information shall be erased, no number information shall be sent to the calling party and the received presentation indicator (PI) showing “presentation restricted” shall be sent to FE1 unless FE5 has the override category. If FE1 has such a category, then all the received information shall be sent to FE1; + +- 923: FE2 shall transfer the received information into a format that makes it usable by FE1 (e.g. adding prefixes); +- 924: FE2 shall forward the information to FE1. + +#### 5.9.3 *FEAs of FE3* + +In the case of a national call, FE3 has null functionality. + +- 930: FE3 shall check if a partial number or no information is received. In this case no information is sent to FE2; +- 931: FE3 shall check if the connected line identity may be passed between the networks; +- 932: FE3 shall convert a national number to an international ISDN number if not already in this form. Number belonging to other numbering plans shall be passed transparently; +- 933: if a number cannot be passed to FE2, FE3 shall erase the number and sub-address information and shall set the presentation indicator to “number not available”. +- 934: FE3 shall forward the information to FE2. + +#### 5.9.4 *FEAs of FE4* + +- 940: FE4 shall check if the connected line identity is provided by FE5 and if not, shall include the default connected line identity with the presentation indicator set to “network provided”; +- 941: FE4 shall verify connected line identity (unless a special arrangement for not screening the number exists); +- 942: FE4 shall complete a partial number or a subscriber number to a national number. FE4 shall put the number into the format used in the current ISDN; +- 943: FE4 shall set the presentation indicator; +- 944: FE4 shall set the screening indicator; +- 945: FE4 shall set the type of number (when a special arrangement exists, FE5 shall also set the type of number); +- 946: FE4 shall set the numbering plan identification (when a special arrangement exists, FE5 shall also set the numbering plan identification); +- 947: FE4 shall forward the information to FE3. + +#### 5.9.5 *FEAs of FE5* + +- 950: FE5 shall receive and shall forward destination users service requests to FE4; +- 951: FE5 shall request the COLR supplementary service temporary mode (override of network stored value of presentation indicator); +- 955: in the case of a special arrangement, FE5 shall screen the number to be provided; +- 956: in the case of a special arrangement, FE5 shall complete the number to national or international format (for ISDN numbers); +- 957: FE5 shall set the type of number; +- 958: FE5 shall set the numbering plan identification. + +### 5.10 *Allocation of functional entities to physical locations* + +The possible locations of functional entities FE1, FE2, FE3, FE4 and FE5 are shown in Table 5-5/Q.81. + +TABLE 5-5/Q.81 + +| Scenarios | FE1 | FE2 | FE3 | FE4 | FE5 | +|-----------|-----|-----|--------|-----|-----| +| 1 | TE | LE | – | LE | TE | +| 2 | TE | LE | INT TR | LE | TE | +| 3 | PNX | LE | – | LE | PNX | +| 4 | PNX | LE | INT TR | LE | PNX | +| 5 | PNX | LE | – | LE | TE | +| 6 | PNX | LE | INT TR | LE | TE | +| 7 | TE | LE | – | LE | PNX | +| 8 | TE | LE | INT TR | LE | PNX | + +### 5.11 *Interactions with other supplementary services* + +The COLP supplementary service interacts with the freephone supplementary service in such a way that when the freephone supplementary service is used, the served user shall receive the freephone number as the connected line identification. The description of this is included in the stage 2 description of the freephone supplementary service (see Recommendation Q.86, Section 4 [10]). \ No newline at end of file diff --git a/marked/Q/T-REC-Q.814-200002-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Q/T-REC-Q.814-200002-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfb306508e5de90fe0a9a96200ef3224196b5d15 --- /dev/null +++ b/marked/Q/T-REC-Q.814-200002-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0f548bf7bb309b429905df1a18eb598603e9b60da694ee80688ddc19b68ff5a +size 56891 diff --git a/marked/Q/T-REC-Q.814-200002-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.814-200002-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a13adce8e719a3ddbdae0b20f4a10d4be0f4fcf9 --- /dev/null +++ b/marked/Q/T-REC-Q.814-200002-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e224023e11b6b11cc6c5b1c2f7eec81f37e357f6df979b44af26bb3f447d8f46 +size 17575 diff --git a/marked/Q/T-REC-Q.814-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.814-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/Q/T-REC-Q.814-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.814-200002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.814-200002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99a52f973759ba63fb087c605c89934b976953ce --- /dev/null +++ b/marked/Q/T-REC-Q.814-200002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fc3886bf6151d251713c095f0bafd29c8e9ea777ef78c4ac829df4f6cdc8dd3 +size 34982 diff --git a/marked/Q/T-REC-Q.814-200002-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Q/T-REC-Q.814-200002-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf385d352bbbb93f095f221b0598a788fd07654c --- /dev/null +++ b/marked/Q/T-REC-Q.814-200002-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e84f2c8b4ea1f4c6f6964f4bd89e0710a4494f73bedd6057d8ba006da67fb03 +size 103606 diff --git a/marked/Q/T-REC-Q.814-200002-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.814-200002-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02893c98252efe510c5678f70b9c57c4f9bef90f --- /dev/null +++ b/marked/Q/T-REC-Q.814-200002-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf507e12eb9faa2613f8803be9931148774f315278504a3718a6afa697161344 +size 107023 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf0287a5578f90f2fe40be057d4b3b966ab0ece0 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:896ae397a72ea74653fcf3c5aa75d5dd548b1440e8e5232742b658af263311dd +size 29273 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..488ae5e9ddc84d8aa1cd8417633d7bea72d90323 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ddc48e6743bf79b5c1cc45f5d6238d503729363d826dfa2ecbdb2c273c4b3a6 +size 27844 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/23cb65390082ab306c15bd3d8196135e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57b865f9215d7d0cd6b7262cbca191aeb1f010df --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/23cb65390082ab306c15bd3d8196135e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8600a93b9ad45a6f33664134c4b5e8b1eba3a958b4d063ed0f41ca40ceddb05b +size 54905 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e079ffef318c7ca1ff0c751934d45067d57d7cff --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5e7ad734490be160b8e59b67070183b1c1a7e365a89abedd99d02ae13fb341c +size 7834 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..589861651c6c69954af9e2ec4245c68b655da14e --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61a9652b66a57b31a038ae91efe087743714c6e6a321fe21e9f10a76e60ac545 +size 35953 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c68d7e58ef2a8bdf77c188b99cf7d1671502af4 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0cb4847a9dede7c333b6ed00922605b36dd411dd793824394a30f540b8c91f9 +size 38102 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..736243222bd191c55e71eb849eb749c669dbcf42 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6db02636724523bd81b1f86005a5cff5ca4bcea8a461093e46a5211b41fc6661 +size 44889 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd1b1d7bf83331ecb2a59285cb156420fa612201 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e7d0bc0bd61ccee157db181ffb36a41e52797de8941a49293046da0e720295f +size 40217 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9f37ad5e041bc1b8f068d412135e1f11273457d --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef7b3457ab84e7fe2e96d063fc259f5fe0b41d66e3384be744b135af28da4feb +size 56147 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c98edfc0f36db32d747597907b467723b7fff13a --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65741ff3be414fa93c1d479958ce8938215b369f674b6e4f4ee42c0119938733 +size 35810 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05640ccc4421bec7abaea70230a4da2b66e335dd --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fcdae097f1ac3ef30151cee7820ddfc71b9290c0ff6a1a3d9662a3aaed67ecc +size 54789 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c75b7a0cf66ab7381824bd3339d531e4ddae80b9 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93ac584ea347d4f7eeaaddb36991b3066c0041abaf49de7ee350dbc863aa3bb7 +size 81312 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f34feb4212772d4c3c89d7a57c6a41813fa8b51 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:307eb9b481a40b1f2a59e435a5e86971cffbac1257c8f6902006a047c3bdf5ef +size 42881 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f752be45f58375d2f23bddd377c49eaed2689871 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e6d14bf81869d2a9ac35fb6a0fbe2445c722e4c7c105b3306f3e6c6aafe2b8d +size 37570 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3608778a5ca791f7644e7dbd74442bdcdf6cfe6 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e52270c76740b9a4e7e66d42f6e2bcf36b5aed73244e2f428c6b96aca46080cb +size 34605 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..180fb705da1cbf1a8fda7e2f9cf85e4f099912ee --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dbb196c3e241c0a00c8f5f195e50558c934e9c99c559660825c178eeeebc363 +size 32121 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58a28ff5a9fbe0197a503f64d96f987f059baa25 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bcdb5cedf048e87b87b259de78e0185a301c27caaf719249cf3c3bae50b9f86 +size 34134 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b5ccef1a764365892e95ec7d80d88b956ab9d27 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17d30e2b8ef1ddf3133ce43c11c95fee63b9fca649e386445d60f6c3645ca90d +size 34877 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f78aa2ca1681258fe3f495e6ed587ce40f37d4c2 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e786ca21bc4704468291ec04322e0db18f142364e289cd4271229775fb029c9 +size 82271 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..782d7e6ca8b1b848e19d2ce5e947ce1f3d12ecd9 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f0d34387db2ef12776838974b106de3e6ba621abaf2363c85f7fa2c5e3fc23a +size 31216 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..630adbb9021ff60169392907a78ea33c0ddb07e9 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ae1c12e8f54ec72bba6c0bb19346cbc2c48ececc9a9cf0b4b20645de0dabc1a +size 36397 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc7d8c902dea1349681a646d7334f68b82867be9 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48f258de2537a4fcdc24f05aed1018d2d8a381f7679e2fd2ae9c3028fe6192cc +size 50794 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/f88e403864388f59871586472847bbd0_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/f88e403864388f59871586472847bbd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..965970e9a79fff9e9e727261d1287e328e7acd35 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/f88e403864388f59871586472847bbd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d46ebd15395aecb53c4756e65ecc3794883310146924da6a7d3f4a26820ce66d +size 33068 diff --git a/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fa4a3e154d28e1b847c1c5874deb35535322724 --- /dev/null +++ b/marked/Q/T-REC-Q.821.1-200109-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d71e4f98c706a96cd3ba22fc75157a46de9519db6d28feb4ceba2fc7d31aee5 +size 49637 diff --git a/marked/Q/T-REC-Q.824.6-199806-I_PDF-E/raw.md b/marked/Q/T-REC-Q.824.6-199806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ae385fa0292a384d9ae721739533c5a1a38004e9 --- /dev/null +++ b/marked/Q/T-REC-Q.824.6-199806-I_PDF-E/raw.md @@ -0,0 +1,6854 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.824.6** + +(06/98) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Q3 interface + +--- + +**Stage 2 and stage 3 description for the Q3 +interface – Customer administration: +Broadband switch management** + +ITU-T Recommendation Q.824.6 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.709 | +| Signalling connection control part (SCCP) | Q.711–Q.719 | +| Telephone user part (TUP) | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION Q.824.6** + +## **STAGE 2 AND STAGE 3 DESCRIPTION FOR THE Q3 INTERFACE – CUSTOMER ADMINISTRATION: BROADBAND SWITCH MANAGEMENT** + +## **Source** + +ITU-T Recommendation Q.824.6 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of June 1998. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 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 | Introduction ..... | 1 | +| 1.1 | Purpose and Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Definitions, abbreviations and conventions ..... | 2 | +| 3.1 | Definitions ..... | 2 | +| 3.2 | Abbreviations ..... | 3 | +| 3.3 | Conventions ..... | 4 | +| 4 | General overview ..... | 4 | +| 4.1 | Entity Relationship Models ..... | 5 | +| 4.1.1 | ATM generic modelling ..... | 5 | +| 4.1.2 | ATM interworking and adaptation layer modelling ..... | 9 | +| 4.1.3 | Broadband customer administration modelling ..... | 10 | +| 4.1.4 | Broadband routing modelling ..... | 11 | +| 4.2 | Inheritance hierarchy ..... | 12 | +| 5 | Formal definitions ..... | 15 | +| 5.1 | Object classes ..... | 15 | +| 5.1.1 | ATM generic fragment ..... | 16 | +| 5.1.2 | ATM adaptation layer fragment ..... | 16 | +| 5.1.3 | Signalling fragment ..... | 18 | +| 5.1.4 | Broadband customer administration fragment ..... | 19 | +| 5.1.5 | Broadband and narrowband interworking call routing fragment ..... | 29 | +| 5.1.6 | Circuit emulation service interworking fragment ..... | 37 | +| 5.2 | Name bindings ..... | 38 | +| 5.2.1 | aalProfile-managedElementR1 ..... | 38 | +| 5.2.2 | aalProtocolCurrentData-interworkingVcTtpBidirectional ..... | 39 | +| 5.2.3 | abstractDestination-managedElementR1 ..... | 39 | +| 5.2.4 | analysisCriteria-managedElementR1 ..... | 39 | +| 5.2.5 | bearerServiceBb-customerProfileBb ..... | 39 | +| 5.2.6 | callingNumberScreeningBb-uniAccess ..... | 40 | +| 5.2.7 | callRoutingOfficeData-managedElementR1 ..... | 40 | +| 5.2.8 | carrierData-managedElementR1 ..... | 40 | +| 5.2.9 | cesServiceProfile-managedElementR1 ..... | 40 | +| 5.2.10 | connectedNumberScreeningBb-uniAccess ..... | 41 | + +| | Page | +|-----------------------------------------------------------------------------------------------------------------------------|-------------| +| 5.2.11 crCircuitEndPoint-crCircuitEndPointSubgroupBb ..... | 41 | +| 5.2.12 crCircuitEndPointSubgroupBb-nniAccess ..... | 41 | +| 5.2.13 customerProfileBb-managedElementR1 ..... | 41 | +| 5.2.14 customizedResourceBb-customerProfileBb ..... | 42 | +| 5.2.15 digitManip-managedElementR1 ..... | 42 | +| 5.2.16 directoryNumberE164-managedElementR1 ..... | 42 | +| 5.2.17 listOfRouteTps-managedElementR1 ..... | 42 | +| 5.2.18 localDestination-managedElementR1 ..... | 43 | +| 5.2.19 nniAccess-managedElementR1 ..... | 43 | +| 5.2.20 postAnalysisEvaluation-managedElementR1 ..... | 43 | +| 5.2.21 prefixDigitAnalysis-managedElementR1 ..... | 43 | +| 5.2.22 routeData-managedElementR1 ..... | 44 | +| 5.2.23 saalUniProtocolProfile-managedElementR1 ..... | 44 | +| 5.2.24 supplementaryServiceDepBb-bearerServiceBb ..... | 44 | +| 5.2.25 supplementaryServiceDepBb-teleserviceBb ..... | 44 | +| 5.2.26 supplementaryServiceIndBb-customerProfileBb ..... | 45 | +| 5.2.27 sVpTtp-managedElementR1 ..... | 45 | +| 5.2.28 teleserviceBb-customerProfileBb ..... | 45 | +| 5.2.29 userData-customerProfileBb ..... | 45 | +| 5.2.30 uniAccess-managedElementR1 ..... | 45 | +| 5.2.31 vcCTPBidirectional-managedElementR1 ..... | 46 | +| 5.2.32 virtualPathGroup-nniAccess ..... | 46 | +| 5.2.33 xtpsgComb-managedElementR1 ..... | 46 | +| 5.3 Definition of packages ..... | 47 | +| 5.3.1 AAL type 1 performance parameter package
(aalTypeOnePerformanceParameterPkg) ..... | 47 | +| 5.3.2 AAL type 1 performance parameter history data package
(aalTypeOnePerformanceParameterHistoryDataPkg) ..... | 47 | +| 5.3.3 AAL type 1 profile package (aalTypeOneProfilePkg) ..... | 48 | +| 5.3.4 AAL type 3/4 performance parameter package
(aalTypeThreeFourPerformanceParameterPkg) ..... | 48 | +| 5.3.5 AAL type 3/4 performance parameter history data package
(aalTypeThreeFourPerformanceParameterHistoryDataPkg) ..... | 49 | +| 5.3.6 AAL type 3/4 profile package (aalTypeThreeFourProfilePkg) ..... | 50 | +| 5.3.7 AAL type 5 performance parameter package
(aalTypeFivePerformanceParameterPkg) ..... | 50 | + +| | Page | +|---------------------------------------------------------------------------------------------------------------------|-------------| +| 5.3.8 AAL type 5 performance parameter history data package
(aalTypeFivePerformanceParameterHistoryDataPkg)..... | 50 | +| 5.3.9 AAL type 5 profile package (aalTypeFiveProfilePkg) ..... | 50 | +| 5.3.10 Blocked for maintenance package (blockedForMaintenancePkg)..... | 51 | +| 5.3.11 Calling line identification presentation for broadband package (clipBbPkg). | 51 | +| 5.3.12 Calling line identification restriction for broadband package (clirBbPkg)..... | 51 | +| 5.3.13 Carrier data pointer package (carrierDataPtrPkg)..... | 51 | +| 5.3.14 Carrier parameter required package (carrierParameterRequiredPkg)..... | 51 | +| 5.3.15 Closed user group subscription option package for broadband
(cugSubscriptionOptionBbPkg)..... | 52 | +| 5.3.16 Connected line identification presentation for broadband package
(colpBbPkg)..... | 52 | +| 5.3.17 Connected line identification restriction for broadband package
(colrBbPkg)..... | 52 | +| 5.3.18 Customer profile pointers behaviour package
(customerProfilePointersBehPkg) ..... | 52 | +| 5.3.19 Customized resource pointers behaviour package
(customizedResourcePointersBehPkg)..... | 53 | +| 5.3.20 Destination code package (destinationCodePkg) ..... | 53 | +| 5.3.21 Destination type package (destinationTypePkg)..... | 53 | +| 5.3.22 Digit combination insertion package (digitCombInsertPkg) ..... | 53 | +| 5.3.23 Digit combination replace package (digitCombReplacePkg)..... | 53 | +| 5.3.24 Digit manipulation pointer package (digitManipPtrPkg) ..... | 54 | +| 5.3.25 Digit suppression package (digitSuppressPkg)..... | 54 | +| 5.3.26 Local area code package (localAreaCodePkg) ..... | 54 | +| 5.3.27 Maintenance signalling running package
(maintenanceSignallingRunningPkg)..... | 54 | +| 5.3.28 Maximum digits package (maxDigitsPkg) ..... | 54 | +| 5.3.29 Minimum digits package (minDigitsPkg) ..... | 54 | +| 5.3.30 Modify termination point list package (modifyTerminationPointListPkg) .... | 55 | +| 5.3.31 Network type package (networkTypePkg) ..... | 55 | +| 5.3.32 Origin mark package (originMarkPkg)..... | 55 | +| 5.3.33 Poll after retransmission package (pollAfterRetransmissionPkg) ..... | 55 | +| 5.3.34 Preferred carrier package (preferredCarrierPkg) ..... | 55 | +| 5.3.35 Propagation delay package (propagationDelayPkg) ..... | 55 | +| 5.3.36 Remote blocking package (remoteBlockingPkg) ..... | 56 | + +| | Page | +|----------------------------------------------------------------------------------------------|-------------| +| 5.3.37 Remote blocking narrowband package (remoteBlockingNbPkg) ..... | 56 | +| 5.3.38 Required narrowband transfer capability package
(reqNbTransferCapabilityPkg) ..... | 56 | +| 5.3.39 Ring time limit package (ringTimeLimitPkg) ..... | 56 | +| 5.3.40 Search method package (searchMethodPkg) ..... | 56 | +| 5.3.41 Send TNS package (sendTnsPkg) ..... | 56 | +| 5.3.42 Signalling channel pointer package (signallingChannelPtrPkg)..... | 57 | +| 5.3.43 Signalling type package (signallingTypePkg) ..... | 57 | +| 5.3.44 Sub-addressing for broadband package (subBbPkg) ..... | 57 | +| 5.3.45 Two calling party number delivery package
(twoCallingPartyNumberDeliveryPkg) ..... | 57 | +| 5.3.46 User to user signalling for broadband package
(userToUserSignallingBbPkg)..... | 57 | +| 5.4 Definition of attributes..... | 58 | +| 5.4.1 AAL mode (aalMode)..... | 58 | +| 5.4.2 AAL pointer (aalPtr)..... | 58 | +| 5.4.3 AAL profile identifier (aalProfileId) ..... | 58 | +| 5.4.4 AAL profile pointer (aalProfilePointer) ..... | 58 | +| 5.4.5 AAL type (aalType)..... | 58 | +| 5.4.6 Abstract destination identifier (abstractDestinationId)..... | 59 | +| 5.4.7 Abstract destination pointer (abstractDestinationPtr)..... | 59 | +| 5.4.8 Access pointer list (accessPtrList) ..... | 59 | +| 5.4.9 Active list of route termination points pointer (activeListOfRouteTpsPtr).... | 59 | +| 5.4.10 Active target pointer (activeTargetPtr) ..... | 60 | +| 5.4.11 Analysis criteria identifier (analysisCriteriaId)..... | 60 | +| 5.4.12 Assign non-assign (assignNonAssign) ..... | 60 | +| 5.4.13 B/E tag mismatch (bETagMismatch) ..... | 60 | +| 5.4.14 Blocked for maintenance (blockedForMaintenance)..... | 60 | +| 5.4.15 BOM/EOM unexpected MID (bomsEomsUnexpectedMID) ..... | 61 | +| 5.4.16 Buffer overflows (bufferOverflows)..... | 61 | +| 5.4.17 Buffer release (bufferRelease) ..... | 61 | +| 5.4.18 Buffer underflows (bufferUnderflows)..... | 61 | +| 5.4.19 Calling party category (callingPartyCategory)..... | 62 | +| 5.4.20 Called party number representation Type (cdpnRepresentationType) ..... | 62 | +| 5.4.21 Call routing circuit endpoint identifier (crCircuitEndPointId) ..... | 62 | + +| | Page | +|----------------------------------------------------------------------------------------------|------| +| 5.4.22 Call routing circuit endpoint subgroup identifier (crCircuitEndPointSubgroupId)..... | 62 | +| 5.4.23 Call routing office data identifier (callRoutingOfficeDataId) ..... | 63 | +| 5.4.24 Carrier code (carrierCode)..... | 63 | +| 5.4.25 Carrier data identifier (carrierDataId)..... | 63 | +| 5.4.26 Carrier data pointer (carrierDataPtr)..... | 63 | +| 5.4.27 CBR rate (cbrRate) ..... | 63 | +| 5.4.28 Cell loss (cellLoss) ..... | 64 | +| 5.4.29 Cell loss integration period (cellLossIntegrationPeriod) ..... | 64 | +| 5.4.30 Cell misinsertion (cellMisinsertion) ..... | 64 | +| 5.4.31 CES buffered CDV tolerance (cesBufferedCDVtolerance) ..... | 64 | +| 5.4.32 CES service profile identifier (cesServiceProfileId) ..... | 65 | +| 5.4.33 Channel associated signalling (channelAssociatedSignalling)..... | 65 | +| 5.4.34 CIP required (cipRequired)..... | 65 | +| 5.4.35 Circuit identification code (cic)..... | 65 | +| 5.4.36 Clock recovery type (clockRecoveryType)..... | 66 | +| 5.4.37 Closed user group barring (cugBarring) ..... | 66 | +| 5.4.38 Closed user group data network identification (cugDataNetworkIdentification)..... | 66 | +| 5.4.39 Closed user group index (cugIndex)..... | 66 | +| 5.4.40 Closed user group interlock code (cugInterlockCode) ..... | 67 | +| 5.4.41 Code (code)..... | 67 | +| 5.4.42 COM/EOM unexpected SN (comsEomsUnexpectedSN) ..... | 67 | +| 5.4.43 Connected line identification restriction options (connLineIdRestrictionOptions)..... | 67 | +| 5.4.44 Connected number screening identifier (connectedNumberScreeningId)..... | 68 | +| 5.4.45 Connection identification offering (connectionIdOffering)..... | 68 | +| 5.4.46 CRC violations (crcViolations) ..... | 68 | +| 5.4.47 CSP Required (cspRequired)..... | 68 | +| 5.4.48 Customer profile pointer (customerProfilePtr)..... | 68 | +| 5.4.49 Customized resource pointer list (customizedResourcePtrList)..... | 69 | +| 5.4.50 Default directory number (defaultDirectoryNumber)..... | 69 | +| 5.4.51 Destination code (destinationCode)..... | 69 | +| 5.4.52 Destination type (destinationType)..... | 69 | +| 5.4.53 Digit combination insertion (digitCombInsert) ..... | 69 | + +| | Page | +|------------------------------------------------------------------------------|-------------| +| 5.4.54 Digit combination replace (digitCombReplace)..... | 70 | +| 5.4.55 Digit manipulation identifier (digitManipId)..... | 70 | +| 5.4.56 Digit manipulation pointer (digitManipPtr) ..... | 70 | +| 5.4.57 Digit suppression (digitSuppress)..... | 70 | +| 5.4.58 Excluded subscriber codes (excludedSubscriberCodes) ..... | 70 | +| 5.4.59 Forward error correction method (forwardErrorCorrectionMethod)..... | 71 | +| 5.4.60 Header errors (headerErrors) ..... | 71 | +| 5.4.61 Initial subscriber codes (initialSubscriberCodes) ..... | 71 | +| 5.4.62 Inter closed user group access (interCugAccess)..... | 71 | +| 5.4.63 Length BA size mismatch (lengthBASizeMismatch)..... | 72 | +| 5.4.64 Length mismatch (lengthMismatch)..... | 72 | +| 5.4.65 Link group pointer (linkGroupPtr) ..... | 72 | +| 5.4.66 Link type (linkType)..... | 72 | +| 5.4.67 List of link groups pointer list (listOfLinkGroupsPtrList)..... | 72 | +| 5.4.68 List of routes pointer list (listOfRoutesPtrList) ..... | 73 | +| 5.4.69 List of route termination points identifier (listOfRouteTpsId) ..... | 73 | +| 5.4.70 Local area code (localAreaCode)..... | 73 | +| 5.4.71 Local destination identifier (localDestinationId)..... | 73 | +| 5.4.72 Local destination pointer (localDestinationPtr)..... | 74 | +| 5.4.73 Maintenance signalling running (maintenanceSignallingRunning)..... | 74 | +| 5.4.74 Maximun CC (maxCc) ..... | 74 | +| 5.4.75 Maximum CPCS_PDU size (maxCpcsPduSize)..... | 74 | +| 5.4.76 Maximum digits (maxDigits) ..... | 75 | +| 5.4.77 Maximum information field length (maxInformationFieldLength) ..... | 75 | +| 5.4.78 Maximum length of SSCOP user to user field (maxLengthSscopUuField)... | 75 | +| 5.4.79 Maximum PD (maxPd)..... | 75 | +| 5.4.80 Maximum SSCOP credit to peer (maxSscopCreditToPeer)..... | 75 | +| 5.4.81 Maximum STAT (maxStat)..... | 76 | +| 5.4.82 MID range (midRange)..... | 76 | +| 5.4.83 Minimum digits (minDigits)..... | 76 | +| 5.4.84 Nature of address (natureOfAddress) ..... | 76 | +| 5.4.85 Network border (networkBorder) ..... | 77 | + +| | Page | +|---------------------------------------------------------------------------------------------------------------|-------------| +| 5.4.86 Network type (networkType)..... | 77 | +| 5.4.87 NNI access identifier (nniAccessId) ..... | 77 | +| 5.4.88 No connected line identification presentation restrictions allowed
(noColpRestrictionsAllowed)..... | 77 | +| 5.4.89 Number of aborts (numberOfAborts) ..... | 78 | +| 5.4.90 Origin (origin)..... | 78 | +| 5.4.91 Origin for routing (originForRouting) ..... | 78 | +| 5.4.92 Origin mark (originMark)..... | 78 | +| 5.4.93 Own international code (ownInternationalCode) ..... | 79 | +| 5.4.94 Partially filled cells (partiallyFilledCells)..... | 79 | +| 5.4.95 Poll after retransmission (pollAfterRetransmission) ..... | 79 | +| 5.4.96 Post analysis evaluation identifier (postAnalysisEvaluationId) ..... | 79 | +| 5.4.97 Preferred carrier (preferredCarrier)..... | 79 | +| 5.4.98 Preferred closed user group index (preferredCugIndex) ..... | 80 | +| 5.4.99 Prefix digit analysis identifier (prefixDigitAnalysisId) ..... | 80 | +| 5.4.100 Propagation delay (propagationDelay) ..... | 80 | +| 5.4.101 Reassembly timer expirations (reassemblyTimerExpirations) ..... | 80 | +| 5.4.102 Remote blocking (remoteBlocking) ..... | 80 | +| 5.4.103 Remote blocking reason (remoteBlockingReason) ..... | 81 | +| 5.4.104 Required bandwidth egress (reqBandwidthEgress)..... | 81 | +| 5.4.105 Required bandwidth ingress (reqBandwidthIngress)..... | 81 | +| 5.4.106 Required bearer capability (reqBearerCapab)..... | 81 | +| 5.4.107 Required narrowband transfer capability (reqNbTransferCapability) ..... | 82 | +| 5.4.108 Ring time limit (ringTimeLimit) ..... | 82 | +| 5.4.109 Route data identifier (routeDataId)..... | 82 | +| 5.4.110 SAAL UNI protocol profile identifier (saalUniProtocolProfileId)..... | 82 | +| 5.4.111 SAR CRC violations (sarCrcViolations)..... | 82 | +| 5.4.112 Screen number (screenNumber) ..... | 83 | +| 5.4.113 Search method (searchMethod) ..... | 83 | +| 5.4.114 Sends TNS (sendTns) ..... | 84 | +| 5.4.115 Sequence violations (sequenceViolations) ..... | 84 | +| 5.4.116 Service profile pointer (serviceProfilePointer) ..... | 84 | +| 5.4.117 Signalling channel pointer (signallingChannelPtr)..... | 84 | +| 5.4.118 Signalling protocol (signallingProtocol)..... | 85 | +| 5.4.119 Signalling route pointer (sigRoutePtr)..... | 85 | +| 5.4.120 Signalling standard (signallingStandard)..... | 85 | + +| | Page | +|------------------------------------------------------------------------------------------------------------------|-------------| +| 5.4.121 Signalling type (signallingType)..... | 85 | +| 5.4.122 SRI timeouts (sriTimeOuts)..... | 85 | +| 5.4.123 SSCOP timer CC (sscopTimerCc) ..... | 86 | +| 5.4.124 SSCOP timer idle (sscopTimerIdle)..... | 86 | +| 5.4.125 SSCOP timer keep alive (sscopTimerKeepAlive)..... | 86 | +| 5.4.126 SSCOP timer no response (sscopTimerNoResponse)..... | 86 | +| 5.4.127 SSCOP timer poll (sscopTimerPoll) ..... | 87 | +| 5.4.128 SSCS type (sscsType)..... | 87 | +| 5.4.129 STD pointer parity failures (stdPointerParityFailures)..... | 87 | +| 5.4.130 STD pointer reframes (stdPointerReframes) ..... | 87 | +| 5.4.131 Structured data transfer (structuredDataTransfer) ..... | 88 | +| 5.4.132 Subscriber category (subscriberCategory) ..... | 88 | +| 5.4.133 Subtype (subType)..... | 88 | +| 5.4.134 Sum of incorrect CS field errors (sumOfIncorrectCSFieldErrors) ..... | 88 | +| 5.4.135 Sum of incorrect SAR field errors (sumOfIncorrectSARFieldErrors) ..... | 89 | +| 5.4.136 Sum of invalid CS field errors (sumOfInvalidCSFieldErrors) ..... | 89 | +| 5.4.137 Sum of invalid SAR field errors (sumOfInvalidSARFieldErrors) ..... | 89 | +| 5.4.138 Supplementary service independent for broadband pointer list
(supplementaryServiceIndBbPtrList) ..... | 89 | +| 5.4.139 Termination point and VPCI pointer list (tpAndVpciPtrList)..... | 90 | +| 5.4.140 Termination point and VPCI Signalling Pointer List (tpAndVpciSigPtrList) | 90 | +| 5.4.141 Termination point list (terminationPointList)..... | 90 | +| 5.4.142 Timeslot pointer (timeslotPtr) ..... | 91 | +| 5.4.143 Timing relation (timingRelation)..... | 91 | +| 5.4.144 Transit delay limit (transitDelayLimit)..... | 91 | +| 5.4.145 Two calling party number delivery (twoCallingPartyNumberDelivery) ..... | 91 | +| 5.4.146 UNI access identifier (uniAccessId) ..... | 91 | +| 5.4.147 Used algorithm (usedAlgorithm)..... | 92 | +| 5.4.148 User data identifier (userDataId) ..... | 92 | +| 5.4.149 User data pointer (userDataPtr) ..... | 92 | +| 5.4.150 Virtual path group identifier (virtualPathGroupId) ..... | 92 | +| 5.4.151 Virtual path type (vpType)..... | 92 | +| 5.4.152 XTPSG combination identifier (xtpsgCombId)..... | 93 | + +| | Page | | +|---------------------------------------------------|---------------------------------------------------------|-----| +| 5.5 | Definition of actions ..... | 93 | +| 5.5.1 | Add termination point (addTerminationPoint) ..... | 93 | +| 5.5.2 | Remove termination point (removeTerminationPoint) ..... | 93 | +| 5.6 | Definition of behaviour..... | 94 | +| 5.6.1 | Set by manager behaviour (setByManagerBeh) ..... | 94 | +| 6 | Type Definitions ..... | 94 | +| 7 | Protocol stacks ..... | 101 | +| ANNEX A – Management requirements ..... | | 102 | +| A.1 | Configuration management functions..... | 102 | +| A.1.1 | General NE configuration functions..... | 102 | +| A.1.2 | ATM transport layer configuration functions..... | 102 | +| A.1.3 | ATM adaptation layer configuration functions ..... | 103 | +| A.1.4 | Broadband signalling configuration functions..... | 103 | +| A.2 | Performance management functions..... | 103 | +| A.2.1 | General NE performance functions ..... | 104 | +| A.2.2 | ATM transport layer performance functions ..... | 104 | +| A.2.3 | ATM adaptation layer performance functions..... | 105 | +| A.3 | Fault management functions ..... | 106 | +| A.3.1 | Alarm surveillance..... | 106 | +| A.3.2 | Test and fault localisation..... | 107 | +| A.3.3 | Fault correction..... | 107 | +| A.4 | Modelling specific requirements..... | 108 | +| APPENDIX I – Point-to-multipoint connections..... | | 108 | +| APPENDIX II – Bibliography..... | | 108 | + + + +**STAGE 2 AND STAGE 3 DESCRIPTION FOR THE Q3 INTERFACE – +CUSTOMER ADMINISTRATION: BROADBAND SWITCH MANAGEMENT** + +*(Geneva, 1998)* + +## **1 Introduction** + +### **1.1 Purpose and Scope** + +This Recommendation specifies the Q3 interface between an ATM switch and the Telecommunications Management Network (TMN). The interface specified is that between TMN Network Elements or Q-Adapters which interface to TMN Operations Systems (OSs) without mediation and between OSs and Mediation Devices, as defined in Recommendation M.3010 [5]. + +The configuration by management of channels for signalling, including those for B-ISDN signalling, is within the scope of this Recommendation. The management of broadband customer administration and the configuration for call routing, including that for interworking with narrowband switches for both incoming and outgoing interfaces, is also within the scope of this Recommendation. + +An ATM switch may include ATM cross-connect functionality, but this is specified by reference to the ITU-T Recommendation on ATM network elements [4] and by importing the relevant classes of managed objects where appropriate. + +Existing protocols are used where possible, and the focus of the work is on defining the object model. The definition of the functionality of TMN Operations Systems is outside the scope of this Recommendation. + +Security management is also outside the scope of this Recommendation. + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; 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.311 (1996), *B-ISDN general network aspects*. +- [2] ITU-T Recommendation I.363.5 (1996), *B-ISDN ATM adaptation layer specification: Type 5 AAL*. +- [3] ITU-T Recommendation I.610 (1995), *B-ISDN operation and maintenance principles and functions*. + +- [4] ITU-T Recommendation I.751 (1996), *Asynchronous transfer mode management of the network element view.* +- [5] ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network.* +- [6] ITU-T Recommendation M.3100 (1995), *Generic network information model.* +- [7] ITU-T Recommendation Q.2110 (1994), *B-ISDN ATM adaptation layer – Service Specific Connection Oriented Protocol (SSCOP).* +- [8] ITU-T Recommendation Q.2130 (1994), *B-ISDN ATM adaptation layer – Service Specific Coordination Function for the Support of Signalling at the User-Network Interface (SSFC at UNI).* +- [9] ITU-T Recommendation Q.2140 (1995), *B-ISDN ATM adaptation layer – Service Specific Coordination Function for the Support of Signalling at the Network Node Interface (SSFC at NNI).* +- [10] ITU-T Recommendations Q.2761 (1995), Q.2762 (1995), Q.2763 (1995), Q.2764 (1995), *A group of Recommendations on B-ISDN – User Part (B-ISUP) of Signalling System No. 7.* +- [11] ITU-T Recommendation Q.2931 (1995), *Digital Subscriber Signalling System No. 2 (DSS 2) – User-Network Interface (UNI) layer 3 specification for basic call/connection control.* +- [12] CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, *Information technology – Open Systems Interconnection – Structure of management information: Management information model.* +- [13] CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- [14] CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2:1992, *Information technology – Open Systems Interconnection – Systems management: State management function.* +- [15] CCITT Recommendation X.732 (1992) | ISO/IEC 10164-3:1992, *Information technology – Open Systems Interconnection – Systems management: Attributes for representing relationships.* +- [16] ITU-T Recommendation Q.821 (1993), *Stage 2 and stage 3 description for the Q3 interface – Alarm surveillance.* +- [17] ATM Forum Specification af-nm-0027.000 (1995), *CMIP Specification for the MA Interface.* + +### 3 Definitions, abbreviations and conventions + +#### 3.1 Definitions + +This Recommendation defines the following terms: + +**3.1.1 permanent VCC:** A permanent VCC is a virtual circuit connection which is established by configuration management, not by on-demand call control. + +- 3.1.2 virtual channel trail:** This corresponds to a VCC in standard ATM terminology. +- 3.1.3 virtual channel trail termination point:** This corresponds to the end point of a VCC and marks the extremity of an end-to-end F5 OAM flow. +- 3.1.4 virtual channel connection termination point:** This corresponds to an intermediate point of a VCC and may mark the extremity of a segment F5 OAM flow. +- 3.1.5 virtual path trail:** This corresponds to a VPC in standard ATM terminology. +- 3.1.6 virtual path trail termination point:** This corresponds to the end point of a VPC and marks the extremity of an end-to-end F4 OAM flow. +- 3.1.7 virtual path connection termination point:** This corresponds to an intermediate point of a VPC and may mark the extremity of a segment F4 OAM flow. + +In addition, this Recommendation uses terms defined in ITU-T Recommendations: + +**F4 OAM flow:** See Recommendation I.610 [3]. + +**F5 OAM flow:** See Recommendation I.610 [3]. + +**Trail Termination Point:** See Recommendation M.3100 [6]. + +**Virtual Channel:** See Recommendation I.311 [1]. + +**Virtual Channel Connection:** See Recommendation I.311 [1]. + +**Virtual Path:** See Recommendation I.311 [1]. + +**Virtual Path Connection:** See Recommendation I.311 [1]. + +## **3.2 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-----|----------------------------| +| NNI | Network-Network Interface | +| TTP | Trail Termination Point | +| UNI | User-Network Interface | +| VC | Virtual Channel | +| VCC | Virtual Channel Connection | +| VP | Virtual Path | +| VPC | Virtual Path Connection | + +### 3.3 Conventions + +Objects and their characteristics and associated ASN.1 defined here are given names with capitals used to indicate the start of the next word and acronyms are treated as if they were words. + +Throughout this Recommendation, all new attributes are named according to the following guidelines: + +- The name of an attribute ends in the string "Ptr" if and only if the attribute value is intended to identify a single object. +- The name of an attribute ends in the string "PtrList" if and only if the attribute value is intended to identify one or more objects. +- The name of an attribute is composed of the name of an object class followed by the string "Ptr" if and only if the attribute value is intended to identify a specific object class. +- If an attribute is intended to identify different object classes, a descriptive name is given to that attribute and a description is provided in the attribute behaviour. +- The name of an attribute ends in the string "Id" if and only if the attribute value is intended to identify the name of an object, in which case this attribute should be the first one listed, should use ASN.1 NameType and should not be used to convey other information. +- The name of an attribute is composed of the name of an object class followed by the string "Id" if and only if the attribute value is intended to identify the name of the object class holding that attribute. + +## 4 General overview + +The following information model diagrams have been drawn for the purpose of clarifying the relations between the different object classes of the model. + +- 1) Entity Relationship Models showing the relations of the different managed objects; +- 2) Inheritance Hierarchy showing how managed objects are derived from each other (i.e. the different paths of inherited characteristics of the different managed objects). + +These diagrams are only for clarification. The formal specification in terms of GDMO templates and ASN.1 type definitions are the relevant information for implementations. + +## 4.1 Entity Relationship Models + +The following conventions are used in the diagrams: + +![Conventions used in diagrams for Entity Relationship Models. The diagram shows various symbols: 'c' for containment, 'a' for association, 'i' for inheritance, '1:1' and '1:N' for cardinality, arrows for directionality, 'moc' for managed object class, a dashed box for uninstantiable object class, and a shaded box for managed object class outside the actual fragment.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +The diagram illustrates the following conventions: + +- c**: is contained in +- a**: is associated with +- i**: 'is-a' relation (inheritance) +- 1 : 1**: cardinality (represented by a double line with 'X' marks at both ends) +- 1 : N**: cardinality (represented by a line with an 'X' mark at one end and an arrow at the other) +- unidirectional**: relationship direction (represented by a line with an arrow) +- bidirectional**: relationship direction (represented by a line with arrows at both ends) +- moc**: managed object class (represented by a solid box) +- moc** (dashed box): uninstantiable object class (superclass) +- moc** (shaded box): managed object class outside the actual fragment + +T0409530-98/d01 + +Conventions used in diagrams for Entity Relationship Models. The diagram shows various symbols: 'c' for containment, 'a' for association, 'i' for inheritance, '1:1' and '1:N' for cardinality, arrows for directionality, 'moc' for managed object class, a dashed box for uninstantiable object class, and a shaded box for managed object class outside the actual fragment. + +**Figure 1/Q.824.6 – Conventions used in diagrams for Entity Relationship Models** + +Where the directionality of containment is not clear it can be identified by implications since the root class is unique. + +ATM switching network elements are represented by instances of the class atmSwitch and this contains, either directly or indirectly, all other managed objects which represent parts of the ATM switch. + +### 4.1.1 ATM generic modelling + +Modelling of ATM is restricted to bidirectional trails so that there is always a backwards channel for OAM purposes. + +The interfaces to the ATM switching network element consist of User-Network Interfaces (UNIs), which are labelled by instances of the class uni, and of Network-Network Interfaces (NNIs) which are labelled by instances of the class intraNNI if the interface is to the same network operator as the network element or by instances of the class interNNI if the interface is to a different network operator. The managed objects which label the interfaces are contained in the instance of managedElementR1 which represents the ATM switch and point to an instance of tcAdaptorTTPBidirectional class which represents the adaptation of the ATM layer to the underlying physical infrastructure. + +![Entity Relationship Model – ATM interfaces diagram showing relationships between managedElementR1, interNNI, tcAdaptorTTPBidirectional, atmAccessProfile, vpCTPBidirectional, vpTTPBidirectional, vcCTPBidirectional, and vcTTPBidirectional.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + + graph TD + ME[managedElementR1] -- c --> C1[c] + C1 --> NNI[interNNI +intraNNI +or UNI] + C1 --> TC[tcAdaptorTTP +Bidirectional] + C1 --> VP_TTP[vpTTP +Bidirectional] + C1 --> VC_TTP[vcTTP +Bidirectional] + + NNI -- a --> TC + TC -- c --> C2[c] + C2 --> AAP1[atm +Access +Profile] + C2 --> VP_CTP[vpCTP +Bidirectional] + + VP_CTP -- a --> VP_TTP + + VP_TTP -- c --> C3[c] + C3 --> AAP2[atm +Access +Profile] + C3 --> VC_CTP[vcCTP +Bidirectional] + + VC_CTP -- a --> VC_TTP + +``` + +The diagram illustrates the Entity Relationship Model for ATM interfaces. At the top is a box labeled 'managedElementR1'. A line descends to a containment box 'c', which branches out to 'interNNI/intraNNI or UNI', 'tcAdaptorTTP Bidirectional', 'vpTTP Bidirectional', and 'vcTTP Bidirectional'. The 'interNNI' box has an association 'a' with 'tcAdaptorTTP Bidirectional'. The 'tcAdaptorTTP Bidirectional' box contains (via 'c') an 'atm Access Profile' and 'vpCTP Bidirectional'. The 'vpCTP Bidirectional' has an association 'a' with 'vpTTP Bidirectional'. The 'vpTTP Bidirectional' contains (via 'c') another 'atm Access Profile' and 'vcCTP Bidirectional'. Finally, 'vcCTP Bidirectional' has an association 'a' with 'vcTTP Bidirectional'. A reference number 'T0409540-98/d02' is at the bottom right. + +Entity Relationship Model – ATM interfaces diagram showing relationships between managedElementR1, interNNI, tcAdaptorTTPBidirectional, atmAccessProfile, vpCTPBidirectional, vpTTPBidirectional, vcCTPBidirectional, and vcTTPBidirectional. + +**Figure 2/Q.824.6 – Entity Relationship Model – ATM interfaces** + +Instances of tcAdaptorTTPBidirectional are contained in the instance of managedElementR1. The adaptation to a physical infrastructure, represented by an instance of tcAdaptorTTPBidirectional, serves a number of virtual path trails which pass through the associated interface. The intermediate points on these trails which are served by the adaptation are represented by instances of vpCTPBidirectional class which are contained in the instance of tcAdaptorTTPBidirectional. The instance of tcAdaptorTTPBidirectional may also contain an instance of atmAccessProfile which characterizes the virtual paths. + +An instance of atmAccessProfile may also be contained in an instance of vpTTPBidirectional, which represents the end point of virtual path trail, to characterize the virtual channels served by the virtual path trail. The intermediate points of the virtual channel trails are represented by instances of vcCTPBidirectional which are contained in the instance of vpTTPBidirectional. The end points of the virtual channel trails are represented by instances of vcTTPBidirectional. Instances of vpTTPBidirectional and of vcTTPBidirectional are contained in the instance of managedElementR1. + +End points of virtual path trails (vpTTPBidirectional) must be directly associated with intermediate points (vpCTPBidirectional) using reciprocal upstream and downstream pointers. These pointers must also be used to associate the end points of virtual connections trails (vcTTPBidirectional) with their intermediate points (vcCTPBidirectional). A flexible cross-connection of two intermediate points at the same virtual level (either path or channel) is represented by an instance of atmCrossConnection. These instances are contained in an instance of atmFabric which represents the management of the cross-connection functionality and which is contained in the instance of managedElementR1. The upstream and downstream pointers may be used to associate a CTP object with a TTP object, or to associate CTP objects in a cross-connection, but not both simultaneously. + +![Diagram of VP cross-connection instantiation. At the top is 'managed ElementR1' connected via a 'c' (concatenation) node to a horizontal bus. Below the bus are three nodes: 'tcAdaptorTTP Bidirectional', 'atmFabric', and 'tcAdaptorTTP Bidirectional'. Each of these is connected via a 'c' node to a 'vpCTP Bidirectional' node. The two 'vpCTP Bidirectional' nodes are connected to a central 'atmCross Connection' node via 'a' (adaptation) nodes. The 'atmCross Connection' node is also connected to the 'atmFabric' node via a 'c' node. A reference 'T0409550-98/d03' is at the bottom right.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Diagram of VP cross-connection instantiation. At the top is 'managed ElementR1' connected via a 'c' (concatenation) node to a horizontal bus. Below the bus are three nodes: 'tcAdaptorTTP Bidirectional', 'atmFabric', and 'tcAdaptorTTP Bidirectional'. Each of these is connected via a 'c' node to a 'vpCTP Bidirectional' node. The two 'vpCTP Bidirectional' nodes are connected to a central 'atmCross Connection' node via 'a' (adaptation) nodes. The 'atmCross Connection' node is also connected to the 'atmFabric' node via a 'c' node. A reference 'T0409550-98/d03' is at the bottom right. + +Figure 3/Q.824.6 – Instantiation example – VP cross-connection + +![Diagram of VC cross-connection instantiation. At the top is 'managed ElementR1' connected via a 'c' node to a horizontal bus. Below the bus are four nodes: 'vpTTP Bidirectional', 'tcAdaptorTTP Bidirectional', 'atmFabric', and 'tcAdaptorTTP Bidirectional'. The 'vpTTP Bidirectional' nodes are connected to 'vpCTP Bidirectional' nodes via 'a' nodes. The 'vpCTP Bidirectional' nodes are connected to 'vcCTP Bidirectional' nodes via 'c' nodes. The 'vcCTP Bidirectional' nodes are connected to a central 'atmCross Connection' node via 'a' nodes. The 'atmCross Connection' node is also connected to the 'atmFabric' node via a 'c' node. A reference 'T0409560-98/d04' is at the bottom right.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Diagram of VC cross-connection instantiation. At the top is 'managed ElementR1' connected via a 'c' node to a horizontal bus. Below the bus are four nodes: 'vpTTP Bidirectional', 'tcAdaptorTTP Bidirectional', 'atmFabric', and 'tcAdaptorTTP Bidirectional'. The 'vpTTP Bidirectional' nodes are connected to 'vpCTP Bidirectional' nodes via 'a' nodes. The 'vpCTP Bidirectional' nodes are connected to 'vcCTP Bidirectional' nodes via 'c' nodes. The 'vcCTP Bidirectional' nodes are connected to a central 'atmCross Connection' node via 'a' nodes. The 'atmCross Connection' node is also connected to the 'atmFabric' node via a 'c' node. A reference 'T0409560-98/d04' is at the bottom right. + +Figure 4/Q.824.6 – Instantiation example – VC cross-connection + +Performance monitoring and continuity monitoring using OAM flows is modelled by instances of bidirectionalPerformanceMonitor and bidirectionalContinuityMonitor which are contained within the appropriate end points or intermediate points of the virtual path trails or virtual connection trails + +(vpTTPBidirectional, vpCTPBidirectional, vcTTPBidirectional or vcCTPBidirectional). Loopback and alarm OAM flows are handled directly by the instances which represent the end points or intermediate points. ATM cell header abnormalities are recorded as instances of cellHeaderAbnormalityLogRecord which are contain in an instance of log which is contained in the instance of atmSwitch. + +![Entity relationship diagram – ATM fault and performance management](08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg) + +``` + + graph TD + subgraph TopLeft + A1[interNNI, intraNNI or UNI] -- c --> B1[atmTrafficLoad CurrentData] + A1 -- c --> B2[cellLevelProtocol CurrentData] + B1 -- c --> C1[atmTrafficLoad HistoryData] + B2 -- c --> C2[cellLevelProtocol HistoryData] + end + + subgraph TopRight + A2[vpTTPBidirectional or vcTTPBidirectional] -- c --> B3[bidirectional Performance Monitor] + A2 -- c --> B4[bidirectional Continuity Monitor] + B3 -- c --> C3[vpVcPM CurrentData] + C3 -- c --> D1[vpVcPM HistoryData] + end + + subgraph BottomLeft + A3[tcAdaptorTTP Bidirectional] -- c --> B5[tcAdaptor CurrentData] + B5 -- c --> C4[tcAdaptor HistoryData] + end + + subgraph BottomRight + A4[vpCTPBidirectional or vcCTPBidirectional] -- c --> B6[atmTrafficLoad CurrentData] + A4 -- c --> B7[upcNpc CurrentData] + A4 -- c --> B8[bidirectional Performance Monitor] + A4 -- c --> B9[bidirectional Continuity Monitor] + B6 -- c --> C5[atmTrafficLoad HistoryData] + B7 -- c --> C6[upcNpc HistoryData] + B8 -- c --> C7[vpVcPM CurrentData] + C7 -- c --> D2[vpVcPM HistoryData] + end + +``` + +T0409570-98/d05 + +Entity relationship diagram – ATM fault and performance management + +**Figure 5/Q.824.6 – Entity relationship diagram – ATM fault and performance management** + +8          **Recommendation Q.824.6 (06/98)** + +Statistical information which is currently being gathered is represented by currentData objects and that which has been previously gathered is represented by historyData objects. The historyData objects are contained in the currentData objects which are contained in the managed object which represents the source of the statistical information. The statistics for the number of incoming and outgoing cells are represented by instances of atmTrafficLoadCurrentData and atmTrafficLoadHistoryData contained (directly or indirectly) in the managed objects which represent the interfaces or represent intermediate points on trails. Statistics on discarded cells are represented by instances of cellLevelProtocolCurrentData and cellLevelProtocolHistoryData contained (directly or indirectly) in the managed objects which represent the interfaces. Statistics on header errors are represented by instances of tcAdaptorCurrentData and tcAdaptorHistoryData contained (directly or indirectly) in tcAdaptorTTP which represents the adaptation function. Statistics on the policing of traffic in accordance with traffic descriptors are represented by instances of upcNpcCurrentData and upcNpcHistoryData contained (directly or indirectly) in the managed objects which represent the interfaces or represent intermediate points on trails. Statistics collected through F4 and F5 performance monitoring flows are represented by instances of vpVcPMCurrentData and vpVcPMHistoryData which are contained (directly or indirectly) in the managed objects which represent the modelling of performance monitoring by OAM flows. + +#### 4.1.2 ATM interworking and adaptation layer modelling + +![Entity relationship diagram for ATM interworking and adaptation layer modelling. The diagram shows a central 'interworkingVCTTP Bidirectional' object connected to various other objects. At the top, it connects via a 'c' relationship to a 'managedElementR1' object. To the left, it connects via an 'a' relationship to an 'interworked TP class' object. To the right, it connects via 'a' relationships to 'aalProfile' and 'cesServiceProfile' objects, and via a double-headed 'a' relationship to a 'vcCTP Bidirectional' object. Below the central object, it connects via a 'c' relationship to an 'aalProtocol CurrentData' object, which in turn connects via a 'c' relationship to an 'aalProtocol HistoryData' object. Arrows indicate the direction of the relationships, with some being bidirectional. A label 'T0409580-98/d06' is present near the bottom right.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +``` + +graph TD + managedElementR1[managedElementR1] + interworkedTPclass[interworked TP class] + interworkingVCTTP[interworkingVCTTP Bidirectional] + aalProfile[aalProfile] + cesServiceProfile[cesServiceProfile] + vcCTPBidirectional[vcCTP Bidirectional] + aalProtocolCurrentData[aalProtocol CurrentData] + aalProtocolHistoryData[aalProtocol HistoryData] + + managedElementR1 -- c --> interworkingVCTTP + interworkedTPclass -- a --> interworkingVCTTP + interworkingVCTTP -- a --> aalProfile + interworkingVCTTP -- a --> cesServiceProfile + interworkingVCTTP <-- a --> vcCTPBidirectional + interworkingVCTTP -- c --> aalProtocolCurrentData + aalProtocolCurrentData -- c --> aalProtocolHistoryData + T0409580-98/d06[T0409580-98/d06] + +``` + +Entity relationship diagram for ATM interworking and adaptation layer modelling. The diagram shows a central 'interworkingVCTTP Bidirectional' object connected to various other objects. At the top, it connects via a 'c' relationship to a 'managedElementR1' object. To the left, it connects via an 'a' relationship to an 'interworked TP class' object. To the right, it connects via 'a' relationships to 'aalProfile' and 'cesServiceProfile' objects, and via a double-headed 'a' relationship to a 'vcCTP Bidirectional' object. Below the central object, it connects via a 'c' relationship to an 'aalProtocol CurrentData' object, which in turn connects via a 'c' relationship to an 'aalProtocol HistoryData' object. Arrows indicate the direction of the relationships, with some being bidirectional. A label 'T0409580-98/d06' is present near the bottom right. + +Figure 6/Q.824.6 – Entity relationship diagram – ATM interworking and adaptation layer modelling + +### 4.1.3 Broadband customer administration modelling + +![Entity relationship diagram for Broadband customer administration modelling. The diagram shows a central 'managed ElementR1' connected to 'directory Number E164Bb', 'customer ProfileBb', and 'uni Access'. 'customer ProfileBb' is linked to 'supplementary Service IndependentBb', 'bearer ServiceBb', and 'tele ServiceBb'. 'uni Access' is linked to 'sVpTTP', 'vcTTP Bidirectional', and 'saalUni ProtocolProfile'. 'supplementary Service IndependentBb' is linked to 'customized ResourceBb' and 'directDiallingIn IndBb'. 'bearer ServiceBb' is linked to 'dbr', 'sbr', 'abr', 'ubr', 'abtDt', and 'abtIt'. 'tele ServiceBb' is linked to 'supplementary Service DependentBb', which includes 'cLIPDepBb', 'cLIRDepBb', 'cOLPDepBb', 'cOLRDepBb', 'sUBDepBb', 'userToUser SignallingDepBb', and 'cUGSubscription OptionDepBb'. 'customized ResourceBb' is linked to 'calling Number ScreeningBb' and 'connected Number ScreeningBb'.](73b5cce955ba9415a98791db7b0080ad_img.jpg) + +The diagram illustrates the Broadband customer administration modelling. At the top, a grey box labeled 'managed ElementR1' is connected via a 'c' relationship to a horizontal line. This line branches to 'directory Number E164Bb', 'customer ProfileBb', and 'uni Access'. 'customer ProfileBb' is connected to 'supplementary Service IndependentBb', 'bearer ServiceBb', and 'tele ServiceBb' via 'c' relationships. 'uni Access' is connected to 'sVpTTP', 'vcTTP Bidirectional', and 'saalUni ProtocolProfile' via 'a' relationships. 'supplementary Service IndependentBb' is connected to 'customized ResourceBb' and 'directDiallingIn IndBb' via 'a' relationships. 'bearer ServiceBb' is connected to a list of service types: 'dbr', 'sbr', 'abr', 'ubr', 'abtDt', and 'abtIt' via 'i' relationships. 'tele ServiceBb' is connected to 'supplementary Service DependentBb' via 'c' relationships. 'supplementary Service DependentBb' includes a list of service types: 'cLIPDepBb', 'cLIRDepBb', 'cOLPDepBb', 'cOLRDepBb', 'sUBDepBb', 'userToUser SignallingDepBb', and 'cUGSubscription OptionDepBb' via 'i' relationships. 'customized ResourceBb' is connected to 'calling Number ScreeningBb' and 'connected Number ScreeningBb' via 'a' relationships. + +Entity relationship diagram for Broadband customer administration modelling. The diagram shows a central 'managed ElementR1' connected to 'directory Number E164Bb', 'customer ProfileBb', and 'uni Access'. 'customer ProfileBb' is linked to 'supplementary Service IndependentBb', 'bearer ServiceBb', and 'tele ServiceBb'. 'uni Access' is linked to 'sVpTTP', 'vcTTP Bidirectional', and 'saalUni ProtocolProfile'. 'supplementary Service IndependentBb' is linked to 'customized ResourceBb' and 'directDiallingIn IndBb'. 'bearer ServiceBb' is linked to 'dbr', 'sbr', 'abr', 'ubr', 'abtDt', and 'abtIt'. 'tele ServiceBb' is linked to 'supplementary Service DependentBb', which includes 'cLIPDepBb', 'cLIRDepBb', 'cOLPDepBb', 'cOLRDepBb', 'sUBDepBb', 'userToUser SignallingDepBb', and 'cUGSubscription OptionDepBb'. 'customized ResourceBb' is linked to 'calling Number ScreeningBb' and 'connected Number ScreeningBb'. + +T0409590-98/d07 + +Figure 7/Q.824.6 – Entity relationship diagram – Broadband customer administration + +#### 4.1.4 Broadband routing modelling + +all object classes beside virtualPathGroup, crCircuitEndPointSubgroup and crCircuitEndPoint are contained in managedElementR1 + +![Entity relationship diagram for Broadband call routing management. The diagram shows a hierarchy of object classes. At the top is 'analysis Criteria', which has a 1..* relationship with 'carrier Data' (multiplicity 'a'). 'analysis Criteria' also has a 1..* relationship with 'abstract Destination'. 'abstract Destination' is a superclass for 'local Destination' and 'digit Manip'. 'local Destination' has a 1..* relationship with 'analysis Criteria' (multiplicity 'a'). 'digit Manip' has a 1..* relationship with 'analysis Criteria' (multiplicity 'a'). 'analysis Criteria' also has a 1..* relationship with 'post Analysis Evaluation'. 'post Analysis Evaluation' has a 1..* relationship with 'listOf RouteTps'. 'listOf RouteTps' has a 1..* relationship with 'route Data'. 'route Data' has a 1..* relationship with 'xtpsg Comb'. 'xtpsg Comb' has a 1..* relationship with 'crCircuit EndPoint Subgroup' (multiplicity 'a'). 'crCircuit EndPoint Subgroup' has a 1..* relationship with 'crCircuit EndPoint'. 'crCircuit EndPoint' has a 1..* relationship with 'e0CTP/ds0CTP' (multiplicity 'a'). 'crCircuit EndPoint Subgroup' also has a 1..* relationship with 'virtual Path Group'. 'virtual Path Group' has a 1..* relationship with 'sVpTTP' (multiplicity 'a'). 'virtual Path Group' also has a 1..* relationship with 'nni Access'. 'nni Access' has a 1..* relationship with 'signRoute SetNePart' (multiplicity 'a'). 'analysis Criteria' also has a 1..* relationship with 'prefix Digit Analysis' and 'callRouting Office Data'.](552265bdbcf6d43d341fd018a9076269_img.jpg) + +``` + +classDiagram + analysisCriteria[analysis Criteria] "1..*" -- "1..*" carrierData[carrier Data] : a + analysisCriteria "1..*" -- "1..*" abstractDestination[abstract Destination] + abstractDestination <|-- localDestination[local Destination] + abstractDestination <|-- digitManip[digit Manip] + localDestination "1..*" -- "1..*" analysisCriteria : a + digitManip "1..*" -- "1..*" analysisCriteria : a + analysisCriteria "1..*" -- "1..*" postAnalysisEvaluation[post Analysis Evaluation] + postAnalysisEvaluation "1..*" -- "1..*" listOfRouteTps[listOf RouteTps] + listOfRouteTps "1..*" -- "1..*" routeData[route Data] + routeData "1..*" -- "1..*" xtpsgComb[xtpsg Comb] + xtpsgComb "1..*" -- "1..*" crCircuitEndPointSubgroup[crCircuit EndPoint Subgroup] : a + crCircuitEndPointSubgroup "1..*" -- "1..*" crCircuitEndPoint[crCircuit EndPoint] + crCircuitEndPoint "1..*" -- "1..*" e0CTPds0CTP[e0CTP/ds0CTP] : a + crCircuitEndPointSubgroup "1..*" -- "1..*" virtualPathGroup[virtual Path Group] + virtualPathGroup "1..*" -- "1..*" sVpTTP[sVpTTP] : a + virtualPathGroup "1..*" -- "1..*" nniAccess[nni Access] + nniAccess "1..*" -- "1..*" signRouteSetNePart[signRoute SetNePart] : a + analysisCriteria "1..*" -- "1..*" prefixDigitAnalysis[prefix Digit Analysis] + analysisCriteria "1..*" -- "1..*" callRoutingOfficeData[callRouting Office Data] + +``` + +Entity relationship diagram for Broadband call routing management. The diagram shows a hierarchy of object classes. At the top is 'analysis Criteria', which has a 1..\* relationship with 'carrier Data' (multiplicity 'a'). 'analysis Criteria' also has a 1..\* relationship with 'abstract Destination'. 'abstract Destination' is a superclass for 'local Destination' and 'digit Manip'. 'local Destination' has a 1..\* relationship with 'analysis Criteria' (multiplicity 'a'). 'digit Manip' has a 1..\* relationship with 'analysis Criteria' (multiplicity 'a'). 'analysis Criteria' also has a 1..\* relationship with 'post Analysis Evaluation'. 'post Analysis Evaluation' has a 1..\* relationship with 'listOf RouteTps'. 'listOf RouteTps' has a 1..\* relationship with 'route Data'. 'route Data' has a 1..\* relationship with 'xtpsg Comb'. 'xtpsg Comb' has a 1..\* relationship with 'crCircuit EndPoint Subgroup' (multiplicity 'a'). 'crCircuit EndPoint Subgroup' has a 1..\* relationship with 'crCircuit EndPoint'. 'crCircuit EndPoint' has a 1..\* relationship with 'e0CTP/ds0CTP' (multiplicity 'a'). 'crCircuit EndPoint Subgroup' also has a 1..\* relationship with 'virtual Path Group'. 'virtual Path Group' has a 1..\* relationship with 'sVpTTP' (multiplicity 'a'). 'virtual Path Group' also has a 1..\* relationship with 'nni Access'. 'nni Access' has a 1..\* relationship with 'signRoute SetNePart' (multiplicity 'a'). 'analysis Criteria' also has a 1..\* relationship with 'prefix Digit Analysis' and 'callRouting Office Data'. + +T0409600-98/d08 + +Figure 8/Q.824.6 – Entity relationship diagram – Broadband call routing management + +### 4.2 Inheritance hierarchy + +Figures 9 to 13 below trace the inheritance relationships from the highest level object (Recommendation X.721 [13], "top") to the managed objects which are defined in this Recommendation. + +![Figure 9/Q.824.6 – Inheritance hierarchy – ATM generic fragment](2a25e8bc21554c0efceda1a8ccf57db3_img.jpg) + +``` + + graph LR + A["X.721": +top] --> B["M.3100": +termination +Point] + B --> C["M.3100": +trail +Termination +Point +Source"] + B --> D["M.3100": +trail +Termination +Point +Sink"] + C --> E["M.3100": +trail +Termination +Point +Bidirectional"] + D --> E + E --> F["I.751": +vpTTP +Bidirectional] + F --> G[sVpTtp] + +``` + +T0409610-98/d09 + +Figure 9/Q.824.6 – Inheritance hierarchy – ATM generic fragment + +**Figure 9/Q.824.6 – Inheritance hierarchy – ATM generic fragment** + +![Figure 10/Q.824.6 – Inheritance hierarchy – ATM adaptation layer and signalling fragments](004a497465710d16d63f436bb330fb42_img.jpg) + +``` + + graph LR + TOP["X.721": +top] --- BRANCH + BRANCH --- aalProfile[aalProfile] + BRANCH --- scanner["X.739": +scanner] + BRANCH --- history["Q.822": +history +Data] + BRANCH --- saalUni[saalUni +Protocol +Profile] + + scanner --- current["Q.822": +current +Data] + current --- aalCurrent[aal +Protocol +Current +Data] + + history --- aalHistory[aal +Protocol +History +Data] + +``` + +T0409620-98/d10 + +Figure 10/Q.824.6 – Inheritance hierarchy – ATM adaptation layer and signalling fragments + +**Figure 10/Q.824.6 – Inheritance hierarchy – ATM adaptation layer and signalling fragments** + +12 Recommendation Q.824.6 (06/98) + +![Inheritance hierarchy diagram for Broadband customer administration fragment. The root is 'X.721: top'. It branches into 'bearer ServiceBb', 'customer ProfileBb', 'customized ResourceBb', 'calling Number Screening Bb', 'connected Number Screening Bb', 'Q.824.0: directory Number', 'supplementary ServiceDepBb', 'supplementary ServiceIndBb', 'teleserviceBb', 'uniAccess', and 'userData'. Sub-nodes include 'abr', 'abtDt', 'abtIt', 'dbr', 'sbr', 'ubr' for the first three; 'directory NumberE164' for 'Q.824.0: directory Number'; and various 'clipDepBb', 'clirDepBb', 'cugSubscriptionOptionDepBb', 'colpDepBb', 'colrDepBb', 'subDepBb', 'userToUserSignallingDepBb' for 'supplementary ServiceDepBb'. 'supplementary ServiceIndBb' has 'cugIndBb', 'directDiallingInIndBb', and 'multipleSubscriberNumberIndBb'. A small note 'T0409630-98/d11' is present near the bottom right.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` + +graph TD + X721_top["X.721: top"] --> bearer_ServiceBb["bearer ServiceBb"] + X721_top --> customer_ProfileBb["customer ProfileBb"] + X721_top --> customized_ResourceBb["customized ResourceBb"] + X721_top --> calling_Number_Screening_Bb["calling Number Screening Bb"] + X721_top --> connected_Number_Screening_Bb["connected Number Screening Bb"] + X721_top --> Q8240_directory_Number["Q.824.0: directory Number"] + X721_top --> supplementary_ServiceDepBb["supplementary ServiceDepBb"] + X721_top --> supplementary_ServiceIndBb["supplementary ServiceIndBb"] + X721_top --> teleserviceBb["teleserviceBb"] + X721_top --> uniAccess["uniAccess"] + X721_top --> userData["userData"] + + bearer_ServiceBb --> abr["abr"] + bearer_ServiceBb --> abtDt["abtDt"] + bearer_ServiceBb --> abtIt["abtIt"] + bearer_ServiceBb --> dbr["dbr"] + bearer_ServiceBb --> sbr["sbr"] + bearer_ServiceBb --> ubr["ubr"] + + Q8240_directory_Number --> directory_NumberE164["directory NumberE164"] + + supplementary_ServiceDepBb --> clipDepBb["clipDepBb"] + supplementary_ServiceDepBb --> clirDepBb["clirDepBb"] + supplementary_ServiceDepBb --> cugSubscriptionOptionDepBb["cugSubscriptionOptionDepBb"] + supplementary_ServiceDepBb --> colpDepBb["colpDepBb"] + supplementary_ServiceDepBb --> colrDepBb["colrDepBb"] + supplementary_ServiceDepBb --> subDepBb["subDepBb"] + supplementary_ServiceDepBb --> userToUserSignallingDepBb["userToUserSignallingDepBb"] + + supplementary_ServiceIndBb --> cugIndBb["cugIndBb"] + supplementary_ServiceIndBb --> directDiallingInIndBb["directDiallingInIndBb"] + supplementary_ServiceIndBb --> multipleSubscriberNumberIndBb["multipleSubscriberNumberIndBb"] + + T0409630_98_d11["T0409630-98/d11"] + +``` + +Inheritance hierarchy diagram for Broadband customer administration fragment. The root is 'X.721: top'. It branches into 'bearer ServiceBb', 'customer ProfileBb', 'customized ResourceBb', 'calling Number Screening Bb', 'connected Number Screening Bb', 'Q.824.0: directory Number', 'supplementary ServiceDepBb', 'supplementary ServiceIndBb', 'teleserviceBb', 'uniAccess', and 'userData'. Sub-nodes include 'abr', 'abtDt', 'abtIt', 'dbr', 'sbr', 'ubr' for the first three; 'directory NumberE164' for 'Q.824.0: directory Number'; and various 'clipDepBb', 'clirDepBb', 'cugSubscriptionOptionDepBb', 'colpDepBb', 'colrDepBb', 'subDepBb', 'userToUserSignallingDepBb' for 'supplementary ServiceDepBb'. 'supplementary ServiceIndBb' has 'cugIndBb', 'directDiallingInIndBb', and 'multipleSubscriberNumberIndBb'. A small note 'T0409630-98/d11' is present near the bottom right. + +Figure 11/Q.824.6 – Inheritance hierarchy – Broadband customer administration fragment + +![Inheritance hierarchy diagram for Broadband and narrowband interworking call routing fragment. The root node is 'X.721: top', which branches into a list of 15 components: abstractDestination, analysisCriteria, crCircuitEndPointBb, crCircuitEndPointSubgroupBb, callRoutingOfficeData, carrierData, digitManip, listOfRouteTps, localDestination, nniAccess, prefixDigitAnalysis, postAnalysisEvaluation, routeData, virtualPathGroup, and xtpsgComb.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +``` + +graph LR + X721["X.721: top"] --- abstractDestination + X721 --- analysisCriteria + X721 --- crCircuitEndPointBb + X721 --- crCircuitEndPointSubgroupBb + X721 --- callRoutingOfficeData + X721 --- carrierData + X721 --- digitManip + X721 --- listOfRouteTps + X721 --- localDestination + X721 --- nniAccess + X721 --- prefixDigitAnalysis + X721 --- postAnalysisEvaluation + X721 --- routeData + X721 --- virtualPathGroup + X721 --- xtpsgComb + +``` + +Inheritance hierarchy diagram for Broadband and narrowband interworking call routing fragment. The root node is 'X.721: top', which branches into a list of 15 components: abstractDestination, analysisCriteria, crCircuitEndPointBb, crCircuitEndPointSubgroupBb, callRoutingOfficeData, carrierData, digitManip, listOfRouteTps, localDestination, nniAccess, prefixDigitAnalysis, postAnalysisEvaluation, routeData, virtualPathGroup, and xtpsgComb. + +T0409640-98/d12 + +**Figure 12/Q.824.6 – Inheritance hierarchy – Broadband and narrowband interworking call routing fragment** + +![Inheritance hierarchy diagram for Circuit emulation service interworking fragment. The root node is 'X.721: top', which branches into 'cesServiceProfile'. 'cesServiceProfile' branches into 'M.3100: termination Point'. 'M.3100: termination Point' branches into two nodes: 'M.3100: trail Termination Point Source' and 'M.3100: trail Termination Point Sink'. Both of these nodes branch into 'M.3100: trail Termination Point Bidirectional'. 'M.3100: trail Termination Point Bidirectional' branches into 'I.751: vcTTP Bidirectional', which finally branches into 'interworking VcTtpBidirectional'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +graph LR + X721["X.721: top"] --- cesServiceProfile + cesServiceProfile --- M3100TP["M.3100: termination Point"] + M3100TP --- M3100TPS["M.3100: trail Termination Point Source"] + M3100TP --- M3100TPK["M.3100: trail Termination Point Sink"] + M3100TPS --- M3100TPB["M.3100: trail Termination Point Bidirectional"] + M3100TPK --- M3100TPB + M3100TPB --- I751["I.751: vcTTP Bidirectional"] + I751 --- interworking["interworking VcTtpBidirectional"] + +``` + +Inheritance hierarchy diagram for Circuit emulation service interworking fragment. The root node is 'X.721: top', which branches into 'cesServiceProfile'. 'cesServiceProfile' branches into 'M.3100: termination Point'. 'M.3100: termination Point' branches into two nodes: 'M.3100: trail Termination Point Source' and 'M.3100: trail Termination Point Sink'. Both of these nodes branch into 'M.3100: trail Termination Point Bidirectional'. 'M.3100: trail Termination Point Bidirectional' branches into 'I.751: vcTTP Bidirectional', which finally branches into 'interworking VcTtpBidirectional'. + +T0409650-98/d13 + +**Figure 13/Q.824.6 – Inheritance hierarchy – Circuit emulation service interworking fragment** + +## 5 Formal definitions + +This clause gives the formal definitions of the managed object classes, name bindings, general packages, behaviours, attributes, actions and notifications. + +### 5.1 Object classes + +This subclause specifies the object classes for all of the managed objects used in the management information model. These object classes are either defined here or by reference to other specifications. Classes of managed objects which are defined elsewhere and which are only used for containment are not included, but are identified by the name bindings for the classes specified here. + +Unidirectional trails are modelled by bidirectional objects with the traffic descriptor in the unused direction set to a null value. + +The following class which is defined in Recommendation M.3100 [6] may be instantiated: + +- **managedElementR1.** + +The following classes which are defined in Recommendation I.751 [4] may be instantiated: + +- **"I.751":atmAccessProfile;** +- **"I.751":atmCrossConnection;** +- **"I.751":atmCurrentData;** +- **"I.751":atmFabric;** +- **"I.751":atmTrafficLoadCurrentData;** +- **"I.751":atmTrafficLoadHistoryData;** +- **"I.751":bidirectionalContinuityMonitor;** +- **"I.751":bidirectionalPerformanceMonitor;** +- **"I.751":cellHeaderAbnormalityLogRecord;** +- **"I.751":cellLevelProtocolCurrentData;** +- **"I.751":cellLevelProtocolHistoryData;** +- **"I.751":interNNI;** +- **"I.751":intraNNI;** +- **"I.751":tcAdaptorCurrentData;** +- **"I.751":tcAdaptorHistoryData;** +- **"I.751":tcAdaptorTTPBidirectional;** +- **"I.751":uni;** +- **"I.751":upcNpcCurrentData;** +- **"I.751":upcNpcHistoryData;** +- **"I.751":vcCTPBidirectional;** +- **"I.751":vcTTPBidirectional;** +- **"I.751":vpCTPBidirectional;** +- **"I.751":vpTTPBidirectional;** +- **"I.751":vpVcPMCurrentData;** +- **"I.751":vpVcPMHistoryData.** + +The following class which is defined in Recommendation X.721 [13] may be instantiated: + +- **log.** + +### 5.1.1 ATM generic fragment + +#### 5.1.1.1 Switch virtual path TTP (sVpTtp) + +##### **sVpTtp MANAGED OBJECT CLASS** + +**DERIVED FROM "Rec. I.751":vpTTPBidirectional;** + +##### **CHARACTERIZED BY** + +**sVpTtpPkg PACKAGE** + +**BEHAVIOUR sVpTtpBeh;** + +##### **ATTRIBUTES** + +**vpType** + +**GET-REPLACE;;;** + +##### **CONDITIONAL PACKAGES** + +**blockedForMaintenancePkg** + +**PRESENT IF "requested by the managing system",** + +**maintenanceSignallingRunningPkg** + +**PRESENT IF "requested by the managing system.",** + +**propagationDelayPkg** + +**PRESENT IF "supported by the managing system",** + +**remoteBlockingPkg** + +**PRESENT IF "requested by the managing system.";** + +**REGISTERED AS {managedObjectClass 1};** + +##### **sVpTtpBeh BEHAVIOUR** + +##### **DEFINED AS** + +**"A switch virtual path TTP is an object class representing the endpoint of an ATM VPC at a switching network element.";** + +### 5.1.2 ATM adaptation layer fragment + +#### 5.1.2.1 AAL profile (aalProfile) + +##### **aalProfile MANAGED OBJECT CLASS** + +**DERIVED FROM "ITU-T Rec. X.721 | ISO/IEC 10165-2":top;** + +##### **CHARACTERIZED BY** + +**aalProfilePkg PACKAGE** + +**BEHAVIOUR aalProfileBeh;** + +##### **ATTRIBUTES** + +**aalProfileId** + +**GET,** + +**aalType** + +**GET;;;** + +##### **CONDITIONAL PACKAGES** + +**aalTypeOneProfilePkg** + +**PRESENT IF "the aalType attribute is set to aal1",** + +**aalTypeThreeFourProfilePkg** + +**PRESENT IF "the aalType attribute is set to aal34",** + +**aalTypeFiveProfilePkg** + +**PRESENT IF "the aalType attribute is set to aal5";** + +**REGISTERED AS {managedObjectClass 2};** + +**aalProfileBeh BEHAVIOUR** + +**DEFINED AS** + +"The aalProfile object class is a managed support object used to organize data that describes the AAL processing functions of the ATM NE. The attribute aalType identifies the type of AAL processing (i.e., AAL1, AAL3/4, or AAL5). The AAL profiling information is contained in packages which are present based on the value of the aalType attribute. "; + +**5.1.2.2 AAL protocol current data (aalProtocolCurrentData)** + +**aalProtocolCurrentData MANAGED OBJECT CLASS** + +**DERIVED FROM "ITU-T Rec. Q.822": currentData;** + +**CHARACTERIZED BY** + +**aalProtocolCurrentDataPkg PACKAGE** + +**BEHAVIOUR aalProtocolCurrentDataBeh;;;** + +**CONDITIONAL PACKAGES** + +**aalTypeOnePerformanceParameterPkg** + +**PRESENT IF "AAL Type 1 processing is being performed",** + +**aalTypeThreeFourPerformanceParameterPkg** + +**PRESENT IF "AAL Type 3/4 processing is being performed",** + +**aalTypeFivePerformanceParameterPkg** + +**PRESENT IF "AAL Type 5 processing is being performed";** + +**REGISTERED AS {managedObjectClass 3};** + +**aalProtocolCurrentDataBeh BEHAVIOUR** + +**DEFINED AS** + +"The aalProtocolCurrentData object is a managed support object that contains the current performance monitoring data collected as a result of performing Segmentation and Reassembly (SAR) Level and Convergence Sublayer (CS) protocol monitoring. The granularityPeriod attribute inherited from the scanner object class shall be set to 15 minutes. Instances of this object class shall be inherently created by the managed system whenever an instance of the Interworking VCC Termination Point object class is created that represents AAL functions."; + +**5.1.2.3 AAL protocol history data (aalProtocolHistoryData)** + +**aalProtocolHistoryData MANAGED OBJECT CLASS** + +**DERIVED FROM "ITU-T Rec. Q.822": historyData;** + +**CHARACTERIZED BY** + +**aalProtocolHistoryDataPkg PACKAGE** + +**BEHAVIOUR aalProtocolHistoryDataBeh;;;** + +**CONDITIONAL PACKAGES** + +**aalTypeOnePerformanceParameterHistoryDataPkg** + +**PRESENT IF "AAL Type 1 processing is being performed",** + +**aalTypeThreeFourPerformanceParameterHistoryDataPkg** + +**PRESENT IF "AAL Type 3/4 processing is being performed",** + +**aalTypeFivePerformanceParameterHistoryDataPkg** + +**PRESENT IF "AAL Type 5 processing is being performed";** + +**REGISTERED AS {managedObjectClass 4};** + +**aalProtocolHistoryDataBeh BEHAVIOUR** + +**DEFINED AS** + +"The aalProtocolHistoryData object is a managed support object that contains the past performance monitoring data collected as a result of performing Segmentation and Reassembly (SAR) Level and Convergence Sublayer (CS) protocol monitoring. Instances of this object class can only be created locally by an agent (managed system) according to the value of the historyRetention attribute specified in the aalProtocolCurrentData object."; + +### 5.1.3 Signalling fragment + +#### 5.1.3.1 SAAL UNI protocol profile (saalUniProtocolProfile) + +**saalUniProtocolProfile** MANAGED OBJECT CLASS + +DERIVED FROM "ITU-T Rec. X.721 | ISO/IEC 10165-2": top; + +CHARACTERIZED BY + +**saalUniProtocolProfilePkg** PACKAGE + +BEHAVIOUR **saalUniProtocolProfileBeh**; + +ATTRIBUTES + +**saalUniProtocolProfileId** + +GET SET-BY-CREATE, + +**bufferRelease** + +DEFAULT VALUE **ASN1DefinedTypesModule.bufferReleaseDefault** + +GET SET-BY-CREATE, + +**maxCc** + +DEFAULT VALUE **ASN1DefinedTypesModule.maxCcDefault** + +GET SET-BY-CREATE, + +**maxInformationFieldLength** + +DEFAULT VALUE + +**ASN1DefinedTypesModule.maxInformationFieldLengthDefault** + +GET SET-BY-CREATE, + +**maxLengthSscopUuField** + +DEFAULT VALUE + +**ASN1DefinedTypesModule.maxLengthSscopUuFieldDefault** + +GET SET-BY-CREATE, + +**maxPd** + +DEFAULT VALUE **ASN1DefinedTypesModule.maxPdDefault** + +GET SET-BY-CREATE, + +**maxSscopCreditToPeer** + +DEFAULT VALUE **ASN1DefinedTypesModule.maxSscopCreditToPeerDefault** + +GET SET-BY-CREATE, + +**maxStat** + +DEFAULT VALUE **ASN1DefinedTypesModule.maxStatDefault** + +GET SET-BY-CREATE, + +**sscoperTimerCc** + +DEFAULT VALUE **ASN1DefinedTypesModule.sscoperTimerCcDefault** + +GET SET-BY-CREATE, + +**sscoperTimerIdle** + +DEFAULT VALUE **ASN1DefinedTypesModule.sscoperTimerIdleDefault** + +GET SET-BY-CREATE, + +**sscoperTimerKeepAlive** + +DEFAULT VALUE **ASN1DefinedTypesModule.sscoperTimerKeepAliveDefault** + +GET SET-BY-CREATE, + +**sscoperTimerNoResponse** + +DEFAULT VALUE **ASN1DefinedTypesModule.sscoperTimerNoResponseDefault** + +GET SET-BY-CREATE, + +**sscoperTimerPoll** + +DEFAULT VALUE **ASN1DefinedTypesModule.sscoperTimerPollDefault** + +GET SET-BY-CREATE;;; + +CONDITIONAL PACKAGES + +"ITU-T Rec. M.3100":**createDeleteNotificationsPackage** + +PRESENT IF "supported by an instance of this class", + +**pollAfterRetransmissionPkg** + +PRESENT IF "an instance supports this national option"; + +REGISTERED AS {managedObjectClass 5}; + +**saalUniProtocolProfileBeh BEHAVIOUR** + +**DEFINED AS** + +"The saalUniProtocolProfile is a broadband-specific object class which comprises attributes required for SSCOP, SSCF-UNI and Layer Management for UNI."; + +#### **5.1.4 Broadband customer administration fragment** + +##### **5.1.4.1 Available bit rate (abr)** + +**abr MANAGED OBJECT CLASS** + +**DERIVED FROM** bearerServiceBb; + +**CHARACTERIZED BY** + +**abrPkg PACKAGE** + +**BEHAVIOUR** abrBeh;;; + +**REGISTERED AS** {managedObjectClass 6}; + +**abrBeh BEHAVIOUR** + +**DEFINED AS** + +"This subclass of 'bearer service' represents the adaptation of connection-oriented data with available bit rate."; + +##### **5.1.4.2 ATM block transfer with delayed transmission (abtDt)** + +**abtDt MANAGED OBJECT CLASS** + +**DERIVED FROM** bearerServiceBb; + +**CHARACTERIZED BY** + +**abtDtPkg PACKAGE** + +**BEHAVIOUR** abtDtBeh;;; + +**REGISTERED AS** {managedObjectClass 7}; + +**abtDtBeh BEHAVIOUR** + +**DEFINED AS** + +"This subclass of 'bearer service' represents the adaptation of connection-oriented data with ATM block transfer with delayed transmission."; + +##### **5.1.4.3 ATM block transfer with immediate transmission (abtIt)** + +**abtIt MANAGED OBJECT CLASS** + +**DERIVED FROM** bearerServiceBb; + +**CHARACTERIZED BY** + +**abtItPkg PACKAGE** + +**BEHAVIOUR** abtItBeh;;; + +**REGISTERED AS** {managedObjectClass 8}; + +**abtItBeh BEHAVIOUR** + +**DEFINED AS** + +"This subclass of 'bearer service' represents the adaptation of connection-oriented data with ATM block transfer with immediate transmission."; + +##### **5.1.4.4 Bearer service for broadband (bearerServiceBb)** + +**bearerServiceBb MANAGED OBJECT CLASS** + +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2": top; + +**CHARACTERIZED BY** + +**customizedResourcePointersBehPkg,** + +**bearerServiceBbPkg PACKAGE** + +**BEHAVIOUR** bearerServiceBbBeh; +**ATTRIBUTES** + "ITU-T Q.824.0":bearerServiceId + GET SET-BY-CREATE, + "CCITT Rec. X.721 | ISO/IEC 10165-2": administrativeState + GET-REPLACE, + "ITU-T Q.824.0":customizedResourcePtrList + DEFAULT VALUE ASN1DefinedTypesModule.emptySet + GET; +**NOTIFICATIONS** + "CCITT Rec. X.721 | ISO/IEC 10165-2":stateChange, + "CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange;;; +**REGISTERED AS** {managedObjectClass 9}; + +**bearerServiceBbBeh BEHAVIOUR** +**DEFINED AS** + "The Bearer Service object class represents the common aspects of the bearer services. While the Bearer Service object class is not instantiated, it is a superclass from which specialized subclasses are derived and instantiated."; + +#### 5.1.4.5 Calling line identification presentation dependent for broadband (clipDepBb) + +**clipDepBb MANAGED OBJECT CLASS** +**DERIVED FROM** supplementaryServiceDepBb; +**CHARACTERIZED BY** + clipBbPkg; +**CONDITIONAL PACKAGES** + twoCallingPartyNumberDeliveryPkg + PRESENT IF "supplied by the managing system"; +**REGISTERED AS** {managedObjectClass 10}; + +#### 5.1.4.6 Calling line identification restriction dependent for broadband (clirDepBb) + +**clirDepBb MANAGED OBJECT CLASS** +**DERIVED FROM** supplementaryServiceDepBb; +**CHARACTERIZED BY** + clirBbPkg; +**REGISTERED AS** {managedObjectClass 11}; + +#### 5.1.4.7 Calling number screening for broadband (callingNumberScreeningBb) + +**callingNumberScreeningBb MANAGED OBJECT CLASS** +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2":top; +**CHARACTERIZED BY** + callingNumberScreeningPkg **PACKAGE** +**BEHAVIOUR** callingNumberScreeningBeh; +**ATTRIBUTES** + "ITU-T Q.824.1": callingNumberScreeningId + GET SET-BY-CREATE, + screenNumber + DEFAULT VALUE ASN1DefinedTypesModule.defaultScreenNumber + GET-REPLACE, + defaultDirectoryNumber + GET-REPLACE; + +## NOTIFICATIONS + +"CCITT Rec. X.721 | ISO/IEC 10165-2": attributeValueChange, +"CCITT Rec. X.721 | ISO/IEC 10165-2": objectCreation, +"CCITT Rec. X.721 | ISO/IEC 10165-2": objectDeletion;;; + +REGISTERED AS {managedObjectClass 12}; + +callingNumberScreeningBeh BEHAVIOUR + +### DEFINED AS + +"This object identifies characteristics used for the screening of the Calling Party Directory Number as described in Rec. Q.2951.3. Only one object of this object class shall be contained in the superior object instance."; + +## 5.1.4.8 Closed user group independent for broadband (cugIndBb) + +cugIndBb MANAGED OBJECT CLASS + +DERIVED FROM supplementaryServiceIndBb; + +### CHARACTERIZED BY + +cugBbPkg PACKAGE + +BEHAVIOUR cugBbBeh; + +### ATTRIBUTES + +cugIndex + +GET SET-BY-CREATE, + +cugInterlockCode + +GET SET-BY-CREATE, + +cugDataNetworkIdentification + +GET SET-BY-CREATE, + +cugBarring GET-REPLACE, + +"ITU-T Q.824.0":servicePtrList + +DEFAULT VALUE ASN1DefinedTypesModule.emptySet + +GET-REPLACE ADD-REMOVE;;; + +REGISTERED AS {managedObjectClass 13}; + +cugBbBeh BEHAVIOUR + +### DEFINED AS + +"This managed object class is used to store the closed user group general subscription options specified by ITU-T Rec. Q.2955.1. This package is instantiated by for each Closed User Group. When the value of cugBarring is outgoingCallsBarred, this CUG must not be a preferential Closed User Group (denoted by preferredCugIndex in cugSubscriptionOption managed object). An object of this class can only deleted, if it is not referenced by a cugSubscriptionOption(Independent) object. The 'customizedResourcePtrList' and the 'servicePtrList' can only be used mutually exclusive. This means that one of them has to be empty."; + +## 5.1.4.9 Closed user group subscription option dependent for broadband (cugSubscriptionOptionDepBb) + +cugSubscriptionOptionDepBb MANAGED OBJECT CLASS + +DERIVED FROM supplementaryServiceDepBb; + +### CHARACTERIZED BY + +cugSubscriptionOptionBbPkg; + +REGISTERED AS {managedObjectClass 14}; + +#### **5.1.4.10 Connected line identification presentation dependent for broadband (colpDepBb)** + +**colpDepBb MANAGED OBJECT CLASS** +**DERIVED FROM** supplementaryServiceDepBb; +**CHARACTERIZED BY** +    colpBbPkg; +**REGISTERED AS** {managedObjectClass 15}; + +#### **5.1.4.11 Connected line identification restriction dependent for broadband (colrDepBb)** + +**colrDepBb MANAGED OBJECT CLASS** +**DERIVED FROM** supplementaryServiceDepBb; +**CHARACTERIZED BY** +    colrBbPkg; +**REGISTERED AS** {managedObjectClass 16}; + +#### **5.1.4.12 Connected number screening for broadband (connectedNumberScreeningBb)** + +**connectedNumberScreeningBb MANAGED OBJECT CLASS** +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2":top; +**CHARACTERIZED BY** +    connectedNumberScreeningPkg **PACKAGE** +        **BEHAVIOUR** connectedNumberScreeningBeh; +        **ATTRIBUTES** +            connectedNumberScreeningId +                **GET SET-BY-CREATE,** +            screenNumber +                **DEFAULT VALUE** ASN1DefinedTypesModule.defaultScreenNumber +                **GET-REPLACE,** +            defaultDirectoryNumber +                **GET-REPLACE;** +        **NOTIFICATIONS** +            "CCITT Rec. X.721 | ISO/IEC 10165-2": attributeValueChange, +            "CCITT Rec. X.721 | ISO/IEC 10165-2": objectCreation, +            "CCITT Rec. X.721 | ISO/IEC 10165-2": objectDeletion;;; +**REGISTERED AS** {managedObjectClass 17}; + +**connectedNumberScreeningBeh BEHAVIOUR** +**DEFINED AS** +    "This object identifies characteristics used for the screening of the Connected Line Directory Number as described in Rec. Q.2951.5. Only one object of this object class shall be contained in the superior object instance."; + +#### **5.1.4.13 Customer profile for broadband (customerProfileBb)** + +**customerProfileBb MANAGED OBJECT CLASS** +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2":top; +**CHARACTERIZED BY** +    customerProfilePointersBehPkg, +    customerProfileBbPkg **PACKAGE** +        **BEHAVIOUR** customerProfileBbBeh; +        **ATTRIBUTES** + +"ITU-T Q.824.0":customerProfileId + GET SET-BY-CREATE, + accessPtrList + GET-REPLACE ADD-REMOVE, + "ITU-T Q.824.0":directoryNumberPtrList + GET-REPLACE ADD-REMOVE;; + +REGISTERED AS {managedObjectClass 18}; + +**customerProfileBbBeh BEHAVIOUR** + +**DEFINED AS** + +"The Customer Profile represents a single point of reference used to bind together a range of services and resources for customer administration purposes. It is a class of managed objects representing the characteristics of the Directory Number(s) (DN) assigned to an individual subscriber, independent of the access type and bearer service. Each instance of the customer profile object class includes a Directory Number Pointer List attribute that represents the Directory Number(s) assigned to the customer profile object and an Access Pointer List attribute that represents Access(es) also assigned to the customer profile object. + Objects which are related through direct or indirect containment or by a direct pointer relationship with a customerProfileBb object can not be related in the same way to a different customerProfileBb object. + More than one entry in the 'directoryNumberPtrList' are allowed only if a 'multipleSubscriberNumberIndBb' object is contained in this 'customerProfileBb' object."; + +**5.1.4.14 Customized resource for broadband (customizedResourceBb)** + +**customizedResourceBb MANAGED OBJECT CLASS** + +DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2": top; + +**CHARACTERIZED BY** + +customizedResourcePointersBehPkg, + customizedResourceBbPkg PACKAGE + BEHAVIOUR customizedResourceBbBeh; + ATTRIBUTES + +"ITU-T Q.824.0":customizedResourceId + GET SET-BY-CREATE, + "ITU-T Q.824.0":bearerServicePtrList + GET-REPLACE ADD-REMOVE, + "ITU-T Q.824.0":directoryNumberPtrList + GET-REPLACE ADD-REMOVE, + "ITU-T Q.824.0":teleServicePtrList + GET-REPLACE ADD-REMOVE, + supplementaryServiceIndBbPtrList + GET-REPLACE ADD-REMOVE, + userDataPtr + GET-REPLACE;; + +REGISTERED AS {managedObjectClass 19}; + +**customizedResourceBbBeh BEHAVIOUR** + +**DEFINED AS** + +"The Customized Resource object is a class of managed objects that represents the service provisioning for a subscriber. It allows association of a set of services and/or one userData object to one or more Directory Numbers. + When no customized resource objects are contained in a customer profile object, then all services/userData contained in this customer profile object are applicable to all directory numbers associated with this customer profile object. + If one or more customized resource objects are contained in a customer profile object, then only these services/userData (contained in this customer profile object) are applicable to a certain directory number (associated with the customer profile object) which are explicitly associated to this directory number object using a customized resource object. + Only one entry shall be contained in the directoryNumberPtrList. + The teleServicePtrList attribute points to instances of the class teleserviceBb or its subclasses."; + +#### 5.1.4.15 Deterministic bit rate (dbr) + +**dbr MANAGED OBJECT CLASS** + +**DERIVED FROM** bearerServiceBb; + +**CHARACTERIZED BY** + +**dbrPkg PACKAGE** + +**BEHAVIOUR** dbrBeh;;; + +**REGISTERED AS** {managedObjectClass 20}; + +**dbrBeh BEHAVIOUR** + +**DEFINED AS** + +"This subclass of 'bearer service' represents the adaptation of connection-oriented data with deterministic (constant) bit rate and timing relation between sender and receiver."; + +#### 5.1.4.16 Direct dialling in independent for broadband (directDiallingInIndBb) + +**directDiallingInIndBb MANAGED OBJECT CLASS** + +**DERIVED FROM** supplementaryServiceIndBb; + +**CHARACTERIZED BY** + +**directDiallingInIndBbPkg PACKAGE** + +**BEHAVIOUR** directDiallingInIndBbBeh; + +**ATTRIBUTES** + +**cdpnRepresentationType** + +**GET-REPLACE;;;** + +**CONDITIONAL PACKAGES** + +**"ITU-T Q.824.2":digitsOptionPkg** + +**PRESENT IF** "if supported by administration"; + +**REGISTERED AS** {managedObjectClass 21}; + +**directDiallingInIndBbBeh BEHAVIOUR** + +**DEFINED AS** + +"This Supplementary Service enables a user to call directly via a public ISDN to a user on a private ISDN by use of the public ISDN numbering plan as described in ITU-T Rec. Q.2951.1. + +Only one object of this class shall be contained within the superior managed object. The customizedResourcePtrList derived from the supplementaryServiceIndBb shall be empty."; + +#### 5.1.4.17 Directory number E164 (directoryNumberE164) + +**directoryNumberE164 MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Q.824.0":directoryNumber; + +**CHARACTERIZED BY** + +**customerProfilePointersBehPkg,** + +**directoryNumberE164Pkg PACKAGE** + +**BEHAVIOUR** directoryNumberE164Beh; + +**ATTRIBUTES** + +**"ITU-T Q.824.0":e164DirectoryNumber** + +**GET SET-BY-CREATE,** + +**localDestinationPtr** + +**GET SET-BY-CREATE;;;** + +**REGISTERED AS** {managedObjectClass 22}; + +**directoryNumberE164Beh BEHAVIOUR** + +**DEFINED AS** + +"The E.164 Directory Number object class represents directory numbers belonging to the international public telecommunication numbering plan as defined in ITU-T E.164. The E.164 Directory Number is a single-valued, read-only attribute, set only at creation time. The E.164 Directory Number is updated implicitly if the attribute values of the referenced localDestination object are modified. The routingBlockPtrPkg inherited from the directoryNumber object class shall not be present. + +Only one entry shall be contained in the customizedResourcePtrList." + +#### **5.1.4.18 Multiple subscriber number independent for broadband (multipleSubscriberNumberIndBb)** + +**multipleSubscriberNumberIndBb MANAGED OBJECT CLASS** + +**DERIVED FROM** supplementaryServiceIndBb; + +**CHARACTERIZED BY** + +**multipleSubscriberNumberIndBbPkg PACKAGE** + +**BEHAVIOUR** multipleSubscriberNumberIndBbBeh; + +**ATTRIBUTES** + +**"ITU-T Q.824.2":** assocDefaultDN + +**GET-REPLACE,** + +**cdpnRepresentationType** + +**GET-REPLACE;;;** + +**CONDITIONAL PACKAGES** + +**"ITU-T Q.824.2":** networkOptionsPkg + +**PRESENT IF** "if supported by administration." + +**REGISTERED AS** {managedObjectClass 23}; + +**multipleSubscriberNumberIndBbBeh BEHAVIOUR** + +**DEFINED AS** + +"The MSN supplementary service provides the possibility for assigning multiple numbers (not necessarily consecutive) to a single public or private interface as described in ITU-T Rec. Q.2951.2. This enables the selection of multiple distinct terminals attached to the same interface. + +The service provider shall fix the length of the numbers to be transmitted to the user's installation. They may comprise the least significant digit up to the full ISDN number as defined in CCITT Rec. E.164. The digit(s) significant for terminal differentiation shall be an integral part of the ISDN numbering scheme. + +If the attribute 'cdpnRepresentationType' has the value 'unknown', the 'networkOptionsPkg' must be present to determine the number of digits to be transmitted to the user. + +Only one object of this class shall be contained within the superior managed object. The customizedResourcePtrList derived from the supplementaryServiceIndBb shall be empty." + +#### **5.1.4.19 Statistical bit rate (sbr)** + +**sbr MANAGED OBJECT CLASS** + +**DERIVED FROM** bearerServiceBb; + +**CHARACTERIZED BY** + +**sbrPkg PACKAGE** + +**BEHAVIOUR** sbrBeh; + +**ATTRIBUTES** + +**timingRelation** + +**GET-REPLACE;;;** + +**REGISTERED AS** {managedObjectClass 24}; + +#### **sbrBeh BEHAVIOUR** + +##### **DEFINED AS** + +"This subclass of 'bearer service' represents the adaptation of connection-oriented data with statistical (variable) bit rate (SBR 1/2/3)."; + +#### **5.1.4.20 Sub-addressing dependent for broadband (subDepBb)** + +##### **subDepBb MANAGED OBJECT CLASS** + +**DERIVED FROM** supplementaryServiceDepBb; + +##### **CHARACTERIZED BY** + +subBbPkg; + +**REGISTERED AS** {managedObjectClass 25}; + +#### **5.1.4.21 Supplementary service dependent for broadband (supplementaryServiceDepBb)** + +##### **supplementaryServiceDepBb MANAGED OBJECT CLASS** + +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2": top; + +##### **CHARACTERIZED BY** + +supplementaryServiceDepBbPkg **PACKAGE** + +##### **BEHAVIOUR** + +supplementaryServiceDepBbBeh; + +##### **ATTRIBUTES** + +"ITU-T Q.824.0":supplementaryServiceId + +**GET SET-BY-CREATE,** + +"CCITT Rec. X.721 | ISO/IEC 10165-2": administrativeState + +**GET-REPLACE;** + +##### **NOTIFICATIONS** + +"CCITT Rec. X.721 | ISO/IEC 10165-2": stateChange, + +"CCITT Rec. X.721 | ISO/IEC 10165-2": attributeValueChange, + +"CCITT Rec. X.721 | ISO/IEC 10165-2": objectCreation, + +"CCITT Rec. X.721 | ISO/IEC 10165-2": objectDeletion;;; + +**REGISTERED AS** {managedObjectClass 26}; + +#### **supplementaryServiceDepBbBeh BEHAVIOUR** + +##### **DEFINED AS** + +"This object class is defined to allow the creation of specific supplementary service subclasses for those supplementary services that are defined by ITU-T to be configurable on a per bearer or teleservice basis. Supplementary services, as defined in I.210, are services that can only be used in conjunction with another bearer service or another teleservice. + +While the supplementaryServiceDepBb object class is not instantiated, it is a superclass from which specialized subclasses are derived and instantiated."; + +#### **5.1.4.22 Supplementary service independent for broadband (supplementaryServiceIndBb)** + +##### **supplementaryServiceIndBb MANAGED OBJECT CLASS** + +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2": top; + +##### **CHARACTERIZED BY** + +customizedResourcePointersBehPkg, + +supplementaryServiceIndBbPkg **PACKAGE** + +**BEHAVIOUR** supplementaryServiceIndBbBeh; + +##### **ATTRIBUTES** + +"ITU-T Q.824.0":supplementaryServiceId + +**GET SET-BY-CREATE,** + +"CCITT Rec. X.721 | ISO/IEC 10165-2": administrativeState + +**GET-REPLACE,** + +"ITU-T Q.824.0":customizedResourcePtrList + DEFAULT VALUE ASN1DefinedTypesModule.emptySet + GET; + NOTIFICATIONS + +"CCITT Rec. X.721 | ISO/IEC 10165-2": stateChange, + "CCITT Rec. X.721 | ISO/IEC 10165-2": attributeValueChange, + "CCITT Rec. X.721 | ISO/IEC 10165-2": objectCreation, + "CCITT Rec. X.721 | ISO/IEC 10165-2": objectDeletion;;; + +REGISTERED AS {managedObjectClass 27}; + +supplementaryServiceIndBbBeh BEHAVIOUR + +DEFINED AS + +"This object class is defined to allow the creation of specific supplementary service subclasses for those supplementary services that are defined by ITU-T to be independent of any particular bearer/teleservice. Supplementary services, as defined in I.210, are services that can only be used in conjunction with another bearer service or another teleservice. + While the supplementaryServiceIndBb object class is not instantiated, it is a superclass from which specialized subclasses are derived and instantiated." + +#### 5.1.4.23 Teleservice for broadband (teleserviceBb) + +teleserviceBb MANAGED OBJECT CLASS + +DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2": top; + +CHARACTERIZED BY + +customizedResourcePointersBehPkg, + +teleserviceBbPkg PACKAGE + +BEHAVIOUR teleserviceBbBeh; + +ATTRIBUTES + +"ITU-T Q.824.0":teleserviceId + +GET SET-BY-CREATE, + +"ITU-T Q.824.0":bearerServicePtr + +GET-REPLACE, + +"CCITT Rec. X.721 | ISO/IEC 10165-2": administrativeState + +GET-REPLACE, + +"ITU-T Q.824.0":customizedResourcePtrList + +DEFAULT VALUE ASN1DefinedTypesModule.emptySet + +GET; + +NOTIFICATIONS + +"CCITT Rec. X.721 | ISO/IEC 10165-2": stateChange;;; + +REGISTERED AS {managedObjectClass 28}; + +teleserviceBbBeh BEHAVIOUR + +DEFINED AS + +"The teleservices managed object class defines a communication service that makes available layer 1 – layer 7 capabilities. + While the teleserviceBb object class is not instantiated, it is a superclass from which specialized subclasses are derived and instantiated." + +#### 5.1.4.24 Uni access (uniAccess) + +uniAccess MANAGED OBJECT CLASS + +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2":top; + +CHARACTERIZED BY + +"CCITT Rec. X.721 | ISO/IEC 10165-2":administrativeStatePackage, + +customerProfilePointersBehPkg, + +uniAccessPkg PACKAGE + +**BEHAVIOUR uniAccessBeh;** + +**ATTRIBUTES** + +**uniAccessId** + +**GET SET-BY-CREATE,** + +**signallingStandard** + +**GET-REPLACE,** + +**customerProfilePtr** + +**DEFAULT VALUE ASN1DefinedTypesModule.defaultNULL** + +**GET,** + +**tpAndVpciSigPtrList** + +**GET-REPLACE** + +**ADD-REMOVE,** + +**connectionIdOffering** + +**DEFAULT VALUE ASN1DefinedTypesModule.connectionIdOfferingDefault** + +**GET-REPLACE;;;** + +**CONDITIONAL PACKAGES** + +**maintenanceSignallingRunningPkg** + +**PRESENT IF "requested by the managing system.",** + +**searchMethodPkg** + +**PRESENT IF "supplied by the managing system.",** + +**signallingChannelPtrPkg** + +**PRESENT IF "non-associated signalling is used for this object instance",** + +**signallingTypePkg** + +**PRESENT IF "the managed system supports associated signalling";** + +**REGISTERED AS {managedObjectClass 29};** + +**uniAccessBeh BEHAVIOUR** + +**DEFINED AS** + +**"This managed object represents a group of VPs coming from the same User Network Interface (UNI). The VPs can be distributed over one or more physical interfaces. One physical interface can contain VPs of several object instances of the object class uniAccess.** + +**In the case of non-associated signalling, all VPs of one uniAccess object instance are controlled by the same signalling channel and there is only one signalling channel for the group. In the case of associated signalling there is one signalling channel, typically VCI = 5, for each VP in the group. Non-associated signalling is assumed if the signallingTypePkg is not present in a uniAccess object instance.** + +**If the administrativeState attribute is set to locked, all signalled virtual connections shall be released. PVCs are not influenced by this attribute.** + +**It is not requested (but allowed) that the VPC which contains the signalling VCC be contained in the tpAndVpciSigPtrList. If this VPC is contained in the list then it can be used for on-demand connections controlled by this signalling VCC. If the VPC is not in the list then it cannot be used for on-demand connections controlled by the identified signalling VC."** + +### **5.1.4.25 Unspecified bit rate (ubr)** + +**ubr MANAGED OBJECT CLASS** + +**DERIVED FROM bearerServiceBb;** + +**CHARACTERIZED BY** + +**ubrPkg PACKAGE** + +**BEHAVIOUR ubrBeh;;;** + +**REGISTERED AS {managedObjectClass 30};** + +**ubrBeh BEHAVIOUR** + +**DEFINED AS** + +**"This subclass of 'bearer service' represents the adaptation of connection-oriented data with unspecified bit rate."** + +#### 5.1.4.26 User data (userData) + +**userData MANAGED OBJECT CLASS** + +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2": top; + +**CHARACTERIZED BY** + +customizedResourcePointersBehPkg, + +userDataPkg **PACKAGE** + +**BEHAVIOUR** userDataBeh; + +**ATTRIBUTES** + +userId + +**GET SET-BY-CREATE,** + +"ITU-T Q.824.0":customizedResourcePtrList + +**DEFAULT VALUE** ASN1DefinedTypesModule.emptySet + +**GET,** + +subscriberCategory + +**DEFAULT VALUE** ASN1DefinedTypesModule.subscriberCategoryDefault + +**GET-REPLACE ;** + +**NOTIFICATIONS** + +"CCITT Rec. X.721 | ISO/IEC 10165-2": attributeValueChange, + +"CCITT Rec. X.721 | ISO/IEC 10165-2": objectCreation, + +"CCITT Rec. X.721 | ISO/IEC 10165-2": objectDeletion;;; + +**CONDITIONAL PACKAGES** + +originMarkPkg + +**PRESENT IF** "supplied by the managing system" , + +preferredCarrierPkg + +**PRESENT IF** "carrier specific routing is supplied" ; + +**REGISTERED AS** {managedObjectClass 31}; + +**userDataBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the properties of a certain subscriber (user). The properties may be either valid for the whole superior customerProfile or for a certain directory number only, depending from the use of customizedResource objects. + +Only one 'userData' object with an empty 'customizedResourcePtrList' shall be contained in a customerProfile object." ; + +#### 5.1.4.27 User to user signalling dependent for broadband (userToUserSignallingDepBb) + +**userToUserSignallingDepBb MANAGED OBJECT CLASS** + +**DERIVED FROM** supplementaryServiceDepBb; + +**CHARACTERIZED BY** + +userToUserSignallingBbPkg; + +**REGISTERED AS** {managedObjectClass 32}; + +### 5.1.5 Broadband and narrowband interworking call routing fragment + +#### 5.1.5.1 Abstract destination (abstractDestination) + +**abstractDestination MANAGED OBJECT CLASS** + +**DERIVED FROM** "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + +**CHARACTERIZED BY** + +abstractDestinationPkg **PACKAGE** + +**BEHAVIOUR** abstractDestinationBeh; + +#### ATTRIBUTES + +abstractDestinationId + +GET SET-BY-CREATE; + +#### NOTIFICATIONS + +"CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, + +"CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, + +"CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; + +#### CONDITIONAL PACKAGES + +maxDigitsPkg + +PRESENT IF "supplied by managing system" , + +ringTimeLimitPkg + +PRESENT IF "supplied by managing system" ; + +REGISTERED AS {managedObjectClass 33}; + +abstractDestinationBeh BEHAVIOUR + +#### DEFINED AS + +"This entity is a result of digit processing in the originating, transit or gateway exchange."; + +### 5.1.5.2 Analysis criteria (analysisCriteria) + +analysisCriteria MANAGED OBJECT CLASS + +DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + +#### CHARACTERIZED BY + +analysisCriteriaPkg PACKAGE + +BEHAVIOUR analysisCriteriaBeh; + +#### ATTRIBUTES + +analysisCriteriaId + +GET SET-BY-CREATE, + +activeTargetPtr + +GET-REPLACE, + +callingPartyCategory + +GET-REPLACE, + +origin + +GET-REPLACE ; + +#### NOTIFICATIONS + +"CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, + +"CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, + +"CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; + +#### CONDITIONAL PACKAGES + +carrierDataPtrPkg + +PRESENT IF "the target is carrier dependent", + +destinationCodePkg + +PRESENT IF "in any case with exception of the case of one Point of Presence of the carrier " , + +destinationTypePkg + +PRESENT IF "destinationCodePkg is present"; + +REGISTERED AS {managedObjectClass 34}; + +analysisCriteriaBeh BEHAVIOUR + +#### DEFINED AS + +"This entity describes the management information needed to manage the internal digit trees."; + +### 5.1.5.3 Call routing circuit end point for broadband (crCircuitEndPointBb) + +crCircuitEndPointBb MANAGED OBJECT CLASS + +DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top; + +#### CHARACTERIZED BY + +``` + +"CCITT Rec. X.721 | ISO/IEC 10165-2":administrativeStatePackage, +crCircuitEndPointBbPkg PACKAGE + BEHAVIOUR crCircuitEndPointBbBeh; + ATTRIBUTES + crCircuitEndPointId + GET SET-BY-CREATE, + cic + GET SET-BY-CREATE, + propagationDelay + GET-REPLACE, + timeslotPtr + GET SET-BY-CREATE;; + CONDITIONAL PACKAGES + blockedForMaintenancePkg + PRESENT IF "supplied by the managing system", + remoteBlockingNbPkg + PRESENT IF "supplied by the managing system", + maintenanceSignallingRunningPkg + PRESENT IF "supplied by the managing system"; + REGISTERED AS {managedObjectClass 35}; + +crCircuitEndPointBbBeh BEHAVIOUR + DEFINED AS + "This object class represents a termination point of an individual circuit. The CIC value has to be + unique within the NNI access."; +``` + +#### 5.1.5.4 Call routing circuit end point subgroup for broadband (crCircuitEndPointSubgroupBb) + +``` + +crCircuitEndPointSubgroupBb MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top; + CHARACTERIZED BY + crCircuitEndPointSubgroupBbPkg PACKAGE + BEHAVIOUR crCircuitEndPointSubgroupBbBeh; + ATTRIBUTES + crCircuitEndPointSubgroupId + GET SET-BY-CREATE, + "ITU-T M.3100":userLabel + GET-REPLACE, + searchMethod + GET-REPLACE;; + REGISTERED AS {managedObjectClass 36}; + +crCircuitEndPointSubgroupBbBeh BEHAVIOUR + DEFINED AS + "This object class represents a set of circuit end points with similar characteristics. The value of the + signallingType attribute of the superior nniAccess object shall be equal 'nisup'."; +``` + +#### 5.1.5.5 Call routing office data (callRoutingOfficeData) + +``` + +callRoutingOfficeData MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + CHARACTERIZED BY + callRoutingOfficeDataPkg PACKAGE + BEHAVIOUR callRoutingOfficeDataBeh; + ATTRIBUTES +``` + +**callRoutingOfficeDataId** +**GET SET-BY-CREATE,** +**ownInternationalCode** +**GET-REPLACE ;** +**NOTIFICATIONS** +**"CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ;** +**REGISTERED AS {managedObjectClass 37};** + +**callRoutingOfficeDataBeh BEHAVIOUR** +**DEFINED AS** + +"This entity describes the office data concerning the call routing application. One instance of this object class shall be automatically created by the managed system upon completion of system initialization."; + +#### 5.1.5.6 Carrier data (carrierData) + +**carrierData MANAGED OBJECT CLASS** +**DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ;** +**CHARACTERIZED BY** + +**carrierDataPkg PACKAGE** + +**BEHAVIOUR carrierDataBeh;** + +**ATTRIBUTES** + +**carrierDataId** + +**GET SET-BY-CREATE,** + +**carrierCode** + +**GET SET-BY-CREATE;** + +**NOTIFICATIONS** + +**"CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation,** + +**"CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion,** + +**"CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ;** + +**CONDITIONAL PACKAGES** + +**carrierParameterRequiredPkg** + +**PRESENT IF "supplied by the managing system";** + +**REGISTERED AS {managedObjectClass 38};** + +**carrierDataBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the necessary information concerning carrier available within one exchange."; + +#### 5.1.5.7 Digit manipulation (digitManip) + +**digitManip MANAGED OBJECT CLASS** +**DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ;** +**CHARACTERIZED BY** + +**digitManipPkg PACKAGE** + +**BEHAVIOUR digitManipBeh;** + +**ATTRIBUTES** + +**digitManipId** + +**GET SET-BY-CREATE;** + +**NOTIFICATIONS** + +**"CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation,** + +**"CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion,** + +**"CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ;** + +**CONDITIONAL PACKAGES** + +**destinationTypePkg** + +**PRESENT IF "modification of digits effects a change of the type of number" ,** + +``` + +digitCombInsertPkg + PRESENT IF "supplied by managing system" , +digitCombReplacePkg + PRESENT IF "supplied by managing system" , +digitSuppressPkg + PRESENT IF "supplied by managing system" ; +REGISTERED AS {managedObjectClass 39}; + +digitManipBeh BEHAVIOUR + DEFINED AS + "This entity describes the possibility to manipulate the called number (sequence of digits) and/or the + destination type. Parts of the sequence or the whole number including the destination type may be + changed. It is also used for signalling purposes, i.e. it can be referenced from 'routeData'. It is + possible either to insert, to replace or to suppress digits. Reference for all changes is the original + string, start position is the first digit."; +``` + +#### 5.1.5.8 List of route termination points (listOfRouteTps) + +``` + +listOfRouteTps MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + CHARACTERIZED BY + listOfRouteTpsPkg PACKAGE + BEHAVIOUR listOfRouteTpsBeh; + ATTRIBUTES + listOfRouteTpsId + GET SET-BY-CREATE, + listOfRoutesPtrList + GET-REPLACE, + usedAlgorithm + GET-REPLACE ; + NOTIFICATIONS + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, + "CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; +REGISTERED AS {managedObjectClass 40}; + +listOfRouteTpsBeh BEHAVIOUR + DEFINED AS + "This entity describes a set of routes for a 'postAnalysisEvaluation' object. With it an ordered list of + possible routes (instance 'routeData') exists meeting the quality parameters required by attributes of + 'postAnalysisEvaluation'. Additionally, it describes the traffic distribution about the set of routes."; +``` + +#### 5.1.5.9 Local destination (localDestination) + +``` + +localDestination MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + CHARACTERIZED BY + localDestinationPkg PACKAGE + BEHAVIOUR localDestinationBeh; + ATTRIBUTES + localDestinationId + GET SET-BY-CREATE, + excludedSubscriberCodes + GET-REPLACE ADD-REMOVE, + initialSubscriberCodes + GET-REPLACE ADD-REMOVE; +``` + +#### NOTIFICATIONS + +"CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, +"CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, +"CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; + +#### CONDITIONAL PACKAGES + +localAreaCodePkg +PRESENT IF "E164 addresses or subfields are supported", +ringTimeLimitPkg +PRESENT IF "supplied by managing system" ; + +REGISTERED AS {managedObjectClass 41}; + +#### localDestinationBeh BEHAVIOUR + +##### DEFINED AS + +"This entity describes a set of terminating points within the exchange as the result of the digit analysis."; + +### 5.1.5.10 NNI access (nniAccess) + +#### nniAccess MANAGED OBJECT CLASS + +DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top; + +##### CHARACTERIZED BY + +#### nniAccessPkg PACKAGE + +BEHAVIOUR nniAccessBeh; + +##### ATTRIBUTES + +nniAccessId +GET SET-BY-CREATE, +signallingProtocol +GET SET-BY-CREATE, +networkBorder +GET-REPLACE, +linkType +GET-REPLACE, +originForRouting +GET-REPLACE, +sigRoutePtr +GET SET-BY-CREATE; ; ; + +#### CONDITIONAL PACKAGES + +networkTypePkg +PRESENT IF "supplied by the managing system"; + +REGISTERED AS {managedObjectClass 42}; + +#### nniAccessBeh BEHAVIOUR + +##### DEFINED AS + +"This object class is used to group the VPCs in broadband NNIs or equivalent narrowband links between two signalling points which are controlled by the same signalling protocol."; + +### 5.1.5.11 Prefix digit analysis (prefixDigitAnalysis) + +#### prefixDigitAnalysis MANAGED OBJECT CLASS + +DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + +##### CHARACTERIZED BY + +#### prefixDigitAnalysisPkg PACKAGE + +BEHAVIOUR prefixDigitAnalysisBeh; + +##### ATTRIBUTES + +prefixDigitAnalysisId +GET SET-BY-CREATE, +code +GET-REPLACE ADD-REMOVE, + +``` + +natureOfAddress + GET SET-BY-CREATE; +NOTIFICATIONS + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, + "CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; +REGISTERED AS {managedObjectClass 43}; + +prefixDigitAnalysisBeh BEHAVIOUR + DEFINED AS + "This entity describes the digits used as prefix dependent of the nature of the address." ; + +``` + +### 5.1.5.12 Post analysis evaluation (postAnalysisEvaluation) + +``` + +postAnalysisEvaluation MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + CHARACTERIZED BY + postAnalysisEvaluationPkg PACKAGE + BEHAVIOUR postAnalysisEvaluationBeh; + ATTRIBUTES + postAnalysisEvaluationId + GET SET-BY-CREATE, + activeListOfRouteTpsPtr + GET-REPLACE, + reqBandwidthEgress + GET-REPLACE, + reqBandwidthIngress + GET-REPLACE, + reqBearerCapab + GET-REPLACE ADD-REMOVE, + abstractDestinationPtr + GET-REPLACE, + transitDelayLimit + GET-REPLACE ; + NOTIFICATIONS + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, + "CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; + CONDITIONAL PACKAGES + reqNbTransferCapabilityPkg + PRESENT IF "narrowband transfer capability dependent routing required" ; + REGISTERED AS {managedObjectClass 44}; + +postAnalysisEvaluationBeh BEHAVIOUR + DEFINED AS + "This entity describes a set of information like abstractDestination and different quality parameters. + The required quality parameter of a certain call is compared with the defined value. For a certain + call only one instance has to match the required parameters. The network operator is responsible to + define a set of route selection criterias without gaps or overlapping parts." ; + +``` + +### 5.1.5.13 Route data (routeData) + +``` + +routeData MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + CHARACTERIZED BY + routeDataPkg PACKAGE + +``` + +``` + +BEHAVIOUR routeDataBeh; +ATTRIBUTES + routeDataId + GET SET-BY-CREATE, + linkGroupPtr + GET-REPLACE ; +NOTIFICATIONS + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, + "CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; +CONDITIONAL PACKAGES + digitManipPtrPkg + PRESENT IF "digit manipulation is required" , + minDigitsPkg + PRESENT IF "minimum number of digits for seizing required" , + sendTnsPkg + PRESENT IF "TNS has to be signalled" ; +REGISTERED AS {managedObjectClass 45}; + +routeDataBeh BEHAVIOUR + DEFINED AS + "This entity describes one element of the ordered list of routes ('listOfRouteTps')."; + +``` + +#### 5.1.5.14 Virtual path group (virtualPathGroup) + +``` + +virtualPathGroup MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top; + CHARACTERIZED BY + virtualPathGroupPkg PACKAGE + BEHAVIOUR virtualPathGroupBeh; + ATTRIBUTES + virtualPathGroupId + GET SET-BY-CREATE, + "ITU-T M.3100":userLabel + GET-REPLACE, + assignNonAssign + GET SET-BY-CREATE, + tpAndVpciPtrList + GET-REPLACE + ADD-REMOVE;;; + CONDITIONAL PACKAGES + searchMethodPkg + PRESENT IF "object instance is of type assign"; + REGISTERED AS {managedObjectClass 46}; + +virtualPathGroupBeh BEHAVIOUR + DEFINED AS + "This object class represents a set of end points of VPCs with similar characteristics. The VPCs can be distributed over one or more physical interfaces. One physical interface can contain VPCs of several object instances of the object class virtualPathGroup. All vpTTPBidirectional referenced by the tpAndVpciPtrList shall be administratively locked before the virtualPathGroup can be deleted."; + +``` + +#### 5.1.5.15 XTPSG combination (xtpsgComb) + +``` + +xtpsgComb MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top ; + CHARACTERIZED BY + +``` + +``` + +xtpsgCombPkg PACKAGE + BEHAVIOUR xtpsgCombBeh; + ATTRIBUTES + xtpsgCombId + GET SET-BY-CREATE, + listOfLinkGroupsPtrList + GET-REPLACE, + usedAlgorithm + GET-REPLACE ; + NOTIFICATIONS + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectCreation, + "CCITT Rec. X.721 | ISO/IEC 10165-2":objectDeletion, + "CCITT Rec. X.721 | ISO/IEC 10165-2":attributeValueChange ; ; ; +REGISTERED AS {managedObjectClass 47}; + +``` + +``` + +xtpsgCombBeh BEHAVIOUR + DEFINED AS + "This entity describes an ordered list of virtual path groups (vpg) or CEPSGs."; + +``` + +## 5.1.6 Circuit emulation service interworking fragment + +### 5.1.6.1 CES service profile (cesServiceProfile) + +``` + +cesServiceProfile MANAGED OBJECT CLASS + DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top; + CHARACTERIZED BY + cesServiceProfilePkg PACKAGE + BEHAVIOUR cesServiceProfileBeh; + ATTRIBUTES + cesServiceProfileId + GET SET-BY-CREATE, + cesBufferedCDVtolerance + GET-REPLACE, + channelAssociatedSignalling + GET-REPLACE;;; + REGISTERED AS {managedObjectClass 48}; + +``` + +``` + +cesServiceProfileBeh BEHAVIOUR + DEFINED AS + "This managed object is used to organize data that describes the circuit emulation service + interworking functions of the ATM NE. + + The cesBufferedCDVtolerance attribute specifies the duration of user data that must be + buffered by the interworkingVcTtpBidirectional managed object to offset Cell Delay variation. The + recommended default value for DS1 CES is 750 micro seconds and 1000 micro seconds for DS3 CES. + + The channelAssociatedSignalling attribute identifies which AAL1 format should be used. It + applies only to structured format. For unstructured format this attribute must be set to the default + value of basic. + + Instances of this object class shall be explicitly created and deleted by the managing system. + An instance of this object class shall not be deleted if it is in use by any + interworkingVcTtpBidirectional object instance."; +``` + +### 5.1.6.2 Interworking VC TTP Bidirectional (interworkingVcTtpBidirectional) + +**interworkingVcTtpBidirectional MANAGED OBJECT CLASS** + +**DERIVED FROM "CCITT Rec. I.751":vcTTPBidirectional;** + +**CHARACTERIZED BY** + +**interworkingVcTtpBidirectionalPkg PACKAGE** + +**BEHAVIOUR interworkingVcTtpBidirectionalBeh;** + +**ATTRIBUTES** + +**"ITU-T Rec. I.751":vpiValue** + +**GET,** + +**serviceProfilePointer** + +**GET-REPLACE,** + +**aalProfilePointer** + +**GET-REPLACE,** + +**terminationPointList** + +**GET SET-BY-CREATE;;;** + +**CONDITIONAL PACKAGES** + +**modifyTerminationPointListPkg** + +**PRESENT IF "an instance supports addition and removal of interworked termination points.";** + +**REGISTERED AS {managedObjectClass 49};** + +**interworkingVcTtpBidirectionalBeh BEHAVIOUR** + +**DEFINED AS** + +**"This managed object represents a point in the managed system where the interworking of a service (e.g. frame relay or SMDS) or an underlying physical infrastructure (e.g. nDS0/DS1/DS3/E3/J2) takes place. At this point ATM cells are generated from the service or physical bit stream or vice versa.** + +**An instance of this object class shall point (via the upstreamConnectivityPointer and downstreamConnectivityPointer attributes) to a vcCTPBidirectional managed object (if already created) and that instance of vcCTPBidirectional object class shall point back (via supportedByObjectList) to this instance of interworkingVcTtpBidirectional object class.** + +**For the conditional package oamCellLoopbackPkg inherited from vcTTPBidirectional object, the loopback cell shall be inserted at the interworkingVcTtpBidirectional side of the network element and the direction of the cell shall be into the switch. Thus the connection matrix of the interworking NE is included by the Loopback.** + +**This managed object shall send a communicationsAlarm notification to the managing system, when the cellLossIntegrationPeriod (identified by aalProfile) expires.** + +**Instances of this object class may be explicitly created and deleted by the managing system. Instances of this managed object class may also be automatically created by the managed system.";** + +## 5.2 Name bindings + +### 5.2.1 aalProfile-managedElementR1 + +**aalProfile-managedElementR1 NAME BINDING** + +**SUBORDINATE OBJECT CLASS aalProfile AND SUBCLASSES;** + +**NAMED BY SUPERIOR OBJECT CLASS "ITU-T Rec. M.3100":managedElementR1 AND SUBCLASSES;** + +**WITH ATTRIBUTE aalProfileId;** + +**CREATE** + +**WITH-REFERENCE-OBJECT,** + +**WITH-AUTOMATIC-INSTANCE-NAMING;** + +**DELETE** +    **DELETES-CONTAINED-OBJECTS;** +**REGISTERED AS {nameBinding 1};** + +### **5.2.2 aalProtocolCurrentData-interworkingVcTtpBidirectional** + +**aalProtocolCurrentData-interworkingVcTtpBidirectional NAME BINDING** +    **SUBORDINATE OBJECT CLASS aalProtocolCurrentData AND SUBCLASSES;** +    **NAMED BY SUPERIOR OBJECT CLASS interworkingVcTtpBidirectional AND SUBCLASSES;** +    **WITH ATTRIBUTE "ITU-T Rec. X.739":scannerId;** +    **CREATE** +        **WITH-REFERENCE-OBJECT,** +        **WITH-AUTOMATIC-INSTANCE-NAMING;** +    **DELETE** +        **DELETES-CONTAINED-OBJECTS;** +**REGISTERED AS {nameBinding 2};** + +### **5.2.3 abstractDestination-managedElementR1** + +**abstractDestination-managedElementR1 NAME BINDING** +    **SUBORDINATE OBJECT CLASS abstractDestination** +        **AND SUBCLASSES ;** +    **NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1** +        **AND SUBCLASSES ;** +    **WITH ATTRIBUTE abstractDestinationId ;** +    **CREATE** +        **WITH-AUTOMATIC-INSTANCE-NAMING;** +    **DELETE ;** +**REGISTERED AS {nameBinding 3};** + +### **5.2.4 analysisCriteria-managedElementR1** + +**analysisCriteria-managedElementR1 NAME BINDING** +    **SUBORDINATE OBJECT CLASS analysisCriteria** +        **AND SUBCLASSES ;** +    **NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1** +        **AND SUBCLASSES ;** +    **WITH ATTRIBUTE analysisCriteriaId ;** +    **CREATE** +        **WITH-AUTOMATIC-INSTANCE-NAMING;** +    **DELETE ;** +**REGISTERED AS {nameBinding 4};** + +### **5.2.5 bearerServiceBb-customerProfileBb** + +**bearerServiceBb-customerProfileBb NAME BINDING** +    **SUBORDINATE OBJECT CLASS bearerServiceBb** +        **AND SUBCLASSES;** +    **NAMED BY SUPERIOR OBJECT CLASS customerProfileBb** +        **AND SUBCLASSES;** +    **WITH ATTRIBUTE "ITU-T Q.824.0":bearerServiceId;** +    **CREATE;** +    **DELETE;** +**REGISTERED AS {nameBinding 5};** + +### 5.2.6 callingNumberScreeningBb-uniAccess + +callingNumberScreeningBb-uniAccess NAME BINDING +SUBORDINATE OBJECT CLASS callingNumberScreeningBb AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS uniAccess +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Q.824.1":callingNumberScreeningId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; +REGISTERED AS {nameBinding 6}; + +### 5.2.7 callRoutingOfficeData-managedElementR1 + +callRoutingOfficeData-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS callRoutingOfficeData +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE callRoutingOfficeDataId ; +REGISTERED AS {nameBinding 7}; + +### 5.2.8 carrierData-managedElementR1 + +carrierData-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS carrierData +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE carrierDataId ; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE ; +REGISTERED AS {nameBinding 8}; + +### 5.2.9 cesServiceProfile-managedElementR1 + +cesServiceProfile-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS cesServiceProfile +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE cesServiceProfileId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; +REGISTERED AS {nameBinding 9}; + +### **5.2.10 connectedNumberScreeningBb-uniAccess** + +**connectedNumberScreeningBb-uniAccess NAME BINDING +SUBORDINATE OBJECT CLASS connectedNumberScreeningBb AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS uniAccess +AND SUBCLASSES; +WITH ATTRIBUTE connectedNumberScreeningId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; +REGISTERED AS {nameBinding 10};** + +### **5.2.11 crCircuitEndPoint-crCircuitEndPointSubgroupBb** + +**crCircuitEndPointBb-crCircuitEndPointSubgroupBb NAME BINDING +SUBORDINATE OBJECT CLASS crCircuitEndPointBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS crCircuitEndPointSubgroupBb +AND SUBCLASSES; +WITH ATTRIBUTE crCircuitEndPointId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 11};** + +### **5.2.12 crCircuitEndPointSubgroupBb-nniAccess** + +**crCircuitEndPointSubgroupBb-nniAccess NAME BINDING +SUBORDINATE OBJECT CLASS crCircuitEndPointSubgroupBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS nniAccess +AND SUBCLASSES; +WITH ATTRIBUTE crCircuitEndPointSubgroupId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; +REGISTERED AS {nameBinding 12};** + +### **5.2.13 customerProfileBb-managedElementR1** + +**customerProfileBb-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS customerProfileBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Q.824.0":customerProfileId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 13};** + +#### **5.2.14 customizedResourceBb-customerProfileBb** + +**customizedResourceBb-customerProfileBb NAME BINDING +SUBORDINATE OBJECT CLASS customizedResourceBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS customerProfileBb +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Q.824.0":customizedResourceId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 14};** + +#### **5.2.15 digitManip-managedElementR1** + +**digitManip-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS digitManip +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE digitManipId ; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE ; +REGISTERED AS {nameBinding 15};** + +#### **5.2.16 directoryNumberE164-managedElementR1** + +**directoryNumberE164-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS directoryNumberE164 +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Rec. Q.824.0":directoryNumberId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 16};** + +#### **5.2.17 listOfRouteTps-managedElementR1** + +**listOfRouteTps-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS listOfRouteTps +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE listOfRouteTpsId ; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE ; +REGISTERED AS {nameBinding 17};** + +### **5.2.18 localDestination-managedElementR1** + +**localDestination-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS localDestination +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE localDestinationId ; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE ; +REGISTERED AS {nameBinding 18};** + +### **5.2.19 nniAccess-managedElementR1** + +**nniAccess-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS nniAccess AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES; +WITH ATTRIBUTE nniAccessId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; +REGISTERED AS {nameBinding 19};** + +### **5.2.20 postAnalysisEvaluation-managedElementR1** + +**postAnalysisEvaluation-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS postAnalysisEvaluation +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE postAnalysisEvaluationId ; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE ; +REGISTERED AS {nameBinding 20};** + +### **5.2.21 prefixDigitAnalysis-managedElementR1** + +**prefixDigitAnalysis-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS prefixDigitAnalysis +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE prefixDigitAnalysisId ; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE ; +REGISTERED AS {nameBinding 21};** + +### **5.2.22 routeData-managedElementR1** + +**routeData-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS routeData +AND SUBCLASSES ; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES ; +WITH ATTRIBUTE routeDataId ; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE ; +REGISTERED AS {nameBinding 22};** + +### **5.2.23 saalUniProtocolProfile-managedElementR1** + +**saalUniProtocolProfile-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS saalUniProtocolProfile +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T Rec. M.3100":managedElementR1 +AND SUBCLASSES; +WITH ATTRIBUTE saalUniProtocolProfileId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 23};** + +### **5.2.24 supplementaryServiceDepBb-bearerServiceBb** + +**supplementaryServiceDepBb-bearerServiceBb NAME BINDING +SUBORDINATE OBJECT CLASS supplementaryServiceDepBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS bearerServiceBb +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Q.824.0":supplementaryServiceId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 24};** + +### **5.2.25 supplementaryServiceDepBb-teleserviceBb** + +**supplementaryServiceDepBb-teleserviceBb NAME BINDING +SUBORDINATE OBJECT CLASS supplementaryServiceDepBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS teleserviceBb +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Q.824.0":supplementaryServiceId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 25};** + +### **5.2.26 supplementaryServiceIndBb-customerProfileBb** + +**supplementaryServiceIndBb-customerProfileBb NAME BINDING +SUBORDINATE OBJECT CLASS supplementaryServiceIndBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS customerProfileBb +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Q.824.0":supplementaryServiceId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 26};** + +### **5.2.27 sVpTtp-managedElementR1** + +The name binding to managedElementR1 and subclasses as defined in Recommendation I.751 [4] for subclasses of vpTTPBidirectional is used. + +### **5.2.28 teleserviceBb-customerProfileBb** + +**teleserviceBb-customerProfileBb NAME BINDING +SUBORDINATE OBJECT CLASS teleserviceBb +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS customerProfileBb +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Q.824.0":teleserviceId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 27};** + +### **5.2.29 userData-customerProfileBb** + +**userData-customerProfileBb NAME BINDING +SUBORDINATE OBJECT CLASS userData +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS customerProfileBb +AND SUBCLASSES; +WITH ATTRIBUTE userDataId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {nameBinding 28};** + +### **5.2.30 uniAccess-managedElementR1** + +**uniAccess-managedElementR1 NAME BINDING +SUBORDINATE OBJECT CLASS uniAccess AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 +AND SUBCLASSES; +WITH ATTRIBUTE uniAccessId; +CREATE** + +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**ONLY-IF-NO-CONTAINED-OBJECTS;** +**REGISTERED AS {nameBinding 29};** + +### **5.2.31 vcCTPBidirectional-managedElementR1** + +**vcCTPBidirectional-managedElementR1 NAME BINDING** +**SUBORDINATE OBJECT CLASS "ITU-T L.751":vcCTPBidirectional AND SUBCLASSES ;** +**NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1 AND SUBCLASSES ;** +**WITH ATTRIBUTE "ITU-T M.3100":cTPId ;** +**BEHAVIOUR** +**vcCTPBidirectional-managedElementR1Behaviour BEHAVIOUR** +**DEFINED AS** +**"The value of vcCTPId attribute (VCI value) in the vcCTPBidirectional object is used internal to the** +**ATM Network Element and the value it is given is a local matter.";;** +**CREATE** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**ONLY-IF-NO-CONTAINED-OBJECTS;** +**REGISTERED AS {nameBinding 30};** + +### **5.2.32 virtualPathGroup-nniAccess** + +**virtualPathGroup-nniAccess NAME BINDING** +**SUBORDINATE OBJECT CLASS virtualPathGroup AND SUBCLASSES;** +**NAMED BY SUPERIOR OBJECT CLASS nniAccess** +**AND SUBCLASSES;** +**WITH ATTRIBUTE virtualPathGroupId;** +**CREATE** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE;** +**REGISTERED AS {nameBinding 31};** + +### **5.2.33 xtpsgComb-managedElementR1** + +**xtpsgComb-managedElementR1 NAME BINDING** +**SUBORDINATE OBJECT CLASS xtpsgComb** +**AND SUBCLASSES ;** +**NAMED BY SUPERIOR OBJECT CLASS "ITU-T M.3100":managedElementR1** +**AND SUBCLASSES ;** +**WITH ATTRIBUTE xtpsgCombId ;** +**CREATE** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE ;** +**REGISTERED AS {nameBinding 32};** + +### 5.3 Definition of packages + +#### 5.3.1 Paquetage "paramètre de performance de couche AAL de type 1" (aalTypeOnePerformanceParameterPkg) + +**aalTypeOnePerformanceParameterPkg** PACKAGE +ATTRIBUTES +    sequenceViolations +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    cellLoss +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    cellMisinsertion +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    bufferUnderflows +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    bufferOverflows +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    headerErrors +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    stdPointerReframes +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    stdPointerParityFailures +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET; +REGISTERED AS {package 1}; + +#### 5.3.2 AAL type 1 performance parameter history data package (aalTypeOnePerformanceParameterHistoryDataPkg) + +**aalTypeOnePerformanceParameterHistoryDataPkg** PACKAGE +ATTRIBUTES +    sequenceViolations +        GET, +    cellLoss +        GET, +    cellMisinsertion +        GET, +    bufferUnderflows +        GET, +    bufferOverflows +        GET, + +``` + +headerErrors + GET, +stdPointerReframes + GET, +stdPointerParityFailures + GET; +REGISTERED AS {package 2}; + +``` + +### 5.3.3 AAL type 1 profile package (aalTypeOneProfilePkg) + +``` + +aalTypeOneProfilePkg PACKAGE + ATTRIBUTES + cbrRate + GET, + cellLossIntegrationPeriod + GET, + clockRecoveryType + GET, + forwardErrorCorrectionMethod + GET, + partiallyFilledCells + GET, + structuredDataTransfer + GET, + subType + GET; +REGISTERED AS {package 3}; + +``` + +### 5.3.4 AAL type 3/4 performance parameter package (aalTypeThreeFourPerformanceParameterPkg) + +``` + +aalTypeThreeFourPerformanceParameterPkg PACKAGE + ATTRIBUTES + sumOfInvalidSARFieldErrors + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, + sumOfIncorrectSARFieldErrors + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, + sarCrcViolations + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, + comsEomsUnexpectedSN + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, + bomsEomsUnexpectedMID + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, + sriTimeOuts + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, + +``` + +``` + +numberOfAborts + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, +sumOfInvalidCSFieldErrors + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, +sumOfIncorrectCSFieldErrors + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, +bETagMismatch + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, +lengthBASizeMismatch + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET, +lengthMismatch + REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1DefinedTypesModule.integerZero + GET; +REGISTERED AS {package 4}; + +``` + +### 5.3.5 AAL type 3/4 performance parameter history data package (aalTypeThreeFourPerformanceParameterHistoryDataPkg) + +``` + +aalTypeThreeFourPerformanceParameterHistoryDataPkg PACKAGE + ATTRIBUTES + sumOfInvalidSARFieldErrors + GET, + sumOfIncorrectSARFieldErrors + GET, + sarCrcViolations + GET, + comsEomsUnexpectedSN + GET, + bomsEomsUnexpectedMID + GET, + sriTimeOuts + GET, + numberOfAborts + GET, + sumOfInvalidCSFieldErrors + GET, + sumOfIncorrectCSFieldErrors + GET, + bETagMismatch + GET, + lengthBASizeMismatch + GET, + lengthMismatch + GET; + REGISTERED AS {package 5}; + +``` + +### 5.3.6 AAL type 3/4 profile package (aalTypeThreeFourProfilePkg) + +**aalTypeThreeFourProfilePkg** PACKAGE +ATTRIBUTES +    maxCpcsPduSize +        GET, +    midRange +        GET, +    aalMode +        GET, +    sscsType +        GET; +REGISTERED AS {package 6}; + +### 5.3.7 AAL type 5 performance parameter package (aalTypeFivePerformanceParameterPkg) + +**aalTypeFivePerformanceParameterPkg** PACKAGE +ATTRIBUTES +    sumOfInvalidCSFieldErrors +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    crcViolations +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET, +    reassembleTimerExpirations +        REPLACE-WITH-DEFAULT +        DEFAULT VALUE ASN1DefinedTypesModule.integerZero +        GET; +REGISTERED AS {package 7}; + +### 5.3.8 AAL type 5 performance parameter history data package (aalTypeFivePerformanceParameterHistoryDataPkg) + +**aalTypeFivePerformanceParameterHistoryDataPkg** PACKAGE +ATTRIBUTES +    sumOfInvalidCSFieldErrors +        GET, +    crcViolations +        GET, +    reassembleTimerExpirations +        GET; +REGISTERED AS {package 8}; + +### 5.3.9 AAL type 5 profile package (aalTypeFiveProfilePkg) + +**aalTypeFiveProfilePkg** PACKAGE +ATTRIBUTES +    maxCpcsPduSize +        GET, +    aalMode +        GET, +    sscsType +        GET; +REGISTERED AS {package 9}; + +### 5.3.10 Blocked for maintenance package (blockedForMaintenancePkg) + +``` +blockedForMaintenancePkg PACKAGE + ATTRIBUTES + blockedForMaintenance + DEFAULT VALUE ASN1DefinedTypesModule.defaultBlockedForMaintenance + GET-REPLACE; +REGISTERED AS {package 10}; +``` + +### 5.3.11 Calling line identification presentation for broadband package (clipBbPkg) + +``` +clipBbPkg PACKAGE + BEHAVIOUR clipBbBeh; + ATTRIBUTES + "ITU-T Q.824.2": noRestrictionsAllowed + GET-REPLACE;; + +clipBbBeh BEHAVIOUR + DEFINED AS + "This Supplementary Service (described in Rec. Q.2951.3) provides the called party with the + possibility of receiving identification of the calling party. In addition to the ISDN number, the calling + line identity may include a subaddress generated by the calling user and transparently transported + by the network. The network shall deliver the calling line identity to the called party during call + establishment, regardless of the terminal capability to handle the information."; +``` + +### 5.3.12 Calling line identification restriction for broadband package (clirBbPkg) + +``` +clirBbPkg PACKAGE + BEHAVIOUR clirBbBeh; + ATTRIBUTES + "ITU-T Q.824.2": callIdRestrictionOptions + GET-REPLACE;; + +clirBbBeh BEHAVIOUR + DEFINED AS + "This Supplementary Service (described in Rec. Q.2951.4) provides the calling party with the + possibility to prevent presentation of the calling party's ISDN number, and subaddress information + (if any) to the called party. If the called party subscribes to the CLIP Supplementary Service then + the called party shall receive an indication that the calling party information is not available due to + restriction."; +``` + +### 5.3.13 Carrier data pointer package (carrierDataPtrPkg) + +``` +carrierDataPtrPkg PACKAGE + ATTRIBUTES + carrierDataPtr + GET SET-BY-CREATE; +REGISTERED AS {package 11}; +``` + +### 5.3.14 Carrier parameter required package (carrierParameterRequiredPkg) + +``` +carrierParameterRequiredPkg PACKAGE + ATTRIBUTES + cspRequired + GET-REPLACE, +``` + +``` + + cipRequired + GET-REPLACE; +REGISTERED AS {package 12}; + +``` + +### 5.3.15 Closed user group subscription option package for broadband (cugSubscriptionOptionBbPkg) + +``` + +cugSubscriptionOptionBbPkg PACKAGE + BEHAVIOUR cugSubscriptionOptionBbBeh; + ATTRIBUTES + preferredCugIndex + GET-REPLACE, + interCugAccess + GET-REPLACE;; + +cugSubscriptionOptionBbBeh BEHAVIOUR + DEFINED AS + "The CUG subscription options object may only be instantiated if either attribute + preferredCugIndex is assigned a non-NULL value or attribute interCugAccess is not empty. M_SET + operations which would result in preferredCugIndex value NULL and interCugAccess value empty + set are not allowed. The value of attribute preferredCugIndex should not be NULL when + interCugvalue is 'none' or 'incomingaccess'."; +``` + +### 5.3.16 Connected line identification presentation for broadband package (colpBbPkg) + +``` + +colpBbPkg PACKAGE + BEHAVIOUR colpBbBeh; + ATTRIBUTES + noColpRestrictionsAllowed + GET-REPLACE;; + +colpBbBeh BEHAVIOUR + DEFINED AS + "This Supplementary Service (described in Rec. Q.2951.5) provides the calling party with the + possibility of receiving identification of the connected party."; +``` + +### 5.3.17 Connected line identification restriction for broadband package (colrBbPkg) + +``` + +colrBbPkg PACKAGE + BEHAVIOUR colrBbBeh; + ATTRIBUTES + connLineIdRestrictionOptions + GET-REPLACE;; + +colrBbBeh BEHAVIOUR + DEFINED AS + "This Supplementary Service (described in Rec. Q.2951.6) provides the called party with the + possibility to prevent presentation of the connected party's ISDN number, and subaddress + information (if any) to the calling party."; +``` + +### 5.3.18 Customer profile pointers behaviour package (customerProfilePointersBehPkg) + +``` + +customerProfilePointersBehPkg PACKAGE + BEHAVIOUR customerProfilePointersBeh; +REGISTERED AS {package 13}; + +``` + +**customerProfilePointersBeh BEHAVIOUR** + +**DEFINED AS** + +"The attribute 'customerProfilePtr' in the slave objects are synchronized with the pointers in the master customer profile object. That is, when the pointers in the associated customer profile object are changed, the 'customerProfilePtr' in the slave objects are updated accordingly."; + +### **5.3.19 Customized resource pointers behaviour package (customizedResourcePointersBehPkg)** + +**customizedResourcePointersBehPkg PACKAGE** + +**BEHAVIOUR customizedResourcePointersBeh;** + +**REGISTERED AS {package 14};** + +**customizedResourcePointersBeh BEHAVIOUR** + +**DEFINED AS** + +"The attribute 'customizedResourcePtrList' in the slave objects are synchronized with the pointers in the master customized resource object. That is, when the pointers in the associated customized resource object are changed, the 'customizedResourcePtrList' in the slave objects are updated accordingly."; + +### **5.3.20 Destination code package (destinationCodePkg)** + +**destinationCodePkg PACKAGE** + +**ATTRIBUTES** + +**destinationCode** + +**GET SET-BY-CREATE;** + +**REGISTERED AS {package 15};** + +### **5.3.21 Destination type package (destinationTypePkg)** + +**destinationTypePkg PACKAGE** + +**ATTRIBUTES** + +**destinationType** + +**GET SET-BY-CREATE;** + +**REGISTERED AS {package 16};** + +### **5.3.22 Digit combination insertion package (digitCombInsertPkg)** + +**digitCombInsertPkg PACKAGE** + +**ATTRIBUTES** + +**digitCombInsert** + +**GET-REPLACE ADD-REMOVE ;** + +**REGISTERED AS {package 17};** + +### **5.3.23 Digit combination replace package (digitCombReplacePkg)** + +**digitCombReplacePkg PACKAGE** + +**ATTRIBUTES** + +**digitCombReplace** + +**GET-REPLACE ADD-REMOVE ;** + +**REGISTERED AS {package 18};** + +### **5.3.24 Digit manipulation pointer package (digitManipPtrPkg)** + +**digitManipPtrPkg PACKAGE** +**ATTRIBUTES** +**digitManipPtr** +**GET-REPLACE ;** +**REGISTERED AS {package 19};** + +### **5.3.25 Digit suppression package (digitSuppressPkg)** + +**digitSuppressPkg PACKAGE** +**ATTRIBUTES** +**digitSuppress** +**GET-REPLACE ADD-REMOVE ;** +**REGISTERED AS {package 20};** + +### **5.3.26 Local area code package (localAreaCodePkg)** + +**localAreaCodePkg PACKAGE** +**ATTRIBUTES** +**localAreaCode** +**GET-REPLACE;** +**REGISTERED AS {package 21};** + +### **5.3.27 Maintenance signalling running package (maintenanceSignallingRunningPkg)** + +**maintenanceSignallingRunningPkg PACKAGE** +**ATTRIBUTES** +**maintenanceSignallingRunning** +**INITIAL VALUE DERIVATION RULE setByManagerBeh** +**GET;** +**REGISTERED AS {package 22};** + +### **5.3.28 Maximum digits package (maxDigitsPkg)** + +**maxDigitsPkg PACKAGE** +**ATTRIBUTES** +**maxDigits** +**GET-REPLACE ;** +**REGISTERED AS {package 23};** + +### **5.3.29 Minimum digits package (minDigitsPkg)** + +**minDigitsPkg PACKAGE** +**ATTRIBUTES** +**minDigits** +**GET-REPLACE ;** +**REGISTERED AS {package 24};** + +### 5.3.30 Modify termination point list package (modifyTerminationPointListPkg) + +modifyTerminationPointListPkg PACKAGE +ACTIONS +    addTerminationPoint, +    removeTerminationPoint; +REGISTERED AS {package 25}; + +### 5.3.31 Network type package (networkTypePkg) + +networkTypePkg PACKAGE +ATTRIBUTES +    networkType +        GET SET-BY-CREATE; +REGISTERED AS {package 26}; + +### 5.3.32 Origin mark package (originMarkPkg) + +originMarkPkg PACKAGE +ATTRIBUTES +    originMark +        GET-REPLACE; +REGISTERED AS {package 27}; + +### 5.3.33 Poll after retransmission package (pollAfterRetransmissionPkg) + +pollAfterRetransmissionPkg PACKAGE +BEHAVIOUR pollAfterRetransmissionPkgBeh; +ATTRIBUTES +    pollAfterRetransmission +        GET SET-BY-CREATE; +REGISTERED AS {package 28}; + +pollAfterRetransmissionPkgBeh BEHAVIOUR +DEFINED AS +    "This package should be used, if the poll after retransmission can be selected at creation time of a saalUniProtocolProfile."; + +### 5.3.34 Preferred carrier package (preferredCarrierPkg) + +preferredCarrierPkg PACKAGE +ATTRIBUTES +    preferredCarrier +        GET-REPLACE; +REGISTERED AS {package 29}; + +### 5.3.35 Propagation delay package (propagationDelayPkg) + +propagationDelayPkg PACKAGE +ATTRIBUTES +    propagationDelay +        GET-REPLACE; +REGISTERED AS {package 30}; + +### **5.3.36 Remote blocking package (remoteBlockingPkg)** + +**remoteBlockingPkg PACKAGE** +**ATTRIBUTES** +**remoteBlocking** +**INITIAL VALUE DERIVATION RULE setByManagerBeh** +**GET;** +**REGISTERED AS {package 31};** + +### **5.3.37 Remote blocking narrowband package (remoteBlockingNbPkg)** + +**remoteBlockingNbPkg PACKAGE** +**ATTRIBUTES** +**remoteBlocking** +**INITIAL VALUE DERIVATION RULE setByManagerBeh** +**GET,** +**remoteBlockingReason** +**INITIAL VALUE DERIVATION RULE setByManagerBeh** +**GET;** +**REGISTERED AS {package 32};** + +### **5.3.38 Required narrowband transfer capability package (reqNbTransferCapabilityPkg)** + +**reqNbTransferCapabilityPkg PACKAGE** +**ATTRIBUTES** +**reqNbTransferCapability** +**GET-REPLACE ADD-REMOVE;** +**REGISTERED AS {package 33};** + +### **5.3.39 Ring time limit package (ringTimeLimitPkg)** + +**ringTimeLimitPkg PACKAGE** +**ATTRIBUTES** +**ringTimeLimit** +**GET-REPLACE ;** +**REGISTERED AS {package 34};** + +### **5.3.40 Search method package (searchMethodPkg)** + +**searchMethodPkg PACKAGE** +**ATTRIBUTES** +**searchMethod** +**GET-REPLACE;** +**REGISTERED AS {package 35};** + +### **5.3.41 Send TNS package (sendTnsPkg)** + +**sendTnsPkg PACKAGE** +**ATTRIBUTES** +**sendTns** +**GET-REPLACE ;** +**REGISTERED AS {package 36};** + +### 5.3.42 Signalling channel pointer package (signallingChannelPtrPkg) + +signallingChannelPtrPkg PACKAGE +ATTRIBUTES +    aalPtr +        GET-REPLACE, +    signallingChannelPtr +        GET SET-BY-CREATE; +REGISTERED AS {package 37}; + +### 5.3.43 Signalling type package (signallingTypePkg) + +signallingTypePkg PACKAGE +ATTRIBUTES +    signallingType +        DEFAULT VALUE ASN1DefinedTypesModule.defaultSignallingType +        GET SET-BY-CREATE; +REGISTERED AS {package 38}; + +### 5.3.44 Sub-addressing for broadband package (subBbPkg) + +subBbPkg PACKAGE +BEHAVIOUR subBbBeh;; + +subBbBeh BEHAVIOUR +DEFINED AS +    "This Supplementary Service (described in Rec. Q.2951.8) provides the called user to expand his addressing capacity beyond the one given by the ISDN number."; + +### 5.3.45 Two calling party number delivery package (twoCallingPartyNumberDeliveryPkg) + +twoCallingPartyNumberDeliveryPkg PACKAGE +ATTRIBUTES +    twoCallingPartyNumberDelivery +        DEFAULT VALUE ASN1DefinedTypesModule.defaultTwoCallingPartyNumberDelivery +        GET-REPLACE; +REGISTERED AS {package 39}; + +### 5.3.46 User to user signalling for broadband package (userToUserSignallingBbPkg) + +userToUserSignallingBbPkg PACKAGE +BEHAVIOUR userToUserSignallingBbBeh;; + +userToUserSignallingBbBeh BEHAVIOUR +DEFINED AS +    "This service allows an ISDN subscriber to send/receive a limited amount of information to/from another ISDN subscriber over the signalling channel associated with their call according to Rec. Q.2957."; + +## 5.4 Definition of attributes + +### 5.4.1 AAL mode (aalMode) + +**aalMode ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.AalMode; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR aalModeBeh; +REGISTERED AS {attribute 1}; + +**aalModeBeh BEHAVIOUR** +DEFINED AS +"This attribute indicates whether the AAL for the supporting VCC is operating in message mode or streaming mode, assured or unassured."; + +### 5.4.2 AAL pointer (aalPtr) + +**aalPtr ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ObjectInstance; +MATCHES FOR EQUALITY; +BEHAVIOUR aalPtrBeh; +REGISTERED AS {attribute 2}; + +**aalPtrBeh BEHAVIOUR** +DEFINED AS +"This attribute identifies the associated object which represents the functions performed at the ATM adaptation layer."; + +### 5.4.3 AAL profile identifier (aalProfileId) + +**aalProfileId ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType; +MATCHES FOR EQUALITY; +BEHAVIOUR aalProfileIdBeh; +REGISTERED AS {attribute 3}; + +**aalProfileIdBeh BEHAVIOUR** +DEFINED AS +"This attribute can be used as an RDN when naming an instance of the aalProfile managed object class."; + +### 5.4.4 AAL profile pointer (aalProfilePointer) + +**aalProfilePointer ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PointerOrNull; +MATCHES FOR EQUALITY; +BEHAVIOUR aalProfilePointerBeh; +REGISTERED AS {attribute 4}; + +**aalProfilePointerBeh BEHAVIOUR** +DEFINED AS +"This attribute provides a pointer to an aalProfile managed object instance that defines the common ATM Adaptation Layer processing needed."; + +### 5.4.5 AAL type (aalType) + +**aalType ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.AalType; +MATCHES FOR EQUALITY; + +**BEHAVIOUR aalTypeBeh;** +**REGISTERED AS {attribute 5};** + +**aalTypeBeh BEHAVIOUR** +**DEFINED AS** + +**"This attribute identifies the AAL Type. Valid types are AAL1, AAL3/4, and AAL5."**; + +#### **5.4.6 Abstract destination identifier (abstractDestinationId)** + +**abstractDestinationId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR abstractDestinationIdBeh;** +**REGISTERED AS {attribute 6};** + +**abstractDestinationIdBeh BEHAVIOUR** +**DEFINED AS** + +**"This entity describes the object identifier attribute of the object class 'abstractDestination'."** ; + +#### **5.4.7 Abstract destination pointer (abstractDestinationPtr)** + +**abstractDestinationPtr ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.AbstractDestinationPtr ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR abstractDestinationPtrBeh;** +**REGISTERED AS {attribute 7};** + +**abstractDestinationPtrBeh BEHAVIOUR** +**DEFINED AS** + +**"This entity describes the pointer to the instance of 'abstractDestination'."** ; + +#### **5.4.8 Access pointer list (accessPtrList)** + +**accessPtrList ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SetOfInstances;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR accessPtrListBeh;** +**REGISTERED AS {attribute 8};** + +**accessPtrListBeh BEHAVIOUR** +**DEFINED AS** + +**"This is a set-valued attribute whose value(s) points to instances of the Access object class or its subclasses."**; + +#### **5.4.9 Active list of route termination points pointer (activeListOfRouteTpsPtr)** + +**activeListOfRouteTpsPtr ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ActiveListOfRouteTpsPtr ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR activeListOfRouteTpsPtrBeh;** +**REGISTERED AS {attribute 9};** + +**activeListOfRouteTpsPtrBeh BEHAVIOUR** +**DEFINED AS** + +**"This entity describes the pointer to the selected 'ListOfRouteTps' object, which contains an ordered list of instances of 'routeData' matching the selection criteria."** ; + +#### **5.4.10 Active target pointer (activeTargetPtr)** + +**activeTargetPtr ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ActiveTargetPtr ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR activeTargetPtrBeh;** +**REGISTERED AS {attribute 10};** + +**activeTargetPtrBeh BEHAVIOUR** +**DEFINED AS** +**"This entity describes the target which is currently addressed by the 'analysisCriteria' instance."**; + +#### **5.4.11 Analysis criteria identifier (analysisCriteriaId)** + +**analysisCriteriaId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR analysisCriteriaIdBeh;** +**REGISTERED AS {attribute 11};** + +**analysisCriteriaIdBeh BEHAVIOUR** +**DEFINED AS** +**"This entity describes the object identifier attribute of the object class 'analysisCriteria' ;** + +#### **5.4.12 Assign non-assign (assignNonAssign)** + +**assignNonAssign ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.AssignNonAssign;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR assignNonAssignBeh;** +**REGISTERED AS {attribute 12};** + +**assignNonAssignBeh BEHAVIOUR** +**DEFINED AS** +**"Indicates whether the exchange is for the VPC's of this object instance the assigning or the nonassigning exchange."**; + +#### **5.4.13 B/E tag mismatch (bETagMismatch)** + +**bETagMismatch ATTRIBUTE** +**DERIVED FROM "ITU-T Rec. X.721":counter;** +**BEHAVIOUR bETagMismatchBeh;** +**REGISTERED AS {attribute 13};** + +**bETagMismatchBeh BEHAVIOUR** +**DEFINED AS** +**"This attribute represents the number of times an incoming CS\_PDU had a BTag field value that did not equal the ETag field value."**; + +#### **5.4.14 Blocked for maintenance (blockedForMaintenance)** + +**blockedForMaintenance ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.BlockedForMaintenance;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR blockedForMaintenanceBeh;** +**REGISTERED AS {attribute 14};** + +**blockedForMaintenanceBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute indicates the blocking state of the virtual path and is typically used when creating new VPs. A blocked virtual path cannot be selected for new non-test traffic; however it can be used for test calls. The blocking of a virtual path has no influence on existing calls (non-test calls and test calls)."; + +#### **5.4.15 BOM/EOM unexpected MID (bomsEomsUnexpectedMID)** + +**bomsEomsUnexpectedMID ATTRIBUTE** + +**DERIVED FROM "ITU-T Rec. X.721":counter;** + +**BEHAVIOUR bomsEomsUnexpectedMIDBeh;** + +**REGISTERED AS {attribute 15};** + +**bomsEomsUnexpectedMIDBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute represents the number of BOM/EOM segments with an unexpected MID value. This attribute will be incremented by one each time a BOM is received with a currently active MID (a MID for which an EOM has not yet been received), or when an EOM is received for which a MID is NOT currently active. "; + +#### **5.4.16 Buffer overflows (bufferOverflows)** + +**bufferOverflows ATTRIBUTE** + +**DERIVED FROM "ITU-T Rec. X.721":counter;** + +**BEHAVIOUR bufferOverflowsBeh;** + +**REGISTERED AS {attribute 16};** + +**bufferOverflowsBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute represents a count of the number of times the reassembly buffer overflows. If the interworking function is implemented with multiple buffers, such as a cell level buffer and a bit level buffer, then either buffer overflow will cause this count to be incremented."; + +#### **5.4.17 Buffer release (bufferRelease)** + +**bufferRelease ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.BufferRelease;** + +**BEHAVIOUR bufferReleaseBeh;** + +**REGISTERED AS {attribute 17};** + +**bufferReleaseBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute determines whether SSCOP can release its transmission buffer and transmission queue on connection release and can selectively release messages from the transmission buffer when older messages are still outstanding."; + +#### **5.4.18 Buffer underflows (bufferUnderflows)** + +**bufferUnderflows ATTRIBUTE** + +**DERIVED FROM "ITU-T Rec. X.721":counter;** + +**BEHAVIOUR bufferUnderflowsBeh;** + +**REGISTERED AS {attribute 18};** + +**bufferUnderflowsBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute represents a count the number of times the reassembly buffer underflows. In the case of a continuous underflow caused by a loss of ATM cell flow, a single buffer underflow should be counted. If the interworking function is implemented with multiple buffers, such as a cell level buffer and a bit level buffer, then either buffer underflow will cause this count to be incremented."; + +#### **5.4.19 Calling party category (callingPartyCategory)** + +**callingPartyCategory ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CallingPartyCategory ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR callingPartyCategoryBeh;** + +**REGISTERED AS {attribute 19};** + +**callingPartyCategoryBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the category as the type of calling subscriber considered for the routing process." ; + +#### **5.4.20 Called party number representation Type (cdpnRepresentationType)** + +**cdpnRepresentationType ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CdpnRepresentationType;** + +**BEHAVIOUR cdpnRepresentationTypeBeh;** + +**REGISTERED AS {attribute 20};** + +**cdpnRepresentationTypeBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute specifies the format (nature of address) of the called party number to be delivered to the called party." ; + +#### **5.4.21 Call routing circuit endpoint identifier (crCircuitEndPointId)** + +**crCircuitEndPointId ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR crCircuitEndPointIdBeh;** + +**REGISTERED AS {attribute 21};** + +**crCircuitEndPointIdBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute is used to name instances of the crCircuitEndPoint managed object class."; + +#### **5.4.22 Call routing circuit endpoint subgroup identifier (crCircuitEndPointSubgroupId)** + +**crCircuitEndPointSubgroupId ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR crCircuitEndPointSubgroupIdBeh;** + +**REGISTERED AS {attribute 22};** + +**crCircuitEndPointSubgroupIdBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute is used to name instances of the crCircuitEndPointSubgroup managed object class."; + +#### **5.4.23 Call routing office data identifier (callRoutingOfficeDataId)** + +**callRoutingOfficeDataId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR callRoutingOfficeDataIdBeh;** +**REGISTERED AS {attribute 23};** + +**callRoutingOfficeDataIdBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the object identifier attribute of the object class 'callRoutingOfficeData'." ; + +#### **5.4.24 Carrier code (carrierCode)** + +**carrierCode ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CarrierCode ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR carrierCodeBeh;** +**REGISTERED AS {attribute 24};** + +**carrierCodeBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the unambiguous carrier specific code used to distinguish it from other carriers at the exchange. It can be dialled by the customer or supplied by the originating exchange." ; + +#### **5.4.25 Carrier data identifier (carrierDataId)** + +**carrierDataId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR carrierDataIdBeh;** +**REGISTERED AS {attribute 25};** + +**carrierDataIdBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the object identifier attribute of the object class 'carrierData'." ; + +#### **5.4.26 Carrier data pointer (carrierDataPtr)** + +**carrierDataPtr ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CarrierDataPtr ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR carrierDataPtrBeh;** +**REGISTERED AS {attribute 26};** + +**carrierDataPtrBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the pointer to an instance of 'carrierData'." ; + +#### **5.4.27 CBR rate (cbrRate)** + +**cbrRate ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Integer;** +**MATCHES FOR EQUALITY, ORDERING;** +**BEHAVIOUR cbrRateBeh;** +**REGISTERED AS {attribute 27};** + +**cbrRateBeh** BEHAVIOUR + +DEFINED AS + +"This attribute represents the rate of the CBR service supported by the AAL."; + +#### **5.4.28 Cell loss (cellLoss)** + +**cellLoss** ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR **cellLossBeh**; + +REGISTERED AS {attribute 28}; + +**cellLossBeh** BEHAVIOUR + +DEFINED AS + +"This attribute represents a count the number of lost cells, as detected by the AAL1 sequence number processing, for example. This count records the number of cells detected as lost in the network prior to the destination interworking function AAL1 layer processing. A negative value indicates that this attribute is not supported."; + +#### **5.4.29 Cell loss integration period (cellLossIntegrationPeriod)** + +**cellLossIntegrationPeriod** ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Integer; + +MATCHES FOR EQUALITY, ORDERING; + +BEHAVIOUR **cellLossIntegrationPeriodBeh**; + +REGISTERED AS {attribute 29}; + +**cellLossIntegrationPeriodBeh** BEHAVIOUR + +DEFINED AS + +"This attribute identifies the time in milliseconds for the cell loss integration period. If cells are lost for this period of time, the containing interworkingVcTtpBidirectional object will generate a communications alarm."; + +#### **5.4.30 Cell misinsertion (cellMisinsertion)** + +**cellMisinsertion** ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR **cellMisinsertionBeh**; + +REGISTERED AS {attribute 30}; + +**cellMisinsertionBeh** BEHAVIOUR + +DEFINED AS + +"This attribute represents a count of sequence violation events which the AAL CS interprets as misinserted of cells as defined by ITU-T Rec. I.363.1. A negative value indicates that this attribute is not supported."; + +#### **5.4.31 CES buffered CDV tolerance (cesBufferedCDVtolerance)** + +**cesBufferedCDVtolerance** ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Integer; + +MATCHES FOR EQUALITY; + +BEHAVIOUR **cesBufferedCDVtoleranceBeh**; + +REGISTERED AS {attribute 31}; + +**cesBufferedCDVtoleranceBeh** BEHAVIOUR + +DEFINED AS + +"This attribute identifies the duration of user data that must be buffered by the InterworkingVcTtpBidirectional managed object to offset Cell Delay variation. The timing is in increment of 10 micro seconds. The recommended default value for DS1 CES is 750 micro seconds and 1000 micro seconds for DS3 CES. The use of this attribute is for further study."; + +#### **5.4.32 CES service profile identifier (cesServiceProfileId)** + +##### **cesServiceProfileId ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR cesServiceProfileIdBeh;** + +**REGISTERED AS {attribute 32};** + +##### **cesServiceProfileIdBeh BEHAVIOUR** + +**DEFINED AS** + +**"This attribute is used for naming instances of cesServiceProfile managed object class."**; + +#### **5.4.33 Channel associated signalling (channelAssociatedSignalling)** + +##### **channelAssociatedSignalling ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ChannelAssociatedSignalling;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR channelAssociatedSignallingBeh;** + +**REGISTERED AS {attribute 33};** + +##### **channelAssociatedSignallingBeh BEHAVIOUR** + +**DEFINED AS** + +**"This attribute identifies which AAL1 format should be used. This attribute applies only to structured format. The default value Basic does not carry channel associated signalling (CAS) bits and uses a single 125 microsec frame. e1Cas, ds1sfCas, and ds1EsfCas carry CAS bits in a multiframe structure for E1, DS1 SF, and DS1 ESF respectively."**; + +#### **5.4.34 CIP required (cipRequired)** + +##### **cipRequired ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CIPRequired ;** + +**BEHAVIOUR cipRequiredBeh;** + +**REGISTERED AS {attribute 34};** + +##### **cipRequiredBeh BEHAVIOUR** + +**DEFINED AS** + +**"This entity indicates if the CIP (carrier identification parameter) has to be signalled further."** ; + +#### **5.4.35 Circuit identification code (cic)** + +##### **cic ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Cic;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR cicBeh;** + +**REGISTERED AS {attribute 35};** + +##### **cicBeh BEHAVIOUR** + +**DEFINED AS** + +**"This attribute indicates the Circuit Identification Code (CIC) of the circuit which is terminated by the circuit end point. The value of the CIC is identical in the two circuit end points which terminate the circuit."**; + +#### 5.4.36 Clock recovery type (clockRecoveryType) + +**clockRecoveryType ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ClockRecoveryType;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR clockRecoveryTypeBeh;** + +**REGISTERED AS {attribute 36};** + +**clockRecoveryTypeBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute indicates whether the clock recovery type is Synchronous, SRTS (Synchronous Residual Time Stamp), or Adaptive Clock Recovery." + +#### 5.4.37 Closed user group barring (cugBarring) + +**cugBarring ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CugBarring ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR cugBarringBeh;** + +**REGISTERED AS {attribute 37};** + +**cugBarringBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute maintains the Intra-CUG restriction of the General subscription option in ITU-T Rec. Q.2955.1." + +#### 5.4.38 Closed user group data network identification (cugDataNetworkIdentification) + +**cugDataNetworkIdentification ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CugDataNetworkIdentification ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR cugDataNetworkIdentificationBeh;** + +**REGISTERED AS {attribute 38};** + +**cugDataNetworkIdentificationBeh BEHAVIOUR** + +**DEFINED AS** + +"This information is signalled during setup of a CUG call and serves (in conjunction with the closed user groupInterlockCode) to uniquely identify the CUG in the international network. It can be thought of as the area code of the CUG." + +#### 5.4.39 Closed user group index (cugIndex) + +**cugIndex ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CugIndex ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR cugIndexBeh;** + +**REGISTERED AS {attribute 39};** + +**cugIndexBeh BEHAVIOUR** + +**DEFINED AS** + +"cugIndex of General subscription option in ITU-T Rec. Q.2955.1 must be explicitly assigned upon object creation. No two instances of the closed user group object class contained within a single object may have identical values for attribute cugIndex." + +#### 5.4.40 Closed user group interlock code (cugInterlockCode) + +cugInterlockCode ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CugInterlockCode ; +MATCHES FOR EQUALITY; +BEHAVIOUR cugInterlockCodeBeh; +REGISTERED AS {attribute 40}; + +cugInterlockCodeBeh BEHAVIOUR +DEFINED AS +"The attribute cugInterlockCode must be assigned explicitly upon object creation. No multiple instances of the closed user group object class contained within a single object are allowed to have identical combinations of attribute cugInterlockCode and cugDataNetworkIdentification."; + +#### 5.4.41 Code (code) + +code ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Code ; +BEHAVIOUR codeBeh; +REGISTERED AS {attribute 41}; + +codeBeh BEHAVIOUR +DEFINED AS +"This entity describes the prefix digits." ; + +#### 5.4.42 COM/EOM unexpected SN (comsEomsUnexpectedSN) + +comsEomsUnexpectedSN ATTRIBUTE +DERIVED FROM "ITU-T Rec. X.721":counter; +BEHAVIOUR comsEomsUnexpectedSNBeh; +REGISTERED AS {attribute 42}; + +comsEomsUnexpectedSNBeh BEHAVIOUR +DEFINED AS +"This attribute represents the number of COM and EOM segments received with an unexpected Sequence Number (SN). For a particular message (i.e., MID) transported over a VPC or VCC, this attribute is incremented by one each time a COM or EOM is received with a SAR Sequence Number (SN) that is not correct relative to the SN in the previous (non-EOM) segment."; + +#### 5.4.43 Connected line identification restriction options (connLineIdRestrictionOptions) + +connLineIdRestrictionOptions ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ConnLineIdRestrictionOptions; +MATCHES FOR EQUALITY; +BEHAVIOUR connLineIdRestrictionOptionsBeh; +REGISTERED AS {attribute 43}; + +connLineIdRestrictionOptionsBeh BEHAVIOUR +DEFINED AS +"This attribute of the COLRBB supplementary Service allows the subscriber to select the mode in which the connected line identification restriction is applied. Valid options for the mode are: Permanent to have the service active for all calls, or Temporary to have the service requested by the user per call."; + +#### **5.4.44 Connected number screening identifier (connectedNumberScreeningId)** + +**connectedNumberScreeningId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR connectedNumberScreeningIdBhv;** +**REGISTERED AS {attribute 44};** + +**connectedNumberScreeningIdBhv BEHAVIOUR** +**DEFINED AS** +"This is the naming attribute of the connected number screening managed object."; + +#### **5.4.45 Connection identification offering (connectionIdOffering)** + +**connectionIdOffering ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ConnectionIdOffering;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR connectionIdOfferingBeh;** +**REGISTERED AS {attribute 45};** + +**connectionIdOfferingBeh BEHAVIOUR** +**DEFINED AS** +"This attribute indicates which procedure is used for the selection of VPCI and VCI."; + +#### **5.4.46 CRC violations (crcViolations)** + +**crcViolations ATTRIBUTE** +**DERIVED FROM "ITU-T Rec. X.721":counter;** +**BEHAVIOUR crcViolationsBeh;** +**REGISTERED AS {attribute 46};** + +**crcViolationsBeh BEHAVIOUR** +**DEFINED AS** +"This attribute represents the number of CRC violations that were detected for the incoming AAL PDUs."; + +#### **5.4.47 CSP Required (cspRequired)** + +**cspRequired ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.CSPRequired ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR cspRequiredBeh;** +**REGISTERED AS {attribute 47};** + +**cspRequiredBeh BEHAVIOUR** +**DEFINED AS** +"This entity indicates if the CSP (carrier selection parameter) has to be signalled further." ; + +#### **5.4.48 Customer profile pointer (customerProfilePtr)** + +**customerProfilePtr ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PointerOrNull;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR customerProfilePtrBeh;** +**REGISTERED AS {attribute 48};** + +**customerProfilePtrBeh BEHAVIOUR** +**DEFINED AS** +"This attribute is used as a pointer to an instance of the customerProfile managed object class."; + +#### **5.4.49 Customized resource pointer list (customizedResourcePtrList)** + +**customizedResourcePtrList ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SetOfInstances; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR customizedResourcePtrListBeh; +**REGISTERED AS {attribute 49};** + +**customizedResourcePtrListBeh BEHAVIOUR** +DEFINED AS +"This is a set-valued attribute whose value(s) points to instances or instances of subclasses of the customizedResourceBb object class."; + +#### **5.4.50 Default directory number (defaultDirectoryNumber)** + +**defaultDirectoryNumber ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.DefaultDirectoryNumber; +MATCHES FOR EQUALITY; +BEHAVIOUR defaultDirectoryNumberBhv; +**REGISTERED AS {attribute 50};** + +**defaultDirectoryNumberBhv BEHAVIOUR** +DEFINED AS +"This attribute indicates the default directory number."; + +#### **5.4.51 Destination code (destinationCode)** + +**destinationCode ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.DestinationCode ; +MATCHES FOR EQUALITY; +BEHAVIOUR destinationCodeBeh; +**REGISTERED AS {attribute 51};** + +**destinationCodeBeh BEHAVIOUR** +DEFINED AS +"This entity describes the digit string including the local area code." ; + +#### **5.4.52 Destination type (destinationType)** + +**destinationType ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.DestinationType ; +MATCHES FOR EQUALITY; +BEHAVIOUR destinationTypeBeh; +**REGISTERED AS {attribute 52};** + +**destinationTypeBeh BEHAVIOUR** +DEFINED AS +"This entity describes unambiguously the type of destination like international, national or local." ; + +#### **5.4.53 Digit combination insertion (digitCombInsert)** + +**digitCombInsert ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.DigitCombInsert ; +MATCHES FOR EQUALITY; +BEHAVIOUR digitCombInsertBeh; +**REGISTERED AS {attribute 53};** + +**digitCombInsertBeh BEHAVIOUR** +DEFINED AS +"This entity describes which sequence of digits is to be inserted and where." ; + +#### 5.4.54 Digit combination replace (digitCombReplace) + +digitCombReplace ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.DigitCombReplace ; +MATCHES FOR EQUALITY; +BEHAVIOUR digitCombReplaceBeh; +REGISTERED AS {attribute 54}; + +digitCombReplaceBeh BEHAVIOUR +DEFINED AS +"This entity describes which sequence of digits is to be replaced and through which." ; + +#### 5.4.55 Digit manipulation identifier (digitManipId) + +digitManipId ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ; +MATCHES FOR EQUALITY; +BEHAVIOUR digitManipIdBeh; +REGISTERED AS {attribute 55}; + +digitManipIdBeh BEHAVIOUR +DEFINED AS +"This entity describes the object identifier attribute of the object class 'digitManip'." ; + +#### 5.4.56 Digit manipulation pointer (digitManipPtr) + +digitManipPtr ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.DigitManipPtr ; +MATCHES FOR EQUALITY; +BEHAVIOUR digitManipPtrBeh; +REGISTERED AS {attribute 56}; + +digitManipPtrBeh BEHAVIOUR +DEFINED AS +"This entity describes the pointer to 'digitManip' " ; + +#### 5.4.57 Digit suppression (digitSuppress) + +digitSuppress ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.DigitSuppress ; +MATCHES FOR EQUALITY; +BEHAVIOUR digitSuppressBeh; +REGISTERED AS {attribute 57}; + +digitSuppressBeh BEHAVIOUR +DEFINED AS +"This entity describes which sequence of digits is to be suppressed." ; + +#### 5.4.58 Excluded subscriber codes (excludedSubscriberCodes) + +excludedSubscriberCodes ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ExcludedSubscriberCodes ; +MATCHES FOR EQUALITY; +BEHAVIOUR excludedSubscriberCodesBeh; +REGISTERED AS {attribute 58}; + +**excludedSubscriberCodesBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the directory numbers which are excluded from the upper limit of the possible directory numbers for this local destination. The excluded numbers are defined in terms of a set of sequences of directory numbers where each sequence is specified by its common most significant digits." ; + +#### **5.4.59 Forward error correction method (forwardErrorCorrectionMethod)** + +**forwardErrorCorrectionMethod ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.FecMethod;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR forwardErrorCorrectionMethodBeh;** + +**REGISTERED AS {attribute 59};** + +**forwardErrorCorrectionMethodBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute indicates the FEC method: no FEC, FEC for Loss Sensitive Signal Transport, or FEC for Delay Sensitive Signal Transport."; + +#### **5.4.60 Header errors (headerErrors)** + +**headerErrors ATTRIBUTE** + +**DERIVED FROM "ITU-T Rec. X.721":counter;** + +**BEHAVIOUR headerErrorsBeh;** + +**REGISTERED AS {attribute 60};** + +**headerErrorsBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute represents a count of the number of AAL1 header errors detected, including those corrected. Header errors include correctable and uncorrectable CRC plus bad parity."; + +#### **5.4.61 Initial subscriber codes (initialSubscriberCodes)** + +**initialSubscriberCodes ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.InitialSubscriberCodes ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR initialSubscriberCodesBeh;** + +**REGISTERED AS {attribute 61};** + +**initialSubscriberCodesBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the upper limit of the possible directory numbers which can belong to this local destination. The upper limit is defined in terms of a set of sequences of directory numbers where each sequence is specified by its common most significant digits." ; + +#### **5.4.62 Inter closed user group access (interCugAccess)** + +**interCugAccess ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.InterCugAccess;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR interCugAccessBeh;** + +**REGISTERED AS {attribute 62};** + +**interCugAccessBeh BEHAVIOUR** + +**DEFINED AS** + +"Inter-CUG access of per service subscription option in ITU-T Rec. Q.2955.1."; + +#### 5.4.63 Length BA size mismatch (lengthBASizeMismatch) + +lengthBASizeMismatch ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR lengthBASizeMismatchBeh; + +REGISTERED AS {attribute 63}; + +lengthBASizeMismatchBeh BEHAVIOUR + +DEFINED AS + +"This attribute represents the number of CS\_PDUs in which the Length field value was not consistent with the BASize field value. The definition of consistent depends on the mode in which CS\_PDU fragments are being processed. In the message-mode, the BASize field must equal the Length field. In the streaming mode, the BASize field must be less than the Length field."; + +#### 5.4.64 Length mismatch (lengthMismatch) + +lengthMismatch ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR lengthMismatchBeh; + +REGISTERED AS {attribute 64}; + +lengthMismatchBeh BEHAVIOUR + +DEFINED AS + +"This attribute represents the number of CS\_PDUs received with a Length field value that does not represent the actual length of the CS\_PDU payload."; + +#### 5.4.65 Link group pointer (linkGroupPtr) + +linkGroupPtr ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ObjectInstance; + +MATCHES FOR EQUALITY; + +BEHAVIOUR linkGroupPtrBeh; + +REGISTERED AS {attribute 65}; + +linkGroupPtrBeh BEHAVIOUR + +DEFINED AS + +"This entity describes the result pointer to an instance of 'xtpsgComb', 'crCircuitEndPointSubgroup' or 'virtualPathGroup'."; + +#### 5.4.66 Link type (linkType) + +linkType ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.LinkType; + +MATCHES FOR EQUALITY; + +BEHAVIOUR linkTypeBeh; + +REGISTERED AS {attribute 66}; + +linkTypeBeh BEHAVIOUR + +DEFINED AS + +"This attribute is used to indicate whether the NNI is an international interface or not."; + +#### 5.4.67 List of link groups pointer list (listOfLinkGroupsPtrList) + +listOfLinkGroupsPtrList ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ListOfLinkGroupsPtrList; + +MATCHES FOR EQUALITY; + +BEHAVIOUR listOfLinkGroupsPtrListBeh; + +REGISTERED AS {attribute 67}; + +**listOfLinkGroupsPtrListBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the sequence of instances of 'virtualPathGroup' or +'crCircuitEndPointSubgroup'." ; + +#### **5.4.68 List of routes pointer list (listOfRoutesPtrList)** + +**listOfRoutesPtrList ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ListOfRoutesPtrList ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR listOfRoutesPtrListBeh;** +**REGISTERED AS {attribute 68};** + +**listOfRoutesPtrListBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the sequence of the selected routes ('routeData')." ; + +#### **5.4.69 List of route termination points identifier (listOfRouteTpsId)** + +**listOfRouteTpsId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR listOfRouteTpsIdBeh;** +**REGISTERED AS {attribute 69};** + +**listOfRouteTpsIdBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the object identifier attribute of the object class 'listOfRouteTps'." ; + +#### **5.4.70 Local area code (localAreaCode)** + +**localAreaCode ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.LocalAreaCode ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR localAreaCodeBeh;** +**REGISTERED AS {attribute 70};** + +**localAreaCodeBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the local area code of the subscribers which belong to this local destination. +The local area code is used without any prefix." ; + +#### **5.4.71 Local destination identifier (localDestinationId)** + +**localDestinationId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR localDestinationIdBeh;** +**REGISTERED AS {attribute 71};** + +**localDestinationIdBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the object identifier attribute of the object class 'localDestination'." ; + +#### **5.4.72 Local destination pointer (localDestinationPtr)** + +##### **localDestinationPtr ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ObjectInstance;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR localDestinationPtrBeh;** + +**REGISTERED AS {attribute 72};** + +##### **localDestinationPtrBeh BEHAVIOUR** + +**DEFINED AS** + +**"This attribute describes the pointer to localDestination. The directoryNumberE164 shall be member of the local area defined by the localAreaCode and the initial digit string part of the SN part of the directoryNumberE164 shall match with one of the initialSubscriberCodes of the referenced object. The directoryNumberE164 shall not be excluded by one of the excludedSubscriberCodes from the referenced object."** + +#### **5.4.73 Maintenance signalling running (maintenanceSignallingRunning)** + +##### **maintenanceSignallingRunning ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaintenanceSignallingRunning;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR maintenanceSignallingRunningBeh;** + +**REGISTERED AS {attribute 73};** + +##### **maintenanceSignallingRunningBeh BEHAVIOUR** + +**DEFINED AS** + +**"This attribute indicates that a maintenance signalling procedure (e.g. reset, restart, blocking, unblocking) is running."** + +#### **5.4.74 Maximun CC (maxCc)** + +##### **maxCc ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxCc;** + +**BEHAVIOUR maxCcBeh;** + +**REGISTERED AS {attribute 74};** + +##### **maxCcBeh BEHAVIOUR** + +**DEFINED AS** + +**"This attribute defines the maximum value [PDUs] of the state variable VT(CC), corresponding to the maximum number of transmissions of BGN, END, ER or RS PDUs."** + +#### **5.4.75 Maximum CPCS\_PDU size (maxCpcsPduSize)** + +##### **maxCpcsPduSize ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxCpcsPduSize;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR maxCpcsPduSizeBeh;** + +**REGISTERED AS {attribute 75};** + +##### **maxCpcsPduSizeBeh BEHAVIOUR** + +**DEFINED AS** + +**"This multi-valued attribute represents the maximum CPCS\_PDU size that will be transmitted over the connection in both the incoming (forward) and outgoing (backward) direction of transmission."** + +#### 5.4.76 Maximum digits (maxDigits) + +**maxDigits ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxDigits ; +MATCHES FOR EQUALITY; +BEHAVIOUR maxDigitsBeh; +REGISTERED AS {attribute 76}; + +**maxDigitsBeh BEHAVIOUR** +DEFINED AS +"This entity describes the maximum number of digits required by the destination exchange. Further digits will be ignored." ; + +#### 5.4.77 Maximum information field length (maxInformationFieldLength) + +**maxInformationFieldLength ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxInformationFieldLength; +BEHAVIOUR maxInformationFieldLengthBeh; +REGISTERED AS {attribute 77}; + +**maxInformationFieldLengthBeh BEHAVIOUR** +DEFINED AS +"This attribute defines the maximum length of the information field in SD PDUs, UD PDUs and MD PDUs 'k'. The unit of the INTEGER value is octets."; + +#### 5.4.78 Maximum length of SSCOP user to user field (maxLengthSscopUuField) + +**maxLengthSscopUuField ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxLengthSscopUuField; +BEHAVIOUR maxLengthSscopUuFieldBeh; +REGISTERED AS {attribute 78}; + +**maxLengthSscopUuFieldBeh BEHAVIOUR** +DEFINED AS +"This attribute defines the maximum length of a variable length SSCOP UU field 'j'. The SSCOP UU is an optional field of BGN PDUs, BGAK PDUs, BGREJ PDUs, END PDUs and RS PDUs. The unit of the INTEGER value is octets"; + +#### 5.4.79 Maximum PD (maxPd) + +**maxPd ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxPd; +BEHAVIOUR maxPdBeh; +REGISTERED AS {attribute 79}; + +**maxPdBeh BEHAVIOUR** +DEFINED AS +"This attribute defines the maximum acceptable value [PDUs] of the state variable VT(PD) before sending a POLL PDU and resetting VT(PD) to zero. The VT(PD) is incremented each time an SD PDU is transmitted."; + +#### 5.4.80 Maximum SSCOP credit to peer (maxSscopCreditToPeer) + +**maxSscopCreditToPeer ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxSscopCreditToPeer; +BEHAVIOUR maxSscopCreditToPeerBeh; +REGISTERED AS {attribute 80}; + +**maxSscopCreditToPeerBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the absolute value [PDUs] of the size of the receive window given to the peer. This value is added to VR(R) to generate VR(MR). VR(MR) is mapped to N(MR) by transmission of STAT, USTAT, RS RSAK, ER, ERAK, BGN or BGAK PDUs."; + +#### **5.4.81 Maximum STAT (maxStat)** + +**maxStat ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MaxStat;** + +**BEHAVIOUR maxStatBeh;** + +**REGISTERED AS {attribute 81};** + +**maxStatBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the maximum number of list elements placed in a STAT PDU."; + +#### **5.4.82 MID range (midRange)** + +**midRange ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MidRange;** + +**MATCHES FOR EQUALITY, ORDERING;** + +**BEHAVIOUR midRangeBeh;** + +**REGISTERED AS {attribute 82};** + +**midRangeBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute represents the range of MID values supported at the AAL for the supporting VCC."; + +#### **5.4.83 Minimum digits (minDigits)** + +**minDigits ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.MinDigits ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR minDigitsBeh;** + +**REGISTERED AS {attribute 83};** + +**minDigitsBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the minimum number of digits required before the outgoing termination point can be seized. It is only needed in case of overlapped dialling." ; + +#### **5.4.84 Nature of address (natureOfAddress)** + +**natureOfAddress ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NatureOfAddress ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR** natureOfAddressBeh; +**REGISTERED AS** {attribute 84}; + +natureOfAddressBeh **BEHAVIOUR** +**DEFINED AS** +    "This entity describes the destination type of the prefix." ; + +#### **5.4.85 Network border (networkBorder)** + +**networkBorder ATTRIBUTE** +    **WITH ATTRIBUTE SYNTAX** ASN1DefinedTypesModule.NetworkBorder; +    **MATCHES FOR EQUALITY;** +    **BEHAVIOUR** networkBorderBeh; +**REGISTERED AS** {attribute 85}; + +**networkBorderBeh BEHAVIOUR** +**DEFINED AS** +    "This attribute is used to indicate whether the NNI is an operator network border or not."; + +#### **5.4.86 Network type (networkType)** + +**networkType ATTRIBUTE** +    **WITH ATTRIBUTE SYNTAX** ASN1DefinedTypesModule.NetworkType; +    **MATCHES FOR EQUALITY;** +    **BEHAVIOUR** networkTypeBeh; +**REGISTERED AS** {attribute 86}; + +**networkTypeBeh BEHAVIOUR** +**DEFINED AS** +    "This attribute is used to indicate whether an access belongs to a national transit network. It is used together with the linkType and the signallingType to generate the setting of the location field according to Q.850."; + +#### **5.4.87 NNI access identifier (nniAccessId)** + +**nniAccessId ATTRIBUTE** +    **WITH ATTRIBUTE SYNTAX** ASN1DefinedTypesModule.NameType; +    **MATCHES FOR EQUALITY;** +    **BEHAVIOUR** nniAccessIdBeh; +**REGISTERED AS** {attribute 87}; + +**nniAccessIdBeh BEHAVIOUR** +**DEFINED AS** +    "This attribute is used to name instances of the nniAccess managed object class."; + +#### **5.4.88 No connected line identification presentation restrictions allowed (noColpRestrictionsAllowed)** + +**noColpRestrictionsAllowed ATTRIBUTE** +    **WITH ATTRIBUTE SYNTAX** ASN1DefinedTypesModule.Boolean; +    **MATCHES FOR EQUALITY;** +    **BEHAVIOUR** noColpRestrictionsAllowedBeh ; +**REGISTERED AS** {attribute 88}; + +**noColpRestrictionsAllowedBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute of COLP is where the calling party continues to have the capability to override the COLR restriction and have the connected party number presented as described in the COLP supplementary service. A TRUE value of this attribute permits the called party COLP supplementary service to override the calling party COLR supplementary service."; + +#### **5.4.89 Number of aborts (numberOfAborts)** + +**numberOfAborts ATTRIBUTE** + +**DERIVED FROM "ITU-T Rec. X.721":counter;** + +**BEHAVIOUR numberOfAbortsBeh;** + +**REGISTERED AS {attribute 89};** + +**numberOfAbortsBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute provides a count of the number aborts (i.e., EOM with SAR\_PDU Length Indication = 63) that are received for the underlying VPC or VCC."; + +#### **5.4.90 Origin (origin)** + +**origin ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Origin ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR originBeh;** + +**REGISTERED AS {attribute 90};** + +**originBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the origin of the calling subscriber considered for the routing process." ; + +#### **5.4.91 Origin for routing (originForRouting)** + +**originForRouting ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Integer;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR originForRoutingBeh;** + +**REGISTERED AS {attribute 91};** + +**originForRoutingBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute determines the origin assigned to the NNI access for call routing purpose."; + +#### **5.4.92 Origin mark (originMark)** + +**originMark ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Integer;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR originMarkBeh;** + +**REGISTERED AS {attribute 92};** + +**originMarkBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute determines the origination of the calling subscriber."; + +#### 5.4.93 Own international code (ownInternationalCode) + +**ownInternationalCode ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.OwnInternationalCode ; +MATCHES FOR EQUALITY; +BEHAVIOUR ownInternationalCodeBeh; +REGISTERED AS {attribute 93}; + +**ownInternationalCodeBeh BEHAVIOUR** +DEFINED AS +"This entity describes the country code of the calling party. The own international code is used without any prefix." ; + +#### 5.4.94 Partially filled cells (partiallyFilledCells) + +**partiallyFilledCells ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Integer; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR partiallyFilledCellsBeh; +REGISTERED AS {attribute 94}; + +**partiallyFilledCellsBeh BEHAVIOUR** +DEFINED AS +"This attribute identifies the number of leading octets in use."; + +#### 5.4.95 Poll after retransmission (pollAfterRetransmission) + +**pollAfterRetransmission ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PollAfterRetransmission; +BEHAVIOUR pollAfterRetransmissionBeh; +REGISTERED AS {attribute 95}; + +**pollAfterRetransmissionBeh BEHAVIOUR** +DEFINED AS +"This attribute specifies if a POLL is transmitted each time the retransmission queue is emptied"; + +#### 5.4.96 Post analysis evaluation identifier (postAnalysisEvaluationId) + +**postAnalysisEvaluationId ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ; +MATCHES FOR EQUALITY; +BEHAVIOUR postAnalysisEvaluationIdBeh; +REGISTERED AS {attribute 96}; + +**postAnalysisEvaluationIdBeh BEHAVIOUR** +DEFINED AS +"This entity describes the object identifier attribute of the object class 'postAnalysisEvaluation'." ; + +#### 5.4.97 Preferred carrier (preferredCarrier) + +**preferredCarrier ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PreferredCarrier; +MATCHES FOR EQUALITY; +BEHAVIOUR preferredCarrierBeh; +REGISTERED AS {attribute 97}; + +**preferredCarrierBeh BEHAVIOUR** +DEFINED AS +"This attribute identifies the default carrier to use when one is not explicitly identified in the call setup message received and processed by the managed system."; + +#### **5.4.98 Preferred closed user group index (preferredCugIndex)** + +**preferredCugIndex ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PreferredCugIndex; +MATCHES FOR EQUALITY; +BEHAVIOUR preferredCugIndexBeh; +REGISTERED AS {attribute 98}; + +**preferredCugIndexBeh BEHAVIOUR** +DEFINED AS +"This attribute indicates the index of the preferred CUG."; + +#### **5.4.99 Prefix digit analysis identifier (prefixDigitAnalysisId)** + +**prefixDigitAnalysisId ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ; +MATCHES FOR EQUALITY; +BEHAVIOUR prefixDigitAnalysisIdBeh; +REGISTERED AS {attribute 99}; + +**prefixDigitAnalysisIdBeh BEHAVIOUR** +DEFINED AS +"This entity describes the object identifier attribute of the object class 'prefixDigitAnalysis'." ; + +#### **5.4.100 Propagation delay (propagationDelay)** + +**propagationDelay ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PropagationDelay; +MATCHES FOR EQUALITY; +BEHAVIOUR propagationDelayBeh; +REGISTERED AS {attribute 100}; + +**propagationDelayBeh BEHAVIOUR** +DEFINED AS +"Indicates the expected propagation delay (in micro seconds)."; + +#### **5.4.101 Reassembly timer expirations (reassemblyTimerExpirations)** + +**reassemblyTimerExpirations ATTRIBUTE** +DERIVED FROM "ITU-T Rec. X.721":counter; +BEHAVIOUR reassemblyTimerExpirationsBeh; +REGISTERED AS {attribute 101}; + +**reassemblyTimerExpirationsBeh BEHAVIOUR** +DEFINED AS +"This attribute provides a count of reassembly timer expirations. A negative value indicates that this attribute is not supported. "; + +#### **5.4.102 Remote blocking (remoteBlocking)** + +**remoteBlocking ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.RemoteBlocking; +MATCHES FOR EQUALITY; +BEHAVIOUR remoteBlockingBeh; +REGISTERED AS {attribute 102}; + +**remoteBlockingBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute indicates the remote blocking state of the virtual path. A blocked virtual path cannot be selected for new non-test traffic; however it can be used for test calls. The blocking of a virtual path has no influence to existing calls (non-test calls and test calls)."; + +#### **5.4.103 Remote blocking reason (remoteBlockingReason)** + +**remoteBlockingReason ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.RemoteBlockingReason ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR remoteBlockingReasonBeh;** + +**REGISTERED AS {attribute 103};** + +**remoteBlockingReasonBeh BEHAVIOUR** + +**DEFINED AS** + +"Indicates the reason when the circuit was remotely blocked."; + +#### **5.4.104 Required bandwidth egress (reqBandwidthEgress)** + +**reqBandwidthEgress ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ReqBandwidthEgress ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR reqBandwidthEgressBeh;** + +**REGISTERED AS {attribute 104};** + +**reqBandwidthEgressBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the range of supported bandwidth." ; + +#### **5.4.105 Required bandwidth ingress (reqBandwidthIngress)** + +**reqBandwidthIngress ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ReqBandwidthIngress ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR reqBandwidthIngressBeh;** + +**REGISTERED AS {attribute 105};** + +**reqBandwidthIngressBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the range of supported bandwidth." ; + +#### **5.4.106 Required bearer capability (reqBearerCapab)** + +**reqBearerCapab ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ReqBearerCapab ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR reqBearerCapabBeh;** + +**REGISTERED AS {attribute 106};** + +**reqBearerCapabBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the supported bearer capabilities." ; + +#### **5.4.107 Required narrowband transfer capability (reqNbTransferCapability)** + +**reqNbTransferCapability ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ReqNbTransferCapability ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR reqNbTransferCapabilityBeh;** +**REGISTERED AS {attribute 107};** + +**reqNbTransferCapabilityBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the N-ISDN bearer capability of the underlying routes." ; + +#### **5.4.108 Ring time limit (ringTimeLimit)** + +**ringTimeLimit ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.RingTimeLimit ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR ringTimeLimitBeh;** +**REGISTERED AS {attribute 108};** + +**ringTimeLimitBeh BEHAVIOUR** +**DEFINED AS** +"This attribute limits the ring time in seconds." ; + +#### **5.4.109 Route data identifier (routeDataId)** + +**routeDataId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR routeDataIdBeh;** +**REGISTERED AS {attribute 109};** + +**routeDataIdBeh BEHAVIOUR** +**DEFINED AS** +"This entity describes the object identifier attribute of the object class 'routeData'." ; + +#### **5.4.110 SAAL UNI protocol profile identifier (saalUniProtocolProfileId)** + +**saalUniProtocolProfileId ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR saalUniProtocolProfileIdBeh;** +**REGISTERED AS {attribute 110};** + +**saalUniProtocolProfileIdBeh BEHAVIOUR** +**DEFINED AS** +"This attribute is used for naming instances of the object class saalUniProtocolProfile." ; + +#### **5.4.111 SAR CRC violations (sarCrcViolations)** + +**sarCrcViolations ATTRIBUTE** +**DERIVED FROM "ITU-T Rec. X.721":counter;** +**BEHAVIOUR sarCrcViolationsBeh;** +**REGISTERED AS {attribute 111};** + +**sarCrcViolationsBeh BEHAVIOUR** +**DEFINED AS** +"This attribute represents the number of CRC violations that were detected for the incoming SAR PDUs." ; + +#### 5.4.112 Screen number (screenNumber) + +**screenNumber ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Boolean;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR screenNumberBhv;** + +**REGISTERED AS {attribute 112};** + +**screenNumberBhv BEHAVIOUR** + +**DEFINED AS** + +**"This is a boolean attribute. When the value of this attribute is TRUE, the switch will screen the directory number information for validity when provided on a call by the user equipment."** + +#### 5.4.113 Search method (searchMethod) + +**searchMethod ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SearchMethod;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR searchMethodBeh;** + +**REGISTERED AS {attribute 113};** + +**searchMethodBeh BEHAVIOUR** + +**DEFINED AS** + +**"This attribute describes the method how to select a VPC with sufficient free bandwidth or an idle circuit within this object instance. The following algorithms are defined for that purpose:** + +**– forwardSequential: This algorithm selects the VPC with the lowest VPCI value, which has sufficient free bandwidth in the broadband case. This algorithm selects the idle circuit with the lowest CIC number in the narrowband case.** + +**– backwardSequential: This algorithm selects the VPC with the highest VPCI value, which has sufficient free bandwidth in the broadband case. This algorithm selects the idle circuit with the highest CIC number in the narrowband case.** + +**– forwardCyclic: In the broadband case this algorithm selects the VPC with sufficient free bandwidth with the lowest VPCI value that is larger than the VPCI value of the previously selected VPC. If no such VPC exists, it selects the VPC with sufficient bandwidth with the lowest VPCI value that is less than the VPCI value of the previously selected VPC.** + +**In the narrowband case this algorithm selects the idle circuit with the lowest CIC number that is larger than the CIC number of the previously selected circuit. If no such idle circuit exists, it selects the idle CIC with the lowest CIC number that is less than the CIC number of the previously selected circuit.** + +**– backwardCyclic: In the broadband case this algorithm selects the VPC with sufficient bandwidth with the highest VPCI value that is less than the VPCI value of the previously selected VPC. If no such VPC exists, it selects the VPC with sufficient bandwidth with the highest VPCI value that is larger than the VPCI value number of the previously selected circuit.** + +**In the narrowband case this algorithm selects the idle circuit with the highest CIC number that is less than the CIC number of the previously selected circuit. If no such idle circuit exists, it selects the idle CIC with the highest CIC number that is larger than the CIC number of the previously selected circuit."** + +#### 5.4.114 Sends TNS (sendTns) + +##### sendTns ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SendTns ; + +MATCHES FOR EQUALITY; + +BEHAVIOUR sendTnsBeh; + +REGISTERED AS {attribute 114}; + +##### sendTnsBeh BEHAVIOUR + +DEFINED AS + +"This entity describes whether for this instance of 'routeData' the TNS is to be signalled to the next node." ; + +#### 5.4.115 Sequence violations (sequenceViolations) + +##### sequenceViolations ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR sequenceViolationsBeh; + +REGISTERED AS {attribute 115}; + +##### sequenceViolationsBeh BEHAVIOUR + +DEFINED AS + +"This attribute represents a count incoming AAL Type 1 SAR-PDUs where the sequence count in the PDU header causes a transition from the SYNC state to the OUT OF SEQUENCE state as defined by ITU-T Rec. I.363.1. A negative value indicates that this attribute is not supported."; + +#### 5.4.116 Service profile pointer (serviceProfilePointer) + +##### serviceProfilePointer ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PointerOrNull; + +MATCHES FOR EQUALITY; + +BEHAVIOUR serviceProfilePointerBeh; + +REGISTERED AS {attribute 116}; + +##### serviceProfilePointerBeh BEHAVIOUR + +DEFINED AS + +"This attribute provides a pointer to a managed object instance that provides information used to control service interworking (e.g., a cesServiceProfile object)."; + +#### 5.4.117 Signalling channel pointer (signallingChannelPtr) + +##### signallingChannelPtr ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ObjectInstance; + +MATCHES FOR EQUALITY; + +BEHAVIOUR signallingChannelPtrBeh; + +REGISTERED AS {attribute 117}; + +##### signallingChannelPtrBeh BEHAVIOUR + +DEFINED AS + +"This attribute is used as a pointer to an instance of the vcTTPBidirectional managed object class. The referenced vcTTPBidirectional instance terminates the signalling virtual channel."; + +#### 5.4.118 Signalling protocol (signallingProtocol) + +**signallingProtocol ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SignallingProtocol; +MATCHES FOR EQUALITY; +BEHAVIOUR signallingProtocolBeh; +REGISTERED AS {attribute 118}; + +**signallingProtocolBeh BEHAVIOUR** +DEFINED AS +"This attribute indicates which type of signalling protocol is used."; + +#### 5.4.119 Signalling route pointer (sigRoutePtr) + +**sigRoutePtr ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ObjectInstance; +MATCHES FOR EQUALITY; +BEHAVIOUR sigRoutePtrBeh; +REGISTERED AS {attribute 119}; + +**sigRoutePtrBeh BEHAVIOUR** +DEFINED AS +"Identifies the CCS7 signalling resource (Q.2751:signRouteSetNePart)."; + +#### 5.4.120 Signalling standard (signallingStandard) + +**signallingStandard ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SignallingStandard; +MATCHES FOR EQUALITY; +BEHAVIOUR signallingStandardBeh; +REGISTERED AS {attribute 120}; + +**signallingStandardBeh BEHAVIOUR** +DEFINED AS +"This attribute is used to indicate the type of signalling used by instances of this class."; + +#### 5.4.121 Signalling type (signallingType) + +**signallingType ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SignallingType; +MATCHES FOR EQUALITY; +BEHAVIOUR signallingTypeBeh; +REGISTERED AS {attribute 121}; + +**signallingTypeBeh BEHAVIOUR** +DEFINED AS +"This attribute is used to indicate whether associated or nonassociated signalling is used at the instance of this class."; + +#### 5.4.122 SRI timeouts (sriTimeOuts) + +**sriTimeOuts ATTRIBUTE** +DERIVED FROM "ITU-T Rec. X.721":counter; +BEHAVIOUR sriTimeOutsBeh; +REGISTERED AS {attribute 122}; + +**sriTimeOutsBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute represents a count of the number of SRI time-outs that occurred on an ATM connection." + +#### **5.4.123 SSCOP timer CC (sscopTimerCc)** + +**sscopTimerCc ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SscopTimerCc;** + +**BEHAVIOUR sscopTimerCcBeh;** + +**REGISTERED AS {attribute 123};** + +**sscopTimerCcBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the time interval between transmissions of BGN, END, RS and ER PDUs when an acknowledge to these PDUs has not been received. The unit for the INTEGER value is milliseconds." + +#### **5.4.124 SSCOP timer idle (sscopTimerIdle)** + +**sscopTimerIdle ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SscopTimerIdle;** + +**BEHAVIOUR sscopTimerIdleBeh;** + +**REGISTERED AS {attribute 124};** + +**sscopTimerIdleBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the SSCOP timer IDLE. The SSCOP connection is partitioned into phases. The SSCOP timer IDLE supervises the idle phase. In this phase the timer NO\_RESPONSE is not running and no POLL PDUs are transmitted. The unit for the INTEGER value is milliseconds." + +#### **5.4.125 SSCOP timer keep alive (sscopTimerKeepAlive)** + +**sscopTimerKeepAlive ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SscopTimerKeepAlive;** + +**BEHAVIOUR sscopTimerKeepAliveBeh;** + +**REGISTERED AS {attribute 125};** + +**sscopTimerKeepAliveBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the SSCOP timer KEEP\_ALIVE. The SSCOP connection is partitioned into phases. The SSCOP timer KEEP\_ALIVE supervises the transient phase. In this phase there are no outstanding acknowledgements or new data pending transmission. The unit for the INTEGER value is milliseconds." + +#### **5.4.126 SSCOP timer no response (sscopTimerNoResponse)** + +**sscopTimerNoResponse ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SscopTimerNoResponse;** + +**BEHAVIOUR sscopTimerNoResponseBeh;** + +**REGISTERED AS {attribute 126};** + +**sscopTimerNoResponseBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute defines the SSCOP timer NO\_RESPONSE. This timer is used to detect a faulty connection. The timer runs with either the timer POLL or KEEP\_ALIVE simultaneously. The unit for the INTEGER value is milliseconds." + +#### 5.4.127 SSCOP timer poll (sscopTimerPoll) + +##### sscopTimerPoll ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SscopTimerPoll; + +BEHAVIOUR sscopTimerPollBeh; + +REGISTERED AS {attribute 127}; + +##### sscopTimerPollBeh BEHAVIOUR + +DEFINED AS + +"This attribute defines the SSCOP timer POLL. The SSCOP connection is partitioned into phases. The SSCOP timer POLL supervises the active phase. In this new data is pending, transmission or acknowledgements are outstanding. The unit for the INTEGER value is milliseconds."; + +#### 5.4.128 SSCS type (sscsType) + +##### sscsType ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SscsType; + +MATCHES FOR EQUALITY; + +BEHAVIOUR sscsTypeBeh; + +REGISTERED AS {attribute 128}; + +##### sscsTypeBeh BEHAVIOUR + +DEFINED AS + +"This attribute identifies the SSCS type for the AAL. Valid values are NULL, Data SSCS based on SSCOP (assured operation), Data SSCS based on SSCOP (non-assured operation), or Frame Relay SSCS."; + +#### 5.4.129 STD pointer parity failures (stdPointerParityFailures) + +##### stdPointerParityFailures ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR stdPointerParityFailuresBeh; + +REGISTERED AS {attribute 129}; + +##### stdPointerParityFailuresBeh BEHAVIOUR + +DEFINED AS + +"This attribute represents a count of the number of times the AAL reassembler detects a parity check failure at the point where a structured data pointer is expected. This count is only meaningful for structured data transfer modes as unstructured modes do not use pointers. A negative value indicates that this attribute is not supported."; + +#### 5.4.130 STD pointer reframes (stdPointerReframes) + +##### stdPointerReframes ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR stdPointerReframesBeh; + +REGISTERED AS {attribute 130}; + +##### stdPointerReframesBeh BEHAVIOUR + +DEFINED AS + +"This attribute represents a count of the number of events in which the AAL1 reassembler found that a structured data pointer is not where it is expected, and the pointer must be reacquired. This count is only meaningful for structured data transfer modes as unstructured modes do not use pointers. A negative value indicates that this attribute is not supported; however it must be supported when pointers are used."; + +#### 5.4.131 Structured data transfer (structuredDataTransfer) + +structuredDataTransfer ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Boolean; +MATCHES FOR EQUALITY; +BEHAVIOUR structuredDataTransferBeh; +REGISTERED AS {attribute 131}; + +structuredDataTransferBeh BEHAVIOUR +DEFINED AS +"This attribute indicates whether Structured Data Transfer (SDT) has been configured at the AAL. +A value of TRUE means SDT has been selected. This attribute value cannot be set to TRUE when the +errorCorrectionType attribute equals TRUE."; + +#### 5.4.132 Subscriber category (subscriberCategory) + +subscriberCategory ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SubscriberCategory; +MATCHES FOR EQUALITY; +BEHAVIOUR subscriberCategoryBeh; +REGISTERED AS {attribute 132}; + +subscriberCategoryBeh BEHAVIOUR +DEFINED AS +"This attribute determines the category of the calling subscriber."; + +#### 5.4.133 Subtype (subType) + +subType ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SubType; +MATCHES FOR EQUALITY; +BEHAVIOUR subTypeBeh; +REGISTERED AS {attribute 133}; + +subTypeBeh BEHAVIOUR +DEFINED AS +"This attribute is used to identify the AAL subtype. Valid values for this attribute are NULL, Voice-band based on 64 kbit/s, Circuit Emulation (synchronous), Circuit Emulation (asynchronous), High-quality Audio, and Video."; + +#### 5.4.134 Sum of incorrect CS field errors (sumOfIncorrectCSFieldErrors) + +sumOfIncorrectCSFieldErrors ATTRIBUTE +DERIVED FROM "ITU-T Rec. X.721":counter; +BEHAVIOUR sumOfIncorrectCSFieldErrorsBeh; +REGISTERED AS {attribute 134}; + +sumOfIncorrectCSFieldErrorsBeh BEHAVIOUR +DEFINED AS +"This attribute provides a sum-of-errors count for incorrect Convergence Sublayer (CS) field errors. For AAL Type 3/4, this attribute provides a single count of CS\_PDUs discarded due to one of the following error conditions: BETag mismatch, BASize field value not consistent with Length field value, or Length field value not consistent with CS\_PDU length."; + +#### 5.4.135 Sum of incorrect SAR field errors (sumOfIncorrectSARFieldErrors) + +sumOfIncorrectSARFieldErrors ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR sumOfIncorrectSARFieldErrorsBeh; + +REGISTERED AS {attribute 135}; + +sumOfIncorrectSARFieldErrorsBeh BEHAVIOUR + +DEFINED AS + +"This attribute provides a sum-of-errors count for incorrect Segmentation And Reassembly (SAR) field errors. For AAL Type 3/4, this attribute provides a single count of SAR\_PDUs discarded due to one of the following errors: CRC violation, unexpected Sequence Number (SN) field value, or unexpected MID field value."; + +#### 5.4.136 Sum of invalid CS field errors (sumOfInvalidCSFieldErrors) + +sumOfInvalidCSFieldErrors ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR sumOfInvalidCSFieldErrorsBeh; + +REGISTERED AS {attribute 136}; + +sumOfInvalidCSFieldErrorsBeh BEHAVIOUR + +DEFINED AS + +"This attribute provides a sum-of-errors count for invalid Convergence Sublayer (CS) field errors. For AAL Type 3/4, this attribute provides a single count of the number of CS\_PDUs discarded due to one of the following error conditions: Common Part Indicator (CPI) field not equal to 0, Alignment field value not equal to 0, or BASize field value < 37 octets for multi-segment messages. For AAL Type 5, this attribute provides a single count of the number of CS\_PDUs discarded due to one of the following error conditions: Invalid Common Part Indicator (CPI), oversized received SDU, or length violation."; + +#### 5.4.137 Sum of invalid SAR field errors (sumOfInvalidSARFieldErrors) + +sumOfInvalidSARFieldErrors ATTRIBUTE + +DERIVED FROM "ITU-T Rec. X.721":counter; + +BEHAVIOUR sumOfInvalidSARFieldErrorsBeh; + +REGISTERED AS {attribute 137}; + +sumOfInvalidSARFieldErrorsBeh BEHAVIOUR + +DEFINED AS + +"This attribute provides a sum-of-errors count for invalid Segmentation And Reassembly (SAR) field errors. For AAL Type 3/4, this attribute provides a single count of the number of SAR\_PDUs discarded due to one of the following error conditions: MID = 0 when there is multiplexing, MID not equal to 0 when there is no multiplexing, Length field not equal to 44 octets for a BOM or COM, Length field not in the set [4, 8, ..., 44] octets or 63 octets for an EOM, or Length field not in the set [8, 12, ..., 44] octets for an SSM."; + +#### 5.4.138 Supplementary service independent for broadband pointer list (supplementaryServiceIndBbPtrList) + +supplementaryServiceIndBbPtrList ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SetOfInstances; + +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; + +BEHAVIOUR supplementaryServiceIndBbPtrListBeh; + +REGISTERED AS {attribute 138}; + +**supplementaryServiceIndBbPtrListBeh BEHAVIOUR** + +**DEFINED AS** + +"This is a set-valued attribute whose value(s) points to instances of subclasses of the supplementaryServiceIndBb object class."; + +#### **5.4.139 Termination point and VPCI pointer list (tpAndVpciPtrList)** + +**tpAndVpciPtrList ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.TpAndVpciPtrList;** + +**MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION;** + +**BEHAVIOUR tpAndVpciPtrListBeh;** + +**REGISTERED AS {attribute 139};** + +**tpAndVpciPtrListBeh BEHAVIOUR** + +**DEFINED AS** + +"This is a set-valued attribute whose value(s) point to instances of termination point classes. A VPCI value is related to every pointer."; + +#### **5.4.140 Termination point and VPCI Signalling Pointer List (tpAndVpciSigPtrList)** + +**tpAndVpciSigPtrList ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.TpAndVpciSigPtrList;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR tpAndVpciSigPtrListBeh;** + +**REGISTERED AS {attribute 140};** + +**tpAndVpciSigPtrListBeh BEHAVIOUR** + +**DEFINED AS** + +"This is a set-valued attribute whose value(s) point to instances of the vpTTPBidirectional managed object class or its subclasses. This vpTTPBidirectional object instances terminate the VPC's managed by this uni access. A VPCI value is related to every pointer, corresponding to the two octets defined for ITU-T UNI signalling. In the case of associated signalling, additionally a signalling channel pointer is related to every pointer. The optional signChannel in the associated ASN.1 definition which identifies the signalling channel for associated signalling is omitted for non-associated signalling."; + +#### **5.4.141 Termination point list (terminationPointList)** + +**terminationPointList ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ObjectList;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR terminationPointListBeh;** + +**REGISTERED AS {attribute 141};** + +**terminationPointListBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute provides an ordered list of the termination points (e.g. nDS0/DS1/DS3/E3/J2/Frame Relay) that are interworked. The traffic characteristics of the interworked ATM VC termination point must be able to accommodate the combination of traffic characteristics of all the termination points in this list."; + +#### 5.4.142 Timeslot pointer (timeslotPtr) + +**timeslotPtr ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.ObjectInstance; +MATCHES FOR EQUALITY; +BEHAVIOUR timeslotPtrBeh; +REGISTERED AS {attribute 142}; + +**timeslotPtrBeh BEHAVIOUR** +DEFINED AS +"Pointer to the terminated timeslot (e.g. e0CTP, ds0CTP)."; + +#### 5.4.143 Timing relation (timingRelation) + +**timingRelation ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.TimingRelation ; +MATCHES FOR EQUALITY; +BEHAVIOUR timingRelationBeh; +REGISTERED AS {attribute 143}; + +**timingRelationBeh BEHAVIOUR** +DEFINED AS +"This attribute indicates the timing relation between sender and receiver (end-to-end)."; + +#### 5.4.144 Transit delay limit (transitDelayLimit) + +**transitDelayLimit ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.TransitDelayLimit ; +MATCHES FOR EQUALITY; +BEHAVIOUR transitDelayLimitBeh; +REGISTERED AS {attribute 144}; + +**transitDelayLimitBeh BEHAVIOUR** +DEFINED AS +"This entity describes the range of transit delay value (in micro seconds) for the underlying routes. +The propagation delay (delay already encountered as signalled) plus the transit delay (for this route) +have to be less than the end to end transit delay required by the user." ; + +#### 5.4.145 Two calling party number delivery (twoCallingPartyNumberDelivery) + +**twoCallingPartyNumberDelivery ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Boolean; +MATCHES FOR EQUALITY; +BEHAVIOUR twoCallingPartyNumberDeliveryBeh; +REGISTERED AS {attribute 145}; + +**twoCallingPartyNumberDeliveryBeh BEHAVIOUR** +DEFINED AS +"This attribute indicates whether two calling party numbers have to be sent to the called party if +two were received."; + +#### 5.4.146 UNI access identifier (uniAccessId) + +**uniAccessId ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType; +MATCHES FOR EQUALITY; +BEHAVIOUR uniAccessIdBeh; +REGISTERED AS {attribute 146}; + +**uniAccessIdBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute is used to name instances of the uniAccess managed object class."; + +#### **5.4.147 Used algorithm (usedAlgorithm)** + +**usedAlgorithm ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.UsedAlgorithm;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR usedAlgorithmBeh;** + +**REGISTERED AS {attribute 147};** + +**usedAlgorithmBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute describes the method how to select a resource from the pointer list."; + +#### **5.4.148 User data identifier (userDataId)** + +**userDataId ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR userDataIdBeh;** + +**REGISTERED AS {attribute 148};** + +**userDataIdBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute is used to name objects of the userData managed object class."; + +#### **5.4.149 User data pointer (userDataPtr)** + +**userDataPtr ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.PointerOrNull;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR userDataPtrBeh;** + +**REGISTERED AS {attribute 149};** + +**userDataPtrBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute describes a single pointer to an object of the userData object class or its subclasses."; + +#### **5.4.150 Virtual path group identifier (virtualPathGroupId)** + +**virtualPathGroupId ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR virtualPathGroupIdBeh;** + +**REGISTERED AS {attribute 150};** + +**virtualPathGroupIdBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute is used to name instances of the virtualPathGroup managed object class."; + +#### **5.4.151 Virtual path type (vpType)** + +**vpType ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.VpType;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR vpTypeBeh;** + +**REGISTERED AS {attribute 151};** + +**vpTypeBeh BEHAVIOUR** + +**DEFINED AS** + +"This attribute indicates whether a virtual path can be used for permanent, for on-demand or for both types of virtual channels."; + +#### **5.4.152 XTPSG combination identifier (xtpsgCombId)** + +**xtpsgCombId ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType ;** + +**MATCHES FOR EQUALITY;** + +**BEHAVIOUR xtpsgCombIdBeh;** + +**REGISTERED AS {attribute 152};** + +**xtpsgCombIdBeh BEHAVIOUR** + +**DEFINED AS** + +"This entity describes the object identifier attribute of the object class 'xtpsgComb'." ; + +### **5.5 Definition of actions** + +#### **5.5.1 Add termination point (addTerminationPoint)** + +**addTerminationPoint ACTION** + +**BEHAVIOUR addTerminationPointBeh;** + +**MODE CONFIRMED;** + +**WITH INFORMATION SYNTAX ASN1DefinedTypesModule.AddTerminationPointInfo;** + +**WITH REPLY SYNTAX ASN1DefinedTypesModule.AddTerminationPointReply;** + +**REGISTERED AS {action 1};** + +**addTerminationPointBeh BEHAVIOUR** + +**DEFINED AS** + +"This action is used to add one or more termination point objects to the identified interworkingVcTtpBidirectional. The traffic characteristics of the interworked ATM VC termination point must be able to accommodate the additional termination point. + +Supplied with this action is the following information: + +- **New TPs:** This parameter identifies the additional Termination Points to be added to the existing terminationPointList attribute of the identified interworkingVcTtpBidirectional object. +- **InterworkingVcTtpBidirectional:** This parameter identifies the instance of the interworkingVcTtpBidirectional object class to which the additional termination point to be interworked. + +If the request is granted, the terminationPointList attribute, in the interworkingVcTtpBidirectional object, shall be reset to reflect the new termination point added."; + +#### **5.5.2 Remove termination point (removeTerminationPoint)** + +**removeTerminationPoint ACTION** + +**BEHAVIOUR removeTerminationPointBeh;** + +**MODE CONFIRMED;** + +**WITH INFORMATION SYNTAX ASN1DefinedTypesModule.RemoveTerminationPointInfo;** + +**WITH REPLY SYNTAX ASN1DefinedTypesModule.RemoveTerminationPointReply;** + +**REGISTERED AS {action 2};** + +**removeTerminationPointBeh** BEHAVIOUR + +DEFINED AS + +"This action is used to remove one or more termination point objects from the identified interworkingVcTtpBidirectional. + +Supplied with this action is the following information: + +- Existing TPs: This parameter identifies the existing Termination Points to be removed from the identified interworkingVcTtpBidirectional object. +- InterworkingVcTtpBidirectional: This parameter identifies the instance of the interworkingVcTtpBidirectional object class from which the identified termination points should be removed. + +If the request is granted, the terminationPointList attribute, in the interworkingVcTtpBidirectional object, shall be reset to reflect the remaining termination points."; + +## 5.6 Definition of behaviour + +### 5.6.1 Set by manager behaviour (setByManagerBeh) + +**setByManagerBeh** BEHAVIOUR + +DEFINED AS + +"value is set by the managed system"; + +## 6 Type Definitions + +**ASN1DefinedTypesModule** {itu-t(0) recommendation(0) q(17) 824(824) dot(127) bsm(6) informationModel(0) asn1Module(2) asn1TypeModule(0)} + +**DEFINITIONS IMPLICIT TAGS ::=** + +**BEGIN** + +-- EXPORTS everything + +**IMPORTS** + +**ObjectInstance** + +**FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)}** + +**NameType,** + +**ObjectList,** + +**PointerOrNull,** + +**ProblemCause** + +**FROM ASN1DefinedTypesModule {ccitt recommendation m gnm(3100) informationModel(0) asn1Modules(2) asn1DefinedTypesModule(0)}** + +**ProbableCause** + +**FROM Attribute-ASN1Module {joint-iso-ccitt ms(9) smi(3) part2(2) asn1Module(2) 1}** + +**integerZero** + +**FROM** + +**AtmMIBMod {itu-t(0) recommendation(0) i(9) atmm(751) informationModel(0) asn1Module(2) atm(0)};** + +-- additional value definitions to probableCause production + +**cellStarvation ProbableCause ::= globalValue : {atmSwitchProbableCause 1}** + +**informationModel OBJECT IDENTIFIER ::= {itu-t(0) recommendation(0) q(17) 824(824) dot(127) bsm(6) informationModel(0) asn1Module(2) asn1TypeModule(0)}** + +**standardSpecificExtension OBJECT IDENTIFIER ::= {informationModel standardSpecificExtension(0)}** + +``` + +managedObjectClass OBJECT IDENTIFIER ::= {informationModel managedObjectClass(3)} +package OBJECT IDENTIFIER ::= {informationModel package(4)} +nameBinding OBJECT IDENTIFIER ::= {informationModel nameBinding(6)} +attribute OBJECT IDENTIFIER ::= {informationModel attribute (7)} +action OBJECT IDENTIFIER ::= {informationModel action(9)} +notification OBJECT IDENTIFIER ::= {informationModel notification(10)} +atmSwitchProbableCause OBJECT IDENTIFIER ::= {standardSpecificExtension 0} + +AalMode ::= ENUMERATED { + messageAssured (0), + messageUnassured (1), + streamingAssured (2), + streamingUnassured (3)} + +AalType ::= ENUMERATED { + aal1 (0), + aal2 (1), -- encoded for future use + aal34 (2), + aal5 (3)} + +AbstractDestinationPtr ::= ObjectInstance + +ActiveListOfRouteTpsPtr ::= ObjectInstance + +ActiveTargetPtr ::= CHOICE { + pointer ObjectInstance, + carrierRequired NULL } + +AddTerminationPointInfo ::= SEQUENCE { + newTPs NewTPs, + interworkingVcTtpBidirectionalInstance ObjectInstance} + +AddTerminationPointReply ::= SEQUENCE OF SEQUENCE { + tpAdded ObjectInstance, + tpNotAdded ProblemCause OPTIONAL} + +AssignNonAssign ::= INTEGER { + assign (0), + nonAssign (1) } + +BearerCapab ::= INTEGER { + dbr (0), + sbrRt (1), + sbrNrt (2), + abr (3), + ubr (4), + abtDt (5), + abtIt (6) } + +BlockedForMaintenance ::= INTEGER { + blocked (0), + unblocked (1) } + +Boolean ::= BOOLEAN + +BufferRelease ::= BOOLEAN +bufferReleaseDefault BufferRelease ::= TRUE + +CallingPartyCategory ::= CHOICE { + unused NULL, + category Category } + +``` + +**Category ::= BIT STRING (SIZE (8))** *-- acc. Rec. Q.2763* +**CarrierCode ::= NetworkIdentification** +**CarrierDataPtr ::= ObjectInstance** +**CCITTNetworkPlanIndicator ::= INTEGER** +**ChannelAssociatedSignalling ::= INTEGER** +     { +         basic (0), +         e1Cas (1), +         ds1SfCas (2), +         ds1EsfCas (3), +         j2Cas (4) +     } +**Cic ::= INTEGER (0..65335)** +**CIPRequired ::= Boolean** +**ClockRecoveryType ::= ENUMERATED {** +     synchronous (0), +     srts (1), +     adaptive (2)} +**Code ::= SET OF DigitString4** +**CSPRequired ::= Boolean** +**ConnLineIdRestrictionOptions ::= SEQUENCE {** +     mode            **INTEGER {permanent(1), temporary(2)},** +     default         **INTEGER {restricted(1),** +                             **notRestr(2)}** *OPTIONAL -- for temporary mode only --* +     } +**ConnectionIdOffering ::= INTEGER {** +     exclusiveVpciExclusiveVci    (0), +     exclusiveVpciAnyVci            (1), +     noIndication                    (8) } +**connectionIdOfferingDefault ConnectionIdOffering ::= exclusiveVpciExclusiveVci** +**CdpnRepresentationType ::= INTEGER {** +     subscriber    (0), +     national        (1), +     international (2), +     unknown        (3) } +**CugBarring ::= INTEGER {** +     none            (1), +     incomingCallsBarred (2), +     outgoingCallsBarred (3)} +**CugDataNetworkIdentification ::= NumericString (SIZE(4))** *-- Rec. Q.2763* +**CugIndex ::= INTEGER (0..65535)** *-- Rec. Q.2955* +**CugInterlockCode ::= INTEGER (0..65535)** *-- Rec. Q.2763* +**DestinationCode ::= DigitString15** +**DestinationType ::= INTEGER {** +     international (1), +     national        (2), +     local            (3)} + +``` + +defaultBlockedForMaintenance BlockedForMaintenance ::= blocked + +DefaultDirectoryNumber ::= CHOICE { + noDefault NULL, + directoryNumber DirectoryNumber} + +defaultNULL ::= NULL + +defaultScreenNumber Boolean ::= TRUE + +defaultSignallingType SignallingType ::= nonassociated + +defaultTwoCallingPartyNumberDelivery Boolean ::= TRUE + +DigitComb ::= SEQUENCE OF DigitElement + +DigitCombInsert ::= SET OF SEQUENCE { + startPosition [0] INTEGER , + combination [1] DigitComb } + +DigitCombReplace ::= SET OF SEQUENCE { + startPosition [0] INTEGER , + endPosition [1] INTEGER , + combination [2] DigitComb } + +DigitElement ::= PrintableString + (FROM("1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"|"0"|"A"|"B"|"C"|"D"|"E"|"F")) + (SIZE (1)) + +DigitManipPtr ::= ObjectInstance + +DigitString4 ::= PrintableString + (FROM("1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"|"0"|"A"|"B"|"C"|"D"|"E"|"F")) + (SIZE (1..4)) + +DigitString8 ::= PrintableString + (FROM("1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"|"0"|"A"|"B"|"C"|"D"|"E"|"F")) + (SIZE (1..8)) + +DigitString15 ::= PrintableString + (FROM("1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"|"0"|"A"|"B"|"C"|"D"|"E"|"F")) + (SIZE (1..15)) + +DigitSuppress ::= SET OF SEQUENCE { + startPosition [0] INTEGER , + endPosition [1] INTEGER } + +DirectoryNumber ::= E164DN + +E164DN ::= SEQUENCE { + countryCode [0] NumericString (SIZE (1..4)) OPTIONAL, + nationalSignificantNumber [1] SEQUENCE { + nationalDestinationNumber [0] NumericString (SIZE (1..6)) OPTIONAL, + subscriberNumber [1] NumericString (SIZE (1..8))} + } + +emptySet SetOfInstances ::= { } + +ExcludedSubscriberCodes ::= SET OF PrintableString + (FROM("1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"|"0"|"A"|"B"|"C"|"D"|"E"|"F")) + +ExistingTPs ::= SEQUENCE OF ObjectInstance + +FecMethod ::= ENUMERATED{ + noFEC (0), + lossSensitiveSignalFEC (1), + delaySensitiveSignalFEC (2)} + +``` + +**InitialSubscriberCodes ::= SET OF PrintableString** +**(FROM("1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"|"0"|"A"|"B"|"C"|"D"|"E"|"F"))** + +**Integer ::= INTEGER** + +**InterCugAccess ::= INTEGER** + {none (1), + outgoingPermanentAccess (2), + outgoingPerCallAccess (3), + incomingAccess (4), + outgoingPermanentAndIncomingAccess (5), + outgoingPerCallAndIncomingAccess (6) } + +**LinkType ::= INTEGER {** + national (0), + international (1) } + +**ListOfRoutesPtrList ::= SEQUENCE OF ObjectInstance** + +**ListOfLinkGroupsPtrList ::= SEQUENCE OF ObjectInstance** + +**LocalAreaCode ::=** +**NumericString (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"))** + +**MaintenanceSignallingRunning ::= BOOLEAN** + +**MaxCc ::= INTEGER** +**maxCcDefault MaxCc ::= 4** + +**MaxCpcsPduSize ::= SEQUENCE {** + forward [0] INTEGER (1..65535) OPTIONAL, + backward [1] INTEGER (1..65535) OPTIONAL } + +**MaxDigits ::= INTEGER** + +**MaxInformationFieldLength ::= INTEGER** +**maxInformationFieldLengthDefault MaxInformationFieldLength ::= 4096** + +**MaxLengthSscopUuField ::= INTEGER** +**maxLengthSscopUuFieldDefault MaxLengthSscopUuField ::= 4096** + +**MaxPd ::= INTEGER** +**maxPdDefault MaxPd ::= 25** + +**MaxSscopCreditToPeer ::= INTEGER** +**maxSscopCreditToPeerDefault MaxSscopCreditToPeer ::= 16** + +**MaxStat ::= INTEGER** +**maxStatDefault MaxStat ::= 67** + +**MidRange ::= SEQUENCE {** + lowvalue [0] INTEGER (1..66536), + highvalue [1] INTEGER (1..66536) } + +**MinDigits ::= INTEGER** + +**NationalNetworkIdenPlanIndicator ::= INTEGER** + +**NatureOfAddress ::= DestinationType** + +**NbTransferCapability ::= INTEGER {** + speech (0), + r64kbitUnrestricted (1), + r56kbitDigitalRestricted (2), + r3point1khzAudio (3), + r7khzAudio (4), + video (5) } + +``` + +NbTransferCapabilitySet ::= SET OF NbTransferCapability + +NetworkBorder ::= INTEGER { + intraNetwork (0), + interNetwork (1) } + +NetworkIdentification ::= DigitString8 + +NetworkIdentificationPlan ::= CHOICE +{ + cCITNetworkPlanIndicator [0] CCITNetworkPlanIndicator, + nationalNetworkIdenPlanIndicator [1] NationalNetworkIdenPlanIndicator } + +NetworkType ::= INTEGER { + transit (0), + nonTransit (1) } + +NewTPs ::= SEQUENCE OF ObjectInstance + +Null ::= NULL + +Origin ::= CHOICE { + unused NULL, + origin INTEGER } + +OwnInternationalCode ::= NumericString +(FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9")) + +PollAfterRetransmission ::= BOOLEAN + +PreferredCarrier ::= SEQUENCE { -- acc. Rec. Q.2763 + networkIdentificationPlan NetworkIdentificationPlan, + typesOfNetworkIdentification TypesOfNetworkIdentification, + networkIdentification NetworkIdentification } + +PreferredCugIndex ::= CHOICE{ + notDefined [0] NULL, + defined [1] CugIndex} + +PropagationDelay ::= INTEGER + +RemoteBlocking ::= INTEGER { + remoteBlocked (0), + remoteUnblocked (1) } + +RemoteBlockingReason ::= INTEGER { + none (0), + mob (1), + hob (2), + mobAndHob (3) } + +RemoveTerminationPointInfo ::= SEQUENCE { + existingTPs ExistingTPs, + interworkingVcTtpBidirectionalInstance ObjectInstance} + +RemoveTerminationPointReply ::= SEQUENCE OF SEQUENCE { + tpInstance ObjectInstance, + tpRemovalProblem ProblemCause OPTIONAL + -- absent if tpInstance is removed +} + +ReqBandwidthEgress ::= SEQUENCE { + lowerLimit INTEGER, + upperLimit INTEGER } + +``` + +``` + +ReqBandwidthIngress ::= SEQUENCE { + lowerLimit INTEGER, + upperLimit INTEGER } + +ReqBearerCapab ::= SET OF BearerCapab + +ReqNbTransferCapability ::= CHOICE { + withoutNbCapab NULL, + withNbCapab NbTransferCapabilitySet } + +RingTimeLimit ::= INTEGER + +SearchMethod ::= INTEGER { + forwardSequential (0), + backwardSequential (1), + forwardCyclic (2), + backwardCyclic (3) } + +SendTns ::= BOOLEAN + +SetOfInstances ::= SET OF ObjectInstance + +SignallingStandard ::= INTEGER { + itu (0), + atm31 (1), + atm40 (2) } + +SignallingProtocol ::= INTEGER { + nisup (0), + bisup (1) } + +SignallingType ::= INTEGER { + nonassociated (0), + associated (1) } + +SscopTimerCc ::= INTEGER +sscopTimerCcDefault SscopTimerCc ::= 1000 + +SscopTimerIdle ::= INTEGER +sscopTimerIdleDefault SscopTimerIdle ::= 15000 + +SscopTimerKeepAlive ::= INTEGER +sscopTimerKeepAliveDefault SscopTimerKeepAlive ::= 2000 + +SscopTimerNoResponse ::= INTEGER +sscopTimerNoResponseDefault SscopTimerNoResponse ::= 7000 + +SscopTimerPoll ::= INTEGER +sscopTimerPollDefault SscopTimerPoll ::= 750 + +SscsType ::= INTEGER { + null (0), + dataAssured (1), + dataNonAssured (2), + frameRelay (3)} + +SubscriberCategory ::= INTEGER { + unknownAtThisMoment (0), -- acc. Rec. Q.2763 + operatorLanguageFrench (1), -- for national use + operatorLanguageEnglish (2), + operatorLanguageGerman (3), + operatorLanguageRussian (4), + operatorLanguageSpanish (5), + nationalOperator (9), -- for national use + ordinaryCallingSubscriber (10), +} + +``` + +``` + + callingSubscriberWithPriority (11), + dataCall (12), + testCall (13), + payPhone (15) } (0..255) + +subscriberCategoryDefault SubscriberCategory ::= ordinaryCallingSubscriber + +SubType ::= INTEGER { + null (0), + voiceBand (1), + circuitEmulationSynchronous (2), + circuitEmulationAsynchronous (3), + highQualityAudio (4), + video (5)} + +TimingRelation ::= INTEGER { + timingNotRequired (0), + timingRequired (1) } + +TpAndVpciSigPtrList ::= SET OF SEQUENCE { + tp ObjectInstance, + vpci VpciValue, + sigChannel ObjectInstance OPTIONAL} + +TransitDelayLimit ::= SEQUENCE { + lowerLimit INTEGER, + upperLimit UpLimit } + +TypesOfNetworkIdentification ::= INTEGER + +UpLimit ::= CHOICE { + noLimit NULL, + limit INTEGER } + +UsedAlgorithm ::= INTEGER { + sequential (0), + cyclic (1) } + +VpciValue ::= INTEGER (0..65535) + +TpAndVpciPtrList ::= SET OF SEQUENCE { + tp ObjectInstance, + vpci VpciValue } + +VpType ::= INTEGER { + on-demand (0), + permanent (1), + mixed (2)} + +END -- of ASN1DefinedTypesModule + +``` + +## 7 Protocol stacks + +The protocol stacks specified in Recommendations Q.811, Q.812, G.773 and the SDH digital cross-connect part of Recommendation G.784 can be used as part of this Recommendation. The following Recommendations should be used to extend these stacks to include ATM: + +- Q.2811 Broadband Q3 and X interfaces – Lower Layer Protocols; +- Q.2812 Broadband Q3 and X interfaces – Upper Layer Protocols. + +## ANNEX A + +### **Management requirements** + +This annex uses as a reference Recommendation I.751 [4] about the management of the ATM cross-connects, and describes or enhances management requirements for those aspects present only in the ATM switch. + +The complete set of management requirements for ATM switching network elements has to be composed from this and the above-mentioned Recommendation. + +ATM adaptation layer 5 is specified in Recommendation I.363.5 [2] + +The signalling ATM adaptation layer is split into the Service Specific Connection-Oriented Protocol (SSCOP) defined in Recommendation Q.2110 [7] and the Service Specific Coordination Function (SSCF) defined for the UNI in Recommendation Q.2130 [8] and for the NNI in Recommendation Q.2140 [9]. + +DSS 2 user signalling is defined in Recommendation Q.2931 [11] and B-ISUP network signalling is defined in Recommendations Q.2761 to Q.2764 [10]. + +#### **A.1 Configuration management functions** + +Configuration management provides functions to exercise control over, identify, collect data from and provide data to NEs. + +On one side, in an ATM cross-connect VP/VC connections are set up, modified and released via configuration management functions. On the other side, in an ATM switch, connections are set up, modified and released by signalling procedures, and configuration management is concerned mainly with managing control entities. + +##### **A.1.1 General NE configuration functions** + +This group of functions includes the set of procedures needed to bring the NE into service and to take care of hardware and software modifications and upgrades. It also includes the requirements for customer administration and call routing. + +##### **A.1.2 ATM transport layer configuration functions** + +###### **A.1.2.1 VPC/VCC configuration functions** + +The capability of setting a VP/VC connection in an unlocked administrative state (traffic flow is enabled), or in a locked state (traffic flow is suspended) must be provided. + +This capability will be used by system management to take corrective actions in response to performance degradation or fault of the virtual connection. + +### **A.1.3 ATM adaptation layer configuration functions** + +The various ATM adaptation layers generate requirements for configuration management and these requirements which are listed here. Each trail on the virtual channel layer supports a single ATM adaptation layer, which may either be configured or defined by call control. Unless otherwise stated, changes to the ATM adaptation layer may be requested, but such a request may be rejected if the change is not supported by the implementation. Likewise, unless otherwise stated, it shall always be possible to read the details of the actual configuration of the ATM adaptation layers. + +#### **A.1.3.1 Configuration management requirements for ATM adaptation layer 5** + +The following items may be read and changes may be requested: + +- the maximum number of octets in CPCS-PDU payload which is supported by ATM adaptation layer 5 both for transmit and for receive directions; +- the form of data encapsulation used over the ATM adaptation layer 5 Service Specific Convergence Sublayer (SSCS). + +#### **A.1.3.2 Configuration management requirements for the signalling ATM adaptation layer** + +The type of Service Specific Convergence Sublayer (SSCS) used may be read and changes may be requested. + +It should be possible to configure timer values for the Signalling ATM Adaptation Layer (SAAL). + +### **A.1.4 Broadband signalling configuration functions** + +#### **A.1.4.1 Co-ordination of VPCI values** + +There is a requirement for management co-ordination between interconnected switches so that the switch which handles the signalling is aware of how the VPCI mappings differ from those of directly connected accesses when the access is connected indirectly via another switch with cross-connect functionality. + +### **A.2 Performance management functions** + +Performance management provides functions to evaluate and report upon the behaviour of telecommunications equipment and the effectiveness of the network element. + +Performance management functions will be based on Recommendation Q.822; the set of monitored parameters is detailed in the following subclauses. + +The identified functions for the ATM switches are concerned with performance and error measurements to report the general behaviour of the network element and can be useful to detect situations of degraded performance and identify possible causes of the abnormal situation. + +### **A.2.1 General NE performance functions** + +### **A.2.2 ATM transport layer performance functions** + +Three main sets of parameters need to be monitored; the first one is related to the OAM F4 and F5 flows mechanism, the second one deals with load and traffic related parameters, while the third one relies on system-dependent techniques. + +#### **A.2.2.1 F4 / F5 OAM flows related parameters** + +Performance monitoring is based on the use of OAM flows, both segment and end-to-end (see Recommendation I.610). At the ATM layer the F4 and F5 flows are considered. + +Each trail termination point must have the capability to generate the F4/F5 flows on the outgoing link and/or to process the incoming F4/F5 flows. + +These flows can be used to monitor the following parameters, at VP and VC layer, respectively: + +- bit error rate; +- cell loss/insertion; +- cell transfer delay; +- cell delay variation. + +Suitable mechanisms are present in the flow, to support these functions, such as the Block Error Detection Code (BIP-X: see Recommendation I.610). + +When the measured values of these parameters exceed a preassigned threshold, an alarm is generated and sent to the TMN and to the control plane functions. + +#### **A.2.2.2 Load and traffic related parameters** + +The following parameters related to load and traffic need to be monitored; various methods can be used not included in the OAM flow mechanism: + +- internal overload/congestion; +- external congestion; +- blocking at virtual connection level. + +Functions responsible for the supervision of the overload and congestion state of the node (internal congestion) and of the network (external congestion) are examined below. + +Possible causes of overload can be faults inside the switching fabric, lack of internal capacity due to a poor system engineering that is unable to deal with traffic bursts, or malfunctioning of the UPC/NPC functions. + +Overload conditions can be indicated by overflow of the buffers located at the input and/or output of the switching fabric. In this case the automatic reaction to the condition is to discard cells, possibly in a selective way if a priority mechanism has been adopted. + +If the overload condition persists, the switch can enter into a congestion state. This status is also shown by a permanent buffer overflow condition. + +When a network elements enters in a congestion state, the system has to inform all the downstream nodes about its condition; a notification of this state is inserted in all the cells leaving the node through a particular code on the PTI field of the ATM cell header (I.361). + +The congestion indication is therefore propagated forward in the network. + +Monitoring of congested cells on a VP/VC basis can be used to prevent the congestion of the whole network. + +At virtual connection level, the switch can experience a connection blocking state when it is impossible to connect an allocatable VP/VC connection on an input interface with an equivalent allocatable VP/VC connection on the corresponding output interface. The connection control cannot accept the new VP/VC connection, although the interfaces have enough capacity available. + +Causes of this event can be internal blocking inside the switching fabric, due to implementation of the switching fabric itself with a blocking architecture, or use of resources management policies to guarantee the requested quality of service. + +### **A.2.2.3 Additional parameters** + +The following parameters need also to be monitored: + +- HEC error check; +- Cell multiplexing error check; +- UPC/NPC intervention. + +The HEC and the cell multiplexing error checking functions are performed at the lower layers of the B-ISDN protocol reference model (at physical layer and ATM layer, respectively). In the first case indications are provided about cells affected by multiple errors on the header, so that correction procedures cannot be applied; in the second case cells come in with an apparently correct cell header, but the internal VCI/VPI translation table does not contain any valid entry for that VCI/VPI. This means that a VCI/VPI multiplexing error has occurred. + +It is assumed that in both cases cells are discarded. + +The UPC and NPC functions mark or discard cells when they exceed the agreed service parameters. The number of tagged cells need to be counted on a VP and/or VC basis. + +### **A.2.3 ATM adaptation layer performance functions** + +Sets of parameters need to be monitored for the various ATM adaptation layers. + +### **A.2.3.1 Performance management requirements for ATM adaptation layer 5** + +Performance monitoring of ATM adaptation layer 5 is concerned with the use of the payload type field in the ATM cell header and the use of the last 8 octets of the CPCS-PDU [2]. In particular, the following should be monitored: + +- undelineated ATM cell sequences which are longer than the maximum number of cells in a CPCS-PDU; +- inconsistencies between the number of ATM cells in a CPCS-PDU as indicated by the coding in the cells' payload type field and the length of the CPCS as indicated in the length field of the CPCS-PDU trailer; +- the error rate as detected by the CRC field in the CPCS-PDU. + +In addition, the following performance statistics should be available: + +- number of received and transmitted PDUs; +- PDUs discarded due to CRC errors; +- PDUs discarded due to reassembly time out; +- PDUs discarded due to overlarge size; +- PDUs discarded due to protocol errors. + +## **A.3 Fault management functions** + +Fault management is a set of functions which enables the detection, isolation and correction of abnormal operation of the ATM switch. + +### **A.3.1 Alarm surveillance** + +#### **A.3.1.1 General NE alarm surveillance functions** + +No requirements identified. + +#### **A.3.1.2 ATM transport layer alarm surveillance functions** + +When a fault or a condition of severely degraded performance situation is detected, a connection termination point must be able to send a VP-AIS alarm on the OAM F4/F5 flow, and to send an alarm to the TMN and to the control plane functions. + +#### **A.3.1.3 ATM adaptation layer alarm surveillance functions** + +Detected problems in the ATM adaptation layers will generate various alarms. + +#### **A.3.1.3.1 Alarm surveillance management requirements for ATM adaptation layer 5** + +Alarms are generated under the following conditions: + +- when the payload type field in the ATM cell header fails to indicate the last ATM cell of a CPCS-PDU for more than the maximum number of cells in a CPCS-PDU; +- when the number of ATM cells in a CPCS-PDU is not consistent with the length of the CPCS as indicated in the length field of the CPCS-PDU trailer; +- when the error rate as detected by the CRC field in the CPCS-PDU becomes too high. + +### **A.3.2 Test and fault localisation** + +#### **A.3.2.1 General NE test and fault localisation functions** + +No requirements identified. + +#### **A.3.2.2 ATM transport layer test and fault localisation functions** + +The mechanism of continuity check, performed using OAM F4/F5 flows, is used for testing the integrity of the translation and routing tables of the NE. When a connection termination point does not transmit user cells and there is no failure indication through the VP-AIS and VP-FERF signals, then it must be able to send a continuity check signal. If the receiving termination point receives no OAM cells, it will generate a VP-FERF signal. This mechanism is useful for localisation of the termination points that has experienced a failure. + +#### **A.3.2.3 ATM adaptation layer test and fault localisation functions** + +When a fault is suspected in the ATM adaptation layers, or an alarm has been generated, it may be necessary to perform activities to check the correct operation of the ATM adaptation layers and to identify the origin of a confirmed ATM adaptation layer fault. + +##### **A.3.2.3.1 Testing and fault localisation requirements for ATM adaptation layer 5** + +Non-intrusive testing of ATM adaptation layer 5 shall be carried out by generating and detecting patterns on the CPCS-UU octet of the CPCS-PDU trailer and/or on the padding octets. Intrusive testing of ATM adaptation layer 5 shall be carried out by generating and detecting patterns on the CPCS-PDU payload. These patterns may either be looped back to their source or sent in a single direction. + +### **A.3.3 Fault correction** + +#### **A.3.3.1 General NE fault correction functions** + +No requirements identified. + +### **A.3.3.2 ATM transport layer fault correction functions** + +When a failure in a VP/VC connection occurs, it is possible to perform fault correction by protection switching. + +The mechanism of protection switching is based on the use of a spare VP/VC connection, shared among a group of active virtual connections; it is directed by Layer Management. + +## **A.4 Modelling specific requirements** + +Recommendation Q.2764 describes a parameter Transit Network Selection for the setup messages. This parameter may be "included in the setup message from the calling party or provided on a subscription basis". This information "is used for routing the call/connection, e.g. to a specific B-ISDN". + +To support this parameter, it should be possible to assign a preferred carrier (transit network) value either to the whole customer or to an individual directory number. + +Recommendation Q.2764 describes a parameter Calling Party Category for the setup messages. + +To support this parameter, it should be possible to assign a category value either to the whole customer or to an individual directory number. + +The Call Routing Management allows to mark a NNI with an origination mark, to support the origination dependent routing of incoming calls. Origination dependent routing should be possible for calls coming from an UNI too. + +It should be possible to mark either the whole customer or an individual directory number with an origination mark, which can be used e.g. for the origination dependent routing. + +## **APPENDIX I** + +### **Point-to-multipoint connections** + +As long as there is no modelling of point-to-multipoint connections within ITU-T, the reader is referred to the ATM Forum Specification af-nm-0027.000 [17]. + +## **APPENDIX II** + +### **Bibliography** + +- ITU-T Recommendation E.164 (1997), *The international public telecommunication numbering plan*. +- ITU-T Recommendation G.773 (1993), *Protocol suites for Q-interfaces for management of transmission systems*. + +- CCITT Recommendation G.774 (1992), *Synchronous Digital Hierarchy (SDH) management information model.* +- ITU-T Recommendation G.803 (1997), *Architecture of transport networks based on the Synchronous Digital Hierarchy (SDH).* +- ITU-T Recommendation I.211 (1993), *B-ISDN service aspects.* +- ITU-T Recommendation I.327 (1993), *B-ISDN functional architecture.* +- ITU-T Recommendation I.356 (1996), *B-ISDN ATM layer cell transfer performance.* +- ITU-T Recommendation I.371 (1996), *Traffic control and congestion control in B-ISDN.* +- ITU-T Recommendation I.413 (1993), *B-ISDN user-network interface.* +- ITU-T Recommendation I.432 series, *B-ISDN user-network interface – Physical layer specification.* +- ITU-T Recommendation I.580 (1995), *General arrangements for interworking between B-ISDN and 64 kbit/s based ISDN.* +- ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network.* +- ITU-T Recommendation M.3100 (1995), *Generic network information model.* +- ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: overview.* +- ITU-T Recommendation M.3400 (1997), *TMN management functions.* +- ITU-T Recommendation Q.822 (1994): *Stage 1, stage 2 and stage 3 description for the Q3 interface – Performance management.* +- CCITT Recommendation X.208 (1988) | ISO/IEC 8824:1990, *Specification of Abstract Syntax Notification One (ASN.1).* +- ITU-T Recommendation X.701 (1997) | ISO/IEC 10040:1998, *Information technology – Open Systems Interconnection – System management overview.* +- CCITT Recommendation X.722 (1992) | ISO/IEC 10165-4:1992, *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects.* +- CCITT Recommendation X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function.* + +- CCITT Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, *Information technology – Open Systems Interconnection – Systems Management: Event report management function.* +- CCITT Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open systems Interconnection – Systems Management: Log control function.* +- ITU-T Recommendation X.737 (1995) | ISO/IEC 10164-14:1996, *Information technology – Open Systems Interconnection – Systems Management: Confidence and diagnostic test categories.* +- ITU-T Recommendation X.738 (1993) | ISO/IEC 10164-13:1995, *Information technology – Open Systems Interconnection – Systems Management: Summarization function.* +- ITU-T Recommendation X.739 (1993) | ISO/IEC 10164-11:1994, *Information technology – Open Systems Interconnection – Systems Management: Metric objects and attributes.* +- ITU-T Recommendation X.745 (1993) | ISO/IEC 10164-12:1994, *Information technology – Open Systems Interconnection – Systems Management: Test management function.* +- ITU-T Recommendation X.746 (1995) | ISO/IEC 10164-15:1995, *Information technology – Open Systems Interconnection – Systems Management: Scheduling function.* +- ATM Forum Specification, *ATM User-Network Interface Specification, Version 3.0.* +- ATM Forum Specification, *ATM User-Network Interface Specification, Version 3.1.* +- ATM Forum Specification, *CMIP Specification for the M4 Interface, Version 1.0.* +- ATM Forum Specification, *M4 Interface Requirements and Logical MIB: ATM Network Element View, Version 1.0.* + +## 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.83.2-199202-I_PDF-E/01141eb99b707de5aead56f84afe3b1f_img.jpg b/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/01141eb99b707de5aead56f84afe3b1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..369fad3b49280ff27744bc1d48008db7dfef4cb7 --- /dev/null +++ b/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/01141eb99b707de5aead56f84afe3b1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24ed9c95de48c15c0c301b12527057d93ea769750e4b60961169c2e6fa5ee225 +size 21606 diff --git a/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..911be444e7a941744820f4c8651a4b7407dad36f --- /dev/null +++ b/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3427dd3d6bf673043c47bd0aa0072dee41db523aca40d67dcc7a05ae79ed8822 +size 103890 diff --git a/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4133aa65cc1cafeb0ba9ed16b63ab374db42a2bb --- /dev/null +++ b/marked/Q/T-REC-Q.83.2-199202-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ab638d3da5d40619a85594fe0293aa362aa484e81fb3a4747e29b1d8b5a1c20 +size 8771 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1e5c1987b3a25cbb9d1d0bc42d7a935f2e4b7c8 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df92c48677cb04c0920cfadb0895c2f8a89f90a28543ca3f812f76c6792959ee +size 35726 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b4714cba004f88f8b77ebff9d97d5ff2f083a83 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28b2ce525359698a16ee6b7459764400824da23a0a7db4ed240f239f12f1f357 +size 43272 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48157372b70aebb6967623e38a93b50d28059059 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f05efac3a8c0af4917246dbef1ad51623d814fb1cf3608776c0e3a0e8182219 +size 35493 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d75ae82e680c584a51b38cb6f37eba6731f0fc16 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94df6f61634d1797e7156a29e3b7b2e1709717dab108ac0c3b385bf7728cd27d +size 18868 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c4d7a697f56091721ddafc369d845f276b67c57 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1da8ace57b3b4b0818a8189bb3e92f59a494cba417ac0ee5e17cd40422cb43c9 +size 8344 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4f70e4d7ea4a60193ac95a766c8b4dda4a6feaa --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b1bd618ac5b4641055e5839873372e72b0abd073793134080c225d4cd2c7d08 +size 76170 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e38236fbf9978ed16128c6a3a659c0c2b0a47a28 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89b0d31e590819f44d53d05bb6473f0322afb52f8f86882435425c5f908aab1a +size 95827 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14c217e955b6d12eae15940ca5b45cf77c0e2749 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:731a3a9f2a8c6b139825b549cf41324191a70f04df46de9db359de37bbf0b8c2 +size 37757 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44c0eb3940eee45d92eaf648e70f29f3eec9559c --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b81b0d3e4bc6f4f3e277cfe551aaccd93f5b2501471cde13b5c85be1114e8dc +size 31245 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..138a89f10eafdb1eb3e16ec8fe9c55b03e89370c --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef5135e539b919b9d9dbb2bab24f87ca070c1797a8a47a4d7283aa6c7a5a749f +size 41414 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe7b3e5202ac0de6c0216338d43691c571a5b345 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d66cd639feff0668dfd84479d98d2d5f80d110d0c0b45b238d64c9f66f664be2 +size 19776 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59dd3bc9a9c9080d1c50e185d54ffb10c9c350f2 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bfb45fe0122d08c2480fce619c7a227354f4263f84cbafcbdedd87e07c2046c +size 12898 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fab3651cb0fd28a28d21d1a91365bfc15591c415 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1020e78fc7a72ac4c3ec1d20a7bbedea7f4a6be59fd9b8d1de4c59fc37cc5b8e +size 25006 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e44543dd026b52c8bfe3703a8d43adac36870aaf --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:966849cea905c3798c14695248b351946e12b0d7a85dc03a47299c93c8189b9a +size 37939 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66fb91de5cec61ba39db27cc0fb999ff098a159e --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8e11eb9e1b6f8c167826f54fccd603e4f8b24c570a3ccc738da9fa5840378e7 +size 40605 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e8b0a8e4dbee3cc2c7ddd54d205089b6591fbc1 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efb266e4f9ad24b1f804c01b5c6a5c5309b718b3adb7c790f46117a1b2e0ba9d +size 24357 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d771fae538c48d32185e850475343f1dc91c6004 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:861d412414fa0a0b70ba44007c8c03aa55bbed7e54afc5e93b9b35eb22c129ce +size 99791 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37c12dbb67429071e5da134b742e798de64fff96 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fb2ace64d4b11d6d3f5acbc465a22e6b1a5c5e6394397639a03c7bc88177670 +size 80317 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a30f461474d764c69e91544eed0faf8c81ea8b7 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28e8f7e3b18b7f49df9a97b3c19239d29883d6d8fd05fb4e0a19f0be96cd2448 +size 21448 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..092abf5d6351225181bd3cf3ef2f7bfb03284441 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72db5a3ddae1948b31cb853a60b7756826369d4fb75eb84a6f28114dff416dca +size 51462 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..833f4700690a2d7231a611a9316d90311b21ec0b --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0f929b6bc68adf4b0aa124bf4cde070fc667a2468778a02ca6aedacf19cb613 +size 9270 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c4228676078558cd10cf73bdf1c173e31724e2d --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5b6fd7434333bc839d7a0bd19fe31f9672ce3049e2ba6db03d0f57200a0002f +size 89958 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b5d6d146ca34c9d911b1264e9f1df1095c07499 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad5b6d28bc7e62fe579ee4729113c47a0df16c7c580cd650d09600ea45848bb4 +size 45846 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80d6a06d560437c32eccb4c375af247be71ba73d --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67d0af729d97dfff03c7767c58b7b22b3b0ed734b067f4fbe492237b9e01cde9 +size 82378 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b18898bcfd64e8b515bcf9c66a0a6e55f694e816 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:378d24d917e99a8b6553c2848c183445ca520826af6f81ec962e93e027efaeaa +size 77210 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74e79b73866d7112dd451a0b05f7f4a6d057bada --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4335d2641692a3c6e27bdbfaae8e1732d35b4e45d9cd3123876582d583af899 +size 21477 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96334306ecbf29a3275dcebf7076ed818f70f5bc --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a7acc4a44f5b116b32570ca6516a6bea90e6b44318caae9222fba53ddf39940 +size 98626 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3ec51242c19cd9461e8ef85f91350219244fe9b --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a22742f8d23cc2e0d925efd71b54e375931fca1650fbaf0a10bd0c4cdf92a5bc +size 11384 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..444c91f2602abb535613597ab38607d4df2ba0be --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d21ca3965a583f6be14ccb21b31df8f12a268f3458e2ba1408d4a5287214cd3 +size 11071 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15db8be6e1945a669b8e5fbaa837b16b6542d03e --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aebef68aa98052cbac333bf83d2f1e7700c98702092540ee1199618857ef185b +size 188706 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c182e882744ab2be4930939da07f719a9360931 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9e78633af8112887f94a9dcb3395e1c65e8f9539c00d2fbf28b62b38cadbb5f +size 30557 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc85381ebad8bf9a65afb59dafe09d1edbe968b1 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b425c24ea7dd7306369354effa7edd40ccb3f1e85d3cb76ef0c2f7eba4414c14 +size 47707 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7934640f2d6f17153ef1886fabc4a80a9f913ea9 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57055dffd7d4fb4ca13be85190b0e168329939bfaf5d1a10a4e0a8ecd87296c8 +size 30576 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44e6d0a57289e66a532da2289001d8e3beec6e86 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc9256d86e8f1f8316d7ff562fe12f2f06f6c7652546854ea031e0c5457dfc6a +size 24966 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..556a92d75e0a6833640cd87999696a2def63d976 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb9bf7c1d8cf805aed2a7b5da396d8e38980f2217469c37620f44b82f6b32120 +size 45902 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e90d808a7a4b020ab81d8e1921568a6dd4470e4 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27c2fda8ca1faa111a208303cfdeb3de7d7f0c30baad216576650861e0a8545f +size 44068 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/f10dc32e3673e1392029a49e958a9d6c_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/f10dc32e3673e1392029a49e958a9d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99e4d44b6e117525b98afd1a6bc126b76fdca71e --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/f10dc32e3673e1392029a49e958a9d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8bfb2b42eaf3dde64a54d663b402918a7246f957d24f319e9a322c1df2b8b41 +size 19346 diff --git a/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7345b1996b692911aa1d0ddad97cd5f09cd9a3e3 --- /dev/null +++ b/marked/Q/T-REC-Q.831.1-200002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:375dfed7e4452b143ccabb727df83ea9092bf66b0aaaf692ccf1fe56edc63fa7 +size 22508 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/018fd261187e5e5412b0c34e29beabab_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/018fd261187e5e5412b0c34e29beabab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..848128d910ed4c549c8bcf6084086f756e68d342 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/018fd261187e5e5412b0c34e29beabab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ac082b40bbf4ff329421ac7ea18fb70f088be9b77206a05c0c9c287a9574c4a +size 101360 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/1d62ade6b682fdfb8e192d10a06246a4_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/1d62ade6b682fdfb8e192d10a06246a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c3f8a8bae63234897fce2238bde23a200094eb4 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/1d62ade6b682fdfb8e192d10a06246a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d62ed463fd0f2488baae3a0fa6a763d42b075203e2b8d27e8f60a7f3e89e9a3e +size 71642 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/2690cca56d57ad5978da52f7ad84cafd_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/2690cca56d57ad5978da52f7ad84cafd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e100cd62c0590b11bd7b83bf96c75787bdd2ae9 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/2690cca56d57ad5978da52f7ad84cafd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3edbd9e69b6108bad3ca69cb09d6bc8c0a84fe08857bc90aac499d5a7fce7b77 +size 100393 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-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.834.1-200406-I_PDF-E/37cc5b3a159a6081e5193673fa2996b2_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/37cc5b3a159a6081e5193673fa2996b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c54cdd089118bf4e7836d1f6c1f5d8ed0237d2e6 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/37cc5b3a159a6081e5193673fa2996b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e72ae0d1b38fa4f7854b8f2db939877955add9460a1797e70ae8090592595c9 +size 100602 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34583b846e04f1b367619b02e31caded9c0abad1 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b63c2e669fe6f34857fad4f141d6218ebb71f68d633ed83f0e946b8cebf789e +size 189565 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ae055a1b1c012d05e692086c726945f769c9c07 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7434ace16c4a0901e6a2b0a8cf19cbdf2611c35c564b4c8fdb74447e8b605800 +size 186324 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/52fe5bc3ba967e0e8f56f1a3ab9d9c3e_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/52fe5bc3ba967e0e8f56f1a3ab9d9c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cac0d42c692b6c87ff7a36819def4b73eca7dff9 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/52fe5bc3ba967e0e8f56f1a3ab9d9c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06d548a3601bb9064b1b90ae8e032c62a850efba47ae708a3e72feb8b7d43058 +size 60515 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/67cbb5a621a69ab58534bb3376bbb724_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/67cbb5a621a69ab58534bb3376bbb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..345692b38153965a5e39ba3e55053e65c373862d --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/67cbb5a621a69ab58534bb3376bbb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0bf36582ef258e794ec4825a2597970ab291027db73ddbc65f331a5f90c2d49 +size 119409 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e453eceb134fe65d08eb13042e72e5d4807db42 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32b1ed666b1a0302c2f4215b1e6cc8fb89ce79430dda80b8bf525fef73d658bd +size 137255 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/80a44321a02e8a7d638ac9d53e88772c_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/80a44321a02e8a7d638ac9d53e88772c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ff85d3703874c1a10aa31832c305f2a6f43a178 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/80a44321a02e8a7d638ac9d53e88772c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7f3646bda43264c3f702395dd876fd6f65e4fca495db8d3937ef83286f7885e +size 176445 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19eeed6be29fd5417719e914f3e5fa04886e0993 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ae42610e8b83ee4f2f4735e8a3a8091d6a039b9df2a13e389ad21f835d0d905 +size 53819 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8834bb0ae63244411bb6289c0603f0ebd20e12ba --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76aad1f6d4d9785b638877b4d3ea0cbeaf9ad01e56b9efc32e80ed060cb331c4 +size 150910 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/8942c590307508b28df9c207bad75740_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/8942c590307508b28df9c207bad75740_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f9b0e253c6536d091f0f9be04391bfd92c4920b --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/8942c590307508b28df9c207bad75740_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:931d3567836a2ffa133feb2ee5906c1d6dce666e7f494a80923d13e3a69a2306 +size 45465 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ba1f38907ac6c896934d9290e1d586aac59a203 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f07192696fe2fe26f07f3955a977f04864a058e8f1894decbec0549da7a1f7d3 +size 108840 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d1a2252c9e93e43b28db9d51cbfe0dab4f873c1 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a436d53fd1c1f21188b723b72c4ef24620f9f620b1662da878013adae48c4a81 +size 88435 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/a969a3a831d0967b54efe1400846ed30_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/a969a3a831d0967b54efe1400846ed30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51b5f0de4aac572b743c5490b486c8844bdf46a9 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/a969a3a831d0967b54efe1400846ed30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02d2ca2e672a23b12e56e33d22df691ee62d649a7995a76bbd62b283267a4bc3 +size 38515 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/abc0eb594f9d2c0daa0e60df05f2a666_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/abc0eb594f9d2c0daa0e60df05f2a666_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e320b34c53e682ae5f28e17ed9fea579533fd656 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/abc0eb594f9d2c0daa0e60df05f2a666_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d646001e0ac9820e92cea880d49edb886f8ae949146250ca8a27487df89b3935 +size 57858 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b27617acb57b3e0c7a080137631e908cfcdbfa15 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/be9225da20b1fa284d0ed4b44fd633a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f0f928dc1fffebe544df9fc2088940289ff6645d007d200867491c192017b4e +size 64404 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44df3ed839a15f1b5c6cde68a925752f3228bd8c --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60b617ee59ee14c993f6a457fce788f75e739fcdc9570a586c2807cbe6aed677 +size 97267 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b667bdde36b97c309e164058596e064029367fe8 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:384e79d7fb69e1bfa748f593608824e5d0daa85e3b7328a3184b6fbc11dac536 +size 94385 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/cb9e3603e260c7b07aca73128586df80_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/cb9e3603e260c7b07aca73128586df80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d13b5ddcb278f59fcd0f51c886b17adc0a1a259 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/cb9e3603e260c7b07aca73128586df80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:290d5788f428081ac102a1a3d8c2b30d8de2411bc985fb7f021ef3aed952cf41 +size 32986 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/cf75ef88724c24497dfe437c81b74325_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/cf75ef88724c24497dfe437c81b74325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbee72a85db79b56e1a4a06a396a8e4cb27404a7 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/cf75ef88724c24497dfe437c81b74325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:293ba1f6d7534c50e7e148f75308c598a0c42afae699d12385540ff2b43895fd +size 123157 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d13d29ff2ebef1a20c60c05fc4bca45b_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d13d29ff2ebef1a20c60c05fc4bca45b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..995433d74a3983e619bb6ae6529fd2e4b1ccf5b8 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d13d29ff2ebef1a20c60c05fc4bca45b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab2ca11dafff7dfd4f2ed70b18aa61a33031a796d8942a60664d85f9cc65646c +size 103225 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d24636250101595e660b20830d8c2c64_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d24636250101595e660b20830d8c2c64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf55528ec0501609b9dada4f98ec36153655739d --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d24636250101595e660b20830d8c2c64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a48a3ed57895d0ce3e9f58c33929b7448bb22e07d4aeb7d53b1b021e0e81a51 +size 45806 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d2f4940093768001d427ab18d4e40cf1_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d2f4940093768001d427ab18d4e40cf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e365d5be6ae3cd90e57d9f1b40d00c8dcf4d5f28 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d2f4940093768001d427ab18d4e40cf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3d526633036c1c6f6627207409dbd69363dd595121fa5036ad888beeb88b632 +size 81220 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bbd436d3fe303b8918dbf8672a335d49c32a565 --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3294a2a3fd8d1df1dd7028c5d449034c73d0d00ab3da3cb1d6e5988f521f0cfb +size 101920 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..183e7e02f3556783a56dfde1a9c0be408fd2f89d --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6ba6958de58159c78987f43bb0e4df819024a3e215f405865099753cdac06d0 +size 100039 diff --git a/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ee85061e06c10d16bb9be439312ffed265faefdc --- /dev/null +++ b/marked/Q/T-REC-Q.834.1-200406-I_PDF-E/raw.md @@ -0,0 +1,5836 @@ + + +![ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.834.1 + +(06/2004) + +SERIES Q: SWITCHING AND SIGNALLING + +Q3 interface + +# --- **ATM-PON requirements and managed entities for the network and network element views** + +ITU-T Recommendation Q.834.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 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation Q.834.1** + +# **ATM-PON requirements and managed entities for the network and network element views** + +## **Summary** + +This Recommendation defines the managed entities that are required to support the requirements for the management of a Passive Optical Network (ATM-PON). These definitions are to be used to develop a protocol-neutral information model. A network element view combined with a network view of an ATM-PON is modelled according to a protocol-neutral information modelling concept. The concept provides a protocol-neutral MIB and thus permits developers to derive an implementation-specific MIB from any management protocol. The information model described herein is used on an interface between a Network Management Layer and an Element Management Layer. + +### **Source** + +ITU-T Recommendation Q.834.1 was approved on 13 June 2004 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +### **Keywords** + +APON, BPON. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|--------------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations..... | 3 | +| 5 Conventions ..... | 5 | +| 6 General overview..... | 6 | +| 6.1 Operations architecture..... | 6 | +| 6.2 NE view combined with NW view (Combined view)..... | 6 | +| 7 Requirements ..... | 7 | +| 7.1 Related requirements ..... | 7 | +| 7.2 Fault processing..... | 10 | +| 7.3 Performance monitoring..... | 11 | +| 8 Managed entities..... | 18 | +| 8.1 AAL1PMHistoryDataF ..... | 19 | +| 8.2 AAL1ProfileF ..... | 20 | +| 8.3 AAL2PMHistoryDataF ..... | 21 | +| 8.4 AAL2ProfileF ..... | 22 | +| 8.5 AAL2PVCProfileF ..... | 22 | +| 8.6 AAL5PMHistoryDataF ..... | 23 | +| 8.7 AAL5ProfileF ..... | 24 | +| 8.8 accessGroupF ..... | 24 | +| 8.9 adslCTPF ..... | 25 | +| 8.10 adslLayerNetworkDomainF ..... | 25 | +| 8.11 adslLinkConnectionF ..... | 25 | +| 8.12 adslSubnetworkF ..... | 25 | +| 8.13 adslTopologicalLinkEndF ..... | 26 | +| 8.14 adslTopologicalLinkF..... | 26 | +| 8.15 adslTrailF..... | 26 | +| 8.16 adslTTPF ..... | 26 | +| 8.17 alarmLogRecordF ..... | 26 | +| 8.18 alarmSeverityAssignmentProfileF ..... | 27 | +| 8.19 APONCTP..... | 27 | +| 8.20 APONLayerNetworkDomain ..... | 28 | +| 8.21 APONLink..... | 28 | +| 8.22 APONLinkConnection ..... | 28 | +| 8.23 APONLogicalLinkEnd ..... | 28 | +| 8.24 APONSubnetwork ..... | 28 | +| 8.25 APONTrail ..... | 29 | + +| | Page | +|------------------------------------------|-------------| +| 8.26 APONPhysicalPortResource ..... | 29 | +| 8.27 APONPMHistoryData ..... | 30 | +| 8.28 APONTTP ..... | 30 | +| 8.29 ATMCrossConnectionF ..... | 30 | +| 8.30 ATMCrossConnectionControlF ..... | 31 | +| 8.31 ATMNetworkAccessProfileF ..... | 31 | +| 8.32 ATMPhysicalPortResource ..... | 32 | +| 8.33 ATMTrafficLoadHistoryDataF ..... | 33 | +| 8.34 attributeValueChangeRecordF ..... | 33 | +| 8.35 au3CTPF ..... | 34 | +| 8.36 au4CTPF ..... | 34 | +| 8.37 BridgedLANLayerNetworkDomainF ..... | 34 | +| 8.38 BridgedLANServiceProfileF ..... | 35 | +| 8.39 BridgedLANSubnetworkF ..... | 35 | +| 8.40 BICIF ..... | 35 | +| 8.41 BISSIF ..... | 36 | +| 8.42 cellBasedCTPF ..... | 36 | +| 8.43 cellBasedTTPF ..... | 36 | +| 8.44 CESServiceProfileF ..... | 37 | +| 8.45 CTPF ..... | 37 | +| 8.46 DS1CTPF ..... | 38 | +| 8.47 DS1LayerNetworkDomainF ..... | 38 | +| 8.48 DS1PMHistoryDataF ..... | 38 | +| 8.49 DS1SubnetworkConnectionF ..... | 40 | +| 8.50 DS1SubnetworkF ..... | 40 | +| 8.51 DS1TTPF ..... | 40 | +| 8.52 DS3CTPF ..... | 40 | +| 8.53 DS3LayerNetworkDomainF ..... | 40 | +| 8.54 DS3PhysicalPortResource ..... | 40 | +| 8.55 DS3PMHistoryDataF ..... | 41 | +| 8.56 DS3SubnetworkF ..... | 42 | +| 8.57 DS3SubnetworkConnectionF ..... | 42 | +| 8.58 DS3TTPF ..... | 42 | +| 8.59 E1CTPF ..... | 42 | +| 8.60 E1LayerNetworkDomainF ..... | 42 | +| 8.61 E1PMHistoryDataF ..... | 43 | +| 8.62 E1SubnetworkConnectionF ..... | 43 | +| 8.63 E1SubnetworkF ..... | 43 | +| 8.64 E1TTPF ..... | 44 | +| 8.65 E3CTPF ..... | 44 | + +| | Page | +|--------------------------------------------|-------------| +| 8.66 E3LayerNetworkDomainF ..... | 44 | +| 8.67 E3PMHistoryDataF ..... | 44 | +| 8.68 E3SubnetworkConnectionF ..... | 45 | +| 8.69 E3SubnetworkF ..... | 45 | +| 8.70 E3TTPF ..... | 45 | +| 8.71 EquipmentHolderF ..... | 45 | +| 8.72 EthernetCTPF ..... | 46 | +| 8.73 EthernetPhysicalPortResource ..... | 46 | +| 8.74 EthernetPMHistoryDataF ..... | 47 | +| 8.75 EthernetProfileF ..... | 48 | +| 8.76 EthernetTTPF ..... | 49 | +| 8.77 filterProfileF ..... | 49 | +| 8.78 LESServiceProfileF ..... | 49 | +| 8.79 layerNetworkDomainF ..... | 50 | +| 8.80 linkConnectionF ..... | 50 | +| 8.81 logF ..... | 51 | +| 8.82 logicalLinkEndF ..... | 52 | +| 8.83 logicalLinkF ..... | 52 | +| 8.84 logicalMTPLinkF ..... | 53 | +| 8.85 MACBridgeConfigurationDataF ..... | 53 | +| 8.86 MACBridgeF ..... | 54 | +| 8.87 MACBridgePMHistoryDataF ..... | 54 | +| 8.88 MACBridgePortF ..... | 55 | +| 8.89 MACBridgePortPMHistoryDataF ..... | 56 | +| 8.90 MACBridgeServiceProfileF ..... | 56 | +| 8.91 managedEntityCreationLogRecordF ..... | 57 | +| 8.92 managedEntityDeletionLogRecordF ..... | 57 | +| 8.93 MLTTestResultsF ..... | 58 | +| 8.94 msCTPF ..... | 59 | +| 8.95 msTTPF ..... | 59 | +| 8.96 NEFSAN ..... | 59 | +| 8.97 networkF ..... | 60 | +| 8.98 NT ..... | 61 | +| 8.99 OLT ..... | 61 | +| 8.100 OLTResource ..... | 61 | +| 8.101 ONT ..... | 61 | +| 8.102 ONU ..... | 62 | +| 8.103 PhysicalPathTPF ..... | 62 | +| 8.104 PhysicalPONPortF ..... | 63 | +| 8.105 PhysicalPortF ..... | 63 | + +| | Page | +|-------------------------------------------------------|-------------| +| 8.106 pluginUnitF ..... | 64 | +| 8.107 PriorityQueue ..... | 65 | +| 8.108 rsCTPF ..... | 66 | +| 8.109 rsTTPF ..... | 66 | +| 8.110 SSCSPParameterProfile1F ..... | 66 | +| 8.111 SSCSPParameterProfile2F ..... | 67 | +| 8.112 softwareF ..... | 68 | +| 8.113 SONETSDHLinePMHistoryData ..... | 68 | +| 8.114 SONETSDHPhysicalPortResource ..... | 69 | +| 8.115 SONETSDHSectionAdaptationPMHistoryData ..... | 70 | +| 8.116 SONETSDHSectionPathPMHistoryData ..... | 70 | +| 8.117 subnetworkConnectionF ..... | 72 | +| 8.118 subnetworkF ..... | 72 | +| 8.119 TCAdaptorDbFairnessPMHistoryData ..... | 73 | +| 8.120 tcAdaptorTTPF ..... | 74 | +| 8.121 TCAdaptionProtocolMonitoringPMHistoryData ..... | 75 | +| 8.122 T-CONT ..... | 75 | +| 8.123 TCONTbuffer ..... | 76 | +| 8.124 TCONTbufferPMHistoryData ..... | 76 | +| 8.125 thresholdDataF ..... | 77 | +| 8.126 topologicalLinkEndF ..... | 77 | +| 8.127 topologicalLinkF ..... | 77 | +| 8.128 trafficDescriptorProfileF ..... | 78 | +| 8.129 TrafficScheduler ..... | 79 | +| 8.130 trailF ..... | 80 | +| 8.131 TTPF ..... | 80 | +| 8.132 uniInfoF ..... | 81 | +| 8.133 upcNpcDisagreementPMHistoryDataF ..... | 82 | +| 8.134 vc3TTPF ..... | 83 | +| 8.135 vc4TTPF ..... | 83 | +| 8.136 vcCTPF ..... | 84 | +| 8.137 vcLayerNetworkDomainF ..... | 85 | +| 8.138 vcLinkConnectionF ..... | 85 | +| 8.139 vcLogicalLinkF ..... | 85 | +| 8.140 vcSubnetworkConnectionF ..... | 86 | +| 8.141 vcSubnetworkF ..... | 86 | +| 8.142 vcTopologicalLinkEndF ..... | 86 | +| 8.143 vcTopologicalLinkF ..... | 87 | +| 8.144 vcTrailF ..... | 87 | +| 8.145 vcTTPF ..... | 87 | + +| | Page | +|------------------------------------------------------------|-------------| +| 8.146 vdslCTPF ..... | 88 | +| 8.147 vdslLayerNetworkDomainF ..... | 88 | +| 8.148 vdslLinkConnectionF ..... | 88 | +| 8.149 vdslSubnetworkF ..... | 88 | +| 8.150 vdslTopologicalLinkEndF ..... | 88 | +| 8.151 vdslTopologicalLinkF ..... | 89 | +| 8.152 vdslTrailF ..... | 89 | +| 8.153 vdslTTPF ..... | 89 | +| 8.154 voiceCTPF ..... | 89 | +| 8.155 voiceLayerNetworkDomainF ..... | 90 | +| 8.156 voicePMHistoryDataF ..... | 90 | +| 8.157 voiceServiceProfileAAL1F ..... | 91 | +| 8.158 voiceServiceProfileAAL2F ..... | 91 | +| 8.159 voiceSubnetworkConnectionF ..... | 91 | +| 8.160 voiceSubnetworkF ..... | 92 | +| 8.161 voiceTTPF ..... | 92 | +| 8.162 vpCTPF ..... | 92 | +| 8.163 vpLayerNetworkDomainF ..... | 93 | +| 8.164 vpLinkConnectionF ..... | 93 | +| 8.165 vpLogicalLinkF ..... | 94 | +| 8.166 vpSubnetworkConnectionF ..... | 94 | +| 8.167 vpSubnetworkF ..... | 94 | +| 8.168 vpTopologicalLinkEndF ..... | 94 | +| 8.169 vpTopologicalLinkF ..... | 95 | +| 8.170 vpTrailF ..... | 95 | +| 8.171 vpTTPF ..... | 95 | +| 8.172 vpvPMHistoryDataF ..... | 96 | +| Annex A – Tables of possible faults ..... | 98 | +| A.1 DCN alarms for the FSN element management system ..... | 98 | +| A.2 Equipment alarms ..... | 99 | +| A.3 Quality of Service alarms ..... | 109 | +| Annex B – Communication network ..... | 112 | +| Annex C – Entity relationship diagram ..... | 114 | +| C.1 Inventory management ..... | 115 | +| C.2 Termination points ..... | 116 | +| C.3 AAL ..... | 117 | +| C.4 Physical performance monitor ..... | 118 | +| C.5 TCAdaptor E-R diagram ..... | 119 | +| C.6 ATM cross-connection E-R diagram ..... | 120 | + +| | Page | +|----------------------------------------------------------------------|-------------| +| C.7 Traffic characterization E-R diagram..... | 121 | +| C.8 Log..... | 122 | +| C.9 ATM traffic load..... | 123 | +| C.10 Combined view managed entities..... | 124 | +| C.11 Layer network domain and subnetwork ..... | 125 | +| C.12 Link connection ..... | 126 | +| C.13 Subnetwork connection ..... | 126 | +| Appendix I – FSAN operations requirements..... | 127 | +| I.1 Introduction ..... | 127 | +| I.2 Processes..... | 127 | +| I.3 Management architecture ..... | 134 | +| I.4 Management requirements ..... | 138 | +| I.5 Data communications network..... | 147 | +| I.6 Element management platform..... | 147 | +| I.7 Fault and performance management of the transmission medium..... | 149 | +| I.8 References ..... | 151 | +| Appendix II – Tables of managed entities ..... | 152 | +| II.1 NE view ..... | 152 | +| II.2 Network view ..... | 155 | + +# ITU-T Recommendation Q.834.1 + +# ATM-PON requirements and managed entities for the network and network element views + +## 1 Scope + +This Recommendation specifies an information of ATM-PON system at a Q interface at a reference point beyond an element management layer (ITU-T Rec. M.3013). This Q interface is defined as the network and network element views. + +This Recommendation provides network as well as network element view managed entities to support a protocol-neutral information model for ATM-PON. As a consequence, the managed entities and their properties will be used to develop a protocol-neutral information model. The model may then be used to develop specific MIBs, which are appropriate for the management protocols. These managed entities are specific to the ATM-PON system. Therefore, the suffix "F" is added to their names in order to distinguish them from generic managed entities. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [2] ITU-T Recommendation M.3013 (2000), *Considerations for a telecommunications management network*. +- [3] ITU-T Recommendation G.709/Y.1331 (2003), *Interfaces for the Optical Transport Network (OTN)*. +- [4] ITU-T Recommendation G.774 (2001), *Synchronous digital hierarchy (SDH) – Management information model for the network element view*. +- [5] ITU-T Recommendation G.902 (1995), *Framework Recommendation on functional access networks (AN) – Architecture and functions, access types, management and service mode aspects*. +- [6] ITU-T Recommendation G.982 (1996), *Optical access networks to support services up to the ISDN primary rate or equivalent bit rates*. +- [7] ITU-T Recommendation G.983.1 (1998), *Broadband optical access systems based on Passive Optical Networks (PON), plus Amendment 1 (2001) and Corrigendum 1 (1999)*. +- [8] ITU-T Recommendation G.983.2 (2002), *ONT management and control interface specification for B-PON, plus Amendment 1 (2003)*. +- [9] ITU-T Recommendation G.983.3 (2001), *A broadband optical access system with increased service capability by wavelength allocation, plus Amendment 1 (2002)*. +- [10] ITU-T Recommendation G.983.4 (2001), *A broadband optical access system with increased service capability using dynamic bandwidth assignment*. + +- [11] ITU-T Recommendation G.852.2 (1999), *Enterprise viewpoint description of transport network resource model*. +- [12] ITU-T Recommendation G.992.1 (1999), *Asymmetrical digital subscriber line (ADSL) transceivers*. +- [13] ITU-T Recommendation G.992.2 (1999), *Splitterless asymmetric digital subscriber line (ADSL) transceivers*. +- [14] ITU-T Recommendation I.321 (1991), *B-ISDN protocol reference model and its application*. +- [15] ITU-T Recommendation I.326 (2003), *Functional architecture of transport networks based on ATM*. +- [16] ITU-T Recommendation I.366.1 (1998), *Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2*. +- [17] ITU-T Recommendation I.366.2 (2000), *AAL type 2 service specific convergence sublayer for narrow-band services*. +- [18] ITU-T Recommendation I.432.2 (1999), *B-ISDN user-network interface – Physical layer specification: 155 520 kbit/s and 622 080 kbit/s operation*. +- [19] ITU-T Recommendation X.731 (1992) | ISO/IEC 10164-2:1993, *Information technology – Open Systems Interconnection – Systems Management: State management function*. +- [20] ATM Forum AF-NM-0020.001 (1998), *M4 Interface Requirements and Logical MIB: ATM Network Element View*. +- [21] IETF RFC 1483 (1993), *Multiprotocol Encapsulation over ATM Adaptation Layer 5*. +- [22] ANSI T1.413 (1998), *Network to Customer Installation Interfaces – Asymmetric Digital Subscriber Line (ADSL) Metallic Interface*. +- [23] IEEE 802.1D, *Standard for Local and Metropolitan Area Networks: Media Access Control (MAC) Bridges*. + +## 3 Definitions + +This Recommendation uses the following terms that are already defined in ITU-T Recs G.982 and G.983.1: + +**3.1 optical access network (OAN):** The set of access links sharing the same network-side interfaces and supported by optical access transmission systems. The OAN may include a number of ODNs connected to the same OLT. + +**3.2 optical distribution network (ODN):** An ODN provides the optical transmission means from the OLT towards the users, and vice versa. It utilizes passive optical components. + +**3.3 optical line terminal (OLT):** An OLT provides the network-side interface of the OAN, and is connected to one or more ODNs. + +**3.4 optical network terminal (ONT):** An ONU used for FTTH and includes the User Port function. + +**3.5 optical network unit (ONU):** An ONU provides (directly or remotely) the user-side interface of the OAN, and is connected to the ODN. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|--------------------------------------------| +| AAL | ATM Adaptation Layer | +| ABR | Available Bit Rate | +| ADSL | Asymmetrical Digital Subscriber Line | +| AIS | Alarm Indication Signal | +| AN | Access Network | +| APON | ATM-PON | +| ATM | Asynchronous Transfer Mode | +| BBE | Background Block Error | +| BES | Bursty Errored Seconds | +| BICI | Broadband Inter-Carrier Interface | +| BISSI | Broadband Inter-Switching System Interface | +| CBR | Constant Bit Rate | +| CCS | Common Channel Signalling | +| CES | Circuit Emulation Service | +| CID | Channel ID | +| CLP | Cell Loss Priority | +| CMIP | Common Management Information Protocol | +| CORBA | Common Object Request Broker Architecture | +| CPS | Common Part Sublayer | +| CRC | Cyclic Redundancy Check | +| CS | Convergence Sublayer | +| CTP | Connection Termination Point | +| DCE | Data-Circuit terminating Equipment | +| DCN | Data Communications Network | +| DSx | Digital Signal Level x | +| DTE | Data Terminating Equipment | +| ELCP | Emulated Loop Control Protocol | +| EM | Element Management | +| EML | Element Management Layer | +| EMS | Element Management System | +| ES | Errored Second | +| ESF | Extended Super Frame | +| FSAN | Full Service Access Network | +| GFR | Guaranteed Frame Rate | +| HEC | Header Error Control | + +| | | +|---------|------------------------------------------------------| +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| ITU | International Telecommunication Union | +| LES-EOC | Loop Emulation Service – Embedded Operations Channel | +| LIM | Line Interface Module | +| LOF | Loss Of Frame | +| LOS | Loss Of Signal | +| ME | Managed Entity | +| MIB | Management Information Base | +| MTP | Multipoint Termination Point | +| NE | Network Element | +| NEL | Network Element Layer | +| NM | Network Management | +| NML | Network Management Layer | +| NMS | Network Management System | +| NPC | Network Parameter Control | +| NT | Network Termination | +| NW | Network | +| OAM | Operations, Administration and Maintenance | +| OAN | Optical Access Network | +| ODN | Optical Distribution Network | +| OFS | Out-of-Frame Second | +| OLT | Optical Line Terminal | +| OMCI | ONT Management and Control Interface | +| ONT | Optical Network Terminal | +| ONU | Optical Network Unit | +| OOF | Out-Of-Frame | +| OSF | Operations System Function | +| PDU | Protocol Data Unit | +| PM | Performance Management | +| PON | Passive Optical Network | +| POTS | Plain Old Telephone Service | +| PVC | Permanent Virtual Circuit | +| QoS | Quality of Service | +| RDI | Remote Defect Indication | +| RFI | Remote Failure Indication | +| SAR | Segmentation And Reassembly | + +| | | +|------|-----------------------------------------| +| SCP | Service Capability and Performance | +| SD | Signal Degraded | +| SDH | Synchronous Digital Hierarchy | +| SDP | Severely Disturbed Period | +| SDU | Service Data Unit | +| SES | Severely Errored Second | +| SM | Service Management | +| SML | Service Management Layer | +| SN | Service Node | +| SNC | SubNetwork Connection | +| SNI | Service Node Interface | +| SNMP | Simple Network Management Protocol | +| SRTS | Synchronous Residual Time Stamp | +| STD | Structured Data | +| STF | Start Field | +| SVC | Switched Virtual Channel | +| TMN | Telecommunication Management Network | +| TP | Termination Point | +| TTP | Trail Termination Point | +| UAS | UnAvailable Second | +| UBR | Unspecified Bit Rate | +| UNI | User-Network Interface | +| UPC | Usage Parameter Control | +| UUI | User-to-User Indication | +| VBR | Variable Bit Rate | +| VC | Virtual Channel | +| VCC | Virtual Channel Connection | +| VCI | Virtual Channel Identifier | +| VDSL | Very high speed Digital Subscriber Line | +| VP | Virtual Path | +| VPC | Virtual Path Connection | +| VPI | Virtual Path Identifier | + +## **5 Conventions** + +None. + +## 6 General overview + +### 6.1 Operations architecture + +This Recommendation addresses the management functions of FSAN network elements across the Q interface. + +The operation systems manage FSAN network elements and their interface ports through the Q interface by means of managing OLT. FSAN network elements include OLT, ODN, ONU, NT and ONT (ITU-T Rec. G.983.1) shown in Figure 1. The ODN offers one or more optical paths between one OLT and one or more ONU/ONTs. ONU and NT are connected by ADSL or VDSL. OLT has a BICI/BISSI port towards the core network, and ONT/NT has one or more UNI port(s) for the customers. The OLT manages ONU, NT and ONT (ITU-T Rec. G.983.2). + +The FSAN Element Management System (FSAN EMS) consists of E-OSF and includes a little N-OSF and S-OSF (ITU-T Recs M.3010 and M.3013) and manages all the FSAN network elements shown in Figure 1. The Q interface specifies a network element view combined with a network view. This interface is called IF1 in the FSAN operations requirements in Appendix I. + +![Figure 1/Q.834.1 – FSAN network elements and target interface of operations architecture. The diagram shows a three-layer architecture. The top layer is the 'Network management layer' containing the 'FSAN network management system'. The middle layer is the 'Element management layer' containing the 'FSAN element management system (E-OSF, N-OSF and S-OSF)'. These two layers are connected by a thick line labeled 'Q'. The bottom layer is the 'Network element layer', which contains a dashed box labeled 'FSAN network elements'. Inside this box, the components are connected in a sequence: BICI/BISSI (represented by a vertical bar) connects to OLT (represented by a rectangle), which connects to ODN (represented by an oval), which then connects to a stack of ONU and NT (represented by rectangles), and finally to a stack of ONT (represented by rectangles). The ONT stack connects to UNI (represented by a vertical bar). A line from the 'FSAN element management system' box points to the OLT box. Another line from the 'FSAN element management system' box points to the ODN oval. A third line from the 'FSAN element management system' box points to the ONT stack. The label 'Q.834.1_F1' is at the bottom right.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +Q.834.1\_F1 + +Figure 1/Q.834.1 – FSAN network elements and target interface of operations architecture. The diagram shows a three-layer architecture. The top layer is the 'Network management layer' containing the 'FSAN network management system'. The middle layer is the 'Element management layer' containing the 'FSAN element management system (E-OSF, N-OSF and S-OSF)'. These two layers are connected by a thick line labeled 'Q'. The bottom layer is the 'Network element layer', which contains a dashed box labeled 'FSAN network elements'. Inside this box, the components are connected in a sequence: BICI/BISSI (represented by a vertical bar) connects to OLT (represented by a rectangle), which connects to ODN (represented by an oval), which then connects to a stack of ONU and NT (represented by rectangles), and finally to a stack of ONT (represented by rectangles). The ONT stack connects to UNI (represented by a vertical bar). A line from the 'FSAN element management system' box points to the OLT box. Another line from the 'FSAN element management system' box points to the ODN oval. A third line from the 'FSAN element management system' box points to the ONT stack. The label 'Q.834.1\_F1' is at the bottom right. + +**Figure 1/Q.834.1 – FSAN network elements and target interface of operations architecture** + +### 6.2 NE view combined with NW view (Combined view) + +This Recommendation adopts a combined view defined as the network element (NE) view combined with the network (NW) view in order to treat both FSAN network element and FSAN subnetwork. + +## **7 Requirements** + +The general requirements for the ATM-PON operation system are described in FSAN operations requirements in Appendix I. This Recommendation uses some of them and derives fault processing from fault management requirements and performance monitoring from performance management requirements. + +### **7.1 Related requirements** + +The number and letter written after the requirements refer to an associated item in Appendix I, FSAN operations requirements. + +#### **7.1.1 Configuration management** + +For equipment installation, automatic detection shall include the following sequence of activities: installation, power-up self test, equipment authentication, read inventory information, report installation to the FSAN EMS, and download of configuration information. Inventory information shall be read and sent to the FSAN EMS, where possible, regardless of whether the equipment is of the correct type. (38 M) + +The FSAN element management system shall be able to create the logical representations of the resources required to manage the network and services. All necessary network and service parameters shall be supplied in the appropriate request. (77 M) + +It shall be possible to create the logical resources in the FSAN element management system without the need for equipment to be physically present in the network. (79 M) + +The FSAN element management system shall automatically allocate the required resources if they are not identified in the provision request. (82 M) + +If all spare and installed resources are in use, the FSAN element management system shall use the next available spare and not the installed resources. (83 M) + +If there are no spare resources awaiting installation, then the FSAN element management system shall propose a list of equipment that need to be installed to allow the request to be fulfilled. The equipment list shall indicate: + +- the type of equipment to be installed; +- the location where it is to be installed (rack/shelf/slot, OLT or ONU, etc.); +- the software and hardware versions that are compatible with the existing version of installed hardware. (84 M) + +Each equipment list shall be stored in the FSAN element management system until an event is received from the NE to indicate that the network equipment has been physically installed and has been correctly authenticated. (85 M) + +It shall be possible to pre-configure equipment prior to its installation by providing the required data when the logical representation is created. (86 M) + +It shall be possible to modify service parameters (such as bit rate, service type, error checking as applicable) for individual UNI(s) or virtual paths (VPs). (87 M) + +The NMS shall be able to create logical resources and paths for end-to-end network and service provision. All necessary parameters shall be supplied in the appropriate request. (121 M) + +It shall be possible to create the logical resources in the NMS without the need for the FSAN element management system to be present. (123 M) + +The NMS user shall receive an indication on the success or failure of all operations. (127 M) + +#### 7.1.2 Fault management + +Fault management refers to the broad set of functions associated with the detection, isolation, reporting and correction of abnormal operational conditions in the network. In this context, fault management consists of the following: + +- alarm surveillance (detecting/receiving events); +- event processing (correlation and filtering); +- fault localization; +- event logging; +- testing. (24 M) + +Network equipment is required to automatically perform a self test (where applicable) when connected to the network. Completion of the self test should leave the network equipment in a known state. An event shall be sent to the FSAN EMS to indicate failure of the self test. (50 M) + +It shall be possible to perform service-specific tests associated with the transport medium between the ONU and NT, where the ONU and NT are separate. The test functions, where possible, should also be able to determine if the customer's equipment is present or absent. Any faults detected during testing shall be reported to the FSAN EMS. (55 M) + +It shall be possible to accurately distinguish between faults on the ODN and faults on the ONU possibly through the use of internal event correlation and test functions. (57 M) + +Detection of a fault, through network surveillance or network testing, which is affecting service shall cause the related equipment to be placed in an unavailable state for provisioning purposes. (100 M) + +It shall be possible to block and unblock resources that provide service to allow equipment to be maintained. Whilst a resource is blocked for maintenance purposes, it shall not be possible to use the service supported by that resource. The event report shall use the format described in ITU-T Rec. X.733. (101 M) + +The FSAN EMS shall be capable of reporting the following categories of faults to the NMS: + +- faults on the network equipment; +- faults on interfaces; +- environmental conditions within the network element where applicable. (102 M) + +Fault reports shall accurately indicate the cause, severity, time and location of conditions detected by the network down to specific replaceable equipment. (103 M) + +It shall be possible to invoke self tests on specific network equipment from the FSAN EMS. (106 M) + +It shall be possible to verify the correct configuration of a service by requesting a connection test from the FSAN EMS to the NE. (107 O) + +Where there is an occurrence of a large number of faults, the FSAN EMS shall analyse and correlate the faults within its domain to determine the underlying cause of the problem. This should result in the escalation of one fault report with an appropriate repair action to a user or NMS. (108 M) + +It shall be possible to set and modify service-specific failure thresholds. A fault shall be reported to the specified users or NMS when a threshold is exceeded. (109 M) + +All fault reports shall be logged. (111 M) + +The FSAN EMS shall accept and act on requests to permit/inhibit fault reports from the NMS. (112 M) + +It shall be possible to apply test loops to the NE manually on a demand basis during fault diagnosis or automatically as part of background test routines to aid proactive fault location. It shall be possible to activate/deactivate a bit error rate test source in the NE to check for errors on the path between the loops. (113 M) + +It shall be possible for an NM-OSF to permit/inhibit fault reports to/from an FSAN EMS. (133 M) + +#### **7.1.3 Performance management** + +Once installed, the network equipment shall be monitored to provide information on network performance and service performance. Measurements shall be based on monitoring network or service parameters. An event shall be sent to the FSAN EMS when the monitoring function detects that a threshold for a parameter has been exceeded. Monitoring shall not affect customer traffic. (62 M) + +It shall be possible to activate and de-activate scheduled reporting of current and historical performance data of the network from the FSAN EMS. The parameters used for monitoring shall be configured with network defaults and shall be modifiable where applicable. It shall not be possible to modify any parameters once all monitoring criteria are set and monitoring has been activated without first de-activating. (65 M) + +When a monitoring function is activated, it shall be possible to specify a time period over which performance information is to be recorded. The time period shall be configurable. (66 M) + +The NE shall suppress all monitoring intervals that have zero counts within any scheduled report that is sent to the FSAN EMS. (68 M) + +Performance monitoring shall involve gathering current and historical statistical data relating to 15-minute intervals over a 24-hour period for the purpose of monitoring and correcting the behaviour and effectiveness of the network. This information should also assist network analysis, network planning, capacity management and billing processes. (69 O) + +It shall be possible to activate and de-activate the performance monitoring functions from the FSAN EMS. When a monitoring function is activated, it shall be possible to specify a time period over which performance information is to be recorded. The time period shall be configurable. (115 M) + +Certain performance monitoring data shall be collected automatically to support the generation of Quality of Service (QoS) information. The management system shall provide QoS information for each of the ATM Constant Bit Rate (CBR), Variable Bit Rate (VBR) and Available Bit Rate (ABR) class of service supported by the network. This information shall include cells discarded, CLP=0 cells discarded, cells successfully passed and CLP=0 cells successfully passed. (116 M) + +The EM-OSF shall provide performance data on demand via the user interface or shall generate performance reports periodically as reports according to a pre-established schedule. (118 M) + +#### **7.1.4 NW view management** + +The FSAN element management system shall be able to create the logical representations of the resources required to manage the network and services. All necessary network and service parameters shall be supplied in the appropriate request. (77 M) + +It shall be possible to create the logical resources in the FSAN element management system without the need for equipment to be physically present in the network. (79 M) + +The FSAN element management system shall automatically allocate the required resources if they are not identified in the provision request. (82 M) + +If all spare and installed resources are in use, the FSAN element management system shall use the next available spare and not the installed resources. (83 M) + +If there are no spare resources awaiting installation, then the FSAN element management system shall propose a list of the equipment that needs to be installed to allow the request to be fulfilled. The equipment list shall indicate: + +- the type of equipment to be installed; +- the location where it is to be installed (rack/shelf/slot, OLT or ONU, etc.); +- the software and hardware versions which are compatible with the existing version of installed hardware. (84 M) + +Each equipment list shall be stored in the FSAN element management system until an event is received from the NE to indicate that the network equipment has been physically installed and has been correctly authenticated. (85 M) + +It shall be possible to pre-configure equipment prior to its installation by providing the required data when the logical representation is created. (86 M) + +It shall be possible to modify service parameters (such as bit rate, service type, error checking as applicable) for individual UNI(s) or Virtual Paths (VPs) when the relevant resources are out of active use. (87 M) + +The NMS shall be able to create logical resources and paths for end-to-end network and service provision. All necessary parameters shall be supplied in the appropriate request. (121 M) + +It shall be possible to create the logical resources in the NMS without the need for the FSAN element management system to be present. (123 M) + +The NMS shall receive an indication on the success or failure of all operations from FSAN element management system. (127 M) + +#### **7.1.5 Others** + +It shall be possible to archive logs periodically using back-up mechanisms. Archiving shall not affect current logs. (34 M) + +The Data Communications Network (DCN) that conveys the management information between the operations functions is a key component of the management architecture. (137 I) + +### **7.2 Fault processing** + +Figure 2 shows the basic sequence of operations that are executed during fault processing. + +- Anomaly processing deals with the detection of faults or abnormal conditions and generating the corresponding fault notification. +- Filtering is used to filter a fault notification depending on the type and cause of the failure. +- Persistency processing allows the network element to hold a notification for a certain time or to forward a notification if a configurable number of fault occurrences or abnormal conditions have taken place in a specified time window. Thus, transient and toggling defects can be filtered. Therefore, timers are required which can be modified at installation time only. Persistency processing uses a persistency profile. +- Assign severity is used to assign a predefined severity to an alarm. Severity assignment is to be supported for each alarm. The assign severity profile includes the classification of alarms. +- Correlation of alarm is used to allow the FSAN EMS to report only the root cause of the event. + +- Notification generates the alarm format that will be logged and/or forwarded to other network management system functions. + +![Figure 2/Q.834.1 – Fault processing sequence diagram. The diagram shows a flow from 'Anomaly processing' at the 'Network element level' through 'Filtering', 'Persistency processing', 'Assign severity', 'Correlation', and 'Notification' to 'Logging' and 'Forward event' at the 'Network management system level'. Arrows indicate the flow between these steps.](812e188283162af0b54fb3e30ffee51b_img.jpg) + +``` + +graph TD + subgraph "Network element level" + AP[Anomaly processing] --> F[Filtering] + end + subgraph "Network management system level1" + F --> PP[Persistency processing] + PP --> AS[Assign severity] + AS --> C[Correlation] + C --> N[Notification] + N --> L[Logging] + N --> FE[Forward event] + L --> Out1[ ] + FE --> Out2[ ] + end + style Out1 fill:none,stroke:none + style Out2 fill:none,stroke:none + +``` + +G.834.1\_F2 + +Figure 2/Q.834.1 – Fault processing sequence diagram. The diagram shows a flow from 'Anomaly processing' at the 'Network element level' through 'Filtering', 'Persistency processing', 'Assign severity', 'Correlation', and 'Notification' to 'Logging' and 'Forward event' at the 'Network management system level'. Arrows indicate the flow between these steps. + +1 This does not imply that any implementation part of the network management functionality may not be realized within the network element. + +**Figure 2/Q.834.1 – Fault processing sequence** + +### 7.3 Performance monitoring + +Performance monitoring is described based on the network layer structure shown in Annex B. + +The OLT will always stay in a 1:N relationship to ONU or ONT, and the ONU will always have a 1:1 relationship to the NT. The ONT/NT side ends with either a ATM 25 Mbit/s or an IP interface or a Leased Line interface. The different possible layers of performance monitoring are shown in Figures 3, 4 and 5. + +![Diagram showing VP monitoring architecture for Figure 3/Q.834.1. It includes OLT, ONU, and NT/ONT blocks with various layers like SDH, PON, xDSL, and ATM Adapt. Layer.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +**VP monitoring** + +The diagram illustrates the architecture for performance monitoring on the VP Layer. It shows the connection between the OLT (Optical Line Terminal), ONU (Optical Network Unit), and the NT (Network Terminal) or ONT (Optical Network Terminal). + +**OLT (Optical Line Terminal):** Contains SDH PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. + +**ONU (Optical Network Unit):** Contains PON PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. + +**NT (Network Terminal):** Contains xDSL PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. The VC-Layer and VP-Layer are connected to the ATM Adapt. Layer, which is further connected to the ATM UNI (User-Network Interface). + +**ONT (Optical Network Terminal):** Contains PON PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. The VC-Layer and VP-Layer are connected to the ATM Adapt. Layer, which is further connected to the ATM UNI. + +The connections are as follows: OLT to ONU (1:N), ONU to NT (1:1), and OLT to ONT (1:N). + +G.834.1\_F3 + +Diagram showing VP monitoring architecture for Figure 3/Q.834.1. It includes OLT, ONU, and NT/ONT blocks with various layers like SDH, PON, xDSL, and ATM Adapt. Layer. + +Figure 3/Q.834.1 – Performance monitoring on VP Layer + +![Diagram showing VC monitoring architecture for Figure 4/Q.834.1. It includes OLT, ONU, and NT/ONT blocks with various layers like SDH, PON, xDSL, and ATM Adapt. Layer.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +**VC monitoring** + +The diagram illustrates the architecture for performance monitoring on the VC Layer. It shows the connection between the OLT (Optical Line Terminal), ONU (Optical Network Unit), and the NT (Network Terminal) or ONT (Optical Network Terminal). + +**OLT (Optical Line Terminal):** Contains SDH PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. + +**ONU (Optical Network Unit):** Contains PON PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. + +**NT (Network Terminal):** Contains xDSL PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. The VC-Layer and VP-Layer are connected to the ATM Adapt. Layer, which is further connected to the ATM UNI. + +**ONT (Optical Network Terminal):** Contains PON PL-TP, VC-Layer, VP-Layer, and TC-Adaptor. The VC-Layer and VP-Layer are connected to the ATM Adapt. Layer, which is further connected to the ATM UNI. + +The connections are as follows: OLT to ONU (1:N), ONU to NT (1:1), and OLT to ONT (1:N). + +G.834.1\_F4 + +Diagram showing VC monitoring architecture for Figure 4/Q.834.1. It includes OLT, ONU, and NT/ONT blocks with various layers like SDH, PON, xDSL, and ATM Adapt. Layer. + +Figure 4/Q.834.1 – Performance monitoring on VC Layer + +![Diagram showing AAL monitoring architecture for two scenarios: xDSL and PON. The top scenario shows an OLT connected to an ONU (1:N) which is then connected to an NT (1:1). The bottom scenario shows an OLT connected to an ONT (1:N). Both scenarios show the internal layer structure of the OLT, ONU/ONT, and the network termination/terminal equipment.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +**AAL monitoring** + +The diagram illustrates the AAL monitoring architecture for two scenarios: xDSL and PON. + +**Top Scenario (xDSL):** + +- OLT (Optical Line Terminal):** Contains SDH PL-TP, TC-Adaptor, VP-Layer, and PON PL-TP. +- ONU (Optical Network Unit):** Contains PON PL-TP, TC-Adaptor, VP-Layer, and xDSL PL-TP. +- NT (Network Termination):** Contains xDSL PL-TP, TC-Adaptor, VP-Layer, and ATM Adapt. Layer 1/5. + +**Bottom Scenario (PON):** + +- OLT (Optical Line Terminal):** Contains SDH PL-TP, TC-Adaptor, VP-Layer, and PON PL-TP. +- ONT (Optical Network Terminal):** Contains PON PL-TP, TC-Adaptor, VP-Layer, and ATM Adapt. Layer 1/5. + +The diagram also shows the internal structure of the network termination/terminal equipment (NT/ONT), which includes: + +- ATM Adapt. Layer 1/5:** Contains Native LAN UNI AAL5, CES UNI AAL1, and N×64 kbit/s UNI AAL1. +- Fix Conn:** Contains ATM UNI. +- TC-Adaptor:** Contains ATM UNI. +- VP-Layer:** Contains ATM UNI. + +G.834.1\_F5 + +Diagram showing AAL monitoring architecture for two scenarios: xDSL and PON. The top scenario shows an OLT connected to an ONU (1:N) which is then connected to an NT (1:1). The bottom scenario shows an OLT connected to an ONT (1:N). Both scenarios show the internal layer structure of the OLT, ONU/ONT, and the network termination/terminal equipment. + +**Figure 5/Q.834.1 – Performance monitoring on AAL** Performance monitoring is a function to produce user- or service-dependant information to indicate the state of connections for maintenance. For performance monitoring, the source of the connection/link and the sink of the connection/link will be considered. Table 1 describes the required attributes for collection of information and the related managed entities (always bidirectional). A suffix "FSAN" is omitted from each entity. ITU-T Recommendation numbers for the related managed objects are written in the table as references. Traffic management or monitoring will always be executed at one point in the network. + +**Table 1/Q.834.1 – Performance parameters** + +| Monitoring group | Descriptions | Network element | Attribute | Managed entity | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|---------------------------------------------------------------------------------------------------------------------| +| ATM Adaptation Layer 1 (AAL1) | Count of the number of AAL1 header errors. Header errors include correctable and uncorrectable CRC plus bad parity. | OLT/ONT | Header errors | AAL1 Protocol Monitoring current data
AAL1 Protocol Monitoring history data

Monitoring Period 15 min/24 h | +| | Count of incoming AAL Type 1 SAR-PDUs where the sequence count in the PDU header causes a transition from the SYNC state to the OUT OF SEQUENCE state as defined by ITU-T Rec. I.363.1. | OLT/ONT | Sequence violations | | +| | Count of the number of lost cells, as detected by the AAL1 sequence number processing, for example. This count records the number of cells detected as lost in the network prior to the destination interworking function AAL1 layer processing. | OLT/ONT | Cell loss | | +| | Count of sequency violation events which the AAL CS interprets as misinserted of cells as defined by ITU-T Rec. I.363.1. | OLT/ONT | Cell misinsertion | | +| | Count of the number of times the reassembly buffer underflows. In the case of a continuous underflow caused by a loss of ATM cell flow, a single buffer underflow should be counted. If the interworking function is implemented with multiple buffers, such as a cell level buffer and a bit level buffer, then either buffer underflow will cause this count to be incremented. | OLT/ONT | Buffer underflows | | +| | Count of the number of times the reassembly buffer overflows. If the interworking function is implemented with multiple buffers, such as a cell level buffer and a bit level buffer, then either buffer overflow will cause this count to be incremented. | OLT/ONT | Buffer overflows | | + +**Table 1/Q.834.1 – Performance parameters** + +| Monitoring group | Descriptions | Network element | Attribute | Managed entity | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------------------|--------------------------------------------------------------------------------| +| | Count of the number of events in which the AAL1 reassembler found that a structured data pointer is not where it is expected, and the pointer must be reacquired. This count is only meaningful for structured data transfer modes as unstructured modes do not use pointers. | OLT/ONT | STD pointer reframes | | +| | Count of the number of times the AAL reassembler detects a parity check failure at the point where a structured data pointer is expected. This count is only meaningful for structured data transfer modes as unstructured modes do not use pointers. | OLT/ONT | STD pointer parity check failures | | +| ATM Adaptation Layer 5 (AAL5) | Sum-of-errors count for invalid Convergence Sub-layer (CS) field errors. For AAL Type 5, this attribute provides a single count of the number of CS PDUs discarded due to one of the following error conditions: Invalid Common Part Indicator (CPI), oversized received SDU, or length violation. | OLT/ONT | Invalid CS fields | AAL5 Protocol Monitoring current data
AAL5 Protocol Monitoring history data | +| | Number of CRC violations that were detected for the incoming SAR PDUs. | OLT/ONT | CRC violation | Monitoring Period 15 min/24 h | +| | Count of reassembly timer expirations. A negative value indicates that this attribute is not supported. | OLT/ONT | Reassembly timer expirations | | + +**Table 1/Q.834.1 – Performance parameters** + +| Monitoring group | Descriptions | Network element | Attribute | Managed entity | +|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|----------------------------------------------------------------| +| Traffic measurement | Count of the number of ATM cells that were discarded due to traffic descriptor violations detected by the UPC/NPC policing of the combined high and low cell loss priority traffic. | OLT/ONT | Discarded cells | upcNpcCurrentData, upcNpcHistoryData (7.2.18 and 7.2.19/I.751) | +| | Count of number of cells with CLP=0 that were discarded due to traffic descriptor violations detected by UPC/NPC policing of high priority (CLP=0) only traffic. | OLT/ONT | Discarded CLP0 cells | Monitoring Period 15 min/24 h | +| | Count of number of cells with CLP=0 that were tagged (i.e., CLP reset to 1) by UPC/NPC function. | OLT/ONT | Tagged CLP0 cells | | +| ATM layer VP/VC performance management | Count for incoming user information cells processed on the termination point being monitored. | OLT/ONU/ONT/NT | User cells | vpVcPMCurrentData, vpVcPMHistoryData (7.2.24 and 7.2.25/I.751) | +| | Count of detected lost cells. | OLT/ONU/ONT/NT | Lost cells | Monitoring Period 15 min/24 h | +| | Count of incoming user information cells processed on the termination point being monitored by the far-end terminal. | OLT/ONU/ONT/NT | Far-end user cells | | +| | Count of detected lost cells. | OLT/ONU/ONT/NT | Far-end lost cells | | + +**Table 1/Q.834.1 – Performance parameters** + +| Monitoring group | Descriptions | Network element | Attribute | Managed entity | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------------|-----------------------------------------------------------------------------------------| +| Circuit emulation service UNI | Number of errored seconds encountered by a DS1/E1/J1 interface in the current 15-minute interval. | OLT/ONT | Errored seconds | PM Current Data/PM History Data (ITU-T Rec. G.826)

Monitoring Period 15 min/24 h | +| | Number of severely errored seconds encountered by a DS1/E1/J1 interface in the current 15-minute interval. | OLT/ONT | Severely errored seconds | | +| | Number of bursty errored seconds encountered by a DS1/E1/J1 interface in the current 15-minute interval. A BES is any second that is not a UAS that contains between 2 and 319 error events, but no LOS, AIS, or OOF condition. | OLT/ONT | Bursty errored seconds | | +| | Number of unavailable seconds encountered by a DS1/E1/J1 interface in the current 15-minute interval. | OLT/ONT | Unavailable seconds | | +| | Number of controlled slip seconds encountered by a DS1/E1/J1 interface in the current 15-minute interval. | OLT/ONT | Controlled slip seconds | | + +### 8 Managed entities + +This clause describes the managed entities that are visible across the Q interface. These managed entities are abstract representations of resources and services in a full service access network. Managed entities are defined in a protocol-neutral fashion. Further work will be required to make the MIB definitions protocol-specific (e.g., CMIP- or CORBA-compliant). Some MIB definitions defined herein are based on the models defined by the ATM Forum [20]. New specific classes are so indicated. + +This Recommendation uses a combined view defined in 6.2. Some managed entities for the network view and those for the network element view are pointed to each other in the combined view. Figures 6-1 and 6-2 illustrate combined view managed entities relevant to APON layer. + +![Figure 6-1/Q.834.1 – APON managed entities](abc0eb594f9d2c0daa0e60df05f2a666_img.jpg) + +``` + + graph LR + subgraph OLT + tcAdaptorF_OLT[tcAdaptorF] + APON_TTP_OLT[APON TTP] + APON_CTP_OLT[APON CTP] + tcAdaptorF_OLT --- APON_TTP_OLT + APON_TTP_OLT --- APON_CTP_OLT + end + + subgraph ONT + tcAdaptorF_ONT[tcAdaptorF] + APON_TTP_ONT[APON TTP] + APON_CTP_ONT[APON CTP] + tcAdaptorF_ONT --- APON_TTP_ONT + APON_TTP_ONT --- APON_CTP_ONT + end + + APON_TTP_OLT -- APONTrail -- APON_TTP_ONT + APON_CTP_OLT -- APONLinkConnection -- APON_CTP_ONT + + OLT_Link(( )) -- APONLink -- ONT_Link(( )) + +``` + +The figure consists of two parts. The left part is a block diagram showing the connectivity between OLT (Optical Line Terminal) and ONT (Optical Network Terminal). It shows a vertical stack of tcAdaptorF, APON TTP, and APON CTP on both sides. Horizontal lines connect APON TTPs (labeled APONTrail) and APON CTPs (labeled APONLinkConnection). Below these, a branching line labeled APONLink connects the OLT to multiple ONT points. The right part is a 3D perspective diagram of a layered architecture. It shows three horizontal layers labeled Trail, Link Connection, and Link. Within these layers, vertical blocks represent tcAd, TTP, and CTP entities, showing their hierarchical relationship across the OLT and multiple ONT instances. + +Figure 6-1/Q.834.1 – APON managed entities + +**Figure 6-1/Q.834.1 – APON managed entities** + +18 ITU-T Rec. Q.834.1 (06/2004) + +![Diagram illustrating APON managed entities and their connections. The diagram shows two ONT/ONU entities (ONT/ONU #1 and ONT/ONU #2) on the left, each with a PhysicalPathTPF and a Sink/Source. These are connected to two APONLink entities (Downstream and Upstream) in the center. The Downstream APONLink is connected to the ONT/ONU #1 and ONT/ONU #2, while the Upstream APONLink is connected to the ONT/ONU #2 and the OLT on the right. The OLT has a PhysicalPathTPF and a Sink/Source. The diagram also shows connections between APONLinkConnection #1 and #2, and APONTrail #1 and #2. The diagram is labeled Q.834.1_F6-2.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +The diagram illustrates the APON managed entities and their connections. It shows two ONT/ONU entities (ONT/ONU #1 and ONT/ONU #2) on the left, each with a PhysicalPathTPF and a Sink/Source. These are connected to two APONLink entities (Downstream and Upstream) in the center. The Downstream APONLink is connected to the ONT/ONU #1 and ONT/ONU #2, while the Upstream APONLink is connected to the ONT/ONU #2 and the OLT on the right. The OLT has a PhysicalPathTPF and a Sink/Source. The diagram also shows connections between APONLinkConnection #1 and #2, and APONTrail #1 and #2. The diagram is labeled Q.834.1\_F6-2. + +Diagram illustrating APON managed entities and their connections. The diagram shows two ONT/ONU entities (ONT/ONU #1 and ONT/ONU #2) on the left, each with a PhysicalPathTPF and a Sink/Source. These are connected to two APONLink entities (Downstream and Upstream) in the center. The Downstream APONLink is connected to the ONT/ONU #1 and ONT/ONU #2, while the Upstream APONLink is connected to the ONT/ONU #2 and the OLT on the right. The OLT has a PhysicalPathTPF and a Sink/Source. The diagram also shows connections between APONLinkConnection #1 and #2, and APONTrail #1 and #2. The diagram is labeled Q.834.1\_F6-2. + +Figure 6-2/Q.834.1 – APON managed entities + +### 8.1 AAL1PMHistoryDataF + +This is a managed entity that contains the past performance monitoring data collected as a result of performing Segmentation and Reassembly (SAR) Level and Convergence Sub-layer (CS) protocol monitoring. Instances of this managed entity are created automatically whenever the client requests performance monitoring or NMS at the associated interworking vcCTPF managed entity and the data collection interval is completed. + +#### Attributes + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**InterworkingVCCTPPtr:** This attribute identifies the associated vcCTPF representing the AAL1 functions. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**HeaderErrors:** A count of the number of AAL1 header errors detected, including corrected ones. Header errors include correctable and uncorrectable CRC plus bad parity. + +**LostCells:** A count recording the number of cells detected as lost in the network prior to the destination interworking function AAL1 layer processing. + +**CellMisinsertion:** A count of sequence violation events that the AAL CS interprets as due to a misinserted cell. + +**BufferUnderflows:** A count of the number of times that the reassembly buffer underflows. + +**BufferOverflows:** A count of the number of times that the reassembly buffer overflows. + +**SequenceViolations:** A count of incoming AAL Type 1 SAR-PDUs where the sequence count in the PDU header causes a transition from the SYNC state to the OUT OF SEQUENCE state. + +**SDTPtrReframes:** The count of the number of times that the AAL1 reassembler found that a structured data pointer is not where it is expected (only for use with Structured CES). + +**SDTPtrParityCheckFailures:** The count of the number of times the AAL reassembler detects a parity check failure at the point where a structured data pointer is expected (only for use with Structured CES). + +#### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of an interworking vcCTPF managed entity that represents AAL1 functions. + +### **8.2 AAL1ProfileF** + +This managed entity is used to organize data that describes the AAL Type 1 processing functions of the FSAN NE. Each instance of this managed entity class defines a combination of parameter values that may be associated with one or more interworking vcCTPF managed entities. Instances of this managed entity are created and deleted by request of the NMS or operators. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SubType:** This attribute identifies the AAL subtype. Valid values for this attribute are "null", "voice-band based on 64 kbit/s", "Synchronous Circuit Emulation", "Asynchronous Circuit Emulation", "High-quality Audio", and "Video". + +**CBRRate:** This attribute represents the rate of the CBR service supported by the AAL. Allowed values are "64 kbit/s", "1544 kbit/s", "44 736 kbit/s", and various "n×64 kbit/s". + +**ClockRecoveryType:** This attribute indicates whether the clock recovery type is derived from the physical interface, SRTS (Synchronous Residual Time Stamp), Adaptive Clock Recovery, or derived from a local oscillator. SRTS is chosen for CES DS1 at the ONT. Local oscillator is chosen for DS3 network interface on the OLT. + +**ForwardErrorCorrectionType:** This attribute indicates the FEC method: no FEC, FEC for Loss Sensitive Signal Transport, or FEC for Delay Sensitive Signal Transport. + +**StructuredDataTransfer:** This Boolean attribute indicates whether Structured Data Transfer (SDT) has been configured at the AAL. A value of TRUE means SDT has been selected. This attribute value cannot be set to TRUE when the Forward Error Correction Type attribute equals no FEC. + +**PartiallyFilledCells:** This Boolean attribute identifies the number of leading octets in use. This attribute is used only in conjunction with a value of TRUE for the Structured Data Transfer attribute. This attribute has a permitted range between 0 and 53. + +**CellLossIntegrationPeriod:** This attribute represents the time in milliseconds for the cell loss integration period. If cells are lost for this period of time, the associated interworking vcCTPF entity will generate a cell starvation alarm.1 + +#### *Relationships* + +One instance of this managed entity shall exist for each combination of AAL1 parameter values used within a FSAN NE. One instance of this managed entity may be associated to one or more instances of an interworking vcCTPF. + +### **8.3 AAL2PMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected as a result of adaptation layer 2 protocol conversion monitoring. Instances of this managed entity are created automatically whenever the client requests performance monitoring or NMS at the associated interworking vcCTP managed entity and the data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**InterworkingVCCTerminationPointPtr:** This attribute identifies the associated vcCTP representing the AAL2 functions. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**CPSInPkts:** This attribute records the number of CPS packets received by the port group associated with the interworking vcCTP. + +**CPSOutPkts:** This attribute records the number of CPS packets transmitted by the port group associated with the interworking vcCTP. + +**BufferUnderflow:** This attribute records the number of times the reassembly buffer underflows. In the case of a continuous underflow caused by a loss of ATM cell flow, a single buffer underflow should be counted. If the interworking function is implemented with multiple buffers, such as cell level buffer and a bit level buffer, then either buffer underflow will cause this count to be incremented. If the actual counter saturates, it remains at the maximum value. + +**BufferOverflow:** This attribute records the number of times the reassembly buffer overflows. In the case of a continuous underflow caused by a loss of ATM cell flow, a single buffer overflow should be counted. If the interworking function is implemented with multiple buffers, such as cell level buffer and a bit level buffer, then either buffer overflow will cause this count to be incremented. If the actual counter saturates, it remains at the maximum value. + +**ParityErrors:** This attribute records the number of CPS PDUs discarded because of incorrect parity value in the STF. + +**SeqNumErrors:** This attribute records the number of CPS PDUs received with incorrect sequence number in the STF. + +--- + +1 Current OMCI limits the range of this value between 0 and 65535. + +**CPS\_OSFMismatchErrors:** This attribute records the number of CPS PDUs received with the number of octets expected for a CPS-Packet overlapping into the next CPS PDU not matching with the information contained in the STF. + +**CPS\_OSFEErrors:** This attribute records the number of CPS PDUs discarded because of the incorrect OSF value in the STF. + +**CPSHECErrors:** This attribute records the number of CPS packets having a header value indicating transmission errors in the header. + +**OversizedSDUErrors:** This attribute records the number of times the received CPS packet payload exceeds the maximum length indicated in MaxCPS\_SDULen attribute. + +**ReassemblyErrors:** This attribute records the number of times that partial CPS packets are discarded because errors were detected for the reassembly could be completed. + +**HECOverlapErrors:** This attribute records the number of times that a CPS packet is received with a HEC that overlaps a CPS PDS boundary. + +**UIErrors:** This attribute records the number of times that a UII is received with a value that is reserved for future use. + +**CIDErrors:** This attribute records the number of times that a CPS PDU is received with an incorrect CID value. + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of an interworking vcCTP managed entity that represents AAL2 functions. + +### **8.4 AAL2ProfileF** + +This managed entity is used to organize some of the data that describes the AAL Type 2 processing functions of the NE. Each instance of this managed entity class defines a combination of parameter values that may be associated with one or more instances of the interworking vcCTP managed entities. Instances of this managed entity are created and deleted by request of the NMS or Operators. These attributes must be provisioned for both PVC and SVC VCCs. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**DefaultSSCSPParameterProfile1Ptr:** This attribute identifies the default values for the service-specific convergence service profile associated with channels carrying control and management plane traffic (e.g., CCS, ELCP, ISDN D-channels, and LES-EOC). + +**DefaultSSCSPParameterProfile2Ptr:** This attribute identifies the default values for the service-specific convergence service profile associated with channels carrying media streams (e.g., POTS or ISDN B-channels). + +#### *Relationships* + +One instance of this managed entity shall exist for each combination of AAL2 parameter values used within an NE associated with a VCC that is either an SVC or a PVC. One instance of this managed entity may be associated with one or more instances of an interworking vcCTP. + +### **8.5 AAL2PVCProfileF** + +This managed entity is used to organize data that describes some of the AAL Type 2 processing functions of the NE. Each instance of this managed entity class defines a combination of parameter values that may be associated with one or more instances of the interworking vcCTP managed + +entities. Instances of this managed entity are created and deleted by request of the NMS or Operators. These attributes must be provisioned for PVCs (including soft-PVCs). + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AppId:** This attribute specifies the protocol combinations used between the interworking functions found in the Voice Gateway and the ONT. Valid values include those provided in Section 4.1.1 of ATM Forum AF-VMOA-0145.000. + +**MaximumNumChan:** This attribute provides the maximum number of channels that can be carried by the VC trail associated with the interworking vcCTP. + +**MinimumChanIdVal:** This attribute provides the minimum value for the Channel Id allowed for any channel within the connection. + +**MaximumChanIdVal:** This attribute provides the maximum value for the Channel Id allowed for the channel within the connection. + +**MaxCPS\_SDULen:** This attribute provides the maximum allowed length of the Common Part Sublayer Service Data Unit (or CPS SDU) that will be allowed over the connection in either the upstream or downstream direction of transmission. + +**TimerCULen:** This attribute provides the value for the "combined use" timer Timer\_CU. + +#### *Relationships* + +One instance of this managed entity shall exist for each combination of AAL2 parameter values used within an NE associated with a VCC that is a PVC. One instance of this managed entity may be associated with one or more instances of an interworking vcCTP. + +### **8.6 AAL5PMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected as a result of performing Segmentation and Reassembly (SAR) Level and Convergence Sublayer (CS) protocol monitoring. Instances of this managed entity are created automatically whenever the client requests performance monitoring or NMS at the associated interworking vcCTPF managed entity and the data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**InterworkingVCCTPPtr:** This attribute identifies the associated TP representing the AAL5 functions. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**SumOfInvalidCSFieldErrors:** This attribute provides a sum-of-errors count for invalid Convergence Sublayer (CS) field errors. This attribute provides a single count of the number of CS PDUs discarded due to one of the following error conditions: Invalid Common Part Indicator, oversized received SDU, or length violation. + +**CRCViolations:** This attribute represents the number of CRC violations that were detected for the incoming Segmentation and Reassembly Layer (SAR) PDUs. + +**BufferOverflows:** This attribute indicates the number of times that there was not enough buffer space for a reassembled packet. + +**EncapProtocolErrors:** This attribute indicates the number of times that the RFC 1483 encapsulation protocol detects a bad header. + +#### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of the interworking vcCTPF managed entity that represents AAL5 functions. + +### **8.7 AAL5ProfileF** + +This managed entity is used to organize data that describes the AAL Type 5 processing functions of the FSAN NE. Each instance of this managed entity class defines a combination of parameter values that may be associated with one or more interworking vcCTPF managed entities. Instances of this managed entity are created and deleted by request of the NMS or operators. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MaxCPCSSDUSize:** This multi-valued attribute represents the maximum CPCS\_SDU size that will be transmitted over the connection in both the incoming (forward) and outgoing (backward) direction of transmission.2 + +**AALMode:** This attribute indicates which mode the AAL for the supporting VCC is employed: message assured, message unasserted, streaming assured, and streaming non-assured. + +**SSCSType:** This attribute identifies the SSCS type for the AAL. Valid values are "none", "Data SSCS based on SSCOP" (assured mode), "Data SSCS based on SSCOP" (non-assured mode), or "Frame Relay SSCS". + +#### *Relationships* + +One instance of this managed entity shall exist for any combination of AAL5 parameter values used within the FSAN NE. One instance of this managed entity may be associated to one or more instances of interworking vcCTPF. + +### **8.8 accessGroupF** + +This managed entity is used to group TTPFs that lie outside the management scope of the FSAN EMS (even outside the scope of the operator's network) but need to be referred to for management purposes. For example, this managed entity will be used to group vcTTPF instances terminated on customer-provided equipment. It is used to provide a topological view to the operator. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**TopologicalLinkFPtr:** This attribute identifies the topologicalLinkF managed entity for which this managed entity is ending. + +**SignalIdentification:** This attribute identifies the characteristic signal transported between this accessGroupF and the other end of the topologicalLinkF. + +--- + +2 The current version of the OMCI limits the range of this attribute between 0 and 65535. However, the actual maximum value depends on the buffer size in the ONT subscriber circuitry and is likely to be smaller. + +**Logical(MTP)LinkFPtr:** This attribute identifies the logicalLinkF or logicalMTPLinkF associated with this end point. + +**TTPFPtrList:** This attribute serves as a pointer to the instances of the TTPF that is grouped by this managed entity. This pointer may be null. + +**TopologicalDirectionality:** This attribute identifies whether the termination point is "source", "sink", or "bidirectional". + +#### *Relationships* + +Zero or one of these managed entities is associated with a topologicalLinkF. + +### **8.9 adslCTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates an ADSL section link connection. + +#### *Attributes* + +**ADSLProfilePtr:** This attribute identifies the ADSL transport level profile associated with this CTPF. + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE except for the OLT. One of these managed entities exists for each adslTTPF. + +### **8.10 adslLayerNetworkDomainF** + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. The characteristic signal associated with this layer is defined by ITU-T Recs G.992.1 and G.992.2, or ANSI T1.413. + +### **8.11 adslLinkConnectionF** + +This managed entity is a type of LinkConnectionF and inherits all the attributes and relationships defined by LinkConnectionF. This managed entity represents a VDSL link connection, derived from the G.852.2 definition, i.e., "the transparent capacity of transfer of information characterized by a given signal identification between two fixed points". Directionality is always set to "bidirectional". + +#### *Attributes* + +**SignalIdentification:** This fixed attribute describes the signal that is transferred across the link. Here, it is set to "ADSL". + +#### *Relationships* + +A topological link is a group of link connections sharing the same extremities. This relationship involves zero or more instances of the managed entity adslLinkConnectionF. An adslLinkConnectionF links two adslCTPFs. + +### **8.12 adslSubnetworkF** + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "ADSL". + +#### *Attributes* + +**ONUPtr:** This attribute identifies the associated ONU. + +**ContainedLinkList:** This attribute identifies the instances of adslTopologicalLinkF contained in this subnetwork. + +### **8.13 adslTopologicalLinkEndF** + +This managed entity is a type of topologicalLinkEndF and inherits all the attributes and relationships defined by topologicalLinkEndF. Signal identification is set to "ADSL". + +### **8.14 adslTopologicalLinkF** + +This managed entity is a type of topologicalLinkF and inherits all the attributes and relationships defined by topologicalLinkF. Signal identification is set to "ADSL". + +### **8.15 adslTrailF** + +This managed entity is a type of trailF and inherits all the attributes and relationships defined by trailF. + +#### *Relationships* + +Each adslTrailF is terminated by adslTTPs. + +### **8.16 adslTTPF** + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a trail for ADSL. The following alarms can be detected at this managed entity: Loss of Frame (LOF), Remote Failure Indication (RFI), Signal Degraded (SD) fast datastream, Signal Degraded (SD) interleave datastream, Signal Degraded (SD) fast datastream far end, Signal Degraded (SD) interleave datastream far end, Initialization failed (detected by dataInitFailure, configInitFailure, protocolInitFailure, noPeerAtuPresent), Loss of Link, and Loss of Power. + +#### *Attributes* + +**TcAdaptorPtr:** This attribute points to the tcAdaptor managed entity that uses this managed entity as a server trail. + +**ADSLProfilePtr:** This attribute identifies the ADSL transport level profile associated with this TTPF. + +#### *Relationships* + +There is one or more of these managed entities contained within an FSAN NE except for the OLT. One of these managed entities exists for each adslCTPF managed entity and one for each tcAdaptorF managed entity it supports. One of these managed entities exists for each PhysicalPathTPF of Type "ADSL". + +### **8.17 alarmLogRecordF** + +This managed entity represents information logged by the FSAN EMS resulting from a FSAN NE generated alarm and subsequent alarm processing within the FSAN EMS. Instances of this managed entity are created and deleted by the FSAN EMS. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**LoggingTime:** This attribute provides the time at which the record was entered into the log. + +**ManagedEntityAssertion:** This attribute identifies the type and instance for the managed entity reporting the failure condition. + +**FailureCondition:** This attribute identifies the failure condition detected by the FSAN NE. + +**Severity:** This attribute identifies the severity assigned to the alarm notification. + +**EventTime:** This attribute provides the time at which the event took place as detected by the FSAN NE. + +**Back-upStatus:** This attribute indicates whether or not the managed entity in the FSAN NE emitting the alarm has been backed-up if the managed entity has failed. + +**Back-upEntity:** This attribute identifies the instance of the managed entity that is providing the back-up services to the failed managed entity. + +**AdditionalInfo:** This attribute is used to list service instances affected by the failure condition. + +**MonitoredParameter:** This attribute identifies the performance monitored parameter whose observed value triggered a threshold crossing alert in the FSAN NE, if the alarm is based on a Threshold Crossing Alert (TCA). + +**ThresholdRange:** This attribute identifies the high and low values for the threshold setting of the monitored parameter. If high and low values are the same, then there is only a single threshold setting. + +**ObservedValue:** This attribute provides the value for the performance parameter triggering a TCA, if the alarm is based on a TCA. + +#### *Relationships* + +Multiple instances of this managed entity may be contained in an instance of the LogF managed entity. + +### **8.18 alarmSeverityAssignmentProfileF** + +This managed entity is used to identify the alarm severity assignments for failure conditions associated with alarm-reporting managed entities. Instances of this managed entity are created and deleted by request of the NMS or the Operator. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AlarmSeverityAssignmentList:** This attribute identifies one or more alarm severity assignments. The assignment correlates severity (critical, major, minor, warning) with failure condition and alarm event name. + +#### *Relationships* + +An instance of this managed entity is referred to by the AlarmSeverityAssignmentProfileFPtr attribute in the alarm-reporting managed entities (e.g., pluginUnitF, PhysicalPathTPF, EquipmentHolderF, etc.). + +### **8.19 APONCTP** + +This managed entity is a type of CTPF and possesses all the attributes and relationships defined by CTPF. This managed entity is used to represent the termination of APONLinkConnection on an FSAN NE. + +#### *Attributes* + +**PhysicalPathTPFPtr:** This pointer attribute identifies the associated instance of the physicalPathTPF managed entity. + +#### *Relationships* + +There is one or more of these managed entities contained within an OLT, ONU, or ONT. One of these managed entities exists for each APONTTPF. + +### **8.20 APONLayerNetworkDomain** + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. Characteristic information provided in this layer is defined by the APON protocol as defined in ITU-T Rec. G.983.1. + +### **8.21 APONLink** + +This managed entity is a type of LogicalMTPLinkF and inherits all the attributes and relationships defined by LogicalMTPLinkF. Each PON is composed of two LogicalMTPLinkF(s), one describing the downstream and the other describing the upstream capacity provided by the OLT PON interface. The Aend is associated with a PON interface on the OLT. There is one Zend for each ONT ranged to the Aend PON interface. The TotalLinkConnectionCount attribute value is determined by the number of output ports on the passive optical coupler. + +#### *Attributes* + +**OLTTCAdaptorId:** This attribute identifies the OLT PON interface. + +**ONTTCAdaptorIdList:** This attribute identifies (lists) the subtending ONT PON interfaces. + +**PairedAPONLinkPtr:** This pointer attribute identifies the APON Link that paired with this one describes the upstream and downstream APON layer capacity. + +#### *Relationships* + +There are two APONLink managed entities for every PON interface on the OLT. + +### **8.22 APONLinkConnection** + +This managed entity is a type of LinkConnectionF and inherits all the attributes and relationships defined by LinkConnectionF. + +#### *Relationships* + +There is one instance of this managed entity for every installed ONT. + +### **8.23 APONLogicalLinkEnd** + +This managed entity is a type of logicalLinkEndF and inherits all the attributes and relationships defined by logicalLinkEndF. + +### **8.24 APONSubnetwork** + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "APON". + +#### *Attributes* + +**OLTPtr:** This attribute identifies the associated OLT. This pointer may be null-valued when the APONSubnetworkF is the subnetworkF for the entire APONNetworkLayerDomainF. + +**ContainedLinkList:** This attribute identifies the instances of logicalMTPLinkF contained in this subnetworkF. + +**ContainedLinkEndList:** This attribute identifies the instances of logicalLinkEndF contained in this subnetworkF. + +#### *Relationships* + +One of these managed entities exists for each installed OLT. + +### **8.25 APONTrail** + +This managed entity is a type of trailF and inherits all the attributes and relationships defined by trailF. + +#### *Relationships* + +Each APONTrail is terminated by two APONTTPs. + +### **8.26 APONPhysicalPortResource** + +This managed entity collects key capacity metrics for PON-side port of the OLT. One instance of this managed entity is created automatically when the port with PhysicalPathType equal to APON is provisioned. The automatic creation of instances of this managed entity may be reported to the managing system. The managed entity shall be automatically deleted when the port is deleted. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PortManagedEntityId:** This attribute identifies the associated port. + +**MaxBW:** This attribute identifies the maximum amount of bandwidth for assignment at the port of OLT. + +**MaxVPConnectionCount:** This attribute identifies the maximum count of VPs assigned to the port of OLT. + +**AssignedVPConnectionCount:** This attribute identifies the already-assigned count of VPs assigned to the port of OLT. + +**ReservedVPConnectionCount:** This attribute identifies the reserved count of VPs assigned to the port of OLT. + +**MaxVCCConnectionCount:** This attribute identifies the maximum count of VCs assigned to the port of OLT. + +**AssignedVCCConnectionCount:** This attribute identifies the already-assigned count of VCs assigned to the port of OLT. + +**ReservedVCCConnectionCount:** This attribute identifies the reserved count of VCs assigned to the port of OLT. + +**MaxTCONTBW:** This attribute identifies the sum of max bandwidth of all provisioned T-CONT assigned to the port of OLT. + +**AssignedGuaranteedBW:** This attribute identifies the already-assigned guaranteed bandwidth assigned to the port of OLT. + +**ReservedGuaranteedBW:** This attribute identifies the reserved guaranteed bandwidth assigned to the port of OLT. + +#### *Relationships* + +One instance of this managed entity shall exist for each instance of the PON-side port of OLT. + +### **8.27 APONPMHistoryData** + +This managed entity is used to manage performance monitoring data that is collected at PON sections in the past. OLT measures errored second on OLT and each ONU/ONT. This entity is created when performance data is confirmed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique number for each instance of this managed entity. + +**GranularityPeriod:** This attribute represents time of a measurement period. + +**ES:** This attribute represents the count of seconds with one or more errors of signal from each ONU/ONT which were detected at OLT during a past measurement period. + +**FEES:** This attribute represents the count of seconds with one or more errors detected at far-end ONU/ONT during a past measurement period. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the threshold data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** Collection completed time is represented. + +#### *Relationships* + +Multiple instances can be contained towards APONPMCurrentDataF. + +### **8.28 APONTTP** + +This managed entity is a type of TTPF and possesses all the attributes and relationships defined by TTPF. This managed entity represents the point in the FSAN NE where APONTrailF is terminated and originated. The following alarms can be detected at this managed entity: Loss of Physical Layer (detected by LOAi (Loss of Acknowledgement), OAMLi (PLOAM cell loss), CP Ei (Cell Phase Error), SUFi (Start up failure) and REC-INH (Receive Alarm Inhibition)), SD (Signal Degraded) and SD (Signal Degraded) far end. + +#### *Relationships* + +There is one or more of these managed entities contained within an OLT, ONU, or ONT. One of these managed entities exists for each APONCTPF. + +### **8.29 ATMCrossConnectionF** + +This managed entity is used to represent the cross-connect relationship between two VP or VC CTPFs. Instances of this managed entity are created automatically by request of the managing system based on connection requests. Instances of this managed entity are deleted by the FSAN NE or by request of the managing system. The managed entity supports the operational state and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**Availability:** This attribute indicates whether or not a managed entity is capable of performing its task. + +**TerminationPointA:** This attribute identifies the instance of the vp (or vc) CTPF managed entity that represents the termination point of one of the two cross-connected link connections. + +**TerminationPointZ:** This attribute identifies the instance of the vp (or vc) CTPF managed entity that represents the termination point of the other one of the two cross-connected link connections. + +**RecoveryType:** This attribute is used to configure an ATMCrossConnectionF as a "recoverable" cross-connection or "non-recoverable" cross-connection. Recoverable cross-connection relationships remain intact regardless of the operational state of the supporting virtual path or virtual connection. A non-recoverable cross-connection is one that is torn down (i.e., released) upon detection of an affecting failure. + +#### *Relationships* + +Zero or more instances of the ATMCrossConnectionF managed entity shall exist for each instance of the ATMCrossConnectionControlF managed entity. Each instance of this managed entity is associated with two (for point-to-point) instances of the vp (or vc) CTPF managed entity by the Termination Point A and Termination Point Z pointer attributes. + +### **8.30 ATMCrossConnectionControlF** + +This managed entity manages the establishment and release of vp or vc cross-connections (e.g., VPI/VCI translations) in the FSAN NE. The managed entity supports the operational state function as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. The FSAN NE upon initialization creates an instance of this managed entity automatically. This managed entity cannot be deleted as long as the NE is in service. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**OperationalState:** This attribute indicates whether or not a managed entity is capable of performing its task. Valid values are "enabled" and "disabled". + +#### *Relationships* + +One instance of the ATMCrossConnectionControlF managed entity shall exist for each instance of the OLT, ONT, or ONU managed entity. + +### **8.31 ATMNetworkAccessProfileF** + +This managed entity is used to organize data associated with ATM Network Interfaces (NNI). Instances of this managed entity help to configure ATM network interfaces and PON interfaces terminating on the OLT. Instances of this managed entity can be created automatically at OLT initialization. Instances of this managed entity are created and deleted by request of the NMS or Operators. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**LocalMaximumNumberofVPCsSupportable:** This attribute identifies the number of VPCs that can be supported by the OLT at this end of the interface. + +**LocalMaximumNumberofVCCsSupportable:** This attribute identifies the number of VCCs that can be supported by the ATM NE at this end of the interface. + +**LocalMaximumNumberofAllocatedVPIBits:** This attribute identifies the maximum number of allocated bits of the VPI sub-field that can be supported by the FSAN NE at this end of the interface. + +**LocalMaximumNumberofAllocatedVCIBits:** This attribute identifies the maximum number of allocated bits of the VCI sub-field that can be supported by the FSAN NE at this end of the interface. + +**TotalEgressBandwidth:** This attribute identifies the total amount of egress bandwidth for an ATM Interface. + +**TotalIngressBandwidth:** This attribute identifies the total amount of ingress bandwidth for an ATM Interface. + +**UPC/NPC:** This Boolean attribute determines whether or not policing is performed for all connections at the interface. + +#### *Relationships* + +A single instance of ATMNetworkAccessProfileF managed entity is used to characterize the tcAdaptorF managed entity describing the ATM adaptation on the OLT ATM Network Interface or on the OLT PON Interface. + +### **8.32 ATMPhysicalPortResource** + +This managed entity collects key capacity metrics for NNI-side ATM port of the OLT. One instance of this managed entity is created automatically when the port with ATMBearerInd equal to true is provisioned. The automatic creation of instances of this managed entity may be reported to the managing system. The managed entity shall be automatically deleted when the port is deleted. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PortManagedEntityId:** This attribute identifies the associated port. + +**MaxVPCConnectionCount:** This attribute identifies the maximum count of VPs assigned to the port of OLT. + +**MaxVCCConnectionCount:** This attribute identifies the maximum count of VCs assigned to the port of OLT. + +**ReservedVPCConnectionCount:** This attribute identifies the reserved count of VPs assigned to the port of OLT. + +**ReservedVCCConnectionCount:** This attribute identifies the reserved count of VCs assigned to the port of OLT. + +**AssignedVPCConnectionCount:** This attribute identifies the already-assigned count of VPs assigned to the port of OLT. + +**AssignedVCCConnectionCount:** This attribute identifies the already-assigned count of VCs assigned to the port of OLT. + +**MaxBW:** This attribute identifies the maximum amount of bandwidth assigned to the port of OLT. + +**ReservedBW:** This attribute identifies the reserved bandwidth assigned to the port of OLT. + +**AssignedBW:** This attribute identifies the already-assigned bandwidth assigned to the port of OLT. + +#### *Relationships* + +One instance of this managed entity shall exist for each instance of the NNI-side OLT Port with ATMbearerInd equal to true. + +### **8.33 ATMTrafficLoadHistoryDataF** + +This managed entity records historic traffic load data on links to a specific FSAN NE that is produced as a result of ATM cell monitoring. Instances of this managed entity are created automatically whenever performance monitoring is requested by the managing system on the associated managed entity and the data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MonitoringPtPtr:** This attribute identifies the monitoring point for which PM data monitoring was requested. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**CellsReceived:** This attribute provides a count of the number of cells received with either CLP=0 or CLP=1. + +**CellsTransmitted:** This attribute provides a count of the number of cells transmitted with either CLP=0 or CLP=1. + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the associated monitoring point. + +### **8.34 attributeValueChangeRecordF** + +This managed entity is used to represent logged information that resulted from attribute value change notifications. The FSAN NE automatically creates instances of this managed entity. Instances of this managed entity are deleted by the FSAN NE or by request of the managing system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**LoggingTime:** This attribute identifies the time at which the record was entered into the log. + +**ManagedEntity:** This attribute identifies the type and instance ID of the managed entity that generated the attribute value change notification. + +**Attribute Type:** This attribute identifies the type of attribute whose value has changed. + +**OldAttributeValue:** This attribute identifies the previous value of the attribute. + +**NewAttributeValue:** This attribute identifies the new value of the attribute. + +#### *Relationships* + +Multiple instances of this managed entity may exist for an instance of a logF managed entity. + +### **8.35 au3CTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It represents a termination point where an au3 connection is terminated and originated. The AU-3 consists of a VC-3 plus an AU pointer that indicates the phase alignment of the VC-3 with respect to the STM-N frame. The following alarms can be detected at this managed entity: Alarm Indication Signal (AIS) and Loss of Pointer (LOP). + +#### *Attributes* + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for each msTTPF and one for each vc3TTPF. + +### **8.36 au4CTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It represents a termination point where an au4 connection is terminated and originated. The AU-4 consists of a VC-4 plus an AU pointer that indicates the phase alignment of the VC-4 with respect to the STM-N frame. The following alarms can be detected at this managed entity: Alarm Indication Signal (AIS) and Loss of Pointer (LOP). + +#### *Attributes* + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exist for each msTTPF and one for each vc3TTPF. + +### **8.37 BridgedLANLayerNetworkDomainF** + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. Characteristic information provided in this layer is set to "Bridged LAN". + +### 8.38 BridgedLANServiceProfileF + +This managed entity is used to organize data that describes the Bridged LAN Service functions of the FSAN NE if supported. Instances of this managed entity are created and deleted by request of the managing system or operator. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**LANType:** This attribute provides information on the type of LAN employed, e.g., Ethernet, token-ring, etc. + +**EncapsulationProtocol:** This attribute identifies the encapsulation protocol used for bridging LAN over ATM. + +**PID:** This attribute identifies the media type values that can be used in ATM encapsulation (defined in RFC 1483). + +#### *Relationships* + +This managed entity may be associated to zero or more instances of an interworking vcCTPF terminating AAL5. + +### 8.39 BridgedLANSubnetworkF + +This managed entity is a type of SubnetworkF and inherits all the attributes and relationships defined by SubnetworkF. This managed entity cannot be further decomposed. Characteristic information provided in this layer is set to "Bridged LAN". + +### 8.40 BICIF + +This managed entity is used to organize data associated with Broadband Inter-Carrier Interfaces (BICIFs) terminating on the FSAN NE. One instance of this managed entity shall exist for each BICIF terminating on the FSAN NE. Instances of this managed entity are created and deleted by request of the managing system to configure ATM interfaces terminating on the FSAN NE as BICIFs. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**TCAdaptorId:** This attribute provides a Ptr to the associated instance of the tcAdaptorF managed entity. + +**Far-EndCarrierNetwork:** This attribute identifies the adjacent carrier to which the BICIF transmission path is connected. This attribute is needed to support SVC services only. + +**LoopbackLocationCode:** This attribute provides the code that shall exist in incoming OAM Loopback cells that are to be looped-back at the BICIF termination point represented by the managed entity. + +#### *Relationships* + +Multiple instances of the BICIF managed entity may exist for each instance of the OLT managed entity. Each instance of the BICIF managed entity is related to a tcAdaptorF managed entity by the TCAdaptorId attribute. + +### 8.41 BISSIF + +This managed entity is used to organize data associated with Broadband Inter-Switching System Interfaces (BISSIFs) terminating on the FSAN NE. One instance of this managed entity shall exist for each BISSIF terminating on the FSAN NE. Instances of this managed entity are created and deleted by request of the managing system to configure ATM interfaces terminating on the FSAN NE as BISSIFs. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**TCAdaptorId:** This attribute provides a Ptr to the associated instance of the TC Adaptor managed entity. + +**LoopbackLocationCode:** This attribute provides the code that shall exist in incoming OAM loopback cells that are to be looped-back at the BISSIF termination point represented by the managed entity. + +#### *Relationships* + +Multiple instances of the BISSIF managed entity may exist for each instance of the OLT. Each instance of the BISSIF managed entity is related to a tcAdaptorF managed entity by the TCAdaptorId attribute. + +### 8.42 cellBasedCTPF + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates a cell-based connection. + +#### *Attributes* + +**BitratePhysicalLayer:** This attribute provides the value for the corresponding line bit rate (e.g., 155 Mbit/s). + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for each cellBasedTTPF managed entity having the same line bit rate. + +### 8.43 cellBasedTTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a cell-based section trail. The following alarms can be detected at this managed entity: Loss of Frame (LOF), Loss of Multiframe (LOM), Alarm Indication Signal (AIS), Signal Degraded (SD) and Remote Defect Indication (RDI). + +#### *Attributes* + +**BitratePhysicalLayer:** This attribute provides the value for the corresponding line bit rate (e.g., 155 Mbit/s). + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exist for each cellBasedCTPF and one or more for each tcAdaptorF for each interface on a FSAN NE providing native ATM physical layer. One of these managed entities exists for each PhysicalPathTPF of type "cell-based" with the same bit rate. + +### 8.44 CESServiceProfileF + +This managed entity is used to organize data that describes the CES service functions of the FSAN NE (at the DS1 or DS3 level). Instances of this managed entity are created and deleted by request of the managing system or operator. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**CESBufferedCDVTolerance:** This attribute represents the duration of user data that must be buffered by the CES interworking entity to offset cell delay variation. This timing will be in 10 microsecond increments. The default value for DS1 CES is 750 microseconds and 1000 microseconds for DS3 CES. + +**ChannelAssociatedSignalling:** This attribute selects which AAL1 format should be used. It applies to structured interfaces only. For unstructured interfaces this value, if present, must be set to the default "basic". The valid values are: basic, e1Cas, SfCas, ds1EsfCas, j2Cas. + +**CableGaugeLength:** This attribute provides the length of twisted pair cable from the physicalPathTP of type "DS1" interface to the DSX1 cross-connect point (if applicable).3 + +#### *Relationships* + +This managed entity may be associated to zero or more instances of an interworking vcCTPF terminating AAL1. + +### 8.45 CTPF + +This managed entity terminates and originates a link connection as well as a subnetwork connection. Instances of this managed entity can be created and deleted by request of the managing system or implicitly through a provisioning request. The managed entity supports the availability status, operational state and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. This managed entity is defined for the purposes of grouping together all common attributes of connection termination point on an FSAN NE in the NE view, but only instances of specific CTPFs (e.g., adslCTPF, DS1CTPF, etc.) shall be implemented. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**AvailabilityStatus:** This attribute indicates whether or not a managed entity is capable of performing its task. + +**OperationalState:** This attribute indicates whether or not a managed entity is capable of performing its task. The operational state reflects the perceived ability to receive or to generate a valid signal. Valid values are "enabled" and "disabled". If the termination point detects that a signal received has failed or it is unable to process the incoming signal, then the operational state will change from the value enabled to disabled. If the termination point detects that a valid signal cannot be generated, then the operational state will also change from the value "enabled" to "disabled". + +--- + +3 This attribute may have enumerated syntax with a selection of length ranges as setting values. + +**SupportedByPlug-inF:** This attribute identifies the interface circuit pack to which this managed entity is associated. + +**UpstreamConnectivityPointer:** This attribute identifies the termination point managed entity that sends information (traffic) to this managed entity at the same layer. + +**DownstreamConnectivityPointer:** This attribute identifies the termination point managed entity that receives information (traffic) from this managed entity at the same layer. + +**PointDirectionality:** This attribute identifies whether the termination point is "source", "sink", or "bidirectional". + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for any TTPF supported by it. Two instances of this managed entity are associated to each link connection. Zero or more of these instances are associated with each subnetworkConnectionF. + +### **8.46 DS1CTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates a 1544 kbit/s link connection. Characteristic information provided in this layer is set to "DS1". The following alarms can be detected at this managed entity: Loss of Frame (LOF), Alarm Indication Signal (AIS), Signal Degraded (SD), and Remote Alarm Indication (RAI). + +#### *Attributes* + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair ", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**sncPtr:** This attribute identifies the ds1SubnetworkConnectionF terminated by this managed entity. + +#### *Relationships* + +There is zero or more of these managed entities contained within a TDM interface on an FSAN NE. One of these managed entities exists for each DS1TTPF. + +### **8.47 DS1LayerNetworkDomainF** + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. Characteristic information provided in this layer is set to "DS1". + +### **8.48 DS1PMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected at a DS1CTPF for near-end DS1 path monitoring for both directions of traffic. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated DS1CTPF managed entity and a data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**CTFPPtr:** This attribute identifies the associated TPF. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**ErroredSecondsP:** If the line uses ESF framing, an ES is any second that is not a UAS that contains a LOS condition, an AIS condition, an OOF (frame alignment) condition, or one or more CRC-6 or bipolar violation errors (line code violations). If a line uses SF framing, an ES is any second with a BPV, LOS, AIS, or OOF. This parameter monitors the characteristic signal from the customer to the NE. + +**BurstyErroredSecondsP:** A BES is any second that is not a UAS that contains between 2 and 319 error events, but no LOS, AIS, or OOF condition. This parameter monitors the characteristic signal from the customer to the NE. + +**SeverelyErroredSecondsP:** An SES is any second that is not a UAS that contains an LOS condition, an AIS condition, or an OOF condition or more than 320 error events. This parameter monitors the characteristic signal from the customer to the NE. + +**UnavailableSecondsP:** UAS provides the count of seconds of unavailability. A UAS state is declared when ten consecutive SESs occur. The ten SESs are subtracted from the SES count and added to the UAS count. Subsequent seconds are accrued to the UAS count until the UAS state is cleared. The UAS state is cleared when ten consecutive non-SESs occur. When that happens, the consecutive ten non-SESs are subtracted from the UAS count. This parameter monitors the characteristic signal from the customer to the NE. + +**ErroredSecondsPFE:** If the line uses ESF framing, an ES is any second that is not a UAS that contains a LOS condition, an AIS condition, an OOF (frame alignment) condition, or one or more CRC-6 or Bipolar violation errors (line code violations). If a line uses SF framing, an ES is any second with a BPV, LOS, AIS, or OOF. This parameter monitors the characteristic signal from the network to the NE. + +**BurstyErroredSecondsPFE:** A BES is any second that is not a UAS that contains between 2 and 319 error events, but no LOS, AIS, or OOF condition. This parameter monitors the characteristic signal from the network to the NE. + +**SeverelyErroredSecondsPFE:** An SES is any second that is not a UAS that contains an LOS condition, an AIS condition, or an OOF condition or more than 320 error events. This parameter monitors the characteristic signal from the network to the NE. + +**UnavailableSecondsPFE:** UAS provides the count of seconds of unavailability. A UAS state is declared when ten consecutive SESs occur. The ten SESs are subtracted from the SES count and added to the UAS count. Subsequent seconds are accrued to the UAS count until the UAS state is cleared. The UAS state is cleared when ten consecutive non-SESs occur. When that happens, the consecutive ten non-SESs are subtracted from the UAS count. This parameter monitors the characteristic signal from the network to the NE. + +#### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of DS1CTPF. + +### 8.49 DS1SubnetworkConnectionF + +This managed entity is a type of subnetworkConnectionF and inherits all the attributes and relationships defined by subnetworkConnectionF. + +### 8.50 DS1SubnetworkF + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "DS1". + +#### *Attributes* + +**OLTPtr:** This attribute identifies the associated OLT. + +### 8.51 DS1TTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a 1544 kbit/s trail. Characteristic information provided in this layer is set to "DS1". The following alarms can be detected at this managed entity: LOF (Loss of Frame), AIS (Alarm Indication Signal), Alarm Indication Signal – Customer Installation (AIS-CI), Signal Degraded (SD), Remote Alarm Indication (RAI). + +#### *Relationships* + +There is zero or more of these managed entities contained within a network terminating FSAN NE. One of these managed entities exists for each DS1CTPF. One of these managed entities exists for each PhysicalPathTPF of type "DS1". + +### 8.52 DS3CTPF + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates a 44 736 kbit/s link connection. Characteristic information provided in this layer is set to "DS3". + +#### *Attributes* + +**DS1CTPFPointerList:** This attribute points to the DS1CTPFs within a channelized DS3 interface. + +**sncPtr:** This attribute identifies the ds3SubnetworkConnectionF terminated by this managed entity. + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for each PhysicalPathTPF of type "DS3 " and one for each DS3TTPF. Zero or one of these managed entities exists for up to 28 DS1CTPF(s) for a channelized DS3 interface. + +### 8.53 DS3LayerNetworkDomainF + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. Characteristic information provided in this layer is set to "DS3". + +#### 8.54 DS3PhysicalPortResource + +This managed entity collects key capacity metrics for NNI-side DS3 Port of the OLT. One instance of this managed entity is created automatically when the port with PhysicalPathType equal to DS3 is provisioned. The automatic creation of instances of this managed entity may be reported to the managing system. The managed entity shall be automatically deleted when the port is deleted. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PortManagedEntityId:** This attribute identifies the associated port. + +**MaxTSs:** This attribute identifies the maximum amount of timeslots assigned to the port of OLT. + +**ReservedTSs:** This attribute identifies the reserved timeslots assigned to the port of OLT. + +**AssignedTSs:** This attribute identifies the already-assigned timeslots assigned to the port of OLT. + +### *Relationships* + +One instance of this managed entity shall exist for each instance of the NNI-side OLT Port with PhysicalPathType equal to DS3. + +## **8.55 DS3PMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected at the DS3 interfaces to the OLT, ONT, or NT for near-end DS3 line and path monitoring. Instances of this managed entity are created automatically whenever performance monitoring is requested by the managing system at the associated PhysicalPathTPF managed entity and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**CTPPtr:** This attribute identifies the associated DS3CTPF. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**ErroredSecondsL:** This parameter is a count of one-second intervals containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution codes (as defined in ANSI T1.102) are excluded. + +**SeverelyErroredSecondsL:** This parameter is a count of one-second intervals containing 45 or more BPVs or EXZs and no LOS defects. BPVs that are part of the zero substitution codes (as defined in ANSI T1.102) are excluded. + +**CVCPorCVPP:** This parameter is a count of one-second intervals containing one or more CP-bit parity errors for CP parity applications or a count of one-second intervals containing one or more P-bit parity errors for M13 applications. + +**ESCPPorESPP:** This parameter is the count of one-second intervals containing the occurrence of one or more CP-bit parity errors, one or more SEF defects, or one or more AIS defects, in the case of C-bit parity applications; or the count of one-second intervals containing the occurrence of one or more P-bit parity errors, one or more SEF defects, or one or more AIS defects in the case of M13 applications. + +**SESCPPorSESPP:** This parameter is the count of one-second intervals containing the occurrence of 45 or more CP-bit parity errors, one or more SEF defects, or one or more AIS defects in the case of C-bit parity applications; or the count of one-second intervals + +containing the occurrence of 45 or more P-bit parity errors, one or more SEF defects, or one or more AIS defects in the case of M13 applications. + +**UASCPPorUASPP:** This parameter is a count of one-second unavailable intervals beginning with the onset of 10 contiguous severely errored seconds. It ends at the onset of 10 contiguous seconds with no severely errored seconds. + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the PhysicalPathTPF managed entity of type "DS3" contained in a FSAN NE. + +### **8.56 DS3SubnetworkF** + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "DS3". + +#### *Attributes* + +**OLTPtr:** This attribute identifies the associated OLT. + +### **8.57 DS3SubnetworkConnectionF** + +This managed entity is a type of subnetworkConnectionF and inherits all the attributes and relationships defined by subnetworkConnectionF. + +### **8.58 DS3TTPF** + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a 44 736 kbit/s path trail. Characteristic information provided in this layer is set to "DS3". The following alarms can be detected at this managed entity: Loss of Frame (LOF), Alarm Indication Signal (AIS), Alarm Indication Signal – Customer Installation (AIS-CI), Signal Degraded (SD), Remote Alarm Indication (RAI). + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for each DS3CTPF. One of these managed entities exists for each PhysicalPathTPF of type "DS3". + +### **8.59 E1CTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates a 2048 kbit/s link connection. Characteristic information provided in this layer is set to "E1". + +#### *Attributes* + +**sncPtr:** This attribute identifies the E1SubnetworkConnectionF terminated by this managed entity. + +#### *Relationships* + +There is zero or more of these managed entities contained within a terminating FSAN NE. One of these managed entities exists for each E1TTPF. + +### **8.60 E1LayerNetworkDomainF** + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. Characteristic information provided in this layer is set to "E1". + +## 8.61 E1PMHistoryDataF + +This is a managed entity that contains the past performance monitoring data collected at the E1CTPF for near-end E1 path monitoring for both directions of traffic. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated E1CTPF managed entity and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PhysicalPathTPFPtr:** This attribute identifies the associated TPF. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**ErroredSecondsP:** This parameter monitors the characteristic signal from the customer to the NE. + +**BurstyErroredSecondsP:** This parameter monitors the characteristic signal from the customer to the NE. + +**SeverelyErroredSecondsP:** This parameter monitors the characteristic signal from the customer to the NE. + +**UnavailableSecondsP:** UAS provides the count of seconds of unavailability. This parameter monitors the characteristic signal from the customer to the NE. + +**ErroredSecondsPFE:** This parameter monitors the characteristic signal from the network to the NE. + +**BurstyErroredSecondsPFE:** This parameter monitors the characteristic signal from the network to the NE. + +**SeverelyErroredSecondsPFE:** This parameter monitors the characteristic signal from the network to the NE. + +**UnavailableSecondsPFE:** UAS provides the count of seconds of unavailability. This parameter monitors the characteristic signal from the network to the NE. + +### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of E1CTPF. + +## 8.62 E1SubnetworkConnectionF + +This managed entity is a type of subnetworkConnectionF and inherits all the attributes and relationships defined by subnetworkConnectionF. + +## 8.63 E1SubnetworkF + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "E1". + +### *Attributes* + +**OLTPtr:** This attribute identifies the associated OLT. + +## 8.64 E1TTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a 2048 kbit/s path trail. Characteristic information provided in this layer is set to "E1". The following alarms can be detected at this managed entity: Loss of Frame (LOF), Alarm Indication Signal (AIS), Signal Degraded (SD), Remote Alarm Indication (RAI). + +### *Relationships* + +There is zero or more of these managed entities contained within a network terminating FSAN NE. One of these managed entities exists for each E1CTPF. One of these managed entities exists for each PhysicalPathTPF of type "E1". + +## 8.65 E3CTPF + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates a 34 368 kbit/s link connection. Characteristic information provided in this layer is set to "E3". + +### *Attributes* + +**E1CTPFPointerList:** This attribute points to the E1CTPFs within a channelized E3 interface. + +**sncPtr:** This attribute identifies the E3SubnetworkConnectionF terminated by this managed entity. + +### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for each E3TTPF. Zero or one of these managed entities exists for up to 16 E1CTPF(s) for a channelized E3 interface. + +## 8.66 E3LayerNetworkDomainF + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. Characteristic information provided in this layer is set to "E3". + +## 8.67 E3PMHistoryDataF + +This is a managed entity that contains the past performance monitoring data collected at the E3 interfaces to the OLT, ONT, or NT for near-end E3 line and path monitoring. Instances of this managed entity are created automatically whenever performance monitoring is requested by the managing system at the associated PhysicalPathTPF managed entity and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PhysicalPathTPFPtr:** This attribute identifies the associated PhysicalPathTPF. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the PhysicalPathTPF managed entity of type "E3" contained in a FSAN NE. + +#### **8.68 E3SubnetworkConnectionF** + +This managed entity is a type of subnetworkConnectionF and inherits all the attributes and relationships defined by subnetworkConnectionF. + +#### **8.69 E3SubnetworkF** + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "E3". + +### *Attributes* + +**OLTPtr:** This attribute identifies the associated OLT. + +#### **8.70 E3TTPF** + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a 34 368 kbit/s path trail. Characteristic information provided in this layer is set to "E3". The following alarms can be detected at this managed entity: Loss of Frame (LOF), Alarm Indication Signal (AIS), Signal Degraded (SD), Remote Alarm Indication (RAI). + +### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for each E3CTPF. One of these managed entities exists for each PhysicalPathTPF of type "E3". + +#### **8.71 EquipmentHolderF** + +This managed entity represents physical resources of the FSAN NE that are capable of holding other physical resources. Examples include slots in the ONT and bays, shelves, and slots associated with the OLT. An instance of this managed entity shall exist for each bay, shelf, and slot of the FSAN NE. Instances of this managed entity are created with FSAN NE initialization and reported by the FSAN EMS to the NMS. The managed entity supports the operational state and alarm status functions as defined in ITU-T Rec. X.731. Changes in status are reported automatically or on demand to the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**EquipmentHolderType:** This attribute indicates whether the EquipmentHolderF instance is being used to represent a bay, a shelf, or a slot. + +**EquipmentHolderAddress:** This attribute identifies the physical location of resource represented by the EquipmentHolderF instance. In the case of slot type, this address provides the slot number reading from upper left to lower right. In the case of shelf type, this address provides the shelf number from top to bottom. In the case of bay, this attribute provides the central office bay location code. + +**SlotStatus:** This attribute provides a Boolean indication as to whether or not the slot is full. This attribute only applies when the EquipmentHolderF type is slot. + +**ExpectedPlug-inTypes:** This attribute provides a list of plug-in types that are acceptable in the slot. This attribute only applies when the EquipmentHolderF type is slot. + +**SoftwareLoad:** This attribute identifies the software load (if there is any) that is currently designated as the one to be loaded to the plug-in unit whenever an automatic reload of software is required. This attribute only applies when the EquipmentHolderF type is slot. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**OperationalState:** This attribute identifies whether or not the managed entity is capable of performing its normal functions (enabled or disabled). + +#### *Relationships* + +An instance of this managed entity supported nested containment relationships matching the physical resource nested containment relationships. Identification of instances of this managed entity is related to the identification of the FSAN NE. An instance of slot type equipment holder contains an instance of plug-in when the slot status is full (=TRUE). + +### **8.72 EthernetCTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. This managed entity terminates and originates an Ethernet section link connection. This managed entity is used to indicate a loopback location in a subscriber line card in the ONT. The attribute PointDirectionality has the value "bidirectional". + +#### *Relationships* + +There is one or more of these managed entities contained within an ONT. One of these managed entities exists for each PhysicalPathTPF of Type "Ethernet" and for each EthernetTTPF. + +### **8.73 EthernetPhysicalPortResource** + +This managed entity collects key capacity metrics for NNI-side Ethernet Port of the OLT. One instance of this managed entity is created automatically when the port with PhysicalPathType equal to Ethernet is provisioned. The automatic creation of instances of this managed entity may be reported to the managing system. The managed entity shall be automatically deleted when the port is deleted. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PortManagedEntityId:** This attribute identifies the associated port. + +**MaxVLANtags:** This attribute identifies the maximum amount of VLAN tags assigned to the port of OLT. + +**ReservedVLANtags:** This attribute identifies the reserved VLAN tags assigned to the port of OLT. + +**AssignedVLANtags:** This attribute identifies the already-assigned VLAN tags assigned to the port of OLT. + +**MaxBW:** This attribute identifies the maximum amount of bandwidth assigned to the port of OLT. + +**ReservedBW:** This attribute identifies the reserved bandwidth assigned to the port of OLT. + +**AssignedBW:** This attribute identifies the already-assigned bandwidth assigned to the port of OLT. + +#### *Relationships* + +One instance of this managed entity shall exist for each instance of the NNI-side OLT port with PhysicalPathType equal to Ethernet. + +### **8.74 EthernetPMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected at Ethernet interfaces to the ONT. Instances of this managed entity are created automatically whenever performance monitoring is requested by a client application or NMS at the associated EthernetCTPF managed entity and a data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**TPPointer:** This attribute identifies the associated TP. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +#### **Transmission side** + +**SingleCollisionFrameCount:** A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. + +**MultipleCollisionFramesCount:** A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. + +**SQECOUNT:** A count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface. + +**DeferredTransmissionCount:** A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions. + +**LateCollisionCount:** The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. + +**ExcessiveCollisionCount:** A count of frames for which transmission on a particular interface fails due to excessive collisions. + +**InternalMACTransmitErrorCount:** A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. + +**CarrierSenseErrorCount:** The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. + +**BufferOverflows:** A count of the number of times that the buffer overflows. + +#### **Receiving side** + +**AlignmentErrorCount:** A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. + +**FrameTooLong:** A count of frames received on a particular interface that exceed the maximum permitted frame size. The count is incremented when the frameTooLong status is returned by the MAC service to the LLC. + +**FCSErrors:** A count of frames received on a particular interface that are an integral number of octets in length but do not pass the Frame Check Sequence (FCS) check. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the Link Layer Control (LLC) or other MAC user. Received frames for which multiple error conditions obtain are counted exclusively according to the error status presented to the LLC. + +**InternalMACReceiveErrorCount:** A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. + +**BufferOverflows:** A count of the number of times that the buffer overflows. + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the PhysicalPathTPF managed entity of type "Ethernet". + +### **8.75 EthernetProfileF** + +This managed entity groups together attributes for an Ethernet physical interface to the ONT. Instances of this managed entity are created and deleted by request of the managing system or operator. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance for all applications notified of its creation. + +**DuplexInd:** This attribute indicates whether full-duplex (=TRUE) or half-duplex mode (=FALSE) is employed. + +**AutoDetectionInd:** This Boolean attribute identifies whether or not data rate auto-detection is enabled. + +**DataRate:** This attribute provides the data rate for the Ethernet connection. The valid values are 10 Mbit/s or 100 Mbit/s. + +**MaxFrameSize:** This attribute denotes the maximum allowed frame size to be transmitted across this interface.4 + +**DTEorDCEInd:** This attribute indicates whether the Ethernet interface wiring is DTE or DCE.5 + +**BridgedorIPInd:** This attribute indicates whether the Ethernet interface is bridged or derived from an IP router function. + +#### *Relationships* + +This managed entity may be associated to zero or more instances of the Physical Path TP managed entity contained in an ONT. + +--- + +4 Currently, this value is fixed at 1518. + +5 This attribute is maintained for inventory management and is not settable. + +## 8.76 EthernetTTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. This managed entity terminates and originates an Ethernet section trail. The attribute PointDirectionality has the value "bidirectional". + +### *Relationships* + +There is one or more of these managed entities contained within an ONT. One of these managed entities exists for each EthernetCTPF managed entity. + +## 8.77 filterProfileF + +This "support" managed entity provides a filter construct upon which management actions are based. Instances of this managed entity are created and deleted by request of the managing system. The managed entity supports the operational state and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**OperationalState:** This attribute identifies whether or not the managed entity is capable of performing its normal functions (enabled or disabled). + +**AdministrativeState:** This attribute is used to inhibit (lock) and allow (unlock) the use of this profile entity. + +**FilterConstructList:** This attribute provides a listing of the logical constraints describing the filter. + +### *Relationships* + +One instance of this managed entity shall exist for each logF managed entity (to describe situations under which information is added as records to the logF). Filter profiles can also be associated with the forwarding of real-time information to the managing system. + +## 8.78 LESServiceProfileF + +This managed entity is used to organize data that describes voice grade Loop Emulation Service functions of the FSAN NE associated with AAL2 interworking. Instances of this managed entity are created and deleted by request of the managing system or operator. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**ELCPInd:** This Boolean attribute indicates whether or not Emulated Loop Control Protocol is in use. + +**POTSSignalling:** This attribute selects which signalling format should be used for POTS service. Valid values include but are not limited to PSTN, CAS, CCS, and other. + +**BRISignalling:** This attribute selects which signalling format should be used for basic rate ISDN. Valid values include but are not limited to DSS1, CCS, and other. + +**MaxNumCIDs:** This attribute specifies the maximum number of channels within the VCC that can be active. + +**MaxPacketLength:** This attribute specifies the maximum packet length. + +**Channel&SSCSParameterPointerList:** This attribute correlates channel Ids with SSCS parameter values. + +NOTE – SSCS parameter sets are yet to be defined. + +#### *Relationships* + +This managed entity may be associated to zero or more instances of an interworking vcCTPF terminating AAL2. + +### **8.79 layerNetworkDomainF** + +The layer network domain is defined to support the requirement for independent layer management. Each layer is concerned with the generation and transfer of characteristic information. The layer network domain managed entity represents the part of the layer that is available to an operator managing system. It contains only managed entities from a single layer. The layer domain includes all topological aspects of the transport network layer. It is assumed that a layerNetworkDomainF contains one and only one subnetworkF, which can be further decomposed. There may be several layer network domains within a single network. It is assumed that the layer network domain is created automatically at the installation of the superior networkF managed entity. The automatic creation of instances of this managed entity shall be reported to the operator managing system. The managing system may subsequently create and delete other instances of the layer network domain provided there are no dependent entities. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SignalIdentification:** This attribute represents the characteristic information of the layer network domain. + +**SystemTitle:** This attribute provides an operator-provided system name to identify the network. + +**UserLabel:** This attribute allows a manager to represent additional information about the layer network domain. + +#### *Relationships* + +A layerNetworkDomainF is delineated by zero or more CTPF(s). A layerNetworkDomainF groups zero or more trailF(s). A layerNetworkDomainF is partitioned into one or more subnetworkF(s). + +### **8.80 linkConnectionF** + +This managed entity is used to describe the transport entity transferring information between two CTPFs. A link connection can be a component of a trail. A sequence of one or more link connections and subnetwork connections may be pieced together to form a trail. A linkConnectionF cannot be created between a composite subnetwork and one of its component subnetworks. An instance of this managed entity is created automatically with the provisioning of information transfer in the network layer to which this link connection belongs. The managed entity can only be deleted when the provisioned bandwidth is taken out of service. The managed entity supports availability status and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**AvailabilityStatus:** This attribute indicates whether or not a managed entity is capable of performing its task. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +**ACTPPtr:** This attribute is used to identify one end of the link connection. + +**ZCTPPtr:** This attribute is used to identify the other end of the link connection. + +**Directionality:** This attribute indicates whether or not a link is "unidirectional" or "bidirectional". + +**RecoverableInd:** This attribute is used to identify the connection as recoverable (protected) or not. + +### *Relationships* + +This managed entity is established between two CTPFs. + +## **8.81 logF** + +This managed entity is used to store incoming event reports. It is used to group multiple instances of the same event type to form a logF. Examples include alarm logs, state change logs, attribute value change logs, managed entity creation logs, and managed entity deletion logs. This managed entity includes attributes that allow the FSAN upstream system or operator to control the behaviour of the logF. Instances of this managed entity are created automatically by the FSAN EMS upon initialization. The managed entity supports operational state and administrative state and alarm status functions as defined in ITU-T Rec. X.731. Changes in state or status are reported automatically or on demand to the managing system. In case of Threshold Crossing, an alarm is generated. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the logging function of this managed entity in the FSAN EMS. + +**OperationalState:** This attribute indicates whether or not a managed entity is capable of performing its task, in this case logging. Valid values are "enabled" or "disabled". + +**AvailabilityStatus:** This attribute provides more information on whether or not the managed entity is capable of performing its normal functions. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**FilterProfileId:** This attribute points to a filter object that encapsulates constraints used by this managed entity in determining whether or not to logF a particular event instance. + +**EventType:** This attribute identifies the event type recorded in the logF instance. + +**LogFullAction:** This attribute identifies the action the logF recording should take when the log is full. Valid values are "stop" and "wraparound". + +**CapacityThreshold:** This attribute identifies the log size, after crossing an alarm is generated. + +**MaxNumRecords:** This attribute identifies the maximum number of records that can be stored in the log. + +**CurrentLogSize:** This attribute identifies the current number of records stored in the log. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +#### *Relationships* + +Instances of this managed entity are used to contain (multiple) instances of alarmLogRecordFs, managed entity creation records, managed entity deletion records, state change records, and attributeValueChangeRecordFs. + +### **8.82 logicalLinkEndF** + +A logical link end contains CTPFs for the purposes of representing topology. It represents the end of a logicalLinkF or logicalMTPLinkF. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SignalIdentification:** This attribute identifies the characteristic information of the layer to which this managed entity belongs. + +**LinkFPtr:** This attribute identifies the logicalLinkF or logicalMTPLinkF associated with this end point. + +**LinkEndDirectionality:** This attribute specifies whether this managed entity contains sink, source, bidirectional or undefined (combination of the above three) connection termination points. + +**CTPList:** This attribute lists the CTPFs that are contained by this managed entity. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +#### *Relationships* + +Each logicalLinkF or logicalMTPLinkF has two or more logicalLinkEndF(s). + +### **8.83 logicalLinkF** + +A logical link is administratively composed of link connections or bandwidth that may be provided by one or more topological links or other logical links. This entity may be explicitly created by the network management system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SignalIdentification:** This attribute identifies the characteristic information of the layer to which this managed entity belongs. + +**LinkDirectionality:** This attribute specifies whether this managed entity contains unidirectional, bidirectional or undefined (combination of the above two) link connections. + +**Aend:** This pointer attribute identifies the link end at one extremity. + +**Zend:** This pointer attribute identifies the link end or access group at the other extremity. + +**LinkConnectionList:** This attribute lists the linkConnectionFs that are contained by this managed entity. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +#### *Relationships* + +A logicalLinkF is a group of link connections sharing two extremities. One logicalLinkF has a relationship with the two managed entities that it is linking. A logicalLinkF cannot exist without the subnetworkF being identified. + +### **8.84 logicalMTPLinkF** + +A logicalMTPLinkF is administratively composed of link connections or bandwidth that may be provided by one or more topological links or other logical links where the links share a common Aend link end point. This entity may be explicitly created by the network management system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SignalIdentification:** This attribute identifies the characteristic information of the layer to which this managed entity belongs. + +**LinkDirectionality:** This attribute specifies whether this managed entity contains unidirectional, bidirectional or undefined (combination of the above two) link connections. + +**MTPLinkDirectionality:** This attribute indicates whether or not a logicalMTPLink is "downstream" (from Aend), "upstream" (to Aend), or "bidirectional". + +**Aend:** This pointer attribute identifies the shared link end. + +**ZendList:** This pointer attribute identifies the list of terminating link ends or access groups. + +**LinkConnectionList:** This attribute lists the linkConnectionFs that are contained by this managed entity. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +#### *Relationships* + +A logicalMTPLinkF is a group of link connections sharing one extremity. One logicalMTPLinkF has a relationship with the managed entities that it is linking. A logicalMTPLinkF cannot exist without the subnetworkF being identified. + +### **8.85 MACBridgeConfigurationDataF** + +This managed entity is used to organize and record data that is associated with bridged LAN configurations. Some of the data is volatile. Instances of this managed entity are created automatically whenever an interworking vcCTPF is established for AAL5 on the ONT for a bridged LAN Ethernet PhysicalPathTPF. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**BridgeMACAddress:** The MAC address used by the bridge. + +**BridgePriority:** This attribute denotes the priority of the bridge and is positive integer-valued.6 + +--- + +6 The range of values for this item is 0 to 65535 with default value 32768. + +**DesignatedRoot:** This attribute provides the bridge identifier for the root of the spanning tree. + +**RootPathCost:** This attribute provides the cost of the best path to the root as seen from the bridge. + +**BridgePortCount:** This attribute counts the number of existing ports controlled by this bridge. + +**RootPortNum:** This attribute provides the port number that has the lowest cost from the bridge to the root bridge. + +**TPManagedEntityIdPortList:** This attribute identifies list of termination points for each of the ports controlled by the bridge and their association to the appropriate port number. + +#### *Relationships* + +This managed entity is associated with one instance of a PhysicalPathTPF of type "Ethernet". + +### **8.86 MACBridgeF** + +This managed entity organizes the data associated with the configuration of a bridged Ethernet subscriber interface involving a learning function. Instances of this managed entity are created automatically whenever an interworking vcCTPF is established for AAL5 on the ONT for a learning bridged LAN Ethernet PhysicalPathTPF. The managed entity supports the operational state and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MACBridgeConfigurationDataPtr:** This attribute identifies the associated configuration data. + +**MACBridgeServiceProfilePtr:** This attribute identifies the associated service profile. + +**InterworkingVcCTPPtr:** This attribute identifies the associated interworking vcCTP. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**OperationalState:** This attribute identifies whether or not the managed entity is capable of performing its normal functions (enabled or disabled). + +#### *Relationships* + +There is zero or more of these managed entities contained within LAN subscriber card on an FSAN ONT. One or more of these managed entities exists for each EthernetTTPF, EthernetCTPF. Zero or more of these managed entities exists for each EthernetCTPF and EthernetTTPF. + +### **8.87 MACBridgePMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected at a MAC bridging function supporting Ethernet interfaces on the ONT. Instances of this managed entity are created automatically whenever performance monitoring is requested by a client application or NMS at the associated BridgedLANCTPF managed entity and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**TPPointer:** This attribute identifies the associated TP. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**BridgeLearningEntryDiscardCount:** This attribute records the number of forwarding database entries that have been or would have been learned but were discarded or replaced due to lack of space in the database table. + +### *Relationships* + +Zero or more instances of this managed entity may be associated with an instance of BridgedLANCTPF. + +## **8.88 MACBridgePortF** + +This managed entity is used to organize and record data that is associated with a bridge port. Some of the data is volatile. Instances of this managed entity are created automatically whenever an interworking vcCTPF is established for AAL5 on the ONT for a bridged LAN Ethernet PhysicalPathTPF. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**BridgeIdPointer:** This attribute identifies the MAC bridge controlling the port. + +**PortNum:** This attribute provides the port number. + +**PortPriority:** This attribute denotes the priority of the port. + +**PortPathCost:** This attribute provides the cost contribution of the port to the path cost towards the spanning tree root bridge. + +**PortSpanInd:** This Boolean attribute indicates whether or not spanning tree algorithms are used by the bridge port. + +**PortState:** This attribute provides status information on the port. Valid values include "disabled", "blocking", "listening", "learning", "forwarding", and "inoperable". + +**DesignatedBridgeRootCostPort:** This attribute provides the Designated Root, Designated Cost, Designated Bridge, and Designated Port outputs of "Read port parameters" operation defined in 14.8.2.1 of IEEE 802.1D, i.e.: + +- bridge identifier of the designated bridge for the port's segment; +- bridge identifier of the root transmitted by the designated bridge for the segment; +- port number of the designated port on the designated bridge considered to be part of this port's segment; +- path cost contribution of the designated port to this port's segment. + +**VcCTPManagedEntityId\_LANPhysicalPathTPManagedEntityId:** This attribute identifies either the virtual channel connection termination point or the LAN Physical Path Trail Termination Point associated with this port. + +**MACFilterTable:** This attribute lists the destination MAC addresses, whether they are learned or statically assigned, whether packets having them as destination addresses are filtered or forwarded, and their age. + +**BridgeTable:** This attribute lists for every MAC address of a terminal served by the bridge port the destination MAC addresses, whether they are learned or statically assigned, whether they are permanent or non-permanent, and their age. + +#### *Relationships* + +One or more instances of this managed entity are associated with an instance of the managed entity EthernetTTPF associated with a MAC bridging function in the ONT. + +### **8.89 MACBridgePortPMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected at the port bridging function for Ethernet interfaces on the ONT. Instances of this managed entity are created automatically whenever performance monitoring is requested by a client application or NMS at the associated BridgedLANCTPF managed entity and a data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**TPPPointer:** This attribute identifies the associated TP. + +**PortNum:** This attribute identifies the port at which monitoring takes place. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +#### **Transmission side** + +**ForwardedFrameCount:** A count of successfully transmitted frames on a particular port. + +**DelayExceededDiscardCount:** A count of frames discarded on a particular port because transmission is delayed. + +**MTUExceededDiscardCount:** A count of frames discarded on a particular port because MTU is exceeded. + +#### **Receiving side** + +**ReceivedFrameCount:** A count of frames received at the port. + +**ReceivedAndDiscardedCount:** A count of frames received on a particular port that have been discarded due to errors. + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the BridgedLANCTPF managed entity for each port that the MAC Bridge is controlling. + +### **8.90 MACBridgeServiceProfileF** + +This managed entity is used to organize data that affects all ports on a MAC Bridge at a bridge LAN Ethernet UNI interface on the ONT. Instances of this managed entity are created and deleted by request of the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance for all applications notified of its creation. + +**SpanningTreeInd:** This Boolean attribute indicates whether or not a spanning tree algorithm is enabled. The value TRUE means enabled. + +**LearningInd:** This Boolean attribute indicates whether or not the learning functions of the bridge are enabled. The value TRUE means enabled. + +**MaxAge:** This attribute indicates the maximum age (in seconds) for an entry in the spanning tree listing. It indicates the maximum age in seconds of received protocol information before it is discarded. + +**HelloTime:** This attribute provides the time interval (in hundredths of a second) between hello packets. It is the time interval, in hundredths of a second, that a bridge advertises its presence while as a root or attempting to become a root. + +**ForwardDelay:** This attribute gives the time (in hundredths of a second) that the bridge on the Ethernet card in the ONT (as a member of the community of all bridges in the Bridged Local Area Network) retains a packet before forwarding it. It is the parameter used as the timeout value for ageing Filtering Database dynamic entries following changes in active topology. This is equivalent to the value in hundredths of a second that the bridge uses for Forward Delay when the bridge acts as the root. + +### *Relationships* + +This managed entity may be associated with zero or one instance of a PhysicalPathTPF of type "Ethernet". + +## **8.91 managedEntityCreationLogRecordF** + +This managed entity is used to represent logged information that resulted from managed entity creation events. An instance of this managed entity is created automatically by the FSAN NE upon creation of other managed entities in the FSAN NE. Instances of this managed entity can be deleted by the FSAN NE or by request of the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**LoggingTime:** This attribute identifies the time at which the record was entered into the log. + +**ManagedEntityAssertion:** This attribute identifies the type and instance Id of the managed entity that was created. + +### *Relationships* + +Multiple instances of this managed entity may be contained in an instance of the logF managed entity. + +## **8.92 managedEntityDeletionLogRecordF** + +This managed entity is used to represent logged information that resulted from managed entity deletion events. An instance of this managed entity is created automatically by the FSAN NE upon deletion of other managed entities in the FSAN NE. Instances of this managed entity can be deleted by the FSAN NE or at the request of the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**LoggingTime:** This attribute identifies the time at which the record was entered into the log. + +**ManagedEntityAssertion:** This attribute identifies the type and instance Id of the managed entity that was deleted. + +### *Relationships* + +Multiple instances of this managed entity may be contained in an instance of the logF managed entity. + +## **8.93 MLTTestResultsF** + +This managed entity provides the results of conducting Metallic Loop Testing on the twisted pair connected to any RJ-11 port of the ONT. Instances of this managed entity are created by the EMS when an operator or OMS system invokes this test. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**VoiceCTPPtr:** This attribute identifies the voice channel tested. + +**HazardousPotential:** This Boolean attribute indicates whether or not the MLT test results have been compromised by a detected dangerously high voltage condition. + +**ForeignElectroMotiveForce:** This attribute reports the results of checking for excess voltage on the drop. It either provides indication of a pass or a sequence of measurement values in units of volts for acVoltageTipToGround, acVoltageRingToGround, dcVoltageTipToGround, dcVoltageRingToGround. + +**ResistiveFaults:** This attribute reports the results of checking for dc resistance faults across T-R, T-G, and R-G. It either provides indication of a pass or a sequence of items the first of which indicates whether a two- or three-terminal measurement was conducted followed by three measurement values in ohms for dcResistanceTipToRing, dcResistanceTipToGround, and dcResistanceRingToGround. + +**ReceiverOffHook:** This attribute reports the results of testing to distinguish between a tip-ring resistive fault and an off-hook condition. It either provides indication of a pass or a sequence of measurements in ohms for dcResistance1TipToRing and dcResistance2TipToRing. + +**Ringer:** This attribute reports the results of detection of appropriate ringer terminations on the customer's line. It either provides indication of pass or a sequence of measurements in ohms for acImpedanceTipToRing, acImpedanceTipToGround, acImpedanceRingToGround. + +**NetworkTermination1dcSignatureTest:** This attribute reports the results of testing for the presence of a Network Termination 1. The NT1 is CPE that terminates an ISDN Basic Access Digital Subscriber Line. It either provides indication of pass or a sequence of measurements in volts for dcVoltage1TipToRing and dcVoltage2TipToRing. + +**TestCompletionTimeStamp:** This attribute indicates when all the MLT testing was completed. + +### *Relationships* + +Zero or more instance of this managed entity shall exist for each VoiceCTPF. + +## 8.94 msCTPF + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. This managed entity terminates and originates a multiplex section link connection. + +### *Attributes* + +**StmLevel:** This attribute provides the corresponding STM Level (e.g., STM1, STM4, ...). + +### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exists for each rsTTPF and for each msTTPF. + +## 8.95 msTTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a multiplex section trail. The following alarms can be detected at this managed entity: Alarm Indication Signal (AIS), Far-End Receive Failure (FERF), Signal Degraded (SD) and Excessive Bit Error Rate (EBER). + +### *Attributes* + +**StmLevel:** This attribute provides the corresponding STM Level (e.g., STM1, STM4, ...). + +### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exist for each msCTPF and for each au4CTPF or for up to 3 au3CTPF. + +## 8.96 NEFSAN + +This managed entity is used to represent equipment that is found as part of the FSAN architecture and conforms to the definition as provided in ITU-T Rec. G.983.2. An instance of this managed entity is created when the equipment is initialized. The automatic creation of instances of this managed entity shall be reported to the managing system. The managed entity can only be deleted when the equipment is taken out of service and only by request of the managing system. The managed entity supports the operational state and administrative state and alarm status functions as defined in ITU-T Rec. X.731. Changes in state or status are reported automatically or on demand to the managing system. The managed entity also reports on appropriate equipment alarms. This managed entity is defined for the purposes of grouping together all common attributes of an FSAN NE, but only instances of specific FSAN nodes (OLT, ONT, ONU, NT) shall be implemented. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**OperationalState:** This attribute indicates whether or not a managed entity is capable of performing its task. Valid values are "enabled" and "disabled". + +**ModelCode:** This attribute stores the product model code of the Network Element. The product model code is the manufacturer's model identification information. It is vendor-provided information that the vendor uses to distinguish the network element among a family of products. This attribute is useful for OSSs performing equipment discovery and inventory processes. + +**ExternalTime:** This attribute provides the time-of-day system time. The attribute functions as a reference for all time stamp activities in the NEFSAN. + +**LocationName:** This attribute identifies the specific or general location of the NEFSAN. + +**SupplierName:** This attribute identifies the supplier of the NEFSAN. + +**Version:** This attribute identifies the version of the NEFSAN. + +**SerialNumber:** This attribute provides the serial number for the NEFSAN used for inventory management. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an AlarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**ThresholdDataPtr:** This attribute provides a pointer to an instance of the ThresholdDataF object that provides threshold values for monitored parameters to be used to generate Threshold Crossing Alert notifications whenever a monitored parameter crosses its associated threshold value for this managed entity. + +**SupportedByManagedEntityList:** This attribute provides pointers to instances of managed entities that affect the performance and/or state of this managed entity. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +#### *Relationships* + +One instance of the NEFSAN managed entity would exist for each node in the FSAN architecture being managed. The NEFSAN contains zero or more EquipmentHolderF managed entities indicating "shelves". These shelves, in turn, contain zero or more EquipmentHolderF managed entities indicating slots. + +### **8.97 networkF** + +The networkF managed entity groups all the managed entities visible over the NMS-EMS interface. The managed entities grouped under networkF may span several transport layers (e.g., the VP and VC layers). This managed entity is automatically created when the FSAN network is initialized. It is not created or deleted by the managing system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SystemTitle:** This attribute provides an operator-provided system name to identify the network. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +#### *Relationships* + +The networkF managed entity is made up of a set of transport and other managed entities (e.g., logF). This managed entity is a type of layerNetworkDomainF and inherits all the attributes and relationships defined by layerNetworkDomainF. + +## 8.98 NT + +This managed entity is one type of NEFSAN, and inherits all of the properties and relationships of this superclass. Instances can be created and deleted by request of the FSAN managing system. Additionally, the NT possesses an attribute identifying the ONU from which it is hosted. + +### *Attributes* + +**upstreamNEFSAN:** This attribute identifies the FSAN ONU node hosting the NT equipment node. + +### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the ONU. + +## 8.99 OLT + +This managed entity is one type of NEFSAN, and inherits all of the properties and relationships of this superclass. Additionally, the OLT possesses an extra attribute listing the FSAN ONTs and ONUs hosted by the OLT instance. + +### *Attributes* + +**subtendingNEFSANList:** This attribute identifies the FSAN ONT and FSAN ONU instances for which the OLT acts as a head-end. + +**DCNAddress:** This attribute identifies the address (normally IP address) for the OLT on the Data Communications Network of the SMS. + +**AdministrationDomain:** This attribute identifies the name of the domain. + +## 8.100 OLTResource + +This managed entity collects key capacity metrics for the OLT system. One instance of this managed entity is created automatically when the OLT is initialized. The automatic creation of an instance of this managed entity may be reported to the managing system. The managed entity shall be automatically deleted when the OLT is taken out of service. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**OLTManagedEntityId:** This attribute identifies the associated system. + +**UnassignedSlotList:** This attribute lists the slot number within the OLT that has not been assigned yet. + +**AssignedSlotList:** This attribute lists the slot number within the OLT that has already been assigned. + +### *Relationships* + +One instance of this managed entity shall exist for each instance of the OLT. + +## 8.101 ONT + +This managed entity is one type of NEFSAN, and inherits all of the properties and relationships of this superclass. Instances can be created and deleted by request of the FSAN managing system. Additionally, the ONT possesses an attribute identifying the OLT from which it is hosted. + +### *Attributes* + +**upstreamNEFSAN:** This attribute identifies the FSAN OLT node hosting the ONT equipment node. + +**SRIndicator:** This Boolean attribute indicates the capability of status reporting. The value true means that the status reporting is available for all the T-CONT buffers which are associated with the APON-side PhysicalPathTPF of each ONT/ONU. + +**MaximumNumberOfTCONT:** This attribute identifies the maximum number of T-CONT that the APON-side PhysicalPathTPF of each ONT/ONU is capable of. It ranges from 1 to 252. + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the OLT. + +### **8.102 ONU** + +This managed entity is one type of NEFSAN, and inherits all of the properties and relationships of this superclass. Instances can be created and deleted by request of the FSAN managing system. Additionally, the ONU possesses an attribute identifying the OLT from which it is hosted. + +#### *Attributes* + +**upstreamNEFSAN:** This attribute identifies the FSAN OLT node hosting the ONU equipment node. + +**SRIndicator:** This Boolean attribute indicates the capability of status reporting. The value true means that the status reporting is available for all the T-CONT buffers which are associated with the APON-side PhysicalPathTPF of each ONT/ONU. + +**MaximumNumberOfTCONT:** This attribute identifies the maximum number of T-CONT that the APON-side PhysicalPathTPF of each ONT/ONU is capable of. It ranges from 1 to 252. + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the OLT. + +### **8.103 PhysicalPathTPF** + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. This managed entity is used to represent the points in the FSAN NE where physical paths terminate and physical level functions (e.g., path overhead functions) are performed. The operational state reflects the perceived ability to generate and/or receive a valid signal. An instance of this managed entity is created automatically by the FSAN NE for each physical path terminating on the FSAN NE or by request of the managing system. The following alarms can be detected at this managed entity: Loss of Signal (LOS), Transmitter failure (detected by Laser Bias High, Laser Power Low, Laser Power High) and Physical Equipment Error (PEEi) specifically for PhysicalPathTPs. The managed entity supports the administrative and operational state and alarm status functions as defined in ITU-T Rec. X.731. Changes in state and status are reported automatically or on demand to the managing system. Although this managed entity is a type of TTPF, UpstreamConnectivityPointer and DownstreamConnectivityPointer will not be used. Instead, ConnectivityPtrList is used, because this managed entity models point-to-multipoint connectivity. + +#### *Attributes* + +**PhysicalPathType:** This attribute identifies the physical path type terminated at the PhysicalPathTP managed entity instance. Choices include but are not limited to DS1, DS3, OC-3c, STS-3c, Ethernet, STS-1, cellBased, E1, E3, and APON. + +**ATMBearerInd:** This attribute indicates whether or not the interface designated by the managed entity is a bearer for ATM traffic. + +**OpticalReach:** This attribute indicates the length the optical signal may travel before requiring termination or regeneration if the physical path is optical. + +**OpticalWaveLengthArray:** This attribute specifies the optical wavelengths and directionality used by each optical physicalPathTTPF managed entity. + +**PortId:** This attribute identifies the port on the line card or equipment where the physical path terminates. + +**FramingFormat:** This attribute provides the physical framing format associated with the physical path being terminated. + +**ConnectivityPtrList:** This attribute points to instance(s) of the far-end PhysicalPathTTPF corresponding to this instance of the managed entity (either upstream or downstream). For example, in case that this managed entity resides in OLT, this attribute points to the corresponding PhysicalPathTTPFs that reside in ONTs/ONUs. + +**ThresholdDataPtr:** This attribute provides a pointer to an instance of the ThresholdDataF object that provides threshold values for monitored parameters to be used to generate Threshold Crossing Alert notifications whenever a monitored parameter crosses its associated threshold value. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +**InterfaceSpeed:** This attribute represents the physically available bandwidth at the interface. + +#### *Relationships* + +Instances of this managed entity shall be associated with an instance of the pluginUnitF managed entity. + +### **8.104 PhysicalPONPortF** + +This managed entity represents the physical port of Passive Optical Network (PON) equipments at the PON side. This managed entity is derived from physicalPortF and inherits all the attributes and relationships of its super class. + +#### *Attributes* + +**OpticalReach:** This attribute indicates the length the optical signal may travel before requiring termination or regeneration. + +**OpticalWavelengthArray:** This attribute specifies the optical wavelengths and their directionality for WDM based technologies. When single wavelength technology is applied, just one element is listed in this attribute. + +#### *Relationships* + +Zero or more instances of this managed entity can be contained within a plugInUnitF or NEFSAN in case of integrated ONT/ONU. + +### **8.105 PhysicalPortF** + +This managed entity represents the characteristics of physical termination of network equipments. This managed entity is a collection of common attributes of physical ports, and it is defined for inheritance. + +## *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. When the port is locked, all the logical entities supported by this physical port will not be available, unless this attribute is set to "unlocked". + +**SupportedTPList:** This attribute is the list of the lowest server trail termination points (TTPs) supported by this physical port, such as PhysicalPathTPF. + +**PhysicalPortSignalRateAndMappingList:** This attribute identifies the signal rate associated with an equipment port (e.g., port=0, rate=stm1) and its payload mapping (e.g., au3 or au4). The signal rate and payload mapping is provisionable. For example, a port with signal rate stm4 may have a payload mapping of au4-4. Another possible mapping of this rate is a sequence of four individual au4 (i.e., au4, au4, au4, au4) or a sequence of mixed au3 and au4 (e.g., au3, au3, au3, au4, au4, au3, au3, au3). This attribute supports two choices depending on whether the signal may be sent with the same rate in both directions, or depending on the direction. It is also possible to support only one direction for signal transfer, which is a special case of different rates in the two directions. In addition, if the port terminates an optical signal, different rates may be supported on different wavelengths. + +**ConnectorType:** This attribute describes the connector type used for this port. The value of this attribute can be one of the following: Fibre Connector (FC), Lucent Connector (LC), Subscriber Connector (SC), etc. + +**PortDirectionality:** This attribute indicates the capability of the port to support the directionality for data transfer. The value of this attribute may be one of the following: one way in, one way out, or two-way. The port mapping list shall be consistent with the value of this attribute. For example, if the directionality is one way out, "uniform" choice in the port mapping list is not a valid option. + +**Reach:** This attribute indicates the length a signal may travel before requiring termination or regeneration. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +## *Relationships* + +Zero or more instances of this managed entity or its derived managed entities can be contained within a plugInUnitF or NEFSAN in case of integrated ONT/ONU. + +### **8.106 pluginUnitF** + +This managed entity is used to represent equipment that is inserted (plugged into) and removed from slots of the FSAN NE. The FSAN NE creates an instance of this managed entity automatically when a plug-in unit is inserted into the FSAN NE slot. Instances can also be created and deleted at the request of the managing system. The managed entity supports the operational state and administrative state and alarm status functions as defined in ITU-T Rec. X.731. Changes in state or status are reported automatically or on demand to the managing system. The managed entity reports on associated equipment alarms. + +## *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by the plug-in unit. + +**AvailabilityStatus:** This attribute is used to further describe the state of the plug-in managed entity. + +**OperationalState:** This attribute indicates whether or not a managed entity is capable of performing its task. Valid values are "enabled", "disabled", or "unknown". + +**ModelCode:** This attribute stores the product model code of the Network Element. The product model code is the manufacturer's model identification information. It is vendor-provided information that the vendor uses to distinguish the network element among a family of products. This attribute is useful for OSSs performing equipment discovery and inventory processes. + +**SupplierName:** This attribute identifies the supplier of the plug-in unit. + +**Version:** This attribute identifies the version of the plug-in. + +**SerialNumber:** This attribute provides the serial number for the plug-in unit used for inventory management. + +**PortCount:** This attribute indicates the number of ports on the plug-in. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an AlarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +### *Relationships* + +An instance of this managed entity is associated with at least one instance of equipmentHolderF representing the slot that the plug-in occupies. + +## **8.107 PriorityQueue** + +This managed entity specifies the priority queue in the ONT that is used for the vpCTPF. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**QueueConfigurationOption:** This attribute identifies the buffer-partitioning policy. One value means that all the queues share one buffer size of Maximum Queue Size and the other value means that each queue uses its individual buffer size of Maximum Queue Size. + +**MaximumQueueSize:** This attribute specifies the maximum size of the queue. + +**AllocatedQueueSize:** This attribute identifies the allocated size of this queue. + +**DCsCounterResetInterval:** This attribute represents the interval in milliseconds that the counter for discarded cells on this queue due to buffer overflow reset itself. + +**DCsThreshold:** The threshold for the number of cells discarded on this queue due to buffer overflow. + +**TrafficSchedulerPtr:** This attribute points to the Traffic Scheduler that is directly associated with this priority queue. + +**PriorityWeight:** This attribute represents priority for HOL scheduling or the weight for WRR scheduling. This value is used by Traffic Scheduler pointed by TrafficSchedulerPtr. + +If the indicated pointer has Policy = HOL, then this value is interpreted as a priority. If the indicated pointer has Policy = WRR, then this value is interpreted as a weight. + +#### *Relationships* + +This managed entity can be associated with TrafficScheduler. + +### **8.108 rsCTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates a regenerator section link connection. + +#### *Attributes* + +**StmLevel:** This attribute provides the corresponding STM Level (e.g., STM1, STM4 ...). + +#### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities exist for each rsTTPF. + +### **8.109 rsTTPF** + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a regenerator section trail. The following alarms can be detected at this managed entity: LOS of Frame (LOF), Signal Degraded (SD) and Excessive Bit Error Rate (EBER). + +#### *Attributes* + +**StmLevel:** This attribute provides the corresponding STM Level (e.g., STM1, STM4 ...). + +#### *Relationships* + +There is zero or more of these managed entities contained within any FSAN NE. One of these managed entities exist for each PhysicalPathTPF of Type "SDH" and one for each rsCTPF and each msCTPF. + +### **8.110 SSCSPParameterProfile1F** + +These are managed entity groups default values for Service Specific Convergence Sublayer parameters for channels carried in an AAL2 VCC that provide control and management plane traffic. These parameters are defined in ITU-T Rec. I.366.1. Instances of this managed entity are created and deleted at the request of the NMS or Operators. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SegmentLength:** This attribute provides the length of segment for the Segmentation and Reassembly Service Specific Convergence sublayer. It ranges from 0 to the maximum value provided by MaxCPS\_SDULen attribute. + +**RASTimer:** This attribute provides the reassembly time (in seconds) of the Segmentation and Reassembly Service Specific Convergence sublayer for ITU-T Rec. I.366.1. + +**MaxSSSARSDULen:** This attribute provides the maximum length allowed for an SSSAR-SDU of the Segmentation and Reassembly Service Specific Convergence sublayer. + +**SSTEDInd:** This Boolean attribute indicates whether or not the transmission error detection mechanisms have been selected, with value TRUE indicating selection. + +**SSADTInd:** This Boolean attribute indicates whether or not the assured data transfer mechanism has been selected, with value TRUE indicating selection. + +### *Relationships* + +One instance of this managed entity shall exist for each instance of the AAL2ParameterProfileF used within an NE. One instance of this managed entity may be associated with one or more instances of an interworking vcCTPF. + +## **8.111 SSCSPParameterProfile2F** + +These are managed entity groups default values for Service Specific Convergence Sublayer parameters for channels carried in an AAL2 VCC that provide media streams. These parameters are defined in ITU-T Rec. I.366.2. Instances of this managed entity are created and deleted at the request of the NMS or Operators. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**ServiceCatType:** This attribute indicates the type of service category provided by AAL2. Valid values include but are not limited to "Audio" and "Multirate". + +**EncSrcType:** This attribute indicates the source for the encoding profile format. Valid values include but are not limited to "ITU-T" and "ATM Forum". + +**EncProfileIndex:** This attribute indicates the specific predefined encoding profile used. + +**AudioServInd:** This Boolean attribute indicates whether or not audio service is transported, where the value TRUE implies the presence of this service. + +**PCMEncType:** This attribute indicates the type of PCM coding. Valid values include but are not limited to "mu-law PCM coding" and "alpha-law PCM coding". + +**CMDDataInd:** This Boolean attribute indicates whether or not Circuit Mode Data is carried on this connection, where the value TRUE implies its presence. + +**CMMultiplierNum:** This attribute provides the N value in N×64 kbit/s circuit mode data. + +**FMDDataInd:** This Boolean attribute indicates whether or not Frame Mode Data is carried on this connection, where the value TRUE implies its presence. + +**FMMaxFrameLen:** This attribute provides the maximum length of a frame mode data unit. + +**CASInd:** This Boolean attribute indicates whether or not Channel Associated Signalling is enabled on the connection, where the value TRUE implies it is enabled. + +**DTMFInd:** This Boolean attribute indicates whether or not Dual Tone Multi-Frequency dialled digits is transported on the connection, where the value TRUE implies its presence. + +**MFR1Ind:** This Boolean attribute indicates whether or not Multi-Frequency R1 dialled digits is transported on the connection, where the value TRUE implies its presence. + +**MFR2Ind:** This Boolean attribute indicates whether or not Multi-Frequency R2 dialled digits is transported on the connection, where the value TRUE implies its presence. + +**RateControlInd:** This Boolean attribute indicates whether or not rate control is transported on the connection, where the value TRUE implies its presence. + +**SynchChangeInd:** This Boolean attribute indicates whether or not synchronization of change in SSCS operation is transported on the connection, where the value TRUE implies its presence. + +### *Relationships* + +One instance of this managed entity shall exist for each instance of the AAL2ParameterProfileF used within an NE. One instance of this managed entity may be associated with one or more instances of an interworking vcCTPF. + +### **8.112 softwareF** + +This managed entity is used to represent logical information stored in equipment, including programs and data tables. Instances of this managed entity are created and deleted by the FSAN NE or at the request of the managing system. The managed entity supports the operational state and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) softwareF that has been installed in the ATM NE. For example, this attribute may be used to administer the activation and deactivation of multiple softwareF entities in the ATM NE, particularly useful when downloading new software in the ATM NE. + +**OperationalState:** This attribute identifies whether or not the softwareF being represented is capable of performing its normal functions (i.e., in-service or out-of-service). + +**SupplierName:** This attribute identifies the supplier. + +**Version:** This attribute identifies the version of the softwareF. + +**AffectedManagedEntityList:** This attribute lists the managed entities (plug-ins, equipmentHolders, FSAN NEs, etc.) that can be directly affected by a change in state or deletion of this managed entity. + +**UserLabel:** This attribute correlates the managed entity instance to an NMS-provided identifier. This attribute is required for managed entities associated with user-network interfaces. + +### *Relationships* + +Multiple instances of this managed entity may be contained in an instance of the NEFSAN and PluginUnitF managed entities. + +### **8.113 SONETSDHLinePMHistoryData** + +This is a managed entity that contains the past performance monitoring data collected at an rsTTPF for near-end regenerator section monitoring for both directions of traffic. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated rsTTPF managed entity, and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MonitoringMEPtr:** This attribute identifies the monitored managed entity. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**ErroredSecondsP:** An ES represents the count of seconds with one or more errored blocks during the available time of the monitored resource. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**SeverelyErroredSecondsP:** A SES represents the count of one second periods containing greater than or equal to 30% of errored blocks, or at least one Severely Disturbed Period (SDP), that is one second, containing one or more defects during the available time of the monitored resource. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**BackgroundBlockErrorP:** A BBE represents the count of the errored blocks (Estimated Errored Block on Bip-n violation) not occurring as part of an SES. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**OutOfFrameSecondsP:** An OFS represents the count of seconds with at least one out of Frame Event during the available time of the monitored resource. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**UnavailableSecondsP:** UAS provides the count of seconds of unavailability. A UAS state is declared when ten consecutive SESs occur. The ten SESs are subtracted from the SES count and added to the UAS count. Subsequent seconds are accrued to the UAS count until the UAS state is cleared. The UAS state is cleared when ten consecutive non-SESs occur. When that happens, the consecutive ten non-SESs are subtracted from the UAS count. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +#### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of rsTTPF. + +### **8.114 SONETSDHPHysicalPortResource** + +This managed entity collects key capacity metrics for NNI-side OC-3 or STS-1 or STS-3 port of the OLT. One instance of this managed entity is created automatically when the port with PhysicalPathType equal to OC-3 or STS-1 or STS-3 is provisioned. The automatic creation of instances of this managed entity may be reported to the managing system. The managed entity shall be automatically deleted when the port is deleted. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PortManagedEntityId:** This attribute identifies the associated port. + +**MaxTSs:** This attribute identifies the maximum amount of timeslots assigned to the port of OLT. + +**ReservedTSs:** This attribute identifies the reserved timeslots assigned to the port of OLT. + +**AssignedTSs:** This attribute identifies the already-assigned timeslots assigned to the port of OLT. + +#### *Relationships* + +One instance of this managed entity shall exist for each instance of the NNI-side OLT Port with PhysicalPathType equal to OC-3 or STS-1 or STS-3. + +### 8.115 SONETSDHSectionAdaptationPMHistoryData + +This is a managed entity that contains the past performance monitoring data collected at an au3CTPF or au4CTPF for near-end and far-end path monitoring for both directions of traffic. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated au3CTPF or au4CTPF managed entity and a data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MonitoringMEPtr:** This attribute identifies the monitored managed entity. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**PointerJustificationCountHighP:** A pJCHigh represents the positive PJE count on one selectable outgoing AU within an STM-N signal after the AU has been resynchronized on the local clock. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**PointerJustificationCountLowP:** A pJCLow represents the negative PJE count on one selectable outgoing AU within an STM-N signal after the AU has been resynchronized on the local clock. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +#### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of au3CTPF or au4CTPF. + +### 8.116 SONETSDHSectionPathPMHistoryData + +This is a managed entity that contains the past performance monitoring data collected at an msTTPF or vc3TTPF or vc4TTPF for near-end and far-end multiplex section monitoring for both directions of traffic. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated msTTPF or vc3TTPF or vc4TTPF managed entity, and a data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MonitoringMEPtr:** This attribute identifies the monitored managed entity. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**ErroredSecondsP:** An ES represents the count of seconds with one or more errored blocks during the available time of the monitored resource. This parameter monitors the + +characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**SeverelyErroredSecondsP:** An SES represents the count of one second periods containing greater than or equal to 30% of errored blocks, or at least one Severely Disturbed Period (SDP) that is one second containing one or more defects during the available time of the monitored resource. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**BackgroundBlockErrorP:** A BBE represents the count of the errored blocks (Estimated Errored Block on Bip-n violation) not occurring as part of an SES. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**UnavailableSecondsP:** UAS provides the count of seconds of unavailability at the near end. A UAS state is declared when ten consecutive SESs occur. The ten SESs are subtracted from the SES count and added to the UAS count. Subsequent seconds are accrued to the UAS count until the UAS state is cleared. The UAS state is cleared when ten consecutive non-SESs occur. When that happens, the consecutive ten non-SESs are subtracted from the UAS count. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**FailureCountP:** An FC represents a count of the number of occurrences of near-end failure events. This parameter monitors the characteristic signal either from the customer to the NE or from the NNI-side network to the NE. + +**ErroredSecondsTypeAP:** An FC represents a count of errored seconds of type A at the near-end. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**ErroredSecondsTypeBP:** An FC represents a count of errored seconds of type B at the near-end. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE. + +**ErroredSecondsPFE:** An ES represents the count of seconds with one or more errored blocks during the available time of the monitored resource. This parameter monitors the characteristic signal either from the NE to the customer, or from the NE to the NNI-side network. + +**SeverelyErroredSecondsPFE:** An SES represents the count of one second periods containing greater than or equal to 30% of errored blocks, or at least one Severely Disturbed Period (SDP) that is one second containing one or more defects during the available time of the monitored resource. This parameter monitors the characteristic signal either from the NE to the customer, or from the NE to the NNI-side network. + +**BackgroundBlockErrorPFE:** A BBE represents the count of the errored blocks (Estimated Errored Block on Bip-n violation) not occurring as part of an SES. This parameter monitors the characteristic signal either from the NE to the customer, or from the NE to the NNI-side network. + +**UnavailableSecondsPFE:** UAS provides the count of seconds of unavailability at the far end. A UAS state is declared when ten consecutive SESs occur. The ten SESs are subtracted from the SES count and added to the UAS count. Subsequent seconds are accrued to the UAS count until the UAS state is cleared. The UAS state is cleared when ten consecutive non-SESs occur. When that happens, the consecutive ten non-SESs are subtracted from the UAS count. This parameter monitors the characteristic signal either from the NE to the customer, or from the NE to the NNI-side network. + +**FailureCountPFE:** An FC represents a count of the number of occurrences of far-end failure events. This parameter monitors the characteristic signal either from the NE to the customer, or from the NE to the NNI-side network. + +**ErroredSecondsTypeAPFE:** An FC represents a count of errored seconds of type A at the far-end. This parameter monitors the characteristic signal either from the NE to the customer, or from the NE to the NNI-side network. + +**ErroredSecondsTypeBPFE:** An FC represents a count of errored seconds of type B at the far-end. This parameter monitors the characteristic signal either from the NE to the customer, or from the NE to the NNI-side network. + +#### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of msTTPF or vc3TTPF or vc4TTPF. + +### **8.117 subnetworkConnectionF** + +This managed entity represents a G.852.2 subnetwork connection (SNC), i.e., "a transport entity that transfers information across a subnetwork". A subnetwork connection is associated with two network termination points or a network termination point and a group of network termination points. The managed entity supports availability status and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**AvailabilityStatus:** This attribute indicates whether or not a managed entity is capable of performing its task. + +**UserLabel:** This attribute provides the listing of service Ids associated with this connection. + +**ATPPtr:** This attribute is used to identify one end of the subnetwork connection. + +**ZTPPtr:** This attribute is used to identify the other end of the subnetwork connection. + +**Directionality:** This attribute indicates whether or not a link is "unidirectional", "bidirectional", or "undefined". + +**RecoverableInd:** This attribute is used to identify the connection as recoverable (protected) or not. + +#### *Relationships* + +A subnetwork connection is associated with termination points or a termination point and a group of termination points. The termination points may be TTPFs or CTPFs. + +### **8.118 subnetworkF** + +A subnetworkF (according to ITU-T Rec. G.852.2) is a topological component used for carrying characteristic information. Note that a subnetworkF may be empty. Subnetworks are used for making subnetwork connections. This Managed Entity is specialized per layer. The subnetworkF is delineated by CTPF and/or TTPF managed entities. Instances of this managed entity are automatically created when the OLT is installed. The managed entity supports administrative state and availability status functions as defined in ITU-T Rec. X.731. Changes in state and status are reported automatically or on demand to the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**AvailabilityStatus:** This attribute describes the degree to which the managed entity is able to perform its normal functions. + +**ContainedNetworkTPList:** This attribute is a list of pointers to TPs that are contained in a subnetwork. + +**SignalIdentification:** This attribute represents the specific format that the resource carries. + +**UserLabel:** This attribute provides an operator-defined label. + +### *Relationships* + +One or more of these managed entities exist for each installed or pre-provisioned FSAN NE. + +## **8.119 TCAdaptorDbFairnessPMHistoryData** + +This is a managed entity that contains the past performance monitoring data collected at a tcAdaptorF of OLT. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated tcAdaptorF managed entity and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MonitoringMEPtr:** This attribute identifies the monitored managed entity. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**Variance2:** This attribute is a gauge providing the variance among all T-CONTs of Type 2 of the ratio of received cells to guaranteed cells per T-CONT. The sampling frequency is determined by supplier implementation. + +**Variance3:** This attribute is a gauge providing the variance among all T-CONTs of Type 3 of the ratio of received cells to guaranteed cells per T-CONT. The sampling frequency is determined by supplier implementation. + +**Variance4:** This attribute is a gauge providing the variance among all T-CONTs of Type 4 of the ratio of received cells to guaranteed cells per T-CONT. The sampling frequency is determined by supplier implementation. + +**Variance5:** This attribute is a gauge providing the variance among all T-CONTs of Type 5 of the ratio of received cells to guaranteed cells per T-CONT. The sampling frequency is determined by supplier implementation. + +### *Relationships* + +One managed entity may exist for each instance of PON-side tcAdaptorF of OLT. + +## 8.120 tcAdaptorTTPF + +An instance of this managed entity represents a point in the ATM NE where the adaptation of the ATM Layer to the underlying physical infrastructure takes place. This adaptation happens on PON interface ports at the OLT and ONT as well as on ATM Network Interfaces on the OLT and subscriber ATM interfaces on the ONT. ITU-T Rec. I.321 identifies this adaptation function as one of many functions performed at the Transmission Convergence (TC) sublayer of the B-ISDN protocol stack. This managed entity is responsible for generating alarms that report the (in)ability of the managed entity to delineate ATM cells from the payload of a terminated digital transmission path. + +An instance of this managed entity is created automatically for each instance of the associated Physical Path Termination Point managed entity. Instances of this managed entity can also be created and deleted by request of the managing system. The managed entity supports the operational state and administrative state and alarm status functions as defined in ITU-T Rec. X.731. Changes in state and status are reported automatically or on demand to the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by this managed entity. + +**OperationalState:** This attribute identifies whether or not the managed entity is capable of performing its normal functions (i.e., in-service or out-of-service). + +**PhysicalPathTPFPtr:** This pointer attribute identifies the associated instance of the physicalPathTPF managed entity. + +**APONTPPtr:** This pointer attribute identifies the associated instance of the APONTTP managed entity in case that this managed entity exits on APON-side of ONU or OLT. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an AlarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**ATMNetworkAccessProfileFORUNInfoF:** This attribute provides a pointer to the object instance of the associated ATMNetworkAccessProfileF object or UNInfoF object. + +**CellScramblingControl:** This attribute is used to activate/deactivate the ATM cell scrambling function. This attribute is only present for ATM interfaces where ATM cell scrambling may be controlled (i.e., activated/deactivated). The ATM Forum UNI specification requires cell scrambling for ATM/SONET interfaces but allows cell scrambling to be controlled (i.e., turned on and off) for ATM/DS3 interfaces. + +**Framerconfiguration:** Some UNIs such as the ATM45 have two methods of mapping of ATM cells into the payload of a DS3 frame, physical layer convergence protocol (PLCP)-based mapping and HEC-based mapping. Valid values are "PLCP option" or "HEC option". + +**CellRateDecouplingType:** This attribute is used to select the cell rate decoupling type whenever the ITU-T and ATM Forum standards give different definitions. Valid values are "ITU-T definition" and "ATM Forum definition". This attribute is needed for interfaces with decoupling options. + +### *Relationships* + +Each instance of this managed entity is associated with one instance of the PhysicalPathTP managed entity through the physicalPathTPFPtr attribute. One instance of ATMNetworkAccessProfileF or uniInfoF shall be used to characterize this managed entity. + +### **8.121 TCAdaptionProtocolMonitoringPMHistoryData** + +This is a managed entity that contains the past performance monitoring data collected at a tcAdaptorF for near-end TC sublayer monitoring for both directions of traffic. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated tcAdaptorF managed entity and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MonitoringMEPtr:** This attribute identifies the monitored managed entity. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**DiscardedCellsHECViolationP:** This attribute provides a count of the number of cells discarded due to uncorrectable header bit errors. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE, or from PON-side network to the NE. + +**ErroredCellsHECViolationP:** This attribute provides a count of the number of cells with header bit errors. This parameter monitors the characteristic signal either from the customer to the NE, or from the NNI-side network to the NE, or from PON-side network to the NE. + +### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of tcAdaptorF. + +### **8.122 T-CONT** + +This managed entity is a type of logicalLinkEndF and inherits all the attributes and relationships defined by logicalLinkEndF. Signal identification is set to "VP" or "VC". It contains vpCTPFs or vcCTPFs for the purposes of DBA management. LinkFPtr points to vpLogicalLinkF or vcLogicalLinkF. LinkEndDirectionality is "source" in case that T-CONT resides in ONT/ONU, while it is "sink" in case that T-CONT resides in OLT. Note that although a contained vpCTPF or vcCTPF is bidirectional, only its source part in ONT/ONU or its sink part in OLT is affected by this TCONT. + +### *Attributes* + +**MaximumBandwidth:** This attribute identifies the maximum amount of bandwidth assigned to the T-CONT. + +**GuaranteedBandwidth:** This attribute identifies the summation of FixedBandwidth and "Assured Bandwidth" assigned to the link end. Note that "Assured Bandwidth" is the bandwidth that is always available to the ONU/ONT concerned, but can be used by other T-CONTs, when ONU/ONT concerned does not have cells to transmit. + +**FixedBandwidth:** This attribute identifies the amount of entirely reserved bandwidth assigned to the link end in order to achieve a low cell transfer delay. + +**TcontType:** This attribute identifies the T-CONT Type 1-5. + +**BandwidthUpdateFrequency:** This attribute is used to decide the update frequency of the DBA bandwidth. + +#### *Relationships* + +vpLogicalLinkF or vcLogicalLinkF has two T-CONTs. + +### **8.123 TCONTbuffer** + +This managed entity represents a logical object to the data grant provided by the OLT. A T-CONT buffer can accommodate ATM cells in Traffic Schedulers that exist in the ATM layer. Therefore, the T-CONT buffer is regarded as a logical buffer and it does not have the QoS control function. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PhysicalPathTPFPtr:** This attribute points to the PhysicalPathTPF associated with this TCONTbuffer. + +**NEAssignmentPtr:** This attribute identifies the T-CONT in the network view associated with this TCONTbuffer. + +#### *Relationships* + +This managed entity can be associated with the Traffic Scheduler. Moreover, it can be associated with corresponding T-CONT in the network view. + +### **8.124 TCONTbufferPMHistoryData** + +This is a managed entity that contains the past performance monitoring data collected at a TCONTbuffer of OLT. Instances of this managed entity are created automatically whenever performance monitoring is requested by the management system at the associated TCONTbuffer managed entity, and a data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**MonitoringMEPtr:** This attribute identifies the monitored managed entity. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**AverageReceive\_AssignRate:** This attribute is a gauge recording the average of received cells to cells allowed through the granting mechanism. + +**MaxReceive\_AssignRate:** This attribute is the maximum value achieved by AverageReceive\_AssignRate gauge during the collection interval. + +**MinReceive\_AssignRate:** This attribute is the minimum value achieved by AverageReceive\_AssignRate gauge during the collection interval. + +### *Relationships* + +One managed entity may exist for each instance of PON-side TCONTbuffer of OLT. + +#### **8.125 thresholdDataF** + +This managed entity contains threshold values for the performance monitoring parameters maintained in one or more instances of other managed entities. The FSAN NE upon initialization creates instances of this managed entity automatically. Instances of this managed entity are also created and deleted at the request of the managing system. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**PMType:** This attribute identifies the type of performance monitoring associated with these threshold values (e.g., AAL1, AAL5, DS1PhysicalLayer, ...) + +**PerformanceParameterandThresholdValueList:** This attribute identifies one or more performance monitoring parameters (e.g., Discarded Cells due to HEC Violations) and their associated threshold value. + +### *Relationships* + +Relationship of this managed entity to one or more other managed entities is provided through the consistent use of a pointer mechanism. + +#### **8.126 topologicalLinkEndF** + +A topological link end contains CTPFs for the purposes of representing topology. It represents the end of a topological link. It is related to one and only one TTPF in the underlying server layer. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SignalIdentification:** This attribute identifies the characteristic information of the layer to which this managed entity belongs. + +**ServerTTPFPtr:** This attribute identifies the TTPF managed entity in the server layer supporting this end point. + +**TopologicalLinkFPtr:** This attribute identifies the topological link or logicalMPTLinkF associated with this end point. + +**PointDirectionality:** This attribute specifies whether this managed entity contains sink, source or bidirectional connection termination points. + +**CTPList:** This attribute lists the CTPFs that are contained by this managed entity. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +### *Relationships* + +Each topologicalLinkF has two topologicalLinkEndF(s). + +#### **8.127 topologicalLinkF** + +A topological link provides a topological description of capacity between two adjacent subnetworks (from one topological link end to another), or between a subnetwork and an access group. There can be multiple topological links between subnetworks. A topological link cannot be created between a composite subnetwork and one of its component subnetworks. This entity may be explicitly created by the network management system. + +## *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**SignalIdentification:** This attribute identifies the characteristic information of the layer to which this managed entity belongs. + +**ServerTrail:** This attribute identifies the underlying trail in the layered network model for which this managed entity is its unique client. + +**Directionality:** This attribute indicates whether or not a link is "unidirectional", "bidirectional". + +**Aend:** This pointer attribute identifies the subnetwork, link end, or access group at one end of the topological link. + +**Zend:** This pointer attribute identifies the subnetwork, link end, or access group at the other end of the topological link. + +**LinkConnectionList:** This attribute lists the linkConnectionFs that are contained by this managed entity. + +**Weight:** This attribute describes the relative weight of using the link. The specific value of this attribute is determined by the managing system. This attribute takes on a NULL value in cases where the link is not assigned a specific weight. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +## *Relationships* + +A topologicalLinkF is a group of link connections sharing the same extremities. This relationship involves one and only one instance of the topologicalLinkF managed entity, and zero or more instances of the linkConnectionF managed entity. One topologicalLinkF has a relationship with the two managed entities that it is linking. A topologicalLinkF cannot exist without the subnetworkF being identified. + +## **8.128 trafficDescriptorProfileF** + +This managed entity specifies traffic parameters for virtual channel or virtual path connections. Where ingress and egress parameters are mentioned, they may take different values. Instances of this managed entity are provided for the FSAN NE upon FSAN NE initialization. Instances of this managed entity are also created and deleted at the request of the managing system. + +## *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**ServiceCategory:** Indicates the service category as defined in ATM Forum Traffic Management 4.0. Valid values are CBR, rt-VBR, nrt-VBR, UBR, ABR, or GFR. + +**ConformanceDefinition:** Indicates the type of conformance as defined in ATM Forum Traffic Management 4.0. Valid values are CBR.1, VBR.1, VBR.2, VBR.3, UBR.1, UBR.2, ABR, GFR.1, GFR.2. The NE should enforce the correspondence between Conformance Definition and Service Category as specified in ATM Forum Traffic Management 4.1. + +**PeakCellRate – Ingress and Egress:** These parameters are required for traffic of all service categories. They apply to CLP=0 flow for ABR and apply to CLP=0+1 flow otherwise. + +**CellDelayVariationTolerancePCR – Ingress and Egress:** These parameters are required for all service categories. They apply to CLP=0 flow for ABR and apply to CLP=0+1 flow otherwise. + +**CellDelayVariationToleranceSCR – Ingress and Egress:** These parameters apply to real-time and non-real-time VBR. They apply to CLP=0+1 traffic flow for VBR.1 and apply to CLP=0 traffic flow VBR.2 and VBR.3. + +**SustainableCellRate – Ingress and Egress:** These parameters are required for real-time and non-real-time VBR traffic. They apply to CLP=0+1 traffic flow for VBR.1 and apply to CLP=0 traffic flow for VBR.2 and VBR.3. + +**MaximumBurstSize – Ingress and Egress:** These parameters are required for real-time and non-real-time VBR traffic and for GFR traffic. They apply to CLP=0+1 traffic flow for VBR.1, GFR.1, and GFR.2, and apply to CLP=0 traffic flow for VBR.2 and VBR.3. + +**MFS – Ingress and Egress:** These parameters are required for GFR traffic only. They refer to maximum frame size. + +**MinimumCellRate – Ingress and Egress:** These parameters are required for ABR and GFR traffic. In the case of GFR it is MCR applied to CLP=0. + +**InitialCellRate – Ingress and Egress:** These parameters are required for ABR traffic. + +**TransientBufferExposure – Ingress and Egress:** These parameters are required for ABR traffic. + +**RateDecreaseFactor – Ingress and Egress:** These parameters are required for ABR traffic. + +**RateIncreaseFactor – Ingress and Egress:** These parameters are required for ABR traffic. + +**FixedRoundTripTime:** This parameter is required for ABR traffic. + +**Nrm – Ingress and Egress:** These parameters apply to ABR and are optional in the ABR context (Default = 32). + +**Trm – Ingress and Egress:** These parameters apply to ABR and are optional in the ABR context (Default = 100). + +**CDF – Ingress and Egress:** These parameters apply to ABR and are optional in the ABR context (Default = 1/16). + +**ADTF – Ingress and Egress:** These parameters apply to ABR and are optional in the ABR context (Default = 0.5). + +### *Relationships* + +Each instance of this entity may be related to zero or more instances of vcCTPF or vpCTPF managed entities through a pointer attribute. + +## **8.129 TrafficScheduler** + +This managed entity represents a logical object of some Traffic Scheduler to control upstream ATM cells. A Traffic Scheduler can accommodate ATM cells after priority queue or other Traffic Scheduler and transfer ATM cells toward the next Traffic Scheduler or T-CONT buffer + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**Policy:** This attribute represents scheduling policy. Valid values include but are not limited to "Null", "HOL" or "WRR". + +**TrafficSchedulerPtr:** This attribute points to the Traffic Scheduler instance that is directly associated with this Traffic Scheduler. This pointer is used only when this Traffic Scheduler is connected to another Traffic Scheduler. + +**PriorityWeight:** This attribute represents priority for HOL scheduling or the weight for WRR scheduling. This value is used by Traffic Scheduler pointed by TrafficSchedulerPtr. If the indicated pointer has Policy = HOL, then this value is interpreted as a priority. If the indicated pointer has Policy = WRR, then this value is interpreted as a weight. + +**TCONTbufferPtr:** This attribute points to the T-CONT Buffer instance that is directly associated with this Traffic Scheduler. This pointer is used only when this Traffic Scheduler is contained by the T-CONT buffer directly. + +#### *Relationships* + +This managed entity can be associated with another TrafficScheduler or TCONTbuffer. + +### **8.130 trailF** + +This managed entity is used to describe the transport entity transferring information between two TTPFs. A sequence of one or more link connections and subnetwork connections may be pieced together to form a trail. An instance of this managed entity is created automatically with the provisioning of information transfer in the network layer to which this trail belongs. The managed entity can only be deleted when the provisioned service is taken out of service. The managed entity supports availability status and administrative state functions as defined in ITU-T Rec. X.731. Changes in state are reported automatically or on demand to the managing system. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**AvailabilityStatus:** This attribute indicates whether or not a managed entity is capable of performing its task. + +**UserLabel:** This attribute is used for an operator to assign a user-friendly name. + +**ATTPPtr:** This attribute is used to identify one end of the trail. + +**ZTTPPtr:** This attribute is used to identify the other end of the trail. + +**Directionality:** This attribute indicates whether or not a trail is "unidirectional" or "bidirectional". + +#### *Relationships* + +There is one instance of this managed entity for the two TTPFs it joins. + +### **8.131 TTPF** + +This managed entity terminates and originates a trail and can be used to represent the termination of subnetworkConnectionFs on an FSAN NE. Instances of this managed entity may be created and deleted at the request of the managing system or implicitly through a provisioning request. The managed entity supports the availability status, operational state and administrative state and alarm status functions as defined in ITU-T Rec. X.731. Changes in state and status are reported automatically or on demand to the managing system. This managed entity is defined for the purposes of grouping together all common attributes of connection termination point on an FSAN NE in the NE view, but only instances of specific TTPFs (e.g., adslTTPF, DS1TTPF, etc.) shall be implemented. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AdministrativeState:** This attribute is used to activate (unlock) and deactivate (lock) the functions performed by instances of this managed entity. + +**OperationalState:** This attribute indicates whether or not a managed entity is capable of performing its task. The operational state reflects the perceived ability to receive or to generate a valid signal. Valid values are "enabled" and "disabled". If the termination point detects that a signal received has failed or it is unable to process the incoming signal, then the operational state will change from the value "enabled" to "disabled". If the termination point detects that a valid signal cannot be generated, then the operational state will also change from the value "enabled" to "disabled". + +**AvailabilityStatus:** This attribute indicates whether or not a managed entity is capable of performing its task. + +**SupportedByPlug-inF:** This attribute identifies the interface circuit pack to which this managed entity is associated. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**UpstreamConnectivityPointer:** This attribute identifies the termination point managed entity that sends information (traffic) to this managed entity at the same layer. + +**DownstreamConnectivityPointer:** This attribute identifies the termination point managed entity that receives information (traffic) from this managed entity at the same layer. + +**PointDirectionality:** This attribute identifies whether the termination point is "source", "sink", or "bidirectional". + +### *Relationships* + +There is zero or more of these managed entities contained within an FSAN NE. One of these managed entities must exist for each CTPF for a section link connection having the same characteristic signal. One of these managed entities must exist for each PhysicalPathTPF having the same characteristic signal type. Zero or more of these instances are associated with each subnetworkConnectionF. Two of these instances are associated with each trailF. + +## **8.132 uniInfoF** + +This managed entity is used to organize data associated with the ATM User Network Interfaces (UNIs) supported by the ONT or NT. One instance of this managed entity shall exist for each ATM UNI supported by the ONT or NT. Instances of this managed entity are created and deleted at the request of the NMS or Operators. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AccessGroupPtr:** This attribute provides a pointer to the TTPFs associated with the end users to which this profile applies. + +**TCAdaptorId:** This attribute provides a Ptr to the associated instance of the TC Adaptor managed entity. + +**LocalMaximumNumberofVPCsSupportable:** This attribute identifies the maximum number of VPCs that the ONT or NT can support at its end of the interface for the associated user. + +**LocalMaximumNumberofVCCsSupportable:** This attribute identifies the maximum number of VCCs that the ONT or NT can support for the associated user. + +**LocalMaximumNumberofAllocatedVPIBits:** This attribute identifies the number of allocated bits of the VPI sub-field that the ONT or NT can support at its end of the interface for the associated user. + +**LocalMaximumNumberofAllocatedVCIBits:** This attribute identifies the number of allocated bits of the VCI sub-field that the ONT or NT can support at its end of the interface for the associated user. + +**LoopbackLocationCode:** This attribute provides the code that identifies incoming ATM layer OAM loopback cells that are to be looped-back at this UNIF. + +#### *Relationships* + +One instance of this managed entity shall be associated with each local user interface supported by the ONT or NT. + +### **8.133 upcNpcDisagreementPMHistoryDataF** + +An instance of this managed entity is used to record historical data associated with UPC/NPC Disagreement Monitoring functions performed by the OLT. UPC policing at the ONT or ONU as well as the corresponding performance monitoring capability will be expected in the future. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**CTPFPtr:** This attribute identifies the associated vpCTPF or vcCTPF managed entity where performance monitoring occurs. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**DiscardedCellsduetoUPC/NPC:** This attribute provides a raw count of the number of discarded cells due to combined CLP=0 and CLP=1 UPC/NPC policing. + +**DiscardedCLP=0CellsduetoUPC/NPC:** This attribute provides a raw count of the number of discarded CLP=0 cells due to CLP=0 only UPC/NPC policing. This counter is only present if CLP=0 traffic is separately policed. + +**TaggedCLP=0Cells:** This attribute provides a count of the number of cells that have been tagged. + +#### *Relationships* + +Zero or more instance of this managed entity may exist for each instance of the vpCTPF and vcCTPF managed entities. + +### 8.134 vc3TTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a vc3 trail. Changes in state or status are reported automatically or on demand to the managing system. The following alarms can be detected at this managed entity: Far-End Receive Failure (FERF), Path Trace Mismatch and Signal Label Mismatch. + +#### *Attributes* + +**J1PathTraceExpected:** This attribute is used to specify the value of the expected J1 Byte VC Path Trace byte message for this managed entity. + +**J1PathTraceReceive:** This attribute is used to indicate the value of the incoming J1 Byte VC Path Trace byte message for this managed entity. + +**J1PathTraceSend:** This attribute is used to indicate the value of the outgoing J1 VC Path Trace byte message for this managed entity. + +**C2SignalLabelExpected:** This attribute specifies the expected C2 VC Signal Label for this incoming vc3TTPF. See ITU-T Rec. G.709/Y.1331 for a list of valid values. + +**C2SignalLabelReceive:** This attribute specifies the C2 VC Signal Label for this incoming vc3TTPF. See ITU-T Rec. G.709/Y.1331 for a list of valid values. + +**C2SignalLabelSend:** This attribute specifies the C2 VC Signal Label for this outgoing vc3TTPF. See ITU-T Rec. G.709/Y.1331 for a list of valid values. + +**TcAdaptorPtr:** This attribute points to the tcAdaptor managed entity that uses this managed entity as a server trail. + +#### *Relationships* + +There is zero or more of these managed entities contained within any FSAN NE. One of these managed entities exists for each au3CTPF. + +### 8.135 vc4TTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a vc4 trail. The following alarms can be detected at this managed entity: Far End Receive Failure (FERF), Path Trace Mismatch and Signal Label Mismatch. + +#### *Attributes* + +**J1PathTraceExpected:** This attribute is used to specify the value of the expected J1 Byte VC Path Trace byte message for this managed entity. + +**J1PathTraceReceive:** This attribute is used to indicate the value of the incoming J1 Byte VC Path Trace byte message for this managed entity. + +**J1PathTraceSend:** This attribute is used to indicate the value of the outgoing J1 VC Path Trace byte message for this managed entity. + +**C2SignalLabelExpected:** This attribute specifies the expected C2 VC Signal Label for this incoming vc4TTPF. See ITU-T Rec. G.709/Y.1331 for a list of valid values. + +**C2SignalLabelReceive:** This attribute specifies the C2 VC Signal Label for this incoming vc4TTPF. See ITU-T Rec. G.709/Y.1331 for a list of valid values. + +**C2SignalLabelSend:** This attribute specifies the C2 VC Signal Label for this outgoing vc4TTPF. See ITU-T Rec. G.709/Y.1331 for a list of valid values. + +**TcAdaptorPtr:** This attribute points to the tcAdaptor managed entity that uses this managed entity as a server trail. + +## Relationships + +There is zero or more of these managed entities contained within an OLT, an ONT or an NT. One of these managed entities exists for each au4CTPF. + +### 8.136 vcCTPF + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. This managed entity is used to represent the termination of vcLinkConnectionF on an FSAN NE and (possibly) vcSubnetworkConnectionFs. A Traffic descriptor profile is used to characterize this managed entity. Represents the point in the FSAN NE where the VCC and associated overhead (F5 OAM cells) are terminated and originated. The following alarms can be detected at this managed entity: Cell Starvation, Alarm Indication Signal (AIS) and Remote Defect Indication (RDI). + +#### Attributes + +**VPIVCIValue:** This attribute identifies the VPI/VCI value associated with the link connection if the managed entity terminates a link connection. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**IngressTrafficDescriptorProfilePtr:** This attribute identifies the ingress trafficDescriptorProfileF object associated with configuration of this TP. + +**EgressTrafficDescriptorProfilePtr:** This attribute identifies the egress trafficDescriptorProfileF object associated with configuration of this TP. + +**IngressQualityOfServiceProfilePtr:** This attribute identifies the ingress qualityOfServiceProfileF object associated with configuration of this TP. + +**EgressQualityOfServiceProfilePtr:** This attribute identifies the egress qualityOfServiceProfileF object associated with configuration of this TP. + +**SegmentEndpoint:** This Boolean attribute indicates whether or not the termination point has been configured to represent a segment end point. + +**PMOAMMethod:** This attribute indicates the method used to set up and terminate the PM OAM monitoring activity. Valid values are "TMN", "OAM", or "notSupported". If the value is "notSupported", then PM OAM is not supported on the end point. + +**PMOAMDirection:** This attribute indicates the desired direction(s) of transmission to monitor PM OAM. Valid directions are: away from activator (transmit), towards activator (receive), or both. + +**PMOAMBlockSize:** This attribute indicates the PM OAM nominal block size choice for both the receive and transmit directions. + +**PMOAMForwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the forward direction by setting the value to TRUE. + +**PMOAMBackwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the backward direction by setting the value to TRUE. + +**AALProfilePtr:** This attribute provides a pointer to an instance of the AAL Profile object associated with this managed entity (if any). + +**ServiceProfilePtr:** This attribute provides a Ptr to the instance of a service profile, such as the CESServiceProfileF associated with this vcCTPF if it is interworking vcCTPF. + +**ThresholdDataPtr:** This attribute provides a pointer to an instance of the ThresholdDataF object that provides threshold values for monitored parameters to be used to generate Threshold Crossing Alert notifications whenever a monitored parameter crosses its associated threshold value and this managed entity represents the monitoring point. + +**ServiceLevelCTPFList:** This attribute provides a list of service level connection termination points that are being inter-worked if this vcCTPF is interworking ATM and AAL (e.g., the list of DS1 CTPFs for a channelized DS3 card on an OLT, the single DS1 CTPF associated with a port on a multi-port DS1 subscriber line card on an ONT, the single Ethernet CTPF associated with a port on a bridged LAN 10/100Base-T subscriber line card on an ONT, etc.). + +### *Relationships* + +Zero or more instances of the managed entity shall exist for each instance of an FSAN NE. Each instance of this managed entity is associated with one instance of the vcTTPF managed entity. Two of these managed entities are associated with every vcLinkConnectionF. Zero or more of these managed entities may be associated with a vcSubnetworkConnectionF. + +### **8.137 vcLayerNetworkDomainF** + +This managed entity is a type of layerNetworkDomainF and inherits all the attributes and relationships defined by layerNetworkDomainF. Characteristic information provided in this layer is set to "VC". + +### **8.138 vcLinkConnectionF** + +This managed entity is a type of linkConnectionF and inherits all the attributes and relationships defined by linkConnectionF. This managed entity represents a vc layer link connection, derived from the G.852.2 definition, i.e., "the transparent capacity of transfer of information characterized by a given signal identification between two fixed points." Directionality is always set to "bidirectional". + +### *Attributes* + +**SignalIdentification:** This fixed attribute describes the signal that is transferred across the link. Here, it is set to "VC". + +**RetainedResource:** This Boolean attribute indicates if the managed entity instance needs to be retained when it is a component of a composite connection (involving a set of link connections and subnetwork connections) that has been deleted, or when supporting a trail that has been deleted. + +**CompositePtr:** This pointer attribute identifies the vcSubnetworkConnectionF managed entity to which this managed entity belongs. It may be the null pointer. + +### *Relationships* + +A topological link is a group of link connections sharing the same extremities. This relationship involves zero or more instances of the vcLinkConnectionF managed entity. A vcLinkConnectionF link is established between two vcCTPFs. + +### **8.139 vcLogicalLinkF** + +This managed entity is a type of logicalLinkF and inherits all the attributes and relationships defined by logicalLinkF. Signal identification is set to "VC". It contains vcLinkConnectionFs for + +the purposes of DBA management. LinkDirectionality is unidirectional from ONT/ONU to OLT. Note that although a contained vcLinkConnectionF is bidirectional, only its upstream part from ONT/ONU to OLT is affected by this vcLogicalLinkF. + +#### 8.140 vcSubnetworkConnectionF + +This managed entity is a type of subnetworkConnectionF and inherits all the attributes and relationships defined by subnetworkConnectionF. + +##### *Attributes* + +**ComponentPtrList:** This pointer attribute identifies the vcSubnetworkConnectionF(s) and vcLinkConnectionF(s) that comprise this vcSubnetworkConnectionF. It may be the null pointer. + +**CompositePtr:** This pointer attribute identifies the vcSubnetworkConnectionF managed entity to which this managed entity belongs. It may be the null pointer. + +#### 8.141 vcSubnetworkF + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "VC". + +##### *Attributes* + +**OLTPtr:** This attribute identifies the associated OLT. + +**ContainedLinkList:** This attribute identifies the instances of vcTopologicalLinkF contained in this subnetwork. + +**ContainedSubnetworkList:** This attribute identifies the instances of vcSubnetworkF contained in this subnetworkF. + +**ContainedAccessGroupList:** This attribute identifies the instances of accessGroupF contained in this subnetworkF. + +**LinkPtrList:** This attribute identifies the instances of vcTopologicalLinkF terminated by this subnetwork. + +##### *Relationships* + +One or more of these managed entities exist for each installed or pre-provisioned FSAN NE. + +#### 8.142 vcTopologicalLinkEndF + +This managed entity is a type of topologicalLinkEndF and inherits all the attributes and relationships defined by topologicalLinkEndF. This managed entity is used to represent the termination of a topological Link at the VC-layer. In the vcLayerNetworkDomainF, a vcTopologicalLinkEndF represents an ATM interface associated with the underlying transport facility. The PointDirectionality attribute will be "unidirectional". + +##### *Attributes* + +**LinkTPTType:** Describes the interface type that the managed entity supports: UNI, inter-NNI, intra-NNI, or unconfigured. + +**LoopbackLocationIdentifier:** A code used for OAM cell loopback purposes. Incoming OAM Loopback cells with a Loopback Location field value that matches the value of the loopbackLocationIdentifier attribute shall be looped-back over the interface. + +**SupportedByPlug-inF:** This attribute identifies the interface circuit pack to which this managed entity is associated. + +**PortId:** This attribute indicates port Id on the plug-in associated with the vcTopologicalLinkEndF. + +**CellScramblingEnable:** This attribute allows cell scrambling to be activated or deactivated on the ATM Interface represented by the vcTopologicalLinkEndF. + +#### *Relationships* + +Each vcTopologicalLinkF may be terminated by two instances of the vcTopologicalLinkEndF managed entity. One vcTopologicalLinkEndF managed entity is associated with one or more vcSubnetworkFs. Each vcTopologicalLinkEndF may be supported by one instance of a server vpTTPF managed entity in the server layer. vcCTPFs are contained in vcTopologicalLinkEndF. + +### **8.143 vcTopologicalLinkF** + +This managed entity is a type of topologicalLinkF and inherits all the attributes and relationships defined by topologicalLinkF. Signal identification is set to "VC". + +#### *Attributes* + +**RestorationMode:** This attribute is used to configure the restoration mode of a link as: "unavailable for routing and re-routing", "available for routing and not re-routing"; "available for re-routing and not routing"; or "available for both routing and re-routing". + +### **8.144 vcTrailF** + +This managed entity is a type of trailF and inherits all the attributes and relationships defined by trailF. This managed entity represents an I.326-defined trail in the VC layer domain. The vcTrailF is always bidirectional. + +#### *Attributes* + +**RestoreableInd:** This attribute is used to identify the connection as restorable or not. + +#### *Relationships* + +Each vcTrailF is terminated by at least two vcTTPFs. + +### **8.145 vcTTPF** + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It represents the point in the ATM subnetwork where the vcTrail and associated overhead (F5 OAM cells) are terminated/originated. The following alarms can be detected at this managed entity: Alarm Indication Signal (AIS) and Remote Defect Indication (RDI). + +#### *Attributes* + +**PMOAMMethod:** This attribute indicates the method used to set up and terminate the PM OAM monitoring activity. Valid values are "TMN", "OAM", or "notSupported". If the value is "notSupported", then PM OAM is not supported on the end point. + +**PMOAMDirection:** This attribute indicates the desired direction(s) of transmission to monitor PM OAM. Valid directions are: away from activator (transmit), towards activator (receive), or both. + +**PMOAMBlockSize:** This attribute indicates the PM OAM nominal block size choice for both the receive and transmit directions. + +**PMOAMForwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the forward direction by setting the value to TRUE. + +**PMOAMBackwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the backward direction by setting the value to TRUE. + +#### *Relationships* + +Zero or one instance of the vcTTPF managed entity may exist for each instance of a vcCTPF managed entity. A vcTrailF is terminated by two vcTTPFs. + +### **8.146 vdslCTPF** + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. It terminates and originates a VDSL section link connection. + +#### *Relationships* + +One or more of these managed entities exist for each PhysicalPathTPF of type "VDSL". There is zero or more of these managed entities contained within an ONU or an NT FSAN NE. One of these managed entities exists for each vdslTTPF. + +### **8.147 vdslLayerNetworkDomainF** + +This managed entity is a type of layerNetworkDomainF and inherits all the attributes and relationships defined by layerNetworkDomainF. ITU-T Rec. G.993.1 defines the characteristic signal associated with this layer. + +### **8.148 vdslLinkConnectionF** + +This managed entity is a type of linkConnectionF and inherits all the attributes and relationships defined by linkConnectionF. This managed entity represents a VDSL link connection, derived from the G.852.2 definition, i.e., "the transparent capacity of transfer of information characterized by a given signal identification between two fixed points". Directionality is always set to "bidirectional". + +#### *Attributes* + +**SignalIdentification:** This fixed attribute describes the signal that is transferred across the link. Here, it is set to "VDSL". + +#### *Relationships* + +A topological link is a group of link connections sharing the same extremities. This relationship involves zero or more instances of the managed entity vdslLinkConnectionF. A vdslLinkConnectionF links two vdslCTPFs. + +### **8.149 vdslSubnetworkF** + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "VDSL". + +#### *Attributes* + +**ONUPtr:** This attribute identifies the associated ONU. + +**ContainedLinkList:** This attribute identifies the instances of vdslTopologicalLinkF contained in this subnetwork. + +### **8.150 vdslTopologicalLinkEndF** + +This managed entity is a type of topologicalLinkEndF and inherits all the attributes and relationships defined by topologicalLinkEndF. Signal identification is set to "VDSL". + +### 8.151 vdslTopologicalLinkF + +This managed entity is a type of topologicalLinkF and inherits all the attributes and relationships defined by topologicalLinkF. Signal identification is set to "VDSL". + +### 8.152 vdslTrailF + +This managed entity is a type of trailF and inherits all the attributes and relationships defined by trailF. + +#### *Relationships* + +Each vdslTrailF is terminated by vdslTTPs. + +### 8.153 vdslTTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It terminates and originates a VDSL section trail. The following alarms can be detected at this managed entity: Loss of Frame (LOF), Remote Failure Indication (RFI), Signal Degraded (SD) fast datastream, Signal Degraded (SD) interleave datastream, Signal Degraded (SD) fast datastream far end, Signal Degraded (SD) interleave datastream far end, Initialization failed (detected by dataInitFailure, configInitFailure, protocolInitFailure, noPeerAtuPresent), Loss of Link, and Loss of Power. + +#### *Attributes* + +**TcAdaptorPtr:** This attribute points to the tcAdaptor managed entity that uses this managed entity as a server trail. + +#### *Relationships* + +There is zero or more of these managed entities contained within an ONU or an NT FSAN NE. One of these managed entities exists for each vdslCTPF managed entity. One of these managed entities exists for each PhysicalPathTPF of Type "VDSL". + +### 8.154 voiceCTPF + +This managed entity is a type of CTP and inherits all the attributes and relationships defined by CTP. It represents the point in the FSAN NE where the voice channel is terminated/originated. The attribute PointDirectionality has the value "bidirectional". + +#### *Attributes* + +**TelephoneNumber:** This attribute provides the network owner supplied value for the end user telephone number. + +**SSCSParameterProfile2Ptr:** This attribute identifies the SSCS parameter values used to provision this voice connection if AAL2 is employed. + +**InterworkingVCCTPPtr:** This attribute identifies the interworking VCC carrying this voice channel. + +**ChannelId:** This attribute identifies the logical Channel Id for this service if AAL2 is employed. This attribute is null if another type of adaptation is employed. + +**SignallingCode:** This attribute specifies whether "loop start" or "ground start" signalling is employed. + +**RobbedBitSignalling:** This attribute describes the robbed bit signalling in use on the telephony port. Valid values include "a", "ab", "abcd", "transparent", and "other". + +**FlashInd:** This Boolean attribute indicates whether or not flash detection is enabled. + +**SilenceSuppressionInd:** This Boolean attribute indicates whether or not silence suppression is on or off. + +**EchoCancelInd:** This Boolean attribute indicates whether or not echo cancellation is on or off. + +**VoiceCompressionType:** This attribute identifies the voice compression applied to the voice channel. Valid values include but are not limited to the following: PCM-64, ADPCM-32, LD-CELP16, CS-ACELP8, unknown. + +**VoiceInterfaceGroupPtr:** This attribute identifies the GR-303 interface group to which this voice channel belongs. + +**CRVIndex:** This attribute identifies the Call Reference Value within the Voice Interface Group associated with this voice circuit. + +#### *Relationships* + +Zero or more of these instances is associated with an ONT. One of these managed entities exists for each voiceCTPF. One or more of these instances is associated with a voice channel. + +### **8.155 voiceLayerNetworkDomainF** + +This managed entity is a type of LayerNetworkDomainF and inherits all the attributes and relationships defined by LayerNetworkDomainF. Characteristic information provided in this layer is set to "Voice". + +### **8.156 voicePMHistoryDataF** + +This is a managed entity that contains the past performance monitoring data collected as a result of monitoring a voice port on an ONT. Instances of this managed entity are created automatically whenever the client requests performance monitoring or NMS at the associated voiceCTPF managed entity and the data collection interval is completed. + +#### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**VoiceCTPPtr:** This attribute identifies the monitoring point. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**IncomingCallAttempts:** This attribute provides the cumulative count of incoming call attempts for this voice port. + +**OutgoingCallAttempts:** This attribute provides the cumulative count of outgoing call attempts for this voice port. + +**VoicePortBufferOverflows:** A count of the number of times that the voice port buffer overflows. + +**VoicePortBufferUnderflows:** A count of the number of times that the voice port buffer underflows. + +### *Relationships* + +Zero or more instances of this managed entity shall exist for each instance of a voiceCTPF. + +#### **8.157 voiceServiceProfileAAL1F** + +This managed entity is used to organize data that describes the Voice Service functions of the FSAN NE if supported by AAL1. Instances of this managed entity are created and deleted at the request of the managing system or operator. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AnnouncementType:** This attribute provides the announcement to the customer going off-hook when no call has been attempted. Valid values include but are not limited to "silence", "reorderTone", "fastBusy", "voiceAnnouncement". + +### *Relationships* + +This managed entity may be associated to zero or more instances of an interworking vcCTPF terminating AAL1 and carrying voice services. + +#### **8.158 voiceServiceProfileAAL2F** + +This managed entity is used to organize data that describes the voice service functions of the FSAN NE if supported by AAL2. Instances of this managed entity are created and deleted by request of the managing system or operator. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**AnnouncementType:** This attribute provides the announcement to the customer going off-hook when no call has been attempted. Valid values include but are not limited to "silence", "reorderTone", "fastBusy", "voiceAnnouncement". + +**JitterTarget:** This attribute provides the target value of the jitter buffer. The system will try to maintain the jitter buffer at the target value. Units are in milliseconds. + +**JitterBufferMax:** This attribute provides the maximum depth of the jitter buffer associated with this service. Units are in milliseconds. + +**TimingReference:** This attribute defines how the internal timing is derived. Valid values include "Network Timing Reference", "Adaptive Voice", and "Free Run". + +### *Relationships* + +This managed entity may be associated to zero or more instances of an interworking vcCTPF terminating AAL2 and carrying voice services. + +#### **8.159 voiceSubnetworkConnectionF** + +This managed entity is a type of SubnetworkConnectionF and inherits all the attributes and relationships defined by SubnetworkConnectionF. If the FSAN system has a non-integrated voice gateway, then this managed entity is never instantiated. Characteristic information provided in this layer is set to "Voice". A voiceSubnetworkConnectionF is terminated by two voiceCTPFs. + +### 8.160 voiceSubnetworkF + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. If a system has a non-integrated voice gateway, then this managed entity cannot be further decomposed. Characteristic information provided in this layer is set to "Voice". + +### 8.161 voiceTTPF + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It represents the point in FSAN network where the voice trail terminated or originates. The following alarms can be detected at this managed entity: Alarm Indication Signal (AIS) and Remote Defect Indication (RDI). The attribute PointDirectionality has the value "bidirectional". + +#### *Attributes* + +**TelephoneNumber:** This attribute provides the network-owner-supplied value for the end-user telephone number. + +**InterworkingVCCTPPtr:** This attribute identifies the interworking VCC carrying this voice channel. + +**ChannelId:** This attribute identifies the logical Channel Id for this service if AAL2 is employed. This attribute is null if another type of adaptation is employed. + +#### *Relationships* + +Zero or one instance of the voiceTTPF managed entity may exist for each instance of a voiceCTPF managed entity. One or more of these instances is associated with a voice channel on an ONT. + +### 8.162 vpCTPF + +This managed entity is a type of CTPF and inherits all the attributes and relationships defined by CTPF. This managed element is used to represent the termination of vpLinkConnectionF on an FSAN NE and (possibly) vpSubnetworkConnections. A Traffic descriptor profile is used to characterize this managed entity. It represents the point in the FSAN NE where the virtual private connection and associated overhead (F4 OAM cells) are terminated/originated. The following alarms can be detected at this managed entity: Alarm Indication Signal (AIS) and Remote Defect Indication (RDI). + +#### *Attributes* + +**VPIValue:** This attribute identifies the VPI values associated with this vpCTPF. + +**AlarmSeverityAssignmentProfileFPtr:** This attribute provides a pointer relationship to an alarmSeverityAssignmentProfileF managed entity. + +**AlarmStatus:** This attribute provides information to the managing system on the alarm condition of the managed entity. Valid values include "under repair", "critical", "major", "minor", "alarm outstanding", and "null". Interpretation of these values is found in ITU-T Rec. X.731. + +**IngressTrafficDescriptorProfilePtr:** This attribute identifies the ingress trafficDescriptorProfileF object associated with configuration of this TP. + +**EgressTrafficDescriptorProfilePtr:** This attribute identifies the egress trafficDescriptorProfileF object associated with configuration of this TP. + +**IngressQualityOfServiceProfilePtr:** This attribute identifies the ingress qualityOfServiceProfileF object associated with configuration of this TP. + +**EgressQualityOfServiceProfilePtr:** This attribute identifies the egress qualityOfServiceProfileF object associated with configuration of this TP. + +**SupportedServiceCategories:** This attribute specifies the set of service categories that are supported by the virtual path for virtual channel connections. + +**PropagationDelay:** This attribute indicates the expected propagation delay (in micro seconds). + +**SegmentEndpoint:** This Boolean attribute indicates whether or not the termination point has been configured to represent a segment end point. + +**PMOAMMethod:** This attribute indicates the method used to set up and terminate the PM OAM monitoring activity. Valid values are "TMN", "OAM", or "notSupported". If the value is "notSupported", then PM OAM is not supported on the end point. + +**PMOAMDirection:** This attribute indicates the desired direction(s) of transmission to monitor PM OAM. Valid directions are: away from activator (transmit), towards activator (receive), or both. + +**PMOAMBlockSize:** This attribute indicates the PM OAM nominal block size choice for both the receive and transmit directions. + +**PMOAMForwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the forward direction by setting the value to TRUE. + +**PMOAMBackwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the backward direction by setting the value to TRUE. + +### *Relationships* + +Zero or more instances of the vpCTPF managed entity shall exist for each instance of a FSAN NE. One instance of the vpCTPF shall exist for each instance of vpTTPF. Two of these management entities are associated with every vpLinkConnectionF. Zero or more of these managed entities may be associated with a vpSubnetworkConnectionF. + +## **8.163 vpLayerNetworkDomainF** + +This managed entity is a type of layerNetworkDomainF and inherits all the attributes and relationships defined by layerNetworkDomainF. Characteristic information provided in this layer is set to "VP". + +## **8.164 vpLinkConnectionF** + +This managed entity is a type of linkConnectionF and inherits all the attributes and relationships defined by linkConnectionF. This managed entity represents an I.326 link connection, derived from the G.852.2 definition, i.e., "the transparent capacity of transfer of information characterized by a given signal identification between two fixed points." Directionality is always set to "bidirectional". + +### *Attributes* + +**SignalIdentification:** This fixed attribute describes the signal that is transferred across the link. Here, it is set to "VP". + +**RetainedResource:** This Boolean attribute indicates if the managed entity instance needs to be retained when it is a component of a composite connection (involving a set of link connections and subnetwork connections) that has been deleted or when supporting a trail that has been deleted. + +**CompositePtr:** This pointer attribute identifies the vcSubnetworkConnectionF managed entity to which this managed entity belongs. It may be the null pointer. + +### *Relationships* + +A topological link is a group of link connections sharing the same extremities. This relationship involves zero or more instances of the vpLinkConnectionF managed entity. A vpLinkConnectionF link is established between two vpCTPFs. + +#### **8.165 vpLogicalLinkF** + +This managed entity is a type of logicalLinkF and inherits all the attributes and relationships defined by logicalLinkF. Signal identification is set to "VP". It contains vpLinkConnectionFs for the purposes of DBA management. LinkDirectionality is unidirectional from ONT/ONU to OLT. Note that although a contained vpLinkConnectionF is bidirectional, only its upstream part from ONT/ONU to OLT is affected by this vpLogicalLinkF. + +#### **8.166 vpSubnetworkConnectionF** + +This managed entity is a type of subnetworkConnectionF and inherits all the attributes and relationships defined by subnetworkConnectionF. + +### *Attributes* + +**ComponentPtrList:** This pointer attribute identifies the vpSubnetworkConnectionF(s) and vpLinkConnectionF(s) that comprise this vpSubnetworkConnectionF. It may be the null pointer. + +**CompositePtr:** This pointer attribute identifies the vpSubnetworkConnectionF managed entity to which this managed entity belongs. It may be the null pointer. + +#### **8.167 vpSubnetworkF** + +This managed entity is a type of subnetworkF and inherits all the attributes and relationships defined by subnetworkF. Signal identification is set to "VP". + +### *Attributes* + +**OLTPtr:** This attribute identifies the associated OLT. + +**ContainedLinkList:** This attribute identifies the instances of vpTopologicalLinkF contained in this subnetworkF. + +**ContainedSubnetworkList:** This attribute identifies the instances of vpSubnetworkF contained in this subnetworkF. + +**LinkPtrList:** This attribute identifies the instances of vpTopologicalLinkF terminated by this subnetworkF. + +### *Relationships* + +One or more of these managed entities exist for each installed or pre-provisioned FSAN NE. + +#### **8.168 vpTopologicalLinkEndF** + +This managed entity is a type of topologicalLinkEndF and inherits all the attributes and relationships defined by topologicalLinkEndF. This managed entity is used to represent the termination of a topological link at the VP-layer. In the vpLayerNetworkDomainF, a vpTopologicalLinkEndF represents an ATM interface associated with the underlying transport facility. The PointDirectionality attribute will be either "sink" or "source". + +### *Attributes* + +**LinkTPTType:** Describes the interface type that the managed entity supports: UNI, inter-NNI, intra-NNI, or unconfigured. + +**LoopbackLocationIdentifier:** A code used for OAM cell loopback purposes. Incoming OAM Loopback cells with a Loopback Location field value that matches the value of the loopbackLocationIdentifier attribute shall be looped-back over the interface. + +**SupportedByPlug-inF:** This attribute identifies the interface circuit pack to which this managed entity is associated. + +**PortId:** This attribute indicates port Id on the plug-in associated with the vpTopologicalLinkEndF. + +**CellScramblingEnable:** This attribute allows cell scrambling to be activated or deactivated on the ATM Interface represented by the vcTopologicalLinkEndF. + +### *Relationships* + +Each vpTopologicalLinkF may be terminated by two instances of the vpTopologicalLinkEndF managed entity. One vpTopologicalLinkEndF managed entity is associated with one or more vpSubnetworkFs. Each vpTopologicalLinkEndF may be supported by one instance of a server APONTTP managed entity in the server layer. vpCTPFs are contained in vpTopologicalLinkEndF. + +## **8.169 vpTopologicalLinkF** + +This managed entity is a type of topologicalLinkF and inherits all the attributes and relationships defined by topologicalLinkF. Signal identification is set to "VP". + +### *Attributes* + +**RestorationMode:** This attribute is used to configure the restoration mode of a link as: unavailable for routing and re-routing, available for routing and not re-routing; available for re-routing and not routing; or available for both routing and rerouting. + +## **8.170 vpTrailF** + +This managed entity is a type of trailF and inherits all the attributes and relationships defined by trailF. This managed entity represents an I.326-defined trail in the VP layer domain. The vpTrailF is always bidirectional. + +### *Attributes* + +**RestoreableInd:** This attribute is used to identify the connection as restorable or not. + +**ClientLinkList:** This attribute is used to identify the vpLinkConnectionFs supported by the vpTrailF. + +### *Relationships* + +Each vpTrailF is terminated by at least two vpTTPFs. + +## **8.171 vpTTPF** + +This managed entity is a type of TTPF and inherits all the attributes and relationships defined by TTPF. It represents the point in the ATM subnetwork where the vpTrail and associated overhead (F4 OAM cells) are terminated/originated. The following alarms can be detected at this managed entity: Alarm Indication Signal (AIS) and Remote Defect Indication (RDI). + +### *Attributes* + +**PMOAMMethod:** This attribute indicates the method used to setup and terminate the PM OAM monitoring activity. Valid values are "TMN", "OAM", or "notSupported". If the value is "notSupported", then PM OAM is not supported on the end point. + +**PMOAMDirection:** This attribute indicates the desired direction(s) of transmission to monitor PM OAM. Valid directions are: away from activator (transmit), towards activator (receive), or both. + +**PMOAMBlockSize:** This attribute indicates the PM OAM nominal block size choice for both the receive and transmit directions. + +**PMOAMForwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the forward direction by setting the value to TRUE. + +**PMOAMBackwardActive:** This Boolean attribute is used to initiate generation of PM OAM cells in the backward direction by setting the value to TRUE. + +### *Relationships* + +Zero or one instance of the vpTTPF managed entity may exist for each instance of a vpCTPF managed entity. A vcTrailF is terminated by two vpTTPFs. + +## **8.172 vpvcPMHistoryDataF** + +This is a managed entity that contains the historical performance monitoring data collected for a VPC or VCC connection, related to VP and VC OAM flows. Instances of this managed entity are created automatically whenever the client requests performance monitoring or NMS for the VPC connection managed entity and a data collection interval is completed. + +### *Attributes* + +**ManagedEntityId:** This attribute provides a unique name for the managed entity instance. + +**CTPFPtr:** This attribute identifies the associated vpCTPF or vcCTPF managed entity where performance monitoring occurs. + +**SuspectIntervalFlag:** This attribute is used to indicate that the performance data for the current period may not be reliable. + +**ThresholdDataName:** This attribute provides the name of the Threshold Data profile containing the threshold values for the performance monitoring data contained in this managed entity. + +**PeriodEndTime:** This attribute records the time at the end of the data collection interval. + +**Lost0+1UserInformationCells:** This attribute measures background cell loss. It cannot distinguish between cells lost because of header bit errors, ATM-level header errors, cell policing, or buffer overflows. It records only loss of genuine user information independent of the priority of the user cell. + +**Lost0UserInformationCells:** This attribute measures background cell loss. It cannot distinguish between cells lost because of header bit errors, ATM-level header errors, cell policing, or buffer overflows. It records only loss of genuine user information of high priority. + +**MisinsertedUserInformationCells:** This attribute is used to measure small occurrences of when a cell is mis-routed to an active VP/VC that is being monitored. + +**Transmitted0+1UserInformationCells:** A count of all the user cells that are originated at a monitored connection by the transmitting end point (i.e., backward reporting is assumed). + +**Transmitted0UserInformation Cells:** A count of all the user cells of high priority that are originated at a monitored connection by the transmitting end point (i.e., backward reporting is assumed). + +**ImpairedBlock:** The severely errored cell block counter will be incremented whenever one of the following events takes place: the number of misinserted user cells exceeds $M_{\text{misinserted}}$ , the number of bipolar violations exceeds $M_{\text{errored}}$ , or the number of lost user cells exceeds $M_{\text{lost}}$ . + +#### *Relationships* + +Zero or more instance of this managed entity shall exist for each instance of the associated TPF managed entity. + +## Annex A + +### Tables of possible faults + +#### A.1 DCN alarms for the FSAN element management system + +**Table A.1/Q.834.1 – DCN alarms** + +| Problem group | Problem | Detected by 7 | | Generated notification | | | Caused by attribute value | +|---------------|-------------------------|--------------------------|-----------------|------------------------|-------------------------------------------|------------------|-----------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| DCN | Communication error if1 | NML (-OS) | physicalPathTPF | Communication | Communication subsystem failure/LAN error | Major | Attributes are protocol dependent | +| | Communication error if2 | EML (-OS) | physicalPathTPF | Communication | Communication subsystem failure/LAN error | Major | Attributes are protocol dependent | + +--- + +7 "Detected by" column shows managed entities that detect the alarm. + +## A.2 Equipment alarms + +**Table A.2/Q.834.1 – Equipment alarms** + +| Problem group | Problem | Detected by 7 | | Generated notification | | | Caused by attribute value | +|---------------|---------------------------------------------|--------------------------|----------------|------------------------|--------------------------|------------------|-------------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| Equipment | Functional failure on an internal interface | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Equipment | Equipment malfunction | Critical | Equipment alarm | +| | Loss of external power | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Equipment | Power problem | Major | Powering alarm | +| | Voltage dropped below defined threshold | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Equipment | Battery problem | Major | Battery alarm | +| | Room/cabinet/enclosure door open | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Environmental | Door open | Major | Door open | +| | Fire detected | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Environmental | Fire detected | Major | Fire | +| | Humidity too high | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Environmental | Humidity | Minor | Humidity | +| | Temperature high/low | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Environmental | Temperature unacceptable | Minor | Temperature high
Temperature low | +| | Heating/ventilation/cooling system problem | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Environmental | See Problem | Minor | See Problem | +| | Environment flooded | OLT/ONT/ONU/NT | OLT/ONT/ONU/NT | Environmental | Flood detected | | Flood detected | + +**Table A.2/Q.834.1 – Equipment alarms** + +| Problem group | Problem | Detected by 7 | | Generated notification | | | Caused by attribute value | +|-----------------------------|------------------------------------------------------------|--------------------------|------------------|------------------------|-------------------------|------------------|---------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| Subscriber line card Holder | Configured plug-in Line Interface Module (LIM) not present | OLT/NT | EquipmentHolderF | Equipment | Line-card not present | Minor | Line-card not present | +| | Inserted plug-in LIM wrong type | OLT/NT | EquipmentHolderF | Equipment | Line-card mismatch | Minor | Line-card mismatch | +| Subscriber line card | Failure on an internal interface or failed selftest | OLT/NT | pluginUnitF | Equipment | Line-card malfunction | Major | Self-test failed | +| | LIM fuse failure or failure on LIM DC/DC converter | OLT/NT | pluginUnitF | Equipment | Line-card power problem | Major | Line-card power problem | + +**Table A.3/Q.834.1 – Network faults** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|-----------------------------------------------------------------------|---------------------------------------------------|-----------------|---------------------|------------------------|------------------------|------------------|---------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| PH Layer
SDH SNI
ATM-UNI
(SDH and Sonet)
ITU-T Rec. G.774 | Loss of communication bidirectional section level | OLT/ONT/NT | Physical PathTPF | Communication | LOS | Critical | LOS | +| | | OLT/ONT/NT | rsTTPF | Communication | LOF | Critical | LOF | +| | | OLT/ONT/NT | msTTPF | Communication | AIS | Major | ms-AIS | +| | Loss of communication far-end section level | OLT/ONT/NT | msTTPF | Communication | RDI | Minor | ms-RDI | +| | Bit errors section level | OLT/ONT/NT | msTTPF | Communication | SD | Warning | ms-SD | +| | Bit errors far-end section level | OLT/ONT/NT | msTTPF | Communication | SD far end | Warning | ms-SD far end | +| | Loss of communication bidirectional path level | OLT/ONT/NT | au3CTPF/
au4CTPF | Communication | LOP | Critical | au-LOP | +| | Bit errors far-end section level | OLT/ONT/NT | au3CTPF/
au4CTPF | Communication | AIS | Major | au-AIS | +| | Loss of communication far-end path level | OLT/ONT/NT | vc3TTPF/
vc4TTPF | Communication | RDI | Minor | path-RDI | +| | Bit errors path level | OLT/ONT/NT | vc3TTPF/
vc4TTPF | Communication | SD | Warning | path-SD | +| | Bit errors far-end path level | OLT/ONT/NT | vc3TTPF/
vc4TTPF | Communication | SD far end | Warning | path-SD far end | +| | Wrong path | OLT/ONT/NT | vc3TTPF/
vc4TTPF | Communication | Path Trace ID Mismatch | Critical | TIM (Trace Identifier Mismatch) | + +**Table A.3/Q.834.1 – Network faults** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|---------------------------------------------------------|-------------------------------------|-----------------|---------------------|------------------------|---------------------|------------------|---------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| | Wrong signal | OLT/ONT/NT | vc3TTPF/
vc4TTPF | Communication | Payload Mismatch | Critical | PLM (Payload Mismatch) | +| | Transmitter failure | OLT/ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Warning | Laser Bias High | +| | | OLT/ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Minor | Laser Power High | +| | | OLT/ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Minor | Laser Power Low | +| PH Layer SDH (ATM UNI Cell based)
ITU-T Rec. I.432.2 | Loss of communication bidirectional | ONT/NT | PhysicalPathTPF | Communication | LOS | Major | LOS | +| | Loss of maintenance flow | ONT/NT | cellBasedTTPF | Communication | LOM | Major | Loss of PLOAM-Cell | +| | Loss of maintenance flow | ONT/NT | cellBasedTTPF | Communication | AIS | Minor | AIS | +| | Bit errors | ONT/NT | cellBasedTTPF | Communication | SD | Warning | SD | +| | Loss of communication far end | ONT/NT | cellBasedTTPF | Communication | RDI | Minor | RDI | +| | Transmitter failure | ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Warning | Laser Bias High | +| | | ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Minor | Laser Power High | +| | | ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Minor | Laser Power Low | + +Table A.3/Q.834.1 – Network faults + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|--------------------------------------------------|--------------------------------------------------------|-----------------|-----------------|------------------------|------------------------|------------------|----------------------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| PH Layer
PON (OLT Side)
ITU-T Rec. G.983.2 | Loss of communication bidirectional | OLT | PhysicalPathTPF | Communication | LOS | Critical | LOSi | +| | | OLT | aponTTP | Communication | Loss of physical layer | Critical | LOAi
(Loss of acknowledgement) | +| | | OLT | aponTTP | Communication | Loss of physical layer | Critical | OAMLi
(PLOAM cell loss) | +| | | OLT | aponTTP | Communication | Loss of physical layer | Critical | CPEi
(Cell Phase Error) | +| | Bit errors | OLT | aponTTP | Communication | SDi | Minor | SDi | +| | Bit errors far end (ONU i ) | OLT | aponTTP | Communication | SDi fare end | Minor | SDi far end | +| | Activation of communication to ONU i failed | OLT | aponTTP | Communication | Loss of physical layer | Critical | SUFi (Start up failure) | +| | Power shutdown in ONU i | OLT | aponTTP | Communication | Loss of physical layer | Critical | REC-INH (Receive Alarm inhibition) | +| | ONU i unable to transfer ATM cells | OLT | aponTTP | Equipment | Transmit failure | Critical | PEEi (Physical Equipment Error) | +| | Link mismatch of ONU i | OLT | aponTTP | Communication | Link mismatch | Critical | MISi
(Link mismatch of ONU i ) | + +**Table A.3/Q.834.1 – Network faults** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|-------------------------|------------------------------------------------------------------|-----------------|-----------------|------------------------|---------------------------------|------------------|---------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| | Transmitter failure OLT | OLT | PhysicalPathTPF | Equipment | Transmitter failure | Minor | Laser Bias High | +| | | OLT | PhysicalPathTPF | Equipment | Transmitter failure | Critical | Laser Power High | +| | | OLT | PhysicalPathTPF | Equipment | Transmitter failure | Major | Laser Power Low | +| PH Layer PON – ONU Side | Transmitter failure ONU i (no message to OLT defined) | ONU/ONT | PhysicalPathTPF | Equipment | Transmitter failure | Minor | Laser Bias High | +| | | ONU/ONT | PhysicalPathTPF | Equipment | Transmitter failure | Critical | Laser Power High | +| | | ONU/ONT | PhysicalPathTPF | Equipment | Transmitter failure | Major | Laser Power Low | +| PH Layer ADSL | Loss of communication bidirectional | ONU | PhysicalPathTPF | Communication | LOS | Critical | LOS | +| | | ONU | ADSLTTPF | Communication | LOF | Critical | LOF | +| | Loss of communication far end (NT) | ONU | ADSLTTPF | Communication | RFI (Remote Failure Indication) | Critical | RFI (Remote Failure Indication) | +| | Bit errors (Fast) | ONU | ADSLTTPF | Communication | SD (fast) | Minor | SD (fast) | +| | Bit errors (Interleave) | ONU | ADSLTTPF | Communication | SD (interleave) | Minor | SD (interleave) | +| | Bit errors far end (Fast) (NT) | ONU | ADSLTTPF | Communication | SD far end (fast) | Minor | SD far end (fast) | +| | Bit errors far end (Interleave) (NT) | ONU | ADSLTTPF | Communication | SD far end (interleave) | Minor | SD far end (interleave) | + +Table A.3/Q.834.1 – Network faults + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|---------------|------------------------------------------|-----------------|-----------------|------------------------|---------------------------------|------------------|---------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| | Activation of communication to NT failed | ONU | ADSLTTPF | Communication | Initialization failed | Critical | dataInitFailure | +| | | ONU | ADSLTTPF | | | | configInitFailure | +| | | ONU | ADSLTTPF | | | | protocolInitFailure | +| | | ONU | ADSLTTPF | | | | noPeerAtuPresent | +| | Deactivated communication from NT (NT) | ONU | ADSLTTPF | Communication | Loss of Link | Major | Loss of Link | +| | Loss of power far end (NT) | ONU | ADSLTTPF | Equipment | Power problem | Major | Loss of Power | +| PH Layer VDSL | Loss of communication bidirectional | ONU | PhysicalPathTPF | Communication | LOS | Critical | LOS | +| | | ONU | VDSLTPF | Communication | LOF | Critical | LOF | +| | Loss of communication far end (NT) | ONU | VDSLTPF | Communication | RFI (Remote Failure Indication) | Critical | RFI (Remote Failure Indication) | +| | Bit errors (Fast) | ONU | VDSLTPF | Communication | SD (fast) | Minor | SD (fast) | +| | Bit errors (Interleave) | ONU | VDSLTPF | Communication | SD (interleave) | Minor | SD (interleave) | +| | Bit errors far end (Fast) (NT) | ONU | VDSLTPF | Communication | SD far end (fast) | Minor | SD far end (fast) | +| | Bit errors far end (Interleave) (NT) | ONU | VDSLTPF | Communication | SD far end (interleave) | Minor | SD far end (interleave) | + +**Table A.3/Q.834.1 – Network faults** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|---------------|------------------------------------------|-----------------|----------------|------------------------|-----------------------|------------------|---------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| | Activation of communication to NT failed | ONU | VDSLTTTF | Communication | Initialization failed | Critical | dataInItFailure | +| | | ONU | VDSLTTTF | | | | configInItFailure | +| | | ONU | VDSLTTTF | | | | protocolInItFailure | +| | | ONU | VDSLTTTF | | | | noPeer AtuPresent | +| | Deactivated communication from NT (NT) | ONU | VDSLTTTF | Communication | Loss of Link | Major | Loss of Link | +| | Loss of power far end (NT) | ONU | VDSLTTTF | Equipment | Power problem | Major | Loss of Power | + +**Table A.3/Q.834.1 – Network faults** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|-------------------------------------------------|--------------------------------------------|--------------------|-------------------------------------|------------------------|---------------------|------------------|---------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| Circuit emulation service UNI | Loss of communication bidirectional | ONT/NT | PhysicalPathTPF | Communication | LOS | Critical | LOS | +| | | ONT/NT | DS1TTPF, E1TTPF
DS3TTPF, E3TTPF | Communication | LOF | Critical | Loss of PLOAMCell | +| | | ONT/NT | DS1TTPF, E1TTPF
DS3TTPF, E3TTPF | Communication | AIS | Critical | AIS | +| | Bit errors | ONT/NT | DS1TTPF, E1TTPF
DS3TTPF, E3TTPF | Communication | SD | Minor | SD | +| | Loss of communication far end | ONT/NT | DS1TTPF, E1TTPF,
DS3TTPF, E3TTPF | Communication | RAI | Critical | RAI | +| | Transmitter failure (if optical interface) | ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Minor | Laser Bias High | +| | | ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Critical | Laser Power High | +| | | ONT/NT | PhysicalPathTPF | Equipment | Transmitter failure | Major | Laser Power Low | +| TC-Adapter | Loss of communication | OLT/ONT/
ONU/NT | tcAdaptorF | Communication | LCD | Critical | Loss of Cell delineation | +| ATM Layer "Inter-working VPC Termination Point" | Loss of communication bidirectional | OLT/ONT/
ONU/NT | vpCTPF | Communication | AIS | Major | VP AIS | +| | Loss of communication far end | OLT/ONT/
ONU/NT | vpCTPF | Communication | RDI | Minor | VP RDI | + +**Table A.3/Q.834.1 – Network faults** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|-------------------------------------------------|-------------------------------------|-----------------|----------------|------------------------|----------------|------------------|---------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| ATM Layer, VP level | Loss of communication bidirectional | OLT/ONT/ONU/NT | vpTTPF | Communication | AIS | Major | VP AIS | +| | Loss of communication far end | OLT/ONT/ONU/NT | vpTTPF | Communication | RDI | Minor | VP RDI | +| ATM Layer "Inter-working VCC Termination Point" | Loss of communication bidirectional | OLT/ONT/NT | vcCTPF | Communication | AIS | Major | VC AIS | +| | Loss of communication far end | OLT/ONT/NT | vcCTPF | Communication | RDI | Minor | VC RDI | +| ATM Layer, VC level | Loss of communication bidirectional | OLT/ONT/NT | vcTTPF | Communication | AIS | Major | VC AIS | +| | Loss of communication far end | OLT/ONT/NT | vcTTPF | Communication | RDI | Minor | VC RDI | + +### A.3 Quality of Service alarms + +Table A.4/Q.834.1 – QoS alarms + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|----------------------|------------------------------------------------------|-----------------|---------------------|------------------------|-----------------------------------|------------------|-----------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| ATM Adoption Layer 1 | Header errors threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | Header errors | Minor | Header errors | +| | Sequence Violation threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | Sequence Violation | Minor | Sequence Violation | +| | Cell loss threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | Cell loss | Minor | Cell loss | +| | Cell misinsertion threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | Cell misinsertion | Minor | Cell misinsertion | +| | Buffer Underflows threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | Buffer Underflows | Minor | Buffer Underflows | +| | Buffer Overflows threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | Buffer Overflows | Minor | Buffer Overflows | +| | STD Pointer Reframes threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | STD Pointer Reframes | Minor | STD Pointer Reframes | +| | STD Pointer Parity Check Failures threshold crossing | OLT/NT | AAL1PM CurrentDataF | Quality of Service | STD Pointer Parity Check Failures | Minor | STD Pointer Parity Check Failures | +| | Cell starvation alarm | OLT/NT | AAL1PM CurrentDataF | Quality of Service | CSA | Minor | CSA | + +**Table A.4/Q.834.1 – QoS alarms** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|----------------------|-------------------------------------------------|-----------------|----------------------------------|------------------------|------------------------------|------------------|------------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| ATM Adoption Layer 5 | Threshold crossing Invalid Field | OLT/NT | AAL5PM CurrentDataF | Quality of Service | Invalid Field | Minor | Invalid Field | +| | Threshold crossing CRC Violation | OLT/NT | AAL5PM CurrentDataF | Quality of Service | CRC Violation | Minor | CRC Violation | +| | Threshold crossing Reassembly Timer Expirations | OLT/NT | AAL5PM CurrentDataF | Quality of Service | Reassembly Timer Expirations | Minor | Reassembly Timer Expirations | +| Traffic Management | Threshold crossing maximum Queue Size | OLT/NT | priorityQueueF | Quality of Service | Priority Queue | Major | Maximum Queue Size | +| | Threshold crossing discarded cells | OLT/NT | upcNpc Disagreement CurrentDataF | Quality of Service | Discarded Cells | Warning | Discarded Cells | +| | Threshold crossing discarded CLP0 cells | OLT/NT | upcNpc Disagreement CurrentDataF | Quality of Service | Discarded CLP0 Cells | Minor | Discarded CLP0 Cells | +| ATM Layer VP/VC PM | Threshold crossing lost cells | OLT/ONT/ONU/NT | vpvcPMCurent DataF | Quality of Service | Lost cells | Minor | Lost cells | +| | Threshold crossing far end lost cells | OLT/ONT/NT | vpvcPMCurent DataF | Quality of Service | Far end lost cells | Minor | Far end lost cells | + +**Table A.4/Q.834.1 – QoS alarms** + +| Problem group | Problem | Detected by | | Generated notification | | | Caused by attribute value | +|----------------------------------|--------------------------|-----------------|--------------------------------------------------------------------------|------------------------|----------------|------------------|---------------------------| +| | | Network element | Managed entity | Event type | Probable cause | Default severity | | +| Circuit Emulation Service UNI PM | Errored Seconds | OLT/NT | DS1PMCurrentDataF, DS3PMCurrentDataF, E1PMCurrentDataF, E3PMCurrentDataF | Quality of Service | ES | Minor | Errored Seconds | +| | Severely Errored Seconds | OLT/NT | DS1PMCurrentDataF, DS3PMCurrentDataF, E1PMCurrentDataF, E3PMCurrentDataF | Quality of Service | SES | Minor | Severely Errored Seconds | +| | Bursty Errored Seconds | OLT/NT | DS1PMCurrentDataF, DS3PMCurrentDataF, E1PMCurrentDataF, E3PMCurrentDataF | Quality of Service | BES | Minor | Bursty Errored Seconds | +| | Unavailable Seconds | OLT/NT | DS1PMCurrentDataF, DS3PMCurrentDataF, E1PMCurrentDataF, E3PMCurrentDataF | Quality of Service | UAS | Minor | Unavailable Seconds | +| | Controlled Slip Seconds | OLT/NT | DS1PMCurrentDataF, DS3PMCurrentDataF, E1PMCurrentDataF, E3PMCurrentDataF | Quality of Service | CSS | Minor | Controlled Slip Seconds | + +## Annex B + +### Communication network + +![Diagram of PON network layer structure (OLT-ONT) showing OLT and ONT-n components and their connections to various network layers.](80a44321a02e8a7d638ac9d53e88772c_img.jpg) + +The diagram illustrates the PON network layer structure between an OLT (Optical Line Terminal) and an ONT-n (Optical Network Terminal-n). + +**OLT Structure:** + +- VC-CTP:** Contains vpVcPM CurrentData. +- VP-TTP:** Contains vpVcPM CurrentData. +- VC-CC:** Connects VC-CTP and VP-TTP. +- VP-CC:** Connects VP-TTP and VP-CTP. +- VP-CTP:** Contains vpVcPM CurrentData. +- TC-Adaption:** Connects VP-CTP and SDH. +- SDH:** Contains physicalPathTP, rsTTP, msTTP, au3CTP/au4CTP, and vc3TTP/vc4TTP. + +**ONT-n Structure:** + +- VC-TTP:** Contains vpVcPM CurrentData. +- VP-TTP:** Contains vpVcPM CurrentData. +- VP-CTP:** Contains upcNpcCurrentData and vpVcPM CurrentData. +- TC-Adaption:** Connects VP-CTP and ATM UNI. +- ATM UNI:** Contains Cell based: SDH based: rsTTP, msTTP, au3CTP/au4CTP, and vc3TTP/vc4TTP. +- AAL5:** Contains AAL5PM CurrentData and AAL5PM HistoryData. +- AAL1:** Contains AAL1PM CurrentData and AAL1PM HistoryData. +- Adaption:** Connects AAL5 and AAL1. +- LAN UNI:** Connects Adaption and Ethernet. +- Voice UNI:** Connects Adaption and ATM-25. +- CES UNI:** Connects Adaption and ATM-25. + +**Connections:** + +- OLT SDH connects to SDH. +- OLT PON connects to PON. +- ONT-n PON connects to PON. +- ONT-n ATM UNI connects to ATM-25. +- ONT-n LAN UNI connects to Ethernet. +- ONT-n Voice UNI connects to ATM-25. +- ONT-n CES UNI connects to ATM-25. + +**NOTE –** The suffix "F" in TPs is curtailed for simplicity. + +G.834.1\_FB1 + +Diagram of PON network layer structure (OLT-ONT) showing OLT and ONT-n components and their connections to various network layers. + +**Figure B.1/Q.834.1 – PON network layer structure (OLT-ONT)** + +![Diagram of PON network layer structure (OLT-ONT) showing OLT, ONU-n, and NT-n components and their connections.](49d7bfbc65a92a7e1bd61777326a212d_img.jpg) + +The diagram illustrates the network layer structure for a PON network, divided into three main sections: OLT (Optical Line Terminal), ONU-n (Optical Network Unit), and NT-n (Network Terminal). + +**OLT Section:** + +- VC-CTP:** Contains *vpVcPM CurrentData*. +- VP-TTP:** Contains *vpVcPM CurrentData*. +- VP-CTP:** Contains *vpVcPM CurrentData*. +- TC-Adaption:** Contains *physicalPathTP*. +- SDH:** Contains *physicalPathTP*, *rsTTP*, *msTTP*, *au3CTP/au4CTP*, and *vc3TTP/vc4TTP*. + +**ONU-n Section:** + +- VC-CTP:** Contains *vpVcPM CurrentData*. +- TC-Adaption:** Contains *physicalPathTP*. +- PON:** Contains *physicalPathTP*. + +**NT-n Section:** + +- VC-TTP:** Contains *vpVcPM CurrentData*. +- VP-TTP:** Contains *vpVcPM CurrentData*. +- VP-CTP:** Contains *vpVcPM CurrentData*. +- TC-Adaption:** Contains *physicalPathTP*. +- ATM UNI:** Contains *Cell based:*, *SDH based:*, *rsTTP*, *msTTP*, *au3CTP/au4CTP*, and *vc3TTP/vc4TTP*. +- AAL5:** Contains *AAL5PM CurrentData* and *AAL5PM HistoryData*. +- AAL1:** Contains *AAL1PM CurrentData* and *AAL1PM HistoryData*. +- Adaption:** Contains *physicalPathTP*. +- LAN UNI:** Contains *physicalPathTP*. +- Voice UNI:** Contains *physicalPathTP*. +- CES UNI:** Contains *physicalPathTP*. + +**Connections:** + +- VC-CC:** Connects VC-CTP in OLT to VC-CTP in ONU-n. +- VP-CC:** Connects VP-CTP in OLT to VP-CTP in ONU-n. +- Physical Connections:** SDH, PON, xDSL, LAN UNI, Voice UNI, and CES UNI. + +**Legend:** + +- CES-UNI:** Cell-based UNI +- LL:** Local Loop +- Ethernet:** Ethernet +- ATM-25:** ATM-25 + +**NOTE –** The suffix "F" in TPs is curtailed for simplicity. + +G.834.1\_FB2 + +Diagram of PON network layer structure (OLT-ONT) showing OLT, ONU-n, and NT-n components and their connections. + +Figure B.2/Q.834.1 – PON network layer structure (OLT-ONT) + +## Annex C + +### Entity relationship diagram + +Notation is found in Figures C.1 to C.9. This notation is defined as follows: + +A ————— B    A is associated with B. Relationships can be indicated by pointer attributes that are listed on the line + +A ———— ◇ B    A is contained by B + +A ———— < B    B inherits from A + +## C.1 Inventory management + +![E-R diagram for inventory management showing entities NetworkF, NEFSAN, OLT, ONT, ONU, NT, EquipmentHolderF, plugInUnitF, and SoftwareF with their relationships.](1d62ade6b682fdfb8e192d10a06246a4_img.jpg) + +``` + + erDiagram + NetworkF ||--o{ NEFSAN : " " + NEFSAN ||--o{ OLT : " " + NEFSAN ||--o{ ONT : " " + NEFSAN ||--o{ ONU : " " + NEFSAN ||--o{ NT : " " + NEFSAN ||--o{ EquipmentHolderF : " " + NEFSAN ||--o{ SoftwareF : " " + OLT ||--o{ ONT : "upstreamNEFSAN" + ONT ||--o{ OLT : "subtendingNEFSANList" + ONU ||--o{ NT : "upstreamNEFSAN" + NT ||--o{ ONU : "subtendingNEFSANList" + EquipmentHolderF ||--o{ plugInUnitF : " " + EquipmentHolderF ||--o{ EquipmentHolderF : " " + plugInUnitF ||--o{ SoftwareF : " " + +``` + +The diagram illustrates the inventory management structure. At the top is the **NetworkF** entity, which is associated with the **NEFSAN** entity via a one-to-many relationship. The **NEFSAN** entity is associated with several other entities: **OLT**, **ONT**, **ONU**, **NT**, **EquipmentHolderF**, and **SoftwareF**. The **OLT** and **ONT** entities are associated with each other via a one-to-many relationship labeled *upstreamNEFSAN* and *subtendingNEFSANList*. Similarly, the **ONU** and **NT** entities are associated with each other via a one-to-many relationship labeled *upstreamNEFSAN* and *subtendingNEFSANList*. The **EquipmentHolderF** entity is associated with the **plugInUnitF** entity via a one-to-many relationship. The **EquipmentHolderF** entity also has a self-association. The **SoftwareF** entity is associated with the **plugInUnitF** entity via a one-to-many relationship. The **plugInUnitF** entity is associated with the **SoftwareF** entity via a one-to-many relationship. + +E-R diagram for inventory management showing entities NetworkF, NEFSAN, OLT, ONT, ONU, NT, EquipmentHolderF, plugInUnitF, and SoftwareF with their relationships. + +G.834.1\_FC1 + +Figure C.1/Q.834.1 – E-R diagram for inventory management + +## C.2 Termination points + +![E-R diagram for termination points showing the hierarchy from NEFSAN down to various CTPF and TTP entities.](cf75ef88724c24497dfe437c81b74325_img.jpg) + +The diagram illustrates the E-R relationships for termination points. At the top is the **NEFSAN** entity. It has several associations with other entities: + +- EquipmentHolderF**: Associated with NEFSAN and **plugInUnitF**. It is supported by **Plug-inF**. +- plugInUnitF**: Associated with NEFSAN and **PhysicalPortF**. It is used for integrated ONT/ONU. +- physicalPathTTP**: Associated with NEFSAN. It is supported by **Plug-inF** and has two specific cases: (in case of PON-side) and (in case of UNI/NNI-side). +- APONTTTP**: Associated with NEFSAN in the case of PON-side. +- cellBasedTTP**, **msTTP**, **DS3TTP**, **E3TTP**, and **vpTTPF**: Associated with NEFSAN in the case of UNI/NNI-side. + +Further down the hierarchy: + +- PhysicalPortF** is associated with **PhysicalPONPortF**. +- physicalPathTTP** is associated with **rsCTP**, **vds1CTPF**, **DS1CTPF**, **E3CTPF**, **cellBasedCTPF**, **ads1CTPF**, **DS3CTPF**, and **E1CTPF**. +- cellBasedTTP** is associated with **rsTTP** and **vpCTPF**. +- rsTTP** is associated with **msCTPF**. +- msTTP** is associated with **tcAdaptorTTPF**. +- DS3TTP** is associated with **DS1CTP**. +- E3TTP** is associated with **E1CTP**. +- vpTTPF** is associated with **vcCTPF**. +- tcAdaptorTTPF** is associated with **vpCTPF**. + +Q.834.1\_FC2 + +E-R diagram for termination points showing the hierarchy from NEFSAN down to various CTPF and TTP entities. + +Figure C.2/Q.834.1 – E-R diagram for termination points + +![E-R diagram for AAL showing relationships between NEFSAN, AAL5ProfileF, AAL1ProfileF, vcCTPF, and various data objects.](018fd261187e5e5412b0c34e29beabab_img.jpg) + +``` + +erDiagram + NEFSAN ||--o{ AAL5ProfileF : "" + NEFSAN ||--o{ AAL1ProfileF : "" + AAL5ProfileF ||--o{ vcCTPF : "AALProfilePtr" + AAL1ProfileF ||--o{ vcCTPF : "AALProfilePtr" + CESServiceProfileF ||--o{ vcCTPF : "ServiceProfilePtr" + vcCTPF ||--o{ AAL1PMCurrentDataF : "InterworkingVCCTPPtr" + vcCTPF ||--o{ AAL1PMCurrentDataF : "InterworkingVCCTPPtr" + vcCTPF ||--o{ UpcNpcDisagreementPMCurrentDataF : "CTPFPtr" + vcCTPF ||--o{ vpvcPMCurrentDataF : "CTPFPtr" + AAL1PMHistoryDataF ||--o{ AAL1PMCurrentDataF : "" + AAL5PMHistoryDataF ||--o{ AAL1PMCurrentDataF : "" + thresholdDataID ||--o{ AAL1PMCurrentDataF : "" + UpcNpcDisagreementPMCurrentDataF ||--o{ UpcNpcDisagreementPMCurrentDataF : "" + thresholdDataID ||--o{ UpcNpcDisagreementPMCurrentDataF : "" + vpvcPMCurrentDataF ||--o{ vpvcPMHistoryDataF : "" + thresholdDataID ||--o{ vpvcPMCurrentDataF : "" + +``` + +The diagram illustrates the Entity-Relationship (E-R) structure for AAL. At the top is the **NEFSAN** entity, which connects to **AAL5ProfileF** and **AAL1ProfileF**. These profile entities associate with the central **vcCTPF** entity via **AALProfilePtr**. A **CESServiceProfileF** entity also associates with **vcCTPF** via **ServiceProfilePtr**. From **vcCTPF**, relationships extend to performance monitoring entities: two **AAL1PMCurrentDataF** entities (via **InterworkingVCCTPPtr**), a **UpcNpcDisagreementPMCurrentDataF** entity (via **CTPFPtr**), and a **vpvcPMCurrentDataF** entity (via **CTPFPtr**). These current data entities are further linked to history data entities (**AAL1PMHistoryDataF**, **AAL5PMHistoryDataF**, **UpcNpcDisagreementPMCurrentDataF**, **vpvcPMHistoryDataF**) and a **thresholdDataID** entity. + +E-R diagram for AAL showing relationships between NEFSAN, AAL5ProfileF, AAL1ProfileF, vcCTPF, and various data objects. + +Q.834.1\_FC3 + +Figure C.3/Q.834.1 – E-R diagram for AAL + +## C.4 Physical performance monitor + +![E-R diagram for physical performance monitor showing entities and their relationships.](d13d29ff2ebef1a20c60c05fc4bca45b_img.jpg) + +``` + + erDiagram + PhysicalPathTTPF ||--o{ DS1PMHistoryDataF : "PhysicalPathTTPFPtr" + PhysicalPathTTPF ||--o{ DS3PMCurrentDataF : "PhysicalPathTTPFPtr" + PhysicalPathTTPF ||--o{ E1PMCurrentDataF : "PhysicalPathTTPFPtr" + PhysicalPathTTPF ||--o{ E3PMCurrentDataF : "PhysicalPathTTPFPtr" + DS1PMHistoryDataF ||--o{ DS1PMCurrentDataF : "" + DS1PMHistoryDataF ||--o{ ThresholdDataF : "ThresholdDataId" + DS3PMCurrentDataF ||--o{ ThresholdDataF : "ThresholdDataId" + E1PMCurrentDataF ||--o{ ThresholdDataF : "ThresholdDataId" + E3PMCurrentDataF ||--o{ ThresholdDataF : "ThresholdDataId" + DS1PMHistoryDataF ||--o{ DS3PMHistoryDataF : "" + DS3PMCurrentDataF ||--o{ DS3PMHistoryDataF : "" + E1PMCurrentDataF ||--o{ E1PMHistoryDataF : "" + E3PMCurrentDataF ||--o{ E3PMHistoryDataF : "" + ThresholdDataF ||--o{ ThresholdDataF : "" + ThresholdDataF ||--o{ DS3PMHistoryDataF : "" + ThresholdDataF ||--o{ E1PMHistoryDataF : "" + ThresholdDataF ||--o{ E3PMHistoryDataF : "" + +``` + +The diagram illustrates the Entity-Relationship (E-R) model for a physical performance monitor. It features several entities and their relationships: + +- PhysicalPathTTPF** is a central entity that has a one-to-many relationship with four entities: **DS1PMHistoryDataF**, **DS3PMCurrentDataF**, **E1PMCurrentDataF**, and **E3PMCurrentDataF**. The relationship is labeled **PhysicalPathTTPFPtr**. +- DS1PMHistoryDataF** has a one-to-many relationship with **DS1PMCurrentDataF**. +- DS1PMHistoryDataF**, **DS3PMCurrentDataF**, **E1PMCurrentDataF**, and **E3PMCurrentDataF** all have a one-to-many relationship with **ThresholdDataF**. The relationship is labeled **ThresholdDataId**. +- DS1PMHistoryDataF** has a one-to-many relationship with **DS3PMHistoryDataF**. +- DS3PMCurrentDataF** has a one-to-many relationship with **DS3PMHistoryDataF**. +- E1PMCurrentDataF** has a one-to-many relationship with **E1PMHistoryDataF**. +- E3PMCurrentDataF** has a one-to-many relationship with **E3PMHistoryDataF**. +- ThresholdDataF** has a one-to-many relationship with **ThresholdDataF** (self-referencing) and also has one-to-many relationships with **DS3PMHistoryDataF**, **E1PMHistoryDataF**, and **E3PMHistoryDataF**. + +E-R diagram for physical performance monitor showing entities and their relationships. + +Q.834.1\_FC4 + +Figure C.4/Q.834.1 – E-R diagram for physical performance monitor + +## C.5 TCAdaptor E-R diagram + +![E-R diagram for TCAdaptor showing relationships between various entities.](be9225da20b1fa284d0ed4b44fd633a3_img.jpg) + +``` + + erDiagram + alarmSeverityAssignmentProfileF ||--o{ tcAdaptorF : "alarmSeverityAssignmentProfilePtr" + BICIF ||--o{ tcAdaptorF : "TCAdaptorId" + ATMNetworkAccessProfileF ||--o{ tcAdaptorF : "ATMNetworkAccessProfileFORUNInfoF" + BISSIF ||--o{ tcAdaptorF : "TCAdaptorId" + tcAdaptorF ||--o{ UNIInfoF : "TCAdaptorId" + tcAdaptorF ||--o{ APONTTP : "APONTTPPtr" + tcAdaptorF ||--o{ APONCTP : "PhysicalPathTPFPtr" + tcAdaptorF ||--o{ PhysicalPathTPF : "PhysicalPathTPFPtr" + +``` + +The diagram illustrates the E-R relationships for the TCAdaptor. The central entity is **tcAdaptorF**. It is connected to several other entities: + +- alarmSeverityAssignmentProfileF**: Connected via **alarmSeverityAssignmentProfilePtr**. +- BICIF**: Connected via **TCAdaptorId**. +- ATMNetworkAccessProfileF**: Connected via **ATMNetworkAccessProfileFORUNInfoF**. +- BISSIF**: Connected via **TCAdaptorId**. +- UNIInfoF**: Connected via **TCAdaptorId**. +- APONTTP**: Connected via **APONTTPPtr**. +- APONCTP**: Connected via **PhysicalPathTPFPtr**. +- PhysicalPathTPF**: Connected via **PhysicalPathTPFPtr**. + +Q.834.1\_FC5 + +E-R diagram for TCAdaptor showing relationships between various entities. + +Figure C.5/Q.834.1 – E-R diagram for TCAdaptor + +## C.6 ATM cross-connection E-R diagram + +![E-R diagram for ATM cross-connection showing entities NEFSAN, ATMCrossConnectionControlF, ATMCrossConnectionF, vcCTPF, and vpCTPF with their relationships and attributes.](52fe5bc3ba967e0e8f56f1a3ab9d9c3e_img.jpg) + +The diagram illustrates the E-R model for ATM cross-connection. It features the following entities and relationships: + +- NEFSAN**: The top-level entity, connected to **ATMCrossConnectionControlF** via a diamond relationship labeled "ATM cross-connection". +- ATMCrossConnectionControlF**: A control entity connected to **ATMCrossConnectionF**. +- ATMCrossConnectionF**: A central entity connected to **vcCTPF** and **vpCTPF**. It has two sets of attributes: *TerminationPointA* and *TerminationPointZ* on both the left and right sides. +- vcCTPF** and **vpCTPF**: Two entities at the bottom, connected to **ATMCrossConnectionF** via lines labeled *ConnectivityPtr*. + +Q.834.1\_FC6 + +E-R diagram for ATM cross-connection showing entities NEFSAN, ATMCrossConnectionControlF, ATMCrossConnectionF, vcCTPF, and vpCTPF with their relationships and attributes. + +Figure C.6/Q.834.1 – E-R diagram for ATM cross-connection + +## C.7 Traffic characterization E-R diagram + +![E-R diagram for traffic characterization showing entities NEFSAN, vcCTPF, trafficDescriptorF, QoSParameterProfileF, vpCTPF, priorityQueueF, ONT, and ONU with their relationships and pointers.](d2f4940093768001d427ab18d4e40cf1_img.jpg) + +The diagram illustrates the relationships between various entities in a traffic characterization system. The entities and their associated pointers are as follows: + +- NEFSAN**: A central entity with two diamond-shaped pointers (indicating 1:1 relationships) connecting to **trafficDescriptorF** and **QoSParameterProfileF**. +- vcCTPF**: A container entity with two pointers: + - IngressTrafficDescriptorProfilePtr* pointing to **trafficDescriptorF**. + - EgressTrafficDescriptorProfilePtr* pointing to **trafficDescriptorF**. +- trafficDescriptorF**: An entity that is pointed to by **vcCTPF** and **NEFSAN**. +- QoSParameterProfileF**: An entity that is pointed to by **NEFSAN** and **vpCTPF**. +- vpCTPF**: A container entity with two pointers: + - EgressTrafficDescriptorProfilePtr* pointing to **trafficDescriptorF**. + - IngressTrafficDescriptorProfilePtr* pointing to **trafficDescriptorF**. + - IngressQoSParameterProfilePtr* pointing to **QoSParameterProfileF**. + - EgressQoSParameterProfilePtr* pointing to **QoSParameterProfileF**. +- priorityQueueF**: An entity that is pointed to by both **ONT** and **ONU** via diamond-shaped pointers. +- ONT** and **ONU**: Entities representing different types of network elements, both pointing to **priorityQueueF**. + +Additional labels in the diagram include **Q.834.1\_FC7** near the **priorityQueueF** entity and a set of pointers (*IngressQoSParameterProfilePtr*, *EgressQoSParameterProfilePtr*) associated with the **vpCTPF** entity. + +E-R diagram for traffic characterization showing entities NEFSAN, vcCTPF, trafficDescriptorF, QoSParameterProfileF, vpCTPF, priorityQueueF, ONT, and ONU with their relationships and pointers. + +Figure C.7/Q.834.1 – E-R diagram for traffic characterization + +## C.8 Log + +![E-R diagram for log entities](d24636250101595e660b20830d8c2c64_img.jpg) + +The diagram illustrates the relationships between several entities in a database. At the top, the **logF** entity is connected to the **filterProfileF** entity via a relationship labeled *FilterProfileId*. Below **logF**, there is a generalization hierarchy where **logF** is the superclass, and four entities are its subclasses: **attributeValueChangeRecordF**, **alarmLogRecordF**, **managedEntityCreationLogRecordF**, and **managedEntityDeletionLogRecordF**. The superclass **logF** is connected to the subclasses by a vertical line with a diamond at the top, indicating a generalization relationship. + +Q.834.1\_FC.8 + +E-R diagram for log entities + +**Figure C.8/Q.834.1 – E-R diagram for log** + +## C.9 ATM traffic load + +![E-R diagram for ATM traffic load showing entities, relationships, and cardinalities.](37cc5b3a159a6081e5193673fa2996b2_img.jpg) + +The diagram illustrates the entities and relationships for ATM traffic load. It features two main entity sets at the top and bottom, both labeled **ATMTrafficLoadCurrentDataF**. The relationships are defined by vertical lines connecting these entity sets to various entities in the middle. The entities are categorized by their shading: white boxes for primary entities and gray boxes for secondary or derived entities. Cardinalities are indicated by *MonitoringPtPtr* at the ends of the relationship lines. + +**Entities and Relationships:** + +- Primary Entities (White Boxes):** + - vcCTPF**: Connected to the top entity set. + - vpNetworkCTPF**: Connected to the top entity set. + - physicalPathTTPF**: Connected to the top entity set. + - vpCTPF**: Connected to the top entity set. +- Secondary Entities (Gray Boxes):** + - vcNetworkCTPF**: Connected to **vcCTPF** and the bottom entity set. + - topologicalEnd**: Connected to **vpNetworkCTPF** and the bottom entity set. + - logicalEnd**: Connected to **physicalPathTTPF** and the bottom entity set. + +**Cardinalities:** The cardinality *MonitoringPtPtr* is shown at the ends of the relationship lines connecting the entity sets to the primary entities, and at the ends of the lines connecting the primary entities to the secondary entities. + +Q.834.1\_FC9 + +E-R diagram for ATM traffic load showing entities, relationships, and cardinalities. + +Figure C.9/Q.834.1 – E-R diagram for ATM traffic load + +## C.10 Combined view managed entities + +![UML diagram showing containment relationships between managed entities in NetworkF and NEFSAN domains.](67cbb5a621a69ab58534bb3376bbb724_img.jpg) + +``` + +classDiagram + class NetworkF + class layerNetworkDomainF + class NEFSAN + class topologicalLinkF + class TopologicalLinkEndF + class accessGroupF + class trailF + class logicalMTPLinkF + class LogicalLinkF + class linkConnectionF + class LogicalLinkEndF + class SubnetworkF + class subnetworkConnectionF + class OLT + class ONT + class ONU + class NT + class TTPF + class CTPF + class ATMCrossConnectionControlF + class ATMCrossConnectionF + class EquipmentHolderF + class plugInUnitF + class SoftwareF + + NetworkF o-- layerNetworkDomainF + NetworkF o-- NEFSAN + layerNetworkDomainF o-- topologicalLinkF + layerNetworkDomainF o-- TopologicalLinkEndF + layerNetworkDomainF o-- accessGroupF + layerNetworkDomainF o-- trailF + layerNetworkDomainF o-- logicalMTPLinkF + layerNetworkDomainF o-- LogicalLinkF + layerNetworkDomainF o-- linkConnectionF + layerNetworkDomainF o-- LogicalLinkEndF + layerNetworkDomainF o-- SubnetworkF + layerNetworkDomainF o-- subnetworkConnectionF + NEFSAN o-- OLT + NEFSAN o-- ONT + NEFSAN o-- ONU + NEFSAN o-- NT + NEFSAN o-- TTPF + NEFSAN o-- CTPF + NEFSAN o-- ATMCrossConnectionControlF + NEFSAN o-- EquipmentHolderF + NEFSAN o-- plugInUnitF + NEFSAN o-- SoftwareF + + topologicalLinkF o-- linkConnectionF + OLT o-- ONT + ONU o-- NT + TTPF o-- CTPF + ATMCrossConnectionControlF o-- ATMCrossConnectionF + EquipmentHolderF o-- plugInUnitF + plugInUnitF o-- SoftwareF + +``` + +The diagram illustrates the containment relationships between managed entities in the NetworkF and NEFSAN domains. NetworkF contains layerNetworkDomainF and NEFSAN. layerNetworkDomainF contains topologicalLinkF, Topological LinkEndF, access GroupF, trailF, LogicalLinkF, linkConnectionF, Logical LinkEndF, SubnetworkF, logicalMTPLinkF, and subnetwork ConnectionF. NEFSAN contains OLT, ONT, ONU, NT, TTPF, CTPF, ATMCrossConnectionControlF, ATMCrossConnectionF, EquipmentHolderF, plugInUnitF, and SoftwareF. Containment is indicated by a hollow diamond on the line connecting the containing entity to the contained entity. + +UML diagram showing containment relationships between managed entities in NetworkF and NEFSAN domains. + +This figure shows containment relationships. + +Figure C.10/Q.834.1 – E-R Combined view managed entities + +## C.11 Layer network domain and subnetwork + +![E-R diagrams for layer network domain and subnetwork](2690cca56d57ad5978da52f7ad84cafd_img.jpg) + +The diagram illustrates two inheritance hierarchies for network modeling. The top hierarchy is for 'layerNetworkDomainF', which generalizes nine specific layer network domains. The bottom hierarchy is for 'SubnetworkF', which generalizes nine specific subnetwork types. In both cases, a central triangle symbol below the parent entity indicates an inheritance relationship to the entities below. + +``` +graph TD; + LND[layerNetworkDomainF] --- T1(( )) + T1 --- vpLND[vpLayerNetworkDomainF] + T1 --- aponLND[aponLayerNetworkDomainF] + T1 --- e1LND[e1LayerNetworkDomainF] + T1 --- e3LND[e3LayerNetworkDomainF] + T1 --- vdslLND[vdslLayerNetworkDomainF] + T1 --- vcLND[vcLayerNetworkDomainF] + T1 --- ds1LND[ds1LayerNetworkDomainF] + T1 --- ds3LND[ds3LayerNetworkDomainF] + T1 --- adslLND[adslLayerNetworkDomainF] + + SNF[SubnetworkF] --- T2(( )) + T2 --- vpSNF[vpSubnetworkF] + T2 --- aponSNF[aponSubnetworkF] + T2 --- e1SNF[e1SubnetworkF] + T2 --- e3SNF[e3SubnetworkF] + T2 --- vdslSNF[vdslSubnetworkF] + T2 --- vcSNF[vcSubnetworkF] + T2 --- ds1SNF[ds1SubnetworkF] + T2 --- ds3SNF[ds3SubnetworkF] + T2 --- adslSNF[adslSubnetworkF] +``` + +E-R diagrams for layer network domain and subnetwork + +Q.834.1\_FC11 + +**Figure C.11/Q.834.1 – E-R diagrams for layer network domain and subnetwork** + +## C.12 Link connection + +![E-R diagram for link connection showing linkConnectionF as a base class for five subclasses: vpLinkConnectionF, aponLinkConnectionF, vcLinkConnectionF, adsILinkConnectionF, and vdsILinkConnectionF.](cb9e3603e260c7b07aca73128586df80_img.jpg) + +``` +graph TD; linkConnectionF[linkConnectionF] --|> vpLinkConnectionF[vpLinkConnectionF]; linkConnectionF --|> aponLinkConnectionF[aponLinkConnectionF]; linkConnectionF --|> vcLinkConnectionF[vcLinkConnectionF]; linkConnectionF --|> adsILinkConnectionF[adsILinkConnectionF]; linkConnectionF --|> vdsILinkConnectionF[vdsILinkConnectionF]; +``` + +Q.834.1\_FC12 + +E-R diagram for link connection showing linkConnectionF as a base class for five subclasses: vpLinkConnectionF, aponLinkConnectionF, vcLinkConnectionF, adsILinkConnectionF, and vdsILinkConnectionF. + +Figure C.12/Q.834.1 – E-R diagram for link connection + +## C.13 Subnetwork connection + +![E-R diagram for subnetwork connection showing SubnetworkConnectionF as a base class for six subclasses: vpSubnetworkConnectionF, vcSubnetworkConnectionF, ds1SubnetworkConnectionF, e1SubnetworkConnectionF, ds3SubnetworkConnectionF, and e3SubnetworkConnectionF.](8942c590307508b28df9c207bad75740_img.jpg) + +``` +graph TD; SubnetworkConnectionF[SubnetworkConnectionF] --|> vpSubnetworkConnectionF[vpSubnetworkConnectionF]; SubnetworkConnectionF --|> vcSubnetworkConnectionF[vcSubnetworkConnectionF]; SubnetworkConnectionF --|> ds1SubnetworkConnectionF[ds1SubnetworkConnectionF]; SubnetworkConnectionF --|> e1SubnetworkConnectionF[e1SubnetworkConnectionF]; SubnetworkConnectionF --|> ds3SubnetworkConnectionF[ds3SubnetworkConnectionF]; SubnetworkConnectionF --|> e3SubnetworkConnectionF[e3SubnetworkConnectionF]; +``` + +Q.834.1\_FC13 + +E-R diagram for subnetwork connection showing SubnetworkConnectionF as a base class for six subclasses: vpSubnetworkConnectionF, vcSubnetworkConnectionF, ds1SubnetworkConnectionF, e1SubnetworkConnectionF, ds3SubnetworkConnectionF, and e3SubnetworkConnectionF. + +Figure C.13/Q.834.1 – E-R diagram for subnetwork connection + +## Appendix I + +### FSAN operations requirements + +#### I.1 Introduction + +- 1 I Since early 1995 a number of operators and suppliers have collaborated on developing solutions and designs for delivering a low-cost full-services access network (FSAN). The operator members of this collaboration believe that agreement on a common set of requirements on as many aspects as possible will lead to a cost-effective solution. It was also decided that involving suppliers at an early stage of the discussions would enable them to deliver the required solutions. A number of working groups were set up to facilitate this, each covering a specific area of the FSAN [I-1]. +- 2 I This appendix describes the set of common requirements which have been developed by the OAM group members (both operators and suppliers). The requirements cover the following aspects of OAM: +- a) High-level business processes; + - b) Network Management Architecture; + - c) Operational requirements; + - d) OAM of the transmission medium. +- 3 I Requirements from the other FSAN working groups have also been used as an input to this work [I-2]. +- 4 I NOTE – All statements in this appendix are numbered "n x" to aid traceability where "n" is an integer number starting from 1 and "x" indicates the type of statement. The statement can be an (I)nformation statement, a (M)andatory requirement or an (O)ptional requirement. + +#### I.2 Processes + +- 5 I Operators are increasingly using process engineering methods to describe the flow of fundamental business activities to assist them in defining the required operational system functionality. Once these processes are understood it is possible to determine which activities can be automated to provide improvements in operations. +- 6 I A process can be viewed as a series of tasks that describe the operations functions and the relationship between the functions. Processes also identify the instances of data that are manipulated by the operations functions. +- 7 I Every operator defines processes suitable for his organization and infrastructure by grouping tasks in different ways to form unique business processes. This makes it difficult to define a set of common detailed processes that are applicable to every operator. For this reason, this appendix describes a small set of high-level processes which cover most of the tasks for specific operations as an aid to understanding the source of the management requirements. Although the names of the processes may need to be translated to equivalent names within each operator's organization, they are considered to be generally applicable to each operator. Process work by the Network Management Forum (NMF) [I-3] may also help to understand the set of activities that every operator has to address. +- 8 I Some of the key activities involve planning and engineering, service and network provisioning, network repair, network testing and accounting. + +9 I The following clauses describe high-level examples of some of the key processes which can be used to provision and maintain the FSAN and to manage services. These, together with operators' experience, have been used as a baseline for developing the management requirements described in this appendix. + +### **1.2.1 Planning and engineering** + +10 I This process ensures that sufficient network resources are available to meet overall customers needs (see Figure I.1). The process performs trend analysis of customer network usage and generates demand forecasts on network resources. The process will be used to determine access network capacity such as PON bandwidth, OLT/ONU/ONT line cards, VP/VC switch and cross-connect requirements. The process requires network usage, planning and engineering data for analysis. + +![Flowchart of the high-level planning and engineering process, showing five main stages: Service planning & negotiation, Network planning & engineering, Installation, Performance mngt & control, and Network service provision control. A Process control block is shown below, connected to the Network planning & engineering and Installation stages. A feedback loop connects the Performance mngt & control stage back to the Network planning & engineering stage.](9b6977f95ef47e2c87cd4979c09a7edb_img.jpg) + +``` + +graph LR + SPN[Service planning & negotiation] --> NPE[Network planning & engineering] + NPE --> I[Installation] + I --> PMC[Performance mngt & control] + PMC --> NSPC[Network service provision control] + PMC --> NPE + PC[Process control] -.-> NPE + PC -.-> I + +``` + +**Service planning & negotiation** + +- 1) Process new service requests +- 2) Define service feature needs + +**Network planning & engineering** + +- 1) Perform trend analysis +- 2) Determine demand forecasts +- 3) Determine infrastructure (Network, access, facility design) +- 4) Determine capacity needed (loop, trunk, switch) +- 5) Perform technology analysis + +**Installation** + +- 1) Procure NE, facilities +- 2) Procure real estate +- 3) Re-arrange NE, facilities as required +- 4) Install NE and facilities (h/w and s/w) + +**Performance mngt & control** + +- 1) Monitor NE, facility performance +- 2) Collect service-specific data + +**Network service provision control** + +- 1) Update inventory records + +**Process control** + +- 1) Service policy +- 2) Accounting policy + +Q.834.1\_Fl.1 + +Flowchart of the high-level planning and engineering process, showing five main stages: Service planning & negotiation, Network planning & engineering, Installation, Performance mngt & control, and Network service provision control. A Process control block is shown below, connected to the Network planning & engineering and Installation stages. A feedback loop connects the Performance mngt & control stage back to the Network planning & engineering stage. + +**Figure I.1/Q.834.1 – High-level planning and engineering process** + +## **I.2.2 Service provision** + +- 11 I This process covers the set of tasks required to deliver service to customers across the FSAN. The process is illustrated in Figure I.2. This process begins with customer interaction to record customer data and service data to meet the customer's request. Other activities of this process are responsible for tracking the progress of the request and for updating (interacting with other functions) at particular times. For example, it may be necessary to verify the customer's credit history prior to progressing an order. On completion of the order, accounting data is updated to ensure that the customer can be effectively billed for the service. Other functions covered include network planning, work force scheduling and the provisioning of network equipment (OLTs, ONUs, ONTs, NTs, Service cards and so on). + +![High-level service provision process flowchart showing the sequence from Customer to Billing, with feedback loops and parallel processes.](3ce6b213ec556257e32ff7451182369d_img.jpg) + +``` + +graph LR + Customer --> OH[Order handling] + OH --> OC[Order control] + OC --> SPC[Service provisioning control] + SPC --> WA[Workforce administration] + WA --> I[Installation] + I --> Billing[Billing] + Billing --> Customer + + %% Feedback loops (dashed arrows) + SPC -.-> OH + WA -.-> OC + I -.-> OH + Billing -.-> OH + + %% Parallel processes + OC --> NA[Number allocation] + SPC --> Planning[Planning] + +``` + +**Order handling** + +- 1) Determine requirements +- 2) Confirm customer details +- 3) Assess credit history +- 4) Arrange provisional appointment +- 5) Review order and assess date +- 6) Confirm appointment +- 7) Issue contract +- 8) Cancel order + +**Order control** + +- 1) Receive job +- 2) Distribute job to downstream systems. +- 3) Monitor progress +- 4) Chase/escalate as required +- 5) Receive completion notice +- 6) Update operations systems. + +**Service provisioning control** + +- 1) Assess order +- 2) Design & assign access facility. +- 3) Manage service system activities +- 4) Assign and configure route +- 5) Record stores required +- 6) Determine work items +- 7) Configure service node +- 8) Update records +- 9) Enter details for review + +**Workforce administration** + +- 1) Receive order +- 2) Material management +- 3) Allocate work and resources (feeder, distribution, access network) +- 4) Co-op with field if required + +**Installation** + +- 1) Receive order +- 2) Order stores +- 3) Provide NT, OLT, ONU, ONT, software and wiring +- 4) Co-op with WFA +- 5) Commission service +- 6) Advise completion +- 7) Test service + +**Number allocation** + +- 1) Confirm network circuit availability +- 2) Determine affected NEs +- 3) Allocate service (customer) number +- 4) Complete records + +**Planning** + +- 1) Receive request +- 2) Assess requirement +- 3) Inform SPC of timescale +- 4) Initiate work +- 5) Advise SPC when complete + +**Billing** + +- 1) Read meter if required +- 2) Advise service reps +- 3) Update customer profile +- 4) Receive completed order +- 5) Generate bill for service +- 6) Close order + +Customer + +Q.834.1\_F1.2 + +High-level service provision process flowchart showing the sequence from Customer to Billing, with feedback loops and parallel processes. + +Figure I.2/Q.834.1 – High-level service provision process + +### **I.2.3 Network repair** + +- 12 I Network repair involves the set of tasks required to determine the cause and location of faults in the FSN and the tasks needed to restore service at the contracted service level. Network repair can be proactive or reactive. Proactive repair can be initiated as a result of network self-diagnostics in terms of hardware, software or traffic conditions. A network operator will normally initiate reactive repair on receipt of a report from a customer indicating a degradation or fault in the service being delivered over the network. +- 13 I Figure I.3 shows the tasks for reactive repair of the network. Particular functions involved include trouble administration, surveillance, performance monitoring and testing. Proactive repair will contain similar steps except that the process will be driven by event reports from the network rather than from a report by the customer. + +![High-level repair process flowchart showing the sequence from Customer handling to Network repair control, including various repair tasks like Replace ONU/ONT FRUs, Replace OLT FRUs, Repair PON, and Repair CPE.](845e014e3b8677eb735d0e21f21206be_img.jpg) + +``` + +graph LR + Customer --> CH[Customer handling] + CH --> TA[Trouble administration] + TA -.-> NRC1[Network repair control] + TA --> NRC1 + NRC1 --> WA[Workforce administration] + WA -.-> NRC1 + WA --> ROFR[Replace ONU/ONT FRUs] + WA --> ROLFR[Replace OLT FRUs] + WA --> RPON[Repair PON] + WA --> RCPE[Repair CPE] + ROFR --> NRC2[Network repair control] + ROLFR --> NRC2 + RPON --> NRC2 + RCPE --> NRC2 + NRC2 --> Customer2[Customer] + +``` + +**Customer handling** + +- 1) Receive fault report +- 2) Identify service affected +- 3) Structured questions +- 4) Record details +- 5) Issue fault for diagnostics + +**Trouble administration** + +- 1) Process fault report +- 2) Correlate with previous fault (if possible) +- 3) Analyse subscriber data (address, no., acct. etc) +- 4) Identify access technology +- 5) Generate trouble ticket + +**Network repair control** + +- 1) Retrieve network data for tests +- 2) Diagnose +- 3) Check for network reported faults +- 4) Correlate +- 5) Isolate fault +- 6) Monitor service performance. + +**Workforce administration** + +- 1) Determine workforce domain +- 2) Determine repair time +- 3) Schedule and dispatch workforce. + +**Replace ONU/ONT FRUs** + +- 1) Allocate work +- 2a) Replace FRUs +- 2b) Replace NT +- 2c) Repair customer wiring +- 2d) Replace ONT +- 3) Test & Advise customer + +**Replace OLT FRUs** + +- 1) Allocate work +- 2a) Repair core network +- 2b) Replace FRUs or wiring +- 3) Test +- 4) Advise clear + +**Repair PON** + +- 1) Allocate work +- 2a) Repair fibre +- 2b) Replace OTS +- 3) Test +- 4) Advise clear + +**Repair CPE** + +- 1) Allocate work +- 2a) Repair CPE +- 2b) Replace CPE +- 3) Test CPE +- 4) Advise clear + +**Network repair control** + +- 1) Configure if needed +- 2) Receive clear details +- 3) Record details +- 4) Confirm clear with customer +- 5) Adjust billing +- 6) Close trouble ticket + +Q.834.1\_F13 + +High-level repair process flowchart showing the sequence from Customer handling to Network repair control, including various repair tasks like Replace ONU/ONT FRUs, Replace OLT FRUs, Repair PON, and Repair CPE. + +Figure I.3/Q.834.1 – High-level repair process + +### I.3 Management architecture + +- 14 I This clause provides a definition of the management terms used in this appendix, the FSAN target management architecture, and the management interfaces. +- 15 I A definition of the terms (see Table I.1) is necessary to ensure a common understanding. Where necessary, the definitions are based on those used in ITU-T Recs M.3010 [I-4], M.3013 [I-14], G.902 [I-5] and G.982 [I-6]. + +**Table I.1/Q.834.1 – Definition of terms** + +| Term | Source | Description | +|---------------------------------------------------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Operations System Function (OSF) | M.3010 | This is the collection of similar functions which provide different levels of management capability. Three kinds of OSFs are shown in Figure 1: Element management layer – OSF (E-OSF), Network management layer-OSF (N-OSF) and Service management layer – OSF (S-OSF). Each OSF provides management services to the layer above. | +| Network Element Layer (NEL) | M.3010
M.3013 | Refers to the physical resources that reside in the Access Network. | +| Element management layer – Operations System Function (E-OSF) | M.3010 | E-OSF manages the physical resources which reside in the access network. Typical management functions at this level are configuration, fault management and performance monitoring. E-OSF is responsible for understanding the details of transmission technology information and equipment thus removing the need for this complexity of information to be held by higher-layer management functions. | +| Network management layer – Operations System Function (N-OSF) | M.3010 | N-OSF coordinates the management of network elements to provide a user-to-user or service node to user path in order to transport telecommunication services. NM functions will coordinate multiple E-OSFs to provide overall network supervision. | +| Service management layer – Operations System Function (S-OSF) | M.3010 | S-OSF manages the services supported by the network. It is not concerned with the physical nature of the network. Typical functions of this layer are service creation, provision, cessation, billing and accounting information. | +| FSAN Element Management System | FSAN | The collection of E-OSF, N-OSF and S-OSF is implemented on one Operations System (OS). | +| Service Node (SN) | G.902 | A network element that provides access to various switched and/or permanent telecommunication services. For switched services, the SN provides call control, connection control and resource handling functions. | +| Access Network (AN) | G.902 | The collection of network equipment which provides a transport capability for the provision of telecommunication services between a Service Node Interface (SNI) and one or more associated User Network Interfaces (UNI). User signalling is carried transparently by the AN. | +| Optical Access Network (OAN) | G.983.1 | The set of access links sharing the same network-side interfaces and supported by optical access transmission systems. The OAN may include a number of ODNs connected to the same OLT. | + +**Table I.1/Q.834.1 – Definition of terms** + +| Term | Source | Description | +|------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Extended Feeder | FSAN | Provides the physical resources to extend the AN over larger distances. These physical resources will not alter the transmission on the SNI and will require minimal management. This is not considered to be part of the Network Element. | +| Optical Line Termination (OLT) | G.982 | An OLT provides the network-side interface of the OAN. It is connected to one or more ODNs. | +| Optical Distribution Network (ODN) | G.982 | Refers to the point-to-multipoint fibre network used to transport services in a common format from the OLT to the ONU/ONT. It utilizes passive optical components. | +| Optical Network Unit (ONU) | G.983.1 | An ONU provides (directly or remotely) the user-side interface of the OAN, and is connected to the ODN. | +| Network Termination (NT) | FSAN | Physical resource, which resides in the customers premises and forms the boundary of the access network (UNI). It provides onward transmission of services over building wiring to customer premises equipment. | +| Optical Network Termination (ONT) | G.983.1
FSAN | An ONU used for FTTH and includes the User Port function. For some operators, the ONU and NT functions will be combined in one physical resource which is called an ONT. | +| Drop Medium | FSAN | Refers to the network used to transport services in a common format from the OLT to the NT. | +| Data Communications Network (DCN) | M.3010 | Refers to the management communications network which is needed to transfer management information between OSFs and between OSFs and the NEL. | +| User | FSAN | A crafts person interacting with the management system. | +| Customer | FSAN | The person or organization that uses the services provided by the network provider or the service provider. A customer can be a service provider as well. | + +16 I The target management architecture is shown in Figure I.4 which also shows the management interfaces that will need to be supported. The architecture shows the different layers of management functionality that is required to manage the FSAN. Each layer consists of one or more operations system functions (OSFs). + +![Figure I.4/Q.834.1 – Target network management architecture. The diagram shows a multi-layered architecture divided into four horizontal sections: SML (Service Management Layer), NML (Network Management Layer), EML (Element Management Layer), and NEL (Network Element Layer). Domain 2 (left) contains SM OSF, NM OSF, EM OSF, and NE. Domain 1 (right) contains SM OSF, NM OSF, EM OSF, SN, Extended Feeder, OLT, ODN, ONU, NT, and ONT. Interfaces are labeled: if7 (IF7:X) between SM OSFs; if8 (IF8:Q3/X) between SM OSF and NM OSF; if0 (IF0:Q3) between NM OSFs; if1 (IF1:Q3/CORBA) between NM OSF and EM OSFs; if2 (IF2:SNMP/Q3/CORBA) between EM OSFs and the DCN cloud; if3 (IF3:SN1) between SN and Extended Feeder; if4 (IF4) between Extended Feeder and OLT; if4 (IF4) between OLT and ODN; if5 (IF5) between ODN and ONU; if6 (IF6:UNI) between ONU and ONT. A dashed box labeled 'Network Elements' encloses OLT, ODN, ONU, NT, and ONT. The DCN cloud connects EM OSFs and Network Elements. Labels 'Domain 2', 'Domain 1', 'SML', 'NML', 'EML', and 'NEL' are placed in their respective sections.](c93353297f7ed04bc9173ac1f224d406_img.jpg) + +Figure I.4/Q.834.1 – Target network management architecture. The diagram shows a multi-layered architecture divided into four horizontal sections: SML (Service Management Layer), NML (Network Management Layer), EML (Element Management Layer), and NEL (Network Element Layer). Domain 2 (left) contains SM OSF, NM OSF, EM OSF, and NE. Domain 1 (right) contains SM OSF, NM OSF, EM OSF, SN, Extended Feeder, OLT, ODN, ONU, NT, and ONT. Interfaces are labeled: if7 (IF7:X) between SM OSFs; if8 (IF8:Q3/X) between SM OSF and NM OSF; if0 (IF0:Q3) between NM OSFs; if1 (IF1:Q3/CORBA) between NM OSF and EM OSFs; if2 (IF2:SNMP/Q3/CORBA) between EM OSFs and the DCN cloud; if3 (IF3:SN1) between SN and Extended Feeder; if4 (IF4) between Extended Feeder and OLT; if4 (IF4) between OLT and ODN; if5 (IF5) between ODN and ONU; if6 (IF6:UNI) between ONU and ONT. A dashed box labeled 'Network Elements' encloses OLT, ODN, ONU, NT, and ONT. The DCN cloud connects EM OSFs and Network Elements. Labels 'Domain 2', 'Domain 1', 'SML', 'NML', 'EML', and 'NEL' are placed in their respective sections. + +Q.834.1\_F14 + +NOTE – The F interface as defined in ITU-T Rec. M.3010 is not shown in this figure but is implicit where there is an OSF. + +**Figure I.4/Q.834.1 – Target network management architecture** + +- 17 I An OSF should not be interpreted as a physical systems implementation. One or more OSFs may reside on one or more physical platforms. +- 18 M Each interface is shown with a lower case reference point (e.g., if1) and an uppercase implementation option of that interface (e.g., IF:Q3/CORBA) if it physically exists between two systems. This requirement specifically refers to reference points if1, if3, if4 and if6 in Figure I.4. +- 19 M Where a Q3 implementation is adopted, this shall be based on the Telecommunications Management Network (TMN) interface [I-7] using the Common Management Interface Protocol (CMIP) [I-8] and [I-9]. With this approach, a high-layer management function will contain a "manager" function and a lower-layer management function will contain an "agent" function. Management operations are communicated between the manager and agent functions using CMIP. It is not necessary to implement a Q3 interface if the management functions reside on the same physical system. + +- 20 I The purpose of showing these interfaces is to determine the management information flows and data which will pass between the management functions. Information flows will be realized through management services between operations functions. Table I.2 gives a brief description of the possible management services provided at each reference point. The management flows are currently under study. + +**Table I.2/Q.834.1 – Services provided over management interfaces** + +| Reference point | Management services | Comments on implementation of reference point | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| if0 | Topology, service configuration and provisioning;
Trouble/test administration;
Account/billing/QoS performance reporting. | Q3 | +| if1 | Configuration/provisioning/test/fault/performance management of transport resources;
Equipment management;
Configuration/fault/performance management of transmission system. | Either Q3 based on the TMN Q3 interface using the Common Management Interface Protocol (CMIP) Network Management Hierarchy or CORBA | +| if2 | Configuration/fault/performance/test management of network element;
Network element consistency checks;
Network element initialization/authentication/security management. | SNMP initially but does not preclude migration to Q3 or CORBA | +| if3 | Termination of SNI;
Management/control/maintenance/testing of interface;
Connection establishment;
Mapping of bearer services to access transport resources. | SNI | +| if4 | Multiplexing of bearer services;
Management communications;
Connection/fault/performance management;
Link initialization;
Media access control;
Security and user data encryption. | Management communications between OLT and ONU/ONT is via management channel over this interface [I-6]. | +| if5 | Error detection/reporting;
Fault detection/reporting;
Reset control;
Configuration/activation/deactivation of NT resource. | This reference point may not be implemented if the ONU and NT are combined as in the case of the ONT | +| if6 | Termination of UNI;
Management/control/maintenance/testing of interface;
Activation/deactivation. | UNI | +| if7 | Ordering, service configuration and provisioning;
Trouble/test administration;
Account/billing/QoS performance reporting. | X
This interface should have special security aspects because it links two different domains. | +| if8 | Topology, ordering, service configuration and provisioning;
Trouble/test administration;
Account/billing/QoS performance reporting for the purposes of the service user. | Q3/X
This interface should have special security aspects because it links a customer OSF to a network provider OSF. | + +## **I.4 Management requirements** + +### **I.4.1 Scope** + +- 21 I This clause defines the management requirements for Network Element and Element Management layers, as shown in the logical architecture. The requirements have been further subdivided under the Configuration, Fault, Performance, Accounting and Security management functions within each layer. In addition, some requirements have been included for the Network Management and Service Management Layer. + +### **I.4.2 Common management requirements** + +- 22 I This clause defines requirements that are considered to be common for all layers in the FSAN architecture. All management functions and interfaces shall be based on existing standard information models and interfaces where possible. +- 23 M All management functions are required to support the range of services defined in [I-10]. + +#### **I.4.2.1 Fault management** + +- 24 M FSAN fault management refers to the broad set of functions associated with the detection, isolation, reporting and correction of abnormal operational conditions in the FSAN network. In this context, fault management consists of the following: +- alarm surveillance (detecting/receiving events); + - event processing (correlation and filtering); + - fault localization; + - event logging; + - testing. + +#### **I.4.2.2 Security** + +- 25 M Access to management functions and data at any layer, either by users or external systems, shall require authentication and access control. +- 26 M Users or external systems shall be authenticated through a challenge-response mechanism. This mechanism involves authentication through the use of identification and passwords. The mechanism may include use of devices such as smart cards for user identification. +- 27 M It shall be possible to configure the identification, the minimum length of the password, the expiry time of the password, the maximum allowed attempts "m" to enter the password and the retry expiry timeout for each individual user or external system. +- 28 M A user failing "m" attempts to enter the correct password shall be denied further attempts to gain access until expiry of the retry time-out. In this case, a security violation event shall be logged and a message shall be displayed, if appropriate, to indicate that access has been denied. +- 29 M Passwords shall not be echoed when entered and shall be encrypted if transmitted over any communications link. +- 30 M It shall be possible to configure the management functions and data available to a user or external system. The access parameters shall be based on read/write/modify/execute/delete privileges, geographic location, service type, time period over which access is allowed, functions available, data available and user profile and/or system name. +- 31 M Illegal attempts to access functions and or data shall be reported as a security violation. All accesses shall be logged. +- 32 M If a security violation is detected, the security function shall isolate the user or external system to prevent any further access attempts. + +### **I.4.2.3 Logs** + +- 33 O All OSF log(s) shall operate in a first-in first-out basis in case of overflow. It shall be possible to configure a log to send an event, to a higher-layer management system, when a log full threshold has been exceeded or an overflow occurs. +- 34 M It shall be possible to archive logs periodically using back-up mechanisms. Archiving shall not affect current logs. +- 35 M It shall be possible to read all OSF logs (current or archived) from the user interface. + +### **I.4.3 Network element layer requirements** + +#### **I.4.3.1 Configuration management** + +- 36 M All network equipment shall be modular in design so that it is easy to install, remove, replace or upgrade without affecting existing services to other customers. +- 37 M The NE shall automatically detect the installation and removal of network equipment. +- 38 M For equipment installation, automatic detection shall include the following sequence of activities: installation, power-up self test, equipment authentication, read inventory information, report installation to the EM-OSF, and download of configuration information. Inventory information shall be read and sent to the EM-OSF, where possible, regardless of whether the equipment is of the correct type. +- 39 M Download of configuration information shall be performed automatically following successful installation or on request from the EM-OSF. The configuration information shall include service-specific software where appropriate. Configuration of the equipment shall not be allowed if the associated logical resources do not exist in the EM database. +- 40 M For equipment removal, the NE is only required to report the event to the EM-OSF. +- 41 M An event report shall be sent to the EM-OSF to indicate the success or failure of the equipment installation or removal. This event shall contain the following information: + - a) type of network equipment (known, unknown or incompatible); + - b) an indication of whether the installation/removal succeeded or failed; and + - c) inventory of the network equipment (e.g., equipment id, hardware and software version) if the equipment is known or incompatible. No inventory information if the equipment is unknown. +- 42 M Any change of equipment state and relationship information shall be communicated to the EM-OSF by event reports. This information shall accurately reflect the status of the network equipment that exists or has been built in the NE database. +- 43 M The NE shall store all operational and service-related parameters (e.g., slot assignments, power levels, cross-connections, etc.) in the NE database. + +#### **I.4.3.2 Fault management** + +- 44 M The NE shall continue to function if it loses management communications with the EM-OSF. +- 45 O The NE should perform a connection test from the SNI port on the OLT to the UNI port on the NT when the NT/ONT is installed to ensure that the path between the SNI and UNI is correctly configured. + +- 46 M There shall be simple visual indications (e.g., light-emitting diode) to confirm faults on the network equipment and to aid local maintenance procedures, where appropriate. All visual indications shall be consistent with the state of the network equipment. Where appropriate, the following shall be indicated: +- faults on the equipment; + - status of external interface(s), if present (e.g., signal present/not present); + - equipment synchronizing/synchronized; + - whether equipment is main or standby. +- 47 M It shall be possible to identify (via an LED) which is a main (currently operating) resource and which is the standby for those resources which are protected. A protection switching function shall be provided to switch to the standby resource if there is a fault on the main resource. On switch-over, the standby resource shall become the main resource and the main resource shall become the standby resource. The protection switch event shall be reported to the EM-OSF. +- 48 M Events indicating faults should be reported as soon as a fault has been detected following any persistence checks and correlation performed by the NE. A single event should be raised following correlation. +- 49 M Event reports shall not be raised against equipment that has been created in the NE database but has not yet been installed. +- 50 M Network equipment is required to automatically perform a self-test (where applicable) when connected to the network. Completion of the self-test should leave the network equipment in a known state. An event shall be sent to the EM-OSF to indicate failure of the self-test. +- 51 M The network equipment shall not require the manual use of specialized fault-finding techniques or tools to diagnose faults in the OLT, ODN, ONU or NT. +- 52 M The NE shall support network or customer facing loops to determine the integrity of the access network or parts of the access network. Logical loops shall be provided at the ATM layer for maintenance and performance management using OAM cells. It shall be possible for the EM-OSF to request application of logical loops on the FSAN NE. +- 53 O Physical loops shall be provided on the interfaces at the OLT and ONU/ONT. Physical loops shall be applied on request from the EM-OSF. +- 54 M A bit error rate test source shall be provided in the OLT. Activation and de-activation of the test source shall be carried out on request from the EM-OSF. +- 55 M It shall be possible to perform service-specific tests associated with the transport medium between the ONU and NT, where the ONU and NT are separate. The test functions, where possible, should also be able to determine if the customer's equipment is present or absent. Any faults detected during testing shall be reported to the EM-OSF. +- 56 M Detection of failures in the received transport signal at the OLT or ONU/ONT shall cause the NE to report the fault to the EM-OSF. If the failure is detected at the OLT, an immediate switch shall be performed to a standby ODN interface if available. A failure on the received signal (downstream) at the ONU/ONT shall not result in the corruption of data on the ODN in the upstream signal to the OLT. In this case, the ONU shall attempt to indicate the failure to the OLT. +- 57 M It shall be possible to accurately distinguish between faults on the ODN and faults on the ONU possibly through the use of internal event correlation and test functions. +- 58 M Any outstanding new event shall be made available to the EM-OSF following restoration of communications with the NE. + +- 59 M A local craft terminal interface shall only be used for equipment installation. +- 60 O Any test function which is employed shall accurately report the location of a fault on the ODN. +- 61 O The NE shall automatically re-configure its internal resources (software) to rectify a fault where possible. + +#### **I.4.3.3 Performance management** + +- 62 M Once installed, the network equipment shall be monitored to provide information on Network Performance and Service Performance. Measurements shall be based on monitoring network or service parameters. An event shall be sent to the EM-OSF when the monitoring function detects that a threshold for a parameter has been exceeded. Monitoring shall not affect customer traffic. +- 63 M Performance data shall be generated based on performance parameters that have been configured. +- 64 M Error-rate performance measurements shall be provided at specific points in the NE. +- 65 M It shall be possible to activate and deactivate scheduled reporting of current and historical performance data of the network from the EM-OSF. The parameters used for monitoring shall be configured with network defaults and shall be modifiable where applicable. It shall not be possible to modify any parameters once all monitoring criteria are set and monitoring has been activated without first deactivating. +- 66 M When a monitoring function is activated, it shall be possible to specify a time period over which performance information is to be recorded. The time period shall be configurable. +- 67 M The transport function in the OLT, ONU/ONT and NT shall monitor the receive and transmit bit-error rates over the corresponding physical layer to determine the transport integrity. Errors above a configured threshold shall be reported to the EM-OSF. +- 68 M The NE shall suppress all monitoring intervals that have zero counts within any scheduled report that is sent to the EM-OSF. +- 69 O Performance monitoring shall involve gathering current and historical statistical data relating to 15-minute intervals over a 24-hour period for the purpose of monitoring and correcting the behaviour and effectiveness of the network. This information should also assist network analysis, network planning, capacity management and billing processes. +- 70 M The EM-OSF shall collect the following performance data: +- OLT and ONU/ONT common equipment performance (e.g., line cards, buffers, CPUs, etc.); + - SDH interface statistics (e.g., LOS, LCD, errored seconds, severely errored seconds, code violations, line errored seconds, line code violations, utilization); + - OAM cells transmitted; + - ATM protocol layer (e.g., cells discarded due to HEC violations, cells discarded due to protocol errors); + - AAL protocol layer (e.g., invalid fields, CRC-32 violations, reassembly timer expiry, sequence violations, buffer under/overflow); + - cells discarded due to UPC/NPC disagreement for each virtual connection; + - SDH, PON and xDSL interface statistics (e.g., LOS, LCD, error second). + +#### **I.4.3.4 Accounting management** + +- 71 O The NE shall collect usage data at the SNI and UNI for billing purposes. + +### I.4.3.5 Security management + +- 72 M Where applicable, network equipment shall perform an authentication handshake upon connection to the NE. The authentication handshake is implementation dependent but would include such actions that verify the equipment is of the right type, checking for manufacturer-specific information, compatibility of software and hardware version information, etc. Resources that fail this authentication check shall not be configured or allowed to use network capacity. +- 73 M The NE shall perform a consistency check of its data upon request from the EM-OSF. This check shall compare the data held in the NE and EM-OSF databases. Inconsistencies shall be reported to the EM-OSF. The NE shall prevent reporting of events from a resource until it has completed the consistency check. +- 74 M The NE shall not configure any equipment that has been identified as unknown by the integrity check. + +### I.4.4 Element management layer requirements + +#### I.4.4.1 Configuration management + +- 75 M The EM-OSF shall provide functions to support management of Network Planning and Engineering and Network and Service provision. +- 76 M It shall be possible to manage all variants of an NE (both new version of the same product and FTTx products from the same range) from a single vendor using the same EM-OSF. The EM-OSF shall also be able to manage NEs from multiple vendors. +- 77 M The EM-OSF shall be able to create, modify, display and delete the logical representations of the resources required to manage the network and services. All necessary network and service parameters shall be supplied in the appropriate request. Table I.3 shows examples of logical NE resources and Table I.4 shows logical connection resources that shall be held by the EM-OSF. + +**Table I.3/Q.834.1 – FSAN logical NE resources** + +| Logical resource | Description | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| OLT | Represents the physical shelf in the exchange | +| ONU | Represents the physical FTTx cabinet and its inherent functions | +| Transmission System (TS) | Represents the card(s) which support the Bit Transport functions. There will be a transmission system resource in the OLT and ONU | +| Transmission Interface (TI) | Represents the ODN interface card(s). There will be a transmission interface resource in the OLT and ONU | +| SN Interface (SI) | Represents the service specific interface cards to the service node | +| Customer Interface (CI) | Represents the service specific customer interface cards | +| Power Supply Unit (PSU) | Represents the Power Supply Unit card(s) | +| Network Termination (NT) | Represents the physical unit to which customer premises equipment is connected. This resource may only exist for some service types | +| Management Function (MF) | Represents the card(s) which perform the management functions. This resource will exist on the OLT and may exist on the ONU | +| Test Function (TF) | Represents the test facility card(s) | +| Outlets | Represents the physical connectors on the SI, CI and TI | +| Slots | Represents the physical locations into which cards are inserted. Both OLT and ONU can have slots | + +**Table I.4/Q.834.1 – FSAN logical connection resources** + +| Logical resource | Description | +|-------------------------|-----------------------------------------------------------------------------------------------| +| Channels | Represents a subdivision of the service-specific bandwidth provided at a SI or CI outlet | +| Path | Represents a path from an OLT to an ONU or from an ONU to an NT. Can represent a virtual path | +| Circuit | Represents a circuit from a SI outlet to an CI or NT outlet. Can represent a virtual circuit | + +- 78 M The EM-OSF shall maintain a database containing the logical representations, state and relationship of the resources being managed. +- 79 M It shall be possible to create the logical resources in the EM-OSF database without the need for equipment to be physically present in the network. +- 80 M The EM-OSF shall maintain and respond to state and relationship information changes for all resources. +- 81 M Any management operation which violates a resource relationship or causes an invalid state transition shall not be allowed. An example of this is a request to create an SI before creating an OLT. In all such cases, the request should be rejected with a useful message to the source of the request. +- 82 M The EM-OSF shall automatically allocate the required resources if they are not identified in the provision request. +- 83 M If all spare and installed resources are in use, the EM-OSF shall use the next available spare and not installed resources. +- 84 M If there are no spare resources awaiting installation, then the EM-OSF shall propose a list of the equipment that needs to be installed to allow the request to be fulfilled. The equipment list shall indicate: +- the type of equipment to be installed; + - the location where it is to be installed (rack/shelf/slot, OLT or ONU etc.); + - the software and hardware versions which are compatible with the existing version of installed hardware. +- 85 M Each equipment list shall be stored in the EM-OSF until an event is received from the NE to indicate that the network equipment has been physically installed and has been correctly authenticated. +- 86 M It shall be possible to pre-configure equipment prior to its installation by providing the required data when the logical representation is created. +- 87 M It shall be possible to modify service parameters (such as bit rate, service type, error checking as applicable) for individual UNI(s) or Virtual Paths (VPs). +- 88 M The EM-OSF shall support download of configuration information when equipment is installed. Where multi-service equipment is used, it shall be possible to download service-specific software. +- 89 M It shall be possible to change the UNI or SNI of a path to use spare resources, thus enabling the path to be re-configured. +- 90 M A new network or service provision request shall not affect service to other customers on the network. +- 91 M All resource state information shall be consistent with the visual indications and state of the NE. + +- 92 M A capacity management function shall be provided by the EM-OSF to monitor NE usage. The rate of take-up of network resources shall be monitored by the EM-OSF. This function shall provide the information listed below to assist with network planning: +- the network equipment that is in use; + - the network equipment that is spare; + - the network equipment that is faulty; + - the amount of PON bandwidth that is in use for permanently configured paths; + - the amount of PON bandwidth that is spare for permanently configured paths; + - the location of network equipment; + - the types of service that can be supported by the spare bandwidth. +- 93 M The EM-OSF shall determine the increase or decrease in capacity based on the equipment installation event report from the NE. The inventory information in this event report shall be recorded in the EM-OSF database. This information shall only be deleted when the logical resource has been marked for removal and the equipment is physically removed from the network. +- 94 M The capacity management function shall take account of any modification to the network or service which creates new capacity, releases capacity, or uses spare capacity. The impact of planning and rearrangement of the network shall also be evaluated by this function. +- 95 M All requests to create, modify and delete network resources shall be logged. Each request shall be recorded with the identity of the source that originated the request and the date of the request. +- 96 M The EM-OSF shall provide functions for storage, backup, restoration and maintenance of NE configuration, connectivity and service-related information. +- 97 M Restoration of network element information from storage media shall be accomplished through software download from the EM-OSF to the NE via the data communications network. +- 98 M The monitoring function shall allow a user or NM-OSF to set/modify capacity thresholds. An event shall be generated to the user or NM-OSF when a capacity threshold is exceeded. The threshold exceeded event shall remain visible to the user or NM-OSF until it is acknowledged. + +#### **I.4.4.2 Fault management** + +- 99 M The EM-OSF shall provide network surveillance and network testing functions to support network maintenance. +- 100 M Detection of a fault, through network surveillance or network testing, which is affecting service shall cause the related equipment to be placed in an unavailable state for provisioning purposes. +- 101 M It shall be possible to block and unblock resources which provide service to allow equipment to be maintained. Whilst a resource is blocked for maintenance purposes it shall not be possible to use the service supported by that resource. The event report shall use the format described in [I-13]. +- 102 M The EM-OSF shall be capable of reporting the following categories of faults to the NM-OSF: +- faults on the network equipment; + - faults on interfaces; + - environmental conditions within the network element where applicable. + +- 103 M Fault reports shall accurately indicate the cause, severity, time and location of conditions detected by the network down to specific replaceable equipment. +- 104 M Fault information shall be presented to the user in a human-readable and easy-to-understand format. +- 105 M The EM-OSF shall allow a user or NM-OSF to acknowledge and mark outstanding faults as cleared where this is not detected automatically. +- 106 M It shall be possible to invoke self-tests on specific network equipment from the EM-OSF. +- 107 O It shall be possible to verify the correct configuration of a service by requesting a connection test from the EM-OSF to the NE. +- 108 M Where there is an occurrence of a large number of faults, the EM-OSF shall analyse and correlate the faults within its domain to determine the underlying cause of the problem. This should result in the escalation of one fault report with an appropriate repair action to a user or NM-OSF. +- 109 M It shall be possible to set and modify service-specific failure thresholds. A fault shall be reported to the specified users or NM-OSF when a threshold is exceeded. +- 110 M The EM-OSF is required to use all available information (such as known network faults and performance data) to support proactive fault location and hence reduce the need for the use of test functions. +- 111 M All fault reports shall be logged. +- 112 M The EM-OSF shall accept and act on requests to permit/inhibit fault reports from the NM-OSF. +- 113 M It shall be possible to apply test loops to the NE manually on a demand basis during fault diagnosis, or automatically as part of background test routines to aid proactive fault location. It shall be possible to activate/deactivate a bit error rate test source in the NE to check for errors on the path between the loops. +- 114 O The EM-OSF shall take account of the impact on network capacity as a result of automatic reconfiguration performed by the NE to rectify a fault. It shall be possible to manually invoke this capability from the EM-OSF. + +#### **I.4.4.3 Performance management** + +- 115 M It shall be possible to activate and deactivate the performance monitoring functions from the EM-OSF. When a monitoring function is activated, it shall be possible to specify a time period over which performance information is to be recorded. The time period shall be configurable. +- 116 M Certain performance monitoring data shall be collected automatically to support the generation of Quality of Service (QoS) information. The management system shall provide QoS information for each of the ATM Constant Bit Rate (CBR), Variable Bit Rate (VBR) and Available Bit Rate (ABR) class of service supported by the network. This information shall include cells discarded, CLP=0 cells discarded, cells successfully passed and CLP=0 cells successfully passed. +- 117 O Performance management shall involve gathering statistical data for the purpose of monitoring and correcting the behaviour and effectiveness of the network. This information should also assist network analysis, network planning, capacity management and billing processes. +- 118 M The EM-OSF shall provide performance data on demand via the user interface, or shall generate performance reports periodically as reports according to a pre-established schedule. + +#### **I.4.4.4 Accounting management** + +- 119 O The EM-OSF shall provide the capability to collect data on the use of the access network which will be used to determine access network usage charges. This data will be provided by the NE. + +#### **I.4.4.5 Security management** + +- 120 M It shall be possible to request an integrity check of data held by the NE with the data held by the EM-OSF. + +### **I.4.5 Network management layer requirements** + +#### **I.4.5.1 Configuration management** + +- 121 M The NM-OSF shall be able to create, modify, display and delete logical resources and paths for end-to-end network and service provision. All necessary parameters shall be supplied in the appropriate request. +- 122 M The NM-OSF shall maintain a database containing the logical representations, state and relationship of the NML resources being managed. +- 123 M It shall be possible to create the logical resources in the NM-OSF database without the need for the EM-OSF to be present. +- 124 M The NM-OSF shall maintain and respond to state and relationship information changes for all NML resources. +- 125 O The NM-OSF shall partition logical and physical inventory data by service domains. +- 126 M It shall be possible to access the management facilities on the EM-OSF via a remote login facility on the NM-OSF. +- 127 M The NM-OSF user shall receive an indication on the success or failure of all create, modify, delete or display operations. + +#### **I.4.5.2 Fault management** + +- 128 M The NM-OSF shall correlate faults from a number of EM-OSF domains to determine the actual location of a network problem. +- 129 M The NM-OSF shall parse and filter all faults received from an EM-OSF based on service criteria. +- 130 M It shall be possible to acknowledge and/or clear a fault received by the NM-OSF via the user interface. +- 131 O A facility shall be provided to monitor faults that have not been acknowledged by a user. An alert shall be raised for any fault which has not been dealt with within a configured time. +- 132 M The NM-OSF shall maintain a mapping of all faults which have been received and which have not been cleared. This requirement should contain a list of services impacted. +- 133 M It shall be possible for a NM-OSF to permit/inhibit fault reports to/from an EM-OSF. + +#### **I.4.5.3 Performance management** + +- 134 M The NM-OSF shall provide end-to-end network performance reports based on the performance information collected by the EM-OSFs. + +#### **I.4.5.4 Accounting management** + +- 135 I This area is for further study. + +#### **I.4.5.5 Security management** + +- 136 I This area is for further study. + +## **I.5 Data communications network** + +- 137 I The Data Communications Network (DCN) which conveys the management information between the operations functions is a key component of the management architecture. +- 138 I The DCN between the NE and the EM-OSF must take into account traffic volumes, security and the geographically dispersed nature of the physical resources being managed. +- 139 M The DCN between the NE and EM-OSF shall be based on IP or ITU-T Rec. X.25. +- 140 M The NMS shall periodically check the communication to the EMS. The EMS shall periodically check the communication to the FSAN NE. + +## **I.6 Element management platform** + +- 141 I This clause defines the requirements of the system platform on which an EM-OSF will reside and execute. + +### **I.6.1 Operating system** + +- 142 M The operating system shall be based on supported versions of UNIX or Windows NT. + +### **I.6.2 Availability** + +- 143 I Non-availability shall be considered as loss of any part of the functionality of the system platform for whatever reason. +- 144 M The system platform should have an availability of over 99.9% of planned operation time. + +### **I.6.3 Portability** + +- 145 M The management software shall be portable from one supported version of an operating system to a new version of the same operating system on the same or higher specification system platform. It shall be possible to port management software across the last 4 versions of an operating system. + +### **I.6.4 Scalability** + +- 146 M The management software should be designed so that it can be economically provisioned in small to large deployments. For example, to increase management capacity it would only be necessary to increase hard disk capacity and/or provide additional memory. +- 147 M For a fibre-to-the-home architecture, the system platform should be dimensioned to be capable of managing a minimum of 50 OLTs and the maximum number of subtending ONTs as specified in the architecture section in the FSAN specification [I-2]. For a fibre-to-the-building/office/curb architecture, the system platform should be dimensioned to be capable of managing a minimum of 100 OLTs including the maximum number of subtending ONUs and NTs. + +### **I.6.5 Maintainability** + +- 148 M The system platform shall provide administration functions which facilitate effective and efficient system maintenance such as back up and restoration of data, simple upgrade procedures, simple installation procedures, simple recovery procedures, etc. + +### **I.6.6 Performance** + +- 149 M Typical system platform response times shall be as follows: +- less than 3 minutes for system startup (for warm restart of a configured system); + - less than 1 minute for user log-in. +- 150 M Typical application response times shall be as follows: +- less than 2 seconds between sending a command and confirmation of receipt of the command; + +- execution of a command within 6 seconds of receipt. + +151 I NOTE – The above times do not take account of delays due to the DCN. + +#### **I.6.7 Migration strategy** + +152 M The supplier shall provide a migration strategy if there is a need to move to a different platform or software application during the life of the product. This specifically covers the rebuilding of network data from an existing database to a new database. This capability shall remove the need for re-entering network data that has already been entered. + +#### **I.6.8 Overload** + +153 M Overload conditions shall not cause the complete failure of the system platform to function. Overload shall only result in a graceful degradation of the system platform performance. + +#### **I.6.9 Evolution/Upgrade** + +154 M System platform hardware and software upgrades and evolution shall not impact quality of service to customers. + +155 M Any system platform software and hardware upgrades should support "backwards compatibility". + +156 M It shall be possible to roll-back gracefully to the former software version under manual control if a problem occurs during system platform upgrade. + +157 M The system platform shall provide a software download function to upgrade software in the NE. + +#### **I.6.10 User interface requirements** + +158 M It shall be possible to access the management functions on the system platform from remote locations. Access to management functions shall be form-based or icon-based as appropriate to the facility and shall be supported via a Graphical User Interface (GUI) or from a Hypertext Mark-up Language (HTML)-based World Wide Web (WWW) interface. + +159 M The system platform shall allow configuration of different user profiles. It shall be only be possible to create/display/modify/delete user profiles from a privileged user profile. This facility shall allow the privileged user to set/modify the user identification, password, access rights to applications and data, password expiry and number of attempts to enter a password. + +160 M The interface between the system platform and the user shall be designed in a manner that allows reusability across different OSFs from the same vendor. + +161 M The interface between the system platform and the user shall support hierarchical advancement displays. An example would be to display the network as an icon; by clicking on this icon the user is presented with more icons that provide details of the components in the network (e.g., OLTs and ONU/ONTs). Selection of the OLT or ONU/ONT would show the details of the cards. This type of view will also be needed for the VPs and VCs (e.g., list all VCs associated with a VP or list all VPs which are associated with a given service). + +162 M System administration functions shall be executable from a workstation/terminal connected directly to the management system platform. + +163 M It shall be possible to copy information from one window to another on the system platform to reduce operator retyping. + +164 M The system platform should provide acknowledgement that user commands have been completed. A suitable indication shall show that a command is being processed when this means further entry to the system cannot take place until its completion. + +### **I.6.11 DCN interface requirements** + +165 M The system platform shall provide interfaces to either an IP or X.25 networks for communications with the NE. In addition, the system platform shall provide an alternative to IP and X.25 where these networks do not exist. + +### **I.7 Fault and performance management of the transmission medium** + +166 M The following functions shall be provided for maintenance of the transmission medium (passive optical network and copper drop medium): + +- monitoring of transport integrity; +- detection and reporting of defects and failures; +- protection switching; +- location of faults using test systems; +- ability to run diagnostics; +- automatic restoration; +- test access. + +#### **I.7.1 Passive Optical Network** + +167 M The transport function in the OLT and ONU/ONT shall monitor the bit error rates at the source and sink of the PON to determine the transport integrity. Errors above a configured threshold shall be reported to the management system. + +168 M Detection of failures in the received signal at the OLT or ONU/ONT shall cause the OLT to report the fault to the management system. If the failure is detected by the OLT, an immediate switch shall be performed to a standby PON if one is available. A failure on the received signal at the ONU shall cause the ONU to switch off until communication between OLT and ONU/ONT can be re-established. + +169 M Protection switching capability shall be available at the OLT to switch between a main and standby PON. + +170 M The management system is required to distinguish between faults on the PON or ONU/ONT. + +171 O Any test function which is employed shall accurately report the location of a fault on the PON. + +172 M The network shall support the five OAM hierarchical levels associated with the physical and ATM layers of the B-ISDN protocol reference model as described in ITU-T Rec. I.610 [I-12]. + +173 M The physical layer transmission system shall support the F1, F2 and F3 flows and their associated OAM functions (see Table I.5). These flows shall be carried in maintenance cells at the physical layer which conforms to the cell format described in ITU-T Rec. I.432 [I-13]. + +**Table I.5/Q.834.1 – Physical layer OAM flows** + +| Flow | Functions | +|-------------|-----------------------------------------------------------------------------------------------------| +| F1 | Signal detection and frame alignment (e.g., Loss of signal or frame, laser switch-off) | +| F2/F3 | Error monitoring, automatic protection switching, cell slot allocation and ranging error monitoring | + +174 M The ATM Layer shall support the F4 and F5 OAM flows (see Table I.6). + +Table I.6/Q.834.1 – ATM layer OAM flows + +| Flow | Functions | +|------|-----------------------------------------------------------------------------| +| F4 | Fault and performance monitoring information on virtual path connections | +| F5 | Fault and performance monitoring information on virtual channel connections | + +175 M It shall be possible to configure segment AIS/RDI for F4 and F5 flows. In addition, it shall be possible to enable and disable the emission of AIS/RDI in the F4 and F5 flows. The AIS/RDI message shall report the conditions described in Table I.7. + +Table I.7/Q.834.1 – F4 and F5 OAM conditions + +| Function | Description | Direction
ONU/ONT
OLT | +|--------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------| +| Alarm Indication Signal (AIS) | All 1's bit pattern. Reported by the end that has lost its received signal. Sent as VP-AIS/VC-AIS at ATM layer. | ←→ | +| Remote Defect Indication (RDI) | Indicates that the remote end has detected loss of signal or AIS. Sent as VP-RDI/VC-RDI at ATM layer. | ←→ | + +Figure I.5 shows examples of OAM flows and is not all inclusive of possible flows. Where the service node is owned by a different operator, cooperation is required on F5 to the service node. All OAM flows across the T reference point will need to be allowed where the TE is managed as part of the access network. + +![Figure I.5/Q.834.1 – FSAN OAM flows diagram. The diagram illustrates the network architecture and OAM flow directions. On the left, a vertical dashed line marks the (T) reference point (UNI). On the right, a vertical dashed line marks the (V) reference point (SNI). The network components include an ONT connected to the (T) reference point, an ODN (Optical Distribution Network) in the center, and an OLT connected to the (V) reference point. A service node (SN) is connected to the OLT. A Drop Medium is shown between the ONT and the ONU. An NT (Network Terminator) is also shown. Below the network diagram, four horizontal arrows indicate OAM flow directions: 1. F2/F3 (VDSL) flow from the (T) reference point to the ONT. 2. F1/F2/F3 (BPON) flow from the ONT to the ODN. 3. F4/F5 flow from the ODN to the OLT. 4. F4/F5 flow from the OLT to the (V) reference point. The label Q.834.1_F15 is located at the bottom right of the diagram area.](a969a3a831d0967b54efe1400846ed30_img.jpg) + +Figure I.5/Q.834.1 – FSAN OAM flows diagram. The diagram illustrates the network architecture and OAM flow directions. On the left, a vertical dashed line marks the (T) reference point (UNI). On the right, a vertical dashed line marks the (V) reference point (SNI). The network components include an ONT connected to the (T) reference point, an ODN (Optical Distribution Network) in the center, and an OLT connected to the (V) reference point. A service node (SN) is connected to the OLT. A Drop Medium is shown between the ONT and the ONU. An NT (Network Terminator) is also shown. Below the network diagram, four horizontal arrows indicate OAM flow directions: 1. F2/F3 (VDSL) flow from the (T) reference point to the ONT. 2. F1/F2/F3 (BPON) flow from the ONT to the ODN. 3. F4/F5 flow from the ODN to the OLT. 4. F4/F5 flow from the OLT to the (V) reference point. The label Q.834.1\_F15 is located at the bottom right of the diagram area. + +Figure I.5/Q.834.1 – FSAN OAM flows + +I.7.2 Drop medium between ONU and NT + +176 I VDSL modem technology on existing copper facilities would be a typical application. + +177 M Table I.8 lists the required OAM functions for the VDSL interface which will be used on the copper drop medium. It shall be possible to activate/deactivate these functions depending on the needs of the service being delivered to the customer. + +**Table I.8/Q.834.1 – List of OAM functions to be supported by VDSL** + +| Function | Description | Direction | +|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------| +| | | NT      ONU | +| Loss of signal | Indicates no recognized signal at receiver | ←→ | +| Loss of sync | Indicates loss of synchronization clock | ←→ | +| Reset control | Allows NT to be reset | ← | +| Error detection (Far/Near end) | Detection of error rates in transmit and received signals | ←→ | +| Error reporting (Far/Near end) | Reporting of the errors detected to an OS or locally (e.g., LED) | ←→ | +| Loopback control | Allows loops to be set up at NT or ONU | ← | +| Number of far/near end block error corrections | Indication of number of block errors for performance purposes | ←→ | +| Dying Gasp | Indicates impending loss of power | → | +| Error correction switch on/off mechanism | Ability to switch error correction mechanisms on or off depending on whether it is needed or not | ← | +| Channel quality (Signal-to-Noise margin) | Comparison of incoming signal with configured value to estimate channel quality. Can be used also for proactive maintenance | → | +| Data integrity check | The NT shall have the capability to notify the management system when it receives invalid data | → | +| NT Loopback capabilities | The NT shall be capable to support the I.610 ATM layer loopback capabilities | ←→ | +| F1, F2, F3, F4 and F5 | The VDSL should support the F1 to F5 information flows | ←→ | +| NT configuration | Ability to modify bit rates and other configurations in the NT | ← | +| Activation/deactivation | Ability to set NT in sleep mode to reduce power consumption when there is no activity | ←→ | + +## I.8 References + +- [I-1] FAULKNER (D.) *et al*: The Full Services Access Network Initiative, *IEEE Communications Magazine*, April 1997, Vol. 35, No. 4. +- [I-2] Full Services Access Network Requirements Specification +- [I-3] ADAMS (E.), WILLETTS (K.): The Lean Communications Provider, *McGraw-Hill*. +- [I-4] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [I-5] ITU-T Recommendation G.902 (1995), *Framework Recommendation on functional access networks (AN) – Architecture and functions, access types, management and service mode aspects*. +- [I-6] ITU-T Recommendation G.982 (1996), *Optical access networks to support services up to the ISDN primary rate or equivalent bit rates*. +- [I-7] ITU-T Recommendation M.3100 (1995), *General network information model*. + +- [I-8] ITU-T Recommendation X.710 (1997) | ISO/IEC 9595:1998, *Information technology – Open Systems Interconnection – Common Management Information service.* +- [I-9] ITU-T Recommendation X.711 | ISO/IEC 9596-1:1998, *Information technology – Open Systems Interconnection – Common Management Information Protocol: Specification.* +- [I-10] Service Requirements – Minutes of FSAN SCP Working Group. +- [I-11] SCP directory, BellSouth FSAN server November 1997, Draft 1. +- [I-12] ITU-T Recommendation I.610 (1999), *B-ISDN operation and maintenance principles and functions.* +- [I-13] ITU-T Recommendation I.432.x (1999), *B-ISDN User-network interface – Physical layer specification.* +- [I-14] ITU-T Recommendation M.3013 (2000), *Considerations for a telecommunications management network.* + +## Appendix II + +### Tables of managed entities + +#### II.1 NE view + +**Table II.1/Q.834.1 – Usage of managed entities name (NE View)** + +| Managed entity name in this Recommendation | Related managed object name in other ITU-T Recommendations | Ref. | +|--------------------------------------------|------------------------------------------------------------|------| +| AAL1PMCurrentDataF | AALProtocolCurrentData (Q.824.6) | AF20 | +| AAL1PMHistoryDataF | AALProtocolHistoryData (Q.824.6) | AF20 | +| AAL1ProfileF | AALProfile (Q.824.6) | AF20 | +| AAL2PMCurrentDataF | | new | +| AAL2PMHistoryDataF | | new | +| AAL2ProfileF | | new | +| AAL2PVCPProfileF | | new | +| AAL5PMCurrentDataF | AALProtocolCurrentData (Q.824.6) | AF20 | +| AAL5PMHistoryDataF | AALProtocolHistoryData (Q.824.6) | AF20 | +| AAL5ProfileF | AALProfile (Q.824.6) | AF20 | +| adslCTPF | | new | +| adslTTPF | | new | +| alarmLogRecordF | alarmRecord (X.721) | AF20 | +| alarmSeverityAssignmentProfileF | alarmSeverityAssignmentProfile (M.3100) | AF20 | +| APONCTP | | new | +| APONStaticBW | | new | +| APONPMCurrentData | | new | +| APONPMHistoryData | | new | +| APONTP | | new | + +**Table II.1/Q.834.1 – Usage of managed entities name (NE View)** + +| Managed entity name in this Recommendation | Related managed object name in other ITU-T Recommendations | Ref. | +|---------------------------------------------------|-------------------------------------------------------------------|-------------| +| ATMCrossConnectionControlF | atmFabric (I.751) | AF20 | +| ATMCrossConnectionF | atmCrossConnection (I.751) | AF20 | +| ATMNetworkAccessProfileF | | new | +| ATMTrafficLoadCurrentDataF | atmTrafficLoadCurrentData (I.751) | AF20 | +| ATMTrafficLoadHistoryDataF | atmTrafficLoadHistoryData (I.751) | AF20 | +| attributeValueChangeRecordF | AttributeValueChangeRecord (X.721) | AF20 | +| au3CTPF | au3CTP (G.774) | | +| au4CTPF | au4CTP (G.774) | | +| BICIF | InterNNI (I.751) | AF20 | +| BISSIF | IntraNNI (I.751) | AF20 | +| bridgedLANServiceProfileF | | new | +| cellBasedCTPF | | new | +| cellBasedTTPF | | new | +| CESServiceProfileF | | AF20 | +| CTPF | | new | +| DS1CTPF | | new | +| DS1PMCurrentDataF | | new | +| DS1PMHistoryDataF | | new | +| DS1TTPF | | new | +| DS3CTPF | | new | +| DS3PMCurrentDataF | | new | +| DS3PMHistoryDataF | | new | +| DS3TTPF | | new | +| E1CTPF | | new | +| E1PMCurrentDataF | | new | +| E1PMHistoryDataF | | new | +| E1TTPF | | new | +| E3CTPF | | new | +| E3PMCurrentDataF | | new | +| E3PMHistoryDataF | | new | +| E3TTPF | | new | +| equipmentHolderF | equipmentHolder (M.3100) | AF20 | +| EthernetCTPF | | new | +| EthernetPMCurrentDataF | | new | +| EthernetPMHistoryDataF | | new | +| EthernetProfileF | | new | +| EthernetTTPF | | new | + +**Table II.1/Q.834.1 – Usage of managed entities name (NE View)** + +| Managed entity name in this Recommendation | Related managed object name in other ITU-T Recommendations | Ref. | +|---------------------------------------------------|-------------------------------------------------------------------|-------------| +| filterProfileF | | new | +| LESServiceProfileF | | new | +| logF | log (X.721) | AF20 | +| MACBridgeConfigurationDataF | | new | +| MACBridgeF | | new | +| MACBridgePMCurrentDataF | | new | +| MACBridgePMHistoryDataF | | new | +| MACBridgePortConfigurationDataF | | new | +| MACBridgePortPMCurrentDataF | | new | +| MACBridgePortPMHistoryDataF | | new | +| MACBridgeServiceProfileF | | new | +| managedEntityCreationLogRecordF | objectCreationRecord (X.721) | AF20 | +| managedEntityDeletionLogRecordF | objectDeletionRecord (X.721) | AF20 | +| MLTTestResultsF | | new | +| msCTPF | msCTP (G.774) | | +| msTTPF | msTTP (G.774) | | +| NEFSAN | | new | +| NT | equipmentR1 (M.3100) | | +| OLT | managedElementR1 (M.3100) | | +| ONT | managedElementR1 (M.3100) | | +| ONU | managedElementR1 (M.3100) | | +| PhysicalPathTPF | | AF20 | +| pluginUnitF | circuitPack (M.3100) | AF20 | +| rsCTPF | rsCTP (G.774) | | +| rsTTPF | rsTTP (G.774) | | +| softwareF | softwareR1 (M.3100) | AF20 | +| SSCSParameterProfile1F | SSCSParameterProfile1 (I.366.1) | | +| SSCSParameterProfile2F | SSCSParameterProfile2 (I.366.2) | | +| tcAdaptorF | tcAdaptorTTP (I.751) | AF20 | +| thresholdDataF | thresholdData (Q.822) | AF20 | +| trafficDescriptorProfileF | | AF20 | +| TTPF | | new | +| uniF | uni (I.751) | AF20 | +| uniInfoF | | new | +| upcNpcDisagreementPMCurrentDataF | upcNpcCurrentData (I.751) | AF20 | +| upcNpcDisagreementPMHistoryDataF | upcNpcHistoryData (I.751) | AF20 | +| vc3TTPF | vc3TTP (G.774) | | + +**Table II.1/Q.834.1 – Usage of managed entities name (NE View)** + +| Managed entity name in this Recommendation | Related managed object name in other ITU-T Recommendations | Ref. | +|------------------------------------------------------------------|-------------------------------------------------------------------|-------------| +| vc4TTPF | vc4TTP (G.774) | | +| vcCTPF | vcCTP (I.751) | AF20 | +| vcTTPF | vcTTP (I.751) | | +| vdslCTPF | | new | +| vdslTTPF | | new | +| VoiceCTPF | | new | +| VoicePMCurrentDataF | | new | +| VoicePMHistoryDataF | | new | +| VoiceServiceProfileAAL1F | | new | +| VoiceServiceProfileAAL2F | | new | +| VoiceTTPF | | new | +| vpCTPF | vpCTP (I.751) | AF20 | +| vpTTPF | vpTTP (I.751) | | +| vpvcPMCurrentDataF | vpvcPMCurrentData (I.751) | | +| vpvcPMHistoryDataF | vpvcPMHistoryData (I.751) | | +| Ref. References other than ITU-T Recommendations: AF-NM-0020.001 | | | +| new Newly defined | | | + +## II.2 Network view + +**Table II.2/Q.834.1 – Usage of managed entities name (Network View)** + +| Managed entity name in ITU-T Rec. Q.834.2 | Related managed object in other ITU-T Recommendations | Ref. | +|--------------------------------------------------|--------------------------------------------------------------|-------------| +| accessGroupF | AccessGroup (M3100amd) | | +| adslLayerNetworkDomainF | | new | +| adslLinkConnectionF | | new | +| adslSubnetworkF | | new | +| adslTopologicalLinkEndF | | new | +| adslTopologicalLinkF | | new | +| APONLayerNetworkDomain | | new | +| APONLink | | new | +| APONLinkConnection | | new | +| APONSubNetwork | | new | +| APONTrail | | new | +| BridgedLANLayerNetworkDomainF | | new | +| BridgedLANNetworkCTPF | | new | +| BridgedLANNetworkTTPF | | new | + +**Table II.2/Q.834.1 – Usage of managed entities name (Network View)** + +| Managed entity name in
ITU-T Rec. Q.834.2
| Related managed object in other
ITU-T Recommendations
| Ref. | +|------------------------------------------------------|------------------------------------------------------------------|-------------| +| BridgedLANSubnetworkF | | new | +| DS1LayerNetworkDomainF | | new | +| DS1SubnetworkConnectionF | | new | +| DS1SubnetworkF | | new | +| DS3LayerNetworkDomainF | | new | +| DS3SubnetworkConnectionF | | new | +| DS3SubnetworkF | | new | +| E1LayerNetworkDomainF | | new | +| E1SubnetworkConnectionF | | new | +| E1SubnetworkF | | new | +| E3LayerNetworkDomainF | | new | +| E3SubnetworkConnectionF | | new | +| E3SubnetworkF | | new | +| layerNetworkDomainF | LayerNetworkDomain (M3100amd) | AF58 | +| linkConnectionF | LinkConnection (M3100amd) | AF58 | +| logicalLinkEndF | LogicalLinkEnd (M3100amd) | | +| logicalLinkF | LogicalLink (M3100amd) | | +| logicalMTPLinkF | | new | +| tworkF | networkR1 (M.3100) | AF58 | +| subnetworkConnectionF | SubnetworkConnection (M3100amd) | AF58 | +| subnetworkF | Subnetwork (M3100amd) | AF58 | +| topologicalLinkEndF | TopologicalLinkEnd (M.3100amd) | AF58 | +| topologicalLinkF | TopologicalLink (M.3100amd) | AF58 | +| trailF | TrailR2 (M.3100amd) | AF58 | +| vcLayerNetworkDomainF | LayerNetworkDomain (M.3100amd) | AF58 | +| vcLinkConnectionF | LinkConnection (M.3100amd) | AF58 | +| vcLogicalLinkF | LogicalLink (M3100amd) | | +| vcSubnetworkConnectionF | SubnetworkConnection (M.3100amd) | AF58 | +| vcSubnetworkF | Subnetwork (M.3100amd) | AF58 | +| vcTopologicalLinkEndF | TopologicalLinkEnd (M.3100amd) | AF58 | +| vcTopologicalLinkF | TopologicalLink (M.3100amd) | AF58 | +| vcTrailF | TrailR2 (M.3100amd) | AF58 | +| vdslLayerNetworkDomainF | | new | +| vdslLinkConnectionF | | new | +| vdslSubnetworkF | | new | +| vdslTopologicalLinkEndF | | new | +| vdslTopologicalLinkF | | new | + +**Table II.2/Q.834.1 – Usage of managed entities name (Network View)** + +| Managed entity name in
ITU-T Rec. Q.834.2
| Related managed object in other
ITU-T Recommendations
| Ref. | +|-----------------------------------------------------------------|------------------------------------------------------------------|-------------| +| voiceLayerNetworkDomainF | | new | +| voiceSubnetworkConnectionF | | new | +| voiceSubnetworkF | | new | +| vpLayerNetworkDomainF | LayerNetworkDomain (M100amd) | AF58 | +| vpLinkConnectionF | LinkConnection (M.3100amd) | AF58 | +| vpLogicalLinkF | LogicalLink (M3100amd) | | +| vpSubnetworkConnectionF | SubnetworkConnection (M.3100amd) | AF58 | +| vpSubnetworkF | Subnetwork (M.3100amd) | AF58 | +| vpTopologicalLinkEndF | TopologicalLinkEnd (M.3100amd) | AF58 | +| vpTopologicalLinkF | TopologicalLink (M.3100amd) | AF58 | +| vpTrailF | TrailR2 (M.3100amd) | AF58 | +| Ref References other than ITU-T Recommendations: AF-NM-0058.001 | | | +| new Newly defined | | | + + + + + +## 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.834.4-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/Q/T-REC-Q.834.4-200307-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.834.4-200307-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63479355f0f09e80ba4a0e0b682f594e73596ede --- /dev/null +++ b/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31c9294118fc092ab12bb531a43e541e8d1cb3435702de571d55021d15885436 +size 127409 diff --git a/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b620a2810ea77d4990afe2221221106451b0dc1e --- /dev/null +++ b/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6801076136fe393282ba32d1df92fa9aa25cc1b9dc898b85ff87127a0588341 +size 43816 diff --git a/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/raw.md b/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..680073c03099dae31507221cd3d0f7eb3c20a71f --- /dev/null +++ b/marked/Q/T-REC-Q.834.4-200307-I_PDF-E/raw.md @@ -0,0 +1,10091 @@ + + +![ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.834.4 + +(07/2003) + +SERIES Q: SWITCHING AND SIGNALLING + +Q3 interface + +# --- **A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements** + +ITU-T Recommendation Q.834.4 + +--- + +## 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.834.4** + +# **A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements** + +## **Summary** + +This Recommendation provides a CORBA IDL definition for the management interface between a Supplier Management System and an Operator Management System. This work defines part of the management aspects for network resources defined by the G.983.x series of ITU-T Recommendations for Broadband Passive Optical Network (BPON) equipment. + +Generally speaking, the Supplier Management System is an Element Management System (EMS) and the Operator Management System (OMS) is a Network Management System (NMS). However, the Supplier Management System is required to present a "network view" of connection management to the Operator Management System. So it was deemed necessary for clarity's sake to use the terminology adopted in naming the systems involved. + +In addition, it should be noted that ITU-T Rec. Q.834.1 contains a set of functionality requirements and a listing of managed entity definitions forming the basis for management information required for a "network element view" of BPON equipment. ITU-T Rec. Q.834.2 completes the management information definition for management of BPON equipment by providing the definitions of managed entities for the "network view". ITU-T Rec. Q.834.3 addresses management interface behaviour through use of UML diagrams and Use Case descriptions. The management information modelled in ITU-T Recs Q.834.1 and Q.834.2 is referenced throughout this Recommendation and ITU-T Rec. Q.834.3. + +## **Source** + +ITU-T Recommendation Q.834.4 was approved on 7 July 2003 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. This edition includes the modifications introduced by Corrigendum 1 approved on 13 January 2004. + +## **Keywords** + +APON, BPON, CORBA, IDL, PON, UML. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|--------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 2.1 Normative references..... | 1 | +| 2.2 Other references..... | 2 | +| 3 Terms and definitions ..... | 2 | +| 3.1 Terms imported from ITU-T Rec. M.3010 ..... | 2 | +| 3.2 Terms imported from UML..... | 2 | +| 3.3 Terms imported from OMG Naming Service ..... | 3 | +| 3.4 Terms imported from ITU-T Rec. Q.834.1 ..... | 3 | +| 3.5 Terms imported from ITU-T Rec. Q.834.3 ..... | 3 | +| 3.6 New terms..... | 3 | +| 4 Abbreviations..... | 3 | +| 5 Conventions ..... | 5 | +| 5.1 Module description conventions..... | 5 | +| 5.2 IDL file conventions..... | 5 | +| 5.3 NULL values ..... | 6 | +| 6 Interface architecture overview ..... | 6 | +| 7 Names and naming constraint..... | 7 | +| 7.1 Service objects and OMG naming service ..... | 8 | +| 7.2 Domain objects..... | 9 | +| 8 Organization of IDL files..... | 9 | +| 9 Modules ..... | 10 | +| 9.1 AccessControl module..... | 10 | +| 9.2 Build module ..... | 16 | +| 9.3 Q834Common module ..... | 25 | +| 9.4 ControlArchive module ..... | 26 | +| 9.5 SoftwareDownload module ..... | 30 | +| 9.6 EventPublisher module..... | 37 | +| 9.7 MIBTransfer module ..... | 40 | +| 9.8 PerformanceManager module ..... | 43 | +| 9.9 ProfileManager ..... | 52 | +| 9.10 Registrar module ..... | 54 | +| 9.11 ResourceAllocation module ..... | 59 | +| 9.12 SchedulerManagement module ..... | 62 | +| 9.13 ServiceProvisioning module..... | 66 | +| 9.14 Synchroniser module ..... | 70 | +| 9.15 Test module ..... | 73 | +| 9.16 FileTransfer module ..... | 79 | + +| | Page | +|--------------------------------------------|-------------| +| 10 Compliance statement..... | 82 | +| Annex A – Data dictionary ..... | 82 | +| Annex B – Exceptions ..... | 104 | +| Annex C – IDL files..... | 109 | +| C.1 Q834AccessControl.idl ..... | 109 | +| C.2 Q834Build.idl ..... | 114 | +| C.3 Q834Common.idl ..... | 120 | +| C.4 Q834ControlArchive.idl ..... | 134 | +| C.5 Q834SoftwareDownload.idl ..... | 137 | +| C.6 Q834EventPublisher.idl..... | 142 | +| C.7 Q834MIBTransfer.idl ..... | 146 | +| C.8 Q834PerformanceManager.idl ..... | 149 | +| C.9 Q834ProfileManager.idl..... | 154 | +| C.10 Q834Registrar.idl ..... | 165 | +| C.11 Q834ResourceAllocation.idl ..... | 168 | +| C.12 Q834SchedulerManagement.idl ..... | 171 | +| C.13 Q834ServiceProvisioning.idl..... | 173 | +| C.14 Q834Synchroniser.idl..... | 176 | +| C.15 Q834Test.idl ..... | 178 | +| C.16 Q834Filetransfer.idl..... | 183 | +| Annex D – Example endpoint templates ..... | 186 | + +# ITU-T Recommendation Q.834.4 + +# A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements + +# 1 Scope + +This Recommendation addresses the design of an interactive mechanized interface between the Supplier Management System managing BPON network resources and an Operator Management System (OMS). The design is based on the UML diagrams and Use Case descriptions of ITU-T Rec. Q.834.3. The general approach adopted in ITU-T Rec. Q.834.3, and implemented here, is that the Supplier Management System provides management services to the Operator Management System. These services provide the OMS with a high level abstraction of the following capabilities: + +- Provisioning installed network resources; +- Provisioning uninstalled network resources including capacity reservation; +- Service provisioning; +- Archive management; +- NE software management; +- NE configuration data backup and restoral; +- Performance management; +- NE event publication; +- Profile management; +- Testing; +- Activity scheduling; +- Bulk transfer management; +- NE-EMS synchronisation; +- Access control. + +This Recommendation describes the CORBA IDL interfaces supporting the services listed above. + +# 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 M.3010 (2000), *Principles for a telecommunications management network*. +- [2] ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: Overview*. +- [3] ITU-T Recommendation M.3400 (2000), *TMN Management Functions*. +- [4] OMG Document formal/99-06-01, *Unified Modelling Language, Section 1*. + +- [5] ITU-T Recommendation G.983.1 (1998), *Broadband optical access systems based on Passive Optical Networks (PON)*, plus Amendment 1 (2001). +- [6] ITU-T Recommendation Q.834.1 (2001), *ATM-PON requirements and managed entities for the network element view*. +- [7] ITU-T Recommendation Q.834.2 (2001), *ATM-PON requirements and managed entities for the network view*. +- [8] ITU-T Recommendation Q.834.3 (2001), *A UML description for management interface requirements for Broadband Passive Optical Networks*. +- [9] ITU-T Recommendation M.3020 (2000), *TMN Interface Specification Methodology*. +- [10] ITU-T Recommendation G.983.2 (2002), *ONT management and control interface specification for B-PON*. +- [11] ITU-T Recommendation G.983.3 (2001), *A broadband optical access system with increased service capability by wavelength allocation*. +- [12] ITU-T Recommendation G.983.4 (2001), *A broadband optical access system with increased service capability using dynamic bandwidth assignment (DBA)*. +- [13] ITU-T Recommendation G.983.5 (2002), *A broadband optical access system with enhanced survivability*. +- [14] ITU-T Recommendation G.983.6 (2002), *ONT management and control interface specifications for B-PON system with protection features*. +- [15] ITU-T Recommendation G.983.7 (2001), *ONT Management and Control interface specification for Dynamic Bandwidth Assignment (DBA) B-PON system*. +- [16] ITU-T Recommendation X.780 (2001), *TMN guidelines for defining CORBA managed objects*. +- [17] ITU-T Recommendation Q.816 (2001), *CORBA-based TMN services*. + +## **2.2 Other references** + +- [18] OMG Document formal/02-09-02, *CORBA Services – Naming Service specification*. +- [19] OMG Document formal/02-08-04, *CORBA Services – Notification Service specification*. + +# **3 Terms and definitions** + +## **3.1 Terms imported from ITU-T Rec. M.3010** + +The following term from ITU-T Rec. M.3010 is used in this Recommendation: + +- User. + +## **3.2 Terms imported from UML** + +The following terms from UML [4] are used in this Recommendation: + +- Actor; +- Class; +- Class Diagram; +- Use Case. + +## 3.3 Terms imported from OMG Naming Service + +The following terms from OMG Naming Service [18] are used in this Recommendation: + +- Naming graph; +- Name. + +## 3.4 Terms imported from ITU-T Rec. Q.834.1 + +The following term from ITU-T Rec. Q.834.1 is used in this Recommendation: + +- Managed Entity. + +## 3.5 Terms imported from ITU-T Rec. Q.834.3 + +The following terms from ITU-T Rec. Q.834.3 are used in this Recommendation: + +- Activate; +- Assign; +- Autodiscovery; +- BPON resource; +- Build; +- Filtering; +- Install; +- Range; +- Register; +- Reserve; +- Service Instance; +- User Label. + +## 3.6 New terms + +This Recommendation defines the following terms: + +**3.6.1 service object:** The set of objects providing access to the management services implemented in the Supplier Management System. Interfaces to service objects constitute the specification for the portion of IF1 defined in this Recommendation. + +**3.6.2 domain object:** The set of objects defining the management information for management of BPON network resources. Domain objects are primarily provided by the Managed Entity listings of ITU-T Recs Q.834.1 and Q.834.2. + +**3.6.3 internal object:** The set of objects used to support Supplier Management System internal logic. They are completely obscure from the point of view of the OMS. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|--------------------------------------------| +| AAL | ATM Adaptation Layer | +| APON | ATM-PON | +| ATM | Asynchronous Transfer Mode | +| BICI | Broadband Inter-Carrier Interface | +| BISSI | Broadband Inter-Switching System Interface | +| BPON | Broadband Passive Optical Network | + +| | | +|-------|------------------------------------------------------------------| +| CAC | Call Admission Control | +| CCITT | Consultative Committee for International Telephone and Telegraph | +| CES | Circuit Emulation Service | +| CNM | Customer Network Management | +| CORBA | Common Object Request Broker Architecture | +| CTP | Connection Termination Point | +| CTT | Customer Trouble Ticket | +| DCN | Data Communications Network | +| DSx | Digital Signal x | +| EM | Element Management | +| EML | Element Management Layer | +| EMS | Element Management System | +| EOC | Embedded Operations Channel | +| Ex | European Digital Signal x | +| FSAN | Full Services Access Network | +| GUI | Graphical User Interface | +| IDL | Interface Definition Language | +| ITU | International Telecommunication Union | +| ME | Managed Entity | +| MIB | Management Information Base | +| NE | Network Element | +| NMS | Network Management System | +| NT | Network Terminal | +| ODN | Optical Distribution Network | +| OLT | Optical Line Terminal | +| OMG | Object Management Group | +| OMS | Operator Management System | +| ONT | Optical Network Terminal | +| ONU | Optical Network Unit | +| OS | Operations System | +| PON | Passive Optical Network | +| PVC | Permanent Virtual Circuit | +| QoS | Quality of Service | +| TCA | Threshold Crossing Alert | +| TMN | Telecommunications Management Network | +| TP | Termination Point | +| TTP | Trail Termination Point | +| UML | Unified Modelling Language | +| UNI | User-Network Interface | +| VC | Virtual Channel | +| VCC | Virtual Channel Connection | + +| | | +|-----|----------------------------| +| VCI | Virtual Channel Identifier | +| VP | Virtual Path | +| VPC | Virtual Path Connection | +| VPI | Virtual Path Identifier | + +# 5 Conventions + +There are two clauses in this Recommendation where specific conventions have been followed. The first is the description of the IDL Modules in clause 8 and the second is the IDL files found in Annex C. Finally, this Recommendation uses certain conventions involving null values. + +## 5.1 Module description conventions + +Module descriptions have the following pattern: + +- Module Name – services overview, including any relevant high-level modelling, key business data element descriptions, and scenarios as required. + - Interface Name – overview of the specific services provided by this interface. + - Operation Name1 – detailed description of the behaviour of this operation including signature of the operation, description of each input parameter, and description of the return value. + - ... + - Operation Namen – detailed description of the behaviour of this operation including signature of the operation, description of each input parameter, and description of the return value. + - Exceptions – context-specific conditions that cause the named exceptions to be raised. + +## 5.2 IDL file conventions + +Each IDL file has the following format: + +- **#ifndef \_\_\_DEFINED** (module name is the same as the filename); +- **#define \_\_\_DEFINED** +- **#include ""1** +- **#pragma prefix "itu.Int"** +- **module q834\_4 {** +- **module {** +- all the specific data type definitions and interface specifications needed and indicated by the interface design initiated from examination of ITU-T Rec. Q.834.3; +- **}; //module ** +- **}; //module q834\_4** + +Within each module definition, data type definitions precede and are segmented from the interface definitions. All data types defined in this Recommendation start with an initial capitalized alpha character. If data type names are joins of several proper nouns, pronouns, or adjectives, the join will expect a capitalized alpha character at the start of each component. Labels for parameters used in any interface operation signature start with a lower case alpha character. Each operation name begins with a lower case alpha character. + +--- + +1 Q834Common.idl file is included with every other IDL file in this Recommendation. + +## 5.3 NULL values + +In this Recommendation, when there is a mention of "null string", it is meant to be an empty string and not a null object supported by languages such as JAVA. Similarly, when a "null sequence" is mentioned, a sequence with zero elements is passed. + +# 6 Interface architecture overview + +Figure 1 illustrates the BPON network architecture and management system. This technology provides an integrated loop access delivery mechanism for every telecommunications service currently deployed by operators. A list of such services includes telephony and voice grade services, circuit-emulation, Ethernet, ATM, xDSL, and video. This standardization effort is ongoing in its consideration of layer 1 and 2 transport solutions on the ODN, although initial implementations exist in operator networks involving APON and ATM as defined in ITU-T Rec. G.983.1. + +The figure also shows the IF1 (Q) interface between the Supplier Management System and Operator Management Systems. The IF1 interface covers all aspects of network and service provisioning management, network performance management, traffic management, maintenance, testing, and user security administration. Specification of IF1 would have been an overwhelming challenge if the approach adopted had not pursued a level of abstraction above the transport delivery technology details as well as the complexities inherent in managing so many service types. The approach included the definition and description of interface requirements using Unified Modelling Language, followed the methodology of ITU-T Rec. M.3020, and was documented in ITU-T Rec. Q.834.3. + +The operator systems identified in this diagram correspond directly to system actors defined in ITU-T Rec. Q.834.3. This Recommendation specifies the interactive real-time transactions involving the Supplier Management System and does not explicitly describe the file structures transferred between the Supplier Management System and either the Data Warehouse or Secure File Server. Since the interfaces to OMG Naming Service and OMG Notification Service are already specified, the focus of this Recommendation narrows down to messaging between the Supplier Management System and the shaded system actors. + +![Figure 1/Q.834.4 – Interface architecture overview. This diagram illustrates the interface architecture of a Supplier Management System (SMS). The SMS is a central oval connected to several external entities: Data warehouse, Secure file server, Privileged user, Profile object repository, Other OMSs, OMS notification service, and OMS naming service. Dashed lines labeled 'IF1' connect the SMS to the Data warehouse, Secure file server, and OMS notification service. A dashed line labeled 'Non Real-time' connects the SMS to the Secure file server. A dashed line labeled 'Real-time' connects the SMS to the OMS naming service. The SMS is also connected to an OLT (Optical Line Terminal) within a dashed box labeled 'BPON network elements'. The OLT is connected to an ODN (Optical Distribution Network) oval, which is then connected to a stack of ONUs (Optical Network Units). The ONUs are connected to a stack of NTs (Network Terminals) via an NNI (Network to Network Interface). The NTs are connected to a stack of ONTs (Optical Network Terminals) via a UNI (User-Network Interface). The ONTs are connected to a stack of ONTs via a UNI. The diagram is labeled 'Q.834.4_F01'.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Q.834.4\_F01 + +| | | | | +|-------|--------------------------------------------|-----|------------------------------| +| BICI | Broadband Inter-Carrier Interface | ODN | Optical Distribution Network | +| BISSI | Broadband Inter-Switching System Interface | OLT | Optical Line Terminal | +| BPON | Broadband Passive Optical Network | ONT | Optical Network Terminal | +| NNI | Network to Network Interface | ONU | Optical Network Unit | +| NT | Network Terminal | UNI | User-Network Interface | + +Figure 1/Q.834.4 – Interface architecture overview. This diagram illustrates the interface architecture of a Supplier Management System (SMS). The SMS is a central oval connected to several external entities: Data warehouse, Secure file server, Privileged user, Profile object repository, Other OMSs, OMS notification service, and OMS naming service. Dashed lines labeled 'IF1' connect the SMS to the Data warehouse, Secure file server, and OMS notification service. A dashed line labeled 'Non Real-time' connects the SMS to the Secure file server. A dashed line labeled 'Real-time' connects the SMS to the OMS naming service. The SMS is also connected to an OLT (Optical Line Terminal) within a dashed box labeled 'BPON network elements'. The OLT is connected to an ODN (Optical Distribution Network) oval, which is then connected to a stack of ONUs (Optical Network Units). The ONUs are connected to a stack of NTs (Network Terminals) via an NNI (Network to Network Interface). The NTs are connected to a stack of ONTs (Optical Network Terminals) via a UNI (User-Network Interface). The ONTs are connected to a stack of ONTs via a UNI. The diagram is labeled 'Q.834.4\_F01'. + +**Figure 1/Q.834.4 – Interface architecture overview** + +# 7 Names and naming constraint + +This clause provides guidelines for object names and managed entity identifiers referenced on IF1. + +Review of all the class diagrams developed in ITU-T Rec. Q.834.3 shows that the Supplier Management System manages three distinct types of "objects". These can be classified as follows: + +- **Service Objects:** provide access to the management services implemented in the Supplier Management System. The interfaces of these services are the main subject of this Recommendation. A few examples are NERegistrar, ServiceProvisioner, TestActionPerformer, and DownloadMgr. They are aligned with ITU-T Rec. X.780 as derivations of Managed Object Interface in this Recommendation. +- **Domain Objects:** define the management information for management of BPON network resources. Domain objects are primarily resources (managed entities) identified by ITU-T Recs Q.834.1 and Q.834.2. These domain objects, as well as others defined in ITU-T Rec. M.3120 and other Recommendations following the CORBA Framework of ITU-T, may be made available for use on IF1. A mechanism for harmonizing the use of Service Objects and Domain Objects is explained later on in this clause. + +- Internal Objects: used to support Supplier Management System internal logic. They are completely obscure from the point of view of the OMS. + +## 7.1 Service objects and OMG naming service + +All Service objects (either instantiated by the Supplier Management System or the OMS) have their IDL interface defined in this Recommendation and their object reference registered with the OMG Naming Service pictured in Figure 1 using the bind() operation of Naming Service interface. Subsequently, the location of the object instance can be found using the resolve() operation of Naming Service, if required. + +Object names can be either "well known" (meaning that the name has been documented and agreed to prior to runtime), or communicated at run-time through another interface. In the case of this Recommendation, all of the Service objects are "well-known". The name of a well-known object can be documented via a naming graph. Figure 2 provides an example of a naming graph for some of the Service Objects in this Recommendation, following the naming convention described in ITU-T Rec. Q.816. Shown in the diagram is the Id, followed by a dot, followed by the Kind value. Only four of the Service Objects are shown, for the sake of simplicity, in the figure. The other Service Objects would be named in an analogous fashion. + +![A naming graph diagram showing a hierarchy of service objects. The root node points to BPON.Technology and ProfileRetriever.ServiceObject. BPON.Technology points to supplier1.Supplier and supplier2.Supplier. supplier1.Supplier points to ems1.SuppMS and ems2.SuppMS. ems1.SuppMS points to NERegistrar.ServiceObject. ems2.SuppMS points to Builder.ServiceObject and ServiceProvisioner ServiceObject. Each of these three points to an Object. node.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +graph TD + root((root)) --> BPON.Technology((BPON.Technology)) + root --> ProfileRetriever.ServiceObject((ProfileRetriever.ServiceObject)) + BPON.Technology --> supplier1.Supplier((supplier1.Supplier)) + BPON.Technology --> supplier2.Supplier((supplier2.Supplier)) + supplier1.Supplier --> ems1.SuppMS((ems1.SuppMS)) + supplier1.Supplier --> ems2.SuppMS((ems2.SuppMS)) + ems1.SuppMS --> NERegistrar.ServiceObject((NERegistrar.ServiceObject)) + ems2.SuppMS --> Builder.ServiceObject((Builder.ServiceObject)) + ems2.SuppMS --> ServiceProvisioner.ServiceObject((ServiceProvisioner ServiceObject)) + NERegistrar.ServiceObject --> Object1((Object.)) + Builder.ServiceObject --> Object2((Object.)) + ServiceProvisioner.ServiceObject --> Object3((Object.)) + ProfileRetriever.ServiceObject --> Object4((Object.)) + +``` + +A naming graph diagram showing a hierarchy of service objects. The root node points to BPON.Technology and ProfileRetriever.ServiceObject. BPON.Technology points to supplier1.Supplier and supplier2.Supplier. supplier1.Supplier points to ems1.SuppMS and ems2.SuppMS. ems1.SuppMS points to NERegistrar.ServiceObject. ems2.SuppMS points to Builder.ServiceObject and ServiceProvisioner ServiceObject. Each of these three points to an Object. node. + +Q.834.3\_F02 + +**Figure 2/Q.834.4 – Naming graph** + +The complete path for the name is required for a "well known" object. At start-up of a newly installed Supplier Management System, all instances of Service objects are automatically registered to a single OMG Naming Service maintained by the Operator. The Name of any object registered with OMG Naming Service has the following syntax: + +``` + +typedef string Istring; + +struct NameComponent { + Istring id; + Istring kind; +}; + +typedef sequence Name; + +``` + +One interpretation of the naming graph of Figure 2 is that the "kind" field in each of the naming components of the service objects has the value of null string, and that each of the nodes shown + +represents the values for the "id" field. The details of the naming graph, as well as its interpretation, should be determined via agreement between the supplier and operator and these details lie outside the scope of this Recommendation. + +## 7.2 Domain objects + +The Supplier Management System maintains a large number of Managed Entities (or Domain Objects)2. These entities are managed indirectly through the management services offered by the Supplier Management System. However, references (identifiers) to specific resources instances are often needed for the OMS to make effective use of the management services of the Supplier Management System. When the identifier is returned as result of a management operation (or included in notifications) it is assumed that the identifier is "known" in subsequent management service invocations from the OMS. In this specification, the identifier of a Managed Entity has been provided a syntax that allows the Supplier Management System to inform the OMS of at least one of three ways to interact with the Managed Entity in subsequent invocations. If the Managed Entity is a Managed Object available on IF1, then the CORBA name of the object is provided as described in ITU-T Rec. X.780. If the Managed Entity has a supporting Façade object available on IF1, then the CORBA name of the façade object is provided as described in ITU-T Rec. X.780.1. If neither of these capabilities is available yet, then the identifier consists of a reference unique within the context of the management domain of the Supplier Management System. In general, details of this reference are based on a specific containment hierarchy determined via agreement between the supplier and operator and the details lie outside the scope of this Recommendation. + +# 8 Organization of IDL files + +The proposed interface specification found in this Recommendation consists of a parent module called "q834\_4". The parent module is partitioned into IDL files (smaller modules) corresponding to smaller named modules. Each of these files contains one or more interface definitions representing a specific management service supported on IF1. Table 1 provides a listing correlating Annex C Reference number, IDL File Name, contained IDL Interfaces, and reference to the associated Use Case Description of ITU-T Rec. Q.834.3. + +**Table 1/Q.834.4 – q834\_4 module organization** + +| Annex reference | IDL files | IDL interface | Use case title | +|------------------------|--------------------|----------------------------------------------------------------------------------------------|-----------------------| +| C.1 | Q834AccessControl | AccessControlMgr | AccessControl | +| C.2 | Q834Build | Builder | Build BPON Resources | +| C.3 | Q834Common | ProbableCause
MonitoringParameter
RecordSetType
PMCategory
PhysicalLayerLoopback | | +| C.4 | Q834ControlArchive | RecordSetMgr | Control Archiving | + +2 If the Supplier Management System manages 100-200 BPON systems (desirable sizing requirement) and fully supports the shared management knowledge base contained in ITU-T Recs Q.843.1 and Q.834.2, then the number of managed entity instances supported by the Supplier Management System varies between 10s of millions to billions depending on the service offerings. + +**Table 1/Q.834.4 – q834\_4 module organization** + +| Annex reference | IDL files | IDL interface | Use case title | +|------------------------|-------------------------|-----------------------------------------------------------------------|----------------------------------------------------| +| C.5 | Q834SoftwareDownload | DownloadMgr | Distribute Software | +| | | VersionRepository | NE Software Version Control | +| C.6 | Q834EventPublisher | AlarmEventSupplier
SecurityEventSupplier
DiscoveryEventSupplier | Publish Events | +| C.7 | Q834MIBTransfer | MIBMover | NE Restoral | +| C.8 | Q834PerformanceManager | ImpairmentPersistence | RCAA & RCIA | +| | | ReportController | Performance & Traffic Monitoring Reporting Control | +| C.9 | Q834ProfileManager | ProfileConsumer
ProfileUsageMgr
ProfileRetriever | Profile Object Management | +| C.10 | Q834Registrar | NERegistrar | Provision Installed BPON Resources | +| C.11 | Q834ResourceAllocation | ResourceAllocator | Reserve Resources | +| C.12 | Q834SchedulerManagement | SchedulerMgr | Scheduler | +| C.13 | Q834ServiceProvisioning | ServiceProvisioner | Provision Service | +| C.14 | Q834Synchroniser | Synchroniser | Provide Current Event Summary Listings | +| | | | NE Synchronisation | +| C.15 | Q834Test | TestActionPerformer | Testing | +| C.16 | Q834FileTransfer | TransferMgr | Bulk Transfer | + +# **9 Modules** + +## **9.1 AccessControl module** + +This module describes functionality for creating, deleting, assigning, and using access control information for operators using the GUI client application of the Supplier Management System. In this module, users can be assigned to user groups. Permission can be granted to individual users or to user groups. The user possesses the permission of any group to which he or she has been assigned. Any individually defined permission (see 9.1.1.14 and 9.1.1.15) for a specific user takes precedence over a group assignment. With group assignments the highest level of permission prevails for any user assigned to the groups. It is assumed that the privileged user does not request any ambiguous target activities when creating or modifying a user group, or when specifying the permission for an individual user. + +A target activity is defined as shown in Table 2, throughout the module: + +**Table 2/Q.834.4 – Target activity detail** + +| Field name | Definition | Syntax | Comments | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|-------------------------------------------------------------------| +| activityLevel | Specifies the access level of the activity | enum | monitorOnly
allowedToExecute
noAccess | +| activityType | Specifies the type of the activity | short | Defined as various constants in the interface
AccessControlMgr | +| administrationDomainList | The identifier provided by the OMS or operator during registration to indicate the administration domain to which the NE belongs | UserLabel | | + +### 9.1.1 AccessControlMgr interface + +#### 9.1.1.1 setPasswordPolicy + +This operation allows the privileged users to manage the password policy. + +The operation signature for **setPasswordPolicy** is shown below: + +``` +void setPasswordPolicy (in PasswordPolicyType passwordPolicy) + raises (AccessDenied); +``` + +The input parameter **passwordPolicy** identifies the password policy which is enforced by the Supplier Management System and it consists of UserLoginPolicy and SessionPolicy. UserLoginPolicy dictates the following parameters regarding userId and password: minimum size for user Id, minimum size for user password, length of time in days before a password can be reused, maximum number of login attempts allowed before the user access is blocked for a day, how long the password is valid (in days), whether the password must contain an alphanumeric mixture, whether or not at least one special character is required, whether or not the password can contain repeating characters, and whether or not the user Id can be part of the password. + +SessionPolicy identifies the following parameters regarding the session: length of time that a session is inactive before the session is discontinued, length of time an inactive user Id is disabled, and the maximum number of active sessions per user Id is permitted. + +Since only one passwordPolicy can exist in a Supplier Management System, there is no need to have a create method, either a default policy exists in the Supplier Management System or the first set method can act as set-by-create. + +The return value is of type **void**. + +#### 9.1.1.2 passwordPolicyGet + +This operation allows the privileged users to retrieve the policy concerning the syntax of data exchanged and timers used when logging into the Supplier Management System. + +The operation signature for **passwordPolicyGet** is shown below: + +``` +PasswordPolicyType passwordPolicyGet () + raises (AccessDenied); +``` + +There is no input parameter required by this operation. + +The return value is of type **PasswordPolicyType** providing the details governing user log on to the Supplier Management System. + +#### 9.1.1.3 userListGet + +This operation allows the privileged users to retrieve the list of user ids having some form of access to the Supplier Management System as well as their target activities and group memberships. + +The operation signature for **userListGet** is shown below: + +``` +UserSeqType userListGet () + raises (AccessDenied); +``` + +There is no input parameter required by this operation. + +The return value is of type **UserSeqType** providing the list of user ids having some form of access to the Supplier Management System as well as their target activities and group memberships. + +#### 9.1.1.4 userGroupListGet + +This operation allows the privileged users to retrieve the user groups having access to the Supplier Management System with the members of the group and target activities identified. + +The operation signature for **userGroupListGet** is shown below: + +``` +UserGroupSeqType userGroupListGet () + raises (AccessDenied); +``` + +There is no input parameter required by this operation. + +The return value is of type **UserGroupSeqType** providing the user groups having access to the Supplier Management System with the members of the group and target activities identified. + +#### 9.1.1.5 userGet + +This operation allows the privileged users to retrieve the user's group membership and target activities. + +The operation signature for **userGet** is shown below: + +``` +UserType userGet ( + in UserIdType userId ) + raises (AccessDenied, UnknownUserIds); +``` + +The input parameter **userId** identifies the user of interest. + +The return value is of type **UserType** provides the user's group membership and target activities. + +#### 9.1.1.6 userGroupGet + +This operation allows the privileged users to retrieve the member users of the group and their allowed target activities. + +The operation signature for **userGroupGet** is shown below: + +``` +UserGroupType userGroupGet ( + in UserLabelType userGroupId) + raises (AccessDenied, UnknownUserGroupId); +``` + +The input parameter **userGroupId** identifies the user group. + +The return value is of type **UserGroupType** provides the identifier for the user group, the member users of the group, and the allowed target activities. + +#### 9.1.1.7 createUserGroup + +This operation allows the privileged users to create a new user group. User group is used to give certain users certain accesses to certain network elements. The privileged user creates the new group providing the list of the activities allowed to the user group. + +The operation signature for **createUserGroup** is shown below: + +``` +void createUserGroup ( + in UserLabelType userGroupId, + in TargetActivitySeqType targetAdditions) + raises (DuplicateUserGroupId, UnknownTargets, AccessDenied); +``` + +The input parameter **userGroupId** identifies the group to be created. UserGroupId is not allowed to have the empty string value. The input parameter **targetAdditions** identifies the TargetActivities allowed to the users belonging to this group. + +The return value is of type **void**. + +#### 9.1.1.8 modifyUserGroup + +This operation allows the privileged users to add/delete the target activities of a user group. The privileged user specifies the user group and the list of the target activities to be added or deleted. The Supplier Management System processes the deletions before the additions. This allows for example the raising of the permission level of a given activity. + +The operation signature for **modifyUserGroup** is shown below: + +``` +TargetActivitySeqType modifyUserGroup ( + in UserLabelType userGroupId, + in TargetActivitySeqType targetAdditions, + in TargetActivitySeqType targetDeletions) + raises (UnknownUserGroupId, UnknownTargets, + AccessDenied); +``` + +The input parameter **userGroupId** identifies the user group to/from which an operator wants to add/delete target activities. The input parameter **targetAdditions** identifies the TargetActivities which need to be added to the group. The input parameter **targetDeletions** identifies the TargetActivities which need to be deleted from the group. + +The return value is of type **TargetActivitySeqType** that provides the updated list of TargetActivities which are allowed to the users belonging to this user group. + +#### 9.1.1.9 deleteUserGroup + +This operation allows the privileged users to delete an existing user group. The deletion can be completed only if the user group is empty. + +The operation signature for **deleteUserGroup** is shown below: + +``` +void deleteUserGroup ( + in UserLabelType userGroupId) + raises (AccessDenied, UserGroupNotEmpty, UnknownUserGroupId); +``` + +The input parameter **userGroupId** identifies the group to be deleted. + +The return value is of type **void**. + +#### 9.1.1.10 addUsersToGroup + +This operation allows the privileged user to add new users to an existing user group. + +The operation signature for **addUsersToGroup** is shown below: + +``` +void addUsersToGroup ( + in UserLabelType userGroupId, + in UserIdSeqType userIdList) + raises (AccessDenied, UnknownUserGroupId); +``` + +The input parameter **userGroupId** identifies the group to which new users need to be added. The input parameter **userIdList** identifies a set of userIds which need to be added to the existing user group. + +The return value is of type **void**. + +#### 9.1.1.11 deleteUsersFromGroup + +This operation allows the privileged users to delete users from a user group. + +The operation signature for **deleteUsersFromGroup** is shown below: + +``` +void deleteUsersFromGroup ( + in UserLabelType userGroupId, + in UserIdSeqType userIdList) + raises (AccessDenied, UnknownUserGroupId, UnknownUserIds ); +``` + +The input parameter **userGroupId** identifies the group from which users need to be deleted. The input parameter **userIdList** identifies a set of userIds to be deleted from the user group. + +The return value is of type **void**. + +#### 9.1.1.12 getPermissionList + +This operation allows the privileged users to obtain the list of the activities allowed to a specified user. + +The operation signature for **getPermissionList** is shown below: + +``` +TargetActivitySeqType getPermissionList ( + in UserIdType userId) + raises (UnknownUserIds, AccessDenied); +``` + +The input parameter **userId** identifies the user whose allowed TargetActivities the privileged user wants to obtain. + +The return value is of type **TargetActivitySeqType** that provides the list of the TargetActivities which are allowed to a specified user. + +#### 9.1.1.13 modifyPermissionList + +This operation allows the privileged users to modify the list of the activities allowed to a user. The privileged user specifies the userId and the list of the activities which need to be added or deleted. The Supplier Management System processes the deletions before the additions. This allows, for example, the raising of the permission level of a given activity. + +The operation signature for **modifyPermissionList** is shown below: + +``` +TargetActivitySeqType modifyPermissionList ( + in UserIdType userId, + in TargetActivitySeqType targetAdditions, + in TargetActivitySeqType targetDeletions) + raises (UnknownUserIds, UnknownTargets, AccessDenied); +``` + +The input parameter **userId** identifies the user whose allowed activities the privileged user wants to modify. The input parameter **targetAdditions** identifies the allowed activities which need to be added to a specified user. The input parameter **targetDeletions** identifies the allowed activities which need to be deleted from a specified user. + +If a user belongs to multiple groups that have the same activity, then the user assumes the access level that is the highest. When both the user and the group the user belongs to are added to the same administration domain, then the users activityLevel takes precedence over the group's activityLevel. + +The return value of type **TargetActivitySeqType** provides the list of the activities which are allowed to a specified user after the modification. + +#### 9.1.1.14 **createUser** + +This operation allows the privileged users to create a new user. The privileged user provides a new **userId**, its password, and the list of the activities allowed to the user. + +The operation signature for **createUser** is shown below: + +``` +void createUser ( + in UserIdType userId, + in PasswordType password, + in TargetActivitySeqType targetAdditions) + raises (DuplicateUserId, UnknownTargets, AccessDenied, + UserLoginPolicyViolation); +``` + +The input parameter **userId** identifies the identification information to be associated to the new user. The input parameter **password** identifies the password to be associated with the new user Id. The input parameter **targetAdditions** identifies the TargetActivities allowed to the new user. + +The return value is of type **void**. + +#### 9.1.1.15 **deleteUser** + +This operation allows the privileged users to delete an existing user. + +The operation signature for **deleteUser** is shown below: + +``` +void deleteUser ( + in UserIdType userId) + raises (UnknownUserIds, AccessDenied); +``` + +The input parameter **userId** identifies the user to be deleted. + +The return value is of type **void**. + +#### 9.1.1.16 **resetPassword** + +This operation allows the privileged users to reset the password for a user. This operation takes place when the old password is not available and the privileged user needs to set the new password for the user. On first use, the Supplier Management System will prompt the user to change their password. + +The operation signature for **resetPassword** is shown below: + +``` +void resetPassword ( + in UserIdType userId, + in PasswordType newPassword) + raises (UnknownUserIds, UserLoginPolicyViolation, AccessDenied); +``` + +The input parameter **userId** identifies the user which needs to be deleted. The input parameter **newPassword** specifies the password which needs to be associated with the userId. + +The return value is of type **void**. + +#### 9.1.1.17 **Exceptions** + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **DuplicateUserId** is raised when the userId specified for the new creation of a user already exists in the Supplier Management System's database. + +The exception **DuplicateUserGroupId** is raised when the userGroupId specified for the new creation of a user group already exists in the Supplier Management System. In other words, the + +Supplier Management System polices the assignment of User Label for user group identifiers for all users recognized by it. + +The exception **UnknownTargets** is raised when the specified list of the TargetActivities cannot be identified. + +The exception **UnknownUserGroupId** is raised when the specified UserGroupId cannot be identified. + +The exception **UnknownUserIds** is raised when any userId is unrecognized. + +The exception **UserGroupNotEmpty** is raised when there is an attempt to delete a user group but the user group is not empty (i.e., there are registered users in the group). + +The exception **UserLoginPolicyViolation** is raised when the password specified for a new user or for the password change is violating the UserLoginPolicy. + +## 9.2 Build module + +The Supplier Management System builds management model groupings for planned equipment on request of an OMS or Operator as part of preprovisioning activities. These resources include nodes (OLT, ONT, ONU, NT) and plug-in units. If equipment is installed, modify operations are used to complete the provisioning of the installed resources. Protection groupings are established for either preprovisioned or installed resources. + +### 9.2.1 Builder interface + +#### 9.2.1.1 buildNode + +This operation builds a NE in the Supplier Management System. A set of managed entities is automatically created in the management information model maintained by the Supplier Management System as a result of this operation. Depending on the equipment implementation of the supplier, instances of equipmentHolderF for shelves and slots, instances of NEFSAN, and instances of physicalPathTPF for integrated ports, are examples of what can be automatically created. + +If the NE is an ONT or ONU, this activity automatically removes the bandwidth necessary to support the embedded operations channel between the OLT and ONT or ONU from the available system bandwidth. + +The operation signature for **buildNode** is shown below: + +``` +ManagedEntityIdType buildNode ( + in NEKindType nEKind, + in string supplierName, + in string location, + in VersionType version, + in SerialNumType serialNum, + in NameSeqType alarmSeverityProfiles, + in NameSeqType thresholdDataProfiles, + in SlotAssignmentSeqType slotAssignmentList, + in ManagedEntityIdType port, + in string modelCode, + in string systemTitle, + in VersionSeqType softwareVersions, + in UserLabelType nEUserLabel, + in ExternalTimeType externalTime, + in SystemTimingType systemTiming, + in AdministrationDomainType administrationDomain) + raises (UnrecognisedVersion, InvalidSerialNumSyntax, + DuplicateSerialNumber, UnknownProfiles, + UnknownManagedEntity, DuplicateUserLabel, AccessDenied, +``` + +``` +InvalidExternalTime, UnknownSystemTimingSource, +ProfileSuspended); +``` + +The input parameter **nEKind** identifies the type of NE to be built. Possible choices of NE type are: OLT, ONT, ONU, or NT. The inputs **supplierName** and **version** identify the NE vendor and the hardware version of the NE to be built. The input parameter **location** designates the physical location of the planned NE. The input **serialNum** provides a unique string corresponding to the NE. The input **alarmSeverityProfiles** identifies profiles to configure alarm severity for individual alarms to be reported by the NE. The input **thresholdDataProfiles** identifies profiles to be used when configuring threshold values to generate TCAs from the NE. The input **slotAssignmentList** identifies acceptable plug-in unit assignments for the slots of the NE. If a slot number is not mentioned in the list, then the assumption is made that no assignment has been made for it and, therefore, there are no restrictions on the type of card that can be placed in the slot. The same is true if the value of the plugIn is the empty string. The input **port** identifies the PON port of the OLT if the NE under construction is either an ONT or ONU. The input **port** identifies the port of the ONU serving the NT if an NT is under construction. In case of building an OLT, the value for **port** is null. The input **modelCode** provides a unique string identifying the type of network resource. This input parameter is primarily of interest when pre-provisioning an ONT or NT. The input **systemTitle** identifies an operator-defined label to be applied to the node. The input **softwareVersions** identifies the versions of software to be used by the node. The input **nEUserLabel** provides a unique operator designation for the constructed NE. The input **externalTime** sets current time expressed in generalized time for the NE. The input **systemTiming** identifies the input clock source of the NE that will be used for timing synchronisation. Whenever unspecified is passed for the "enum" data type **systemTiming** from the OMS, the NE shall use its default timing source. The input **administrationDomain** identifies the domain to which the NE belongs. + +The return value of type **ManagedEntityIdType** provides an identifier for the new NE created by the operation. + +#### 9.2.1.2 assignUserLabelsToNE + +This operation assigns operator administrative designations to NEs. This operation is required when the OMS first learns of the NE through autodiscovery. + +The operation signature for **assignUserLabelsToNE** is shown below: + +``` +void assignUserLabelsToNE ( + in SerialNumType serialNum, + in UserLabelType nEUserLabel, + in AdministrationDomainType administrationDomain) + raises (InvalidSerialNumSyntax, DuplicateSerialNumber, + DuplicateUserLabel, AccessDenied); +``` + +The input **serialNum** identifies specific NE. The input **nEUserLabel** provides an operator assigned name for the NE. The input **administrationDomain** identifies the domain to which the NE is assigned. + +The return value is of type **void**. + +#### 9.2.1.3 modifyNode + +The operation initiates reconfiguration and update of specific parameters associated with a NE. + +The operation signature for **modifyNode** is shown below: + +``` +void modifyNode ( + in ManagedEntityIdType managedEntityId, + in SlotAssignmentSeqType newSlotAssignmentList, + in NameSeqType newAlarmSeverityProfiles, + in NameSeqType newThresholdDataProfiles, + in ManagedEntityIdType port, + in string newModelCode, + in UserLabelType newNEUserLabel, + in ExternalTimeType externalTime, + in AdministrationDomainType administrationDomain) + raises(UnknownManagedEntity, UnknownNE, InvalidSlotAssignmentList, + UnknownProfiles, DuplicateUserLabel, AccessDenied, + InvalidExternalTime, ProfileSuspended ); +``` + +The input **managedEntityId** identifies the target NE to be modified. The **newSlotAssignmentList** identifies a new assignment of acceptable plug in units for the slots of the NE. If a slot number is not mentioned in the list, then the assumption is made that there is no change for the assignment of that slot. If the value of the plugIn is the empty string then there are no restrictions on the type of card that can be placed in the slot and if a plug-in unit is subsequently removed from the slot no removal alarms are raised. The input **alarmSeverityProfiles** identifies profiles to configure alarm severity for individual alarms to be reported by the NE. The input **thresholdDataProfiles** identifies profiles to be used when configuring threshold values to generate TCAs from the NE. The input **port** identifies PON port on the OLT if there is a change in the relationship between the planned ONT or ONU and the OLT port. The input **port** identifies the ONU port if there is a change in the relationship between the planned NT and ONU port. The input **newModelCode** provides a unique string identifying the type of network resource. This input parameter is primarily of interest when modified node is an ONT or NT. The input **newNEUserLabel** provides a new User Label to be applied to the NE. The input **externalTime** gives a new current reference time for the NE. The input **administrationDomain** identifies the domain to which the NE is reassigned + +The return value is of type **void**. + +#### 9.2.1.4 deleteNode + +This operation deletes the NE from the Supplier Management System and cancels a previous preprovisioning request. As a consequence of this operation, all managed entities automatically created as a result of the corresponding buildNode operation are deleted as well. It will raise **RemainingContainedManagedEntities** exception if there are any other contained managed entities still present such as service connections. Any bandwidth reservations associated with this node are also deleted. + +The operation signature for **deleteNode** is shown below: + +``` +void deleteNode ( + in ManagedEntityIdType managedEntityId) + raises (UnknownNE, RemainingContainedManagedEntities, AccessDenied, + RemainingReservations, RemainingSubnetworkConnections); +``` + +The input **managedEntityId** identifies the NE to be deleted by this operation. + +The return value is of type **void**. + +#### 9.2.1.5 modifyPort + +The operation modifies parameters of the designated port identified by **physicalPathTPId**. + +The operation signature for **modifyPort** is shown below: + +``` +void modifyPort ( + in ManagedEntityIdType physicalPathTPIId, + in NameSeqType newAlarmSeverityProfiles, + in NameSeqType newThresholdDataProfiles, + in NameSeqType newPortProfiles, + in string newFrameFormat, + in AdministrativeStateType administrativeState, + in OpticalWaveLengthArraySeqType newOpticalWavelengthArray, + in LoopbackLocationIdSeqType newLoopbackLocationIds, + in unsigned long newInterfaceSpeed, + in unsigned long aRCTimer) + raises (UnknownManagedEntity, UnknownProfiles, AccessDenied, + InterfaceSpeedNotChangeable, ProfileSuspended ); +``` + +The input **physicalPathTPIId** identifies the port to be modified. The input **alarmSeverityProfiles** identifies profiles to configure alarm severity for individual alarms to be reported by the NE. The input **thresholdDataProfiles** identifies profiles to be used when configuring threshold values to generate TCAs from the NE. The input parameter **newPortProfiles** identifies profiles used to finish the provisioning of the port. Examples of such profiles include but are not limited to the following: ATMNetworkAccessProfile, UNIInfo, EthernetProfile, CESServiceProfile, MACBridgeServiceProfile, LESServiceProfile, AAL1Profile, and AAL5Profile. The input **newFrameFormat** identifies a new frame format that will be terminated and generated over the physical port provided the frame format is configurable. The input **administrativeState** specifies the modified setting for this parameter. The input **newLoopbackLocationIds** identifies new location identifiers for loopback associated with the physical port. The input **newInterfaceSpeed** identifies a new interface speed of the physical port provided this is configurable. The input parameter **aRCTimer** provides the non-negative time (in seconds) for which the network resource initially detects a valid signal before raising any communication alarms on the port. + +The return value is of type **void**. + +#### 9.2.1.6 buildPlugInUnit + +This operation builds a plug-in unit in the Supplier Management System as part of the preprovisioning activities. A set of managed entities are automatically created in the management information model maintained by the Supplier Management System as a result of this operation. Depending on the type of plug-in unit, various termination points are automatically created. The slot assignment of the containing node is automatically updated to include the change requested by this operation. + +The operation signature for **buildPlugInUnit** is shown below: + +``` +ManagedEntityIdType buildPlugInUnit ( + in ManagedEntityIdType nEId, + in NameType alarmSeverityProfile, + in UserLabelType plugInUnitUserLabel, + in string modelCode, + in AdministrativeStateType administrativeState, + in ManagedEntityIdType equipmentHolder) + raises (UnknownNE, DuplicateUserLabel, + AccessDenied, UnknownManagedEntity, + InvalidEquipmentCode, SlotAlreadyAssigned, UnknownSlot, + InvalidSlotAssignmentList, UnknownProfiles, + ProfileSuspended ); +``` + +The input **nEId** provides a unique name for the NE that contains the plug-in unit to be built. The input **plugInUnitUserLabel** gives an identifier for the plug-in unit to be built. The input **alarmSeverityProfile** identifies the profile to configure alarm severity assignments for equipment + +failures relating to the plug-in unit. The input **modelCode** identifies the type of the plug-in unit. The input **administrativeState** specifies the initial setting for this parameter. The input **equipmentHolder** identifies the location of the slot where the built plug-in unit will occupy. + +The return value of type **ManagedEntityIdType** provides a unique identifier for the constructed circuit pack. + +#### 9.2.1.7 modifyPlugInUnit + +The operation modifies attributes of the plug-in unit in the Supplier Management System. + +The operation signature for **modifyPlugInUnit** is shown below: + +``` +ManagedEntityIdType modifyPlugInUnit ( + in ManagedEntityIdType plugInUnitId, + in NameType alarmSeverityProfile newAlarmSeverityProfile, + in string newModelCode, + in ManagedEntityIdType newEquipmentHolder, + in UserLabelType newPlugInUnitUserLabel, + in AdministrativeStateType newAdministrativeState) + raises (UnknownManagedEntity, UnknownProfiles, AccessDenied, + InvalidEquipmentCode, SlotAlreadyAssigned, UnknownSlot, + InvalidSlotAssignmentList, InvalidUserLabelSyntax, + ProfileSuspended); +``` + +The input **plugInUnitId** identifies the managed entity to be modified by this operation. The input **newAlarmSeverityProfile** changes the profile to configure alarm severity assignments for equipment failures relating to the plug-in unit. The input **newModelCode** changes the type of the plug-in unit. The input **newEquipmentHolder** changes the slot assignment for the plug-in unit. The input **newPlugInUserLabel** gives a new User Label for the plug-in unit. The input **newAdministrativeState** specifies the modified setting for this parameter. + +The return value of type **ManagedEntityIdType** provides a unique identifier for the modified circuit pack. + +#### 9.2.1.8 deletePlugInUnit + +This operation deletes a plug-in unit from the Supplier Management System. As a consequence of this operation, all managed entities automatically created as a result of the corresponding **buildPlugInUnit** operation are deleted as well. It will raise **RemainingSubnetworkConnections** exception if there are any connections still present. It is employed to remove preprovisioning information that is no longer desired by the operator. + +The operation signature for **deletePlugInUnit** is shown below: + +``` +void deletePlugInUnit ( + in ManagedEntityIdType plugInUnitId) + raises (UnknownManagedEntity, RemainingSubnetworkConnections, + AccessDenied, RemainingReservations); +``` + +The input **plugInUnitId** identifies the plug-in unit to be deleted. + +The return value is of type **void**. + +#### 9.2.1.9 buildProtectionGrouping + +This operation builds a protectionGrouping in the Supplier Management System. No port can belong to more than one protection grouping and must be provisioned prior to this operation. Outside the scope of IF1, the supplier and operator have come to a mutual understanding of the valid protection arrangements supported by the supplier equipment. If a protected port is listed in the **protectionUnitList**, there must also be at least one protecting port. All ports must have the same physical path characteristics. + +The operation signature for **buildProtectionGrouping** is shown below: + +``` +ManagedEntityIdType buildProtectionGrouping ( + in ProtectionParameterType protectionParameters, + in ProtectionUnitSeqType protectionUnitList) + raises (InvalidProtectionScheme, AccessDenied ); +``` + +The input **protectionParameters** provides the characteristics for the protection scheme. The input **protectionUnitList** identifies the protecting and protected ports on the network resource. + +The return value of type **ManagedEntityIdType** provides a unique identifier for the constructed relationship between protected and protecting ports. + +#### 9.2.1.10 modifyProtectionParameters + +This operation modifies the protection schema for the identified protection grouping. If either m (= number of protecting ports) or n (= number of protected ports) is decreased, it will be necessary for the OMS to consider invoking modifyProtectionUnitList to avoid an invalid protection schema exception. If either m or n is increasing, it is not necessary to invoke modifyProtectionUnitList. + +The operation signature for **modifyProtectionParameters** is shown below: + +``` +void modifyProtectionParameters ( + in ManagedEntityIdType protectionGroupingId, + in ProtectionParameterType newProtectionParameters) + raises (UnknownManagedEntity, InvalidProtectionScheme, + AccessDenied); +``` + +The input **protectionGroupingId** identifies the managed entity to be modified by this operation. The input **newProtectionParameters** provides a replacement for the existing protection parameters. + +The return value is of type **void**. + +#### 9.2.1.11 modifyProtectionUnitList + +This operation either adds to or removes from the list of protected and protecting ports for the identified protection grouping. A removal of all protecting ports can only occur if all protected ports are also removed. An addition of protected or protecting ports cannot exceed the bounds of m or n specified within the data structure of protectionParameters associated with the protection grouping. No port can belong to more than one protection grouping and must be provisioned prior to this operation. All ports must have the same physical path characteristics. + +The operation signature for **modifyProtectionUnitList** is shown below: + +``` +void modifyProtectionUnitList ( + in ManagedEntityIdType protectionGroupingId, + in ProtectionUnitSeqType deltaProtectionUnitList, + in boolean addDeleteInd) + raises (UnknownManagedEntity, InvalidProtectionScheme, + AccessDenied); +``` + +The input **protectionGroupingId** identifies the managed entity to be modified by this operation. The input **deltaProtectionUnitList** provides the changes to the protected and protecting ports. The input parameter **addDeleteInd** shows whether or not the change is an addition or removal. + +The return value is of type **void**. + +#### 9.2.1.12 deleteProtectionGrouping + +This operation deletes a protection grouping of ports from the Supplier Management System. As a consequence of this operation, all managed entities automatically created as a result of the corresponding buildProtectionGrouping operation are deleted as well. + +The operation signature for **deleteProtectionGrouping** is shown below: + +``` +void deleteProtectionGrouping ( + in ManagedEntityIdType protectionGroupingId) + raises (UnknownManagedEntity, AccessDenied); +``` + +The input **protectionGroupingId** identifies the protection grouping to be deleted. + +The return value is of type **void**. + +#### 9.2.1.13 buildBridge + +This operation builds a MAC Bridge in the Supplier Management System. All ports must be provisioned prior to this operation. All UNI ports must be LAN ports. This operation is not required if all UNI LAN ports on a network element automatically belong to the same bridge and the default settings for the bridge parameters is desired by the operator. + +The operation signature for **buildBridge** is shown below: + +``` +ManagedEntityIdType buildBridge ( + in NameType mACBridgeProfile, + in ManagedEntityIdType uplinkPort, + in ManagedEntityIdSeqType uNIPortList) + raises (UnknownProfiles, AccessDenied, + UnknownManagedEntity, ProfileSuspended); +``` + +The input **mACBridgeProfile** provides the characteristics for the bridge conforming to ANSI/IEEE 802.1D. The input **uplinkPort** identifies the OLT physical port interfacing with the IP layer backbone network. This parameter has the value empty string when there is no such interfacing on the OLT. The input **uNIPortList** identifies the UNI physical ports associated with the bridge. + +The return value of type **ManagedEntityIdType** provides a unique identifier for the constructed bridge. + +#### 9.2.1.14 modifyBridgeProfile + +This operation modifies the characteristics of the bridging function by changing the MAC Bridge Service Profile associated with the bridge. + +The operation signature for **modifyBridgeProfile** is shown below: + +``` +void modifyBridgeProfile ( + in ManagedEntityIdType bridgeId, + in NameType newMACBridgeProfile) + raises (UnknownManagedEntity, UnknownProfiles, AccessDenied, + ProfileSuspended); +``` + +The input **bridgeId** identifies the managed entity to be modified by this operation. The input **newMACBridgeProfile** provides a replacement for the existing bridge profile. + +The return value is of type **void**. + +#### 9.2.1.15 modifyBridgePortList + +This operation either adds to or removes from the list of UNI ports belonging to the bridge grouping. A removal of all UNI ports can occur. A UNI port cannot be removed if there exists an active service connection associated with it. If every UNI LAN port must belong to the same bridge, then this operation is not needed. + +The operation signature for **modifyBridgePortList** is shown below: + +``` +void modifyBridgePortList ( + in ManagedEntityIdType bridgeId, + in ManagedEntityIdSeqType deltaUNIPortList, + in boolean addDeleteInd) + raises (UnknownManagedEntity, RemainingSubnetworkConnections, + AccessDenied); +``` + +The input **bridgeId** identifies the managed entity to be modified by this operation. The input **deltaUNIPortList** provides the changes to the UNI ports desired. The input parameter **addDeleteInd** shows whether or not the change is an addition or removal. + +The return value is of type **void**. + +#### 9.2.1.16 deleteBridge + +This operation deletes a bridge provisioning from the Supplier Management System. As a consequence of this operation, all managed entities automatically created as a result of the corresponding buildBridge operation are deleted as well. A bridge cannot be deleted if there are outstanding active subnetwork connections associated with it. + +The operation signature for **deleteBridge** is shown below: + +``` +void deleteBridge ( + in ManagedEntityIdType bridgeId) + raises (UnknownManagedEntity, AccessDenied, + RemainingSubnetworkConnections); +``` + +The input **bridgeId** identifies the bridge to be deleted. + +The return value is of type **void**. + +#### 9.2.1.17 buildVPNetworkCTP + +This operation builds a VP Network CTP in the Supplier Management System. The port containing this VP Network CTP must be provisioned prior to this construction. This operation is used to construct VP Network CTPs in order to support installation testing. Both build and delete operations are needed.3 + +The operation signature for **buildVPNetworkCTP** is shown below: + +``` +ManagedEntityIdType buildVPNetworkCTP ( + in ManagedEntityIdType port, + in short vPI, + in NameType trafficDescriptorProfileName, + in ATMOverbookingFactorType overbookingFactor, + in UserLabelType userLabel, + in SegmentEndpointIndType segmentEndpointInd) + raises (UnknownProfiles, AccessDenied, + UnknownManagedEntity, ParameterViolation, + ProfileSuspended); +``` + +The input **port** identifies the ATM interface on the network resource. The input **vPI** gives the value of the index. The input **trafficDescriptorProfileName** identifies the ATM traffic descriptor profile associated with the CTP. The parameter **overbookingFactor** gives the percentage overbooking factor that can be used in the call admission control algorithms for any PVC have the same VPI value for the ATM interface port. The input parameter **userLabel** provides an operator-provided name for the VPNetworkCTP. The input parameter **segmentEndpoint** identifies whether or not the CTP is a segment endpoint. + +--- + +3 Delete operation is provided in 9.2.1.18. + +The return value of type **ManagedEntityIdType** provides unique identifier for the constructed CTP. + +#### 9.2.1.18 deleteVPNetworkCTP + +This operation deletes a VP Network CTP provisioning from the Supplier Management System. As a consequence of this operation, all managed entities automatically created as a result of the corresponding buildVPNetworkCTP operation are deleted as well. + +The operation signature for **deleteVPNetworkCTP** is shown below: + +``` +void deleteVPNetworkCTP ( + in ManagedEntityIdType vPNetworkCTP) + raises (UnknownManagedEntity, AccessDenied); +``` + +The input **vPNetworkCTP** identifies the bridge to be deleted. + +The return value is of type **void**. + +#### 9.2.1.19 createdNodesGet + +This operation retrieves the list of network elements that have been constructed through invocation of this interface. + +The operation signature of **createdNodesGet** is provided below: + +``` +ManagedEntityIdSeqType createdNodesGet () raises (AccessDenied); +``` + +There is no input parameter. + +The return value is of type **ManagedEntityIdSeqType** which provides the list nodes that have been constructed through invocation of the Q834:Builder interface. + +#### 9.2.1.20 Exceptions + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **DuplicateSerialNumber** is raised if there exists other equipment of the same type with this serial number. + +The exception **DuplicateUserLabel** is raised if the User Label provided in the request has been used to label another NE or plug-in unit. In other words, the Supplier Management System is responsible for policing User Labels assigned for NEs and plug-in units within its management jurisdiction. + +The exception **InterfaceSpeedNotChangeable** is raised if the physical port cannot support the new interface speed or if the speed is not configurable. + +The exception **InvalidEquipmentCode** is raised if the equipment code does not conform to syntax agreed to by the operator and supplier. + +The exception **InvalidExternalTime** is raised if the External Time specified is not valid. + +The exception **InvalidProtectionScheme** is raised if the network resource does not support the protection parameters specified in context with the port listing or if the protection units are ports of dissimilar physical path characteristic. + +The exception **InvalidSerialNumSyntax** is raised if the syntax of the serial number provided violates the supplier syntax. + +The exception **InvalidSlotAssignmentList** will be raised if the designated equipmentHolder cannot accept the requested type of plug-in unit. + +The exception **InvalidUserLabelSyntax** is raised if the User Label provided violates business rules of syntax defined by the operator and implemented in the Supplier Management System. + +The exception **ParameterViolation** is raised when the VPI is out of range or a duplicate. + +The exception **ProfileSuspended** is raised when profile(s) named in the invocation has been suspended for use within the Supplier Management System by the OMS or operator. + +The exception **RemainingContainedManagedEntities** will be raised if there are any remaining managed entities contained by the managed entity to be deleted. + +The exception **RemainingReservations** will be raised if there are remaining resource reservations associated with the managed entity to be deleted. + +The exception **RemainingSubnetworkConnections** will be raised if the managed entity which is being deleted contains one or more valid Subnetwork Connections. + +The exception **SlotAlreadyAssigned** is raised if the requested slot is already provisioned. + +The exception **UnknownManagedEntity** is raised if the identified managed entity is unknown to the Supplier Management System. + +The exception **UnknownNE** is raised if the identified NE is unknown to the Supplier Management System. + +The exception **UnknownProfiles** is raised if the profile name provided is unknown to the Supplier Management System and cannot be retrieved from the Profile Object Repository. + +The exception **UnknownSlot** is raised if the requested slot is unknown to the NE. + +The exception **UnknownSystemTimingSource** is raised if the External time source is unknown to the Supplier Management System or NE. + +The exception **UnrecognizedVersion** is raised if the Equipment version provided does not match known values. + +## 9.3 Q834Common module + +This module contains the definitions of data types used by more than one of the other IDL modules in this Recommendation. It also provides three groupings of constants. Many of the data types mentioned in Q834Common are imported from ITU-T Rec. X.780. The most important aspect of this IDL file is the definition of ManagedEntityIdType. The definition is extracted from the IDL file and presented below for discussion purposes. + +``` +struct NamingComponentType { + string type; // managed entity type + string id; +}; + +typedef sequence RDNTType; +typedef sequence RDNSeqType; +typedef sequence NameSeqType; + +enum IdType { + none, + x780_fineGrained, + x780_coarseGrained +}; + +typedef RDNTType MEIdType; +``` + +``` + +struct ManagedEntityIdType { + IdType id; + MEIdType mEId; +}; + +``` + +ManagedEntityIdType is a return value for many of the operations throughout this Recommendation. Examining the definition of this data type (reading from bottom to top) shows that the Supplier Management System returns a value providing a reference either to a fine-grain Managed Object, a coarse-grain Façade, or a RDN identifier for a data structure within the Supplier Management System. In all three cases, the fundamental syntax for the mEId is a sequence of pairs of naming components which is the syntax employed by ITU-T Rec. X.780 for Managed Objects and the syntax employed by ITU-T Rec. X.780.1 for Façades. + +### 9.3.1 ProbableCauseConst Module and ProbableCause interface + +This module definition follows the pattern specified in ITU-T Rec. X.780 and uses the same syntax for the values of probable cause. It provides some technology-specific values in addition to the values defined in ITU-T Rec. X.780. + +### 9.3.2 MonitoringParameter interface + +This interface provides the names for monitored performance and traffic parameters to be used by interfaces AlarmEventSupplier, ImpairmentPersistence and ProfileConsumer. The MonitoringParameter values are expressed as a string of values and are part of filterable data in a structured event. + +### 9.3.3 RecordSetType interface + +This interface provides the data value(s) to be used for recordset data type value by interfaces ReportController and RecordSetMgr. The recordSet type values are expressed as unsigned short values. The Values 1-99 are reserved for HistoryDataType. + +### 9.3.4 PhysicalLayerLoopback interface + +This interface provides the data value(s) to be used for loopbackTestType data type value by the TestActionPerformer interface. The recordSet type values are expressed as unsigned short values. + +## 9.4 ControlArchive module + +The Supplier Management System provides the functionality to manage logs for specific groups of events including the clearing of the contents of the logs. The Privileged User can create, initialize, suspend, resume, and remove event logs. The Supplier Management System also provides the functionality to control the short-term archiving of performance monitoring and traffic monitoring reports, including the clearing of contents of these record sets. This function also includes the reporting of status for current logs or statistics record sets. The majority of short-term archives within the Supplier Management System are created automatically when the Supplier Management System is first instantiated. The names of these archives, identified by ManagedEntityIdType syntax, can be provided by the supplier to the operator or obtained by invocation of the operation recordSetListGet with creationModeType value "initialList" and iterative invocations of the operation getStatusAttributes for each record set identified in the first operation. + +### 9.4.1 RecordSetMgr interface + +#### 9.4.1.1 createLog + +CreateLog operation is used to create a RecordSet in the Supplier Management System for the purposes of archiving event information. + +The signature of **createLog** is as follows: + +``` +ManagedEntityIdType createLog ( + in UserLabelType recordSetUserLabel, + in AdministrativeStateType administrativeState, + in NameType filterName, + in FullActionType fullAction, + in MaxSizeType maxSize, + in SizeThresholdType sizeThreshold) + raises (RecordSetExists, DuplicateUserLabel, AccessDenied); +``` + +The input parameter **recordSetUserLabel** uniquely identifies the recordSet within the Supplier Management System. The input parameter **administrativeState** specifies if the new log is initialized for recording of event information. The input parameter **filterName** explains the entrance criteria determining what event notifications are recorded in the log to be created. If the **filterName** is unrecognized by the Supplier Management System, it looks up the IOR for the filterObject using **filterName** by consulting the directory of Naming Service. Using the IOR, the system is then able to retrieve the entrance criteria details from CosNotifyFilter interface available on Notification Service. The input parameter **fullAction** specifies the behaviour of the recordset when it reaches its maximum size. The input parameter **maxSize** specifies the maximum size of the recordSet. The input parameter **sizeThreshold** specifies the threshold on size of the RecordSet which triggers the Supplier Management System to generate an alarm/event. + +The return value is of type **ManagedEntityIdType** and provides the identifier for the log archive created with this operation. + +#### 9.4.1.2 createArchive + +CreateArchive operation is used to create a recordSet for storing history data. The archiving will halt automatically its recording when it hits the maximum size. + +The signature of **createArchive** is as follows: + +``` +ManagedEntityIdType createArchive ( + in UserLabelType recordSetUserLabel, + in AdministrativeStateType administrativeState, + in RecordKindType recordKind, + in MaxSizeType maxSize) + raises (RecordSetExists, DuplicateUserLabel, AccessDenied); +``` + +The input parameter **recordSetUserLabel** uniquely identifies the record Set within the Supplier Management System. The input parameter **administrativeState** specifies if the new archive is initialized for recording of appropriate records. The input parameter **recordKind** identifies the type of record to be stored in the record set. The input parameter **maxSize** specifies the maximum size of the recordSet. + +The return value is of type **ManagedEntityIdType** and provides the identifier for the archive created with this operation. + +#### 9.4.1.3 getStatusAttributes + +At any time the Operator or OMS can view the current status of a short-term archive. + +The signature of **getStatusAttributes** is as follows: + +``` +RecordSetStatusType getStatusAttributes ( + in ManagedEntityIdType recordSetId) + raises (AccessDenied, UnknownRecordSet); +``` + +The input parameter **recordSetId** uniquely identifies the recordSet within the Supplier Management System. + +The return value is of type **RecordSetStatusType** which contains the current status of the recordset. + +#### 9.4.1.4 suspendArchive + +Once the short-term archive has been created and initialized for use, the OMS can suspend its use. + +The signature of **suspendArchive** is as follows: + +``` +void suspendArchive ( + in ManagedEntityIdType recordSetId) + raises (AccessDenied, UnknownRecordSet); +``` + +The input parameter **recordSetId** uniquely identifies the recordSet within the Supplier Management System. + +The return value is of type **void**. + +#### 9.4.1.5 resumeArchive + +This operation resumes recording in an archive or initializes the recording within a recordSet that has been constructed in a locked state. + +The signature of **resumeArchive** is as follows: + +``` +void resumeArchive ( + in ManagedEntityIdType recordSetId) + raises (UnknownRecordSet, AccessDenied); +``` + +The input parameter **recordSetId** uniquely identifies the recordSet within the Supplier Management System. + +The return value is of type **void**. + +#### 9.4.1.6 deleteArchive + +This operation removes an archive from the Supplier Management System. + +The signature of **deleteArchive** is as follows: + +``` +void deleteArchive ( + in ManagedEntityIdType recordSetId ) + raises (UnknownRecordSet, AccessDenied ); +``` + +The input parameter **recordSetId** identifies the name that the Privileged User wishes to use to identify the log to be created in subsequent interactions. + +The return value is of type **void**. + +#### 9.4.1.7 purgeArchive + +The operation removes the information contained within a specified archive. However, the archive continues its recording. + +The signature of **purgeArchive** is as follows: + +``` +void purgeArchive ( + in ManagedEntityIdType recordSetId ) + raises (UnknownRecordSet, AccessDenied ); +``` + +The input parameter **recordSetId** identifies the name that the Privileged User wishes to use to identify the log to be created in subsequent interactions. + +The return value is of type **void**. + +#### 9.4.1.8 selectRecords + +After the creation of an archive, the OMS may select some of the records from it. + +The signature of **selectRecords** is: + +``` +RecordSeqType selectRecords ( + in FilterType selectionFilter, + in ManagedEntityIdType recordSetId) + raises (UnknownRecordSet, Timeout, NoSuchRecords, + AccessDenied, TooManyRecords); +``` + +The input parameter **recordSetId** identifies the name that the Privileged User wishes to use to identify the log to be created in subsequent interactions. The input parameter **selectionFilter** is defined by specific record set as defined in the data structure. + +The return value is of type **RecordSeqType** supplying the requested information. + +#### 9.4.1.9 recordSetListGet + +This operation allows an OMS to get a complete listing of record sets managed by the Supplier Management System. + +The signature of **recordSetListGet** is: + +``` +ManagedEntityIdSeqType recordSetListGet ( + in CreationModeType creationMode) + raises (AccessDenied); +``` + +The input parameter **creationMode** identifies the way the archive was creation, i.e., whether by an operator or automatically as part of Supplier Management System initialization. + +The return value is of type **ManagedEntityIdSeqType** listing the names for the short-term archives of the Supplier Management System. + +#### 9.4.1.10 changeUserLabel + +After the creation of a short-term archive, the OMS can change the User Label assigned to the archive. + +The signature of **changeUserLabel** is: + +``` +void changeUserLabel ( + in ManagedEntityIdType recordSetId, + in UserLabelType newUserLabel) + raises (UnknownRecordSet, AccessDenied, DuplicateUserLabel); +``` + +The input parameter **recordSetId** identifies the archive. The input parameter **newUserLabel** identifies the new name for a specific archive. + +The return value is of type **void**. + +#### 9.4.1.11 Exceptions + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **DuplicateUserLabel** is raised if the User Label provided in the request has been used to label another archive. In other words, the Supplier Management System is responsible for policing User Labels assigned for record sets within its management jurisdiction. + +The exception **LockedAlready** is raised if the set value of the administrativeState is "locked". + +The exception **NoSuchRecords** is raised if no records among the designated record sets matches the selection criteria. + +The exception **RecordSetExists** is raised if the archive defined by the parameters of creation request already exists in the Supplier Management System. + +The exception **Timeout** is raised if the process duration reached a system-defined timeout before the process could complete. + +The exception **TooManyRecords** is raised if the number of records selected for retrieval produces a response to the request that exceeds a predetermined size.4 + +The exception **UnknownRecordSet** is raised if the designated record set is unknown to the Supplier Management System. + +## **9.5 SoftwareDownload module** + +The software download process consists of four phases: delivery, distribution, installation (commit), and activation. The Supplier Management System supports these stages for the download of software generic programs, software upgrades, and software maintenance changes (patches) to NEs in this module. The Supplier Management System can accept requests involving one or multiple NEs at once. All software management activities can be individually scheduled. Any request for downloading software generics is accompanied by security credentials whereby the Supplier Management System is allowed to communicate with the source server. Which security credentials are being used depends on implementation: If the software load is resident on the EMS and the EMS will push it (through file transfer) to the NE, then the credentials are for the NE. If the software load is resident on the EMS and the NE will pull, then the credentials are for the EMS. If the software load is resident on a separate repository, then the security credentials are for the separate repository and the NE pulls the load from the repository. + +Requests for a software management activity may generate the creation of a software management tracking object. This lifecycle of this object must extend until all associated activities are completed successfully or unsuccessfully. The object is only deleted after a predefined retention period and the length of time of the retention period is agreed to outside the scope of this interface. The retention period for the tracking object should be generous enough to include any revert activity desired. If the tracking object has been automatically deleted by the Supplier Management System, then the revert activity is viewed as download activity of a previous software load. The OMS can also delete this tracking object before its automatic termination if desired. + +The Supplier Management System creates a log record for every software distribution activity including delivery, commitment, and activation, regardless of the result of the activity. The record contains detailed results for every affected target including start/stop times and success or failure indication. + +The Supplier Management System maintains a current listing of all software activities in progress. + +This module also includes support for retrieval of hardware and software version information from installed NEs. It is also possible to verify that a software set may be downloaded to a NE or to a specific plug-in unit. + +### **9.5.1 DownloadMgr interface** + +#### **9.5.1.1 deliverDistSWGlobal** + +This operation requests the Supplier Management System to download software generics from a software source machine for the purpose of software upgrades and software maintenance changes (patches) to NEs. The Supplier Management System can accept requests for one or multiple NEs at once. The operation is best effort, meaning the Supplier Management System attempts to execute the delivery and distribution to all specified targets. As appropriate, it continues to attempt to + +--- + +4 This size to be agreed upon by supplier and operator in advance. + +deliver and distribute software to all named targets, even when it encounters a failure in either process for a specific target. The activity completion log is used to record successes and failures of both the delivery and distribution attempts. The `SoftwareDownloadTrackingObject` continues to be available for commit, activate attempts and those activities are only attempted for targets where the delivery and distribution was successful. The `SoftwareDownloadTrackingObject` is retained beyond the successful activation stage (in part to allow for revert activities if required). + +Subsequently, if a new ONT is ranged, or if a broken fibre connection is repaired, or if a new plug-in unit is installed, and in each of these cases the active software load differs from that specified in this operation, then the Supplier Management System (or network resource) will be responsible for upgrading the software automatically. + +The signature of the operation **deliverDistSWGloab** is provided below: + +``` +SoftwareDownloadTrackingObjectIdType deliverDistSWGloab ( + in FilenameSeqType softwareSet, + in DCNAddressType softwareSourceAddr, + in UserIdType userId, + in PasswordType password, + in ManagedEntityIdSeqType deliverDistTargets) +raises (CommFailure, UnrecognisedTarget, + InsufficientMemory, SoftwareLoadHWMismatch, + SourceUnreachable, UnknownSoftwareLoad, Timeout, + AccessDenied, DeniedAccess); +``` + +The input parameter **softwareSet** identifies the software load and where it is located (file names and full path) to be downloaded. The input parameter **softwareSourceAddr** provides the DCN address of the server where the set of software resides. The input parameters **userId** and **password** provide the login mechanism to the softwareSource (assuming such security credentials are needed). The input parameter **deliverDistTargets** indicates the list of OLTs where the software is to be delivered. + +The return value of type **SoftwareDownloadTrackingObjectIdType** provides a reference to be used when attempting to commit, activate or check the status of the delivery and distribution process. The result of software download is logged by the Supplier Management System. + +#### 9.5.1.2 deliverDistSWSpecific + +This operation is the same as `deliverDistSWGloab` except the scope is within a single NE/PlugInUnit/slot as described in the input parameter `distributionTarget`. + +The operation signature of **deliverDistSWSpecific** is provided below: + +``` +SoftwareDownloadTrackingObjectIdType deliverDistSWSpecific ( + in FilenameSeqType softwareSet, + in DCNAddressType softwareSourceAddr, + in UserIdType userId, + in PasswordType password, + in TargetType deliverDistTarget) +raises (CommFailure, UnrecognisedTarget, + InsufficientMemory, SoftwareLoadHWMismatch, + SourceUnreachable, UnknownSoftwareLoad, Timeout, + AccessDenied, DeniedAccess); +``` + +The input parameter **softwareSet** identifies the software load and where it is located (file names and full path) to be downloaded. The input parameter **softwareSourceAddr** provides the DCN address of the server where the set of software resides. The input parameters **userId** and **password** provide the login mechanism to the softwareSource (assuming such security credentials are needed). The input parameter **deliverDistTarget** indicates the specific target at the NE/PlugInUnit/slot level. The components for the value of this parameter are described in Table 3. + +**Table 3/Q.834.4 – deliverDistTarget details** + +| Field name | Description | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| containingSystem | The system is identified by the Managed Entity Id of the headend OLT. | +| containingNE | Identifies the destination network resource. When the value is the empty sequence, the operation distributes the software to all NEs in the system. | +| plugInUnitType | Identifies the plugInUnitType. When this value is the empty string, the distribution target is all suitable plugInUnitTypes within the containingNE. | +| slot | Identifies the slot. When this value is the empty sequence, then any suitable slot is considered. | + +The return value of type **SoftwareDownloadTrackingObjectIdType** provides a correlation key reference to be used when attempting to commit, activate or check the status of the delivery and distribution process. The result of software download is logged by the Supplier Management System. + +#### 9.5.1.3 deleteSoftwareDownloadTrackingObject + +This operation allows the OMS to notify the Supplier Management System that the software tracking object specified is no longer needed. + +The operation signature of **deleteSoftwareDownloadTrackingObject** is provided below: + +``` +void deleteSoftwareDownloadTrackingObject ( + in SoftwareDownloadTrackingObjectIdType id) + raises (UnknownSoftwareDownloadTrackingObject, AccessDenied, + SoftwareTrackingObjectInUse); +``` + +The input parameters **id** identifies the software tracking object. + +The return value is of type **void**. + +#### 9.5.1.4 commit + +This operation requests the Supplier Management System to install (commit) the downloaded software to target locations. + +The operation signature of **commit** is provided below: + +``` +void commit ( + in SoftwareDownloadTrackingObjectIdType id, + in TargetType commitTarget) + raises (InstallationFailure, UnknownSoftwareDownloadTrackingObject, + AccessDenied, UnrecognisedTarget); +``` + +The input parameters **id** provides a reference to software download tracking object. The input parameter **commitTarget** specifies the specific target at the NE/PlugInUnit/slot level. The commitTarget can be a subset of the original target. + +The return value is of type **void**. + +#### 9.5.1.5 activate + +This operation activates installed software at target locations. + +The operation signature of **activate** is provided below: + +``` +void activate ( + in SoftwareDownloadTrackingObjectIdType id, + in TargetType activateTarget) +``` + +``` + + raises (UnknownSoftwareDownloadTrackingObject, + SoftwareNotYetInstalled, ActivationFailure, AccessDenied, + UnrecognisedTarget); + +``` + +The input parameters **id** provides a reference to software download tracking object. The input parameter **activateTarget** specifies the specific target at the NE/PlugInUnit/slot level. The activateTarget can be a subset of the original target. + +The return value is of type **void**. + +#### 9.5.1.6 revert + +This operation activates older installed software at target locations. The revert operation is only meaningfully invoked after activation of a new software load. The SoftwareDownloadTrackingObjectId refers to the most recent software download affecting the named Target. If revert completes successfully, then the active version becomes the standby version. + +The operation signature of **revert** is provided below: + +``` + +void revert ( + in SoftwareDownloadTrackingObjectIdType id, + in TargetType revertTarget) + raises (UnknownSoftwareDownloadTrackingObject, + SoftwareNotYetInstalled, ActivationFailure, AccessDenied, + UnrecognisedTarget, InvalidSoftwareTrackingObject); + +``` + +The input parameters **id** provides a reference to software download tracking object. The input parameter **revertTarget** specifies the specific target at the NE/PlugInUnit/slot level. The revertTarget can be a subset of the original target. + +The return value is of type **void**. + +#### 9.5.1.7 getStatus + +This operation requests the status of software activities. + +The operation signature of **getStatus** is provided below: + +``` + +DownloadStatusSeqType getStatus ( + in SoftwareDownloadTrackingObjectIdType id) + raises (UnknownSoftwareDownloadTrackingObject, AccessDenied); + +``` + +The input parameters **id** provides a reference to the software download tracking object. + +The return value of type **DownloadStatusSeqType** provides the progress status for all the download activities tracked by the Software Download Tracking Object. + +#### 9.5.1.8 scheduleDeliverDist + +This operation schedules the delivery and distribution of software to specified targets. The distribution of the software within the specified targets is up to the supplier's implementation. + +The operation signature of **scheduleDeliverDist** is provided below: + +``` + +SoftwareDownloadTrackingObjectIdType scheduleDeliverDist ( + in FilenameSeqType softwareSet, + in DCNAddressType softwareSourceAddr, + in UserIdType userId, + in PasswordType password, + in ManagedEntityIdSeqType deliverDistTargets, + in GeneralizedTimeType deliverDistStartTime) + raises (SoftwareLoadHWMismatch, AccessDenied, InvalidStartTime ); + +``` + +The input parameter **softwareSet** identifies the software load and where it is located (file names and full path) to be downloaded. The input parameter **softwareSourceAddr** provides the DCN address of the server where the set of software resides. The input parameters **userId** and **password** provide the login mechanism to the softwareSource (assuming such security credentials are needed). The input parameter **deliverDistTargets** indicates the list of OLTs where the software is to be delivered. The input parameter **deliverDistStartTime** provide the scheduled time to start. + +The return value of type **SoftwareDownloadTrackingObjectIdType** provides a reference to the scheduled process that can be used to track the progress of the process or to cancel it. + +#### 9.5.1.9 **scheduleCommit** + +This operation schedules the installation (commit) of software to predetermined targets. + +The operation signature of **scheduleCommit** is provided below: + +``` +void scheduleCommit ( + in SoftwareDownloadTrackingObjectIdType + deliverDistSoftwareDownloadTrackingObjectId, + in GeneralizedTimeType commitStartTime) + raises (UnknownSoftwareDownloadTrackingObject, + SoftwareNotYetInstalled, AccessDenied, InvalidStartTime ); +``` + +The input parameters **deliverDistSoftwareDownloadTrackingObjectId** provides a reference to software delivery tracking object. The input parameter **commitStartTime** provides the time to start this scheduled activity. + +The return value of type **void**. + +#### 9.5.1.10 **scheduleActivate** + +This operation schedules the activation of software to predetermined targets. + +The operation signature of **scheduleActivate** is provided below: + +``` +void scheduleActivate ( + in SoftwareDownloadTrackingObjectIdType id, + in GeneralizedTimeType activateStartTime) + raises (UnknownSoftwareDownloadTrackingObject, + SoftwareNotYetInstalled, AccessDenied, InvalidStartTime ); +``` + +The input parameters **id** provides a reference to the software delivery tracking object. The input parameter **activateStartTime** provides the time to start this activity. + +The return value of type **void**. + +#### 9.5.1.11 **cancelScheduledSoftwareActivity** + +This operation cancels all subsequently scheduled software download activities associated with this tracking object. + +The operation signature of **cancelScheduledSoftwareActivity** is provided below: + +``` +void cancelScheduledSoftwareActivity ( + in SoftwareDownloadTrackingObjectIdType id) + raises (UnknownSoftwareDownloadTrackingObject, + ActivityCompleted, ActivityInProgress, AccessDenied); +``` + +The input parameters **id** provides a reference to software activity tracking object. + +The return value is of type **void**. + +#### 9.5.1.12 **scheduledSoftwareDownloadTrackingObjectListGet** + +This operation retrieves the list of outstanding scheduled activities for software download. + +The operation signature of **scheduledSoftwareDownloadTrackingObjectListGet** is provided below: + +``` +SoftwareDownloadTrackingObjectIdSeqType +scheduledSoftwareDownloadTrackingObjectListGet () raises (AccessDenied); +``` + +There is no input parameter. + +The return value is of type **SoftwareDownloadTrackingObjectIdSeqType** which provides the list of outstanding scheduled activities. + +#### 9.5.1.13 onDemandSoftwareDownloadTrackingObjectListGet + +This operation retrieves the list of outstanding non-scheduled activities for software download. + +The operation signature of **onDemandSoftwareDownloadTrackingObjectListGet** is provided below: + +``` +SoftwareDownloadTrackingObjectIdSeqType +onDemandSoftwareDownloadTrackingObjectListGet () raises (AccessDenied); +``` + +There is no input parameter. + +The return value is of type **SoftwareDownloadTrackingObjectIdSeqType** which provides the list of outstanding non-scheduled activities. + +#### 9.5.1.14 Exceptions + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **ActivityCompleted** is raised when the software activity has been executed and cannot be cancelled. + +The exception **ActivationFailure** is raised if the software activation process failed even though the software has been installed (i.e., commit was successful). + +The exception **ActivityInProgress** is raised when the software activity has been initiated and cannot be cancelled. + +The exception **CommFailure** is raised when the DCN between Supplier Management System and OLT or the communication between OLT and source ONT is down. + +The exception **DeniedAccess** is raised if the access to NE is denied as a result of access control restrictions. + +The exception **InstallationFailure** is raised if the Software installation process failed. + +The exception **InsufficientMemory** is raised if there is insufficient memory on the NE to load the software. + +The exception **InvalidSoftwareTrackingObject** is raised if the referenced software tracking object is not the most recent associated with the installation of a software load on the NE. + +The exception **InvalidStartTime** is raised if the start time is before the current system time. + +The exception **SoftwareLoadHWMismatch** is raised if the designated software may not be loaded onto the equipment hardware since the version of the hardware cannot accept the software load. + +The exception **SoftwareNotYetInstalled** is raised when activation is requested and the software has not been installed yet. + +The exception **SoftwareTrackingObjectInUse** is raised when there are outstanding software activities tracked by this object and it may not be deleted. + +The exception **SourceUnreachable** is raised if the server holding the software load to be downloaded could not be reached by the OLT. + +The exception **Timeout** is raised if the process duration reached a system-defined timeout before the process could complete. + +The exception **UnknownSoftwareLoad** is raised when the specified software set cannot be found. + +The exception **UnknownSoftwareDownloadTrackingObject** is raised when the software download process is unknown to the Supplier Management System. + +The exception **UnrecognizedTarget** is raised when the designated software in the Secure File Server is unknown to the Supplier Management System. + +### 9.5.2 VersionRepository interface + +#### 9.5.2.1 retrieveVersions + +This operation retrieves all version information (both software and hardware) for a network resource. + +The operation signature of **retrieveVersions** is provided below: + +``` +VersionsSeqType retrieveVersions ( + in ManagedEntityIdType containingManagedEntityId) + raises (CommFailure, UnknownManagedEntity, AccessDenied); +``` + +The input parameters **containingManagedEntityId** identifies the network resource. + +The return value is of type **VersionsSeqType** and provides a listing of the hardware and software versions associated with this network resource. + +#### 9.5.2.2 validateNEVersion + +This operation requests the Supplier Management System to validate if the proposed software is compatible with the NE. + +The operation signature of **validateNEVersion** is provided below: + +``` +boolean validateNEVersion ( + in ManagedEntityIdType managedEntityId, + in VersionType proposedSoftware) + raises (UnknownNE, AccessDenied); +``` + +The input parameters **managedEntityId** identifies the NE. + +The input parameter **proposedSoftware** identifies the proposed software to be validated. + +The return value is of type **boolean**. + +#### 9.5.2.3 validatePlugInVersion + +This operation requests the Supplier Management System to validate if the proposed software is compatible with the plugInUnit. + +The operation signature of **validatePlugInVersion** is provided below: + +``` +boolean validatePlugInVersion ( + in ManagedEntityIdType plugInUnitId, + in VersionType proposedSoftware) + raises (UnknownManagedEntity, AccessDenied); +``` + +The input parameter **plugInUnitId** identifies the plugInUnit. + +The input parameter **proposedSoftware** identifies the proposed software to be validated. + +The return value is of type **boolean**. + +#### 9.5.2.4 Exceptions + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **CommFailure** is raised when the DCN between Supplier Management System and OLT or the communication between OLT and source ONT is down. + +The exception **UnknownManagedEntity** is raised if the Identifier for plugInUnit or port is unknown to the Supplier Management System. + +## 9.6 EventPublisher module + +On receipt of processed configuration, performance, or fault event information provided by other use cases within the Supplier Management System and based on rules concerning publication, the Supplier Management System queues and channels event information to all interested consumers, including Operators and OMS(s). + +### 9.6.1 AlarmEventSupplier interface + +The purpose of the interface is to announce alarm events to the Operator Management System via the OMG Notification Service. This interface has no operations. However, it does provide the fixed header mapping as well as the filterable data mappings for the structured event object used to push event information through the event channel of the OMG Notification Service. Both sets of mappings shall follow the guidelines specified in ITU-T Rec. X.780 for the Notifications interface. + +In the fixed header, the **domain\_type** is set to "telecommunications", the **type\_name** is set to "Alarm", and the **event\_name** is set to a constant string that has one of the following values: "Communications Alarm", "Environmental Alarm", "Equipment Alarm", "Processing Error Alarm", or "Quality of Service Alarm". + +The mapping in the filterable data consists of pairs of items. The first component in the pair is a string identifier for a data name and the second is the value for that data element. The string identifiers are constants that are defined in this interface. Furthermore, the filterable data pairs must occur in a specific order. + +The order of the filterable items is as follows: + +- AlarmEmittingMEId +- EventTime +- ProbableCause +- SpecificProblems +- PerceivedSeverity +- ServiceAffectingInd +- BackUpStatus +- BackUpManagedEntityId +- ThresholdInfo +- NotificationIdentifier +- CorrelatedNotifications +- StateChangeDefinition +- AdditionalText + +The value for ProbableCause has syntax ProbableCauseType and assumes one of the specific values defined in ITU-T Rec. X.780 or q834\_4::Q834Common::ProbableCauseConst. + +The value for ThresholdInfo has syntax MonitoredParameterType and assumes one of the specific values defined in q834\_4::Q834Common::MonitoredParameter. The null string is supplied for this value for all event\_names except "QualityOfServiceAlarm". + +The syntax and interpretation for all other data types and interpretation of their use is found in ITU-T Rec. X.780. + +### 9.6.2 SecurityEventSupplier + +The purpose of the interface is to announce security events to the Operator Management System via the OMG Notification Service. This interface has no operations. However, it does provide the fixed header mapping as well as the filterable data mappings for the structured event object used to push event information through the event channel of the OMG Notification Service. Both sets of mappings shall follow the guidelines specified in ITU-T Rec. X.780 for the Notifications interface. + +In the fixed header, the **domain\_type** is set to "telecommunications", the **type\_name** is set to "SecurityEvent", and the **event\_name** is set to a constant string that has one of the following values: "IntegrityViolation", "OperationalViolation", "PhysicalViolation", "SecurityEventViolation", or "TimeDomainViolation". + +The mapping in the filterable data consists of pairs of items. The first component in the pair is a string identifier for a data name and the second is the value for that data element. The string identifiers are constants that are defined in this interface. Furthermore, the filterable data pairs must occur in a specific order. + +The order of the filterable items is as follows: + +- EventEmittingMEId +- EventTime +- SecurityAlarmCause +- SecurityAlarmDetector +- ServiceUser +- ServiceProvider +- NotificationIdentifier +- CorrelatedNotifications +- AdditionalText + +The syntax for data types and interpretation of their use is found in ITU-T Rec. X.780. + +### 9.6.3 DiscoveryEventSupplier + +The purpose of the interface is to announce changes to installed equipment to the Operator Management System via the OMG Notification Service. This interface has no operations. However, it does provide the fixed header mapping as well as the filterable data mappings for the structured event object used to push event information through the event channel of the OMG Notification Service. + +In the fixed header, the **domain\_type** is set to "telecommunications", the **type\_name** is set to "DiscoveryEvent", and the **event\_name** is set to a constant string that has one of the following values: "ManagedEntityCreation" or "ManagedEntityDeletion". + +The mapping in the filterable data consists of pairs of items. The first component in the pair is a string identifier for a data name, and the second is the value for that data element. The string identifiers are constants that are defined in this interface. Furthermore, the filterable data pairs must occur in a specific order. + +The order of the filterable items for an event\_name of "ManagedEntityCreation" is as follows: + +- ManagedEntityType +- EventTime +- ManagedEntityAttributeValues +- NotificationIdentifier +- CorrelatedNotifications +- AdditionalText + +The value for ManagedEntityType has syntax of EquipmentType that indicates the type of inventory data discovered. The interface defines constants for various NE types as well as plugInUnits, equipmentHolders and software. + +The value for EventTime has syntax of GeneralizedTimeType and refers to the moment when the discovery condition was detected by the network. + +The value for ManagedEntityAttributeValues has syntax MEstruct. However, the data type supplied for this value is one of a set of data structures defined in the module. The data item ManagedEntityType identifies the type of struct that is passed in this value in the structured event object. + +The value for NotificationIdentifier has syntax NotificationIdentifierType and it provides a reference sequence number for the event. The value for CorrelatedNotifications has syntax of CorrelatedNotificationType and supplies a list of reference numbers for other event notifications provided by the Supplier Management System for associated inventory conditions. If there are no related notifications, the value of the empty set is supplied. + +Finally, the value for AdditionalText has syntax string. This data item provides a location to pass any textual miscellaneous information from the Supplier Management System concerning the inventory change condition. If there is no additional information, the null string will be passed. + +The order of the filterable items for an event\_name of "ManagedEntityDeletion" is as follows: + +- ManagedEntityType +- EventTime +- ManagedEntityAttributeValues +- NotificationIdentifier +- CorrelatedNotifications +- AdditionalText + +The value for ManagedEntityType has syntax of EquipmentType that indicates the type of inventory data removed. The interface defines constants for various NE types as well as plugInUnits and equipmentHolders. + +The value for EventTime has syntax of GeneralizedTimeType and refers to the moment when the removal condition was detected by the network. + +The value for ManagedEntityAttributeValues has syntax MEstruct. However, the data type supplied for this value is one of a set of data structures defined in the module. The data item ManagedEntityType identifies the type of struct that is passed in this value in the structured event object. + +The value for NotificationIdentifier has syntax NotificationIdentifierType and it provides a reference sequence number for the event. The value for CorrelatedNotifications has syntax of CorrelatedNotificationType and supplies a list of reference numbers for other event notifications + +provided by the Supplier Management System for associated inventory change conditions. If there are no related notifications the value of the empty set is supplied. + +Finally, the value for **AdditionalText** has syntax string. This data item provides a location to pass any textual miscellaneous information from the Supplier Management System concerning the inventory change condition. If there is no additional information, the null string will be passed. + +Insertion or removal of a plug-in unit always creates a notification no matter what provisioning state surrounds the plug-in unit. + +## 9.7 MIBTransfer module + +This module manages the process for collection of system configuration data to be used to restore a system in the event that a catastrophic failure condition has occurred. The collection of the configuration data can be done either on a real-time or on a scheduled basis. It also provides status information for backup and restoral processes in progress. The results of backup and restore processes are logged by the Supplier Management System. Any request to backup or restore configuration data is accompanied by security credentials whereby the Supplier Management System or OLT is allowed to communicate with the external server. While the backup is progress, all provisioning requests involving the designated OLT system are rejected/blocked. Transfer Tracking Objects are automatically deleted by the Supplier Management System once the associated file transfer(s) have finished and results (whether successful or unsuccessful) are recorded in the completion log. + +### 9.7.1 MIBMover interface + +#### 9.7.1.1 startBackup + +This operation initiates an immediate backup of system configuration data from a system and/or Supplier Management System to a backup server destination. + +The operation signature for **startBackup** is shown below: + +``` +TransferTrackingObjectIdType startBackup ( + in ManagedEntityIdType nEManagedEntityId, + in DCNAddressType destinationServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType destinationFile, + in boolean overwriteExistingFile) + raises (UnknownNE, UnknownDestinationServer, CommFailure, + EquipmentFailure, DeniedAccess, AccessDenied); +``` + +The input parameter **nEManagedEntityId** identifies the system to be backed up. The input parameter **destinationServerAddr** identifies the data communication networking address for the server that is the destination of the backup. The input parameter **userId** identifies the user login to the destination server. The input parameter **password** is the password to access the destination server. The input parameter **destinationFile** provides a full directory location for the backup file. Finally, the parameter **overwriteExistingFile** indicates whether or not the backup should allow the overwriting of a pre-existing file with the same destination directory location. + +The return value is of type **TransferTrackingObjectIdType** providing a correlation key to track the progress status of the backup process. + +#### 9.7.1.2 getBackupStatus + +This operation provides the capability to retrieve the status of a backup process. + +The operation signature for **getBackupStatus** is shown below: + +``` +StatusAttributeSeqType getBackupStatus ( + in TransferTrackingObjectIdType id) + raises (UnknownBackupProcess, AccessDenied); +``` + +The input parameter **id** identifies the backup process. + +The return value is of type **StatusAttributeSeqType** and gives the status of the previously requested backup process. + +#### 9.7.1.3 scheduleBackup + +This operation schedules backup processes. + +The operation signature for **scheduleBackup** is shown below: + +``` +TransferTrackingObjectIdType scheduleBackup( + in ManagedEntityIdType nEManagedEntityId, + in UserIdType userId, + in PasswordType password, + in UserLabelType schedulerName, + in DCNAddressType destinationServerAddr, + in FilenameType destinationFile, + in boolean overwriteExistingFile) + raises (UnknownNE, UnknownScheduler, UnknownDestinationServer, + InvalidScheduler, AccessDenied); +``` + +The input parameter **nEManagedEntityId** identifies the OLT to be backed up. The input parameter **schedulerName** is the scheduler name to be used for backup. The input parameter **userId** identifies the user login to the destination server. The input parameter **password** is the password to access the destination server. The parameter **destinationServerAddr** indicates the DCN address for the destination server where the data is to be backed up. The input parameter **destinationFile** provides a full directory location for the backup file. Finally, the parameter **overwriteExistingFile** indicates whether or not the backup should allow the overwriting of a pre-existing file with the same destination directory location. + +The return value is of type **TransferTrackingObjectIdType** and provides a correlation key to be used when attempting to track the status of the non-real time at some later point. + +#### 9.7.1.4 modifyBackupSchedule + +This operation cancels all subsequent backup processes for a system based on a scheduler. This operation will not interrupt a backup process in progress. + +The operation signature for **modifyBackupSchedule** is shown below: + +``` +void modifyBackupSchedule ( + in TransferTrackingObjectIdType id, + in UserLabelType newSchedulerName) + raises (UnknownBackupProcess, AccessDenied, UnknownScheduler, + InvalidScheduler); +``` + +The input parameter **id** identifies the scheduled process to be modified. The input parameter **newSchedulerName** identifies the new time triggers. + +The return value is of type **void**. + +#### 9.7.1.5 cancelScheduledBackup + +This operation cancels all subsequent backup processes for a system based on a scheduler. This operation will not interrupt a backup process in progress. + +The operation signature for **cancelScheduledBackup** is shown below: + +``` +void cancelScheduledBackup ( + in TransferTrackingObjectIdType id) + raises (UnknownBackupProcess, AccessDenied); +``` + +The input parameter **id** identifies the scheduled process to be cancelled. + +The return value is of type **void**. + +#### 9.7.1.6 abortBackup + +This operation aborts a backup process in progress whether scheduled or not. Subsequent scheduled backup process are not affected by this operation. + +The operation signature for **abortBackup** is shown below: + +``` +void abortBackup ( + in TransferTrackingObjectIdType id) + raises (UnknownBackupProcess, CommFailure, EquipmentFailure, + AccessDenied); +``` + +The input parameter **id** identifies the backup process to be aborted. + +The return value is of type **void**. + +#### 9.7.1.7 startRestore + +This **startRestore** operation provides functionality to restore a system based on a backed up copy of configuration data. + +The operation signature for **startRestore** is shown below. The configuration data is resident on an external secure server. + +``` +TransferTrackingObjectIdType startRestore ( + in ManagedEntityIdType nEManagedEntityId, + in DCNAddressType sourceServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType sourceFile) + raises ( UnknownNE, CommFailure, EquipmentFailure, + UnknownSourceServer, DeniedAccess, + SoftwareLoadHardwareMismatch, AccessDenied ); +``` + +The input parameter **nEManagedEntityId** identifies the OLT to be restored. The input parameter **sourceServerAddr** identifies the data communication networking address for the server that is the destination of the backup. The input parameter **userId** identifies the user login to the destination server. The input parameter **password** is the password to access the destination server. The parameter **sourceFile** indicates the file where the data has been backed up, from which the restoral will take place. + +The return value is of type **TransferTrackingObjectIdType** and provides a correlation key to be used when attempting to track the status of the requested restoration. + +#### 9.7.1.8 getRestoreStatus + +This operation provides the status of a restoral process. + +The operation signature for **getRestoreStatus** is shown below: + +``` +StatusAttributeSeqType getRestoreStatus ( + in TransferTrackingObjectIdType id) + raises (UnknownRestoreProcess, AccessDenied); +``` + +The input parameter **id** identifies the restoration process. + +The return value is of type **StatusAttributeSeqType** and provides the progress state of the restoration process. + +#### 9.7.1.9 transferTrackingObjectIdListGet + +This operation retrieves the list of outstanding system MIB transfers, both backup and restore. + +The operation signature of **transferTrackingObjectIdListGet** is provided below: + +``` +TransferTrackingObjectIdSeqType transferTrackingObjectIdListGet () + raises (AccessDenied); +``` + +There is no input parameter. + +The return value is of type **TransferTrackingObjectIdSeqType** which provides the list of outstanding system MIB transfers, both backup and restore. + +#### 9.7.1.10 Exceptions + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **CommFailure** is raised when the DCN between Supplier Management System and OLT or the communication between OLT and source ONT is down. + +The exception **DeniedAccess** is raised if the access to NE is denied. + +The exception **EquipmentFailure** is raised when the equipment where the data is backed up from is in failure condition. + +The exception **InvalidScheduler** is raised when the given scheduler is inappropriate for use in this operation or out-of-date. + +The exception **SoftwareLoadHardwareMismatch** is raised when the source software does not match with the destination hardware. + +The exception **UnknownBackupProcess** is raised when the given TransferTrackingObjectId related backup process is not found. + +The exception **UnknownDestinationServer** is raised when the IP address of destination server is not found. + +The exception **UnknownNE** is raised when the OLT is unknown to the Supplier Management System. + +The exception **UnknownRestoreProcess** is raised when the given TransferTrackingObjectId related restoral process is unknown. + +The exception **UnknownScheduler** is raised when the given scheduler name is not found. + +The exception **UnknownSourceServer** is raised when the source server is unknown to the Supplier Management System. + +## 9.8 PerformanceManager module + +The Supplier Management System shall provide for the activation and deactivation of performance data or traffic measurements reporting on individual termination points contained in the NEs as required by the operator or OMS for OLTs that have been installed. Requirements for the Supplier Management System found in this Recommendation also include provision for the setting of threshold values and describe automatic reporting of performance measurements to the Supplier + +Management System when thresholds have been crossed. When there is an occurrence of a set of Threshold Crossing Alerts associated with a single performance degradation condition, the Supplier Management System shall analyse and correlate the alert events within its domain to the best of its ability, determine the underlying root cause of the problem, and store this information in a log. If several occurrences of the same root cause impairment are detected within a period of time, the Supplier Management System shall prepare a QoS alarm record for publication any interested consumer (Operator or OMS). If the Supplier Management System can collect all the history data records for all the monitoring points5 for all the network elements in its management domain, there is no need for reporting control. In this case, it is assumed that reporting is constantly available. + +### 9.8.1 ImpairmentPersistence interface + +Throughout this Recommendation, it is assumed and required that profile objects that are of threshold data type6 are groupings of threshold values can be associated with one, and only one, type of monitoring point. + +#### 9.8.1.1 setSlidingWindowParameters + +This operation sets the sliding window parameters for one, some or all monitored parameters in an NE. This setting is applied for all points monitoring the parameters. Subsequently, the Supplier Management System generates a QoS alarm if a monitoring point detects a TCA **persistenceMinimum** times within **totConsecutiveIntvls** consecutive monitoring intervals. This operation is best effort. + +The exception **CommFailure** is raised if the Supplier Management System is unable to communicate with the NE identified in the operation, and if the sliding window parameter values are set directly on network resources. + +This operation is used to establish system-wide default settings if the indicator **sysScopeInd** has the value **TRUE** and the **nManagedEntityId** is the identifier for an OLT. This means that the sliding window parameter values are to be applied to all monitoring points of any equipment components currently or potentially belonging to the system with the named OLT headend. If the OLT has lost communications with any subtending network resource prior to or during invocation of this operation, it is up to supplier implementation to guarantee that the settings are applied once communication is established. If the indicator **sysScopeInd** has the value **TRUE** and the **nManagedEntityId** is the identifier for an ONU, then the settings are viewed to apply to the ONU and all NTs subtending from it. As equipment components are added to the system with headend of OLT or ONU, the Supplier Management System automatically sets these parameter values. + +If **sysScopeInd** has the value **FALSE**, then the sliding window parameter settings are to be applied only to the indicated resource. The settings are still applied to both existing and potential equipment components of the node. + +The operation signature for **setSlidingWindowParameters** is shown below: + +``` +void setSlidingWindowParameters ( + in ManagedEntityIdType nManagedEntityId, + in MonitoredParameterSeqType monitoredParameterList, + in short totConsecutiveIntvls, + in short persistenceMinimum, + in boolean sysScopeInd) + raises (UnknownNE, UnknownParameters, IntervalCountTooLarge, + AccessDenied, CommFailure); +``` + +--- + +5 History data records and monitoring points are defined in ITU-T Rec. Q.834.1. + +6 Of type 21 as specified in the ProfileManager module. + +The input parameter **nEManagedEntityId** identifies the network element. The input parameter **monitoredParameterList** identifies the parameters to be monitored. Values for the parameters are provided in q834\_4::Q834Common::MonitoredParameter. The input parameter **totConsecutiveIntvls** identifies the value of total consecutive monitored intervals. The input parameter **persistenceMinimum** identifies the minimum number of occurrences of the TCA for the monitoredParameter. The input **sysScopeInd** indicates whether or not the sliding window settings should be applied to all network elements subtending from the initial one designated in the operation. + +The return value is of type **void**. + +#### 9.8.1.2 setSpecificSlidingWindowParameters + +This operation is similar to the operation setSlidingWindowParameters except the scope of assignment of settings is limited to a specific monitoring point identified in the operation. + +The operation signature for **setSpecificSlidingWindowParameters** is shown below: + +``` +void setSpecificSlidingWindowParameters ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in MonitoredParameterSeqType monitoredParameterList, + in short totConsecutiveIntvls, + in short persistenceMinimum, + in boolean allowGlobalOverwrite) + raises (UnknownNE, UnknownParameters, IntervalCountTooLarge, + AccessDenied, UnknownManagedEntity, CommFailure, EquipmentFailure); +``` + +The input parameter **nEManagedEntityId** identifies the network element managed by the Supplier Management System. The input parameter **monitoringPoint** identifies the specific monitoring point for setting the sliding window parameters for a monitored parameter. The input parameter **monitoredParameterList** identifies the parameters to be monitored values for which are defined in Q834Common::MonitoredParameter. The input parameter **totConsecutiveIntvls** identifies the value of total consecutive monitored intervals. The input parameter **persistenceMinimum** identifies the minimum number of occurrences of the TCA for the monitoredParameter. The parameter **allowGlobalOverwrite** indicates if the specific sliding window parameters can be overwritten in a subsequent invocation of **setSlidingWindowParameters** operation. + +The return value is of type **void**. + +#### 9.8.1.3 getSpecificSlidingWindowParameters + +This operation provides a listing of monitoring points and their sliding window settings for a specified parameter. + +The operation signature for **getSpecificSlidingWindowParameters** is shown below: + +``` +SWPValueSeqType getSpecificSlidingWindowParameters ( + in ManagedEntityIdType nEManagedEntityId, + in MonitoredParameterType monitoredParameter) + raises (UnknownNE, UnknownParameters, CommFailure); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **monitoredParameter** identifies the parameter to be monitored and is defined in q834\_4::Q834Common::MonitoredParameter. + +The return value is of type **SWPValueSeqType** providing the sliding window assignments for a specific monitoring point. + +#### 9.8.1.4 setThreshold + +This operation sets the threshold value identified by a profile to a monitoring point in a network element. + +The operation signature for **setThreshold** is shown below: + +``` +void setThreshold ( + in ManagedEntityIdType nManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in NameType thresholdDataProfileName ) + raises (UnknownNE, AccessDenied, UnknownManagedEntity, + UnknownProfiles, InvalidAssociation, CommFailure, ProfileSuspended); +``` + +The input parameter **nManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **monitoringPoint** identifies the specific monitoring point for setting the sliding window parameters for a monitored parameter. The input parameter **thresholdDataProfileName** provides listing of profile names for threshold values. + +The return value is of type **void**. + +#### 9.8.1.5 setThresholds + +This operation allows the setting of a collection of threshold value, monitoringPointType pairs on a particular NE. The exception CommFailure is raised if the Supplier Management System is unable to communicate with the NE identified in the operation, and if threshold values are set directly on network resources. + +This operation is used to establish system-wide default settings if the indicator sysScopeInd has the value TRUE and the nManagedEntityId is the identifier for an OLT. This means that the threshold values are to be applied to all monitoring points of any equipment components currently or potentially belonging to the system with the named OLT headend. If the OLT has lost communications with any subtending network resource prior to or during invocation of this operation, it is up to supplier implementation to guarantee that the settings are applied once communication is established. If the indicator sysScopeInd has the value TRUE and the nManagedEntityId is the identifier for an ONU, then the settings are viewed to apply to the ONU and all NTs subtending from it. As equipment components are added to the system with headend of OLT or ONU, the Supplier Management System automatically sets these threshold values. + +If sysScopeInd has the value FALSE, then the threshold settings are to be applied only to the indicated resource. The settings are still applied to both existing and potential equipment components of the node. + +The operation signature for **setThresholds** is shown below: + +``` +void setThresholds ( + in ManagedEntityIdType nManagedEntityId, + in boolean sysScopeInd, + in ThresholdsSeqType thresholdsList) + raises (UnknownNE, UnknownProfiles, AccessDenied, + UnknownMonitoringPointTypes, InvalidAssociation, + CommFailure, ProfileSuspended ); +``` + +The input parameter **nManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **thresholdList** identifies a list of pairs consisting of Threshold Data name and monitoringPointType. The input **sysScopeInd** indicates whether or not the sliding window settings should be applied to all network elements subtending from the initial one designated in the operation. + +The return value is of type **void**. + +#### 9.8.1.6 getThresholdValues + +This operation provides a listing of monitoring points and their threshold data setting names for a specified monitoring point type. + +The operation signature for **getThresholdValues** is shown below: + +``` +MonitoringPointThresholdsSeqType getThresholdValues ( + in ManagedEntityIdType nEManagedEntityId, + in MonitoringKindType monitoringPointType) + raises (UnknownNE, UnknownMonitoringPointTypes, CommFailure); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **monitoringPointType** identifies the monitoring point on which the retrieval is based. + +The return value is of type **MonitoringPointThresholdsSeqType** and provides the setting values for threshold crossings. + +#### 9.8.1.7 getSystemThresholdsSetting + +This operation retrieves the system default values for Threshold Data. + +The operation signature of **getSystemThresholdsSetting** is provided below: + +``` +ThresholdsSeqType getSystemThresholdsSetting ( + in ManagedEntityIdType nEManagedEntityId) + raises (AccessDenied, UnknownManagedEntity); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the system for which default settings are requested. + +The return value is of type **ThresholdsSeqType** which provides the list of system defaults. + +#### 9.8.1.8 getSystemSWSettings + +This operation retrieves the system default sliding window settings. + +The operation signature of **getSystemSWSettings** is provided below: + +``` +ParameterSettingSeqType getSystemSWSettings ( + in ManagedEntityIdType nEManagedEntityId) + raises (AccessDenied, UnknownManagedEntity); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the system for which default sliding window settings are requested. + +The return value is of type **ParameterSettingSeqType** which provides the list of system defaults. + +#### 9.8.1.9 Exceptions + +The exception **AccessDenied** is raised when the operator management system is not granted access to this interface object. + +The exception **CommFailure** is raised when there was a DCN link failure between the NE and the Supplier Management System fails. + +The exception **EquipmentFailure** is raised when the equipment is in failure condition and the settings cannot be applied. + +The exception **InvalidAssociation** is raised when the given profile cannot be applied to a monitoring point. + +The exception **IntervalCountTooLarge** is raised when the requested intervals exceed the maximum supported by the Supplier Management System. The exception indicates the maximum allowed monitoring intervals supported by the Supplier Management System. + +The exception **ProfileSuspended** is raised when profile(s) named in the invocation has been suspended for use within the Supplier Management System by the OMS or operator. + +The exception **UnknownNE** is raised when the NE mentioned in the request is unknown to the Supplier Management System. + +The exception **UnknownManagedEntity** is raised when the monitoring point is unknown to the Supplier Management System. + +The exception **UnknownMonitoringPointTypes** is raised when the monitoring point is unknown to the Supplier Management System. + +The exception **UnknownParameters** is raised when the given monitored parameter is unknown in the Supplier Management System. + +The exception **UnknownProfiles** is raised if the profile name provided is unknown to the Supplier Management System and cannot be retrieved from the profile object repository. + +### 9.8.2 ReportController interface + +#### 9.8.2.1 addCustomerMonitoringReporting + +This operation adds a historydatatype to be monitored to a specific monitoring point in response to a customer complaint identified by the supplied serviceInstanceId or in order to support CNM services. + +The operation signature for **addCustomerMonitoringReporting** is shown below: + +``` +void addCustomerMonitoringReporting ( + in ManagedEntityIdType nEManagedEntityId, + in ServiceInstanceIdType serviceInstanceId, + in ManagedEntityIdType monitoringPoint, + in GeneralizedTimeType stopTime, + in HistoryDataType historyData, + in short granularityPeriod) + raises ( UnknownServiceInstance, AccessDenied, UnknownNE, + UnknownManagedEntity, CollectionPeriodPast, CollectionLimitation, + InvalidAssociation, UnknownHistoryDataType, CommFailure); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **serviceInstanceId** identifies the customer service instance associated with the monitoring point. The input parameter **monitoringPoint** identifies the specific monitoring point for collecting history data. The input parameter **stopTime** identifies the time at which the collection of history data will cease. If the reporting is to be ongoing, then stopTime is given as "0". Reporting also terminates automatically when the service is deleted. The input parameter **historyData** identifies the type of history data to be collected, the values of which are defined in q834\_4::Q834Common::RecordSetType. The input parameter **granularityPeriod** identifies the collection interval period in minutes. When the **stopTime** falls within the granularity period, the history data is collected for the whole granularity period. + +The return value is of type **void**. + +#### 9.8.2.2 removeCustomerMonitoringReporting + +This operation removes all historydatatype collection on behalf of a supplied service instance. + +The operation signature for **removeCustomerMonitoringReporting** is shown below: + +``` +void removeCustomerMonitoringReporting ( +``` + +``` + + in ServiceInstanceIdType serviceInstanceId ) + raises ( UnknownServiceInstance, AccessDenied, + CollectionPeriodPast, CommFailure); + +``` + +The input parameter **serviceInstanceId** identifies the customer service instance associated with the monitoring point. + +The return value is of type **void**. + +#### 9.8.2.3 selectByServiceInstance + +This operation gets all the records available in the Supplier Management System associated with the given serviceInstanceId. The returned list has no redundant records. The Supplier Management System scans all relevant recordsets. + +The operation signature for **selectByServiceInstance** is shown below: + +``` + +RecordsSeqType selectByServiceInstance ( + in ServiceInstanceIdType serviceInstanceId, + in GeneralizedTimeType intervalStartTime, + in GeneralizedTimeType intervalEndTime) + raises ( UnknownServiceInstance, AccessDenied); + +``` + +The input parameter **serviceInstanceId** identifies the customer service instance. The input parameter **intervalStartTime** filters out selection of history data records with periodEndTime before this value. The input parameter **intervalEndTime** filters out selection of history data records with periodEndTime after this value. + +The return value is of type **RecordsSeqType** that provides a list of history data records associated with performance monitoring reported for this service instance. + +#### 9.8.2.4 displayActiveReporting + +This operation gets all the monitoring points for which history data is currently being collected for a given serviceInstanceId. + +The operation signature for **displayActiveReporting** is shown below: + +``` + +MonitoringPointSeqType displayActiveReporting ( + in ServiceInstanceIdType serviceInstanceId) + raises ( UnknownServiceInstance, AccessDenied); + +``` + +The input parameter **serviceInstanceId** identifies the customer service instance. + +The return value is of type **MonitoringPointSeqType** and provides the listing of all actively reporting monitoring points. + +#### 9.8.2.5 addNewMonitoringReporting + +This operation adds a history data type to be monitored on a specific monitoring point. + +The operation signature for **addNewMonitoringReporting** is shown below: + +``` + +void addNewMonitoringReporting ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in GeneralizedTimeType stopTime, + in HistoryDataType historyData, + in short granularityPeriod) + raises ( AccessDenied, UnknownNE, UnknownManagedEntity, + CollectionPeriodPast, CollectionLimitation, InvalidAssociation, + UnknownHistoryDataType, CommFailure); + +``` + +The input parameter **nEManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **monitoringPoint** identifies the specific + +monitoring point for collecting history data. The input parameter **stopTime** identifies the time at which the collection of history data will cease. If the reporting is to be ongoing, then stopTime is given as "0". Reporting also terminates automatically when the managedEntity (monitoring point) deleted. The inputParameter **historyData** identifies the type of history data to be collected, the values of which are defined in q834\_4::Q834Common::RecordSetType. The input parameter **granularityPeriod** identifies the collection interval period in minutes. When the **stopTime** falls within the granularity period, the history data is collected for the whole granularity period. + +The return value is of type **void**. + +#### 9.8.2.6 selectByMonitoringPoint + +This operation gets all the records available in the Supplier Management System associated with the given monitoring point. The returned list has no redundant records. + +The operation signature for **selectByMonitoringPoint** is shown below: + +``` +RecordsSeqType selectByMonitoringPoint ( + in ManagedEntityIdType monitoringPoint, + in GeneralizedTimeType intervalStartTime, + in GeneralizedTimeType intervalEndTime) + raises ( UnknownManagedEntity, AccessDenied); +``` + +The input parameter **monitoringPoint** identifies the specific monitoring for which records should be retrieved. The input parameter **intervalStartTime** filters out selection of history data records with periodEndTime before this value. The input parameter **intervalEndTime** filters out selection of history data records with periodEndTime after this value. + +The return value is of type **RecordsSeqType** and provides all the history data records stored within the Supplier Management System reported by the monitoring point within the time period specified. + +#### 9.8.2.7 createReportingSchedule + +This operation adds a scheduled collection of history data to be monitored on a specific monitoring point. The Supplier Management System will collect a historyData record for the monitoring point based on the schedule. The schedule identifies the periodEndTime(s) for the records to be collected. + +The operation signature for **createReportingSchedule** is shown below: + +``` +void createReportingSchedule ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in HistoryDataType historyData, + in ServiceInstanceIdType serviceInstance, + in short granularityPeriod, + in UserLabelType schedulerName) + raises (AccessDenied, UnknownNE, UnknownManagedEntity, + CollectionLimitation, UnknownScheduler, InvalidAssociation, + UnknownHistoryDataType, InvalidScheduler); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **monitoringPoint** identifies the specific monitoring point for collecting history data. The inputParameter **historyData** identifies the type of history data to be collected, the values of which are defined in q834\_4::Q834Common::RecordSetType. The input parameter **serviceInstance** provides an optional reference to a service instance. Empty string value is used if no reference is desired. The input parameter **granularityPeriod** identifies the collection interval period in minutes. The input parameter **schedulerName** identifies the name for a schedule that was created earlier. + +The return value is of type **void**. + +#### 9.8.2.8 modifyReportingSchedule + +This operation modifies the scheduled collection of history data to be monitored on a specific monitoring point. If successful, the change to scheduled collection of history data will occur with the next iteration. + +The operation signature for **modifyReportingSchedule** is shown below: + +``` +void modifyReportingSchedule ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in HistoryDataType historyData, + in UserLabelType newSchedulerName) + raises (AccessDenied, UnknownNE, UnknownManagedEntity, + CollectionLimitation, UnknownScheduler, InvalidAssociation, + UnknownHistoryDataType, InvalidScheduler); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **monitoringPoint** identifies the specific monitoring point for collecting history data. The input parameter **historyData** identifies the type of history data to be collected, the values of which are defined in q834\_4::Q834Common::RecordSetType. The input parameter **newSchedulerName** identifies the name of the new schedule to be applied. + +The return value is of type **void**. + +#### 9.8.2.9 cancelReportingSchedule + +This operation cancels subsequent scheduled reporting of history data where the reporting was requested by the operator previously. It does not interrupt history data reporting in progress or reporting that is supported as default behaviour between the Supplier Management System and the network resources. + +The operation signature for **cancelReportingSchedule** is shown below: + +``` +void cancelReportingSchedule ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in HistoryDataType historyData, + in UserLabelType schedulerName) + raises (AccessDenied, UnknownNE, UnknownManagedEntity, + UnknownScheduler, InvalidAssociation, UnknownHistoryDataType); +``` + +The input parameter **nEManagedEntityId** uniquely identifies the network element managed by the Supplier Management System. The input parameter **monitoringPoint** identifies the specific monitoring point for collecting history data. The input parameter **historyData** identifies the type of history data to be collected, the values of which are defined in q834\_4::Q834Common::RecordSetType. The input parameter **schedulerName** identifies the schedule to be cancelled. + +The return value is of type **void**. + +#### 9.8.2.10 Exceptions + +The exception **AccessDenied** is raised when the operator management system is not granted access to this interface object. + +The exception **CommFailure** is returned when there was a DCN link failure between the NE and the Supplier Management System. + +The exception **CollectionLimitation** is raised when the Supplier Management System cannot collect data for the given time duration and granularity period due to implementation restrictions. + +The exception **CollectionPeriodPast** is raised when period end time is lesser than equal to the current time. + +The exception **InvalidAssociation** is raised when the given profile cannot be applied to a monitoringPoint. + +The exception **InvalidScheduler** is raised when the given scheduler is inappropriate for use in this operation or out-of-date. + +The exception **UnknownNE** is raised when the NE mentioned in the request is unknown to the Supplier Management System. + +The exception **UnknownHistoryDataType** is raised when history data type is unknown in the Supplier Management System. + +The exception **UnknownManagedEntity** is raised when the monitoring point is unknown to the Supplier Management System. + +The exception **UnknownScheduler** is raised when the named scheduler is unknown to the Supplier Management System. + +The exception **UnknownServiceInstance** is raised when the Service Instance is unknown to the Supplier Management System. + +## 9.9 ProfileManager + +This module consists of three interfaces: ProfileConsumer, ProfileUsageMgr, and ProfileRetriever. ProfileConsumer specifies the contents of event notification for profile creations within the Profile Object Repository. ProfileUsageMgr supports operations to manage profile settings cached within the Supplier Management System. ProfileRetriever allows Supplier Management System to obtain the values for profile settings. + +### 9.9.1 ProfileConsumer Interface + +The purpose of the interface is to announce the existence of new profile settings and to convey those settings to the Supplier Management System. This interface has no operations. However, it does provide the fixed header mapping as well as the filterable data mappings for the structured event object used to push event information through the event channel of the OMG Notification Service. + +In the fixed header, the **domain\_type** is set to "telecommunications", the **type\_name** is set to "ProfileEvent", and the **event\_name** is set to a constant string that has the value "ProfileCreation" as defined in the interface. + +The mapping in the filterable data follows a strategy using a constant string identifier for the filterable data component followed by the value for that data element. Also, the filterable data items are listed in a specific order. + +The order of the filterable items is ProfileName, ProfileType, EventTime, ProfileAttributeValues, and NotificationIdentifier. ProfileName value has the syntax of NameType. ProfileType value has the syntax "unsigned short", and it allows the consumer (Supplier Management System) to identify the type of profile created and to unmarshal the attribute values found later in profileStruct. The syntax of ProfileAttributeValues is profileStruct. EventTime has the syntax of GeneralizedTimeType, and it is the time that the profile was created. NotificationIdentifier has the syntax of NotificationIdentifierType. This identifier uniquely labels the profile creation event and is incremented with each profile creation. + +### 9.9.2 ProfileUsageMgr interface + +#### 9.9.2.1 reName + +This operation provides the capability to rename a profile. + +The operation signature for **reName** is shown below: + +``` +void reName ( + in NameType oldProfileName, + in NameType newProfileName) + raises (UnknownProfiles, AccessDenied, DuplicateProfileName); +``` + +The input parameter **oldProfileName** is the old profile name to be renamed. The input parameter **newProfileName** is the new name for the profile. + +The return value is of type **void**. + +#### 9.9.2.2 inUse + +This operation returns a boolean value to tell if the profile is in use. + +The operation signature for **inUse** is shown below: + +``` +boolean inUse ( + in NameType profileName) + raises (UnknownProfiles, AccessDenied); +``` + +The input parameter **profileName** provides the profile name which is to be checked if it is used by the other party. + +The return value is of type **boolean**. + +#### 9.9.2.3 suspendUse + +This operation suspends the use of a profile. + +The operation signature for **suspendUse** is shown below: + +``` +void suspendUse ( + in NameType profileName) + raises (UnknownProfiles, AccessDenied); +``` + +The input parameter **profileName** is a profile name which is to be suspended. + +The return value is of type **void**. + +#### 9.9.2.4 resumeUse + +This operation resumes the use of a named profile. + +The operation signature for **resumeUse** is shown below: + +``` +void resumeUse ( + in NameType profileName) + raises (UnknownProfiles, AccessDenied); +``` + +The input parameter **profileName** names the profile whose values are to be again made available for use by the Supplier Management System. + +The return value is of type **void**. + +#### 9.9.2.5 deleteProfile + +This operation deleteProfile provides the capability to remove a profile which is not in use. + +The operation signature for **deleteProfile** is shown below: + +``` +void deleteProfile (in NameType profileName) raises (UnknownProfiles, +AccessDenied, ProfileInUse); +``` + +The input parameter **profileName** is the name of the profile to be deleted. + +The return value is of type **void**. + +#### 9.9.2.6 Exceptions + +The exception **AccessDenied** is raised when the OMS is not granted access to the requested operation. + +The exception **DuplicateProfileName** is raised when duplicate profile name is found. + +The exception **ProfileInUse** is raised when deleting a profile, and found when the profile is in use by the other party. + +The exception **UnknownProfiles** is raised if the profile name provided is unknown to the Supplier Management System and cannot be retrieved from the profile object repository. + +### 9.9.3 ProfileRetriever interface + +#### 9.9.3.1 retrieve + +This operation provides the capability to retrieve a profile. This operation is used by the Supplier Management System to retrieve a profile from the Operator management system. + +The operation signature for **retrieve** is shown below: + +``` +ProfileInfoType retrieve ( + in NameType profileName) + raises (UnknownProfiles); +``` + +The input parameter **profileName** is the name of the profile to be retrieved. + +The return value is of type **ProfileInfoType** and provides the attribute values for the named profile. + +#### 9.9.3.2 Exceptions + +The exception **UnknownProfiles** is raised if the profile name provided is unknown to the Supplier Management System and cannot be retrieved from the profile object repository. + +## 9.10 Registrar module + +This module supports the process of bringing a new NE into the management jurisdiction of the Supplier Management System. It supports both initial installations and equipment replacements motivated by maintenance or service upgrades. It explicitly supports the ranging function that is used to measure the round trip delay between the OLT and each ONU or ONT and establish security mechanisms (churning key algorithm) and communication timing including automatic setup of the embedded operations channel. + +A set of managed entities is automatically created in the management information model maintained by the Supplier Management System as a result of registration. Depending on the equipment type, instances of OLT, ONT, ONU, APONLink, APONTTP, APONTrail, APONNetworkCTP, APONNetworkTTP, APONLinkConnection, tcAdapterF, vpLinkConnectionF, vpTopologicalLinkF, and physicalPathTPF are automatically created. Depending on supplier implementation as well as what is physically installed, other managed entities are also automatically created. + +### 9.10.1 NERegistrar interface + +#### 9.10.1.1 registerNE + +This operation registers an NE with a particular instance of Supplier Management System. The NE should be installed at this point. The Managed Entity Id of the NE is returned in order to indicate that the Supplier Management System can perform at least one rudimentary management function. + +The operation signature for **registerNE** is shown below: + +``` +ManagedEntityIdType registerNE ( + in DCNAddressType nEDCNAddress, + in UserLabelType nEUserLabel, + in AdministrationDomainType administrationDomain) + raises (AccessDenied, DCNTimeout, AddressLabelMismatch, + DuplicateUserLabel, TooManyNEs, InvalidDCNAddress, + DeniedAccess, InvalidUserLabelSyntax); +``` + +The input parameter **nEDCNAddress** identifies a DCN address to be used to access this NE. The NE should already have been configured with this address. The input parameter **nEUserLabel** provides an operator defined label for the NE. The NE should already have been provisioned with the User Label. The input parameter **administrationDomain** identifies the management domain to which this NE is assigned. + +The return value of type **ManagedEntityIdType** identifies the newly registered NE if this operation completes successfully. + +#### 9.10.1.2 modifyNEDCNAddress + +This operation changes the DCN address of a registered NE. Communications may be temporarily lost between Supplier Management System and NE during this operation. The new DCN address should take effect immediately. + +The operation signature for **modifyNEDCNAddress** is shown below: + +``` +void modifyNEDCNAddress ( + in ManagedEntityIdType nEManagedEntityId, + in DCNAddressType newNEDCNAddress) + raises (AccessDenied, DeniedAccess, AddressLabelMismatch, + DCNTimeout, CommFailure, UnknownNE, InvalidDCNAddress, BackupInProgress); +``` + +The input parameter **nEManagedEntityId** identifies the NE to which this operation applies. The input parameter **newDCNAddress** identifies the new DCN address for the NE. + +The return value is of type **void**. + +#### 9.10.1.3 rangeONTorONU + +This operation ranges an ONT or ONU using the serial number of the PON interface of the NE. If the NE being ranged has not been built, then buildNode will be called before ranging occurs. After the ranging has completed successfully a NE synch is initiated. This will update the Supplier Management System with the configuration data from the newly ranged NE. + +The operation signature for **rangeONTorONU** is shown below: + +``` +ManagedEntityIdType rangeONTorONU ( + in ManagedEntityIdType oLTManagedEntityId, + in UserLabelType nEUserLabel, + in SerialNumType serialNum, + in ManagedEntityIdType port) + raises (AccessDenied, CommFailure, EquipmentFailure, UnknownNE, +``` + +``` +UnknownPort, MaxSubtendingNodesExceeded, InsufficientPONBW, +InvalidSerialNumSyntax, APONLayerFailure, DuplicateUserLabel, +InvalidUserLabelSyntax, BackupInProgress, SynchInProgress ); +``` + +The input parameter **oLTManagedEntityId** identifies the OLT to which this operation applies. The input parameter **neUserLabel** is a label given to the NE to be ranged. The input parameter **serialNum** identifies the NE serial number. The input parameter **port** identifies the specific PON port on the OLT where the NE is to be ranged. + +The return value of type **ManagedEntityIdType** is the managed entity id of the ranged NE. + +#### 9.10.1.4 rangeReplacementNE + +This operation ranges a replacement ONT or ONU using the serial number of the replacement equipment. All existing service connection information is automatically assigned to the replacement NE. Replacement scenarios occur due to maintenance activities for existing customers and services. The old and new NE User Label can be the same. Outside the scope of IF1 the supplier and the operator have come to an understanding of what type of hardware may replace any existing hardware. + +The operation signature for **rangeReplacementNE** is shown below: + +``` +ManagedEntityIdType rangeReplacementNE( + in ManagedEntityIdType oldNEManagedEntityId, + in UserLabelType newNEUserLabel, + in SerialNumType replacementSerialNum) + raises (AccessDenied, CommFailure, UnknownNE, + InvalidSerialNumSyntax, APONLayerFailure, EquipmentFailure, + InvalidUserLabelSyntax, HWServicesMismatch, DuplicateUserLabel, + BackupInProgress, SynchInProgress ); +``` + +The input parameter **oldNEManagedEntityId** identifies the NE to be replaced. The input parameter **newNEUserLabel** identifies a label for the new ONT or ONU to be ranged. The input parameter **replacementSerialNum** identifies the NE serial number. + +The return value of type **ManagedEntityIdType** is the managed entity id of the newly ranged NE. + +#### 9.10.1.5 rangeUpgradeNE + +This operation ranges a replacement NE for the purposes of upgrading the hardware. All existing service connection information is automatically assigned to the replacement NE. Additionally, it is assumed that the replacement NE has been preprovisioned (using buildNode operation) and any new service connections have been provisioned or bandwidth has been reserved. The new NE User Label can be the same as the old. Outside the scope of IF1 the supplier and the operator have come to an understanding of what type of hardware may replace any existing hardware. + +The operation signature for **rangeUpgradeNE** is shown below: + +``` +ManagedEntityIdType rangeUpgradeNE( + in ManagedEntityIdType oldNEManagedEntityId, + in ManagedEntityIdType newNEManagedEntityId, + in UserLabelType newNEUserLabel, + in SerialNumType newNESerialNum ) + raises (AccessDenied, CommFailure, APONLayerFailure, + EquipmentFailure, InvalidUserLabelSyntax, DuplicateUserLabel, + UnknownNE, HWServicesMismatch, InsufficientPONBW, + BackupInProgress, SynchInProgress ); +``` + +The input parameter **oldNEManagedEntityId** identifies the NE being replaced. In this case, the type of NE being replaced is either an ONT or an ONU. The input parameter **newNEManagedEntityId** identifies the preprovisioned replacement. All new service connection or bandwidth reservation information is accessible to the Supplier Management System through this + +identifier. The input parameter **newNEUserLabel** provides a label for the new NE to be ranged. The old and new ONU or ONT User Label can be the same. The input parameter **newNESerialNum** provides the serial number to be used for ranging the replacement. + +The return value of type **ManagedEntityIdType** is the managed entity id of the newly ranged NE. + +#### 9.10.1.6 moveONTorONU + +This operation is used to move an ONT or ONU from one PON to another and also to move all of the associated services. + +The operation signature for **moveONTorONU** is shown below: + +``` +ManagedEntityIdType moveONTorONU( + in ManagedEntityIdType oldNEManagedEntityId, + in ManagedEntityIdType newPONPort) + raises (AccessDenied, CommFailure, UnknownNE, UnknownPort, + APONLayerFailure, EquipmentFailure, InsufficientPONBW, + BackupInProgress, SynchInProgress ); +``` + +The input parameter **oldNEManagedEntityId** identifies the NE to be replaced. The input parameter **newPONPort** identifies the new PON to which these services are being moved. + +The return value of type **ManagedEntityIdType** is the managed entity id of the newly ranged NE. + +#### 9.10.1.7 getSubtendingNEList + +This operation returns all subtending NEs of a particular NE. + +The operation signature for **getSubtendingNEList** is shown below: + +``` +ManagedEntityIdSeqType getSubtendingNEList( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, AccessDenied); +``` + +The input parameter **nEManagedEntityId** identifies the specific NE for which the list should be returned. + +The return value of type **ManagedEntityIdSeqType** provides a list of subtending network elements. + +#### 9.10.1.8 nEListGet + +This operation retrieves the network elements under the management jurisdiction of the Supplier Management System. + +The operation signature of **nEListGet** is provided below: + +``` +ManagedEntityIdSeqType nEListGet () raises (AccessDenied); +``` + +There are no input parameters. + +The return value is of type **ManagedEntityIdSeqType** which provides the list of network elements managed by the Supplier Management System. + +#### 9.10.1.9 deRegisterNE + +This operation removes the network element from the management jurisdiction of the Supplier Management System. + +The operation signature of **deRegisterNE** is provided below: + +``` +void deRegisterNE ( + in ManagedEntityIdType nE) + raises (AccessDenied); +``` + +The input parameter **nE** identifies the network element to remove from the management jurisdiction of the Supplier Management System. + +The return value is of type **void**. + +#### 9.10.1.10 **associateNE** + +This operation associates preprovisioning information with a network element that has been installed and autodiscovered. The activities of preprovisioning and installation both produce a managed entity within the Supplier Management System that is made available to the OMS. This operation unifies the two managed entities into one. + +The operation signature of **associateNE** is provided below: + +``` +ManagedEntityIdType associateNE ( + in ManagedEntityIdType preProvisionedNE, + in ManagedEntityIdType discoveredNE) + raises (AccessDenied, UnknownManagedEntity); +``` + +The input parameter **preProvisionedNE** identifies the information associated with the preprovisioned network element. The input parameter **discoveredNE** identifies the information associated with the installed network element. + +The return value of type **ManagedEntityIdType** provides the identification of the merged information. + +#### 9.10.1.11 **Exceptions** + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **AddressLabelMismatch** is raised when the identified NE does not have the current DCN Address provided in the request. + +The exception **APONLayerFailure** is raised when there was an APON protocol ranging failure between the OLT and the designed subtending node. + +The exception **BackupInProgress** is raised when the cancellation request is issued while the backup is in progress. + +The exception **CommFailure** is raised when the DCN between Supplier Management System and OLT or the communication between OLT and source ONT is down. + +The exception **DCNTimeout** is raised when the DCN communications link between at least one of the NEs and the Supplier Management System is so congested that current state or status information cannot be transferred within a system defined synch time. + +The exception **DeniedAccess** is raised if the access to NE is denied as a result of access control restrictions. + +The exception **DuplicateUserLabel** is raised if the User Label provided in the request has been used to label another NE or plugInUnit. In other words, the Supplier Management System is responsible for policing User Labels assigned for NEs and plug-in units within its management jurisdiction. + +The exception **EquipmentFailure** is raised when the equipment where the data is backed up from is in failure condition. + +The exception **HWServicesMismatch** is raised when the replacement NE cannot perform the provisioned services. + +The exception **InsufficientPONBW** is raised when the ONT or ONU cannot be ranged due to insufficient bandwidth on the APONLink. + +The exception **InvalidDCNAddress** is raised when the specified DCN address is not valid. + +The exception **InvalidSerialNumSyntax** is raised when the Syntax of the serial number provided does not match definition rules. + +The exception **InvalidUserLabelSyntax** is raised when the User Label provided for the ONU or ONT violates business rules of syntax defined by the operator and implemented in the Supplier Management System. + +The exception **MaxSubtendingNodesExceeded** is raised when the maximum engineered number of subtending nodes for the identified PON interface has been exceeded with this request for service provisioning. + +The exception **SynchInProgress** will be raised when any operation is requested while the Supplier Management System is in the process of synchronising with the NE. + +The exception **TooManyNEs** is raised when the Supplier Management System cannot manage one more OLT. + +The exception **UnknownManagedEntity** is raised when the equipment is unknown to the Supplier Management System. + +The exception **UnknownNE** is raised when the OLT is unknown to the Supplier Management System. + +The exception **UnknownPort** is raised when the identified port is unknown to the Supplier Management System. + +## 9.11 ResourceAllocation module + +This service allows the OMS to reserve bandwidth on a system resources for an anticipated service connection. The reserved bandwidth can be deleted or retrieved. The ResourceAllocator interface provides the means for creating, deleting, or displaying a resource reservation. This operation is used prior to dispatch of personnel for the installation of a network element. Once resource capacity is reserved, the reserved resource can be used only for the service specified in the reservation. + +### 9.11.1 ResourceAllocator Interface + +#### 9.11.1.1 reserveForService + +This operation reserves bandwidth for a network resource such as ONT, ONU, or NT whose installation is pending. This operation is used when the ONT, ONU, or NT that serves the bandwidth associated with the designated OLT is first provisioned. When the operation is completed, the return value, **ReservationBandwidthType**, provides an accounting of the reserved bandwidth to the OMS. + +The operation signature for the **reserveForService** is shown below: + +``` +ReservationBandwidthType reserveForService( + in EndPointType endPointA, + in EndPointType endPointZ, + in NameSeqType networkCharacteristicsProfiles, + in ServiceInstanceIdType serviceInstanceId) +raises(UnknownNE, UnknownPort, UnknownProfiles, +InsufficientBW, MaxSubtendingNodesExceeded, +ConnectionCountExceeded, CommFailure, AccessDenied, +ProfileSuspended ); +``` + +The input parameters **endPointA** and **endPointZ** identify the two endpoints of the service connection that will determine the resources necessary to support an anticipated service connection. The input parameter **networkCharacteristicsProfiles** is a list consisting of the following; abTrafficDescriptorProfile, and baTrafficDescriptorProfile (in this order). The input parameter **serviceInstanceId** identifies the associated service instance for this reserved bandwidth. + +The return value is of type **ReservationBandwidthType** and includes a Reservation Id and the amount of network resource bandwidth that has been reserved by the Supplier Management System. The Reservation Id can be used by the OMS during service provisioning or to cancel this reservation. + +#### 9.11.1.2 **cancelReservation** + +This operation is used to delete the reservation and release the resources from the reserved system capacity. + +The operation signature for the **cancelReservation** is shown below: + +``` +AvailableSysBandwidthSeqType cancelReservation ( + in ReservationIdType reservationId ) + raises (UnknownReservationId, CommFailure, AccessDenied); +``` + +The input parameter **reservationId** identifies the existing reservation associated with the bandwidth that was allocated. + +The return value of type **AvailableSysBandwidthSeqType** indicates the current available bandwidth of the OLT after the deletion of the reserved bandwidth. + +#### 9.11.1.3 **getReservationId** + +This operation is used to display the reservation Id associated with the service instance id that is assigned for the reserved bandwidth. + +The operation signature for the **getReservationId** is shown below: + +``` +ReservationIdType getReservationId ( + in ServiceInstanceIdType serviceInstanceId) + raises (UnknownServiceInstance, AccessDenied); +``` + +The input parameter **serviceInstanceId** is used to identify the existing service instances assigned during the time the resource is reserved. + +The return value of type **ReservationIdType** is associated with the given service instance id. + +#### 9.11.1.4 **reportReservedResources** + +This operation is used by the OMS to display the current reserved bandwidth in the specific headend NE (in this case the OLT). + +The operation signature for the **reportReservedResources** is shown below: + +``` +ReservedBandwidthSeqType reportReservedResources ( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, AccessDenied); +``` + +The input parameter **nEManagedEntityId** is used to identify the network element for which current bandwidth reservations are requested. + +The return value of type **ReservedBandwidthSeqType** has the all current reserved bandwidth information for the network element. + +#### 9.11.1.5 **getReservations** + +This operation is used by OMS to retrieve all the reservations associated with the given NE. + +The operation signature for the **getReservations** is shown below: + +``` +ReservationIdSeqType getReservations( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, AccessDenied); +``` + +The input parameter **nEManagedEntityId** is used to identify the NE for retrieval of the current reserved bandwidth. + +The return value of type **ReservationIdSeqType** provides all the reservation id(s) currently allocated to the OLT. + +#### 9.11.1.6 **cancelAllRemainingReservations** + +This operation is used to delete all the remaining reservations against capacity associated with a given network element. The network element can have bandwidth that is either assigned, reserved, or available for service connections. This operation only changes reserved resources to available resources. + +The operation signature for the **cancelAllRemainingReservations** is shown below: + +``` +AvailableSysBandwidthSeqType cancelAllRemainingReservations ( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, CommFailure, AccessDenied); +``` + +The input parameter **nEManagedEntityId** is used to identify the network element. + +The return value of type **AvailableSysBandwidthSeqType** indicates the current available bandwidth of the network element after the deletion of the reserved bandwidth. + +#### 9.11.1.7 **getReservation** + +This operation is used to investigate the origins of a reservation of capacity within an NE. + +The operation signature for the **getReservation** is shown below: + +``` +ReservationInfoType getReservation ( + in ReservationIdType reservationId) + raises (UnknownReservationId, AccessDenied); +``` + +The input parameter **reservationId** is used to specify the reservation. + +The return value of type **ReservationIdInfoType** indicates the service connection information provided as part of the reservation request with the provided **reservationId**. + +#### 9.11.1.8 **getAvailableSysBandwidth** + +This operation is used to determine the amount of capacity remaining for service connection reservation or assignment for a network element. + +The operation signature for the **getAvailableSysBandwidth** is shown below: + +``` +AvailableSysBandwidthSeqType getAvailableSysBandwidth ( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, CommFailure, AccessDenied); +``` + +The input parameter **nEManagedEntityId** is used to identify the network element. + +The return value of type **AvailableSysBandwidthSeqType** indicates the current available bandwidth of the network element. It provides the available bandwidth for each provisioned port on the network element as characterized by the supplier implementation. + +#### 9.11.1.9 **Exceptions** + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **CommFailure** is raised when the DCN between Supplier Management System and OLT or the communication between OLT and ONT or ONU is down. + +The exception **ConnectionCountExceeded** is raised when the maximum number of connections for the OLT or PON port has been exceeded with this request for service provisioning. + +The exception **InsufficientBW** is raised when the bandwidth is insufficient to the requested service. + +The exception **MaxSubtendingNodesExceeded** is raised when the maximum engineered number of subtending nodes for the identified PON interface has been exceeded with this request for service provisioning. + +The exception **ProfileSuspended** is raised when a profile(s) named in the invocation has been suspended for use within the Supplier Management System by the OMS or operator. + +The exception **UnknownNE** is raised when the OLT is unknown to the Supplier Management System. + +The exception **UnknownPort** is raised when the identified port is unknown to the Supplier Management System. + +The exception **UnknownProfiles** is raised if the profile name provided is unknown to the Supplier Management System and cannot be retrieved from the profile object repository. + +The exception **UnknownReservationId** is raised when the Supplier Management System does not recognize this Reservation Id. + +The exception **UnknownServiceInstance** is raised when the service instance is unknown to the Supplier Management System. + +## 9.12 SchedulerManagement module + +This service is used to provide OMS interfaces for managing schedulers to be used for invoking various activities. Once the scheduler is created, the OMS can initiate requests to schedule an activity such as NE MIB uploading, bulk transfer, testing, or software downloading by referencing the scheduler. Schedulers are determined by needs of the operations environment. It is assumed that there will be no schedulers named or established automatically upon instantiation of the Supplier Management System. References to a specific scheduler will always be made via User Label. A trigger matrix is used to describe the schedule. The values in the matrix are interpreted based on the value of HourlyDailyWeeklyMonthlyInd. + +### 9.12.1 SchedulerMgr interface + +#### 9.12.1.1 makeScheduler + +This operation creates a new scheduler object. The OMS can then associate activities with the scheduler object by referencing the User Label name of the scheduler. + +The operation signature for the **makeScheduler** is shown below: + +``` +void makeScheduler ( + in UserLabelType schedulerName, + in GeneralizedTimeType startTime, + in GeneralizedTimeType stopTime, + in HourlyDailyWeeklyMonthlyIndType hourlyDailyWeeklyMonthlyInd, + in TriggerTimeMatrixSeqType matrix) + raises (InvalidStartTime, InvalidStopTime, DuplicateUserLabel, + MatrixSchedulerTypeMismatch, AccessDenied, InvalidTrigger); +``` + +The input parameter **schedulerName** identifies the scheduler which can be referenced by different activities. The input parameters **startTime** and **stopTime** identify the time range in which the scheduled activiti[es] is[are] applicable. The input parameter **hourlyDailyWeeklyMonthlyInd** indicates the frequency (hourly, daily, weekly or monthly) with which the schedule should be triggered. The input parameter **matrix** provides specific schedule invocation information and is affected by the **hourlyDailyWeeklyMonthlyInd** parameter value. + +Table 4 below provides a table showing the dependency of **hourlyDailyWeeklyMonthlyInd** and **matrix**: + +**Table 4/Q.834.4 – Matrix details** + +| hourlyDailyWeeklyMonthlyInd value | matrix value | +|------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| Hourly | time – Any value between 0 and 3600 7
dayOfWeek – must be 'unspecified'
dayOfMonth – must be 0 | +| Daily | time – Any value between 0 and 86400 8
dayOfWeek – must be 'unspecified'
dayOfMonth – must be 0 | +| Weekly | Time – Any value between 0 and 86400
dayOfWeek – different from 'unspecified'
dayOfMonth – must be 0 | +| Monthly | Time – Any value between 0 and 86400
dayOfWeek – must be 'unspecified'
dayOfMonth – different from 0 | + +The return value is of type **void**. + +#### **9.12.1.2 suspendScheduler** + +This operation is used to suspend a schedule. It essentially sets the schedule's administrativeState from 'unlocked' to 'locked'. This will be applicable starting from the next schedule iteration. This operation causes any associated scheduled activity to be suspended. + +The operation signature for the **suspendScheduler** is shown below: + +``` +void suspendScheduler ( + in UserLabelType schedulerName) + raises (UnknownScheduler, AccessDenied); +``` + +The input parameter **schedulerName** is used to identify the schedule to be suspended. + +The return value is of type **void**. + +#### **9.12.1.3 resumeScheduler** + +This operation is used to resume a suspended schedule. It essentially sets the schedule's administrativeState from 'locked' to 'unlocked'. This will be applicable starting with the next schedule iteration. This operation causes any associated scheduled activity to be resumed. + +The operation signature for the **resumeScheduler** is shown below: + +``` +void resumeScheduler ( + in UserLabelType schedulerName) + raises (UnknownScheduler, AccessDenied ); +``` + +The input parameter **schedulerName** is used to identify the schedule to be resumed. + +The return value is of type **void**. + +7 Represents the number of seconds from the beginning of the hour for the trigger time. + +8 Represents the number of seconds from the beginning of the day for the trigger time where the day begins after midnight. + +#### 9.12.1.4 modifyTime + +This operation is used in order to change the **startTime** and **stopTime** of a schedule. It is used by the OMS to extend or to shorten the time range in which the schedule is applicable. + +The operation signature for the **modifyTime** is shown below: + +``` +void modifyTime ( + in UserLabelType schedulerName, + in GeneralizedTimeType newStartTime, + in GeneralizedTimeType newStopTime) + raises (InvalidStartTime, InvalidStopTime, UnknownScheduler, + AccessDenied); +``` + +The input parameter **schedulerName** is used to identify the schedule. The input parameter **newStartTime** provides the time at which this scheduler starts and the input parameter **newStopTime** provides the time at which the scheduler stops. If the value of newStartTime is earlier than the current system time, the exception InvalidStartTime will be raised. A value of 0 for either **newStartTime** or **newStopTime** indicates that the previous value should not be changed. + +The return value is of type **void**. + +#### 9.12.1.5 changeSchedulerName + +This operation is used to change the name of the scheduler object. Upon success of this operation, the new scheduler name will immediately be applicable. Any reference to this schedule will have to be made using the newly assigned name. + +Many activities can be associated with the same scheduler name. Changing the scheduler name will not affect the activities associated with the scheduler. All activities associated with the changed scheduler will maintain their association. + +The operation signature for **changeSchedulerName** is shown below: + +``` +void changeSchedulerName ( + in UserLabelType oldSchedulerName, + in UserLabelType newSchedulerName) + raises (UnknownScheduler, DuplicateUserLabel, AccessDenied); +``` + +The input parameter **oldSchedulerName** is used to identify the existing schedule. The input parameter **newSchedulerName** is used to indicate the new name to assign for this scheduler. + +The return value is of type **void**. + +#### 9.12.1.6 modifyTriggerTimes + +This operation is used by the OMS to specify new trigger times and iteration for a scheduler9. If this operation is successful, then any associated scheduled activity will occur at the new schedule times starting from the next schedule iteration. + +The operation signature for the **modifyTriggerTimes** is shown below: + +``` +void modifyTriggerTimes ( + in UserLabelType schedulerName, + in HourlyDailyWeeklyMonthlyIndType newHourlyDailyWeeklyMonthlyInd, + in TriggerTimeMatrixSeqType newMatrix) + raises (UnknownScheduler, MatrixSchedulerTypeMismatch, + InvalidTrigger, AccessDenied ); +``` + +The input parameter **schedulerName** is used to identify the schedule to be modified. The input parameter **newHourlyDailyWeeklyMonthlyInd** indicates the new frequency with which the + +--- + +9 Please refer to makeScheduler operation for details on the dependency of used variables. + +schedule should be triggered. The input parameter **newMatrix** is used to provide the new specific schedule invocation information. Please refer to Table 4 for dependency of the variables. Both **newDailyWeeklyMonthlyInd** and **newMatrix** must be explicitly specified. + +The return value is of type **void**. + +#### 9.12.1.7 removeScheduler + +This operation is used to delete a scheduler. This operation will be allowed only if there are no activities associated with this scheduler. + +The operation signature for the **removeScheduler** is shown below: + +``` +void removeScheduler ( + in UserLabelType schedulerName) + raises (UnknownScheduler, AccessDenied, ScheduleInUse ); +``` + +The input parameter **schedulerName** is used to identify the schedule to be deleted. + +The return value is of type **void**. + +#### 9.12.1.8 retrieveScheduler + +This operation is used to retrieve information on the schedule. The schedule object will be returned upon successful invocation of this operation. + +The operation signature for the **retrieveScheduler** is shown below: + +``` +SchedulerType retrieveScheduler ( + in UserLabelType schedulerName) + raises (UnknownScheduler, AccessDenied); +``` + +The input parameter **schedulerName** is used to identify the schedule to be displayed. + +The return value of type **Scheduler** provides the following information: schedulerName; startTime; stopTime; hourlyDailyWeeklyMonthlyInd; matrix; operationalState and administrativeState. + +#### 9.12.1.9 schedulerListGet + +This operation is used to retrieve the names of all existing schedulers defined for the Supplier Management System. + +The operation signature for the **schedulerListGet** is shown below: + +``` +SchedulerSeqType schedulerListGet ( + raises (AccessDenied); +``` + +There are no input parameters. + +The return value is of type **SchedulerSeqType** and provides the listing desired. + +#### 9.12.1.10 Exceptions + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **DuplicateUserLabel** is raised if the User Label provided in the request has been used to label another Scheduler. In other words, the Supplier Management System is responsible for policing User Labels assigned for schedulers within its management jurisdiction. + +The exception **InvalidStartTime** is raised when the specified start time is inconsistent with the current trigger time matrix or the stop time. + +The exception **InvalidStopTime** is raised when the specified stop time is inconsistent with the current trigger time matrix or the start time. + +The exception **InvalidTrigger** is raised when the specified Trigger has values that cannot be interpreted by the Scheduler. + +The exception **MatrixSchedulerTypeMismatch** is raised when the syntax for the Trigger Time Matrix is mismatched with the type of scheduler named. + +The exception **ScheduleInUse** will be returned from removeScheduler operation in case there are operations associated with the schedule. + +The exception **UnknownScheduler** is raised when the given scheduler name is not found. + +## 9.13 ServiceProvisioning module + +In this module, the Supplier Management System selects ports, facilities and bandwidth in order to be able to complete the design, selection and assignment process associated with a service. + +### 9.13.1 ServiceProvisioner interface + +#### 9.13.1.1 provisionConnection + +This operation provisions a connection between any two endpoints of a BPON fibre access system. A connection may be established between an NNI and a UNI, between two UNIs, or between two NNIs. Figure 1 illustrates these endpoints. + +The operation signature for **provisionConnection** is shown below: + +``` +ManagedEntityIdType provisionConnection( + in EndpointType endPointA, + in EndpointType endPointZ, + in NameSeqType networkCharacteristicsProfiles, + in ServiceInstanceIdType serviceInstanceId, + in AdministrativeStateType administrativeState) + raises (UnknownNE, UnknownProfiles, UnknownPort, InsufficientBW, + ConnectionCountExceeded, CommFailure, EquipmentFailure, + ParameterViolation, AccessDenied, InsufficientPONBW, + ProfileSuspended, ConnectionAlreadyExists); +``` + +The input parameters **endPointA** and **endPointZ** identify the two endpoints of the connection request. An endpoint is defined by the data structure provided in Table 5. + +**Table 5/Q.834.4 – Endpoint details** + +| Field name | Definition | Syntax | Comments | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| portId | Specifies the physical port containing one end point of the connection. | ManagedEntityType | The assumption is that this is the physicalPathTP Managed Entity for the port. | +| endPointParameters | Identifies service instance specific parameters assisting in the joining together of network connection components. | any | Structures to be provided as part of implementation. An ATM connection, for example, would have the VPI, VCI parameters. | +| serviceCharacteristicsProfile | Lists references to profiles characterizing the service at the endpoint. | NameSeqType | Examples are AAL1Profile, AAL5Profile, ATMNetworkAccess Profile, UNIPProfile, CESServiceProfile, DS1Profile, DS3Profile, EthernetProfile, AAL2Profile, LESProfile, SSCSPParameter Profile1, SSCSPParameter Profile2, VoiceService ProfileAAL2, BridgedLAN ServiceProfile, MACBridgeService Profile. (Note) | +| NOTE – Specific choices depend on service and equipment characteristics. Profiles are listed by the names provided in the module Q834ProfileManager. See Annex D for example relationships. | | | | + +The input parameter **networkCharacteristicsProfiles** provides the list of transport related profiles to be used for service provisioning including azTrafficDescriptorProfile and zaTrafficDescriptorProfile. The az Traffic Descriptor Profiles are listed before the za in the listing. The parameter **serviceInstanceId** indicates the service instance identifier to be used as the key when referring to network resources associated with the service. The input parameter **administrativeState** specifies whether or not the subnetwork connection is able to carry subscriber traffic once this operation is executed. + +The return value of type **ManagedEntityType** is a managed entity identifier to identify the subnetworkConnection created as the result of this request. + +#### 9.13.1.2 provisionReservation + +This operation provisions service between the NNI of an OLT and the UNI of an ONT or between two UNIs based on an outstanding reservation. Once the service connection is provisioned, the reserved bandwidth and associated reservation Id is removed from the Supplier Management System because the reserved resources are assigned. + +The operation signature for **provisionReservation** is shown below: + +``` +ManagedEntityIdType provisionReservation( + in ReservationIdType reservationId, + in AdministrativeStateType administrativeState) + raises ( UnknownReservationId, AccessDenied); +``` + +The input parameter **reservationId** specifies the reservation Id. It points to all the other information (such as service instance Id and endpoints) to associate with the provisioned connection. The input parameter **administrativeState** specifies whether or not the subnetwork connection is able to carry subscriber traffic once this operation is executed. + +The return value of type **ManagedEntityIdType** is a managed entity identifier to identify the subnetworkConnection created as the result of this request. + +#### 9.13.1.3 deleteConnection + +The operation tears down the existing service and connections. + +The operation signature for **deleteConnection** is shown below: + +``` +void deleteConnection( + in ManagedEntityIdType subnetworkConnectionId) + raises (UnknownConnection, CommFailure, EquipmentFailure, + AccessDenied); +``` + +The input parameter **subnetworkConnectionId** is the subnetwork that was created previously via service provisioning request. + +The return value is of type **void**. + +#### 9.13.1.4 modifyConnection + +This operation provides the capability to modify the existing service. + +The operation signature for **modifyConnection** is shown below: + +``` +ManagedEntityIdType modifyConnection ( + in ManagedEntityIdType subnetworkConnectionId, + in ManagedEntityIdType portB, + in NameSeqType newNetworkCharacteristicsProfiles, + in NameSeqType newServiceCharacteristicsProfiles) + raises (UnknownConnection, UnknownProfiles, InsufficientBW, + UnknownPort, AccessDenied, ProfileSuspended ); +``` + +The input parameter **subnetworkConnectionId** is the subnetwork that was created previously via service provisioning request. The input parameter **portB** helps to clarify the directionality of the traffic descriptor profiles named in the next input parameter as well as to specify where the service profiles are meant to be applied. This port is either the A or Z port of the original connection request. The input parameter **newNetworkCharacteristicsProfiles** provides the modified list of network related profiles to be used for service provisioning where "b-to-opposite endpoint" traffic descriptor profiles are listed before "the opposite endpoint-to-b" traffic descriptor profiles. The input parameter **newServiceCharacteristicsProfiles** provides the new list of service related profiles. + +The return value of type **ManagedEntityIdType** is a managed entity identifier to identify the subnetworkConnection created as the result of this request. + +#### 9.13.1.5 suspendService + +This operation disables the flow of user traffic through the service subnetwork connection. In effect, suspension of service is equivalent to locking the administrative state of the subnetwork connection. + +The operation signature for **suspendService** is shown below: + +``` +void suspendService ( + in ServiceInstanceIdType serviceInstanceId, + in GeneralizedTimeType startTime, + in GeneralizedTimeType stopTime) + raises (UnknownServiceInstance, AccessDenied, InvalidStartTime, + InvalidStopTime); +``` + +The input parameter **serviceInstanceId** identifies the service connection to be suspended. The input parameter **startTime** provides the time point at which the service is to be suspended. The input parameter **stopTime** provides the time point at which the service is to be resumed. + +The return value is of type **void**. + +#### 9.13.1.6 resumeService + +This operation enables the flow of user traffic through the service subnetwork connection. This operation can be invoked either after service has been suspended (see operation above) or if the original service connection is configured in an inactive state. The service is to be resumed immediately. + +The operation signature for **resumeService** is shown below: + +``` +void resumeService ( + in ServiceInstanceIdType serviceInstanceId) + raises (UnknownServiceInstance, AccessDenied); +``` + +The input parameter **serviceInstanceId** identifies the service connection to be resume. + +The return value is of type **void**. + +#### 9.13.1.7 Exceptions + +The exception **AccessDenied** is raised when the NE access is denied due to a security reason. + +The exception **CommFailure** is raised when communication between the Supplier Management System and NEs failed. + +The exception **ConnectionAlreadyExists** is raised when there already exists a subnetwork connection with the same endpoints. + +The exception **ConnectionCountExceeded** is raised when the connection count exceeds the allowable connection count. + +The exception **EquipmentFailure** is raised when the connection requested cannot be applied to an installed network resource because of the failure condition of the NE. + +The exception **InsufficientBW** is raised when the bandwidth is insufficient to the requested service. + +The exception **InsufficientPONBW** is raised when the available PON bandwidth is not sufficient to support the requested service provisioning. + +The exception **InvalidStartTime** is raised when the specified start time is inconsistent with the current time or the stop time. + +The exception **InvalidStopTime** is raised when the specified stop time is inconsistent with the current time or the start time. + +The exception **ParameterViolation** is raised when the endpoint parameters do not match the protocol characteristics of the port, or if the value(s) are out of range or invalid duplicates. + +The exception **ProfileSuspended** is raised when a profile(s) named in the invocation has been suspended for use within the Supplier Management System by the OMS or operator. + +The exception **UnknownConnection** is raised when the connection to be deleted is not found. + +The exception **UnknownNE** is raised when the OLT name is not known to the Supplier Management System. + +The exception **UnknownPort** is raised when the input port id is not known to the Supplier Management System. + +The exception **UnknownProfiles** is raised if the profile name provided is unknown to the Supplier Management System and cannot be retrieved from the profile object repository. + +The exception **UnknownReservationId** is raised when the reservation identifier is not known to the Supplier Management System. + +The exception **UnknownServiceInstance** is raised when the service identifier is not known to the Supplier Management System. + +## 9.14 Synchroniser module + +This module manages the synchronisation process between the Supplier Management System and a specific NE. The requested synchronisation process can be narrowed to a specific set of current event listings. The details on how inconsistencies are detected and what data is retrieved is up to the suppliers implementation. However, this process results in the removal of any inconsistencies between the management information found with the NE and the information model maintained in the Supplier Management System. + +The operations in this module can only be invoked by a privileged user. The synchronisation process is "best effort" in the sense that any inconsistencies detected and corrected prior to a system defined timeout period10 are preserved. The synchronisation process may impact the performance of the Supplier Management System in a negative way prior to its completion. + +When the network element chosen is an OLT, then the synchronisation process is system-wide. + +### 9.14.1 NESynchroniser interface + +#### 9.14.1.1 synchNE + +This operation initiates a synchronisation process between the Supplier Management System and a specific NE. This operation is blocking only as long as it takes for the Supplier Management System to validate that the process can be initiated, and performs the synchronisation operation in the background. + +The operation signature for **synchNE** is shown below: + +``` +void synchNE(in ManagedEntityIdType nEManagedEntityId) + raises (AccessDenied, CommFailure, UnknownNE, EquipmentFailure, + BackupInProgress, SynchInProgress); +``` + +The input **nEManagedEntityId** identifies NE to synchronise with the Supplier Management System. + +--- + +10 This timeout period is a matter of agreement between the Operator and the Supplier. + +The return value is of type **void**. + +#### 9.14.1.2 abortSynchNE + +This operation aborts a synchronisation process in progress between the Supplier Management System and a specific NE. Any inconsistencies between the Supplier Management System and the NE that have been resolved before the abort are retained. + +The operation can only be invoked by a privileged user. + +The operation signature for **abortSynchNE** is shown below: + +``` +void abortSynchNE( + in ManagedEntityIdType nEManagedEntityId) + raises (AccessDenied, CommFailure, UnknownNE, EquipmentFailure, + NoSynchInProgress); +``` + +The input **nEManagedEntityId** identifies the NE whose synchronisation with the Supplier Management System is to be aborted. + +The return value is of type **void**. + +#### 9.14.1.3 scheduleSynchNE + +This operation schedules a synchronisation process between the Supplier Management System and a specific NE. The scheduled synchronisation process is triggered by the scheduler which is predefined by the operator. At most, one scheduler can be associated with this activity for a specific NE. + +The operation signature for **scheduleSynchNE** is shown below: + +``` +void scheduleSynchNE( + in ManagedEntityIdType nEManagedEntityId, + in UserLabelType schedulerName) + raises (AccessDenied, UnknownNE, UnknownScheduler, InvalidScheduler); +``` + +The input **nEManagedEntityId** identifies the NE to synchronise with the Supplier Management System. The input **schedulerName** identifies scheduler to be used to invoke scheduled synchronisation operation of Supplier Management System. + +The return value is of type **void**. + +#### 9.14.1.4 modifyNESynchSchedule + +This operation modifies the schedule for NE synchronisation. This operation will not interrupt a synchronisation process in progress. If successful, the new schedule is applied with the next iteration. + +The operation signature for **modifyNESynch** is shown below: + +``` +void modifyNESynchSchedule( + in ManagedEntityIdType nEManagedEntityId, + in UserLabelType newSchedulerName) + raises (AccessDenied, UnknownNE, UnknownScheduler, + InvalidScheduler); +``` + +The input **nEManagedEntityId** identifies the NE where the scheduled NE synchronisation is activated. The input **newSchedulerName** identifies the schedule to be applied. + +The return value is of type **void**. + +#### 9.14.1.5 cancelScheduledSynchNE + +This operation cancels all subsequent scheduled synchronisation processes for this NE. This operation will not interrupt a synchronisation process in progress. + +The operation signature for **cancelScheduledSynchNE** is shown below: + +``` +void cancelScheduledSynchNE( + in ManagedEntityIdType nEManagedEntityId ) + raises (AccessDenied, UnknownNE); +``` + +The input **nEManagedEntityId** identifies the NE where the scheduled NE synchronisation is activated. + +The return value is of type **void**. + +#### 9.14.1.6 synchCurrentEventListings + +The operation initiates synchronisation between the Supplier Management System and specified NE for items in particular current event listings. The Supplier Management System normally retrieves current values of state, status, or management attributes and tracks these via current summary event listings for the system. If any automatic system retrieval process shows that the listing is not up-to-date with the current conditions of the system, then the listing is modified (through deletion of an entry or insertion of a new entry) in order to correct the listing. This operation is a manual version driven by OMS request. While this operation is in effect, the exception **SynchInProgress** for any other operation may not be invoked. + +The operation signature for **synchCurrentEventListings** is shown below: + +``` +void synchCurrentEventListings( + in ManagedEntityIdType nEManagedEntityId, + in CurrentListingSeqType currentListingTypeList) + raises (AccessDenied, CommFailure, DCNTimeout, UnknownNE, + EquipmentFailure, Timeout); +``` + +The input **nEManagedEntityId** identifies the NE for synchronisation. The input **currentListingTypeList** identifies the list of current event that are to be synchronised between the Supplier Management System and the specified NE. The Supplier Management System retrieves the specified current event listing values from NE. + +The return value is of type **void**. + +#### 9.14.1.7 scheduledSynchNEListGet + +This operation is used to retrieve the names of all NEs with synchronisation schedules. + +The operation signature for the **scheduledSynchNEListGet** is shown below: + +``` +ScheduledSynchNESeqType scheduledSynchNEListGet () + raises (AccessDenied); +``` + +There are no input parameters. + +The return value is of type **ScheduledSynchNESeqType** and provides the listing of NEs desired. + +#### 9.14.1.8 Exceptions + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **BackupInProgress** is raised when the synchronisation request is issued while the backup is in progress. + +The exception **CommFailure** is raised when the DCN between the Supplier Management System and OLT or the communication between OLT and subtending ONT or ONU is down. + +The exception **DCNTimeout** is raised when the DCN communications link between at least one of the NEs and the Supplier Management System is so congested that current state or status information cannot be transferred within a system defined time period. + +The exception **EquipmentFailure** is raised when the equipment where the data is backed up from is in failure condition. + +The exception **InvalidScheduler** is raised when the given scheduler is inappropriate for use in this operation, or out-of-date. + +The exception **SynchInProgress** will be raised when a new synchNe is requested while either synchNe or scheduledSynchNe is in progress. + +The exception **SynchNotScheduled** is raised if no planned synchronisation exists for the NE at the specified time. + +The exception **UnknownNE** is raised when the NE mentioned in the request is unknown to the Supplier Management System. + +The exception **UnknownScheduler** is raised when the given scheduler name is not found. + +The exception **Timeout** is raised when the specified process has exceeded a system-defined default timeout period. + +The exception **NoSynchInProgress** is raised if there is no synchronisation process in progress. + +## 9.15 Test module + +This service is used to provide interfaces for the operator or OMS to perform directed or scheduled testing procedures. Tests such as ATM OAM cell loopback testing, interface loopback set-up on subscriber cards or OLT network interface cards, and ATM continuity checks are specified using this service. Tests can be either scheduled or manually invoked following an identified fault or subscriber service complaint. The TestActionPerformer interface provides the operations to execute tests applicable on network resources. + +### 9.15.1 TestActionPerformer interface + +#### 9.15.1.1 aTMLoopback + +This operation is used to invoke an ATM OAM Loopback test. ATM Loopback test is unidirectional. + +The operation signature for the **aTMLoopback** is shown below: + +``` +AggregateATMLoopbackResultSeqType aTMLoopback ( + in UserIdType testRequestorId, + in ManagedEntityIdType ctp, + in ATMLoopbackInfoType aTMLoopbackInfo, + in TestIterationNumType testIterationNum, + in ServiceInstanceIdType serviceInstanceId) + raises (AccessDenied, CommFailure, UnknownManagedEntity, + NotAvailableForTest, InvalidLocationId, InvalidDirection); +``` + +The input parameter **testRequestorId** is used to identify the initiator of the ATM Loopback test. The input parameter **ctp** is used to uniquely identify the CTP for the loopback cell injection point. The input parameter **aTMLoopbackInfo** is used to provide specific ATM test information; the LoopbackLocationId is part of aTMLoopbackInfo. The input parameter **testIterationNum** identifies the iteration number for the ATM loopback test. The input parameter **serviceInstanceId** identifies the possible service instance associated with the loopback test request. + +When specifying aTMLoopbackInfo, the only applicable values for directionality are 'egress' or 'ingress' only. The directionality is specified as part of the **aTMLoopbackInfo**. + +The LoopbackLocationId identifies the point(s) along a virtual connection where the loopback is to occur. The default value of all ones is used by the transmitter to indicate the end point. When segmentCellInd is set to 'false', the LoopbackLocationId must be set to the default. If no + +LoopbackLocationId is provided, it is assumed that there is a designated segment endpoint for the flow associated with the injection ctp. + +For ctp, all zeros indicate a loopback request directed at all connection points having a LoopbackLocationId. All ones indicate a loopback request directed at the endpoint (segment or connection endpoint). 'x6A'H indicates no designated CP for loopback, and therefore no loopback should be performed. All other values for LoopbackLocationId indicate a loopback request directed at a specific LoopbackLocationId location. + +The return value is of type **AggregateATMLoopbackResultSeqType** which provides information on the test, specifically the loopbackingLLID, responseTime in microseconds, and success/failure for each iteration. + +#### 9.15.1.2 initializeContinuityCheck + +This operation is used to prepare for an ATM continuity check. The creation of a continuity test environment does not necessarily initiate the test, but rather schedules a test to be initiated. Upon successful creation of a continuity check, the system will return a unique identifier that is used to identify the test. + +This operation deals with the test setup only. Once the test is executed, an alarm will be raised in case of a failure. + +The operation signature for the **initializeContinuityCheck** is shown below: + +``` +CCSetUpIdType initializeContinuityCheck( + in UserIdType testRequestorId, + in ManagedEntityIdType sourceCtp, + in ATMContinuityCheckInfoType aTMContinuityCheckInfo, + in GeneralizedTimeType stopTime, + in ServiceInstanceIdType serviceInstanceId) + raises (AccessDenied, CommFailure, UnknownManagedEntity, + NotAvailableForTest, InvalidStartTime, InvalidStopTime, + InvalidDirection); +``` + +The input parameter **testRequestorId** is used to identify the initiator of the test. The input parameter **sourceCtp** and **sinkCtp** is used to identify the A point for the continuity test. The input parameter **aTMContinuityCheckInfo** is used to provide specific continuity test information. The directionality must be set to 'BothDirections' and segmentCellInd is set to 'true' for segment continuity test, and 'false' for end-to-end. The input parameter **stopTime** provides information on how long the test should be executed. The input parameter **serviceInstanceId** identifies the possible service instance associated with the loopback test request. + +The return value is of type **CCSetUpIdType** which uniquely identifies the test that was set up. The CCSetUpId for the setup test exists until the stopTime is reached, or until it is explicitly cancelled using the terminateContinuityCheck operation. + +#### 9.15.1.3 terminateContinuityCheck + +This operation is used to take down the ATM continuity test environment. If the continuity test has already been initiated (i.e., its startTime is reached), the continuity test will stop executing and will then be removed. + +The operation signature for **terminateContinuityCheck** is shown below: + +``` +void terminateContinuityCheck( + in CCSetUpIdType cCSetUpId) + raises (AccessDenied, CommFailure, UnknownTest); +``` + +The input parameter **CCSetUpId** is used to identify the test to terminate. + +The return value is of type **void**. + +#### 9.15.1.4 **scheduleResourceSelfTest** + +This operation is used to schedule a resource self test. This operation is used by the OMS to set up self tests on resources to be executed at a regular basis. Having a scheduler object setup is a prerequisite for initiating this operation. + +The operation signature for the **scheduleResourceSelfTest** is shown below: + +``` +TestTrackingObjectIdType scheduleResourceSelfTest ( + in UserIdType testRequestorId, + in ManagedEntityIdType targetNE, + in unsigned long timeOutPeriod, //In seconds. + in ResourceSelfTestInfoSeqType specificTestInfo, + in UserLabelType schedulerName) + raises (AccessDenied, UnknownNE, UnknownScheduler, + InvalidScheduler, InvalidTimeoutPeriod, InvalidTestOperations); +``` + +The input parameter **testRequestorId** is used to identify the initiator of the test. The input parameter **targetNE** identifies the network element to perform self test. The input parameter **timeOutPeriod** identifies the maximum time period that the system will allow the test to run on the resource. The input parameter **specificTestInfo** is used to provide supplier-specific self test information regarding each diagnostic test type to be run; this information is provided to the operator via system documentation. The input parameter **schedulerName** is used to reference the applicable scheduler for this test. + +The return value of type **TestTrackingObjectIdType** uniquely identifies the scheduled testing. The Test Tracking Object exists until it is explicitly cancelled using the **terminateScheduledResourceSelfTest** operation or if the scheduler end time is reached. + +The self test results are logged. The **ResourceSelfTestResultSeqType** data type defines part of the information that is logged. + +#### 9.15.1.5 **modifyResourceSelfTestSchedule** + +This operation is used to modify the schedule for a regularly conducted resource self test. If successful, the resource self test initiation is changed with the next iteration. + +The operation signature for **modifyResourceSelfTestSchedule** is shown below: + +``` +void modifyResourceSelfTestSchedule ( + in TestTrackingObjectIdType testTrackingObjectId, + in UserLabelType newSchedulerName) + raises (UnknownTest, UnknownScheduler, InvalidScheduler, + AccessDenied); +``` + +The input parameter **testTrackingObjectId** is used to identify the scheduled test. The input parameter **testTrackingObjectId** is used to identify the new schedule. + +The return value is of type **void**. + +#### 9.15.1.6 **cancelScheduledResourceSelfTest** + +This operation is used to cancel a regularly scheduled resource self test. If successful, this operation cancels the test prior to its initiation with the next trigger time. + +The operation signature for **cancelScheduledResourceSelfTest** is shown below: + +``` +void cancelScheduledResourceSelfTest ( + in TestTrackingObjectIdType testTrackingObjectId) + raises (UnknownTest, UncontrolledTestInProgress, AccessDenied); +``` + +The input parameter **testTrackingObjectId** is used to identify the scheduled test to terminate. + +The return value is of type **void**. + +#### 9.15.1.7 conductResourceSelfTest + +This operation is used to initiate a resource self test following the identification of a system fault or a subscriber service complaint. The test results are logged in the Supplier Management System. + +The operation signature for the **conductResourceSelfTest** is shown below: + +``` +TestTrackingObjectIdType conductResourceSelfTest ( + in UserIdType testRequestorId, + in ManagedEntityIdType targetNE, + in unsigned long timeOutPeriod, //In seconds. + in ResourceSelfTestInfoSeqType specificTestInfo) + raises (AccessDenied, CommFailure, UnknownNE, + InvalidTimeoutPeriod, InvalidTestOperations); +``` + +The input parameter **testRequestorId** is used to identify the initiator of the test. The input parameter **targetNE** identifies the network element to perform self test. The input parameter **timeOutPeriod** identifies the time period that the system will try to initiate the test. The input parameter **specificTestInfo** is used to provide specific self test information providing details on each diagnostic test type to run. + +The return value is of type **TestTrackingObjectId** and provides a mechanism to allow the operator to terminate a controlled resource self test. If the resource self test is uncontrolled, the Supplier Management System returns the value 0. + +#### 9.15.1.8 terminateResourceSelfTest + +This operation terminates a resource self test in progress. + +The operation signature for **terminateResourceSelfTest** is shown below: + +``` +ResourceSelfTestResultSeqType terminateResourceSelfTest ( + in TestTrackingObjectIdType testTrackingObjectId) + raises (UnknownTest, UncontrolledTestInProgress, AccessDenied); +``` + +The input parameter **testTrackingObjectId** is used to identify the test to terminate. + +The return value of type **ResourceSelfTestResultSeqType** provides whatever interim test results are available. + +#### 9.15.1.9 initiateLoopback + +This operation is used to initiate a loopback for a service. For example, a DS1 NearEndLineLoopback [could we support far end] or a SONET FacilityLoop will be performed. + +The operation signature for the **initiateLoopback** is shown below: + +``` +LoopbackTrackingObjectIdType initiateLoopback ( + in UserIdType testRequestorId, + in ManagedEntityIdType loopingCtp, + in long duration, //In minutes. + in DirectionalityType directionality, + in LoopbackTestType loopbackTest + in ServiceInstanceIdType serviceInstanceId) + raises (AccessDenied, CommFailure, UnknownManagedEntity, + NotAvailableForTest); +``` + +The input parameter **testRequestorId** is used to identify the initiator of the test. The input parameter **loopingCtp** is used to identify the CTP to perform the loopback on. The input parameter **duration** defined the amount of time in seconds that the loopback should be active. The input parameter **directionality** indicates if the loopback should be performed for ingress traffic, egress traffic or for traffic in both directions. The input parameter **loopbackTest** is used to identify the + +specific loopback test type. The input parameter **serviceInstanceId** is used to specify the service associated with this loopback operation. + +The return value of type **LoopbackTrackingObjectIdType** uniquely identifies the loopback test that is initiated. Once a loopback completes its running cycle (i.e., the test duration elapses), the object will not longer be available. + +#### 9.15.1.10 terminateLoopback + +This operation is used to cancel a running loopback. + +The operation signature for the **terminateLoopback** is shown below: + +``` +void terminateLoopback ( + in LoopbackTrackingObjectId loopbackTrackingObjectId) + raises (UnknownTest, AccessDenied); +``` + +The input parameter **loopbackTrackingObjectId** is used to identify the loopback to terminate. + +The return value is of type **void**. + +#### 9.15.1.11 getLoopbackInfo + +This operation is used to retrieve the loopback information of a particular connection termination point. + +The operation signature for the **getLoopbackInfo** is shown below: + +``` +LoopbackInfoType getLoopbackInfo ( + in ManagedEntityIdType cTP) + raises (UnknownManagedEntity, AccessDenied); +``` + +The input parameter **cTP** is used to identify the possible loopback location. + +The return value is of type **LoopbackInfoType** and it specifies the loopback type and directionality. + +#### 9.15.1.12 getLoopbackInfoByNE + +This operation is used to retrieve the location and details of every connection point in an NE that are in loopback mode. + +The operation signature for the **getLoopbackInfoByNE** is shown below: + +``` +LoopbackInfoSeqType getLoopbackInfoByNE ( + in ManagedEntityIdType nEId) + raises (UnknownManagedEntity, AccessDenied); +``` + +The input parameter **nEId** is used to identify the network resource. + +The return value is of type **LoopbackInfoSeqType** providing a listing of loopback locations, loopback types and directionality. + +#### 9.15.1.13 getTestStatus + +This operation is used to retrieve the status of a loopback in progress. + +The operation signature for the **getTestStatus** is shown below: + +``` +StatusValueType getTestStatus ( + in LoopbackTrackingObjectIdType id) + raises (AccessDenied, UnknownTest); +``` + +The input parameter **id** specifies the test setup of interest. + +The return value is of type **StatusValueType** and indicates the status of the loopback action. + +#### 9.15.1.14 **scheduledTestNEListGet** + +This operation is used to retrieve the list of all scheduled NE testing. + +The operation signature for the **scheduledTestNEListGet** is shown below: + +``` +ScheduledTestNESeqType scheduledTestNEListGet () + raises (AccessDenied); +``` + +There are no input parameters. + +The return value is of type **ScheduledTestNESeqType** and provides the listing desired. + +#### 9.15.1.15 **testHistoryByManagedEntity** + +This operation is used to retrieve the test history associated with a managed entity. This history should be retained as long as required by the operator. + +The operation signature for the **testHistoryByManagedEntity** is shown below: + +``` +TestHistorySeqType testHistoryByManagedEntity ( + in ManagedEntityIdType managedEntityId) + raises (AccessDenied, UnknownManagedEntity); +``` + +The input parameter **managedEntityId** specifies the reference managed entity. + +The return value is of type **TestHistorySeqType** and provides the listing desired. + +#### 9.15.1.16 **testHistoryByServiceInstance** + +This operation is used to retrieve the test history associated with a service instance. This history should be retained as long as required by the operator. + +The operation signature for the **testHistoryByServiceInstance** is shown below: + +``` +TestHistorySeqType testHistoryByServiceInstance ( + in ServiceInstanceIdType serviceInstanceId) + raises (AccessDenied, UnknownServiceInstance); +``` + +The input parameter **serviceInstanceId** specifies the reference service instance. + +The return value is of type **TestHistorySeqType** and provides the listing desired. + +#### 9.15.1.17 **Exceptions** + +The exception **AccessDenied** is raised when the system is not granted access to the interface object. + +The exception **CommFailure** is raised when the DCN between Supplier Management System and OLT or the communication between OLT and source ONT is down. + +The exception **InvalidDirection** is raised when the specified test directionality is invalid for the given test. + +The exception **InvalidLocationId** is raised when the LLID specified is not valid. + +The exception **InvalidScheduler** is raised when the given scheduler is inappropriate for use in this operation, or out-of-date. + +The exception **InvalidStartTime** is raised when the specified start time is inconsistent with the current trigger time matrix or the stop time. + +The exception **InvalidStopTime** is raised when the specified stop time is inconsistent with the current trigger time matrix or the start time. + +The exception **InvalidTestOperations** is raised when the requested self test operation is not valid. + +The exception **InvalidTimeOutPeriod** is raised when the designated timeout period violates definition of valid values. + +The exception **NotAvailableForTest** is raised when the sourceCTP is unable to establish a continuity check test setup with the sinkCTP. + +The exception **UncontrolledTestInProgress** is raised when the self test cannot be cancelled because of an uncontrolled test. + +The exception **UnknownNE** is raised when the NE mentioned in the request is unknown to the Supplier Management System. + +The exception **UnknownManagedEntity** is raised when the specified ManagedEntity is unknown to the Supplier Management System. + +The exception **UnknownServiceInstance** is raised when the specified Service Instance is unknown to the Supplier Management System. + +The exception **UnknownScheduler** is raised when the given scheduler name is not found. + +The exception **UnknownTest** is raised when the test specified by the trackingId is not known in the Supplier Management system. + +## 9.16 FileTransfer module + +This module deals with the management of non-real time transfer records stored in any short-term archive in the Supplier Management System. It supports the subsequent tracking and monitoring of the file transfer process through the use of TransferTrackingObjectId. The Supplier Management System logs the successful or unsuccessful results of the file transfer. Any request for file transfer is accompanied by security credentials whereby the Supplier Management System is allowed to communicate with the destination server. The file transfer can be scheduled in advance. Transfer Tracking Objects are automatically deleted by the Supplier Management System once the associated file transfer has finished and results (whether successful or unsuccessful) are recorded in the completion log. + +### 9.16.1 TransferMgr interface + +#### 9.16.1.1 fileTransfer + +The file transfer is initiated immediately by this operation. + +The operation signature for **fileTransfer** is shown below: + +``` +TransferTrackingObjectIdType fileTransfer( + in ManagedEntityIdType recordSetId, + in DCNAddressType destinationServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType destinationFile, + in boolean overwriteExistingFile) + raises (AccessDenied, CommFailure, UnknownRecordSet, + UnknownDestinationServer ); +``` + +The input parameter **recordSetId** identifies the short-term archive from which the data is to be extracted for file transfer. The input parameter **destinationServerAddr** identifies the data communication networking address for the server that is the destination of the file transfer. The input parameters **userId** and **password** provide the login mechanism to the destination server (assuming such security credentials are needed). The input parameter **destinationFile** provides a full directory location for the transferred file. Finally, the parameter **overwriteExistingFile** indicates whether or not the file transfer should allow the overwriting of a pre-existing file with the same destination directory location. + +The return value of type **TransferTrackingObjectIdType** provides a correlation key to be used when attempting to track the status of the non-real time transfer of data from the short-term archive at some later point. + +#### 9.16.1.2 **scheduleFileTransfer** + +The file transfer is scheduled for future initiation by this operation. All the contents of the identified short-term archive are extracted for file transfer. No assumption is made concerning the purging of the archive based on successful file transfer of data. Instead, the archive is purged, based on agreements between the supplier and operator concerning retention policy of archived information. + +The operation signature for **scheduleFileTransfer** is shown below: + +``` +TransferTrackingObjectIdType scheduleFileTransfer ( + in ManagedEntityIdType recordSetId, + in DCNAddressType destinationServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType destinationFile, + in boolean overwriteExistingFile, + in UserLabelType schedulerName) + raises (AccessDenied, UnknownRecordSet, + UnknownDestinationServer, UnknownScheduler, InvalidScheduler); +``` + +The input parameter **recordSetId** identifies the short-term archive from which the data is to be extracted for file transfer. The input parameter **destinationServerAddr** identifies the data communication networking address for the server that is the destination of the file transfer. The input parameters **userId** and **password** provide the login mechanism to the destination server (assuming such security credentials are needed). The input parameter **destinationFile** provides a full directory location for the transferred file. The parameter **overwriteExistingFile** indicates whether or not the file transfer should allow the overwriting of a pre-existing file with the same destination directory location. Finally, the input parameter **schedulerName** is the schedule information associated with the file transfer, based on which the file transfer takes place. + +The return value of type **TransferTrackingObjectIdType** provides a correlation key to be used when attempting to track the status of the non-real time transfer of data from the short-term archive at some later point. + +#### 9.16.1.3 **modifyFileTransferSchedule** + +The file transfer schedule is modified by this operation. If successful, the new schedule is applied with the next iteration. + +The operation signature for **modifyFileTransferSchedule** is shown below: + +``` +void modifyFileTransferSchedule ( + in TransferTrackingObjectIdType transferTrackingObjectId, + in UserLabelType newSchedulerName) + raises (AccessDenied, UnknownTransferProcess, + UnknownScheduler, InvalidScheduler); +``` + +The input parameter **transferTrackingObjectId** identifies the scheduled file transfer activity. The input parameter **newSchedulerName** is the new schedule information to be associated with the file transfer. + +The return value is of type **void**. + +#### 9.16.1.4 **cancelScheduledFileTransfer** + +The file transfer schedule is cancelled by this operation. If successful, the activity is cancelled with the next iteration. + +The operation signature for **cancelScheduledFileTransfer** is shown below: + +``` +void cancelScheduledFileTransfer ( + in TransferTrackingObjectIdType transferTrackingObjectId) + raises (AccessDenied, UnknownTransferProcess); +``` + +The input parameter **transferTrackingObjectId** identifies the scheduled file transfer activity. + +The return value is of type **void**. + +#### 9.16.1.5 **getStatus** + +This operation allows the client to check the status of a transfer before its completion using a key. + +The operation signature for **getStatus** is shown below: + +``` +StatusValueType getStatus ( + in TransferTrackingObjectIdType transferTrackingObjectId) + raises (UnknownTransferProcess, AccessDenied); +``` + +The input parameter **transferTrackingObjectId** identifies the key of a particular file transfer process. The operator specifies this information and finds the status information of that file transfer process. + +The return value is of type **StatusValueType** and provides the status of the file transfer process. + +#### 9.16.1.6 **fileTransferHistoryListGet** + +This operation is used to retrieve the list of all completed file transfers for the Supplier Management System. This list is maintained in the Supplier Management System as a wraparound log. + +The operation signature for the **fileTransferHistoryListGet** is shown below: + +``` +FileTransferHistorySeqType fileTransferHistoryListGet () + raises (AccessDenied); +``` + +There are no input parameters. + +The return value is of type **FileTransferHistorySeqType** and provides the listing desired. + +#### 9.16.1.7 **scheduledFileTransferListGet** + +This operation is used to retrieve the names of all existing scheduled file transfers defined for the Supplier Management System. + +The operation signature for the **scheduledFileTransferListGet** is shown below: + +``` +ScheduledFileTransferSeqType scheduledFileTransferListGet () + raises (AccessDenied); +``` + +There are no input parameters. + +The return value is of type **ScheduledFileTransferSeqType** and provides the listing desired. + +#### 9.16.1.8 **Exceptions** + +The exception **AccessDenied** is raised when the client is not granted access to this interface object. + +The exception **CommFailure** is raised when there is a communication failure between the destination server and the Supplier Management System. + +The exception **UnknownDestinationServer** is raised when the specified destination server cannot be accessed by the transfer agent. + +The exception **UnknownRecordSet** is raised when the target file cannot be found. + +The exception **UnknownScheduler** is raised when the specified scheduler cannot be accessed by the transfer agent. + +The exception **UnknownTransferProcess** is raised when the specified **TransferTrackingObjectId** cannot be identified. + +# 10 Compliance statement + +An implementation claiming conformance to any of the interfaces defined in this Recommendation shall implement the complete behaviour associated with all the operations of the interface, as well as behaviour of referenced definitions in the module q834\_4::Q834Common. + +# Annex A + +## Data dictionary + +Table A.1 provides a listing of all data elements (data types) used in the interface specification found within this Recommendation. The listing includes management information interpretation, syntax, and any qualifying comments for each. Data elements are listed in alphabetical order. If a data type and a second data type constructed as a sequence of the first are both present in the interface specification, then only the first data element is defined. The interpretation of the second is obvious. In these cases, the name of the sequence is the name of the original data element with the characters "Seq" inserted before the ending of "Type". + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|-----------------------|------------------------------------------------------------------------------------|--------|-----------------------------------------------| +| AAL1PMHistoryDataType | This data element provides the items in this record type. | struct | | +| AAL1ProfileType | This data element provides the values for a profile of kind AAL1. | struct | | +| AAL2PMHistoryDataType | This data element provides the items in this record type. | struct | | +| AAL2ProfileType | This data element provides the values for a profile of kind AAL2. | struct | | +| AAL2PVCProfileType | This data element provides the values for a profile of kind AAL2PVC. | struct | | +| AAL5PMHistoryDataType | This data element provides the items in this record type. | struct | | +| AAL5ProfileType | This data element provides the values for a profile of kind AAL5. | struct | | +| AALModeType | This data element indicates which mode the AAL for the supporting VCC is employed. | enum | | +| ActivityLevelType | Specifies the permission level of access afforded to a user for an activity. | enum | monitorOnly,
allowedToExecute,
noAccess | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------------------------------------------------------------------------------------------| +| ActivityType | Specifies the type or category of user activity. | short | Defined as constants within the interface q834_4::AccessControl::AccessControlMgr | +| AdministrationDomainType | The identifier provided by the OMS or operator during registration to indicate the administration domain to which the NE belongs. | UserLabelType | | +| AdministrativeStateType | Is used to activate (unlock), deactivate (lock), or shutdown (shuttingdown) the functions of the associated managed entity. | enum | Defined in ITU-T Rec. X.780. | +| AggregateATMLoopbackResultType | Specifies the results of an ATM loopback test. | struct | | +| AlarmLogRecordType | This data element provides the items in this record type. | struct | | +| AlarmStatusSeqType | This data element provides all relevant values for the status variable alarm status. | enum | Valid enum values are AS_UnderRepair, AS_Critical, AS_Major, AS_Minor, AS_AlarmOutstanding | +| AnnouncementType | This data element provides the announcement to the customer going off-hook when no call has been attempted. | enum | | +| APONPMHistoryDataType | This data element provides the items in this record type. | struct | | +| AppIdType | This data element specifies the protocol combinations used between the Inter-Working Functions found in the Voice Gateway function and the ONT or NT. | enum | | +| ATMContinuityCheckInfoType | Specifies the input for ATM continuity check. | struct | | +| ATMLoopbackInfoType | Specifies the ATM loopback test info. | struct | | +| ATMNetworkAccessProfileType | Profiles an instance of profile kind ATMNetworkAccess | struct | | +| ATMOverbookingFactorType | This data element provides the value for ATM Overbooking. | struct | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|------------------------------| +| AudioServIndType | This boolean data element indicates whether or not audio service is transported, where the value TRUE implies the presence of this service. | boolean | | +| AutoDetectionIndType | This boolean data element identifies whether or not data rate auto-detection is enabled. | boolean | | +| AvailableSysBandwidthSeqType | This is a listing of available system bandwidth by port. | sequence of PortBandwidthType | | +| AvailabilityStatusSetType | This data element provides all relevant values for the status variable availability status. | sequence of availability status values | Defined in ITU-T Rec. X.780. | +| BackedUpStatusType | This data element indicates whether or not the alarm emitting managed entity has an operational backup unit. | boolean | Defined in ITU-T Rec. X.780. | +| BridgedLANServiceProfileType | This data element provides the values for a profile of kind Bridged LAN Service. | struct | | +| BridgePriorityType | This boolean data element indicates whether or not the learning functions of the bridge are enabled. The value TRUE means enabled. | short | | +| BRISignallingType | This data element selects which signalling format should be used for Basic Rate ISDN. | enum | | +| BufferedCDVToleranceType | This data element represents the duration of user data that must be buffered by the CES interworking entity to offset cell delay variation. This timing will be in 10 microsecond increments. | long long | | +| CableLengthType | This data element provides the length of twisted pair cable from the physicalPathTP of type "DS1" interface to the DSX1 cross-connect point (if applicable). | long long | | +| CASType | This data element selects which AAL1 format should be used. It applies to structured interfaces only. For unstructured interfaces this value, if present, must be set to the default of basic. | enum | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------| +| CASIndType | This boolean data element indicates whether or not Channel Associated Signaling is enabled on the connection, where the value TRUE implies it is enabled. | boolean | | +| CBRRateType | This data element represents the rate of the CBR service supported by the AAL. | enum | | +| CCSetUpIdType | Specifies a unique Id for CC test set up. | long long | | +| CDVTPCREgressType | Cell Delay Variation Tolerance – this parameter is required for all service categories. It is applied to CLP = 0 flow for ABR and apply to CLP = 0 + 1 flows otherwise. | long long | | +| CDVTPCRIngressType | Cell Delay Variation Tolerance – this parameter is required for all service categories. It is apply to CLP = 0 flow for ABR and apply to CLP = 0 + 1 flows otherwise. | long long | | +| CellLossIntegrationPeriodType | This data element represents the time in milliseconds for the cell loss integration period. If cells are lost for this period of time, the associated interworking vcCTPF entity will generate a cell starvation alarm. | long long | | +| CESServiceProfileType | This data element provides the values for a profile of kind CES Service. | struct | | +| ClockRecoveryType | This data element indicates whether the clock recovery type is derived from the physical interface. | enum | | +| CMDataIndType | This boolean data element indicates whether or not Circuit Mode Data is carried on this connection, where the value TRUE implies its presence. | boolean | | +| CMMultiplierNumType | This data element provides the $N$ value in $N \times 64$ kbit/s circuit mode data. | short | | +| ConformanceDefType | Indicates the type of conformance as defined in ATM-Forum TM 4.0. | enum | | +| ControlStatusSetType | This data element provides all relevant values for the status variable control status. | Sequence of enum | Defined in ITU-T Rec. X.780. | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CorrelatedNotificationType | This data element lists the reference numbers for other event notifications that have a relationship to this event notification. | Sequence of Notification IdentifierType | | +| CreationModeType | This data element indicates how the record set was created. | enum | Choice between operator-defined or instantiated as part of Supplier Management System application installation. | +| CurrentListingType | Specifies a current event listing type that can be synchronized between the Supplier Management System and the NE. | short | Values specified as constants. | +| CurrentSizeType | This data element describes the current size of a record set. | unsigned long long | In the same units as MaxSizeType. | +| DataRateType | This data element provides the data rate for the Ethernet connection. The valid values are 10 Mbit/s or 100 Mbit/s. | enum | | +| DayOfMonthType | Specifies the day of the month. | short | 0 is interpreted to mean unspecified. | +| DayOfWeekType | Specifies the day of the week in the schedule. | enum | Sunday,
Monday,
Tuesday,
Wednesday,
Thursday,
Friday,
Saturday,
Unspecified | +| DCNAddressType | Provides the address for the NE or system server on the Data Communications Network of the Operator. Used for routing of messages. | string | Normally IP Address.
Examples include items labelled as softwareSourceAddr, destinationServerAddr, sourceServerAddr, nEDCNAddress, and newNEDCNAddress. | +| DefaultSSCSPParameterProfile1PtrType | This data element identifies the default values for the service specific convergence service profile associated with channels carrying control and management plane traffic. | Name | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| DefaultSSCSParameterProfile2PtrType | This data element identifies the default values for the service specific convergence service profile associated with channels carrying media streams (e.g., POTS or ISDN B-channels). | Name | | +| DiagnosticType | Specifies the diagnostic test type. | short | Supplier specific | +| DirectionalityType | Specifies the directionality of the test. | enum | Values are Egress, Ingress, BothDirections | +| DirectionType | Specifies the direction of the optical wavelength associated with a port. | enum | Values are unidirection or bidirection. | +| DownloadStatusSeqType | This data element provides the status of a software download activity. | struct
comprised of the Id of a target followed by the status for delivery, distribution, commitment, and activation | | +| DS1EncodingType | This data element identifies the type of DS1 line encoding. | enum | | +| DS1FramingType | This data element identifies the type of framing employed. | enum | | +| DS1PMHistoryDataType | This data element provides the items in this record type. | struct | | +| DS1ProfileType | This data element provides the values for a profile of kind DS1. | struct | | +| DS3ApplicationType | This data element identifies the type of DS3 signal. | enum | | +| DS3PMHistoryDataType | This data element provides the items in this record type. | struct | | +| DS3ProfileType | This data element provides the values for a profile of kind DS3. | struct | | +| DS3EncodingType | This data element identifies the DS3 line encoding. | enum | | +| DTEDCType | This data element indicates whether the Ethernet Interface wiring is DTE or DCE. | boolean | | +| DTMFIndType | This boolean data element indicates whether or not Dual Tone Multi-Frequency dialled digits is transported on the connection, where the value TRUE implies its presence. | boolean | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------| +| DuplexType | This data element indicates whether full duplex (=TRUE) or half duplex mode (=FALSE) is employed. | boolean | | +| E1PMHistoryDataType | This data element provides the items in this record type. | struct | | +| E3PMHistoryDataType | This data element provides the items in this record type. | struct | | +| EchoCancellationIndType | This data element indicates the presence of echo cancellation circuitry. | boolean | | +| ELCPIndType | This boolean data element indicates whether or not Emulated Loop Control Protocol is in use. | boolean | | +| EncapsulationProtocolType | This data element identifies the encapsulation protocol used for bridging LAN over ATM. | short | | +| EncProfileIndexType | This data element indicates the specific predefined encoding profile used. | short | | +| EncSrcTypeType | This data element indicates the source for the encoding profile format. Valid values include but are not limited to "ITU-T" and "ATM Forum". | enum | | +| EndPointType | This specifies the characteristics of an end point of a connection | struct | | +| EquipmentHolderAddressType | This data element identifies the equipment location for a circuit pack. | struct whose components include the shelf number (short) and the port number (short) | | +| EquipmentHolderFType | This data structure identifies the equipmentHolderF item named in the autodiscovery event. | struct listing the attribute values for the equipmentHolderF Managed Entity | | +| EquipmentType | This data element identifies the inventory item named in the autodiscovery event. | short | | +| EthernetPMHistoryDataType | This data element provides the items in this record type. | struct | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------------------------------------------------------------------------| +| EthernetProfileType | This data element provides the values for a profile of kind Ethernet. | struct | | +| ExternalTimeType | This data element establishes the local time to be associated with the network resource. | GeneralizedTimeType | | +| FaxDemodIndType | This boolean data element indicates whether or not a FAX demodulation is present, where the value TRUE implies its presence. | boolean | | +| FilenameType | Identifies the full pathname of a file. This file can contain configuration data uploaded from an NE, a location to transfer a file of records, or a location for an NE software generic or patch. | string | | +| FileTransferHistoryType | This data element provides a record concerning file transfer still logged on the Supplier Management System. | struct | | +| FilterType | This data element is defined by CosNotifyFilter::Filter. | | | +| FMDDataIndType | This boolean data element indicates whether or not Frame Mode Data is carried on this connection, where the value TRUE implies its presence. | boolean | | +| FMMaxFrameLenType | This data element the maximum length of a frame mode data unit. | long long | | +| ForwardDelayType | This data element gives the time (in hundredths of a second) that the bridge on the Ethernet card in the ONT (as a member of the community of all bridges in the Bridged Local Area Network) retains a packet before forwarding it. | short | | +| ForwardErrorCorrectionType | This data element indicates the FEC method. | enum | | +| FullActionType | Specifies the behaviour of the record set when it reaches its maximum size. | enum | Choice between wrap and halt. | +| GeneralizedTimeType | Provides a normalized metric of time. Used to avoid ambiguities involving time zones. | string | Only one allowed format
YYYYMMDDHH
MMSS.fffZ (i.e.,
Greenwich Mean
Time). | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------| +| HelloTimeType | This data element provides the time interval (in hundredths of a second) between hello packets. It is the time interval, in hundredths of a second, that a bridge advertises its presence while a root or attempting to become a root. | short | | +| HistoryDataType | Identifies a record type comprised of performance monitoring statistics. | RecordKind Type | | +| HourlyDailyWeeklyMonthlyIndType | Specifies whether the schedule has an Hourly, Daily, Weekly or Monthly time cycle | enum | Hourly,
Daily,
Weekly,
Monthly | +| IDLCCallProcessingProfileType | This data element provides the values for a profile of kind IDLC Call Processing. | struct | | +| JitterBufferMaxType | This data element provides the maximum depth of the jitter buffer associated with this service. Units are in milliseconds. | long long | | +| JitterTargetType | This data element provides the target value of the jitter buffer. The system will try to maintain the jitter buffer at the target value. Units are in milliseconds. | long long | | +| LANType | This data element provides information on the type of LAN employed, e.g., ethernet, token-ring, etc. | short | | +| LESProfileType | This data element provides the values for a profile of kind LES. | struct | | +| LocalMaxNumVCCSupportedType | This data element identifies the number of VCCs that can be supported by the ATM NE at this end of the interface. | long long | | +| LocalMaxNumVCIBitsType | This data element identifies the maximum number of allocated bits of the VCI sub-field that can be supported by the FSN NE at this end of the interface. | short | | +| LocalMaxNumVPCSupportedType | This data element identifies the number of VPCs that can be supported by the OLT at this end of the interface. | long long | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------------------------------------------------------------------------| +| LocalMaxNumVPIBitsType | This data element identifies the maximum number of allocated bits of the VPI sub-field that can be supported by the FSAN NE at this end of the interface. | short | | +| LoopbackCodeType | This data element identifies the type of in-band loopback code supported. | enum | | +| LoopbackInfoType | The data element specifies the loopback type, directionality, and location. | struct | | +| LoopbackInfoSeqType | Provides information concerning one loopback condition in the network resource. | struct | | +| LoopbackLocationIdSeqType | Specifies the unique location Id for a ctp. | Sequence of octets of length 16 | | +| LoopbackLocCodeType | This data element provides the code that identifies incoming ATM layer OAM loopback cells that are to be looped-back at this UNI. | string | | +| LoopbackTestType | This data element identifies the type of loopback test setup to be used or in use. | unsigned short | Possible values are defined in PhysicalLayerLoopback interface of Q834::Common. | +| LoopbackTrackingObjectIdType | This data element identifies current loopback condition. | Tracking ObjectIdType | | +| MACBridgePortPMHistoryDataType | This data element provides the items in this record type. | struct | | +| MACBridgePMHistoryDataType | This data element provides the items in this record type. | struct | | +| MACBridgeServiceProfileType | This data element provides the values for a profile of kind MACBridgeService. | struct | | +| ManagedEntityIdType | This data element provides a unique name for a managed entity. The name includes an indication if the name represents a fine-grain managed object name, a façade object name, or just references a data structure. | struct of an enum and an RDNTType | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------| +| MaxAgeType | This data element indicates the maximum age (in seconds) for an entry in the spanning tree listing. It indicates the maximum age in seconds of received protocol information before it is discarded. | short | | +| MaxBSEgressType | Maximum Burst Size - This parameter is required for real-time and non-real-time VBR traffic and for GFR traffic. It applies to CLP = 0 + 1 traffic flow for VBR.1, GFR.1, and GFR.2, and applies to CLP = 0 traffic flow for VBR.2 and VBR.3. | long long | | +| MaxBSIngressType | Maximum Burst Size - This parameter is required for real-time and non-real-time VBR traffic and for GFR traffic. It applies to CLP = 0 + 1 traffic flow for VBR.1, GFR.1, and GFR.2, and applies to CLP = 0 traffic flow for VBR.2 and VBR.3. | long long | | +| MaxCPCSSDUSizeType | This multi-valued data element represents the maximum CPCS_SDU size that will be transmitted over the connection in both the incoming (forward) and outgoing (backward) direction of transmission. | struct | | +| MaxCPS_SDULengthType | This data element provides the maximum allowed length of the Common Part Sublayer Service Data Unit (or CPS SDU) that will be allowed over the connection in either the upstream or downstream direction of transmission. | long long | | +| MaxFrameSizeType | This data element denotes the maximum allowed frame size to be transmitted across this interface. | long long | | +| MaximumChanIdType | This data element provides the maximum value for the Channel Id allowed for the channel within the connection. | short | | +| MaxNumChannelsType | This data element provides the maximum number of channels that can be carried by the VC Trail associated with the interworking vcCTP. | short | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|------------------------------------------------------------------------------| +| MaxNumCIDsType | This data element specifies the maximum number of channels within the VCC that can be active. | short | | +| MaxPacketLengthType | This data element specifies the maximum packet length. | long long | | +| MaxSizeType | Specifies the maximum size of the Record Set. | unsigned long long | In units to be determined by mutual agreement between supplier and operator. | +| MaxSSSARSDULengthType | This data element provides the maximum length allowed for an SSSAR-SDU of the Segmentation and Reassembly Service Specific Convergence sublayer. | long long | | +| MFR1IndType | This boolean data element indicates whether or not Multi-Frequency R1 dialled digits is transported on the connection, where the value TRUE implies its presence. | boolean | | +| MFR2IndType | This boolean data element indicates whether or not Multi-Frequency R2 dialled digits is transported on the connection, where the value TRUE implies its presence. | boolean | | +| MFSEgressType | Maximum Frame Size – This parameter is required for GFR traffic only. | long long | | +| MFSIngressType | Maximum Frame Size – This parameter is required for GFR traffic only. | long long | | +| MinimumChanIdType | This data element provides the minimum value for the Channel Id allowed for any channel within the connection. | short | | +| MonitoredParameterSeqType | This data element identifies a monitored parameter. | string | Monitored parameters are defined in Q834Common::MonitoredParameter | +| MonitoringKindType | This data element identifies the type of performance monitoring specified. | string | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------| +| MonitoringPointThresholdsType | This data element provides a listing of monitoring point instances and the associated threshold data for a specified network resource. | sequence of struct | | +| NameType | This data element provides a CORBA name for a profile object. | CosNaming::Name | | +| NEFSANType | This data structure identifies the generic equipment inventory item named in the autodiscovery event. | struct listing the attribute values for the NEFSAN Managed Entity | | +| NEKindType | This data element identifies the type of network elements that can be constructed. | enum | The choice is between BPONOLT, BPONONT, BPONONU, and BPONNT (Note). | +| NotificationIdentifierType | Uniquely identifies the Notification. | long long | | +| NTType | This data structure identifies the NT inventory item named in the autodiscovery event. | struct listing the attribute values for the NT Managed Entity | | +| OLTType | This data structure identifies the OLT inventory item named in the autodiscovery event. | struct listing the attribute values for the OLT Managed Entity | | +| ONTType | This data structure identifies the ONT inventory item named in the autodiscovery event. | struct listing the attribute values for the ONT Managed Entity | | +| ONUType | This data structure identifies the ONU inventory item named in the autodiscovery event. | struct listing the attribute values for the ONU Managed Entity | | +| OperationalStateType | Specifies the operational state (enabled or disabled) of the managed entity. | enum | Defined in ITU-T Rec. X.780. | +| OpticalWaveLengthArraySeqType | Specifies the wavelength (in nanometers) and direction for a wavelength multiplexed on this optical port. | struct | | +| ParameterSettingSeqType | This data element identifies a monitoring parameter together with its associated sliding window parameters. | struct | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| PartiallyFilledCellsType | This boolean data element identifies the number of leading octets in use. | long long | | +| PasswordType | Provides a security credential for access to the Supplier Management System application or servers. | string | A password supplied with a user Id must confirm to the passwordPolicy enforced by the Supplier Management System. | +| PasswordPolicyType | Specifies the Password Policy which is enforced by the Supplier Management System. It is composed of two components: UserLoginPolicyType and SessionPolicyType. | struct | | +| PCMEncTypeType | This data element indicates the type of PCM coding. Valid values include but are not limited to "mu-law PCM coding" and "alpha-law PCM coding". | short | | +| PCREgressType | Peak Cell Rate – This parameter is required for traffic of all service categories. It is applied to CLP = 0 flow for ABR and applied to CLP = 0 + 1 flow otherwise. | long long | | +| PCRIngressType | Peak Cell Rate – This parameter is required for traffic of all service categories. It is applied to CLP = 0 flow for ABR and applied to CLP = 0 + 1 flow otherwise. | long long | | +| PerceivedSeverityType | Defined by ITU-T Rec. X.780. | enum | | +| PIDType | This data element identifies the media type values that can be used in ATM encapsulation (defined in RFC 1483). | short | | +| PlugInUnitFType | This data structure identifies the PlugInUnitF inventory item named in the autodiscovery event. | struct listing the attribute values for the PlugInUnitType Managed Entity. | | +| PlugInUnitType | Implementation specific, supplier provided name of circuit pack type. | string | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------------------------------------------------------| +| PortBandwidthSeqType | This data element gives bandwidth by provisioned port. | struct | Listing examples include ReservedBandwidthSeqType and AvailableSysBandwidthSeqType | +| POTSSignallingType | This data element selects which signalling format should be used for POTS service. | enum | | +| ProbableCauseType | Data for probable cause. | unsigned short | Values are defined in Q834Common:: ProbableCause and ITU-T Rec. X.780 | +| ProceduralStatusSetType | Provides the procedural status of a non-terminated activity. | Sequence of enum | Defined in ITU-T Rec. X.780. | +| ProfileInfoType | This data element identifies the profile type and its attribute values. | struct | | +| ProfileKindType | This data element identifies the type of profile named. | unsigned short | Values provided in Q834Common. | +| ProtectionParameterType | This data element describes the protection switching parameters associated with a protection grouping of managed entities. Parameters include protection switching ratio, allowed protection switching mechanisms, revertive indicator, and wait time to revert. | struct | | +| ProtectionUnitType | This data element associates protected and protecting network resources. | struct | | +| RASTimerType | This data element provides the reassembly time (in seconds) of the Segmentation and Reassembly Service Specific Convergence sublayer for ITU-T Rec. I.366.1. | short | | +| RateControlIndType | This boolean data element indicates whether or not rate control is transported on the connection, where the value TRUE implies its presence. | boolean | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| RecordType | This is an item stored in a Record Set. | any | The value is a struct based in the RecordKindType defined in Q834Common::RecordSetType. Only one type of RecordKind can be stored in a record set. | +| RecordSetIdType | The ManagedEntityId of the Record Set. | ManagedEntityIdType | | +| RecordSetStatusType | Specifies the current status of the RecordSet. | struct of currentSize Type, Operational State Type, MaxSize Type, Size Threshold Type, filterName, AdministrativeState Type, RecordKind Type, and RecordSet UserLabel | | +| RecordKindType | Identifies the type of the record. | unsigned short | Values defined in Q834Common::RecordSetType | +| RecordsSeqType | This data element provides a set of records grouped together by type. | sequence of any | See above. | +| RemainingPassword Validity | Specifies the password validity in number of days. | long | Value ≥ 1 | +| ReservationIdType | An identifier that correlates bandwidth reserved on a PON or within an OLT system with a service instance. | string | | +| ReservationInfoType | This data element provides a complete accounting of the reservation information and associated service connection information. | struct | | +| ReservedBandwidthSeq Type | Quantifies the amount of bandwidth associated with a reservation Id for a port. | sequence of PortBandwidthType | | +| ResourceSelfTestInfo Type | Provides one testing diagnostic to be used in the resource self test. | short | Values are determined by supplier implementation. | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------------------------------------| +| ResourceSelfTestResultType | Specifies one result for Resource self test. | struct | | +| ScheduledFileTransferType | Identifies a pending scheduled file transfer activity for the Supplier Management System. | struct | | +| ScheduledSynchNEType | This data element associates an NE with its schedule for synchronisation. | struct | | +| ScheduledTestNESeqType | This data element associates an NE with a scheduled test. | struct | | +| SchedulerType | Identifies an instance of Scheduler within the Supplier Management System. | struct | | +| SCREgressType | Sustainable Cell Rate – This parameter applies to real-time and non-real-time VBR. It applies to CLP = 0 + 1 traffic flow for VBR.1 and applies to CLP = 0 traffic flow VBR.2 and VBR.3. | long long | | +| SCRIngressType | Sustainable Cell Rate – This parameter applies to real-time and non-real-time VBR. It applies to CLP = 0 + 1 traffic flow for VBR.1 and applies to CLP = 0 traffic flow VBR.2 and VBR.3. | long long | | +| SecurityAlarmLogRecordType | This data element provides the items in this record type. | struct | | +| SegmentEndpointIndType | Indicates whether or not the constructed vpNetworkCTP is to be viewed as a segment or endpoint for ATM OAM cell loopback testing. | enum | choice of segment, endpoint, or none | +| SegmentLengthType | This data element provides the length of segment for the Segmentation and Reassembly Service Specific Convergence sublayer. It ranges from 0 to the maximum value provided by MaxCPS_SDULen data element. | long long | | +| SerialNumType | Provides the unique hardware Id used in the ranging activity defined in ITU-T Rec. Q.983.1. | string | | +| ServiceAffectingType | This data element indicates whether or not a failure condition is affecting service if it can be determined. | enum | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------------------------------------------------------| +| ServiceCategoryType | Indicates the service category as defined in ATM-Forum TM 4.0. Valid values are CBR, rt-VBR, nrt-VBR, UBR, ABR, or GFR. | enum | | +| ServiceCatType | This data element indicates the type of service category provided by AAL2. Valid values include but are not limited to "Audio" and "Multirate". | enum | | +| ServiceInstanceIdType | Operator-provided label associated by the Supplier Management System with connections. | string | | +| ServiceOutageRecordType | This data element provides the items in this record type. | struct | | +| SessionPolicyType | Specifies the rules governing GUI client sessions interconnected to the Supplier Management System. | struct | | +| SizeThresholdType | Specifies the threshold in the record set to raise alarms. | unsigned short | The value is interpreted as a whole number percentage (0-100%) of MaxSize. | +| SlotAssignmentType | Provides an association of a slot to a provisioning assignment. | struct showing the slot number and plug-in type | | +| SoftwareDownloadTrackingObjectIdType | Identifies one software download activity in progress or have failed to complete successfully. | TrackObjectIdType | | +| SONETSDHLinePMHistoryData | Provides the record structure itemizing the performance data collected in a 15-minute interval for monitoring point rsTTPF. | struct | | +| SONETSDHSectionAdaptationPMHistoryData | Provides the record structure itemizing the performance data collected in a 15-minute interval for monitoring points for au3CTPF or au4CTPF. | struct | | +| SONETSDHSectionPathPMHistoryData | Provides the record structure itemizing the performance data collected in a 15-minute interval for monitoring points for msTTPF, vc3CTPF or vc4CTPF. | | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------| +| SpanningTreeIndType | This boolean data element indicates whether or not a spanning tree algorithm is enabled. The value TRUE means enabled. | boolean | | +| SpecificProblems | This data element provides a listing of code values for all specific problems associated with a failure condition and alarm. | sequence of long | Values defined by supplier. | +| SSADTIndType | This boolean data element indicates whether or not the assured data transfer mechanism has been selected, with value TRUE indicating selection. | boolean | | +| SSCSParameterProfile1Type | This data element provides the values for a profile of kind SSCS Parameter Profile 1. | struct | | +| SSCSParameterProfile2Type | This data element provides the values for a profile of kind SSCS Parameter Profile 2. | struct | | +| SSCSTypeType | This data element identifies the SSCS type for the AAL. | enum | | +| SSTEDIndType | This boolean data element indicates whether or not the transmission error detection mechanisms have been selected, with value TRUE indicating selection. | boolean | | +| StateChangeDefinitionType | This data element provides a listing of all state and status variable changes triggered by a failure condition causing an alarm. | AttributeChangeSetType | Imported from ITU-T Rec. X.780. | +| StatusAttributeType | A pair showing the StatusValueType and completion percentage for the backup or restore of configuration data associated with an NE. | struct | | +| StatusValueType | Provides a choice of values between ProceduralStatusSetType and OtherStatus values indicating completion aspects. | union | | +| StructuredDataTransferType | This boolean data element indicates whether Structured Data Transfer (SDT) has been configured at the AAL. | boolean | | +| SubType | This data element identifies the AAL subtype. | enum | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|----------------------------------------------------------------------------| +| SupplyPowerIndType | This data element indicates whether or not the associated port provides power. | boolean | | +| SWPValueType | Shows a monitoring point and its associated sliding window parameters. | struct | | +| SynchChangeIndType | This boolean data element indicates whether or not synchronization of change in SSCS operation is transported on the connection, where the value TRUE implies its presence. | boolean | | +| SystemTimingType | Specifies the primary and secondary clock source for the NE. | struct of struct | | +| T303Type | This data element defines the maximum length of time in milliseconds that the ONT will wait for a reply to the "SETUP" message found at Layer 3 for the TMC or the CSC. | enum | | +| T396Type | This data element specifies the length of time that the ONT will wait for a reply to a "SETUP" message following the initial expiration of the timer T303. | enum | | +| TargetType | This data element provides a listing of network resources. | sequence of struct of Managed EntityIdType and string | Allows selection at system, NE, plug-in unit type, or specific slot level. | +| TargetActivityType | Provides an association of activityLevel, activityType and administrative domain to be associated with a user or a user group. | struct | | +| TCAdaptionProtocol MonitoringPM HistoryData | Provides the record structure itemizing the performance data collected in a 15-minute interval for monitoring points for tcAdaptorF. | | | +| TestHistoryType | This data element shows archived information on one completed testing activity for the Supplier Management System. | struct | | +| TestIterationNumType | This data element specifies the number of times that a test is to be repeated. | short | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| TestTrackingObjectIdType | This data element identifies a test in progress or pending within the Supplier Management System. | TrackingObjectId | | +| ThresholdDataProfileType | This data element is a listing of pairs: a thresholdDataProfile instance and a monitoring point type. | sequence of struct | | +| ThresholdDataType | This data element lists names of performance parameter with a threshold value for each. | struct | | +| ThresholdInfoType | This data element supplies information for a quality of service alarm event and provides the identity of the performance parameter, its observed value, and the upper and lower values that defined its threshold value range. | struct | | +| ThresholdsList | This data element lists relationships between monitoring termination point types and their associated threshold data profile. | sequence of struct
the first component indicating the type of monitoring point and the second giving the reference to a threshold Data profile | | +| ThresholdsType | This data element provides an association of monitoring point types associated with its threshold data profile name. | struct | | +| TimerCULengthType | This data element provides the value for the "combined use" timer Timer_CU. | long long | | +| TimingReferenceType | This data element defines how the internal timing is derived. | enum | | +| TotalEgressBandwidthType | This data element identifies the total amount of egress bandwidth for an ATM Interface. | long long | | +| TotalIngressBandwidthType | This data element identifies the total amount of ingress bandwidth for an ATM Interface. | long long | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| TrackingObjectIdType | This data element helps to identify the status of a requested activity whose time of completion takes longer than a few seconds. | unsigned long | Examples include TransferTrackingObjectIdType, SoftwareDownloadTrackingObjectType, and TestTrackingObjectIdType. | +| TrafficDescriptorProfileType | This data element provides the values for a profile of kind Traffic Descriptor. | struct | | +| TransferTrackingObjectIdType | Identifies either an outstanding file transfer activity in the Supplier Management System. | string | | +| TriggerTimeMatrixType | Specifies trigger times associated with a period schedule. | struct | | +| UNIProfileType | This data element provides the values for a profile of kind UNI. | struct | | +| UPCNPCDisagreementPMHistoryDataType | This data element provides the items in this record type. | struct | | +| UPCNPCIndicatorType | This boolean data element determines whether or not policing is performed for all connections at the interface. | boolean | | +| UsageStateType | This data element enumerates the value for the usage state variable. | enum | Valid enum values are idle, active, busy. Defined in ITU-T Rec. X.780. | +| UserGroupId | This is the operator-provided name for a grouping of users to the Supplier Management System. | UserLabelType | Cannot be the empty string. | +| UserGroupType | Provides the User Label for the user group, lists the users who are members of the group, and enumerates their target activities. | struct of UserGroupIdType, UserIdSeqType, and TargetActivitySeqType | | +| UserIdType | UserLabel assigned for users of the Supplier Management System. | UserLabel | | +| UserLabelType | Provides an identifier that is created and provided by the Operator or OMS to associate with a managed resource by the Supplier Management System. | string | | +| UserLoginPolicyType | Specifies the policy governing user login. | struct | | + +**Table A.1/Q.834.4 – Data elements and definitions** + +| Data element name | Definition | Syntax | Comments | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------| +| UserLoginPolicyViolationReasonType | Specifies one reason for rejecting the assignment of a password to a user. | enum | | +| UserType | Provides the user Id, the user groups to which the user belongs, and the users assigned target activities. | struct of
UserIdType,
UserGroupId
SeqType, and
Target
ActivitySeq
Type | | +| VersionType | Provides one version identifier of the hardware or software for the system by managedEntityIdType. | struct | | +| VoicePMHistoryDataType | This data element provides the items in this record type. | struct | | +| VoiceServicesProfileAAL1Type | This data element provides the values for a profile of kind Voice Services using AAL1. | struct | | +| VoiceServicesProfileAAL2ProfileType | This data element provides the values for a profile of kind Voice Services using AAL2. | struct | | +| VPVCPMHistoryDataType | This data element provides the items in this record type. | struct | | +| NOTE – If Q834Build module is considered for use in the management of other types of access technologies, then either the enumerated values should be expanded, or the syntax could be changed to short, with constants identifying the types of network elements to be constructed. | | | | + +# Annex B + +## Exceptions + +Table B.1 provides the list of all possible exceptions and circumstances under which they may be raised by one or more operations in this interface specification. + +**Table B.1/Q.834.4 – Exceptions** + +| Exception raised | Description | +|-------------------------|-------------------------------------------------------------------------------------------------| +| AccessDenied | System is not granted access to this interface object. | +| ActivationCompleted | Indicates that software activation has been executed so that activation cannot be cancelled. | +| ActivationFailure | Software activation process failure. | +| ActivityCompleted | The software activity has been executed and cannot be cancelled. | +| ActivityInProgress | This exception is raised when the software activity has been initiated and cannot be cancelled. | + +**Table B.1/Q.834.4 – Exceptions** + +| Exception raised | Description | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AddressLabelMismatch | The identified NE does not have the current DCN Address provided in the request. | +| APONLayerFailure | There was a APON protocol ranging failure between the OLT and the designed subtending node. | +| BackupInProgress | This exception is raised when the request is issued while the backup is in progress. | +| CannotAssignManagedEntityId | The Supplier Management System was unable to set the ManagedEntityId for the OLT, thus indicating that the Supplier Management System is unable to manage the OLT. | +| CannotRetrieveUserLabel | The Supplier Management System was unable to read the User Label provisioned on the OLT. | +| CollectionLimitation | The Supplier Management System cannot collect data for the given time duration and granularity period due to implementation restrictions. | +| CollectionPeriodPast | When period end time is lesser than or equal to the current time. | +| CommFailure | There was a DCN link failure between the NE and the Supplier Management System. | +| ConnectionAlreadyExists | There already exists a subnetwork connection with the same endpoints. | +| ConnectionCountExceeded | The maximum number of connections for the OLT or PON port has been exceeded with this request for service provisioning. | +| DCNTimeout | The DCN communications link between at least one of the NEs and the Supplier Management System is so congested that current state or status information cannot be transferred within a system defined synch time. | +| DeniedAccess | System is not granted access to the NE. | +| DuplicateProfileName | This exception is raised when the new profile name duplicates an existing profile name. | +| DuplicateSerialNumber | There exists other equipment of the same type with this serial number. | +| DuplicateUserGroupId | The id is already used for another User Group. | +| DuplicateUserId | Access control profile has already been established for this User Id. | +| DuplicateUserLabel | The User Label provided in the request has been used to label another managed entity of the same time. | +| EquipmentFailure | The NE currently has a failure condition preventing the requested transaction from being completed. | +| HWServicesMismatch | The replacement NE cannot perform the provisioned services. | +| InstallationFailure | Software installation process failure | +| InsufficientBW | The CAC algorithm indicates that requested service requires too much bandwidth for the OLT. | +| InsufficientMemory | There is insufficient memory on the NE to load the software unit. | +| InsufficientPONBW | The ONT or ONU cannot be ranged due to insufficient bandwidth on the APONLink. | + +**Table B.1/Q.834.4 – Exceptions** + +| Exception raised | Description | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InterfaceSpeedNotChangeable | The physical port cannot support the new interface speed or if the speed is not configurable. | +| IntervalCountTooLarge | This exception is raised when the requested intervals exceed the maximum supported by the Supplier Management System. The exception indicates the maximum allowed monitoring intervals supported by the Supplier Management System. | +| InvalidDCNAddress | The specified DCN address is not valid. | +| InvalidEquipmentCode | The equipment code does not conform to syntax. | +| InvalidExternalTime | External Time specified is not valid. | +| InvalidLocationId | The LLID specified is not valid. | +| InvalidPort | The specified PON port is not valid. | +| InvalidProtectionScheme | The network resource does not support the protection parameters specified in context with the port listing or if the protection units are ports of dissimilar physical path characteristic. | +| InvalidScheduler | The Scheduler parameters values are outside defined scope. | +| InvalidSerialNumSyntax | Syntax of the serial number provided does not match definition rules. | +| InvalidSlotAssignmentList | Expected slot provisioning rules are violated by slot assignment provided. | +| InvalidSoftwareTrackingObject | The referenced software tracking object is not the most recent associated with the installation of a software load on the NE. | +| InvalidStartTime | The start time is inconsistent with the current time, the current trigger time matrix, or the new stop time. | +| InvalidStopTime | The new stop time is inconsistent with the current trigger time matrix, the current time, or the new start time. | +| InvalidTestOperations | The requested self test operation is not valid. | +| InvalidTimeoutPeriod | Designated timeout period violates definition of valid values. | +| InvalidTrigger | The specified Trigger has values that cannot be interpreted by the Scheduler. | +| InvalidUserLabelSyntax | The specified UserLabel does not follow established rules for userLabel. | +| LockedAlready | The administrative state of the named managed entity is locked already and it has not been performing its normal function. | +| MaxSubtendingNodesExceeded | The maximum engineered number of subtending nodes for the identified PON interface has been exceeded with this request for service provisioning or reservation. | +| NoResponse | The ONT or ONU could not be ranged and the failure was due to something other than a detected problem with the serial number syntax, the APON Layer protocol, or duplicate or invalid User Labels. | +| NoSuchRecords | No records among the designated Record Sets match the selection criteria. | +| NoSynchInProgress | The exception is raised if there is no synchronisation process in progress. | + +**Table B.1/Q.834.4 – Exceptions** + +| Exception raised | Description | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotAvailableForTest | The specified CTP is not available for this test. | +| ParameterViolation | This exception is raised when the endpoint parameters do not match the protocol characteristics of the port, or when the values are out of range or invalid duplicates. | +| ProfileInUse | This exception is raised when the profile may not be deleted because it is still being used to characterize managed entities within the management jurisdiction of the Supplier Management System. | +| ProfileSuspended | The named profile(s) in the invocation have been suspended for use within the Supplier Management System by the OMS or operator. | +| RecordSetExists | The record set defined by the parameters of the creation request already exists in the Supplier Management System. | +| RemainingContainedManagedEntities | Contained circuit packs or equipment holders have not been deleted yet. | +| RemainingReservations | The node cannot be deleted as resource reservations still exist. | +| RemainingSubnetworkConnections | The node of plug-in unit cannot be deleted as there are remaining subnetwork connections. | +| ScheduleInUse | There are still activities scheduled by the named Scheduler. | +| SlotAlreadyAssigned | The requested slot is already provisioned. | +| SoftwareLoadHardwareMismatch | The former NE configuration data could not be downloaded to the NE because there were changes made to the NE hardware that caused an incapability. | +| SoftwareLoadHWMismatch | The designated software may not be loaded onto the equipment hardware since the version of the hardware cannot accept the software load. | +| SoftwareNotYetInstalled | The software may not be activated since it has not been installed yet. | +| SoftwareTrackingObjectInUse | There are outstanding software activities tracked by this object and it may not be deleted. | +| SourceUnreachable | The server holding the software load to be downloaded could not be reached by the OLT. | +| SynchNotScheduled | This exception is raised when the schedule modification references a NE for which no synchronization schedule has previously been established. | +| Timeout | The process duration reached a system-defined timeout before the process could complete. | +| TooManyNEs | The Supplier Management System cannot manage one more OLT. | +| TooManyRecords | The number of records selected for retrieval produces a response to the request that exceeds a predetermined size. | +| UncontrolledTestInProgress | The self test cannot be cancelled because of a uncontrolled test. | +| UnknownBackupProcess | The named transfer-tracking object identifying the file transfer process is unknown to the Supplier Management System. | + +**Table B.1/Q.834.4 – Exceptions** + +| Exception raised | Description | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UnknownConnection | The subnetwork connection is not known by the Supplier Management System. | +| UnknownDestinationServer | The identified destination server cannot be accessed by the transfer agent. | +| UnknownHistoryDataType | The history data type is unknown in the Supplier Management System. | +| UnknownManagedEntity | The specified Managed Entity is unknown to the Supplier Management System. | +| UnknownMonitoringPointTypes | The monitoringPointType is unknown to the Supplier Management System. | +| UnknownNE | Identified NE is unknown to the Supplier Management System. | +| UnknownOption | The given value of the archive administrativeState is "ShuttingDown". | +| UnknownParameters | The given monitored parameter is unknown in the Supplier Management System. | +| UnknownPort | The identified port is unknown to the Supplier Management System. | +| UnknownProfiles | This exception is raised if the profile name provided is unknown to the Supplier Management System and cannot be retrieved from the profile object repository. | +| UnknownRecordSet | Record set identified in the request is unknown to the Supplier Management System. | +| UnknownReservationId | The Supplier Management System does not recognize this Reservation Id. | +| UnknownRestoreProcess | The named transfer-tracking object identifying the file transfer process is unknown to the Supplier Management System. | +| UnknownScheduler | The named scheduler is unknown to the Supplier Management System. | +| UnknownService | The described Service is unknown to the Supplier Management System. | +| UnknownServiceInstance | The Service Instance is unknown to the Supplier Management System. | +| UnknownSlot | The requested slot is unknown in the NE. | +| UnknownSoftwareDownloadTrackObject | The named Software Unit (refers to software distributed to an NE) is unknown to the Supplier Management System. | +| UnknownSoftwareLoad | The specified software unit cannot be found. | +| UnknownSourceServer | The Supplier Management System and/or OLT cannot communicate with the Source Server. The DCN address is unknown or access is blocked. | +| UnknownSystemTimingSource | External time source unknown to the Supplier Management System. | +| UnknownTargets | The list of target activities is unknown to the Supplier Management System. | + +**Table B.1/Q.834.4 – Exceptions** + +| Exception raised | Description | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| UnknownTest | The test specified by the Test Tracking Object Id is not known in the Supplier Management System. | +| UnknownTransferProcess | The status of the identified transfer process could not be checked because it is unknown to the Supplier Management System. | +| UnknownUserGroupId | User Group is unknown to the Supplier Management System. | +| UnknownUserIds | This exception is raised when any userId is unrecognized. | +| UnrecognisedVersion | Equipment version provided does not match known values. | +| UserGroupNotEmpty | Non-empty User Group cannot be deleted. | +| UserLoginPolicyViolation | The specified assignment of a new password to a user violates the user login policy currently enforced by the Supplier Management System. | + +# Annex C + +## IDL files + +If the following files are saved as text files, then any subset of them can be compiled successfully using any OMG IDL compiler conforming to CORBA Specification 2.1 or later provided that the subset includes Q834Common.idl, and the standardized CosNaming.idl, CosNotifyFilter.idl, CosNotification.idl, X780.idl, and CosNotifyComm.idl.11 + +## C.1 Q834AccessControl.idl + +``` + +#ifndef __Q834_4_ACCESSCONTROL_DEFINED +#define __Q834_4_ACCESSCONTROL_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module AccessControl { + // Begin definitions from other idl files + + // From Q834Common + + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + typedef Q834Common::AdministrationDomainSeqType + AdministrationDomainSeqType; + +``` + +11 See references [18] and [19]. + +``` + +typedef Q834Common::UserLabelType UserLabelType; +typedef Q834Common::UserIdType UserIdType; +typedef Q834Common::PasswordType PasswordType; + +#define AccessDenied Q834Common::AccessDenied + +// End definitions from other idl files + +// Local data types + +struct UserLoginPolicyType { + short minUserId; // Minimum length of userid + short minPassword; // Minimum length of password + short passwordReuse; + short loginAttempts; + long passwordValidity; + boolean alphanumeric; //?should password contain alphanumeric mixture + boolean specialCharacters; + //?should password contain special characters + boolean repeatingCharacters; //?should password contain repeating + boolean disallowUserId; //disallow username in password +}; + +struct SessionPolicyType { + short sessionInactiveTime; + short inactiveUserIdDisableTime; + short multipleActiveLogins; +}; + +struct PasswordPolicyType { + UserLoginPolicyType userLoginPolicy; + SessionPolicyType sessionPolicy; +}; + +typedef sequence UserIdSeqType; + +enum ActivityLevelType { + monitorOnly, // read + allowedToExecute, // write + noAccess +}; + +typedef short ActivityType; + +struct TargetActivityType { + ActivityType type; + ActivityLevelType activityLevel; + AdministrationDomainSeqType AdministrationDomainSeq; +}; + +typedef sequence TargetActivitySeqType; + +enum UserLoginPolicyViolationReasonType { + minUserId, + minPassword, + passwordReuse, + loginAttempts, + passwordValidity, + alphanumeric, + specialCharacters, + repeatingCharacters, + +``` + +``` + + disallowUserId +}; + +typedef sequence +UserLoginPolicyViolationReasonSeqType; + typedef sequence UserGroupIdSeqType; + +struct UserType { + UserIdType userId; + UserGroupIdSeqType userGroupIdSeq; + TargetActivitySeqType TargetActivitySeq; +}; + +struct UserGroupType { + UserLabelType userGroupId; + UserIdSeqType userIdSeq; + TargetActivitySeqType TargetActivitySeq; +}; + +typedef sequence UserSeqType; +typedef sequence UserGroupSeqType; + +// Local exceptions + +exception UnknownUserIds { + UserIdSeqType userIdSeq; +}; +exception DuplicateUserId {}; +exception UnknownUserGroupId {}; +exception DuplicateUserGroupId {}; +exception UnknownTargets { + TargetActivitySeqType unknownTargetActivities; +}; +exception UserGroupNotEmpty {}; +exception UserLoginPolicyViolation { + UserLoginPolicyType userLoginPolicy; + UserLoginPolicyViolationReasonSeqType reason; +}; +// End local definitions + +valuetype AccessControlMgrValueType: itut_x780::ManagedObjectValueType { + + public PasswordPolicyType passwordPolicy; // GET + public UserSeqType userList; // GET + public UserGroupSeqType userGroupList; // GET +}; + +interface AccessControlMgr : itut_x780::ManagedObject { + +// define the activities + const short ALL_ACTIVITIES = 0; + const short ACCESS_CONTROL_MANAGEMENT = 1; + const short ALARM_EVENT_CONFIGURATION_MANAGEMENT = 2; + const short SCHEDULE_ACTIVITY = 3; + const short SOFTWARE_DOWNLOAD = 4; + const short TEST_CONTROL = 5; + const short SYNCHRONISE_CURRENT_EVENT_LIST = 6; + const short SYNCHRONISE_NE = 7; + const short RANGE_NE = 8; + const short REGISTER_SYSTEM = 9; + +``` + +``` + +const short RESERVE_RESOURCES = 10; +const short PROFILE_MANAGEMENT = 11; +const short PROVISION_NE = 12; +const short PROVISION_TELEPHONY_SERVICE = 13; +const short PROVISION_PACKETISED_DATA_SERVICES = 14; +const short PROVISION_VIDEO_SERVICE = 15; +const short PROVISION_LEASED_LINE_SERVICE = 16; +const short BULK_TRANSFER = 17; +const short HISTORY_DATA_COLLECTION = 18; +const short CONTROL_ARCHIVING = 19; +const short CONTROL_PERFORMANCE_MONITORING = 20; +const short CONFIGURATION_BACKUP_RESTORE = 21; + +// See 9.1.1.1 for the description of the behaviour of this operation + +void setPasswordPolicy( + in PasswordPolicyType passwordPolicy ) + raises ( AccessDenied); + +// See 9.1.1.2 for the description of the behaviour of this operation + +PasswordPolicyType passwordPolicyGet() + raises (AccessDenied); + +// See 9.1.1.3 for the description of the behaviour of this operation + +UserSeqType userListGet () + raises (AccessDenied); + +// See 9.1.1.4 for the description of the behaviour of this operation + +UserGroupSeqType userGroupListGet () + raises (AccessDenied); + +// See 9.1.1.5 for the description of the behaviour of this operation + +UserType userGet ( + in UserIdType userId ) + raises (AccessDenied, + UnknownUserIds); + +// See 9.1.1.6 for the description of the behaviour of this operation + +UserGroupType userGroupGet ( + in UserLabelType userGroupId) + raises (AccessDenied, + UnknownUserGroupId); + +// See 9.1.1.7 for the description of the behaviour of this operation + +void createUserGroup ( + in UserLabelType userGroupId, + in TargetActivitySeqType targetAdditions) + raises (DuplicateUserGroupId, + UnknownTargets, + AccessDenied); + +// See 9.1.1.8 for the description of the behaviour of this operation + +TargetActivitySeqType modifyUserGroup ( + in UserLabelType userGroupId, + +``` + +``` + + in TargetActivitySeqType targetAdditions, + in TargetActivitySeqType targetDeletions) + raises (UnknownUserGroupId, + UnknownTargets, + AccessDenied ); + +// See 9.1.1.9 for the description of the behaviour of this operation + + void deleteUserGroup ( + in UserLabelType userGroupId) + raises (AccessDenied, + UserGroupNotEmpty, + UnknownUserGroupId ); + +// See 9.1.1.10 for the description of the behaviour of this operation + + void addUsersToGroup ( + in UserLabelType userGroupId, + in UserIdSeqType userIdList ) + raises (AccessDenied, + UnknownUserGroupId); // duplicate users are ignored + +// See 9.1.1.11 for the description of the behaviour of this operation + + void deleteUsersFromGroup ( + in UserLabelType userGroupId, + in UserIdSeqType userIdList ) + raises (AccessDenied, + UnknownUserGroupId, + UnknownUserIds); + +// See 9.1.1.12 for the description of the behaviour of this operation + + TargetActivitySeqType getPermissionList ( + in UserIdType userId ) + raises (UnknownUserIds, + AccessDenied) ; + +// See 9.1.1.13 for the description of the behaviour of this operation + + TargetActivitySeqType modifyPermissionList ( + in UserIdType userId, + in TargetActivitySeqType targetAdditions, + in TargetActivitySeqType targetDeletions ) + raises (UnknownUserIds, + UnknownTargets, + AccessDenied); + +// See 9.1.1.14 for the description of the behaviour of this operation + + void createUser ( + in UserIdType userId, + in PasswordType password, + in TargetActivitySeqType targetAdditions ) + raises (DuplicateUserId, + UnknownTargets, + AccessDenied, + UserLoginPolicyViolation); + +``` + +``` + +// See 9.1.1.15 for the description of the behaviour of this operation + +void deleteUser ( + in UserIdType userId ) + raises (UnknownUserIds, + AccessDenied); + +// See 9.1.1.16 for the description of the behaviour of this operation + +void resetPassword ( + in UserIdType userId, + in PasswordType newPassword ) + raises (UnknownUserIds, + UserLoginPolicyViolation, + AccessDenied); + +}; // interface AccessControlMgr + +}; // module AccessControl + +}; // module q834_4 + +#endif + +``` + +## C.2 Q834Build.idl + +``` + +#ifndef __Q834_4_BUILD_DEFINED +#define __Q834_4_BUILD_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module Build { + + // begin definitions from other idl files + + // From Q834Common + typedef Q834Common::NameType NameType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + typedef Q834Common::UserLabelType UserLabelType; + + typedef Q834Common::SlotAssignmentSeqType SlotAssignmentSeqType; + typedef Q834Common::SerialNumType SerialNumType; + typedef Q834Common::NameSeqType NameSeqType; + typedef Q834Common::ExternalTimeType ExternalTimeType; + typedef Q834Common::SystemTimingType SystemTimingType; + typedef Q834Common::ReservationIdType ReservationIdType; + typedef Q834Common::ReservationIdSeqType ReservationIdSeqType; + typedef Q834Common::AdministrationDomainType AdministrationDomainType; + typedef Q834Common::VersionType VersionType; + typedef Q834Common::LoopbackLocationIdSeqType LoopbackLocationIdSeqType; + typedef Q834Common::AdministrativeStateType AdministrativeStateType; + typedef Q834Common::ServiceCategoryType ServiceCategoryType; + typedef Q834Common::ConformanceDefType ConformanceDefType; + typedef Q834Common::ATMOverbookingFactorType ATMOverbookingFactorType; + +``` + +``` + +#define AccessDenied Q834Common::AccessDenied +#define DuplicateUserLabel Q834Common::DuplicateUserLabel +#define InvalidSerialNumSyntax Q834Common::InvalidSerialNumSyntax +#define UnknownProfiles Q834Common::UnknownProfiles +#define InvalidUserLabelSyntax Q834Common::InvalidUserLabelSyntax +#define UnknownManagedEntity Q834Common::UnknownManagedEntity +#define ParameterViolation Q834Common::ParameterViolation +#define ProfileSuspended Q834Common::ProfileSuspended +#define UnknownNE Q834Common::UnknownNE + +// End definitions from other idl files + +// Local data types + +enum NEKindType { + BPONOLT, + BPONONT, + BPONONU, + BPONNT +}; + +struct ProtectionUnit +{ + ManagedEntityIdType portId; + boolean protectingInd; //TRUE = Protecting, FALSE = Protected +}; + +typedef sequence ProtectionUnitSeqType; + +enum ProtectionRatioType +{ + oneForOne, + oneForN, // N > 1 + mForN // M > 1 +}; + +enum AllowedProtectionSwitchingType +{ + automatic, + manual, + both +}; + +struct ProtectionParameterType +{ + ProtectionRatioType protectionRatio; + AllowedProtectionSwitchingType protectionSwitchingMethod; + boolean revertiveInd; // TRUE = revertive + long waitToRestore; // number of milliseconds before // reverting +}; + +enum SegmentEndpointIndType +{ + segment, + endpoint, + none +}; + +``` + +``` + +enum DirectionType +{ + unidirection, + bidirection +}; + +struct OpticalWaveLengthArrayType { + unsigned long wavelength; + DirectionType direction; +}; +typedef sequence +OpticalWaveLengthArraySeqType; + +// Local exceptions + +exception InvalidExternalTime {}; +exception UnrecognisedVersion {}; +exception DuplicateSerialNumber {}; +exception InvalidSlotAssignmentList {}; +exception RemainingContainedManagedEntities { + ManagedEntityIdSeqType containedManagedEntities ; +}; +exception UnknownNE {}; +exception UnknownSystemTimingSource {}; +exception RemainingReservations { + ReservationIdSeqType remainingReservationList; +}; +exception InvalidEquipmentCode {}; +exception SlotAlreadyAssigned {}; +exception UnknownSlot {}; +exception RemainingSubnetworkConnections { + ManagedEntityIdSeqType containedManagedEntities ; +}; +exception InterfaceSpeedNotChangeable {}; +exception InvalidProtectionScheme {}; + +// End local definitions + +valuetype BuilderValueType: itut_x780::ManagedObjectValueType { + public ManagedEntityIdSeqType createdNodes; // GET +}; + +interface Builder: itut_x780::ManagedObject { + +// See 9.2.1.1 for the description of the behaviour of this operation + +ManagedEntityIdType buildNode ( + in NEKindType nEKind, + in string supplierName, + in string location, + in VersionType hWVersion, + in SerialNumType serialNum, + in NameSeqType alarmSeverityProfiles, + in NameSeqType thresholdDataProfiles, + in SlotAssignmentSeqType slotAssignmentList, + in ManagedEntityIdType port, // OLT PON port + in string modelCode, + +``` + +``` + +in string systemTitle, +in VersionSeqType softwareVersions, +in UserLabelType nEUserLabel, +in ExternalTimeType externalTime, +in SystemTimingType systemTiming, +in AdministrationDomainType administrationDomain ) +raises (UnrecognisedVersion, + InvalidSerialNumSyntax, + DuplicateSerialNumber, + UnknownProfiles, + UnknownManagedEntity, + DuplicateUserLabel, + AccessDenied, + InvalidExternalTime, + UnknownSystemTimingSource, + ProfileSuspended); + +``` + +// See 9.2.1.2 for the description of the behaviour of this operation + +``` + +void assignUserLabelsToNE ( +in SerialNumType serialNum, +in UserLabelType nEUserLabel, +in AdministrationDomainType administrationDomain) +raises (InvalidSerialNumSyntax, + DuplicateSerialNumber, + DuplicateUserLabel, + AccessDenied); + +``` + +// See 9.2.1.3 for the description of the behaviour of this operation + +``` + +void modifyNode ( +in ManagedEntityIdType managedEntityId, +in SlotAssignmentSeqType newSlotAssignmentList, +in NameSeqType newAlarmSeverityProfiles, +in NameSeqType newThresholdDataProfiles, +in ManagedEntityIdType port, // OLT PON Port +in string newModelCode, +in UserLabelType newNEuserLabel, +in ExternalTimeType externalTime, +in AdministrationDomainType administrationDomain ) +raises (UnknownManagedEntity, + UnknownNE, + InvalidSlotAssignmentList, + UnknownProfiles, + DuplicateUserLabel, + AccessDenied, + InvalidExternalTime, + ProfileSuspended); + +``` + +// See 9.2.1.4 for the description of the behaviour of this operation + +``` + +void deleteNode ( +in ManagedEntityIdType managedEntityId ) +raises (UnknownNE, + RemainingContainedManagedEntities, + AccessDenied, + RemainingReservations, + RemainingSubnetworkConnections); + +``` + +// See 9.2.1.5 for the description of the behaviour of this operation + +``` + +void modifyPort ( + in ManagedEntityIdType physicalPathTPId, + in NameSeqType newAlarmSeverityProfiles, + in NameSeqType newThresholdDataProfiles, + in NameSeqType newPortProfiles, + in string newFrameFormat, + in AdministrativeStateType administrativeState, + in OpticalWaveLengthArraySeqType newOpticalWavelengthArray, + in LoopbackLocationIdSeqType newLoopbackLocationId, + in unsigned long newInterfaceSpeed, + in unsigned long arCTimer) + raises (UnknownManagedEntity, + UnknownProfiles, + AccessDenied, + InterfaceSpeedNotChangeable, + ProfileSuspended); + +// See 9.2.1.6 for the description of the behaviour of this operation + +ManagedEntityIdType buildPlugInUnit ( + in ManagedEntityIdType nEId, + in NameType alarmSeverityProfile, + in UserLabelType plugInUnitUserLabel, + in string modelCode, + in ManagedEntityIdType equipmentHolder, + in AdministrativeStateType administrativeState) + raises (UnknownNE, + DuplicateUserLabel, + AccessDenied, + UnknownManagedEntity, + InvalidEquipmentCode, + SlotAlreadyAssigned, + UnknownSlot, + InvalidSlotAssignmentList, + UnknownProfiles, + ProfileSuspended); + +// See 9.2.1.7 for the description of the behaviour of this operation + +ManagedEntityIdType modifyPlugInUnit ( + in ManagedEntityIdType plugInUnitId, + in NameType newAlarmSeverityProfile, + in string newModelCode, + in ManagedEntityIdType newEquipmentHolder, + in UserLabelType newPlugInUnitUserLabel, + in AdministrativeStateType newAdministrativeState) + raises (UnknownManagedEntity, + UnknownProfiles, + AccessDenied, + InvalidEquipmentCode, + SlotAlreadyAssigned, + UnknownSlot, + InvalidSlotAssignmentList, + InvalidUserLabelSyntax, + ProfileSuspended); + +// See 9.2.1.8 for the description of the behaviour of this operation + +void deletePlugInUnit ( + in ManagedEntityIdType plugInUnitId ) + raises (UnknownManagedEntity, + RemainingSubnetworkConnections, + +``` + +``` + + AccessDenied, + RemainingReservations); + +// See 9.2.1.9 for the description of the behaviour of this operation + +ManagedEntityIdType buildProtectionGrouping( + in ProtectionParameterType protectionParameters, + in ProtectionUnitSeqType protectionUnitList) + raises (InvalidProtectionScheme, + AccessDenied); + +// See 9.2.1.10 for the description of the behaviour of this operation + +void modifyProtectionParameters( + in ManagedEntityIdType protectionGroupingId, + in ProtectionParameterType newProtectionParameters) + raises (UnknownManagedEntity, + InvalidProtectionScheme, + AccessDenied); + +// See 9.2.1.11 for the description of the behaviour of this operation + +void modifyProtectionUnitList( + in ManagedEntityIdType protectionGroupingId, + in ProtectionUnitSeqType deltaProtectionUnitList, + in boolean addDeleteInd) // TRUE = add + raises (UnknownManagedEntity, + InvalidProtectionScheme, + AccessDenied); + +// See 9.2.1.12 for the description of the behaviour of this operation +void deleteProtectionGrouping( + in ManagedEntityIdType protectionGroupingId) + raises (UnknownManagedEntity, + AccessDenied); + +// See 9.2.1.13 for the description of the behaviour of this operation +ManagedEntityIdType buildBridge( + in NameType mACBridgeProfile, + in ManagedEntityIdType uplinkPort, + in ManagedEntityIdSeqType uNIPortList) + raises (UnknownProfiles, + AccessDenied, + UnknownManagedEntity, + ProfileSuspended); + +// See 9.2.1.14 for the description of the behaviour of this operation +void modifyBridgeProfile( + in ManagedEntityIdType bridgeId, + in NameType newMACBridgeProfile) + raises (UnknownProfiles, + AccessDenied, + UnknownManagedEntity, + ProfileSuspended); + +// See 9.2.1.15 for the description of the behaviour of this operation +void modifyBridgePortList( + in ManagedEntityIdType bridgeId, + in ManagedEntityIdSeqType deltaUNIPortList, + in boolean addDeleteInd) + raises (AccessDenied, + RemainingSubnetworkConnections, + UnknownManagedEntity); + +``` + +``` + +// See 9.2.1.16 for the description of the behaviour of this operation +void deleteBridge( + in ManagedEntityIdType bridgeId) + raises (AccessDenied, + RemainingSubnetworkConnections, + UnknownManagedEntity); + +// See 9.2.1.17 for the description of the behaviour of this operation +ManagedEntityIdType buildVPNetworkCTP( + in ManagedEntityIdType port, + in short vPI, + in NameType trafficDescriptorProfileName, + in ATMOverbookingFactorType overbookingFactor, + in UserLabelType userLabel, + in SegmentEndpointIndType segmentEndpointInd) + raises (AccessDenied, + UnknownManagedEntity, + UnknownProfiles, + ParameterViolation, + ProfileSuspended); + +// See 9.2.1.18 for the description of the behaviour of this operation +void deleteVPNetworkCTP ( + in ManagedEntityIdType vPNetworkCTP) + raises (AccessDenied, + RemainingSubnetworkConnections, + UnknownManagedEntity); + +// See 9.2.1.19 for the description of the behaviour of this operation + +ManagedEntityIdSeqType createdNodesGet () + raises (AccessDenied); + +}; // interface Builder + +}; // module Build + +}; // module q834_4 + +#endif + +``` + +## C.3 Q834Common.idl + +``` + +#ifndef __Q834_4_COMMON_DEFINED +#define __Q834_4_COMMON_DEFINED + +#include "CosNaming.idl" +#include "CosNotifyFilter.idl" +#include "itut_x780.idl" +#include "TimeBase.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module Q834Common { + +// Begin definitions from other idl files + +// From CosNaming +typedef CosNaming::Name NameType; + +``` + +``` + +// From CosNotifyFilter + typedef CosNotifyFilter::Filter FilterType; + +// From TimeBase + typedef TimeBase::UtcT UtcT; + +// From X780 + + typedef itut_x780::ProbableCauseType ProbableCauseType; + typedef itut_x780::AdministrativeStateType AdministrativeStateType; + typedef itut_x780::OperationalStateType OperationalStateType; + typedef itut_x780::ProceduralStatusSetType ProceduralStatusSetType; + typedef itut_x780::PerceivedSeverityType PerceivedSeverityType; + typedef itut_x780::AvailabilityStatusSetType AvailabilityStatusSetType; + typedef itut_x780::UsageStateType UsageStateType; + typedef itut_x780::ControlStatusSetType ControlStatusSetType; + typedef itut_x780::SpecificProblemSetType SpecificProblemSetType; + typedef itut_x780::BackedUpStatusType BackedUpStatusType; + typedef itut_x780::AttributeChangeSetType AttributeChangeSetType; + typedef itut_x780::SecurityAlarmCauseType SecurityAlarmCauseType; + +// End definitions from other idl files + +// Local data types + + struct NamingComponentType { + string type; // managed entity type + string id; + }; + + typedef sequence RDNTType; + typedef sequence RDNSeqType; + typedef sequence NameSeqType; + + enum IdType { + none, + x780_fineGrained, + x780_coarseGrained + }; + + typedef RDNTType MEIdType; + + struct ManagedEntityIdType { + IdType id; + MEIdType mEId; + }; + + typedef sequence ManagedEntityIdSeqType; + typedef string UserLabelType; + typedef string SerialNumType; + typedef string VersionType; + typedef string PlugInUnitType; + typedef sequence UserLabelSeqType; + + typedef UserLabelType AdministrationDomainType; + typedef sequence AdministrationDomainSeqType; + + typedef string DCNAddressType; + + typedef unsigned short RecordKindType; + + typedef string PlugInType; + +``` + +``` + +// SlotAssignmentList +struct SlotAssignmentType { + short number; + PlugInType plugIn; // empty string implies that the slot is not + // provisioned for any particular type of plug-in unit +}; + +typedef sequence SlotAssignmentSeqType; +typedef string ReservationIdType; +typedef sequence ReservationIdSeqType; +typedef string ServiceInstanceIdType; +typedef sequence ServiceInstanceIdSeqType; + +typedef UtcT GeneralizedTimeType; +typedef GeneralizedTimeType ExternalTimeType; + +enum SystemTimingSourceType { + internalTimingSource, // freerun + remoteTimingSource, // external + slaveTimingTerminationSignal +}; + +typedef ManagedEntityIdType TimingSourceIdType ; + +struct SystemTimingComponentType { + SystemTimingSourceType type; + TimingSourceIdType id; +}; + +struct SystemTimingType { + SystemTimingComponentType Primary; + SystemTimingComponentType Secondary; +}; + +typedef UserLabelType UserIdType; +typedef string PasswordType; + +/* +All zeros indicate a loopback request directed at all connection +points having an LLID in the flow. All ones indicate a loopback +request directed at the endpoint (segment or connection endpoint). +'x6A'H indicates no designated CP for loopback, and therefore no +loopback should be performed. All other values for LLID indicate +a loopback request directed at a specific LLID location. +*/ +typedef sequence LoopbackLocationIdSeqType; + +typedef string FilenameType; // specifies the complete path + +enum StatusType { + procedural_status, + other +}; + +enum OtherStatusType { + completed_success, + completed_failure, + activityInProgress, + unknownstatus +}; + +``` + +``` + +union StatusValueType switch (StatusType) { + case procedural_status: ProceduralStatusSetType proceduralStatusSet; + case other: OtherStatusType otherStatus; +}; + +struct StatusAttributeType { + StatusValueType valueOfStatus; + ManagedEntityIdType ne; + short percentComplete; +}; + +typedef sequence StatusAttributeSeqType; + +typedef unsigned long TrackingObjectIdType; + +typedef TrackingObjectIdType TransferTrackingObjectIdType; + +typedef any RecordType; // based on recordType (Values defined in +Q834Common::RecordSetType) Need definition of recordType and individual type of +records +typedef sequence RecordSeqType; + +typedef unsigned long long NotificationIdentifierType; // will be replaced +// by NotifIDType defined in X.780 when that definition +is changed from "long" to "long long" + +typedef sequence NotificationIdentifierSeqType; + +typedef stringMonitoredParameterType; // Values defined in +Q834Common::MonitoringParameter +typedef unsigned short MonitoringKindType; // values defined in +Q834Common::PMCategory interface + +struct EndPointType { + ManagedEntityIdType portId; + any endPointParameters; + NameSeqType serviceCharacteristicsProfiles; +}; + +/* +endPointParameters: service specific parameters, structures to be +provided as part of implementation. An ATM connection for example +would have the VPI, VCI parameters. +*/ + +enum AlarmStatusComponentType { + AS_UnderRepair, + AS_Critical, + AS_Major, + AS_Minor, + AS_AlarmOutstanding +}; + +typedef sequence AlarmStatusSeqType; + +struct EquipmentHolderAddressType { + short shelfNumber; + short slotNumber; +}; + +/* + +``` + +If the equipment holder is a shelf, the slot number is 0. If the equipment holder is a slot, then both the slot number and shelf numbers are greater than or equal to 1. + +\*/ + +/\* + +The supplier provides a customization of the DiscoveryEventSupplier interface by defining the const string plugInUnit names. It will be up to the operator to enforce consistency and non-duplication across multiple supplier's solutions. + +\*/ + +typedef sequence PlugInUnitSeqType; + +``` +struct NEFSANType { + ManagedEntityIdType managedEntityId; + AdministrativeStateType administrativeState; + OperationalStateType operationalState; + GeneralizedTimeType externalTime; + string locationName; + string supplierName; + VersionType hardwareVersion; + VersionSeqType softwareVersions; + string serialNumber; + NameSeqType alarmSeverityAssignmentProfileNames; + AlarmStatusSeqType alarmStatusValues; + NameSeqType thresholdDataNames; + ManagedEntityIdSeqType supportedByManagedEntityList; + UserLabelType userLabel; +}; +/* +SupportedByManagedEntityList should include the instance of Software +controlling the NE. +*/ + +/* +Next, structs are defined that form the basis for equipment +inventory information discovered at installation or with equipment +rearrangement actions. Any one of these structs is subsequently +identified as Mestruct in the DiscoveryEventSupplier interface +specification. +*/ + +struct OLTType { + NEFSANType nEFSAN; + ManagedEntityIdSeqType subtendingNEFSANList; +}; + +struct ONTType { + NEFSANType nEFSAN; + ManagedEntityIdType upstreamNEFSAN; +}; + +struct ONUType { + NEFSANType nEFSAN; + ManagedEntityIdType upstreamNEFSAN; + ManagedEntityIdSeqType subtendingNEFSANList; +}; +``` + +``` + +struct NTType { + NEFSANType nEFSAN; + ManagedEntityIdType upstreamNEFSAN; +}; + +struct EquipmentHolderFType { + ManagedEntityIdType equipmentHolderFId; + ManagedEntityIdType containingNEId; + EquipmentHolderAddressType equipmentHolderAddress; + boolean slotStatus; + PlugInUnitSeqType expectedPlugInUnits; + string SoftwareLoad; + NameType alarmSeverityAssignmentProfileName; + AlarmStatusSeqType alarmStatusValues; + OperationalStateType operationalState; +}; + +struct PlugInUnitFType { + ManagedEntityIdType plugInUnitFId; + ManagedEntityIdType containingNEId; + EquipmentHolderAddressType containingSlotAddress; + AdministrativeStateType administrativeState; + AvailabilityStatusSetType availabilityStatus; + OperationalStateType operationalState; + string modelCode; + string functionCode; + string supplierName; + VersionType hardwareVersion; + string serialNumber; + short portCount; + NameSeqType alarmSeverityAssignmentProfileNames; + NameSeqType thresholdDataNames; + UserLabelType circuitPackUserLabel; + ManagedEntityIdSeqType supportedByManagedEntityList; +}; + +enum ServiceCategoryType { + CBR, + UBR, + RTVBR, + NRTVBR, + AdaptiveBR, + GFR +}; + +enum ConformanceDefType { + CBR1, + UBR1, + UBR2, + VBR1, + VBR2, + VBR3, + ABR, + GFR1, + GFR2 +}; + +struct ATMOverbookingFactorType { + ServiceCategoryType serviceCategory; + ConformanceDefType conformanceDef; + short overbookingFactor; // percentage: 100 = no overbooking +}; + +struct AlarmLogRecordType { + +``` + +``` + + long long recordId; + ManagedEntityIdType mEId; + GeneralizedTimeType loggingTime; + short probableCause; + PerceivedSeverityType severity; + GeneralizedTimeType eventTime; + ManagedEntityIdType backupEntityId; + boolean backedupStatus; + boolean serviceAffectingInd; + ServiceInstanceIdSeqType affectedServices; + NotificationIdentifierType notificationId; + NotificationIdentifierSeqType correlatedNotifications; + string monitoredParameter; + long long thresholdValue; + long long observedValue; + string additionalText; +}; + +struct SecurityAlarmLogRecordType { + long long recordId; + ManagedEntityIdType mEId; + GeneralizedTimeType loggingTime; + short securityAlarmCause; // values defined in X.780 + GeneralizedTimeType eventTime; + ManagedEntityIdType securityAlarmDetector; + ManagedEntityIdType serviceUser; + ManagedEntityIdType serviceProvider; + NotificationIdentifierType notificationId; + NotificationIdentifierSeqType correlatedNotifications; + string additionalText; +}; + +struct ServiceOutageRecordType { + long long recordId; + ServiceInstanceIdType affectedService; + GeneralizedTimeType loggingTime; + GeneralizedTimeType outageStartTime; + GeneralizedTimeType outageEndTime; + NotificationIdentifierSeqType correlatedNotifications; +}; + +struct AAL1PMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long HeaderErrors; + unsigned long long LostCells; + unsigned long long CellMisinsertion; + unsigned long long BufferUnderflows; + unsigned long long SequenceViolations; + unsigned long long SDTPtrReframes; + unsigned long long SDTPtrParityCheckFailures; +}; + +struct AAL2PMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; unsigned long long CPSInPkts; + unsigned long long CPSOutPkts; + unsigned long long BufferUnderflow; +}; + +``` + +``` + + unsigned long long BufferOverflow; + unsigned long long ParityErrors; + unsigned long long SeqNumErrors; + unsigned long long CPS_OSFMismatchErrors; + unsigned long long CPS_OSFErrors; + unsigned long long CPSHECErrors; + unsigned long long OversizedSDUErrors; + unsigned long long ReassemblyErrors; + unsigned long long HECOverlapErrors; + unsigned long long UIIErrors; + unsigned long long CIDErrors; +}; + +struct AAL5PMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long SumOfInvalidCSFieldErrors; + unsigned long long CRCViolations; + unsigned long long BufferOverflows; + unsigned long long EncapProtocolErrors; +}; + +struct APONPMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long ES; + unsigned long long FEES; +}; + +struct ATMTrafficLoadHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long CellsReceived; + unsigned long long CellsTransmitted; +}; + +struct DS1PMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long ESP; + unsigned long long BESP; + unsigned long long SESP; + unsigned long long UASP; + unsigned long long ESPFE; + unsigned long long BESPFE; + unsigned long long SESPFE; + unsigned long long UASPFE; +}; + +struct DS3PMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + +``` + +``` + + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long ESL; + unsigned long long SESL; + unsigned long long CVCPPorCVPP; + unsigned long long ESCPPorESPP; + unsigned long long SESCPPorSESPP; + unsigned long long UASCPPorUASPP; +}; + +struct ElPMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long ESP; + unsigned long long BESP; + unsigned long long SESP; + unsigned long long UASP; + unsigned long long ESPFE; + unsigned long long BESPFE; + unsigned long long SESPFE; + unsigned long long UASPFE; +}; + +struct EthernetHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long SingleCollisionFrame; + unsigned long long MultipleCollisionFrames; + unsigned long long SQE; + unsigned long long DeferredTransmission; + unsigned long long LateCollision; + unsigned long long ExcessiveCollision; + unsigned long long InternalMACTransmitError; + unsigned long long CarrierSenseError; + unsigned long long BufferOverflows; + unsigned long long AlignmentError; + unsigned long long FrameTooLongs; + unsigned long long FCSErrors; + unsigned long long InternalMACReceiveError; +}; + +struct MACBridgePMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long NumberofSuppressedIntervals; + unsigned long long BridgeLearningEntryDiscard; +}; + +struct MACBridgePMPortHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + +``` + +``` + + unsigned long long ForwardedFrame; + unsigned long long DelayExceededDiscard; + unsigned long long MTUExceededDiscard; + unsigned long long ReceivedFrame; + unsigned long long ReceivedAndDiscarded; +}; + +struct UpcNpcDisagreementPMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long DiscardedCells; + unsigned long long DiscardedCLP_0Cells; + unsigned long long TaggedCLP_0Cells; +}; + +struct VoicePMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long IncomingCallAttempts; + unsigned long long OutgoingCallAttempts; + unsigned long long VoicePortBufferOverflows; + unsigned long long VoicePortBufferUnderflows; +}; + +struct VpVcPMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long Lost0plus1UserInformationCells; + unsigned long long Lost0UserInformationCells; + unsigned long long MisinsertedUserInformationCells; + unsigned long long Transmitted0plus1UserInformationCells; + unsigned long long Transmitted0UserInformation; + unsigned long long ImpairedBlock; +}; + +struct SONETSDHLinePMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long ErroredSecondsP; + unsigned long long SeverelyErroredSecondsP; + unsigned long long BackgroundBlockErrorP; + unsigned long long OutOfFrameSecondsP; + unsigned long long UnavailableSecondsP; +}; + +struct SONETSDHSectionPathPMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long ErroredSecondsP; + +``` + +``` + + unsigned long long SeverelyErroredSecondsP; + unsigned long long BackgroundBlockErrorP; + unsigned long long OutOfFrameSecondsP; + unsigned long long UnavailableSecondsP; + unsigned long long FailureCountP; + unsigned long long ErroredSecondsTypeAP; + unsigned long long ErroredSecondsTypeBP; + unsigned long long ErroredSecondsPFE; + unsigned long long SeverelyErroredSecondsPFE; + unsigned long long BackgroundBlockErrorPFE; + unsigned long long OutOfFrameSecondsPFE; + unsigned long long UnavailableSecondsPFE; + unsigned long long FailureCountPFE; + unsigned long long ErroredSecondsTypeAPFE; + unsigned long long ErroredSecondsTypeBPFE; +}; + +struct SONETSDHSectionAdaptationPMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long PointerJustificationHighCountP; + unsigned long long PointerJustificationLowCountP; +}; + +struct TCAdaptationProtocolMonitoringPMHistoryDataType { + long long recordId; + ManagedEntityIdType monitoringPoint; + GeneralizedTimeType periodEndTime; + boolean suspectIntervalFlag; + NameType ThresholdDataId; + unsigned long long DiscardedCellsHECViolationP; + unsigned long long ErroredCellsHECViolationP; +}; + +``` + +//Common exceptions + +``` + +exception AccessDenied {}; +exception CommFailure {}; +exception ConnectionCountExceeded {}; +exception DuplicateUserLabel {}; +exception EquipmentFailure {}; +exception InsufficientBW {}; +exception InsufficientPONBW { + ManagedEntityIdType ponPORT; +}; +exception InvalidSerialNumSyntax {}; +exception InvalidUserLabelSyntax {}; +exception MaxSubtendingNodesExceeded {}; +exception Timeout {}; +exception UnknownManagedEntity { + ManagedEntityIdType managedEntityId; +}; +exception UnknownNE { + ManagedEntityIdSeqType unknownNEs; +}; +exception UnknownPort {}; +exception UnknownProfiles {}; +exception UnknownReservationId {}; +exception UnknownScheduler {}; +exception InvalidScheduler {}; +exception DCNTimeout {}; + +``` + +``` + +exception UnknownDestinationServer {}; +exception UnknownServiceInstance {}; +exception DeniedAccess {}; +exception BackupInProgress {}; +exception InvalidStartTime {}; +exception InvalidStopTime {}; +exception ParameterViolation {}; +exception UnknownRecordSet {}; +exception SynchInProgress {}; +exception ProfileSuspended { + NameSeqType profilesSuspended; +}; + +``` + +``` + +module ProbableCauseConst { + +``` + +``` + + const string moduleName = "q834_4::Q834Common::ProbableCauseConst"; + +``` + +``` + + interface ProbableCause { + +``` + +``` + + /* + +``` + +``` + + For X.780 probableCause refer to itut_x780::ProbableCauseConst. + +``` + +``` + + */ + +``` + +``` + + // Additional ProbableCause values needed for BPON + +``` + +``` + + const unsigned short LOSS_OF_PATH_POINTER = 1; + +``` + +``` + + const unsigned short STS_PAYLOAD_LABEL_MISMATCH = 2; + +``` + +``` + + const unsigned short STS_PATH_UNEQUIPPED = 3; + +``` + +``` + + const unsigned short ALARM_INDICATION_SIGNAL = 4; + +``` + +``` + + const unsigned short REMOTE_FAILURE_INDICATION = 5; + +``` + +``` + + const unsigned short REMOTE_ALARM_INDICATION = 6; + +``` + +``` + + const unsigned short ALARM_INDICATION_SIGNAL_PATH = 7; + +``` + +``` + + const unsigned short + +``` + +``` + +ALARM_INDICATION_SIGNAL_CUSTOMER_INSTALLATION = 8; + +``` + +``` + + const unsigned short LOSS_OF_SIGNAL_TO_ALL_ONU_ONU = 9; + +``` + +``` + + const unsigned short LOSS_OF_SIGNAL_ONU_OR_ONT = 10; + +``` + +``` + + const unsigned short LOSS_OF_ACKNOWLEDGEMENT_ONU_OR_ONT = 11; + +``` + +``` + + const unsigned short PLOAMCL_ONU_OR_ONT = 12; //Physical Layer OAM + +``` + +``` + +Cell Loss + +``` + +``` + + const unsigned short LOCD_ONU_OR_ONT = 13; // Loss of Cell + +``` + +``` + +Delineation + +``` + +``` + + const unsigned short CPHE_ONU_OR_ONT = 14; // Cell Phase Error + +``` + +``` + + const unsigned short PEE_ONU_OR_ONT = 15; + +``` + +``` + + const unsigned short RF_ONU_OR_ONT = 16; // Ranging Failure + +``` + +``` + + const unsigned short BED_ONU_OR_ONT = 17; // Block Error Detection + +``` + +``` + + const unsigned short SD_ONU_OR_ONT = 18; // Signal Degraded + +``` + +``` + + const unsigned short REI_ONU_OR_ONT = 19; // Remote Error + +``` + +``` + +Indication + +``` + +``` + + const unsigned short UM_ONU_OR_ONT = 20; // Unknown Message + +``` + +``` + + const unsigned short LM_ONU_OR_ONT = 21; // Link Mismatch + +``` + +``` + + const unsigned short REMOTE_DEFECT_INDICATION = 22; // Signal + +``` + +``` + +Degraded + +``` + +``` + + const unsigned short MAJOR_POWER_FAILURE = 23; + +``` + +``` + + const unsigned short + +``` + +``` + +REMOTE_ALARM_INDICATION_FAR_END_CUSTOMER_INSTALLATION = 24; + +``` + +``` + + const unsigned short LOSS_OF_ATM_CELL_DELINEATION = 25; + +``` + +``` + + const unsigned short LOW_BATTERY_THRESHOLD = 26; + +``` + +``` + + const unsigned short DIAGNOSTIC_TEST_FAILURE = 27; // See below + +``` + +``` + +comment + +``` + +``` + + const unsigned short LOSS_OF_DCN_LINK = 28; + +``` + +``` + + const unsigned short CELL_STARVATION = 29; + +``` + +``` + + const unsigned short UNEXPECTED_PLUGIN = 30; + +``` + +``` + + const unsigned short IMPROPER_CARD_REMOVAL = 31; + +``` + +``` + + const unsigned short SLOT_CARD_MISMATCH = 32; + +``` + +``` + +const unsigned short LOS_LAN = 33; // Loss of carrier on Bridge +LAN port +const unsigned short PERSISTENT_IMPAIRMENT = 34; +}; // interface ProbableCause +}; // module ProbableCauseConst + +interface MonitoringParameter { +/* +Names for monitored performance and traffic parameters +*/ + +const string allParameters = "AllParameters"; +const string aAL1HeaderErrors = "AAL1HeaderErrors"; +const string allTypesCellsDiscarded = "AllTypesCellsDiscarded"; +const string aTMProtocolErrors = "ATMProtocolErrors"; +const string bESFEP = "BESFEP"; +const string bESP = "BESP"; +const string bufferOverflows = "BufferOverflows"; +const string bufferUnderflows = "BufferUnderflows"; +const string cellDelineationAnomalies = "CellDelineationAnomalies"; +const string cellMisinsertion = "CellMisinsertion"; +const string cRCViolations = "CRCViolations"; +const string cVCP = "CVCP"; +const string cVL = "CVL"; +const string cVPP = "CVPP"; +const string cVS = "CVS"; +const string discardedAllTypeCellsduetoNPC = +"DiscardedAllTypeCellsduetoNPC"; +const string discardedAllTypeCellsduetoUPC = +"DiscardedAllTypeCellsduetoUPC"; +const string discardedPriorityCellsduetoNPC = +"DiscardedPriorityCellsduetoNPC"; +const string discardedPriorityCellsduetoUPC = +"DiscardedPriorityCellsduetoUPC"; +const string encapProtocolErrors = "EncapProtocolErrors"; +const string eSCPP = "ESCPP"; +const string eSPONT = "ESPONT"; +const string eSL = "ESL"; +const string eSP = "ESP"; +const string eSPP = "ESPP"; +const string eSS = "ESS"; +const string excessiveCollisions = "ExcessiveCollisions"; +const string fCSErrors = "FCSErrors"; +const string frameTooLongs = "FrameTooLongs"; +const string hECViolations = "HECViolations"; +const string impairedBlocks = "ImpairedBlocks"; +const string lateCollisions = "LateCollisions"; +const string lostCells = "LostCells"; +const string lostPriorityUserInformationCells = +"LostPriorityUserInformationCells"; +const string lostUserInformationCells = "LostUserInformationCells"; +const string misinsertedUserInformationCells = +"MisinsertedUserInformationCells"; +const string priorityCellsDiscarded = "PriorityCellsDiscarded"; +const string sDTPointerReframes = "SDTPointerReframes"; +const string sDTPointerParityCheckFailures = +"SDTPointerParityCheckFailures"; +const string sequenceViolations = "SequenceViolations"; +const string sESCPP = "SESCPP"; +const string sESPONT = "SESPONT"; +const string sESL = "SESL"; +const string sESP = "SESP"; +const string sESPP = "SESPP"; +const string sESS = "SESS"; + +``` + +``` + +const string sumOfInvalidCSFieldErrors = "SumOfInvalidCSFieldErrors"; +const string uASPONT = "UASPONT"; +const string uASCPP = "UASCPP"; +const string uASP = "UASP"; +const string uASPP = "UASPP"; +const string incomingCallAttempts = "IncomingCallAttempts"; +const string outgoingCallAttempts = "OutgoingCallAttempts"; +const string voicePortBufferOverflows = "VoicePortBufferOverflows"; +const string voicePortBufferUnderflows = "VoicePortBufferUnderflows"; +const string cPSInPkts = "CPSInPkts"; +const string cPSOutPkts = "CPSOutPkts"; +const string bufferUnderflow = "BufferUnderflow"; +const string bufferOverflow = "BufferOverflow"; +const string parityErrors = "ParityErrors"; +const string seqNumErrors = "SeqNumErrors"; +const string cPS_OSFMismatchErrors = "CPS_OSFMismatchErrors"; +const string cPS_OSFErrors = "CPS_OSFErrors"; +const string cPSHECErrors = "CPSHECErrors"; +const string oversizedSDUErrors = "OversizedSDUErrors"; +const string reassemblyErrors = "ReassemblyErrors"; +const string hECOverlapErrors = "HECOverlapErrors"; +const string uUIErrors = "UUIErrors"; +const string CIDErrors = "CIDErrors"; + +}; // interface MonitoringParameter + +interface PMCategory { + const unsigned short DS1_PM = 1; + const unsigned short DS3_PM = 2; + const unsigned short E1_PM = 3; + const unsigned short E3_PM = 4; + const unsigned short VP_PM = 5; + const unsigned short VC_PM = 6; + const unsigned short ETHERNET_PM = 7; + const unsigned short TC_ADAPTOR_PM = 8; + const unsigned short VOICE_PM = 9; + const unsigned short APON_PM = 10; + const unsigned short MACBRIDGE_PM = 11; + const unsigned short MACBRIDGEPORT_PM = 12; + const unsigned short ATMTRAFFICLOAD_PM = 13; + const unsigned short AAL1_PM = 14; + const unsigned short AAL2_PM = 15; + const unsigned short AAL5_PM = 16; + const unsigned short UPCNPC_PM = 17; + const unsigned short DBA_PM = 18; + const unsigned short SONET_SDH_LINE_PM = 19; + const unsigned short SONET_SDH_SECTION_PATH_PM = 20; + const unsigned short SONET_SDH_SECTION_ADAPTATION_PM = 21; + const unsigned short CALL_STATS_PM = 22; + const unsigned short VIDEO_PM = 23; + +}; // interface PMCategory + +interface RecordSetType { + +// Beginning of Values for RecordKindType +// Values 1-99 reserved for HistoryDataType + + const unsigned short DS1PMHISTORYDATA = 1; + const unsigned short DS3PMHISTORYDATA = 2; + const unsigned short E1PMHISTORYDATA = 3; + const unsigned short E3PMHISTORYDATA = 4; + const unsigned short VPVCPMHISTORYDATA = 5; + const unsigned short AAL1PMHISTORYDATA = 6; + +``` + +``` + + const unsigned short AAL2PMHISTORYDATA = 7; + const unsigned short AAL5PMHISTORYDATA = 8; + const unsigned short UPCNPCDISAGREEMENTPMHISTORYDATA = 9; + const unsigned short ETHERNETPMHISTORYDATA = 10; + const unsigned short VOICEPMHISTORYDATA = 11; + const unsigned short MACBRIDGEPORTPMHISTORYDATA = 12; + const unsigned short MACBRIDGEPMHISTORYDATA = 13; + const unsigned short APONPMHISTORYDATA = 14; + const unsigned short SONESTDHLINEPMHISTORYDATA = 15; + const unsigned short SONESTDHSECTIONADAPTATIONPMHISTORYDATA = 16; + const unsigned short SONESTDHSECTIONPATHPMHISTORYDATA = 17; + const unsigned short TCADAPTATIONPROTOCOLMONITORINGPMHISTORYDATA = 18; + const unsigned short ALARMLOGRECORD = 100; + const unsigned short SECURITYALARMLOGRECORD = 101; + const unsigned short SERVICEOUTAGERECORD = 102; + +// End of Values for RecordKindType + +}; // interface RecordSetType + +interface PhysicalLayerLoopback { + + // Beginning of Values for LoopbackTestType + + const unsigned short LINELOOPBACK = 1; + const unsigned short PAYLOADLOOPBACK = 2; + const unsigned short INWARDLOOPBACK = 3; + const unsigned short DUALLOOPBACK = 4; + const unsigned short FACILITYLOOPBACK = 5; + const unsigned short TERMINALLOOPBACK = 6; + +// End of Values for LoopbackTestType + +}; // interface PhysicalLayerLoopback + +}; // module Q834Common + +}; // module q834_4 +#endif + +``` + +## C.4 Q834ControlArchive.idl + +``` + +#ifndef __Q834_4_CONTROLARCHIVE_DEFINED +#define __Q834_4_CONTROLARCHIVE_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module ControlArchive { + +// begin definitions from other idl files + +// From Q834Common + typedef Q834Common::NameType NameType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + typedef Q834Common::AdministrativeStateType AdministrativeStateType; + typedef Q834Common::FilterType FilterType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::OperationalStateType OperationalStateType; + typedef Q834Common::RecordType RecordType; + } +} + +``` + +``` + +typedef Q834Common::RecordSeqType RecordSeqType; +typedef Q834Common::UserLabelSeqType UserLabelSeqType; +typedef Q834Common::RecordKindType RecordKindType; + +#define AccessDenied Q834Common::AccessDenied +#define DuplicateUserLabel Q834Common::DuplicateUserLabel +#define Timeout Q834Common::Timeout +#define UnknownRecordSet Q834Common::UnknownRecordSet + +// End definitions from other idl files + +// Local data types + +enum FullActionType { + halt, // indicates that the log should stop writing any more records +if the log is full + wrap // indicates that the log should delete old records if the log is +full. +}; + +typedef unsigned long long MaxSizeType; +typedef unsigned short SizeThresholdType; // 0-100% +typedef unsigned long long CurrentSizeType; + +struct RecordSetStatusType { + CurrentSizeType currentSize; + OperationalStateType operationalState; + MaxSizeType maxSize; + SizeThresholdType sizeThreshold; + NameType filterName; + FullActionType fullAction; + AdministrativeStateType administrativeState; + RecordKindType recordKind; + UserLabelType recordSetUserLabel; +}; + +enum CreationModeType { + operatorDefined, + initialList, + either +}; + +// Local exceptions + +exception RecordSetExists {ManagedEntityIdType recordSetId;}; +exception LockedAlready {}; +exception UnknownOption {}; +exception NoSuchRecords {}; +exception TooManyRecords {}; + +// End local definitions + +interface RecordSetMgr : itut_x780::ManagedObject { + +// See 9.4.1.1 for the description of the behaviour of this operation + + ManagedEntityIdType createLog ( + in UserLabelType recordSetUserLabel, + in AdministrativeStateType administrativeState, + +``` + +``` + + in NameType filterName, + in FullActionType fullAction, + in MaxSizeType maxSize, + in SizeThresholdType sizeThreshold) + raises (RecordSetExists, + DuplicateUserLabel, + AccessDenied); + +// See 9.4.1.2 for the description of the behaviour of this operation + +ManagedEntityIdType createArchive ( + in UserLabelType recordSetUserLabel, + in AdministrativeStateType administrativeState, + in RecordKindType recordKind, + in MaxSizeType maxSize) + raises (RecordSetExists, + DuplicateUserLabel, + AccessDenied); + +// See 9.4.1.3 for the description of the behaviour of this operation + +RecordSetStatusType getStatusAttributes ( + in ManagedEntityIdType recordSetId) + raises (AccessDenied, UnknownRecordSet); + +// See 9.4.1.4 for the description of the behaviour of this operation + +void suspendArchive ( + in ManagedEntityIdType recordSetId) + raises (AccessDenied, UnknownRecordSet); + +// See 9.4.1.5 for the description of the behaviour of this operation + +void resumeArchive ( + in ManagedEntityIdType recordSetId) + raises (AccessDenied, UnknownRecordSet); + +// See 9.4.1.6 for the description of the behaviour of this operation + +void deleteArchive ( + in ManagedEntityIdType recordSetId ) + raises (UnknownRecordSet, + AccessDenied ); + +// See 9.4.1.7 for the description of the behaviour of this operation + +void purgeArchive ( + in ManagedEntityIdType recordSetId ) + raises (UnknownRecordSet, + AccessDenied ); + +// See 9.4.1.8 for the description of the behaviour of this operation + +RecordSeqType selectRecords ( + in FilterType SelectionFilter, + in ManagedEntityIdType recordSetId) + raises (UnknownRecordSet, + Timeout, + NoSuchRecords, + AccessDenied, + TooManyRecords); + +``` + +``` + +// See 9.4.1.9 for the description of the behaviour of this operation + +ManagedEntityIdSeqType recordSetListGet ( + in CreationModeType creationMode) + raises (AccessDenied); + +// See 9.4.1.10 for the description of the behaviour of this operation + +void changeUserLabel( + in ManagedEntityIdType recordSetId, + in UserLabelType newUserLabel) + raises (UnknownRecordSet, + AccessDenied, + DuplicateUserLabel); + +}; // interface RecordSetMgr + +}; // module ControlArchive + +}; // module q834_4 + +#endif + +``` + +## C.5 Q834SoftwareDownload.idl + +``` + +#ifndef __Q834_4_SOFTWAREDOWNLOAD_DEFINED +#define __Q834_4_SOFTWAREDOWNLOAD_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module SoftwareDownload { + + // begin definitions from other idl files + + // From Q834Common + typedef Q834Common::DCNAddressType DCNAddressType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::VersionType VersionType; + typedef Q834Common::PlugInUnitType PlugInUnitType; + typedef Q834Common::FilenameType FilenameType; + typedef Q834Common::ProceduralStatusSetType ProceduralStatusSetType; + typedef Q834Common::StatusAttributeSeqType StatusAttributeSeqType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::UserIdType UserIdType; + typedef Q834Common::PasswordType PasswordType; + typedef Q834Common::StatusValueType StatusValueType; + typedef Q834Common::GeneralizedTimeType GeneralizedTimeType; + typedef Q834Common::TrackingObjectIdType TrackingObjectIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + + #define AccessDenied Q834Common::AccessDenied + #define CommFailure Q834Common::CommFailure + #define UnknownScheduler Q834Common::UnknownScheduler + #define UnknownNE Q834Common::UnknownNE + #define DeniedAccess Q834Common::DeniedAccess + #define UnknownManagedEntity Q834Common::UnknownManagedEntity + #define Timeout Q834Common::Timeout + +``` + +``` + +#define InvalidScheduler Q834Common::InvalidScheduler +#define InvalidStartTime Q834Common::InvalidStartTime + +// End definitions from other idl files + +// Local data types + + typedef TrackingObjectIdType SoftwareDownloadTrackingObjectIdType; + + typedef sequence +SoftwareDownloadTrackingObjectIdSeqType; + typedef sequence FilenameSeqType; + + struct VersionsType { + ManagedEntityIdType resourceId; + VersionType softwarePrimary; + VersionType softwareStandBy; + VersionType hardware; + }; + + typedef sequence VersionsSeqType; + + struct TargetType { + ManagedEntityIdType containingSystem; + ManagedEntityIdType containingNE; // empty sequence means everything + string plugInUnitType; // empty string here implies to any suitable +plugInUnitType + ManagedEntityIdType slot; // empty sequence here means any slot. + }; //string is supplied by the supplier with Release Notes. + + struct DownloadStatusType + { + ManagedEntityIdType targetId; + StatusValueType deliveryStatus; + StatusValueType commitStatus; + StatusValueType activationStatus; + StatusValueType revertStatus; + }; + + typedef sequence DownloadStatusSeqType; + +// Local exceptions + + exception InvalidExternalTime {}; + exception UnrecognisedTarget {}; + exception InsufficientMemory {}; + exception SoftwareLoadHWMismatch {}; + exception SourceUnreachable {}; + exception UnknownSoftwareLoad {}; + exception InstallationFailure {}; + exception UnknownSoftwareDownloadTrackingObject {}; + exception SoftwareNotYetInstalled {}; + exception ActivationFailure {}; + exception ActivationCompleted {}; + exception ActivityCompleted {}; + exception ActivityInProgress {}; + exception InvalidSoftwareTrackingObject {}; + exception SoftwareTrackingObjectInUse {}; + +// End local definitions + + valuetype DownloadMgrValueType: itut_x780::ManagedObjectValueType { + +``` + +``` + + public SoftwareDownloadTrackingObjectIdSeqType +ScheduledSoftwareDownloadTrackingObjectList; // GET + public SoftwareDownloadTrackingObjectIdSeqType +OnDemandSoftwareDownloadTrackingObjectList; // GET + +}; + +interface DownloadMgr : itut_x780::ManagedObject { + +// See 9.5.1.1 for the description of the behaviour of this operation + + SoftwareDownloadTrackingObjectIdType deliverDistSWGloabal ( + in FilenameSeqType softwareSet, + in DCNAddressType softwareSourceAddr, + in UserIdType userId, + in PasswordType password, + in ManagedEntityIdSeqType deliverDistTargets) + raises (CommFailure, + UnrecognisedTarget, + InsufficientMemory, + SoftwareLoadHWMismatch, + SourceUnreachable, + UnknownSoftwareLoad, + Timeout, + AccessDenied, + DeniedAccess); + +// See 9.5.1.2 for the description of the behaviour of this operation + + SoftwareDownloadTrackingObjectIdType deliverDistSWSpecific ( + in FilenameSeqType softwareSet, + in DCNAddressType softwareSourceAddr, + in UserIdType userId, + in PasswordType password, + in TargetType deliverDistTarget) + raises (CommFailure, + UnrecognisedTarget, + InsufficientMemory, + SoftwareLoadHWMismatch, + SourceUnreachable, + UnknownSoftwareLoad, + Timeout, + AccessDenied, + DeniedAccess); + +// See 9.5.1.3 for the description of the behaviour of this operation + + void deleteSoftwareDownloadTrackingObject ( + in SoftwareDownloadTrackingObjectIdType id) + raises (UnknownSoftwareDownloadTrackingObject, AccessDenied); + +// See 9.5.1.4 for the description of the behaviour of this operation + + void commit ( + in SoftwareDownloadTrackingObjectIdType id, + in TargetType commitTarget) + raises (InstallationFailure, + UnknownSoftwareDownloadTrackingObject, + AccessDenied, + UnrecognisedTarget); + +// See 9.5.1.5 for the description of the behaviour of this operation + +``` + +``` + +void activate ( + in SoftwareDownloadTrackingObjectIdType id, + in TargetType activateTarget) + raises (UnknownSoftwareDownloadTrackingObject, + SoftwareNotYetInstalled, + ActivationFailure, + AccessDenied, + UnrecognisedTarget); + +// See 9.5.1.6 for the description of the behaviour of this operation + +void revert ( + in SoftwareDownloadTrackingObjectIdType id, + in TargetType revertTarget) + raises (UnknownSoftwareDownloadTrackingObject, + SoftwareNotYetInstalled, + ActivationFailure, + AccessDenied, + UnrecognisedTarget, + InvalidSoftwareTrackingObject); + +// See 9.5.1.7 for the description of the behaviour of this operation + +DownloadStatusSeqType getStatus ( + in SoftwareDownloadTrackingObjectIdType id) + raises (UnknownSoftwareDownloadTrackingObject, + AccessDenied); + +// See 9.5.1.8 for the description of the behaviour of this operation + +SoftwareDownloadTrackingObjectIdType scheduleDeliverDist ( + in FilenameSeqType softwareSet, + in DCNAddressType softwareSourceAddr, + in UserIdType userId, + in PasswordType password, + in ManagedEntityIdSeqType deliverDistTargets, + in GeneralizedTimeType deliverDistStartTime) + raises (SoftwareLoadHWMismatch, + UnknownScheduler, + AccessDenied, + InvalidStartTime); + +// See 9.5.1.9 for the description of the behaviour of this operation + +void scheduleCommit ( + in SoftwareDownloadTrackingObjectIdType + deliverDistSoftwareDownloadTrackingObjectId, + in GeneralizedTimeType commitStartTime) + raises (UnknownSoftwareDownloadTrackingObject, + UnknownScheduler, + SoftwareNotYetInstalled, + AccessDenied, + InvalidStartTime); + +// See 9.5.1.10 for the description of the behaviour of this operation + +void scheduleActivate ( + in SoftwareDownloadTrackingObjectIdType id, + in UserLabelType activateSchedulerName, + in GeneralizedTimeType activateStartTime) + raises (UnknownSoftwareDownloadTrackingObject, + InvalidStartTime, + SoftwareNotYetInstalled, + AccessDenied, + +``` + +``` + + InvalidScheduler ); + +// See 9.5.1.11 for the description of the behaviour of this operation + + void cancelScheduledSoftwareActivity ( + in SoftwareDownloadTrackingObjectIdType id) + raises (UnknownSoftwareDownloadTrackingObject, + ActivityCompleted, + ActivityInProgress, + AccessDenied); + +// See 9.5.1.12 for the description of the behaviour of this operation + + SoftwareDownloadTrackingObjectIdSeqType + scheduledSoftwareDownloadTrackingObjectList () + raises (AccessDenied); + +// See 9.5.1.13 for the description of the behaviour of this operation + + SoftwareDownloadTrackingObjectIdSeqType + onDemandSoftwareDownloadTrackingObjectList () + raises (AccessDenied); + +}; // interface DownloadMgr + +interface VersionRepository : itut_x780::ManagedObject { + +// See 9.5.2.1 for the description of the behaviour of this operation + + VersionsSeqType retrieveVersions ( + in ManagedEntityIdType containingManagedEntityId) + raises (CommFailure, + UnknownManagedEntity, + AccessDenied); + +// See 9.5.2.2 for the description of the behaviour of this operation + + boolean validateNEVersion ( + in ManagedEntityIdType managedEntityId, + in VersionType proposedSoftware) + raises (UnknownNE, AccessDenied); + +// See 9.5.2.3 for the description of the behaviour of this operation + + boolean validatePlugInVersion ( + in ManagedEntityIdType plugInUnitId, + in VersionType proposedSoftware) + raises (UnknownManagedEntity, AccessDenied); + +}; // interface VersionRepository + +}; // module SoftwareDownload + +}; // module q834_4 + +#endif + +``` + +## C.6 Q834EventPublisher.idl + +``` +#ifndef __Q834_4_EVENTPUBLISHING_DEFINED +#define __Q834_4_EVENTPUBLISHING_DEFINED +#include "Q834Common.idl" +#pragma prefix "itu.Int" + +module q834_4 +{ + +module EventPublisher +{ + +// begin definitions from other idl files - filterable data value types + +// From Q834Common + + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + typedef Q834Common::GeneralizedTimeType GeneralizedTimeType; + typedef Q834Common::NameType NameType; + typedef Q834Common::NameSeqType NameSeqType; + typedef Q834Common::VersionType VersionType; + typedef Q834Common::ProceduralStatusSetType ProceduralStatusSetType; + typedef Q834Common::PerceivedSeverityType PerceivedSeverityType; + typedef Q834Common::OperationalStateType OperationalStateType; + typedef Q834Common::AdministrativeStateType AdministrativeStateType; + typedef Q834Common::ProbableCauseType ProbableCauseType; // Values defined +in Q834Common::ProbableCauseConst + typedef Q834Common::NotificationIdentifierType NotificationIdentifierType; + typedef Q834Common::NotificationIdentifierSeqType +NotificationIdentifierSeqType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::MonitoredParameterType MonitoredParameterType; + typedef Q834Common::EquipmentHolderFType EquipmentHolderFType; + typedef Q834Common::PlugInUnitFType PlugInUnitFType; + typedef Q834Common::UsageStateType UsageStateType; + typedef Q834Common::ControlStatusSetType ControlStatusSetType; + typedef Q834Common::SpecificProblemSetType SpecificProblemSetType; + typedef Q834Common::BackedUpStatusType BackedUpStatusType; + typedef Q834Common::AttributeChangeSetType AttributeChangeSetType; + typedef Q834Common::SecurityAlarmCauseType SecurityAlarmCauseType; + +// End definitions from other idl files + +// Local data types + + typedef NotificationIdentifierSeqType CorrelatedNotificationType; + + typedef AttributeChangeSetType StateChangeDefinitionType; + + struct ThresholdInfoType { + MonitoredParameterType monitoredParameter; + unsigned long long observedValue; + unsigned long long thresholdValueLow; + unsigned long long thresholdValueHigh; + }; +}; +}; +``` + +``` + +/* +Values for monitoredParameter are provided in +Q834Common::MonitoringParameter. +Currently only counters are supported for performance or traffic monitoring +in BPON technology, consequently observedValue, and thresholdValueHigh are +restricted to non-negative integer values, and thresholdValueLow is 0. +*/ + +typedef unsigned short EquipmentType; + + +enum ServiceAffectingType { + serviceAffecting, + nonServiceAffecting, + unableToDetermine +}; + +//End local data type definitions + +// Local exceptions + +// End local exceptions + + +interface AlarmEventSupplier : itut_x780::ManagedObject { + + /* Structured event fixed header mappings: + domain_type is set to "telecommunications", + type_name is set to "Alarm", and + event_name is set to one of the following constant strings provided + below. + */ + + const string communicationAlarm = "CommunicationAlarm"; + const string equipmentAlarm = "EquipmentAlarm"; + const string environmentalAlarm = "EnvironmentalAlarm"; + const string processingErrorAlarm = "ProcessingErrorAlarm"; + const string qualityOfServiceAlarm = "QualityOfServiceAlarm"; + + /* + Filterable data names for populating the filterable event body in the + structured event are listed in order below. + */ + + const string alarmEmittingMEId = "AlarmEmittingMEId"; + const string eventTime = "EventTime"; + const string probableCause = "ProbableCause"; + const string specificProblems = "SpecificProblems"; + const string perceivedSeverity = "PerceivedSeverity"; + const string backUpStatus = "BackUpStatus"; + const string backUpManagedEntityId = "BackUpManagedEntityId"; + const string thresholdInfo = "ThresholdInfo"; + const string notificationIdentifier = "NotificationIdentifier"; + const string correlatedNotifications = "CorrelatedNotifications"; + const string stateChangeDefinition = "StateChangeDefinition"; + const string monitoredAttributes = "MonitoredAttributes"; + const string additionalText = "AdditionalText"; + const string serviceAffectingInd = "ServiceAffectingInd"; + + /* + Remaining filterable data values. + +``` + +``` + +/* Names for State and Status Variables for StateChangeDefinition +*/ + +const string administrativeState = "AdministrativeState"; +const string operationalState = "OperationalState"; +const string usageState = "UsageState"; +const string availabilityStatus = "AvailabilityStatus"; +const string proceduralStatus = "ProceduralStatus"; +const string controlStatus = "ControlStatus"; +const string alarmStatus = "AlarmStatus"; + +/* +Mapping to filterable data within the structured event is provided +below for communication alarm, equipment alarm, processing error +alarm, environmental alarm, and quality of service alarm. + +{ + {"AlarmEmittingMEId", any (ManagedEntityIdType)}, + {"EventTime", any (GeneralizedTimeType)}, + {"ProbableCause", any (ProbableCauseType)}, + {"SpecificProblems", any (SpecificProblemSetType)}, + {"PerceivedSeverity", any (PerceivedSeverityType)}, + {"ServiceAffectingInd", any (ServiceAffectingType)}, + {"BackUpStatus", any (BackedUpStatusType)}, + {"BackUpManagedEntityId", any (ManagedEntityIdType)}, + {"ThresholdInfo", any (ThresholdInfoType)}, + {"NotificationIdentifier", any (NotificationIdentifierType)}, + {"CorrelatedNotifications", any (CorrelatedNotificationType)}, + {"StateChangeDefinition", any (StateChangeDefinitionType)}, + {"AdditionalText", any (string)} +} + +*/ + +}; // interface AlarmEventSupplier + +interface SecurityEventSupplier : itut_x780::ManagedObject { + + /* Structured event fixed header mappings: + domain_type is set to "telecommunications", + type_name is set to "SecurityEvent", and + event_name is set to one of the following constant strings + provided below. + */ + + const string integrityViolation = "IntegrityViolation"; + const string operationalViolation = "OperationalViolation"; + const string physicalViolation = "PhysicalViolation"; + const string securityEventViolation = "SecurityEventViolation"; + const string timeDomainViolation = "TimeDomainViolation"; + + const string eventEmittingMEId = "EventEmittingMEId"; + const string eventTime = "EventTime"; + const string securityAlarmCause = "SecurityAlarmCause"; + const string securityAlarmDetector = "SecurityAlarmDetector"; + const string serviceUser = "ServiceUser"; + const string serviceProvider = "ServiceProvider"; + const string securityEventNotificationIdentifier = + +``` + +``` + + "NotificationIdentifier"; +const string correlatedNotifications = "CorrelatedNotifications"; +const string additionalText = "AdditionalText"; +/* +Mapping to filterable data within the structured event is provided +below for Integrity Violations, Operational Violations, Physical +Violations, Security Event Violations, Time Domain Violations. + +{ + {"EventEmittingMEId", any (ManagedEntityIdType)}, + {"EventTime", any (GeneralizedTimeType)}, + {"SecurityAlarmCause", any (SecurityAlarmCauseType)}, + {"SecurityAlarmDetector", any (ManagedEntityIdType)}, + {"ServiceUser", any (ManagedEntityIdType)}, + {"ServiceProvider", any (ManagedEntityIdType)}, + {"NotificationIdentifier", any (NotificationIdentifierType)}, + {"CorrelatedNotifications", any (CorrelatedNotificationType)}, + {"AdditionalText", any (string)} +} + +*/ + +}; // interface SecurityEventSupplier + +interface DiscoveryEventSupplier : itut_x780::ManagedObject { + + /* Structured event fixed header mappings: + domain_type is set to "telecommunications", + type_name is set to "DiscoveryEvent", and + event_name is set to one of the following constant strings + provided below. Only installed equipment changes are declared + through this interface. + */ + + const string managedEntityCreation = "ManagedEntityCreation"; + const string managedEntityDeletion = "ManagedEntityDeletion"; + + const string managedEntityType = "ManagedEntityType"; + const string managedEntityAttributeValues = + "ManagedEntityAttributeValues"; + const string discoveryNotificationIdentifier = + "NotificationIdentifier"; + const string correlatedNotifications = "CorrelatedNotifications"; + const string additionalText = "AdditionalText"; + + // The following items are equipment types that are discovered by the + // Supplier Management System and automatically revealed to the OMS. + // The data structure passed on the notification is defined in + // Q834Common.idl and the mapping below refers to it as MEstruct. More + // specifically, here is the list of data structures currently + // supported: OLTType, ONUType, ONTType, NTType, EquipmentHolderType, + // and PlugInUnitFType. + + const unsigned short OLT_NE = 1; + const unsigned short ONT_NE = 2; + const unsigned short ONU_NE = 3; + const unsigned short NT_NE = 4; + +``` + +``` + +const unsigned short EQUIPMENT HOLDER_F = 5; +const unsigned short PLUG_IN_UNIT_F = 6; + +/* +Mapping to filterable data within the structured event is provided +below for a discovery event that involves the creation of a managed +entity. + +{ + {"ManagedEntityType", any (EquipmentType)}, + {"EventTime", any (GeneralizedTimeType)}, + {"ManagedEntityAttributeValues", any (MEstruct)}, + {"NotificationIdentifier", any (NotificationIdentifierType)}, + {"CorrelatedNotifications", any (CorrelatedNotificationType)}, + {"AdditionalText", any (string)} +} + +*/ + +}; // interface DiscoveryEventSupplier + +}; // module EventPublisher + +}; // module q834_4 + +#endif + +``` + +## C.7 Q834MIBTransfer.idl + +``` + +#ifndef __Q834_4_MIBTRANSFER_DEFINED +#define __Q834_4_MIBTRANSFER_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module MIBTransfer { + // Begin definitions from other idl files + + // From Q834Common + + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::DCNAddressType DCNAddressType; + typedef Q834Common::FilenameType FilenameType; + typedef Q834Common::StatusAttributeSeqType StatusAttributeSeqType; + typedef Q834Common::TransferTrackingObjectIdType + TransferTrackingObjectIdType; + typedef Q834Common::UserIdType UserIdType; + typedef Q834Common::PasswordType PasswordType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + +#define AccessDenied Q834Common::AccessDenied +#define CommFailure Q834Common::CommFailure +#define EquipmentFailure Q834Common::EquipmentFailure +#define UnknownNE Q834Common::UnknownNE +#define UnknownScheduler Q834Common::UnknownScheduler +#define InvalidScheduler Q834Common::InvalidScheduler +#define UnknownDestinationServer Q834Common::UnknownDestinationServer +#define FileExists Q834Common::FileExists + +``` + +``` + +#define CannotCreateFile Q834Common::CannotCreateFile +#define DeniedAccess Q834Common::DeniedAccess + +// End definitions from other idl files + +// Local data types + + typedef sequence +TransferTrackingObjectIdSeqType; + +// Local exceptions + + exception UnknownBackupProcess {}; + exception UnknownSourceServer {}; + exception UnknownRestoreProcess {}; + exception SoftwareLoadHardwareMismatch {}; + +// End local definitions + + valuetype MIBMoverValueType: itut_x780::ManagedObjectValueType { + + public TransferTrackingObjectIdSeqType transferTrackingObjectIdList; +// GET + + }; + + interface MIBMover : itut_x780::ManagedObject { + +// See 9.7.1.1 for the description of the behaviour of this operation + + TransferTrackingObjectIdType startBackup ( + in ManagedEntityIdType nEManagedEntityId, // OLT + in DCNAddressType destinationServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType destinationFile, + in boolean overwriteExistingFile) + raises (AccessDenied, + UnknownNE, + UnknownDestinationServer, + CommFailure, + EquipmentFailure, + DeniedAccess); + +// See 9.7.1.2 for the description of the behaviour of this operation + + StatusAttributeSeqType getBackupStatus ( + in TransferTrackingObjectIdType id) + raises (AccessDenied, + UnknownBackupProcess); + +// See 9.7.1.3 for the description of the behaviour of this operation + + TransferTrackingObjectIdType scheduleBackup ( + in ManagedEntityIdType nEManagedEntityId, // OLT + in UserIdType userId, + in PasswordType password, + in UserLabelType schedulerName, + in DCNAddressType destinationServerAddr, + in FilenameType destinationFile, + +``` + +``` + + in boolean overwriteExistingFile) + raises (AccessDenied, + UnknownNE, + UnknownScheduler, + UnknownDestinationServer, + InvalidScheduler); + +// See 9.7.1.4 for the description of the behaviour of this operation + +void modifyBackupSchedule( + in TransferTrackingObjectIdType id, + in UserLabelType newSchedulerName) + raises (AccessDenied, + UnknownBackupProcess, + UnknownScheduler, + InvalidScheduler); + +// See 9.7.1.5 for the description of the behaviour of this operation + +void cancelScheduledBackup ( + in TransferTrackingObjectIdType id) + raises (AccessDenied, + UnknownBackupProcess); + +// See 9.7.1.6 for the description of the behaviour of this operation + +void abortBackup ( + in TransferTrackingObjectIdType id) + raises (AccessDenied, + UnknownBackupProcess, + CommFailure, + EquipmentFailure); + +// See 9.7.1.7 for the description of the behaviour of this operation + +TransferTrackingObjectIdType startRestore ( + in ManagedEntityIdType nEManagedEntityId, // OLT + in DCNAddressType sourceServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType sourceFile) + raises (AccessDenied, + UnknownNE, + UnknownSourceServer, + CommFailure, + EquipmentFailure, + DeniedAccess, + SoftwareLoadHardwareMismatch ); + +// See 9.7.1.8 for the description of the behaviour of this operation + +StatusAttributeSeqType getRestoreStatus ( + in TransferTrackingObjectIdType id) + raises (AccessDenied, + UnknownRestoreProcess); + +``` + +``` + +// See 9.7.1.9 for the description of the behaviour of this operation + + TransferTrackingObjectIdSeqType transferTrackingObjectIdListGet () + raises (AccessDenied); + +}; // interface MIBMover + +}; // module MIBTransfer + +}; // module q834_4 + +#endif + +``` + +## C.8 Q834PerformanceManager.idl + +``` + +#ifndef __Q834_4_PERFORMANCEMANAGER_DEFINED +#define __Q834_4_PERFORMANCEMANAGER_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module PerformanceManager { + + // begin definitions from other idl files + + // From Q834Common + typedef Q834Common::NameType NameType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::GeneralizedTimeType GeneralizedTimeType; + typedef Q834Common::RecordSeqType RecordSeqType; + typedef Q834Common::ServiceInstanceIdType ServiceInstanceIdType; + typedef Q834Common::MonitoredParameterType MonitoredParameterType; + typedef Q834Common::NameSeqType NameSeqType; + typedef Q834Common::MonitoringKindType MonitoringKindType; + typedef Q834Common::RecordKindType RecordKindType; + + #define AccessDenied Q834Common::AccessDenied + #define UnknownNE Q834Common::UnknownNE + #define UnknownManagedEntity Q834Common::UnknownManagedEntity + #define UnknownProfiles Q834Common::UnknownProfiles + #define UnknownServiceInstance Q834Common::UnknownServiceInstance + #define UnknownScheduler Q834Common::UnknownScheduler + #define CommFailure Q834Common::CommFailure + #define InvalidScheduler Q834Common::InvalidScheduler + #define EquipmentFailure Q834Common::EquipmentFailure + #define ProfileSuspended Q834Common::ProfileSuspended + + // End definitions from other idl files + + // Local data types + + struct MonitoringPointKindAndThresholdsType { + MonitoringKindType monitoringType; + NameType thresholdDataProfileName; + }; + /* + +``` + +NOTE - ITU-T Recs Q.834.1 and Q.834.2 describe the relationships between ThresholdData and specific monitoring point types. +\*/ + +``` +typedef sequence ThresholdsSeqType; +``` + +``` +struct MonitoringPointAndThresholdsType { + ManagedEntityIdType monitoringPoint; + NameType thresholdDataProfileName; +}; +``` + +``` +typedef sequence +MonitoringPointThresholdsSeqType; +``` + +``` +typedef sequence MonitoredParameterSeqType; +``` + +``` +typedef sequence RecordsSeqType; // Implicitly grouped by +record type. +``` + +``` +typedef RecordKindType HistoryDataType; // Values defined in +Q834Common::RecordSetType +``` + +``` +typedef ManagedEntityIdSeqType MonitoringPointSeqType; +``` + +``` +struct SWPValueType { + ManagedEntityIdType monitoringPoint; + short totConsecutiveIntvls; + short persistenceMinimum; +}; +``` + +``` +typedef sequence< SWPValueType > SWPValueSeqType; +``` + +``` +struct ParameterSettingType { + MonitoredParameterType monitoredParameter; + short totConsecutiveIntvls; + short persistenceMinimum; +}; +``` + +``` +typedef sequence ParameterSettingSeqType; +``` + +``` +// Local exceptions +``` + +``` +exception UnknownParameters { + MonitoredParameterSeqType monitoredParameterList; +}; +exception IntervalCountTooLarge {}; +exception UnknownMonitoringPointTypes { + MonitoringPointSeqType monitoringPointKindList; +}; +exception InvalidAssociation {}; +exception CollectionPeriodPast {}; +exception CollectionLimitation {}; +exception UnknownHistoryDataType {}; +``` + +``` +// End local definitions +``` + +``` +interface ImpairmentPersistence : itut_x780::ManagedObject { +``` + +``` + // See 9.8.1.1 for the description of the behaviour of this operation +``` + +``` + void setSlidingWindowParameters ( + in ManagedEntityIdType nEManagedEntityId, +``` + +``` + + in MonitoredParameterSeqType monitoredParameterList, + in short totConsecutiveIntvls, + in short persistenceMinimum, + in boolean sysScopeInd) + raises (UnknownNE, + UnknownParameters, + IntervalCountTooLarge, + AccessDenied, + CommFailure); + +// See 9.8.1.2 for the description of the behaviour of this operation + +void setSpecificSlidingWindowParameters ( + in ManagedEntityIdType nManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in MonitoredParameterSeqType monitoredParameterList, + in short totConsecutiveIntvls, + in short persistenceMinimum, + in boolean allowGlobalOverwrite) + raises (UnknownNE, + UnknownParameters, + IntervalCountTooLarge, + AccessDenied, + UnknownManagedEntity, + CommFailure, + EquipmentFailure); + +// See 9.8.1.3 for the description of the behaviour of this operation + +SWPValueSeqType getSpecificSlidingWindowParameters ( + in ManagedEntityIdType nManagedEntityId, + in MonitoredParameterType monitoredParameter) + raises (UnknownNE, + UnknownParameters, + CommFailure); + +// See 9.8.1.4 for the description of the behaviour of this operation + +void setThreshold ( + in ManagedEntityIdType nManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in NameType thresholdDataProfileName) + raises (UnknownNE, + AccessDenied, + UnknownManagedEntity, + UnknownProfiles, + InvalidAssociation, + CommFailure, + ProfileSuspended); + +// See 9.8.1.5 for the description of the behaviour of this operation + +void setThresholds ( + in ManagedEntityIdType nManagedEntityId, + in boolean sysScopeInd, + in ThresholdsSeqType thresholdsList) + raises (UnknownNE, + UnknownProfiles, + AccessDenied, + UnknownMonitoringPointTypes, + InvalidAssociation, + CommFailure, + ProfileSuspended); + +``` + +``` + +// See 9.8.1.6 for the description of the behaviour of this operation + +MonitoringPointThresholdsSeqType getThresholdValues ( + in ManagedEntityIdType nEManagedEntityId, + in MonitoringKindType monitoringType) + raises (UnknownNE, + UnknownMonitoringPointTypes, + CommFailure); + +// See 9.8.1.7 for the description of the behaviour of this operation + +ThresholdsSeqType getSystemThresholdsSetting( + in ManagedEntityIdType nEManagedEntityId) + raises (AccessDenied, UnknownManagedEntity); + +// See 9.8.1.8 for the description of the behaviour of this operation + +ParameterSettingSeqType getSystemSWSSettings( + in ManagedEntityIdType nEManagedEntityId) + raises (AccessDenied, UnknownManagedEntity); + +}; // interface ImpairmentPersistence + +interface ReportController : itut_x780::ManagedObject { + + // See 9.8.2.1 for the description of the behaviour of this operation + + void addCustomerMonitoringReporting ( + in ManagedEntityIdType nEManagedEntityId, + in ServiceInstanceIdType serviceInstanceId, + in ManagedEntityIdType monitoringPoint, + in GeneralizedTimeType stopTime, + in HistoryDataType historyData, + in short granularityPeriod) //in minutes + raises (UnknownServiceInstance, + AccessDenied, + UnknownNE, + UnknownManagedEntity, + CollectionPeriodPast, + CollectionLimitation, + InvalidAssociation, + UnknownHistoryDataType, + CommFailure); + + // See 9.8.2.2 for the description of the behaviour of this operation + + void removeCustomerMonitoringReporting ( + in ServiceInstanceIdType serviceInstanceId) + raises (UnknownServiceInstance, + AccessDenied, + CollectionPeriodPast, + CommFailure); + + // See 9.8.2.3 for the description of the behaviour of this operation + + RecordsSeqType selectByServiceInstance ( + in ServiceInstanceIdType serviceInstanceId, + in GeneralizedTimeType intervalStartTime, + in GeneralizedTimeType intervalEndTime) + raises (UnknownServiceInstance, + AccessDenied ); + +``` + +``` + +// See 9.8.2.4 for the description of the behaviour of this operation + +MonitoringPointSeqType displayActiveReporting ( + in ServiceInstanceIdType serviceInstanceId) + raises (UnknownServiceInstance, + AccessDenied); + +// See 9.8.2.5 for the description of the behaviour of this operation + +void addNewMonitoringReporting ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in GeneralizedTimeType stopTime, + in HistoryDataType historyData, + in short granularityPeriod) //in minutes + raises (AccessDenied, + UnknownNE, + UnknownManagedEntity, + CollectionPeriodPast, + CollectionLimitation, + InvalidAssociation, + UnknownHistoryDataType, + CommFailure); + +// See 9.8.2.6 for the description of the behaviour of this operation + +RecordsSeqType selectByMonitoringPoint ( + in ManagedEntityIdType monitoringPoint, + in GeneralizedTimeType intervalStartTime, + in GeneralizedTimeType intervalEndTime) + raises (UnknownManagedEntity, + AccessDenied); + +// See 9.8.2.7 for the description of the behaviour of this operation + +void createReportingSchedule ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in HistoryDataType historyData, + in ServiceInstanceIdType serviceInstance, + in short granularityPeriod, //in minutes + in UserLabelType schedulerName) + raises (AccessDenied, + UnknownNE, + UnknownManagedEntity, + CollectionLimitation, + UnknownScheduler, + InvalidAssociation, + UnknownHistoryDataType, + InvalidScheduler); + +// See 9.8.2.8 for the description of the behaviour of this operation + +void modifyReportingSchedule ( + in ManagedEntityIdType nEManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in HistoryDataType historyData, + in UserLabelType newSchedulerName) + raises (AccessDenied, + UnknownNE, + UnknownManagedEntity, + CollectionLimitation, + UnknownScheduler, + +``` + +``` + + InvalidAssociation, + UnknownHistoryDataType, + InvalidScheduler); + +// See 9.8.2.9 for the description of the behaviour of this operation + +void cancelReportingSchedule ( + in ManagedEntityIdType nManagedEntityId, + in ManagedEntityIdType monitoringPoint, + in HistoryDataType historyData, + in UserLabelType schedulerName) + raises (AccessDenied, + UnknownNE, + UnknownManagedEntity, + UnknownScheduler, + InvalidAssociation, + UnknownHistoryDataType); + +}; // interface ReportController + +}; // module PerformanceManager + +}; // module q834_4 + +#endif + +``` + +## C.9 Q834ProfileManager.idl + +``` + +#ifndef __Q834_4_PROFILEMANAGER_DEFINED +#define __Q834_4_PROFILEMANAGER_DEFINED +#include "Q834Common.idl" +#pragma prefix "itu.Int" + +module q834_4 +{ + + module ProfileManager + { + + // begin definitions from other idl files - filterable data value types + typedef Q834Common::NameType NameType; + typedef Q834Common::NotificationIdentifierType NotificationIdentifierType; + typedef Q834Common::PerceivedSeverityType PerceivedSeverityType; + typedef Q834Common::ProbableCauseType ProbableCauseType; + typedef Q834Common::MonitoredParameterType MonitoredParameterType; + typedef Q834Common::ServiceCategoryType ServiceCategoryType; + typedef Q834Common::ConformanceDefType ConformanceDefType; + typedef Q834Common::ATMOverbookingFactorType ATMOverbookingFactorType; + typedef Q834Common::MonitoringKindType MonitoringKindType; + + #define UnknownProfiles Q834Common::UnknownProfiles + #define AccessDenied Q834Common::AccessDenied + + // End definitions from other idl files + + // Local data types + + typedef unsigned short ProfileKindType; + } +} + +``` + +``` + +struct ProfileInfoType { + ProfileKindType profileKind; + any attributeValuestruct; +}; + +``` + +``` + +/* + +``` + +Next, structs (and sequence of structs) are defined having the attribute values for the newly created profile objects. Any one of these structs is subsequently identified as ProfileStruct in the Profile Event Consumer interface specification. + +``` + +*/ + +``` + +``` + +enum SubType { + NULL, + VoicebandBasedOn64kbps, + SynchronousCircuitEmulation, + AsynchronousCircuitEmulation, + HighQualityAudio, + Video +}; + +``` + +``` + +enum CBRRateType { + br44736kbps, + br1544kbps, + br2048kbps, + brE3kbps, + br64kbps, + br2x64kbps, + br3x64kbps, + br4x64kbps, + br5x64kbps, + br6x64kbps, + br7x64kbps, + br8x64kbps, + br9x64kbps, + br10x64kbps, + br11x64kbps, + br12x64kbps, + br13x64kbps, + br14x64kbps, + br15x64kbps, + br16x64kbps, + br17x64kbps, + br18x64kbps, + br19x64kbps, + br20x64kbps, + br21x64kbps, + br22x64kbps, + br23x64kbps, + br24x64kbps, + br25x64kbps, + br26x64kbps, + br27x64kbps, + br28x64kbps, + br29x64kbps, + br30x64kbps, + br31x64kbps +}; + +``` + +``` + +enum ClockRecoveryType { + PhysInterface, + SRTS, + +``` + +``` + + AdaptiveClock, + LocalOsc +}; + +enum ForwardErrorCorrectionType { + NoFEC, + FECforLossSensitiveSigTransport, + FECforDelaySensSigTransport +}; + +typedef boolean StructuredDataTransferType; //TRUE = STD has been chosen +typedef long long PartiallyFilledCellsType; +typedef long long CellLossIntegrationPeriodType; + +struct AAL1ProfileType { + SubType aAL1subtype; + CBRRateType cBRRate; + ClockRecoveryType clockRecovery; + ForwardErrorCorrectionType forwardErrorCorrection; + StructuredDataTransferType structuredDataTransfer; + PartiallyFilledCellsType partiallyFilledCells; +}; // ProfileStruct for profile type = 1 + +typedef stringDefaultSSCSParameterProfile1PtrType; +typedef stringDefaultSSCSParameterProfile2PtrType; + +struct AAL2ProfileType { + DefaultSSCSParameterProfile1PtrType defaultSSCSParameterProfile1Ptr; + DefaultSSCSParameterProfile2PtrType defaultSSCSParameterProfile2Ptr; +}; // ProfileStruct for profile type = 2 + +struct MaxCPCSSDUSizeType { + long long forwardDirectionCPCS_SDU; + long long backwardsDirectionCPCS_SDU; +}; + +enum AALModeType { + MessageAssured, + MessageUnassured, + StreamingAssured, + StreamingUnassured +}; + +enum SSCSType { + NoSSC, + DataSSCSonSSCOPAssured, + DataSSCSonSSCOPNotAssured, + FrameRelaySSCS +}; + +struct AAL5ProfileType { + // ManagedEntityIdType mEId; ?? + MaxCPCSSDUSizeType maxCPCSSDUSize; + AALModeType aALMode; + SSCSType sSCS; +}; // ProfileStruct for profile type = 4 + +enum AppIdType { + LES_CAS_noELCP, + LES_PSTN_noELCP, + +``` + +``` + + LES_PSTN_ELCP, + LES_DSS1forBRI_noELCP, + LES_DSS1forBRI_ELCP, + LES_CASforPOTS_DSS1forBRI_noELCP, + LES_PSTNforPOTS_DSS1forBRI_noELCP, + LES_PSTNforPOTS_DSS1forBRI_ELCP, + LES_otherCCS, + UnspecifiedLES +}; + +typedef long long MaxNumChannelsType; +typedef long long MinimumChanIdType; +typedef long long MaximumChanIdType; +typedef long long MaxCPS_SDULengthType; +typedef long long TimerCULengthType; + +struct AAL2PVCProfileType { + MaxNumChannelsType maxNumChannels; + MinimumChanIdType minimumChanId; + MaximumChanIdType maximumChanId; + MaxCPS_SDULengthType maxCPS_SDULength; + TimerCULengthType timerCULength; +}; // ProfileStruct for profile type = 3 + +struct AlarmSeverityAssignProfileType { + string eventName; //As defined in AlarmEventSupplier + ProbableCauseType probableCauseValue; //Ditto as above + PerceivedSeverityType serviceAffectingSeverity; + PerceivedSeverityType nonServiceAffectingSeverity; +}; // ProfileStruct for profile type = 5 + +typedef sequence +AlarmSeverityAssignProfileSeqType; +typedef long long LocalMaxNumVPCSupportedType; +typedef long long LocalMaxNumVCCSupportedType; +typedef short LocalMaxNumVPIBitsType; +typedef short LocalMaxNumVCIBitsType; +typedef long long TotalEgressBandwidthType; +typedef long long TotalIngressBandwidthType; +typedef boolean UPCNPCIndicatorType; //TRUE = policing is on + +struct ATMNetworkAccessProfileType { + LocalMaxNumVPCSupportedType localMaxNumVPCSupported; + LocalMaxNumVCCSupportedType localMaxNumVCCSupported; + LocalMaxNumVPIBitsType localMaxNumVPIBits; + LocalMaxNumVCIBitsType localMaxNumVCIBits; + TotalEgressBandwidthType totalEgressBandwidth; + TotalIngressBandwidthType totalIngressBandwidth; + UPCNPCIndicatorType uPCNPCIndicator; +}; // ProfileStruct for profile type = 6 + +typedef short LANType; +typedef short EncapsulationProtocolType; +typedef short PIDType; + +struct BridgedLANServiceProfileValues { + LANType lAN; + EncapsulationProtocolType encapsulationProtocol; + PIDType pID; +}; // ProfileStruct for profile type = 7 + +typedef long long BufferedCDVToleranceType; + +``` + +``` + +enum CASType { + basic, + e1Cas, + SfCas, + ds1EsfCas, + j2Cas +}; + +typedef long long CableLengthType; + +struct CESServiceProfileValues { + BufferedCDVToleranceType bufferedCDVTolerance; + CASType cAS; +}; // ProfileStruct for profile type = 8 + +enum DS1FramingType { + SuperFrame, + ExtendedSuperFrame, + Unframed +}; + +enum DS1EncodingType { + AMI, + B8ZS +}; + +enum LoopbackCodeType { + SmartJack, + SmartJack_ONTinband, + COInband +}; + +typedef boolean SupplyPowerIndType; + +struct DS1ProfileValues { + DS1FramingType dS1Framing; + DS1EncodingType dS1Encoding; + LoopbackCodeType loopbackCode; + SupplyPowerIndType supplyPowerInd; + CableLengthType cableLength; +}; // ProfileStruct for profile type = 9 + +enum DS3ApplicationType { + CBitParity, + M23 +}; + +enum DS3EncodingType { + B3ZS, + CCHAN +}; + +struct DS3ProfileType { + DS3ApplicationType dS3Application; + DS3EncodingType dS3Encoding; + CableLengthType cableLength; +}; // ProfileStruct for profile type = 10 + +typedef boolean DuplexType; //TRUE = full, FALSE = half +typedef boolean AutoDetectionIndType; + +``` + +``` + +enum DataRateType { + TenBT, + HundredBT, + ThousandBT, + otherrate +}; + +typedef long long MaxFrameSizeType; //Fixed for Ethernet + +typedef boolean DTEDCEType; // TRUE = DTE setting; FALSE = DCE setting. + +struct EthernetProfileValues { + DuplexType duplex; + AutoDetectionIndType autoDetectionInd; + DataRateType dataRate; + MaxFrameSizeType maxFrameSize; + DTEDCEType dTEDCE; +}; // ProfileStruct for profile type = 11 + +enum T303Type { + m700, + m1200, + m1700, + m2200, + m2700, + m3200, + m3700, + m4200, + m4700 +}; + +enum T396Type { + ms700, + ms1700, + ms2700, + ms3700, + ms4700, + ms5700, + ms6700, + ms7700, + ms8700, + ms9700, + ms10700, + ms11700, + ms12700, + ms13700, + ms14700 +}; + +struct IDLCCallProcessingProfileType { + T303Type t303; + T396Type t396; +}; // ProfileStruct for profile type = 12 + +typedef boolean ELCPIndType; + +enum POTSSignallingType { + PSTN, + ChAS, + CCS, + UNKNOWN +}; + +``` + +``` + +enum BRISignallingType { + DSS1, + OtherCCS +}; + +typedef long long MaxNumCIDsType; +typedef long long MaxPacketLengthType; +struct ChannelWithSSCSPtrType { + long channelIndex; + boolean ptr1orPtr2; +}; + +typedef sequence ChanAndSSCSParaPtrSeqType; + +struct LESProfileType { + ELCPIndType eLCPInd; + POTSSignallingType pOTSSignalling; + BRISignallingType bRISignalling; + MaxNumCIDsType maxNumCIDs; + MaxPacketLengthType maxPacketLength; + ChanAndSSCSParaPtrSeqType chanAndSSCSParaPtrSeq; +}; // ProfileStruct for profile type = 13 + +typedef boolean SpanningTreeIndType; +typedef short BridgePriorityType; +typedef short MaxAgeType; +typedef short HelloTimeType; +typedef short ForwardDelayType; + +struct MACBridgeServiceProfileType { + SpanningTreeIndType spanningTreeInd; + BridgePriorityType bridgePriority; + MaxAgeType maxAge; + HelloTimeType helloTime; + ForwardDelayType forwardDelay; +}; // ProfileStruct for profile type = 14 + +typedef long long SegmentLengthType; +typedef short RASTimerType; +typedef long longMaxSSSARSDULengthType; +typedef boolean SSTEDIndType; +typedef boolean SSADTIndType; + +struct SSCSPParameterProfile1Type { + SegmentLengthType segmentLength; + RASTimerType rASTimer; + MaxSSSARSDULengthType maxSSSARSDULength; + SSTEDIndType sSTEDInd; + SSADTIndType sSADTInd; +}; // ProfileStruct for profile type = 15 + +enum ServiceCatType { + Audio, + Multirate, + UNKNCategory +}; + +enum EncSrcType { + ITUT, + ATMForum, + Proprietary +}; + +``` + +``` + +typedef short EncProfileIndexType; +typedef boolean AudioServIndType; +typedef short PCMEncType; +typedef boolean CMDDataIndType; +typedef short CMMultiplierNumType; +typedef boolean FMDataIndType; +typedef long long FMMaxFrameLenType; +typedef boolean CASIndType; +typedef boolean DTMFIndType; +typedef boolean MFR1IndType; +typedef boolean MFR2IndType; +typedef boolean RateControlIndType; +typedef boolean SynchChangeIndType; +typedef boolean FaxDemodIndType; + +struct SSCSPParameterProfile2Type { + ServiceCatType serviceCat; + EncSrcType encSrc; + EncProfileIndexType encProfileIndex; + AudioServIndType audioServInd; + PCMEncType pCMEnc; + CMDDataIndType cMDDataInd; + CMMultiplierNumType cMMultiplierNum; + FMDataIndType fMDataInd; + FMMaxFrameLenType fMMaxFrameLen; + CASIndType cASInd; + DTMFIndType dTMFInd; + MFR1IndType mFR1Ind; + MFR2IndType mFR2Ind; + RateControlIndType rateControlInd; + SynchChangeIndType synchChangeInd; + FaxDemodIndType faxDemodInd; +}; // ProfileStruct for profile type = 16 + +``` + +``` + +typedef long long PCRIngressType; +typedef long long PCREgressType; +typedef long long CDVTPCRIngressType; +typedef long long CDVTPCREgressType; +typedef long long CDVTSCRIngressType; +typedef long long CDVTSCREgressType; +typedef long long SCRIngressType; +typedef long long SCREgressType; +typedef long long MaxBSIngressType; +typedef long long MaxBSEgressType; +typedef long long MFSIngressType; +typedef long long MFSEgressType; + +struct TrafficDescriptorProfileType { + ServiceCategoryType serviceCategory; + ConformanceDefType conformanceDef; + PCRIngressType pCRIngress; + PCREgressType pCREgress; + CDVTPCRIngressType cDVTPCRIngress; + CDVTPCREgressType cDVTPCREgress; + CDVTSCRIngressType cDVTSKRIngress; + CDVTSCREgressType cDVTSKREgress; + SCRIngressType sCRIngress; + SCREgressType sCREgress; + MaxBSIngressType maxBSIngress; + MaxBSEgressType maxBSEgress; + MFSIngressType mFSIngress; + MFSEgressType mFSEgress; +}; // ProfileStruct for profile type = 17 + +``` + +``` + +typedef string LoopbackLocCodeType; + +struct UNIProfileType { + LocalMaxNumVPCSupportedType localMaxNumVPCSupported; + LocalMaxNumVCCSupportedType localMaxNumVCCSupported; + LocalMaxNumVPiBitsType localMaxNumVPiBits; + LocalMaxNumVCiBitsType localMaxNumVCiBits; + LoopbackLocCodeType loopbackLocCode; +}; // ProfileStruct for profile type = 18 + +enum AnnouncementType { + Silence, + ReorderTone, + FastBusy, + VoiceAnnouncement, + OtherAnnouncementType, + UNKNAnnouncementType +}; + +enum TimingReferenceType { + NetworkTimingReference, + AdaptiveVoice, + FreeRun, + OtherTimingReference +}; + +typedef boolean EchoCancellationIndType; + +struct VoiceServiceProfileAAL1Type { + AnnouncementType announcement; + TimingReferenceType timingReference; + EchoCancellationIndType echoCancellationInd; +}; // ProfileStruct for profile type = 19 + +typedef long long JitterTargetType; +typedef long long JitterBufferMaxType; + +struct VoiceServiceProfileAAL2Type { + AnnouncementType announcement; + TimingReferenceType timingReference; + JitterTargetType jitterTarget; + JitterBufferMaxType jitterBufferMax; + EchoCancellationIndType echoCancellationInd; +}; // ProfileStruct for profile type = 20 + +struct ThresholdDataComponentType { + MonitoredParameterType monitoredParameter; // Values defined in + Q834Common::MonitoringParameter unsigned long long thresholdValue; +}; + +typedef sequence ThresholdDataSeqType; + +struct ThresholdDataProfileType { + MonitoringKindType monitoringType; + ThresholdDataSeqType thresholdValues; +}; // ProfileStruct for profile type = 21 + +typedef sequence ATMOverbookingProfileType; +// ProfileStruct for profile type = 22 + +``` + +``` + +// Local exceptions +exception ProfileInUse {}; +exception DuplicateProfileName {}; + +// End local definitions + +interface ProfileConsumer : itut_x780::ManagedObject { + /* + Structured event fixed header mappings: + domain_type is set to "telecommunications", + type_name is set to "ProfileEvent", and + event_name is set to the constant string + provided below. Only new profiles are announced + through this interface. + */ + + const string profileCreation = "ProfileCreation"; + + /* + Identification of remaining items in filterable data of structured + event. + */ + + const string profileName = "ProfileName"; + const string profileType = "ProfileType"; + const string profileAttributeValues = "ProfileAttributeValues"; + + /* + Values identifying the types of profiles used is provided below. + */ + + const unsigned short AAL1Profile = 1; + const unsigned short AAL2Profile = 2; + const unsigned short AAL2PVCPProfile = 3; + const unsigned short AAL5Profile = 4; + const unsigned short AlarmSeverityAssignmentProfile = 5; + const unsigned short ATMNetworkAccessProfile = 6; + const unsigned short BridgedLANServiceProfile = 7; + const unsigned short CESServiceProfile = 8; + const unsigned short DS1Profile = 9; + const unsigned short DS3Profile = 10; + const unsigned short EthernetProfile = 11; + const unsigned short IDLCCallProcessingProfile = 12; + const unsigned short LESProfile = 13; + const unsigned short MACBridgeServiceProfile = 14; + const unsigned short SSCSPParameterProfile1 = 15; + const unsigned short SSCSPParameterProfile2 = 16; + const unsigned short TrafficDescriptorProfile = 17; + const unsigned short UNIPProfile = 18; + const unsigned short VoiceServiceProfileAAL1 = 19; + const unsigned short VoiceServiceProfileAAL2 = 20; + const unsigned short ThresholdData = 21; + const unsigned short ATMOverbookingFactorProfile = 22; + + /* + Mapping to filterable data within the structured event is provided for + a consumer event that involves the creation of a profile object. + + { + {"ProfileName", any (NameType)}, + {"ProfileType", any (ProfileKindType)}, + {"EventTime", any (GeneralizedTimeType)}, + {"ProfileAttributeValues", any (ProfileStruct)}, + +``` + +``` + + {"NotificationIdentifier", any (NotificationIdentifierType)} + } + + */ + +}; // interface ProfileConsumer + +interface ProfileUsageMgr : itut_x780::ManagedObject { + + // See 9.9.2.1 for the description of the behaviour of this operation + + void reName ( + in NameType oldProfileName, + in NameType newProfileName) + raises (UnknownProfiles, + AccessDenied, + DuplicateProfileName + ); + + // See 9.9.2.2 for the description of the behaviour of this operation + + boolean inUse ( + in NameType profileName) + raises (UnknownProfiles, + AccessDenied); + + // See 9.9.2.3 for the description of the behaviour of this operation + + void suspendUse ( + in NameType profileName) + raises (UnknownProfiles, + AccessDenied); + + // See 9.9.2.4 for the description of the behaviour of this operation + + void resumeUse ( + in NameType profileName) + raises (UnknownProfiles, AccessDenied) ; + + // See 9.9.2.5 for the description of the behaviour of this operation + + void deleteProfile ( + in NameType profileName) + raises (UnknownProfiles, + AccessDenied, + ProfileInUse); + +}; // interface ProfileUsageMgr + +/* +This object is instantiated on the actor called Profile Object Repository. +The Supplier Management System is the client. +*/ + +interface ProfileRetriever : itut_x780::ManagedObject { + +``` + +``` + + // See 9.9.3.1 for the description of the behaviour of this operation + + ProfileInfoType retrieve ( + in NameType profileName) + raises (UnknownProfiles); + +}; // interface ProfileRetriever + +}; // module ProfileManager + +}; // module q834_4 +#endif + +``` + +## C.10 Q834Registrar.idl + +``` + +#ifndef __Q834_4_REGISTRAR_DEFINED +#define __Q834_4_REGISTRAR_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 +{ + module Registrar + { + // begin definitions from other idl files + + // From Q834Common + typedef Q834Common::NameType NameType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::SerialNumType SerialNumType; + typedef Q834Common::ReservationIdType ReservationIdType; + typedef Q834Common::DCNAddressType DCNAddressType; + typedef Q834Common::AdministrationDomainType AdministrationDomainType; + typedef Q834Common::UserLabelSeqType UserLabelSeqType; + +#define AccessDenied Q834Common::AccessDenied +#define CommFailure Q834Common::CommFailure +#define DuplicateUserLabel Q834Common::DuplicateUserLabel +#define EquipmentFailure Q834Common::EquipmentFailure +#define InsufficientPONBW Q834Common::InsufficientPONBW +#define InvalidSerialNumSyntax Q834Common::InvalidSerialNumSyntax +#define MaxSubtendingNodesExceeded Q834Common::MaxSubtendingNodesExceeded +#define UnknownNE Q834Common::UnknownNE +#define UnknownPort Q834Common::UnknownPort +#define DCNTimeout Q834Common::DCNTimeout +#define DeniedAccess Q834Common::DeniedAccess +#define BackupInProgress Q834Common::BackupInProgress +#define UnknownManagedEntity Q834Common::UnknownManagedEntity +#define InvalidUserLabelSyntax Q834Common::InvalidUserLabelSyntax +#define SynchInProgress Q834Common::SynchInProgress + + // End definitions from other idl files + } +} + +``` + +``` + +// Local data types + +// Local exceptions +exception TooManyNEs {}; +exception InvalidDCNAddress {}; +exception AddressLabelMismatch {}; +exception APONLayerFailure {}; +exception InvalidPort {}; +exception HWServicesMismatch {}; + +// End local definitions + +valuetype NERegistrarValueType: itut_x780::ManagedObjectValueType { + public ManagedEntityIdSeqType NEList; // GET +}; + +interface NERegistrar : itut_x780::ManagedObject { + + // See 9.10.1.1 for the description of the behaviour of this operation + ManagedEntityIdType registerNE ( + in DCNAddressType nEDCNAddress, + in UserLabelType nEUserLabel, + in AdministrationDomainType administrationDomain) + raises (AccessDenied, + DCNTimeout, + AddressLabelMismatch, + DuplicateUserLabel, + TooManyNEs, + InvalidDCNAddress, + CanNotAssignManagedEntityId, + CanNotRetrieveUserLabel, + DeniedAccess, + InvalidUserLabelSyntax); + + // See 9.10.1.2 for the description of the behaviour of this operation + void modifyNEDCNAddress ( + in ManagedEntityIdType nEManagedEntityId, + in DCNAddressType newNEDCNAddress) + raises (AccessDenied, + DeniedAccess, + AddressLabelMismatch, + DCNTimeout, + CommFailure, + UnknownNE, + InvalidDCNAddress, + BackupInProgress); + + // See 9.10.1.3 for the description of the behaviour of this operation + ManagedEntityIdType rangeONTorONU ( + in ManagedEntityIdType oltManagedEntityId, + in UserLabelType nEUserLabel, + in SerialNumType serialNum, + in ManagedEntityIdType port ) // OLT PON Port + raises (AccessDenied, + CommFailure, + +``` + +``` + + EquipmentFailure, + UnknownNE, + UnknownPort, + MaxSubtendingNodesExceeded, + InsufficientPONBW, + InvalidSerialNumSyntax, + APONLayerFailure, + DuplicateUserLabel, + InvalidUserLabelSyntax, + BackupInProgress, + SynchInProgress ); + +// See 9.10.1.4 for the description of the behaviour of this operation + +ManagedEntityIdType rangeReplacementNE ( + in ManagedEntityIdType oldNEManagedEntityId, + in UserLabelType newNEUserLabel, + in SerialNumType replacementSerialNum ) +raises (AccessDenied, + CommFailure, + UnknownNE, + InvalidSerialNumSyntax, + APONLayerFailure, + EquipmentFailure, + InvalidUserLabelSyntax, + DuplicateUserLabel, + HWServicesMismatch, + BackupInProgress, + SynchInProgress); + +// See 9.10.1.5 for the description of the behaviour of this operation + +ManagedEntityIdType rangeUpgradeNE ( + in ManagedEntityIdType oldNEManagedEntityId, + in ManagedEntityIdType newNEManagedEntityId, + in UserLabelType newNEUserLabel, + in SerialNumType newNESerialNum ) +raises (AccessDenied, + CommFailure, + UnknownNE, + InvalidSerialNumSyntax, + APONLayerFailure, + EquipmentFailure, + InvalidUserLabelSyntax, + DuplicateUserLabel, + HWServicesMismatch, + BackupInProgress, + SynchInProgress); + +// See 9.10.1.6 for the description of the behaviour of this operation + +ManagedEntityIdType moveONTorONU( + in ManagedEntityIdType oldNEManagedEntityId, + in ManagedEntityIdType newPONPort) +raises (AccessDenied, + CommFailure, + UnknownPort, + APONLayerFailure, + EquipmentFailure, + InsufficientPONBW, + BackupInProgress, + SynchInProgress, + UnknownNE ); + +``` + +``` + +// See 9.10.1.7 for the description of the behaviour of this operation + +ManagedEntityIdSeqType getSubtendingNEList( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, AccessDenied); + +// See 9.10.1.8 for the description of the behaviour of this operation + +ManagedEntityIdSeqType nEListGet () + raises (AccessDenied); + +// See 9.10.1.9 for the description of the behaviour of this operation + +void deRegisterNE( + in ManagedEntityIdType nE) + raises (UnknownNE, + AccessDenied); + +// See 9.10.1.10 for the description of the behaviour of this +operation + +ManagedEntityIdType associateNE( +in ManagedEntityIdType preProvisionedNE, + in ManagedEntityIdType discoveredNE) + raises (UnknownManagedEntity, + AccessDenied); + +}; // interface NERegistrar + +}; // module Registrar + +}; // module q834_4 + +#endif + +``` + +## C.11 Q834ResourceAllocation.idl + +``` + +#ifndef __Q834_4_RESOURCEALLOCATOR_DEFINED +#define __Q834_4_RESOURCEALLOCATOR_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module ResourceAllocation { + + // Begin definitions from other idl files + + // From Q834Common + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::NameSeqType NameSeqType; + typedef Q834Common::ReservationIdType ReservationIdType; + typedef Q834Common::ReservationIdSeqType ReservationIdSeqType; + typedef Q834Common::ServiceInstanceIdType ServiceInstanceIdType; + typedef Q834Common::EndPointType EndPointType; + +#define AccessDenied Q834Common::AccessDenied +#define CommFailure Q834Common::CommFailure + +``` + +``` + +#define ConnectionCountExceeded Q834Common::ConnectionCountExceeded +#define InsufficientBW Q834Common::InsufficientBW +#define MaxSubtendingNodesExceeded Q834Common::MaxSubtendingNodesExceeded +#define UnknownNE Q834Common::UnknownNE +#define UnknownPort Q834Common::UnknownPort +#define UnknownProfiles Q834Common::UnknownProfiles +#define UnknownReservationId Q834Common::UnknownReservationId +#define UnknownServiceInstance Q834Common::UnknownServiceInstance +#define ProfileSuspended Q834Common::ProfileSuspended + +// End of definitions from other idl files + +// Local data types + +struct BandwidthInfoType { + long upstreamBW; + long downstreamBW; +}; + +struct PortBandwidthType { + BandwidthInfoType portBandwidth; + ManagedEntityIdType portId; +}; + +typedef sequence PortBandwidthSeqType; +typedef PortBandwidthSeqType AvailableSysBandwidthSeqType; +typedef PortBandwidthSeqType ReservedBandwidthSeqType; + +struct ReservationInfoType { + ReservationIdType reservationId; + EndPointType endPointA; + EndPointType endPointB; + NameSeqType profileNameList; // servicetemplates + ServiceInstanceIdType serviceInstanceId; + ReservedBandwidthSeqType reservedBandwidth; +}; + +struct ReservationBandwidthType { + ReservationIdType reservationId; + ReservedBandwidthSeqType reservedBandwidth; +}; + +// Local exceptions + +// End local definitions + +interface ResourceAllocator : itut_x780::ManagedObject { + + // See 9.11.1.1 for the description of the behaviour of this operation + + ReservationBandwidthType reserveForService( + in EndPointType endPointA, + in EndPointType endPointZ, + in NameSeqType networkCharacteristicsProfiles, + in ServiceInstanceIdType serviceInstanceId ) + raises (UnknownNE, + UnknownPort, + UnknownProfiles, + InsufficientBW, + MaxSubtendingNodesExceeded, + +``` + +``` + + ConnectionCountExceeded, + CommFailure, + AccessDenied, + ProfileSuspended ); + +// See 9.11.1.2 for the description of the behaviour of this operation + +AvailableSysBandwidthSeqType cancelReservation ( + in ReservationIdType reservationId ) + raises (UnknownReservationId, + CommFailure, + AccessDenied); + +// See 9.11.1.3 for the description of the behaviour of this operation + +ReservationIdType getReservationId ( + in ServiceInstanceIdType serviceInstanceId) + raises (UnknownServiceInstance, AccessDenied); + +// See 9.11.1.4 for the description of the behaviour of this operation + +ReservedBandwidthSeqType reportReservedResources ( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, AccessDenied); + +// See 9.11.1.5 for the description of the behaviour of this operation + +ReservationIdSeqType getReservations( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, AccessDenied); + +// See 9.11.1.6 for the description of the behaviour of this operation + +AvailableSysBandwidthSeqType cancelAllRemainingReservations( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, + CommFailure, + AccessDenied); + +// See 9.11.1.7 for the description of the behaviour of this operation + +ReservationInfoType getReservation ( + in ReservationIdType reservationId) + raises (UnknownReservationId, + AccessDenied); + +// See 9.11.1.8 for the description of the behaviour of this operation + +AvailableSysBandwidthSeqType getAvaliableSysBandwidth( + in ManagedEntityIdType nEManagedEntityId) + raises (UnknownNE, + CommFailure, + AccessDenied); + +}; // interface ResourceAllocator + +}; // module ResourceAllocation + +}; // module q834_4 + +#endif + +``` + +## C.12 Q834SchedulerManagement.idl + +``` +#ifndef __Q834_4_SCHEDULERMGR_DEFINED +#define __Q834_4_SCHEDULERMGR_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 { + + module SchedulerManagement { + // Begin definitions from other idl files + + // From Q834Common + + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::GeneralizedTimeType GeneralizedTimeType; + typedef Q834Common::AdministrativeStateType AdministrativeStateType; + typedef Q834Common::OperationalStateType OperationalStateType; + +#define AccessDenied Q834Common::AccessDenied +#define DuplicateUserLabel Q834Common::DuplicateUserLabel +#define UnknownScheduler Q834Common::UnknownScheduler +#define InvalidStartTime Q834Common::InvalidStartTime +#define InvalidStopTime Q834Common::InvalidStopTime + + // End definitions from other idl files + + // Local data types + + enum HourlyDailyWeeklyMonthlyIndType { + Hourly, + Daily, + Weekly, + Monthly + }; + + enum DayOfWeekType { + Sunday, + Monday, + Tuesday, + Wednesday, + Thursday, + Friday, + Saturday, + Unspecified + }; + + typedef short DayOfMonthType; // 0 is interpreted to mean unspecified. + + struct TriggerTimeType + { + long time; // trigger time in number of seconds + DayOfWeekType dayOfWeek; + DayOfMonthType dayOfMonth; + }; + + typedef sequence TriggerTimeMatrixSeqType; + + struct SchedulerType +``` + +``` + +{ + UserLabelType schedulerName; + GeneralizedTimeType startTime; // schedule start time + GeneralizedTimeType stopTime; // schedule stop time + HourlyDailyWeeklyMonthlyIndType hourlyDailyWeeklyMonthlyInd; + TriggerTimeMatrixSeqType matrix; + OperationalStateType operationalState; + AdministrativeStateType administrativeState; +}; + +typedef sequence SchedulerSeqType; + +// Local exceptions + +exception MatrixSchedulerTypeMismatch {}; +exception InvalidTrigger {}; +exception ScheduleInUse {}; + +// End local definitions + +valuetype SchedulerMgrValueType: itut_x780::ManagedObjectValueType { + + public SchedulerSeqType schedulerList; // GET + +}; + +interface SchedulerMgr : itut_x780::ManagedObject { + + // See 9.12.1.1 for the description of the behaviour of this operation + + void makeScheduler ( + in UserLabelType schedulerName, + in GeneralizedTimeType startTime, + in GeneralizedTimeType stopTime, + in HourlyDailyWeeklyMonthlyIndType hourlyDailyWeeklyMonthlyInd, + in TriggerTimeMatrixSeqType matrix) + raises (InvalidStartTime, + InvalidStopTime, + DuplicateUserLabel, + MatrixSchedulerTypeMismatch, + AccessDenied, + InvalidTrigger ); + + // See 9.12.1.2 for the description of the behaviour of this operation + + void suspendScheduler ( + in UserLabelType schedulerName) + raises (UnknownScheduler, + AccessDenied ); + + // See 9.12.1.3 for the description of the behaviour of this operation + + void resumeScheduler (in UserLabelType schedulerName) raises +(UnknownScheduler, AccessDenied ); + + // See 9.12.1.4 for the description of the behaviour of this operation + + void modifyTime ( + in UserLabelType schedulerName, + in GeneralizedTimeType newStartTime, + +``` + +``` + + in GeneralizedTimeType newStopTime) + raises (InvalidStartTime, + InvalidStopTime, + UnknownScheduler, + AccessDenied ); + +// See 9.12.1.5 for the description of the behaviour of this operation + +void changeSchedulerName ( + in UserLabelType oldSchedulerName, + in UserLabelType newSchedulerName) + raises (UnknownScheduler, + DuplicateUserLabel, + AccessDenied ); + +// See 9.12.1.6 for the description of the behaviour of this operation + +void modifyTriggerTimes ( + in UserLabelType schedulerName, + in HourlyDailyWeeklyMonthlyIndType newHourlyDailyWeeklyMonthly, + in TriggerTimeMatrixSeqType newMatrix) + raises (UnknownScheduler, + MatrixSchedulerTypeMismatch, + AccessDenied, + InvalidTrigger ); + +// See 9.12.1.7 for the description of the behaviour of this operation + +void removeScheduler ( + in UserLabelType schedulerName) + raises (UnknownScheduler, + AccessDenied, + ScheduleInUse ); + +// See 9.12.1.8 for the description of the behaviour of this operation + +SchedulerType retrieveScheduler (in UserLabelType schedulerName) + raises (UnknownScheduler, + AccessDenied) ; + +// See 9.12.1.9 for the description of the behaviour of this operation + +SchedulerSeqType schedulerListGet () raises (AccessDenied); + +}; // interface SchedulerMgr + +}; // module SchedulerManagement + +}; // module q834_4 + +#endif + +``` + +## C.13 Q834ServiceProvisioning.idl + +``` + +#ifndef __Q834_4_SERVICEPROVISIONING_DEFINED +#define __Q834_4_SERVICEPROVISIONING_DEFINED + +#include "Q834Common.idl" +#include "Q834ProfileManager.idl" + +#pragma prefix "itu.Int" + +``` + +``` + +module q834_4 { + +module ServiceProvisioning { + +// Begin definitions from other idl files + +// From Q834Common + typedef Q834Common::RDNTType RDNTType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::NameSeqType NameSeqType; + typedef Q834Common::ServiceInstanceIdType ServiceInstanceIdType; + typedef Q834Common::ReservationIdType ReservationIdType; + typedef Q834Common::EndPointType EndPointType; + typedef Q834Common::NameType NameType; + typedef Q834Common::AdministrativeStateType AdministrativeStateType; + typedef Q834Common::GeneralizedTimeType GeneralizedTimeType; + +#define AccessDenied Q834Common::AccessDenied +#define CommFailure Q834Common::CommFailure +#define ConnectionCountExceeded Q834Common::ConnectionCountExceeded +#define EquipmentFailure Q834Common::EquipmentFailure +#define InsufficientBW Q834Common::InsufficientBW +#define InsufficientPONBW Q834Common::InsufficientPONBW +#define UnknownProfiles Q834Common::UnknownProfiles +#define UnknownReservationId Q834Common::UnknownReservationId +#define UnknownNE Q834Common::UnknownNE +#define UnknownServiceInstance Q834Common::UnknownServiceInstance +#define ProfileSuspended ProfileManager::ProfileSuspended +#define InvalidStartTime Q834Common::InvalidStartTime +#define InvalidStopTime Q834Common::InvalidStopTime +#define ParameterViolation Q834Common::ParameterViolation +#define UnknownPort Q834Common::UnknownPort +#define ProfileSuspended Q834Common::ProfileSuspended + +// End definitions from other idl files + +// Local data types + +// Local exceptions + exception UnknownConnection {}; + exception ConnectionAlreadyExists {}; + +// End local definitions + + interface ServiceProvisioner : itut_x780::ManagedObject { + + // See 9.13.1.1 for the description of the behaviour of this operation + + ManagedEntityIdType provisionConnection( + in EndPointType endPointA, + in EndPointType endPointB, + in NameSeqType networkCharacteristicsProfiles, + in ServiceInstanceIdType serviceInstanceId, + in AdministrativeStateType administrativeState) + raises (UnknownNE, + UnknownProfiles, + UnknownPort, + InsufficientBW, + ConnectionCountExceeded, + CommFailure, + EquipmentFailure, + +``` + +``` + + ParameterViolation, + AccessDenied, + InsufficientPONBW, + ConnectionAlreadyExists, + ProfileSuspended); + +// See 9.13.1.2 for the description of the behaviour of this operation + +ManagedEntityIdType provisionReservation( + in ReservationIdType reservationId, + in AdministrativeStateType administrativeState) + raises (UnknownReservationId, + AccessDenied); + +// See 9.13.1.3 for the description of the behaviour of this operation + +void deleteConnection ( + in ManagedEntityIdType subnetworkConnectionId) + raises (UnknownConnection, + CommFailure, + EquipmentFailure, + AccessDenied); + +// See 9.13.1.4 for the description of the behaviour of this operation + +ManagedEntityIdType modifyConnection ( + in ManagedEntityIdType subnetworkConnectionId, + in ManagedEntityIdType portB, + in NameSeqType newNetworkCharacteristicsProfiles) + raises (UnknownConnection, + UnknownPort, + UnknownProfiles, + InsufficientBW, + AccessDenied, + ProfileSuspended); + +// See 9.13.1.5 for the description of the behaviour of this operation + +void suspendService ( + in ServiceInstanceIdType serviceInstanceId, + in GeneralizedTimeType startTime, + in GeneralizedTimeType stopTime) + raises (UnknownServiceInstance, + InvalidStartTime, + InvalidStopTime, + AccessDenied); + +// See 9.13.1.6 for the description of the behaviour of this operation + +void resumeService( + in ServiceInstanceIdType serviceInstanceId) + raises (UnknownServiceInstance, + AccessDenied); + +}; // interface ServiceProvisioner + +}; // module ServiceProvisioning + +}; // module q834_4 + +#endif + +``` + +## C.14 Q834Synchroniser.idl + +``` +#ifndef __Q834_4_SYNCHRONISER_DEFINED +#define __Q834_4_SYNCHRONISER_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 +{ + +module Synchroniser +{ + +// begin definitions from other idl files + +// From Q834Common + typedef Q834Common::NameType NameType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + +#define AccessDenied Q834Common::AccessDenied +#define CommFailure Q834Common::CommFailure +#define DCNTimeout Q834Common::DCNTimeout +#define EquipmentFailure Q834Common::EquipmentFailure +#define UnknownNE Q834Common::UnknownNE +#define UnknownScheduler Q834Common::UnknownScheduler +#define InvalidScheduler Q834Common::InvalidScheduler +#define BackupInProgress Q834Common::BackupInProgress +#define Timeout Q834Common::Timeout +#define SynchInProgress Q834Common::SynchInProgress + +// End definitions from other idl files + +// Local data types + + typedef sequence CurrentListingSeqType; + + struct ScheduledSynchNEType { + ManagedEntityIdType managedEntityId; + UserLabelType schedulerName; + }; + typedef sequence ScheduledSynchNESeqType; + +// Local exceptions + exception NoSynchInProgress {}; + +// End local definitions + + valuetype SynchroniserValueType: itut_x780::ManagedObjectValueType { + + public ScheduledSynchNESeqType scheduledSynchNEList; // GET + + }; + + interface NESynchroniser : itut_x780::ManagedObject { + + // Define constants for current event listings +``` + +``` + +const short CURRENT_ALARM = 1; +const short CURRENT_OPERATIONAL_STATE_DISABLED = 2; +const short CURRENT_ADMINISTRATIVE_STATE_LOCKED = 3; +const short CURRENT_PROTECTION_SWITCHING_EVENT = 4; +const short CURRENT_SERVICE_OUTAGE = 5; + +// See 9.14.1.1 for the description of the behaviour of this operation + +void synchNE( + in ManagedEntityIdType nManagedEntityId) + raises (AccessDenied, + CommFailure, + UnknownNE, + EquipmentFailure, + BackupInProgress, + SynchInProgress); + +// See 9.14.1.2 for the description of the behaviour of this operation + +void abortSynchNE( + in ManagedEntityIdType nManagedEntityId) + raises (AccessDenied, + CommFailure, + UnknownNE, + EquipmentFailure, + NoSynchInProgress); + +// See 9.14.1.3 for the description of the behaviour of this operation + +void scheduleSynchNE( + in ManagedEntityIdType nManagedEntityId, + in UserLabelType schedulerName) + raises (AccessDenied, + UnknownNE, + UnknownScheduler, + InvalidScheduler); + +// See 9.14.1.4 for the description of the behaviour of this operation + +void modifyNESynchSchedule( + in ManagedEntityIdType nManagedEntityId, + in UserLabelType newSchedulerName) + raises (AccessDenied, + UnknownNE, + UnknownScheduler, + InvalidScheduler); + +// See 9.14.1.5 for the description of the behaviour of this operation + +void cancelScheduledSynchNE( + in ManagedEntityIdType nManagedEntityId) + raises (AccessDenied, + UnknownNE); + +// See 9.14.1.6 for the description of the behaviour of this operation + +void synchCurrentEventListings( + in ManagedEntityIdType nManagedEntityId, + in CurrentListingSeqType currentListingTypeList) + raises (AccessDenied, + CommFailure, + DCNTimeout, + UnknownNE, + +``` + +``` + + EquipmentFailure, + Timeout); + + // See 9.14.1.7 for the description of the behaviour of this operation + + ScheduledSynchNESeqType scheduledSynchNEListGet () + raises (AccessDenied); + +}; // interface NESynchroniser + +}; // module Synchroniser + +}; // module q834_4 + +#endif + +``` + +## C.15 Q834Test.idl + +``` + +#ifndef __Q834_4_TEST_DEFINED +#define __Q834_4_TEST_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 +{ + module Test + { + // begin definitions from other idl files + + // From Q834Common + + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::ManagedEntityIdSeqType ManagedEntityIdSeqType; + typedef Q834Common::UserIdType UserIdType; + typedef Q834Common::GeneralizedTimeType GeneralizedTimeType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::LoopbackLocationIdSeqType + LoopbackLocationIdSeqType; + typedef Q834Common::StatusValueType StatusValueType; + typedef Q834Common::ServiceInstanceIdType ServiceInstanceIdType; + typedef Q834Common::TrackingObjectIdType TrackingObjectIdType; + +#define AccessDenied Q834Common::AccessDenied +#define CommFailure Q834Common::CommFailure +#define UnknownScheduler Q834Common::UnknownScheduler +#define InvalidScheduler Q834Common::InvalidScheduler +#define InvalidStopTime Q834Common::InvalidStopTime +#define InvalidStartTime Q834Common::InvalidStartTime +#define UnknownManagedEntity Q834Common::UnknownManagedEntity +#define UnknownNE Q834Common::UnknownNE +#define UnknownServiceInstance Q834Common::UnknownServiceInstance + + // End definitions from other idl files + + // Local data types + } +} + +``` + +``` + +enum DirectionalityType { + Egress, + Ingress, + BothDirections +}; + +struct ATMLoopbackInfoType { + DirectionalityType directionality; + LoopbackLocationIdSeqType targetLLID; + boolean segmentCellInd; +}; + +typedef unsigned short TestIterationNumType; + +struct ATMLoopbackResultType { + LoopbackLocationIdSeqType loopbackingLLID; + unsigned long responseTime; //in microseconds + boolean succeeded; //true or false +}; + +typedef sequence ATMLoopbackResultSeqType; + +struct AggregateATMLoopbackResultType { + unsigned short iterationSeqNum; + ATMLoopbackResultSeqType iterationTestResults; +}; + +typedef sequence +AggregateATMLoopbackResultSeqType; + +struct ATMContinuityCheckInfoType { + DirectionalityType directionality; + boolean segmentCellInd; +}; + +typedef short DiagnosticType; // Supplier specific. +typedef DiagnosticType ResourceSelfTestInfoType; +typedef sequence ResourceSelfTestInfoSeqType; + +struct ResourceSelfTestResultType { + DiagnosticType diagnostic; + boolean testPassed; +}; + +typedef sequence +ResourceSelfTestResultSeqType; +typedef long long CCSetUpIdType; +typedef TrackingObjectIdType TestTrackingObjectIdType; +typedef long long LoopbackTrackingObjectIdType; + +typedef unsigned short LoopbackTestType; + +struct LoopbackInfoType { + LoopbackTrackingObjectIdType trackingId; + unsigned long remainingTime; // in seconds +ManagedEntityIdType ctpId; + LoopbackTestType loopbackTest; + DirectionalityType directionality; +}; + +typedef sequence LoopbackInfoSeqType; + +``` + +``` + +typedef string SupportedTestType; + +typedef sequence SupportedTestSeqType; + +struct ScheduledTestNEType { + ManagedEntityIdType managedEntityId; + SupportedTestType supportedTest; + UserLabelType schedulerName; +}; +typedef sequence ScheduledTestNESeqType; + +struct TestHistoryType { + ManagedEntityIdType managedEntityId; + SupportedTestType supportedTest; + StatusValueType testStatus; +}; +typedef sequence TestHistorySeqType; + +// Local exceptions + +exception InvalidTimeoutPeriod {}; +exception NotAvailableForTest {}; +exception InvalidLocationId {}; +exception UnknownTest {}; +exception UncontrolledTestInProgress {}; +exception InvalidDirection {}; +exception InvalidTestOperations {}; + +// End local definitions + +valuetype TestActionPerformerValueType: itut_x780::ManagedObjectValueType { + + public ScheduledTestNESeqType scheduledTestNEList; // GET + +}; + +interface TestActionPerformer : itut_x780::ManagedObject { + + // See 9.15.1.1 for the description of the behaviour of this operation + + AggregateATMLoopbackResultSeqType aTMLoopback ( + in UserIdType testRequestorId, + in ManagedEntityIdType ctp, + in ATMLoopbackInfoType aTMLoopbackInfo, + in TestIterationNumType testIterationNum, + in ServiceInstanceIdType serviceInstanceId) + raises (AccessDenied, + CommFailure, + UnknownManagedEntity, + NotAvailableForTest, + InvalidLocationId, + InvalidDirection); + + // See 9.15.1.2 for the description of the behaviour of this operation + + CCSetUpIdType initializeContinuityCheck( + in UserIdType testRequestorId, + in ManagedEntityIdType sourceCtp, + in ATMContinuityCheckInfoType atmContinuityCheckInfo, + in GeneralizedTimeType stopTime, + in ServiceInstanceIdType serviceInstanceId) + raises (AccessDenied, + CommFailure, + +``` + +``` + + UnknownManagedEntity, + NotAvailableForTest, + InvalidStartTime, + InvalidStopTime, + InvalidDirection); + +// See 9.15.1.3 for the description of the behaviour of this operation + +void terminateContinuityCheck( + in CCSetUpIdType cCSetUpId) + raises (AccessDenied, + CommFailure, + UnknownTest); + +// See 9.15.1.4 for the description of the behaviour of this operation + +TestTrackingObjectIdType scheduleResourceSelfTest ( + in UserIdType testRequestorId, + in ManagedEntityIdType targetNE, + in unsigned long timeOutPeriod, //In seconds. + in ResourceSelfTestInfoSeqType specificTestInfo, + in UserLabelType schedulerName) + raises (AccessDenied, + UnknownNE, + UnknownScheduler, + InvalidScheduler, + InvalidTimeoutPeriod, + InvalidTestOperations); + +// See 9.15.1.5 for the description of the behaviour of this operation + +void modifyResourceSelfTestSchedule( + in TestTrackingObjectIdType testTrackingObjectId, + in UserLabelType newSchedulerName) + raises (AccessDenied, + UnknownTest, + UnknownScheduler, + InvalidScheduler); + +// See 9.15.1.6 for the description of the behaviour of this operation + +void cancelScheduledResourceSelfTest ( + in TestTrackingObjectIdType testTrackingObjectId) + raises (AccessDenied, + UnknownTest); + +// See 9.15.1.7 for the description of the behaviour of this operation + +TestTrackingObjectIdType conductResourceSelfTest ( + in UserIdType testRequestorId, + in ManagedEntityIdType targetNE, + in unsigned long timeOutPeriod, //In seconds. + in ResourceSelfTestInfoSeqType specificTestInfo) + raises (AccessDenied, + CommFailure, + UnknownNE, + InvalidTimeoutPeriod, + InvalidTestOperations); + +// See 9.15.1.8 for the description of the behaviour of this operation + +ResourceSelfTestResultSeqType terminateResourceSelfTest ( + in TestTrackingObjectIdType testTrackingObjectId) + raises (UnknownTest, + +``` + +``` + + UncontrolledTestInProgress, + AccessDenied); + +// See 9.15.1.9 for the description of the behaviour of this operation + +LoopbackTrackingObjectIdType initiateLoopback ( + in UserIdType testRequestorId, + in ManagedEntityIdType loopingCtp, + in long duration, //In minutes. + in DirectionalityType directionality, + in LoopbackTestType loopbackTest, + in ServiceInstanceIdType serviceInstanceId) + raises (AccessDenied, + CommFailure, + UnknownManagedEntity, + NotAvailableForTest); + +// See 9.15.1.10 for the description of the behaviour of this +operation + +void terminateLoopback( + in LoopbackTrackingObjectIdType testTrackingObjectId) + raises (UnknownTest, + AccessDenied); + +// See 9.15.1.11 for the description of the behaviour of this +operation + +LoopbackInfoType getLoopbackInfo( + in ManagedEntityIdType cTP) + raises (UnknownManagedEntity, + AccessDenied); + +// See 9.15.1.12 for the description of the behaviour of this +operation + +LoopbackInfoSeqType getLoopbackInfoByNE( + in ManagedEntityIdType nEId) + raises (UnknownManagedEntity, + AccessDenied); + +// See 9.15.1.13 for the description of the behaviour of this +operation + +StatusValueType getTestStatus ( + in LoopbackTrackingObjectIdType id) + raises (AccessDenied, + UnknownTest); + +// See 9.15.1.14 for the description of the behaviour of this +operation + +ScheduledTestNESeqType scheduledTestNEListGet () + raises (AccessDenied); + +// See 9.15.1.15 for the description of the behaviour of this +operation + +TestHistorySeqType testHistoryByManagedEntity ( + in ManagedEntityIdType managedEntityId) + raises (UnknownManagedEntity, + AccessDenied); + +``` + +``` + + // See 9.15.1.16 for the description of the behaviour of this + operation + + TestHistorySeqType testHistoryByServiceInstance ( + in ServiceInstanceIdType serviceInstanceId) + raises (UnknownServiceInstance, + AccessDenied); + +}; // interface TestActionPerformer + +}; // module Test + +}; // module q834_4 + +#endif + +``` + +## C.16 Q834Filetransfer.idl + +``` + +#ifndef __Q834_4_TRANSFERMGR_DEFINED +#define __Q834_4_TRANSFERMGR_DEFINED + +#include "Q834Common.idl" + +#pragma prefix "itu.Int" + +module q834_4 +{ + + module FileTransfer + { + + // begin definitions from other idl files + + // From Q834Common + + typedef Q834Common::ManagedEntityIdType ManagedEntityIdType; + typedef Q834Common::UserLabelType UserLabelType; + typedef Q834Common::StatusValueType StatusValueType; + typedef Q834Common::DCNAddressType DCNAddressType; + typedef Q834Common::FilenameType FilenameType; + typedef Q834Common::TransferTrackingObjectIdType + TransferTrackingObjectIdType; + typedef Q834Common::UserIdType UserIdType; + typedef Q834Common::PasswordType PasswordType; + typedef Q834Common::GeneralizedTimeType GeneralizedTimeType; + +#define AccessDenied Q834Common::AccessDenied +#define CommFailure Q834Common::CommFailure +#define UnknownScheduler Q834Common::UnknownScheduler +#define UnknownDestinationServer Q834Common::UnknownDestinationServer +#define InvalidScheduler Q834Common::InvalidScheduler +#define UnknownRecordSet Q834Common::UnknownRecordSet + + // End definitions from other idl files + + // Local data types + + struct FileTransferHistoryType { + ManagedEntityIdType recordSetId; + DCNAddressType destinationServerAddr; + UserIdType userId; + +``` + +``` + + FilenameType destinationFile; + GeneralizedTimeType transferTime; +}; +typedef sequence FileTransferHistorySeqType; + +struct ScheduledFileTransferType { + ManagedEntityIdType recordSetId; + UserLabelType schedulerName; +}; +typedef sequence ScheduledFileTransferSeqType; + +// Local exceptions + + exception UnknownTransferProcess {}; + +// End local definitions + +valuetype TransferMgrValueType: itut_x780::ManagedObjectValueType { + + public FileTransferHistorySeqType fileTransferHistoryList; // GET + public ScheduledFileTransferSeqType scheduledFileTransferList; // GET + +}; + +interface TransferMgr : itut_x780::ManagedObject { + + // See 9.16.1.1 for the description of the behaviour of this operation + + TransferTrackingObjectIdType fileTransfer( + in ManagedEntityIdType recordSetId, + in DCNAddressType destinationServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType destinationFile, + in boolean overwriteExistingFile) + raises (AccessDenied, + CommFailure, + UnknownRecordSet, + UnknownDestinationServer + ); + + // See 9.16.1.2 for the description of the behaviour of this operation + + TransferTrackingObjectIdType scheduleFileTransfer( + in ManagedEntityIdType recordSetId, + in DCNAddressType destinationServerAddr, + in UserIdType userId, + in PasswordType password, + in FilenameType destinationFile, + in boolean overwriteExistingFile, + in UserLabelType schedulerName) + raises (AccessDenied, + UnknownRecordSet, + UnknownDestinationServer, + UnknownScheduler, + InvalidScheduler); + + // See 9.16.1.3 for the description of the behaviour of this operation + + void modifyFileTransferSchedule( + in TransferTrackingObjectIdType transferTrackingObjectId, + in UserLabelType newSchedulerName) + +``` + +``` + + raises (AccessDenied, + UnknownTransferProcess, + UnknownScheduler, + InvalidScheduler); + +// See 9.16.1.4 for the description of the behaviour of this operation + +void cancelScheduledFileTransfer ( + in TransferTrackingObjectIdType transferTrackingObjectId) + raises (AccessDenied, + UnknownTransferProcess); + +// See 9.16.1.5 for the description of the behaviour of this operation + +StatusValueType getStatus( + in TransferTrackingObjectIdType transferTrackingObjectId) + raises (UnknownTransferProcess, + AccessDenied); + +// See 9.16.1.6 for the description of the behaviour of this operation + +FileTransferHistorySeqType fileTransferHistoryListGet () + raises (AccessDenied); + +// See 9.16.1.7 for the description of the behaviour of this operation + +ScheduledFileTransferSeqType scheduledFileTransferListGet () + raises (AccessDenied); + +}; // interface TransferMgr + +}; // module FileTransfer + +}; // module q834_4 + +#endif + +``` + +# Annex D + +## Example endpoint templates + +Tables D.1 and D.2 provide example templates of how an endpoint might be defined by service type. Table D.1 shows examples for the case when the endpoint is part of an NNI port. Table D.2 shows examples for the case when the endpoint is part of a UNI port. + +**Table D.1/Q.834.4 – NNI port endpoints** + +| Service type | Port | Parameter | Profiles | +|--------------|----------|--------------------------------------|-------------------------------------------------------------------------------| +| DS1 | TDM DS3 | Channel # | – | +| DS3 | TDM DS3 | – | – | +| DS1 | ATM DS3 | VPI/VCI | – | +| DS3 | ATM DS3 | VPI/VCI | – | +| DS1 | TDM OC-n | STS #/VT1.5 # | – | +| DS1 | ATM OC-n | VPI/VCI | – | +| DS3 | ATM OC-n | VPI/VCI | – | +| Bridged LAN | ATM OC-n | VPI/VCI | – | +| Bridged LAN | ATM DS3 | VPI/VCI | – | +| Bridged LAN | TDM DS3 | Channel # | – | +| Bridged LAN | TDM OC-n | STS #/VT1.5 # | – | +| Voice | ATM DS3 | VPI/VCI
CID | TrafficDescriptorProfile
(ingress)
TrafficDescriptorProfile
(egress) | +| Voice | – | Interface Group #/
Call Ref Value | – | +| ATM | ATM | VPI/VCI | TrafficDescriptorProfile
(ingress)
TrafficDescriptorProfile
(egress) | + +**Table D.2/Q.834.4 – UNI port endpoints** + +| Service type | Port | Parameter | Profiles | +|---------------------|----------------------|------------------|-------------------------------------------------------------------------------------------| +| DS1 | TDM DS3 | Channel # | DS1Profile
CESProfile
AAL1Profile | +| DS3 | TDM DS3 | – | DS3Profile
CESProfile
AAL1Profile | +| DS1 | ATM DS3 | VPI/VCI | – | +| DS3 | ATM DS3 | VPI/VCI | – | +| DS1 | TDM OC-n or
STS-n | STS #/VT1.5 # | AAL1Profile
CESProfile | +| DS1 | ATM OC-n | VPI/VCI | – | +| DS3 | ATM OC-n | VPI/VCI | – | +| Bridged LAN | Ethernet | Logical port # | BridgedLANServiceProfile
AAL5Profile or
AAL1Profile | +| Voice | RJ-11 | – | VoiceServiceProfileAAL2
SSCSPParameterProfile1
SSCSPParameterProfile2
LESService | +| Voice | RJ-11 | – | VoiceServiceProfileAAL1 | +| ATM | ATM | VPI/VCI | TrafficDescriptorProfile
(ingress)
TrafficDescriptorProfile
(egress) | +| VLAN | Ethernet | VLAN tag | – | + + + + + +# 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.835-199903-I_PDF-E/raw.md b/marked/Q/T-REC-Q.835-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5457e36c09718343b29e6fb43653d7d9322fb582 --- /dev/null +++ b/marked/Q/T-REC-Q.835-199903-I_PDF-E/raw.md @@ -0,0 +1,3851 @@ + + +![ITU logo: a globe with the letters ITU inside, crossed by a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU inside, crossed by a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.835** + +(03/99) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Q3 interface + +# --- **Line and line circuit test management of ISDN and analogue customer accesses** + +ITU-T Recommendation Q.835 + +(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.* + +# **LINE AND LINE CIRCUIT TEST MANAGEMENT OF ISDN AND ANALOGUE CUSTOMER ACCESSES** + +## **Summary** + +The purpose of this Recommendation is to define the Q3 interface between a network element for customer access (i.e. local exchange, access network) and the telecommunications management network (TMN) for the support of line and line circuit test functions and the associated management for ISDN and analogue customer accesses which are connected either directly to a local exchange or remotely at an access network and across V5.1 and/or V5.2 interfaces to a local exchange. + +The focus of this Recommendation is on defining an object model based on ITU-T Recommendations Q.824.0, Q.824.5, Q.831, and X.745. Existing protocols are used where possible. The definition of Operations System (OS) functionality is outside the scope of this Recommendation. + +## **Source** + +ITU-T Recommendation Q.835 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of March 1999. + +### **Keywords** + +Access network, information model, line and line circuit testing, local exchange, Q3 interface, TMN. + +## 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 Terms and definitions, abbreviations..... | 3 | +| 3.1 Definitions ..... | 3 | +| 3.2 Abbreviations..... | 4 | +| 4 Line and line circuit testing functions..... | 4 | +| 4.1 Description of the service ..... | 4 | +| 4.2 Components of service..... | 5 | +| 4.3 Management function list ..... | 5 | +| 4.4 Description of management functions ..... | 6 | +| 5 Information model diagrams..... | 6 | +| 5.1 Entity relationship diagram..... | 7 | +| 5.1.1 Line testing and line circuit testing..... | 7 | +| 5.1.2 The testResultNotifications of the tests..... | 8 | +| 5.2 Inheritance hierarchy..... | 8 | +| 5.3 Naming hierarchy..... | 9 | +| 6 Formal object class definitions ..... | 10 | +| 6.1 Definitions of object classes ..... | 10 | +| 6.1.1 Access port fragment..... | 10 | +| 6.1.2 Support fragment ..... | 10 | +| 6.1.3 Test fragment..... | 10 | +| 6.2 Name bindings ..... | 19 | +| 6.2.1 Test fragment..... | 19 | +| 6.3 Definition of packages ..... | 22 | +| 6.3.1 Metallic Test Access Line Package ..... | 22 | +| 6.3.2 Test environment conditions package ..... | 22 | +| 6.3.3 Voice access package..... | 22 | +| 6.4 Definition of attributes..... | 23 | +| 6.4.1 AC voltage threshold ..... | 23 | +| 6.4.2 Access network ringback service treatment ID ..... | 23 | +| 6.4.3 Apply ringing current..... | 23 | +| 6.4.4 Apply tone ..... | 23 | +| 6.4.5 Capacitance threshold..... | 24 | +| 6.4.6 DC voltage threshold..... | 24 | + +| | Page | +|--------------------------------------------------------------|-------------| +| 6.4.7 Dial speed threshold ..... | 24 | +| 6.4.8 Electrical measurement test ..... | 24 | +| 6.4.9 ISDN quick test..... | 24 | +| 6.4.10 Iterations ..... | 24 | +| 6.4.11 Loopback channel..... | 25 | +| 6.4.12 Loopback duration ..... | 25 | +| 6.4.13 Loopback position ..... | 25 | +| 6.4.14 Metallic test access message..... | 25 | +| 6.4.15 Metallic test access timeout period..... | 26 | +| 6.4.16 Monitor and speak ..... | 26 | +| 6.4.17 Number of digits ..... | 26 | +| 6.4.18 Off hook simulation..... | 26 | +| 6.4.19 Proposed metallic test access..... | 27 | +| 6.4.20 Pulse no pulse ratio..... | 27 | +| 6.4.21 Request result type..... | 27 | +| 6.4.22 Resistance threshold ..... | 27 | +| 6.4.23 Ring ..... | 27 | +| 6.4.24 Ring back number..... | 28 | +| 6.4.25 Number of subscriber private meter (SPM) pulses..... | 28 | +| 6.4.26 Type of Line..... | 28 | +| 6.4.27 Wait time ..... | 28 | +| 6.4.28 Test threshold class identifier ..... | 28 | +| 6.5 Definition of actions ..... | 29 | +| 6.5.1 Loopback select ..... | 29 | +| 6.6 Definition of notifications..... | 29 | +| 6.6.1 Off hook..... | 29 | +| 6.6.2 On hook ..... | 29 | +| 6.6.3 Time out..... | 29 | +| 6.7 Definition of parameters ..... | 30 | +| 6.7.1 Access result ..... | 30 | +| 6.7.2 Dialed digit test result..... | 30 | +| 6.7.3 Dialed digit test uncontrolled request..... | 30 | +| 6.7.4 Dialed digit test uncontrolled result ..... | 30 | +| 6.7.5 Dial tone test result..... | 30 | +| 6.7.6 Dial tone test uncontrolled request ..... | 31 | +| 6.7.7 Dial tone test uncontrolled result..... | 31 | +| 6.7.8 Electrical measurement test result ..... | 31 | +| 6.7.9 Electrical measurement test uncontrolled request ..... | 31 | + +| | Page | +|-----------------------------------------------------------------------------------|-------------| +| 6.7.10 Electrical measurement test uncontrolled result ..... | 31 | +| 6.7.11 Generic test result ..... | 32 | +| 6.7.12 Invalid loopback request..... | 32 | +| 6.7.13 ISDN quick test uncontrolled request..... | 32 | +| 6.7.14 ISDN quick test uncontrolled result ..... | 32 | +| 6.7.15 Loopback test result..... | 32 | +| 6.7.16 Loop back test uncontrolled request ..... | 33 | +| 6.7.17 Loop back test uncontrolled result..... | 33 | +| 6.7.18 Number of metallic test accesses ..... | 33 | +| 6.7.19 Pattern test result ..... | 33 | +| 6.7.20 Ringing test uncontrolled request ..... | 33 | +| 6.7.21 SPM pulses test uncontrolled request..... | 34 | +| 6.7.22 Test to line circuit result ..... | 34 | +| 6.7.23 Test to line circuit uncontrolled request ..... | 34 | +| 6.7.24 Test to line circuit uncontrolled result ..... | 34 | +| 6.7.25 Voice access test result ..... | 34 | +| 6.7.26 ISDN quick test result..... | 35 | +| 6.8 ASN.1 defined types module ..... | 35 | +| 7 Protocol requirements ..... | 42 | +| Annex A – Requirements and specification of parameters for access port tests..... | 42 | +| A.1 General test requirements ..... | 42 | +| A.1.1 Scheduled testing..... | 43 | +| A.1.2 Test capability..... | 43 | +| A.2 Access port test requirements ..... | 43 | +| A.2.1 Access port test management functions..... | 43 | +| A.2.2 Test scheduling ..... | 43 | +| A.2.3 Test result management ..... | 44 | +| A.2.4 Test threshold management ..... | 44 | +| A.2.5 Test requirements description..... | 44 | +| Annex B – Test categories ..... | 49 | +| B.1 Electrical measurement tests..... | 49 | +| B.2 Dialled digit test..... | 50 | +| B.3 Dial tone test ..... | 51 | +| B.4 Subscriber private meter pulses test..... | 51 | +| B.5 Ringing test ..... | 52 | +| B.6 Test to line circuit ..... | 52 | + +| | Page | +|----------------------------------------------------------------------------------------------------------|-------------| +| B.7 ISDN loopback test ..... | 53 | +| B.8 ISDN quick test ..... | 54 | +| Annex C – Test termination ..... | 54 | +| C.1 Termination of uncontrolled tests ..... | 54 | +| C.2 Termination of controlled tests ..... | 55 | +| C.2.1 One-step test ..... | 55 | +| C.2.2 Test session ..... | 55 | +| C.2.3 Aborting tests ..... | 55 | +| C.2.4 Termination sequence ..... | 56 | +| Annex D – Test result notification ..... | 56 | +| Annex E – Additional requirements on the test action performer ..... | 57 | +| E.1 Indication of supported tests ..... | 57 | +| E.2 Indication of unsuccessful test requests ..... | 57 | +| Annex F – Requirements and specification of parameters for V5 interface tests ..... | 57 | +| F.1 V5 interface test requirements ..... | 57 | +| F.1.1 V5 interface ID testing ..... | 57 | +| F.1.2 Link ID testing ..... | 57 | +| F.1.3 Provisioning variant testing ..... | 57 | +| Appendix I – Message flows ..... | 58 | +| Appendix II – Description of test procedures – Application for V5 access networks ..... | 60 | +| II.1 Background ..... | 60 | +| II.2 Test procedures scenario ..... | 60 | +| II.2.1 Scenario for faultsman ringback tests in an AN environment ..... | 61 | +| II.2.2 Scenario for a subscriber-assisted test in an AN environment ..... | 62 | +| Appendix III – State management in relation with line testing – Application for V5 access networks ..... | 64 | +| III.1 Intrusive tests ..... | 64 | +| III.2 Dealing with conflicts between intrusive tests and normal service ..... | 64 | +| III.3 State values during intrusive testing ..... | 65 | +| III.4 V5 blocking mechanism ..... | 65 | +| Appendix IV – Bibliography ..... | 66 | + +# Introduction + +Line and circuit testing of analogue customer accesses and ISDN customer accesses is part of a management activity which is performed by the operator in order to detect failure conditions and to bring the customer access back to its normal state of operation whenever a deviation occurs. + +A customer access is considered as being that part of the local network which extends from the network termination equipment up to and including the exchange termination. + +Here, only these parts of the activity are covered which are related directly to that part of the customer access which extends from the local exchange to the network termination equipment. An ISDN access extends to but does not include the T reference point. An analogue access extends to and may include the customer premises equipment (CPE) (see Figure 0). + +In Figure 0 both customer access scenarios are illustrated: + +- Direct access case for PSTN and ISDN customer to a local exchange (LE), which is shown in the top of Figure 0; +- Remote access case for PSTN and ISDN customer as well as for leased lines (semi-permanent lines) via an access network (AN) and across the V5.1 and/or V5.2 interface (as specified in Recommendations I.414, G.964 and G.965), shown in the bottom part of Figure 0. + +The shaded areas are subject to line and circuit testing and the associated management as presented within this Recommendation is based on the specifications within Recommendation Q.831. + +![Figure 0/Q.835 – Direct and remote customer access case scenarios. The diagram illustrates two scenarios: direct access and remote access. In the direct access scenario (top), a PSTN TE connects via a Z interface to a PSTN UP at a Local Exchange (LE). An ISDN TE connects via a T interface through an NT1 to an ISDN UP at the same LE. A shaded area covers the TE, NT1, and the interfaces. In the remote access scenario (bottom), a PSTN TE connects via a Z interface to a PSTN UP at an Access Network (AN). An ISDN TE connects via a T interface through an NT1 to an ISDN UP at the AN. A TE connects to an LL UP at the AN. A shaded area covers the TE, NT1, and the interfaces. The AN connects via a V5 interface (V5 TP) to a V5 TP at the Local Exchange (LE). A shaded area covers the AN and the V5 interface. The LE contains the PSTN UP, ISDN UP, and V5 TP. A shaded area covers the AN, the V5 interface, and the LE. The diagram is labeled T0409860-98.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Figure 0/Q.835 – Direct and remote customer access case scenarios. The diagram illustrates two scenarios: direct access and remote access. In the direct access scenario (top), a PSTN TE connects via a Z interface to a PSTN UP at a Local Exchange (LE). An ISDN TE connects via a T interface through an NT1 to an ISDN UP at the same LE. A shaded area covers the TE, NT1, and the interfaces. In the remote access scenario (bottom), a PSTN TE connects via a Z interface to a PSTN UP at an Access Network (AN). An ISDN TE connects via a T interface through an NT1 to an ISDN UP at the AN. A TE connects to an LL UP at the AN. A shaded area covers the TE, NT1, and the interfaces. The AN connects via a V5 interface (V5 TP) to a V5 TP at the Local Exchange (LE). A shaded area covers the AN and the V5 interface. The LE contains the PSTN UP, ISDN UP, and V5 TP. A shaded area covers the AN, the V5 interface, and the LE. The diagram is labeled T0409860-98. + +NOTE – Shaded areas are subject to line and circuit testing. User ports (UP) represent the different configurations for line circuit, line termination, exchange termination and network termination (NT). The option of ISDN access without remote NT1 is valid for ISDN BA only. + +**Figure 0/Q.835 – Direct and remote customer access case scenarios** + + + +## Recommendation Q.835 + +# LINE AND LINE CIRCUIT TEST MANAGEMENT OF ISDN AND ANALOGUE CUSTOMER ACCESSES + +(Geneva, 1999) + +# 1 Scope + +This Recommendation specifies the Q3 interface between a network element for customer access (i.e. local exchange, access network) and the Telecommunications Management Network (TMN) for the support of line and line circuit test functions and the associated management for ISDN and analogue customer accesses which are connected either directly to a local exchange or remotely at an access network and across V5.1 and/or V5.2 interfaces to a local exchange. + +It is not mandatory to implement the test and measurements specified in this Recommendation for all types of customer access realisations. However, if any test is implemented and is required to be managed via the Q3 interface on the network element, it shall be modelled as described in this Recommendation. + +The focus of this Recommendation is on defining an object model based on Recommendation X.745 [22]. Existing protocols are used where possible. The definition of Operations System (OS) functionality is outside the scope of this Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation G.964 (1994), *V-Interfaces at the digital local exchange (LE) – V5.1-interface (based on 2048 kbit/s) for the support of access network (AN)*. +- [2] ITU-T Recommendation G.965 (1995), *V-Interfaces at the digital local exchange (LE) – V5.2 Interface (based on 2048 kbit/s) for the support of access network (AN)*. +- [3] ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network*. +- [4] ITU-T Recommendation M.3100 (1995), *Generic network information model*. +- [5] CCITT Recommendation M.3603 (1992), *Application of maintenance principles to ISDN basic rate access*. +- [6] CCITT Recommendation M.3604 (1992), *Application of maintenance principles to ISDN primary rate access*. +- [7] ITU-T Recommendation Q.543 (1993), *Digital exchange performance design objectives*. +- [8] ITU-T Recommendation Q.811 (1997), *Lower layer protocol profiles for the Q3 and X interfaces*. + +- [9] ITU-T Recommendation Q.812 (1997), *Upper layer protocol profiles for the Q3 and X interfaces.* +- [10] ITU-T Recommendation Q.824.0 (1995), *Stage 2 and stage 3 description for the Q3 interface – Customer administration – Common information.* +- [11] ITU-T Recommendation Q.824.5 (1997), *Stage 2 and stage 3 description for the Q3 interface – Configuration management of V5 interface environments and associated customer profiles.* +- [12] ITU-T Recommendation Q.831 (1997), *Fault and performance management of V5 interface environments and associated customer profiles.* +- [13] CCITT Recommendation X.208 (1988), *Specification of Abstract Syntax Notation One (ASN.1).* +- [14] CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, *Information technology – Open Systems Interconnection – Structure of management information: Management information model.* +- [15] CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- [16] CCITT Recommendation X.730 (1992) | ISO/IEC 10164-1:1993, *Information technology – Open Systems Interconnection – Systems Management: Object management function.* +- [17] CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2:1993, *Information technology – Open Systems Interconnection – Systems management: State management function.* +- [18] CCITT Recommendation X.732 (1992) | ISO/IEC 10164-3:1993, *Information technology – Open Systems Interconnection – Systems Management: Attributes for representing relationships.* +- [19] CCITT Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, *Information technology – Open Systems Interconnection – Systems Management: Event report management function.* +- [20] CCITT Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems Management: Log control function.* +- [21] ITU-T Recommendation X.737 (1995) | ISO/IEC 10164-14:1996, *Information technology – Open Systems Interconnection – Systems management: Confidence and diagnostic test categories.* +- [22] ITU-T Recommendation X.745 (1993) | ISO/IEC 10164-12:1994, *Information technology – Open Systems Interconnection – Systems Management: Test management function.* +- [23] ITU-T Recommendation X.746 (1995) | ISO/IEC 10164-15:1995, *Information technology – Open Systems interconnection – Systems management: Scheduling function.* +- [24] ITU-T Recommendation X.680 (1997) | ISO/IEC 8824-1:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation.* +- [25] ITU-T Recommendation X.681 (1997) | ISO/IEC 8824-2:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Information object specification.* +- [26] ITU-T Recommendation X.682 (1997) | ISO/IEC 8824-3:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Constraint specification.* + +- [27] ITU-T Recommendation X.683 (1997) | ISO/IEC 8824-4:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications*. + +# 3 Terms and definitions, abbreviations + +## 3.1 Definitions + +This Recommendation defines the following terms: + +- Access Network (AN): See Recommendation G.964 [1]. +- bearer channel: See Recommendation G.964 [1]. +- Bearer Channel Connection (BCC): See Recommendation G.965 [2]. +- cable pair identification tone: See A.2.5.1.10. +- capacitance measurement: See A.2.5.1.2. +- codec testing: See A.2.5.2.1.6. +- Communication Channel (C-Channel): See Recommendation G.964 [1]. +- communication path: See Recommendation G.964 [1]. +- control protocol: See Recommendation G.964 [1]. +- dial pulse test: See A.2.5.1.5. +- dial tone test: See A.2.5.2.2.1. +- digit reception: See A.2.5.2.1.7. +- dry loop: See A.2.5.1.11. +- DTMF dialling test: See A.2.5.1.6. +- envelope function address: See Recommendation G.964 [1]. +- feeding current: See A.2.5.2.1.2. +- feeding voltage: See A.2.5.2.1.1. +- foreign voltage or current: See A.2.5.1.1. +- insulation resistance measurement: See A.2.5.1.3. +- layer 3 address: See Recommendation G.964 [1]. +- leased lines: See Recommendation G.964 [1]. +- PSTN line testing: See A.2.5.1. +- line circuit testing: See A.2.5.2.1. +- Local Exchange (LE): See Recommendation G.964 [1]. +- loop and ring trip detection: See A.2.5.2.1.3. +- loop resistance measurement: See A.2.5.1.4. +- loopback 1 (line termination loopback): See A.2.5.3.2.1. +- loopback 2, 21 and 1A (NT1 loopbacks): See A.2.5.3.2.1. +- monitoring of the line: See A.2.5.1.9. +- Operation System (OS): See Recommendation M.3010 [3]. +- power feed: See A.2.5.3.3.1. +- private meter pulses: See A.2.5.2.1.5. +- protection protocol: See Recommendation G.965 [2]. + +- register recall button test: See A.2.5.1.12. +- subscriber private meter testing: See A.2.5.1.7. +- V5 interface: See Recommendation G.964 [1]. +- V5 interface messages: This term refers to all Function Elements (FEs) and other V5 protocol messages as defined in Recommendations G.964 [1] and G.965 [2] which are communicated via the V5 interface. +- V5 time slot: See Recommendation G.964 [1]. + +## 3.2 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|----------------------------------------| +| AN | Access Network | +| CMIP | Common Management Information Protocol | +| CPE | Customer Premises Equipment | +| LC | Line Circuit | +| LE | Local Exchange | +| LL | Leased Line | +| MORT | Managed Object Referring to Test | +| MTA | Metallic Test Access | +| NE | Network Element | +| OS | Operations System | +| REG | Regenerator | +| RDN | Relative Distinguished Name | +| SPM | Subscriber Private Meter | +| TMN | Telecommunication Management Network | +| TE | Terminal Equipment | +| TO | Test Object | +| TP | Termination Point | +| UP | User Port | + +# 4 Line and line circuit testing functions + +## 4.1 Description of the service + +Line and circuit testing is part of a management activity which is performed by the operator in order to detect failure conditions and to bring the customer access back to its normal state of operation whenever a deviation occurs. A customer access is considered as being that part of the local network which extends from the network termination equipment up to and including the exchange termination. + +In this clause, only the parts of the activities are covered which are directly related to that part of the customer access which extends from the exchange termination to the network termination equipment. An ISDN access extends to but does not include the T reference point. An analogue access extends to and may include the CPE. + +## **4.2 Components of service** + +- a) *Failure detection* +Observe or supervise the subscriber access and collect relevant data in order to detect failures or degradation. Perform continuous or periodic checks of the system functions. +- b) *Failure information* +Send alarms and event reports from the NE to TMN with failure information related to subscriber access. +- c) *Failure localization* +Receive failure information from NEs which may be generated by performing tests and measurements on subscriber access. Initiate additional fault localization procedures and receive information from these procedures. +- d) *Fault correction* +Replace faulty access port equipment with working replacements. +- e) *Verification* +Apply the appropriate tests and measurements to the replaced component before bringing it back to service. +- f) *Restoration* +Restore the component to service. + +## **4.3 Management function list** + +- a) *Request status* +TMN requests NE to send the current status information related to the access port. +- b) *Set service state* +TMN directs NE to place a access port in a specified service state, e.g. in service (available for use), standby (not for normal use), out of service (unavailable for use). +- c) *Alarm report* +NE notifies TMN of alarm information concerning access ports. +- d) *Set alarm conditions* +TMN directs NE to assign specific alarm parameters, modes and thresholds to alarms concerning access ports. +- e) *Start line or circuit test* +TMN directs NE to start an on-demand or a periodic test of the subscriber line or access port. +- f) *Stop line or circuit test* +TMN directs NE to stop an on-demand or a periodic test of the subscriber line or access port. +- g) *Set test conditions* +TMN directs NE to assign parameters, modes and thresholds to tests and measurements of the subscriber line or access port. + +- h) *Apply test signals* +TMN directs NE to send test signals to the terminating equipment or to the line circuit, e.g. ringing signals, dial pulses, meter pulses. +- i) *Remove test signals* +TMN directs NE to remove the test signal sent by the apply function. +- j) *Connect external test equipment* +TMN directs NE to connect the customer line or access port to an external test equipment. +- k) *Disconnect external test equipment* +TMN directs NE to disconnect the subscriber line or access port from a previously connected external test equipment. +- l) *Request test results* +TMN requests NE to report intermediate or final results from a test applied to a subscriber line or an access port. +- m) *Test result report* +NE sends the results of a test applied to a subscriber line or an access port to TMN. + +## 4.4 Description of management functions + +Management functions related to testing are defined in Recommendation X.745 [22]. No specific functions are defined in the context of line and circuit testing at the network element for customer access (i.e. local exchange, access network). + +# 5 Information model diagrams + +The entity relationship diagram is given in 5.1 and the inheritance hierarchy ("is-a" relationships) and naming hierarchy (containment relationships) are given in 5.2 and 5.3, respectively. + +The conventions given in Figure 1 are used in the entity relationship diagrams. + +![Figure 1/Q.835: Conventions used in diagrams for entity relationship diagrams. The figure shows four symbols: a diamond with 'a' and a single arrow, a diamond with 'a' and two opposite arrows, a diamond with 'i' and a single arrow, and a diamond with 'c' and a single arrow. Each symbol is followed by a text description: 'is associated with (unidirectional)', 'is associated with (reciprocal relation)', ' Diamond with 'a' and single arrow Diamond with 'a' and two opposite arrows Diamond with 'i' and single arrow Diamond with 'c' and single arrow](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +is associated with (unidirectional) + is associated with (reciprocal relation) + "is-a" relation (inheritance) + is contained in + +T0409870-98 + +Figure 1/Q.835: Conventions used in diagrams for entity relationship diagrams. The figure shows four symbols: a diamond with 'a' and a single arrow, a diamond with 'a' and two opposite arrows, a diamond with 'i' and a single arrow, and a diamond with 'c' and a single arrow. Each symbol is followed by a text description: 'is associated with (unidirectional)', 'is associated with (reciprocal relation)', ' Diamond with 'a' and single arrow Diamond with 'a' and two opposite arrows Diamond with 'i' and single arrow Diamond with 'c' and single arrow + +**Figure 1/Q.835 – Conventions used in diagrams for entity relationship diagrams** + +## 5.1 Entity relationship diagram + +Figure 2 shows the various entities related to line and circuit testing at the network element for customer access (i.e. local exchange, access network). They extend the information model described in Recommendations Q.824.0 [10] and Q.824.5 [11], which specifies management information describing the various user port aspects. + +![Entity relationship diagram for the test fragment. The diagram shows a hierarchy of entities. At the top is 'managedElement'. It connects to 'testThreshold-Class', 'testAction Performer', and 'anRbs Treatment (Note)'. 'testAction Performer' connects to 'loopTest', 'metallicTest Access', and 'accessTest'. 'loopTest' connects to 'accessPort' (with cardinalities 1, N, a) and 'electrical Measurement Test'. 'metallicTest Access' connects to 'dialledDigit-Test'. 'accessTest' connects to 'spmPulses', 'ringing', 'voiceAccess-Test', and 'isdnQuickTest'. 'voiceAccess-Test' connects to 'dryLoop'. 'electrical Measurement Test' connects to 'patternTest'. 'dialledDigit-Test' connects to 'dialledDigit-Test'. 'spmPulses' connects to 'testToLineTest'. 'ringing' connects to 'cablePairIdTone'. 'voiceAccess-Test' connects to 'dryLoop'. 'isdnQuickTest' connects to 'isdnQuickTest'. The diagram also shows 'accessPort' connected to 'loopTest' and 'accessTest' with cardinalities 1, M, a. The diagram is labeled 'test fragment' and 'T0409880-98'.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +Entity relationship diagram for the test fragment. The diagram shows a hierarchy of entities. At the top is 'managedElement'. It connects to 'testThreshold-Class', 'testAction Performer', and 'anRbs Treatment (Note)'. 'testAction Performer' connects to 'loopTest', 'metallicTest Access', and 'accessTest'. 'loopTest' connects to 'accessPort' (with cardinalities 1, N, a) and 'electrical Measurement Test'. 'metallicTest Access' connects to 'dialledDigit-Test'. 'accessTest' connects to 'spmPulses', 'ringing', 'voiceAccess-Test', and 'isdnQuickTest'. 'voiceAccess-Test' connects to 'dryLoop'. 'electrical Measurement Test' connects to 'patternTest'. 'dialledDigit-Test' connects to 'dialledDigit-Test'. 'spmPulses' connects to 'testToLineTest'. 'ringing' connects to 'cablePairIdTone'. 'voiceAccess-Test' connects to 'dryLoop'. 'isdnQuickTest' connects to 'isdnQuickTest'. The diagram also shows 'accessPort' connected to 'loopTest' and 'accessTest' with cardinalities 1, M, a. The diagram is labeled 'test fragment' and 'T0409880-98'. + +NOTE – Only for customers connected remotely via an access network (AN) and V5 interface to the local exchange (LE). + +**Figure 2/Q.835 – Entity relationship diagram – test fragment** + +### 5.1.1 Line testing and line circuit testing + +Test requests from the OS are sent as Common Management Information Protocol (CMIP) testRequestControlled or testRequestUncontrolled action to an instance of testActionPerformer. In this model, all controlled tests are delegated by instances of testActionPerformer to instances of subclasses of testObject, i.e. when receiving a test request the testActionPerformer automatically creates the required instances of these classes. Further instances of subclasses of testObject are created if further delegation of the performance of the test is required. This creation is achieved by sending additional testRequestControlled actions; the testSessionId parameter is used to identify in which access test instance the new tests should be contained. All instances of these subclasses of testObject exist only for the duration of their delegated operations. Details of the mechanism how to transmit test requests to testActionPerformer and how test results are generated are described in Recommendation X.745 [22]. + +Management information related to uncontrolled tests can be found in Annex B. + +Controlled testing is initially delegated to an instance of `accessTest` or to an instance of `loopTest` or to an instance of `metallicTestAccess`. Each instance of `loopTest` or `accessTest` or `metallicTestAccess` is contained in an instance of `testActionPerformer`. + +The object class `loopTest` is used to set up loopbacks for the user port to which it is associated by an attribute. If patterns are to be injected and compared within the NE as part of the loopback test, then this is delegated to an instance of `patternTest` which is contained in the delegating instance of `loopTest`. + +The object class `accessTest` has all specific non-loopback tests allocated to it. It has an attribute which specifies one or a list of user ports which are to be tested. + +If external test systems are used for line testing, the `metallicTestAccess` allows to connect it to each subscriber line (outbound or bridged) and to each line circuit (inbound) of the NE. The implementation of the metallic test access is outside the scope of this Recommendation. + +The creation of an instance of `accessTest` represents a test session and permits test access to lines or line circuits during which a number of different tests can be performed. These delegated tests are handled by specific contained test objects. Each contained test object triggers the specific test on one or more user ports which are specified in `accessTest`. + +Electrical measurements, such as voltage, capacitance and resistance, are delegated to instances of `electricalMeasurementTest`. Dialed digit tests, dial tone tests and other tests (in particular those involving sending meter pulses to the line, cable pair identification tone and ringing) are triggered by the creation of instances of `dialedDigitTest`, `dialToneTest`, `spmPulses`, `cablePairIdTone` and `ringing`, respectively. The dry loop condition is set up by instances of `dryLoopTest`. The inward line circuit tests are delegated to instances of `testToLineCircuit`. The `voiceAccessTest` allows for the provision of those tests which involve the establishment of a voice connection with the line under test. A quick check of an ISDN access is represented by an `isdnQuickTest` object. + +The object class `testThresholdClass` can be used to modify predefined test thresholds via the Q3 interface. + +### **5.1.2 The testResultNotifications of the tests** + +The sending time, the information contents and the number of `testResultNotifications` sent per test request are not restricted. It is a matter up to the NE implementation. If the `testResultNotification` contains results whose testing time has importance, they shall be ordered in the ASN.1 sequence oldest first. + +## **5.2 Inheritance hierarchy** + +Figure 3 traces the inheritance from the highest level object "ITU-T Recommendation X.721":top to the managed objects defined in this Recommendation. + +![Inheritance hierarchy diagram for Figure 3/Q.835. The hierarchy starts with 'X.721': top, which branches into 'X.745': testActionPerformer, 'X.745': testObject, and testThresholdClass. 'X.745': testActionPerformer further branches into isdnQuickTest, loopTest, patternTest, accessTest, electricalMeasurementTest, dialledDigitTest, and dialToneTest. 'X.745': testObject branches into metallicTestAccess, spmPulses, cablePairIdTone, ringing, testToLineCircuit, dryLoop, and voiceAccessTest. 'X.721': top also branches into treatment (Note 2), which then branches into anRbsTreatment (Note 2).](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + X721["X.721': top"] --- X745_AP["X.745': testActionPerformer"] + X721 --- X745_TO["X.745': testObject"] + X721 --- testThresholdClass + X745_AP --- isdnQuickTest + X745_AP --- loopTest + X745_AP --- patternTest + X745_AP --- accessTest + X745_AP --- electricalMeasurementTest + X745_AP --- dialledDigitTest + X745_AP --- dialToneTest + X745_TO --- metallicTestAccess + X745_TO --- spmPulses + X745_TO --- cablePairIdTone + X745_TO --- ringing + X745_TO --- testToLineCircuit + X745_TO --- dryLoop + X745_TO --- voiceAccessTest + X721 --- treatment["treatment (Note 2)"] + treatment --- anRbsTreatment["anRbsTreatment (Note 2)"] + +``` + +Inheritance hierarchy diagram for Figure 3/Q.835. The hierarchy starts with 'X.721': top, which branches into 'X.745': testActionPerformer, 'X.745': testObject, and testThresholdClass. 'X.745': testActionPerformer further branches into isdnQuickTest, loopTest, patternTest, accessTest, electricalMeasurementTest, dialledDigitTest, and dialToneTest. 'X.745': testObject branches into metallicTestAccess, spmPulses, cablePairIdTone, ringing, testToLineCircuit, dryLoop, and voiceAccessTest. 'X.721': top also branches into treatment (Note 2), which then branches into anRbsTreatment (Note 2). + +NOTE 1 – Only classes which are underlined may be instantiated. + +NOTE 2 – Only for customers connected remotely via an access network (AN) and V5 interface to the local exchange (LE). + +**Figure 3/Q.835 – Inheritance hierarchy** + +## 5.3 Naming hierarchy + +Figure 4 shows the naming (i.e. containment) relationships for the NE's managed objects associated with line and circuit testing. + +![Naming hierarchy diagram for Figure 4/Q.835. The hierarchy starts with 'M.3100': managedElement, which branches into anRbsTreatment (Note), 'X.745': testActionPerformer, and testThresholdClass. 'X.745': testActionPerformer branches into loopTest, accessTest, and metallicTestAccess. loopTest branches into patternTest. accessTest branches into dialToneTest, spmPulses, ringing, dryLoop, and isdnQuickTest. dialToneTest branches into electricalTest-Measurement. spmPulses branches into dialledDigit-Test. ringing branches into testToLine-Circuit. dryLoop branches into cablePairId-Tone. isdnQuickTest branches into voiceAccessTest.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +graph TD + M3100["M.3100': managedElement"] --- anRbsTreatment["anRbsTreatment (Note)"] + M3100 --- X745_AP["X.745': testActionPerformer"] + M3100 --- testThresholdClass + X745_AP --- loopTest + X745_AP --- accessTest + X745_AP --- metallicTestAccess + loopTest --- patternTest + accessTest --- dialToneTest + accessTest --- spmPulses + accessTest --- ringing + accessTest --- dryLoop + accessTest --- isdnQuickTest + dialToneTest --- electricalTestMeasurement["electricalTest-Measurement"] + spmPulses --- dialledDigitTest["dialledDigit-Test"] + ringing --- testToLineCircuit["testToLine-Circuit"] + dryLoop --- cablePairIdTone["cablePairId-Tone"] + isdnQuickTest --- voiceAccessTest + +``` + +Naming hierarchy diagram for Figure 4/Q.835. The hierarchy starts with 'M.3100': managedElement, which branches into anRbsTreatment (Note), 'X.745': testActionPerformer, and testThresholdClass. 'X.745': testActionPerformer branches into loopTest, accessTest, and metallicTestAccess. loopTest branches into patternTest. accessTest branches into dialToneTest, spmPulses, ringing, dryLoop, and isdnQuickTest. dialToneTest branches into electricalTest-Measurement. spmPulses branches into dialledDigit-Test. ringing branches into testToLine-Circuit. dryLoop branches into cablePairId-Tone. isdnQuickTest branches into voiceAccessTest. + +NOTE – Only for customers connected remotely via an access network (AN) and V5 interface to the local exchange (LE). + +**Figure 4/Q.835 – Naming hierarchy** + +# **6 Formal object class definitions** + +This clause gives the formal definitions of the managed object classes, name bindings, general packages, behaviours, attributes, actions and notifications. + +## **6.1 Definitions of object classes** + +This subclause specifies the object classes for all of the managed objects used in the management information model. These object classes are either defined here or by reference to other specifications. Classes of managed objects which are defined elsewhere and which are only used for containment are not included, but are identified by the name bindings for the classes specified here. + +### **6.1.1 Access port fragment** + +#### **6.1.1.1 Access port fragment at the local exchange** + +In this fragment, the following object classes are used. They are used in the test operations to identify the MORTs. They are defined in Recommendation Q.824.0 [10]: + +- analogueAccess; +- "ITU-T Recommendation Q.824.1":accessPortISDNBasicRate; +- "ITU-T Recommendation Q.824.1":accessPortISDNPrimaryRate. + +#### **6.1.1.2 Access port fragment at the access network** + +In this fragment, the following object classes are used. They are used in the test operations to identify the MORTs. They are defined in Recommendation Q.824.5 [11]: + +- "ITU-T Recommendation Q.824.5":pstnUserPort; +- "ITU-T Recommendation Q.824.5":isdnBAUserPort; +- "ITU-T Recommendation Q.824.5":isdnPRAUserPort; +- "ITU-T Recommendation Q.824.5":leasedPort; +- "ITU-T Recommendation Q.824.5":userPortBearerChannelCtp. + +### **6.1.2 Support fragment** + +The following classes which are defined in Recommendation X.721 [15] may be instantiated: + +- "ITU-T Recommendation X.721:1992":attributeValueChangeRecord; +- "ITU-T Recommendation X.721:1992":eventForwardingDiscriminator; +- "ITU-T Recommendation X.721:1992":log. + +The following classes which are defined in Recommendation X.745 [22] may be instantiated. + +- "ITU-T Recommendation X.745:1993":schedulingConflictRecord; +- "ITU-T Recommendation X.745:1993":testActionPerformer; +- "ITU-T Recommendation X.745:1993":testResultsRecord. + +### **6.1.3 Test fragment** + +The following classes which are required for the testing of lines and line circuits are defined in the following subclauses. They may all be instantiated. + +#### 6.1.3.1 Access test + +accessTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +testEnvironmentConditionsPackage, + +"ITU-T Recommendation X.745": mORTsPackage, + +accessTestPkg **PACKAGE** + +**BEHAVIOUR** + +accessTestPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "The MORTs which are subject to test are listed in the mORTs attribute. + +The creation of an instance of this object class represents a test session and permits test access to lines or line circuits during which a number of different tests can be performed. These tests are executed by instances of specific test object classes contained in the accessTest object, which acts for them as a common framework in terms of state handling (dependent on the performed tests) and test mechanism reservation (implementation specific). + +If this object class is instantiated with a contained voiceAccessTest object instance, the mORTs attribute shall contain only one user port. + +If an instance of this object class contains instances of specific test object classes, the line access conditions are those implicitly specified by the individual test objects. The procedure for the sequential or parallel performance of the tests specified by the contained objects on the user port(s) listed in their mORTs, attributes is up to the implementation. + +The testEnvironmentConditionsPackage is used to control any possible interference between tests ordered by the manager and all other activities taking place in the NE. + +In case of multiple MORTs testing, the additionalInformation field of the test result notification shall contain the results for each MORT under test. In the case that at least one test of a MORT fails to seize sufficient test resources, the testOutcome field of test result notification shall contain the value 'fail'. The test result notification shall only be sent for the MORTs for which there was a failure to set up an adequate test environment. + +The NE may perform, at any time during the lifespan of the accessTest object, a check for the presence of a dangerous voltage. If this condition is detected, then this is reported in the test result of the accessTest and the affected test is terminated (in the case of multiple MORTs testing, the effective MORT is skipped)."; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification accessResult;; + +**REGISTERED AS** {q835ManagedObjectClass 1}; + +#### 6.1.3.2 Cable pair identification tone + +cablePairIdTone **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +cablePairIdTonePkg **PACKAGE** + +**BEHAVIOUR** + +cablePairIdTonePkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT(s) to which the test is to be applied. + +This test shall be performed in the following way: a tone shall be sent out on a 2-wire pair to assist in identifying cable pairs in the field.";; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification genericTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 2}; + +#### 6.1.3.3   Dialled digit test + +dialledDigitTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +dialledDigitTestPkg **PACKAGE** + +**BEHAVIOUR** + +dialledDigitTestPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT to which the test is to be applied. + +DTMF tone (if possible) or pulses received are decoded and results reported after the specified number of digits have been received. This value is stored in the numberOfDigits attribute (default 1 digit). + +The wrongSignal value of the NotDigit data type result may be generated by the NE if a signal has been detected of similar nature as the expected one, but out of the range for any of its aspects, e.g., invalid duration (loop break or DTMF tones), invalid level and/or frequency (DTMF) or one-tone-missing (DTMF). If an implementation generates this result, it shall be well specified under which conditions it is done.";; + +**ATTRIBUTES** + +numberOfDigits **DEFAULT VALUE** + +ASN1LLCTTypeModule.defaultNumberOfDigits                   GET-REPLACE, + +requestedResultType **DEFAULT VALUE** + +ASN1LLCTTypeModule.defaultRequestedResultType           GET-REPLACE; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification dialledDigitTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 3}; + +#### 6.1.3.4   Dial tone test + +dialToneTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +dialToneTestPkg **PACKAGE** + +**BEHAVIOUR** + +dialToneTestPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT(s) to which the test is to be applied. + +An off-hook is simulated by the NE according to the offHookSimulation attribute and the time is measured until the dial tone appears on the line circuit termination. This time is compared with a predefined threshold. If a number of iterations are specified, then the results are returned in a single test result notification. + +In case of multiple MORTs testing, the additionalInformation field of the test result notification shall contain the results for each MORT under test. When all MORTs passed the tests, the testOutcome field of the test result notification shall contain the value 'pass'. In case at least one MORT test fails, the testOutcome field of the test result notification shall contain the value 'fail'. + +The requestedResultType is used to control the test result notification. Its three Boolean parameters define whether the MORTs which passed and/or those which failed and/or the measured values are to be reported.";; + +**ATTRIBUTES** + +offHookSimulation **GET**, + +requestedResultType **DEFAULT VALUE** + +ASN1LLCTTypeModule.defaultRequestedResultType           GET-REPLACE, + +iterations **DEFAULT VALUE** ASN1LLCTTypeModule.defaultIterations; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification dialToneTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 4}; + +#### 6.1.3.5 Dry loop + +dryLoop **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +dryLoopPkg **PACKAGE** + +**BEHAVIOUR** + +dryLoopPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT(s) to which the test is to be applied. + +When an object is instantiated, the lines related to the user ports listed in the MORTs attribute are disconnected from the corresponding line circuit. + +The result of the attempt to switch the requested dry loop(s) may be reported immediately or after the appropriate wait time as given in the test request. + +A dry loop is terminated by time-out, by deleting the dryLoop object or by terminating the function with a testTerminate action.";; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification genericTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 5}; + +#### 6.1.3.6 Electrical measurement test + +electricalMeasurementTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +electricalMeasurementTestPkg **PACKAGE** + +**BEHAVIOUR** + +electricalMeasurementTestPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT(s) to which the test is to be applied. + +The electricalMeasurementTestToBePerformed attribute defines which electrical measurements are to be performed, what results are required and (optionally) thresholds that override predefined NE thresholds to be used only during this test. + +The appropriate testOutcome shall be set to 'pass' only if all performed tests were successful. If requested, measured values will be returned in the electricalMeasurementTestResult parameter carried in the test result notification. If a requested measurement could not be executed by the NE because it is not supported, the NE shall omit the related optional elements within the electricalMeasurementTestResult. + +In case of multiple MORTs testing, the additionalInformation field of the test result notification shall contain the results for each MORT under test. When all MORTs passed the tests, the testOutcome field of the test result notification shall contain the value 'pass'. In case at least one MORT test fails, the testOutcome field of the test result notification shall contain the value 'fail'. + +The requestedResultType is used to control the test result notification. Its three Boolean parameters define whether the MORTs which passed and/or those which failed and/or the measured values are to be reported.";; + +**ATTRIBUTES** + +electricalMeasurementTestToBePerformed **DEFAULT VALUE** + +ASN1LLCTTypeModule.defaultElectricalMeasurementTestToBePerformed GET-REPLACE, + +requestedResultType **DEFAULT VALUE** + +ASN1LLCTTypeModule.defaultRequestedResultType GET-REPLACE; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification electricalMeasurementTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 6}; + +#### 6.1.3.7 ISDN quick test + +isdnQuickTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +"ITU-T Recommendation X.745":mORTsPackage, + +isdnQuickTestPkg **PACKAGE** + +**BEHAVIOUR** + +isdnQuickTestPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "The ISDN quick test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745 for the MORT(s) to which the test is to be applied. + +The isdnQuickTestToBePerformed attribute defines which quick tests are to be performed. + +The appropriate testOutcome shall be set to 'pass' only if all test steps performed by the quick test were successful. If requested, detailed error reasons will be returned in the isdnQuickTestResult parameter carried in the test result notification. If a requested isdnQuickTest could not be executed by the NE because it is not supported, the NE shall generate the appropriate specific error indicating the not supported test. + +In case of multiple MORTs testing the additionalInformation field of the test result notification shall contain the results for each MORT under test. When all MORTs passed the tests, the testOutcome field of the test result notification contains the value 'pass'. In case at least one MORT test fails, the testOutcome field of the test result notification shall contain the value 'fail'. + +The requestedResultType is used to control the test result notification. Its three Boolean parameters define whether the MORTs which passed and/or those which failed and/or the measured values are to be reported.";; + +**ATTRIBUTES** + +isdnQuickTestToBePerformed **DEFAULT VALUE** + +ASN1LLCTTypeModule.defaultIsdnQuickTestToBePerformed GET-REPLACE, + +requestedResultType **DEFAULT VALUE** + +ASN1LLCTTypeModule.defaultRequestedResultType GET-REPLACE; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745":testResultNotification isdnQuickTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 7}; + +#### 6.1.3.8 Loop test + +loopTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +testEnvironmentConditionsPackage, + +"ITU-T Recommendation X.745": mORTsPackage, + +loopTestPkg **PACKAGE** + +**BEHAVIOUR** + +loopTestPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "Instances of this object class represent loopbacks which are used for testing. + +When an instance of this object class is applied to a set of user ports which are represented by objects, then the inherited mORTs attribute consists of a set of object identifiers which indicates the ports to which loopback are to be applied. Patterns are transmitted towards the user, then looped back towards the port for each indicated port. + +Further details about the generation and comparison of patterns may be modeled using one or more objects which are contained in this loopTest object instance. If there are no such contained objects, then pattern generation and detection may be performed remotely or implicitly performed locally. + +The loopbackDuration attribute indicates for how long a loopback is to be applied. It shall have a finite value to ensure that the loopback will be eventually removed, and any request which would result in a loopback being applied infinitely shall be rejected. The loopback shall be removed before the instance of this class is deleted. + +The loopbackPosition attribute indicates the position where loopback is to be applied. Loopbacks in different positions may be used in the testing of a single object. The loopbackPosition attribute indicates both the position and the direction of the loopback. + +The loopbackChannel attribute indicates the nature of the loopback, in particular the channels or connections which are looped back at the loopback position. + +The loopbackSelect action may be used to select new durations, positions and types for further loopback testing, without deleting the instance of this object class. + +If an invalid loopback is requested, then the request shall be rejected with an invalidLoopbackRequest parameter. If the test is terminated before completion of the specified duration, then the loopback shall be removed before the result is returned and the instance deleted. If the loopback is successful, then the loopbackResult parameter shall be returned in the testResult notification. + +The testEnvironmentalConditionsPackage package is used to control any possible interference between tests ordered by the manager and all other activities taking place in the NE.";; + +##### **ATTRIBUTES** + +loopbackDuration DEFAULT VALUE ASN1LLCTTypeModule.defaultLoopBackDuration GET, + +loopbackPosition DEFAULT VALUE ASN1LLCTTypeModule.defaultLoopBackPosition GET, + +loopbackChannel DEFAULT VALUE ASN1LLCTTypeModule.defaultLoopBackChannel GET; + +##### **ACTIONS** + +loopbackSelect; + +##### **NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification loopbackTestResult;;; + +**REGISTERED AS** {q835ManagedObjectClass 8}; + +#### **6.1.3.9 Metallic test access** + +metallicTestAccess **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +"ITU-T Recommendation X.745":mORTsPackage, + +metallicTestAccessPkg **PACKAGE** + +##### **BEHAVIOUR** + +metallicTestAccessPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "The test establishes a physical connection between an instance of MORT and a measurement interface of an external test system. + +The OS identifies the measurement interface in parameter numberOfMTA, which is included in the information syntax of testRequestControlledAction. + +In case the measurement interface is not available for any reason, the NE automatically tries to connect the MORT to an alternative measurement interface. In both cases, the attribute proposedMTA indicates the measurement interface where the MORT is physically connected to. + +The attribute mtaMsg contains the return value of a successful connection. + +The connection will be released after the time defined by attribute mtaTimeoutPeriod. In this case, all test-related resources are released, the instance of metallicTestAccess is implicitly deleted, and an objectDeletionNotification is generated. Setting the attribute mtaTimeoutPeriod extends the connection time by the indicated value.";; + +##### **ATTRIBUTES** + +mtaTimeoutPeriod DEFAULT VALUE + +ASN1LLCTTypeModule.defaultMtaTimeoutPeriod GET-REPLACE, + +mtaMsg GET, + +proposedMTA GET; + +##### **NOTIFICATIONS** + +"ITU-T Recommendation X.721":objectDeletion;;; + +##### **CONDITIONAL PACKAGES** + +testEnvironmentConditionsPackage **PRESENT IF** "an instance supports it", + +mtaLinePackage **PRESENT IF** "the metallic test access is a two-wire interface."; + +**REGISTERED AS** {q835ManagedObjectClass 9}; + +#### **6.1.3.10 Pattern test** + +patternTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +patternTestPkg **PACKAGE** + +##### **BEHAVIOUR** + +patternTestPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "A Pattern Test is an object class which represents the generation and matching of bit patterns which may be used in association with loopback testing. The mORTs attribute consists of a set of two objects identifiers. The first of these defines how pattern generation is applied, and the second defines how pattern matching is applied. Patterns are injected at the object identified by the first identifier unless it is null, in which case pattern generation shall be disabled. Patterns received from the object identified by the second identifier are used for comparison unless this identifier is null, in which case pattern matching shall be disabled. + +Possible ambiguities about the signal paths by which injected signals leave or arrive at the objects identified in the mORTs attribute is normally resolved in the object which contains the instance of this object. If ambiguities remain, they may be clarified in an object contained in this object.";; + +##### **ATTRIBUTES** + +"ITU-T Recommendation X.737": testPattern GET-REPLACE, +requestedResultType DEFAULT VALUE + +ASN1LLCTTypeModule.defaultRequestedResultType GET-REPLACE, + +"ITU-T Recommendation X.737": errorRatioReportType GET; + +##### **NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification patternTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 10}; + +#### **6.1.3.11 Ringing** + +ringing **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +ringingPkg **PACKAGE** + +##### **BEHAVIOUR** + +ringingPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT(s) to which the test is to be applied. + +An instance of this object class represent the application of a ringing current to the line. The current shall be removed either on request or after a time-out. The testOutcome parameter of the testResult shall indicate 'pass' if the ringing was tripped. When a time-out occurs, it shall be indicated in the appropriate testOutcome parameter. + +The ring attribute indicates for how long ringing is to be applied.";; + +##### **ATTRIBUTES** + +ring DEFAULT VALUE ASN1LLCTTypeModule.defaultRing GET-REPLACE; + +##### **NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification genericTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 11}; + +#### **6.1.3.12 Subscriber private meter (SPM) pulses** + +spmPulses **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +spmPulsesPkg **PACKAGE** + +##### **BEHAVIOUR** + +spmPulsesPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT(s) to which the test is to be applied. + +This test shall be performed in the following way: apply the requested number of Subscriber Private Metering pulses (0-99) at the required frequency level to the line. After the pulses have been sent or after a time-out, the test result notification shall be emitted, with the testOutcome parameter set to 'inconclusive' or 'timed-out'. + +The spmPulsesNo indicates the number of pulses which shall be applied.";; + +##### **ATTRIBUTES** + +spmPulsesNo DEFAULT VALUE ASN1LLCTTypeModule.defaultSpmPulses GET-REPLACE; + +##### **NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification genericTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 12}; + +#### 6.1.3.13 Test to line circuit + +testToLineCircuit **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +testToLineCircuitPkg **PACKAGE** + +**BEHAVIOUR** + +testToLineCircuitPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This test is only performed given that the containing accessTest object instance exists and that it is in the testing state, as defined in ITU-T Recommendation X.745, for the MORT(s) to which the test is to be applied. + +This managed object class is instantiated whenever an OS requests an inward test on a specified user port or on a set of user ports. This consists of executing a set of specific circuit tests. + +The test result is based on a GO/NOGO method covering all circuit tests on a global way. If the NE supports the transfer of result values, these may be additionally provided in the test result notification. + +In case of multiple MORTs testing, the additionalInformation field of the test result notification shall contain the results for each MORT under test. When all tests on a MORT passed, the testOutcome field of the test result notification contains the value 'pass'. In case at least one test on a MORT fails, the testOutcome field of the test result notification shall contain the value 'fail'. If the testOutcome for a MORT is 'fail' and the NE is able to, it provides a list of the line circuit tests which have failed.";; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745": testResultNotification testToLineCircuitResult;; + +**REGISTERED AS** {q835ManagedObjectClass 13}; + +#### 6.1.3.14 Test Threshold Class + +testThresholdClass **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.721":top; + +**CHARACTERIZED BY** + +testThresholdClassPkg **PACKAGE** + +**BEHAVIOUR** + +testThresholdClassPkgBehaviour **BEHAVIOUR** + +**DEFINED AS** "When a passed/not passed result is requested, provisionable threshold values are used, unless the test request contains threshold values which override the provisioned thresholds. After the termination of that test, the provisioned thresholds will be restored. + +Provisionable thresholds are default thresholds for tests which can be modified via the Q3 interface. For each type of test it is possible to specify a number of different thresholds. Each of these thresholds may be assigned to a particular group of thresholds, so-called threshold classes. + +Access ports may be associated with one of these threshold classes, e.g. by using the supportedByObjectList attribute.";; + +**ATTRIBUTES** + +| | | +|------------------------------------------------|----------------| +| testThresholdClassId | GET, | +| capacitanceThreshold DEFAULT VALUE | | +| ASN1LLCTTypeModule.defaultCapacitanceThreshold | GET-REPLACE, | +| resistanceThreshold DEFAULT VALUE | | +| ASN1LLCTTypeModule.defaultResistanceThreshold | GET-REPLACE, | +| acVoltageThreshold DEFAULT VALUE | | +| ASN1LLCTTypeModule.defaultAcVoltageThreshold | GET-REPLACE, | +| dcVoltageThreshold DEFAULT VALUE | | +| ASN1LLCTTypeModule.defaultDcVoltageThreshold | GET-REPLACE, | +| dialSpeedThreshold DEFAULT VALUE | | +| ASN1LLCTTypeModule.defaultDialSpeedThreshold | GET-REPLACE, | +| pulseNoPulseRatio DEFAULT VALUE | | +| ASN1LLCTTypeModule.defaultPulseNoPulseRatio | GET-REPLACE;;; | + +**REGISTERED AS** {q835ManagedObjectClass 14}; + +#### 6.1.3.15 Voice access test + +voiceAccessTest **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.745": testObject; + +**CHARACTERIZED BY** + +voiceAccessPackage, + +voiceAccessTestPackage **PACKAGE** + +**BEHAVIOUR** + +voiceAccessTestBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class allows for the provision of a voice access test";; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.745":testResultNotification voiceAccessTestResult;; + +**REGISTERED AS** {q835ManagedObjectClass 15}; + +#### 6.1.3.16 Access network ringback service treatment + +anRbsTreatment **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Recommendation X.721": top; + +**CHARACTERIZED BY** + +anRbsTreatmentPackage **PACKAGE** + +**BEHAVIOUR** + +anRbsTreatmentBehaviour **BEHAVIOUR** + +**DEFINED AS** "The anRbsTreatment object class is a class of managed objects that represent the capability of an LE to support AN-based tests initiated from the subscriber premises by dialling special service codes (ringback service). Instances of this object class will be pointed at by instances of object classes representing the special service codes. In addition, instances of anRbsTreatment may be pointed at by instances of other object classes representing tones or announcements which are related to particular steps and results of the test procedure identified by the service code. + +Whenever one of those service codes is dialled, the call routing function in the LE selects an appropriate instance of this object class. This instance shall then emit the offHook notification. + +When a CPE under test goes on-hook, this shall be reported by means of the onHook notification. Test results produced in the LE, e.g. by DTMF measurements, may optionally be contained in the information syntax of this notification. + +When a user port address is added to the list contained in the applyRinginCurrent attribute, the ringing current shall be applied to the associated subscriber line. The feeding shall stop when the CPE goes off-hook or when a pre-defined timer in the LE expires. The user port address shall then be removed from the attribute. A time out shall be reported by means of the timeOut notification. + +When a user port address is added to the list contained in the applyTone attribute, a tone or announcement related to the test result as specified in the information syntax of the attribute shall be applied to the associated subscriber line in order to indicate the test result. The tone or announcement shall stop when the CPE goes on-hook or when a pre-defined timer in the LE expires or optionally when the next code is typed in at the CPE. The user port address and any related test result shall then be removed from the attribute. A time out shall be reported by means of the timeOut notification. The applyTone attribute may also be set by LE internal test procedures, e.g. DTMF measurements.";; + +**ATTRIBUTES** + +anRbsTreatmentId + +GET, + +applyTone + +GET-REPLACE ADD-REMOVE, + +applyRinginCurrent + +GET-REPLACE ADD-REMOVE; + +**NOTIFICATIONS** + +"ITU-T Recommendation X.721": objectCreation, + +"ITU-T Recommendation X.721": objectDeletion, + +offHook, + +onHook, + +timeOut;; + +**REGISTERED AS** {q835ManagedObjectClass 16}; + +## 6.2 Name bindings + +### 6.2.1 Test fragment + +#### 6.2.1.1 accessTest-testActionPerformer + +accessTest-testActionPerformer **NAME BINDING** +SUBORDINATE OBJECT CLASS accessTest AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS "ITU-T Recommendation X.745": testActionPerformer +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE DELETES-CONTAINED-OBJECTS; +**REGISTERED AS** {q835NameBinding 1}; + +#### 6.2.1.2 anRbsTreatment-managedElement + +anRbsTreatment-managedElement **NAME BINDING** +SUBORDINATE OBJECT CLASS anRbsTreatment; +NAMED BY +SUPERIOR OBJECT CLASS "ITU-T Recommendation M.3100": managedElement +AND SUBCLASSES; +WITH ATTRIBUTE anRbsTreatmentId; +CREATE WITH-REFERENCE-OBJECT, WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +**REGISTERED AS** {q835NameBinding 2}; + +#### 6.2.1.3 cablePairIdTone-accessTest + +cablePairIdTone-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS cablePairIdTone AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 3}; + +#### 6.2.1.4 dialledDigitTest-accessTest + +dialledDigitTest-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS dialledDigitTest AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 4}; + +#### 6.2.1.5 dialToneTest-accessTest + +dialToneTest-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS dialToneTest AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 5}; + +#### 6.2.1.6 dryLoop-accessTest + +dryLoop-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS dryLoop AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 6}; + +#### 6.2.1.7 electricalMeasurementTest-accessTest + +electricalMeasurementTest-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS electricalMeasurementTest AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 7}; + +#### 6.2.1.8 isdnQuickTest-accessTest + +isdnQuickTest-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS isdnQuickTest AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745":testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 8}; + +#### 6.2.1.9 loopTest-testActionPerformer + +loopTest-testActionPerformer **NAME BINDING** +SUBORDINATE OBJECT CLASS loopTest AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS "ITU-T Recommendation X.745": testActionPerformer +AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE DELETES-CONTAINED-OBJECTS; +**REGISTERED AS** {q835NameBinding 9}; + +#### 6.2.1.10 metallicTestAccess-testActionPerformer + +metallicTestAccess-testActionPerformer **NAME BINDING** +SUBORDINATE OBJECT CLASS metallicTestAccess AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T Recommendation X.745":testActionPerformer AND +SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745":testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 10}; + +#### 6.2.1.11 patternTest-loopTest + +patternTest-loopTest **NAME BINDING** +SUBORDINATE OBJECT CLASS patternTest AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS loopTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 11}; + +#### 6.2.1.12 spmPulses-accessTest + +spmPulses-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS spmPulses AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 12}; + +#### 6.2.1.13 ringing-accessTest + +ringing-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS ringing AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 13}; + +#### 6.2.1.14 testThresholdClass-managedElement + +testThresholdClass-managedElement **NAME BINDING** +SUBORDINATE OBJECT CLASS testThresholdClass AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T Recommendation M.3100": managedElement AND +SUBCLASSES; +WITH ATTRIBUTE testThresholdClassId; +CREATE; +DELETE; +**REGISTERED AS** {q835NameBinding 14}; + +#### 6.2.1.15 testToLineCircuit-accessTest + +testToLineCircuit-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS testToLineCircuit AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 15}; + +#### 6.2.1.16 voiceAccessTest-accessTest + +voiceAccessTest-accessTest **NAME BINDING** +SUBORDINATE OBJECT CLASS voiceAccessTest AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS accessTest AND SUBCLASSES; +WITH ATTRIBUTE "ITU-T Recommendation X.745": testObjectId; +DELETE; +**REGISTERED AS** {q835NameBinding 16}; + +## 6.3 Definition of packages + +### 6.3.1 Metallic Test Access Line Package + +mtaLinePackage **PACKAGE** + +**BEHAVIOUR** + +mtaLinePackageBehaviour **BEHAVIOUR** + +**DEFINED AS** "The package mtaLinePackage is instantiated if the metallic test access supports a two-wire interface. The attribute typeOfLine identifies the direction of the connection, inbound or outbound or bridged. Setting the attribute typeOfLine switches the direction of the metallic test access.";; + +**ATTRIBUTES** + +typeOfLine GET-REPLACE; + +**REGISTERED AS** {q835Package 1}; + +### 6.3.2 Test environment conditions package + +testEnvironmentConditionsPackage **PACKAGE** + +**BEHAVIOUR** + +testEnvironmentConditionsBehaviour **BEHAVIOUR** + +**DEFINED AS** "This package allows the manager to specify the relative priorities between a test request and normal traffic. This package does not work in case a voiceAccessTest is instantiated, contained in the same accessTest object and its monitorSpeak attribute is set to existingConnection. + +The priority between normal traffic and a test request is determined by the testConditions attribute. + +If this attribute is set to testIfBusy, then testing shall proceed. + +In the case of an active connection and the attribute is set to waitIfBusy, then the test shall wait at most for the period of time specified in the attribute waitTime. If the active connection has not been released within this time, then the test shall enter the terminating phase, skipping the testing phase. The manager shall be notified about the termination using the test result notification with the value busyAccessAborted. Otherwise, testing shall proceed. + +In the case of an active connection and the attribute is set to rejectIfBusy, then the test shall enter the terminating phase, skipping the testing phase immediately. The manager may be notified about the termination using the test result notification with the value busyAccessAborted. + +During the initialization of the testing phase, an outgoing call attempt may be detected, depending on the particular test and implementation. If the value of the testConditions attribute is noCustomerOverrideTest, the test shall continue; otherwise, the terminating phase shall be entered and the call shall proceed. The termination shall be notified to the manager using the test result notification with the value customerOverrideAborted.";; + +**ATTRIBUTES** + +"ITU-T Recommendation X.737": testConditions + +DEFAULT VALUE ASN1LLCTTypeModule.defaultTestConditions GET, + +waitTime DEFAULT VALUE ASN1LLCTTypeModule.defaultBusyLCWaitTime GET-REPLACE; + +**REGISTERED AS** {q835Package 2}; + +### 6.3.3 Voice access package + +voiceAccessPackage **PACKAGE** + +**BEHAVIOUR** + +voiceAccessPackageBehaviour **BEHAVIOUR** + +**DEFINED AS** "This package provides the central operator with a voice access to the line to be tested. This test shall only be applied to a single User Port. An agent provides the voice path by one or both of the following methods. + +For the 'existing connection' method, an object instance with the attribute monitorSpeak set to existingConnection shall enter its initializing phase during an ongoing, previously established normal connection between the User Port and the Operator Port. Then the existing connection shall be transformed into a test condition; i.e. the voice connection shall be maintained (ignoring the testConditions parameter), but the line signalling shall now be controlled by the Q3 interface of the agent by means of other possible test objects for subscriber assisted tests, so that, an on-hook shall not clear the connection at this time, but be indicated to the manager. This allows the use of an existing connection for a subscriber-assisted test. + +For the 'parallel voice path' method, the monitorSpeak attribute shall be set to monitorWithoutMark, monitorWithMark or speakAndMonitor. In this method, a parallel voice path across the test function instead of + +the User Port line circuit is used. The ringBackNo attribute may be used to inform the test function of the operator's directory number to which the parallel voice path shall be established. If the establishment of the parallel voice path fails, an error shall be reported (ringBackFailed) and the test shall be aborted. After successful establishment of the parallel voice path, the agent shall connect the parallel voice path to the User Port line as requested in the monitorSpeak attribute. An initial intrusion tone shall be applied if the values monitorWithMark or speakAndMonitor are requested. + +When a connection is successful, a test result notification with the value connectionEstablished shall be emitted.";; + +#### **ATTRIBUTES** + +monitorSpeak DEFAULT VALUE + +ASN1LLCTTypeModule.defaultMonitorSpeak GET-REPLACE, + +ringBackNo GET-REPLACE; + +**REGISTERED AS** {q835Package 3}; + +## **6.4 Definition of attributes** + +### **6.4.1 AC voltage threshold** + +acVoltageThreshold **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.AcVoltageThreshold; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +acVoltageThresholdBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute specifies the thresholds for AC voltage testing.";; + +**REGISTERED AS** {q835Attribute 1}; + +### **6.4.2 Access network ringback service treatment ID** + +anRbsTreatmentId **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.NameType; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +anRbsTreatmentIdBehaviour **BEHAVIOUR** + +**DEFINED AS** "It is the object identifier.";; + +**REGISTERED AS** {q835Attribute 2}; + +### **6.4.3 Apply ringing current** + +applyRingingCurrent **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.AnRingTest; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +applyRingingCurrentBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute indicates all subscriber lines under test where a ringing current is currently applied to the line.";; + +**REGISTERED AS** {q835Attribute 3}; + +### **6.4.4 Apply tone** + +applyTone **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.Results; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +applyToneBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute indicates for each subscriber line under test the last test result which shall be used to apply the appropriate tones or announcements to the line.";; + +**REGISTERED AS** {q835Attribute 4}; + +### 6.4.5 Capacitance threshold + +capacitanceThreshold **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.CapacitanceThreshold; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +capacitanceThresholdBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the thresholds for capacitance testing.";; +**REGISTERED AS** {q835Attribute 5}; + +### 6.4.6 DC voltage threshold + +dcVoltageThreshold **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.DcVoltageThreshold; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +dcVoltageThresholdBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the thresholds for DC voltage testing.";; +**REGISTERED AS** {q835Attribute 6}; + +### 6.4.7 Dial speed threshold + +dialSpeedThreshold **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.DialSpeedThreshold; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +dialSpeedThresholdBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the thresholds for testing the dial speed.";; +**REGISTERED AS** {q835Attribute 7}; + +### 6.4.8 Electrical measurement test + +electricalMeasurementTestToBePerformed **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.ElectricalMeasurementTestToBePerformed; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +electricalMeasurementTestToBePerformedBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies which electrical parameters are to be tested. Multiple parameters may be identified in the same request. The default is that all parameters which the tester can support shall be tested, excluding subscriber-assisted tests.";; +**REGISTERED AS** {q835Attribute 8}; + +### 6.4.9 ISDN quick test + +isdnQuickTestToBePerformed **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.IsdnQuickTestToBePerformed; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +isdnQuickTestToBePerformedBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies which types of quick tests are to be performed.";; +**REGISTERED AS** {q835Attribute 9}; + +### 6.4.10 Iterations + +iterations **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.Iterations; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +iterationsBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the number of iterations to be performed.";; +**REGISTERED AS** {q835Attribute 10}; + +### 6.4.11 Loopback channel + +#### loopbackChannel ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.LoopbackChannel; +MATCHES FOR EQUALITY; + +#### BEHAVIOUR + +loopbackChannelBehaviour **BEHAVIOUR** + +**DEFINED AS** "The loopbackChannel attribute specifies the channels or connections which are to be looped back.";; + +**REGISTERED AS** {q835Attribute 11}; + +### 6.4.12 Loopback duration + +#### loopbackDuration ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.LoopbackDuration; +MATCHES FOR EQUALITY; + +#### BEHAVIOUR + +loopbackDurationBehaviour **BEHAVIOUR** + +**DEFINED AS** "The loopbackDuration attribute specifies for how long the loopback is applied. The duration is measured from the time of the application of the loopback, and not from the time when the loopback request is received.";; + +**REGISTERED AS** {q835Attribute 12}; + +### 6.4.13 Loopback position + +#### loopbackPosition ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.LoopbackPosition; +MATCHES FOR EQUALITY; + +#### BEHAVIOUR + +loopbackPositionBehaviour **BEHAVIOUR** + +**DEFINED AS** "The loopbackPosition attribute specifies the location and direction of the loopback which is to be applied.";; + +**REGISTERED AS** {q835Attribute 13}; + +### 6.4.14 Metallic test access message + +#### mtaMsg ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.MtaMsg; +MATCHES FOR EQUALITY; + +#### BEHAVIOUR + +mtaMsgBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute specifies the return value of a metallic test access connection. + +Possible values of a successful connection to the metallic test access are: + +- analogueFree                      the analogueAccess is in the idle state +- analogueOccupied                the analogueAccess is in the busy state +- analogueOccupiedNotUsed      the analogueAccess is in a blocked state because of a permanent off-hook situation (blocked permanent) +- analogueBlocked                the analogueAccess is in a blocked state because of administrative or maintenance reasons or due to a transient line fault +- isdnAccess                      successful connection of a basicRateAccess to the metallic test access + +In case of a not successful connection of the MORT to the metallic test access, the attribute mtaMsg is included in the generated independent test invocation error, having one of the following values: + +- error                              not successful connection to the metallic test access due to a general error situation, that is not represented by one of the specific errors described below +- testing                            the MORT is already busy testing via MTA +- mTAoccupied                    all measurement interfaces that would be accessible by the MORT are occupied +- noAccess-noSub                the MORT exists as physical access, but has no subscriber assigned to it + +- noAccess-hdh                      the MORT is an access using higher digital hierarchy that does not support the metallic test access connection +- noAccess-aconc                  the MORT is connected to an analogue access concentrator that does not support the metallic test access connection +- notAccessible                    the metallic test access is temporarily not accessible (e.g. internal testbus busy by another test than MTA) +- noAccess-nuc                    the MORT is part of a nailed-up connection +- noAccess-any                    the MORT is part of an equipment that does not support the connection to the metallic test access due to any reason.";; + +**REGISTERED AS** {q835Attribute 14}; + +### 6.4.15 Metallic test access timeout period + +mtaTimeoutPeriod **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.MtaTimeoutPeriod; + +MATCHES FOR EQUALITY; + +**BEHAVIOUR** + +mtaTimeoutPeriodBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute specifies the time of a metallic test access connection.";; + +**REGISTERED AS** {q835Attribute 15}; + +### 6.4.16 Monitor and speak + +monitorSpeak **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.MonitorSpeak; + +MATCHES FOR EQUALITY; + +**BEHAVIOUR** + +monitorSpeakBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute specifies whether the line is to be monitored, whether speech can be injected, and whether a tone is used to indicate to the user that the line is being monitored.";; + +**REGISTERED AS** {q835Attribute 16}; + +### 6.4.17 Number of digits + +numberOfDigits **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.NumberOfDigits; + +MATCHES FOR EQUALITY; + +**BEHAVIOUR** + +numberOfDigitsBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute specifies the number of digits which are to be tested during a dialled digit test. The default value is 1.";; + +**REGISTERED AS** {q835Attribute 17}; + +### 6.4.18 Off hook simulation + +offHookSimulation **ATTRIBUTE** + +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.OffHookSimulation; + +MATCHES FOR EQUALITY; + +**BEHAVIOUR** + +offHookSimulationBehaviour **BEHAVIOUR** + +**DEFINED AS** "This attribute specifies how offHook for the dial tone test is realized depending on national, vendor or operator specific conditions. The default value is 0, which means loop calling.";; + +**REGISTERED AS** {q835Attribute 18}; + +### 6.4.19 Proposed metallic test access + +proposedMTA **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.NumberOfMTA; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +proposedMTABehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute identifies the measurement interface to which the MORT is connected.";; +**REGISTERED AS** {q835Attribute 19}; + +### 6.4.20 Pulse no pulse ratio + +pulseNoPulseRatio **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.PulseNoPulseRatio; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +pulseNoPulseRatioBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the threshold for testing the pulse no pulse ratio.";; +**REGISTERED AS** {q835Attribute 20}; + +### 6.4.21 Request result type + +requestedResultType **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.RequestedResultType; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +requestedResultTypeBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute is used to control the test result reports by a combination of the three Boolean parameters GO, NOGO and VALUE. If GO is true, a result report is sent only if a port passed a test. If NOGO is true, a result report is sent only if a port did not pass a test. If VALUE is true, the measured value is reported.";; +**REGISTERED AS** {q835Attribute 21}; + +### 6.4.22 Resistance threshold + +resistanceThreshold **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.ResistanceThreshold; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +resistanceThresholdBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the thresholds for resistance testing.";; +**REGISTERED AS** {q835Attribute 22}; + +### 6.4.23 Ring + +ring **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.Ring; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +ringBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the time for which ringing is applied. The ring attribute is used to generate continuous or timed ringing. If it has an integer value, then it specifies the time in seconds for which ringing is applied. If it has a Null value, then continuous ringing shall be applied. If the value is not specified, then the default value shall be used.";; +**REGISTERED AS** {q835Attribute 23}; + +### 6.4.24 Ring back number + +ringBackNo **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.RingBackNo; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +ringBackNoBehaviour **BEHAVIOUR** +**DEFINED AS** "The ringBackNo attribute allows the test function to be informed of the telephone number of the operator and to dial back to set up a monitor or a monitor and speak path.";; +**REGISTERED AS** {q835Attribute 24}; + +### 6.4.25 Number of subscriber private meter (SPM) pulses + +spmPulsesNo **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.SpmPulses; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +spmPulsesNoBehaviour **BEHAVIOUR** +**DEFINED AS** "The spmPulsesNo attribute indicates the number of SPM pulses which shall be applied. This number ranges between 0 and 99.";; +**REGISTERED AS** {q835Attribute 25}; + +### 6.4.26 Type of Line + +typeOfLine **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.TypeOfLine; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +typeOfLineBehaviour **BEHAVIOUR** +**DEFINED AS** "This attribute specifies the switched direction of the measurement interface in case of a two-wire interface.";; +**REGISTERED AS** {q835Attribute 26}; + +### 6.4.27 Wait time + +waitTime **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.WaitTime; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +waitTimeBehaviour **BEHAVIOUR** +**DEFINED AS** "In case of waitIfBusy as value for testConditions attribute, this attribute defines the maximum amount of time to wait for the end of the busy condition before performing a test.";; +**REGISTERED AS** {q835Attribute 27}; + +### 6.4.28 Test threshold class identifier + +testThresholdClassId **ATTRIBUTE** +WITH ATTRIBUTE SYNTAX ASN1LLCTTypeModule.NameType; +MATCHES FOR EQUALITY; +**BEHAVIOUR** +testThresholdClassIdBehaviour **BEHAVIOUR** +**DEFINED AS** "It is the object identifier, the RDN of the test threshold class.";; +**REGISTERED AS** {q835Attribute 28}; + +## 6.5 Definition of actions + +### 6.5.1 Loopback select + +loopbackSelect **ACTION** + +**BEHAVIOUR** + +loopbackSelectActionBehaviour **BEHAVIOUR** + +**DEFINED AS** "The loopbackSelect action is used either to change duration, position and type of already existing loopbacks, or to remove one. If the loopbackSelect action specifies a new loopback duration, position and type, it causes any existing loopbacks specified by the managed object to be removed, regardless of their specified duration or time to completion. It then causes a new loopback to be applied according to the new specified parameters of duration, position and type. + +If the action specifies as loopback position the value noloopback, the existing loopback specified by the managed object is removed. + +If the new parameters specified are invalid, then the request is rejected and the original loopback is not removed or otherwise affected. + +The result returns the parameters which are given in the request and confirms the correct reception of the requested.";; + +MODE CONFIRMED; + +WITH INFORMATION SYNTAX + +ASN1LLCTTypeModule.LoopbackSelectRequestInfo; + +WITH REPLY SYNTAX + +ASN1LLCTTypeModule.LoopbackSelectRequestResult; + +**REGISTERED AS** {q835Action 1}; + +## 6.6 Definition of notifications + +### 6.6.1 Off hook + +offHook **NOTIFICATION** + +**BEHAVIOUR** + +offHookBehaviour **BEHAVIOUR** + +**DEFINED AS** "This notification indicates that a CPE under test has changed to the off-hook condition. It contains the associated user port address and the dialled service code.";; + +WITH INFORMATION SYNTAX ASN1LLCTTypeModule.OffHook; + +**REGISTERED AS** {q835Notification 1}; + +### 6.6.2 On hook + +onHook **NOTIFICATION** + +**BEHAVIOUR** + +onHookBehaviour **BEHAVIOUR** + +**DEFINED AS** "This notification indicates that a CPE under test has changed to the on-hook condition. It contains the associated user port address and optionally test results produced in the LE for this user port.";; + +WITH INFORMATION SYNTAX ASN1LLCTTypeModule.OnHook; + +**REGISTERED AS** {q835Notification 2}; + +### 6.6.3 Time out + +timeOut **NOTIFICATION** + +**BEHAVIOUR** + +timeOutBehaviour **BEHAVIOUR** + +**DEFINED AS** "This notification indicates that a procedure applying a tone or ringing current to a subscriber line under test has been terminated. It contains the associated user port address.";; + +WITH INFORMATION SYNTAX ASN1LLCTTypeModule.UserPort; + +**REGISTERED AS** {q835Notification 3}; + +## 6.7 Definition of parameters + +### 6.7.1 Access result + +#### accessResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.AccessResult; + +#### **BEHAVIOUR** + +accessResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The accessResult is carried in the test result notification testResultInfo additionalInformation field.";; + +**REGISTERED AS** {q835Parameter 1}; + +### 6.7.2 Dialed digit test result + +#### dialledDigitTestResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.DialedDigitTestResult; + +#### **BEHAVIOUR** + +dialledDigitTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The dialledDigitTestResult is carried in the test result notification testResultInfo additional information field when the dialled digit test is invoked.";; + +**REGISTERED AS** {q835Parameter 2}; + +### 6.7.3 Dialed digit test uncontrolled request + +#### dialledDigitTestUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.DialedDigitTestUncontrolledRequestType; + +#### **BEHAVIOUR** + +dialledDigitTestUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The dialledDigitTestUncontrolledRequest parameter is used to check the proper operation of the subscriber's terminal equipment with the testCategoryInformation field of an uncontrolled test request.";; + +**REGISTERED AS** {q835Parameter 3}; + +### 6.7.4 Dialed digit test uncontrolled result + +#### dialledDigitTestUncontrolledResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledResult.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.DialedDigitTestResult; + +#### **BEHAVIOUR** + +dialledDigitTestUncontrolledResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The dialledDigitTestUncontrolledResult parameter contains the result(s) of previously requested dialled digit tests and is carried in the additional information field of the uncontrolled test response.";; + +**REGISTERED AS** {q835Parameter 4}; + +### 6.7.5 Dial tone test result + +#### dialToneTestResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.DialToneTestResult; + +#### **BEHAVIOUR** + +dialToneTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The dialToneTestResult is carried in the test result notification testResultInfo additional information field when the dial tone test is invoked.";; + +**REGISTERED AS** {q835Parameter 5}; + +### 6.7.6 Dial tone test uncontrolled request + +#### dialToneTestUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.DialToneTestUncontrolledRequestType; + +#### **BEHAVIOUR** + +dialToneTestUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The dialToneTestUncontrolledRequest parameter is used to request the simulation of an off-hook condition in the NE. It is checked whether the dial tone appears at the line circuit termination or not.";; + +**REGISTERED AS** {q835Parameter 6}; + +### 6.7.7 Dial tone test uncontrolled result + +#### dialToneTestUncontrolledResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledResult.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.DialToneTestResult; + +#### **BEHAVIOUR** + +dialToneTestUncontrolledResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The dialToneTestUncontrolledResult parameter contains the result(s) of previously requested dial tone tests and is carried in the additional information field of the uncontrolled test response.";; + +**REGISTERED AS** {q835Parameter 7}; + +### 6.7.8 Electrical measurement test result + +#### electricalMeasurementTestResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.ElectricalMeasurementTestResult; + +#### **BEHAVIOUR** + +electricalMeasurementTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The electricalMeasurementTestResult is carried in the test result notification testResultInfo additionalInformation field.";; + +**REGISTERED AS** {q835Parameter 8}; + +### 6.7.9 Electrical measurement test uncontrolled request + +#### electricalMeasurementTestUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.ElectricalMeasurementTestUncontrolledRequestType; + +#### **BEHAVIOUR** + +electricalMeasurementTestUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The electricalMeasurementTestUncontrolledRequest parameter is used to request one or more electrical measurement tests with the testCategoryInformation field of an uncontrolled test request.";; + +**REGISTERED AS** {q835Parameter 9}; + +### 6.7.10 Electrical measurement test uncontrolled result + +#### electricalMeasurementTestUncontrolledResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledResult.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.ElectricalMeasurementTestResult; + +#### **BEHAVIOUR** + +electricalMeasurementTestUncontrolledResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The electricalMeasurementTestUncontrolledResult parameter contains the result(s) of previously requested electrical measurement tests and is carried in the additional information field of the uncontrolled test response.";; + +**REGISTERED AS** {q835Parameter 10}; + +### 6.7.11 Generic test result + +#### genericTestResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.GenericTestResult ; + +#### **BEHAVIOUR** + +genericTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The genericTestResult is carried in the test result notification testResultInfo additionalInformation field.";; + +**REGISTERED AS** {q835Parameter 11}; + +### 6.7.12 Invalid loopback request + +#### invalidLoopbackRequest **PARAMETER** + +CONTEXT SPECIFIC-ERROR; + +WITH SYNTAX ASN1LLCTTypeModule.InvalidLoopbackRequest; + +#### **BEHAVIOUR** + +invalidLoopbackRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The invalidLoopbackRequest parameter type is used to report that the requested loopback cannot be applied. This may be due to invalid parameters or to a loopback already in existence.";; + +**REGISTERED AS** {q835Parameter 12}; + +### 6.7.13 ISDN quick test uncontrolled request + +#### isdnQuickTestUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.IsdnQuickTestUncontrolledRequestType; + +#### **BEHAVIOUR** isdnQuickTestUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The isdnQuickTestUncontrolledRequest parameter is used to request one of a set of possible ISDN tests, as layer 1 activation (in case of an ISDN BA: test on the capability to activate the layer 1; in case of an ISDN PRA: test on the presence of an active layer 1), loop back test, power feeding test and function test.";; + +**REGISTERED AS** {q835Parameter 13}; + +### 6.7.14 ISDN quick test uncontrolled result + +#### isdnQuickTestUncontrolledResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledResult.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.IsdnQuickTestResult; + +#### **BEHAVIOUR** isdnQuickTestUncontrolledResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The isdnQuickTestUncontrolledResult parameter contains the result of previously requested ISDN quick tests and is carried in the additional information field of the uncontrolled test response. The way, how the test results are achieved is implementation specific; the function test e.g. may be implemented as a sequence of the other test functions.";; + +**REGISTERED AS** {q835Parameter 14}; + +### 6.7.15 Loopback test result + +#### loopbackTestResult **PARAMETER** + +CONTEXT EVENT-INFO; + +WITH SYNTAX ASN1LLCTTypeModule.LoopTestResult; + +#### **BEHAVIOUR** + +loopbackTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The loopbackTestResult is carried in the test result notification testResultInfo additionalInformation field.";; + +**REGISTERED AS** {q835Parameter 15}; + +### 6.7.16 Loop back test uncontrolled request + +#### loopBackTestUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.LoopBackTestUncontrolledRequestType; + +#### **BEHAVIOUR** + +loopBackTestUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The loopBackTestUncontrolledRequest parameter is used to request a loopback at a certain loopback point, to apply a test pattern and to determine differences between the sent and received test pattern. Contained in the request are duration and position of the loopback and the channel(s) to which the loopback shall be applied.";; + +**REGISTERED AS** {q835Parameter 16}; + +### 6.7.17 Loop back test uncontrolled result + +#### loopBackTestUncontrolledResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledResult.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.LoopBackTestUncontrolledResult; + +#### **BEHAVIOUR** + +loopBackTestUncontrolledResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The loopBackTestUncontrolledResult parameter contains the result(s) of previously requested loopback tests including the comparison of the sent and received test patterns and is carried in the additional information field of the uncontrolled test response";; + +**REGISTERED AS** {q835Parameter 17}; + +### 6.7.18 Number of metallic test accesses + +#### numberOfMTA **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestControlledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.NumberOfMTA; + +#### **BEHAVIOUR** numberOfMTABehaviour **BEHAVIOUR** + +**DEFINED AS** "The numberOfMTA parameter is used to request a metallic test access connection at the measurement interface identified by NumberOfMTA. The definition of a naming scheme is not part of this standard and is up to the implementation.";; + +**REGISTERED AS** {q835Parameter 18}; + +### 6.7.19 Pattern test result + +#### patternTestResult **PARAMETER** + +CONTEXT EVENT-INFO; + +WITH SYNTAX ASN1LLCTTypeModule.PatternTestResult; + +#### **BEHAVIOUR** + +patternTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The patternTestResult is carried in the test result notification testResultInfo additionalInformation field.";; + +**REGISTERED AS** {q835Parameter 19}; + +### 6.7.20 Ringing test uncontrolled request + +#### ringingTestUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.GenericUncontrolledRequestType; + +#### **BEHAVIOUR** + +ringingTestUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The ringingTestUncontrolledRequest parameter is used to apply ringing to the subscriber line with the testCategoryInformation field of an uncontrolled test request.";; + +**REGISTERED AS** {q835Parameter 20}; + +### 6.7.21 SPM pulses test uncontrolled request + +#### spmPulsesTestUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.SpmPulsesTestUncontrolledRequestType; + +#### **BEHAVIOUR** + +spmPulsesUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The spmPulsesUncontrolledRequest parameter is used to request one or more SPM pulses to be sent to the subscriber private meter with the testCategoryInformation field of an uncontrolled test request.";; + +**REGISTERED AS** {q835Parameter 21}; + +### 6.7.22 Test to line circuit result + +#### testToLineCircuitResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.TestToLineCircuitResult; + +#### **BEHAVIOUR** + +testToLineCircuitResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The testToLineCircuitResult is carried in the test result notification testResultInfo additionalInformation field.";; + +**REGISTERED AS** {q835Parameter 22}; + +### 6.7.23 Test to line circuit uncontrolled request + +#### testToLineCircuitUncontrolledRequest **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledInfo.testCategoryInformation; + +WITH SYNTAX ASN1LLCTTypeModule.GenericUncontrolledRequestType; + +#### **BEHAVIOUR** + +testToLineCircuitUncontrolledRequestBehaviour **BEHAVIOUR** + +**DEFINED AS** "The testToLineCircuitUncontrolledRequest parameter is used to request the check of the ability of the line circuit to provide and to detect certain signals and feeding voltage with the testCategoryInformation field of an uncontrolled test request.";; + +**REGISTERED AS** {q835Parameter 23}; + +### 6.7.24 Test to line circuit uncontrolled result + +#### testToLineCircuitUncontrolledResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestRequestUncontrolledResult.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.TestToLineCircuitResult; + +#### **BEHAVIOUR** + +testToLineCircuitUncontrolledResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The testToLineCircuitUncontrolledResult parameter contains the result(s) of previously requested inward tests and is carried in the additional information field of the uncontrolled test response.";; + +**REGISTERED AS** {q835Parameter 24}; + +### 6.7.25 Voice access test result + +#### voiceAccessTestResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.VoiceAccessTestResult; + +#### **BEHAVIOUR** + +voiceAccessTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The voiceAccessTestResult is carried in the test result notification testResultInfo additional information field.";; + +**REGISTERED AS** {q835Parameter 25}; + +### 6.7.26 ISDN quick test result + +isdnQuickTestResult **PARAMETER** + +CONTEXT Test-ASN1Module.TestResultInfo.additionalInformation; + +WITH SYNTAX ASN1LLCTTypeModule.IsdnQuickTestResult; + +**BEHAVIOUR** + +isdnQuickTestResultBehaviour **BEHAVIOUR** + +**DEFINED AS** "The isdnQuickTestResult is carried in the test result notification testResultInfo additional information field.";; + +**REGISTERED AS** {q835Parameter 26}; + +## 6.8 ASN.1 defined types module + +**ASN1LLCTTypeModule** {itu-t(0) recommendation(0) q(17) q835 (835) informationModel(0) asn1Module(2) asn1TypeModule(0)} + +**DEFINITIONS IMPLICIT TAGS ::=** + +**BEGIN** -- *EXPORTS everything* + +**IMPORTS** + +-- *ITU-T Recommendation M.3100* + +NameType + +**FROM** ASN1DefinedTypesModule {ccitt recommendation m gnm(3100) informationModel(0) asn1Module(2)} + +asn1DefinedTypesModule(0)} + +-- *ITU-T Recommendation Q.824.5* + +EnvelopeFunctionAddress, Layer3PortAddress + +**FROM** ASN1CMLETypeModule {itu-t(0) recommendation(0) q(17) ca(824) dot(127) v5interface(5) informationModel(0) asn1Modules(2) cAV5LEModule(0)} + +-- *ITU-T Recommendation Q.831* + +DigitComb + +**FROM** ASN1FPLETypeModule {itu-t(0) recommendation(0) q(17) fpv5(831) informationModel(0) asn1Modules(2) fpV5LEModule(0)} + +-- *ITU-T Recommendation X.711* + +ObjectInstance + +**FROM** CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)} + +-- *ITU-T Recommendation Q.824.0* + +E164DN + +**FROM** CACCommonModule {itu-t(0) recommendation(0) q(17) ca(824) dot(127) common(0) informationModel(0) asn1Modules(2) cACCommonModule(0)} + +-- *ITU-T Recommendation X.745* + +ActualStartTime, + +ActualStopTime, + +EndTime, + +TestOutcome, + +TestRequestControlledInfo, + +TestRequestUncontrolledInfo, + +TestRequestUncontrolledResult, + +TestResultInfo, + +Timespec + +**FROM** Test-ASN1Module { joint-iso-ccitt ms(9) function(2) part12(12) asn1Module(2) 0 } + +-- *ITU-T Recommendation X.737* + +ErrorRatioReportType, + +LoopBackTestResults, + +TestPattern, + +TestConditions + +**FROM** TestCategories-ASN1Module {joint-iso-ccitt ms(9) function(2) part14(14) asn1Module(2) 1} + +; + +**q835InformationModel** OBJECT IDENTIFIER ::= {itu-t(0) recommendation(0) q(17) q835 (835) informationModel(0)} +**q835ManagedObjectClass** OBJECT IDENTIFIER ::= {q835InformationModel-managedObjectClass(3)} +**q835Package** OBJECT IDENTIFIER ::= {q835InformationModel package(4)} +**q835Parameter** OBJECT IDENTIFIER ::= {q835InformationModel parameter(5)} +**q835NameBinding** OBJECT IDENTIFIER ::= {q835InformationModel nameBinding(6)} +**q835Attribute** OBJECT IDENTIFIER ::= {q835InformationModel attribute(7)} +**q835Action** OBJECT IDENTIFIER ::= {q835InformationModel action(9)} +**q835Notification** OBJECT IDENTIFIER ::= {q835InformationModel notification(10)} +**AccessResult** ::= SET OF SEQUENCE { +     mORT [0] MORT, +     realStartTime [1] ActualStartTime OPTIONAL, +     realStopTime [2] ActualStopTime OPTIONAL, +     accessTestResult [3] AccessTestResult} +**AccessTestResult** ::= ENUMERATED { +     connectionEstablished (0), +     accessFailed (1), +     busyAccessAborted (2), +     dangerousVoltage (3), +     testMechanismBusy (4), +     customerOverrideAborted (5)} +**AcVoltage** ::= INTEGER (0..250000) -- *milli Volt* +**AcVoltageThreshold** ::= SEQUENCE { +     acaEarth [1] AcVoltage OPTIONAL, +     acbEarth [2] AcVoltage OPTIONAL, +     acab [3] AcVoltage OPTIONAL} +**AnRingTest** ::= SET OF UserPort +**Between** ::= SET OF SEQUENCE { +     between BetweenType, +     threshold Threshold OPTIONAL} +**BetweenType** ::= ENUMERATED { +     aTob (0), +     aToEarth (1), +     bToEarth (2), +     aToBattery (3), +     bToBattery (4), +     aTobReverse (5), +     aToEarthReverse (6), +     bToEarthReverse (7), +     aToBatteryReverse (8), +     bToBatteryReverse (9)} +**Capacitance** ::= INTEGER (0..10000) -- *nano Farad* +**CapacitanceThreshold** ::= SEQUENCE { +     caEarth [1] Capacitance OPTIONAL, +     cbEarth [2] Capacitance OPTIONAL, +     cabUpperLimit [3] Capacitance OPTIONAL, +     cabLowerLimit [4] Capacitance OPTIONAL} +**DcVoltage** ::= INTEGER (0..150000) -- *milli Volt* +**DcVoltageThreshold** ::= SEQUENCE { +     dcaEarth [1] DcVoltage OPTIONAL, +     dcbEarth [2] DcVoltage OPTIONAL, +     dcab [3] DcVoltage OPTIONAL} +**defaultAcVoltageThreshold** AcVoltageThreshold ::= { +     acaEarth 250000, +     acbEarth 250000, +     acab 250000} +**defaultCapacitanceThreshold** CapacitanceThreshold ::= { +     caEarth 0, +     cbEarth 0, +     cabUpperLimit 10000, +     cabLowerLimit 0} + +**defaultDcVoltageThreshold** DcVoltageThreshold ::= { +dcaEarth 150000, +dcbEarth 150000, +dcab 150000} + +**defaultDialSpeedThreshold** DialSpeedThreshold ::= { +dialSpeedUpperLimit 255, +dialSpeedLowerLimit 0} + +**defaultIsdnQuickTestToBePerformed** IsdnQuickTestToBePerformed ::= functionTest + +**defaultMtaTimeoutPeriod** MtaTimeoutPeriod ::= minutes : 5 + +**defaultPulseNoPulseRatio** PulseNoPulseRatio ::= { +pulseNoPulseRatioUpperLimit 100, +pulseNoPulseRatioLowerLimit 0} + +**defaultResistanceThreshold** ResistanceThreshold ::= { +raEarth milliOhm : 0, +rbEarth milliOhm : 0, +rabUpperLimit kiloOhm : 100000, +rabLowerLimit milliOhm : 0, +rLoop milliOhm : 0, +rEarth milliOhm : 0} + +**DialledDigits** ::= IA5String (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"|"\*"|"#"")) + +**DialledDigitTestResult** ::= SEQUENCE OF ReceivedDigit + +**DialledDigitTestUncontrolledRequestType** ::= SEQUENCE { +numberOfDigits [1] NumberOfDigits, +testConditions [2] TestConditions OPTIONAL, +waitTime [3] INTEGER OPTIONAL} +-- waitTime has importance only if TestConditions are set to waitIfBusy. + +**DialSpeed** ::= INTEGER (0..255) -- x 0.1 Hz + +**DialSpeedThreshold** ::= SEQUENCE { +dialSpeedUpperLimit [1] DialSpeed OPTIONAL, +dialSpeedLowerLimit [2] DialSpeed OPTIONAL} + +**DialToneTestResult** ::= SET OF SEQUENCE { +mORT [0] MORT, +realStartTime [1] ActualStartTime OPTIONAL, +realStopTime [2] ActualStopTime OPTIONAL, +result [3] Result} + +**DialToneTestUncontrolledRequestType** ::= SEQUENCE { +offHookSimulation [0] OffHookSimulation, +requestedResultType [1] RequestedResultType, +iterations [2] Iterations, +testConditions [3] TestConditions OPTIONAL, +waitTime [4] INTEGER OPTIONAL} +-- waitTime has importance only if TestConditions are set to waitIfBusy. + +**ElectricalMeasurementTestResult** ::= SET OF SEQUENCE { +mORT [0] MORT, +realStartTime [1] ActualStartTime OPTIONAL, +realStopTime [2] ActualStopTime OPTIONAL, +foreignAcVoltage [3] Reading OPTIONAL, +foreignDcVoltage [4] Reading OPTIONAL, +foreignACCurrent [5] Reading OPTIONAL, +foreignDCCurrent [6] Reading OPTIONAL, +resistanceInsulation [7] Reading OPTIONAL, +resistanceLoop [8] Reading OPTIONAL, +capacitance [9] Reading OPTIONAL, +termination [10] Termination OPTIONAL, +feedingVoltage [11] Reading OPTIONAL, +feedingCurrent [12] Reading OPTIONAL, +testOutcome [13] TestOutcome OPTIONAL} + +``` + +ElectricalMeasurementTests ::= SEQUENCE { + foreignAcVoltage [0] Between OPTIONAL, + foreignDcVoltage [1] Between OPTIONAL, + foreignACCurrent [2] Between OPTIONAL, + foreignDCCurrent [3] Between OPTIONAL, + capacitance [4] Between OPTIONAL, + resistance [5] ResistanceBetween OPTIONAL, + termination [6] NULL OPTIONAL, + feedingVoltage [7] Between OPTIONAL, + feedingCurrent [8] Between OPTIONAL, + ring [9] Between OPTIONAL} + +ElectricalMeasurementTestToBePerformed ::= CHOICE { + full NULL, + electricalMeasurementTests ElectricalMeasurementTests} + +ElectricalMeasurementTestUncontrolledRequestType ::= SEQUENCE { + electrMeasToBePerformed [0] ElectricalMeasurementTestToBePerformed, + requestedResultType [1] RequestedResultType, + testConditions [2] TestConditions OPTIONAL, + waitTime [3] INTEGER OPTIONAL} + -- waitTime has importance only if TestConditions are set to waitIfBusy. + +FunctionTestResult ::= ENUMERATED { + noFailure (0), + activationLayer1Failure (1), + ntLoopFailure (2), + leLoopFailure (3), + dtrLoopFailure (4), + shortCircuit (5), + neError (6), + alarmCheckFailure (7), + leLoopAndPowerFeedingFailure (8)} + +GenericTestResult ::= SET OF SEQUENCE { + mORT [0] MORT, + realStartTime [1] ActualStartTime OPTIONAL, + realStopTime [2] ActualStopTime OPTIONAL, + testOutcome [3] TestOutcome} + +GenericUncontrolledRequestType ::= SEQUENCE { + testConditions [1] TestConditions OPTIONAL, + waitTime [2] INTEGER OPTIONAL} + -- waitTime has importance only if TestConditions are set to waitIfBusy. + +InvalidLoopbackRequest ::= ENUMERATED { + loopExists (0), + loopNotSupported (1), + loopTimeTooLarge (2)} + +IsdnQuickTestResult ::= SET OF SEQUENCE{ + mORT [0] MORT, + realStartTime [1] ActualStartTime OPTIONAL, + realStopTime [2] ActualStopTime OPTIONAL, + layer1Activation [3] Layer1ActivationResult OPTIONAL, + loopbackTest [4] LoopbackQuickTestResult OPTIONAL, + powerFeedingTest [5] PowerFeedingTestResult OPTIONAL, + functionTest [6] FunctionTestResult OPTIONAL, + testOutcome [7] TestOutcome OPTIONAL} + +IsdnQuickTestToBePerformed ::= ENUMERATED { + layer1Activation (0), + loopbackTest (1), + powerFeedingTest (2), + functionTest (3)} + +``` + +``` + +IsdnQuickTestUncontrolledRequestType ::= SEQUENCE { + isdnQuickTestToBePerformed [1] IsdnQuickTestToBePerformed, + requestedResultType [2] RequestedResultType, + testConditions [3] TestConditions OPTIONAL + waitTime [4] INTEGER OPTIONAL} + -- waitTime has importance only if TestConditions are set to waitIfBusy. + +Iterations ::= INTEGER +Layer1ActivationResult ::= ENUMERATED { + noFailure (0), + activationLayer1Failure (1)} + +LoopbackChannel ::= ENUMERATED { + b1 (0), + b2 (1), + b1b2d (2), + pra (3)} + +LoopbackDuration ::= Timespec +LoopbackPosition ::= ENUMERATED { + noLoopback (0), + ltNetwork (1), + nt1Network (2), + repNetwork (3)} + +LoopbackQuickTestResult ::= ENUMERATED { + noFailure (0), + ntLoopFailure (1), + leLoopFailure (2)} + +LoopbackResult ::= ENUMERATED { + override (0)} + -- Further values for this syntax are for further study. + +LoopbackSelectRequestInfo ::= SEQUENCE { + loopbackPosition LoopbackPosition, + loopbackTime LoopbackDuration, + loopbackChannel LoopbackChannel OPTIONAL} + +LoopbackSelectRequestResult ::= ENUMERATED { + loopbackSet (1), + loopNotSupported (2), + loopbackTimeTooLarge (3)} + +LoopTestResult ::= SET OF SEQUENCE { + mORT [0] MORT, + realStartTime [1] ActualStartTime OPTIONAL, + realStopTime [2] ActualStopTime OPTIONAL, + testOutcome [3] TestOutcome, + loopbackResult [4] LoopbackResult OPTIONAL} + +LoopbackTestUncontrolledRequestType ::= SEQUENCE { + loopbackDuration [1] LoopbackDuration, + loopbackPosition [2] LoopbackPosition, + loopbackChannel [3] LoopbackChannel, + testPattern [4] TestPattern OPTIONAL, + errorRatioReport [5] ErrorRatioReportType OPTIONAL, + testConditions [6] TestConditions OPTIONAL, + waitTime [7] INTEGER OPTIONAL} + -- waitTime has importance only if TestConditions are set to waitIfBusy. + +LoopbackTestUncontrolledResult ::= LoopbackTestResults +MonitorSpeak ::= ENUMERATED { + monitorWithMark (0), + speakAndMonitor (1), + monitorWithOutMark (2), + existingConnection (3)} + +``` + +**MORT** ::= ObjectInstance +**MtaMsg** ::= ENUMERATED { +     error (0), +     analogueFree (1), +     analogueOccupied (2), +     analogueOccupiedNotUsed (3), +     analogueBlocked (4), +     testing (5), +     mTAoccupied (6), +     noAccess-noSub (7), +     noAccess-hdh (8), +     noAccess-aconc (9), +     notAccessible (10), +     noAccess-nuc (11), +     isdAccess (12), +     noAccess-any (13)} +**MtaTimeoutPeriod** ::= Timespec +**NotDigit** ::= ENUMERATED { +     recallButton (0), +     onhook (1), +     wrongSignal (2), +     offhook (3)} +**Null** ::= NULL +**NumberOfDigits** ::= INTEGER +**NumberOfMTA** ::= INTEGER +**OffHook** ::= SEQUENCE { +     port [0] UserPort, +     serviceNumber [1] DigitComb} +**OffHookSimulation** ::= ENUMERATED { +     loopCalling (0), +     earthCalling (1)} +**OnHook** ::= SEQUENCE { +     port [0] UserPort, +     dtmfResult [1] TestOutcome OPTIONAL} +**PatternTestResult** ::= SET OF SEQUENCE { +     mORT [0] MORT, +     realStartTime [1] ActualStartTime OPTIONAL, +     realStopTime [2] ActualStopTime OPTIONAL, +     testOutcome [3] TestOutcome, +     loopbackTestResult [4] LoopbackTestResult OPTIONAL} +**PowerFeedingTestResult** ::= ENUMERATED { +     noFailure (0), +     shortCircuit (1), +     neError (2)} +**PulseNoPulseRatio** ::= SEQUENCE { +     pulseNoPulseRatioUpperLimit [1] Ratio OPTIONAL, +     pulseNoPulseRatioLowerLimit [2] Ratio OPTIONAL} +**Range** ::= INTEGER +**Ratio** ::= INTEGER (0..100) -- *percentage* +**Reading** ::= SEQUENCE { +     aToB [0] Result OPTIONAL, +     aToEarth [1] Result OPTIONAL, +     bToEarth [2] Result OPTIONAL, +     aToBattery [3] Result OPTIONAL, +     bToBattery [4] Result OPTIONAL, +     bToEarthReverse [5] Result OPTIONAL, +     aToEarthReverse [6] Result OPTIONAL, +     bToa [7] Result OPTIONAL, +     aToBatteryReverse [8] Result OPTIONAL, +     bToBatteryReverse [9] Result OPTIONAL} + +``` + +ReceivedDigit ::= SEQUENCE { + digit [0] CHOICE { + normalDigits [0] DialedDigits, + notDigit [8] NotDigit}, + lowLevel [1] REAL OPTIONAL, + highLevel [2] REAL OPTIONAL, + lowFrequency [3] REAL OPTIONAL, + highFrequency [4] REAL OPTIONAL, + pulseLength [5] REAL OPTIONAL, + makeDuration [6] REAL OPTIONAL, + breakDuration [7] REAL OPTIONAL} + +RequestedResultType ::= SEQUENCE { + passed BOOLEAN, + notPassed BOOLEAN, + value BOOLEAN} + +ResistanceBetween ::= CHOICE { + insulation [0] Between, + loop [1] Between} + +Resistance ::= CHOICE { + milliOhm [0] INTEGER (0..100000), + ohm [1] INTEGER (0..100000), + kiloOhm [2] INTEGER (0..100000)} + +ResistanceThreshold ::= SEQUENCE { + raEarth [1] Resistance OPTIONAL, + rbEarth [2] Resistance OPTIONAL, + rabUpperLimit [3] Resistance OPTIONAL, + rabLowerLimit [4] Resistance OPTIONAL, + rLoop [5] Resistance OPTIONAL, + rEarth [6] Resistance OPTIONAL} + +Result ::= SEQUENCE { + testOutcome TestOutcome OPTIONAL, + value REAL OPTIONAL} + +ResultOfTestToLineCircuit ::= SEQUENCE { + feedingVoltage [0] Result OPTIONAL, + feedingCurrent [1] Result OPTIONAL, + loopRingTripDetection [2] Result OPTIONAL, + ringingCurrent [3] Result OPTIONAL, + privateMeterPulses [4] Result OPTIONAL, + codecTesting [5] Result OPTIONAL, + digitReception [6] Result OPTIONAL} + +Results ::= SET OF SEQUENCE { + port [0] UserPort, + result [1] TestOutcome} + +Ring ::= CHOICE { + timedRing [0] INTEGER, -- number of seconds + continuousRing [1] NULL} + +RingBackNo ::= E164DN + +SpmPulses ::= INTEGER (0..99) + +SpmPulsesTestUncontrolledRequestType ::= SEQUENCE { + numberOfPulses [1] SpmPulses, + testConditions [2] TestConditions OPTIONAL, + waitTime [3] INTEGER OPTIONAL} + -- waitTime has importance only if TestConditions are set to waitIfBusy. + +Termination ::= ENUMERATED { + nTEAndCPE (0), + nTE (1), + leakageCurrent (2), + noTermination (3), + offHook (4), + nonStandardTermination (5)} + +``` + +``` + +TestsPassed ::= ENUMERATED { + timesTaken (0)} +TestToLineCircuitResult ::= SET OF SEQUENCE { + mORT [0] MORT, + realStartTime [1] ActualStartTime OPTIONAL, + realStopTime [2] ActualStopTime OPTIONAL, + testOutcome [3] TestOutcome, + resultOfTestToLineCircuit [4] ResultOfTestToLineCircuit OPTIONAL} +Threshold ::= SEQUENCE { + min [0] REAL OPTIONAL, + max [1] REAL OPTIONAL} +TypeOfLine ::= ENUMERATED { + inbound (0), + outbound (1), + bridged (2)} +UserPort ::= CHOICE { + pstn [0] Layer3PortAddress, + isdn [1] EnvelopeFunctionAddress} +VoiceAccessTestResult ::= ENUMERATED { + connectionEstablished (0), + ringbackFailed (3), + noExistingConnection (6)} +WaitTime ::= EndTime +-- default value definitions +defaultBusyLCWaitTime EndTime ::= relative : minutes : 5 +defaultElectricalMeasurementTestToBePerformed ElectricalMeasurementTestToBePerformed ::= full : NULL +defaultIterations Iterations ::= 1 +defaultLoopbackChannel LoopbackChannel ::= b1b2d +defaultLoopbackDuration LoopbackDuration ::= seconds : 500 +defaultLoopbackPosition LoopbackPosition ::= noLoopback +defaultMonitorSpeak MonitorSpeak ::= monitorWithMark +defaultNumberOfDigits NumberOfDigits ::= 1 +defaultRequestedResultType RequestedResultType ::= {passed FALSE, notPassed TRUE, value FALSE} +defaultRing Ring ::= timedRing : 3 +defaultSpmPulses SpmPulses ::= 1 +defaultTestConditions TestConditions ::= {first rejectIfBusy, second noCustomerOverride} +END -- of ASN1LCTTypeModule + +``` + +# 7 Protocol requirements + +Protocol suites for the Q3 interface are specified in Recommendations Q.811 [8] and Q.812 [9]. No specific requirements are identified. + +# ANNEX A + +## Requirements and specification of parameters for access port tests + +It is not mandatory to implement test requirements and functionalities described in this Recommendation, but if any test is required to be managed via the Q3 interface on the NE, it shall be modelled as described in the relevant subclause(s) of this Recommendation. + +### A.1 General test requirements + +These are the general requirements for the test management of access ports via the Q3 interface of an NE. + +#### A.1.1 Scheduled testing + +The Q3 interface provides the functionality to control scheduling of tests in the NE, if the scheduling functionality is implemented in the NE. + +#### A.1.2 Test capability + +Information about which tests the NE is able to perform is required at the Q3 interface. The manager should be able to retrieve information about the test capabilities of an NE. If the OS is requesting the execution of a non-existing test, then the NE shall reply with an error message. + +### A.2 Access port test requirements + +These are the requirements for line and circuit testing of analogue and ISDN subscriber lines managed via the Q3 interface of an NE. + +Further complex test procedures may be operator dependant. These procedures may involve the execution of simple tests or other procedures such as subscriber-assisted tests described in this subclause. + +#### A.2.1 Access port test management functions + +Whenever a test request is sent by the manager to the NE, the following information may be associated to it, as given in Table A.1. + +**Table A.1/Q.835 – Possible test request parameters and values** + +| Parameter | Value | +|---------------------------------|--------------------------------------------------------------------------------------| +| Type of tests and/or procedures | See list of test requirement description | +| Scheduling of test | Start time, stop time | +| ID of access ports under test | List of 1 or N access port object instances involved in the test | +| Type of result | Any conceivable combination among three possible results: passed, not passed, values | + +If one of the parameters is not permitted in the relevant test request, it shall be ignored by the NE. + +If the NE is not able to manage one of the parameters listed above, a notification shall be emitted to the manager indicating the error cause. + +#### A.2.2 Test scheduling + +The following tests are suitable for scheduled tests: + +- foreign voltage and current measurement; +- capacitance measurement; +- insulation resistance measurement; +- all line circuit tests; +- dial tone test; +- loopback test; +- ISDN quick test. + +The following requirements are valid for scheduling: + +- routine tests shall have lower priority than on-demand test and normal traffic; +- the test result shall indicate those ports which have not been tested due to any reason; + +- it shall be possible to specify the start time and the stop time of the whole test sequence; +- it shall be possible to specify the test interval between the start of consecutive test sequences (e.g. daily, weekly). + +The information model for scheduling and test repetition shall be based on already existing models specified in Recommendation X.746 [23]. + +#### **A.2.3 Test result management** + +The result for a test request shall be reported on a per test and per port basis. These reports are controlled by a combination of the following three Boolean conditions: + +- a) pass: if TRUE, send a result report if the port passed the test (the testOutcome field of the additional information parameter of the test result notification in Recommendation X.745 [22] contains the value "pass"); +- b) not passed: if TRUE, send a result report only if the port did not pass the test (in this case the testOutcome field of the additional information parameter of the test result notification in Recommendation X.745 [22] contains one of the following values: "fail", "inconclusive", "timed out" or "premature termination"); +- c) measured values: if TRUE, send the measured values (for these tests producing values as result). + +These Boolean values shall be combined by means of the logical operator AND in order to determine when the result is to be sent. + +EXAMPLE: When the following combination is used: + +``` +pass = FALSE; +not passed = TRUE; +values = TRUE, +``` + +the expected result contains the list of measured values for such ports that have not passed the test. + +#### **A.2.4 Test threshold management** + +When a passed/not passed result is requested, provisionable threshold values are used, unless the test request contains threshold values which override the provisioned thresholds. After the termination of that test, the provisioned thresholds shall be restored. + +Provisionable thresholds are default thresholds for tests which can be modified via the Q3 interface. For each type of test it shall be possible to specify a number of different thresholds. Each of these thresholds shall be assigned to a particular group of thresholds, so-called threshold classes. Access ports may be associated with one of these threshold classes. + +#### **A.2.5 Test requirements description** + +This subclause deals with requirements for line testing purposes. It is subdivided into PSTN line tests and PSTN inward tests: ISDN BA testing and ISDN PRA testing. + +Accuracy and range of measurements are out of the scope of this Recommendation. + +##### **A.2.5.1 PSTN line testing** + +In general, line testing requires that a certain line condition is established (e.g. off-hook or a line termination); then a test is performed and after the test the line is restored to its normal condition. In some cases, not all of these steps are under the control of the Q3 interface (e.g. where the test action is carried out by craft personnel), and so a test function may include all, or only some, of these steps. + +The dry loop test, for example, is concerned only with disconnecting a line from the line circuit. In this case, the actual test conduct and the observation of the test outcome are assumed to be controlled separately. + +In the following, "subscriber assisted" and "voice connection" mean that an operator gives instructions to the subscriber on how to perform a test. The subscriber returns the result back to the operator, when applicable. + +##### **A.2.5.1.1 Foreign voltage or current** + +It is required to check for the presence of foreign voltage or foreign current on the line. + +This test is performed by disconnecting the line from the line circuit and measuring foreign voltage or foreign current between a/b, a/E or b/E. Both AC and DC voltage measurement are required. The manager may select one or more of these measurements. Results shall be: passed, not passed and/or the values. Units are V (Volt) or A (Ampere). + +###### **A.2.5.1.2 Capacitance measurement** + +It is required to measure the capacitance on the line. + +This test is performed by disconnecting the line from the line circuit and measuring the capacitance between a/b, a/E or b/E. The manager may select one or more of these measurements. Results shall be: passed, not passed and/or the values. The unit is F (Farad). + +##### **A.2.5.1.3 Insulation resistance measurement** + +It is required to measure the insulation resistance. + +This test is performed by disconnecting the line from the line circuit and measuring the insulation resistance between a/b, a/Earth, b/Earth, aToBattery or bToBattery (both polarities are possible). The manager may select one or more of these measurements. Results shall be: passed, not passed and/or the values. The unit is $\Omega$ (Ohm). + +##### **A.2.5.1.4 Loop resistance measurement** + +It is required to measure the loop resistance during off-hook. + +The loop resistance between a/b (both polarities are possible) is measured during off-hook. The manager may select one or both measurements. Results shall be: passed, not passed and/or the values. Subscriber assistance may be required. The unit is $\Omega$ (Ohm). + +##### **A.2.5.1.5 Dial pulse test** + +It is required to check the proper operation of the subscriber terminal. + +The subscriber is requested to dial one or more digits: it is required to verify that the correct sequence of dialled digits is received by the NE. Results shall be: passed, not passed and/or the values. The reported values are number of pulses, average make and break duration. + +##### **A.2.5.1.6 DTMF dialling test** + +It is required to check the proper operation of the subscriber terminal. + +The subscriber is requested to dial one or more digits. It is required to verify that the correct sequence of digits is received by the NE in normal operation. DTMF handling is out of the scope of the V5 interface because the tones are carried transparently through the NE and call processing is performed at the NE. However, an NE implementation may have this test functionality, thus providing a common maintenance support for both types of dialling. Results shall be: passed, not + +passed and/or values for dialled digits, tone levels, tone frequencies, pulse length. Units are dBm (decibel relative to 1 milliwatt), Hz (Hertz), s (seconds). + +##### **A.2.5.1.7 Subscriber private meter testing** + +It is required to check the subscriber's private meter. + +The NE sends a specified number of metering pulses to the subscriber. The private meter at the customer premises should then step the same number of pulses. As a result, a comparison is made at the manager between subscriber answer and the notification from the NE about the number of pulses sent. The result parameter is number of pulses. + +##### **A.2.5.1.8 Ring subscriber** + +It is required to check the proper operation of the subscriber terminal. + +The test is carried out by applying the ring signal and checking the answer of the subscriber. When off-hook is detected (both during the ringing tone itself or during the silent interval), no ringing current shall be sent anymore, according to the limits described in Recommendation Q.543 [7]. The digital exchange performance design objectives are: + +- a) <100 ms (mean value); +- b) <150 ms (95% value). + +##### **A.2.5.1.9 Monitoring of the line** + +It is required that the operator may either listen into the line with or without sending a mark tone, or listen and speak. + +###### **A.2.5.1.10 Cable pair identification tone** + +It is required to assist the identification of cable pairs in the field, by generating a trace tone at the NE side. The tone shall continue until it is stopped by a manager command or after a timeout. + +##### **A.2.5.1.11 Dry loop** + +It is required to disconnect the line from the line circuit. This condition is called "dry loop". After a dry loop is established, tests may be performed on the line outside the influence of the Q3 interface, until normal conditions are re-established. + +a and b wires are disconnected from the line circuit, leaving them in an open circuit state. The subscriber line shall remain in dry loop condition until re-connected by a manager command or after a timeout. + +##### **A.2.5.1.12 Register recall button test** + +It is required to check the proper operation of the register recall button of the subscriber terminal. + +The subscriber is requested to press the button. The pulse break time is then checked for acceptability. Results shall be passed/not passed. + +##### **A.2.5.1.13 Ring back procedure** + +The installer at the subscriber site may initiate a test procedure by dialling a special ring back code to the NE. The NE shall then initiate the ring back procedure. If during this procedure line or line circuit tests are required, those already defined in this Recommendation shall be applied. More detailed information on execution of this procedure is contained in Appendix II. + +##### **A.2.5.2 PSTN inward tests** + +###### **A.2.5.2.1 Line circuit testing** + +PSTN line circuit test results shall be reported as passed/not passed covering all circuit tests in a global way, in order to identify the replaceable units. + +If the NE is able to provide the relevant information, the manager may be notified about which test failed and the related measured values. Even if the NE supports this information, the management application still requires a pass/fail (passed/not passed) result. + +In the following, detailed requirements are described. This list is not exhaustive, and new items may be added in the future. + +Thresholds for result comparison are specific to the line card implementation and the manager is not required to manage (both reading and setting) them. + +###### **A.2.5.2.1.1 Feeding voltage** + +Feeding voltage between a and b wires shall be measured. + +###### **A.2.5.2.1.2 Feeding current** + +Feeding current between a and b wires shall be measured. + +###### **A.2.5.2.1.3 Loop and ring trip detection** + +It is checked whether the line circuit is able to detect a loop (i.e. an off-hook) with both normal and reversed polarity, while the line circuit is busy or idle (busy means ongoing call on the line). The ring trip detection is carried out by applying the ring signal and simulating the answer of the subscriber. When off-hook simulation is detected (during the ringing tone itself or during the silent interval), the ringing current shall be stopped immediately, according to the limits described in Recommendation Q.543 [7]: + +- a) <100 ms (mean value); +- b) <150 ms (95% value). + +###### **A.2.5.2.1.4 Ringing current sending** + +The ringing current shall be measured at the line side of the line circuit. + +###### **A.2.5.2.1.5 Private meter pulses** + +The duration and the level of private meter pulses shall be tested. + +###### **A.2.5.2.1.6 Codec testing** + +The analogue-to-digital and the digital-to-analogue conversion shall be tested including hybrid functionality. + +###### **A.2.5.2.1.7 Digit reception** + +The line circuit is tested to check whether it receives a hexadecimal digit. The test shall be performed with both normal and reversal polarities. + +##### **A.2.5.2.2 Other inward tests** + +###### **A.2.5.2.2.1 Dial tone test** + +An off-hook condition is simulated in the NE. It shall be checked whether the dial tone appears at the LC termination or not. + +##### **A.2.5.3 ISDN BA testing** + +###### **A.2.5.3.1 ISDN BA line testing** + +If copper wires are used, the following line tests as defined for PSTN lines shall be carried out: + +- foreign voltage; +- current measurement; +- capacitance measurement; +- insulation resistance measurement (only normal polarity is possible); +- dry loop. + +###### **A.2.5.3.2 ISDN BA line termination testing** + +###### **A.2.5.3.2.1 Loopbacks** + +Generally, a loopback is set up to test the integrity of the devices and the line between two points, by applying a known signal (pattern) on one side and checking whether the signal received is the same as the sent one. The input signal may be applied either by a device embedded in the network element which contains the port (or related line) under test, or by an external equipment. In the latter case, it is required that a loopback is set up without signal generation. + +According to Recommendation M.3603 [5], the terminology for ISDN BA loopbacks is: + +- loopback 1: complete Line Termination (LT) loopback; +- loopback 1A: Regenerator (REG) loopback; +- loopback 2: complete NT1 loopback; +- loopback 21: B1, B2, NT1 loopback. + +The NT1 may be located either within or outside the NE (see Figure 1). + +All the loopbacks mentioned above may be applied in connection with either an NE internal equipment or an external equipment to inject and detect a test pattern. The line under test is activated and a loopback is established. + +The manager shall be notified whether the loopback is set up or not. + +If the pattern injection and detection equipment are under the control of the manager via the Q3 interface, pattern injection and detection shall be initiated after the set-up of the loopback. The pattern may be injected at a particular point and detected either at the same point or at another one. The received pattern shall be compared with the sent one and the result shall be: passed, not passed and/or bit error rate. + +###### **A.2.5.3.2.2 Activation and deactivation of lines** + +It is required to check the capability for activating and deactivating the line under test. + +##### **A.2.5.3.3 ISDN BA line circuit testing** + +###### **A.2.5.3.3.1 Power feed** + +It is required to measure the feeding voltage between a and b wires provided by the line circuit. The voltage between a and b shall be measured in order to verify the proper operation of the power feeding of the NT1. The reported result shall be: passed/not passed. + +##### **A.2.5.4 ISDN PRA testing** + +##### **A.2.5.4.1 ISDN PRA line testing** + +Not applicable. + +##### **A.2.5.4.2 ISDN PRA line termination testing** + +Set-up of loopbacks at the LT (loopback 1) at the regenerator [if more than one regenerator is installed, it shall be the one which is closest to the line termination (loopback 1A)] and at the NT1 (loopback 2) shall be possible. + +According to Recommendation M.3604 [6], the terminology for ISDN PRA loopbacks is: + +- loopback 1: complete Line Termination (LT) loopback; +- loopback 1A: Regenerator (REG) loopback; +- loopback 2: complete NT1 loopback. + +##### **A.2.5.5 ISDN BA and PRA quick tests** + +In order to perform a quick test of the basic functionality of an ISDN BA or PRA, it shall be possible to apply a certain set of tests on the ISDN line. This includes the following tests: + +- layer 1 activation (in case of an ISDN BA: test on the capability to activate the layer 1; in case of an ISDN PRA: test on the presence of an active layer 1); +- loopback test; +- power feeding test; +- function test. + +If the ISDN quick test function is implemented in the NE, it shall be possible to invoke this quick test via the Q3 interface. + +##### **A.2.5.6 Connection of external test systems** + +For external test systems used for line testing, a metallic test access shall be provided to each subscriber line (outbound) and to each line circuit (inbound) of the NE. It shall be possible to connect the test system to the outbound or inbound line and to disconnect it via the Q3 interface of the NE. + +# **ANNEX B** + +## **Test categories** + +This annex specifies the test categories for all tests in a NE which are invoked by the uncontrolled test request as defined in Recommendation X.745 [22]. + +### **B.1 Electrical measurement tests** + +**Test category name:** Electrical Measurement Tests + +**Test category purpose:** The purpose of tests of this category is measurement of electrical parameters. Possible tests according to the ASN.1 definition of electricalMeasurementTest, e.g.: + +- foreign voltage; +- foreign current; +- capacitance; + +- resistance; +- termination; +- feeding voltage; +- feeding current; +- ring. + +**MORT requirements:** The test invocation involves one object class (analogueAccess or accessPortISDNBasicRate as defined in Recommendation Q.824.0 [10]), which represents the access port under test. One or more object instances can be involved in the test. + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this category are outward tests or inward tests. Tests of this category do not require customer assistance. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The electricalMeasurementTestUncontrolledRequest parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** The electricalMeasurementTest-UncontrolledResult parameter as content of the additionalInformation field in the reply syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +### B.2 Dialed digit test + +**Test category name:** Dialed Digit Test + +**Test category purpose:** The purpose of tests of this category is to check the proper operation of the subscriber equipment's (pulse or DTMF) dialling. Possible tests according to the ASN.1 definition of dialledDigitTest, e.g.: + +- dial pulse test; +- DTMF dialling test; +- register recall button test. + +**MORT requirements:** The test invocation involves one object class (analogueAccess as defined in Recommendation Q.824.0 [10]), which represents the line being measured. Only one object instances can be involved in the test. + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this test category are outward tests. Tests of this category require customer assistance. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The dialledDigitTestUncontrolledRequest parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** The dialledDigitTestUncontrolledResult parameter as content of the additionalInformation field in the reply syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +### B.3 Dial tone test + +**Test category name:** Dial Tone Test + +**Test category purpose:** The purpose of tests of this category is to check the ability of the line circuit to detect an off-hook and to check the provision of the dial tone from the NE. Possible tests according to the ASN.1 definition of dialToneTest: + +- dial tone test. + +**MORT requirements:** The test invocation involves one object class (analogueAccess as defined in Recommendation Q.824.0 [10]), which represents the line being measured. One or more object instances can be involved in the test. + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this test category are inward tests. They are performed with disconnected line. Tests of this category do not require customer assistance. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The dialToneTestUncontrolledRequest parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** The dialToneTestUncontrolledResult parameter as content of the additionalInformation field in the reply syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +### B.4 Subscriber private meter pulses test + +**Test category name:** SPM Pulses Test + +**Test category purpose:** The purpose of tests of this category is to check the cable and equipment in the customer's premises by sending SPM pulses to the private meter of the subscriber. Possible tests according to the ASN.1 definition of spmPulses test: + +- subscriber private meter testing. + +**MORT requirements:** The test invocation involves one object class (analogueAccess as defined in Recommendation Q.824.0 [10]), which represents the line being measured. One or more object instances can be involved in the test. + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this test category are outward tests. They are performed with the line connected to the line circuit or with disconnected line. Tests of this category either require customer assistance or assist an operator's craftsman in detecting an error in the field. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The spmPulsesTestUncontrolledRequest parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** None. + +### **B.5 Ringing test** + +**Test category name:** Ringing Test + +**Test category purpose:** The purpose of tests of this category is to check the cable and equipment in the customer's premises by applying ringing to the subscriber. Possible tests according to the ASN.1 definition of ringing test: + +- ringing test. + +**MORT requirements:** The test invocation involves one object class (analogueAccess as defined in Recommendation Q.824.0 [10]) which represents the line being measured. One or more object instances can be involved in the test; + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this test category are outward tests. They are performed with the line connected to the line circuit or with disconnected line. Tests of this category either require customer assistance or assist an operator's craftsman in detecting an error in the field. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The ringingTestUncontrolledRequest parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** None. + +### **B.6 Test to line circuit** + +**Test category name:** Test To Line Circuit + +**Test category purpose:** The purpose of tests of this category is to check the ability of the inward test to provide or detect certain signals or feeding voltage. The test comprises of a set of possible tests, which are predefined in the NE and performed all together, e.g.: + +- feeding voltage; +- feeding current; +- loop detection and ring trip detection; +- ringing current sending; +- private meter pulse generator test; + +- Codec testing; +- digit reception. + +**MORT requirements:** The test invocation involves one object class (analogueAccess or accessPortISDNBasicRate as defined in Recommendation Q.824.0 [10]), as under test, which represents the line being measured. One or more object instances can be involved in the test. + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this test category are inward tests. They are performed with disconnected line. Tests of this category do not require customer assistance. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The testToLineCircuitUncontrolledRequest parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** The testToLineCircuitUncontrolledResult parameter as content of the additionalInformation field in the reply syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +### B.7 ISDN loopback test + +**Test category name:** ISDN Loopback Test + +**Test category purpose:** The purpose of tests of this category is to perform an internal loop test for ISDN basic or primary rate accesses. Possible tests according to the ASN.1 definition of iSDNLoopTest: + +- loopback test. + +**MORT requirements:** The test invocation involves one object class (accessPortISDNBasicRate or accessPortISDNPrimaryRate as defined in Recommendation Q.824.0 [10]), which represents the line being measured. One or more object instances can be involved in the test. + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this test category are outward tests. Tests of this category do not require customer assistance. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The loopBackTestUncontrolledRequest parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** The loopBackTestUncontrolledResult parameter as content of the additionalInformation field in the reply syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +### B.8 ISDN quick test + +**Test category name:** ISDN Quick Test + +**Test category purpose:** The purpose of tests of this category is to check the proper operation of certain functionalities of the subscriber equipment. Possible tests according to the ASN.1 definition `IsdnQuickTestUncontrolledRequestType` are: + +- layer 1 activation (in case of an ISDN BA: test on the capability to activate the layer 1; in case of an ISDN PRA: test on the presence of an active layer 1) +- loopback test +- power feeding test +- function test + +**MORT requirements:** The test invocation involves one object class (`accessPortISDNBasicRate` or `accessPortISDNPrimaryRate` as defined in Recommendation Q.824.0 [10]), which represents the line being tested. One or more object instances can be involved in the test. + +**Associated object requirements:** There are no associated object classes. + +**Test environment:** Tests of this test category are outward and inward tests. They do not require customer assistance. + +**Test request service type:** "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Specific errors:** + +- "ITU-T Recommendation X.745:1993":noSuchMORT; +- "ITU-T Recommendation X.745:1993":mORTNotAvailable; +- "ITU-T Recommendation X.745:1993":mistypedTestCategoryInformation. + +**Test category information parameter:** The `isdnQuickTestUncontrolledRequest` parameter as content of the test category information field in the information syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction. + +**Uncontrolled test response additional information parameter:** The `isdnQuickTestUncontrolledResult` parameter as content of the `additionalInformation` field in the reply syntax of "ITU-T Recommendation X.745:1993":testRequestUncontrolledAction + +# ANNEX C + +## Test termination + +As specified in Recommendation X.745 [22], a test may terminate spontaneously or by request. In the following subclauses, guidelines are given on termination of line and circuit tests. + +### C.1 Termination of uncontrolled tests + +Uncontrolled tests terminate spontaneously: + +- upon completion of the test; or +- upon fault situations; or +- upon the fulfilment of predefined criteria. + +These predefined criteria and some specific fault situations are specified by the test category. The final test results or test failure response shall be returned using the test request uncontrolled action response message. + +### **C.2 Termination of controlled tests** + +Controlled tests shall terminate depending on the test invocation: + +#### **C.2.1 One-step test** + +A one-step test is specified by one or more tests being invoked by a single test request controlled action. The request specifies a new access test object together with the test object(s) representing the specific test(s) to be performed. + +A one-step test shall terminate spontaneously: + +- upon completion of the test; or +- upon fault situations; or +- upon the fulfilment of predefined criteria. + +These predefined criteria and some specific fault situations shall be specified by the test category or TO class. The final test results shall be returned using one or more controlled test result notifications. A test failure response shall be returned in the test request controlled action response or be contained in result notifications. + +Before completion of the requested tests, a one-step test may be terminated by a test terminate action directed to the test action performer which received the test request. The tests are identified in termination requests using the test invocation id. All TO(s) identified by the test shall be terminated; otherwise, an error shall be returned. The tests that have been terminated successfully as a result of this termination request shall be returned in the action response. In case an error occurs during test termination, the agent shall respond with a test termination error. + +#### **C.2.2 Test session** + +A test session is invoked by a test request controlled action which specifies a new access test object without any contained specific test objects. Subsequently, one or more other test requests are given which specify the specific tests to be performed within the already existing test session. + +Test sessions shall be terminated by a test terminate action directed to the test action performer which received the test request. Test sessions may terminate spontaneously in case of fault situations or due to a time out specified in the test request. In case specific tests represented by contained test objects are invoked for this test session, these tests shall also be terminated. Test sessions are identified in termination requests using the test session id or the corresponding list of test invocation id(s). If a test session id is provided in the termination request, test invocations identified by the session shall be terminated in a best effort fashion. If a test invocation id is provided in the termination request, all TO(s) identified by the test shall be terminated; otherwise, an error shall be returned. In the response to the termination request, the list of all test invocations that have been terminated as a result of this request shall be returned. + +Specific controlled tests invoked during a test session shall terminate spontaneously or may be terminated by a test terminate action before completion of the test. Requirements are the same as for one-step tests. + +#### **C.2.3 Aborting tests** + +Controlled tests may also be aborted by deleting all TO(s) related by the same test invocation identifier. Test objects accepting deletion requests shall not emit any further test result reports. Where available it is recommended that the Scope parameter include all TOs with the same Test invocation identifier and that the Filter parameter select TOs with the same Test invocation identifier. If an abort request results in the deletion of some, but not all, TOs with the same test invocation identifier, the test becomes indeterminate. In this case, it is recommended to terminate the + +test by subsequent attempts to delete the surviving test objects. Yet, it may depend on the specific implementation how to resolve this situation. + +#### **C.2.4 Termination sequence** + +When a controlled test or test session is terminated, the TO(s) of the test or test session will execute a termination sequence which may include issuing test result reports and performing any necessary clean-up including ending the test activity of MORT(s) and associated object(s). Successfully terminating a test or a test session implies that all the TO(s) of the test or test session are deleted automatically. If a result report is issued and the test outcome has not been concluded, then the test outcome shall indicate a value of premature termination. The temporal order in which the termination sequence(s) are carried out is system specific and not defined by the test. + +# **ANNEX D** + +## **Test result notification** + +As specified in Recommendation X.745 [22], test results of controlled tests may be emitted as notifications from the TO. The results are provided by one or more notifications. + +- 1) A result notification shall contain the test invocation identifier of the test. +- 2) If present in the test request, the test session identifier and the associated object identifier shall also be present in the result notification. They may be used for the correlation of test results. +- 3) The additional information identifier shall be present in the notification if specified in the behaviour of a specific test. +- 4) The MORTs identifier shall be present if not included in the test-specific additional information field. +- 5) The test outcome parameter shall be included in the result notification to indicate the completion of a test. In case a TO is sending more than one test result notification during the execution of a test, then the test outcome parameter also indicates that the TO is sending no more reports for the execution of the test. The parameter shall not be included in intermediate result notifications. It may take one of the following values: pass, fail, inconclusive, timed-out or premature termination, indicating the overall outcome of the test. In addition, notifications may contain specific test outcome information pertinent to the type of test. + +The use of further generic information of the test result notification is left up to the implementation. + +# ANNEX E + +## Additional requirements on the test action performer + +This annex contains additional requirements on the implementation of the test action performer which detail the generic capabilities specified in Recommendation X.745 [22]. + +### E.1 Indication of supported tests + +It shall be possible to retrieve the line and circuit test capabilities of an agent system. For this purpose the testActionPerformer object class specified in Recommendation X.745 [22] shall support the following packages: + +- supportedTOClassesPackage, if controlled tests are supported; and +- supportedUncontrolledTestsPackage, if uncontrolled tests are supported. + +Supported controlled tests are identified by a set of object identifiers of their related TO classes. Supported uncontrolled tests are identified by a set of object identifiers of their respective uncontrolled request parameter. + +On receipt of a test request indicating a controlled test not supported by the agent system, an independent or related test invocation error shall be generated. On receipt of a test request indicating a not supported uncontrolled test, a mistyped test category information error shall be generated in the agent system. + +### E.2 Indication of unsuccessful test requests + +The response to a not successful line or circuit test request shall contain a failure indication and information pertaining to the failure. According to Recommendation X.745 [22], these failures shall be reported as Specific Errors. + +# ANNEX F + +## Requirements and specification of parameters for V5 interface tests + +### F.1 V5 interface test requirements + +These are the requirements for the test management of V5 interfaces via the Q3 interface at either side of a V5 interface. They are covered by the information model defined in this Recommendation. + +#### F.1.1 V5 interface ID testing + +The testing of consistency between the V5 interface IDs at either side of a V5 interface is required. + +#### F.1.2 Link ID testing + +The testing of consistency between the link IDs at either side of a V5 2048 kbit/s link is required. + +#### F.1.3 Provisioning variant testing + +The testing of consistency between the provisioning variant labels at either side of a V5 interface is required. + +# APPENDIX I + +## Message flows + +In Figures I.1 to I.5 the principles of the message flows are introduced as examples. + +![Sequence diagrams for successful on-demand tests: controlled and uncontrolled actions.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +The diagram shows two sequence diagrams between a Manager and an Agent, separated by the word "or". + +**Top Diagram (Controlled Action):** + +- Manager sends `testRequestControlledAction` to Agent. +- Agent sends `TO(s)` to Manager. +- Agent sends `Test object instance(s) created` (as a note). +- Agent sends `action confirmation` to Manager. +- Agent sends `testResultNotification(s)` to Manager. +- Agent sends `testOutcome 'pass'` to Manager. + +**Bottom Diagram (Uncontrolled Action):** + +- Manager sends `testRequestUncontrolledAction` to Agent. +- Agent sends `test categories` to Manager. +- Agent sends `No test object instances created` (as a note). +- Agent sends `action confirmation(s)` to Manager. +- Agent sends `testOutcome 'pass'` to Manager. + +T0409890-98 + +Sequence diagrams for successful on-demand tests: controlled and uncontrolled actions. + +**Figure I.1/Q.835 – The simple cases: a successful on-demand test** + +![Sequence diagrams for failed tests: negative and positive action confirmations.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +The diagram shows two sequence diagrams between a Manager and an Agent, separated by the word "or". + +**Top Diagram (Negative Confirmation):** + +- Manager sends `testRequestControlledAction` to Agent. +- Agent sends `TO(s)` to Manager. +- Agent sends `negative action confirmation` to Manager. + +**Bottom Diagram (Positive Confirmation):** + +- Manager sends `testRequestControlledAction` to Agent. +- Agent sends `TO(s)` to Manager. +- Agent sends `positive action confirmation` to Manager. +- Agent sends `testResultNotification` to Manager. +- Agent sends `testOutcome not 'pass'` to Manager. + +T0409900-98 + +Sequence diagrams for failed tests: negative and positive action confirmations. + +**Figure I.2/Q.835 – Any failed test** + +![Sequence diagram for a test session between Manager and Agent.](af6c3f383ddc0c142cdd7e186cc78199_img.jpg) + +``` + +sequenceDiagram + participant Manager + participant Agent + Manager->>Agent: testRequestControlledAction +testSessionId A, TO(s) + Note right of Agent: Test mechanism of NE reserved for this testing session (impl. spec.) + Agent->>Manager: action confirmation + Agent->>Manager: testResultNotification(s) + Note right of Agent: accessTest and other test object instance(s) created, test(s) performed + Note right of Agent: Test object instance(s) deleted + Manager->>Agent: testRequestControlledAction +testSessionId A, TO(s) + Note right of Agent: Additional test object instance(s) created, test(s) performed + Agent->>Manager: action confirmation + Agent->>Manager: testResultNotification(s) + Note right of Agent: Test object instance(s) deleted + Manager->>Agent: testTerminateAction + Note right of Agent: accessTest instance deleted, test mechanism freed (impl. spec.) + Agent->>Manager: action confirmation + +``` + +T0409910-98 + +Sequence diagram for a test session between Manager and Agent. + +**Figure I.3/Q.835 – A test session** + +![Sequence diagram for internal pattern injection between Manager and Agent.](e2b7490a3455c66c85db12872c78fcc3_img.jpg) + +``` + +sequenceDiagram + participant Manager + participant Agent + Manager->>Agent: testRequestControlledAction +loopTest+patternTest TOs + Note right of Agent: Create loopTest and patternTest instances + Agent->>Manager: action confirmation + Note right of Agent: Duration + Manager->>Agent: M-GET patternTestResult + Agent->>Manager: M-GET Result + Manager->>Agent: testTerminateAction + Agent->>Manager: action confirmation + +``` + +T0409920-98 + +Sequence diagram for internal pattern injection between Manager and Agent. + +**Figure I.4/Q.835 – Internal pattern injection** + +![Two sequence diagrams showing external pattern injection between a Manager and an Agent. The top diagram shows a testRequestControlledAction with a loopTest, followed by an action confirmation, then a testResultNotification with a timeout and loopbackOverride. The bottom diagram shows a testRequestControlledAction with a loopTest, followed by an action confirmation, then a testTerminateAction, and finally an action confirmation. Both diagrams include annotations for 'Create loopTest instance', 'Duration', and 'Delete loopTest instance'.](6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg) + +``` + +sequenceDiagram + participant Manager + participant Agent + + Manager->>Agent: testRequestControlledAction + Note over Agent: Create loopTest instance + Agent-->>Manager: action confirmation + Note over Agent: Duration + Manager->>Agent: testResultNotification + Note over Agent: Delete loopTest instance + Note over Agent: timeout loopbackOverride + + or + + Manager->>Agent: testRequestControlledAction + Note over Agent: Create loopTest instance + Agent-->>Manager: action confirmation + Note over Agent: Duration + Manager->>Agent: testTerminateAction + Note over Agent: Delete loopTest instance + Agent-->>Manager: action confirmation + +``` + +T0409930-98 + +Two sequence diagrams showing external pattern injection between a Manager and an Agent. The top diagram shows a testRequestControlledAction with a loopTest, followed by an action confirmation, then a testResultNotification with a timeout and loopbackOverride. The bottom diagram shows a testRequestControlledAction with a loopTest, followed by an action confirmation, then a testTerminateAction, and finally an action confirmation. Both diagrams include annotations for 'Create loopTest instance', 'Duration', and 'Delete loopTest instance'. + +**Figure I.5/Q.835 – External pattern injection** + +# APPENDIX II + +## Description of test procedures – Application for V5 access networks + +## II.1 Background + +This appendix describes complex test procedures, as ringback service and all subscriber-assisted tests at the AN side, to show the impact that they have on both Q3 interfaces. + +## II.2 Test procedures scenario + +The general scenario (Figure II.1) includes four functional blocks and all reference points between them as described in Recommendation M.3010 [3]. + +The functional blocks are: NE functionalities which represent LE and AN, and OS functionalities managing AN and LE. + +The reference points are: q (between AN or LE and respective OS) and q (or x if they belong to different TMNs) between OSs1. + +1 This reference point and the interface relating to it are out of the scope of this Recommendation. + +![Functional architecture diagram for test procedures showing four entities: two OSF (Operation Support Functions) at the top and two NEF (Network Element Functions) at the bottom. The left OSF is connected to the left NEF by a dashed line labeled 'q'. The right OSF is connected to the right NEF by a dashed line labeled 'q'. The two OSF entities are connected to each other by a dashed line labeled 'q (or x)'. The two NEF entities are connected to each other by a solid line. Below the diagram is the reference number T0409940-98.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +Functional architecture diagram for test procedures showing four entities: two OSF (Operation Support Functions) at the top and two NEF (Network Element Functions) at the bottom. The left OSF is connected to the left NEF by a dashed line labeled 'q'. The right OSF is connected to the right NEF by a dashed line labeled 'q'. The two OSF entities are connected to each other by a dashed line labeled 'q (or x)'. The two NEF entities are connected to each other by a solid line. Below the diagram is the reference number T0409940-98. + +**Figure II.1/Q.835 – Functional architecture for test procedures** + +The following subclauses describe examples of test procedures and the interactions between functional blocks via reference points. + +### II.2.1 Scenario for faultsman ringback tests in an AN environment + +Figure II.2 gives a synopsis of all elements involved in maintenance of an AN subscriber line and set: in this example, all the previous reference points have been translated to interfaces and the OSs belong to different TMNs. The telephone set located at the AN operator premises will not be used for this scenario as the operator at the subscriber location will only get responses from the system: + +- 1) The operator at the subscriber location (installer) dials a special service code. This special code is detected at the LE over the V5 interface (③ in Figure II.2): + - a) the LE notifies the OSLE via the Q3LE interface (⑤ in Figure II.2); + - b) the OSLE "informs" OSAN via the X interface (⑥ in Figure II.2); + - c) OSAN checks via Q3AN if Test Equipment is available at AN level and reserves this equipment (④ in Figure II.2). + - d) reporting back from OSAN to OSLE via X interface (⑥ in Figure II.2). + - e) OSLE initiates tone LE via Q3LE (⑤ in Figure II.2). +- 2) If test equipment is available, the LE answers with a ringing tone (③ in Figure II.2), otherwise with a busy tone (③ in Figure II.2). +- 3) The installer puts the set on-hook (③ in Figure II.2): + - a) the LE notifies the OSLE via the Q3LE interface of the on-hook (⑤ in Figure II.2); + - b) the OSLE "informs" OSAN via the X interface (⑥ in Figure II.2); + - c) OSAN requests testing at AN level via Q3AN (④ in Figure II.2); + - d) the AN blocks the related user port object instance via the V5 protocol (③ in Figure II.2). +- 4) Automatic testing is performed by the AN (foreign voltage, insulation, capacitance, etc.): + - a) the AN notifies the test results via Q3AN to OSAN (④ in Figure II.2); + - b) the test equipment is disconnected at the AN; + - c) reporting back the passed/not passed result from OSAN to OSLE via X interface (⑥ in Figure II.2); + - d) OSLE initiates ringing to LE via Q3LE (⑤ in Figure II.2) and indicates which tone to apply. + +- 5) The LE rings the installer back. +- 6) The installer takes the set off-hook (implying the ringer is OK). +- 7) The test results (of item 4 above) are communicated with a tone (passed: dial tone, not passed: busy tone) to the installer (③ in Figure II.2). +- 8) Faultsman receives dial tone and sends digits (DTMF or DECADIC) in a given order, removal of dial tone after first digit (③ in Figure II.2). This is just a check of the capability to dial (i.e. no measurements are performed on the dial performance). +- 9) Passed/not passed tone to report a successful test (③ in Figure II.2). +- 10) End of test, set on-hook: + - a) the LE notifies the OSLE via the Q3LE interface of the on-hook and successful test (⑤ in Figure II.2); + - b) the OSLE "informs" OSAN via the X interface (⑥ in Figure II.2); + - c) report is printed on the AN operator printer (⑦ in Figure II.2). + +![Physical architecture diagram for faultsman ringback service and subscriber-assisted tests in an AN environment.](638a308af25f1f56b4456a1fc503f161_img.jpg) + +The diagram illustrates the physical architecture for faultsman ringback service and subscriber-assisted tests in an AN environment. It shows the following components and connections: + +- Access Network operator:** Enclosed in a dashed oval, it contains a telephone set and a computer. It is connected to the OSAN block via a line labeled ②. +- OSAN (Access Network Operator System):** A central block that receives input from the Access Network operator (②) and the AN (④). It is connected to OSLE via the X interface (⑥). +- AN (Access Network):** Contains a telephone set and a 'Test equipment' block. It is connected to the Access Network operator (①) and OSAN (④). It is connected to the LE via the V5 interface (③). +- OSLE (Local Exchange Operator System):** Connected to OSAN via the X interface (⑥) and to the LE via the Q3LE interface (⑤). +- LE (Local Exchange):** Connected to the AN via the V5 interface (③) and to OSLE via the Q3LE interface (⑤). + +Numbered circles (① through ⑦) indicate specific connection points or interfaces as defined in the text. + +Physical architecture diagram for faultsman ringback service and subscriber-assisted tests in an AN environment. + +T0409950-98 + +NOTE – The operator's telephone set may also be connected to another AN, or to this or another LE. + +**Figure II.2/Q.835 – Physical architecture for the faultsman ringback service and for subscriber-assisted tests in an AN environment** + +### II.2.2 Scenario for a subscriber-assisted test in an AN environment + +The subscriber-assisted tests, i.e. those in which the subscriber at its premises handles the telephone set and observes the SPM, are normally carried out with a speech connection between him and the operator who is also working at the OSAN. This speech connection can be in two modes, as specified in the voice access package. + +#### II.2.2.1 Existing connection mode + +- 1) A normal connection is set up between the subscriber and the operator. This connection can be, for example, due to a claiming call from the subscriber (①-③-② in Figure II.2) (no charging should be applied) or may be originated by the operator (②-③-① in Figure II.2). +The operator indicates to the subscriber that some tests are going to be performed, and requests assistance for this purpose according to the following instructions. +- 2) The operator, by means of a test request on the Q3AN interface (⑦-④ in Figure II.2), converts the existing voice connection into a test connection (by creating an access test object and a voice access test object contained in it with the monitorSpeak parameter set to existingConnection). The test connection condition means that the voice connection is kept (①-③-②) but the line signalling is put under the control of the OSAN interface instead of the LE, which will not receive any V5 signal message. +- 3) If, for example, the ringing function of the telephone set has to be tested, the operator asks the subscriber to hang up and to pick up again when the set rings (or after a given time otherwise). The on-hook is noticed by the operator by listening to the line (or by previously creating within the access test object a dialled digit test object which reports the on-hook signal event through the Q3AN interface). +Then the operator creates within the access test object a ringing test object. This causes the AN to generate ringing to the subscriber's line. The test object will generate a result either upon the off-hook detection or when a built-in timer expires (e.g. a little before the subscriber should pick up if the ringing does not work). In both cases the ringing test object is automatically deleted. +- 4) If, for example, the dialling function of the telephone set has to be tested, the operator creates within the access test object a dialled digit test object and then asks the subscriber to dial a given sequence of digits. Information on detected digits at the AN and their performance (e.g. make/break duration) are reported by the test object to the OSAN where the operator checks it. The dialled digit test object is automatically deleted. +- 5) If, for example, the SPM pulse reception function has to be tested, the operator asks the subscriber to watch how many pulses are going to be received, then creates within the access test an SPM pulse test object with the desired number of pulses to be sent as a parameter. This causes the generation of those pulses. The subscriber counts the number of pulses accumulated in the SPM and it is checked against the generated number. +- 6) When no more subscriber-assisted testing is needed, the operator terminates the voice access test object and the access test object through the Q3AN interface. An implementation may restore the original normal connection condition (voice connection kept and line signalling again under LE control) or release the connection completely. + +#### II.2.2.2 Parallel voice path mode + +- 1) The operator creates through the Q3AN interface (⑦-④ in Figure II.2) an access test object and contained in it a voice access test object with the monitorSpeak parameter set to speakAndMonitor. This causes the AN to block the port (③ in Figure II.2) and to generate a call from the AN-internal test function (simulating to be a telephone) to the telephone number of the operator, provided in the ringBackNo parameter of the test request (③-② in Figure II.2, though the V5 interface and the LE for the test function may not be the same as for the port to be tested). +- 2) Once the voice path between the operator and the test function is established, the test function is connected to the subscriber's line so that the operator and the subscriber can speak to each other. + +3), 4) and 5) as in the existing connection mode above. + +- 6) When no more subscriber-assisted testing is needed, the operator terminates the voice access test object and the access test object through the Q3AN interface. The user port is unblocked (③ in Figure II.2) and gets ready for normal traffic. + +# APPENDIX III + +## State management in relation with line testing – Application for V5 access networks + +## III.1 Intrusive tests + +Tests can be intrusive or non-intrusive. A test on a resource is intrusive when its testing phase is incompatible with the normal working of that resource. + +Most of the test functionality modelled in this Recommendation is intrusive, the only exceptions being that of the monitoring function and of the monitor-and-speak function while a previous connection between the user port being tested and a third party is still on (if this connection is cleared, then the monitor-and-speak function becomes intrusive). + +Additionally, any tests performed during a speech connection between the operator and the user in the "existingConnection" mode (as described in the voiceAccessTest object) are not considered as intrusive. + +## III.2 Dealing with conflicts between intrusive tests and normal service + +When a resource is disabled for any reason, it cannot provide its normal service and thus there is no conflict with intrusive tests. For V5-related user ports, the disabled state of the object implies the blocked state of the corresponding V5 FSM. Disabling reasons are AN-internal, e.g. faults or a (V5-specific) blocking procedure initiated at the LE, as specified in Recommendation Q.824.5 [11]. + +When a resource is not disabled, a way of avoiding conflicts between intrusive testing on that resource and its normal working is by preventing the latter by setting its administrative state to "locked" (via shutting down, if desired). This state also allows the holding of a test session without risk of interruption due to call attempts between consecutive tests. With V5-related user ports, the locked state implies that the V5 FSM is blocked (see Recommendation Q.824.5 [11]). + +However, the locking or shutting down and the subsequent unlocking operations on the Q3 interface may be cumbersome, e.g. in the case of series of single tests on many user ports, and for this reason the model allows to avoid them. In this case, the AN shall solve interferences between an intrusive test and normal traffic according to the priority criterion defined in the testConditions parameter of the request for the containing access test. As specified in the object model, tests to be initiated when the port is not idle may have to be rejected ("reject if busy"), or wait until the port becomes idle ("wait if busy", with a time limit set by the waitTime parameter), or force the clearance of the call ("test if busy"). + +NOTE 1 – A test session without call interruptions between tests can be supported, without using the locked administrative state, by means of the access test object along with the testSessionId parameter. + +NOTE 2 – The above approach of using the administrative state does not cover the "reject if busy" case or the timing facility for the "wait if busy" case. + +In order for the AN to appropriately use the testConditions and the waitTime parameters, two functions are necessary: + +- 1) capability to know whether there is an ongoing call; +- 2) procedures for the possible cases of interference. + +Regarding function 1, the general principles for ANs and in particular the V5 specifications state that the AN has limited or no knowledge of the state of the call. On that basis, there are two ways out: + +- a) for V5-related user ports, an approach is the use of the V5 blocking mechanisms. They only indirectly provide some call information, but at the same time cover function 2 (they are active procedures), as explained in III.4; +- b) it is possible for an AN to have additional capabilities allowing it to get call state information, if an implementation goes beyond the definition of AN in the V5 specification. + +This approach has the disadvantage of making the AN more complex and dependent on possibly network-specific and time-evolving signalling issues, against the spirit of the V5 specification. However, it cannot be ruled out, and for that reason the V5 blocking approach described below is not in the normative part of this Recommendation. Moreover, keeping independence on the V5 specificities allows the model to be used in non-V5 environments. + +Regarding function 2, in the case of a user port related to a V5 interface, the normal way is by means of the V5 blocking mechanisms, even if a different approach is used for function 1. + +A second aspect of possible interference between service and testing is when a call attempt occurs during the execution of a test. The testConditions parameter may also be used by the manager to choose which function prevails, as described in the model. The "customer overrides" option, which is not possible if the locked administrative state is used, requires the AN to be able to detect the call attempt, as well as procedures to abort the test, and for this aspect the same considerations above are valid. + +## **III.3 State values during intrusive testing** + +Whenever the user port is in the testing phase of an intrusive test, it cannot give normal service. Thus, the testing phase of an intrusive test is an AN-internal disabling reason, i.e. one of the possible reasons for its disabled operational state. + +For short tests, this general rule may be simplified so that the Q3 interface state attributes of the user port are not affected, thus avoiding the corresponding notifications and manager processing. This means that during the test execution the disabled condition of the port is only known by the AN. + +For V5-related user ports, the disabled condition (even if not reflected on the Q3 interface) means the blocked state of the V5 FSM, as defined in Recommendation Q.824.5 [11]. Exceptions are or may be: + +- the dial tone test requires the unblocked state due to its special nature; +- for other tests, if their execution have a very short duration, an implementation might not follow this rule. + +## **III.4 V5 blocking mechanism** + +This subclause describes the use of the V5 blocking mechanism for V5-related user ports to cover functions 1 and 2 (as described in III.2) as a complement of the generic behaviour description of the test environment conditions package. + +- If the testConditions parameter is set to "test if busy", the V5 urgent blocking procedure is started so that the test proceeds (as far as this mechanism is concerned, the AN does not know if there was a call). +- If the parameter is set to "wait if busy", the V5 deferred blocking is started, and it is up to the LE to block the port (when this happens, the AN "knows" that the call has finished). If the timer expires, the AN cancels the block request. + +- The least elegant case for this approach is when the testConditions parameter is set to "reject if busy", as there is no direct V5 mechanism. Then the AN starts the deferred blocking procedure; if after "a few seconds" the LE has not yet confirmed the blocking, the AN assumes that there is a call and rejects the test, while the block request to the LE is cancelled. + +For the dial tone test, these procedures need to be complemented, once the port is blocked, by the unblocking procedure (if the concept of test session were to be supported to avoid a call to interrupt a sequence of dial tone tests, the user port would be immediately blocked after each test). + +It is possible for an implementation to follow the above V5 blocking approach with the variation that, for PSTN ports and/or ISDN-BA ports without permanent line activation, the AN determines by itself whether the line is busy, only in order to simplify the "reject if busy" case (direct rejection if the port is found busy); and, on PSTN ports, also to simplify the dial tone test (direct testing when the port is found idle). + +# APPENDIX IV + +## Bibliography + +- CCITT Recommendation I.601 (1988), *General maintenance principles of ISDN subscriber access and subscriber installation*. +- CCITT Recommendation X.722 (1992) | ISO/IEC 10165-4:1992, *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects*. +- CCITT Recommendation X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function*. + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure 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.86.7-199510-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed8768d24658cb6067c13042991645cb01f9b751 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db89d66963be4f678da8b4daff67641d2554bbc2d701ea689d438edd0df70a4d +size 47743 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e15dd05712b20b7cb4d7bba992759ee1871f3500 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c95396ccbb72007cd5c07b52b35070b7f5fee753e204f0fa518eed8e76e12a74 +size 45665 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c86148de9e0ad110b8cde01544a06206fc19ab73 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:949f83e9f2c150810039a0e1f5a4fe79b812afd7d7c3be597597bc45c57c465d +size 60784 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5326c67ebdb7a8e845c53287972377baaafda807 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcf6d27cf4efdd17e708125698aee6146713c2cdac94a845f3f08ab13805d9f2 +size 51834 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16b4c9eaa4470c4cf57b97788b391bc369861e2d --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:710a66af0c7657eeab0d248dec52a44bae92942be1c78bd86bfa1f8e6197536e +size 15839 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1af40a593f8091664fd9d06d8537a7a102c0fc3 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:882f3ce20fe82e8df6b65efe94f21e47f6089f803675c75e2082bec54decb59c +size 40772 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c032e895100fcda13e757dec95f82cb1dc1d54c --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f39e49c4db99e410ca59bf99f5f7dcaf172f51ef39fe3e207375a0f81d1f9dda +size 8400 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dcc675af6a405da83485ca411c0d608e8a14cea --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ab6512d668ac6c0f16cdc9ea1481f9745d6f49157840f167adcab4036665d86 +size 43967 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69e076a8bfeae17d3d48b208303bd39192a93b96 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50777f16d8af04bb67a0b87517f48ca89d94885b26336b225cbad7e1d4f9fc3a +size 115819 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0637a49d217a12051f9b30242f867312fa2976cc --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09d2fc52eeb24355dd5c179d4fe96eeb68b9c2c21deef529a82e3a13826ee979 +size 26965 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..333e767ec8bcf40b71d9cabcada2ca6896ed96ca --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90c9a1d9fef13953b0cf51ae2c4e24737dd3c581e6a9c1899fc3a5d6000e16b2 +size 71989 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86d30a44ea691a59be96276f500a6332a60fb87b --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5c1ec02ac1239d0e536358f240876d5abd29298127c76a55cb3723591c92145 +size 27900 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbfb4fe31799603c1cf6008853c986ac9a69d914 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:644449d2e5059ce3d975f608b0c064bd783ba58308b3c8e307dbb06090e35c8c +size 17758 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c187795c1f4cdb4720a083a4c39b23ce2f09d75 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97187188a013e6d1247ba8860f859afe262dfd75807507be6900bdad9ed81e6d +size 35860 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44973ccae8df055217870ec43d42658b19d317ab --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5a20b571f5c2ceafd438c88d27a7f026d66a200f9f799cce2e636644376cc7d +size 57387 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c64866d174a6023a69693dd7eb67a4a81aedea30 --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdf425f00815cff56648f80230ee193a8cba3ce664f0bdf678c9daceebf18a1c +size 24067 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c086628fbcb0cfa6f6e6f39be9a24b6797a452aa --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9823394e44d1ff62ad1e5aacc656a5f7a5cbc9031c92a17b1409a7277addcb5f +size 18018 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04eaf9c9ee9661f1b30496020d590ca27c05d03f --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:caf05907c5053efca74962a144d806023e66757f4f418ac895eb38c8b58c37a0 +size 103902 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab8e7be711cdea270032b5f9fe6f391c7899ebce --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e74b99329a01425b2a35d23f7a7360d647e8742d48dcea890bce5d2131c77ac5 +size 83715 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a704619135b5fc52545db21b7b34a5b647e607aa --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe2667bdb7ffbd20c02b9718bbfa2fc3b5b603443b9232effc57700cf7e8fba1 +size 100162 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..754ea5e3be51ea14c0e6343dd0d7f48156bb831d --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98908542d9eed50604800a46013b47c79cd024dc4c0fcc8dc9a5bf089b549295 +size 73470 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61b35cc9175975f0a2b386b656621e103927d96f --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef460497ba95fb8fc5f473b93956b5742029c690df37ccefb62d8b14b1ca648d +size 66861 diff --git a/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/raw.md b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..847ad7ac7fc24452316ef77db2d8fbd32bbe8bae --- /dev/null +++ b/marked/Q/T-REC-Q.86.7-199510-I_PDF-E/raw.md @@ -0,0 +1,1495 @@ + + +![ITU logo: a globe with the letters ITU and a lightning bolt symbol.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: a globe with the letters ITU and a lightning bolt symbol. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.86 + +(10/95) + +# **GENERAL RECOMMENDATIONS ON TELEPHONE SWITCHING AND SIGNALLING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN** --- + +## **STAGE 2 DESCRIPTION FOR CHARGING SUPPLEMENTARY SERVICES** + +## **CLAUSE 7 – INTERNATIONAL TELECOMMUNICATION CHARGE CARD (ITCC)** + +### **ITU-T Recommendation Q.86** + +(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.86, clause 7 was revised by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. + +## --- NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +© ITU 1996 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|--------------------------------------------------------------------------------------------|-------------| +| 7 International Telecommunication Charge Card (ITEC)..... | 1 | +| 7.1 Scope ..... | 1 | +| 7.2 References..... | 1 | +| 7.3 Definitions ..... | 2 | +| 7.4 Abbreviations..... | 2 | +| 7.5 Description of ITCC ..... | 3 | +| 7.6 Functional model for ITCC..... | 3 | +| 7.6.1 Functional model description..... | 3 | +| 7.7 Information Flows for ITCC..... | 6 | +| 7.7.1 ITCC procedures..... | 6 | +| 7.7.2 Definition of individual information flows..... | 9 | +| 7.8 SDL diagrams for ITCC ..... | 11 | +| 7.8.1 Card validation procedure..... | 12 | +| 7.8.2 Call Disposition procedure..... | 14 | +| 7.9 Functional Entity Actions ..... | 14 | +| 7.10 Allocation of FEs to physical locations ..... | 19 | +| Appendix I – Access and identification procedure..... | 21 | +| Appendix II – Validation Rejection and Retry procedure ..... | 23 | +| Appendix III – Maximum retries reached and service logic initiated release procedure ..... | 25 | +| Appendix IV – Outgoing call ..... | 25 | +| Appendix V – Calling party abandon ..... | 27 | +| Appendix VI – Calling and called party initiated disconnection..... | 28 | +| Appendix VII – Follow-on recognition ..... | 29 | +| Appendix VIII – Network initiated disconnection ..... | 30 | + +## **SUMMARY** + +This Recommendation provides the stage 2 service description of the International Telecommunication Charge Card supplementary service. This Recommendation describes the validation of the charge card in terms of the transfer of the necessary validation information to the card issuing administration across an international interface. + +## STAGE 2 DESCRIPTION FOR CHARGING SUPPLEMENTARY SERVICES + +(revised 1995) + +## 7 International Telecommunication Charge Card (ITEC) + +## 7.1 Scope + +This Recommendation provides a stage 2 description for the International Telecommunication Charge Card (ITCC) as defined in Recommendations E.113 and E.118. The ITCC service provides for the validation of the charge card and transmission of call documentation to the card issuing Administration across the international interface (SCF-SDF). Other interfaces associated with placing an international charge card call that are beyond the international validation (e.g. collecting information and user prompting performed by SRF) are national in nature and therefore beyond the scope of this Recommendation. + +## 7.2 References + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation E.109 (1995) – *International billed number screening procedures for collect and third-party calling.* +- ITU-T Recommendation E.113 (1993), *Validation procedures for the international telecommunications charge card service.* +- CCITT Recommendation E.116 (1992), *International telecommunication charge card service.* +- CCITT Recommendation E.118 (1992), *The international telecommunication charge card.* +- ITU-T Recommendation Q.1205 (1993), *Intelligent network physical plane architecture.* +- ITU-T Recommendation Q.1213 (1993), *Global functional plane for intelligent network CS-1.* +- ITU-T Recommendation Q.1214 (1993), *Distributed functional plane for intelligent network CS-1.* +- ITU-T Recommendation Q.1218 (1993), *Interface Recommendation for intelligent network CS-1.* +- ITU-T Recommendation Q.1219 (1994), *Intelligent network user's guide for capability set 1.* +- ITU-T Recommendation Q.71 (1993), *ISDN circuit mode switched bearer services.* +- CCITT Recommendation Q.65 (1988), *Stage 2 of the method for the characterization of services supported by an ISDN.* +- ITU-T Recommendation clause 1/Q.736 (1995), *International Telecommunication charge card (ITCC).* + +## 7.3 Definitions + +For the purposes of this Recommendation, the following definitions apply. + +**7.3.1 card acceptor** (Subclause 3.2/E.116): The Recognized Operating Agency (ROA) that accepts the use of the card as payment for the provision of certain telecommunication services. + +**7.3.2 card acceptor SDF**: It is the SDF (Service Data Functions) of the card acceptor where the service agreements are stored. It is designated SDF(ca). + +**7.3.3 card issuer**: (Subclause 3.1/E.116) The Recognized Operating Agency (ROA) that issues the card. The card issuer is responsible for the collection of charges from the card holder and for making the appropriate payments for the service concerned to the card acceptor. + +**7.3.4 card issuer SDF**: It is the SDF of the card issuer where the ITCC charge card user profile is stored. It is designated SDF(ci). + +**7.3.5 originating network**: The network from which any user originates an ITCC service request. + +**7.3.6 personal identification number** (Subclause 2.2.6/E.113): The Personal Identification Number (PIN) is used by the card issuer to identify the user and authorize the use of the card. It is obtained from the user or encoded on the card. + +**7.3.7 primary account number** (Subclauses 2.2.3/E.113 and 2.1/E.118): The Primary Account Number (PAN) (19 visible characters – maximum) is the number assigned to a charge card. It is obtained from the card or the user when the user attempts to make a charge card call. The user identification number, which is a subpart of the Primary Account Number, can be used by the call originating ROA to identify the card-issuing ROA. + +**7.3.8 terminating network**: It is the network of the called party. + +## 7.4 Abbreviations + +For the purposes of this Recommendation, the following abbreviations are used. + +| | | +|-------|---------------------------------------------------| +| BCSM | Basic Call State Model (in Recommendation Q.1214) | +| CCAF | Call Control Agent Function | +| CCF | Call Control Function | +| CHG | Charge SIB | +| CLI | Calling Line Identity | +| CS-1 | Capability Set 1 | +| DP | Detection Point (in BCSM) | +| EDP | Event Detection Point (in BCSM) | +| EDP-N | Event Detection Point – Notification (in BCSM) | +| EDP-R | Event Detection Point – Report (in BCSM) | +| FE | Functional Entity | +| FEA | Functional Entity Action | +| IE | Information Element | +| IF | Information Flow | +| IN | Intelligent Network | +| IP | Intelligent Peripheral | +| ISDN | Integrated Services Digital Network | +| ITCC | International Telecommunication Charge Card | +| PSTN | Public Switched Telephone Network | +| SCF | Service Control Function | +| SDF | Service Data Function | + +| | | +|---------|-------------------------------------| +| SDF(ca) | Card Acceptor Service Data Function | +| SDF(ci) | Card Issuer Service Data Function | +| SIB | Service Independent Building Block | +| SRF | Specialized Resource Function | +| SSF | Service Switching Function | + +## 7.5 Description of ITCC + +The International Telecommunication Charge Card service allows the holder of a telecommunication charge card to make use of a variety of telecommunication services provided by the card acceptor and have the charges billed to the customer's account by the card issuer (see Recommendations E.113, E.116 and E.118). + +## 7.6 Functional model for ITCC + +### 7.6.1 Functional model description + +This subclause contains a description of the functional model of ITCC and it is depicted in Figure 1. The functional model merges the IN and non-IN models as defined in the reviewed Recommendation Q.65. It contains nine Functional Entities (FE1 to FE9) and seven relationship types (Rj, Rm, Rn, Rp, Rq, Rs and Rr). Functional Entities are represented by circles and the relationship between two communicating functional entities is identified by a line joining them. Modelling of entities and information flows which relate to the service management are not shown. + +There are three networks involved in the validation procedure. They are originating, terminating and card issuing. + +![Functional model for ITCC provision diagram showing nine Functional Entities (FE1 to FE9) and their relationships.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +The diagram illustrates the functional model for ITCC provision, showing nine Functional Entities (FE1 to FE9) and their relationships. The entities are represented by circles, and the relationships are represented by lines connecting them. The relationships are labeled with relationship types (Rj, Rm, Rn, Rp, Rq, Rs, Rr). + +The entities and their roles are: + +- FE1: CCAF (Originating) +- FE2: CCF +- FE4: CCF +- FE5: CCAF (Terminating) +- FE6: SCF(ca) +- FE7: SDF(ca) +- FE8: SRF +- FE9: SDF(ci) + +The relationships are: + +- Rj: CCAF (Originating) to CCF (FE2) +- Rm: CCF (FE4) to CCAF (Terminating) +- Rn: CCF (FE2) to CCF (FE4) +- Rs: CCF (FE2) to SRF (FE8) +- Rp: SCF(ca) (FE6) to CCF (FE2) +- Rr: SCF(ca) (FE6) to SRF (FE8) +- Rq: SCF(ca) (FE6) to SDF(ca) (FE7) +- Rq: SCF(ca) (FE6) to SDF(ci) (FE9) + +Legend: + +- Basic call process: Solid line +- ITCC service control: Dashed line +- ca: Card acceptor +- ci: Card issuer + +T1166190-94/d01 + +Functional model for ITCC provision diagram showing nine Functional Entities (FE1 to FE9) and their relationships. + +FIGURE 1/Q.86 +Functional model for ITCC provision + +In Figure 1 the Functional Entities (FEs) have the following meaning: + +- FE1: Originating Call Control Agent Function (CCAF). +- FE2: Originating Call Control Function (CCF) associated with Service Switching Function (SSF). +- FE3: Not used. +- FE4: Terminating CCF. +- FE5: Terminating CCAF. +- FE6: Service Control Function (SCF). +- FE7: Service Data Function in the Originating network [SDF(ca)]. +- FE8: Specialized Resource Function (SRF). +- FE9: Service Data Function in the Terminating network [SDF(ci)]. + +NOTE – In CS-1, the CCF and SSF are assumed to have a relationship which is not externally visible and which is therefore not subject for standardization. + +It can be assumed that descriptions of FEs for non-IN is similar to an IN description. + +With reference to 3.3/Q.1214, a description of these FEs is given below: + +#### **The CCA Function (CCAF)** + +The CCAF is the Call Control Agent (CCA) Function that provides access for users. It is the interface between user and network Call Control functions. It: + +- a) provides for user access, interacting with the user to establish, maintain, modify and release, as required, a call or instance of service; +- b) accesses the service-providing capabilities of the Call Control Function (CCF), using service requests (e.g. set-up, transfer, hold, etc.) for the establishment, manipulation and release of a call or instance of service; +- c) receives indications relating to the call or service from the CCF and relays them to the user as required; +- d) maintains call/service state information as perceived by this functional entity. + +#### **The CC Function (CCF)** + +The CCF is the Call Control (CC) Function in the network that provides call/connection processing and control. It: + +- a) establishes, manipulates and releases call/connection as “requested” by the CCAF; +- b) provides the capability to associate and relate CCAF functional entities that are involved in a particular call and/or connection instance (that may be due to SSF requests); +- c) manages the relationship between CCAF functional entities involved in a call (e.g. supervises the overall perspective of the call and/or connection instance); +- d) provides trigger mechanisms to access IN functionality (e.g. passes events to the SSF). + +#### **The SS Function (SSF)** + +The SSF is the Service Switching (SS) Function, which associated with the CCF, provides the set of functions required for interaction between the CCF and a Service Control Function (SCF). It: + +- a) extends the logic of the CCF to include recognition of the service (service control triggers) and to interact with the SCF; +- b) manages signalling between the CCF and the SCF; +- c) modifies call/connection processing functions (in the CCF) as required to process requests for IN and non-IN provided service usage under the control of the SCF. + +#### **The SC Function (SCF)** + +The SCF is a function that commands call control functions in the processing of IN provided and/or custom service requests. The SCF may interact with other functional entities to access additional logic or to obtain information (service or user data) required to process a call/service logic instance. It: + +- a) interfaces and interacts with Service Switching Function/Call Control Function, Specialized Resource Function (SRF) and Service Data Function (SDF) functional entities; +- b) contains the logic and processing capability required to handle IN-provided service attempts. + +#### **The SD Function (SDF)** + +The SDF contains customer and network data for real time access by the SCF in the execution of an IN provided service. It interfaces and interacts with SCFs as required. + +NOTE – The SDF contains data relating directly to the provision or operation of IN provided services. Thus it does not necessarily encompass data provided by third party such as credit information, but may provide access to these data. + +#### **The SR Function (SRF)** + +The SRF provides the specialized resources required for the execution of IN and non-IN provided services (e.g. digit receivers, announcements, conference bridges, etc.). It: + +- a) interfaces and interacts with SCF and SSF (and with the CCF); +- b) may contain the logic and processing capability to receive/send and convert information received from users; +- c) may contain functionality similar to the CCF to manage bearer connections to the specialized resources. + +For the purposes of this Recommendation, the CCAF is identical with the CCA of Recommendation Q.71. The CCF is based on the corresponding Q.71 ISDN definitions but modified for the use in IN. The enhanced Basic Call Model of IN defines standard Detection Points (DPs) at which IN service feature logic instances can be invoked. These DPs correspond to the Q.71 “hooks” where an ISDN supplementary service interfaces to the Basic Call Model. For the purposes of this Recommendation, relationships Rj, Rn, Rm are outside the scope of this Recommendation and are identical with those defined in Recommendation Q.71. For the purposes of this Recommendation, Rs is identical with relationship r2 in Recommendation Q.71, since it involves the control of a connection between CCF and SRF in order to provide specialized resources such as tones and announcements. Network capabilities common to a number of supplementary services for user interaction and their switching and signalling requirements are also outside the scope of this Recommendation. Finally, as the Rp and Rr relationships are nationally dependent, only the relation Rq is in the scope of this Recommendation. + +This Recommendation treats the case where there is no transfer of the user’s service profile information and SDF(ci) will be accessed for any query (e.g. validation request) on or update (e.g. threshold update) of the ITCC user’s data. Note that the SDF(ci) does not belong to the card acceptor and it is usually located outside the national boundary. + +The SDF associated with the card acceptor network may contain some data related to the provision of ITCC service to the visiting user. For example, SDF(ca) may contain information on agreements with other ITCC service providers. No additional security for interworking is provided other than such knowledge of existence of service agreements between service providers. SDF(ca) may also contain data on security measures, e.g. the number of retries allowed by the originating network to an ITCC user attempting to access ITCC service. It is also assumed that SDF(ci) will also be able to check that a service agreement exists with the service provider of the invoking SCF. + +## 7.7 Information Flows for ITCC + +The Information Flows (IFs) and their contents (Information Elements, IEs) are based on those developed by Study Group 11 for the IN architecture, as described in clause 6/Q.1214. The individual IFs are described in 7.7.2 of this Recommendation. Whether IFs are confirmed or unconfirmed and of type req. ind. or resp. conf. is described here. Information flows and information elements for non-IN can be considered to be equivalent. + +In the information flow diagrams the CS-1 IF names are shown in mixed case lettering, without the req. ind. or resp. conf. descriptors. The full descriptions of these IFs are in 7.7.2 (The individual IFs). IFs derived from Recommendation Q.71 are shown in upper case italic letters, with type descriptors. + +The IFs do not show any IFs relating to timer control of interaction between FEs. Not all error paths are considered. + +### 7.7.1 ITCC procedures + +The ITCC user invokes access to ITCC service by setting up a call to an ITCC card acceptor network. The user is then connected to an SRF which provides the mechanism of interaction between the ITCC user and the ITCC card acceptor network for the collection of information to enable access to the service. + +The interactions between the ITCC user and the SRF are assumed to be by DTMF in-band signalling. The SRF also provides voice prompts but specific content of the announcements is beyond the scope of this Recommendation. + +The sequence (e.g. PAN, PIN, Called Number) in which the information is sent from the ITCC user to the network is a national matter, and is also beyond the scope of this Recommendation. + +An outline of the sequence in which the procedures are invoked is shown in Figure 2, exit and error paths are not included. + +The main body of text of this Recommendation contains the description of the validation and call disposition procedures for the ITCC service as defined in Recommendation E.113. Other procedures that are out of the scope of standardization (national dependent) are reported in the appendixes. + +#### 7.7.1.1 Validation procedure + +The ITCC service is based on an automatic validation procedure that implies that the call handling Administration will query the database of the card issuing Administration to validate telephone charge cards used by customers who are making a call in a country other than their own. + +Recommendation E.113 “Validation procedures for the international telecommunications charge card service” defines the procedures for the validation process between Administrations. The validation process foresees the following messages: + +- **Authorization Request (M)**: is a message from the card acceptor network to the card issuer network which provides details of an attempt to use a telephone charge card (i.e. card validation). +- **Request Response (M)**: is a message from the card issuer network to the card acceptor network to provide either a positive or negative response to the authorization request. + +The following is a high-level description of the network actions required in order to validate the ITCC service. + +According to Recommendation E.118 describing the card format, the identity of the ITCC card issuer can be deduced from the Primary Account Number. Moreover, if there is a service agreement between the card acceptor and the card issuer, then the SDF associated with the card acceptor network may contain some data related to the agreements with other ITCC service providers. + +![Flowchart illustrating the sequencing of ITCC procedures. The process starts with 'Start', followed by 'Access and User Identification (Figure I.1)'. An 'OK' response leads to the 'Validation Procedure'. From 'Validation Procedure', an 'OK' response leads to 'Outgoing Call (Figure IV.1)', while a 'NOK' response leads to 'Validation rejection and Retry (Figure II.1)'. From 'Validation rejection and Retry', an 'OK' response leads to 'Outgoing Call', while a 'NOK limit not reached' response loops back to 'Validation Procedure'. A 'Limit exceeded' response leads to 'Max. retries reached and Service Logic Initiated Disconnection (Figure III.1)'. From 'Outgoing Call', the process branches into 'Calling Party Disconnection (Figure VI.1)' and 'Called Party Disconnection (Figure VI.2)'. Both lead to 'Call Disposition (Figure 4)'. From 'Call Disposition', the process can end (marked with a circle with an X) or proceed to 'Follow-on Procedure (Figure VII.1)' if a 'Follow-on Request' is received. The 'Follow-on Procedure' then loops back to the 'Validation Procedure'.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +graph TD + Start([Start]) --> Access[Access and User Identification (Figure I.1)] + Access -- OK --> Validation[Validation Procedure] + Validation -- OK --> Outgoing[Outgoing Call (Figure IV.1)] + Validation -- NOK --> Retry[Validation rejection and Retry (Figure II.1)] + Retry -- OK --> Outgoing + Retry -- "NOK limit not reached" --> Validation + Retry -- "Limit exceeded" --> Disconn[Max. retries reached and Service Logic Initiated Disconnection (Figure III.1)] + Outgoing --> Calling[Calling Party Disconnection (Figure VI.1)] + Outgoing --> Called[Called Party Disconnection (Figure VI.2)] + Calling --> Disposition[Call Disposition (Figure 4)] + Called --> Disposition + Disposition --> End((End)) + Disposition -- "Follow-on Request" --> Follow[Follow-on Procedure (Figure VII.1)] + Follow --> Validation + +``` + +T1166200-94/d02 + +Flowchart illustrating the sequencing of ITCC procedures. The process starts with 'Start', followed by 'Access and User Identification (Figure I.1)'. An 'OK' response leads to the 'Validation Procedure'. From 'Validation Procedure', an 'OK' response leads to 'Outgoing Call (Figure IV.1)', while a 'NOK' response leads to 'Validation rejection and Retry (Figure II.1)'. From 'Validation rejection and Retry', an 'OK' response leads to 'Outgoing Call', while a 'NOK limit not reached' response loops back to 'Validation Procedure'. A 'Limit exceeded' response leads to 'Max. retries reached and Service Logic Initiated Disconnection (Figure III.1)'. From 'Outgoing Call', the process branches into 'Calling Party Disconnection (Figure VI.1)' and 'Called Party Disconnection (Figure VI.2)'. Both lead to 'Call Disposition (Figure 4)'. From 'Call Disposition', the process can end (marked with a circle with an X) or proceed to 'Follow-on Procedure (Figure VII.1)' if a 'Follow-on Request' is received. The 'Follow-on Procedure' then loops back to the 'Validation Procedure'. + +FIGURE 2/Q.86 +Outline of sequencing of ITCC procedures + +Procedures for the SRF to the interface with the calling user in order to collect his information or to provide announcements is national in nature and beyond the scope of this Recommendation. + +###### Outline + +- 1) The originating network requires the card issuer network to validate (Authorization Request) the card. +- 2) The card issuer network undertakes authentication checks and sends back the result (Request Response). + +- 3) Decision: + - if successful, continue the ITCC procedures; + - if unsuccessful and subsequent attempts allowed, advise user of failure and restart the user validation; + - if unsuccessful and no subsequent attempts allowed, advise user and release the call. + +###### 7.7.1.1.1 Information flow diagram + +The following diagram (Figure 3) shows the validation procedure. + +![Figure 3/Q.86: Validation procedure information flow diagram. The diagram shows a sequence of functional entities (FE2, FE6, FE8, FE7, FE9) and a 'Screen SIB' block. FE2 (SSF/CCF) sends message Rp to FE6 (SCF). FE6 sends Rq to FE8 (SRF) and FE7 (SDF(ca)). FE8 sends Rr to FE6. FE7 sends Rq to FE9 (SDF(ci)). FE6, FE8, FE7, and FE9 are part of a larger block containing a table with search results. The table has columns for FE6, FE8, FE7, and FE9. The first row contains '623', 'Search', a shaded box, a shaded box, and a shaded box. The second row contains '670', 'Search Result', a shaded box, a shaded box, and '900'. An arrow points from the '900' cell to the 'Screen SIB' block. The reference T1166210-94/d03 is at the bottom right.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +T1166210-94/d03 + +Figure 3/Q.86: Validation procedure information flow diagram. The diagram shows a sequence of functional entities (FE2, FE6, FE8, FE7, FE9) and a 'Screen SIB' block. FE2 (SSF/CCF) sends message Rp to FE6 (SCF). FE6 sends Rq to FE8 (SRF) and FE7 (SDF(ca)). FE8 sends Rr to FE6. FE7 sends Rq to FE9 (SDF(ci)). FE6, FE8, FE7, and FE9 are part of a larger block containing a table with search results. The table has columns for FE6, FE8, FE7, and FE9. The first row contains '623', 'Search', a shaded box, a shaded box, and a shaded box. The second row contains '670', 'Search Result', a shaded box, a shaded box, and '900'. An arrow points from the '900' cell to the 'Screen SIB' block. The reference T1166210-94/d03 is at the bottom right. + +FIGURE 3/Q.86 +Validation procedure + +The validation is undertaken by the ITCC card issuer using the information received by the SCF(ca) including PAN, PIN and eventually the Called Number1). If authentication is successful, the ITCC service logic in the originating network can continue. If authentication fails, action could proceed to “Authentication rejection and retry” (see Figure II.1) or terminate the call to “Maximum retries reached” (see Figure III.1). + +#### 7.7.1.2 Call disposition procedure + +Recommendation E.113 “Validation procedures for the international telecommunications charge card service” foresees, based on bilateral agreement, the procedure for the transmission of call details to the card issuing Administration at the end of each ITCC call. This procedure, uses the following message: + +- **Call Disposition (O):** is a message from the card acceptor network to the card issuer network to track usage of the card against the credit limit of the customer and gather other statistics. The main purpose of this additional message is to provide, on a timely basis, better control against potential fraudulent use of the charge card. + +1) PAN (max. 19 digits)      PIN (Max. 4 digits) + MII = 89 + CC      CLD No. (Recommendation E.164) + Issuer ID      CLG No. (Recommendation E.164) + ACT No. + +The following is a high-level description of the network actions required in order to update the threshold in SDF(ci). + +###### Outline + +- 1) The originating network sends to the card issuer network the call details including the estimated charge as soon as the call is completed. +- 2) The card issuing network updates the usage value of the card and sends back a response. +- 3) If follow-on is foreseen, a trigger condition was met during the called party initiated disconnection; the action proceeds to “Follow-on” (see Figure VII.1). + +It is assumed that the appropriate points of control for detecting call abandon of the Calling party and the call disconnect of Calling/Called party will always be appropriately armed. + +Call details information to be sent in a Call Disposition message must be obtained from the SSF upon completion of a call. Procedures to provide this information by SSF to SCF are national in nature and beyond the scope of this Recommendation (see Figure IV.1). + +###### 7.7.1.2.1 Information flow diagram + +The following diagram (Figure 4) shows the Call Disposition procedure. + +![Sequence diagram of the Call Disposition procedure showing interactions between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci).](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +``` + +sequenceDiagram + participant FE2 as FE2 +SSF/CCF + participant FE6 as FE6 +SCF + participant FE8 as FE8 +SRF + participant FE7 as FE7 +SDF(ca) + participant FE9 as FE9 +SDF(ci) + + FE2->>FE6: Rp + FE6->>FE8: Rq + FE6->>FE7: Rq + FE6->>FE9: Rq + FE6->>FE8: Rr + FE6->>FE7: Update Data + FE6->>FE9: Update Data + FE7->>FE9: 901 + FE9->>FE6: Update Confirmation + FE6-->>FE8: (Note) + +``` + +The diagram illustrates the Call Disposition procedure. It shows five functional entities: FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). The process begins with FE2 sending a message 'Rp' to FE6. FE6 then sends 'Rq' to FE8, FE7, and FE9, and 'Rr' to FE8. FE6 sends 'Update Data' to both FE7 and FE9. FE7 sends '901' to FE9. FE9 sends 'Update Confirmation' back to FE6. Finally, FE6 sends a '(Note)' to FE8. A shaded box labeled 'Service Data Management SIB' encompasses the FE6, FE8, FE7, and FE9 entities. The reference 'T1166220-94/d04' is located at the bottom right of the diagram. + +Sequence diagram of the Call Disposition procedure showing interactions between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). + +NOTE – If follow-on is foreseen, a trigger condition was met during the called party initiated disconnection (see Figure VI.2, FEA 603), the action now proceeds to “Follow-on Recognition” (see Figure VII.1). + +FIGURE 4/Q.86 +Call Disposition procedure + +The Call Disposition procedure updates the ITCC service profile adding details related to the call documentation including the estimated call charge. Note that the confirmation response from the SDF(ci) to SCF(ca) could be not requested. + +### 7.7.2 Definition of individual information flows + +The Information Flows (IFs) contained in this subclause are those described in clauses 5 and 6/Q.1214. The information elements (IEs) shown as those which are either mandatory (M) or Optional but needed for ITCC service (O). All of them are related to the SCF-SDF interface. + +NOTE 1 – As far as the SCF-SDF interface is concerned, Study Group XI/4 decided to use the X.500 protocol for the SCF-SDF interface. After the September 1994 meeting, this Recommendation will be updated in order to consider the necessary modifications. + +The IFs are also cross-referenced to the Service Independent Building Block (SIB) in which the IF is described in clause 5/Q.1214. + +NOTE 2 – Based on the SG 4/11 final decision, also the Service Independent Building Block (SIB) description in clause 5/Q.1214 has to be updated accordingly. + +The IFs related to the SSF-SCF and SRF-SSF interfaces, as stated in 7.7.1, are outside the scope of this Recommendation as they refer to a part of the architecture that may be implemented both using IN/non-IN model. For simplicity, these IFs are shown in Appendix I. + +#### 7.7.2.1 Relationship Rq (SCF-SDF) + +The abbreviations for the SIBs and the relevant subclause numbers in Recommendation Q.1214 are: + +- Screen Screen 5.2.8/Q.1214 +- Service Data Management SDM 5.2.9/Q.1214 + +The Screen SIB provides the capability for the SCF to perform a comparison of an identifier against a list located in a specified storage space in the SDF. + +The Service Data Management SIB provides the capability for the SCF to: retrieve, replace, increment and decrement data in a specified storage space in the SDF. + +Non-IN use of relationship Rq for SCF-SDF is essentially the same as that described using IN terminology. + +###### 7.7.2.1.1 SCF to SDF flows + +The Query IF is used to query an item of data held in the SDF. + +The Update Data IF when requested entails an automatic execution of the update. + +Query req. ind. – confirmed IF (SDM, Screen, Trans.) + +| | | | +|------|---------------------|---| +| IEs: | Database Id | O | +| | Requested Info Type | O | +| | Information Key | M | + +Update Data req. ind. – confirmed IF (SDM, LCI) + +| | | | +|------|-----------------|---| +| IEs: | Function Type | O | +| | Database Id | O | +| | Updated Info | M | +| | Information Key | M | + +###### 7.7.2.1.2 SDF to SCF flows + +The Query Result IF is the response to a Query IF. Note that in INAP this IF maps on to the RESULT part of the Query operation. + +The Update Confirmation IF is the response to an Update Data IF. Note that in INAP this IF maps on to the RESULT part of the Update Data operation. + +Query Result resp. conf. – unconfirmed IF (SDM, Screen, Trans.) + +| | | | +|------|----------------|---| +| IEs: | Requested Info | M | +|------|----------------|---| + +Update Confirmation resp. conf. – unconfirmed IF (SDM, LCI) + +| | | | +|------|---------|---| +| IEs: | Outcome | M | +|------|---------|---| + +## 7.8 SDL diagrams for ITCC + +The SDL diagrams depicted in Figure 5 describe the sequencing of the Information Flows of 7.7. The SDL are related to the SCF-SDF interface. See Figure 5a. + +![Two SDL diagrams for the SCF-SDF interface. The left diagram shows a linear sequence: an initial state, a 'Request to SDF' message, an 'SDF Request' message, and a return to the previous state. The right diagram shows a branching sequence: a 'Request type' decision leading to 'Query to SDF' or 'Update to SDF', followed by 'Waiting for SDF Response', and then 'Query Result from SDF' or 'Update Confirmation from SDF' messages leading to final states.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +The diagram consists of two separate SDL (Sequence Diagram Language) diagrams for the SCF-SDF interface. + +**Left Diagram:** + +- Starts with a state node (rounded rectangle). +- Transitions to a message box labeled "Request to SDF". +- Transitions to a message box labeled "SDF Request". +- Transitions to a state node. + +**Right Diagram:** + +- Starts with a state node (rounded rectangle). +- Transitions to a decision diamond labeled "Request type". +- Branches into two paths: + - Left path: "Query to SDF" message. + - Right path: "Update to SDF" message. +- Both paths merge and transition to a state node labeled "Waiting for SDF Response". +- Branches into two paths: + - Left path: "Query Result from SDF" message. + - Right path: "Update Confirmation from SDF" message. +- Both paths merge and transition to a final state node (circle with an X). + +Annotations for the left diagram: + +- "Can be any state but Idle" points to the initial state node. +- "Request from service logic" points to the "Request to SDF" message. +- "Request type is Query or Update" points to the "SDF Request" message. +- "Return to previous state" points to the final state node. + +T1166230-94/d05 + +Two SDL diagrams for the SCF-SDF interface. The left diagram shows a linear sequence: an initial state, a 'Request to SDF' message, an 'SDF Request' message, and a return to the previous state. The right diagram shows a branching sequence: a 'Request type' decision leading to 'Query to SDF' or 'Update to SDF', followed by 'Waiting for SDF Response', and then 'Query Result from SDF' or 'Update Confirmation from SDF' messages leading to final states. + +FIGURE 5a/Q.86 +SDLs diagram for SCF + +### 7.8.1 Card validation procedure + +This paragraph describes two possible solutions to provide a card validation procedure; the first one uses the Retrieve operation, the second one shows the Screen operation. See Figures 5b and 5c. + +![SDL diagram for card successful validation procedure.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +The diagram illustrates the first example of an SDL procedure for card successful validation. It consists of two main parts: a request sequence and a response sequence. + +**Request Sequence:** + +- Starts with a start symbol (oval with two vertical lines). +- Followed by a **Retrieve Request to SDF h** operation (rectangle with a right-pointing arrow). +- A dashed line connects this operation to a data object: `Request from ITCC Service Logic to send a Retrieve`. +- The next operation is **Retrieve to SDF h** (rectangle with a right-pointing arrow). +- A dashed line connects this operation to a data object containing a structured list: + +``` +{object name +{ {type providerId + value providerIdVar}, +{type pan + value panVar}, +{type pin + value pinVar} +} +selection +{type pin + value pinVar} +} +``` +- The sequence ends with a **Waiting for SDF Response** symbol (oval). + +**Response Sequence:** + +- Starts with a **Waiting for SDF h Response** symbol (oval). +- Followed by a **Retrieve Result from SDF h** operation (rectangle with a left-pointing arrow). +- A dashed line connects this operation to a data object: `{entries {type pin value pinVar}}`. +- The sequence ends with a stop symbol (circle with an 'X'). + +The identifier `T1166240-94/d06` is located to the right of the response sequence. + +SDL diagram for card successful validation procedure. + +FIGURE 5b/Q.86 +First example of SDL procedure for card successful validation + +![Sequence diagram showing the SDL procedure for card successful validation. The process starts with a start node, followed by a 'Screen Request to SDF h' message box. A dashed line indicates a 'Request from ITCC Service Logic to send a Screen'. This leads to a 'Screen to SDF h' message box, which has a dashed line indicating a data object: {object name { {type providerId value providerIdVar}, {type pan value panVar}, {type pin value pinVar} } }. This leads to a 'Waiting for SDF h Response' message box. The process then continues to a 'Screen Result from SDF h' message box, which has a dashed line indicating a data object: {matched {TRUE}}. This leads to an end node (a circle with an X).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + Start([Start]) --> ScreenRequest[Screen Request to SDF h] + ScreenRequest -.->> Note1[Request from ITCC Service Logic to send a Screen] + ScreenRequest --> ScreenToSDFh[Screen to SDF h] + ScreenToSDFh -.->> Note2["{object name +{ {type providerId +value providerIdVar}, +{type pan +value panVar}, +{type pin +value pinVar} +} +}"] + ScreenToSDFh --> WaitingResponse[Waiting for SDF h Response] + WaitingResponse --> ScreenResult[Screen Result from SDF h] + ScreenResult -.->> Note3["{matched +{TRUE}}"] + ScreenResult --> End((X)) + +``` + +T1166250-94/d07 + +Sequence diagram showing the SDL procedure for card successful validation. The process starts with a start node, followed by a 'Screen Request to SDF h' message box. A dashed line indicates a 'Request from ITCC Service Logic to send a Screen'. This leads to a 'Screen to SDF h' message box, which has a dashed line indicating a data object: {object name { {type providerId value providerIdVar}, {type pan value panVar}, {type pin value pinVar} } }. This leads to a 'Waiting for SDF h Response' message box. The process then continues to a 'Screen Result from SDF h' message box, which has a dashed line indicating a data object: {matched {TRUE}}. This leads to an end node (a circle with an X). + +FIGURE 5c/Q.86 +Second example of SDL procedure for card successful validation + +### 7.8.2 Call Disposition procedure + +See Figure 5d. + +![Sequence diagram showing the call disposition procedure at the end of a successful call. The process starts with a start node, followed by an 'Update Request to SDF h' action triggered by a 'Request from ITCC Service Logic to send an Update'. This leads to an 'Update to SDF h' action, which sends a message containing object details and changes to the SDF h. This is followed by a 'Waiting for SDF h Response' state. The process then continues with an 'Update Result from SDF h' action triggered by the response, leading to an end node. A final 'Waiting for SDF h Response' state is also shown.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +``` +sequenceDiagram + Start([Start]) -->> UpdateRequest[Update Request to SDF h] + Note over UpdateRequest: Request from ITCC Service Logic to send an Update + UpdateRequest -->> UpdateSDFh[Update to SDF h] + Note over UpdateSDFh: {object name +{ {type providerId +value providerIdVar}, +{type pan +value panVar}, +{type pin +value pinVar} +{type userId +value userIdVar} +} +changes +{ addComponentValue +{ type callInfoRecord +value callInfoRecordVar } +} +} + UpdateSDFh -->> WaitSDFh1([Waiting for SDF h Response]) + WaitSDFh1 -->> UpdateResult[Update Result from SDF h] + Note over UpdateResult: {empty} + UpdateResult -->> End((End)) + UpdateResult -->> WaitSDFh2([Waiting for SDF h Response]) +``` + +T1166260-94/d08 + +Sequence diagram showing the call disposition procedure at the end of a successful call. The process starts with a start node, followed by an 'Update Request to SDF h' action triggered by a 'Request from ITCC Service Logic to send an Update'. This leads to an 'Update to SDF h' action, which sends a message containing object details and changes to the SDF h. This is followed by a 'Waiting for SDF h Response' state. The process then continues with an 'Update Result from SDF h' action triggered by the response, leading to an end node. A final 'Waiting for SDF h Response' state is also shown. + +FIGURE 5d/Q.86 + +Example of SDL procedure for call disposition at the end of a successful call + +## 7.9 Functional Entity Actions + +###### FEA: 200 [A] + +- On detection of the request for ITCC service, the SSF formulates and sends Initial DP req. ind. to SCF. +- Suspend the call processing until the validation is complete. + +###### FEA: 201 [E] + +- Receive and react to DISCONNECT req. ind. from CCAF. +- Formulate and send RELEASE req. ind. to SRF to Release resources. +- Disconnect. +- Stop charging, if applicable. + +###### **FEA: 202 [E]** + +- Receive and react to RELEASE req. conf. from CCAF. +- Formulate and send Event Report BCSM req. ind. to SCF, if required. +- Continue clearing call as per Recommendation Q.71. + +###### **FEA: 203 [F.1]** + +- Receive and react to DISCONNECT req. ind. from CCAF. +- Formulate and send Event Report BCSM req. ind. to SCF. + +###### **FEA: 210 [A]** + +- Receive Request Report BCSM Event req. ind. from SCF. +- Arm Detection Points as EDP-N to report user abandon (before answer – DP 10) or user disconnect (after answer – DP 9). + +###### **FEA: 211 [A, G]** + +- Receive and react to Establish Temporary Connection req. ind. from SCF. +- Formulate and send SETUP req. ind. to SRF to establish a connection to it. + +###### **FEA: 212 [D, H]** + +- Receive and react to Disconnect Forward connection req. ind. from SCF. +- Formulate and send Release req. ind. to SRF. + +###### **FEA: 214 [D]** + +- Receive Request Report BCSM Event req. ind. from SCF. +- Arm Detection Points as EDP-R or EDP-N to report route select failure (DP 4), B busy (DP 5), B no answer timeout (DP 6), and B clear (DP 9). + +NOTE 1 – If follow-on call is allowed, the DPs will be armed as EDP-R, or else as EDP-N. + +###### **FEA: 215 [D]** + +- Receive and react Furnish Charging Information req. ind. from SCF. + +###### **FEA: 216 [D]** + +- Receive and react ApplyCharging Information req. ind. from SCF. + +###### **FEA: 217 [D]** + +- Receive and react to Connect req. ind. from SCF. +- Take appropriate action for Basic Call Set-up. + +###### **FEA: 219 [F.1, F.2]** + +- Formulate and send Apply Charging report req. ind. to communicate to the SCF the amount for the call. + +###### **FEA: 250 [A, G]** + +- Receive and react to SETUP resp. conf. from SRF. +- Establish a relationship between the leg between the calling party and the SSF/CCF, and the leg between the SSF/CCF and the SRF. +- Through-connect calling party to SRF. + +###### **FEA: 251 [E]** + +- Receive and react to RELEASE resp. conf. from SRF. +- If no other RELEASE resp. conf. outstanding: + - formulate and send Event Report BCSM req. ind. to SCF, if required. + +###### **FEA: 252 [D, H]** + +- Receive and react to RELEASE resp. conf. from SRF. + +NOTE – The SRF is being released in the middle of a procedure and the call is not yet being terminated. + +###### **FEA: 270 [F.2]** + +- Receive and react to RELEASE req. ind. from forward direction. +- Formulate and send Call Information Report BCSM req. ind. to SCF to report called party release (EDP-N). +- Continue clearing call as per Recommendation Q.71. + +###### **FEA: 600 [A]** + +- Receive and react to Initial DP req. ind. from SSF/CCF. +- Formulate and send Request Report BCSM Event req. ind. to SSF/CCF to arm Detection Points as EDP-N for calling party abandon (DP 10) and disconnect (DP 9), if the latter is required. +- Formulate and send Retrieve req. ind. to SDF(ca) to get the SDF(ci) address if it cannot be deduced from the PAN and the appropriate language to use for announcement (optional). + +###### **FEA: 601 [E]** + +- Receive and react to Event Report BCSM req. ind. from SSF/CCF. + +###### **FEA: 602 [F.1, F.2]** + +- Receive and react to Apply Charging Report req. ind. from SSF/CCF. +- Go to Call Disposition procedure (see Figure 3). + +###### **FEA: 603 [F.1]** + +- Receive and react to Event Report BCSM req. ind. from SSF/CCF. +- If follow-on is foreseen, a trigger condition is met; after the call disposition procedure (see Figure 4), the SCF will initiate the follow-on recognition procedure (see Figure VII.1). + +###### **FEA: 605 [F.2]** + +- Receive and react to Event Report BCSM req. ind. from SSF/CCF. + +#### **FEA: 610 [A]** + +- Receive and react to Retrieve Result req. conf from SDF(ca) by storing the SDF(ci) address and identifying the correct language to use in announcements. +- Formulate and send Establish Temporary Connection req. ind. to SSF/CCF to instruct it to connect to SRF. + +###### **FEA: 620 [A, G]** + +- Receive and react to Assist Request Instructions from SRF req. ind. from SRF. +- Formulate and send Prompt and Collect User Information req. ind. to SRF to prompt user to input his identity in the form of his PIN number. + +###### **FEA: 621 [A]** + +- Receive and react to Collected User Information resp. conf. from SRF. +- Formulate and send a Prompt and Collect User Information req. ind. to SRF to prompt user to input the destination number. + +###### **FEA: 622 [A, B, G]** + +- Receive and react to Collect User Information resp. conf. from SRF. +- Formulate and send Prompt and Collect User Information req. ind. to SRF to prompt user to input his PIN. + +###### **FEA: 623 [Figure 3, B]** + +- Start the Validation procedure. +- Formulate and send a Query req. ind. to SDF(ci) in order to validate the card. Go to the outgoing call procedure. + +###### **FEA: 624 [C]** + +- Receive and react to SR Report resp. ind from SRF. +- Formulate and send Update req. ind. to SDF(ci) to communicate the SDF(ci) the failed attempts record, if not already done. +- Activate security measures to prevent access re-attempts. + +###### **FEA: 650 [B]** + +- On first execution start the SCF counter of validation retries using as the allowed limit the smaller of the two values retrieved from SDF(ca) and SDF(ci). +- Modify counter value as required. +- Formulate and send Update Data req. ind. to SDF(ci) to record numbers of validation failures. + +###### **FEA: 669 [4]** + +- Receive and react to Update Result resp. conf. from SDF(h). +- If the threshold is not exceeded go to FEA xx in “Follow-on allowed” procedure. +- If authentication fails go to FEA xx in “Disconnection” procedure. + +###### **FEA: 670 [Figure 3]** + +- Receive and react to Query Result resp. conf. from SDF(ci). +- If authentication is successful, go to the outgoing call procedure (Figure IV.1); +- If authentication fails and it was the first time go to Validation rejection and retry procedure (Figure II.1). + +###### **FEA: 671 [B]** + +- On first execution formulate and send a Query req. ind. to SDF(ci) to obtain value of validation retry counter allowed from ITCC card issuer (optional). + +###### **FEA: 672 [B]** + +- Receive and react to Query Result req. ind. from SDF(ci). +- Formulate and send Query req. ind. to SDF(ca) to obtain value of local validation retry counter allowed from the originating (local) network (optional). + +###### **FEA: 673 [B]** + +- Receive and react to Query, Result resp. conf. from SDF(ci). +- If authentication is successful, go to the “outgoing call” procedure. +- If authentication fails go to FEA 650 in Validation Retry procedure to update record of failure. + +###### **FEA: 674 [B]** + +- Receive and react to Update Confirmation resp. conf. from SDF(ci). +- Test if retry counter limit is reached. +- If reached, go to Maximum retries reached (Figure III.1). +- If not reached formulate and send Prompt and Collect User Information req. ind. to SRF to prompt user to input his PAN. + +###### **FEA: 675 [C]** + +- Formulate and send Play Announcements req. ind. to SRF to advise the user that the maximum retries number is reached. + +###### **FEA: 678 [C]** + +- Receive and react to Update Conf. resp. conf. from SDF(ci). +- Formulate and send Release Call req. ind. to SSF/CCF. + +#### **FEA: 679 [C]** + +- Receive and react to Release Call resp. conf. req. ind. from SSF/CCF. + +###### **FEA: 700 [A, B]** + +- Receive and react to Retrieve req. ind. from SCF. +- Extract Data request. +- Formulate and send Retrieve Result resp. conf. to SCF. + +#### **FEA: 800 [A, G]** + +- Receive and react to SETUP req. ind. from SSF/CCF. +- On successful establishment of connection: + - formulate and send SETUP resp. conf. to SSF/CCF; + - formulate and send Assist Request Instruction from SRF req. ind. to SCF. + +###### **FEA: 801 [D, E, H]** + +- Receive and react to RELEASE req. ind. from SSF/CCF. +- Disconnect resources. +- Formulate and send RELEASE resp. conf. to SSF/CCF. + +#### **FEA: 810 [A, B, G]** + +- Receive and react to Prompt and Collect User Information req. ind. from SCF. +- Play announcement requested by SCF. +- Collect information. +- On successful receipt of information, or on error condition, formulate and send Collected User Information resp. conf. to SCF. + +#### **FEA: 811 [C]** + +- Receive and react to Play announcement req. ind. from SCF. +- Play announcement requested by SCF. +- Formulate and send a SR Report to SCF. + +#### **FEA: 900 [3, B]** + +- Receive and react to Screen req. ind. from SCF. +- Perform the match required. +- Formulate and send Screen Result resp. conf. to SCF. + +###### **FEA: 901 [4, B]** + +- Receive and react to Update req. ind. from SCF. +- Perform the action required. +- Formulate and send Update Result resp. conf. to SCF. + +###### **FEA: 902 [B]** + +- Receive and react to Retrieve req. ind. from SCF. +- Retrieve data. +- Formulate and send Retrieve Result resp. conf. to SCF. + +## **7.10 Allocation of FEs to physical locations** + +The functional entities depicted in Figure 1 include both IN and non-IN models. Therefore the functional entity and the physical entity relationship can be considered identical for either model. + +The PE used for the mapping are the following: + +**Service Switching Point:** The SSP provides switching functionalities, and if it is a local exchange, provides the user with access to the network. The SSP allows access to the service after a request for the service has been detected. It communicates with other PEs such as an SCP. Functionally the SSP contains CCF, SSF, and, if the SSP is a local exchange, a CCAF. An SCF, an SRF and an SDF may be optionally contained in the SSP. + +**Service Network Access Point:** This PE contains only the CCAF and CCF FEs. The SNAP cannot communicate with an SCF but has the capability to recognize a call requiring the service and route the call to an SSP. + +**Service Control Point:** The SCP contains the Service Logic Programs to provide services. SCP and SSP are connected by signalling network. An SCP contains an SCF and an SDF. + +**Intelligent Peripheral:** The IP provides resources for the user interaction with the network. Functionally an IP contains an SRF. + +**Service Switching and Control Point:** This is a combined SCP and SSP in a single node. Functionally it contains an SCF, SDF, CCAF, CCF and SSF. An SSCP may optionally contain an SRF. + +**Service Data Point:** The SDP contains the customer and network data which is accessed during the execution of a service. Functionally the SDP contains SDF. + +| PE/FE | SSF
FE6 | CCF/SSF
FE2 | SDF(ca) | SDF(ci)
FE9 | SRF
FE8 | +|---------------------------|------------|----------------|---------|----------------|------------| +| SCP | X | – | X | X | – | +| SSP | – | X | X | X | X | +| IP | – | – | – | – | X | +| SDP | – | – | X | X | – | +| SSCP | X | X | X | X | X | +| NAP | – | X | – | – | – | +| X Possible configurations | | | | | | +| – Not recommended | | | | | | + +Scenario 1 + +![Network diagram for Scenario 1 showing a sequence of components: TE (FE1) connected to SSP LE (FE2), which connects to SCP (FE6). SCP (FE6) connects to TR (FE3) and IP (FE8). IP (FE8) connects to LE (FE4), which connects to TE (FE5). Additionally, SCP (FE6) has two 'rq' connections to DB (FE9) and DB (FE7).](73b5cce955ba9415a98791db7b0080ad_img.jpg) + +``` + +graph LR + FE1[TE] --- FE2[SSP LE] + FE2 --- FE6[SCP] + FE6 --- FE3[TR] + FE6 --- FE8[IP] + FE8 --- FE4[LE] + FE4 --- FE5[TE] + FE6 -- rq --- FE9[DB] + FE6 -- rq --- FE7[DB] + +``` + +Network diagram for Scenario 1 showing a sequence of components: TE (FE1) connected to SSP LE (FE2), which connects to SCP (FE6). SCP (FE6) connects to TR (FE3) and IP (FE8). IP (FE8) connects to LE (FE4), which connects to TE (FE5). Additionally, SCP (FE6) has two 'rq' connections to DB (FE9) and DB (FE7). + +Scenario 2 + +![Network diagram for Scenario 2 showing a sequence of components: TE connected to LE, which connects to TR, which connects to another LE, which connects to another TE. The first LE has two 'rq' connections to two separate DB components.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +graph LR + TE1[TE] --- LE1[LE] + LE1 --- TR[TR] + TR --- LE2[LE] + LE2 --- TE2[TE] + LE1 -- rq --- DB1[DB] + LE1 -- rq --- DB2[DB] + +``` + +Network diagram for Scenario 2 showing a sequence of components: TE connected to LE, which connects to TR, which connects to another LE, which connects to another TE. The first LE has two 'rq' connections to two separate DB components. + +Scenario 3 + +![Network diagram for Scenario 3 showing a sequence of components: TE connected to LE, which connects to TR, which connects to another LE, which connects to another TE. The TR component has two 'rq' connections to two separate DB components.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +``` + +graph LR + TE1[TE] --- LE1[LE] + LE1 --- TR[TR] + TR --- LE2[LE] + LE2 --- TE2[TE] + TR -- rq --- DB1[DB] + TR -- rq --- DB2[DB] + +``` + +Network diagram for Scenario 3 showing a sequence of components: TE connected to LE, which connects to TR, which connects to another LE, which connects to another TE. The TR component has two 'rq' connections to two separate DB components. + +T1166270-94/d09 + +| PE/FE | SCF | CCF/SSF | SDF o | SDF h | SRF | +|-------------------------------------------|-----|--------------|-------|-------|-----| +| SCP | c | – | c | c | – | +| SSP | – | c | o | o | o | +| IP | – | – | – | – | c | +| SDP | – | – | c | c | – | +| SSCP | c | c | c | c | o | +| NAP | – | c (CCF only) | – | – | – | +| c Core
o Optional
– Not recommended | | | | | | + +Scenario 1 + +![Network diagram for Scenario 1 showing a sequence of components: TE (FE1) connected to SSP LE (FE2), which connects to SCP (FE6). SCP (FE6) connects to DB (FE7) via Rq and to IP (FE8). The main path continues from TR (FE3) to LE (FE4) to TE (FE5).](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg) + +``` + +graph LR + FE1[TE +FE1] --- FE2[SSP LE +FE2] + FE2 --- FE3[TR +FE3] + FE3 --- FE4[LE +FE4] + FE4 --- FE5[TE +FE5] + FE2 --- FE6[SCP +FE6] + FE6 --- FE7[DB +FE7] + FE6 --- FE8[IP +FE8] + FE6 -- Rq --- FE7 + +``` + +Network diagram for Scenario 1 showing a sequence of components: TE (FE1) connected to SSP LE (FE2), which connects to SCP (FE6). SCP (FE6) connects to DB (FE7) via Rq and to IP (FE8). The main path continues from TR (FE3) to LE (FE4) to TE (FE5). + +Scenario 2 +Non-IN + +![Network diagram for Scenario 2 (Non-IN) showing a sequence of components: TE (FE1) connected to LE (FE2), which connects to TR (FE3), which connects to LE (FE4), which connects to TE (FE5). A bracket groups FE2, FE6, and FE7, with an Rq label pointing to it.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +graph LR + FE1[TE +FE1] --- FE2[LE +FE2] + FE2 --- FE3[TR +FE3] + FE3 --- FE4[LE +FE4] + FE4 --- FE5[TE +FE5] + FE2 --- FE6[FE6] + FE6 --- FE7[FE7] + FE2 -.-> Rq[Rq] + FE6 -.-> Rq + FE7 -.-> Rq + +``` + +Network diagram for Scenario 2 (Non-IN) showing a sequence of components: TE (FE1) connected to LE (FE2), which connects to TR (FE3), which connects to LE (FE4), which connects to TE (FE5). A bracket groups FE2, FE6, and FE7, with an Rq label pointing to it. + +T1166280-94/d10 + +NOTE – Non-IN configurations may not have similar relationships to IN. + +### Appendix I + +#### Access and identification procedure + +(This appendix does not form an integral part of this Recommendation) + +Regarding the access procedures, three different types can be foreseen: card reader procedure, auto access procedure and operator procedure. Since the choice of one of them is a national decision, it is out of the scope of this Recommendation. In this subclause an example of an ITCC call originated from a telephone not equipped with card reader using an auto access procedure (i.e. without operator assistance) is shown. + +The following is a high-level description of the network actions required when a user requests access to the ITCC service. + +#### Outline + +- 1) Service Access Code (SAC) and the Primary Account Number (PAN) input by the user. +- 2) Recognition of SAC, suspension of the call processing in CCF, information flow to SCF advising initiation of ITCC request. +- 3) The card acceptor's SCF, using the PAN information, applies call screening and retrieves from its own DB the card issuer identification information. Other call screening could be related to the retrieval of the appropriate language to use for the subsequent announcements. If it could be assumed that the ITCC card user DB can be deduced from the PAN number, the retrieve is not necessary. +- 4) Connection of SRF (Establish Temporary Connection). +- 5) Prompt for PIN code and collect it. +- 6) Prompt user to input destination number and collect it. + +This solution is only one of the possible implementations at the end of this procedure. Regardless of which implementation is used however, the SCF will have obtained the same information for the call at the end of this procedure. + +#### Information flow diagram + +The information flow shows the access and identification procedures. See Figure I.1. + +![Sequence diagram showing the successful access and identification procedure between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(di). The process starts with an ITCC Call Request (Note 1) to FE2, followed by Initial DP (Rp) to FE6, Request Report BCSM event (Rp) to FE6, and Retrieve (Rr) to FE8. FE8 sends Retrieve Result (Rr) to FE6, which then sends it to FE7 (Note 3). FE6 sends Establish Temporary Connection (Rp) to FE2, followed by SETUP req. ind. (Rp) to FE8. FE8 sends resp. conf. Assist Request Instr. from SRF (Rr) to FE6, which then sends it to FE2 (Note 4). FE6 sends Prompt & Collect User information (Rr) to FE8, which prompts the user for PIN code (Note 5). FE8 sends Collected User Information Prompt & Collect User Information (Rr) to FE6, which then sends it to FE2 (Note 6). FE6 sends Collected User Information (Rr) to FE8, which prompts the user for Destination Number. FE8 sends the Destination Number (Rr) to FE6, which then sends it to FE2.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) + +``` + +sequenceDiagram + participant FE2 as FE2 SSF/CCF + participant FE6 as FE6 SCF + participant FE8 as FE8 SRF + participant FE7 as FE7 SDF(ca) + participant FE9 as FE9 SDF(di) + + Note over FE2: ITCC Call Request (Note 1) + FE2->>FE6: Initial DP (Rp) + FE6->>FE2: Request Report BCSM event (Rp) + FE6->>FE8: Retrieve (Rr) + FE8->>FE6: Retrieve Result (Rr) + FE6->>FE7: (Note 3) + FE6->>FE2: Establish Temporary Connection (Rp) + FE6->>FE8: SETUP req. ind. (Rp) + FE8->>FE6: resp. conf. Assist Request Instr. from SRF (Rr) + FE6->>FE2: (Note 4) + FE6->>FE8: Prompt & Collect User information (Rr) + Note over FE8: (Note 5) + FE8->>FE6: Collected User Information Prompt & Collect User Information (Rr) + FE6->>FE2: (Note 6) + FE6->>FE8: Collected User Information (Rr) + FE8->>FE6: (Note 6) + FE6->>FE2: (Note 6) + +``` + +Sequence diagram showing the successful access and identification procedure between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(di). The process starts with an ITCC Call Request (Note 1) to FE2, followed by Initial DP (Rp) to FE6, Request Report BCSM event (Rp) to FE6, and Retrieve (Rr) to FE8. FE8 sends Retrieve Result (Rr) to FE6, which then sends it to FE7 (Note 3). FE6 sends Establish Temporary Connection (Rp) to FE2, followed by SETUP req. ind. (Rp) to FE8. FE8 sends resp. conf. Assist Request Instr. from SRF (Rr) to FE6, which then sends it to FE2 (Note 4). FE6 sends Prompt & Collect User information (Rr) to FE8, which prompts the user for PIN code (Note 5). FE8 sends Collected User Information Prompt & Collect User Information (Rr) to FE6, which then sends it to FE2 (Note 6). FE6 sends Collected User Information (Rr) to FE8, which prompts the user for Destination Number. FE8 sends the Destination Number (Rr) to FE6, which then sends it to FE2. + +T1166290-94/d11 + +#### NOTES + +- 1 The contents of SETUP req. ind. from FE1 (CCAF) to FE2 (SSF/CCF) are the SAC, the PAN and the Calling Number if present. This is one possible implementation. Other solutions can be envisaged. The nature of the req. ind. is dependent on the national network in use (PSTN, ISDN, PLMN). +- 2 On initiation of the ITCC service, control points (DPs) are dynamically armed by Request BCSM Event Report req. ind. in order to detect the calling party abandon. +- 3 This IF is optional and could be used to determine particular aspects of the service (e.g. SDM to be sent or country language to be played). +- 4 The order in which the SRF sends the SETUP resp. conf. and the Assist Request Instruction from SRF req. ind. is not significant. There are several SRF connection procedures, related to the physical location of the SRF. This example refers to a case in which there is a direct path between SCP and IP. +- 5 The user is prompted to input his PIN code by dialling digits or using a DTMF tone sender, for example. SCF-initiated disconnection of SRF is assumed, hence the SRF is not allowed to disconnect at the end of the user interaction. +- 6 The user is prompted to input the destination number by the SRF, using Prompt and Collect User Information req. ind. The number is reported to SCF using Collect User Information req. ind. + +FIGURE I.1/Q.86 +Successful access and identification procedure + +### **Appendix II** + +### **Validation Rejection and Retry procedure** + +(This appendix does not form an integral part of this Recommendation) + +The Validation Rejection and Retry procedure is used when a charge card validation result is not accepted. Treatment of the call at this point is implementation dependent. Figure II.1 uses a query to service databases to obtain information on services rejection and retry agreements. Using information retrieved, the calling user is requested to re-enter a PAN and PIN. This procedure ends when the SCF has collected the subsequent user information. + +#### **Outline** + +The following is a high-level description of the actions for a validation retry: + +- 1) Obtain service/user retry ability from card issuer and/or card accepting databases. +- 2) Request SRF to prompt and collect subsequent PAN/PIN. +- 3) Provide result from SRF to SCF. + +#### Information flow diagram + +The information flow shows the Validation and Retry procedure. See Figure II.1. + +![Sequence diagram showing the Validation rejection and retry procedure between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci).](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +The diagram illustrates the Validation rejection and retry procedure across five functional entities (FEs): FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). The process involves several steps, including queries, updates, and prompts, with specific data flows and error handling paths. + +**Sequence of Events:** + +- Initial Query (Note 1):** FE6 SCF sends a Query (671) to FE7 SDF(ca). FE7 SDF(ca) returns a Query Result (902) to FE6 SCF. +- Second Query (Note 2):** FE6 SCF sends a Query (672) to FE7 SDF(ca). FE7 SDF(ca) returns a Query Result (700) to FE6 SCF. +- Update and Confirmation (Note 3):** FE6 SCF sends an Update (650) to FE8 SRF. FE8 SRF returns an Update Conf. (674) to FE6 SCF. +- Prompt and Collect User Information (Note 4):** FE6 SCF sends a Prompt & Collect User Information (810) to FE8 SRF. FE8 SRF returns a Collected User Information Prompt & Collect User Information (622) to FE6 SCF. +- PIN Collection:** FE6 SCF sends a PIN code to FE2 SSF/CCF. FE2 SSF/CCF returns a "Provide your PIN" message to FE6 SCF. +- Final Query (Note 4):** FE6 SCF sends a Query Result (673) to FE7 SDF(ca). FE7 SDF(ca) returns a Query Result (900) to FE6 SCF. + +**Data Flows:** + +- Rp (Request Path):** FE2 SSF/CCF sends data to FE6 SCF. +- Rq (Response Path):** FE6 SCF sends data to FE8 SRF. +- Rr (Retry Path):** FE6 SCF sends data to FE7 SDF(ca). + +**Messages:** + +- "Wrong authentication, please retry. Provide your PAN" +- "PAN code" +- "Provide your PIN" +- "PIN code" + +Sequence diagram showing the Validation rejection and retry procedure between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). + +#### NOTES + +- 1 Once authentication fails, a count must be kept of the number of retry attempts. On first execution of this sequence, the limit set by the ITCC card issuer is retrieved from SDF(ci). +- 2 On first execution of this sequence, the retry limit of originating network of ITCC card acceptor is retrieved from SDF(ca). The counter logic resides in SCF. It is assumed that the SCF would use the smaller of these two values as the allowed limit, should they be different. +- 3 The count of authentication failures is now recorded in SDF(ci) for security and administration purposes. +- 4 If authentication fails, the specific reason for failure should not be advised to the user, for security reasons. Therefore both the PAN and the PIN will need to be re-entered. + +FIGURE II.1/Q.86 +Validation rejection and retry procedure + +## Appendix III + +### Maximum retries reached and service logic initiated release procedure (This appendix does not form an integral part of this Recommendation) + +Image: Sequence diagram showing the release procedure when maximum retries are reached. + +The diagram shows interactions between FE2 (SSF/CCF), FE6 (SCF), FE8 (SRF), FE7 (SDF(ca)), and FE9 (SDF(ci)). + +- FE6 (SCF) sends 'Play Announcement' (675) to FE8 (SRF). +- FE8 (SRF) plays an announcement to the user: "Retry limit exceeded. Please hang up". +- FE8 (SRF) sends 'SR Report' (811) back to FE6 (SCF). +- FE6 (SCF) sends 'Update' (624) to FE9 (SDF(ci)). +- FE9 (SDF(ci)) returns 'Update Result' (901) to FE6 (SCF). +- FE6 (SCF) sends 'Release Call' (679) to FE2 (SSF/CCF). +- FE2 (SSF/CCF) initiates a disconnect (disc >>>). + +T1166310-94/d13 + +NOTES + +- 1 The SRF now plays a final announcement to the user. SRF-initiated disconnection could be used to disconnect the SRF in this case but has not been shown. +- 2 The SDF(ci) is updated with record of the failed attempts if not already done. Security measures may be required to reject further attempts. The user is advised of failure and requested to hang up. The network then does forced release of the call and disconnects the SRF. +- 3 In the IN environment, the Release call requests a confirmation. + +FIGURE III.1/Q.86 +**Maximum retries reached and network initiated release** + +## Appendix IV + +### Outgoing call (This appendix does not form an integral part of this Recommendation) + +Outgoing calls from an ITCC user may be a single call, in which the procedure terminates at the end of the call or may allow follow-on (see Appendix VII). + +**Outline** + +The following is a high-level description of the actions required to set up an outgoing call: + +- 1) Disconnection of SRF. +- 2) Arm triggers to detect call set-up failure and to detect mid-call feature activation (if required) and activate an application timer on "Called party no answer" (if required). + +**Recommendation Q.86 (10/95)**      25 + +- 3) Furnish charging operation (or other charging operation) for generation of billing record. +- 4) ApplyCharging operation to request information on call consuming. +- 5) Connect to destination number using Connect IF. + +#### Information flow diagram + +The information flow shows the outgoing call procedure. See Figure IV.1. + +![Sequence diagram showing the outgoing call setup procedure between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci).](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant FE2 as FE2 SSF/CCF + participant FE6 as FE6 SCF + participant FE8 as FE8 SRF + participant FE7 as FE7 SDF(ca) + participant FE9 as FE9 SDF(ci) + + Note over FE2, FE9: Rq, Rp, Rr interfaces + + rect rgb(240, 240, 240) + Note left of FE2: (Note 1) + FE2->>FE6: Disconnect Fwd (212) + FE2->>FE6: Connection RELEASE req. ind. + FE6->>FE8: RELEASE (801) + FE8->>FE6: resp. conf. (252) + end + + FE6->>FE2: RequestReport BCSMEvent (214) (Note 2) + FE6->>FE2: Furnish Charging Info. (215) (Note 3) + FE6->>FE2: ApplyCharging (216) (Note 4) + FE6->>FE2: Connect (217) (Note 5) + Note right of FE6: Basic Call Set-up + +``` + +The diagram illustrates the outgoing call setup procedure involving the following entities: FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). Interfaces Rq, Rp, and Rr are indicated. A shaded box (Note 1) contains the initial release sequence. Subsequent operations from FE6 to FE2 include RequestReport BCSMEvent (Note 2), Furnish Charging Info. (Note 3), ApplyCharging (Note 4), and Connect (Note 5), followed by Basic Call Set-up. + +Sequence diagram showing the outgoing call setup procedure between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). + +T1166320-94/d14 + +#### NOTES + +- 1 The SRF is released (SCF initiated). If the follow-on procedure is foreseen the SRF may be not released. +- 2 Request Report BCSM Event req. ind. is used to arm Control Points (DPs) for Called disconnection and call set-up failure to allow follow-on. +- 3 Furnish charging operation (or other charging operation) for generation of billing record. +- 4 ApplyCharging operation to request information on call consuming. +- 5 Connect to destination number. + +FIGURE IV.1/Q.86 + +#### Outgoing call set-up + +### Appendix V + +#### **Calling party abandon** + +(This appendix does not form an integral part of this Recommendation) + +![Sequence diagram for 'Calling party abandon' showing interactions between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci).](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant Ext as External + participant FE2 as FE2 SSF/CCF + participant FE6 as FE6 SCF + participant FE8 as FE8 SRF + participant FE7 as FE7 SDF(ca) + participant FE9 as FE9 SDF(ci) + + Note over FE2, FE6: Rp + Note over FE6, FE8: Rq / Rr + Note over FE6, FE7: Rq + Note over FE6, FE9: Rq + + Ext->>FE2: DISC.321 req. ind. + Note right of FE2: 201 + FE2->>FE8: RELEASE req. ind. + Ext-->>FE2: RELEASE req. ind. + Note right of FE2: 251 + FE6->>FE8: RELEASE + Note right of FE8: 801 + FE8-->>FE6: resp. conf. + Ext->>FE2: RELEASE resp. conf. + Note right of FE2: 202 + FE2->>FE6: EventReport BCSM + Note right of FE6: 601 + +``` + +The diagram illustrates the sequence of events for a calling party abandon. It features five main entities: FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). The interactions are as follows: + +- FE2 SSF/CCF** receives an external **DISC.321 req. ind.** (state 201) and a **RELEASE req. ind.** is sent to **FE8 SRF**. +- An external **RELEASE req. ind.** is received by **FE2 SSF/CCF** (state 251). +- FE6 SCF** sends a **RELEASE** message to **FE8 SRF** (state 801), which returns a **resp. conf.**. +- FE2 SSF/CCF** receives an external **RELEASE resp. conf.** (state 202) and sends an **EventReport BCSM** to **FE6 SCF** (state 601). +- Interfaces are labeled as **Rp** (FE2-FE6), **Rr** (FE6-FE8), and **Rq** (connecting FE6 to FE8, FE7, and FE9). + +Sequence diagram for 'Calling party abandon' showing interactions between FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). + +FIGURE V.1/Q.86 +**Calling party abandon** + +**Appendix VI** + +**Calling and called party initiated disconnection** + +(This appendix does not form an integral part of this Recommendation) + +![Figure VI.1/Q.86: Calling party initiated disconnection](853ef5420f0432e626e83987e3f38a0b_img.jpg) + +``` + + sequenceDiagram + participant DISC as DISC.321 req. ind. + participant FE2 as FE2 SSF/CCF + participant FE6 as FE6 SCF + participant FE8 as FE8 SRF + participant FE7 as FE7 SDF(ca) + participant FE9 as FE9 SDF(ci) + + Note over FE2, FE6: Rp + Note over FE6, FE8: Rr + Note over FE6, FE7: Rq + Note over FE6, FE9: Rq + + DISC->>FE2: + Note right of FE2: 203 + FE2->>FE6: EventReport BCSM (601) + Note right of FE2: 219 + FE2->>FE6: ApplyCharging Report (602) + +``` + +FIGURE VI.1/Q.86 +**Calling party initiated disconnection** + +Figure VI.1/Q.86: Calling party initiated disconnection + +![Figure VI.2/Q.86: Called party initiated disconnection](5bf611979ab0126ebd219a1c6eda6b1e_img.jpg) + +``` + + sequenceDiagram + participant FE2 as FE2 SSF/CCF + participant FE6 as FE6 SCF + participant FE8 as FE8 SRF + participant FE7 as FE7 SDF(ca) + participant FE9 as FE9 SDF(ci) + participant DISC as 431-451 + + Note over FE2, FE6: Rp + Note over FE6, FE8: Rr + Note over FE6, FE7: Rq + Note over FE6, FE9: Rq + + DISC->>FE9: + FE6->>FE2: RELEASE req. ind. + Note left of FE2: 421 + Note left of FE2: 270 + FE2->>FE6: EventReport BCSM (603) + Note left of FE2: 219 + FE2->>FE6: ApplyCharging Report (602) + +``` + +FIGURE VI.2/Q.86 +**Called party initiated disconnection** + +Figure VI.2/Q.86: Called party initiated disconnection + +28 **Recommendation Q.86 (10/95)** + +### Appendix VII + +#### Follow-on recognition + +(This appendix does not form an integral part of this Recommendation) + +![Sequence diagram for successful follow-on recognition involving FE2, FE6, FE8, FE7, and FE9.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The diagram illustrates a sequence of events for successful follow-on recognition. It features five functional entities (FEs) represented as vertical lifelines: FE2 SSF/CCF, FE6 SCF, FE8 SRF, FE7 SDF(ca), and FE9 SDF(ci). The sequence begins with FE2 sending a 'ra' (request acknowledgment) to FE6. FE6 then sends a 're' (request establishment) to FE8, with a note '(Note 1)' indicating a direct path. FE8 sends a 'SETUP req. ind.' (Setup request indication) to FE2. FE2 responds with a '250' (successful completion) to FE8. FE8 then sends a 'SETUP resp. conf.' (Setup response confirmation) to FE6. FE6 sends an 'Assist Request Instr. from SRF' to FE8. FE8 prompts and collects user information, sending a '620' (collect user information) to FE6. FE8 then sends an '810' (enter new destination) to FE2. FE2 sends a 'response=xxx' to FE8. Finally, FE8 sends 'Collected User Information' to FE6, with a '622' (collected user information) message. + +``` + +sequenceDiagram + participant FE2 as FE2 SSF/CCF + participant FE6 as FE6 SCF + participant FE8 as FE8 SRF + participant FE7 as FE7 SDF(ca) + participant FE9 as FE9 SDF(ci) + + FE2->>FE6: ra + FE6->>FE8: re (Note 1) + FE8->>FE2: SETUP req. ind. + FE2->>FE8: 250 + FE8->>FE6: SETUP resp. conf. + FE6->>FE8: Assist Request Instr. from SRF + FE8->>FE6: 620 Prompt and Collect User information + FE8->>FE2: 810 Enter the new destination + FE2->>FE8: "response=xxx" + FE8->>FE6: 622 Collected User Information + +``` + +Sequence diagram for successful follow-on recognition involving FE2, FE6, FE8, FE7, and FE9. + +T1166360-94/d18 + +#### NOTES + +1 See Note in Figure 4. + +2 The order in which the SRF sends the SETUP resp. conf. and the Assist Request Instruction from SRF req. ind. is not significant. There are several SRF connection procedures, related to the physical location of the SRF. This example refers to the case in which there is a direct path between SCP and IP. + +FIGURE VII.1/Q.86 + +#### Successful follow-on recognition + +### Appendix VIII + +#### Network initiated disconnection + +(This appendix does not form an integral part of this Recommendation) + +![Sequence diagram for network initiated disconnection showing interactions between FE2, FE6, FE8, FE7, and FE9.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +The diagram illustrates a network-initiated disconnection sequence. It features five functional entities (FEs) represented as vertical lifelines: FE2 (SSF/CCF), FE6 (SCF), FE8 (SRF), FE7 (SDF(ca)), and FE9 (SDF(ci)). + +- External Event:** A message labeled "DISC.421 req. ind." with four arrowheads points to the start of the FE2 lifeline. +- Internal Action:** Inside the FE2 lifeline, the number "212" is present. +- Message Rp:** A message labeled "Disconnect Fwd Connection" is sent from FE2 to FE6. This message is associated with the label "Rp" above the FE2 lifeline. +- Internal Action:** Inside the FE2 lifeline, the number "251" is present. +- Message Rr:** A message labeled "RELEASE req. ind." is sent from FE2 to FE6. This message is associated with the label "Rr" above the FE6 lifeline. +- Message Rq:** A message labeled "RELEASE resp. conf." is sent from FE6 to FE8. This message is associated with the label "Rq" above the FE6 lifeline. +- Internal Action:** Inside the FE8 lifeline, the number "801" is present. +- Message Rq:** A message labeled "Release Call" is sent from FE6 to FE2. This message is associated with the label "Rq" above the FE6 lifeline. + +Sequence diagram for network initiated disconnection showing interactions between FE2, FE6, FE8, FE7, and FE9. + +T1166370-94/d19 + +FIGURE VIII.1/Q.86 +Network initiated disconnection \ No newline at end of file diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5120e9368da9216da33d814de0220af6d520979d --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a043be9fc5ff783dbfd1b53dd85c1f777007663236d81135021822ef8bbc3e8 +size 23004 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f2e9461e4f0b79a8c42a06923b2840e15bc8426 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70c21e54c7fddd5e43138058b5324fc2643a5ffb8b2c7afdb20c14456016f219 +size 8210 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6265282d4a753044619b7216b1fc0aa76264778 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:816a73bf9dd67641eb07d6e30adcbb8c13d5976ef77dd52f5be7e708a474cba6 +size 43376 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28aa54882b532839d277a8aceaa4a6d11ad94a2f --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc997ec661847060d3196e9851020d5e5c39fa05153ac708cc41e174cb6ee88c +size 81608 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52d37885bc70f93f2c649ee667a6a34d9a81f942 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4162d4f2a928c47f7aad7d13e0f5d5d0b3e8ebad6ba6b41a4e26f394c86152c6 +size 34031 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4114cc6c1c0edf407c520eadc2f43bd2c6840f33 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a3a2dc3aa5fa8881fcbbfb2d4e3be908e32347096435834b98118afd4c93749 +size 36774 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1a8810ffa060e0692f69513920f3f36b71ece97 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa826bb578d3bfeae66f92b051bfd67373782c85e0031894504f22a622bcd981 +size 106095 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d905d72aa85ac39d00db54f08419910ed5d30c40 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f47ce8f422fcd832fe599c133540014f235701efcbf7a3690d05307db1cadacb +size 114475 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..332639688842b6e83669c51f2feaf818c31e8f51 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:056635e0180d71406ad27dbf184ef6afd76d7bc91d698332000116d5fe8e45be +size 120246 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca93e7c713b5df6008e18fa6613b8aa8be8ef691 --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f969f2940547c79fd5bdebb8e9fd04bb53c39c3c68d26fcc8d5a35b7dee0eb46 +size 45933 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f439542c8ac5f0066453cded7f59d9847c7a77dd --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8f2c0db06cfd3294a2dbb28fc51874b8d86de700ff0aa90687a9617cdf98b7b +size 46065 diff --git a/marked/Q/T-REC-Q.920-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.920-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd9aefc15b85b0bf8e96159d0fefb1a38490572d --- /dev/null +++ b/marked/Q/T-REC-Q.920-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf446bf5490574067cd949eef3cf4cd34ad44c6a085da042750c980cacbe8f57 +size 72609 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52ca5bc907626a7398367ceb6d2b2bcb4b6b7138 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f2a06c605bc610bce5b07ccad4337ccce9fc83962b20e6d7d4dfb641640cb02 +size 114991 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e7f4c5d38f19884360b373b15ed3df5650d1ab3 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b368222bc44372be3f9dbf5c6e19b0d8be6c6f5b9bc7dc2c4faed2dfe4d6450 +size 98293 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d41cec764fe280255aa371efdc4fc68ee204bf66 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed817361f552fb014e59e2822a144f642c4529e5e661e45a08d76c928f54ddd6 +size 51973 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c7d0e8e6ae9ed15896694b9d86900e46760442a --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ee83a4c2f5f18faa69038d720b941e45c7d0deaeb6f8840a5db858c52c1dcba +size 104631 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21abb2e336629c9a4aa053388d185b1b5c603662 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99543f26596328b91a29c1b09f405d207190dfeae7a81450ef8003cb61ce4737 +size 111243 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16f1f91f10be1ee941ecb0410b1febdf59de5bb8 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72a34031073a81c93c230657202a2dfba3bc557a2b7d942b85f34176dcfbc8be +size 95529 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ab77a88345b323a8120f19e4a8c1057ded112d7 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c5ad2fd3656ad09a5fa9f5752e19c14e288b7f2e46e092a009300147e588169 +size 89433 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..516600f465a24559321359b5fa6d2191ed322b4e --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd92f5d281ccdf63d2021c075b89a97d99e38082217078a4d6fc13e9477a94e7 +size 85844 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40c6157b4f69c338149f48284e1106e4ff958857 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22fedff7c20a2f00a806e729177f6024303ec9d57557df91becafd6a89d9a148 +size 31059 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e09497be9ff20d262fad9ce6f40028acd9beb836 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d6f3405fae805812dd05acd5b0f4d3218bcce09dd60e8702c8744e417486e58 +size 92960 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05a4d86136d60a327a8e722fbc0bbb28431d0cf3 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d7ecf073ef71d3b09788bf7ee06cfff1b4500ce8f6895c34816888b922f863a +size 101421 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02900702d2f5ef2a62515f45fc0e5ab14a29b2b7 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53a0eedb9875c9f1367b00c1e2b34186ba50350a036d3dca59280cd3ab3d9e5a +size 35254 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9b7fd7099cb389e6317ad4afce06cb8731ac0e2 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5224f2658d29526a349f15e387c989a997d56e954d66bb24b81d08b5a6c30537 +size 7369 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fd2f8029989252eeb772b0c3072238c10910f5c --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e52d6f7e2bedd1643156b183c5f506a4486a7ad56c920164dbcb3204713a582 +size 116927 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56e3001285e2b147f33fa0ab0280f8f0ae7d1812 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9894ff864dc8768f3a89d293fb320ea69bb196be847440b6aec3465ba334769 +size 100910 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..821c46580af5837716dcf006fabfee3421fe3d5d --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02646e797df130c0706fbd5cb34ae7ed2bff0dc605e6e7c2b2c55160a812fa67 +size 97275 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c9c99e0c1fa91af44fa9b5604586d17487c7340 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f5e606d75022346671567f7b366303c74261b081c7a063251ee6f296a4a41f2 +size 47022 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5135d94c10d92009ca497321f5f83621151c0f04 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47b02f708890e9a1fc75b034d3aa539808889c0840291a6e35190ae57e131185 +size 139109 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e05454ab26bc504fc76d82e066bddba2564ab650 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c16da86b3784c2733a78893e4bb5b06ca88ae729a7868d45d77acb7dbe485236 +size 96888 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7cb004d537feec4ceeb0c8c81b561cde09ed001 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91bb09a2c8ab37833d5a4ae5e80176cad9433343b377576c9fdb208c8ec2b8fa +size 137213 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17cc7b61c1483db9d9463b76229cd30ebf13d34a --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c0458a9dbf843a386598dabdcbe4fe201b87509f338212836771d709811b03f +size 63773 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86b46418d784d61431952c2b82964f6cf7c708a1 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09de2ae9ea25cf7eda645247413af37b0fca5eb0e44c0b66fc24045bd9cc5df3 +size 73140 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0b8ddd09bcbd136b33806f4a6f0173d72e8e50e --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31c12c1a1ff86855bb8baa4fde91b3f5da9260276dc5607ba4886124f1ede45f +size 102540 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b99727d717cff876a841c4bca6504df41b1c26c --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d76b6aaac335dca1f3e799161d73fd3c33d63dec19d2750142a70cc9eef9fa2e +size 130969 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638c23b3176a21d3b56e9f20df2781661cd616ab --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a406acf742070276575f469b798872180fd87b6400497b646adea9d322051831 +size 152228 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b034198952f753c99639825d6b631edbae54ad9 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa05e37913df4cecfa756af4efcec5bfe714657a28eabeaf5fdd3a5ceb686721 +size 5676 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76947feeb59932746955dcd520f53c8b234a3937 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d5422479c2b4570989e064d91eea8fd11b95b89ede0f23a1c981ca6ef47ff04 +size 92616 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf8bbc0285816b38cd388482245bf8d3888e6084 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:606e369b4df598487d68e06650694b0afb1d0a6c3adbd5b1efd2c080a97a8f8d +size 78127 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c242fb797e297807f428fdd928919e7ca8fd0b4 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf9a13886971ec248f8105e7cc6e591267cc85ec2b622252182daf1cbe3d6726 +size 127583 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9aaaa6ae05ca4b6deff6a70236a633ce710d4b35 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a290090315012a386cdb87104cbd1c271c946ffb3aca44adfd10c4a6e6448752 +size 86825 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4734b6a0989bdda2f7e7478ee282d9f16204b86d --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97c8215619778342ad18913e52ff43c1076be9e1e06dddf4b2646c8d7d222180 +size 79108 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/9a6db092db1d77918bfc7e163c628848_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/9a6db092db1d77918bfc7e163c628848_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0c5de0291afcb56f78c6a2b776c3defde3a8cdf --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/9a6db092db1d77918bfc7e163c628848_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ab98e5b8803a0d714472d19c0ff7d63bc400030cff59e000509f471eb913e60 +size 32810 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8ca9e73386ed95a971eb08e7f3fd8f01015c931 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ff7cf023c3df3411e7a2a51f4d4d583d761db458b0cc8ed0bc3917ec069a519 +size 40385 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f45cbb6b0ce6f4eeaa14f429982260753f92a51 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/a780a960b3f2de2493d5785bedae10ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d31ea42a9f82f50ff5987e8c6a1d841bcba6b32193fa22df353d39ecedfa1bf +size 99532 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58e1fd9548fe2b3083f274cbfdda8f7e68fb7eee --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d4966c11c86d3f237096f01fd034b120f02b6de9f2e1d0081f657e5309287ea +size 107641 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a1e43bd288160879dd1475362bc1eac45fba492 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2709094b118ac2199f845d7f942fd421318973d04eac866e7d5d2b9a81437fdb +size 93031 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb8b759a1d8b81ecf3592535b7b3dd2ccfff13e0 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:398facfa3e3e3187e5c14cb3873eb4e36933d67f452726ad6691fee8178d2167 +size 55223 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31216cedbb38dbeed30149965b162ec11dc22b9a --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c843865177da9ee4d0b8023909693755404e9db35cb9d79fad338ee4a3266a8 +size 109970 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbdbc3c7816486f0951a84f802e1545c0a5a243d --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48b56ef086fb0fbb4343580fabb31669e2b7c5e672149e15f2b94a6531cda45d +size 102642 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47395e9ef0ad45c3f42ffdba0b3db4bf5b26e2a8 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a3f99b0a50a1e09e22d42788a7603afa6c881dbe55ee661677b85db1a936936 +size 48215 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98786c87f912ef7f93936b6847fa36cd97526563 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72f645cd88ca359cb779a6afdbb552a0b7124339a4a49651b955d91afca77235 +size 94970 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98e59585aeb06f5a464911f4dcf05bafa4735011 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c174d135f7a87fee9c7273c99843f69c812f41f33042229611ea6296ab2fad32 +size 150290 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9291162f9434e525e2e2bdc8b31f83d51f7bc4f --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69f52473b01aeba96f1800ea7154b9b20a574c91bc06657ef78e0dba8dafd4bf +size 62192 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aca850a5fb95339b08c9db0ba1fce0aa19afa88e --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64ec376123242e724181edf3cd5887fb18ba946e1bc4838025a62758c680ae17 +size 58866 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65b1884faabe7f71b2bfc78f4153938a1e1ecb7f --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d45d91106a14d6bdd1d57f2188d611fddeda3a6dc8b8881d57582cef2706f63 +size 46612 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb809e7bd7abaf59a9c0fa9e857c8830086e6d92 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a9c38768b049cc41b32231ad38b50d1f3fdca7923a9dce27776d8b402b0db9f +size 45441 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..865fee0f973492405794a7589a1023fc54db5221 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17f863f880bb98504a47a3297429b87dc5bbb27edd23e3e7dd25062345e1cfd9 +size 113204 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/dcf83796ccf494110638fbd4677b931d_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dcf83796ccf494110638fbd4677b931d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4922a88c7a4b4678da0f1707a3b8a2f9b37f5ccd --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dcf83796ccf494110638fbd4677b931d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79fb2ebb0a2da45c749767f83ea81967974028dc81fda0d4e12116dc1e8733ea +size 23549 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b0df0c4b5d1898e1a3b36c4173168d62b05e64c --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45a1418d8032c5398df5302f08177ad7a3c0240e70d6b00bc449621c16d29b8e +size 100368 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85a7f75d9c9b8625a1788efa988ec1eb2e2b71a1 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23226084129848527ab6b721e059fef8d5542300e10486e2a333730d66874675 +size 132789 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0b00c4ffec84cca074e431e2fd4e56ff7a95e70 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f556ad803782d577385bc7200c524d9863e8c228cc26cf5d03b05d8a785a2539 +size 127638 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc5be6314b12c435ce49a7a9a8dddd38535ec25e --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e10844c3ac5041e2ead6a5b3015e297343af9134689d0f210e33af587a85138 +size 43028 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32f816c1dcaf3fdf8395c7259581a81946276739 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f796387a1df5cf1fa29b33789eced02e7392a7e7fe3af66f0b2b46d9c5a3d5c +size 107152 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2e4e66c0b31cb5d4cd1c1cbd2ebad49ee14a27c --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e952c6ebf54df01a005f50de17940f17baf1f5249996d481ede5443a4343703 +size 72297 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7c0a8547e20fb848d2425acda43ec617915dddc --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a562f4d379638ea94b23dd6fd67d960b168282dbda86b845ec259d966a99335b +size 119532 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37b38e18b570ac2771024cb4f1346f69ad6c4aab --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33183c660e9d062f52f97819dc562c824eb8c5379e1f419d92bae843e2b6cf54 +size 103341 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54d97e5de20d4cc31c57e1eab9f5b4dff71b61f1 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03a3f090b2332845724389e51d0445bcdeaaa07541c17f153f9d42ae339be6d3 +size 125289 diff --git a/marked/Q/T-REC-Q.922-199202-I_PDF-E/ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg b/marked/Q/T-REC-Q.922-199202-I_PDF-E/ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1cf90c01d5b0465661a879eb5c9beba72818373 --- /dev/null +++ b/marked/Q/T-REC-Q.922-199202-I_PDF-E/ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de3b327fa6281adc2a4597232cfdf3c0445122f999d2fdd6e3016c048b99384c +size 17454 diff --git a/marked/Q/T-REC-Q.951.6-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.951.6-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7d7360da4e2bf7f5d586d494a72eb03dc7f89628 --- /dev/null +++ b/marked/Q/T-REC-Q.951.6-199303-I_PDF-E/raw.md @@ -0,0 +1,1709 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt symbol.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt symbol. + +INTERNATIONAL TELECOMMUNICATION UNION + +# ITU-T + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +## Q.951 + +(03/93) + +# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 STAGE 3 DESCRIPTION FOR SUPPLEMENTARY SERVICES USING DSS 1** --- + +## **STAGE 3 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES USING DSS 1** + +**Clause 3 – Calling Line Identification Presentation (CLIP)** + +**Clause 4 – Calling Line Identification Restriction (CLIR)** + +**Clause 5 – Connected Line Identification Presentation (COLP)** + +**Clause 6 – Calling Line Identification Restriction (COLR)** + +## **ITU-T Recommendation Q.951** + +(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.951, clauses 3, 4, 5 and 6 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. + +# CONTENTS + +| | Page | +|--------------------------------------------------------------------------------------------------------|-------------| +| 3    Calling Line Identification Presentation (CLIP) ..... | 1 | +| 3.1    Definition..... | 1 | +| 3.2    Description..... | 1 | +| 3.3    Operational requirements..... | 2 | +| 3.4    Coding requirements..... | 2 | +| 3.5    Signalling requirements..... | 2 | +| 3.6    Interaction with other supplementary services ..... | 6 | +| 3.7    Interaction with other networks ..... | 8 | +| 3.8    Signalling flows ..... | 9 | +| 3.9    Parameter values (timers) ..... | 9 | +| 3.10    Dynamic description ..... | 9 | +| Annex A (referred to in clause 3) – Two Calling party number information elements delivery option..... | 12 | +| A.1    Scope ..... | 12 | +| A.2    Additional procedures at the destination network side ..... | 12 | +| A.3    Actions at the originating user ..... | 12 | +| A.4    Additional actions at the originating local exchange ..... | 12 | +| 4    Calling Line Identification Restriction (CLIR) ..... | 13 | +| 4.1    Definition..... | 13 | +| 4.2    Description..... | 13 | +| 4.3    Operational requirements..... | 14 | +| 4.4    Coding requirements..... | 14 | +| 4.5    Signalling requirements..... | 14 | +| 4.6    Interaction with other supplementary services ..... | 15 | +| 4.7    Interaction with other networks ..... | 17 | +| 4.8    Signalling flows ..... | 17 | +| 4.9    Parameter values (timers) ..... | 17 | +| 4.10    Dynamic description ..... | 17 | +| 5    Connected Line Identification Presentation (COLP) ..... | 17 | +| 5.1    Definition..... | 17 | +| 5.2    Description..... | 17 | +| 5.3    Operational requirements..... | 19 | +| 5.4    Coding requirements..... | 19 | +| 5.5    Signalling requirements..... | 21 | +| 5.6    Interaction with other supplementary services ..... | 25 | +| 5.7    Interaction with other networks ..... | 27 | +| 5.8    Signalling flows ..... | 27 | +| 5.9    Parameter values (timers) ..... | 27 | +| 5.10    Dynamic description ..... | 27 | +| 6    Connected Line Identification Restriction (COLR) ..... | 30 | +| 6.1    Definition..... | 30 | +| 6.2    Description..... | 30 | +| 6.3    Operational requirements..... | 30 | +| 6.4    Coding requirements..... | 31 | +| 6.5    Signalling requirements..... | 31 | +| 6.6    Interaction with other supplementary services ..... | 31 | +| 6.7    Interaction with other networks ..... | 33 | +| 6.8    Signalling flows ..... | 33 | +| 6.9    Parameter values (timers) ..... | 33 | +| 6.10    Dynamic description ..... | 33 | + + + +## STAGE 3 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES USING DSS 1 + +*(Helsinki, 1993)* + +# 3 Calling Line Identification Presentation (CLIP) + +## 3.1 Definition + +**calling line identification presentation (CLIP)** is a supplementary service offered to the called party which provides the calling party's ISDN number, possibly with sub-address information to the called party. + +## 3.2 Description + +#### 3.2.1 General description + +This supplementary service provides the ability of indicating the ISDN number of the calling line, with possible additional sub-address information (i.e. the Calling party sub-address information element), to the called party. + +The information provided to the called user consists of the ISDN number of the calling user in a form sufficient to allow the returning of the call (i.e. a subscriber number, a national number or an international number and optionally a sub-address if provided by the calling user). + +#### 3.2.2 Specific terminology + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the presentation of the calling line identification information in association with incoming calls. The served user is also known as the called user. + +A **calling user** is the user that initiated an incoming call at the served user. The calling user need not have subscribed to the Calling Line Identification Presentation supplementary service. + +An **ISDN number** is a number conforming to the numbering plan structure specified in Recommendation E.164. + +An **address** is the number of the calling user (normally ISDN number), and a sub-address if provided by that user. + +An **international number** is an ISDN number structured as specified in Recommendation E.164. + +A **national number; national significant number** is an ISDN number structured as specified in Recommendation E.164. + +A **subscriber number** is an ISDN number structured as specified in Recommendation E.164. + +A **default number** is an agreed number between the user at the calling side and the network provider. + +A **special arrangement** is an arrangement between a customer and a public network operator whereby customer supplied calling numbers are not screened by the public ISDN. + +CLIP     Calling Line Identification Presentation + +CLIR     Calling Line Identification Restriction + +#### **3.2.3 Qualification on the applicability to telecommunication services** + +See Recommendation I.251.3. + +#### **3.2.4 State definitions** + +No specific state definitions are required. + +## **3.3 Operational requirements** + +#### **3.3.1 Provision/withdrawal** + +See Recommendation I.251.3. + +NOTE – Annex A contains some additional procedures to support the two Calling party number information elements delivery option. This is a network option. + +#### **3.3.2 Requirements on the originating network side** + +All information pertaining to CLIP, shall be inserted in the SETUP message sent as part of the basic call procedures according to 5/Q.931. + +In the case where no information is provided by the calling user (as part of the basic call procedures) the network shall provide the default number associated with the user access (in which the call was generated) in the originating local exchange. + +When the calling party information is provided by the user, the network can only verify that the number is within the range allocated to that user. + +Where a special arrangement exists with the calling user, no screening of the calling number they supplied, shall be performed. + +#### **3.3.3 Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **3.3.4 Requirements on the destination network side** + +See 3.5.2.3. + +### **3.4 Coding requirements** + +All information pertaining to CLIP is inserted in the SETUP message. 4.5.10/Q.931 and 4.5.11/Q.931 give the coding for the Calling party number and Calling party sub-address information elements which are required to support this service. The purpose of the Calling party number information element is to identify the origin of a call. The purpose of the Calling party sub-address information element is to identify a sub-address associated with the origin of the call. + +## **3.5 Signalling requirements** + +#### **3.5.1 Activation/deactivation/registration** + +Not applicable. + +#### **3.5.2 Invocation and operation** + +##### **3.5.2.1 Actions at the originating local exchange** + +###### **3.5.2.1.1 Normal operation** + +###### **3.5.2.1.1.1 Actions at the originating user** + +These procedures shall be provided as part of the basic service and the calling user need not have subscribed to the CLIP supplementary service. + +The numbering plan identification, to be indicated with the Calling party number information element, sent by the calling user, shall be either “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”. + +NOTE – Either coding may be used and the treatment of both by the network is identical. + +Where the calling number included by the calling user is complete the type of number to be indicated within the Calling party number information element, sent by the calling user, shall be one of the following: + +- “*Subscriber number*” – In the case where the complete subscriber number is sent. +- “*National number*” – In the case where the complete national number is sent. +- “*International number*” – In the case where the complete international number is sent. + +Where a partial calling number is included by the calling user (e.g., to indicate digits specific to the Direct-Dialling-In or the Multiple Subscriber Number supplementary services) the user shall set the type of number to be indicated within the Calling party number information element to “unknown”. + +###### **3.5.2.1.1.2 Actions at the originating local exchange if a special arrangement does not apply** + +These procedures shall be provided as part of the basic service and the calling user need not have subscribed to the CLIP supplementary service. + +When a SETUP message is received from the calling user, the network shall check to see if the Calling party number and Calling party sub-address information elements are included. + +If the Calling party number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Calling party number information element and process the call as if that information was not received. + +The network shall set the value of the screening indicator based on the outcome of the screening of the calling number. The network shall disregard any value of the screening indicator, if received from the calling user. + +If the Calling party number information element is included, the network shall perform the screening function. + +NOTE 1 – Some networks may accept a full ISDN number in a Calling party number information element with the addition of a prefix or escape digits to the number digits field and the type of number field set to “unknown”. + +If the calling number received from the calling user is determined to be correct, the network shall set the screening indicator to “user-provided, verified and passed”. + +If the screening function fails the network shall note that the screening is failed and shall use a default number associated with the calling user. The network shall set the screening indicator to “network provided”. + +If the SETUP message does not contain the Calling party number information element the network shall use a default number associated with the calling user. The network shall set the screening indicator to “network provided”. + +In the case where the calling user provides only partial calling number information and the number is a valid digit sequence for the user access arrangement, the network shall complete the number as appropriate. The network shall set the screening indicator to “user-provided, verified and passed”. + +NOTE 2 – In some cases the network cannot guarantee that the completed number identifies an end user. + +The information determined by the procedures above, shall be forwarded to the destination local exchange, in association with the basic call request. + +The presentation indicator, as determined by the procedures of the CLIR supplementary service (see clause 4), shall be forwarded to the destination local exchange, in association with the basic call request. + +If the Calling party sub-address information element is available, it shall be passed transparently through the network. + +The actions at the originating local exchange when special arrangement does not apply are summarized in Table 3-1. + +TABLE 3-1/Q.951 + +###### **Information provided by the calling user and by the network when special arrangement does not apply** + +| Information provided by the calling user | | Information provided by the network to the called user | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------| +| Calling number received from the calling user (octet 4) | Type of number (octet 3) | Calling number forwarded (if CLIR is not activated) (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No calling party number information element is provided by the calling user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 7) | +| Valid part of the number not sufficient for returning the call (Note 2) | “Unknown” | Completion of the number (Note 3) | User-provided verified and passed (Note 4) | “International number” or “national number” (Notes 1, 7) | +| Correct complete calling party number (Note 5) | “Subscriber number” or “national number” or “international number” | Complete calling party number | User-provided verified and passed | “International number” or “national number” (Notes 1, 7) | +| Incorrect number (Note 6) | Any type of number | Default number stored at the network side sufficient for returning the call | Network-provided | “International number” or “national number” (Notes 1, 7) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network path where the destination is in a different country.

2 This assumes that the user's equipment provides that part of the number pertaining to its own (private) domain. This may be multiple subscriber number digits provided by a terminal equipment or an extension line number provided by a private ISDN. The network shall interpret the number digits and check if it is a valid digit sequence according to the agreements existing between the calling user and the network provider.

3 Completion means that the remaining part of the ISDN number associated with the appropriate access is added to the user provided part of the number.

4 The term “verified” implies matching the user provided number or part of this number with the range(s) of numbers stored at the network side and it implies at least a valid format of user provided number information.

5 The term “correct” implies, from the network point of view, matching the subscriber number provided by the user with one of the numbers in the set of numbers stored at the network side.

6 The number provided by the user is discarded.

7 As a network option the type of number forwarded to the called user may be coded “unknown” when a prefix is added to the number, in which case the number is organized according to the network dialling plan, i.e. prefixes or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +###### 3.5.2.1.1.3 Actions at the originating local exchange if a special arrangement applies + +These procedures shall be provided as part of the basic service and the calling user need not have subscribed to the CLIP supplementary service. + +When a SETUP message is received from the calling user, the network shall check to see if the Calling party number and Calling party sub-address information elements are included. + +If the Calling party number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Calling party number information element and process the call as if that information element was not received. + +If the Calling party number information element is received with the coding of the type of number field other than “national number” or “international number”, then the network shall discard the Calling party number information element and process the call as if that information element was not received. + +The network shall disregard any value of the screening indicator, if received from the calling user. + +If the SETUP message does not contain the Calling party number information element the network shall use a default number associated with the calling user. The network shall set the screening indicator to “network provided”. + +If the Calling party number information element is included the network shall set the screening indicator to “user-provided, not screened”. + +NOTE – For the above condition, the procedures of basic call will provide for another calling number to be transported through the network. This other calling number will contain the default number, with an associated screening indicator set to “network provided”. + +The information determined by the procedures above, shall be forwarded to the destination local exchange, in association with the basic call request. + +The presentation indicator, as determined by the procedures of the CLIR supplementary service (see clause 4) shall be forwarded to the destination local exchange, in association with the basic call request. + +If the Calling party sub-address information element is available, it shall be passed transparently through the network. + +The actions at the originating local exchange when special arrangement applies are summarized in Table 3-2. + +TABLE 3-2/Q.951 + +###### **Information provided by the calling user and by the network when special arrangement applies** + +| Information provided by the calling user | | Information provided by the network to the called user | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------|------------------------------------------|----------------------------------------------------------| +| Calling party number received from the calling user (octet 4) | Type of number (octet 3) | Calling party number forwarded (if CLIR is not activated) (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No calling party number information element is provided by the calling user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 2) | +| Any digit sequence conforming to E.164 | “National number” or “international number” | Number provided by the user (Note 1) | User-provided, not screened | “International number” or “national number” (Notes 1, 2) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network path where the destination is in a different country.

2 As a network option the type of number forwarded to the called user may be coded “unknown” when a prefix is added to the number, in which case the number is organized according to the network dialling plan, i.e. prefixes or the absence of prefixes, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +###### 3.5.2.1.2 Exceptional procedures + +Not applicable. + +#### **3.5.2.2 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **3.5.2.3 Actions at the destination local exchange** + +###### **3.5.2.3.1 Normal operation** + +When the network sends a SETUP message to the called user and if the called user is provided with the CLIP supplementary service, the network shall check to see if the calling number is available. + +If the calling number is available and presentation is allowed according to the presentation indicator supplied together with the calling number, the network shall include the Calling party number information element in the SETUP message sent to the called user. If provided, the network shall also include the Calling party sub-address information element in the SETUP message. The presentation and screening indicators associated with the calling number, and the calling sub-address, received at the destination exchange, shall be passed transparently to the called user. + +The numbering plan identification field shall be coded either “ISDN/telephony numbering plan” (see Recommendation E.164)” or “unknown”. + +If presentation is not allowed according to the presentation indicator supplied together with the calling number, the network shall include the Calling party number information element in the SETUP message sent to the called user. The presentation indicator in the Calling party number information element shall indicate “presentation restricted”. The network shall encode the screening indicator, numbering plan identification and the type of number according to one of the following options: + +- i) The screening indicator shall indicate “network provided”. The type of number and numbering plan identification shall be set to “unknown”. +- ii) The screening indicator, numbering plan identification and the type of number shall be as received at the destination network. + +The network shall not include digits field. The network shall not include the Calling party sub-address information element in the SETUP message. + +If neither the calling number nor an indication that presentation is restricted is available at the destination local exchange the network shall include the Calling party number information element in the SETUP message sent to the called user. The presentation indicator shall be set to “number not available due to interworking”, and the screening indicator shall be set to “network provided”, the type of number and the numbering plan identification shall be set to “unknown” and the number digits field shall not be included. The network shall not include the Calling party sub-address information element, if provided, in the SETUP message. + +If the called user is not provided with the CLIP supplementary service, then neither the Calling party number nor the Calling party sub-address information elements shall be included in the SETUP message sent to the called user. + +If presentation is restricted but as a national network option the called user has the “override” category (e.g., police or emergency service) marked in the destination local exchange, the network shall include the Calling party number information element, and Calling party sub-address information element if the sub-address was supplied by the calling party in the SETUP message. In this case, the presentation and screening indicators shall be passed transparently to the called user. + +NOTE – If the presentation indicator in the Calling party number information element received by the user is set to “number not available due to interworking” or “presentation restricted”, the remaining information in the Calling party number information element should be ignored by the user. + +###### **3.5.2.3.2 Exceptional procedures** + +Not applicable. + +### **3.6 Interaction with other supplementary services** + +#### **3.6.1 Call Waiting** + +No interaction. + +#### **3.6.2 Call Transfer** + +No interaction. + +#### **3.6.3 Connected Line Identification Presentation** + +No interaction. + +#### **3.6.4 Connected Line Identification Restriction** + +No interaction. + +#### **3.6.5 Calling Line Identification Presentation** + +No interaction. + +#### **3.6.6 Calling Line Identification Restriction** + +The calling line identification will not be presented if the calling user has an arrangement to inhibit the presentation of his number(s) to the called party (calling user subscribes to the supplementary service “Calling Line Identification Restriction”). The only occasion when a user subscribing to CLIP can take precedence over CLIR is when the CLIP served user has an override category. This is a national option. + +#### **3.6.7 Closed User Group** + +No interaction. + +#### **3.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **3.6.9 Direct-Dialling-In** + +No interaction. + +#### **3.6.10 Call diversion (call forwarding) services** + +##### **3.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **3.6.10.2 Call Forwarding No Reply** + +As specified in 3/Q.952. + +##### **3.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +##### **3.6.10.4 Call Deflection** + +As specified in 5/952. + +#### **3.6.11 Line Hunting** + +No interaction. + +#### **3.6.12 Three-Party Service** + +No interaction. + +#### **3.6.13 User-to-User Signalling** + +##### **3.6.13.1 Service 1** + +No interaction. + +##### **3.6.13.2 Service 2** + +No interaction. + +##### **3.6.13.3 Service 3** + +No interaction. + +#### **3.6.14 Multiple Subscriber Number** + +Upon call initiation, if the ISDN number indicated by the MSN user terminal is not subscribed to for the interface, or if no numbering information is indicated, a default number or a number unavailable indication is provided to the CLIP user. + +#### **3.6.15 Call Hold** + +No interaction. + +#### **3.6.16 Advice of charge** + +No interaction. + +#### **3.6.17 Sub-addressing** + +No interaction. + +#### **3.6.18 Terminal Portability** + +No interaction. + +#### **3.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **3.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **3.6.21 Reverse Charging** + +No interaction. + +#### **3.6.22 Multilevel Precedence and Preemption** + +No interaction. + +### **3.7 Interaction with other networks** + +#### **3.7.1 Interaction with non-ISDNs** + +On calls incoming from some non-ISDNs, the calling number may be delivered to the destination ISDN without an indication of calling line identity restriction. In this case a number of options exist and the selection of the following is according to the network rules and regulations: + +- The network shall send the Calling party number information element according to 3.5.2.3.1, sixth paragraph, and shall include no Calling party sub-address information element. +- The network shall send the Calling party number information element according to 3.5.2.3.1, fourth paragraph, and shall include no Calling party sub-address information element. +- The network shall send the Calling party number information element according to 3.5.2.3.1, second paragraph, and shall include the Calling party sub-address information element if the calling sub-address is available. + +For some other non-ISDNs, no complete calling number may be available to the ISDN and therefore the full number of the calling user cannot be given to the called user who has been provided with the CLIP supplementary service. In this case the network shall send the Calling party number information element according to 3.5.2.3.1, sixth paragraph, and shall include no Calling party sub-address information element. + +On calls incoming from some non-ISDNs, the calling number may be delivered to the destination ISDN with an indication of Calling Line Identity Restriction. In this case the network shall send the Calling party number information element according to 3.5.2.3.1, second paragraph, and shall include the Calling party sub-address information element if the calling sub-address is available. + +As a network option the originating network may restrict any address information identifying the calling user from being forwarded to another network. + +#### **3.7.2 Procedures for interworking with private ISDNs** + +The procedures specified in 3.5.2 shall be used. + +NOTE – The provision of the special arrangement where an access is used by a private network is especially appropriate. + +### **3.8 Signalling flows** + +The signalling flows are not included as they are an integral part of the basic call control procedures. + +### **3.9 Parameter values (timers)** + +No specific timers are required. + +### **3.10 Dynamic description** + +See Figures 3-1 and 3-2. + +![Flowchart for Originating network side dynamic description (FIGURE 3-1/Q.951). The process starts with a 'Null 0' terminal, followed by a 'SETUP' message. A decision diamond asks 'CPN IE provided by the calling user?'. If 'No', it goes to 'Default number set SI = 11'. If 'Yes', it goes to another decision diamond 'Special arrangement?'. If 'Yes' to 'Special arrangement?', it goes to 'Set SI = 00'. If 'No', it goes to a third decision diamond 'Verification of the number?'. If 'OK', it goes to 'Complete the number set SI = 01'. If 'Not OK', it goes to 'Default number set SI = 11'. All three paths (SI = 11, SI = 01, and SI = 00) merge at a junction, followed by 'CLIR Service', 'Set type of number and numbering plan', 'Setup indication', and finally 'Call initiated 1' terminal.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph TD + Start([Null 0]) --> Setup[SETUP] + Setup --> CPN{CPN IE provided by the calling user?} + CPN -- No --> SI11_1[Default number set SI = 11] + CPN -- Yes --> Special{Special arrangement?} + Special -- Yes --> SI00[Set SI = 00] + Special -- No --> Verification{Verification of the number?} + Verification -- OK --> SI01[Complete the number set SI = 01] + Verification -- Not OK --> SI11_2[Default number set SI = 11] + SI11_1 --> Merge(( )) + SI01 --> Merge + SI11_2 --> Merge + SI00 --> Merge + Merge --> CLIR[CLIR Service] + CLIR --> SetType[Set type of number and numbering plan] + SetType --> SetupInd[Setup indication] + SetupInd --> End([Call initiated 1]) + +``` + +T1158670-94/d01 + +Flowchart for Originating network side dynamic description (FIGURE 3-1/Q.951). The process starts with a 'Null 0' terminal, followed by a 'SETUP' message. A decision diamond asks 'CPN IE provided by the calling user?'. If 'No', it goes to 'Default number set SI = 11'. If 'Yes', it goes to another decision diamond 'Special arrangement?'. If 'Yes' to 'Special arrangement?', it goes to 'Set SI = 00'. If 'No', it goes to a third decision diamond 'Verification of the number?'. If 'OK', it goes to 'Complete the number set SI = 01'. If 'Not OK', it goes to 'Default number set SI = 11'. All three paths (SI = 11, SI = 01, and SI = 00) merge at a junction, followed by 'CLIR Service', 'Set type of number and numbering plan', 'Setup indication', and finally 'Call initiated 1' terminal. + +## NOTES + +- 1 This procedure operates independently from any CLIP subscription by the calling user and is provided as part of the basic service. +- 2 The screenings indicator encodings are: + SI = 11 Network provided + SI = 01 User provided verified and passed + SI = 00 User provided not screened. + +FIGURE 3-1/Q.951 +**Originating network side dynamic description** + +![Flowchart for Destination network side dynamic description (Recommendation Q.951). The process starts with a 'Null 0' start node, followed by a 'Setup request' input. A decision 'User subscribed to CLIP?' branches the flow. If 'No', it leads to 'No CPN IE is sent to the called user'. If 'Yes', it leads to 'CPN IE available?'. If 'CPN IE available?' is 'No', it leads to 'CPN IE without number digits (Note)'. If 'Yes', it leads to 'Presentation allowed?'. If 'Presentation allowed?' is 'No', it leads to 'Override?'. If 'Override?' is 'No', it leads to 'No CPN IE is sent to the called user'. If 'Override?' is 'Yes', it leads to 'Send CPN IE as received'. If 'Presentation allowed?' is 'Yes', it also leads to 'Send CPN IE as received'. All paths for 'Send CPN IE as received' and the 'CPN IE without number digits (Note)' path merge and lead to a 'SETUP' output, followed by a 'Call present 6' end node.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +graph TD + Start([Null +0]) --> SetupReq[/Setup +request/] + SetupReq --> UserSubscribed{User +subscribed +to CLIP?} + UserSubscribed -- No --> NoCPNIE[No CPN IE is sent +to the called user] + UserSubscribed -- Yes --> CPNIEAvailable{CPN IE +available?} + CPNIEAvailable -- No --> CPNIEWithoutDigitsNote[CPN IE without +number digits +(Note)] + CPNIEAvailable -- Yes --> PresentationAllowed{Presentation +allowed?} + PresentationAllowed -- No --> Override{Override?} + Override -- No --> NoCPNIE + Override -- Yes --> SendCPNIE[Send CPN IE as +received] + PresentationAllowed -- Yes --> SendCPNIE + CPNIEWithoutDigitsNote --> Merge(( )) + SendCPNIE --> Merge + Merge --> SETUP[/SETUP/] + SETUP --> End([Call +present +6]) + +``` + +T1130140-91/d02 + +Flowchart for Destination network side dynamic description (Recommendation Q.951). The process starts with a 'Null 0' start node, followed by a 'Setup request' input. A decision 'User subscribed to CLIP?' branches the flow. If 'No', it leads to 'No CPN IE is sent to the called user'. If 'Yes', it leads to 'CPN IE available?'. If 'CPN IE available?' is 'No', it leads to 'CPN IE without number digits (Note)'. If 'Yes', it leads to 'Presentation allowed?'. If 'Presentation allowed?' is 'No', it leads to 'Override?'. If 'Override?' is 'No', it leads to 'No CPN IE is sent to the called user'. If 'Override?' is 'Yes', it leads to 'Send CPN IE as received'. If 'Presentation allowed?' is 'Yes', it also leads to 'Send CPN IE as received'. All paths for 'Send CPN IE as received' and the 'CPN IE without number digits (Note)' path merge and lead to a 'SETUP' output, followed by a 'Call present 6' end node. + +NOTE – In this case SI = 11 and PI = 10. + +FIGURE 3-2/Q.951 +Destination network side dynamic description + +## **Annex A** (referred to in clause 3) + +### **Two Calling party number information elements delivery option** + +### **A.1 Scope** + +This annex specifies additional procedures to be supported for the delivery of two Calling party number information elements to the served user. The support of these procedures (or of a part of these) is a network option. + +These additional features shall have no impact and shall place no requirement whatsoever on the provision and operation of the CLIP supplementary service defined in this Recommendation by public ISDNs that do not support these additional features, nor on the interchangeability of terminals. + +### **A.2 Additional procedures at the destination network side** + +The procedures described in this annex pertain to networks capable of delivering two numbers to the called user. + +#### **A.2.1 Normal operation** + +The procedures described in 3.5.2.3.1 apply in the following situations: + +- a) only a single number is available for delivery at the terminating exchange; +- b) presentation is restricted; +- c) the called user is not provided with the CLIP supplementary service; +- d) if the subscription option to two number delivery exists and the called user has not subscribed to two number delivery. + +When two numbers are available at the terminating exchange with screening indicators of one set to “network provided” and the other set to “user provided not screened”, the network shall deliver the information in two Calling party number information elements sent in a SETUP message to the called user. + +In addition, for some networks, when two numbers are available at the terminating exchange with screening indicators of one set to “network provided” and the other set to “user-provided, verified and failed”, the network shall deliver the information in two Calling party number information elements sent in a SETUP message to the called user. + +The order in which the Calling party number information elements appear in the SETUP message is a network option. + +If provided, the network shall also include the Calling party sub-address information element in the SETUP message. The presentation and screening indicators associated with the calling number, and the calling sub-address, received at the destination exchange, shall be passed transparently to the called user. + +#### **A.2.2 Exceptional procedures** + +Not applicable. + +### **A.3 Actions at the originating user** + +Actions at the originating user are as described in 3.5.2.1.1.1. + +### **A.4 Additional actions at the originating local exchange** + +The procedures of 3.5.2.1.1.2 shall apply except in the case where the screening function fails. + +When the screening function fails, the network shall set the screening indicator to “user-provided, verified and failed”. + +NOTE – For the above condition, the procedures of basic call will provide for another calling number to be transported through the network. This other calling number will contain the default number with an associated screening indicator set to “network provided”. + +The information determined by the procedures above shall be forwarded to the destination local exchange in association with the basic call request. + +The presentation indicator, as determined by the procedures of the CLIR supplementary service (see clause 4) shall be forwarded to the destination local exchange in association with the basic call request. + +If the Calling party sub-address information element is available, it shall be passed transparently through the network. + +The actions at the originating local exchange when screening fails are summarized in Table A.1. + +TABLE A-1/Q.951 + +#### **Information provided by the calling user and by the network when screening fails** + +| Information provided by the calling user | | Information provided by the network to the called user | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------|------------------------------------|----------------------------------------------------------------------------| +| Any digit sequence conforming to E.164 | “Unknown number”, “national number” or “international number” | Number provided by the user (Note 1) | User-provided, verified and failed | “Unknown number”, “international number” or “national number” (Notes 1, 2) | +| NOTES
1 A national number shall be converted to an international number at some point in the public network path where the destination is in a different country.
2 As a network option the type of number forwarded to the called user may be coded “unknown” when a prefix is added to the number, in which case the number is organized according to the network dialling plan, i.e. prefixes or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other. | | | | | + +## 4 Calling Line Identification Restriction (CLIR) + +### 4.1 Definition + +**calling line identification restriction (CLIR)** is a supplementary service offered to the calling party to restrict presentation of the calling party’s ISDN number and sub-address to the called party. + +### 4.2 Description + +#### 4.2.1 General description + +When CLIR is applicable and activated the originating network shall provide the destination network with an indication that the calling user’s ISDN number and sub-address (if provided by the calling user) are not allowed to be presented to the called user. In this case no calling user number and sub-address shall be included in the call offered to the called user. + +The presentation restriction function shall not influence the forwarding of the calling party number within the network as part of the basic service procedures. + +#### 4.2.2 Specific terminology + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the restriction of the calling line identification information (on a permanent or on a per-call basis) in association with outgoing calls. The served user is also known as the calling user. + +A **called user** is the receiver of a call, initiated by the served user, on which CLIR has been activated. + +An ISDN number is a number conforming to the numbering plan and structure specified in Recommendation E.164. + +CLIP     Calling Line Identification Presentation + +CLIR     Calling Line Identification Restriction + +#### **4.2.3     Qualification on the applicability to telecommunication services** + +See Recommendation I.251.4. + +#### **4.2.4     State definition** + +No specific states are required. + +### **4.3     Operational requirements** + +#### **4.3.1     Provision/withdrawal** + +See Recommendation I.251.4 + +#### **4.3.2     Requirements on the originating network side** + +All information pertaining to CLIR is inserted in the SETUP message sent as part of the basic call procedures according to Recommendation Q.931. + +#### **4.3.3     Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **4.3.4     Requirements on the destination network side** + +See 4.5.2.3. + +### **4.4     Coding requirements** + +The same as for 3.4. + +### **4.5     Signalling requirements** + +#### **4.5.1     Activation/deactivation/registration** + +Not applicable. + +#### **4.5.2     Invocation and operation** + +#### **4.5.2.1     Actions at the originating user** + +If the calling user wishes to override the default setting in the network, the SETUP message sent by the user shall contain the Calling party number information element with the presentation indicator set appropriately. + +#### **4.5.2.2     Actions at the originating local exchange** + +###### **4.5.2.2.1     Normal operation** + +If the calling user has subscribed to the Calling Line Identification Restriction supplementary service permanent mode, the presentation indicator received in the SETUP message will be ignored. The network shall set the presentation indicator to “presentation restricted”. + +If the calling user has subscribed to the CLIR supplementary service on a per-call basis and requests to override the default setting, the originating network shall set the presentation indicator according to that in the received Calling party number information element. + +The number digits, if included, shall be treated according to Table 3-1 or Table 3-2, and 3.5.2.1.1. + +If the CLIR is requested by the user on a per-call basis, and no Calling party number information element is included in the SETUP message, the originating network shall set the presentation indicator according to the subscribed default value. + +The presentation indicator shall be forwarded to the destination in association with the basic call request. + +###### **4.5.2.2.2 Exceptional procedures** + +Not applicable. + +#### **4.5.2.3 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **4.5.2.4 Actions at the destination local exchange** + +###### **4.5.2.4.1 Normal operation** + +The actions to be performed at the destination local exchange are provided as part of the CLIP service, described in 3.5.2.3.1. + +###### **4.5.2.4.2 Exceptional procedures** + +Not applicable. + +### **4.6 Interaction with other supplementary services** + +#### **4.6.1 Call Waiting** + +No interaction. + +#### **4.6.2 Call Transfer** + +No interaction. + +#### **4.6.3 Connected Line Identification Presentation** + +No interaction. + +#### **4.6.4 Connected Line Identification Restriction** + +No interaction. + +#### **4.6.5 Calling Line Identification Presentation** + +CLIR takes precedence over CLIP. The only occasion when a user subscribing to CLIP can take precedence over CLIR is when the CLIP served user has an override category. This is a national option. + +#### **4.6.6 Calling Line Identification Restriction** + +No interaction. + +#### **4.6.7 Closed User Group** + +No interaction. + +#### **4.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **4.6.9 Direct-Dialling-In** + +No interaction. + +#### **4.6.10 Call diversion (call forwarding) services** + +##### **4.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **4.6.10.2 Call Forwarding No Reply** + +As specified in 3/Q.952. + +##### **4.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +#### **4.6.10.4 Call Deflection** + +As specified in 5/Q.952. + +#### **4.6.11 Line Hunting** + +No interaction. + +#### **4.6.12 Three-Party Service** + +No interaction. + +#### **4.6.13 User-to-User Signalling** + +##### **4.6.13.1 Service 1** + +No interaction. + +##### **4.6.13.2 Service 2** + +No interaction. + +##### **4.6.13.3 Service 3** + +No interaction. + +#### **4.6.14 Multiple Subscriber Number** + +No interaction. + +#### **4.6.15 Call Hold** + +No interaction. + +#### **4.6.16 Advice of Charge** + +No interaction. + +#### **4.6.17 Sub-addressing** + +No interaction. + +#### **4.6.18 Terminal Portability** + +No interaction. + +#### **4.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **4.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **4.6.21 Reverse Charging** + +No interaction. + +#### **4.6.22 Multi-level Precedence and Preemption** + +No interaction. + +### **4.7 Interaction with other networks** + +#### **4.7.1 Interaction with other networks** + +On calls to or via non-ISDNs, it cannot be assured that a restriction indication can be carried to the destination network. As a national network option the originating network shall have the possibility to restrict any information identifying the calling party being forwarded to the destination network when CLIR is applicable. If a destination network receives a calling party number without any indication of presentation allowed or restricted, the destination network (the host network) will act according to its rules and regulations. For further information see 3.7. + +#### **4.7.2 Procedures for interworking with private ISDNs** + +The procedures specified in 4.5 shall be used. + +### **4.8 Signalling flows** + +The signalling flows are not included as they form an integral part of the basic call control procedures. + +### **4.9 Parameter values (timers)** + +No specific timers are required. + +### **4.10 Dynamic description** + +See Figure 4-1. + +## **5 Connected Line Identification Presentation (COLP)** + +### **5.1 Definition** + +**connected line identification presentation (COLP)** is a supplementary service offered to the calling party which provides the connected party's ISDN number, with possible additional sub-address information, to the calling party. + +### **5.2 Description** + +#### **5.2.1 General description** + +This supplementary service is not a dialling check but an indication to the calling subscriber of the connected ISDN number. In a full ISDN environment, the connected line identity must include all the information necessary to unambiguously identify the connected line. + +Moreover, the information on the connected line identity may include additional sub-address information (i.e. the Connected sub-address information element) generated by the connected user and transparently transported by the network. The network is not responsible for the content of this additional sub-address information. + +Unless COLR has been subscribed by the connected user, the network delivers the connected line identity to the calling user regardless of the terminal capability to handle the information. + +![Flowchart for CLIR service logic. It starts with 'CLIR service' in an oval, leading to a decision diamond 'Calling usersubscribed to CLIR?'. If 'No', it leads to 'PI = 00 set by the network'. If 'Yes', it leads to a triangle 'Subscription option'. From there, 'Permanent' leads to 'PI = 01 set by the network', and 'Temporary' leads to another decision diamond 'PI included in the CPN IE?'. If 'No', it leads to 'PI = default value'. If 'Yes', it leads to 'PI as received from the calling user'. All four paths converge at a junction marked with a valve symbol, which then leads to a circle with an 'X'.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +graph TD + Start([CLIR service]) --> D1{Calling usersubscribed to CLIR?} + D1 -- No --> P1[PI = 00 set by the network] + D1 -- Yes --> T1[/Subscription option/] + T1 -- Permanent --> P2[PI = 01 set by the network] + T1 -- Temporary --> D2{PI included in the CPN IE?} + D2 -- No --> P3[PI = default value] + D2 -- Yes --> P4[PI as received from the calling user] + P1 --> J(( )) + P2 --> J + P3 --> J + P4 --> J + J --> End((X)) + +``` + +T1124580-90/d03 + +Flowchart for CLIR service logic. It starts with 'CLIR service' in an oval, leading to a decision diamond 'Calling usersubscribed to CLIR?'. If 'No', it leads to 'PI = 00 set by the network'. If 'Yes', it leads to a triangle 'Subscription option'. From there, 'Permanent' leads to 'PI = 01 set by the network', and 'Temporary' leads to another decision diamond 'PI included in the CPN IE?'. If 'No', it leads to 'PI = default value'. If 'Yes', it leads to 'PI as received from the calling user'. All four paths converge at a junction marked with a valve symbol, which then leads to a circle with an 'X'. + +PI = 00 "presentation allowed" + PI = 01 "presentation restricted" + +FIGURE 4-1/Q.951 + Originating network side dynamic description + +#### 5.2.2 Specific terminology + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the presentation of the connected line identification information in association with outgoing calls. The served user is also known as the calling user. + +A **connected user** is the user that responded to the served user call request at the destination network and has been awarded the call by the network. The connected user need not have subscribed to the Connected Line Identification Presentation supplementary service. + +An ISDN number is a number conforming to the numbering plan structure specified in Recommendation E.164. + +An international number is an ISDN number structured as specified in Recommendation E.164. + +A national number or a national significant number is an ISDN number structured as specified in Recommendation E.164. + +A subscriber number is an ISDN number structured as specified in Recommendation E.164. + +An address is the number of the connected user (normally ISDN number), and a sub-address if provided by that user. + +A default number is an agreed number between the user at the connected side and the network provider. + +A special arrangement is an arrangement between a customer and a public network operator whereby customer supplied connected numbers are not screened by the public ISDN. + +COLP Connected Line Identification Presentation + +COLR Connected Line Identification Restriction + +#### **5.2.3 Qualification on the applicability to telecommunication services** + +See Recommendation I.251.5. + +#### **5.2.4 State definition** + +No specific states are required. + +### **5.3 Operational requirements** + +#### **5.3.1 Provision/withdrawal** + +See Recommendation I.251.5. + +#### **5.3.2 Requirements on the originating network side** + +See 5.5.2.1. + +#### **5.3.3 Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **5.3.4 Requirements on the destination network side** + +All information pertaining to COLP shall be inserted in the CONNECT message sent as part of the basic call procedures according to 5/Q.931. + +In the case where no information is provided by the connected user (as part of the basic call procedures), the network shall provide the default number associated with this user's access in the destination local exchange. When the connected number is provided by the connected user, the network can only verify that the number is within the set of numbers allocated to that user. Where a special arrangement exists with the connected user, no verification shall be performed. + +### **5.4 Coding requirements** + +The COLP supplementary service shall make use of the Connected number and Connected sub-address information elements inserted in the CONNECT message. + +All codesets used in this Recommendation are defined in codeset 0. + +TABLE 5-1/Q.951 +**CONNECT message content** + +Message type: CONNECT +Significance: local +Direction: both + +| Information element | Reference | Direction | Type | Length | +|--------------------------------------------------------------|-----------|-----------|------|--------| +| Protocol discriminator | 4.2/Q.931 | Both | M | 1 | +| Call reference | 4.3/Q.931 | Both | M | 2-* | +| Message type | 4.4/Q.931 | Both | M | 1 | +| Connected number | 5.4.1 | Both | O | 2-* | +| Connected sub-address | 5.4.1 | Both | O | 2-23 | +| NOTE – Other information elements as described in 3.1/Q.931. | | | | | + +#### 5.4.1 Connected number information element + +The purpose of the Connected number information element is to indicate which number is connected to a call. The connected number may be different from the called party number because of changes (e.g. call redirection, transfer) during the lifetime of a call. + +The Connected number information element is coded as shown in Figure 5-1. The maximum length of this information element is network dependent. + +![](171115f072e42b379238ed0dd438e9d7_img.jpg) + +| | | | | | | | | | +|-------------------------------------|---------------------------------------------------------------------------------------------------|--------------------------|---|---|-------------------------------|------------------------|-----------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 1      0      0      1      1      0      0
Connected number
Information element identifier | | | | | | Octet 1 | | +| Length of connected number contents | | | | | | | 2 | | +| 0/1
ext. | Type of number | | | | Numbering plan identification | | 3 | | +| 1
ext. | Presentation
indicator | 0      0      0
Spare | | | | Screening
indicator | 3a* | | +| 0
Spare | Number digits
(IA5 characters) | | | | | | 4
etc. | | + +FIGURE 5-1/Q.951 +**Connected number information element** + +#### 5.4.2 Connected sub-address information element + +The purpose of the Connected sub-address information element is to identify a sub-address associated with the connected number of a call. For the definition of sub-address, see Recommendation I.330. + +The Connected sub-address information element is coded as shown in Figure 5-2. Octets 3 and 4 are coded as in calling and Called party sub-address information elements in Recommendation Q.931. The maximum length of this information element is 23. + +![](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +| | | | | | | | | | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------|---|-------|---|---|-----------| +| bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +| 0 |
Sub-address
1001101
Information element identifier
| | | | | | 1 | | +| Length of calling party sub-address contents | | | | | | | | 2 | +| 1
ext. | Type of sub-address | | Odd/Even
indicator | 0 | Spare | | 0 | 3 | +| Sub-address information | | | | | | | | 4
etc. | + +FIGURE 5-2/Q.951 + +#### Connected sub-address information element + +### 5.5 Signalling requirements + +#### 5.5.1 Activation/deactivation/registration + +Not applicable. + +#### 5.5.2 Invocation and operation + +#### 5.5.2.1 Actions at the originating local exchange + +###### 5.5.2.1.1 Normal operation + +When the network sends a CONNECT message to the calling user and the calling user is provided with the COLP supplementary service, the network shall check to see if the connected number is available. + +If the connected number is available and presentation is allowed according to the presentation indicator supplied together with the connected number, the network shall include the Connected number information element in the CONNECT message sent to the calling user. If provided, the network shall also include the Connected sub-address information element in the CONNECT message. The presentation and screening indicators associated with the connected number and the connected sub-address received at the originating exchange shall be passed transparently to the calling user. + +The numbering plan identification field shall be coded either as “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”. + +If presentation is not allowed according to the presentation indicator supplied together with the connected number, the network shall include the Connected number information element in the CONNECT message sent to the calling user. The presentation indicator in the Connected number information element shall indicate “presentation restricted”. The network shall encode the screening indicator, numbering plan identification and the type of number according to one of the following options: + +- i) The screening indicator shall indicate “network provided”. The type of number and numbering plan identification shall be set to “unknown”. +- ii) The screening indicator, numbering plan identification and the type of number shall be passed as received at the destination network. + +The network shall not include number digits field. The network shall not include the Connected sub-address information element, in the CONNECT message. + +If neither the connected number nor an indication that presentation is restricted is available at the originating local exchange, the network shall include the Connected number information element in the CONNECT message sent to the calling user. The presentation indicator shall be set to “number not available due to interworking” and the screening indicator shall be set to “network provided”, the type of number and numbering plan identification shall be set to “unknown” and the number digits field shall not be included. The network shall not include the Connected sub-address information element, if provided, in the CONNECT message. + +If the calling user is not provided with the COLP supplementary service, then neither the Connected number nor the Connected sub-address information elements shall be included in the CONNECT message sent to the calling user. + +If presentation is restricted but as a national network option the calling user has the “override” category (e.g. police or emergency service) marked in the originating local exchange, the network shall include the Connected number information element and Connected sub-address information element if the sub-address was supplied by the connected user, in the CONNECT message. In this case, the presentation and screening indicators shall be passed transparently to the calling user. + +NOTE – If the presentation indicator in the Connected number information element received by the user is set to “number not available due to interworking” or “presentation restricted”, the remaining information in the Connected number information element should be ignored by the user. + +###### **5.5.2.1.2 Exceptional procedures** + +Not applicable. + +#### **5.5.2.2 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **5.5.2.3 Actions at the destination local exchange** + +###### **5.5.2.3.1 Normal operation** + +###### **5.5.2.3.1.1 Action at the destination user** + +These procedures shall be provided as part of the basic service and the connected user need not have subscribed to the COLP supplementary service. + +The numbering plan identification to be indicated within the Connected number information element, sent by the connected user shall be either “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”. + +NOTE – Either coding may be used and the treatment of both by the network is identical. + +Where the connected number included by the connected user is complete, the type of number to be indicated within the Connected number information element, sent by the connected user, shall be one of the following: + +- “*Subscriber number*” – In the case where the complete subscriber number is sent. +- “*National number*” – In the case where the complete national number is sent. +- “*International number*” – In the case where the complete international number is sent. + +Where a partial connected number is included by the connected user (e.g. to indicate digits specific to the Multiple Subscriber Number supplementary service) the user shall set the type of number to be indicated within the Connected number information element to “unknown”. + +###### **5.5.2.3.1.2 Actions at the destination local exchange if a special arrangement does not apply** + +These procedures shall be provided as part of the basic service and the connected user need not have subscribed to the COLP supplementary service. + +If multiple CONNECT messages are received from the called user, the network shall only perform the following procedures when it has decided which CONNECT message to acknowledge. + +Where a CONNECT message is received from the connected user, the network shall check to see if the Connected number and Connected sub-address information elements are included. + +If the Connected number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Connected number information element and process the call as if that information was not received. + +The network shall set the value of the screening indicator based on the outcome of the screening of the connected number. The network shall disregard any value of the screening indicator, if received from the connected user. + +If the Connected number information element is included, the network shall perform the screening function. + +NOTE 1 – Some networks may accept a full ISDN number with the addition of a prefix or escape digits to the number digits field and the type of number field set to “unknown”. + +If the connected number received from the connected user is determined to be correct, the network shall set the screening indicator to “user-provided, verified and passed”. + +If the screening function fails, the network shall note that the screening is failed and shall use a default number associated with the connected user. The network shall set the screening indicator to “network provided”. + +If the CONNECT message does not contain the Connected number information element, the network shall use a default number associated with the connected user. The network shall set the screening indicator to “network provided”. + +In the case where the connected user provides partial connected number information, and the number is a valid digit sequence for the user access arrangement, the network shall complete the number as appropriate. The network shall set the screening indicator to “user-provided, verified and passed”. + +NOTE 2 – In some cases the network cannot guarantee that the completed number identifies an end user. + +The information, as determined by the procedures above, shall be forwarded to the originating local exchange, in association with the basic call response. + +The presentation indicator, as determined by the procedures of the COLR supplementary service (see clause 6), shall be forwarded to the originating local exchange, in association with the basic call response. + +If the Connected sub-address information element is available, it shall be passed transparently through the network. + +The actions at the destination local exchange if a special arrangement does not apply are shown in Table 5-2. + +###### **5.5.2.3.1.3 Actions at the destination local exchange if a special arrangement applies** + +These procedures shall be provided as part of the basic service and the connected user need not have subscribed to the COLP supplementary service. + +If multiple CONNECT messages are received from the called user, the network shall only perform the following procedures when it has decided which CONNECT message to acknowledge. + +When a CONNECT message is received from the connected user, the network shall check to see if the Connected number and Connected sub-address information elements are included. + +If the Connected number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony numbering plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Connected number information element and process the call as if that information element was not received. + +If the Connected number information element is received with a coding of the type of number field other than “national number” or “international number”, then the network shall discard the Connected number information element and process the call as if that information element was not received. + +If the Connected number information element is received with a coding of the numbering plan identification field other than “ISDN/telephony number plan” (see Recommendation E.164) or “unknown”, then the network shall discard the Connected number information element and process the call as if that information element was not received. + +The network shall disregard any value of the screening indicator, if received from the connected user. + +TABLE 5-2/Q.951 + +###### **Information provided by the connected user and by the network when special arrangement does not apply** + +| Information provided by the connected user | | Information provided by the network to the calling user | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------| +| Connected number received from the connected user (octet 4) | Type of number (octet 3) | Connected number forwarded (if COLR is not activated) (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No connected number information element is provided by the connected user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 7) | +| Valid part of the number not sufficient for returning the call (Note 2) | “Unknown” | Completion of the number (Note 3) | User-provided verified and passed (Note 4) | “International number” or “national number” (Notes 1, 7) | +| Correct complete connected number (Note 5) | “Subscriber number” or “national number” or “international number” | Complete connected number | User-provided verified and passed | “International number” or “national number” (Notes 1, 7) | +| Incorrect number (Note 6) | Any type of number | Default number stored at the network side sufficient for returning the call | Network-provided | “International number” or “national number” (Notes 1, 7) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network where the origination is in a different country.

2 This assumes that the user's equipment provides that part of the number pertaining to its own (private) domain. This may be multiple subscriber number digits provided by a terminal equipment or an extension line number provided by a private ISDN. The network shall interpret the number digits and check if it is a valid digit sequence according to the agreements existing between the connected user and the network provider.

3 Completion means that the remaining part of the ISDN number associated with the appropriate access is added to the user provided part of the number.

4 The term “verified” implies matching the user provided number or part of this number(s) with the range(s) of numbers stored at the network side and it implies at least a valid format of user provided number information.

5 The term “correct” implies, from the network point of view, matching the subscriber number provided by the user with one of the range(s) of subscriber numbers stored at the network side.

6 The number provided by the user is discarded.

7 As a network option the type of number may be coded “unknown”, in which case, the number is organized according to the network dialling plan, i.e. prefixes, or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +If the CONNECT message does not contain the Connected number information element, the network shall use a default number associated with the connected user. The network shall set the screening indicator to “network provided”. + +The actions at the destination local exchange when special arrangement does not apply, are summarized in Table 5-2. + +The information, as determined by the procedures above, shall be forwarded to the origination local exchange, in association with the basic call response. + +If the Connected sub-address information element is available, it shall be passed transparently through the network. + +The presentation indicator, as determined by the procedures of the COLR supplementary service (see clause 6), shall be forwarded to the originating local exchange, in association with the basic call response. + +The actions at the destination local exchange when special arrangement applies are summarized in Table 5-3. + +If the Connected number information element is included, the network shall set the screening indicator forwarded to the calling user to “user-provided, not screened”. + +TABLE 5-3/Q.951 + +###### **Information provided by the connected user and by the network when special arrangement applies** + +| Information provided by the connected user | | Information provided by the network to the called user | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------|------------------------------------------|----------------------------------------------------------| +| Connected number received from the connected user (octet 4) | Type of number (octet 3) | Connected number forwarded if COLR is not activated (octet 4) | Screening indicator forwarded (octet 3a) | Type of number forwarded (octet 3) | +| No connected number information element is provided by the connected user | | Default number stored at the network side sufficient for returning the call | Network provided | “International number” or “national number” (Notes 1, 2) | +| Any digit sequence conforming to Rec. E.164 | “National number” or “international number” | Number provided by the user (Note 1) | User-provided, not screened | “International number” or “national number” (Notes 1, 2) | +|

NOTES

1 A national number shall be converted to an international number at some point in the public network path where the origination is in a different country.

2 As a network option the type of number may be coded “unknown”, in which case, the number is organized according to the network dialling plan, i.e. prefixes, or the absence of a prefix, shall be used to distinguish international numbers and national numbers from each other.

| | | | | + +###### 5.5.2.3.2 Exceptional procedures + +Not applicable. + +### 5.6 Interaction with other supplementary services + +#### 5.6.1 Call Waiting + +No interaction. + +#### 5.6.2 Call Transfer + +No interaction. + +#### 5.6.3 Connected Line Identification Presentation + +No interaction. + +#### 5.6.4 Connected Line Identification Restriction + +The connected line identification will not be presented to the calling user if the connected user has subscribed to COLR. The only occasion when a user subscribing to COLP can take precedence over COLR is when the COLP user has an override category. This is a national option. + +#### 5.6.5 Calling Line Identification Presentation + +No interaction. + +#### **5.6.6 Calling Line Identification Restriction** + +No interaction. + +#### **5.6.7 Closed User Group** + +No interaction. + +#### **5.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **5.6.9 Direct-Dialling-in** + +No interaction. + +#### **5.6.10 Call diversion (call forwarding) services** + +##### **5.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **5.6.10.2 Call Forwarding no Reply** + +As specified in 3/Q.952. + +##### **5.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +#### **5.6.10.4 Call Deflection** + +As specified in 5/Q.952. + +#### **5.6.11 Line Hunting** + +No interaction. + +#### **5.6.12 Three-Party Service** + +No interaction. + +#### **5.6.13 User-to-User Signalling** + +##### **5.6.13.1 Service 1** + +No interaction. + +##### **5.6.13.2 Service 2** + +No interaction. + +##### **5.6.13.3 Service 3** + +No interaction. + +#### **5.6.14 Multiple Subscriber Number** + +No interaction. + +#### **5.6.15 Call Hold** + +No interaction. + +#### **5.6.16 Advice of charge** + +No interaction. + +#### **5.6.17 Sub-addressing** + +No interaction. + +#### **5.6.18 Terminal Portability** + +No interaction. + +#### **5.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **5.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **5.6.21 Reverse Charging** + +No interaction. + +#### **5.6.22 Multilevel Precedence and Preemption** + +No interaction. + +### **5.7 Interaction with other networks** + +#### **5.7.1 Interaction with non-ISDNs** + +On calls destined for some non-ISDNs, the connected number may be delivered to the originating ISDN without an indication of connected line identity restriction. In this case a number of options exist and the selection of the following options is according to the network rules and regulations: + +- The network shall send the Connected number information element according to 5.5.2.1.1, sixth paragraph, and shall include no Connected sub-address information element. +- The network shall send the Connected number information element according to 5.5.2.1.1, fourth paragraph, and shall include no Connected sub-address information element. +- The network shall send the Connected number information element according to 5.5.2.1.1, second paragraph, and shall include the Connected sub-address information element if the connected sub-address is available. + +For some other non-ISDNs, no complete connected number may be available to the ISDN and therefore the full number of the connected user cannot be given to the calling user who has been provided with the COLP supplementary service. In this case the network shall send the Connected number information element according to 5.5.2.1.1, sixth paragraph, and shall include no Connected sub-address information element. + +On calls destined for some non-ISDNs, the connected number may be delivered to the originating ISDN with an indication of connected line identity restriction. In this case the network shall send the Connected number information element according to 5.5.2.1.1, second paragraph, and shall include the Connected sub-address information element if the connected sub-address is available. + +As a network option, the destination network may restrict any information identifying the connected user from being forwarded to another network. + +#### **5.7.2 Procedures for interworking with private ISDNs** + +These procedures specified in 5.5.2 shall be used. + +NOTE – The provision of the special arrangement where an access is used by a private network is especially appropriate. + +### **5.8 Signalling flows** + +The signalling flows are not included as they are an integral part of the basic call control procedures. + +### **5.9 Parameter values (timers)** + +No specific timers are required. + +### **5.10 Dynamic description** + +See Figures 5-3 and 5-4. + +![Flowchart for Destination network side dynamic description. The process starts with a call present, incoming call proceeding, and call received. It then connects and checks if CON IE is provided by the connected user. If yes, it checks for special arrangements. If yes, it sets SI = 00. If no, it verifies the number. If OK, it completes the number set (SI = 01). If not OK, it sets the default number set (SI = 11). If the user did not provide CON IE, it also sets the default number set (SI = 11). All paths lead to COLR Service, then setting the type of number and numbering plan, setup confirmation, and finally a connect request.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +``` + +graph TD + Start([Call present 6 +Incoming call proceeding 9 +Call received 7]) --> Connect[/CONNECT/] + Connect --> Decision1{CON IE +provided by +the connected +user?} + Decision1 -- No --> SI11_1[Default +number set +SI = 11] + Decision1 -- Yes --> Decision2{Special +arrangement?} + Decision2 -- Yes --> SI00[Set SI = 00] + Decision2 -- No --> Decision3{Verification +of the number?} + Decision3 -- OK --> SI01[Complete the +number set +SI = 01] + Decision3 -- Not OK --> SI11_2[Default +number set +SI = 11] + SI11_1 --> Merge(( )) + SI01 --> Merge + SI11_2 --> Merge + SI00 --> Merge + Merge --> COLR[COLR +Service] + COLR --> SetType[Set type of +number and +numbering plan] + SetType --> Setup[/Setup +confirmation/] + Setup --> End([Connect request 8]) + +``` + +T1158680-94/d04 + +Flowchart for Destination network side dynamic description. The process starts with a call present, incoming call proceeding, and call received. It then connects and checks if CON IE is provided by the connected user. If yes, it checks for special arrangements. If yes, it sets SI = 00. If no, it verifies the number. If OK, it completes the number set (SI = 01). If not OK, it sets the default number set (SI = 11). If the user did not provide CON IE, it also sets the default number set (SI = 11). All paths lead to COLR Service, then setting the type of number and numbering plan, setup confirmation, and finally a connect request. + +## NOTES + +- 1 This procedure operates independently from any COLP subscription by the connected user and is provided as part of the basic service. +- 2 The screening indicator encodings are: + - SI = 11 Network provided + - SI = 01 User provided verified and passed + - SI = 00 User provided verified not screened. + +FIGURE 5-3/Q.951 +Destination network side dynamic description + +![Flowchart for Originating network side dynamic description (Q.951). The process starts with a state 'Overlap sending 2 outgoing call proceeding 3 Call delivered 4', followed by an input 'Setup response'. A decision 'User subscribed to COLP?' leads to 'Yes' or 'No'. 'No' leads to 'No CON IE is sent to the calling user'. 'Yes' leads to 'CON IE available?'. 'CON IE available?' leads to 'No' (resulting in 'CON IE without number digits (Note)') or 'Yes' (leading to 'Presentation allowed?'). 'Presentation allowed?' leads to 'Yes' (resulting in 'Send CON IE as received') or 'No' (leading to 'Override?'). 'Override?' leads to 'Yes' (resulting in 'Send CON IE as received') or 'No' (resulting in 'CON IE without number digits'). All action blocks lead to the 'CONNECT' message and finally the 'Active 10' state.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +``` + +graph TD + Start([Overlap sending +2 outgoing call +proceeding 3 +Call delivered 4]) --> Setup[/Setup +response/] + Setup --> COLP{User +subscribed +to COLP?} + COLP -- No --> NoCON[No CON IE is sent +to the calling user] + COLP -- Yes --> CONIE{CON IE +available?} + CONIE -- No --> NoDigitsNote[CON IE without +number digits +(Note)] + CONIE -- Yes --> Presentation{Presentation +allowed?} + Presentation -- Yes --> SendCON[Send CON IE as +received] + Presentation -- No --> Override{Override?} + Override -- Yes --> SendCON + Override -- No --> NoDigits[CON IE without +number digits] + NoCON --> Connect[/CONNECT/] + NoDigits --> Connect + SendCON --> Connect + NoDigitsNote --> Connect + Connect --> Active10([Active 10]) + +``` + +T1130160-91/d05 + +Flowchart for Originating network side dynamic description (Q.951). The process starts with a state 'Overlap sending 2 outgoing call proceeding 3 Call delivered 4', followed by an input 'Setup response'. A decision 'User subscribed to COLP?' leads to 'Yes' or 'No'. 'No' leads to 'No CON IE is sent to the calling user'. 'Yes' leads to 'CON IE available?'. 'CON IE available?' leads to 'No' (resulting in 'CON IE without number digits (Note)') or 'Yes' (leading to 'Presentation allowed?'). 'Presentation allowed?' leads to 'Yes' (resulting in 'Send CON IE as received') or 'No' (leading to 'Override?'). 'Override?' leads to 'Yes' (resulting in 'Send CON IE as received') or 'No' (resulting in 'CON IE without number digits'). All action blocks lead to the 'CONNECT' message and finally the 'Active 10' state. + +NOTE – In this case SI=11 and PI=10. + +**FIGURE 5-4/Q.951** +**Originating network side dynamic description** + +# **6 Connected Line Identification Restriction (COLR)** + +## **6.1 Definition** + +**connected line identification restriction (COLR)**fs is a supplementary service offered to the connected party to restrict presentation of the connected party's ISDN number and sub-address to the calling party. + +### **6.2 Description** + +#### **6.2.1 General description** + +When COLR is applicable and activated, the destination network shall provide the originating network with an indication that the connected user's ISDN number and sub-address information is (if provided by the connected user) are not allowed to be presented to the calling user. In this case no connected number and sub-address shall be included in the call connected information to the calling user. + +The presentation restriction function shall not influence the forwarding of the connected number within the network as part of the basic service procedures. + +#### **6.2.2 Specific terminology** + +For the purposes of this Recommendation, the following terms apply: + +A **served user** is the user of a particular ISDN number who has subscribed to the restriction of the connected line identification information (on a permanent or on a per-call basis) in association with incoming calls. The served user may also be known as the connected user. + +A **calling user** is the initiator of a call, received by the served user, on which COLR has been activated. + +An ISDN number is a number conforming to the numbering plan and structure specified in Recommendation E.164. + +COLP Connected Line Identification Presentation + +COLR Connected Line Identification Restriction + +#### **6.2.3 Qualification on the applicability to telecommunication services** + +See Recommendation I.251.6. + +#### **6.2.4 State definition** + +No specific states are required. + +### **6.3 Operational requirements** + +#### **6.3.1 Provision/withdrawal** + +See Recommendation I.251.6. + +#### **6.3.2 Requirements on the originating network side** + +See 6.5.2.1. + +#### **6.3.3 Requirements in the network** + +This subclause is not applicable to DSS 1. + +#### **6.3.4 Requirements on the destination network side** + +All information pertaining to COLR is inserted in the CONNECT message sent as part of the basic call procedures according to 5/Q.931. + +### **6.4 Coding requirements** + +The same as for 5.4. + +### **6.5 Signalling requirements** + +#### **6.5.1 Activation/deactivation/registration** + +Not applicable. + +#### **6.5.2 Invocation and operation** + +##### **6.5.2.1 Actions at the originating local exchange** + +###### **6.5.2.1.1 Normal operation** + +The actions to be performed at the originating local exchange are provided as part of the COLP supplementary service, described in 5.5.2.1.1. + +###### **6.5.2.1.2 Exceptional procedures** + +Not applicable. + +#### **6.5.2.2 Actions at the transit exchange** + +This subclause is not applicable to DSS 1. + +#### **6.5.2.3 Action at the destination user** + +If the connected user wishes to override the default setting in the network, the CONNECT message sent by the user shall contain the Connected number information element with the presentation indicator set appropriately. + +#### **6.5.2.4 Actions at the destination local exchange** + +###### **6.5.2.4.1 Normal operation** + +If the connected user has subscribed to the Connected Line Identification Restriction supplementary service permanent mode, the presentation indicator received in the CONNECT message will be ignored. The network shall set the presentation indicator to “presentation restricted”. + +If the connected user has subscribed to the COLR supplementary service on a per-call basis and requests to override the default setting, the destination network shall set the presentation indicator according to that in the received Connected number information element. + +The digits, if included, shall be treated according to Table 5-2 or Table 5-3, and 5.5.2.3.1. + +If COLR is requested by the user on a per-call basis, and no Connected number information element is included in the CONNECT message, the destination network shall set the presentation indicator according to the subscriber value. + +The presentation indicator shall be forwarded to the originating network in association with the basic call response. + +###### **6.5.2.4.2 Exceptional procedures** + +Not applicable. + +### **6.6 Interaction with other supplementary services** + +#### **6.6.1 Call Waiting** + +No interaction. + +#### **6.6.2 Call Transfer** + +No interaction. + +#### **6.6.3 Connected Line Identification Presentation** + +COLR will take precedence over COLP. The only occasion when a user subscribing to COLP can take precedence over COLR is when the user has an override category. This is a national option. + +#### **6.6.4 Connected Line Identification Restriction** + +No interaction. + +#### **6.6.5 Calling Line Identification Presentation** + +No interaction. + +#### **6.6.6 Calling Line Identification Restriction** + +No interaction. + +#### **6.6.7 Closed User Group** + +No interaction. + +#### **6.6.8 Conference Calling** + +As specified in 1/Q.954. + +#### **6.6.9 Direct-Dialling-In** + +No interaction. + +#### **6.6.10 Call diversion (call forwarding) services** + +##### **6.6.10.1 Call Forwarding Busy** + +As specified in 2/Q.952. + +##### **6.6.10.2 Call Forwarding no Reply** + +As specified in 3/Q.952. + +##### **6.6.10.3 Call Forwarding Unconditional** + +As specified in 4/Q.952. + +##### **6.6.10.4 Call Deflection** + +As specified in 5/Q.952. + +#### **6.6.11 Line Hunting** + +No interaction. + +#### **6.6.12 Three-Party Service** + +No interaction. + +#### **6.6.13 User-to-User Signalling** + +##### **6.6.13.1 Service 1** + +No interaction. + +##### **6.6.13.2 Service 2** + +No interaction. + +##### **6.6.13.3 Service 3** + +No interaction. + +#### **6.6.14 Multiple Subscriber Number** + +No interaction. + +#### **6.6.15 Call Hold** + +No interaction. + +#### **6.6.16 Advice of Charge** + +No interaction. + +#### **6.6.17 Sub-addressing** + +No interaction. + +#### **6.6.18 Terminal Portability** + +No interaction. + +#### **6.6.19 Completion of Calls to Busy Subscriber** + +As specified in 3/Q.953. + +#### **6.6.20 Malicious Call Identification** + +As specified in clause 7. + +#### **6.6.21 Reverse Charging** + +No interaction. + +#### **6.6.22 Multilevel Precedence and Preemption** + +No interaction. + +### **6.7 Interaction with other networks** + +#### **6.7.1 Interaction with non-ISDNs** + +On calls to or via non-ISDNs, it cannot be assured that a restriction indication can be carried to the originating network. As a national network option the destination network shall have the possibility to restrict any information identifying the connected party from being returned to the originating network when COLR is applicable. If an originating network receives a connected party ISDN number without any indication of presentation allowed or restricted, the originating network (the host network) will act according to its rules and regulations. For further information see 5.7. + +#### **6.7.2 Procedures for interworking with private ISDNs** + +The procedures specified in 6.5 shall be used. + +### **6.8 Signalling flows** + +The signalling flows are not included as they form an integral part of the basic call control procedures. + +### **6.9 Parameter values (timers)** + +No specific timers are required. + +### **6.10 Dynamic description** + +See Figure 6-1. + +![Flowchart for Destination network side dynamic description. It starts with 'COLR service' leading to a decision 'Connected user subscribed to COLR?'. If 'No', PI = 00 set by the network. If 'Yes', it goes to 'Subscription option'. If 'Permanent', PI = 01 set by the network. If 'Temporary', it goes to 'PI included in the CON IE?'. If 'No', PI = default value. If 'Yes', PI as received from the connected user. All paths merge at a junction marked with a circle containing an X.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +``` + +graph TD + Start([COLR service]) --> Dec1{Connected user +subscribed to +COLR?} + Dec1 -- No --> PI00[PI = 00 set by +the network] + Dec1 -- Yes --> Dec2{Subscription +option} + Dec2 -- Permanent --> PI01[PI = 01 set by +the network] + Dec2 -- Temporary --> Dec3{PI included +in the CON IE?} + Dec3 -- No --> PIDefault[PI = default +value] + Dec3 -- Yes --> PIUser[PI as received +from the +connected user] + PI00 --> Merge((X)) + PI01 --> Merge + PIDefault --> Merge + PIUser --> Merge + +``` + +T1124610-90/d06 + +Flowchart for Destination network side dynamic description. It starts with 'COLR service' leading to a decision 'Connected user subscribed to COLR?'. If 'No', PI = 00 set by the network. If 'Yes', it goes to 'Subscription option'. If 'Permanent', PI = 01 set by the network. If 'Temporary', it goes to 'PI included in the CON IE?'. If 'No', PI = default value. If 'Yes', PI as received from the connected user. All paths merge at a junction marked with a circle containing an X. + +PI = 00 “presentation allowed” +PI = 01 “presentation restricted” + +**FIGURE 6-1/Q.951** +**Destination network side dynamic description** \ No newline at end of file